If port 27015 doesn't work then use another. One thing I've noticed is that if you run an HL Client it will grab 27015 and if you try to run a server after running the client it will fail to allocate.
Also, if the client crashes, WIN may not release the allocated ports for a long time. One last thing, Kazaa or one of the other P2P programs has been reported to be using 27015 (go figure). before you run the server, go to a command prompt and run netstat -ano to see what ports are already allocated. qUiCkSiLvEr ----- Original Message ----- From: Rob Harwood Sent: Tuesday, June 29, 2004 3:36 PM The heartbeat/master server is irrelevant here, HLDS is failing to bind to the _local_ ip/port, I'm assuming he has ruled out any other process using port 27015 so the next guess is that the IP is invalid, so if he overrides it then the problem may just disappear. If hes using two modems, chances are the config for one of them is fuxed. -- Rob > ----- Original Message ----- > From: "Steve!" > Sent: Tuesday, June 29, 2004 6:07 AM > > > WAENING: UDP_OpenSocket: port: 27015 bind: WSAEADDRNOTAVAIL > > > > and yeah I've added the ports in the NAT section, maybe it's the pure fact that it uses NAT? > > > > In any event, certainly not an 'out of the box' job.. > > > > Steve! _______________________________________________ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds
