Windows XP built-in 802.1x supplicant problem

Unanswered Question
Oct 7th, 2009
User Badges:

Hi, we are deploying PEAP for wireless access, we had no problem to get this working with laptop vendor supplied wireless management software (which includes 802.1x supplicant), but when I switch to Windows Zero configuration and let Windows XP management wireless, the laptop can not associate with wireless SSIDs, back end Radius server (MS IAS) log shows that user (with AD credentials) is successfully authenticated, but Windows XP supplicant seems did not receive authentication successful response from Radius server, and keeps retrying and finally gives up. Any idea what is going on with Windows XP dot1x supplicant? Laptop is running XP SP3.

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Robert.N.Barrett_2 Wed, 10/14/2009 - 07:43
User Badges:
  • Bronze, 100 points or more

Windows XP has supported 802.1X on wireless via WZC for quite some time. With XP SP3 and current wireless drivers, you can easily do EAP-TLS or PEAP at the user and machine level without using a 3rd Party supplicant.

Robert.N.Barrett_2 Wed, 10/14/2009 - 08:09
User Badges:
  • Bronze, 100 points or more

Not exactly sure what could be the problem. It should be working - it's definitely supported (I'm currently typing this via a XP SP3 machine using PEAP WPA2/AES via WZC). The only things I can think of to check are:

- Make sure your wireless drivers are up to date *this is a must*

- Make sure the other supplicant is completely disabled (uninstall it if you really need to rule it out)

- Try disabling the server certificate check in the WZC profile for this network (do you know for sure that your laptop trusts the IAS server's certificate)?

- Are you doing machine or user authentication for PEAP - make sure you have the WZC profile properly configured

- Are you 100% sure that you've configured everything properly for the network (WPA vs WPA2? AES vs. TKIP? etc.)


This Discussion



Trending Topics: Other Wireless Mobility

client could not be authenticated
Network Analysis Module (NAM) Products
Cisco 6500 nam
reason 440 driver failure
Cisco password cracker
Cisco Wireless mode