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 2015.
As of 1.5 months ago, 2.4ghz band has been very intermittent, and at this point i was already using firmware 1.0.4.30. Rebooting the router did not do anything. I do not have any settings on the router except the ssid, password and channels.
I tried going back to firmware 1.0.4.28 and that only worked for maybe 2 days, then the disconnects started again. i have been using Wifi Analyzer app on my tablet just to see if there is a transmission signal from the router. 5ghz band has a constant transmission signal however the 2.4ghz band has an off to on time of maybe 3:1 at the best of times. This allows me to SOMETIMES connect to the router while on 2.4ghz band, but usually it will not connect. I have been forced to connect my desktop via a really long ethernet cable and older devices no longer have internet connections. I am currently still monitoring the off to on time and the worst as of yet is about 10:1. Basically the 2.4 ghz band is completely dead minus random spikes of it showing up.
I've seen a few posts with the 5ghz band issue similarly but no fix either. I used to have a wndr3700 and that worked fine until the range on the router out of nowhere and permanently dropped by about 25% causing me to buy a repeater to get coverage. Using the repeater solved the distance issue but then i had issues with connection speed (not huge but noticeable). I figured buying an R7000 would be a no brainer since its a top of the line unit and priced as such. I am very disappointed as i haven't been able to find a fix anywhere for this.
Any help would be greatly appreciated
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!
425 Replies
- Killhippie I'll do another hard reset and reflash the netgear beta and see what happens as like you it doesn't make sense why I have this issue.
Don't use a config file after to put back your settings, enter everything by hand. It's a chore but it's the best way to avoid issues. Hope it works.
After I reverted to an earlier firmware V1.0.5.48_1.1.79 I used my backup file to restore my settings. I found that everything worked fine including my 2.4 ghz but all of the port forwarding I had for my cameras and security/home automation system did not work. I had to manually delete them and re-enter and that fixed the problem.
I have tried everything mentioned here following every advice carefully to no avail, I'm using my old wndr3700v1, yep another netgear product, hopefully that one doesn't go bad on me like the r7000, oh my bad i would have to flah the messed up netgear firmware for that to happen.
I even tried 3rd party firmware and still can only connect to 5g not to 2.4
I'm done with netgear.
Hardware dies, it happens it could also happen to any make of router you buy. I'm sorry it happened to you but its one of those things. All hardware dies eventually.
I just tested and it works on 1.0.6.28 and 1.0.6.40 when disabling the security, but not with security enabled? Still same issue device shows up in list of devices but with no name or IP. Is this a known issue? Any suggestions or solutions?
Hi mkruger,
If it will still not work after factory reset and manual reconfigure, you may revert to firmware version v1.0.4.30.
I just installed the beta version, 1.0.6.40, this morning when my earlier version, 1.0.5.48, failed on 2.4GHz. I did a hard reset to factory and reconfigured everything. It worked for about 9 hours and then 2.4GHz failed. I am going back to 1.0.4.30 to see if it works. I guess 1.0.6.40 isn't quite ready for distribution yet.
- You guys are like a bunch of whiny kids. Run 1.0.40.3 and stop whining.
First off I don't want to run a version with vulnerabilities in it. Readyshare print is vulnerable In that version. Secondly there are features in the latest firmware I use. Just because you don't please don't assume others don't as well, if you can't come up with a helpful comment don't comment at all.
Then make sure your WAN end of things are secure. If you have to protect against intruders on your LAN side then you have bigger issues than a firmware one.
- I use pfsense as my UTM and only use the R7000 as AP 2.4 still doesn't work for me and I have tried every suggestion mentioned here.
the flaws in the firmware exist regardlessTry using the AdvancedTomato firmware. I had no issues on 1.0.4.30 but the Tomato has more features and control.
- I will try that and see how it goes, thanks
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.
- J_Gonzalez - I know your pain. I spent about 80 hours testing the heck out of this router. 1.0.4.28 has been rock solid for over a month. I have about a dozen devices (including switches) connected via Ethernet, about ten 5ghz devices, and several 2.4Ggz devices connected almost continuously. Every other firmware version after 4.28 (I tried them all for multiple days) had issues. Because 4.28 is so reliable, I am inclined to think there is not a problem with the chipset per se but is almost certainly a firmware bug introduced in 4. 30 and carried forward thereafter.
Hi all, I'm sorry for my delayed response. I've been out of the office with a root canal, so I have not been able to speak directly to the engineer about this, but have only swapped emails with him. Let me share what I understand, recognizing that I may not have all the information.
When we began testing the new beta firmware, we added some new test cases to evaluate the 2.4 GHz in a very noisy environment. In these new tests, we see some wireless disconnects. We think the issue may be with the chipset driver.
Interestingly, most people on this thread have had good success with the beta firmware. Perhaps our noisy testing is more extreme than most customers experience and we're being too cautious in delaying our beta firmware release. But when I read KazzMANIA's post and saw the time investment he made, I'm reluctant to release firmware unless we're certain it's rock solid.
JGonzalez, I'm sorry to hear that the beta firmware didn't work for you, but if you have any config files you could share, we would love to see them.
Again, I'm very sorry for the delay and continue to appreciate the feedback.
I do have a config file. Let me know how to send it to you and I will.
Regarding the noise, my client that is having this problem is in a "creative space", which is neo speak for an open floor, a large table with a bunch of people on laptops sitting side by side and across from each other. So perhaps the "noise" comes from a bunch of laptops being spaced a couple of feet apart.
The router in this environment is wall mounted on a backboard, up high, without anything nearby. So it's in a pretty clean location. And it's the only WiFi device in the office.
- REGARDING MY LAST POST - please note that I have not tried the beta. I spent more than enough time being a test subject and will wait for a confirmed working release before giving up 4.28
Oh no, oh no oh no oh no. I've just been experiencing problems on the 2.4Ghz channel with my brand new R7000 on the latest firmware which is frankly a disaster - because I bought the R7000 to replace an Asus AC68U that had the same issues with the 2.4Ghz channel!
It's like i'm doomed to never have a working 2.4Ghz channel. I'm starting to think the issues both routers have might even be related, they share a lot of the same hardware I believe.
Does anybody know of alternative firmwares work? E.g. Tomato / DD-WRT?
