Home > IT Answers > Channel > Remote users with VPN client slow access time...
Help

Question

  Asked: Jun 18 2007   12:23 AM GMT
  Asked by: dimchik

Remote users with VPN client slow access times


OS, Servers, SQL Server, Security, Desktops, Management, Microsoft Windows, DataCenter, Identity & Access Management, Digital certificates, Single Signon, provisioning, Security tokens, Biometrics, Microsoft Systems Management Server, Wireless, Mobile security

I have couple of remote users with VPN clients. From time to time when they are not connected to main site they report that it takes long time to open documents on local machines. Their laptops are attached to domain; I enable logon cache in for 50 logons, via policy. Am I missing anything else? It seems like their laptops trying to find dc that?s why it takes long times. Any suggestions or help.
Thaks

Subscribe to Alerts! Get questions and answers delivered to your Inbox.


E-mail me updates on this question



   SUBSCRIBE

hidden modal window
Help

Answer Wiki (Improve, edit or add to this answer)

IMPROVE THIS ANSWER
View History
 RATE THIS ANSWER
0
Click to Vote:
  •   0
  •  0
Last Answered: Jun 21 2007  2:29 AM GMT  by bobkberg




Use SysInternal's tools TCPView and FileMon to see what connections are being attempted during this problem, and what files and paths are being attempted also during this problem.

They can be found on Microsoft's TechNet site.

You can have the users just run the tools, and save the results and email them to you for analysis.

Bob
  • AddThis Social Bookmark Button

Browse more Questions and Answers on Channel, DataCenter and SQL Server.

Looking for relevant Channel Whitepapers? Visit the SearchITChannel.com Research Library.


RSS - Discussions Help

Discuss This Answer


You must be logged-in to discuss a question. Log-in/Register

MODMOD  |   Jun 21 2007  8:37AM GMT

You may also want to look at their MTU size. If a VPN packet gets fragmented it can cause some pretty ugly connection problems. You can have the users test by running the “ping -l BufferSize” I believe windows defaults somewhere around 1500, but I’ve seen situations you need to drop to around 1400 or less to avoid problems when connecting through some ISPs/networks.