Firmware V9.10.4.1_1.1.17 killed satellites

Straq Thanks for the reply and info. I can't do all that right now as others in the house need the internet to work right now. 

I'd also rather not fully reset my main router as I have a lot of stuff dialed in nicely. I might try manually rolling back to the last official version and see what happens.

Again, everything has been working perfectly the last few months with this setup even through a few software updates but the update from today is a problem. 

The RBS only need to be reset, not the RBR. Resetting the RBS would not bother the router.

Well, I rolled the main router back to RBE971-V9.10.2.3_1.1.13 which was actually pretty easy and smooth and then once it rebooted it immediately recognized my two satellites and started optimizing them.

The weird part is that I had removed them from my system and also held down the factory reset button on them both, especially one of them numerous times.

Anyway, I'm going to leave it be overnight and then be more careful about doing this new update but I think I can safely say that something about today's firmware release definitely borked my satellites. 

FWIW, this is what I have going on right now. It looks suspect but it at least works again:

interesting, the RBS updated to v.4.1 already. You can update the RBR and after all should work.

What's crazy is that when I just tried to update RBR to V9.10.4.1 the router worked but it said 0 of 2 satellites found and the 2 satellites were offline.

I just reverted RBR back again to V9.10.2.3 and the router and satellites all work.

Not ideal, but working. 

A factory reset on the RBS seems to be needed after the RBR is updated.

The thing is, I'm pretty sure I tried that after the first RBR update and the two RBS units would not appear or connect. 

With the power turned on the RBS, I used a paper clip to hold the RESET button down for a long time numerous times, power cycled it, etc. and it would not successfully connect to the RBR with the latest firmware update from yesterday. 

Am I missing something with that?

What's weirder is that after doing that and manually removing the two RBS units from my network, when I rolled back to the previous RBR firmware the two RBS units more or less automatically connected again and had the same name I had given them, and they work.

This makes me think maybe I didn't factory reset the RBS units but again, I don't know what else to do.

At this point, I may just wait for the next RBR update and see if it solves all this.

What I would do, Factory reset the RBS one at a time by pressing the reset button for 15 seconds then release. Watch the back Power LED and after it goes from AMBER to Green power OFF the RBS. 

Then update the RBR to v.4.1 using it's update all function. After it's updated and back to ready, use the ERASE button under Advanced tab/Administration/Backup to do a factory reset on the RBR. Let the RBR begin the reset however do not setup the RBR just yet, after the front LED begins to blink WHITE, turn ON the RBS and give about 5 minutes. The RBS should auto connect to the RBRs default SSID name and configuration here. Allow the RBS front LED to turn BLUE, when this happens, being the RBR setup routine using a web browser and PC. During the setup, it should try to connect to the RBS and should see both. Continue. I recommend not changing the SSID and PW during the setup routine, wait until thats finished then go in and change the SSID name and PW to what you need it to be. 

I've done this before with my 970 series and found this method works well to ensure the RBS connect to the RBR during a factory reset. 

I'd rather not have to redo my RBR since I have all devices named and other things set up. This is all kind of silly.

I tried again by updating the RBR to 4.1 and factory resetting the satellites and no matter what, the RBR will not see the RBS after the 4.1 update.

I once again downgraded the RBR to the previous firmware and both RBS units automatically reconnected without any effort.

I'm just going to wait and see if the next RBR firmware solves all this.

I don't have all day to mess around resetting it all again to maybe work.

It seems that NETGEAR really screwed the pooch on this latest update.

👍

Keep your system back on last official release then.

Hopefully next update will get your system right.

My system worked great on v.4.1.