The Notebook Review forums were hosted by TechTarget, who shut down them down on January 31, 2022. This static read-only archive was pulled by NBR forum users between January 20 and January 31, 2022, in an effort to make sure that the valuable technical information that had been posted on the forums is preserved. For current discussions, many NBR forum users moved over to NotebookTalk.net after the shutdown.
Problems? See this thread at archive.org.

    [Remote Desktop]already port followed, but not working :S

    Discussion in 'Networking and Wireless' started by Kossel, Apr 7, 2010.

  1. Kossel

    Kossel Notebook Evangelist

    Reputations:
    120
    Messages:
    356
    Likes Received:
    0
    Trophy Points:
    30
    target ipconfig:
    ipv4 .. .... 192.168.1.66
    mask subnet.....255.255.255.0
    default gateway...192.168.1.254

    I did the following:

    -forward port 3389 (tcp and udp)
    -set "ip to forward" to the target computer's ip (192.168.1.66)
    - I got successful message in www.canyouseeme.org with port 3389
    -work in LAN

    but in a external network, i can ping it, but when i tried to connect using windows remote desktop it says not response

    any idea??
     
  2. blue68f100

    blue68f100 Notebook Virtuoso

    Reputations:
    1,020
    Messages:
    3,439
    Likes Received:
    0
    Trophy Points:
    105
    Personal Firewall blocking it?
     
  3. ronnieb

    ronnieb Representing the Canucks

    Reputations:
    613
    Messages:
    1,869
    Likes Received:
    0
    Trophy Points:
    55
    Are both computers connected to the same network? Did you allow both of them to be remotely controlled (Setting?)
     
  4. makaveli72

    makaveli72 Eat.My.Shorts

    Reputations:
    1,235
    Messages:
    2,108
    Likes Received:
    0
    Trophy Points:
    55
    I think you might be missing something OP. I hope you are not trying to Remote from outside your LAN (externally) by using the 192.168.1.66 IP Address. That is Local only, and will only work Locally on your LAN; unless VPN is set up or something.

    Otherwise, you will need to use your Network's WAN/Public/Internet IP Address. 192.168.X.X is a Private IP Address. You can go to http://www.speakeasy.net/speedtest/ for ex. to see your Internet IP Address.

    The Internet IP Address is what you should be using to connect from outside your Local Area Network. And it should be a Static IP Address. Meaning an IP Address that does not change. If it changes then you will need to use a service such as DynDNS to map your Internet IP Address to a domain name. So you will enter the domain name in Remote Desktop to connect to your LAN from outside your network.

    Connecting on LAN vs. Remotely from Outside are two different things.
     
  5. Kossel

    Kossel Notebook Evangelist

    Reputations:
    120
    Messages:
    356
    Likes Received:
    0
    Trophy Points:
    30
    thanks for reply!

    - I have personal firewall disabled (the windows's one, and the router's)
    - and yes I m trying to remote externally but using a public IP address (actually I'm using DynDNS)

    I also tried this:
    Eg. my pc public's public ip is 189.148.xxx.yyy and has ip 192.168.1.66
    when I tried to remote in a LAN, both 189.148.xxx.yyy and 192.168.1.66 work
    but when I'm outside LAN, that public ip is not responding the connection request :S
     
  6. makaveli72

    makaveli72 Eat.My.Shorts

    Reputations:
    1,235
    Messages:
    2,108
    Likes Received:
    0
    Trophy Points:
    55
    I see. Well then maybe the computer you're trying to remote from is having the RDP OUT connection blocked by a Firewall. Maybe Hardware Firewall? where are you trying to remote in from? Is it possible to try to remote in from a completely different computer on a different network/location?

    And can you print screen or type the exact error you receive from RDC. That might hint on what the problem may be.