NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
DDNS & Port Forwarding from within network doesn't work
So I have port forwarding of port 80 setup on my router to forward to a computer on my network. I've also setup DDNS to easily hit this webserver from outside of my network. I'm trying to host a basic web server as an experiment and ran into a bizarre issue.
When accessing the DDNS url or my public IP directly from within my Wi-Fi network, the page just spins and loads before timing out after a long while. If I get off my home network and hotspot my computer using my mobile hotspot I can connect to the DDNS url and public IP immediately.
Is there some setting that I'm missing in the NETGEAR admin that should allow this port to be accessed from within the network itself?
So I've gotten my issue resolved. It seems I was running a previous firmware (3.2.16.6). I've updated to 3.2.16.22 (released mid-November). Now I can access my server from within the network by public IP, DDNS url, and private IP.
10 Replies
The web page loads fine when addressed with the LAN IP address, correct?
It's just a guess, but the DDNS is resolving to the publici IP of the Orbi and it probably does not respond to connection attempts from inside the network.
Do you mean by the private IP? My server is at 192.168.1.11:80 and I am unable to get that to load in a web browser. It just seems to timeout after about a minute.
jaron-lowe wrote:Do you mean by the private IP? My server is at 192.168.1.11:80 and I am unable to get that to load in a web browser. It just seems to timeout after about a minute.
Oh, my. A computer with IP 192.168.1.x cannot access a web server at 192.168.1.11:80?
Yet, it CAN be reached from the internet?
