No, but it's a moot point now. Long story.
From: Steve Kradel [mailto:skra...@zetetic.net]
Sent: Thursday, August 02, 2012 6:50 PM
To: NT System Admin Issues
Subject: Re: certificate status could not be determined...
What CRL and OCSP fields are on the cert?
Have you tried browsing to
...@lgnetworksinc.com
>
> [image: Description: Description: cid:image001.jpg@01CCF24C.F9B05160]
>
> ** **
>
> *From:* Richard Stovall [mailto:rich...@gmail.com]
> *Sent:* Thursday, August 02, 2012 5:30 PM
>
> *To:* NT System Admin Issues
> *Subje
Subject: Re: certificate status could not be determined...
That shouldn't be a problem. We use GoDaddy certs all the time for all kinds
of things including Exchange.
This may be way off base, but are the GoDaddy intermediate certs installed?
--
I've also seen goofy stuff like this when th
iption: cid:image001.jpg@01CCF24C.F9B05160]
>
> ** **
>
> *From:* Steve Kradel [mailto:skra...@zetetic.net]
> *Sent:* Thursday, August 02, 2012 2:56 PM
> *To:* NT System Admin Issues
> *Subject:* Re: certificate status could not be determined...
>
> ** **
>
> I've also se
I've also seen this error when the cert has no CRL information on it (i.e.,
the issuing CA policy includes zero CRL publication URLs). Yes, the cert
is valid... no, Exchange won't take it.
--Steve
On Thu, Aug 2, 2012 at 11:41 AM, Daniel Chenault <
dchena...@lgnetworksinc.com> wrote:
> Exchange
