Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[snake3scape]

I've had this router for a few months after my last one died and I'm now completely unable to port forward. I follow all the steps to port forward but alas the port is still closed every single time. I've tried a few fixes in the past including disabling UPnP, using those auto port forwarding programs, and creating an exception for the port in my fire wall. Nothing has worked!

Here's a screenshot of my port set-up:

http://i.imgur.com/gvRybc0.png

I'm sure a lot more process and screenshots will be needed and I'll be happy to go through these things. Thanks in advance for anyone who helps me!

[FurryNutz]

Link>Welcome!
What Hardware version is your router? Look at sticker under router.
Link>What Firmware version is currently loaded? Found on routers web page under status.
What region are you located?
Are you wired or wireless connected to the router?
Has a Factory Reset been performed?

What ISP Service do you have? Cable or DSL?
What ISP Modem make and model do you have?
If this modem has a built in router, it's best to bridge the modem. Having 2 routers on the same line can cause connection problems.
Double NAT
To tell if the modem is bridged or not, look at the routers web page, Status/Device Info/Wan Section, if there is a 192.168.0.# address in the WAN IP address field, then the modem is not bridged.
If the modem can't be bridged then see if the modem has a DMZ option and input the IP address the router gets from the modem and put that into the modems DMZ.

Some things to try: - Log into the routers web page at 192.168.0.1. Use IE, Opera or FF to manage the router.
Turn off ALL QoS or Disable Traffic Shaping (DIR only) GameFuel (DGL only and if ON.) options. Advanced/QoS or Gamefuel.
Turn off Advanced DNS Services if you have this option under Setup/Internet/Manual.
Turn on DNS Relay under Setup/Networking.
Setup DHCP reserved IP addresses for all devices ON the router. Setup/Networking. This ensures each devices gets its own IP address when turned on and connected, eliminates IP address conflicts and helps in troubleshooting.
Ensure devices are set to auto obtain an IP address.
Set Firewall settings to Endpoint Independent for TCP and UDP under Advanced/Firewall.
Enable uPnP and Multi-cast Streaming under Advanced/Networking. Disable uPnP for testing Port Forwarding rules.
WAN Port Speed set to Auto or specific speed? Some newer ISP modems support 1000Mb so manually setting to Gb speeds can be supported by the router. Advanced/Advanced Networking/WAN Port Speed
Set Time and Time Zone under Tools/Time.

[Hard Harry]

Well first open server.properties and see if the port is set to that. Also what are you using to determine if ports are open?

[snake3scape]

Thanks for the help!

I am using Hardware Version B1. The firmware I have on right now is 2.07NA, which I believe is the most updated. I am located in the Midwest region of the United States. I am on wireless connection to my router, all my computers in my house are on a wireless connection. No factory reset has been preformed yet.

I use Comcast Cable as my ISP where I live. I'll have to check back and give you my ISP Modem make and model when I have more time. There is no problem with my modem being not bridged, however, as there was no 192.168.0.# in the WAN IP address field.

Ok so after doing all of your steps the port is of course still closed. I did have a few things to bring up however. One was minor which is that ever since I switched routers I have not been able to connect to my router with 192.168.0.1, but instead with 192.168.100.1. That's probably just from a firmware/hardware update I'm guessing. Other than that I didn't touch anything with the WAN Port Speed because I was guessing it wasn't really needed in this situation.

Thanks for the help! Please reply back with anything more you need, and I'll also have the ISP modem info soon.

To Hard Harry: I am using simple sites like http://www.yougetsignal.com to check if a port is open, which I thought was pretty standard for checking for an open port. I've also made sure many of times that my ports were set right in server.properties, there is no problem there.

[FurryNutz]

You do need to be actively using the port before testing to check the port status. Just configuring the port on the router doesn't mean it's open. Only when it's actively being used should the port status be revealed.

[snake3scape]

I booted up my Minecraft server using port 25565 and the port is still closed, and I still cannot reach the server. No problems there.

[FurryNutz]

Have you tried setting up Virtual Server?

[snake3scape]

No I haven't. Any tutorials on how to do this that you could point me to?

I do add, however, that this is not only for the my minecraft server, but also for another program that uses that port 1336. If a virtual server could help me get ports open for both those that would be great.

[Hard Harry]

Hmm,  that 192.168.100.1 gateway could be a issue, because thats the default (although transparent) gateway for your modem.

Second, can you access the server from your LAN (a different computer) using the 192 IP? That will isolate problem.

Third, if on LAN works, try putting the IP of the PC with the Server on it into the DMZ (Under Advanced > Firewall Settings). That will isolate if the firewall is just blocking it before it can be forwarded.

[snake3scape]

None of my computers are able to reach the server using the 192.168.0.1 address. When I try to go to that it seems to try to connect for 20-25 seconds, but then gives me a page from the browser that says it was unable to reach the site. This is for all the computers. They are reaching the 192.168.100.1 very quickly though.

I wasn't sure which IP you meant by the '192 IP'. Like I said, all the computers can reach the 192.168.100.1, but none of them can reach the 192.168.0.1. Should I still put my computer into DMZ?

Edit: Just put my server PC into DMZ and ran an mc server. Still the server is not connectable and the port is not open.

[Hard Harry]

Ok, well that rules out the router firewall. We need to rule out PC issues (client config, PC firewall, etc). So from another PC on your network (besides one running the Minecraft server) try playing off your server by entering the IP address (192.168.100.x) of your computer running the server.

Also, happen to get your modem's model number yet?

[snake3scape]

Well to go specifically with minecraft the only way I can enter my server on the computer I'm hosting is through my IPv4 Address, which is 192.168.56.1 for that computer. I tried that same IP on a different computer and it did not connect. Not sure if that is odd or not again, as my other computer has the IPv4 Address of 192.168.100.102. It seems weird their address's would be so different, but maybe that's how it's suppose to be.

My modem's model is a Motorola SB5120 SURFboard.

[Hard Harry]

Theres your problem. The two computers are on different subnets. If you can't connect from from computer A on your network to computer B, it has nothing to do with forwarding. Atleast not directly.

 I think your missing something. Go over your network again? Connect computer A and B to DIR-825. As long as there both set to DHCP, they should both get a similar IP. By similar, I mean atleast 3 of the octets (IE 192.168.56.x) should match. If not, then maybe there is a DHCP reservation set incorrectly?

Until you can get the server to work on your own network, there is no hope of getting it to work outside of your network.

[snake3scape]

If I did get these computers connected would I be able to port forward again?

I think now its got something to with me somehow having multiple wifi networks. No idea how that happened but I'll work on getting the server computer connected to the main network.

[Hard Harry]

Yes. Think of ISP to You as A, from your modem to your routers WAN as B, from your routers WAN to your routers LAN as C, and your Router's LAN to your computer as D. Finally software issues may occur (bad server.con file, AV Firewall, etc) between your LAN and your actual server as E. So we need to get up to C first, which means we need it working on your LAN. And then we can forward the ports from C to B and the rest will flow out to A.

By the way, what was the last update? I used to play alot but haven't since...about the wolfs patch? Anything interesting added since then?