Why does my phone say 'WiFi connected but no internet access' even after restarting?

This usually means your phone received an invalid DHCP lease (often a 169.254.x.x APIPA address) or the router's DNS is unreachable. Try forgetting the network, rebooting the router, then reconnecting. On Android, also try Settings → System → Reset → Reset Wi-Fi, mobile & Bluetooth, then reconnect. If the problem persists only on your phone, set a static IP and DNS of 8.8.8.8 in the WiFi advanced settings.

My Cox Panoramic WiFi says connected but has no internet — what do I do?

First, unplug the Panoramic gateway for 60 seconds (not just 10). If the 'Online' light is solid white after restarting, the gateway is provisioned. If it blinks or shows orange/red, Cox has a provisioning issue. Use the MyAccount app to restart the modem remotely or call Cox support at 1-800-234-3993. Also check cox.com/residential/support for active outages in your area before calling.

Why does my laptop show WiFi connected but no internet only on my home network, not on others?

This is a router-specific configuration issue. Your laptop is connecting successfully to the WiFi radio but the router is not forwarding traffic correctly. Check: (1) Router admin page (usually 192.168.1.1 or 192.168.0.1) → WAN/Internet Status — if it shows 'Disconnected' or '0.0.0.0', the ISP link is down. (2) Check if MAC address filtering is enabled on the router and inadvertently blocking your laptop. (3) Verify the DHCP pool has not been exhausted (too many devices).

How do I fix 'WiFi connected but no internet' on a hotel or public hotspot on Android?

Pull down the notification shade and tap 'Sign in to network' if visible. If not, open Chrome and type 'http://neverssl.com' — this forces the captive portal to appear. If the portal loads but login fails, clear Chrome's cache (Settings → Apps → Chrome → Storage → Clear Cache) and try again. On newer Android versions, go to Settings → Network & Internet → WiFi → tap the hotel network → verify it shows 'Connected, no internet' then tap 'Use anyway' if prompted — this bypasses Android's validation check so you can manually open the portal.

Why does only 5GHz WiFi show no internet while 2.4GHz works fine?

This typically indicates a band-specific routing or QoS misconfiguration in the router, or a driver issue with how the WiFi adapter handles the 5GHz radio. On the router admin page, check if the 5GHz band has its own VLAN or SSID isolation enabled. On the device side, update the WiFi adapter driver — Intel AX200/AX210 adapters on Dell and Lenovo laptops commonly show this after Windows updates. Also try disabling 802.11ax (Wi-Fi 6) mode on the router's 5GHz band to fall back to 802.11ac.

WiFi Connected But No Internet: Complete Troubleshooting Guide for All Devices & ISPs

Fix 'WiFi connected but no internet' on any device or ISP. Step-by-step DNS flush, IP renewal, gateway resets & driver fixes that actually work.

Last updated: February 27, 2026

Last verified: February 27, 2026

2,760 words

Key Takeaways

Root cause #1: IP address conflict or DHCP failure — your device gets a 169.254.x.x (APIPA) address or no gateway, meaning the router issued no valid lease.
Root cause #2: DNS resolution failure — your device can ping 8.8.8.8 but cannot resolve hostnames, pointing to a broken or unreachable DNS server.
Root cause #3: ISP or modem upstream failure — the router shows 'Internet' but the WAN link is down, a common issue with Cox Panoramic, Fios, Frontier, Charter, and Bell modems after power cycling.
Root cause #4: Captive portal not dismissed — hotels, hotspots, and guest networks require a browser login that the OS intercepts poorly on iOS, Android, Chromebook, and Fire tablets.
Root cause #5: Corrupted or outdated network adapter drivers — especially on Dell, HP, and Lenovo laptops running Windows 10/11 or Kali Linux.
Quick fix summary: Reboot modem → router → device in sequence; flush DNS with 'ipconfig /flushdns' (Windows) or 'sudo dscacheutil -flushcache' (macOS); renew IP with 'ipconfig /renew'; set DNS to 8.8.8.8; update or reinstall NIC drivers if hardware is suspect.

Fix Approaches Compared
Method	When to Use	Time	Risk
Modem + Router power cycle	ISP upstream down, Cox/Fios/Frontier/Bell/Charter outage, WAN link dropped	3-5 min	Low — no config lost
IP renewal (ipconfig /renew or dhclient)	APIPA 169.254.x.x address, DHCP lease expired, 'No valid IP' error	< 1 min	Low — temporary disconnect
DNS flush & change to 8.8.8.8	Sites won't load but ping to IP works, DNS_PROBE_FINISHED_NO_INTERNET, ERR_NAME_NOT_RESOLVED	1-2 min	Low
Forget & reconnect to WiFi network	Wrong password cached, corrupted network profile, hotel captive portal stuck	2 min	Low — must re-enter password
Disable IPv6 on adapter	IPv6 misconfiguration from ISP, Meraki or Google Nest dual-stack issues	1 min	Low — IPv4 still functional
Update / rollback NIC driver	Dell, HP, Lenovo WiFi adapter showing yellow exclamation, packet loss after OS update	5-15 min	Medium — may need restart
Network stack reset (netsh/winsock)	Persistent 'Unidentified Network', Windows TCP/IP stack corruption	2 min + reboot	Medium — resets all adapter settings
Factory reset router	All devices affected, config corruption, Meraki or Google Nest firmware bug	10-20 min	High — all settings erased
ISP-side provisioning call	Cox/Charter/Bell/Fios modem not provisioned after replacement or outage	20-60 min	None — ISP action

Understanding the 'WiFi Connected But No Internet' Error

When your operating system shows a WiFi connection (full signal bars) but browsers return errors like ERR_INTERNET_DISCONNECTED, DNS_PROBE_FINISHED_NO_INTERNET, Cannot connect to the Internet, or the dreaded yellow exclamation triangle on Windows, the symptom almost always means one of five underlying problems: a broken DHCP lease, a DNS failure, an upstream ISP link failure, an undismissed captive portal, or a corrupted network driver. The fix depends entirely on which layer is broken.

Step 1: Identify the Scope — Is It One Device or All Devices?

The single fastest diagnostic is to check another device on the same WiFi network.

All devices affected → The problem is in the modem, router, or ISP upstream. Skip to Step 3.
One device affected → The problem is in that device's network stack, DNS config, IP lease, or driver. Continue to Step 2.

Step 2: Check Your Actual IP Address

Open a terminal or command prompt and run the appropriate command for your OS (see the code block below). Look for these red flags:

169.254.x.x — This is an APIPA address. Your device never got a valid DHCP lease from the router. The router or its DHCP service is the problem.
0.0.0.0 — No IP at all. Network adapter failed to associate properly.
192.168.x.x or 10.x.x.x with a valid gateway — IP is fine; the problem is DNS or upstream ISP.

For Windows, open Command Prompt as Administrator and run:

ipconfig /all

For macOS/Linux:

ifconfig -a
ip addr show

For Android: Go to Settings → WiFi → tap the connected network → Advanced → IP address. For iOS: Settings → WiFi → tap ⓘ next to the network → check IP Address.

Step 3: Power Cycle in the Correct Order

Skipping this step or doing it out of order is the #1 reason ISP-related issues persist. This applies to Cox Panoramic, Fios ONT + router, Frontier DSL, Charter/Spectrum, Bell, Belong, and ACT broadband setups.

Unplug the modem (or ONT) from power. Wait 60 seconds — not 10. The ISP DHCP server must time out your old session.
Unplug the router (if separate from modem) from power.
Plug the modem back in first. Wait for all lights to stabilize (usually 30-60 seconds).
Plug the router back in. Wait 30 seconds.
Reconnect your device to WiFi.

For Cox Panoramic WiFi (all-in-one modem/router): unplug the unit, wait 60 seconds, plug back in. If the 'Online' light stays blinking orange after 3 minutes, Cox has a provisioning issue — call support or use the MyCox app to restart remotely.

Step 4: Flush DNS and Renew IP (Windows)

If the power cycle did not fix it on a single Windows machine (Dell, HP, Lenovo), open an elevated Command Prompt and run the sequence in the code block. Key commands:

ipconfig /release — Surrenders the current IP lease.
ipconfig /flushdns — Clears the local DNS resolver cache, which may contain stale or poisoned entries.
ipconfig /renew — Requests a fresh IP from DHCP.
netsh winsock reset — Resets the Winsock catalog to its clean state. Fixes 'Unidentified Network' and corrupted TCP/IP stack errors.
netsh int ip reset — Rewrites TCP/IP registry keys.

A reboot is required after the netsh resets.

Step 5: Change DNS Servers

If you can ping 8.8.8.8 but ping google.com fails with 'could not find host', your DNS is broken.

Windows: Control Panel → Network and Sharing Center → Change adapter settings → Right-click your WiFi adapter → Properties → IPv4 → Use the following DNS: 8.8.8.8 (primary), 1.1.1.1 (secondary).

macOS (Monterey and later): System Settings → Network → WiFi → Details → DNS → click '+' and add 8.8.8.8 and 1.1.1.1. Remove ISP-provided entries.

MacBook Air/Pro terminal method:

sudo networksetup -setdnsservers Wi-Fi 8.8.8.8 1.1.1.1
sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder

Android: Settings → WiFi → long-press network → Modify network → Advanced → IP settings: Static → DNS 1: 8.8.8.8. Note: on Android 9+ you can use Private DNS (Settings → Network → Advanced → Private DNS): enter dns.google.

Kali Linux:

echo 'nameserver 8.8.8.8' | sudo tee /etc/resolv.conf

Note: NetworkManager may overwrite resolv.conf. Edit /etc/NetworkManager/NetworkManager.conf and set dns=none under [main] to prevent this.

Step 6: Fix Captive Portal Issues (Hotel, Hotspot, Guest WiFi)

Hotels, car WiFi (Toyota, Hertz rental hotspots), mobile hotspots, Amazon Fire tablets on public networks, and guest WiFi on home routers all use captive portals. Symptoms: connected, no internet, browser shows nothing or an error.

Fixes:

Open a browser and navigate to http://neverssl.com or http://captive.apple.com — these plain HTTP pages trigger the portal redirect that HTTPS sites block.
On Android, tap the 'Sign in to network' notification if it appears.
On iOS, if the portal window auto-closes, go to Settings → WiFi → tap ⓘ → forget network → reconnect → wait for the portal popup.
On Amazon Fire tablets: open Silk browser manually and type any HTTP URL.
On Chromebook: click the network icon → click the portal notification → complete login in the window that opens.

Step 7: Update or Reinstall WiFi Drivers (Windows — Dell, HP, Lenovo, Moto E6 via ADB)

After a Windows Update, Intel or Qualcomm WiFi drivers sometimes regress. Symptoms: adapter shows in Device Manager with a yellow exclamation, or it appears normal but has no internet despite valid IP.

Press Win+X → Device Manager → Network Adapters.
Right-click your WiFi adapter → Update driver → Search automatically.
If that fails: right-click → Properties → Driver tab → Roll Back Driver.
Alternatively, download the latest driver directly:
- Dell: dell.com/support → enter Service Tag → Drivers → Network.
- HP: support.hp.com → enter model → Software & Drivers → Network.
- Lenovo: support.lenovo.com → Drivers & Software → Networking: Wireless LAN.

Step 8: Device-Specific Fixes

LG TV / LG G7 ThinQ: Go to Settings → Network → WiFi Connection → Advanced Settings → Set IP to Static, enter your router's IP range (e.g., 192.168.1.150), subnet 255.255.255.0, gateway = your router IP, DNS = 8.8.8.8. LG TVs are notorious for DHCP timing issues.

MacBook Air/Pro on macOS Monterey: Monterey introduced a bug where the WiFi service order gets corrupted. Fix: System Preferences → Network → click gear icon → Set Service Order → drag Wi-Fi to the top. Also delete the file /Library/Preferences/SystemConfiguration/com.apple.network.identification.plist and reboot.

Google Nest WiFi: Open the Google Home app → tap your Wifi device → Settings → Network & General → Test internet. If it fails, perform a factory reset by holding the reset button for 10 seconds on the Nest router (not the point). Re-add via Google Home app.

Meraki MR: Check Dashboard → Wireless → Access Points → click the AP → Event Log. Look for 'DHCP not received' or 'Client blocked by firewall policy'. Common fix: update the DHCP scope on the upstream switch or expand the IP pool in Network-wide → Configure → DHCP.

Android Box: Set a static IP via Settings → Network → WiFi → (long press SSID) → Manage network settings → Show advanced options → IP settings: Static. This bypasses DHCP race conditions common on cheap Android TV boxes.

5GHz Band Only: Some older devices (2.4GHz-only adapters) associate to the 5GHz SSID but cannot maintain a stable connection. In your router admin panel, temporarily enable band steering or split SSIDs (e.g., 'HomeNetwork' for 2.4GHz, 'HomeNetwork_5G' for 5GHz) and connect the device to the appropriate band.

Frequently Asked Questions

bash

# ============================================================
# WIFI CONNECTED BUT NO INTERNET — DIAGNOSTIC & FIX SCRIPT
# Covers: Windows (CMD/PowerShell), macOS, Linux, Android ADB
# ============================================================


# ------ WINDOWS (Run Command Prompt as Administrator) ------

# 1. Check current IP, gateway, and DNS
ipconfig /all

# 2. Ping gateway (replace with your router IP, usually 192.168.1.1 or 192.168.0.1)
ping 192.168.1.1 -n 4

# 3. Ping external IP to isolate DNS from routing
ping 8.8.8.8 -n 4

# 4. DNS lookup test
nslookup google.com
nslookup google.com 8.8.8.8

# 5. Release, flush, renew IP and DNS
ipconfig /release
ipconfig /flushdns
ipconfig /renew

# 6. Reset Winsock and TCP/IP stack (fixes corrupted network stack)
netsh winsock reset
netsh int ip reset
netsh int ipv6 reset

# 7. Disable IPv6 on WiFi adapter if causing issues
netsh interface ipv6 set interface "Wi-Fi" disabled

# 8. Set DNS manually to Google DNS on Wi-Fi adapter
netsh interface ip set dns name="Wi-Fi" static 8.8.8.8 primary
netsh interface ip add dns name="Wi-Fi" 1.1.1.1 index=2

# 9. Restart the network adapter
netsh interface set interface "Wi-Fi" disable
netsh interface set interface "Wi-Fi" enable

# 10. Full network reset (Windows 10/11 — run in PowerShell as Admin)
Reset-NetAdapterAdvancedProperty -Name "Wi-Fi" -DisplayName "*"

# Reboot after steps 6-10
# shutdown /r /t 5


# ------ macOS (Terminal) ------

# Check IP and routing table
ifconfig en0
netstat -rn | head -20

# Ping gateway and external IP
ping -c 4 192.168.1.1
ping -c 4 8.8.8.8

# DNS lookup
nslookup google.com
nslookup google.com 8.8.8.8

# Flush DNS cache (macOS Monterey / Ventura / Sonoma)
sudo dscacheutil -flushcache
sudo killall -HUP mDNSResponder

# Set DNS to Google via networksetup
sudo networksetup -setdnsservers Wi-Fi 8.8.8.8 1.1.1.1

# Renew DHCP lease
sudo ipconfig set en0 DHCP

# Toggle WiFi off and on
networksetup -setairportpower en0 off
sleep 3
networksetup -setairportpower en0 on

# Delete corrupted network preference files (fixes macOS Monterey WiFi bug)
sudo rm -f /Library/Preferences/SystemConfiguration/com.apple.airport.preferences.plist
sudo rm -f /Library/Preferences/SystemConfiguration/com.apple.network.identification.plist
sudo rm -f /Library/Preferences/SystemConfiguration/NetworkInterfaces.plist
# Reboot after deleting these files


# ------ Linux / Kali Linux (Terminal) ------

# Check interfaces
ip addr show
ip route show

# Ping gateway and external
ping -c 4 192.168.1.1
ping -c 4 8.8.8.8

# DNS test
nslookup google.com
dig @8.8.8.8 google.com

# Flush DNS (systemd-resolved)
sudo systemd-resolve --flush-caches
sudo systemd-resolve --statistics

# Override DNS temporarily
echo 'nameserver 8.8.8.8' | sudo tee /etc/resolv.conf
echo 'nameserver 1.1.1.1' >> /etc/resolv.conf

# Prevent NetworkManager from overwriting resolv.conf
# Edit /etc/NetworkManager/NetworkManager.conf
# Under [main] section add: dns=none
sudo sed -i '/\[main\]/a dns=none' /etc/NetworkManager/NetworkManager.conf
sudo systemctl restart NetworkManager

# Renew DHCP lease via dhclient
sudo dhclient -r wlan0
sudo dhclient wlan0

# Renew via NetworkManager
sudo nmcli device disconnect wlan0
sudo nmcli device connect wlan0

# Check for packet loss with traceroute
traceroute 8.8.8.8


# ------ Android (via ADB — USB Debugging enabled) ------

# List WiFi networks and status
adb shell dumpsys wifi | grep -E 'mNetworkInfo|ipAddress|gateway|DNS'

# Force WiFi reassociation
adb shell svc wifi disable
sleep 3
adb shell svc wifi enable

# Set custom DNS (Android 9+ Private DNS via adb)
adb shell settings put global private_dns_mode hostname
adb shell settings put global private_dns_specifier dns.google

# Clear WiFi config for a fresh start (wipes all saved networks)
adb shell settings delete global wifi_on
adb shell rm -rf /data/misc/wifi/*.conf
adb reboot

# ============================================================
# QUICK ONE-LINER: Test if DNS or routing is the problem
# If first succeeds and second fails, DNS is broken
# ------ Windows:
#   ping 8.8.8.8 && nslookup google.com
# ------ macOS/Linux:
#   ping -c 1 8.8.8.8 && nslookup google.com
# ============================================================

Error Medic Editorial

The Error Medic Editorial team is composed of senior DevOps engineers, SREs, and network administrators with 10+ years of experience troubleshooting enterprise and consumer networking issues across ISPs including Cox, Verizon Fios, Charter/Spectrum, Frontier, and Bell. Our guides are tested on real hardware and validated against official vendor documentation before publication.

Sources

Explore More wifi Guides

"Connected Without Internet" Error: Complete Fix Guide for Wi-Fi, Routers, Android & ISP Issues

Fix the "Connected Without Internet" error on Wi-Fi, Android, hotspots & routers. Step-by-step commands for Cox, CenturyLink, Frontier, T-Mobile & more.

"Connected Without Internet" Error: Complete Fix Guide for WiFi, Routers, Android & ISP Issues

Fix the 'connected without internet' error on WiFi, Android, hotspots & ISPs like Cox, CenturyLink & Fios. Step-by-step commands and solutions inside.

"Connected Without Internet" Error: What It Means and How to Fix It (All Devices & ISPs)

Fix the 'Connected Without Internet' WiFi error on Android, router, hotspot, Cox, CenturyLink, Fios & more. Step-by-step commands and solutions inside.