Win 2003 Open Remote Desktop Note

Windows2003 Enable Remote Desktop Connection Function

Windows2003 enables remote desktop connection function, it is very simple, check Enable System Assistance in the system properties, as shown below: Br>

Related tips, windows2003 enabled remote desktop sometimes encounters remote connection failure, it may be that windows2003 does not set the system login password

I will meet below The remote desktop problems that have been visited are listed one by one:

Remote desktops cannot be connected into two categories:

One, unable to connect from the client to the remote

Error condition Roughly: "This computer cannot connect to a remote computer. Please try to reconnect. If the problem persists, please contact the owner or network administrator of the remote computer.

Solution: 1. Check if the firewall is enabled, whether it will be port 3389 or "remote desktop" The service is listed as an exception. If not, please turn off the firewall or list this service as an exception;

2. Check if TCP/IP filtering is enabled, ncpa.cpl opens the network connection, right click “local connection”. -“Attributes --&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&& Check if there is any filtering that is not conducive to remote desktop port pass, if any, please turn off TCP/IP filtering or redefine the filtering port;

3. Enter services.msc to check if an important service is enabled, Terminal Services This is a necessary service for remote desktop. Generally, turning this service on and ensuring that the Windows Firewall service is closed can solve most problems, but we may also ignore it. Some things;

4, check whether the anti-virus software or security products on the server have been upgraded, some anti-virus software will also bring some security features, they think the remote desktop port is too dangerous, so disable it If the above 3 are not feasible, check the configuration of the anti-virus software or security product, or uninstall it directly;

5. Enter the group policy and check if the following ipsec security policy has been assigned to block the remote. The policy for connecting ports, if any, redefine the policy or define it as “do not assign 

6, port conflicts, perhaps for security, many people will manually remote desktop when configuring the server The default port (3389) is changed, which does prevent a lot of port heuristics, but if there are a lot of software installed on the server, it will inadvertently cause port conflicts, causing you to be able to connect to the remote before restarting the server. Desktop, but after restarting, how can I not connect, if the methods have tried Then the last may be your solution. First regedit enters the note table: \\HKEY_LOCAL_MACHINE\\SYSTEM\\CurrentControlSet\\Control\\Terminal Server\\Wds\ dpwd\\Tds\\tcp, there is a portnumber here, change it to a different port number, then HKEY_LOCAL_MACHINE\\SYSTEM\\CurrentControlSet\\Control \\Terminal Server\\WinStations\\RDP-Tcp, there is also a portnumber below, which should be the same port number as above. If you are not sure if the port conflict is unable to connect, you can use the above two registry keys. First change the port back to the default 3389, if this can be connected, then the description is indeed a port conflict, the registry needs to be restarted after the change!

Second, connect to the remote desktop but can not log in, display no permissions

Solution: Enter Group Policy--Computer Configuration--Windows Settings--Security Settings--Local Policies--Users Right assignment, check & ldquo; refuse to log in through Terminal Services & rdquo; there are no users you need to log in, if there is, please delete it, & ldquo; allow login through Terminal Services & rdquo; to join the user you need to log in