AirPort doesn't connect after wakeup

I'm not sure what you mean "moving the services up" ??

But since I tried some of the advices here around New Year - among them to delete all information and start over with the Airport settings I have actually have had no problems.

Although, I still hope for a soon 10.5.2. update to fix various issues with my PB - among them "goes to deep sleep and needs to be restarted" issue - the Airport behaves well now.

Hi I have been having the same problems that most of you have here.
I have tried the solution posted here too but after a while it stopped working.

So I was testing some other solutions When I came across this work around.
It's not 100% but it does seem to work. All you need to do is create another user
and make sure that user can connect to the airport network.
Once you have tested it. You do not have to log-in to that account anymore.
It seems that by having a second account that connects to the same network automatically
seems to trigger the main account to connect automatically.

As I said before it's only a work around and it's not 100% but after a week of this
it seems to have settled down.

Hope this helps
Dave

Any joy from 10.5.2? Doesn't seem to have helped with mine...

Tried 10.5.2 and now I cannot connect to any wireless networks. Internal network card seem to be dead.

I have experience improved stability for some weeks now - and are not able to report any changes due to the 10.5.2 update.

As suggested in this forum, I had previously deleted all settings in AirPort (Network preferences) and re-started the computer and then started all over selecting a network etc...

Since then the AirPort on my PB G4 has been stable.

Have you tried the steps above? They seem in line with a suggestion I saw here, indicating that a creation of a "new" user would help.

That means ? You are not able to seen any networks at all?

Thats right, cannot see any network.

And you have turned AirPort on - I guess? It's a stupid question - but we have to start somewhere.

Have you tried with the AirPort Admin tool - if that can recognize your network?

I deleted the airport service, then I try to add it. I push the button "Turn Airport on" but nothing happens. The Airport utility does not detect any AirPort base stations. I have also tried to reset the base station. A PC can connect so it works.

I assume you are using an AirPort device from Apple? Or what?

If you can connect to the wireless network from a PC - and you can not turn AirPort on in the Apple menu - there might be a real problem with your AirPort card in the Mac.

Have you tried to use on of the Widgets that can detect wireless networks - just to test? E.g. from MacWireless.com ?

Hello,
I called Apple Support. They told me to try the "archive and install" option. This is a new installation, but my previous settings are migrated to the new installation afterwards. Still no response from my built in network card.

I then sent the macbook to apple support. They switched to a new network card but they were still not able to make it work. They tried to load a fresh os and that worked.

I have now reintalled from scratch with the format option. It seems to work fine now! DO NOT MIGRATE YOUR PREVIOUS SETTINGS!!! Install everything manually afterwards, do not use the migration assistant.

Because the archive and install option did not work, I would expect that the source of the problem is in my previous profile, and that a new user profile might make it work. Just create a new user and delete the old one or something. If not - reinstall.

Remember backup´s and good luck 🙂

Finn Ove

I had this problem with my brand new MacBook pro (Tiger pre-installed with Leopard upgrade drop-in). Everyone seemed to have a long, drawn out solution that involved deleting keychains and turning airport on and off a billion times. None of it helped me. I got impatient as none of the Apple updates improved the issue. Finally I resolved the issue by doing a clean install of Leopard (not as scary as it sounds since I had a good history of Time Machine backups). The problem totally went away. I am now assuming that the issue had something to do with installing Leopard as an upgrade over Tiger (i.e. an upgrade install instead of a clean install).

I had this problem from Day 1 with my Intel iMac that had Leopard pre-installed. I outlined the details in a previous thread titled "Sleep function=wireless problem?" My experiences with Apple Support are also described there.

To briefly recap, my work around is to set the sleep time in the Energy Saver preferences panel to Never. (The screen is still set to dim out after 15 minutes of inactivity.) As long as the computer doesn't sleep the wireless connection remains strong and robust. Since I did this, about four weeks ago, the connection hasn't even flickered. Shut down and start up are no problem either - it's just the sleep function that causes the wireless fadeout.

I'd be very interested to know if anyone else has had a similar experience.

I am now assuming that the issue had something to do with installing Leopard as an upgrade over Tiger

Nope. I did a clean install of Leopard on my MacBook Pro (2.16 GHz Intel Core Duo). I fully wiped the hard disk, did a clean install and reinstalled all software. Nothing ported from the Tiger installation (except data files).

And... I have the same problem. No problems anywhere except at home. (Airport Extreme Basestation 802.11n - WPA encryption.)

The airport fails to connect consistently when waking from sleep. Manually turning off the Airport and back on instantly reconnects.

Hoping for a fix ...

I never had this well known strange behavior occur in my Macbook until today, after recently upgrading my Leopard to 10.5.3. After several sleep sessions (closing the lid), AirPort became non-responsive and would not connect to my robust wireless network (full signal). I had to turn it off and then back on (annoying) and then AirPort connected immediately. Rather than fixing this issue, it appears that 10.5.3 has created the issue for previously non-affected Macs. Here is to hoping this issue will be really fixed for all Macs in 10.5.4!