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.
Like "I" have said in this thread I have 10.5.2 and it doesn't do this. It did in 10.5.1!!!
Initially it did it in 10.5.2 as well, like it did it in 10.5.1 for me but I took the Airport express out of the equation, changed the channel to 9 for all three remaining Airport hubs, and changed the refresh rate to something like 9 days. I have not had a drop out for nearly three to four weeks now.
Plus you can not say it is because 10.5.2 when it was doing it to some people that were using 10.5.1 as well. There are just to many variables in the equation. There is a problem but it is not known what it is yet. Millions of users on 10.5.2 are not having the problem. There WERE a lot of people having this problem in 10.5.1 as well. Maybe it is just Leopard.
You shouldn't jump on somebody "Haven't you been reading the thread?" statements. Every suggestion might help some body out there. A lot of people are having problems. Even though people think it is exactly like the other person problem a fix might work for one that didn't work for another. Example me, have not had a drop for three to four weeks, so a solution worked for me that didn't work for others.
Yes, I have read this incredibly long thread and it goes all over the place as far as cause and solutions go.
So, unless you have something positive and constructive to say, why don't you just keep your flip comments to yourself.
Come to think of it "areine" might have a point here. We've seemed to figured out that the Wireless Access Point in use will not make any difference, BUT has anyone used non Apple network cards?
It would seem everyone to date is using Apple Airport/Airport Express NICs. I can't see anyone talking about non Apple hardware
in/on the Mac which has the problem.......
Maybe it's an Apple driver issue in 10.5.2 and not using the built in Airport cards, and using a 3rd party drive will provide a fix this....
Neil Cudmore wrote:
Maybe it's an Apple driver issue in 10.5.2 and not using the built in Airport cards, and using a 3rd party drive will provide a fix this....
I've actually wondered the same thing myself. I'm thinking of getting a 3rd party wireless card for my MacBook to test it out. Seems easier to do that than to mess with the NIC in my Mac Pro.
Have tried the solutions on the thread, but nothing has worked. Happens on all networks, and an old Powerbook G4 running 10.4 works a treat on my home network. Not at all happy at the prospect of trying third party cards. I'm not a technician, nor should I have to be after forking out £1300 for a lap-top.
This thread is interesting, but I'm curious as to why everyone considers it a bug.
When ever you click the airport icon in the menu bar, it triggers the OS to scan for available connections to make sure the menu options are up to date. If you wait for just a second, it normally stops, unless there are a ton of available access points, which may then take a little longer.
So it will always say this when you click the menu, since clicking starts that process. To assume that it was "scanning" before you clicked it because it always says scanning when you click it seems a false assumption.
This is so frustrating. My signal constantly gets dropped, excessive scanning, and having to reconnect to my airport express. I read everything else on this, so I know I'm not alone.
Bought this beauty on Saturday, MacBook Pro, screamin fast. This morning when I awoke it from sleep the internet connection was VERY choppy so I did a ping router and noticed 4.3 ms all the way up to 403.2 ms... this isn't right, i thought.
I did the search on airport and speed issues and I ended up here reading this thread for a few hours.
I tried a few of the steps like running onyx, deleting prefs, powering down my Linksys router wrt4g, and nothing fixed the sporadic connection. My next step was to utilize my apple care agreement and spent about 30 mins going through everything the tech guy could think of to know avail.
I then got into my router config and starting messing around with the channels. For this router there are 11. I tried different channels until I found one that was consistent and then I looked for the fastest consistent channel. Right now I am pinging my wireless router at 2.5-2.89 ms. It isn't as fast as the straight ethernet cat5 cable which was .8 ms but it is consistent. I am gonna gonna check out routers and the apple modem tomorrow. So if you haven't tried changing channels try changing all 11 of them and then pinging your router to find the most consistent. The tech guy said there could be some interference but I doubt that. Anyway, I will continue to follow this link and hope for a fix by apple or some other better option.
My experience may help, unfortunately it is a long saga. Firstly it took me two and a half days to get my Mac to Talk to the Airport Express, but that is another story!
My setup is a G5 PPC Tower running 10.5.2, and a BT Home Hub, I was also getting severe drop out when trying to stream music from my study to the lounge about 35 foot distance. I tried everything, and nothing would improve it, tried activity monitor and noticed that a programme called CleanApp had a deamon that was taking up about 65% of the processor time every few seconds, this was near the problem I had with the Airport Express, which worked for about 5 seconds then went of for about 5 seconds. On clean app there is a feature called 'logging' this can be turned of in its preferences, this stopped it using the processor, but unfortunately made no difference to the Airport Express, but it would be a good idea to turn off this feature if you have the programme installed.
I next tried a G4 I have running 10.4.11 which is hard wired by ethernet in to the BT Home Hub, this reduced the drop out, but it still existed. I then plugged in the Airport Express near to my computer and used some headphones, worked perfectly ! I then moved the Airport Express back to the wall socket near my stereo, still the same problem, so I used an extension to put the Airport Express up higher, and it worked perfectly.
I have had a lot of experience with Radio Microphones, and unless you used a diversity receiver there could be blind spots even in direct line of sight between the microphone and the receiver, moving the receiver a few inches either removed the blind spot or moved it eleswhere, and I think this may be a case of the same, not a problem with 10.5.2 or even 10.4.11. Where the Airport Express was plugged in was behind the television and about 10 inches or so off the floor, so it may have been screened by the television. It is certainly worth a try putting the Airport Express on a mains extension cable and moving it around a bit, it seems to have worked for me, but I will let you know if there are any further developments. It has only taken 7 days to get it to work!!!
