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

Understanding Why Your Chromebook Won't Connect to WiFi

Chromebook WiFi failures fall into four distinct layers: network profile/credential issues, OS-level driver or firmware bugs, enterprise authentication failures, and hardware-specific OEM problems. Identifying the layer before applying a fix saves significant time and avoids unnecessary resets.

Error messages you might see include:

• EAP authentication failed
• Not connected — out of range
• Failed to obtain IP address
• Authentication error. Try again.
• No networks found
• Unable to connect to [SSID]

Step 1: Confirm the Failure Scope

Before touching settings, answer these questions:

1. Can other devices connect to the same WiFi network? If no, the router is the problem.
2. Does the Chromebook connect to a different network (e.g., mobile hotspot)? If yes, the issue is network-specific.
3. Did the issue start after a Chrome OS update, power wash, or physical move?
4. Are you on a corporate/school network using WPA2-Enterprise or 802.1X?

Open chrome://network-internals in your Chromebook browser. Click WiFi in the left sidebar. This shows real-time connection state, DHCP lease details, signal strength (RSSI), and authentication errors. Screenshot this before proceeding.

Step 2: Basic Restart and Forget/Reconnect

2a. Hard restart your Chromebook: Press and hold the Power button for 3 seconds, then select Shut down (not sleep). Wait 30 seconds. Power on.

2b. Restart your router: Unplug the router power cable for 30 seconds. Plug back in. Wait 2 minutes for it to fully initialize.

2c. Forget the WiFi network and reconnect:

1. Click the system clock (bottom-right corner)
2. Click the WiFi network name
3. Click the gear icon next to the SSID
4. Click Forget
5. Reconnect from scratch, entering the password manually

This resolves roughly 40% of Chromebook WiFi failures by clearing stale DHCP leases and cached authentication tokens.

Step 3: Fix EAP Authentication Failed

The error EAP authentication failed appears on WPA2-Enterprise networks (common in schools, universities, and corporate environments). It means the RADIUS server rejected your Chromebook's credentials or certificate.

Common causes:

• Expired or missing CA certificate on the Chromebook
• Incorrect Identity or Anonymous identity field format
• EAP method mismatch (PEAP vs. EAP-TLS vs. TTLS)
• User account password changed on the domain but not updated on the Chromebook

Fix 3a — Re-enter credentials:

1. Forget the enterprise network (Step 2c)
2. Click the network SSID in the connection menu
3. In the EAP dialog, verify:
   • EAP Method: PEAP (most common for school/corporate)
   • Phase 2 Authentication: MSCHAPv2
   • CA Certificate: Select the correct certificate or choose Do not check for testing
   • Identity: Your full username (e.g., user@domain.com)
   • Password: Current password
4. Click Connect

Fix 3b — Install CA Certificate:

1. Obtain the CA certificate file (.pem or .crt) from your IT administrator
2. Go to chrome://settings/certificates
3. Under Authorities, click Import
4. Select the certificate file and check Trust this certificate for identifying websites
5. Reconnect to the enterprise network, selecting this CA certificate in the EAP dialog

Step 4: Fix Chromebook Won't Connect After Power Wash

A power wash (factory reset) erases all saved WiFi profiles, user certificates, and network policies. After a power wash:

1. During the OOBE (Out-of-Box Experience) setup, if the Chromebook fails to connect, try a mobile hotspot first to complete initial enrollment.
2. For enterprise-managed Chromebooks: The device must re-enroll via chrome://enterprise-enrollment before network policies (including auto-provisioned WiFi) are re-applied.
3. Re-import any user certificates needed for EAP (see Step 3b).
4. If DNS resolution fails after reconnecting, go to Settings > Network > [Your WiFi] > Network and set DNS servers manually to 8.8.8.8 and 8.8.4.4.

Step 5: Fix "Out of Range" or "No Networks Found" Errors

If your Chromebook shows Not connected — out of range while other devices see the network:

5a. Toggle WiFi off and on:

• Click system clock > Click WiFi toggle off > Wait 10 seconds > Toggle back on

5b. Check for 5GHz band incompatibility: Some older Chromebook WiFi adapters (especially on budget HP and Lenovo models) have poor 5GHz sensitivity. Log into your router admin panel (usually 192.168.1.1 or 192.168.0.1) and:

• Enable the 2.4GHz band if only 5GHz is broadcasting
• Enable Band Steering so the Chromebook auto-selects the stronger band
• Change the WiFi channel on 2.4GHz to channels 1, 6, or 11 to reduce interference

5c. Reset Chrome OS network stack via crosh: Press Ctrl+Alt+T to open crosh, then run the commands in the code_block section below.

Step 6: Model-Specific Fixes

HP Chromebooks (HP Chromebook 14, x360): HP Chromebooks using the Realtek RTL8822CE WiFi chip have a known issue where the adapter enters a low-power state and fails to re-associate. Go to chrome://flags and search for WiFi Power Save Mode. If available, set it to Disabled. Also check for pending Chrome OS updates via chrome://os-settings/help.

Lenovo Chromebooks (Flex 5, Duet, IdeaPad): Lenovo Chromebooks have reported issues after Chrome OS version 114+ with certain Intel WiFi 6 adapters dropping 5GHz connections. Workaround: force the router to use 80MHz channel width instead of 160MHz, and ensure the router firmware is up to date.

Acer Chromebooks (Spin 713, Chromebook 315): Acer models are frequently affected by DHCP timeout failures on networks with short lease times. Fix: In chrome://os-settings, navigate to Network > [Your WiFi] > Network tab and assign a static IP within your subnet (e.g., 192.168.1.150) with your router's gateway (e.g., 192.168.1.1) and subnet mask 255.255.255.0.

Step 7: Advanced — Check Chrome OS WiFi Logs

Navigate to chrome://device-log and filter by wifi to see raw connection event logs. Look for:

• supplicant: WPA: 4-way handshake failed → Wrong password or TKIP/AES mismatch
• dhcpcd: timed out → DHCP server not responding, try static IP
• wpa_supplicant: CTRL-EVENT-ASSOC-REJECT → AP is rejecting association, check MAC filtering on router
• nl80211: connect failed: -110 → Connection timeout, signal too weak or router overloaded

For persistent issues, enable verbose WiFi logging: go to chrome://net-internals/#chromeos and click Store Debug Logs, then Send feedback with the log attached.

Step 8: Last Resort — Powerwash and Re-enrollment

If all steps fail, perform a power wash:

1. Go to chrome://os-settings/reset
2. Click Reset, then confirm
3. After reboot, connect via mobile hotspot first
4. For managed devices, re-enroll at chrome://enterprise-enrollment
5. Re-apply all certificates and network configurations

Before power washing, ensure you have backed up any local files to Google Drive, as all local data is permanently deleted.