Ignore:
Timestamp:
Jun 16, 2009, 5:52:30 PM (16 years ago)
Author:
Herwig Bauernfeind
Message:

Update 3.2 to 3.2.12

File:
1 edited

Legend:

Unmodified
Added
Removed
  • branches/samba-3.2.x/docs/htmldocs/Samba3-HOWTO/domain-member.html

    r231 r272  
    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:[email protected]">[email protected]</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:[email protected]">[email protected]</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:[email protected]">[email protected]</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:[email protected]">[email protected]</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:[email protected]">[email protected]</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:[email protected]">[email protected]</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#id2569104">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#id2569791">Manual Creation of Machine Trust Accounts</a></span></dt><dt><span class="sect2"><a href="domain-member.html#id2570227">Managing Domain Machine Accounts using NT4 Server Manager</a></span></dt><dt><span class="sect2"><a href="domain-member.html#id2570508">On-the-Fly Creation of Machine Trust Accounts</a></span></dt><dt><span class="sect2"><a href="domain-member.html#id2570614">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#id2571079">Joining an NT4-type Domain with Samba-3</a></span></dt><dt><span class="sect2"><a href="domain-member.html#id2571815">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#id2572097">Configure smb.conf</a></span></dt><dt><span class="sect2"><a href="domain-member.html#id2572288">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#id2573382">Notes</a></span></dt></dl></dd><dt><span class="sect1"><a href="domain-member.html#id2573454">Sharing User ID Mappings between Samba Domain Members</a></span></dt><dt><span class="sect1"><a href="domain-member.html#id2573660">Common Errors</a></span></dt><dd><dl><dt><span class="sect2"><a href="domain-member.html#id2573700">Cannot Add Machine Back to Domain</a></span></dt><dt><span class="sect2"><a href="domain-member.html#id2573776">Adding Machine to Domain Fails</a></span></dt><dt><span class="sect2"><a href="domain-member.html#id2574012">I Can't Join a Windows 2003 PDC</a></span></dt></dl></dd></dl></div><p>
    2 <a class="indexterm" name="id2569052"></a>
    3 <a class="indexterm" name="id2569058"></a>
    4 <a class="indexterm" name="id2569066"></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:[email protected]">[email protected]</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:[email protected]">[email protected]</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:[email protected]">[email protected]</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:[email protected]">[email protected]</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:[email protected]">[email protected]</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:[email protected]">[email protected]</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#id25691">I Can't Join a Windows 2003 PDC</a></span></dt></dl></dd></dl></div><p>
     2<a class="indexterm" name="id25690"></a>
     3<a class="indexterm" name="id25690"></a>
     4<a class="indexterm" name="id25690"></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="id2569081"></a>
    11 <a class="indexterm" name="id2569088"></a>
     10<a class="indexterm" name="id25690"></a>
     11<a class="indexterm" name="id2569"></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="id2569104"></a>Features and Benefits</h2></div></div></div><p>
    20 <a class="indexterm" name="id2569112"></a>
    21 <a class="indexterm" name="id2569119"></a>
    22 <a class="indexterm" name="id2569126"></a>
     19</p><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id25691"></a>Features and Benefits</h2></div></div></div><p>
     20<a class="indexterm" name="id25691"></a>
     21<a class="indexterm" name="id25691"></a>
     22<a class="indexterm" name="id25691"></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="id2569158"></a>
    31 <a class="indexterm" name="id2569164"></a>
    32 <a class="indexterm" name="id2569171"></a>
    33 <a class="indexterm" name="id2569178"></a>
     30<a class="indexterm" name="id25691"></a>
     31<a class="indexterm" name="id25691"></a>
     32<a class="indexterm" name="id25691"></a>
     33<a class="indexterm" name="id25691"></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="id2569197"></a>
     38        <a class="indexterm" name="id2569"></a>
    3939        MS Windows workstation users get the benefit of SSO.
    4040        </p></li><li><p>
    41         <a class="indexterm" name="id2569209"></a>
    42         <a class="indexterm" name="id2569216"></a>
    43         <a class="indexterm" name="id2569223"></a>
    44         <a class="indexterm" name="id2569230"></a>
     41        <a class="indexterm" name="id25692"></a>
     42        <a class="indexterm" name="id25692"></a>
     43        <a class="indexterm" name="id25692"></a>
     44        <a class="indexterm" name="id25692"></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="id2569245"></a>
    51         <a class="indexterm" name="id2569252"></a>
     50        <a class="indexterm" name="id25692"></a>
     51        <a class="indexterm" name="id25692"></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="id2569271"></a>
    56         <a class="indexterm" name="id2569278"></a>
    57         <a class="indexterm" name="id2569285"></a>
    58         <a class="indexterm" name="id2569292"></a>
     55        <a class="indexterm" name="id25692"></a>
     56        <a class="indexterm" name="id25692"></a>
     57        <a class="indexterm" name="id2569"></a>
     58        <a class="indexterm" name="id2569"></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="id2569311"></a>
    63         <a class="indexterm" name="id2569318"></a>
    64         <a class="indexterm" name="id2569325"></a>
     62        <a class="indexterm" name="id25693"></a>
     63        <a class="indexterm" name="id25693"></a>
     64        <a class="indexterm" name="id25693"></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="id2569338"></a>
    69         <a class="indexterm" name="id2569345"></a>
    70         <a class="indexterm" name="id2569352"></a>
    71         <a class="indexterm" name="id2569359"></a>
     68        <a class="indexterm" name="id25693"></a>
     69        <a class="indexterm" name="id25693"></a>
     70        <a class="indexterm" name="id25693"></a>
     71        <a class="indexterm" name="id25693"></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="id2569387"></a>
    79 <a class="indexterm" name="id2569394"></a>
    80 <a class="indexterm" name="id2569401"></a>
    81 <a class="indexterm" name="id2569408"></a>
     78<a class="indexterm" name="id2569"></a>
     79<a class="indexterm" name="id2569"></a>
     80<a class="indexterm" name="id25694"></a>
     81<a class="indexterm" name="id25694"></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="id2569427"></a>
    88 <a class="indexterm" name="id2569436"></a>
    89 <a class="indexterm" name="id2569443"></a>
    90 <a class="indexterm" name="id2569450"></a>
    91 <a class="indexterm" name="id2569458"></a>
     87<a class="indexterm" name="id25694"></a>
     88<a class="indexterm" name="id25694"></a>
     89<a class="indexterm" name="id25694"></a>
     90<a class="indexterm" name="id25694"></a>
     91<a class="indexterm" name="id25694"></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="id2569478"></a>
    100 <a class="indexterm" name="id2569485"></a>
    101 <a class="indexterm" name="id2569492"></a>
    102 <a class="indexterm" name="id2569498"></a>
     99<a class="indexterm" name="id25694"></a>
     100<a class="indexterm" name="id2569"></a>
     101<a class="indexterm" name="id2569"></a>
     102<a class="indexterm" name="id2569"></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="id2569516"></a>
    111         <a class="indexterm" name="id2569523"></a>
    112         <a class="indexterm" name="id2569530"></a>
     110        <a class="indexterm" name="id25695"></a>
     111        <a class="indexterm" name="id25695"></a>
     112        <a class="indexterm" name="id25695"></a>
    113113        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="id2569561"></a>
    118         <a class="indexterm" name="id2569568"></a>
    119         <a class="indexterm" name="id2569575"></a>
    120         <a class="indexterm" name="id2569582"></a>
    121         <a class="indexterm" name="id2569588"></a>
    122         <a class="indexterm" name="id2569596"></a>
     117        <a class="indexterm" name="id25695"></a>
     118        <a class="indexterm" name="id25695"></a>
     119        <a class="indexterm" name="id25695"></a>
     120        <a class="indexterm" name="id2569"></a>
     121        <a class="indexterm" name="id2569"></a>
     122        <a class="indexterm" name="id2569"></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="id2569618"></a>
    129         <a class="indexterm" name="id2569624"></a>
    130         <a class="indexterm" name="id2569631"></a>
    131         <a class="indexterm" name="id2569638"></a>
     128        <a class="indexterm" name="id25696"></a>
     129        <a class="indexterm" name="id25696"></a>
     130        <a class="indexterm" name="id25696"></a>
     131        <a class="indexterm" name="id25696"></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="id2569658"></a>
    137         <a class="indexterm" name="id2569665"></a>
     136        <a class="indexterm" name="id25696"></a>
     137        <a class="indexterm" name="id25696"></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="id2569691"></a>
     143<a class="indexterm" name="id2569"></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="id2569708"></a>
     146        <a class="indexterm" name="id25697"></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="id2569721"></a>
    151         <a class="indexterm" name="id2569728"></a>
     150        <a class="indexterm" name="id25697"></a>
     151        <a class="indexterm" name="id25697"></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="id2569744"></a>
    158         <a class="indexterm" name="id2569751"></a>
     157        <a class="indexterm" name="id25697"></a>
     158        <a class="indexterm" name="id25697"></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="id2569770"></a>
    165 <a class="indexterm" name="id2569777"></a>
     164<a class="indexterm" name="id25697"></a>
     165<a class="indexterm" name="id25697"></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="id2569791"></a>Manual Creation of Machine Trust Accounts</h3></div></div></div><p>
    169 <a class="indexterm" name="id2569799"></a>
    170 <a class="indexterm" name="id2569806"></a>
    171 <a class="indexterm" name="id2569811"></a>
    172 <a class="indexterm" name="id2569818"></a>
     168</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2569"></a>Manual Creation of Machine Trust Accounts</h3></div></div></div><p>
     169<a class="indexterm" name="id2569"></a>
     170<a class="indexterm" name="id25698"></a>
     171<a class="indexterm" name="id25698"></a>
     172<a class="indexterm" name="id25698"></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="id2569887"></a>
    187 <a class="indexterm" name="id2569894"></a>
    188 <a class="indexterm" name="id2569900"></a>
     186<a class="indexterm" name="id2569"></a>
     187<a class="indexterm" name="id2569"></a>
     188<a class="indexterm" name="id25699"></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="id2569920"></a>
    194 <a class="indexterm" name="id2569927"></a>
     193<a class="indexterm" name="id25699"></a>
     194<a class="indexterm" name="id25699"></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="id2569968"></a>
    202 <a class="indexterm" name="id2569975"></a>
    203 <a class="indexterm" name="id2569982"></a>
    204 <a class="indexterm" name="id2569988"></a>
     201<a class="indexterm" name="id25699"></a>
     202<a class="indexterm" name="id25699"></a>
     203<a class="indexterm" name="id25"></a>
     204<a class="indexterm" name="id25"></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="id2570031"></a>
    214 <a class="indexterm" name="id2570038"></a>
    215 <a class="indexterm" name="id2570045"></a>
     213<a class="indexterm" name="id25700"></a>
     214<a class="indexterm" name="id25700"></a>
     215<a class="indexterm" name="id25700"></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="id2570070"></a>
    224 <a class="indexterm" name="id2570077"></a>
    225 <a class="indexterm" name="id2570084"></a>
     223<a class="indexterm" name="id25700"></a>
     224<a class="indexterm" name="id25700"></a>
     225<a class="indexterm" name="id2570"></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="id2570126"></a>
    236 <a class="indexterm" name="id2570133"></a>
    237 <a class="indexterm" name="id2570140"></a>
    238 <a class="indexterm" name="id2570146"></a>
     235<a class="indexterm" name="id25701"></a>
     236<a class="indexterm" name="id25701"></a>
     237<a class="indexterm" name="id25701"></a>
     238<a class="indexterm" name="id25701"></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="id2570168"></a>
    244 <a class="indexterm" name="id2570175"></a>
    245 <a class="indexterm" name="id2570182"></a>
    246 <a class="indexterm" name="id2570189"></a>
    247 <a class="indexterm" name="id2570196"></a>
     243<a class="indexterm" name="id25701"></a>
     244<a class="indexterm" name="id25701"></a>
     245<a class="indexterm" name="id2570"></a>
     246<a class="indexterm" name="id2570"></a>
     247<a class="indexterm" name="id2570"></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="id2570205"></a>
     250<a class="indexterm" name="id25702"></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="id2570227"></a>Managing Domain Machine Accounts using NT4 Server Manager</h3></div></div></div><p>
    258 <a class="indexterm" name="id2570236"></a>
    259 <a class="indexterm" name="id2570243"></a>
    260 <a class="indexterm" name="id2570250"></a>
     257</p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id25702"></a>Managing Domain Machine Accounts using NT4 Server Manager</h3></div></div></div><p>
     258<a class="indexterm" name="id25702"></a>
     259<a class="indexterm" name="id25702"></a>
     260<a class="indexterm" name="id25702"></a>
    261261A 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="id2570276"></a>
    266 <a class="indexterm" name="id2570283"></a>
    267 <a class="indexterm" name="id2570289"></a>
    268 <a class="indexterm" name="id2570296"></a>
     265<a class="indexterm" name="id25702"></a>
     266<a class="indexterm" name="id2570"></a>
     267<a class="indexterm" name="id2570"></a>
     268<a class="indexterm" name="id2570"></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="id2570334"></a>
    276 <a class="indexterm" name="id2570341"></a>
     275<a class="indexterm" name="id25703"></a>
     276<a class="indexterm" name="id25703"></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="id2570385"></a>
    287 <a class="indexterm" name="id2570392"></a>
     286<a class="indexterm" name="id2570"></a>
     287<a class="indexterm" name="id2570"></a>
    288288Launch the <code class="literal">srvmgr.exe</code> (Server Manager for Domains) and follow these steps:
    289 </p><div class="procedure"><a name="id2570407"></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="id25704"></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="id2570508"></a>On-the-Fly Creation of Machine Trust Accounts</h3></div></div></div><p>
    307 <a class="indexterm" name="id2570516"></a>
     306        </p></li></ol></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id25705"></a>On-the-Fly Creation of Machine Trust Accounts</h3></div></div></div><p>
     307<a class="indexterm" name="id25705"></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="id2570532"></a>
    312 <a class="indexterm" name="id2570542"></a>
    313 <a class="indexterm" name="id2570548"></a>
     311<a class="indexterm" name="id25705"></a>
     312<a class="indexterm" name="id25705"></a>
     313<a class="indexterm" name="id25705"></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="id2570570"></a>
    320 <a class="indexterm" name="id2570577"></a>
     319<a class="indexterm" name="id25705"></a>
     320<a class="indexterm" name="id25705"></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="id2570599"></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="id2570614"></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="id2570"></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="id25706"></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="id2570625"></a>Windows 200x/XP Professional Client</h4></div></div></div><p>
    327 <a class="indexterm" name="id2570633"></a>
    328 <a class="indexterm" name="id2570640"></a>
    329 <a class="indexterm" name="id2570649"></a>
    330 <a class="indexterm" name="id2570656"></a>
     326</p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id25706"></a>Windows 200x/XP Professional Client</h4></div></div></div><p>
     327<a class="indexterm" name="id25706"></a>
     328<a class="indexterm" name="id25706"></a>
     329<a class="indexterm" name="id25706"></a>
     330<a class="indexterm" name="id25706"></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.