How To Install Samba On Solaris 10

Installing and Configuring Samba

This department contains the procedures y'all need to install and configure Samba.

How to Install and Configure Samba

This section contains the procedures you need to install and configure Samba.

Determine how many Samba instances will exist used.
Refer to Brake for multiple Samba instances that require winbind for more data.
Decide which Solaris zone to apply.
Refer to Decide which Solaris Zone Samba volition run use for more information.
If a zone will exist used, create the non-global zone or HA container.
Refer to Arrangement Assistants Guide: Oracle Solaris Containers-Resource Management and Oracle Solaris Zones for complete information well-nigh installing and configuring a Solaris Container.

Refer to Oracle Solaris Cluster Information Service for Solaris Containers Guide for complete data well-nigh creating an HA container.
Create a cluster file system or highly bachelor local file system for the Samba files.
Refer to Restriction for the Location of Samba files for more information.

Refer to Oracle Solaris Cluster Data Services Planning and Administration Guide for more than information about creating a cluster file system or highly available local file system.

Annotation - Y'all may as well want to consider allocating additional space if yous install Samba from http://www.samba.org.
Install Samba onto a cluster file system or highly available local file system.

Note - Sunday provides support for Samba that is packaged with Solaris nine or 10, but does non offer support for Samba that has been downloaded and compiled from http://world wide web.samba.org.
- Check Samba is installed on Solaris nine or x.
  Refer to How to Check Samba is installed with Solaris 9 or 10 for more information.
- Download and compile Samba from http://www.samba.org.
  Refer to How to Install and Configure Samba downloaded from http://www.samba.org for more information.

How to Check Samba is installed with Solaris 9 or ten

Samba is already installed and configured with Solaris 9 or 10 and included in the following packages SUNWsmbac, SUNWsmbar, SUNWsmbau, and SUNWsfman. Refer to the Freeware Features within the book Solaris ten What'due south New to check if new features have been added to Samba packaged with Solaris 10.

Check the packet data to verify that Samba is installed on every node.

#              for i in SUNWsmbac SUNWsmbar SUNWsmbau SUNWsfman              >              do              >              pkginfo $i              >              washed              system      SUNWsmbac samba - A Windows SMB/CIFS fileserver for UNIX (client) organization      SUNWsmbar samba - A Windows SMB/CIFS fileserver for UNIX (Root) system      SUNWsmbau samba - A Windows SMB/CIFS fileserver for UNIX (Usr) organisation      SUNWsfman GNU and open up source man pages

Check what Samba version is installed on every node.

#              pkginfo -l SUNWsmbac              PKGINST:  SUNWsmbac       Proper noun:  samba - A Windows SMB/CIFS fileserver for UNIX (client)   CATEGORY:  system       ARCH:  i386    VERSION:  11.10.0,REV=2005.01.08.01.09    BASEDIR:  /     VENDOR:  Sunday Microsystems, Inc.       DESC:  samba - A Windows SMB/CIFS fileserver for UNIX (customer) 3.0.xi     PSTAMP:  sfw10-patch-x20050420163529   INSTDATE:  October 03 2005 09:23    HOTLINE:  Please contact your local service provider     Condition:  completely installed      FILES:       13 installed pathnames                    three shared pathnames                    3 directories                   ten executables                10937 blocks used (approx)

Next Steps

See How to Prepare Samba for HA for Samba.

How to Install and Configure Samba downloaded from http://www.samba.org

If a newer version of Samba is required y'all can download and compile Samba from http://www.samba.org.

(Optional) Mountain the highly available local file arrangement.
It is recommended that yous download and install Samba onto a cluster file organization or highly available local file system. Doing so will allow you lot to have Samba installed in one location. Yous will also exist able to mount the file system in Solaris zones.

If multiple Samba instances will exist deployed yous should use a cluster file system for the Samba binaries and either a cluster file system or highly available local file system for the Samba files.

Refer to Instance 1-2 in Restriction for the Samba smb.conf files for an instance of download and compiling Samba onto a cluster file system and using a highly bachelor local file system for the Samba files for each Samba instance.

Alternatively, yous can download and compile Samba onto local file system for each Solaris zone.

Note - If a cluster file system is being used, the file system should already be mounted at boot as a global file organisation.
```
#              mount              samba-highly-bachelor-local-file-organisation            
```

Download and compile Samba from http://www.samba.org.

Hither Kerberos, OpenLDAP, and Samba will be downloaded and compiled.

Samba will employ the idmap_rid facility to map a single ADS domain SIDs to Solaris UIDs and GIDs. Y'all should determine what idmap is suitable for your installation.

Within this example the samba-highly-available-local-file-system is /local/samba, where the software is installed into /local/samba/software and compiled into /opt/samba.

For more data using these filenames refer to the following deployment example in Appendix B, Deployment Example: Installing Samba from http://www.samba.org where these commands have been has been taken.

Download, Extract and Install Kerberos.

Vigor5#                  cd /local/samba/software                  Vigor5#                  wget http://spider web.mit.edu/kerberos/dist/krb5/1.four/krb5-one.4.3-signed.tar                  Vigor5#                  tar -xfBp krb5*tar                  Vigor5#                  gunzip -c krb5*.tar.gz | tar -xfBp -                  Vigor5#                  rm krb5*tar*                  Vigor5#                  cd krb5*/src                  Vigor5#                  CC=/opt/SUNWspro/bin/cc ./configure --prefix=/opt/samba \                  >                  --enable-dns-for-realm                  Vigor5#                  make                  Vigor5#                  brand install

Download, Extract and Install OpenLDAP.

Note - You must obtain a set up for Issues ID: 6419029 which describes a problem when compiling OpenLDAP before proceeding with this footstep.

Vigor5#                  cd /local/samba/software                  Vigor5#                  wget \                  >                  ftp://ftp.openldap.org/pub/OpenLDAP/openldap-release/openldap-2.3.24.tgz                  Vigor5#                  gunzip -c openldap-2.3.24.tgz | tar -xfBp -                  Vigor5#                  rm openldap-2.3.24.tgz                  Vigor5#                  cd openldap*                  Vigor5#                  CC=/opt/SUNWspro/bin/cc \                  >                  CPPFLAGS="-I/opt/samba/include" \                  >                  LDFLAGS="-50/opt/samba/lib -R/opt/samba/lib" ./configure --prefix=/opt/samba \                  >                  --disable-slapd --disable-slurpd                  Vigor5#                  make depend                  Vigor5#                  make                  Vigor5#                  make install

Download, Extract and Install Samba.

Vigor5#                  cd /local/samba/software                  Vigor5#                  wget http://us3.samba.org/samba/ftp/old-versions/samba-three.0.22.tar.gz                  Vigor5#                  gunzip -c samba-3.0.22.tar.gz | tar -xfBp -                  Vigor5#                  rm samba-3.0.22.tar.gz                  Vigor5#                  cd samba*/source                  Vigor5#                  CC=/opt/SUNWspro/bin/cc \                  >                  CFLAGS=-I/opt/samba/include \                  >                  LDFLAGS="-L/opt/samba/lib -R/opt/samba/lib" ./configure --prefix=/opt/samba \                  >                  --with-ads --with-krb5=/opt/samba --with-shared-modules=idmap_rid                  Vigor5#                  make                  Vigor5#                  make install

Copy winbind libnss_winbind.so to /usr/lib.

#              cd /local/samba/software/samba*/source              # #              cp nsswitch/libnss_winbind.so /usr/lib              #              ln -southward /usr/lib/libnss_winbind.so /usr/lib/libnss_winbind.and so.ane              #              ln -s /usr/lib/libnss_winbind.so /usr/lib/nss_winbind.and so.1

Adjacent Steps

Come across How to Prepare Samba for HA for Samba.

How to Fix Samba for HA for Samba

This section contains the steps to prepare Samba for utilise with the HA for Samba information service.

Some steps crave that you use Samba commands, refer to the Docs and Books section with http://www.samba.org for the relevant man pages for more information of these Samba commands.

Perform this procedure on one node of the cluster, unless a specific stride indicates otherwise.

If a not-global zone or HA container is being used, ensure the zone is booted.

Repeat this step on all nodes on the cluster.

#              zoneadm list -v

Boot the zone if information technology is not running.

#              zoneadm -z              zonename              kick

Create the fault monitor user.

If winbind is being used.
Create the fault monitor user on the NT PDC or ADS server with no home directory, no user profile and no logon script. Gear up the Countersign never elapse parameter to true and User cannot alter password parameter to true.

If winbind is non existence used.

Echo this step on all nodes or zones on the cluster.

If the global zone is being used for Samba.

#                      groupadd -k 1000                      samba-fault-monitor-group                      #                      useradd -u 1000 -g 1000 -s /bin/false                      samba-fault-monitor-user

If a non-global zone or HA container is existence used for Samba.

Create the error monitor user in the zone.

#                      zlogin                      zonename                      groupadd -g 1000                      samba-fault-monitor-group                      #                      zlogin                      zonename                      useradd -u 1000 -1000 1000 -due south /bin/false                      samba-error-monitor-user

Annotation - A local Samba fmuser also requires a local password. The settings in the smb.conf specify which password will be used.

If winbind is used, add together winbind as a name service on all nodes with Oracle Solaris Cluster.
Repeat this step on all nodes or zones on the cluster.

Edit /etc/nsswitch.conf in the zones being used for Samba and add winbind to the passwd: and group: entries, for example:
```
#              grep winbind /etc/nsswitch.conf              passwd:     files winbind group:      files winbind
```

If winbind is used, disable the Name Service Cache Daemon on all nodes with Oracle Solaris Cluster.

Echo this step on all nodes or zones on the cluster.

If running Solaris 9

#                  /etc/init.d/nscd finish

If running Solaris 10

If the global zone is being used for Samba.

#                      svcadm disable proper name-service-cache

If a non-global zone or HA container is being used for Samba.

#                      zlogin                      zonename                      svcadm disable name-service-cache

Create a cluster file system or highly available local file system.
Perform this stride on all nodes of the cluster.

You must create a cluster file system or highly bachelor local file system for some Samba files. Refer to Restriction for the Location of Samba files for more than information on what is meant by Samba files.

Refer to Oracle Solaris Cluster Data Services Planning and Administration Guide for more information about how to create a cluster file system or highly available local file system.

Mount the cluster file system or highly available local file arrangement.

Perform this step on one node of the cluster.

If the global zone is being used for Samba.

#                  mount                  samba-highly-available-local-file-system

If a not-global zone or HA container is being used for Samba.

Create the mountain point on all zones of the cluster that are being used for Samba.

Mountain the cluster file system or highly available local file system on one of the zones being used past Samba.

#                  zlogin                  zonename                  mkdir                  samba-highly-available-local-file-system                  # #                  mount -F lofs                  samba-highly-available-local-file-system                  \ >                  /                  zonepath                  /root/                  samba-highly-available-local-file-organisation

Create the Samba configuration directory.

Repeat this pace for each Samba or winbind example on i node of the cluster.

Create the Samba configuration directory inside the samba-highly-available-local-file-system.

#              mkdir -p              samba-configuration-directory              #              cd              samba-configuration-directory              #              mkdir -p lib logs private shares var/locks

The following deployment example has been taken from Appendix A, Deployment Example: Installing Samba packaged with Solaris 10 where /local is the highly bachelor local file system and /local/samba/smb1 is the samba-configuration-directory.

Vigor5#              mkdir -p /local/samba/smb1              Vigor5#              cd /local/samba/smb1              Vigor5#              mkdir -p lib logs individual shares var/locks

Create the smb.conf file within the configuration directory.

Repeat this stride for each Samba or winbind instance on 1 node of the cluster.

Create a smb.conf file inside the configuration directory that reflects the example.

Refer to Required parameters for the Samba smb.conf file and the smb.conf[v] human being folio for an explanation of the required parameters.

The following deployment example has been taken from Appendix B, Deployment Instance: Installing Samba from http://www.samba.org.

Vigor5#              cat > /local/samba/smb1/lib/smb.conf <<-EOF [global] workgroup = ADS bind interfaces just = yes interfaces = SMB1/255.255.255.0 netbios name = SMB1 security = ADS realm = ADS.EXAMPLE.COM password server = ADS.Case.COM server string = Samba (%v) domain (%h) pid directory = /local/samba/smb1/var/locks log file = /local/samba/smb1/logs/log.%m smb passwd file = /local/samba/smb1/private/smbpasswd private dir = /local/samba/smb1/private lock dir = /local/samba/smb1/var/locks winbind enshroud time = 30 allow trusted domains = no idmap backend = rid:ADS=100000-200000 idmap uid = 100000-200000 idmap gid = 100000-200000 winbind enum groups = yes winbind enum users = aye winbind use default domain = yeah [scmondir] comment = Monitor directory for Sun Cluster path = /tmp browseable = No EOF

Note - If security = share is required and so you must include guest only = yes inside [scmondir].

Add together the NetBIOS name entry to /etc/hosts and /etc/inet/ipnodes.
Echo this step on all nodes or zones on the cluster.

Edit /etc/hosts and /etc/inet/ipnodes in the zones existence used for Samba and add together the NetBIOS name entries, for example:
```
#              egrep -e "SMB1|ADS" /etc/hosts /etc/inet/ipnodes              /etc/hosts:192.168.1.132    SMB1#20 /etc/hosts:192.168.1.ix      ADS.EXAMPLE.COM#20 /etc/inet/ipnodes:192.168.1.132    SMB1#20 /etc/inet/ipnodes:192.168.ane.9      ADS.Instance.COM#xx
```
Note - The name resolve order parameter in the smb.conf file will determine what naming service to use and in what guild to resolve host names to IP addresses. Refer to the smb.conf[5] for more than data.

The interfaces, netbios name and password server all require host name to IP address resolution.
If Samba will operate equally an Active Directory Domain Member Server, create the Kerberos krb5.conf file.
Repeat this step on all nodes or zones on the cluster.

Create the /etc/krb5.conf file in the zones being used for Samba, that reflects the ADS realm. Refer to http://world wide web.samba.org for complete information most installing and configuring Samba equally a ADS domain member.

The post-obit deployment case has been taken from Appendix B, Deployment Example: Installing Samba from http://www.samba.org.
```
Vigor5#              cat > /etc/krb5.conf <<-EOF [libdefaults] default_realm = ADS.Example.COM [realms] ADS.EXAMPLE.COM = { kdc = 192.168.i.9 admin_server = 192.168.1.9 } [domain_realm] .your.domain.proper noun = ADS.EXAMPLE.COM your.domain.proper noun = ADS.Example.COM EOF              Vigor5# Vigor5#              rm /etc/krb5/krb5.conf              Vigor5#              ln -s /etc/krb5.conf /etc/krb5/krb5.conf            
```

Configure the logical host.

Perform this step on ane node of the cluster.

The samba-logical-host should be the value you specified for the interfaces parameter when you created the smb.conf file in Footstep eight.

If the global zone only is existence used for Samba.

#                  ifconfig                  interface                  addif                  samba-logical-host                  upwardly

If a non-global zone or HA container is being used for Samba.

Configure the logical host within the zone.

#                  ifconfig                  interface                  addif                  samba-logical-host                  up zone                  zonename

Exam the smb.conf file.

Perform this step on 1 node or zone of the cluster.

If the global zone is existence used for Samba.

#                  samba-bin-directory                  /testparm \                  >                  samba-configuration-directory                  /lib/smb.conf

If a non-global zone or HA container is beingness used for Samba.

#                  zlogin                  zonename                  samba-bin-directory                  /testparm \                  >                  samba-configuration-directory                  /lib/smb.conf

If configured as a NT Domain Member and using Samba ii.ii.x join the domain.

Perform this stride on one node or zone of the cluster.

If the global zone is being used for Samba.

#                  samba-bin-directory                  /smbpasswd \                  >                  -c                  samba-configuration-directory                  /lib/smb.comf \                  >                  -j                  domain                  -r                  PDC                  \                  >                  -U                  Administrator-on-the-PDC

If a not-global zone or HA container is being used for Samba.

#                  zlogin                  zonename                  samba-bin-directory                  /smbpasswd \                  >                  -c                  samba-configuration-directory                  /lib/smb.comf \                  >                  -j                  domain                  -r                  PDC                  \                  >                  -U                  Ambassador-on-the-PDC

If configured as a NT Domain Fellow member and using Samba 3.0.x join the domain.

Perform this footstep on one node or zone of the cluster.

If the global zone is being used for Samba.

#                  samba-bin-directory                  /net \                  >                  -s                  samba-configuration-directory                  /lib/smb.comf \                  >                  RPC Join                  \                  >                  -U                  Ambassador-on-the-PDC

If a not-global zone or HA container is existence used for Samba.

#                  zlogin                  zonename                  samba-bin-directory                  /net \                  >                  -s                  samba-configuration-directory                  /lib/smb.comf \                  >                  RPC Join                  \                  >                  -U                  Administrator-on-the-PDC

If configured as a Windows 2003 Domain Member Server with ADS join the domain.

Perform this step on ane node or zone of the cluster.

If the global zone is beingness used for Samba.

#                  samba-bin-directory                  /internet \                  >                  -s                  samba-configuration-directory                  /lib/smb.comf \                  >                  ADS Join                  \                  >                  -U                  Administrator-on-the-ADS

If a non-global zone or HA container is being used for Samba.

#                  zlogin                  zonename                  samba-bin-directory                  /net \                  >                  -s                  samba-configuration-directory                  /lib/smb.comf \                  >                  ADS JOIN                  \                  >                  -U                  Administrator-on-the-ADS

If configured every bit a PDC or with security = user add the fault monitor user.

Perform this step on ane node or zone of the cluster.

If the global zone is beingness used for Samba.

#                  samba-bin-directory                  /smbpasswd \                  >                  -c                  samba-configuration-directory                  /lib/smb.comf \                  >                  -a                  samba-mistake-monitor-user

If a not-global zone or HA container is being used for Samba.

#                  zlogin                  zonename                  samba-bin-directory                  /smbpasswd \                  >                  -c                  samba-configuration-directory                  /lib/smb.comf \                  >                  -a                  samba-fault-monitor-user

If configured with security = share perform this step.
Ensure invitee simply = yes is coded within the [scmondir] section of your smb.conf file.