NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
BR200 can't forward a port no matter what I try :(
Hi, first post although I've been all over the web (including here) to try to figure out what is going wrong. I'm not any sort of "pro" when it comes to networking, but, I bought this BR200: 1) t...
Hmmm, yes ... there was something. Give me a minute please.
Found it. The current BR200 Firmware Version 5.10.0.5 (also the one for the BR500, and some minor versions before) says this:
===
Known Issues:
...
NAT loopback does not work in this release. NAT loopback is useful for accessing internal resources by public domain name.
Workarounds: Use one of these workarounds:- Change device hosts file to map public domain name to local IP when working on the same subnet as a public server.
- Use a separate DNS server that can handle accessing public resources from an internal network.
Downgrade to a previous released firmware with NAT loopback support.
===
Scratch the last suggested workaround, this applies to the BR500 only.
Sorry, I'm compereably "new" back on the BR500/BR200 8-)
Thank you for your reply! To answer your questions.
Does the BR200 WAN/Internet address as shown on the Dashboard match to the "Google what is my IP address"?
Yes, this is confirmed the same.
If not, there is another NAT router in front, either as part of your connection, or in the form of the ISP CPE WiFi router?
No, the BR200 is connected directly via ethernet right into FiOS ONT.
Almost forgot: How are you testing the port forwarding: From the wild Internet, or from the LAN(x) via NAT loopback?
Actually, no, I always test via a PC or phone on my LAN. Does this not work with this router?
Thank you for your help!
Hmmm, yes ... there was something. Give me a minute please.
Found it. The current BR200 Firmware Version 5.10.0.5 (also the one for the BR500, and some minor versions before) says this:
===
Known Issues:
...
NAT loopback does not work in this release. NAT loopback is useful for accessing internal resources by public domain name.
Workarounds: Use one of these workarounds:
- Change device hosts file to map public domain name to local IP when working on the same subnet as a public server.
- Use a separate DNS server that can handle accessing public resources from an internal network.
Downgrade to a previous released firmware with NAT loopback support.
===
Scratch the last suggested workaround, this applies to the BR500 only.
Sorry, I'm compereably "new" back on the BR500/BR200 8-)
- Wow, that was it!
I didn't even know this was a thing (NAT loopback). Hopefully they will enable this in a future release so it isn't necessary to have to keep reconfiguring the app accessing these devices to use different IP addresses whether I'm on my local network or not. But I'm glad I can access them at all.
Thank you so much for your help!
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
