Windows Server, multiple instances, port conflicts? Can't connect to non 26900 ports

[hocbeelzebub]

I have a windows machine that I configured with two separate 7daystodie dedicated server instances. They have their own directories/files; the server config file was edited for the second ded server. I can connect to them fine over a local network, but not over the internet. I have one server setup for port 26900 and the other for 26915. I have port forwarding rules as follows: TCP: 26900-26905 , TCP: 26915, UDP 26900-26903. When I try to connect over the internet to the Ded Server on port 26915 from a pc I have access through remotely, my routers log shows it trying to access through both 26915 and 26900. The other ded server is on port 26900, so there must be a conflict. Is there any way to only have the server receive requests on 26915 and not also 26900?

Thanks for all your help!

The reason why I'm having two ded servers is because when I play with my wife, she wants the vanilla experience, and when I play with friends, mods are fun. Also, different difficulty levels. 

[hocbeelzebub]

ok, I figured out how to get it to work. I had previous tried port 26905 and had the same issue. I tried port 26901 and it works. One server is on 26900 and the second is on 26901. Both connect no problems now. Hopefully this helps anyone in the future after a forum search for multiple dedicated server instances.

[SylenThunder]

Considering you need a minimum spacing of 4 between the servers, I'm not sure how you got it to work.

 

The closest you should have those is the first server on 26900 and the second server on 26905.

 

As such, your forwarding should be as follows...

TCP 26900

UDP 26900-26903

TCP 26905

UDP 26905-26908