NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
V1.0.4.122_10.0.95 Update on R6400v2 kills lon in page
I applied V1.0.4.122_10.0.95 to my Netgear R6400v2 router yesterday. Now I can’t access the router configuration GUI. Everything else works OK, but I can’t log into the router now. The update complet...
Hopefully someone from Netgear will read these posts and get this problem fixed.
With just a handful of reports, it doesn't look like the usual firmware bug.That would usually show up with a torrent of specific complaints. (We have hand a couple of those lately.)
We have yet to exhaust all of the possible reason for this problem and have yet to rule out issues at your end for example, I still see no answers to this earlier question:
What modem (if there is one) in front of this router?
It is there for a reason. Take this behaviour:
Finally, as a last resort, I did a factory reset and, lo and behold, I could access the router's GUI. My joy was short lived. I made a minor change (changing my time zone) and, lo and behold, I'm locked out of the GUI again.
One cause for this can be a conflict between the router and the modem in front of it. Hence the modem question.
Coming up with theories about what is going wrong is fine, but it helps to go through all of the standard troubleshooting steps before reaching conclusions.
After I applied the update the router's GUI at https://192.168.1.1 was not longer accessable.. See my previous post to see the screen shot. I rebooted the router and still no joy. Then I ran an nmap intensive scan to see what ports were open. The ports the web browsers use to acces the GUI are standard web server ports at either http (port 80) or https (port 443). Neither of these ports are up. That is why you can't get a log in. This is an internal issue with the router. If a modem issue suddenly causes a problem after a Netgear update, then Netgear has a huge problem and maybe it is time to consider another vendor. But I repeat myself, the standard web ports are not up so the web GUI will not be acessable until the router brings these ports back up.
The the R6400 does not have port 80 or 443 up after the update
I put my old WNR2000 router on the bench and ran an nmap scan and can see port 80 is up on that router.
This is what it should look like..
I was unable to downgrade the firmware via tftp. After powering off the router for 10 seconds and powering back on the power led was only solid orange until turning white, never flashing. I also noticed that nothing was being served on port 69 (even right after the router began returning pings).
I was able to resolve the issue by doing a factory reset via the pin hole. It did requrie me to reset up everything but shame on me for not having a recent backup.
Dido.. I could not get tftp to work for some reason. I ended up doing a factory reset which brought up the router up and I was able to revert to .91. I always save the settings before an upgrade so I restored them and now every things works as it should. Are you still running .95 ok? I am a little leary of loading .95 for now as .91 works ok.
Tvestra wrote:
Dido.. I could not get tftp to work for some reason. I ended up doing a factory reset which brought up the router up and I was able to revert to .91.
This discussion is all about people who cannot access the login page. Now you are saying that a reset lets you back in.
Earlier you said that the issue returned after making changes to the settings. Is that still the case?
The first move that anyone should try if new firmware causes problems is a factory reset.
If that fixes the issue, then the problem may not be the firmware but that something went wrong in the original update process.
So, if a reset removes the issue, rather than going back to older firmware, it might be a better idea to manually reinstall the new firmware. That could mend any errors that occurred during the original installation.
Braunc55 wrote:
...shame on me for not having a recent backup.True, but restoring a backup can also restore bugs that existed before the reset.
But at least you could have wiped it and started over yet again.