The Remote Desktop cannot verify identity time or date difference error occurs while trying to connect to a remote server via RDP. Don’t worry. This post list 6 tested solutions to help you fix it.
During my attempt to establish an RDP connection to a remote server within the Active Directory (AD) domain, I encountered an error. Despite inputting the accurate domain credentials for the RDP user, the following error message surfaced, resulting in the closure of the RDP client window. I am seeking guidance on resolving this error.
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. Make sure your computer's clock is set to the correct time, and then try connecting again. If the problem occurs again, contact your network administrator or the owner of the remote computer.”
- Question from Reddit
Encountering the "Remote Desktop cannot verify identity time date difference" error when attempting to connect to a remote server within the AD domain via RDP? Here are four helpful tips that can assist you in resolving this issue.
To address the "Remote Desktop cannot verify identity time or date difference" error, it is crucial to ensure that the time and date settings are accurate and consistent on both the local and remote computers. Follow these steps to check and synchronize the time settings:
Step 1. Run Command Prompt as administrator.
Step 2. Execute the following command to check the time on the remote computer:
Step 3. If necessary, manually synchronize the time and restart the w32time service using the following commands:
To address the issue, "Remote Desktop cannot verify identity time date difference," it is essential to ensure that the DNS settings are configured correctly on the Windows machine initiating the remote desktop connection. Follow these steps to verify the DNS settings:
Step 1. If you have physical access to the remote computer, check the DNS server specified in the network adapter settings.
Step 2. Ensure that the DNS server can be accessed from the remote server by using the following command:
If the DNS server is unresponsive, ensure that it is functioning correctly or consider specifying an alternative DNS server address.
Additionally, if multiple network adapters are utilized on the remote computer, confirm that the routing table is accurate when accessing the DNS server. Sometimes, the computer may attempt to access the DNS server using a different network adapter with a distinct IP subnet. By verifying and correcting these settings, you can mitigate the "Remote Desktop cannot verify identity time or date difference" error.
If the error suggests that the RDP client failed to authenticate using Kerberos, an alternative solution is to connect to the remote computer using its IP address instead of the fully qualified domain name (FQDN) in the RDP client connection window. By doing so, Kerberos authentication will be bypassed. Follow these steps:
Step 1. Click on the Start menu and then navigate to Settings.
Step 2. Locate and click on Network & Internet.
Step 3. In the Network & Internet interface, find Advanced network settings and click on Change adapter options below.
Step 4. Right-click on your network and select Properties.
Step 5.Uncheck Internet Protocol Version 6 (TCP/IPv6) and click on OK.
To address the issue, it is crucial to confirm that the same "RDP Security Layer" is selected on both the local and remote computers. Follow these steps:
Step 1. Press Win + R to open the Run dialog box, then type "gpedit.msc" and press OK. This will open the Local Group Policy Editor window.
Step 2. Navigate to the following path: Computer Configuration > Administrative Templates > Windows Components > Remote Desktop Services > Remote Desktop Session Host > Security.
Step 3. Locate the setting named "Require use of specific security layer for remote connections" and click on it. Change its status to Enabled. From the drop-down list, select "RDP" as the Security Layer.
To address the issue, it is recommended to install the latest Windows updates. Follow these steps:
Step 1. Open the Control Panel and locate Update & Security.
Step 2. In the Update & Security interface, check if a new version is available. If an update is available, proceed to download and install it (ensure that you have backed up your data before initiating the update).
If none of the aforementioned solutions resolve the "Remote Desktop cannot verify identity time date difference" error, it is worth considering AnyViewer as an alternative. AnyViewer is a free remote desktop software designed specifically for Windows. It allows you to take complete control of a remote computer, regardless of your physical location.
In addition, AnyViewer offers several advantages over Remote Desktop Connection, making it a preferred choice for remote desktop requirements:
By considering AnyViewer as an alternative, you can explore a robust and feature-rich remote desktop solution that may better suit your needs while addressing the "Remote Desktop cannot verify identity time date difference" error.
Step 1. Download, install, and launch AnyViewer on both computers. Go to Log in, and then click Sign up. (If you already have signed up on its official website, you can log in directly.)
Step 2. Fill in the signup information.
Step 3. Then you can see you successfully logged in to AnyViewer. Your device will automatically be assigned to the account you've logged in to.
Step 4. Log in to the same AnyViewer account on the two devices, then you can achieve an unattended remote connection by clicking One-click control.
You can also upgrade your account to a Professional or Enterprise plan. What can a professional or enterprise plan brings to you:
If you come across the "Remote Desktop cannot verify identity time date difference" error and none of the suggested solutions prove effective, we suggest you give AnyViewer a try. AnyViewer is a no-cost remote desktop software designed for Windows, offering extensive control over remote computers. With internet accessibility, chat functionality, support for multiple sessions, and compatibility with Windows Home, AnyViewer stands out as an excellent option for resolving errors and ensuring a smooth remote desktop experience.
