Windows Shares Asking for Credentials via Client VPN

Here to help

Windows Shares Asking for Credentials via Client VPN

In an older version of the Cisco VPN client the username and password for the VPN did not seem to passthrough over to Windows when connecting to file shares, the server would use the credentials of the user logged onto the computer, this doesn't seem to be the case for Client VPN, it seems to be passing over the username and password set up for the client VPN.  Is there another way to set that up or way so the client VPN username & password doesn't get passed on to Windows server shared when you connect?

Here to help

How are you authenticating users on the VPN? Also are you using Cisco AnyConnect or windows built-in?

Authenticating against Meraki Cloud, the list we've built in the dashboard, we're using Windows built-in.


Side-bar: Does Cisco AnyConnect require additional licensing?

Kind of a big deal

There are some requirements that you need to configure before:


And yes, you need to buy an Anyconnect license.


How does AnyConnect licensing work with the Meraki MX/vMX appliance?

Customers are expected to have a valid AnyConnect license to use AnyConnect with the MX Appliance. Customers are not required to validate their licenses via the Meraki MX or the dashboard. Customers will only be required to accept terms and conditions of use before they can enable AnyConnect. If you are already using AnyConnect or setting it up for the first time, there will be a dashboard notification to accept the terms and conditions of use. There will be no disruption of the AnyConnect service for active networks.

Get notified when there are additional replies to this discussion.
Welcome to the Meraki Community!
To start contributing, simply sign in with your Cisco account. If you don't yet have a Cisco account, you can sign up.