Restart your MacBook and power-cycle your router first. This single move clears temporary network glitches and forces a fresh DHCP lease, which resolves most Wi-Fi dropouts without any further steps. If the connection still fails after that, work through the checklist below in order: settings first, then diagnostics, then hardware. If you are also seeing signs of drive failure, stop all disk writes immediately and back up what you can before troubleshooting further.
TL;DR:
- A self assigned address beginning with 169.254 points to a failed DHCP handshake; renew the lease, then recreate the network service if needed.
- If the Mac connects on one network but not another, test its private address and IP tracking settings before suspecting hardware.
- Apple Diagnostics hardware error codes make further software resets unlikely to help; repeated codes or physical damage warrant professional inspection before repair attempts.
- When other devices also disconnect, investigate the router or ISP; if only the Mac fails, test a phone hotspot to isolate the source.
- If drive corruption appears alongside connectivity trouble, stop disk writes, back up what you can, and seek professional diagnostics before troubleshooting further.
Before touching settings menus or running diagnostics, rule out the simple causes. These steps take a few minutes and fix a large share of Wi-Fi complaints on their own.
If another device also loses connection, the router or ISP is the likely cause. If only the Mac struggles while everything else connects fine, the issue sits with the Mac’s network settings or hardware, and the next sections will help you narrow that down.
Stale saved networks and leftover IP information cause a lot of “connected but no internet” situations. Clearing that state usually gets you back online without any deeper repair.
These steps address the most common causes of a MacBook that shows a Wi-Fi signal but won’t load anything. When renewing the lease or recreating the service doesn’t change anything, the cause is likely a setting elsewhere on the Mac rather than the network itself, which the next section covers.
Apple’s privacy features and third-party security software sometimes block a connection that otherwise looks healthy. These settings are worth checking before assuming a hardware fault.
Pro Tip: If Wi-Fi works on one network but fails on another, test Private Wi-Fi Address and Private Relay settings first. That mismatch is one of the most common causes of network-specific failures.
When settings changes don’t help, a hardware-level reset or a diagnostic scan will tell you whether the problem is software or a failing component.
| Result | Likely cause | Next step |
|---|---|---|
| Wi-Fi works after NVRAM reset | Corrupted startup settings | No further action needed |
| Wireless Diagnostics flags excessive retries | Router channel conflict | Adjust router settings |
| Apple Diagnostics returns a Wi-Fi error code | Failing Wi-Fi module | Professional hardware check |
| No error, but Wi-Fi still fails | Software conflict or ISP issue | Continue troubleshooting |
A hardware error code from Apple Diagnostics indicates that further software resets are unlikely to help. At that point, back up your data if you can and avoid DIY repair attempts.
Sometimes the Mac is fine and the problem sits with the router, the ISP, or interference in the room. These checks rule out everything outside the Mac itself.
If the Mac connects fine elsewhere but struggles only at home, the router or ISP is the more likely source of the problem rather than the Mac itself.
Repeated hardware errors from Apple Diagnostics, or no change at all after every reset above, point to a failing Wi-Fi module or logic board component rather than a settings issue.
Since 2006, we’ve run free diagnostics on Mac hardware issues just like these, checking the Wi-Fi module, logic board, and related components before recommending any repair. Our no recovery, no charge policy applies to every data recovery case we take on, so you only pay when we actually get your files back.
Software checks come before hardware swaps, always. Replacing a Wi-Fi module or logic board component without ruling out a setting or a corrupted network configuration wastes money and time. Component-level diagnostics exist precisely so a lab can confirm a fault before opening the case. Local, same-day service also matters here: a mail-in shop adds days you don’t get back, while a nearby lab can test, diagnose, and often repair the same afternoon.
— Kaya
If you’ve worked through every step above and your MacBook still won’t hold a connection, the cause is almost certainly hardware, and that’s exactly the kind of case we handle daily. We offer free diagnostics and a no recovery, no charge policy on every data case, with same-day appointments available for Wi-Fi module and logic board repairs at our lab at 12041 Wilshire Blvd, Ste 26, between the 405 and Santa Monica, near UCLA and the Getty Center. We serve West LA, Santa Monica, Beverly Hills, Brentwood, Westwood, Venice, Hollywood, and Culver City.
Bring your MacBook, its power adapter, and your Apple ID credentials so we can test and reconnect your network once the repair is complete. Call us at 310-866-0828 to book a same-day slot, or start with our Mac repair service page to see what a full diagnostic check covers.
Restart the MacBook, power-cycle your router, then forget and rejoin the network to clear stale credentials. If the connection still fails, run Wireless Diagnostics to generate a report, and follow up with Apple Diagnostics if a hardware fault is suspected.
A sudden disconnect is usually caused by a corrupted network configuration, an expired DHCP lease, or a router firmware glitch rather than a hardware failure. Renewing the DHCP lease and power-cycling the router resolves most sudden drops within minutes.
Check whether Wi-Fi shows as connected but pages won’t load, which often points to a DNS issue rather than a lost connection. Testing a public DNS resolver like 8.8.8.8 and clearing browser cache usually isolates whether the problem is network-level or browser-specific.
This typically means the Mac has a valid Wi-Fi link but no working IP address or DNS path, often shown by a self-assigned address starting with 169.254. Renewing the DHCP lease or recreating the Wi-Fi service, as outlined in Apple’s troubleshooting guide, usually restores a valid connection.
Compare Apple and independent MacBook keyboard repairs, learn when a top case needs replacement, and…
Cut power, avoid heat or rice, and protect files in the first 60 minutes after…
Free diagnostics in Los Angeles. Diagnostic‑first guidance on MacBook FlexGate repair, when microsoldering can save…
Run six quick checks to troubleshoot MagSafe not charging, or bring your Mac to West…
Run 4 quick checks to isolate power or mechanical causes of a beeping hard drive.…
Technician led triage for MacBook screen lines using screenshot, external display, and Apple Diagnostics. Free…