Re: Need advice with Remote Desktop Connection

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance


Thanks to all who replied.



Let me first review - No problem doing a Remote Desktop Computer (RDC) from
within my LAN using either the computers internal IP address or its name.
However, doing this same thing on an external XP Pro computer does not seem
work. I'm also not sure I understand how the external RDC computer
understands an address such as 192.168.1.xxx.



The problem seems to be that my remote port 3389 is being blocked external
but how/why, is it because of the Windows firewall, my router, or by my ISP?
How can I test this?



I also understand that I can only use port 3389 on one of my LAN computer
and that I will have to edit my XP register to change port 3389 to something
else for the other computers - is this correct? If so, must I then make the
appropriate changes in there Windows firewall as well as my router? What
about HTTP port 80, must it be on?



I would certainly appreciate any follow-up advice, keeping in mind I'm not
an expert in this area.



Jim



"Jim" <jrwolfe@xxxxxxxxxxx> wrote in message
news:e5qccMW$JHA.1488@xxxxxxxxxxxxxxxxxxxxxxx
I would greatly appreciate some advice on why I cannot achieve a Remote
Desktop Connection from a remote location yet it works just fine between
computers on my LAN.



Here is my setup, 3 XP Pro computers plus a Windows Home Server (WHS)
running on a LAN with a Linksys BEFSR41 router.



Let's assume the internal address of one of my computers is 192.168.1.123.
For this computer, I have the "Remote Desktop" box checked in both Windows
Firewall Exceptions and Advanced sections (TCP port 3389). I'm also port
forwarding 3389 for address 192.168.1.123 in the Linksys router. Shouldn't
things now work from a remote location, what am I missing?



I should also point out that I have no problems accessing my WHS server
from a remote location. When I make a connection to this server I can view
all my LAN computers.



Thanks in advance






.

Relevant Pages

  • Re: Kazaa Block !
    ... >> security breach, but worse, it is a blatant abuse of work computers. ... >> If this is a home LAN, and these are your children, ground them first, ... >> block KaZaA from their computers, ... > goes over port 80. ...
    (comp.security.firewalls)
  • Re: Establishing Remote Desktop Connection
    ... Internet connection is via a TI, ... enables the host desktop to accept remote connection. ... you have to configure your router to forward traffic on port 3389 to the ... If you wanted to access multiple computers at your office, ...
    (microsoft.public.windowsxp.general)
  • RE: Desperate for assistance
    ... I wouldn't advise calling Norton and asking them such technical questions. ... Remote support online pays their techs notoriously low wages. ... When I click on Norton under network, ... computers to connect remotely to my computer? ...
    (microsoft.public.security)
  • Re: Remote Desktop Users and Least User Rights
    ... user accounts (no administrative rights on the local machine). ... the Administrators group, the list of authorized remote users (My ... Remote tab> Select Remote Users) gets wiped out. ... You can create/link a new GPO at the appropriate OU where your computers ...
    (microsoft.public.windowsxp.security_admin)
  • RE: Remote Administrator 2.x: highly possible remote hole or back door
    ... This *does not* automatically mean that radmin is insecure. ... settings for remote ... Affected computers have different ... There are Windows 98 as well as Windows 2000 ...
    (Bugtraq)