TL;DR
Your Android phone is stuck on "Authentication problem — Couldn't connect to Wi-Fi network". Other devices connect fine. Fastest fix: forget the network, reboot your router, reconnect. Still broken? Force a static IP or flip your router from WPA3 to WPA2. Every other scenario is covered below.
What's actually failing
The error fires during the 4-way handshake — the back-and-forth where Android and your router agree on an encryption key. That exchange breaks, and Android bails out with this message. The frustrating part: the same error covers at least six different root causes.
- Wrong password cached on the device (most common)
- Router stuck in a bad state after a firmware update or power cycle
- IP address conflict — your phone got assigned an IP already in use
- WPA3 compatibility issues on older Android builds or certain chipsets
- MAC address filtering blocking the device
- DHCP pool exhausted on the router
Fix 1: Forget and reconnect (do this first)
Cached credentials are the #1 culprit. Android holds onto the old password even after you change it on the router — and you'd never know.
- Go to Settings → Wi-Fi
- Long-press the network name → Forget network (or tap the gear icon → Forget)
- On Samsung: Settings → Connections → Wi-Fi → hold the SSID → Forget
- Reboot your router (pull the power, wait 30 seconds)
- Reconnect and type the password manually — don't paste it
Verify: The network should show "Connected" without the authentication error. Still showing "Obtaining IP address" after 10 seconds? Move to Fix 2.
Fix 2: Force a static IP
DHCP timeouts and IP conflicts are sneaky. Assigning a static IP sidesteps both — no negotiation, no conflict.
- Settings → Wi-Fi → tap the gear icon next to the network
- Tap Advanced (or "More")
- Change IP settings from DHCP to Static
- Set these values:
IP address: 192.168.1.200 (pick something outside your DHCP range)
Gateway: 192.168.1.1 (your router's IP)
Subnet mask: 255.255.255.0
DNS 1: 8.8.8.8
DNS 2: 8.8.4.4
Not sure what your router's DHCP range is? Check the router admin panel at 192.168.1.1 or 192.168.0.1. The Subnet Calculator on ToolCraft helps you find valid host addresses quickly — handy when you're juggling 10+ devices and want to avoid conflicts.
Verify: Forget and reconnect after setting the static IP. Open a browser and load any page — if it loads, you're done.
Fix 3: Switch WPA3 → WPA2 on the router
Android 10 and below has spotty WPA3 support. Some Snapdragon 660 and MediaTek Helio chipsets also choke on WPA3 transition mode, even on Android 11.
Log into your router admin panel and find the wireless security settings:
# Common router admin URLs
http://192.168.1.1
http://192.168.0.1
http://10.0.0.1
# On OpenWrt/DD-WRT via SSH:
uci show wireless | grep encryption
uci set wireless.default_radio0.encryption='psk2' # Force WPA2
uci commit && wifi restart
Change Security Mode from "WPA3" or "WPA2/WPA3 Mixed" to WPA2-PSK (AES). Save and reboot the router.
Verify: Try connecting from Android. Most devices clear the error at this step.
Fix 4: Reset network settings on Android
Multiple routers, old VPN configs, corporate Wi-Fi profiles — these accumulate. Eventually the network stack itself gets corrupted in ways the UI never exposes.
Settings → General Management → Reset → Reset network settings
# Samsung path ↑
Settings → System → Reset options → Reset Wi-Fi, mobile & Bluetooth
# Pixel / stock Android path ↑
This wipes all saved Wi-Fi passwords, Bluetooth pairings, and VPN configs. Write down your passwords before running it.
Verify: After the reset, reconnect fresh. Corrupted config files are gone — the OS now starts clean.
Fix 5: Check MAC address filtering
MAC filtering is easy to forget about — until it breaks things. Android 10+ randomizes the MAC address per network by default, so your device might be presenting a different MAC than what's whitelisted on the router.
# Check current MAC on Android:
Settings → About phone → Status → Wi-Fi MAC address
# Or via adb:
adb shell ip link show wlan0 | grep ether
# Output: link/ether aa:bb:cc:dd:ee:ff
To disable MAC randomization for this specific network:
- Settings → Wi-Fi → gear icon next to the network
- Privacy → change from "Use randomized MAC" to "Use device MAC"
Then add your device's real MAC to the router's whitelist.
Fix 6: ADB-level reset (advanced)
USB debugging enabled? You can reset the Wi-Fi subsystem without wiping the whole device.
# Connect device via USB, then:
adb shell svc wifi disable
adb shell svc wifi enable
# If still failing, clear wpa_supplicant state:
adb shell su -c 'rm /data/misc/wifi/wpa_supplicant.conf'
adb reboot
# On Android 11+, the config path changed:
adb shell su -c 'rm /data/vendor/wifi/wpa/wpa_supplicant.conf'
adb reboot
Deleting the config file needs root. The svc wifi toggle works without it.
Quick checklist
- Router's 2.4 GHz channel overlapping with neighbors? Switch to channel 1, 6, or 11
- DHCP lease pool full? Check connected devices in router admin — old leases pile up fast on busy networks
- Router firmware outdated? Update it — authentication bugs get patched regularly
- Trying to connect to 5 GHz with an older device? Android 6–7 phones sometimes drop 5 GHz bands entirely
- Enterprise network (WPA2-Enterprise / 802.1X)? A password isn't enough — you need a certificate installed
Prevention
Most of these problems trace back to two things: weak passwords and dynamic IPs. A router reset with a short, default password is a recipe for cache mismatches next time.
Use a strong, random Wi-Fi password — 20+ characters, mixed case, no dictionary words. The Password Generator on ToolCraft runs in-browser and sends nothing anywhere. Generate it, copy it, done.
For devices that matter (laptops, smart TVs, NAS boxes), give them static DHCP leases in the router rather than configuring static IPs on each device. One setting in the admin panel eliminates IP-conflict authentication failures across the board.