NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
ORBI RBR50 Serving up 169 IP addresses for wired devices
My ORBI RBR50 is serving up 169 IP addresses for wired devices. Wireless connections are being served 192 addresses. I need the wired devices on the 192 subnet. Any help appreciated
169 means the wire connected device is not getting anything from the RBR. Maybe a bad LAN port on deivce, bad cable or incorrect configuration on the device.
Do ALL LAN devices not get a 192. from the RBR?
What Firmware version is currently loaded?
Have you pulled the power cord from the back of the RBR for 30 seconds then plug it back on with 1 wired PC connected to the back for the RBR? Disconnect ALL wired devices from the RBR accept for the 1 wired PC.
Ensure the wired PCs ethernet adapter is set for auto obtain IP addressing.
Ensure your using good quality LAN cables, CAT6 is recommended.
Try a factory reset on the RBR.
I swapped one router out for the Orbi. I'm not concerned about the cables etc.
All wired devices get a 169 address.
christophermc wrote:I swapped one router out for the Orbi. I'm not concerned about the cables etc.
All wired devices get a 169 address.
Can you describe more about this "swap"?
Both WiFi and wired devices were connected to a previous router and worked correctly, and the only thing that changed is that first router was replaced by an Orbi router?
On the Orbi web interface, Advanced Tab, Setup, LAN Setup menu what does it show for the DHCP Range (Starting and Ending IP addresses)?
These 169 IP addresses show up in the Orbi Attached Devices page?
> [...] I'm not concerned about the cables etc.
People who can't see them might be less confident than you. How much
"etc" is there? Are these (unspecified) "devices" connected directly to
LAN Ethernet ports on the RBR50, or what? What, exactly, is connected
to what, exactly? (Hint: If a device has different types of ports,
then "connected to device" is not enough detail.)> All wired devices get a 169 address.
As explained above, that means that they're not getting an address
from the router (DHCP server). Typical causes: Bad Ethernet ports; bad
cables. That is, no actual connection.Is there any evidence that these (unspecified) "devices" have a good
physical link to the router? Someone should have some LEDs or enough
software to characterize that connection.I had an issue with my Wiindows 10 laptop involving DHCP (since resolved)*. When it would wake up from sleep, there would be no ethernet connection until I opened the Network Troubleshooter or diabled/enabled the ethernet adapter.
Wondering what was going on, I captured the LAN traffic between the PC and Orbi. Using Wireshark to display the dhcp packets, it became obvious that the PC was broadcasting a request for IIP, the Orbi was answering as it should, and the PC was broadcasting again. NEVER accepting the offered IP. The PC was not following the DHCP protocol. The Orbi was.
Capturing and anlyzing the LAN packets is not trivial, but is the only I can think of to establish that the 168 IP address does NOT come from the Orbi.
* There have been a ton of Windows software updates since that time and the problem has not come back.
