Re: netscape & unknown protocol error 0x02

[Mark Smith <mcs@netscape.com>]

"Wim.Holemans" wrote:
> 
> We were experimenting with referall's and we noticed something strange :
> if we referred to certain servers in our openldap server and we used
> netscape as ldap client, we couldn't access our own ldapserver anymore
> after having been referred. We always get an unknown protocol 0x02 error.
> For an unknown reason the netscape client changed the way it makes the
> request and the openldap server doesn't recognize the request anymore.

Error 2 is "protocol error."  I suspect that Netscape
Communicator/Navigator is trying to use LDAPv3 and not falling back to
LDAPv2 correctly.  But I am not sure since I don't work on Communicator.


> 
> We already found out that it has something to do with something called
> 'dvd' a ldapv3 feature ??
> Putting the line
> user_pref("ldap_2.servers.ua_1.vlvDisabled", true);
> in the prefs.js file solves this.

VLV is "virtual list view" and is an LDAPv3 extension that not all
servers will support.    I suspect that the vlvDisabled preference
changes Communicator's behavior so it does not use LDAPv3... just a
guess.

-- 
Mark Smith
Directory Architect / Sun-Netscape Alliance
My words are my own, not my employer's.  Got LDAP?