Blank password raises remote connection Windows Server 2008 failed

Failure phenomenon

The Unit network administrator upgrades one file server in the LAN to a Windows Server 2008 system and installs an application control software in the system. A user in a local area network wants to use the Remote Desktop Connection feature to perform data backup operations on the target control software in the Windows Server 2008 Server system in a common client system, but the user is dumbfounded when trying to establish a remote Desktop connection to the target server system. Regardless of the connection operation, the system always prompts you to remotely connect to Windows Server 2008 failure prompts, what's the good?

Network administrator received a fault "call for help" phone, immediately rushed to the fault scene, after careful observation and analysis, he estimated most likely is the current user account does not have Remote Desktop Connection permissions, for this he reopened the Remote Desktop Connection Settings window, from which the correct input administrator account and password, and then click "OK button, every thought of the system screen still appears to be a failure prompt such as unable to log on.

Fault analysis

Does the Administrator account have no Remote Desktop Connection permissions? Looking at the above symptom, the network administrator estimates that the Windows Server 2008 Server system may have problems with the permissions setting, so he immediately arrives at the Windows Server 2008 Server System site, clicking the start/Run command. In the System Run dialog box that pops up, enter the string command "Secpol.msc", enter the Local Security Settings window for the corresponding system after clicking Enter, and in the left child pane of the Settings window, expand the security Settings/local Policy/User Rights Assignment Branch option, in the User Rights assignment In the right sub pane of the Branch option, right-click the "Access this computer from the network" option to run the Properties command from the pop-up shortcut menu to open the target Group Policy property Settings window, shown in Figure 1, from which the network administrator sees that the server system has already joined the Administrator account , which means that the Administrator account has Remote Desktop Connection permissions. Later, the network administrator will terminal Server User, Remote Interactive and other accounts also added to the Figure 1 Settings window, but this effort has no effect.

Figure I

Considering that the Windows Server 2008 Server system also has appropriate control options in the system Terminal Services settings, this network administrator immediately clicks the Programs/Administrative Tools/Terminal Services Configuration command on the Start menu of the server system, selecting RDP-TCP Connection options, and right-click the option, from the pop-up shortcut menu to perform the "Properties" command, open the corresponding system Terminal Services Configuration dialog box, click the "Security" tab, open the tab set as shown in Figure 2 page, in the Settings page, the network administrator found the account administrator, Remote Desktop Users account has full control of operation rights, which means that these accounts should have the right to Remote Desktop Connection operation.

Figure II

Because the Windows Server 2008 Server system provides multiple forms of authentication, the system makes network-level authentication to remote connection users by default, which can hinder traditional operating systems from being unable to work with Windows Server 2008 Server system to establish Remote Desktop Connection; To do this, the network administrator in the corresponding system in the Terminal Services Configuration dialog box to select the "General" tab, open as shown in Figure 3 of the tab Settings page, you do see the "only allowed to run computer with Network Level Authentication Remote Desktop Connection" option is already selected , cancel the selection of this option, and then click OK to save the above settings, but the previous symptoms are the same.

Figure Three