NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
RBR40 ORBI assigning IP out of range!
ORBI RBR40 is behaving very oddly. IP Range is set to 192.168.0.x I lost internet to my wired ethernet PC. But was able to successfully connect same PC via WiFi. Checked IP Table and found...
RedCab wrote:ORBI RBR40 is behaving very oddly.
IP Range is set to 192.168.0.x
I lost internet to my wired ethernet PC. But was able to successfully connect same PC via WiFi.
Checked IP Table and found PC (ethernet) address was 169.254.118.245 !!! No wonder no internet via ethernet.
Using Win10, I checked network connections and Ethernet shows "could not identify network" during those down times. Not surprising.
Wish I had a solution. 169.254.x.x is one of those "auto addresses" that a computer assigns when DHCP fails to supply an IP address. https://en.wikipedia.org/wiki/Link-local_address
My Windows 10 computer also does this with the ethernet adapter (says "unknown network"). I either use the network "troubleshooter" or use the network control panel to "disable" and then "enable" the ethernet adapter. Tedious.
I am certain there is a setting (somewhere) that makes this problem go away, but have not yet found it. (I just disable/enable and go on.)
Interesting...
This morning I restarted the router and both satelites ...and for the moment everything is operating fine. Let's see if it stays stable.
The PC now has both wired ethernet and wifi turned on... I'll keep an eye out today to see if that ethernet connection bugs out, in which case my suspicion is that something has gone wrong with the Orbi's ethernet outputs.
I rolled back firmware to V2.6.1.36 just in case.
If I catch the Orbi misbehaving (ie, not assigning proper IP addresses to hardwired devices) would you say that it's a firmware or a hardware issue?
RedCab wrote:If I catch the Orbi misbehaving (ie, not assigning proper IP addresses to hardwired devices) would you say that it's a firmware or a hardware issue?
Sorry I was not clear. The Orbi did not "assign" that private IP to the ethernet port. The computer made up that IP itself because it did not get an IP from the Orbi. The problem is entirely within the Windows 10 computer. (My Windows 10 laptop started doing that and I am embarassed that thus far I have not resolved the issue.)
If every device but one is working correctly, then there must be a problem with the router? - NOT.
I wasn't clear either, sorry.
I wrote about the problem with the PC as example because it provided the most diagnostic info.
The problem also is happening (when it does happen) with other devices downstream from the Orbi's ethernet outputs. For example one of those outputs goes to a switch which supplies my video streaming devices. All of them were unable to reach internet while that issue with the PC was going on.
SO... it's on the Orbi side of things, right? Would you agree the Orbi isn't registering hardwired ethernet connections, ie, not assigning IP address to those, in turn causing "no internet" at those various devices?
The wifi connections off the Orbi appear to be uneffected, at least I haven't observed an issue with those (yet).