by Marcus Reed Updated Apr 24, 2026
You can see the WiFi network in your list, you tap connect, enter the password, and... nothing. The connection spins, fails, or shows "Unable to connect." This is different from not seeing any networks at all—here the network is visible, but your device refuses to join it. The causes range from simple password typos to more complex authentication and configuration issues.
This guide walks you through every reason a device might fail to connect to a visible WiFi network and provides targeted fixes for each scenario.
| Error Message / Behavior | Most Likely Cause | Fix |
|---|---|---|
| "Incorrect password" or "Wrong password" | Password is wrong or has a typo | Verify password → Fix 1 |
| "Unable to connect" or "Cannot join" | Corrupted network profile | Forget & reconnect → Fix 2 |
| "Authentication error" | Security type mismatch | Check WPA settings → Fix 4 |
| "Obtaining IP address..." forever | DHCP pool full or DHCP disabled | Check router DHCP → Fix 5 |
| Connects briefly then drops | IP conflict or MAC filtering | Check conflicts → Fix 6 |
| "Limited connectivity" or "No internet" | Connected but no internet | See WiFi connected no internet guide |
This is the #1 cause of connection failures. WiFi passwords are case-sensitive. Common mistakes:
To verify the correct password: find your WiFi password from a device that is already connected, or check the router admin panel.
Saved network profiles can become corrupted, especially after password changes or router replacements.
Then find the network again and enter the password fresh.
Simple but effective. Restart in this order:
If your router uses WPA3 but your device only supports WPA2, the connection will fail. Log in to your router and check the wireless security mode:
Also check that the wireless mode is set to Mixed or Auto (not "AC only" or "AX only") so devices with older WiFi chips can connect.
When your device connects to WiFi, the router assigns it an IP address via DHCP. If DHCP is disabled or the address pool is exhausted, your device gets stuck at "Obtaining IP address."
Log in to your router and verify:
If your router has MAC filtering enabled in whitelist mode, only pre-approved devices can connect. New devices will be silently rejected.
Log in to your router → look for Access Control or MAC Filtering. Either add your device's MAC address to the allowed list or disable the filter.
If DHCP is causing issues, bypass it entirely by assigning a static IP on your device:
netsh interface ip set address name="Wi-Fi" static 192.168.1.200 255.255.255.0 192.168.1.1
netsh interface ip set dns name="Wi-Fi" static 1.1.1.1Settings → WiFi → (i) → Configure IP → Manual → enter IP Address, Subnet Mask, and Router.
Outdated drivers or operating systems may lack support for modern WiFi security protocols or have bugs that prevent connection.
If nothing else works, reset all network settings to factory defaults:
Pro Tip: If a specific device consistently cannot connect while others can, try connecting it to a different WiFi network (like a phone hotspot). If it connects successfully, the problem is specific to your router's configuration. If it fails everywhere, the device's WiFi hardware may be faulty.
Single-device failures are caused by device-specific issues: corrupted network profile, outdated driver, incompatible security settings, or MAC filtering. Forget the network, update drivers, and try reconnecting.
Windows WiFi drivers are more prone to bugs than mobile OS WiFi implementations. Update the WiFi driver from the manufacturer's website (not just Windows Update). Also check that power management is not disabling the adapter (Device Manager → WiFi adapter → Properties → Power Management).
Your device still has the old password saved. Forget the network and reconnect with the new password. This is required on every device after a password change.
It means the password is wrong, the security type does not match, or the network profile is corrupted. Forget the network, verify the password is correct (check capitalization and special characters), and try connecting again.
Yes. Routers have a maximum client limit (typically 32–64 for consumer models). If the limit is reached, new devices are rejected. Also, if the DHCP pool is exhausted, no IP addresses are available. Check connected devices and remove any you do not need.
Try 5 GHz first for faster speeds and less interference. If it fails, try 2.4 GHz which has broader compatibility, especially with older devices. If your router uses band steering (same name for both), manually connect to the specific band by temporarily giving them separate names to troubleshoot.
 |
 |
 |
 |
About Marcus Reed
Marcus Reed is a network technician and technical writer who has configured and troubleshot routers and modems across thousands of home and small business installations for major ISPs including Comcast, AT&T, and Spectrum. That field experience across different hardware, firmware versions, and ISP environments gives him a practical command of what goes wrong and why. At RouterHax, he covers brand-specific router setup guides, ISP modem compatibility, and step-by-step troubleshooting tutorials.
Promotion for FREE Gifts. Moreover, Free Items here. Disable Ad Blocker to get them all.
Once done, hit any button as below
|
|
|
|
