No Internet Access But Connected: Fix 'Connected, No Internet' on Wi-Fi & Ethernet

Understanding 'No Internet Access But Connected'

This maddening state — where your device shows a solid Wi-Fi signal or a green Ethernet link light yet browsers refuse to load pages — is one of the most common networking complaints across Windows, macOS, and Linux. The operating system considers itself connected to the local network (Layer 2 success) but cannot reach the internet (Layer 3 or Layer 7 failure). Windows labels this with a yellow exclamation triangle and the text 'No Internet Access' or 'No network access'. macOS displays 'Connected' in System Settings while Safari shows 'Safari Can't Connect to the Server'.

Understanding the OSI layers involved helps you diagnose faster:

• Layer 1 (Physical): Cable plugged in, Wi-Fi radio on.
• Layer 2 (Data Link): Device associated with router/AP, gets a MAC-to-IP binding.
• Layer 3 (Network): Device receives a valid IP from DHCP — this is where most failures hide.
• Layer 7 (Application): DNS resolves names to IPs, browser opens TCP connection.

A failure at any layer above Layer 2 produces the 'connected but no internet' symptom.

Step 1: Identify Which Layer Is Failing

Check your IP address first. An address starting with 169.254.x.x (Windows APIPA) or 0.0.0.0 (Linux/macOS) means DHCP failed — your device never got a valid lease.

Windows:

ipconfig /all

Look for 'IPv4 Address'. If it shows 169.254.x.x, skip to the DHCP fix section.

macOS / Linux:

ifconfig
# or
ip addr show

Ping the gateway. If your IP is valid (e.g., 192.168.1.x), find your default gateway and ping it:

# Windows
ping 192.168.1.1

# macOS/Linux
ping -c 4 192.168.1.1

If the gateway responds but internet is down, your router has a problem or DNS is broken. If the gateway does NOT respond, the issue is between your device and the router.

Ping a public IP (bypass DNS entirely):

ping 8.8.8.8

If ping 8.8.8.8 succeeds but ping google.com fails, you have a pure DNS failure. This is the most common scenario.

Step 2: Fix DHCP / IP Address Problems

Windows — Release and Renew: Open Command Prompt as Administrator and run:

ipconfig /release
ipconfig /renew

This forces Windows to drop its current (possibly stale or conflicted) lease and request a fresh one from your router's DHCP server. If the router is healthy, you will receive a valid address within seconds.

If renewal fails with error Unable to contact your DHCP server, power cycle your router (unplug 30 seconds, replug) and retry.

Linux (Ubuntu/Debian) — Renew DHCP Lease:

sudo dhclient -r eth0    # release
sudo dhclient eth0       # renew

Replace eth0 with your actual interface name from ip addr show.

macOS — Renew DHCP Lease: Go to System Settings → Network → select your adapter → Details → TCP/IP tab → click Renew DHCP Lease. Alternatively, use Terminal:

sudo ipconfig set en0 DHCP

Step 3: Fix DNS Failures

Flush DNS Cache:

Windows:

ipconfig /flushdns

Expected output: Successfully flushed the DNS Resolver Cache.

macOS (Ventura/Sonoma):

sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder

Linux (systemd-resolved):

sudo systemd-resolve --flush-caches

Change DNS Servers to Public Resolvers: If flushing the cache does not help, your ISP's DNS servers may be down or returning bad data.

Windows (via netsh):

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

Replace "Wi-Fi" with "Ethernet" for wired connections. Verify adapter name with netsh interface show interface.

Linux (/etc/resolv.conf):

echo "nameserver 8.8.8.8" | sudo tee /etc/resolv.conf
echo "nameserver 1.1.1.1" | sudo tee -a /etc/resolv.conf

Step 4: Reset the TCP/IP Stack (Windows)

This is the nuclear option for Windows when the IP stack itself is corrupt — common after malware removal, failed VPN uninstalls, or botched Windows updates.

Run the following commands in an elevated Command Prompt in order:

netsh winsock reset
netsh int ip reset
ipconfig /release
ipconfig /flushdns
ipconfig /renew

Restart the computer after running all five commands. Upon reboot, Windows rebuilds the Winsock catalog and TCP/IP registry keys from scratch.

Step 5: Fix Ethernet-Specific 'No Internet Access'

Ethernet connections (no wireless involved) that show 'connected, no internet' often point to:

1. Wrong cable or faulty port: Try a different Ethernet cable and a different router/switch port. A Cat5e cable in a Gigabit network can cause intermittent data corruption.
2. NIC driver issue: Open Device Manager (Win+X → Device Manager), expand Network Adapters, right-click your Ethernet adapter → Update driver. If a yellow ! is visible, uninstall the driver and reinstall from the manufacturer's website (Intel, Realtek, Broadcom).
3. Speed/Duplex mismatch: Right-click adapter → Properties → Configure → Advanced tab → set Speed & Duplex to Auto Negotiation.
4. VLAN misconfiguration in enterprise environments: If on a corporate network, your switch port may require a specific VLAN tag. Contact your network admin.

Step 6: Check for Proxy or VPN Interference

A proxy setting pointing to a dead server or a VPN client with split tunneling misconfiguration will allow your device to show 'connected' while blocking all real traffic.

Windows — Clear Proxy Settings:

netsh winhttp reset proxy

Also check: Settings → Network & Internet → Proxy → toggle off all manual proxy options.

Disable VPN: Disconnect or uninstall any active VPN client temporarily. If internet returns, the VPN configuration is at fault.

Step 7: Laptop-Specific Fixes

Laptops have additional failure modes due to power management:

1. Wake-from-sleep adapter glitch: Disable, wait 10 seconds, re-enable the network adapter in Device Manager.
2. Power management throttling the NIC: Device Manager → right-click adapter → Properties → Power Management → uncheck 'Allow the computer to turn off this device to save power'.
3. Wi-Fi roaming aggressiveness: Advanced tab in adapter properties → set Roaming Aggressiveness to Medium or High to avoid the adapter clinging to a weak AP signal.
4. Airplane Mode stuck on: Some laptops have a hardware Wi-Fi kill switch. Check physical buttons and fn-key combos.

Step 8: Router and Modem Verification

If multiple devices lose internet at the same time, the issue is upstream:

1. Log into your router admin page (typically 192.168.1.1 or 192.168.0.1, credentials usually on the label).
2. Check the WAN status page — it should show a valid public IP from your ISP. If it shows 0.0.0.0 or Disconnected, call your ISP.
3. Power cycle: Modem off 60 seconds → Modem back on, wait 2 min → Router off 30 seconds → Router back on.
4. Check for ISP outages at your ISP's status page or https://downdetector.com.