- Timestamp:
- May 23, 2008, 6:56:41 AM (17 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
branches/samba-3.0/docs/htmldocs/Samba3-HOWTO/samba-pdc.html
r44 r134 1 <html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter 4. Domain Control</title><link rel="stylesheet" href=" samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.71.0"><link rel="start" href="index.html" title="The Official Samba-3 HOWTO and Reference Guide"><link rel="up" href="type.html" title="Part II. Server Configuration Basics"><link rel="prev" href="ServerType.html" title="Chapter 3. Server Types and Security Modes"><link rel="next" href="samba-bdc.html" title="Chapter 5. Backup Domain Control"></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 4. Domain Control</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="ServerType.html">Prev</a> </td><th width="60%" align="center">Part II. Server Configuration Basics</th><td width="20%" align="right"> <a accesskey="n" href="samba-bdc.html">Next</a></td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="samba-pdc"></a>Chapter 4. Domain Control</h2></div><div><div class="author"><h3 class="author"><span class="firstname">John</span> <span class="othername">H.</span> <span class="surname">Terpstra</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><code class="email"><<a href="mailto:jht@samba.org">jht@samba.org</a>></code></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">Gerald</span> <span class="othername">(Jerry)</span> <span class="surname">Carter</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><code class="email"><<a href="mailto:jerry@samba.org">jerry@samba.org</a>></code></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">David</span> <span class="surname">Bannon</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><code class="email"><<a href="mailto:dbannon@samba.org">dbannon@samba.org</a>></code></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">Guenther</span> <span class="surname">Deschner</span></h3><span class="contrib">LDAP updates</span><div class="affiliation"><span class="orgname">SuSE<br></span><div class="address"><p><code class="email"><<a href="mailto:gd@suse.de">gd@suse.de</a>></code></p></div></div></div></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="samba-pdc.html#id327668">Features and Benefits</a></span></dt><dt><span class="sect1"><a href="samba-pdc.html#id328244">Single Sign-On and Domain Security</a></span></dt><dt><span class="sect1"><a href="samba-pdc.html#id328748">Basics of Domain Control</a></span></dt><dd><dl><dt><span class="sect2"><a href="samba-pdc.html#id328766">Domain Controller Types</a></span></dt><dt><span class="sect2"><a href="samba-pdc.html#id329223">Preparing for Domain Control</a></span></dt></dl></dd><dt><span class="sect1"><a href="samba-pdc.html#id329677">Domain Control: Example Configuration</a></span></dt><dt><span class="sect1"><a href="samba-pdc.html#id330430">Samba ADS Domain Control</a></span></dt><dt><span class="sect1"><a href="samba-pdc.html#id330473">Domain and Network Logon Configuration</a></span></dt><dd><dl><dt><span class="sect2"><a href="samba-pdc.html#id330490">Domain Network Logon Service</a></span></dt><dt><span class="sect2"><a href="samba-pdc.html#id331027">Security Mode and Master Browsers</a></span></dt></dl></dd><dt><span class="sect1"><a href="samba-pdc.html#id331242">Common Errors</a></span></dt><dd><dl><dt><span class="sect2"><a href="samba-pdc.html#id331248">“<span class="quote">$</span>” Cannot Be Included in Machine Name</a></span></dt><dt><span class="sect2"><a href="samba-pdc.html#id331343">Joining Domain Fails Because of Existing Machine Account</a></span></dt><dt><span class="sect2"><a href="samba-pdc.html#id331401">The System Cannot Log You On (C000019B)</a></span></dt><dt><span class="sect2"><a href="samba-pdc.html#id331468">The Machine Trust Account Is Not Accessible</a></span></dt><dt><span class="sect2"><a href="samba-pdc.html#id331569">Account Disabled</a></span></dt><dt><span class="sect2"><a href="samba-pdc.html#id331595">Domain Controller Unavailable</a></span></dt><dt><span class="sect2"><a href="samba-pdc.html#id331611">Cannot Log onto Domain Member Workstation After Joining Domain</a></span></dt></dl></dd></dl></div><p>1 <html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter 4. Domain Control</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.73.2"><link rel="start" href="index.html" title="The Official Samba 3.2.x HOWTO and Reference Guide"><link rel="up" href="type.html" title="Part II. Server Configuration Basics"><link rel="prev" href="ServerType.html" title="Chapter 3. Server Types and Security Modes"><link rel="next" href="samba-bdc.html" title="Chapter 5. Backup Domain Control"></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 4. Domain Control</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="ServerType.html">Prev</a> </td><th width="60%" align="center">Part II. Server Configuration Basics</th><td width="20%" align="right"> <a accesskey="n" href="samba-bdc.html">Next</a></td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="samba-pdc"></a>Chapter 4. Domain Control</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">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">David</span> <span class="surname">Bannon</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><code class="email"><<a class="email" href="mailto:dbannon@samba.org">dbannon@samba.org</a>></code></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">Guenther</span> <span class="surname">Deschner</span></h3><span class="contrib">LDAP updates</span> <div class="affiliation"><span class="orgname">SuSE<br></span><div class="address"><p><code class="email"><<a class="email" href="mailto:gd@suse.de">gd@suse.de</a>></code></p></div></div></div></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="samba-pdc.html#id350366">Features and Benefits</a></span></dt><dt><span class="sect1"><a href="samba-pdc.html#id350899">Single Sign-On and Domain Security</a></span></dt><dt><span class="sect1"><a href="samba-pdc.html#id351396">Basics of Domain Control</a></span></dt><dd><dl><dt><span class="sect2"><a href="samba-pdc.html#id351413">Domain Controller Types</a></span></dt><dt><span class="sect2"><a href="samba-pdc.html#id351870">Preparing for Domain Control</a></span></dt></dl></dd><dt><span class="sect1"><a href="samba-pdc.html#id352336">Domain Control: Example Configuration</a></span></dt><dt><span class="sect1"><a href="samba-pdc.html#id353048">Samba ADS Domain Control</a></span></dt><dt><span class="sect1"><a href="samba-pdc.html#id353096">Domain and Network Logon Configuration</a></span></dt><dd><dl><dt><span class="sect2"><a href="samba-pdc.html#id353114">Domain Network Logon Service</a></span></dt><dt><span class="sect2"><a href="samba-pdc.html#id353648">Security Mode and Master Browsers</a></span></dt></dl></dd><dt><span class="sect1"><a href="samba-pdc.html#id353878">Common Errors</a></span></dt><dd><dl><dt><span class="sect2"><a href="samba-pdc.html#id353884">“<span class="quote">$</span>” Cannot Be Included in Machine Name</a></span></dt><dt><span class="sect2"><a href="samba-pdc.html#id353978">Joining Domain Fails Because of Existing Machine Account</a></span></dt><dt><span class="sect2"><a href="samba-pdc.html#id354037">The System Cannot Log You On (C000019B)</a></span></dt><dt><span class="sect2"><a href="samba-pdc.html#id354104">The Machine Trust Account Is Not Accessible</a></span></dt><dt><span class="sect2"><a href="samba-pdc.html#id354209">Account Disabled</a></span></dt><dt><span class="sect2"><a href="samba-pdc.html#id354234">Domain Controller Unavailable</a></span></dt><dt><span class="sect2"><a href="samba-pdc.html#id354251">Cannot Log onto Domain Member Workstation After Joining Domain</a></span></dt></dl></dd></dl></div><p> 2 2 There are many who approach MS Windows networking with incredible misconceptions. 3 3 That's okay, because it gives the rest of us plenty of opportunity to be of assistance. … … 5 5 that is already available. 6 6 </p><p> 7 <a class="indexterm" name="id3 27547"></a>7 <a class="indexterm" name="id350254"></a> 8 8 You are advised not to tackle this section without having first understood 9 9 and mastered some basics. MS Windows networking is not particularly forgiving of … … 13 13 that in some magical way is expected to solve all network operational ills. 14 14 </p><p> 15 <a href="samba-pdc.html#domain-example" title="Figure 4.1. An Example Domain.">The Example Domain Illustration</a> shows a typical MS Windows domain security15 <a class="link" href="samba-pdc.html#domain-example" title="Figure 4.1. An Example Domain.">The Example Domain Illustration</a> shows a typical MS Windows domain security 16 16 network environment. Workstations A, B, and C are representative of many physical MS Windows 17 17 network clients. … … 33 33 make mistakes, then please do it on a test network, away from users, and in such a way as 34 34 to not inflict pain on others. Do your learning on a test network. 35 </p><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id3 27668"></a>Features and Benefits</h2></div></div></div><p>36 <a class="indexterm" name="id3 27676"></a>35 </p><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id350366"></a>Features and Benefits</h2></div></div></div><p> 36 <a class="indexterm" name="id350374"></a> 37 37 <span class="emphasis"><em>What is the key benefit of Microsoft Domain Security?</em></span> 38 38 </p><p> 39 <a class="indexterm" name="id3 27690"></a>40 <a class="indexterm" name="id3 27698"></a>41 <a class="indexterm" name="id3 27705"></a>42 <a class="indexterm" name="id3 27712"></a>39 <a class="indexterm" name="id350386"></a> 40 <a class="indexterm" name="id350395"></a> 41 <a class="indexterm" name="id350401"></a> 42 <a class="indexterm" name="id350407"></a> 43 43 In a word, <span class="emphasis"><em>single sign-on</em></span>, or SSO for short. To many, this is the Holy Grail of MS 44 44 Windows NT and beyond networking. SSO allows users in a well-designed network to log onto any workstation that … … 48 48 feature of the domain security protocols. 49 49 </p><p> 50 <a class="indexterm" name="id3 27735"></a>51 <a class="indexterm" name="id3 27742"></a>52 <a class="indexterm" name="id3 27748"></a>53 <a class="indexterm" name="id3 27757"></a>54 <a class="indexterm" name="id3 27766"></a>50 <a class="indexterm" name="id350429"></a> 51 <a class="indexterm" name="id350435"></a> 52 <a class="indexterm" name="id350441"></a> 53 <a class="indexterm" name="id350450"></a> 54 <a class="indexterm" name="id350458"></a> 55 55 The benefits of domain security are available to those sites that deploy a Samba PDC. A domain provides a 56 56 unique network security identifier (SID). Domain user and group security identifiers are comprised of the … … 59 59 organizational access control. UNIX systems recognize only local security identifiers. 60 60 </p><p> 61 <a class="indexterm" name="id3 27780"></a>61 <a class="indexterm" name="id350472"></a> 62 62 A SID represents a security context. For example, every Windows machine has local accounts within the security 63 63 context of the local machine which has a unique SID. Every domain (NT4, ADS, Samba) contains accounts that 64 64 exist within the domain security context which is defined by the domain SID. 65 65 </p><p> 66 <a class="indexterm" name="id3 27793"></a>67 <a class="indexterm" name="id3 27799"></a>66 <a class="indexterm" name="id350484"></a> 67 <a class="indexterm" name="id350490"></a> 68 68 A domain member server will have a SID that differs from the domain SID. The domain member server can be 69 69 configured to regard all domain users as local users. It can also be configured to recognize domain users and … … 83 83 The result is that every account in the Windows networking world has a globally unique security identifier. 84 84 </p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p> 85 <a class="indexterm" name="id3 27837"></a>86 <a class="indexterm" name="id3 27846"></a>87 <a class="indexterm" name="id3 27853"></a>85 <a class="indexterm" name="id350526"></a> 86 <a class="indexterm" name="id350534"></a> 87 <a class="indexterm" name="id350540"></a> 88 88 Network clients of an MS Windows domain security environment must be domain members to be able to gain access 89 89 to the advanced features provided. Domain membership involves more than just setting the workgroup name to the 90 90 domain name. It requires the creation of a domain trust account for the workstation (called a machine 91 account). Refer to <a href="domain-member.html" title="Chapter 6. Domain Membership">Domain Membership</a> for more information.91 account). Refer to <a class="link" href="domain-member.html" title="Chapter 6. Domain Membership">Domain Membership</a> for more information. 92 92 </p></div><p> 93 93 The following functionalities are new to the Samba-3 release: 94 94 </p><div class="itemizedlist"><ul type="disc"><li><p> 95 <a class="indexterm" name="id3 27882"></a>95 <a class="indexterm" name="id350567"></a> 96 96 Samba-3 supports the use of a choice of backends that may be used in which user, group and machine 97 97 accounts may be stored. Multiple passwd backends can be used in combination, either as additive backend 98 98 data sets, or as fail-over data sets. 99 99 </p><p> 100 <a class="indexterm" name="id3 27897"></a>101 <a class="indexterm" name="id3 27904"></a>102 <a class="indexterm" name="id3 27910"></a>103 <a class="indexterm" name="id3 27917"></a>104 <a class="indexterm" name="id3 27924"></a>100 <a class="indexterm" name="id350581"></a> 101 <a class="indexterm" name="id350587"></a> 102 <a class="indexterm" name="id350593"></a> 103 <a class="indexterm" name="id350600"></a> 104 <a class="indexterm" name="id350606"></a> 105 105 An LDAP passdb backend confers the benefit that the account backend can be distributed and replicated, 106 106 which is of great value because it confers scalability and provides a high degree of reliability. 107 107 </p></li><li><p> 108 <a class="indexterm" name="id3 27937"></a>109 <a class="indexterm" name="id3 27949"></a>110 <a class="indexterm" name="id3 27958"></a>108 <a class="indexterm" name="id350618"></a> 109 <a class="indexterm" name="id350629"></a> 110 <a class="indexterm" name="id350637"></a> 111 111 Windows NT4 domain trusts. Samba-3 supports workstation and server (machine) trust accounts. It also 112 112 supports Windows NT4 style interdomain trust accounts, which further assists in network scalability 113 113 and interoperability. 114 114 </p></li><li><p> 115 <a class="indexterm" name="id3 27971"></a>116 <a class="indexterm" name="id3 27978"></a>117 <a class="indexterm" name="id3 27984"></a>118 <a class="indexterm" name="id3 27991"></a>119 <a class="indexterm" name="id3 28000"></a>120 <a class="indexterm" name="id3 28010"></a>115 <a class="indexterm" name="id350650"></a> 116 <a class="indexterm" name="id350656"></a> 117 <a class="indexterm" name="id350662"></a> 118 <a class="indexterm" name="id350668"></a> 119 <a class="indexterm" name="id350677"></a> 120 <a class="indexterm" name="id350685"></a> 121 121 Operation without NetBIOS over TCP/IP, rather using the raw SMB over TCP/IP. Note, this is feasible 122 122 only when operating as a Microsoft active directory domain member server. When acting as a Samba domain 123 123 controller the use of NetBIOS is necessary to provide network browsing support. 124 124 </p></li><li><p> 125 <a class="indexterm" name="id3 28026"></a>126 <a class="indexterm" name="id3 28032"></a>127 <a class="indexterm" name="id3 28039"></a>125 <a class="indexterm" name="id350700"></a> 126 <a class="indexterm" name="id350707"></a> 127 <a class="indexterm" name="id350713"></a> 128 128 Samba-3 provides NetBIOS name services (WINS), NetBIOS over TCP/IP (TCP port 139) session services, SMB over 129 129 TCP/IP (TCP port 445) session services, and Microsoft compatible ONC DCE RPC services (TCP port 135) 130 130 services. 131 131 </p></li><li><p> 132 <a class="indexterm" name="id3 28052"></a>132 <a class="indexterm" name="id350726"></a> 133 133 Management of users and groups via the User Manager for Domains. This can be done on any MS Windows client 134 134 using the <code class="filename">Nexus.exe</code> toolkit for Windows 9x/Me, or using the SRVTOOLS.EXE package for MS … … 140 140 The following functionalities are not provided by Samba-3: 141 141 </p><div class="itemizedlist"><ul type="disc"><li><p> 142 <a class="indexterm" name="id3 28085"></a>143 <a class="indexterm" name="id3 28092"></a>142 <a class="indexterm" name="id350757"></a> 143 <a class="indexterm" name="id350763"></a> 144 144 SAM replication with Windows NT4 domain controllers (i.e., a Samba PDC and a Windows NT BDC, or vice versa). 145 145 This means Samba cannot operate as a BDC when the PDC is Microsoft-based Windows NT PDC. Samba-3 can not 146 146 participate in replication of account data to Windows PDCs and BDCs. 147 147 </p></li><li><p> 148 <a class="indexterm" name="id3 28105"></a>149 <a class="indexterm" name="id3 28112"></a>148 <a class="indexterm" name="id350776"></a> 149 <a class="indexterm" name="id350783"></a> 150 150 Acting as a Windows 2000 active directory domain controller (i.e., Kerberos and Active Directory). In point of 151 151 fact, Samba-3 does have some Active Directory domain control ability that is at this time purely experimental. … … 154 154 support during the Samba-3 series life-cycle. 155 155 </p></li><li><p> 156 <a class="indexterm" name="id3 28131"></a>157 <a class="indexterm" name="id3 28138"></a>158 <a class="indexterm" name="id3 28144"></a>156 <a class="indexterm" name="id350797"></a> 157 <a class="indexterm" name="id350804"></a> 158 <a class="indexterm" name="id350810"></a> 159 159 The Windows 200x/XP Microsoft Management Console (MMC) cannot be used to manage a Samba-3 server. For this you 160 160 can use only the MS Windows NT4 Domain Server Manager and the MS Windows NT4 Domain User Manager. Both are 161 161 part of the SVRTOOLS.EXE package mentioned later. 162 162 </p></li></ul></div><p> 163 <a class="indexterm" name="id3 28160"></a>164 <a class="indexterm" name="id3 28167"></a>163 <a class="indexterm" name="id350825"></a> 164 <a class="indexterm" name="id350831"></a> 165 165 Windows 9x/Me/XP Home clients are not true members of a domain for reasons outlined in this chapter. The 166 166 protocol for support of Windows 9x/Me-style network (domain) logons is completely different from NT4/Windows … … 168 168 network logon facilities that are supported in Samba since approximately the Samba-1.9.15 series. 169 169 </p><p> 170 <a class="indexterm" name="id3 28180"></a>170 <a class="indexterm" name="id350844"></a> 171 171 Samba-3 implements group mapping between Windows NT groups and UNIX groups (this is really quite complicated 172 to explain in a short space). This is discussed more fully in <a href="groupmapping.html" title="Chapter 12. Group Mapping: MS Windows and UNIX">Group Mapping: MS172 to explain in a short space). This is discussed more fully in <a class="link" href="groupmapping.html" title="Chapter 12. Group Mapping: MS Windows and UNIX">Group Mapping: MS 173 173 Windows and UNIX</a>. 174 174 </p><p> 175 <a class="indexterm" name="id3 28202"></a>176 <a class="indexterm" name="id3 28208"></a>177 <a class="indexterm" name="id3 28217"></a>175 <a class="indexterm" name="id350863"></a> 176 <a class="indexterm" name="id350869"></a> 177 <a class="indexterm" name="id350877"></a> 178 178 Samba-3, like an MS Windows NT4 PDC or a Windows 200x Active Directory, needs to store user and Machine Trust 179 Account information in a suitable backend data-store. Refer to <a href="domain-member.html#machine-trust-accounts" title="MS Windows Workstation/Server Machine Trust Accounts">MS179 Account information in a suitable backend data-store. Refer to <a class="link" href="domain-member.html#machine-trust-accounts" title="MS Windows Workstation/Server Machine Trust Accounts">MS 180 180 Windows Workstation/Server Machine Trust Accounts</a>. With Samba-3 there can be multiple backends for 181 this. A complete discussion of account database backends can be found in <a href="passdb.html" title="Chapter 11. Account Information Databases">Account181 this. A complete discussion of account database backends can be found in <a class="link" href="passdb.html" title="Chapter 11. Account Information Databases">Account 182 182 Information Databases</a>. 183 </p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id3 28244"></a>Single Sign-On and Domain Security</h2></div></div></div><p>184 <a class="indexterm" name="id3 28252"></a>185 <a class="indexterm" name="id3 28260"></a>186 <a class="indexterm" name="id3 28267"></a>187 <a class="indexterm" name="id3 28274"></a>188 <a class="indexterm" name="id3 28280"></a>189 <a class="indexterm" name="id3 28287"></a>190 <a class="indexterm" name="id3 28294"></a>183 </p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id350899"></a>Single Sign-On and Domain Security</h2></div></div></div><p> 184 <a class="indexterm" name="id350906"></a> 185 <a class="indexterm" name="id350915"></a> 186 <a class="indexterm" name="id350921"></a> 187 <a class="indexterm" name="id350927"></a> 188 <a class="indexterm" name="id350934"></a> 189 <a class="indexterm" name="id350940"></a> 190 <a class="indexterm" name="id350946"></a> 191 191 When network administrators are asked to describe the benefits of Windows NT4 and active directory networking 192 192 the most often mentioned feature is that of single sign-on (SSO). Many companies have implemented SSO … … 198 198 uniqueness and history limits are applied. 199 199 </p><p> 200 <a class="indexterm" name="id3 28311"></a>200 <a class="indexterm" name="id350962"></a> 201 201 There is a broadly held perception that SSO is the answer to the problem of users having to deal with too many 202 202 information system access credentials (username/password pairs). Many elaborate schemes have been devised to … … 205 205 many SSO solutions are an administrative nightmare. 206 206 </p><p> 207 <a class="indexterm" name="id3 28325"></a>208 <a class="indexterm" name="id3 28332"></a>209 <a class="indexterm" name="id3 28339"></a>207 <a class="indexterm" name="id350976"></a> 208 <a class="indexterm" name="id350982"></a> 209 <a class="indexterm" name="id350989"></a> 210 210 SSO implementations utilize centralization of all user account information. Depending on environmental 211 211 complexity and the age of the systems over which a SSO solution is implemented, it may not be possible to … … 216 216 Ideally, the implementation of SSO should reduce complexity and reduce administative overheads. 217 217 </p><p> 218 <a class="indexterm" name="id3 28355"></a>219 <a class="indexterm" name="id3 28362"></a>220 <a class="indexterm" name="id3 28371"></a>221 <a class="indexterm" name="id3 28380"></a>222 <a class="indexterm" name="id3 28387"></a>218 <a class="indexterm" name="id351004"></a> 219 <a class="indexterm" name="id351011"></a> 220 <a class="indexterm" name="id351019"></a> 221 <a class="indexterm" name="id351028"></a> 222 <a class="indexterm" name="id351034"></a> 223 223 The initial goal of many network administrators is often to create and use a centralized identity management 224 224 system. It is often assumed that such a centralized system will use a single authentication infrastructure … … 233 233 and access control were designed and built. 234 234 </p><p> 235 <a class="indexterm" name="id3 28406"></a>236 <a class="indexterm" name="id3 28413"></a>237 <a class="indexterm" name="id3 28420"></a>238 <a class="indexterm" name="id3 28427"></a>239 <a class="indexterm" name="id3 28434"></a>240 <a class="indexterm" name="id3 28441"></a>241 <a class="indexterm" name="id3 28447"></a>242 <a class="indexterm" name="id3 28454"></a>235 <a class="indexterm" name="id351062"></a> 236 <a class="indexterm" name="id351068"></a> 237 <a class="indexterm" name="id351075"></a> 238 <a class="indexterm" name="id351081"></a> 239 <a class="indexterm" name="id351087"></a> 240 <a class="indexterm" name="id351094"></a> 241 <a class="indexterm" name="id351100"></a> 242 <a class="indexterm" name="id351106"></a> 243 243 Over the past decade an industry has been developed around the various methods that have been built to get 244 244 around the key limitations of legacy information technology systems. One approach that is often used involves … … 249 249 credentials. 250 250 </p><p> 251 <a class="indexterm" name="id3 28476"></a>252 <a class="indexterm" name="id3 28485"></a>253 <a class="indexterm" name="id3 28494"></a>254 <a class="indexterm" name="id3 28504"></a>251 <a class="indexterm" name="id351121"></a> 252 <a class="indexterm" name="id351130"></a> 253 <a class="indexterm" name="id351139"></a> 254 <a class="indexterm" name="id351147"></a> 255 255 The Organization for the Advancement of Structured Information Standards (OASIS) has developed the Security 256 256 Assertion Markup Language (SAML), a structured method for communication of authentication information. The … … 259 259 authenticate their respective users and vouch for secure access to the services each provides. 260 260 </p><p> 261 <a class="indexterm" name="id3 28518"></a>262 <a class="indexterm" name="id3 28527"></a>263 <a class="indexterm" name="id3 28534"></a>264 <a class="indexterm" name="id3 28541"></a>265 <a class="indexterm" name="id3 28548"></a>266 <a class="indexterm" name="id3 28553"></a>261 <a class="indexterm" name="id351161"></a> 262 <a class="indexterm" name="id351169"></a> 263 <a class="indexterm" name="id351176"></a> 264 <a class="indexterm" name="id351182"></a> 265 <a class="indexterm" name="id351188"></a> 266 <a class="indexterm" name="id351194"></a> 267 267 SAML documents can be wrapped in a Simple Object Access Protocol (SOAP) message for the computer-to-computer 268 268 communications needed for Web services. Or they may be passed between Web servers of federated organizations … … 274 274 interfaces. In a nust-shell, that is why FIM is a big and growing industry. 275 275 </p><p> 276 <a class="indexterm" name="id3 28569"></a>277 <a class="indexterm" name="id3 28576"></a>278 <a class="indexterm" name="id3 28582"></a>279 <a class="indexterm" name="id3 28589"></a>280 <a class="indexterm" name="id3 28596"></a>276 <a class="indexterm" name="id351216"></a> 277 <a class="indexterm" name="id351223"></a> 278 <a class="indexterm" name="id351230"></a> 279 <a class="indexterm" name="id351237"></a> 280 <a class="indexterm" name="id351243"></a> 281 281 Ignoring the bigger picture, which is beyond the scope of this book, the migration of all user and group 282 282 management to a centralized system is a step in the right direction. It is essential for interoperability … … 287 287 programming interface (GSSAPI) services. 288 288 </p><p> 289 <a class="indexterm" name="id3 28614"></a>290 <a class="indexterm" name="id3 28621"></a>291 <a class="indexterm" name="id3 28628"></a>289 <a class="indexterm" name="id351262"></a> 290 <a class="indexterm" name="id351269"></a> 291 <a class="indexterm" name="id351275"></a> 292 292 A growing number of companies provide authentication agents for disparate legacy platforms to permit the use 293 293 of LDAP systems. Thus the use of OpenLDAP, the dominant open source software implementation of the light … … 295 295 LDAP and Microsoft ADS make Samba a highly scalable and forward reaching organizational networking technology. 296 296 </p><p> 297 <a class="indexterm" name="id3 28641"></a>298 <a class="indexterm" name="id3 28648"></a>299 <a class="indexterm" name="id3 28655"></a>300 <a class="indexterm" name="id3 28662"></a>301 <a class="indexterm" name="id3 28668"></a>302 <a class="indexterm" name="id3 28675"></a>297 <a class="indexterm" name="id351289"></a> 298 <a class="indexterm" name="id351296"></a> 299 <a class="indexterm" name="id351302"></a> 300 <a class="indexterm" name="id351309"></a> 301 <a class="indexterm" name="id351316"></a> 302 <a class="indexterm" name="id351323"></a> 303 303 Microsoft ADS provides purely proprietary services that, with limitation, can be extended to provide a 304 304 centralized authentication infrastructure. Samba plus LDAP provides a similar opportunity for extension of a … … 308 308 sustainable choice and competition in the FIM market place. 309 309 </p><p> 310 <a class="indexterm" name="id3 28696"></a>311 <a class="indexterm" name="id3 28703"></a>312 <a class="indexterm" name="id3 28709"></a>310 <a class="indexterm" name="id351343"></a> 311 <a class="indexterm" name="id351350"></a> 312 <a class="indexterm" name="id351357"></a> 313 313 Primary domain control, if it is to be scalable to meet the needs of large sites, must therefore be capable of 314 314 using LDAP. The rapid adoption of OpenLDAP, and Samba configurations that use it, is ample proof that the era 315 of the directo y has started. Samba-3 does not demand the use of LDAP, but the demand for a mechanism by which315 of the directory has started. Samba-3 does not demand the use of LDAP, but the demand for a mechanism by which 316 316 user and group identity information can be distributed makes it an an unavoidable option. 317 317 </p><p> 318 <a class="indexterm" name="id3 28723"></a>319 <a class="indexterm" name="id3 28730"></a>320 <a class="indexterm" name="id3 28736"></a>318 <a class="indexterm" name="id351371"></a> 319 <a class="indexterm" name="id351377"></a> 320 <a class="indexterm" name="id351384"></a> 321 321 At this time, the use of Samba based BDCs, necessitates the use of LDAP. The most commonly used LDAP 322 322 implementation used by Samba sites is OpenLDAP. It is possible to use any standards compliant LDAP server. 323 323 Those known to work includes those manufactured by: IBM, CA, Novell (e-Directory), and others. 324 </p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id3 28748"></a>Basics of Domain Control</h2></div></div></div><p>325 <a class="indexterm" name="id3 28756"></a>324 </p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id351396"></a>Basics of Domain Control</h2></div></div></div><p> 325 <a class="indexterm" name="id351403"></a> 326 326 Over the years, public perceptions of what domain control really is has taken on an almost mystical nature. 327 327 Before we branch into a brief overview of domain control, there are three basic types of domain controllers. 328 </p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id3 28766"></a>Domain Controller Types</h3></div></div></div><div class="itemizedlist"><ul type="disc"><li><p>NT4 style Primary Domain Controller</p></li><li><p>NT4 style Backup Domain Controller</p></li><li><p>ADS Domain Controller</p></li></ul></div><p>329 <a class="indexterm" name="id3 28790"></a>330 <a class="indexterm" name="id3 28797"></a>331 <a class="indexterm" name="id3 28804"></a>332 <a class="indexterm" name="id3 28813"></a>328 </p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id351413"></a>Domain Controller Types</h3></div></div></div><div class="itemizedlist"><ul type="disc"><li><p>NT4 style Primary Domain Controller</p></li><li><p>NT4 style Backup Domain Controller</p></li><li><p>ADS Domain Controller</p></li></ul></div><p> 329 <a class="indexterm" name="id351438"></a> 330 <a class="indexterm" name="id351445"></a> 331 <a class="indexterm" name="id351451"></a> 332 <a class="indexterm" name="id351461"></a> 333 333 The <span class="emphasis"><em>Primary Domain Controller</em></span> or PDC plays an important role in MS Windows NT4. In 334 334 Windows 200x domain control architecture, this role is held by domain controllers. Folklore dictates that … … 338 338 (domain member) servers than in the domain controllers. 339 339 </p><p> 340 <a class="indexterm" name="id3 28836"></a>341 <a class="indexterm" name="id3 28843"></a>342 <a class="indexterm" name="id3 28849"></a>343 <a class="indexterm" name="id3 28856"></a>344 <a class="indexterm" name="id3 28863"></a>340 <a class="indexterm" name="id351484"></a> 341 <a class="indexterm" name="id351490"></a> 342 <a class="indexterm" name="id351497"></a> 343 <a class="indexterm" name="id351504"></a> 344 <a class="indexterm" name="id351511"></a> 345 345 In the case of MS Windows NT4-style domains, it is the PDC that initiates a new domain control database. 346 346 This forms a part of the Windows registry called the Security Account Manager (SAM). It plays a key … … 348 348 database with BDCs. 349 349 </p><p> 350 <a class="indexterm" name="id3 28878"></a>351 <a class="indexterm" name="id3 28890"></a>352 <a class="indexterm" name="id3 28896"></a>353 <a class="indexterm" name="id3 28906"></a>350 <a class="indexterm" name="id351526"></a> 351 <a class="indexterm" name="id351537"></a> 352 <a class="indexterm" name="id351544"></a> 353 <a class="indexterm" name="id351553"></a> 354 354 With MS Windows 200x Server-based Active Directory domains, one domain controller initiates a potential 355 355 hierarchy of domain controllers, each with its own area of delegated control. The master domain … … 358 358 LDAP-based user and machine account backend. 359 359 </p><p> 360 <a class="indexterm" name="id3 28919"></a>361 <a class="indexterm" name="id3 28926"></a>360 <a class="indexterm" name="id351567"></a> 361 <a class="indexterm" name="id351574"></a> 362 362 New to Samba-3 is the ability to use a backend database that holds the same type of data as the NT4-style SAM 363 database (one of the registry files)<sup>[<a name="id3 28934" href="#ftn.id328934">1</a>]</sup>364 </p><p> 365 <a class="indexterm" name="id3 28950"></a>366 <a class="indexterm" name="id3 28956"></a>367 <a class="indexterm" name="id3 28963"></a>368 <a class="indexterm" name="id3 28970"></a>369 <a class="indexterm" name="id3 28977"></a>370 <a class="indexterm" name="id3 28983"></a>363 database (one of the registry files)<sup>[<a name="id351582" href="#ftn.id351582" class="footnote">1</a>]</sup> 364 </p><p> 365 <a class="indexterm" name="id351598"></a> 366 <a class="indexterm" name="id351604"></a> 367 <a class="indexterm" name="id351611"></a> 368 <a class="indexterm" name="id351617"></a> 369 <a class="indexterm" name="id351624"></a> 370 <a class="indexterm" name="id351631"></a> 371 371 The <span class="emphasis"><em>Backup Domain Controller</em></span> or BDC plays a key role in servicing network authentication 372 372 requests. The BDC is biased to answer logon requests in preference to the PDC. On a network segment that has … … 380 380 particular logon authentication request. 381 381 </p><p> 382 <a class="indexterm" name="id3 29005"></a>383 <a class="indexterm" name="id3 29012"></a>382 <a class="indexterm" name="id351653"></a> 383 <a class="indexterm" name="id351660"></a> 384 384 A Windows NT4 BDC can be promoted to a PDC. If the PDC is online at the time that a BDC is promoted to PDC, 385 385 the previous PDC is automatically demoted to a BDC. With Samba-3, this is not an automatic operation; the PDC 386 386 and BDC must be manually configured, and other appropriate changes also need to be made. 387 387 </p><p> 388 <a class="indexterm" name="id3 29025"></a>388 <a class="indexterm" name="id351672"></a> 389 389 With MS Windows NT4, a decision is made at installation to determine what type of machine the server will be. 390 390 It is possible to promote a BDC to a PDC, and vice versa. The only method Microsoft provide to convert a … … 394 394 it obtains authentication from a domain controller for all access controls.</p></li><li><p><span class="emphasis"><em>Standalone Server</em></span> one that plays no part in SAM synchronization, 395 395 has its own authentication database, and plays no role in domain security.</p></li></ul></div><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p> 396 <a class="indexterm" name="id3 29088"></a>396 <a class="indexterm" name="id351736"></a> 397 397 Algin Technology LLC provide a commercial tool that makes it possible to promote a Windows NT4 standalone 398 server to a PDC or a BDC, and also permits this process to be reversed. Refer to the <a href="http://utools.com/UPromote.asp" target="_top">Algin</a> web site for further information.398 server to a PDC or a BDC, and also permits this process to be reversed. Refer to the <a class="ulink" href="http://utools.com/UPromote.asp" target="_top">Algin</a> web site for further information. 399 399 </p></div><p> 400 <a class="indexterm" name="id3 29105"></a>401 <a class="indexterm" name="id3 29117"></a>400 <a class="indexterm" name="id351753"></a> 401 <a class="indexterm" name="id351764"></a> 402 402 Samba-3 servers can readily be converted to and from domain controller roles through simple changes to the 403 403 <code class="filename">smb.conf</code> file. Samba-3 is capable of acting fully as a native member of a Windows 200x server Active 404 404 Directory domain. 405 405 </p><p> 406 <a class="indexterm" name="id3 29135"></a>406 <a class="indexterm" name="id351782"></a> 407 407 For the sake of providing a complete picture, MS Windows 2000 domain control configuration is done after the server has been 408 408 installed. Please refer to Microsoft documentation for the procedures that should be followed to convert a 409 409 domain member server to or from a domain control, and to install or remove active directory service support. 410 410 </p><p> 411 <a class="indexterm" name="id3 29150"></a>412 <a class="indexterm" name="id3 29159"></a>411 <a class="indexterm" name="id351798"></a> 412 <a class="indexterm" name="id351807"></a> 413 413 New to Samba-3 is the ability to function fully as an MS Windows NT4-style domain controller, 414 414 excluding the SAM replication components. However, please be aware that Samba-3 also supports the 415 415 MS Windows 200x domain control protocols. 416 416 </p><p> 417 <a class="indexterm" name="id3 29173"></a>417 <a class="indexterm" name="id351821"></a> 418 418 At this time any appearance that Samba-3 is capable of acting as a <span class="emphasis"><em>domain controller</em></span> in 419 419 native ADS mode is limited and experimental in nature. This functionality should not be used until the Samba … … 423 423 </p><div class="itemizedlist"><ul type="disc"><li><p>No machine policy files.</p></li><li><p>No Group Policy Objects.</p></li><li><p>No synchronously executed Active Directory logon scripts.</p></li><li><p>Can't use Active Directory management tools to manage users and machines.</p></li><li><p>Registry changes tattoo the main registry, while with Active Directory they do not leave 424 424 permanent changes in effect.</p></li><li><p>Without Active Directory you cannot perform the function of exporting specific 425 applications to specific users or groups.</p></li></ul></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id3 29223"></a>Preparing for Domain Control</h3></div></div></div><p>426 <a class="indexterm" name="id3 29231"></a>427 <a class="indexterm" name="id3 29237"></a>428 <a class="indexterm" name="id3 29244"></a>429 <a class="indexterm" name="id3 29251"></a>425 applications to specific users or groups.</p></li></ul></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id351870"></a>Preparing for Domain Control</h3></div></div></div><p> 426 <a class="indexterm" name="id351878"></a> 427 <a class="indexterm" name="id351885"></a> 428 <a class="indexterm" name="id351892"></a> 429 <a class="indexterm" name="id351899"></a> 430 430 There are two ways that MS Windows machines may interact with each other, with other servers, 431 431 and with domain controllers: either as <span class="emphasis"><em>standalone</em></span> systems, more commonly … … 433 433 more commonly called <span class="emphasis"><em>domain</em></span> members. 434 434 </p><p> 435 <a class="indexterm" name="id3 29274"></a>436 <a class="indexterm" name="id3 29281"></a>437 <a class="indexterm" name="id3 29290"></a>435 <a class="indexterm" name="id351922"></a> 436 <a class="indexterm" name="id351928"></a> 437 <a class="indexterm" name="id351938"></a> 438 438 It should be noted that workgroup membership involves no special configuration other than the machine being 439 439 configured so the network configuration has a commonly used name for its workgroup entry. It is not uncommon … … 443 443 involve security machine accounts</em></span>. 444 444 </p><p> 445 <a class="indexterm" name="id3 29308"></a>446 <a class="indexterm" name="id3 29315"></a>447 <a class="indexterm" name="id3 29324"></a>445 <a class="indexterm" name="id351956"></a> 446 <a class="indexterm" name="id351963"></a> 447 <a class="indexterm" name="id351972"></a> 448 448 Domain member machines have a machine trust account in the domain accounts database. A special procedure 449 449 must be followed on each machine to effect domain membership. This procedure, which can be done … … 452 452 domain, a machine trust account password change will be automatically triggered. 453 453 </p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p> 454 <a class="indexterm" name="id3 29339"></a>454 <a class="indexterm" name="id351987"></a> 455 455 When Samba is configured as a domain controller, secure network operation demands that 456 456 all MS Windows NT4/200x/XP Professional clients should be configured as domain members. 457 457 If a machine is not made a member of the domain, then it will operate like a workgroup 458 (standalone) machine. Please refer to <a href="domain-member.html" title="Chapter 6. Domain Membership">Domain Membership</a>, for458 (standalone) machine. Please refer to <a class="link" href="domain-member.html" title="Chapter 6. Domain Membership">Domain Membership</a>, for 459 459 information regarding domain membership. 460 460 </p></div><p> 461 461 The following are necessary for configuring Samba-3 as an MS Windows NT4-style PDC for MS Windows 462 462 NT4/200x/XP clients: 463 </p><div class="itemizedlist"><ul type="disc"><li><p>Configuration of basic TCP/IP and MS Windows networking.</p></li><li><p>Correct designation of the server role (<a class=" indexterm" name="id329372"></a>security = user).</p></li><li><p>Consistent configuration of name resolution.<sup>[<a name="id329384" href="#ftn.id329384">2</a>]</sup></p></li><li><p>Domain logons for Windows NT4/200x/XP Professional clients.</p></li><li><p>Configuration of roaming profiles or explicit configuration to force local profile usage.</p></li><li><p>Configuration of network/system policies.</p></li><li><p>Adding and managing domain user accounts.</p></li><li><p>Configuring MS Windows NT4/2000 Professional and Windows XP Professional client machines to become domain members.</p></li></ul></div><p>463 </p><div class="itemizedlist"><ul type="disc"><li><p>Configuration of basic TCP/IP and MS Windows networking.</p></li><li><p>Correct designation of the server role (<a class="link" href="smb.conf.5.html#SECURITY">security = user</a>).</p></li><li><p>Consistent configuration of name resolution.<sup>[<a name="id352035" href="#ftn.id352035" class="footnote">2</a>]</sup></p></li><li><p>Domain logons for Windows NT4/200x/XP Professional clients.</p></li><li><p>Configuration of roaming profiles or explicit configuration to force local profile usage.</p></li><li><p>Configuration of network/system policies.</p></li><li><p>Adding and managing domain user accounts.</p></li><li><p>Configuring MS Windows NT4/2000 Professional and Windows XP Professional client machines to become domain members.</p></li></ul></div><p> 464 464 The following provisions are required to serve MS Windows 9x/Me clients: 465 </p><div class="itemizedlist"><ul type="disc"><li><p>Configuration of basic TCP/IP and MS Windows networking.</p></li><li><p>Correct designation of the server role (<a class=" indexterm" name="id329444"></a>security = user).</p></li><li><p>Network logon configuration (since Windows 9x/Me/XP Home are not technically domain465 </p><div class="itemizedlist"><ul type="disc"><li><p>Configuration of basic TCP/IP and MS Windows networking.</p></li><li><p>Correct designation of the server role (<a class="link" href="smb.conf.5.html#SECURITY">security = user</a>).</p></li><li><p>Network logon configuration (since Windows 9x/Me/XP Home are not technically domain 466 466 members, they do not really participate in the security aspects of Domain logons as such).</p></li><li><p>Roaming profile configuration.</p></li><li><p>Configuration of system policy handling.</p></li><li><p>Installation of the network driver “<span class="quote">Client for MS Windows Networks</span>” and configuration 467 467 to log onto the domain.</p></li><li><p>Placing Windows 9x/Me clients in user-level security if it is desired to allow 468 468 all client-share access to be controlled according to domain user/group identities.</p></li><li><p>Adding and managing domain user accounts.</p></li></ul></div><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p> 469 <a class="indexterm" name="id3 29494"></a>470 <a class="indexterm" name="id3 29500"></a>469 <a class="indexterm" name="id352148"></a> 470 <a class="indexterm" name="id352154"></a> 471 471 Roaming profiles and system/network policies are advanced network administration topics 472 that are covered in <a href="ProfileMgmt.html" title="Chapter 27. Desktop Profile Management">Desktop Profile Management</a> and473 <a href="PolicyMgmt.html" title="Chapter 26. System and Account Policies">System and Account Policies</a> of this document. However, these are not472 that are covered in <a class="link" href="ProfileMgmt.html" title="Chapter 27. Desktop Profile Management">Desktop Profile Management</a> and 473 <a class="link" href="PolicyMgmt.html" title="Chapter 26. System and Account Policies">System and Account Policies</a> of this document. However, these are not 474 474 necessarily specific to a Samba PDC as much as they are related to Windows NT networking concepts. 475 475 </p></div><p> 476 476 A domain controller is an SMB/CIFS server that: 477 477 </p><div class="itemizedlist"><ul type="disc"><li><p> 478 <a class="indexterm" name="id3 29534"></a>479 <a class="indexterm" name="id3 29542"></a>480 <a class="indexterm" name="id3 29549"></a>481 <a class="indexterm" name="id3 29556"></a>482 <a class="indexterm" name="id3 29563"></a>478 <a class="indexterm" name="id352188"></a> 479 <a class="indexterm" name="id352196"></a> 480 <a class="indexterm" name="id352203"></a> 481 <a class="indexterm" name="id352210"></a> 482 <a class="indexterm" name="id352217"></a> 483 483 Registers and advertises itself as a domain controller (through NetBIOS broadcasts 484 484 as well as by way of name registrations either by Mailslot Broadcasts over UDP broadcast, 485 485 to a WINS server over UDP unicast, or via DNS and Active Directory). 486 486 </p></li><li><p> 487 <a class="indexterm" name="id3 29576"></a>488 <a class="indexterm" name="id3 29583"></a>487 <a class="indexterm" name="id352230"></a> 488 <a class="indexterm" name="id352237"></a> 489 489 Provides the NETLOGON service. (This is actually a collection of services that runs over 490 490 multiple protocols. These include the LanMan logon service, the Netlogon service, … … 493 493 Provides a share called NETLOGON. 494 494 </p></li></ul></div><p> 495 <a class="indexterm" name="id3 29600"></a>496 <a class="indexterm" name="id3 29612"></a>497 <a class="indexterm" name="id3 29624"></a>498 <a class="indexterm" name="id3 29630"></a>499 <a class="indexterm" name="id3 29637"></a>495 <a class="indexterm" name="id352254"></a> 496 <a class="indexterm" name="id352266"></a> 497 <a class="indexterm" name="id352278"></a> 498 <a class="indexterm" name="id352284"></a> 499 <a class="indexterm" name="id352291"></a> 500 500 It is rather easy to configure Samba to provide these. Each Samba domain controller must provide the NETLOGON 501 service that Samba calls the <a class=" indexterm" name="id329645"></a>domain logonsfunctionality (after the name of the501 service that Samba calls the <a class="link" href="smb.conf.5.html#DOMAINLOGONS">domain logons</a> functionality (after the name of the 502 502 parameter in the <code class="filename">smb.conf</code> file). Additionally, one server in a Samba-3 domain must advertise itself as the 503 domain master browser.<sup>[<a name="id3 29659" href="#ftn.id329659">3</a>]</sup> This causes the PDC to claim a domain-specific NetBIOS name that identifies503 domain master browser.<sup>[<a name="id352318" href="#ftn.id352318" class="footnote">3</a>]</sup> This causes the PDC to claim a domain-specific NetBIOS name that identifies 504 504 it as a DMB for its given domain or workgroup. Local master browsers (LMBs) in the same domain or workgroup on 505 505 broadcast-isolated subnets then ask for a complete copy of the browse list for the whole wide-area network. 506 506 Browser clients then contact their LMB, and will receive the domain-wide browse list instead of just the list 507 507 for their broadcast-isolated subnet. 508 </p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id3 29677"></a>Domain Control: Example Configuration</h2></div></div></div><p>508 </p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id352336"></a>Domain Control: Example Configuration</h2></div></div></div><p> 509 509 The first step in creating a working Samba PDC is to understand the parameters necessary 510 in <code class="filename">smb.conf</code>. An example <code class="filename">smb.conf</code> for acting as a PDC can be found in <a href="samba-pdc.html#pdc-example" title="Example 4.1. smb.conf for being a PDC">the510 in <code class="filename">smb.conf</code>. An example <code class="filename">smb.conf</code> for acting as a PDC can be found in <a class="link" href="samba-pdc.html#pdc-example" title="Example 4.1. smb.conf for being a PDC">the 511 511 smb.conf file for an example PDC</a>. 512 </p><div class="example"><a name="pdc-example"></a><p class="title"><b>Example 4.1. smb.conf for being a PDC</b></p><div class="example-contents"><table class="simplelist" border="0" summary="Simple list"><tr><td> </td></tr><tr><td><em class="parameter"><code>[global]</code></em></td></tr><tr><td><a class="indexterm" name="id3 29730"></a><em class="parameter"><code>netbios name</code></em></td></tr><tr><td><a class="indexterm" name="id329743"></a><em class="parameter"><code>workgroup</code></em></td></tr><tr><td><a class="indexterm" name="id329755"></a><em class="parameter"><code>passdb backend = tdbsam</code></em></td></tr><tr><td><a class="indexterm" name="id329768"></a><em class="parameter"><code>os level = 33</code></em></td></tr><tr><td><a class="indexterm" name="id329780"></a><em class="parameter"><code>preferred master = auto</code></em></td></tr><tr><td><a class="indexterm" name="id329793"></a><em class="parameter"><code>domain master = yes</code></em></td></tr><tr><td><a class="indexterm" name="id329805"></a><em class="parameter"><code>local master = yes</code></em></td></tr><tr><td><a class="indexterm" name="id329818"></a><em class="parameter"><code>security = user</code></em></td></tr><tr><td><a class="indexterm" name="id329830"></a><em class="parameter"><code>domain logons = yes</code></em></td></tr><tr><td><a class="indexterm" name="id329843"></a><em class="parameter"><code>logon path = \\%N\profiles\%U</code></em></td></tr><tr><td><a class="indexterm" name="id329856"></a><em class="parameter"><code>logon drive = H:</code></em></td></tr><tr><td><a class="indexterm" name="id329868"></a><em class="parameter"><code>logon home = \\homeserver\%U\winprofile</code></em></td></tr><tr><td><a class="indexterm" name="id329881"></a><em class="parameter"><code>logon script = logon.cmd</code></em></td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[netlogon]</code></em></td></tr><tr><td><a class="indexterm" name="id329902"></a><em class="parameter"><code>path = /var/lib/samba/netlogon</code></em></td></tr><tr><td><a class="indexterm" name="id329915"></a><em class="parameter"><code>read only = yes</code></em></td></tr><tr><td><a class="indexterm" name="id329928"></a><em class="parameter"><code>write list</code></em></td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[profiles]</code></em></td></tr><tr><td><a class="indexterm" name="id329949"></a><em class="parameter"><code>path = /var/lib/samba/profiles</code></em></td></tr><tr><td><a class="indexterm" name="id329962"></a><em class="parameter"><code>read only = no</code></em></td></tr><tr><td><a class="indexterm" name="id329974"></a><em class="parameter"><code>create mask = 0600</code></em></td></tr><tr><td><a class="indexterm" name="id329987"></a><em class="parameter"><code>directory mask = 0700</code></em></td></tr></table></div></div><br class="example-break"><p>513 The basic options shown in <a href="samba-pdc.html#pdc-example" title="Example 4.1. smb.conf for being a PDC">this example</a> are explained as follows:512 </p><div class="example"><a name="pdc-example"></a><p class="title"><b>Example 4.1. smb.conf for being a PDC</b></p><div class="example-contents"><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="id352389"></a></td></tr><tr><td><a class="indexterm" name="id352395"></a></td></tr><tr><td><a class="indexterm" name="id352402"></a><em class="parameter"><code>passdb backend = tdbsam</code></em></td></tr><tr><td><a class="indexterm" name="id352414"></a><em class="parameter"><code>os level = 33</code></em></td></tr><tr><td><a class="indexterm" name="id352425"></a><em class="parameter"><code>preferred master = auto</code></em></td></tr><tr><td><a class="indexterm" name="id352437"></a><em class="parameter"><code>domain master = yes</code></em></td></tr><tr><td><a class="indexterm" name="id352448"></a><em class="parameter"><code>local master = yes</code></em></td></tr><tr><td><a class="indexterm" name="id352460"></a><em class="parameter"><code>security = user</code></em></td></tr><tr><td><a class="indexterm" name="id352471"></a><em class="parameter"><code>domain logons = yes</code></em></td></tr><tr><td><a class="indexterm" name="id352482"></a><em class="parameter"><code>logon path = \\%N\profiles\%U</code></em></td></tr><tr><td><a class="indexterm" name="id352494"></a><em class="parameter"><code>logon drive = H:</code></em></td></tr><tr><td><a class="indexterm" name="id352506"></a><em class="parameter"><code>logon home = \\homeserver\%U\winprofile</code></em></td></tr><tr><td><a class="indexterm" name="id352517"></a><em class="parameter"><code>logon script = logon.cmd</code></em></td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[netlogon]</code></em></td></tr><tr><td><a class="indexterm" name="id352538"></a><em class="parameter"><code>path = /var/lib/samba/netlogon</code></em></td></tr><tr><td><a class="indexterm" name="id352549"></a><em class="parameter"><code>read only = yes</code></em></td></tr><tr><td><a class="indexterm" name="id352561"></a></td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[profiles]</code></em></td></tr><tr><td><a class="indexterm" name="id352576"></a><em class="parameter"><code>path = /var/lib/samba/profiles</code></em></td></tr><tr><td><a class="indexterm" name="id352588"></a><em class="parameter"><code>read only = no</code></em></td></tr><tr><td><a class="indexterm" name="id352600"></a><em class="parameter"><code>create mask = 0600</code></em></td></tr><tr><td><a class="indexterm" name="id352611"></a><em class="parameter"><code>directory mask = 0700</code></em></td></tr></table></div></div><br class="example-break"><p> 513 The basic options shown in <a class="link" href="samba-pdc.html#pdc-example" title="Example 4.1. smb.conf for being a PDC">this example</a> are explained as follows: 514 514 </p><div class="variablelist"><dl><dt><span class="term">passdb backend </span></dt><dd><p> 515 <a class="indexterm" name="id3 30021"></a>516 <a class="indexterm" name="id3 30030"></a>517 <a class="indexterm" name="id3 30037"></a>518 <a class="indexterm" name="id3 30044"></a>519 <a class="indexterm" name="id3 30051"></a>520 <a class="indexterm" name="id3 30057"></a>515 <a class="indexterm" name="id352644"></a> 516 <a class="indexterm" name="id352653"></a> 517 <a class="indexterm" name="id352660"></a> 518 <a class="indexterm" name="id352667"></a> 519 <a class="indexterm" name="id352674"></a> 520 <a class="indexterm" name="id352680"></a> 521 521 This contains all the user and group account information. Acceptable values for a PDC 522 522 are: <span class="emphasis"><em>smbpasswd, tdbsam, and ldapsam</em></span>. The “<span class="quote">guest</span>” entry provides 523 523 default accounts and is included by default; there is no need to add it explicitly. 524 524 </p><p> 525 <a class="indexterm" name="id3 30077"></a>526 <a class="indexterm" name="id3 30084"></a>527 <a class="indexterm" name="id3 30090"></a>528 <a class="indexterm" name="id3 30097"></a>525 <a class="indexterm" name="id352700"></a> 526 <a class="indexterm" name="id352707"></a> 527 <a class="indexterm" name="id352713"></a> 528 <a class="indexterm" name="id352720"></a> 529 529 Where use of BDCs is intended, the only logical choice is 530 530 to use LDAP so the passdb backend can be distributed. The tdbsam and smbpasswd files 531 531 cannot effectively be distributed and therefore should not be used. 532 532 </p></dd><dt><span class="term">Domain Control Parameters </span></dt><dd><p> 533 <a class="indexterm" name="id3 30116"></a>534 <a class="indexterm" name="id3 30123"></a>535 <a class="indexterm" name="id3 30130"></a>536 <a class="indexterm" name="id3 30136"></a>533 <a class="indexterm" name="id352739"></a> 534 <a class="indexterm" name="id352746"></a> 535 <a class="indexterm" name="id352753"></a> 536 <a class="indexterm" name="id352759"></a> 537 537 The parameters <span class="emphasis"><em>os level, preferred master, domain master, security, 538 538 encrypt passwords</em></span>, and <span class="emphasis"><em>domain logons</em></span> play a central role in assuring domain 539 539 control and network logon support. 540 540 </p><p> 541 <a class="indexterm" name="id3 30158"></a>542 <a class="indexterm" name="id3 30164"></a>541 <a class="indexterm" name="id352781"></a> 542 <a class="indexterm" name="id352787"></a> 543 543 The <span class="emphasis"><em>os level</em></span> must be set at or above a value of 32. A domain controller 544 544 must be the DMB, must be set in <span class="emphasis"><em>user</em></span> mode security, 545 545 must support Microsoft-compatible encrypted passwords, and must provide the network logon 546 546 service (domain logons). Encrypted passwords must be enabled. For more details on how 547 to do this, refer to <a href="passdb.html" title="Chapter 11. Account Information Databases">Account Information Databases</a>.547 to do this, refer to <a class="link" href="passdb.html" title="Chapter 11. Account Information Databases">Account Information Databases</a>. 548 548 </p></dd><dt><span class="term">Environment Parameters </span></dt><dd><p> 549 <a class="indexterm" name="id3 30198"></a>550 <a class="indexterm" name="id3 30205"></a>551 <a class="indexterm" name="id3 30212"></a>552 <a class="indexterm" name="id3 30218"></a>549 <a class="indexterm" name="id352821"></a> 550 <a class="indexterm" name="id352828"></a> 551 <a class="indexterm" name="id352835"></a> 552 <a class="indexterm" name="id352841"></a> 553 553 The parameters <span class="emphasis"><em>logon path, logon home, logon drive</em></span>, and <span class="emphasis"><em>logon script</em></span> are 554 554 environment support settings that help to facilitate client logon operations and that help … … 556 556 to the man page information for these parameters. 557 557 </p></dd><dt><span class="term">NETLOGON Share </span></dt><dd><p> 558 <a class="indexterm" name="id3 30245"></a>559 <a class="indexterm" name="id3 30252"></a>560 <a class="indexterm" name="id3 30258"></a>561 <a class="indexterm" name="id3 30265"></a>562 <a class="indexterm" name="id3 30272"></a>563 <a class="indexterm" name="id3 30279"></a>558 <a class="indexterm" name="id352868"></a> 559 <a class="indexterm" name="id352875"></a> 560 <a class="indexterm" name="id352881"></a> 561 <a class="indexterm" name="id352888"></a> 562 <a class="indexterm" name="id352895"></a> 563 <a class="indexterm" name="id352902"></a> 564 564 The NETLOGON share plays a central role in domain logon and domain membership support. 565 565 This share is provided on all Microsoft domain controllers. It is used to provide logon … … 567 567 tools that may be needed for logon processing. This is an essential share on a domain controller. 568 568 </p></dd><dt><span class="term">PROFILE Share </span></dt><dd><p> 569 <a class="indexterm" name="id3 30299"></a>570 <a class="indexterm" name="id3 30305"></a>571 <a class="indexterm" name="id3 30312"></a>572 <a class="indexterm" name="id3 30319"></a>573 <a class="indexterm" name="id3 30326"></a>569 <a class="indexterm" name="id352922"></a> 570 <a class="indexterm" name="id352928"></a> 571 <a class="indexterm" name="id352935"></a> 572 <a class="indexterm" name="id352942"></a> 573 <a class="indexterm" name="id352949"></a> 574 574 This share is used to store user desktop profiles. Each user must have a directory at the root 575 575 of this share. This directory must be write-enabled for the user and must be globally read-enabled. … … 581 581 of operation. The following <code class="filename">smb.conf</code> parameters are the essentials alone: 582 582 </p><p> 583 </p><table class="simplelist" border="0" summary="Simple list"><tr><td><a class="indexterm" name="id3 30361"></a><em class="parameter"><code>netbios name = BELERIAND</code></em></td></tr><tr><td><a class="indexterm" name="id330374"></a><em class="parameter"><code>workgroup = MIDEARTH</code></em></td></tr><tr><td><a class="indexterm" name="id330386"></a><em class="parameter"><code>domain logons = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id330399"></a><em class="parameter"><code>domain master = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id330411"></a><em class="parameter"><code>security = User</code></em></td></tr></table><p>583 </p><table class="simplelist" border="0" summary="Simple list"><tr><td><a class="indexterm" name="id352984"></a><em class="parameter"><code>netbios name = BELERIAND</code></em></td></tr><tr><td><a class="indexterm" name="id352996"></a><em class="parameter"><code>workgroup = MIDEARTH</code></em></td></tr><tr><td><a class="indexterm" name="id353007"></a><em class="parameter"><code>domain logons = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id353018"></a><em class="parameter"><code>domain master = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id353030"></a><em class="parameter"><code>security = User</code></em></td></tr></table><p> 584 584 </p><p> 585 585 The additional parameters shown in the longer listing in this section just make for 586 586 a more complete explanation. 587 </p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id3 30430"></a>Samba ADS Domain Control</h2></div></div></div><p>588 <a class="indexterm" name="id3 30438"></a>587 </p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id353048"></a>Samba ADS Domain Control</h2></div></div></div><p> 588 <a class="indexterm" name="id353056"></a> 589 589 Samba-3 is not, and cannot act as, an Active Directory server. It cannot truly function as an Active Directory 590 590 PDC. The protocols for some of the functionality of Active Directory domain controllers has been partially … … 595 595 someday or maybe never! 596 596 </p><p> 597 <a class="indexterm" name="id3 30454"></a>598 <a class="indexterm" name="id3 30460"></a>597 <a class="indexterm" name="id353077"></a> 598 <a class="indexterm" name="id353084"></a> 599 599 To be sure, Samba-3 is designed to provide most of the functionality that Microsoft Windows NT4-style 600 600 domain controllers have. Samba-3 does not have all the capabilities of Windows NT4, but it does have … … 602 602 is not Windows Server 200x: it is not an Active Directory server. We hope this is plain and simple 603 603 enough for all to understand. 604 </p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id3 30473"></a>Domain and Network Logon Configuration</h2></div></div></div><p>605 <a class="indexterm" name="id3 30481"></a>604 </p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id353096"></a>Domain and Network Logon Configuration</h2></div></div></div><p> 605 <a class="indexterm" name="id353104"></a> 606 606 The subject of network or domain logons is discussed here because it forms 607 607 an integral part of the essential functionality that is provided by a domain controller. 608 </p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id3 30490"></a>Domain Network Logon Service</h3></div></div></div><p>609 <a class="indexterm" name="id3 30498"></a>608 </p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id353114"></a>Domain Network Logon Service</h3></div></div></div><p> 609 <a class="indexterm" name="id353122"></a> 610 610 All domain controllers must run the netlogon service (<span class="emphasis"><em>domain logons</em></span> 611 in Samba). One domain controller must be configured with <a class=" indexterm" name="id330510"></a>domain master = Yes612 (the PDC); on all BDCs set the parameter <a class=" indexterm" name="id330517"></a>domain master = No.613 </p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id3 30525"></a>Example Configuration</h4></div></div></div><div class="example"><a name="PDC-config"></a><p class="title"><b>Example 4.2. smb.conf for being a PDC</b></p><div class="example-contents"><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="id330554"></a><em class="parameter"><code>domain logons = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id330567"></a><em class="parameter"><code>domain master = (Yes on PDC, No on BDCs)</code></em></td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[netlogon]</code></em></td></tr><tr><td><a class="indexterm" name="id330588"></a><em class="parameter"><code>comment = Network Logon Service</code></em></td></tr><tr><td><a class="indexterm" name="id330601"></a><em class="parameter"><code>path = /var/lib/samba/netlogon</code></em></td></tr><tr><td><a class="indexterm" name="id330614"></a><em class="parameter"><code>guest ok = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id330626"></a><em class="parameter"><code>browseable = No</code></em></td></tr></table></div></div><br class="example-break"></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id330641"></a>The Special Case of MS Windows XP Home Edition</h4></div></div></div><p>614 <a class="indexterm" name="id3 30649"></a>611 in Samba). One domain controller must be configured with <a class="link" href="smb.conf.5.html#DOMAINMASTER">domain master = Yes</a> 612 (the PDC); on all BDCs set the parameter <a class="link" href="smb.conf.5.html#DOMAINMASTER">domain master = No</a>. 613 </p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id353156"></a>Example Configuration</h4></div></div></div><div class="example"><a name="PDC-config"></a><p class="title"><b>Example 4.2. smb.conf for being a PDC</b></p><div class="example-contents"><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="id353184"></a><em class="parameter"><code>domain logons = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id353196"></a><em class="parameter"><code>domain master = (Yes on PDC, No on BDCs)</code></em></td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[netlogon]</code></em></td></tr><tr><td><a class="indexterm" name="id353217"></a><em class="parameter"><code>comment = Network Logon Service</code></em></td></tr><tr><td><a class="indexterm" name="id353228"></a><em class="parameter"><code>path = /var/lib/samba/netlogon</code></em></td></tr><tr><td><a class="indexterm" name="id353240"></a><em class="parameter"><code>guest ok = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id353251"></a><em class="parameter"><code>browseable = No</code></em></td></tr></table></div></div><br class="example-break"></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id353265"></a>The Special Case of MS Windows XP Home Edition</h4></div></div></div><p> 614 <a class="indexterm" name="id353273"></a> 615 615 To be completely clear: If you want MS Windows XP Home Edition to integrate with your 616 616 MS Windows NT4 or Active Directory domain security, understand it cannot be done. … … 626 626 If it can be done, then to do so would violate your software license agreement with 627 627 Microsoft, and we recommend that you do not do that. 628 </p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id3 30672"></a>The Special Case of Windows 9x/Me</h4></div></div></div><p>629 <a class="indexterm" name="id3 30680"></a>630 <a class="indexterm" name="id3 30687"></a>631 <a class="indexterm" name="id3 30694"></a>632 <a class="indexterm" name="id3 30700"></a>633 <a class="indexterm" name="id3 30707"></a>628 </p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id353296"></a>The Special Case of Windows 9x/Me</h4></div></div></div><p> 629 <a class="indexterm" name="id353304"></a> 630 <a class="indexterm" name="id353311"></a> 631 <a class="indexterm" name="id353318"></a> 632 <a class="indexterm" name="id353324"></a> 633 <a class="indexterm" name="id353331"></a> 634 634 A domain and a workgroup are exactly the same in terms of network 635 635 browsing. The difference is that a distributable authentication … … 639 639 now in the same way as MS Windows NT/200x. 640 640 </p><p> 641 <a class="indexterm" name="id3 30721"></a>641 <a class="indexterm" name="id353345"></a> 642 642 The SMB client logging on to a domain has an expectation that every other 643 643 server in the domain should accept the same authentication information. … … 646 646 It should be noted that browsing is totally orthogonal to logon support. 647 647 </p><p> 648 <a class="indexterm" name="id3 30737"></a>649 <a class="indexterm" name="id3 30744"></a>650 <a class="indexterm" name="id3 30750"></a>648 <a class="indexterm" name="id353358"></a> 649 <a class="indexterm" name="id353365"></a> 650 <a class="indexterm" name="id353371"></a> 651 651 Issues related to the single-logon network model are discussed in this 652 652 section. Samba supports domain logons, network logon scripts, and user … … 654 654 which are the focus of this section. 655 655 </p><p> 656 <a class="indexterm" name="id3 30763"></a>656 <a class="indexterm" name="id353384"></a> 657 657 When an SMB client in a domain wishes to log on, it broadcasts requests for a logon server. The first one to 658 658 reply gets the job and validates its password using whatever mechanism the Samba administrator has installed. … … 670 670 performs a logon: 671 671 </p><div class="orderedlist"><ol type="1"><li><p> 672 <a class="indexterm" name="id3 30801"></a>673 <a class="indexterm" name="id3 30807"></a>672 <a class="indexterm" name="id353422"></a> 673 <a class="indexterm" name="id353428"></a> 674 674 The client broadcasts (to the IP broadcast address of the subnet it is in) 675 675 a NetLogon request. This is sent to the NetBIOS name DOMAIN<1C> at the … … 680 680 the netlogon service). 681 681 </p></li><li><p> 682 <a class="indexterm" name="id3 30841"></a>683 <a class="indexterm" name="id3 30847"></a>684 <a class="indexterm" name="id3 30854"></a>682 <a class="indexterm" name="id353462"></a> 683 <a class="indexterm" name="id353468"></a> 684 <a class="indexterm" name="id353475"></a> 685 685 The client connects to that server, logs on (does an SMBsessetupX) and 686 686 then connects to the IPC$ share (using an SMBtconX). 687 687 </p></li><li><p> 688 <a class="indexterm" name="id3 30869"></a>688 <a class="indexterm" name="id353490"></a> 689 689 The client does a NetWkstaUserLogon request, which retrieves the name 690 690 of the user's logon script. … … 694 694 After this, the client disconnects from the NetLogon share. 695 695 </p></li><li><p> 696 <a class="indexterm" name="id3 30891"></a>697 <a class="indexterm" name="id3 30898"></a>696 <a class="indexterm" name="id353512"></a> 697 <a class="indexterm" name="id353519"></a> 698 698 The client sends a NetUserGetInfo request to the server to retrieve 699 699 the user's home share, which is used to search for profiles. Since the … … 702 702 home directory. 703 703 </p></li><li><p> 704 <a class="indexterm" name="id3 30914"></a>704 <a class="indexterm" name="id353535"></a> 705 705 The client connects to the user's home share and searches for the 706 706 user's profile. As it turns out, you can specify the user's home share as … … 708 708 If the profiles are found, they are implemented. 709 709 </p></li><li><p> 710 <a class="indexterm" name="id3 30935"></a>710 <a class="indexterm" name="id353556"></a> 711 711 The client then disconnects from the user's home share and reconnects to 712 712 the NetLogon share and looks for <code class="filename">CONFIG.POL</code>, the policies file. If this is … … 715 715 The main difference between a PDC and a Windows 9x/Me logon server configuration is: 716 716 </p><div class="itemizedlist"><ul type="disc"><li><p> 717 <a class="indexterm" name="id3 30962"></a>718 <a class="indexterm" name="id3 30971"></a>717 <a class="indexterm" name="id353583"></a> 718 <a class="indexterm" name="id353592"></a> 719 719 Password encryption is not required for a Windows 9x/Me logon server. But note 720 720 that beginning with MS Windows 98 the default setting is that plaintext 721 721 password support is disabled. It can be re-enabled with the registry 722 changes that are documented in <a href="PolicyMgmt.html" title="Chapter 26. System and Account Policies">System and Account Policies</a>.723 </p></li><li><p> 724 <a class="indexterm" name="id3 30992"></a>722 changes that are documented in <a class="link" href="PolicyMgmt.html" title="Chapter 26. System and Account Policies">System and Account Policies</a>. 723 </p></li><li><p> 724 <a class="indexterm" name="id353613"></a> 725 725 Windows 9x/Me clients do not require and do not use Machine Trust Accounts. 726 726 </p></li></ul></div><p> 727 <a class="indexterm" name="id3 31003"></a>727 <a class="indexterm" name="id353624"></a> 728 728 A Samba PDC will act as a Windows 9x/Me logon server; after all, it does provide the 729 729 network logon services that MS Windows 9x/Me expect to find. 730 730 </p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p> 731 <a class="indexterm" name="id3 31016"></a>731 <a class="indexterm" name="id353637"></a> 732 732 Use of plaintext passwords is strongly discouraged. Where used they are easily detected 733 733 using a sniffer tool to examine network traffic. 734 </p></div></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id3 31027"></a>Security Mode and Master Browsers</h3></div></div></div><p>735 <a class="indexterm" name="id3 31035"></a>736 <a class="indexterm" name="id3 31042"></a>737 <a class="indexterm" name="id3 31048"></a>734 </p></div></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id353648"></a>Security Mode and Master Browsers</h3></div></div></div><p> 735 <a class="indexterm" name="id353656"></a> 736 <a class="indexterm" name="id353663"></a> 737 <a class="indexterm" name="id353669"></a> 738 738 There are a few comments to make in order to tie up some loose ends. There has been much debate over the issue 739 739 of whether it is okay to configure Samba as a domain controller that operates with security mode other than … … 741 741 and server mode security are really just a variation on SMB user-level security. 742 742 </p><p> 743 <a class="indexterm" name="id3 31062"></a>744 <a class="indexterm" name="id3 31069"></a>745 <a class="indexterm" name="id3 31076"></a>746 <a class="indexterm" name="id3 31082"></a>747 <a class="indexterm" name="id3 31089"></a>748 <a class="indexterm" name="id3 31095"></a>749 <a class="indexterm" name="id3 31102"></a>743 <a class="indexterm" name="id353683"></a> 744 <a class="indexterm" name="id353690"></a> 745 <a class="indexterm" name="id353697"></a> 746 <a class="indexterm" name="id353703"></a> 747 <a class="indexterm" name="id353710"></a> 748 <a class="indexterm" name="id353716"></a> 749 <a class="indexterm" name="id353723"></a> 750 750 Actually, this issue is also closely tied to the debate on whether Samba must be the DMB for its workgroup 751 751 when operating as a domain controller. In a pure Microsoft Windows NT domain, the PDC wins the election to be … … 753 753 to locate the domain controller, all domain controllers register the DOMAIN<1C> name and Windows clients 754 754 locate a network logon server by seraching for the DOMAIN<1C> name. A DMB is a Domain Master Browser 755 see <a href="NetworkBrowsing.html" title="Chapter 10. Network Browsing">The Network Browsing Chapter</a>, <ahref="NetworkBrowsing.html#DMB" title="Configuring Workgroup Browsing">Configuring WORKGROUP Browsing</a>; Microsoft PDCs expect to win the election to become the755 see <a class="link" href="NetworkBrowsing.html" title="Chapter 10. Network Browsing">The Network Browsing Chapter</a>, <a class="link" href="NetworkBrowsing.html#DMB" title="Configuring Workgroup Browsing">Configuring WORKGROUP Browsing</a>; Microsoft PDCs expect to win the election to become the 756 756 DMB, if it loses that election it will report a continuous and rapid sequence of warning messages to its 757 757 Windows event logger complaining that it has lost the election to become a DMB. For this reason, in networks 758 758 where a Samba server is the PDC it is wise to configure the Samba domain controller as the DMB. 759 759 </p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p> 760 <a class="indexterm" name="id3 31143"></a>761 <a class="indexterm" name="id3 31149"></a>762 <a class="indexterm" name="id3 31156"></a>763 <a class="indexterm" name="id3 31163"></a>764 <a class="indexterm" name="id3 31170"></a>760 <a class="indexterm" name="id353764"></a> 761 <a class="indexterm" name="id353770"></a> 762 <a class="indexterm" name="id353777"></a> 763 <a class="indexterm" name="id353784"></a> 764 <a class="indexterm" name="id353791"></a> 765 765 SMB/CIFS servers that register the DOMAIN<1C> name do so because they provide the network logon 766 766 service. Server that register the DOMAIN<1B> name are DMBs meaning that they are responsible … … 771 771 other. 772 772 </p></div><p> 773 Now back to the issue of configuring a Samba domain controller to use a mode other than <a class=" indexterm" name="id331201"></a>security = user. If a Samba host is configured to use another SMB server or domain773 Now back to the issue of configuring a Samba domain controller to use a mode other than <a class="link" href="smb.conf.5.html#SECURITY">security = user</a>. If a Samba host is configured to use another SMB server or domain 774 774 controller in order to validate user connection requests, it is a fact that some other machine on the network 775 (the <a class=" indexterm" name="id331209"></a>password server) knows more about the user than the Samba host. About 99 percent775 (the <a class="link" href="smb.conf.5.html#PASSWORDSERVER">password server</a>) knows more about the user than the Samba host. About 99 percent 776 776 of the time, this other host is a domain controller. Now to operate in domain mode security, the 777 <a class=" indexterm" name="id331218"></a>workgroupparameter must be set to the name of the Windows NT domain (which already777 <a class="link" href="smb.conf.5.html#WORKGROUP">workgroup</a> parameter must be set to the name of the Windows NT domain (which already 778 778 has a domain controller). If the domain does not already have a domain controller, you do not yet have a 779 779 domain. … … 781 781 Configuring a Samba box as a domain controller for a domain that already by definition has a 782 782 PDC is asking for trouble. Therefore, you should always configure the Samba domain controller 783 to be the DMB for its domain and set <a class=" indexterm" name="id331231"></a>security = user.783 to be the DMB for its domain and set <a class="link" href="smb.conf.5.html#SECURITY">security = user</a>. 784 784 This is the only officially supported mode of operation. 785 </p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id3 31242"></a>Common Errors</h2></div></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id331248"></a>“<span class="quote">$</span>” Cannot Be Included in Machine Name</h3></div></div></div><p>786 <a class="indexterm" name="id3 31258"></a>787 <a class="indexterm" name="id3 31264"></a>788 <a class="indexterm" name="id3 31271"></a>785 </p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id353878"></a>Common Errors</h2></div></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id353884"></a>“<span class="quote">$</span>” Cannot Be Included in Machine Name</h3></div></div></div><p> 786 <a class="indexterm" name="id353894"></a> 787 <a class="indexterm" name="id353900"></a> 788 <a class="indexterm" name="id353907"></a> 789 789 A machine account, typically stored in <code class="filename">/etc/passwd</code>, takes the form of the machine 790 790 name with a “<span class="quote">$</span>” appended. Some BSD systems will not create a user with a “<span class="quote">$</span>” in the name. 791 791 Recent versions of FreeBSD have removed this limitation, but older releases are still in common use. 792 792 </p><p> 793 <a class="indexterm" name="id3 31296"></a>793 <a class="indexterm" name="id353932"></a> 794 794 The problem is only in the program used to make the entry. Once made, it works perfectly. Create a user 795 795 without the “<span class="quote">$</span>”. Then use <code class="literal">vipw</code> to edit the entry, adding the “<span class="quote">$</span>”. … … 799 799 The use of vipw will ensure that shadow files (where used) will remain current with the passwd file. This is 800 800 important for security reasons. 801 </p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id3 31343"></a>Joining Domain Fails Because of Existing Machine Account</h3></div></div></div><p>802 <a class="indexterm" name="id3 31351"></a>801 </p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id353978"></a>Joining Domain Fails Because of Existing Machine Account</h3></div></div></div><p> 802 <a class="indexterm" name="id353987"></a> 803 803 “<span class="quote">I get told, `You already have a connection to the Domain....' or `Cannot join domain, the 804 804 credentials supplied conflict with an existing set...' when creating a Machine Trust Account.</span>” … … 815 815 you are joining (bad idea), you will get this message. Change the workgroup name to something else 816 816 it does not matter what reboot, and try again. 817 </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id3 31401"></a>The System Cannot Log You On (C000019B)</h3></div></div></div><p>“<span class="quote">817 </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id354037"></a>The System Cannot Log You On (C000019B)</h3></div></div></div><p>“<span class="quote"> 818 818 I joined the domain successfully but after upgrading to a newer version of the Samba code I get the message, 819 819 <span class="errorname">`The system cannot log you on (C000019B). Please try again or consult your system 820 820 administrator</span> when attempting to logon.'</span>” 821 821 </p><p> 822 <a class="indexterm" name="id3 31419"></a>822 <a class="indexterm" name="id354055"></a> 823 823 This occurs when the domain SID stored in the secrets.tdb database is changed. The most common cause of a 824 824 change in domain SID is when the domain name and/or the server name (NetBIOS name) is changed. The only way … … 837 837 can be recovered from the secrets.tdb file. The alternative is to visit each workstation to rejoin 838 838 it to the domain. 839 </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id3 31468"></a>The Machine Trust Account Is Not Accessible</h3></div></div></div><p>839 </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id354104"></a>The Machine Trust Account Is Not Accessible</h3></div></div></div><p> 840 840 “<span class="quote">When I try to join the domain I get the message, <span class="errorname">"The machine account 841 841 for this computer either does not exist or is not accessible</span>." What's wrong?</span>” 842 842 </p><p> 843 843 This problem is caused by the PDC not having a suitable Machine Trust Account. If you are using the 844 <a class=" indexterm" name="id331488"></a>add machine scriptmethod to create accounts, then this would indicate that it has not844 <a class="link" href="smb.conf.5.html#ADDMACHINESCRIPT">add machine script</a> method to create accounts, then this would indicate that it has not 845 845 worked. Ensure the domain admin user system is working. 846 846 </p><p> … … 859 859 Some people have also reported that inconsistent subnet masks between the Samba server and the NT 860 860 client can cause this problem. Make sure that these are consistent for both client and server. 861 </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id3 31569"></a>Account Disabled</h3></div></div></div><p>“<span class="quote">When I attempt to log in to a Samba domain from a NT4/W200x workstation,861 </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id354209"></a>Account Disabled</h3></div></div></div><p>“<span class="quote">When I attempt to log in to a Samba domain from a NT4/W200x workstation, 862 862 I get a message about my account being disabled.</span>”</p><p> 863 863 Enable the user accounts with <strong class="userinput"><code>smbpasswd -e <em class="replaceable"><code>username</code></em> 864 864 </code></strong>. This is normally done as an account is created. 865 </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id3 31595"></a>Domain Controller Unavailable</h3></div></div></div><p>“<span class="quote">Until a few minutes after Samba has started, clients get the error `Domain Controller Unavailable'</span>”</p><p>865 </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id354234"></a>Domain Controller Unavailable</h3></div></div></div><p>“<span class="quote">Until a few minutes after Samba has started, clients get the error `Domain Controller Unavailable'</span>”</p><p> 866 866 A domain controller has to announce its role on the network. This usually takes a while. Be patient for up to 15 minutes, 867 867 then try again. 868 </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id3 31611"></a>Cannot Log onto Domain Member Workstation After Joining Domain</h3></div></div></div><p>869 <a class="indexterm" name="id3 31619"></a>870 <a class="indexterm" name="id3 31626"></a>868 </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id354251"></a>Cannot Log onto Domain Member Workstation After Joining Domain</h3></div></div></div><p> 869 <a class="indexterm" name="id354259"></a> 870 <a class="indexterm" name="id354266"></a> 871 871 After successfully joining the domain, user logons fail with one of two messages: one to the 872 872 effect that the domain controller cannot be found; the other claims that the account does not … … 885 885 </p><p> 886 886 It is important that these be set consistently with the Samba-3 server settings. 887 </p></div></div><div class="footnotes"><br><hr width="100" align="left"><div class="footnote"><p><sup>[<a name="ftn.id3 28934" href="#id328934">1</a>] </sup>See also <ahref="passdb.html" title="Chapter 11. Account Information Databases">Account Information888 Databases</a>.</p>.</div><div class="footnote"><p><sup>[<a name="ftn.id3 29384" href="#id329384">2</a>] </sup>See <ahref="NetworkBrowsing.html" title="Chapter 10. Network Browsing">Network Browsing</a>, and889 <a href="integrate-ms-networks.html" title="Chapter 29. Integrating MS Windows Networks with Samba">Integrating MS Windows Networks with Samba</a>.</p></div><div class="footnote"><p><sup>[<a name="ftn.id329659" href="#id329659">3</a>] </sup>See <ahref="NetworkBrowsing.html" title="Chapter 10. Network Browsing">Network887 </p></div></div><div class="footnotes"><br><hr width="100" align="left"><div class="footnote"><p><sup>[<a name="ftn.id351582" href="#id351582" class="para">1</a>] </sup>See also <a class="link" href="passdb.html" title="Chapter 11. Account Information Databases">Account Information 888 Databases</a>.</p>.</div><div class="footnote"><p><sup>[<a name="ftn.id352035" href="#id352035" class="para">2</a>] </sup>See <a class="link" href="NetworkBrowsing.html" title="Chapter 10. Network Browsing">Network Browsing</a>, and 889 <a class="link" href="integrate-ms-networks.html" title="Chapter 29. Integrating MS Windows Networks with Samba">Integrating MS Windows Networks with Samba</a>.</p></div><div class="footnote"><p><sup>[<a name="ftn.id352318" href="#id352318" class="para">3</a>] </sup>See <a class="link" href="NetworkBrowsing.html" title="Chapter 10. Network Browsing">Network 890 890 Browsing</a>.</p></div></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="ServerType.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="type.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="samba-bdc.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">Chapter 3. Server Types and Security Modes </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> Chapter 5. Backup Domain Control</td></tr></table></div></body></html>
Note:
See TracChangeset
for help on using the changeset viewer.
