Ignore:
Timestamp:
Nov 24, 2016, 1:14:11 PM (9 years ago)
Author:
Silvan Scherrer
Message:

Samba Server: update vendor to version 4.4.3

File:
1 edited

Legend:

Unmodified
Added
Removed

  • vendor/current/docs-xml/Samba3-ByExample/SBE-AddingUNIXClients.xml

    r414 r988  
    307307        <indexterm><primary>Domain Controller</primary></indexterm>
    308308        The domain member server and the domain member client are at the center of focus in this chapter.
    309         Configuration of Samba-3 domain controller is covered in earlier chapters, so if your
     309        Configuration of Samba domain controller is covered in earlier chapters, so if your
    310310        interest is in domain controller configuration, you will not find that here. You will find good
    311311        oil that helps you to add domain member servers and clients.
    … …  
    675675<smbconfoption name="idmap gid">10000-20000</smbconfoption>
    676676<smbconfoption name="winbind trusted domains only">Yes</smbconfoption>
    677 <smbconfoption name="printer admin">root</smbconfoption>
    678677<smbconfoption name="printing">cups</smbconfoption>
    679678
    … …  
    949948<smbconfoption name="template shell">/bin/bash</smbconfoption>
    950949<smbconfoption name="winbind separator">+</smbconfoption>
    951 <smbconfoption name="printer admin">root</smbconfoption>
    952950<smbconfoption name="hosts allow">192.168.2., 192.168.3., 127.</smbconfoption>
    953951<smbconfoption name="printing">cups</smbconfoption>
    … …  
    10421040<smbconfoption name="printcap name">CUPS</smbconfoption>
    10431041<smbconfoption name="wins server">192.168.2.1</smbconfoption>
    1044 <smbconfoption name="printer admin">root</smbconfoption>
    10451042<smbconfoption name="hosts allow">192.168.2., 192.168.3., 127.</smbconfoption>
    10461043<smbconfoption name="printing">cups</smbconfoption>
    … …  
    10751072        <indexterm><primary>Kerberos</primary></indexterm>
    10761073        <indexterm><primary>Domain Member</primary><secondary>server</secondary></indexterm>
    1077         One of the much-sought-after features new to Samba-3 is the ability to join an Active Directory
     1074        One of the much-sought-after features new to Samba is the ability to join an Active Directory
    10781075        domain using Kerberos protocols. This makes it possible to operate an entire Windows network
    10791076        without the need to run NetBIOS over TCP/IP and permits more secure networking in general. An
    10801077        exhaustively complete discussion of the protocols is not possible in this book; perhaps a
    1081         later book may explore the intricacies of the NetBIOS-less operation that Samba-3 can participate
    1082         in. For now, we simply focus on how a Samba-3 server can be made a domain member server.
     1078        later book may explore the intricacies of the NetBIOS-less operation that Samba can participate
     1079        in. For now, we simply focus on how a Samba server can be made a domain member server.
    10831080        </para>
    10841081
    … …  
    10881085        <indexterm><primary>Identity resolution</primary></indexterm>
    10891086        <indexterm><primary>Kerberos</primary></indexterm>
    1090         The diagram in <link linkend="ch9-adsdc"/> demonstrates how Samba-3 interfaces with
     1087        The diagram in <link linkend="ch9-adsdc"/> demonstrates how Samba interfaces with
    10911088        Microsoft Active Directory components. It should be noted that if Microsoft Windows Services
    10921089        for UNIX (SFU) has been installed and correctly configured, it is possible to use client LDAP
    1093         for identity resolution just as can be done with Samba-3 when using an LDAP passdb backend.
     1090        for identity resolution just as can be done with Samba when using an LDAP passdb backend.
    10941091        The UNIX tool that you need for this, as in the case of LDAP on UNIX/Linux, is the PADL
    10951092        Software nss_ldap tool-set. Compared with use of winbind and Kerberos, the use of
    10961093        LDAP-based identity resolution is a little less secure. In view of the fact that this solution
    10971094        requires additional software to be installed on the Windows 200x ADS domain controllers,
    1098         and that means more management overhead, it is likely that most Samba-3 ADS client sites
     1095        and that means more management overhead, it is likely that most Samba ADS client sites
    10991096        may elect to use winbind.
    11001097        </para>
    11011098
    11021099        <para>
    1103         Do not attempt to use this procedure if you are not 100 percent certain that the build of Samba-3
     1100        Do not attempt to use this procedure if you are not 100 percent certain that the build of Samba
    11041101        you are using has been compiled and linked with all the tools necessary for this to work.
    1105         Given the importance of this step, you must first validate that the Samba-3 message block
     1102        Given the importance of this step, you must first validate that the Samba message block
    11061103        daemon (<command>smbd</command>) has the necessary features.
    11071104        </para>
    … …  
    11271124                <step><para>
    11281125                <indexterm><primary>smbd</primary></indexterm>
    1129                 Before you try to use Samba-3, you want to know for certain that your executables have
     1126                Before you try to use Samba, you want to know for certain that your executables have
    11301127                support for Kerberos and for LDAP. Execute the following to identify whether or
    11311128                not this build is perhaps suitable for use:
    … …  
    12051202                <indexterm><primary>validated</primary></indexterm>
    12061203                The next step is to identify which version of the Kerberos libraries have been used.
    1207                 In order to permit Samba-3 to interoperate with Windows 2003 Active Directory, it is
     1204                In order to permit Samba to interoperate with Windows 2003 Active Directory, it is
    12081205                essential that it has been linked with either MIT Kerberos version 1.3.1 or later,
    12091206                or that it has been linked with Heimdal Kerberos 0.6 plus specific patches. You may
    … …  
    12241221
    12251222                <para>
    1226                 From this point on, you are certain that the Samba-3 build you are using has the
    1227                 necessary capabilities. You can now configure Samba-3 and the NSS.
     1223                From this point on, you are certain that the Samba build you are using has the
     1224                necessary capabilities. You can now configure Samba and the NSS.
    12281225                </para></step>
    12291226
    … …  
    12751272Joined 'FRAN' to realm 'LONDON.ABMAS.BIZ'
    12761273</screen>
    1277                 You have successfully made your Samba-3 server a member of the ADS domain
     1274                You have successfully made your Samba server a member of the ADS domain
    12781275                using Kerberos protocols.
    12791276                </para>
    … …  
    14241421                <indexterm><primary>Active Directory</primary><secondary>server</secondary></indexterm>
    14251422                <indexterm><primary>Kerberos</primary></indexterm>
    1426                 You may now perform final verification that communications between Samba-3 winbind and
     1423                You may now perform final verification that communications between Samba winbind and
    14271424                the Active Directory server is using Kerberos protocols. Execute the following:
    14281425<screen>
    … …  
    15201517-------------- End Of Security Descriptor
    15211518</programlisting>
    1522                 And now you have conclusive proof that your Samba-3 ADS domain member server
     1519                And now you have conclusive proof that your Samba ADS domain member server
    15231520                called <constant>FRAN</constant> is able to communicate fully with the ADS
    15241521                domain controllers.
    … …  
    15291526
    15301527        <para>
    1531         Your Samba-3 ADS domain member server is ready for use. During training sessions,
     1528        Your Samba ADS domain member server is ready for use. During training sessions,
    15321529        you may be asked what is inside the <filename>winbindd_cache.tdb and winbindd_idmap.tdb</filename>
    15331530        files. Since curiosity just took hold of you, execute the following:
    … …  
    17241721<smbconfoption name="winbind enum groups">No</smbconfoption>
    17251722<smbconfoption name="winbind nested groups">Yes</smbconfoption>
    1726 <smbconfoption name="printer admin">"KPAK\Domain Admins"</smbconfoption>
    17271723</smbconfblock>
    17281724</example>
    … …  
    18181814        <indexterm><primary>ADAM</primary></indexterm>
    18191815        <indexterm><primary>ADS</primary></indexterm>
    1820         The storage of IDMAP information in LDAP can be used with both NT4/Samba-3-style domains as well as
     1816        The storage of IDMAP information in LDAP can be used with both NT4/Samba-style domains as well as
    18211817        with ADS domains. OpenLDAP is a commonly used LDAP server for this purpose, although any standards-compliant
    18221818        LDAP server can be used. It is therefore possible to deploy this IDMAP configuration using
    … …  
    18521848        <para>
    18531849        <indexterm><primary>realm</primary></indexterm>
    1854         In the case of an NT4 or Samba-3-style domain the <parameter>realm</parameter> is not used, and the
     1850        In the case of an NT4 or Samba-style domain the <parameter>realm</parameter> is not used, and the
    18551851        command used to join the domain is <command>net rpc join</command>. The above example also demonstrates
    18561852        advanced error reporting techniques that are documented in the chapter called "Reporting Bugs" in
    1857         <quote>The Official Samba-3 HOWTO and Reference Guide, Second Edition</quote> (TOSHARG2).
     1853        <quote>The Official Samba HOWTO and Reference Guide, Second Edition</quote> (TOSHARG2).
    18581854        </para>
    18591855
    … …  
    21952191        systems logons (SSO), providing user and group accounts are stored in an LDAP directory. This
    21962192        provides logon services for UNIX/Linux users, while Windows users obtain their sign-on
    2197         support via Samba-3.
     2193        support via Samba.
    21982194        </para>
    21992195
    … …  
    22232219                <para>
    22242220                The following steps provide a Linux system that users can log onto using
    2225                 Windows NT4 (or Samba-3) domain network credentials:
     2221                Windows NT4 (or Samba) domain network credentials:
    22262222                </para>
    22272223
    … …  
    27562752
    27572753                <para>
    2758                 Is proper DNS operation necessary for Samba-3 plus LDAP? If so, what must I put into
     2754                Is proper DNS operation necessary for Samba plus LDAP? If so, what must I put into
    27592755                my DNS configuration?
    27602756                </para>
    … …  
    28182814                <para>
    28192815                Our Windows 2003 Server Active Directory domain runs with NetBIOS disabled. Can we
    2820                 use Samba-3 with that configuration?
     2816                use Samba with that configuration?
    28212817                </para>
    28222818
    … …  
    28562852                <primary>authentication</primary>
    28572853              </indexterm>
    2858                 No. This is not okay. It means that your Samba-3 client has joined the ADS domain as
    2859                 a Windows NT4 client, and Samba-3 will not be using Kerberos-based authentication.
     2854                No. This is not okay. It means that your Samba client has joined the ADS domain as
     2855                a Windows NT4 client, and Samba will not be using Kerberos-based authentication.
    28602856                </para>
    28612857
Note: See TracChangeset for help on using the changeset viewer.