After installing 10.5.2 I'm noticing that if I click on Airport icon it indicates that it's scanning briefly and then stops. Is this a bug with 10.5.2? Unplugging my Airport Express briefly didn't seem to do anything.
I have tried the solution described elsewhere - download AP Grapher and have it running in the background - scanning every 10 secs. This seems to keep the connection busy and I have had a trouble free day.
Small overhead in performance, but well worth it.
None of the updates seem to make any difference on my machine.
I don't know if this was mentioned before, but I figured I throw it out there anyway. My Macbook seems to hold the connection, but doesn't receive any data. When clicking the airport icon, it is always down one bar from max when this happens. As expected, it goes to "scanning" once clicked, as this is by design. If I keep clicking the icon to force it to scan repeatedly, the connection works and web pages load while I'm clicking it. The problem only exists when other networks are detected during the icon clicking.
I tried changing my Time Capsule to wireless-N only and the problem seemed to go away. Unfortunately, my other wireless machines aren't "N", so this is not a viable solution for me.
I feel guilty now about recommending Apple to friends & family, as this is just stupid.
Hi. I have had this problem right from when i got my first macbook pro in February 2007.
I replaced the airport card and there was some improvement, but it wasn't good enough.
i tried to purchase the 802.11n enabler but then discovered that was only for 10.4, that i already had it. then purchased the new macbook pro and the same problem's here. drops signal, then scans for ages, then picks up again, and then drops. tried both the solutions suggested through this thread but no particularly huge impact... does seem to be somewhat better though, msn hasn't knocked off. i am shocked that this is still a problem since so long.
PS. problem returned when got 10.5, had gone away after new airport card in tiger.
Had no 'Scanning' problems yesterday when I was running OSX 10.4 today I installed 10.5 and updated to 10.5.6... What is going on!!! This forum has been running this problem for almost a year! I've tried the 'fixes' but this is ridiculous. Why are we not getting a 'solution' from on high??
Add me to the list of the disgruntled. I just bought a new MACBOOKPRO. The airport continues to scan non stop. I am hardwired just to get this message off.
My MacBook Pro MacOX10.5.6 is also scanning excessively. Scanning is almost constant on/off and drops connection. I have 3 others computers (Mac & PC) on same network/wireless router which do not experience this problem. So it's specific to my MacBook Pro. Cannot find any credible solutions for this problem anywhere. Amazing that Apple Techs have not chimed in here. Any suggestions?
Seeing this on 10.5.6 on an Intel MBP. My older PPC MBP does not suffer from the same problem (at least my wife isn't complaining about it and I don't know how you could miss it).
I'm in the same boat and I'm on my way to join others in the padded room.
I have 2 macs- powerbook pro running 10.4.11 and my new macbook pro running 10.5.6 both using the same older airport extreme. The older mac finds the airport and stays on like it should but the newer macbook running leopard is constantly scanning. I have tried all of the suggesting here and else where but without any luck. Hopefully Apple will hear us bouncing off the walls and come up with a solution soon!
I've tried all of the following individually and together without success-
- changed the channel away from the neighbors
- changed to g only instead of b/g radio mode (older airport)
- increased the mbps rate
- interference robustness
– closed network
- apgrapher
still scanning and still slower than a muddy river...
Clicking on the drop down menu does work to shut it up but only for a few moments.
Could it be an incompatibility between the new internal network card and the old extreme? Any suggestion appreciated...
Oh and yes the internet connection is dropped occasionally as well even with full bars...
can it really be true that there is no solution working!
I am furious about it, i tried everything, and its scanning constantly in the menu bar... sometimes i only have few minutes online, and the reboot! Apple please take this issue serious and come with an update or bugfix!
Gee, I think I see what's happening here. Windows users abandoning ship because they fell for some slick ad. Sorry folks, but you still gotta know basic stuff...like _which wireless network you are connect(ed/ing) to_! Hey, you get what you deserve for connecting to your neighbor's wireless network. Did you ever consider that maybe your "generous" neighbor may want to intercept sensitive information such as a credit card number?!
I also have a new MacBook Pro running 10.5.6. I use a Time Capsule and my Airport connection has become unusuable. My wife's aluminum iMac in the next room is humming along fine on the same network, but here I am with a laptop hooked up to the internet with an Ethernet cable. I can't believe it. It's laptop teathered to a Time Capsule. The only time I can move this "laptop" is if I am willing to go without internet access. I can usually fix my own problems; I have had Apples starting with 2 Lisas, but I am stumped here. A computer that continually scans for the network even after it has connected to the network.... wow....
Installed and rebooted, but no change. I have 2 Windows laptops and a Windows desktop, and Xbox 360 and my iPhone that ALL connect to the WiFi flawlessly. But my Mac Mini constantly drops the network. It's infuriating. I have a difficult time running the Software Update because of this network problem.
What's really disappointing to me as a fairly recent convert to the Mac is that this has been going on for a pretty long time (based on this thread) and there has been no participation from Apple, and no clear solution. I've tried most of the ideas suggested but with no positive results.
It's pathetic that for the magnitude of the problem, there hasn't been a concerted effort from Apple to resolve this (at least, it's not apparent in this thread).
