NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
jwong84
Sep 10, 2015Aspirant
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 ...
- May 25, 2016
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!
ikalatch
Nov 04, 2015Aspirant
Same issue here - 2.4 Ghz band has been behaving erratically recently (dropping all conections and refusing to connect devices until the router is restarted). Died completely today - the LED on the front panel is lit and all the settings on the admin page of the router suggest that the 2.4Ghz network should be working but it is not visible anymore. Been on the latest firmware for a while, so no changes there. Seems like a H/W problem - a dead radio...
JamesGL
Nov 05, 2015NETGEAR Employee Retired
Hi ikalatch,
If you have not tried resetting the router to factory default, please try it and check if it will continue to have the same behaviour. After resetting, manually configure the router instead of using the back up.
Regards,
JamesGL
Community Team
- ikalatchNov 05, 2015Aspirant
Thanks, James, yep, I did that last night after reading up a bit more and it seems to have fixed it. Wanted to wait a bit more and see if the fix holds but from what I've seen so far after 20 or so hours - seems to be OK.
I'd have bet good money that this was a hardware problem, nice to be able to resolve it with a reset!