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 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.
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
9 Replies
Russ_9863 wrote:
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.
This explains some of the other drawbacks.
What is Double NAT? | Answer | NETGEAR SupportBy 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.
> Which of the following could cause the problem:
> Has FireFox updates broken it or
> Has Win 10 prevented it from working?Or, there's some other difference between the systems which work and
those which don't. (Which would be my guess.)> When I try to use it I get the following
>
> You may not be connected to your Router's WiFi network. [...]Welcome to what may be the worst error message in the world. For an
explanation, try:https://community.netgear.com/t5/x/x/m-p/1365830
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.It does? Olfactory system trouble?
.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
one with Win 7 the other with Win 10.
