RE: RD works on LAN not across Internet

Thanks for the feedback...

Al

"Jim Johnson - Serenity Consulting" wrote:

> PROBLEM FIXED?:
>
> I activitated various event logs, and found this error...
> ID: 20106
> Source: RemoteAccess
> Version: 5.2
> Symbolic Name: ROUTERLOG_COULDNT_ADD_INTERFACE
> Message: Unable to add the interface %1 with the Router Manager for the %2
> protocol. The following error occurred: %3
>
> Explanation
> Possible causes include:
>
> The interface type is not dedicated
> The loopback and router is configured in Lanonly mode
> ======================
> I then checked Services in the Adminstrative Tools and found that the
> following services where in manual mode and not started:
> Remote Access Auto Connection Manager
> Remote Access Connection Manager
> Remote Desktop Help Session Manager
>
> Changing these services to 'automatic' (and starting the Remote Access
> services) now allows port 3389 to be seen using the web-based port scanner,
> www.canyouseeme.org. Without these services running, Remote Desktop will only
> work on a LAN.
>
> How they got changed to manual and turned off in the first place is beyond me.
>
>
> "Jim Johnson - Serenity Consulting" wrote:
>
> > 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

  • All going well... until Server 2003!
    ... Error:The requested session access is denied. ... Can I stop Remote Desktop from locking host? ...
    (microsoft.public.windowsxp.work_remotely)
  • Re: Cannot connect to remote server
    ... icon for Outlook on the remote desktop. ... You hover over the icon on the remote desktop and a "hand pointer" ... I have a feeling that you were using RDP 5.1 with Windows XP SP2. ...
    (microsoft.public.windows.server.sbs)
  • Re: Cannot connect to remote server
    ... you can't access the Start menu on the remote desktop? ... So this is not a Windows XP SP3 ... I have a feeling that you were using RDP 5.1 with Windows XP ...
    (microsoft.public.windows.server.sbs)
  • Re: Remote Desktop works but does not unlock the host PC after disconnect
    ... Can you disable the screen saver and other power options on the XP machine ... I access the Host via Remote Desktop, ...
    (microsoft.public.windowsxp.work_remotely)
  • Re: Remote desktop only works if someone is already logged in
    ... That is the command I run ... I can ping the ip address of the host computer ... The exact error message is - This computer can't connect to the remote ... how you launch Remote Desktop on the remote machine. ...
    (microsoft.public.windowsxp.general)