[Date Prev][Date Next]
[Chronological]
[Thread]
[Top]
Re: OpenLDAP 1.1.4 and Netscape Address Book
I had this same problem. Netscape has 'tweaked' its addressbook
and you need to remove those tweaks to work well with Openldap.
Especially the use 'efficient wildcards' option.
Edit your ...path to netscape\Users\default\prefs.js file. Remember
to be out of Netscape when you edit this file, as Netscape recreates
it everytime it closes.
See: http://developer.netscape.com/docs/manuals/communicator/ldap45.htm
Basically, I used the configuration below.
user_pref("ldap_2.servers.DHL.position", 0);
user_pref("ldap_2.servers.DHLLDAP.auth.enabled", false);
user_pref("ldap_2.servers.DHLLDAP.auth.savePassword", false);
user_pref("ldap_2.servers.DHLLDAP.autoComplete.enabled", true);
user_pref("ldap_2.servers.DHLLDAP.autoComplete.filter", "cn=%1 %2");
user_pref("ldap_2.servers.DHLLDAP.csid", "UTF-8");
user_pref("ldap_2.servers.DHLLDAP.description", "DHL LDAP");
user_pref("ldap_2.servers.DHLLDAP.efficientWildcards", false);
user_pref("ldap_2.servers.DHLLDAP.filename", "DHLLDAP.na2");
user_pref("ldap_2.servers.DHLLDAP.filter1.repeatFilterForWords", true);
user_pref("ldap_2.servers.DHLLDAP.filter1.string", "(|(cn=%s)(sn=%s))");
user_pref("ldap_2.servers.DHLLDAP.position", 1);
user_pref("ldap_2.servers.DHLLDAP.replication.enabled", false);
user_pref("ldap_2.servers.DHLLDAP.replication.lastChangeNumber", 0);
user_pref("ldap_2.servers.DHLLDAP.searchBase", "dc=DHL Airways, dc=com");
user_pref("ldap_2.servers.DHLLDAP.serverName", "nowhere");
user_pref("ldap_2.servers.DHLLDAP.vlvDisabled", true);
-Dale
Chris Zimmerman wrote:
>
> Has anyone had a problem with the two items I have mentioned in the
> subject? To be more specific, we are running openldap only for a
> company-wide address book. The clients are running Netscape 4.5, and
> everything works properly-most of the time. Occasionally, we get
> timeouts (actually, they are just long pauses) before the Address Book
> in Netscape will allow any queries. Netscape shows in the window
> 'Connecting to [name of list]', then the long pause (sometimes as long
> as 2-3 minutes), then the queries work fine. This is not isolated to
> one client, as all clients exhibit the same behavior when this
> phenomenon occurs. There are only 90 entries on the LDAP database, and
> only 10-15 max number of clients connect concurrently. I had thought I
> was overloading the slapd server by configuring the Netscape mail
> clients to 'Check names against this server', but again, I have had no
> problems 95% of the time. Unfortunately, everyone only remembers the 5%
> problem times....
>
> The box that is running slapd is also running sendmail, qpopper, and
> DNS. Running netstat during one of these "outages" shows only a few
> concurrent connections-nothing extraordinary.
>
> Any help would be appreciated....
>
> Chris Zimmerman