hey all
I have been testing a PEAP deployment for the past couple of weeks and have an unusual error that is stopping me in my tracks. I have 4 test machines - all Dell laptops beside the test AP. The test AP runs 2 different SSIDS on different vlans - one is for external and works fine using WPA auth - and one is for internal using PEAP back to our Cisco ACS 4.2 server. The problem is that 2 of them machines work fine with the Windows client to PEAP and get internal addresses without issue on authentication with ACS. Both of these machines are XP SP3.
The other 2 are XP SP2 but will not connect using the Windows client. On associating with the WAP, the ACS failed attempts log shows the following error:
EAP-TLS or PEAP authentication failed during SSL handshake
Apparently MS have released a hotfix for PEAP issues which i applied. The 2 laptops still give the same error on trying to connect. I upgraded them to SP3 and they still give the same problem.
The bizarre thing is that regardless of SP or hotfix, if I use the Intel Proset wireless manager instead of the Windows wireless manager, both machines connect to PEAP every time.
Both are configured exactly the same as the 2 working Windows machines and as this is going to be rolled out live in a global policy - I am not confident of it working considering i have 2 machines that don't like it.
Has anyone encountered any strange issues with PEAP and Windows wireless like this or have any suggestions on how I can try to resolve this? I am pretty confident the problem is individually with these laptops and not with the Cisco AP or Cisco ACS as I don't have any issues with the AP or ACS on different clients.
Would be v grateful for help on this one!
cheers
Start Free Trial
