topic Re: Client Authentication Failed in Wireless

Client Authentication Failed

jbracho61292 — Sun, 04 Jul 2021 18:24:41 GMT

My wireless system was working fine until a week and a half ago. I am getting the clients MAC address and Authentication Failed error message in the log

(1 Dec 12 14:46:38.101 GMT Debugging Station 000c.ce93.3ac4 Authentication failed)

I ran the clients Troubleshooting utility and get the following report;

Atheros Troubleshooting Utility

Troubleshooter report...

Report date: Monday, December 12, 2005

Name: Driver installation test

Description: This test is to check the radio driver installation.

The radio's registry keys are OK.

Nic name. . . . . . . . . : HP WLAN 802.11a/b/g W500

Driver name . . . . . . . : WLAN_400_500_SERVICE

Driver path . . . . . . . : C:\WINDOWS\System32\DRIVERS\ar5211.sys

Driver version. . . . . . : 3.1.1.54

Active Profile Name . . : DAIROAMER

Test Done: The radio driver has been installed.

Name: Card insertion test

Description: This test is to check the radio insertion.

Test Done: The radio has been inserted.

Name: Card enable test

Description: This test is to check if the radio/driver is enabled.

Test Done: The radio has been enabled.

Name: Radio test

Description: This test is to check if the radio is turned on.

Test Done: Your radio is turned on.

Name: Association test

Description: This test is to check your client adapter's association to an access point.

Link Status . . . . . . . : Associated

AP Name . . . . . . . . . : Dopey

AP IP Address . . . . . . : 10.0.0.9

Test Done: Test passed

Name: Authentication test

Description: This test is to check authentication.

Link Status . . . . . . . : Authenticating...

Authentication type . . . : PEAP (EAP-MSCHAP V2)

Encryption type . . . . . :

WEP Enabled . . . . . . . : No

Test not started.

Name: Network test

Description: This test is to check your network settings.

Your IP address: 0.0.0.0.

Test Failure: You have not configured your computer to use the client adapter.

Solution: Your IP address: 0.0.0.0. Try to renew the IP address.

Test completed.

Has anyone seen anything like this??? or point me to the right direction....

Re: Client Authentication Failed

will.shaw — Tue, 13 Dec 2005 08:26:36 GMT

Is this affecting all your clients, or just a select few? What are you using to authenticate against?

Re: Client Authentication Failed

jbracho61292 — Tue, 13 Dec 2005 14:53:37 GMT

It is affecting all my clients. We are using certificates to authenticate against. All clients have received the certificate from our authenticating server. However, if you see my previous e-mail the clients are being authenticated in the AP. But, once the communication between the AP and the Server suppose to start it is not happening, and IP addresses are not assigned.

Name: Authentication test

Description: This test is to check authentication.

Link Status . . . . . . . : Authenticating...

Authentication type . . . : PEAP (EAP-MSCHAP V2)

Encryption type . . . . . :

WEP Enabled . . . . . . . : No

Test not started.

Name: Network test

Description: This test is to check your network settings.

Your IP address: 0.0.0.0.

Test Failure: You have not configured your computer to use the client adapter.

Solution: Your IP address: 0.0.0.0. Try to renew the IP address.

Sincerely,

Re: Client Authentication Failed

will.shaw — Tue, 13 Dec 2005 15:53:45 GMT

Are you authenticating against a AAA server? Are the certificates still valid, or is it possible they have expired? Also check the server certificate.

Re: Client Authentication Failed

jbracho61292 — Tue, 13 Dec 2005 18:24:17 GMT

Yes, we are authenticating to a AAA server. All certificates are valid, including the server.

That's why is so pulseing.

Any other ideas???

Re: Client Authentication Failed

will.shaw — Wed, 14 Dec 2005 08:37:54 GMT

Try configuring one client to use just LEAP authentication to check that it works. It could be that your accesss point can't see the AAA server. Check if there are any 'failed attempts' logs on the ACS, and check you can ping the ACS from the console of the AP. Has anything changed which would cause the fault to occour, e.g. access lists changed, ip addresses changed, shared key changes, hostname of the ACS changed? anything like that around the time the fault surfaced.