Error Medic

How to Fix "Connected Without Internet" on Samsung Phone (Wi-Fi Shows Connected But No Internet Access)

Fix Samsung 'Connected Without Internet' Wi-Fi error fast. Step-by-step guide covering Samsung A12 and all Samsung phones. Clear causes and proven fixes.

Last updated:
Last verified:
2,446 words
Key Takeaways
  • Root Cause 1: Samsung's network validation check (Captive Portal Detection) is failing — the phone pings Google's connectivity servers but gets no valid HTTP 204 response, flagging the network as having no internet even when it does.
  • Root Cause 2: Incorrect IP configuration (wrong DNS, DHCP failure, or IP conflict on the network) means your Samsung device received an IP lease but cannot route traffic to the internet.
  • Root Cause 3: Router-side issues such as ISP outage, MAC address filtering, or firmware bugs that break NAT/firewall forwarding cause the connection to appear valid at Layer 2 but fail at Layer 3.
  • Quick Fix Summary: Start by forgetting and reconnecting to the Wi-Fi network, then try toggling Airplane Mode, flushing DNS (set manual DNS to 8.8.8.8 / 8.8.4.4), resetting network settings, and finally clearing the Wi-Fi subsystem cache via Safe Mode or ADB — most users resolve the error within one of these five steps.
Fix Approaches Compared
MethodWhen to UseTimeRisk
Toggle Airplane ModeFirst quick attempt; resets radio stack without data loss30 secNone
Forget & Reconnect to Wi-FiWrong password saved or corrupted network profile2 minNone — must re-enter password
Set Static IP / Manual DNS (8.8.8.8)DHCP gave bad IP or ISP DNS is down3 minLow — revert to DHCP if not working
Clear Network Settings (Settings > General Management)Multiple networks misbehaving or after OS update2 minMedium — forgets ALL saved Wi-Fi, Bluetooth, VPN
Router Reboot & Firmware UpdateOther devices also show 'no internet'10 minLow — brief outage for all connected devices
ADB Shell Network ResetPersistent captive portal detection failure, developer tools available10 minMedium — requires USB debugging enabled
Factory Reset (last resort)All else fails, possibly corrupted system partition45 minHigh — all data lost unless backed up

Understanding the "Connected Without Internet" Error on Samsung

When your Samsung phone displays the message "Connected, no internet" or "Connected without internet" beneath a Wi-Fi network name, it means Android's connectivity service successfully associated with the access point at the Wi-Fi (Layer 2) level — the handshake completed, an IP address was obtained — but a higher-level probe to verify real internet reachability failed.

Android uses a mechanism called Captive Portal Detection (CPD). After connecting to any Wi-Fi network, the operating system silently sends an HTTP GET request to a Google-hosted URL:

http://connectivitycheck.gstatic.com/generate_204

If the server responds with HTTP 204 No Content, Android marks the network as "internet available." If it receives anything else — a redirect (common on hotel portals), a timeout, or an error — it shows "Connected without internet." On Samsung One UI devices, this exact notification appears in the status bar dropdown and under Settings > Connections > Wi-Fi.


Step 1: Confirm the Scope of the Problem

Before changing anything, determine whether the issue is with your Samsung device only or all devices on the network.

Check on another device: Connect a laptop, tablet, or a second phone to the same Wi-Fi. If those devices also have no internet, the problem is with your router or ISP — not your Samsung phone.

Check mobile data: On your Samsung, temporarily disable Wi-Fi and use mobile data. If apps and browsers work fine, the phone's hardware and software are functioning correctly.

Observe the exact error string: On Samsung One UI (Android 11–14), you will see:

  • In the Wi-Fi list: "Connected without internet"
  • In the notification shade: "Wi-Fi has no internet access"
  • On Samsung A12 (One UI Core 3.1): "Connected, no internet access" under the network SSID

Step 2: Toggle Airplane Mode (Fastest Fix)

  1. Pull down the notification shade.
  2. Tap Airplane Mode to enable it — wait 10 seconds.
  3. Tap Airplane Mode again to disable it.
  4. Your phone will reconnect to Wi-Fi automatically.

This forces the radio stack to reinitialize, clearing transient state issues in the Wi-Fi firmware.


Step 3: Forget and Reconnect to the Wi-Fi Network

  1. Go to Settings > Connections > Wi-Fi.
  2. Tap the gear icon next to your network name.
  3. Tap Forget.
  4. Tap the network name in the list and re-enter the password.

This clears any corrupted network profile (saved DHCP lease, wrong saved IP configuration) and forces a fresh DHCP handshake.


Step 4: Set Manual DNS Servers

A very common cause on Samsung A12 and similar budget Samsung phones is that the carrier or router's DNS servers are unreachable or returning bad responses, causing the captive portal probe to fail.

  1. Go to Settings > Connections > Wi-Fi.
  2. Tap the gear icon next to your connected network.
  3. Tap IP Settings and change from DHCP to Static.
  4. Keep the IP address and gateway as-is (note them down first).
  5. Change DNS 1 to 8.8.8.8 and DNS 2 to 8.8.4.4.
  6. Tap Save and reconnect.

Alternatively, use Cloudflare's DNS: 1.1.1.1 / 1.0.0.1.


Step 5: Reset All Network Settings

If the issue persists across multiple networks, a deeper reset is needed.

  1. Go to Settings > General Management > Reset.
  2. Tap Reset Network Settings.
  3. Confirm — this will erase all saved Wi-Fi networks, Bluetooth pairings, and VPN configurations.
  4. Reconnect to your Wi-Fi network.

Note for Samsung A12 users: On One UI Core, navigate to Settings > General Management > Reset > Reset Network Settings. The path is identical but menus may render slightly differently on the 6.5" display.


Step 6: Clear Wi-Fi Direct and Captive Portal Cache via ADB

For advanced users with USB Debugging enabled (or IT administrators managing Samsung fleets), you can use ADB to reset the connectivity check settings and clear network caches directly.

See the Diagnostic Commands section below for exact ADB commands.


Step 7: Check Router Configuration

If you control the router:

  • Reboot the router (power cycle for 30 seconds).
  • Log into the router admin panel (typically 192.168.1.1 or 192.168.0.1).
  • Check if MAC address filtering is enabled — your Samsung's MAC may not be on the allowlist. Note: Samsung phones use randomized MAC addresses by default since Android 10. Disable MAC randomization: Settings > Connections > Wi-Fi > gear icon > MAC address type > Use phone MAC.
  • Check that the router's DHCP pool is not exhausted (too many connected devices).
  • Verify the router has a valid WAN IP from the ISP (check the router's status page).
  • Update the router firmware if an update is available.

Step 8: Check for Samsung-Specific One UI Captive Portal Setting

Some Samsung devices on custom ROMs or after carrier updates have the captive portal detection URL overridden or disabled. You can check and reset it via ADB:

adb shell settings get global captive_portal_server
adb shell settings get global captive_portal_https_url

If these return unexpected values or null, reset them to Google defaults (commands in the code section below).


Step 9: Safe Mode Test

Boot into Safe Mode to check if a third-party app (VPN client, battery saver, firewall app) is intercepting the captive portal check:

  1. Press and hold the Power button.
  2. Long-press the Power Off option until Safe Mode appears.
  3. Tap Safe Mode to reboot.
  4. Connect to Wi-Fi in Safe Mode — if it shows "Connected" with internet, a third-party app is the culprit.
  5. Reboot normally and uninstall recently installed VPN, firewall, or network management apps.

Step 10: Factory Reset (Last Resort)

If nothing else works and the error appears on every network including mobile hotspots:

  1. Back up all data via Samsung Smart Switch or Settings > Accounts and Backup.
  2. Go to Settings > General Management > Reset > Factory Data Reset.
  3. Confirm and allow the reset to complete (10–20 minutes).
  4. During initial setup, connect to Wi-Fi — if it now works, a software corruption was the root cause.

Frequently Asked Questions

bash
# ============================================================
# Samsung "Connected Without Internet" — ADB Diagnostic & Fix
# Prerequisites: ADB installed, USB Debugging enabled on phone
# Enable USB Debugging: Settings > Developer Options > USB Debugging
# (Enable Developer Options: Settings > About Phone > tap Build Number 7x)
# ============================================================

# --- Step 1: Verify ADB can see your device ---
adb devices
# Expected output: <serial_number>   device
# If 'unauthorized': unlock phone and tap 'Allow' on the RSA prompt

# --- Step 2: Check current captive portal settings ---
adb shell settings get global captive_portal_server
adb shell settings get global captive_portal_https_url
adb shell settings get global captive_portal_http_url
adb shell settings get global captive_portal_mode
# captive_portal_mode: 0=disabled, 1=enabled (default)
# If captive_portal_https_url returns 'null', it's using the system default

# --- Step 3: Reset captive portal URLs to Google defaults ---
adb shell settings put global captive_portal_server connectivitycheck.gstatic.com
adb shell settings put global captive_portal_https_url https://www.google.com/generate_204
adb shell settings put global captive_portal_http_url http://connectivitycheck.gstatic.com/generate_204
adb shell settings put global captive_portal_fallback_url http://www.google.com/gen_204
adb shell settings put global captive_portal_mode 1

# --- Step 4: If Google URLs are blocked on your network, use alternative ---
# (Use this if corporate firewall blocks *.gstatic.com)
adb shell settings put global captive_portal_https_url https://www.google.com/generate_204
# OR point to Cloudflare (no server setting needed with full URL):
adb shell settings put global captive_portal_https_url https://captive.apple.com/hotspot-detect.html

# --- Step 5: Force connectivity re-evaluation ---
# Toggle Wi-Fi off and on via ADB
adb shell svc wifi disable
sleep 3
adb shell svc wifi enable

# --- Step 6: Check assigned IP, gateway, and DNS ---
adb shell ip addr show wlan0
adb shell ip route
adb shell getprop net.dns1
adb shell getprop net.dns2

# Expected: net.dns1 should return a valid IP (e.g., 192.168.1.1 or 8.8.8.8)
# If blank or 0.0.0.0, DHCP failed — use static IP on the phone

# --- Step 7: Test DNS resolution from the phone ---
adb shell nslookup connectivitycheck.gstatic.com
adb shell nslookup google.com
# If these fail: DNS is broken. Set manual DNS 8.8.8.8 in Wi-Fi settings.

# --- Step 8: Ping the gateway to test Layer 3 connectivity ---
adb shell ping -c 4 $(adb shell ip route | grep default | awk '{print $3}')
# If ping to gateway fails: IP/routing issue (DHCP conflict or static IP misconfigured)
# If ping to gateway succeeds but DNS fails: ISP DNS is down, use 8.8.8.8

# --- Step 9: Test connectivity to Google's 204 endpoint directly ---
adb shell curl -v http://connectivitycheck.gstatic.com/generate_204
# Expected: HTTP/1.1 204 No Content
# If you see HTTP 302 redirect: you're on a captive portal — sign in via browser
# If connection refused/timeout: firewall is blocking outbound HTTP

# --- Step 10: Clear network subsystem cache (NetworkStack) ---
adb shell cmd network_stack reload
# Note: Available on Android 10+ / One UI 2.0+

# --- Step 11: Check for MAC randomization setting ---
adb shell cmd wifi get-configured-networks
# Look for 'macRandomizationSetting' in output
# 1 = RANDOMIZATION_PERSISTENT (default, may cause issues with MAC filtering routers)
# 3 = RANDOMIZATION_NONE (uses device MAC)
# To disable randomization for a specific network, use Settings > Wi-Fi > gear > MAC address type

# --- Step 12: Full network settings reset via ADB (alternative to GUI) ---
adb shell sm reset-network-settings
# Note: This may not be available on all One UI versions
# Prefer: Settings > General Management > Reset > Reset Network Settings

echo "Diagnostic complete. Check adb logcat for connectivity errors:"
adb logcat -d | grep -i "captive\|ConnectivityService\|WifiConnected\|NetworkMonitor" | tail -50
E

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 Android, Samsung One UI, and network infrastructure issues. Our guides are tested on real devices — including the Samsung Galaxy A12, A52, S21, and S23 series — running Android 11 through Android 14. We reference official Android Open Source Project documentation, Samsung Developer resources, and reproduce every fix in a controlled lab environment before publishing.

Sources

Related Articles in Samsung Connected Without Internet

Explore More wifi Guides