Questions

Remote Desktop

+
0 Votes
Locked

Remote Desktop

pentrex
I set SOHO in our building : Lyncsis router, a printer and four PCs. I established the Remote Desktop connection with one of computers located in the other end of our building. Everything was fine. But when I tried to connect the Remote Desktop to my computer in my office from that remote one, I failed to do that.

I checked all settings on both PCs Firewalls, settings in the router's Firewall, checked both accounts have permissions to operate the Remote Desktop, but no matter what I tried I still cannot get the Remote Desktop connection from that computer. It works only in one direction. I use dynamic IP addressing in the router and double checked the addresses on both PCs.

Anyone can explain what's going on?
  • +
    0 Votes
    OH Smeg

    You are attempting to reach a computer through a Router at your end and at the other end right?

    If that's the case you need to establish a VPN between the 2 routers.

    Col

    +
    0 Votes
    pentrex

    That's right - reaching one computer at one end and from that end trying to reach the original computer and I can't. But I have only one router.

    Btw ,I tried the Remote assistance and it works fine both ways, but not the Remote Desktop. Do I still need VPN? Or this connection is not possible with just one router?

    +
    0 Votes
    OH Smeg

    Not in that case.

    I'll have a think on this and see what if anything I can come up with.

    Col

    +
    0 Votes
    TobiF

    What system versions do you have at both ends?
    (For example Windows Home versions don't act as RDP servers, but can be a client)

    +
    0 Votes
    pentrex

    At both ends XP Professional. Suppose to work both ways but it doesn't. But the Remote Assistance, btw having the same port 3389 as RDP, works fine.

    +
    0 Votes
    -nhone-

    In Windows XP Remote Desktop Connection is set to administrator with password.. try giving the user a permission to access remote desktop connection

    In Computer Properties - Remote Tab
    Allow user to connect remotely then select remote users. remote user must have password.

    +
    0 Votes
    pentrex

    Seems I tried this but will double check it again.

    +
    0 Votes
    pentrex

    Just checked in the Local Users and Groups console both accounts. Both are set to the administrative group. Both are members of the Remote Desktop Users. The Remote Tab in the System Properties certainly is checked otherwise I would have no connection in the first place. But the problem still remains the same- from the computer 1 to computer 2the RDP works OK, from the computer 2 to 1 it doesn't. Message I got - "This computer can't connect to the remote computer. Try connecting again".

    Just unexplainable puzzle what else might be wrong here?

    +
    0 Votes
    OH Smeg

    You may need to look at it's configuration to fix this issue.

    Col

    +
    0 Votes
    -nhone-

    Sounds like you have network authentication in your computer 1 check your local network connection in computer 1 try to un-check Enable IEEE 802.1x authentication in Authentication Tab.

    windows xp sp3 with .net3.5 doesn't work well in RDP try removing that if you ever install xp sp3 and .net3.5 that may cause the issue.

    and check terminal services for both computer if running in services console

    +
    0 Votes
    pentrex

    That exactly what I have - XP sp3 .net3.5 sp1, and .net3.0 sp2 installed on both computers.

    I 'll check what you said.

    What exactly do I need to remove? .net3.5 or sp3?

    +
    0 Votes
    seanferd

    No, don't roll back sp3.

    +
    0 Votes
    rkuhn

    Can you ping #1 from #2?

    Are you using the IP or computer name in RDC?

    Can you do a nslookup successfully? Tracert?

    Don't skip the basics...you may find something obvious like a misconfiguration at the router/switch level.

    +
    0 Votes
    pentrex

    I use IP in RDC

    Yes, I can ping from #1 to #2 and vice versa.

    There is no problems with tracert either from both ends.

    Nslookup gives the following output:

    ***Can't find server name for address 192.168.1.1: Non-existent domain
    ***Can't find server name for address 192.168.2.1: Non-existent domain
    ***Default servers are not available
    Server: Unknown
    Address: 192168.1.1
    ***Unknown can't find 192.168.1.103: Non-existent domain

    It's the same output from both ends except the last line where address of the second PC is 192.168.1.100.

    Is this looks like an error?

    +
    0 Votes

    RDP

    ganesan.kuppusamy

    Did u check the RDP port 3389, whether is opening or not. try doing
    telnet remotemachinename 3389 --> from the command prompt.

    http://serveradministrators.blogspot.com/

    +
    0 Votes
    pentrex

    I checked the 3389 port by using the Remote Assistance. Works fine from both ends.

    Isn't this enough?

    +
    0 Votes
    -nhone-

    Say you have ip configured to static ex. 192.168.10.2 mask 255.255.255.0 gw 192.168.10.1 for pc1 and 192.168.10.3 mask 255.255.255.0 gw 192.168.10.1 for pc2

    try access to rdp.. if you have different gateway make a routing point from default gw to destination

  • +
    0 Votes
    OH Smeg

    You are attempting to reach a computer through a Router at your end and at the other end right?

    If that's the case you need to establish a VPN between the 2 routers.

    Col

    +
    0 Votes
    pentrex

    That's right - reaching one computer at one end and from that end trying to reach the original computer and I can't. But I have only one router.

    Btw ,I tried the Remote assistance and it works fine both ways, but not the Remote Desktop. Do I still need VPN? Or this connection is not possible with just one router?

    +
    0 Votes
    OH Smeg

    Not in that case.

    I'll have a think on this and see what if anything I can come up with.

    Col

    +
    0 Votes
    TobiF

    What system versions do you have at both ends?
    (For example Windows Home versions don't act as RDP servers, but can be a client)

    +
    0 Votes
    pentrex

    At both ends XP Professional. Suppose to work both ways but it doesn't. But the Remote Assistance, btw having the same port 3389 as RDP, works fine.

    +
    0 Votes
    -nhone-

    In Windows XP Remote Desktop Connection is set to administrator with password.. try giving the user a permission to access remote desktop connection

    In Computer Properties - Remote Tab
    Allow user to connect remotely then select remote users. remote user must have password.

    +
    0 Votes
    pentrex

    Seems I tried this but will double check it again.

    +
    0 Votes
    pentrex

    Just checked in the Local Users and Groups console both accounts. Both are set to the administrative group. Both are members of the Remote Desktop Users. The Remote Tab in the System Properties certainly is checked otherwise I would have no connection in the first place. But the problem still remains the same- from the computer 1 to computer 2the RDP works OK, from the computer 2 to 1 it doesn't. Message I got - "This computer can't connect to the remote computer. Try connecting again".

    Just unexplainable puzzle what else might be wrong here?

    +
    0 Votes
    OH Smeg

    You may need to look at it's configuration to fix this issue.

    Col

    +
    0 Votes
    -nhone-

    Sounds like you have network authentication in your computer 1 check your local network connection in computer 1 try to un-check Enable IEEE 802.1x authentication in Authentication Tab.

    windows xp sp3 with .net3.5 doesn't work well in RDP try removing that if you ever install xp sp3 and .net3.5 that may cause the issue.

    and check terminal services for both computer if running in services console

    +
    0 Votes
    pentrex

    That exactly what I have - XP sp3 .net3.5 sp1, and .net3.0 sp2 installed on both computers.

    I 'll check what you said.

    What exactly do I need to remove? .net3.5 or sp3?

    +
    0 Votes
    seanferd

    No, don't roll back sp3.

    +
    0 Votes
    rkuhn

    Can you ping #1 from #2?

    Are you using the IP or computer name in RDC?

    Can you do a nslookup successfully? Tracert?

    Don't skip the basics...you may find something obvious like a misconfiguration at the router/switch level.

    +
    0 Votes
    pentrex

    I use IP in RDC

    Yes, I can ping from #1 to #2 and vice versa.

    There is no problems with tracert either from both ends.

    Nslookup gives the following output:

    ***Can't find server name for address 192.168.1.1: Non-existent domain
    ***Can't find server name for address 192.168.2.1: Non-existent domain
    ***Default servers are not available
    Server: Unknown
    Address: 192168.1.1
    ***Unknown can't find 192.168.1.103: Non-existent domain

    It's the same output from both ends except the last line where address of the second PC is 192.168.1.100.

    Is this looks like an error?

    +
    0 Votes

    RDP

    ganesan.kuppusamy

    Did u check the RDP port 3389, whether is opening or not. try doing
    telnet remotemachinename 3389 --> from the command prompt.

    http://serveradministrators.blogspot.com/

    +
    0 Votes
    pentrex

    I checked the 3389 port by using the Remote Assistance. Works fine from both ends.

    Isn't this enough?

    +
    0 Votes
    -nhone-

    Say you have ip configured to static ex. 192.168.10.2 mask 255.255.255.0 gw 192.168.10.1 for pc1 and 192.168.10.3 mask 255.255.255.0 gw 192.168.10.1 for pc2

    try access to rdp.. if you have different gateway make a routing point from default gw to destination