Windows XP remote controlIn the operating system Windows XP Professional built-in tool for remote computer management. You can from any room, in which place you eat another computer with any Windows version (at least 95 OSR2) also with a modem or the Internet, own full access to the desktop of your family computer if it is connected to the network.
For the source, we need to allow the use of remote control. Moving to the "Control Panel -> System -> Remote Sessions" is also included there "Allow remote access to this computer."
In principle, now the computer is ready for remote control. However, one must find it somehow on the Internet. If your provider provides an external static IP address, then there is no problem. However, many providers (in particular, Stream) provide an external dynamic IP address - it is different once in a while, and in a few hours your ancient IP may already belong to someone else. To solve this problem, there are numerous DynDNS services - they give you a domain name that will point to your IP, and they constantly keep track of changes to your IP changes. In particular, this gratuitous favor to eat on No-IP.com, there you can create your computer some third-level domain on the Internet, for example, mycomputer.no-ip.com. There, blah blah, it is allowed to download the customer - No-IP dynamic update client, which will non-stop contacting the No-IP.com service and check / update your IP. I will not talk about the settings of this customer, but I can advise you not to change its settings, in addition to the "When updating via NAT / Router / Proxy address ONLY ..." parameter, which is better to set to "every 5 minutes".
Now, it is allowed to find a computer through the Internet. However, it is necessary to establish a connection with him. If for example you have an ADSL-LAN-modem, or just NAT, then you need to configure the "Port Forwarding" function on TCP for TCP port 3389 (remote control works on it).
Also in the firewall you need to allow TCP-port 3389 to enter. I will tell you on a sample of the Windows XP firewall (which appeared in another service pack). We follow the “Exceptions” tab to also allow the “Remote Desktop Management” program (Fig. 2), then break through to the “Advanced” tab and enable the “Remote Desktop Management” service (Fig. 3) in the network connection settings. For Agnitum Outpost v.2.5, you need to find svchost.exe in the "Options -> Applications" menu, then use "Change -> Edit locations -> Create" to create a location.
Now let's deal with the client side. The customer for remote control is initially built into Windows XP. It is also allowed to find it in "Start -> Programs -> Standard -> Union -> Remote Desktop Connection". If you manage remotely from an earlier version of Windows, you will need to install a customer (you can either take it on the Microsoft website or send it from the c: \ windows \ system32 \ directory of Windows XP installed, mstsc.exe files are also mstcsax.dll.
So, we are going to connect. Establish integration with the Internet also launch the customer ("Start -> Programs -> Standard -> Union -> Remote Desktop Connection" or simply mstsc.exe). Click the "Parameters" button to access additional settings (Fig. 5), in order to proceed to customize the client settings. "Computer" is the address of your computer on the Internet. Here you must specify either a static IP address, or, for example, the previously mentioned dynamic domain such as mycomputer.no-ip.com.
"User" is usually the Administrator or any of the administrator accounts that exist on the managed computer. On the "Screen" tab, you can customize the size of the customer's window (I do not recommend to put more than 800x600). To optimize the work of a remote customer on modem lines, it is also desirable to disable the "Sound on the remote computer" mode, which is located on the "Local Resources" tab. Is it done? Great, connect.
I note that when installing a remote control session, local access on a remote machine will be blocked at once by the blah blah - you will also be prompted for a name as a password. After the end of the session, the computer will remain in locked mode until it is unlocked at all by entering the name and password locally.
Well, that's all. I’ll add another significant security recommendation - don’t make admin accounts passwords (at least a couple of them in Windows XP –– created when you install the Administrator / Administrator is also yours) shorter than ten characters –– otherwise, attackers will be able to pick it up.