From cdd3fa410a6b9f0ddc778149175f3ba7e8a7095d Mon Sep 17 00:00:00 2001 From: Jelmer Vernooij Date: Thu, 17 Apr 2003 19:15:22 +0000 Subject: Regenerate docs (This used to be commit 13a4cd540a1c193e77d973b9dac5bc2d9e7a5353) --- docs/htmldocs/samba-pdc.html | 867 ++++++++++++------------------------------- 1 file changed, 245 insertions(+), 622 deletions(-) (limited to 'docs/htmldocs/samba-pdc.html') diff --git a/docs/htmldocs/samba-pdc.html b/docs/htmldocs/samba-pdc.html index 0c1e085159..31e5468681 100644 --- a/docs/htmldocs/samba-pdc.html +++ b/docs/htmldocs/samba-pdc.html @@ -74,37 +74,123 @@ CLASS="CHAPTER" >Chapter 6. Samba as an NT4 or Win2k Primary Domain ControllerChapter 7. Samba as an NT4 or Win2k Primary Domain Controller
Table of Contents
7.1. Prerequisite Reading
7.2. Background
7.3. Configuring the Samba Domain Controller
7.4. Creating Machine Trust Accounts and Joining Clients to the Domain
7.4.1. Manual Creation of Machine Trust Accounts
7.4.2. "On-the-Fly" Creation of Machine Trust Accounts
7.4.3. Joining the Client to the Domain
7.5. Common Problems and Errors
7.5.1. I cannot include a '$' in a machine name
7.5.2. 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.
7.5.3. The system can not log you on (C000019B)....
7.5.4. The machine trust account for this computer either does not +exist or is not accessible.
7.5.5. When I attempt to login to a Samba Domain from a NT4/W2K workstation, +I get a message about my account being disabled.
7.6. Domain Control for Windows 9x/ME

6.1. Prerequisite Reading7.1. Prerequisite Reading

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(5) -manpage.

smb.conf manpage.

6.2. Background7.2. Background

This article outlines the steps necessary for configuring Samba as a PDC. @@ -250,19 +336,17 @@ CLASS="SECT1" >

6.3. Configuring the Samba Domain Controller7.3. Configuring the Samba Domain Controller

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.

smb.conf man page.

Here is an example Encrypted passwords must be enabled. For more details on how to do this, refer to ENCRYPTION.htmlthe User Database chapter.

6.4. Creating Machine Trust Accounts and Joining Clients to the Domain7.4. Creating Machine Trust Accounts and Joining Clients to the Domain

A machine trust account is a Samba account that is used to @@ -549,7 +633,10 @@ CLASS="EMPHASIS" 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 [globals] section of the smb.conf file.

  • Read the chapter about the User Database +for details.

    A Samba PDC, however, stores each machine trust account in two parts, as follows: @@ -632,8 +725,8 @@ CLASS="SECT2" >

    6.4.1. Manual Creation of Machine Trust Accounts7.4.1. Manual Creation of Machine Trust Accounts

    The first step in manually creating a machine trust account is to @@ -738,12 +831,12 @@ as shown here:

    root# smbpasswd -a -m machine_name

    where

    6.4.2. "On-the-Fly" Creation of Machine Trust Accounts7.4.2. "On-the-Fly" Creation of Machine Trust Accounts

    The second (and recommended) way of creating machine trust accounts is @@ -839,8 +932,8 @@ CLASS="SECT2" >

    6.4.3. Joining the Client to the Domain7.4.3. Joining the Client to the Domain

    The procedure for joining a client to the domain varies with the @@ -899,6 +992,22 @@ CLASS="EMPHASIS" (i.e., you must supply a Samba administrative account when prompted).

  • Samba

    Joining a samba client to a domain is documented in + the Domain Member chapter.

    • 6.5. Common Problems and Errors7.5. Common Problems and Errors

    7.5.1. I cannot include a '$' in a machine name

    7.5.2. 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.

    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: -

    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:

    C:\WINNT\> net use * /d -

    Further, if the machine is a 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. -

  • The system can not log you on (C000019B).... -

    Further, if the machine is a 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.

    • 7.5.3. The system can not log you on (C000019B)....

    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. -

    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 smbpasswd or rpcclient utilities. -

  • The machine trust account for this computer either does not - exist or is not accessible. -

    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 smbpasswd or rpcclient utilities.

    • 7.5.4. The machine trust account for this computer either does not +exist or is not accessible.

    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? -

    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?

    This problem is caused by the PDC not having a suitable machine trust account. - If you are using the This problem is caused by the PDC not having a suitable machine trust account. +If you are using the add user script method to create - accounts then this would indicate that it has not worked. Ensure the domain - admin user system is working. -

    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. -

  • When I attempt to login to a Samba Domain from a NT4/W2K workstation, - I get a message about my account being disabled. -

    This problem is caused by a PAM related bug in Samba 2.2.0. This bug is - fixed in 2.2.1. Other symptoms could be unaccessible shares on - NT/W2K member servers in the domain or the following error in your smbd.log: - passdb/pampass.c:pam_account(268) PAM: UNKNOWN ERROR for User: %user% -

    At first be ensure to enable the useraccounts with smbpasswd -e - %user%, this is normally done, when you create an account. -

    In order to work around this problem in 2.2.0, configure the - account control flag in - /etc/pam.d/samba file as follows: - 

    	account required        pam_permit.so
-

    If you want to remain backward compatibility to samba 2.0.x use - pam_permit.so, it's also possible to use - pam_pwdb.so. There are some bugs if you try to - use pam_unix.so, if you need this, be ensure to use - the most recent version of this file. -

    • 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.

    6.6. What other help can I get?

    There are many sources of information available in the form -of mailing lists, RFC's and documentation. The docs that come -with the samba distribution contain very good explanations of -general SMB topics such as browsing.

    smbpasswd -e +%user%, this is normally done, when you create an account.

    6.7. Domain Control for Windows 9x/ME7.6. Domain Control for Windows 9x/ME

    A domain and a workgroup are exactly the same thing in terms of network @@ -1625,8 +1248,8 @@ CLASS="SECT2" >

    6.7.1. Configuration Instructions: Network Logons7.6.1. Configuration Instructions: Network Logons

    The main difference between a PDC and a Windows 9x logon -- cgit