Excessive Airport Scanning after 10.5.2

I tried the first step in this post and so far that has helped.
http://discussions.apple.com/thread.jspa?threadID=1689557&tstart=0

GOOD NEWS. Apple just released a software update for Airport yesterday (9 Nov. 2008) that I installed, and it fixed the problem. Almost unforgivable that it took so long, but better late than never.

I don't see this update when I run the software updates...what kind of update was it? the only one I saw had to do with camera software. This is so frustrating.

It's "AirPort Extreme Update 2008-004" (1.0)." Find it here: http://www.apple.com/support/downloads/airportextremeupdate2008004.html

From the site: "This update is recommended for all Intel-based Macintosh computers running Mac OS 10.5.5."

Note: I don't have Airport Extreme. I have an old Airport Express and a Linksys. But it still fixed the problem.

Good luck!

I am also having the problem of losing signal off and on. I applied the update (mentioned above) yesterday, and I still have the same problem

This is me on the third parragraph.

Just bought my first Macbook Pro and I have the Netgear DG834G or something. I can't believe this doesn't work. No one has found a fix for it yet?

Another vote for 'problem NOT fixed' after applying every update available on my MacbookPro.

What if we launch a coordinated mass email to Apple and some Mac publications editors with the same heading? If they get 3,000+ emails all with the same heading they ma notice and try to help us. Does any one know of the email addresses (not just support@apple.com) of actual engineers/execs at Apple whose attention would be useful?

My suggestion for a heading would be [Wireless connection failures on Macs]

The publication to email would be Macworld (I am not up on the current Mac publications).

What do you all think?

-bakki

Glad to know I'm not alone. Slight comfort. I almost bought a new AP thinking that had to be the problem. Of course, this has only happened since the OS update. I never had a problem prior to that. None of the subsequent updates have helped, either. Getting rid of the airport status in the menu bar has only helped in that I don't constantly see black bars fade to completely ghosted every 30 seconds. I'm hoping that this issue is resolved soon. It's beyond maddening.

Well there's a couple of things I've learnt.

The 'Excessive Airport Scanning' isn't really a problem if your connection actually isn't dropping. When you click on the wireless icon it always says "scanning" and then "on" (if on, obviously).

Other internet problems are when you're connected for a while and then it suddenly drops. My problem personally is that my connection is fine and then suddenly drops for a fraction of a minute (where all my Skype calls drop, loading sites stop loading, etc...) but a few seconds later it's back on.

I've already had all the updates and I'm going MAD with this. I would definitely write to the mac people but let's be even more specific with the subject tile.

This is extremely stupid! I had to watch my airport lose the signal 3 times while logging in to post this response. I dropped an international business call 5 times this morning. It's sad that Apple can't admit there's something wrong here.

It seems that Mail is related somehow. I force quit the app and the internet stays up a little longer.

I installed the latest update AirPortExtremeUp2008004.dmg (from http://support.apple.com/downloads/AirPortExtreme_Update_2008004). As I suspected, it did absolutely nothing.

The airport continues to scan AND self-assigns itself an IP address. Like the rest of you, I have been raking my brains trying to solve it. At this point I am sorely tempted to blog about this. Just how many people in total are having this issue? If we took this to the media I wonder how Apple might react?

Am I crazy or has the latest OS update fixed this? I'm waiting and the bars haven't faded...

I don't know, if I'm too happy at the moment, but the latest Update seems to work!
I'm crossing my fingers...

Okay, it's been totally stable since the update last night. I do believe the problem is solved.

Don't know guys... I cannot say "is stable" after this 10.5.6 update but "is MORE stable..."

Comparing to months of "nothing" and "not fixed" I'm happy to see that something is changed.