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

Understanding Why Your Chromebook Won't Connect to WiFi

Chrome OS handles WiFi through a combination of shill (the connection manager daemon), wpa_supplicant (the 802.11 authenticator), and vendor-specific kernel WiFi drivers. When any layer breaks, the result is a Chromebook that simply refuses to connect — sometimes silently, sometimes with a cryptic message like "EAP authentication failed", "Out of range" (even when the router is inches away), or a spinning indicator that never resolves.

Unlike Windows or Linux, Chrome OS abstracts most networking config away from the user, which means the standard fixes (flushing ARP cache, reinstalling drivers) require crosh shell access or specific flag toggles.

Step 1: Identify Your Specific Symptom

Before applying any fix, match your symptom to a category:

• Spinning icon / "Connecting..." forever → likely DHCP failure or captive portal issue
• "EAP authentication failed" → 802.1X enterprise network problem (clock, cert, or RADIUS)
• "Out of range" when router is nearby → driver issue or MAC randomization conflict
• Worked before Powerwash, now broken → network profile was wiped; router may use MAC filtering
• Only this Chromebook can't connect (others can) → device-specific driver or profile corruption
• No networks visible at all → WiFi hardware disabled or driver crash

Step 2: Quick Triage (Do These First)

2a. Toggle WiFi Off and Back On Click the system tray → WiFi toggle OFF → wait 10 seconds → toggle ON. This forces shill to reinitialize the adapter and re-scan.

2b. Forget the Network and Reconnect

1. Go to Settings → Network → WiFi.
2. Click the gear icon next to your network.
3. Select Forget.
4. Reconnect by selecting the SSID and re-entering credentials.

This is the single most effective fix for post-Powerwash connection failures because Powerwash wipes saved network profiles but sometimes leaves corrupt partial entries.

2c. Verify System Date and Time This is the #1 overlooked fix for EAP authentication failed errors. If your Chromebook's clock is wrong, TLS certificate validation fails and wpa_supplicant rejects the RADIUS server certificate.

• Go to Settings → Advanced → Date & time.
• Enable Set time automatically.
• If the device won't reach NTP because it can't connect, manually set the correct date/time, connect, then re-enable auto.

Step 3: Fix EAP Authentication Failures (Enterprise / WPA2-Enterprise)

If you see "EAP authentication failed" on a school or corporate network:

1. Check the CA Certificate: Go to Settings → Network → WiFi → [your network] → EAP method. Ensure the correct CA certificate is selected, not "Default".
2. Verify Identity fields: The "Identity" field must match exactly what your RADIUS server expects (usually your domain username, e.g. jsmith@company.com).
3. Re-enroll the certificate: If your org uses Google Admin Console, ask IT to push a new client certificate via the Chrome Device Policy.
4. Check RADIUS server reachability: Run ping 8.8.8.8 from crosh on an ethernet connection to verify the network stack works, then test if the RADIUS server IP is reachable.
5. Exact error to look for in shill logs: wpa_supplicant[...]: CTRL-EVENT-EAP-FAILURE EAP authentication failed — this confirms the reject came from the server, not the client.

Step 4: Fix "Out of Range" When Router Is Nearby

This symptom — seeing your SSID but getting "Out of range" immediately — usually means the WiFi adapter is in a bad state or MAC randomization is confusing the router.

4a. Disable MAC Address Randomization

1. Go to Settings → Network → WiFi.
2. Click the gear icon on your saved network.
3. Toggle "Use random MAC addresses" to OFF.
4. Forget and reconnect the network.

Some home and enterprise routers with DHCP reservations or MAC-based access control lists reject randomized MACs.

4b. Check for Driver Issues on HP, Lenovo, and Acer Chromebooks

HP Chromebook 14 (Intel Celeron/Jasper Lake) and Lenovo IdeaPad Flex 5i Chromebook frequently exhibit WiFi driver regressions after channel updates. Acer Chromebook Spin 513 (MediaTek MT8183) also has known issues.

To check your OS version: Settings → About ChromeOS.

If the issue started after a recent update:

• Go to Settings → About ChromeOS → Additional details → Channel.
• Switch from Stable to LTS (Long-Term Support) channel, or roll back by enabling Developer mode and using update_engine_client --rollback in crosh.

Step 5: Use crosh for Advanced Diagnostics

Open crosh by pressing Ctrl + Alt + T.

Key commands:

network_diag --wifi          # Run built-in WiFi diagnostics
ping 8.8.8.8 -c 5           # Test basic IP connectivity
ping google.com -c 5         # Test DNS resolution
route                        # Show routing table
ifconfig                     # Show adapter IP and state

To view shill logs for deeper analysis:

sudo cat /var/log/net.log | grep -i 'wifi\|eap\|dhcp\|fail' | tail -50

Step 6: Flush DNS and Socket Pools

For cases where the Chromebook connects but pages don't load, or where DHCP completes but DNS fails:

1. Open Chrome and navigate to chrome://net-internals/#dns.
2. Click Clear host cache.
3. Navigate to chrome://net-internals/#sockets.
4. Click Flush socket pools.
5. Navigate to chrome://net-internals/#proxy.
6. Click Re-apply settings.

Step 7: Post-Powerwash WiFi Recovery

After a Powerwash (chromebook won't connect to wifi after power wash), your saved networks are gone but your router's DHCP/ARP cache may still hold the old lease. Do the following:

1. On your router admin page (usually 192.168.1.1 or 192.168.0.1), go to the DHCP lease table and delete the entry for your Chromebook's hostname.
2. If the router uses MAC filtering, re-add your Chromebook's hardware MAC (find it under Settings → Network → WiFi → [connected network] → gear icon → MAC address).
3. Force-forget all networks on the Chromebook via crosh:

   sudo stop shill
   sudo rm -rf /var/cache/shill/default.profile
   sudo start shill
   

   This is a targeted alternative to a full Powerwash and clears all network state.

Step 8: Last Resort — Full Powerwash or Hardware Check

If none of the above works:

• Powerwash: Settings → Advanced → Reset settings → Powerwash. Backs up nothing locally — ensure Google Drive sync is complete first.
• Hardware test: Press Ctrl + Alt + T for crosh, then run memory_test and check if WiFi adapter is listed under sudo lspci (Intel/MediaTek cards should appear). If not listed, the adapter may have failed physically.
• Contact OEM support: HP, Lenovo, and Acer all have Chromebook-specific support lines with ChromeOS diagnostics access.