PEAP intermittent problem

Unanswered Question
Oct 7th, 2009
User Badges:


I am using PEAP with mschapv2 and authentication using ACS with AD.

The client is winXP/SP2. I am using windows configuration to configure the wireless setup in XP.

The client can connect to the network via wireless. But after i disconnect and try to connect again, connection will fail. I couldn't see any logs in the ACS.

THe next day i try to connect again, it worked. After disconnect, it did not work again.

Any one has encountered such problem b4?


Eng Wee

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

Can you give us some more detail?

What sort of messages is the client displaying, and what do you mean by "fail" (no IP address? what?)

What sort of messages are you seeing on the wireless controller or AP?

If everything is working fine for other clients/users (ruling out the wireless network itself), the only time I have seen problems with WZC is due to older wireless card drivers and not applying the wireless client updates from Microsoft ( If you are using an Intel card, driver updates are a must.

e-chuah Wed, 10/14/2009 - 18:19
User Badges:

Hi Robert,

thanks for the reply.

At the client, it got stucked at

"Pls wait while windows connect to the EMPLOYEE network, waiting for the network"

At the controller, i turn on debug and could not any related debug message.

When the client is able to connect successfully, i do see debug messages appearing at the controller.


Eng Wee


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