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 on for one computer. I've set up DDNS using the Netgear provided domain (mynetgear.com). I'm using port
8443 and the port check indicates it is open. With my DDNS host name provided by Netgear via No-ip along with the port I can reach my router from within
my LAN with the DDNS URL by proceeding through the "NET::ERR_CERT_AUTHORITY_INVALID" message. But when I try to access my router from outside my network I
can't get past the "Certificate Invalid" message. I get a blank page with the error that the root certificate for "www.routerlogin.net" is not trusted.
This is probably because the DDNS is using my real IP address as opposed to "www.routerlogin.net", so they don't match. I don't know how to get around
this. The point of doing remote management is so you can manage the router away from the local network which is what I'm trying to do. Any ideas? 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?
5 Replies
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):
