Re: Exchange + Entourage

Tech-Archive recommends: Fix windows errors by optimizing your registry

From: Boris Lokhvitsky (msexpert_at_community.nospam)
Date: 01/28/05 

Date: Fri, 28 Jan 2005 14:21:41 -0800

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

<pax> wrote in message news:ulhzsPHBFHA.2076@TK2MSFTNGP15.phx.gbl...
> 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
>
>
> "Boris Lokhvitsky" <msexpert@community.nospam> wrote in message
> news:uiQn96nAFHA.3120@TK2MSFTNGP12.phx.gbl...
> > 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
> >
> >
> > <pax> wrote in message news:uoEUB4fAFHA.2712@TK2MSFTNGP15.phx.gbl...
> > >
> > > 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
> > >
> > >
> >
> >
>
>

Relevant Pages

  • RE: Outlook trying to connect.......
    ... does outlook client connect to exchange server ...
    (microsoft.public.windows.server.sbs)
  • Re: Client was exchange calendaring only, sbs2k, small setup. Disable Exchange?
    ... client is using Outlook or OE to retrieve mail directly from external POP ... > is to run it as if you were going to use Exchange with the POP connector. ... > First of all, that configuration shouldn't expose you to any risks in ISA, ... >>internal emails. ...
    (microsoft.public.backoffice.smallbiz2000)
  • Re: Exchange + Entourage
    ... ISA and other firewalls may indeed contribute to the problem. ... Depending on your Exchange design and on the client configuration, ... On all of my Windows 2003 based Exchange servers, ... > I'd like the Exchange server to be accessible over the Internet, ...
    (microsoft.public.exchange.connectivity)
  • Re: Exchange + Entourage
    ... ISA and other firewalls may indeed contribute to the problem. ... Depending on your Exchange design and on the client configuration, ... On all of my Windows 2003 based Exchange servers, ... > I'd like the Exchange server to be accessible over the Internet, ...
    (microsoft.public.exchange.admin)
  • Re: Exchange + Entourage
    ... ISA and other firewalls may indeed contribute to the problem. ... Depending on your Exchange design and on the client configuration, ... On all of my Windows 2003 based Exchange servers, ... > I'd like the Exchange server to be accessible over the Internet, ...
    (microsoft.public.exchange.clients)