HT4628: Wi-Fi: How to troubleshoot Wi-Fi connectivity

Learn about Wi-Fi: How to troubleshoot Wi-Fi connectivity
iness

Q: Macbook Air does not connect automatically after sleep

Hi everyone.

 

I just got a brand new Macbook Air and have a really annoying issue:

it won't reconnect automatically to wi-fi networks in memory when coming back from sleep.

 

Been in touch with Apple Care.

Went through all the procedures: erasing all networks, adding them again, etc...

Nothing helped.

 

Any tips anyone?

I noticed there was a recent update for the exact same problem on iMac's.....

MacBook Air, Mac OS X (10.7.3)

Posted on Mar 9, 2012 8:41 AM

Close

Q: Macbook Air does not connect automatically after sleep

  • All replies
  • Helpful answers

  • by DaveHoulbrooke,

    DaveHoulbrooke DaveHoulbrooke Mar 15, 2012 2:46 AM in response to iness
    Level 1 (0 points)
    Mar 15, 2012 2:46 AM in response to iness

    I have the exact same thing.

     

    Macbook Air wakes from sleep, and doesn't automatically connect to local preferred wifi networks until I hover over the wifi icon and it realises they exist.

  • by joshuafromauburn,

    joshuafromauburn joshuafromauburn Apr 16, 2012 6:36 PM in response to iness
    Level 1 (5 points)
    Apr 16, 2012 6:36 PM in response to iness

    It may be a problem with the connection information stored in your network profile.

    1. Go to System Preferences > Network.
    2. Click the Wi-Fi connection.
    3. Click the Advanced... button on the bottom right.
    4. Click the Wi-Fi tab.
    5. Under Preferred Networks, select your wireless network.
    6. Click the - (delete) button.
    7. Turn off your Wi-Fi connection.
    8. Turn it back on.
    9. Select and login to your wireless network. This will re-save your connection under Preferred Networks.
    10. Close your laptop and reopen it to test whether it worked.
  • by DaveHoulbrooke,

    DaveHoulbrooke DaveHoulbrooke Apr 17, 2012 6:50 AM in response to joshuafromauburn
    Level 1 (0 points)
    Apr 17, 2012 6:50 AM in response to joshuafromauburn

    Fixed now! Thanks.

  • by iness,

    iness iness Apr 17, 2012 7:45 AM in response to joshuafromauburn
    Level 1 (0 points)
    Apr 17, 2012 7:45 AM in response to joshuafromauburn

    Hi. Thanks for your reply.

     

    Unfortunatey I already tried this - more than once - and the problem persists (with several networks)....

  • by Neil Cox,

    Neil Cox Neil Cox May 2, 2012 5:15 PM in response to iness
    Level 1 (5 points)
    May 2, 2012 5:15 PM in response to iness

    I just tried the procedure @joshuafromauburn suggested and it solved my wifi connectivity issue. The weird part is, I know I tried that same thing about a week ago. Not sure what I did different.

  • by c1v,

    c1v c1v Aug 9, 2012 8:23 PM in response to joshuafromauburn
    Level 1 (0 points)
    Aug 9, 2012 8:23 PM in response to joshuafromauburn

    Instead of closing the lid try restarting. Thanks for the tip! This worked for me.

  • by Ry4n3s,

    Ry4n3s Ry4n3s Jun 12, 2013 11:16 PM in response to joshuafromauburn
    Level 1 (0 points)
    Jun 12, 2013 11:16 PM in response to joshuafromauburn

    It worked. been bugging me for awhile! thank you

  • by sosinovitch,

    sosinovitch sosinovitch Jun 19, 2014 8:10 PM in response to joshuafromauburn
    Level 1 (0 points)
    Jun 19, 2014 8:10 PM in response to joshuafromauburn

    I had a similar issue, and what worked were the following steps recommended by joshuafromauburn :

     

    1. Under Preferred Networks, select your wireless network.
    2. Click the - (delete) button.

     

    My problem was caused by the fact I changed my encryption from WPA/WPA2 to WPA2 Personal. I failed to remove my old wireless network SSID name from the preferred networks list, and until I did so, reconnect, then bring my new SSID name with the new configuration to the top of the list, it wouldn't connect automatically. My old configuration look like this: SSID name WPA/WPA2 Personal. My new configuration looks like this: SSID name WPA2 Personal. I thought the first configuration would work with either WPA or WPA2 ... so that is why I didn't detect this issue until now.