This topic has been marked solved and closed to new posts due to inactivity. We hope you'll join the conversation by posting to an open topic or starting a new one.
it does not. I have to use the IP address instead to get to the administrator page..
I can goto any other page just not the routerlogin.
Which of the following could cause the problem:
Has FireFox updates broken it or
Has Win 10 prevented it from working?
When I try to use it I get the following
You may not be connected to your Router’s WiFi network. To access routerlogin.com, your device must be connected to your Router’s WiFi network. Check your current connection and try again.
I am using a computer that has a direct Ethernet cable connection to the router
I just discovered something. I forgot I have another much older Win 7 computer
Ethernet cable connected to the same router. When I tried http://www.routerlogin.net it worked ! That means either FF or Win 10 is not allowing the router to see the command.
I just discovered something. I forgot I have another much older Win 7 computer
Ethernet cable connected to the same router. When I tried http://www.routerlogin.net it worked ! That means either FF or Win 10 is not allowing the router to see the command.
Smells like you may be in "double NAT" territory.
What firmware version do you have on the WNR2000v3 device?
A number is more useful than "the latest". (It may not be by the time people read this.) There can also be newer versions, or "hot fixes", that do not show up if you check for new firmware in the browser interface.
It might also help if you told people what the modem is in front of this router. The model number could be useful. Is it, by any chance, also a router, with a set of LAN ports on the back?
The reason for asking is that a lot of people turn up here trying to put a router behind a modem that is also a router.
Having two routers on a network can cause headaches. For example, you can end up with local address problems. Among other things, the other router can misdirect addresses that the Netgear router usually handles, such as routerlogin.net or the usual IP address for a router, 192.168.1.1.
By the way, the WNR2000v3 is pretty old (2010). I wouldn't expect much, probably slow local network and no 5 GHz wifi. No problem if it meets your needs.
Briefly, the idea is that "[www.]routerlogin.net" (or ".com") should point to your own router, but that's true only if you use your own router for DNS name resolution. (Or, if the Netgear router can intercept your DNS queries.) Regardless, as you have discovered, you should be able to get to the thing using its IP address, if you can determine (or guess) that.
I'd look at the DNS server settings on these systems, and see if differences in them explain the differences in their behaviors.
> [...] That means either FF or Win 10 is not allowing the router to see > the command.
No, it really doesn't. There are more variables than those two.
"My red car starts, but my green car doesn't. Must be the paint."
> Smells like you may be in "double NAT" territory.
Re: WNR2000v3 cannot access router page via www.routerlogin.net must use IP address
.The modem is an Arris TM902 cable telephony modem (Charter) with only one ethernet output which goes to the Netgear router which in turn goes to two desktop computers
Re: WNR2000v3 cannot access router page via www.routerlogin.net must use IP address
> [...] Do you have any idea as why having Enable DNS over HTTPS checked > blocks the routerlogin.net causing to receive the infamously bad NETGEAR > error message?
Programs (like a web browser) need an actual IP address to establish communication with the program at the other end the other end (like a web server). DNS is the system which translates between names and numbers (IP addresses).
The various "routerlogin" names work (when they do) because the router can intercept the DNS requests which ask for the address which corresponds to any of those names. When it sees a request to translate any of those names, it returns its own (LAN) IP address, instead of using the usual (real-world) DNS server.
"DNS over HTTPS" encrypts your name-to-number requests, so that the router can't recognize any "routerlogin" names in them, so it will be unable to intercept them, and, hence, won't return its own (LAN) IP address.
The result is the same as with any other configuration which bypasses the router's DNS server -- your name-to-number request goes to a real-world DNS server, which gives you the address of Netgear's stinking-error-message server.
Thanks for the research and the interesting report. I never fiddle with those browser settings, so I might never think to look there.
