TCPIP Timewaitstate May Not Remain in 2*msl

This article was previously published under Q194429
This article has been archived. It is offered "as is" and will no longer be updated.
SYMPTOMS
TCP/IP timewaitstate will not remain in 2*MSL because of scavenging.This happens even after applying the patch mentioned in:

151418WinNT TCP/IP May Reuse TIME-WAIT Connections Prior to 2MSL
The default size may be written back to the registry (2000 Windows NT 4.0Service Pack 3).
RESOLUTION
To resolve this problem, obtain the latest service pack for Windows NT 4.0 or Windows NT Server 4.0, Terminal Server Edition. For additional information, click the following article number to view the article in theMicrosoft Knowledge Base:
152734 How to Obtain the Latest Windows NT 4.0 Service Pack

STATUS
Microsoft has confirmed that this is a problem in Windows NT 4.0 and Windows NT Server 4.0, Terminal Server Edition. This problem was first corrected in Windows NT 4.0 Service Pack 4.0 and Windows NT Server 4.0, Terminal Server Edition Service Pack 4.
MORE INFORMATION
For additional information, please see the following article in theMicrosoft Knowledge Base:

151418WinNT TCP/IP May Reuse TIME-WAIT Connections Prior to 2MSL
MSL
Properties

Article ID: 194429 - Last Review: 10/10/2013 22:33:42 - Revision: 1.3

  • Microsoft Windows NT Server 4.0, Terminal Server Edition
  • Microsoft Windows NT Workstation 4.0 Developer Edition
  • Microsoft Windows NT Server 4.0 Standard Edition
  • Microsoft Windows NT Server 4.0 Enterprise Edition
  • kbnosurvey kbarchive kbhotfixserver kbqfe kbbug kbfix kbnetwork KB194429
Feedback