[Fedora-directory-users] Samba PDC using FDS backend

[Brian Rudy]

Hi Folks,

I had a crack at setting up a Samba PDC using a fresh installation of 
FDS 1.0.1 as the backend on one of our RHEL 3 servers per the Wiki 
Howto:Samba but ran into a few issues.

In the section 'Populating FDS with PDC Entry', it instructs the user to 
run 'net getlocalsid'. This results in the following:

[root at mybox logs]# net getlocalsid
[2006/01/03 14:32:58, 0] lib/smbldap.c:smbldap_search_domain_info(1392)
  Adding domain info for CMOMA failed with NT_STATUS_UNSUCCESSFUL
SID for domain mybox is: S-1-5-21-4207250186-2406131440-3849861866

Thinking that I might just have a Samba configuration problem, I 
continued by attempting to add the following ldif:

dn: sambaDomainName=CMOMA,dc=cmoma,dc=mycompany,dc=com
objectclass: sambaDomain
objectclass: sambaUnixIDPool
objectclass: top
sambaDomainName: CMOMA
sambaSID: S-1-5-21-4207250186-2406131440-3849861866
uidNumber: 550
gidNumber: 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 be happening here?