Microsoft KB Archive/285663

From BetaArchive Wiki

Article ID: 285663

Article Last Modified on 1/29/2007



APPLIES TO

  • Microsoft Windows 2000 Service Pack 1
  • Microsoft Windows 2000 Service Pack 2
  • Microsoft Windows 2000 Advanced Server
  • Microsoft Windows 2000 Advanced Server
  • Microsoft Windows 2000 Service Pack 1
  • Microsoft Windows 2000 Service Pack 2
  • Microsoft Windows NT 4.0 Service Pack 6a
  • Microsoft Windows NT 4.0 Service Pack 6a
  • Microsoft Windows NT Workstation 4.0 Developer Edition



This article was previously published under Q285663

SYMPTOMS

When a client is configured with two gateways and one of the gateways is not working, existing Transmission Control Protocol/Internet Protocol (TCP/IP) connectivity may break if the client receives a reset from a remote server. The reset may occur when the client tries to connect to a remote server port that is not listening.

CAUSE

This problem occurs because of the way that TCP processes a reset during connection establishment. SYN is retried three times, even if RST is received. On the second retry, TCP tries to check for an alternate route. If the number of connections that are not working is greater than 25 percent of the connections, TCP tries to switch all of the connections to a different route. Because the second gateway is not working, existing connections are broken.

RESOLUTION

Windows 2000

To resolve this problem, obtain the latest service pack for 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


The English version of this fix should have the following file attributes or later:

   Date         Time     Version         Size      File name
   ------------------------------------------------------------
   5/29/2001   07:54a   5.0.2195.3649   118,800   Afd.sys
   5/31/2001   03:31p   5.0.2195.3649   104,720   Msafd.dll
   5/30/2001   02:28p   5.0.2195.3650   312,240   Tcpip.sys
   5/29/2001   07:53a   5.0.2195.3649    16,208   Tdi.sys
   5/31/2001   03:32p   5.0.2195.3649    17,680   Wshtcpip.dll 
                


Windows NT 4.0

A supported hotfix is now available from Microsoft, but it is only intended to correct the problem that this article describes. Apply it only to systems that are experiencing this specific problem.

To resolve this problem, contact Microsoft Product Support Services to obtain the hotfix. For a complete list of Microsoft Product Support Services telephone 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 usual 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 should have the following file attributes or later:

   Date         Time     Version         Size      File name     Platform
   ------------------------------------------------------------------
   01/07/2000   04:51p   4.0.1381.7036    66,480   Afd.sys       Intel
   03/20/2001   07:01p   4.0.1381.7045    47,888   Msafd.dll     Intel
   03/20/2001   06:43p   4.0.1381.7095   174,736   Tcpip.sys     Intel
   02/12/1999   03:01p   4.0.1381.164      9,712   Tdi.sys       Intel
   03/20/2001   07:01p   4.0.1381.7045    18,704   Wshtcpip.dll  Intel

   03/01/2001   05:01p   4.0.1381.7092   115,408   Afd.sys       Alpha
   03/20/2001   07:01p   4.0.1381.7052    79,120   Msafd.dll     Alpha
   03/20/2001   06:39p   4.0.1381.7095   308,784   Tcpip.sys     Alpha
   03/01/2001   05:01p   4.0.1381.7092    14,224   Tdi.sys       Alpha
   03/20/2001   07:01p   4.0.1381.7052    28,432   Wshtcpip.dll  Alpha
                

NOTE: Because of file dependencies, this fix requires Microsoft Windows NT 4.0 Service Pack 6a.


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 Windows 2000 Service Pack 3.

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


For additional information about how to install multiple hotfixes with only one reboot, click the article number below to view the article in the Microsoft Knowledge Base:

296861 Use QChain.exe to Install Multiple Hotfixes with One Reboot


For additional information about how to install Windows 2000 and Windows 2000 hotfixes at the same time, click the article number below to view the article in the Microsoft Knowledge Base:

249149 Installing Microsoft Windows 2000 and Windows 2000 Hotfixes



Additional query words: ing TCPIP

Keywords: kbbug kbfix kbperformance kbwin2000presp3fix kbqfe kbwin2000sp3fix kbnetwork kbhotfixserver KB285663