Issues connecting to 802.1X Enterprise Wireless on OS X Maverick

Question

Level 1

8 points

Issues connecting to 802.1X Enterprise Wireless on OS X Maverick

Hi,

I am trying to connect my Macbook Air to the office wireless. The office Wireless uses 802.1X authentication using certificates WPA2 Enterprise. We have deployed Microsoft AD-NPS as the RADIUS Server with certificates being issued by Microsoft AD-CS infrastructure.

I tried the following steps to connect my Macbook to the environment.

1. Exported an 802.1X certificate from a windows machine with the key's .

2. Clicked "Join Other Network" link on the WiFi symbol.

3. Added the network SSID

4. Selected WPA2 Enterprise in the Security Options drop down.

5. Selected EAP-TLS mode in the Mode drop down.

6. In Username added the windows machine name

I get the following error in the console windows

"3/07/2014 11:46:10.864 am eapolclient[5997]: [EAPCertificateUtil.c:325] EAPSecIdentityCreateCertificateTrustChain(): SecTrustGetCertificateCount returned 0"

The same certificate has successfully been used with the same network settings to connect an iPhone, Android Samsung Note to the network without any issues.

I have also added the Root Certificate and the RADIUS server certificates to the Systems Keychain on the Mac.

Any suggestions on how I can fix this ?

- Ashish

Posted on Jul 2, 2014 7:46 PM

Reply

Answer 1

Jul 2, 2014 9:16 PM in response to ashishol

What version of the Mac OS? (is it fully up-to-date?)

I've been joining 802.1X PEAP (MSCHAPv2) networks without any issues ever since 10.6 was released.

The only differences:

Not using AD (Elektron and Meraki Radius)

Network broadcast is visible.
Accepting the certificate is part of the connection process.

I have not seen your error before, so I'm not sure where to start in troubleshooting other than Google.

What happens if you change between EAP/PEAP?

Reply

Answer 2

ashishol Author

Level 1

8 points

Jul 2, 2014 11:46 PM in response to chattphotos

Hi Using Mac OS X Maverick (And its fully up to date).

Changing over to anything else gives me the same error.

Tried goggling but could not find anything on the error yet.

Reply

Answer 3

Jul 3, 2014 12:20 PM in response to ashishol

Call on Microsoft, see if they have any troubleshooting tips.

Have you deleted the wifi networks and certificates and tried to create the connection again?

What happens if you load the pre-configured wifi profile? (use your favorite MDM or profile manager to install)

I've modeled the configuration option set to what you've mentioned using Meraki's MDM.

Reply