Windows 10: Slow mapped drive connection over VPN

Hello,


We having some issues with remote users accessing our shared drive over a VPN. Everything was fine up to about a week ago, when the connection slowed down dramatically. The VPN latency and bandwidth seem fine 100 ms and 600 MB/s, and also I tested the client against a shared drive on a different file server, and the problem persists. That makes me believe the problem lies in the Windows 10 client. The shared drive can take 10s+ to just open a folder, although it does usually finish successfully. Since this happened seemingly randomly, I am guessing it has something to do with Windows updates.


Let me know if have any ideas for diagnosing the issue or if you know of any Windows updates that may be relevant.


Thank you,

Sebastian

:)

 

Trouble mapping a drive over a VPN


I have a network attached storage system and when I am out of network I connect through a VPN and map the drive to access.

A few computers have been able to connect to the VPN and map the drive while others can connect to the VPN but then when trying to map the drive it says network error "windows cannot access (folder location)"

Anyone know what the issue may be? I suspect it's a setting on those individual computers not being able to map the drive rather than an issue with my NAS system.

I've attached a screenshot of the error.

 

Vpn ( trusted Vpn)

Hi everyone.
I am not an expert about Vpn and that's why I would like to know if someone could list me a few trusted Vpns, I would really appreciate any suggestion/ advice.

Thanks.

 

Issue connecting to a mapped drive over VPN...

I'm working on an odd problem with drive mapping over our F5 VPN. Here are the particulars...

1. I can map the drive, but not access either of the folders on it via my prod VPN (tested on three laptops, using Win7 and Win10). It works fine over my Lab VPN, wireless and on the LAN itself.

2. Not everyone is having this issue, and we have many users utilizing VPN (no idea how many actually use drive mapping, but I'd say quite a few).

Has anyone ever run into this issue? Why would it be possible to map a drive, yet not access its contents (depending on the connection method)?

I have a ticket open with F5 regarding this and have provided them with some captures, but no response just yet. I figured I'd ask here, bounce the issue off the Microsoft experts and see what they think.

Thanks!

AB