Re: RD works on LAN not across Internet

I was using a static IP behind the router, and yes the public IP was
verified. I have verified that the Windows Firewall's scope for Remote
Desktop includes all computers, even those with public IP addresses. No
policies have been implemented on the host. My attempted login is with an
administrator group account (actually the same account to which I login
locally).

For last test, 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. In other words, the host
is no longer part of the LAN (and no other PC on the LAN can connect to the
Internet).

I *still* cannot make a RD connection across the Internet. Both my former
ISP (Charter Cable) and my new ISP (SBC/Yahoo DSL) claim they do not block
port 3389. However, using web-based port checking tools, my PC cannot be seen
at port 3389. I *am* able to successfully ping the public IP address of the
host across the Internet.

So, within a LAN using private IP addressing, RD works fine. Using a direct
connection to the Internet (no local router in the circuit) and public IP
addressing, RD fails.

By the way, I had also tested using the router and port forwarding to a
static private IP address (no changes from what used to work), AND disabling
all software firewall protection at the host (relied on the router's
firewall). The result was identical.

*Something* within the host simply does not like doing RD across the
Internet. I am leary of dredging up a SP1 copy of trmserv.dll - but may
experiment if no one has a better suggestion.

thanks,

Jim Johnson


"Sooner Al [MVP]" wrote:

> 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

  • XP DNS stopped working?
    ... Since then, it has been impossible to access the internet with IE or OE: page not found, server not found etc. ... All other PCs connected to the router continue to function normally. ... The DNS server addresses in the PC are fine. ... Going back to the DNS failure, I put a valid host entry in the hosts file, and it was possible to access the host using its FQDN. ...
    (microsoft.public.windowsxp.network_web)
  • Re: "Lost" DNS on WIndows XP Home
    ... I have other computers on the network and internet was fine. ... If you are the admin for your NAT router, check if you can connect to its web server used for its configuration. ... Using ipconfig /all and looking at the DCHP table in the router (whose DHCP server is presumably being used to assign intranetwork IP addresses), check that the one used by your troublesome host doesn't duplicate one assigned to a different host. ...
    (microsoft.public.windowsxp.general)
  • 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: network design using SBS 2003
    ... Claus i am using a adtran 3120 for internet access, what has to be done to ... for 2NIC SBS) set as 20.1 and 16.1. ... send the traffic to 16.2 (your VPN Router). ... You have to do the same on your remote subnet. ...
    (microsoft.public.windows.server.sbs)
  • XP Home and local area network
    ... I am setting up a small home network for 3rd party, ... The host machine has been ... same workgroup and connecting to the internet. ... I am using a Netgear WGR614 router. ...
    (microsoft.public.windowsxp.network_web)