NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
Trouble accessing local network devices from Orbi satellite connection
My problem: Unable to "see" a Mac Mini server on my local network when the client device is connected via Wifi to a satellite. If connected to the main router via Wifi or cable, it is fine. In a day to day scenario this surfaces itself as Plex not working in some rooms of the house, but OK in others.
My setup: RBR50 router in AP mode with 3 satellites, 2x RBS50 and 1x RBS20. My ISP's router (an Adtran) has no bridge mode, hence why the RBR50 is AP. The Mac Mini runs Plex and is connected via wire to the Adtran with a fixed IP.
Firmware: V2.7.3.22
How I tested:
Using my laptop (MacBook Pro) I turn Wifi on/off and connect to the RBS50 satellite. This is confirmed by checking the Orbi App to see what the laptop is connected to.
Using Plex Web App, try to view any content. The web app cannot locate the Plex Mac Mini server, saying it is offline.
Also I cannot ping the Mac Mini nor does the Share Screen option work from the laptop.
Now I move to another room where the RBR50 router is located and toggle the laptop's Wifi again.
I confirm that I am now connected to the RBR50 router using the Orbi App.
This time, Plex Web App works. So does ping. So does Screen Share.
I can repeat the test with my iPhone, iPad and Apple TV - they all cannot connect to the Mac Mini via a Satellite but can via the Router
Any device connected via cable, such as another computer in my office works fine.
Within Orbi, these are all enabled:
Fast Roaming
MU-MIMO
Beamforming
Daisy Chain
WMM
Does anyone know why this is happening?
Try it with nothing connected to the adtran router other than the orbi router.
If you're using a wired backhaul go
adtran---->orbi wan port----->switch/devices/satellites.
Because in ap mode, the adtran is managing the routing/dhcp/nat.
8 Replies
Try it with nothing connected to the adtran router other than the orbi router.
If you're using a wired backhaul go
adtran---->orbi wan port----->switch/devices/satellites.
Because in ap mode, the adtran is managing the routing/dhcp/nat.
It is using a wireless backhaul. Why would I need to unplug the other network cables from the Adtran?
It is now working!
The fix, as you suggested, was to run a Cat6 cable from the Mac Mini into one of the Orbi's ports directly, eventhough it is "only" in AP mode and the Adtran router is doing DHCP, etc.
The Orbi is, for some reason, blocking traffic from going "through" it from Wifi to something connected to it's ports indirectly, such as via Adtran router, to another device.
It so odd that this just started to happen, as my setup has been this way for over 6 months and was fine.
Thanks so much for helping.
Be sure to save off a back up configuration to file for safe keeping. Saves time if a reset is needed.
https://kb.netgear.com/000062080/How-do-I-back-up-the-configuration-settings-on-my-Orbi-WiFi-System
wilro15 wrote:- Any device connected via cable, such as another computer in my office works fine.
Interesting, so devices connected by wi-fi cannot talk to your Mac Mini but if connected by ethernet they can?
Are your satellites wired or wireless to the Orbi base?
When you ping, is it by DNS name or by IP address of the Mac Mini? If it is by DNS, also test if pinging by IP address works when wireless connected to the satellite.
Wifi only works if the device is connected to the RBR50 and the RBS20 (the smaller satellite). The two larger satellites, RBS50, do not work.
I am using a wireless backhaul. The ping is done by IP address, when it doesn't work I get a "request timed out" message in teminal.
Up until Dec 27th, it was working fine, then the issue started.
Its really strange!
