Termnial Services Problem

  • Thread starter Thread starter Kennith Owens
  • Start date Start date
K

Kennith Owens

Before I started at this company, our main server was
attacked by malware. One of the after effects that I've
noticed is it seems to have corrupted some necessary
Windows files. Right now, whenever anyone tries to use
Terminal Services to access this particular server, it
restarts the machine. Has anyone else seen this before?
If so, what is the solution? Is there some other
newsgroup I should be corresponding with?

Thanks, beforehand for your assistance.
 
First of all, I would configure the server to *not* automatically
reboot when a STOP error occurs, but to have it halted. That will
give you an opportunity to write down the STOP error code (if
any).

If the server still reboots automatically after you made this
change, then that means that the OS never got the chance to
generate a STOP error. That is indicative of a hardware problem,
and I would run all the diagnostics test, especially CPU and
memory, that came with the server.

If the server actually halts with a STOP error, write down the
driver that is listed on the fourth line of the blue screen (the
one that causes the crash). If it lists something that is a
remnant of the malware, you might be able to uninstall it
completely.
But I must say that I would seriously consider to do a fresh
install of the server. After an incident like this, you can never
be sure what is going on in your server.
 
Thanks for all your great advice. Aren't there any tools
that can go through and look for and correct corrupt
Windows files? Thanks again.
 
Back
Top