search for: 61samba

...dNumber: 550 which resulted in the following error: adding new entry sambaDomainName=CMOMA,dc=cmoma,dc=mycompany,dc=com ldap_add: Object class violation ldap_add: additional info: unknown object class "sambaUnixIDPool" I double checked /opt/fedora-ds/slapd-<server>/config/schema/61samba.ldif created in the initial setup steps and was unable to find a sambaUnixIDPool objectclass, but did see a sambaUnixIdPool. However, after I edited /tmp/sambaDomainName.ldif to reflect this objectclass name, ldif2ldap still complains about an 'unknown object class'. Any idea of what might...

...hat I would like to use LDAP credentials to authenticate with. Found guides for using LDAP credentials with SAMBA here: http://directory.fedoraproject.org/wiki/Howto:Samba http://sangacollins.wordpress.com/posts/directory-server/ What I have been able to do: Added the samba schema information (61samba.ldif) into my 389 directory server. Used the configure.pl script to configure smbldap-tools for my 389 Directory server. Ran smbldap-populate to add the basic Windows user setup for SAMBA. Issues: It seems that all of the SAMBA/LDAP guides expect SAMBA and LDAP to be on the same server. Don&...

...in server was successfully created, configured, and started. >>Exiting . . . >>Log file is '/tmp/setupOYDg5L.log' >> >> <<screen dump>> ===================================================================== 3. Import samba.schema into FDS 3.1 Copy file 61samba.ldif to /etc/dirsrv/schema and /etc/dirsrv/slapd-centserver/schema 3.2 service dirsrv restart ===================================================================== 4. Modify file migrate_common.ph /usr/share/openldap/migration/migrate_common.ph 4.1 Search for the following OrganizationalUnit :...