NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
Firmware Version V1.0.4.118_10.0.90 FIRMWARE ISSUE FOR ROUTER AC1750 SMART WIFI R6400V
A week ago i logged onto router and updated the firmware with what was suggested by Netgear. Ever since then, I keep having issues with DNS. Every site I select from the list of search results come...
here's where you can get the firmware: R6400v2 | WiFi Router | NETGEAR Support
for older firmware, click on "view previous versions"
then just follow the manual firmware update process but use the older version you downloaded and not the newer.
I'd downgrade to the version prior. Seems to resolve it for issues.
I've seen multiple posts on here about recent upgrades breaking dns so I have a feeling netgear is aware of it.
How do I do that? I do not know the version prior?
here's where you can get the firmware: R6400v2 | WiFi Router | NETGEAR Support
for older firmware, click on "view previous versions"
then just follow the manual firmware update process but use the older version you downloaded and not the newer.
Thank you I did not see the previous link before
Went to the current version of firmware. My issue wasn't as pervasive as what others had reported. I would get a message "HMMM - Page couldn't be loaded" (Perhaps this was the DNS issue reported by others) then 4/5 seconds later it would load. Occaisionally, there would be problems with the rendered page. After doing a lot of searches and trying some setting adjustment the problem was still present. Installed chrome and tested and the problem disappeared. Fell back to edge and the problem would popup. I have a router on either side of a hardware firewall. The issue never surface on RTR1 only RTR2 behind the firewall. No error messages in the FW log. I reversed RTR2 and RTR1 and the problem stayed with RTR2 now infront of the firewall. REalizing that although I had WIndows maint recently I alos upgrade rtr2's firmware. So risking bricking the router I opted to fallback to the prior version and move the routers back to their original location. I retested for about 30 minutes going against a URL that regularly had the issues. Couldn't recreate the issue.
Probably wasted about 3 or 4 hours over 2 days diagnosing and resolving...
