All-
I have attempted this so many times at this point I can do it in my sleep.
I certified a domain controller (Windows 2003 Standard SP2) following the MS whitepaper which includes creating the request.inf file, filled out all fqdn info etc. Created the request.req file from there a new cert called certnew.cer.
When I install services to check where the certs were installed, everything looks correct -there is a cert in the Personal store, one in the Trusted and Intermediate root etc etc.
my problem is when I use ldp.exe or have my ldap guys trying to check and see if the cert is on the domain controller over port 636 (ldap port) if fails to find the cert. I have re-tried this installation of the cert yet now I have learned how to use ldp.exe, make the connection of port 636 (this identifies ldaps connectivity and that the cert is on the dc) yet it continuously fails.
The only thing I can thing of is when I was creating the request file I believe it tells you to save it as basecode64 file, which I honestly tried using a command line cert option pointing to the request.req file
Has anyone tested a dc they might have applied an ssl cert to over port 636 ldap port where it failed?
Please if you have a moment, let me know. I am running in circles here.
thanks
blade
I have attempted this so many times at this point I can do it in my sleep.
I certified a domain controller (Windows 2003 Standard SP2) following the MS whitepaper which includes creating the request.inf file, filled out all fqdn info etc. Created the request.req file from there a new cert called certnew.cer.
When I install services to check where the certs were installed, everything looks correct -there is a cert in the Personal store, one in the Trusted and Intermediate root etc etc.
my problem is when I use ldp.exe or have my ldap guys trying to check and see if the cert is on the domain controller over port 636 (ldap port) if fails to find the cert. I have re-tried this installation of the cert yet now I have learned how to use ldp.exe, make the connection of port 636 (this identifies ldaps connectivity and that the cert is on the dc) yet it continuously fails.
The only thing I can thing of is when I was creating the request file I believe it tells you to save it as basecode64 file, which I honestly tried using a command line cert option pointing to the request.req file
Has anyone tested a dc they might have applied an ssl cert to over port 636 ldap port where it failed?
Please if you have a moment, let me know. I am running in circles here.
thanks
blade