Terminal Services reboots the Win2k server

[Guest]

Hi there
I have Terminal Services installed to a Win2k SBS SP1 server, simple application 1 remote user. It was connecting fine and running the application. I decided to upgrade to Win2k SP4 and now as soon as a remote desktop client attempts to connect to the TS the Win2K server shuts down and reboots. There are no errors on the error log. I did uninstall TS and reinstall it again but to no avail
Any suggestions
Thank
Ard

 

[Vera Noest [MVP]]

From SBS to Windows 2000 is not a valid upgrade path. You have to do
a clean installation. Check:

Upgrading from Previous Versions of Windows
http://www.microsoft.com/windows2000/server/howtobuy/upgrading/path/d
efault.asp

 

[Vera Noest [MVP]]

OK, so you ran Windows update and are now on SBS 2000, SP4, is
that correct?

Did you also install any 3th party printer drivers? Or other 3th
party software, just before this problem started?

To get more information, I would configure the server to *not*
automatically reboot when a critical STOP error occurs (in Control
Panel - System). Next time it crashes, it will show you a Blue
Screen of Death. Write down the STOP error code, the parameters,
and possibly the name of the driver causing the STOP error.

Either post this information here, or check the troubleshooting
tools for this particular STOP error in the
MSDN Bug Check Codes pages at
http://msdn.microsoft.com/library/default.asp?url=/library/en-
us/ddtools/hh/ddtools/bcintro_3dkj.asp

More information:

Windows Server 2000 Resource Kit - Troubleshooting Strategies
http://www.microsoft.com/resources/documentation/windows/2000/serv
er/reskit/en-us/serverop/part4/sopch14.mspx

Windows 2000 STOP Messages:
http://www.microsoft.com/resources/documentation/windows/2000/prof
essional/reskit/en-us/part7/proch33.mspx

Analysis the BSOD (Blue Screen of Death) with DUMPEXAM
http://www.i386.com/default.asp?c=8&p=933

 

[Guest]

Vera
Thanks, with your advice I was able to locate the "service" that was causing the problem NS.EXE. I did research that and could not find any information, may be was a spy ware installed there some how “ my guessâ€. I did remove/deleted all the instances where that appeared, registry included. After that, TS seems to be up in running stable and connecting there was no problem again.

Thanks Again
Ard M