NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
jaron-lowe
Dec 15, 2020Aspirant
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 basi...
- Dec 15, 2020
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.
jaron-lowe
Dec 15, 2020Aspirant
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.
CrimpOn
Dec 15, 2020Guru - Experienced User
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?
- jaron-loweDec 15, 2020Aspirant
Yeah that's my whole issue. It's very bizarre and only forwards the traffic when on an external network. From within my network, It just spins and spins away. Seems to be only an issue with port 80 too. I've got port forwarding setup for RDP & Plex and both are having no issues internally or externally.
- CrimpOnDec 15, 2020Guru - Experienced User
Is this web server on a Windows machine? Windows Firewall has separate rules for "public" and "local" networks.
- jaron-loweDec 15, 2020Aspirant
It is a Windows machine, yes. I've got the network set to private with network discovery turned on. Any setting you would recommend me setting?