2002-11-06 01:28:45 +03:00
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
2001-04-20 01:33:44 +04:00
< HTML
>< HEAD
>< TITLE
2003-03-30 15:22:22 +04:00
>Samba as an NT4 or Win2k Primary Domain Controller< /TITLE
2001-04-20 01:33:44 +04:00
>< META
NAME="GENERATOR"
2003-03-18 19:48:14 +03:00
CONTENT="Modular DocBook HTML Stylesheet Version 1.7">< LINK
2002-11-06 01:28:45 +03:00
REL="HOME"
TITLE="SAMBA Project Documentation"
HREF="samba-howto-collection.html">< LINK
REL="UP"
TITLE="Type of installation"
2002-11-13 18:34:49 +03:00
HREF="type.html">< LINK
2002-11-06 01:28:45 +03:00
REL="PREVIOUS"
2003-04-02 22:07:52 +04:00
TITLE="Samba as Stand-Alone Server"
2002-11-13 18:34:49 +03:00
HREF="securitylevels.html">< LINK
2002-11-06 01:28:45 +03:00
REL="NEXT"
2003-04-02 22:07:52 +04:00
TITLE="Samba Backup Domain Controller to Samba Domain Control"
2002-11-06 01:28:45 +03:00
HREF="samba-bdc.html">< /HEAD
2001-04-20 01:33:44 +04:00
>< BODY
2002-11-06 01:28:45 +03:00
CLASS="CHAPTER"
2001-04-20 01:33:44 +04:00
BGCOLOR="#FFFFFF"
TEXT="#000000"
LINK="#0000FF"
VLINK="#840084"
ALINK="#0000FF"
>< DIV
2002-11-06 01:28:45 +03:00
CLASS="NAVHEADER"
>< TABLE
SUMMARY="Header navigation table"
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
CELLSPACING="0"
>< TR
>< TH
COLSPAN="3"
ALIGN="center"
>SAMBA Project Documentation< /TH
>< /TR
>< TR
>< TD
WIDTH="10%"
ALIGN="left"
VALIGN="bottom"
>< A
2002-11-13 18:34:49 +03:00
HREF="securitylevels.html"
2002-11-06 01:28:45 +03:00
ACCESSKEY="P"
>Prev< /A
>< /TD
>< TD
WIDTH="80%"
ALIGN="center"
VALIGN="bottom"
>< /TD
>< TD
WIDTH="10%"
ALIGN="right"
VALIGN="bottom"
>< A
HREF="samba-bdc.html"
ACCESSKEY="N"
>Next< /A
>< /TD
>< /TR
>< /TABLE
>< HR
ALIGN="LEFT"
WIDTH="100%">< /DIV
2001-04-20 01:33:44 +04:00
>< DIV
2002-11-06 01:28:45 +03:00
CLASS="CHAPTER"
2001-04-20 01:33:44 +04:00
>< H1
>< A
2003-02-19 01:14:04 +03:00
NAME="SAMBA-PDC"
>< /A
2003-03-30 15:22:22 +04:00
>Chapter 6. Samba as an NT4 or Win2k Primary Domain Controller< /H1
2001-04-20 01:33:44 +04:00
>< DIV
CLASS="SECT1"
>< H1
CLASS="SECT1"
>< A
2003-04-07 18:01:19 +04:00
NAME="AEN878"
2003-03-30 15:22:22 +04:00
>6.1. Prerequisite Reading< /A
2003-03-18 19:48:14 +03:00
>< /H1
2001-06-01 15:50:38 +04:00
>< P
2001-10-10 21:19:10 +04:00
>Before you continue reading in this chapter, please make sure
2001-06-01 15:50:38 +04:00
that you are comfortable with configuring basic files services
2001-10-10 21:19:10 +04:00
in smb.conf and how to enable and administer password
2001-06-01 15:50:38 +04:00
encryption in Samba. Theses two topics are covered in the
< A
HREF="smb.conf.5.html"
TARGET="_top"
>< TT
CLASS="FILENAME"
>smb.conf(5)< /TT
>< /A
>
2003-03-30 15:22:22 +04:00
manpage.< /P
2001-06-01 15:50:38 +04:00
>< /DIV
>< DIV
CLASS="SECT1"
2002-11-06 01:28:45 +03:00
>< H1
2001-06-01 15:50:38 +04:00
CLASS="SECT1"
>< A
2003-04-07 18:01:19 +04:00
NAME="AEN883"
2003-03-30 15:22:22 +04:00
>6.2. Background< /A
2003-03-18 19:48:14 +03:00
>< /H1
2001-04-20 01:33:44 +04:00
>< P
2003-03-30 15:22:22 +04:00
>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.< /P
2001-04-20 01:33:44 +04:00
>< P
>< /P
>< UL
>< LI
>< P
2003-04-02 22:07:52 +04:00
> Domain logons for Windows NT 4.0 / 200x / XP Professional clients.
2001-06-01 15:50:38 +04:00
< /P
2001-04-20 01:33:44 +04:00
>< /LI
>< LI
>< P
2003-04-02 22:07:52 +04:00
> Placing Windows 9x / Me clients in user level security
2001-06-01 15:50:38 +04:00
< /P
2001-04-20 01:33:44 +04:00
>< /LI
>< LI
>< P
2003-04-02 22:07:52 +04:00
> Retrieving a list of users and groups from a Samba PDC to
2003-03-30 15:22:22 +04:00
Windows 9x / Me / NT / 200x / XP Professional clients
2001-06-01 15:50:38 +04:00
< /P
2001-04-20 01:33:44 +04:00
>< /LI
>< LI
>< P
2003-04-02 22:07:52 +04:00
> Roaming Profiles
2001-06-01 15:50:38 +04:00
< /P
2001-04-20 01:33:44 +04:00
>< /LI
>< LI
>< P
2003-04-02 22:07:52 +04:00
> Network/System Policies
2001-06-01 15:50:38 +04:00
< /P
2001-04-20 01:33:44 +04:00
>< /LI
>< /UL
2003-04-02 22:07:52 +04:00
>< DIV
CLASS="NOTE"
>< P
>< /P
>< TABLE
CLASS="NOTE"
WIDTH="100%"
BORDER="0"
>< TR
>< TD
WIDTH="25"
ALIGN="CENTER"
VALIGN="TOP"
>< IMG
SRC="/usr/share/sgml/docbook/stylesheet/dsssl/modular/images/note.gif"
HSPACE="5"
ALT="Note">< /TD
>< TD
ALIGN="LEFT"
VALIGN="TOP"
>< P
>Roaming Profiles and System/Network policies are advanced network administration topics
that are covered separately in this document.< /P
>< /TD
>< /TR
>< /TABLE
>< /DIV
2001-04-20 01:33:44 +04:00
>< P
2003-03-30 15:22:22 +04:00
>The following functionalities are new to the Samba 3.0 release:< /P
2001-04-20 01:33:44 +04:00
>< P
>< /P
>< UL
>< LI
>< P
2001-06-01 15:50:38 +04:00
> Windows NT 4 domain trusts
< /P
2001-04-20 01:33:44 +04:00
>< /LI
>< LI
>< P
2003-03-30 15:22:22 +04:00
> Adding users via the User Manager for Domains
2001-06-01 15:50:38 +04:00
< /P
2001-04-20 01:33:44 +04:00
>< /LI
2003-03-30 15:22:22 +04:00
>< /UL
>< P
>The following functionalities are NOT provided by Samba 3.0:< /P
>< P
>< /P
>< UL
2001-04-20 01:33:44 +04:00
>< LI
>< P
2003-03-30 15:22:22 +04:00
> SAM replication with Windows NT 4.0 Domain Controllers
(i.e. a Samba PDC and a Windows NT BDC or vice versa)
2001-06-01 15:50:38 +04:00
< /P
2001-04-20 01:33:44 +04:00
>< /LI
>< LI
>< P
2001-06-01 15:50:38 +04:00
> Acting as a Windows 2000 Domain Controller (i.e. Kerberos and
Active Directory)
< /P
2001-04-20 01:33:44 +04:00
>< /LI
>< /UL
>< P
2003-03-30 15:22:22 +04:00
>Please note that Windows 9x / Me / XP Home clients are not true members of a domain
2001-04-20 01:33:44 +04:00
for reasons outlined in this article. Therefore the protocol for
2001-12-06 10:37:58 +03:00
support Windows 9x-style domain logons is completely different
2003-03-30 15:22:22 +04:00
from NT4 / Win2k type domain logons and has been officially supported for some
2001-04-20 01:33:44 +04:00
time.< /P
>< P
2003-03-30 15:22:22 +04:00
>< SPAN
CLASS="emphasis"
>< I
CLASS="EMPHASIS"
>MS Windows XP Home edition is NOT able to join a domain and does not permit
the use of domain logons.< /I
>< /SPAN
>< /P
>< P
>Implementing a Samba PDC can basically be divided into 3 broad
2001-04-20 01:33:44 +04:00
steps.< /P
>< P
>< /P
>< OL
TYPE="1"
>< LI
>< P
2001-06-01 15:50:38 +04:00
> Configuring the Samba PDC
2001-04-20 01:33:44 +04:00
< /P
>< /LI
>< LI
>< P
2003-03-30 15:22:22 +04:00
> Creating machine trust accounts and joining clients to the domain
< /P
>< /LI
>< LI
>< P
> Adding and managing domain user accounts
2001-06-01 15:50:38 +04:00
< /P
2001-04-20 01:33:44 +04:00
>< /LI
>< /OL
>< P
>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
2003-03-30 15:22:22 +04:00
concepts.< /P
2001-04-20 01:33:44 +04:00
>< /DIV
>< DIV
CLASS="SECT1"
2002-11-06 01:28:45 +03:00
>< H1
2001-04-20 01:33:44 +04:00
CLASS="SECT1"
>< A
2003-04-07 18:01:19 +04:00
NAME="AEN923"
2003-03-30 15:22:22 +04:00
>6.3. Configuring the Samba Domain Controller< /A
2003-03-18 19:48:14 +03:00
>< /H1
2001-04-20 01:33:44 +04:00
>< P
>The first step in creating a working Samba PDC is to
2003-03-30 15:22:22 +04:00
understand the parameters necessary in smb.conf. Here we
attempt to explain the parameters that are covered in
< A
2001-04-20 01:33:44 +04:00
HREF="smb.conf.5.html"
TARGET="_top"
> the smb.conf
man page< /A
2003-03-30 15:22:22 +04:00
>.< /P
2001-04-20 01:33:44 +04:00
>< P
2001-12-06 10:37:58 +03:00
>Here is an example < TT
CLASS="FILENAME"
>smb.conf< /TT
> for acting as a PDC:< /P
2001-04-20 01:33:44 +04:00
>< P
>< PRE
CLASS="PROGRAMLISTING"
>[global]
; Basic server settings
< A
HREF="smb.conf.5.html#NETBIOSNAME"
TARGET="_top"
>netbios name< /A
2003-03-18 19:48:14 +03:00
> = < VAR
2001-04-20 01:33:44 +04:00
CLASS="REPLACEABLE"
2003-03-18 19:48:14 +03:00
>POGO< /VAR
2001-04-20 01:33:44 +04:00
>
< A
HREF="smb.conf.5.html#WORKGROUP"
TARGET="_top"
>workgroup< /A
2003-03-18 19:48:14 +03:00
> = < VAR
2001-04-20 01:33:44 +04:00
CLASS="REPLACEABLE"
2003-03-18 19:48:14 +03:00
>NARNIA< /VAR
2001-04-20 01:33:44 +04:00
>
; we should act as the domain and local master browser
< A
HREF="smb.conf.5.html#OSLEVEL"
TARGET="_top"
>os level< /A
> = 64
< A
HREF="smb.conf.5.html#PERFERREDMASTER"
TARGET="_top"
>preferred master< /A
> = yes
< A
HREF="smb.conf.5.html#DOMAINMASTER"
TARGET="_top"
>domain master< /A
> = yes
< A
HREF="smb.conf.5.html#LOCALMASTER"
TARGET="_top"
>local master< /A
> = yes
; security settings (must user security = user)
< A
HREF="smb.conf.5.html#SECURITYEQUALSUSER"
TARGET="_top"
>security< /A
> = user
; encrypted passwords are a requirement for a PDC
< A
HREF="smb.conf.5.html#ENCRYPTPASSWORDS"
TARGET="_top"
>encrypt passwords< /A
> = yes
; support domain logons
< A
HREF="smb.conf.5.html#DOMAINLOGONS"
TARGET="_top"
>domain logons< /A
> = yes
; where to store user profiles?
< A
HREF="smb.conf.5.html#LOGONPATH"
TARGET="_top"
>logon path< /A
> = \\%N\profiles\%u
2003-03-30 15:22:22 +04:00
; where is a user's home directory and where should it be mounted at?
2001-04-20 01:33:44 +04:00
< A
HREF="smb.conf.5.html#LOGONDRIVE"
TARGET="_top"
>logon drive< /A
> = H:
< A
HREF="smb.conf.5.html#LOGONHOME"
TARGET="_top"
>logon home< /A
> = \\homeserver\%u
; specify a generic logon script for all users
2001-06-01 15:50:38 +04:00
; this is a relative **DOS** path to the [netlogon] share
2001-04-20 01:33:44 +04:00
< A
HREF="smb.conf.5.html#LOGONSCRIPT"
TARGET="_top"
>logon script< /A
> = logon.cmd
; necessary share for domain controller
[netlogon]
< A
HREF="smb.conf.5.html#PATH"
TARGET="_top"
>path< /A
> = /usr/local/samba/lib/netlogon
< A
2001-12-06 10:37:58 +03:00
HREF="smb.conf.5.html#READONLY"
2001-04-20 01:33:44 +04:00
TARGET="_top"
2001-12-06 10:37:58 +03:00
>read only< /A
> = yes
2001-04-20 01:33:44 +04:00
< A
HREF="smb.conf.5.html#WRITELIST"
TARGET="_top"
>write list< /A
2003-03-18 19:48:14 +03:00
> = < VAR
2001-04-20 01:33:44 +04:00
CLASS="REPLACEABLE"
2003-03-18 19:48:14 +03:00
>ntadmin< /VAR
2001-04-20 01:33:44 +04:00
>
; share for storing user profiles
[profiles]
< A
HREF="smb.conf.5.html#PATH"
TARGET="_top"
>path< /A
> = /export/smb/ntprofile
< A
2001-12-06 10:37:58 +03:00
HREF="smb.conf.5.html#READONLY"
2001-04-20 01:33:44 +04:00
TARGET="_top"
2001-12-06 10:37:58 +03:00
>read only< /A
> = no
2001-04-20 01:33:44 +04:00
< A
HREF="smb.conf.5.html#CREATEMASK"
TARGET="_top"
>create mask< /A
> = 0600
< A
HREF="smb.conf.5.html#DIRECTORYMASK"
TARGET="_top"
>directory mask< /A
> = 0700< /PRE
>< /P
>< P
2001-06-01 15:50:38 +04:00
>There are a couple of points to emphasize in the above configuration.< /P
2001-04-20 01:33:44 +04:00
>< P
>< /P
>< UL
>< LI
>< P
2001-06-01 15:50:38 +04:00
> Encrypted passwords must be enabled. For more details on how
to do this, refer to < A
2003-04-06 22:42:44 +04:00
HREF="passdb.html"
2001-04-20 01:33:44 +04:00
>ENCRYPTION.html< /A
>.
< /P
>< /LI
>< LI
>< P
2001-06-01 15:50:38 +04:00
> The server must support domain logons and a
< TT
2001-04-20 01:33:44 +04:00
CLASS="FILENAME"
>[netlogon]< /TT
2001-06-01 15:50:38 +04:00
> share
< /P
2001-04-20 01:33:44 +04:00
>< /LI
>< LI
>< P
2001-06-01 15:50:38 +04:00
> 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.
< /P
2001-04-20 01:33:44 +04:00
>< /LI
>< /UL
>< P
2003-03-30 15:22:22 +04:00
>Samba 3.0 offers a complete implementation of group mapping
2001-12-06 10:37:58 +03:00
between Windows NT groups and Unix groups (this is really quite
2003-03-30 15:22:22 +04:00
complicated to explain in a short space).< /P
2001-04-20 01:33:44 +04:00
>< /DIV
>< DIV
CLASS="SECT1"
2002-11-06 01:28:45 +03:00
>< H1
2001-04-20 01:33:44 +04:00
CLASS="SECT1"
>< A
2003-04-07 18:01:19 +04:00
NAME="AEN965"
2003-03-30 15:22:22 +04:00
>6.4. Creating Machine Trust Accounts and Joining Clients to the Domain< /A
2003-03-18 19:48:14 +03:00
>< /H1
2001-04-20 01:33:44 +04:00
>< P
2001-12-06 10:37:58 +03:00
>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."< /P
>< P
>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
2003-03-30 15:22:22 +04:00
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.< /P
2001-12-06 10:37:58 +03:00
>< P
>A Windows PDC stores each machine trust account in the Windows
2003-03-30 15:22:22 +04:00
Registry. A Samba-3 PDC also has to stoe machine trust account information
in a suitable back-end data store. With Samba-3 there can be multiple back-ends
for this including:< /P
>< P
>< /P
>< UL
>< LI
>< P
> < SPAN
CLASS="emphasis"
>< I
CLASS="EMPHASIS"
>smbpaswd< /I
>< /SPAN
> - the plain ascii file stored used by
earlier versions of Samba. This file configuration option requires
a Unix/Linux system account for EVERY entry (ie: both for user and for
machine accounts). This file will be located in the < SPAN
CLASS="emphasis"
>< I
CLASS="EMPHASIS"
>private< /I
>< /SPAN
>
directory (default is /usr/local/samba/lib/private or on linux /etc/samba).
< /P
>< /LI
>< LI
>< P
> < SPAN
CLASS="emphasis"
>< I
CLASS="EMPHASIS"
>smbpasswd_nua< /I
>< /SPAN
> - 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 < TT
CLASS="FILENAME"
>private< /TT
> directory.
< /P
>< /LI
>< LI
>< P
> < SPAN
CLASS="emphasis"
>< I
CLASS="EMPHASIS"
>tdbsam< /I
>< /SPAN
> - a binary database backend that will be
stored in the < SPAN
CLASS="emphasis"
>< I
CLASS="EMPHASIS"
>private< /I
>< /SPAN
> directory in a file called
< SPAN
CLASS="emphasis"
>< I
CLASS="EMPHASIS"
>passwd.tdb< /I
>< /SPAN
>. 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.
< /P
>< /LI
>< LI
>< P
> < SPAN
CLASS="emphasis"
>< I
CLASS="EMPHASIS"
>tdbsam_nua< /I
>< /SPAN
> 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.
< /P
>< /LI
>< LI
>< P
> < SPAN
CLASS="emphasis"
>< I
CLASS="EMPHASIS"
>ldapsam< /I
>< /SPAN
> - An LDAP based back-end. Permits the
LDAP server to be specified. eg: ldap://localhost or ldap://frodo.murphy.com
< /P
>< /LI
>< LI
>< P
> < SPAN
CLASS="emphasis"
>< I
CLASS="EMPHASIS"
>ldapsam_nua< /I
>< /SPAN
> - LDAP based back-end with no unix
account requirement, like smbpasswd_nua and tdbsam_nua above.
< /P
>< /LI
>< /UL
>< P
>A Samba PDC, however, stores each machine trust account in two parts,
as follows:
2001-12-06 10:37:58 +03:00
< P
>< /P
>< UL
>< LI
>< P
>A Samba account, stored in the same location as user
LanMan and NT password hashes (currently
< TT
2001-04-20 01:33:44 +04:00
CLASS="FILENAME"
>smbpasswd< /TT
2001-12-06 10:37:58 +03:00
>). The Samba account
possesses and uses only the NT password hash.< /P
>< /LI
>< LI
2001-06-01 15:50:38 +04:00
>< P
2001-12-06 10:37:58 +03:00
>A corresponding Unix account, typically stored in
< TT
2001-06-01 15:50:38 +04:00
CLASS="FILENAME"
>/etc/passwd< /TT
2001-12-06 10:37:58 +03:00
>. (Future releases will alleviate the need to
create < TT
2001-06-01 15:50:38 +04:00
CLASS="FILENAME"
>/etc/passwd< /TT
2001-12-06 10:37:58 +03:00
> entries.) < /P
>< /LI
>< /UL
>< /P
2001-04-20 01:33:44 +04:00
>< P
2001-12-06 10:37:58 +03:00
>There are two ways to create machine trust accounts:< /P
2001-04-20 01:33:44 +04:00
>< P
>< /P
>< UL
>< LI
>< P
2001-12-06 10:37:58 +03:00
> Manual creation. Both the Samba and corresponding
Unix account are created by hand.< /P
2001-04-20 01:33:44 +04:00
>< /LI
>< LI
>< P
2001-12-06 10:37:58 +03:00
> "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. < /P
2001-04-20 01:33:44 +04:00
>< /LI
>< /UL
2001-06-01 15:50:38 +04:00
>< DIV
CLASS="SECT2"
2002-11-06 01:28:45 +03:00
>< H2
2001-06-01 15:50:38 +04:00
CLASS="SECT2"
>< A
2003-04-07 18:01:19 +04:00
NAME="AEN1008"
2003-03-30 15:22:22 +04:00
>6.4.1. Manual Creation of Machine Trust Accounts< /A
2003-03-18 19:48:14 +03:00
>< /H2
2001-04-20 01:33:44 +04:00
>< P
2001-12-06 10:37:58 +03:00
>The first step in manually creating a machine trust account is to
manually create the corresponding Unix account in
< TT
CLASS="FILENAME"
>/etc/passwd< /TT
>. This can be done using
< B
2001-06-01 15:50:38 +04:00
CLASS="COMMAND"
>vipw< /B
2001-12-06 10:37:58 +03:00
> 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:< /P
2001-06-01 15:50:38 +04:00
>< P
2003-03-18 19:48:14 +03:00
> < SAMP
2001-06-01 15:50:38 +04:00
CLASS="PROMPT"
2003-03-18 19:48:14 +03:00
>root# < /SAMP
2001-12-06 10:37:58 +03:00
>< B
CLASS="COMMAND"
2003-03-18 19:48:14 +03:00
>/usr/sbin/useradd -g 100 -d /dev/null -c < VAR
2001-06-01 15:50:38 +04:00
CLASS="REPLACEABLE"
2001-10-10 21:19:10 +04:00
>"machine
2003-03-18 19:48:14 +03:00
nickname"< /VAR
> -s /bin/false < VAR
2001-10-10 21:19:10 +04:00
CLASS="REPLACEABLE"
2003-03-18 19:48:14 +03:00
>machine_name< /VAR
2001-12-06 10:37:58 +03:00
>$ < /B
>< /P
2001-10-10 21:19:10 +04:00
>< P
2003-03-18 19:48:14 +03:00
>< SAMP
2001-10-10 21:19:10 +04:00
CLASS="PROMPT"
2003-03-18 19:48:14 +03:00
>root# < /SAMP
2001-12-06 10:37:58 +03:00
>< B
CLASS="COMMAND"
2003-03-18 19:48:14 +03:00
>passwd -l < VAR
2001-06-01 15:50:38 +04:00
CLASS="REPLACEABLE"
2003-03-18 19:48:14 +03:00
>machine_name< /VAR
2001-12-06 10:37:58 +03:00
>$< /B
>< /P
2001-04-20 01:33:44 +04:00
>< P
2002-11-06 01:28:45 +03:00
>On *BSD systems, this can be done using the 'chpass' utility:< /P
>< P
2003-03-18 19:48:14 +03:00
>< SAMP
2002-11-06 01:28:45 +03:00
CLASS="PROMPT"
2003-03-18 19:48:14 +03:00
>root# < /SAMP
2002-11-06 01:28:45 +03:00
>< B
CLASS="COMMAND"
2003-03-18 19:48:14 +03:00
>chpass -a "< VAR
2002-11-06 01:28:45 +03:00
CLASS="REPLACEABLE"
2003-03-18 19:48:14 +03:00
>machine_name< /VAR
>$:*:101:100::0:0:Workstation < VAR
2002-11-06 01:28:45 +03:00
CLASS="REPLACEABLE"
2003-03-18 19:48:14 +03:00
>machine_name< /VAR
2002-11-06 01:28:45 +03:00
>:/dev/null:/sbin/nologin"< /B
>< /P
>< P
2001-04-20 01:33:44 +04:00
>The < TT
CLASS="FILENAME"
>/etc/passwd< /TT
> entry will list the machine name
2001-12-06 10:37:58 +03:00
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
2001-04-20 01:33:44 +04:00
< TT
CLASS="FILENAME"
>/etc/passwd< /TT
2001-12-06 10:37:58 +03:00
> entry like this:< /P
2001-04-20 01:33:44 +04:00
>< P
>< PRE
CLASS="PROGRAMLISTING"
2003-03-18 19:48:14 +03:00
>doppy$:x:505:501:< VAR
2001-06-01 15:50:38 +04:00
CLASS="REPLACEABLE"
2003-03-18 19:48:14 +03:00
>machine_nickname< /VAR
2001-06-01 15:50:38 +04:00
>:/dev/null:/bin/false< /PRE
2001-04-20 01:33:44 +04:00
>< /P
>< P
2003-03-18 19:48:14 +03:00
>Above, < VAR
2001-06-01 15:50:38 +04:00
CLASS="REPLACEABLE"
2003-03-18 19:48:14 +03:00
>machine_nickname< /VAR
2001-12-06 10:37:58 +03:00
> can be any
descriptive name for the client, i.e., BasementComputer.
2003-03-18 19:48:14 +03:00
< VAR
2001-06-01 15:50:38 +04:00
CLASS="REPLACEABLE"
2003-03-18 19:48:14 +03:00
>machine_name< /VAR
2001-12-06 10:37:58 +03:00
> 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.< /P
>< P
>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 < A
HREF="smbpasswd.8.html"
2001-06-01 15:50:38 +04:00
TARGET="_top"
>< B
CLASS="COMMAND"
>smbpasswd(8)< /B
>< /A
> command
as shown here:< /P
2001-04-20 01:33:44 +04:00
>< P
2003-03-18 19:48:14 +03:00
>< SAMP
2001-04-20 01:33:44 +04:00
CLASS="PROMPT"
2003-03-18 19:48:14 +03:00
>root# < /SAMP
2001-12-06 10:37:58 +03:00
>< B
CLASS="COMMAND"
2003-03-18 19:48:14 +03:00
>smbpasswd -a -m < VAR
2001-04-20 01:33:44 +04:00
CLASS="REPLACEABLE"
2003-03-18 19:48:14 +03:00
>machine_name< /VAR
2001-12-06 10:37:58 +03:00
>< /B
2001-04-20 01:33:44 +04:00
>< /P
>< P
2003-03-18 19:48:14 +03:00
>where < VAR
2001-04-20 01:33:44 +04:00
CLASS="REPLACEABLE"
2003-03-18 19:48:14 +03:00
>machine_name< /VAR
2001-10-10 21:19:10 +04:00
> is the machine's NetBIOS
2001-12-06 10:37:58 +03:00
name. The RID of the new machine account is generated from the UID of
the corresponding Unix account.< /P
2001-06-01 15:50:38 +04:00
>< DIV
CLASS="WARNING"
2001-04-20 01:33:44 +04:00
>< P
2001-06-01 15:50:38 +04:00
>< /P
>< TABLE
CLASS="WARNING"
WIDTH="100%"
2002-11-06 01:28:45 +03:00
BORDER="0"
2001-06-01 15:50:38 +04:00
>< TR
>< TD
2002-11-06 01:28:45 +03:00
WIDTH="25"
2001-06-01 15:50:38 +04:00
ALIGN="CENTER"
2002-11-06 01:28:45 +03:00
VALIGN="TOP"
>< IMG
2003-02-19 01:14:04 +03:00
SRC="/usr/share/sgml/docbook/stylesheet/dsssl/modular/images/warning.gif"
2002-11-06 01:28:45 +03:00
HSPACE="5"
ALT="Warning">< /TD
>< TH
ALIGN="LEFT"
VALIGN="CENTER"
2001-06-01 15:50:38 +04:00
>< B
>Join the client to the domain immediately< /B
2002-11-06 01:28:45 +03:00
>< /TH
2001-06-01 15:50:38 +04:00
>< /TR
>< TR
>< TD
2002-11-06 01:28:45 +03:00
> < /TD
>< TD
2001-06-01 15:50:38 +04:00
ALIGN="LEFT"
2002-11-06 01:28:45 +03:00
VALIGN="TOP"
2001-06-01 15:50:38 +04:00
>< P
> Manually creating a machine trust account using this method is the
2001-12-06 10:37:58 +03:00
equivalent of creating a machine trust account on a Windows NT PDC using
2001-06-01 15:50:38 +04:00
the "Server Manager". From the time at which the account is created
2001-12-06 10:37:58 +03:00
to the time which the client joins the domain and changes the password,
2001-06-01 15:50:38 +04:00
your domain is vulnerable to an intruder joining your domain using a
2001-10-10 21:19:10 +04:00
a machine with the same NetBIOS name. A PDC inherently trusts
2001-06-01 15:50:38 +04:00
members of the domain and will serve out a large degree of user
information to such clients. You have been warned!
< /P
>< /TD
>< /TR
>< /TABLE
>< /DIV
>< /DIV
>< DIV
CLASS="SECT2"
2002-11-06 01:28:45 +03:00
>< H2
2001-06-01 15:50:38 +04:00
CLASS="SECT2"
>< A
2003-04-07 18:01:19 +04:00
NAME="AEN1049"
2003-03-30 15:22:22 +04:00
>6.4.2. "On-the-Fly" Creation of Machine Trust Accounts< /A
2003-03-18 19:48:14 +03:00
>< /H2
2001-06-01 15:50:38 +04:00
>< P
2001-12-06 10:37:58 +03:00
>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. < /P
>< P
>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
< A
2001-04-20 01:33:44 +04:00
HREF="smb.conf.5.html#ADDUSERSCRIPT"
TARGET="_top"
>add user script< /A
2001-12-06 10:37:58 +03:00
>
option in < TT
CLASS="FILENAME"
>smb.conf< /TT
>. This
method is not required, however; corresponding Unix accounts may also
be created manually.< /P
>< P
>Below is an example for a RedHat 6.2 Linux system.< /P
2001-04-20 01:33:44 +04:00
>< P
>< PRE
CLASS="PROGRAMLISTING"
2001-12-06 10:37:58 +03:00
>[global]
2003-03-18 19:48:14 +03:00
# < ...remainder of parameters...>
2001-12-06 10:37:58 +03:00
add user script = /usr/sbin/useradd -d /dev/null -g 100 -s /bin/false -M %u < /PRE
2001-04-20 01:33:44 +04:00
>< /P
2001-12-06 10:37:58 +03:00
>< /DIV
>< DIV
CLASS="SECT2"
2002-11-06 01:28:45 +03:00
>< H2
2001-12-06 10:37:58 +03:00
CLASS="SECT2"
>< A
2003-04-07 18:01:19 +04:00
NAME="AEN1058"
2003-03-30 15:22:22 +04:00
>6.4.3. Joining the Client to the Domain< /A
2003-03-18 19:48:14 +03:00
>< /H2
2001-04-20 01:33:44 +04:00
>< P
2001-12-06 10:37:58 +03:00
>The procedure for joining a client to the domain varies with the
version of Windows.< /P
>< P
>< /P
>< UL
>< LI
>< P
2002-11-06 01:28:45 +03:00
>< SPAN
CLASS="emphasis"
2001-12-06 10:37:58 +03:00
>< I
2001-04-20 01:33:44 +04:00
CLASS="EMPHASIS"
2001-12-06 10:37:58 +03:00
>Windows 2000< /I
2002-11-06 01:28:45 +03:00
>< /SPAN
2001-12-06 10:37:58 +03:00
>< /P
>< P
> 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
< TT
2001-04-20 01:33:44 +04:00
CLASS="FILENAME"
>/etc/passwd< /TT
2001-12-06 10:37:58 +03:00
> entry, for security
reasons. < /P
>< P
>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.< /P
>< /LI
>< LI
>< P
2002-11-06 01:28:45 +03:00
>< SPAN
CLASS="emphasis"
2001-12-06 10:37:58 +03:00
>< I
CLASS="EMPHASIS"
>Windows NT< /I
2002-11-06 01:28:45 +03:00
>< /SPAN
2001-12-06 10:37:58 +03:00
>< /P
>< P
> 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.< /P
>< P
> 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).< /P
>< /LI
>< /UL
2001-06-01 15:50:38 +04:00
>< /DIV
2001-04-20 01:33:44 +04:00
>< /DIV
>< DIV
CLASS="SECT1"
2002-11-06 01:28:45 +03:00
>< H1
2001-04-20 01:33:44 +04:00
CLASS="SECT1"
>< A
2003-04-07 18:01:19 +04:00
NAME="AEN1073"
2003-03-30 15:22:22 +04:00
>6.5. Common Problems and Errors< /A
2003-03-18 19:48:14 +03:00
>< /H1
2001-04-20 01:33:44 +04:00
>< P
>< /P
>< P
2001-06-01 15:50:38 +04:00
>< /P
>< UL
>< LI
>< P
2002-11-06 01:28:45 +03:00
> < SPAN
CLASS="emphasis"
>< I
2001-04-20 01:33:44 +04:00
CLASS="EMPHASIS"
>I cannot include a '$' in a machine name.< /I
2002-11-06 01:28:45 +03:00
>< /SPAN
2001-06-01 15:50:38 +04:00
>
< /P
2001-04-20 01:33:44 +04:00
>< P
2001-06-01 15:50:38 +04:00
> A 'machine name' in (typically) < TT
2001-04-20 01:33:44 +04:00
CLASS="FILENAME"
>/etc/passwd< /TT
>
2001-06-01 15:50:38 +04:00
of the machine name with a '$' appended. FreeBSD (and other BSD
2001-12-06 10:37:58 +03:00
systems?) won't create a user with a '$' in their name.
2001-06-01 15:50:38 +04:00
< /P
2001-04-20 01:33:44 +04:00
>< P
2001-06-01 15:50:38 +04:00
> The problem is only in the program used to make the entry, once
made, it works perfectly. So create a user without the '$' and
use < B
2001-04-20 01:33:44 +04:00
CLASS="COMMAND"
>vipw< /B
> to edit the entry, adding the '$'. Or create
2001-06-01 15:50:38 +04:00
the whole entry with vipw if you like, make sure you use a
2001-12-06 10:37:58 +03:00
unique User ID !
2001-06-01 15:50:38 +04:00
< /P
>< /LI
>< LI
2001-04-20 01:33:44 +04:00
>< P
2002-11-06 01:28:45 +03:00
> < SPAN
CLASS="emphasis"
>< I
2001-04-20 01:33:44 +04:00
CLASS="EMPHASIS"
>I get told "You already have a connection to the Domain...."
2001-06-01 15:50:38 +04:00
or "Cannot join domain, the credentials supplied conflict with an
2001-12-06 10:37:58 +03:00
existing set.." when creating a machine trust account.< /I
2002-11-06 01:28:45 +03:00
>< /SPAN
2001-06-01 15:50:38 +04:00
>
< /P
2001-04-20 01:33:44 +04:00
>< P
2001-12-06 10:37:58 +03:00
> This happens if you try to create a machine trust account from the
2001-06-01 15:50:38 +04:00
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:
< /P
2001-04-20 01:33:44 +04:00
>< P
2003-03-18 19:48:14 +03:00
> < SAMP
2001-06-01 15:50:38 +04:00
CLASS="PROMPT"
2003-03-18 19:48:14 +03:00
>C:\WINNT\> < /SAMP
2001-06-01 15:50:38 +04:00
> < B
CLASS="COMMAND"
>net use * /d< /B
>
< /P
2001-04-20 01:33:44 +04:00
>< P
2001-06-01 15:50:38 +04:00
> 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.
< /P
>< /LI
>< LI
2001-04-20 01:33:44 +04:00
>< P
2002-11-06 01:28:45 +03:00
> < SPAN
CLASS="emphasis"
>< I
2001-04-20 01:33:44 +04:00
CLASS="EMPHASIS"
2001-06-01 15:50:38 +04:00
>The system can not log you on (C000019B)....< /I
2002-11-06 01:28:45 +03:00
>< /SPAN
2001-06-01 15:50:38 +04:00
>
< /P
2001-04-20 01:33:44 +04:00
>< P
>I joined the domain successfully but after upgrading
2001-06-01 15:50:38 +04:00
to a newer version of the Samba code I get the message, "The system
2003-04-02 22:07:52 +04:00
can not log you on (C000019B), Please try again or consult your
2001-06-01 15:50:38 +04:00
system administrator" when attempting to logon.
< /P
2001-04-20 01:33:44 +04:00
>< P
2003-04-02 22:07:52 +04:00
> 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.
2001-06-01 15:50:38 +04:00
< /P
>< /LI
>< LI
>< P
2002-11-06 01:28:45 +03:00
> < SPAN
CLASS="emphasis"
>< I
2001-06-01 15:50:38 +04:00
CLASS="EMPHASIS"
2001-12-06 10:37:58 +03:00
>The machine trust account for this computer either does not
2001-06-01 15:50:38 +04:00
exist or is not accessible.< /I
2002-11-06 01:28:45 +03:00
>< /SPAN
2001-06-01 15:50:38 +04:00
>
< /P
>< P
> When I try to join the domain I get the message "The machine account
2001-12-06 10:37:58 +03:00
for this computer either does not exist or is not accessible". What's
2001-06-01 15:50:38 +04:00
wrong?
< /P
2001-04-20 01:33:44 +04:00
>< P
2001-12-06 10:37:58 +03:00
> This problem is caused by the PDC not having a suitable machine trust account.
2003-03-18 19:48:14 +03:00
If you are using the < VAR
2001-06-01 15:50:38 +04:00
CLASS="PARAMETER"
2003-03-18 19:48:14 +03:00
>add user script< /VAR
2001-06-01 15:50:38 +04:00
> method to create
accounts then this would indicate that it has not worked. Ensure the domain
admin user system is working.
< /P
>< P
> Alternatively if you are creating account entries manually then they
have not been created correctly. Make sure that you have the entry
2001-12-06 10:37:58 +03:00
correct for the machine trust account in smbpasswd file on the Samba PDC.
2001-06-01 15:50:38 +04:00
If you added the account using an editor rather than using the smbpasswd
2001-10-10 21:19:10 +04:00
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
2001-06-01 15:50:38 +04:00
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.
< /P
>< /LI
>< LI
>< P
2002-11-06 01:28:45 +03:00
> < SPAN
CLASS="emphasis"
>< I
2001-04-20 01:33:44 +04:00
CLASS="EMPHASIS"
2001-06-01 15:50:38 +04:00
>When I attempt to login to a Samba Domain from a NT4/W2K workstation,
I get a message about my account being disabled.< /I
2002-11-06 01:28:45 +03:00
>< /SPAN
2001-06-01 15:50:38 +04:00
>
< /P
2001-04-20 01:33:44 +04:00
>< P
2001-06-01 15:50:38 +04:00
> 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%
< /P
2001-04-20 01:33:44 +04:00
>< P
2001-06-01 15:50:38 +04:00
> At first be ensure to enable the useraccounts with < B
2001-04-20 01:33:44 +04:00
CLASS="COMMAND"
2001-06-01 15:50:38 +04:00
>smbpasswd -e
%user%< /B
2001-10-10 21:19:10 +04:00
>, this is normally done, when you create an account.
2001-06-01 15:50:38 +04:00
< /P
>< P
> In order to work around this problem in 2.2.0, configure the
2003-03-18 19:48:14 +03:00
< VAR
2001-06-01 15:50:38 +04:00
CLASS="PARAMETER"
2003-03-18 19:48:14 +03:00
>account< /VAR
2001-06-01 15:50:38 +04:00
> control flag in
< TT
CLASS="FILENAME"
>/etc/pam.d/samba< /TT
> file as follows:
< /P
>< P
>< PRE
CLASS="PROGRAMLISTING"
> account required pam_permit.so
< /PRE
>< /P
>< P
> If you want to remain backward compatibility to samba 2.0.x use
< TT
CLASS="FILENAME"
>pam_permit.so< /TT
>, it's also possible to use
< TT
CLASS="FILENAME"
>pam_pwdb.so< /TT
>. There are some bugs if you try to
use < TT
CLASS="FILENAME"
>pam_unix.so< /TT
>, if you need this, be ensure to use
the most recent version of this file.
< /P
>< /LI
>< /UL
2001-04-20 01:33:44 +04:00
>< /DIV
>< DIV
CLASS="SECT1"
2002-11-06 01:28:45 +03:00
>< H1
2001-04-20 01:33:44 +04:00
CLASS="SECT1"
>< A
2003-04-07 18:01:19 +04:00
NAME="AEN1119"
2003-04-02 22:07:52 +04:00
>6.6. What other help can I get?< /A
2003-03-18 19:48:14 +03:00
>< /H1
2001-04-20 01:33:44 +04:00
>< P
>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.< /P
>< P
2001-06-01 15:50:38 +04:00
>< /P
>< UL
>< LI
>< P
2002-11-06 01:28:45 +03:00
> < SPAN
CLASS="emphasis"
>< I
2001-04-20 01:33:44 +04:00
CLASS="EMPHASIS"
>What are some diagnostics tools I can use to debug the domain logon
2001-06-01 15:50:38 +04:00
process and where can I find them?< /I
2002-11-06 01:28:45 +03:00
>< /SPAN
2001-06-01 15:50:38 +04:00
>
< /P
2001-04-20 01:33:44 +04:00
>< P
> One of the best diagnostic tools for debugging problems is Samba itself.
2001-10-10 21:19:10 +04:00
You can use the -d option for both smbd and nmbd to specify what
2001-04-20 01:33:44 +04:00
'debug level' at which to run. See the man pages on smbd, nmbd and
smb.conf for more information on debugging options. The debug
level can range from 1 (the default) to 10 (100 for debugging passwords).
< /P
>< P
> Another helpful method of debugging is to compile samba using the
< B
CLASS="COMMAND"
>gcc -g < /B
> flag. This will include debug
information in the binaries and allow you to attach gdb to the
running smbd / nmbd process. In order to attach gdb to an smbd
process for an NT workstation, first get the workstation to make the
connection. Pressing ctrl-alt-delete and going down to the domain box
is sufficient (at least, on the first time you join the domain) to
generate a 'LsaEnumTrustedDomains'. Thereafter, the workstation
maintains an open connection, and therefore there will be an smbd
process running (assuming that you haven't set a really short smbd
idle timeout) So, in between pressing ctrl alt delete, and actually
typing in your password, you can gdb attach and continue.
< /P
>< P
> Some useful samba commands worth investigating:
< /P
>< P
>< /P
>< UL
>< LI
>< P
>testparam | more< /P
>< /LI
>< LI
>< P
>smbclient -L //{netbios name of server}< /P
>< /LI
>< /UL
>< P
> An SMB enabled version of tcpdump is available from
2001-06-01 15:50:38 +04:00
< A
2001-04-20 01:33:44 +04:00
HREF="http://www.tcpdump.org/"
TARGET="_top"
>http://www.tcpdup.org/< /A
>.
2001-12-06 10:37:58 +03:00
Ethereal, another good packet sniffer for Unix and Win32
2001-04-20 01:33:44 +04:00
hosts, can be downloaded from < A
HREF="http://www.ethereal.com/"
TARGET="_top"
>http://www.ethereal.com< /A
>.
< /P
>< P
> For tracing things on the Microsoft Windows NT, Network Monitor
(aka. netmon) is available on the Microsoft Developer Network CD's,
the Windows NT Server install CD and the SMS CD's. The version of
netmon that ships with SMS allows for dumping packets between any two
2001-10-10 21:19:10 +04:00
computers (i.e. placing the network interface in promiscuous mode).
2001-04-20 01:33:44 +04:00
The version on the NT Server install CD will only allow monitoring
of network traffic directed to the local NT box and broadcasts on the
local subnet. Be aware that Ethereal can read and write netmon
formatted files.
< /P
2001-06-01 15:50:38 +04:00
>< /LI
>< LI
>< P
2002-11-06 01:28:45 +03:00
> < SPAN
CLASS="emphasis"
>< I
2001-04-20 01:33:44 +04:00
CLASS="EMPHASIS"
>How do I install 'Network Monitor' on an NT Workstation
2001-06-01 15:50:38 +04:00
or a Windows 9x box?< /I
2002-11-06 01:28:45 +03:00
>< /SPAN
2001-06-01 15:50:38 +04:00
>
< /P
2001-04-20 01:33:44 +04:00
>< P
> Installing netmon on an NT workstation requires a couple
of steps. The following are for installing Netmon V4.00.349, which comes
with Microsoft Windows NT Server 4.0, on Microsoft Windows NT
Workstation 4.0. The process should be similar for other version of
Windows NT / Netmon. You will need both the Microsoft Windows
NT Server 4.0 Install CD and the Workstation 4.0 Install CD.
< /P
>< P
> Initially you will need to install 'Network Monitor Tools and Agent'
on the NT Server. To do this
< /P
>< P
>< /P
>< UL
>< LI
>< P
>Goto Start - Settings - Control Panel -
Network - Services - Add < /P
>< /LI
>< LI
>< P
>Select the 'Network Monitor Tools and Agent' and
click on 'OK'.< /P
>< /LI
>< LI
>< P
>Click 'OK' on the Network Control Panel.
< /P
>< /LI
>< LI
>< P
>Insert the Windows NT Server 4.0 install CD
when prompted.< /P
>< /LI
>< /UL
>< P
> At this point the Netmon files should exist in
< TT
CLASS="FILENAME"
>%SYSTEMROOT%\System32\netmon\*.*< /TT
>.
Two subdirectories exist as well, < TT
CLASS="FILENAME"
>parsers\< /TT
>
which contains the necessary DLL's for parsing the netmon packet
dump, and < TT
CLASS="FILENAME"
>captures\< /TT
>.
< /P
>< P
> In order to install the Netmon tools on an NT Workstation, you will
first need to install the 'Network Monitor Agent' from the Workstation
install CD.
< /P
>< P
>< /P
>< UL
>< LI
>< P
>Goto Start - Settings - Control Panel -
Network - Services - Add< /P
>< /LI
>< LI
>< P
>Select the 'Network Monitor Agent' and click
on 'OK'.< /P
>< /LI
>< LI
>< P
>Click 'OK' on the Network Control Panel.
< /P
>< /LI
>< LI
>< P
>Insert the Windows NT Workstation 4.0 install
CD when prompted.< /P
>< /LI
>< /UL
>< P
> Now copy the files from the NT Server in %SYSTEMROOT%\System32\netmon\*.*
to %SYSTEMROOT%\System32\netmon\*.* on the Workstation and set
permissions as you deem appropriate for your site. You will need
administrative rights on the NT box to run netmon.
< /P
>< P
> To install Netmon on a Windows 9x box install the network monitor agent
from the Windows 9x CD (\admin\nettools\netmon). There is a readme
file located with the netmon driver files on the CD if you need
information on how to do this. Copy the files from a working
Netmon installation.
< /P
2001-06-01 15:50:38 +04:00
>< /LI
>< LI
>< P
> The following is a list if helpful URLs and other links:
< /P
2001-04-20 01:33:44 +04:00
>< P
>< /P
>< UL
>< LI
>< P
>Home of Samba site < A
HREF="http://samba.org"
TARGET="_top"
> http://samba.org< /A
>. We have a mirror near you !< /P
>< /LI
>< LI
>< P
2002-11-06 01:28:45 +03:00
> The < SPAN
CLASS="emphasis"
>< I
2001-04-20 01:33:44 +04:00
CLASS="EMPHASIS"
>Development< /I
2002-11-06 01:28:45 +03:00
>< /SPAN
2001-04-20 01:33:44 +04:00
> document
on the Samba mirrors might mention your problem. If so,
it might mean that the developers are working on it.< /P
>< /LI
>< LI
>< P
>See how Scott Merrill simulates a BDC behavior at
< A
HREF="http://www.skippy.net/linux/smb-howto.html"
TARGET="_top"
> http://www.skippy.net/linux/smb-howto.html< /A
>. < /P
>< /LI
>< LI
>< P
>Although 2.0.7 has almost had its day as a PDC, David Bannon will
keep the 2.0.7 PDC pages at < A
HREF="http://bioserve.latrobe.edu.au/samba"
TARGET="_top"
> http://bioserve.latrobe.edu.au/samba< /A
> going for a while yet.< /P
>< /LI
>< LI
>< P
>Misc links to CIFS information
< A
HREF="http://samba.org/cifs/"
TARGET="_top"
>http://samba.org/cifs/< /A
>< /P
>< /LI
>< LI
>< P
>NT Domains for Unix < A
HREF="http://mailhost.cb1.com/~lkcl/ntdom/"
TARGET="_top"
> http://mailhost.cb1.com/~lkcl/ntdom/< /A
>< /P
>< /LI
>< LI
>< P
>FTP site for older SMB specs:
< A
HREF="ftp://ftp.microsoft.com/developr/drg/CIFS/"
TARGET="_top"
> ftp://ftp.microsoft.com/developr/drg/CIFS/< /A
>< /P
>< /LI
>< /UL
2001-06-01 15:50:38 +04:00
>< /LI
>< /UL
2001-04-20 01:33:44 +04:00
>< P
2001-06-01 15:50:38 +04:00
>< /P
>< UL
>< LI
>< P
2002-11-06 01:28:45 +03:00
> < SPAN
CLASS="emphasis"
>< I
2001-04-20 01:33:44 +04:00
CLASS="EMPHASIS"
2001-12-06 10:37:58 +03:00
>How do I get help from the mailing lists?< /I
2002-11-06 01:28:45 +03:00
>< /SPAN
2001-06-01 15:50:38 +04:00
>
< /P
2001-04-20 01:33:44 +04:00
>< P
2001-06-01 15:50:38 +04:00
> There are a number of Samba related mailing lists. Go to < A
2001-04-20 01:33:44 +04:00
HREF="http://samba.org"
TARGET="_top"
>http://samba.org< /A
>, click on your nearest mirror
2001-06-01 15:50:38 +04:00
and then click on < B
2001-04-20 01:33:44 +04:00
CLASS="COMMAND"
>Support< /B
> and then click on < B
CLASS="COMMAND"
2001-06-01 15:50:38 +04:00
> Samba related mailing lists< /B
>.
< /P
2001-04-20 01:33:44 +04:00
>< P
2001-06-01 15:50:38 +04:00
> For questions relating to Samba TNG go to
< A
2001-04-20 01:33:44 +04:00
HREF="http://www.samba-tng.org/"
TARGET="_top"
>http://www.samba-tng.org/< /A
>
2001-06-01 15:50:38 +04:00
It has been requested that you don't post questions about Samba-TNG to the
main stream Samba lists.< /P
2001-04-20 01:33:44 +04:00
>< P
2001-06-01 15:50:38 +04:00
> If you post a message to one of the lists please observe the following guide lines :
< /P
2001-04-20 01:33:44 +04:00
>< P
>< /P
>< UL
>< LI
>< P
> Always remember that the developers are volunteers, they are
not paid and they never guarantee to produce a particular feature at
a particular time. Any time lines are 'best guess' and nothing more.
< /P
>< /LI
>< LI
>< P
> Always mention what version of samba you are using and what
operating system its running under. You should probably list the
relevant sections of your smb.conf file, at least the options
in [global] that affect PDC support.< /P
>< /LI
>< LI
>< P
>In addition to the version, if you obtained Samba via
CVS mention the date when you last checked it out.< /P
>< /LI
>< LI
>< P
> Try and make your question clear and brief, lots of long,
convoluted questions get deleted before they are completely read !
Don't post html encoded messages (if you can select colour or font
size its html).< /P
>< /LI
>< LI
>< P
> If you run one of those nifty 'I'm on holidays' things when
you are away, make sure its configured to not answer mailing lists.
< /P
>< /LI
>< LI
>< P
> Don't cross post. Work out which is the best list to post to
2001-10-10 21:19:10 +04:00
and see what happens, i.e. don't post to both samba-ntdom and samba-technical.
2001-04-20 01:33:44 +04:00
Many people active on the lists subscribe to more
than one list and get annoyed to see the same message two or more times.
Often someone will see a message and thinking it would be better dealt
with on another, will forward it on for you.< /P
>< /LI
>< LI
>< P
2002-11-06 01:28:45 +03:00
>You might include < SPAN
CLASS="emphasis"
>< I
2001-04-20 01:33:44 +04:00
CLASS="EMPHASIS"
>partial< /I
2002-11-06 01:28:45 +03:00
>< /SPAN
2001-04-20 01:33:44 +04:00
>
log files written at a debug level set to as much as 20.
Please don't send the entire log but enough to give the context of the
error messages.< /P
>< /LI
>< LI
>< P
>(Possibly) If you have a complete netmon trace ( from the opening of
the pipe to the error ) you can send the *.CAP file as well.< /P
>< /LI
>< LI
>< P
>Please think carefully before attaching a document to an email.
Consider pasting the relevant parts into the body of the message. The samba
mailing lists go to a huge number of people, do they all need a copy of your
2001-12-06 10:37:58 +03:00
smb.conf in their attach directory?< /P
2001-04-20 01:33:44 +04:00
>< /LI
>< /UL
2001-06-01 15:50:38 +04:00
>< /LI
>< LI
2001-04-20 01:33:44 +04:00
>< P
2002-11-06 01:28:45 +03:00
> < SPAN
CLASS="emphasis"
>< I
2001-04-20 01:33:44 +04:00
CLASS="EMPHASIS"
2001-12-06 10:37:58 +03:00
>How do I get off the mailing lists?< /I
2002-11-06 01:28:45 +03:00
>< /SPAN
2001-06-01 15:50:38 +04:00
>
< /P
2001-04-20 01:33:44 +04:00
>< P
>To have your name removed from a samba mailing list, go to the
2001-06-01 15:50:38 +04:00
same place you went to to get on it. Go to < A
2001-04-20 01:33:44 +04:00
HREF="http://lists.samba.org/"
TARGET="_top"
>http://lists.samba.org< /A
2001-06-01 15:50:38 +04:00
>,
click on your nearest mirror and then click on < B
2001-04-20 01:33:44 +04:00
CLASS="COMMAND"
>Support< /B
> and
2001-06-01 15:50:38 +04:00
then click on < B
2001-04-20 01:33:44 +04:00
CLASS="COMMAND"
> Samba related mailing lists< /B
>. Or perhaps see
2001-06-01 15:50:38 +04:00
< A
2001-04-20 01:33:44 +04:00
HREF="http://lists.samba.org/mailman/roster/samba-ntdom"
TARGET="_top"
>here< /A
2001-06-01 15:50:38 +04:00
>
< /P
2001-04-20 01:33:44 +04:00
>< P
> Please don't post messages to the list asking to be removed, you will just
2001-06-01 15:50:38 +04:00
be referred to the above address (unless that process failed in some way...)
< /P
>< /LI
>< /UL
>< /DIV
>< DIV
CLASS="SECT1"
2002-11-06 01:28:45 +03:00
>< H1
2001-06-01 15:50:38 +04:00
CLASS="SECT1"
>< A
2003-04-07 18:01:19 +04:00
NAME="AEN1233"
2003-04-02 22:07:52 +04:00
>6.7. Domain Control for Windows 9x/ME< /A
2003-03-18 19:48:14 +03:00
>< /H1
2001-06-01 15:50:38 +04:00
>< P
>A domain and a workgroup are exactly the same thing in terms of network
browsing. The difference is that a distributable authentication
database is associated with a domain, for secure login access to a
network. Also, different access rights can be granted to users if they
2003-04-02 22:07:52 +04:00
successfully authenticate against a domain logon server. Samba-3 does this
now in the same way that MS Windows NT/2K.< /P
2001-06-01 15:50:38 +04:00
>< P
>The SMB client logging on to a domain has an expectation that every other
server in the domain should accept the same authentication information.
2003-04-02 22:07:52 +04:00
Network browsing functionality of domains and workgroups is identical and
is explained in this documentation under the browsing discussions.
It should be noted, that browsing is totally orthogonal to logon support.< /P
2001-06-01 15:50:38 +04:00
>< P
>Issues related to the single-logon network model are discussed in this
2001-12-06 10:37:58 +03:00
section. Samba supports domain logons, network logon scripts, and user
profiles for MS Windows for workgroups and MS Windows 9X/ME clients
2003-04-02 22:07:52 +04:00
which are the focus of this section.< /P
2001-06-01 15:50:38 +04:00
>< P
>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
password using whatever mechanism the Samba administrator has installed.
It is possible (but very stupid) to create a domain where the user
2001-10-10 21:19:10 +04:00
database is not shared between servers, i.e. they are effectively workgroup
2001-06-01 15:50:38 +04:00
servers advertising themselves as participating in a domain. This
demonstrates how authentication is quite different from but closely
involved with domains.< /P
>< P
>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.< /P
>< P
2001-12-06 10:37:58 +03:00
>Before launching into the configuration instructions, it is
worthwhile lookingat how a Windows 9x/ME client performs a logon:< /P
2001-06-01 15:50:38 +04:00
>< P
>< /P
>< OL
TYPE="1"
>< LI
>< P
> The client broadcasts (to the IP broadcast address of the subnet it is in)
2003-03-18 19:48:14 +03:00
a NetLogon request. This is sent to the NetBIOS name DOMAIN< 1c> at the
2001-06-01 15:50:38 +04:00
NetBIOS layer. The client chooses the first response it receives, which
contains the NetBIOS name of the logon server to use in the format of
\\SERVER.
< /P
>< /LI
>< LI
>< P
> The client then connects to that server, logs on (does an SMBsessetupX) and
then connects to the IPC$ share (using an SMBtconX).
< /P
>< /LI
>< LI
>< P
> The client then does a NetWkstaUserLogon request, which retrieves the name
of the user's logon script.
< /P
>< /LI
>< LI
>< P
> The client then connects to the NetLogon share and searches for this
and if it is found and can be read, is retrieved and executed by the client.
After this, the client disconnects from the NetLogon share.
< /P
>< /LI
>< LI
>< P
> The client then sends a NetUserGetInfo request to the server, to retrieve
the user's home share, which is used to search for profiles. Since the
response to the NetUserGetInfo request does not contain much more
the user's home share, profiles for Win9X clients MUST reside in the user
home directory.
< /P
>< /LI
>< LI
>< P
> The client then connects to the user's home share and searches for the
2001-10-10 21:19:10 +04:00
user's profile. As it turns out, you can specify the user's home share as
2001-06-01 15:50:38 +04:00
a sharename and path. For example, \\server\fred\.profile.
If the profiles are found, they are implemented.
< /P
>< /LI
>< LI
>< P
> The client then disconnects from the user's home share, and reconnects to
the NetLogon share and looks for CONFIG.POL, the policies file. If this is
found, it is read and implemented.
< /P
>< /LI
>< /OL
>< DIV
CLASS="SECT2"
2002-11-06 01:28:45 +03:00
>< H2
2001-06-01 15:50:38 +04:00
CLASS="SECT2"
>< A
2003-04-07 18:01:19 +04:00
NAME="AEN1256"
2003-04-02 22:07:52 +04:00
>6.7.1. Configuration Instructions: Network Logons< /A
2003-03-18 19:48:14 +03:00
>< /H2
2001-06-01 15:50:38 +04:00
>< P
2001-12-06 10:37:58 +03:00
>The main difference between a PDC and a Windows 9x logon
server configuration is that< /P
2001-06-01 15:50:38 +04:00
>< P
>< /P
2001-12-06 10:37:58 +03:00
>< UL
2001-06-01 15:50:38 +04:00
>< LI
>< P
2001-12-06 10:37:58 +03:00
>Password encryption is not required for a Windows 9x logon server.< /P
2001-06-01 15:50:38 +04:00
>< /LI
>< LI
>< P
2001-12-06 10:37:58 +03:00
>Windows 9x/ME clients do not possess machine trust accounts.< /P
2001-06-01 15:50:38 +04:00
>< /LI
2001-12-06 10:37:58 +03:00
>< /UL
2001-06-01 15:50:38 +04:00
>< P
2001-12-06 10:37:58 +03:00
>Therefore, a Samba PDC will also act as a Windows 9x logon
server.< /P
2001-06-01 15:50:38 +04:00
>< DIV
CLASS="WARNING"
>< P
>< /P
>< TABLE
CLASS="WARNING"
WIDTH="100%"
2002-11-06 01:28:45 +03:00
BORDER="0"
2001-06-01 15:50:38 +04:00
>< TR
>< TD
2002-11-06 01:28:45 +03:00
WIDTH="25"
2001-06-01 15:50:38 +04:00
ALIGN="CENTER"
2002-11-06 01:28:45 +03:00
VALIGN="TOP"
>< IMG
2003-02-19 01:14:04 +03:00
SRC="/usr/share/sgml/docbook/stylesheet/dsssl/modular/images/warning.gif"
2002-11-06 01:28:45 +03:00
HSPACE="5"
ALT="Warning">< /TD
>< TH
ALIGN="LEFT"
VALIGN="CENTER"
2001-06-01 15:50:38 +04:00
>< B
>security mode and master browsers< /B
2002-11-06 01:28:45 +03:00
>< /TH
2001-06-01 15:50:38 +04:00
>< /TR
>< TR
>< TD
2002-11-06 01:28:45 +03:00
> < /TD
>< TD
2001-06-01 15:50:38 +04:00
ALIGN="LEFT"
2002-11-06 01:28:45 +03:00
VALIGN="TOP"
2001-06-01 15:50:38 +04:00
>< P
>There are a few comments to make in order to tie up some
loose ends. There has been much debate over the issue of whether
or not it is ok to configure Samba as a Domain Controller in security
2003-03-18 19:48:14 +03:00
modes other than < CODE
2001-06-01 15:50:38 +04:00
CLASS="CONSTANT"
2003-03-18 19:48:14 +03:00
>USER< /CODE
2001-06-01 15:50:38 +04:00
>. The only security mode
2003-03-18 19:48:14 +03:00
which will not work due to technical reasons is < CODE
2001-06-01 15:50:38 +04:00
CLASS="CONSTANT"
2003-03-18 19:48:14 +03:00
>SHARE< /CODE
2001-06-01 15:50:38 +04:00
>
2003-03-18 19:48:14 +03:00
mode security. < CODE
2001-06-01 15:50:38 +04:00
CLASS="CONSTANT"
2003-03-18 19:48:14 +03:00
>DOMAIN< /CODE
> and < CODE
2001-06-01 15:50:38 +04:00
CLASS="CONSTANT"
2003-03-18 19:48:14 +03:00
>SERVER< /CODE
2001-06-01 15:50:38 +04:00
>
mode security is really just a variation on SMB user level security.< /P
>< P
2001-12-06 10:37:58 +03:00
>Actually, this issue is also closely tied to the debate on whether
2001-06-01 15:50:38 +04:00
or not Samba must be the domain master browser for its workgroup
when operating as a DC. While it may technically be possible
to configure a server as such (after all, browsing and domain logons
are two distinctly different functions), it is not a good idea to
2001-10-10 21:19:10 +04:00
so. You should remember that the DC must register the DOMAIN#1b NetBIOS
2001-06-01 15:50:38 +04:00
name. This is the name used by Windows clients to locate the DC.
Windows clients do not distinguish between the DC and the DMB.
For this reason, it is very wise to configure the Samba DC as the DMB.< /P
>< P
>Now back to the issue of configuring a Samba DC to use a mode other
than "security = user". If a Samba host is configured to use
another SMB server or DC in order to validate user connection
requests, then it is a fact that some other machine on the network
(the "password server") knows more about user than the Samba host.
99% of the time, this other host is a domain controller. Now
in order to operate in domain mode security, the "workgroup" parameter
must be set to the name of the Windows NT domain (which already
has a domain controller, right?)< /P
>< P
>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.< /P
>< /TD
>< /TR
>< /TABLE
>< /DIV
>< /DIV
2001-04-20 01:33:44 +04:00
>< /DIV
>< /DIV
2002-11-06 01:28:45 +03:00
>< DIV
CLASS="NAVFOOTER"
>< HR
ALIGN="LEFT"
WIDTH="100%">< TABLE
SUMMARY="Footer navigation table"
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
CELLSPACING="0"
>< TR
>< TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
>< A
2002-11-13 18:34:49 +03:00
HREF="securitylevels.html"
2002-11-06 01:28:45 +03:00
ACCESSKEY="P"
>Prev< /A
>< /TD
>< TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
>< A
HREF="samba-howto-collection.html"
ACCESSKEY="H"
>Home< /A
>< /TD
>< TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
>< A
HREF="samba-bdc.html"
ACCESSKEY="N"
>Next< /A
>< /TD
>< /TR
>< TR
>< TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
2003-04-02 22:07:52 +04:00
>Samba as Stand-Alone Server< /TD
2002-11-06 01:28:45 +03:00
>< TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
>< A
2002-11-13 18:34:49 +03:00
HREF="type.html"
2002-11-06 01:28:45 +03:00
ACCESSKEY="U"
>Up< /A
>< /TD
>< TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
2003-04-02 22:07:52 +04:00
>Samba Backup Domain Controller to Samba Domain Control< /TD
2002-11-06 01:28:45 +03:00
>< /TR
>< /TABLE
>< /DIV
2001-04-20 01:33:44 +04:00
>< /BODY
>< /HTML
>
