I recently purchased a 750 system with a router and two satellites. We have a very long house. The internet cable enters at one end of the house. That's where the RBR750 is located. The first RBS750 is located about 25 feet away from the router. The next RBS750 is located about 30 feet past the first. The three units are strung out in almost a perfectly strait line. The problem that I am having is that the furthest satellite is connecting to the directly to the router and has a slow connection. In my mind it should be connecting the other satellite, since it is closer to the router and has a good connection. Is there a way to force the furthest satellite to connect to the closer satellite? Or am I misunderstanding the mesh concept?
Might move the closer RBS to the RBR a bit farther away from the RBR. 30 feet distance is starting distance.
Try powering OFF both RBS, Power ON the closer RBS to the RBR and let it sync. Then power ON the farther RBS and see if it will sync to the middle RBS.
In my mind it should be connecting the other satellite, since it is closer to the router and has a good connection. Is there a way to force the furthest satellite to connect to the closer satellite?
Your impression is correct, and what most users would assume should happen. Alas, the Orbi system has no mechanism to force satellite connections (or user device connections, either). @FURRYe38 has a good suggestion (powering the far away satellite off and then back on again). I have done experiments observing how user WiFi devices connect when Orbi systems are powered on that suggest that some devices will connect to the first Orbi unit they "see" and may (or may not) change to a stronger signal later.
Netgear does not provide documentation on how the router to satellite process works. It is obvious that connecting a satellite with an Ethernet cable will cause the connection to switch from WiFi to Ethernet (and removing the Ethernet cable will cause it to switch back to WiFi). The transition does not happen instantly, however, which leads to a conclusion that there must be some process which looks for what connections are available on some sort of schedule. Whether there is a similar process which compares signal strength of potential WiFi connections from time-to-time is not clear.
The very first Orbi system in 2016 had a setting for Daisy Chain, with the default being "enabled". That option remains today in the very latest firmware. When AX systems were introduced, the option was eliminated and the Daisy Chain feature is permanently enabled.
One of the most attractive features of mesh WiFi systems is that they do not require physical wiring between units. Connecting satellites to the router with Ethernet cable provides a faster connection and higher performance. If there is existing cable wiring in the house, a pair of Multimedia over CoAx (MoCA) adapters can create a high speed link. If two units happen to be on the same electrical circuit, a pair of Powerline adapters can provide a good link. (Powerline struggles going through circuit breakers.)
V7.2.6.31_5.0.24 I think this is the most current version.
Your suggestion worked, but not in the way I expected. I moved the closer RBS750 about 5 feet farther from the router, which put in the same room as the further RBS750. I unplugged the further and plugged it back in after the nearer booted up. The nearer RBS750 showed a "poor" connection to the router (in the admin app - which I have to say is handier than the Orbi app.). But the further connected to yet another RBS750 that I didn't previously mention. At that time I had not added it to the system. The third RBS750 is connected to the router via wire t get it configured. Its in the same room as the router, but about 7 feet lower. That satellite is what the further connected to with a "good" connection. So weird. But there is a lot of ductwork and pipes in the basement ceiling. I think the angle of the backhaul transmission from the further satellite to the 3rd satellite gets under the obstacles. I have some placement experimentation to do.
