Lion - Wi-Fi doesn't automatically reconnect when reawakening after sleep

Try turning off the auto update feature on Time Machine.

Launch KeyChain application and delete entries corresponding to the problematic Wifi connection. Did the trick for me. I saw a bunch of other solutions, checking DHCP settings and Network settings. But turned out to be a KeyChain issue for me.

Didn't work for me...I'm only using MAC address filtering on my router so I have no keys associated with my wireless connection. WHERE THE HECK is the "auto update" selection in Time Machine that was mentioned? I don't see it anyplace!

Well, I called Apple today and the person I spoke to indicated that they knew nothing about the issue. They instead asked me to rest my PRAM & NVRAM and reset the SMC. I was unable to reset the SMC controller because I can't remove the battery...I reset the PRAM / NVRAM and the problem still exists.

I have an appointment with the local Apple store on Sunday AM (kinda busy on Saturday) so I hope to know more then as I can recreate this anytime I choose.

More later....

Does your computer require a password upon resuming from sleep?

If so - on average - how long does it take for you to type your password in? 5 seconds, 10?

I have seen this behaviour before on machines, and it only affected the machines where there was a significant delay between resuming from sleep and the authentication.

This is because while your comptuer is asleep / locked - so is the keychain.

If the wireless attempts to connect - while your machine is locked - its unable to access theh keychain - and thus authenticate the wireless. Usually turning the wireless off / on after logging in will reconnect the wireless, proving the user details in the keychain are correct.

If you don't have a password on resume try deleting the wireless connection from your computer completely - while the wireless is off and then save the settings. Then create the connection and turn your wireless back on. You could also try creating a new location and setting the wireless up inside that, making sure your in that location when you sleep.

If you have updated from Snow Leopard - have you repaired your permissions since the upgrade? or restarted your machine into Safe Mode? Have you tried to see if a new user account has the same issue?

While its not documented, and it means the reboot after safe mode takes longer to start then normal - Repairing the Permissions, Checking your disk doesn't have errors, and cleaning the caches out with a safe boot doesn't hurt and is usually a good thing to try if your having issues.

Apple article HT3964 tells you how to reset the SMC. For computers out of which you cannot take the battery, use the second option in the list headed: "Resetting the System Management Controller (SMC)

http://support.apple.com/kb/ht3964

I THINK IT IS FIXED!!!

As per instructions from Apple, I reset the SMC controller (for those of you with newer MBP's, look for the alternate instructions as we can not remove our batteries).

Do a search for the following for complete (easy) instructions:

Intel-based Macs: Resetting the System Management Controller (SMC)

(remember to leave the mag-safe power adapter connected to your laptop...only unplug the power adapter from the wall).

Good luck!!

I'm not sure if this issue is restricted to Lion or not, but it's definitely happening to me. I've got a Macbook Air and it consistently won't reconnect to the wireless network after waking from sleep. I've tried deleting and rebuilding the keychain, resetting PRAM, permissions and SMC and I've started it in safe mode. It still happens. The console shows the following when this occurs:

Marker - 31/07/2011 8:15:12 PM

Jul 31 20:15:46 joelmacair-2 kernel[0]: PM notification timeout (pid 4065, iTunes)

Jul 31 20:15:48 joelmacair-2 kernel[0]: en0: BSSID changed to c0:3f:0e:d2:92:da

Jul 31 20:15:48 joelmacair-2 kernel[0]: wlEvent: en0 en0 Link DOWN

Jul 31 20:15:48 joelmacair-2 kernel[0]: AirPort: Link Down on en0. Reason 8 (Disassociated because station leaving).

Jul 31 20:15:48 joelmacair-2 kernel[0]: vmnet: bridge-en0: interface en is going DOWN

Jul 31 20:15:49 joelmacair-2 kernel[0]: vmmon: powerStateDidChange flags=0x4 (state 2)

Jul 31 20:15:49 joelmacair-2 kernel[0]:

Jul 31 20:16:45 joelmacair-2 kernel[0]: Wake reason: EC.LidOpen (User)

Jul 31 20:16:45 joelmacair-2 kernel[0]: AppleMCP89TMS::powerGatingDown(0): Done

Jul 31 20:16:45 joelmacair-2 kernel[0]: vmmon: powerStateDidChange flags=0x82 (state 3)

Jul 31 20:16:45 joelmacair-2 kernel[0]: Previous Sleep Cause: 5

Jul 31 20:16:45 joelmacair-2 kernel[0]: en0: 802.11d country code set to 'X1'.

Jul 31 20:16:45 joelmacair-2 kernel[0]: en0: Supported channels 1 2 3 4 5 6 7 8 9 10 11 12 13 36 40 44 48 52 56 60 64 149 153 157 161 165

Jul 31 20:16:45 joelmacair-2 kernel[0]: vmnet: VMNetDisconnect called for port 0xffffff800eb80d00

Jul 31 20:16:45 joelmacair-2 kernel[0]: vmnet: Invalidating peer info for hub: 0, port: 0

Jul 31 20:16:45 joelmacair-2 kernel[0]: vmnet: bridge-en0: filter detached

Jul 31 20:16:45 joelmacair-2 kernel[0]: vmnet: bridge-en0: down

Jul 31 20:16:45 joelmacair-2 kernel[0]: vmnet: bridge-en0: detached

Jul 31 20:16:45 joelmacair-2 kernel[0]: vmnet: Freeing hub at 0xffffff8030cc0000.

Jul 31 20:16:46 joelmacair-2 kernel[0]: AppleUSBMultitouchDriver::checkStatus - received Status Packet, Payload 2: device was reinitialized

Jul 31 20:16:46 joelmacair-2 kernel[0]: EIR is supported.

Jul 31 20:16:46 joelmacair-2 kernel[0]: SSP is supported.

Jul 31 20:16:46 joelmacair-2 kernel[0]: Sound assertion "0 == fAudioEngineArray" failed in AppleHDADriver at line 3161 goto Exit

Jul 31 20:16:47: --- last message repeated 1 time ---

Jul 31 20:16:47 joelmacair-2 kernel[0]: [SendHCIRequestFormatted] ### ERROR: [0x0804] (Exit Sniff Mode) -- Send request failed (err = 0x000C (kBluetoothHCIErrorCommandDisallowed))

Jul 31 20:16:47 joelmacair-2 kernel[0]: ### ERROR: Exit sniff failed (probably already unsniffed) (err=c)

Anyone got any clues as to why this might be happening?

OK...I need to retract my previous post. It's NOT FIXED...

I'm not certain what the problem is but maybe if we get enough people calling Apple for support they'll pay attention to it. I'm going to recreate it and then call Apple later today...YOU SHOULD AS WELL!

Keep this thread updated...

Thanks

OK...just called Apple and was on the phone for 30 min with a great guy named Andrew. I now have a new case opened (Case# 236891865) and he took me thru a few things...none worked and the problem was recreated every time.

My next stop is my local Apple store (Valencia Town Center) where I'll see if they can shed any light on the issue.

More to follow.

IF YOU'RE HAVING THIS ISSUE...PLS CALL and have them log a ticket. Just don't wait for a patch.

Thanks

SW

You stated that you where using MAC address filtering, but that you where not using any sort of wireless encryption. Dubious security at best but it would rule out that possibility of incompatibility.

However, I will ask the questions anyway, what router are you using. What is your timeout settings for DHCP assigned addresses? Have you updated your router to it's most current firmware?

I only ask these questions because I am using a Linksys E3000 and since upgrading to Lion, I have had much better performance then before with my WiFi and the two Macs in the house that we running Lion.

As has been said many times before in many threads, there is lilely to be compatibility issues with some third party wireless routers. More so if they are based on draft or unfinished versions of the 802.11n standard.

I highly recommend to anyone having issues with WiFi to check with the manufacturer of your WiFi Access Point / router and see if there is an update for it.

If there was a major issue with WiFi in Lion, I assure you they would not have released it. They delayed the release of iOS 4 last year for a WiFi issue, so they have no problems delaying the release of something if it is broken.

I guess all I am trying to say is please don't just assume it is Lion and not something else in the chain.

Yes, I understand the only thing that has changed from your perspective is that you installed Lion. But, it may be that Lion is more secure or is more adversely affected by certain settings on a given WiFi network.

I actually have two (2) AP's in my home. one is a 5th Gen AirPort Extreme and the other is a Netgear WNR3500L.

YES, both appear to have the most current version of firmware.

As a CISSP, I agree that MAC filtering by itself is not the best way to do things but as you indicated, it does remove almot everyhting from the picture. Thus my choice....

As I indicated in my previous posts, the issue is easily recreated on a variety of AP's so that in itself would tend to rule out a single point of failure...the singular AP. No, I'm still betting it's LION....

Don't get me wrong, thanks for the suggestions and I'll be the first to admit I goofed something up.

Any other thoughts?

SW

@BoloMK33,

I bet you what is happening is some of your configuration files where messed during the install/upgrade. Here is how I would fix it.

Please note: You will have to reconfigure any network settings (WiFi preferred networks, VPN interfaces, Proxy settings, etc) in order to start from scratch.

1. Open a terminal and do cd /Library/Preferences/ and hit return

2. Next do open . and hit return

3. A finder window will open. Click on the SystemConfiguration folder move it to your Desktop. This gives you a backup copy incase you want to restore the plists in the SystemConfiguration folder.

4. Now delete the SystemPreferences folder that exists in /Library/Preferences. You will be prompted for your admin password to delete the folder.

5. Reboot your Mac.

6. When your Mac reboots, Lion will re-create the SystemConfiguration folder and your network prefs will be set to default values.

7. Connect to your WiFi network.

8. Try a Sleep/Wake test and see if you can reconnect.

If this fails, you can easily restore your Mac to the way it was before this experiment by just dragging the SystemConfiguration folder from your Desktop back to the /Library/Preferences folder and rebooting.

Let me know if this works.

Great idea...but sadly one that the Apple folks already tried. The following files were deleted (multiple times) and recreated (have I said today how I love the MAC OS...no way you could do this on a PC):

- preferences.plist

- networkinterfaces.plist

- com.apple.airport.preference.plist

Nope...problem remains...I leave for the Apple store in 15 min.

BTW...I hear that the machines in the Apple stores are all loaded from a disk image...so it's a fresh install and NOT an upgrade. THAT is what I'm pushing for...gimme a DVD w/ LION on it and let me do a virgin install...

More later....

Thanks everybody!

Ok,

Let's try this. Open a terminal again.

When you wake from sleep start a ping to www.apple.com. If the pings is successfull (assuming you get L2 connectivity, then an IP from your rotuer) but your Applications (Safari, Mail, iChat cannot connect) then this sounds like a stack issue and not a wireless issue.