Share via

Remote Desktop can't connect to the remote computer for one of these reasons:

Anonymous
2009-12-08T11:27:51+00:00

We are using Windows server 2003 sp2 & windows xp professional sp3. We would like to connect to the server using Remote Desktop, but we get the following error:

Remote Desktop can't connect to the remote computer for one of these reasons:

  1. Remote access to the server is not enabled
  2. The remote computer is turned off
  3. The remote computer is not available on the network

Make sure the remote computer is turned on and connected to the network, and that remote access is enabled.

We have enabled remote access on server & the user is member of admin & remote desktop users group on the server. The firewall is on & exception is allowed for Remote Desktop port 3389.

Could you please help us on this.

Windows Server Remote and virtual desktops Remote desktop services and terminal services

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question. To protect privacy, user profiles for migrated questions are anonymized.

0 comments
Accepted answer
  1. Anonymous
    2009-12-08T15:38:39+00:00

    try it with the firewall off.  If it works, you need to reconfigure the firewall.

    thanks,

    v

    M.V.P. - Desktop Experience | M.C.S.A. | M.C.P. - MS Server 2k3, Network Architecture

    305 people found this answer helpful.
    0 comments
Accepted answer
  1. Anonymous
    2011-01-21T21:43:30+00:00

    Hi ,

    Look for event logs on both Terminal Server and Local User PC

    Is this happening to all users ?

    • If you get an error in the TS then it is a client side issue.
    • Take TCP Dump using wire shark and see who is sendign RST packet.

    Search for that error message in google that might give you light.. !!

    Regards,

    Dhruv

    136 people found this answer helpful.
    0 comments

19 additional answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2011-02-02T16:06:33+00:00

    Thanks to all of you for your suggestions. Actually Firewall was the culprit. The firewall exceptions for port 3389 is not effective!!! If the firewall is turned off on client then the user can do remote login.

    0 comments
  2. Anonymous
    2011-03-12T12:50:49+00:00

    Check terminal services is running (mine was disabled for some reason) on the target/host computer.

    1 person found this answer helpful.
    0 comments
  3. Anonymous
    2011-07-22T00:20:04+00:00

    So I had a new Server 2008R2 Enterprise x64 and fell into the same black hole, after I'd done a bunch of our std new build configurations, which includes turning off Win firewall completely (on units inside our perimeter security).  Subsequently, RDP which was working, stopped.

    After a lot of puzzling around, I turned Domain firewall back on - and RDP worked, turned it off, RDP stopped.  Turns out in the domain confiuration pane, the default is all inbound blocked (subject presumably to ruls), and that was still respected when it was turned off (but now no rules).  By setting the default to ALLOW, then turning Domain firewall OFF, RDP continues to work

    Mike Wolfe

    1 person found this answer helpful.
    0 comments