Re: RD works on LAN not across Internet

I was finally able to be seen by "canyouseeme" tool. I just opened the 3389
port in the cable modem. I didn't have it open there; I never thought it
would make a difference. I am not using a router, I use a HPNA network and
my "host" PC is the DHCP.

Now I will try it accessing my XP Pro PC from the outside world to see if it
really works.

Eduardo

"Jim Johnson - Serenity Consulting" wrote:

> I have also tried canyouseeme and other web-based scanning tools with a
> report that the PC cannot be seen.
>
> Keep in mind, that I also tried connecting the RD host directly to the DSL
> modem - no router involved (reconfigured IP settings naturally) with the same
> result. My XP Pro PC simply does not acknowledge anything on port 3389 when
> coming from a non-private IP address.
>
> For yesterday's test, I substituted the SP1 version of termsrv.dll, and used
> Zone Alarm's free firewall behind the router with port forwarding (note that
> I discovered you cannot open specific ports with the free version). Web-based
> scanning tools still see nothing, BUT Zone Alarm did see and warn me about
> one rogue port scan for port 3389 FORWARDED BY MY ROUTER TO MY STATIC PRIVATE
> IP ADDRESS.
>
> I shut down all firewalls on my PC (relying on the router's firewall - and
> knowing the router IS correctly doing port forwarding), then again tried
> web-based port scans of 3389 - again, in no case was port 3389 detected from
> outside my LAN.
>
> Obviously the issue is not simply SP1 vs. SP2 of termsrv.dll - but some
> deeper, greater issue in XP Pro that is blocking RD access from non-private
> IP addresses.
>
> "Sooner Al [MVP]" wrote:
>
> > If you setup port forwarding for TCP Port 3389 on your router to the private LAN IP of the PC you
> > want to connect to remotely using Remote Desktop, then run this test...
> >
> > http://www.canyouseeme.org/
> >
> > If it fails then you have an issue with port forwarding on the router.
> >
> > --
> >
> > 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...
> >
> >
> > "mobief" <mobief@xxxxxxxxxxxxxxxxxxxx> wrote in message
> > news:xAU8e.68275$YC4.4788260@xxxxxxxxxxxxxxxxxxxxxxxx
> > >I think I have the same problem... somebody does solve it ?
> > >
> > >
> > > "Jim Johnson - Serenity Consulting" <JimJohnsonSerenityConsulting@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote
> > > in message news:B0457AE0-AB4C-4B38-9022-5A56D44AD5D8@xxxxxxxxxxxxxxxx
> > >>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

  • Re: Cant get port forwarding to work (LinkSys)
    ... I use a similar LinkSys Router and I was able to get port forwarding working ... the menu you get when you first enter the router config - the Advanced / ...
    (comp.security.firewalls)
  • Re: Remote Assistance not working
    ... Using Remote Assistance to Get Help When You Need It ... Should I disable the NAT on the modem/router to allow the wireless router to ... using port forwarding makes it work that's one of those times. ...
    (microsoft.public.windowsxp.general)
  • Re: Using Remote Desktop From an SBS Domain
    ... when you tried to RDP while attached directly to a port on your router? ... So if 3389 needs forwarded on the client end too then that is what the ... Hopefully next week I can attempt a connection while my ISP watches the ...
    (microsoft.public.windows.server.sbs)
  • Re: Remote Assistance not working
    ... Should I disable the NAT on the modem/router to allow the wireless router to ... using port forwarding makes it work that's one of those times. ... internet with a cable modem and DSL modem. ...
    (microsoft.public.windowsxp.general)
  • Re: RWW interal not external
    ... SBS Standard, one NIC, no ISA. ... I have set the port forwarding on the router as best I can. ...
    (microsoft.public.windows.server.sbs)