Remote Desktop cannot verify the identity of the computer you want to connect to.

Remote Desktop cannot verify the identity of the computer you want to connect to.

When connecting to older machines with RDP sometimes I get the message : 
Remote Desktop cannot verify the identity of the computer you want to connect to. This problem can occur if: 

1) The remote computer is running a version of Windows that is earlier than Windows Vista. 
2) The remote computer is configured to support only the RDP security layer. 

Contact your network administrator or the owner of the remote computer for assistance. 

Do you want to connect anyway?




The following information comes from : 
http://weblogs.asp.net/owscott/archive/2006/11/10/Vista_2700_s-Remote-Desktop-Prompt.aspx 

Vista and RDP6.0's Remote Desktop Prompt 

I use Remote Desktop Client dozens of times per day to administer remote servers. With Windows Vista, I get an ugly prompt when connecting to Windows Server 2003 and Windows 2000 Server machines saying: 

Remote Desktop cannot verify the identity of the computer you want to connect to. This problem can occur if: 

1) The remote computer is running a version of Windows that is earlier than Windows Vista. 
2) The remote computer is configured to support only the RDP security layer. 

Contact your network administrator or the owner of the remote computer for assistance. 

Do you want to connect anyway? 

I know that the remote server is good, it's in a memorized list of servers. But it is Windows Server 2003 or Windows 2000 Server. Although the prompt is correct, I don't want to have to acknowledge that prompt over and over again. 

Note: (added later) The obvious answer that I was alerted to from a comment from Blandname is to do this per session: click on the advanced tab in the Remote Desktop Connection tool and change the Authentication options to "Always connection, even if authentication fails". If you create your own RDP file, you can set it with "authentication level:i:0." 

If you want to set this at the server level or find out more about this setting, read on. 

I did some digging using Process Monitor from www.sysinternals.com (recently acquired by Microsoft) and found that the mstsc process was checking for some particular keys in the registry. Two of them seemed possible candidates and after testing I confirmed that AuthenticationLevelOverride is the key that applies to this situation. 

The registry key is a DWORD value at \\\\HKCU\\Software\\Microsoft\\Terminal Server Client\\AuthenticationLevelOverride 

I googled on AuthenticationLevelOverride and couldn't find very much information. But one article had a fair bit of information:http://support.microsoft.com/kb/895433. Here are the 3 possible values, at least in Windows Server 2003: 

Set the authentication level value to one of the following values: 

• 0 This value corresponds to "No authentication." 
• 1 This value corresponds to "Require authentication." 
• 2 This value corresponds to "Attempt authentication." 
I experimented and found that 2 is the default now. I tested the 3 modes and found that: 

0 -> Doesn't prompt. Yah! 
1 -> Gives a similar message but doesn't allow me to continue. This is the strictest. 
2 -> Gives the message but allows me to accept and continue. 

In my case, I don't even want the prompt so I set AuthenticationLevelOverride to 0 and I'm able to log into my Remote Desktop sessions without that extra prompt. 

Warning: this is a decrease in security so should only be changed if you are aware of the what and why of this change. 

In summary, if you want to remove the Authentication check on Windows Vista that prompts you every time you connect to a pre-Vista machine, add a DWORD registry entry called AuthenticationLevelOverride in the \\\\HKLM\\Software\\Microsoft\\Terminal Server Client\\ key and ensure that its value is set to 0. 

Another suggestion comes from : http://blandname.com/2006/09/30/microsoft-rdp-6-client-screenshots/ 

Where in the RDP client you can go to the advanced tab and change the Server Authentication prompt on how it warns you.

    Can't find the KB

    Unable to find the KB to address your issue ?  

      • Recent Articles

      • Change Reset Password Button Text

        Change the text of the "Reset Password" button on the UW Login Page How to change the text of the Reset Password button on the Login Page. Login to webNetwork and open webAdmin on your Relay Central Server Expand Customization Center Expand Tenants ...
      • Remove Reset Password Button From Login Page

        Remove the Reset Password Button from the Login Page How to remove the Reset Password button from the Unified Workspace login page. Login to webNetwork and open webAdmin on your Relay Central Server Expand Customization Center Expand Tenants Expand ...
      • Lenovo Unified Workspace End-of-Life Questions and Answers

        As of January 31st 2024, Lenovo Unified Workspace (formerly Stoneware WebNetwork) is no longer supported. This means that we no longer provide licenses, downloads, updates, patches, or technical assistance for this product. If you have any questions ...
      • How do I determine my Unified Workspace license expiration date?

        The best method for determining the licensing information including the expiration date of your Unified Workspace license: Login to your 8090 management console on each server This may take remoting into each LUW server and relay, opening a browser, ...
      • Lenovo Unified Workspace 7.0.2.13 Released

        Highlights of Unified Workspace 7.0.2.13 Before you install: Please view the installation notes here. 7.0.2.13 requires a 7.0 license file. Below is a list of enhancements and fixes released in Unified Workspace 7.0.2.13 Fixed external storage ...
      • Related Articles

      • Terminal Server (Remote Desktop Services) licensing.

        When Remote Desktop Services role is installed you will be given 3 options.  Configure Later - You can postpone your decision and simply select Configure Later. You'll have a grace period of 120 days to configure licensing and select a licensing ...
      • Remote computer requires authentication be enabled to connect

        The customer is trying to make a terminal server webapp and when they connect terminal server gives the message :  The remote computer requires that authentication is enabled to connect.  Remote computer: xxxx.xxxx.xxx  The connection cannot proceed ...
      • Remote Desktop Connection Broker

        Issue: Does Unified Workspace work with Remote Desktop Connection Broker? Solution: Unified Workspace does not currently work with Remote Desktop Connection Broker. Here is a URL on how a Remote Desktop Connection Broker works: ...
      • Cannot connect to Terminal Server

        I'm using Remote Desktop Connection to connect to my Terminal Server. When opening Remote Desktop Connection, I put in the FQDN (ts.example-cloud.com) in the Computer field, switch to the tab Security in the Remote Desktop Connection (the last tab or ...
      • What is needed to setup the remote desktop feature?

        Issue The administrator would like to allow users to remotely connect to their workstations through Unified Workspace. Solution Give users access to the PersonalRDP or PersonalVNC links. Next have the user login and click on Personal RDP or Personal ...