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,489 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
Netscaler Common Configuration How To guides

If you use NetScaler you will want to see these guides. The NetScaler How To Guides show administrators how to get NetScaler up and configured by providing instructions for common scenarios and some not so common ones.

 

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

Is Your Active Directory as Secure as You Think?

More than 75% of all records are compromised because of the loss or theft of a privileged credential. Experts have been exploring Active Directory infrastructure to identify key threats and establish best practices for keeping data safe. Attend this month’s webinar to learn more.

Question has a verified solution.

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

I was supporting a handful of Windows 2008 (non-R2) 2 node clusters with shared quorum disks. Some had SQL 2008 installed and some were just a vendor application that we supported. For the purposes of this article it doesn’t really matter which so w…
A procedure for exporting installed hotfix details of remote computers using powershell
This tutorial will walk an individual through the process of transferring the five major, necessary Active Directory Roles, commonly referred to as the FSMO roles to another domain controller. Log onto the new domain controller with a user account t…
This tutorial will show how to configure a single USB drive with a separate folder for each day of the week. This will allow each of the backups to be kept separate preventing the previous day’s backup from being overwritten. The USB drive must be s…

930 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

Need Help in Real-Time?

Connect with top rated Experts

18 Experts available now in Live!

Get 1:1 Help Now