Note - this article is unfinished. Please check back later for the rest!
If your operating environment is based on Windows Terminal Server you may be able to login remotely and run all your usual programs from anywhere in the world provided you have internet access, just as if you were sitting at your desk (albeit not quite as snappily, depending on available bandwidth and network congestion). Maybe you have a sick child at home but need to do the payroll today, or perhaps you're in a farmer's paddock writing a contract and connecting to the internet over your mobile phone or a wireless internet card. In the same way you might have a remote weighbridge that can communicate with your Grain Trader database in real time, giving both parties access to the most up-to-date information possible, or just want to check your email while on a trip. With a remote login you can have the same access to programs and data that you already have in the office, from anywhere.
The ability of a user to login remotely is governed by configuration settings in the server. The specifics of how this is done varies depending on several factors including whether your network uses a Domain, and is not within the scope of this guide. In any event it's something that is best left to your IT support personnel.
Assuming however that a user is permitted to login remotely, it is relatively simple to actually make the connection. Depending on the way your network and server has been configured and once you have a live connection to the internet, it will be a one- or two-step process.
If you are logging in from home or another office location you probably already have a permanent internet connection and can skip to the Making a Virtual Private Network Connection. Otherwise you will need to initiate a connection to the internet. Again, the way you do this is beyond the scope of this document but the following may be useful:
A Virtual Private Network (VPN) connection provides a “tunnel” through the internet which keeps your data safer by encrypting it at both ends before transmission. Your installation may or may not require a VPN connection - check with your IT support staff. If you don't need to make a VPN connection you can skip to Making a Remote Desktop Connection below, otherwise:
Click Next and select “Virtual Private Network connection” as shown below:
Click Next and enter a meaningful name to remember your new connection by, as shown below.
Click Next. We have already discussed connecting to the internet above, so ensure “Do not dial the initial connection” is selected, as shown below:
Click Next. Enter the host name (eg mycompany.dnsalias.com or mycompany.com.au) or IP address (4 groups of up to 3 numbers, separated by periods eg 123.123.123.123) of your server, as shown below. If you don't know either of these contact your IT support person.
Click Next. If you are working on your own computer and may want to make this connection again, you can if you wish tick the checkbox “Add a shortcut to this connection to my desktop”.