Hello all,

I use a Linksys wireless router for my home network. I would like to be
able to use Remote Desktop to access my work computer but when I try to
connect, it fails. I canm establish a VPN connection but not successful with
RDC. When I remove the Linksys router, establishing a remote desktop
connection is successful. Any advice would be appreciative.

Thanks

Joe

I also am having some trouble and think Linksys may be involved. My work
(desktop) computer has XP pro and my internet guy used a linksys router for a
firewall. I am trying to connect to this desktop with my laptop that also
has XP pro, but after configuring remote desktop, I'm not able to connect. I
double-checked the configurations, could this Linksys firewall at my desktop
be the problem?
--
Thanks

Ken


"Joe" wrote:

> Hello all,
>
> I use a Linksys wireless router for my home network. I would like to be
> able to use Remote Desktop to access my work computer but when I try to
> connect, it fails. I canm establish a VPN connection but not successful with
> RDC. When I remove the Linksys router, establishing a remote desktop
> connection is successful. Any advice would be appreciative.
>
> Thanks
>
> Joe

You need to open TCP Port 3389 on the router.

http://theillustratednetwork.mvps.or...eshooting.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...


"KDrop" <(E-Mail Removed)> wrote in message
news:6CA67324-106F-469B-9525-(E-Mail Removed)...
>I also am having some trouble and think Linksys may be involved. My work
> (desktop) computer has XP pro and my internet guy used a linksys router
> for a
> firewall. I am trying to connect to this desktop with my laptop that also
> has XP pro, but after configuring remote desktop, I'm not able to connect.
> I
> double-checked the configurations, could this Linksys firewall at my
> desktop
> be the problem?
> --
> Thanks
>
> Ken
>
>
> "Joe" wrote:
>
>> Hello all,
>>
>> I use a Linksys wireless router for my home network. I would like to be
>> able to use Remote Desktop to access my work computer but when I try to
>> connect, it fails. I canm establish a VPN connection but not successful
>> with
>> RDC. When I remove the Linksys router, establishing a remote desktop
>> connection is successful. Any advice would be appreciative.
>>
>> Thanks
>>
>> Joe

When the VPN tunnel is established can you ping the desktop?

http://theillustratednetwork.mvps.or...eshooting.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...


"Joe" <(E-Mail Removed)> wrote in message
news:B7E0F62F-6F57-45FE-B85F-(E-Mail Removed)...
> Hello all,
>
> I use a Linksys wireless router for my home network. I would like to be
> able to use Remote Desktop to access my work computer but when I try to
> connect, it fails. I canm establish a VPN connection but not successful
> with
> RDC. When I remove the Linksys router, establishing a remote desktop
> connection is successful. Any advice would be appreciative.
>
> Thanks
>
> Joe

I have not attempted to ping the desktop and as for TCP port 3389, I have
forwarded that port in my Linksys router. Today at lunch I will tunnell in
and try to ping my office pc.

"Sooner Al [MVP]" wrote:

> When the VPN tunnel is established can you ping the desktop?
>
> http://theillustratednetwork.mvps.or...eshooting.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...
>
>
> "Joe" <(E-Mail Removed)> wrote in message
> news:B7E0F62F-6F57-45FE-B85F-(E-Mail Removed)...
> > Hello all,
> >
> > I use a Linksys wireless router for my home network. I would like to be
> > able to use Remote Desktop to access my work computer but when I try to
> > connect, it fails. I canm establish a VPN connection but not successful
> > with
> > RDC. When I remove the Linksys router, establishing a remote desktop
> > connection is successful. Any advice would be appreciative.
> >
> > Thanks
> >
> > Joe
>
>
>

Hi,

Joe wrote:
> I have not attempted to ping the desktop and as for TCP port 3389, I
> have forwarded that port in my Linksys router. Today at lunch I will
> tunnell in and try to ping my office pc.

Forwarding the port 3389 on your router at home is required if you want to
access your _home_computer_ remotely. It has nothing to do with your
ability to RDP "out", such as accessing your office computer from home.

I suspect your problem lies with (or relates to) the VPN, but would need
more information about it to suggest a solution. Unfortunately, there are
many possible VPN configurations, each of which creates a completely
different scenario. I am going to throw out a couple guesses, but would
really need you to describe your VPN setup in as much detail as possible.

If you are using RDP over VPN, where the VPN must be connected before you
can connect via remote desktop, and this works without the router, but not
with it -- then I would suggest that your VPN only appears to connect with
the router, but the supposedly established tunnel actually doesn't work.
This is not uncommon, especially with IPSEC VPN implementations. Many
routers simply don't pass the protocols through correctly.

Another common problem is the same private address block on both ends, e.g.
the popular 192.168.1.x block (which, if I am not mistaken, is the Linksys
default) also used on the internal network in your office. The result is
broken routing and the fix would be to reconfigure your router to use a
different block, such as 192.168.2.x.


--
Chris Priede

Chris,

This was a simple solution. I have changed my private ip address block at
home to reflect 192.168.2.x. RDP was successful.

Thanks again,

Joe


"Another common problem is the same private address block on both ends, e.g.
> the popular 192.168.1.x block (which, if I am not mistaken, is the Linksys
> default) also used on the internal network in your office. The result is
> broken routing and the fix would be to reconfigure your router to use a
> different block, such as 192.168.2.x."

"Chris Priede" wrote:

> Hi,
>
> Joe wrote:
> > I have not attempted to ping the desktop and as for TCP port 3389, I
> > have forwarded that port in my Linksys router. Today at lunch I will
> > tunnell in and try to ping my office pc.
>
> Forwarding the port 3389 on your router at home is required if you want to
> access your _home_computer_ remotely. It has nothing to do with your
> ability to RDP "out", such as accessing your office computer from home.
>
> I suspect your problem lies with (or relates to) the VPN, but would need
> more information about it to suggest a solution. Unfortunately, there are
> many possible VPN configurations, each of which creates a completely
> different scenario. I am going to throw out a couple guesses, but would
> really need you to describe your VPN setup in as much detail as possible.
>
> If you are using RDP over VPN, where the VPN must be connected before you
> can connect via remote desktop, and this works without the router, but not
> with it -- then I would suggest that your VPN only appears to connect with
> the router, but the supposedly established tunnel actually doesn't work.
> This is not uncommon, especially with IPSEC VPN implementations. Many
> routers simply don't pass the protocols through correctly.
>
> Another common problem is the same private address block on both ends, e.g.
> the popular 192.168.1.x block (which, if I am not mistaken, is the Linksys
> default) also used on the internal network in your office. The result is
> broken routing and the fix would be to reconfigure your router to use a
> different block, such as 192.168.2.x.
>
>
> --
> Chris Priede
>
>
>
>