WiFi-Network Issue After Installing Updates, When I turn my mac on from sleep. Help..

I am having the same issue. Just installed updates a few days ago (Lion) and now when I come out of a sleep WIFI takes forever to connect. My system did not do this before the updates.

I'm very angry about this. This has been ongoing for quite a while, and the past several point updates (10.7.1 and 10.7.2 haven't fixed it.) I'm on 10.7.2 and still having this problem 100% of the time when I wake my 15" 2010 MacBook Pro from sleep by opening the lid. Even thought it's connected to the same network (Airport Express, fully updated) when I close and open it, WIFI does not reconnect, and I have to manually turn it off and on again before it will work.

I'm not the only angry one about this though. Do a search on the Apple Communities forums for "macbook pro lion wifi sleep" to see many other users with the same problem.

Hi,

same Problem with my MacBook Pro after Updates. WiFi symbol shows network, but there is no connection. I have to change Network Settings and wait for about one minute. After this everything works. Apple: Please find a solution! Fast!

I posted here a few days after the original update caused this issue and it was fixed with the next update (10.7.2). I didn't do anything on my end, just waited for apple to fix it and it worked. I wanted to add back to this post to verify that the fix is working for some people. Sorry your Mac is still not working.

I had exactly the same problem as you describe, sometimes it did automatically reconnect and very often it drops my wifi connection. None of the software patches from Apple seemed to fix the issue either.

For a complete separate reason i changed so that you have to enter your password when waking up from sleep mode, and for some reason that made my wifi rock solid again, both from wake up and no more random drops..

That opion should btw be turned on by default.

So that could be worth trying for you. You change that setting in Users & Groups, Automatic login = Off.

I also had the exact same problem. Just upgraded to 10.7.2 and it fixed it for me.