Server Port Changes
by Dave Young · in Torque Game Engine · 10/17/2008 (5:53 am) · 0 replies
We've run into an odd thing and I wanted to see if anyone has seen this yet before we spend more time on it.
On a Vista Box (running with IPv6 which is the default) a dedicated server tries to bind to a specific port, (like 28000), but the master server sees it as a seemingly random port (like 20586). No console errors, and no one can connect to it, including the master server when it tries to verify the server and port are still running/open.
So the server disappears off the master server list after its first couple of queries. No one can connect to the server either on the random port# or on the port it is supposed to be binding on, 28000.
This isn't my area of expertise, but it feels like there is some kind of port translation going on at the router level or something. The inability to connect on either port also seems like the ports aren't being forwarded to the server properly. But the random port # is troublesome, any insights?
A few other Vista machines can host and run the server just fine.
On a Vista Box (running with IPv6 which is the default) a dedicated server tries to bind to a specific port, (like 28000), but the master server sees it as a seemingly random port (like 20586). No console errors, and no one can connect to it, including the master server when it tries to verify the server and port are still running/open.
So the server disappears off the master server list after its first couple of queries. No one can connect to the server either on the random port# or on the port it is supposed to be binding on, 28000.
This isn't my area of expertise, but it feels like there is some kind of port translation going on at the router level or something. The inability to connect on either port also seems like the ports aren't being forwarded to the server properly. But the random port # is troublesome, any insights?
A few other Vista machines can host and run the server just fine.
