RDS client computer cannot connect to the RDS server by using a remote desktop connection in Windows

Symptoms

Consider the following scenario:
  • You configure a Windows 7 Service Pack 1 (SP1)-based, Windows Server 2008 R2 SP1-based, Windows Vista Service Pack 2 (SP2)-based, or Windows Server 2008 SP2-based Remote Desktop Services (RDS) server to use Secure Sockets Layer (SSL) as a security layer.
  • You configure an SSL certificate template for the RDS server, and then the RDS server applies the SSL certificate.
  • The certificate is archived on the RDS server.
  • You try to use a remote desktop connection to connect an RDS client computer to the RDS server.
In this scenario, the remote desktop connection attempt fails. Additionally, you receive an error message that resembles the following:
The remote computer requires Network Level Authentication, which your computer does not support.

Note For example, you configure the auto-enrollment feature for the SSL certificate. When the certificate enters the renewal period, the certificate is archived, and the computer requests a new certificate automatically. You can also manually renew a certificate by starting the Certificate Microsoft Management Console (MMC). To do this, right-click the certificate that is used by RDS server, clik All Tasks, and then click Renew Certificate with New Key.

Resolution

Hotfix information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing the problem described in this article. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft website: Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

Prerequisites

To apply this hotfix, you must be running Windows 7 Service Pack 1 (SP1) or Windows Server 2008 R2 SP1.

For more information about how to obtain a Windows 7 or Windows Server 2008 R2 service pack, click the following article number to view the article in the Microsoft Knowledge Base:

976932 Information about Service Pack 1 for Windows 7 and for Windows Server 2008 R2

Registry information

To apply this hotfix, you do not have to make any changes to the registry.

Restart requirement

You must restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace a previously released hotfix.

File information

The global version of this hotfix installs files that have the attributes that are listed in the following tables. The dates and the times for these files are listed in Coordinated Universal Time (UTC). The dates and the times for these files on your local computer are displayed in your local time together with your current daylight saving time (DST) bias. Additionally, the dates and the times may change when you perform certain operations on the files.

Windows 7 and Windows Server 2008 R2 file information notes
Windows 7 and Windows Server 2008 R2 file information notes
Windows Vista and Windows Server 2008 file information notes
Windows Vista and Windows Server 2008 file information notes

Workaround

To work around this issue, delete the original certificate on the RDS server instead of archiving it at first. Or, you can delete the value of the TemplateCertificate registry entry that is under the following registry subkey after the issue occurs:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Terminal Server\WinStations

Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

More Information

For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:

824684 Description of the standard terminology that is used to describe Microsoft software updates

Additional file information

Additional file information for Windows 7 and for Windows Server 2008 R2
Additional file information for Windows Vista and for Windows Server 2008
Ιδιότητες

Αναγνωριστικό άρθρου: 2752618 - Τελευταία αναθεώρηση: 9 Σεπ 2014 - Αναθεώρηση: 1

Σχόλια