Why does my Chromebook say 'Network Not Available' but it shows connected to WiFi?

This happens because WiFi association (connecting to the router) is separate from internet connectivity (routing to the internet). Your Chromebook successfully joined the WiFi network (got an IP from the router), but something beyond the router — such as DNS resolution, the ISP connection, or a captive portal — is blocking internet traffic. Chrome OS detects this via its connectivity check to Google servers and shows 'Network Not Available'. Start by flushing DNS at chrome://net-internals/#dns and toggling Airplane Mode.

My Acer Chromebook shows 'Network Not Available' — is this a known hardware issue?

Yes, some Acer Chromebook models with Intel AX201 or MediaTek WiFi chips have a firmware bug where the adapter enters a low-power idle state while Chrome OS still reports it as connected. The symptom is 'Network Not Available' that resolves after toggling Airplane Mode or rebooting. Ensure your Acer Chromebook is on the latest Chrome OS update (Settings > About Chrome OS > Check for updates), which contains WiFi driver patches.

How do I fix 'Network Not Available' on a Lenovo Chromebook after waking from sleep?

Lenovo Chromebooks (particularly the Duet and Flex 5) are known to lose DNS resolution after sleep/wake cycles on Chrome OS versions 102–108. The quickest fix is to toggle Airplane Mode on and off after waking. For a permanent fix, update to Chrome OS 109 or later. If updates are not available for your device, you can also set a custom DNS server (8.8.8.8) in network settings to reduce the failure frequency.

Will Powerwashing my Chromebook fix the 'Network Not Available' error?

Powerwash (factory reset) resolves the error in cases where Chrome OS system files, certificate stores, or network configuration databases are corrupted — often after a failed OS update. However, Powerwash erases all local data and downloaded apps. Try all other steps first: forget/reconnect WiFi, flush DNS, renew DHCP lease via Crosh, and change DNS servers. Only Powerwash if those steps fail. Ensure Google Drive sync is current before proceeding.

I see 'ERR_NETWORK_CHANGED' in Chrome instead of 'Network Not Available' — are these the same issue?

They are related but slightly different. 'ERR_NETWORK_CHANGED' in Chrome means the network configuration changed mid-request (e.g., IP reassignment or a WiFi handoff), which Chrome treats as an error. 'Network Not Available' is a Chrome OS system-level message indicating no verified internet path exists. Both can have the same root causes (DHCP conflict, DNS failure, adapter power management issues) and respond to the same fixes: flush DNS at chrome://net-internals/#dns, toggle Airplane Mode, and renew your DHCP lease.

Chromebook 'Network Not Available' Error: Complete Troubleshooting Guide

Fix the 'Network Not Available' error on Chromebook even when connected to WiFi. Step-by-step solutions for Acer, Lenovo, and all Chromebook models.

Last updated: February 27, 2026

Last verified: February 27, 2026

2,298 words

Key Takeaways

Root Cause 1: Chrome OS captive portal detection or DNS resolution failure causes 'Network Not Available' even when the device appears connected to WiFi — the router handshake completes but internet routing breaks at the ISP or gateway level.
Root Cause 2: Corrupted network stack, stale DHCP lease, or misconfigured proxy settings prevent Chrome OS from establishing a verified internet connection, triggering the error on Acer Chromebook, Lenovo Chromebook, and other models alike.
Root Cause 3: Chrome OS system partition or certificate store corruption — often after a failed OS update — blocks HTTPS validation, making all network connectivity appear unavailable to the browser and system services.
Quick Fix Summary: Start by forgetting and reconnecting to the WiFi network, then flush DNS via chrome://net-internals/#dns, toggle Airplane Mode, check proxy/VPN settings, run a Powerwash as a last resort, or use the Crosh shell to renew your DHCP lease and ping test connectivity.

Fix Approaches Compared
Method	When to Use	Time	Risk
Forget & Reconnect WiFi	First attempt — stale WiFi credentials or DHCP conflict	2 min	Low — no data loss
Flush DNS via chrome://net-internals	Network connected but pages won't load; DNS cache corruption	1 min	None — safe browser action
Toggle Airplane Mode	Quick reset of network stack after connectivity drop	30 sec	None
Disable Proxy / VPN	Error appeared after installing an extension or enabling VPN	2 min	Low — may disconnect VPN
Crosh DHCP Lease Renewal	IP address conflict or stale lease from router	3 min	Low — requires Crosh shell
Chrome OS Network Reset via Settings	Persistent error across multiple networks	5 min	Low — resets saved networks
Disable DNS-over-HTTPS	Intermittent failure with secure DNS providers	2 min	Very Low
Powerwash (Factory Reset)	All other methods failed; suspected OS corruption	30 min	High — erases local data
Recovery Mode / OS Reinstall	Failed update bricked network stack; Powerwash ineffective	60 min	High — full reinstall

Understanding the 'Chromebook Network Not Available' Error

The exact error message Chrome OS displays is:

"Network not available"

In some cases users also see:

"No network available" "Cannot connect to the internet" "ERR_NETWORK_CHANGED" (in the Chrome browser) "ERR_NAME_NOT_RESOLVED" (DNS failure variant)

This error is deceptive — your Chromebook shows a WiFi signal with full bars, yet no web pages load and Chrome OS services such as the Play Store, Google Drive sync, and system updates fail. The WiFi association (Layer 2) succeeded, but internet routing (Layer 3+) broke down.

This affects all Chromebook brands including Acer Chromebook models (Spin 514, 315, CB315), Lenovo Chromebook models (Duet, Flex 5, IdeaPad), Samsung, HP, and ASUS.

Step 1: Confirm the Exact Failure Mode

Before applying any fix, identify which layer is broken:

A) Are you getting a valid IP address? Open Crosh (Ctrl+Alt+T) and type:

ip addr show

If your IP starts with 169.254.x.x, you have an APIPA address — your router's DHCP server did not assign you an IP. This is a DHCP failure.

If your IP looks normal (e.g., 192.168.x.x or 10.x.x.x), proceed to DNS testing.

B) Can you ping the gateway?

ping -c 4 192.168.1.1

(Replace with your actual gateway IP found via ip route show)

If the gateway ping fails, the problem is between your Chromebook and the router — likely a WiFi driver or association issue.

C) Can you ping a public IP (bypassing DNS)?

ping -c 4 8.8.8.8

If this succeeds but DNS lookups fail, you have a DNS-only problem.

D) Can you resolve DNS?

nslookup google.com

If you get NXDOMAIN or a timeout, DNS is broken.

Step 2: Apply Fixes in Order of Complexity

Fix 1 — Toggle Airplane Mode (30 seconds)

Click the system tray (bottom-right) → Click the WiFi icon to open Network settings → Enable Airplane Mode → Wait 10 seconds → Disable Airplane Mode → Reconnect to WiFi.

This forces a full network stack reset without rebooting.

Fix 2 — Forget and Reconnect to WiFi (2 minutes)

Open Settings → Network → Wi-Fi
Click the connected network → Forget
Wait 30 seconds, then reconnect by entering your password again.

This clears the cached network profile including any corrupted DHCP lease stored by Chrome OS.

Fix 3 — Flush DNS Cache (1 minute)

Open a new Chrome tab and navigate to:

chrome://net-internals/#dns

Click "Clear host cache".

Then navigate to:

chrome://net-internals/#sockets

Click "Flush socket pools".

This clears all cached DNS entries and open socket connections, forcing Chrome to re-resolve all hostnames.

Fix 4 — Check and Disable Proxy Settings (2 minutes)

Open Settings → Network → Wi-Fi → Click your connected network
Scroll to Proxy → Ensure it is set to Direct Internet connection (not Manual or Auto)
If a proxy is configured, clear it.

Also disable any browser extensions that act as VPN or proxy: open chrome://extensions/ and toggle off any network-modifying extensions.

Fix 5 — Renew DHCP Lease via Crosh (3 minutes)

Open Crosh with Ctrl+Alt+T and run:

dhclient -r
dhclient

If dhclient is unavailable (it is on some builds), use:

ifconfig eth0 down
ifconfig eth0 up

Or for WiFi:

ifconfig wlan0 down
ifconfig wlan0 up

This releases your current IP lease and requests a fresh one from the router's DHCP server.

Fix 6 — Change DNS Servers (3 minutes)

Open Settings → Network → Wi-Fi → Click your connected network
Expand Network section → Set Name Servers to Custom name servers
Enter 8.8.8.8 and 8.8.4.4 (Google DNS) or 1.1.1.1 and 1.0.0.1 (Cloudflare DNS)

This bypasses a broken ISP DNS server.

Fix 7 — Disable DNS-over-HTTPS (2 minutes)

Navigate to chrome://settings/security → Scroll to "Use secure DNS" → Toggle it Off.

Some networks (hotel WiFi, captive portals, enterprise networks) block DoH traffic, causing the network to appear unavailable.

Fix 8 — Chrome OS Network Settings Reset (5 minutes)

Open Settings → Network
At the bottom, click "Reset settings" (if available for your Chrome OS version)
Alternatively, go to Settings → About Chrome OS → Diagnostics and run the Connectivity test

Fix 9 — Powerwash / Factory Reset (30 minutes — data loss)

Only if all above steps fail:

Sign out of your Chromebook
Press Ctrl+Shift+Alt+R
Click Restart → Powerwash → Continue
Follow the setup wizard and reconnect to WiFi

Warning: This erases all local data. Ensure Google Drive sync is up to date before proceeding.

Fix 10 — Chrome OS Recovery (60 minutes — worst case)

If a failed system update corrupted the network stack and Powerwash does not resolve it:

On a separate device, download the Chromebook Recovery Utility from the Chrome Web Store
Create a recovery USB for your specific Chromebook model
Boot your Chromebook into Recovery Mode (Esc+Refresh+Power)
Follow on-screen prompts to reinstall Chrome OS

Acer Chromebook — Model-Specific Notes

Acer Chromebook models (especially the Spin series) have had a known firmware bug where the WiFi adapter (Intel AX201) enters a low-power state that disconnects from the router at Layer 2 while Chrome OS still shows it as connected. Update your Chromebook to the latest stable channel: Settings → About Chrome OS → Check for updates.

Lenovo Chromebook — Model-Specific Notes

Lenovo IdeaPad Duet and Flex 5 Chromebooks running Chrome OS 102–108 had an issue where DNS resolution failed after sleep/wake cycles due to a network manager bug. The fix is to toggle Airplane Mode after waking from sleep, or update to Chrome OS 109 or later.

Frequently Asked Questions

bash

# ============================================================
# Chromebook 'Network Not Available' Diagnostic Script
# Run commands in Crosh: press Ctrl+Alt+T to open Crosh shell
# Note: Crosh is a restricted shell; use 'shell' for more access
# (developer mode required for full shell access)
# ============================================================

# --- Step 1: Open Crosh shell ---
# Press Ctrl+Alt+T in Chrome OS
# Type: shell  (only available in Developer Mode)
# Or run individual commands directly in Crosh

# --- Step 2: Check network interfaces ---
ip addr show
# Look for wlan0 or eth0 with a valid IP (192.168.x.x or 10.x.x.x)
# 169.254.x.x = APIPA = DHCP failure

# --- Step 3: Show routing table ---
ip route show
# Look for a default route like: default via 192.168.1.1 dev wlan0

# --- Step 4: Ping the gateway (replace with your gateway IP) ---
GATEWAY=$(ip route show | grep default | awk '{print $3}')
echo "Gateway: $GATEWAY"
ping -c 4 "$GATEWAY"
# Expected: 4 packets transmitted, 4 received, 0% packet loss

# --- Step 5: Ping a public IP (bypasses DNS) ---
ping -c 4 8.8.8.8
# If this works but Step 6 fails, DNS is the problem

# --- Step 6: Test DNS resolution ---
nslookup google.com
# Or:
curl -I https://www.google.com
# Expected: HTTP/2 200

# --- Step 7: Check current DNS servers ---
cat /etc/resolv.conf
# Shows active nameservers; compare with what you set in Settings

# --- Step 8: Renew DHCP lease ---
# Release current IP
sudo dhclient -r wlan0 2>/dev/null || echo "dhclient not available, using ip command"
# Request new IP
sudo dhclient wlan0 2>/dev/null

# Alternative DHCP renewal using ip command:
sudo ip link set wlan0 down && sleep 2 && sudo ip link set wlan0 up

# --- Step 9: Test connectivity to Google's captive portal check ---
curl -sv http://clients3.google.com/generate_204
# Expected response: HTTP/1.1 204 No Content
# Chrome OS uses this URL to detect internet availability
# If this returns 204, the OS should show network as available

# --- Step 10: Check WiFi signal strength ---
iwconfig wlan0
# Look at 'Link Quality' and 'Signal level'
# Low signal (< -75 dBm) can cause intermittent disconnects

# --- Step 11: Flush DNS via Chrome (run in browser address bar) ---
# chrome://net-internals/#dns  -> Clear host cache
# chrome://net-internals/#sockets  -> Flush socket pools

# --- Step 12: Check for conflicting network processes ---
ps aux | grep -E 'dhcp|wpa|network'

# --- Step 13: View recent network-related system logs ---
journalctl -u shill --since '10 minutes ago' 2>/dev/null | tail -50
# 'shill' is Chrome OS network manager; look for ERROR or WARN lines

# ============================================================
# Quick one-liner to test all layers at once:
# ============================================================
echo "=== IP Addresses ==="; ip addr show | grep 'inet '
echo "=== Default Gateway ==="; ip route show | grep default
echo "=== Gateway Ping ==="; ping -c 2 $(ip route show | grep default | awk '{print $3}') 2>&1 | tail -2
echo "=== Public IP Ping ==="; ping -c 2 8.8.8.8 2>&1 | tail -2
echo "=== DNS Test ==="; nslookup google.com 2>&1 | tail -4
echo "=== Captive Portal Check ==="; curl -so /dev/null -w "%{http_code}" http://clients3.google.com/generate_204

Error Medic Editorial

The Error Medic Editorial team is composed of senior DevOps engineers, SREs, and network administrators with 10+ years of experience diagnosing connectivity, OS, and cloud infrastructure issues across enterprise and consumer environments. Our guides are tested on real hardware and verified against official vendor documentation before publication.

Sources

Explore More wifi Guides

"Connected Without Internet" Error: Complete Fix Guide for Wi-Fi, Routers, Android & ISP Issues

Fix the "Connected Without Internet" error on Wi-Fi, Android, hotspots & routers. Step-by-step commands for Cox, CenturyLink, Frontier, T-Mobile & more.

"Connected Without Internet" Error: Complete Fix Guide for WiFi, Routers, Android & ISP Issues

Fix the 'connected without internet' error on WiFi, Android, hotspots & ISPs like Cox, CenturyLink & Fios. Step-by-step commands and solutions inside.

"Connected Without Internet" Error: What It Means and How to Fix It (All Devices & ISPs)

Fix the 'Connected Without Internet' WiFi error on Android, router, hotspot, Cox, CenturyLink, Fios & more. Step-by-step commands and solutions inside.