IPFYI

Connected to Wi-Fi But No Internet Access

Beginner Connectivity

A device shows a successful Wi-Fi connection with full signal strength but cannot access the internet or load any websites. This is a common scenario that presents differently from a complete network failure — the device has joined the wireless network successfully but something beyond the access point is preventing internet access.

Symptoms

  • ⚠ Device shows Wi-Fi connected with full bars, but browser displays 'No Internet' or 'DNS_PROBE_FINISHED_NO_INTERNET'
  • ⚠ Device receives a 169.254.x.x (APIPA) IP address instead of a valid 192.168.x.x address
  • ⚠ Ping to the router gateway (e.g., 192.168.1.1) succeeds, but ping to 8.8.8.8 fails
  • ⚠ Other devices on the same Wi-Fi network also cannot access the internet
  • ⚠ Network icon shows a yellow warning triangle or globe with an X (Windows) or no internet indicator

Possible Root Causes

  • • Router's WAN connection to the ISP has failed (DHCP lease expired, PPPoE dropped)
  • • DHCP server on the router is not functioning, causing devices to fall back to APIPA addresses
  • • DNS server assigned via DHCP is unresponsive or returning incorrect results
  • • Wi-Fi association succeeded but the device is on a guest VLAN with internet access blocked by a firewall rule
  • • Captive portal requiring authentication before internet access is granted (common in hotels, cafes)

Diagnosis Steps

Step 1: Check your IP address

# Linux / macOS
ip addr show wlan0
# or
ifconfig en0

# Windows
ipconfig
  • 192.168.x.x, 10.x.x.x, or 172.16-31.x.x = Valid DHCP assignment
  • 169.254.x.x = APIPA — DHCP server is unreachable, device assigned itself a link-local address

Step 2: Ping the gateway

# Replace 192.168.1.1 with your actual gateway IP
ping -c 4 192.168.1.1   # Linux / macOS
ping 192.168.1.1        # Windows
  • Gateway responds = Your device and router are communicating. Problem is between router and ISP.
  • Gateway doesn't respond = Wi-Fi association issue or DHCP failure.

Step 3: Attempt to reach a public IP (bypassing DNS)

# Test TCP connectivity to Google DNS on port 53
# Linux / macOS
ping -c 4 8.8.8.8

# If ping is blocked, try with curl
curl -m 5 http://8.8.8.8
  • Reaches 8.8.8.8 but not websites = DNS failure
  • Cannot reach 8.8.8.8 = Routing issue between router and internet

Step 4: Test DNS resolution manually

# Linux / macOS
nslookup google.com
nslookup google.com 8.8.8.8   # force use of Google DNS

# Windows
nslookup google.com
nslookup google.com 8.8.8.8

If nslookup google.com fails but nslookup google.com 8.8.8.8 succeeds, your DHCP-assigned DNS server is faulty.

Step 5: Verify the router has internet access

Log in to http://192.168.1.1 and check the WAN status. If the router itself shows no internet (WAN IP = 0.0.0.0), the issue is between the router and ISP — affecting all devices.

Solution

Fix 1: Restart the router and modem

The quickest fix for most cases:

  1. Power off the modem (ISP device) and router
  2. Wait 30 seconds
  3. Power on the modem first — wait for all lights to stabilize (1-2 minutes)
  4. Power on the router — wait 60 seconds
  5. Reconnect your device to Wi-Fi

Fix 2: Force DHCP renewal on your device

# Linux
sudo dhclient -r wlan0
sudo dhclient wlan0

# macOS (Network Preferences > Advanced > TCP/IP > Renew DHCP Lease)
# Or via terminal:
sudo ipconfig set en0 DHCP

# Windows
ipconfig /release
ipconfig /renew

Fix 3: Set a manual DNS server

If you have a gateway IP but no DNS:

# macOS — add manual DNS (System Settings > Network > Wi-Fi > Details > DNS)
# Add: 1.1.1.1 and 8.8.8.8

# Linux (NetworkManager)
nmcli con mod "Wi-Fi Connection" ipv4.dns "1.1.1.1,8.8.8.8"
nmcli con up "Wi-Fi Connection"

# Windows
netsh interface ip set dns "Wi-Fi" static 1.1.1.1
netsh interface ip add dns "Wi-Fi" 8.8.8.8 index=2

Fix 4: Forget and reconnect to the Wi-Fi network

Sometimes the association state becomes corrupted. Forget the network and reconnect:

  1. Go to Wi-Fi settings
  2. Tap/click on the network name > Forget / Remove
  3. Scan and reconnect, entering the password again

Fix 5: Check for a captive portal

Open a browser and navigate to http://neverssl.com or http://captive.apple.com. If a login page appears, complete the captive portal authentication.

Prevention

  • Assign DHCP reservations for important devices so they always receive the same IP and DNS configuration
  • Configure a secondary DNS server in DHCP settings (e.g., 8.8.8.8 as fallback to your primary DNS)
  • Set up a simple network monitoring check that pings 1.1.1.1 from your router and alerts you when connectivity drops
  • Restart your router on a scheduled monthly basis during off-hours to prevent DHCP table overflow and firmware memory leaks
  • For critical work setups, keep a cellular hotspot available as a backup connection

Related Protocols

DHCP DNS ICMP IPV4 TCP

Related Terms

dhcp dns gateway ip-address nat

More in Connectivity

Ethernet Connected But No Link Detected Beginner IP Address Conflict Resolution Beginner IPv6-Only Network Connectivity Failures Advanced Intermittent Connectivity Drops Intermediate No Internet After Router Reboot Beginner Path MTU Discovery Black Hole Advanced