TCPIP Timewaitstate May Not Remain in 2*msl

Article translations Article translations
Article ID: 194429 - View products that this article applies to.
This article was previously published under Q194429
This article has been archived. It is offered "as is" and will no longer be updated.
Expand all | Collapse all

SYMPTOMS

TCP/IP timewaitstate will not remain in 2*MSL because of scavenging. This happens even after applying the patch mentioned in:

151418 WinNT TCP/IP May Reuse TIME-WAIT Connections Prior to 2MSL
The default size may be written back to the registry (2000 Windows NT 4.0 Service 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 the Microsoft 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 the Microsoft Knowledge Base:

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

Properties

Article ID: 194429 - Last Review: October 10, 2013 - Revision: 1.3
APPLIES TO
  • 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
Keywords: 
kbnosurvey kbarchive kbhotfixserver kbqfe kbbug kbfix kbnetwork KB194429

Give Feedback

 

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com