That error is generated when the server tries to open a listening socket, and the OS tells the server that it can't. This usually means that another server on the same box or some other program already has that port open. It could also mean that the ip address in your startup command line is not allocated to your machine. For example, if you are using a dsl router that has external ip of 64.155.55.5 and your server machine has ip address of 10.0.0.1, then you must specify -ip 10.0.0.1 on your startup command line.
Dave -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Ned Haskin Sent: Monday, March 21, 2005 10:32 AM To: hlds Subject: [hlds] Couldn't allocate dedicated server UDP port OOP's I had the external ip for the dsl bridge in the bat file not the server box's local ip, stupid me. Up and running now! Just got my 1st dedicated CS Source server updated and ready to go, so I though. Ran the bat and got the start dedicated server screen, customized my settings and hit okay. and got this error 'Couldn't allocate dedicated server UDP port' . My firewall has srcds.exe set as a server it should be able to use any port it wants. The srcds.exe that is steam dependent does, the firewall lists them separately as it should. I went in and added expert rules to make sure. That didn't work either. _So I turned off the fire wall_, same error, getting frustrated here. The box is running 2K pro sp4 & Zonealarm, have no problems running source dedicated server from steam, just the stand alone server has the problem. _______________________________________________ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds _______________________________________________ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds
