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...
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.
michaelkenward...
Checked in this afternoon and saw your post. I am happy staying on V1.0.4.120_10.0.91 for now. After trying the Netgear reset method to get tftp to work several times and failing I tried to log in and got a log in prompt. This was after reseting the router about three times trying to get tftp to work. When I loggrd in I saw the router was at V1.0.4.120_10.0.95, but the web pages were kind of off and I had trouble navigating to the update page. So I reapplied V1.0.4.120_10.0.91 and reapplied my config settings I saved before the update. Now everything works as it should. As I said I am leary of the new update and plan to sit on the old version until the dust settles. I have put numerous updates on my older and this Netgear routers without any issues. As I said I noticed that the router was not showing the http/https ports open after the V1.0.4.120_10.0.95 upgrade, which would explain why you could not log on to the GUI as the web service for the GUI was not reachable. Any one that gets the error message I reference in my 2021-12-22 01:24 PM post above can try using nmap to see if ports 80 or 443 are open. Is easy to use and free on all platforms. A quick scan will tell you if the ports are there or not. It may help Netgear to know this if enough users see this problem. I don't know if it is an install issue or not but it seems others are gettin the same issue.
Here is an nmap scan I router and as you can see port 80 and 443 are there. They were not when the router was running the newer update (see my post at 2021-12-24 12:34 PM).
$ sudo nmap -T4 -F 192.168.1.1
Starting Nmap 7.80 ( https://nmap.org ) at 2021-12-28 16:10 EST
Nmap scan report for _gateway (192.168.1.1)
Host is up (0.0023s latency).
Not shown: 93 closed ports
PORT STATE SERVICE
53/tcp open domain
80/tcp open http
443/tcp open https
548/tcp open afp
631/tcp open ipp
5000/tcp open upnp
9100/tcp open jetdirect
MAC Address: 9C:xx:xx:xx:xxxx (Netgear)Nmap done: 1 IP address (1 host up) scanned in 0.37 seconds
michaelkenward I noticed your last post at https://community.netgear.com/t5/Nighthawk-WiFi-Routers/R6700v3-Firmware-update-V1-0-4-122-10-0-95-problem/td-p/2174695
ie - "OK. That adds up to enough cases to warrant escalating this."
Hope this helps...
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.
