Connections to RPC Server cause 100% CPU Usage

SYMPTOMS
========

When an RPC server application is running on Windows NT, if the RPC client 
gracefully disconnects from the server without supplying the server all 
the data it expects, the NT CPU Usage jumps to 100% and does not come back
down until the NT machine is rebooted.

CAUSE
=====
If an RPC Server application using a Sockets based transport (Tcp or Spx)
has a client randomly initiate a gracefully disconnect the RPCSS.EXE 
(Server Side RPC) can be left in a tight loop making recv() calls for more
data.  The recv() call returns 0 bytes, which is not treated as an error.
This causes the CPU exhaustion.  If the disconnection is not graceful 
(such as from a crash,) an error will result, avoiding this code path. 

RESOLUTION
==========

A new version of RPCLTSCM.DLL is available that corrects this problem. 

STATUS
======

Microsoft has confirmed this to be a problem in Windows NT version 4.0. A
supported fix is now available, but has not been fully regression-tested
and should be applied only to systems experiencing this specific problem.
Unless you are severely impacted by this specific problem, Microsoft
recommends that you wait for the next service pack that contains this fix.
Contact Microsoft Technical Support for more information.

This hotfix has been posted to the following Internet location:

   ftp://ftp.microsoft.com/bussys/winnt/winnt-public/fixes/usa/NT40/
   hotfixes-postSP2/RPC-fix