topic Re: iPad AAA Authentication Failure in Wireless

iPad AAA Authentication Failure

jspobuk — Tue, 26 Apr 2022 03:03:23 GMT

Hello,

I setup a WLAN on a vWLC to not use any security, and the iPad can connect wirelessly to my network.

I changed the security to be WPA2+WPA3 using our existing RADIUS server, and now the iPad doesn't connect properly. The message I get in the vWLC trap log is:

"AAA Authentication Failure for Client MAC: XX:XX:XX:XX:XX:XX, Username:XXXXX, User Type:WLAN USER, Reason: Authentication failed"

There is a client listed on the vWLC Monitor page, and it is the right MAC address. However, the IP address is shown as 0.0.0.0 whereas the iPad has the IP address as a static entry.

The iPad shows a checkmark by the Wifi Network with privacy warning (i turned off private wifi address option)

I can't ping the iPad from the network side.

I can't go to webpages on iPad that I should be able to get to when on the network.

Network is isolated industrial network without internet access.

I setup iPad profile configuration with iPhone Configuration Utility, installed root certificate on iPad.

I don't see any Event Log events on the server hosting the RADIUS, not sure if i am looking in the right place? Looked at all Windows Logs and Server Role logs.

Sorry for the long post. Any help with any part of the process is appreciated.

Thank you,

John

Re: iPad AAA Authentication Failure

Mark Elsen — Tue, 26 Apr 2022 06:33:27 GMT

- What's in the radius-server authenticating logs for that particular authentication ?

Re: iPad AAA Authentication Failure

Flavio Miranda — Tue, 26 Apr 2022 09:45:00 GMT

Try to use only WPA2 instead WPA2+WPA3. Probably the client is not associanting the network due encryption problem and that´s why you are not seing authentication logs on radius server.

Re: iPad AAA Authentication Failure

jspobuk — Thu, 28 Apr 2022 02:33:09 GMT

Update: I found that the reason I didn't have RADIUS events in the event log was because I didn't have Audit Network Policy Server properties configured. Once I configured it for Success and Failure events I was able to see the failed event in the Security log. The problem was my authentication was not matching my Network Policy, so I had to change that and it worked.

Thank you for the responses.

-John