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!
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.
1.0.5.48 has an issue with port forwarding that's why 1.0.6.28 was released, but you had to manually reset the router by holding in the reset button for twenty seconds to clear all port forwarding info and reset the router. If you do that with 1.0.6.40 that should also work. Hopefully there will be a full release firmware soon. Do not use back up settings, they can contain settings from previous firmware versions that do not apply to the latest versions and once again cause corruption. Also always reset the router with firmware updates, I can not stress this enough, lots of code changes happen and a hard reset and manual install of your settings is really the only way to make sure things work as they should. Also some peoples issues are hardware related, and they blame the firmware because when re-writing any devices firmware if you have hardware issues thats when they will really show up.
Thanks Killhippie,
Yes.....that is why I had a problem with my port forwarding. When I did a hard reset and rolled back the firmware I did a restore from my saved backup. When I went to the port forwarding page they were all there but not functioning. That is when I manually deleted and re-entered them to fix my problem. Since everything is working right now I will jsut wait until I get the go ahead with a proven and tested new firmware release. At that time I will enter everything as you suggested manually.
Thanks again for your help.
Jim
47672
85763
As others have mentioned, I too had saved a copy of my old settings in to a back-up along with my previous firmware version in the event that I had to revert back to my old configuration. A question that I have for Netgear is whether or not the entire non-volatile area used to hold configuration settings is backed up when you execute the back-up and save the file to your hard drive or not. In addition, if you load your back-up file in to the router, is the entire non-volatile area erased overwritten? This is an important question that I would like to have answer to. If only partial data is overwritten when a back settings are restored then it makes sense to me that you would need to perform the "factory reset" to wipe out the NV area. If the restore of the back-up settings is only partial, this is a bad concept in my opinion! The lack of an erasure of the NV area seems to be the situation and that is why these factory resets are required whenever versions of firmware are changed (with or without backup settings).
I would also like to sharply disagree with the idea that Netgear is pushing out firmware updates from within the browser management system that require a factory update. I would suggest, and I think that most would agree that without notification to the user, firmware updates that require a full-blown factory reset, and the requirement of abandoning all previously saved configuration settings should not be made through this interface unless you have the ability to warn the user that they must perform a factory reset and abandon their back-up settings. I am guessing that many people do not even back up their settings every time they perform the firmware update, and rightfully assuming that an incompatibility would not be introduced in this way!
If you cannot warn the user about what is going to be required of them if they click the on the auto-update link then please do not do it. Also please do not insult my intelligence by stating that there was a mention of factory reset requirement in some release notes that I was never presented with during the update process. I do not have the time or inclination to read these release notes for features that I will not use.
I would also like to chime in on the comment about new features being enabled automatically on a firmware update. This is irrespective of all of the other firmware issues going on. When I did an upgrade to one of the newer versions of firmware, I noticed that the port forwarding for my website (one of the most typical uses for ANY router) could not be enabled because some new feature had been enabled and was using port 80. I had to hunt around in the settings to find this new service and disable it before I could re-enable the port forwarding for my website. This was a time consuming and frustrating process as I do not have time to learn about new features that I will never use that have taking over resources used in the most typical use case that becomes disabled. When I discovered what happened I have to say that I found that irritating to say the least. What the <blank> comes to mind.
While someone had argued that if new features are disabled then people will probably never use them. I would sharply disagree that just because you want to role out some new feature that you will make the decision to take my time to figure out why my system no longer works, placing the new feature above my customizations. To be honest, I do not care about this new feature and I sure as heck do not want it taking over port 80!
To summarize, in the future please do not enable new features that A) Could present a possible security risk that should be enabled by the end user willing to take that risk not knowing a thing about it. B) Please do not role out new features that take critical resources away from the mostly commonly used use cases!