03-15-2009, 03:58 PM
Hi all!
I've run into an issue that is beyond anything I have seen before...
I have been running a small dedicated server from home for friends over the internet. It has been running on ubuntu, and all the ports have worked fine at IP:27015. Today, I restaged that box to Windows Server 2003.
The machine is using the same internal static IP of 192.168.1.101.
I loaded the server, and all was going OK. However, even though I blatantly specify port 27015, there is an issue...
It is forwarded correctly. People can actually telnet to IP:27015 and get connected properly. However, their game clients can NOT connect...
Oddly enough, someone took the time to 'search' the master list, only to actually find my server apparently available on IP:49770.
I have no idea what port 49770 is. In fact, it isn't even open... my router is not forwarding that port. However, the game client can connect just fine. It even works if they type "connect IP:49770" in console. However, they can NOT telnet directly to that port. (I don't have it forwarded!)
At first I thought, "maybe my ISP is translating the 27015 port now to stop server traffic", but then realized that isn't the case, since people can STILL CONNECT properly if they do a direct telnet to 27015.
I tried switching the port to 27016 instead. This time, it worked right! Players could actually connect to IP:27016.
Switched it back to 27015, and same thing... showed up with 49770. What the heck?
The last thing i tried was putting the box into the DMZ. With this configuration, 27015 appears to work properly. It isn't 'remapped' to 49770.
Very, very, very weird.
My guesses are that:
1) Windows 2003 Server is doing some sort of dynamic NAT translation
2) My router is doing some sort of dynamic NAT translation
3) Something is getting goofed up at the steam master servers, and they are recording and translating the server:port incorrectly.
#1 seems incorrect to me, because if translation occurred on the box, then the port would have to be forwarded, and it isn't.
Before you ask, I have tried all combinations of +ip and +port you can imagine.
Guys, I'm really out of ideas on this one. What are these steam master servers doing to my poor port number? And why does it only seem to affect 27015? Please, I don't want to leave this in the DMZ!
Thanks!
I've run into an issue that is beyond anything I have seen before...
I have been running a small dedicated server from home for friends over the internet. It has been running on ubuntu, and all the ports have worked fine at IP:27015. Today, I restaged that box to Windows Server 2003.
The machine is using the same internal static IP of 192.168.1.101.
I loaded the server, and all was going OK. However, even though I blatantly specify port 27015, there is an issue...
It is forwarded correctly. People can actually telnet to IP:27015 and get connected properly. However, their game clients can NOT connect...
Oddly enough, someone took the time to 'search' the master list, only to actually find my server apparently available on IP:49770.
I have no idea what port 49770 is. In fact, it isn't even open... my router is not forwarding that port. However, the game client can connect just fine. It even works if they type "connect IP:49770" in console. However, they can NOT telnet directly to that port. (I don't have it forwarded!)
At first I thought, "maybe my ISP is translating the 27015 port now to stop server traffic", but then realized that isn't the case, since people can STILL CONNECT properly if they do a direct telnet to 27015.
I tried switching the port to 27016 instead. This time, it worked right! Players could actually connect to IP:27016.
Switched it back to 27015, and same thing... showed up with 49770. What the heck?
The last thing i tried was putting the box into the DMZ. With this configuration, 27015 appears to work properly. It isn't 'remapped' to 49770.
Very, very, very weird.
My guesses are that:
1) Windows 2003 Server is doing some sort of dynamic NAT translation
2) My router is doing some sort of dynamic NAT translation
3) Something is getting goofed up at the steam master servers, and they are recording and translating the server:port incorrectly.
#1 seems incorrect to me, because if translation occurred on the box, then the port would have to be forwarded, and it isn't.
Before you ask, I have tried all combinations of +ip and +port you can imagine.
Guys, I'm really out of ideas on this one. What are these steam master servers doing to my poor port number? And why does it only seem to affect 27015? Please, I don't want to leave this in the DMZ!
Thanks!
![[Image: b_350x20_C002748-004880-FFFFFF-000000.png]](http://cache.www.gametracker.com/server_info/173.58.194.29:27015/b_350x20_C002748-004880-FFFFFF-000000.png)
![[Image: 76561197965445574.png]](http://badges.steamprofile.com/profile/simple/steam/76561197965445574.png)