Remote Desktop through a router

  • Thread starter Thread starter SPUD
  • Start date Start date
S

SPUD

I am having difficulty connecting to the host from the internet. I can
remote connect on my wireless Lan with no trouble. I have programmed my
Windows firewall and router firewalls to allow Remote Desktop to pass to the
host. I have pinged my routers public IP and verified it is connectible. On
RD I use the routers Public IP as the computer and the host
name\administrator name as user id. Am I using the wrong format?? Or am I
missing something else??
 
Many times calling the public IP of the router from a PC on the same private
LAN will not work because many consumer grade routers do not support loop
back.

http://theillustratednetwork.mvps.org/RemoteDesktop/TroubleshootingDiagrams/Basic.html

The best test is from a true remote site, ie. a public hot spot like the
library, a bar (my favorite) or a friends house.

Remember you need TCP Port 3389 forwarded/opened on any router the target
RDC host PC is behind. You can test that from the target RDC host PC by going
to the http://www.canyouseeme.org site.

Its also recommend the PC has a static LAN IP address.

http://theillustratednetwork.mvps.org/RemoteDesktop/RemoteDesktopSetupandTroubleshooting.html

http://theillustratednetwork.mvps.org/RemoteDesktop/RDP6ConfigRecommendations.html

--

Al Jarvi (MS-MVP Windows – Desktop User Experience)

This posting is provided "AS IS" with no warranties, and confers no
rights...
The MS-MVP Program - http://mvp.support.microsoft.com
 
I guess I wasnt clear enough. When I was accessing in the Lan, I was only
using the host name, not the router public IP. I was using the router public
IP from remote locations.
 
So you want to call the target RDC host PC by a name versus the public IP of
the router from a remote location? If so you need to use something like the
free dynamic naming service from No-IP.com or DynDNS or similar.

The way it works is you run a small program on one of your PCs. The program
contacts the No-IP.com or DynDNS servers on a time scheduled basis. The
servers then map a fully qualified domain name [FQDN] to the current public
IP of your router. You call home using the FQDN. Some consumer grade routers
have built-in support for No-IP.com or DynDNS or similar free services. Check
the router manual for help with that.

http://www.no-ip.com
http://www.dyndns.com

If that's not what your trying to do please post back.

As far as user credentials are concerned the user ID and password are local
to the target RDC host PC not your remote client PC.
--

Al Jarvi (MS-MVP Windows – Desktop User Experience)

This posting is provided "AS IS" with no warranties, and confers no
rights...
The MS-MVP Program - http://mvp.support.microsoft.com
 
No. I would still like to use the router public ID as the entry in RD
"Computer" (If that is appropriate). What I really need to know is the
proper format for entries in the RD window boxes. This may not be my
problem, but it is a starting place.


Sooner Al said:
So you want to call the target RDC host PC by a name versus the public IP of
the router from a remote location? If so you need to use something like the
free dynamic naming service from No-IP.com or DynDNS or similar.

The way it works is you run a small program on one of your PCs. The program
contacts the No-IP.com or DynDNS servers on a time scheduled basis. The
servers then map a fully qualified domain name [FQDN] to the current public
IP of your router. You call home using the FQDN. Some consumer grade routers
have built-in support for No-IP.com or DynDNS or similar free services. Check
the router manual for help with that.

http://www.no-ip.com
http://www.dyndns.com

If that's not what your trying to do please post back.

As far as user credentials are concerned the user ID and password are local
to the target RDC host PC not your remote client PC.
--

Al Jarvi (MS-MVP Windows – Desktop User Experience)

This posting is provided "AS IS" with no warranties, and confers no
rights...
The MS-MVP Program - http://mvp.support.microsoft.com



SPUD said:
I guess I wasnt clear enough. When I was accessing in the Lan, I was only
using the host name, not the router public IP. I was using the router public
IP from remote locations.
Click to expand...
Click to expand...
 
Also, when I used the "canyouseeme.org" It references my router public IP
and when I put in 3389, it responds "Error: I could not see your service on
76.201.76.166 on port (3389)
Reason: Connection timed out" even though the router shows 3389 as the
correct port??
 
When connecting from a remote location use either the public IP of the router
or a fully qualified domain name.

The user ID and password is local to the PC you want to login to with Remote
Desktop.

So, if PC-A is behind a router that has a public IP of 12.34.56.78 and a
user named Joe with a password JoeJoe enter those in the appropriate places
in the RDC connectoid. If you use a fully qualified domain name, ie.
joesPC.noip.com for example, substitute that for the public IP address. Also
remember that the user Joe must either be an administrator on PC-A or a
member of the Remote Desktop Users Group.

http://www.microsoft.com/windowsxp/using/mobility/getstarted/starteremote.mspx

If the http://www.canyouseeme.org test is failing then the port is not open
or TCP Port 3389 is being directecd to the wrong LAN IP (static) or your ISP
is blocking TCP Port 3389 (unlikely but not impossible). If your calling from
a work environment its also possible the network admins have blocked TCP Port
3389 outbound.

--

Al Jarvi (MS-MVP Windows – Desktop User Experience)

This posting is provided "AS IS" with no warranties, and confers no
rights...
The MS-MVP Program - http://mvp.support.microsoft.com
 
Back
Top