Internet & Network / Ethernet
How to Fix Ethernet "Unidentified Network" in Windows
Quick answer
Unidentified network with a 169.254 address means Windows made up a local address because the router never offered one. Check the cable is in a LAN port, restart the router, then release/renew the address. If lights are off or Windows says the cable is unplugged, use [Ethernet not working](/guides/ethernet-not-working-windows) instead, that is a link problem, not DHCP.
Quick diagnosis
If several of these match what you see, you are in the right guide.
- Ethernet shows Unidentified network
- ipconfig shows an address starting with 169.254
- Link lights are on, but there is no internet
- Wi-Fi on the same router works
Possible causes
- The PC did not get a DHCP lease from the router
- A static IP leftover from an old office or lab
- The cable is in a dead LAN port or an ISP-only jack
- AP isolation or a guest VLAN that never hands an address
- A broken TCP/IP stack on this adapter
What you need
- Command Prompt or PowerShell
- Access to the router if you can
What this problem usually means
169.254.x.x is APIPA: Windows saying "I have a cable, nobody answered DHCP." That is different from no link (unplugged) and different from a valid LAN IP with no internet (routing/DNS).
Before you start
- Prefer another LAN port on the router, not the WAN/internet port.
- If you set a static IP years ago, write it down before switching back to automatic.
Quick fixes
1. Automatic IP, then renew
- Settings → Network & internet → Ethernet → the adapter → IP assignment → Edit → Automatic (DHCP).
- Open an admin terminal.
- Run ipconfig /release then ipconfig /renew.
- ipconfig: you want an address that matches your router (often 192.168.x.x or 10.x), not 169.254.
2. Restart the router after a port change
If the DHCP pool is exhausted or the port is wedged, a one-minute power cut on the router is more effective than a Windows network reset.
Step-by-step troubleshooting
Static leftovers
A leftover 192.168.0.50 on a 192.168.1.x home network looks "connected" and still unidentified or useless. Automatic DHCP is the home default unless you have a reason.
Same cable, another device
If another PC or a USB Ethernet adapter gets a real lease on this cable, the wall and router are fine, this PC's adapter or stack is the problem. If nothing gets a lease, the router DHCP or the cable path is the problem.
Network reset, later
Reset network settings if DHCP still fails after automatic IP and a router restart, and Wi-Fi is not your only remaining connection (reset forgets Wi-Fi too).
Do you have a 169.254 address?
Choose an answer. The next question appears below, no account or download required.
DHCP failed. Automatic IP, renew, router LAN port, then reset if needed.
You have a lease. Look at DNS and routing, no internet or change DNS. Unidentified can also be a public/private profile glitch; toggling the network profile in Settings is a minor test.
No link. Use the Ethernet not-working guide. This article will not help until lights come on.
How to know the problem is fixed
ipconfig shows a DHCP address and gateway. A website loads while Wi-Fi is off so you are not cheating with wireless.
If the problem continues
A USB Ethernet adapter that gets a lease when the onboard NIC does not points at the onboard port or its driver. Vendor Ethernet driver from the PC maker is legitimate; "LAN booster" is not.
When this may be hardware failure
Link lights on and DHCP failing on every router, after a reset, can still be a dying NIC, confirm with a USB adapter. Lights off on every cable is a port or cable issue, covered in the other Ethernet guide.
Common mistakes to avoid
- Setting a random static IP from a blog.
- Resetting Windows because the cable was in the WAN port.
- Flushing DNS to fix APIPA (DNS is not involved yet).
Frequently asked questions
Why 169.254?
It is a standard automatic private address. It means "no DHCP server answered." It is not your ISP's public IP.
Can I fix this by changing DNS?
Not while you have 169.254. There is no useful internet path yet. Change DNS after you have a real LAN address if names still fail.
Written by Practical PC editorial team. We write practical Windows and PC troubleshooting guides for home users, students, and office workers. Guides are researched from official documentation and widely observed support patterns, then reviewed for safety and plain language. We do not invent lab tests, certifications, or first-hand repair experience we do not have.