This topic has been marked solved and closed to new posts due to inactivity. We hope you'll join the conversation by posting to an open topic or starting a new one.
For those of you who were in the 2nd batch (Anyone before my previous post), the fix has been deployed. Please reboot your routers and let me know if you experience any issues.
Anyone after my last update I have submitted your serial numbers and am awaiting confirmation that the fix has been deployed.
I am still waiting for advice on the next steps from the team regarding the reported issues reported after the fix was deployed. I am hoping to get more information later tonight.
@FURRYe38 and @ChristineT , I believe the question that @_Mike asked is the one that I too have. Namely, if NG is successful in engineering a fix that will NOT require a factory reset and assuming that the fix will be to the RBR's directly, how do you think it will be applied? If it's not a push update to the router (i.e. the equivalent of an auto-update), how would the fix be administered? Using the Orbi app someway?
I know the fix does not yet exist and there may be no way to know the method that might be used, but just trying to understand how we'll regain functionality (other than a factory reset). Further, how will we be notified what to do?
>>but just trying to understand how we'll regain functionality (other than a factory reset)
I had this same question. Level 2 support said they would call and walk users through the process. I'm too far gone and had the reset but I am super curious ..
Thank you for your inquiry. We have had a good number of people report that the fix being deployed (similar to a firmware push) is successful in recovering the ability to access the Router settings. Once we are confident that the fix resolves the issue and does not introduce any other issues we will deploy it to all the impacted users.
Thanks Christine, that resolved my issue. One thing to note, it takes about 3-4 mins after the router has come back online for the mobile app to re-register and connect. Something to note for others that are testing.
I also had to reboot one more time with the satellite nodes, to get my device names to come back and mesh satellites (backhaul) to synch up. All good now.
I have been notified that this round of serial numbers has had the fix deployed and request that the folks that recently provided their serial numbers reboot their systems at this time. Please note, that we have seen it can take 5 minutes after a reboot for the system to be fully operational. In addition, if device names are showing as NA in the Connected Devices list a second reboot resolves this issue.
Please also verify if your Armor and Smart Parental Controls services are active and working as expected.
Yes @tiburon7227 , I would do that on your mesh satellites as well if you have any. I had do this two full cycles for everything to refresh and synch back up.
This fix will be pushed in the very near future however we are still taking serial numbers for those who want the fix as soon as possible. Please send me a private message with your model and serial number and I'll let you know when the fix has been pushed.
Once we have deployed the fix to the general audience I'll post another note here and mark it as the solution. You can also check status.netgear.com/orbi for updates.
Hi Christine ! Thanks so much for helping us, it is SUPER appreciated.
I had to do a super / 30-30-30 reset early this afternoon. Didn't get too far with support but after a few tries on my own I finally got up back and running. Had to build my network and connect devices again but it was working.
I sent my SN and I believe mine was in the second round of pushes / updates. Since then my orbi restarts about every minute or so. Devices loose their connection. Get an unhappy face at orbilogin Net and an "error. Not connected" message in red under the internet status
