An SSL/TLS certificate trust issue on Windows Server generally indicates that the client cannot establish a trusted certificate chain between the server's SSL/TLS certificate and a trusted root certification authority (CA). This can occur when the server certificate is self-signed, has expired, is missing an intermediate certificate, or was issued by an internal CA whose root certificate is not trusted by the client.
Start by examining the certificate installed on the Windows Server. Use the Certificates MMC snap-in (certlm.msc) and inspect Personal > Certificates under the Local Computer account. Verify that the certificate is within its validity period, has an associated private key, and includes the appropriate Server Authentication Enhanced Key Usage (EKU). Also verify that the certificate's Subject Alternative Name (SAN) includes the DNS name clients use to connect to the server.
Next, verify the certificate chain. Open the certificate and examine the Certification Path tab. Windows should be able to build a complete chain from the server certificate through any intermediate CA certificates to a trusted root CA. If the chain is incomplete, install the missing intermediate certificates in the Local Computer's Intermediate Certification Authorities store. If the issuing root CA is internal, distribute its root certificate to client computers and install it in Trusted Root Certification Authorities.
You can use PowerShell to examine the certificate stores and verify certificate details. For example:
Get-ChildItem Cert:\LocalMachine\My |
Select-Object Subject, Issuer, NotBefore, NotAfter, Thumbprint
You can also use the Windows certificate verification utility:
certutil -verify server.cer
Finally, verify that the application or service is actually presenting the intended certificate. IIS, RDP, LDAPS, and other services can have separate certificate bindings or configuration requirements. For IIS, inspect the HTTPS binding in IIS Manager and confirm that the correct certificate is selected. For LDAPS, verify that the certificate meets the domain controller's requirements and is available in the appropriate computer certificate store.
Keep in mind that installing a certificate on the server alone does not establish trust. The client must trust the certificate's issuing CA, and the certificate must be valid for the server name being accessed.
If the above response helps answer your question, remember to "Accept Answer" so that others in the community facing similar issues can easily find the solution. Your contribution is highly appreciated.
hth
Marcin