NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
RBR20 Ethernet Unidentified Network
Hi Have plugged in an ethernet cable into the Router and am getting an Unidentified Network. Tried all the regular troubleshooting. Looks like maybe the DHCP isn't working on the router? In...
Typical reason for the DHCP server not assigning an IP address is either security or the DHCP pool is full (no or IP addresses available, or all IP addresses reserved to some defined MAC addresses).
Have an eye on the ADVANCED > Security > Access Control settings, like Block all new devices from connecting. With this setting, if you buy a new device, before it can access your network, you must enter its MAC address for an Ethernet connection and its MAC address for a WiFi connection in the allowed list. Then look here View list of blocked devices not currently connected to the network
On the DHCP, it's unlikely the DHCP server is disabled, as your wireless devices get addresses assigned. On the LAN settings, check the DHCP Server Start and End IP addresses - if this range is to small there are no free IP addresses to be assigned.
Modern computers automatically fall-back to ZeroConfig (169.254.x.x/16) addresses if a network link (Ethernet or WiFi) is up, no static IP is configured, and no IP config is assigned by DHCP. Nothing odd at this point at least.
Thx for the reply. Had already checked a few of those things.
The DHCP pool isn't full, the router is ticked for "Use Router as DHCP Server" and starts from 192.168.1.2 and ends 192.168.1.254
Device isn't blocked, its status is allowed. New devices are allowed to connect.
My take is there is something wrong with the ethernet driver in the PC. The WiFi adapter did get an IP address using DHCP. That indicates that the Orbi DHCP process is working. The PC may think it has sent a DHCP request, but has not actually done so.
It might be worth reloading the ethernet driver.
My own approach would be to use Wireshark to capture traffic through the ethernet connection and display the dhcp packets.
Never used Wireshark. Im decent at troubleshooting PC problems but nowhere near an expert.
It might not be worth it anyways as its probably not that - I installed a new PCIE NIC and tried that. Exactly the same issue as the mobo network -
Even tried setting my TCP/IPv4 manually with -
IP 192.168.1.111 - chose an address that wasn't assigned yet
Subnet 255.255.255.0
Gateway 192.168.1.1
DNS addresses I put in from my ISP.
That changes the IP in the router attached devices but still in Windows it gives me an Unidentified Network.
