Why Is My Mac Not Connecting 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 on the network works fine. The good news is that most Mac Wi-Fi problems fall into a handful of well-understood categories, and working through them systematically usually turns up the culprit.

What's Actually Happening When Your Mac Won't Connect

Your Mac connects to Wi-Fi through a wireless network adapter (built into every modern Mac) that communicates with your router using one of several Wi-Fi standards — most commonly Wi-Fi 5 (802.11ac) or Wi-Fi 6 (802.11ax) on newer hardware. When something breaks down in that chain — the adapter, the router, the software managing the connection, or the network credentials — your Mac either can't connect at all or connects without internet access.

These are meaningfully different problems, and the fix depends on which one you're dealing with.

The Most Common Reasons a Mac Won't Connect to Wi-Fi

1. Incorrect or Outdated Network Credentials

If your router password recently changed or your Mac saved the wrong password, it will repeatedly fail to authenticate. macOS stores Wi-Fi passwords in the Keychain, and occasionally a corrupted or outdated entry causes connection loops even when you're entering the correct password.

What to try: Go to System Settings → Wi-Fi, click the network name, and select "Forget This Network." Reconnect from scratch and enter the password manually.

2. IP Address Conflicts or DHCP Failures

Your Mac needs a valid IP address to communicate on a network. This is typically assigned automatically by your router via DHCP. If the router fails to assign one — or assigns an address already in use by another device — your Mac may show as "connected" but with no actual internet access.

You'll often see a self-assigned IP address warning (usually starting with 169.254), which is macOS telling you it couldn't get a proper address from the router.

What to try: Go to System Settings → Wi-Fi → Details → TCP/IP and click "Renew DHCP Lease."

3. DNS Issues

Even with a valid IP address, if your Mac can't resolve domain names through DNS (Domain Name System), websites won't load. The connection looks fine, but nothing works. This is a common source of confusion because the Wi-Fi icon shows full strength while the browser reports errors.

What to try: Switching your DNS servers to a public alternative like 8.8.8.8 (Google) or 1.1.1.1 (Cloudflare) under System Settings → Wi-Fi → Details → DNS often resolves this quickly.

4. macOS Software or Network Configuration Bugs 🔧

macOS manages Wi-Fi through a combination of system processes and preference files. These can occasionally become corrupted, especially after:

  • A macOS update
  • Waking from sleep repeatedly
  • Switching between multiple networks frequently

Resetting the network configuration by removing and recreating network service entries, or clearing specific network preference files, can resolve persistent issues that aren't explained by hardware or router problems.

5. Router-Side Problems

Sometimes the issue has nothing to do with your Mac. Routers need occasional restarts, and older routers can struggle with modern Wi-Fi standards or frequency bands. Most modern routers broadcast on both 2.4 GHz and 5 GHz bands — your Mac may be trying to connect to a band it's having trouble with, or that the router is mismanaging.

What to try: Restart the router by unplugging it for 30 seconds. If you have a dual-band router, try manually connecting to the 2.4 GHz network to test whether the 5 GHz band is the issue.

6. Wi-Fi Hardware or Driver Problems

On rare occasions, the Mac's wireless adapter itself is the problem — either due to a hardware fault or a driver conflict introduced by a system update. macOS includes built-in wireless diagnostics (hold Option and click the Wi-Fi icon in the menu bar, then select "Open Wireless Diagnostics") that can identify hardware-level issues and capture detailed logs.

Variables That Change the Troubleshooting Path

FactorWhy It Matters
macOS versionOlder versions may lack support for newer Wi-Fi standards; some updates introduce new bugs
Mac model and ageOlder Macs may not support Wi-Fi 6; some hardware has known adapter issues
Router brand and firmwareSome routers have known compatibility quirks with macOS
Network typeHome networks, public Wi-Fi, and enterprise networks with captive portals each behave differently
VPN or firewall softwareThese can intercept or block network traffic, mimicking a connectivity problem

Wired vs. Wireless as a Diagnostic Step 🔍

One of the fastest ways to isolate the problem: plug your Mac directly into the router using an Ethernet cable (with a USB-C adapter if needed). If wired internet works but Wi-Fi doesn't, the problem is specific to the wireless connection — either on your Mac or your router. If neither works, the issue is likely upstream with your ISP or modem.

What "Connected But No Internet" Usually Means

This specific state — where macOS shows Wi-Fi connected but the internet doesn't work — almost always points to one of three things:

  • A DHCP failure (no valid IP address)
  • A DNS failure (can't resolve domain names)
  • A router or ISP outage affecting actual internet delivery

The Wi-Fi connection itself being functional doesn't mean the full network path is working. These are separate layers, and diagnosing which one is broken changes the fix significantly.

How Severity and Frequency Shape the Approach

A one-time connection drop after a software update is a different problem from a Mac that can never maintain a stable Wi-Fi connection. Similarly, a Mac that works fine on home networks but fails at coffee shops or hotels is pointing toward a specific network type — often captive portal handling or network security settings — rather than a fundamental hardware problem.

How long the issue has been happening, whether it affects all networks or just one, and whether other devices on the same network work normally are the three questions that most quickly narrow down where the fault actually lives. The answers to those questions, specific to your setup, are what determine which fix applies.