Should simple domain be used to access Remote Desktop? Is Remote Desktop Connection equivalent to VPN?
Posted on 2004-08-19
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?