Chromebook Won't Connect to WiFi: Complete Troubleshooting Guide (All Models & Error Types)

Understanding Why Your Chromebook Won't Connect to WiFi

Chromebooks run ChromeOS, a Linux-based operating system that handles networking through a combination of wpa_supplicant (for WPA/WPA2/WPA3 and 802.1x/EAP authentication), dhcpcd or shill (for IP assignment), and the shill network manager daemon. When any of these components encounters an inconsistency — a stale lease, an invalid certificate, a firmware hiccup — your Chromebook silently fails to connect or shows vague errors like "Not connected" or "EAP authentication failed."

This guide covers every scenario: fresh out-of-the-box, after a Powerwash, on enterprise/school networks, and model-specific issues with HP, Lenovo, and Acer Chromebooks.

Step 1: Identify the Exact Symptom

Before applying any fix, classify which failure mode you're experiencing:

• WiFi toggle is grayed out: The wireless adapter is not initialized. Usually a driver or firmware issue.
• Networks list is empty: Adapter is on, but scanning fails. Common after ChromeOS updates on certain Intel WiFi chipsets.
• Network visible but won't connect: Password rejected, DHCP failure, or MAC filtering at the router.
• "EAP authentication failed": Enterprise/school network 802.1x — certificate issue or wrong identity/password.
• Connected but no internet: IP assigned, but DNS or routing is broken.
• Chromebook won't connect to WiFi after Powerwash: Network profile was wiped; the network needs to be re-added manually.
• "Out of range" error on nearby network: Signal strength issue, band mismatch (5 GHz at range limit), or driver bug misreporting signal.

Step 2: Quick Wins (Try These First)

2a. Restart the Chromebook Hold the Power button → select "Restart" (not Shut Down). This reloads the shill daemon and often resolves transient adapter issues.

2b. Toggle WiFi Off and Back On

1. Click the system tray (bottom-right corner).
2. Click the WiFi icon to disable it.
3. Wait 10 seconds.
4. Click again to re-enable.

If the WiFi icon is permanently grayed out, press Refresh + Power simultaneously for a hard reboot (EC reset).

2c. Forget the Network and Re-add It

1. Open Settings → Network → WiFi.
2. Click the gear icon next to your network name.
3. Select "Forget" at the bottom.
4. Reconnect by selecting the SSID and entering credentials fresh.

This is the #1 fix for Chromebooks that won't connect after a Powerwash — the old profile is gone, but the device sometimes attempts to use a ghost entry.

Step 3: Fix EAP Authentication Failures

If you're on a school, university, or enterprise network and see "EAP authentication failed" or the connection spins indefinitely, the certificate chain or identity string is misconfigured.

3a. Re-enter EAP Credentials

1. Go to Settings → Network → WiFi → Click your network.
2. Under "EAP method", verify the correct method: PEAP, TLS, TTLS, or LEAP.
3. For PEAP/TTLS: confirm your Identity (usually your org email or username) and Password.
4. For TLS: ensure the Client Certificate is installed. Go to Settings → Privacy and Security → Manage Certificates → Import your .p12 file.
5. Set Server CA certificate — if your IT team hasn't provided one, select "Do not check" (insecure but functional for testing).

3b. Check Certificate Validity via crosh Open crosh (Ctrl+Alt+T) and run:

cert_verify_tool --input_chain=/etc/ssl/certs/ca-certificates.crt

An expired or missing root CA certificate causes silent EAP failures.

Step 4: Diagnose with Built-in Tools

4a. chrome://network-internals Type chrome://network-internals in the address bar. This is the most powerful built-in WiFi debugging tool.

• WiFi tab: Shows current SSID, signal strength (dBm), frequency band, security type, and connection state machine.
• Logs tab: Enable "WiFi debugging" and attempt to connect. The logs will show the exact failure point (association, 4-way handshake, DHCP, etc.).
• DHCP tab: Shows current lease details. If IP is 169.254.x.x, DHCP has failed.

4b. chrome://net-internals/#dns If WiFi connects but pages don't load:

1. Navigate to chrome://net-internals/#dns.
2. Click "Clear host cache".
3. Go to chrome://net-internals/#sockets → "Flush socket pools".

4c. crosh Network Diagnostics Press Ctrl+Alt+T to open the crosh terminal:

# Check current network status
network_diag --wifi

# Ping the router gateway
ping 192.168.1.1

# Check DNS resolution
nslookup google.com

# View current IP configuration
ifconfig

# Force DHCP renewal
dhclient -r && dhclient

# Check WiFi signal and available networks
iwlist scan

Step 5: Model-Specific Fixes

HP Chromebook (e.g., HP Chromebook 14, x360) HP Chromebooks using Realtek RTL8821CE chipsets are known to experience WiFi drops after the ChromeOS 107-110 update range. Verify:

1. Check ChromeOS version: Settings → About ChromeOS → Build number.
2. If on a known bad build, connect via Ethernet (USB-C adapter) → update ChromeOS to the latest stable channel.
3. If no Ethernet available, use your phone as a USB hotspot → tether → update.

Lenovo Chromebook (e.g., Flex 5i, IdeaPad Duet) Lenovo Chromebooks with Intel AX200/AX201 WiFi 6 cards sometimes show an empty network list due to a wpa_supplicant race condition on boot:

1. Open crosh (Ctrl+Alt+T).
2. Type: restart wpa_supplicant — if this command errors, instead perform a hard EC reset: hold Refresh + Power for 3 seconds.
3. After restart, WiFi scanning should resume normally.

Acer Chromebook (e.g., Spin 311, Chromebook 315) Acer Chromebooks running MediaTek MT7921 WiFi adapters may show "out of range" errors on networks that are physically nearby. This is a driver bug causing incorrect RSSI reporting:

1. Try disabling WiFi 6 (802.11ax) on your router — force it to 802.11ac (WiFi 5) mode.
2. Or, under your router's Advanced Wireless settings, disable "Band Steering" and manually set the 5 GHz SSID to a different name. Connect the Acer to the 2.4 GHz band temporarily.

Step 6: Router-Side Checks

1. MAC Address Filtering: Log into your router admin panel (typically 192.168.1.1 or 192.168.0.1). Disable MAC filtering or add your Chromebook's MAC address. Find your Chromebook's WiFi MAC: Settings → Network → WiFi → your network → Network tab → MAC Address.
2. DHCP Pool: If many devices are on the network, the DHCP pool may be exhausted. Increase the pool range in router settings (e.g., extend from .100-.150 to .100-.250).
3. WPA3 Compatibility: Some older Chromebooks don't fully support WPA3-SAE. Set your router to WPA2/WPA3 mixed mode.
4. Channel Congestion: Use a WiFi analyzer app to find a less congested channel. Set your router to a fixed channel (1, 6, or 11 for 2.4 GHz; 36, 40, 44, or 48 for 5 GHz).

Step 7: Last Resort — Powerwash

If your Chromebook still won't connect after all steps above, a Powerwash (factory reset) resolves deep system state corruption:

1. Back up your data to Google Drive — Powerwash erases all local files.
2. Go to Settings → Advanced → Reset settings → Powerwash → Restart.
3. After the device restarts to the setup screen, connect to WiFi fresh.
4. If WiFi still fails at the setup screen, the issue is hardware (antenna cable, WiFi card failure) — contact manufacturer support.

Note: "Chromebook won't connect to WiFi after Powerwash" is itself a common complaint. After Powerwash, you must manually re-enter all network credentials, including EAP certificates for enterprise networks. These are not backed up to your Google Account.