NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Updated to FW 1.1.6.122. Satellites now report no connected devices, and more issues. WTF?
Netgear MK63 system. FW just updated to 1.1.6.122. Sorry for my frustration but this mesh system is the biggest POS I've ever encountered. I updated the firmware because my Roku android app wou...
Revert your MS then MR back to v116 if your having problems with v122. v122 already has known problems and it's recommended to users to not use this version of FW.
FURRYe38 wrote:Revert your MS then MR back to v116 if your having problems with v122. v122 already has known problems and it's recommended to users to not use this version of FW.
Hi FURRYe38
Your suggestion should not even be an option. Why release v122 and/or keep it released as the current version when it has, and I quote "known problems and it's recommended to users to not use this version of FW" ? If Netgear are aware of this issue, it should be rectified as a matter of urgency and new FW released. Users should not have to rollback. I myself have been a lifelong user of Netgear products and the customer support from Netgear and their help pages is atrocious. A small example, search for MR60 on the support pages and it provides answers for Orbi, as far as I'm aware, the MR60 is not an Orbi product. Another support page suggests that the MR60 can support a maximum of 3 satellites with a maximum of 2 satellites in a daisy-chain, there is no option in the MR60 GUI to turn daisy-chain on/off so if it nativly works on a daisy-chain and cannot be changed, how can it support a maximum of 3 satellites?
I'm sorry for the rant but I think for the money that Netgear charge for their products, the FW should be bullet proof.
Rolling back is a short term solution while we wait for FW to be fixed. FW fixes do NOT happen over night and can take months. So best option is to roll back to what had worked before.
Otherwise, users can make contact with NG support and open a support ticket:
https://my.netgear.com/support/contact.aspx
This is beyond forum help and there is nothing else forum help and information can do to fix this.
Good Luck.
Same issue here... Couple comments.
1. I've had nothing but issues with updates for the last year. This release is the same...
2. Why in the hell would I have to do a full factory reset (and to what FW version) to fix this problem
3. Why was the firmware update hastily rolled out in the first place4. Where in the hell is my remote management, oh yeah, it was sneakily removed by Netgear over the holidays.
So... I can't remotely fix this, I can't login, and I have to factory reset my network to fix this. Yeah, this is the poorest example of device support and firmware versioning of any device I have ever worked with. POS!
justinpyle wrote:
Same issue here... Couple comments.
1. I've had nothing but issues with updates for the last year. This release is the same...
See this:
2. Why in the hell would I have to do a full factory reset (and to what FW version) to fix this problem. Valid troubleshooting step to make sure odd configurations or lingering prior FW code is removed.
3. Why was the firmware update hastily rolled out in the first place - We don't know this so don't ask.4. Where in the hell is my remote management, oh yeah, it was sneakily removed by Netgear over the holidays.
We believe for security reasons NG has been removing the web page based remote management features. Any remote management is now handled by limited use of the Nighthawk mobile application now. This is happening across all product lines. https://kb.netgear.com/000062097/Remote-Management-is-now-Anywhere-Access-in-the-Nighthawk-and-Orbi-apps
So... I can't remotely fix this, I can't login, and I have to factory reset my network to fix this. Yeah, this is the poorest example of device support and firmware versioning of any device I have ever worked with. POS!
I recommend reverting back to v116 on the MS first then MR lastly. Make contact with NG support if you continue to see problems. We've attempted to make NG aware of the issue seen with v122 so they know about this.
Good Luck.