NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
R7000 2.4ghz not working but 5ghz is fine
Firmware 1.0.4.30 and 1.0.4.28 tried for weeks at a time.
Wireless devices connected to 5ghz band are all working perfectly and have been since i purchased this router at the beginning of June ...
Good news! We now have a production version of firmware that should resolve the 2.4 GHz issue, v1.0.5.64. You may download this firmware from our R7000 page here: http://downloadcenter.netgear.com/en/product/R7000#searchResults
As IrvSp correctly notes, this version of firmware fixes the 2.4 GHz issue and reinstates the new features, such as Kwilt, Smart Connect, and WiFI Transmit Power Control. It does not support Arlo. We hope to have a beta version that supports Arlo in the next two weeks.
We welcome any feedback you provide on this new firmware, and appreciate your patience as we resolved these issues. Thank you all for supporting the R7000 and NETGEAR!
Netgear, any updates?
I've been waiting patiently, but if I'd run my consulting business this way I'd have no customers.
I have no time for tinkering and am not interested in resetting my LAN configuration or installing alternative or beta software or digging through 30 pages of user comments for work-arounds.
I paid good money for this router as your flagship product and expect to have issue addressed with priority, especially those introduced by you.
Thanks.
Fishbone, I apologize for the delay in responding. In the process of testing the fix for the 2.4 GHz issue, we uncovered another issue. Rather than release new firmware that resolved one bug while leaving another one present, our plan was to fix the second issue before releasing the production firmware. We agree that rolling back production firmware has been time-consuming and frustrating for our customers, which is why we thought it would be better to take the time to resolve this second issue.
We think we understand the root cause for the second issue, and hope to have new firmware completely tested and available at the end of March. I apologize for the time it has taken us to resolve these problems. If you or others disagree with this plan and prefer that we go into production with the 2.4 GHz fix faster rather then waiting to resolve the second issue, I am open to that feedback. Thank you for your patience, and again, I apologize for the delay.
Nifer - thanks for the update.
It's just that 2 weeks ago you delayed the update for 'another week' and we didn't hear anything further since then, which is frustrating.
I think a lot of us might prefer to get the radio working but that depends on the nature of this other issue - if we can live with it.
And are you confident the previous 'beta' is addressing the radio issue or have there been additional changes - and is all the work going forward (3 weeks...) related to the new issue?
Thanks.
I wanted to update my status with this router.
It was purchased in December of 2015 for a 15 person office. After I first plugged it in and configured it in, I then updated the firmware, as I normally do, to v 1.0.5.48. I don't remeber what version it had out of the box, but I think it was 1.0.5.x
Out of the 15 people, about 7 or so are connected via WiFi. out of those 7, 2 of them are connected to the 2.4GHz channel. Shortly after the installation, one of the guys on the 2.4Ghz channel dropped his connection. Didn't think much of it, so I just logged on remotely and rebooted the router. All good. A few days later, same thing, and since I couldn't log on, I asked him to power cycle the router which got him back on. Since this was very close to the holidays, we sort of worked through it and thought it might have been his computer. The one thing that was clear though was that no one else was having problems.
So in January I started getting more complaints. They would power cycle the router, but that wasn't a practical solution because then it would disconnect everyone, and files that were open on the server would lock up or get corrupted.
I began looking for a solution which lead me to this thread. Shortly after I downgraded the firmware to 1.0.4.30. After 3 days or so, the problems returned. Power cycled the router, then the 2.4GHz channel dropped again 2 days later. Since I had made contact with Netgear, I was given the beta version of the firmware (1.1.10.167514). Hoping that was the magic bullet, I installed it, only to have it fail 3 days later, then again a few days after.
The office was good at letting me know when it went down.
I should add that since I am not on site, I was doing the firmware changes remotely, so I never did a hard reset after the firmware change. I've NEVER had to do that on a router, so I find it an odd request to do so.
So finally, last Friday (3-4-2016), I went into the office and downgraded the firmware (from the Beta version) and installed 1.0.4.28_1.1.64
This time I did the hard reset after the downgrade and reconfigured the router. We don't have any port forward rules, so it's general config that I had to do. I've not heard of a problem yet, but since guys are in and out of the office regularly, I'm not sure how much use it's gotten. I will keep the forum updated on way or the other.
Having said all that, I understand Fishbone's position. I'm VERY thankful that this client is very patient and understanding. I have other clients that would not be so understanding and would have expected this fixed after the 2nd or 3rd time it failed. Since I recommended the router, I would be on the hook for it. While I'm glad that Netgear has acknowledged the problem - and purports to be working on it - we all have, essentially, a faulty product. I like to standardize on hardware because it makes support and management much easier for me. But there's no way that I'll buy another R7000, why would I risk my time and reputation?
Linksys had a problem with their WRT-1900AC (v1) a while back. The router would reboot itself several times a day, dropping all connections for a couple of minutes until it came back up. Linksys knew they had a bad product, and even after a year they are accepting the routers back for a full refund! BestBuy is aware of it and handle the returns effortlessly. Netgear may want to take notice.
Having worked in IT for over 20 years, I'm willing to give some slack to software and hardware vendors, and am willing to work with the vendors in resolving problems. But the key word there is "resolving". I struggle to believe that a company like Netgear hasn't solved this by now.