Should simple domain be used to access Remote Desktop? Is Remote Desktop Connection equivalent to VPN?

Good morning all. Two-part question follows:

1. For convenience, I'm forwarding an easy-to-remember public domain to my Remote Desktop Connection domain (which includes a high port number) at dyndns.org. My local router then matches the fixed IP at dyndns with the variable IP coming from my DSL service.

simple-public-domain.com  >  long-nasty-domain:port.number.com

When the easy-to-remember domain is entered in a browser, I'm prompted for the Windows user/password, which lets me get into my machine at home from anywhere on the road.

It is bad security practice to use the simple domain, which has already been spidered by Google? Or am I better off memorizing and using the long domain that includes an obscure port number?

2. Is Windows Desktop Connection equivalent to VPN, or should I be implementing VPN for added security/privacy at public hotspots? Recommendations?


michaelnorthAsked:
Who is Participating?
 
mikeleebrlaCommented:
1.  i would just use the IP address and port number and connect that way, without using a DNS name at all.

2.  Windows Desktop connection and a VPN are 2 completely differernt things alltogether and not really related at all. But as far as you are concerned Windows desktop connection has 128 bit encryption and a VPN generally has 128 bit encryption also.  So my point is that you are OK with just the Remote desktop connection and dont need to put a VPN into the mix which will probably just cause more problems and will of course be slower,, since it will have to encrypt and decrypt twice then.

0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.