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...
Tvestra wrote:
Will Netgear be putting an updated version out soon with directions on how to upload it? In the mean time can I reload the R6400v2-V1.0.4.120_10.0.91.chk file I have? I am running Ubuntu and my tftp client appears to connect to the router. Is anyone else reporting this problem?
Is there any evidence that this is a widespread issue?
Do any of these messages suggest the same thing?
Search - NETGEAR Communities – R6400v2
wcalifas wrote:
you should try and re-apply the firmware with tftp and see if that fixes it, if not revert back to the previous firmware until another firmware comes out.
Definitely a good idea to reapply the firmware. But TFTP is usually needed only if the standard approach does not work, unless it is the only way to update firmware. (That isn't clear from the first message.) Before playing with complicated stuff, why not just try the manual updfate?
How do I manually upgrade firmware to my NETGEAR router? | Answer | NETGEAR Support
The same strategy applies if you want to install an earlier version.
Then again, it isn't obvious to me that there is anything wrong with the new firmware. The inability to access the router's GUI needs a bit of investigation. For a start we don't know what happens when Tvestra tries to get into the GUI.
I would troubleshoot that before doing any more damage.
I did the manual install V1.0.4.122_10.0.95. The update completed, but instead of displaying the routers web interface it displayed the attached message. Now when I try to log into the router it imedantly displays the same message. When I use nmap on the routers ip address the http/https ports are missing. Everything else is working. the problem is, if you can't log on to the router, how do you apply an update. Looks like the tftp is the only option at this point. I have seen several posts compaining the they can't log on to the router after this update. Could Netgear have a bug?
That doesn't look like the usual error.
How did you get to that page?
Which browser? (Tried a different one?)
What address did you go for? IP address or something else?
What modem (if there is one) in front of this router?
Have you tried the usual moves:
- tried a different browser?
- reboot the router? (power off and on)
- reboot the whole network
If this were a widespread issue that hit everyone with this new firmware, it would be all over this place. If it just hit you, then it may take some troubleshooting.
It might be something as hard to unravel as changes in your browser's security settings. (They hate http links.) Browser knitters are going out of their way to make it difficult for people to access "sites" that they don't understand.
I am experiencing the same issue as Tvestra after updating the routers firmware. Chrome (Windows & IOS), Edge, Safari (IOS) and curl all return their form of connection refused when attempting to navigate to the web ui (192.168.2.1, yes this is not the standard .1.1). Since the browser was able to access the web ui immediately prior to the firmware update and was how the update was initiated, I have a hard time believing it is an issue with the browser. The router seems to otherwise be functioning as expected. I have rebooted the router 5 or 6 times since the firmware update with no change. I have attempted to access the web ui from both wireless (both 2.4 GHz and 5 GHz) and wired connections with the same results.
An interesting observation is that the Nighthawk IOS app is able to connect.
BrowserNighthawk App
As I stated before the problem is that the router no longer has the HTTP/HTTPS (80/443) ports open. If these ports are not open you cannot connect to the web server in the router. That is the problem. You are just chasing your tail doing a bunch of other stuff to try and connect as there is nothing to connect to. Please refer to the nmap run I did and you can see a lot of ports are open, but no 80 or 443. Port 5555 is running some kind of web service (maybe that is for the IOS app), so the web server running that virtual server. It looks like the server has a configuration issue. As long as port 80 or 443 are closed you will not be able to log onto the router with a web browser. The only solution I can see is to load a pervious version of the update with tftp as that port is still open.
As all the other functions on the router are still working I am going to leave it alone until next week, then I will try to fix it with tftp.
https://kb.netgear.com/000059634/How-to-upload-firmware-to-a-NETGEAR-router-using-Windows-TFTP
