My MacBook Pro Airport Connection Problem And Solution
Out of the middle of nowhere today my MacBook Pro wouldn't reconnect to my WiFi connection. This happened after I awoke the computer from sleep. It took a restart to get it working again. A few hours later the same thing happened when I woke the computer up again, but this time it wasn't fixed after a restart. I connected to my Linksys wrt54g wireless router with a manual IP address and snooped around. I ended up clearing the DHCP clients table and then trying to reconnect with DHCP. The router assigned my computer a new IP address in the clients table, but the computer itself didn't get the address. This seemed kinda strange.
After a bit of reading on the internet it seems that there are quite a few people who's Mac's won't reconnect their WiFi after sleeping. I attempted some of the most common fixes.
- Turning AirPort on and off
- Reconnecting to the access point
- Deleting the following files
Whenever I would put the computer to sleep it would loose its connection with the access point. However, unlike before, I could reconnect by turning AirPort off and then back on again. This is less than optimal though. It was really a pain in the butt to do all the time. Especially since I have the computer set to go to sleep after 5 minutes of inactivity.
I set out to eliminate this problem. I must have created a new 'Location' in the Network System Preferences when I first got my computer before I knew what I was doing. So I deleted that. Then I clicked the options button and set 'Keep looking for recent networks' when a preferred network is not found. Next, I removed all the 'Preferred Networks'. Followed by opening the Keychain Access application and removing all keys related to those preferred networks.
After all these changes my MBP now reconnects upon waking up from sleep again. It took me a few hours to figure out what was going on and find a fix for it. I can't say for sure exactly what the ended up being the solution since I was trying multiple things. I do know however, that one of the things listed above took care of the problem. At least now if it happens again I'll be able to hopefully fix the problem quickly!