[Samba] Samba 3B3 with LDAP

[William234 at aol.com]

Hello,

I am using OpenLDAP 2.1.22.  To the best of my understanding, my server is 
not set up as a replica.  I don't know if there is a relevant section in 
slapd.conf that you'd like to look at as most of it is just telling slapd where the 
database goes, what the indexes should be and the basic configuration of the 
schema's.

Bill Miller
William234 at aol.com

In a message dated 7/22/2003 12:14:39 PM Pacific Daylight Time, 
smoorhouse at ae-solutions.com writes:

> Are you attempting to update the password on an LDAP server that's a
> replica?  A replica server will not be willing to update its database
> directly for you (unwilling to perform) but will rather provide you an
> referral to its master server where the update should be performed.  If
> the replica server is set up improperly, it won't provide the valid URL
> for the update referral.
> 
> Check the 'updateref' in slapd.conf on the ldap server you're using
> (since it seems you are running some version of OpenLDAP).
> 
> On Tue, 2003-07-22 at 14:00, William234 at aol.com wrote:
> >Hello,
> >
> >I have compiled Samba 3.0 Beta 3 and am attempting to get it to work with 
> >LDAPSAM.
> >
> >Whenever I run smbpasswd or pdbedit, I get the following output.
> >
> >    sparc10:/etc/openldap# /usr/local/samba/bin/smbpasswd -a bill
> >    New SMB password:
> >    Retype new SMB password:
> >    failed to add user dn= uid=bill,ou=People with: Server is unwilling to 
> >perform
> >         referral missing
> >    failed to modify/add user with uid = bill (dn = uid=bill,ou=People)
> >    Failed to add entry for user bill.
> >    Failed to modify password entry for user bill
> >
> >To try to figure out what is causing this problem I have grep'd through the 
> 
> >source code looking for the error messages above, searched deja.com, and 
> looked 
> >through the archives of this list.  I cannot find anything anywhere that 
> >makes a reference to "referral missing" and as such have no idea where to 
> go to 
> >debug the problem.
>