I know I read about this somewhere else I just can't find it. Is it possible to join a Dedicated NS Server from the same computer? When I try it, it says my CD key is in use. I heard there was someway around this. Is that true and how do you do it.
if u run a ns server and u play on it then it isnt a dedicated server <!--emo&;)--><img src='http://www.unknownworlds.com/forums/html/emoticons/wink.gif' border='0' style='vertical-align:middle' alt='wink.gif'><!--endemo-->
This is what I would like to do. Start a NS dedicated server. Then start NS up and connect to the server. This way when I don't want to play NS I can close it but still have the NS server running. If this isn't possible, fine. I just thought I saw a topic were somone got around this by changing ports or something. I didn't read it carefully becuase I was looking for something different at the time. Now I can't find that topic.
Basically, the problem is that the client is trying to use the same port as the server, and must be on different ports. Since most servers are on 27015 by default, using port as 27016 often fixes the problem.
The +connect switch is only needed if you can't see your server in the browsing lists.
TY very very much. I am not doing this to have a public server. Just for my team to have a place to practice, even if I am not their or busy doing other things.
I know _how_ to do it, but really don't know _why_ you would do it. I learned to do it while testing some DS stuff at home (RCBOT problems), and I only had one functioning PC at the time. After that, I stood up a cheapo 600MHz box for testing.
I only needed to do this because I was having a problem where the listen server and DS server were acting different (listen worked, DS crashed), so I needed to test both.
I run a 10 player dedicated server AND play on it from the same machine with NO problems. First install your dedicated server "Win32_HLDS_4.1.1.0_full" and then your NS mod "ns_install_v1", updating it to 1.04. This server is NOT equipped to play from. Also add ServerDoc to restart your server when it crashes, and make your target line look like this <!--QuoteBegin--></span><table border='0' align='center' width='95%' cellpadding='3' cellspacing='1'><tr><td><b>QUOTE</b> </td></tr><tr><td id='QUOTE'><!--QuoteEBegin-->"C:\Program Files\ServerDoc\serverdoc.exe" C:\HLServer\hlds.exe -console -game ns +port 27017 +maxplayers 10 +noipx +map ns_eclipse<!--QuoteEnd--></td></tr></table><span class='postcolor'><!--QuoteEEnd-->Be certain to make the port 27016 or 27017 as your client will use 27015.
You may join this server using your hl/ns client (the one you play on now)
I do the same thing when I host temporary ded. servers. Start it up, do sv_lan 1, join, do sv_lan 1, others can connect. Happy days are here again, just so long as you don't look at two hundred entities. There may be a small amount of additional lag when you do that <!--emo&:)--><img src='http://www.unknownworlds.com/forums/html/emoticons/smile.gif' border='0' style='vertical-align:middle' alt='smile.gif'><!--endemo--> You can do your second sv_lan with rcon.
Sidenote: Client connection uses 27005, not 27015. So don't worry too much about changing the port number.
<!--QuoteBegin--></span><table border='0' align='center' width='95%' cellpadding='3' cellspacing='1'><tr><td><b>QUOTE</b> </td></tr><tr><td id='QUOTE'><!--QuoteEBegin-->Sidenote: Client connection uses 27005, not 27015. So don't worry too much about changing the port number. <!--QuoteEnd--></td></tr></table><span class='postcolor'><!--QuoteEEnd-->Understand that lordbluewolf is talking about running a listenserver, NOT a seperate dedicated server you can play on from the same machine. As Squidget said <!--QuoteBegin--></span><table border='0' align='center' width='95%' cellpadding='3' cellspacing='1'><tr><td><b>QUOTE</b> </td></tr><tr><td id='QUOTE'><!--QuoteEBegin-->Basically, the problem is that the client is trying to use the same port as the server, and must be on different ports. Since most servers are on 27015 by default, using port as 27016 often fixes the problem. <!--QuoteEnd--></td></tr></table><span class='postcolor'><!--QuoteEEnd-->
Negative on the listenserver, I use seperate dedicated server and client. Please read posts harder before you try to interpret them to others. At least test it before you say something as well.
Or perhaps I'm being presumptious. My client connects to my local dedicated server (same computer) using port 27005. There are no conflicts for me.
Indeed you are being presumptuous. To run a dedicated server and join from a client on the same machine requires you to ensure the port numbers aren't the same.
That's my point exactly: The default ports are different, so there should be no need to change them. Now I am totally confused, I never had port conflicts...
Comments
You must add one or two things to the command line of your shortcut:
-port <newport>
+connect <server IP>:<server port>
example:
-port 27016 +connect 127.0.0.4:27015
Basically, the problem is that the client is trying to use the same port as the server, and must be on different ports. Since most servers are on 27015 by default, using port as 27016 often fixes the problem.
The +connect switch is only needed if you can't see your server in the browsing lists.
See this website for all kinds of HLDS info:
<a href='http://half-life.gamehelp.com/info.html' target='_blank'>http://half-life.gamehelp.com/info.html</a>
but it should not.
I am not doing this to have a public server. Just for my team to have a place to practice, even if I am not their or busy doing other things.
I'll add my agreement to the others here, tho.
I know _how_ to do it, but really don't know _why_ you would do it. I learned to do it while testing some DS stuff at home (RCBOT problems), and I only had one functioning PC at the time. After that, I stood up a cheapo 600MHz box for testing.
I only needed to do this because I was having a problem where the listen server and DS server were acting different (listen worked, DS crashed), so I needed to test both.
You may join this server using your hl/ns client (the one you play on now)
Sidenote: Client connection uses 27005, not 27015. So don't worry too much about changing the port number.
<!--QuoteEnd--></td></tr></table><span class='postcolor'><!--QuoteEEnd-->
Or perhaps I'm being presumptious. My client connects to my local dedicated server (same computer) using port 27005. There are no conflicts for me.