Re: RDP Access Hung after reboot
- From: Krish <Krish@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Wed, 21 Nov 2007 13:18:03 -0800
Hi All,
i had a question here are we getting any specific error related to TS login.
it might be "Remote logins are currently disabled". If yes please let me know
because there is a hotfix for this in KB 842506
Thanks
Krish
"Ag IT Guy" wrote:
I've had the same issue when rebooting after installing Windows Updates and.
I'm not sure of the cause, but what solved the problem for me was initiating
a reboot using the shutdown command from the command line prompt. For some
reason it seems that Terminal Services don't start after a reboot sometimes.
If you find yourself unable to remote desktop into a server, go to the
command line and execute the following:
shutdown -r -m \\servername
"-r" specifies a reboot
"-m" following by \\ and then IP address or server name on the domain
RECOMMENDED:
Also use the option "-t XX" where XX is the time in seconds the server waits
to reboot. Allowing a few minutes of buffer time is a good measure to allow
for a safe shutdown and also gives you time to abort the shutdown if needed
(it happened to me and I'm glad I used that option..."-a" is the abort option)
Using the shutdown command means that the reboot is initiated by
winlogon.exe instead of wuauclt.exe (Windows Update) or some other process.
Hope this helps...
- References:
- RDP Access Hung after reboot
- From: News Group
- Re: RDP Access Hung after reboot
- From: Brock Hensley
- Re: RDP Access Hung after reboot
- From: News Group
- RDP Access Hung after reboot
- Prev by Date: EventID 53 source certsrv; Eventid 13 Autoenrollment failure (request subject name too long) 2003 server.. Pls Help..
- Next by Date: Re: Do I need defragment on server running RAID 5?
- Previous by thread: Re: RDP Access Hung after reboot
- Next by thread: Re: RDP Access Hung after reboot
- Index(es):
Relevant Pages
|