I think I had the same issue, and it went away after I left more room inbetween the ports for each gameserver, an I did not use anything in the 2702x range.
I know its not a good solution, but its worth a try. Andrew Armstrong wrote: > Hi, > > > > We are experiencing some problems trying to run a few Team Fortress 2 > servers on a new Windows Server 2008 64bit machine. > > > > While the server attempts to start, the following error messages appear in > the server console: > > > > -- > > WARNING: NNET_OpenSocket: bind: WSAEINVAL > > <other log lines> > > steamservice.cpp (275) : Assertion Failed: Failed to start in-process Steam > Service > > CreateBoundSocket: ::bind returned Win32 error 10022 > > cminterface.cpp (598) : Assertion Failed: NULL != m_hConnection > > -- > > > > We also receive the following error at times: > > > > -- > > A dialog box appears with an OK button saying: "Couldn't allocate any hltv > IP port" > > -- > > > > I know someone is going to suggest the tv_port variable, and so we tried > setting that to a unique, free port. This removes the "Couldn't allocate any > hltv IP port" error. We have had hltv support disabled though the entire > time. > > > > However, the server still boots up with the "WARNING: NN_NET.." Log lines as > above, and the server remains "insecure": 1.0.4.9/14 3755 insecure (secure > mode enabled, disconnected from Steam 3) > > > > Please note we run the exact same server configuration on Windows 2003 32bit > without any problems. > > > > Is this a known issue at Valve (a quick google indicates a few other people > have the same problem), or is there a fix available? > > > > Thanks, > > Andrew > > _______________________________________________ > 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
