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.
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.
> [...] 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.
Yep that'll do it. I'm going to call their offices in the morning when they open but being in an apartment complex (even though I have an individual line) and not owning the account might make things hairy. Thanks for all the help and I'll see to getting this resolved through my ISP!
> [...] see if they'll let me have a static IP [...]
What you really need is "public", not "static", although both
"public" and "static" would let you get a real domain instead of using
DDNS.I'm curious how your ISP responded. This started happening to me yesterday at Comcast. I will check for the WAN IP mismatch when I get home, but everything sounds similar. Was a private IP an option?
Thanks everybody on the thread.
I did end up being able to get a public IP address. Comcast uses some weird routing/Carrier Grade NAT and it can get difficult to get a public IP from them from what I understand. I jumped that ship and went to a local Fiber ISP ASAP.
Ah, well good for you. No Fiber where I am. I wonder if that issue will disappear with IPv6 or if they are going to NAT those as well.