Entourage 2004 and Exchange 2003: Getting rid of that RootCertificate Warning

[Gerry Simmons]

Folks,

I've been doing extensive research on this subject, and several of you have
offered great tips. I'm now convinced that I, in fact, DO have the correct
Root Certificate from our Exchange Server installed. I am equally convinced
that I have Entourage 2004 configured correctly to access all the services -
LDAP and DAV - correctly.

But, still no joy!

I've run across an interesting article written by someone at the University
of Texas, that was experiencing the same issues. He's obviously a S/W dude.
Read his article:

http://www.talkaboutmac.com/group/microsoft.public.mac.office.entourage/mess
ages/44036.html

His conclusion is that there is one or more bugs in OS 10.3.X and/or
Entourage 2004 that are the root of the issue.

My question to you all is: Does anyone have Entourage 2004 connecting with
their Exchange Server 2003 - using SSL - and NOT getting the Error/Warning
messages?

What version of OS X are you running???

 

[Anand]

Hi Gerry,

I understand your frustation and also agree with you that its not a very
easy configuration to get rid of this error.
However, I have my Entourage 2004 on Mac OS 10.3.6 connecting to an exchange
server on SSL. It works perfectly fine.
One main thing that you need to keep in mind is that the name in the issued
to field of the certificate should match your excahnge server name that you
enter in Entourage. If this does not match then there is no way you can get
this setup properly.
Tell me if this matches and lets see if I can help you further.

Anand P

 

[Gerry Simmons]

Spot on!! You know, it doesn't. I suspected this might be an issue.

The issue is that the I access Exchange from a VPN - the internal name is
server.local. The certificate is titled SERVER.COM. However, there are
additional names on the certificate under Common names: localhost, server,
companyweb, and server.local, and SERVER.COM.

Neither SERVER.COM nor server.local are public names in DNS. (Do they have
to be??) I had to put entries in my /etc/hosts file for both. SERVER.COM has
a public IP address, and server.local is a private address.

I can try testing this hypothesis by changing the hosts entry for .local to
..COM, but when I change the Exchange Server name, Entourage will re-download
ALL my e-mail. (What a drag!)

Do you think this might clear up the error?

 

[Anand]

Hi Gerry,

As long as you are entering the server name as in the certificate and have
access to the server with that name, I feel it would wok fine.
About downloading all the messages, since it is an exchange client I don't
think you will have any issue...configure a different identity altogether.

Let me know if it works

Anand P