Have you checked to see if TCP Port 3389 is open on any router and/or
firewall (including software firewalls) the PC is behind?

Is Remote Desktop enabled on the host/server PC?

http://theillustratednetwork.mvps.or...ubles hooting

--

Al Jarvi (MS-MVP Windows - Desktop User Experience)

Please post *ALL* questions and replies to the news group for the
mutual benefit of all of us...
The MS-MVP Program - http://mvp.support.microsoft.com
This posting is provided "AS IS" with no warranties, and confers no
rights...
How to ask a question
http://support.microsoft.com/KB/555375

"Justin Harding" <jharding13@msn.com> wrote in message
news:g22743$jo5$3@aioe.org...
>I have the remote IP address for my other system, but it still won't let me
>connect to it at all... I can't even connect via telnet on any ports, in
>fact it appears every port is closed...
>
> Any ideas ?
> "Sooner Al [MVP]" <SoonerAl@somewhere.net.invalid> wrote in message
> news:97CD6AFE-7362-47E3-BD42-854C734BB663@microsoft.com...
>> More than likely you will not be able to get the public IP without you or
>> someone being at the remote PC. If you can then from the PC you want to
>> remotely connect to go to the http://www.whatismyip.com site to get the
>> public IP.
>>
>> With that said many ISP provide dynamic IP addresses to residential
>> accounts. So even knowing the public IP at one instance will not help if
>> the PC is rebooted and the public IP changes. A way around that is to use
>> a free dynamic name service like No-IP.com or DynDNS that maps a fully
>> qualified domain name (FQDN) to the ISP assigned dynamic IP. That way
>> when or if the public IP changes the change is mapped to the FQDN. You
>> always call home using the FQDN.
>>
>> http://www.no-ip.com
>> http://www.dyndns.com
>>
>> Many routers have built-in support for those or you can download and
>> install a small program onto the home PC. The program runs in the
>> background and on a time scheduled basis contacts the server which then
>> maps the current public IP to the FQDN.
>>
>> Remember you also need to make sure TCP Port 3389 is forwarded through
>> any router the home PC is behind.
>>
>> --
>>
>> Al Jarvi (MS-MVP Windows - Desktop User Experience)
>>
>> Please post *ALL* questions and replies to the news group for the
>> mutual benefit of all of us...
>> The MS-MVP Program - http://mvp.support.microsoft.com
>> This posting is provided "AS IS" with no warranties, and confers no
>> rights...
>> How to ask a question
>> http://support.microsoft.com/KB/555375
>>
>> "Justin Harding" <jharding13@msn.com> wrote in message
>> news:g20ngr$561$3@aioe.org...
>>> I'am trying to establish a remote connection between my home computer,
>>> which is wireless, and my secondary home computer, at another location,
>>> but I have seemed to have run into some difficulty... The computer I'am
>>> trying to connect to seems to be behind a Wireless Router. it sends out
>>> a wireless signal, and is also a 192.168.0.0 IP address... How do I find
>>> the actual IP address for that system, since I cannot connect to that ID
>>> address which is what the router gave the system... when I have my home
>>> computer there on the wireless network (It's a laptop I'm using to
>>> connect with) it works fine, but as soon as my laptop is out of range
>>> and on a different wireless network I cannot connect to this system
>>> anymore...
>>>
>>>
>>> Can anyone help ?
>>>
>>> Thanks...
>>>
>>
>
>