TCP Does Not Set Timestamp Correctly (331491)



The information in this article applies to:

  • Microsoft Windows 2000 Advanced Server SP1
  • Microsoft Windows 2000 Advanced Server SP2
  • Microsoft Windows 2000 Advanced Server SP3
  • Microsoft Windows 2000 Professional SP1
  • Microsoft Windows 2000 Professional SP2
  • Microsoft Windows 2000 Professional SP3
  • Microsoft Windows 2000 Server SP1
  • Microsoft Windows 2000 Server SP2
  • Microsoft Windows 2000 Server SP3

This article was previously published under Q331491

SYMPTOMS

If you are using a slow connection (such as a remote access or virtual private network [VPN] connection), nothing may be sent to the server if you set the Tcp1323Opts registry value to 3 on the client. The following behavior occurs when a TCP session is established between the client and the server (the Web service is running on the VPN server, and the VPN client visits the Web site on the VPN server):

Client sends to server: SYN, with Timestamps option
Server sends to client: ACK, SYN, without Timestamps option
Client sends to server: ACK, without Timestamps option
Server sends to client: ACK, with Timestamps option
Client sends to server: ACK, without Timestamps option
Client sends to server: ACK, without Timestamps option
Server sends to client: ACK, with Timestamps option
...

The first packet that is sent by the client does have the Timestamps option, but the others do not. The first packet that is sent by the server does not have the Timestamps option, but the others do.

RESOLUTION

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: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
   --------------------------------------------------------
   13-Nov-2002  19:36  5.0.2195.6127  118,896  Afd.sys
   02-Dec-2002  22:16  5.0.2195.6020  105,232  Msafd.dll
   02-Dec-2002  22:15  5.0.2195.6146  313,648  Tcpip.sys
   31-Jul-2001  03:15  5.0.2195.3988   16,240  Tdi.sys
   02-Dec-2002  22:16  5.0.2195.4874   17,680  Wshtcpip.dll


Note You must install this hotfix on the server, not the client.

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.

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


Modification Type:MinorLast Reviewed:10/11/2005
Keywords:kbHotfixServer kbQFE kbbug kbfix kbQFE kbWin2000preSP4Fix KB331491