Samba schema and related indices were added and containers created.
Added user xxx to LDAP database via phpLDAPadmin and executed
smbpasswd -a xxx -D 256
Besides the does not exist issues, the attribute sambaDomainName was added.
Are there additional containers and/or attributes
... without sambaGroupMapping aux objects on at least some of your
posixGroups your installation will be of minimal utility - you need the
required groups like Domain Administrators, Power Users, etc... to get
'normal' NT behaviour.
Excellent. This is why I selected phpLDAPadmin; it utilizes
Where I remain unclear is the ldap password sync flag in smb.conf. If set to
yes, does a Windows NT/2K/XP user participating with Samba3 in a workgroup
(security=user) automatically have his or her password transparently
synchronized on the Samba box the next time he or she attempts to
I remain unclear regarding Samba and LDAP.
It appears that mkntpwd is required to generate a viable sambaNTPassword and
sambaLMPassword attribute values. But I believe I read that the current
incarnation of smbpasswd can accomplish this. Lastly, when utilzing
phpLDAPadmin, do the NT and LM
I remain unclear regarding Samba and LDAP.
It appears that mkntpwd is required to generate a viable sambaNTPassword and
sambaLMPassword attribute values.
No.
But I believe I read that the current
incarnation of smbpasswd can accomplish this.
Yes, this is all done via the PDB backend.
Samba schema and related indices were added and containers created.
Added user xxx to LDAP database via phpLDAPadmin and executed
smbpasswd -a xxx -D 256
Besides the does not exist issues, the attribute sambaDomainName was added.
Are there additional containers and/or attributes that I