HLDS Day of Defeat not connecting

[fiercetiger]

Hello fellow gamers,

This is the current problem we have with our VDS using Win2008 R2:

Our Day Of Defeat (HL1) setup works fine when there is only one active IP.
But fails to connect to its assigned IP when our other two IPs are active. And by active I mean as setup in the instructions by NFO (viewtopic.php?f=68&t=5421).
Now, it fails to connect whether or not we are running any other games on the two additional IPs.
I have ran the game from a Short-Cut with launch commands (including the given IP & port). I have also tried HL Server Monitor v2.4.1 to launch.
I have ran straight from the HLDS.exe. Which gives me the following in the console tab:

Code: Select all

L 12/11/2015 - 00:13:07: Log file started (file "logs\L1211008.log") (game "dod") (version "48/1.1.2.6/6153")
Connection to Steam servers successful.
   VAC secure mode is activated.

I have tried using all the IPs available.
The game loads up and shows it running, but when I type in "status" when using the launch command "-console", it states "Can't "status", not connected."

The strange thing is that when I remove the two additional IPs and leave only one IP, then DOD runs fine.
I have tried blocking the TCP as mentioned here (viewtopic.php?f=46&t=8430 ) but that did not work either.

NFO staff said it's a software problem.

[soja]

Can you post your full command line used for the first server?

Also, are the IP addresses currently assigned to the OS? If so, can you please post them here?

[soja]

Just to note, I just spun up a quick VPS on my home server and gave it 3 IPs and I was able to boot up a dod server on each IP, with all showing up on my network:
http://i.gflclan.com/20151211034527.png
(Running on Windows Server 2008R2 atop vmware esxi 6.0)

So your problem should be fixable, we just need to pinpoint what's wrong.

[fiercetiger]

Thanks for replying so quickly to help, soja.
But it looks like I've accidently hit on the solution.

But here are the Launch command lines:

Code: Select all

Day of Defeat: C:\HL1servers\hlds.exe -game dod  +ip 66.151.138.111 -port 27015 +sv_lan 0 +maxplayers 30 -nocrashdialog
CSGO: srcds -game csgo -console -ip 66.151.138.147 -port 27018 +sv_lan 0 -noipx +maxplayers 16 +map de_dust -nohltv -usercon
Dino D-Day: srcds -game dinodday -ip 66.151.138.138  -port 27017 -console  +sv_lan 0 -noipx +maxplayers 14 +map ddd_canyon -nohltv -usercon

I recheck the liblist.gam file for DOD, since we want to run AMXX mod (which of course requires MetaMod). So, I reset it to it original ... gamedll "dlls\dod.dll" instead of redirecting it to... gamedll "addons\metamod\dlls\metamod.dll"
But it still failed.
Then I thought that maybe... gamedll "dlls\dod.dll" should be called somewhere. So, I put it in metamod's "config.ini" file.
And now it is working.

Hopefully, others can avoid my prolonged agony of trying to figure this problem out by reading this post.
It is strange that it worked when only one IP was available on the VDS without that fix.

[soja]

Well I don't really understand why that fixed it, but i'm glad you are up and running now

If you run into any other issues, please ask for help!

[fiercetiger]

Thanks for checking that soja.

When I use the "-console" launch command, it doesn't seem to connect to the outside world.
But launching with Valve's dialog boxes works fine.
I am using HL Server Monitor v2.4.1 to launch my other two Source games, since that program can monitor and restart games.
Any suggestions why "-console" launch command wouldn't work.

[soja]

Do you have your map specified in an autoexec.cfg file? If not you need to add +map to your command line. Mine looks like this:

Code: Select all

hlds.exe -console +ip 192.168.1.109 +map dod_anzio -game dod +maxplayers 32

EDIT: Pretty sure that's your problem

Here is what I get if I don't specify a map in my command line:


Add +map and you should be good to go. The gui automatically selects a map for you in the dropdown so that's why it works without console