NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
walkerx
Feb 24, 2019Guide
Orbi Satellites connection
I have my orbi satellites connected via ethernet, yet one always wants to connect wirelessly.
will there be a reason why it wants to connect wirelessly even though it should be connecting via ethernet for the backhaul.
I've already contacted amazon and they are sending out a replacement system
19 Replies
- ekhalilMaster
Reasons can be one of the following:
- Bad connectivity caused by bad cable or switch in between
- You have a device or devices connected to the Satellite's LAN that causes loops on the Satellite and will cause Orbi to disable the LAN ports. Please check if you have such devices that can have both Ethernet and wifi connections.
- Becaue of a bug in current software (2.2.1.210) the loops can also be cause by enabling Daisy Chain while having Ethernet backhaul. Please make sure that Daisy Chain is disabled when you have Ethernet backhaul.
- walkerxGuide
ekhalil wrote:
Reasons can be one of the following:
- Bad connectivity caused by bad cable or switch in between
- You have a device or devices connected to the Satellite's LAN that causes loops on the Satellite and will cause Orbi to disable the LAN ports. Please check if you have such devices that can have both Ethernet and wifi connections.
- Becaue of a bug in current software (2.2.1.210) the loops can also be cause by enabling Daisy Chain while having Ethernet backhaul. Please make sure that Daisy Chain is disabled when you have Ethernet backhaul.
1) Tested in the spot where the other satellite (Sat2) is and get the same under the main orbi it shows that its (Sat1) connected via 5Ghz and backhaul is good, place my other satellite(Sat2) back in position and its connected via ethernet and backhaul is good. If I then place Sat2 where Sat1 is usually situated it is connected via ethernet and backhaul is good. This now makes me wonder if there is a fault with Sat1.
2) The only connection on the satellites is the cable for the backhaul
3) Checked the Daisy Chain setting on main Orbi and this is unticked
I have my Orbi's set outside of the DHCP range with their IP's reserved for all 3 units. But I have also noticed recently that if I disconnect the wan of my router (not the Orbi) my wifi goes down, which is also odd, as should still be able to access devices on my internal network
- ekhalilMaster
walkerx wrote:1) Tested in the spot where the other satellite (Sat2) is and get the same under the main orbi it shows that its (Sat1) connected via 5Ghz and backhaul is good, place my other satellite(Sat2) back in position and its connected via ethernet and backhaul is good. If I then place Sat2 where Sat1 is usually situated it is connected via ethernet and backhaul is good. This now makes me wonder if there is a fault with Sat1.
.........
There can be an issue with your Sat1.
- Have you tried to factory reset the Satellite?
- Have you tried to connect the Ethernet backhaul to another LAN port on the Satellite?
walkerx wrote:...........
I have my Orbi's set outside of the DHCP range with their IP's reserved for all 3 units. But I have also noticed recently that if I disconnect the wan of my router (not the Orbi) my wifi goes down, which is also odd, as should still be able to access devices on my internal network
The IP address reservation should be from within the Orbi DHCP range NOT outside!
If you get wifi issues when you disconnect the WAN port this tells that your ISP router has also control over routing in your network or is also proving DHCP addressing. Do you have Orbi in Router Mode? If yes is your ISP router bridged? What is the model of your ISP router?
- FURRYe38Guru - Experienced User
What is the Mfr and model# of the ethernet switch if one is in the configuration.
Is Daisy Chain disabled?
Do the following in the same room as the Orbi base router:
When connecting the satellites via wired back haul, connect 1 satellite first via wireless, then once you get the BLUE led on top of the satellite, connect the LAN cable between the satellite and Orbi router. Wait for up to 5 minutes for the top LED to turn BLUE.
Don't do any IP address reservation. Just see if the satellite gets to this point and check the status. Sometimes the status in the UI takes a bit to refresh.
For normal IP address reservations, typically these are done with IN the default IP address pool. Static IP addresses are done outside of the default IP address pool which are done ON devices, not on the router.
walkerx wrote:
I have my orbi satellites connected via ethernet, yet one always wants to connect wirelessly.
will there be a reason why it wants to connect wirelessly even though it should be connecting via ethernet for the backhaul.
- walkerxGuide
FURRYe38 wrote:
What is the Mfr and model# of the ethernet switch if one is in the configuration.
Is Daisy Chain disabled?
Do the following in the same room as the Orbi base router:
When connecting the satellites via wired back haul, connect 1 satellite first via wireless, then once you get the BLUE led on top of the satellite, connect the LAN cable between the satellite and Orbi router. Wait for up to 5 minutes for the top LED to turn BLUE.
Don't do any IP address reservation. Just see if the satellite gets to this point and check the status. Sometimes the status in the UI takes a bit to refresh.
For normal IP address reservations, typically these are done with IN the default IP address pool. Static IP addresses are done outside of the default IP address pool which are done ON devices, not on the router.
walkerx wrote:
I have my orbi satellites connected via ethernet, yet one always wants to connect wirelessly.
will there be a reason why it wants to connect wirelessly even though it should be connecting via ethernet for the backhaul.
One is a HP ProCurve 1810G - 8 GE and the other is a Zyxel GS1900-24E, both currently in unmanaged mode, so nothing to with vlans or managed configuration.
As per my post above daisy chain is disabled
Amazon have offered to replace, so I'm not messing about much more with this especially as the other satellite is working fine, its only 1 satellite that is not
Previously IP address reservation was done outside of the dhcp range, not inside, even microsoft only changed it for their products when they done server 2008 r2, prior to that they used outside of the range for reservations. You will also find a lot of companies still work that way where the reserved ip's are out of the dhcp range.
- FURRYe38Guru - Experienced User
Your two switches are non Un-Manged, they are Managed:
https://www.zyxel.com/support/DownloadLandingSR.shtml?c=gb&l=en&kbid=M-01602&md=GS1900-24E
https://support.hpe.com/hpsc/doc/public/display?docId=emr_na-c02563753
If you can connect the satellite direct with the Orbi router to test to see if the satellite connects via wired cable and remains. Then you can see if the satellite is good. If it does connect and remain, then the issue will be how it's connected thru these managed switches.
Any and ALL IGMP Protocols should be disabled on these switches as this seems to cause problems with Orbi and wired connections with satellites.
Maybe however for most home networking environments, reserved is within and static are outside only. Keeps things simple and this works.Any other configurations may work or cause problems. However lets keep things simple first. Anything after that, will be up to you.
walkerx wrote:
FURRYe38 wrote:
What is the Mfr and model# of the ethernet switch if one is in the configuration.
Is Daisy Chain disabled?
Do the following in the same room as the Orbi base router:
When connecting the satellites via wired back haul, connect 1 satellite first via wireless, then once you get the BLUE led on top of the satellite, connect the LAN cable between the satellite and Orbi router. Wait for up to 5 minutes for the top LED to turn BLUE.
Don't do any IP address reservation. Just see if the satellite gets to this point and check the status. Sometimes the status in the UI takes a bit to refresh.
For normal IP address reservations, typically these are done with IN the default IP address pool. Static IP addresses are done outside of the default IP address pool which are done ON devices, not on the router.
walkerx wrote:
I have my orbi satellites connected via ethernet, yet one always wants to connect wirelessly.
will there be a reason why it wants to connect wirelessly even though it should be connecting via ethernet for the backhaul.
One is a HP ProCurve 1810G - 8 GE and the other is a Zyxel GS1900-24E, both currently in unmanaged mode, so nothing to with vlans or managed configuration.
As per my post above daisy chain is disabled
Amazon have offered to replace, so I'm not messing about much more with this especially as the other satellite is working fine, its only 1 satellite that is not
Previously IP address reservation was done outside of the dhcp range, not inside, even microsoft only changed it for their products when they done server 2008 r2, prior to that they used outside of the range for reservations. You will also find a lot of companies still work that way where the reserved ip's are out of the dhcp range.
- FURRYe38Guru - Experienced User
Probably need to get the system RMAd then. Also having it not show as working in the app, probably is a indication that the satellite is bad as your can't seem to get the app to work right with it in your other thread.
Good Luck.