Xp stuck on validating identity accomodating party

Rated 4.9/5 based on 917 customer reviews

We also start logging cisco APs - RADIUS authenticator and in logs are some errors regarding to our problem.

the error says: Client 0016.6f5b.e5b5 failed: Timeout waiting for client EAP auth response Jan 18 .127: dot11_auth_dot1x_send_client_fail: Authentication failed for 0016.6f5b.e5b5 Jan 18 .127: dot11_auth_send_msg: sending data to requestor status 0 Jan 18 .127: dot11_auth_send_msg: client FAILED to authenticate If we use 3rd party supplicant e.g. We have found that in Microsoft Windows XP SP2 supplicant is a problem with PEAP but only if RADIUS server is Cisco or another 3rd party RADIUS server (KB885453) but we have Microsoft Radius server so it seems this is not our case.

Click on Properties once you select the wireless network that is having problems.

Click on the Authentication tab and now uncheck the Enable IEEE 802.1x authentication for this network box.

You just have to find the common setting between the two devices.

This article assumes background knowledge in IEEE 802.11 wireless LAN and associated security technologies and the components of a Windows-based authentication infrastructure.

On a couple of occasions I've seen that particular AP (don't know what firmware) suddenly stop attempting to authnenticate clients (it never sends any RADIUS requests) and power-cycling the AP "fixes" the issue.

If you have the Dell WLAN Utility controlling the connection, uncheck the 'Let this tool manage your wireless connections' box on its Wireless Networks tab, click Apply (you will lose the computer's wireless connection at that point), then OK.

Now open the windows wireless manager (My Network Places, View Network Connections, select the Dell wireless adapter, then click View available wireless networks), select the proper AP from the list, click Connect and configure the connection.

My system picks it up automatically and windows is managing my wireless called Intel Proset Wireless, however just after it connects it drops the connection.

I have never encountered this with other wireless connections for which I have the password.

Leave a Reply