WAP321 Authentication failure log codes

Unanswered Question
Jul 19th, 2013
User Badges:

Devices that have previoulsy connected to the WAP are still able to connect but any new device to the environment is not.  If I delete the network from an existing device that device is no longer able to authenticate and connect to the WAP.  Log entries below show the following errors for a single MAC.  This happened once before and to solve the issue I reentered the key into the SSID setup on the WAP.  All devices had to delete the existing SSID from their list of networks but then they were able to rejoin.  I don't want to ask users to do that again.  Any help on the log entries below is greatly appreciated!

Jul 19 2013 01:42:34infohostapd[1078]wlan0: IEEE 802.11 STA 90:18:7c:b1:79:ea deauthed from BSSID c4:64:13:0c:e3:00 reason 1
Jul 19 2013 01:42:34infohostapd[1078]Station 90:18:7c:b1:79:ea had an authentication failure, reason 16

Jul 19 2013 01:42:32warnhostapd[1078]Received invalid EAPOL-Key MIC (msg 2/4)
Jul 19 2013 01:42:32infohostapd[1078]Station 90:18:7c:b1:79:ea had an authentication failure, reason 22

Jul 19 2013 01:42:31infohostapd[1078]Station 90:18:7c:b1:79:ea had an authentication failure, reason 22
Jul 19 2013 01:42:30warnhostapd[1078]Received invalid EAPOL-Key MIC (msg 2/4)

Jul 19 2013 01:42:30infohostapd[1078]Station 90:18:7c:b1:79:ea had an authentication failure, reason 22
Jul 19 2013 01:42:30infohostapd[1078]wlan0: IEEE 802.11 STA 90:18:7c:b1:79:ea associated with BSSID c4:64:13:0c:e3:00
Jul 19 2013 01:42:30infohostapd[1078]wlan0: IEEE 802.11 Assoc request from 90:18:7c:b1:79:ea BSSID c4:64:13:0c:e3:00 SSID KnightIns1
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
John Gage Tue, 07/23/2013 - 05:45
User Badges:

Well same issue and same outcome.  I rekeyed the wireless password into the web GUI for the WAP.  Devices still can't connect until they re-enter the password on their device, even if it was previously able to connect and work properly.  Any suggestions on how to avoid this in the future or fix it when it returns?  This time I did upgrade the firmware on the WAP if for no other reason because a newer version was available.

Eric Moyers Tue, 07/23/2013 - 08:21
User Badges:
  • Silver, 250 points or more

Hi, My name is Eric Moyers. I am a Network Support Engineer in the Cisco Small Business Support Center. Thank you for using the Cisco Community Post Forums.

Reason Code 16: Authentication failed due to a user credentials mismatch.

Reason-Code 22: The client could not be authenticated because the Extensible Authentication Protocol (EAP) Type cannot be processed by the server.

I am not sure what is causing this. However I would ask that you do two things. While everything is working normally go to Administration/Support Information and download a diagnostic file. Label it with a date WAP321 and the word "good". Save it somewhere. When this happens again, before doing anything go back in and get another diagnostic file label it the same except with the word "bad".

Call in and open a support case and have the engineer notify me that you have opened one and also give them a reference to this community support thread.

I will work with your engineer to see what is happening.


Eric Moyers    .:|:.:|:.

Cisco Small Business US STAC Advanced Support Engineer

CCNA, CCNA-Wireless


Mon - Fri 09:00 - 18:00 (UTC - 05:00)

*Please rate the Post so other will know when an answer has been found.