Domain Name – for Remote Desktop Connection ????

gbdusmc asked 2 years ago

I have looked through the help in MS Windows 7 and online but I can't figure out the information in the correct format to enter for my FQDN so I can access my computers from outside my LAN using the RDC. I have set up permissions on the computers and can log on when on the LAN but can't find the correct FQDN to enter to get me logged into the computers remotely.

I know my assigned IP address and my actual external IP (I found it using WhatIsMyIP.com and I have my ISP and my various computer names. What else do I need? I thought my computerName.ExternalIP.AssignedIP.ISP.com would do it. I have tried every combination including leaving out one or both IP addresses and no luck. Any help?

Thanks!

/Gary/

2 Answers
wimiadmin Staff answered 2 years ago

If you google RDP, I'm sure there are some thorough explanations out there.

You'll need to understand port forwarding. And to access multiple windows computers behind the same IP address, you can actually change the port windows listens on instead of 3389.

Your FQDN won't be needed in this case.

The basics are this....From outside of your network pull up Start, Run, mstsc, click OK. In the Computer box, put your IP address (the one you found on whatismyip.com) and the port (if you've changed it)...like this 12.12.12.12 if the default is still set at 3389 or 12.12.12.12:3390 if you change the RDP port to 3390. Keep in mind you'll have to forward each port in your router.

Rob Vargas Staff answered 2 years ago

The FQDN is going to be your public FQDN, and that is, basically, up to the ISP. Some ISP's use a FQDN that matches the IP address, but they can't use periods in the actual host name. So if they assigned you an IP address of 1.2.3.4, then is could be something like 1-2-3-4-chicago.illinois.isp.com Or more, or less.

Sometimes you can get that FQDN by pinging with the -a tag. So, using a well-known address:
[code]ping -a 4.2.2.2[/code]
Yields:
[code]Pinging [b]vnsc-bak.sys.gtei.net[/b] [4.2.2.2] with 32 bytes of data:
Reply from 4.2.2.2: bytes=32 time=14ms TTL=55
Reply from 4.2.2.2: bytes=32 time=39ms TTL=55
Reply from 4.2.2.2: bytes=32 time=14ms TTL=55
Reply from 4.2.2.2: bytes=32 time=18ms TTL=55

Ping statistics for 4.2.2.2:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 14ms, Maximum = 39ms, Average = 21ms
[/code]
See that bolded part above? That's the FQDN for 4.2.2.2.

But pay attention to what wimiadmin said about port forwarding. How does your router (the actual machine represented by your public FQDN) know what to do with a RDP attempt? Port forwarding.

Know the answer? Login or sign up for an account to answer this question.
Sign Up