03-07-2006 07:29 AM - edited 07-04-2021 11:44 AM
I'm getting a very slow authentication time for users running the XP wireless client. If they user switches to the Intel client, Dell client or whatever more hardware specific wireless client they authenticate within a second or 2. I've downloaded the new XP PEAP update KB893357 without an improvement. This is the error that shows up during debug that is responsible for the delay. I cannot find a reference to this error on the Cisco site. Has anyone seen this before and/or formulated a fix? Thanks.
Feb 21 09:59:40: RADIUS(0000000B): Config NAS IP: 10.2.2.2
Feb 21 09:59:40: RADIUS(0000000B): Send Access-Request to 10.1.1.1:1645 id 1645/51, len 187
Feb 21 09:59:45: RADIUS: no sg in radius-timers: ctx 0xC97180 sg 0x0000
Feb 21 09:59:45: RADIUS: Retransmit to (10.1.1.1:1645,1646) for id 1645/51
Feb 21 09:59:51: RADIUS: no sg in radius-timers: ctx 0xC97180 sg 0x0000
Feb 21 09:59:51: RADIUS: Retransmit to (10.1.1.1:1645,1646) for id 1645/51
Feb 21 09:59:56: RADIUS: no sg in radius-timers: ctx 0xC97180 sg 0x0000
Feb 21 09:59:56: RADIUS: Retransmit to (10.1.1.1:1645,1646) for id 1645/51
Feb 21 10:00:01: RADIUS: no sg in radius-timers: ctx 0xC97180 sg 0x0000
Feb 21 10:00:01: RADIUS: Retransmit to (10.1.1.1:1645,1646) for id 1645/51
Feb 21 10:00:07: RADIUS: no sg in radius-timers: ctx 0xC97180 sg 0x0000
Feb 21 10:00:07: RADIUS: No response from (10.1.1.1:1645,1646) for id 1645/51
Feb 21 10:00:07: RADIUS/DECODE: parse response no app start; FAIL
Feb 21 10:00:07: RADIUS/DECODE: parse response; FAIL
03-07-2006 05:41 PM
What Radius server are you using? I use a Cisco ACS 3.3 and experience the exact same roaming issues with PEAP MsChap V2. I have Windows XP SP2 MS has a patch related to PEAP authenication issues with 3rd party Radius servers. I have not been successful in recieving the patch as of yet. KB Article Number(s): 885453
03-08-2006 05:24 AM
Are you getting the same errors? We're running the ACS server version 3.3 as well.
03-08-2006 06:16 AM
Where are you enabling logging. I will check my logs also. Im just experiencing the same type of issues with Windows XP.
03-08-2006 07:41 AM
I ran a couple debugs to see the process in action:
debug radius authentication
debug dot11 aaa authenticator process
debug dot11 aaa authenticator state-machine
These should show you the errors that are delaying/stopping the PEAP authentication process. The Radius debug is the one that shows the error I listed in my openning message.
Rick
03-17-2006 08:57 AM
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide