When Windows shows the “Ethernet doesn’t have a valid IP configuration” or “no valid IP configuration on Ethernet” error, what it means is that your PC has failed to set an IP address with your router’s Dynamic Host Configuration Protocol (DHCP) server.

Without a valid IP address, your system cannot route any network traffic, be it local or the internet traffic via wired connection. This problem occurs from:

  • a stuck IP lease
  • a corrupted TCP/IP stack
  • misconfigured IPv4 settings
  • conflicts created by virtual network adapters (such as VPN or virtualization drivers).

Below is a complete troubleshooting guide to get your Ethernet connection back on. Each solution provides two ways, you can either follow the Windows GUI steps or use the Command Prompt (CMD) instructions.

What does “invalid IP configuration” mean?

Every connected device needs a unique IP address (such as 192.168.1.50) to communicate.

Your router automatically assigns these addresses using DHCP. When your Ethernet cable is plugged in but Windows shows an invalid IP configuration error, one of three things has happened:

  • Your PC sent an IP request, but the router failed to assign one.
  • Windows assigned itself an Automatic Private IP Address starting with 169.254.x.x. This range allows local hardware communication but cannot connect to the internet.
  • A virtual network adapter (like a VPN, TAP/TUN driver) has interfered with your network card’s routing tables.

Quick fix to “Ethernet does not have a valid IP configuration” error

If you want to reset your entire network stack at once, run this sequence of instructions in Command Prompt. It releases your existing IP, resets winsock sockets, flushes stale DNS entries, and requests a fresh IP lease from your router.

Press Win + S → type cmd → Command Prompt → select Run as administrator.

Copy and paste the following commands one by one, pressing Enter after each:

ipconfig /release

ipconfig /flushdns

netsh winsock reset

netsh int ip reset

ipconfig /renew

Once you are done, restart your computer.

If your connection is still blocked after the reboot, follow the step-by-step solutions below to isolate the specific failure point.

Fix 1: Restart your system

Before changing system configurations, clear temporary hardware memory leaks. Why it is needed is because routers keep a DHCP lease table in RAM. If this table gets corrupted or runs out of available addresses, the router rejects new IP requests from your Ethernet card. Here’s what you can do to fix it.

  • Unplug the power cable from your internet router and modem.
  • Wait 60 seconds to fully discharge the hardware capacitors and clear the RAM.
  • Plug the power cable back into your router.
  • Wait 2 to 3 minutes for the router’s boot cycle to complete and all connection lights to stabilize.
  • Power on your PC and check your Ethernet connection.

Fix 2: Set IPv4 and DNS to automatic (DHCP)

If your network adapter was manually assigned a static IP address or custom DNS server that doesn’t match your current router’s subnet, Windows will fail to establish an active IP lease. Setting the adapter back to automatic mode allows the router to manage configuration values.

  • Win + R to open the Run dialog box.
  • Type ncpa.cpl and press Enter to open Network Connections.
  • Right-click your active Ethernet network adapter and select Properties.
  • Select Internet Protocol Version 4 (TCP/IPv4) from the list and click the Properties button.
  • Select Obtain an IP address automatically.
  • Select Obtain DNS server address automatically.
  • Click OK, then click Close to save your changes.

Via command prompt

Run Command Prompt as Administrator and run these two commands to force your Ethernet adapter back to dynamic IP and DNS assignment:

  • netsh interface ipv4 set address name=”Ethernet” source=dhcp
  • netsh interface ipv4 set dnsservers name=”Ethernet” source=dhcp

(Note: If your network connection has a custom name, replace “Ethernet” with your exact adapter name).

Fix 3: Disable and re-enable the network adapter

Turning the network adapter off and then back on can refresh the connection and fix the problems.

  • Press Win + R, type ncpa.cpl, and press Enter.
  • Right-click your Primary Ethernet adapter.
  • Select Disable.
  • Wait 10 seconds.
  • Right-click the Ethernet adapter again and select Enable

Via command prompt

Open Command Prompt or PowerShell as Administrator and run:

  • Netsh interface set interface “Ethernet” disable
  • netsh interface set interface “Ethernet” enable

Fix 4: Resolve virtual network adapter & VPN driver conflicts

Desktop VPNs and virtualization applications create virtual network interface drivers (often named TAP-Windows Adapter, TUN, or VirtualBox Host-Only Adapter). These virtual interfaces alter your local routing table.If a VPN client closes unexpectedly or a virtual adapter crashes, its routing bindings can linger. This traps traffic in a dead-end tunnel and prevents your physical Ethernet card from receiving a dynamic IP assignment.

  • Press Win + X → Device Manager.
  • Expand the Network adapters category.
  • Look for virtual adapters such as TAP-Windows Adapter, TUN Adapter, or virtual machine switches.
  • Right-click the virtual driver and select Disable device.
  • Restart your desktop VPN software to allow its virtual adapter to re-initialize clean bindings.

Modern Windows desktop VPN apps like EonVPN rely on precise adapter routing. Disabling older drivers from previously uninstalled VPNs ends conflict points and allows EonVPN and your physical Ethernet port to communicate better.

Via PowerShell

In the command prompt,

  • List all active adapters on your desktop system with:
  • Get-NetAdapter
  • Identify any TAP, TUN, or third-party virtual adapters. Disable the conflicting virtual adapter using its exact name:
  • Disable-NetAdapter -Name “TAP-Windows Adapter V9” -Confirm:$false
  • Reset your main Ethernet adapter to re-establish physical gateway bindings:
  • Reset-NetAdapter -Name “Ethernet”

Fix 5: Restart the Windows DHCP client service

The DHCP Client service is a Windows background process that registers and updates IP addresses for your computer. If this service stops responding, Windows will fail to process incoming IP responses from your router.

  • Use Win + R, type services.msc, and press Enter.
  • Scroll down through the alphabetical list to find DHCP Client.
  • Check the Status column. It should read Running.
  • Right-click DHCP Client and select Restart.

If the restart option is grayed out, click Properties, set Startup type to Automatic, then restart your PC.

Fix 6: Reinstall network interface card (NIC)

If network drivers get corrupted, the physical card will lose its ability to construct valid TCP/IP packets. Uninstalling the network adapter will force Windows to wipe corrupted software profiles and reload a clean hardware driver upon reboot.

  • Press Win + X and select Device Manager.
  • Expand Network adapters.
  • Locate your primary physical Ethernet controller (e.g. Realtek, Intel, or Killer Networking).
  • Right-click your Ethernet controller and select ‘Uninstall device’.
  • Check the box for ‘Attempt to remove the driver for this device’ if prompted, then click ‘Uninstall’.

Do not panic if your network icon vanishes. Go to the top menu bar in Device Manager, click Action, and select ‘Scan for hardware changes’.

Windows will automatically detect the unmounted physical Ethernet port and will install a default driver.

Fix 7: Fast startup & fast network idle reset

Windows Fast Startup puts your kernel into a hybrid hibernation state instead of performing a cold shutdown. While this speeds up boot times, it saves the current network stack memory image to disk. If your network driver had an invalid IP configuration when you turned off your PC, that broken configuration gets reloaded directly into memory when you turn it back on.

  • Use Win + R, type control powercfg.cpl, and press Enter.
  • In the left-hand sidebar, click ‘Choose what the power buttons do’.
  • Click ‘Change settings that are currently unavailable’.
  • Scroll down to ‘Shutdown settings’.
  • Uncheck ‘Turn on fast startup (recommended)’.
  • Click ‘Save changes’ and reboot your system.

Summarized fixes to “No valid IP configuration” on Ethernet error

Failure ReasonPrimary IndicatorCMD ShortcutGUI Action
DHCP Lease StalledSelf-assigned 169.254.x.x IP addressipconfig /release
ipconfig /renew		Unplug router power for 60 seconds
Winsock/TCP Stack CorruptionConnected to LAN, no internet routingnetsh winsock reset
netsh int ip reset		Run Windows Network Troubleshooter
Static IP / DNS MismatchCustom DNS unresponsivenetsh int ipv4 set address name=”Ethernet” source=dhcpncpa.cpl > IPv4 Properties > Set Automatic
VPN / TAP Driver ConflictVirtual adapter active while physical failsDisable-NetAdapter -Name “TAP-Windows Adapter V9”Device Manager > Disable TAP/TUN adapters
Stuck Service MemoryDHCP Client service stoppedRestart-Service -Name “Dhcp” -Forceservices.msc > Restart DHCP Client
Driver CorruptionYellow exclamation mark in Device Managerpnputil /scan-devicesUninstall NIC in Device Manager & Rescan

How to avoid “Ethernet does not have a valid IP configuration” error

The “Ethernet doesn’t have a valid IP configuration” error is a software handshake failure between your Windows network stack and your router’s DHCP server.

To keep your wired network connection stable on desktop PCs:

  • Clear Old VPN Adapters: If you switch or test different VPN services, always uninstall unused virtual TAP drivers. Dedicated Windows desktop solutions like EonVPN manage virtual network drivers well, but older drivers from previous installations can still intercept network traffic.
  • Keep NIC drivers updated: Download the latest network adapter drivers directly from your laptop or motherboard manufacturer’s website ONLY.
  • Avoid aggressive network cleaners: Registry cleaners and anti-malware tools often accidentally purge registry entries for the Winsock stack, which can cause IP configuration failures.

Conclusion

In most cases, you can fix an invalid IP configuration on Ethernet error by resetting your network stack (netsh winsock reset and netsh int ip reset) and restarting your PC. If you’re still offline, check the auto IP address configuration and then inspect your DHCP server. Should those steps fail, re-verify your adapter’s IPv4 bindings and update your network card drivers.

FAQs

Is 192.168.1.1 a valid IP address?

Yes. 192.168.1.1 is a valid, private IPv4 address.

It falls within the standard private network address block (192.168.0.0 to 192.168.255.255) and is widely used by router manufacturers as the gateway address to log into the router’s admin control panel. It is used strictly within local area networks (LANs) and cannot be routed across the public internet.

How to configure IP for Ethernet?

You can manage your Ethernet IP settings through Windows:

  1. Press Win + R, type ncpa.cpl, and press Enter.
  2. Right-click Ethernet and select Properties.
  3. Double-click Internet Protocol Version 4 (TCP/IPv4).
  4. Select Obtain an IP address automatically and Obtain DNS server address automatically.
  5. Click OK to save.