Fix 'Limited Connectivity' by Resetting the TCP/IP Stack

What "Limited Connectivity" Actually Means

When Windows shows No internet, secured or the network icon has a warning triangle, it means your PC has a network link (it's talking to the router or switch) but isn't getting proper internet-layer connectivity — usually because it fell back to a self-assigned 169.254.x.x APIPA address, DNS resolution is failing, or the Winsock/TCP-IP stack itself has gotten into a corrupted state after malware removal, a botched VPN client uninstall, or a driver conflict. A full stack reset walks through each layer — DNS cache, DHCP lease, Winsock catalog, and the TCP/IP driver bindings themselves — rather than guessing which one is broken.

Step 1: Check What You're Actually Dealing With

Open Command Prompt and run:

ipconfig /all

Look at the IPv4 Address for your active adapter:

• An address starting with 169.254. means DHCP failed entirely — the PC gave up waiting for the router and self-assigned an address, which can't route to the internet.
• A normal-looking address (e.g. 192.168.1.x) but still no internet suggests DNS or gateway routing is the problem, not DHCP.

Step 2: Run the Full Reset Sequence

Open Command Prompt as Administrator and run these commands in order:

ipconfig /release
ipconfig /flushdns
ipconfig /renew
netsh winsock reset
netsh int ip reset
ipconfig /registerdns

Here's what each one actually does:

• ipconfig /release — drops the current DHCP lease.
• ipconfig /flushdns — clears the local DNS resolver cache, which can hold stale records pointing at dead servers.
• ipconfig /renew — requests a fresh IP address, gateway, and DNS servers from the DHCP server (your router in most home setups).
• netsh winsock reset — rebuilds the Winsock catalog, the registry-stored list of protocol providers (LSPs) that applications use to talk to the network stack. This fixes issues where a VPN client, antivirus, or malware left behind a broken or hijacked Winsock provider.
• netsh int ip reset — resets the TCP/IP stack itself back to its default configuration, rewriting two key registry keys (tcpip.sys and tcpip6.sys bindings). This is the most aggressive step, useful when static IP settings or IPv6 configuration have gotten corrupted.
• ipconfig /registerdns — re-registers this machine's hostname with your DNS server, useful mainly on domain networks.

Step 3: Reboot

netsh winsock reset and netsh int ip reset both require a restart to fully take effect — the changes are written but don't apply to the running network stack until the machine reboots. Restart now.

Step 4: Verify

After rebooting, check the new configuration:

ipconfig /all
ping 8.8.8.8
ping google.com

If ping 8.8.8.8 works but ping google.com fails, the IP stack is fine and the issue is DNS specifically — try switching to a public DNS server like 1.1.1.1 (Cloudflare) or 8.8.8.8 (Google) in the adapter's IPv4 properties. If neither ping succeeds, the problem is upstream of your PC: check the router itself, cable connections, or contact your ISP.

Rare Cases: Rebuild ARP and Route Tables

If limited connectivity persists specifically after your PC has been on the network a while (rather than immediately after boot), a stale ARP cache or corrupted route table can be the culprit — this shows up as connectivity that intermittently drops or one specific host becoming unreachable while others work fine:

arp -d *
route -f

arp -d * clears all cached MAC-to-IP mappings, forcing fresh ARP resolution. route -f flushes the routing table of all entries except the persistent ones defined in the registry — useful if a VPN client or virtual adapter left behind a route that's silently swallowing your traffic.

When None of This Fixes It

If the reset sequence doesn't help, the problem is more likely a driver or hardware issue than a stack corruption issue. Update or reinstall the network adapter driver from Device Manager, and if it's a laptop, try disabling and re-enabling the adapter, or test with a USB Ethernet adapter to rule out a failing onboard NIC.