<chapter id="samba-pdc">
-
<chapterinfo>
- &author.jerry;
&author.jht;
+ &author.jerry;
<author>
<firstname>David</firstname><surname>Bannon</surname>
<affiliation>
<address><email>dbannon@samba.org</email></address>
</affiliation>
</author>
- <pubdate> (26 Apr 2001) </pubdate>
</chapterinfo>
-<title>
-Samba as an NT4 or Win2k Primary Domain Controller
-</title>
-
-
-<sect1>
-<title>Prerequisite Reading</title>
+<title>Domain Control</title>
+<formalpara><title><emphasis>The Essence of Learning:</emphasis></title>
<para>
-Before you continue reading in this chapter, please make sure
-that you are comfortable with configuring basic files services
-in smb.conf and how to enable and administer password
-encryption in Samba. Theses two topics are covered in the
-&smb.conf; manpage.
+There are many who approach MS Windows networking with incredible misconceptions.
+That's OK, because it give the rest of us plenty of opportunity to be of assistance.
+Those who really want help would be well advised to become familiar with information
+that is already available.
</para>
+</formalpara>
-
-</sect1>
-
-
-
-<sect1>
-<title>
-Background
-</title>
+<para>
+The reader is advised NOT to tackle this section without having first understood
+and mastered some basics. MS Windows networking is not particularly forgiving of
+misconfiguration. Users of MS Windows networking are likely to complain bitterly
+of persistent niggles that may be caused by broken network or system configuration.
+To a great many people however, MS Windows networking starts with a domain controller
+that in some magical way is expected to solve all ills.
+</para>
<para>
-This article outlines the steps necessary for configuring Samba as a PDC.
-It is necessary to have a working Samba server prior to implementing the
-PDC functionality.
+From the Samba mailing list one can readilly identify many common networking issues.
+If you are not clear on the following subjects, then it will do much good to read the
+sections of this HOWTO that deal with it. These are the most common causes of MS Windows
+networking problems:
</para>
<itemizedlist>
- <listitem><para>
- Domain logons for Windows NT 4.0 / 200x / XP Professional clients.
- </para></listitem>
-
- <listitem><para>
- Placing Windows 9x / Me clients in user level security
- </para></listitem>
-
- <listitem><para>
- Retrieving a list of users and groups from a Samba PDC to
- Windows 9x / Me / NT / 200x / XP Professional clients
- </para></listitem>
-
- <listitem><para>
- Roaming Profiles
- </para></listitem>
-
- <listitem><para>
- Network/System Policies
- </para></listitem>
+ <listitem><para>Basic TCP/IP configuration</para></listitem>
+ <listitem><para>NetBIOS name resolution</para></listitem>
+ <listitem><para>Authentication configuration</para></listitem>
+ <listitem><para>User and Group configuration</para></listitem>
+ <listitem><para>Basic File and Directory Permission Control in Unix/Linux</para></listitem>
+ <listitem><para>Understanding of how MS Windows clients interoperate in a network
+ environment</para></listitem>
</itemizedlist>
-<note>
<para>
-Roaming Profiles and System/Network policies are advanced network administration topics
-that are covered separately in this document.
+Do not be put off, on the surface of it MS Windows networking seems so simple that any fool
+can do it. In fact, it is not a good idea to set up an MS Windows network with
+inadequate training and preparation. But let's get our first indelible principle out of the
+way: <emphasis>It is perfectly OK to make mistakes!</emphasis> In the right place and at
+the right time, mistakes are the essence of learning. It is <emphasis>very much</emphasis>
+not Ok to make mistakes that cause loss of productivity and impose an avoidable financial
+burden on an organisation.
</para>
-</note>
<para>
-The following functionalities are new to the Samba 3.0 release:
+Where is the right place to make mistakes? Only out of harms' way! If you are going to
+make mistakes, then please do this on a test network, away from users and in such a way as
+to not inflict pain on others. Do your learning on a test network.
</para>
-<itemizedlist>
- <listitem><para>
- Windows NT 4 domain trusts
- </para></listitem>
-
- <listitem><para>
- Adding users via the User Manager for Domains
- </para></listitem>
-</itemizedlist>
+<sect1>
+<title>Features and Benefits</title>
<para>
-The following functionalities are NOT provided by Samba 3.0:
+The following functionalities are new to the Samba-3 release:
</para>
<itemizedlist>
<listitem><para>
- SAM replication with Windows NT 4.0 Domain Controllers
- (i.e. a Samba PDC and a Windows NT BDC or vice versa)
+ Windows NT4 domain trusts
</para></listitem>
<listitem><para>
- Acting as a Windows 2000 Domain Controller (i.e. Kerberos and
- Active Directory)
+ Adding users via the User Manager for Domains or via the Windows 200x Microsoft
+ Management Console.
</para></listitem>
-</itemizedlist>
-<para>
-Please note that Windows 9x / Me / XP Home clients are not true members of a domain
-for reasons outlined in this article. Therefore the protocol for
-support of Windows 9x-style domain logons is completely different
-from NT4 / Win2k type domain logons and has been officially supported for some
-time.
-</para>
-
-<para><emphasis>
-MS Windows XP Home edition is NOT able to join a domain and does not permit
-the use of domain logons.</emphasis>
-</para>
-
-
-<para>
-Implementing a Samba PDC can basically be divided into 3 broad
-steps.
-</para>
-
-<orderedlist numeration="arabic">
<listitem><para>
- Configuring the Samba PDC
- </para></listitem>
-
- <listitem><para>
- Creating machine trust accounts and joining clients to the domain
+ Introduces replaceable and multiple user account (authentication)
+ back ends. In the case where the back end is placed in an LDAP database
+ Samba-3 confers the benefits of a back end that can be distributed, replicated,
+ and highly scalable.
</para></listitem>
<listitem><para>
- Adding and managing domain user accounts
+ Implements full Unicode support. This simplifies cross locale internationalisation
+ support. It also opens up the use of protocols that samba-2.2.x had but could not use due
+ to the need to fully support Unicode.
</para></listitem>
-</orderedlist>
-
-<para>
-There are other minor details such as user profiles, system
-policies, etc... However, these are not necessarily specific
-to a Samba PDC as much as they are related to Windows NT networking
-concepts.
-</para>
-
-</sect1>
-
-
-<sect1>
-<title>Configuring the Samba Domain Controller</title>
-
-<para>
-The first step in creating a working Samba PDC is to
-understand the parameters necessary in smb.conf. Here we
-attempt to explain the parameters that are covered in
-the &smb.conf; man page.
-</para>
-
-<para>
-Here is an example &smb.conf; for acting as a PDC:
-</para>
-
-<para><programlisting>
-[global]
- ; Basic server settings
- <ulink url="smb.conf.5.html#NETBIOSNAME">netbios name</ulink> = <replaceable>POGO</replaceable>
- <ulink url="smb.conf.5.html#WORKGROUP">workgroup</ulink> = <replaceable>NARNIA</replaceable>
-
- ; User and Machine Account Backends
- ; Choices are: tdbsam, tdbsam_nua, smbpasswd, smbpasswd_nua, ldapsam, ldapsam_nua, ...
- ; mysqlsam, xmlsam, guest
- <ulink url="smb.conf.5.html#PASSDBBACKEND">passdb backend</ulink> = ldapsam, guest
-
- ; we should act as the domain and local master browser
- <ulink url="smb.conf.5.html#OSLEVEL">os level</ulink> = 64
- <ulink url="smb.conf.5.html#PERFERREDMASTER">preferred master</ulink> = yes
- <ulink url="smb.conf.5.html#DOMAINMASTER">domain master</ulink> = yes
- <ulink url="smb.conf.5.html#LOCALMASTER">local master</ulink> = yes
-
- ; security settings (must user security = user)
- <ulink url="smb.conf.5.html#SECURITYEQUALSUSER">security</ulink> = user
-
- ; encrypted passwords are a requirement for a PDC
- <ulink url="smb.conf.5.html#ENCRYPTPASSWORDS">encrypt passwords</ulink> = yes
-
- ; support domain logons
- <ulink url="smb.conf.5.html#DOMAINLOGONS">domain logons</ulink> = yes
-
- ; where to store user profiles?
- <ulink url="smb.conf.5.html#LOGONPATH">logon path</ulink> = \\%N\profiles\%u
-
- ; where is a user's home directory and where should it be mounted at?
- <ulink url="smb.conf.5.html#LOGONDRIVE">logon drive</ulink> = H:
- <ulink url="smb.conf.5.html#LOGONHOME">logon home</ulink> = \\homeserver\%u
-
- ; specify a generic logon script for all users
- ; this is a relative **DOS** path to the [netlogon] share
- <ulink url="smb.conf.5.html#LOGONSCRIPT">logon script</ulink> = logon.cmd
-
-; necessary share for domain controller
-[netlogon]
- <ulink url="smb.conf.5.html#PATH">path</ulink> = /usr/local/samba/lib/netlogon
- <ulink url="smb.conf.5.html#READONLY">read only</ulink> = yes
- <ulink url="smb.conf.5.html#WRITELIST">write list</ulink> = <replaceable>ntadmin</replaceable>
-
-; share for storing user profiles
-[profiles]
- <ulink url="smb.conf.5.html#PATH">path</ulink> = /export/smb/ntprofile
- <ulink url="smb.conf.5.html#READONLY">read only</ulink> = no
- <ulink url="smb.conf.5.html#CREATEMASK">create mask</ulink> = 0600
- <ulink url="smb.conf.5.html#DIRECTORYMASK">directory mask</ulink> = 0700
-</programlisting></para>
-
-<note><para>
-The above parameters make for a full set of parameters that may define the server's mode
-of operation. The following parameters are the essentials alone:
-
-<programlisting>
- workgroup = NARNIA
- domain logons = Yes
- security = User
-</programlisting>
-
-The additional parameters shown in the longer listing above just makes for a
-more complete environment.
-</para></note>
+</itemizedlist>
<para>
-There are a couple of points to emphasize in the above configuration.
+The following functionalities are NOT provided by Samba-3:
</para>
<itemizedlist>
<listitem><para>
- Encrypted passwords must be enabled. For more details on how
- to do this, refer to <link linkend="passdb">the User Database chapter</link>.
- </para></listitem>
-
- <listitem><para>
- The server must support domain logons and a
- <filename>[netlogon]</filename> share
+ SAM replication with Windows NT4 Domain Controllers
+ (i.e. a Samba PDC and a Windows NT BDC or vice versa)
</para></listitem>
<listitem><para>
- The server must be the domain master browser in order for Windows
- client to locate the server as a DC. Please refer to the various
- Network Browsing documentation included with this distribution for
- details.
+ Acting as a Windows 2000 Domain Controller (i.e. Kerberos and
+ Active Directory) - In point of fact, Samba-3 DOES have some
+ Active Directory Domain Control ability that is at this time
+ purely experimental <emphasis>AND</emphasis> that is certain
+ to change as it becomes a fully supported feature some time
+ during the samba-3 (or later) life cycle.
</para></listitem>
-</itemizedlist>
+</itemizedlist>
<para>
-Samba 3.0 offers a complete implementation of group mapping
-between Windows NT groups and Unix groups (this is really quite
-complicated to explain in a short space).
+Windows 9x / Me / XP Home clients are not true members of a domain for reasons outlined
+in this chapter. The protocol for support of Windows 9x / Me style network (domain) logons
+is completely different from NT4 / Win2k type domain logons and has been officially supported
+for some time. These clients use the old LanMan Network Logon facilities that are supported
+in Samba since approximately the samba-1.9.15 series.
</para>
-</sect1>
-
-
-<sect1>
-<title>Creating Machine Trust Accounts and Joining Clients to the Domain</title>
-
-<para>
-A machine trust account is a Samba account that is used to
-authenticate a client machine (rather than a user) to the Samba
-server. In Windows terminology, this is known as a "Computer
-Account."</para>
-
<para>
-The password of a machine trust account acts as the shared secret for
-secure communication with the Domain Controller. This is a security
-feature to prevent an unauthorized machine with the same NetBIOS name
-from joining the domain and gaining access to domain user/group
-accounts. Windows NT, 200x, XP Professional clients use machine trust
-accounts, but Windows 9x / Me / XP Home clients do not. Hence, a
-Windows 9x / Me / XP Home client is never a true member of a domain
-because it does not possess a machine trust account, and thus has no
-shared secret with the domain controller.
+Samba-3 has an implementation of group mapping between Windows NT groups
+and Unix groups (this is really quite complicated to explain in a short space) this is
+discussed more fully in a chapter dedicated to this topic..
</para>
-<para>A Windows PDC stores each machine trust account in the Windows
-Registry. A Samba-3 PDC also has to store machine trust account information
-in a suitable backend data store. With Samba-3 there can be multiple back-ends
-for this including:
+<para>
+A Samba-3, like an MS Windows NT4 PDC or a Windows 200x Active Directory, needs to store
+user and machine trust account information in a suitable backend data store. With Samba-3
+there can be multiple back-ends for this including:
</para>
<itemizedlist>
directory (default is /usr/local/samba/lib/private or on linux /etc/samba).
</para></listitem>
- <listitem><para>
- <emphasis>smbpasswd_nua</emphasis> - This file is independant of the
- system wide user accounts. The use of this back-end option requires
- specification of the "non unix account range" option also. It is called
- smbpasswd and will be located in the <filename>private</filename> directory.
- </para></listitem>
-
<listitem><para>
<emphasis>tdbsam</emphasis> - a binary database backend that will be
stored in the <emphasis>private</emphasis> directory in a file called
<emphasis>passwd.tdb</emphasis>. The key benefit of this binary format
file is that it can store binary objects that can not be accomodated
- in the traditional plain text smbpasswd file.
- </para></listitem>
-
- <listitem><para>
- <emphasis>tdbsam_nua</emphasis> like the smbpasswd_nua option above, this
- file allows the creation of arbitrary user and machine accounts without
- requiring that account to be added to the system (/etc/passwd) file. It
- too requires the specification of the "non unix account range" option
- in the [globals] section of the &smb.conf; file.
+ in the traditional plain text smbpasswd file. These permit the extended
+ account controls that MS Windows NT4 and later also have.
</para></listitem>
<listitem><para>
<emphasis>ldapsam</emphasis> - An LDAP based back-end. Permits the
- LDAP server to be specified. eg: ldap://localhost or ldap://frodo.murphy.com
+ LDAP server to be specified. eg: ldap://localhost or ldap://frodo.murphy.com.
+ Like the tdbsam, ldapsam permits the storing of extended account attributes
+ for control of things like: Permitted access times, password activation and
+ expiry, permitted points of access (workstation names), per user profile
+ location, and much more.
</para></listitem>
<listitem><para>
- <emphasis>ldapsam_nua</emphasis> - LDAP based back-end with no unix
- account requirement, like smbpasswd_nua and tdbsam_nua above.
+ <emphasis>ldapsam_compat</emphasis> - An LDAP back-end that maintains backwards
+ compatibility with the behaviour of samba-2.2.x. You should use this in the process
+ of mirgrating from samba-2.2.x to samba-3 if you do not want to rebuild your LDAP
+ database.
</para></listitem>
</itemizedlist>
-<para>Read the chapter about the <link linkend="passdb">User Database</link>
-for details.</para>
+<para>
+Read the chapter about the <link linkend="passdb">User Database</link> for details
+regarding the choices available and how to configure them.
+</para>
<note><para>
-The new tdbsam and ldapsam account backends store vastly more information than
+The new tdbsam and ldapsam account backends store substantially more information than
smbpasswd is capable of. The new backend database includes capacity to specify
per user settings for many parameters, over-riding global settings given in the
<filename>smb.conf</filename> file. eg: logon drive, logon home, logon path, etc.
+Thus, with samba-3 it is possible to have a default system configuration for profiles,
+and on a per user basis to over-ride this for those users who should not be subject
+to the default configuration.
</para></note>
-<para>
-A Samba PDC, however, stores each machine trust account in two parts,
-as follows:
+</sect1>
-<itemizedlist>
- <listitem><para>A Samba account, stored in the same location as user
- LanMan and NT password hashes (currently
- <filename>smbpasswd</filename>). The Samba account
- possesses and uses only the NT password hash.</para></listitem>
-
- <listitem><para>A corresponding Unix account, typically stored in
- <filename>/etc/passwd</filename>. (Future releases will alleviate the need to
- create <filename>/etc/passwd</filename> entries.) </para></listitem>
-</itemizedlist>
-</para>
+<sect1>
+<title>Basics of Domain Control</title>
<para>
-There are two ways to create machine trust accounts:
+Over the years public perceptions of what Domain Control really is has taken on an
+almost mystical nature. Before we branch into a brief overview of Domain Control
+there are three basic types of domain controllers:
</para>
-<itemizedlist>
- <listitem><para> Manual creation. Both the Samba and corresponding
- Unix account are created by hand.</para></listitem>
-
- <listitem><para> "On-the-fly" creation. The Samba machine trust
- account is automatically created by Samba at the time the client
- is joined to the domain. (For security, this is the
- recommended method.) The corresponding Unix account may be
- created automatically or manually. </para>
- </listitem>
+<sect2>
+<title>Domain Controller Types</title>
+<itemizedlist>
+ <listitem><para>Primary Domain Controller</para></listitem>
+ <listitem><para>Backup Domain Controller</para></listitem>
+ <listitem><para>ADS Domain Controller</para></listitem>
</itemizedlist>
-<sect2>
-<title>Manual Creation of Machine Trust Accounts</title>
-
<para>
-The first step in manually creating a machine trust account is to
-manually create the corresponding Unix account in
-<filename>/etc/passwd</filename>. This can be done using
-<command>vipw</command> or other 'add user' command that is normally
-used to create new Unix accounts. The following is an example for a
-Linux based Samba server:
+The <emphasis>Primary Domain Controller</emphasis> or PDC plays an important role in the MS
+Windows NT4 and Windows 200x Domain Control architecture, but not in the manner that so many
+expect. There is folk lore that dictates that because of it's role in the MS Windows
+network that the PDC should be the most powerful and most capable machine in the network.
+As strange as it may seem to say this here, good over all network performance dictates that
+the entire infrastructure needs to be balanced. It is advisable to invest more in the Backup
+Domain Controllers and Stand-Alone (or Domain Member) servers than in the PDC.
</para>
<para>
- <prompt>root# </prompt><command>/usr/sbin/useradd -g 100 -d /dev/null -c <replaceable>"machine
-nickname"</replaceable> -s /bin/false <replaceable>machine_name</replaceable>$ </command>
+In the case of MS Windows NT4 style domaines it is the PDC seeds the Domain Control database,
+a part of the Windows registry called the SAM (Security Accounts Management). It plays a key
+part in NT4 type domain user authentication and in synchronisation of the domain authentication
+database with Backup Domain Controllers.
</para>
+
<para>
-<prompt>root# </prompt><command>passwd -l <replaceable>machine_name</replaceable>$</command>
+With MS Windows 200x Server based Active Directory domains, one domain controller seeds a potential
+hierachy of domain controllers, each with their own area of delegated control. The master domain
+controller has the ability to override any down-stream controller, but a down-line controller has
+control only over it's down-line. With Samba-3 this functionality can be implemented using an
+LDAP based user and machine account back end.
</para>
-<para>On *BSD systems, this can be done using the 'chpass' utility:</para>
-
<para>
-<prompt>root# </prompt><command>chpass -a "<replaceable>machine_name</replaceable>$:*:101:100::0:0:Workstation <replaceable>machine_name</replaceable>:/dev/null:/sbin/nologin"</command>
+New to Samba-3 is the ability to use a back-end database that holds the same type of data as
+the NT4 style SAM (Security Account Manager) database (one of the registry files).
+The samba-3 SAM can be specified via the smb.conf file parameter
+<emphasis>passwd backend</emphasis> and valid options include
+<emphasis>smbpasswd, tdbsam, ldapsam, nisplussam, xmlsam, mysqlsam, plugin, guest</emphasis>.
</para>
<para>
-The <filename>/etc/passwd</filename> entry will list the machine name
-with a "$" appended, won't have a password, will have a null shell and no
-home directory. For example a machine named 'doppy' would have an
-<filename>/etc/passwd</filename> entry like this:
+The <emphasis>Backup Domain Controller</emphasis> or BDC plays a key role in servicing network
+authentication requests. The BDC is biased to answer logon requests in preference to the PDC.
+On a network segment that has a BDC and a PDC the BDC will be most likely to service network
+logon requests. The PDC will answer network logon requests when the BDC is too busy (high load).
+A BDC can be promoted to a PDC. If the PDC is on line at the time that the BDC is promoted to
+PDC the previous PDC is automatically demoted to a BDC. With Samba-3 this is NOT an automatic
+operation, the PDB and BDC must be manually configured and changes need to be made likewise.
</para>
-<para><programlisting>
-doppy$:x:505:501:<replaceable>machine_nickname</replaceable>:/dev/null:/bin/false
-</programlisting></para>
-
<para>
-Above, <replaceable>machine_nickname</replaceable> can be any
-descriptive name for the client, i.e., BasementComputer.
-<replaceable>machine_name</replaceable> absolutely must be the NetBIOS
-name of the client to be joined to the domain. The "$" must be
-appended to the NetBIOS name of the client or Samba will not recognize
-this as a machine trust account.
+With MS Windows NT4 it is an install time decision what type of machine the server will be.
+It is possible to change the promote a BDC to a PDC and vica versa only, but the only way
+to convert a domain controller to a domain member server or a stand-alone server is to
+reinstall it. The install time choices offered are:
</para>
+<itemizedlist>
+ <listitem><para>Primary Domain Controller - The one that seeds the domain SAM</para></listitem>
+ <listitem><para>Backup Domain Controller - One that obtains a copy of the domain SAM</para></listitem>
+ <listitem><para>Domain Controller - One that has NO copy of the domain SAM, rather it obtains authentication from a Domain Controller for all access controls.</para></listitem>
+ <listitem><para>Stand-Alone Server - One that plays NO part is SAM synchronisation, has it's own authentication database and plays no role in Domain security.</para></listitem>
+</itemizedlist>
<para>
-Now that the corresponding Unix account has been created, the next step is to create
-the Samba account for the client containing the well-known initial
-machine trust account password. This can be done using the <ulink
-url="smbpasswd.8.html"><command>smbpasswd(8)</command></ulink> command
-as shown here:
+With MS Windows 2000 the configuration of domain control is done after the server has been
+installed. Samba-3 is capable of acting fully as a native member of a Windows 200x server
+Active Directory domain.
</para>
<para>
-<prompt>root# </prompt><userinput>smbpasswd -a -m <replaceable>machine_name</replaceable></userinput>
+New to Samba-3 is the ability to function fully as an MS Windows NT4 style Domain Controller,
+excluding the SAM replication components. However, please be aware that Samba-3 support the
+MS Windows 200x domain control protcols also.
</para>
<para>
-where <replaceable>machine_name</replaceable> is the machine's NetBIOS
-name. The RID of the new machine account is generated from the UID of
-the corresponding Unix account.
+At this time Samba-3 is capable of acting as an <emphasis>ADS Domain Controller</emphasis> but
+in only a limited and experimental manner. This functionality should not be depended upon
+until the samba-team offers formal support for it. At such a time, the documentation will
+be revised to duely reflect all configuration and management requirements.
</para>
-<warning>
- <title>Join the client to the domain immediately</title>
-
- <para>
- Manually creating a machine trust account using this method is the
- equivalent of creating a machine trust account on a Windows NT PDC using
- the "Server Manager". From the time at which the account is created
- to the time which the client joins the domain and changes the password,
- your domain is vulnerable to an intruder joining your domain using
- a machine with the same NetBIOS name. A PDC inherently trusts
- members of the domain and will serve out a large degree of user
- information to such clients. You have been warned!
- </para>
-</warning>
</sect2>
-
<sect2>
-<title>"On-the-Fly" Creation of Machine Trust Accounts</title>
+<title>Preparing for Domain Control</title>
<para>
-The second (and recommended) way of creating machine trust accounts is
-simply to allow the Samba server to create them as needed when the client
-is joined to the domain. </para>
-
-<para>Since each Samba machine trust account requires a corresponding
-Unix account, a method for automatically creating the
-Unix account is usually supplied; this requires configuration of the
-<ulink url="smb.conf.5.html#ADDMACHINESCRIPT">add machine script</ulink>
-option in <filename>smb.conf</filename>. This
-method is not required, however; corresponding Unix accounts may also
-be created manually.
+The following are necessary for configuring Samba-3 as an MS Windows NT4 style PDC for MS Windows
+NT4 / 200x / XP clients.
</para>
+<orderedlist numeration="arabic">
+ <listitem><para>
+ Configuration of basic TCP/IP and MS Windows Networking
+ </para></listitem>
-<para>Below is an example for a RedHat 6.2 Linux system.
-</para>
+ <listitem><para>
+ Correct designation of the Server Role (<emphasis>security = user</emphasis>)
+ </para></listitem>
-<para><programlisting>
-[global]
- # <...remainder of parameters...>
- add machine script = /usr/sbin/useradd -d /dev/null -g 100 -s /bin/false -M %u
-</programlisting></para>
+ <listitem><para>
+ Consistent configuration of Name Resolution (See chapter on Browsing and on
+ MS Windows network Integration)
+ </para></listitem>
-</sect2>
+ <listitem><para>
+ Domain logons for Windows NT4 / 200x / XP Professional clients
+ </para></listitem>
+
+ <listitem><para>
+ Configuration of Roaming Profiles or explicit configuration to force local profile usage
+ </para></listitem>
+
+ <listitem><para>
+ Configuration of Network/System Policies
+ </para></listitem>
+ <listitem><para>
+ Adding and managing domain user accounts
+ </para></listitem>
-<sect2><title>Joining the Client to the Domain</title>
+ <listitem><para>
+ Configuring MS Windows client machines to become domain members
+ </para></listitem>
+</orderedlist>
<para>
-The procedure for joining a client to the domain varies with the
-version of Windows.
+The following provisions are required to serve MS Windows 9x / Me Clients:
</para>
-<itemizedlist>
-<listitem><para><emphasis>Windows 2000</emphasis></para>
-
- <para>
- When the user elects to join the client to a domain, Windows prompts for
- an account and password that is privileged to join the domain. A Samba administrative
- account (i.e., a Samba account that has root privileges on the Samba server) must be
- entered here; the operation will fail if an ordinary user account is given.
- The password for this account should be set to a different password than the associated
- <filename>/etc/passwd</filename> entry, for security reasons.
- </para>
+<orderedlist>
+ <listitem><para>
+ Configuration of basic TCP/IP and MS Windows Networking
+ </para></listitem>
- <para>
- The session key of the Samba administrative account acts as an
- encryption key for setting the password of the machine trust
- account. The machine trust account will be created on-the-fly, or
- updated if it already exists.
- </para>
+ <listitem><para>
+ Correct designation of the Server Role (<emphasis>security = user</emphasis>)
+ </para></listitem>
-</listitem>
+ <listitem><para>
+ Network Logon Configuration (Since Windows 9x / XP Home are not technically domain
+ members, they do not really particpate in the security aspects of Domain logons as such)
+ </para></listitem>
-<listitem><para><emphasis>Windows NT</emphasis></para>
+ <listitem><para>
+ Roaming Profile Configuration
+ </para></listitem>
- <para> If the machine trust account was created manually, on the
- Identification Changes menu enter the domain name, but do not
- check the box "Create a Computer Account in the Domain." In this case,
- the existing machine trust account is used to join the machine to
- the domain.</para>
+ <listitem><para>
+ Configuration of System Policy handling
+ </para></listitem>
- <para> If the machine trust account is to be created
- on-the-fly, on the Identification Changes menu enter the domain
- name, and check the box "Create a Computer Account in the Domain." In
- this case, joining the domain proceeds as above for Windows 2000
- (i.e., you must supply a Samba administrative account when
- prompted).</para>
-</listitem>
+ <listitem><para>
+ Installation of the Network driver "Client for MS Windows Networks" and configuration
+ to log onto the domain
+ </para></listitem>
-<listitem><para><emphasis>Samba</emphasis></para>
- <para>Joining a samba client to a domain is documented in
- the <link linkend="domain-member">Domain Member</link> chapter.
-</para></listitem>
-</itemizedlist>
+ <listitem><para>
+ Placing Windows 9x / Me clients in user level security - if it is desired to allow
+ all client share access to be controlled according to domain user / group identities.
+ </para></listitem>
-</sect2>
-</sect1>
+ <listitem><para>
+ Adding and managing domain user accounts
+ </para></listitem>
+</orderedlist>
-<sect1>
-<title>Common Problems and Errors</title>
+<note><para>
+Roaming Profiles and System/Network policies are advanced network administration topics
+that are covered separately in this document. However, these are not necessarily specific
+to a Samba PDC as much as they are related to Windows NT networking concepts.
+</para></note>
-<sect2>
-<title>I cannot include a '$' in a machine name</title>
<para>
-A 'machine name' in (typically) <filename>/etc/passwd</filename>
-of the machine name with a '$' appended. FreeBSD (and other BSD
-systems?) won't create a user with a '$' in their name.
+A Domain Controller is an SMB/CIFS server that:
</para>
-<para>
-The problem is only in the program used to make the entry. Once made, it works perfectly.
-Create a user without the '$' using <command>vipw</command> to edit the entry, adding
-the '$'. Or create the whole entry with vipw if you like, make sure you use a unique User ID!
-</para>
-</sect2>
+<itemizedlist>
+ <listitem><para>
+ Advertises and registers itself as a Domain Controller (Through NetBIOS broadcasts
+ as well as by way of name registrations either by Mailslot Broadcasts over UDP broadcast,
+ to a WINS server over UDP unicast, or via DNS and Active Directory)
+ </para></listitem>
-<sect2>
-<title>I get told "You already have a connection to the Domain...."
-or "Cannot join domain, the credentials supplied conflict with an
-existing set.." when creating a machine trust account.</title>
+ <listitem><para>
+ Provides the NETLOGON service (actually a collection of services that runs over
+ a number of protocols. These include the LanMan Logon service, the Netlogon service,
+ the Local Security Account service, and variations of them)
+ </para></listitem>
-<para>
-This happens if you try to create a machine trust account from the
-machine itself and already have a connection (e.g. mapped drive)
-to a share (or IPC$) on the Samba PDC. The following command
-will remove all network drive connections:
-</para>
+ <listitem><para>
+ Provides a share called NETLOGON
+ </para></listitem>
+</itemizedlist>
<para>
-<prompt>C:\WINNT\></prompt> <command>net use * /d</command>
+For samba to provide these is rather easy to configure. Each Samba Domain Controller must provide
+the NETLOGON service which samba calls the <emphasis>domain logons</emphasis> functionality
+(after the name of the parameter in the &smb.conf; file). Additionally, one (1) server in a Samba-3
+Domain must advertise itself as the domain master browser. This causes the Primary Domain Controller
+to claim domain specific NetBIOS name that identifies it as a domain master browser for its given
+domain/workgroup. Local master browsers in the same domain/workgroup on broadcast-isolated subnets
+then ask for a complete copy of the browse list for the whole wide area network. Browser clients
+will then contact their local master browser, and will receive the domain-wide browse list,
+instead of just the list for their broadcast-isolated subnet.
</para>
-<para>
-Further, if the machine is already a 'member of a workgroup' that
-is the same name as the domain you are joining (bad idea) you will
-get this message. Change the workgroup name to something else, it
-does not matter what, reboot, and try again.
-</para>
</sect2>
+</sect1>
-<sect2>
-<title>The system can not log you on (C000019B)....</title>
+<sect1>
+<title>Domain Control - Example Configuration</title>
-<para>I joined the domain successfully but after upgrading
-to a newer version of the Samba code I get the message, "The system
-can not log you on (C000019B), Please try again or consult your
-system administrator" when attempting to logon.
+<para>
+The first step in creating a working Samba PDC is to understand the parameters necessary
+in &smb.conf;. Here we attempt to explain the parameters that are covered in
+the &smb.conf; man page.
</para>
<para>
-This occurs when the domain SID stored in the secrets.tdb database
-is changed. The most common cause of a change in domain SID is when
-the domain name and/or the server name (netbios name) is changed.
-The only way to correct the problem is to restore the original domain
-SID or remove the domain client from the domain and rejoin. The domain
-SID may be reset using either the net or rpcclient utilities.
+Here is an example &smb.conf; for acting as a PDC:
</para>
-<para>
-The reset or change the domain SID you can use the net command as follows:
+<para><programlisting>
+ [global]
+ ; Basic server settings
+ <ulink url="smb.conf.5.html#NETBIOSNAME">netbios name</ulink> = <replaceable>POGO</replaceable>
+ <ulink url="smb.conf.5.html#WORKGROUP">workgroup</ulink> = <replaceable>NARNIA</replaceable>
+
+ ; User and Machine Account Backends
+ ; Choices are: tdbsam, smbpasswd, ldapsam, mysqlsam, xmlsam, guest
+ <ulink url="smb.conf.5.html#PASSDBBACKEND">passdb backend</ulink> = ldapsam, guest
+
+ ; we should act as the domain and local master browser
+ <ulink url="smb.conf.5.html#OSLEVEL">os level</ulink> = 64
+ <ulink url="smb.conf.5.html#PERFERREDMASTER">preferred master</ulink> = yes
+ <ulink url="smb.conf.5.html#DOMAINMASTER">domain master</ulink> = yes
+ <ulink url="smb.conf.5.html#LOCALMASTER">local master</ulink> = yes
+
+ ; security settings (must user security = user)
+ <ulink url="smb.conf.5.html#SECURITYEQUALSUSER">security</ulink> = user
+
+ ; encrypted passwords are a requirement for a PDC
+ <ulink url="smb.conf.5.html#ENCRYPTPASSWORDS">encrypt passwords</ulink> = yes
+
+ ; support domain logons
+ <ulink url="smb.conf.5.html#DOMAINLOGONS">domain logons</ulink> = yes
+
+ ; where to store user profiles?
+ <ulink url="smb.conf.5.html#LOGONPATH">logon path</ulink> = \\%N\profiles\%u
+
+ ; where is a user's home directory and where should it be mounted at?
+ <ulink url="smb.conf.5.html#LOGONDRIVE">logon drive</ulink> = H:
+ <ulink url="smb.conf.5.html#LOGONHOME">logon home</ulink> = \\homeserver\%u\winprofile
+
+ ; specify a generic logon script for all users
+ ; this is a relative **DOS** path to the [netlogon] share
+ <ulink url="smb.conf.5.html#LOGONSCRIPT">logon script</ulink> = logon.cmd
+
+ ; necessary share for domain controller
+ [netlogon]
+ <ulink url="smb.conf.5.html#PATH">path</ulink> = /usr/local/samba/lib/netlogon
+ <ulink url="smb.conf.5.html#READONLY">read only</ulink> = yes
+ <ulink url="smb.conf.5.html#WRITELIST">write list</ulink> = <replaceable>ntadmin</replaceable>
+
+ ; share for storing user profiles
+ [profiles]
+ <ulink url="smb.conf.5.html#PATH">path</ulink> = /export/smb/ntprofile
+ <ulink url="smb.conf.5.html#READONLY">read only</ulink> = no
+ <ulink url="smb.conf.5.html#CREATEMASK">create mask</ulink> = 0600
+ <ulink url="smb.conf.5.html#DIRECTORYMASK">directory mask</ulink> = 0700
+</programlisting></para>
+
+<note><para>
+The above parameters make for a full set of parameters that may define the server's mode
+of operation. The following parameters are the essentials alone:
<programlisting>
- net getlocalsid 'OLDNAME'
- net setlocalsid 'SID'
+ workgroup = NARNIA
+ domain logons = Yes
+ domain master = Yes
+ security = User
</programlisting>
+
+The additional parameters shown in the longer listing above just makes for a
+more complete environment.
+</para></note>
+
+<para>
+There are a couple of points to emphasize in the above configuration.
</para>
-</sect2>
+<itemizedlist>
+ <listitem><para>
+ Encrypted passwords must be enabled. For more details on how
+ to do this, refer to <link linkend="passdb">the User Database chapter</link>.
+ </para></listitem>
+
+ <listitem><para>
+ The server must support domain logons and have a
+ <filename>[netlogon]</filename> share
+ </para></listitem>
+
+ <listitem><para>
+ The server must be the domain master browser in order for Windows
+ client to locate the server as a DC. Please refer to the various
+ Network Browsing documentation included with this distribution for
+ details.
+ </para></listitem>
+</itemizedlist>
-<sect2>
-<title>The machine trust account for this computer either does not
-exist or is not accessible.</title>
+</sect1>
+
+<sect1>
+<title>Samba ADS Domain Control</title>
<para>
-When I try to join the domain I get the message "The machine account
-for this computer either does not exist or is not accessible". What's
-wrong?
+Samba-3 can behave and appear to MS Windows 200x and XP clients as an Active Directory Server.
+To do this, Configure samba as a Primary Domain Controller, use LDAP as the passdb backend,
+and configure Kerberos5. The problem with doing this is that samba-3 is NOT, despite this
+configuration, and Active Directory server and does NOT yet fully support all protocols needed
+to make this a possibility.
</para>
<para>
-This problem is caused by the PDC not having a suitable machine trust account.
-If you are using the <parameter>add machine script</parameter> method to create
-accounts then this would indicate that it has not worked. Ensure the domain
-admin user system is working.
+The best advice we can give at this time is - DO NOT DO THIS yet as it is NOT ready for
+production deployment.
</para>
+</sect1>
+
+<sect1>
+<title>Domain and Network Logon Configuration</title>
+
<para>
-Alternatively if you are creating account entries manually then they
-have not been created correctly. Make sure that you have the entry
-correct for the machine trust account in smbpasswd file on the Samba PDC.
-If you added the account using an editor rather than using the smbpasswd
-utility, make sure that the account name is the machine NetBIOS name
-with a '$' appended to it ( i.e. computer_name$ ). There must be an entry
-in both /etc/passwd and the smbpasswd file. Some people have reported
-that inconsistent subnet masks between the Samba server and the NT
-client have caused this problem. Make sure that these are consistent
-for both client and server.
+The subject of Network or Domain Logons is discussed here because it rightly forms
+an integral part of the essential functionality that is provided by a Domain Controller.
</para>
-</sect2>
<sect2>
-<title>When I attempt to login to a Samba Domain from a NT4/W2K workstation,
-I get a message about my account being disabled.</title>
+<title>Domain Network Logon Service</title>
<para>
-At first be ensure to enable the useraccounts with <command>smbpasswd -e
-%user%</command>, this is normally done, when you create an account.
+All Domain Controllers must run the netlogon service (<emphasis>domain logons</emphasis>
+in Samba. One Domain Controller must be configured with <emphasis>domain master = Yes</emphasis>
+(the Primary Domain Controller), on ALL Backup Domain Controllers <emphasis>domain master = No</emphasis>
+must be set.
</para>
-</sect2>
+<title>Example Configuration</title>
-</sect1>
+<programlisting>
+<title> A minimal configuration to support Domain Logons</title>
+<para>
+ [globals]
+ domain logons = Yes
+ domain master = (Yes on PDC, No on BDCs)
-<sect1>
-<title>Domain Control for Windows 9x/ME</title>
+ [netlogon]
+ comment = Network Logon Service
+ path = /var/lib/samba/netlogon
+ guest ok = Yes
+ browseable = No
+</para>
+</programlisting>
+
+<sect3>
+<title>The Special Case of Windows 9x / Me / XP Home</title>
<para>
A domain and a workgroup are exactly the same thing in terms of network
which are the focus of this section.
</para>
-
<para>
When an SMB client in a domain wishes to logon it broadcast requests for a
logon server. The first one to reply gets the job, and validates its
involved with domains.
</para>
-
<para>
Using these features you can make your clients verify their logon via
the Samba server; make clients run a batch file when they logon to
the network and download their preferences, desktop and start menu.
</para>
+<para><emphasis>
+MS Windows XP Home edition is NOT able to join a domain and does not permit
+the use of domain logons.
+</emphasis></para>
+
<para>
Before launching into the configuration instructions, it is
worthwhile to look at how a Windows 9x/ME client performs a logon:
<para>
The client then connects to the user's home share and searches for the
user's profile. As it turns out, you can specify the user's home share as
- a sharename and path. For example, \\server\fred\.profile.
+ a sharename and path. For example, \\server\fred\.winprofile.
If the profiles are found, they are implemented.
</para>
</listitem>
</listitem>
</orderedlist>
-
-<sect2>
-<title>Configuration Instructions: Network Logons</title>
-
<para>
-The main difference between a PDC and a Windows 9x logon
-server configuration is that
+The main difference between a PDC and a Windows 9x logon server configuration is that
</para>
<itemizedlist>
-
-<listitem><para>
-Password encryption is not required for a Windows 9x logon server.
-</para></listitem>
-
<listitem><para>
-Windows 9x/ME clients do not possess machine trust accounts.
-</para></listitem>
+ Password encryption is not required for a Windows 9x logon server.
+ </para></listitem>
+ <listitem><para>
+ Windows 9x/ME clients do not possess machine trust accounts.
+ </para></listitem>
</itemizedlist>
<para>
-Therefore, a Samba PDC will also act as a Windows 9x logon
-server.
+A Samba PDC will also act as a Windows 9x logon server.
</para>
+</sect3>
+</sect2>
-<warning>
-<title>security mode and master browsers</title>
+<sect2>
+<title>Security Mode and Master Browsers</title>
<para>
There are a few comments to make in order to tie up some
Therefore configuring a Samba box as a DC for a domain that
already by definition has a PDC is asking for trouble.
Therefore, you should always configure the Samba DC to be the DMB
-for its domain.
+for its domain and set <emphasis>security = user</emphasis>. This is the only
+officially supported mode of operation.
+</para>
+
+</sect2>
+
+</sect1>
+
+<sect1>
+<title>Common Problems and Errors</title>
+
+<sect2>
+<title>I cannot include a '$' in a machine name</title>
+<para>
+A 'machine name' in (typically) <filename>/etc/passwd</filename>
+of the machine name with a '$' appended. FreeBSD (and other BSD
+systems?) won't create a user with a '$' in their name.
+</para>
+
+<para>
+The problem is only in the program used to make the entry. Once made, it works perfectly.
+Create a user without the '$' using <command>vipw</command> to edit the entry, adding
+the '$'. Or create the whole entry with vipw if you like, make sure you use a unique User ID!
+</para>
+</sect2>
+
+<sect2>
+<title>I get told "You already have a connection to the Domain...."
+or "Cannot join domain, the credentials supplied conflict with an
+existing set.." when creating a machine trust account.</title>
+
+<para>
+This happens if you try to create a machine trust account from the
+machine itself and already have a connection (e.g. mapped drive)
+to a share (or IPC$) on the Samba PDC. The following command
+will remove all network drive connections:
+</para>
+
+<para>
+<prompt>C:\WINNT\></prompt> <command>net use * /d</command>
+</para>
+
+<para>
+Further, if the machine is already a 'member of a workgroup' that
+is the same name as the domain you are joining (bad idea) you will
+get this message. Change the workgroup name to something else, it
+does not matter what, reboot, and try again.
+</para>
+</sect2>
+
+<sect2>
+<title>The system can not log you on (C000019B)....</title>
+
+<para>I joined the domain successfully but after upgrading
+to a newer version of the Samba code I get the message, "The system
+can not log you on (C000019B), Please try again or consult your
+system administrator" when attempting to logon.
+</para>
+
+<para>
+This occurs when the domain SID stored in the secrets.tdb database
+is changed. The most common cause of a change in domain SID is when
+the domain name and/or the server name (netbios name) is changed.
+The only way to correct the problem is to restore the original domain
+SID or remove the domain client from the domain and rejoin. The domain
+SID may be reset using either the net or rpcclient utilities.
+</para>
+
+<para>
+The reset or change the domain SID you can use the net command as follows:
+
+<programlisting>
+ net getlocalsid 'OLDNAME'
+ net setlocalsid 'SID'
+</programlisting>
+</para>
+
+</sect2>
+
+<sect2>
+<title>The machine trust account for this computer either does not
+exist or is not accessible.</title>
+
+<para>
+When I try to join the domain I get the message "The machine account
+for this computer either does not exist or is not accessible". What's
+wrong?
+</para>
+
+<para>
+This problem is caused by the PDC not having a suitable machine trust account.
+If you are using the <parameter>add machine script</parameter> method to create
+accounts then this would indicate that it has not worked. Ensure the domain
+admin user system is working.
+</para>
+
+<para>
+Alternatively if you are creating account entries manually then they
+have not been created correctly. Make sure that you have the entry
+correct for the machine trust account in smbpasswd file on the Samba PDC.
+If you added the account using an editor rather than using the smbpasswd
+utility, make sure that the account name is the machine NetBIOS name
+with a '$' appended to it ( i.e. computer_name$ ). There must be an entry
+in both /etc/passwd and the smbpasswd file. Some people have reported
+that inconsistent subnet masks between the Samba server and the NT
+client have caused this problem. Make sure that these are consistent
+for both client and server.
+</para>
+</sect2>
+
+<sect2>
+<title>When I attempt to login to a Samba Domain from a NT4/W2K workstation,
+I get a message about my account being disabled.</title>
+
+<para>
+At first be ensure to enable the useraccounts with <command>smbpasswd -e
+%user%</command>, this is normally done, when you create an account.
</para>
-</warning>
</sect2>
</sect1>
git.samba.org / nivanova / samba-autobuild / .git / blobdiff