HP ProLiant DL380G5-WSS 3.7.0 HP StorageWorks HP Scalable NAS File Serving Sof - Page 414

and groups. These ranges are configurable. There are several winbind models as well. The default and most common involves assigning uids and gids in the order they are read from the domain. Another common model uses the RID portion of the Windows SID along with a formula to determine the uid or gid values. Permissions to Linux resources are granted through the group memberships defined in ADS using the IDs assigned through winbind. Winbind users cannot be mixed with Linux users in common groups. Winbind users and groups can be mapped to native Linux uids; however, there are some issues with doing this. See the Samba Official HOWTO on the www.samba.org website for more details and limitations. Configure the Samba solution with ADS Each cluster node running Samba needs to be joined to the domain individually using the hostname. The computer account should be kept on a non-shared path. Several Samba parameters will need to be changed to allow Samba to be joined to the domain. It is best to get the Samba deployment pack installed and working before changing the Samba configuration so it can be joined to the domain. The following parameters need to be changed before Samba can be joined to a domain. Changes for domain level security Set these parameters: • Workgroup = [short Domain Name] • security = domain • password server = [IPs of DCs of domain] See the Samba Official HOWTO for more information about using net rpc join to join Samba to a domain using domain level security. NOTE: As an example of a short domain name, if the domain is "nevada.usa.com", the short domain name is "nevada". Use net rpc testjoin to test the join after the join has completed successfully. 414 Samba configuration