Home / server / Questions / 381477
Accepted
Matt
Asked: 2012-04-21 02:03:57 +0800 CST

Time or date difference using remote desktop

  • 772

When remoting into 2008 R2 we are getting 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.

I have checked the server and the time is correct.

Checking the event logs it is saying The RPC server is unavailable I'm not sure if this is related.

Additional note: We have Nagios monitoring, and it has reported Result from smbclient not suitable.

windows-server-2008-r2

8 Answers

  1. Best Answer

    Restarting the server and installing all of the latest updates solved the issue.

    • 10

  2. A little old but there are several other options for this issue like DNS issues... please take a look at this link:

    http://www.chicagotech.net/remoteissues/rdc4.htm

    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.

    But yeah, most of the times just rebooting the server fix this issue.

    • 5

  3. Make sure port TCP 88 isn't blocked by a firewall; Kerberos uses this port in addition to 3389 to authenticate the session, if you have Network Level Authentication enabled.

    • 1

  4. I used the machine's IP address instead of the hostname when making the connection, and that circumvented the error.

    This is obviously not a complete fix but it was a very useful workaround.

    • 1

  5. In my case issue was static IP. Once I switched it to dynamic the issue was resolved.

    • 0

  6. In my case I had left a VPN connection open on the machine (to a different time zone, don't know if that's important) I logged on directly and closed the connection and the error went away.

    • 0

  7. My users have this error if their password for a remote computer is saved locally in "Remote Desktop" settings and it's wrong. This is 100% repeatable.

    • 0

  8. And one more potential cause. ipV6. Disable it. Whenever I have a machine with ipV6 enabled, there are network problems. I JUST had a backup server that was inaccessible with RDP. I WAS able to access it by using the IP address instead of the backup server name. That's quite telling. It took me a while to find the issue. My time wasn't wasted. I at least got to clean up some old DNS entries. But the solution was: go to network and disable ipV6. Problem solved. Gawd, I hate ipV6. A security and reliability nightmare.

    • 0