Server's certificate chain has expired or is not yet valid

I updated our SSL Cert for our Exchange 2003 server back in January. I believe the current certificate was due to expire yesterday (April 5th, 2009). As of this morning, I am receiving the following message on Entourage clients which have been configured with the option "This LDAP server requires a secure conection(SSL)". I do not encounter certificate errors when I connect to the Exchange server via OWA. I have verified on my exchange server that the current certificate installed for the 'Default Web Site' is valid, it expires on April 5th, 2011. Is there perhaps another location in which I missed updating the cert? Any info would be greatly appreciated. I am attaching a screen cap of the error message which Entourage is producing.
Who is Participating?

Improve company productivity with a Business Account.Sign Up

sgs521Connect With a Mentor Author Commented:
Corrected this issue by removing and re-adding the certificate, rebooted the server. 5 days now and no further incidents of the ssl error client side.

How is this client connecting to the server?  If POP/IMAP, have you made sure the new certificate is installed on those services?

sgs521Author Commented:
The client connects as an exchange client, which in my limited understanding of how Entourage actually talks to exchange, I think is over http. There's a configuration option in the account setup that specifies the account is on exchange, then I have to enter both the exchange server and ldap server, which is the same server address. We don't have anyone who is using pop, smtp or imap directly from the email client in our environment.
NEW Internet Security Report Now Available!

WatchGuard’s Threat Lab is a group of dedicated threat researchers committed to helping you stay ahead of the bad guys by providing in-depth analysis of the top security threats to your network.  Check out this quarters report on the threats that shook the industry in Q4 2017.

sgs521Author Commented:
Thanks strung, the first link seemed to fix this. Just really odd that it had been working before this when we'd never installed the cert client side. Going to do more testing across other workstations before I accept as solution, but it looks like that may be the one.
Glad to be of help

sgs521Author Commented:
An update, I returned to the office this morning, booted up my laptop, launched Entourage and received the error again. So it looks like perhaps installing the cert client side only temporarily fixed until reboot. I'm thinking there's still something I've missed when updating the secure cert on the exchange server. The only way to repeatedly duplicate the issue is by turning on the "this ldap server requires a secure connection" option under account settings in Entourage. Is there another location that the certificate needs to be installed within Active Directory to secure it's ldap communication?
sgs521Author Commented:
Also as an update, on the configuration of the exchange server, this was put in place prior to my arrival, but it was configured with AD and Exchange on the same server.
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.