Re: RDP Access Hung after reboot
- From: "Brock Hensley" <brock.hensley@xxxxxxxxxxxxxxxxxxx>
- Date: Thu, 15 Nov 2007 08:48:35 -0500
What error are you getting? Can't connect period or sessions full or
anything that would help diagnose
-B
"News Group" <news.group@xxxxxxxxxxx> wrote in message
news:OsQf5p4JIHA.5224@xxxxxxxxxxxxxxxxxxxxxxx
This has been happening more and more ever since the release of SP1 and
SP2. After a system reboot through scheduled tasks (tsshutdn /REBOOT), we
are not able to RDP into the server but the server is up and running (no
other issues). This doesn't happen every time but it seems to be more
frequent. The only way to fix it is to plug-in at the console and reboot
the server again. Restarting any RPC related services never helps. We
have a mixture of Windows 2003 Standard/Enterprise servers with all
updates applied and running the latest RDC console on servers and
workstations.
Does anyone else run into this problem and if so, any suggestion on how to
address this issue?
.
- Follow-Ups:
- Re: RDP Access Hung after reboot
- From: News Group
- Re: RDP Access Hung after reboot
- References:
- RDP Access Hung after reboot
- From: News Group
- RDP Access Hung after reboot
- Prev by Date: Ping packets during AD domain login?
- Next by Date: Re: RDP Access Hung after reboot
- Previous by thread: RDP Access Hung after reboot
- Next by thread: Re: RDP Access Hung after reboot
- Index(es):
Relevant Pages
|