NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
HTTP access and Port Forwarding
I couldn't get port forwarding to work at all, well it seemed. I thought i had all the settings right, and http access worked from inside the network, just not from outside. Normal File sharing and ...
-on FTP, you DON"T want to set the masquerade to your local lan IP (static or otherwise). Either set it to your dyns name, or leave it out. FileZilla is ok either way (and I think many other clients are also).
-If you want secure HTTP, then don't forward port 80. Instead forward the alternative https port (settable via Frontview on sparc and x86 platforms). You may need to specify this port in the URL (e.g., https://dydnsname:port/
-domain server should certainly be blank if you don't have your own domain server.
-often your DNS address is the same as your gateway address. Not all routers proxy DNS (some simply pass through the ISP DNS servers), but many do.
-on static IP generally, IMHO it is better to use address reservation if your router supports it. In that case, you would use the normal DHCP configuration in the NAS.
-If you want secure HTTP, then don't forward port 80. Instead forward the alternative https port (settable via Frontview on sparc and x86 platforms). You may need to specify this port in the URL (e.g., https://dydnsname:port/
-domain server should certainly be blank if you don't have your own domain server.
-often your DNS address is the same as your gateway address. Not all routers proxy DNS (some simply pass through the ISP DNS servers), but many do.
-on static IP generally, IMHO it is better to use address reservation if your router supports it. In that case, you would use the normal DHCP configuration in the NAS.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
