Mac Not Connecting to Wi-Fi: How to Fix It

Router and modem issues are the most frequent culprits. A router that has been running for weeks without a restart can develop memory leaks, channel congestion, or firmware glitches that prevent new connections. Other devices on the same network may continue working because they established their connections before the problem appeared.

DNS problems prevent your Mac from resolving domain names even when the Wi-Fi connection itself is technically active. You may see the Wi-Fi icon in the menu bar with no exclamation mark, yet Safari reports that it cannot find the server. This happens when the DNS servers provided by your ISP become unresponsive or return incorrect results.

Corrupted network preference files stored in /Library/Preferences/SystemConfiguration/ can cause persistent connection failures. These plist files contain DHCP settings, saved network passwords, and interface configurations. When they become corrupted, macOS may fail to negotiate a proper connection even though the Wi-Fi hardware is functioning normally.

macOS updates occasionally introduce Wi-Fi regressions. Apple's release notes sometimes acknowledge connectivity bugs that appear after a major update. Hardware failure, though uncommon, is also possible. The Wi-Fi antenna or the wireless chipset can degrade over time, especially on older MacBooks that have sustained physical impacts.

Toggling Wi-Fi off and on forces macOS to release the current wireless interface state and reinitialize it. Click the Wi-Fi icon in the menu bar, turn it off, wait ten seconds, then turn it back on. This clears temporary negotiation errors without requiring a full system restart.

Restarting your Mac clears memory, resets all network interfaces, and forces macOS to reload its networking stack from scratch. Persistent connection problems caused by background service crashes or memory corruption often disappear after a clean restart.

Restarting your router is equally important. Unplug the router from power, wait 30 seconds, then plug it back in. This forces the router to clear its DHCP lease table, release congested channels, and reload its firmware. If you have a separate modem, restart that device first, wait for it to fully connect, then restart the router.

Forgetting the network removes the saved credentials and configuration for that specific SSID. Open System Settings > Wi-Fi, find the network in the list, click the details button, and select "Forget This Network." Then rejoin by selecting the network and entering the password fresh. This eliminates issues caused by stale or corrupted saved credentials.

macOS does not have a single "Reset Network Settings" button like iOS. Instead, you need to manually remove the preference files that store network configuration. Open Finder, press Cmd+Shift+G, and navigate to /Library/Preferences/SystemConfiguration/. Back up the folder contents first, then delete these files: com.apple.airport.preferences.plist, com.apple.network.identification.plist, NetworkInterfaces.plist, and preferences.plist. Restart your Mac afterward to let macOS regenerate these files with default values.

Renewing the DHCP lease forces your Mac to request a fresh IP address from the router. Open System Settings > Wi-Fi, click the details button next to your connected network, select the TCP/IP tab, and click "Renew DHCP Lease." This resolves IP address conflicts where two devices on the same network were assigned the same address.

Changing your DNS servers to Google's public DNS (8.8.8.8 and 8.8.4.4) or Cloudflare's DNS (1.1.1.1) bypasses unreliable ISP name servers. In the same network details panel, select the DNS tab and add 8.8.8.8 as the primary server. This ensures domain name resolution works even when your ISP's DNS infrastructure is experiencing problems.

VPN applications modify your Mac's routing tables and DNS configuration. When a VPN connection fails or disconnects improperly, these modifications can persist, leaving your network stack in a broken state. The Mac may appear connected to Wi-Fi but cannot reach any websites because traffic is being routed to a VPN tunnel that no longer exists. Fully quitting the VPN application and restarting usually clears this.

Third-party firewall software such as Little Snitch or LuLu can block outgoing connections if a rule accidentally denies traffic for a system networking service. Check your firewall rules to ensure that mDNSResponder, configd, and other macOS networking processes are allowed through. Temporarily disabling the firewall is a quick way to determine whether it is the source of the problem.

Proxy configurations, whether set manually or by a corporate profile, redirect all network traffic through a proxy server. If that server is unreachable, no traffic flows. Check System Settings > Wi-Fi > network details > Proxies and ensure no proxy is configured unless you specifically need one. Third-party network utilities that modify DNS or install kernel extensions can also interfere with standard Wi-Fi behavior and should be temporarily uninstalled during troubleshooting.

Wi-Fi problems are often intermittent. Your connection may drop for a few seconds, reconnect, and drop again. Without continuous monitoring, these brief outages are difficult to confirm because the Wi-Fi icon in the menu bar may still show a full signal. MoniThor tracks real-time upload and download throughput, so a drop to zero bytes per second is immediately visible.

The SSID display confirms which network your Mac is actually connected to. In environments with multiple access points or similarly named networks, your Mac may silently roam to a weaker access point. Seeing the current SSID at a glance helps you verify that your Mac is connected to the correct network.

Local and public IP addresses shown in the menu bar provide instant confirmation that your Mac received a valid DHCP lease and has internet connectivity. A missing public IP indicates that while your Mac is connected to the router, the router itself may not have an active internet connection. This distinction saves time by pointing you toward the right device to troubleshoot.

A failed Wi-Fi hardware module is the most definitive reason to contact Apple. If your Mac cannot detect any Wi-Fi networks at all, even after resetting network settings and restarting in Safe Mode, the wireless chipset or antenna may be physically damaged. This is especially common on older MacBooks that have been dropped or exposed to liquid.

If you have completed every software troubleshooting step (toggling Wi-Fi, restarting, deleting preference files, renewing DHCP, changing DNS, removing third-party network software) and the problem persists, a deeper system issue likely requires Apple's diagnostic tools. Apple technicians can run hardware tests that are not available to end users.

macOS includes a built-in Wireless Diagnostics tool. Hold the Option key and click the Wi-Fi icon in the menu bar, then select "Open Wireless Diagnostics." This utility runs a series of tests on your Wi-Fi environment, checking for signal interference, channel congestion, and hardware errors. If the tool reports a hardware fault, the next step is an Apple Store appointment or an authorized service provider visit.