Ethernet Limited Connectivity Fix: Step-by-Step Guide

Your Ethernet shows 'limited connectivity' and no internet. Start with the quick fix: unplug the cable and power cycle. If that fails, dig into the settings.

The 30-Second Fix: Power Cycle & Cable Check

Don't overthink this. The culprit here is almost always a temporary glitch in your router, switch, or the PC's network stack.

Unplug the Ethernet cable from your PC. Wait 5 seconds. Plug it back in.
If that didn't work, unplug your router's power cable. Wait 30 seconds. Plug it back in.
Wait 2 minutes for the router to fully boot. Then check your connection.

I've seen this fix work on Windows 10, Windows 11, and even older Windows 8 machines. Nine times out of ten, it's just the router acting up. Skip the 'release and renew' voodoo for now — we'll hit that if this doesn't work.

If you're still seeing 'Limited connectivity' after that, move to the next step.

The 5-Minute Fix: Disable Fast Startup & Reset Network Stack

Windows Fast Startup is a common cause of this problem. It doesn't fully shut down the network adapter, so the next boot can get confused.

Step 1: Turn Off Fast Startup

Press Win + X and choose Power Options.
Click Additional power settings (on the right).
Click Choose what the power buttons do.
Click Change settings that are currently unavailable.
Uncheck Turn on fast startup (recommended).
Click Save changes. Restart the PC.

This alone fixes it for many people. Don't skip it — I've seen it work on hundreds of Dell and HP laptops.

Step 2: Release, Renew, and Reset DNS

Open Command Prompt as Administrator and run these commands one at a time:

ipconfig /release
ipconfig /renew
ipconfig /flushdns
nbtstat -R
nbtstat -RR
netsh int ip reset
netsh winsock reset

After each command, press Enter. When the last one completes, restart the PC. This clears out any screwed-up IP or DNS cache. I've used this exact sequence on Windows 10 Pro and Windows 11 Enterprise machines that refused to connect after a cable swap.

If the 'ipconfig /renew' hangs or errors out, your DHCP server isn't handing out an IP. That's a router or switch problem, not your PC. Skip to the advanced section.

The 15+ Minute Fix: Adapter Settings & Driver Deep Dive

If you're still stuck, we're going into the weeds. This is where the actual hardware or driver issue lives.

Step 1: Check the Adapter Speed & Duplex Settings

A mismatch between your PC's adapter speed and what the switch port supports can cause 'limited connectivity'. You'll see this on cheap switches or old cables.

Press Win + R, type ncpa.cpl, hit Enter.
Right-click your Ethernet adapter, choose Properties.
Click Configure next to the adapter name.
Go to the Advanced tab.
Find Speed & Duplex (may also be called 'Link Speed').
If it's set to 'Auto Negotiation', change it to 100 Mbps Full Duplex (or 1 Gbps if you're on gigabit hardware and the cable is good).
Click OK, restart the PC.

If the link comes back, your auto-negotiation was failing. I've seen this on Realtek and Intel adapters connected to older Cisco switches. Sometimes you have to force it.

Step 2: Update or Roll Back the Network Driver

A bad driver update (looking at you, Windows Update) can break Ethernet. Here's the blunt truth: the driver from your PC manufacturer's site is usually better than the latest from Intel or Realtek.

Press Win + X, choose Device Manager.
Expand Network adapters.
Right-click your Ethernet adapter, choose Update driver.
Select Browse my computer for drivers.
Click Let me pick from a list of available drivers on my computer.
Try an older version if there are multiple. If you see one dated a few months back, select it.

If you're on a corporate network, check with your IT team before rolling back. Some drivers have security patches you don't want to lose.

Step 3: Check for Static IP vs. DHCP Conflict

If you've ever set a static IP on this adapter (maybe for a lab or test setup), it might still be hiding in the settings. A static IP outside the DHCP range gives you 'limited connectivity' every time.

Go back to ncpa.cpl.
Right-click Ethernet, Properties.
Double-click Internet Protocol Version 4 (TCP/IPv4).
Make sure Obtain an IP address automatically and Obtain DNS server address automatically are selected.
If they were already set to auto, try the opposite: set a static IP like 192.168.1.50 (subnet 255.255.255.0, gateway 192.168.1.1) and see if that works. Then switch back to auto.

I've seen a bug where the adapter remembers the old static IP even after you set it to DHCP. Forcing a static IP and then switching back clears it.

Step 4 (Last Resort): Reset Network Settings Completely

This nukes all your network adapters, Wi-Fi, VPNs, everything. You'll have to re-enter passwords.

Go to Settings > Network & Internet > Advanced network settings.
Click Network reset.
Click Reset now. Confirm. Your PC will restart.

After the reboot, go back and re-run the ipconfig /renew and /flushdns commands from the 5-minute section. This has fixed stubborn 'limited connectivity' on Windows 11 machines that had been through three driver updates.

When to Call It — Hardware Issues

If none of the above worked, the hardware is suspect. Try these quick checks:

Plug the cable into a different port on the router/switch.
Try a different Ethernet cable. Cat5e or Cat6 minimum. Don't use a crappy old cable.
If you're using a USB-to-Ethernet dongle, throw it away. They're unreliable. Buy a PCIe card or use the motherboard port.
On a work machine, contact your IT team. They might have a firewall rule or VLAN issue that's blocking DHCP.

I've saved this last bit for the end because it's rare, but I've seen a bad switch port cause 'limited connectivity' on every device plugged into it. Test with a laptop on the same cable and port.

That's it. Start with the 30-second fix, work your way down. Most people stop at the power cycle. If you're reading this, you're probably already past that. Move fast, don't waste time on things that don't matter.