NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
Remote Management
I'm using a Netgear R6700v3 router with Windows 8.1 using Chrome. Also iPhone 8 and iPad. I'm attempting to do full remote management as opposed to the Nighthawk app. I have remote management turned...
> [...] Is this how it's supposed to work? [...]
I'd say so. When "only this computer" means "only this IP address",
and that IP address changes, then it's not seen as the same "this
computer".> [...] I guess I could allow remote access by "everyone" but it doesn't
> seem like the wise thing to do. [...]Choose a good password.
> [...] Or maybe an IP range but I wouldn't know what range to put in.
> [...]I'd expect that to depend on the ISP in use by the phone. What are
some example IP addresses which it has gotten recently?> [...] Or else get a static IP address. [...]
For a phone? I'd bet against that being possible.
I suspect that the designers expected the user to have a real
computer with a fixed (or reasonably limited) IP address. Or else,choose a good password?
When I plug in my actual local router IP address and port while using a device that is outside my local network then I can access the router management fine. So it's just when I'm using the DDNS URL that doesn't match.
Actually using the public IP from within the LAN did not work either. Guess it doesn't match www.routerlogin.net.
> I'm using a Netgear R6700v3 router [...]
Connected to what?
> Actually using the public IP from within the LAN did not work either.Useful test.
> Guess it doesn't match www.routerlogin.net.
Not the right match question. All those "routerlogin" names point to
the router's LAN interface.What matters for Remote Management (or port forwarding, and so on) is
whether your public IP address matches the IP address of the router's
WAN/Internet interface. ADVANCED > ADVANCED Home : Internet Port :
Internet IP Address. Plug that address into the form at:
If the R6700v3 is not hiding behind some other local router (say, in
a "modem" which really is a modem+router), then the next suspect would
be carrier-grade NAT (growing in popularity these days):My "Advanced > Advanced Home:Internet Port:Internet IP Address" does indeed match my router's public IP. I did plug the routers public IP in WHOIS-RWS which was able to find it ok (Comcast). The router is connected to a modem which is modem only. But I did find something. In the "remote management" section I had specified "only this computer" in which I entered the WAN IP address my phone shows with wifi/bluetooth/personal hotspot turned off. I've discovered that while this IP address matches what my phone shows, then I can access remote managment just fine. But when the IP address lease on the phone expires and a new one is assigned then I can no longer use remote management. If I then manually update the "only this computer" IP address to the new WAN address my phone shows then I can use remote management again. So nothing is updating the "only this computer" IP address when my phone IP lease expires and I get a new one. Is this how it's supposed to work? I guess I could allow remote access by "everyone" but it doesn't seem like the wise thing to do. Or try to anticipate when I will need remote management and update the IP address in remote management first. Or maybe an IP range but I wouldn't know what range to put in. Or else get a static IP address. Am I understanding the correctly or still missing something? Thank you.
> [...] Is this how it's supposed to work? [...]
I'd say so. When "only this computer" means "only this IP address",
and that IP address changes, then it's not seen as the same "this
computer".> [...] I guess I could allow remote access by "everyone" but it doesn't
> seem like the wise thing to do. [...]Choose a good password.
> [...] Or maybe an IP range but I wouldn't know what range to put in.
> [...]I'd expect that to depend on the ISP in use by the phone. What are
some example IP addresses which it has gotten recently?> [...] Or else get a static IP address. [...]
For a phone? I'd bet against that being possible.
I suspect that the designers expected the user to have a real
computer with a fixed (or reasonably limited) IP address. Or else,choose a good password?