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?!

Well, we've got to 200 posts and it looks like the problem just doesn't want to go away. :(

The worst thing is that people who NEVER had any wirless issues before have suddenly joined our club thanks to the new update - I feel pretty sorry for those people. Of course it does appear from this thread and others that SOME people are now sorted and if I still had my MBP I'd love to know if I was one of them!

Unfortunately a lot of people aren't so lucky as this thread that was setup yesterday shows:
https://forums.macrumors.com/threads/432284/

I don't know what else to say; I'm kinda giving up hope here. All I can say is for people to keep sending their feedback to Apple themselves, describing the problem and hardware you have in detail:
http://www.apple.com/feedback/macosx.html

In the meantime I think I may have to get back my Tiger disc from the guy who bought my MBP before I decide to buy a Mac again ...
 
I've had nothing but problems with wifi since the airport update that came out after 10.4.10. It drops connection all the time. Nothing that I did would keep it from doing that. I got so used to turning off and on the wifi that it almost feels weird to not have to do it now.

That's because 10.5.2 finally fixed my wifi problems. Since the update came out, not one single dropped connection.

For those still having problems or having new problems with wifi, I feel your pain but am glad I don't have it anymore. Let's hope Apple fixes this without messing mine up.
 
I discovered this...

I was trying the connection and I put the computer to sleep, it sleeps on its own fine, then it cant find the network? I tried my own hint of deleting the keychain and starting a new one, did it once (nothing happened) and then I decided to inspect the control access panel and one item was missing: which was the system preferences icon on this list, i add it to the list and now i tested it and i think its working so inspect your keychain access allowed apps.
 

Attachments

  • one.jpg
    one.jpg
    23 KB · Views: 875
just had a bit of scare - i thought i was completely fixed then the connection dropped!

Changed my security to WPA-PSK (as i've been meaning to do for ages) and it all seems to be OK again.

Everyone with problems - try this:

-turn airport off on all your wirelessly connecting machines
-Hardwire a computer to the wireless router
-type 192.168.0.1 (or whatever your router IP is) into safari/firefox
-Reset your security to WPA-PSK, if you already using WPA-PSK then reset it anyway
-change your password (everyone choose a new password) and whatever else you need to do
-restart the router etc
-unplug from the router
-search for 'keychain' in spotlight (well thats how i do it) and delete the keychain password for your current network
-now turn Airport on on one machine you use to surf wirelessly
-click on network properties
-assist me
-follow the instructions
-do the same for all other machines

So hopefully you have now completely reset the connection, deleting all memory of the old connection(s)

Let us know if this works out - it seems to have done the trick for me
 
After the update I haven't experienced any disconnections. I was able to download and install the 10.5.2 without any issues. It's been a couple of days but my MacBook Pro is rarely powered down and it's either being used or in sleep which before is what would bring on the issues.

Another issue I had is when I used the laptop with another router(Motorolla) at a different location. Very very slow to connect or open pages. I never changed any settings so I'm gonna be interested to see if the problem goes away this weekend.

In both cases I'm using WEP. I don't have WPA options because of other older devices that don't support WPA.
 
Wifi still broken for me on 10.5.2 - For some particular networks it cant connect at all in the first place.

Everything worked on 10.3.9 using the automatic settings, upgraded to leopard and now I can't connect to some networks no matter what I do. It can still connect to other networks, and other 10.3 and 10.4 and vista machines I have still connect to all the networks perfectly.

Airport is still broken in Leopard.
 
it could be your configuration?...

how do you have your network settings configured? if you have pics just post them, there may be something thats overlooked.(never mind answering I already posted on your other thread,motulist) I guess we can define two types of issues here, those users who are connecting to various networks and are constantly mobile and those who have a personal network at home and cant connect, so the answers need to be distinct. please specify for whom are you issuing possible solutions and thanks all for the any input, thanks again.
 
now I remember!...

It was at miami airport that I had trouble connecting, the full bars on but I had no router ip, their automatic loadpage would not load, anyway it was only after a while that their page loaded. no instant on. I did make it's own location, I did a traceroute through network utilities, and it was a "no go" until for some reason it kicked in, I did nothing special other than to hit the the "renew dhcp lease". did I mention I did install 10.5.2? :cool:
 
the variables are plenty...

I have a mac mini (intel) and a powerbook g4, the powerbook has been more consistent than the mini, I think that this thread applies mostly to portables, I have read on the apple forums that some had had issues with the airport card itself (a certain series), Im running a home wireless network so my testing on the field is limited, most of my posts have been about achieving a stable connection at home, thats why I ask those that are coming into this thread to state the issue as best you can and to make the differentiation between home network and mobile connections such as connecting at Starbucks and such.
 
airportd has been moved in 10.5.2

Searching through one of my external drives for airportd (airport daemon) I found its location under /usr/bin/libexec or the hidden files of the HD, when I looked in the same spot it was not there under the new 10.5.2 upgrade, it had been relocated to Groups://. this can explain the initial connectivity problems after the upgrade, after a quick permissions repair and a cache clean-up it seems to have stabilize (for home networks at least) and adding the system preference app to the keychain control access applet help return it to normal. So far its been good and I've been connected for the last 4 days or so.
 
Consultant said:
A lot of modems, especially the cheap stuff, don't work well with either windows or mac os x.

NO PROBLEM HERE WITH AIRPORT EXTREME N.
Click to expand...

But the point is that it DOES work well with Windows XP, Windows Vista, Mac OS Tiger and some Linux distros. It's Leopard that's the problem; blaming the hardware is letting Apple off the hook. If they just put the networking components used in Tiger into Leopard then a lot of people's problems would vanish.
 
I am experiencing exactly the same issue that the initial post described. My Imac drops the connection for no operant reason, the problem gets worse when I am downloading a large file. It took me two tries to get 10.5.2 update. I am using a new Linksys 802.11N router, never happens to the windows machine. I also notice that WPA was much worse then WEP, I never tried it with security off.


being new to MAC, I thought I had gotten a bad unit; Iwas about read to return it to the store when I came across a few threads describing the drop connection issue with 10.5.
this needs to be fixed
 
Grrr!

I set a bookmark using Quick Links, Subscribed Threads... so I always see the threads I replied to when I log into MacRumors.

I go nuts every time I see this thread. :mad:

"When the hell are Apple gonna fix..."

The better question is...

"When the hell is our skools gonna..." teach people proper grammar! :rolleyes:

(For you in Rio Linda, it should read... "When the hell is Apple...")

Maybe I just need to drink decaf. ;)
 
majordude said:
Grrr!

I set a bookmark using Quick Links, Subscribed Threads... so I always see the threads I replied to when I log into MacRumors.

I go nuts every time I see this thread. :mad:

"When the hell are Apple gonna fix..."

The better question is...

"When the hell is our skools gonna..." teach people proper grammar! :rolleyes:

(For you in Rio Linda, it should read... "When the hell is Apple...")

Maybe I just need to drink decaf. ;)
Click to expand...

majordude, I never knew you felt so strongly about the grammatical properties of the title. So, as to avoid your upcoming heart attack and keep the fragile notion of world peace in order, I have decided to ease your stress and changed the title accordingly.

All you had to do was ask! After all you only had 2.5 months to tell me ... :D (I'm surprised you haven't mentioned the capital "W" in "Wireless" as well; I get night sweats waiting for someone to reprimand me on that one.)

Now if only Apple would fix the wireless problem in the same way I fixed the title; we've both had the same amount of time after all ...
 
I can't stand this anymore! Apple should fix this ASAP, it's REALLY getting annoying
 
Vitek said:
I can't stand this anymore! Apple should fix this ASAP, it's REALLY getting annoying
Click to expand...

Annoying is an understatement. Frankly, I think it lets Apple off the hook. It's like putting up with the idiosyncrasies of an old car, an old machine or maybe an old piece of shareware that crashes twice a day but is still better than most software you can find in Staples.

I believe that having a viable wireless internet connection (especially on a notebook computer) is non-negotiable.

Fixing this issue should be priority one for Apple. Obviously it isn't. :mad:

Frankly, I don't even know if they even believe it is an issue.

I paid something near $3K for something that Dell would have charged me $1K for and I'd be able to get email at LAX, Starbucks and in my %$@^& home! :mad:
 
10.5.2

I installed 10.5.2. The size of the update was only 180mb. That update didn't solve the problem with Wi-Fi connection to my D-link router. Then I went to Apple.com and downloaded "Combo Update 10.5.2". After the instllation EVERYTHING is ok! My Wi-Fi connection is solid.:):):)
 
this is my latest addition to the keychain...

"I think that these elements add stability to the network...the system prefs app, the systemUIserver, apple80211agent and the network diagnostic app shows there because that the only way to establish the keychain after the update. No matter how many times you set the configurations in the network pane it does not establish a keychain, unless you do a diagnostic and check the box that says;"add password to keychain" then you add these apps to the access control tab"
after this post I tested it and the connection dropped during sleep so...
I had to delete all the plist files because it did not re-connect after I awoke the computer from sleep, so I threw away the system configuration folder, all airport plists files and the keychain, upon restarting the keychain showed the files I was looking for which is the systemUIserver and the airport deamon, (in the keychain lists as: airport) I added the System prefs and the apple80211agent. I think this stabilizes yet again the network.
 

Attachments

  • one.jpg
    one.jpg
    31.8 KB · Views: 92
I was pulling my hair out there for a few days, but the 10.5.2 update solved the problem completely. I was this close to downgrading back to Tiger... I actually put the disk in the slot but canceled out of installation.

I kept thinking of those Mac vs. PC commercials where they claim PC users were "downgrading" back to XP due to problems with Vista...
 
perhaps another fix:

Create a new keychain.

i've just done this and it seems to have stabilized my connection.

I think the problem must lie within the keychain somewhere. Either time machine is corrupting the keychain, or there is a conflict within the keychain somewhere that seems to mess up the airport.

Jesus! You'd think by now between us we'd have found some hard and fast way of sorting this out wouldn't you! I hope apple are looking at this and trying all the things we're suggesting and bolting down a proper fix into 10.5.3!
 
fluidedge said:
Jesus! You'd think by now between us we'd have found some hard and fast way of sorting this out wouldn't you! I hope apple are looking at this and trying all the things we're suggesting and bolting down a proper fix into 10.5.3!
Click to expand...

I think it's time I sent Apple links to this thread and the various other Mac Rumors threads devoted to wireless problems with 10.5.1 and 10.5.2. Either that or it's time for a mass online petition ... what do you think?
 
inconsistent

Im running 10.5.2. and I was having this problem before the latest update. The wireless connection problems are happening on different routers and networks both open and closed.

Somehow I am able to consistently use firefox and IE in Parallels with XPSP2. If I have signal strength of any amount it works brilliantly on the XP side.

I have been through the available channels and posts on this thread and sometimes it helps for a few hours/days. After almost resigning to have to use XP for wireless I thought I would restart my MB. Now both operating system's browsers work.

Sometimes using network utility works... although at a rate that might as well be inconsistent.

Right now I am writing this from safari 10.5.2. all four browsers I have are connected (safari, firefox, and IE and firefox on xp).

I have reset routers, passwords, erased caches, keychain information, done some terminal commands (thank you Mlobo01) and now after two hours without connectivity through 10.5.2, I am suddenly on after a restart with Option/Command pr. Now I am on very solid as it usually is when I finally get online.

There should be a fix here soon. Thank you all for your help, time and energy.
 
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