Unable to connect using RDP

Sponsored Links

I have a Windows Server 2003 R2 Standard Edition x64 server as one of my
domain controllers. I have Remote Desktop enabled on it for the domain
admin account.

Recently I've been unable to connect using RDP. The server itself is
listening on port 3389, and I can telnet to the server's IP on this port and
establish a connection. However when I try to connect using my RDP client I
receive the following error:

--------------------------------------
Remote Desktop Disconnected

This computer can't connect to the remote computer.
Try connecting again. If the problem continues, contact the owner of the
remote computer or your network administrator.
--------------------------------------

I see nothing in my System or Application event logs indicating the failure.
I've tried disabling and re-enabling the Remote Desktop feature on the
Remote tab in the System Properties, but it fails to make a difference. Any
thoughts? Thanks.


Joe

Update the RDP client on the workstation to the latest version available
from Windows Update, I believe it's 6.0. There's a versioning issue with RDP
clients prior to R2 that produces the error you're reporting.

HTH

Laura E. Hunter - MVP: Windows Server - Networking

"Joe Grover" <grover.joe@acd.net> wrote in message
news:enbdWz6THHA.4188@TK2MSFTNGP06.phx.gbl...
>I have a Windows Server 2003 R2 Standard Edition x64 server as one of my
>domain controllers. I have Remote Desktop enabled on it for the domain
>admin account.
>
> Recently I've been unable to connect using RDP. The server itself is
> listening on port 3389, and I can telnet to the server's IP on this port
> and establish a connection. However when I try to connect using my RDP
> client I receive the following error:
>
> --------------------------------------
> Remote Desktop Disconnected
>
> This computer can't connect to the remote computer.
> Try connecting again. If the problem continues, contact the owner of the
> remote computer or your network administrator.
> --------------------------------------
>
> I see nothing in my System or Application event logs indicating the
> failure. I've tried disabling and re-enabling the Remote Desktop feature
> on the Remote tab in the System Properties, but it fails to make a
> difference. Any thoughts? Thanks.
>
>
> Joe
>
>

Unfortunately I was hoping the problem was that I was using the latest RDP
(which I am). It's odd that both DC's are the exact same hardware (Proliant
DL140's) installed within an hour of each other with the same media and
identical configuration (except one is a global catalog server), and I can
connect to one but not the other. :/

If it helps any, the RDP client on the server can't connect to itself
either.


"Laura E. Hunter [MVP]" <laurahcomputing.nospam@gmail.com> wrote in message
news:us84Wd7THHA.5068@TK2MSFTNGP03.phx.gbl...
> Update the RDP client on the workstation to the latest version available
> from Windows Update, I believe it's 6.0. There's a versioning issue with
> RDP clients prior to R2 that produces the error you're reporting.
>
> HTH
>
> Laura E. Hunter - MVP: Windows Server - Networking
>
> "Joe Grover" <grover.joe@acd.net> wrote in message
> news:enbdWz6THHA.4188@TK2MSFTNGP06.phx.gbl...
>>I have a Windows Server 2003 R2 Standard Edition x64 server as one of my
>>domain controllers. I have Remote Desktop enabled on it for the domain
>>admin account.
>>
>> Recently I've been unable to connect using RDP. The server itself is
>> listening on port 3389, and I can telnet to the server's IP on this port
>> and establish a connection. However when I try to connect using my RDP
>> client I receive the following error:
>>
>> --------------------------------------
>> Remote Desktop Disconnected
>>
>> This computer can't connect to the remote computer.
>> Try connecting again. If the problem continues, contact the owner of the
>> remote computer or your network administrator.
>> --------------------------------------
>>
>> I see nothing in my System or Application event logs indicating the
>> failure. I've tried disabling and re-enabling the Remote Desktop feature
>> on the Remote tab in the System Properties, but it fails to make a
>> difference. Any thoughts? Thanks.
>>
>>
>> Joe
>>
>>
>
>