- Timestamp:
- Jun 17, 2009, 2:19:52 PM (16 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
branches/samba-3.3.x/docs/htmldocs/Samba3-HOWTO/domain-member.html
r218 r274 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"><<a class="email" href="mailto:jht@samba.org">jht@samba.org</a>></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"><<a class="email" href="mailto:jra@samba.org">jra@samba.org</a>></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"><<a class="email" href="mailto:jerry@samba.org">jerry@samba.org</a>></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"><<a class="email" href="mailto:tridge@samba.org">tridge@samba.org</a>></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"><<a class="email" href="mailto:jelmer@samba.org">jelmer@samba.org</a>></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"><<a class="email" href="mailto:gd@suse.de">gd@suse.de</a>></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="id25690 52"></a>3 <a class="indexterm" name="id25690 58"></a>4 <a class="indexterm" name="id25690 66"></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.3.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"><<a class="email" href="mailto:jht@samba.org">jht@samba.org</a>></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"><<a class="email" href="mailto:jra@samba.org">jra@samba.org</a>></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"><<a class="email" href="mailto:jerry@samba.org">jerry@samba.org</a>></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"><<a class="email" href="mailto:tridge@samba.org">tridge@samba.org</a>></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"><<a class="email" href="mailto:jelmer@samba.org">jelmer@samba.org</a>></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"><<a class="email" href="mailto:gd@suse.de">gd@suse.de</a>></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#id2569122">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#id2569809">Manual Creation of Machine Trust Accounts</a></span></dt><dt><span class="sect2"><a href="domain-member.html#id2570246">Managing Domain Machine Accounts using NT4 Server Manager</a></span></dt><dt><span class="sect2"><a href="domain-member.html#id2570526">On-the-Fly Creation of Machine Trust Accounts</a></span></dt><dt><span class="sect2"><a href="domain-member.html#id2570632">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#id2571097">Joining an NT4-type Domain with Samba-3</a></span></dt><dt><span class="sect2"><a href="domain-member.html#id2571833">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#id2572115">Configure smb.conf</a></span></dt><dt><span class="sect2"><a href="domain-member.html#id2572306">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#id2573400">Notes</a></span></dt></dl></dd><dt><span class="sect1"><a href="domain-member.html#id2573472">Sharing User ID Mappings between Samba Domain Members</a></span></dt><dt><span class="sect1"><a href="domain-member.html#id2573679">Common Errors</a></span></dt><dd><dl><dt><span class="sect2"><a href="domain-member.html#id2573719">Cannot Add Machine Back to Domain</a></span></dt><dt><span class="sect2"><a href="domain-member.html#id2573794">Adding Machine to Domain Fails</a></span></dt><dt><span class="sect2"><a href="domain-member.html#id2574030">I Can't Join a Windows 2003 PDC</a></span></dt></dl></dd></dl></div><p> 2 <a class="indexterm" name="id2569070"></a> 3 <a class="indexterm" name="id2569077"></a> 4 <a class="indexterm" name="id2569084"></a> 5 5 Domain membership is a subject of vital concern. Samba must be able to 6 6 participate as a member server in a Microsoft domain security context, and … … 8 8 otherwise it would not be able to offer a viable option for many users. 9 9 </p><p> 10 <a class="indexterm" name="id25690 81"></a>11 <a class="indexterm" name="id2569 088"></a>10 <a class="indexterm" name="id2569099"></a> 11 <a class="indexterm" name="id2569106"></a> 12 12 This chapter covers background information pertaining to domain membership, 13 13 the Samba configuration for it, and MS Windows client procedures for joining a … … 17 17 misinformation, incorrect understanding, and lack of knowledge. Hopefully 18 18 this 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="id25691 04"></a>Features and Benefits</h2></div></div></div><p>20 <a class="indexterm" name="id25691 12"></a>21 <a class="indexterm" name="id25691 19"></a>22 <a class="indexterm" name="id25691 26"></a>19 </p><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2569122"></a>Features and Benefits</h2></div></div></div><p> 20 <a class="indexterm" name="id2569130"></a> 21 <a class="indexterm" name="id2569137"></a> 22 <a class="indexterm" name="id2569144"></a> 23 23 MS Windows workstations and servers that want to participate in domain security need to 24 24 be made domain members. Participating in domain security is often called … … 28 28 server) or a Samba server a member of an MS Windows domain security context. 29 29 </p><p> 30 <a class="indexterm" name="id25691 58"></a>31 <a class="indexterm" name="id25691 64"></a>32 <a class="indexterm" name="id25691 71"></a>33 <a class="indexterm" name="id25691 78"></a>30 <a class="indexterm" name="id2569176"></a> 31 <a class="indexterm" name="id2569183"></a> 32 <a class="indexterm" name="id2569190"></a> 33 <a class="indexterm" name="id2569196"></a> 34 34 Samba-3 can join an MS Windows NT4-style domain as a native member server, an 35 35 MS Windows Active Directory domain as a native member server, or a Samba domain 36 36 control network. Domain membership has many advantages: 37 37 </p><div class="itemizedlist"><ul type="disc"><li><p> 38 <a class="indexterm" name="id2569 197"></a>38 <a class="indexterm" name="id2569216"></a> 39 39 MS Windows workstation users get the benefit of SSO. 40 40 </p></li><li><p> 41 <a class="indexterm" name="id25692 09"></a>42 <a class="indexterm" name="id25692 16"></a>43 <a class="indexterm" name="id25692 23"></a>44 <a class="indexterm" name="id25692 30"></a>41 <a class="indexterm" name="id2569228"></a> 42 <a class="indexterm" name="id2569235"></a> 43 <a class="indexterm" name="id2569242"></a> 44 <a class="indexterm" name="id2569249"></a> 45 45 Domain user access rights and file ownership/access controls can be set 46 46 from the single Domain Security Account Manager (SAM) database … … 48 48 that are domain members). 49 49 </p></li><li><p> 50 <a class="indexterm" name="id25692 45"></a>51 <a class="indexterm" name="id25692 52"></a>50 <a class="indexterm" name="id2569264"></a> 51 <a class="indexterm" name="id2569270"></a> 52 52 Only <span class="application">MS Windows NT4/200x/XP Professional</span> 53 53 workstations that are domain members can use network logon facilities. 54 54 </p></li><li><p> 55 <a class="indexterm" name="id25692 71"></a>56 <a class="indexterm" name="id25692 78"></a>57 <a class="indexterm" name="id2569 285"></a>58 <a class="indexterm" name="id2569 292"></a>55 <a class="indexterm" name="id2569289"></a> 56 <a class="indexterm" name="id2569296"></a> 57 <a class="indexterm" name="id2569303"></a> 58 <a class="indexterm" name="id2569310"></a> 59 59 Domain member workstations can be better controlled through the use of 60 60 policy files (<code class="filename">NTConfig.POL</code>) and desktop profiles. 61 61 </p></li><li><p> 62 <a class="indexterm" name="id25693 11"></a>63 <a class="indexterm" name="id25693 18"></a>64 <a class="indexterm" name="id25693 25"></a>62 <a class="indexterm" name="id2569329"></a> 63 <a class="indexterm" name="id2569336"></a> 64 <a class="indexterm" name="id2569343"></a> 65 65 Through the use of logon scripts, users can be given transparent access to network 66 66 applications that run off application servers. 67 67 </p></li><li><p> 68 <a class="indexterm" name="id25693 38"></a>69 <a class="indexterm" name="id25693 45"></a>70 <a class="indexterm" name="id25693 52"></a>71 <a class="indexterm" name="id25693 59"></a>68 <a class="indexterm" name="id2569357"></a> 69 <a class="indexterm" name="id2569364"></a> 70 <a class="indexterm" name="id2569370"></a> 71 <a class="indexterm" name="id2569377"></a> 72 72 Network administrators gain better application and user access management 73 73 abilities because there is no need to maintain user accounts on any network … … 76 76 LDAP directory, or via an Active Directory infrastructure). 77 77 </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="id2569 387"></a>79 <a class="indexterm" name="id2569 394"></a>80 <a class="indexterm" name="id25694 01"></a>81 <a class="indexterm" name="id25694 08"></a>78 <a class="indexterm" name="id2569406"></a> 79 <a class="indexterm" name="id2569412"></a> 80 <a class="indexterm" name="id2569419"></a> 81 <a class="indexterm" name="id2569426"></a> 82 82 A Machine Trust Account is an account that is used to authenticate a client machine (rather than a user) to 83 83 the domain controller server. In Windows terminology, this is known as a “<span class="quote">computer account.</span>” The … … 85 85 access to a domain member workstation. 86 86 </p><p> 87 <a class="indexterm" name="id25694 27"></a>88 <a class="indexterm" name="id25694 36"></a>89 <a class="indexterm" name="id25694 43"></a>90 <a class="indexterm" name="id25694 50"></a>91 <a class="indexterm" name="id25694 58"></a>87 <a class="indexterm" name="id2569446"></a> 88 <a class="indexterm" name="id2569455"></a> 89 <a class="indexterm" name="id2569462"></a> 90 <a class="indexterm" name="id2569469"></a> 91 <a class="indexterm" name="id2569476"></a> 92 92 The password of a Machine Trust Account acts as the shared secret for secure communication with the domain 93 93 controller. This is a security feature to prevent an unauthorized machine with the same NetBIOS name from … … 97 97 possess a Machine Trust Account, and, thus, has no shared secret with the domain controller. 98 98 </p><p> 99 <a class="indexterm" name="id25694 78"></a>100 <a class="indexterm" name="id2569 485"></a>101 <a class="indexterm" name="id2569 492"></a>102 <a class="indexterm" name="id2569 498"></a>99 <a class="indexterm" name="id2569497"></a> 100 <a class="indexterm" name="id2569504"></a> 101 <a class="indexterm" name="id2569510"></a> 102 <a class="indexterm" name="id2569517"></a> 103 103 A Windows NT4 PDC stores each Machine Trust Account in the Windows Registry. 104 104 The introduction of MS Windows 2000 saw the introduction of Active Directory, … … 108 108 109 109 </p><div class="itemizedlist"><ul type="disc"><li><p> 110 <a class="indexterm" name="id25695 16"></a>111 <a class="indexterm" name="id25695 23"></a>112 <a class="indexterm" name="id25695 30"></a>110 <a class="indexterm" name="id2569534"></a> 111 <a class="indexterm" name="id2569541"></a> 112 <a class="indexterm" name="id2569548"></a> 113 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 114 114 the <code class="filename">smb.conf</code> file. The precise nature of the account information that is stored depends on the type of 115 115 backend database that has been chosen. 116 116 </p><p> 117 <a class="indexterm" name="id25695 61"></a>118 <a class="indexterm" name="id25695 68"></a>119 <a class="indexterm" name="id25695 75"></a>120 <a class="indexterm" name="id2569 582"></a>121 <a class="indexterm" name="id2569 588"></a>122 <a class="indexterm" name="id2569 596"></a>117 <a class="indexterm" name="id2569580"></a> 118 <a class="indexterm" name="id2569587"></a> 119 <a class="indexterm" name="id2569594"></a> 120 <a class="indexterm" name="id2569600"></a> 121 <a class="indexterm" name="id2569607"></a> 122 <a class="indexterm" name="id2569614"></a> 123 123 The older format of this data is the <code class="filename">smbpasswd</code> database 124 124 that contains the UNIX login ID, the UNIX user identifier (UID), and the … … 126 126 this file that we do not need to concern ourselves with here. 127 127 </p><p> 128 <a class="indexterm" name="id25696 18"></a>129 <a class="indexterm" name="id25696 24"></a>130 <a class="indexterm" name="id25696 31"></a>131 <a class="indexterm" name="id25696 38"></a>128 <a class="indexterm" name="id2569636"></a> 129 <a class="indexterm" name="id2569643"></a> 130 <a class="indexterm" name="id2569650"></a> 131 <a class="indexterm" name="id2569656"></a> 132 132 The two newer database types are called ldapsam and tdbsam. Both store considerably more data than the older 133 133 <code class="filename">smbpasswd</code> file did. The extra information enables new user account controls to be 134 134 implemented. 135 135 </p></li><li><p> 136 <a class="indexterm" name="id25696 58"></a>137 <a class="indexterm" name="id25696 65"></a>136 <a class="indexterm" name="id2569677"></a> 137 <a class="indexterm" name="id2569684"></a> 138 138 A corresponding UNIX account, typically stored in <code class="filename">/etc/passwd</code>. Work is in progress to 139 139 allow a simplified mode of operation that does not require UNIX user accounts, but this has not been a feature … … 141 141 </p></li></ul></div><p> 142 142 </p><p> 143 <a class="indexterm" name="id2569 691"></a>143 <a class="indexterm" name="id2569710"></a> 144 144 There are three ways to create Machine Trust Accounts: 145 145 </p><div class="itemizedlist"><ul type="disc"><li><p> 146 <a class="indexterm" name="id25697 08"></a>146 <a class="indexterm" name="id2569726"></a> 147 147 Manual creation from the UNIX/Linux command line. Here, both the Samba and 148 148 corresponding UNIX account are created by hand. 149 149 </p></li><li><p> 150 <a class="indexterm" name="id25697 21"></a>151 <a class="indexterm" name="id25697 28"></a>150 <a class="indexterm" name="id2569740"></a> 151 <a class="indexterm" name="id2569747"></a> 152 152 Using the MS Windows NT4 Server Manager, either from an NT4 domain member 153 153 server or using the Nexus toolkit available from the Microsoft Web site. … … 155 155 logged on as the administrator account. 156 156 </p></li><li><p> 157 <a class="indexterm" name="id25697 44"></a>158 <a class="indexterm" name="id25697 51"></a>157 <a class="indexterm" name="id2569763"></a> 158 <a class="indexterm" name="id2569770"></a> 159 159 “<span class="quote">On-the-fly</span>” creation. The Samba Machine Trust Account is automatically 160 160 created by Samba at the time the client is joined to the domain. … … 162 162 account may be created automatically or manually. 163 163 </p></li></ul></div><p> 164 <a class="indexterm" name="id25697 70"></a>165 <a class="indexterm" name="id25697 77"></a>164 <a class="indexterm" name="id2569789"></a> 165 <a class="indexterm" name="id2569795"></a> 166 166 Neither MS Windows NT4/200x/XP Professional, nor Samba, provide any method for enforcing the method of machine 167 167 trust 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="id2569 791"></a>Manual Creation of Machine Trust Accounts</h3></div></div></div><p>169 <a class="indexterm" name="id2569 799"></a>170 <a class="indexterm" name="id25698 06"></a>171 <a class="indexterm" name="id25698 11"></a>172 <a class="indexterm" name="id25698 18"></a>168 </p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2569809"></a>Manual Creation of Machine Trust Accounts</h3></div></div></div><p> 169 <a class="indexterm" name="id2569817"></a> 170 <a class="indexterm" name="id2569824"></a> 171 <a class="indexterm" name="id2569830"></a> 172 <a class="indexterm" name="id2569836"></a> 173 173 The first step in manually creating a Machine Trust Account is to manually 174 174 create the corresponding UNIX account in <code class="filename">/etc/passwd</code>. … … 184 184 </pre><p> 185 185 </p><p> 186 <a class="indexterm" name="id2569 887"></a>187 <a class="indexterm" name="id2569 894"></a>188 <a class="indexterm" name="id25699 00"></a>186 <a class="indexterm" name="id2569905"></a> 187 <a class="indexterm" name="id2569912"></a> 188 <a class="indexterm" name="id2569919"></a> 189 189 In the example above there is an existing system group “<span class="quote">machines</span>” which is used 190 190 as the primary group for all machine accounts. In the following examples the “<span class="quote">machines</span>” group 191 191 numeric GID is 100. 192 192 </p><p> 193 <a class="indexterm" name="id25699 20"></a>194 <a class="indexterm" name="id25699 27"></a>193 <a class="indexterm" name="id2569939"></a> 194 <a class="indexterm" name="id2569946"></a> 195 195 On *BSD systems, this can be done using the <code class="literal">chpass</code> utility: 196 196 </p><pre class="screen"> … … 199 199 </pre><p> 200 200 </p><p> 201 <a class="indexterm" name="id25699 68"></a>202 <a class="indexterm" name="id25699 75"></a>203 <a class="indexterm" name="id25 69982"></a>204 <a class="indexterm" name="id25 69988"></a>201 <a class="indexterm" name="id2569987"></a> 202 <a class="indexterm" name="id2569994"></a> 203 <a class="indexterm" name="id2570000"></a> 204 <a class="indexterm" name="id2570007"></a> 205 205 The <code class="filename">/etc/passwd</code> entry will list the machine name 206 206 with a “<span class="quote">$</span>” appended, and will not have a password, will have a null shell and no … … 211 211 </pre><p> 212 212 </p><p> 213 <a class="indexterm" name="id25700 31"></a>214 <a class="indexterm" name="id25700 38"></a>215 <a class="indexterm" name="id25700 45"></a>213 <a class="indexterm" name="id2570049"></a> 214 <a class="indexterm" name="id2570056"></a> 215 <a class="indexterm" name="id2570063"></a> 216 216 in which <em class="replaceable"><code>machine_nickname</code></em> can be any 217 217 descriptive name for the client, such as BasementComputer. … … 221 221 this as a Machine Trust Account. 222 222 </p><p> 223 <a class="indexterm" name="id25700 70"></a>224 <a class="indexterm" name="id25700 77"></a>225 <a class="indexterm" name="id2570 084"></a>223 <a class="indexterm" name="id2570089"></a> 224 <a class="indexterm" name="id2570096"></a> 225 <a class="indexterm" name="id2570103"></a> 226 226 Now that the corresponding UNIX account has been created, the next step is to create 227 227 the Samba account for the client containing the well-known initial … … 233 233 </pre><p> 234 234 </p><p> 235 <a class="indexterm" name="id25701 26"></a>236 <a class="indexterm" name="id25701 33"></a>237 <a class="indexterm" name="id25701 40"></a>238 <a class="indexterm" name="id25701 46"></a>235 <a class="indexterm" name="id2570144"></a> 236 <a class="indexterm" name="id2570151"></a> 237 <a class="indexterm" name="id2570158"></a> 238 <a class="indexterm" name="id2570165"></a> 239 239 where <em class="replaceable"><code>machine_name</code></em> is the machine's NetBIOS 240 240 name. The RID of the new machine account is generated from the UID of 241 241 the corresponding UNIX account. 242 242 </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="id25701 68"></a>244 <a class="indexterm" name="id25701 75"></a>245 <a class="indexterm" name="id2570 182"></a>246 <a class="indexterm" name="id2570 189"></a>247 <a class="indexterm" name="id2570 196"></a>243 <a class="indexterm" name="id2570187"></a> 244 <a class="indexterm" name="id2570194"></a> 245 <a class="indexterm" name="id2570200"></a> 246 <a class="indexterm" name="id2570207"></a> 247 <a class="indexterm" name="id2570214"></a> 248 248 Manually creating a Machine Trust Account using this method is the 249 249 equivalent of creating a Machine Trust Account on a Windows NT PDC using 250 <a class="indexterm" name="id25702 05"></a>250 <a class="indexterm" name="id2570224"></a> 251 251 the <span class="application">Server Manager</span>. From the time at which the 252 252 account is created to the time the client joins the domain and … … 255 255 trusts members of the domain and will serve out a large degree of user 256 256 information 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="id25702 27"></a>Managing Domain Machine Accounts using NT4 Server Manager</h3></div></div></div><p>258 <a class="indexterm" name="id25702 36"></a>259 <a class="indexterm" name="id25702 43"></a>260 <a class="indexterm" name="id25702 50"></a>257 </p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2570246"></a>Managing Domain Machine Accounts using NT4 Server Manager</h3></div></div></div><p> 258 <a class="indexterm" name="id2570254"></a> 259 <a class="indexterm" name="id2570262"></a> 260 <a class="indexterm" name="id2570269"></a> 261 261 A working <a class="link" href="smb.conf.5.html#ADDMACHINESCRIPT" target="_top">add machine script</a> is essential 262 262 for machine trust accounts to be automatically created. This applies no matter whether 263 263 you use automatic account creation or the NT4 Domain Server Manager. 264 264 </p><p> 265 <a class="indexterm" name="id25702 76"></a>266 <a class="indexterm" name="id2570 283"></a>267 <a class="indexterm" name="id2570 289"></a>268 <a class="indexterm" name="id2570 296"></a>265 <a class="indexterm" name="id2570294"></a> 266 <a class="indexterm" name="id2570301"></a> 267 <a class="indexterm" name="id2570308"></a> 268 <a class="indexterm" name="id2570314"></a> 269 269 If the machine from which you are trying to manage the domain is an 270 270 <span class="application">MS Windows NT4 workstation or MS Windows 200x/XP Professional</span>, … … 273 273 and <code class="literal">UsrMgr.exe</code> (both are domain management tools for MS Windows NT4 workstation). 274 274 </p><p> 275 <a class="indexterm" name="id25703 34"></a>276 <a class="indexterm" name="id25703 41"></a>275 <a class="indexterm" name="id2570353"></a> 276 <a class="indexterm" name="id2570360"></a> 277 277 If your workstation is a <span class="application">Microsoft Windows 9x/Me</span> family product, 278 278 you should download the <code class="literal">Nexus.exe</code> package from the Microsoft Web site. … … 284 284 <a class="ulink" href="http://support.microsoft.com/default.aspx?scid=kb;en-us;172540" target="_top">172540</a> 285 285 </p><p> 286 <a class="indexterm" name="id2570 385"></a>287 <a class="indexterm" name="id2570 392"></a>286 <a class="indexterm" name="id2570404"></a> 287 <a class="indexterm" name="id2570411"></a> 288 288 Launch the <code class="literal">srvmgr.exe</code> (Server Manager for Domains) and follow these steps: 289 </p><div class="procedure"><a name="id25704 07"></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="id2570426"></a><p class="title"><b>Procedure 6.1. Server Manager Account Machine Account Management</b></p><ol type="1"><li><p> 290 290 From the menu select <span class="guimenu">Computer</span>. 291 291 </p></li><li><p> … … 304 304 enter the machine name in the field provided, and click the 305 305 <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="id25705 08"></a>On-the-Fly Creation of Machine Trust Accounts</h3></div></div></div><p>307 <a class="indexterm" name="id25705 16"></a>306 </p></li></ol></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2570526"></a>On-the-Fly Creation of Machine Trust Accounts</h3></div></div></div><p> 307 <a class="indexterm" name="id2570535"></a> 308 308 The third (and recommended) way of creating Machine Trust Accounts is simply to allow the Samba server to 309 309 create them as needed when the client is joined to the domain. 310 310 </p><p> 311 <a class="indexterm" name="id25705 32"></a>312 <a class="indexterm" name="id25705 42"></a>313 <a class="indexterm" name="id25705 48"></a>311 <a class="indexterm" name="id2570550"></a> 312 <a class="indexterm" name="id2570560"></a> 313 <a class="indexterm" name="id2570567"></a> 314 314 Since each Samba Machine Trust Account requires a corresponding UNIX account, a method 315 315 for automatically creating the UNIX account is usually supplied; this requires configuration of the … … 317 317 accounts may also be created manually. 318 318 </p><p> 319 <a class="indexterm" name="id25705 70"></a>320 <a class="indexterm" name="id25705 77"></a>319 <a class="indexterm" name="id2570588"></a> 320 <a class="indexterm" name="id2570595"></a> 321 321 Here 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="id2570 599"></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 14"></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="id2570617"></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="id2570632"></a>Making an MS Windows Workstation or Server a Domain Member</h3></div></div></div><p> 324 324 The procedure for making an MS Windows workstation or server a member of the domain varies 325 325 with the version of Windows. 326 </p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id25706 25"></a>Windows 200x/XP Professional Client</h4></div></div></div><p>327 <a class="indexterm" name="id25706 33"></a>328 <a class="indexterm" name="id25706 40"></a>329 <a class="indexterm" name="id25706 49"></a>330 <a class="indexterm" name="id25706 56"></a>326 </p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2570643"></a>Windows 200x/XP Professional Client</h4></div></div></div><p> 327 <a class="indexterm" name="id2570651"></a> 328 <a class="indexterm" name="id2570658"></a> 329 <a class="indexterm" name="id2570668"></a> 330 <a class="indexterm" name="id2570675"></a> 331 331 When the user elects to make the client a domain member, Windows 200x prompts for 332 332 an account and password that has privileges to create machine accounts in the domain. … … 335 335 account is given. 336 336 </p><p> 337 <a class="indexterm" name="id25706 76"></a>338 <a class="indexterm" name="id2570 683"></a>337 <a class="indexterm" name="id2570694"></a> 338 <a class="indexterm" name="id2570701"></a> 339 339 For security reasons, the password for this administrator account should be set 340 340 to a password that is other than that used for the root user in <code class="filename">/etc/passwd</code>. 341 341 </p><p> 342 <a class="indexterm" name="id25707 01"></a>343 <a class="indexterm" name="id25707 08"></a>344 <a class="indexterm" name="id25707 15"></a>345 <a class="indexterm" name="id25707 22"></a>342 <a class="indexterm" name="id2570720"></a> 343 <a class="indexterm" name="id2570726"></a> 344 <a class="indexterm" name="id2570733"></a> 345 <a class="indexterm" name="id2570740"></a> 346 346 The name of the account that is used to create domain member machine trust accounts can be 347 347 anything the network administrator may choose. If it is other than <code class="constant">root</code>, … … 349 349 <a class="link" href="smb.conf.5.html#USERNAMEMAP" target="_top">username map = /etc/samba/smbusers</a>. 350 350 </p><p> 351 <a class="indexterm" name="id25707 62"></a>352 <a class="indexterm" name="id25707 69"></a>353 <a class="indexterm" name="id25707 75"></a>351 <a class="indexterm" name="id2570780"></a> 352 <a class="indexterm" name="id2570787"></a> 353 <a class="indexterm" name="id2570793"></a> 354 354 The session key of the Samba administrator account acts as an encryption key for setting the password of the machine trust 355 355 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="id2570 788"></a>Windows NT4 Client</h4></div></div></div><p>357 <a class="indexterm" name="id2570 796"></a>358 <a class="indexterm" name="id25708 03"></a>359 <a class="indexterm" name="id25708 10"></a>356 </p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2570806"></a>Windows NT4 Client</h4></div></div></div><p> 357 <a class="indexterm" name="id2570814"></a> 358 <a class="indexterm" name="id2570821"></a> 359 <a class="indexterm" name="id2570828"></a> 360 360 If the Machine Trust Account was created manually, on the 361 361 Identification Changes menu enter the domain name, but do not … … 364 364 to the domain. 365 365 </p><p> 366 <a class="indexterm" name="id25708 30"></a>367 <a class="indexterm" name="id25708 37"></a>368 <a class="indexterm" name="id25708 44"></a>369 <a class="indexterm" name="id25708 51"></a>366 <a class="indexterm" name="id2570849"></a> 367 <a class="indexterm" name="id2570856"></a> 368 <a class="indexterm" name="id2570862"></a> 369 <a class="indexterm" name="id2570869"></a> 370 370 If the Machine Trust Account is to be created on the fly, on the Identification Changes menu enter the domain 371 371 name and check the box <span class="guilabel">Create a Computer Account in the Domain</span>. In this case, joining 372 372 the domain proceeds as above for Windows 2000 (i.e., you must supply a Samba administrator account when 373 373 prompted). 374 </p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id25708 71"></a>Samba Client</h4></div></div></div><p>375 <a class="indexterm" name="id25708 79"></a>374 </p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2570890"></a>Samba Client</h4></div></div></div><p> 375 <a class="indexterm" name="id2570898"></a> 376 376 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>. 377 377 </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="id25709 10"></a>379 <a class="indexterm" name="id25709 17"></a>380 <a class="indexterm" name="id25709 24"></a>381 <a class="indexterm" name="id25709 31"></a>378 <a class="indexterm" name="id2570928"></a> 379 <a class="indexterm" name="id2570935"></a> 380 <a class="indexterm" name="id2570942"></a> 381 <a class="indexterm" name="id2570949"></a> 382 382 This mode of server operation involves the Samba machine being made a member 383 383 of a domain security context. This means by definition that all user … … 388 388 </p><p> 389 389 <span class="emphasis"><em> 390 <a class="indexterm" name="id25709 50"></a>391 <a class="indexterm" name="id25709 59"></a>392 <a class="indexterm" name="id25709 66"></a>393 <a class="indexterm" name="id25709 73"></a>394 <a class="indexterm" name="id25709 80"></a>395 <a class="indexterm" name="id257 0987"></a>396 <a class="indexterm" name="id257 0993"></a>397 <a class="indexterm" name="id25710 00"></a>390 <a class="indexterm" name="id2570968"></a> 391 <a class="indexterm" name="id2570978"></a> 392 <a class="indexterm" name="id2570985"></a> 393 <a class="indexterm" name="id2570991"></a> 394 <a class="indexterm" name="id2570998"></a> 395 <a class="indexterm" name="id2571005"></a> 396 <a class="indexterm" name="id2571012"></a> 397 <a class="indexterm" name="id2571018"></a> 398 398 Of course it should be clear that the authentication backend itself could be 399 399 from any distributed directory architecture server that is supported by Samba. … … 402 402 </em></span> 403 403 </p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p> 404 <a class="indexterm" name="id25710 16"></a>405 <a class="indexterm" name="id25710 23"></a>406 <a class="indexterm" name="id25710 30"></a>404 <a class="indexterm" name="id2571035"></a> 405 <a class="indexterm" name="id2571042"></a> 406 <a class="indexterm" name="id2571048"></a> 407 407 When Samba is configured to use an LDAP or other identity management and/or 408 408 directory service, it is Samba that continues to perform user and machine … … 410 410 authentication handling in place of what Samba is designed to do. 411 411 </p></div><p> 412 <a class="indexterm" name="id25710 45"></a>413 <a class="indexterm" name="id25710 52"></a>414 <a class="indexterm" name="id25710 60"></a>412 <a class="indexterm" name="id2571064"></a> 413 <a class="indexterm" name="id2571071"></a> 414 <a class="indexterm" name="id2571078"></a> 415 415 Please refer to <a class="link" href="samba-pdc.html" title="Chapter 4. Domain Control">Domain Control</a>, for more information regarding 416 416 how to create a domain machine account for a domain member server as well as for 417 417 information on how to enable the Samba domain member machine to join the domain 418 418 and be fully trusted by it. 419 </p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id25710 79"></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="id25711 63"></a>419 </p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2571097"></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="id2571182"></a> 421 421 First, you must edit your <code class="filename">smb.conf</code> file to tell Samba it should now use domain security. 422 422 </p><p> 423 <a class="indexterm" name="id25711 79"></a>424 <a class="indexterm" name="id2571 186"></a>425 <a class="indexterm" name="id2571 193"></a>426 <a class="indexterm" name="id25712 00"></a>423 <a class="indexterm" name="id2571198"></a> 424 <a class="indexterm" name="id2571205"></a> 425 <a class="indexterm" name="id2571212"></a> 426 <a class="indexterm" name="id2571219"></a> 427 427 Change (or add) your <a class="link" href="smb.conf.5.html#SECURITY" target="_top">security</a> line in the [global] section 428 428 of 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="id25712 31"></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="id2571249"></a><em class="parameter"><code>security = domain</code></em></td></tr></table><p> 430 430 Note that if the parameter <em class="parameter"><code>security = user</code></em> is used, this machine would function as a 431 431 standalone server and not as a domain member server. Domain security mode causes Samba to work within the … … 434 434 Next 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> 435 435 section to read: 436 </p><table class="simplelist" border="0" summary="Simple list"><tr><td><a class="indexterm" name="id25712 79"></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="id2571297"></a><em class="parameter"><code>workgroup = MIDEARTH</code></em></td></tr></table><p> 437 437 This is the name of the domain we are joining. 438 438 </p><p> 439 <a class="indexterm" name="id2571 295"></a>440 <a class="indexterm" name="id25713 02"></a>439 <a class="indexterm" name="id2571313"></a> 440 <a class="indexterm" name="id2571320"></a> 441 441 You must also have the parameter <a class="link" href="smb.conf.5.html#ENCRYPTPASSWORDS" target="_top">encrypt passwords</a> 442 442 set to <code class="constant">yes</code> in order for your users to authenticate to the NT PDC. … … 444 444 parameter, but if it is specified in the <code class="filename">smb.conf</code> file, it must be set to <code class="constant">Yes</code>. 445 445 </p><p> 446 <a class="indexterm" name="id25713 41"></a>447 <a class="indexterm" name="id25713 47"></a>448 <a class="indexterm" name="id25713 54"></a>449 <a class="indexterm" name="id25713 61"></a>446 <a class="indexterm" name="id2571359"></a> 447 <a class="indexterm" name="id2571366"></a> 448 <a class="indexterm" name="id2571372"></a> 449 <a class="indexterm" name="id2571379"></a> 450 450 Finally, add (or modify) a <a class="link" href="smb.conf.5.html#PASSWORDSERVER" target="_top">password server</a> line in the [global] 451 451 section to read: 452 </p><table class="simplelist" border="0" summary="Simple list"><tr><td><a class="indexterm" name="id2571 385"></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="id2571404"></a><em class="parameter"><code>password server = DOMPDC DOMBDC1 DOMBDC2</code></em></td></tr></table><p> 453 453 These are the PDC and BDCs Samba 454 454 will attempt to contact in order to authenticate users. Samba will … … 457 457 among Domain Controllers. 458 458 </p><p> 459 <a class="indexterm" name="id25714 05"></a>460 <a class="indexterm" name="id25714 12"></a>461 <a class="indexterm" name="id25714 19"></a>462 <a class="indexterm" name="id25714 26"></a>459 <a class="indexterm" name="id2571423"></a> 460 <a class="indexterm" name="id2571430"></a> 461 <a class="indexterm" name="id2571437"></a> 462 <a class="indexterm" name="id2571444"></a> 463 463 Alternatively, if you want smbd to determine automatically the list of domain controllers to use for 464 464 authentication, you may set this line to be: 465 </p><table class="simplelist" border="0" summary="Simple list"><tr><td><a class="indexterm" name="id25714 41"></a><em class="parameter"><code>password server = *</code></em></td></tr></table><p>466 <a class="indexterm" name="id25714 53"></a>465 </p><table class="simplelist" border="0" summary="Simple list"><tr><td><a class="indexterm" name="id2571459"></a><em class="parameter"><code>password server = *</code></em></td></tr></table><p> 466 <a class="indexterm" name="id2571471"></a> 467 467 This method allows Samba to use exactly the same mechanism that NT does. The 468 468 method either uses broadcast-based name resolution, performs a WINS database … … 471 471 </p><p> 472 472 To join the domain, run this command: 473 <a class="indexterm" name="id25714 68"></a>473 <a class="indexterm" name="id2571487"></a> 474 474 </p><pre class="screen"> 475 475 <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> 476 476 </pre><p> 477 477 </p><p> 478 <a class="indexterm" name="id25715 02"></a>479 <a class="indexterm" name="id25715 09"></a>480 <a class="indexterm" name="id25715 15"></a>481 <a class="indexterm" name="id25715 22"></a>478 <a class="indexterm" name="id2571520"></a> 479 <a class="indexterm" name="id2571527"></a> 480 <a class="indexterm" name="id2571534"></a> 481 <a class="indexterm" name="id2571540"></a> 482 482 If 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 483 483 the NetBIOS name of the PDC will be obtained either using a WINS lookup or via NetBIOS broadcast based name 484 484 look up. 485 485 </p><p> 486 <a class="indexterm" name="id25715 45"></a>487 <a class="indexterm" name="id25715 52"></a>488 <a class="indexterm" name="id25715 58"></a>489 <a class="indexterm" name="id25715 65"></a>486 <a class="indexterm" name="id2571563"></a> 487 <a class="indexterm" name="id2571570"></a> 488 <a class="indexterm" name="id2571577"></a> 489 <a class="indexterm" name="id2571584"></a> 490 490 The machine is joining the domain DOM, and the PDC for that domain (the only machine 491 491 that has write access to the domain SAM database) is DOMPDC; therefore, use the <code class="option">-S</code> … … 498 498 </pre><p> 499 499 </p><p> 500 <a class="indexterm" name="id2571602"></a>501 <a class="indexterm" name="id2571613"></a>502 500 <a class="indexterm" name="id2571620"></a> 501 <a class="indexterm" name="id2571632"></a> 502 <a class="indexterm" name="id2571638"></a> 503 503 Where Active Directory is used, the command used to join the ADS domain is: 504 504 </p><pre class="screen"> … … 513 513 administration</a> for further information. 514 514 </p><p> 515 <a class="indexterm" name="id25716 77"></a>516 <a class="indexterm" name="id2571 684"></a>517 <a class="indexterm" name="id2571 691"></a>515 <a class="indexterm" name="id2571696"></a> 516 <a class="indexterm" name="id2571702"></a> 517 <a class="indexterm" name="id2571710"></a> 518 518 This process joins the server to the domain without separately having to create the machine 519 519 trust account on the PDC beforehand. 520 520 </p><p> 521 <a class="indexterm" name="id25717 03"></a>522 <a class="indexterm" name="id25717 13"></a>523 <a class="indexterm" name="id25717 20"></a>524 <a class="indexterm" name="id25717 27"></a>521 <a class="indexterm" name="id2571722"></a> 522 <a class="indexterm" name="id2571731"></a> 523 <a class="indexterm" name="id2571738"></a> 524 <a class="indexterm" name="id2571746"></a> 525 525 This command goes through the machine account password change protocol, then writes the new (random) machine 526 526 account password for this Samba server into a file in the same directory in which a smbpasswd file would be … … 528 528 <code class="filename">/usr/local/samba/private/secrets.tdb</code> or <code class="filename">/etc/samba/secrets.tdb</code>. 529 529 </p><p> 530 <a class="indexterm" name="id25717 56"></a>531 <a class="indexterm" name="id25717 63"></a>530 <a class="indexterm" name="id2571774"></a> 531 <a class="indexterm" name="id2571781"></a> 532 532 This file is created and owned by root and is not readable by any other user. It is 533 533 the key to the domain-level security for your system and should be treated as carefully 534 534 as a shadow password file. 535 535 </p><p> 536 <a class="indexterm" name="id25717 76"></a>537 <a class="indexterm" name="id2571 783"></a>538 <a class="indexterm" name="id2571 790"></a>536 <a class="indexterm" name="id2571795"></a> 537 <a class="indexterm" name="id2571802"></a> 538 <a class="indexterm" name="id2571809"></a> 539 539 Finally, restart your Samba daemons and get ready for clients to begin using domain 540 540 security. The way you can restart your Samba daemons depends on your distribution, … … 543 543 <code class="prompt">root# </code>/etc/init.d/samba restart 544 544 </pre><p> 545 </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id25718 15"></a>Why Is This Better Than <em class="parameter"><code>security = server</code></em>?</h3></div></div></div><p>546 <a class="indexterm" name="id25718 29"></a>547 <a class="indexterm" name="id25718 36"></a>548 <a class="indexterm" name="id25718 43"></a>545 </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2571833"></a>Why Is This Better Than <em class="parameter"><code>security = server</code></em>?</h3></div></div></div><p> 546 <a class="indexterm" name="id2571847"></a> 547 <a class="indexterm" name="id2571854"></a> 548 <a class="indexterm" name="id2571861"></a> 549 549 Currently, domain security in Samba does not free you from having to create local UNIX users to represent the 550 550 users attaching to your server. This means that if domain user <code class="constant">DOM\fred</code> attaches to your … … 553 553 NT server in the same way as a Windows 95 or Windows 98 server would. 554 554 </p><p> 555 <a class="indexterm" name="id25718 77"></a>556 <a class="indexterm" name="id2571 883"></a>557 <a class="indexterm" name="id2571 890"></a>555 <a class="indexterm" name="id2571896"></a> 556 <a class="indexterm" name="id2571902"></a> 557 <a class="indexterm" name="id2571908"></a> 558 558 Please 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 559 559 to automatically assign UNIX UIDs and GIDs to Windows NT domain users and groups. 560 560 </p><p> 561 <a class="indexterm" name="id25719 09"></a>562 <a class="indexterm" name="id25719 16"></a>563 <a class="indexterm" name="id25719 23"></a>561 <a class="indexterm" name="id2571928"></a> 562 <a class="indexterm" name="id2571934"></a> 563 <a class="indexterm" name="id2571941"></a> 564 564 The advantage of domain-level security is that the authentication in domain-level security is passed down the 565 565 authenticated RPC channel in exactly the same way that an NT server would do it. This means Samba servers now … … 568 568 domain PDC). 569 569 </p><p> 570 <a class="indexterm" name="id25719 41"></a>571 <a class="indexterm" name="id25719 47"></a>572 <a class="indexterm" name="id25719 54"></a>570 <a class="indexterm" name="id2571959"></a> 571 <a class="indexterm" name="id2571966"></a> 572 <a class="indexterm" name="id2571972"></a> 573 573 In addition, with <a class="link" href="smb.conf.5.html#SECURITY" target="_top">security = server</a>, every Samba daemon on a server has to 574 574 keep a connection open to the authenticating server for as long as that daemon lasts. This can drain the … … 578 578 connection resources. 579 579 </p><p> 580 <a class="indexterm" name="id257 1994"></a>581 <a class="indexterm" name="id25720 00"></a>582 <a class="indexterm" name="id25720 07"></a>583 <a class="indexterm" name="id25720 14"></a>580 <a class="indexterm" name="id2572012"></a> 581 <a class="indexterm" name="id2572019"></a> 582 <a class="indexterm" name="id2572026"></a> 583 <a class="indexterm" name="id2572032"></a> 584 584 Finally, acting in the same manner as an NT server authenticating to a PDC means that as part of the 585 585 authentication reply, the Samba server gets the user identification information such as the user SID, the list … … 590 590 <span class="emphasis"><em>Doing the NIS/NT Samba</em></span>. 591 591 </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="id25720 64"></a>593 <a class="indexterm" name="id25720 70"></a>594 <a class="indexterm" name="id25720 80"></a>595 <a class="indexterm" name="id2572 086"></a>592 <a class="indexterm" name="id2572082"></a> 593 <a class="indexterm" name="id2572089"></a> 594 <a class="indexterm" name="id2572098"></a> 595 <a class="indexterm" name="id2572105"></a> 596 596 This is a rough guide to setting up Samba-3 with Kerberos authentication against a 597 597 Windows 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="id2572 097"></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="id2572115"></a>Configure <code class="filename">smb.conf</code></h3></div></div></div><p> 599 599 You 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="id25721 23"></a><em class="parameter"><code>realm = your.kerberos.REALM</code></em></td></tr><tr><td><a class="indexterm" name="id2572134"></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="id2572154"></a><em class="parameter"><code>encrypt passwords = yes</code></em></td></tr></table><p>601 <a class="indexterm" name="id25721 68"></a>602 <a class="indexterm" name="id25721 75"></a>603 <a class="indexterm" name="id2572 182"></a>604 <a class="indexterm" name="id2572 188"></a>605 <a class="indexterm" name="id2572 195"></a>600 </p><table class="simplelist" border="0" summary="Simple list"><tr><td><a class="indexterm" name="id2572141"></a><em class="parameter"><code>realm = your.kerberos.REALM</code></em></td></tr><tr><td><a class="indexterm" name="id2572153"></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="id2572173"></a><em class="parameter"><code>encrypt passwords = yes</code></em></td></tr></table><p> 601 <a class="indexterm" name="id2572187"></a> 602 <a class="indexterm" name="id2572193"></a> 603 <a class="indexterm" name="id2572200"></a> 604 <a class="indexterm" name="id2572207"></a> 605 <a class="indexterm" name="id2572214"></a> 606 606 In case samba cannot correctly identify the appropriate ADS server using the realm name, use the 607 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="id25722 26"></a><em class="parameter"><code>password server = your.kerberos.server</code></em></td></tr></table><p>608 </p><table class="simplelist" border="0" summary="Simple list"><tr><td><a class="indexterm" name="id2572245"></a><em class="parameter"><code>password server = your.kerberos.server</code></em></td></tr></table><p> 609 609 The most common reason for which Samba may not be able to locate the ADS domain controller is a consequence of 610 610 sites maintaining some DNS servers on UNIX systems without regard for the DNS requirements of the ADS … … 612 612 server</code></em>. 613 613 </p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p> 614 <a class="indexterm" name="id25722 53"></a>615 <a class="indexterm" name="id25722 60"></a>614 <a class="indexterm" name="id2572272"></a> 615 <a class="indexterm" name="id2572278"></a> 616 616 You do <span class="emphasis"><em>not</em></span> need an smbpasswd file, and older clients will be authenticated as 617 617 if <a class="link" href="smb.conf.5.html#SECURITY" target="_top">security = domain</a>, although it will not do any harm and 618 618 allows 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="id2572 288"></a>Configure <code class="filename">/etc/krb5.conf</code></h3></div></div></div><p>620 <a class="indexterm" name="id25723 00"></a>621 <a class="indexterm" name="id25723 06"></a>622 <a class="indexterm" name="id25723 16"></a>623 <a class="indexterm" name="id25723 23"></a>619 </p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2572306"></a>Configure <code class="filename">/etc/krb5.conf</code></h3></div></div></div><p> 620 <a class="indexterm" name="id2572318"></a> 621 <a class="indexterm" name="id2572325"></a> 622 <a class="indexterm" name="id2572334"></a> 623 <a class="indexterm" name="id2572341"></a> 624 624 With both MIT and Heimdal Kerberos, it is unnecessary to configure the <code class="filename">/etc/krb5.conf</code>, 625 625 and it may be detrimental. 626 626 </p><p> 627 <a class="indexterm" name="id25723 41"></a>628 <a class="indexterm" name="id25723 47"></a>629 <a class="indexterm" name="id25723 54"></a>630 <a class="indexterm" name="id25723 61"></a>631 <a class="indexterm" name="id25723 67"></a>627 <a class="indexterm" name="id2572359"></a> 628 <a class="indexterm" name="id2572366"></a> 629 <a class="indexterm" name="id2572372"></a> 630 <a class="indexterm" name="id2572379"></a> 631 <a class="indexterm" name="id2572386"></a> 632 632 Microsoft ADS automatically create SRV records in the DNS zone 633 633 <em class="parameter"><code>_kerberos._tcp.REALM.NAME</code></em> for each KDC in the realm. This is part … … 636 636 active directory infrastructure. 637 637 </p><p> 638 <a class="indexterm" name="id2572 389"></a>639 <a class="indexterm" name="id2572 396"></a>640 <a class="indexterm" name="id25724 03"></a>641 <a class="indexterm" name="id25724 09"></a>642 <a class="indexterm" name="id25724 16"></a>643 <a class="indexterm" name="id25724 23"></a>638 <a class="indexterm" name="id2572407"></a> 639 <a class="indexterm" name="id2572414"></a> 640 <a class="indexterm" name="id2572421"></a> 641 <a class="indexterm" name="id2572428"></a> 642 <a class="indexterm" name="id2572435"></a> 643 <a class="indexterm" name="id2572442"></a> 644 644 UNIX systems can use kinit and the DES-CBC-MD5 or DES-CBC-CRC encryption types to authenticate to the Windows 645 645 2000 KDC. For further information regarding Windows 2000 ADS kerberos interoperability please refer to the … … 649 649 explains much of the magic behind the operation of Kerberos. 650 650 </p><p> 651 <a class="indexterm" name="id25724 55"></a>652 <a class="indexterm" name="id25724 61"></a>653 <a class="indexterm" name="id25724 68"></a>654 <a class="indexterm" name="id25724 75"></a>655 <a class="indexterm" name="id2572 482"></a>656 <a class="indexterm" name="id2572 488"></a>651 <a class="indexterm" name="id2572473"></a> 652 <a class="indexterm" name="id2572480"></a> 653 <a class="indexterm" name="id2572486"></a> 654 <a class="indexterm" name="id2572493"></a> 655 <a class="indexterm" name="id2572500"></a> 656 <a class="indexterm" name="id2572507"></a> 657 657 MIT's, as well as Heimdal's, recent KRB5 libraries default to checking for SRV records, so they will 658 658 automatically find the KDCs. In addition, <code class="filename">krb5.conf</code> only allows specifying … … 660 660 libraries to use whichever KDCs are available. 661 661 </p><p> 662 <a class="indexterm" name="id25725 10"></a>662 <a class="indexterm" name="id2572528"></a> 663 663 When manually configuring <code class="filename">krb5.conf</code>, the minimal configuration is: 664 664 </p><pre class="screen"> … … 675 675 </pre><p> 676 676 </p><p> 677 <a class="indexterm" name="id25725 35"></a>677 <a class="indexterm" name="id2572554"></a> 678 678 When using Heimdal versions before 0.6, use the following configuration settings: 679 679 </p><pre class="screen"> … … 692 692 </pre><p> 693 693 </p><p> 694 <a class="indexterm" name="id25725 57"></a>695 <a class="indexterm" name="id25725 64"></a>694 <a class="indexterm" name="id2572576"></a> 695 <a class="indexterm" name="id2572582"></a> 696 696 Test your config by doing a <strong class="userinput"><code>kinit 697 697 <em class="replaceable"><code>USERNAME</code></em>@<em class="replaceable"><code>REALM</code></em></code></strong> and 698 698 making sure that your password is accepted by the Win2000 KDC. 699 699 </p><p> 700 <a class="indexterm" name="id2572 587"></a>701 <a class="indexterm" name="id2572 594"></a>702 <a class="indexterm" name="id25726 01"></a>703 <a class="indexterm" name="id25726 07"></a>700 <a class="indexterm" name="id2572606"></a> 701 <a class="indexterm" name="id2572613"></a> 702 <a class="indexterm" name="id2572619"></a> 703 <a class="indexterm" name="id2572626"></a> 704 704 With Heimdal versions earlier than 0.6.x you can use only newly created accounts 705 705 in ADS or accounts that have had the password changed once after migration, or … … 709 709 in a state of flux. 710 710 </p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p> 711 <a class="indexterm" name="id25726 29"></a>712 <a class="indexterm" name="id25726 36"></a>713 <a class="indexterm" name="id25726 42"></a>711 <a class="indexterm" name="id2572647"></a> 712 <a class="indexterm" name="id2572654"></a> 713 <a class="indexterm" name="id2572661"></a> 714 714 The realm must be in uppercase or you will get a “<span class="quote"><span class="errorname">Cannot find KDC for 715 715 requested realm while getting initial credentials</span></span>” error (Kerberos 716 716 is case-sensitive!). 717 717 </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="id25726 60"></a>719 <a class="indexterm" name="id25726 66"></a>720 <a class="indexterm" name="id25726 73"></a>721 <a class="indexterm" name="id25726 80"></a>718 <a class="indexterm" name="id2572678"></a> 719 <a class="indexterm" name="id2572685"></a> 720 <a class="indexterm" name="id2572692"></a> 721 <a class="indexterm" name="id2572699"></a> 722 722 Time between the two servers must be synchronized. You will get a “<span class="quote"><span class="errorname">kinit(v5): Clock skew too 723 723 great while getting initial credentials</span></span>” if the time difference (clock skew) is more than five minutes. 724 724 </p></div><p> 725 <a class="indexterm" name="id2572 698"></a>726 <a class="indexterm" name="id25727 05"></a>725 <a class="indexterm" name="id2572716"></a> 726 <a class="indexterm" name="id2572723"></a> 727 727 Clock skew limits are configurable in the Kerberos protocols. The default setting is five minutes. 728 728 </p><p> 729 <a class="indexterm" name="id25727 17"></a>730 <a class="indexterm" name="id25727 23"></a>731 <a class="indexterm" name="id25727 30"></a>732 <a class="indexterm" name="id25727 37"></a>729 <a class="indexterm" name="id2572735"></a> 730 <a class="indexterm" name="id2572742"></a> 731 <a class="indexterm" name="id2572748"></a> 732 <a class="indexterm" name="id2572755"></a> 733 733 You also must ensure that you can do a reverse DNS lookup on the IP address of your KDC. Also, the name that 734 734 this reverse lookup maps to must either be the NetBIOS name of the KDC (i.e., the hostname with no domain 735 735 attached) or it can be the NetBIOS name followed by the realm. 736 736 </p><p> 737 <a class="indexterm" name="id25727 51"></a>738 <a class="indexterm" name="id25727 58"></a>739 <a class="indexterm" name="id25727 65"></a>737 <a class="indexterm" name="id2572770"></a> 738 <a class="indexterm" name="id2572777"></a> 739 <a class="indexterm" name="id2572783"></a> 740 740 The easiest way to ensure you get this right is to add a <code class="filename">/etc/hosts</code> entry mapping the IP 741 741 address of your KDC to its NetBIOS name. If you do not get this correct, then you will get a <span class="errorname">local 742 742 error</span> when you try to join the realm. 743 743 </p><p> 744 <a class="indexterm" name="id2572 788"></a>745 <a class="indexterm" name="id2572 794"></a>746 <a class="indexterm" name="id25728 02"></a>747 <a class="indexterm" name="id25728 09"></a>744 <a class="indexterm" name="id2572806"></a> 745 <a class="indexterm" name="id2572813"></a> 746 <a class="indexterm" name="id2572820"></a> 747 <a class="indexterm" name="id2572827"></a> 748 748 If 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> 749 749 and <span class="application">winbindd</span>. 750 750 </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="id25728 79"></a>752 <a class="indexterm" name="id2572 886"></a>753 <a class="indexterm" name="id2572 893"></a>754 <a class="indexterm" name="id25729 00"></a>751 <a class="indexterm" name="id2572898"></a> 752 <a class="indexterm" name="id2572904"></a> 753 <a class="indexterm" name="id2572911"></a> 754 <a class="indexterm" name="id2572918"></a> 755 755 As a user who has write permission on the Samba private directory (usually root), run: 756 756 </p><pre class="screen"> … … 761 761 On the UNIX/Linux system, this command must be executed by an account that has UID=0 (root). 762 762 </p><p> 763 <a class="indexterm" name="id25729 34"></a>764 <a class="indexterm" name="id25729 41"></a>765 <a class="indexterm" name="id25729 48"></a>766 <a class="indexterm" name="id25729 55"></a>767 <a class="indexterm" name="id25729 62"></a>768 <a class="indexterm" name="id25729 68"></a>763 <a class="indexterm" name="id2572953"></a> 764 <a class="indexterm" name="id2572959"></a> 765 <a class="indexterm" name="id2572966"></a> 766 <a class="indexterm" name="id2572973"></a> 767 <a class="indexterm" name="id2572980"></a> 768 <a class="indexterm" name="id2572987"></a> 769 769 When making a Windows client a member of an ADS domain within a complex organization, you 770 770 may want to create the machine trust account within a particular organizational unit. Samba-3 permits … … 776 776 Your ADS manager will be able to advise what should be specified for the "organizational_unit" parameter. 777 777 </p><p> 778 <a class="indexterm" name="id25730 18"></a>779 <a class="indexterm" name="id25730 26"></a>780 <a class="indexterm" name="id25730 33"></a>781 <a class="indexterm" name="id25730 39"></a>778 <a class="indexterm" name="id2573037"></a> 779 <a class="indexterm" name="id2573044"></a> 780 <a class="indexterm" name="id2573051"></a> 781 <a class="indexterm" name="id2573058"></a> 782 782 For example, you may want to create the machine trust account in a container called “<span class="quote">Servers</span>” 783 783 under the organizational directory “<span class="quote">Computers/BusinessUnit/Department,</span>” like this: … … 790 790 valid characters in an OU name and used as escapes for other characters. If you need a backslash in an OU 791 791 name, 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="id2573 089"></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="id2573107"></a>Possible Errors</h4></div></div></div><p> 793 793 </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="id25731 08"></a>795 <a class="indexterm" name="id25731 15"></a>796 <a class="indexterm" name="id25731 22"></a>794 <a class="indexterm" name="id2573126"></a> 795 <a class="indexterm" name="id2573133"></a> 796 <a class="indexterm" name="id2573140"></a> 797 797 Samba must be reconfigured (remove config.cache) and recompiled (make clean all install) after the 798 798 Kerberos libraries and headers files are installed. 799 799 </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="id25731 41"></a>801 <a class="indexterm" name="id25731 48"></a>800 <a class="indexterm" name="id2573160"></a> 801 <a class="indexterm" name="id2573167"></a> 802 802 You need to log in to the domain using <strong class="userinput"><code>kinit 803 803 <em class="replaceable"><code>USERNAME</code></em>@<em class="replaceable"><code>REALM</code></em></code></strong>. 804 804 <em class="replaceable"><code>USERNAME</code></em> must be a user who has rights to add a machine to the domain. 805 805 </p></dd><dt><span class="term">Unsupported encryption/or checksum types</span></dt><dd><p> 806 <a class="indexterm" name="id2573 181"></a>807 <a class="indexterm" name="id2573 188"></a>808 <a class="indexterm" name="id2573 195"></a>806 <a class="indexterm" name="id2573200"></a> 807 <a class="indexterm" name="id2573207"></a> 808 <a class="indexterm" name="id2573214"></a> 809 809 Make sure that the <code class="filename">/etc/krb5.conf</code> is correctly configured 810 810 for the type and version of Kerberos installed on the system. 811 811 </p></dd></dl></div><p> 812 812 </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="id25732 27"></a>814 <a class="indexterm" name="id25732 34"></a>815 <a class="indexterm" name="id25732 41"></a>813 <a class="indexterm" name="id2573246"></a> 814 <a class="indexterm" name="id2573252"></a> 815 <a class="indexterm" name="id2573259"></a> 816 816 If the join was successful, you will see a new computer account with the 817 817 NetBIOS name of your Samba server in Active Directory (in the “<span class="quote">Computers</span>” 818 818 folder under Users and Computers. 819 819 </p><p> 820 <a class="indexterm" name="id25732 57"></a>821 <a class="indexterm" name="id25732 64"></a>822 <a class="indexterm" name="id25732 73"></a>820 <a class="indexterm" name="id2573275"></a> 821 <a class="indexterm" name="id2573282"></a> 822 <a class="indexterm" name="id2573291"></a> 823 823 On a Windows 2000 client, try <strong class="userinput"><code>net use * \\server\share</code></strong>. You should 824 824 be logged in with Kerberos without needing to know a password. If this fails, then run … … 826 826 an encryption type of DES-CBC-MD5? 827 827 </p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p> 828 <a class="indexterm" name="id25733 00"></a>829 <a class="indexterm" name="id25733 07"></a>830 <a class="indexterm" name="id25733 14"></a>828 <a class="indexterm" name="id2573318"></a> 829 <a class="indexterm" name="id2573325"></a> 830 <a class="indexterm" name="id2573332"></a> 831 831 Samba can use both DES-CBC-MD5 encryption as well as ARCFOUR-HMAC-MD5 encoding. 832 832 </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="id25733 41"></a>834 <a class="indexterm" name="id25733 47"></a>835 <a class="indexterm" name="id25733 54"></a>833 <a class="indexterm" name="id2573359"></a> 834 <a class="indexterm" name="id2573366"></a> 835 <a class="indexterm" name="id2573373"></a> 836 836 On your Samba server try to log in to a Windows 2000 server or your Samba 837 837 server using <span class="application">smbclient</span> and Kerberos. Use <span class="application">smbclient</span> as usual, but 838 838 specify 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="id2573 382"></a>Notes</h3></div></div></div><p>840 <a class="indexterm" name="id2573 390"></a>841 <a class="indexterm" name="id2573 397"></a>842 <a class="indexterm" name="id25734 04"></a>839 </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2573400"></a>Notes</h3></div></div></div><p> 840 <a class="indexterm" name="id2573408"></a> 841 <a class="indexterm" name="id2573415"></a> 842 <a class="indexterm" name="id2573422"></a> 843 843 You must change the administrator password at least once after installing a domain controller, 844 844 to create the right encryption types. 845 845 </p><p> 846 <a class="indexterm" name="id25734 16"></a>847 <a class="indexterm" name="id25734 23"></a>848 <a class="indexterm" name="id25734 30"></a>846 <a class="indexterm" name="id2573434"></a> 847 <a class="indexterm" name="id2573441"></a> 848 <a class="indexterm" name="id2573448"></a> 849 849 Windows 200x does not seem to create the <em class="parameter"><code>_kerberos._udp</code></em> and 850 850 <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="id25734 54"></a>Sharing User ID Mappings between Samba Domain Members</h2></div></div></div><p>852 <a class="indexterm" name="id25734 63"></a>853 <a class="indexterm" name="id25734 70"></a>854 <a class="indexterm" name="id25734 76"></a>855 <a class="indexterm" name="id2573 483"></a>851 </p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2573472"></a>Sharing User ID Mappings between Samba Domain Members</h2></div></div></div><p> 852 <a class="indexterm" name="id2573481"></a> 853 <a class="indexterm" name="id2573488"></a> 854 <a class="indexterm" name="id2573495"></a> 855 <a class="indexterm" name="id2573501"></a> 856 856 Samba maps UNIX users and groups (identified by UIDs and GIDs) to Windows users and groups (identified by SIDs). 857 857 These mappings are done by the <em class="parameter"><code>idmap</code></em> subsystem of Samba. 858 858 </p><p> 859 <a class="indexterm" name="id25735 01"></a>860 <a class="indexterm" name="id25735 08"></a>861 <a class="indexterm" name="id25735 15"></a>859 <a class="indexterm" name="id2573520"></a> 860 <a class="indexterm" name="id2573526"></a> 861 <a class="indexterm" name="id2573533"></a> 862 862 In some cases it is useful to share these mappings between Samba domain members, 863 863 so <span class="emphasis"><em>name->id</em></span> mapping is identical on all machines. 864 864 This may be needed in particular when sharing files over both CIFS and NFS. 865 865 </p><p> 866 <a class="indexterm" name="id25735 32"></a>867 <a class="indexterm" name="id25735 39"></a>866 <a class="indexterm" name="id2573551"></a> 867 <a class="indexterm" name="id2573557"></a> 868 868 To 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="id25735 62"></a><em class="parameter"><code>ldap idmap suffix = ou=Idmap</code></em></td></tr></table><p>869 </p><table class="simplelist" border="0" summary="Simple list"><tr><td><a class="indexterm" name="id2573581"></a><em class="parameter"><code>ldap idmap suffix = ou=Idmap</code></em></td></tr></table><p> 870 870 See 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> 871 871 parameter for further information. 872 872 </p><p> 873 <a class="indexterm" name="id2573 599"></a>874 <a class="indexterm" name="id25736 05"></a>875 <a class="indexterm" name="id25736 12"></a>873 <a class="indexterm" name="id2573617"></a> 874 <a class="indexterm" name="id2573624"></a> 875 <a class="indexterm" name="id2573631"></a> 876 876 Do not forget to specify also the <a class="link" href="smb.conf.5.html#LDAPADMINDN" target="_top">ldap admin dn</a> 877 877 and to make certain to set the LDAP administrative password into the <code class="filename">secrets.tdb</code> using: … … 881 881 In place of <code class="literal">ldap-admin-password</code>, substitute the LDAP administration password for your 882 882 system. 883 </p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id25736 60"></a>Common Errors</h2></div></div></div><p>884 <a class="indexterm" name="id25736 68"></a>885 <a class="indexterm" name="id25736 75"></a>883 </p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2573679"></a>Common Errors</h2></div></div></div><p> 884 <a class="indexterm" name="id2573687"></a> 885 <a class="indexterm" name="id2573694"></a> 886 886 In the process of adding/deleting/re-adding domain member machine trust accounts, there are 887 887 many traps for the unwary player and many “<span class="quote">little</span>” things that can go wrong. … … 891 891 of problem. The real solution is often quite simple, and with an understanding of how MS Windows 892 892 networking functions, it is easy to overcome. 893 </p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id25737 00"></a>Cannot Add Machine Back to Domain</h3></div></div></div><p>894 <a class="indexterm" name="id25737 08"></a>895 <a class="indexterm" name="id25737 15"></a>893 </p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2573719"></a>Cannot Add Machine Back to Domain</h3></div></div></div><p> 894 <a class="indexterm" name="id2573727"></a> 895 <a class="indexterm" name="id2573734"></a> 896 896 “<span class="quote">A Windows workstation was reinstalled. The original domain machine trust 897 897 account was deleted and added immediately. The workstation will not join the domain if I use … … 899 899 exists on the network I know it does not. Why is this failing?</span>” 900 900 </p><p> 901 <a class="indexterm" name="id25737 37"></a>902 <a class="indexterm" name="id25737 43"></a>901 <a class="indexterm" name="id2573755"></a> 902 <a class="indexterm" name="id2573761"></a> 903 903 The original name is still in the NetBIOS name cache and must expire after machine account 904 904 deletion before adding that same name as a domain member again. The best advice is to delete … … 908 908 <code class="prompt">C:\> </code> nbtstat -R 909 909 </pre><p> 910 </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id25737 76"></a>Adding Machine to Domain Fails</h3></div></div></div><p>911 <a class="indexterm" name="id2573 784"></a>912 <a class="indexterm" name="id2573 790"></a>910 </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2573794"></a>Adding Machine to Domain Fails</h3></div></div></div><p> 911 <a class="indexterm" name="id2573802"></a> 912 <a class="indexterm" name="id2573809"></a> 913 913 “<span class="quote">Adding a Windows 200x or XP Professional machine to the Samba PDC Domain fails with a 914 914 message that says, <span class="errorname">"The machine could not be added at this time, there is a network problem. 915 915 Please try again later."</span> Why?</span>” 916 916 </p><p> 917 <a class="indexterm" name="id25738 11"></a>917 <a class="indexterm" name="id2573829"></a> 918 918 You 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> 919 919 file. If there is not, please add one that is appropriate for your OS platform. If a script … … 924 924 Possible causes include: 925 925 </p><div class="itemizedlist"><ul type="disc"><li><p> 926 <a class="indexterm" name="id25738 69"></a>927 <a class="indexterm" name="id25738 75"></a>926 <a class="indexterm" name="id2573887"></a> 927 <a class="indexterm" name="id2573894"></a> 928 928 The script does not actually exist, or could not be located in the path specified. 929 929 </p><p> 930 <a class="indexterm" name="id2573 887"></a>931 <a class="indexterm" name="id2573 894"></a>930 <a class="indexterm" name="id2573906"></a> 931 <a class="indexterm" name="id2573912"></a> 932 932 <span class="emphasis"><em>Corrective action:</em></span> Fix it. Make sure when run manually 933 933 that the script will add both the UNIX system account and the Samba SAM account. 934 934 </p></li><li><p> 935 <a class="indexterm" name="id25739 11"></a>936 <a class="indexterm" name="id25739 18"></a>935 <a class="indexterm" name="id2573929"></a> 936 <a class="indexterm" name="id2573936"></a> 937 937 The machine could not be added to the UNIX system accounts file <code class="filename">/etc/passwd</code>. 938 938 </p><p> 939 <a class="indexterm" name="id25739 35"></a>940 <a class="indexterm" name="id25739 42"></a>939 <a class="indexterm" name="id2573953"></a> 940 <a class="indexterm" name="id2573960"></a> 941 941 <span class="emphasis"><em>Corrective action:</em></span> Check that the machine name is a legal UNIX 942 942 system account name. If the UNIX utility <code class="literal">useradd</code> is called, … … 945 945 nor will it allow spaces in the name. 946 946 </p></li></ul></div><p> 947 <a class="indexterm" name="id25739 73"></a>948 <a class="indexterm" name="id25739 80"></a>949 <a class="indexterm" name="id257 3987"></a>947 <a class="indexterm" name="id2573992"></a> 948 <a class="indexterm" name="id2573999"></a> 949 <a class="indexterm" name="id2574006"></a> 950 950 The <a class="link" href="smb.conf.5.html#ADDMACHINESCRIPT" target="_top">add machine script</a> does not create the 951 951 machine account in the Samba backend database; it is there only to create a UNIX system 952 952 account 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="id25740 12"></a>I Can't Join a Windows 2003 PDC</h3></div></div></div><p>954 <a class="indexterm" name="id25740 20"></a>955 <a class="indexterm" name="id25740 26"></a>956 <a class="indexterm" name="id25740 32"></a>957 <a class="indexterm" name="id25740 39"></a>953 </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2574030"></a>I Can't Join a Windows 2003 PDC</h3></div></div></div><p> 954 <a class="indexterm" name="id2574038"></a> 955 <a class="indexterm" name="id2574044"></a> 956 <a class="indexterm" name="id2574051"></a> 957 <a class="indexterm" name="id2574058"></a> 958 958 Windows 2003 requires SMB signing. Client-side SMB signing has been implemented in Samba-3.0. 959 959 Set <a class="link" href="smb.conf.5.html#CLIENTUSESPNEGO" target="_top">client use spnego = yes</a> when communicating
Note:
See TracChangeset
for help on using the changeset viewer.
