Re: RD works on LAN not across Internet

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: Remote desktop & Netgear router
    ... if you can connect to the PC from another PC using the "private LAN IP address" over your ... local LAN then Remote Desktop is obviously setup right and working. ... The issue then is the port forwarding on the router. ...
    (microsoft.public.windowsxp.work_remotely)
  • Re: confused on how to set up remote assistance
    ... requesting pc on XP Home SP2, receiving request is pc on XP Pro SP3 ... tried forwarding port 3389 for both pc's in router ... A Remote Assistance connection could not be established because the DNS ... TeamViewer also can be used IP to IP over a local LAN. ...
    (microsoft.public.windowsxp.work_remotely)
  • Re: RDP thru a router
    ... if your testing from another PC on your private LAN use the LAN IP. ... Its possible your ISP is blocking the IIS port, ... Can you test using the normal Remote Desktop client, ie. not the web based method, from both another ... >I have a Linksys router and I wish to enable RDP on a PC behind a router. ...
    (microsoft.public.windowsxp.work_remotely)
  • Re: RD works on LAN not across Internet
    ... modem - no router involved with the same ... Zone Alarm's free firewall behind the router with port forwarding (note that ... knowing the router IS correctly doing port forwarding), ... outside my LAN. ...
    (microsoft.public.windowsxp.work_remotely)
  • RE: confused on how to set up remote assistance
    ... In my case both the expert and novice PCs are behind my NAT router. ... Al Jarvi (MS-MVP Windows – ... TeamViewer also can be used IP to IP over a local LAN. ... you can *NOT* use Remote Desktop to remotely access/control a XP Home ...
    (microsoft.public.windowsxp.work_remotely)