How to Fix 'Connected Without Internet' on Samsung: Complete Troubleshooting Guide
Fix 'Connected Without Internet' on Samsung phones (A12 and others). Step-by-step guide covering DNS reset, network settings, and ADB commands.
- Root cause 1: Samsung's network captive portal detection server (connectivitycheck.gstatic.com or samsung's own endpoint) fails to respond, causing Android to flag the connection as having no internet even when data flows normally.
- Root cause 2: Corrupted DHCP lease, stale DNS cache, or misconfigured static IP settings cause the Samsung device to obtain an IP but fail to route traffic correctly, triggering the 'Connected, no internet access' warning.
- Root cause 3: Wi-Fi router settings such as AP isolation, MAC filtering, or firewall rules block the device's connectivity check probe requests, leading to a false 'no internet' status.
- Quick fix summary: Forget and reconnect to the network, flush DNS via ADB or Settings, change DNS to 8.8.8.8/8.8.4.4, toggle Airplane Mode, or reset network settings under General Management — most issues resolve in under five minutes.
| Method | When to Use | Time | Risk |
|---|---|---|---|
| Toggle Airplane Mode | Quick first-pass fix; refreshes radio stack | 30 seconds | None |
| Forget & Reconnect to Wi-Fi | After password change or DHCP conflict | 2 minutes | None |
| Change DNS to Google/Cloudflare | ISP DNS unresponsive or captive-portal mismatch | 3 minutes | None |
| Set Static IP in Wi-Fi Advanced | DHCP server assigning conflicting leases | 5 minutes | Low — revert if issues persist |
| Clear Wi-Fi & Network Stack via Settings | Persistent issue across multiple networks | 5 minutes | Low — loses saved Wi-Fi passwords |
| ADB flush DNS & connectivity check reset | Developer/advanced users; all else fails | 10 minutes | Low — requires USB debugging enabled |
| Reset Network Settings (General Management) | All other fixes failed; device-wide network corruption | 5 minutes | Medium — removes all saved networks and Bluetooth pairings |
| Factory Reset | Severe OS corruption not resolved by other steps | 30-60 minutes | High — wipes all data |
Understanding the 'Connected Without Internet' Error on Samsung
When your Samsung phone (including popular models like the Galaxy A12, A32, A52, S21, or S23) shows 'Connected, no internet access' or 'Connected without internet' beneath a Wi-Fi network name, it means Android's connectivity check subsystem has concluded that the device cannot reach the open internet — even though a valid IP address was obtained from the router.
Android periodically sends an HTTP probe to a known endpoint (historically http://connectivitycheck.gstatic.com/generate_204) and expects an HTTP 204 response. Samsung One UI modifies this to also check Samsung's own servers. If either probe fails or returns an unexpected response, the OS displays the warning and may automatically switch to mobile data instead.
Exact warning messages you may see:
Connected, no internet accessConnected without internetWi-Fi has no internet access. Stay connected?No internet connection(in the Wi-Fi details panel)
Step 1: Diagnose the Root Cause
Before applying fixes, determine whether the issue is with the device, the router, or the ISP.
1.1 — Check if other devices are affected Connect a second device (laptop, another phone) to the same Wi-Fi network. If that device also shows no internet, the problem is the router or ISP, not your Samsung. Skip to Step 2.4.
1.2 — Check if the issue follows the phone Connect your Samsung to a different Wi-Fi network (mobile hotspot from another phone works perfectly). If the error disappears, the original router is the problem. If it persists, the issue is on the Samsung device itself.
1.3 — Review IP address assignment Go to Settings → Connections → Wi-Fi → tap the gear icon next to the connected network → View More. Confirm:
- IP Address is a valid private range (192.168.x.x, 10.x.x.x, or 172.16-31.x.x)
- Gateway matches your router's address
- DNS servers are populated (not 0.0.0.0)
If IP is 0.0.0.0 or the gateway is empty, you have a DHCP failure — proceed to Step 2.3.
1.4 — Enable Developer Options and check connectivity logs Go to Settings → About Phone → Software Information → tap Build Number 7 times to enable Developer Options. Then navigate to Settings → Developer Options → Mobile data always active and ensure it is OFF (this setting can interfere with Wi-Fi routing).
Step 2: Apply Fixes in Order
Fix 2.1 — Toggle Airplane Mode (30 seconds)
Swipe down the notification shade and tap the Airplane Mode tile to enable it. Wait 15 seconds, then disable it. This forces the radio stack to re-initialize and renegotiate the connection. Recheck the Wi-Fi status.
Fix 2.2 — Forget and Reconnect to Wi-Fi Network (2 minutes)
- Go to Settings → Connections → Wi-Fi.
- Long-press the problematic network (or tap the gear icon).
- Tap Forget.
- Wait 10 seconds, then tap the network and re-enter the password.
This clears the cached DHCP lease and forces the router to issue a fresh IP assignment.
Fix 2.3 — Change DNS Servers (3 minutes)
ISP-provided DNS servers are the most common culprit on Samsung devices because Android's captive portal check relies on successful DNS resolution of Google or Samsung domains.
- Settings → Connections → Wi-Fi → tap the gear icon next to your network.
- Tap IP Settings and switch from DHCP to Static.
- Keep the existing IP and Gateway values, but clear the DNS fields.
- Set DNS 1 to
8.8.8.8(Google) and DNS 2 to8.8.4.4. - Alternatively use Cloudflare:
1.1.1.1and1.0.0.1. - Tap Save and wait 10 seconds.
Samsung One UI 4/5 Private DNS option (recommended for newer models):
Go to Settings → Connections → More Connection Settings → Private DNS → Private DNS provider hostname and enter dns.google or one.one.one.one. This applies across all networks.
Fix 2.4 — Assign a Static IP to Avoid DHCP Conflicts (5 minutes)
If your router's DHCP pool is exhausted or a lease conflict exists:
- Find your current IP in Wi-Fi Advanced settings (e.g.,
192.168.1.105). - Change the last octet to something outside the DHCP range — typically
192.168.1.200or higher. - Set subnet mask to
255.255.255.0, gateway to192.168.1.1(or your actual router IP). - Save and reconnect.
Fix 2.5 — Reset Network Settings (5 minutes)
This clears all Wi-Fi passwords, Bluetooth pairings, and mobile data settings.
Samsung Galaxy A12 / One UI path: Settings → General Management → Reset → Reset Network Settings → Reset Settings → confirm
After the reset, reconnect to your Wi-Fi and test.
Fix 2.6 — Router-Side Fixes
If multiple devices experience the same issue on this router:
- Restart the router: Unplug for 30 seconds and plug back in.
- Check AP Isolation: Log into your router admin panel (typically
192.168.1.1or192.168.0.1). Look under Wireless settings for AP Isolation or Client Isolation — disable it. - Check MAC Filtering: Ensure your Samsung's MAC address is not blocked. Note: Samsung devices use randomized MAC addresses by default. In Wi-Fi settings, tap the gear icon → MAC address type → change to Phone MAC to use a consistent hardware address.
- Update router firmware: Outdated firmware can cause DHCP and DNS resolution failures.
Fix 2.7 — ADB-Based Network Stack Reset (Advanced)
For persistent issues on Samsung developer units or rooted devices, use Android Debug Bridge commands (see the code block section below for full script).
Key commands:
adb shell settings put global captive_portal_detection_enabled 0
adb shell settings put global captive_portal_server connectivitycheck.gstatic.com
adb shell svc wifi disable && adb shell svc wifi enable
Note: Disabling captive portal detection removes the warning but does not fix underlying connectivity — use only for diagnostic purposes.
Fix 2.8 — Clear Cache Partition (Samsung-specific)
On Samsung phones, a corrupted system cache can cause persistent network misfires.
- Power off the device.
- Hold Volume Up + Power until the Samsung logo appears, then release Power but keep holding Volume Up.
- In Recovery mode, use Volume keys to navigate to Wipe cache partition and confirm with Power.
- Reboot and test.
Step 3: Verify the Fix
After applying any fix:
- Open a browser and navigate to
http://connectivitycheck.gstatic.com/generate_204— you should receive an empty 204 response. - Run a speed test at
fast.comorspeedtest.net. - Check the Wi-Fi network label in the notification bar — it should no longer show the 'no internet' warning.
If the warning persists despite working internet (pages load fine), the captive portal check itself is blocked. This is cosmetic and can be resolved via the ADB commands in Fix 2.7 or by changing Private DNS settings.
Frequently Asked Questions
#!/usr/bin/env bash
# Samsung 'Connected Without Internet' Diagnostic & Fix Script
# Prerequisites: ADB installed, USB debugging enabled on Samsung device
# Run: chmod +x samsung_wifi_fix.sh && ./samsung_wifi_fix.sh
set -euo pipefail
echo "=== Samsung Wi-Fi 'Connected Without Internet' Diagnostic ==="
echo ""
# 1. Verify ADB connection
echo "[1/8] Checking ADB device connection..."
adb devices | grep -v 'List of devices' | grep -v '^$'
if ! adb get-state &>/dev/null; then
echo "ERROR: No device found. Ensure USB debugging is enabled."
exit 1
fi
echo "Device connected."
echo ""
# 2. Check current Wi-Fi state
echo "[2/8] Current Wi-Fi connection info:"
adb shell dumpsys wifi | grep -E 'mWifiInfo|ssid|ipAddress|linkSpeed|SSID|BSSID|DNS'
echo ""
# 3. Check connectivity service state
echo "[3/8] Connectivity Manager status:"
adb shell dumpsys connectivity | grep -E 'NetworkInfo|connected|internet|CONNECTED|DISCONNECTED|ValidationResult' | head -30
echo ""
# 4. Ping gateway and external hosts from device
echo "[4/8] Pinging gateway and external hosts..."
GATEWAY=$(adb shell ip route | grep default | awk '{print $3}')
echo "Gateway: $GATEWAY"
adb shell ping -c 3 -W 2 "$GATEWAY" 2>/dev/null || echo "WARNING: Cannot reach gateway"
adb shell ping -c 3 -W 2 8.8.8.8 2>/dev/null || echo "WARNING: Cannot reach 8.8.8.8"
adb shell ping -c 3 -W 2 connectivitycheck.gstatic.com 2>/dev/null || echo "WARNING: DNS resolution failed for captive portal host"
echo ""
# 5. Check and update captive portal settings
echo "[5/8] Checking captive portal detection settings..."
CURRENT_DETECTION=$(adb shell settings get global captive_portal_detection_enabled 2>/dev/null || echo 'unknown')
CURRENT_SERVER=$(adb shell settings get global captive_portal_server 2>/dev/null || echo 'unknown')
echo "Current captive_portal_detection_enabled: $CURRENT_DETECTION"
echo "Current captive_portal_server: $CURRENT_SERVER"
echo ""
# Fix: Ensure captive portal server is set to reliable endpoint
echo "Setting captive portal server to connectivitycheck.gstatic.com..."
adb shell settings put global captive_portal_detection_enabled 1
adb shell settings put global captive_portal_server connectivitycheck.gstatic.com
adb shell settings put global captive_portal_use_https 1
echo "Captive portal settings updated."
echo ""
# 6. Flush DNS cache
echo "[6/8] Flushing DNS cache..."
adb shell ndc resolver flushdefaultif 2>/dev/null || \
adb shell cmd connectivity flush-dns-cache 2>/dev/null || \
adb shell killall -HUP netd 2>/dev/null || \
echo "Note: DNS flush requires root or may not be supported on this Android version."
echo ""
# 7. Force Wi-Fi reconnect
echo "[7/8] Toggling Wi-Fi to force reconnect..."
adb shell svc wifi disable
sleep 3
adb shell svc wifi enable
sleep 5
echo "Wi-Fi re-enabled."
echo ""
# 8. Verify fix
echo "[8/8] Verifying connectivity after fix..."
adb shell curl -s -o /dev/null -w '%{http_code}' http://connectivitycheck.gstatic.com/generate_204 2>/dev/null | \
xargs -I{} bash -c 'if [ "{}" = "204" ]; then echo "SUCCESS: Captive portal check returns 204 — internet confirmed."; else echo "FAIL: Got HTTP {} instead of 204. Further investigation needed."; fi'
echo ""
# Optional: Disable Mobile Data Always Active (can interfere with Wi-Fi routing)
echo "Disabling mobile_data_always_active to prevent Wi-Fi routing conflicts..."
adb shell settings put global mobile_data_always_active 0
echo ""
echo "=== Diagnostic complete. Check device Wi-Fi status. ==="
echo "If issue persists, try: Settings → General Management → Reset → Reset Network Settings"Error Medic Editorial
The Error Medic Editorial team is composed of senior DevOps engineers, SREs, and mobile platform specialists with 10+ years of experience diagnosing network, OS, and application-layer issues across Android, iOS, Linux, and cloud infrastructure. Our guides are tested on real hardware and reviewed against official vendor documentation before publication.
Sources
- https://source.android.com/docs/core/connect/network-access
- https://developer.android.com/training/basics/network-ops/connecting
- https://stackoverflow.com/questions/16862256/android-wifi-connected-but-no-internet-access
- https://www.samsung.com/global/galaxy/apps/samsung-help/mobile/network-connectivity-issues/
- https://issuetracker.google.com/issues/180526692