Netgear Orbi RBK53 Wired 2.1.4.16, too many issues!

Daisy Chaing is for wireless connected satellites, two or more. I presume if your using wireld backhaul, this option needs to be disabled. I presume fast roaming may be a push however this option depends on how wireless clients handle roaming with the Orbi. MIMO is for devices that support MIMO. So if you don't have any or maybe just one, I'd disable MIMO. 

How long did you want after you connected the LAN cable to the satellite? You need 5 minutes to wait for the top led to turn on BLUE. Then the network should settle down. 

https://community.netgear.com/t5/Orbi/OrbiOS-2-1-4-10-kills-Internet-access-if-you-use-Ethernet-back/m-p/1603922/highlight/true#M35521

Aother way I would connect satellites via wired backhaul is to disconnect ALL other wired and network devices from the ORbi. Then connect the lan cable to the satellites, 1 at a time, waiting up to 5 minutes for the top led to turn on BLUE. Once you have all the satellites connected and tested. Then re-connect all the rest of the devices. 

I believe sometimes the Orbi router may have problems with DHCP and IP address conflicts during this process when a wired satelllite is connected. Saw behavior on my satellite where for some reason, it was in conflict with my cell phone microcell. I had to turn OFF the microcell, get the satellite reconnected, gave it a IP reservattion on the router, then turn on my microcell then the system was ok. 

---

jjvoliver wrote:

Well,

 

I accept your solution because, well, it IS the solution to have the mesh system working now.

 

However, does anyone know anything about why the options (daisy chain, MU-MIMO, beamforming, etc) seem to break this?

 

Also, is there anything from Netgear about an estimated time of resolution for the wired backhaul?

 

I've been searching all over and cannot find anything on these subjects, other than owners complaining about them.

 

Thank you.

---