09-12-2017 10:36 AM
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.
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
Solved! Go to Solution.
09-12-2017 10:45 AM
See Windows 10 AnyConnect 4.3 NAM Questions
If possible, please provide TAC case number.
09-12-2017 10:45 AM
See Windows 10 AnyConnect 4.3 NAM Questions
If possible, please provide TAC case number.
09-12-2017 10:49 AM
683041561
09-12-2017 12:20 PM
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.
09-12-2017 01:04 PM
I guess I posted here looking for someone who's done eap-chaining for win10
09-25-2017 01:34 PM
Modify the win10 reg keys and add LsaAllowReturningUnencryptedSecrets. That was the fix!
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide