It seems to make the 'RPCSS' (Remote Procedure Call Server Service) eat
99% of cpu time. You can prevent rebooting by killing and restarting
RPCSS. (I was not able to stop the process on my NT4.0 WKS SP2 box except
by attaching a debugger to the process, and then stopping the debugger.
Then to restart, do 'net start rpcss' from a CMD.EXE window.
Hmm...
- Aaron
--
Aaron Spangler EE Unix System Administrator
Electrical Engineering FT-10 pokee_at_ee.washington.edu
University of Washington Phone (206) 543-8984
Box 352500 or (206) 543-2523
Seattle, WA 98195-2500 Fax (206) 543-3842
> -----Original Message-----
> From: Jason T. Luttgens [SMTP:luttgenj_at_kic.or.jp]
> Sent: 21 January 1997 11:26
> To: Multiple recipients of list BUGTRAQ
> Subject: NT4 bug? Or bug in my hardware?
>
> Can anyone confirm this? On an NT4 server (maybe workstation too, I
> don't have it to try),
> if you telnet to port 135, type a bunch of junk (say 10-20
> characters), hit enter and disconnect,
> the server's processor utilization will go up to 100%!!! The only fix
> I found was to reboot.
> I tried with and without SP2.....same result. The installation is 'out
> of the box' with standard
> default install options, of course including TCP/IP. I have no other
> NT4 servers to try this on
> and was wondering if I could get someone to try and confirm this
> .....
>
> Luck
>
Received on Jan 22 1997
Intro
