The Frustrating Paradox: Connected, Assigned an IP, Yet Completely Offline
Few computing scenarios are as exasperating as launching your web browser, being greeted by a yellow exclamation mark or a globe icon with a slash through it, and seeing the infamous status message: "Connected, no internet."
You open your operating system settings or type ipconfig into Command Prompt, and to your confusion, everything looks superficially normal: your network adapter shows an IPv4 address like 192.168.1.142 or 10.0.0.85. If your computer was given an IP address, why can’t it load a single webpage, stream music, or connect to chat servers?
Having an IP address merely proves that your computer’s network interface card (NIC) has initialized an addressing layer—it does not prove that traffic can traverse past your local machine or through your router to the wider World Wide Web. In this professional diagnostic guide, we will walk through the exact sequence network administrators use to triage this issue in under two minutes, pinpoint whether the fault lies in your PC, your router, or your ISP, and restore your connection.
The Critical Step 0: Check If Your IP Is an "APIPA Ghost" (169.254.x.x)
Before testing connectivity, you must examine the actual numbers of the IP address assigned to your PC. Not all IP addresses are created equal.
If your IPv4 address begins with 169.254 (such as 169.254.120.45), you do not have a real IP address from your router. You are looking at an Automatic Private IP Addressing (APIPA) fallback address.
⚠️ What APIPA (169.254.x.x) Means:
When a PC’s network card broadcasts a DHCP Discover packet requesting an IP address, and your router fails to answer within a specified timeout (due to DHCP pool exhaustion, Wi-Fi authentication issues, or a frozen router daemon), Windows, macOS, and Linux automatically assign themselves a temporary 169.254.x.x address. Your PC thinks it is connected to a local link, but it has no gateway and cannot talk to any other device.
If your IP is in the 169.254 range, skip ahead to the DHCP and router lease renewal section. But if your IP begins with 192.168.x.x, 10.x.x.x, or 172.16-31.x.x, you have a legitimate private LAN address. In that case, here is the absolute first thing you must check.
The FIRST Thing You Check: Ping Your Default Gateway
If your computer has a valid local IP address, the single most illuminating first action is to test whether your PC can physically exchange data packets with your Default Gateway (the local IP of your router).
The Default Gateway is your computer’s sole doorway to the outside world. If your PC cannot talk to its gateway, nothing on the global internet will ever load. Conversely, if your PC can talk to its gateway with zero packet loss, you have instantly eliminated your computer's Wi-Fi card, Ethernet port, patch cable, and local operating system drivers from suspicion.
How to Find and Ping Your Default Gateway
Follow these steps depending on your operating system:
On Windows (CMD or PowerShell):
- Press Win + R, type
cmd, and press Enter.
- Type
ipconfig and press Enter. Look for the active network adapter and note the Default Gateway (commonly 192.168.1.1, 192.168.0.1, or 10.0.0.1).
- Type the ping command followed by that gateway address:
ping 192.168.1.1
On macOS or Linux (Terminal):
Open your Terminal app and run:
# Find the gateway IP
route -n get default | grep gateway # macOS
ip route show default # Linux
# Ping the gateway (send 4 packets)
ping -c 4 192.168.1.1
Interpreting the Gateway Ping Results
This single command splits your troubleshooting journey into two distinct halves:
- Scenario A: Request Timed Out or Destination Host Unreachable. Your PC cannot talk to the router. The issue is strictly local to your premises—Wi-Fi encryption errors, duplicate static IP collisions, faulty cables, or corrupted NIC driver state.
- Scenario B: Reply from 192.168.1.1: bytes=32 time<1ms TTL=64. Your PC-to-router local link is 100% healthy! The problem is further upstream: a DNS server failure, an ISP WAN outage, or a router routing table freeze.
Figure 1: The 4-tier diagnostic ladder isolating network failures from local interface to WAN DNS.
The 4-Tier Network Diagnostic Ladder
When triaging network connectivity, never guess blindly. Follow the standard four-tier diagnostic ladder from the inside out:
| Diagnostic Tier |
Command to Execute |
What It Validates |
Failure Indication |
| Tier 1: Local Loopback |
ping 127.0.0.1 |
Internal TCP/IP software stack on OS |
Corrupted Winsock or network driver |
| Tier 2: Default Gateway |
ping [Gateway IP] |
Physical link, switch port, and router LAN |
Bad cable, Wi-Fi channel drop, subnet mismatch |
| Tier 3: Public Internet IP |
ping 1.1.1.1 or ping 8.8.8.8 |
WAN routing to the outside world (bypasses DNS) |
ISP outage, modem offline, WAN PPPoE dropped |
| Tier 4: DNS Resolution |
nslookup google.com |
Domain Name resolution capability |
Dead DNS server, Pi-hole lockup, DNS poisoning |
Notice Tier 3 and Tier 4: this is where 70% of "connected, no internet" mysteries are solved. If ping 8.8.8.8 works, but typing google.com into your browser times out, your internet is actually working perfectly! The only component broken is your DNS server, which is unable to translate human domain names into numerical IP addresses.
The 6 Most Common Root Causes (And How to Fix Them)
1. DNS Deadlock (The "Silent Killer" of Web Browsing)
When you subscribe to an internet service provider (ISP), your router defaults to using the ISP's proprietary DNS servers. If those servers experience an outage, DDoS attack, or maintenance downtime, your browser will display "No Internet Connection" or DNS_PROBE_FINISHED_NO_INTERNET even though your underlying connection is active.
The Fix: Switch to High-Performance Public Anycast DNS
- Cloudflare DNS: Primary
1.1.1.1 · Secondary 1.0.0.1
- Google Public DNS: Primary
8.8.8.8 · Secondary 8.8.4.4
- Quad9 (Security Focused): Primary
9.9.9.9 · Secondary 149.112.112.112
To configure on Windows 11:
- Open Settings > Network & internet > Wi-Fi (or Ethernet) > Hardware properties.
- Next to DNS server assignment, click Edit.
- Select Manual, enable IPv4, enter
1.1.1.1 for Preferred DNS and 8.8.8.8 for Alternate DNS, and save.
2. Corrupted Winsock Catalog and TCP/IP Stack
Windows maintains a core networking driver framework known as Winsock (Windows Sockets). If third-party antivirus utilities, VPN software uninstallation, or sudden power drops corrupt the Winsock catalog, your PC will bind an IP address but refuse to serialize outbound TCP packets.
The Fix: Full TCP/IP & Winsock Flush
Open Command Prompt as Administrator and run this exact sequence of commands:
netsh winsock reset
netsh int ip reset
ipconfig /release
ipconfig /flushdns
ipconfig /renew
Once complete, restart your computer to apply the clean network socket catalog.
3. Rogue VPN Kill-Switches and Virtual Network Adapters
Modern VPN clients (NordVPN, ExpressVPN, WireGuard, Tailscale) and virtualization platforms (Docker Desktop, Hyper-V, VMware) install virtual network interface cards (vNICs) with custom routing table metrics.
If a VPN client crashes or its "Kill Switch" feature remains engaged after closing the app, it deliberately blocks all non-tunneled outbound traffic through your physical adapter, leaving you stranded with an IP address and no internet access.
The Fix:
- Open your VPN client, reconnect, and disconnect cleanly.
- Temporarily disable the VPN "Kill Switch" inside its settings.
- In Windows, open Control Panel > Network and Sharing Center > Change adapter settings, right-click any unused TAP, TUN, or virtual adapters, and select Disable.
4. Subnet Mask & Duplicate Static IP Collisions
If another device on your network (like a smart TV, security camera, or NAS) was configured with a static IP matching your computer's DHCP reservation (for example, both claim 192.168.1.100), an Address Resolution Protocol (ARP) collision occurs. The router gets confused over which MAC address owns the traffic, causing intermittent packet drops or complete severance.
Similarly, if your PC was accidentally configured with a static subnet mask of 255.255.0.0 while your router operates on a 255.255.255.0 (/24) boundary, your computer cannot calculate its broadcast domain correctly.
The Fix: Force your network adapter to obtain both its IP address and DNS server address automatically via DHCP in adapter properties.
5. Captive Portal Interception
If you are on a hotel, cafe, airport, or corporate guest Wi-Fi network, your computer receives a valid IP address immediately upon connecting. However, the router's internal firewall intercepts all outgoing port 80/443 traffic until you accept terms of service or log in through a browser splash screen.
Because modern browsers enforce HTTPS everywhere with Strict Transport Security (HSTS), the captive portal cannot inject its HTTP redirect, resulting in an endless "No Internet" status.
The Fix: Open your browser and navigate to a plain, unencrypted HTTP test page: http://neverssl.com or http://1.1.1.1. This forces the router's captive portal gateway to intercept the session and display the login screen.
6. Router WAN / Optical Network Terminal (ONT) Lockup
Sometimes your local network is operating flawlessly, but the router itself has lost its upstream link to the ISP. Modern routers feature multiple independent microchips: one chip handles the local Ethernet switch and Wi-Fi access point (LAN), while another modem chip handles the fiber, coaxial, or DSL connection (WAN).
If the WAN interface locks up, your computer will happily communicate with the router, obtain an IP via DHCP, and show "Connected", while the router itself has zero throughput to the internet.
The Fix: The Proper 60-Second Power Cycle
- Unplug both your modem (or fiber ONT) and your standalone Wi-Fi router from wall power.
- Wait a full 60 seconds (this allows the capacitors to completely drain and forces the ISP line card to register a session drop).
- Plug in the modem/ONT first. Wait 2 minutes until the WAN/PON/Internet light turns solid green or white.
- Plug in your Wi-Fi router. Wait 90 seconds for DHCP leases to reinitialize.
Quick-Reference Troubleshooting Matrix
| Symptom |
Ping Gateway |
Ping 8.8.8.8 |
Root Cause |
Direct Remedy |
| IP is 169.254.x.x |
N/A |
N/A |
DHCP assignment failed |
ipconfig /renew or reboot router |
| Valid IP, Gateway Unreachable |
Failed |
Failed |
Local physical/wireless link break |
Check Wi-Fi password, replace cable, reinstall NIC driver |
| Gateway OK, 8.8.8.8 Unreachable |
Passed |
Failed |
Router has no WAN internet access |
Reboot modem/ONT; check ISP service status |
| 8.8.8.8 OK, Webpages Won't Load |
Passed |
Passed |
DNS resolver failure |
Assign manual DNS (1.1.1.1 & 8.8.8.8); flush DNS |
Frequently Asked Questions (FAQ)
Why does my smartphone have Wi-Fi on the same network, but my PC says "No Internet"?
If your phone can browse the web on the identical Wi-Fi network, the router and ISP connection are operating normally. The problem is localized strictly to your PC. The most common reasons are: corrupted local DNS cache on the PC, a lingering VPN kill-switch blocking non-encrypted packets, a third-party antivirus firewall blocking outbound port 80/443, or a corrupt wireless network adapter driver.
Can an incorrect date and time on my computer cause "No Internet"?
Yes, absolutely. Secure web browsing relies on SSL/TLS encryption certificates, which have strict validity date ranges. If your PC's CMOS battery dies or its clock desynchronizes by more than a few minutes, every HTTPS connection will fail security verification, causing browsers to report connection failures that appear identical to having no internet.
What does "DNS_PROBE_FINISHED_NO_INTERNET" mean?
This is a standard Chromium error code indicating that the browser attempted to resolve a domain name (such as wikipedia.org) through your configured DNS servers, and the lookup failed due to either a dead DNS server or an offline network connection. Running ping 1.1.1.1 will immediately verify whether you have internet connectivity or just a broken DNS path.
Summary: The 60-Second Action Checklist
Whenever you encounter a PC that has an IP address but no internet, remember this golden checklist:
- Verify the IP range: Ensure it is not a self-assigned
169.254.x.x APIPA address.
- Ping the Default Gateway: Run
ping [gateway] to prove your local hardware link is intact.
- Ping 1.1.1.1 or 8.8.8.8: Test whether you have raw IP routing past your router.
- Test DNS resolution: Run
nslookup google.com. If it fails, configure Cloudflare (1.1.1.1) or Google DNS (8.8.8.8).
- Reset the network stack: Run
netsh winsock reset and netsh int ip reset if all else fails.
By following this methodical tier-by-tier approach, you eliminate guesswork and resolve the problem rapidly every single time.