1. You are viewing our forum as a guest. For full access please Register. WindowsBBS.com is completely free, paid for by advertisers and donations.

Remote Desktop Can't connect

Discussion in 'Networking (Hardware & Software)' started by ryorizzo, 2009/06/29.

  1. 2009/06/29
    ryorizzo

    ryorizzo Inactive Thread Starter

    Joined:
    2009/06/29
    Messages:
    6
    Likes Received:
    0
    When I try to connect (via Remote Desktop) to my home office PC from my laptop I get the following message:
    "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 "

    Both PCs are XP Pro SP3. The home office is a brand new Dell and the laptop is a recently reloaded Dell.

    I'm connecting thru a Netgear router that has port 3389 forwarded.
    The host is listening on port 3389.

    I can ping successfully using the IP address or the no-ip name.
    If I have both PCs in the same workgroup I can open files on either.

    I have even attempted to connect through my work PC at another location by using Remote Web into my work PC and then Remote Desktop back to my home office. I get the same message.

    Any ideas?
     
    ryorizzo,
    #1
  2. 2009/06/30
    Steve R Jones

    Steve R Jones SuperGeek Staff

    Joined:
    2001/12/30
    Messages:
    12,317
    Likes Received:
    252
    Welcome to WindowsBBS;)

    Control Panel->Firewall ->exception tab on both computers and make sure RD has been made an exception.
     
    Steve R Jones,
    #2


  3. to hide this advert.

  4. 2009/06/30
    ryorizzo

    ryorizzo Inactive Thread Starter

    Joined:
    2009/06/29
    Messages:
    6
    Likes Received:
    0
    Steve,

    Thanks for the quick reply. I had already checked that on the host. I just checked my laptop. Both have exceptions for RD on port 3389.

    Ray
     
    ryorizzo,
    #3
  5. 2009/06/30
    Arie

    Arie Administrator Administrator Staff

    Joined:
    2001/12/27
    Messages:
    15,174
    Likes Received:
    412
    Your office (hardware) firewall may not pass RD connections.
     
    Arie,
    #4
  6. 2009/06/30
    ryorizzo

    ryorizzo Inactive Thread Starter

    Joined:
    2009/06/29
    Messages:
    6
    Likes Received:
    0
    The only hardware between the two PCs is my router, which is set to forward the RD port.
     
    ryorizzo,
    #5
  7. 2009/06/30
    Arie

    Arie Administrator Administrator Staff

    Joined:
    2001/12/27
    Messages:
    15,174
    Likes Received:
    412
    Do you get an error message when you run telnet <IP address> 3389 from a command prompt?

    The <IP address> should be the address of the computer you try to connect to, and you should run the command on the computer where you are trying to initiate the RD connection from.
     
    Arie,
    #6
  8. 2009/06/30
    ryorizzo

    ryorizzo Inactive Thread Starter

    Joined:
    2009/06/29
    Messages:
    6
    Likes Received:
    0
    Telnet command returned the following error:
    "Connecting to <IP address> . . .Could not open connection to the host, on port 3389: Connect failed. "
    Ping to the same IP was successful
     
    ryorizzo,
    #7
  9. 2009/06/30
    Steve R Jones

    Steve R Jones SuperGeek Staff

    Joined:
    2001/12/30
    Messages:
    12,317
    Likes Received:
    252
    Try turning off the firewall to see if that helps.
     
    Steve R Jones,
    #8
  10. 2009/06/30
    ryorizzo

    ryorizzo Inactive Thread Starter

    Joined:
    2009/06/29
    Messages:
    6
    Likes Received:
    0
    Tried it - no help.
     
    ryorizzo,
    #9
  11. 2009/07/01
    sergeantash

    sergeantash Inactive

    Joined:
    2009/04/28
    Messages:
    25
    Likes Received:
    0
    Very simple suggestion, but you don't mention at any stage that you've actually enabled RDP on either of the machines?

    START -> CONTROL PANEL -> SYSTEM -> REMOTE

    Make sure that the bottom tickbox for Remote Desktop is ticked, also click REMOTE USERS and ensure that your user accounts are in there.

    Once done, give it another try - enabling Remote Desktop will automatically add exceptions into the firewall.

    Let us know how you get on!
     
    Last edited: 2009/07/01
    sergeantash,
    #10
  12. 2009/07/01
    Arie

    Arie Administrator Administrator Staff

    Joined:
    2001/12/27
    Messages:
    15,174
    Likes Received:
    412
    Run this command (Start > Run > cmd) on the computer you are trying to connect to:

    netstat -a -o and press [Enter]

    Look for an entry for TCP port 3389 with a State of Listening. Take a note of the Process Identifier (PID). The PID of the process or service using that port appears under the PID column.

    Next, type tasklist /svc (and press [Enter]). Look for an entry for the PID number that is associated with the port (from the netstat output). The services or processes associated with that PID will appear on the right.

    Post those details here.
     
    Arie,
    #11
  13. 2009/07/01
    Arie

    Arie Administrator Administrator Staff

    Joined:
    2001/12/27
    Messages:
    15,174
    Likes Received:
    412
    Hmmm... so we are talking about 2 PCs in the same location then? You are not passing through the Internet?

    Please explain the physical setup & which router is forwarding to which IP address & the IP addresses of the PC's involved (as well as the 'public' IP if the route traverses the Internet).
     
    Arie,
    #12
  14. 2009/07/01
    sergeantash

    sergeantash Inactive

    Joined:
    2009/04/28
    Messages:
    25
    Likes Received:
    0
    I don't think he's got it enabled - the router the two machines are connected through won't be doing anything other than providing switching between the two machines, therefore if its not Windows Firewall and the router isn't setup to do anything special, it can only be that RDP isn't enabled!

    We'll see I guess :)
     
    sergeantash,
    #13
  15. 2009/07/01
    Arie

    Arie Administrator Administrator Staff

    Joined:
    2001/12/27
    Messages:
    15,174
    Likes Received:
    412
    Yea, when I re-read the posts I see that some points needs to be cleared, that's why I asked for a description of the physical layout. Most users try connecting to friends/family (to offer help) which involves the Internet, but I have my doubts that's the case here... we'll wait & see for more info...
     
    Arie,
    #14
  16. 2009/07/01
    ryorizzo

    ryorizzo Inactive Thread Starter

    Joined:
    2009/06/29
    Messages:
    6
    Likes Received:
    0
    Netstat returns:
    Proto Local addr. Foreign addr State PID
    TCP [PC name]:3389 [PC name]:0 LISTENING 1016

    Tasklist /svc returns:
    Image Name PID Services
    svchost.exe 1016 DcomLaunch, TermService

    Currently both PC are connected via cable to the same Netgear router. The router has port 3389 forwarded.
     
    ryorizzo,
    #15
  17. 2009/07/02
    sergeantash

    sergeantash Inactive

    Joined:
    2009/04/28
    Messages:
    25
    Likes Received:
    0
    Please see the above post, and let us know whether its enabled...
     
    sergeantash,
    #16
  18. 2009/07/02
    sergeantash

    sergeantash Inactive

    Joined:
    2009/04/28
    Messages:
    25
    Likes Received:
    0
    You shouldn't need port forwarding on a local LAN unless you're got internal firewalling. This could actually be causing part of the problem, try removing this rule.
     
    sergeantash,
    #17

Share This Page

  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.
    Accept Learn More...