Ignore:
Timestamp:
Jun 24, 2009, 5:09:21 PM (16 years ago)
Author:
Herwig Bauernfeind
Message:

Update 3.0 to 3.0.35

File:
1 edited

Legend:

Unmodified
Added
Removed

  • branches/samba-3.0/docs/htmldocs/Samba3-HOWTO/domain-member.html

    r158 r286  
    1 <html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter 6. Domain Membership</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.73.2"><link rel="start" href="index.html" title="The Official Samba 3.2.x HOWTO and Reference Guide"><link rel="up" href="type.html" title="Part II. Server Configuration Basics"><link rel="prev" href="samba-bdc.html" title="Chapter 5. Backup Domain Control"><link rel="next" href="StandAloneServer.html" title="Chapter 7. Standalone Servers"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter 6. Domain Membership</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="samba-bdc.html">Prev</a> </td><th width="60%" align="center">Part II. Server Configuration Basics</th><td width="20%" align="right"> <a accesskey="n" href="StandAloneServer.html">Next</a></td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="domain-member"></a>Chapter 6. Domain Membership</h2></div><div><div class="author"><h3 class="author"><span class="firstname">John</span> <span class="othername">H.</span> <span class="surname">Terpstra</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><code class="email">&lt;<a class="email" href="mailto:jht@samba.org">jht@samba.org</a>&gt;</code></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">Jeremy</span> <span class="surname">Allison</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><code class="email">&lt;<a class="email" href="mailto:jra@samba.org">jra@samba.org</a>&gt;</code></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">Gerald</span> <span class="othername">(Jerry)</span> <span class="surname">Carter</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><code class="email">&lt;<a class="email" href="mailto:jerry@samba.org">jerry@samba.org</a>&gt;</code></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">Andrew</span> <span class="surname">Tridgell</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><code class="email">&lt;<a class="email" href="mailto:tridge@samba.org">tridge@samba.org</a>&gt;</code></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">Jelmer</span> <span class="othername">R.</span> <span class="surname">Vernooij</span></h3><div class="affiliation"><span class="orgname">The Samba Team<br></span><div class="address"><p><code class="email">&lt;<a class="email" href="mailto:jelmer@samba.org">jelmer@samba.org</a>&gt;</code></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">Guenther</span> <span class="surname">Deschner</span></h3><span class="contrib">LDAP updates</span> <div class="affiliation"><span class="orgname">SuSE<br></span><div class="address"><p><code class="email">&lt;<a class="email" href="mailto:gd@suse.de">gd@suse.de</a>&gt;</code></p></div></div></div></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="domain-member.html#id331937">Features and Benefits</a></span></dt><dt><span class="sect1"><a href="domain-member.html#machine-trust-accounts">MS Windows Workstation/Server Machine Trust Accounts</a></span></dt><dd><dl><dt><span class="sect2"><a href="domain-member.html#id332575">Manual Creation of Machine Trust Accounts</a></span></dt><dt><span class="sect2"><a href="domain-member.html#id332990">Managing Domain Machine Accounts using NT4 Server Manager</a></span></dt><dt><span class="sect2"><a href="domain-member.html#id333256">On-the-Fly Creation of Machine Trust Accounts</a></span></dt><dt><span class="sect2"><a href="domain-member.html#id333355">Making an MS Windows Workstation or Server a Domain Member</a></span></dt></dl></dd><dt><span class="sect1"><a href="domain-member.html#domain-member-server">Domain Member Server</a></span></dt><dd><dl><dt><span class="sect2"><a href="domain-member.html#id333787">Joining an NT4-type Domain with Samba-3</a></span></dt><dt><span class="sect2"><a href="domain-member.html#id334482">Why Is This Better Than <em class="parameter"><code>security = server</code></em>?</a></span></dt></dl></dd><dt><span class="sect1"><a href="domain-member.html#ads-member">Samba ADS Domain Membership</a></span></dt><dd><dl><dt><span class="sect2"><a href="domain-member.html#id334742">Configure <code class="filename">smb.conf</code></a></span></dt><dt><span class="sect2"><a href="domain-member.html#id334924">Configure <code class="filename">/etc/krb5.conf</code></a></span></dt><dt><span class="sect2"><a href="domain-member.html#ads-create-machine-account">Create the Computer Account</a></span></dt><dt><span class="sect2"><a href="domain-member.html#ads-test-server">Testing Server Setup</a></span></dt><dt><span class="sect2"><a href="domain-member.html#ads-test-smbclient">Testing with <span class="application">smbclient</span></a></span></dt><dt><span class="sect2"><a href="domain-member.html#id335956">Notes</a></span></dt></dl></dd><dt><span class="sect1"><a href="domain-member.html#id336026">Sharing User ID Mappings between Samba Domain Members</a></span></dt><dt><span class="sect1"><a href="domain-member.html#id336222">Common Errors</a></span></dt><dd><dl><dt><span class="sect2"><a href="domain-member.html#id336256">Cannot Add Machine Back to Domain</a></span></dt><dt><span class="sect2"><a href="domain-member.html#id336326">Adding Machine to Domain Fails</a></span></dt><dt><span class="sect2"><a href="domain-member.html#id336546">I Can't Join a Windows 2003 PDC</a></span></dt></dl></dd></dl></div><p>
    2 <a class="indexterm" name="id331892"></a>
    3 <a class="indexterm" name="id331899"></a>
    4 <a class="indexterm" name="id331906"></a>
     1<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter 6. Domain Membership</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"><link rel="home" href="index.html" title="The Official Samba 3.2.x HOWTO and Reference Guide"><link rel="up" href="type.html" title="Part II. Server Configuration Basics"><link rel="prev" href="samba-bdc.html" title="Chapter 5. Backup Domain Control"><link rel="next" href="StandAloneServer.html" title="Chapter 7. Standalone Servers"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter 6. Domain Membership</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="samba-bdc.html">Prev</a> </td><th width="60%" align="center">Part II. Server Configuration Basics</th><td width="20%" align="right"> <a accesskey="n" href="StandAloneServer.html">Next</a></td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="domain-member"></a>Chapter 6. Domain Membership</h2></div><div><div class="author"><h3 class="author"><span class="firstname">John</span> <span class="othername">H.</span> <span class="orgname">Samba Team</span> <span class="surname">Terpstra</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><code class="email">&lt;<a class="email" href="mailto:jht@samba.org">jht@samba.org</a>&gt;</code></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">Jeremy</span> <span class="orgname">Samba Team</span> <span class="surname">Allison</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><code class="email">&lt;<a class="email" href="mailto:jra@samba.org">jra@samba.org</a>&gt;</code></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">Gerald</span> <span class="othername">(Jerry)</span> <span class="orgname">Samba Team</span> <span class="surname">Carter</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><code class="email">&lt;<a class="email" href="mailto:jerry@samba.org">jerry@samba.org</a>&gt;</code></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">Andrew</span> <span class="orgname">Samba Team</span> <span class="surname">Tridgell</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><code class="email">&lt;<a class="email" href="mailto:tridge@samba.org">tridge@samba.org</a>&gt;</code></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">Jelmer</span> <span class="othername">R.</span> <span class="orgname">The Samba Team</span> <span class="surname">Vernooij</span></h3><div class="affiliation"><span class="orgname">The Samba Team<br></span><div class="address"><p><code class="email">&lt;<a class="email" href="mailto:jelmer@samba.org">jelmer@samba.org</a>&gt;</code></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">Guenther</span> <span class="orgname">SuSE</span> <span class="surname">Deschner</span></h3><span class="contrib">LDAP updates</span> <div class="affiliation"><span class="orgname">SuSE<br></span><div class="address"><p><code class="email">&lt;<a class="email" href="mailto:gd@suse.de">gd@suse.de</a>&gt;</code></p></div></div></div></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="domain-member.html#id2569108">Features and Benefits</a></span></dt><dt><span class="sect1"><a href="domain-member.html#machine-trust-accounts">MS Windows Workstation/Server Machine Trust Accounts</a></span></dt><dd><dl><dt><span class="sect2"><a href="domain-member.html#id2569795">Manual Creation of Machine Trust Accounts</a></span></dt><dt><span class="sect2"><a href="domain-member.html#id2570231">Managing Domain Machine Accounts using NT4 Server Manager</a></span></dt><dt><span class="sect2"><a href="domain-member.html#id2570512">On-the-Fly Creation of Machine Trust Accounts</a></span></dt><dt><span class="sect2"><a href="domain-member.html#id2570618">Making an MS Windows Workstation or Server a Domain Member</a></span></dt></dl></dd><dt><span class="sect1"><a href="domain-member.html#domain-member-server">Domain Member Server</a></span></dt><dd><dl><dt><span class="sect2"><a href="domain-member.html#id2571083">Joining an NT4-type Domain with Samba-3</a></span></dt><dt><span class="sect2"><a href="domain-member.html#id2571819">Why Is This Better Than security = server?</a></span></dt></dl></dd><dt><span class="sect1"><a href="domain-member.html#ads-member">Samba ADS Domain Membership</a></span></dt><dd><dl><dt><span class="sect2"><a href="domain-member.html#id2572101">Configure smb.conf</a></span></dt><dt><span class="sect2"><a href="domain-member.html#id2572292">Configure /etc/krb5.conf</a></span></dt><dt><span class="sect2"><a href="domain-member.html#ads-create-machine-account">Create the Computer Account</a></span></dt><dt><span class="sect2"><a href="domain-member.html#ads-test-server">Testing Server Setup</a></span></dt><dt><span class="sect2"><a href="domain-member.html#ads-test-smbclient">Testing with smbclient</a></span></dt><dt><span class="sect2"><a href="domain-member.html#id2573386">Notes</a></span></dt></dl></dd><dt><span class="sect1"><a href="domain-member.html#id2573458">Sharing User ID Mappings between Samba Domain Members</a></span></dt><dt><span class="sect1"><a href="domain-member.html#id2573664">Common Errors</a></span></dt><dd><dl><dt><span class="sect2"><a href="domain-member.html#id2573704">Cannot Add Machine Back to Domain</a></span></dt><dt><span class="sect2"><a href="domain-member.html#id2573780">Adding Machine to Domain Fails</a></span></dt><dt><span class="sect2"><a href="domain-member.html#id2574016">I Can't Join a Windows 2003 PDC</a></span></dt></dl></dd></dl></div><p>
     2<a class="indexterm" name="id2569056"></a>
     3<a class="indexterm" name="id2569062"></a>
     4<a class="indexterm" name="id2569070"></a>
    55Domain membership is a subject of vital concern. Samba must be able to
    66participate as a member server in a Microsoft domain security context, and
    … …  
    88otherwise it would not be able to offer a viable option for many users.
    99</p><p>
    10 <a class="indexterm" name="id331919"></a>
    11 <a class="indexterm" name="id331925"></a>
     10<a class="indexterm" name="id2569085"></a>
     11<a class="indexterm" name="id2569092"></a>
    1212This chapter covers background information pertaining to domain membership,
    1313the Samba configuration for it, and MS Windows client procedures for joining a
    … …  
    1717misinformation, incorrect understanding, and lack of knowledge. Hopefully
    1818this chapter will fill the voids.
    19 </p><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id331937"></a>Features and Benefits</h2></div></div></div><p>
    20 <a class="indexterm" name="id331945"></a>
    21 <a class="indexterm" name="id331952"></a>
    22 <a class="indexterm" name="id331959"></a>
     19</p><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2569108"></a>Features and Benefits</h2></div></div></div><p>
     20<a class="indexterm" name="id2569116"></a>
     21<a class="indexterm" name="id2569123"></a>
     22<a class="indexterm" name="id2569130"></a>
    2323MS Windows workstations and servers that want to participate in domain security need to
    2424be made domain members. Participating in domain security is often called
    … …  
    2828server) or a Samba server a member of an MS Windows domain security context.
    2929</p><p>
    30 <a class="indexterm" name="id331987"></a>
    31 <a class="indexterm" name="id331994"></a>
    32 <a class="indexterm" name="id332001"></a>
    33 <a class="indexterm" name="id332007"></a>
     30<a class="indexterm" name="id2569162"></a>
     31<a class="indexterm" name="id2569168"></a>
     32<a class="indexterm" name="id2569175"></a>
     33<a class="indexterm" name="id2569182"></a>
    3434Samba-3 can join an MS Windows NT4-style domain as a native member server, an
    3535MS Windows Active Directory domain as a native member server, or a Samba domain
    3636control network. Domain membership has many advantages:
    3737</p><div class="itemizedlist"><ul type="disc"><li><p>
    38         <a class="indexterm" name="id332025"></a>
     38        <a class="indexterm" name="id2569201"></a>
    3939        MS Windows workstation users get the benefit of SSO.
    4040        </p></li><li><p>
    41         <a class="indexterm" name="id332036"></a>
    42         <a class="indexterm" name="id332043"></a>
    43         <a class="indexterm" name="id332050"></a>
    44         <a class="indexterm" name="id332057"></a>
     41        <a class="indexterm" name="id2569213"></a>
     42        <a class="indexterm" name="id2569220"></a>
     43        <a class="indexterm" name="id2569227"></a>
     44        <a class="indexterm" name="id2569234"></a>
    4545        Domain user access rights and file ownership/access controls can be set
    4646        from the single Domain Security Account Manager (SAM) database
    … …  
    4848        that are domain members).
    4949        </p></li><li><p>
    50         <a class="indexterm" name="id332070"></a>
    51         <a class="indexterm" name="id332077"></a>
     50        <a class="indexterm" name="id2569249"></a>
     51        <a class="indexterm" name="id2569256"></a>
    5252        Only <span class="application">MS Windows NT4/200x/XP Professional</span>
    5353        workstations that are domain members can use network logon facilities.
    5454        </p></li><li><p>
    55         <a class="indexterm" name="id332095"></a>
    56         <a class="indexterm" name="id332101"></a>
    57         <a class="indexterm" name="id332108"></a>
    58         <a class="indexterm" name="id332115"></a>
     55        <a class="indexterm" name="id2569275"></a>
     56        <a class="indexterm" name="id2569282"></a>
     57        <a class="indexterm" name="id2569289"></a>
     58        <a class="indexterm" name="id2569296"></a>
    5959        Domain member workstations can be better controlled through the use of
    6060        policy files (<code class="filename">NTConfig.POL</code>) and desktop profiles.
    6161        </p></li><li><p>
    62         <a class="indexterm" name="id332133"></a>
    63         <a class="indexterm" name="id332140"></a>
    64         <a class="indexterm" name="id332147"></a>
     62        <a class="indexterm" name="id2569315"></a>
     63        <a class="indexterm" name="id2569322"></a>
     64        <a class="indexterm" name="id2569329"></a>
    6565        Through the use of logon scripts, users can be given transparent access to network
    6666        applications that run off application servers.
    6767        </p></li><li><p>
    68         <a class="indexterm" name="id332159"></a>
    69         <a class="indexterm" name="id332166"></a>
    70         <a class="indexterm" name="id332172"></a>
    71         <a class="indexterm" name="id332179"></a>
     68        <a class="indexterm" name="id2569342"></a>
     69        <a class="indexterm" name="id2569349"></a>
     70        <a class="indexterm" name="id2569356"></a>
     71        <a class="indexterm" name="id2569363"></a>
    7272        Network administrators gain better application and user access management
    7373        abilities because there is no need to maintain user accounts on any network
    … …  
    7676        LDAP directory, or via an Active Directory infrastructure).
    7777        </p></li></ul></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="machine-trust-accounts"></a>MS Windows Workstation/Server Machine Trust Accounts</h2></div></div></div><p>
    78 <a class="indexterm" name="id332203"></a>
    79 <a class="indexterm" name="id332210"></a>
    80 <a class="indexterm" name="id332217"></a>
    81 <a class="indexterm" name="id332223"></a>
     78<a class="indexterm" name="id2569391"></a>
     79<a class="indexterm" name="id2569398"></a>
     80<a class="indexterm" name="id2569405"></a>
     81<a class="indexterm" name="id2569412"></a>
    8282A Machine Trust Account is an account that is used to authenticate a client machine (rather than a user) to
    8383the domain controller server. In Windows terminology, this is known as a &#8220;<span class="quote">computer account.</span>&#8221; The
    … …  
    8585access to a domain member workstation.
    8686</p><p>
    87 <a class="indexterm" name="id332240"></a>
    88 <a class="indexterm" name="id332249"></a>
    89 <a class="indexterm" name="id332256"></a>
    90 <a class="indexterm" name="id332263"></a>
    91 <a class="indexterm" name="id332270"></a>
     87<a class="indexterm" name="id2569431"></a>
     88<a class="indexterm" name="id2569440"></a>
     89<a class="indexterm" name="id2569447"></a>
     90<a class="indexterm" name="id2569454"></a>
     91<a class="indexterm" name="id2569462"></a>
    9292The password of a Machine Trust Account acts as the shared secret for secure communication with the domain
    9393controller. This is a security feature to prevent an unauthorized machine with the same NetBIOS name from
    … …  
    9797possess a Machine Trust Account, and, thus, has no shared secret with the domain controller.
    9898</p><p>
    99 <a class="indexterm" name="id332285"></a>
    100 <a class="indexterm" name="id332292"></a>
    101 <a class="indexterm" name="id332298"></a>
    102 <a class="indexterm" name="id332305"></a>
     99<a class="indexterm" name="id2569482"></a>
     100<a class="indexterm" name="id2569489"></a>
     101<a class="indexterm" name="id2569496"></a>
     102<a class="indexterm" name="id2569502"></a>
    103103A Windows NT4 PDC stores each Machine Trust Account in the Windows Registry.
    104104The introduction of MS Windows 2000 saw the introduction of Active Directory,
    … …  
    108108
    109109</p><div class="itemizedlist"><ul type="disc"><li><p>
    110         <a class="indexterm" name="id332320"></a>
    111         <a class="indexterm" name="id332326"></a>
    112         <a class="indexterm" name="id332333"></a>
    113         A domain security account (stored in the <a class="link" href="smb.conf.5.html#PASSDBBACKEND">passdb backend</a>) that has been configured in
     110        <a class="indexterm" name="id2569520"></a>
     111        <a class="indexterm" name="id2569527"></a>
     112        <a class="indexterm" name="id2569534"></a>
     113        A domain security account (stored in the <a class="link" href="smb.conf.5.html#PASSDBBACKEND" target="_top">passdb backend</a>) that has been configured in
    114114        the <code class="filename">smb.conf</code> file. The precise nature of the account information that is stored depends on the type of
    115115        backend database that has been chosen.
    116116        </p><p>
    117         <a class="indexterm" name="id332361"></a>
    118         <a class="indexterm" name="id332368"></a>
    119         <a class="indexterm" name="id332375"></a>
    120         <a class="indexterm" name="id332381"></a>
    121         <a class="indexterm" name="id332388"></a>
    122         <a class="indexterm" name="id332395"></a>
     117        <a class="indexterm" name="id2569565"></a>
     118        <a class="indexterm" name="id2569572"></a>
     119        <a class="indexterm" name="id2569579"></a>
     120        <a class="indexterm" name="id2569586"></a>
     121        <a class="indexterm" name="id2569592"></a>
     122        <a class="indexterm" name="id2569600"></a>
    123123        The older format of this data is the <code class="filename">smbpasswd</code> database
    124124        that contains the UNIX login ID, the UNIX user identifier (UID), and the
    … …  
    126126        this file that we do not need to concern ourselves with here.
    127127        </p><p>
    128         <a class="indexterm" name="id332415"></a>
    129         <a class="indexterm" name="id332422"></a>
    130         <a class="indexterm" name="id332429"></a>
    131         <a class="indexterm" name="id332436"></a>
     128        <a class="indexterm" name="id2569622"></a>
     129        <a class="indexterm" name="id2569628"></a>
     130        <a class="indexterm" name="id2569635"></a>
     131        <a class="indexterm" name="id2569642"></a>
    132132        The two newer database types are called ldapsam and tdbsam. Both store considerably more data than the older
    133133        <code class="filename">smbpasswd</code> file did. The extra information enables new user account controls to be
    134134        implemented.
    135135        </p></li><li><p>
    136         <a class="indexterm" name="id332454"></a>
    137         <a class="indexterm" name="id332461"></a>
     136        <a class="indexterm" name="id2569662"></a>
     137        <a class="indexterm" name="id2569669"></a>
    138138        A corresponding UNIX account, typically stored in <code class="filename">/etc/passwd</code>. Work is in progress to
    139139        allow a simplified mode of operation that does not require UNIX user accounts, but this has not been a feature
    … …  
    141141        </p></li></ul></div><p>
    142142</p><p>
    143 <a class="indexterm" name="id332485"></a>
     143<a class="indexterm" name="id2569695"></a>
    144144There are three ways to create Machine Trust Accounts:
    145145</p><div class="itemizedlist"><ul type="disc"><li><p>
    146         <a class="indexterm" name="id332500"></a>
     146        <a class="indexterm" name="id2569712"></a>
    147147        Manual creation from the UNIX/Linux command line. Here, both the Samba and
    148148        corresponding UNIX account are created by hand.
    149149        </p></li><li><p>
    150         <a class="indexterm" name="id332513"></a>
    151         <a class="indexterm" name="id332520"></a>
     150        <a class="indexterm" name="id2569725"></a>
     151        <a class="indexterm" name="id2569732"></a>
    152152        Using the MS Windows NT4 Server Manager, either from an NT4 domain member
    153153        server or using the Nexus toolkit available from the Microsoft Web site.
    … …  
    155155        logged on as the administrator account.
    156156        </p></li><li><p>
    157         <a class="indexterm" name="id332533"></a>
    158         <a class="indexterm" name="id332540"></a>
     157        <a class="indexterm" name="id2569748"></a>
     158        <a class="indexterm" name="id2569755"></a>
    159159        &#8220;<span class="quote">On-the-fly</span>&#8221; creation. The Samba Machine Trust Account is automatically
    160160        created by Samba at the time the client is joined to the domain.
    … …  
    162162        account may be created automatically or manually.
    163163        </p></li></ul></div><p>
    164 <a class="indexterm" name="id332557"></a>
    165 <a class="indexterm" name="id332563"></a>
     164<a class="indexterm" name="id2569774"></a>
     165<a class="indexterm" name="id2569781"></a>
    166166Neither MS Windows NT4/200x/XP Professional, nor Samba, provide any method for enforcing the method of machine
    167167trust account creation. This is a matter of the administrator's choice.
    168 </p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id332575"></a>Manual Creation of Machine Trust Accounts</h3></div></div></div><p>
    169 <a class="indexterm" name="id332583"></a>
    170 <a class="indexterm" name="id332590"></a>
    171 <a class="indexterm" name="id332596"></a>
    172 <a class="indexterm" name="id332602"></a>
     168</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2569795"></a>Manual Creation of Machine Trust Accounts</h3></div></div></div><p>
     169<a class="indexterm" name="id2569803"></a>
     170<a class="indexterm" name="id2569810"></a>
     171<a class="indexterm" name="id2569815"></a>
     172<a class="indexterm" name="id2569822"></a>
    173173The first step in manually creating a Machine Trust Account is to manually
    174174create the corresponding UNIX account in <code class="filename">/etc/passwd</code>.
    … …  
    184184</pre><p>
    185185</p><p>
    186 <a class="indexterm" name="id332668"></a>
    187 <a class="indexterm" name="id332674"></a>
    188 <a class="indexterm" name="id332681"></a>
     186<a class="indexterm" name="id2569891"></a>
     187<a class="indexterm" name="id2569898"></a>
     188<a class="indexterm" name="id2569904"></a>
    189189In the example above there is an existing system group &#8220;<span class="quote">machines</span>&#8221; which is used
    190190as the primary group for all machine accounts. In the following examples the &#8220;<span class="quote">machines</span>&#8221; group
    191191numeric GID is 100.
    192192</p><p>
    193 <a class="indexterm" name="id332700"></a>
    194 <a class="indexterm" name="id332707"></a>
     193<a class="indexterm" name="id2569924"></a>
     194<a class="indexterm" name="id2569931"></a>
    195195On *BSD systems, this can be done using the <code class="literal">chpass</code> utility:
    196196</p><pre class="screen">
    … …  
    199199</pre><p>
    200200</p><p>
    201 <a class="indexterm" name="id332747"></a>
    202 <a class="indexterm" name="id332753"></a>
    203 <a class="indexterm" name="id332760"></a>
    204 <a class="indexterm" name="id332767"></a>
     201<a class="indexterm" name="id2569972"></a>
     202<a class="indexterm" name="id2569979"></a>
     203<a class="indexterm" name="id2569986"></a>
     204<a class="indexterm" name="id2569992"></a>
    205205The <code class="filename">/etc/passwd</code> entry will list the machine name
    206206with a &#8220;<span class="quote">$</span>&#8221; appended, and will not have a password, will have a null shell and no
    … …  
    211211</pre><p>
    212212</p><p>
    213 <a class="indexterm" name="id332807"></a>
    214 <a class="indexterm" name="id332814"></a>
    215 <a class="indexterm" name="id332820"></a>
     213<a class="indexterm" name="id2570035"></a>
     214<a class="indexterm" name="id2570042"></a>
     215<a class="indexterm" name="id2570049"></a>
    216216in which <em class="replaceable"><code>machine_nickname</code></em> can be any
    217217descriptive name for the client, such as BasementComputer.
    … …  
    221221this as a Machine Trust Account.
    222222</p><p>
    223 <a class="indexterm" name="id332843"></a>
    224 <a class="indexterm" name="id332850"></a>
    225 <a class="indexterm" name="id332857"></a>
     223<a class="indexterm" name="id2570074"></a>
     224<a class="indexterm" name="id2570081"></a>
     225<a class="indexterm" name="id2570088"></a>
    226226Now that the corresponding UNIX account has been created, the next step is to create
    227227the Samba account for the client containing the well-known initial
    … …  
    233233</pre><p>
    234234</p><p>
    235 <a class="indexterm" name="id332896"></a>
    236 <a class="indexterm" name="id332902"></a>
    237 <a class="indexterm" name="id332909"></a>
    238 <a class="indexterm" name="id332916"></a>
     235<a class="indexterm" name="id2570130"></a>
     236<a class="indexterm" name="id2570137"></a>
     237<a class="indexterm" name="id2570144"></a>
     238<a class="indexterm" name="id2570150"></a>
    239239where <em class="replaceable"><code>machine_name</code></em> is the machine's NetBIOS
    240240name. The RID of the new machine account is generated from the UID of
    241241the corresponding UNIX account.
    242242</p><div class="warning" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Join the client to the domain immediately</h3><p>
    243 <a class="indexterm" name="id332936"></a>
    244 <a class="indexterm" name="id332943"></a>
    245 <a class="indexterm" name="id332950"></a>
    246 <a class="indexterm" name="id332956"></a>
    247 <a class="indexterm" name="id332963"></a>
     243<a class="indexterm" name="id2570172"></a>
     244<a class="indexterm" name="id2570179"></a>
     245<a class="indexterm" name="id2570186"></a>
     246<a class="indexterm" name="id2570193"></a>
     247<a class="indexterm" name="id2570200"></a>
    248248Manually creating a Machine Trust Account using this method is the
    249249equivalent of creating a Machine Trust Account on a Windows NT PDC using
    250 <a class="indexterm" name="id332971"></a>
     250<a class="indexterm" name="id2570209"></a>
    251251the <span class="application">Server Manager</span>. From the time at which the
    252252account is created to the time the client joins the domain and
    … …  
    255255trusts members of the domain and will serve out a large degree of user
    256256information to such clients. You have been warned!
    257 </p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id332990"></a>Managing Domain Machine Accounts using NT4 Server Manager</h3></div></div></div><p>
    258 <a class="indexterm" name="id332999"></a>
    259 <a class="indexterm" name="id333005"></a>
    260 <a class="indexterm" name="id333012"></a>
    261 A working <a class="link" href="smb.conf.5.html#ADDMACHINESCRIPT">add machine script</a> is essential
     257</p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2570231"></a>Managing Domain Machine Accounts using NT4 Server Manager</h3></div></div></div><p>
     258<a class="indexterm" name="id2570240"></a>
     259<a class="indexterm" name="id2570247"></a>
     260<a class="indexterm" name="id2570254"></a>
     261A working <a class="link" href="smb.conf.5.html#ADDMACHINESCRIPT" target="_top">add machine script</a> is essential
    262262for machine trust accounts to be automatically created. This applies no matter whether
    263263you use automatic account creation or the NT4 Domain Server Manager.
    264264</p><p>
    265 <a class="indexterm" name="id333035"></a>
    266 <a class="indexterm" name="id333041"></a>
    267 <a class="indexterm" name="id333048"></a>
    268 <a class="indexterm" name="id333055"></a>
     265<a class="indexterm" name="id2570280"></a>
     266<a class="indexterm" name="id2570287"></a>
     267<a class="indexterm" name="id2570293"></a>
     268<a class="indexterm" name="id2570300"></a>
    269269If the machine from which you are trying to manage the domain is an
    270270<span class="application">MS Windows NT4 workstation or MS Windows 200x/XP Professional</span>,
    … …  
    273273and <code class="literal">UsrMgr.exe</code> (both are domain management tools for MS Windows NT4 workstation).
    274274</p><p>
    275 <a class="indexterm" name="id333091"></a>
    276 <a class="indexterm" name="id333098"></a>
     275<a class="indexterm" name="id2570338"></a>
     276<a class="indexterm" name="id2570345"></a>
    277277If your workstation is a <span class="application">Microsoft Windows 9x/Me</span> family product,
    278278 you should download the <code class="literal">Nexus.exe</code> package from the Microsoft Web site.
    … …  
    284284<a class="ulink" href="http://support.microsoft.com/default.aspx?scid=kb;en-us;172540" target="_top">172540</a>
    285285</p><p>
    286 <a class="indexterm" name="id333138"></a>
    287 <a class="indexterm" name="id333145"></a>
     286<a class="indexterm" name="id2570389"></a>
     287<a class="indexterm" name="id2570396"></a>
    288288Launch the <code class="literal">srvmgr.exe</code> (Server Manager for Domains) and follow these steps:
    289 </p><div class="procedure"><a name="id333159"></a><p class="title"><b>Procedure 6.1. Server Manager Account Machine Account Management</b></p><ol type="1"><li><p>
     289</p><div class="procedure"><a name="id2570411"></a><p class="title"><b>Procedure 6.1. Server Manager Account Machine Account Management</b></p><ol type="1"><li><p>
    290290        From the menu select <span class="guimenu">Computer</span>.
    291291        </p></li><li><p>
    … …  
    304304        enter the machine name in the field provided, and click the
    305305        <span class="guibutton">Add</span> button.
    306         </p></li></ol></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id333256"></a>On-the-Fly Creation of Machine Trust Accounts</h3></div></div></div><p>
    307 <a class="indexterm" name="id333264"></a>
     306        </p></li></ol></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2570512"></a>On-the-Fly Creation of Machine Trust Accounts</h3></div></div></div><p>
     307<a class="indexterm" name="id2570520"></a>
    308308The third (and recommended) way of creating Machine Trust Accounts is simply to allow the Samba server to
    309309create them as needed when the client is joined to the domain.
    310310</p><p>
    311 <a class="indexterm" name="id333278"></a>
    312 <a class="indexterm" name="id333287"></a>
    313 <a class="indexterm" name="id333294"></a>
     311<a class="indexterm" name="id2570536"></a>
     312<a class="indexterm" name="id2570546"></a>
     313<a class="indexterm" name="id2570552"></a>
    314314Since each Samba Machine Trust Account requires a corresponding UNIX account, a method
    315315for automatically creating the UNIX account is usually supplied; this requires configuration of the
    … …  
    317317accounts may also be created manually.
    318318</p><p>
    319 <a class="indexterm" name="id333312"></a>
    320 <a class="indexterm" name="id333319"></a>
     319<a class="indexterm" name="id2570574"></a>
     320<a class="indexterm" name="id2570581"></a>
    321321Here is an example for a Red Hat Linux system:
    322 </p><table class="simplelist" border="0" summary="Simple list"><tr><td> </td></tr><tr><td><em class="parameter"><code>[global]</code></em></td></tr><tr><td><a class="indexterm" name="id333341"></a><em class="parameter"><code>add machine script = /usr/sbin/useradd -d /var/lib/nobody -g 100 -s /bin/false -M %u</code></em></td></tr></table><p>
    323 </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id333355"></a>Making an MS Windows Workstation or Server a Domain Member</h3></div></div></div><p>
     322</p><table class="simplelist" border="0" summary="Simple list"><tr><td> </td></tr><tr><td><em class="parameter"><code>[global]</code></em></td></tr><tr><td><a class="indexterm" name="id2570603"></a><em class="parameter"><code>add machine script = /usr/sbin/useradd -d /var/lib/nobody -g 100 -s /bin/false -M %u</code></em></td></tr></table><p>
     323</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2570618"></a>Making an MS Windows Workstation or Server a Domain Member</h3></div></div></div><p>
    324324The procedure for making an MS Windows workstation or server a member of the domain varies
    325325with the version of Windows.
    326 </p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id333364"></a>Windows 200x/XP Professional Client</h4></div></div></div><p>
    327 <a class="indexterm" name="id333372"></a>
    328 <a class="indexterm" name="id333379"></a>
    329 <a class="indexterm" name="id333388"></a>
    330 <a class="indexterm" name="id333395"></a>
     326</p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2570629"></a>Windows 200x/XP Professional Client</h4></div></div></div><p>
     327<a class="indexterm" name="id2570637"></a>
     328<a class="indexterm" name="id2570644"></a>
     329<a class="indexterm" name="id2570653"></a>
     330<a class="indexterm" name="id2570660"></a>
    331331        When the user elects to make the client a domain member, Windows 200x prompts for
    332332        an account and password that has privileges to create  machine accounts in the domain.
    … …  
    335335        account is given.
    336336        </p><p>
    337 <a class="indexterm" name="id333412"></a>
    338 <a class="indexterm" name="id333419"></a>
     337<a class="indexterm" name="id2570680"></a>
     338<a class="indexterm" name="id2570687"></a>
    339339        For security reasons, the password for this administrator account should be set
    340340        to a password that is other than that used for the root user in <code class="filename">/etc/passwd</code>.
    341341        </p><p>
    342 <a class="indexterm" name="id333436"></a>
    343 <a class="indexterm" name="id333443"></a>
    344 <a class="indexterm" name="id333449"></a>
    345 <a class="indexterm" name="id333456"></a>
     342<a class="indexterm" name="id2570705"></a>
     343<a class="indexterm" name="id2570712"></a>
     344<a class="indexterm" name="id2570719"></a>
     345<a class="indexterm" name="id2570726"></a>
    346346        The name of the account that is used to create domain member machine trust accounts can be
    347347        anything the network administrator may choose. If it is other than <code class="constant">root</code>,
    348348        then this is easily mapped to <code class="constant">root</code> in the file named in the <code class="filename">smb.conf</code> parameter
    349         <a class="link" href="smb.conf.5.html#USERNAMEMAP">username map = /etc/samba/smbusers</a>.
     349        <a class="link" href="smb.conf.5.html#USERNAMEMAP" target="_top">username map = /etc/samba/smbusers</a>.
    350350        </p><p>
    351 <a class="indexterm" name="id333493"></a>
    352 <a class="indexterm" name="id333499"></a>
    353 <a class="indexterm" name="id333506"></a>
     351<a class="indexterm" name="id2570766"></a>
     352<a class="indexterm" name="id2570773"></a>
     353<a class="indexterm" name="id2570779"></a>
    354354        The session key of the Samba administrator account acts as an encryption key for setting the password of the machine trust
    355355        account. The Machine Trust Account will be created on-the-fly, or updated if it already exists.
    356         </p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id333517"></a>Windows NT4 Client</h4></div></div></div><p>
    357 <a class="indexterm" name="id333525"></a>
    358 <a class="indexterm" name="id333531"></a>
    359 <a class="indexterm" name="id333538"></a>
     356        </p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2570792"></a>Windows NT4 Client</h4></div></div></div><p>
     357<a class="indexterm" name="id2570800"></a>
     358<a class="indexterm" name="id2570807"></a>
     359<a class="indexterm" name="id2570814"></a>
    360360        If the Machine Trust Account was created manually, on the
    361361        Identification Changes menu enter the domain name, but do not
    … …  
    364364        to the domain.
    365365        </p><p>
    366 <a class="indexterm" name="id333556"></a>
    367 <a class="indexterm" name="id333563"></a>
    368 <a class="indexterm" name="id333570"></a>
    369 <a class="indexterm" name="id333577"></a>
     366<a class="indexterm" name="id2570834"></a>
     367<a class="indexterm" name="id2570841"></a>
     368<a class="indexterm" name="id2570848"></a>
     369<a class="indexterm" name="id2570855"></a>
    370370        If the Machine Trust Account is to be created on the fly, on the Identification Changes menu enter the domain
    371371        name and check the box <span class="guilabel">Create a Computer Account in the Domain</span>. In this case, joining
    372372        the domain proceeds as above for Windows 2000 (i.e., you must supply a Samba administrator account when
    373373        prompted).
    374         </p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id333594"></a>Samba Client</h4></div></div></div><p>
    375 <a class="indexterm" name="id333602"></a>
     374        </p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2570875"></a>Samba Client</h4></div></div></div><p>
     375<a class="indexterm" name="id2570883"></a>
    376376        Joining a Samba client to a domain is documented in <a class="link" href="domain-member.html#domain-member-server" title="Domain Member Server">the next section</a>.
    377377        </p></div></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="domain-member-server"></a>Domain Member Server</h2></div></div></div><p>
    378 <a class="indexterm" name="id333631"></a>
    379 <a class="indexterm" name="id333637"></a>
    380 <a class="indexterm" name="id333644"></a>
    381 <a class="indexterm" name="id333651"></a>
     378<a class="indexterm" name="id2570914"></a>
     379<a class="indexterm" name="id2570921"></a>
     380<a class="indexterm" name="id2570928"></a>
     381<a class="indexterm" name="id2570935"></a>
    382382This mode of server operation involves the Samba machine being made a member
    383383of a domain security context. This means by definition that all user
    … …  
    388388</p><p>
    389389<span class="emphasis"><em>
    390 <a class="indexterm" name="id333666"></a>
    391 <a class="indexterm" name="id333676"></a>
    392 <a class="indexterm" name="id333682"></a>
    393 <a class="indexterm" name="id333689"></a>
    394 <a class="indexterm" name="id333696"></a>
    395 <a class="indexterm" name="id333703"></a>
    396 <a class="indexterm" name="id333709"></a>
    397 <a class="indexterm" name="id333716"></a>
     390<a class="indexterm" name="id2570954"></a>
     391<a class="indexterm" name="id2570963"></a>
     392<a class="indexterm" name="id2570970"></a>
     393<a class="indexterm" name="id2570977"></a>
     394<a class="indexterm" name="id2570984"></a>
     395<a class="indexterm" name="id2570991"></a>
     396<a class="indexterm" name="id2570997"></a>
     397<a class="indexterm" name="id2571004"></a>
    398398Of course it should be clear that the authentication backend itself could be
    399399from any distributed directory architecture server that is supported by Samba.
    … …  
    402402</em></span>
    403403</p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
    404 <a class="indexterm" name="id333731"></a>
    405 <a class="indexterm" name="id333737"></a>
    406 <a class="indexterm" name="id333744"></a>
     404<a class="indexterm" name="id2571020"></a>
     405<a class="indexterm" name="id2571027"></a>
     406<a class="indexterm" name="id2571034"></a>
    407407When Samba is configured to use an LDAP or other identity management and/or
    408408directory service, it is Samba that continues to perform user and machine
    … …  
    410410authentication handling in place of what Samba is designed to do.
    411411</p></div><p>
    412 <a class="indexterm" name="id333757"></a>
    413 <a class="indexterm" name="id333764"></a>
    414 <a class="indexterm" name="id333770"></a>
     412<a class="indexterm" name="id2571049"></a>
     413<a class="indexterm" name="id2571056"></a>
     414<a class="indexterm" name="id2571064"></a>
    415415Please refer to <a class="link" href="samba-pdc.html" title="Chapter 4. Domain Control">Domain Control</a>, for more information regarding
    416416how to create a domain machine account for a domain member server as well as for
    417417information on how to enable the Samba domain member machine to join the domain
    418418and be fully trusted by it.
    419 </p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id333787"></a>Joining an NT4-type Domain with Samba-3</h3></div></div></div><p><a class="link" href="domain-member.html#assumptions" title="Table 6.1. Assumptions">Assumptions</a> lists names that are used in the remainder of this chapter.</p><div class="table"><a name="assumptions"></a><p class="title"><b>Table 6.1. Assumptions</b></p><div class="table-contents"><table summary="Assumptions" border="1"><colgroup><col align="right"><col align="left"></colgroup><tbody><tr><td align="right">Samba DMS NetBIOS name:</td><td align="left">SERV1</td></tr><tr><td align="right">Windows 200x/NT domain name:</td><td align="left">MIDEARTH</td></tr><tr><td align="right">Domain's PDC NetBIOS name:</td><td align="left">DOMPDC</td></tr><tr><td align="right">Domain's BDC NetBIOS names:</td><td align="left">DOMBDC1 and DOMBDC2</td></tr></tbody></table></div></div><br class="table-break"><p>
    420 <a class="indexterm" name="id333870"></a>
     419</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2571083"></a>Joining an NT4-type Domain with Samba-3</h3></div></div></div><p><a class="link" href="domain-member.html#assumptions" title="Table 6.1. Assumptions">Assumptions</a> lists names that are used in the remainder of this chapter.</p><div class="table"><a name="assumptions"></a><p class="title"><b>Table 6.1. Assumptions</b></p><div class="table-contents"><table summary="Assumptions" border="1"><colgroup><col align="right"><col align="left"></colgroup><tbody><tr><td align="right">Samba DMS NetBIOS name:</td><td align="left">SERV1</td></tr><tr><td align="right">Windows 200x/NT domain name:</td><td align="left">MIDEARTH</td></tr><tr><td align="right">Domain's PDC NetBIOS name:</td><td align="left">DOMPDC</td></tr><tr><td align="right">Domain's BDC NetBIOS names:</td><td align="left">DOMBDC1 and DOMBDC2</td></tr></tbody></table></div></div><br class="table-break"><p>
     420<a class="indexterm" name="id2571167"></a>
    421421First, you must edit your <code class="filename">smb.conf</code> file to tell Samba it should now use domain security.
    422422</p><p>
    423 <a class="indexterm" name="id333885"></a>
    424 <a class="indexterm" name="id333892"></a>
    425 <a class="indexterm" name="id333899"></a>
    426 <a class="indexterm" name="id333906"></a>
    427 Change (or add) your <a class="link" href="smb.conf.5.html#SECURITY">security</a> line in the [global] section
     423<a class="indexterm" name="id2571183"></a>
     424<a class="indexterm" name="id2571190"></a>
     425<a class="indexterm" name="id2571197"></a>
     426<a class="indexterm" name="id2571204"></a>
     427Change (or add) your <a class="link" href="smb.conf.5.html#SECURITY" target="_top">security</a> line in the [global] section
    428428of your <code class="filename">smb.conf</code> to read:
    429 </p><table class="simplelist" border="0" summary="Simple list"><tr><td><a class="indexterm" name="id333935"></a><em class="parameter"><code>security = domain</code></em></td></tr></table><p>
     429</p><table class="simplelist" border="0" summary="Simple list"><tr><td><a class="indexterm" name="id2571235"></a><em class="parameter"><code>security = domain</code></em></td></tr></table><p>
    430430Note that if the parameter <em class="parameter"><code>security = user</code></em> is used, this machine would function as a
    431431standalone server and not as a domain member server. Domain security mode causes Samba to work within the
    432432domain security context.
    433433</p><p>
    434 Next change the <a class="link" href="smb.conf.5.html#WORKGROUP">workgroup</a> line in the <em class="parameter"><code>[global]</code></em>
     434Next change the <a class="link" href="smb.conf.5.html#WORKGROUP" target="_top">workgroup</a> line in the <em class="parameter"><code>[global]</code></em>
    435435section to read:
    436 </p><table class="simplelist" border="0" summary="Simple list"><tr><td><a class="indexterm" name="id333980"></a><em class="parameter"><code>workgroup = MIDEARTH</code></em></td></tr></table><p>
     436</p><table class="simplelist" border="0" summary="Simple list"><tr><td><a class="indexterm" name="id2571283"></a><em class="parameter"><code>workgroup = MIDEARTH</code></em></td></tr></table><p>
    437437This is the name of the domain we are joining.
    438438</p><p>
    439 <a class="indexterm" name="id333995"></a>
    440 <a class="indexterm" name="id334002"></a>
    441 You must also have the parameter <a class="link" href="smb.conf.5.html#ENCRYPTPASSWORDS">encrypt passwords</a>
     439<a class="indexterm" name="id2571299"></a>
     440<a class="indexterm" name="id2571306"></a>
     441You must also have the parameter <a class="link" href="smb.conf.5.html#ENCRYPTPASSWORDS" target="_top">encrypt passwords</a>
    442442set to <code class="constant">yes</code> in order for your users to authenticate to the NT PDC.
    443443This is the default setting if this parameter is not specified. There is no need to specify this
    444444parameter, but if it is specified in the <code class="filename">smb.conf</code> file, it must be set to <code class="constant">Yes</code>.
    445445</p><p>
    446 <a class="indexterm" name="id334038"></a>
    447 <a class="indexterm" name="id334044"></a>
    448 <a class="indexterm" name="id334051"></a>
    449 <a class="indexterm" name="id334058"></a>
    450 Finally, add (or modify) a <a class="link" href="smb.conf.5.html#PASSWORDSERVER">password server</a> line in the [global]
     446<a class="indexterm" name="id2571345"></a>
     447<a class="indexterm" name="id2571351"></a>
     448<a class="indexterm" name="id2571358"></a>
     449<a class="indexterm" name="id2571365"></a>
     450Finally, add (or modify) a <a class="link" href="smb.conf.5.html#PASSWORDSERVER" target="_top">password server</a> line in the [global]
    451451section to read:
    452 </p><table class="simplelist" border="0" summary="Simple list"><tr><td><a class="indexterm" name="id334081"></a><em class="parameter"><code>password server = DOMPDC DOMBDC1 DOMBDC2</code></em></td></tr></table><p>
     452</p><table class="simplelist" border="0" summary="Simple list"><tr><td><a class="indexterm" name="id2571389"></a><em class="parameter"><code>password server = DOMPDC DOMBDC1 DOMBDC2</code></em></td></tr></table><p>
    453453These are the PDC and BDCs Samba
    454454will attempt to contact in order to authenticate users. Samba will
    … …  
    457457among Domain Controllers.
    458458</p><p>
    459 <a class="indexterm" name="id334098"></a>
    460 <a class="indexterm" name="id334105"></a>
    461 <a class="indexterm" name="id334112"></a>
    462 <a class="indexterm" name="id334119"></a>
     459<a class="indexterm" name="id2571409"></a>
     460<a class="indexterm" name="id2571416"></a>
     461<a class="indexterm" name="id2571423"></a>
     462<a class="indexterm" name="id2571430"></a>
    463463Alternatively, if you want smbd to determine automatically the list of domain controllers to use for
    464464authentication, you may set this line to be:
    465 </p><table class="simplelist" border="0" summary="Simple list"><tr><td><a class="indexterm" name="id334133"></a><em class="parameter"><code>password server = *</code></em></td></tr></table><p>
    466 <a class="indexterm" name="id334144"></a>
     465</p><table class="simplelist" border="0" summary="Simple list"><tr><td><a class="indexterm" name="id2571445"></a><em class="parameter"><code>password server = *</code></em></td></tr></table><p>
     466<a class="indexterm" name="id2571457"></a>
    467467This method allows Samba to use exactly the same mechanism that NT does. The
    468468method either uses broadcast-based name resolution, performs a WINS database
    … …  
    471471</p><p>
    472472To join the domain, run this command:
    473 <a class="indexterm" name="id334157"></a>
     473<a class="indexterm" name="id2571472"></a>
    474474</p><pre class="screen">
    475475<code class="prompt">root# </code><strong class="userinput"><code>net rpc join -S DOMPDC -U<em class="replaceable"><code>Administrator%password</code></em></code></strong>
    476476</pre><p>
    477477</p><p>
    478 <a class="indexterm" name="id334190"></a>
    479 <a class="indexterm" name="id334197"></a>
    480 <a class="indexterm" name="id334203"></a>
    481 <a class="indexterm" name="id334210"></a>
     478<a class="indexterm" name="id2571506"></a>
     479<a class="indexterm" name="id2571513"></a>
     480<a class="indexterm" name="id2571519"></a>
     481<a class="indexterm" name="id2571526"></a>
    482482If the <code class="option">-S DOMPDC</code> argument is not given, the domain name will be obtained from <code class="filename">smb.conf</code> and
    483483the NetBIOS name of the PDC will be obtained either using a WINS lookup or via NetBIOS broadcast based name
    484484look up.
    485485</p><p>
    486 <a class="indexterm" name="id334231"></a>
    487 <a class="indexterm" name="id334238"></a>
    488 <a class="indexterm" name="id334245"></a>
    489 <a class="indexterm" name="id334251"></a>
     486<a class="indexterm" name="id2571549"></a>
     487<a class="indexterm" name="id2571556"></a>
     488<a class="indexterm" name="id2571562"></a>
     489<a class="indexterm" name="id2571569"></a>
    490490The machine is joining the domain DOM, and the PDC for that domain (the only machine
    491491that has write access to the domain SAM database) is DOMPDC; therefore, use the <code class="option">-S</code>
    … …  
    498498</pre><p>
    499499</p><p>
    500 <a class="indexterm" name="id334283"></a>
    501 <a class="indexterm" name="id334294"></a>
    502 <a class="indexterm" name="id334301"></a>
     500<a class="indexterm" name="id2571606"></a>
     501<a class="indexterm" name="id2571617"></a>
     502<a class="indexterm" name="id2571624"></a>
    503503Where Active Directory is used, the command used to join the ADS domain is:
    504504</p><pre class="screen">
    … …  
    513513administration</a> for further information.
    514514</p><p>
    515 <a class="indexterm" name="id334355"></a>
    516 <a class="indexterm" name="id334362"></a>
    517 <a class="indexterm" name="id334369"></a>
     515<a class="indexterm" name="id2571681"></a>
     516<a class="indexterm" name="id2571688"></a>
     517<a class="indexterm" name="id2571695"></a>
    518518This process joins the server to the domain without separately having to create the machine
    519519trust account on the PDC beforehand.
    520520</p><p>
    521 <a class="indexterm" name="id334380"></a>
    522 <a class="indexterm" name="id334389"></a>
    523 <a class="indexterm" name="id334396"></a>
    524 <a class="indexterm" name="id334403"></a>
     521<a class="indexterm" name="id2571707"></a>
     522<a class="indexterm" name="id2571717"></a>
     523<a class="indexterm" name="id2571724"></a>
     524<a class="indexterm" name="id2571731"></a>
    525525This command goes through the machine account password change protocol, then writes the new (random) machine
    526526account password for this Samba server into a file in the same directory in which a smbpasswd file would be
    … …  
    528528<code class="filename">/usr/local/samba/private/secrets.tdb</code> or <code class="filename">/etc/samba/secrets.tdb</code>.
    529529</p><p>
    530 <a class="indexterm" name="id334428"></a>
    531 <a class="indexterm" name="id334434"></a>
     530<a class="indexterm" name="id2571760"></a>
     531<a class="indexterm" name="id2571767"></a>
    532532This file is created and owned by root and is not readable by any other user. It is
    533533the key to the domain-level security for your system and should be treated as carefully
    534534as a shadow password file.
    535535</p><p>
    536 <a class="indexterm" name="id334446"></a>
    537 <a class="indexterm" name="id334453"></a>
    538 <a class="indexterm" name="id334460"></a>
     536<a class="indexterm" name="id2571780"></a>
     537<a class="indexterm" name="id2571787"></a>
     538<a class="indexterm" name="id2571794"></a>
    539539Finally, restart your Samba daemons and get ready for clients to begin using domain
    540540security. The way you can restart your Samba daemons depends on your distribution,
    … …  
    543543<code class="prompt">root# </code>/etc/init.d/samba restart
    544544</pre><p>
    545 </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id334482"></a>Why Is This Better Than <em class="parameter"><code>security = server</code></em>?</h3></div></div></div><p>
    546 <a class="indexterm" name="id334496"></a>
    547 <a class="indexterm" name="id334503"></a>
    548 <a class="indexterm" name="id334509"></a>
     545</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2571819"></a>Why Is This Better Than <em class="parameter"><code>security = server</code></em>?</h3></div></div></div><p>
     546<a class="indexterm" name="id2571833"></a>
     547<a class="indexterm" name="id2571840"></a>
     548<a class="indexterm" name="id2571847"></a>
    549549Currently, domain security in Samba does not free you from having to create local UNIX users to represent the
    550550users attaching to your server. This means that if domain user <code class="constant">DOM\fred</code> attaches to your
    551551domain security Samba server, there needs to be a local UNIX user fred to represent that user in the UNIX file
    552 system. This is similar to the older Samba security mode <a class="link" href="smb.conf.5.html#SECURITY">security = server</a>, where Samba would pass through the authentication request to a Windows
     552system. This is similar to the older Samba security mode <a class="link" href="smb.conf.5.html#SECURITY" target="_top">security = server</a>, where Samba would pass through the authentication request to a Windows
    553553NT server in the same way as a Windows 95 or Windows 98 server would.
    554554</p><p>
    555 <a class="indexterm" name="id334538"></a>
    556 <a class="indexterm" name="id334545"></a>
    557 <a class="indexterm" name="id334551"></a>
     555<a class="indexterm" name="id2571881"></a>
     556<a class="indexterm" name="id2571887"></a>
     557<a class="indexterm" name="id2571894"></a>
    558558Please refer to <a class="link" href="winbind.html" title="Chapter 24. Winbind: Use of Domain Accounts">Winbind: Use of Domain Accounts</a>, for information on a system
    559559to automatically assign UNIX UIDs and GIDs to Windows NT domain users and groups.
    560560</p><p>
    561 <a class="indexterm" name="id334569"></a>
    562 <a class="indexterm" name="id334576"></a>
    563 <a class="indexterm" name="id334583"></a>
     561<a class="indexterm" name="id2571913"></a>
     562<a class="indexterm" name="id2571920"></a>
     563<a class="indexterm" name="id2571927"></a>
    564564The advantage of domain-level security is that the authentication in domain-level security is passed down the
    565565authenticated RPC channel in exactly the same way that an NT server would do it. This means Samba servers now
    … …  
    568568domain PDC).
    569569</p><p>
    570 <a class="indexterm" name="id334596"></a>
    571 <a class="indexterm" name="id334603"></a>
    572 <a class="indexterm" name="id334610"></a>
    573 In addition, with <a class="link" href="smb.conf.5.html#SECURITY">security = server</a>, every Samba daemon on a server has to
     570<a class="indexterm" name="id2571945"></a>
     571<a class="indexterm" name="id2571951"></a>
     572<a class="indexterm" name="id2571958"></a>
     573In addition, with <a class="link" href="smb.conf.5.html#SECURITY" target="_top">security = server</a>, every Samba daemon on a server has to
    574574keep a connection open to the authenticating server for as long as that daemon lasts. This can drain the
    575575connection resources on a Microsoft NT server and cause it to run out of available connections. With
    576 <a class="link" href="smb.conf.5.html#SECURITY">security = domain</a>, however, the Samba daemons connect to the PDC or BDC
     576<a class="link" href="smb.conf.5.html#SECURITY" target="_top">security = domain</a>, however, the Samba daemons connect to the PDC or BDC
    577577only for as long as is necessary to authenticate the user and then drop the connection, thus conserving PDC
    578578connection resources.
    579579</p><p>
    580 <a class="indexterm" name="id334644"></a>
    581 <a class="indexterm" name="id334651"></a>
    582 <a class="indexterm" name="id334658"></a>
    583 <a class="indexterm" name="id334664"></a>
     580<a class="indexterm" name="id2571998"></a>
     581<a class="indexterm" name="id2572004"></a>
     582<a class="indexterm" name="id2572011"></a>
     583<a class="indexterm" name="id2572018"></a>
    584584Finally, acting in the same manner as an NT server authenticating to a PDC means that as part of the
    585585authentication reply, the Samba server gets the user identification information such as the user SID, the list
    … …  
    590590<span class="emphasis"><em>Doing the NIS/NT Samba</em></span>.
    591591</p></div></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="ads-member"></a>Samba ADS Domain Membership</h2></div></div></div><p>
    592 <a class="indexterm" name="id334711"></a>
    593 <a class="indexterm" name="id334717"></a>
    594 <a class="indexterm" name="id334726"></a>
    595 <a class="indexterm" name="id334733"></a>
     592<a class="indexterm" name="id2572068"></a>
     593<a class="indexterm" name="id2572074"></a>
     594<a class="indexterm" name="id2572084"></a>
     595<a class="indexterm" name="id2572090"></a>
    596596This is a rough guide to setting up Samba-3 with Kerberos authentication against a
    597597Windows 200x KDC. A familiarity with Kerberos is assumed.
    598 </p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id334742"></a>Configure <code class="filename">smb.conf</code></h3></div></div></div><p>
     598</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2572101"></a>Configure <code class="filename">smb.conf</code></h3></div></div></div><p>
    599599You must use at least the following three options in <code class="filename">smb.conf</code>:
    600 </p><table class="simplelist" border="0" summary="Simple list"><tr><td><a class="indexterm" name="id334767"></a><em class="parameter"><code>realm = your.kerberos.REALM</code></em></td></tr><tr><td><a class="indexterm" name="id334779"></a><em class="parameter"><code>security = ADS</code></em></td></tr><tr><td># The following parameter need only be specified if present.</td></tr><tr><td># The default setting if not present is Yes.</td></tr><tr><td><a class="indexterm" name="id334798"></a><em class="parameter"><code>encrypt passwords = yes</code></em></td></tr></table><p>
    601 <a class="indexterm" name="id334812"></a>
    602 <a class="indexterm" name="id334818"></a>
    603 <a class="indexterm" name="id334825"></a>
    604 <a class="indexterm" name="id334832"></a>
    605 <a class="indexterm" name="id334838"></a>
     600</p><table class="simplelist" border="0" summary="Simple list"><tr><td><a class="indexterm" name="id2572127"></a><em class="parameter"><code>realm = your.kerberos.REALM</code></em></td></tr><tr><td><a class="indexterm" name="id2572138"></a><em class="parameter"><code>security = ADS</code></em></td></tr><tr><td># The following parameter need only be specified if present.</td></tr><tr><td># The default setting if not present is Yes.</td></tr><tr><td><a class="indexterm" name="id2572158"></a><em class="parameter"><code>encrypt passwords = yes</code></em></td></tr></table><p>
     601<a class="indexterm" name="id2572172"></a>
     602<a class="indexterm" name="id2572179"></a>
     603<a class="indexterm" name="id2572186"></a>
     604<a class="indexterm" name="id2572192"></a>
     605<a class="indexterm" name="id2572199"></a>
    606606In case samba cannot correctly identify the appropriate ADS server using the realm name, use the
    607 <a class="link" href="smb.conf.5.html#PASSWORDSERVER">password server</a> option in <code class="filename">smb.conf</code>:
    608 </p><table class="simplelist" border="0" summary="Simple list"><tr><td><a class="indexterm" name="id334868"></a><em class="parameter"><code>password server = your.kerberos.server</code></em></td></tr></table><p>
     607<a class="link" href="smb.conf.5.html#PASSWORDSERVER" target="_top">password server</a> option in <code class="filename">smb.conf</code>:
     608</p><table class="simplelist" border="0" summary="Simple list"><tr><td><a class="indexterm" name="id2572230"></a><em class="parameter"><code>password server = your.kerberos.server</code></em></td></tr></table><p>
    609609The most common reason for which Samba may not be able to locate the ADS domain controller is a consequence of
    610610sites maintaining some DNS servers on UNIX systems without regard for the DNS requirements of the ADS
    … …  
    612612server</code></em>.
    613613</p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
    614 <a class="indexterm" name="id334892"></a>
    615 <a class="indexterm" name="id334899"></a>
     614<a class="indexterm" name="id2572257"></a>
     615<a class="indexterm" name="id2572264"></a>
    616616You do <span class="emphasis"><em>not</em></span> need an smbpasswd file, and older clients will be authenticated as
    617 if <a class="link" href="smb.conf.5.html#SECURITY">security = domain</a>, although it will not do any harm and
     617if <a class="link" href="smb.conf.5.html#SECURITY" target="_top">security = domain</a>, although it will not do any harm and
    618618allows you to have local users not in the domain.
    619 </p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id334924"></a>Configure <code class="filename">/etc/krb5.conf</code></h3></div></div></div><p>
    620 <a class="indexterm" name="id334936"></a>
    621 <a class="indexterm" name="id334943"></a>
    622 <a class="indexterm" name="id334952"></a>
    623 <a class="indexterm" name="id334959"></a>
     619</p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2572292"></a>Configure <code class="filename">/etc/krb5.conf</code></h3></div></div></div><p>
     620<a class="indexterm" name="id2572304"></a>
     621<a class="indexterm" name="id2572310"></a>
     622<a class="indexterm" name="id2572320"></a>
     623<a class="indexterm" name="id2572327"></a>
    624624With both MIT and Heimdal Kerberos, it is unnecessary to configure the <code class="filename">/etc/krb5.conf</code>,
    625625and it may be detrimental.
    626626</p><p>
    627 <a class="indexterm" name="id334976"></a>
    628 <a class="indexterm" name="id334982"></a>
    629 <a class="indexterm" name="id334989"></a>
    630 <a class="indexterm" name="id334996"></a>
    631 <a class="indexterm" name="id335002"></a>
     627<a class="indexterm" name="id2572345"></a>
     628<a class="indexterm" name="id2572351"></a>
     629<a class="indexterm" name="id2572358"></a>
     630<a class="indexterm" name="id2572365"></a>
     631<a class="indexterm" name="id2572371"></a>
    632632Microsoft ADS automatically create SRV records in the DNS zone
    633633<em class="parameter"><code>_kerberos._tcp.REALM.NAME</code></em> for each KDC in the realm. This is part
    … …  
    636636active directory infrastructure.
    637637</p><p>
    638 <a class="indexterm" name="id335021"></a>
    639 <a class="indexterm" name="id335028"></a>
    640 <a class="indexterm" name="id335035"></a>
    641 <a class="indexterm" name="id335042"></a>
    642 <a class="indexterm" name="id335048"></a>
    643 <a class="indexterm" name="id335055"></a>
     638<a class="indexterm" name="id2572393"></a>
     639<a class="indexterm" name="id2572400"></a>
     640<a class="indexterm" name="id2572407"></a>
     641<a class="indexterm" name="id2572413"></a>
     642<a class="indexterm" name="id2572420"></a>
     643<a class="indexterm" name="id2572427"></a>
    644644UNIX systems can use kinit and the DES-CBC-MD5 or DES-CBC-CRC encryption types to authenticate to the Windows
    6456452000 KDC. For further information regarding Windows 2000 ADS kerberos interoperability please refer to the
    … …  
    649649explains much of the magic behind the operation of Kerberos.
    650650</p><p>
    651 <a class="indexterm" name="id335082"></a>
    652 <a class="indexterm" name="id335088"></a>
    653 <a class="indexterm" name="id335095"></a>
    654 <a class="indexterm" name="id335102"></a>
    655 <a class="indexterm" name="id335109"></a>
    656 <a class="indexterm" name="id335115"></a>
     651<a class="indexterm" name="id2572459"></a>
     652<a class="indexterm" name="id2572465"></a>
     653<a class="indexterm" name="id2572472"></a>
     654<a class="indexterm" name="id2572479"></a>
     655<a class="indexterm" name="id2572486"></a>
     656<a class="indexterm" name="id2572492"></a>
    657657MIT's, as well as Heimdal's, recent KRB5 libraries default to checking for SRV records, so they will
    658658automatically find the KDCs. In addition, <code class="filename">krb5.conf</code> only allows specifying
    … …  
    660660libraries to use whichever KDCs are available.
    661661</p><p>
    662 <a class="indexterm" name="id335134"></a>
     662<a class="indexterm" name="id2572514"></a>
    663663When manually configuring <code class="filename">krb5.conf</code>, the minimal configuration is:
    664664</p><pre class="screen">
    … …  
    675675</pre><p>
    676676</p><p>
    677 <a class="indexterm" name="id335158"></a>
     677<a class="indexterm" name="id2572539"></a>
    678678When using Heimdal versions before 0.6, use the following configuration settings:
    679679</p><pre class="screen">
    … …  
    692692</pre><p>
    693693</p><p>
    694 <a class="indexterm" name="id335176"></a>
    695 <a class="indexterm" name="id335183"></a>
     694<a class="indexterm" name="id2572561"></a>
     695<a class="indexterm" name="id2572568"></a>
    696696Test your config by doing a <strong class="userinput"><code>kinit
    697697<em class="replaceable"><code>USERNAME</code></em>@<em class="replaceable"><code>REALM</code></em></code></strong> and
    698698making sure that your password is accepted by the Win2000 KDC.
    699699</p><p>
    700 <a class="indexterm" name="id335206"></a>
    701 <a class="indexterm" name="id335212"></a>
    702 <a class="indexterm" name="id335219"></a>
    703 <a class="indexterm" name="id335225"></a>
     700<a class="indexterm" name="id2572591"></a>
     701<a class="indexterm" name="id2572598"></a>
     702<a class="indexterm" name="id2572605"></a>
     703<a class="indexterm" name="id2572611"></a>
    704704With Heimdal versions earlier than 0.6.x you can use only newly created accounts
    705705in ADS or accounts that have had the password changed once after migration, or
    … …  
    709709in a state of flux.
    710710</p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
    711 <a class="indexterm" name="id335243"></a>
    712 <a class="indexterm" name="id335250"></a>
    713 <a class="indexterm" name="id335257"></a>
     711<a class="indexterm" name="id2572633"></a>
     712<a class="indexterm" name="id2572640"></a>
     713<a class="indexterm" name="id2572646"></a>
    714714The realm must be in uppercase or you will get a &#8220;<span class="quote"><span class="errorname">Cannot find KDC for
    715715requested realm while getting initial credentials</span></span>&#8221; error (Kerberos
    716716is case-sensitive!).
    717717</p></div><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
    718 <a class="indexterm" name="id335274"></a>
    719 <a class="indexterm" name="id335280"></a>
    720 <a class="indexterm" name="id335287"></a>
    721 <a class="indexterm" name="id335294"></a>
     718<a class="indexterm" name="id2572664"></a>
     719<a class="indexterm" name="id2572670"></a>
     720<a class="indexterm" name="id2572677"></a>
     721<a class="indexterm" name="id2572684"></a>
    722722Time between the two servers must be synchronized. You will get a &#8220;<span class="quote"><span class="errorname">kinit(v5): Clock skew too
    723723great while getting initial credentials</span></span>&#8221; if the time difference (clock skew) is more than five minutes.
    724724</p></div><p>
    725 <a class="indexterm" name="id335310"></a>
    726 <a class="indexterm" name="id335317"></a>
     725<a class="indexterm" name="id2572702"></a>
     726<a class="indexterm" name="id2572709"></a>
    727727Clock skew limits are configurable in the Kerberos protocols. The default setting is five minutes.
    728728</p><p>
    729 <a class="indexterm" name="id335328"></a>
    730 <a class="indexterm" name="id335335"></a>
    731 <a class="indexterm" name="id335341"></a>
    732 <a class="indexterm" name="id335348"></a>
     729<a class="indexterm" name="id2572721"></a>
     730<a class="indexterm" name="id2572727"></a>
     731<a class="indexterm" name="id2572734"></a>
     732<a class="indexterm" name="id2572741"></a>
    733733You also must ensure that you can do a reverse DNS lookup on the IP address of your KDC. Also, the name that
    734734this reverse lookup maps to must either be the NetBIOS name of the KDC (i.e., the hostname with no domain
    735735attached) or it can be the NetBIOS name followed by the realm.
    736736</p><p>
    737 <a class="indexterm" name="id335360"></a>
    738 <a class="indexterm" name="id335367"></a>
    739 <a class="indexterm" name="id335374"></a>
     737<a class="indexterm" name="id2572755"></a>
     738<a class="indexterm" name="id2572762"></a>
     739<a class="indexterm" name="id2572769"></a>
    740740The easiest way to ensure you get this right is to add a <code class="filename">/etc/hosts</code> entry mapping the IP
    741741address of your KDC to its NetBIOS name. If you do not get this correct, then you will get a <span class="errorname">local
    742742error</span> when you try to join the realm.
    743743</p><p>
    744 <a class="indexterm" name="id335395"></a>
    745 <a class="indexterm" name="id335402"></a>
    746 <a class="indexterm" name="id335409"></a>
    747 <a class="indexterm" name="id335416"></a>
     744<a class="indexterm" name="id2572792"></a>
     745<a class="indexterm" name="id2572798"></a>
     746<a class="indexterm" name="id2572806"></a>
     747<a class="indexterm" name="id2572813"></a>
    748748If all you want is Kerberos support in <span class="application">smbclient</span>, then you can skip directly to <a class="link" href="domain-member.html#ads-test-smbclient" title="Testing with smbclient">Testing with <span class="application">smbclient</span></a> now.  <a class="link" href="domain-member.html#ads-create-machine-account" title="Create the Computer Account">Create the Computer Account</a> and <a class="link" href="domain-member.html#ads-test-server" title="Testing Server Setup">Testing Server Setup</a> are needed only if you want Kerberos support for <span class="application">smbd</span>
    749749and <span class="application">winbindd</span>.
    750750</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="ads-create-machine-account"></a>Create the Computer Account</h3></div></div></div><p>
    751 <a class="indexterm" name="id335481"></a>
    752 <a class="indexterm" name="id335488"></a>
    753 <a class="indexterm" name="id335495"></a>
    754 <a class="indexterm" name="id335502"></a>
     751<a class="indexterm" name="id2572883"></a>
     752<a class="indexterm" name="id2572890"></a>
     753<a class="indexterm" name="id2572897"></a>
     754<a class="indexterm" name="id2572904"></a>
    755755As a user who has write permission on the Samba private directory (usually root), run:
    756756</p><pre class="screen">
    … …  
    761761On the UNIX/Linux system, this command must be executed by an account that has UID=0 (root).
    762762</p><p>
    763 <a class="indexterm" name="id335532"></a>
    764 <a class="indexterm" name="id335539"></a>
    765 <a class="indexterm" name="id335546"></a>
    766 <a class="indexterm" name="id335552"></a>
    767 <a class="indexterm" name="id335559"></a>
    768 <a class="indexterm" name="id335566"></a>
     763<a class="indexterm" name="id2572938"></a>
     764<a class="indexterm" name="id2572945"></a>
     765<a class="indexterm" name="id2572952"></a>
     766<a class="indexterm" name="id2572959"></a>
     767<a class="indexterm" name="id2572966"></a>
     768<a class="indexterm" name="id2572972"></a>
    769769When making a Windows client a member of an ADS domain within a complex organization, you
    770770may want to create the machine trust account within a particular organizational unit. Samba-3 permits
    … …  
    776776Your ADS manager will be able to advise what should be specified for the "organizational_unit" parameter.
    777777</p><p>
    778 <a class="indexterm" name="id335612"></a>
    779 <a class="indexterm" name="id335619"></a>
    780 <a class="indexterm" name="id335626"></a>
    781 <a class="indexterm" name="id335633"></a>
     778<a class="indexterm" name="id2573022"></a>
     779<a class="indexterm" name="id2573030"></a>
     780<a class="indexterm" name="id2573037"></a>
     781<a class="indexterm" name="id2573043"></a>
    782782For example, you may want to create the machine trust account in a container called &#8220;<span class="quote">Servers</span>&#8221;
    783783under the organizational directory &#8220;<span class="quote">Computers/BusinessUnit/Department,</span>&#8221; like this:
    … …  
    790790valid characters in an OU name and used as escapes for other characters.  If you need a backslash in an OU
    791791name, it may need to be quadrupled to pass through the shell escape and ldap escape.
    792 </p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id335676"></a>Possible Errors</h4></div></div></div><p>
     792</p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2573093"></a>Possible Errors</h4></div></div></div><p>
    793793</p><div class="variablelist"><dl><dt><span class="term"><span class="errorname">ADS support not compiled in</span></span></dt><dd><p>
    794         <a class="indexterm" name="id335695"></a>
    795         <a class="indexterm" name="id335702"></a>
    796         <a class="indexterm" name="id335708"></a>
     794        <a class="indexterm" name="id2573112"></a>
     795        <a class="indexterm" name="id2573119"></a>
     796        <a class="indexterm" name="id2573126"></a>
    797797        Samba must be reconfigured (remove config.cache) and recompiled (make clean all install) after the
    798798        Kerberos libraries and headers files are installed.
    799799        </p></dd><dt><span class="term"><span class="errorname">net ads join prompts for user name</span></span></dt><dd><p>
    800         <a class="indexterm" name="id335727"></a>
    801         <a class="indexterm" name="id335734"></a>
     800        <a class="indexterm" name="id2573145"></a>
     801        <a class="indexterm" name="id2573152"></a>
    802802        You need to log in to the domain using <strong class="userinput"><code>kinit
    803803        <em class="replaceable"><code>USERNAME</code></em>@<em class="replaceable"><code>REALM</code></em></code></strong>.
    804804        <em class="replaceable"><code>USERNAME</code></em> must be a user who has rights to add a machine to the domain.
    805805        </p></dd><dt><span class="term">Unsupported encryption/or checksum types</span></dt><dd><p>
    806         <a class="indexterm" name="id335766"></a>
    807         <a class="indexterm" name="id335772"></a>
    808         <a class="indexterm" name="id335779"></a>
     806        <a class="indexterm" name="id2573185"></a>
     807        <a class="indexterm" name="id2573192"></a>
     808        <a class="indexterm" name="id2573199"></a>
    809809        Make sure that the <code class="filename">/etc/krb5.conf</code> is correctly configured
    810810        for the type and version of Kerberos installed on the system.
    811811        </p></dd></dl></div><p>
    812812</p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="ads-test-server"></a>Testing Server Setup</h3></div></div></div><p>
    813 <a class="indexterm" name="id335809"></a>
    814 <a class="indexterm" name="id335816"></a>
    815 <a class="indexterm" name="id335823"></a>
     813<a class="indexterm" name="id2573231"></a>
     814<a class="indexterm" name="id2573238"></a>
     815<a class="indexterm" name="id2573245"></a>
    816816If the join was successful, you will see a new computer account with the
    817817NetBIOS name of your Samba server in Active Directory (in the &#8220;<span class="quote">Computers</span>&#8221;
    818818folder under Users and Computers.
    819819</p><p>
    820 <a class="indexterm" name="id335838"></a>
    821 <a class="indexterm" name="id335844"></a>
    822 <a class="indexterm" name="id335853"></a>
     820<a class="indexterm" name="id2573261"></a>
     821<a class="indexterm" name="id2573268"></a>
     822<a class="indexterm" name="id2573277"></a>
    823823On a Windows 2000 client, try <strong class="userinput"><code>net use * \\server\share</code></strong>. You should
    824824be logged in with Kerberos without needing to know a password. If this fails, then run
    … …  
    826826an encryption type of DES-CBC-MD5?
    827827</p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
    828 <a class="indexterm" name="id335878"></a>
    829 <a class="indexterm" name="id335885"></a>
    830 <a class="indexterm" name="id335892"></a>
     828<a class="indexterm" name="id2573304"></a>
     829<a class="indexterm" name="id2573311"></a>
     830<a class="indexterm" name="id2573318"></a>
    831831Samba can use both DES-CBC-MD5 encryption as well as ARCFOUR-HMAC-MD5 encoding.
    832832</p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="ads-test-smbclient"></a>Testing with <span class="application">smbclient</span></h3></div></div></div><p>
    833 <a class="indexterm" name="id335917"></a>
    834 <a class="indexterm" name="id335924"></a>
    835 <a class="indexterm" name="id335931"></a>
     833<a class="indexterm" name="id2573345"></a>
     834<a class="indexterm" name="id2573351"></a>
     835<a class="indexterm" name="id2573358"></a>
    836836On your Samba server try to log in to a Windows 2000 server or your Samba
    837837server using <span class="application">smbclient</span> and Kerberos. Use <span class="application">smbclient</span> as usual, but
    838838specify the <code class="option">-k</code> option to choose Kerberos authentication.
    839 </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id335956"></a>Notes</h3></div></div></div><p>
    840 <a class="indexterm" name="id335964"></a>
    841 <a class="indexterm" name="id335971"></a>
    842 <a class="indexterm" name="id335978"></a>
     839</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2573386"></a>Notes</h3></div></div></div><p>
     840<a class="indexterm" name="id2573394"></a>
     841<a class="indexterm" name="id2573401"></a>
     842<a class="indexterm" name="id2573408"></a>
    843843You must change the administrator password at least once after installing a domain controller,
    844844to create the right encryption types.
    845845</p><p>
    846 <a class="indexterm" name="id335989"></a>
    847 <a class="indexterm" name="id335996"></a>
    848 <a class="indexterm" name="id336003"></a>
     846<a class="indexterm" name="id2573420"></a>
     847<a class="indexterm" name="id2573427"></a>
     848<a class="indexterm" name="id2573434"></a>
    849849Windows 200x does not seem to create the <em class="parameter"><code>_kerberos._udp</code></em> and
    850850<em class="parameter"><code>_ldap._tcp</code></em> in the default DNS setup. Perhaps this will be fixed later in service packs.
    851 </p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id336026"></a>Sharing User ID Mappings between Samba Domain Members</h2></div></div></div><p>
    852 <a class="indexterm" name="id336034"></a>
    853 <a class="indexterm" name="id336041"></a>
    854 <a class="indexterm" name="id336047"></a>
    855 <a class="indexterm" name="id336054"></a>
     851</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2573458"></a>Sharing User ID Mappings between Samba Domain Members</h2></div></div></div><p>
     852<a class="indexterm" name="id2573467"></a>
     853<a class="indexterm" name="id2573474"></a>
     854<a class="indexterm" name="id2573480"></a>
     855<a class="indexterm" name="id2573487"></a>
    856856Samba maps UNIX users and groups (identified by UIDs and GIDs) to Windows users and groups (identified by SIDs).
    857857These mappings are done by the <em class="parameter"><code>idmap</code></em> subsystem of Samba.
    858858</p><p>
    859 <a class="indexterm" name="id336071"></a>
    860 <a class="indexterm" name="id336078"></a>
    861 <a class="indexterm" name="id336084"></a>
     859<a class="indexterm" name="id2573505"></a>
     860<a class="indexterm" name="id2573512"></a>
     861<a class="indexterm" name="id2573519"></a>
    862862In some cases it is useful to share these mappings between Samba domain members,
    863863so <span class="emphasis"><em>name-&gt;id</em></span> mapping is identical on all machines.
    864864This may be needed in particular when sharing files over both CIFS and NFS.
    865865</p><p>
    866 <a class="indexterm" name="id336100"></a>
    867 <a class="indexterm" name="id336106"></a>
     866<a class="indexterm" name="id2573536"></a>
     867<a class="indexterm" name="id2573543"></a>
    868868To use the <span class="emphasis"><em>LDAP</em></span> <em class="parameter"><code>ldap idmap suffix</code></em>, set:
    869 </p><table class="simplelist" border="0" summary="Simple list"><tr><td><a class="indexterm" name="id336130"></a><em class="parameter"><code>ldap idmap suffix = ou=Idmap</code></em></td></tr></table><p>
    870 See the <code class="filename">smb.conf</code> man page entry for the <a class="link" href="smb.conf.5.html#LDAPIDMAPSUFFIX">ldap idmap suffix</a>
     869</p><table class="simplelist" border="0" summary="Simple list"><tr><td><a class="indexterm" name="id2573566"></a><em class="parameter"><code>ldap idmap suffix = ou=Idmap</code></em></td></tr></table><p>
     870See the <code class="filename">smb.conf</code> man page entry for the <a class="link" href="smb.conf.5.html#LDAPIDMAPSUFFIX" target="_top">ldap idmap suffix</a>
    871871parameter for further information.
    872872</p><p>
    873 <a class="indexterm" name="id336164"></a>
    874 <a class="indexterm" name="id336170"></a>
    875 <a class="indexterm" name="id336177"></a>
    876 Do not forget to specify also the <a class="link" href="smb.conf.5.html#LDAPADMINDN">ldap admin dn</a>
     873<a class="indexterm" name="id2573603"></a>
     874<a class="indexterm" name="id2573609"></a>
     875<a class="indexterm" name="id2573616"></a>
     876Do not forget to specify also the <a class="link" href="smb.conf.5.html#LDAPADMINDN" target="_top">ldap admin dn</a>
    877877and to make certain to set the LDAP administrative password into the <code class="filename">secrets.tdb</code> using:
    878878</p><pre class="screen">
    … …  
    881881In place of <code class="literal">ldap-admin-password</code>, substitute the LDAP administration password for your
    882882system.
    883 </p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id336222"></a>Common Errors</h2></div></div></div><p>
    884 <a class="indexterm" name="id336230"></a>
    885 <a class="indexterm" name="id336236"></a>
     883</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2573664"></a>Common Errors</h2></div></div></div><p>
     884<a class="indexterm" name="id2573672"></a>
     885<a class="indexterm" name="id2573679"></a>
    886886In the process of adding/deleting/re-adding domain member machine trust accounts, there are
    887887many traps for the unwary player and many &#8220;<span class="quote">little</span>&#8221; things that can go wrong.
    … …  
    891891of problem. The real solution is often quite simple, and with an understanding of how MS Windows
    892892networking functions, it is easy to overcome.
    893 </p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id336256"></a>Cannot Add Machine Back to Domain</h3></div></div></div><p>
    894 <a class="indexterm" name="id336264"></a>
    895 <a class="indexterm" name="id336271"></a>
     893</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2573704"></a>Cannot Add Machine Back to Domain</h3></div></div></div><p>
     894<a class="indexterm" name="id2573712"></a>
     895<a class="indexterm" name="id2573719"></a>
    896896&#8220;<span class="quote">A Windows workstation was reinstalled. The original domain machine trust
    897897account was deleted and added immediately. The workstation will not join the domain if I use
    … …  
    899899exists on the network  I know it does not. Why is this failing?</span>&#8221;
    900900</p><p>
    901 <a class="indexterm" name="id336290"></a>
    902 <a class="indexterm" name="id336297"></a>
     901<a class="indexterm" name="id2573741"></a>
     902<a class="indexterm" name="id2573747"></a>
    903903The original name is still in the NetBIOS name cache and must expire after machine account
    904904deletion before adding that same name as a domain member again. The best advice is to delete
    … …  
    908908<code class="prompt">C:\&gt; </code> nbtstat -R
    909909</pre><p>
    910 </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id336326"></a>Adding Machine to Domain Fails</h3></div></div></div><p>
    911 <a class="indexterm" name="id336334"></a>
    912 <a class="indexterm" name="id336340"></a>
     910</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2573780"></a>Adding Machine to Domain Fails</h3></div></div></div><p>
     911<a class="indexterm" name="id2573788"></a>
     912<a class="indexterm" name="id2573794"></a>
    913913&#8220;<span class="quote">Adding a Windows 200x or XP Professional machine to the Samba PDC Domain fails with a
    914914message that says, <span class="errorname">"The machine could not be added at this time, there is a network problem.
    915915Please try again later."</span> Why?</span>&#8221;
    916916</p><p>
    917 <a class="indexterm" name="id336359"></a>
    918 You should check that there is an <a class="link" href="smb.conf.5.html#ADDMACHINESCRIPT">add machine script</a> in your <code class="filename">smb.conf</code>
     917<a class="indexterm" name="id2573815"></a>
     918You should check that there is an <a class="link" href="smb.conf.5.html#ADDMACHINESCRIPT" target="_top">add machine script</a> in your <code class="filename">smb.conf</code>
    919919file. If there is not, please add one that is appropriate for your OS platform. If a script
    920 has been defined, you will need to debug its operation. Increase the <a class="link" href="smb.conf.5.html#LOGLEVEL">log level</a>
     920has been defined, you will need to debug its operation. Increase the <a class="link" href="smb.conf.5.html#LOGLEVEL" target="_top">log level</a>
    921921in the <code class="filename">smb.conf</code> file to level 10, then try to rejoin the domain. Check the logs to see which
    922922operation is failing.
    … …  
    924924Possible causes include:
    925925</p><div class="itemizedlist"><ul type="disc"><li><p>
    926 <a class="indexterm" name="id336412"></a>
    927 <a class="indexterm" name="id336419"></a>
     926<a class="indexterm" name="id2573873"></a>
     927<a class="indexterm" name="id2573879"></a>
    928928        The script does not actually exist, or could not be located in the path specified.
    929929        </p><p>
    930 <a class="indexterm" name="id336430"></a>
    931 <a class="indexterm" name="id336437"></a>
     930<a class="indexterm" name="id2573891"></a>
     931<a class="indexterm" name="id2573898"></a>
    932932        <span class="emphasis"><em>Corrective action:</em></span> Fix it. Make sure when run manually
    933933        that the script will add both the UNIX system account and the Samba SAM account.
    934934        </p></li><li><p>
    935 <a class="indexterm" name="id336452"></a>
    936 <a class="indexterm" name="id336459"></a>
     935<a class="indexterm" name="id2573915"></a>
     936<a class="indexterm" name="id2573922"></a>
    937937        The machine could not be added to the UNIX system accounts file <code class="filename">/etc/passwd</code>.
    938938        </p><p>
    939 <a class="indexterm" name="id336476"></a>
    940 <a class="indexterm" name="id336482"></a>
     939<a class="indexterm" name="id2573939"></a>
     940<a class="indexterm" name="id2573946"></a>
    941941        <span class="emphasis"><em>Corrective action:</em></span> Check that the machine name is a legal UNIX
    942942        system account name. If the UNIX utility <code class="literal">useradd</code> is called,
    … …  
    945945        nor will it allow spaces in the name.
    946946        </p></li></ul></div><p>
    947 <a class="indexterm" name="id336511"></a>
    948 <a class="indexterm" name="id336518"></a>
    949 <a class="indexterm" name="id336525"></a>
    950 The <a class="link" href="smb.conf.5.html#ADDMACHINESCRIPT">add machine script</a> does not create the
     947<a class="indexterm" name="id2573977"></a>
     948<a class="indexterm" name="id2573984"></a>
     949<a class="indexterm" name="id2573991"></a>
     950The <a class="link" href="smb.conf.5.html#ADDMACHINESCRIPT" target="_top">add machine script</a> does not create the
    951951machine account in the Samba backend database; it is there only to create a UNIX system
    952952account to which the Samba backend database account can be mapped.
    953 </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id336546"></a>I Can't Join a Windows 2003 PDC</h3></div></div></div><p>
    954 <a class="indexterm" name="id336554"></a>
    955 <a class="indexterm" name="id336560"></a>
    956 <a class="indexterm" name="id336567"></a>
    957 <a class="indexterm" name="id336574"></a>
     953</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2574016"></a>I Can't Join a Windows 2003 PDC</h3></div></div></div><p>
     954<a class="indexterm" name="id2574024"></a>
     955<a class="indexterm" name="id2574030"></a>
     956<a class="indexterm" name="id2574036"></a>
     957<a class="indexterm" name="id2574043"></a>
    958958        Windows 2003 requires SMB signing. Client-side SMB signing has been implemented in Samba-3.0.
    959         Set <a class="link" href="smb.conf.5.html#CLIENTUSESPNEGO">client use spnego = yes</a> when communicating
     959        Set <a class="link" href="smb.conf.5.html#CLIENTUSESPNEGO" target="_top">client use spnego = yes</a> when communicating
    960960        with a Windows 2003 server. This will not interfere with other Windows clients that do not
    961961        support the more advanced security features of Windows 2003 because the client will simply
Note: See TracChangeset for help on using the changeset viewer.