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 cannot verify the identity of the remote computer because there is a time or date difference between your computer and the remote computer

Case 1I have been accessing one of my windows 7 remotely using RDC. For some I can’t access it any more wit 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. 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."

I have tried to access this windows 7 from Vista and windows 7 workstation, but all get the same error. I have checked the date and time are the same on all computers.

Fix: We found the client changed the default gateway. We fixed the problem by rebooting the remote computer.

Case 2: After the client renewed the IP address, they had this issue. Restarting the remote computer fixes the problem.

Case 3: Try to logon different user.

Case 4: • I just had the same problem connecting from one Win7 box to another Win7 box. What helped me was changing a connection setting from "Automatically detect RD Gateway server settings" to "Do not use an RD Gateway server" in Options-->Advanced-->Settings.

Case 5: In my case, it is DNS issue. After we moved one Hyper-V VM from one physical server to another physical server, we receive this error: "Your computer could not connect to another console session on the remote computer because you already have a console session in progress." If I use IP address, I can login without any problems. When I ping the remote computer by name, it replies with IPv6 IP address. Then I checked the DNS record, I don’t see the remote computer A record. Running ipconfig /flushdns and ipconfig /registerdns on the remote computer doesn’t fix the problem. Finally, I found the problem is the remote computer has incorrect DNS server IP address and it was using router as DNS server. Changing the DNS to domain controller as DNS fixes the problem.

Post your questions, comments, feedbacks and suggestions

Contact a consultant