Chromebook 'Network Not Available' Error: Complete Troubleshooting Guide (2024)

Understanding the 'Network Not Available' Error on Chromebooks

The 'Network Not Available' message on Chrome OS typically appears in one of two ways:

1. In the system tray: A network icon with an exclamation mark or a message reading "Not connected" or "Network not available" even though your Chromebook shows a WiFi signal.
2. In the browser: Chrome displays ERR_NETWORK_CHANGED, ERR_INTERNET_DISCONNECTED, or ERR_NAME_NOT_RESOLVED when you try to load any URL.

On Acer Chromebooks (particularly the Spin 311 and Chromebook 314) and Lenovo Chromebooks (IdeaPad Flex 3, Duet), this error frequently follows a Chrome OS update or a sleep/wake cycle. The underlying cause is almost always one of:

• Stale DNS cache with poisoned or expired entries
• DHCP lease expiry where the IP address was not properly renewed
• Captive portal detection loop where Chrome OS mistakenly flags a network as requiring sign-in
• Corrupted network profile stored in the user's Chrome OS session
• WiFi driver regression introduced via an OTA Chrome OS update

Step 1: Confirm the Actual Connectivity State

Before fixing anything, determine whether the problem is at the WiFi/IP layer or the DNS/routing layer.

Check your IP address: Open Chrome and navigate to chrome://system. Search for ifconfig in the log entries. Look for your WiFi interface (wlan0 typically). If you see inet addr: 169.254.x.x, your Chromebook did NOT get a valid DHCP lease — this is an APIPA address indicating a DHCP failure.

A valid IP will look like 192.168.x.x or 10.x.x.x.

Check DNS resolution: Navigate to chrome://net-internals/#dns. Click Clear host cache. Then try loading a site. If you see ERR_NAME_NOT_RESOLVED in chrome://net-internals/#events, your DNS is the culprit.

Check the captive portal status: Go to chrome://net-internals/#chromeos. Look at the Portal Detection section. If status shows portal instead of online, Chrome OS thinks you need to complete a captive portal sign-in, even if you don't.

Step 2: Quick Fixes (No Developer Mode Required)

Fix A — Flush DNS Cache

1. Open Chrome and go to chrome://net-internals/#dns
2. Click the Clear host cache button
3. Navigate to chrome://net-internals/#sockets
4. Click Flush socket pools
5. Reload your browser and test connectivity

Fix B — Change Your DNS Servers

1. Click the clock in the bottom-right corner → Settings icon
2. Go to Network → Click your WiFi network name
3. Expand Network section → Toggle Name servers from Automatic to Custom
4. Enter 8.8.8.8 and 8.8.4.4 (Google) or 1.1.1.1 and 1.0.0.1 (Cloudflare)
5. Click outside the field to save, then test

Fix C — Forget and Reconnect to WiFi

1. Click the system tray → WiFi network name → Forget
2. Wait 10 seconds
3. Reconnect by selecting the network and entering credentials
4. This forces a fresh DHCP handshake and clears cached network state

Fix D — Toggle WiFi Off and On

1. Press Alt + Shift + S to open Quick Settings (or click the system tray clock)
2. Click the WiFi icon to disable it
3. Wait 15 seconds
4. Click again to re-enable
5. This resets the WiFi adapter state without losing your network profile

Fix E — Reset Chrome Network Settings

1. Open Chrome → Navigate to chrome://flags
2. Search for network and reset any experimental flags you've changed
3. Alternatively: Settings → Reset settings → Restore settings to their original defaults (this only resets Chrome browser settings, not OS-level network config)

Step 3: Intermediate Fixes

Fix F — Chrome OS Network Reset

This removes ALL saved WiFi networks and resets the network stack:

1. Go to Settings → Advanced → Reset settings
2. Click Reset under Reset network settings
3. All saved WiFi passwords are deleted — you'll need to reconnect

Fix G — Sign Out and Sign Back In

Network policies can be scoped to a user profile. Signing out forces a fresh profile load:

1. Click the system tray → your account name → Sign out
2. Sign back in with your Google account
3. Test network access before launching Chrome extensions

Fix H — Check for Chrome OS Update

A known WiFi driver bug may have a patch available:

1. Settings → About Chrome OS → Check for updates
2. Install any available update and restart
3. Acer Chromebooks running Chrome OS 114–116 had documented WiFi regressions fixed in 117

Step 4: Advanced Fixes (Developer Mode / Crosh Shell)

Warning: Enabling Developer Mode will wipe local data. Only use if other methods fail.

Once in Developer Mode, press Ctrl + Alt + T to open Crosh, then type shell to access the full bash shell.

Run the following diagnostic and fix commands:

# Check current IP configuration
ip addr show wlan0

# Check routing table
ip route show

# Manually release and renew DHCP lease
dhclient -r wlan0
dhclient wlan0

# Test DNS resolution manually
nslookup google.com 8.8.8.8

# Ping gateway to test layer-3 connectivity
ping -c 4 $(ip route | grep default | awk '{print $3}')

# Flush ARP cache
ip neigh flush all

# Check for WiFi driver errors in kernel log
dmesg | grep -i 'wlan\|wifi\|80211\|firmware' | tail -30

Step 5: Last Resort — Powerwash

If all else fails and the 'Network Not Available' error persists across reboots, user accounts, and WiFi networks, a Powerwash (factory reset) is the most reliable fix:

1. Press Ctrl + Alt + Shift + R
2. Click Restart
3. On the reset screen, select Powerwash → Continue
4. Sign back in with your Google account

After Powerwash, all Chrome OS settings are fresh and network corruption is eliminated. Your Google Drive files and bookmarks sync back automatically.

Acer Chromebook Specific Notes

Acer Chromebook models (especially the CB315, Spin 513, and 314) have had recurring issues with WiFi dropping after the lid is opened from sleep. The fix is:

1. Settings → Device → Power → Disable Sleep when lid is closed
2. Or update to Chrome OS 117+ which patches the MediaTek WiFi driver regression

Lenovo Chromebook Specific Notes

Lenovo IdeaPad Duet and Flex 5i Chromebooks sometimes show 'Network Not Available' due to a conflict between the Intel WiFi driver and Chrome OS's network manager after resume. Disabling WiFi power saving via the Developer Mode shell resolves this:

iw dev wlan0 set power_save off

To make this persistent across reboots, add it to /etc/rc.local (requires Developer Mode).