- Timestamp:
- May 20, 2009, 6:46:53 PM (16 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
branches/samba-3.2.x/docs/htmldocs/Samba3-HOWTO/domain-member.html
r149 r204 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.1"><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#id2562183">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#id2562869">Manual Creation of Machine Trust Accounts</a></span></dt><dt><span class="sect2"><a href="domain-member.html#id2563306">Managing Domain Machine Accounts using NT4 Server Manager</a></span></dt><dt><span class="sect2"><a href="domain-member.html#id2563586">On-the-Fly Creation of Machine Trust Accounts</a></span></dt><dt><span class="sect2"><a href="domain-member.html#id2563692">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#id2564157">Joining an NT4-type Domain with Samba-3</a></span></dt><dt><span class="sect2"><a href="domain-member.html#id2564892">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#id2565174">Configure <code class="filename">smb.conf</code></a></span></dt><dt><span class="sect2"><a href="domain-member.html#id2565365">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#id2566460">Notes</a></span></dt></dl></dd><dt><span class="sect1"><a href="domain-member.html#id2566532">Sharing User ID Mappings between Samba Domain Members</a></span></dt><dt><span class="sect1"><a href="domain-member.html#id2566738">Common Errors</a></span></dt><dd><dl><dt><span class="sect2"><a href="domain-member.html#id2566777">Cannot Add Machine Back to Domain</a></span></dt><dt><span class="sect2"><a href="domain-member.html#id2566853">Adding Machine to Domain Fails</a></span></dt><dt><span class="sect2"><a href="domain-member.html#id2567089">I Can't Join a Windows 2003 PDC</a></span></dt></dl></dd></dl></div><p> 2 <a class="indexterm" name="id2562130"></a> 3 <a class="indexterm" name="id2562137"></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.1"><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#id2562196">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#id2562883">Manual Creation of Machine Trust Accounts</a></span></dt><dt><span class="sect2"><a href="domain-member.html#id2563320">Managing Domain Machine Accounts using NT4 Server Manager</a></span></dt><dt><span class="sect2"><a href="domain-member.html#id2563599">On-the-Fly Creation of Machine Trust Accounts</a></span></dt><dt><span class="sect2"><a href="domain-member.html#id2563705">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#id2564171">Joining an NT4-type Domain with Samba-3</a></span></dt><dt><span class="sect2"><a href="domain-member.html#id2564906">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#id2565187">Configure <code class="filename">smb.conf</code></a></span></dt><dt><span class="sect2"><a href="domain-member.html#id2565378">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#id2566473">Notes</a></span></dt></dl></dd><dt><span class="sect1"><a href="domain-member.html#id2566545">Sharing User ID Mappings between Samba Domain Members</a></span></dt><dt><span class="sect1"><a href="domain-member.html#id2566752">Common Errors</a></span></dt><dd><dl><dt><span class="sect2"><a href="domain-member.html#id2566792">Cannot Add Machine Back to Domain</a></span></dt><dt><span class="sect2"><a href="domain-member.html#id2566867">Adding Machine to Domain Fails</a></span></dt><dt><span class="sect2"><a href="domain-member.html#id2567103">I Can't Join a Windows 2003 PDC</a></span></dt></dl></dd></dl></div><p> 4 2 <a class="indexterm" name="id2562144"></a> 3 <a class="indexterm" name="id2562151"></a> 4 <a class="indexterm" name="id2562158"></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="id25621 59"></a>11 <a class="indexterm" name="id25621 66"></a>10 <a class="indexterm" name="id2562173"></a> 11 <a class="indexterm" name="id2562180"></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="id2562183"></a>Features and Benefits</h2></div></div></div><p> 20 <a class="indexterm" name="id2562191"></a> 21 <a class="indexterm" name="id2562198"></a> 19 </p><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2562196"></a>Features and Benefits</h2></div></div></div><p> 22 20 <a class="indexterm" name="id2562204"></a> 21 <a class="indexterm" name="id2562211"></a> 22 <a class="indexterm" name="id2562218"></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="id2562236"></a>31 <a class="indexterm" name="id2562243"></a>32 30 <a class="indexterm" name="id2562250"></a> 33 31 <a class="indexterm" name="id2562257"></a> 32 <a class="indexterm" name="id2562263"></a> 33 <a class="indexterm" name="id2562270"></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="id25622 76"></a>38 <a class="indexterm" name="id2562290"></a> 39 39 MS Windows workstation users get the benefit of SSO. 40 40 </p></li><li><p> 41 <a class="indexterm" name="id2562288"></a>42 <a class="indexterm" name="id2562295"></a>43 41 <a class="indexterm" name="id2562302"></a> 44 <a class="indexterm" name="id2562309"></a> 42 <a class="indexterm" name="id2562308"></a> 43 <a class="indexterm" name="id2562315"></a> 44 <a class="indexterm" name="id2562322"></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="id25623 24"></a>51 <a class="indexterm" name="id25623 31"></a>50 <a class="indexterm" name="id2562337"></a> 51 <a class="indexterm" name="id2562344"></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="id2562350"></a>56 <a class="indexterm" name="id2562356"></a>57 55 <a class="indexterm" name="id2562363"></a> 58 56 <a class="indexterm" name="id2562370"></a> 57 <a class="indexterm" name="id2562377"></a> 58 <a class="indexterm" name="id2562384"></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="id2562390"></a>63 <a class="indexterm" name="id2562396"></a>64 62 <a class="indexterm" name="id2562403"></a> 63 <a class="indexterm" name="id2562410"></a> 64 <a class="indexterm" name="id2562417"></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="id2562417"></a>69 <a class="indexterm" name="id2562424"></a>70 68 <a class="indexterm" name="id2562431"></a> 71 <a class="indexterm" name="id2562437"></a> 69 <a class="indexterm" name="id2562438"></a> 70 <a class="indexterm" name="id2562444"></a> 71 <a class="indexterm" name="id2562451"></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="id2562466"></a>79 <a class="indexterm" name="id2562472"></a>80 78 <a class="indexterm" name="id2562479"></a> 81 79 <a class="indexterm" name="id2562486"></a> 80 <a class="indexterm" name="id2562493"></a> 81 <a class="indexterm" name="id2562500"></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="id2562506"></a> 88 <a class="indexterm" name="id2562515"></a> 89 <a class="indexterm" name="id2562522"></a> 87 <a class="indexterm" name="id2562519"></a> 90 88 <a class="indexterm" name="id2562529"></a> 91 89 <a class="indexterm" name="id2562536"></a> 90 <a class="indexterm" name="id2562543"></a> 91 <a class="indexterm" name="id2562550"></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="id25625 57"></a>100 <a class="indexterm" name="id25625 64"></a>101 <a class="indexterm" name="id25625 70"></a>102 <a class="indexterm" name="id25625 77"></a>99 <a class="indexterm" name="id2562571"></a> 100 <a class="indexterm" name="id2562578"></a> 101 <a class="indexterm" name="id2562584"></a> 102 <a class="indexterm" name="id2562591"></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="id2562594"></a>111 <a class="indexterm" name="id2562601"></a>112 110 <a class="indexterm" name="id2562608"></a> 111 <a class="indexterm" name="id2562615"></a> 112 <a class="indexterm" name="id2562622"></a> 113 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="id2562640"></a>118 <a class="indexterm" name="id2562647"></a>119 117 <a class="indexterm" name="id2562654"></a> 120 118 <a class="indexterm" name="id2562660"></a> 121 119 <a class="indexterm" name="id2562667"></a> 122 120 <a class="indexterm" name="id2562674"></a> 121 <a class="indexterm" name="id2562681"></a> 122 <a class="indexterm" name="id2562688"></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="id2562696"></a>129 <a class="indexterm" name="id2562703"></a>130 128 <a class="indexterm" name="id2562710"></a> 131 129 <a class="indexterm" name="id2562717"></a> 130 <a class="indexterm" name="id2562723"></a> 131 <a class="indexterm" name="id2562730"></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="id25627 37"></a>137 <a class="indexterm" name="id25627 44"></a>136 <a class="indexterm" name="id2562751"></a> 137 <a class="indexterm" name="id2562758"></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="id25627 70"></a>143 <a class="indexterm" name="id2562784"></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="id2562 786"></a>146 <a class="indexterm" name="id2562800"></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="id25628 00"></a>151 <a class="indexterm" name="id25628 07"></a>150 <a class="indexterm" name="id2562814"></a> 151 <a class="indexterm" name="id2562821"></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="id25628 23"></a>158 <a class="indexterm" name="id25628 30"></a>157 <a class="indexterm" name="id2562836"></a> 158 <a class="indexterm" name="id2562843"></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="id25628 49"></a>165 <a class="indexterm" name="id25628 56"></a>164 <a class="indexterm" name="id2562862"></a> 165 <a class="indexterm" name="id2562869"></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="id25628 69"></a>Manual Creation of Machine Trust Accounts</h3></div></div></div><p>169 <a class="indexterm" name="id25628 78"></a>170 <a class="indexterm" name="id25628 84"></a>171 <a class="indexterm" name="id2562 890"></a>172 <a class="indexterm" name="id2562 897"></a>168 </p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2562883"></a>Manual Creation of Machine Trust Accounts</h3></div></div></div><p> 169 <a class="indexterm" name="id2562891"></a> 170 <a class="indexterm" name="id2562898"></a> 171 <a class="indexterm" name="id2562903"></a> 172 <a class="indexterm" name="id2562910"></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="id2562965"></a>187 <a class="indexterm" name="id2562972"></a>188 186 <a class="indexterm" name="id2562979"></a> 187 <a class="indexterm" name="id2562986"></a> 188 <a class="indexterm" name="id2562992"></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="id256 2999"></a>194 <a class="indexterm" name="id25630 06"></a>193 <a class="indexterm" name="id2563013"></a> 194 <a class="indexterm" name="id2563020"></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="id2563047"></a> 202 <a class="indexterm" name="id2563054"></a> 203 <a class="indexterm" name="id2563060"></a> 201 <a class="indexterm" name="id2563061"></a> 204 202 <a class="indexterm" name="id2563067"></a> 203 <a class="indexterm" name="id2563074"></a> 204 <a class="indexterm" name="id2563081"></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="id2563110"></a>214 <a class="indexterm" name="id2563116"></a>215 213 <a class="indexterm" name="id2563123"></a> 214 <a class="indexterm" name="id2563130"></a> 215 <a class="indexterm" name="id2563137"></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="id2563149"></a>224 <a class="indexterm" name="id2563156"></a>225 223 <a class="indexterm" name="id2563163"></a> 224 <a class="indexterm" name="id2563170"></a> 225 <a class="indexterm" name="id2563177"></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="id2563204"></a>236 <a class="indexterm" name="id2563211"></a>237 235 <a class="indexterm" name="id2563218"></a> 238 236 <a class="indexterm" name="id2563225"></a> 237 <a class="indexterm" name="id2563232"></a> 238 <a class="indexterm" name="id2563238"></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="id2563247"></a>244 <a class="indexterm" name="id2563254"></a>245 243 <a class="indexterm" name="id2563260"></a> 246 244 <a class="indexterm" name="id2563267"></a> 247 245 <a class="indexterm" name="id2563274"></a> 246 <a class="indexterm" name="id2563281"></a> 247 <a class="indexterm" name="id2563288"></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="id25632 84"></a>250 <a class="indexterm" name="id2563297"></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="id25633 06"></a>Managing Domain Machine Accounts using NT4 Server Manager</h3></div></div></div><p>258 <a class="indexterm" name="id25633 15"></a>259 <a class="indexterm" name="id25633 22"></a>260 <a class="indexterm" name="id25633 29"></a>257 </p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2563320"></a>Managing Domain Machine Accounts using NT4 Server Manager</h3></div></div></div><p> 258 <a class="indexterm" name="id2563328"></a> 259 <a class="indexterm" name="id2563335"></a> 260 <a class="indexterm" name="id2563342"></a> 261 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="id2563355"></a>266 <a class="indexterm" name="id2563361"></a>267 265 <a class="indexterm" name="id2563368"></a> 268 266 <a class="indexterm" name="id2563375"></a> 267 <a class="indexterm" name="id2563381"></a> 268 <a class="indexterm" name="id2563388"></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="id25634 13"></a>276 <a class="indexterm" name="id25634 20"></a>275 <a class="indexterm" name="id2563426"></a> 276 <a class="indexterm" name="id2563433"></a> 277 277 If your workstation is a <span class="application">Microsoft Windows 9x/Me</span> family product, 278 278 you should download the <code class="literal">Nexus.exe</code> package from the Microsoft Web site. … … 284 284 <a class="ulink" href="http://support.microsoft.com/default.aspx?scid=kb;en-us;172540" target="_top">172540</a> 285 285 </p><p> 286 <a class="indexterm" name="id25634 64"></a>287 <a class="indexterm" name="id25634 71"></a>286 <a class="indexterm" name="id2563478"></a> 287 <a class="indexterm" name="id2563484"></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="id2563 486"></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="id2563500"></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="id25635 86"></a>On-the-Fly Creation of Machine Trust Accounts</h3></div></div></div><p>307 <a class="indexterm" name="id2563 594"></a>306 </p></li></ol></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2563599"></a>On-the-Fly Creation of Machine Trust Accounts</h3></div></div></div><p> 307 <a class="indexterm" name="id2563608"></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="id25636 10"></a>312 <a class="indexterm" name="id25636 19"></a>313 <a class="indexterm" name="id25636 26"></a>311 <a class="indexterm" name="id2563623"></a> 312 <a class="indexterm" name="id2563633"></a> 313 <a class="indexterm" name="id2563640"></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="id25636 48"></a>320 <a class="indexterm" name="id25636 54"></a>319 <a class="indexterm" name="id2563661"></a> 320 <a class="indexterm" name="id2563668"></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="id25636 77"></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="id2563 692"></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="id2563690"></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="id2563705"></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="id25637 02"></a>Windows 200x/XP Professional Client</h4></div></div></div><p>327 <a class="indexterm" name="id25637 11"></a>328 <a class="indexterm" name="id25637 18"></a>329 <a class="indexterm" name="id25637 27"></a>330 <a class="indexterm" name="id25637 34"></a>326 </p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2563716"></a>Windows 200x/XP Professional Client</h4></div></div></div><p> 327 <a class="indexterm" name="id2563724"></a> 328 <a class="indexterm" name="id2563731"></a> 329 <a class="indexterm" name="id2563741"></a> 330 <a class="indexterm" name="id2563748"></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="id25637 54"></a>338 <a class="indexterm" name="id25637 61"></a>337 <a class="indexterm" name="id2563767"></a> 338 <a class="indexterm" name="id2563774"></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="id25637 79"></a>343 <a class="indexterm" name="id25637 86"></a>344 <a class="indexterm" name="id2563 793"></a>345 <a class="indexterm" name="id25638 00"></a>342 <a class="indexterm" name="id2563792"></a> 343 <a class="indexterm" name="id2563799"></a> 344 <a class="indexterm" name="id2563806"></a> 345 <a class="indexterm" name="id2563813"></a> 346 346 The name of the account that is used to create domain member machine trust accounts can be 347 347 anything the network administrator may choose. If it is other than <code class="constant">root</code>, … … 349 349 <a class="link" href="smb.conf.5.html#USERNAMEMAP">username map = /etc/samba/smbusers</a>. 350 350 </p><p> 351 <a class="indexterm" name="id2563840"></a>352 <a class="indexterm" name="id2563846"></a>353 351 <a class="indexterm" name="id2563853"></a> 352 <a class="indexterm" name="id2563860"></a> 353 <a class="indexterm" name="id2563867"></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="id2563866"></a>Windows NT4 Client</h4></div></div></div><p> 357 <a class="indexterm" name="id2563874"></a> 358 <a class="indexterm" name="id2563881"></a> 356 </p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2563880"></a>Windows NT4 Client</h4></div></div></div><p> 359 357 <a class="indexterm" name="id2563888"></a> 358 <a class="indexterm" name="id2563895"></a> 359 <a class="indexterm" name="id2563902"></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="id2563908"></a>367 <a class="indexterm" name="id2563915"></a>368 366 <a class="indexterm" name="id2563922"></a> 369 367 <a class="indexterm" name="id2563929"></a> 368 <a class="indexterm" name="id2563935"></a> 369 <a class="indexterm" name="id2563942"></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="id25639 49"></a>Samba Client</h4></div></div></div><p>375 <a class="indexterm" name="id25639 57"></a>374 </p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2563963"></a>Samba Client</h4></div></div></div><p> 375 <a class="indexterm" name="id2563971"></a> 376 376 Joining a Samba client to a domain is documented in <a class="link" href="domain-member.html#domain-member-server" title="Domain Member Server">the next section</a>. 377 377 </p></div></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="domain-member-server"></a>Domain Member Server</h2></div></div></div><p> 378 <a class="indexterm" name="id2563988"></a>379 <a class="indexterm" name="id2563995"></a>380 378 <a class="indexterm" name="id2564002"></a> 381 379 <a class="indexterm" name="id2564009"></a> 380 <a class="indexterm" name="id2564016"></a> 381 <a class="indexterm" name="id2564023"></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="id2564028"></a> 391 <a class="indexterm" name="id2564037"></a> 392 <a class="indexterm" name="id2564044"></a> 390 <a class="indexterm" name="id2564042"></a> 393 391 <a class="indexterm" name="id2564051"></a> 394 392 <a class="indexterm" name="id2564058"></a> 395 393 <a class="indexterm" name="id2564065"></a> 396 <a class="indexterm" name="id256407 1"></a>394 <a class="indexterm" name="id2564072"></a> 397 395 <a class="indexterm" name="id2564078"></a> 396 <a class="indexterm" name="id2564085"></a> 397 <a class="indexterm" name="id2564092"></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="id2564094"></a>405 <a class="indexterm" name="id2564101"></a>406 404 <a class="indexterm" name="id2564108"></a> 405 <a class="indexterm" name="id2564115"></a> 406 <a class="indexterm" name="id2564122"></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="id25641 23"></a>413 <a class="indexterm" name="id25641 31"></a>414 <a class="indexterm" name="id25641 38"></a>412 <a class="indexterm" name="id2564137"></a> 413 <a class="indexterm" name="id2564144"></a> 414 <a class="indexterm" name="id2564151"></a> 415 415 Please refer to <a class="link" href="samba-pdc.html" title="Chapter 4. Domain Control">Domain Control</a>, for more information regarding 416 416 how to create a domain machine account for a domain member server as well as for 417 417 information on how to enable the Samba domain member machine to join the domain 418 418 and be fully trusted by it. 419 </p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id25641 57"></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="id25642 41"></a>419 </p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2564171"></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="id2564255"></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="id2564257"></a>424 <a class="indexterm" name="id2564264"></a>425 423 <a class="indexterm" name="id2564271"></a> 426 424 <a class="indexterm" name="id2564278"></a> 425 <a class="indexterm" name="id2564285"></a> 426 <a class="indexterm" name="id2564292"></a> 427 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="id25643 09"></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="id2564322"></a><em class="parameter"><code>security = domain</code></em></td></tr></table><p> 430 430 Note that if the parameter <em class="parameter"><code>security = user</code></em> is used, this machine would function as a 431 431 standalone server and not as a domain member server. Domain security mode causes Samba to work within the … … 434 434 Next change the <a class="link" href="smb.conf.5.html#WORKGROUP">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="id25643 57"></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="id2564371"></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="id25643 73"></a>440 <a class="indexterm" name="id25643 80"></a>439 <a class="indexterm" name="id2564386"></a> 440 <a class="indexterm" name="id2564393"></a> 441 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. … … 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="id2564419"></a>447 <a class="indexterm" name="id2564425"></a>448 446 <a class="indexterm" name="id2564432"></a> 449 447 <a class="indexterm" name="id2564439"></a> 448 <a class="indexterm" name="id2564445"></a> 449 <a class="indexterm" name="id2564452"></a> 450 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="id25644 63"></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="id2564477"></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="id25644 83"></a>460 <a class="indexterm" name="id2564 490"></a>461 <a class="indexterm" name="id2564 497"></a>462 <a class="indexterm" name="id25645 04"></a>459 <a class="indexterm" name="id2564496"></a> 460 <a class="indexterm" name="id2564503"></a> 461 <a class="indexterm" name="id2564510"></a> 462 <a class="indexterm" name="id2564517"></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="id25645 19"></a><em class="parameter"><code>password server = *</code></em></td></tr></table><p>466 <a class="indexterm" name="id25645 30"></a>465 </p><table class="simplelist" border="0" summary="Simple list"><tr><td><a class="indexterm" name="id2564532"></a><em class="parameter"><code>password server = *</code></em></td></tr></table><p> 466 <a class="indexterm" name="id2564544"></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="id25645 46"></a>473 <a class="indexterm" name="id2564560"></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="id2564579"></a>479 <a class="indexterm" name="id2564586"></a>480 478 <a class="indexterm" name="id2564593"></a> 481 479 <a class="indexterm" name="id2564600"></a> 480 <a class="indexterm" name="id2564606"></a> 481 <a class="indexterm" name="id2564613"></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="id2564623"></a>487 <a class="indexterm" name="id2564630"></a>488 486 <a class="indexterm" name="id2564636"></a> 489 487 <a class="indexterm" name="id2564643"></a> 488 <a class="indexterm" name="id2564650"></a> 489 <a class="indexterm" name="id2564657"></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="id25646 79"></a>501 <a class="indexterm" name="id2564 690"></a>502 <a class="indexterm" name="id2564 697"></a>500 <a class="indexterm" name="id2564693"></a> 501 <a class="indexterm" name="id2564704"></a> 502 <a class="indexterm" name="id2564710"></a> 503 503 Where Active Directory is used, the command used to join the ADS domain is: 504 504 </p><pre class="screen"> … … 513 513 administration</a> for further information. 514 514 </p><p> 515 <a class="indexterm" name="id2564754"></a>516 <a class="indexterm" name="id2564761"></a>517 515 <a class="indexterm" name="id2564768"></a> 516 <a class="indexterm" name="id2564775"></a> 517 <a class="indexterm" name="id2564782"></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="id25647 80"></a>522 <a class="indexterm" name="id2564 790"></a>523 <a class="indexterm" name="id2564 797"></a>524 <a class="indexterm" name="id25648 04"></a>521 <a class="indexterm" name="id2564794"></a> 522 <a class="indexterm" name="id2564803"></a> 523 <a class="indexterm" name="id2564811"></a> 524 <a class="indexterm" name="id2564818"></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="id25648 33"></a>531 <a class="indexterm" name="id25648 40"></a>530 <a class="indexterm" name="id2564846"></a> 531 <a class="indexterm" name="id2564853"></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="id2564853"></a>537 <a class="indexterm" name="id2564860"></a>538 536 <a class="indexterm" name="id2564867"></a> 537 <a class="indexterm" name="id2564874"></a> 538 <a class="indexterm" name="id2564881"></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="id2564 892"></a>Why Is This Better Than <em class="parameter"><code>security = server</code></em>?</h3></div></div></div><p>546 <a class="indexterm" name="id25649 06"></a>547 <a class="indexterm" name="id25649 13"></a>548 <a class="indexterm" name="id25649 20"></a>545 </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2564906"></a>Why Is This Better Than <em class="parameter"><code>security = server</code></em>?</h3></div></div></div><p> 546 <a class="indexterm" name="id2564919"></a> 547 <a class="indexterm" name="id2564926"></a> 548 <a class="indexterm" name="id2564933"></a> 549 549 Currently, domain security in Samba does not free you from having to create local UNIX users to represent the 550 550 users attaching to your server. This means that if domain user <code class="constant">DOM\fred</code> attaches to your … … 553 553 NT server in the same way as a Windows 95 or Windows 98 server would. 554 554 </p><p> 555 <a class="indexterm" name="id25649 54"></a>556 <a class="indexterm" name="id25649 60"></a>557 <a class="indexterm" name="id25649 67"></a>555 <a class="indexterm" name="id2564968"></a> 556 <a class="indexterm" name="id2564974"></a> 557 <a class="indexterm" name="id2564980"></a> 558 558 Please refer to <a class="link" href="winbind.html" title="Chapter 24. Winbind: Use of Domain Accounts">Winbind: Use of Domain Accounts</a>, for information on a system 559 559 to automatically assign UNIX UIDs and GIDs to Windows NT domain users and groups. 560 560 </p><p> 561 <a class="indexterm" name="id2564986"></a>562 <a class="indexterm" name="id2564993"></a>563 561 <a class="indexterm" name="id2565000"></a> 562 <a class="indexterm" name="id2565007"></a> 563 <a class="indexterm" name="id2565014"></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="id2565018"></a>571 <a class="indexterm" name="id2565024"></a>572 570 <a class="indexterm" name="id2565031"></a> 571 <a class="indexterm" name="id2565038"></a> 572 <a class="indexterm" name="id2565044"></a> 573 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 … … 578 578 connection resources. 579 579 </p><p> 580 <a class="indexterm" name="id2565071"></a> 581 <a class="indexterm" name="id2565077"></a> 582 <a class="indexterm" name="id2565084"></a> 580 <a class="indexterm" name="id2565085"></a> 583 581 <a class="indexterm" name="id2565091"></a> 582 <a class="indexterm" name="id2565098"></a> 583 <a class="indexterm" name="id2565104"></a> 584 584 Finally, acting in the same manner as an NT server authenticating to a PDC means that as part of the 585 585 authentication reply, the Samba server gets the user identification information such as the user SID, the list … … 590 590 <span class="emphasis"><em>Doing the NIS/NT Samba</em></span>. 591 591 </p></div></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="ads-member"></a>Samba ADS Domain Membership</h2></div></div></div><p> 592 <a class="indexterm" name="id25651 41"></a>593 <a class="indexterm" name="id25651 47"></a>594 <a class="indexterm" name="id25651 56"></a>595 <a class="indexterm" name="id25651 63"></a>592 <a class="indexterm" name="id2565154"></a> 593 <a class="indexterm" name="id2565161"></a> 594 <a class="indexterm" name="id2565170"></a> 595 <a class="indexterm" name="id2565177"></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="id25651 74"></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="id2565187"></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="id2565200"></a><em class="parameter"><code>realm = your.kerberos.REALM</code></em></td></tr><tr><td><a class="indexterm" name="id2565211"></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="id2565231"></a><em class="parameter"><code>encrypt passwords = yes</code></em></td></tr></table><p> 601 <a class="indexterm" name="id2565245"></a> 602 <a class="indexterm" name="id2565252"></a> 600 </p><table class="simplelist" border="0" summary="Simple list"><tr><td><a class="indexterm" name="id2565213"></a><em class="parameter"><code>realm = your.kerberos.REALM</code></em></td></tr><tr><td><a class="indexterm" name="id2565225"></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="id2565245"></a><em class="parameter"><code>encrypt passwords = yes</code></em></td></tr></table><p> 603 601 <a class="indexterm" name="id2565259"></a> 604 <a class="indexterm" name="id256526 5"></a>602 <a class="indexterm" name="id2565266"></a> 605 603 <a class="indexterm" name="id2565272"></a> 604 <a class="indexterm" name="id2565279"></a> 605 <a class="indexterm" name="id2565286"></a> 606 606 In case samba cannot correctly identify the appropriate ADS server using the realm name, use the 607 607 <a class="link" href="smb.conf.5.html#PASSWORDSERVER">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="id25653 03"></a><em class="parameter"><code>password server = your.kerberos.server</code></em></td></tr></table><p>608 </p><table class="simplelist" border="0" summary="Simple list"><tr><td><a class="indexterm" name="id2565317"></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="id25653 30"></a>615 <a class="indexterm" name="id25653 37"></a>614 <a class="indexterm" name="id2565344"></a> 615 <a class="indexterm" name="id2565350"></a> 616 616 You do <span class="emphasis"><em>not</em></span> need an smbpasswd file, and older clients will be authenticated as 617 617 if <a class="link" href="smb.conf.5.html#SECURITY">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="id25653 65"></a>Configure <code class="filename">/etc/krb5.conf</code></h3></div></div></div><p>620 <a class="indexterm" name="id25653 77"></a>621 <a class="indexterm" name="id25653 84"></a>622 <a class="indexterm" name="id2565 393"></a>623 <a class="indexterm" name="id25654 00"></a>619 </p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2565378"></a>Configure <code class="filename">/etc/krb5.conf</code></h3></div></div></div><p> 620 <a class="indexterm" name="id2565390"></a> 621 <a class="indexterm" name="id2565397"></a> 622 <a class="indexterm" name="id2565407"></a> 623 <a class="indexterm" name="id2565414"></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="id2565418"></a> 628 <a class="indexterm" name="id2565424"></a> 629 <a class="indexterm" name="id2565431"></a> 627 <a class="indexterm" name="id2565432"></a> 630 628 <a class="indexterm" name="id2565438"></a> 631 629 <a class="indexterm" name="id2565445"></a> 630 <a class="indexterm" name="id2565452"></a> 631 <a class="indexterm" name="id2565458"></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="id2565466"></a>639 <a class="indexterm" name="id2565473"></a>640 638 <a class="indexterm" name="id2565480"></a> 641 639 <a class="indexterm" name="id2565487"></a> 642 640 <a class="indexterm" name="id2565494"></a> 643 641 <a class="indexterm" name="id2565500"></a> 642 <a class="indexterm" name="id2565507"></a> 643 <a class="indexterm" name="id2565514"></a> 644 644 UNIX systems can use kinit and the DES-CBC-MD5 or DES-CBC-CRC encryption types to authenticate to the Windows 645 645 2000 KDC. For further information regarding Windows 2000 ADS kerberos interoperability please refer to the … … 649 649 explains much of the magic behind the operation of Kerberos. 650 650 </p><p> 651 <a class="indexterm" name="id2565532"></a> 652 <a class="indexterm" name="id2565538"></a> 653 <a class="indexterm" name="id2565545"></a> 651 <a class="indexterm" name="id2565546"></a> 654 652 <a class="indexterm" name="id2565552"></a> 655 653 <a class="indexterm" name="id2565559"></a> 656 654 <a class="indexterm" name="id2565566"></a> 655 <a class="indexterm" name="id2565572"></a> 656 <a class="indexterm" name="id2565579"></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="id2565 587"></a>662 <a class="indexterm" name="id2565600"></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="id25656 12"></a>677 <a class="indexterm" name="id2565626"></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="id25656 35"></a>695 <a class="indexterm" name="id25656 41"></a>694 <a class="indexterm" name="id2565648"></a> 695 <a class="indexterm" name="id2565655"></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="id2565665"></a>701 <a class="indexterm" name="id2565672"></a>702 700 <a class="indexterm" name="id2565678"></a> 703 701 <a class="indexterm" name="id2565685"></a> 702 <a class="indexterm" name="id2565692"></a> 703 <a class="indexterm" name="id2565698"></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="id2565706"></a>712 <a class="indexterm" name="id2565713"></a>713 711 <a class="indexterm" name="id2565720"></a> 712 <a class="indexterm" name="id2565726"></a> 713 <a class="indexterm" name="id2565733"></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="id2565737"></a>719 <a class="indexterm" name="id2565744"></a>720 718 <a class="indexterm" name="id2565751"></a> 721 <a class="indexterm" name="id2565758"></a> 719 <a class="indexterm" name="id2565757"></a> 720 <a class="indexterm" name="id2565764"></a> 721 <a class="indexterm" name="id2565771"></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="id25657 75"></a>726 <a class="indexterm" name="id25657 82"></a>725 <a class="indexterm" name="id2565789"></a> 726 <a class="indexterm" name="id2565796"></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="id2565794"></a> 730 <a class="indexterm" name="id2565801"></a> 731 <a class="indexterm" name="id2565807"></a> 729 <a class="indexterm" name="id2565808"></a> 732 730 <a class="indexterm" name="id2565814"></a> 731 <a class="indexterm" name="id2565821"></a> 732 <a class="indexterm" name="id2565828"></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="id2565829"></a>738 <a class="indexterm" name="id2565836"></a>739 737 <a class="indexterm" name="id2565842"></a> 738 <a class="indexterm" name="id2565849"></a> 739 <a class="indexterm" name="id2565856"></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="id2565865"></a>745 <a class="indexterm" name="id2565872"></a>746 744 <a class="indexterm" name="id2565879"></a> 747 <a class="indexterm" name="id2565886"></a> 745 <a class="indexterm" name="id2565885"></a> 746 <a class="indexterm" name="id2565892"></a> 747 <a class="indexterm" name="id2565900"></a> 748 748 If all you want is Kerberos support in <span class="application">smbclient</span>, then you can skip directly to <a class="link" href="domain-member.html#ads-test-smbclient" title="Testing with smbclient">Testing with <span class="application">smbclient</span></a> now. <a class="link" href="domain-member.html#ads-create-machine-account" title="Create the Computer Account">Create the Computer Account</a> and <a class="link" href="domain-member.html#ads-test-server" title="Testing Server Setup">Testing Server Setup</a> are needed only if you want Kerberos support for <span class="application">smbd</span> 749 749 and <span class="application">winbindd</span>. 750 750 </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="ads-create-machine-account"></a>Create the Computer Account</h3></div></div></div><p> 751 <a class="indexterm" name="id2565957"></a>752 <a class="indexterm" name="id2565964"></a>753 751 <a class="indexterm" name="id2565971"></a> 754 <a class="indexterm" name="id2565978"></a> 752 <a class="indexterm" name="id2565977"></a> 753 <a class="indexterm" name="id2565984"></a> 754 <a class="indexterm" name="id2565992"></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="id2566012"></a>764 <a class="indexterm" name="id2566019"></a>765 763 <a class="indexterm" name="id2566026"></a> 766 764 <a class="indexterm" name="id2566033"></a> 767 765 <a class="indexterm" name="id2566040"></a> 768 766 <a class="indexterm" name="id2566047"></a> 767 <a class="indexterm" name="id2566053"></a> 768 <a class="indexterm" name="id2566060"></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="id2566 097"></a>779 <a class="indexterm" name="id25661 04"></a>780 <a class="indexterm" name="id25661 11"></a>781 <a class="indexterm" name="id25661 18"></a>778 <a class="indexterm" name="id2566110"></a> 779 <a class="indexterm" name="id2566117"></a> 780 <a class="indexterm" name="id2566124"></a> 781 <a class="indexterm" name="id2566131"></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="id25661 67"></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="id2566180"></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="id2566186"></a>795 <a class="indexterm" name="id2566193"></a>796 794 <a class="indexterm" name="id2566200"></a> 795 <a class="indexterm" name="id2566206"></a> 796 <a class="indexterm" name="id2566213"></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="id25662 20"></a>801 <a class="indexterm" name="id25662 26"></a>800 <a class="indexterm" name="id2566233"></a> 801 <a class="indexterm" name="id2566240"></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="id25662 60"></a>807 <a class="indexterm" name="id25662 66"></a>808 <a class="indexterm" name="id25662 74"></a>806 <a class="indexterm" name="id2566273"></a> 807 <a class="indexterm" name="id2566280"></a> 808 <a class="indexterm" name="id2566287"></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="id2566305"></a>814 <a class="indexterm" name="id2566312"></a>815 813 <a class="indexterm" name="id2566319"></a> 814 <a class="indexterm" name="id2566326"></a> 815 <a class="indexterm" name="id2566332"></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="id25663 35"></a>821 <a class="indexterm" name="id25663 42"></a>822 <a class="indexterm" name="id25663 51"></a>820 <a class="indexterm" name="id2566349"></a> 821 <a class="indexterm" name="id2566356"></a> 822 <a class="indexterm" name="id2566365"></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="id2566378"></a>829 <a class="indexterm" name="id2566385"></a>830 828 <a class="indexterm" name="id2566392"></a> 829 <a class="indexterm" name="id2566399"></a> 830 <a class="indexterm" name="id2566406"></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="id2566419"></a>834 <a class="indexterm" name="id2566426"></a>835 833 <a class="indexterm" name="id2566432"></a> 834 <a class="indexterm" name="id2566439"></a> 835 <a class="indexterm" name="id2566446"></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="id2566460"></a>Notes</h3></div></div></div><p> 840 <a class="indexterm" name="id2566467"></a> 841 <a class="indexterm" name="id2566474"></a> 839 </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2566473"></a>Notes</h3></div></div></div><p> 842 840 <a class="indexterm" name="id2566481"></a> 841 <a class="indexterm" name="id2566488"></a> 842 <a class="indexterm" name="id2566495"></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="id2566 494"></a>847 <a class="indexterm" name="id25665 01"></a>848 <a class="indexterm" name="id25665 08"></a>846 <a class="indexterm" name="id2566507"></a> 847 <a class="indexterm" name="id2566514"></a> 848 <a class="indexterm" name="id2566521"></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="id2566532"></a>Sharing User ID Mappings between Samba Domain Members</h2></div></div></div><p> 852 <a class="indexterm" name="id2566540"></a> 853 <a class="indexterm" name="id2566547"></a> 851 </p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2566545"></a>Sharing User ID Mappings between Samba Domain Members</h2></div></div></div><p> 854 852 <a class="indexterm" name="id2566554"></a> 855 <a class="indexterm" name="id2566560"></a> 853 <a class="indexterm" name="id2566561"></a> 854 <a class="indexterm" name="id2566568"></a> 855 <a class="indexterm" name="id2566574"></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="id2566579"></a>860 <a class="indexterm" name="id2566586"></a>861 859 <a class="indexterm" name="id2566593"></a> 860 <a class="indexterm" name="id2566599"></a> 861 <a class="indexterm" name="id2566606"></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="id25666 10"></a>867 <a class="indexterm" name="id25666 17"></a>866 <a class="indexterm" name="id2566624"></a> 867 <a class="indexterm" name="id2566630"></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="id25666 40"></a><em class="parameter"><code>ldap idmap suffix = ou=Idmap</code></em></td></tr></table><p>869 </p><table class="simplelist" border="0" summary="Simple list"><tr><td><a class="indexterm" name="id2566654"></a><em class="parameter"><code>ldap idmap suffix = ou=Idmap</code></em></td></tr></table><p> 870 870 See the <code class="filename">smb.conf</code> man page entry for the <a class="link" href="smb.conf.5.html#LDAPIDMAPSUFFIX">ldap idmap suffix</a> 871 871 parameter for further information. 872 872 </p><p> 873 <a class="indexterm" name="id2566677"></a>874 <a class="indexterm" name="id2566683"></a>875 873 <a class="indexterm" name="id2566690"></a> 874 <a class="indexterm" name="id2566696"></a> 875 <a class="indexterm" name="id2566704"></a> 876 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: … … 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="id25667 38"></a>Common Errors</h2></div></div></div><p>884 <a class="indexterm" name="id25667 46"></a>885 <a class="indexterm" name="id25667 53"></a>883 </p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2566752"></a>Common Errors</h2></div></div></div><p> 884 <a class="indexterm" name="id2566760"></a> 885 <a class="indexterm" name="id2566766"></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="id25667 77"></a>Cannot Add Machine Back to Domain</h3></div></div></div><p>894 <a class="indexterm" name="id2566 785"></a>895 <a class="indexterm" name="id2566 792"></a>893 </p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2566792"></a>Cannot Add Machine Back to Domain</h3></div></div></div><p> 894 <a class="indexterm" name="id2566800"></a> 895 <a class="indexterm" name="id2566807"></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="id25668 14"></a>902 <a class="indexterm" name="id25668 21"></a>901 <a class="indexterm" name="id2566828"></a> 902 <a class="indexterm" name="id2566834"></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="id25668 53"></a>Adding Machine to Domain Fails</h3></div></div></div><p>911 <a class="indexterm" name="id25668 62"></a>912 <a class="indexterm" name="id25668 68"></a>910 </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2566867"></a>Adding Machine to Domain Fails</h3></div></div></div><p> 911 <a class="indexterm" name="id2566875"></a> 912 <a class="indexterm" name="id2566882"></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="id2566 888"></a>917 <a class="indexterm" name="id2566902"></a> 918 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 … … 924 924 Possible causes include: 925 925 </p><div class="itemizedlist"><ul type="disc"><li><p> 926 <a class="indexterm" name="id25669 46"></a>927 <a class="indexterm" name="id25669 53"></a>926 <a class="indexterm" name="id2566960"></a> 927 <a class="indexterm" name="id2566967"></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="id25669 65"></a>931 <a class="indexterm" name="id25669 72"></a>930 <a class="indexterm" name="id2566978"></a> 931 <a class="indexterm" name="id2566985"></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="id256 6989"></a>936 <a class="indexterm" name="id256 6996"></a>935 <a class="indexterm" name="id2567002"></a> 936 <a class="indexterm" name="id2567009"></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="id25670 13"></a>940 <a class="indexterm" name="id25670 20"></a>939 <a class="indexterm" name="id2567026"></a> 940 <a class="indexterm" name="id2567033"></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="id2567051"></a>948 <a class="indexterm" name="id2567058"></a>949 947 <a class="indexterm" name="id2567065"></a> 948 <a class="indexterm" name="id2567072"></a> 949 <a class="indexterm" name="id2567079"></a> 950 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="id2567089"></a>I Can't Join a Windows 2003 PDC</h3></div></div></div><p> 954 <a class="indexterm" name="id2567097"></a> 955 <a class="indexterm" name="id2567104"></a> 956 <a class="indexterm" name="id2567110"></a> 953 </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2567103"></a>I Can't Join a Windows 2003 PDC</h3></div></div></div><p> 954 <a class="indexterm" name="id2567111"></a> 957 955 <a class="indexterm" name="id2567117"></a> 956 <a class="indexterm" name="id2567124"></a> 957 <a class="indexterm" name="id2567131"></a> 958 958 Windows 2003 requires SMB signing. Client-side SMB signing has been implemented in Samba-3.0. 959 959 Set <a class="link" href="smb.conf.5.html#CLIENTUSESPNEGO">client use spnego = yes</a> when communicating
Note:
See TracChangeset
for help on using the changeset viewer.
