NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Nighthawk App Logon Timeout
I can not access my WiFi settings using the Nighthawk App. I get to the admin login portion and type in my password and an error message pops up saying logon timeout. I’ve tried resetting the admin...
Xenobiotics wrote:
UPDATE: I downgraded the firmware from v1.0.2.134 to v1.0.2.130, and now I can connect using the app. This isn't the first time a firmware update has broken the app. So frustrating. If I could go back in time, I would tell myself not to buy this router---and to steer completely clear of Netgear.
Oh so true.
One thing to try, if you haven't done so already, is a factory reset with the new firmware.
If you have, forget it.
New firmware sometimes introduces changes that are not compatible with the old configuration.
So while it isn't guaranteed to fix problems a factory reset is the first thing to try if you have issues with new firmware.
This is a nuisance because you then have to reconfigure the device all over again.
You can backup your settings before you reset and restore them later. But that may just bring back the fault. Then again, at least you will know if the reset fixed the problem.
I had the same issue here. App version 2.6.2.12. Router R8000P. The App was working until a couple of weeks ago, when I received the time-out message, and was never able to get on again even after resetting the router. I had Face ID on, so the password should be correct. No issue with logging in from the web at 10.0.0.1 with the phone's browser. This is definitely a bug. I also had the issue of the router itself not auto updating to the new firmware or downgrading to a previous version. It's stuck on V1.4.1.50_1.3.10. The whole system is a big mess.
lexllp wrote:
No issue with logging in from the web at 10.0.0.1 with the phone's browser.
This suggests an atypical installation.The default LAN IP address for the browser graphical user interface is 192.168.1.1.
Unless you set that up deliberately, that IP address usually happens when you put a router behind a router. (More often it is a modem.router.)
In those circumstances some things won't work as expected.
Two routers on your 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 SupportNot sure how that is relevent. The Nighthawk App was working for five months in that setup and it is not now. Yes, I set the router behind a FIOS router, which is in bridge mode. I can access the R8000P either from 10.0.0.1 or 192.168.1.2. This was the same setup on the R6900 for many years before I replaced it with the R8000P. Long stories short, I've had problems with Circle, Time Machine, etc. that led me to think that Netgear firware is not up to par. Users shouldn't have to search for tricks and obscure routines to fix some hidden issues on a router that ought to be a plug and play for simple wi-fi setups.
lexllp wrote:
Not sure how that is relevent.
Fine.I thought you might be interested in investigating your issue.
I can see how it might be relevant – based on experience and what I read here – but that is your call.
lexllp wrote:
Users shouldn't have to search for tricks and obscure routines to fix some hidden issues on a router that ought to be a plug and play for simple wi-fi setups.
True. But they should know how to configure their networks correctly.
Double NAT is not a hidden issue. It is a well known "feature" that can wreck an otherwise functioning network.
Thanks for your answers. I apprciate it your help. As mentioned, I don't have a double NAT issue since the fios router is functioning only as a bridge, which is one of the solutions offered in the link you provided.
I am having this problem but think I might have found the cause. Am I right in thinking the app will only work on one device?
It works fine on one of my iPads but I get this problem on the other.
Very silly if that's the case .
It works fine on one of my iPads and not on the other. Save version.