mnowicky
asked on
Network drive delay when using VPN
Hello,
A few users are reporting that when they connect to the network through the VPN, the network drives are not immediately available. After a few minutes the network drives will eventually come up and be available.
I have been playing with the TCP/IP settings and trying to search around but can't find the answer to this one... anyone ever experienced this? It is through a Sonicwall VPN.
Thanks for any tips!
A few users are reporting that when they connect to the network through the VPN, the network drives are not immediately available. After a few minutes the network drives will eventually come up and be available.
I have been playing with the TCP/IP settings and trying to search around but can't find the answer to this one... anyone ever experienced this? It is through a Sonicwall VPN.
Thanks for any tips!
ASKER
Thanks for the suggestion!
Thinking it through a little more... the user is taking the laptop home and connecting to the corporate network from home, where as I remote into my work computer from my home computer.
So I guess there has to be some sort of setting that would make the network drives available immediately after making the VPN connection?
Thinking it through a little more... the user is taking the laptop home and connecting to the corporate network from home, where as I remote into my work computer from my home computer.
So I guess there has to be some sort of setting that would make the network drives available immediately after making the VPN connection?
ASKER
Also- this is only happening with one file server.
We have 2 other file servers with shares that are immediately available once connected.
What's happening with the problem share is that you can see the drive mapped, but there are no contents for a few minutes. After a couple minutes the contents are populated.
We have 2 other file servers with shares that are immediately available once connected.
What's happening with the problem share is that you can see the drive mapped, but there are no contents for a few minutes. After a couple minutes the contents are populated.
What if you simulate the user's login method or environment by using your ID for testing ? Does it the same as well ?
>> can see the drive mapped, but there are no contents for a few minutes. After a couple minutes the contents are populated.
This lead to me to think of the size of the files share being mapped, is in huge of size, as huge size of files share will take longer time to load. Try to do some house keeping on that file server, those files that not in used, can be archived up and move to another location and not shared.
>> can see the drive mapped, but there are no contents for a few minutes. After a couple minutes the contents are populated.
This lead to me to think of the size of the files share being mapped, is in huge of size, as huge size of files share will take longer time to load. Try to do some house keeping on that file server, those files that not in used, can be archived up and move to another location and not shared.
ASKER
Yes, the share is about 700GB in size.
I am going to take a laptop home tonight and see what happens when I try to recreate the same environment the user is using.
Thanks again.
I am going to take a laptop home tonight and see what happens when I try to recreate the same environment the user is using.
Thanks again.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
You can tell your users to try to use direct addressing:
enter the path to the "shared folder" directly in the the explorer address bar:
\\<FileServerName>\<SharedFolderName>
(or use a Net Use command as it was mentioned earlier. Note that you may not need to enter a disk drive letter in the net use command, net use \\<FileServerName>\<SharedFolderName> is OK too, but the "mounted" shared folder will not appear in the resources available to the user in Explorer).
If this works, you have a start on an answer The problem is certainly related to name resolving and/or populating the resources available on your network.
You also would have a workaround (if it works)...
enter the path to the "shared folder" directly in the the explorer address bar:
\\<FileServerName>\<SharedFolderName>
(or use a Net Use command as it was mentioned earlier. Note that you may not need to enter a disk drive letter in the net use command, net use \\<FileServerName>\<SharedFolderName> is OK too, but the "mounted" shared folder will not appear in the resources available to the user in Explorer).
If this works, you have a start on an answer The problem is certainly related to name resolving and/or populating the resources available on your network.
You also would have a workaround (if it works)...
mnowicky,
Any update on this?
Any update on this?
ASKER
Thank you
You're welcome...my pleasure. Glad I could help and thanks for the points!
How about yourself ?? if yourself is working fine, try to use the same environment to login as that few users, if the problem goes away, it could be the network speed of the user's end.