Ldap error with Entourage 2004

[Jay Westendorf]

Hello all.

I currently maintain some MAC os x 10.3.3 clients that are trying to use the
Entourage 2004 that recently came out. I have everything set up except
accessing the GAL properly with LDAP. I receive the following error when
trying to do a check names (the current LDAP is pointing to our Exchange
Server 2000 SP3 on a Windows 2000 Server SP4).

Error ----
The connection to the server failed because the network is unavailable.
Make sure that your computer is connected to the network and that your
server is working correctly. If you need help, contact your network
administrator.

Explanation ---
LDAP Server Error.
Account name: "name of account"
Error -3260

----

If I change the LDAP server to one of our Windows 2000 Domain Controllers, I
get almost the same error but get back numbers -17768 or -3170 depending on
if I select secure LDAP or basic authentication (port 389).

Any ideas on this issue?

Sincerely,

James Westendorf
Network Administrator
Nova Solutions, Inc.
(e-mail address removed)

 

[Corentin Cras-Méneur [MVP]]

Hi Jay,

Error ----
The connection to the server failed because the network is unavailable.
Make sure that your computer is connected to the network and that your
server is working correctly. If you need help, contact your network
administrator.

Are you sure you specified the proper port of rhte LDAP server ???


Corentin

 

[csanford]

I'm getting the same error. Do we need to specify the port number as part
of the LDAP server address? Since I'm not certain of the port number, I
checked the box that read: "Override default LDAP port" in the Advanced
Settings within the Directory tab.

 

[csanford]

I had been struggling with Entourage and LDAP after being told by an
Exchange admin that the LDAP server was part of the Exchange server; so
the
two would have the same address. I was later told by a different (more
knowledgeable) Exchange admin that, unlike Exchange Server 5.5, the LDAP
server on an Exchange 2003 server has a separate address. Once I put that

address into the LDAP field in Tools/Accounts/(email account)/Directory, I

was getting a blank Global Address List form that was not populated with
addresses. I tried putting in the port number at the end of the LDAP
address, but that didn't work either.
What finally worked was selecting an overlooked checkbox (I think it was
deselected by default). If you look below the "Search Base" field, there
is
a button that reads, "Click here for advanced options". The checkbox in
question reads, "The server requires me to log on". Once I selected that

box, I was able to populate the both the "to" field and the Directory
Services with the Global Address List of company email accounts.

 

[Corentin Cras-Méneur [MVP]]

I'm getting the same error. Do we need to specify the port number as
part of the LDAP server address? Since I'm not certain of the port
number, I checked the box that read: "Override default LDAP port" in the
Advanced Settings within the Directory tab.

I'm using a custom port here and using the "override" option worked just
fine. I don;t think it's the case.

I know that in order to properly access LDAP I've had to play for a
while with the Directory Access app (in /Applications/Utilities) though.

The problem with LDAP is that the setup can be really different from one
site to another :-\


Corentin

 

[Corentin Cras-Méneur [MVP]]

I had been struggling with Entourage and LDAP after being told by an
Exchange admin that the LDAP server was part of the Exchange server; so
the two would have the same address. I was later told by a different
(more knowledgeable) Exchange admin that, unlike Exchange Server 5.5,
the LDAP server on an Exchange 2003 server has a separate address.

It sure isn't always the same address all the time (it isn't for me). I
*can* be though.

Once I put that
address into the LDAP field in Tools/Accounts/(email account)/Directory,
I was getting a blank Global Address List form that was not populated with
addresses.

It never is. You can only query the LDAP (as opposed to accessing the
GAL on Windows).

I tried putting in the port number at the end of the LDAP
address, but that didn't work either. What finally worked was selecting
an overlooked checkbox (I think it was deselected by default). If you
look below the "Search Base" field, there is a button that reads, "Click
here for advanced options". The checkbox in question reads, "The server
requires me to log on". Once I selected that
box, I was able to populate the both the "to" field and the Directory
Services with the Global Address List of company email accounts.

I see what you mean by populated now... The LDAP servers very often
require you to authentify and many also use custom ports.


Corentin

 

[csanford]

I had been struggling with Entourage and LDAP after being told by an
Exchange admin that the LDAP server was part of the Exchange server; so
the
two would have the same address. I was later told by a different (more
knowledgeable) Exchange admin that, unlike Exchange Server 5.5, the LDAP
server on an Exchange 2003 server has a separate address. Once I put that

address into the LDAP field in Tools/Accounts/(email account)/Directory, I

was getting a blank Global Address List form that was not populated with
addresses. I tried putting in the port number at the end of the LDAP
address, but that didn't work either.
What finally worked was selecting an overlooked checkbox (I think it was
deselected by default). If you look below the "Search Base" field, there
is
a button that reads, "Click here for advanced options". The checkbox in
question reads, "The server requires me to log on". Once I selected that

box, I was able to populate the both the "to" field and the Directory
Services with the Global Address List of company email accounts.