Grant, Go grab a copy of tcpview from sysinternals: http://www.sysinternals.com/Utilities/TcpView.html
and then look at the ports that are being assigned to each server. If you aren't assigning specific ports then SRCDS automatically increments ports for itself. The ports you want to be concerned about are the sports on 26900, etc. You should not have any servers sharing the same ports. If you start up all of the servers at the same time you might have a momentary conflict, try starting up each server in sequence with a 5 or 10 second delay between each. Also, if you have an HLDS server on the same box you may cause a similar problem. There, you'll have to add -sport 269xx where xx is different from any of the 7 srcds servers sports. Using -sport on SRCDS launch properties does not work right now but it does work on HLDS. Here are 4 SRCDS servers I started up and what I saw: srcds.exe:3708 TCP 67.100.129.82:27015 0.0.0.0:0 LISTENING srcds.exe:3708 UDP 0.0.0.0:26900 *:* srcds.exe:3708 UDP 0.0.0.0:27005 *:* srcds.exe:3708 UDP 0.0.0.0:27015 *:* srcds.exe:3708 UDP 0.0.0.0:27020 *:* srcds.exe:3884 TCP 67.100.129.82:27016 0.0.0.0:0 LISTENING srcds.exe:3884 UDP 0.0.0.0:26901 *:* srcds.exe:3884 UDP 0.0.0.0:27006 *:* srcds.exe:3884 UDP 0.0.0.0:27016 *:* srcds.exe:3884 UDP 0.0.0.0:27021 *:* srcds.exe:4068 TCP 67.100.129.82:27017 0.0.0.0:0 LISTENING srcds.exe:4068 UDP 0.0.0.0:26902 *:* srcds.exe:4068 UDP 0.0.0.0:27007 *:* srcds.exe:4068 UDP 0.0.0.0:27017 *:* srcds.exe:4068 UDP 0.0.0.0:27022 *:* srcds.exe:984 TCP 67.100.129.82:1145 68.142.72.250:27038 SYN_SENT srcds.exe:984 TCP 67.100.129.82:27018 0.0.0.0:0 LISTENING srcds.exe:984 UDP 0.0.0.0:26903 *:* srcds.exe:984 UDP 0.0.0.0:27008 *:* srcds.exe:984 UDP 0.0.0.0:27018 *:* srcds.exe:984 UDP 0.0.0.0:27023 *:* ----- Original Message ----- From: "Grant Harmanis" To: <[email protected]> Sent: Wednesday, June 28, 2006 11:35 PM Subject: [hlds] VAC Problems
I don't know if this problem has been rectified, but I'm struggling to find literature on the subject. 3/7 servers I'm running for DoD:Source are coming up with being secure, but they cannot connect to steam3 and thus are insecure. All necessary ports are open, and no matter what I do, it seems nothing can remedy the problem. E.g.: hostname: xxxxxxxxxxxxxx version : 1.0.0.5/7 2782 insecure (secure mode enabled, disconnected from Steam3) udp/ip : xxx.xxx.xxx.xx:xxxxx map : dod_colmar at: 0 x, 0 y, 0 z players : 31 (32 max) The other 4 servers that are running are running of the same kind of config, yet they are secure, it really boggles the mind as to what the problem can be. Your help will be appreciated. cheers
_______________________________________________ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds
