What causes ethernet shows "limited" or "no internet access" on Windows?

Common causes of ethernet shows "limited" or "no internet access" include: DHCP server not responding (router issue or DHCP exhaustion), Static IP configuration incorrect or conflicting with another device, Ethernet driver corrupted or incompatible after Windows Update, Network cable damaged or not fully seated, Router or switch port malfunctioning, TCP/IP stack corrupted in Windows, DNS configuration pointing to unreachable servers.

How do I know if I have ethernet shows "limited" or "no internet access" issues?

Common symptoms of ethernet shows "limited" or "no internet access" include: Ethernet connected but shows "Limited" or yellow triangle, Network icon shows "No Internet access" with Ethernet plugged in, "Unidentified Network" appearing for wired connection, Ethernet works for local network but not internet, IP address showing 169.254.x.x (APIPA — no DHCP response), Ethernet light on router/switch is on but no connectivity in Windows, WiFi works fine but Ethernet does not on the same network.

Fix Ethernet Shows "Limited" or "No Internet Access"

Symptoms

You might be experiencing this problem if you notice:

•Ethernet connected but shows "Limited" or yellow triangle
•Network icon shows "No Internet access" with Ethernet plugged in
•"Unidentified Network" appearing for wired connection
•Ethernet works for local network but not internet
•IP address showing 169.254.x.x (APIPA — no DHCP response)
•Ethernet light on router/switch is on but no connectivity in Windows
•WiFi works fine but Ethernet does not on the same network

Common Causes

⚠DHCP server not responding (router issue or DHCP exhaustion)
⚠Static IP configuration incorrect or conflicting with another device
⚠Ethernet driver corrupted or incompatible after Windows Update
⚠Network cable damaged or not fully seated
⚠Router or switch port malfunctioning
⚠TCP/IP stack corrupted in Windows
⚠DNS configuration pointing to unreachable servers

Solutions

Solution 1: Reset TCP/IP and Winsock

1Open Command Prompt as Administrator
2Run: netsh winsock reset
3Run: netsh int ip reset
4Run: ipconfig /release
5Run: ipconfig /renew
6Run: ipconfig /flushdns
7Restart the computer
8This resets the entire TCP/IP stack and forces a fresh DHCP request

Solution 2: Check IP Configuration

1Open Command Prompt → run: ipconfig /all
2Look at "Ethernet adapter" section:
3If IP is 169.254.x.x: DHCP isn't working — your PC can't get an IP from the router
4Try: unplug Ethernet cable, wait 10 seconds, plug back in
5Try: connect to a different port on your router/switch
6Try: connect with a different Ethernet cable
7If still 169.254: set a static IP temporarily: Settings → Network → Ethernet → IP settings → Edit → Manual

Solution 3: Reinstall Ethernet Driver

1Open Device Manager → Network adapters
2Right-click your Ethernet adapter (Intel, Realtek, etc.) → Uninstall device
3Check "Delete the driver software for this device"
4Restart the computer — Windows will reinstall a fresh driver
5If the fresh generic driver works: download the latest driver from your motherboard/laptop manufacturer
6Intel: use Intel Driver & Support Assistant
7Realtek: use your PC manufacturer's support page

Solution 4: Set DNS Manually

1If you have an IP but no internet: DNS may be the issue
2Open Settings → Network & Internet → Ethernet → DNS server assignment → Edit
3Switch to Manual → enable IPv4
4Preferred DNS: 8.8.8.8 (Google) or 1.1.1.1 (Cloudflare)
5Alternate DNS: 8.8.4.4 or 1.0.0.1
6Save and test: open Command Prompt → ping google.com
7If ping works after changing DNS: your router's DNS configuration was the problem

FIXES THIS IN 5 MINUTES