I'm sure I'm missing something obvious but is www.routerlogin.net only available via wifi? I tried to access from my desktop PC with a wired connection whilst setting-up my Nighthawk this morning (which I had to abandon, going to re-attempt tomorrow) and couldn't - but it was perfectly accessible from my phone.
> [...] is www.routerlogin.net only available via wifi? [...]
> [...] I tried to access from my desktop PC with a wired connection
> [...] couldn't - [...]
"couldn't" is not a useful problem description. It does not say what
you did. It does not say what happened when you did it. As usual,
showing actual actions (commands) with their actual results (error
messages, LED indicators, ...) can be more helpful than vague
descriptions or interpretations.
If you ended up here:
then welcome to what may be the worst error message in the world. For
an explanation, try:
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, you should be able to get to
the thing using its IP address, if you can determine (or guess) that.
Normally, that would be something like "192.168.1.1" (for a plain
router) or "192.168.0.1" (for a modem+router), but it could be
different. ("10.0.0.1" is a typical alternate, for example.)
If you manually configured the DNS server settings on your
(unspecified) "my desktop PC", then it's all your fault, and you'll need
to use the router's (LAN) IP address, instead. A wireless device is
more likely to get all its settings from the router, including its DNS
server settings, so it's more likely to work with the "routerlogin"
Forget the fancy stuff. Use the router's IP address, normally 192.168.1.1 in a browser. That should always work as long as the router is healthy.
> Forget the fancy stuff. Use the router's IP address, normally
> 192.168.1.1 in a browser. [...]
The advantage to using a "routerlogin" name is that it relieves the
user of the need to know the router's LAN IP address, which is not
The value of this should be evident to anyone who read the original
post and the first response here, because, in this case, for a "Model:
D7000|Nighthawk AC1900 VDSL/ADSL Modem Router", the default LAN IP
address is "192.168.0.1 (for a modem+router)", _not_ "normally
It's ok with me if anyone wants to "Forget the fancy stuff", but,
when doing that, it can pay to remember _correct_ stuff, instead.
Use the router's IP address, normally 192.168.1.1 in a browser.
That won't work if you have got yourself in a pickle, for example, thanks to having a modem/router in front of the router, healthy or otherwise.
Then again, many experienced users with properly configured networks prefer using the IP address.
Just another user.My network DM200 -> R7800 -> GS316 -> PL1000 -> Orbi RBR40 -> Orbi RBS50Y -> RBS40V