- Timestamp:
- May 23, 2008, 6:56:41 AM (17 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
branches/samba-3.0/docs/htmldocs/Samba3-HOWTO/domain-member.html
r44 r134 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.71.0"><link rel="start" href="index.html" title="The Official Samba-3 HOWTO and Reference Guide"><link rel="up" href="type.html" title="Part II. Server Configuration Basics"><link rel="prev" href="samba-bdc.html" title="Chapter 5. Backup Domain Control"><link rel="next" href="StandAloneServer.html" title="Chapter 7. Standalone Servers"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter 6. Domain Membership</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="samba-bdc.html">Prev</a> </td><th width="60%" align="center">Part II. Server Configuration Basics</th><td width="20%" align="right"> <a accesskey="n" href="StandAloneServer.html">Next</a></td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="domain-member"></a>Chapter 6. Domain Membership</h2></div><div><div class="author"><h3 class="author"><span class="firstname">John</span> <span class="othername">H.</span> <span class="surname">Terpstra</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><code class="email"><<a 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="surname">Allison</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><code class="email"><<a 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="surname">Carter</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><code class="email"><<a 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="surname">Tridgell</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><code class="email"><<a 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="surname">Vernooij</span></h3><div class="affiliation"><span class="orgname">The Samba Team<br></span><div class="address"><p><code class="email"><<a 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="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 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#id334840">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#id335474">Manual Creation of Machine Trust Accounts</a></span></dt><dt><span class="sect2"><a href="domain-member.html#id335889">Managing Domain Machine Accounts using NT4 Server Manager</a></span></dt><dt><span class="sect2"><a href="domain-member.html#id336151">On-the-Fly Creation of Machine Trust Accounts</a></span></dt><dt><span class="sect2"><a href="domain-member.html#id336252">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#id336680">Joining an NT4-type Domain with Samba-3</a></span></dt><dt><span class="sect2"><a href="domain-member.html#id337364">Why Is This Better Than <em class="parameter"><code>security = server</code></em>?</a></span></dt></dl></dd><dt><span class="sect1"><a href="domain-member.html#ads-member">Samba ADS Domain Membership</a></span></dt><dd><dl><dt><span class="sect2"><a href="domain-member.html#id337614">Configure <code class="filename">smb.conf</code></a></span></dt><dt><span class="sect2"><a href="domain-member.html#id337793">Configure <code class="filename">/etc/krb5.conf</code></a></span></dt><dt><span class="sect2"><a href="domain-member.html#ads-create-machine-account">Create the Computer Account</a></span></dt><dt><span class="sect2"><a href="domain-member.html#ads-test-server">Testing Server Setup</a></span></dt><dt><span class="sect2"><a href="domain-member.html#ads-test-smbclient">Testing with <span class="application">smbclient</span></a></span></dt><dt><span class="sect2"><a href="domain-member.html#id338826">Notes</a></span></dt></dl></dd><dt><span class="sect1"><a href="domain-member.html#id338895">Sharing User ID Mappings between Samba Domain Members</a></span></dt><dt><span class="sect1"><a href="domain-member.html#id339086">Common Errors</a></span></dt><dd><dl><dt><span class="sect2"><a href="domain-member.html#id339120">Cannot Add Machine Back to Domain</a></span></dt><dt><span class="sect2"><a href="domain-member.html#id339190">Adding Machine to Domain Fails</a></span></dt><dt><span class="sect2"><a href="domain-member.html#id339399">I Can't Join a Windows 2003 PDC</a></span></dt></dl></dd></dl></div><p>2 <a class="indexterm" name="id3 34795"></a>3 <a class="indexterm" name="id3 34802"></a>4 <a class="indexterm" name="id3 34808"></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.73.2"><link rel="start" href="index.html" title="The Official Samba 3.2.x HOWTO and Reference Guide"><link rel="up" href="type.html" title="Part II. Server Configuration Basics"><link rel="prev" href="samba-bdc.html" title="Chapter 5. Backup Domain Control"><link rel="next" href="StandAloneServer.html" title="Chapter 7. Standalone Servers"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter 6. Domain Membership</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="samba-bdc.html">Prev</a> </td><th width="60%" align="center">Part II. Server Configuration Basics</th><td width="20%" align="right"> <a accesskey="n" href="StandAloneServer.html">Next</a></td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="domain-member"></a>Chapter 6. Domain Membership</h2></div><div><div class="author"><h3 class="author"><span class="firstname">John</span> <span class="othername">H.</span> <span class="surname">Terpstra</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><code class="email"><<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="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="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="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="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="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#id357484">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#id358122">Manual Creation of Machine Trust Accounts</a></span></dt><dt><span class="sect2"><a href="domain-member.html#id358537">Managing Domain Machine Accounts using NT4 Server Manager</a></span></dt><dt><span class="sect2"><a href="domain-member.html#id358802">On-the-Fly Creation of Machine Trust Accounts</a></span></dt><dt><span class="sect2"><a href="domain-member.html#id358901">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#id359333">Joining an NT4-type Domain with Samba-3</a></span></dt><dt><span class="sect2"><a href="domain-member.html#id360028">Why Is This Better Than <em class="parameter"><code>security = server</code></em>?</a></span></dt></dl></dd><dt><span class="sect1"><a href="domain-member.html#ads-member">Samba ADS Domain Membership</a></span></dt><dd><dl><dt><span class="sect2"><a href="domain-member.html#id360288">Configure <code class="filename">smb.conf</code></a></span></dt><dt><span class="sect2"><a href="domain-member.html#id360470">Configure <code class="filename">/etc/krb5.conf</code></a></span></dt><dt><span class="sect2"><a href="domain-member.html#ads-create-machine-account">Create the Computer Account</a></span></dt><dt><span class="sect2"><a href="domain-member.html#ads-test-server">Testing Server Setup</a></span></dt><dt><span class="sect2"><a href="domain-member.html#ads-test-smbclient">Testing with <span class="application">smbclient</span></a></span></dt><dt><span class="sect2"><a href="domain-member.html#id361503">Notes</a></span></dt></dl></dd><dt><span class="sect1"><a href="domain-member.html#id361572">Sharing User ID Mappings between Samba Domain Members</a></span></dt><dt><span class="sect1"><a href="domain-member.html#id361768">Common Errors</a></span></dt><dd><dl><dt><span class="sect2"><a href="domain-member.html#id361802">Cannot Add Machine Back to Domain</a></span></dt><dt><span class="sect2"><a href="domain-member.html#id361872">Adding Machine to Domain Fails</a></span></dt><dt><span class="sect2"><a href="domain-member.html#id362092">I Can't Join a Windows 2003 PDC</a></span></dt></dl></dd></dl></div><p> 2 <a class="indexterm" name="id357439"></a> 3 <a class="indexterm" name="id357445"></a> 4 <a class="indexterm" name="id357452"></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="id3 34821"></a>11 <a class="indexterm" name="id3 34828"></a>10 <a class="indexterm" name="id357465"></a> 11 <a class="indexterm" name="id357472"></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="id3 34840"></a>Features and Benefits</h2></div></div></div><p>20 <a class="indexterm" name="id3 34847"></a>21 <a class="indexterm" name="id3 34854"></a>22 <a class="indexterm" name="id3 34861"></a>19 </p><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id357484"></a>Features and Benefits</h2></div></div></div><p> 20 <a class="indexterm" name="id357491"></a> 21 <a class="indexterm" name="id357498"></a> 22 <a class="indexterm" name="id357505"></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="id3 34890"></a>31 <a class="indexterm" name="id3 34896"></a>32 <a class="indexterm" name="id3 34903"></a>33 <a class="indexterm" name="id3 34910"></a>30 <a class="indexterm" name="id357533"></a> 31 <a class="indexterm" name="id357540"></a> 32 <a class="indexterm" name="id357547"></a> 33 <a class="indexterm" name="id357554"></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="id3 34927"></a>38 <a class="indexterm" name="id357571"></a> 39 39 MS Windows workstation users get the benefit of SSO. 40 40 </p></li><li><p> 41 <a class="indexterm" name="id3 34939"></a>42 <a class="indexterm" name="id3 34946"></a>43 <a class="indexterm" name="id3 34952"></a>44 <a class="indexterm" name="id3 34959"></a>41 <a class="indexterm" name="id357583"></a> 42 <a class="indexterm" name="id357589"></a> 43 <a class="indexterm" name="id357596"></a> 44 <a class="indexterm" name="id357603"></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="id3 34972"></a>51 <a class="indexterm" name="id3 34979"></a>50 <a class="indexterm" name="id357616"></a> 51 <a class="indexterm" name="id357623"></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="id3 34997"></a>56 <a class="indexterm" name="id3 35004"></a>57 <a class="indexterm" name="id3 35010"></a>58 <a class="indexterm" name="id3 35017"></a>55 <a class="indexterm" name="id357641"></a> 56 <a class="indexterm" name="id357648"></a> 57 <a class="indexterm" name="id357654"></a> 58 <a class="indexterm" name="id357661"></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="id3 35035"></a>63 <a class="indexterm" name="id3 35042"></a>64 <a class="indexterm" name="id3 35049"></a>62 <a class="indexterm" name="id357679"></a> 63 <a class="indexterm" name="id357686"></a> 64 <a class="indexterm" name="id357693"></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="id3 35061"></a>69 <a class="indexterm" name="id3 35068"></a>70 <a class="indexterm" name="id3 35075"></a>71 <a class="indexterm" name="id3 35081"></a>68 <a class="indexterm" name="id357705"></a> 69 <a class="indexterm" name="id357712"></a> 70 <a class="indexterm" name="id357718"></a> 71 <a class="indexterm" name="id357725"></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="id3 35106"></a>79 <a class="indexterm" name="id3 35112"></a>80 <a class="indexterm" name="id3 35119"></a>81 <a class="indexterm" name="id3 35126"></a>78 <a class="indexterm" name="id357749"></a> 79 <a class="indexterm" name="id357756"></a> 80 <a class="indexterm" name="id357763"></a> 81 <a class="indexterm" name="id357770"></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="id3 35142"></a>88 <a class="indexterm" name="id3 35151"></a>89 <a class="indexterm" name="id3 35158"></a>90 <a class="indexterm" name="id3 35165"></a>91 <a class="indexterm" name="id3 35172"></a>87 <a class="indexterm" name="id357786"></a> 88 <a class="indexterm" name="id357795"></a> 89 <a class="indexterm" name="id357802"></a> 90 <a class="indexterm" name="id357809"></a> 91 <a class="indexterm" name="id357816"></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="id3 35187"></a>100 <a class="indexterm" name="id3 35194"></a>101 <a class="indexterm" name="id3 35201"></a>102 <a class="indexterm" name="id3 35207"></a>99 <a class="indexterm" name="id357831"></a> 100 <a class="indexterm" name="id357838"></a> 101 <a class="indexterm" name="id357844"></a> 102 <a class="indexterm" name="id357851"></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="id3 35222"></a>111 <a class="indexterm" name="id3 35229"></a>112 <a class="indexterm" name="id3 35235"></a>113 A domain security account (stored in the <a class=" indexterm" name="id335243"></a>passdb backend) that has been configured in110 <a class="indexterm" name="id357866"></a> 111 <a class="indexterm" name="id357872"></a> 112 <a class="indexterm" name="id357879"></a> 113 A domain security account (stored in the <a class="link" href="smb.conf.5.html#PASSDBBACKEND">passdb backend</a>) that has been configured in 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="id3 35260"></a>118 <a class="indexterm" name="id3 35267"></a>119 <a class="indexterm" name="id3 35274"></a>120 <a class="indexterm" name="id3 35280"></a>121 <a class="indexterm" name="id3 35287"></a>122 <a class="indexterm" name="id3 35294"></a>117 <a class="indexterm" name="id357907"></a> 118 <a class="indexterm" name="id357914"></a> 119 <a class="indexterm" name="id357921"></a> 120 <a class="indexterm" name="id357928"></a> 121 <a class="indexterm" name="id357934"></a> 122 <a class="indexterm" name="id357941"></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="id3 35314"></a>129 <a class="indexterm" name="id3 35321"></a>130 <a class="indexterm" name="id3 35328"></a>131 <a class="indexterm" name="id3 35335"></a>128 <a class="indexterm" name="id357961"></a> 129 <a class="indexterm" name="id357968"></a> 130 <a class="indexterm" name="id357975"></a> 131 <a class="indexterm" name="id357982"></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="id3 35353"></a>137 <a class="indexterm" name="id3 35360"></a>136 <a class="indexterm" name="id358001"></a> 137 <a class="indexterm" name="id358007"></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="id3 35384"></a>143 <a class="indexterm" name="id358031"></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="id3 35399"></a>146 <a class="indexterm" name="id358046"></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="id3 35412"></a>151 <a class="indexterm" name="id3 35418"></a>150 <a class="indexterm" name="id358059"></a> 151 <a class="indexterm" name="id358066"></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="id3 35432"></a>158 <a class="indexterm" name="id3 35439"></a>157 <a class="indexterm" name="id358079"></a> 158 <a class="indexterm" name="id358086"></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="id3 35456"></a>165 <a class="indexterm" name="id3 35462"></a>164 <a class="indexterm" name="id358103"></a> 165 <a class="indexterm" name="id358110"></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="id3 35474"></a>Manual Creation of Machine Trust Accounts</h3></div></div></div><p>169 <a class="indexterm" name="id3 35482"></a>170 <a class="indexterm" name="id3 35489"></a>171 <a class="indexterm" name="id3 35495"></a>172 <a class="indexterm" name="id3 35501"></a>168 </p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id358122"></a>Manual Creation of Machine Trust Accounts</h3></div></div></div><p> 169 <a class="indexterm" name="id358130"></a> 170 <a class="indexterm" name="id358136"></a> 171 <a class="indexterm" name="id358142"></a> 172 <a class="indexterm" name="id358149"></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="id3 35567"></a>187 <a class="indexterm" name="id3 35573"></a>188 <a class="indexterm" name="id3 35580"></a>186 <a class="indexterm" name="id358214"></a> 187 <a class="indexterm" name="id358221"></a> 188 <a class="indexterm" name="id358227"></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="id3 35599"></a>194 <a class="indexterm" name="id3 35606"></a>193 <a class="indexterm" name="id358246"></a> 194 <a class="indexterm" name="id358253"></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="id3 35646"></a>202 <a class="indexterm" name="id3 35652"></a>203 <a class="indexterm" name="id3 35659"></a>204 <a class="indexterm" name="id3 35666"></a>201 <a class="indexterm" name="id358293"></a> 202 <a class="indexterm" name="id358300"></a> 203 <a class="indexterm" name="id358306"></a> 204 <a class="indexterm" name="id358313"></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="id3 35706"></a>214 <a class="indexterm" name="id3 35712"></a>215 <a class="indexterm" name="id3 35719"></a>213 <a class="indexterm" name="id358353"></a> 214 <a class="indexterm" name="id358360"></a> 215 <a class="indexterm" name="id358366"></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="id3 35742"></a>224 <a class="indexterm" name="id3 35749"></a>225 <a class="indexterm" name="id3 35756"></a>223 <a class="indexterm" name="id358389"></a> 224 <a class="indexterm" name="id358396"></a> 225 <a class="indexterm" name="id358403"></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="id3 35794"></a>236 <a class="indexterm" name="id3 35801"></a>237 <a class="indexterm" name="id3 35808"></a>238 <a class="indexterm" name="id3 35815"></a>235 <a class="indexterm" name="id358442"></a> 236 <a class="indexterm" name="id358448"></a> 237 <a class="indexterm" name="id358455"></a> 238 <a class="indexterm" name="id358462"></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="id3 35835"></a>244 <a class="indexterm" name="id3 35842"></a>245 <a class="indexterm" name="id3 35848"></a>246 <a class="indexterm" name="id3 35855"></a>247 <a class="indexterm" name="id3 35862"></a>243 <a class="indexterm" name="id358482"></a> 244 <a class="indexterm" name="id358489"></a> 245 <a class="indexterm" name="id358496"></a> 246 <a class="indexterm" name="id358502"></a> 247 <a class="indexterm" name="id358509"></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="id3 35870"></a>250 <a class="indexterm" name="id358517"></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="id3 35889"></a>Managing Domain Machine Accounts using NT4 Server Manager</h3></div></div></div><p>258 <a class="indexterm" name="id3 35898"></a>259 <a class="indexterm" name="id3 35904"></a>260 <a class="indexterm" name="id3 35911"></a>261 A working <a class=" indexterm" name="id335918"></a>add machine scriptis essential257 </p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id358537"></a>Managing Domain Machine Accounts using NT4 Server Manager</h3></div></div></div><p> 258 <a class="indexterm" name="id358545"></a> 259 <a class="indexterm" name="id358552"></a> 260 <a class="indexterm" name="id358558"></a> 261 A working <a class="link" href="smb.conf.5.html#ADDMACHINESCRIPT">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="id3 35930"></a>266 <a class="indexterm" name="id3 35937"></a>267 <a class="indexterm" name="id3 35944"></a>268 <a class="indexterm" name="id3 35950"></a>265 <a class="indexterm" name="id358581"></a> 266 <a class="indexterm" name="id358587"></a> 267 <a class="indexterm" name="id358594"></a> 268 <a class="indexterm" name="id358601"></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="id3 35987"></a>276 <a class="indexterm" name="id3 35993"></a>275 <a class="indexterm" name="id358637"></a> 276 <a class="indexterm" name="id358644"></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. … … 281 281 </p><p> 282 282 Further information about these tools may be obtained from Knowledge Base articles 283 <a href="http://support.microsoft.com/default.aspx?scid=kb;en-us;173673" target="_top">173673</a>, and284 <a href="http://support.microsoft.com/default.aspx?scid=kb;en-us;172540" target="_top">172540</a>285 </p><p> 286 <a class="indexterm" name="id3 36034"></a>287 <a class="indexterm" name="id3 36040"></a>283 <a class="ulink" href="http://support.microsoft.com/default.aspx?scid=kb;en-us;173673" target="_top">173673</a>, and 284 <a class="ulink" href="http://support.microsoft.com/default.aspx?scid=kb;en-us;172540" target="_top">172540</a> 285 </p><p> 286 <a class="indexterm" name="id358684"></a> 287 <a class="indexterm" name="id358691"></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="id3 36055"></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="id358706"></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="id3 36151"></a>On-the-Fly Creation of Machine Trust Accounts</h3></div></div></div><p>307 <a class="indexterm" name="id3 36159"></a>306 </p></li></ol></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id358802"></a>On-the-Fly Creation of Machine Trust Accounts</h3></div></div></div><p> 307 <a class="indexterm" name="id358810"></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="id3 36173"></a>312 <a class="indexterm" name="id3 36183"></a>313 <a class="indexterm" name="id3 36189"></a>311 <a class="indexterm" name="id358824"></a> 312 <a class="indexterm" name="id358833"></a> 313 <a class="indexterm" name="id358840"></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="id3 36208"></a>320 <a class="indexterm" name="id3 36215"></a>319 <a class="indexterm" name="id358859"></a> 320 <a class="indexterm" name="id358865"></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="id3 36237"></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="id3 36252"></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="id358887"></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="id358901"></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="id3 36261"></a>Windows 200x/XP Professional Client</h4></div></div></div><p>327 <a class="indexterm" name="id3 36269"></a>328 <a class="indexterm" name="id3 36276"></a>329 <a class="indexterm" name="id3 36285"></a>330 <a class="indexterm" name="id3 36292"></a>326 </p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id358911"></a>Windows 200x/XP Professional Client</h4></div></div></div><p> 327 <a class="indexterm" name="id358918"></a> 328 <a class="indexterm" name="id358925"></a> 329 <a class="indexterm" name="id358934"></a> 330 <a class="indexterm" name="id358941"></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="id3 36309"></a>338 <a class="indexterm" name="id3 36315"></a>337 <a class="indexterm" name="id358958"></a> 338 <a class="indexterm" name="id358965"></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="id3 36332"></a>343 <a class="indexterm" name="id3 36339"></a>344 <a class="indexterm" name="id3 36346"></a>345 <a class="indexterm" name="id3 36353"></a>342 <a class="indexterm" name="id358982"></a> 343 <a class="indexterm" name="id358989"></a> 344 <a class="indexterm" name="id358996"></a> 345 <a class="indexterm" name="id359002"></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>, 348 348 then this is easily mapped to <code class="constant">root</code> in the file named in the <code class="filename">smb.conf</code> parameter 349 <a class=" indexterm" name="id336375"></a>username map = /etc/samba/smbusers.349 <a class="link" href="smb.conf.5.html#USERNAMEMAP">username map = /etc/samba/smbusers</a>. 350 350 </p><p> 351 <a class="indexterm" name="id3 36385"></a>352 <a class="indexterm" name="id3 36392"></a>353 <a class="indexterm" name="id3 36399"></a>351 <a class="indexterm" name="id359039"></a> 352 <a class="indexterm" name="id359045"></a> 353 <a class="indexterm" name="id359052"></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="id3 36410"></a>Windows NT4 Client</h4></div></div></div><p>357 <a class="indexterm" name="id3 36417"></a>358 <a class="indexterm" name="id3 36424"></a>359 <a class="indexterm" name="id3 36431"></a>356 </p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id359063"></a>Windows NT4 Client</h4></div></div></div><p> 357 <a class="indexterm" name="id359071"></a> 358 <a class="indexterm" name="id359078"></a> 359 <a class="indexterm" name="id359084"></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="id3 36449"></a>367 <a class="indexterm" name="id3 36456"></a>368 <a class="indexterm" name="id3 36463"></a>369 <a class="indexterm" name="id3 36470"></a>366 <a class="indexterm" name="id359103"></a> 367 <a class="indexterm" name="id359109"></a> 368 <a class="indexterm" name="id359116"></a> 369 <a class="indexterm" name="id359123"></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="id3 36487"></a>Samba Client</h4></div></div></div><p>375 <a class="indexterm" name="id3 36495"></a>376 Joining a Samba client to a domain is documented in <a href="domain-member.html#domain-member-server" title="Domain Member Server">the next section</a>.374 </p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id359140"></a>Samba Client</h4></div></div></div><p> 375 <a class="indexterm" name="id359148"></a> 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="id3 36523"></a>379 <a class="indexterm" name="id3 36530"></a>380 <a class="indexterm" name="id3 36537"></a>381 <a class="indexterm" name="id3 36544"></a>378 <a class="indexterm" name="id359177"></a> 379 <a class="indexterm" name="id359184"></a> 380 <a class="indexterm" name="id359190"></a> 381 <a class="indexterm" name="id359197"></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="id3 36559"></a>391 <a class="indexterm" name="id3 36568"></a>392 <a class="indexterm" name="id3 36575"></a>393 <a class="indexterm" name="id3 36582"></a>394 <a class="indexterm" name="id3 36589"></a>395 <a class="indexterm" name="id3 36596"></a>396 <a class="indexterm" name="id3 36602"></a>397 <a class="indexterm" name="id3 36609"></a>390 <a class="indexterm" name="id359213"></a> 391 <a class="indexterm" name="id359222"></a> 392 <a class="indexterm" name="id359229"></a> 393 <a class="indexterm" name="id359235"></a> 394 <a class="indexterm" name="id359242"></a> 395 <a class="indexterm" name="id359249"></a> 396 <a class="indexterm" name="id359256"></a> 397 <a class="indexterm" name="id359262"></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="id3 36623"></a>405 <a class="indexterm" name="id3 36630"></a>406 <a class="indexterm" name="id3 36637"></a>404 <a class="indexterm" name="id359277"></a> 405 <a class="indexterm" name="id359284"></a> 406 <a class="indexterm" name="id359290"></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="id3 36649"></a>413 <a class="indexterm" name="id3 36656"></a>414 <a class="indexterm" name="id3 36663"></a>415 Please refer to <a href="samba-pdc.html" title="Chapter 4. Domain Control">Domain Control</a>, for more information regarding412 <a class="indexterm" name="id359303"></a> 413 <a class="indexterm" name="id359310"></a> 414 <a class="indexterm" name="id359317"></a> 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="id3 36680"></a>Joining an NT4-type Domain with Samba-3</h3></div></div></div><p><ahref="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="id3 36763"></a>419 </p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id359333"></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="id359416"></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="id3 36778"></a>424 <a class="indexterm" name="id3 36785"></a>425 <a class="indexterm" name="id3 36792"></a>426 <a class="indexterm" name="id3 36798"></a>427 Change (or add) your <a class=" indexterm" name="id336805"></a>securityline in the [global] section423 <a class="indexterm" name="id359431"></a> 424 <a class="indexterm" name="id359438"></a> 425 <a class="indexterm" name="id359445"></a> 426 <a class="indexterm" name="id359452"></a> 427 Change (or add) your <a class="link" href="smb.conf.5.html#SECURITY">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="id3 36824"></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="id359481"></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 432 432 domain security context. 433 433 </p><p> 434 Next change the <a class=" indexterm" name="id336848"></a>workgroupline in the <em class="parameter"><code>[global]</code></em>434 Next change the <a class="link" href="smb.conf.5.html#WORKGROUP">workgroup</a> line in the <em class="parameter"><code>[global]</code></em> 435 435 section to read: 436 </p><table class="simplelist" border="0" summary="Simple list"><tr><td><a class="indexterm" name="id3 36866"></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="id359526"></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="id3 36883"></a>440 <a class="indexterm" name="id3 36890"></a>441 You must also have the parameter <a class=" indexterm" name="id336896"></a>encrypt passwords439 <a class="indexterm" name="id359541"></a> 440 <a class="indexterm" name="id359548"></a> 441 You must also have the parameter <a class="link" href="smb.conf.5.html#ENCRYPTPASSWORDS">encrypt passwords</a> 442 442 set to <code class="constant">yes</code> in order for your users to authenticate to the NT PDC. 443 443 This is the default setting if this parameter is not specified. There is no need to specify this 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="id3 36921"></a>447 <a class="indexterm" name="id3 36928"></a>448 <a class="indexterm" name="id3 36934"></a>449 <a class="indexterm" name="id3 36941"></a>450 Finally, add (or modify) a <a class=" indexterm" name="id336948"></a>password serverline in the [global]446 <a class="indexterm" name="id359584"></a> 447 <a class="indexterm" name="id359590"></a> 448 <a class="indexterm" name="id359597"></a> 449 <a class="indexterm" name="id359604"></a> 450 Finally, add (or modify) a <a class="link" href="smb.conf.5.html#PASSWORDSERVER">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="id3 36961"></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="id359627"></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="id3 36979"></a>460 <a class="indexterm" name="id3 36986"></a>461 <a class="indexterm" name="id3 36993"></a>462 <a class="indexterm" name="id3 37000"></a>459 <a class="indexterm" name="id359645"></a> 460 <a class="indexterm" name="id359652"></a> 461 <a class="indexterm" name="id359658"></a> 462 <a class="indexterm" name="id359665"></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="id3 37014"></a><em class="parameter"><code>password server = *</code></em></td></tr></table><p>466 <a class="indexterm" name="id3 37026"></a>465 </p><table class="simplelist" border="0" summary="Simple list"><tr><td><a class="indexterm" name="id359679"></a><em class="parameter"><code>password server = *</code></em></td></tr></table><p> 466 <a class="indexterm" name="id359690"></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="id3 37039"></a>473 <a class="indexterm" name="id359703"></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="id3 37072"></a>479 <a class="indexterm" name="id3 37079"></a>480 <a class="indexterm" name="id3 37085"></a>481 <a class="indexterm" name="id3 37092"></a>478 <a class="indexterm" name="id359736"></a> 479 <a class="indexterm" name="id359743"></a> 480 <a class="indexterm" name="id359749"></a> 481 <a class="indexterm" name="id359756"></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="id3 37113"></a>487 <a class="indexterm" name="id3 37120"></a>488 <a class="indexterm" name="id3 37127"></a>489 <a class="indexterm" name="id3 37133"></a>486 <a class="indexterm" name="id359777"></a> 487 <a class="indexterm" name="id359784"></a> 488 <a class="indexterm" name="id359791"></a> 489 <a class="indexterm" name="id359798"></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="id3 37165"></a>501 <a class="indexterm" name="id3 37176"></a>502 <a class="indexterm" name="id3 37183"></a>500 <a class="indexterm" name="id359829"></a> 501 <a class="indexterm" name="id359840"></a> 502 <a class="indexterm" name="id359847"></a> 503 503 Where Active Directory is used, the command used to join the ADS domain is: 504 504 </p><pre class="screen"> … … 510 510 </pre><p> 511 511 </p><p> 512 Refer to the <code class="literal">net</code> man page and to <a href="NetCommand.html" title="Chapter 13. Remote and Local Management: The Net Command">the chapter on remote512 Refer to the <code class="literal">net</code> man page and to <a class="link" href="NetCommand.html" title="Chapter 13. Remote and Local Management: The Net Command">the chapter on remote 513 513 administration</a> for further information. 514 514 </p><p> 515 <a class="indexterm" name="id3 37237"></a>516 <a class="indexterm" name="id3 37244"></a>517 <a class="indexterm" name="id3 37251"></a>515 <a class="indexterm" name="id359901"></a> 516 <a class="indexterm" name="id359908"></a> 517 <a class="indexterm" name="id359915"></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="id3 37262"></a>522 <a class="indexterm" name="id3 37271"></a>523 <a class="indexterm" name="id3 37278"></a>524 <a class="indexterm" name="id3 37285"></a>521 <a class="indexterm" name="id359926"></a> 522 <a class="indexterm" name="id359935"></a> 523 <a class="indexterm" name="id359942"></a> 524 <a class="indexterm" name="id359949"></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="id3 37310"></a>531 <a class="indexterm" name="id3 37316"></a>530 <a class="indexterm" name="id359974"></a> 531 <a class="indexterm" name="id359980"></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="id3 37328"></a>537 <a class="indexterm" name="id3 37335"></a>538 <a class="indexterm" name="id3 37342"></a>536 <a class="indexterm" name="id359992"></a> 537 <a class="indexterm" name="id359999"></a> 538 <a class="indexterm" name="id360006"></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="id3 37364"></a>Why Is This Better Than <em class="parameter"><code>security = server</code></em>?</h3></div></div></div><p>546 <a class="indexterm" name="id3 37378"></a>547 <a class="indexterm" name="id3 37385"></a>548 <a class="indexterm" name="id3 37391"></a>545 </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id360028"></a>Why Is This Better Than <em class="parameter"><code>security = server</code></em>?</h3></div></div></div><p> 546 <a class="indexterm" name="id360042"></a> 547 <a class="indexterm" name="id360049"></a> 548 <a class="indexterm" name="id360056"></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 551 551 domain security Samba server, there needs to be a local UNIX user fred to represent that user in the UNIX file 552 system. This is similar to the older Samba security mode <a class=" indexterm" name="id337405"></a>security = server, where Samba would pass through the authentication request to a Windows552 system. This is similar to the older Samba security mode <a class="link" href="smb.conf.5.html#SECURITY">security = server</a>, where Samba would pass through the authentication request to a Windows 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="id3 37416"></a>556 <a class="indexterm" name="id3 37423"></a>557 <a class="indexterm" name="id3 37430"></a>558 Please refer to <a href="winbind.html" title="Chapter 24. Winbind: Use of Domain Accounts">Winbind: Use of Domain Accounts</a>, for information on a system555 <a class="indexterm" name="id360084"></a> 556 <a class="indexterm" name="id360091"></a> 557 <a class="indexterm" name="id360097"></a> 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="id3 37448"></a>562 <a class="indexterm" name="id3 37454"></a>563 <a class="indexterm" name="id3 37461"></a>561 <a class="indexterm" name="id360115"></a> 562 <a class="indexterm" name="id360122"></a> 563 <a class="indexterm" name="id360129"></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="id3 37475"></a>571 <a class="indexterm" name="id3 37482"></a>572 <a class="indexterm" name="id3 37488"></a>573 In addition, with <a class=" indexterm" name="id337495"></a>security = server, every Samba daemon on a server has to570 <a class="indexterm" name="id360143"></a> 571 <a class="indexterm" name="id360149"></a> 572 <a class="indexterm" name="id360156"></a> 573 In addition, with <a class="link" href="smb.conf.5.html#SECURITY">security = server</a>, every Samba daemon on a server has to 574 574 keep a connection open to the authenticating server for as long as that daemon lasts. This can drain the 575 575 connection resources on a Microsoft NT server and cause it to run out of available connections. With 576 <a class=" indexterm" name="id337504"></a>security = domain, however, the Samba daemons connect to the PDC or BDC576 <a class="link" href="smb.conf.5.html#SECURITY">security = domain</a>, however, the Samba daemons connect to the PDC or BDC 577 577 only for as long as is necessary to authenticate the user and then drop the connection, thus conserving PDC 578 578 connection resources. 579 579 </p><p> 580 <a class="indexterm" name="id3 37516"></a>581 <a class="indexterm" name="id3 37523"></a>582 <a class="indexterm" name="id3 37530"></a>583 <a class="indexterm" name="id3 37536"></a>580 <a class="indexterm" name="id360191"></a> 581 <a class="indexterm" name="id360197"></a> 582 <a class="indexterm" name="id360204"></a> 583 <a class="indexterm" name="id360210"></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 … … 587 587 </p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p> 588 588 Much of the text of this document was first published in the Web magazine 589 <a href="http://www.linuxworld.com" target="_top"><span class="emphasis"><em>LinuxWorld</em></span></a> as the article <ahref="http://www.linuxworld.com/linuxworld/lw-1998-10/lw-10-samba.html" target="_top">http://www.linuxworld.com/linuxworld/lw-1998-10/lw-10-samba.html</a>589 <a class="ulink" href="http://www.linuxworld.com" target="_top"><span class="emphasis"><em>LinuxWorld</em></span></a> as the article <a class="ulink" href="http://www.linuxworld.com/linuxworld/lw-1998-10/lw-10-samba.html" target="_top">http://www.linuxworld.com/linuxworld/lw-1998-10/lw-10-samba.html</a> 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="id3 37583"></a>593 <a class="indexterm" name="id3 37589"></a>594 <a class="indexterm" name="id3 37598"></a>595 <a class="indexterm" name="id3 37605"></a>592 <a class="indexterm" name="id360257"></a> 593 <a class="indexterm" name="id360263"></a> 594 <a class="indexterm" name="id360272"></a> 595 <a class="indexterm" name="id360279"></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="id3 37614"></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="id360288"></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="id3 37639"></a><em class="parameter"><code>realm = your.kerberos.REALM</code></em></td></tr><tr><td><a class="indexterm" name="id337652"></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="id337672"></a><em class="parameter"><code>encrypt passwords = yes</code></em></td></tr></table><p>601 <a class="indexterm" name="id3 37687"></a>602 <a class="indexterm" name="id3 37693"></a>603 <a class="indexterm" name="id3 37700"></a>604 <a class="indexterm" name="id3 37707"></a>605 <a class="indexterm" name="id3 37714"></a>600 </p><table class="simplelist" border="0" summary="Simple list"><tr><td><a class="indexterm" name="id360314"></a><em class="parameter"><code>realm = your.kerberos.REALM</code></em></td></tr><tr><td><a class="indexterm" name="id360325"></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="id360344"></a><em class="parameter"><code>encrypt passwords = yes</code></em></td></tr></table><p> 601 <a class="indexterm" name="id360358"></a> 602 <a class="indexterm" name="id360364"></a> 603 <a class="indexterm" name="id360371"></a> 604 <a class="indexterm" name="id360378"></a> 605 <a class="indexterm" name="id360384"></a> 606 606 In case samba cannot correctly identify the appropriate ADS server using the realm name, use the 607 <a class=" indexterm" name="id337721"></a>password serveroption in <code class="filename">smb.conf</code>:608 </p><table class="simplelist" border="0" summary="Simple list"><tr><td><a class="indexterm" name="id3 37740"></a><em class="parameter"><code>password server = your.kerberos.server</code></em></td></tr></table><p>607 <a class="link" href="smb.conf.5.html#PASSWORDSERVER">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="id360414"></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="id3 37765"></a>615 <a class="indexterm" name="id3 37772"></a>614 <a class="indexterm" name="id360438"></a> 615 <a class="indexterm" name="id360445"></a> 616 616 You do <span class="emphasis"><em>not</em></span> need an smbpasswd file, and older clients will be authenticated as 617 if <a class=" indexterm" name="id337783"></a>security = domain, although it will not do any harm and617 if <a class="link" href="smb.conf.5.html#SECURITY">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="id3 37793"></a>Configure <code class="filename">/etc/krb5.conf</code></h3></div></div></div><p>620 <a class="indexterm" name="id3 37806"></a>621 <a class="indexterm" name="id3 37812"></a>622 <a class="indexterm" name="id3 37822"></a>623 <a class="indexterm" name="id3 37828"></a>619 </p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id360470"></a>Configure <code class="filename">/etc/krb5.conf</code></h3></div></div></div><p> 620 <a class="indexterm" name="id360482"></a> 621 <a class="indexterm" name="id360489"></a> 622 <a class="indexterm" name="id360498"></a> 623 <a class="indexterm" name="id360505"></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="id3 37845"></a>628 <a class="indexterm" name="id3 37852"></a>629 <a class="indexterm" name="id3 37859"></a>630 <a class="indexterm" name="id3 37865"></a>631 <a class="indexterm" name="id3 37872"></a>627 <a class="indexterm" name="id360522"></a> 628 <a class="indexterm" name="id360528"></a> 629 <a class="indexterm" name="id360535"></a> 630 <a class="indexterm" name="id360542"></a> 631 <a class="indexterm" name="id360548"></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="id3 37891"></a>639 <a class="indexterm" name="id3 37898"></a>640 <a class="indexterm" name="id3 37904"></a>641 <a class="indexterm" name="id3 37911"></a>642 <a class="indexterm" name="id3 37918"></a>643 <a class="indexterm" name="id3 37925"></a>638 <a class="indexterm" name="id360567"></a> 639 <a class="indexterm" name="id360574"></a> 640 <a class="indexterm" name="id360581"></a> 641 <a class="indexterm" name="id360588"></a> 642 <a class="indexterm" name="id360594"></a> 643 <a class="indexterm" name="id360601"></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 646 Microsoft Windows 2000 Kerberos <a href="http://www.microsoft.com/windows2000/techinfo/planning/security/kerbsteps.asp" target="_top">Interoperability</a>646 Microsoft Windows 2000 Kerberos <a class="ulink" href="http://www.microsoft.com/windows2000/techinfo/planning/security/kerbsteps.asp" target="_top">Interoperability</a> 647 647 guide. Another very useful document that may be referred to for general information regarding Kerberos 648 interoperability is <a href="http://www.ietf.org/rfc/rfc1510.txt?number=1510" target="_top">RFC1510</a>. This RFC648 interoperability is <a class="ulink" href="http://www.ietf.org/rfc/rfc1510.txt?number=1510" target="_top">RFC1510</a>. This RFC 649 649 explains much of the magic behind the operation of Kerberos. 650 650 </p><p> 651 <a class="indexterm" name="id3 37951"></a>652 <a class="indexterm" name="id3 37958"></a>653 <a class="indexterm" name="id3 37965"></a>654 <a class="indexterm" name="id3 37971"></a>655 <a class="indexterm" name="id3 37978"></a>656 <a class="indexterm" name="id3 37985"></a>651 <a class="indexterm" name="id360628"></a> 652 <a class="indexterm" name="id360634"></a> 653 <a class="indexterm" name="id360641"></a> 654 <a class="indexterm" name="id360648"></a> 655 <a class="indexterm" name="id360655"></a> 656 <a class="indexterm" name="id360662"></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="id3 38004"></a>662 <a class="indexterm" name="id360680"></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="id3 38027"></a>677 <a class="indexterm" name="id360704"></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="id3 38046"></a>695 <a class="indexterm" name="id3 38052"></a>694 <a class="indexterm" name="id360722"></a> 695 <a class="indexterm" name="id360729"></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="id3 38075"></a>701 <a class="indexterm" name="id3 38082"></a>702 <a class="indexterm" name="id3 38088"></a>703 <a class="indexterm" name="id3 38095"></a>700 <a class="indexterm" name="id360752"></a> 701 <a class="indexterm" name="id360758"></a> 702 <a class="indexterm" name="id360765"></a> 703 <a class="indexterm" name="id360772"></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="id3 38113"></a>712 <a class="indexterm" name="id3 38120"></a>713 <a class="indexterm" name="id3 38127"></a>711 <a class="indexterm" name="id360790"></a> 712 <a class="indexterm" name="id360796"></a> 713 <a class="indexterm" name="id360803"></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="id3 38143"></a>719 <a class="indexterm" name="id3 38150"></a>720 <a class="indexterm" name="id3 38157"></a>721 <a class="indexterm" name="id3 38164"></a>718 <a class="indexterm" name="id360820"></a> 719 <a class="indexterm" name="id360827"></a> 720 <a class="indexterm" name="id360833"></a> 721 <a class="indexterm" name="id360840"></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="id3 38180"></a>726 <a class="indexterm" name="id3 38187"></a>725 <a class="indexterm" name="id360856"></a> 726 <a class="indexterm" name="id360863"></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="id3 38198"></a>730 <a class="indexterm" name="id3 38204"></a>731 <a class="indexterm" name="id3 38211"></a>732 <a class="indexterm" name="id3 38218"></a>729 <a class="indexterm" name="id360874"></a> 730 <a class="indexterm" name="id360881"></a> 731 <a class="indexterm" name="id360887"></a> 732 <a class="indexterm" name="id360894"></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="id3 38230"></a>738 <a class="indexterm" name="id3 38237"></a>739 <a class="indexterm" name="id3 38243"></a>737 <a class="indexterm" name="id360906"></a> 738 <a class="indexterm" name="id360913"></a> 739 <a class="indexterm" name="id360920"></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="id3 38265"></a>745 <a class="indexterm" name="id3 38271"></a>746 <a class="indexterm" name="id3 38278"></a>747 <a class="indexterm" name="id3 38285"></a>748 If all you want is Kerberos support in <span class="application">smbclient</span>, then you can skip directly to <a href="domain-member.html#ads-test-smbclient" title="Testing with smbclient">Testing with <span class="application">smbclient</span></a> now. <a href="domain-member.html#ads-create-machine-account" title="Create the Computer Account">Create the Computer Account</a> and <ahref="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>744 <a class="indexterm" name="id360941"></a> 745 <a class="indexterm" name="id360948"></a> 746 <a class="indexterm" name="id360955"></a> 747 <a class="indexterm" name="id360962"></a> 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="id3 38351"></a>752 <a class="indexterm" name="id3 38358"></a>753 <a class="indexterm" name="id3 38364"></a>754 <a class="indexterm" name="id3 38371"></a>751 <a class="indexterm" name="id361027"></a> 752 <a class="indexterm" name="id361034"></a> 753 <a class="indexterm" name="id361041"></a> 754 <a class="indexterm" name="id361048"></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="id3 38402"></a>764 <a class="indexterm" name="id3 38408"></a>765 <a class="indexterm" name="id3 38415"></a>766 <a class="indexterm" name="id3 38422"></a>767 <a class="indexterm" name="id3 38429"></a>768 <a class="indexterm" name="id3 38436"></a>763 <a class="indexterm" name="id361078"></a> 764 <a class="indexterm" name="id361085"></a> 765 <a class="indexterm" name="id361092"></a> 766 <a class="indexterm" name="id361098"></a> 767 <a class="indexterm" name="id361105"></a> 768 <a class="indexterm" name="id361112"></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="id3 38482"></a>779 <a class="indexterm" name="id3 38489"></a>780 <a class="indexterm" name="id3 38496"></a>781 <a class="indexterm" name="id3 38502"></a>778 <a class="indexterm" name="id361158"></a> 779 <a class="indexterm" name="id361165"></a> 780 <a class="indexterm" name="id361172"></a> 781 <a class="indexterm" name="id361179"></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="id3 38546"></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="id361222"></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="id3 38564"></a>795 <a class="indexterm" name="id3 38571"></a>796 <a class="indexterm" name="id3 38578"></a>794 <a class="indexterm" name="id361241"></a> 795 <a class="indexterm" name="id361248"></a> 796 <a class="indexterm" name="id361255"></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="id3 38596"></a>801 <a class="indexterm" name="id3 38603"></a>800 <a class="indexterm" name="id361273"></a> 801 <a class="indexterm" name="id361280"></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="id3 38635"></a>807 <a class="indexterm" name="id3 38642"></a>808 <a class="indexterm" name="id3 38649"></a>806 <a class="indexterm" name="id361312"></a> 807 <a class="indexterm" name="id361319"></a> 808 <a class="indexterm" name="id361325"></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="id3 38679"></a>814 <a class="indexterm" name="id3 38686"></a>815 <a class="indexterm" name="id3 38692"></a>813 <a class="indexterm" name="id361355"></a> 814 <a class="indexterm" name="id361362"></a> 815 <a class="indexterm" name="id361369"></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="id3 38707"></a>821 <a class="indexterm" name="id3 38714"></a>822 <a class="indexterm" name="id3 38723"></a>820 <a class="indexterm" name="id361384"></a> 821 <a class="indexterm" name="id361391"></a> 822 <a class="indexterm" name="id361400"></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="id3 38748"></a>829 <a class="indexterm" name="id3 38755"></a>830 <a class="indexterm" name="id3 38762"></a>828 <a class="indexterm" name="id361424"></a> 829 <a class="indexterm" name="id361431"></a> 830 <a class="indexterm" name="id361438"></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="id3 38787"></a>834 <a class="indexterm" name="id3 38794"></a>835 <a class="indexterm" name="id3 38800"></a>833 <a class="indexterm" name="id361463"></a> 834 <a class="indexterm" name="id361470"></a> 835 <a class="indexterm" name="id361477"></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="id3 38826"></a>Notes</h3></div></div></div><p>840 <a class="indexterm" name="id3 38834"></a>841 <a class="indexterm" name="id3 38841"></a>842 <a class="indexterm" name="id3 38847"></a>839 </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id361503"></a>Notes</h3></div></div></div><p> 840 <a class="indexterm" name="id361510"></a> 841 <a class="indexterm" name="id361517"></a> 842 <a class="indexterm" name="id361524"></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="id3 38859"></a>847 <a class="indexterm" name="id3 38865"></a>848 <a class="indexterm" name="id3 38872"></a>846 <a class="indexterm" name="id361535"></a> 847 <a class="indexterm" name="id361542"></a> 848 <a class="indexterm" name="id361549"></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="id3 38895"></a>Sharing User ID Mappings between Samba Domain Members</h2></div></div></div><p>852 <a class="indexterm" name="id3 38903"></a>853 <a class="indexterm" name="id3 38910"></a>854 <a class="indexterm" name="id3 38917"></a>855 <a class="indexterm" name="id3 38923"></a>851 </p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id361572"></a>Sharing User ID Mappings between Samba Domain Members</h2></div></div></div><p> 852 <a class="indexterm" name="id361580"></a> 853 <a class="indexterm" name="id361587"></a> 854 <a class="indexterm" name="id361593"></a> 855 <a class="indexterm" name="id361600"></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="id3 38940"></a>860 <a class="indexterm" name="id3 38947"></a>861 <a class="indexterm" name="id3 38954"></a>859 <a class="indexterm" name="id361617"></a> 860 <a class="indexterm" name="id361624"></a> 861 <a class="indexterm" name="id361630"></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="id3 38969"></a>867 <a class="indexterm" name="id3 38976"></a>866 <a class="indexterm" name="id361646"></a> 867 <a class="indexterm" name="id361653"></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="id3 38999"></a><em class="parameter"><code>ldap idmap suffix = ou=Idmap</code></em></td></tr></table><p>870 See the <code class="filename">smb.conf</code> man page entry for the <a class=" indexterm" name="id339020"></a>ldap idmap suffix869 </p><table class="simplelist" border="0" summary="Simple list"><tr><td><a class="indexterm" name="id361676"></a><em class="parameter"><code>ldap idmap suffix = ou=Idmap</code></em></td></tr></table><p> 870 See the <code class="filename">smb.conf</code> man page entry for the <a class="link" href="smb.conf.5.html#LDAPIDMAPSUFFIX">ldap idmap suffix</a> 871 871 parameter for further information. 872 872 </p><p> 873 <a class="indexterm" name="id3 39031"></a>874 <a class="indexterm" name="id3 39038"></a>875 <a class="indexterm" name="id3 39045"></a>876 Do not forget to specify also the <a class=" indexterm" name="id339052"></a>ldap admin dn873 <a class="indexterm" name="id361710"></a> 874 <a class="indexterm" name="id361716"></a> 875 <a class="indexterm" name="id361723"></a> 876 Do not forget to specify also the <a class="link" href="smb.conf.5.html#LDAPADMINDN">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: 878 878 </p><pre class="screen"> … … 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="id3 39086"></a>Common Errors</h2></div></div></div><p>884 <a class="indexterm" name="id3 39094"></a>885 <a class="indexterm" name="id3 39100"></a>883 </p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id361768"></a>Common Errors</h2></div></div></div><p> 884 <a class="indexterm" name="id361776"></a> 885 <a class="indexterm" name="id361782"></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="id3 39120"></a>Cannot Add Machine Back to Domain</h3></div></div></div><p>894 <a class="indexterm" name="id3 39128"></a>895 <a class="indexterm" name="id3 39135"></a>893 </p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id361802"></a>Cannot Add Machine Back to Domain</h3></div></div></div><p> 894 <a class="indexterm" name="id361810"></a> 895 <a class="indexterm" name="id361817"></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="id3 39154"></a>902 <a class="indexterm" name="id3 39161"></a>901 <a class="indexterm" name="id361836"></a> 902 <a class="indexterm" name="id361843"></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="id3 39190"></a>Adding Machine to Domain Fails</h3></div></div></div><p>911 <a class="indexterm" name="id3 39198"></a>912 <a class="indexterm" name="id3 39204"></a>910 </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id361872"></a>Adding Machine to Domain Fails</h3></div></div></div><p> 911 <a class="indexterm" name="id361880"></a> 912 <a class="indexterm" name="id361886"></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="id3 39223"></a>918 You should check that there is an <a class=" indexterm" name="id339230"></a>add machine scriptin your <code class="filename">smb.conf</code>917 <a class="indexterm" name="id361905"></a> 918 You should check that there is an <a class="link" href="smb.conf.5.html#ADDMACHINESCRIPT">add machine script</a> in your <code class="filename">smb.conf</code> 919 919 file. If there is not, please add one that is appropriate for your OS platform. If a script 920 has been defined, you will need to debug its operation. Increase the <a class=" indexterm" name="id339245"></a>log level920 has been defined, you will need to debug its operation. Increase the <a class="link" href="smb.conf.5.html#LOGLEVEL">log level</a> 921 921 in the <code class="filename">smb.conf</code> file to level 10, then try to rejoin the domain. Check the logs to see which 922 922 operation is failing. … … 924 924 Possible causes include: 925 925 </p><div class="itemizedlist"><ul type="disc"><li><p> 926 <a class="indexterm" name="id3 39268"></a>927 <a class="indexterm" name="id3 39275"></a>926 <a class="indexterm" name="id361958"></a> 927 <a class="indexterm" name="id361965"></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="id3 39286"></a>931 <a class="indexterm" name="id3 39293"></a>930 <a class="indexterm" name="id361976"></a> 931 <a class="indexterm" name="id361983"></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="id3 39308"></a>936 <a class="indexterm" name="id3 39315"></a>935 <a class="indexterm" name="id361998"></a> 936 <a class="indexterm" name="id362005"></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="id3 39332"></a>940 <a class="indexterm" name="id3 39339"></a>939 <a class="indexterm" name="id362022"></a> 940 <a class="indexterm" name="id362029"></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="id3 39367"></a>948 <a class="indexterm" name="id3 39374"></a>949 <a class="indexterm" name="id3 39381"></a>950 The <a class=" indexterm" name="id339388"></a>add machine scriptdoes not create the947 <a class="indexterm" name="id362057"></a> 948 <a class="indexterm" name="id362064"></a> 949 <a class="indexterm" name="id362071"></a> 950 The <a class="link" href="smb.conf.5.html#ADDMACHINESCRIPT">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="id3 39399"></a>I Can't Join a Windows 2003 PDC</h3></div></div></div><p>954 <a class="indexterm" name="id3 39406"></a>955 <a class="indexterm" name="id3 39413"></a>956 <a class="indexterm" name="id3 39420"></a>957 <a class="indexterm" name="id3 39427"></a>953 </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id362092"></a>I Can't Join a Windows 2003 PDC</h3></div></div></div><p> 954 <a class="indexterm" name="id362100"></a> 955 <a class="indexterm" name="id362107"></a> 956 <a class="indexterm" name="id362113"></a> 957 <a class="indexterm" name="id362120"></a> 958 958 Windows 2003 requires SMB signing. Client-side SMB signing has been implemented in Samba-3.0. 959 Set <a class=" indexterm" name="id339434"></a>client use spnego = yeswhen communicating959 Set <a class="link" href="smb.conf.5.html#CLIENTUSESPNEGO">client use spnego = yes</a> when communicating 960 960 with a Windows 2003 server. This will not interfere with other Windows clients that do not 961 961 support the more advanced security features of Windows 2003 because the client will simply 962 negotiate a protocol tha both it and the server suppport. This is a well-known fall-back facility962 negotiate a protocol that both it and the server suppport. This is a well-known fall-back facility 963 963 that is built into the SMB/CIFS protocols. 964 964 </p></div></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="samba-bdc.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="type.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="StandAloneServer.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">Chapter 5. Backup Domain Control </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> Chapter 7. Standalone Servers</td></tr></table></div></body></html>
Note:
See TracChangeset
for help on using the changeset viewer.
