You now need to extend the Directory Server schema with the Samba subschema from the HP CIFS Server into your Directory Server. Ensure that you have configured your LDAP directory and LDAP-UX Client Services before extending the schema.
Set the passwd backend parameter to ldapsam:ldap://<ldap server name>.
Samba Subschema Differences Between HP CIFS Server Versions |
 |
New HP CIFS Server releases sometimes extend the attributes for use but update are backwards compatible with older versions of LDAP schemas.
Procedures to Extend the Samba Subschema into Your Directory |
|
Use the following steps to extend the Samba subschema /opt/samba/LDAP3/98samba3.ldif in HP CIFS Server A.02.* into the Directory Server:
Run the ftp commands to get the /opt/samba/LDAP3/98samba3.ldif file from the HP CIFS Server and place it in the Directory Server:
For example, the following commands copy /opt/samba/LDAP3/98samba3.ldif file from the HP CIFS Server to the /var/opt/netscape/servers/sldapd-hostA.hp.com/config/schema/98samba3.ldif file in the Directory Server, hostA.hp.com:
cd /opt/samba/LDAP3
ftp hostA.org.hp.com
user root
root passwd
cd /var/opt/netscape/servers/sldapd-hostA.hp.com/config/schema
put 98samba3.ldif
quit
|
Login to your Directory Server and restart the daemon, slapd. This is to ensure that the sambaSamAccount subschema is recognized by the LDAP directory.
$ /var/opt/netscape/servers/slapd-<server name>/restart-slapd |
For example:
$ /var/opt/netscape/servers/slapd-hostA.hp.com/restart-slapd |
Use the following ldapsearch command to verify that you have updated the schema in the Directory Server with the Samba subschema:
$ /opt/ldapux/bin/ldapsearch -T -b "cn=schema" -s base \
"(objectclass=*)"|grep -i samb |
You need to ensure that the output displays the following sambaSamAccount objectclass when you run the ldapsearch command:
objectClasses: ( 1.3.6.1.4.1.7165.2.2.6 NAME 'sambaSamAccount'
DESC 'Samba 3.0 Auxilary SAM Account' STRUCTURAL MUST ( uid $ sambaSID )
Printable version
