Mapped drives do not open after connecting via Cisco VPN Client - Cisco Community

23627

Views

4

Helpful

3

Replies

I have an issue when I initially connect to my remote network, I cannot get to any mapped drive unless I wait a few minutes for the VPN connect to mature. To explain further, I have to wait 2-4 minutes after connecting to the VPN for me to actually connect to those drives.

The error that pops up is:

"An error occurred while reconnecting to DriveLetter: to \\Server\sharedDrive\ Microsoft WIndows Network: The network path was not found. This connection has not been restored.

Now, immediately after I connect, I am able to successfully ping the server that hosts those folder locations but for some reason I cannot get to the server via UNC/shared drives until I wait a few minutes after connecting.

Below is the list of error logs I get when attempting to connect to the mapped drives during those first few minutes of connectivity:

1 15:26:39.804 10/06/14 Sev=Warning/3 IKE/0xA300005F

Firewall, Sygate Security Agent, is not running, the client will not send firewall information to concentrator.

2 15:28:10.614 10/06/14 Sev=Warning/2 IPSEC/0xE3700003

Function CniInjectSend() failed with an error code of 0xE4510023 (IPSecDrvCB:856)

3 15:28:10.614 10/06/14 Sev=Warning/2 IPSEC/0xE3700003

Function CniInjectSend() failed with an error code of 0xE4510023 (IPSecDrvCB:856)

4 15:28:10.614 10/06/14 Sev=Warning/2 IPSEC/0xE3700003

Function CniInjectSend() failed with an error code of 0xE4510023 (IPSecDrvCB:856)

5 15:28:10.614 10/06/14 Sev=Warning/2 IPSEC/0xE3700003

Function CniInjectSend() failed with an error code of 0xE4510023 (IPSecDrvCB:856)

6 15:28:10.614 10/06/14 Sev=Warning/2 IPSEC/0xE3700003

Function CniInjectSend() failed with an error code of 0xE4510023 (IPSecDrvCB:856)

7 15:28:10.614 10/06/14 Sev=Warning/2 IPSEC/0xE3700003

Function CniInjectSend() failed with an error code of 0xE4510023 (IPSecDrvCB:856)

8 15:28:10.614 10/06/14 Sev=Warning/2 IPSEC/0xE3700003

Function CniInjectSend() failed with an error code of 0xE4510023 (IPSecDrvCB:856)

9 15:28:10.614 10/06/14 Sev=Warning/2 IPSEC/0xE3700003

Function CniInjectSend() failed with an error code of 0xE4510023 (IPSecDrvCB:856)

10 15:28:17.188 10/06/14 Sev=Warning/2 IPSEC/0xE3700003

Function CniInjectSend() failed with an error code of 0xE4510023 (IPSecDrvCB:856)

11 15:28:17.188 10/06/14 Sev=Warning/2 IPSEC/0xE3700003

Function CniInjectSend() failed with an error code of 0xE4510023 (IPSecDrvCB:856)

12 15:33:50.642 10/06/14 Sev=Warning/2 CVPND/0xA3400015

Error with call to IpHlpApi.DLL: CheckUpVASettings: Found IPADDR entry addr=192.168.11.120, error 0

13 15:33:51.656 10/06/14 Sev=Warning/2 CVPND/0xA3400015

Error with call to IpHlpApi.DLL: CleanUpVASettings: Was able to delete all VA settings after all, error 0

14 15:35:16.855 10/06/14 Sev=Warning/3 IKE/0xA300005F

Firewall, Sygate Security Agent, is not running, the client will not send firewall information to concentrator.

Any ideas on what it could be?

3 Replies 3

I have a client that is showing a similar issue.. Windows 7 computer using Cisco IPSec client terminating on a Cisco 881 Router. I can ping the server by IP, Name and even access the drive from the start menu option, but not the mapped drive. Currently I am looking into this from a offline file issue in windows, but ran across this post and was wondering if you had figured this out? I am going to try the following and will post back if that resolves it.

Doing some research I found that Windows 7 and Vista both have what’s called “slow link mode”. The behavior is that if the latency of the network connection exceeds 80 milliseconds (ms), the system will transition the files to “offline mode”. The 80 ms value is configurable using a local group policy edit.

Open Group policy (start -> run -> gpedit.msc)
Expand “Computer Configuration”
Expand “Administrative Templates”
Expand “Network”
Click on “Offline Files”
Locate “Configure slow-link mode”
This policy can either be disabled or set to a higher value for slower connections.

https://www.conetrix.com/Blog/post/Fixing-Problem-With-Windows-7-Shared-Files-and-Mapped-Drives-Unavailable-Over-VPN.aspx

I am assuming you are using a Domain. Your group policies are not being applied because you are not connected to the Domain before you logon. Try connecting to VPN, then switch user in Windows and logon to the Domain. You should then get your drives.

Thanks

John

**Please rate posts you find helpful**

John,

Thanks for commenting on this. I was actually able to fully resolve my user's issue with a combination of disabling Slow link mode and also unchecking the IPv6 box from the VPN adapter's properties. Drives were always mapped, just not accessible when on the VPN for at least the first 5 minutes.

Regards,

Raul