NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Orbi Access Control Not Working Properly (since FW update?)
Since I got my Orbi RBK50 (RBR50 router with RBS50 satellite) well over a year ago, I've been using Access Control set to "Block all new devices from connecting" until I specifically approve. Last w...
Did you update FW and then continue? You may need to factory reset and setup from scratch as we've seen some updates cuase problems on exhisting systems then a reset is performed and setup from scratch and seem to correct the bad behavior.
FURRYe38 , manually restoring this configution from scratch would be a terrible mess. From rebuidling acccess lists, properly naming devices, restoring address reservations -- it would take a long time to get things back to where they were -- all to test a hypothesis. If I could save, and subsequenly restore, settings, to the same end, that would be acceptible. Requiring me to start again from scratch would be the last straw between me and Netgear (they have failed me several other times, including on other devices, lately -- causing me to question their commitment to quality).
Do you know if it is possible to reload the same version of the OS/firmware (perhaps that would clean out some cobwebs)? Would factory reset followed by restoration from a recent (known to be working) configuration backup be the equivalnet?
Thank you.
Stev3D wrote:
Would factory reset followed by restoration from a recent (known to be working) configuration backup be the equivalnet?
This is what people warn against. If you reload saved settings it can resurrect bugs.
Try it and see.
If bugs return you have answered your own question.
It should not be necessary to reset a device. Do it only if you see problems.
michaelkenward , you wrote:
> This is what people warn against. If you reload saved settings it can resurrect bugs.
This is a recent issue, and I have configuration files going back to my beginning with the Orbi (June 2017), and the second most recent one is form March 29 — before this problem began. So, assuming my other, less-nuclear fix doesn’t work, I have a backup from when things were known to be working well.
I’ll post the outcome to this thread as soon as implement something (won’t be today).
