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.
Just upgraded the firmware and now the router login doesn't work. Tried it with just the IP and that didn't resolve. Seen a lot of complaints about logins. Seems like that's something that should be addressed by now. Tried incognito mode and that didn't work either. Everything resolves to https://www.netgear.com/home/products/networking/routerlogincom.html or not at all.
Folks on this forum are end users like you. Some have experience and can help others.
Have you tried using a browser and going to the router's IP address, typically 192.168.1.1. Apps and relying on the DNS lookup for access can be iffy at times.
"not work" 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.
> [...] Tried it with just the IP and that didn't resolve. [...]
"Tried" _what_, exactly? With _which_ "the IP"? What, exactly, does "didn't resolve" mean to you? See "not a useful problem description [...]", above.
> [...] Seen a lot of complaints about logins. [...]
Swell. The non-psychics in your audience may not be able to guess what you saw where.
> [...] Everything [...]
Which subset of real "Everything" did you actually try?
> [...] resolves to [...]
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.)
> [...] or not at all.
See "not a useful problem description [...]", above.
Folks on this forum are end users like you. Some have experience and can help others.
Have you tried using a browser and going to the router's IP address, typically 192.168.1.1. Apps and relying on the DNS lookup for access can be iffy at times.
> [...] I was using .html instead of .htm which I thought I had seen > with the hostname. [...]
And that's why an accurate, precise description of actual actions (commands) with their actual results (error messages, LED indicators, ...) can be more helpful than vague descriptions or interpretations.
Visit http://netgear.com/support , put in your model number, and look for Documentation. Get the User Manual. Read. Where does it mention ".htm" or ".html"?
> Do you work for Netgear?
That's your biggest concern? Yow. Look for the "N" logo by the relevant user ID.
