cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
527
Views
0
Helpful
5
Replies
Highlighted
Beginner

Anyconnect cannot connect VPN when unrelated Smartcard is inserted.

Hi Community.

We are cureently facing the issue that AnyConnect 4.6.00362 won't connect to VPN when an unrelated smartcard is inserted in the windows pc.

anyconnect uses machine certificates as an additional means of authorization but it should not check the userspace for any certificates like smartcard.

When SC is removed VPN connect works without delay or issues.

 

does anyone have an idea where to look at?

 

regards

Bernhard

1 ACCEPTED SOLUTION

Accepted Solutions
Highlighted
Beginner

Re: Anyconnect cannot connect VPN when unrelated Smartcard is inserted.

The solution for me was to upgrade the users in question to W10 and use AnyConnect 4.8.

The issue was never to be seen again.

 

View solution in original post

5 REPLIES 5
Highlighted
Hall of Fame Guru

Re: Anyconnect cannot connect VPN when unrelated Smartcard is inserted.

The default behavior is to check for user certificates. You can override that in the VPN profile by choosing the Machine certificate store and checking the "Certificate Store Override" box.

 

AC Certificate Store.PNG

Highlighted
Beginner

Re: Anyconnect cannot connect VPN when unrelated Smartcard is inserted.

Hi Marvin,

thanks for your reply.

 

The thing is that the profile is already set to Machine store.

Here is the screenshot of it.

temp.png

 

 

as far as I can trust the user, he's got a 10% chance of it working despite the smart card inserted.

if it's not working the removal of the sc will solve the issue.

still Windows 7 it it helps.

Highlighted
Hall of Fame Guru

Re: Anyconnect cannot connect VPN when unrelated Smartcard is inserted.

Highlighted
Beginner

Re: Anyconnect cannot connect VPN when unrelated Smartcard is inserted.

good idea,
will check and report back

thanks

Highlighted
Beginner

Re: Anyconnect cannot connect VPN when unrelated Smartcard is inserted.

The solution for me was to upgrade the users in question to W10 and use AnyConnect 4.8.

The issue was never to be seen again.

 

View solution in original post