Re: 2008; Certificate problems



I am having the exact same problem as described below, and we are also using a GoDaddy certificate that has never been a problem in the past. I sure hope we find an answer soon.

I am having the exact same issue with Macs that have been updated to Office
2008 SP1. There are NO issues on Entourage 2004 (fully patched) or Entourage
2008 WITHOUT SP1. I have two domains, one with Exchange 2007 SP1 rollup 2,
the other with Exchange 2007 rollup 6. They both behave the same. I get this
popup:

"Unable to establish a secure connection to domain.com because the server or
IP address does not match the name or IP address on the server's certificate.

If you continue, the information you view and send will be encrypted, but
will not be secure."

This popup appears once per session (when it is initiated) and causes NO
problems with mail flow.

Bill:

All clients are configured as per the instructions in the link you gave
(were before installing SP1 as well). The Exchange server SSL certificates
are from a commercial CA (Go Daddy) and certainly DO include the machine
name. I am assuming that the problem has to do with the "enhancements" in the
autodiscover feature intruduced with SP1, but that is as far as I can get.

As far as installing certificates on the Macs, I never had to before. The
keychain on the Macs show a root certificate from my CA and that has been
good enough in the past (prior to Office 2008 SP1).

Any help would be appreciated.

"William Smith" wrote:

Russell Tolman wrote:
I am having certificate issues again. Not really sure if the issue is anew
one or a continuation. This error appears on every Mac that has Office 2008
installed and updated to SP1.

I will try and give as much detail as possible.

All Intel based computers.
All OSX 10.5.2
All Updates for OSX done.
Office 2008; either 12.0.1 or 12.0 before SP1 Applied.

Every single computer in or School district shows the error shown in the
picture I included with this post.

This appears to be a problem with your certificate or what you're using
for your Exchange server name.

According to your screenshot Entourage is trying to connect to a server
named "graniteschools.org", which is not a server name but a domain
name. Your server name should look something like
"echange.graniteschools.org".

Make sure the certificate you're installing on your Macs is a
certificate specifically for your server's fully qualified domain name.

Since I don't know what you're using for your server addresses all I can
do is point you to these setup instructions for Entourage 2004 (they're
still valid for 2008).

"Connecting Entourage to an Exchange Server at work"


Hope this helps!

--

bill

William M. Smith, Microsoft Interop MVP - Mac/Windows
Entourage Help Page
Entourage Help Blog


.



Relevant Pages

  • Re: 2008; Certificate problems
    ... I am having the exact same issue with Macs that have been updated to Office ... the other with Exchange 2007 rollup 6. ... IP address does not match the name or IP address on the server's certificate. ... The Exchange server SSL certificates ...
    (microsoft.public.mac.office.entourage)
  • Re: 2008; Certificate problems
    ... Have never setup a certificate, using Intermedia.net as an Exchange 2007 provider, no problem with Entourage 2004, or 2008. ... The Exchange server SSL certificates ...
    (microsoft.public.mac.office.entourage)
  • RPC over HTTP, Microsoft solution
    ... Exchange Server 2003 RPC over HTTP Deployment Scenarios ... Place a check in the box next to 'Certificate Services' and click 'Yes' ...
    (microsoft.public.exchange.setup)
  • Re: OWA 2003 w/ Smart Card Authentication.
    ... Exchange 2003 server via ActivSync. ... the IIS certificate. ... Whether or not authentication will succeed is completely dictated by ... Server's SSL certificate must be configured on root of v-server via ...
    (microsoft.public.exchange.connectivity)
  • Re: Configuring LDAP on Entourage 2004 OS X
    ... Microsoft CSS Online Newsgroup Support ... does not work with a self signed SSL certificate OR with the SSL ... configure the System to allow OMA and "Server ActiveSync" access from the ... Configuring Exchange Server 2003 for Client Access. ...
    (microsoft.public.windows.server.sbs)