Chromebook 'Network Not Available' Error: Complete Troubleshooting Guide

Understanding the 'Network Not Available' Error on Chromebook

When your Chromebook displays 'Network not available' — either in the system tray, on the login screen, or as a Chrome browser error — it signals a disconnect between the OS reporting a Wi-Fi association and the actual ability to route packets to the internet. The exact strings you may encounter include:

• Network not available
• No network available
• ERR_NETWORK_CHANGED
• ERR_NAME_NOT_RESOLVED
• DNS_PROBE_FINISHED_NO_INTERNET
• Network not available. Try connecting to a network. (login screen variant)

This guide covers all Chromebook brands — including Acer Chromebook network not available (Chromebook 314, Spin 514) and Lenovo Chromebook network not available (IdeaPad Flex 3, Duet) — since the Chrome OS network stack is identical across OEMs.

Step 1: Verify the Actual Connection State

Before changing anything, confirm exactly what Chrome OS sees.

1. Click the system tray (bottom-right clock area).
2. Click the Wi-Fi icon — note whether it shows full bars with an exclamation mark (!) or a disconnected icon.
3. Open a new Chrome tab and navigate to chrome://network-internals/ — this is your diagnostic dashboard.
4. In the left pane, click Wi-Fi — confirm connection_state shows connected and that an IP address, gateway, and DNS server are listed.
5. Navigate to chrome://net-internals/#dns and look for repeated net::ERR_NAME_NOT_RESOLVED entries.

If the device shows connected with an IP but no internet, you have a DNS or routing problem, not a Wi-Fi association problem. If it shows no IP at all, you have a DHCP failure.

Step 2: Quick Restart Sequence (90-Second Fix)

This resolves transient stack errors in the majority of cases:

1. Toggle Airplane Mode — Click system tray → click the Wi-Fi toggle twice (off, wait 5 seconds, on).
2. Restart the Chromebook — Hold Power → select Restart (not Shut Down; Restart fully clears kernel network buffers).
3. Restart your router/modem — Unplug power for 30 seconds, plug back in, wait for full boot (~90 seconds), then reconnect the Chromebook.

Step 3: Forget and Re-Add the Wi-Fi Network

A corrupted network profile is a leading cause of Chromebook network not available but connected symptoms.

1. Go to Settings → Network → Wi-Fi.
2. Click the gear icon next to your network.
3. Click Forget at the bottom.
4. Reconnect by selecting the network from the list and entering your password.
5. Before reconnecting, confirm your router is broadcasting on 2.4 GHz as well as 5 GHz — some Chromebook Wi-Fi cards (notably Mediatek MT7921 in budget Lenovo models) have intermittent 5 GHz association issues.

Step 4: Flush DNS Cache and Switch DNS Servers

1. Open Chrome and go to chrome://net-internals/#dns.
2. Click Clear host cache.
3. Go to chrome://net-internals/#sockets and click Flush socket pools.
4. To change DNS servers permanently:
   • Settings → Network → Wi-Fi → click your network name.
   • Click the Network tab.
   • Under Name servers, select Custom name servers.
   • Enter 8.8.8.8 and 8.8.4.4 (Google) or 1.1.1.1 and 1.0.0.1 (Cloudflare).
5. Reconnect and test.

Step 5: Check for Captive Portals and Proxy Issues

Hotel, school, or corporate networks often require clicking a login page before granting internet access. Chrome OS should auto-detect this and open a portal window, but this detection can fail.

1. With Wi-Fi connected, open Chrome and manually navigate to http://captive.apple.com or http://neverssl.com — these plain HTTP pages force captive portals to intercept.
2. If a login page appears, authenticate and test connectivity.
3. If a proxy is configured: Settings → Network → Proxy → verify it's set to Direct Internet connection unless you intentionally use a proxy.
4. Disable any Chrome extensions that inject proxy settings (common culprits: VPN extensions, ad-blockers with proxy features). Go to chrome://extensions/ and toggle them off one by one.

Step 6: Reset Network Configuration via crosh

For persistent cases, Chrome OS's built-in developer shell (crosh) lets you interact with the network stack directly.

Open crosh with Ctrl+Alt+T, then use the commands shown in the code_block section below.

Step 7: Acer Chromebook — Specific Notes

Several Acer Chromebook models (Chromebook 315, Chromebook Spin 713) have reported Wi-Fi dropping after suspend/resume due to a firmware bug in the Intel AX201 Wi-Fi card. Symptoms match 'network not available but connected to Wi-Fi' exactly.

• Ensure Chrome OS is fully updated: Settings → About Chrome OS → Check for updates.
• In crosh, run connectivity show devices and check if the Wi-Fi device state is enabled.
• If the Wi-Fi card shows as disabled after wake, the workaround is: Settings → Device → Power → disable Sleep when lid is closed, or enable Keep Wi-Fi on during sleep.

Step 8: Lenovo Chromebook — Specific Notes

Lenovo Chromebook (IdeaPad 3, Duet, Flex 5) users running Chrome OS 105+ have reported DNS failures tied to the Mediatek Wi-Fi driver. The fix:

1. Go to chrome://flags/#dns-over-https.
2. Set Secure DNS lookups to Enabled.
3. In Settings → Privacy and security → Security → Use secure DNS, choose With: Cloudflare (1.1.1.1).
4. Reboot and test.

Step 9: Powerwash (Last Resort)

If all steps above fail, a Powerwash resets Chrome OS to factory defaults without reinstalling the OS.

1. Settings → Advanced → Reset settings → Powerwash → Restart.
2. Alternatively, on the login screen, press Ctrl+Alt+Shift+R.
3. Warning: This erases all local files, Android apps, and Linux containers. Sync your Google Drive files first.
4. After Powerwash, connect to Wi-Fi before signing in to allow Chrome OS to pull the latest updates immediately.