Server Side Issues

• Front End server issues
• Account Auto setup won't work
• GAL will not work unless the Active Directory (AD) Global Catalog (GC) is exposed
• Free Busy public folders need to be replicated to front end
• If mail folders are displayed in OWA or Outlook, but not in Entourage, you may be running into an Exchange server limitation. Make sure that you have the latest Exchange server patches (at least SP1 for Exchange 2003, or this patch for Exchange 2000: KB 840546, http://bugcheck/default.asp?URL=/bugs/Exchange/241983.asp) and server packs, then use OWA or Outlook to rename the offending folders, and then rename them back.
• Ports: Entourage uses HTTP for syncing mail, public folders, contacts and events. That is port 80, or port 443 if you are using SSL. Entourage sends LDAP queries to the Active Directory (AD) Global Catalog (GC) to get GAL data (and to get account info during account auto-setup), and we use port 3268 for that. If for some reason your Exchange deployment uses different ports for the above protocols, then you can change them in Entourage as well. Entourage also uses UDP to get notifications of new mail, port varies between 49152 and 65535 (no major loss of functionality if this one isn't available). Lastly, entourage issues DNS queries to Domain Controller to find the GC when trying to auto-configure an account, this uses port 53 (if this doesn't work then you can still configure the account manually in Entourage).
• If you are seeing unexplained failure to sync messages in the Entourage error log, your Exchange server may have blocked certain DAV verbs that Entourage needs. Read this KB article, or send it to your Exchange admin: http://support.microsoft.com/default.aspx?scid=kb;en-us;823175
• The server may modify the HTML parts of messages sent from Entourage or add HTML parts to plain-text messages sent to DLs
• Getting too many reminders? Make sure the calendar preference "tentatively accept invites" is off (it is by default when you create an Exchange account)