Benches macOS

15

Leopard problems connecting to WPA secure…

apple Verified

Imported from the Apple Support Forums via the Wayback Machine 🔗

i have been reading through a lot of posts here related to wifi issues with leopard and there seem to be several different issues all getting mashed into a few threads.

the issue that i am having is not a "connection reliability" issue. it is specifically related to connecting via my airport extreme to a WPA secured wifi router. this same hardware connected to that router seamlessly under tiger. after a [clean] upgrade to leopard, i can no longer connect to that router via either the menubar airport icon, or the standard network system preference pane.

the router is seen and appears with a lock. leopard knows that it is WPA. i key in the password and it tries to connect and then comes back with the message "Connection Failed".

HOWEVER, if i open safari and click on its "Network Diagnostics" button (or just open the network diagnostics app from system/library/coreservices) and run through the screens there, picking my router out of the list of signals it sees, then it connects successfully. every time.

i don't get dropped connections or poor performance. the only issue is that when the machine boots up (or if i turn off the airport for any reason), it will not connect unless i manually go through the network diagnostics application.

which is kind of a pain in the butt.

in case this helps anyone figure out what the issue is, here are a few relevant lines from the console that appeared concurrent with the "Connection Failure" message:

Nov 3 22:10:06 skyclad airportd[503]: Error: Apple80211Associate() failed -4

Nov 3 22:10:06 skyclad Apple80211Agent[506]: Error: airportd MIG failed = -4 ((null)) (port = 22787)

Nov 3 22:10:06 skyclad Apple80211Agent[506]: Error joining pjv: Connection failed (-4 result unavailable)

15 replies

Sign in or join Beachball Help to reply.

  1. 0

    ABCDENTAL

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    Hi there,

    I got the same problem. I have been trying to call support but I did not got thru so far.

    I'll let you know if they can help me.

    Good luck

  2. 0

    dj640

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    When you go thru network diagnostics , does it bring up a user password window? does it have

    a button that says "Always Allow"? if so , click that button.

    Go to login keychain (user/library/keychain), unlock the login lock (top left side) next,

    double-click the wireless name keychain,

    go to Access Control, click the "confirm before..." button, hit the + at bottom of window, add the

    applications (safari, mail, ichat, network diag.., ect....) that you need to access the wireless network, save changes, enter password.

    leave the login lock unlocked on the first page.

    hope this helps

    dj

  3. 0

    psub

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    thanks for the effort dj, but this didn't work.

    when i go through network diagnostics, it doesn't ask me for a password, so it is clearly seeing the password that already exists in my keychain.

    just to be sure, i just went in to the keychain and deleted the airport key from both my login chain and the system chain and then went through network diagnostics again. this time there was a password field and a "remember this password" checkbox. i put in the password, checked the remember box and it connected fine. then turned off airport and turned it back on and it still won't connect from the airport menubar icon or automatically as a "preferred" network. then connects through network diagnostics again without prompting me for a password.

  4. 0

    paul_andrews

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    Thank you! We had a Macbook running Leopard here and while it attached to "normal" networks when trying to attach to a Ascii 128 bit passworded network, it just failed. The fix (via Safari) woked first time. Nice one.

  5. 0

    psub

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    please note, paul (and APPLE!!!), that i don't consider this a fix, but only a pain in the butt work-around. having to go through a bunch of manual steps to get connected to the network every time the computer is turned on S U C K S.

  6. 0

    psub

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    short-term
    SOLUTION:

    I found this fix on another site.

    you can use a terminal command to do what the network diagnostics app is doing a lot faster and since a command like that can be called by other processes, it can happen automagically when you log in. you need to be a little proficient with terminal and unix commands and i can't do a tutorial on that here.

    here are the details:

    open up a terminal and type in:

    sudo chmod +s /usr/sbin/networksetup

    sudo nano /etc/rc.local

    networksetup -setairportnetwork "yournetwork" "yourpassword"

    ctrl-W (saves the file)

    ctrl-X (exits from the nano editor)

    be sure to substitute in your actual network name and password.

    this is obviously not a good long-term solution since it puts your network password in cleartext in a file on your disk. but it is working for me until apple presumably releases a fix in 10.5.1. at that point, i will just delete the file /etc.rc.local.

    thanks to chipsxd and cirrus

    Message was edited by: psub

  7. 0

    Paul Craton

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    Same problem here - with try the short term fix - can anyone in Aplle put their hand up and let us know this bug is being worked...?

  8. 0

    Paul Craton

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    Guys - fixed the problem on my machine. I am using WEP and connecting to a netgear router. The netgear router had a setting for the way the encryption/authentication handshake is done... netgear called it eiher "open" or "auto" and by default it was set to "auto". Setting it to "open", reducing the speed support to only support b+g (11Mbps and 54Mbps), reinstalling the keychain login fix and rebooting to safe mode (which I think clears/resets all the caches) has left the machine working correctly with none of the wierd what I would now call "post error" symptoms that showed up after the machine had the problem. I'd suggest looking at the wireless router config to look at non-standard ways it might be supporting the authentication handshake. Take everything back to as standards implemented way you can then see if it resolves it.

    Here's the post that fixed it for me...

    "I had the same problem getting 'connection timeout' using a Netgear 834 Router & managed to sort it !

    Try logging in to the web interface for the router, going to the wireless settings page & just above the encryption details area, there is a drop down box that has the options of 'automatic' & 'open system'. It defaults to auto, so try changing it to 'open system', then click 'apply' & hopefully it should all be working!"

    Best of luck.

    Paul

  9. 0

    psub

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    thanks for the followup paul, but that fix doesn't work for my particular issue. i had already tried messing with many parameters in my router, but when i read this, i tried again. no go. also, i don't get a "connection timeout" error message. i get a "connection failed" error message, so i think we may be seeing two similar but different issues. i am also trying to connect to a WPA secured network, not WEP.

  10. 0

    sapzolls

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    I had similar observations ... I opened the Keychain Access from Utilities and ran a verify . I got some errors with the login.keychain file (may be correct name!!) and after Repair on the keychain, my WPA issue was resolved

  11. 0

    sensibilita

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    I have a secured LinkSys Router (DI-524)(and a Motorola modem); I tried most of the tips given here (especially the Unix command line stuff), but my network connection decays very fast: maybe 3 minutes is the longest time I've been on. If I leave it alone, it comes up again from time to time (I hear my Skype contacts coming online).

    I am typing this on my DELL notebook; no network access problems -- and for both MacBook and Inspiron DELL, the router is about 15 metres away, located in my lounge-room.

    When will Apple fix this nuisance?

  12. 0

    bigj6360

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    Hi psub,

    I am having the exact (almost) same problem, but I can go a step further. I cannot even connect manually through the network diagnostics. Do you broadcast your ssid? I don't... may be that's my problem with manual.

    Here is my more detailed information:

    Error: Apple80211Associate() Failed -7

    Error: airportd MIG Failed = -7 ((null)) (port = 59651)

    Error joining mynetwork: connection failed (-7 unspecified failure)

    I cannot edit the router settings because I am at work... and have to run an embarrassingly long 75ft ethernet cable to the nearest switch (the windows guys around me eat that up.)

    I was a clean install as well.

    Apple Please Help!

  13. 0

    psub

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    i don't know if this is the reason why the network diagnostics and the command-line solution works, but i do broadcast my SSID.

    fwiw, still the same issue after the 10.5.1 update...

  14. 0

    mlrvpl

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    Same problems in general here:

    -Mac mini Intel Duo, 1.66 GHz

    -Linksys Wireless router WRT54G running WPA encrpyption

    -Ran fine under 10.4, including surfing and Internet radio streaming under iTunes

    -Installed 10.5 and ran terrible (progressively slowing, dropping, reconnecting)

    -Installed 10.5.1 and it is somewhat better but still SLOW and occasionally drops

    I am actually an IT person and network literate, but I do enough of this stuff at work and I would expect a pretty vanilla wireless networking setup to run fine (or faster) with an .1 upgrade that I paid over a $100 for.

    Would really like to see another update tp fix all these problems Apple. Thanks

  15. 0

    bigj6360

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    sapzoll...

    Keychain repair does not display any issues, much less fix anything. In fact I went a step further and completely removed all references to this network and started from scratch multiple times, across multiple restarts. I have also checked all disk permissions as well. No-go. Thanks for the suggestion though.

    Mirvpl...

    I think you may have pointed a common thread here. Linksys WRT54g... at least between both of us, except I get the connection failed response from the network assistant, rather than a limited connection. We are running firmware version 4.21.1 (Apple are you seeing this? Can you reproduce it? There seems to be some sort of common thread here.)

    Hey psub...

    Are you running on a linksys router? maybe even a wrt54g?

    At home I have a Netgear running WPA, unbroadcasted SSID, and have no issues, well almost none. Sometimes after the computer has been to sleep it will not reconnect, and I have to manually go up to the airport menu and re select it.

    Maybe it is a conflict between airport drivers and Linksys specific network calls.

    Apple...

    If you need more information concerning settings on the router say so. Lets work on this to get it fixed. I know I am willing to do some testing on it if you just ask me. I can also tell you the the other 5 macs (tiger.11) and 2 XP machines in the office do not exhibit any of these failures.

    -Me