MSTerminalServices.org Forums

Forums Home | FAQ | Search | Profile | Private Messages | Log in/Register/Password

Windows Server 2003 Reboot after connection Remote Desktop

Page 1 of 1
Next:  General Discussions: 2 security issues regarding terminal services  
Author Message
piet.vermeir

External


Since: Nov 06, 2006
Posts: 3



(Msg. 1) Posted: Mon Nov 06, 2006 10:54 am
Post subject: Windows Server 2003 Reboot after connection Remote Desktop
Archived from groups: microsoft>public>windows>terminal_services (more info?)

Hi everyone

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 schema style:

1) through KVM-switch view
2) connection remote desktop
3) disconnect remote desktop
4) trough KVM-switch view
5) reboot

Many thanks in advance.
Back to top
Send e-mail Login to vote
TP

External


Since: Mar 16, 2005
Posts: 1449



(Msg. 2) Posted: Mon Nov 06, 2006 2:43 pm
Post subject: Re: Windows Server 2003 Reboot after connection Remote Desktop [Login to view extended thread Info.]
Archived from groups: per prev. post (more info?)

Any related entries in the event log around the time of the reboot?

For example, something from source Save Dump indicating that
"The computer has rebooted from a bugcheck."?

Or perhaps an entry from source EventLog indicating that the
previous system shutdown was unexpected?

What are your Startup and Recovery options set to?

Is your colleague connecting to the server console via RDP, or
a non-console session?

Are you and your colleague using the same windows account
to logon to the server?

When exactly does the server reboot? How far in the logon
process are you able to get before it reboots?

-TP

piet.vermeir DeleteThis @palmbreweries.com wrote:
> Hi everyone
>
> 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 schema style:
>
> 1) through KVM-switch view
> 2) connection remote desktop
> 3) disconnect remote desktop
> 4) trough KVM-switch view
> 5) reboot
>
> Many thanks in advance.
Back to top
Send e-mail Login to vote
Laurent Falguiere

External


Since: Nov 06, 2006
Posts: 5



(Msg. 3) Posted: Mon Nov 06, 2006 9:16 pm
Post subject: Re: Windows Server 2003 Reboot after connection Remote Desktop [Login to view extended thread Info.]
Archived from groups: per prev. post (more info?)

Hi

Did you check this article:
You may receive a "Stop 0x000000ab" error message when you log off a
Terminal Services session on a Windows Server 2003 SP1-based Terminal Server
http://support.microsoft.com/kb/901150/en-us

--
Laurent FALGUIERE
www.laurentfalguiere.fr
--
<piet.vermeir DeleteThis @palmbreweries.com> a écrit dans le message de news:
1162828471.203890.294010 DeleteThis @h54g2000cwb.googlegroups.com...
> Hi everyone
>
> 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 schema style:
>
> 1) through KVM-switch view
> 2) connection remote desktop
> 3) disconnect remote desktop
> 4) trough KVM-switch view
> 5) reboot
>
> Many thanks in advance.
>
Back to top
Send e-mail Login to vote
piet.vermeir

External


Since: Nov 06, 2006
Posts: 3



(Msg. 4) Posted: Tue Nov 07, 2006 4:42 am
Post subject: Re: Windows Server 2003 Reboot after connection Remote Desktop [Login to view extended thread Info.]
Archived from groups: per prev. post (more info?)

Hi TP

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:

> Any related entries in the event log around the time of the reboot?
>
> For example, something from source Save Dump indicating that
> "The computer has rebooted from a bugcheck."?
>
> Or perhaps an entry from source EventLog indicating that the
> previous system shutdown was unexpected?
>
> What are your Startup and Recovery options set to?
>
> Is your colleague connecting to the server console via RDP, or
> a non-console session?
>
> Are you and your colleague using the same windows account
> to logon to the server?
>
> When exactly does the server reboot? How far in the logon
> process are you able to get before it reboots?
>
> -TP
>
> piet.vermeir.DeleteThis@palmbreweries.com wrote:
> > Hi everyone
> >
> > 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 schema style:
> >
> > 1) through KVM-switch view
> > 2) connection remote desktop
> > 3) disconnect remote desktop
> > 4) trough KVM-switch view
> > 5) reboot
> >
> > Many thanks in advance.
Back to top
Send e-mail Login to vote
TP

External


Since: Mar 16, 2005
Posts: 1449



(Msg. 5) Posted: Wed Nov 08, 2006 1:51 pm
Post subject: Re: Windows Server 2003 Reboot after connection Remote Desktop [Login to view extended thread Info.]
Archived from groups: per prev. post (more info?)

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:

Windows Server 2003 Troubleshooting Stop Errors

http://www.microsoft.com/downloads/details.aspx?FamilyID=859637b4-85f1...15-b7d0

The above document will help you find more information
about the error, as well as track down the cause.

Also, refer to the Windows Server 2003 Troubleshooting
Guide (part of the 2003 Resource Kit) for related
information.

-TP

piet.vermeir.TakeThisOut@palmbreweries.com wrote:
> Hi TP
>
> 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.
>
>
Back to top
Send e-mail Login to vote
piet.vermeir

External


Since: Nov 06, 2006
Posts: 3



(Msg. 6) Posted: Thu Nov 09, 2006 9:22 am
Post subject: Re: Windows Server 2003 Reboot after connection Remote Desktop [Login to view extended thread Info.]
Archived from groups: per prev. post (more info?)

TP

We always use Remote Desktop to connect to a server.
I've tried your workaround with the option of automatically restart
disabled. Now I get an Blue screen of Death. Which I didn't get before.

On that screen I have the message: BAD_POOL_CALLER. I've search in the
document that you gave me and now I know it can be an hardware problem
or a driver problem. That's what I have to search for now.

So If I don't get any further, you here from me.
Anyway, many thanks for helping me.

Greetz
Piet


TP schreef:

> 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:
>
> Windows Server 2003 Troubleshooting Stop Errors
>
> http://www.microsoft.com/downloads/details.aspx?FamilyID=859637b4-85f1...15-b7d0
>
> The above document will help you find more information
> about the error, as well as track down the cause.
>
> Also, refer to the Windows Server 2003 Troubleshooting
> Guide (part of the 2003 Resource Kit) for related
> information.
>
> -TP
>
> piet.vermeir RemoveThis @palmbreweries.com wrote:
> > Hi TP
> >
> > 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.
> >
> >
Back to top
Send e-mail Login to vote
TP

External


Since: Mar 16, 2005
Posts: 1449



(Msg. 7) Posted: Thu Nov 09, 2006 1:09 pm
Post subject: Re: Windows Server 2003 Reboot after connection Remote Desktop [Login to view extended thread Info.]
Archived from groups: per prev. post (more info?)

Thank you for posting back with your progress.

Windbg will tell you more about the source of
the problem.

You should also search the MS knowledge base for
BAD_POOL_CALLER to see if they have a hotfix
available that fits your issue.

Since the server crashes when you logon via a KVM
switch, I would start with the video driver, but that
is a guess.

In general I would contact the hardware vendor(s)
about the issue as well as update firmware, drivers,
etc.

If none of the above solves it consider opening a
ticket with PSS. They can analyze the crash dump
and help you with troubleshooting. If it turns out to
be a Microsoft bug, there would be no charge.

Good luck!

-TP

piet.vermeir RemoveThis @palmbreweries.com wrote:
> TP
>
> We always use Remote Desktop to connect to a server.
> I've tried your workaround with the option of automatically restart
> disabled. Now I get an Blue screen of Death. Which I didn't get
> before.
>
> On that screen I have the message: BAD_POOL_CALLER. I've search in the
> document that you gave me and now I know it can be an hardware problem
> or a driver problem. That's what I have to search for now.
>
> So If I don't get any further, you here from me.
> Anyway, many thanks for helping me.
>
> Greetz
> Piet
>
Back to top
Send e-mail Login to vote
Display posts from previous:   
    All times are: Eastern Time (US & Canada) (change) Page 1 of 1

 
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum

Looking for more Terminal Services info?

Sign up to the MSTerminalServices.org Monthly Newsletter, written by Terminal Server MVP & Citrix CTP Stefan Vermeulen, containing news, tips, interviews, links of the month and much more. Subscribe today and don't miss a thing!

Become an MSTerminalServices.org member!

Discuss your Terminal Services & Citrix issues with thousands of other SBC experts. Click here to join!

Community Area

Log in | Register