Solved

Remote Desktop cannot connect to the remote computer because the authentication certificate received from the remote computer is expired or invalid.

Posted on 2009-05-14
6
12,648 Views
Last Modified: 2012-05-07
Using remote desktop attempting to access a 2008 server I am getting the following error message.  The error does not appear when using XP, the time difference between the server and work station is  negligible - Remote Desktop cannot connect to the remote computer because the authentication certificate received from the remote computer is expired or invalid.
In some cases, this error might also be caused by a large discrepancy between the client and server computers.

0
Comment
Question by:Melvinf
  • 3
  • 2
6 Comments
 
LVL 74

Expert Comment

by:Glen Knight
ID: 24384343
Try allowing the less secure remote desktop in Windows 2008 Server by default it requires a higher level of security.
Right click my computer, select properties then Advanced System Settings.
You will then see 3 options.  Select "Allow connections from computers running any version of Remote Desktop"

Alternatively if you are running XP SP3 it should have 6.1 version of the remote desktop client
0
 

Author Comment

by:Melvinf
ID: 24384584
I checked the settings and "Allow connections from computers running any version of Remote Desktop"
is set.
0
 
LVL 1

Expert Comment

by:Saldavo
ID: 24384945
This message can appear when the date isn't set correctly in your bios.
0
PRTG Network Monitor: Intuitive Network Monitoring

Network Monitoring is essential to ensure that computer systems and network devices are running. Use PRTG to monitor LANs, servers, websites, applications and devices, bandwidth, virtual environments, remote systems, IoT, and many more. PRTG is easy to set up & use.

 

Author Comment

by:Melvinf
ID: 24385256
I believe you are on to something.  Is there a way to set the bios clock without rebooting the system?
0
 
LVL 1

Accepted Solution

by:
Saldavo earned 125 total points
ID: 24385473
I have seen such a utilty to change some bios settings in Windows. However it was developed especially for that type mainboard. If your mainboard doesn't come with such a utility, you should reboot your system to change the bios settings.
0
 

Author Comment

by:Melvinf
ID: 24394425
The solution came down to rebooting the server.  Funny the problem on affected Vista work stations.

Thank you for the help.
0

Featured Post

Announcing the Most Valuable Experts of 2016

MVEs are more concerned with the satisfaction of those they help than with the considerable points they can earn. They are the types of people you feel privileged to call colleagues. Join us in honoring this amazing group of Experts.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Suggested Solutions

Restoring deleted objects in Active Directory has been a standard feature in Active Directory for many years, yet some admins may not know what is available.
A procedure for exporting installed hotfix details of remote computers using powershell
This tutorial will show how to push an installation of Backup Exec to an additional server in both 2012 and 2014 versions of the software. Click on the Backup Exec button in the upper left corner. From here, select Installation and Licensing, then I…
This tutorial will walk an individual through setting the global and backup job media overwrite and protection periods in Backup Exec 2012. Log onto the Backup Exec Central Administration Server. Examine the services. If all or most of them are stop…

792 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question