Remote Desktop cannot verify the identity of the remote computer because there is a time or date difference between your computer and the remote computer

Chicago Area Laptop for rent: $35 per day plus $10 for additional day

Remote Desktop can't connect to the remote computer - Resolution with screenshots

Situation: When attempting to RemoteApp or RD Web on Windows 2008 R2, you may receive this message: "Remote Desktop cannot verify the identity of the remote computer because there is a time or date difference between your computer and the remote computer "computer name" for one of these reason:

1) Your user account is not listed in the RD Gateway's permission list.

2) You might have specified the remote computer in NetBIOS format (for example, computer1), but the RD Gateway is expecting an FQDN or IP address format (for example, omputer1.fabrikam.com or 157.60.0.1).

Case 1: The remote computer is running multihomed computer. Disabling one of NICs fix the problem. Or creating a NIC teaming instead of using two NICs.

Case 2: Change the network adapter to a dedicated NIC in RDP-Tcp connection. Please refer to this link: How to modify RDP-Tcp Network Adapter in TS and RDS - Step by step with screenshots

Case 3: We fixed this issue by changing HKLM\SYSTEM\CurrentControlSet\Control\Terminal Server find that entry from 0 to 1.

Case 4: You must use a certificate with a SAN (Subject Alternative Name) and this must match the internal FQDN.

Case 5: You may have a Port assignment conflict. You can use netstat tool to determine if port 3389 (or the assigned RDP port) is being used by another application on the Remote Desktop server

Case 6: It could "Limit number of connections" Policy under Local Computer Policy > Computer Configuration>Administrative Templates > Windows Components > Remote Desktop Services> Remote Desktop Session Host> Connections

Case 7: it could be missing Remote Desktop Services Logon rights.

Case 8: You may have an incorrectly configured Authentication and Encryption setting.

Case 9: You may have a Certificate Corruption.

Case 10: This error could be caused by a Windows Update to Remote Desktop Protocol 8.0. The workaround is to uninstall KB2592687 and reboot.

Case 11: If only one special machine can not connect to the RDS server, there is an issue on your client machine.

Contact a consultant