Re: Remote Desktop & Linksys

Tech-Archive recommends: Fix windows errors by optimizing your registry

From: Sooner Al (SoonerAl_at_somewhere.net.invalid)
Date: 07/22/04 

Date: Thu, 22 Jul 2004 09:12:18 -0500

If the office PC is behind a firewall/NAT/router then TCP Port 3389 would need to be open in order
for you to access the desktop via RD. How is the office PC connected to the public internet? 

-- 
    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...
"Raj" <rajmen73@yahoo.com> wrote in message news:6fd8c1ca.0407220558.4d494692@posting.google.com...
> Hello All,
>
> I am trying to connect to my work PC running XP professional from home
> which runs the same OS. Remote Desktop is enabled and it works fine
> when i try to connect from other PCs at work, which are ofcourse on
> the same subnet.
>
> When i try connecting from my home PC, which is behind a Linksys
> router (WRT54G), i cannot make the connection. I tried disabling the
> XP and zonealarm firewalls running on my office pc, nothing helped.
>
> I have the firewall and DHCP enabled on the router at home. My IP
> address is in the 192.168.X.X range. I tried ping and traceroute, that
> didn't work either. Other than that i don't have a problem getting to
> any other websites, do secure shell connections etc.
>
> Will port forwarding help in this case? I thought it makes sense when
> i am trying to connect to a PC behind the router. But mine is the
> other way around.
>
> I would really appreciate any help / pointers in this matter.
>
> Thanks in advance.
>
> - Raj

Relevant Pages

  • Re: Remote desktop
    ... You need to make sure TCP port 3389 is open between the client and host. ... This posting is provided "AS IS" with no warranties, ... > I have had trouble connecting the remote desktop across ... > on the same router and I put the wan IP address in for ...
    (microsoft.public.windowsxp.network_web)
  • Re: unable to connect
    ... Is the home PC behind a firewall/NAT/router? ... Its always possible your work network administrators have blocked TCP Port 3389 outbound. ... However at work I can run remote desktop between computers with no ... > in the office to give permission as with remote assistance. ...
    (microsoft.public.windowsxp.work_remotely)
  • Re: Connectivity Issues
    ... some businesses block TCP Port 3389 outbound. ... If so you also need to forward TCP Port 3389 to the private LAN IP ... Call using the public IP of the firewall/NAT/router. ... > Check with your network admin at work. ...
    (microsoft.public.windowsxp.work_remotely)
  • Re: lets start at the beginning...
    ... For the home PC forward/open TCP Port 3389 if the PC is behind a firewall/NAT/router. ... >I have a router which is connected to DSL. ... > third computer is at home and uses a cable connection to ... > the internet. ...
    (microsoft.public.windowsxp.work_remotely)
  • Re: Remote Desktop Issue?
    ... If its behind a firewall/NAT/router is TCP Port 3389 open to the private LAN IP of the PC? ... Please try connecting again later. ... >> The client PC has had a problem connecting to Kaazaa Lite also. ...
    (microsoft.public.windowsxp.work_remotely)