Why Won't My Mac Connect to Wi-Fi? Common Causes and How to Fix Them
Few things are more frustrating than a Mac that refuses to connect to Wi-Fi — especially when every other device in the room is online without issue. The good news is that Mac Wi-Fi problems almost always have a diagnosable cause. The less straightforward news is that the cause varies significantly depending on your Mac model, macOS version, router setup, and network environment.
Here's a clear breakdown of what's actually happening under the hood, and what factors determine which fix will work for you.
What Actually Happens When Your Mac Connects to Wi-Fi
When your Mac joins a wireless network, it goes through several steps: scanning for available networks, authenticating with the router (using a security protocol like WPA2 or WPA3), obtaining an IP address via DHCP, and establishing a working path to the internet through your router's gateway.
A failure at any of these stages produces the same visible symptom — no connection — but the fix is completely different depending on where the breakdown occurred.
The Most Common Reasons a Mac Won't Connect
1. The Network Itself Has a Problem
Before assuming your Mac is the issue, rule out the router and ISP. If your phone or another device can't connect either, the problem is upstream — not your Mac. Restart your router and modem (unplug for 30 seconds, then plug back in) before going further.
2. IP Address Conflicts or DHCP Failures
Your Mac requests an IP address automatically when joining a network. If that process fails — because the router's DHCP lease table is full, the router glitched, or a conflict exists — your Mac may show as "connected" but have no actual internet access. You'll often see a self-assigned IP address (starting with 169.254) in System Settings → Wi-Fi → Details.
The fix here is usually renewing the DHCP lease or releasing and reassigning the IP manually.
3. Corrupted Network Preferences or Keychain Entries
macOS stores Wi-Fi passwords and network configurations in its Keychain and network preference files. If these become corrupted — after a macOS update, a hard shutdown, or disk errors — your Mac may attempt to join a network using bad credentials or malformed settings without telling you clearly what's wrong.
Deleting the saved network from your known networks list and rejoining from scratch often clears this up.
4. DNS Configuration Issues
Your Mac might be connected to the router but unable to resolve domain names — meaning websites don't load even though the connection technically exists. This looks like a Wi-Fi problem but is actually a DNS issue. Switching to a public DNS server (like 8.8.8.8 or 1.1.1.1) under System Settings → Wi-Fi → Details → DNS is a quick test.
5. Wi-Fi Hardware or Driver Issues 🔧
macOS manages Wi-Fi through a system called CoreWLAN, and the underlying driver occasionally gets into a bad state. Turning Wi-Fi off and back on, or creating a new Network Location under System Settings, can reset this without requiring a full restart.
In rare cases — particularly after major macOS upgrades — the wireless driver itself may have a bug that requires an Apple software update to fix.
6. Band and Channel Conflicts
Modern routers broadcast on both 2.4 GHz and 5 GHz bands. Some Macs (especially older models) may struggle to maintain a stable connection on 5 GHz if the router is set to a channel that overlaps with neighboring networks, or if the signal is strong enough to connect but too weak for stable use. Manually selecting a network band (if your router broadcasts them separately) can help identify whether band preference is a factor.
7. macOS Version Compatibility
Certain macOS releases have shipped with known Wi-Fi bugs — particularly around WPA3, 802.11ax (Wi-Fi 6) routers, and private Wi-Fi address features. Apple has historically addressed these in point releases. If your Mac updated recently and Wi-Fi suddenly broke, checking whether other users report the same issue on that specific macOS version is worth doing before assuming hardware failure.
Key Variables That Determine the Right Fix
| Variable | Why It Matters |
|---|---|
| macOS version | Known bugs exist in specific releases; fix methods vary by OS |
| Mac model and Wi-Fi chip | Older Intel Macs and newer Apple Silicon Macs handle drivers differently |
| Router brand and firmware | WPA3 compatibility and DHCP behavior differ by manufacturer |
| Network environment | Enterprise networks, captive portals, and VLANs add layers |
| IP assignment method | Static vs. DHCP setups fail in different ways |
| Security protocol | WPA2 vs. WPA3 compatibility isn't universal across all hardware |
A Practical Troubleshooting Order
- Confirm the problem is isolated to your Mac
- Restart the router and Mac
- Forget the network and rejoin
- Check for a self-assigned IP (and renew DHCP lease if found)
- Test with DNS manually set to 1.1.1.1
- Create a new Network Location and reconnect
- Check macOS release notes or forums for known Wi-Fi bugs on your version
When the Problem Is Deeper 🔍
If none of the above resolves the issue, the problem may sit at the hardware level — a failing Wi-Fi antenna, a logic board issue, or (in older MacBooks) a worn antenna cable. Apple Diagnostics (hold D at startup) can flag hardware-level wireless faults, though it won't catch every antenna issue.
The specific combination of your macOS version, router firmware, network security settings, and Mac hardware generation is what ultimately determines whether this is a five-minute fix or something that needs deeper investigation.