Re: Connection Error when Rebooting
- From: NONU <NONU@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Wed, 25 Apr 2007 07:46:03 -0700
Even i also have the same problem with our environment,but the problem is if
any user who has RDP into the server gives the restart some times (70%
restarts have the same fate) what happens that terminal services don't
respond next time we try to RDp into it..
Then we have to manually login into the console and issue a reboot and once
server comes up everthing works fine.. this problem has been persisting for
quite a while now.. over a year.. and we have no answer to it..except reboot
the server and as mentioned before it is happening with the NON Ts servers
enable in remote administartion mode..
Do you feel that Tsshutdn /restart can help us in resolving the issue..?
Thoughts?
"TP" wrote:
Hi,.
I was addressing Hank's question more so than your
particular issue. I am not saying you cannot use
Start-->Shutdown-->Restart, just the opposite.
Most likely there is something running on your servers that is
cancelling/stopping the shutdown. I think it is happening at a
point in the process after TS connections are disabled, which
would explain the behavior you are noticing.
Using the /F option prevents a process from stopping a
shutdown by responding false or not at all--each process is
terminated regardless. Even with /F there are cases where a
kernel mode driver or other core windows process could
prevent the shutdown from completing.
Do you have any warnings in the event log similar to this:
********************
Source: USER32
Event ID: 1073
Description:
The attempt by user <domain\username> to restart/shutdown computer
<computer> failed
********************
What third-party software do you have running on the server
as a windows service? For example, antivirus, backup agents, etc.
At the time you attempt to restart, is there any user logged on to
the console, either remotely via an RDP console session, or
physically at the console?
Can you think of anything about what is running on your servers
or their configuration that is different from default settings? Try
and think in terms of what is different from someone who *only*
had the windows 2003 cd (no other software), and simply
configured things as much as possible by clicking Next in the
wizards for the various components.
If you can describe some of these differences that may help me
direct you where to investigate. This could be a bug in windows.
If there is one of your servers that has this problem frequently,
you could run tests by stopping certain services and then seeing if
the restart happens without fail.
Below is some information that will help you understand the
shutdown process:
Application Shutdown Changes in Windows Vista
http://msdn2.microsoft.com/en-us/library/ms700677.aspx
WM_QUERYENDSESSION
http://msdn2.microsoft.com/en-us/library/aa376890.aspx
System Shutdown Functions
http://msdn2.microsoft.com/en-us/library/aa376883.aspx
-TP
Dan wrote:
All of this info is appreciated, but I'm not sure either deals with
the direct issue that I have. Are all of you saying that I can't
simply go to Start > Shut Down > Restart? That seems a bit
ridiculous. The regular shutdown command works fine for me when I
use the /F option, but I don't want to do that during every restart.
By the way, this happens on non terminal servers that simply have
remote administration turned on as well.
- Prev by Date: Re: Terminal Services GPO apply based on client computer
- Next by Date: Re: how to increase number of users
- Previous by thread: Terminal Services GPO apply based on client computer
- Next by thread: Re: AntiVirus Problems with Terminal Server 2003
- Index(es):
Relevant Pages
|
Loading
