Android Says 'Connected, No Internet'? Fix It Fast

Quick answer: Toggle Private DNS to Off (or Automatic), forget and rejoin the network, and if that fails set a static IP with 8.8.8.8 as DNS — it's almost always Android's connectivity check failing, not your router.

Here's what's happening. Android pings a Google server (usually connectivitycheck.gstatic.com) every time it joins a Wi-Fi network. If that ping doesn't get a 204 response, Android slaps a 'no internet' label on the connection — even if your router is handing out IPs fine and every other device in the house is streaming Netflix. I had a client last month whose entire office of Pixel 6s started showing this after their ISP swapped in a new modem. Router was fine. Phones were fine. The modem's DNS was mangling the connectivity check response and Android had no idea what to do. So before you factory reset anything, work through these.

Fix 1: Toggle Private DNS off

This is my first stop 90% of the time. If you or some app enabled Private DNS with a hostname that isn't resolving, Android can't complete its check.

1. Open Settings.
2. Go to Network & internet > Private DNS (on Samsung it's under Connections > More connection settings).
3. Set it to Automatic or Off.
4. Toggle Wi-Fi off and back on.

If that fixes it, you were pointing at a DNS provider that had gone down or was blocking the check. Re-enable it later with a known-good hostname like dns.google or one.one.one.one.

Fix 2: Forget and rejoin the network

Corrupt saved credentials and stale DHCP leases cause this more often than people think. Especially if the router rebooted and handed out a new lease range while your phone kept the old one.

1. Settings > Network & internet > Internet.
2. Tap the gear next to your network name.
3. Hit Forget.
4. Reconnect and re-enter the password.

Fix 3: Set a static IP and DNS

If DHCP is the problem — and on older routers with tiny lease pools it absolutely is — this bypasses it entirely.

1. Long-press your Wi-Fi network and pick Modify network.
2. Expand Advanced options.
3. Change IP settings from DHCP to Static.
4. Set IP to something outside your router's DHCP range (e.g. 192.168.1.200 if your router hands out .100–.150).
5. Set DNS 1 to 8.8.8.8 and DNS 2 to 1.1.1.1.
6. Save and reconnect.

If you don't know your gateway, it's usually 192.168.1.1 or 192.168.0.1. Check another connected device if you're unsure.

Fix 4: Reset network settings

This nukes every saved Wi-Fi password and Bluetooth pairing on the phone, so only do it if the above didn't work. But it clears out the kind of corrupted config files that survive reboots.

1. Settings > System > Reset options.
2. Tap Reset Wi-Fi, mobile & Bluetooth.
3. Confirm and reboot.

If none of that works

• Check for a captive portal. Open Chrome and visit http://neverssl.com. If you get a login page, the network is hijacking traffic and you need to authenticate. Hotel, airport, and coffee shop networks do this constantly.
• Reboot the router anyway. Not because it's likely — but because it's free. Unplug for 30 seconds, plug back in.
• Test another device on the same band. If nothing else connects on 5GHz but everything works on 2.4GHz, your router's 5GHz radio is dying.
• Disable MAC randomization. Some routers with strict MAC filtering block Android's randomized MAC. In Wi-Fi settings, tap your network > Privacy > Use device MAC.
• Check the date and time. Seriously. If your phone's clock is off by more than a few minutes, HTTPS checks fail and Android reports no internet. Set it to automatic.

Prevention tip

Leave Private DNS on Automatic unless you've got a reason to change it, and don't let random 'Wi-Fi booster' apps mess with your network stack. Also, when your ISP swaps your modem, reboot every device in the house — not just the router. Half the 'no internet' reports I get come from a stale DHCP lease that only a device reboot clears.

Quick reference