Setup dynamic dns remote desktop

Now that you have a host in your account, you will want to install our Dynamic Update Client at the location that has the dynamic IP address. This is a free download from our downloads tab located at the top of the site. After installing the Dynamic Update Client, be sure to configure it with the email address and password you used to login to this site.

The client will run in the system tray on Windows machines. This will allow the program to start automatically after the user logs in. Note: If you can already reach your remote desktop system by IP address, then you can skip this step. In this way, you can give your dynamic IP address a virtual static IP address.

When connecting to your computer, you would either type in the domain name or you would ping the domain name to find the current IP address. The domain names are always subdomains of the company you are setting up an account with. For example, one provider of dynamic DNS services is no-ip. So when you register and create a hostname, it would end up looking something like aseemkishore.

In order to determine your current IP address, all of these services work in one of two ways: either you install a piece of software on your computer that constantly updates their servers or you configure the service on your router, if it is supported. If you really plan to connect remotely a lot from different parts of the world and you want something very reliable, DynDNS is definitely worth paying for.

However, there are several free options that do a pretty good job and will work just fine for most people. Having multiple hostnames is a nice feature in case you have multiple devices you want to remotely access and you want a different hostname for each device.

The devices can also have different locations, so you could use one hostname to connect to a computer at home and another to connect to a computer at work. To get started, click on the Sign Up Now button and create your account. The next thing to do is to download the update client, as that is the tool that will constantly update the no-ip servers with your current dynamic IP address. It will automatically determine your OS and show the correct download for Mac, Windows, etc.

It will list out the host names you have created, so just check the box next to the one you want. The only other thing I would suggest is clicking on the Daemon tab and clicking the Start button and also checking the Launch Daemon at System Startup box. You can also click on the Settings tab and check the box to start the updater program when logging in. However, I have found it much more convenient to just use the daemon and not worry about the updated app at all.

You should now be able to simply ping the hostname akishore. Anything coming from the public Internet going to port used for Remote Desktop or Terminal Services will get rerouted to the internal host Port is a nonstandard port I chose for a second Remote Desktop host that will get rerouted to internal host Once you've completed these port-forwarding entries, click on the Save Settings button to save your changes.

Note that you should use static IP addresses on these internal hosts because any change in a DHCP address will cause port forwarding to break. Windows Remote Desktop defaults to TCP , but you can have only one machine using this port when you're sharing a single IP address. If you want to open up a second computer for Remote Desktop, you'll need to configure a nonstandard port.

You will need to edit the following registry key with the RegEdit command:. To set an alternative key for the second Remote Desktop host with the IP address of You can keep incrementing the ports for additional hosts you want to open to the Internet.

As powerful and useful as this technique is, convenience comes with responsibility. Anytime you open a port to the outside world, that service -- whether it's a Web server or Remote Desktop server -- can potentially be a backdoor into your network if you're not careful with security. Opening up ports to the Internet means that anyone around the globe can take a shot at your services.

Remember that it doesn't matter what operating system or platform you're using. When it comes to getting hacked on the public Internet, the most important thing is that you follow best practices for locking down the services you expose. Since this article gives examples of using Remote Desktop from anywhere on the Internet, it is critical that you configure Remote Desktop securely.

This usually doesn't use a lot of bandwidth, but it could if you enable desktop animation and audio or video playback over the remote connection.

You can learn how to configure Remote Desktop securely in this article. Host a personal Web site from your own computer.

This is bandwidth constrained because most broadband services don't have great upload capacity. Most broadband connections are capped at around to kbps, although some lucky users have 1 mbps of upload capacity. Host your own FTP server.