Security

So, "suddenly" we started getting this as an error.  The people responsible for making computer images (Windows 10 1703 specifically) have started encountering this error when attempting to perform a user based 802.1X authentication on wireless after a fresh image deployment.  Apparently, the device is joined to the AD domain already, the user logs in, then when they attempt to connect to our SSID with username/password 802.1X authentication, it fails.  The error message on ClearPass (6.6.8) is "Received failure TLV from client".  If the device is changed to perform computer authentication, it succeeds.  Once the single successfull authentication happens, any attempt after that to do user based 802.1X also succeeds.  It is just the first time "out of the box" that fails.  I suspect it is a certificate issue.  Something missing, or an attempt to access some offsite address that fails is causing it.

Anyone have any thoughts?

Edmund C. Greene

Tim,

No, it is set to "None".  Should I set it to "Optional" or "Required"?

Ed

So, I tried it with both (optional, required) and there was no difference in the result.  I am still getting the "Received failure TLV from client" error.

The setting "Disable TLS 1.2" is set to FALSE.  This setting is per server.

Clusterwide, disable TLS 1.0 and 1.1 is set to NONE

Did you ever get a solution to this problem?  I updated the certificate over the weekend on clearpass and now i am seeing the same thing happening on windows 10. Windows 7 works fine.

Hi Guys,

Did you found a fixed for this problem, I'm having this same problem.

Thanks

Unfortunately, it looks like I did not write down the solution anywhere.  But if I remember correctly it had something to do with the client not being able to get or not having the host certificate (of the clearpass server), or having a mismatched certificate.  Since the problem was with imaging windows computers, they put the certificate into the image so new computers would already have it.

Hope this helps.  I'll continue to look to see if I documented the problem anywhere.

I'm seeing this same issue on windows 10 client. Any update to this? 

We are also seeing this today with a Win 10 client. Updates welcome.

Update on our situation - we haven't rolled out the group policy for SSO yet and the end user was using different credentials for machine logon and wi-fi.

I told him to stop doing that. Error gone.