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...
Router model: R6400v2
Firmware: V1.0.4.122_10.0.95
OS: Windows 10 64-bit
My router was working fine, right up to when I updated to the above firmware. When I tried to login to the router's GUI, I received the following:
This site can’t be reached
www.routerlogin.net refused to connect.
Try:
Checking the connection
Checking the proxy and the firewall
ERR_CONNECTION_REFUSED
Nothing I did, short of doing a factory reset, fixed the problem.
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.
There is a serious problem with the above firmware update. I plan to download the previous firmware update, do another factory reset, then install the previous update.
Hopefully someone from Netgear will read these posts and get this problem fixed.
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.
Sorry I didn't respond sooner. I work for a church, so this time of year is big time busy.
The modem in front of my router is a Motorola SB-6141.
I don't really see how that matters, as I can get out to the Internet just fine.
The problem is with the GUI of the router itself. Accessing the GUI worked just fine until I did this most recent update.
My plan is still to do another factory reset and then downgrade to the previous firmware release, which was V1.0.4.120_10.0.91.
Fortunately, I have all my settings documented so I can reenter them all fairly easily.
Darkwater wrote:
The modem in front of my router is a Motorola SB-6141.
I don't really see how that matters, as I can get out to the Internet just fine.
The modem makes all the difference. Time and again people turn up here with problems that track back to their "modem" being a modem/router. So they are trying to daisy chain two routers, which is a recipe for chaos and confusion and the symptoms that you describe.
It even has its own name "Double NAT".
What is Double NAT? | Answer | NETGEAR Support
I mention it only to correct your mistaken belief that modems do not make a difference. But in this case, the Motorola SB-6141 really is just a cable modem. So your problems lie elsewhere.
My plan is still to do another factory reset and then downgrade to the previous firmware release, which was V1.0.4.120_10.0.91.How do you plan to apply the old firmware if you cannot get at the GUI? I ask because they may give us some more information on what is really going on.
Fortunately, I have all my settings documented so I can reenter them all fairly easily.You would not need to reenter anything if you had used the GUI some time in the past to create a backup of your settings. The manual explains how to do that:
Manuals are always a good place to start.
Visit the support pages:
Support | NETGEAR
Feed in your model number and check the documentation for your hardware.
