Telnet to Port 135 Causes 100 Percent CPU UsageLast reviewed: October 15, 1997Article ID: Q162567 |
The information in this article applies to:
SYMPTOMSWhen 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.
CAUSEThis problem is caused by a problem with the remote procedure call (RPC) components in Windows NT.
RESOLUTIONTo resolve this problem, download and install the appropriate file:
Windows NT 3.51This hotfix has been posted to the following Internet location:
ftp://ftp.microsoft.com/bussys/winnt/winnt-public/fixes/usa/NT351/ hotfixes-postSP5/rpc-fix Windows NT 4.0This hotfix has been posted to the following Internet location:
ftp://ftp.microsoft.com/bussys/winnt/winnt-public/fixes/usa/NT40/ hotfixes-postSP2/rpc-fix STATUSMicrosoft has confirmed this to be a problem in Windows NT version 3.51 and 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):
S E R V P A C K |
Additional query words: Telnet RPC crash hang max prodnt
© 1998 Microsoft Corporation. All rights reserved. Terms of Use. |