Q: After Lion upgrade, having network issues after wake from sleep

Did anyone do a clean install?   This isn't a bug the manifests itself in upgrade installs only?

ctomer wrote:

 

Did anyone do a clean install?   This isn't a bug the manifests itself in upgrade installs only?

It's a bug carried over from Snow Leopard - only it happens more frequently with Lion ... And you can't clean install Lion because you have to install install Snow Leopard first.

You can clean install Lion. Hold CMD+R at restart, erase your drive and install.  I'm wondering because I'm tempted to do a re-install but won't bother if this problem still exists in clean installs.

BTW, I never had this problem in Snow Leopard.

Got a buddy who keeps hounding me about not having done a clean install.  Didn't do a clean install on either of  my Macs.  One works, the other doesn't. 

Curious, too, though whether clean installers are having any issues.

I did a clean install and it still didn't solve this problem.

Good info, thanks!

Yes dont mess up your system too badly trying to fix this. This is a bug with Lion itself.

The only fix will be an update from apple to address this.

Anyone bent on updating to Lion, I'd hold off for awhile. I wish I had...

Anyone in this thread who doesn't have VMWare fusion installed?

Anyone in this thread who doesn't have VMWare fusion installed?

I don't.

I don't.

I too am having the same problem after update to Lion. ( early 2008 MBP 17")

the Problem only exists with Static IP. If you use DHCP Internet after sleep works fine !

I am using DHCP Internet , but did not fix the problem. Thanks for your input. I did seem to fix the problem on the inital start up by changing the order of the networks so that my home network is at the bottom of the network list instead of the top. This did not fix the problem after wake from sleep though.

Definately not related to DHCP or Airport or Ethernet or time machine or your internet or clean installs. Trust me I've experienced this independent of any of those. The issue is reminicent of something you could get with viscocity vpn on SL, where certain apps would fail to resolve hostnames, whereas anything from terminal (i.e. ping) would work fine. There i know for a fact that it was an issue with the DNS subsystem and this seems to be very similar (though no 3rd party app is to blame here). Definately looks like a bug in the OS if i've ever seen one. And I've only had it after waking from sleep so far.

My workaround is to shutdown instead of sleeping until apple fixes this. Since lion saves all your windows etc. this is just really annoying. Hope this gets fixed soon.

Early 2009 13" MBP here btw.

My workaround is to simply toggle the wifi off and on from the menu bar.  You might find that easier than shutting down.