EAP Identifier Mismatch

[Xfeldt]

I sometimes experience that some random client have problems connecting to the WiFi.
Analytics just says it is an "EAP identifier mismatch", but what does that mean, and what causes it ??

The SSID uses 802.1x with certificates, and the clients is Windows 10.
I have tried to look at the NPS servers logs, but can't see anything about it denying the client access.

This is what i get from Analytics, what is weird is that the AP sends 3 EAP requests, before it gets a response from the client.
Anybody have any experience with this type of fault ??

[mlapushin]

In the same boat, heaps of this. Curious whats going on.

[net_admin_77721]

We are seeing similar failures - did anyone solve this?

[syamantakomer]

Hello All,

In the above diagram, 3 EAP request frames are retries because there seem no response from the client. 4th one is either a timeout of other EAP failure as client did not respond with expecting information.

This is a client communication failure, to check this any further or deeper, a packet capture on AP's radio interface or using a 3rd party device must be collected and reviewed, along with AP debug logs.

For EAP identified mismatch I suggest you review the NPS policy and make sure correct EAP method is added to the connection policy.

It will be best to open a case with RUCKUS Support.