Natural Selection Dedicated Server on Lan Options

[BadLife]

I want to run a dedicated NS 3.04 server on the Lan but the darn thing always tries to connect to the master server. Even if I allow it to use the internet it still wont let clients join. It worked OK in NS 3.03 I had to let everone go to the net then I could kill the connection. Now it wont work at all Any idea how to tell it not to bork off to the net ? This is a Won setup i guess as I have to copy the NSP folder to the Half-life folder. It works OK as a listen server

[BadLife]

OK I figured it out you need to rename your woncomm.lst file in the half-life\valve folder and make a new one replaceing the server names with the IP address of the dedicated server on the lan. Like so


// Server Lists
//
Titan
{
192.168.0.1:6003
192.168.0.1:6003
192.168.0.1:6003
}

Auth
{
192.168.0.1:7002
192.168.0.1:7002
192.268.0.1:7002
}

Master
{
192.168.0.1:27010
192.168.0.1:27010
192.168.0.1:27010
}

ModServer
{
192.168.0.1:27011
192.168.0.1:27011
192.168.0.1:27011
}

Secure
{
192.168.0.1:27012
192.168.0.1:27012
192.168.0.1:27012
}

Of course if you use another internal IP addressing you will have to use it.

Then you need to edit your server.cfg in the NSP folder and make sure it says


///////////////////////////////
// Dedicated server specific //
///////////////////////////////
sv_lan 1
nomaster 1

Then the dedicated server self auths the server and the clients. By the way all of my half-life installs have retail half-life disks with individual CD Keys. I just want to play on the lan and not have to mess with multiple copies of Steam or haveing a connectionto the net up while I can't mointor it

Also you may have to put the woncomm.lst back to play on line I don't know about that as I never play online anymore