Thats what I'd do is kill the process. I use Pslist and Pskill to check and kill processes remotely on the NT domain.
http://www.systernals.com/ntw2k/freeware/pslist.shtml http://www.systernals.com/ntw2k/freeware/pskill.shtml Rach ----- Original Message ----- From: "Dave Warren" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Saturday, January 19, 2002 1:17 AM Subject: Re: Win2k service unstoppable > I've run into this once in a while, it went away when I upgraded my > video drivers. > > If you have the NT/W2K resource kit, you can use KILL.EXE to terminate > the process... > > Kenneth Porter wrote: > > > My VNC service on Win2k Server has stopped responding, and I can't shut > > it down remotely with the management console; it just reports "stopping" > > and appears to be ignoring the stop request. I expect I'll have to > > reboot the server to get VNC back again. I see nothing interesting in > > the event logs that might give a clue. > > > > Anyone have experience with this? Is there anything I can do short of > > rebooting the box? > > > > Attempts to telnet to port 5900 are refused so I think the service is no > > longer even listening. > > > -- > The nice thing about standards, there is enough for everyone to have their own. > --------------------------------------------------------------------- > To unsubscribe, mail [EMAIL PROTECTED] with the line: > 'unsubscribe vnc-list' in the message BODY > See also: http://www.uk.research.att.com/vnc/intouch.html > --------------------------------------------------------------------- --------------------------------------------------------------------- To unsubscribe, mail [EMAIL PROTECTED] with the line: 'unsubscribe vnc-list' in the message BODY See also: http://www.uk.research.att.com/vnc/intouch.html ---------------------------------------------------------------------
