Archived from groups: microsoft.public.windowsxp.work_remotely (
More info?)
See step 4
--
Al Jarvi (MS-MVP Windows Networking)
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...
"CDCInvest" <CDCInvest@discussions.microsoft.com> wrote in message
news:052AC9F7-AB13-49D1-94DB-77131EAC5242@microsoft.com...
>I have a braodband connection that I connect to using a wireless router. I
> have personal firewalls on both machines, that I disabled while trying to get
> this to work. I followed all directions given to setup remote desktop but had
> problems when it came time to enter IP address, I found a Lan IP, WAN IP , a
> public IP using the site You provided and a router IP and I have no idea
> which one to use. I called my ISP and they said they use dynamic IP. I guess
> I'm a little confused about how easy microsoft makes it sound to install, yet
> finding IP's and rerouting ports is never mentioned.
>
> "Sooner Al" wrote:
>
>> Lets step back a bit and have you explain how...
>>
>> 1. The XP Pro PC your trying to connect to with Remote Desktop is connected to the internet, ie.
>> dialup, a broadband DSL or cable connection, etc.
>> 2. Is the XP Pro PC behind a firewall/NAT/router?
>> 3. Has Remote Desktop been enabled on the XP Pro PC your trying to connect to?
>>
>>
http://www.microsoft.com/windowsxp/using/mobility/getstarted/enableremote.mspx
>>
>> 4. Are you calling the correct public IP of the PC or the firewall/NAT/router?
>>
>> Go to either of the these two sites to get the public IP of your router from your desktop...
>>
>> http://www.whatismyip.com/
>> http://checkip.dyndns.org/
>>
>> If your ISP assigns a dynamic IP to your router, then another solution is to setup an account
>> with
>> one of the dynamic naming services that map a fully qualified domain name to the IP. In my case
>> I
>> use a FREE service from No-IP.com. The No-IP.com software runs on my XP Pro box and on a time
>> schedule basis contacts the No-IP.com servers. The No-IP.com servers then know what your IP is
>> and
>> maps that to a fully qualified domain name. That information is then propagated over the public
>> internet. You could then call the client PC using the fully qualified domain name. It works very
>> well for me when I call my home network using Remote Desktop.
>>
>>
http://www.no-ip.com
>>
>> 5. Depending on the router, if the XP Pro PC your trying to connect to with Remote Desktop is
>> behind
>> one, then you need to forward TCP Port 3389 to the private LAN IP of the PC...
>>
>>
http://www.portforward.com/routers.htm
>>
>> --
>> Al Jarvi (MS-MVP Windows Networking)
>>
>> 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...
>>
>> "CDCInvest" <CDCInvest@discussions.microsoft.com> wrote in message
>> news:0D626A27-65EB-4842-B562-DEF02A330D8E@microsoft.com...
>> >I am in the dark about networking issues like this one. On the Microsoft site
>> > it sounds easy to setup either method yet I cannot get either to work. For
>> > one I cannot figure out which ip address I need to use, one for my router or
>> > one for my computer I want to access. I have no idea where to find the name
>> > or address of my VPN server, which is required to setup a VPN connection. I
>> > have no idea what I need to do to allow access to the correct port 3398.
>> > For the remote desktop web connection, I need to know the Windows
>> > networking name of my server, again I have no idea where to find this info. I
>> > tried typing ipconfig/all from command prompt and there are several ip
>> > addresses, wins and dns information but I cannot seem to find the exact
>> > information I need to setup euther connection. Is there any othe instructions
>> > and tips for helpig with the setup of these connections?
>>
>>