Sign in with
Sign up | Sign in
Your question
Solved

Port forwarding w/Belkin and Win 7 for game server

Last response: in Networking
Share
January 20, 2014 3:12:06 AM

goal in a nutshell: I'm attempting to help someone (online) to forward a port so they can run a game server.

On the game side of things, I also run a server for this game on my machine (XP Pro with a Linksys E2000), and they can connect to me fine. I mention this to help eliminate questions about problems with the server setup or game itself as we seem to have that process down ok.

The key differences between our setups is they run Win 7, and have a Belkin router (F5D8236-4v3) - both of which I'm not familiar with other than what I've learned over the past couple of days. It could be either, but I suspect the Router settings to be the issue...but Im guessing.

I've been using this page as a visual guide to see what they're looking at as we go; http://screenshots.portforward.com/routers/Belkin/F5D82... , as well as screencaps from them.

The game is called 'Starbound'; http://starbounder.org/Guide:Setting_Up_Multiplayer.


Some of the steps taken so far;

-set up game server essentially as I did on my machine (different in name only)

-set a static IP for their system

-accessed router via browser to open port 21025 (TCP) on their 'virtual servers' page (http://screenshots.portforward.com/routers/Belkin/F5D82...)

-uninstalled temp version of Norton (which had apparently been controlling firewall)

-set a new rule for the port in Window's firewall (which didn't let me in so...)

-disabled Windows firewall

-disabled router's firewall

-tried changing connection type in router to 'static' (http://screenshots.portforward.com/routers/Belkin/F5D82...) - default was dynamic


At this point, they can now run the server successfully, and connect to it via their local machine. Using Portforward's port checker tool as well as online sources, their port still shows as closed though, and no one else can connect. According to the server log, I don't even ping their machine - it's as if no attempt has been made (e.g., if it were a password issue, etc. it would show that I had tried and failed to connect).

So, something is still blocking access and giving at least the appearance of a closed port. There must be some additional steps either with Win 7 or their Belkin router that I'm unaware of, since these steps worked on my machine. It may well be security setting on the router, which I'm not familiar with (my default setting worked find so I never messed with those). Any suggestions would be appreciated! Thx

Best solution

January 20, 2014 8:44:18 AM

splittingeve said:
goal in a nutshell: I'm attempting to help someone (online) to forward a port so they can run a game server.

On the game side of things, I also run a server for this game on my machine (XP Pro with a Linksys E2000), and they can connect to me fine. I mention this to help eliminate questions about problems with the server setup or game itself as we seem to have that process down ok.

The key differences between our setups is they run Win 7, and have a Belkin router (F5D8236-4v3) - both of which I'm not familiar with other than what I've learned over the past couple of days. It could be either, but I suspect the Router settings to be the issue...but Im guessing.

I've been using this page as a visual guide to see what they're looking at as we go; http://screenshots.portforward.com/routers/Belkin/F5D82... , as well as screencaps from them.

The game is called 'Starbound'; http://starbounder.org/Guide:Setting_Up_Multiplayer.


Some of the steps taken so far;

-set up game server essentially as I did on my machine (different in name only)

-set a static IP for their system

-accessed router via browser to open port 21025 (TCP) on their 'virtual servers' page (http://screenshots.portforward.com/routers/Belkin/F5D82...)

-uninstalled temp version of Norton (which had apparently been controlling firewall)

-set a new rule for the port in Window's firewall (which didn't let me in so...)

-disabled Windows firewall

-disabled router's firewall

-tried changing connection type in router to 'static' (http://screenshots.portforward.com/routers/Belkin/F5D82...) - default was dynamic


At this point, they can now run the server successfully, and connect to it via their local machine. Using Portforward's port checker tool as well as online sources, their port still shows as closed though, and no one else can connect. According to the server log, I don't even ping their machine - it's as if no attempt has been made (e.g., if it were a password issue, etc. it would show that I had tried and failed to connect).

So, something is still blocking access and giving at least the appearance of a closed port. There must be some additional steps either with Win 7 or their Belkin router that I'm unaware of, since these steps worked on my machine. It may well be security setting on the router, which I'm not familiar with (my default setting worked find so I never messed with those). Any suggestions would be appreciated! Thx


Wow that router doesnt seem to clear but heres a few tips:

1. The page you are setting the static ip on seems to be his internet connection not his PC, Normally you would have to request a static IP from your ISP, If he doesnt have one id change this back. You can get round this using dynamic DNS, (dyndns.org) registering with this service will map a URL to his ip that stays the same so people can use it to connect to his server. Ignore this for now though it just over complicated things, just make sure you have his current IP when testing. he can get his web facing IP from whatismyip.com. it will probably be in the router also.

2.If you want to set a static IP for his PC it will probably be in that "DHCP Client list" option. it needs to match his mac to the same ip every time. Make sure any port forwarding rules you set up already match this IP.

3.Check the port forwarding rules are actually enabled, its often a 2 stage process, you have to create the rules then turn them on. I noticed there is an enable check box in the screen shot.

4.Check the security logs on the router, are they showing your connection being blocked? if not are you able to turn the level of logging up?

5. A trick you can use to check the port is open from your side is to type "telnet [ipaddress]:21025" at command prompt. if it says it cant connect its not open, but if the command prompt hangs at a flashing cursor its open.

6.Its not a good idea for the long term solution but for testing you can add his PC to the DMZ, this basically puts his pc outside of the firewall, which means its vulnerable to attack directly from the internet but will allow you to test and see if the router firewall is the issue, though to be fair the logs should tell you if it is.


Finally I dont want to sound patronising, you've got this far so i'm assuming you are aware you need to be connecting to his web facing IP, which is different to the LAN IP of his PC, because of NAT, and this is why we need the port forwarding.
Share
January 20, 2014 2:09:31 PM

Urumiko said:
Wow that router doesnt seem to clear but heres a few tips:..


No, I think I officially hate Belkin. Heh. My Linksys seemed much more straight forward.



Urumiko said:
1. The page you are setting the static ip on seems to be his internet connection not his PC,...


Sorry, in an attempt to include a lot of info, I didn't make that part very clear. Initially, we actually set a static IP via his network connections in Win 7. That was sufficient on my machine (although it's XP), but not his apparently. That setting in the router doesn't appear in my Linksys, so we gave it a shot.

I figured was probably a long shot - it was I believe the last thing we tried, simply becasue we were out of ideas. Anyway, I'll no doubt go ahead and set that back to defaults. Good catch on your part.



Urumiko said:
2.If you want to set a static IP for his PC it will probably be in that "DHCP Client list" option. it needs to match his mac to the same ip every time. Make sure any port forwarding rules you set up already match this IP.


Yes, I'll have to determine if this is required with his Belkin - it does seem a lot more confusing. On the Linksys, you simply enter the static IP you created in network connections, into the same form that you enter the ports to open, and you're done.



Urumiko said:
3.Check the port forwarding rules are actually enabled, its often a 2 stage process, you have to create the rules then turn them on. I noticed there is an enable check box in the screen shot.


Will do. I def have to get a better look at the software for Belkin, there is a lot there. I'll double check that.



Urumiko said:
4.Check the security logs on the router, are they showing your connection being blocked? if not are you able to turn the level of logging up?


My suspicion, guess-related as it is, is that it does have to do with the router's security settings, the type, etc. I will look deeper into this section and get him to investigate the logs.



Urumiko said:
5. A trick you can use to check the port is open from your side is to type "telnet [ipaddress]:21025" at command prompt. if it says it cant connect its not open, but if the command prompt hangs at a flashing cursor its open.


Thanks! I need all the tricks I can gather. It was a brutal evening with little results.


Urumiko said:
6.Its not a good idea for the long term solution but for testing you can add his PC to the DMZ, this basically puts his pc outside of the firewall, which means its vulnerable to attack directly from the internet but will allow you to test and see if the router firewall is the issue, though to be fair the logs should tell you if it is.


I only knew of this vaguely, and will give it a go for the sake of a test for sure. Thx.


Urumiko said:
Finally I dont want to sound patronising, you've got this far so i'm assuming you are aware you need to be connecting to his web facing IP, which is different to the LAN IP of his PC, because of NAT, and this is why we need the port forwarding.


No, quite alright. Any advice is taken gratefully here. I'm rather new to at least some of this, and am learning by the seat of my pants. But yes, we're good on that front. Thanks for all of the suggestions. He and I don't connect again until at least tomorrow (I'm just on an info gathering hunt) - but I'll report back with any new info. Thx again.
m
0
l
Related resources
January 20, 2014 5:04:17 PM

Cool. Let me know how u get on
m
0
l
January 22, 2014 3:14:45 AM

Urumiko said:
Cool. Let me know how u get on


Just FYI, can't get back with him 'till the weekend, but will return with some results then. Thx
m
0
l
!