NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
Problems with recent firmware update
Since updating three days ago, nothing can connect to this thing except through guest access. SSID, security, and passwords are all the same, but I am having to change everyones device to access thr...
The latest R7000 firmware has been the talk of the forum for weeks.
Try a factory reset and reconfigure the settings by hand. Do not restore settings from a backup file. Turn off the new Arlo setting. If things don't recover, then downgrade the firmware. You can obtain firmware from downloadcenter.netgear.com.
I have been busy and finally got around to the fix - because I had too, nothing was working at home. Downgraded the firmware, did the factory reset and reconfigured the router. The firmware update is inexcusable. Obviously was not tested. It took down my home network, printer would not work, no one could sign on to the woreless network except as a guest. No one could print wirelessly. I am the "netowrk adminstrator" at home - nobody wants to be that guy. Thermostats went down, ipad, kindle, laptops, tv, blu ray players - goodbye netflix and amazon prime. What a mess we have made for ourselves when everything connects. Left Cisco - linksys for NetGear. Next router will be back to Cisco. I don't want to be an IT guy!
I had the same problem used the same solution and everything is back as it should be. I could not agree more with the conclusion as to the lack of care exhibited in pushing out this firmware upgrade without proper testing or support after it clearly failed many people.
Netgear definitely should be held accountable for putting out bad firmware. But short of NASA-style development and testing (1 bug in 420,000 lines of code for the space shuttle vs hundreds to thousands of bugs in typical commercial code), people should understand that bad firmware gets out. It is exceedingly expensive to test code 100% (100% statement coverage does not equate to 100% path coverage).
What is more disappointing is that Netgear took so long to acknowledge that the firmware was bad and pull it. The engineers in the company should be empowered to pull releases. Many years ago in another company, I once put in a request to stop a big software release and ended up in the office of the VP of Engineering. I don't remember if it was my bug or someone else's, but it didn't matter. After I explained the severity of the issue, he gratefully thanked me. Hopefully the culture at Netgear isn't one where speaking up and/or taking action is frowned upon.