Microsoft KB Archive/817069

= Cannot Connect to a Network Share over a VPN Connection =

Article ID: 817069

Article Last Modified on 2/19/2007

-

APPLIES TO


 * Microsoft Windows 2000 Advanced Server
 * Microsoft Windows 2000 Professional Edition
 * Microsoft Windows 2000 Server

-



SYMPTOMS
After you establish a virtual private network (VPN) connection with a server, you cannot connect to any shares on the server. You can ping the server by name and Internet Protocol (IP) address, but cannot connect to shares on the server. Net View and Net Use commands fail with one of the following error messages:

System error 121. The semaphore timeout period has expired

System error 53. The network path was not found.

System error 64. The specified network name is no longer available.



CAUSE
This problem occurs because the TCP window size for the TCP connection for the VPN client is 0 (zero).



Service Pack Information
To resolve this problem, obtain the latest service pack for Microsoft Windows 2000. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:

260910 How to Obtain the Latest Windows 2000 Service Pack

Hotfix Information
A supported fix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Apply it only to computers that are experiencing this specific problem. This fix may receive additional testing. Therefore, if you are not severely affected by this problem, Microsoft recommends that you wait for the next Windows 2000 service pack that contains this hotfix.

To resolve this problem immediately, contact Microsoft Product Support Services to obtain the fix. For a complete list of Microsoft Product Support Services phone numbers and information about support costs, visit the following Microsoft Web site:

http://support.microsoft.com/contactus/?ws=support

NOTE: In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The typical support costs will apply to additional support questions and issues that do not qualify for the specific update in question.

The English version of this fix has the file attributes (or later) that are listed in the following table. The dates and times for these files are listed in coordinated universal time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.

  Date         Time   Version            Size    File name --  17-Mar-2003  17:11  5.0.2195.6687     119,024  Afd.sys 20-Mar-2003 09:14  5.0.2195.6602     108,816  Msafd.dll 20-Mar-2003 09:14  5.0.2195.6691     314,704  Tcpip.sys 15-Jan-2003 10:56  5.0.2195.6655      16,240  Tdi.sys 20-Mar-2003 09:14  5.0.2195.6601      17,680  Wshtcpip.dll



STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article. This problem was first corrected in Microsoft Windows 2000 Service Pack 4.



MORE INFORMATION
For additional information about how to obtain a hotfix for Windows 2000 Datacenter Server, click the article number below to view the article in the Microsoft Knowledge Base:

265173 The Datacenter Program and Windows 2000 Datacenter Server Product

Keywords: kbhotfixserver kbqfe kbwin2ksp4fix kberrmsg kbprb kbwin2000presp4fix kbfix kbbug KB817069

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.