CheckEmoji Community · the emoji forum
🏠 Home 🆕 What's new ❓ Unanswered 🔥 Popular 📡 RSS Members 👥 0 online log in · register
Home › IT › IT Support › Trouble with port forwarding

Trouble with port forwarding

Started by lonedriver99 · · 👁 4 views · 1 reply

📡 Subscribe to replies

Participants lonedriver99
lonedriver99 lonedriver99 NewcomerOP
2 messages
joined Jan 2018
#1 ·
Hey everyone! I actually already posted this over in the bug report thread, but I figured I’d try my luck here too. So, I’m currently wrestling with some port forwarding settings on my Netgear Nighthawk from AT&T, and honestly—it just isn't going my way.
Everything is running perfectly fine on my local machine—I've got an Apache server spinning up without any issues—but the second I try to access the site from outside my local network (you know, via the actual internet), everything hits a wall.

In the router's configuration under "Port forwarding," I’ve set up three specific ports: 80, 443, and 8000. You can see exactly how I laid it out here: image http://tinypic.com/r/15z5g6o/9
The weird part? When I head over to Speedtest.net to check things, it reports port 80 as being open, but the other two are showing up as blocked. And that's despite the fact that all three ports are configured identically!

To make matters even more interesting—and slightly maddening—whenever I try to reach the site through that "open" port 80, I don't see the Apache welcome screen at all... instead, I get redirected straight to the Netgear Nighthawk login page!? It's like the router is hijacking the request.

Has anyone else run into a headache like this, or does anyone have a bright idea on what I might be missing? Please let me know if you have any insights. 🙂

Thanks so much in advance!
lonedriver99 lonedriver99 NewcomerOP
2 messages
joined Jan 2018
#2 ·
I actually stumbled upon the exact issue we've been discussing over on another forum:http://forum.pcekspert.com/showthread.php?t=270478

To give you the short version—it looks like the router (or perhaps the firewall settings?) is blocking access whenever you try to connect via a public IP address while you're actually sitting on the same local network. Isn't that just one of those classic networking quirks?

Essentially, everything functions perfectly fine if you're connecting from a device that sits outside the local network.

You must log in or register to reply here.

Log in Register

🔗 Similar threads