Article ID: 162567
Article Last Modified on 11/1/2006
APPLIES TO
- Microsoft Windows NT Workstation 3.51
- Microsoft Windows NT Workstation 4.0 Developer Edition
- Microsoft Windows NT Server 3.51
- Microsoft Windows NT Server 4.0 Standard Edition
This article was previously published under Q162567
SYMPTOMS
When a client uses the telnet utility to connect to port 135 of a computer
running Windows NT Server, and then types more than 10 random characters
and disconnects, the server CPU usage jumps to 100 percent and does not
come back down until the server is restarted.
CAUSE
This problem is caused by a problem with the remote procedure call (RPC)
components in Windows NT.
RESOLUTION
To resolve this problem, download and install the appropriate file:
Windows NT 3.51
This hotfix has been posted to the following Internet location:
Windows NT 4.0
This hotfix has been posted to the following Internet location:
STATUS
Microsoft has confirmed this problem could result in some degree of
security vulnerability in Windows NT version 4.0. This problem was
corrected in the latest Microsoft Windows NT 4.0 U.S. Service Pack. For
information on obtaining the service pack, query on the following word in
the Microsoft Knowledge Base (without the spaces):
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.
Additional query words: Telnet RPC crash hang max prodnt
Keywords: kbbug kbnetwork KB162567