Currently we run this environment:
1xCisco Wireless LAN Controller V220.127.116.11
1xCisco ACS V18.104.22.168
2xAIR-AP1231G-A-K9 (used for testing; I'm waiting to move to 5xCisco APs when I sort this issue out)
Windows 2003 R2 Domain - the DC has the Cisco ACS client installed
Client machines are Windows XP SP2 on Intel ProWireless NICs (Including Patches: WindowsXP-KB917021-v3-x86-ENU.exe; WindowsXP-KB893357-v2-x86-ENU.exe; WindowsXP-KB885453-x86-enu.exe)
We're securing the WiFi using: MAC Filtering[WPA][Auth(802.1X + CCKM)] - so PEAP on the WinXP clients w/MSCHAPv2 where ACS which does the Radius authentication for us.
Our current Wireless network uses autonomous APs, so I'm moving to LWAPP APs to improve roaming etc etc. We experience the same problems on the autonomous APs as well.
All clients authenticate the first time perfectly, no problems with that and obvisouly I can see the authentication take place on ACS and WLC. However, after a certain amount of time the clients will remain connected to the network but will sit âAttempting to Authenticateâ and this never clears until I disable/enable the NIC - note the clients stay connected even though they site Attempting to Authenticate.
I understand this is a problem with WindowsXP SP2 and using a non-Microsoft Radius - but I've applied all the KBs mentioned on various forums and I still get the same problem. Am I doomed to have these issues unresolved?