Multiple DCS Servers on the same IP address?

[TWC_Alamo]

This is my first post on the forum.

 

I am trying to set up two servers on the same public IP address. Each DCS server is running on a separate computer on my internal LAN and is assigned a different port address (10308 and 10307). However only the server using port 10308 appears in the master server list.

 

I see other people doing this, for instance, currently there are four virtual-TFS51.de Dedicated Servers @ ip = 144.76.35.114 using ports 10302, 10304, 10305 and 10307.

 

It seems that it should be straight forward: just assign a different port number to each server on the NEW SERVER screen and then set up port forwarding on the router to forward external connections from that port to the correct internal IP address of the server.

 

I have one server using the default port of 10308 and set the second server to use 10307, but only the port 10308 server appears in the master server list. I have disabled the Windows 7 Firewall on the 2nd server to avoid local firewall problems without luck and even tried moving it into the router's DMZ also without luck. If I change the port address of the second server back to 10308 it show up in the master server list.

 

I have tested that port 10307 is open from outside my network using http://portchecker.co/check.

 

I am able to connect directly to the second server by entering the local ip address (i.e. 192.168.0.75:10307), but receive a "CONNECTION INTERRUPTED" message when I attempt to connect by IP using the public ip 71.205.138.151:10307.

 

Attached is the network.cfg file from the second server.

 

Seems simple, but I must be something. I would appreciate any help. Thanks.

 

TWC_Alamo

network.cfg

[TWC_Alamo]

Just to update my own post. Turns out both servers do show up in the master service list when viewed from the internet, but for some reason when the master list is viewed from a client inside my LAN only the server assigned to port # 10308 is in the list.

 

So, can anyone tell me how to make servers assigned to some port # other than 10308 appear in the master list when viewed from inside the LAN? It not a big deal, since I can connect to the IP address, but I would still like to figure this out for my own edification.

 

Also is there a reference that explains the parameters and setting that can be included in the network.cfg file?

 

Thanks

 

Alamo

[Merlin-27]

Alamo,

There was a time where I was hosting two public servers on my LAN. I never could see both within the LAN either (same scenario) but it never bothered me much so I never really tried to figure out why.

[TWC_Alamo]

In searching for a solution, I found reference in a post about including a line in the NETWORK.CFG that put an asterisk "*" in the server address line, but I can't find it.

 

Does anyone know of a reference that explains the possible contents of the NETWORK.CFG?

[c0ff]

Just to update my own post. Turns out both servers do show up in the master service list when viewed from the internet, but for some reason when the master list is viewed from a client inside my LAN only the server assigned to port # 10308 is in the list.

 

Huh, you've hit a bug: servers with share the same IP as the client are filtered from the master server list and are taken from the direct LAN probing.

However, only the default port is probed on LAN.

That's why your 'non-standard' server does not appear in the list.

You still can connect to it directly by using "Connect by IP" button.

By the way, you can use host names in IP address string. Like hostname:port.

 

Looks like filtering should take port into account to fix this issue.

Edited July 8, 2015 by c0ff
reworded