The scary things is when you search for similar issues you get pages and pages of threads:
That was just using the search words: network not working after sleep
If you alter the search words to more or less and different words then you end up finding even more threads about the same subject. This is bad. Gone from frustrated to really unhappy ... and now have committed to putting Snow LEopard back on my machine but destroying all settings and starting afresh to see if that fixes anything. Like I really have time to spare to do that ...
Ok, regarding the "Wake to sleep = No internet connection" problem under OSX Lion I discovered a few things.
- Whenever my mac puts itself to sleep the problem seems not to occur.
- Removing my WD 2 TB external harddisk, using for time machine backups, solves the problem instantly.
- Instead of disabling wifi and enabling it again, selecting "make Time machine backup now" ( Time machine icon,
upperright under startup items) also enables Internet again.
So, like some others also concluded, it seems to be Time Machine related ????
At present the bulk of my problem seems to be related to Time Machine and the iMac putting itself to sleep (when not set to do so).
However, with no USB drives plugged in and all is fine.
Plug USB drives in and no Time Machine it connects to Airport Extreme OK and no problems but it then seems to go to sleep very often, a lot more than it is set to and also puts my printer to sleep, it didn't under SL. You can sit and listen to the computer shutting down and then seconds later starting again without touching a button. It does not do this if there are no USB drives connected. It does it whether the button for putting drives to sleep is checked or not in the network settings.
Each time it powers back on, I have not done it does it repeatedly on its own, it renames the iMac saying the name "iMac" is in use. So I start with plain "iMac", next it becomes "iMac 2" and so on. Yesterday I was out for a few hours and left it switched on, when I got back it had got to iMac 856. Thus it had gone to sleep and woken up of it's own volition 856 times. I do not know enough about operating systems to know where to start to sort this but sure did not have this problem with Snow Leopard.
It get worse if I put power into Time Machine, even if it's not set to be used, just merely switching on and then Lion does not like Airport Express. I lose my WiFi connection in Express and yes I have checked that the Time Machine is not configured to be a wireless router in it's own right.
So no USB hard drives connected it works OK.
Connect USB hard drives, WiFI is OK but the computer keeps switching itself off and on again (sleep mode).
Power up Time Machine and I lose the WiFi.
Am able to reproduce this problem without fail on an early 2008 13" MacBook, late 2009 27" iMac, and an early 2011 13" MacBook Pro (purchased 2 days ago). All are on the same home network using a Time Capsule / Qwest router combo.
All it takes is a DVD in the internal optical drive.
Not all DVDs, mind you. Here are some that do: recorded DVD+Rs, to include my Lion install disk and a homemade DVD movie; two commercial education disks; and a commercial Cars DVD video disk. That don't: iLife install disk and a commercial Beauty & the Beast DVD.
All three computers were upgraded using the same Lion image. The iMac and MacBook Pro were updgraded from Snow Leopard; the MacBook from Leopard.
I've seen a lot of discussion about external hard drives and Time Machine backups, but they do not induce the problem for me (the iMac has both, the MacBook has Time Machine only, and the MacBook Pro has neither).
To restate, the "problem" I speak of is loss of internet connection (with wifi on) after the computer is awaken from a manual or automatic sleep. Not all browsers are affected (Firefox on the MacBook and Opera on the iMac work fine).
I have the same problem (airport not reconnecting to WiFi network after waking up) with Macbook late 2009 - and it only happens when the computer goes to sleep while a TimeMachine backup is in progress (the TM HD is connected to the Airport Extreme basestation). Also, sometimes I get the error that another machine is using the IP address. These errors used to happen a long time ago but were fixed after previous updates and now have appeared again with Lion. I hope these are fixed in the coming updates.
I've been having same issues on my MacPro, using Gigabit LAN interfaces. I just tried to reset all ths config by removing all files from :
after that, do a reboot and re-configure network settings again.
I just did two sleeps and problem is not present anymore.
FYI, TimeMachine is inactive since I upgarded to Lion, my NAS is not yet supporting it, so I doubt this is related to TimeMachine interaction.
Give it a try.
I think it's a bootpd problem.!!!
The connection , after it fails does not come back or just some times.
Just for the fun of it, I narrowed the scope from my Extreme down to only one IP address, thus the DHCP server in the Extreme has no more addresses to give.
Therefor I started in the same subnet the DHCP server on the MacPro server.
The funny thing is, I am NOT getting the bootp requests on the MacPro server.
So it seems there's a glitch in the protocols somehwre...
It rimes with the stations that go to sleep and get out of it. If the Lease time of the DHCP is not due, then it tries to get back the old address and the troubles begin.
After widening the scope for the dhcp addresses again on the extreme, it works all fine again.
Strange but true. And that is the reason that I am starting to think in the direction of the routing , the failure of that might be the issue...
Has anyone here cleared their PRAM? (Also no harm to reset your SMC Power Manager.)
Has anyone re-entered their network password and/or made a fresh entry in the keychain? (By deleting the old keychain entry--write it down first--and creating a new one by filling in one of the dialog boxes.)
I've noticed this problem with several big upgrades. I don't believe it's a bug, or special to Lion.
These threads tend to get more and more hysterical. Not helpful to each other.