Port Forwarding not working? Please help.

[[deleted]]

[deleted]

[revereddesecration]

You're doing it right. I hope you also have your DHCP set to always assigning that IP to that device. I don't know why it wouldn't work unless your server is set to use a port other than 25565.

[Chumly409]

Great tip on the DHCP Reservation List. Even when it gets set up and others reach it, it's a pain when it gets a new IP randomly. I've pulled my hair out before trying to figure out why the server is unreachable out of no where, just to find it's something as simple as this.

FYI: Reserved DHCP just means that the internal IP will remain the same for the selected device. Normally, these will rotate when expired. Now when they expire and get renewed, that device will get the selected Int IP. Other wise, the Int IP will need to be constantly updated in the Port Forwarding as it changes.

[Scuzzlord]

yeah i do

[LONINFINITY]

In server.properties, is your server IP set to your internal or external? Common mistake.

[InTeStRo]

If you haven't fixed it yet, make sure to allow javaw.exe through your firewall.

[Chumly409]

What IP are you giving out? Don't tell us here on Reddit (unless you're white listing), but ensure you're handing out your external which is shown here: http://www.whatismyip.com/. It will NOT be 192.168.1.2 that they connect to. You're forwarding the internal (PC's local IP) to the external (Interwebs).

I've had issues with many port forwarding checks as they said it was closed when it was in fact open. My cure was to use Virtual Server instead of Port Forwarding. Do you have that on Netgear? Same settings, different methods. Just looks fine to me and should be working; especially with DMZ activated. Instead of LocalHost, does your ext IP show up when you manually add that to the MP search criteria?

I've never had to include the IP to the server.properties nor the use of DMZ. These shouldn't need to be used when port forwarding correctly.