Exchange + Entourage

G

Guest

Hello, NG!
Could anybody point me to a configuration guide for Exchange 2003 and
Entourage clients. Please understand that I do not need a client-side
configuration guide, but a server-side one, regarding LDAP, WebDAV, ISA
configuration and so on... The server is part of an SBS installation.

Thanks in advance.






Pax
 
B

Boris Lokhvitsky

I have experience configuring Entourage with Exchange 2003 SP1 front-end /
back-end topology. It does NOT require any special server configuration,
only the client-side one.

Regards,
Boris
 
G

Guest

Thanks, Boris. I guess I didn't came with enough details.
I'd like the Exchange server to be accessible over the Internet, the Mac
client is in US and the server is in Europe. There is an ISA Server between
them, on the same machine as the Exchange server.
In IIS Admin I can see that the WebDAV Web Service Extension is prohibited
by default. There are certain places where I read that if OWA works then
Entourage should work also. OK, OWA works just fine. Is the WebDAV Web
Service Extension required or not? Should I allow LDAP traffic on 3268 to
get through ISA?

Thanks.





Pax
 
H

Helpdesk

How do you setup the entourage with exchange 2003? when I goto setup the
exchange account in entourage it is asking for a root certificate. any
ideas?

thanks,

Marc
 
B

Boris Lokhvitsky

So, install a certificate or do not require message encryption / digital
ID... I don't get the problem.
 
B

Boris Lokhvitsky

Well, ISA and other firewalls may indeed contribute to the problem.
Depending on your Exchange design and on the client configuration, you may
require different ports to be opened on the firewall. LDAP to 3268 is
normally required for RPC based MAPI sessions with no front-end involved.

On all of my Windows 2003 based Exchange servers, WebDAV service extensions
is allowed, and I believe this is the default setting if you install this
component at all. And yes I believe if OWA works fine then Entourage should
work, too. There might be issues indeed, we had some, but it all depends on
the specifics of the environment which you didn't describe (say, in our case
Entourage couldn't connect for some clients because it was trying to create
named properties on the information store where the quota was exceeded, and
it was not that easy to troubleshoot).

In any case, for Exchange to be accessible for Internet clients, the only
acceptable ways are OWA or RPC over HTTPS, standard MAPI connection is a
huge security breach. Just my $0.02.

Regards,
Boris
 
G

Guest

Thank you, Boris. I'll dig further. I've read that the 3268 port is needed
for lookups against the Global Catalog. Is it (this lookup) an optional
feature or is it a mandatory one for a normally functioning Entourage?
The WebDAV situation is still foggy; it is disabled but OWA works fine and
also OL2003 with RPC over HTTP.
But the main problem remains the LDAP related 3268 port. Really, I wouldn't
like to open it as I don't know what kind of dialog is going on there.

Thanks.




Pax
 
T

Thomas Polk

Thank you, Boris. I'll dig further. I've read that the 3268 port is needed
for lookups against the Global Catalog. Is it (this lookup) an optional
feature or is it a mandatory one for a normally functioning Entourage?
The WebDAV situation is still foggy; it is disabled but OWA works fine and
also OL2003 with RPC over HTTP.
But the main problem remains the LDAP related 3268 port. Really, I wouldn't
like to open it as I don't know what kind of dialog is going on there.

Thanks.




Pax
Click to expand...
 
Top