Windows Server 2003 Reboot after connection Remote Desktop

I have 2 servers with the same problem. Both of them are running
windows server 2003. The servers are connected with a KVM-switch. This
way of viewing the server’s desktops is only used by me. But if my
collegue connects with Remote desktop to the server and do his work and
disconnect. Then when I want to view the server, he reboots after I
have logged in. So We think it is a problem with sessions. We’ve
googled for different days, but doesn’t find the solution. Can anyone
help us? The second server has the identical problem.

In the event log, ther are no items around the time the server reboots.
Except the message that the server is rebooted unexpected. In that
message, there is no further information about the reboot.
My colleague is connecting to the server console via RDP no through a
non-console session.

Yes we logon with the same account but not on the same time. Purpose
that I logon on 10 o’clock with the kvm-switch. I stop working on the
server on 10:15. My colleague start RDP on 10:30 en stops on 10:45. On
11 o’clock I logon again with the kvm-switch. And on the moment the
server should show my desktop, he reboots. If I look on the eventlog,
there is nothing that says why the server has rebooted.

I hope you have enough information for further analysing of the
problem.

TP schreef:

Tp 2007-10-02 05:21:22

Just to verify, your colleague *is* connecting to the
console via RDP, correct? Connecting to the server’s
console is possible using the /console command
line switch, or using the Remote Desktops tool, which
has a “Connect to console” option.

As a workaround, have your colleague try the following:

1.) Open up Notepad and type the following two lines:

tscon 0 /dest:console
logoff

2.) Save the file to the desktop as tslogoff.cmd

3.) When logging off of the server, your colleague
should double-click the tslogoff.cmd file created above,
*instead* of Start–>Logoff.

——————–
When the server reboots, do you see a blue screen on
the server’s monitor?

You should determine if a STOP error (blue screen) is
occurring, or if the server is *only* rebooting. If a
STOP error is occurring, you can get the error number
and parameters and use this to figure out if there is a
hotfix available, or if you need to troubleshoot more
to find the cause.

What are your Startup and Recovery options set to?

You can check in System Properties–>Advanced–>Startup
and Recovery Settings

Is it set to create a small memory dump? If so, have you
checked if there is a dump file in c:\windows\Minidump?

Is it set to automatically restart? If you want you could
temporarily uncheck this so that if a STOP error happens,
the error information will stay on the server’s screen until
you manually reset the machine.

Please refer to the following document for help in
troubleshooting STOP errors: