The information in this article applies to:
SYMPTOMSComputers running Windows NT or Windows 95 may stop responding (hang) when they receive corrupted Internet Control Message Protocol (ICMP) datagram fragments from a client. RESOLUTION
Microsoft has updated the TCP/IP protocol stack to correct this problem.
Instructions for installing it are available from Microsoft support
channels or directly from the Internet locations below. Windows NT 4.0To 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, please see the following article in the Microsoft Knowledge Base:Q152734 How to Obtain the Latest Windows NT 4.0 Service Pack For your convenience, the English version of this post-SP3 hotfix has been posted to the following Internet location. However, Microsoft recommends that you install Windows NT 4.0 Service Pack 4 to correct this problem. ftp://ftp.microsoft.com/bussys/winnt/winnt-public/fixes/usa/NT40/ hotfixes-postSP3/teardrop2-fixNOTE: Service Pack 3 must be applied to Windows NT 4.0 prior to applying this fix. Windows NT 3.51NOTE: Service Pack 5 must be applied to Windows NT 3.51 prior to applying this fix.This fix should have the following time stamp:
This hotfix has been posted to the following Internet location:
ftp://ftp.microsoft.com/bussys/winnt/winnt-public/fixes/usa/NT351/ hotfixes-postSP5/teardrop2-fix Windows 95This issue is resolved by the following updated file for Windows 95 and OSR2, and later versions of this file:
This file is included in the self-extracting Vipup11.exe file.To install this update, follow these steps:
Vipup11.exeFor more information about downloading files from the Microsoft Software Library, please see the following article in the Microsoft Knowledge Base: Q119591 How to Obtain Microsoft Support Files from Online ServicesThe following files are installed by Vipup11.exe:
STATUSMicrosoft has confirmed this problem could result in some degree of security vulnerability in Windows NT version 4.0. 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. Microsoft has confirmed this problem could result in some degree of security vulnerability in Windows NT version 3.51. A fully supported fix is now available, but it has not been fully regression tested and should only be applied to systems determined to be at risk of attack. Please evaluate your system's physical accessibility, network and Internet connectivity, and other factors to determine the degree of risk to your system. If your system is sufficiently at risk, Microsoft recommends you apply this fix. Otherwise, wait for the next Windows NT service pack, which will contain this fix. Please contact Microsoft Technical Support for more information. Microsoft has confirmed this to be a problem in Microsoft Windows 95 and OEM Service Release 2 (OSR2). An update to address this problem is now available, but is not fully regression tested and should be applied only to computers experiencing this specific problem. Unless you are severely impacted by this specific problem, Microsoft does not recommend implementing this update at this time. Contact Microsoft Technical Support for additional information about the availability of this update. Additional query words:
Keywords : kbfile kbnetwork NT4SP4Fix ntsecurity kbbug4.00 kbfix4.00.sp4 kbbug3.51 kbfix3.51 NTSrvWkst |
Last Reviewed: September 18, 1999 © 2000 Microsoft Corporation. All rights reserved. Terms of Use. |