Archived from groups: microsoft.public.windowsxp.work_remotely (
More info?)
You might consider using a dynamic naming service like No-IP.com... A small program runs on one of
your home PCs and contacts the No-IP.com servers on a scheduled basis. The servers then know what
your current IP is and map that to a fully qualified domain name that you can use to call from a
remote site. I use this for access to my home LAN via VPN or Remote Desktop... It works very well
for me...and its FREE...
http://www.no-ip.com
Personally, I think it doubtful that TCP Port 3389 is blocked by Verizon outgoing from a residential
account, although anything is possible. I do know that some network administrators at work sites may
block pretty much everything outbound as a security measure...
I think its an issue with your router or addressing scheme when calling from a remote site.
What Linksys router are you using? Have you installed the latest firmware?
Also, note that when testing this from one PC to another PC on your local LAN that in most cases
using the public IP of your router will not work. You must use the local LAN IP or be at a remote
site and use the true public IP of the router.
--
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...
"jason" <jason@discussions.microsoft.com> wrote in message
news:59C74A1D-95D9-4EE1-9105-A2C518E3491F@microsoft.com...
> Sooner Al,
> You might be onto something. I have two computers at my work and two
> internet connections. They're both XP Home laptops that can connect either
> wired or wirelessly to either a T3 or a cable modem connections. I tried
> the the telnet test...
>
http://support.microsoft.com/default.aspx?scid=kb;en-us;Q187628 with either
> computer and with either connection and yet they all failed. Could it be
> posisble that both of my ISPs (the T3 and the cable modem) and a friend's
> house using Verizon DSL all block outgoing 3389 connections that would bring
> me to my home host computer?
> Jason
>
> "Sooner Al" wrote:
>
>> In addition to Jim's comments there two tests/tools you can use to troubleshoot this from a
>> remote
>> location...
>>
>> The telnet test...
>>
>>
http://support.microsoft.com/default.aspx?scid=kb;en-us;Q187628
>>
>> The MS Port Query tool...
>>
>>
http://support.microsoft.com/kb/832919
>>
http://www.microsoft.com/technet/community/columns/cableguy/cg0105.mspx
>>
http://www.microsoft.com/downloads/details.aspx?familyid=8355e537-1ea6-4569-aabb-f248f4bd91d0&displaylang=en
>>
>> You can see a few examples of its use in the "Troubleshooting" section on this page...
>>
>>
http://theillustratednetwork.mvps.org/RemoteDesktop/RemoteDesktopSetupandTroubleshooting.html
>>
>> --
>> 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...
>>
>> "Jim, MCSE" <Jim, MCSE@discussions.microsoft.com> wrote in message
>> news:1D3992F3-6FCD-4738-B5E4-4DCEBA2FFBA7@microsoft.com...
>> > It sounds like to me that the forwarding on the router is not setup properly.
>> > You say you can connect to your desktop through your laptop using wireless
>> > but your wireless connection is not going out to the internet then back in.
>> > It should be connecting over the LAN just using the wireless network instead
>> > of the wired. You need to make sure that on the router you make TCP 3389
>> > forward to the IP of your desktop. The way I set it up is make your desktop
>> > a static IP and then port forward to that IP. Then you should be able to
>> > connect from anywhere outside your network. I have seen problems with port
>> > forwarding when the router is setup to be a DHCP server for your network. So
>> > try giving it a static.
>> >
>> > Jim, MCSE
>> >
>> > "jason" wrote:
>> >
>> >> I have my home PC running Windows XP Pro with remote desktop properly setup.
>> >> I have a linksys wired/wireless router with port forwarding correctly set up
>> >> on port 3389. I know it works because I have a laptop running XP home that
>> >> connects wirelessly through the same router and can access the desktop. The
>> >> problem is that when I take the laptop to my office or to anywhere else for
>> >> that matter and attempt to connect to the home desktop, I get a client-side
>> >> protocol error that isn't letting me try to access the home PC running XP
>> >> pro. I know for a fact that the routers & firewalls & NAT settings at any of
>> >> these places that I try to connect from other than my home are not blocking
>> >> outbound access to port 3389. I figure it must be something with my router at
>> >> home. It is a DHCP IP address that is assigned by my cable-modem ISP but it
>> >> hasn't changed in ages since it used a long lease (I have confirmed over and
>> >> over that the IP hasn't changed by going to whatismyip.com). I also have
>> >> correctly set up the port forwarding in my linksys router to forward to the
>> >> appropriate device at home since the xp pro machine is plugged into the #2
>> >> slot (again I know this works since I am able to correctly connect to it from
>> >> the laptop while home ). My question is this: why can I connect to it
>> >> seamlessly from within my home network but not anywhere else?
>>
>>