NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
Port forwarding on R7000 stopped working
I have a nighthawk R7000 with firmware version V1.0.9.88_10.2.88. I have multiple ports setup for forwarding and it was working just fine until a few days ago. Suddenly I couldn't access anyhting ins...
> [...] The WAN listed in the router and my public IP are not identical.
> [...]That would do it. (It's "1" on the list for a reason.) Plug that
address into the form at "https://whois.arin.net/", and get discouraged.> [...] I did notice that the IP for my public IP changed recently [...]
Apparently your ISP moved you onto a CGN router.
> [...] cannot reach the inside of my network using my new public IP.
With another NAT router in the way, that's not amazing.
You could try asking your ISP if you can get (back to having) a
public address (again). They might charge extra for that, if they'll do
it at all. Some ISPs dislike servers for residential customers.
Thank you for the informative reply,
I will try going down a firmware version. I had originally been on a version actually higher than my current one and went down a version to test although I can't remember what version that was and I can't locate it on the website. (Was 1.0.10.something).
I usually get something akin to "site took too long to respond." or "ERR_CONNECTION_TIMED_OUT" for my webpage.
I assigned the IPs in the router itself so they're reserved for those machines at all times.
I specify which IP by using either my domain (which uses my public IP) or my public IP found when I google "What's my IP"
I can access any of these services from within the network and using the WAN IP.
Thanks for the tip for the external to internal port change to strengthen the network some.
**Edit** Went down to that version and still no dice
> I will try going down a firmware version. [...]
Or three.
> [...] (Was 1.0.10.something).
V1.0.10.90_10.2.90 apparently was posted and then pulled within a day
or so. Must have been exceptionally bad. (And normally bad is bad
enough to dissatisfy almost everyone.)
Tried going down in versions and it's rejecting some of the older firmware versions. Pretty much anything past v1.0.9.42 and it ain't having it. Gives "error code -2".
Also it appears the thing that changed was I accidentally left on the auto update function and it went to whatever the most up to date firmware was and killed a bunch of settings. Can't seem to undo the damage it did though. Going to try a factory reset now that I'm on 1.0.9.42.
> [...] Going to try a factory reset now that I'm on 1.0.9.42.
I'd try that settings reset. Just don't try to restore saved
settings from a newer version. I'd expect ".42" to be old enough to
work.> [...] Does the IP address of the WAN/Internet interface on the router
> (still?) agree with that outside-world address?> I assume that you can contact the servers, from a system on your LAN,
> at their LAN IP addresses. Can you also contact the servers, from a
> system on your LAN, at the router's WAN/Internet IP address? That test
> relies on "NAT loopback" (on the router) working, which it should be.Don't get fixated on the firmware without checking the other
possibilities.Still no dice. I can access the services from my WAN IP. The WAN listed in the router and my public IP are not identical. It's odd that this suddenly became an issue as I was able to host things up until recently. I did notice that the IP for my public IP changed recently too but I updated my DNS accordingly and also cannot reach the inside of my network using my new public IP.