Wi-Fi Connected But No Internet Access? The Ultimate Master Diagnostic Guide

Time: 15 mins Level: Beginner

By StepDiag Engineering Team

Reviewed by Ibraheem Taofeeq Opeyemi

Wi-Fi connected but no internet indicates a local wireless handshake succeeded, but DNS routing, DHCP IP assignment, or WAN connectivity failed. Solve it with this step-by-step master diagnostic guide.

Full Diagnostic Tree & Step-by-Step Overview

1. Is the internet missing on ALL connected devices, or just THIS specific device?

All devices on the Wi-Fi have no internet access.
Other devices work fine; the issue is isolated to this single device.

Inspect your Router and Modem Status Lights

The Internet/WAN light is Red, Amber, or completely OFF.
The Internet/WAN light is solid Green or Blue.

Perform a Sequential Hardware Power Drain & Check ISP Status

Solution: An unlit or red WAN light means your modem has lost its synchronization handshake with your ISP's central office.<ol><li>Unplug Power: Disconnect the power cords from both your modem and Wi-Fi router.</li><li>Drain Capacitors: Wait a full 60 seconds. This clears volatile RAM memory and releases stale IP assignments from your ISP's Gateway.</li><li>Power Up Modem First: Plug in the modem only. Wait 2–3 minutes until the Upstream/Downstream and Online lights turn solid green/blue.</li><li>Power Up Router Second: Plug in your Wi-Fi router. Wait 2 minutes for wireless broadcasting to initialize.</li></ol>Note: If the internet light remains red or off after restarting, check your mobile carrier for local outage reports on Downdetector or contact your ISP. Physical line damage or node maintenance is likely in progress.

Override ISP DNS Servers at the Gateway Level

Solution: If the router's WAN light shows an active connection, your ISP's default Domain Name System (DNS) servers are likely down or dropping requests. DNS translates human URLs (like google.com) into numeric IP addresses.<ol><li>Open a web browser on a device connected to the network and type your router's gateway IP (usually <code>192.168.1.1</code> or <code>192.168.0.1</code>).</li><li>Log into your router admin console using your admin credentials.</li><li>Navigate to Advanced Settings > Network / WAN Options > DNS Settings.</li><li>Switch DNS configuration from Automatic / ISP Provider to Manual.</li><li>Enter public, secure DNS servers:<ul><li>Primary DNS: <code>1.1.1.1</code> (Cloudflare) or <code>8.8.8.8</code> (Google)</li><li>Secondary DNS: <code>1.0.0.1</code> (Cloudflare) or <code>8.8.4.4</code> (Google)</li></ul></li><li>Save settings and reboot the router.</li></ol>

Select the Operating System of the Affected Device

Windows 11 or Windows 10
macOS (MacBook / iMac)
iOS (iPhone) or Android
Linux (Ubuntu / Debian / Arch)

Check Your Windows Assigned IP Address (APIPA Check)

My IP starts with 169.254.x.x (Self-assigned APIPA failure).
My IP starts with 192.168.x.x or 10.x.x.x, but internet still fails.

Fix Automatic Private IP Addressing (APIPA 169.254.x.x) & Fast Startup

Solution: An IP address starting with <code>169.254</code> means Windows failed to reach the router's DHCP server and auto-assigned a useless internal dummy IP. This is frequently caused by Windows Fast Startup locking the Network Adapter during hybrid hibernation.<ol><li>Press Win + R, type <code>powercfg.cpl</code> and hit Enter.</li><li>Click 'Choose what the power buttons do' on the left side.</li><li>Click 'Change settings that are currently unavailable'.</li><li>Uncheck 'Turn on fast startup (recommended)' and click Save Changes.</li><li>Open Command Prompt as Administrator, run <code>ipconfig /release</code> followed by <code>ipconfig /renew</code>, then perform a complete System Restart.</li></ol>

Execute a Complete Command-Line Network Stack Reset

Solution: This deep reset purges corrupted Winsock catalog entries, flushes local DNS resolvers, and forces a low-level driver re-initialization.<ol><li>Press the Windows Key, type <code>cmd</code>, right-click Command Prompt, and select Run as administrator.</li><li>Execute the following commands in exact sequential order, pressing Enter after each:</li></ol><pre><code>netsh winsock reset
netsh int ip reset
ipconfig /release
ipconfig /flushdns
ipconfig /renew</code></pre><ol start="3"><li>Reboot your computer immediately to finalize the registry changes.</li></ol>

Fix Time Synchronization, IPv6 Conflicts, and Security Shields

Solution: If your network stack is clean but traffic is blocked, check these three subtle culprits:<ul><li>System Clock Desynchronization: SSL/TLS security certificates require accurate time. Go to Settings > Time & Language > Date & Time and click 'Sync now' under Additional Settings.</li><li>IPv6 Handshake Drops: Many ISPs do not properly support IPv6 routing. Go to Settings > Network & Internet > Advanced network settings > Change adapter options. Right-click your Wi-Fi adapter > Properties, uncheck Internet Protocol Version 6 (TCP/IPv6), and click OK.</li><li>Antivirus/VPN Web Shields: Temporarily disable active VPN clients (NordVPN, ExpressVPN) or third-party web shields (Avast, Bitdefender, Malwarebytes) which can hook into the network stack and drop packets.</li></ul>

Renew DHCP Lease, Flush mDNSResponder, and Delete Network Plists

Solution: macOS network issues are usually tied to cached mDNS corruption or corrupted System Configuration preference files.<ol><li>Renew DHCP Lease: Go to System Settings > Wi-Fi > Details next to your network. Click the TCP/IP tab and click Renew DHCP Lease.</li><li>Flush macOS DNS: Open Terminal (Cmd + Space, type <code>Terminal</code>) and run:</li></ol><pre><code>sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder</code></pre><ol start="3"><li>Purge Network Preferences (If necessary): Open Finder, press <code>Cmd + Shift + G</code>, go to <code>/Library/Preferences/SystemConfiguration/</code>, delete the following files, and reboot your Mac:<ul><li><code>com.apple.airport.preferences.plist</code></li><li><code>NetworkInterfaces.plist</code></li><li><code>preferences.plist</code></li></ul></li></ol>

Disable Private MAC Address Randomization & Reset Network Settings

Solution: Modern iOS and Android devices use randomized hardware (MAC) addresses for privacy. Many home routers refuse IP leases to unrecognized rotating MAC addresses.<ul><li>iPhone (iOS): Go to Settings > Wi-Fi, tap the (i) icon next to your network, and toggle Private Wi-Fi Address to OFF. Tap Forget This Network, then reconnect.</li><li>Android: Go to Settings > Network & Internet > Wi-Fi, tap the gear icon next to your network. Tap Privacy and select Use Device MAC instead of Randomized MAC. Reconnect.</li><li>Nuclear Option: If problems persist, perform a Network Reset (Settings > General > Transfer or Reset iPhone > Reset > Reset Network Settings, or Android equivalent). This resets all Wi-Fi, Bluetooth, and cellular configurations.</li></ul>

Reset NetworkManager and Systemd-Resolved on Linux

Solution: For Linux users experiencing Wi-Fi connection without internet access, restart system network daemons and verify DNS routing via systemd-resolved.<ol><li>Restart NetworkManager: Execute <code>sudo systemctl restart NetworkManager</code></li><li>Flush DNS & Restart Resolver: Run:</li></ol><pre><code>sudo systemd-resolve --flush-caches
sudo systemctl restart systemd-resolved</code></pre><ol start="3"><li>Check Name Resolution: Run <code>resolvectl status</code> to confirm your upstream DNS server is assigned correctly. If empty, manually add <code>nameserver 1.1.1.1</code> to <code>/etc/resolv.conf</code>.</li></ol>

Related Diagnostic Guides

WinSxS Folder Too Large: Component Store Cleanup Diagnostic

Slow Boot After SSD Clone: Boot Trace Diagnostic

Windows 11 Search Bar Not Typing - CTF Loader Diagnostic

Desktop Icons Keep Rearranging on Reboot - Registry Fix Tree

Windows Activation Error 0xC004F213 After Hardware Change

Subscribe to StepDiag

Embed Guide on Your Website