WiFi Connected But No Internet

WiFi Connected But No Internet Access: Diagnostic Guide

Connecting to a Wi-Fi access point successfully only to find you cannot load web pages is a common networking issue. This problem indicates that while the local wireless link between your client device and the router access point is active, the router is unable to communicate with the broader internet, or there is an configuration mismatch blocking IP routing.

To troubleshoot this issue, it is helpful to understand the boundary between your local network (LAN) and the public network (WAN). The local connection to the router does not guarantee an active link to your ISP.

LAN vs. WAN Boundaries and the OSI Model

Your local area network (LAN) consists of your devices connected to the router via Wi-Fi or Ethernet. This operates primarily at Layer 1 (Physical) and Layer 2 (Data Link) of the Open Systems Interconnection (OSI) model. When your device connects to the Wi-Fi radio, it establishes a physical and data-link connection (verifying WPA2/WPA3 security keys and associating MAC addresses).

The wide area network (WAN) is the network interface connecting your router to the Internet Service Provider (ISP) and the rest of the web, operating at Layer 3 (Network). A "Connected, No Internet" status means the Layer 2 LAN connection is functioning perfectly (your device can speak to the router), but the Layer 3 path between the router and the WAN is broken, or your device has been assigned an invalid routing profile that blocks it from accessing the WAN gateway.

DHCP Lease Conflicts, the DORA Handshake, and APIPA Configuration

A frequent cause of local network routing blocks is a conflict in Dynamic Host Configuration Protocol (DHCP) lease allocations. The DHCP process follows a four-step handshake known as DORA:

1. 1Discover: The client broadcasts a request looking for a DHCP server on the local link.
2. 2Offer: The DHCP server (your router) responds with an available IP address, subnet mask, default gateway, and DNS servers.
3. 3Request: The client requests the offered IP address.
4. 4Acknowledge: The server confirms the lease and registers the client's MAC address.

If two devices are assigned the same local IP address, or if a device's network configuration is stale, the router cannot route public traffic to it. Furthermore, if your device fails to receive any IP configuration from the router's DHCP server, it will self-assign an Automatic Private IP Address (APIPA) in the range 169.254.0.1 to 169.254.255.254. An APIPA address indicates a complete breakdown in communication with the router's DHCP service. You must renew your DHCP lease or manually bind a static IP address within the router's active subnet mask (usually 255.255.255.0).

WAN Interface Drop Symptoms & Hardware Diagnostics

If multiple devices on your network show the "No Internet" status, the issue is likely at the router's WAN interface or modem level. Check the physical connections:

1. 1Modem Status Lights: Look at the LEDs on your broadband modem. The "Online", "Sync", or "WAN" indicator must be solid green or blue. If it is blinking amber, red, or turned off, the modem has lost its connection to the ISP.
2. 2Fiber ONT Optical Power Levels: If you have a fiber-to-the-home (FTTH) setup, inspect the Optical Network Terminal (ONT). A red "LOS" (Loss of Signal) light indicates that the optical fiber is bent, broken, or receiving insufficient light levels (typically below -27 dBm).
3. 3WAN Ethernet Cables: Ensure the cable connecting the modem's LAN port to the router's WAN port is a high-quality Category 5e (Cat5e) or Category 6 (Cat6) copper patch cable. Damaged RJ45 clips can cause intermittent WAN port link drops.

Adware, VPN, and Proxy Conflicts

Security software and virtual private networks (VPNs) create virtual network adapters and edit your system's routing tables. If a VPN tunnel disconnects abruptly or its "Kill Switch" engages, it will block all traffic outside the secure tunnel, leading to a "Connected, No Internet" state. Similarly, misconfigured proxy servers, third-party firewalls, or adware can inject themselves into the TCP/IP stack, preventing standard HTTP/HTTPS traffic from reaching the default gateway.

Section 1: What Does "WiFi Connected But No Internet" Mean?

The message "WiFi Connected, No Internet Access" or the yellow warning triangle on your network icon means your operating system has detected that while your device is connected to the local Wi-Fi network, it cannot reach the internet. Technically, your device passed the local connection phase but failed the internet reachability check.

Modern operating systems run a background internet connectivity probe to verify network status:

• Windows NCSI (Network Connectivity Status Indicator): Windows attempts to download a small text file from http://www.msftconnecttest.com/connecttest.txt and checks if it contains the text "Microsoft Connect Test". It also performs a DNS resolution lookup for dns.msftncsi.com, which should return the IP address 131.107.255.255. If either check fails, the system displays the yellow warning triangle.
• Android Captive Portal Detection: Android sends an HTTP GET request to http://connectivitycheck.gstatic.com/generate_204. If it receives an HTTP status code 204 (No Content), it knows the connection is fully open. If it receives a redirect or an HTTP 200, it flags the network as having a captive portal (requiring login) or redirects to a portal login page. If the request fails entirely, it shows a cross next to the Wi-Fi icon.
• Apple iOS/macOS Captive Portal Assistant: Apple devices request a page from http://captive.apple.com/hotspot-detect.html expecting a specific signature. If it is blocked or redirected, Apple launches the Captive Portal screen.

This does not necessarily mean your router is broken. It could mean:

• Your ISP is experiencing an outage in your area
• Your router's WAN configuration is incorrect
• DNS servers are failing to resolve hostnames
• Your device has an APIPA address (169.254.x.x) instead of a valid LAN IP
• A firewall, VPN, or antivirus is intercepting all outbound connections
• Your router's NAT (Network Address Translation) table has become corrupted

Section 2: Most Common Causes

ISP Outage and GPON Line Issues

Your Internet Service Provider may be experiencing a partial or total network outage in your area. This is one of the most common reasons multiple devices on your network all lose internet simultaneously while the Wi-Fi radio still functions normally. Outages can occur due to physical fiber cuts, upstream routing changes, power failures at local distribution cabinets, or maintenance on your provider's Gigabit Passive Optical Network (GPON) splitters. GPON splitters divide a single optical feed from the OLT (Optical Line Terminal) at the central office into up to 64 individual fiber runs, meaning any hardware issue at this critical splitting node affects dozens of households simultaneously. Check your ISP's status page, Twitter feed, or use a service like Downdetector to confirm whether a regional outage is active.

Router Failure or Firmware Crash

Routers run embedded operating systems that can crash or deadlock. A router experiencing a memory overflow, firmware exception, or overheating condition may continue to broadcast Wi-Fi SSIDs and respond to local ARP requests while failing to process any WAN routing tasks. In particular, the NAT connection tracking table (conntrack) has a finite size. If torrent clients or smart home appliances open thousands of concurrent connections, the conntrack table fills up, blocking any new outbound connections. A factory reset or firmware update often resolves this.

DNS Issues

The Domain Name System is the backbone of all internet navigation. When your DNS resolver fails — whether because your ISP's name servers are down, your manually configured DNS entries are incorrect, or your router's internal DNS forwarder has crashed — all hostnames (google.com, youtube.com, etc.) fail to resolve. Switching to public DNS (Cloudflare 1.1.1.1 or Google 8.8.8.8) bypasses this layer entirely.

DHCP Issues

Your router assigns local IP addresses via DHCP. If the DHCP server leases run out (too many devices competing for a small DHCP pool), if lease records become corrupted, or if the DHCP daemon on your router crashes, your device will fail to receive a valid IP address. You will see addresses beginning with 169.254.x.x (APIPA range), indicating your device gave up waiting and self-assigned an address that cannot route beyond your local link.

Gateway Problems

The default gateway is the router's IP address that all traffic is forwarded through. If your device's route table does not have a valid default gateway entry, or if the gateway IP is unreachable, all external traffic fails immediately. This can happen after a network adapter driver update, a VPN software installation, or a Windows update that corrupts the routing table.

VPN Conflicts

VPN software creates virtual network adapters and inserts custom routing rules that can override your physical network adapter's default gateway. If the VPN fails mid-session or its kill-switch activates, all internet traffic is blocked by design. Disabling the VPN temporarily is the fastest diagnostic test.

Firewall Conflicts

Third-party firewall software or Windows Defender Firewall with overly aggressive rules can block all outbound TCP/UDP connections. Some antivirus software updates introduce rules that block HTTPS traffic on port 443, rendering all modern websites inaccessible even though the network layer is functional.

Section 3: Quick Fixes

Before diving into platform-specific diagnostics, try these universal fixes:

1. 1Restart your router and modem. Unplug both devices from power. Wait 30 seconds. This allows the capacitors in the power adapters to discharge completely, resetting the volatile memory. Plug in the modem first, wait 60 seconds for the online indicator to become solid. Then plug in the router and wait another 60 seconds.
2. 2Reconnect your device to Wi-Fi. On your device, forget the network and reconnect. This clears the stored DHCP lease and forces a fresh IP assignment.
3. 3Turn airplane mode on and off (on mobile devices). This triggers a full Wi-Fi radio reset.
4. 4Check other devices. If all devices lose internet simultaneously, the problem is on the router/ISP side. If only one device fails, the problem is device-specific.
5. 5Try a different DNS. Change your DNS manually to 1.1.1.1 or 8.8.8.8. If the internet resumes working, your ISP's DNS was the problem.

Section 4: Windows Fixes

Step 1 — Release and Renew DHCP Lease Open Command Prompt as Administrator (search "cmd", right-click, Run as Administrator):

ipconfig /release
ipconfig /renew

This releases your current IP address and requests a fresh one from the router.

Step 2 — Flush DNS Cache

ipconfig /flushdns

This clears the local resolver cache of any stale or corrupted DNS records.

Step 3 — Reset TCP/IP Stack and Winsock

netsh int ip reset
netsh winsock reset

This resets the network adapter registry settings and repairs the Winsock LSP stack. Reboot after running these commands.

Step 4 — Change DNS Servers Settings → Network & Internet → Wi-Fi → Hardware Properties → DNS Server Assignment. Switch to Manual. Enable IPv4 and enter Primary: 1.1.1.1, Secondary: 1.0.0.1.

Step 5 — Disable IPv6 Control Panel → Network and Sharing Center → Change Adapter Settings. Right-click your Wi-Fi adapter → Properties. Uncheck "Internet Protocol Version 6 (TCP/IPv6)" to see if an IPv6 configuration issue is blocking routing.

Step 6 — Reinstall Network Adapter Drivers Open Device Manager (devmgmt.msc), expand "Network adapters", right-click your wireless card (e.g., Intel Wi-Fi 6E AX211), and select "Uninstall device". Do NOT check the option to delete driver software. Restart your PC; Windows will automatically reinstall the driver.

Section 5: macOS Fixes

Step 1 — Renew DHCP Lease System Settings → Network → Wi-Fi → Details → Renew DHCP Lease button.

Step 2 — Flush DNS Cache Open Terminal and run:

sudo killall -HUP mDNSResponder

Step 3 — Forget and Reconnect to Wi-Fi System Settings → Network → Wi-Fi → tap the details of your network → Forget This Network. Reconnect.

Step 4 — Change DNS on macOS System Settings → Network → Wi-Fi → Details → DNS tab. Add 1.1.1.1 and 8.8.8.8. Remove ISP DNS entries.

Step 5 — Check Proxy Settings System Settings → Network → Wi-Fi → Details → Proxies tab. Ensure no proxies are configured unless intentionally set.

Step 6 — Delete System Configuration PLIST Files To fix deep-seated macOS network stack bugs, open Terminal and run:

sudo rm /Library/Preferences/SystemConfiguration/NetworkInterfaces.plist
sudo rm /Library/Preferences/SystemConfiguration/preferences.plist

Reboot your Mac. This forces macOS to recreate clean default network configuration files.

Section 6: Android Fixes

Step 1 — Toggle Wi-Fi Off and On Swipe down the notification panel and tap the Wi-Fi icon to disable, wait 10 seconds, then re-enable.

Step 2 — Forget and Reconnect Settings → Wi-Fi → Long-press your network → Forget → Reconnect.

Step 3 — Set Static DNS Settings → Wi-Fi → Long-press network → Modify Network → Advanced Options → IP Settings: Static. Enter DNS 1: 1.1.1.1, DNS 2: 8.8.8.8.

Step 4 — Use Private DNS (Android 9+) Settings → Network & Internet → Advanced → Private DNS → Private DNS provider hostname: one.one.one.one. This uses encrypted DNS-over-TLS.

Step 5 — Clear Network Settings Settings → System → Reset options → Reset Wi-Fi, mobile & Bluetooth. This restores all wireless settings to default.

Section 7: iPhone/iPad Fixes

Step 1 — Toggle Airplane Mode Control Center → airplane icon → wait 15 seconds → tap again.

Step 2 — Forget Network and Reconnect Settings → Wi-Fi → tap the "i" icon → Forget This Network → Reconnect.

Step 3 — Configure Custom DNS Settings → Wi-Fi → "i" icon → Configure DNS → Manual → Add Server: 1.1.1.1 and 8.8.8.8.

Step 4 — Renew DHCP Lease Settings → Wi-Fi → "i" icon → tap "Renew Lease".

Step 5 — Disable MAC Address Randomization (Private Wi-Fi Address) Settings → Wi-Fi → "i" icon → toggle off "Private Wi-Fi Address". Some routers block devices that frequently rotate MAC addresses to prevent MAC spoofing.

Step 6 — Reset Network Settings (Last Resort) Settings → General → Transfer or Reset iPhone → Reset → Reset Network Settings. WARNING: This erases all Wi-Fi passwords and VPN settings.

Section 8: Router Troubleshooting

Check Router Admin Panel

Log in to your router's admin interface (typically 192.168.1.1, 192.168.0.1, or 10.0.0.1). Verify:

• WAN IP address is assigned (not 0.0.0.0 or empty)
• DNS server IPs are populated
• Gateway IP is present and correct

PPPoE Re-Authentication

If you use DSL or fiber with PPPoE authentication, re-enter your ISP username and password in the WAN settings and click Reconnect.

Factory Reset the Router

Hold the physical reset button on the back of the device using a paperclip for 10-30 seconds until the LEDs flash. Reconfigure from scratch with your ISP credentials.

Update Router Firmware

Log into router admin, find Firmware Update section, and apply any available updates. Many modern routers support automatic updates.

Check DHCP Pool and IP Exclusions

Verify the DHCP lease pool is large enough. If you have many smart home devices and guests, you may be exhausting the available IP pool. Adjust the lease time from 24 hours to 2 hours to recycle unused addresses faster.

Section 9: Advanced Diagnostics

ipconfig — Check IP Configuration (Windows)

ipconfig /all

Verify IPv4 Address is in 192.168.x.x range (NOT 169.254.x.x), Default Gateway matches your router IP, and DNS Servers show valid IPs.

ping — Test Layer by Layer and ICMP Routing

The ping command uses the Internet Control Message Protocol (ICMP) Echo Request and Echo Reply packets to test the reachability of a host on an Internet Protocol (IP) network. When you run ping 8.8.8.8, your operating system sends a 32-byte ICMP echo request packet to the destination address. It then waits for a response. If a reply is received within a specific timeout threshold, the tool prints the round-trip time (RTT) in milliseconds. This tells you if the packet routing is complete. If you get a 'Request Timed Out' error, it means the packet was sent but no reply was received, which happens when a router along the way drops ICMP packets or the host is offline. If you get a 'Destination Host Unreachable' error, it means your local device could not find a route to the destination IP address, which indicates a local gateway routing configuration issue.

ping 192.168.1.1        (Test router reachability - local link)
ping 8.8.8.8            (Test internet IP connectivity - bypasses DNS)
ping google.com         (Test DNS resolution + internet connectivity)

If the first ping fails, your device cannot reach the router. If the second fails, your router cannot reach the internet. If only the third fails, DNS is the problem.

tracert — Trace the Network Route

tracert 8.8.8.8

Shows every routing hop from your device to Google's servers. If it stops at the first hop (your router), the WAN connection is the problem. If it stops further out, there is an upstream ISP issue.

nslookup — Test DNS Resolution

nslookup google.com
nslookup google.com 1.1.1.1

If the second works but the first doesn't, your router's DNS forwarder or ISP DNS is the problem. Switch to Cloudflare DNS immediately.

Section 10: When To Contact Your ISP

Contact your Internet Service Provider if:

• Multiple devices all show "No Internet" simultaneously after a full router and modem restart
• The modem's WAN light is off, blinking red/amber, or showing a "No Sync" pattern even after a power cycle
• You have factory reset the router and re-entered ISP credentials, but the WAN IP remains 0.0.0.0
• The router admin panel shows WAN status as "Disconnected" or "Authentication Failed" with correct credentials
• The outage is confirmed regional — verified through Downdetector or neighbors reporting the same issue
• Your modem is ISP-provided (rented equipment) — it may need remote reconfiguration by your provider

When calling your ISP, have ready:

1. 1Your account number or the phone number associated with the account
2. 2The modem's serial number and MAC address (printed on the device label)
3. 3The exact LED patterns visible on the modem
4. 4The error or IP status shown in your router admin panel
5. 5Whether the issue affects all devices or only specific ones