Samba

Ed · 12th September 2008

Hope someone can help because this is driving me bonkers!

When trying to add a machine from the command line or via Windows XP I get the following:

Code:

Could not find base dn, to get next uidNumber at /usr/sbin//smbldap_tools.pm line 1073.
[2008/09/12 14:08:14, 0] passdb/pdb_interface.c:pdb_default_create_user(329)
  _samr_create_user: Running the command `/usr/sbin/smbldap-useradd -w -d /dev/null -c 'Machine Account' -s /bin/false 'edstest$'' gave 3
[2008/09/12 14:08:14, 3] passdb/pdb_interface.c:pdb_default_create_user(354)
  pdb_default_create_user: failed to create a new user structure: NT_STATUS_NO_SUCH_USER

This is my etc/smbldap-tools/smbldap_bind.conf

Code:

############################
# Credential Configuration #
############################
# Notes: you can specify two differents configuration if you use a
# master ldap for writing access and a slave ldap server for reading access
# By default, we will use the same DN (so it will work for standard Samba
# release)
slaveDN="cn=config,dc=mail,dc=domain,dc=co,dc=uk"
slavePw="pass"
masterDN="cn=config,dc=mail,dc=domain,dc=co,dc=uk"
masterPw="pass"

Anyone able to help?

Ed · 16th September 2008

I did sort this

Just incase someone else has this problem with the smbldap tools:

Smbldap-tools User Manual (Release: 0.9.3 )

Quote:

6.13 Typical errors on creating a new user or a new group

i've got the following error:

Could not find base dn, to get next uidNumber at /usr/local/sbin//smbldap_tools.pm line 909

1. you do not have created the object to defined the next uidNumber
and gidNumber available.
* for version 0.8.7 : you can just run the smbldap-populate
script that will update the sambaDomain entry to store those
informations
* for version before 0.8.7 : You have updated the
smbldap-tools to version 0.8.5 or newer. You have to do this
manually. Create an file called add.ldif and containing

dn: cn=NextFreeUnixId,dc=idealx,dc=org
objectClass: inetOrgPerson
objectClass: sambaUnixIdPool
uidNumber: 1000
gidNumber: 1000
cn: NextFreeUnixId
sn: NextFreeUnixId

and then add the object with the ldapadd utility:

$ ldapadd -x -D "cn=Manager,dc=idealx,dc=org" -w secret -f add.ldif

Here, 1000 is the first available value for uidNumber and
gidNumber (of course, if this value is already used by a
user or a group, the first available after 1000 will be used).

2. The error also appear when there is a need for TLS (ldapTLS=1 in
smbldap.conf) and something is wrong with certificate naming or
path settings.