Mac cannot find WPA-2 enterprise wifi when updated to Mavericks

Yeah, I found it by googling around... Here are a few useful commands you can type into Terminal:

NOTE: The forum seems to break the word "airport" between the "air" and "port" when copy/pasting. Be sure to remove the unwanted " " before pressing Return.

Get info on the currently-connected SSID (that's an upper-case "I" ("eye")):

/System/Library/PrivateFrameworks/Apple80211.framework/Versions/A/Resources/air port -I

Scan all the available networks:

/System/Library/PrivateFrameworks/Apple80211.framework/Versions/A/Resources/airp ort -s

Get all the options of the 'airport' command:

/System/Library/PrivateFrameworks/Apple80211.framework/Versions/A/Resources/air port -h

Hello sablesg. Yes, you're right, I'M NOT using WPA-2 Enterprise. I thought that other threads on the same topic indicated that this might be a broader issue than that. Sorry for the delay in replying; I've been preoccupied with my own Maverick troubles—USB misbehaviour.

Michael

What USB accessory are you using ?

What Mac hardware are you guys seeing the issue on ? My Macbook Air and Macbook Pro Retina seem to work perfectly with enterprise networks.

You guys can also try deleting the Keychain entry for the WPA2 Enterprise network, re-join the network and then see if the issue still occurs. I remember that helping me in the past for some weird issue.

Experiencing the same issue (have to manually reconnect to the network every time the computer resumes/boots). The network is run by my university using WPA2-Enterprise authentication. This did not happen before Mavericks, it is definitely a 10.9 software bug (and a quite annoying one too).

Anyone submitted a bug report? How did you explain it properly?

Update to this thread: Apple does listen/read these forums. I just got a call (at home, on a Saturday afternoon) from a very smart Apple Support tech who wanted to know all about the troubles I had experienced. He sent me a slick tool for collecting log files, OS and machine configuration, etc and I submitted those.

He also said that they really want to hear about these problems. They need to know what stuff is happening, and that you should call Apple Support (800-275-2273) since you definitely have the 90-day free support on your new (Mavericks/10.9) software.

Huh. That's weird.. It suddenly now "just works". I don't see any recent system updates, so I wonder if they quietly pushed out a fix (is that even possible on OS X?). In any case my Macbook now sees WPA-Enterprise networks, and connects to it automatically...

Anyone else experiencing the same thing?

I updated my Macbook Air from Mountain Lion to Mavericks during weekend. In Mountain Lion I had working configurations (certificates and all) provisioned for eduroam and few other WPA2 Enterprise networks. When I got back to work, my WPA2 Enterprise profiles did not work anymore. Airport command line tool sees the networks, but the laptop does not join to them nor does it list them in Wi-Fi networks list.

I am on one of the eduroam administration mailing lists and there I picked up that at least in some Wi-Fi networks, the problem occurs, when that Wi-Fi network sends Hotspot 2.0 information in its Wi-Fi network beacons. It seems that Mac OS X Mavericks does not know how to use those old profiles with these kind of Hotspot 2.0 networks or it expects the profiles to be configured somehow differently.

From network administration side a workaround may be to disable Hotspot 2.0 extension from the Wi-Fi network, but I think Apple is the one who should fix the compatibility of existing profiles in Mac OS X. The thing is that with iOS 7.0.3 those provisioned profiles work fine, but with Mavericks they do not.

That network administration workaround works. When I disabled Hotspot 2.0 from our company networks, my Macbook Air was able to find and join to those networks without problems.

I also got an email from an Apple rep. and I have responded to him about this.

For some reason I can now see the network and connect to it automatically, however, FaceTime no longer makes or receives calls (it signs in though). I am now wodnering whether this is due to this network issue. Sadly I have not been anywhere wihtout WPA2 Enterprise to test whether it works on normal networks and whether it is only WPA2 Enterprise issue.

How long does it take Apple to fix this bug? My goodness, I thought Apple has top talents for development. How can something that's so critical get overlooked and pass testing.

jackfhwong,

Can you get a sniffer trace of your wireless network and upload it someplace. I can take a look and see if there is something that I can help point out. Use Wireless Diagnositcs->Utilities->Frame Capture to get a sniffer capture.

I have uploaded a Wireless Diagnostics gz file to dropbox. Let me know how you want to access it.

Thanks

Jack

Also, I am able to get the Wirelss Diag, but not sure where to find Util and Frame Capture.