Also, we make sure that we can access this DNS server from the remote server. Since we have physical access to the remote computer, we check the DNS server in the network adapter settings. Note: If the remote server is a virtual machine, we ensure that the time synchronization with the host hypervisor is disabled in the VM settings. Net stop w32time & net start w32time & w32tm /resync w32tm /config /manualpeerlist:your_ntp_server_ip NTP,0x8 /syncfromflags:manual Here is the command we use to sync the time manually if necessary and restart the w32time service. We run the below command to check the time on the remote computer. Also, we made sure that the time and time zone was the same on both computers. In order to fix this error, our Support Engineers opened the remote server console over ILO. How we resolve the error ‘remote desktop cannot verify the identity time or date difference’ It happens because the time difference between the local and remote computer exceeds 5 minutes. This error specifies that the RDP client couldn’t authenticate using Kerberos. This error occurs while trying to connect to a remote server in the AD domain via RDP.įor instance, the error appears as below. Why does the ‘remote desktop cannot verify the identity time or date difference’ error occur

Today we’ll take a look at the causes for this error and see the fix. Here at Bobcares, we have seen several such Windows-related errors as part of our Server Management Services for web hosts and online service providers.

The error ‘remote desktop cannot verify the identity time or date difference’ occurs while trying to connect to a remote server in the AD domain via RDP.

Chrome remote desktop out of date hosts