Server 2008 R2 Terminal server rejecting ALL certificates as invalid

I have a 2008r2 Terminal server that is categorically rejecting ANY certificate it encounters.  Certs that I know for certain are valid.  Everything I can find is related to specific applications, but this is happening across all browsers, and every application that uses SSL.  Malware scans come up clean.  I reset the security providers using IISCrypto (https://www.nartac.com/Products/IISCrypto/), mostly out of desperation.

I'm nearly ready to roll this system back, but I'm not certain of when the behavior started.

The eventviewer is full of Event 36882 SChannel errors that state:
"The certificate received from the remote server was issued by an untrusted certificate authority. Because of this, none of the data contained in the certificate can be validated. The SSL connection request has failed. The attached data contains the server certificate."

Again, this is happening with every cert encountered by the system regardless of source or issuing CA.
LVL 16
Jon BrelieSystem ArchitectAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

VB ITSSpecialist ConsultantCommented:
First thing I'd check is to make sure the date and time is set correctly on the server.

Next step would be to re-synchronize the Trusted Root Certificates on your server as it sounds like something has happened to your Trusted Root CAs. Click on the Microsoft Fix it link on this page underneath For Windows 8.1, Windows 8, Windows 7, Windows Server 2012 R2, Windows Server 2012 or Windows Server 2008 R2: http://support.microsoft.com/kb/931125
0
Jon BrelieSystem ArchitectAuthor Commented:
Time and date are good.  The Fixit didn't appear to work.

What I've done as a stopgap to get things working again was to export the Trusted Root CA store from another server and import it directly on the system in question.  That appears to have mitigated the issue for now, but I fear the underlying update capability is still broken and will cause me issues down the road.

The weird thing is that these systems are all spun up off of templates and configured via policy.  All patches are applied in groups, so my source server and the server having this issue *should* be identical.

Anyway, I'll leave this open for a while in case anyone has any idea what the underlying issue is, but the fire is out for now.
0
VB ITSSpecialist ConsultantCommented:
OK good, at least we know the issue was with your Trusted Root CA store. My next recommendation was going to be to clear out the current certificates in your Trusted Root CA store by exporting them first, then copying over certificates from a working machine.
The weird thing is that these systems are all spun up off of templates and configured via policy.  All patches are applied in groups, so my source server and the server having this issue *should* be identical.
Only thing I can think of is if a Windows Update did not install itself correctly. It's been known from time to time that an update can break one machine but not another.

Definitely keep an eye out on this server over the next few days in case there's an issue with the certificate update mechanism on your TS.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Jon BrelieSystem ArchitectAuthor Commented:
Well, it's been a few weeks and the steps taken above are still working.  I don't know if I'll have an issue with this system at a later date or not, but for now at least, it's easier to import certs from another system than it is to dig through thousands of updates to determine if one of them needs to be re-applied.

If it continues to be a problem, I will probably scrap the system and deploy a new one.  Thanks for your help.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
SSL / HTTPS

From novice to tech pro — start learning today.