Server Interface Setting is LAN IP, not WAN IP

[Jeff Holmes]

Have been trying to setup a server for everyone to enjoy but have run into an issue where the Interface (IP) is my local area IP, 192.168.5.xxx. I have forwarded the port to the server and have the server with a fixed LAN IP. The server shows up on the list of active servers but has the LAN IP which is useless and I can not for the life of me figure out why this is happening. From what I have read in the forums if the ports are opened and forwarded then the WAN IP should show. Not the case right now so if any one has some ideas I would greatly appreciate it. Thanks - Jeff

[Panzertard]

Router NAT / port forwarding.

Your server: 192.168.5.xxx.

 

On the router, add the host.

Add which PORT you want to forward, (probably 10308 in this case) and the IP of the inside reciever. Which is 192.168.5.xxx.

Make sure you forward both TCP & UDP.

I've seen one more case where I had to forward 10309 as well - in the same manner.

 

When you start the MP server, it should list 192.168.5.xxx as the active interface - no changes requires on the MP server.

The router will now manage the translation between the inside and the outside.

 

On the MP server, you may want to check the local firewall(s), Windows Advanced firewall and any 3'rd party antivirus/firewall system you have installed.

They need to allow 10308 (and possibly 10309) - both TCP+UDP for the DCS.exe / simulator.exe (depending on your MP product).

 

And thats about it.

[Jeff Holmes]

Thanks for the info, I made sure that port forwarding was enabled and working by going through the firewall from another client and that the PC firewall had the exception also. (Own two licenses). After some time I noticed that the Multiplayer server list changed my IP from 192.168 to the 24.156 router IP. Guess I just had to give it some time but I was also expecting that the Server setup would show my external IP when I was setting it up and not my LAN IP. Thanks again for the reply and I will continue to watch how this works.

[Jeff Holmes]

Ran another quick test, worked perfectly fine. When setting up the server the IP was listed as 192.168 but on the master server listing the IP is my external router IP. Perfect, so all is working just fine. I was just expecting a different behavior from the UI, go figure.... :thumbup:

[c0ff]

I was just expecting a different behavior from the UI, go figure.... :thumbup:

Good point.