Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Did the update - but problems remain: the password ist not being accepted when logging onto the the Airport Network.

In the attachment you'll find the dialog bbox stating: "incompatible security" after entering the password and clicking on join...


The Update *did* help find more networks, but did not solve the l/p issue.

i :( leopard

upps, forgot the attachment.
here it comes....

http://att.macrumors.com/attachment.php?attachmentid=89102&stc=1&d=1193564202

However if i go through the "Assist me -> Diagnostics" procedure the password will be taken in the dialog box below..

Then everthing works fine... until I have to log onto the network the next time. :(

http://att.macrumors.com/attachment.php?attachmentid=89104&stc=1&d=1193565254

I am also having the same problem after installing the keychain update. The weird thing is that it also caused me to be unable to connection to my Airport from Windows with Boot Camp. I don't know if that is just a coincidence that I had a problem with it in Windows, but it was working fine before the update.

For now I have turned off WPA on my network and that allows me to connect to it in both Leopard and XP.
 
How can Apple not even get the *** basics right?

I'm currently trying to switch from Windows to Mac and so far the experience sucks. I'm also suffering under the screwed AirPort bug, can't use AirTunes, don't see networks other than one even though about 20 should be available from where I'm at. Can't even bother to explore Leopard since I'm so frustrated by now.

I.D.I.O.T.S.
 
Airport

hi guys, the problem IS with the firmware & or software. I am using (like i said) my imac to spit wireless out for my laptops, and they constantly disconnect and have problems with ip resolving. also the network appears and disappears randomly :apple:
 
I think I have a worse problem!

I upgraded to Leopard, everything was ok - but I felt a fresh install would be better.

So tonight I backed up, erased, and installed Leopard from scratch on my intel iMac. (It's also running fine on my 12" PB).

During the install, I noticed that AirPort icon wouldn't pick up ANY networks (there's usually 4 or 5 - I live in a terraced house)

Obviously something from Tiger helped when upgrading - as there were no Airport problems to mention, but having done a fresh install my airport is not working at all.

As I say, everything's fine on the PB, but on the iMac there's no airport at all. I've got my PB tethered to my iMac doing internet connection sharing which is a real PITA!!

Anyone come across any fixes yet?

Update: Having browsed Apple Discussions I looked at Safari's "Network Diagnostics" weird thing is that ALL the networks show in that list:

1801623233_93ccbb1b10.jpg
 
ok, amazingly that keychain update seems to have done the trick.

this is, however, a complete pain - as it means any time I want to do a fresh install on my iMac again, I will need to have that update handy...

Anyway, good luck to you all :)
 
I too had problems with my airport extreme and two airport express.
my whole network was down, including my xbox live. As soon as I upgraded to Leopard, it would not recognized the two airport express. so what I did was I did a hard reset on all airports and I used my ibook wich had tiger on it to set them all. now everything is back to normal. I will not change any settings in leopard until the next update. hopefully the next update will fix all this.
 
i'm suddenly having the same issue after using leopard for 3 days with no issues. i suddenly had my airport connection randomly disconnect and none of my computers can see my network? i even reset it. i can't believe apple doesn't have 24 hr support.
 
ok.. some more news as far as I'm concerned, and it might help some of you :

If I modify the authentification encryption of my AP from wpa2 to wep 128 bits, there is no more disconnexion issue.
So I guess somehow the keychain update borked the wpa2 identification
Are all of you who faces problems using wpa2 ?
 
ok.. some more news as far as I'm concerned, and it might help some of you :

If I modify the authentification encryption of my AP from wpa2 to wep 128 bits, there is no more disconnexion issue.
So I guess somehow the keychain update borked the wpa2 identification
Are all of you who faces problems using wpa2 ?

For me, running wpa2 is a little bit unstable, but it works fine.

However, your suggestion wouldn't solve the problem of not seeing available networks more than the one you're currently connected to, would it?

My main issues are:

1) I can't switch between networks and
2) iTunes wont detect my AirPort Express

The problem started before installing the keychain update and the update doesn't fix the problem. I've been trying to uninstall Airport and reinstalling, actually I've tried altering most settings but nothing does the trick.

Waiting for a patch...

Until then, any information concerning this issue would be very helpful.
 
For me, running wpa2 is a little bit unstable, but it works fine.

However, your suggestion wouldn't solve the problem of not seeing available networks more than the one you're currently connected to, would it?

My main issues are:

1) I can't switch between networks and
2) iTunes wont detect my AirPort Express

The problem started before installing the keychain update and the update doesn't fix the problem. I've been trying to uninstall Airport and reinstalling, actually I've tried altering most settings but nothing does the trick.

Waiting for a patch...

Until then, any information concerning this issue would be very helpful.

is your airport express configured to your main network, mine isn't because i reset it, but it is such a pain to reconfigure, none of my computers can even detect it, and one is hard connected. i'm calling apple now and i'm gonna complain that they make this so hard.
 
annoyingly, the networks flicker up if I randomly decide to surprise my airport by clicking on it, but then disappear again, and I can't find them.
I can get to them through network diagnostics, and the "assist me" thing, or by manually typing the name of the network ++ it's pwd.

but this is happening with all networks, wpa, wep and unsecured ones, and it's beginning to really piss me off...
I went and deleted that outdated driver from the apple discussion, nope, installed the keychain update, nope, restarted, nope... nothing works, I even reset all the routers in my house (2).
My routers are a Netgear DG834G and a BTBusinessHub...
anyway, this is starting to annoy and I'm contemplating a clean install, which would just be another annoyance to add to the list.
If anyone's found some solutions, please tell us!!!
 
annoyingly, the networks flicker up if I randomly decide to surprise my airport by clicking on it, but then disappear again, and I can't find them.
I can get to them through network diagnostics, and the "assist me" thing, or by manually typing the name of the network ++ it's pwd.

but this is happening with all networks, wpa, wep and unsecured ones, and it's beginning to really piss me off...
I went and deleted that outdated driver from the apple discussion, nope, installed the keychain update, nope, restarted, nope... nothing works, I even reset all the routers in my house (2).
My routers are a Netgear DG834G and a BTBusinessHub...
anyway, this is starting to annoy and I'm contemplating a clean install, which would just be another annoyance to add to the list.
If anyone's found some solutions, please tell us!!!

I'm pretty sure the only way to work around the problem at this point would be re-installing Tiger. I can't see how the problem would be router-related. And yes, Leopard developers suck big time.
 
I'm pretty sure the only way to work around the problem at this point would be re-installing Tiger. I can't see how the problem would be router-related. And yes, Leopard developers suck big time.

I'm not going to clean install Tiger, I meant clean reinstall Leopard...
it has annoyed me though, I mean I re-updated my router firmware just in case, but no... nothing really works and this is a major problem (well, not major, just bloody inconvenient).
 
I did a clean install of Leopard on a new hard drive for my MB on Friday, which for me too broke the wireless connection. Neither Leopard nor Windows XP (Bootcamp) on the MB would connect to the network. My Mac mini with Tiger on it still connects to the same network without a problem. Like xerox123 I'm using a Belkin F5D7132 802.11g access point... The keychain update seemed to fix the problem briefly on Saturday, but after an hour or so it was back to not accepting the WPA password and losing connection. The MB would connect to our open wireless network at work without a problem. Unfortunately, I'm living in College accommodation and required to have WPA set on my access point, so can't change that.
At the moment I've swapped the hard drives and am mainly running Tiger again on the MB - no problem with the wireless network. Leopard lives on a separate hard drive in a USB caddy, and I booted into it and played around with it for a while yesterday - switched off IPv6 for the airport connection, noticed that the WINS tab for the Airport connection listed a Netbios name that looked like a mac address (the first few digits were the same as the airport mac address, but the last ones weren't). Oddly, my iMac at work (which also runs Leopard) shows DHCP in the same place, and I definitely didn't specifically configure the MB differently (I wonder whether it's something to do with the iMac not having a bootcamp partition). Went into the access point configuration and added that number to the allowed Mac addresses. Resaved the other settings on the access point (WPA password etc) without changing them. I don't know what did it, but the Airport connection worked after that for the rest of yesterday without a problem. Will try again later today whether it lasts, and if it works under Windows as well, and report back.
 
I'm experiencing the same problems.
At home I have my Airport Extreme and could connect without problems.
Here at work, my airport in my MBP disconnects every 2 seconds.
A strange thing is that connecting to a server actually changes my hostname of my laptop. It takes the hostname of my provider.
My system.log gives me more information.
It appears the requested IPv4 address cannot be assigned (setsockopt).
I'll dig some more later.
I hope this will get patched soon.


Exactly the same here.

Airport connects, deconnects all the time. Makes my wifi unusable.
Did both a 'achive and install' and now a fresh installation... nothing works.
Hoping for a patch very very fast.
 
I did the startup in safe mode and then restart normally and it did the trick for me.

Why? I don't know, but it's working. Airport now remembers preferred networks, yeah! :) :)

BTW Apple support sucks and Leopard is really buggy.
 
Troubleshooting "Incompatible security" (WEP, AirPort, wireless network, Leopard)

Through a lot of luck, I found a solution to the inability of Leopard to find my AirPort base station when awakened. The crucial bit of knowledge is that the WEP Password needed in the Password box in the dialog box titled "None of your preferred networks are available" has to be in hexadecimal format not plain text.

Unfortunately, the only process I found to read the hex key from the AirPort base station requires the AirPort Admin Utility found on a Tiger Mac. For what it is worth, here is the process:

1. The first thing is to interrogate your AirPort base station for its base-16 (hexadecimal) WEP key. I used a Mac with Tiger (on either a wired or wireless network) to find the WEP password in hex. I can’t figure out how to find it from a Leopard Mac.

2. In the Tiger machine: In the Utilities folder, find and double click on AirPort Admin Utility.

3. A window should open titled: “Select Base Station”. I have just one AirPort so only its name and its IP Address were the only entry in the list.

4. Double click on the line for your base station.

5. A new window should open. Its title should be the name of your AirPort base station.

6. At the top of the window should be four active and one grayed icons.

7. Click on the padlock icon labeled “Password”.

8. A small interior window will roll down from the top bar of the window.

9. Ignore the entire paragraph in the roll-down window beginning with “To connect…”. The crucial information is in the line that reads something like:

Hex equivalent password (WEP key): 4771B4DF54

10. “4771B4DF54” is the hex key for my AirPort. My clear text password is 5 characters, so my hex key was 10 hex digits. The hex number for your password might be longer or shorter and will of course have different hex digits. But never mind the theory. Just carefully copy down the numerals and letters.

11. Now, click on the blue Okay button in the roll-down window and quit AirPort Admin Utility. You are through with your Tiger machine. Wake up your Leopard Mac.

12. It should complain, “None of your preferred networks are available.” The complaint window should include a list of detected networks. Scrolling if necessary, find the name of your network (i.e., name of your AirPort base station) in the list. Click on it.

13. New data entry boxes should appear below the list of networks.

If not checked, click the box beside “Remember this network
If not checked, click the box beside “Show password” so you see what you’re doing.

14. We are almost done. First type a dollar sign ($) in the Password box. Then, right after the $, carefully type the numerals and letters from Step 10. In my case, I typed “$4771B4DF54”

15. Double check your typing.

16. Click the Join button and you are done! From now on, your Leopard Mac will automatically join your AirPort network whenever you awaken it.

Note 1: I don’t know how to find the hexadecimal WEP key for your Air Port without a Tiger Mac. Maybe someone else knows.

Note 2: Some say that WEP security protection is worthless. That is not true. It effectively keeps neighbors from easily piggybacking on your Internet connection.

Note 3: There are two places in Leopard which ask for a WEP password. Each has a different format requirement. The above process involves your password in hexadecimal format. The other, down the chain in the built-in "Network Diagnostics" process, requires your password in plaintext. The problem is that Leopard forgets the plaintext password every time it sleeps.

Fred
 
Problem Solved

Just got off the phone with Mac Tech Support.

Here's the fix:

1. Connect your Airport Express to the Mac via an ethernet cable (after a hard reset)
2. In Airport Utility, double click the AX icon
3. Select "wireless"
4. Change channel from "automatic" to 10 (auto always sets to 13)
5. Go through the other panes and untick any boxes that have "over WAN" in them.
6. Name your network
7. Create and enter a network password
8. Update settings
9. Click on airport icon in your menu bar, select your network
10. Open Safari and see if you're online.

The problem I'm told has to do with so many other things (phones, microwaves etc.) hogging Ch. 13 space. If you still have issues, try a a different channel until you find one that works.

Also, you don't really need to rename your Device (AX) just your network so it's recognizable.
Good luck out there.
 
I was having a problem with my network not showing up in the list, then it would show up, only to drop my connection about an hour later....over and over again. I did a reinstall of the Airport utility, trashed preferences....all that...nothing fixed it.

Oddly enough, the problem had something to do with Airport choosing what channel to use. When I went into the airport setup and specifically choose Channel 7 - all my problems were gone. Smooth sailing now. Apaprently, there was something in my area on the other channels that was causing interfearance?? Dunno really, but the fix worked.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.