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!
Ever since installing R7000-V1.0.5.48_1.1.79 and then R7000-V1.0.6.28_1.1.83, I have been having reliability issues with my Samesung S5 and my Windows 7 machine with a Realtek 8812AU Wireless LAN 802.11ac USB NIC.
I have given up and gone back to R7000_V1.0.4.30_1.1.67. It appears that something bad happened at R7000-V1.0.5.48_1.1.79 and it carried on to R7000-V1.0.6.28_1.1.83.
It is not that devices do not connect, it is that data is being dropped somewhere.
I never had a problem with either of these devices prior to that update.
h_smith wrote:Ever since installing R7000-V1.0.5.48_1.1.79 and then R7000-V1.0.6.28_1.1.83, I have been having reliability issues with my Samesung S5 and my Windows 7 machine with a Realtek 8812AU Wireless LAN 802.11ac USB NIC.
I have given up and gone back to R7000_V1.0.4.30_1.1.67. It appears that something bad happened at R7000-V1.0.5.48_1.1.79 and it carried on to R7000-V1.0.6.28_1.1.83.
It is not that devices do not connect, it is that data is being dropped somewhere.
I never had a problem with either of these devices prior to that update.
It's absolutely a must to do a factory reset after upgrading from 1.0.4.X to either 1.0.5.48 or 1.0.6.28. Do not restore settings from a backed up configuration file because that will undo the factory reset. Re-enter settings by hand.
Thanks for the tip.
I had the wireless fail on my last week. I did a factory reset by holding the button on the back; and then manually entered all the settings again.
This morning the 2.4g wireless failed again. Devices see the SSID, but just can't connect. Turning the router off and then back on fixes the problem. But there is definitely an issue with the firmware (I'm using V1.0.6.28_1.1.83).
Same here, I am on V1.0.6.28_1.1.83 and no devices, iphones, ipad, laptop, chromebook, printers, 3dsXL, PS3, Xbox One. I tested everything they all fail when any auth method is used, I tested each chanel. Nothing works. I have to setup a guest network allow it to share my network and enable it for only 2.4 then I can connect to it using wpa2 and all of the other methods.
Same problem here: 5GHz works perfectly fine, 2.4GHz doesn't. I try to roll back to the 1.0.4 firmware, and had the same issue, I then factory-reset the router, and re-entered the configuration by hand, it worked for a while, but the next day 2.4GHz devices were unable to connect again.
Thanks for the tip about re-entering everything by hand. I appreciate you pointing that out, and I'll do it if I have to, but we shouldn't have to accept that as a solution. They clearly broke something here, and a configuration restore should not break it again. It should only be restoring settings like the network names, passwords, channels, etc., which were fine all along and didn't cause the problem. So whatever they broke also exposed a problem in their configuration restore process.
I decided not to do the factory reset just now. Not only do I not want to re-enter everything, I don't want to go back to the original firmware version. I'm assuming that if I do the reset, re-enter all of my configuration, and then upgrade the firmware to the latest version, I'll be right back to the problem I was having. As it is now I have one working 2.4 GHz network (guest) and working 5G networks, so I would like to avoid going back to an earlier firware level where I had nothing but trouble with my router-attached hard drive. It has finally become reliable with later firmware upgrades. So I'm going to hang on for a while and see if Netgear owns up to the problem and issues a new firmware level with a fix, or at least assures us that doing a factory reset and then upgrading to a new level won't break the 2.4 GHz network again. Are you out there Netgear? Show yourself!
This is an extremely long thread. Is there a solution ? What is the solution?
I'm having this issue also. Had no problems for about 16 months with this router, now the 2.4GHz network drops. All the 5GHz are working. What is the answer?
How many times do you have to get burned making hasty f/w update. Who says newer f/w is always better. Did you read the release note B4 updating? Why? you ask? f/w is modular in nature like any other softwares. Often one person does not write whole f/w modules. Kernel is a Linux kernel and it has to work in harmony with all the various modules. Wireless driver is from Broadcom. or Qaulcomm If one part of module is modified by it's original author to improve or fix a bug,etc. he is only thinking his module. But many times it affects other modules causing trouble making it worse than previous version. Numerous beta testing can't cover all the possible operating condition. So if you must update f/w as soon as newer version shows up, test your patience, wait a while until it's proven in the real world.
In my working days I saw a software package which was producing fault condition when every 25K times it is used. It took a while to realize it and another while to correct the bug. Remeber old saying,
'Don't mess with someting not broken' When you get into trouble you should be able to get out of it.
No plan B?
or so used. Took a while to see it happening and took another while to fix the problem. Please, don't be so anxious to try newer f/w when your box is working OK.
