Ethernet Doesn’t Have a Valid IP Configuration: How to Fix It
Ethernet doesn't have a valid IP configuration means DHCP never answered and Windows fell back to a 169.254 address. Confirm it with ipconfig, then fix it.
In this guide
“Ethernet doesn’t have a valid IP configuration” means your PC asked the router for an address over DHCP and got no usable answer, so Windows fell back to a self-assigned 169.254.x.x address that cannot reach the internet. Renew the lease, restart the router, check the cable and the adapter’s DHCP setting, then check the router’s DHCP server.
Test it now
Cloudflare edgeRead at the Cloudflare edge from this request. The homepage adds your provider, network type and the VPN, DNS and WebRTC checks.
Show detailsWhat it means when Ethernet doesn’t have a valid IP configuration
A valid IP configuration is an address, a subnet mask and a default gateway handed to your PC by a DHCP server, which on a home network lives inside the router. RFC 2131 defines the exchange: the client broadcasts a DHCPDISCOVER, a server answers with a DHCPOFFER, the client accepts with a DHCPREQUEST, and the server confirms with a DHCPACK. If no offer arrives, the client retransmits with a randomized exponential backoff, doubling the delay up to a maximum of 64 seconds (section 4.1).
Windows does not wait forever. Microsoft’s documentation on Automatic Private IP Addressing (APIPA) says a Windows computer configured for DHCP broadcasts “three or more” discover messages, and if no server responds it assigns itself an address from 169.254.0.0 to 169.254.255.255, a range IANA reserved for this purpose. That address only works on the local cable or Wi-Fi segment: RFC 3927 requires that packets with a 169.254 source address “MUST NOT be forwarded outside the local link,” and Microsoft notes the computer “cannot communicate with computers on other subnets.” No gateway, no DNS, no internet, and the troubleshooter reports the line you searched for.
So the error is not a wrong address; it is no answer. The fixes below run from the cheapest reason DHCP could have failed to the rarest. The 169.254 guide explains the mechanism in depth; this page is the fix path for the Windows message.
Check what address you actually have
Confirm the diagnosis first. Open Command Prompt as administrator and run ipconfig /all, then read three lines in the Ethernet adapter block: DHCP Enabled, Autoconfiguration Enabled and the IPv4 address line. Microsoft’s APIPA page gives the test: if Autoconfiguration Enabled says Yes and the autoconfiguration address is 169.254.x.y, the computer is using APIPA; in current Windows 10 and 11 output the line is labeled Autoconfiguration IPv4 Address. The Default Gateway line will be empty, because no router told the PC where to send traffic; the default gateway guide shows what a healthy entry looks like.
Two other outputs change the plan. “Media disconnected” means the link itself is down, so start with Fix 1 and Fix 5 and skip the DHCP commands. A normal 192.168.x.x or 10.x.x.x address with a gateway means the configuration is valid after all and the fault is elsewhere, usually DNS or the router’s own uplink.
The local IP tool is the quick check on any device that is online. Modern browsers usually hide the LAN address behind an mDNS name, so the page gives the per-system steps for Windows, macOS, Linux, iPhone and Android and explains the private ranges, including why 169.254.x.x means the device never got an address from the router. Open it on your phone while the PC is offline: if the phone, on the same Wi-Fi, has a proper lease, the router’s DHCP server works and the PC is the problem.
Fix 1: Power-cycle the router and PC, re-seat the cable, try another port
Microsoft’s Ethernet troubleshooting page (Windows 10 and 11) starts on the router side. Make sure the cable sits in a LAN port on the router, not the Internet port that connects the modem, and swap the cable if another is nearby. Then restart the modem and router in Microsoft’s order:
- Unplug the router’s power cable.
- Unplug the modem’s power cable. If its lights stay on, remove its backup battery.
- Wait at least 30 seconds.
- Plug the modem back in and wait for its lights to stop blinking.
- Plug the router back in and wait a few minutes for the status lights to settle.
- Restart the PC and try again.
A combined modem-router is one device, so one cycle. This clears a hung DHCP service and empties an exhausted address pool.
Fix 2: ipconfig /release, /renew and /flushdns
If the link is up and the address still starts with 169.254, ask for a lease explicitly from an administrator Command Prompt:
ipconfig /releaseipconfig /renewipconfig /flushdns
Per the Microsoft Learn ipconfig reference (Windows 10, Windows 11 and Windows Server), /release sends a DHCPRELEASE message and discards the current configuration, /renew renews the DHCP configuration and works only on adapters set to obtain an address automatically, and /flushdns clears the DNS resolver cache. The second command is the one that matters: an address that does not start with 169.254 means you are done, while a message that Windows was unable to contact your DHCP server means nothing answered the broadcast and you continue. The flush is cheap insurance against stale answers once you are back online; the flush DNS guide covers what it does and does not fix.
Fix 3: Reset TCP/IP and Winsock (netsh int ip reset, netsh winsock reset)
Microsoft’s sequence for both Ethernet and Wi-Fi problems is five commands in a fixed order. Run them from an administrator Command Prompt to “manually reset the TCP/IP stack, release and renew the IP address, and flush and reset the DNS client resolver cache”:
netsh winsock resetnetsh int ip resetipconfig /releaseipconfig /renewipconfig /flushdns
Winsock is the interface applications use to reach the network, and the TCP/IP reset returns the stack to its defaults. Both live on the PC, not the router, which is why this fix can work on a machine where every other device on the same router is fine. Restart afterwards and check ipconfig /all again.
Fix 4: Make sure “Obtain an IP address automatically” is on
A static address left over from an old network produces the same symptom, because Windows never sends a DHCPDISCOVER for an adapter set to Manual. Microsoft’s current path (Windows 10 and 11):
- Open Settings > Network & internet > Ethernet and select the connected network.
- Next to IP assignment, select Edit.
- Under Edit IP settings, choose Automatic (DHCP) and save.
With Automatic, Microsoft says, the address and DNS settings “are set automatically by your router or other access point,” and nothing needs changing when you move the device. The static vs dynamic IP guide explains when a manual address is worth the upkeep.
Fix 5: Reinstall the network adapter driver and do a full restart
If the adapter shows Media disconnected with a good cable, or DHCP fails only on this PC after a Windows update, Microsoft’s next step is to remove the driver and let Windows reinstall it:
- Open Device Manager and expand Network adapters.
- Right-click the Ethernet adapter, select Uninstall device, check Attempt to remove the driver for this device, then Uninstall.
- Select Start > Power > Restart; Windows looks for and installs the driver on restart.
Microsoft advises downloading the manufacturer’s driver on another PC first, since this one cannot fetch anything. Network reset (Windows 11: Settings > Network & internet > Advanced network settings > Network reset; Windows 10: Status > Network reset) is the heavier version: it removes every adapter and reinstalls them with defaults, and Microsoft says to use it last.
Use Restart, not Shut down, after either step. Fast Startup is on by default, and Microsoft explains that a shutdown saves the kernel session and device drivers to the hibernation file instead of closing them, while the setting “doesn’t apply to Restart,” which performs a full boot; shutdown /s /t 0 is Microsoft’s documented full shutdown. The checkbox lives under Control Panel > Power Options > System Settings, but Microsoft says disabling it is not recommended, and a restart gives the same clean initialization.
Fix 6: Check the router’s DHCP server, or set a temporary static IP as a workaround
When every device is stuck on 169.254, or the PC is fine on another network, the router’s DHCP server is the suspect. Log in to the router (its address is the default gateway from a working device, often 192.168.1.1) and check the LAN or DHCP page:
- The DHCP server is enabled. A mesh system or a second router added in “router mode” is a common reason it was switched off, or two servers now compete.
- The pool is big enough. A small pool with long leases runs dry in a house full of phones, plugs and cameras; widen the range or shorten the lease.
- MAC filtering is not blocking this adapter. Google notes that Android 10 and later devices have a randomized MAC address per network, shown under the network’s settings, so a filter built from the address printed on the box rejects the phone.
If the router has no internet itself, its WAN status page shows a 169.254 or 0.0.0.0 address: the router failed to get its own lease from the ISP, the same failure one hop up. Once the WAN page shows an address, paste it into the IP lookup, which names the owner and the connection type; they should be your ISP and residential. A 100.64.x.x WAN address is not a fault but carrier-grade NAT.
A manual address gets one PC online tonight while leaving the fault in place for every other device. Use the Edit IP settings screen from Fix 4: choose Manual, turn on IPv4, and type an IP address, subnet mask, gateway and DNS servers, as Microsoft’s page lays out. Pick an address outside the router’s DHCP range, use the router as gateway and DNS, and switch back to Automatic (DHCP) once the router is repaired; an address inside the pool invites a conflict the day the router leases it to something else.
Same failure, different names: Wi-Fi, Android and PS5
The DHCP timeout does not care how the device is attached.
“Wi-Fi doesn’t have a valid IP configuration” is identical on the Windows side; the netsh and ipconfig commands, the driver reinstall and network reset come from Microsoft’s Wi-Fi page. Two Wi-Fi steps come first there: forget the network under Settings > Network & internet > Wi-Fi > Manage known networks and reconnect, and try the other band if the router broadcasts both 2.4 GHz and 5 GHz.
Android shows “IP configuration failure” or “Failed to obtain IP address” under the network name while it keeps trying. Google’s troubleshooting page (menu names vary by device) says to restart the phone, turn Airplane mode on for 10 seconds and off, toggle Wi-Fi, and unplug the router for 30 seconds. To forget a network, go to Settings > Network & internet > Internet, touch and hold it, then tap Forget, and reconnect. If the router filters by MAC, allow the randomized address shown under the network’s settings.
PS5 reports that it can’t obtain an IP address. Sony’s setup page puts everything under Settings > Network > Settings > Set Up Internet Connection, with Set Up Wired LAN > Connect for a cable and Advanced Settings for IP address, DHCP Host Name, DNS, MTU and proxy. Sony notes the PS5 supports IPv6 but not IPv6-only networks, so a router set to IPv6 only must be changed to IPv4, and advises asking your ISP or network administrator before changing advanced settings. The order of fixes is the one above: cable and port, router restart, then a manual address as a last resort.
When any device is back online, open the CheckMyIP homepage from it: a public IP, your ISP’s name and a residential connection type confirm that both the lease and the router’s uplink work.
Sources
- Microsoft Support: Fix Ethernet connection problems in Windows
- Microsoft Support: Fix Wi-Fi connection issues in Windows
- Microsoft Support: Essential network settings and tasks in Windows (Change TCP/IP settings)
- Microsoft Learn: ipconfig command reference
- Microsoft Learn: How to use automatic TCP/IP addressing without a DHCP server (APIPA)
- Microsoft Learn: Fast startup causes hibernation or shutdown to fail in Windows
- RFC 2131: Dynamic Host Configuration Protocol
- RFC 3927: Dynamic Configuration of IPv4 Link-Local Addresses
- Android Help: Fix internet connection problems on Android devices
- Android Help: Connect to Wi-Fi networks on your Android device
- Android Help: Manage advanced network settings on your Android phone
- PlayStation Support: How to set up an internet connection on PlayStation consoles
Questions
Is 192.168.1.1 a valid IP?
Yes. 192.168.1.1 is a private address from the 192.168.0.0/16 range, and on most home networks it is the router itself. A valid configuration for your PC looks like 192.168.1.x plus a default gateway of 192.168.1.1. The invalid one is 169.254.x.x with no gateway at all.
Why is my PC not connecting to Ethernet?
Either the link is physically down (cable, port, driver) or the link is up but DHCP never answered. Run ipconfig /all: no IPv4 address or “Media disconnected” points to the physical side; an Autoconfiguration IPv4 Address of 169.254.x.x points to DHCP. Fix the side the output names.
How do I fix a not valid IP address?
Run ipconfig /release then ipconfig /renew from an administrator Command Prompt. If the address still starts with 169.254, restart the router and modem, confirm IP assignment is Automatic (DHCP), reset Winsock and TCP/IP with netsh, reinstall the adapter driver, and finally check the router’s DHCP server and MAC filter.
How do I configure my Ethernet IP?
In Windows 10 and 11, open Settings > Network & internet > Ethernet, select Edit next to IP assignment, and choose Automatic (DHCP) so the router assigns everything, or Manual to type an IPv4 address, subnet mask, gateway and DNS servers yourself. Use Manual only as a short-term workaround.
Back to your own address: my IP address

