Sidebar Sidebar
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

When the hell is Apple gonna fix the Wireless problem in Leopard?!

Here's how you know there's a problem in Leopard:

Just got an AppleTV yesterday. After a few quirks (You can't play THAT video! No, not THAT one either!), I got it working. I took a look at a bunch of Seinfeld episodes. Barely a flicker. Meanwhile, my MBP has been essentially showing 3 seconds, then thinking for 30, then showing another 3, etc. This even happened when I was TWO FEET FROM THE ROUTER. I plugged it up into the AEBS. No problems at all (even though it's supposed to be slower than 802.11n).

Therefore, I can only imagine it has something to do with Leopard or the 802.11n drivers. Speaking of which, is that stuff still draft specification? Perhaps that's part of the problem. Maybe they got it wrong and are going with a "draught" specification, those drunken fools.

This is beyond annoying. A 100Mbps connection shouldn't be effing up streaming video from 20 feet away. Someone really needs to have a boot put up their posterior.
 
Have the new macbook pro, wi-fi drops every 5 minutes, completely unbearable.

Will be returning it if it isn't fixed shortly.
 
rebo said:
Have the new macbook pro, wi-fi drops every 5 minutes, completely unbearable.

Will be returning it if it isn't fixed shortly.
Click to expand...

Return it. This issue has been around for MONTHS without a fix (or even an acknowledgement from Apple that it is real).
 
i don't really see what returning it will do though? I think we've established this is either OS X software or Router Hardware related, not Mac Hardware related.
 
majordude said:
Return it. This issue has been around for MONTHS without a fix (or even an acknowledgement from Apple that it is real).
Click to expand...

It is real. Everyone here says it's real. And I say the same thing.

My airport connection is very unstable after installing Leopard. With Tiger, my airport configuration was rock-solid.

After updating Leopard to the latest version, the problem was rectified, somewhat, but it was not completely eliminated.
 
I seemed to have fixed my problems by simply ditching my old as dirt D-Link router and picking up an AEBS. All last night and this morning the connection to my mac seemed to be fine. Hopefully it will stay this way, I'll post again if I start having problems.
 
Green2Delta said:
I seemed to have fixed my problems by simply ditching my old as dirt D-Link router and picking up an AEBS. All last night and this morning the connection to my mac seemed to be fine. Hopefully it will stay this way, I'll post again if I start having problems.
Click to expand...

That settles it - i'm convinced my 2 (almost 3 :eek:) year old dLink is the router of all evil (geddit?!?@?!)

It can't be software/OS X related any more, i've tried EVERYTHING.

Getting a new router with my new ISP in a couple of days, so fingers crossed.
 
I was on the phone with Apple support today. They said they never heard of such a problem. He told me to go to the genius bar. I have an appointment tonight, but now I am in a public Wifi area and all is working just fine.

It doesn't mean it's not the OS, but it may mean I should also get a new, better router. Probably time to upgrade anyway.

I'll let you all know what happens.
 
yeh i'm absolutely convinced it's the router not being leopard compatible. I wouldn't really expect a 3 year old router to be fully up to speed on the leopard technologies.

I should be taking delivery of a new router tomorrow! If that one's no good i'm going to try an AEBS.
 
I had this problem using a WRT54G with DD-WRT. Switched the channel and no more problems. I live downtown in a major urban center and there are plenty of other wireless networks causing interference. Understandably. Tiger and Leopard have different network stacks and thus will perform differently under similar circumstances. When using Tiger previously on the channel that Leopard used to drop, I would have delays in page response, but the connection would not drop. After several seconds of lag, things would resume as normal. I suspect Tiger is not dropping a connection in many instances when interference dictates that it should. It holds on to that connection like grim death even though it is unable to use it. Leopard seems to drop the connection when it is not able to use it which makes more sense.
 
The dropouts for me vary. Sometimes I can go hours and hours, sometimes it'll happen a couple of times in an hour.

I've tried every channel in my Airport Extreme, and there is only 2/3 other wireless routers that my MBP can pick up.
 
I don't know for sure why, but my MacBook Air has been really good about staying connected to my wireless network the past couple of days. It may have to do with one of the following:

1. I've been leaving my Airport Utility running constantly, on the wireless monitoring screen where you can see the wireless connections and their signal-to-noise ratios. Perhaps this constant polling of the network keeps the MBA from disconnecting?

2. I finally hit a set of network settings that seem to provide optimal connectivity for my twin Xbox 360s... I'm using channel 6 (obviously, which channel you use depends on what's around you), multicast rate of 5.5, Connection Robustness = on, 802.11n (b/g compatible). Since I made this change, my 360s can stream video flawlessly (no buffering) and they get pretty good connection strength from the AEBS.
 
Problem fixed for me

This issue has been driving me mad. I've had my blackbook since November. The connection started dropping when I upgraded to 10.5.2 (last leopard update). I've scoured these forums and apple's support site for a solution. I tried various things but nothing worked. Last night I finally took it into the genius bar.

I'm not sure exactly how to describe the technical jargin, but essentially the apple guy said the software for airport is probably corrupted, so he did something to archive the existing OS 10.2 (set it asside) and installed 10.1 with his own disk. When we were finished (about an hour), he deleted the archived 10.2 OS (not required, but it took a huge amount of space on my hard drive). It's worked without a single drop since (yesterday).

Here's the key I think: I asked him if I could have done the same thing (go back to the previous OS) with time machine? He said yes, but it would probably not fix the corruption associated with the airport (driver?). His way was cleaner because it set asside everything associated with the existing OS and reinstalled a clean tested version of the OS (although a previous version).

He said, if everything works fine for the next week, then go ahead and update to OS 10.2.

I hope I explained it adequately, perhaps someone could translate it to geek speak. ;)
 
kewl said:
This issue has been driving me mad. I've had my blackbook since November. The connection started dropping when I upgraded to 10.5.2 (last leopard update). I've scoured these forums and apple's support site for a solution. I tried various things but nothing worked. Last night I finally took it into the genius bar.

I'm not sure exactly how to describe the technical jargin, but essentially the apple guy said the software for airport is probably corrupted, so he did something to archive the existing OS 10.2 (set it asside) and installed 10.1 with his own disk. When we were finished (about an hour), he deleted the archived 10.2 OS (not required, but it took a huge amount of space on my hard drive). It's worked without a single drop since (yesterday).

Here's the key I think: I asked him if I could have done the same thing (go back to the previous OS) with time machine? He said yes, but it would probably not fix the corruption associated with the airport (driver?). His way was cleaner because it set asside everything associated with the existing OS and reinstalled a clean tested version of the OS (although a previous version).

He said, if everything works fine for the next week, then go ahead and update to OS 10.2.

I hope I explained it adequately, perhaps someone could translate it to geek speak. ;)
Click to expand...

Very interesting.

This is the first time i've seen a genius acknowledge the problem. If my new router doesn't do the trick then i'll certainly give this one a go.

It sounds like this might be a good solution. I had problems in 10.5.1, but I suppose Airport might have got corrupted somewhere along the line and that didn't get fixed in 10.5.2, the update just papered over the cracks perhaps.

Can someone perhaps point me in the direction of a solid, straightforward guide to moving back from 10.5.2 to 10.5.1 with the install discs that came with my mac pro.
 
Stability...

I had achieved a very stable connection under 10.5.1, actually the solution was hammered out through hints posted here and on the Apple forum sites, when I upgraded to 10.5.2 which was supposed to be the miracle cure for the wireless issue my connection started acting funny again and I had to re-read my own posts etc. First was Location, I reset my location to Automatic and again it manifested the old symptoms of being corrupt or it does not perform as it should so I set up a second location and deleted Automatic for good, Then I switched the channel and for my system channel 2 performs best, my powerbook's connection also started acting funny after the upgrade and so switching to a channel that was stable to both my mini and powerbook was a good solution. After many posts related to the keychain I noticed that the file contained in the Control Access tab related to my wireless network was moved, the file named "Airport" that was initially in /usr/libexec was now moved to Groups://. This I think changed the nature of the keychain and thus affecting the stability yet again. I Also made a copy of the network keychain located in the System section in Keychain and made copies in User and the Login section as best I could, copying over the name of the location and the sort of keychain with all the files contained in the Control Access tab, also adding the System prefs app, SystemUIServer and Apple 80211Agent files to this list added robustness and redundancy to the keychain, so to say that the wireless issue has not been resolved is not entirely accurate, some have not found the small detail that could be the key to a solution or for some reason their configuration does not allow for the vast amount of hints posted here to be of working order, it is also difficult to really address an issue without having hands on your systems, their could be a small detail that somebody may be missing, I would truly like to help all of you but I try my best to point and share as much detail as I can hoping it aids one of you.
 
fluidedge said:
i don't really see what returning it will do though? I think we've established this is either OS X software or Router Hardware related, not Mac Hardware related.
Click to expand...


It's not a router issue. I have this problem too. And yes I agree it's probably not an Airport issue. It's Leopard. It must be, because Windows XP (bootcamp) works fine on the very network I can't seem to get into under OS X.

COME ON APPLE GET YOUR @#$% TOGETHER!!
 
I have to confess, I have not read all the thread (I'm supposed to be working :D)

I have a problem where Wireless to a Netgear DG834 is great and stable and even pretty fast now - but if Macbook sleeps, on waking it will not find my Network again. I do not have WPA2 SSID broadcasting and it seems to struggle. A restart *normally* cures the problem.

It's very frustrating!
 
Holy sh-t. I got it working.

Took it into the Apple Store and they ran a Permission Repair. It worked. I wasn't convinced. I took it home and tried it on my network and behold - it works now.

So if you haven't tried repairing permissions yet, try it. I have no idea how it fixed it but it did.
 
I posted on an another thread that I changed to broadcasting my SSID instead of keeping it hidden and it worked. Not one drop. Seems my MBP had a hard time finding my network if its name wasn't broadcasted.
 
Stridder44 said:
Holy sh-t. I got it working.

Took it into the Apple Store and they ran a Permission Repair. It worked. I wasn't convinced. I took it home and tried it on my network and behold - it works now.

So if you haven't tried repairing permissions yet, try it. I have no idea how it fixed it but it did.
Click to expand...

could you explain how this is done? sorry, i'm a n00b :(
 
Stridder44 said:
Holy sh-t. I got it working.

Took it into the Apple Store and they ran a Permission Repair. It worked. I wasn't convinced. I took it home and tried it on my network and behold - it works now.

So if you haven't tried repairing permissions yet, try it. I have no idea how it fixed it but it did.
Click to expand...

Tried that.

:(

back to the drawing board
 
by the way, i still find it ironic that the problem they hope to fix prevents you from doing so. Apple expects us to download 10mb update files when we can barely download 10kb html files sometimes.
 
You must log in or register to reply here.
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.
Top Bottom
Back