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

Same issue here.  If I down the interface (sudo ifconfig en0 down) then up it again, things are fine immediately.

This is on a 2008 mac pro, wired network.   Another interesting bit - I can resolve dns queries, and even telnet to port 80 using DNS when it's broken in the apps (safari, firefox etc).

Odd one.....

For Ko...bizarre but you are right, two units here had the same problem; removed the DVD form the optical drive and the problem vanished....time machine was not connected to one of the device.

Thanks for your help

At first i thought the problem was solved by removing and reinstalling wifi from the network center but actually the Problem was solved when i removed a dvd from the drive... Strange but true

For what it's worth, it's beginning to look like there may be an issue where by an in-progress Time Machine backup or a DVD in the drive may cause this issue.

I'm leaning towards a priority issue whereby the code responsible for reestablishing the network connection is being prevented from running in those circumstances.

I finally have been able to reproduce this, sort of, due to an in-progress Time Machine backup and the network connection was finally restored as soon as I stopped the in-progress Time Machine backup from the Time Machine menu.

Sorry but I do not see this as the problem. I do not have to an "in-progress" Time Machine backup for the problem to be there. It arises every time the Time Capsule is switched on, whether it's backing up, trying to backup or doing nothing. Just the mere fact of the Time Capsule being connected and powered is sufficient and the WiFi network via Airport Express is knackered. Disconnect power from the Time Capsule and it's fine. Except of course I can never put the iMac to sleep unless I unplug all USB and FireWire drives.

Anyone found a solution to the calendar problem yet? I have deleted and re-installed countless times. It does not sync. It does though on my MacBook, iPad & iPhone.

This too is happening to me. I use a wired connection with a static IP and I have found that in a terminal I can ping my lan's as well as any wan address. I can also resolve any DNS using terminal. I can type the IP address into Safari and it goes to the website and it works perfectly but Safari can not resolve the name itself. Pretty fricking weird. I am going to keep dinking with this to see if there is a simple solution.

richardfromdurham wrote:

 

Sorry but I do not see this as the problem. I do not have to an "in-progress" Time Machine backup for the problem to be there. It arises every time the Time Capsule is switched on, whether it's backing up, trying to backup or doing nothing. Just the mere fact of the Time Capsule being connected and powered is sufficient and the WiFi network via Airport Express is knackered. Disconnect power from the Time Capsule and it's fine. Except of course I can never put the iMac to sleep unless I unplug all USB and FireWire drives.

 

Anyone found a solution to the calendar problem yet? I have deleted and re-installed countless times. It does not sync. It does though on my MacBook, iPad & iPhone.

Please create separate new threads for each of your issues, as they are different from this one and are worthy of investigation.

For example, your Time Capsule issue sounds like a configuration problem more than anything else.

One more data-point and workaround:

Config: Early 2009 Mac Mini (2GHz, 4GB), upgraded to Lion from SL. Using wired ethernet with fixed IP (airport is off), Time Machine backups to USB HD. Automatic sleep disabled, so only via Apple menu (or key combo if I remember). No disk in optical drive.

Symptoms: Since Lion upgrade, on wake from sleep Safari, Mail, etc have no internet connectivity (some complain about DNS issues rather than no connection), but terminal apps work fine. Doesn't happen every time, but certainly more than half the time. never had this problem under Snow Leopard.

Workaround: Restart mDNSResponder, this immediately fixes the problem for me every time. I'm doing this by running sudo killall mDNSResponder in a terminal (Applications > Utilities > Terminal), but there's probably a cleaner way.

Thoughts: Doesn't appear to be specific to Airport, DHCP or optical disks. Could be Time Machine related, but if that's running for 1-2 minutes once an hour, it seems highly unlikely that half the times I told the Mac to sleep since I upgraded to Lion happened to be whilst a backup was running...

I found this:

http://www.makingitscale.com/2011/fix-for-broken-search-domain-resolution-in-osx -lion.html

Which makes reference to mDNSResponder.

Here they added a parameter -AlwaysAppendSearchDomains to the mDNSResponder.plist file under the ProgramArguments block, unloaded the mDNSResponder.plist and then reloaded it.

I have not had the time to try it yet, if anyone else does, let me know if it works. Don't forget to do this to a copy of the mDNSResponder.plist file.

Also this from the Terminal:

How To Fix DNS Search Domains in OS X Lion

==========================================

Edit the mDNSResponder Config

------------------------------

sudo vim /System/Library/LaunchDaemons/com.apple.mDNSResponder.plist

Add <string>-AlwaysAppendSearchDomains</string> below <string>-launchd</string>.

Reload mDNSResponder

--------------------

sudo launchctl unload /System/Library/LaunchDaemons/com.apple.mDNSResponder.plist

sudo launchctl load -F  /System/Library/LaunchDaemons/com.apple.mDNSResponder.plist

This didn't work for me - maybe it's my iMac and some old settings from the upgrade. Anyone else have any luck?

I tried running the command in the Terminal using Vim and noticed that my com.apple.mDNSResponder.plist had not changed.

I ended up using a plist editor to modify the file. I put the iMac to sleep and have not gone back yet.

If it hasn't worked I think I will go through my time machine backups and grab an old com.apple.mDNSResponder.plist from Snow Leopard.

If that doesn't work I'll either wait for an updated OS fix or go back to Snow Leopard for a while. I cloned it to an external HD just in case with CCC.

Or I'll just deal with turning airport on and off all the time. Maybe write an Apple script to do it for me.

Apple must know of this bug though, it was happening at the golden master phase of the Lion OS.

Of course, as a last resort, I could erase and install and then migrate my user settings from a Time Machine backup.

No matter what I do, if I fix it, I'll make sure to post it here.

I have same problem on my MBPro 15' C2D 2.66GHz

Apple has flagged the bug that I raised as being a known issue.  Somewhat good news.

Just hope the fix is in 10.7.1.

Modifying the com.apple.mDNSResponder.plist did work for me, at least so far it seems to.

After several sleeps, I have activated myself, upon waking the internet works again.

Wi-Fi seems to take a second or so longer to connect but that is certainly not a problem comparatively.

I would not consider this a fix necessarily but it is, for me anyway, a work around for now.

By the way, I ended up using PlistEdit Pro to edit the com.apple.mDNSResponder.plist.