03-24-2014 06:45 AM - edited 03-10-2019 09:34 PM
Hi. I am running AnyConnect 3.1 with EAP Chaining/MSCHAPv2. On Windows 7 machines, MSCHAP works well, and pulls my cached credentials. But on Windows 8.1 machines, it prompts for user authentication, instead of using the cached credentials. The configuration file is the same between the two machines. One the Windows 8 user enters their credentials, authentication is successful. Any ideas as to why Windows 8.1 doesn't want to work well with MSCHAP? Thanks.
03-26-2014 03:03 AM
Hi,
I can just think about windows provilege at which the anyconnect runs in windows 8.1. I can imagine its something like the user at which the anyconnect runs has no privilege to save the credentials. or something similar.
it worths to check that.
HTH,
Amjad
03-31-2014 06:36 AM
I just happened to update my Win7 machine and now it is doing the same thing. Anyconnect is prompting for credentials instead of using MSCHAPv2. I notice in the ISE logs that authentication is trying come through as host/machinename and then username is coming in as anonymous. I expect to see 'username >> host/machinename', but I never get it. Just getting authentication failed. I followed the EAP chaining trustsec guide. Everything was working on Win7 before the most recent update. Got to love MS.
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