Mapped Drives do not connect after VPN

TooTallJack
Conversationalist

Mapped Drives do not connect after VPN

After a user logs in with VPN it takes upwards some days 20+ minutes to connect to our mapped drives.

Any suggestions ? 

We have tried enable slow links in windows, connect to VPN first - then log into the domain. 

We are using Cisco Any connect - Tried a few different versions still same issue 

Any suggestions this is very frustrating to our users and to the IT Staff. 

Thanks

 

3 Replies 3
PhilipDAth
Kind of a big deal
Kind of a big deal

A common issue with Windows.

 

Best fix - get rid of mapped drives and change to UNC paths.

Another common method I have seen is having the VPN or user run a script to reconnect the drives.

TooTallJack
Conversationalist

We have tried and the unc path does not open either it takes 15+ minutes then it will with UNC \ IP\ FQDN anything. 

 

TooTallJack
Conversationalist

On a wire shark capture packet capture the Windows File Server closing the connection by sending a RST to the host.

We never had this issue with out old CISCO FireWall not sure how to resolve this 

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.
Labels