• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Cisco WLAN controller & EAP problems

  • Thread starter Thread starter Deleted member 174149
  • Start date Start date
D

Deleted member 174149

Let me preface this by saying I'm not a wireless guru by any means.

I have a Cisco WLAN Controller (model 4402) along with a handful of LWAPs. This is a little development testing network that we use for embedded products that rely on WEP or WPA-PSK authentication, and has been used happily for this purpose for a while now. I'm trying to expand the role of this network to actually let developers connect their laptops to the development network, and I want user authentication instead of just a generic key that everyone uses.

I have configured some users in the local user database, configured the Local EAP profile to use the internal Cisco certificate, then created an SSID using WPA-AES, and set the AAA Services to use Local EAP Authentication.

This is all documented in Cisco's guide on how to configure local authentication:
http://www.cisco.com/en/US/docs/wireless/controller/5.1/configuration/guide/c51sol.html#wp1172157

Unfortunately, I can't connect either Windows or iOS devices to the network. Windows doesn't prompt for a username or password, and pops up the error, "Windows was unable to find a certificate to log you on to the network <SSID>." iOS devices give me the helpful message "Unable to Connect." Android devices connect fine.

I assume this is a certificate problem, but I am not sure how to correct it. Google hasn't been helpful.

Any thoughts?
 
Go into the EAP settings of the client and deselect "verify server certificate". The client doesn't trust the cert and it's not publically signed.
 
I actually tried that (should have put it in the OP, sorry).

The iOS devices are now functioning with a LEAP profile, but same result with the laptops - unable to find a certificate.
 
Ah hah!

Amazing the stupid, simple things we overlook. PEAP has to be manually selected in the wireless properties of the WLAN on the laptops. Once you do that, it prompts you to enter credentials.

I had done that earlier, but the little error bubble was still popping up - only I didn't read it. It was prompting for credentials, not telling me there was no certificate. Grrrr...
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top