NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
WNR2000v3 cannot access router page via www.routerlogin.net must use IP address
I have a WNR2000v3 WiFi router, Firmware Version V1.1.2.18, Windows 10, FF browser When I had Win 7 http://www.routerlogin.net worked, but now that I have Win 10 it does not. I have to use ...
Dear Michael
You were right about it being a browser issue with my netgear router.
I actually have 3 users on this computer, an admin, mine and my wife's.
All this time I have been trying to solve this problem on just mine.
Well just this morning i got the thought to try to get the router's admin page
from both the admin and my wife's users accounts using the www.routerlogin.net
address name, it worked under both users.
Well on the Admin user, I started by looking in OPTIONS. then in GENERAL
scrolled all the way down to NETWORK SETTINGS.clicked on SETTINGS.
Then scrolled down to the bottom to Enable DNS over HTTPS was NOT checked.
I vaguely remember seeing this being checked under my user account, so I
switched users over to mine and went to Enable DNS over HTTPS and sure enough
it was checked. I then cleared it and then clicked SAVE. Next went and tried the
routerlogin.net IT WORKED!! 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?
Sincerely Russ
> I'd look at the DNS server settings on these systems, and see if
> differences in them explain the differences in their behaviors.
Still true.
> .The modem is an Arris TM902 cable telephony modem [...]
That's fine. That "double NAT" stuff was a distraction, unrelated to
this (DNS) problem.
Here is a kicker/ head scratcher
I can access the router's web page using the http//:www.routerlogin.net in IE but not FF.
All the same hardware just different browsers.
Russ_9863 wrote:
Here is a kicker/ head scratcher
I can access the router's web page using the http//:www.routerlogin.net in IE but not FF.
Something tells me it is a browser issue.
The router won't discriminate against them.
Dear Michael
You were right about it being a browser issue with my netgear router.
I actually have 3 users on this computer, an admin, mine and my wife's.
All this time I have been trying to solve this problem on just mine.
Well just this morning i got the thought to try to get the router's admin page
from both the admin and my wife's users accounts using the www.routerlogin.net
address name, it worked under both users.
Well on the Admin user, I started by looking in OPTIONS. then in GENERAL
scrolled all the way down to NETWORK SETTINGS.clicked on SETTINGS.
Then scrolled down to the bottom to Enable DNS over HTTPS was NOT checked.
I vaguely remember seeing this being checked under my user account, so I
switched users over to mine and went to Enable DNS over HTTPS and sure enough
it was checked. I then cleared it and then clicked SAVE. Next went and tried the
routerlogin.net IT WORKED!! 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?
Sincerely Russ
> [...] 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.
