Time or date difference using remote desktop

Question

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.

You said you checked the server but what about the client? The time on the server and client need to be close to each other (I believe within 5 minutes though I'm willing to be corrected) for the kerberos authentication to work. — webtoe, Apr 20 '12 at 10:13
FYI... To anyone reading this in an AD or domain environment. If you have a domain controller or many of them, you might take a quick look at the date and time of the domain controller servers if you run into this when you RDP into machines that give this message. In my case I guess a CMOS battery went out and when the server rebooted after an unexpected power outage, the time did not come back up correctly. Simply adjusting the DC to have the correct time and then rebooting the VM machine that was giving the message corrected. Just restarted the VM before correcting the DC time did not fix. — Pimp Juice IT, May 25 '17 at 18:28

score 10 · Accepted Answer · answered May 21 '12 at 14:35

10

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

answered May 21 '12 at 14:35

Matt

579
5
11
24

7

Of course it did, it's Windows! ;-P – Dave Forgac May 21 '12 at 14:50
+1 worked for me also (although no new updates were needed). – Jonathan Apr 04 '13 at 17:33
13

In my case, using the IP address instead of the machine name did the trick. It's a workaround though. – mati Feb 12 '14 at 15:28
2

@Matias Using the IP Address worked for me. Thanks. Do you happen to know why this is? – Jean Carlos Suárez Marranzini Feb 18 '16 at 12:04

score 5 · Answer 2 · answered Mar 26 '15 at 16:01

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.

score 1 · Answer 3 · answered Jan 18 '22 at 15:37

1

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.

answered Jan 18 '22 at 15:37

StayOnTarget

170
7

score 1 · Answer 4 · answered Sep 11 '19 at 20:22

1

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.

answered Sep 11 '19 at 20:22

Some_network_guy

11
1

score 0 · Answer 5 · answered Oct 21 '20 at 16:26

0

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.

answered Oct 21 '20 at 16:26

Ray Klassen

1
1

score 0 · Answer 6 · answered Jan 18 '22 at 15:39

0

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.

answered Jan 18 '22 at 15:39

Leopold

1

This does not really answer the question. If you have a different question, you can ask it by clicking [Ask Question](https://serverfault.com/questions/ask). To get notified when this question gets new answers, you can [follow this question](https://meta.stackexchange.com/q/345661). Once you have enough [reputation](https://serverfault.com/help/whats-reputation), you can also [add a bounty](https://serverfault.com/help/privileges/set-bounties) to draw more attention to this question. - [From Review](/review/late-answers/509282) – bjoster Jan 24 '22 at 13:37

score 0 · Answer 7 · answered Jul 24 '18 at 22:21

0

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

answered Jul 24 '18 at 22:21

Abdullah

1

score 0 · Answer 8 · edited Jan 18 '22 at 19:36

0

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.

edited Jan 18 '22 at 19:36

StayOnTarget

170
7

answered Mar 07 '19 at 18:15

Steve Gray

1
1

1

Hi, please complete your answer detail, as is, it's not really an answer. – yagmoth555 Mar 07 '19 at 19:56
The issue was that I had a VPN connection open on the machine, that kept me from connecting to it. I closed the connection and the error went away. This won't work in every situation... but it worked in mine. Just trying to be helpful. – Steve Gray Mar 08 '19 at 20:26
2

Hi, I more mean your sentence is not complete in your answer, it miss the end, you can just edit that to be more precise. – yagmoth555 Mar 08 '19 at 20:39

Time or date difference using remote desktop

8 Answers8

Linked