Delegate access from Entourage problems
From: Jørgen Skårup (admin_at_danskefluefiskere.dk)
Date: 02/08/05
- Next message: Holt: "Annoying "Beep" in Entourage"
- Previous message: tbatst_at_comcast.net: "Re: Double spaces between words"
- Messages sorted by: [ date ] [ thread ]
Date: Tue, 08 Feb 2005 15:20:28 +0100
SYMPTOMS
When you try to configure delegate access to a Microsoft Exchange Server account in Microsoft Entourage 2004 for Mac,
you may receive an error message that is similar to the following:
There was an error communicating with the directory server.
CAUSE
This issue may occur if the Exchange account is not configured correctly with the name
of the Lightweight Directory Access Protocol (LDAP) server.
RESOLUTION
Specify the name of your LDAP server in Entourage,
-----------------------------------------------------
We have these settings
LDAP server: dc1.asb.local
Search base: dc=asb,dc=local
"This server requires me to log on "
LDAP port 389
---------------------------------------------------
These setting works fine for making LDAP request in our LDAP server for making "check names" requests
BUT THE PESKY ERROR
"There was an error communicating with the directory server."
COMES WHEN WE ARE TRYING TO GRANT DELEGATE ACCESS.
There are no problem to get delegate access to the same account from at PC using Outlook.
Here comes an print from ETHER-PEAK
130.226.201.158 = Client
130.226.200.39 = LDAP server
---------------------------------------------------------------------------
130.226.201.158 130.226.200.39 LDAP MsgId=1 Bind Request. DN=(null)
130.226.200.39 130.226.201.158 LDAP MsgId=1 Bind Result. SASL bind in progress
130.226.201.158 130.226.200.39 LDAP MsgId=2 Bind Request, DN=(null)
130.226.200.39 130.226.201.158 LDAP MsgId=2 Bind Result.
130.226.201.158 130.226.200.39 LDAP MsgId=3 Search Request. Base DN=dc=asb,dc=local
130.226.200.39 130.226.201.158 LDAP MsgId=3 Search Entry. 1 result
130.226.201.158 130.226.200.39 LDAP MsgId=4 Unbind Request
This is a LDAP REQUEST from the "check names" function, Which works fine
--------------------------------------------------------------
--------------------------------------------------------------
130.226.201.158 130.226.200.39 LDAP MsgId=1 Search Request. Base DN=(null)
130.226.200.39 130.226.201.158 LDAP MsgId=1 Search Entry, 1 result
130.226.201.158 130.226.200.39 LDAP MsgId=2 Bind Request, DN=(null)
130.226.200.39 130.226.201.158 LDAP MsgId=2 Bind Result. SASL bind in progress
130.226.201.158 130.226.200.39 LDAP MsgId=3 Bind Request, DN=(null)
130.226.200.39 130.226.201.158 LDAP MsgId=3 Bind Result.
130.226.201.158 130.226.200.39 LDAP MsgId=4 Search Request. Base DN=(null)
130.226.200.39 130.226.201.158 LDAP MsgId=4 Search Result, No such object
This is a LDAP REQUEST from the "add delegate" function, Which gives the error
"There was an error communicating with the directory server."
--------------------------------------------------------------
It looks like it is not giving DN information to the LDAP server. ( Base DN= null instead of Base DN=dc=asb,dc=local )
Please Help
- Next message: Holt: "Annoying "Beep" in Entourage"
- Previous message: tbatst_at_comcast.net: "Re: Double spaces between words"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
