PEAP authentication failed

Hi,
With reference to your posting regarding the Authication failure on 1242AG, I was just wondering if you had any luck with it because I'm facing exactly the same problem and have had no luck in finding a solution. Any tips would be highly appreciated.

Thanks,

Juzar

I need more than just authentication failed from you. What is your setup like? DHCP? any other routers in between the wireless and the Radius server. If so, make sure the correct ports are open for authentication and accounting. or is it a direct connection to the server?
are you broadcasting the SSID? Are you using a certificate? If so is it installed on the client computers? There are many reasons for authentication errors.

Thank you for your response.
Intentions are to use a CA certificate for PEAP authentication. Following is what I have done so far:
1) Installed Microsoft CA
2) Created root/server certificates
3) Ensured that the certificates are replicated to my servers (Domain Controllers)
4) Installed IAS on my DCs
5) Configured a profile to use PEAP as the authentication.
6) Added the Cisco AP in IAS to act as a Radius Client.
7) Configured the "Radius Server" on my Cisco 1241 Access point (setup shared secret, etc.)
8) Ensured that the certificates are deployed to the workstations.

The above configuration has been done to establish wireless connectivity for a wireless client.

Additionally:
1) SSID is not broadcasted
2) There are no routers between the AP and the Radius Server.
3) DHCP is used for the client PCs

Thank you once again for your time and assistance.

Juzar Zaveri

Believe it or not. My setup would not work either untill i broadcasted the ssid on the ap. I dont realy care about broadcasting the ssid because it does not pose a security risk. And it if you hide it, it can still be sniffed out by software so it does not matter. That might just do it.
Good luck. By the way, did you configure a Wifi policy for your environment. Not that it's mandatory but it makes it easy to deploy to clients on the domain. Make sure windows in managing the wifi on the computer and not third party software.
Dont overlook the obviouse, make sure wireless zero config service in turned on.

Good luck.
Leo

And I bet you can do the same in the newer hardware. It takes a bit of time to configure, but on the screen where you setup logging, you can allocate memory to do packet capture, then do a total sniffer-like packet capture in the AP.

This is invaluable when troubleshooting authentication problems. I used it years ago to show an (arrogant) server admin that the FTP problem was HIS server being misconfigured, not my WLAN APs.