This topic has been marked solved and closed to new posts due to inactivity. We hope you'll join the conversation by posting to an open topic or starting a new one.
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.
I had exactly the same as nytola77. If you go to the netgear website for your router, you can click "Downloads". It will show the latest **120**at the top of the box. At the bottom of the box is a link for all previous versions. I downloaded the zip file to my HD and searched for the '.chk' file. INSTANTLY all became well with the world (10-20-21).
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?
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.
That is exactly what the game plan is tomorrow. Netgear doesn't appear to do the best at verifying functionality before these firmware updates go public
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.
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.
I just want to echo what many others have said here, i. e. that it is ridiculous that Netgear has not yet fixed the bugs in the two firmware updates issued subsequent to the the 1.0.4.106 version. (As I described in previous posts I downgraded back to the 1.0.4.106 version after installing the 1.0.4.120 version.)
Prior to purchasing the R6700v3 I was using a perfectly functioning Netgear WNR2000v5 router. The only reason that I purchased this R6700v3 router was that Netgear indicated the WNR2000v5 had reached end of support and would no longer be getting security updates. So, now I have the R6700v3 with acknowledged security holes that Netgear seems unwilling or unable to patch with workable patches.
Hey DarrenM...just gave the trial firmware a go and reporting in. Unfortunatly the DNS reload issues have not been resolved. Same as the.118 and .120 versions. The speed limiting issues have been resolved however. I have backed out the trial firmware and downgraded back to .106.
Yes, right after I bought my R6700v3 Router in April this year, I updated to the .106 version and it was fine. I wish I NEVER updated it to the latest .118 and then .120 firmware... I only did it because Netgear Emailed me saying "We've Enhanced Your Product's Security. Please Update to the Latest Firmware".
My Ethernet connected PCs seem to exhibit the DNS issue often, sometimes I need to refresh my browser 5 or 6 times to go anywhere! Our Wireless connected Android phones don't seem to do it that often.
