PC Help

How Do I Fix Ethernet Connected No Internet Windows 11?

Ethernet shows connected but no internet on Windows 11? Fix DNS, IP conflicts, adapter settings, and Winsock — with exact commands that solve each cause.

Issue type: PC networking — Ethernet cable is physically connected and Windows 11 shows the network as connected, but no websites load and the connection has no internet access

SEO focus: If you are looking for ethernet connected no internet windows 11, this guide starts with the fastest diagnosis, then moves to the exact fix that matches the symptom.

Short answer: “Connected, no internet” in Windows 11 means the Ethernet link is up — your PC and router are talking to each other — but the path from your router outward to the internet is broken, or Windows itself has a corrupt DNS or IP configuration. The two most common causes are a corrupted Winsock catalog and a wrong or unreachable DNS server. Both are fixed in under two minutes with two commands.

Ethernet Connected No Internet Windows 11: Quick Diagnosis

Open Command Prompt as Administrator and run:
ping 8.8.8.8
If you get replies, your internet connection works but your DNS is broken — your PC can reach the internet but can’t translate domain names into addresses. That’s why websites fail but the connection shows as active.
If ping times out with “Request timed out” or “General failure,” the problem is deeper: either the IP stack on Windows is corrupt, the router isn’t routing traffic, or the ISP has an outage.

Then run:
ping google.com
If ping 8.8.8.8 works but ping google.com fails, confirm: it’s DNS only. If both fail, it’s the network stack or the router.

Also check the yellow exclamation mark on the network icon in the taskbar. “No internet access” = DNS or routing issue. “No network access” = the link itself is broken (wrong IP, DHCP failure). These look similar from the taskbar but the fix is different for each.

What to do first

  1. Flush DNS cache and reset Winsock — this fixes the majority of “connected no internet” cases in Windows 11. Open Command Prompt as Administrator and run these commands one at a time:
    netsh winsock reset
    netsh int ip reset
    ipconfig /release
    ipconfig /flushdns
    ipconfig /renew
    Restart the PC after all five complete. Winsock is the Windows API layer that all network apps use — corruption there breaks internet access while leaving the physical connection intact. This is the most effective single fix for the symptom.
  2. Switch to Cloudflare or Google DNS manually. Open Settings > Network & internet > Ethernet > click your connection > click Edit next to DNS server assignment > switch to Manual > enable IPv4 > enter:
    Preferred DNS: 1.1.1.1
    Alternate DNS: 1.0.0.1
    Save and test immediately. Your ISP’s DNS servers can go down or return bad responses while your physical connection stays active — switching to Cloudflare’s 1.1.1.1 bypasses your ISP’s DNS entirely. If websites load after this change, the ISP’s DNS was the problem.
  3. Release and renew the IP address if the PC received a bad APIPA address. Open Command Prompt as Administrator and run:
    ipconfig /all
    Look at the IPv4 Address for your Ethernet adapter. If it starts with 169.254.x.x, the PC failed to get an IP from the router’s DHCP server and assigned itself a link-local address instead. This means no internet routing is possible. Run ipconfig /release then ipconfig /renew to force a fresh DHCP request. If you keep getting 169.254.x.x, either the DHCP service on the router is full or the PC’s DHCP client service has an error (run net start dhcp in Admin CMD to restart it).
  4. Check whether the Ethernet adapter itself has a driver or hardware error. Open Device Manager (Win + X > Device Manager) > Network adapters. Look for a yellow exclamation mark on the Ethernet adapter. If present, right-click > Update driver > Search automatically. If no update is found, go to your motherboard or laptop manufacturer’s website and download the LAN driver for your exact model. An outdated or partially corrupted Ethernet driver can cause exactly this symptom: link up, no traffic. The guide on Wi-Fi missing from Settings covers similar driver repair steps that apply to Ethernet adapters.
  5. Disable IPv6 on the Ethernet adapter as a targeted fix for IPv6-related routing failures. Open Network and Sharing Center > click your Ethernet connection > Properties > uncheck Internet Protocol Version 6 (TCP/IPv6) > OK. Some routers have buggy IPv6 implementations that cause Windows 11 to attempt IPv6 resolution first, fail, and not fall back to IPv4 cleanly. Disabling IPv6 forces all traffic through IPv4 and often immediately resolves “connected, no internet” where all other settings look correct. This is safe for home networks.
  6. Power cycle the router and modem in the correct order if all PC-side fixes fail. Turn off the modem first, wait 30 seconds. Turn off the router, wait 30 seconds. Turn on the modem, wait 60 seconds for it to sync with your ISP. Turn on the router, wait 30 seconds. Then test. The order matters — the modem must establish its ISP connection before the router tries to get an IP from it. Turning them on simultaneously or in the wrong order can leave the router without a valid WAN IP, which produces exactly the “connected, no internet” symptom on all devices.

Common mistake

Repeatedly clicking “Troubleshoot” in Windows network settings and accepting whatever it reports without doing anything further. Windows’ built-in troubleshooter is useful for identifying the category of the problem (DNS, DHCP, adapter) but its automatic fixes rarely resolve the root cause. Users click Troubleshoot, see “Fixed: DNS resolution issue,” then find the internet still doesn’t work — because the troubleshooter restarted the DNS client service without addressing the underlying DNS server misconfiguration. Use the troubleshooter to diagnose, not to fix. Then apply the targeted commands above for whichever category it identified.

Best next step

If the Winsock reset and DNS change both failed and the router power cycle didn’t help, check whether the problem is on your specific PC or on all devices. Connect a phone or another PC to the same router via Ethernet or Wi-Fi. If other devices have internet, the problem is isolated to your Windows 11 PC — proceed with the Ethernet driver reinstall and check Device Manager for errors. If all devices have no internet, the problem is at the router or ISP level. Log into your router admin panel (usually 192.168.1.1 or 192.168.0.1) > WAN or Internet status section > check whether the router has a valid WAN IP from your ISP. If it shows 0.0.0.0 or an APIPA address on the WAN side, contact your ISP — their DHCP server may be down or your account may have an issue. For deeper DNS understanding, Cloudflare’s DNS setup guide explains exactly how DNS resolution works and how to configure it correctly on any device.

Quick Q&A

Ethernet works fine on another PC connected to the same router. Why does it fail only on my Windows 11 machine?

The issue is definitively Windows-side since the router and cable work for another device. Start with the Winsock reset (step 1) — this fixes most PC-specific “connected no internet” cases in under two minutes. If that doesn’t resolve it, check Device Manager for Ethernet driver errors and reinstall the driver from your manufacturer’s website. Also check whether a VPN client, firewall software, or security suite installed on this PC is intercepting network traffic — temporarily disable them and test.

My Ethernet is connected but I can access some websites and not others. What’s happening?

Partial connectivity like this is almost always a DNS issue. Some websites resolve through cached DNS entries while others need a fresh lookup that fails. Run ipconfig /flushdns in Admin CMD to clear the DNS cache, then set your DNS to 1.1.1.1 and 8.8.8.8 as described in step 2. If specific sites still fail after DNS is fixed, those sites may be down, or your ISP may be blocking them. Test by accessing the site through its IP address directly — if it loads via IP but not by name, it’s a DNS record issue for that specific domain.

After running the reset commands, my network share and printer stopped working. Did the reset break them?

Temporarily, yes — Winsock and IP stack resets clear some network configurations including SMB network discovery settings. After the reset, go to Settings > Network & internet > Advanced network settings > scroll to Related settings > More network adapter options. Right-click the Ethernet adapter > Properties > confirm that “File and Printer Sharing for Microsoft Networks” is checked. Also go to Control Panel > Network and Sharing Center > Change advanced sharing settings > enable Network discovery and File and printer sharing for the Private profile. These settings sometimes need to be re-enabled after a Winsock reset.

My Ethernet shows “Connected, secured” in Windows 11 but there’s still no internet. Is the “secured” part misleading?

“Connected, secured” means your PC has an active link to the router and the connection uses WPA2 or WPA3 authentication (for Wi-Fi) or a valid IP (for Ethernet). It says nothing about whether the router itself has internet access. Think of it as: your PC successfully joined the local network — but whether that local network has a path to the internet depends on the router’s WAN connection to your ISP, which is entirely separate. “Connected, secured” + no internet almost always means the router’s WAN side is the problem. Check the router admin page.

I changed DNS to 1.1.1.1 and the internet worked briefly then stopped again. What does that tell me?

Intermittent failure after a DNS change points to a route stability issue rather than a pure DNS problem. Your IP connection to the router is dropping and re-establishing, which makes it look like DNS is the issue (because browsing fails when the connection drops). Check the Ethernet cable — swap it for a known-good cable and test. Also check the physical port on the router (try a different port). Run ping 192.168.1.1 -t in CMD for 5 minutes and look for “Request timed out” entries — if they appear, the link to the router itself is unstable, confirming a cable or port issue rather than a DNS or Winsock problem.