Remote Desktop Console Connection

There are several independent providers for maintaining remote connection to computers via networks. But most of them require paid subscriptions or purchases. However widely used operating systems like almost all Linux distributions and corporate Microsoft Windows versions do come with built in remote desktop features. As the name implies, remote desktop connection lets users to connect and use a remote computer from a distant location. Users do not need to be in the same network for such a communication platform. Connecting to a computer at work from home or from thousands of miles away is possible, unless connection speed limits a smooth operation.

Remote desktop connection can be established either by using graphical based programs or command based consoles. The basic behind this connection is pretty simple: First prepare the remote computer as accepting remote connections like making necessary changes in user profile and then access the computer remotely using relevant commands and username/password combination to be granted as the owner of the remote computer.

But there's an important difference between a remote connection and remote console connection. In remote desktop connections, the remote user can access the computer as if he/she is standing right in front of the machine. There exists some limitation about the full permission in this connection type. Because this connection ends the running session and thus all running programs and opened files are closed (without saving). In order to use the remote computer, as if the user has just touched the keyboard, remote desktop console connection is strictly required. This connection type protects the running session and remote user can see the running programs/opened files as well as can do what ever is required on that computer.

In terms of syntax, mstsc command is used in a typical remote desktop console connection. If you are running an older version of Vista (using Windows XP or Vista but has not upgraded to Vista SP1) command syntax should be as: mstsc /console ip_adress
This usage also applies for the computers with Windows Server 2003. For Vista Sp1 and above (also valid for Windows Server 2008 platform) the syntax has changed to: mstsc /admin ip_adress

With this command syntax users can access computers remotely and with full ownership, however the IP address is a little bit tricky when making a connection from outside. Because proper routing conditions must be managed beforehand in order to access the remote computer through a network hub that restricts connections. If you are connecting to a computer at home for instance, assuming it is connected to a broadband modem, remote desktop connection port must be opened in the modem and must be forwarded to the specified computer's local IP address. By default port number 3389 is used in Windows computers. Also a dedicated port for the modem must be opened as well, since this port of the broadband modem will be accessed from outside. By default Windows uses port number 80 in its Internet Information Services parameters. However both these ports can be changed to increase accidental access from outside which needs detailed management knowledge.

Remote desktop connection to console is pretty vital in many ways. It does not interfere with the running session, thus outside user can keep on working on the same files or programs and do administrative tasks as well without loosing anything. It is important to access the remote computer as the same user who has already started up the session. Otherwise, connecting with a different user (which must be also granted for remote access), ends the current session. Please keep in mind that, making remote console connection ends the session of the user who may be in front of the remote computer physically. If everything has been managed well, connecting to business computer from home or vice verse makes life easier than before especially for those who are always on the go!