Fix “Ethernet Doesn’t Have a Valid IP Configuration”

“Ethernet doesn’t have a valid IP configuration” means Windows detects the wired connection but has not received a usable IP address from the network. Check the cable, router, and Windows diagnostics first; then renew the address and reset Winsock and TCP/IP if those checks do not fix the problem. Do not change router settings or assign a random static IP unless your network administrator provides the correct values.

What the error means—and where the connection is failing

Windows needs an IP address to communicate with your router and the internet. On most home and office networks, the router assigns that address automatically through DHCP. This error appears when the Ethernet adapter has a physical link but receives no usable address, gateway, or related configuration.

Ethernet doesn't have a valid IP configuration

The failure can occur at several points:

• Cable or port: A damaged cable or faulty router port can produce an unreliable or one-way connection.
• Computer: The adapter may be disabled, configured with an unsuitable static address, affected by a driver problem, or stuck in a damaged Windows network state.
• Router: The router may be powered on while its DHCP service has stopped responding.
• Internet service: The computer can have a valid local IP and still be unable to reach the internet because of an outage or modem problem.

Compare other devices before changing Windows. If Wi-Fi devices also have no internet, check the modem, router, and ISP. If Wi-Fi works but this computer’s Ethernet does not, focus on the cable, Ethernet port, adapter, and Windows. If another computer works through the same cable and router port, the affected computer is the likely source of the problem.

Before changing settings, check the cable, port, and router

These checks are safe and reversible. They help distinguish a cable, computer, router, or service problem before you reset Windows.

This procedure applies to Windows 10 and Windows 11, including wired connections to home routers, office networks, and modems. You need an Administrator account for the command-line resets later. Restarting the modem and router does not erase their configuration, but it temporarily disconnects every device using them. No backup is needed for these checks.

1. Unplug the Ethernet cable from the computer and router, then plug both ends in firmly. If possible, try a different known-good Ethernet cable.
2. Move the cable to another LAN port on the router or network switch. Do not use the router’s Internet or WAN port for the computer unless the device is specifically designed for that arrangement.
3. Check the link lights beside the computer’s Ethernet socket and the router port. A light that stays off can indicate a bad cable, disabled adapter, faulty port, or failed network hardware. Lights alone do not prove that internet access works.
4. Test the same router port and cable with another computer, if one is available. Test the affected computer with another cable or port. If the problem follows the cable or port, the network hardware is the likely cause. If it follows the computer, focus on its adapter, driver, or Windows settings.
5. Restart the network equipment in order. Turn off the modem and router, or unplug their power. Wait until they are fully off, then power on the modem first. Wait for its normal connection lights, power on the router, and wait for it to finish starting. Reconnect or restart the computer afterward.
6. Run Windows’ built-in troubleshooter. Open Settings > Network & internet > Ethernet and select the available network troubleshooter or Diagnose option. Follow its findings, but do not accept a recommendation to use a static IP unless your network administrator supplied the required address.

If other devices are also offline after the restart, stop changing Windows settings. The issue is more likely to be the modem, router, service line, or ISP.

Fix the IP configuration in the safest order

After checking the cable and router, work through Windows from the least disruptive change to the more substantial reset. The settings check does not require an Administrator account; the command-line reset does.

1. Confirm that Windows is set to obtain an address automatically. Open the following path:

Settings > Network & internet > Advanced network settings > More network adapter options > Ethernet > Properties > Internet Protocol Version 4 (TCP/IPv4) > Properties

Select Obtain an IP address automatically and Obtain DNS server address automatically, unless this is a managed network that gave you specific static values. Select OK, close the property windows, and test the connection. Windows should request a fresh address from the router. If the error remains, continue.

2. Disable and re-enable the Ethernet adapter. In More network adapter options, right-click Ethernet, select Disable, wait a few seconds, then right-click it again and select Enable. This reloads the adapter without changing its configuration. If Ethernet does not appear, check Device Manager > Network adapters for a disabled device.
3. Open Command Prompt as administrator. Select Start, type Command Prompt, right-click it, and choose Run as administrator. Run these commands one at a time.

ipconfig /release
ipconfig /renew

ipconfig /renew should obtain a new address. If it reports that no operation can be performed or that the DHCP server cannot be reached, Windows is still not communicating correctly with the router. Continue with the reset.

4. In the same elevated Command Prompt, reset Winsock and the TCP/IP stack.

netsh winsock reset
netsh int ip reset

Restart Windows when prompted, or restart it yourself. These commands repair common software-level network problems, but they can remove or alter custom network settings made by VPNs, virtualization software, or a managed network. Do not repeat them several times. If they do not help after one restart, investigate the adapter, driver, and router instead.

How to confirm the Ethernet connection is actually fixed

Confirm the result with Windows networking information and a local-network test rather than relying only on the troubleshooter’s message.

1. Open Command Prompt and run:

ipconfig /all

Under the Ethernet adapter, look for an IPv4 address, a Default Gateway, and DNS servers. A normal home or office network commonly shows a private IPv4 address, such as one beginning with 192.168, 10., or 172.16 through 172.31, but the exact address depends on the network. An address beginning with 169.254 is an automatic private address that usually means DHCP did not provide a usable address.

2. Test the router first. Replace <gateway> with the Default Gateway shown by ipconfig:

ping <gateway>

Replies indicate that the computer can communicate with the local router. A timeout points to a local connection, adapter, cable, port, or router-side problem. Some routers block ping, so a timeout is a clue rather than absolute proof.

3. Test name resolution and internet access:

ping example.com

If the gateway responds and the domain test works, open a few websites. If the gateway responds but the domain test fails, DNS may be the problem. If the computer has a valid address and gateway but no websites work, check the router’s internet status and whether other devices have service.

The expected result is a valid IPv4 address, a gateway on the same local network, and working web access. If ipconfig /all still shows no IPv4 address or shows 169.254.x.x, Windows is not receiving DHCP information; investigate the cable, adapter, driver, and router rather than repeating the reset.

If it still fails after the reset

A failed reset usually means the cause is outside the basic Windows TCP/IP settings. Check the adapter, driver, router, and service without making more disruptive changes.

Adapter or driver problem. Open Device Manager > Network adapters. If the Ethernet device has a warning icon, right-click it and inspect Properties > General for an error code. Install the correct driver from the computer or motherboard manufacturer using another working device if necessary. Avoid downloading drivers from random driver sites. If the adapter is missing entirely, check whether it is disabled in firmware or whether the hardware has failed.

Router DHCP failure. Sign in to the router only if you know its administrator credentials and can do so safely. Check whether DHCP is enabled and whether its address pool is exhausted. Do not factory-reset the router as a first response: that can erase the ISP connection details, Wi-Fi settings, and other configuration. A router reboot is safe; a factory reset requires a known recovery plan.

Static-IP or managed network. Some offices, servers, and specialized connections do not use automatic addressing. If your network normally requires a fixed IP, subnet mask, gateway, DNS server, VLAN, proxy, or authentication method, ask the network administrator for the exact settings. Do not copy values from another computer or invent them.

VPN or security software. Temporarily disconnect a VPN and check whether recently installed firewall or endpoint software is blocking DHCP or the adapter. Follow your organization’s policy before disabling security controls, and re-enable anything you turn off for testing.

ISP or modem outage. If several devices cannot reach the internet but the router shows a normal local network, contact the ISP or check its service-status channel. Give them the modem status, the time the failure began, and whether a direct wired test or other devices are affected.

Stop resetting Windows when the computer has a valid local IP and gateway but the internet remains unavailable, or when other devices fail in the same way. At that point the router, upstream service, or managed network needs attention.

Conclusion

Leave IPv4 and DNS on automatic unless your network provides documented static settings. If the Ethernet adapter still receives no address after a known-good cable, another router port, a router restart, and one Windows reset, contact the ISP or network administrator with the `ipconfig /all` result and the tests you performed.

Frequently Asked Questions

Why does my Ethernet have an IP address but still no internet?

The computer may be connected to the local router while the router has lost its ISP connection, DNS is failing, or an upstream outage is active. Check the Default Gateway and test other devices. If the gateway responds but websites do not load, inspect the router’s internet status or contact the ISP.

Should I set a manual IP address to fix this error?

Usually, no. Most home networks expect DHCP, and assigning a random address can create a second problem. Use a manual IPv4 address only when your network administrator or ISP has supplied the exact IP address, subnet mask, gateway, and DNS values.

Will resetting Winsock delete my files or Wi-Fi password?

The Winsock and TCP/IP commands do not delete personal files. They can affect custom networking software and settings, so VPNs, virtual machines, or managed connections may need to be configured again. A restart is required after the reset.