Dameware can not solve the problem of remote network control

In the scale of LAN network expanding today, if each encounter failure phenomenon, network administrators have to go to the fault site to solve the problem, the network administrator's workload is obviously very huge, and this will seriously restrict the efficiency of network management. In order to make the network management efficiency to a higher level, I believe that the network managers around the general have similar damewareminiremotecontrol such a powerful "assistant" accompanied, after all, with these "assistants" strong support, network administrators can be remote management and control of the fault computer.

However, when you actually use a professional tool such as Damewareminiremotecontrol for remote control, we often experience the inability to establish a remote connection to the failed computer, and because of the different operating systems used by the failed computer, There are also different reasons why there is no remote control. In order to help friends to solve this problem quickly, this paper takes the Damewareminiremotecontrol tool remote control WinodwsXPSP2 fault computer as an example, to give you a detailed account of the causes of the failure and the specific troubleshooting process, I hope these things will help you.

Uncover reasons for remote control failure

We know that the Damewareminiremotecontrol remote control tools in the default state of installation, operation is often relatively simple; When we accidentally encounter the Damewareminiremotecontrol tool cannot establish a remote Desktop connection failure with the faulty computer system, it should lock the focus of the fault checking on the WinodwsXPSP2 system itself, because compared to previous versions of the system, The operating system has been significantly enhanced in terms of security performance and system Group Policy settings, and the Damewareminiremotecontrol tool is more restrictive when trying to remotely connect to a failed computer that has the system installed. Then the trouble to eliminate the natural need to spend a little more thought.

In general, the Damewareminiremotecontrol Remote Control tool cannot establish a remote Desktop connection with a failed computer that has the WINODWSXPSP2 system installed, which is likely to be limited in some of the following areas:

First of all, the faulty computer system's Internet parameters may be set incorrectly, for example, if the Internet users in the Local Connection Properties dialog box does not select the "Microsoft Network file and Printer Sharing" feature option, it is very easy to cause the system can not establish a remote control connection failure prompts;

Second, the network administrator to use the remote control account is incorrect, for example, in the establishment of Remote Desktop Connection if the input of the remote control account is not correct, then remote control connection can not be successfully established, this time the network administrator just re-enter the correct remote login account is OK, Of course, can also be in advance in the target remote computer system to recreate the appropriate permissions of the remote access account;

Third, the system's own firewall settings are correct, the target remote computer installed WINODWSXPSP2 system, the system's own firewall in the default state will hinder the remote control connection, so the system firewall parameter settings check is also very necessary.