"Sooner Al [MVP]" wrote:

> "Todd" <T***@discussions.microsoft.com> wrote in message
> news:816DBBE4-9B20-4F9A-8FE2-A1B311EA9814@microsoft.com...
> > Trying to connect between work and home w/ xp pro at home and xp home at
> > work
> > (realizing that I cannot go from pro version to home version ). I can
> > connect
> > to other computers on our LAN at work remotely but when I try to dial into
> > home I get the error message: client cannot connect may be too busy try
> > again
> > later etc... both locations have  linksys routers. Does remote desktop
> > automatically configure the router to allow computers in? Or do I manually
> > have to change a setting on the router... if so how?
>
> You need TCP Port 3389 open on your router at the home end. Call the home PC
> using the public IP of the router, ie. the IP assigned by your home ISP.
>
> http://theillustratednetwork.mvps.org/RemoteDesktop/RemoteDesktopSetupandTroubleshooting.html
> http://theillustratednetwork.mvps.org/RemoteDesktop/RDP6ConfigRecommendations.html
>
> Ignore the references to UDP Port 3389 on the following pages...You only
> need TCP Port 3389...
>
> http://www.portforward.com/english/applications/port_forwarding/Remote_Desktop/Remote_Desktopindex.htm
>
> I also suggest consulting with your work network administrators. There may
> be company policies against connecting an untrusted system (your home PC) to
> a trusted network (your office LAN and PC).
>
> --
>
> 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...
>

"Todd" <T***@discussions.microsoft.com> wrote in message
news:EC86525B-1B93-4103-8720-0D472FF6B92E@microsoft.com...
> great I will try that now...
> same procedure going from home to work? same router linksys... different
> computer connecting to at work (xp pro)
> and if so do I have to specify the exact ip address of the work computer
> in
> the port forwarding procedure (it's set up as a static ip so I know it
> will
> periodically change)
> again I know there are security issues but the host computer does need a
> password to be accessed
> -by the way that port forwarding website was exactly what I have been
> looking for, it was great
>

"Sooner Al [MVP]" wrote:

> "Todd" <T***@discussions.microsoft.com> wrote in message
> news:EC86525B-1B93-4103-8720-0D472FF6B92E@microsoft.com...
> > great I will try that now...
> > same procedure going from home to work? same router linksys... different
> > computer connecting to at work (xp pro)
> > and if so do I have to specify the exact ip address of the work computer
> > in
> > the port forwarding procedure (it's set up as a static ip so I know it
> > will
> > periodically change)
> > again I know there are security issues but the host computer does need a
> > password to be accessed
> > -by the way that port forwarding website was exactly what I have been
> > looking for, it was great
> >
>
> Yes, use the same procedure. Its also possible to run Remote Desktop through
> a VPN or SSH tunnel for added security if your work network administrators
> only let you connect that way...
>
> --
>
> 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...
>

"Todd" wrote:

> excellent.. yes thank you... you've been great help
>
> "Sooner Al [MVP]" wrote:
>
> > "Todd" <T***@discussions.microsoft.com> wrote in message
> > news:EC86525B-1B93-4103-8720-0D472FF6B92E@microsoft.com...
> > > great I will try that now...
> > > same procedure going from home to work? same router linksys... different
> > > computer connecting to at work (xp pro)
> > > and if so do I have to specify the exact ip address of the work computer
> > > in
> > > the port forwarding procedure (it's set up as a static ip so I know it
> > > will
> > > periodically change)
> > > again I know there are security issues but the host computer does need a
> > > password to be accessed
> > > -by the way that port forwarding website was exactly what I have been
> > > looking for, it was great
> > >
> >
> > Yes, use the same procedure. Its also possible to run Remote Desktop through
> > a VPN or SSH tunnel for added security if your work network administrators
> > only let you connect that way...
> >
> > --
> >
> > 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...
> >

"Todd" wrote:

> excellent.. yes thank you... you've been great help
>
> "Sooner Al [MVP]" wrote:
>
> > "Todd" <T***@discussions.microsoft.com> wrote in message
> > news:EC86525B-1B93-4103-8720-0D472FF6B92E@microsoft.com...
> > > great I will try that now...
> > > same procedure going from home to work? same router linksys... different
> > > computer connecting to at work (xp pro)
> > > and if so do I have to specify the exact ip address of the work computer
> > > in
> > > the port forwarding procedure (it's set up as a static ip so I know it
> > > will
> > > periodically change)
> > > again I know there are security issues but the host computer does need a
> > > password to be accessed
> > > -by the way that port forwarding website was exactly what I have been
> > > looking for, it was great
> > >
> >
> > Yes, use the same procedure. Its also possible to run Remote Desktop through
> > a VPN or SSH tunnel for added security if your work network administrators
> > only let you connect that way...
> >
> > --
> >
> > 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...
> >

"Sooner Al [MVP]" wrote:

> "Todd" <T***@discussions.microsoft.com> wrote in message
> news:072A703C-BCFF-4CB5-A9ED-F7988BAD380B@microsoft.com...
> > oh and I signed on to canyouseeme.org and there says there's an error
> > message
> > trying to se that port for remote desktop and then shows what looks to be
> > the
> > outside router ip address
> >
>
> Make sure that when you test at home from another PC on your local LAN that
> you call using the private IP of the PC you want to connect to. Its not a
> valid test if you use the public IP...
>
> http://theillustratednetwork.mvps.org/RemoteDesktop/TroubleshootingDiagrams/Basic.html
>
> To properly test the public IP you need to be at a remote location.
>
> If the canyouseeme test fails from the PC you want to access and the local
> test, detailed above, passes then it comes down to a port forwarding issue
> in the router or your running a firewall somewhere that is blocking TCP Port
> 3389 incoming.
>
> --
>
> 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...
>

"Todd" <T***@discussions.microsoft.com> wrote in message
news:CAE5409C-F797-41B8-BB48-58E50B6529A1@microsoft.com...
> tried connecting from another computer in my house on the lan  using the
> private ip address of the host computer and it times out on the
> connection...
> also... when trying to connect from the outside source... I should be
> using
> the private ip address found in the cmd ipconfig/all section correct? not
> the
> public ip address of the router
>
> "Sooner Al [MVP]" wrote:
>
>> "Todd" <T***@discussions.microsoft.com> wrote in message
>> news:072A703C-BCFF-4CB5-A9ED-F7988BAD380B@microsoft.com...
>> > oh and I signed on to canyouseeme.org and there says there's an error
>> > message
>> > trying to se that port for remote desktop and then shows what looks to
>> > be
>> > the
>> > outside router ip address
>> >
>>
>> Make sure that when you test at home from another PC on your local LAN
>> that
>> you call using the private IP of the PC you want to connect to. Its not a
>> valid test if you use the public IP...
>>
>> http://theillustratednetwork.mvps.org/RemoteDesktop/TroubleshootingDiagrams/Basic.html
>>
>> To properly test the public IP you need to be at a remote location.
>>
>> If the canyouseeme test fails from the PC you want to access and the
>> local
>> test, detailed above, passes then it comes down to a port forwarding
>> issue
>> in the router or your running a firewall somewhere that is blocking TCP
>> Port
>> 3389 incoming.
>>
>> --
>>
>> 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...
>>