LDAP Server Error (-3248) and Slowness

[Larry]

I have two identical 1.67 Ghz. PowerBooks w/1.5 GB of RAM running Mac
OS 10.4.1. On both machines, when trying to access our company's global
address list (check name) this error message comes up:

An unknown error (-3248) occured.
LDAP Server Error

Both users are unable to access the GAL. Additionally, one of the users
reports extreme slowness (beachballing) and repeated timeouts requiring
him to login many times a day. I have excluded both users' Microsoft
User Data folders from Spotlight indexing, but have had no luck yet.

Any ideas? This has to be resolved soon or we will be forced to use
Outlook in Classic.

Thanks in advance,
Larry

 

[Corentin Cras-Méneur]

I have two identical 1.67 Ghz. PowerBooks w/1.5 GB of RAM running Mac
OS 10.4.1. On both machines, when trying to access our company's global
address list (check name) this error message comes up:

An unknown error (-3248) occured.
LDAP Server Error

Can you access the server from the System address book (if you set it up
properly there)??

Corentin

 

[Nathan Herring [MSFT]]

I have two identical 1.67 Ghz. PowerBooks w/1.5 GB of RAM running Mac
OS 10.4.1. On both machines, when trying to access our company's global
address list (check name) this error message comes up:

An unknown error (-3248) occured.
LDAP Server Error

Both users are unable to access the GAL. Additionally, one of the users
reports extreme slowness (beachballing) and repeated timeouts requiring
him to login many times a day. I have excluded both users' Microsoft
User Data folders from Spotlight indexing, but have had no luck yet.

Any ideas? This has to be resolved soon or we will be forced to use
Outlook in Classic.

Thanks in advance,
Larry

This error is kEADDRNOTAVAILErr, which is just a mapping from the Unix error
EADDRNOTAVAIL (Cannot assign requested address). Do you have more than one
IP addresses assigned to your machine? Are you setting a manual IP address
in or DHCP or? This error relates to a program trying to open a network
connection with the from-IP-address being one that has doesn't exist on the
local machine. Usually, there's only one IP address and we'd choose it, so
this is an odd error, especially if you're only getting it for one type of
network connection (in this case LDAP).

-nh