- Timestamp:
- Jul 6, 2011, 8:21:13 PM (14 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
trunk/server/docs/htmldocs/Samba3-HOWTO/domain-member.html
r414 r599 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 4.0"><link rel="home" href="index.html" title="The Official Samba 3.5.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#id2569109">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#id2569796">Manual Creation of Machine Trust Accounts</a></span></dt><dt><span class="sect2"><a href="domain-member.html#id2570233">Managing Domain Machine Accounts using NT4 Server Manager</a></span></dt><dt><span class="sect2"><a href="domain-member.html#id2570513">On-the-Fly Creation of Machine Trust Accounts</a></span></dt><dt><span class="sect2"><a href="domain-member.html#id2570619">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#id2571111">Joining an NT4-type Domain with Samba-3</a></span></dt><dt><span class="sect2"><a href="domain-member.html#id2571847">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#id2572129">Configure smb.conf</a></span></dt><dt><span class="sect2"><a href="domain-member.html#id2572320">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#id2573414">Notes</a></span></dt></dl></dd><dt><span class="sect1"><a href="domain-member.html#id2573486">Sharing User ID Mappings between Samba Domain Members</a></span></dt><dt><span class="sect1"><a href="domain-member.html#id2573692">Common Errors</a></span></dt><dd><dl><dt><span class="sect2"><a href="domain-member.html#id2573732">Cannot Add Machine Back to Domain</a></span></dt><dt><span class="sect2"><a href="domain-member.html#id2573808">Adding Machine to Domain Fails</a></span></dt><dt><span class="sect2"><a href="domain-member.html#id2574044">I Can't Join a Windows 2003 PDC</a></span></dt></dl></dd></dl></div><p>2 <a class="indexterm" name="id 2569052"></a>3 <a class="indexterm" name="id 2569059"></a>4 <a class="indexterm" name="id 2569066"></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.75.2"><link rel="home" href="index.html" title="The Official Samba 3.5.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#id339970">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#id340608">Manual Creation of Machine Trust Accounts</a></span></dt><dt><span class="sect2"><a href="domain-member.html#id341023">Managing Domain Machine Accounts using NT4 Server Manager</a></span></dt><dt><span class="sect2"><a href="domain-member.html#id341289">On-the-Fly Creation of Machine Trust Accounts</a></span></dt><dt><span class="sect2"><a href="domain-member.html#id341389">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#id341842">Joining an NT4-type Domain with Samba-3</a></span></dt><dt><span class="sect2"><a href="domain-member.html#id342539">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#id342799">Configure <code class="filename">smb.conf</code></a></span></dt><dt><span class="sect2"><a href="domain-member.html#id342981">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#id344013">Notes</a></span></dt></dl></dd><dt><span class="sect1"><a href="domain-member.html#id344082">Sharing User ID Mappings between Samba Domain Members</a></span></dt><dt><span class="sect1"><a href="domain-member.html#id344280">Common Errors</a></span></dt><dd><dl><dt><span class="sect2"><a href="domain-member.html#id344314">Cannot Add Machine Back to Domain</a></span></dt><dt><span class="sect2"><a href="domain-member.html#id344384">Adding Machine to Domain Fails</a></span></dt><dt><span class="sect2"><a href="domain-member.html#id344604">I Can't Join a Windows 2003 PDC</a></span></dt></dl></dd></dl></div><p> 2 <a class="indexterm" name="id339923"></a> 3 <a class="indexterm" name="id339930"></a> 4 <a class="indexterm" name="id339936"></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="id 2569086"></a>11 <a class="indexterm" name="id 2569093"></a>10 <a class="indexterm" name="id339952"></a> 11 <a class="indexterm" name="id339958"></a> 12 12 This chapter covers background information pertaining to domain membership, 13 13 the Samba configuration for it, and MS Windows client procedures for joining a … … 17 17 misinformation, incorrect understanding, and lack of knowledge. Hopefully 18 18 this chapter will fill the voids. 19 </p><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2569109"></a>Features and Benefits</h2></div></div></div><p>20 <a class="indexterm" name="id 2569117"></a>21 <a class="indexterm" name="id 2569124"></a>22 <a class="indexterm" name="id 2569131"></a>19 </p><div class="sect1" title="Features and Benefits"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id339970"></a>Features and Benefits</h2></div></div></div><p> 20 <a class="indexterm" name="id339978"></a> 21 <a class="indexterm" name="id339985"></a> 22 <a class="indexterm" name="id339992"></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="id 2569163"></a>31 <a class="indexterm" name="id 2569170"></a>32 <a class="indexterm" name="id 2569176"></a>33 <a class="indexterm" name="id 2569183"></a>30 <a class="indexterm" name="id340020"></a> 31 <a class="indexterm" name="id340027"></a> 32 <a class="indexterm" name="id340033"></a> 33 <a class="indexterm" name="id340040"></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 type="disc"><li><p>38 <a class="indexterm" name="id 2569203"></a>37 </p><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem"><p> 38 <a class="indexterm" name="id340058"></a> 39 39 MS Windows workstation users get the benefit of SSO. 40 </p></li><li ><p>41 <a class="indexterm" name="id 2569215"></a>42 <a class="indexterm" name="id 2569222"></a>43 <a class="indexterm" name="id 2569229"></a>44 <a class="indexterm" name="id 2569236"></a>40 </p></li><li class="listitem"><p> 41 <a class="indexterm" name="id340069"></a> 42 <a class="indexterm" name="id340076"></a> 43 <a class="indexterm" name="id340083"></a> 44 <a class="indexterm" name="id340090"></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 ><p>50 <a class="indexterm" name="id 2569250"></a>51 <a class="indexterm" name="id 2569257"></a>49 </p></li><li class="listitem"><p> 50 <a class="indexterm" name="id340103"></a> 51 <a class="indexterm" name="id340109"></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 ><p>55 <a class="indexterm" name="id 2569276"></a>56 <a class="indexterm" name="id 2569283"></a>57 <a class="indexterm" name="id 2569290"></a>58 <a class="indexterm" name="id 2569297"></a>54 </p></li><li class="listitem"><p> 55 <a class="indexterm" name="id340127"></a> 56 <a class="indexterm" name="id340134"></a> 57 <a class="indexterm" name="id340141"></a> 58 <a class="indexterm" name="id340148"></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 ><p>62 <a class="indexterm" name="id 2569316"></a>63 <a class="indexterm" name="id 2569323"></a>64 <a class="indexterm" name="id 2569330"></a>61 </p></li><li class="listitem"><p> 62 <a class="indexterm" name="id340166"></a> 63 <a class="indexterm" name="id340173"></a> 64 <a class="indexterm" name="id340180"></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 ><p>68 <a class="indexterm" name="id 2569344"></a>69 <a class="indexterm" name="id 2569351"></a>70 <a class="indexterm" name="id 2569357"></a>71 <a class="indexterm" name="id 2569364"></a>67 </p></li><li class="listitem"><p> 68 <a class="indexterm" name="id340192"></a> 69 <a class="indexterm" name="id340199"></a> 70 <a class="indexterm" name="id340205"></a> 71 <a class="indexterm" name="id340212"></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" 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="id 2569393"></a>79 <a class="indexterm" name="id 2569399"></a>80 <a class="indexterm" name="id 2569406"></a>81 <a class="indexterm" name="id 2569413"></a>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="id340236"></a> 79 <a class="indexterm" name="id340243"></a> 80 <a class="indexterm" name="id340249"></a> 81 <a class="indexterm" name="id340256"></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">computer account.</span>”The83 the domain controller server. In Windows terminology, this is known as a <span class="quote">“<span class="quote">computer account.</span>”</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="id 2569432"></a>88 <a class="indexterm" name="id 2569442"></a>89 <a class="indexterm" name="id 2569449"></a>90 <a class="indexterm" name="id 2569456"></a>91 <a class="indexterm" name="id 2569463"></a>87 <a class="indexterm" name="id340273"></a> 88 <a class="indexterm" name="id340282"></a> 89 <a class="indexterm" name="id340289"></a> 90 <a class="indexterm" name="id340296"></a> 91 <a class="indexterm" name="id340302"></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="id 2569484"></a>100 <a class="indexterm" name="id 2569491"></a>101 <a class="indexterm" name="id 2569497"></a>102 <a class="indexterm" name="id 2569504"></a>99 <a class="indexterm" name="id340318"></a> 100 <a class="indexterm" name="id340325"></a> 101 <a class="indexterm" name="id340331"></a> 102 <a class="indexterm" name="id340338"></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 type="disc"><li><p>110 <a class="indexterm" name="id 2569521"></a>111 <a class="indexterm" name="id 2569528"></a>112 <a class="indexterm" name="id 2569535"></a>109 </p><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem"><p> 110 <a class="indexterm" name="id340352"></a> 111 <a class="indexterm" name="id340359"></a> 112 <a class="indexterm" name="id340366"></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="id 2569567"></a>118 <a class="indexterm" name="id 2569574"></a>119 <a class="indexterm" name="id 2569581"></a>120 <a class="indexterm" name="id 2569587"></a>121 <a class="indexterm" name="id 2569594"></a>122 <a class="indexterm" name="id 2569601"></a>117 <a class="indexterm" name="id340395"></a> 118 <a class="indexterm" name="id340402"></a> 119 <a class="indexterm" name="id340408"></a> 120 <a class="indexterm" name="id340415"></a> 121 <a class="indexterm" name="id340422"></a> 122 <a class="indexterm" name="id340429"></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="id 2569623"></a>129 <a class="indexterm" name="id 2569630"></a>130 <a class="indexterm" name="id 2569637"></a>131 <a class="indexterm" name="id 2569643"></a>128 <a class="indexterm" name="id340449"></a> 129 <a class="indexterm" name="id340455"></a> 130 <a class="indexterm" name="id340462"></a> 131 <a class="indexterm" name="id340468"></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 ><p>136 <a class="indexterm" name="id 2569664"></a>137 <a class="indexterm" name="id 2569671"></a>135 </p></li><li class="listitem"><p> 136 <a class="indexterm" name="id340487"></a> 137 <a class="indexterm" name="id340494"></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="id 2569697"></a>143 <a class="indexterm" name="id340518"></a> 144 144 There are three ways to create Machine Trust Accounts: 145 </p><div class="itemizedlist"><ul type="disc"><li><p>146 <a class="indexterm" name="id 2569713"></a>145 </p><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem"><p> 146 <a class="indexterm" name="id340533"></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 ><p>150 <a class="indexterm" name="id 2569727"></a>151 <a class="indexterm" name="id 2569734"></a>149 </p></li><li class="listitem"><p> 150 <a class="indexterm" name="id340546"></a> 151 <a class="indexterm" name="id340552"></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 ><p>157 <a class="indexterm" name="id 2569750"></a>158 <a class="indexterm" name="id 2569757"></a>159 “<span class="quote">On-the-fly</span>”creation. The Samba Machine Trust Account is automatically156 </p></li><li class="listitem"><p> 157 <a class="indexterm" name="id340566"></a> 158 <a class="indexterm" name="id340573"></a> 159 <span class="quote">“<span class="quote">On-the-fly</span>”</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="id 2569776"></a>165 <a class="indexterm" name="id 2569782"></a>164 <a class="indexterm" name="id340589"></a> 165 <a class="indexterm" name="id340596"></a> 166 166 Neither MS Windows NT4/200x/XP Professional, nor Samba, provide any method for enforcing the method of machine 167 167 trust account creation. This is a matter of the administrator's choice. 168 </p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2569796"></a>Manual Creation of Machine Trust Accounts</h3></div></div></div><p>169 <a class="indexterm" name="id 2569804"></a>170 <a class="indexterm" name="id 2569811"></a>171 <a class="indexterm" name="id 2569817"></a>172 <a class="indexterm" name="id 2569823"></a>168 </p><div class="sect2" title="Manual Creation of Machine Trust Accounts"><div class="titlepage"><div><div><h3 class="title"><a name="id340608"></a>Manual Creation of Machine Trust Accounts</h3></div></div></div><p> 169 <a class="indexterm" name="id340616"></a> 170 <a class="indexterm" name="id340623"></a> 171 <a class="indexterm" name="id340628"></a> 172 <a class="indexterm" name="id340635"></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">adduser</span>”command175 This can be done using <code class="literal">vipw</code> or another <span class="quote">“<span class="quote">adduser</span>”</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="id 2569892"></a>187 <a class="indexterm" name="id 2569899"></a>188 <a class="indexterm" name="id 2569906"></a>189 In the example above there is an existing system group “<span class="quote">machines</span>”which is used190 as the primary group for all machine accounts. In the following examples the “<span class="quote">machines</span>”group186 <a class="indexterm" name="id340700"></a> 187 <a class="indexterm" name="id340707"></a> 188 <a class="indexterm" name="id340714"></a> 189 In the example above there is an existing system group <span class="quote">“<span class="quote">machines</span>”</span> which is used 190 as the primary group for all machine accounts. In the following examples the <span class="quote">“<span class="quote">machines</span>”</span> group 191 191 numeric GID is 100. 192 192 </p><p> 193 <a class="indexterm" name="id 2569926"></a>194 <a class="indexterm" name="id 2569933"></a>193 <a class="indexterm" name="id340733"></a> 194 <a class="indexterm" name="id340740"></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="id 2569974"></a>202 <a class="indexterm" name="id 2569981"></a>203 <a class="indexterm" name="id 2569987"></a>204 <a class="indexterm" name="id 2569994"></a>201 <a class="indexterm" name="id340779"></a> 202 <a class="indexterm" name="id340786"></a> 203 <a class="indexterm" name="id340793"></a> 204 <a class="indexterm" name="id340800"></a> 205 205 The <code class="filename">/etc/passwd</code> entry will list the machine name 206 with a “<span class="quote">$</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">doppy</span>”would have an206 with a <span class="quote">“<span class="quote">$</span>”</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">“<span class="quote">doppy</span>”</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="id 2570036"></a>214 <a class="indexterm" name="id 2570043"></a>215 <a class="indexterm" name="id 2570050"></a>213 <a class="indexterm" name="id340840"></a> 214 <a class="indexterm" name="id340846"></a> 215 <a class="indexterm" name="id340853"></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>”must be219 name of the client to be joined to the domain. The <span class="quote">“<span class="quote">$</span>”</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="id 2570076"></a>224 <a class="indexterm" name="id 2570083"></a>225 <a class="indexterm" name="id 2570090"></a>223 <a class="indexterm" name="id340876"></a> 224 <a class="indexterm" name="id340883"></a> 225 <a class="indexterm" name="id340890"></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="id 2570131"></a>236 <a class="indexterm" name="id 2570138"></a>237 <a class="indexterm" name="id 2570145"></a>238 <a class="indexterm" name="id 2570152"></a>235 <a class="indexterm" name="id340928"></a> 236 <a class="indexterm" name="id340935"></a> 237 <a class="indexterm" name="id340942"></a> 238 <a class="indexterm" name="id340948"></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" 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="id 2570174"></a>244 <a class="indexterm" name="id 2570181"></a>245 <a class="indexterm" name="id 2570187"></a>246 <a class="indexterm" name="id 2570194"></a>247 <a class="indexterm" name="id 2570201"></a>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="id340969"></a> 244 <a class="indexterm" name="id340976"></a> 245 <a class="indexterm" name="id340982"></a> 246 <a class="indexterm" name="id340989"></a> 247 <a class="indexterm" name="id340996"></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="id 2570210"></a>250 <a class="indexterm" name="id341004"></a> 251 251 the <span class="application">Server Manager</span>. From the time at which the 252 252 account is created to the time the client joins the domain and … … 255 255 trusts members of the domain and will serve out a large degree of user 256 256 information to such clients. You have been warned! 257 </p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2570233"></a>Managing Domain Machine Accounts using NT4 Server Manager</h3></div></div></div><p>258 <a class="indexterm" name="id 2570241"></a>259 <a class="indexterm" name="id 2570248"></a>260 <a class="indexterm" name="id 2570256"></a>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="id341023"></a>Managing Domain Machine Accounts using NT4 Server Manager</h3></div></div></div><p> 258 <a class="indexterm" name="id341031"></a> 259 <a class="indexterm" name="id341038"></a> 260 <a class="indexterm" name="id341045"></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="id 2570281"></a>266 <a class="indexterm" name="id 2570288"></a>267 <a class="indexterm" name="id 2570295"></a>268 <a class="indexterm" name="id 2570301"></a>265 <a class="indexterm" name="id341068"></a> 266 <a class="indexterm" name="id341075"></a> 267 <a class="indexterm" name="id341082"></a> 268 <a class="indexterm" name="id341088"></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="id 2570340"></a>276 <a class="indexterm" name="id 2570346"></a>275 <a class="indexterm" name="id341125"></a> 276 <a class="indexterm" name="id341131"></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="id 2570391"></a>287 <a class="indexterm" name="id 2570398"></a>286 <a class="indexterm" name="id341171"></a> 287 <a class="indexterm" name="id341178"></a> 288 288 Launch the <code class="literal">srvmgr.exe</code> (Server Manager for Domains) and follow these steps: 289 </p><div class="procedure" ><a name="id2570413"></a><p class="title"><b>Procedure 6.1. Server Manager Account Machine Account Management</b></p><ol type="1"><li><p>289 </p><div class="procedure" title="Procedure 6.1. Server Manager Account Machine Account Management"><a name="id341192"></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> 290 290 From the menu select <span class="guimenu">Computer</span>. 291 </p></li><li ><p>291 </p></li><li class="step" title="Step 2"><p> 292 292 Click <span class="guimenuitem">Select Domain</span>. 293 </p></li><li ><p>293 </p></li><li class="step" title="Step 3"><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 ><p>297 </p></li><li class="step" title="Step 4"><p> 298 298 Again from the menu select <span class="guimenu">Computer</span>. 299 </p></li><li ><p>299 </p></li><li class="step" title="Step 5"><p> 300 300 Select <span class="guimenuitem">Add to Domain</span>. 301 </p></li><li ><p>301 </p></li><li class="step" title="Step 6"><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" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2570513"></a>On-the-Fly Creation of Machine Trust Accounts</h3></div></div></div><p>307 <a class="indexterm" name="id 2570522"></a>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="id341289"></a>On-the-Fly Creation of Machine Trust Accounts</h3></div></div></div><p> 307 <a class="indexterm" name="id341297"></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="id 2570537"></a>312 <a class="indexterm" name="id 2570547"></a>313 <a class="indexterm" name="id 2570554"></a>311 <a class="indexterm" name="id341311"></a> 312 <a class="indexterm" name="id341321"></a> 313 <a class="indexterm" name="id341327"></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="id 2570575"></a>320 <a class="indexterm" name="id 2570582"></a>319 <a class="indexterm" name="id341346"></a> 320 <a class="indexterm" name="id341353"></a> 321 321 Here is an example for a Red Hat Linux system: 322 </p><table class="simplelist" border="0" summary="Simple list"><tr><td> </td></tr><tr><td><em class="parameter"><code>[global]</code></em></td></tr><tr><td><a class="indexterm" name="id2570604"></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="id2570619"></a>Making an MS Windows Workstation or Server a Domain Member</h3></div></div></div><p>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="id341375"></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="id341389"></a>Making an MS Windows Workstation or Server a Domain Member</h3></div></div></div><p> 324 324 The procedure for making an MS Windows workstation or server a member of the domain varies 325 325 with the version of Windows. 326 </p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2570630"></a>Windows 200x/XP Professional Client</h4></div></div></div><p>327 <a class="indexterm" name="id 2570638"></a>328 <a class="indexterm" name="id 2570645"></a>329 <a class="indexterm" name="id 2570655"></a>330 <a class="indexterm" name="id 2570662"></a>326 </p><div class="sect3" title="Windows 200x/XP Professional Client"><div class="titlepage"><div><div><h4 class="title"><a name="id341398"></a>Windows 200x/XP Professional Client</h4></div></div></div><p> 327 <a class="indexterm" name="id341406"></a> 328 <a class="indexterm" name="id341413"></a> 329 <a class="indexterm" name="id341422"></a> 330 <a class="indexterm" name="id341429"></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. … … 337 337 by granting the <code class="literal">SeMachineAccountPrivilege</code> privilege to the user account. 338 338 </p><p> 339 <a class="indexterm" name="id 2570701"></a>340 <a class="indexterm" name="id 2570708"></a>339 <a class="indexterm" name="id341464"></a> 340 <a class="indexterm" name="id341471"></a> 341 341 For security reasons, the password for this administrator account should be set 342 342 to a password that is other than that used for the root user in <code class="filename">/etc/passwd</code>. 343 343 </p><p> 344 <a class="indexterm" name="id 2570726"></a>345 <a class="indexterm" name="id 2570733"></a>346 <a class="indexterm" name="id 2570740"></a>347 <a class="indexterm" name="id 2570747"></a>344 <a class="indexterm" name="id341488"></a> 345 <a class="indexterm" name="id341495"></a> 346 <a class="indexterm" name="id341501"></a> 347 <a class="indexterm" name="id341508"></a> 348 348 The name of the account that is used to create domain member machine trust accounts can be 349 349 anything the network administrator may choose. If it is other than <code class="constant">root</code>, … … 351 351 <a class="link" href="smb.conf.5.html#USERNAMEMAP" target="_top">username map = /etc/samba/smbusers</a>. 352 352 </p><p> 353 <a class="indexterm" name="id 2570787"></a>354 <a class="indexterm" name="id 2570794"></a>355 <a class="indexterm" name="id 2570801"></a>353 <a class="indexterm" name="id341546"></a> 354 <a class="indexterm" name="id341552"></a> 355 <a class="indexterm" name="id341559"></a> 356 356 The session key of the Samba administrator account acts as an encryption key for setting the password of the machine trust 357 357 account. The Machine Trust Account will be created on-the-fly, or updated if it already exists. 358 </p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2570814"></a>Windows NT4 Client</h4></div></div></div><p>359 <a class="indexterm" name="id 2570822"></a>360 <a class="indexterm" name="id 2570829"></a>361 <a class="indexterm" name="id 2570836"></a>358 </p></div><div class="sect3" title="Windows NT4 Client"><div class="titlepage"><div><div><h4 class="title"><a name="id341570"></a>Windows NT4 Client</h4></div></div></div><p> 359 <a class="indexterm" name="id341577"></a> 360 <a class="indexterm" name="id341584"></a> 361 <a class="indexterm" name="id341590"></a> 362 362 If the Machine Trust Account was created manually, on the 363 363 Identification Changes menu enter the domain name, but do not … … 366 366 to the domain. 367 367 </p><p> 368 <a class="indexterm" name="id 2570855"></a>369 <a class="indexterm" name="id 2570862"></a>370 <a class="indexterm" name="id 2570869"></a>371 <a class="indexterm" name="id 2570876"></a>368 <a class="indexterm" name="id341609"></a> 369 <a class="indexterm" name="id341615"></a> 370 <a class="indexterm" name="id341622"></a> 371 <a class="indexterm" name="id341629"></a> 372 372 If the Machine Trust Account is to be created on the fly, on the Identification Changes menu enter the domain 373 373 name and check the box <span class="guilabel">Create a Computer Account in the Domain</span>. In this case, joining 374 374 the domain proceeds as above for Windows 2000 (i.e., you must supply a Samba administrator account when 375 375 prompted). 376 </p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2570897"></a>Samba Client</h4></div></div></div><p>377 <a class="indexterm" name="id 2570904"></a>376 </p></div><div class="sect3" title="Samba Client"><div class="titlepage"><div><div><h4 class="title"><a name="id341646"></a>Samba Client</h4></div></div></div><p> 377 <a class="indexterm" name="id341654"></a> 378 378 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>. 379 </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>380 <a class="indexterm" name="id 2570935"></a>381 <a class="indexterm" name="id 2570942"></a>382 <a class="indexterm" name="id 2570949"></a>383 <a class="indexterm" name="id 2570956"></a>379 </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> 380 <a class="indexterm" name="id341682"></a> 381 <a class="indexterm" name="id341689"></a> 382 <a class="indexterm" name="id341696"></a> 383 <a class="indexterm" name="id341703"></a> 384 384 This mode of server operation involves the Samba machine being made a member 385 385 of a domain security context. This means by definition that all user … … 390 390 </p><p> 391 391 <span class="emphasis"><em> 392 <a class="indexterm" name="id 2570982"></a>393 <a class="indexterm" name="id 2570991"></a>394 <a class="indexterm" name="id 2570998"></a>395 <a class="indexterm" name="id 2571005"></a>396 <a class="indexterm" name="id 2571012"></a>397 <a class="indexterm" name="id 2571019"></a>398 <a class="indexterm" name="id 2571025"></a>399 <a class="indexterm" name="id 2571032"></a>392 <a class="indexterm" name="id341722"></a> 393 <a class="indexterm" name="id341731"></a> 394 <a class="indexterm" name="id341738"></a> 395 <a class="indexterm" name="id341744"></a> 396 <a class="indexterm" name="id341751"></a> 397 <a class="indexterm" name="id341758"></a> 398 <a class="indexterm" name="id341765"></a> 399 <a class="indexterm" name="id341771"></a> 400 400 Of course it should be clear that the authentication backend itself could be 401 401 from any distributed directory architecture server that is supported by Samba. … … 403 403 Server, and so on. 404 404 </em></span> 405 </p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>406 <a class="indexterm" name="id 2571048"></a>407 <a class="indexterm" name="id 2571055"></a>408 <a class="indexterm" name="id 2571062"></a>405 </p><div class="note" title="Note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p> 406 <a class="indexterm" name="id341786"></a> 407 <a class="indexterm" name="id341793"></a> 408 <a class="indexterm" name="id341799"></a> 409 409 When Samba is configured to use an LDAP or other identity management and/or 410 410 directory service, it is Samba that continues to perform user and machine … … 412 412 authentication handling in place of what Samba is designed to do. 413 413 </p></div><p> 414 <a class="indexterm" name="id 2571077"></a>415 <a class="indexterm" name="id 2571084"></a>416 <a class="indexterm" name="id 2571092"></a>414 <a class="indexterm" name="id341812"></a> 415 <a class="indexterm" name="id341819"></a> 416 <a class="indexterm" name="id341826"></a> 417 417 Please refer to <a class="link" href="samba-pdc.html" title="Chapter 4. Domain Control">Domain Control</a>, for more information regarding 418 418 how to create a domain machine account for a domain member server as well as for 419 419 information on how to enable the Samba domain member machine to join the domain 420 420 and be fully trusted by it. 421 </p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2571111"></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>422 <a class="indexterm" name="id 2571195"></a>421 </p><div class="sect2" title="Joining an NT4-type Domain with Samba-3"><div class="titlepage"><div><div><h3 class="title"><a name="id341842"></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> 422 <a class="indexterm" name="id341925"></a> 423 423 First, you must edit your <code class="filename">smb.conf</code> file to tell Samba it should now use domain security. 424 424 </p><p> 425 <a class="indexterm" name="id 2571211"></a>426 <a class="indexterm" name="id 2571218"></a>427 <a class="indexterm" name="id 2571225"></a>428 <a class="indexterm" name="id 2571232"></a>425 <a class="indexterm" name="id341941"></a> 426 <a class="indexterm" name="id341947"></a> 427 <a class="indexterm" name="id341954"></a> 428 <a class="indexterm" name="id341961"></a> 429 429 Change (or add) your <a class="link" href="smb.conf.5.html#SECURITY" target="_top">security</a> line in the [global] section 430 430 of your <code class="filename">smb.conf</code> to read: 431 </p><table class="simplelist" border="0" summary="Simple list"><tr><td><a class="indexterm" name="id2571263"></a><em class="parameter"><code>security = domain</code></em></td></tr></table><p>431 </p><table border="0" summary="Simple list" class="simplelist"><tr><td><a class="indexterm" name="id341991"></a><em class="parameter"><code>security = domain</code></em></td></tr></table><p> 432 432 Note that if the parameter <em class="parameter"><code>security = user</code></em> is used, this machine would function as a 433 433 standalone server and not as a domain member server. Domain security mode causes Samba to work within the … … 436 436 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> 437 437 section to read: 438 </p><table class="simplelist" border="0" summary="Simple list"><tr><td><a class="indexterm" name="id2571311"></a><em class="parameter"><code>workgroup = MIDEARTH</code></em></td></tr></table><p>438 </p><table border="0" summary="Simple list" class="simplelist"><tr><td><a class="indexterm" name="id342036"></a><em class="parameter"><code>workgroup = MIDEARTH</code></em></td></tr></table><p> 439 439 This is the name of the domain we are joining. 440 440 </p><p> 441 <a class="indexterm" name="id 2571327"></a>442 <a class="indexterm" name="id 2571334"></a>441 <a class="indexterm" name="id342051"></a> 442 <a class="indexterm" name="id342058"></a> 443 443 You must also have the parameter <a class="link" href="smb.conf.5.html#ENCRYPTPASSWORDS" target="_top">encrypt passwords</a> 444 444 set to <code class="constant">yes</code> in order for your users to authenticate to the NT PDC. … … 446 446 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>. 447 447 </p><p> 448 <a class="indexterm" name="id 2571373"></a>449 <a class="indexterm" name="id 2571379"></a>450 <a class="indexterm" name="id 2571386"></a>451 <a class="indexterm" name="id 2571393"></a>448 <a class="indexterm" name="id342094"></a> 449 <a class="indexterm" name="id342101"></a> 450 <a class="indexterm" name="id342108"></a> 451 <a class="indexterm" name="id342114"></a> 452 452 Finally, add (or modify) a <a class="link" href="smb.conf.5.html#PASSWORDSERVER" target="_top">password server</a> line in the [global] 453 453 section to read: 454 </p><table class="simplelist" border="0" summary="Simple list"><tr><td><a class="indexterm" name="id2571417"></a><em class="parameter"><code>password server = DOMPDC DOMBDC1 DOMBDC2</code></em></td></tr></table><p>454 </p><table border="0" summary="Simple list" class="simplelist"><tr><td><a class="indexterm" name="id342138"></a><em class="parameter"><code>password server = DOMPDC DOMBDC1 DOMBDC2</code></em></td></tr></table><p> 455 455 These are the PDC and BDCs Samba 456 456 will attempt to contact in order to authenticate users. Samba will … … 459 459 among Domain Controllers. 460 460 </p><p> 461 <a class="indexterm" name="id 2571437"></a>462 <a class="indexterm" name="id 2571444"></a>463 <a class="indexterm" name="id 2571451"></a>464 <a class="indexterm" name="id 2571458"></a>461 <a class="indexterm" name="id342155"></a> 462 <a class="indexterm" name="id342162"></a> 463 <a class="indexterm" name="id342169"></a> 464 <a class="indexterm" name="id342176"></a> 465 465 Alternatively, if you want smbd to determine automatically the list of domain controllers to use for 466 466 authentication, you may set this line to be: 467 </p><table class="simplelist" border="0" summary="Simple list"><tr><td><a class="indexterm" name="id2571473"></a><em class="parameter"><code>password server = *</code></em></td></tr></table><p>468 <a class="indexterm" name="id 2571485"></a>467 </p><table border="0" summary="Simple list" class="simplelist"><tr><td><a class="indexterm" name="id342189"></a><em class="parameter"><code>password server = *</code></em></td></tr></table><p> 468 <a class="indexterm" name="id342201"></a> 469 469 This method allows Samba to use exactly the same mechanism that NT does. The 470 470 method either uses broadcast-based name resolution, performs a WINS database … … 473 473 </p><p> 474 474 To join the domain, run this command: 475 <a class="indexterm" name="id 2571500"></a>475 <a class="indexterm" name="id342214"></a> 476 476 </p><pre class="screen"> 477 477 <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> 478 478 </pre><p> 479 479 </p><p> 480 <a class="indexterm" name="id 2571534"></a>481 <a class="indexterm" name="id 2571541"></a>482 <a class="indexterm" name="id 2571547"></a>483 <a class="indexterm" name="id 2571554"></a>480 <a class="indexterm" name="id342246"></a> 481 <a class="indexterm" name="id342253"></a> 482 <a class="indexterm" name="id342260"></a> 483 <a class="indexterm" name="id342267"></a> 484 484 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 485 485 the NetBIOS name of the PDC will be obtained either using a WINS lookup or via NetBIOS broadcast based name 486 486 look up. 487 487 </p><p> 488 <a class="indexterm" name="id 2571577"></a>489 <a class="indexterm" name="id 2571584"></a>490 <a class="indexterm" name="id 2571590"></a>491 <a class="indexterm" name="id 2571597"></a>488 <a class="indexterm" name="id342288"></a> 489 <a class="indexterm" name="id342295"></a> 490 <a class="indexterm" name="id342301"></a> 491 <a class="indexterm" name="id342308"></a> 492 492 The machine is joining the domain DOM, and the PDC for that domain (the only machine 493 493 that has write access to the domain SAM database) is DOMPDC; therefore, use the <code class="option">-S</code> … … 500 500 </pre><p> 501 501 </p><p> 502 <a class="indexterm" name="id 2571634"></a>503 <a class="indexterm" name="id 2571645"></a>504 <a class="indexterm" name="id 2571652"></a>502 <a class="indexterm" name="id342340"></a> 503 <a class="indexterm" name="id342352"></a> 504 <a class="indexterm" name="id342358"></a> 505 505 Where Active Directory is used, the command used to join the ADS domain is: 506 506 </p><pre class="screen"> … … 515 515 administration</a> for further information. 516 516 </p><p> 517 <a class="indexterm" name="id 2571709"></a>518 <a class="indexterm" name="id 2571716"></a>519 <a class="indexterm" name="id 2571723"></a>517 <a class="indexterm" name="id342412"></a> 518 <a class="indexterm" name="id342418"></a> 519 <a class="indexterm" name="id342425"></a> 520 520 This process joins the server to the domain without separately having to create the machine 521 521 trust account on the PDC beforehand. 522 522 </p><p> 523 <a class="indexterm" name="id 2571735"></a>524 <a class="indexterm" name="id 2571745"></a>525 <a class="indexterm" name="id 2571752"></a>526 <a class="indexterm" name="id 2571759"></a>523 <a class="indexterm" name="id342436"></a> 524 <a class="indexterm" name="id342446"></a> 525 <a class="indexterm" name="id342453"></a> 526 <a class="indexterm" name="id342460"></a> 527 527 This command goes through the machine account password change protocol, then writes the new (random) machine 528 528 account password for this Samba server into a file in the same directory in which a smbpasswd file would be … … 530 530 <code class="filename">/usr/local/samba/private/secrets.tdb</code> or <code class="filename">/etc/samba/secrets.tdb</code>. 531 531 </p><p> 532 <a class="indexterm" name="id 2571788"></a>533 <a class="indexterm" name="id 2571795"></a>532 <a class="indexterm" name="id342484"></a> 533 <a class="indexterm" name="id342491"></a> 534 534 This file is created and owned by root and is not readable by any other user. It is 535 535 the key to the domain-level security for your system and should be treated as carefully 536 536 as a shadow password file. 537 537 </p><p> 538 <a class="indexterm" name="id 2571808"></a>539 <a class="indexterm" name="id 2571815"></a>540 <a class="indexterm" name="id 2571822"></a>538 <a class="indexterm" name="id342503"></a> 539 <a class="indexterm" name="id342510"></a> 540 <a class="indexterm" name="id342516"></a> 541 541 Finally, restart your Samba daemons and get ready for clients to begin using domain 542 542 security. The way you can restart your Samba daemons depends on your distribution, … … 545 545 <code class="prompt">root# </code>/etc/init.d/samba restart 546 546 </pre><p> 547 </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2571847"></a>Why Is This Better Than <em class="parameter"><code>security = server</code></em>?</h3></div></div></div><p>548 <a class="indexterm" name="id 2571861"></a>549 <a class="indexterm" name="id 2571868"></a>550 <a class="indexterm" name="id 2571875"></a>547 </p></div><div class="sect2" title="Why Is This Better Than security = server?"><div class="titlepage"><div><div><h3 class="title"><a name="id342539"></a>Why Is This Better Than <em class="parameter"><code>security = server</code></em>?</h3></div></div></div><p> 548 <a class="indexterm" name="id342552"></a> 549 <a class="indexterm" name="id342559"></a> 550 <a class="indexterm" name="id342566"></a> 551 551 Currently, domain security in Samba does not free you from having to create local UNIX users to represent the 552 552 users attaching to your server. This means that if domain user <code class="constant">DOM\fred</code> attaches to your … … 555 555 NT server in the same way as a Windows 95 or Windows 98 server would. 556 556 </p><p> 557 <a class="indexterm" name="id 2571909"></a>558 <a class="indexterm" name="id 2571915"></a>559 <a class="indexterm" name="id 2571922"></a>557 <a class="indexterm" name="id342596"></a> 558 <a class="indexterm" name="id342602"></a> 559 <a class="indexterm" name="id342609"></a> 560 560 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 561 561 to automatically assign UNIX UIDs and GIDs to Windows NT domain users and groups. 562 562 </p><p> 563 <a class="indexterm" name="id 2571941"></a>564 <a class="indexterm" name="id 2571948"></a>565 <a class="indexterm" name="id 2571955"></a>563 <a class="indexterm" name="id342627"></a> 564 <a class="indexterm" name="id342633"></a> 565 <a class="indexterm" name="id342640"></a> 566 566 The advantage of domain-level security is that the authentication in domain-level security is passed down the 567 567 authenticated RPC channel in exactly the same way that an NT server would do it. This means Samba servers now … … 570 570 domain PDC). 571 571 </p><p> 572 <a class="indexterm" name="id 2571973"></a>573 <a class="indexterm" name="id 2571979"></a>574 <a class="indexterm" name="id 2571986"></a>572 <a class="indexterm" name="id342654"></a> 573 <a class="indexterm" name="id342661"></a> 574 <a class="indexterm" name="id342667"></a> 575 575 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 576 576 keep a connection open to the authenticating server for as long as that daemon lasts. This can drain the … … 580 580 connection resources. 581 581 </p><p> 582 <a class="indexterm" name="id 2572026"></a>583 <a class="indexterm" name="id 2572032"></a>584 <a class="indexterm" name="id 2572039"></a>585 <a class="indexterm" name="id 2572046"></a>582 <a class="indexterm" name="id342702"></a> 583 <a class="indexterm" name="id342708"></a> 584 <a class="indexterm" name="id342715"></a> 585 <a class="indexterm" name="id342721"></a> 586 586 Finally, acting in the same manner as an NT server authenticating to a PDC means that as part of the 587 587 authentication reply, the Samba server gets the user identification information such as the user SID, the list 588 588 of NT groups the user belongs to, and so on. 589 </p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>589 </p><div class="note" title="Note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p> 590 590 Much of the text of this document was first published in the Web magazine 591 591 <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> 592 592 <span class="emphasis"><em>Doing the NIS/NT Samba</em></span>. 593 </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>594 <a class="indexterm" name="id 2572096"></a>595 <a class="indexterm" name="id 2572102"></a>596 <a class="indexterm" name="id 2572112"></a>597 <a class="indexterm" name="id 2572118"></a>593 </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> 594 <a class="indexterm" name="id342768"></a> 595 <a class="indexterm" name="id342774"></a> 596 <a class="indexterm" name="id342783"></a> 597 <a class="indexterm" name="id342790"></a> 598 598 This is a rough guide to setting up Samba-3 with Kerberos authentication against a 599 599 Windows 200x KDC. A familiarity with Kerberos is assumed. 600 </p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2572129"></a>Configure <code class="filename">smb.conf</code></h3></div></div></div><p>600 </p><div class="sect2" title="Configure smb.conf"><div class="titlepage"><div><div><h3 class="title"><a name="id342799"></a>Configure <code class="filename">smb.conf</code></h3></div></div></div><p> 601 601 You must use at least the following three options in <code class="filename">smb.conf</code>: 602 </p><table class="simplelist" border="0" summary="Simple list"><tr><td><a class="indexterm" name="id2572155"></a><em class="parameter"><code>realm = your.kerberos.REALM</code></em></td></tr><tr><td><a class="indexterm" name="id2572166"></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="id2572186"></a><em class="parameter"><code>encrypt passwords = yes</code></em></td></tr></table><p>603 <a class="indexterm" name="id 2572200"></a>604 <a class="indexterm" name="id 2572207"></a>605 <a class="indexterm" name="id 2572214"></a>606 <a class="indexterm" name="id 2572220"></a>607 <a class="indexterm" name="id 2572227"></a>602 </p><table border="0" summary="Simple list" class="simplelist"><tr><td><a class="indexterm" name="id342824"></a><em class="parameter"><code>realm = your.kerberos.REALM</code></em></td></tr><tr><td><a class="indexterm" name="id342836"></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="id342855"></a><em class="parameter"><code>encrypt passwords = yes</code></em></td></tr></table><p> 603 <a class="indexterm" name="id342869"></a> 604 <a class="indexterm" name="id342875"></a> 605 <a class="indexterm" name="id342882"></a> 606 <a class="indexterm" name="id342888"></a> 607 <a class="indexterm" name="id342895"></a> 608 608 In case samba cannot correctly identify the appropriate ADS server using the realm name, use the 609 609 <a class="link" href="smb.conf.5.html#PASSWORDSERVER" target="_top">password server</a> option in <code class="filename">smb.conf</code>: 610 </p><table class="simplelist" border="0" summary="Simple list"><tr><td><a class="indexterm" name="id2572258"></a><em class="parameter"><code>password server = your.kerberos.server</code></em></td></tr></table><p>610 </p><table border="0" summary="Simple list" class="simplelist"><tr><td><a class="indexterm" name="id342926"></a><em class="parameter"><code>password server = your.kerberos.server</code></em></td></tr></table><p> 611 611 The most common reason for which Samba may not be able to locate the ADS domain controller is a consequence of 612 612 sites maintaining some DNS servers on UNIX systems without regard for the DNS requirements of the ADS 613 613 infrastructure. There is no harm in specifying a preferred ADS domain controller using the <em class="parameter"><code>password 614 614 server</code></em>. 615 </p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>616 <a class="indexterm" name="id 2572285"></a>617 <a class="indexterm" name="id 2572292"></a>615 </p><div class="note" title="Note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p> 616 <a class="indexterm" name="id342950"></a> 617 <a class="indexterm" name="id342957"></a> 618 618 You do <span class="emphasis"><em>not</em></span> need an smbpasswd file, and older clients will be authenticated as 619 619 if <a class="link" href="smb.conf.5.html#SECURITY" target="_top">security = domain</a>, although it will not do any harm and 620 620 allows you to have local users not in the domain. 621 </p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2572320"></a>Configure <code class="filename">/etc/krb5.conf</code></h3></div></div></div><p>622 <a class="indexterm" name="id 2572332"></a>623 <a class="indexterm" name="id 2572338"></a>624 <a class="indexterm" name="id 2572348"></a>625 <a class="indexterm" name="id 2572355"></a>621 </p></div></div><div class="sect2" title="Configure /etc/krb5.conf"><div class="titlepage"><div><div><h3 class="title"><a name="id342981"></a>Configure <code class="filename">/etc/krb5.conf</code></h3></div></div></div><p> 622 <a class="indexterm" name="id342993"></a> 623 <a class="indexterm" name="id343000"></a> 624 <a class="indexterm" name="id343009"></a> 625 <a class="indexterm" name="id343016"></a> 626 626 With both MIT and Heimdal Kerberos, it is unnecessary to configure the <code class="filename">/etc/krb5.conf</code>, 627 627 and it may be detrimental. 628 628 </p><p> 629 <a class="indexterm" name="id 2572373"></a>630 <a class="indexterm" name="id 2572379"></a>631 <a class="indexterm" name="id 2572386"></a>632 <a class="indexterm" name="id 2572393"></a>633 <a class="indexterm" name="id 2572399"></a>629 <a class="indexterm" name="id343032"></a> 630 <a class="indexterm" name="id343039"></a> 631 <a class="indexterm" name="id343046"></a> 632 <a class="indexterm" name="id343053"></a> 633 <a class="indexterm" name="id343059"></a> 634 634 Microsoft ADS automatically create SRV records in the DNS zone 635 635 <em class="parameter"><code>_kerberos._tcp.REALM.NAME</code></em> for each KDC in the realm. This is part … … 638 638 active directory infrastructure. 639 639 </p><p> 640 <a class="indexterm" name="id 2572421"></a>641 <a class="indexterm" name="id 2572428"></a>642 <a class="indexterm" name="id 2572435"></a>643 <a class="indexterm" name="id 2572441"></a>644 <a class="indexterm" name="id 2572448"></a>645 <a class="indexterm" name="id 2572455"></a>640 <a class="indexterm" name="id343078"></a> 641 <a class="indexterm" name="id343085"></a> 642 <a class="indexterm" name="id343092"></a> 643 <a class="indexterm" name="id343098"></a> 644 <a class="indexterm" name="id343105"></a> 645 <a class="indexterm" name="id343112"></a> 646 646 UNIX systems can use kinit and the DES-CBC-MD5 or DES-CBC-CRC encryption types to authenticate to the Windows 647 647 2000 KDC. For further information regarding Windows 2000 ADS kerberos interoperability please refer to the … … 651 651 explains much of the magic behind the operation of Kerberos. 652 652 </p><p> 653 <a class="indexterm" name="id 2572487"></a>654 <a class="indexterm" name="id 2572493"></a>655 <a class="indexterm" name="id 2572500"></a>656 <a class="indexterm" name="id 2572507"></a>657 <a class="indexterm" name="id 2572514"></a>658 <a class="indexterm" name="id 2572520"></a>653 <a class="indexterm" name="id343138"></a> 654 <a class="indexterm" name="id343145"></a> 655 <a class="indexterm" name="id343152"></a> 656 <a class="indexterm" name="id343159"></a> 657 <a class="indexterm" name="id343165"></a> 658 <a class="indexterm" name="id343172"></a> 659 659 MIT's, as well as Heimdal's, recent KRB5 libraries default to checking for SRV records, so they will 660 660 automatically find the KDCs. In addition, <code class="filename">krb5.conf</code> only allows specifying … … 662 662 libraries to use whichever KDCs are available. 663 663 </p><p> 664 <a class="indexterm" name="id 2572542"></a>664 <a class="indexterm" name="id343191"></a> 665 665 When manually configuring <code class="filename">krb5.conf</code>, the minimal configuration is: 666 666 </p><pre class="screen"> … … 677 677 </pre><p> 678 678 </p><p> 679 <a class="indexterm" name="id 2572567"></a>679 <a class="indexterm" name="id343214"></a> 680 680 When using Heimdal versions before 0.6, use the following configuration settings: 681 681 </p><pre class="screen"> … … 694 694 </pre><p> 695 695 </p><p> 696 <a class="indexterm" name="id 2572589"></a>697 <a class="indexterm" name="id 2572596"></a>696 <a class="indexterm" name="id343233"></a> 697 <a class="indexterm" name="id343240"></a> 698 698 Test your config by doing a <strong class="userinput"><code>kinit 699 699 <em class="replaceable"><code>USERNAME</code></em>@<em class="replaceable"><code>REALM</code></em></code></strong> and 700 700 making sure that your password is accepted by the Win2000 KDC. 701 701 </p><p> 702 <a class="indexterm" name="id 2572619"></a>703 <a class="indexterm" name="id 2572626"></a>704 <a class="indexterm" name="id 2572633"></a>705 <a class="indexterm" name="id 2572639"></a>702 <a class="indexterm" name="id343262"></a> 703 <a class="indexterm" name="id343269"></a> 704 <a class="indexterm" name="id343276"></a> 705 <a class="indexterm" name="id343282"></a> 706 706 With Heimdal versions earlier than 0.6.x you can use only newly created accounts 707 707 in ADS or accounts that have had the password changed once after migration, or … … 710 710 (and no default etypes in krb5.conf). Unfortunately, this whole area is still 711 711 in a state of flux. 712 </p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>713 <a class="indexterm" name="id 2572661"></a>714 <a class="indexterm" name="id 2572668"></a>715 <a class="indexterm" name="id 2572674"></a>716 The realm must be in uppercase or you will get a “<span class="quote"><span class="errorname">Cannot find KDC for717 requested realm while getting initial credentials</span></span>” error (Kerberos712 </p><div class="note" title="Note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p> 713 <a class="indexterm" name="id343300"></a> 714 <a class="indexterm" name="id343307"></a> 715 <a class="indexterm" name="id343314"></a> 716 The realm must be in uppercase or you will get a <span class="quote">“<span class="quote"><span class="errorname">Cannot find KDC for 717 requested realm while getting initial credentials</span></span>”</span> error (Kerberos 718 718 is case-sensitive!). 719 </p></div><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>720 <a class="indexterm" name="id 2572692"></a>721 <a class="indexterm" name="id 2572698"></a>722 <a class="indexterm" name="id 2572705"></a>723 <a class="indexterm" name="id 2572712"></a>724 Time between the two servers must be synchronized. You will get a “<span class="quote"><span class="errorname">kinit(v5): Clock skew too725 great while getting initial credentials</span></span>” if the time difference (clock skew) is more than five minutes.719 </p></div><div class="note" title="Note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p> 720 <a class="indexterm" name="id343330"></a> 721 <a class="indexterm" name="id343337"></a> 722 <a class="indexterm" name="id343344"></a> 723 <a class="indexterm" name="id343351"></a> 724 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 too 725 great while getting initial credentials</span></span>”</span> if the time difference (clock skew) is more than five minutes. 726 726 </p></div><p> 727 <a class="indexterm" name="id 2572730"></a>728 <a class="indexterm" name="id 2572737"></a>727 <a class="indexterm" name="id343367"></a> 728 <a class="indexterm" name="id343374"></a> 729 729 Clock skew limits are configurable in the Kerberos protocols. The default setting is five minutes. 730 730 </p><p> 731 <a class="indexterm" name="id 2572749"></a>732 <a class="indexterm" name="id 2572755"></a>733 <a class="indexterm" name="id 2572762"></a>734 <a class="indexterm" name="id 2572769"></a>731 <a class="indexterm" name="id343385"></a> 732 <a class="indexterm" name="id343391"></a> 733 <a class="indexterm" name="id343398"></a> 734 <a class="indexterm" name="id343405"></a> 735 735 You also must ensure that you can do a reverse DNS lookup on the IP address of your KDC. Also, the name that 736 736 this reverse lookup maps to must either be the NetBIOS name of the KDC (i.e., the hostname with no domain 737 737 attached) or it can be the NetBIOS name followed by the realm. 738 738 </p><p> 739 <a class="indexterm" name="id 2572783"></a>740 <a class="indexterm" name="id 2572790"></a>741 <a class="indexterm" name="id 2572797"></a>739 <a class="indexterm" name="id343417"></a> 740 <a class="indexterm" name="id343424"></a> 741 <a class="indexterm" name="id343430"></a> 742 742 The easiest way to ensure you get this right is to add a <code class="filename">/etc/hosts</code> entry mapping the IP 743 743 address of your KDC to its NetBIOS name. If you do not get this correct, then you will get a <span class="errorname">local 744 744 error</span> when you try to join the realm. 745 745 </p><p> 746 <a class="indexterm" name="id 2572820"></a>747 <a class="indexterm" name="id 2572826"></a>748 <a class="indexterm" name="id 2572834"></a>749 <a class="indexterm" name="id 2572841"></a>746 <a class="indexterm" name="id343452"></a> 747 <a class="indexterm" name="id343459"></a> 748 <a class="indexterm" name="id343466"></a> 749 <a class="indexterm" name="id343472"></a> 750 750 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> 751 751 and <span class="application">winbindd</span>. 752 </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>753 <a class="indexterm" name="id 2572911"></a>754 <a class="indexterm" name="id 2572918"></a>755 <a class="indexterm" name="id 2572925"></a>756 <a class="indexterm" name="id 2572932"></a>752 </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> 753 <a class="indexterm" name="id343538"></a> 754 <a class="indexterm" name="id343544"></a> 755 <a class="indexterm" name="id343551"></a> 756 <a class="indexterm" name="id343558"></a> 757 757 As a user who has write permission on the Samba private directory (usually root), run: 758 758 </p><pre class="screen"> … … 763 763 On the UNIX/Linux system, this command must be executed by an account that has UID=0 (root). 764 764 </p><p> 765 <a class="indexterm" name="id 2572966"></a>766 <a class="indexterm" name="id 2572973"></a>767 <a class="indexterm" name="id 2572980"></a>768 <a class="indexterm" name="id 2572987"></a>769 <a class="indexterm" name="id 2572994"></a>770 <a class="indexterm" name="id 2573001"></a>765 <a class="indexterm" name="id343589"></a> 766 <a class="indexterm" name="id343595"></a> 767 <a class="indexterm" name="id343602"></a> 768 <a class="indexterm" name="id343609"></a> 769 <a class="indexterm" name="id343616"></a> 770 <a class="indexterm" name="id343622"></a> 771 771 When making a Windows client a member of an ADS domain within a complex organization, you 772 772 may want to create the machine trust account within a particular organizational unit. Samba-3 permits … … 778 778 Your ADS manager will be able to advise what should be specified for the "organizational_unit" parameter. 779 779 </p><p> 780 <a class="indexterm" name="id 2573051"></a>781 <a class="indexterm" name="id 2573058"></a>782 <a class="indexterm" name="id 2573065"></a>783 <a class="indexterm" name="id 2573072"></a>784 For example, you may want to create the machine trust account in a container called “<span class="quote">Servers</span>”785 under the organizational directory “<span class="quote">Computers/BusinessUnit/Department,</span>”like this:780 <a class="indexterm" name="id343669"></a> 781 <a class="indexterm" name="id343676"></a> 782 <a class="indexterm" name="id343682"></a> 783 <a class="indexterm" name="id343689"></a> 784 For example, you may want to create the machine trust account in a container called <span class="quote">“<span class="quote">Servers</span>”</span> 785 under the organizational directory <span class="quote">“<span class="quote">Computers/BusinessUnit/Department,</span>”</span> like this: 786 786 </p><pre class="screen"> 787 787 <code class="prompt">root# </code> <strong class="userinput"><code>net ads join "Computers/BusinessUnit/Department/Servers"</code></strong> … … 792 792 valid characters in an OU name and used as escapes for other characters. If you need a backslash in an OU 793 793 name, it may need to be quadrupled to pass through the shell escape and ldap escape. 794 </p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2573121"></a>Possible Errors</h4></div></div></div><p>794 </p><div class="sect3" title="Possible Errors"><div class="titlepage"><div><div><h4 class="title"><a name="id343732"></a>Possible Errors</h4></div></div></div><p> 795 795 </p><div class="variablelist"><dl><dt><span class="term"><span class="errorname">ADS support not compiled in</span></span></dt><dd><p> 796 <a class="indexterm" name="id 2573140"></a>797 <a class="indexterm" name="id 2573147"></a>798 <a class="indexterm" name="id 2573154"></a>796 <a class="indexterm" name="id343751"></a> 797 <a class="indexterm" name="id343758"></a> 798 <a class="indexterm" name="id343765"></a> 799 799 Samba must be reconfigured (remove config.cache) and recompiled (make clean all install) after the 800 800 Kerberos libraries and headers files are installed. 801 801 </p></dd><dt><span class="term"><span class="errorname">net ads join prompts for user name</span></span></dt><dd><p> 802 <a class="indexterm" name="id 2573174"></a>803 <a class="indexterm" name="id 2573180"></a>802 <a class="indexterm" name="id343783"></a> 803 <a class="indexterm" name="id343790"></a> 804 804 You need to login to the domain using <strong class="userinput"><code>kinit 805 805 <em class="replaceable"><code>USERNAME</code></em>@<em class="replaceable"><code>REALM</code></em></code></strong>. 806 806 <em class="replaceable"><code>USERNAME</code></em> must be a user who has rights to add a machine to the domain. 807 807 </p></dd><dt><span class="term">Unsupported encryption/or checksum types</span></dt><dd><p> 808 <a class="indexterm" name="id 2573214"></a>809 <a class="indexterm" name="id 2573220"></a>810 <a class="indexterm" name="id 2573228"></a>808 <a class="indexterm" name="id343822"></a> 809 <a class="indexterm" name="id343829"></a> 810 <a class="indexterm" name="id343836"></a> 811 811 Make sure that the <code class="filename">/etc/krb5.conf</code> is correctly configured 812 812 for the type and version of Kerberos installed on the system. 813 813 </p></dd></dl></div><p> 814 </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>815 <a class="indexterm" name="id 2573259"></a>816 <a class="indexterm" name="id 2573266"></a>817 <a class="indexterm" name="id 2573273"></a>814 </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> 815 <a class="indexterm" name="id343866"></a> 816 <a class="indexterm" name="id343872"></a> 817 <a class="indexterm" name="id343879"></a> 818 818 If the join was successful, you will see a new computer account with the 819 NetBIOS name of your Samba server in Active Directory (in the “<span class="quote">Computers</span>”819 NetBIOS name of your Samba server in Active Directory (in the <span class="quote">“<span class="quote">Computers</span>”</span> 820 820 folder under Users and Computers. 821 821 </p><p> 822 <a class="indexterm" name="id 2573289"></a>823 <a class="indexterm" name="id 2573296"></a>824 <a class="indexterm" name="id 2573305"></a>822 <a class="indexterm" name="id343894"></a> 823 <a class="indexterm" name="id343901"></a> 824 <a class="indexterm" name="id343910"></a> 825 825 On a Windows 2000 client, try <strong class="userinput"><code>net use * \\server\share</code></strong>. It should be possible 826 826 to login with Kerberos without needing to know a password. If this fails, then run 827 827 <strong class="userinput"><code>klist tickets</code></strong>. Did you get a ticket for the server? Does it have 828 828 an encryption type of DES-CBC-MD5? 829 </p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>830 <a class="indexterm" name="id 2573332"></a>831 <a class="indexterm" name="id 2573339"></a>832 <a class="indexterm" name="id 2573346"></a>829 </p><div class="note" title="Note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p> 830 <a class="indexterm" name="id343935"></a> 831 <a class="indexterm" name="id343942"></a> 832 <a class="indexterm" name="id343948"></a> 833 833 Samba can use both DES-CBC-MD5 encryption as well as ARCFOUR-HMAC-MD5 encoding. 834 </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>835 <a class="indexterm" name="id 2573373"></a>836 <a class="indexterm" name="id 2573380"></a>837 <a class="indexterm" name="id 2573386"></a>834 </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> 835 <a class="indexterm" name="id343974"></a> 836 <a class="indexterm" name="id343980"></a> 837 <a class="indexterm" name="id343987"></a> 838 838 On your Samba server try to login to a Windows 2000 server or your Samba 839 839 server using <span class="application">smbclient</span> and Kerberos. Use <span class="application">smbclient</span> as usual, but 840 840 specify the <code class="option">-k</code> option to choose Kerberos authentication. 841 </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2573414"></a>Notes</h3></div></div></div><p>842 <a class="indexterm" name="id 2573422"></a>843 <a class="indexterm" name="id 2573429"></a>844 <a class="indexterm" name="id 2573436"></a>841 </p></div><div class="sect2" title="Notes"><div class="titlepage"><div><div><h3 class="title"><a name="id344013"></a>Notes</h3></div></div></div><p> 842 <a class="indexterm" name="id344021"></a> 843 <a class="indexterm" name="id344028"></a> 844 <a class="indexterm" name="id344035"></a> 845 845 You must change the administrator password at least once after installing a domain controller, 846 846 to create the right encryption types. 847 847 </p><p> 848 <a class="indexterm" name="id 2573448"></a>849 <a class="indexterm" name="id 2573455"></a>850 <a class="indexterm" name="id 2573462"></a>848 <a class="indexterm" name="id344046"></a> 849 <a class="indexterm" name="id344053"></a> 850 <a class="indexterm" name="id344059"></a> 851 851 Windows 200x does not seem to create the <em class="parameter"><code>_kerberos._udp</code></em> and 852 852 <em class="parameter"><code>_ldap._tcp</code></em> in the default DNS setup. Perhaps this will be fixed later in service packs. 853 </p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2573486"></a>Sharing User ID Mappings between Samba Domain Members</h2></div></div></div><p>854 <a class="indexterm" name="id 2573495"></a>855 <a class="indexterm" name="id 2573502"></a>856 <a class="indexterm" name="id 2573508"></a>857 <a class="indexterm" name="id 2573515"></a>853 </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="id344082"></a>Sharing User ID Mappings between Samba Domain Members</h2></div></div></div><p> 854 <a class="indexterm" name="id344090"></a> 855 <a class="indexterm" name="id344097"></a> 856 <a class="indexterm" name="id344104"></a> 857 <a class="indexterm" name="id344110"></a> 858 858 Samba maps UNIX users and groups (identified by UIDs and GIDs) to Windows users and groups (identified by SIDs). 859 859 These mappings are done by the <em class="parameter"><code>idmap</code></em> subsystem of Samba. 860 860 </p><p> 861 <a class="indexterm" name="id 2573533"></a>862 <a class="indexterm" name="id 2573540"></a>863 <a class="indexterm" name="id 2573547"></a>861 <a class="indexterm" name="id344128"></a> 862 <a class="indexterm" name="id344134"></a> 863 <a class="indexterm" name="id344141"></a> 864 864 In some cases it is useful to share these mappings between Samba domain members, 865 865 so <span class="emphasis"><em>name->id</em></span> mapping is identical on all machines. 866 866 This may be needed in particular when sharing files over both CIFS and NFS. 867 867 </p><p> 868 <a class="indexterm" name="id 2573564"></a>869 <a class="indexterm" name="id 2573571"></a>868 <a class="indexterm" name="id344157"></a> 869 <a class="indexterm" name="id344163"></a> 870 870 To use the <span class="emphasis"><em>LDAP</em></span> <em class="parameter"><code>ldap idmap suffix</code></em>, set: 871 </p><table class="simplelist" border="0" summary="Simple list"><tr><td><a class="indexterm" name="id2573595"></a><em class="parameter"><code>ldap idmap suffix = ou=Idmap</code></em></td></tr></table><p>871 </p><table border="0" summary="Simple list" class="simplelist"><tr><td><a class="indexterm" name="id344186"></a><em class="parameter"><code>ldap idmap suffix = ou=Idmap</code></em></td></tr></table><p> 872 872 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> 873 873 parameter for further information. 874 874 </p><p> 875 <a class="indexterm" name="id 2573631"></a>876 <a class="indexterm" name="id 2573637"></a>877 <a class="indexterm" name="id 2573644"></a>875 <a class="indexterm" name="id344222"></a> 876 <a class="indexterm" name="id344228"></a> 877 <a class="indexterm" name="id344235"></a> 878 878 Do not forget to specify also the <a class="link" href="smb.conf.5.html#LDAPADMINDN" target="_top">ldap admin dn</a> 879 879 and to make certain to set the LDAP administrative password into the <code class="filename">secrets.tdb</code> using: … … 883 883 In place of <code class="literal">ldap-admin-password</code>, substitute the LDAP administration password for your 884 884 system. 885 </p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2573692"></a>Common Errors</h2></div></div></div><p>886 <a class="indexterm" name="id 2573700"></a>887 <a class="indexterm" name="id 2573707"></a>885 </p></div><div class="sect1" title="Common Errors"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id344280"></a>Common Errors</h2></div></div></div><p> 886 <a class="indexterm" name="id344287"></a> 887 <a class="indexterm" name="id344294"></a> 888 888 In the process of adding/deleting/re-adding domain member machine trust accounts, there are 889 many traps for the unwary player and many “<span class="quote">little</span>”things that can go wrong.889 many traps for the unwary player and many <span class="quote">“<span class="quote">little</span>”</span> things that can go wrong. 890 890 It is particularly interesting how often subscribers on the Samba mailing list have concluded 891 after repeated failed attempts to add a machine account that it is necessary to “<span class="quote">reinstall</span>”891 after repeated failed attempts to add a machine account that it is necessary to <span class="quote">“<span class="quote">reinstall</span>”</span> 892 892 MS Windows on the machine. In truth, it is seldom necessary to reinstall because of this type 893 893 of problem. The real solution is often quite simple, and with an understanding of how MS Windows 894 894 networking functions, it is easy to overcome. 895 </p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2573732"></a>Cannot Add Machine Back to Domain</h3></div></div></div><p>896 <a class="indexterm" name="id 2573740"></a>897 <a class="indexterm" name="id 2573748"></a>898 “<span class="quote">A Windows workstation was reinstalled. The original domain machine trust895 </p><div class="sect2" title="Cannot Add Machine Back to Domain"><div class="titlepage"><div><div><h3 class="title"><a name="id344314"></a>Cannot Add Machine Back to Domain</h3></div></div></div><p> 896 <a class="indexterm" name="id344322"></a> 897 <a class="indexterm" name="id344329"></a> 898 <span class="quote">“<span class="quote">A Windows workstation was reinstalled. The original domain machine trust 899 899 account was deleted and added immediately. The workstation will not join the domain if I use 900 900 the same machine name. Attempts to add the machine fail with a message that the machine already 901 exists on the network I know it does not. Why is this failing?</span>” 902 </p><p> 903 <a class="indexterm" name="id 2573769"></a>904 <a class="indexterm" name="id 2573775"></a>901 exists on the network I know it does not. Why is this failing?</span>”</span> 902 </p><p> 903 <a class="indexterm" name="id344348"></a> 904 <a class="indexterm" name="id344354"></a> 905 905 The original name is still in the NetBIOS name cache and must expire after machine account 906 906 deletion before adding that same name as a domain member again. The best advice is to delete … … 910 910 <code class="prompt">C:\> </code> nbtstat -R 911 911 </pre><p> 912 </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2573808"></a>Adding Machine to Domain Fails</h3></div></div></div><p>913 <a class="indexterm" name="id 2573816"></a>914 <a class="indexterm" name="id 2573822"></a>915 “<span class="quote">Adding a Windows 200x or XP Professional machine to the Samba PDC Domain fails with a912 </p></div><div class="sect2" title="Adding Machine to Domain Fails"><div class="titlepage"><div><div><h3 class="title"><a name="id344384"></a>Adding Machine to Domain Fails</h3></div></div></div><p> 913 <a class="indexterm" name="id344391"></a> 914 <a class="indexterm" name="id344398"></a> 915 <span class="quote">“<span class="quote">Adding a Windows 200x or XP Professional machine to the Samba PDC Domain fails with a 916 916 message that says, <span class="errorname">"The machine could not be added at this time, there is a network problem. 917 Please try again later."</span> Why?</span>” 918 </p><p> 919 <a class="indexterm" name="id 2573843"></a>917 Please try again later."</span> Why?</span>”</span> 918 </p><p> 919 <a class="indexterm" name="id344417"></a> 920 920 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> 921 921 file. If there is not, please add one that is appropriate for your OS platform. If a script … … 925 925 </p><p> 926 926 Possible causes include: 927 </p><div class="itemizedlist"><ul type="disc"><li><p>928 <a class="indexterm" name="id 2573901"></a>929 <a class="indexterm" name="id 2573908"></a>927 </p><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem"><p> 928 <a class="indexterm" name="id344470"></a> 929 <a class="indexterm" name="id344477"></a> 930 930 The script does not actually exist, or could not be located in the path specified. 931 931 </p><p> 932 <a class="indexterm" name="id 2573919"></a>933 <a class="indexterm" name="id 2573926"></a>932 <a class="indexterm" name="id344487"></a> 933 <a class="indexterm" name="id344493"></a> 934 934 <span class="emphasis"><em>Corrective action:</em></span> Fix it. Make sure when run manually 935 935 that the script will add both the UNIX system account and the Samba SAM account. 936 </p></li><li ><p>937 <a class="indexterm" name="id 2573943"></a>938 <a class="indexterm" name="id 2573950"></a>936 </p></li><li class="listitem"><p> 937 <a class="indexterm" name="id344509"></a> 938 <a class="indexterm" name="id344516"></a> 939 939 The machine could not be added to the UNIX system accounts file <code class="filename">/etc/passwd</code>. 940 940 </p><p> 941 <a class="indexterm" name="id 2573967"></a>942 <a class="indexterm" name="id 2573974"></a>941 <a class="indexterm" name="id344532"></a> 942 <a class="indexterm" name="id344539"></a> 943 943 <span class="emphasis"><em>Corrective action:</em></span> Check that the machine name is a legal UNIX 944 944 system account name. If the UNIX utility <code class="literal">useradd</code> is called, … … 947 947 nor will it allow spaces in the name. 948 948 </p></li></ul></div><p> 949 <a class="indexterm" name="id 2574006"></a>950 <a class="indexterm" name="id 2574012"></a>951 <a class="indexterm" name="id 2574019"></a>949 <a class="indexterm" name="id344568"></a> 950 <a class="indexterm" name="id344575"></a> 951 <a class="indexterm" name="id344582"></a> 952 952 The <a class="link" href="smb.conf.5.html#ADDMACHINESCRIPT" target="_top">add machine script</a> does not create the 953 953 machine account in the Samba backend database; it is there only to create a UNIX system 954 954 account to which the Samba backend database account can be mapped. 955 </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2574044"></a>I Can't Join a Windows 2003 PDC</h3></div></div></div><p>956 <a class="indexterm" name="id 2574052"></a>957 <a class="indexterm" name="id 2574058"></a>958 <a class="indexterm" name="id 2574065"></a>959 <a class="indexterm" name="id 2574072"></a>955 </p></div><div class="sect2" title="I Can't Join a Windows 2003 PDC"><div class="titlepage"><div><div><h3 class="title"><a name="id344604"></a>I Can't Join a Windows 2003 PDC</h3></div></div></div><p> 956 <a class="indexterm" name="id344612"></a> 957 <a class="indexterm" name="id344618"></a> 958 <a class="indexterm" name="id344625"></a> 959 <a class="indexterm" name="id344631"></a> 960 960 Windows 2003 requires SMB signing. Client-side SMB signing has been implemented in Samba-3.0. 961 961 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.
