- Timestamp:
- Mar 1, 2010, 3:05:48 PM (15 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
branches/samba-3.3.x/docs/htmldocs/Samba3-HOWTO/domain-member.html
r368 r411 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.7 5.2"><link rel="home" href="index.html" title="The Official Samba 3.3.x HOWTO and Reference Guide"><link rel="up" href="type.html" title="Part II. Server Configuration Basics"><link rel="prev" href="samba-bdc.html" title="Chapter 5. Backup Domain Control"><link rel="next" href="StandAloneServer.html" title="Chapter 7. Standalone Servers"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter 6. Domain Membership</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="samba-bdc.html">Prev</a> </td><th width="60%" align="center">Part II. Server Configuration Basics</th><td width="20%" align="right"> <a accesskey="n" href="StandAloneServer.html">Next</a></td></tr></table><hr></div><div class="chapter" title="Chapter 6. Domain Membership"><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">Samba Team<br></span><div class="address"><p><code class="email"><<a class="email" href="mailto:gd@samba.org">gd@samba.org</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#id2575193">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#id2575880">Manual Creation of Machine Trust Accounts</a></span></dt><dt><span class="sect2"><a href="domain-member.html#id2576317">Managing Domain Machine Accounts using NT4 Server Manager</a></span></dt><dt><span class="sect2"><a href="domain-member.html#id2576597">On-the-Fly Creation of Machine Trust Accounts</a></span></dt><dt><span class="sect2"><a href="domain-member.html#id2576703">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#id2577168">Joining an NT4-type Domain with Samba-3</a></span></dt><dt><span class="sect2"><a href="domain-member.html#id2577904">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#id2578186">Configure <code class="filename">smb.conf</code></a></span></dt><dt><span class="sect2"><a href="domain-member.html#id2578377">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#id2579471">Notes</a></span></dt></dl></dd><dt><span class="sect1"><a href="domain-member.html#id2579543">Sharing User ID Mappings between Samba Domain Members</a></span></dt><dt><span class="sect1"><a href="domain-member.html#id2579750">Common Errors</a></span></dt><dd><dl><dt><span class="sect2"><a href="domain-member.html#id2579789">Cannot Add Machine Back to Domain</a></span></dt><dt><span class="sect2"><a href="domain-member.html#id2579865">Adding Machine to Domain Fails</a></span></dt><dt><span class="sect2"><a href="domain-member.html#id2580101">I Can't Join a Windows 2003 PDC</a></span></dt></dl></dd></dl></div><p>2 <a class="indexterm" name="id25 75136"></a>3 <a class="indexterm" name="id25 75143"></a>4 <a class="indexterm" name="id25 75150"></a>1 <html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter 6. Domain Membership</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"><link rel="home" href="index.html" title="The Official Samba 3.3.x HOWTO and Reference Guide"><link rel="up" href="type.html" title="Part II. Server Configuration Basics"><link rel="prev" href="samba-bdc.html" title="Chapter 5. Backup Domain Control"><link rel="next" href="StandAloneServer.html" title="Chapter 7. Standalone Servers"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter 6. Domain Membership</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="samba-bdc.html">Prev</a> </td><th width="60%" align="center">Part II. Server Configuration Basics</th><td width="20%" align="right"> <a accesskey="n" href="StandAloneServer.html">Next</a></td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="domain-member"></a>Chapter 6. Domain Membership</h2></div><div><div class="author"><h3 class="author"><span class="firstname">John</span> <span class="othername">H.</span> <span class="orgname">Samba Team</span> <span class="surname">Terpstra</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><code class="email"><<a class="email" href="mailto:jht@samba.org">jht@samba.org</a>></code></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">Jeremy</span> <span class="orgname">Samba Team</span> <span class="surname">Allison</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><code class="email"><<a class="email" href="mailto:jra@samba.org">jra@samba.org</a>></code></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">Gerald</span> <span class="othername">(Jerry)</span> <span class="orgname">Samba Team</span> <span class="surname">Carter</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><code class="email"><<a class="email" href="mailto:jerry@samba.org">jerry@samba.org</a>></code></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">Andrew</span> <span class="orgname">Samba Team</span> <span class="surname">Tridgell</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><code class="email"><<a class="email" href="mailto:tridge@samba.org">tridge@samba.org</a>></code></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">Jelmer</span> <span class="othername">R.</span> <span class="orgname">The Samba Team</span> <span class="surname">Vernooij</span></h3><div class="affiliation"><span class="orgname">The Samba Team<br></span><div class="address"><p><code class="email"><<a class="email" href="mailto:jelmer@samba.org">jelmer@samba.org</a>></code></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">Guenther</span> <span class="orgname">Samba Team</span> <span class="surname">Deschner</span></h3><span class="contrib">LDAP updates</span> <div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><code class="email"><<a class="email" href="mailto:gd@samba.org">gd@samba.org</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#id2569108">Features and Benefits</a></span></dt><dt><span class="sect1"><a href="domain-member.html#machine-trust-accounts">MS Windows Workstation/Server Machine Trust Accounts</a></span></dt><dd><dl><dt><span class="sect2"><a href="domain-member.html#id2569794">Manual Creation of Machine Trust Accounts</a></span></dt><dt><span class="sect2"><a href="domain-member.html#id2570231">Managing Domain Machine Accounts using NT4 Server Manager</a></span></dt><dt><span class="sect2"><a href="domain-member.html#id2570512">On-the-Fly Creation of Machine Trust Accounts</a></span></dt><dt><span class="sect2"><a href="domain-member.html#id2570618">Making an MS Windows Workstation or Server a Domain Member</a></span></dt></dl></dd><dt><span class="sect1"><a href="domain-member.html#domain-member-server">Domain Member Server</a></span></dt><dd><dl><dt><span class="sect2"><a href="domain-member.html#id2571082">Joining an NT4-type Domain with Samba-3</a></span></dt><dt><span class="sect2"><a href="domain-member.html#id2571819">Why Is This Better Than security = server?</a></span></dt></dl></dd><dt><span class="sect1"><a href="domain-member.html#ads-member">Samba ADS Domain Membership</a></span></dt><dd><dl><dt><span class="sect2"><a href="domain-member.html#id2572100">Configure smb.conf</a></span></dt><dt><span class="sect2"><a href="domain-member.html#id2572291">Configure /etc/krb5.conf</a></span></dt><dt><span class="sect2"><a href="domain-member.html#ads-create-machine-account">Create the Computer Account</a></span></dt><dt><span class="sect2"><a href="domain-member.html#ads-test-server">Testing Server Setup</a></span></dt><dt><span class="sect2"><a href="domain-member.html#ads-test-smbclient">Testing with smbclient</a></span></dt><dt><span class="sect2"><a href="domain-member.html#id2573385">Notes</a></span></dt></dl></dd><dt><span class="sect1"><a href="domain-member.html#id2573458">Sharing User ID Mappings between Samba Domain Members</a></span></dt><dt><span class="sect1"><a href="domain-member.html#id2573664">Common Errors</a></span></dt><dd><dl><dt><span class="sect2"><a href="domain-member.html#id2573704">Cannot Add Machine Back to Domain</a></span></dt><dt><span class="sect2"><a href="domain-member.html#id2573779">Adding Machine to Domain Fails</a></span></dt><dt><span class="sect2"><a href="domain-member.html#id2574015">I Can't Join a Windows 2003 PDC</a></span></dt></dl></dd></dl></div><p> 2 <a class="indexterm" name="id2569050"></a> 3 <a class="indexterm" name="id2569057"></a> 4 <a class="indexterm" name="id2569064"></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="id25 75170"></a>11 <a class="indexterm" name="id25 75177"></a>10 <a class="indexterm" name="id2569084"></a> 11 <a class="indexterm" name="id2569091"></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" title="Features and Benefits"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2575193"></a>Features and Benefits</h2></div></div></div><p>20 <a class="indexterm" name="id25 75201"></a>21 <a class="indexterm" name="id25 75208"></a>22 <a class="indexterm" name="id25 75215"></a>19 </p><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2569108"></a>Features and Benefits</h2></div></div></div><p> 20 <a class="indexterm" name="id2569116"></a> 21 <a class="indexterm" name="id2569123"></a> 22 <a class="indexterm" name="id2569130"></a> 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="id25 75247"></a>31 <a class="indexterm" name="id25 75254"></a>32 <a class="indexterm" name="id25 75260"></a>33 <a class="indexterm" name="id25 75267"></a>30 <a class="indexterm" name="id2569161"></a> 31 <a class="indexterm" name="id2569168"></a> 32 <a class="indexterm" name="id2569175"></a> 33 <a class="indexterm" name="id2569182"></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 </p><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem"><p>38 <a class="indexterm" name="id25 75287"></a>37 </p><div class="itemizedlist"><ul type="disc"><li><p> 38 <a class="indexterm" name="id2569201"></a> 39 39 MS Windows workstation users get the benefit of SSO. 40 </p></li><li class="listitem"><p>41 <a class="indexterm" name="id25 75299"></a>42 <a class="indexterm" name="id25 75306"></a>43 <a class="indexterm" name="id25 75312"></a>44 <a class="indexterm" name="id25 75319"></a>40 </p></li><li><p> 41 <a class="indexterm" name="id2569213"></a> 42 <a class="indexterm" name="id2569220"></a> 43 <a class="indexterm" name="id2569227"></a> 44 <a class="indexterm" name="id2569234"></a> 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 47 47 (works with domain member servers as well as with MS Windows workstations 48 48 that are domain members). 49 </p></li><li class="listitem"><p>50 <a class="indexterm" name="id25 75334"></a>51 <a class="indexterm" name="id25 75341"></a>49 </p></li><li><p> 50 <a class="indexterm" name="id2569249"></a> 51 <a class="indexterm" name="id2569256"></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 </p></li><li class="listitem"><p>55 <a class="indexterm" name="id25 75360"></a>56 <a class="indexterm" name="id25 75367"></a>57 <a class="indexterm" name="id25 75374"></a>58 <a class="indexterm" name="id25 75381"></a>54 </p></li><li><p> 55 <a class="indexterm" name="id2569275"></a> 56 <a class="indexterm" name="id2569282"></a> 57 <a class="indexterm" name="id2569288"></a> 58 <a class="indexterm" name="id2569295"></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 </p></li><li class="listitem"><p>62 <a class="indexterm" name="id25 75400"></a>63 <a class="indexterm" name="id25 75407"></a>64 <a class="indexterm" name="id25 75414"></a>61 </p></li><li><p> 62 <a class="indexterm" name="id2569315"></a> 63 <a class="indexterm" name="id2569322"></a> 64 <a class="indexterm" name="id2569328"></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 </p></li><li class="listitem"><p>68 <a class="indexterm" name="id25 75428"></a>69 <a class="indexterm" name="id25 75435"></a>70 <a class="indexterm" name="id25 75441"></a>71 <a class="indexterm" name="id25 75448"></a>67 </p></li><li><p> 68 <a class="indexterm" name="id2569342"></a> 69 <a class="indexterm" name="id2569349"></a> 70 <a class="indexterm" name="id2569356"></a> 71 <a class="indexterm" name="id2569362"></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 … … 75 75 (either NT4/Samba SAM-style domain, NT4 domain that is backend-ed with an 76 76 LDAP directory, or via an Active Directory infrastructure). 77 </p></li></ul></div></div><div class="sect1" title="MS Windows Workstation/Server Machine Trust Accounts"><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="id25 75476"></a>79 <a class="indexterm" name="id25 75483"></a>80 <a class="indexterm" name="id25 75490"></a>81 <a class="indexterm" name="id25 75497"></a>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="id2569391"></a> 79 <a class="indexterm" name="id2569397"></a> 80 <a class="indexterm" name="id2569404"></a> 81 <a class="indexterm" name="id2569411"></a> 82 82 A Machine Trust Account is an account that is used to authenticate a client machine (rather than a user) to 83 the domain controller server. In Windows terminology, this is known as a <span class="quote">“<span class="quote">computer account.</span>”</span>The83 the domain controller server. In Windows terminology, this is known as a “<span class="quote">computer account.</span>” The 84 84 purpose of the machine trust account is to prevent a rogue user and domain controller from colluding to gain 85 85 access to a domain member workstation. 86 86 </p><p> 87 <a class="indexterm" name="id25 75516"></a>88 <a class="indexterm" name="id25 75526"></a>89 <a class="indexterm" name="id25 75533"></a>90 <a class="indexterm" name="id25 75540"></a>91 <a class="indexterm" name="id25 75547"></a>87 <a class="indexterm" name="id2569431"></a> 88 <a class="indexterm" name="id2569440"></a> 89 <a class="indexterm" name="id2569447"></a> 90 <a class="indexterm" name="id2569454"></a> 91 <a class="indexterm" name="id2569461"></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="id25 75568"></a>100 <a class="indexterm" name="id25 75575"></a>101 <a class="indexterm" name="id25 75581"></a>102 <a class="indexterm" name="id25 75588"></a>99 <a class="indexterm" name="id2569482"></a> 100 <a class="indexterm" name="id2569489"></a> 101 <a class="indexterm" name="id2569496"></a> 102 <a class="indexterm" name="id2569502"></a> 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, … … 107 107 as follows: 108 108 109 </p><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem"><p>110 <a class="indexterm" name="id25 75605"></a>111 <a class="indexterm" name="id25 75612"></a>112 <a class="indexterm" name="id25 75619"></a>109 </p><div class="itemizedlist"><ul type="disc"><li><p> 110 <a class="indexterm" name="id2569519"></a> 111 <a class="indexterm" name="id2569526"></a> 112 <a class="indexterm" name="id2569533"></a> 113 113 A domain security account (stored in the <a class="link" href="smb.conf.5.html#PASSDBBACKEND" target="_top">passdb backend</a>) that has been configured in 114 114 the <code class="filename">smb.conf</code> file. The precise nature of the account information that is stored depends on the type of 115 115 backend database that has been chosen. 116 116 </p><p> 117 <a class="indexterm" name="id25 75651"></a>118 <a class="indexterm" name="id25 75658"></a>119 <a class="indexterm" name="id25 75664"></a>120 <a class="indexterm" name="id25 75671"></a>121 <a class="indexterm" name="id25 75678"></a>122 <a class="indexterm" name="id25 75685"></a>117 <a class="indexterm" name="id2569565"></a> 118 <a class="indexterm" name="id2569572"></a> 119 <a class="indexterm" name="id2569579"></a> 120 <a class="indexterm" name="id2569585"></a> 121 <a class="indexterm" name="id2569592"></a> 122 <a class="indexterm" name="id2569599"></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="id25 75707"></a>129 <a class="indexterm" name="id25 75714"></a>130 <a class="indexterm" name="id25 75720"></a>131 <a class="indexterm" name="id25 75727"></a>128 <a class="indexterm" name="id2569621"></a> 129 <a class="indexterm" name="id2569628"></a> 130 <a class="indexterm" name="id2569635"></a> 131 <a class="indexterm" name="id2569642"></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 </p></li><li class="listitem"><p>136 <a class="indexterm" name="id25 75748"></a>137 <a class="indexterm" name="id25 75755"></a>135 </p></li><li><p> 136 <a class="indexterm" name="id2569662"></a> 137 <a class="indexterm" name="id2569669"></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="id25 75781"></a>143 <a class="indexterm" name="id2569695"></a> 144 144 There are three ways to create Machine Trust Accounts: 145 </p><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem"><p>146 <a class="indexterm" name="id25 75797"></a>145 </p><div class="itemizedlist"><ul type="disc"><li><p> 146 <a class="indexterm" name="id2569711"></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 </p></li><li class="listitem"><p>150 <a class="indexterm" name="id25 75811"></a>151 <a class="indexterm" name="id25 75818"></a>149 </p></li><li><p> 150 <a class="indexterm" name="id2569725"></a> 151 <a class="indexterm" name="id2569732"></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. 154 154 This tool can be run from any MS Windows machine as long as the user is 155 155 logged on as the administrator account. 156 </p></li><li class="listitem"><p>157 <a class="indexterm" name="id25 75833"></a>158 <a class="indexterm" name="id25 75840"></a>159 <span class="quote">“<span class="quote">On-the-fly</span>”</span>creation. The Samba Machine Trust Account is automatically156 </p></li><li><p> 157 <a class="indexterm" name="id2569748"></a> 158 <a class="indexterm" name="id2569755"></a> 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. 161 161 (For security, this is the recommended method.) The corresponding UNIX 162 162 account may be created automatically or manually. 163 163 </p></li></ul></div><p> 164 <a class="indexterm" name="id25 75859"></a>165 <a class="indexterm" name="id25 75866"></a>164 <a class="indexterm" name="id2569774"></a> 165 <a class="indexterm" name="id2569781"></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" title="Manual Creation of Machine Trust Accounts"><div class="titlepage"><div><div><h3 class="title"><a name="id2575880"></a>Manual Creation of Machine Trust Accounts</h3></div></div></div><p>169 <a class="indexterm" name="id25 75888"></a>170 <a class="indexterm" name="id25 75895"></a>171 <a class="indexterm" name="id25 75900"></a>172 <a class="indexterm" name="id25 75907"></a>168 </p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2569794"></a>Manual Creation of Machine Trust Accounts</h3></div></div></div><p> 169 <a class="indexterm" name="id2569803"></a> 170 <a class="indexterm" name="id2569809"></a> 171 <a class="indexterm" name="id2569815"></a> 172 <a class="indexterm" name="id2569822"></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>. 175 This can be done using <code class="literal">vipw</code> or another <span class="quote">“<span class="quote">adduser</span>”</span>command175 This can be done using <code class="literal">vipw</code> or another “<span class="quote">adduser</span>” command 176 176 that is normally used to create new UNIX accounts. The following is an example for 177 177 a Linux-based Samba server: … … 184 184 </pre><p> 185 185 </p><p> 186 <a class="indexterm" name="id25 75976"></a>187 <a class="indexterm" name="id25 75983"></a>188 <a class="indexterm" name="id25 75989"></a>189 In the example above there is an existing system group <span class="quote">“<span class="quote">machines</span>”</span>which is used190 as the primary group for all machine accounts. In the following examples the <span class="quote">“<span class="quote">machines</span>”</span>group186 <a class="indexterm" name="id2569890"></a> 187 <a class="indexterm" name="id2569897"></a> 188 <a class="indexterm" name="id2569904"></a> 189 In the example above there is an existing system group “<span class="quote">machines</span>” which is used 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="id25 76010"></a>194 <a class="indexterm" name="id25 76017"></a>193 <a class="indexterm" name="id2569924"></a> 194 <a class="indexterm" name="id2569931"></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="id25 76058"></a>202 <a class="indexterm" name="id25 76064"></a>203 <a class="indexterm" name="id25 76071"></a>204 <a class="indexterm" name="id25 76078"></a>201 <a class="indexterm" name="id2569972"></a> 202 <a class="indexterm" name="id2569979"></a> 203 <a class="indexterm" name="id2569985"></a> 204 <a class="indexterm" name="id2569992"></a> 205 205 The <code class="filename">/etc/passwd</code> entry will list the machine name 206 with a <span class="quote">“<span class="quote">$</span>”</span>appended, and will not have a password, will have a null shell and no207 home directory. For example, a machine named <span class="quote">“<span class="quote">doppy</span>”</span>would have an206 with a “<span class="quote">$</span>” appended, and will not have a password, will have a null shell and no 207 home directory. For example, a machine named “<span class="quote">doppy</span>” would have an 208 208 <code class="filename">/etc/passwd</code> entry like this: 209 209 </p><pre class="programlisting"> … … 211 211 </pre><p> 212 212 </p><p> 213 <a class="indexterm" name="id257 6120"></a>214 <a class="indexterm" name="id257 6127"></a>215 <a class="indexterm" name="id257 6134"></a>213 <a class="indexterm" name="id2570035"></a> 214 <a class="indexterm" name="id2570042"></a> 215 <a class="indexterm" name="id2570048"></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. 218 218 <em class="replaceable"><code>machine_name</code></em> absolutely must be the NetBIOS 219 name of the client to be joined to the domain. The <span class="quote">“<span class="quote">$</span>”</span>must be219 name of the client to be joined to the domain. The “<span class="quote">$</span>” must be 220 220 appended to the NetBIOS name of the client or Samba will not recognize 221 221 this as a Machine Trust Account. 222 222 </p><p> 223 <a class="indexterm" name="id257 6160"></a>224 <a class="indexterm" name="id257 6167"></a>225 <a class="indexterm" name="id257 6174"></a>223 <a class="indexterm" name="id2570074"></a> 224 <a class="indexterm" name="id2570081"></a> 225 <a class="indexterm" name="id2570088"></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="id257 6215"></a>236 <a class="indexterm" name="id257 6222"></a>237 <a class="indexterm" name="id257 6229"></a>238 <a class="indexterm" name="id257 6235"></a>235 <a class="indexterm" name="id2570129"></a> 236 <a class="indexterm" name="id2570136"></a> 237 <a class="indexterm" name="id2570143"></a> 238 <a class="indexterm" name="id2570150"></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 </p><div class="warning" title="Join the client to the domain immediately"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="id257 6257"></a>244 <a class="indexterm" name="id257 6264"></a>245 <a class="indexterm" name="id257 6271"></a>246 <a class="indexterm" name="id257 6278"></a>247 <a class="indexterm" name="id257 6285"></a>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="id2570172"></a> 244 <a class="indexterm" name="id2570179"></a> 245 <a class="indexterm" name="id2570185"></a> 246 <a class="indexterm" name="id2570192"></a> 247 <a class="indexterm" name="id2570199"></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="id257 6294"></a>250 <a class="indexterm" name="id2570209"></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" title="Managing Domain Machine Accounts using NT4 Server Manager"><div class="titlepage"><div><div><h3 class="title"><a name="id2576317"></a>Managing Domain Machine Accounts using NT4 Server Manager</h3></div></div></div><p>258 <a class="indexterm" name="id257 6325"></a>259 <a class="indexterm" name="id257 6332"></a>260 <a class="indexterm" name="id257 6339"></a>257 </p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2570231"></a>Managing Domain Machine Accounts using NT4 Server Manager</h3></div></div></div><p> 258 <a class="indexterm" name="id2570240"></a> 259 <a class="indexterm" name="id2570247"></a> 260 <a class="indexterm" name="id2570254"></a> 261 261 A working <a class="link" href="smb.conf.5.html#ADDMACHINESCRIPT" target="_top">add machine script</a> is essential 262 262 for machine trust accounts to be automatically created. This applies no matter whether 263 263 you use automatic account creation or the NT4 Domain Server Manager. 264 264 </p><p> 265 <a class="indexterm" name="id257 6365"></a>266 <a class="indexterm" name="id257 6372"></a>267 <a class="indexterm" name="id257 6378"></a>268 <a class="indexterm" name="id257 6385"></a>265 <a class="indexterm" name="id2570280"></a> 266 <a class="indexterm" name="id2570286"></a> 267 <a class="indexterm" name="id2570293"></a> 268 <a class="indexterm" name="id2570300"></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="id257 6424"></a>276 <a class="indexterm" name="id257 6430"></a>275 <a class="indexterm" name="id2570338"></a> 276 <a class="indexterm" name="id2570345"></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="id257 6475"></a>287 <a class="indexterm" name="id257 6481"></a>286 <a class="indexterm" name="id2570389"></a> 287 <a class="indexterm" name="id2570396"></a> 288 288 Launch the <code class="literal">srvmgr.exe</code> (Server Manager for Domains) and follow these steps: 289 </p><div class="procedure" title="Procedure 6.1. Server Manager Account Machine Account Management"><a name="id2576497"></a><p class="title"><b>Procedure 6.1. Server Manager Account Machine Account Management</b></p><ol class="procedure" type="1"><li class="step" title="Step 1"><p>289 </p><div class="procedure"><a name="id2570411"></a><p class="title"><b>Procedure 6.1. Server Manager Account Machine Account Management</b></p><ol type="1"><li><p> 290 290 From the menu select <span class="guimenu">Computer</span>. 291 </p></li><li class="step" title="Step 2"><p>291 </p></li><li><p> 292 292 Click <span class="guimenuitem">Select Domain</span>. 293 </p></li><li class="step" title="Step 3"><p>293 </p></li><li><p> 294 294 Click the name of the domain you wish to administer in the 295 295 <span class="guilabel">Select Domain</span> panel and then click 296 296 <span class="guibutton">OK</span>. 297 </p></li><li class="step" title="Step 4"><p>297 </p></li><li><p> 298 298 Again from the menu select <span class="guimenu">Computer</span>. 299 </p></li><li class="step" title="Step 5"><p>299 </p></li><li><p> 300 300 Select <span class="guimenuitem">Add to Domain</span>. 301 </p></li><li class="step" title="Step 6"><p>301 </p></li><li><p> 302 302 In the dialog box, click the radio button to 303 303 <span class="guilabel">Add NT Workstation of Server</span>, then 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" title="On-the-Fly Creation of Machine Trust Accounts"><div class="titlepage"><div><div><h3 class="title"><a name="id2576597"></a>On-the-Fly Creation of Machine Trust Accounts</h3></div></div></div><p>307 <a class="indexterm" name="id257 6606"></a>306 </p></li></ol></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2570512"></a>On-the-Fly Creation of Machine Trust Accounts</h3></div></div></div><p> 307 <a class="indexterm" name="id2570520"></a> 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="id257 6621"></a>312 <a class="indexterm" name="id257 6631"></a>313 <a class="indexterm" name="id257 6638"></a>311 <a class="indexterm" name="id2570536"></a> 312 <a class="indexterm" name="id2570545"></a> 313 <a class="indexterm" name="id2570552"></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="id257 6659"></a>320 <a class="indexterm" name="id257 6666"></a>319 <a class="indexterm" name="id2570574"></a> 320 <a class="indexterm" name="id2570580"></a> 321 321 Here is an example for a Red Hat Linux system: 322 </p><table border="0" summary="Simple list" class="simplelist"><tr><td> </td></tr><tr><td><em class="parameter"><code>[global]</code></em></td></tr><tr><td><a class="indexterm" name="id2576688"></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" title="Making an MS Windows Workstation or Server a Domain Member"><div class="titlepage"><div><div><h3 class="title"><a name="id2576703"></a>Making an MS Windows Workstation or Server a Domain Member</h3></div></div></div><p>322 </p><table class="simplelist" border="0" summary="Simple list"><tr><td> </td></tr><tr><td><em class="parameter"><code>[global]</code></em></td></tr><tr><td><a class="indexterm" name="id2570603"></a><em class="parameter"><code>add machine script = /usr/sbin/useradd -d /var/lib/nobody -g 100 -s /bin/false -M %u</code></em></td></tr></table><p> 323 </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2570618"></a>Making an MS Windows Workstation or Server a Domain Member</h3></div></div></div><p> 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" title="Windows 200x/XP Professional Client"><div class="titlepage"><div><div><h4 class="title"><a name="id2576714"></a>Windows 200x/XP Professional Client</h4></div></div></div><p>327 <a class="indexterm" name="id257 6722"></a>328 <a class="indexterm" name="id257 6729"></a>329 <a class="indexterm" name="id257 6739"></a>330 <a class="indexterm" name="id257 6745"></a>326 </p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2570628"></a>Windows 200x/XP Professional Client</h4></div></div></div><p> 327 <a class="indexterm" name="id2570636"></a> 328 <a class="indexterm" name="id2570643"></a> 329 <a class="indexterm" name="id2570653"></a> 330 <a class="indexterm" name="id2570660"></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="id257 6765"></a>338 <a class="indexterm" name="id257 6772"></a>337 <a class="indexterm" name="id2570679"></a> 338 <a class="indexterm" name="id2570686"></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="id257 6790"></a>343 <a class="indexterm" name="id257 6797"></a>344 <a class="indexterm" name="id257 6804"></a>345 <a class="indexterm" name="id257 6811"></a>342 <a class="indexterm" name="id2570705"></a> 343 <a class="indexterm" name="id2570712"></a> 344 <a class="indexterm" name="id2570719"></a> 345 <a class="indexterm" name="id2570725"></a> 346 346 The name of the account that is used to create domain member machine trust accounts can be 347 347 anything the network administrator may choose. If it is other than <code class="constant">root</code>, … … 349 349 <a class="link" href="smb.conf.5.html#USERNAMEMAP" target="_top">username map = /etc/samba/smbusers</a>. 350 350 </p><p> 351 <a class="indexterm" name="id257 6851"></a>352 <a class="indexterm" name="id257 6858"></a>353 <a class="indexterm" name="id257 6865"></a>351 <a class="indexterm" name="id2570766"></a> 352 <a class="indexterm" name="id2570772"></a> 353 <a class="indexterm" name="id2570779"></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" title="Windows NT4 Client"><div class="titlepage"><div><div><h4 class="title"><a name="id2576878"></a>Windows NT4 Client</h4></div></div></div><p>357 <a class="indexterm" name="id257 6886"></a>358 <a class="indexterm" name="id257 6893"></a>359 <a class="indexterm" name="id257 6900"></a>356 </p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2570792"></a>Windows NT4 Client</h4></div></div></div><p> 357 <a class="indexterm" name="id2570800"></a> 358 <a class="indexterm" name="id2570807"></a> 359 <a class="indexterm" name="id2570814"></a> 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="id257 6919"></a>367 <a class="indexterm" name="id257 6926"></a>368 <a class="indexterm" name="id257 6933"></a>369 <a class="indexterm" name="id257 6940"></a>366 <a class="indexterm" name="id2570834"></a> 367 <a class="indexterm" name="id2570841"></a> 368 <a class="indexterm" name="id2570848"></a> 369 <a class="indexterm" name="id2570855"></a> 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" title="Samba Client"><div class="titlepage"><div><div><h4 class="title"><a name="id2576961"></a>Samba Client</h4></div></div></div><p>375 <a class="indexterm" name="id257 6968"></a>374 </p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2570875"></a>Samba Client</h4></div></div></div><p> 375 <a class="indexterm" name="id2570883"></a> 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 </p></div></div></div><div class="sect1" title="Domain Member Server"><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="id257 6999"></a>379 <a class="indexterm" name="id257 7006"></a>380 <a class="indexterm" name="id257 7013"></a>381 <a class="indexterm" name="id257 7020"></a>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="id2570914"></a> 379 <a class="indexterm" name="id2570921"></a> 380 <a class="indexterm" name="id2570928"></a> 381 <a class="indexterm" name="id2570935"></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="id257 7039"></a>391 <a class="indexterm" name="id257 7048"></a>392 <a class="indexterm" name="id257 7055"></a>393 <a class="indexterm" name="id257 7062"></a>394 <a class="indexterm" name="id257 7069"></a>395 <a class="indexterm" name="id257 7076"></a>396 <a class="indexterm" name="id257 7082"></a>397 <a class="indexterm" name="id257 7089"></a>390 <a class="indexterm" name="id2570953"></a> 391 <a class="indexterm" name="id2570963"></a> 392 <a class="indexterm" name="id2570970"></a> 393 <a class="indexterm" name="id2570977"></a> 394 <a class="indexterm" name="id2570983"></a> 395 <a class="indexterm" name="id2570990"></a> 396 <a class="indexterm" name="id2570997"></a> 397 <a class="indexterm" name="id2571004"></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. … … 401 401 Server, and so on. 402 402 </em></span> 403 </p><div class="note" title="Note"style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>404 <a class="indexterm" name="id257 7106"></a>405 <a class="indexterm" name="id257 7112"></a>406 <a class="indexterm" name="id257 7119"></a>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="id2571020"></a> 405 <a class="indexterm" name="id2571027"></a> 406 <a class="indexterm" name="id2571034"></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="id257 7134"></a>413 <a class="indexterm" name="id257 7142"></a>414 <a class="indexterm" name="id257 7149"></a>412 <a class="indexterm" name="id2571049"></a> 413 <a class="indexterm" name="id2571056"></a> 414 <a class="indexterm" name="id2571063"></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" title="Joining an NT4-type Domain with Samba-3"><div class="titlepage"><div><div><h3 class="title"><a name="id2577168"></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="id257 7252"></a>419 </p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2571082"></a>Joining an NT4-type Domain with Samba-3</h3></div></div></div><p><a class="link" href="domain-member.html#assumptions" title="Table 6.1. Assumptions">Assumptions</a> lists names that are used in the remainder of this chapter.</p><div class="table"><a name="assumptions"></a><p class="title"><b>Table 6.1. Assumptions</b></p><div class="table-contents"><table summary="Assumptions" border="1"><colgroup><col align="right"><col align="left"></colgroup><tbody><tr><td align="right">Samba DMS NetBIOS name:</td><td align="left">SERV1</td></tr><tr><td align="right">Windows 200x/NT domain name:</td><td align="left">MIDEARTH</td></tr><tr><td align="right">Domain's PDC NetBIOS name:</td><td align="left">DOMPDC</td></tr><tr><td align="right">Domain's BDC NetBIOS names:</td><td align="left">DOMBDC1 and DOMBDC2</td></tr></tbody></table></div></div><br class="table-break"><p> 420 <a class="indexterm" name="id2571167"></a> 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="id257 7268"></a>424 <a class="indexterm" name="id257 7275"></a>425 <a class="indexterm" name="id257 7282"></a>426 <a class="indexterm" name="id257 7289"></a>423 <a class="indexterm" name="id2571183"></a> 424 <a class="indexterm" name="id2571190"></a> 425 <a class="indexterm" name="id2571197"></a> 426 <a class="indexterm" name="id2571204"></a> 427 427 Change (or add) your <a class="link" href="smb.conf.5.html#SECURITY" target="_top">security</a> line in the [global] section 428 428 of your <code class="filename">smb.conf</code> to read: 429 </p><table border="0" summary="Simple list" class="simplelist"><tr><td><a class="indexterm" name="id2577320"></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="id2571234"></a><em class="parameter"><code>security = domain</code></em></td></tr></table><p> 430 430 Note that if the parameter <em class="parameter"><code>security = user</code></em> is used, this machine would function as a 431 431 standalone server and not as a domain member server. Domain security mode causes Samba to work within the … … 434 434 Next change the <a class="link" href="smb.conf.5.html#WORKGROUP" target="_top">workgroup</a> line in the <em class="parameter"><code>[global]</code></em> 435 435 section to read: 436 </p><table border="0" summary="Simple list" class="simplelist"><tr><td><a class="indexterm" name="id2577368"></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="id2571282"></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="id257 7384"></a>440 <a class="indexterm" name="id257 7391"></a>439 <a class="indexterm" name="id2571298"></a> 440 <a class="indexterm" name="id2571305"></a> 441 441 You must also have the parameter <a class="link" href="smb.conf.5.html#ENCRYPTPASSWORDS" target="_top">encrypt passwords</a> 442 442 set to <code class="constant">yes</code> in order for your users to authenticate to the NT PDC. … … 444 444 parameter, but if it is specified in the <code class="filename">smb.conf</code> file, it must be set to <code class="constant">Yes</code>. 445 445 </p><p> 446 <a class="indexterm" name="id257 7430"></a>447 <a class="indexterm" name="id257 7437"></a>448 <a class="indexterm" name="id257 7443"></a>449 <a class="indexterm" name="id257 7450"></a>446 <a class="indexterm" name="id2571344"></a> 447 <a class="indexterm" name="id2571351"></a> 448 <a class="indexterm" name="id2571358"></a> 449 <a class="indexterm" name="id2571364"></a> 450 450 Finally, add (or modify) a <a class="link" href="smb.conf.5.html#PASSWORDSERVER" target="_top">password server</a> line in the [global] 451 451 section to read: 452 </p><table border="0" summary="Simple list" class="simplelist"><tr><td><a class="indexterm" name="id2577475"></a><em class="parameter"><code>password server = DOMPDC DOMBDC1 DOMBDC2</code></em></td></tr></table><p>452 </p><table class="simplelist" border="0" summary="Simple list"><tr><td><a class="indexterm" name="id2571389"></a><em class="parameter"><code>password server = DOMPDC DOMBDC1 DOMBDC2</code></em></td></tr></table><p> 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="id257 7494"></a>460 <a class="indexterm" name="id257 7501"></a>461 <a class="indexterm" name="id257 7508"></a>462 <a class="indexterm" name="id257 7515"></a>459 <a class="indexterm" name="id2571409"></a> 460 <a class="indexterm" name="id2571416"></a> 461 <a class="indexterm" name="id2571422"></a> 462 <a class="indexterm" name="id2571430"></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 border="0" summary="Simple list" class="simplelist"><tr><td><a class="indexterm" name="id2577530"></a><em class="parameter"><code>password server = *</code></em></td></tr></table><p>466 <a class="indexterm" name="id257 7542"></a>465 </p><table class="simplelist" border="0" summary="Simple list"><tr><td><a class="indexterm" name="id2571445"></a><em class="parameter"><code>password server = *</code></em></td></tr></table><p> 466 <a class="indexterm" name="id2571456"></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="id257 7558"></a>473 <a class="indexterm" name="id2571472"></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="id257 7591"></a>479 <a class="indexterm" name="id257 7598"></a>480 <a class="indexterm" name="id257 7604"></a>481 <a class="indexterm" name="id257 7611"></a>478 <a class="indexterm" name="id2571505"></a> 479 <a class="indexterm" name="id2571512"></a> 480 <a class="indexterm" name="id2571519"></a> 481 <a class="indexterm" name="id2571526"></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="id257 7634"></a>487 <a class="indexterm" name="id257 7641"></a>488 <a class="indexterm" name="id257 7648"></a>489 <a class="indexterm" name="id257 7655"></a>486 <a class="indexterm" name="id2571548"></a> 487 <a class="indexterm" name="id2571555"></a> 488 <a class="indexterm" name="id2571562"></a> 489 <a class="indexterm" name="id2571569"></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="id257 7691"></a>501 <a class="indexterm" name="id257 7703"></a>502 <a class="indexterm" name="id257 7709"></a>500 <a class="indexterm" name="id2571606"></a> 501 <a class="indexterm" name="id2571617"></a> 502 <a class="indexterm" name="id2571624"></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="id257 7767"></a>516 <a class="indexterm" name="id257 7773"></a>517 <a class="indexterm" name="id257 7780"></a>515 <a class="indexterm" name="id2571681"></a> 516 <a class="indexterm" name="id2571688"></a> 517 <a class="indexterm" name="id2571695"></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="id257 7792"></a>522 <a class="indexterm" name="id257 7802"></a>523 <a class="indexterm" name="id257 7809"></a>524 <a class="indexterm" name="id257 7817"></a>521 <a class="indexterm" name="id2571707"></a> 522 <a class="indexterm" name="id2571716"></a> 523 <a class="indexterm" name="id2571724"></a> 524 <a class="indexterm" name="id2571731"></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="id257 7845"></a>531 <a class="indexterm" name="id257 7852"></a>530 <a class="indexterm" name="id2571759"></a> 531 <a class="indexterm" name="id2571766"></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="id257 7866"></a>537 <a class="indexterm" name="id257 7873"></a>538 <a class="indexterm" name="id257 7880"></a>536 <a class="indexterm" name="id2571780"></a> 537 <a class="indexterm" name="id2571787"></a> 538 <a class="indexterm" name="id2571794"></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" title="Why Is This Better Than security = server?"><div class="titlepage"><div><div><h3 class="title"><a name="id2577904"></a>Why Is This Better Than <em class="parameter"><code>security = server</code></em>?</h3></div></div></div><p>546 <a class="indexterm" name="id257 7918"></a>547 <a class="indexterm" name="id257 7925"></a>548 <a class="indexterm" name="id257 7932"></a>545 </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2571819"></a>Why Is This Better Than <em class="parameter"><code>security = server</code></em>?</h3></div></div></div><p> 546 <a class="indexterm" name="id2571832"></a> 547 <a class="indexterm" name="id2571839"></a> 548 <a class="indexterm" name="id2571846"></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="id257 7966"></a>556 <a class="indexterm" name="id257 7973"></a>557 <a class="indexterm" name="id257 7979"></a>555 <a class="indexterm" name="id2571881"></a> 556 <a class="indexterm" name="id2571887"></a> 557 <a class="indexterm" name="id2571894"></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="id257 7999"></a>562 <a class="indexterm" name="id257 8005"></a>563 <a class="indexterm" name="id257 8012"></a>561 <a class="indexterm" name="id2571913"></a> 562 <a class="indexterm" name="id2571920"></a> 563 <a class="indexterm" name="id2571927"></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="id257 8030"></a>571 <a class="indexterm" name="id257 8036"></a>572 <a class="indexterm" name="id257 8043"></a>570 <a class="indexterm" name="id2571944"></a> 571 <a class="indexterm" name="id2571951"></a> 572 <a class="indexterm" name="id2571957"></a> 573 573 In addition, with <a class="link" href="smb.conf.5.html#SECURITY" target="_top">security = server</a>, every Samba daemon on a server has to 574 574 keep a connection open to the authenticating server for as long as that daemon lasts. This can drain the … … 578 578 connection resources. 579 579 </p><p> 580 <a class="indexterm" name="id257 8083"></a>581 <a class="indexterm" name="id257 8090"></a>582 <a class="indexterm" name="id257 8096"></a>583 <a class="indexterm" name="id257 8103"></a>580 <a class="indexterm" name="id2571998"></a> 581 <a class="indexterm" name="id2572004"></a> 582 <a class="indexterm" name="id2572011"></a> 583 <a class="indexterm" name="id2572017"></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 586 586 of NT groups the user belongs to, and so on. 587 </p><div class="note" title="Note"style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>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 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 </p></div></div></div><div class="sect1" title="Samba ADS Domain Membership"><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="id257 8153"></a>593 <a class="indexterm" name="id257 8160"></a>594 <a class="indexterm" name="id257 8169"></a>595 <a class="indexterm" name="id257 8176"></a>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="id2572067"></a> 593 <a class="indexterm" name="id2572074"></a> 594 <a class="indexterm" name="id2572083"></a> 595 <a class="indexterm" name="id2572090"></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" title="Configure smb.conf"><div class="titlepage"><div><div><h3 class="title"><a name="id2578186"></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="id2572100"></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 border="0" summary="Simple list" class="simplelist"><tr><td><a class="indexterm" name="id2578212"></a><em class="parameter"><code>realm = your.kerberos.REALM</code></em></td></tr><tr><td><a class="indexterm" name="id2578224"></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="id2578244"></a><em class="parameter"><code>encrypt passwords = yes</code></em></td></tr></table><p>601 <a class="indexterm" name="id257 8258"></a>602 <a class="indexterm" name="id257 8264"></a>603 <a class="indexterm" name="id257 8271"></a>604 <a class="indexterm" name="id257 8278"></a>605 <a class="indexterm" name="id257 8284"></a>600 </p><table class="simplelist" border="0" summary="Simple list"><tr><td><a class="indexterm" name="id2572126"></a><em class="parameter"><code>realm = your.kerberos.REALM</code></em></td></tr><tr><td><a class="indexterm" name="id2572138"></a><em class="parameter"><code>security = ADS</code></em></td></tr><tr><td># The following parameter need only be specified if present.</td></tr><tr><td># The default setting if not present is Yes.</td></tr><tr><td><a class="indexterm" name="id2572158"></a><em class="parameter"><code>encrypt passwords = yes</code></em></td></tr></table><p> 601 <a class="indexterm" name="id2572172"></a> 602 <a class="indexterm" name="id2572179"></a> 603 <a class="indexterm" name="id2572185"></a> 604 <a class="indexterm" name="id2572192"></a> 605 <a class="indexterm" name="id2572199"></a> 606 606 In case samba cannot correctly identify the appropriate ADS server using the realm name, use the 607 607 <a class="link" href="smb.conf.5.html#PASSWORDSERVER" target="_top">password server</a> option in <code class="filename">smb.conf</code>: 608 </p><table border="0" summary="Simple list" class="simplelist"><tr><td><a class="indexterm" name="id2578316"></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="id2572230"></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 611 611 infrastructure. There is no harm in specifying a preferred ADS domain controller using the <em class="parameter"><code>password 612 612 server</code></em>. 613 </p><div class="note" title="Note"style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>614 <a class="indexterm" name="id257 8342"></a>615 <a class="indexterm" name="id257 8349"></a>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="id2572257"></a> 615 <a class="indexterm" name="id2572264"></a> 616 616 You do <span class="emphasis"><em>not</em></span> need an smbpasswd file, and older clients will be authenticated as 617 617 if <a class="link" href="smb.conf.5.html#SECURITY" target="_top">security = domain</a>, although it will not do any harm and 618 618 allows you to have local users not in the domain. 619 </p></div></div><div class="sect2" title="Configure /etc/krb5.conf"><div class="titlepage"><div><div><h3 class="title"><a name="id2578377"></a>Configure <code class="filename">/etc/krb5.conf</code></h3></div></div></div><p>620 <a class="indexterm" name="id257 8389"></a>621 <a class="indexterm" name="id257 8396"></a>622 <a class="indexterm" name="id257 8405"></a>623 <a class="indexterm" name="id257 8412"></a>619 </p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2572291"></a>Configure <code class="filename">/etc/krb5.conf</code></h3></div></div></div><p> 620 <a class="indexterm" name="id2572303"></a> 621 <a class="indexterm" name="id2572310"></a> 622 <a class="indexterm" name="id2572319"></a> 623 <a class="indexterm" name="id2572326"></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="id257 8430"></a>628 <a class="indexterm" name="id257 8436"></a>629 <a class="indexterm" name="id257 8443"></a>630 <a class="indexterm" name="id257 8450"></a>631 <a class="indexterm" name="id257 8456"></a>627 <a class="indexterm" name="id2572344"></a> 628 <a class="indexterm" name="id2572351"></a> 629 <a class="indexterm" name="id2572358"></a> 630 <a class="indexterm" name="id2572364"></a> 631 <a class="indexterm" name="id2572371"></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="id257 8478"></a>639 <a class="indexterm" name="id257 8485"></a>640 <a class="indexterm" name="id257 8492"></a>641 <a class="indexterm" name="id257 8499"></a>642 <a class="indexterm" name="id257 8506"></a>643 <a class="indexterm" name="id257 8512"></a>638 <a class="indexterm" name="id2572393"></a> 639 <a class="indexterm" name="id2572399"></a> 640 <a class="indexterm" name="id2572406"></a> 641 <a class="indexterm" name="id2572413"></a> 642 <a class="indexterm" name="id2572420"></a> 643 <a class="indexterm" name="id2572427"></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="id257 8544"></a>652 <a class="indexterm" name="id257 8550"></a>653 <a class="indexterm" name="id257 8557"></a>654 <a class="indexterm" name="id257 8564"></a>655 <a class="indexterm" name="id257 8571"></a>656 <a class="indexterm" name="id257 8578"></a>651 <a class="indexterm" name="id2572458"></a> 652 <a class="indexterm" name="id2572465"></a> 653 <a class="indexterm" name="id2572472"></a> 654 <a class="indexterm" name="id2572478"></a> 655 <a class="indexterm" name="id2572485"></a> 656 <a class="indexterm" name="id2572492"></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="id257 8599"></a>662 <a class="indexterm" name="id2572513"></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="id257 8624"></a>677 <a class="indexterm" name="id2572539"></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="id257 8646"></a>695 <a class="indexterm" name="id257 8653"></a>694 <a class="indexterm" name="id2572561"></a> 695 <a class="indexterm" name="id2572567"></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="id257 8677"></a>701 <a class="indexterm" name="id257 8683"></a>702 <a class="indexterm" name="id257 8690"></a>703 <a class="indexterm" name="id257 8696"></a>700 <a class="indexterm" name="id2572591"></a> 701 <a class="indexterm" name="id2572598"></a> 702 <a class="indexterm" name="id2572604"></a> 703 <a class="indexterm" name="id2572611"></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 … … 708 708 (and no default etypes in krb5.conf). Unfortunately, this whole area is still 709 709 in a state of flux. 710 </p><div class="note" title="Note"style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>711 <a class="indexterm" name="id257 8718"></a>712 <a class="indexterm" name="id257 8725"></a>713 <a class="indexterm" name="id257 8732"></a>714 The realm must be in uppercase or you will get a <span class="quote">“<span class="quote"><span class="errorname">Cannot find KDC for715 requested realm while getting initial credentials</span></span>” </span>error (Kerberos710 </p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p> 711 <a class="indexterm" name="id2572632"></a> 712 <a class="indexterm" name="id2572639"></a> 713 <a class="indexterm" name="id2572646"></a> 714 The realm must be in uppercase or you will get a “<span class="quote"><span class="errorname">Cannot find KDC for 715 requested realm while getting initial credentials</span></span>” error (Kerberos 716 716 is case-sensitive!). 717 </p></div><div class="note" title="Note"style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>718 <a class="indexterm" name="id257 8749"></a>719 <a class="indexterm" name="id257 8756"></a>720 <a class="indexterm" name="id257 8762"></a>721 <a class="indexterm" name="id257 8769"></a>722 Time between the two servers must be synchronized. You will get a <span class="quote">“<span class="quote"><span class="errorname">kinit(v5): Clock skew too723 great while getting initial credentials</span></span>” </span>if the time difference (clock skew) is more than five minutes.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="id2572663"></a> 719 <a class="indexterm" name="id2572670"></a> 720 <a class="indexterm" name="id2572677"></a> 721 <a class="indexterm" name="id2572684"></a> 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 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="id257 8787"></a>726 <a class="indexterm" name="id257 8794"></a>725 <a class="indexterm" name="id2572702"></a> 726 <a class="indexterm" name="id2572708"></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="id257 8806"></a>730 <a class="indexterm" name="id257 8812"></a>731 <a class="indexterm" name="id257 8819"></a>732 <a class="indexterm" name="id257 8826"></a>729 <a class="indexterm" name="id2572720"></a> 730 <a class="indexterm" name="id2572727"></a> 731 <a class="indexterm" name="id2572733"></a> 732 <a class="indexterm" name="id2572740"></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="id257 8841"></a>738 <a class="indexterm" name="id257 8847"></a>739 <a class="indexterm" name="id257 8854"></a>737 <a class="indexterm" name="id2572755"></a> 738 <a class="indexterm" name="id2572762"></a> 739 <a class="indexterm" name="id2572768"></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="id257 8877"></a>745 <a class="indexterm" name="id257 8884"></a>746 <a class="indexterm" name="id257 8891"></a>747 <a class="indexterm" name="id257 8898"></a>744 <a class="indexterm" name="id2572791"></a> 745 <a class="indexterm" name="id2572798"></a> 746 <a class="indexterm" name="id2572805"></a> 747 <a class="indexterm" name="id2572812"></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 </p></div><div class="sect2" title="Create the Computer Account"><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="id257 8968"></a>752 <a class="indexterm" name="id257 8975"></a>753 <a class="indexterm" name="id257 8982"></a>754 <a class="indexterm" name="id257 8989"></a>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="id2572883"></a> 752 <a class="indexterm" name="id2572889"></a> 753 <a class="indexterm" name="id2572896"></a> 754 <a class="indexterm" name="id2572903"></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="id257 9024"></a>764 <a class="indexterm" name="id257 9030"></a>765 <a class="indexterm" name="id257 9037"></a>766 <a class="indexterm" name="id257 9044"></a>767 <a class="indexterm" name="id257 9051"></a>768 <a class="indexterm" name="id257 9058"></a>763 <a class="indexterm" name="id2572938"></a> 764 <a class="indexterm" name="id2572944"></a> 765 <a class="indexterm" name="id2572952"></a> 766 <a class="indexterm" name="id2572958"></a> 767 <a class="indexterm" name="id2572965"></a> 768 <a class="indexterm" name="id2572972"></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="id257 9108"></a>779 <a class="indexterm" name="id257 9115"></a>780 <a class="indexterm" name="id257 9122"></a>781 <a class="indexterm" name="id257 9129"></a>782 For example, you may want to create the machine trust account in a container called <span class="quote">“<span class="quote">Servers</span>”</span>783 under the organizational directory <span class="quote">“<span class="quote">Computers/BusinessUnit/Department,</span>”</span>like this:778 <a class="indexterm" name="id2573022"></a> 779 <a class="indexterm" name="id2573029"></a> 780 <a class="indexterm" name="id2573036"></a> 781 <a class="indexterm" name="id2573043"></a> 782 For example, you may want to create the machine trust account in a container called “<span class="quote">Servers</span>” 783 under the organizational directory “<span class="quote">Computers/BusinessUnit/Department,</span>” like this: 784 784 </p><pre class="screen"> 785 785 <code class="prompt">root# </code> <strong class="userinput"><code>net ads join "Computers/BusinessUnit/Department/Servers"</code></strong> … … 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" title="Possible Errors"><div class="titlepage"><div><div><h4 class="title"><a name="id2579178"></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="id2573092"></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="id257 9197"></a>795 <a class="indexterm" name="id257 9204"></a>796 <a class="indexterm" name="id257 9211"></a>794 <a class="indexterm" name="id2573111"></a> 795 <a class="indexterm" name="id2573118"></a> 796 <a class="indexterm" name="id2573125"></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="id257 9231"></a>801 <a class="indexterm" name="id257 9237"></a>800 <a class="indexterm" name="id2573145"></a> 801 <a class="indexterm" name="id2573152"></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="id257 9271"></a>807 <a class="indexterm" name="id257 9278"></a>808 <a class="indexterm" name="id257 9285"></a>806 <a class="indexterm" name="id2573185"></a> 807 <a class="indexterm" name="id2573192"></a> 808 <a class="indexterm" name="id2573199"></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 </p></div></div><div class="sect2" title="Testing Server Setup"><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="id257 9316"></a>814 <a class="indexterm" name="id257 9323"></a>815 <a class="indexterm" name="id257 9330"></a>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="id2573231"></a> 814 <a class="indexterm" name="id2573237"></a> 815 <a class="indexterm" name="id2573244"></a> 816 816 If the join was successful, you will see a new computer account with the 817 NetBIOS name of your Samba server in Active Directory (in the <span class="quote">“<span class="quote">Computers</span>”</span>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="id257 9346"></a>821 <a class="indexterm" name="id257 9353"></a>822 <a class="indexterm" name="id257 9362"></a>820 <a class="indexterm" name="id2573261"></a> 821 <a class="indexterm" name="id2573268"></a> 822 <a class="indexterm" name="id2573277"></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 825 825 <strong class="userinput"><code>klist tickets</code></strong>. Did you get a ticket for the server? Does it have 826 826 an encryption type of DES-CBC-MD5? 827 </p><div class="note" title="Note"style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>828 <a class="indexterm" name="id257 9389"></a>829 <a class="indexterm" name="id257 9396"></a>830 <a class="indexterm" name="id257 9403"></a>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="id2573304"></a> 829 <a class="indexterm" name="id2573310"></a> 830 <a class="indexterm" name="id2573317"></a> 831 831 Samba can use both DES-CBC-MD5 encryption as well as ARCFOUR-HMAC-MD5 encoding. 832 </p></div></div><div class="sect2" title="Testing with smbclient"><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="id257 9430"></a>834 <a class="indexterm" name="id257 9437"></a>835 <a class="indexterm" name="id257 9443"></a>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="id2573344"></a> 834 <a class="indexterm" name="id2573351"></a> 835 <a class="indexterm" name="id2573358"></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" title="Notes"><div class="titlepage"><div><div><h3 class="title"><a name="id2579471"></a>Notes</h3></div></div></div><p>840 <a class="indexterm" name="id257 9479"></a>841 <a class="indexterm" name="id257 9486"></a>842 <a class="indexterm" name="id257 9493"></a>839 </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2573385"></a>Notes</h3></div></div></div><p> 840 <a class="indexterm" name="id2573393"></a> 841 <a class="indexterm" name="id2573400"></a> 842 <a class="indexterm" name="id2573407"></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="id257 9505"></a>847 <a class="indexterm" name="id257 9512"></a>848 <a class="indexterm" name="id257 9519"></a>846 <a class="indexterm" name="id2573420"></a> 847 <a class="indexterm" name="id2573427"></a> 848 <a class="indexterm" name="id2573433"></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" title="Sharing User ID Mappings between Samba Domain Members"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2579543"></a>Sharing User ID Mappings between Samba Domain Members</h2></div></div></div><p>852 <a class="indexterm" name="id257 9552"></a>853 <a class="indexterm" name="id257 9559"></a>854 <a class="indexterm" name="id257 9565"></a>855 <a class="indexterm" name="id257 9572"></a>851 </p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2573458"></a>Sharing User ID Mappings between Samba Domain Members</h2></div></div></div><p> 852 <a class="indexterm" name="id2573466"></a> 853 <a class="indexterm" name="id2573473"></a> 854 <a class="indexterm" name="id2573480"></a> 855 <a class="indexterm" name="id2573486"></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="id257 9590"></a>860 <a class="indexterm" name="id257 9597"></a>861 <a class="indexterm" name="id257 9604"></a>859 <a class="indexterm" name="id2573505"></a> 860 <a class="indexterm" name="id2573512"></a> 861 <a class="indexterm" name="id2573518"></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="id257 9621"></a>867 <a class="indexterm" name="id257 9628"></a>866 <a class="indexterm" name="id2573536"></a> 867 <a class="indexterm" name="id2573543"></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 border="0" summary="Simple list" class="simplelist"><tr><td><a class="indexterm" name="id2579652"></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="id2573566"></a><em class="parameter"><code>ldap idmap suffix = ou=Idmap</code></em></td></tr></table><p> 870 870 See the <code class="filename">smb.conf</code> man page entry for the <a class="link" href="smb.conf.5.html#LDAPIDMAPSUFFIX" target="_top">ldap idmap suffix</a> 871 871 parameter for further information. 872 872 </p><p> 873 <a class="indexterm" name="id257 9688"></a>874 <a class="indexterm" name="id257 9694"></a>875 <a class="indexterm" name="id257 9702"></a>873 <a class="indexterm" name="id2573602"></a> 874 <a class="indexterm" name="id2573609"></a> 875 <a class="indexterm" name="id2573616"></a> 876 876 Do not forget to specify also the <a class="link" href="smb.conf.5.html#LDAPADMINDN" target="_top">ldap admin dn</a> 877 877 and to make certain to set the LDAP administrative password into the <code class="filename">secrets.tdb</code> using: … … 881 881 In place of <code class="literal">ldap-admin-password</code>, substitute the LDAP administration password for your 882 882 system. 883 </p></div><div class="sect1" title="Common Errors"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2579750"></a>Common Errors</h2></div></div></div><p>884 <a class="indexterm" name="id257 9757"></a>885 <a class="indexterm" name="id257 9764"></a>883 </p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2573664"></a>Common Errors</h2></div></div></div><p> 884 <a class="indexterm" name="id2573672"></a> 885 <a class="indexterm" name="id2573679"></a> 886 886 In the process of adding/deleting/re-adding domain member machine trust accounts, there are 887 many traps for the unwary player and many <span class="quote">“<span class="quote">little</span>”</span>things that can go wrong.887 many traps for the unwary player and many “<span class="quote">little</span>” things that can go wrong. 888 888 It is particularly interesting how often subscribers on the Samba mailing list have concluded 889 after repeated failed attempts to add a machine account that it is necessary to <span class="quote">“<span class="quote">reinstall</span>”</span>889 after repeated failed attempts to add a machine account that it is necessary to “<span class="quote">reinstall</span>” 890 890 MS Windows on the machine. In truth, it is seldom necessary to reinstall because of this type 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" title="Cannot Add Machine Back to Domain"><div class="titlepage"><div><div><h3 class="title"><a name="id2579789"></a>Cannot Add Machine Back to Domain</h3></div></div></div><p>894 <a class="indexterm" name="id257 9798"></a>895 <a class="indexterm" name="id257 9805"></a>896 <span class="quote">“<span class="quote">A Windows workstation was reinstalled. The original domain machine trust893 </p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2573704"></a>Cannot Add Machine Back to Domain</h3></div></div></div><p> 894 <a class="indexterm" name="id2573712"></a> 895 <a class="indexterm" name="id2573719"></a> 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 898 898 the same machine name. Attempts to add the machine fail with a message that the machine already 899 exists on the network I know it does not. Why is this failing?</span>” </span>900 </p><p> 901 <a class="indexterm" name="id257 9826"></a>902 <a class="indexterm" name="id257 9832"></a>899 exists on the network I know it does not. Why is this failing?</span>” 900 </p><p> 901 <a class="indexterm" name="id2573740"></a> 902 <a class="indexterm" name="id2573747"></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" title="Adding Machine to Domain Fails"><div class="titlepage"><div><div><h3 class="title"><a name="id2579865"></a>Adding Machine to Domain Fails</h3></div></div></div><p>911 <a class="indexterm" name="id257 9873"></a>912 <a class="indexterm" name="id257 9880"></a>913 <span class="quote">“<span class="quote">Adding a Windows 200x or XP Professional machine to the Samba PDC Domain fails with a910 </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2573779"></a>Adding Machine to Domain Fails</h3></div></div></div><p> 911 <a class="indexterm" name="id2573787"></a> 912 <a class="indexterm" name="id2573794"></a> 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 Please try again later."</span> Why?</span>” </span>916 </p><p> 917 <a class="indexterm" name="id257 9900"></a>915 Please try again later."</span> Why?</span>” 916 </p><p> 917 <a class="indexterm" name="id2573814"></a> 918 918 You should check that there is an <a class="link" href="smb.conf.5.html#ADDMACHINESCRIPT" target="_top">add machine script</a> in your <code class="filename">smb.conf</code> 919 919 file. If there is not, please add one that is appropriate for your OS platform. If a script … … 923 923 </p><p> 924 924 Possible causes include: 925 </p><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem"><p>926 <a class="indexterm" name="id257 9958"></a>927 <a class="indexterm" name="id257 9965"></a>925 </p><div class="itemizedlist"><ul type="disc"><li><p> 926 <a class="indexterm" name="id2573872"></a> 927 <a class="indexterm" name="id2573879"></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="id257 9976"></a>931 <a class="indexterm" name="id257 9983"></a>930 <a class="indexterm" name="id2573891"></a> 931 <a class="indexterm" name="id2573898"></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 </p></li><li class="listitem"><p>935 <a class="indexterm" name="id25 80000"></a>936 <a class="indexterm" name="id25 80007"></a>934 </p></li><li><p> 935 <a class="indexterm" name="id2573915"></a> 936 <a class="indexterm" name="id2573922"></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="id25 80024"></a>940 <a class="indexterm" name="id25 80031"></a>939 <a class="indexterm" name="id2573938"></a> 940 <a class="indexterm" name="id2573946"></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="id25 80063"></a>948 <a class="indexterm" name="id25 80070"></a>949 <a class="indexterm" name="id25 80076"></a>947 <a class="indexterm" name="id2573977"></a> 948 <a class="indexterm" name="id2573984"></a> 949 <a class="indexterm" name="id2573991"></a> 950 950 The <a class="link" href="smb.conf.5.html#ADDMACHINESCRIPT" target="_top">add machine script</a> does not create the 951 951 machine account in the Samba backend database; it is there only to create a UNIX system 952 952 account to which the Samba backend database account can be mapped. 953 </p></div><div class="sect2" title="I Can't Join a Windows 2003 PDC"><div class="titlepage"><div><div><h3 class="title"><a name="id2580101"></a>I Can't Join a Windows 2003 PDC</h3></div></div></div><p>954 <a class="indexterm" name="id25 80109"></a>955 <a class="indexterm" name="id25 80115"></a>956 <a class="indexterm" name="id25 80122"></a>957 <a class="indexterm" name="id25 80129"></a>953 </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2574015"></a>I Can't Join a Windows 2003 PDC</h3></div></div></div><p> 954 <a class="indexterm" name="id2574023"></a> 955 <a class="indexterm" name="id2574030"></a> 956 <a class="indexterm" name="id2574036"></a> 957 <a class="indexterm" name="id2574043"></a> 958 958 Windows 2003 requires SMB signing. Client-side SMB signing has been implemented in Samba-3.0. 959 959 Set <a class="link" href="smb.conf.5.html#CLIENTUSESPNEGO" target="_top">client use spnego = yes</a> when communicating
Note:
See TracChangeset
for help on using the changeset viewer.
