NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
R6700v3 firmware 1.0.4.118 caused connection problems
Thunderbird could not connect to imap servers.
SplashTop said no internet.
TomTom MyDrive Connect said no internet.
Chrome would say site unavailable and then later connect.
I went back to previous firmware version and all problems have been fixed.
- New 120 Rev appears to be out and fixes the issue, along with others. Running it 5 days now, so far so good.
85 Replies
Further to my post #37 above I did the following additional tests:
1. Changed the WiFi frequency from 5.0 Ghz to 2.5 Ghz. Problem persisted.
2. Connected the computer to the router with an ethernet cable. Problem persisted.
3. Connected the computer directly to the modem. The problems were no longer present.
The firmware upgrade to V1.0.4.120_10.0.91 is definitely the source of the problem.
Netgear please fix this.
From what I can tell the 120 version still has the issues. So far I can tell from the threads there are two issues, connectivity issues getting to the right DNS site, and bandwidth reduction for some.
Is Netgear tech reading these? This problem is extremely serious (software is not usable) and has gone on for too long. We should have a solution by now.
One person has marked this solved which shows at the top as being solved, but the issue is still there in version 120. How do we alert someone this is still an issue and have engineering deal with it? Or remove the solved tag?
Has a factory reset and setup from scratch been performed since last update?
- Several times
go back to the revision of FW before 118. DNS issues started around July 28. Engineering released a beta fix in Sept. They still have not released the official fix. Probably never will.
Just to reiterate what has been mentioned plenty of times here before. I experienced the same issues on my r6700v3. DNS issues (constant page reloading) and also reduced speeds on a gig connection (reduced to 200-220Mbps). This happened on both 1.0.4.120 and 1.0.4.118...same issues. Downgraded even further as recommended here to 1.0.4.106 to resolve the issues. Make sure you disable your auto firmware update to avoid these "feature updates" that literally kill your router. Disappointing there is still no fix, months after.
- Exactly, you have to drop to the.... 106 version, this should be a hint to Netgear where to start looking for the problem.
I've been struggling with this for most of a week. Thought it was my PC until my wife had the same problem. Going back to 1.0.4.106_10.0.80 as I write this, though I got several DNS errors before successfully downloading it, haha!
When I first Googled the issue I learned there are multiple Netgear routers with the exact same issue profile. The same rants, extended timeframes, promised fix announcements, and subsequent multiple broken firmware revisions are repeated - just substitute in a different router model and a different set of fireware numbers in a given Netgear Community thread. I really wonder if they are intentionally breaking old routers so we'll buy new ones.
