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 Connection Problems

Discussion in 'Networking (Hardware & Software)' started by Spyderturbo, 2007/05/08.

  1. 2007/05/08
    Spyderturbo

    Spyderturbo Inactive Thread Starter

    Joined:
    2007/01/04
    Messages:
    41
    Likes Received:
    1
    I need some help with an unusual RDC problem. I have 2 seperate locations connected by a hardware VPN. Everything is working perfectly, except for some of the RDC connections. I have 2 DLink 804HV's handling the VPN and have no problems transferring files, sharing databases, etc. One side is set up with 192.168.0.1 and the other is using 192.168.1.1.

    I am, however, having problems with the RDC. I can connect from any PC on the 192.168.0.1 side to the server on the 192.168.1.1 side. But everytime I attempt to RDC from that PC to any PC other than the server is when the connection fails. I encounter the normal black screen, followed by the broken connection error.

    Here is the really weird part.....If I initiate a RDC from a PC to the server and then initiate another RDC from the server to a PC on the other side of the VPN it works. :eek: So, I have a RDC, inside of an RDC.

    Anyone have any clue what is going on????

    I hope that my post is understandable, but it's a hard situation to describe. Thanks!!!!
     
  2. 2007/05/09
    ReggieB

    ReggieB Inactive Alumni

    Joined:
    2004/05/12
    Messages:
    2,786
    Likes Received:
    2
    When you connect, do you specify the computer name or the IP address of the computer (both can work).
     

  3. to hide this advert.

  4. 2007/05/11
    Spyderturbo

    Spyderturbo Inactive Thread Starter

    Joined:
    2007/01/04
    Messages:
    41
    Likes Received:
    1
    I use IP address. I know there are name resolution problems over VPN and even though we don't have a problem with that, I prefer to use IP address.
     
  5. 2007/05/14
    ReggieB

    ReggieB Inactive Alumni

    Joined:
    2004/05/12
    Messages:
    2,786
    Likes Received:
    2
    There are two areas to look for a solution:
    1. Port access - it is possible that there is a firewall rule on the router that is blocking the ports used by remote desktop, to any PC other than the router. Check your firewall / port blocking rules on your firewall. It would also be worth checking any firewall rules active on the client PCs.
    2. Authentication - The PCs you connect to have to be set up to allow connection. It may be that the PCs are set to allow an admin access from the server, but not from other clients.
     
  6. 2007/05/14
    Scott Smith

    Scott Smith Inactive Alumni

    Joined:
    2002/01/12
    Messages:
    1,950
    Likes Received:
    4
    I'm thinking it's a permission issue.
     
  7. 2007/05/15
    Spyderturbo

    Spyderturbo Inactive Thread Starter

    Joined:
    2007/01/04
    Messages:
    41
    Likes Received:
    1
    How would I fix the permissions. When I attempted to access each PC, I used the login name of the administrator. It said in the dialog box "Admin already has access ". Is there something else I need to change.
     
  8. 2007/05/15
    ReggieB

    ReggieB Inactive Alumni

    Joined:
    2004/05/12
    Messages:
    2,786
    Likes Received:
    2
    Which dialogue? When you configure remote desktop or when you try to connect?

    Also don't forget that there are local admins and domain admins. It might be worth entering the domain name with the admin account name to avoid confusion with whether this is a local account or admin.

    domainname/Administrator and Administrator are two different accounts.
     
  9. 2007/05/15
    Spyderturbo

    Spyderturbo Inactive Thread Starter

    Joined:
    2007/01/04
    Messages:
    41
    Likes Received:
    1
    I was the dialog box that appeared when I was setting up the PC to allow remote access. We are also on a workgroup, but I'll try using the domain name along with the username.

    Thanks!
     
  10. 2007/06/12
    PaalN

    PaalN Inactive

    Joined:
    2007/06/11
    Messages:
    42
    Likes Received:
    0
    Looks like a firewall rule. Since you have broken connection icon. If it was perrmission you should get a error when you tried logging in.
    Looks like it has port 3389 open to 192.168.0.1/32 instead of 192.168.0.0/24
     

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.