Limited connectivity: What It Means and How to Fix It

What "Limited Connectivity" Actually Means

Windows is authenticated on the network — the physical or wireless link is up — but the DHCP exchange did not produce a valid routable IP address. Without a valid IP, gateway address, and DNS server, the PC cannot reach the internet or, in many cases, even the router itself.

When DHCP fails completely, Windows assigns itself a link-local address in the 169.254.0.0/16 range (APIPA — Automatic Private IP Addressing). You can confirm this by running ipconfig in Command Prompt and looking at the IPv4 address on the affected adapter. A 169.254.x.x address is a reliable sign that no DHCP lease was obtained. Alternatively, the adapter may have an old lease that points to a gateway that is no longer reachable, which produces the "No internet access" variant of the same problem.

Step-by-Step Diagnosis

Work through these commands in an Administrator Command Prompt before applying fixes. Understanding exactly where connectivity breaks saves time.

1. ipconfig /all — confirms whether a valid IP address, subnet mask, default gateway, and DNS server are assigned. A 169.254.x.x address means DHCP failed entirely.
2. ping <gateway IP> — ping the default gateway shown in ipconfig. If this fails, the PC cannot reach the router even on the local network. Causes: wrong IP, bad cable, router firewall blocking ICMP.
3. ping 8.8.8.8 — bypasses DNS and tests raw internet reachability. If the gateway ping succeeds but this fails, the router has internet connectivity problems.
4. ping google.com — tests DNS resolution. If 8.8.8.8 succeeds but google.com fails, DNS is the remaining problem.

Common Causes

• DHCP server not responding — the router's DHCP service crashed, was disabled, or the router itself is unresponsive. Affects all devices on the network simultaneously.
• Duplicate IP address — two devices on the LAN share the same IP. Windows detects the conflict and marks the connection as limited. Check the event log for "IP address conflict" entries.
• Incorrect static IP configuration — a manually entered IP address, subnet mask, or gateway that does not match the network. Common after moving a laptop between networks.
• DHCP pool exhausted — the router's DHCP range has no available addresses to lease. This happens in dense environments where many devices have long lease times and the pool is small (e.g., a /24 pool configured as only 50 addresses).
• Corrupt network driver or Winsock catalog — a damaged driver or corrupted TCP/IP stack causes DHCP requests to be malformed or not sent at all. More common after a Windows update or driver change.

How to Fix Limited Connectivity

Step 1: Run Windows' network troubleshooter

Settings → System → Troubleshoot → Other troubleshooters → Network and Internet. It catches DHCP and gateway problems automatically and may apply fixes without further commands.

Step 2: Release and renew the IP address

Open Command Prompt as Administrator and run:

• ipconfig /release — releases the current DHCP lease and removes the IP assignment.
• ipconfig /renew — sends a fresh DHCP discover and attempts to obtain a new lease.

If /renew times out with an error, the router's DHCP server is not responding. Restart the router and try again.

Step 3: Check for a static IP configuration

Settings → Network and Internet → Wi-Fi (or Ethernet) → the connected network → IP assignment. If it is set to Manual, switch it to Automatic (DHCP) unless you have a specific reason for a static address. A static IP misconfigured for a different subnet is a very common cause of this error on laptops.

Step 4: Reset Winsock and TCP/IP stack

Run the following commands as Administrator, then reboot:

• netsh winsock reset — resets the Winsock catalog to a clean state, removing any corrupt layered service providers.
• netsh int ip reset — resets TCP/IP settings including the interface configuration back to defaults.

These commands require a reboot to take effect. After rebooting, DHCP should negotiate normally.

Step 5: Reinstall or update the network driver

Open Device Manager, expand Network Adapters, right-click the affected adapter, and choose Update driver or Uninstall device (then reboot to reinstall). Download the latest driver directly from the NIC manufacturer or laptop vendor's support page rather than relying on Windows Update alone.

Step 6: Restart the router

If multiple devices on the same network show limited connectivity simultaneously, the DHCP server on the router is the problem — not the individual PC. Power-cycle the router (unplug for 30 seconds), wait for it to fully restart, then reconnect.

When the Problem Is the ISP, Not the PC

If all devices on the network have valid local IPs (confirmed via ipconfig) but none can reach the internet, the router has connectivity to your LAN but your ISP connection is down. Signs include: the router admin page loads, pinging the gateway succeeds, but pinging 8.8.8.8 fails. In this case, check the ISP's outage page, reboot the modem separately from the router, and contact support if the outage persists. No amount of Winsock resets or driver updates will fix a problem upstream of your modem.

Still Not Fixed? Rule Out Your Connection

If the steps above did not clear the error, verify the underlying internet connection is healthy. Run a speed test — if download, upload, and ping come back normal, the error was transient or specific to one network profile. If the speed test also fails or shows packet loss, the problem is at the network or ISP layer and needs to be addressed there first.

Frequently Asked Questions

What is the difference between "Limited connectivity" and "No internet, secured"?

Functionally very similar — both indicate the OS cannot reach the internet after connecting. "No internet, secured" (Windows 11) typically means a valid IP was obtained but the internet connectivity check failed. "Limited connectivity" (Windows 10) often indicates a DHCP failure resulting in a 169.254.x.x address. The diagnostic steps and fixes are the same for both.

Why does my IP start with 169.254?

That is an APIPA address — Windows assigned it to itself after DHCP failed. It means no DHCP server responded within the timeout window. The fix is to address why DHCP is not responding: router restart, driver reset, or Winsock reset as described above.