Re: RD works on LAN not across Internet

Well, if you can connect to the Remote Desktop host across your LAN then its obviously an issue with
port forwarding through your firewall/NAT/router device or an addressing issue.

What router? Are you using a static IP for the PC on your LAN? Are you calling the correct public IP
for the router?

There is some troubleshooting help 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 Johnson - Serenity Consulting" <JimJohnsonSerenityConsulting@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote
in message news:A15029FE-AFA4-46B9-A04F-E3807A59A459@xxxxxxxxxxxxxxxx
> Running XP Pro SP2 on both host (desktop) & client (laptop). Windows Firewall
> running on host, Remote Desktop enabled through System Properties and users
> assigned (I've also verfied that the Firewall allows exceptions and Remote
> Desktop is checked, and the 'Advanced' tab shows Remote Desktop enabled and
> pointing to itself by computer name).
>
> Remote Desktop works flawlessly when connecting within the LAN.
>
> At one time RD worked just fine across the Internet using port forwarding
> through my router. Now it refuses to connect across the Internet.
>
> I've tried numerous things, up to and including switching from cable to DSL,
> rebuilding the router settings after doing a factory reset - - and even
> by-passing the router and connecting the host directly to the DSL modem.
>
> I can ping the host PC without problem, so I know I've got the correct IP
> address.
>
> I've seen suggestions for rolling the terminal services .dll on the host
> back to the SP1 version. Before doing that, is there something I've missed?
> For example, an MS Hotfix?


.

Relevant Pages

  • Re: router causing ssh etc. slowdown?
    ... >> port on their public IP from a host on their own LAN. ... Let's say host A starts a TCP connection from its ... The router sends the SYN packet to ...
    (Fedora)
  • Re: RD works on LAN not across Internet
    ... I physically by-passed the router altogether and connected ... > the host directly to the DSL modem - along with changing the host's IP ... > settings to fully use DHCP to access the Internet. ... > is no longer part of the LAN (and no other PC on the LAN can connect to ...
    (microsoft.public.windowsxp.work_remotely)
  • Re: Remote Desktop to home wont work
    ... Don't try to use your external IP address (i.e., your dyndns name) ... Just use your LAN computer name or IP Address. ... >> If you have a router, you must forward the proper ports to the Remote ... If you are running Remote Desktop Standard, ...
    (microsoft.public.windowsxp.work_remotely)
  • Re: Remote Desktop fail from outside
    ... the router ... you should try to enable "PORT FORWARDING" to the LAN ... >> I have set up Remote Desktop on one machine. ... >> For the machine with Remote Desktop Server, ...
    (microsoft.public.windowsxp.work_remotely)
  • Re: remote desktop
    ... Forward TCP Port 3389 to the private LAN IP of the XP Pro Remote Desktop host machine, ... public IP of the router, ie. the IP assigned by your ISP. ...
    (microsoft.public.windowsxp.work_remotely)