NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Laptop and PC refuse to connect to satellite, but can connect to Router -- advice?
Hi All, I have a very frustrating experience with one of 2 RBS850 Satellites. The Router reports the connection to both are good, most devices appear to connect to either satellite, and also to ...
Hi Mikey94025, and Community,
My issue is resolved!! I wanted to share details to help others who may have the same issue.
Summary: IF you have a device connected to a satellite via WiFI AND wired ethernet connection, it will cause the other satellite on your network to misbehave (they provide good WiFi connection, but cannot pass traffic to the Router).
Solution: Disconnect the ethernet cable
In my case my MacBook Pro, was connected via WiFi, and also used an eithernet connection via a docking station when it was at my main desk. This is why:-
- I could never replicate the issue on my MacBook, as I disconnected it from the docking station to go to the misbehaving satellite
- Swapping the satellites never helped, nor rebooting, nor resetting, nor repositioning the satellites etc etc. The "good" satellite was alway the one with my MacBook pro connected and the "bad" satellite was the other one
It took me ages to find the issue, and it only struck me as I was trying to understand what was different between my 2 satellites. I spent ages with support, who suggested I try many things, but all those failed, until I discovered this. (I have asked the support team to flag the issue with their developers.)
Mikey94025, maybe this is what is causing your issue?
Kind regards, TackMan
So this one device was connect to the RBS via wireless and ethernet at the same time?
TackMan wrote:
My issue is resolved!! I wanted to share details to help others who may have the same issue.
Summary: IF you have a device connected to a satellite via WiFI AND wired ethernet connection, it will cause the other satellite on your network to misbehave (they provide good WiFi connection, but cannot pass traffic to the Router).
Solution: Disconnect the ethernet cable
In my case my MacBook Pro, was connected via WiFi, and also used an eithernet connection via a docking station when it was at my main desk. This is why:-
- I could never replicate the issue on my MacBook, as I disconnected it from the docking station to go to the misbehaving satellite
- Swapping the satellites never helped, nor rebooting, nor resetting, nor repositioning the satellites etc etc. The "good" satellite was alway the one with my MacBook pro connected and the "bad" satellite was the other one
It took me ages to find the issue, and it only struck me as I was trying to understand what was different between my 2 satellites. I spent ages with support, who suggested I try many things, but all those failed, until I discovered this. (I have asked the support team to flag the issue with their developers.)
Mikey94025, maybe this is what is causing your issue?
Kind regards, TackMan
Hi FURRYe38,
Yes, this is a fairly standard thing to do on a Mac. Mac OS supports it really well.
Kind regards,
Peter
Well actually networking standards is to only have 1 connection per device. I've always used 1 connected on my Macs at a time. Not both.
Possible problem in that either Mac is causing problems with both connections being connected at the same time or Orbi doesn't support having two connections to 1 device at the same time.
FURRYe38 wrote:Well actually networking standards is to only have 1 connection per device. I've always used 1 connected on my Macs at a time. Not both.
Possible problem in that either Mac is causing problems with both connections being connected at the same time or Orbi doesn't support having two connections to 1 device at the same time.
Right, having two physical connections to a device is really bad, it can cause really odd problems with ARP address resolution on the local network and some services can get really confused by it.
NFS, for example (and possibly other network file systems), gets really confused by responses coming in on a different network interface to the one the it originated on.
