Windows 11 Ethernet with no valid IP address, 169.254.x.x, or an unidentified network usually means DHCP is failing, not DNS. First confirm the adapter has link and is really missing a lease, then try the least destructive Windows fixes: renew the address, disable and re-enable the adapter, reset the network stack, and check the driver. If those do not help, the router, switch, VLAN, DHCP server, cable, dock, or NIC path is more likely than the PC itself.
Symptom: confirm what is failing
Start by separating three different problems: no physical link, link with no DHCP lease, and a network that has a lease but still has no internet.
Open Command Prompt and run ipconfig /all. A healthy Ethernet adapter should show an IPv4 address on your network, a subnet mask, a default gateway, and DHCP enabled. If you only see Media disconnected, the problem is below DHCP and points to the cable, port, dock, or adapter link.
If the adapter has a 169.254.x.x address, that is APIPA. Windows gave itself a fallback address because it did not get a DHCP lease. That tells you the adapter is alive, but DHCP did not finish.
If Windows shows a normal address but browsing still fails, stop treating it like a DHCP problem. That is more likely DNS, gateway, or broader connectivity trouble.
A static IP means the adapter is set manually instead of using DHCP, so Windows will not request a lease unless you change that setting back. A duplicate address warning means another device is already using that IP, or Windows believes it is. “Unidentified network” usually means Windows has a link but cannot build a normal network profile because it does not have the expected lease or gateway information.
Before you start
Use this sequence on Windows 11, and do the checks in order. You do not need to reboot right away, and a reboot by itself does not tell you what failed.
- Make sure you can open Network Connections and Device Manager.
- If you are on a laptop or dock, note which Ethernet port, dock, and cable are in use so you can compare them later.
- If this PC uses a USB Ethernet adapter or dock, keep a second cable or port ready for comparison.
- If you can reach the router or switch, be ready to test another port or another device on the same segment.
If the machine is on a managed network, do not change VLAN, DHCP, or switch settings unless you control that gear or have the right support contact. Some failures are outside the PC, and changing the wrong setting can hide the real cause.
Try the safest Windows-side fixes first
- Open Network Connections, right-click the Ethernet adapter, and choose Disable. Wait a few seconds, then choose Enable.
If the adapter comes back with a normal IPv4 address, the problem was a stuck local session. If it still shows no valid address or APIPA, keep going.
- Open Command Prompt and renew the lease.
ipconfig /release
ipconfig /renewIf ipconfig /renew returns a normal address, DHCP is working again. If it comes back with 169.254.x.x or no usable IPv4 address, the adapter still is not getting a lease.
- Check the adapter’s IPv4 settings.
Settings > Network & Internet > Ethernet > Change adapter options > right-click the adapter > Properties > Internet Protocol Version 4 (TCP/IPv4)Make sure Obtain an IP address automatically is selected, and also confirm Obtain DNS server address automatically if you want the adapter to use DHCP for DNS too. If a static IP was left behind, it can look like a DHCP failure even when the router is fine.
- If that still does not work, reset the Windows network stack using the built-in network reset option. Do this only after you have noted any custom settings, because the reset clears saved network configuration and can remove adapter tweaks. If the connection returns after the reset, the problem was in Windows rather than the cable or router.
- Check the DHCP Client service if the lease still will not appear.
Search > Services > DHCP Client > PropertiesSet Startup type to Automatic and start the service if it is stopped. If the service was already running, move on; the issue is probably not just the service state.
How to tell whether the router, switch, VLAN, or DHCP server is the real fault
If one PC fails while a different device on the same cable, same switch port, or same router path works, the PC or adapter stays near the top of the list. If several devices fail on the same segment, the network gear is more likely than the PC.
A bad cable or marginal switch port can still show link lights and still block clean DHCP traffic. That is why I would test a different cable and a different port before I assume Windows is broken. If the light is on but ipconfig /renew never gets a lease, a physical link test alone is not enough.
If the port was moved, reconfigured, or placed into a different VLAN, DHCP requests may be reaching the wrong place or not reaching the server at all. On a home network, an exhausted DHCP scope is also possible. Microsoft’s support material says to check that the DHCP server is offering the right range and is not running out of addresses.
If more than one Windows PC fails while another device, such as an Android TV, still works, that points to a network-path or Windows-specific problem rather than a full outage. The same pattern can still come from a DHCP policy, VLAN, or driver issue, so compare one known-good device before you change settings at random.
When a USB Ethernet adapter, dock, or NIC driver is the likely cause
If the cable and port are fine, and another device gets a lease, the remaining weak point is often the adapter path on the PC. That includes the onboard NIC driver, a USB Ethernet adapter, the dock, or firmware on that hardware.
A dock or USB Ethernet adapter can negotiate link but still fail to pass DHCP traffic cleanly. In practice, that often shows up as repeated renew failures, an APIPA address, or a setup that works on one dock and fails on another. If the problem follows the dock or adapter instead of the laptop, that is a strong clue.
Check Device Manager for warning symbols, driver errors, or a recently changed adapter. If the problem disappears after a driver update or after moving to a different dock, the hardware path was probably the blocker. If it fails even with a different Ethernet adapter on the same PC, the fault may be deeper in Windows, but that is less common.
One useful clue from Microsoft Q&A is that some Windows 11 DHCP failures have looked like the client ignored an offer until the broadcast behavior changed, and one report mentioned long delays with ESET installed. That is not the everyday case, but it explains why a lease can look stuck even when the cable and switch seem fine.
What to do if the link is up but Windows still will not get a lease
If the Ethernet link is live but Windows keeps missing the lease, treat it as a DHCP handshake problem, not a generic internet problem. The clean order is: confirm automatic IPv4 settings, try ipconfig /release and ipconfig /renew, test another cable or port, then compare the same setup on another device.
If only one adapter profile fails, look for a static IP, a stale gateway, or a profile-specific setting. If every Windows machine on that segment fails but other device types work, suspect the switch port, VLAN, or DHCP server instead of the PC. If the same PC works on one network but not another, the issue is probably network-policy specific rather than a dead NIC.
If the lease arrives only after a long delay, or only after a security product is turned off, the path may be delaying or filtering DHCP packets instead of blocking all networking. That is one reason I prefer to test the simplest Windows settings first before I blame the router.
Verify the fix
Run ipconfig /all again and confirm that the adapter now has a normal IPv4 address, a subnet mask, a default gateway, and DHCP enabled. The address should no longer be in the 169.254.x.x range.
Open a browser only after the lease is back. If the adapter has a valid DHCP address but you still cannot browse, treat that as a separate problem and check DNS, gateway reachability, or the upstream network path.
Conclusion
If the adapter still won’t get a lease after renew, adapter disable/enable, network reset, and a driver check, stop chasing Windows settings and compare another cable, another port, and another device on the same network.
Frequently Asked Questions
How do I know if Windows 11 is using APIPA instead of DHCP?
Run `ipconfig /all` and look for a `169.254.x.x` IPv4 address. That range is APIPA, which means Windows did not receive a DHCP lease and fell back to a self-assigned address.
Should I check the router first or Windows first?
Check Windows first if only one PC is failing, because you can confirm the adapter state and lease behavior quickly with `ipconfig /all`, release and renew, and adapter settings. Check the router, switch, or DHCP server first if multiple devices fail on the same cable, port, or VLAN.
Sources
- How to fix No DHCP server found error in Windows 11 (youtube.com)
- Windows11 DHCP doesnt accept IP - Microsoft Q&A (learn.microsoft.com)
- 'No DHCP server was found', 'The DHCP server isn't responding'. - Microsoft Q&A (learn.microsoft.com)