1 <chapter id="domain-member">
11 <title>Domain Membership</title>
14 Domain Membership is a subject of vital concern, Samba must be able to
15 participate as a member server in a Microsoft Domain security context, and
16 Samba must be capable of providing Domain machine member trust accounts,
17 otherwise it would not be capable of offering a viable option for many users.
21 This chapter covers background information pertaining to domain membership,
22 Samba configuration for it, and MS Windows client procedures for joining a
23 domain. Why is this necessary? Because both are areas in which there exists
24 within the current MS Windows networking world and particularly in the
25 UNIX/Linux networking and administration world, a considerable level of
26 mis-information, incorrect understanding, and a lack of knowledge. Hopefully
27 this chapter will fill the voids.
31 <title>Features and Benefits</title>
34 MS Windows workstations and servers that want to participate in domain security need to
35 be made Domain members. Participating in Domain security is often called
36 <emphasis>Single Sign On</emphasis> or <acronym>SSO</acronym> for short. This
37 chapter describes the process that must be followed to make a workstation
38 (or another server - be it an <application>MS Windows NT4 / 200x</application>
39 server) or a Samba server a member of an MS Windows Domain security context.
43 Samba-3 can join an MS Windows NT4 style domain as a native member server, an
44 MS Windows Active Directory Domain as a native member server, or a Samba Domain
49 Domain membership has many advantages:
54 MS Windows workstation users get the benefit of SSO
58 Domain user access rights and file ownership / access controls can be set
59 from the single Domain SAM (Security Account Manager) database
60 (works with Domain member servers as well as with MS Windows workstations
61 that are domain members)
65 Only <application>MS Windows NT4 / 200x / XP Professional</application>
66 workstations that are Domain members
67 can use network logon facilities
71 Domain Member workstations can be better controlled through the use of
72 Policy files (<filename>NTConfig.POL</filename>) and Desktop Profiles.
76 Through the use of logon scripts, users can be given transparent access to network
77 applications that run off application servers
81 Network administrators gain better application and user access management
82 abilities because there is no need to maintain user accounts on any network
83 client or server, other than the central Domain database
84 (either NT4/Samba SAM style Domain, NT4 Domain that is back ended with an
85 LDAP directory, or via an Active Directory infrastructure)
91 <sect1 id="machine-trust-accounts">
92 <title>MS Windows Workstation/Server Machine Trust Accounts</title>
94 <indexterm><primary>machine trust accounts</primary></indexterm>
97 A machine trust account is an account that is used to authenticate a client
99 (rather than a user) to the Domain Controller server. In Windows terminology,
100 this is known as a "Computer Account."
104 The password of a machine trust account acts as the shared secret for
105 secure communication with the Domain Controller. This is a security
106 feature to prevent an unauthorized machine with the same NetBIOS name
107 from joining the domain and gaining access to domain user/group
108 accounts. Windows NT, 200x, XP Professional clients use machine trust
109 accounts, but Windows 9x / Me / XP Home clients do not. Hence, a
110 Windows 9x / Me / XP Home client is never a true member of a domain
111 because it does not possess a machine trust account, and thus has no
112 shared secret with the domain controller.
116 A Windows NT4 PDC stores each machine trust account in the Windows Registry.
117 The introduction of MS Windows 2000 saw the introduction of Active Directory,
118 the new repository for machine trust accounts.
122 A Samba PDC, however, stores each machine trust account in two parts,
127 A Domain Security Account (stored in the
128 <smbconfoption><name>passdb backend</name></smbconfoption> that has been configured in the
129 &smb.conf; file. The precise nature of the account information that is
130 stored depends on the type of backend database that has been chosen.
134 The older format of this data is the <filename>smbpasswd</filename> database
135 which contains the UNIX login ID, the UNIX user identifier (UID), and the
136 LanMan and NT encrypted passwords. There is also some other information in
137 this file that we do not need to concern ourselves with here.
141 The two newer database types are called <emphasis>ldapsam</emphasis>,
142 <emphasis>tdbsam</emphasis>. Both store considerably more data than the
143 older <filename>smbpasswd</filename> file did. The extra information
144 enables new user account controls to be used.
148 A corresponding UNIX account, typically stored in
149 <filename>/etc/passwd</filename>. Work is in progress to allow a
150 simplified mode of operation that does not require UNIX user accounts, but
151 this may not be a feature of the early releases of Samba-3.
156 <indexterm><primary>machine trust accounts</primary><secondary>creating</secondary></indexterm>
159 There are three ways to create machine trust accounts:
164 Manual creation from the UNIX/Linux command line. Here, both the Samba and
165 corresponding UNIX account are created by hand.
168 <indexterm><primary>Server Manager</primary></indexterm>
170 Using the MS Windows NT4 Server Manager (either from an NT4 Domain member
171 server, or using the Nexus toolkit available from the Microsoft web site.
172 This tool can be run from any MS Windows machine so long as the user is
173 logged on as the administrator account.
177 "On-the-fly" creation. The Samba machine trust account is automatically
178 created by Samba at the time the client is joined to the domain.
179 (For security, this is the recommended method.) The corresponding UNIX
180 account may be created automatically or manually.
185 <title>Manual Creation of Machine Trust Accounts</title>
188 The first step in manually creating a machine trust account is to manually
189 create the corresponding UNIX account in <filename>/etc/passwd</filename>.
190 This can be done using <command>vipw</command> or another 'add user' command
191 that is normally used to create new UNIX accounts. The following is an example for a Linux based Samba server:
194 <indexterm><primary>useradd</primary></indexterm>
195 <indexterm><primary>vipw</primary></indexterm>
199 &rootprompt;<userinput>/usr/sbin/useradd -g 100 -d /dev/null -c <replaceable>"machine nickname"</replaceable> \
200 -s /bin/false <replaceable>machine_name</replaceable>$ </userinput>
202 &rootprompt;<userinput>passwd -l <replaceable>machine_name</replaceable>$</userinput>
206 <indexterm><primary>chpass</primary></indexterm>
209 On *BSD systems, this can be done using the <command>chpass</command> utility:
214 &rootprompt;<userinput>chpass -a \
215 "<replaceable>machine_name</replaceable>$:*:101:100::0:0:Workstation <replaceable>machine_name</replaceable>:/dev/null:/sbin/nologin"</userinput>
220 The <filename>/etc/passwd</filename> entry will list the machine name
221 with a "$" appended, won't have a password, will have a null shell and no
222 home directory. For example a machine named 'doppy' would have an
223 <filename>/etc/passwd</filename> entry like this:
227 doppy$:x:505:100:<replaceable>machine_nickname</replaceable>:/dev/null:/bin/false
231 Above, <replaceable>machine_nickname</replaceable> can be any
232 descriptive name for the client, i.e., BasementComputer.
233 <replaceable>machine_name</replaceable> absolutely must be the NetBIOS
234 name of the client to be joined to the domain. The "$" must be
235 appended to the NetBIOS name of the client or Samba will not recognize
236 this as a machine trust account.
240 Now that the corresponding UNIX account has been created, the next step is to create
241 the Samba account for the client containing the well-known initial
242 machine trust account password. This can be done using the
243 <command>smbpasswd</command> command
249 &rootprompt;<userinput>smbpasswd -a -m <replaceable>machine_name</replaceable></userinput>
254 where <replaceable>machine_name</replaceable> is the machine's NetBIOS
255 name. The RID of the new machine account is generated from the UID of
256 the corresponding UNIX account.
260 <title>Join the client to the domain immediately</title>
263 Manually creating a machine trust account using this method is the
264 equivalent of creating a machine trust account on a Windows NT PDC using
265 <indexterm><primary>Server Manager</primary></indexterm>
266 the <application>Server Manager</application>. From the time at which the
267 account is created to the time which the client joins the domain and
268 changes the password, your domain is vulnerable to an intruder joining
269 your domain using a machine with the same NetBIOS name. A PDC inherently
270 trusts members of the domain and will serve out a large degree of user
271 information to such clients. You have been warned!
277 <title>Using NT4 Server Manager to Add Machine Accounts to the Domain</title>
280 If the machine from which you are trying to manage the domain is an
281 <application>MS Windows NT4 workstation or MS Windows 200x / XP Professional</application>
282 then the tool of choice is the package called <command>SRVTOOLS.EXE</command>.
283 When executed in the target directory this will unpack <command>SrvMge.exe</command>
284 and <command>UsrMgr.exe</command> (both are domain management tools for MS Windows NT4 workstation).
288 If your workstation is a <application>Microsoft Windows 9x/Me</application> family product
289 you should download the <command>Nexus.exe</command> package from the Microsoft web site.
290 When executed from the target directory this will unpack the same tools but for use on
295 Further information about these tools may be obtained from the following locations:
296 <ulink noescape="1" url="http://support.microsoft.com/default.aspx?scid=kb;en-us;173673"></ulink>
297 <ulink noescape="1" url="http://support.microsoft.com/default.aspx?scid=kb;en-us;172540"></ulink>
301 Launch the <command>srvmgr.exe</command> (Server Manager for Domains) and follow these steps:
305 <title>Server Manager Account Machine Account Management</title>
307 From the menu select <guimenu>Computer</guimenu>
311 Click on <guimenuitem>Select Domain</guimenuitem>
315 Click on the name of the domain you wish to administer in the
316 <guilabel>Select Domain</guilabel> panel and then click
317 <guibutton>OK</guibutton>.
321 Again from the menu select <guimenu>Computer</guimenu>
325 Select <guimenuitem>Add to Domain</guimenuitem>
329 In the dialog box, click on the radio button to
330 <guilabel>Add NT Workstation of Server</guilabel>, then
331 enter the machine name in the field provided, then click the
332 <guibutton>Add</guibutton> button.
339 <title>"On-the-Fly" Creation of Machine Trust Accounts</title>
342 The second (and recommended) way of creating machine trust accounts is
343 simply to allow the Samba server to create them as needed when the client
344 is joined to the domain.
347 <para>Since each Samba machine trust account requires a corresponding UNIX account, a method
348 for automatically creating the UNIX account is usually supplied; this requires configuration of the
349 add machine script option in
350 &smb.conf;. This method is not required, however; corresponding UNIX
351 accounts may also be created manually.
356 Below is an example for a RedHat Linux system.
360 <smbconfsection>[global]</smbconfsection>
361 <smbconfcomment><...remainder of parameters...></smbconfcomment>
362 <smbconfoption><name>add machine script</name><value>/usr/sbin/useradd -d /dev/null -g 100 -s /bin/false -M %u </value></smbconfoption>
363 </smbconfblock></para>
369 <sect2><title>Making an MS Windows Workstation or Server a Domain Member</title>
372 The procedure for making an MS Windows workstation of server a member of the domain varies
373 with the version of Windows:
377 <title>Windows 200x XP Professional</title>
380 When the user elects to make the client a domain member, Windows 200x prompts for
381 an account and password that has privileges to create machine accounts in the domain.
382 A Samba administrative account (i.e., a Samba account that has root privileges on the
383 Samba server) must be entered here; the operation will fail if an ordinary user
388 Note: For security reasons the password for this administrative account should be set
389 to a password that is other than that used for the root user in the
390 <filename>/etc/passwd</filename>.
394 The name of the account that is used to create domain member machine accounts can be
395 anything the network administrator may choose. If it is other than <emphasis>root</emphasis>
396 then this is easily mapped to root using the file pointed to be the &smb.conf; parameter
397 <smbconfoption><name>username map</name><value>/etc/samba/smbusers</value></smbconfoption>.
401 The session key of the Samba administrative account acts as an
402 encryption key for setting the password of the machine trust
403 account. The machine trust account will be created on-the-fly, or
404 updated if it already exists.
409 <title>Windows NT4</title>
412 If the machine trust account was created manually, on the
413 Identification Changes menu enter the domain name, but do not
414 check the box <guilabel>Create a Computer Account in the Domain</guilabel>.
415 In this case, the existing machine trust account is used to join the machine
420 If the machine trust account is to be created
421 on-the-fly, on the Identification Changes menu enter the domain
422 name, and check the box <guilabel>Create a Computer Account in the
423 Domain</guilabel>. In this case, joining the domain proceeds as above
424 for Windows 2000 (i.e., you must supply a Samba administrative account when
432 <para>Joining a Samba client to a domain is documented in
433 <link linkend="domain-member-server"></link>.
440 <sect1 id="domain-member-server">
441 <title>Domain Member Server</title>
444 This mode of server operation involves the Samba machine being made a member
445 of a domain security context. This means by definition that all user
446 authentication will be done from a centrally defined authentication regime.
447 The authentication regime may come from an NT3/4 style (old domain technology)
448 server, or it may be provided from an Active Directory server (ADS) running on
449 MS Windows 2000 or later.
454 Of course it should be clear that the authentication back end itself could be
455 from any distributed directory architecture server that is supported by Samba.
456 This can be LDAP (from OpenLDAP), or Sun's iPlanet, of NetWare Directory
462 Please refer to <link linkend="samba-pdc"></link>
463 for more information regarding how to create a domain
464 machine account for a domain member server as well as for information
465 regarding how to enable the Samba domain member machine to join the domain and
466 to be fully trusted by it.
470 <title>Joining an NT4 type Domain with Samba-3</title>
473 <table frame="all"><title>Assumptions</title>
474 <tgroup align="left" cols="2">
476 <row><entry>NetBIOS name:</entry><entry>SERV1</entry></row>
477 <row><entry>Win2K/NT domain name:</entry><entry>&example.workgroup;</entry></row>
478 <row><entry>Domain's PDC NetBIOS name:</entry><entry>DOMPDC</entry></row>
479 <row><entry>Domain's BDC NetBIOS names:</entry><entry>DOMBDC1 and DOMBDC2</entry></row>
486 First, you must edit your &smb.conf; file to tell Samba it should
487 now use domain security.
492 <smbconfoption><name>security</name></smbconfoption> line in the [global] section
493 of your &smb.conf; to read:
498 <smbconfoption><name>security</name><value>domain</value></smbconfoption>
503 Next change the <smbconfoption><name>workgroup</name></smbconfoption> line in the <smbconfsection>[global]</smbconfsection>
509 <smbconfoption><name>workgroup</name><value>&example.workgroup;</value></smbconfoption>
514 as this is the name of the domain we are joining.
518 You must also have the parameter
519 <smbconfoption><name>encrypt passwords</name></smbconfoption> set to <constant>yes
520 </constant> in order for your users to authenticate to the NT PDC.
524 Finally, add (or modify) a <smbconfoption><name>password server</name></smbconfoption> line in the [global]
530 <smbconfoption><name>password server</name><value>DOMPDC DOMBDC1 DOMBDC2</value></smbconfoption>
535 These are the primary and backup domain controllers Samba
536 will attempt to contact in order to authenticate users. Samba will
537 try to contact each of these servers in order, so you may want to
538 rearrange this list in order to spread out the authentication load
539 among domain controllers.
543 Alternatively, if you want smbd to automatically determine
544 the list of Domain controllers to use for authentication, you may
550 <smbconfoption><name>password server</name><value>*</value></smbconfoption>
555 This method allows Samba to use exactly the same mechanism that NT does. This
556 method either broadcasts or uses a WINS database in order to
557 find domain controllers to authenticate against.
561 In order to actually join the domain, you must run this command:
566 &rootprompt;<userinput>net rpc join -S DOMPDC -U<replaceable>Administrator%password</replaceable></userinput>
571 If the <option>-S DOMPDC</option> argument is not given then
572 the domain name will be obtained from &smb.conf;.
576 As we are joining the domain DOM and the PDC for that domain
577 (the only machine that has write access to the domain SAM database)
578 is DOMPDC, we use it for the <option>-S</option> option.
579 The <replaceable>Administrator%password</replaceable> is
580 the login name and password for an account which has the necessary
581 privilege to add machines to the domain. If this is successful
582 you will see the message:
586 <computeroutput>Joined domain DOM.</computeroutput>
587 or <computeroutput>Joined 'SERV1' to realm 'MYREALM'</computeroutput>
591 in your terminal window. See the
592 <command>net</command> man page for more details.
596 This process joins the server to the domain without having to create the machine
597 trust account on the PDC beforehand.
601 This command goes through the machine account password
602 change protocol, then writes the new (random) machine account
603 password for this Samba server into a file in the same directory
604 in which an smbpasswd file would be stored - normally:
608 <filename>/usr/local/samba/private/secrets.tdb</filename>
612 This file is created and owned by root and is not
613 readable by any other user. It is the key to the domain-level
614 security for your system, and should be treated as carefully
615 as a shadow password file.
619 Finally, restart your Samba daemons and get ready for
620 clients to begin using domain security! The way you can restart your
621 samba daemons depends on your distribution, but in most cases running
623 &rootprompt;/etc/init.d/samba restart
631 <title>Why is this better than security = server?</title>
634 Currently, domain security in Samba doesn't free you from
635 having to create local UNIX users to represent the users attaching
636 to your server. This means that if domain user <constant>DOM\fred
637 </constant> attaches to your domain security Samba server, there needs
638 to be a local UNIX user fred to represent that user in the UNIX
639 filesystem. This is very similar to the older Samba security mode
641 where Samba would pass through the authentication request to a Windows
642 NT server in the same way as a Windows 95 or Windows 98 server would.
646 Please refer to <link linkend="winbind"></link> for information on a system
647 to automatically assign UNIX uids and gids to Windows NT Domain users and groups.
651 The advantage to domain-level security is that the
652 authentication in domain-level security is passed down the authenticated
653 RPC channel in exactly the same way that an NT server would do it. This
654 means Samba servers now participate in domain trust relationships in
655 exactly the same way NT servers do (i.e., you can add Samba servers into
656 a resource domain and have the authentication passed on from a resource
657 domain PDC to an account domain PDC).
661 In addition, with <smbconfoption><name>security</name><value>server</value></smbconfoption> every Samba
662 daemon on a server has to keep a connection open to the
663 authenticating server for as long as that daemon lasts. This can drain
664 the connection resources on a Microsoft NT server and cause it to run
665 out of available connections. With <smbconfoption><name>security</name><value>domain</value></smbconfoption>,
666 however, the Samba daemons connect to the PDC/BDC only for as long
667 as is necessary to authenticate the user, and then drop the connection,
668 thus conserving PDC connection resources.
672 And finally, acting in the same manner as an NT server
673 authenticating to a PDC means that as part of the authentication
674 reply, the Samba server gets the user identification information such
675 as the user SID, the list of NT groups the user belongs to, etc.
680 Much of the text of this document
681 was first published in the Web magazine
682 <ulink url="http://www.linuxworld.com">LinuxWorld</ulink> as the article <ulink
683 url="http://www.linuxworld.com/linuxworld/lw-1998-10/lw-10-samba.html">Doing
684 the NIS/NT Samba</ulink>.
691 <sect1 id="ads-member">
692 <title>Samba ADS Domain Membership</title>
694 <indexterm significance="preferred"><primary>Active Directory</primary></indexterm>
695 <indexterm significance="preferred"><primary>ADS</primary><see>Active Directory</see></indexterm>
697 <indexterm><primary>KDC</primary></indexterm>
698 <indexterm><primary>Kerberos</primary></indexterm>
700 This is a rough guide to setting up Samba 3.0 with Kerberos authentication against a
701 Windows2000 KDC. A familiarity with Kerberos is assumed.
705 <title>Setup your &smb.conf;</title>
708 You must use at least the following 3 options in &smb.conf;:
712 <smbconfoption><name>realm</name><value>your.kerberos.REALM</value></smbconfoption>
713 <smbconfoption><name>security</name><value>ADS</value></smbconfoption>
714 <smbconfoption><name>encrypt passwords</name><value>yes</value></smbconfoption>
715 </smbconfblock></para>
718 In case samba can't figure out your ads server using your realm name, use the
719 <smbconfoption><name>ads server</name></smbconfoption> option in &smb.conf;:
721 <smbconfoption><name>ads server</name><value>your.kerberos.server</value></smbconfoption>
726 You do <emphasis>not</emphasis> need a smbpasswd file, and older clients will be authenticated as
727 if <smbconfoption><name>security</name><value>domain</value></smbconfoption>, although it won't do any harm and
728 allows you to have local users not in the domain. It is expected that the above
729 required options will change soon when active directory integration will get
736 <title>Setup your <filename>/etc/krb5.conf</filename></title>
739 The minimal configuration for <filename>krb5.conf</filename> is:
742 <para><programlisting>
744 default_realm = YOUR.KERBEROS.REALM
747 YOUR.KERBEROS.REALM = {
748 kdc = your.kerberos.server
750 </programlisting></para>
752 <indexterm><primary>kinit</primary></indexterm>
755 Test your config by doing a <userinput>kinit
756 <replaceable>USERNAME</replaceable>@<replaceable>REALM</replaceable></userinput> and
757 making sure that your password is accepted by the Win2000 KDC.
761 The realm must be uppercase or you will get <errorname>Cannot find KDC for
762 requested realm while getting initial credentials</errorname> error (Kerberos
767 Time between the two servers must be synchronized. You will get a
768 <errorname>kinit(v5): Clock skew too great while getting initial credentials</errorname>
769 if the time difference is more than five minutes.
773 You also must ensure that you can do a reverse DNS lookup on the IP
774 address of your KDC. Also, the name that this reverse lookup maps to
775 must either be the NetBIOS name of the KDC (ie. the hostname with no
776 domain attached) or it can alternatively be the NetBIOS name
777 followed by the realm.
781 The easiest way to ensure you get this right is to add a
782 <filename>/etc/hosts</filename> entry mapping the IP address of your KDC to
783 its NetBIOS name. If you don't get this right then you will get a
784 <errorname>local error</errorname> when you try to join the realm.
788 If all you want is Kerberos support in &smbclient; then you can skip
789 straight to <link linkend="ads-test-smbclient">Test with &smbclient;</link> now.
790 <link linkend="ads-create-machine-account">Creating a computer account</link>
791 and <link linkend="ads-test-server">testing your servers</link>
792 is only needed if you want Kerberos support for &smbd; and &winbindd;.
797 <sect2 id="ads-create-machine-account">
798 <title>Create the computer account</title>
801 As a user that has write permission on the Samba private directory
804 &rootprompt; <userinput>net ads join -U Administrator%password</userinput>
809 <title>Possible errors</title>
813 <varlistentry><term><errorname>ADS support not compiled in</errorname></term>
814 <listitem><para>Samba must be reconfigured (remove config.cache) and recompiled
815 (make clean all install) after the Kerberos libs and headers are installed.
816 </para></listitem></varlistentry>
818 <varlistentry><term><errorname>net ads join prompts for user name</errorname></term>
819 <listitem><para>You need to login to the domain using <userinput>kinit
820 <replaceable>USERNAME</replaceable>@<replaceable>REALM</replaceable></userinput>.
821 <replaceable>USERNAME</replaceable> must be a user who has rights to add a machine
822 to the domain. </para></listitem></varlistentry>
830 <sect2 id="ads-test-server">
831 <title>Test your server setup</title>
834 If the join was successful, you will see a new computer account with the
835 NetBIOS name of your Samba server in Active Directory (in the "Computers"
836 folder under Users and Computers.
840 On a Windows 2000 client try <userinput>net use * \\server\share</userinput>. You should
841 be logged in with Kerberos without needing to know a password. If
842 this fails then run <userinput>klist tickets</userinput>. Did you get a ticket for the
843 server? Does it have an encoding type of DES-CBC-MD5 ?
848 <sect2 id="ads-test-smbclient">
849 <title>Testing with &smbclient;</title>
851 <indexterm><primary>smbclient</primary></indexterm>
854 On your Samba server try to login to a Win2000 server or your Samba
855 server using &smbclient; and Kerberos. Use &smbclient; as usual, but
856 specify the <option>-k</option> option to choose Kerberos authentication.
865 You must change administrator password at least once after DC
866 install, to create the right encoding types
870 W2k doesn't seem to create the _kerberos._udp and _ldap._tcp in
871 their defaults DNS setup. Maybe this will be fixed later in service packs.
878 <title>Common Errors</title>
881 In the process of adding / deleting / re-adding domain member machine accounts there are
882 many traps for the unwary player and there are many <quote>little</quote> things that can go wrong.
883 It is particularly interesting how often subscribers on the samba mailing list have concluded
884 after repeated failed attempts to add a machine account that it is necessary to "re-install"
885 MS Windows on t he machine. In truth, it is seldom necessary to reinstall because of this type
886 of problem. The real solution is often very simple, and with understanding of how MS Windows
887 networking functions easy to overcome.
891 <title>Can Not Add Machine Back to Domain</title>
894 <quote> A Windows workstation was reinstalled. The original domain machine
895 account was deleted and added immediately. The workstation will not join the domain if I use
896 the same machine name. Attempts to add the machine fail with a message that the machine already
897 exists on the network - I know it doesn't. Why is this failing?</quote>
901 The original name is still in the NetBIOS name cache and must expire after machine account
902 deletion BEFORE adding that same name as a domain member again. The best advice is to delete
903 the old account and then to add the machine with a new name.
909 <title>Adding Machine to Domain Fails</title>
912 <quote>Adding a Windows 200x or XP Professional machine to the Samba PDC Domain fails with a
913 message that, <errorname>The machine could not be added at this time, there is a network problem.
914 Please try again later.</errorname> Why?</quote>
918 You should check that there is an <smbconfoption><name>add machine script</name></smbconfoption> in your &smb.conf;
919 file. If there is not, please add one that is appropriate for your OS platform. If a script
920 has been defined you will need to debug it's operation. Increase the <smbconfoption><name>log level</name></smbconfoption>
921 in the &smb.conf; file to level 10, then try to rejoin the domain. Check the logs to see which
922 operation is failing.
926 Possible causes include:
931 The script does not actually exist, or could not be located in the path specified.
935 <emphasis>Corrective Action:</emphasis> Fix it. Make sure that when run manually
936 that the script will add both the UNIX system account _and_ the Samba SAM account.
940 The machine could not be added to the UNIX system accounts file <filename>/etc/passwd</filename>
944 <emphasis>Corrective Action:</emphasis> Check that the machine name is a legal UNIX
945 system account name. ie: If the UNIX utility <command>useradd</command> is called
946 then make sure that the machine name you are trying to add can be added using this
947 tool. <command>Useradd</command> on some systems will not allow any upper case characters
948 nor will it allow spaces in the name.
955 <title>I can't join a Windows 2003 PDC</title>
957 <para>Windows 2003 requires SMB signing. Client side SMB signing has
958 only been implemented partially in Samba 3.0. Set <smbconfoption><name>client use spnego</name><value>no</value></smbconfoption> when communicating
959 with a windows 2003 server. </para>