Jump to content

Recommended Posts

Posted

Morning all,

 

We have an internal CA server. I have renewed SSL cert for one the member server.

 

All the steps done correctly, but when I open the website, still says that cert is not valid.

 

Although new cert is bind.

 

Pls advise

Posted

Can you please vertfy;

The cert server has issued a certificate to itself, and then you have used Group policy, to tell every other computer in your domain, to accept that server as a "Trusered Root Certificate server".

That you have added Microsoft updated server templates, to the cert server templates, note there is a special requirement for DC.

That you have bound the server to use the new certificate, and removed the old certificate.

 

Sorry to be pedantic, but server certificates requirements are not simple.

Posted
Can you please vertfy;

The cert server has issued a certificate to itself, and then you have used Group policy, to tell every other computer in your domain, to accept that server as a "Trusered Root Certificate server".

That you have added Microsoft updated server templates, to the cert server templates, note there is a special requirement for DC.

That you have bound the server to use the new certificate, and removed the old certificate.

 

Sorry to be pedantic, but server certificates requirements are not simple.

 

CA server has issued a certificate for the webserver.

 

Website published through iis, internally only.

Posted

As julian implies.

 

The CA Issuing a cert does not magically make any clients trust it. You also need to ensure the name you are referring to it and the certificate name are on-and-the-same.

 

As a test, I would look at the cert properties, export it to file and transfer to test PC. From there run mmc as admin and run certificate services as the computer and import the certifcate into trust root CAs

 

IF the browser is now happy then it implies the computer doesnt trust the CA. If it still doesnt then it may be a naming problem.

  • Thanks 1
Posted
As julian implies.

 

The CA Issuing a cert does not magically make any clients trust it. You also need to ensure the name you are referring to it and the certificate name are on-and-the-same.

 

As a test, I would look at the cert properties, export it to file and transfer to test PC. From there run mmc as admin and run certificate services as the computer and import the certifcate into trust root CAs

 

IF the browser is now happy then it implies the computer doesnt trust the CA. If it still doesnt then it may be a naming problem.

 

Many thanks !!

 

Will try this.

  • 2 weeks later...

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...