Your PC shows the ethernet icon as connected, Windows reports “Connected” or even “Connected, secured” in the network panel, but every browser page times out and games refuse to log in. The yellow warning triangle over the network icon in the system tray and the “No internet, open with Connect to a network” message in Windows 11’s Network & internet settings are the classic tells. Meanwhile, the cable is plugged in, the link lights on the back of the PC or on your switch are glowing, and the adapter seems happy.
It’s frustrating but rarely urgent — nothing is broken, and in most cases the fix takes under ten minutes. Work through the fixes below in order; the first three resolve the majority of cases. Before you start, reboot your PC and power-cycle your router and modem (unplug for 30 seconds), since that alone clears a surprising number of “connected but no internet” states.
Likely Causes
| Cause | How to confirm | Fix difficulty |
|---|---|---|
| IP address conflict or bad DHCP lease | Run ipconfig /all in Command Prompt; an IP starting with 169.254.x.x means DHCP failed |
Easy |
| Wrong or corrupted DNS settings | Ping 8.8.8.8 succeeds but pinging google.com fails | Easy |
| Stale or corrupted network adapter driver | Yellow exclamation mark in Device Manager, or issue began after a driver/Windows update | Easy–Medium |
| Network stack corruption (Winsock/TCP-IP) | Wi-Fi also fails on the same PC, or issues started after malware cleanup or a crash | Medium |
| Router or ISP outage | Another device on the same router also has no internet | Easy (no PC fix needed) |
| VPN, proxy, or firewall interference | A VPN client, proxy setting, or third-party security suite is active on the PC | Medium |
Fix 1: Renew Your IP Address
What causes it
Your PC holds a DHCP lease from the router that has gone stale, or DHCP handed out a duplicate address. When that happens, the link layer shows connected but packets have nowhere valid to go. A 169.254.x.x “APIPA” address is the giveaway that DHCP never completed.
How to check
Press Win+R, type cmd, press Enter, then run ipconfig /all. Look at the “Ethernet adapter Ethernet” section. If IPv4 Address reads 169.254.x.x, or the “DHCP Enabled” line says Yes but “DHCP Server” is blank, this is your problem.
What to do
In the same Command Prompt, run these commands in order:
ipconfig /release
ipconfig /renew
Wait up to 30 seconds for the renew to finish, then run ipconfig /all again to confirm a valid address in your router’s range (commonly 192.168.1.x or 192.168.0.x). Test the connection.
How to undo it
Nothing to undo — renewing a lease is harmless and Windows would do it anyway on the next reboot.
Fix 2: Flush DNS and Switch to a Public DNS Server
What causes it
The DNS resolver cache can hold a corrupted or expired entry, or your router’s DNS forwarder is failing while the connection itself is fine. This is why sites fail by name but pings by raw IP succeed.
How to check
In Command Prompt, run ping 8.8.8.8 followed by ping google.com. If the first works and the second returns “could not find host,” DNS is your culprit.
What to do
First flush the cache: run ipconfig /flushdns and retest. If names still fail, set a public DNS server manually. Go to Settings > Network & internet > Ethernet, click your connection, and next to “DNS server assignment” click Edit. Change it from Automatic to Manual, turn on IPv4, and enter:
Preferred DNS: 8.8.8.8
Alternate DNS: 1.1.1.1
Save and test. Optionally also enable IPv6 with 2001:4860:4860::8888 and 2606:4700:4700::1111.
How to undo it
Return to the same Edit DNS screen and switch “DNS server assignment” back to Automatic (DHCP).
Fix 3: Disable Then Re-Enable the Adapter (or Reset It)
What causes it
The adapter’s internal state can hang after sleep/resume cycles, fast startup, or a driver hiccup while still reporting link-up to Windows.
How to check
There’s no diagnostic here — it’s a fast reset worth trying whenever the symptom appears, especially after waking the PC from sleep.
What to do
Go to Settings > Network & internet > Advanced network settings. Click Disable next to your Ethernet adapter, wait five seconds, then click Enable. Alternatively, open an elevated Command Prompt (right-click Start > Terminal (Admin)) and run netsh interface set interface "Ethernet" disable then netsh interface set interface "Ethernet" enable.
How to undo it
Not needed — enabling the adapter restores normal operation by definition.
Fix 4: Roll Back or Reinstall the Network Driver
What causes it
A driver update — whether from Windows Update or a manual install — can break DHCP or the NDIS stack on otherwise healthy hardware. Realtek and Intel onboard controllers both have a history of this after major Windows feature updates.
How to check
Right-click Start > Device Manager > Network adapters. Look for a yellow warning icon on your ethernet controller. Also check the “Driver Date” — if it changed within days of the problem starting, that’s strong evidence.
What to do
In Device Manager, right-click the ethernet adapter. If “Roll back driver” is available (not grayed out), use it and restart. If not, choose “Uninstall device,” check “Attempt to remove the driver for this device” only if you have the driver installer downloaded from your motherboard manufacturer’s support page first, then restart — Windows will reinstall a generic driver. For the cleanest result, download the latest LAN driver from your motherboard or laptop vendor’s site before uninstalling, and install it manually after the reboot.
How to undo it
Reinstall the previous driver version from the vendor’s support page, or use Device Manager > Update driver > Browse my computer to point at an older driver package you’ve kept.
Fix 5: Reset the Network Stack
What causes it
The Winsock catalog or TCP/IP configuration can become corrupted by malware, aggressive cleanup tools, or an interrupted update, breaking name resolution and connections for every protocol.
How to check
Circumstantial: if Wi-Fi on the same PC is also broken, or the trouble started after a security incident or crash, assume stack corruption.
What to do
Open Terminal (Admin) and run these four commands one at a time:
netsh winsock reset
netsh int ip reset
ipconfig /flushdns
netsh int ipv6 reset
Restart the PC — the Winsock reset does not take effect until you do. Note that you’ll need to re-enter any static IP or DNS settings afterward.
How to undo it
There’s no direct reverse, but re-entering your custom settings (static IP, DNS, port forwarding client configs) after the reboot restores everything. This is why you should note them down first.
Fix 6: Disable VPN, Proxy, and Third-Party Firewall Interference
What causes it
A half-uninstalled VPN client leaves behind a TAP adapter or system proxy pointing at a dead local address (typically 127.0.0.1 on some port), swallowing all traffic. Third-party security suites can also block traffic after a definition update.
How to check
Go to Settings > Network & internet > Proxy. If “Use a proxy server” is on with an address you didn’t set, that’s it. Also check Settings > Network & internet > Advanced network settings for leftover TAP or VPN adapters. Temporarily disable any third-party antivirus/firewall from its own tray icon to test.
What to do
Turn off “Automatically detect settings” and “Use a proxy server” on the Proxy page. Uninstall leftover VPN clients via Settings > Apps > Installed apps. If a security suite is the cause, temporarily disable it to confirm, then either add an exclusion for your network (set it to “Private network” in Settings > Network & internet > Ethernet > Network profile type) or reinstall the suite cleanly.
How to undo it
Re-enable proxy settings only if your workplace requires them, and re-enable your security software once the network profile or exclusions are corrected.
Fix 7: Disable Power Management on the Adapter
What causes it
Windows can power down the ethernet controller during sleep or idle to save energy; on some chips it fails to wake properly, leaving the link up but the driver unresponsive.
How to check
If the problem appears specifically after the PC has been asleep or idle, this is likely.
What to do
Device Manager > Network adapters > right-click your ethernet controller > Properties > Power Management tab. Uncheck “Allow the computer to turn off this device to save power.” While you’re there, check the Advanced tab for options named “Energy Efficient Ethernet,” “Green Ethernet,” or “Power Saving Mode” and set them to Disabled/Off. Click OK and test after a sleep cycle.
How to undo it
Re-check the box and re-enable the Advanced-tab power options. The only cost is a marginally higher idle draw.
Fix 8: Set a Static IP and MTU Manually
What causes it
Persistent DHCP problems on the router side, or an MTU mismatch (common with PPPoE or some VPN/ISP setups) where large packets are silently dropped — pages partially load or time out while pings work.
How to check
Test MTU by running ping google.com -f -l 1472. If it replies, MTU 1500 is fine. If it says “Packet needs to be fragmented but DF set,” lower the value (try 1460, 1450, 1432) until it succeeds; your MTU is that number plus 28.
What to do
For a static IP: Settings > Network & internet > Ethernet > IP assignment > Edit > Manual > IPv4 on. Enter an address outside your router’s DHCP pool but in the same subnet (e.g., 192.168.1.50 if the router is 192.168.1.1), subnet mask 255.255.255.0, gateway 192.168.1.1, and DNS 8.8.8.8 / 1.1.1.1. For MTU: in an elevated Command Prompt run netsh interface ipv4 set subinterface "Ethernet" mtu=1450 store=persistent, substituting your tested value.
How to undo it
Set IP assignment back to Automatic (DHCP) in the same menu, and run netsh interface ipv4 set subinterface "Ethernet" mtu=1500 store=persistent to restore the default MTU.
If Nothing Works
At this point the PC’s software stack has been ruled out, so shift focus to hardware and infrastructure. Test the same cable and router port with another device — if that device also fails, replace the cable (try a known-good Cat 5e or Cat 6 patch cable), use a different port on the router, or bypass any switch in the chain. Test the PC on a different router or directly into the modem. If another device works fine on the same port and cable, your NIC may be failing: a $15–25 USB 3.0 ethernet adapter is a cheap, reliable workaround. Finally, check your ISP’s status page or support line for regional outages, and as a last resort use Settings > System > Recovery > “Reset this PC” with “Keep my files,” or the newer “Fix problems using Windows Update” repair option, to repair Windows without losing data.
FAQ
Why does my PC say “connected, no internet” while other devices work fine?
That means the router and ISP are healthy and the problem is local to your PC — almost always a stale IP lease, broken DNS, or a corrupted driver. Start with Fixes 1 through 3.
Can a bad ethernet cable cause this even if the link lights are on?
Yes. Gigabit negotiation only needs a subset of the wire pairs to establish a link, but damaged pins or pairs cause packet loss and dropped negotiation, producing exactly this symptom. Swapping the cable takes ten seconds and rules it out immediately.
Should I disable IPv6 to fix this?
Only as a diagnostic. Some routers mishandle IPv6 prefix delegation, which can stall name resolution. Uncheck “Internet Protocol Version 6 (TCP/IPv6)” in the adapter’s Properties to test, but re-enable it afterward — disabling it long-term can break features that rely on it.
How do I stop this from happening again in 2026 and beyond?
Keep your LAN driver from your motherboard vendor’s site rather than relying solely on Windows Update, leave adapter power management off if you use sleep frequently, and note your DNS and IP settings somewhere safe so a network stack reset is a five-minute job instead of an afternoon.
