Previous to the last big CS:S update, I had been able to set up a server, and using the command sv_lan 0 in the console, the server was able to be seen and played online.

Since the last big update, whenever I set up a server and type in sv_lan 0 nothing happens to indicate it has registered, yet it seems to still require this command. So far so good.

Yet when anyone tries to connect it gives them a message saying they are logged in elsewhere on Steam. I have tried to connect to a friend's server and I get the same error. We are not running two copies (obviously) nor are there any updates in progress etc. Everything is set as it was before and no settings have been changed.

Does anyone know if there is some new fancy shizzle I have to do to allow players on the server? Anyone know why this error occurs? We can both connect to public servers fine, just the private one is not happening.

I have no idea, but I couldn't get a listen server to work that way at all. Had to run a local dedicated server.

Yeah now when I hook up with mates I get the same problem until my bitch went and bought NWA's book entitled 'The art of sucking dick'

last edited by mission at 21:32:00 19/Dec/05

Are you setting up a dedicated css server or what?

9/10 times i have problems like this I go to http://support.steampowered.com/cgi-bin/steampowered.cfg/php/enduser/std_alp.php

.

Type in your exact error number or error message, and it will give you some solutions to your problem. I tryed searching but you need the exact wording or error number. See how it goes.

sv_lan has to be entered by command line I believe, not in the console.

Yeh, try +sv_lan 0 from command line.

Haha, welcome to Valve Software, where things work one day and stop the next!

Haha, welcome to Valve Software, where things work one day and stop the next!

my dedicated windows server worked just fine until one update, then it still didn't work 2 or 3 updates later. To fix it I had to rar up the dir, uninstall it from the add/remove programs menu, then just extract the rar back to its original directory and run it. It still runs just fine. What the HELL did valve do to it? Must be a registry entry messing it about.

last edited by whoop at 21:02:57 20/Dec/05