I have 2 Windows 2003 Server SP2 machines that lose all RDC capability after
a reboot. If I am working on one of them, and reboot it, RDC no longer
works. I can ping it, I can telnet to port 3389, I can view the event viewer
remotely, but RDC is dead. As soon as I click "connect" I instantly get "The
client could not connect to the remote computer. Remote connections might not
be enabled" error msg. I have checked that the Terminal Services service is
running, I have even restarted it, everything looks to be fine. Even the
console command wont work. I then have to initiate a remote reboot command
(shutdown -i) to bounce the server, once it comes back up, I can connect
fine. Its consistant with both servers, I need to reboot them twice for RDC
to work. Has anyone come across this issue? Any fixes?
Vera Noest [MVP] - 12 May 2008 20:32 GMT
Check if this helps:
930045 - A Windows Server 2003-based computer stops responding when
you shut down the computer in a remote console session
http://support.microsoft.com/?kbid=930045
_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
___ please respond in newsgroup, NOT by private email ___
=?Utf-8?B?SmltYm9i?= <Jimbob@discussions.microsoft.com> wrote on
12 maj 2008 in microsoft.public.mac.rdc:
> I have 2 Windows 2003 Server SP2 machines that lose all RDC
> capability after a reboot. If I am working on one of them, and
[quoted text clipped - 10 lines]
> twice for RDC to work. Has anyone come across this issue? Any
> fixes?
jj2b4u - 30 Jun 2008 13:28 GMT
Jimbob, did the posted hotfix help you? I am experiencing the exact same
problem.
> I have 2 Windows 2003 Server SP2 machines that lose all RDC capability after
> a reboot. If I am working on one of them, and reboot it, RDC no longer
[quoted text clipped - 7 lines]
> fine. Its consistant with both servers, I need to reboot them twice for RDC
> to work. Has anyone come across this issue? Any fixes?