Why is eap-chaining failing on windows 10?

[ffadhilpi]

We configured eap-chaining but it is not working with the error: "Machine authentication against Active Directory has failed because of wrong password" after researching, it looks like we are getting this bug "CSCuh23463" we are using NAM/anyconnect 4.4 ISE 2.2 windows 10 joined to the domain.

TAC is taking forever to reply to me and they are insisting that I'm not hitting that bug as this was for NAM 3.x and not for what I use.

Here are some error messages from the live logs:

EapChainingResult

User succeeded and machine failed

DetailedInfo

Invalid username or password specified, Retry is allowed

Machine authentication against Active Directory has failed because of wrong password - All_AD_Join_Points

RPC Logon request failed - STATUS_WRONG_PASSWORD,ERROR_INVALID_PASSWORD,RN-LEN-0NBVGG$@corp.net

[hslai · Accepted solution]

See Windows 10 AnyConnect 4.3 NAM Questions

If possible, please provide TAC case number.

[ffadhilpi]

683041561

[hslai]

Per case notes, this is a new case opened today, TAC is actively working on it and coming into the same conclusion as I suggested above. Please continue engaging TAC.

[ffadhilpi]

I guess I posted here looking for someone who's done eap-chaining for win10

[ffadhilpi]

Modify the win10 reg keys and add LsaAllowReturningUnencryptedSecrets. That was the fix!