NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Orbi Satellite does not see Wired device
I'm connecting a wired Ethernet RTU to teh RBR50 Satellite and when configured for DHCP it is not "seen". If I configure the RTU device with a static IP - it is seen and connects perfectly. Why ...
The Ethernet RTU is produced by Eybond: http://www.eybond.com/page193?_l=en#bb
Again it works with other routers in DHCP mode and works fine with a static IP - just doesn't seem to accept DHCP from the Orbi RBR50 (main or satellite). Access Control is disabled. Since it seems no IP is assigned, "arp -p" does not see the device either (not unexpected).
Any further diagnostic suggestions welcomed!
So with the RTU connected to the back of the RBR, reboot the RBR or power OFF the RBR for 30 seconds then back on.
Once the RBR is back to ready, check the RBRs web page to see if the device appears in the conneccted clients list.
Ok - (ashamed I didn't think of the old standard 'reboot/power-cycle') - 1st tried wired connectivity to the RBS50 (no-go) then relocated to the RBR50 - also a no-go. ...and no show on an "arp -a".
What FW version are you using on the Orbi?
Sounds like this device doesn't like the Orbi DCHP or vs versa. Something to contact NG support about.
It's version: V2.5.1.16.
...was hoping one of you 'guru's out there would have a means to identify/isolate who's not behaving.
Appreciate all your input...