I'm dealing with a frustrating issue where some users are getting a certificate error when they try to connect to our terminal server, which distributes the load between two servers. The error message says, 'The connection has been terminated because an unexpected server authentication certificate was received from the remote computer.' I've already updated the certificates on both the servers and client PCs, but the problem persists. I'm open to any suggestions for fixing this!
3 Answers
I’ve had a similar issue when connecting to terminal servers from different domains. To solve it, I just added the domain prefix to my username like this: domainmyuser, and that worked. Might be worth a shot if your setup involves multiple domains too.
Make sure the certificate matches the exact name your users are using to connect. Also, check the authority that issued the certificate—if it's from your internal AD Certificate Services, it might be causing issues. If the name is too generic, it can lead to these authentication problems.
How exactly are you handling load balancing? I ask because I found that some setups using DNS round robin can sometimes cause these types of issues. It’s pretty basic and can lead to problems if the DNS records aren't set up perfectly.
Related Questions
Can't Load PhpMyadmin On After Server Update
Redirect www to non-www in Apache Conf
How To Check If Your SSL Cert Is SHA 1
Windows TrackPad Gestures