From cd6517abeae38753494fcd64acabe7d15f779864 Mon Sep 17 00:00:00 2001 From: bubulle Date: Sun, 13 Jul 2008 06:30:49 +0000 Subject: merge upstream 3.0.31 git-svn-id: svn://svn.debian.org/svn/pkg-samba/trunk/samba@2035 fc4039ab-9d04-0410-8cac-899223bdd6b0 --- docs/htmldocs/Samba3-HOWTO/AccessControls.html | 304 ++--- .../Samba3-HOWTO/AdvancedNetworkManagement.html | 124 +- docs/htmldocs/Samba3-HOWTO/Appendix.html | 2 +- docs/htmldocs/Samba3-HOWTO/Backup.html | 90 +- docs/htmldocs/Samba3-HOWTO/CUPS-printing.html | 1257 ++++++++++---------- docs/htmldocs/Samba3-HOWTO/ChangeNotes.html | 104 +- docs/htmldocs/Samba3-HOWTO/ClientConfig.html | 248 ++-- docs/htmldocs/Samba3-HOWTO/DNSDHCP.html | 44 +- docs/htmldocs/Samba3-HOWTO/FastStart.html | 94 +- docs/htmldocs/Samba3-HOWTO/InterdomainTrusts.html | 268 ++--- docs/htmldocs/Samba3-HOWTO/IntroSMB.html | 8 +- docs/htmldocs/Samba3-HOWTO/NT4Migration.html | 188 +-- docs/htmldocs/Samba3-HOWTO/NetCommand.html | 324 ++--- docs/htmldocs/Samba3-HOWTO/NetworkBrowsing.html | 854 ++++++------- docs/htmldocs/Samba3-HOWTO/Other-Clients.html | 40 +- docs/htmldocs/Samba3-HOWTO/PolicyMgmt.html | 228 ++-- docs/htmldocs/Samba3-HOWTO/Portability.html | 30 +- docs/htmldocs/Samba3-HOWTO/ProfileMgmt.html | 266 ++--- docs/htmldocs/Samba3-HOWTO/SWAT.html | 116 +- docs/htmldocs/Samba3-HOWTO/SambaHA.html | 218 ++-- docs/htmldocs/Samba3-HOWTO/ServerType.html | 210 ++-- docs/htmldocs/Samba3-HOWTO/StandAloneServer.html | 148 +-- docs/htmldocs/Samba3-HOWTO/TOSHpreface.html | 4 +- docs/htmldocs/Samba3-HOWTO/VFS.html | 228 ++-- docs/htmldocs/Samba3-HOWTO/apa.html | 94 +- docs/htmldocs/Samba3-HOWTO/bugreport.html | 64 +- docs/htmldocs/Samba3-HOWTO/cfgsmarts.html | 154 +-- docs/htmldocs/Samba3-HOWTO/ch-ldap-tls.html | 46 +- docs/htmldocs/Samba3-HOWTO/ch46.html | 106 -- docs/htmldocs/Samba3-HOWTO/ch47.html | 106 ++ docs/htmldocs/Samba3-HOWTO/classicalprinting.html | 444 +++---- docs/htmldocs/Samba3-HOWTO/compiling.html | 74 +- docs/htmldocs/Samba3-HOWTO/diagnosis.html | 122 +- docs/htmldocs/Samba3-HOWTO/domain-member.html | 684 +++++------ docs/htmldocs/Samba3-HOWTO/go01.html | 2 +- docs/htmldocs/Samba3-HOWTO/groupmapping.html | 258 ++-- docs/htmldocs/Samba3-HOWTO/idmapper.html | 452 +++---- docs/htmldocs/Samba3-HOWTO/index.html | 54 +- docs/htmldocs/Samba3-HOWTO/install.html | 140 +-- .../Samba3-HOWTO/integrate-ms-networks.html | 166 +-- docs/htmldocs/Samba3-HOWTO/introduction.html | 4 +- docs/htmldocs/Samba3-HOWTO/ix01.html | 18 +- docs/htmldocs/Samba3-HOWTO/largefile.html | 36 +- docs/htmldocs/Samba3-HOWTO/locking.html | 234 ++-- docs/htmldocs/Samba3-HOWTO/migration.html | 2 +- docs/htmldocs/Samba3-HOWTO/msdfs.html | 144 +-- docs/htmldocs/Samba3-HOWTO/optional.html | 10 +- docs/htmldocs/Samba3-HOWTO/pam.html | 194 +-- docs/htmldocs/Samba3-HOWTO/passdb.html | 912 +++++++------- docs/htmldocs/Samba3-HOWTO/pr02.html | 14 +- docs/htmldocs/Samba3-HOWTO/pr03.html | 2 +- docs/htmldocs/Samba3-HOWTO/problems.html | 102 +- docs/htmldocs/Samba3-HOWTO/rights.html | 342 +++--- docs/htmldocs/Samba3-HOWTO/samba-bdc.html | 382 +++--- docs/htmldocs/Samba3-HOWTO/samba-pdc.html | 526 ++++---- docs/htmldocs/Samba3-HOWTO/securing-samba.html | 186 +-- docs/htmldocs/Samba3-HOWTO/speed.html | 58 +- docs/htmldocs/Samba3-HOWTO/troubleshooting.html | 2 +- docs/htmldocs/Samba3-HOWTO/type.html | 4 +- docs/htmldocs/Samba3-HOWTO/unicode.html | 130 +- docs/htmldocs/Samba3-HOWTO/upgrading-to-3.0.html | 208 ++-- docs/htmldocs/Samba3-HOWTO/winbind.html | 586 ++++----- 62 files changed, 6213 insertions(+), 6246 deletions(-) delete mode 100644 docs/htmldocs/Samba3-HOWTO/ch46.html create mode 100644 docs/htmldocs/Samba3-HOWTO/ch47.html (limited to 'docs/htmldocs/Samba3-HOWTO') diff --git a/docs/htmldocs/Samba3-HOWTO/AccessControls.html b/docs/htmldocs/Samba3-HOWTO/AccessControls.html index a0425047be..c3872f77a8 100644 --- a/docs/htmldocs/Samba3-HOWTO/AccessControls.html +++ b/docs/htmldocs/Samba3-HOWTO/AccessControls.html @@ -1,59 +1,59 @@ -Chapter 16. File, Directory, and Share Access Controls
Chapter 16. File, Directory, and Share Access Controls
Prev Part III. Advanced Configuration Next

Chapter 16. File, Directory, and Share Access Controls

John H. Terpstra

Samba Team

Jeremy Allison

Samba Team

Jelmer R. Vernooij

drawing 
The Samba Team

May 10, 2003

Table of Contents

Features and Benefits
File System Access Controls
MS Windows NTFS Comparison with UNIX File Systems
Managing Directories
File and Directory Access Control
Share Definition Access Controls
User- and Group-Based Controls
File and Directory Permissions-Based Controls
Miscellaneous Controls
Access Controls on Shares
Share Permissions Management
MS Windows Access Control Lists and UNIX Interoperability
Managing UNIX Permissions Using NT Security Dialogs
Viewing File Security on a Samba Share
Viewing File Ownership
Viewing File or Directory Permissions
Modifying File or Directory Permissions
Interaction with the Standard Samba “create mask” Parameters
Interaction with the Standard Samba File Attribute Mapping
Windows NT/200X ACLs and POSIX ACLs Limitations
Common Errors
Users Cannot Write to a Public Share
File Operations Done as root with force user Set
MS Word with Samba Changes Owner of File

- - - - +Chapter 16. File, Directory, and Share Access Controls

Chapter 16. File, Directory, and Share Access Controls
Prev Part III. Advanced Configuration Next

Chapter 16. File, Directory, and Share Access Controls

John H. Terpstra

Samba Team

Jeremy Allison

Samba Team

Jelmer R. Vernooij

drawing 
The Samba Team

May 10, 2003

Table of Contents

Features and Benefits
File System Access Controls
MS Windows NTFS Comparison with UNIX File Systems
Managing Directories
File and Directory Access Control
Share Definition Access Controls
User- and Group-Based Controls
File and Directory Permissions-Based Controls
Miscellaneous Controls
Access Controls on Shares
Share Permissions Management
MS Windows Access Control Lists and UNIX Interoperability
Managing UNIX Permissions Using NT Security Dialogs
Viewing File Security on a Samba Share
Viewing File Ownership
Viewing File or Directory Permissions
Modifying File or Directory Permissions
Interaction with the Standard Samba “create mask” Parameters
Interaction with the Standard Samba File Attribute Mapping
Windows NT/200X ACLs and POSIX ACLs Limitations
Common Errors
Users Cannot Write to a Public Share
File Operations Done as root with force user Set
MS Word with Samba Changes Owner of File

+ + + + Advanced MS Windows users are frequently perplexed when file, directory, and share manipulation of resources shared via Samba do not behave in the manner they might expect. MS Windows network administrators are often confused regarding network access controls and how to provide users with the access they need while protecting resources from unauthorized access.

- - + + Many UNIX administrators are unfamiliar with the MS Windows environment and in particular have difficulty in visualizing what the MS Windows user wishes to achieve in attempts to set file and directory access permissions.

- - - - + + + + The problem lies in the differences in how file and directory permissions and controls work between the two environments. This difference is one that Samba cannot completely hide, even though it does try to bridge the chasm to a degree.

- - - - + + + + POSIX Access Control List technology has been available (along with extended attributes) for UNIX for many years, yet there is little evidence today of any significant use. This explains to some extent the slow adoption of ACLs into commercial Linux products. MS Windows administrators are astounded at this, given that ACLs were a foundational capability of the now decade-old MS Windows NT operating system.

- + The purpose of this chapter is to present each of the points of control that are possible with Samba-3 in the hope that this will help the network administrator to find the optimum method for delivering the best environment for MS Windows desktop users.

- - + + This is an opportune point to mention that Samba was created to provide a means of interoperability and interchange of data between differing operating environments. Samba has no intent to change UNIX/Linux into a platform like MS Windows. Instead the purpose was and is to provide a sufficient level of exchange of data between the two environments. What is available today extends well beyond early plans and expectations, yet the gap continues to shrink. -

Features and Benefits

+

Features and Benefits

Samba offers much flexibility in file system access management. These are the key access control facilities present in Samba today:

Samba Access Control Facilities

  • - + UNIX File and Directory Permissions

    - - - + + + Samba honors and implements UNIX file system access controls. Users who access a Samba server will do so as a particular MS Windows user. This information is passed to the Samba server as part of the logon or @@ -64,7 +64,7 @@ beyond early plans and expectations, yet the gap continues to shrink.

  • Samba Share Definitions

    - + In configuring share settings and controls in the smb.conf file, the network administrator can exercise overrides to native file system permissions and behaviors. This can be handy and convenient @@ -73,20 +73,20 @@ beyond early plans and expectations, yet the gap continues to shrink. The basic options and techniques are described herein.

  • Samba Share ACLs - +

    - + Just as it is possible in MS Windows NT to set ACLs on shares themselves, so it is possible to do in Samba. Few people make use of this facility, yet it remains one of the easiest ways to affect access controls (restrictions) and can often do so with minimum invasiveness compared with other methods.

  • - - + + MS Windows ACLs through UNIX POSIX ACLs

    - + The use of POSIX ACLs on UNIX/Linux is possible only if the underlying operating system supports them. If not, then this option will not be available to you. Current UNIX technology platforms have native support @@ -94,16 +94,16 @@ beyond early plans and expectations, yet the gap continues to shrink. this support. Sadly, few Linux platforms ship today with native ACLs and extended attributes enabled. This chapter has pertinent information for users of platforms that support them. -

File System Access Controls

+

File System Access Controls

Perhaps the most important recognition to be made is the simple fact that MS Windows NT4/200x/XP implement a totally divergent file system technology from what is provided in the UNIX operating system environment. First we consider what the most significant differences are, then we look at how Samba helps to bridge the differences. -

MS Windows NTFS Comparison with UNIX File Systems

- - - - +

MS Windows NTFS Comparison with UNIX File Systems

+ + + + Samba operates on top of the UNIX file system. This means it is subject to UNIX file system conventions and permissions. It also means that if the MS Windows networking environment requires file system behavior, that differs from UNIX file system behavior then somehow Samba is responsible for emulating @@ -114,7 +114,7 @@ at how Samba helps to bridge the differences. but for the greater part we stay within the bounds of default behavior. Those wishing to explore the depths of control ability should review the smb.conf man page.

The following compares file system features for UNIX with those of MS Windows NT/200x: - +

Name Space

MS Windows NT4/200x/XP file names may be up to 254 characters long, and UNIX file names @@ -123,8 +123,8 @@ at how Samba helps to bridge the differences.

What MS Windows calls a folder, UNIX calls a directory.

Case Sensitivity

- - + + MS Windows file names are generally uppercase if made up of 8.3 (8-character file name and 3 character extension. File names that are longer than 8.3 are case preserving and case insensitive. @@ -151,26 +151,26 @@ at how Samba helps to bridge the differences. event that the UNIX directory contains multiple files that would match a case insensitive file listing.

Directory Separators

- + MS Windows and DOS use the backslash \ as a directory delimiter, and UNIX uses the forward-slash / as its directory delimiter. This is handled transparently by Samba.

Drive Identification

- + MS Windows products support a notion of drive letters, like C:, to represent disk partitions. UNIX has no concept of separate identifiers for file partitions; each such file system is mounted to become part of the overall directory tree. The UNIX directory tree begins at / just as the root of a DOS drive is specified as C:\.

File Naming Conventions

- + MS Windows generally never experiences file names that begin with a dot (.), while in UNIX these are commonly found in a user's home directory. Files that begin with a dot (.) are typically startup files for various UNIX applications, or they may be files that contain startup configuration data.

Links and Short-Cuts

- - - + + + MS Windows make use of links and shortcuts that are actually special types of files that will redirect an attempt to execute the file to the real location of the file. UNIX knows of file and directory links, but they are entirely different from what MS Windows users are used to. @@ -183,17 +183,17 @@ at how Samba helps to bridge the differences. There are many other subtle differences that may cause the MS Windows administrator some temporary discomfort in the process of becoming familiar with UNIX/Linux. These are best left for a text that is dedicated to the purpose of UNIX/Linux training and education. -

Managing Directories

- - - +

Managing Directories

+ + + There are three basic operations for managing directories: create, delete, rename. Managing Directories with UNIX and Windows compares the commands in Windows and UNIX that implement these operations. -

Table 16.1. Managing Directories with UNIX and Windows

ActionMS Windows CommandUNIX Command
createmd foldermkdir folder
deleterd folderrmdir folder
renamerename oldname newnamemv oldname newname

File and Directory Access Control

- - - +

Table 16.1. Managing Directories with UNIX and Windows

ActionMS Windows CommandUNIX Command
createmd foldermkdir folder
deleterd folderrmdir folder
renamerename oldname newnamemv oldname newname

File and Directory Access Control

+ + + The network administrator is strongly advised to read basic UNIX training manuals and reference materials regarding file and directory permissions maintenance. Much can be achieved with the basic UNIX permissions without having to resort to more complex facilities like POSIX ACLs or extended attributes (EAs). @@ -226,47 +226,47 @@ drwsrwsrwx 2 maryo gnomes 48 2003-05-12 22:29 muchado08

Figure 16.1. Overview of UNIX permissions field.

Overview of UNIX permissions field.

Any bit flag may be unset. An unset bit flag is the equivalent of "cannot" and is represented as a “-” character (see “Example File”) - - - - - - + + + + + +

Example 16.1. Example File

 -rwxr-x---   Means: 
  ^^^                The owner (user) can read, write, execute
     ^^^             the group can read and execute
        ^^^          everyone else cannot do anything with it.

- - - - + + + + Additional possibilities in the [type] field are c = character device, b = block device, p = pipe device, s = UNIX Domain Socket.

- - - - - + + + + + The letters rwxXst set permissions for the user, group, and others as read (r), write (w), execute (or access for directories) (x), execute only if the file is a directory or already has execute permission for some user (X), set user (SUID) or group ID (SGID) on execution (s), sticky (t).

- - - - + + + + When the sticky bit is set on a directory, files in that directory may be unlinked (deleted) or renamed only by root or their owner. Without the sticky bit, anyone able to write to the directory can delete or rename files. The sticky bit is commonly found on directories, such as /tmp, that are world-writable.

- - - - - + + + + + When the set user or group ID bit (s) is set on a directory, then all files created within it will be owned by the user and/or group whose `set user or group' bit is set. This can be helpful in setting up directories for which it is desired that all users who are in a group should be able to write to and read from a file, particularly when it is undesirable for that file @@ -276,11 +276,11 @@ drwsrwsrwx 2 maryo gnomes 48 2003-05-12 22:29 muchado08 the (r) read flags are not set, files cannot be listed (seen) in the directory by anyone. The group can read files in the directory but cannot create new files. If files in the directory are set to be readable and writable for the group, then group members will be able to write to (or delete) them. -

Protecting Directories and Files from Deletion

- - - - +

Protecting Directories and Files from Deletion

+ + + + People have asked on the Samba mailing list how is it possible to protect files or directories from deletion by users. For example, Windows NT/2K/XP provides the capacity to set access controls on a directory into which people can write files but not delete them. It is possible to set an ACL on a Windows file that permits the file to be written to @@ -288,27 +288,27 @@ drwsrwsrwx 2 maryo gnomes 48 2003-05-12 22:29 muchado08 anyone who has the ability to create a file can write to it. Anyone who has write permission on the directory that contains a file and has write permission for it has the capability to delete it.

- - - + + + For the record, in the UNIX environment the ability to delete a file is controlled by the permissions on the directory that the file is in. In other words, a user can delete a file in a directory to which that user has write access, even if that user does not own the file.

- - - - + + + + Of necessity, Samba is subject to the file system semantics of the host operating system. Samba is therefore limited in the file system capabilities that can be made available through Windows ACLs, and therefore performs a "best fit" translation to POSIX ACLs. Some UNIX file systems do, however support, a feature known as extended attributes. Only the Windows concept of inheritance is implemented by Samba through the appropriate extended attribute.

- - - - + + + + The specific semantics of the extended attributes are not consistent across UNIX and UNIX-like systems such as Linux. For example, it is possible on some implementations of the extended attributes to set a flag that prevents the directory or file from being deleted. The extended attribute that may achieve this is called the immutible bit. @@ -322,7 +322,7 @@ CAP_LINUX_IMMUTABLE capability can set or clear this attribute.

A simple test can be done to check if the immutible flag is supported on files in the file system of the Samba host server. -

Procedure 16.1. Test for File Immutibility Support

  1. +

    Procedure 16.1. Test for File Immutibility Support

    1. Create a file called filename.

    2. Login as the root user, then set the immutibile flag on a test file as follows: @@ -340,11 +340,11 @@ mystic:/home/hannibal > rm filename that cannot be deleted. Check the man page on your particular host system to determine whether or not immutable directories are writable. If they are not, then the entire directory and its contents will effectively be protected from writing (file creation also) and deletion. -

Share Definition Access Controls

- +

Share Definition Access Controls

+ The following parameters in the smb.conf file sections define a share control or affect access controls. Before using any of the following options, please refer to the man page for smb.conf. -

User- and Group-Based Controls

+

User- and Group-Based Controls

User- and group-based controls can prove quite useful. In some situations it is distinctly desirable to force all file system operations as if a single user were doing so. The use of the force user and force group behavior will achieve this. @@ -385,7 +385,7 @@ mystic:/home/hannibal > rm filename List of users that should be allowed to login to this service.

write list

List of users that are given read-write access to a service. -


File and Directory Permissions-Based Controls

+


File and Directory Permissions-Based Controls

Directory permission-based controls, if misused, can result in considerable difficulty in diagnosing the causes of misconfiguration. Use them sparingly and carefully. By gradually introducing each, one at a time, undesirable side effects may be detected. In the event of a problem, always comment all of them out and then gradually reintroduce @@ -416,7 +416,7 @@ mystic:/home/hannibal > rm filename This parameter controls whether smbd will attempt to map UNIX permissions into Windows NT ACLs.

security mask

Controls UNIX permission bits modified when a Windows NT client is manipulating the UNIX permissions on a file. -


Miscellaneous Controls

+


Miscellaneous Controls

The parameter documented in Other Controls are often used by administrators in ways that create inadvertent barriers to file access. Such are the consequences of not understanding the full implications of smb.conf file settings. @@ -449,70 +449,70 @@ mystic:/home/hannibal > rm filename If this parameter is yes, then users of a service may not create or modify files in the service's directory.

veto files

List of files and directories that are neither visible nor accessible. -


Access Controls on Shares

- - - - - +


Access Controls on Shares

+ + + + + This section deals with how to configure Samba per-share access control restrictions. By default, Samba sets no restrictions on the share itself. Restrictions on the share itself can be set on MS Windows NT4/200x/XP shares. This can be an effective way to limit who can connect to a share. In the absence of specific restrictions, the default setting is to allow the global user Everyone - Full Control (full control, change and read).

- - - + + + At this time Samba does not provide a tool for configuring access control settings on the share itself the only way to create those settings is to use either the NT4 Server Manager or the Windows 200x Microsoft Management Console (MMC) for Computer Management. There are currently no plans to provide this capability in the Samba command-line tool set.

- - - - + + + + Samba stores the per-share access control settings in a file called share_info.tdb. The location of this file on your system will depend on how Samba was compiled. The default location for Samba's tdb files is under /usr/local/samba/var. If the tdbdump utility has been compiled and installed on your system, then you can examine the contents of this file by executing tdbdump share_info.tdb in the directory containing the tdb files. -

Share Permissions Management

+

Share Permissions Management

The best tool for share permissions management is platform-dependent. Choose the best tool for your environment. -

Windows NT4 Workstation/Server

- - - - +

Windows NT4 Workstation/Server

+ + + + The tool you need to manage share permissions on a Samba server from a Windows NT4 Workstation or Server is the NT Server Manager. Server Manager is shipped with Windows NT4 Server products but not with Windows NT4 Workstation. You can obtain the NT Server Manager for MS Windows NT4 Workstation from the Microsoft web site support section. -

Procedure 16.2. Instructions

  1. +

    Procedure 16.2. Instructions

    1. Launch the NT4 Server Manager and click on the Samba server you want to administer. From the menu select Computer, then click on Shared Directories.

    2. Click on the share that you wish to manage and click the Properties tab, then click the Permissions tab. Now you can add or change access control settings as you wish. -

Windows 200x/XP

- - - - +

Windows 200x/XP

+ + + + On MS Windows NT4/200x/XP system, ACLs on the share itself are set using native tools, usually from File Manager. For example, in Windows 200x, right-click on the shared folder, then select Sharing, then click on Permissions. The default Windows NT4/200x permission allows "Everyone" full control on the share.

- - - + + + MS Windows 200x and later versions come with a tool called the Computer Management snap-in for the MMC. This tool is located by clicking on Control Panel -> Administrative Tools -> Computer Management. -

Procedure 16.3. Instructions

  1. +

    Procedure 16.3. Instructions

    1. After launching the MMC with the Computer Management snap-in, click the menu item Action and select Connect to another computer. If you are not logged onto a domain you will be prompted to enter a domain login user identifier and a password. This will authenticate you to the domain. @@ -523,7 +523,7 @@ mystic:/home/hannibal > rm filename System Tools, then on the [+] next to Shared Folders in the left panel.

    2. - + In the right panel, double-click on the share on which you wish to set access control permissions. Then click the tab Share Permissions. It is now possible to add access control entities to the shared folder. Remember to set what type of access (full control, change, read) you @@ -534,8 +534,8 @@ mystic:/home/hannibal > rm filename ACL precedence. Everyone with no access means that MaryK who is part of the group Everyone will have no access even if she is given explicit full control access. -

MS Windows Access Control Lists and UNIX Interoperability

Managing UNIX Permissions Using NT Security Dialogs

- +

MS Windows Access Control Lists and UNIX Interoperability

Managing UNIX Permissions Using NT Security Dialogs

+ Windows NT clients can use their native security settings dialog box to view and modify the underlying UNIX permissions.

@@ -549,7 +549,7 @@ mystic:/home/hannibal > rm filename When trying to figure out file access problems, it is vitally important to find the identity of the Windows user as it is presented by Samba at the point of file access. This can best be determined from the Samba log files. -

Viewing File Security on a Samba Share

+

Viewing File Security on a Samba Share

From an NT4/2000/XP client, right-click on any file or directory in a Samba-mounted drive letter or UNC path. When the menu pops up, click on the Properties entry at the bottom of the menu. This brings up the file Properties dialog box. Click on the @@ -560,7 +560,7 @@ mystic:/home/hannibal > rm filename to add auditing requirements to a file if the user is logged on as the NT administrator. This dialog is nonfunctional with a Samba share at this time, because the only useful button, the Add button, will not currently allow a list of users to be seen. -

Viewing File Ownership

+

Viewing File Ownership

Clicking on the Ownership button brings up a dialog box telling you who owns the given file. The owner name will be displayed like this: 

@@ -574,7 +574,7 @@ mystic:/home/hannibal > rm filename
 		If the parameter nt acl support is set to false,
 		the file owner will be shown as the NT user Everyone.
 		

-
+
 		The Take Ownership button will not allow you to change the ownership of this file to
 		yourself (clicking it will display a dialog box complaining that the user as whom you are currently logged onto
 		the NT client cannot be found). The reason for this is that changing the ownership of a file is a privileged
@@ -582,14 +582,14 @@ mystic:/home/hannibal > rm filename
 		NT to attempt to change the ownership of a file to the current user logged into the NT client, this will
 		not work with Samba at this time.
 		

-
-
-
+
+
+
 		There is an NT chown command that will work with Samba and allow a user with administrator
 		privilege connected to a Samba server as root to change the ownership of files on both a local NTFS file system
 		or remote mounted NTFS or Samba drive. This is available as part of the Seclib NT
 		security library written by Jeremy Allison of the Samba Team and is downloadable from the main Samba FTP site.
-

Viewing File or Directory Permissions

+

Viewing File or Directory Permissions

The third button is the Permissions button. Clicking on it brings up a dialog box that shows both the permissions and the UNIX owner of the file or directory. The owner is displayed like this:

SERVER\ @@ -603,7 +603,7 @@ mystic:/home/hannibal > rm filename shown as NT Full Control.

The permissions field is displayed differently for files and directories. Both are discussed next. -

File Permissions

+

File Permissions

The standard UNIX user/group/world triplet and the corresponding read, write, execute permissions triplets are mapped by Samba into a three-element NT ACL with the “r”, “w”, and “x” bits mapped into the corresponding NT @@ -621,7 +621,7 @@ mystic:/home/hannibal > rm filename Take Ownership ACL attribute (which has no meaning in UNIX) and reports a component with no permissions as having the NT O bit set. This was chosen, of course, to make it look like a zero, meaning zero permissions. More details on the decision behind this action are given below. -

Directory Permissions

+

Directory Permissions

Directories on an NT NTFS file system have two different sets of permissions. The first set is the ACL set on the directory itself, which is usually displayed in the first set of parentheses in the normal RW NT style. This first set of permissions is created by Samba in exactly the same way as normal file permissions are, described @@ -632,7 +632,7 @@ mystic:/home/hannibal > rm filename

Samba synthesizes these inherited permissions for NT by returning as an NT ACL the UNIX permission mode that a new file created by Samba on this share would receive. -

Modifying File or Directory Permissions

+

Modifying File or Directory Permissions

Modifying file and directory permissions is as simple as changing the displayed permissions in the dialog box and clicking on OK. However, there are limitations that a user needs to be aware of, and also interactions with the standard Samba permission masks and mapping of DOS attributes that also need to @@ -665,7 +665,7 @@ mystic:/home/hannibal > rm filename If you wish to remove all permissions from a user/group/world component, you may either highlight the component and click on the Remove button or set the component to only have the special Take Ownership permission (displayed as O) highlighted. -

Interaction with the Standard Samba “create mask” Parameters

There are four parameters that control interaction with the standard Samba create mask parameters: +

Interaction with the Standard Samba “create mask” Parameters

There are four parameters that control interaction with the standard Samba create mask parameters:

@@ -719,7 +719,7 @@ mystic:/home/hannibal > rm filename does not force any particular bits to be set on, then set the following parameters in the smb.conf file in that share-specific section: -

security mask = 0777
force security mode = 0
directory security mask = 0777
force directory security mode = 0

Interaction with the Standard Samba File Attribute Mapping

Note

+

security mask = 0777
force security mode = 0
directory security mask = 0777
force directory security mode = 0

Interaction with the Standard Samba File Attribute Mapping

Note

Samba maps some of the DOS attribute bits (such as “read-only”) into the UNIX permissions of a file. This means there can be a conflict between the permission bits set via the security @@ -740,7 +740,7 @@ mystic:/home/hannibal > rm filename attributes dialog, you should always press Cancel rather than OK to ensure that your changes are not overridden. -

Windows NT/200X ACLs and POSIX ACLs Limitations

+

Windows NT/200X ACLs and POSIX ACLs Limitations

Windows administrators are familiar with simple ACL controls, and they typically consider that UNIX user/group/other (ugo) permissions are inadequate and not sufficiently fine-grained. @@ -768,7 +768,7 @@ mystic:/home/hannibal > rm filename ACLs as implemented in UNIX file systems. Samba provides support for masks that permit normal ugo and ACLs functionality to be overrided. This further complicates the way in which Windows ACLs must be implemented. -

UNIX POSIX ACL Overview

+

UNIX POSIX ACL Overview

In examining POSIX ACLs we must consider the manner in which they operate for both files and directories. File ACLs have the following significance: 

@@ -797,7 +797,7 @@ default:group::r-x    <-- inherited group perms
 default:mask:rwx      <-- inherited default mask
 default:other:---     <-- inherited permissions for everyone (other)

-

Mapping of Windows File ACLs to UNIX POSIX ACLs

+

Mapping of Windows File ACLs to UNIX POSIX ACLs

Microsoft Windows NT4/200X ACLs must of necessity be mapped to POSIX ACLs. The mappings for file permissions are shown in How Windows File ACLs Map to UNIX POSIX File ACLs. @@ -816,7 +816,7 @@ default:other:--- <-- inherited permissions for everyone (other) The UNIX administrator can set any directory permission from within the UNIX environment. The Windows administrator is more restricted in that it is not possible from within Windows Explorer to remove read permission for the file owner. -

Mapping of Windows Directory ACLs to UNIX POSIX ACLs

+

Mapping of Windows Directory ACLs to UNIX POSIX ACLs

Interesting things happen in the mapping of UNIX POSIX directory permissions and UNIX POSIX ACLs to Windows ACEs (Access Control Entries, the discrete components of an ACL) are mapped to Windows directory ACLs. @@ -824,10 +824,10 @@ default:other:--- <-- inherited permissions for everyone (other) Directory permissions function in much the same way as shown for file permissions, but there are some notable exceptions and a few peculiarities that the astute administrator will want to take into account in the setting up of directory permissions. -

Common Errors

+

Common Errors

File, directory, and share access problems are common topics on the mailing list. The following are examples recently taken from the mailing list. -

Users Cannot Write to a Public Share

+

Users Cannot Write to a Public Share

The following complaint has frequently been voiced on the Samba mailing list: “ We are facing some troubles with file/directory permissions. I can log on the domain as admin user (root), @@ -887,11 +887,11 @@ drwxrwsr-x 2 jack engr 48 2003-02-04 09:55 foodbar

  • If the user that must have write permission in the directory is not a member of the group engr set in the smb.conf entry for the share: -

    force group = engr

    -

    • File Operations Done as root with force user Set

    +

    force group = engr

    +

    File Operations Done as root with force user Set

    When you have a user in admin users, Samba will always do file operations for this user as root, even if force user has been set. -

    MS Word with Samba Changes Owner of File

    +

    MS Word with Samba Changes Owner of File

    Question: “When user B saves a word document that is owned by user A, the updated file is now owned by user B. Why is Samba doing this? How do I fix this?”

    @@ -906,7 +906,7 @@ drwxrwsr-x 2 jack engr 48 2003-02-04 09:55 foodbar in which you are changing Word documents: chmod g+s `directory_name'. This ensures that all files will be created with the group that owns the directory. In smb.conf share declaration section set:

    -

    force create mode = 0660
    force directory mode = 0770

    +

    force create mode = 0660
    force directory mode = 0770

    These two settings will ensure that all directories and files that get created in the share will be readable/writable by the owner and group set on the directory itself. diff --git a/docs/htmldocs/Samba3-HOWTO/AdvancedNetworkManagement.html b/docs/htmldocs/Samba3-HOWTO/AdvancedNetworkManagement.html index e4fa58bb27..5d3e81c5d4 100644 --- a/docs/htmldocs/Samba3-HOWTO/AdvancedNetworkManagement.html +++ b/docs/htmldocs/Samba3-HOWTO/AdvancedNetworkManagement.html @@ -1,9 +1,9 @@ -Chapter 25. Advanced Network Management

    Chapter 25. Advanced Network Management
    Prev Part III. Advanced Configuration Next

    Chapter 25. Advanced Network Management

    John H. Terpstra

    Samba Team

    June 15 2005

    Table of Contents

    Features and Benefits
    Remote Server Administration
    Remote Desktop Management
    Remote Management from NoMachine.Com
    Remote Management with ThinLinc
    Network Logon Script Magic
    Adding Printers without User Intervention
    Limiting Logon Connections

    - +Chapter 25. Advanced Network Management

    Chapter 25. Advanced Network Management
    Prev Part III. Advanced Configuration Next

    Chapter 25. Advanced Network Management

    John H. Terpstra

    Samba Team

    June 15 2005

    Table of Contents

    Features and Benefits
    Remote Server Administration
    Remote Desktop Management
    Remote Management from NoMachine.Com
    Remote Management with ThinLinc
    Network Logon Script Magic
    Adding Printers without User Intervention
    Limiting Logon Connections

    + This section documents peripheral issues that are of great importance to network administrators who want to improve network resource access control, to automate the user environment, and to make their lives a little easier. -

    Features and Benefits

    +

    Features and Benefits

    Often the difference between a working network environment and a well-appreciated one can best be measured by the little things that make everything work more harmoniously. A key part of every network environment solution is the ability to remotely @@ -13,48 +13,48 @@ network operations.

    This chapter presents information on each of these areas. They are placed here, and not in other chapters, for ease of reference. -

    Remote Server Administration

    “How do I get User Manager and Server Manager?”

    - - - +

    Remote Server Administration

    “How do I get User Manager and Server Manager?”

    + + + Since I do not need to buy an NT4 server, how do I get the User Manager for Domains and the Server Manager?

    - - + + Microsoft distributes a version of these tools called Nexus.exe for installation on Windows 9x/Me systems. The tools set includes:

    • Server Manager

    • User Manager for Domains

    • Event Viewer

    Download the archived file at the Microsoft Nexus link.

    - - - + + + The Windows NT 4.0 version of the User Manager for Domains and Server Manager are available from Microsoft via ftp. -

    Remote Desktop Management

    - - +

    Remote Desktop Management

    + + There are a number of possible remote desktop management solutions that range from free through costly. Do not let that put you off. Sometimes the most costly solution is the most cost effective. In any case, you will need to draw your own conclusions as to which is the best tool in your network environment. -

    Remote Management from NoMachine.Com

    - +

    Remote Management from NoMachine.Com

    + The following information was posted to the Samba mailing list at Apr 3 23:33:50 GMT 2003. It is presented in slightly edited form (with author details omitted for privacy reasons). The entire answer is reproduced below with some comments removed.

    “ - + I have a wonderful Linux/Samba server running as PDC for a network. Now I would like to add remote desktop capabilities so users outside could login to the system and get their desktop up from home or another country. ”

    “ - - - - + + + + Is there a way to accomplish this? Do I need a Windows Terminal server? Do I need to configure it so it is a member of the domain or a BDC or PDC? Are there any hacks for MS Windows XP to enable remote login even if the computer is in a domain? @@ -62,22 +62,22 @@ is the best tool in your network environment. Answer provided: Check out the new offer of “NX” software from NoMachine.

    - - - + + + It implements an easy-to-use interface to the Remote X protocol as well as incorporating VNC/RFB and rdesktop/RDP into it, but at a speed performance much better than anything you may have ever seen.

    - + Remote X is not new at all, but what they did achieve successfully is a new way of compression and caching technologies that makes the thing fast enough to run even over slow modem/ISDN connections.

    - - - - + + + + I test drove their (public) Red Hat machine in Italy, over a loaded Internet connection, with enabled thumbnail previews in KDE konqueror, which popped up immediately on “mouse-over”. From inside that (remote X) @@ -85,18 +85,18 @@ is the best tool in your network environment. To test the performance, I played Pinball. I am proud to announce that my score was 631,750 points at first try.

    - - - - + + + + NX performs better on my local LAN than any of the other “pure” connection methods I use from time to time: TightVNC, rdesktop or Remote X. It is even faster than a direct crosslink connection between two nodes.

    - - - + + + I even got sound playing from the Remote X app to my local boxes, and had a working “copy'n'paste” from an NX window (running a KDE session in Italy) to my Mozilla mailing agent. These guys are certainly doing @@ -118,7 +118,7 @@ is the best tool in your network environment. full-screen, and after a short time you forget that it is a remote session at all).

    - + Now the best thing for last: All the core compression and caching technologies are released under the GPL and available as source code to anybody who wants to build on it! These technologies are working, @@ -140,37 +140,37 @@ is the best tool in your network environment. you can now use a (very inconvenient) command line at no cost, but you can buy a comfortable (proprietary) NX GUI front end for money.

  • - - - - - + + + + + NoMachine is encouraging and offering help to OSS/Free Software implementations for such a front-end too, even if it means competition to them (they have written to this effect even to the LTSP, KDE, and GNOME developer mailing lists). -

    • Remote Management with ThinLinc

    +

    Remote Management with ThinLinc

    Another alternative for remote access is ThinLinc from Cendio.

    - - - - - - - - + + + + + + + + ThinLinc is a terminal server solution that is available for Linux and Solaris based on standard protocols such as SSH, TightVNC, NFS and PulseAudio.

    - - + + ThinLinc an be used both in the LAN environment to implement a Thin Client strategy for an organization, and as secure remote access solution for people working from remote locations, even over smallband connections. ThinLinc is free to use for a single concurrent user.

    - - - + + + The product can also be used as a frontend to access Windows Terminal Server or Citrix farms, or even Windows XP machines, securing the connection via the ssh protocol. The client is available both for Linux (supporting all Linux distributions as well as numerous thin terminals) and for Windows. A Java-based Web client is also @@ -185,7 +185,7 @@ is the best tool in your network environment. PulseAudio , unfsd, Python and rdesktop. -

    Network Logon Script Magic

    +

    Network Logon Script Magic

    There are several opportunities for creating a custom network startup configuration environment.

    • No Logon Script.

    • Simple universal Logon Script that applies to all users.

    • Use of a conditional Logon Script that applies per-user or per-group attributes.

    • Use of Samba's preexec and postexec functions on access to the NETLOGON share to create a custom logon script and then execute it.

    • User of a tool such as KixStart.

    @@ -195,7 +195,7 @@ See examples directory genl

    The following listings are from the genlogon directory.

    - + This is the genlogon.pl file: 

    @@ -274,15 +274,15 @@ This is the genlogon.pl file:

    Those wishing to use a more elaborate or capable logon processing system should check out these sites: -

    Adding Printers without User Intervention

    - +

    Adding Printers without User Intervention

    + Printers may be added automatically during logon script processing through the use of: 

     C:\> rundll32 printui.dll,PrintUIEntry /?

    See the documentation in the Microsoft Knowledge Base article 189105. -

    Limiting Logon Connections

    +

    Limiting Logon Connections

    Sometimes it is necessary to limit the number of concurrent connections to a Samba shared resource. For example, a site may wish to permit only one network logon per user. diff --git a/docs/htmldocs/Samba3-HOWTO/Appendix.html b/docs/htmldocs/Samba3-HOWTO/Appendix.html index 231bd2fe78..b9cf255460 100644 --- a/docs/htmldocs/Samba3-HOWTO/Appendix.html +++ b/docs/htmldocs/Samba3-HOWTO/Appendix.html @@ -1 +1 @@ -Part VI. Reference Section

    Part VI. Reference Section
    Prev   Next

    Part VI. Reference Section

    Table of Contents

    41. How to Compile Samba
    Access Samba Source Code via Subversion
    Introduction
    Subversion Access to samba.org
    Accessing the Samba Sources via rsync and ftp
    Verifying Samba's PGP Signature
    Building the Binaries
    Compiling Samba with Active Directory Support
    Starting the smbd nmbd and winbindd
    Starting from inetd.conf
    Alternative: Starting smbd as a Daemon
    42. Portability
    HPUX
    SCO UNIX
    DNIX
    Red Hat Linux
    AIX: Sequential Read Ahead
    Solaris
    Locking Improvements
    Winbind on Solaris 9
    43. Samba and Other CIFS Clients
    Macintosh Clients
    OS2 Client
    Configuring OS/2 Warp Connect or OS/2 Warp 4
    Configuring Other Versions of OS/2
    Printer Driver Download for OS/2 Clients
    Windows for Workgroups
    Latest TCP/IP Stack from Microsoft
    Delete .pwl Files After Password Change
    Configuring Windows for Workgroups Password Handling
    Password Case Sensitivity
    Use TCP/IP as Default Protocol
    Speed Improvement
    Windows 95/98
    Speed Improvement
    Windows 2000 Service Pack 2
    Windows NT 3.1
    44. Samba Performance Tuning
    Comparisons
    Socket Options
    Read Size
    Max Xmit
    Log Level
    Read Raw
    Write Raw
    Slow Logins
    Client Tuning
    Samba Performance Problem Due to Changing Linux Kernel
    Corrupt tdb Files
    Samba Performance is Very Slow
    45. LDAP and Transport Layer Security
    Introduction
    Configuring
    Generating the Certificate Authority
    Generating the Server Certificate
    Installing the Certificates
    Testing
    Troubleshooting
    46. Samba Support
    Free Support
    Commercial Support
    47. DNS and DHCP Configuration Guide
    Features and Benefits
    Example Configuration
    Dynamic DNS
    DHCP Server
    Prev   Next
    Chapter 40. Reporting Bugs Home Chapter 41. How to Compile Samba
    +Part VI. Reference Section
    Part VI. Reference Section
    Prev   Next

    Part VI. Reference Section

    Table of Contents

    42. How to Compile Samba
    Access Samba Source Code via Subversion
    Introduction
    Subversion Access to samba.org
    Accessing the Samba Sources via rsync and ftp
    Verifying Samba's PGP Signature
    Building the Binaries
    Compiling Samba with Active Directory Support
    Starting the smbd nmbd and winbindd
    Starting from inetd.conf
    Alternative: Starting smbd as a Daemon
    43. Portability
    HPUX
    SCO UNIX
    DNIX
    Red Hat Linux
    AIX: Sequential Read Ahead
    Solaris
    Locking Improvements
    Winbind on Solaris 9
    44. Samba and Other CIFS Clients
    Macintosh Clients
    OS2 Client
    Configuring OS/2 Warp Connect or OS/2 Warp 4
    Configuring Other Versions of OS/2
    Printer Driver Download for OS/2 Clients
    Windows for Workgroups
    Latest TCP/IP Stack from Microsoft
    Delete .pwl Files After Password Change
    Configuring Windows for Workgroups Password Handling
    Password Case Sensitivity
    Use TCP/IP as Default Protocol
    Speed Improvement
    Windows 95/98
    Speed Improvement
    Windows 2000 Service Pack 2
    Windows NT 3.1
    45. Samba Performance Tuning
    Comparisons
    Socket Options
    Read Size
    Max Xmit
    Log Level
    Read Raw
    Write Raw
    Slow Logins
    Client Tuning
    Samba Performance Problem Due to Changing Linux Kernel
    Corrupt tdb Files
    Samba Performance is Very Slow
    46. LDAP and Transport Layer Security
    Introduction
    Configuring
    Generating the Certificate Authority
    Generating the Server Certificate
    Installing the Certificates
    Testing
    Troubleshooting
    47. Samba Support
    Free Support
    Commercial Support
    48. DNS and DHCP Configuration Guide
    Features and Benefits
    Example Configuration
    Dynamic DNS
    DHCP Server
    Prev   Next
    Chapter 41. Managing TDB Files Home Chapter 42. How to Compile Samba
    diff --git a/docs/htmldocs/Samba3-HOWTO/Backup.html b/docs/htmldocs/Samba3-HOWTO/Backup.html index 2398e9adc5..19930ccc59 100644 --- a/docs/htmldocs/Samba3-HOWTO/Backup.html +++ b/docs/htmldocs/Samba3-HOWTO/Backup.html @@ -1,33 +1,33 @@ -Chapter 31. Backup Techniques
    Chapter 31. Backup Techniques
    Prev Part III. Advanced Configuration Next

    Chapter 31. Backup Techniques

    John H. Terpstra

    Samba Team

    Table of Contents

    Features and Benefits
    Discussion of Backup Solutions
    BackupPC
    Rsync
    Amanda
    BOBS: Browseable Online Backup System

    Features and Benefits

    - - - - +Chapter 31. Backup Techniques

    Chapter 31. Backup Techniques
    Prev Part III. Advanced Configuration Next

    Chapter 31. Backup Techniques

    John H. Terpstra

    Samba Team

    Table of Contents

    Features and Benefits
    Discussion of Backup Solutions
    BackupPC
    Rsync
    Amanda
    BOBS: Browseable Online Backup System

    Features and Benefits

    + + + + The Samba project is over 10 years old. During the early history of Samba, UNIX administrators were its key implementors. UNIX administrators use UNIX system tools to backup UNIX system files. Over the past 4 years, an increasing number of Microsoft network administrators have taken an interest in Samba. This is reflected in the questions about backup in general on the Samba mailing lists. -

    Discussion of Backup Solutions

    - - +

    Discussion of Backup Solutions

    + + During discussions at a Microsoft Windows training course, one of the pro-UNIX delegates stunned the class when he pointed out that Windows NT4 is limiting compared with UNIX. He likened UNIX to a Meccano set that has an unlimited number of tools that are simple, efficient, and, in combination, capable of achieving any desired outcome.

    - - + + One of the Windows networking advocates retorted that if she wanted a Meccano set, she would buy one. She made it clear that a complex single tool that does more than is needed but does it with a clear purpose and intent is preferred by some like her.

    - - - + + + Please note that all information here is provided as is and without recommendation of fitness or suitability. The network administrator is strongly encouraged to perform due diligence research before implementing any backup solution, whether free @@ -38,31 +38,31 @@ is located at

    BackupPC

    - - - +

    BackupPC

    + + + BackupPC version 2.0.0 has been released on SourceForge. New features include support for rsync/rsyncd and internationalization of the CGI interface (including English, French, Spanish, and German).

    - - - - - - - - + + + + + + + + BackupPC is a high-performance Perl-based package for backing up Linux, UNIX, and Windows PCs and laptops to a server's disk. BackupPC is highly configurable and easy to install and maintain. SMB (via smbclient), tar over rsh/ssh, or rsync/rsyncd are used to extract client data.

    - - - + + + Given the ever-decreasing cost of disks and RAID systems, it is now practical and cost effective to backup a large number of machines onto a server's local disk or network storage. This is what BackupPC does. @@ -71,24 +71,24 @@ The following three free software projects might also merit consideration. space), compression, and a comprehensive CGI interface that allows users to browse backups and restore files.

    - + BackupPC is free software distributed under a GNU GPL license. BackupPC runs on Linux/UNIX/freenix servers and has been tested on Linux, UNIX, Windows 9x/Me, Windows 98, Windows 200x, Windows XP, and Mac OSX clients. -

    Rsync

    - - - - - - +

    Rsync

    + + + + + + rsync is a flexible program for efficiently copying files or directory trees.

    rsync has many options to select which files will be copied and how they are to be transferred. It may be used as an alternative to ftp, http, scp, or rcp.

    - - - + + + The rsync remote-update protocol allows rsync to transfer just the differences between two sets of files across the network link, using an efficient checksum-search algorithm described in the @@ -107,10 +107,10 @@ The following three free software projects might also merit consideration.

  • Support for anonymous or authenticated rsync servers (ideal for mirroring). -

    • Amanda

    - - - +

    Amanda

    + + + Amanda, the Advanced Maryland Automatic Network Disk Archiver, is a backup system that allows the administrator of a LAN to set up a single master backup server to back up multiple hosts to a single large capacity tape drive. Amanda uses native dump and/or @@ -119,8 +119,8 @@ The following three free software projects might also merit consideration.

    For more information regarding Amanda, please check the www.amanda.org/ site. -

    BOBS: Browseable Online Backup System

    - +

    BOBS: Browseable Online Backup System

    + Browseable Online Backup System (BOBS) is a complete online backup system. Uses large disks for storing backups and lets users browse the files using a Web browser. Handles some special files like AppleDouble and icon files. diff --git a/docs/htmldocs/Samba3-HOWTO/CUPS-printing.html b/docs/htmldocs/Samba3-HOWTO/CUPS-printing.html index f3cde885bc..3fe5204e2a 100644 --- a/docs/htmldocs/Samba3-HOWTO/CUPS-printing.html +++ b/docs/htmldocs/Samba3-HOWTO/CUPS-printing.html @@ -1,8 +1,8 @@ -Chapter 22. CUPS Printing Support

    Chapter 22. CUPS Printing Support
    Prev Part III. Advanced Configuration Next

    Chapter 22. CUPS Printing Support

    Kurt Pfeifle

    Danka Deutschland GmbH

    Ciprian Vizitiu

    drawings 

    Jelmer R. Vernooij

    drawings 
    The Samba Team

    (27 Jan 2004)

    Table of Contents

    Introduction
    Features and Benefits
    Overview
    Basic CUPS Support Configuration
    Linking smbd with libcups.so
    Simple smb.conf Settings for CUPS
    More Complex CUPS smb.conf Settings
    Advanced Configuration
    Central Spooling vs. “Peer-to-Peer” Printing
    Raw Print Serving: Vendor Drivers on Windows Clients
    Installation of Windows Client Drivers
    Explicitly Enable “raw” Printing for application/octet-stream
    Driver Upload Methods
    Advanced Intelligent Printing with PostScript Driver Download
    GDI on Windows, PostScript on UNIX
    Windows Drivers, GDI, and EMF
    UNIX Printfile Conversion and GUI Basics
    PostScript and Ghostscript
    Ghostscript: The Software RIP for Non-PostScript Printers
    PostScript Printer Description (PPD) Specification
    Using Windows-Formatted Vendor PPDs
    CUPS Also Uses PPDs for Non-PostScript Printers
    The CUPS Filtering Architecture
    MIME Types and CUPS Filters
    MIME Type Conversion Rules
    Filtering Overview
    Prefilters
    pstops
    pstoraster
    imagetops and imagetoraster
    rasterto [printers specific]
    CUPS Backends
    The Role of cupsomatic/foomatic
    The Complete Picture
    mime.convs
    “Raw” Printing
    application/octet-stream Printing
    PostScript Printer Descriptions for Non-PostScript Printers
    cupsomatic/foomatic-rip Versus Native CUPS Printing
    Examples for Filtering Chains
    Sources of CUPS Drivers/PPDs
    Printing with Interface Scripts
    Network Printing (Purely Windows)
    From Windows Clients to an NT Print Server
    Driver Execution on the Client
    Driver Execution on the Server
    Network Printing (Windows Clients and UNIX/Samba Print -Servers)
    From Windows Clients to a CUPS/Samba Print Server
    Samba Receiving Job-Files and Passing Them to CUPS
    Network PostScript RIP
    PPDs for Non-PS Printers on UNIX
    PPDs for Non-PS Printers on Windows
    Windows Terminal Servers (WTS) as CUPS Clients
    Printer Drivers Running in “Kernel Mode” Cause Many -Problems
    Workarounds Impose Heavy Limitations
    CUPS: A “Magical Stone”?
    PostScript Drivers with No Major Problems, Even in Kernel -Mode
    Configuring CUPS for Driver Download
    cupsaddsmb: The Unknown Utility
    Prepare Your smb.conf for cupsaddsmb
    CUPS “PostScript Driver for Windows NT/200x/XP”
    Recognizing Different Driver Files
    Acquiring the Adobe Driver Files
    ESP Print Pro PostScript Driver for Windows NT/200x/XP
    Caveats to Be Considered
    Windows CUPS PostScript Driver Versus Adobe Driver
    Run cupsaddsmb (Quiet Mode)
    Run cupsaddsmb with Verbose Output
    Understanding cupsaddsmb
    How to Recognize If cupsaddsmb Completed Successfully
    cupsaddsmb with a Samba PDC
    cupsaddsmb Flowchart
    Installing the PostScript Driver on a Client
    Avoiding Critical PostScript Driver Settings on the Client
    Installing PostScript Driver Files Manually Using rpcclient
    A Check of the rpcclient man Page
    Understanding the rpcclient man Page
    Producing an Example by Querying a Windows Box
    Requirements for adddriver and setdriver to Succeed
    Manual Driver Installation in 15 Steps
    Troubleshooting Revisited
    The Printing *.tdb Files
    Trivial Database Files
    Binary Format
    Losing *.tdb Files
    Using tdbbackup
    CUPS Print Drivers from Linuxprinting.org
    foomatic-rip and Foomatic Explained
    foomatic-rip and Foomatic PPD Download and Installation
    Page Accounting with CUPS
    Setting Up Quotas
    Correct and Incorrect Accounting
    Adobe and CUPS PostScript Drivers for Windows Clients
    The page_log File Syntax
    Possible Shortcomings
    Future Developments
    Other Accounting Tools
    Additional Material
    Autodeletion or Preservation of CUPS Spool Files
    CUPS Configuration Settings Explained
    Preconditions
    Manual Configuration
    Printing from CUPS to Windows-Attached Printers
    More CUPS Filtering Chains
    Common Errors
    Windows 9x/Me Client Can't Install Driver
    “cupsaddsmb” Keeps Asking for Root Password in Never-ending Loop
    “cupsaddsmb” or “rpcclient addriver” Emit Error
    “cupsaddsmb” Errors
    Client Can't Connect to Samba Printer
    New Account Reconnection from Windows 200x/XP Troubles
    Avoid Being Connected to the Samba Server as the Wrong User
    Upgrading to CUPS Drivers from Adobe Drivers
    Can't Use “cupsaddsmb” on Samba Server, Which Is a PDC
    Deleted Windows 200x Printer Driver Is Still Shown
    Windows 200x/XP Local Security Policies
    Administrator Cannot Install Printers for All Local Users
    Print Change, Notify Functions on NT Clients
    Win XP-SP1
    Print Options for All Users Can't Be Set on Windows 200x/XP
    Most Common Blunders in Driver Settings on Windows Clients
    cupsaddsmb Does Not Work with Newly Installed Printer
    Permissions on /var/spool/samba/ Get Reset After Each Reboot
    Print Queue Called “lp” Mishandles Print Jobs
    Location of Adobe PostScript Driver Files for “cupsaddsmb”
    Overview of the CUPS Printing Processes

    Introduction

    Features and Benefits

    - +Chapter 22. CUPS Printing Support

    Chapter 22. CUPS Printing Support
    Prev Part III. Advanced Configuration Next

    Chapter 22. CUPS Printing Support

    Kurt Pfeifle

    Danka Deutschland GmbH

    Ciprian Vizitiu

    drawings 

    Jelmer R. Vernooij

    drawings 
    The Samba Team

    (27 Jan 2004)

    Table of Contents

    Introduction
    Features and Benefits
    Overview
    Basic CUPS Support Configuration
    Linking smbd with libcups.so
    Simple smb.conf Settings for CUPS
    More Complex CUPS smb.conf Settings
    Advanced Configuration
    Central Spooling vs. “Peer-to-Peer” Printing
    Raw Print Serving: Vendor Drivers on Windows Clients
    Installation of Windows Client Drivers
    Explicitly Enable “raw” Printing for application/octet-stream
    Driver Upload Methods
    Advanced Intelligent Printing with PostScript Driver Download
    GDI on Windows, PostScript on UNIX
    Windows Drivers, GDI, and EMF
    UNIX Printfile Conversion and GUI Basics
    PostScript and Ghostscript
    Ghostscript: The Software RIP for Non-PostScript Printers
    PostScript Printer Description (PPD) Specification
    Using Windows-Formatted Vendor PPDs
    CUPS Also Uses PPDs for Non-PostScript Printers
    The CUPS Filtering Architecture
    MIME Types and CUPS Filters
    MIME Type Conversion Rules
    Filtering Overview
    Prefilters
    pstops
    pstoraster
    imagetops and imagetoraster
    rasterto [printers specific]
    CUPS Backends
    The Role of cupsomatic/foomatic
    The Complete Picture
    mime.convs
    “Raw” Printing
    application/octet-stream Printing
    PostScript Printer Descriptions for Non-PostScript Printers
    cupsomatic/foomatic-rip Versus Native CUPS Printing
    Examples for Filtering Chains
    Sources of CUPS Drivers/PPDs
    Printing with Interface Scripts
    Network Printing (Purely Windows)
    From Windows Clients to an NT Print Server
    Driver Execution on the Client
    Driver Execution on the Server
    Network Printing (Windows Clients and UNIX/Samba Print +Servers)
    From Windows Clients to a CUPS/Samba Print Server
    Samba Receiving Job-Files and Passing Them to CUPS
    Network PostScript RIP
    PPDs for Non-PS Printers on UNIX
    PPDs for Non-PS Printers on Windows
    Windows Terminal Servers (WTS) as CUPS Clients
    Printer Drivers Running in “Kernel Mode” Cause Many +Problems
    Workarounds Impose Heavy Limitations
    CUPS: A “Magical Stone”?
    PostScript Drivers with No Major Problems, Even in Kernel +Mode
    Configuring CUPS for Driver Download
    cupsaddsmb: The Unknown Utility
    Prepare Your smb.conf for cupsaddsmb
    CUPS “PostScript Driver for Windows NT/200x/XP”
    Recognizing Different Driver Files
    Acquiring the Adobe Driver Files
    ESP Print Pro PostScript Driver for Windows NT/200x/XP
    Caveats to Be Considered
    Windows CUPS PostScript Driver Versus Adobe Driver
    Run cupsaddsmb (Quiet Mode)
    Run cupsaddsmb with Verbose Output
    Understanding cupsaddsmb
    How to Recognize If cupsaddsmb Completed Successfully
    cupsaddsmb with a Samba PDC
    cupsaddsmb Flowchart
    Installing the PostScript Driver on a Client
    Avoiding Critical PostScript Driver Settings on the Client
    Installing PostScript Driver Files Manually Using rpcclient
    A Check of the rpcclient man Page
    Understanding the rpcclient man Page
    Producing an Example by Querying a Windows Box
    Requirements for adddriver and setdriver to Succeed
    Manual Driver Installation in 15 Steps
    Troubleshooting Revisited
    The Printing *.tdb Files
    Trivial Database Files
    Binary Format
    Losing *.tdb Files
    Using tdbbackup
    CUPS Print Drivers from Linuxprinting.org
    foomatic-rip and Foomatic Explained
    foomatic-rip and Foomatic PPD Download and Installation
    Page Accounting with CUPS
    Setting Up Quotas
    Correct and Incorrect Accounting
    Adobe and CUPS PostScript Drivers for Windows Clients
    The page_log File Syntax
    Possible Shortcomings
    Future Developments
    Other Accounting Tools
    Additional Material
    Autodeletion or Preservation of CUPS Spool Files
    CUPS Configuration Settings Explained
    Preconditions
    Manual Configuration
    Printing from CUPS to Windows-Attached Printers
    More CUPS Filtering Chains
    Common Errors
    Windows 9x/Me Client Can't Install Driver
    “cupsaddsmb” Keeps Asking for Root Password in Never-ending Loop
    “cupsaddsmb” or “rpcclient addriver” Emit Error
    “cupsaddsmb” Errors
    Client Can't Connect to Samba Printer
    New Account Reconnection from Windows 200x/XP Troubles
    Avoid Being Connected to the Samba Server as the Wrong User
    Upgrading to CUPS Drivers from Adobe Drivers
    Can't Use “cupsaddsmb” on Samba Server, Which Is a PDC
    Deleted Windows 200x Printer Driver Is Still Shown
    Windows 200x/XP Local Security Policies
    Administrator Cannot Install Printers for All Local Users
    Print Change, Notify Functions on NT Clients
    Windows XP SP1
    Print Options for All Users Can't Be Set on Windows 200x/XP
    Most Common Blunders in Driver Settings on Windows Clients
    cupsaddsmb Does Not Work with Newly Installed Printer
    Permissions on /var/spool/samba/ Get Reset After Each Reboot
    Print Queue Called “lp” Mishandles Print Jobs
    Location of Adobe PostScript Driver Files for “cupsaddsmb”
    Overview of the CUPS Printing Processes

    Introduction

    Features and Benefits

    + The Common UNIX Print System (CUPS) has become quite popular. All major Linux distributions now ship it as their default printing system. To many, it is still a mystical tool. Mostly, it just works. People tend to regard @@ -11,21 +11,21 @@ Mode

    Classical Printing, which contains much information that is also relevant to CUPS.

    - + CUPS sports quite a few unique and powerful features. While its basic functions may be grasped quite easily, they are also new. Because it is different from other, more traditional printing systems, it is best not to try to apply any prior knowledge about printing to this new system. Rather, try to understand CUPS from the beginning. This documentation will lead you to a complete understanding of CUPS. Let's start with the most basic things first. -

    Overview

    - - - - - - - - +

    Overview

    + + + + + + + + CUPS is more than just a print spooling system. It is a complete printer management system that complies with the new Internet Printing Protocol (IPP). IPP is an industry and Internet Engineering Task Force (IETF) standard for network printing. Many of its functions can be managed remotely (or locally) via a Web @@ -33,19 +33,19 @@ Mode

    KDEPrint).

    - - + + CUPS allows creation of raw printers (i.e., no print file format translation) as well as smart printers (i.e., CUPS does file format conversion as required for the printer). In many ways, this gives CUPS capabilities similar to the MS Windows print monitoring system. Of course, if you are a CUPS advocate, you would argue that CUPS is better! In any case, let us now explore how to configure CUPS for interfacing with MS Windows print clients via Samba. -

    Basic CUPS Support Configuration

    - - - - - +

    Basic CUPS Support Configuration

    + + + + + Printing with CUPS in the most basic smb.conf setup in Samba-3.0 (as was true for 2.2.x) requires just two parameters: printing = cups and printcap = cups. CUPS does not need a printcap file. However, the cupsd.conf configuration file knows of two related directives that control how such a @@ -55,16 +55,16 @@ Legacy programs often require the existence of a printcap file containing printe print. Make sure CUPS is set to generate and maintain a printcap file. For details, see man cupsd.conf and other CUPS-related documentation, like the wealth of documents regarding the CUPS server itself available from the CUPS web site. -

    Linking smbd with libcups.so

    - +

    Linking smbd with libcups.so

    + Samba has a special relationship to CUPS. Samba can be compiled with CUPS library support. Most recent installations have this support enabled. By default, CUPS linking is compiled into smbd and other Samba binaries. Of course, you can use CUPS even if Samba is not linked against libcups.so but there are some differences in required or supported configuration.

    - - + + When Samba is compiled and linked with libcups, printcap = cups uses the CUPS API to list printers, submit jobs, query queues, and so on. Otherwise it maps to the System V commands with an additional -oraw option for printing. On a Linux @@ -79,7 +79,7 @@ libcups.so.2 => /usr/lib/libcups.so.2 (0x40123000) [....]

    - + The line libcups.so.2 => /usr/lib/libcups.so.2 (0x40123000) shows there is CUPS support compiled into this version of Samba. If this is the case, and printing = cups is set, then any otherwise manually set print command in smb.conf is ignored. @@ -95,14 +95,14 @@ libcups.so.2 => /usr/lib/libcups.so.2 (0x40123000) lprm command, queuepause command and queue resume command). -

    Simple smb.conf Settings for CUPS

    +

    Simple smb.conf Settings for CUPS

    To summarize, the Simplest Printing-Related smb.conf file shows the simplest printing-related setup for smb.conf to enable basic CUPS support: -

    Example 22.1. Simplest Printing-Related smb.conf

    [global]
    load printers = yes
    printing = cups
    printcap name = cups
    [printers]
    comment = All Printers
    path = /var/spool/samba
    browseable = no
    public = yes
    guest ok = yes
    writable = no
    printable = yes
    printer admin = root, @ntadmins

    - - - +

    Example 22.1. Simplest Printing-Related smb.conf

    [global]
    load printers = yes
    printing = cups
    printcap name = cups
    [printers]
    comment = All Printers
    path = /var/spool/samba
    browseable = no
    guest ok = yes
    writable = no
    printable = yes
    printer admin = root, @ntadmins, @smbprintadm

    + + + This is all you need for basic printing setup for CUPS. It will print all graphic, text, PDF, and PostScript files submitted from Windows clients. However, most of your Windows users would not know how to send these kinds of files to print without opening a GUI application. Windows clients tend to have local printer drivers @@ -112,25 +112,25 @@ libcups.so.2 => /usr/lib/libcups.so.2 (0x40123000) hooked between the application's native format and the print data stream. If the backend printer is not a PostScript device, the print data stream is “binary,” sensible only for the target printer. Read on to learn what problem this may cause and how to avoid it. -

    More Complex CUPS smb.conf Settings

    +

    More Complex CUPS smb.conf Settings

    The Overriding Global CUPS Settings for One Printer example is a slightly more complex printing-related setup for smb.conf. It enables general CUPS printing support for all printers, but defines one printer share, which is set up differently. -

    Example 22.2. Overriding Global CUPS Settings for One Printer

    [global]
    printing = cups
    printcap name = cups
    load printers = yes
    [printers]
    comment = All Printers
    path = /var/spool/samba
    public = yes
    guest ok = yes
    writable = no
    printable = yes
    printer admin = root, @ntadmins
    [special_printer]
    comment = A special printer with his own settings
    path = /var/spool/samba-special
    printing = sysv
    printcap = lpstat
    print command = echo "NEW: `date`: printfile %f" >> /tmp/smbprn.log ; echo " `date`: p-%p s-%s f-%f" >> /tmp/smbprn.log ; echo " `date`: j-%j J-%J z-%z c-%c" >> /tmp/smbprn.log ; rm %f
    public = no
    guest ok = no
    writable = no
    printable = yes
    printer admin = kurt
    hosts deny = 0.0.0.0
    hosts allow = turbo_xp, 10.160.50.23, 10.160.51.60

    +

    Example 22.2. Overriding Global CUPS Settings for One Printer

    [global]
    printing = cups
    printcap name = cups
    load printers = yes
    [printers]
    comment = All Printers
    path = /var/spool/samba
    guest ok = yes
    writable = no
    printable = yes
    printer admin = root, @ntadmins, @smbprintadm
    [special_printer]
    comment = A special printer with his own settings
    path = /var/spool/samba-special
    printing = sysv
    printcap = lpstat
    print command = echo "NEW: `date`: printfile %f" >> /tmp/smbprn.log ; echo " `date`: p-%p s-%s f-%f" >> /tmp/smbprn.log ; echo " `date`: j-%j J-%J z-%z c-%c" >> /tmp/smbprn.log ; rm %f
    guest ok = no
    writable = no
    printable = yes
    printer admin = kurt
    hosts deny = 0.0.0.0
    hosts allow = turbo_xp, 10.160.50.23, 10.160.51.60

    This special share is only for testing purposes. It does not write the print job to a file. It just logs the job parameters known to Samba into the /tmp/smbprn.log file and deletes the job-file. Moreover, the printer admin of this share is “kurt” (not the “@ntadmins” group), guest access is not allowed, the share isn't published to the Network Neighborhood (so you need to know it is there), and it allows access from only three hosts. To prevent CUPS from kicking in and taking over the print jobs for that share, we need to set printing = sysv and printcap = lpstat. -

    Advanced Configuration

    +

    Advanced Configuration

    Before we delve into all the configuration options, let us clarify a few points. Network printing needs to be organized and set up correctly. This frequently doesn't happen. Legacy systems or small business LAN environments often lack design and good housekeeping. -

    Central Spooling vs. “Peer-to-Peer” Printing

    - - - +

    Central Spooling vs. “Peer-to-Peer” Printing

    + + + Many small office or home networks, as well as badly organized larger environments, allow each client a direct access to available network printers. This is generally a bad idea. It often blocks one client's access to the printer when another client's job is printing. It might freeze the first client's application while it is @@ -138,9 +138,9 @@ libcups.so.2 => /usr/lib/libcups.so.2 (0x40123000) pages mixed with each other. A better concept is the use of a print server: it routes all jobs through one central system, which responds immediately, takes jobs from multiple concurrent clients, and transfers them to the printer(s) in the correct order. -

    Raw Print Serving: Vendor Drivers on Windows Clients

    - - +

    Raw Print Serving: Vendor Drivers on Windows Clients

    + + Most traditionally configured UNIX print servers acting on behalf of Samba's Windows clients represented a really simple setup. Their only task was to manage the “raw” spooling of all jobs handed to them by @@ -149,8 +149,8 @@ libcups.so.2 => /usr/lib/libcups.so.2 (0x40123000) device. In this case, a native (vendor-supplied) Windows printer driver needs to be installed on each and every client for the target device.

    - - + + It is possible to configure CUPS, Samba, and your Windows clients in the same traditional and simple way. When CUPS printers are configured for raw print-through mode operation, it is the responsibility of the @@ -164,15 +164,15 @@ libcups.so.2 => /usr/lib/libcups.so.2 (0x40123000) This is achieved by installation of the printer as if it were physically attached to the Windows client. You then redirect output to a raw network print queue. This procedure may be followed to achieve this: -

    Procedure 22.1. Configuration Steps for Raw CUPS Printing Support

    1. - +

      Procedure 22.1. Configuration Steps for Raw CUPS Printing Support

      1. + Edit /etc/cups/mime.types to uncomment the line near the end of the file that has: 

         #application/octet-...

      2. - + Do the same for the file /etc/cups/mime.convs.

      3. Add a raw printer using the Web interface. Point your browser at @@ -193,25 +193,27 @@ libcups.so.2 => /usr/lib/libcups.so.2 (0x40123000) you have configured above. Example: \\server\raw_q. Here, the name raw_q is the name you gave the print queue in the CUPS environment. -

    Installation of Windows Client Drivers

    +

    Installation of Windows Client Drivers

    The printer drivers on the Windows clients may be installed in two functionally different ways:

    • Manually install the drivers locally on each client, one by one; this yields the old LanMan style printing and uses a \\sambaserver\printershare type of connection.

    • - + Deposit and prepare the drivers (for later download) on the print server (Samba); this enables the clients to use “Point'n'Print” to get drivers semi-automatically installed the first time they access the printer; with this method NT/200x/XP clients use the SPOOLSS/MS-RPC type printing calls.

    - The second method is recommended for use over the first. + The second method is recommended for use over the first as it reduces the + administrative efforts and prevents that different versions of the drivers + are used accidentally.

    Explicitly Enable “raw” Printing for application/octet-stream

    - - - + + + If you use the first option (drivers are installed on the client side), there is one setting to take care of: CUPS needs to be told that it should allow “raw” printing of deliberate (binary) file @@ -223,10 +225,10 @@ libcups.so.2 => /usr/lib/libcups.so.2 (0x40123000) 

     application/octet-stream

    - - + + In /etc/cups/mime.convs, have this line: - + 

     application/octet-stream   application/vnd.cups-raw   0   -

    @@ -237,8 +239,8 @@ application/octet-stream application/vnd.cups-raw 0 - Editing the mime.convs and the mime.types file does not enforce “raw” printing, it only allows it.

    Background.  - - + + That CUPS is a more security-aware printing system than traditional ones does not by default allow a user to send deliberate (possibly binary) data to printing devices. This could be easily abused to launch a “Denial of Service” attack on your printer(s), causing at least the loss of a lot of paper and @@ -252,11 +254,11 @@ application/octet-stream application/vnd.cups-raw 0 - locally installed. If you are not interested in background information about more advanced CUPS/Samba printing, simply skip the remaining sections of this chapter. -

    Driver Upload Methods

    +

    Driver Upload Methods

    This section describes three familiar methods, plus one new one, by which printer drivers may be uploaded.

    - + If you want to use the MS-RPC-type printing, you must upload the drivers onto the Samba server first ([print$] share). For a discussion on how to deposit printer drivers on the @@ -265,27 +267,27 @@ application/octet-stream application/vnd.cups-raw 0 - chapter of this book. There you will find a description or reference to three methods of preparing the client drivers on the Samba server:

    • - + The GUI, “Add Printer Wizard” upload-from-a-Windows-client method.

    • The command line, “smbclient/rpcclient” upload-from-a-UNIX-workstation method.

    • - + The Imprints tool set method.

    - + These three methods apply to CUPS all the same. The cupsaddsmb utility is a new and more convenient way to load the Windows drivers into Samba and is provided if you use CUPS.

    cupsaddsmb is discussed in much detail later in this chapter. But we first explore the CUPS filtering system and compare the Windows and UNIX printing architectures. -

    Advanced Intelligent Printing with PostScript Driver Download

    - +

    Advanced Intelligent Printing with PostScript Driver Download

    + We now know how to set up a “dump” print server, that is, a server that spools print jobs “raw”, leaving the print data untouched.

    You might need to set up CUPS in a smarter way. The reasons could be manifold: -

    • Maybe your boss wants to get monthly statistics: Which +

      • Maybe your boss wants to get monthly statistics: Which printer did how many pages? What was the average data size of a job? What was the average print run per day? What are the typical hourly peaks in printing? Which department prints how much?

      • Maybe you are asked to set up a print quota system: @@ -301,28 +303,28 @@ application/octet-stream application/vnd.cups-raw 0 - Windows and UNIX printing, then a description of the CUPS filtering system, how it works, and how you can tweak it.

        GDI on Windows, PostScript on UNIX

        - - + + Network printing is one of the most complicated and error-prone day-to-day tasks any user or administrator may encounter. This is true for all OS platforms, and there are reasons it is so.

        - - - - - + + + + + You can't expect to throw just any file format at a printer and have it get printed. A file format conversion must take place. The problem is that there is no common standard for print file formats across all manufacturers and printer types. While PostScript (trademark held by Adobe) and, to an extent, PCL (trademark held by Hewlett-Packard) have developed into semi-official “standards” by being the most widely used page description languages (PDLs), there are still many manufacturers who “roll their own” (their reasons may be unacceptable license fees for using printer-embedded PostScript interpreters, and so on). -

        Windows Drivers, GDI, and EMF

        - - - - +

        Windows Drivers, GDI, and EMF

        + + + + In Windows OS, the format conversion job is done by the printer drivers. On MS Windows OS platforms all application programmers have at their disposal a built-in API, the graphical device interface (GDI), as part and parcel of the OS itself to base themselves on. This GDI core is used as one common unified ground for all @@ -333,21 +335,21 @@ application/octet-stream application/vnd.cups-raw 0 - the GDI, often produces a file format called Enhanced MetaFile (EMF). The EMF is processed by the printer driver and converted to the printer-specific file format.

        Note

        - - - + + + To the GDI foundation in MS Windows, Apple has chosen to put paper and screen output on a common foundation - for its (BSD-UNIX-based, did you know?) Mac OS X and Darwin operating - systems. + for its (BSD-UNIX-based, did you know?) Mac OS X and Darwin operating + systems. Apple's core graphic engine uses a PDF derivative for all display work.

        The example in Windows Printing to a Local Printer illustrates local Windows printing. -

        Figure 22.1. Windows Printing to a Local Printer.

        Windows Printing to a Local Printer.

        UNIX Printfile Conversion and GUI Basics

        - - - - +

        Figure 22.1. Windows Printing to a Local Printer.

        Windows Printing to a Local Printer.

        UNIX Printfile Conversion and GUI Basics

        + + + + In UNIX and Linux, there is no comparable layer built into the OS kernel(s) or the X (screen display) server. Every application is responsible for itself to create its print output. Fortunately, most use PostScript and that at least gives some common ground. Unfortunately, there are many different levels of quality for this @@ -361,16 +363,16 @@ application/octet-stream application/vnd.cups-raw 0 - unfavorable inheritance up to the present day by looking into the various “font” directories on your system; there are separate ones for fonts used for X display and fonts to be used on paper.

        Background.  - - - - - - - - - - + + + + + + + + + + The PostScript programming language is an “invention” by Adobe, but its specifications have been published extensively. Its strength lies in its powerful abilities to describe graphical objects (fonts, shapes, patterns, lines, curves, and dots), their attributes (color, linewidth), and the way to manipulate @@ -382,11 +384,11 @@ application/octet-stream application/vnd.cups-raw 0 - interpreted by a rasterizer. Rasterizers produce pixel images, which may be displayed on screen by a viewer program or on paper by a printer.

        PostScript and Ghostscript

        - - - - - + + + + + So UNIX is lacking a common ground for printing on paper and displaying on screen. Despite this unfavorable legacy for UNIX, basic printing is fairly easy if you have PostScript printers at your disposal. The reason is that these devices have a built-in PostScript language “interpreter,” also called a raster image @@ -395,31 +397,31 @@ application/octet-stream application/vnd.cups-raw 0 - commands into a bitmap picture as you see it on paper, in a resolution as done by your printer. This is no different than PostScript printing a file from a Windows origin.

        Note

        - - - + + + Traditional UNIX programs and printing systems while using PostScript are largely not PPD-aware. PPDs are “PostScript Printer Description” files. They enable you to specify and control all options a printer supports: duplexing, stapling, and punching. Therefore, UNIX users for a long time couldn't choose many of the supported device and job options, unlike Windows or Apple users. But now there is CUPS. as illustrated in Printing to a PostScript Printer.

        Figure 22.2. Printing to a PostScript Printer.

        Printing to a PostScript Printer.

        - + However, there are other types of printers out there. These do not know how to print PostScript. They use their own PDL, often proprietary. To print to them is much more demanding. Since your UNIX applications mostly produce PostScript, and since these devices do not understand PostScript, you need to convert the print files to a format suitable for your printer on the host before you can send it away. -

        Ghostscript: The Software RIP for Non-PostScript Printers

        - +

        Ghostscript: The Software RIP for Non-PostScript Printers

        + Here is where Ghostscript kicks in. Ghostscript is the traditional (and quite powerful) PostScript interpreter used on UNIX platforms. It is a RIP in software, capable of doing a lot of file format conversions for a very broad spectrum of hardware devices as well as software file formats. Ghostscript technology and drivers are what enable PostScript printing to non-PostScript hardware. This is shown in Ghostscript as a RIP for Non-PostScript Printers.

        Figure 22.3. Ghostscript as a RIP for Non-PostScript Printers.

        Ghostscript as a RIP for Non-PostScript Printers.

        Tip

        - - - + + + Use the “gs -h” command to check for all built-in “devices” on your Ghostscript version. If you specify a parameter of -sDEVICE=png256 on your Ghostscript command line, you are asking Ghostscript to convert the input into a PNG file. Naming a “device” on the @@ -427,14 +429,14 @@ application/octet-stream application/vnd.cups-raw 0 - input. New Ghostscript versions are released at fairly regular intervals, now by artofcode LLC. They are initially put under the “AFPL” license, but re-released under the GNU GPL as soon as the next AFPL version appears. GNU Ghostscript is probably the version installed on most Samba systems. But it has some - deficiencies. Therefore, ESP Ghostscript was developed as an enhancement over GNU Ghostscript, + deficiencies. Therefore, ESP Ghostscript was developed as an enhancement over GNU Ghostscript, with lots of bug-fixes, additional devices, and improvements. It is jointly maintained by developers from - CUPS, Gimp-Print, MandrakeSoft, SuSE, Red Hat, and Debian. It includes the “cups” device + CUPS, Gutenprint, MandrakeSoft, SuSE, Red Hat, and Debian. It includes the “cups” device (essential to print to non-PS printers from CUPS). -

        PostScript Printer Description (PPD) Specification

        - - - +

      PostScript Printer Description (PPD) Specification

      + + + While PostScript in essence is a PDL to represent the page layout in a device-independent way, real-world print jobs are always ending up being output on hardware with device-specific features. To take care of all the differences in hardware and to allow for innovations, Adobe has specified a syntax and file format for @@ -456,17 +458,17 @@ application/octet-stream application/vnd.cups-raw 0 - PostScript, PJL, JCL, or vendor-dependent commands) into the PostScript file created by the driver.

      Warning

      - - + + A PostScript file that was created to contain device-specific commands for achieving a certain print job output (e.g., duplexed, stapled, and punched) on a specific target machine may not print as expected, or may not be printable at all on other models; it also may not be fit for further processing by software (e.g., by a PDF distilling program). -

      Using Windows-Formatted Vendor PPDs

      - - - +

    Using Windows-Formatted Vendor PPDs

    + + + CUPS can handle all spec-compliant PPDs as supplied by the manufacturers for their PostScript models. Even if a vendor does not mention our favorite OS in his or her manuals and brochures, you can safely trust this: If you get the Windows NT version of the PPD, you can use it unchanged in CUPS and thus @@ -477,31 +479,31 @@ application/octet-stream application/vnd.cups-raw 0 - parsing and checking code enabled; in case of printing trouble, this online resource should be one of your first pit stops.

    Warning

    - - + + For real PostScript printers, do not use the Foomatic or cupsomatic PPDs from Linuxprinting.org. With these devices, the original vendor-provided PPDs are always the first choice.

    Tip

    - + If you are looking for an original vendor-provided PPD of a specific device, and you know that an NT4 box (or any other Windows box) on your LAN has the PostScript driver installed, just use smbclient //NT4-box/print\$ -U username to access the Windows directory where all printer driver files are stored. First look in the W32X86/2 subdirectory for the PPD you are seeking. -

    CUPS Also Uses PPDs for Non-PostScript Printers

    - - - +

    CUPS Also Uses PPDs for Non-PostScript Printers

    + + + CUPS also uses specially crafted PPDs to handle non-PostScript printers. These PPDs are usually not available from the vendors (and no, you can't just take the PPD of a PostScript printer with the same model name and hope it works for the non-PostScript version too). To understand how these PPDs work for non-PS printers, we first need to dive deeply into the CUPS filtering and file format conversion architecture. Stay tuned. -

    The CUPS Filtering Architecture

    - - - - - +

    The CUPS Filtering Architecture

    + + + + + The core of the CUPS filtering system is based on Ghostscript. In addition to Ghostscript, CUPS uses some other filters of its own. You (or your OS vendor) may have plugged in even more filters. CUPS handles all data file formats under the label of various MIME types. Every incoming print file is subjected to an initial @@ -512,118 +514,118 @@ given input data format.

    If CUPS rasterizes a PostScript file natively to a bitmap, this is done in two stages:

    • - - + + The first stage uses a Ghostscript device named “cups” (this is since version 1.1.15) and produces a generic raster format called “CUPS raster”.

    • - + The second stage uses a “raster driver” that converts the generic CUPS raster to a device-specific raster.

    - - - + + + Make sure your Ghostscript version has the “cups” device compiled in (check with gs -h | grep cups). Otherwise you may encounter the dreaded Unable to convert file 0 in your CUPS error_log file. To have “cups” as a device in your Ghostscript, you either need to patch GNU Ghostscript and recompile or use -ESP Ghostscript. The superior alternative is ESP +ESP Ghostscript. The superior alternative is ESP Ghostscript. It supports not just CUPS, but 300 other devices (while GNU Ghostscript supports only about 180). Because of this broad output device support, ESP Ghostscript is the first choice for non-CUPS spoolers, too. It is now recommended by Linuxprinting.org for all spoolers.

    - - - - + + + + CUPS printers may be set up to use external rendering paths. One of the most common is provided by the Foomatic/cupsomatic concept from Linuxprinting.org. This uses the classical Ghostscript approach, doing everything in one step. It does not use the “cups” device, but one of the many others. However, even for Foomatic/cupsomatic usage, best -results and broadest printer +results and broadest printer model support is provided by ESP Ghostscript (more about Foomatic/cupsomatic, particularly the new version called now foomatic-rip, follows). -

    MIME Types and CUPS Filters

    - - - - - +

    MIME Types and CUPS Filters

    + + + + + CUPS reads the file /etc/cups/mime.types (and all other files carrying a *.types suffix in the same directory) upon startup. These files contain the MIME type recognition rules that are applied when CUPS runs its autotyping routines. The rule syntax is explained in the man page for mime.types and in the comments section of the mime.types file itself. A simple rule reads like this: - + 

     application/pdf         pdf string(0,%PDF)

    - - + + This means if a filename has a .pdf suffix or if the magic string %PDF is right at the beginning of the file itself (offset 0 from the start), then it is a PDF file (application/pdf). Another rule is this: 

     application/postscript  ai eps ps string(0,%!) string(0,<04>%!)

    - - - - - - + + + + + + If the filename has one of the suffixes .ai, .eps, .ps, or if the file itself starts with one of the strings %! or <04>%!, it is a generic PostScript file (application/postscript).

    Warning

    - + Don't confuse the other mime.types files your system might be using with the one in the /etc/cups/ directory.

    Note

    - - - - - + + + + + There is an important difference between two similar MIME types in CUPS: one is application/postscript, the other is application/vnd.cups-postscript. While application/postscript is meant to be device-independent, job options for the file are still outside the PS file content, embedded in - command-line or environment variables by CUPS, application/vnd.cups-postscript may have + command line or environment variables by CUPS, application/vnd.cups-postscript may have the job options inserted into the PostScript data itself (where applicable). The transformation of the generic PostScript (application/postscript) to the device-specific version (application/vnd.cups-postscript) is the responsibility of the CUPS pstops filter. pstops uses information contained in the PPD to do the transformation.

    - - - - - - - - - - - - - - - - + + + + + + + + + + + + + + + + CUPS can handle ASCII text, HP-GL, PDF, PostScript, DVI, and many image formats (GIF, PNG, TIFF, JPEG, Photo-CD, SUN-Raster, PNM, PBM, SGI-RGB, and more) and their associated MIME types with its filters. -

    MIME Type Conversion Rules

    - - - - - +

    MIME Type Conversion Rules

    + + + + + CUPS reads the file /etc/cups/mime.convs (and all other files named with a *.convs suffix in the same directory) upon startup. These files contain @@ -634,44 +636,44 @@ application/postscript ai eps ps string(0,%!) string(0,<04>%!) 

     application/pdf         application/postscript   33   pdftops

    - + This means that the pdftops filter will take application/pdf as input and produce application/postscript as output; the virtual cost of this operation is 33 CUPS-$. The next filter is more expensive, costing 66 CUPS-$: - + 

     application/vnd.hp-HPGL application/postscript   66   hpgltops

    - + This is the hpgltops, which processes HP-GL plotter files to PostScript. - + 

     application/octet-stream

    Here are two more examples: - - - - + + + + 

     application/x-shell     application/postscript   33    texttops
 text/plain              application/postscript   33    texttops

    - + The last two examples name the texttops filter to work on text/plain as well as on application/x-shell. (Hint: This differentiation is needed for the syntax highlighting feature of texttops). -

    Filtering Overview

    - +

    Filtering Overview

    + There are many more combinations named in mime.convs. However, you are not limited to use the ones predefined there. You can plug in any filter you like to the CUPS framework. It must meet, or must be made to meet, some minimal requirements. If you find (or write) a cool conversion filter of some kind, make sure it complies with what CUPS needs and put in the right lines in mime.types and mime.convs; then it will work seamlessly inside CUPS. -

    Filter Requirements

    +

    Filter Requirements

    The “CUPS requirements” for filters are simple. Take filenames or stdin as input and write to stdout. They should take these arguments:

    printer

    @@ -687,27 +689,27 @@ text/plain application/postscript 33 texttops

    options

    The job options.

    filename

    - (optionally) The print request file (if missing, filters expected data + (optionally) The print request file (if missing, filters expect data fed through stdin). In most cases, it is easy to write a simple wrapper script around existing filters to make them work with CUPS. -

    Prefilters

    - - - +

    Prefilters

    + + + As previously stated, PostScript is the central file format to any UNIX-based printing system. From PostScript, CUPS generates raster data to feed non-PostScript printers.

    - - - - - - - - - - + + + + + + + + + + But what happens if you send one of the supported non-PS formats to print? Then CUPS runs “prefilters” on these input formats to generate PostScript first. There are prefilters to create PostScript from ASCII text, PDF, DVI, or HP-GL. The outcome of these filters is always of MIME type @@ -717,14 +719,14 @@ text/plain application/postscript 33 texttops MIME type application/vnd.cups-postscript (not application/postscript), meaning it has the print options already embedded into the file. This is shown in Prefiltering in CUPS to Form PostScript. -

    Figure 22.4. Prefiltering in CUPS to Form PostScript.

    Prefiltering in CUPS to Form PostScript.

    pstops

    - - - - - - - +

    Figure 22.4. Prefiltering in CUPS to Form PostScript.

    Prefiltering in CUPS to Form PostScript.

    pstops

    + + + + + + + pstops is a filter that is used to convert application/postscript to application/vnd.cups-postscript. As stated earlier, this filter inserts all device-specific print options (commands to the printer to ask for the duplexing of output, or stapling and @@ -740,10 +742,10 @@ text/plain application/postscript 33 texttops so-called “number-up” function).

  • Counting the pages of the job to insert the accounting information into the /var/log/cups/page_log. -

    • pstoraster

    - - - +

    pstoraster

    + + + pstoraster is at the core of the CUPS filtering system. It is responsible for the first stage of the rasterization process. Its input is of MIME type application/vnd.cups-postscript; its output is application/vnd.cups-raster. This output format is not yet meant to be printable. Its aim is to serve as a @@ -751,10 +753,10 @@ text/plain application/postscript 33 texttops generate device-specific printer data. This is shown in the PostScript to Intermediate Raster Format diagram.

    Figure 22.6. PostScript to Intermediate Raster Format.

    PostScript to Intermediate Raster Format.

    - - - - + + + + CUPS raster is a generic raster format with powerful features. It is able to include per-page information, color profiles, and more, to be used by the downstream raster drivers. Its MIME type is registered with IANA and its specification is, of course, completely open. It is designed to make it quite easy and inexpensive for @@ -764,10 +766,10 @@ text/plain application/postscript 33 texttops raster drivers). This is illustrated in the CUPS-Raster Production Using Ghostscript illustration.

    Figure 22.7. CUPS-Raster Production Using Ghostscript.

    CUPS-Raster Production Using Ghostscript.

    - - - - + + + + CUPS versions before version 1.1.15 shipped a binary (or source code) standalone filter, named pstoraster. pstoraster, which was derived from GNU Ghostscript 5.50 and could be installed instead of and in addition to any GNU or AFPL Ghostscript package without @@ -778,27 +780,27 @@ text/plain application/postscript 33 texttops now a simple shell script calling gs with the -sDEVICE=cups parameter. If your Ghostscript fails when this command is executed: gs -h |grep cups, you might not be able to print, update your Ghostscript. -

    imagetops and imagetoraster

    - - +

    imagetops and imagetoraster

    + + In the section about prefilters, we mentioned the prefilter that generates PostScript from image formats. The imagetoraster filter is used to convert directly from image to raster, without the intermediate PostScript stage. It is used more often than the previously mentioned prefilters. We summarize in a flowchart the image file filtering in the Image Format to CUPS-Raster Format Conversion illustration. -

    Figure 22.8. Image Format to CUPS-Raster Format Conversion.

    Image Format to CUPS-Raster Format Conversion.

    rasterto [printers specific]

    - - - - - - - - - - - +

    Figure 22.8. Image Format to CUPS-Raster Format Conversion.

    Image Format to CUPS-Raster Format Conversion.

    rasterto [printers specific]

    + + + + + + + + + + + CUPS ships with quite a variety of raster drivers for processing CUPS raster. On my system, I find in /usr/lib/cups/filter/ the following: rastertoalps, rastertobj, rastertoepson, rastertoescp, rastertopcl, @@ -806,12 +808,12 @@ text/plain application/postscript 33 texttops rastertodymo, rastertoescp, rastertohp, and rastertoprinter. Don't worry if you have fewer drivers than this; some of these are installed by commercial add-ons to CUPS (like rastertoturboprint), and others (like - rastertoprinter) by third-party driver development projects (such as Gimp-Print) + rastertoprinter) by third-party driver development projects (such as Gutenprint) wanting to cooperate as closely as possible with CUPS. See the Raster to Printer-Specific Formats illustration. -

    Figure 22.9. Raster to Printer-Specific Formats.

    Raster to Printer-Specific Formats.

    CUPS Backends

    - - +

    Figure 22.9. Raster to Printer-Specific Formats.

    Raster to Printer-Specific Formats.

    CUPS Backends

    + + The last part of any CUPS filtering chain is a backend. Backends are special programs that send the print-ready file to the final device. There is a separate backend program for any transfer @@ -885,8 +887,8 @@ text/plain application/postscript 33 texttops email back to the $USER asking him or her to always specify the correct printer name.)

    - - + + Not all of the mentioned backends may be present on your system or usable (depending on your hardware configuration). One test for all available CUPS backends is provided by the lpinfo @@ -894,12 +896,12 @@ text/plain application/postscript 33 texttops all available backends: 

     	$ lpinfo -v
-

    The Role of cupsomatic/foomatic

    - - - - - +

    The Role of cupsomatic/foomatic

    + + + + + cupsomatic filters may be the most widely used on CUPS installations. You must be clear that these were not developed by the CUPS people. They are a third-party add-on to @@ -919,26 +921,26 @@ text/plain application/postscript 33 texttops file. If you have such a PPD installed, the printer shows up in the CUPS Web interface with a foomatic namepart for the driver description. cupsomatic is a Perl script that runs - Ghostscript with all the complicated command-line options - autoconstructed from the selected PPD and command line options give to + Ghostscript with all the complicated command line options + autoconstructed from the selected PPD and command line options given to the print job.

    - - - - - - - - - - - + + + + + + + + + + + However, cupsomatic is now deprecated. Its PPDs (especially the first generation of them, still in heavy use out there) are not meeting the Adobe specifications. You might also suffer difficulties when you try to download them with “Point'n'Print” to Windows clients. A better - and more powerful successor is now in a stable beta-version: it is called foomatic-rip. To use + and more powerful successor is now available: it is called foomatic-rip. To use foomatic-rip as a filter with CUPS, you need the new type of PPDs, which have a similar but different line: 

    @@ -955,11 +957,11 @@ text/plain              application/postscript   33    texttops
 	best thing is that the new foomatic-rip works seamlessly with all
 	legacy spoolers too (like LPRng, BSD-LPD, PDQ, PPR, and so on), providing
 	for them access to use PPDs for their printing.
-

    The Complete Picture

    +

    The Complete Picture

    If you want to see an overview of all the filters and how they relate to each other, the complete picture of the puzzle is at the end of this chapter. -

    mime.convs

    +

    mime.convs

    CUPS autoconstructs all possible filtering chain paths for any given MIME type and every printer installed. But how does it decide in favor of or against a specific alternative? (There may be cases @@ -969,8 +971,8 @@ text/plain application/postscript 33 texttops assigned to this filter. Every possible filtering chain will sum up to a total “filter cost.” CUPS decides for the most “inexpensive” route.

    Tip

    - - + + Setting FilterLimit 1000 in cupsd.conf will not allow more filters to run concurrently than will consume a total of 1000 virtual filter @@ -978,10 +980,10 @@ text/plain application/postscript 33 texttops server by setting an appropriate “FilterLimit” value. A FilterLimit of 200 allows roughly one job at a time, while a FilterLimit of 1000 allows approximately five jobs maximum at a time. -

    “Raw” Printing

    - - - +

    “Raw” Printing

    + + + You can tell CUPS to print (nearly) any file “raw”. “Raw” means it will not be filtered. CUPS will send the file to the printer “as is” without bothering if the printer is able to digest it. Users need to take care themselves that they send sensible data formats only. Raw printing can @@ -999,9 +1001,9 @@ text/plain application/postscript 33 texttops if it can't find a PPD associated with the queue. However, CUPS will only send known MIME types (as defined in its own mime.types file) and refuse others. -

    application/octet-stream Printing

    - - +

    application/octet-stream Printing

    + + Any MIME type with no rule in the /etc/cups/mime.types file is regarded as unknown or application/octet-stream and will not be sent. Because CUPS refuses to print unknown MIME types by default, @@ -1014,11 +1016,11 @@ text/plain application/postscript 33 texttops To enable the printing of application/octet-stream files, edit these two files:

    • /etc/cups/mime.convs

    • /etc/cups/mime.types

    - + Both contain entries (at the end of the respective files) that must be uncommented to allow raw mode operation for application/octet-stream. In /etc/cups/mime.types make sure this line is present: - + 

     application/octet-stream

    @@ -1029,7 +1031,7 @@ application/octet-stream 

     application/octet-stream   application/vnd.cups-raw   0   -

    - + This line tells CUPS to use the Null Filter (denoted as “-”, doing nothing at all) on application/octet-stream, and tag the result as @@ -1040,10 +1042,10 @@ application/octet-stream application/vnd.cups-raw 0 - Editing the mime.convs and the mime.types file does not enforce “raw” printing, it only allows it.

    Background.  - - - - + + + + That CUPS is a more security-aware printing system than traditional ones does not by default allow one to send deliberate (possibly binary) data to printing devices. (This could be easily abused to launch a @@ -1055,13 +1057,13 @@ application/octet-stream application/vnd.cups-raw 0 - /etc/cups/mime.types defines the “rules” of how CUPS recognizes MIME types. The file /etc/cups/mime.convs decides which file conversion filter(s) may be applied to which MIME types. -

    PostScript Printer Descriptions for Non-PostScript Printers

    - - - - - - +

    PostScript Printer Descriptions for Non-PostScript Printers

    + + + + + + Originally PPDs were meant to be used for PostScript printers only. Here, they help to send device-specific commands and settings to the RIP, which processes the job file. CUPS has extended this @@ -1074,7 +1076,7 @@ application/octet-stream application/vnd.cups-raw 0 -

    PPDs for a non-PostScript printer have a few lines that are unique to CUPS. The most important one looks similar to this: - + 

     *cupsFilter: application/vnd.cups-raster  66   rastertoprinter

    @@ -1084,7 +1086,7 @@ application/octet-stream application/vnd.cups-raw 0 - file. Therefore, CUPS should autoconstruct a filtering chain, which delivers as its last output the specified MIME type. This is then taken as input to the specified rastertoprinter filter. After - the last filter has done its work (rastertoprinter is a Gimp-Print + the last filter has done its work (rastertoprinter is a Gutenprint filter), the file should go to the backend, which sends it to the output device.

    @@ -1092,14 +1094,14 @@ application/octet-stream application/vnd.cups-raw 0 - several hundred printer models. You may not be able to control different paper trays, or you may get larger margins than your specific model supports. See Table 21.1“PPDs Shipped with CUPS” for summary information. -

    Table 22.1. PPDs Shipped with CUPS

    PPD filePrinter type
    deskjet.ppdolder HP inkjet printers and compatible
    deskjet2.ppdnewer HP inkjet printers and compatible
    dymo.ppdlabel printers
    epson9.ppdEpson 24-pin impact printers and compatible
    epson24.ppdEpson 24-pin impact printers and compatible
    okidata9.ppdOkidata 9-pin impact printers and compatible
    okidat24.ppdOkidata 24-pin impact printers and compatible
    stcolor.ppdolder Epson Stylus Color printers
    stcolor2.ppdnewer Epson Stylus Color printers
    stphoto.ppdolder Epson Stylus Photo printers
    stphoto2.ppdnewer Epson Stylus Photo printers
    laserjet.ppdall PCL printers

    cupsomatic/foomatic-rip Versus Native CUPS Printing

    - - +

    Table 22.1. PPDs Shipped with CUPS

    PPD filePrinter type
    deskjet.ppdolder HP inkjet printers and compatible
    deskjet2.ppdnewer HP inkjet printers and compatible
    dymo.ppdlabel printers
    epson9.ppdEpson 24-pin impact printers and compatible
    epson24.ppdEpson 24-pin impact printers and compatible
    okidata9.ppdOkidata 9-pin impact printers and compatible
    okidat24.ppdOkidata 24-pin impact printers and compatible
    stcolor.ppdolder Epson Stylus Color printers
    stcolor2.ppdnewer Epson Stylus Color printers
    stphoto.ppdolder Epson Stylus Photo printers
    stphoto2.ppdnewer Epson Stylus Photo printers
    laserjet.ppdall PCL printers

    cupsomatic/foomatic-rip Versus Native CUPS Printing

    + + Native CUPS rasterization works in two steps:

    • - + First is the pstoraster step. It uses the special CUPS - + device from ESP Ghostscript 7.05.x as its tool.

    • Second is the rasterdriver step. It uses various @@ -1114,7 +1116,7 @@ application/octet-stream application/vnd.cups-raw 0 - One other method is the cupsomatic/foomatic-rip way. Note that cupsomatic is not made by the CUPS developers. It is an independent contribution to printing development, - made by people from Linuxprinting.org.[6] + made by people from Linuxprinting.org.[6] cupsomatic is no longer developed, maintained, or supported. It now been replaced by foomatic-rip. foomatic-rip is a complete rewrite of the old cupsomatic idea, but very much improved and generalized to @@ -1122,8 +1124,8 @@ application/octet-stream application/vnd.cups-raw 0 - advised, especially if you are upgrading to a recent version of CUPS, too.

      - - + + Like the old cupsomatic method, the foomatic-rip (new) method from Linuxprinting.org uses the traditional Ghostscript print file processing, doing everything in a single step. It therefore relies on all the other devices built into Ghostscript. The quality is as good (or bad) as @@ -1133,12 +1135,12 @@ application/octet-stream application/vnd.cups-raw 0 - Of course, you can use both methods side by side on one system (and even for one printer, if you set up different queues) and find out which works best for you.

      - - - - - - + + + + + + cupsomatic kidnaps the print file after the application/vnd.cups-postscript stage and deviates it through the CUPS-external, systemwide Ghostscript installation. Therefore, the print file bypasses the pstoraster @@ -1147,14 +1149,14 @@ application/octet-stream application/vnd.cups-raw 0 - backend. cupsomatic/foomatic Processing Versus Native CUPS, illustrates the difference between native CUPS rendering and the Foomatic/cupsomatic method. -

    Examples for Filtering Chains

    +

    Examples for Filtering Chains

    Here are a few examples of commonly occurring filtering chains to illustrate the workings of CUPS.

    - - - - + + + + Assume you want to print a PDF file to an HP JetDirect-connected PostScript printer, but you want to print pages 3-5, 7, and 11-13 only, and you want to print them “two-up” and “duplex”: @@ -1164,7 +1166,7 @@ application/octet-stream application/vnd.cups-raw 0 - pdftops prefilter, which produces PostScript MIME type application/postscript (a preview here would still show all pages of the original PDF).

  • The file then passes the pstops - filter that applies the command-line options: it selects pages + filter that applies the command line options: it selects pages 2-5, 7, and 11-13, creates the imposed layout “two pages on one sheet”, and inserts the correct “duplex” command (as defined in the printer's PPD) into the new PostScript file; the file is now of PostScript MIME @@ -1173,10 +1175,10 @@ application/octet-stream application/vnd.cups-raw 0 - backend, which transfers the job to the printers.

    • The resulting filter chain, therefore, is as shown in the PDF to socket chain illustration. -

    Figure 22.11. PDF to Socket Chain.

    PDF to Socket Chain.

    - - - +

    Figure 22.11. PDF to Socket Chain.

    PDF to Socket Chain.

    + + + Assume you want to print the same filter to an USB-connected Epson Stylus Photo Printer installed with the CUPS stphoto2.ppd. The first few filtering stages are nearly the same:

    • @@ -1186,16 +1188,16 @@ application/octet-stream application/vnd.cups-raw 0 - The (complete) PDF file is sent to CUPS and autotyped as application/pdf.

    • - - + + The file must first pass the pdftops prefilter, which produces PostScript MIME type application/postscript (a preview here would still show all pages of the original PDF).

    • - - + + The file then passes the “pstops” filter that applies - the command-line options: it selects the pages 2-5, 7, and 11-13, + the command line options: it selects the pages 2-5, 7, and 11-13, creates the imposed layout “two pages on one sheet,” and inserts the correct “duplex” command (oops this printer and PPD do not support duplex printing at all, so this option will @@ -1205,7 +1207,7 @@ application/octet-stream application/vnd.cups-raw 0 - The file then passes the pstoraster stage and becomes MIME type application/cups-raster.

    • - + Finally, the rastertoepson filter does its work (as indicated in the printer's PPD), creating the printer-specific raster data and embedding any user-selected @@ -1215,11 +1217,11 @@ application/octet-stream application/vnd.cups-raw 0 -

    The resulting filter chain therefore is as shown in the PDF to USB Chain illustration. -

    Figure 22.12. PDF to USB Chain.

    PDF to USB Chain.

    Sources of CUPS Drivers/PPDs

    +

    Figure 22.12. PDF to USB Chain.

    PDF to USB Chain.

    Sources of CUPS Drivers/PPDs

    On the Internet you can now find many thousands of CUPS-PPD files (with their companion filters), in many national languages supporting more than 1,000 non-PostScript models. -

    • +

      • ESP PrintPro (commercial, non-free) is packaged with more than 3,000 PPDs, ready for successful use “out of the box” on Linux, Mac OS X, IBM-AIX, @@ -1228,9 +1230,9 @@ application/octet-stream application/vnd.cups-raw 0 - themselves and its sales help finance the further development of CUPS, as they feed their creators).

      • - The Gimp-Print Project + The Gutenprint Project (GPL, free software) provides around 140 PPDs (supporting nearly 400 printers, many driven - to photo quality output), to be used alongside the Gimp-Print CUPS filters. + to photo quality output), to be used alongside the Gutenprint CUPS filters.

      • TurboPrint (shareware, non-free) supports roughly the same number of printers in excellent quality. @@ -1246,10 +1248,10 @@ application/octet-stream application/vnd.cups-raw 0 -

      • Foomatic/cupsomatic (LPGL, free) from Linuxprinting.org provide PPDs for practically every Ghostscript - filter known to the world (including Omni, Gimp-Print, and HPIJS). -

    Printing with Interface Scripts

    - - + filter known to the world (including Omni, Gutenprint, and HPIJS). +

    Printing with Interface Scripts

    + + CUPS also supports the use of “interface scripts” as known from System V AT&T printing systems. These are often used for PCL printers, from applications that generate PCL print jobs. Interface @@ -1271,16 +1273,16 @@ application/octet-stream application/vnd.cups-raw 0 - use of interface scripts is found at http://playground.sun.com/printing/documentation/interface.html). -

    Network Printing (Purely Windows)

    +

    Network Printing (Purely Windows)

    Network printing covers a lot of ground. To understand what exactly goes on with Samba when it is printing on behalf of its Windows clients, let's first look at a “purely Windows” setup: Windows clients with a Windows NT print server. -

    From Windows Clients to an NT Print Server

    +

    From Windows Clients to an NT Print Server

    Windows clients printing to an NT-based print server have two options. They may: - - + +

    Driver Execution on the Client

    +

    Driver Execution on the Client

    In the first case, the print server must spool the file as raw, meaning it shouldn't touch the job file and try to convert it in any way. This is what a traditional UNIX-based print server can do too, and at a better performance and more reliably than an NT print server. This is what most Samba administrators probably are @@ -1297,12 +1299,12 @@ familiar with. One advantage of this setup is that this “the Print Driver Execution on the Client diagram. -

    Figure 22.13. Print Driver Execution on the Client.

    Print Driver Execution on the Client.

    Driver Execution on the Server

    - - - - - +

    Figure 22.13. Print Driver Execution on the Client.

    Print Driver Execution on the Client.

    Driver Execution on the Server

    + + + + + The other path executes the printer driver on the server. The client transfers print files in EMF format to the server. The server uses the PostScript, PCL, ESC/P, or other driver to convert the EMF file into the printer-specific language. It is not possible for UNIX to do the same. Currently, there is no program or @@ -1310,14 +1312,14 @@ method to convert a Windows client's GDI output on a UNIX server into something This is illustrated in the Print Driver Execution on the Server diagram.

    Figure 22.14. Print Driver Execution on the Server.

    Print Driver Execution on the Server.

    However, something similar is possible with CUPS, so read on. -

    Network Printing (Windows Clients and UNIX/Samba Print +

    Network Printing (Windows Clients and UNIX/Samba Print Servers)

    Since UNIX print servers cannot execute the Win32 program code on their platform, the picture is somewhat different. However, this does not limit your options all that much. On the contrary, you may have a way here to implement printing features that are not possible otherwise. -

    From Windows Clients to a CUPS/Samba Print Server

    +

    From Windows Clients to a CUPS/Samba Print Server

    Here is a simple recipe showing how you can take advantage of CUPS's powerful features for the benefit of your Windows network printing clients: @@ -1329,7 +1331,7 @@ driver on the CUPS server.

    First, to enable CUPS-based printing through Samba, the following options should be set in your smb.conf file [global] section: -

    printing = cups
    printcap = cups

    +

    printing = cups
    printcap = cups

    When these parameters are specified, all manually set print directives (like print command or lppause command) in smb.conf (as well as in Samba itself) will be ignored. Instead, Samba will directly interface with CUPS through its application program interface (API), as long as Samba has been compiled with CUPS library (libcups) support. If Samba has not been compiled with CUPS @@ -1337,7 +1339,7 @@ support, and if no other print commands are set up, then printing will use the < AT&T command set, with the -oraw option automatically passing through (if you want your own defined print commands to work with a Samba server that has CUPS support compiled in, simply use classicalprinting = sysv). This is illustrated in the Printing via CUPS/Samba Server diagram. -

    Figure 22.15. Printing via CUPS/Samba Server.

    Printing via CUPS/Samba Server.

    Samba Receiving Job-Files and Passing Them to CUPS

    +

    Figure 22.15. Printing via CUPS/Samba Server.

    Printing via CUPS/Samba Server.

    Samba Receiving Job-Files and Passing Them to CUPS

    Samba must use its own spool directory (it is set by a line similar to path = /var/spool/samba, in the [printers] or [printername] section of smb.conf). Samba receives the job in its own spool space and passes it into the spool directory of CUPS (the CUPS spool directory is set by the RequestRoot directive in a line that defaults to RequestRoot /var/spool/cups). CUPS checks the @@ -1349,13 +1351,13 @@ A Windows user authenticates only to Samba (by whatever means is configured). If Samba runs on the same host as CUPS, you only need to allow “localhost” to print. If it runs on different machines, you need to make sure the Samba host gets access to printing on CUPS. -

    Network PostScript RIP

    +

    Network PostScript RIP

    This section discusses the use of CUPS filters on the server configuration where clients make use of a PostScript driver with CUPS-PPDs.

    - - - + + + PPDs can control all print device options. They are usually provided by the manufacturer if you own a PostScript printer, that is. PPD files are always a component of PostScript printer drivers on MS Windows or Apple Mac OS systems. They are ASCII files containing user-selectable print options, mapped to appropriate @@ -1364,12 +1366,12 @@ PostScript, PCL, or PJL commands for the target printer. Printer driver GUI dial

    CUPS can load, without any conversions, the PPD file from any Windows (NT is recommended) PostScript driver and handle the options. There is a Web browser interface to the print options (select http://localhost:631/printers/ and click on one -Configure Printer button to see it) or a command-line interface (see man +Configure Printer button to see it) or a command line interface (see man lpoptions or see if you have lphelp on your system). There are also some different GUI front-ends on Linux/UNIX, which can present PPD options to users. PPD options are normally meant to be evaluated by the PostScript RIP on the real PostScript printer. -

    PPDs for Non-PS Printers on UNIX

    - +

    PPDs for Non-PS Printers on UNIX

    + CUPS does not limit itself to “real” PostScript printers in its use of PPDs. The CUPS developers have extended the scope of the PPD concept to also describe available device and driver options for non-PostScript printers through CUPS-PPDs. @@ -1381,8 +1383,8 @@ All CUPS-PPDs geared to non-PostScript printers contain an additional line, star for the interpretation of the supplied PostScript. Thus CUPS lets all its printers appear as PostScript devices to its clients, because it can act as a PostScript RIP for those printers, processing the received PostScript code into a proper raster print format. -

    PPDs for Non-PS Printers on Windows

    - +

    PPDs for Non-PS Printers on Windows

    + CUPS-PPDs can also be used on Windows clients, on top of a “core” PostScript driver (now recommended is the CUPS PostScript Driver for Windows NT/200x/XP; you can also use the Adobe one, with limitations). This feature enables CUPS to do a few tricks no other spooler can do: @@ -1396,11 +1398,11 @@ limitations). This feature enables CUPS to do a few tricks no other spooler can Enable clients to consolidate on a single PostScript driver, even for many different target printers.

    Using CUPS PPDs on Windows clients enables them to control all print job settings just as a UNIX client can do. -

    Windows Terminal Servers (WTS) as CUPS Clients

    +

    Windows Terminal Servers (WTS) as CUPS Clients

    This setup may be of special interest to people experiencing major problems in WTS environments. WTS often need a multitude of non-PostScript drivers installed to run their clients' variety of different printer models. This often imposes the price of much increased instability. -

    Printer Drivers Running in “Kernel Mode” Cause Many +

    Printer Drivers Running in “Kernel Mode” Cause Many Problems

    Windows NT printer drivers, which run in “kernel mode”, introduce a high risk for the stability of the system if the driver is not really stable and well-tested. And there are a lot of bad drivers out @@ -1412,14 +1414,14 @@ PostScript drivers are generally well-tested. They are not known to cause any pr run in kernel mode. This might be because until now there have been only two different PostScript drivers: the one from Adobe and the one from Microsoft. Both are well-tested and are as stable as you can imagine on Windows. The CUPS driver is derived from the Microsoft one. -

    Workarounds Impose Heavy Limitations

    +

    Workarounds Impose Heavy Limitations

    In an attempt to work around problems, site administrators have resorted to restricting the allowed drivers installed on their WTS to one generic PCL and one PostScript driver. This, however, restricts the number of printer options available for clients to use. Often they can't get out more than simplex prints from one standard paper tray, while their devices could do much better if driven by a different driver! -

    CUPS: A “Magical Stone”?

    - - +

    CUPS: A “Magical Stone”?

    + + Using a PostScript driver, enabled with a CUPS-PPD, seems to be a very elegant way to overcome all these shortcomings. There are, depending on the version of Windows OS you use, up to three different PostScript drivers now available: Adobe, Microsoft, and CUPS PostScript drivers. None of them is known to cause major @@ -1428,14 +1430,14 @@ paper trays, duplex printing, and other settings. However, there is a certain pr server acting as a PostScript RIP for its clients requires more CPU and RAM than when just acting as a “raw spooling” device. Plus, this setup is not yet widely tested, although the first feedbacks look very promising. -

    PostScript Drivers with No Major Problems, Even in Kernel +

    PostScript Drivers with No Major Problems, Even in Kernel Mode

    - - - - - - + + + + + + More recent printer drivers on W200x and XP no longer run in kernel mode (unlike Windows NT). However, both operating systems can still use the NT drivers, running in kernel mode (you can roughly tell which is which as the drivers in subdirectory “2” of “W32X86” are “old” ones). As was @@ -1447,13 +1449,13 @@ it for their own driver development efforts. This is what the CUPS people have d allow them to publish the whole of the source code. However, they have released the “diff” under the GPL, and if you are the owner of an “MS DDK for Windows NT,” you can check the driver yourself. -

    Configuring CUPS for Driver Download

    +

    Configuring CUPS for Driver Download

    As we have said before, all previously known methods to prepare client printer drivers on the Samba server for download and Point'n'Print convenience of Windows workstations are working with CUPS, too. These methods were described in Classical Printing. In reality, this is a pure Samba business and relates only to the Samba-Windows client relationship. -

    cupsaddsmb: The Unknown Utility

    - +

    cupsaddsmb: The Unknown Utility

    + The cupsaddsmb utility (shipped with all current CUPS versions) is an alternative method to transfer printer drivers into the Samba [print$] share. Remember, this share is where clients expect drivers deposited and set up for download and installation. It makes the sharing @@ -1470,11 +1472,11 @@ number of advantages: However, currently only Windows NT, 2000, and XP are supported by the CUPS drivers. You will also need to get the respective part of the Adobe driver if you need to support Windows 95, 98, and Me clients. -

    Prepare Your smb.conf for cupsaddsmb

    +

    Prepare Your smb.conf for cupsaddsmb

    Prior to running cupsaddsmb, you need the settings in smb.conf as shown in the smb.conf for cupsaddsmb Usage. -

    Example 22.3. smb.conf for cupsaddsmb Usage

    [global]
    load printers = yes
    printing = cups
    printcap name = cups
    [printers]
    comment = All Printers
    path = /var/spool/samba
    browseable = no
    public = yes
    # setting depends on your requirements
    guest ok = yes
    writable = no
    printable = yes
    printer admin = root
    [print$]
    comment = Printer Drivers
    path = /etc/samba/drivers
    browseable = yes
    guest ok = no
    read only = yes
    write list = root

    CUPS “PostScript Driver for Windows NT/200x/XP”

    - +

    Example 22.3. smb.conf for cupsaddsmb Usage

    [global]
    load printers = yes
    printing = cups
    printcap name = cups
    [printers]
    comment = All Printers
    path = /var/spool/samba
    browseable = no
    # setting depends on your requirements
    guest ok = yes
    writable = no
    printable = yes
    printer admin = root
    [print$]
    comment = Printer Drivers
    path = /etc/samba/drivers
    browseable = yes
    guest ok = no
    read only = yes
    write list = root, @smbprintadm

    CUPS “PostScript Driver for Windows NT/200x/XP”

    + CUPS users may get the exact same package from http://www.cups.org/software.html. It is a separate package from the CUPS-based software files, tagged as CUPS 1.1.x Windows NT/200x/XP Printer Driver for Samba (tar.gz, 192k). The filename to download is cups-samba-1.1.x.tar.gz. Upon untar and unzipping, it @@ -1487,8 +1489,8 @@ cups-samba.readme cups-samba.remove cups-samba.ss

    - - + + These have been packaged with the ESP meta-packager software EPM. The *.install and *.remove files are simple shell scripts, which untar the *.ss (the *.ss is nothing else but a tar archive, which can be untarred by “tar” too). @@ -1520,32 +1522,32 @@ into/usr/share/drivers/ instead of ./cups-samba.install script) manually to the correct place.

    - + This new CUPS PostScript driver is currently binary only, but free of charge. No complete source code is provided (yet). The reason is that it has been developed with the help of the Microsoft DDK and compiled with Microsoft Visual Studio 6. Driver developers are not allowed to distribute the whole of the source code as free software. However, CUPS developers released the “diff” in source code under the GPL, so anybody with a license for Visual Studio and a DDK will be able to compile for himself or herself. -

    Recognizing Different Driver Files

    +

    Recognizing Different Driver Files

    The CUPS drivers do not support the older Windows 95/98/Me, but only the Windows NT/2000/XP client.

    Windows NT, 2000, and XP are supported by:

    • cups.hlp

    • cupsdrvr.dll

    • cupsui.dll

    Adobe drivers are available for the older Windows 95/98/Me as well as for Windows NT/2000/XP clients. The set of files is different from the different platforms.

    Windows 95, 98, and ME are supported by:

    • ADFONTS.MFM

    • ADOBEPS4.DRV

    • ADOBEPS4.HLP

    • DEFPRTR2.PPD

    • ICONLIB.DLL

    • PSMON.DLL

    Windows NT, 2000, and XP are supported by:

    • ADOBEPS5.DLL

    • ADOBEPSU.DLL

    • ADOBEPSU.HLP

    Note

    - + If both the Adobe driver files and the CUPS driver files for the support of Windows NT/200x/XP are presently installed on the server, the Adobe files will be ignored and the CUPS files will be used. If you prefer for whatever reason to use Adobe-only drivers, move away the three CUPS driver files. The Windows 9x/Me clients use the Adobe drivers in any case. -

    Acquiring the Adobe Driver Files

    +

    Acquiring the Adobe Driver Files

    Acquiring the Adobe driver files seems to be unexpectedly difficult for many users. They are not available on the Adobe Web site as single files, and the self-extracting and/or self-installing Windows-.exe is not easy to locate either. You probably need to use the included native installer and run the installation process on one client once. This will install the drivers (and one generic PostScript printer) locally on the client. When they are installed, share the generic PostScript printer. After this, the client's [print$] share holds the Adobe files, which you can get with smbclient from the CUPS host. -

    ESP Print Pro PostScript Driver for Windows NT/200x/XP

    - +

    ESP Print Pro PostScript Driver for Windows NT/200x/XP

    + Users of the ESP Print Pro software are able to install the ESP print drivers package as an alternative to the Adobe PostScript drivers. To do so, retrieve the driver files from the normal download area of the ESP Print Pro software at Easy Software web site. @@ -1555,19 +1557,19 @@ highlighting the printer in the Printer Manager GUI and selecting [print$] share, and so on. The ESP Print Pro package includes the CUPS driver files as well as a (licensed) set of Adobe drivers for the Windows 95/98/Me client family. -

    Caveats to Be Considered

    - - - - +

    Caveats to Be Considered

    + + + + Once you have run the install script (and possibly manually moved the cups.hlp file to /usr/share/cups/drivers/), the driver is ready to be put into Samba's [print$] share (which often maps to /etc/samba/drivers/ and contains a subdirectory tree with WIN40 and W32X86 branches). You do this by running cupsaddsmb (see also man cupsaddsmb for CUPS since release 1.1.16).

    Tip

    - - + + You may need to put root into the smbpasswd file by running smbpasswd; this is especially important if you should run this whole procedure for the first time and are not working in an environment where everything is configured for single sign-on to a Windows Domain Controller. @@ -1582,8 +1584,8 @@ It is not harmful if you still have the ADOBE*.* d in the /usr/share/cups/drivers/ directory. The new cupsaddsmb (from 1.1.16) will automatically prefer its own drivers if it finds both.

    Note

    - - + + Should your Windows clients have had the old ADOBE*.* files for the Adobe PostScript driver installed, the download and installation of the new CUPS PostScript driver for Windows NT/200x/XP will fail at first. You need to wipe the old driver from the clients first. It is not enough to @@ -1597,43 +1599,43 @@ there is not one single printer left that uses that particular driver. You need printers using this driver in the Printers folder first. You will need Administrator privileges to do this.

    Note

    - - + + Once you have successfully downloaded the CUPS PostScript driver to a client, you can easily switch all printers to this one by proceeding as described in Classical Printing Support. Either change a driver for an existing printer by running the Printer Properties dialog, or use rpcclient with the setdriver subcommand. -

    Windows CUPS PostScript Driver Versus Adobe Driver

    +

    Windows CUPS PostScript Driver Versus Adobe Driver

    Are you interested in a comparison between the CUPS and the Adobe PostScript drivers? For our purposes, these are the most important items that weigh in favor of CUPS:

    • No hassle with the Adobe EULA.

    • No hassle with the question, “Where do I get the ADOBE*.* driver files?”

    • - + The Adobe drivers (on request of the printer PPD associated with them) often put a PJL header in front of the main PostScript part of the print file. Thus, the print file starts with <1B >%-12345X or <escape>%-12345X instead of %!PS. This leads to the CUPS daemon autotyping the incoming file as a print-ready file, not initiating a pass through the pstops filter (to speak more technically, it is not - regarded as the generic MIME-type + regarded as the generic MIME-type application/postscript, but as the more special MIME type - + application/cups.vnd-postscript), which therefore also leads to the page accounting in /var/log/cups/page_log not receiving the exact number of pages; instead the dummy page number of “1” is logged in a standard setup).

    • The Adobe driver has more options to misconfigure the - + PostScript generated by it (like setting it inadvertently to Optimize for Speed instead of Optimize for Portability, which could lead to CUPS being unable to process it).

    • The CUPS PostScript driver output sent by Windows - + clients to the CUPS server is guaranteed to autotype as the generic MIME type application/postscript, thus passing through the CUPS pstops filter and logging the correct number of pages in the page_log for accounting and quota purposes.

    • - + The CUPS PostScript driver supports the sending of additional standard (IPP) print options by Windows NT/200x/XP clients. Such additional print options are naming the CUPS standard banner pages (or the custom ones, should they be installed at the time of driver download), using the CUPS @@ -1646,9 +1648,9 @@ are the most important items that weigh in favor of CUPS: not disturb any other applications because they will regard it as a comment and simply ignore it).

    • The CUPS PostScript driver will be the heart of the fully fledged CUPS IPP client for Windows NT/200x/XP to be released soon - (probably alongside the first beta release for CUPS 1.2).

    Run cupsaddsmb (Quiet Mode)

    - - + (probably alongside the first beta release for CUPS 1.2).

    Run cupsaddsmb (Quiet Mode)

    + + The cupsaddsmb command copies the needed files into your [print$] share. Additionally, the PPD associated with this printer is copied from /etc/cups/ppd/ to [print$]. There the files wait for convenient Windows client installations via @@ -1656,26 +1658,26 @@ Point'n'Print. Before we can run the command successfully, we need to be sure th Samba. If you have a small network, you are probably using user-level security (security = user).

    Here is an example of a successfully run cupsaddsmb command: - - + + 

     root# cupsaddsmb -U root infotec_IS2027
 Password for root required to access localhost via Samba: ['secret']

    - + To share all printers and drivers, use the -a parameter instead of a printer name. Since cupsaddsmb “exports” the printer drivers to Samba, it should be obvious that it only works for queues with a CUPS driver associated. -

    Run cupsaddsmb with Verbose Output

    - +

    Run cupsaddsmb with Verbose Output

    + Probably you want to see what's going on. Use the -v parameter to get a more verbose output. The output below was edited for better readability: all “\” at the end of a line indicate that I inserted an artificial line break plus some indentation here: - - + + 

     root# cupsaddsmb -U root -v infotec_2105
 Password for root required to access localhost via GANDALF:
@@ -1744,17 +1746,17 @@ If you look closely, you'll discover your root password was transferred unencryp
 Also, if you look further, you may discover error messages like NT_STATUS_OBJECT_NAME_COLLISION in the output.
 This will occur when the directories WIN40 and W32X86 already existed in the [print$]
 driver download share (from a previous driver installation). These are harmless warning messages.
-

    Understanding cupsaddsmb

    - +

    Understanding cupsaddsmb

    + What has happened? What did cupsaddsmb do? There are five stages of the procedure:

    1. - + Call the CUPS server via IPP and request the driver files and the PPD file for the named printer.

    2. Store the files temporarily in the local TEMPDIR (as defined in cupsd.conf).

    3. Connect via smbclient to the Samba server's [print$] share and put the files into the share's WIN40 (for Windows 9x/Me) and W32X86 (for Windows NT/200x/XP) subdirectories.

    4. - + Connect via rpcclient to the Samba server and execute the adddriver command with the correct parameters.

    5. - + Connect via rpcclient to the Samba server a second time and execute the setdriver command.

    Note

    You can run the cupsaddsmb utility with parameters to specify one remote host as Samba host and a second remote host as CUPS host. Especially if you want to get a deeper understanding, it is a good idea @@ -1763,7 +1765,7 @@ Samba servers run on the same host): 

     root# cupsaddsmb -H sambaserver -h cupsserver -v printer

    -

    How to Recognize If cupsaddsmb Completed Successfully

    +

    How to Recognize If cupsaddsmb Completed Successfully

    You must always check if the utility completed successfully in all fields. You need at minimum these three messages among the output: @@ -1792,9 +1794,9 @@ the use client driver. It is impossible to see any diagnostic output if you do not run cupsaddsmb in verbose mode. Therefore, we strongly recommend against use of the default quiet mode. It will hide any problems from you that might occur. -

    cupsaddsmb with a Samba PDC

    - - +

    cupsaddsmb with a Samba PDC

    + + Can't get the standard cupsaddsmb command to run on a Samba PDC? Are you asked for the password credential again and again, and the command just will not take off at all? Try one of these variations: @@ -1804,32 +1806,33 @@ variations: root# cupsaddsmb -H SAURON -U MIDEARTH\\root -h cups-server -v printername

    (Note the two backslashes: the first one is required to “escape” the second one). -

    cupsaddsmb Flowchart

    - - +

    cupsaddsmb Flowchart

    + + The cupsaddsmb Flowchart shows a chart about the procedures, command flows, and data flows of the cupaddsmb command. Note again: cupsaddsmb is not intended to, and does not work with, raw print queues! -

    Figure 22.16. cupsaddsmb Flowchart.

    cupsaddsmb Flowchart.

    Installing the PostScript Driver on a Client

    - - +

    Figure 22.16. cupsaddsmb Flowchart.

    cupsaddsmb Flowchart.

    Installing the PostScript Driver on a Client

    + + After cupsaddsmb is completed, your driver is prepared for the clients to use. Here are the steps you must perform to download and install it via Point'n'Print. From a Windows client, browse to the CUPS/Samba server:

    • - + Open the Printers share of Samba in Network Neighborhood.

    • Right-click on the printer in question.

    • From the opening context menu select Install... or Connect... (depending on the Windows version you use).

    After a few seconds, there should be a new printer in your client's local Printers folder. On Windows XP it will follow a naming convention of PrinterName on SambaServer. (In my current case it is infotec_2105 on kde-bitshop). If -you want to test it and send your first job from an application like Winword, the new printer appears in a +you want to test it and send your first job from an application like Microsoft Word, +the new printer appears in a \\SambaServer\PrinterName entry in the drop-down list of available printers.

    - - - + + + cupsaddsmb will only reliably work with CUPS version 1.1.15 or higher and with Samba version 2.2.4, or later. If it does not work, or if the automatic printer driver download to the clients does not succeed, you can still manually install the CUPS printer PPD on top of the Adobe PostScript driver on @@ -1858,34 +1861,34 @@ with the output your client driver settings produce. Treat it well: Sometimes you can choose PostScript Language Level: in case of problems try 2 instead of 3 (the latest ESP Ghostscript package handles Level 3 PostScript very well; Adobe).

  • - Say Yes to PostScript Error Handler (Adobe).

    • Installing PostScript Driver Files Manually Using rpcclient

    + Say Yes to PostScript Error Handler (Adobe).

    Installing PostScript Driver Files Manually Using rpcclient

    Of course, you can run all the commands that are embedded into the cupsaddsmb convenience utility yourself, one by one, and upload and prepare the driver files for future client downloads.

    1. Prepare Samba (a CUPS print queue with the name of the printer should be there. We are providing the driver now).

    2. Copy all files to [print$].

    3. - + Run rpcclient adddriver (for each client architecture you want to support).

    4. - + Run rpcclient setdriver.

    - - - - - + + + + + We are going to do this now. First, read the man page on rpcclient to get a first idea. Look at all the printing-related subcommands: enumprinters, enumdrivers, enumports, adddriver, and setdriver are among the most interesting ones. rpcclient implements an important part of the MS-RPC protocol. You can use it to query (and command) a Windows NT (or 200x/XP) PC, too. MS-RPC is used by Windows clients, among other things, to benefit from the Point'n'Print features. Samba can now mimic this as well. -

    A Check of the rpcclient man Page

    +

    A Check of the rpcclient man Page

    First let's check the rpcclient man page. Here are two relevant passages:

    - - - + + + adddriver <arch> <config> Execute an AddPrinterDriver() RPC to install the printer driver information on the server. The driver files should already exist in the directory returned by getdriverdir. Possible values for arch are the @@ -1908,18 +1911,18 @@ drivers can use a bidirectional link for communication. This field should be  NT print server, the print monitor for a driver must already be installed before adding the driver or else the RPC will fail.

    - - + + setdriver <printername> <drivername> Execute a SetPrinter() command to update the printer driver associated with an installed printer. The printer driver must already be correctly installed on the print server.

    - - + + See also the enumprinters and enumdrivers commands to obtain a list of installed printers and drivers. -

    Understanding the rpcclient man Page

    - +

    Understanding the rpcclient man Page

    + The exact format isn't made too clear by the man page, since you have to deal with some parameters containing spaces. Here is a better description for it. We have line-broken the command and indicated the breaks with “\”. Usually you would type the command in one line without the line @@ -1943,9 +1946,9 @@ printer presents the files to us. Remember that this whole procedure has to be d listening to the traffic caused by Windows computers on the wire. We may as well turn to a Windows box now and access it from a UNIX workstation. We will query it with rpcclient to see what it tells us and try to understand the man page more clearly. -

    Producing an Example by Querying a Windows Box

    - - +

    Producing an Example by Querying a Windows Box

    + + We could run rpcclient with a getdriver or a getprinter subcommand (in level 3 verbosity) against it. Just sit down at a UNIX or Linux workstation with the Samba utilities installed, then type the following command: @@ -1953,7 +1956,7 @@ workstation with the Samba utilities installed, then type the following command: root# rpcclient -U'user%secret' NT-SERVER -c 'getdriver printername 3'

    From the result it should become clear which is which. Here is an example from my installation: - + 

     root# rpcclient -U'Danka%xxxx' W200xSERVER \
     -c'getdriver "DANKA InfoStream Virtual Printer" 3'
@@ -1984,10 +1987,10 @@ Some printer drivers list additional files under the label ListOfFiles,Comma-separated. For the CUPS PostScript
 drivers, we do not need any (nor would we for the Adobe PostScript driver); therefore, the field will get a
 “NULL” entry.
-

    Requirements for adddriver and setdriver to Succeed

    - - - +

    Requirements for adddriver and setdriver to Succeed

    + + + From the man page (and from the quoted output of cupsaddsmb above) it becomes clear that you need to have certain conditions in order to make the manual uploading and initializing of the driver files succeed. The two rpcclient subcommands (adddriver and @@ -2004,19 +2007,19 @@ succeed. The two rpcclient subcommands ([print$] share and create subdirectories.

  • The printer you are going to set up for the Windows clients needs to be installed in CUPS already.

  • - - + + The CUPS printer must be known to Samba; otherwise the setdriver subcommand fails with an NT_STATUS_UNSUCCESSFUL error. To check if the printer is known by Samba, you may use the enumprinters subcommand to rpcclient. A long-standing bug prevented a proper update of the printer list until every smbd process had received a SIGHUP or was restarted. Remember this in case you've created the CUPS printer just recently and encounter problems: try restarting Samba. -

    • Manual Driver Installation in 15 Steps

    +

    Manual Driver Installation in 15 Steps

    We are going to install a printer driver now by manually executing all required commands. Because this may seem a rather complicated process at first, we go through the procedure step by step, explaining every single action item as it comes up. -

    Procedure 22.2. Manual Driver Installation

    1. Install the printer on CUPS.

      +
      Procedure 22.2. Manual Driver Installation
      1. Install the printer on CUPS.
         	root# lpadmin -p mysmbtstprn -v socket://10.160.51.131:9100 -E \
 				-P canonIR85.ppd
 	
        
@@ -2025,7 +2028,7 @@ single action item as it comes up.
 	(a.k.a. JetDirect or Direct TCP/IP) connection. You need to be root
 	for this step.
 	
      2. (Optional.) Check if the printer is recognized by Samba.
        
-	
+	
 
         root# rpcclient -Uroot%xxxx -c 'enumprinters' localhost \
   | grep -C2 mysmbtstprn
@@ -2045,8 +2048,8 @@ comment:[mysmbtstprn]
 	of the following steps. Alternatively, you can authenticate as one of the users from the “write
 	list” as defined in smb.conf for [print$].
 	
      3. (Optional.) Check if Samba knows a driver for the printer.
        
-	
-	
+	
+	
 
         root# rpcclient -Uroot%xxxx -c 'getprinter mysmbtstprn 2'\
  localhost | grep driver 
@@ -2102,7 +2105,7 @@ drwxr-sr-x    2 root     ntadmin       670 May 16 03:15 3
 The driver files now are in the W32X86 architecture “root” of
 [print$].
 
      4. Tell Samba that these are driver files (adddriver).
        
-
+
 
         root# rpcclient -Uroot%xxxx -c 'adddriver "Windows NT x86" \
 	"mydrivername:cupsdrvr.dll:mysmbtstprn.PPD: \
@@ -2133,7 +2136,7 @@ total 5039
 Notice how step 6 also moved the driver files to the appropriate
 subdirectory. Compare this with the situation after step 5.
 
      5. (Optional.) Verify if Samba now recognizes the driver.
        
-
+
 
         root# rpcclient -Uroot%xxxx -c 'enumdrivers 3' \
 	localhost | grep -B2 -A5 mydrivername
@@ -2148,8 +2151,8 @@ Helpfile: [\\kde-bitshop\print$\W32X86\2\cups.hlp]
 
        
 Remember, this command greps for the name you chose for the
 driver in step 6. This command must succeed before you can proceed.
-
      6. <title>Tell Samba which printer should use these driver files (setdriver).</title>
        
-
+
      7. Tell Samba which printer should use these driver files (setdriver).
        
+
 
         root# rpcclient -Uroot%xxxx -c 'setdriver mysmbtstprn mydrivername' \
 	localhost
@@ -2160,9 +2163,9 @@ queues that use the same driver. You do not need to repeat all the previous step
 succeed. The only preconditions are that enumdrivers must find the driver and
 enumprinters must find the printer.
 
      8. (Optional) Verify if Samba has recognized this association.
        
-
-
-
+
+
+
 
         root# rpcclient -Uroot%xxxx -c 'getprinter mysmbtstprn 2' localhost \
   | grep driver
@@ -2202,13 +2205,13 @@ Printer Driver Info 3:
      comment:[mysmbtstprn]
 
 
        
-
+
 Compare these results with the ones from steps 2 and 3. Every one of these commands show the driver is installed. Even
 the enumprinters command now lists the driver
 on the “description” line.
 
      9. (Optional.) Tickle the driver into a correct
 device mode.
        
-
+
 You certainly know how to install the driver on the client. In case
 you are not particularly familiar with Windows, here is a short
 recipe: Browse the Network Neighborhood, go to the Samba server, and look
@@ -2231,12 +2234,12 @@ into the “DOS box” (type root's smbpasswo
 Change any printer setting once (like changing portrait to
 landscape), click on Apply, and change the setting back.
 
      10. Install the printer on a client (Point'n'Print).
        
-
+
 
         C:\> rundll32 printui.dll,PrintUIEntry /in /n "\\sambaserver\mysmbtstprn"
 
        
 If it does not work, it could be a permissions problem with the [print$] share.
-
      11. (Optional) Print a test page.
        +
      12. (Optional) Print a test page.
         C:\> rundll32 printui.dll,PrintUIEntry /p /n "\\sambaserver\mysmbtstprn"
 
        
 Then hit [TAB] five times, [ENTER] twice, [TAB] once, and [ENTER] again, and march to the printer.
@@ -2246,8 +2249,8 @@ Just put it in a frame and bolt it to the wall with the heading "MY FIRST RPCCLI
  why not just throw it away!
 
      13. (Obligatory.) Enjoy. Jump. Celebrate your success.
         root# echo "Cheeeeerioooooo! Success..." >> /var/log/samba/log.smbd
-

    Troubleshooting Revisited

    - +

    Troubleshooting Revisited

    + The setdriver command will fail if in Samba's mind the queue is not already there. A successful installation displys the promising message that the: 

    @@ -2258,20 +2261,20 @@ a disappointing message like this one:
 
 result was NT_STATUS_UNSUCCESSFUL
 
    
-
-
+
+
 It is not good enough that you can see the queue in CUPS, using the lpstat -p ir85wm
 command. A bug in most recent versions of Samba prevents the proper update of the queue list. The recognition
 of newly installed CUPS printers fails unless you restart Samba or send a HUP to all smbd processes. To verify
 if this is the reason why Samba does not execute the setdriver command successfully, check
 if Samba “sees” the printer:
-
+
 
     root# rpcclient transmeta -N -U'root%xxxx' -c 'enumprinters 0'|grep ir85wm
         printername:[ir85wm]
 
    
 An alternate command could be this: 
-
+
 
     root# rpcclient transmeta -N -U'root%secret' -c 'getprinter ir85wm' 
         cmd = getprinter ir85wm
@@ -2281,28 +2284,28 @@ An alternate command could be this:
         comment:[CUPS PostScript-Treiber for Windows NT/200x/XP]
 
    
 By the way, you can use these commands, plus a few more, of course, to install drivers on remote Windows NT print servers too!
-

    The Printing *.tdb Files

    - - - - - - - - - - - - - +

    The Printing *.tdb Files

    + + + + + + + + + + + + + Some mystery is associated with the series of files with a tdb suffix appearing in every Samba installation. They are connections.tdb, printing.tdb, share_info.tdb, ntdrivers.tdb, unexpected.tdb, brlock.tdb, locking.tdb, ntforms.tdb, messages.tdb , ntprinters.tdb, sessionid.tdb, and secrets.tdb. What is their purpose? -

    Trivial Database Files

    - +

    Trivial Database Files

    + A Windows NT (print) server keeps track of all information needed to serve its duty toward its clients by storing entries in the Windows registry. Client queries are answered by reading from the registry, Administrator or user configuration settings that are saved by writing into the registry. Samba and UNIX @@ -2311,7 +2314,7 @@ of *.tdb files. (TDB stands for trivial data base) /var/lib/samba/ or /var/lock/samba/. The printing-related files are ntprinters.tdb, printing.tdb,ntforms.tdb, and ntdrivers.tdb. -

    Binary Format

    +

    Binary Format

    *.tdb files are not human readable. They are written in a binary format. “Why not ASCII?”, you may ask. “After all, ASCII configuration files are a good and proven tradition on UNIX.” The reason for this design decision by the Samba Team is mainly performance. Samba needs to be @@ -2320,16 +2323,16 @@ thousands of them. Some of these smbds might need t *.tdb file at the same time. The file format of Samba's *.tdb files allows for this provision. Many smbd processes may write to the same *.tdb file at the same time. This wouldn't be possible with pure ASCII files. -

    Losing *.tdb Files

    +

    Losing *.tdb Files

    It is very important that all *.tdb files remain consistent over all write and read accesses. However, it may happen that these files do get corrupted. (A kill -9 `pidof smbd' while a write access is in progress could do the damage, as could a power interruption, etc.). In cases of trouble, a deletion of the old printing-related *.tdb files may be the only option. After that, you need to re-create all print-related setups unless you have made a backup of the *.tdb files in time. -

    Using tdbbackup

    - - +

    Using tdbbackup

    + + Samba ships with a little utility that helps the root user of your system to backup your *.tdb files. If you run it with no argument, it prints a usage message: 

    @@ -2356,10 +2359,10 @@ ntprinters.tdb sessionid.tdb
  -rw-------    1 root     root        40960 May  2 03:44 printing.tdb
  -rw-------    1 root     root        40960 May  2 03:44 printing.tdb.bak
 
-

    CUPS Print Drivers from Linuxprinting.org

    - +

    CUPS Print Drivers from Linuxprinting.org

    + CUPS ships with good support for HP LaserJet-type printers. You can install the generic driver as follows: - + 

     root# lpadmin -p laserjet4plus -v parallel:/dev/lp0 -E -m laserjet.ppd

    @@ -2375,9 +2378,9 @@ excellent recommendations about which driver is best used for each printer. Its the tireless work of Till Kamppeter from Mandrakesoft, who is also the principal author of the foomatic-rip utility.

    Note

    - - - + + + The former cupsomatic concept is now being replaced by the new successor, a much more powerful foomatic-rip. cupsomatic is no longer maintained. Here is the new URL to the Foomatic-3.0 @@ -2386,9 +2389,9 @@ for your Foomatic-driven printers. foomatic-rip will not work with PPDs generate cupsomatic. The new-style PPDs are 100% compliant with the Adobe PPD specification. They are also intended to be used by Samba and the cupsaddsmb utility, to provide the driver files for the Windows clients! -

    foomatic-rip and Foomatic Explained

    - - +

    foomatic-rip and Foomatic Explained

    + + Nowadays, most Linux distributions rely on the utilities from the Linuxprinting.org to create their printing-related software (which, by the way, works on all UNIXes and on Mac OS X and Darwin, too). The utilities from this sire have a very end-user-friendly interface that allows for an easy update of drivers and PPDs for all supported models, @@ -2399,8 +2402,8 @@ Recently, Foomatic has achieved the astonishing milestone of Foomatic database. Currently there are 245 drivers in the database. Many drivers support various models, and many models may be driven by different drivers its your choice! -

    690 “Perfect” Printers

    - +

    690 “Perfect” Printers

    + At present, there are 690 devices dubbed as working perfectly: 181 are mostly perfect, 96 are partially perfect, and 46 are paperweights. Keeping in mind that most of these are non-PostScript models (PostScript printers are automatically supported by CUPS to perfection by using their @@ -2408,7 +2411,7 @@ own manufacturer-provided Windows PPD), and that a multifunctional device never if it does not also scan and copy and fax under GNU/Linux then this is a truly astonishing achievement! Three years ago the number was not more than 500, and Linux or UNIX printing at the time wasn't anywhere near the quality it is today. -

    How the Printing HOWTO Started It All

    +

    How the Printing HOWTO Started It All

    A few years ago Grant Taylor started it all. The roots of today's Linuxprinting.org are in the first Linux Printing HOWTO that he authored. As a side-project to this document, which served many Linux users and admins to guide their first steps in this @@ -2417,8 +2420,8 @@ distinct patterns of ink or toner particles on paper substrates”), Postgres database with information about the hardware and driver zoo that made up Linux printing of the time. This database became the core component of today's Foomatic collection of tools and data. In the meantime, it has moved to an XML representation of the data. -

    Foomatic's Strange Name

    - +

    Foomatic's Strange Name

    + “Why the funny name?” you ask. When it really took off, around spring 2000, CUPS was far less popular than today, and most systems used LPD, LPRng, or even PDQ to print. CUPS shipped with a few generic drivers (good for a few hundred different printer models). These didn't support many device-specific options. @@ -2436,10 +2439,10 @@ several birds with one stone: to CUPS users (because often the traditional Ghostscript way of printing was the only one available).

  • It gave all the advanced CUPS options (Web interface, GUI driver configurations) to users wanting (or needing) to use - Ghostscript filters.

    • cupsomatic, pdqomatic, lpdomatic, directomatic

    - - - + Ghostscript filters.

    cupsomatic, pdqomatic, lpdomatic, directomatic

    + + + CUPS worked through a quickly hacked-up filter script named cupsomatic. cupsomatic ran the printfile through Ghostscript, constructing automatically the rather complicated command line needed. It just needed to be copied into the CUPS system to make it work. To configure the way cupsomatic controls the @@ -2460,8 +2463,8 @@ So, to answer your question, “Foomatic” i behind the “*omatic” scripts. Foomatic, up to versions 2.0.x, required (ugly) Perl data structures attached to Linuxprinting.org PPDs for CUPS. It had a different “*omatic” script for every spooler, as well as different printer configuration files. -

    The Grand Unification Achieved

    - +

    The Grand Unification Achieved

    + This has all changed in Foomatic versions 2.9 (beta) and released as “stable” 3.0. It has now achieved the convergence of all *omatic scripts and is called the foomatic-rip. This single script is the unification of the previously different spooler-specific *omatic scripts. @@ -2470,18 +2473,18 @@ PostScript printer PPDs and the Linuxprinting.org-generated ones), all of a sudd have the power of PPDs at their disposal. Users only need to plug foomatic-rip into their system. For users there is improved media type and source support paper sizes and trays are easier to configure.

    - - - + + + Also, the new generation of Linuxprinting.org PPDs no longer contains Perl data structures. If you are a distro maintainer and have used the previous version of Foomatic, you may want to give the new one a spin, but remember to generate a new-version set of PPDs via the new foomatic-db-engine!. Individual users just need to generate a single new PPD specific to their model by following the steps outlined in the Foomatic tutorial or in this chapter. This new development is truly amazing.

    - - - + + + foomatic-rip is a very clever wrapper around the need to run Ghostscript with a different syntax, options, device selections, and/or filters for each different printer or spooler. At the same time, it can read the PPD associated with a print queue and modify the print job according to the user selections. Together with this @@ -2489,8 +2492,8 @@ comes the 100% compliance of the new Foomatic PPDs with the Adobe spec. Some inn Foomatic concept may surprise users. It will support custom paper sizes for many printers and will support printing on media drawn from different paper trays within the same job (in both cases, even where there is no support for this from Windows-based vendor printer drivers). -

    Driver Development Outside

    - +

    Driver Development Outside

    + Most driver development itself does not happen within Linuxprinting.org. Drivers are written by independent maintainers. Linuxprinting.org just pools all the information and stores it in its database. In addition, it also provides the Foomatic glue to integrate the many drivers into any modern (or legacy) printing system @@ -2498,25 +2501,25 @@ known to the world.

    Speaking of the different driver development groups, most of the work is currently done in three projects:

    • - + Omni a free software project by IBM that tries to convert its printer driver knowledge from good-ol' OS/2 times into a modern, modular, universal driver architecture for Linux/UNIX (still beta). This currently supports 437 models.

    • - + HPIJS a free software project by HP to provide the support for its own range of models (very mature, printing in most cases is perfect and provides true photo quality). This currently supports 369 models.

    • - - Gimp-Print a free software + + Gutenprint a free software effort, started by Michael Sweet (also lead developer for CUPS), now directed by Robert Krawitz, which has achieved an amazing level of photo print quality (many Epson users swear that its quality is better than the vendor drivers provided by Epson for the Microsoft - platforms). This currently supports 522 models.

    Forums, Downloads, Tutorials, Howtos (Also for Mac OS X and Commercial UNIX)

    + platforms). This currently supports 522 models.

    Forums, Downloads, Tutorials, Howtos (Also for Mac OS X and Commercial UNIX)

    Linuxprinting.org today is the one-stop shop to download printer drivers. Look for printer information and tutorials or solve printing problems in its popular forums. This @@ -2525,9 +2528,9 @@ commercial UNIX systems are also going there, and the relatively new Mac OS X forum has turned out to be one of the most frequented forums after only a few weeks.

    - - - + + + Linuxprinting.org and the Foomatic driver wrappers around Ghostscript are now a standard tool-chain for printing on all the important distros. Most of them also have CUPS underneath. While in recent years most printer data had been added by Kamppeter, many additional contributions came from engineers with SuSE, Red @@ -2536,16 +2539,16 @@ and Conectiva have merged and are now called Mandriva.

    Note

    Till Kamppeter from Mandrakesoft is doing an excellent job in his spare time to maintain Linuxprinting.org and Foomatic. So if you use it often, please send him a note showing your appreciation. -

    Foomatic Database-Generated PPDs

    - - - - - - - - - +

    Foomatic Database-Generated PPDs

    + + + + + + + + + The Foomatic database is an amazing piece of ingenuity in itself. Not only does it keep the printer and driver information, but it is organized in a way that it can generate PPD files on the fly from its internal XML-based datasets. While these PPDs are modeled to the Adobe specification of PPDs, the @@ -2560,7 +2563,7 @@ ask from Ghostscript to convert the PostScript print job into a raster format re This usage of PPDs to describe the options of non-PostScript printers was the invention of the CUPS developers. The rest is easy. GUI tools (like KDE's marvelous kprinter or the GNOME gtklp xpp and the CUPS Web interface) read the PPD as well and use this information to present the available settings to the user as an intuitive menu selection. -

    foomatic-rip and Foomatic PPD Download and Installation

    +

    foomatic-rip and Foomatic PPD Download and Installation

    Here are the steps to install a foomatic-rip-driven LaserJet 4 Plus-compatible printer in CUPS (note that recent distributions of SuSE, UnitedLinux and Mandrake may ship with a complete package of Foomatic-PPDs plus the @@ -2653,8 +2656,8 @@ how the resulting raster data should look and which printer commands to embed in fit for your printer model's consumption.

  • Ghostscript must (depending on the driver/model) contain support for a certain device representing the selected driver for your model (as shown by gs -h).

  • foomatic-rip needs a new version of PPDs (PPD versions - produced for cupsomatic do not work with foomatic-rip).

    • Page Accounting with CUPS

    - + produced for cupsomatic do not work with foomatic-rip).

    Page Accounting with CUPS

    + Often there are questions regarding print quotas where Samba users (that is, Windows clients) should not be able to print beyond a certain number of pages or data volume per day, week, or month. This feature is dependent on the real print subsystem you're using. Samba's part is always to receive the job files from the @@ -2662,18 +2665,18 @@ clients (filtered or unfiltered) and hand

    Of course one could hack things with one's own scripts. But then there is CUPS. CUPS supports quotas that can be based on the size of jobs or on the number of pages or both, and can span any time period you want. -

    Setting Up Quotas

    - +

    Setting Up Quotas

    + This is an example command of how root would set a print quota in CUPS, assuming an existing printer named “quotaprinter”: - + 

     root# lpadmin -p quotaprinter -o job-quota-period=604800 \
 	-o job-k-limit=1024 -o job-page-limit=100

    This would limit every single user to print no more than 100 pages or 1024 KB of data (whichever comes first) within the last 604,800 seconds ( = 1 week). -

    Correct and Incorrect Accounting

    +

    Correct and Incorrect Accounting

    For CUPS to count correctly, the printfile needs to pass the CUPS pstops filter; otherwise it uses a dummy count of “one”. Some print files do not pass it (e.g., image files), but then those are mostly one-page jobs anyway. This also means that proprietary drivers for the target printer running on the client @@ -2684,12 +2687,12 @@ You need to send PostScript from the clients (i.e., run a PostScript driver ther accounting done. If the printer is a non-PostScript model, you need to let CUPS do the job to convert the file to a print-ready format for the target printer. This is currently working for about a thousand different printer models. Linuxprinting.org has a driver list. -

    Adobe and CUPS PostScript Drivers for Windows Clients

    - - - - - +

    Adobe and CUPS PostScript Drivers for Windows Clients

    + + + + + Before CUPS 1.1.16, your only option was to use the Adobe PostScript driver on the Windows clients. The output of this driver was not always passed through the pstops filter on the CUPS/Samba side, and therefore was not counted correctly (the reason is that it often, depending on the PPD being used, wrote a @@ -2700,13 +2703,13 @@ From CUPS 1.1.16 and later releases, you can use the CUPS PostScript driver for clients (which is tagged in the download area of http://www.cups.org/ as the cups-samba-1.1.16.tar.gz package). It does not work for Windows 9x/Me clients, but it guarantees: -

    • To not write a PJL-header.

    • To still read and support all PJL-options named in the +

      • To not write a PJL-header.

      • To still read and support all PJL-options named in the driver PPD with its own means.

      • That the file will pass through the pstops filter on the CUPS/Samba server.

      • To page-count correctly the print file.

      You can read more about the setup of this combination in the man page for cupsaddsmb (which is only present with CUPS installed, and only current from CUPS 1.1.16). -

    The page_log File Syntax

    - +

    The page_log File Syntax

    + These are the items CUPS logs in the page_log for every page of a job:

    • Printer name

    • User name

    • Job ID

    • Time of printing

    • Page number

    • Number of copies

    • A billing information string (optional)

    • The host that sent the job (included since version 1.1.19)

    Here is an extract of my CUPS server's page_log file to illustrate the @@ -2724,7 +2727,7 @@ by user kurt, a 64-page job printed in t The next job had ID 402, was sent by user boss from IP address 10.160.51.33, printed from one page 440 copies, and is set to be billed to finance-dep. -

    Possible Shortcomings

    +

    Possible Shortcomings

    What flaws or shortcomings are there with this quota system?

    • The ones named above (wrongly logged job in case of printer hardware failure, and so on).

    • In reality, CUPS counts the job pages that are being @@ -2738,7 +2741,7 @@ What flaws or shortcomings are there with this quota system? “used-up” number of current quota.

    • A user having used up 99 sheets of a 100 quota will still be able to send and print a 1,000 sheet job.

    • A user being denied a job because of a filled-up quota does not get a meaningful error message from CUPS other than - “client-error-not-possible”.

    Future Developments

    + “client-error-not-possible”.

    Future Developments

    This is the best system currently available, and there are huge improvements under development for CUPS 1.2:

    • Page counting will go into the backends (these talk @@ -2746,10 +2749,10 @@ improvements under development for CUPS 1.2: actual printing process; thus, a jam at the fifth sheet will lead to a stop in the counting).

    • Quotas will be handled more flexibly.

    • Probably there will be support for users to inquire about their accounts in advance.

    • Probably there will be support for some other tools - around this topic.

    Other Accounting Tools

    + around this topic.

    Other Accounting Tools

    Other accounting tools that can be used includes: PrintAnalyzer, pyKota, printbill, LogReport. For more information regarding these tools you can try a Google search. -

    Additional Material

    +

    Additional Material

    A printer queue with no PPD associated to it is a “raw” printer, and all files will go directly there as received by the spooler. The exceptions are file types application/octet-stream @@ -2828,15 +2831,15 @@ the jobs of hundreds of users on some big machine, where no user is allowed to have direct access (such as when the operators often need to load the proper paper type before running the 10,000 page job requested by marketing for the mailing, and so on). -

    Autodeletion or Preservation of CUPS Spool Files

    - - - +

    Autodeletion or Preservation of CUPS Spool Files

    + + + Samba print files pass through two spool directories. One is the incoming directory managed by Samba (set in the path = /var/spool/samba directive in the [printers] section of smb.conf). The other is the spool directory of your UNIX print subsystem. For CUPS it is normally /var/spool/cups/, as set by the cupsd.conf directive RequestRoot /var/spool/cups. -

    CUPS Configuration Settings Explained

    +

    CUPS Configuration Settings Explained

    Some important parameter settings in the CUPS configuration file cupsd.conf are:

    PreserveJobHistory Yes

    @@ -2860,7 +2863,7 @@ Some important parameter settings in the CUPS configuration file

    (There are also additional settings for MaxJobsPerUser and MaxJobsPerPrinter.) -

    Preconditions

    +

    Preconditions

    For everything to work as it should, you need to have three things:

    • A Samba smbd that is compiled against libcups (check on Linux by running ldd `which smbd').

    • A Samba-smb.conf setting of @@ -2873,14 +2876,14 @@ In this case, all other manually set printing-related commands (like lppause command, and lpresume command) are ignored, and they should normally have no influence whatsoever on your printing. -

    Manual Configuration

    +

    Manual Configuration

    If you want to do things manually, replace the printing = cups by printing = bsd. Then your manually set commands may work (I haven't tested this), and a print command = lp -d %P %s; rm %s may do what you need. -

    Printing from CUPS to Windows-Attached Printers

    - - +

    Printing from CUPS to Windows-Attached Printers

    + + From time to time the question arises, how can you print to a Windows-attached printer from Samba? Normally the local connection from Windows host to printer would be done by USB or parallel cable, but this does not matter to Samba. From here only an SMB connection needs to be opened @@ -2915,8 +2918,8 @@ If this symlink does not exist, create it: 

     root# ln -s `which smbspool` /usr/lib/cups/backend/smb

    - - + + smbspool was written by Mike Sweet from the CUPS folks. It is included and ships with Samba. It may also be used with print subsystems other than CUPS, to spool jobs to Windows printer shares. To set up printer winprinter on CUPS, you need to have a driver for it. Essentially @@ -2931,9 +2934,9 @@ To install a printer with the smb backen root# lpadmin -p winprinter -v smb://WINDOWSNETBIOSNAME/printersharename \ -P /path/to/PPD

    - - - + + + The PPD must be able to direct CUPS to generate the print data for the target model. For PostScript printers, just use the PPD that would be used with the Windows NT PostScript driver. But what can you do if the printer is only accessible with a password? Or if the printer's host is part of another workgroup? This is provided @@ -2946,10 +2949,10 @@ if you want to protect your passwords. Better share the printer in a way that do Printing will only work if you have a working NetBIOS name resolution up and running. Note that this is a feature of CUPS and you do not necessarily need to have smbd running. -

    More CUPS Filtering Chains

    +

    More CUPS Filtering Chains

    The diagrams in Filtering Chain 1 and Filtering Chain with cupsomatic show how CUPS handles print jobs. -

    Figure 22.17. Filtering Chain 1.

    Filtering Chain 1.

    Figure 22.18. Filtering Chain with cupsomatic

    Filtering Chain with cupsomatic

    Common Errors

    Windows 9x/Me Client Can't Install Driver

    For Windows 9x/Me, clients require the printer names to be eight +

    Figure 22.17. Filtering Chain 1.

    Filtering Chain 1.

    Figure 22.18. Filtering Chain with cupsomatic

    Filtering Chain with cupsomatic

    Common Errors

    Windows 9x/Me Client Can't Install Driver

    For Windows 9x/Me, clients require the printer names to be eight characters (or “8 plus 3 chars suffix”) max; otherwise, the driver files will not get transferred when you want to download them from Samba.

    “cupsaddsmb” Keeps Asking for Root Password in Never-ending Loop

    Have you set security = user? Have you used smbpasswd to give root a Samba account? @@ -2960,10 +2963,10 @@ cupsomatic show how CUPS handles print jobs. password).

    If the error is “Tree connect failed: NT_STATUS_BAD_NETWORK_NAME”, you may have forgotten to create the /etc/samba/drivers directory. -

    “cupsaddsmb” or “rpcclient addriver” Emit Error

    +

    “cupsaddsmb” or “rpcclient addriver” Emit Error

    If cupsaddsmb, or rpcclient addriver emit the error message WERR_BAD_PASSWORD, refer to the previous common error. -

    “cupsaddsmb” Errors

    +

    “cupsaddsmb” Errors

    The use of “cupsaddsmb” gives “No PPD file for printer...” message while PPD file is present. What might the problem be?

    @@ -2974,10 +2977,10 @@ cupsomatic show how CUPS handles print jobs. cupsaddsmb -H sambaserver -h cupsserver -v printername.

    Is your TempDir directive in cupsd.conf set to a valid value, and is it writable? -

    Client Can't Connect to Samba Printer

    Use smbstatus to check which user +

    Client Can't Connect to Samba Printer

    Use smbstatus to check which user you are from Samba's point of view. Do you have the privileges to write into the [print$] - share?

    New Account Reconnection from Windows 200x/XP Troubles

    + share?

    New Account Reconnection from Windows 200x/XP Troubles

    Once you are connected as the wrong user (for example, as nobody, which often occurs if you have map to guest = bad user), Windows Explorer will not accept an attempt to connect again as a different user. There will not be any bytes transferred on the wire to Samba, @@ -2992,47 +2995,47 @@ user. The best method is to use a DOS terminal window and Printers folder (on the Samba server in the Network Neighborhood), right-click on the printer in question, and select Connect..... -

    Avoid Being Connected to the Samba Server as the Wrong User

    - +

    Avoid Being Connected to the Samba Server as the Wrong User

    + You see per smbstatus that you are connected as user nobody, but you want to be root or printer admin. This is probably due to map to guest = bad user, which silently connected you under the guest account when you gave (maybe by accident) an incorrect username. Remove map to guest if you want to prevent this. -

    Upgrading to CUPS Drivers from Adobe Drivers

    +

    Upgrading to CUPS Drivers from Adobe Drivers

    This information came from a mailing list posting regarding problems experienced when upgrading from Adobe drivers to CUPS drivers on Microsoft Windows NT/200x/XP clients.

    First delete all old Adobe-using printers. Then delete all old Adobe drivers. (On Windows 200x/XP, right-click in the background of Printers folder, select Server Properties..., select -tab Drivers, and delete here).

    Can't Use “cupsaddsmb” on Samba Server, Which Is a PDC

    Do you use the “naked” root user name? Try to do it +tab Drivers, and delete here).

    Can't Use “cupsaddsmb” on Samba Server, Which Is a PDC

    Do you use the “naked” root user name? Try to do it this way: cupsaddsmb -U DOMAINNAME\\root -v printername> (note the two backslashes: the first one is -required to “escape” the second one).

    Deleted Windows 200x Printer Driver Is Still Shown

    Deleting a printer on the client will not delete the +required to “escape” the second one).

    Deleted Windows 200x Printer Driver Is Still Shown

    Deleting a printer on the client will not delete the driver too (to verify, right-click on the white background of the Printers folder, select Server Properties and click on the Drivers tab). These same old drivers will be re-used when you try to install a printer with the same name. If you want to update to a new driver, delete the old ones first. Deletion is only possible if no -other printer uses the same driver.

    Windows 200x/XP Local Security Policies

    Local security policies may not allow the installation of unsigned drivers “local -security policies” may not allow the installation of printer drivers at all.

    Administrator Cannot Install Printers for All Local Users

    - - +other printer uses the same driver.

    Windows 200x/XP Local Security Policies

    Local security policies may not allow the installation of unsigned drivers “local +security policies” may not allow the installation of printer drivers at all.

    Administrator Cannot Install Printers for All Local Users

    + + Windows XP handles SMB printers on a “per-user” basis. This means every user needs to install the printer himself or herself. To have a printer available for everybody, you might want to use the built-in IPP client capabilities of Win XP. Add a printer with the print path of http://cupsserver:631/printers/printername. We're still looking into this one. Maybe a logon script could automatically install printers for all users. -

    Print Change, Notify Functions on NT Clients

    For print change, notify functions on NT++ clients. These need to run the Server -service first (renamed to File & Print Sharing for MS Networks in XP).

    Win XP-SP1

    Win XP-SP1 introduced a Point and Print Restriction Policy (this restriction does not apply to +

    Print Change, Notify Functions on NT Clients

    For print change, notify functions on NT++ clients. These need to run the Server +service first (renamed to File & Print Sharing for MS Networks in XP).

    Windows XP SP1

    Windows XP SP1 introduced a Point and Print Restriction Policy (this restriction does not apply to “Administrator” or “Power User” groups of users). In Group Policy Object Editor, go to User Configuration -> Administrative Templates -> Control Panel -> Printers. The policy is automatically set to Enabled and the Users can only Point and Print to machines in their Forest . You probably need to change it to Disabled or Users can only Point and Print to these servers to make driver downloads from Samba possible. -

    Print Options for All Users Can't Be Set on Windows 200x/XP

    How are you doing it? I bet the wrong way (it is not easy to find out, though). There are three +

    Print Options for All Users Can't Be Set on Windows 200x/XP

    How are you doing it? I bet the wrong way (it is not easy to find out, though). There are three different ways to bring you to a dialog that seems to set everything. All three dialogs look the same, yet only one of them does what you intend. You need to be Administrator or -Print Administrator to do this for all users. Here is how I do in on XP: +Print Administrator to do this for all users. Here is how I do it on XP:

    1. The first wrong way:

      1. Open the Printers @@ -3062,33 +3065,33 @@ all clients to get the same defaults, you need to conduct these steps printer admin in smb.conf) before a client downloads the driver (the clients can later set their own per-user defaults by following the procedures A or B). -

      Most Common Blunders in Driver Settings on Windows Clients

      +

      Most Common Blunders in Driver Settings on Windows Clients

      Don't use Optimize for Speed, but use Optimize for Portability instead (Adobe PS Driver). Don't use Page Independence: No. Always settle with Page Independence: Yes (Microsoft PS Driver and CUPS PS Driver for Windows NT/200x/XP). If there are problems with fonts, use Download as Softfont into printer (Adobe PS Driver). For TrueType Download Options choose Outline. Use PostScript Level 2 if you are having trouble with a non-PS printer and if there is a choice. -

      cupsaddsmb Does Not Work with Newly Installed Printer

      +

      cupsaddsmb Does Not Work with Newly Installed Printer

      Symptom: The last command of cupsaddsmb does not complete successfully. If the cmd = setdriver printername printername result was NT_STATUS_UNSUCCESSFUL, then possibly the printer was not yet recognized by Samba. Did it show up in Network Neighborhood? Did it show up in rpcclient hostname -c `enumprinters'? Restart smbd (or send a kill -HUP to all processes listed by smbstatus, and try again. -

      Permissions on /var/spool/samba/ Get Reset After Each Reboot

      +

      Permissions on /var/spool/samba/ Get Reset After Each Reboot

      Have you ever by accident set the CUPS spool directory to the same location (RequestRoot /var/spool/samba/ in cupsd.conf or the other way round: /var/spool/cups/ is set as path> in the [printers] section)? These must be different. Set RequestRoot /var/spool/cups/ in cupsd.conf and path = /var/spool/samba in the [printers] section of smb.conf. Otherwise, cupsd will sanitize permissions to its spool directory with each restart and printing will not work reliably. -

      Print Queue Called “lp” Mishandles Print Jobs

      +

      Print Queue Called “lp” Mishandles Print Jobs

      In this case a print queue called “lp” intermittently swallows jobs and spits out completely different ones from what was sent.

      - - - + + + It is a bad idea to name any printer “lp”. This is the traditional UNIX name for the default printer. CUPS may be set up to do an automatic creation of Implicit Classes. This means, to group all printers with the same name to a pool of devices and load-balance the jobs across them in a round-robin fashion. @@ -3097,13 +3100,13 @@ jobs and send your own to his or her device unwittingly. To have tight control o BrowseShortNames No. It will present any printer as printername@cupshost, which gives you better control over what may happen in a large networked environment. -

      Location of Adobe PostScript Driver Files for “cupsaddsmb”

      +

      Location of Adobe PostScript Driver Files for “cupsaddsmb”

      Use smbclient to connect to any Windows box with a shared PostScript printer: smbclient //windowsbox/print\$ -U guest. You can navigate to the W32X86/2 subdir to mget ADOBE* and other files or to WIN40/0 to do the same. Another option is to download the *.exe packaged files from the Adobe Web site. -

    Overview of the CUPS Printing Processes

    +

    Overview of the CUPS Printing Processes

    A complete overview of the CUPS printing processes can be found in the CUPS Printing Overview diagram. -

    Figure 22.19. CUPS Printing Overview.

    CUPS Printing Overview.


    [6] See also http://www.cups.org/cups-help.html

    Prev Up Next
    Chapter 21. Classical Printing Support Home Chapter 23. Stackable VFS modules
    +

    Figure 22.19. CUPS Printing Overview.

    CUPS Printing Overview.


    [6] See also http://www.cups.org/cups-help.html

    Prev Up Next
    Chapter 21. Classical Printing Support Home Chapter 23. Stackable VFS modules
    diff --git a/docs/htmldocs/Samba3-HOWTO/ChangeNotes.html b/docs/htmldocs/Samba3-HOWTO/ChangeNotes.html index d18365a5b2..dcdbefe5fd 100644 --- a/docs/htmldocs/Samba3-HOWTO/ChangeNotes.html +++ b/docs/htmldocs/Samba3-HOWTO/ChangeNotes.html @@ -1,10 +1,10 @@ -Chapter 9. Important and Critical Change Notes for the Samba 3.x Series
    Chapter 9. Important and Critical Change Notes for the Samba 3.x Series
    Prev Part III. Advanced Configuration Next

    Chapter 9. Important and Critical Change Notes for the Samba 3.x Series

    John H. Terpstra

    Samba Team

    Gerald (Jerry) Carter

    Samba Team

    Table of Contents

    Important Samba-3.2.x Change Notes
    Important Samba-3.0.x Change Notes
    User and Group Changes
    Essential Group Mappings
    Passdb Changes
    Group Mapping Changes in Samba-3.0.23
    LDAP Changes in Samba-3.0.23

    +Chapter 9. Important and Critical Change Notes for the Samba 3.x Series

    Chapter 9. Important and Critical Change Notes for the Samba 3.x Series
    Prev Part III. Advanced Configuration Next

    Chapter 9. Important and Critical Change Notes for the Samba 3.x Series

    John H. Terpstra

    Samba Team

    Gerald (Jerry) Carter

    Samba Team

    Table of Contents

    Important Samba-3.2.x Change Notes
    Important Samba-3.0.x Change Notes
    User and Group Changes
    Essential Group Mappings
    Passdb Changes
    Group Mapping Changes in Samba-3.0.23
    LDAP Changes in Samba-3.0.23

    Please read this chapter carefully before update or upgrading Samba. You should expect to find only critical or very important information here. Comprehensive change notes and guidance information can be found in the section Updating and Upgrading Samba. -

    Important Samba-3.2.x Change Notes

    +

    Important Samba-3.2.x Change Notes

    !!!!!!!!!!!!Add all critical update notes here!!!!!!!!!!!!! -

    Important Samba-3.0.x Change Notes

    +

    Important Samba-3.0.x Change Notes

    These following notes pertain in particular to Samba 3.0.23 through Samba 3.0.25c (or more recent 3.0.25 update). Samba is a fluid and ever changing project. Changes throughout the 3.0.x series release are documented in this documention - See Upgrading from Samba-2.x to Samba-3.0.25. @@ -21,35 +21,35 @@ such time as the body of this HOWTO is restructured or modified.

    This chapter is new to the release of the HOWTO for Samba 3.0.23. It includes much of the notes provided in the WHATSNEW.txt file that is included with the Samba source code release tarball. -

    User and Group Changes

    +

    User and Group Changes

    The change documented here affects unmapped user and group accounts only.

    - - - - - + + + + + The user and group internal management routines have been rewritten to prevent overlaps of assigned Relative Identifiers (RIDs). In the past the has been a potential problem when either manually mapping Unix groups with the net groupmap command or when migrating a Windows domain to a Samba domain by executing: net rpc vampire.

    - - - - + + + + Unmapped users are now assigned a SID in the S-1-22-1 domain and unmapped groups are assigned a SID in the S-1-22-2 domain. Previously they were assigned a RID within the SAM on the Samba server. For a domain controller this would have been under the authority of the domain SID where as on a member server or standalone server, this would have been under the authority of the local SAM (see the man page for net getlocalsid).

    - - - - - + + + + + The result is that any unmapped users or groups on an upgraded Samba domain controller may be assigned a new SID. Because the SID rather than a name is stored in Windows security descriptors, this can cause a user to no longer have access to a resource for example if a @@ -59,19 +59,19 @@ GID and not the SID for authorization checks.

    An example helps to illustrate the change:

    - - - - + + + + Assume that a group named developers exists with a UNIX GID of 782. In this case this user does not exist in Samba's group mapping table. It would be perfectly normal for this group to be appear in an ACL editor. Prior to Samba-3.0.23, the group SID might appear as S-1-5-21-647511796-4126122067-3123570092-2565.

    - - - - + + + + With the release of Samba-3.0.23, the group SID would be reported as S-1-22-2-782. Any security descriptors associated with files stored on a Windows NTFS disk partition will not allow access based on the group permissions if the user was not a member of the @@ -79,13 +79,13 @@ on the group permissions if the user was not a member of the S-1-22-2-782 and not reported in a user's token, Windows would fail the authorization check even though both SIDs in some respect refer to the same UNIX group.

    - - + + The workaround for versions of Samba prior to 3.0.23, is to create a manual domain group mapping entry for the group developers to point at the S-1-5-21-647511796-4126122067-3123570092-2565 SID. With the release of Samba-3.0.23 this workaround is no longer needed. -

    Essential Group Mappings

    +

    Essential Group Mappings

    Samba 3.0.x series releases before 3.0.23 automatically created group mappings for the essential Windows domain groups Domain Admins, Domain Users, Domain Guests. Commencing with Samba 3.0.23 these mappings need to be created by the Samba administrator. Failure to do this may result in a failure to @@ -102,39 +102,39 @@ domguests respectively.

    For further information regarding group mappings see Group Mapping: MS Windows and UNIX. -

    Passdb Changes

    - - - - +

    Passdb Changes

    + + + + The passdb backend parameter no long accepts multiple passdb backends in a chained configuration. Also be aware that the SQL and XML based passdb modules have been removed in the Samba-3.0.23 release. More information regarding external support for a SQL passdb module can be found on the pdbsql web site. -

    Group Mapping Changes in Samba-3.0.23

    - - - - - - - - - - - +

    Group Mapping Changes in Samba-3.0.23

    + + + + + + + + + + + The default mapping entries for groups such as Domain Admins are no longer created when using an smbpasswd file or a tdbsam passdb backend. This means that it is necessary to explicitly execute the net groupmap add to create group mappings, rather than use the net groupmap modify method to create the Windows group SID to UNIX GID mappings. This change has no effect on winbindd's IDMAP functionality for domain groups. -

    LDAP Changes in Samba-3.0.23

    - - - - - +

    LDAP Changes in Samba-3.0.23

    + + + + + There has been a minor update the Samba LDAP schema file. A substring matching rule has been added to the sambaSID attribute definition. For OpenLDAP servers, this will require the addition of index sambaSID sub to the diff --git a/docs/htmldocs/Samba3-HOWTO/ClientConfig.html b/docs/htmldocs/Samba3-HOWTO/ClientConfig.html index e775d55459..ccf1cc3d47 100644 --- a/docs/htmldocs/Samba3-HOWTO/ClientConfig.html +++ b/docs/htmldocs/Samba3-HOWTO/ClientConfig.html @@ -1,20 +1,20 @@ -Chapter 8. MS Windows Network Configuration Guide

    Chapter 8. MS Windows Network Configuration Guide
    Prev Part II. Server Configuration Basics Next

    Chapter 8. MS Windows Network Configuration Guide

    John H. Terpstra

    Samba Team

    Table of Contents

    Features and Benefits
    Technical Details
    TCP/IP Configuration
    Joining a Domain: Windows 2000/XP Professional
    Domain Logon Configuration: Windows 9x/Me
    Common Errors

    Features and Benefits

    - - - +Chapter 8. MS Windows Network Configuration Guide

    Chapter 8. MS Windows Network Configuration Guide
    Prev Part II. Server Configuration Basics Next

    Chapter 8. MS Windows Network Configuration Guide

    John H. Terpstra

    Samba Team

    Table of Contents

    Features and Benefits
    Technical Details
    TCP/IP Configuration
    Joining a Domain: Windows 2000/XP Professional
    Domain Logon Configuration: Windows 9x/Me
    Common Errors

    Features and Benefits

    + + + Occasionally network administrators report difficulty getting Microsoft Windows clients to interoperate correctly with Samba servers. It seems that some folks just cannot accept the fact that the right way to configure an MS Windows network client is precisely as one would do when using MS Windows NT4 or 200x servers. Yet there is repetitious need to provide detailed Windows client configuration instructions.

    - - + + The purpose of this chapter is to graphically illustrate MS Windows client configuration for the most common critical aspects of such configuration. An experienced network administrator will not be interested in the details of this chapter. -

    Technical Details

    - - +

    Technical Details

    + + This chapter discusses TCP/IP protocol configuration as well as network membership for the platforms that are in common use today. These are:

    • @@ -23,27 +23,27 @@ that are in common use today. These are: Windows 2000 Professional

    • Windows Millennium edition (Me) -

    TCP/IP Configuration

    - - +

    TCP/IP Configuration

    + + The builder of a house must ensure that all construction takes place on a firm foundation. The same is true for the builder of a TCP/IP-based networking system. Fundamental network configuration problems will plague all network users until they are resolved.

    - - + + MS Windows workstations and servers can be configured either with fixed IP addresses or via DHCP. The examples that follow demonstrate the use of DHCP and make only passing reference to those situations where fixed IP configuration settings can be effected.

    - - + + It is possible to use shortcuts or abbreviated keystrokes to arrive at a particular configuration screen. The decision was made to base all examples in this chapter on use of the Start button. -

    MS Windows XP Professional

    - +

    MS Windows XP Professional

    + There are two paths to the Windows XP TCP/IP configuration panel. Choose the access method that you prefer:

    Click Start -> Control Panel -> Network Connections. @@ -51,48 +51,48 @@ that are in common use today. These are: Alternately, click Start ->, and right-click My Network Places then select Properties.

    - + The following procedure steps through the Windows XP Professional TCP/IP configuration process:

    1. - - - + + + On some installations the interface will be called Local Area Connection and on others it will be called Network Bridge. On our system it is called Network Bridge. Right-click on Network Bridge -> Properties. See “Network Bridge Configuration.”.

      Figure 8.1. Network Bridge Configuration.

      Network Bridge Configuration.


    2. - - + + The Network Bridge Configuration, or Local Area Connection, panel is used to set TCP/IP protocol settings. In This connection uses the following items: box, click on Internet Protocol (TCP/IP), then click on Properties.

      - - + + The default setting is DHCP-enabled operation (i.e., “Obtain an IP address automatically”). See “Internet Protocol (TCP/IP) Properties.”.

      Figure 8.2. Internet Protocol (TCP/IP) Properties.

      Internet Protocol (TCP/IP) Properties.


      - - - - + + + + Many network administrators will want to use DHCP to configure all client TCP/IP protocol stack settings. (For information on how to configure the ISC DHCP server for Windows client support see the DNS and DHCP Configuration Guide, DHCP Server.

      - - - + + + If it is necessary to provide a fixed IP address, click on “Use the following IP address” and enter the IP Address, the subnet mask, and the default gateway address in the boxes provided.

    3. - - - - + + + + Click the Advanced button to proceed with TCP/IP configuration. This opens a panel in which it is possible to create additional IP addresses for this interface. The technical name for the additional addresses is IP aliases, and additionally this @@ -100,28 +100,28 @@ that are in common use today. These are: necessary to create additional settings. See “Advanced Network Settings” to see the appearance of this panel.

      Figure 8.3. Advanced Network Settings

      Advanced Network Settings


      - - - + + + Fixed settings may be required for DNS and WINS if these settings are not provided automatically via DHCP.

    4. - - + + Click the DNS tab to add DNS server settings. The example system uses manually configured DNS settings. When finished making changes, click the OK to commit the settings. See “DNS Configuration.”.

      Figure 8.4. DNS Configuration.

      DNS Configuration.


    5. - - + + Click the WINS tab to add manual WINS server entries. This step demonstrates an example system that uses manually configured WINS settings. When finished making changes, click OK to commit the settings. See “WINS Configuration”.

      Figure 8.5. WINS Configuration

      WINS Configuration


      -

    MS Windows 2000

    - - +

    MS Windows 2000

    + + There are two paths to the Windows 2000 Professional TCP/IP configuration panel. Choose the access method that you prefer:

    Click Start -> Control Panel -> Network and Dial-up Connections. @@ -129,33 +129,33 @@ that are in common use today. These are: Alternatively, click Start, then right-click My Network Places, and select Properties.

    - + The following procedure steps through the Windows XP Professional TCP/IP configuration process:

    1. Right-click on Local Area Connection, then click Properties. See “Local Area Connection Properties.”.

      Figure 8.6. Local Area Connection Properties.

      Local Area Connection Properties.


    2. - - + + The Local Area Connection Properties is used to set TCP/IP protocol settings. Click on Internet Protocol (TCP/IP) in the Components checked are used by this connection: box, then click the Properties button.

    3. - - + + The default setting is DHCP-enabled operation (i.e., “Obtain an IP address automatically”). See “Internet Protocol (TCP/IP) Properties.”.

      Figure 8.7. Internet Protocol (TCP/IP) Properties.

      Internet Protocol (TCP/IP) Properties.


      - - + + Many network administrators will want to use DHCP to configure all client TCP/IP protocol stack settings. (For information on how to configure the ISC DHCP server for Windows client support, see, “DHCP Server”.

      - - + + If it is necessary to provide a fixed IP address, click on “Use the following IP address” and enter the IP Address, the subnet mask, and the default gateway address in the boxes provided. For this example we are assuming that all network clients will be configured using DHCP. @@ -164,50 +164,50 @@ that are in common use today. These are: Refer to “Advanced Network Settings.”.

      Figure 8.8. Advanced Network Settings.

      Advanced Network Settings.


      - - - + + + Fixed settings may be required for DNS and WINS if these settings are not provided automatically via DHCP.

    4. - - + + Click the DNS tab to add DNS server settings. The example system uses manually configured DNS settings. When finished making changes, click OK to commit the settings. See “DNS Configuration.”.

      Figure 8.9. DNS Configuration.

      DNS Configuration.


    5. - - + + Click the WINS tab to add manual WINS server entries. This step demonstrates an example system that uses manually configured WINS settings. When finished making changes, click OK to commit the settings. See “WINS Configuration.”.

      Figure 8.10. WINS Configuration.

      WINS Configuration.


      -

    MS Windows Me

    - - - +

    MS Windows Me

    + + + There are two paths to the Windows Millennium edition (Me) TCP/IP configuration panel. Choose the access method that you prefer:

    Click Start -> Control Panel -> Network Connections.

    - - + + Alternatively, click on Start ->, and right click on My Network Places then select Properties.

    - + The following procedure steps through the Windows Me TCP/IP configuration process:

    1. - + In the box labeled The following network components are installed:, click on Internet Protocol TCP/IP, then click on the Properties button. See “The Windows Me Network Configuration Panel.”.

      Figure 8.11. The Windows Me Network Configuration Panel.

      The Windows Me Network Configuration Panel.


    2. - - - + + + Many network administrators will want to use DHCP to configure all client TCP/IP protocol stack settings. (For information on how to configure the ISC DHCP server for Windows client support see the DNS and DHCP Configuration Guide, @@ -215,41 +215,41 @@ that are in common use today. These are: (i.e., Obtain IP address automatically is enabled). See “IP Address.”.

      Figure 8.12. IP Address.

      IP Address.


      - - - + + + If it is necessary to provide a fixed IP address, click on Specify an IP address and enter the IP Address and the subnet mask in the boxes provided. For this example we are assuming that all network clients will be configured using DHCP.

    3. - - + + Fixed settings may be required for DNS and WINS if these settings are not provided automatically via DHCP.

    4. - + If necessary, click the DNS Configuration tab to add DNS server settings. Click the WINS Configuration tab to add WINS server settings. The Gateway tab allows additional gateways (router addresses) to be added to the network interface settings. In most cases where DHCP is used, it will not be necessary to create these manual settings.

    5. - - + + The following example uses manually configured WINS settings. See “DNS Configuration.”. When finished making changes, click OK to commit the settings.

      Figure 8.13. DNS Configuration.

      DNS Configuration.


      - - + + This is an example of a system that uses manually configured WINS settings. One situation where this might apply is on a network that has a single DHCP server that provides settings for multiple Windows workgroups or domains. See “WINS Configuration.”.

      Figure 8.14. WINS Configuration.

      WINS Configuration.


      -

    Joining a Domain: Windows 2000/XP Professional

    - - - - +

    Joining a Domain: Windows 2000/XP Professional

    + + + + Microsoft Windows NT/200x/XP Professional platforms can participate in domain security. This section steps through the process for making a Windows 200x/XP Professional machine a member of a domain security environment. It should be noted that this process is identical @@ -259,18 +259,18 @@ that are in common use today. These are:

  • Right-click My Computer, then select Properties.

  • - + The opening panel is the same one that can be reached by clicking System on the Control Panel. See “The General Panel.”.

    Figure 8.15. The General Panel.

    The General Panel.


  • - + Click the Computer Name tab. This panel shows the Computer Description, the Full computer name, and the Workgroup or Domain name.

    - - + + Clicking the Network ID button will launch the configuration wizard. Do not use this with Samba-3. If you wish to change the computer name or join or leave the domain, click the Change button. See “The Computer Name Panel.”. @@ -280,38 +280,38 @@ that are in common use today. These are: We will join the domain called MIDEARTH. See “The Computer Name Changes Panel.”.

    Figure 8.17. The Computer Name Changes Panel.

    The Computer Name Changes Panel.


  • - + Enter the name MIDEARTH in the field below the domain radio button.

    This panel shows that our example machine (TEMPTATION) is set to join the domain called MIDEARTH. See “The Computer Name Changes Panel Domain MIDEARTH.”.

    Figure 8.18. The Computer Name Changes Panel Domain MIDEARTH.

    The Computer Name Changes Panel Domain MIDEARTH.


  • - - + + Now click the OK button. A dialog box should appear to allow you to provide the credentials (username and password) of a domain administrative account that has the rights to add machines to the domain.

    - + Enter the name “root” and the root password from your Samba-3 server. See “Computer Name Changes Username and Password Panel.”.

    Figure 8.19. Computer Name Changes Username and Password Panel.

    Computer Name Changes Username and Password Panel.


  • Click on OK.

    - - + + The “Welcome to the MIDEARTH domain.” dialog box should appear. At this point the machine must be rebooted. Joining the domain is now complete. -

    • Domain Logon Configuration: Windows 9x/Me

    - - - +

    Domain Logon Configuration: Windows 9x/Me

    + + + We follow the convention used by most in saying that Windows 9x/Me machines can participate in domain logons. The truth is that these platforms can use only the LanManager network logon protocols.

    Note

    - - - + + + Windows XP Home edition cannot participate in domain or LanManager network logons.

    1. Right-click on the Network Neighborhood icon. @@ -320,44 +320,44 @@ that are in common use today. These are: See “The Network Panel.”.

      Figure 8.20. The Network Panel.

      The Network Panel.


      - - + + Make sure that the Client for Microsoft Networks driver is installed as shown. Click on the Client for Microsoft Networks entry in The following network components are installed: box. Then click the Properties button.

    2. - - + + The Client for Microsoft Networks Properties panel is the correct location to configure network logon settings. See “Client for Microsoft Networks Properties Panel.”.

      Figure 8.21. Client for Microsoft Networks Properties Panel.

      Client for Microsoft Networks Properties Panel.


      - - + + Enter the Windows NT domain name, check the Log on to Windows NT domain box, and click OK.

    3. - - - + + + Click on the Identification button. This is the location at which the workgroup (domain) name and the machine name (computer name) need to be set. See “Identification Panel.”.

      Figure 8.22. Identification Panel.

      Identification Panel.


    4. - - - - + + + + Now click the Access Control button. If you want to be able to assign share access permissions using domain user and group accounts, it is necessary to enable User-level access control as shown in this panel. See “Access Control Panel.”.

      Figure 8.23. Access Control Panel.

      Access Control Panel.


      -

    Common Errors

    - - +

    Common Errors

    + + The most common errors that can afflict Windows networking systems include:

    • Incorrect IP address.

    • Incorrect or inconsistent netmasks.

    • Incorrect router address.

    • Incorrect DNS server address.

    • Incorrect WINS server address.

    • Use of a Network Scope setting watch out for this one!

    - - + + The most common reasons for which a Windows NT/200x/XP Professional client cannot join the Samba controlled domain are:

    • smb.conf does not have correct add machine script settings.

    • “root” account is not in password backend database.

    • Attempt to use a user account instead of the “root” account to join a machine to the domain.

    • Open connections from the workstation to the server.

    • Firewall or filter configurations in place on either the client or the Samba server.

    Prev Up Next
    Chapter 7. Standalone Servers Home Part III. Advanced Configuration
    diff --git a/docs/htmldocs/Samba3-HOWTO/DNSDHCP.html b/docs/htmldocs/Samba3-HOWTO/DNSDHCP.html index 3cbc3a59b0..3529030efd 100644 --- a/docs/htmldocs/Samba3-HOWTO/DNSDHCP.html +++ b/docs/htmldocs/Samba3-HOWTO/DNSDHCP.html @@ -1,6 +1,6 @@ -Chapter 47. DNS and DHCP Configuration Guide
    Chapter 47. DNS and DHCP Configuration Guide
    Prev Part VI. Reference Section Next

    Chapter 47. DNS and DHCP Configuration Guide

    John H. Terpstra

    Samba Team

    Table of Contents

    Features and Benefits
    Example Configuration
    Dynamic DNS
    DHCP Server

    Features and Benefits

    - - +Chapter 48. DNS and DHCP Configuration Guide

    Chapter 48. DNS and DHCP Configuration Guide
    Prev Part VI. Reference Section Next

    Chapter 48. DNS and DHCP Configuration Guide

    John H. Terpstra

    Samba Team

    Table of Contents

    Features and Benefits
    Example Configuration
    Dynamic DNS
    DHCP Server

    Features and Benefits

    + + There are few subjects in the UNIX world that might raise as much contention as Domain Name System (DNS) and Dynamic Host Configuration Protocol (DHCP). Not all opinions held for or against particular implementations of DNS and DHCP @@ -10,16 +10,16 @@ We live in a modern age where many information technology users demand mobility and freedom. Microsoft Windows users in particular expect to be able to plug their notebook computer into a network port and have things “just work.”

    - + UNIX administrators have a point. Many of the normative practices in the Microsoft Windows world at best border on bad practice from a security perspective. Microsoft Windows networking protocols allow workstations to arbitrarily register themselves on a network. Windows 2000 Active Directory registers entries in the DNS namespace that are equally perplexing to UNIX administrators. Welcome to the new world!

    - - - + + + The purpose of this chapter is to demonstrate the configuration of the Internet Software Consortium (ISC) DNS and DHCP servers to provide dynamic services that are compatible with their equivalents in the Microsoft Windows 2000 Server products. @@ -27,26 +27,26 @@ compatible with their equivalents in the Microsoft Windows 2000 Server products. This chapter provides no more than a working example of configuration files for both DNS and DHCP servers. The examples used match configuration examples used elsewhere in this document.

    - - - + + + This chapter explicitly does not provide a tutorial, nor does it pretend to be a reference guide on DNS and DHCP, as this is well beyond the scope and intent of this document as a whole. Anyone who wants more detailed reference materials on DNS or DHCP should visit the ISC Web site at http://www.isc.org. Those wanting a written text might also be interested in the O'Reilly publications on DNS, see the O'Reilly web site, and the BIND9.NET web site for details. The books are: -

    1. DNS and BIND, By Cricket Liu, Paul Albitz, ISBN: 1-56592-010-4

    2. DNS & Bind Cookbook, By Cricket Liu, ISBN: 0-596-00410-9

    3. The DHCP Handbook (2nd Edition), By: Ralph Droms, Ted Lemon, ISBN 0-672-32327-3

    Example Configuration

    - - +

    1. DNS and BIND, By Cricket Liu, Paul Albitz, ISBN: 1-56592-010-4

    2. DNS & Bind Cookbook, By Cricket Liu, ISBN: 0-596-00410-9

    3. The DHCP Handbook (2nd Edition), By: Ralph Droms, Ted Lemon, ISBN 0-672-32327-3

    Example Configuration

    + + The DNS is to the Internet what water is to life. Nearly all information resources (host names) are resolved to their Internet protocol (IP) addresses through DNS. Windows networking tried hard to avoid the -complexities of DNS, but alas, DNS won. The alternative to +complexities of DNS, but alas, DNS won. The alternative to DNS, the Windows Internet Name Service (WINS) an artifact of NetBIOS networking over the TCP/IP protocols has demonstrated scalability problems as well as a flat, nonhierarchical namespace that became unmanageable as the size and complexity of information technology networks grew.

    - - + + WINS is a Microsoft implementation of the RFC1001/1002 NetBIOS Name Service (NBNS). It allows NetBIOS clients (like Microsoft Windows machines) to register an arbitrary machine name that the administrator or user has chosen together with the IP @@ -66,13 +66,13 @@ hostnames via Microsoft WINS.

    The following configurations demonstrate a simple, insecure dynamic DNS server and a simple DHCP server that matches the DNS configuration. -

    Dynamic DNS

    - +

    Dynamic DNS

    + The example DNS configuration is for a private network in the IP address space for network 192.168.1.0/24. The private class network address space is set forth in RFC1918.

    - + It is assumed that this network will be situated behind a secure firewall. The files that follow work with ISC BIND version 9. BIND is the Berkeley Internet Name Daemon. @@ -223,8 +223,8 @@ $ORIGIN 1.168.192.in-addr.arpa. 2 PTR marvel.quenya.org.

    - - + + The configuration files shown here were copied from a fully working system. All dynamically registered entries have been removed. In addition to these files, BIND version 9 will create for each of the dynamic registration files a file that has a @@ -260,6 +260,6 @@ subnet 192.168.1.0 netmask 255.255.255.0 { In this example, IP addresses between 192.168.1.1 and 192.168.1.59 are reserved for fixed-address (commonly called hard-wired) IP addresses. The addresses between 192.168.1.60 and 192.168.1.254 are allocated for dynamic use. -

    Prev Up Next
    Chapter 46. Samba Support Home Appendix A.  +

    Prev Up Next
    Chapter 47. Samba Support Home Appendix A.  GNU General Public License version 3
    diff --git a/docs/htmldocs/Samba3-HOWTO/FastStart.html b/docs/htmldocs/Samba3-HOWTO/FastStart.html index 6f29f4609e..51fdc5a8f8 100644 --- a/docs/htmldocs/Samba3-HOWTO/FastStart.html +++ b/docs/htmldocs/Samba3-HOWTO/FastStart.html @@ -1,4 +1,4 @@ -Chapter 2. Fast Start: Cure for Impatience
    Chapter 2. Fast Start: Cure for Impatience
    Prev Part I. General Installation Next

    Chapter 2. Fast Start: Cure for Impatience

    John H. Terpstra

    Samba Team

    Table of Contents

    Features and Benefits
    Description of Example Sites
    Worked Examples
    Standalone Server
    Domain Member Server
    Domain Controller

    +Chapter 2. Fast Start: Cure for Impatience

    Chapter 2. Fast Start: Cure for Impatience
    Prev Part I. General Installation Next

    Chapter 2. Fast Start: Cure for Impatience

    John H. Terpstra

    Samba Team

    Table of Contents

    Features and Benefits
    Description of Example Sites
    Worked Examples
    Standalone Server
    Domain Member Server
    Domain Controller

    When we first asked for suggestions for inclusion in the Samba HOWTO documentation, someone wrote asking for example configurations and lots of them. That is remarkably difficult to do without losing a lot of value that can be derived from presenting @@ -22,7 +22,7 @@ as the equivalent of an auto mechanic's repair guide. The book “Samba-3 by Example. -

    Features and Benefits

    +

    Features and Benefits

    Samba needs very little configuration to create a basic working system. In this chapter we progress from the simple to the complex, for each providing all steps and configuration file changes needed to make each work. Please note @@ -32,7 +32,7 @@ features. These additional features are covered in the remainder of this documen The examples used here have been obtained from a number of people who made requests for example configurations. All identities have been obscured to protect the guilty, and any resemblance to unreal nonexistent sites is deliberate. -

    Description of Example Sites

    +

    Description of Example Sites

    In the first set of configuration examples we consider the case of exceptionally simple system requirements. There is a real temptation to make something that should require little effort much too complex.

    @@ -53,15 +53,15 @@ network-attached storage (NAS) device and a print server. The later example consider more complex systems that will either integrate into existing MS Windows networks or replace them entirely. These cover domain member servers as well as Samba domain control (PDC/BDC) and finally describes in detail a large distributed network with branch offices in remote locations. -

    Worked Examples

    +

    Worked Examples

    The configuration examples are designed to cover everything necessary to get Samba running. They do not cover basic operating system platform configuration, which is clearly beyond the scope of this text.

    It is also assumed that Samba has been correctly installed, either by way of installation of the packages that are provided by the operating system vendor or through other means. -

    Standalone Server

    - +

    Standalone Server

    + A standalone server implies no more than the fact that it is not a domain controller and it does not participate in domain control. It can be a simple, workgroup-like server, or it can be a complex server that is a member of a domain security context. @@ -69,7 +69,7 @@ of the packages that are provided by the operating system vendor or through othe As the examples are developed, every attempt is made to progress the system toward greater capability, just as one might expect would happen in a real business office as that office grows in size and its needs change.

    Anonymous Read-Only Document Server

    - + The purpose of this type of server is to make available to any user any documents or files that are placed on the shared resource. The shared resource could be a CD-ROM drive, a CD-ROM image, or a file @@ -82,7 +82,7 @@ of the packages that are provided by the operating system vendor or through othe m0r3pa1n of course, that's just the example we are using; do not use this in a production environment because all readers of this document will know it. -

    Procedure 2.1. Installation Procedure: Read-Only Server

    Example 2.1. Anonymous Read-Only Server Configuration

    # Global parameters
    [global]
    workgroup = MIDEARTH
    netbios name = HOBBIT
    security = share
    [data]
    comment = Data
    path = /export
    read only = Yes
    guest ok = Yes

    1. +

    Procedure 2.1. Installation Procedure: Read-Only Server

    Example 2.1. Anonymous Read-Only Server Configuration

    # Global parameters
    [global]
    workgroup = MIDEARTH
    netbios name = HOBBIT
    security = share
    [data]
    comment = Data
    path = /export
    read only = Yes
    guest ok = Yes

    1. Add user to system (with creation of the user's home directory): 

       root# useradd -c "Jack Baumbach" -m -g users -p m0r3pa1n jackb
@@ -151,8 +151,8 @@ Press enter to see a dump of your service definitions

    The information above (following # Global parameters) provides the complete contents of the /etc/samba/smb.conf file. -

    Anonymous Read-Write Document Server

    - +

    Anonymous Read-Write Document Server

    + We should view this configuration as a progression from the previous example. The difference is that shared access is now forced to the user identity of jackb and to the primary group jackb belongs to. One other refinement we can make is to @@ -169,8 +169,8 @@ Added user jackb. instead of to User Unknown.

    The complete, modified smb.conf file is as shown in “Modified Anonymous Read-Write smb.conf”. -

    Example 2.2. Modified Anonymous Read-Write smb.conf

    # Global parameters
    [global]
    workgroup = MIDEARTH
    netbios name = HOBBIT
    security = SHARE
    [data]
    comment = Data
    path = /export
    force user = jackb
    force group = users
    read only = No
    guest ok = Yes

    Anonymous Print Server

    - +

    Example 2.2. Modified Anonymous Read-Write smb.conf

    # Global parameters
    [global]
    workgroup = MIDEARTH
    netbios name = HOBBIT
    security = SHARE
    [data]
    comment = Data
    path = /export
    force user = jackb
    force group = users
    read only = No
    guest ok = Yes

    Anonymous Print Server

    + An anonymous print server serves two purposes:

    • It allows printing to all printers from a single location. @@ -187,7 +187,7 @@ Added user jackb. In this configuration, it is undesirable to present the Add Printer Wizard, and we do not want to have automatic driver download, so we disable it in the following configuration. “Anonymous Print Server smb.conf” is the resulting smb.conf file. -

      Example 2.3. Anonymous Print Server smb.conf

      # Global parameters
      [global]
      workgroup = MIDEARTH
      netbios name = LUTHIEN
      security = share
      printcap name = cups
      disable spoolss = Yes
      show add printer wizard = No
      printing = cups
      [printers]
      comment = All Printers
      path = /var/spool/samba
      guest ok = Yes
      printable = Yes
      use client driver = Yes
      browseable = No

      +

      Example 2.3. Anonymous Print Server smb.conf

      # Global parameters
      [global]
      workgroup = MIDEARTH
      netbios name = LUTHIEN
      security = share
      printcap name = cups
      disable spoolss = Yes
      show add printer wizard = No
      printing = cups
      [printers]
      comment = All Printers
      path = /var/spool/samba
      guest ok = Yes
      printable = Yes
      use client driver = Yes
      browseable = No

      The above configuration is not ideal. It uses no smart features, and it deliberately presents a less than elegant solution. But it is basic, and it does print. Samba makes use of the direct printing application program interface that is provided by CUPS. @@ -220,14 +220,14 @@ Added user jackb. The purpose of setting the sticky bit is to prevent who does not own the temporary print file from being able to take control of it with the potential for devious misuse.

    Note

    - - + + On CUPS-enabled systems there is a facility to pass raw data directly to the printer without intermediate processing via CUPS print filters. Where use of this mode of operation is desired, it is necessary to configure a raw printing device. It is also necessary to enable the raw mime handler in the /etc/mime.conv and /etc/mime.types files. Refer to “Explicitly Enable raw Printing for application/octet-stream”. -

    Secure Read-Write File and Print Server

    +

    Secure Read-Write File and Print Server

    We progress now from simple systems to a server that is slightly more complex.

    Our new server will require a public data storage area in which only authenticated @@ -250,8 +250,8 @@ Added user jackb. it is not necessary to enter it into the configuration file. Note that the guest backend is added to the list of active passdb backends no matter whether it specified directly in Samba configuration file or not. -

    Procedure 2.2. Installing the Secure Office Server

    Example 2.4. Secure Office Server smb.conf

    # Global parameters
    [global]
    workgroup = MIDEARTH
    netbios name = OLORIN
    printcap name = cups
    disable spoolss = Yes
    show add printer wizard = No
    printing = cups
    [homes]
    comment = Home Directories
    valid users = %S
    read only = No
    browseable = No
    [public]
    comment = Data
    path = /export
    force user = maryo
    force group = users
    read only = No
    [printers]
    comment = All Printers
    path = /var/spool/samba
    printer admin = root, maryo
    create mask = 0600
    guest ok = Yes
    printable = Yes
    use client driver = Yes
    browseable = No

    1. - +

      Procedure 2.2. Installing the Secure Office Server

      Example 2.4. Secure Office Server smb.conf

      # Global parameters
      [global]
      workgroup = MIDEARTH
      netbios name = OLORIN
      printcap name = cups
      disable spoolss = Yes
      show add printer wizard = No
      printing = cups
      [homes]
      comment = Home Directories
      valid users = %S
      read only = No
      browseable = No
      [public]
      comment = Data
      path = /export
      force user = maryo
      force group = users
      read only = No
      [printers]
      comment = All Printers
      path = /var/spool/samba
      printer admin = root, maryo
      create mask = 0600
      guest ok = Yes
      printable = Yes
      use client driver = Yes
      browseable = No

      1. + Add all users to the operating system: 

         root# useradd -c "Jack Baumbach" -m -g users -p m0r3pa1n jackb
@@ -290,10 +290,10 @@ Added user ameds.

      2. Start Samba using the operating system administrative interface. Alternately, this can be done manually by executing: - - - - + + + + 

         root#  nmbd; smbd;

        @@ -358,8 +358,8 @@ smb: \> q By now you should be getting the hang of configuration basics. Clearly, it is time to explore slightly more complex examples. For the remainder of this chapter we abbreviate instructions, since there are previous examples. -

    Domain Member Server

    - +

    Domain Member Server

    + In this instance we consider the simplest server configuration we can get away with to make an accounting department happy. Let's be warned, the users are accountants and they do have some nasty demands. There is a budget for only one server for this department. @@ -390,11 +390,11 @@ smb: \> q file area for each member of her team that is private to that person, but she wants full access to all areas. Users must have a private home share for personal work-related files and for materials not related to departmental operations. -

    Example Configuration

    +

    Example Configuration

    The server valinor will be a member server of the company domain. Accounting will have only a local server. User accounts will be on the domain controllers, as will desktop profiles and all network policy files. -

    Example 2.5. Member Server smb.conf (Globals)

    # Global parameters
    [global]
    workgroup = MIDEARTH
    netbios name = VALINOR
    security = DOMAIN
    printcap name = cups
    disable spoolss = Yes
    show add printer wizard = No
    idmap uid = 15000-20000
    idmap gid = 15000-20000
    winbind use default domain = Yes
    printing = cups

    Example 2.6. Member Server smb.conf (Shares and Services)

    [homes]
    comment = Home Directories
    valid users = %S
    read only = No
    browseable = No
    [spytfull]
    comment = Accounting Application Only
    path = /export/spytfull
    valid users = @Accounts
    admin users = maryo
    read only = Yes
    [public]
    comment = Data
    path = /export/public
    read only = No
    [printers]
    comment = All Printers
    path = /var/spool/samba
    printer admin = root, maryo
    create mask = 0600
    guest ok = Yes
    printable = Yes
    use client driver = Yes
    browseable = No

    1. +

      Example 2.5. Member Server smb.conf (Globals)

      # Global parameters
      [global]
      workgroup = MIDEARTH
      netbios name = VALINOR
      security = DOMAIN
      printcap name = cups
      disable spoolss = Yes
      show add printer wizard = No
      idmap uid = 15000-20000
      idmap gid = 15000-20000
      winbind use default domain = Yes
      printing = cups

      Example 2.6. Member Server smb.conf (Shares and Services)

      [homes]
      comment = Home Directories
      valid users = %S
      read only = No
      browseable = No
      [spytfull]
      comment = Accounting Application Only
      path = /export/spytfull
      valid users = @Accounts
      admin users = maryo
      read only = Yes
      [public]
      comment = Data
      path = /export/public
      read only = No
      [printers]
      comment = All Printers
      path = /var/spool/samba
      printer admin = root, maryo
      create mask = 0600
      guest ok = Yes
      printable = Yes
      use client driver = Yes
      browseable = No

      1. Do not add users to the UNIX/Linux server; all of this will run off the central domain.

      2. @@ -402,7 +402,7 @@ smb: \> q (globals) and Member server smb.conf (shares and services).

      3. - + Join the domain. Note: Do not start Samba until this step has been completed! 

         root# net rpc join -Uroot%'bigsecret'
@@ -414,12 +414,12 @@ Joined domain MIDEARTH.

      4. Start Samba following the normal method for your operating system platform. If you wish to do this manually, execute as root: - - - - - - + + + + + + 

         root# nmbd; smbd; winbindd;

        @@ -480,8 +480,8 @@ maryo:x:15000:15003:Mary Orville:/home/MIDEARTH/maryo:/bin/false root# chmod ug=rwxS,o=x /export/{spytfull,public} root# chown maryo.Accounts /export/{spytfull,public}

        -

    Domain Controller

    - +

    Domain Controller

    + For the remainder of this chapter the focus is on the configuration of domain control. The examples that follow are for two implementation strategies. Remember, our objective is to create a simple but working solution. The remainder of this book should help to highlight @@ -515,17 +515,17 @@ maryo:x:15000:15003:Mary Orville:/home/MIDEARTH/maryo:/bin/false in Samba-3 for Security Account Manager database [SAM] replication).

    Note

    If you need more than one domain controller, do not use a tdbsam authentication backend. -

    Example: Engineering Office

    +

    Example: Engineering Office

    The engineering office network server we present here is designed to demonstrate use of the new tdbsam password backend. The tdbsam facility is new to Samba-3. It is designed to provide many user and machine account controls that are possible with Microsoft Windows NT4. It is safe to use this in smaller networks. -

    Example 2.7. Engineering Office smb.conf (globals)

    [global]
    workgroup = MIDEARTH
    netbios name = FRODO
    passdb backend = tdbsam
    printcap name = cups
    add user script = /usr/sbin/useradd -m %u
    delete user script = /usr/sbin/userdel -r %u
    add group script = /usr/sbin/groupadd %g
    delete group script = /usr/sbin/groupdel %g
    add user to group script = /usr/sbin/groupmod -A %u %g
    delete user from group script = /usr/sbin/groupmod -R %u %g
    add machine script = /usr/sbin/useradd -s /bin/false -d /var/lib/nobody %u
    # Note: The following specifies the default logon script.
    # Per user logon scripts can be specified in the user account using pdbedit
    logon script = scripts\logon.bat
    # This sets the default profile path. Set per user paths with pdbedit
    logon path = \\%L\Profiles\%U
    logon drive = H:
    logon home = \\%L\%U
    domain logons = Yes
    os level = 35
    preferred master = Yes
    domain master = Yes
    idmap uid = 15000-20000
    idmap gid = 15000-20000
    printing = cups

    Example 2.8. Engineering Office smb.conf (shares and services)

    [homes]
    comment = Home Directories
    valid users = %S
    read only = No
    browseable = No
    # Printing auto-share (makes printers available thru CUPS)
    [printers]
    comment = All Printers
    path = /var/spool/samba
    printer admin = root, maryo
    create mask = 0600
    guest ok = Yes
    printable = Yes
    browseable = No
    [print$]
    comment = Printer Drivers Share
    path = /var/lib/samba/drivers
    write list = maryo, root
    printer admin = maryo, root
    # Needed to support domain logons
    [netlogon]
    comment = Network Logon Service
    path = /var/lib/samba/netlogon
    admin users = root, maryo
    guest ok = Yes
    browseable = No
    # For profiles to work, create a user directory under the path
    # shown. i.e., mkdir -p /var/lib/samba/profiles/maryo
    [Profiles]
    comment = Roaming Profile Share
    path = /var/lib/samba/profiles
    read only = No
    profile acls = Yes
    # Other resource (share/printer) definitions would follow below.

    1. +

      Example 2.7. Engineering Office smb.conf (globals)

      [global]
      workgroup = MIDEARTH
      netbios name = FRODO
      passdb backend = tdbsam
      printcap name = cups
      add user script = /usr/sbin/useradd -m %u
      delete user script = /usr/sbin/userdel -r %u
      add group script = /usr/sbin/groupadd %g
      delete group script = /usr/sbin/groupdel %g
      add user to group script = /usr/sbin/groupmod -A %u %g
      delete user from group script = /usr/sbin/groupmod -R %u %g
      add machine script = /usr/sbin/useradd -s /bin/false -d /var/lib/nobody %u
      # Note: The following specifies the default logon script.
      # Per user logon scripts can be specified in the user account using pdbedit
      logon script = scripts\logon.bat
      # This sets the default profile path. Set per user paths with pdbedit
      logon path = \\%L\Profiles\%U
      logon drive = H:
      logon home = \\%L\%U
      domain logons = Yes
      os level = 35
      preferred master = Yes
      domain master = Yes
      idmap uid = 15000-20000
      idmap gid = 15000-20000
      printing = cups

      Example 2.8. Engineering Office smb.conf (shares and services)

      [homes]
      comment = Home Directories
      valid users = %S
      read only = No
      browseable = No
      # Printing auto-share (makes printers available thru CUPS)
      [printers]
      comment = All Printers
      path = /var/spool/samba
      printer admin = root, maryo
      create mask = 0600
      guest ok = Yes
      printable = Yes
      browseable = No
      [print$]
      comment = Printer Drivers Share
      path = /var/lib/samba/drivers
      write list = maryo, root
      printer admin = maryo, root
      # Needed to support domain logons
      [netlogon]
      comment = Network Logon Service
      path = /var/lib/samba/netlogon
      admin users = root, maryo
      guest ok = Yes
      browseable = No
      # For profiles to work, create a user directory under the path
      # shown. i.e., mkdir -p /var/lib/samba/profiles/maryo
      [Profiles]
      comment = Roaming Profile Share
      path = /var/lib/samba/profiles
      read only = No
      profile acls = Yes
      # Other resource (share/printer) definitions would follow below.

      1. A working PDC configuration using the tdbsam password backend can be found in Engineering Office smb.conf (globals) together with Engineering Office smb.conf (shares and services): - +

      2. Create UNIX group accounts as needed using a suitable operating system tool: 

        @@ -541,8 +541,8 @@ maryo:x:15000:15003:Mary Orville:/home/MIDEARTH/maryo:/bin/false
 			on files, directories, printers, and as required for use in the Samba
 			environment.

      3. - - + + Assign each of the UNIX groups to NT groups by executing this shell script (You could name the script initGroups.sh): 

        @@ -570,13 +570,13 @@ net groupmap add ntgroup="QA Team"   unixgroup=qateam    type=d

      The above configuration provides a functional PDC system to which must be added file shares and printers as required. -

    A Big Organization

    +

    A Big Organization

    In this section we finally get to review in brief a Samba-3 configuration that uses a Lightweight Directory Access (LDAP)-based authentication backend. The main reasons for this choice are to provide the ability to host primary and Backup Domain Control (BDC), as well as to enable a higher degree of scalability to meet the needs of a very distributed environment. -

    The Primary Domain Controller

    +

    The Primary Domain Controller

    This is an example of a minimal configuration to run a Samba-3 PDC using an LDAP authentication backend. It is assumed that the operating system has been correctly configured. @@ -587,13 +587,13 @@ net groupmap add ntgroup="QA Team" unixgroup=qateam type=d distributions tend to install the Idealx scripts in the /usr/share/doc/packages/sambaXXXXXX/examples/LDAP/smbldap-tools directory. Idealx scripts version smbldap-tools-0.9.1 are known to work well. -

    Example 2.9. LDAP backend smb.conf for PDC

    # Global parameters
    [global]
    workgroup = MIDEARTH
    netbios name = FRODO
    passdb backend = ldapsam:ldap://localhost
    username map = /etc/samba/smbusers
    printcap name = cups
    add user script = /usr/local/sbin/smbldap-useradd -m '%u'
    delete user script = /usr/local/sbin/smbldap-userdel %u
    add group script = /usr/local/sbin/smbldap-groupadd -p '%g'
    delete group script = /usr/local/sbin/smbldap-groupdel '%g'
    add user to group script = /usr/local/sbin/smbldap-groupmod -m '%u' '%g'
    delete user from group script = /usr/local/sbin/smbldap-groupmod -x '%u' '%g'
    set primary group script = /usr/local/sbin/smbldap-usermod -g '%g' '%u'
    add machine script = /usr/local/sbin/smbldap-useradd -w '%u'
    logon script = scripts\logon.bat
    logon path = \\%L\Profiles\%U
    logon drive = H:
    logon home = \\%L\%U
    domain logons = Yes
    os level = 35
    preferred master = Yes
    domain master = Yes
    ldap suffix = dc=quenya,dc=org
    ldap machine suffix = ou=People
    ldap user suffix = ou=People
    ldap group suffix = ou=People
    ldap idmap suffix = ou=People
    ldap admin dn = cn=Manager
    ldap ssl = no
    ldap passwd sync = Yes
    idmap uid = 15000-20000
    idmap gid = 15000-20000
    printing = cups

    1. +

      Example 2.9. LDAP backend smb.conf for PDC

      # Global parameters
      [global]
      workgroup = MIDEARTH
      netbios name = FRODO
      passdb backend = ldapsam:ldap://localhost
      username map = /etc/samba/smbusers
      printcap name = cups
      add user script = /usr/local/sbin/smbldap-useradd -m '%u'
      delete user script = /usr/local/sbin/smbldap-userdel %u
      add group script = /usr/local/sbin/smbldap-groupadd -p '%g'
      delete group script = /usr/local/sbin/smbldap-groupdel '%g'
      add user to group script = /usr/local/sbin/smbldap-groupmod -m '%u' '%g'
      delete user from group script = /usr/local/sbin/smbldap-groupmod -x '%u' '%g'
      set primary group script = /usr/local/sbin/smbldap-usermod -g '%g' '%u'
      add machine script = /usr/local/sbin/smbldap-useradd -w '%u'
      logon script = scripts\logon.bat
      logon path = \\%L\Profiles\%U
      logon drive = H:
      logon home = \\%L\%U
      domain logons = Yes
      os level = 35
      preferred master = Yes
      domain master = Yes
      ldap suffix = dc=quenya,dc=org
      ldap machine suffix = ou=People
      ldap user suffix = ou=People
      ldap group suffix = ou=People
      ldap idmap suffix = ou=People
      ldap admin dn = cn=Manager
      ldap ssl = no
      ldap passwd sync = Yes
      idmap uid = 15000-20000
      idmap gid = 15000-20000
      printing = cups

      1. Obtain from the Samba sources ~/examples/LDAP/samba.schema and copy it to the /etc/openldap/schema/ directory.

      2. Set up the LDAP server. This example is suitable for OpenLDAP 2.1.x. The /etc/openldap/slapd.conf file. - + <title>Example slapd.conf File</title> 

         # Note commented out lines have been removed
@@ -629,7 +629,7 @@ index   default               sub

      3. Create the following file initdb.ldif: - + 

         # Organization for SambaXP Demo
 dn: dc=quenya,dc=org
@@ -684,11 +684,11 @@ userPassword: {SSHA}0jBHgQ1vp4EDX2rEMMfIudvRMJoGwjVb
 				Add users and groups as required. Users and groups added using Samba tools
 				will automatically be added to both the LDAP backend and the operating
 				system as required.
-
    Backup Domain Controller

    +

    Backup Domain Controller

    “Remote LDAP BDC smb.conf” shows the example configuration for the BDC. Note that the smb.conf file does not specify the smbldap-tools scripts they are not needed on a BDC. Add additional stanzas for shares and printers as required. -

    Example 2.10. Remote LDAP BDC smb.conf

    # Global parameters
    [global]
    workgroup = MIDEARTH
    netbios name = GANDALF
    passdb backend = ldapsam:ldap://frodo.quenya.org
    username map = /etc/samba/smbusers
    printcap name = cups
    logon script = scripts\logon.bat
    logon path = \\%L\Profiles\%U
    logon drive = H:
    logon home = \\%L\%U
    domain logons = Yes
    os level = 33
    preferred master = Yes
    domain master = No
    ldap suffix = dc=quenya,dc=org
    ldap machine suffix = ou=People
    ldap user suffix = ou=People
    ldap group suffix = ou=People
    ldap idmap suffix = ou=People
    ldap admin dn = cn=Manager
    ldap ssl = no
    ldap passwd sync = Yes
    idmap uid = 15000-20000
    idmap gid = 15000-20000
    printing = cups

    1. +

      Example 2.10. Remote LDAP BDC smb.conf

      # Global parameters
      [global]
      workgroup = MIDEARTH
      netbios name = GANDALF
      passdb backend = ldapsam:ldap://frodo.quenya.org
      username map = /etc/samba/smbusers
      printcap name = cups
      logon script = scripts\logon.bat
      logon path = \\%L\Profiles\%U
      logon drive = H:
      logon home = \\%L\%U
      domain logons = Yes
      os level = 33
      preferred master = Yes
      domain master = No
      ldap suffix = dc=quenya,dc=org
      ldap machine suffix = ou=People
      ldap user suffix = ou=People
      ldap group suffix = ou=People
      ldap idmap suffix = ou=People
      ldap admin dn = cn=Manager
      ldap ssl = no
      ldap passwd sync = Yes
      idmap uid = 15000-20000
      idmap gid = 15000-20000
      printing = cups

      1. Decide if the BDC should have its own LDAP server or not. If the BDC is to be the LDAP server, change the following smb.conf as indicated. The default configuration in Remote LDAP BDC smb.conf diff --git a/docs/htmldocs/Samba3-HOWTO/InterdomainTrusts.html b/docs/htmldocs/Samba3-HOWTO/InterdomainTrusts.html index 1ebd0fd782..eb7eb3d568 100644 --- a/docs/htmldocs/Samba3-HOWTO/InterdomainTrusts.html +++ b/docs/htmldocs/Samba3-HOWTO/InterdomainTrusts.html @@ -1,13 +1,13 @@ -Chapter 19. Interdomain Trust Relationships

        Chapter 19. Interdomain Trust Relationships
        Prev Part III. Advanced Configuration Next

        Chapter 19. Interdomain Trust Relationships

        John H. Terpstra

        Samba Team

        Rafal Szczesniak

        Samba Team

        Jelmer R. Vernooij

        drawing 
        The Samba Team

        Stephen Langasek

        April 3, 2003

        Table of Contents

        Features and Benefits
        Trust Relationship Background
        Native MS Windows NT4 Trusts Configuration
        Creating an NT4 Domain Trust
        Completing an NT4 Domain Trust
        Interdomain Trust Facilities
        Configuring Samba NT-Style Domain Trusts
        Samba as the Trusted Domain
        Samba as the Trusting Domain
        NT4-Style Domain Trusts with Windows 2000
        Common Errors
        Browsing of Trusted Domain Fails
        Problems with LDAP ldapsam and Older Versions of smbldap-tools

        - - - - - - - - - +Chapter 19. Interdomain Trust Relationships

        Chapter 19. Interdomain Trust Relationships
        Prev Part III. Advanced Configuration Next

        Chapter 19. Interdomain Trust Relationships

        John H. Terpstra

        Samba Team

        Rafal Szczesniak

        Samba Team

        Jelmer R. Vernooij

        drawing 
        The Samba Team

        Stephen Langasek

        April 3, 2003

        Table of Contents

        Features and Benefits
        Trust Relationship Background
        Native MS Windows NT4 Trusts Configuration
        Creating an NT4 Domain Trust
        Completing an NT4 Domain Trust
        Interdomain Trust Facilities
        Configuring Samba NT-Style Domain Trusts
        Samba as the Trusted Domain
        Samba as the Trusting Domain
        NT4-Style Domain Trusts with Windows 2000
        Common Errors
        Browsing of Trusted Domain Fails
        Problems with LDAP ldapsam and Older Versions of smbldap-tools

        + + + + + + + + + Samba-3 supports NT4-style domain trust relationships. This is a feature that many sites will want to use if they migrate to Samba-3 from an NT4-style domain and do not want to adopt Active Directory or an LDAP-based authentication backend. This chapter explains @@ -15,78 +15,78 @@ some background information regarding trust relationships and how to create them possible for Samba-3 to trust NT4 (and vice versa), as well as to create Samba-to-Samba trusts.

        - - - - - + + + + + The use of interdomain trusts requires use of winbind, so the winbindd daemon must be running. Winbind operation in this mode is dependent on the specification of a valid UID range and a valid GID range in the smb.conf file. These are specified respectively using: -

        idmap uid = 10000-20000
        idmap gid = 10000-20000

        - - - - +

        idmap uid = 10000-20000
        idmap gid = 10000-20000

        + + + + The range of values specified must not overlap values used by the host operating system and must not overlap values used in the passdb backend for POSIX user accounts. The maximum value is limited by the upper-most value permitted by the host operating system. This is a UNIX kernel limited parameter. Linux kernel 2.6-based systems support a maximum value of 4294967295 (32-bit unsigned variable).

        Note

        - - - + + + The use of winbind is necessary only when Samba is the trusting domain, not when it is the trusted domain. -

        Features and Benefits

        - - +

        Features and Benefits

        + + Samba-3 can participate in Samba-to-Samba as well as in Samba-to-MS Windows NT4-style trust relationships. This imparts to Samba scalability similar to that with MS Windows NT4.

        - - - - - + + + + + Given that Samba-3 can function with a scalable backend authentication database such as LDAP, and given its ability to run in primary as well as backup domain control modes, the administrator would be well-advised to consider alternatives to the use of interdomain trusts simply because, by the very nature of how trusts function, this system is fragile. That was, after all, a key reason for the development and adoption of Microsoft Active Directory. -

        Trust Relationship Background

        - - - - - - +

        Trust Relationship Background

        + + + + + + MS Windows NT3/4-type security domains employ a nonhierarchical security structure. The limitations of this architecture as it effects the scalability of MS Windows networking in large organizations is well known. Additionally, the flat namespace that results from this design significantly impacts the delegation of administrative responsibilities in large and diverse organizations.

        - - - - - + + + + + Microsoft developed Active Directory Service (ADS), based on Kerberos and LDAP, as a means of circumventing the limitations of the older technologies. Not every organization is ready or willing to embrace ADS. For small companies the older NT4-style domain security paradigm is quite adequate, and so there remains an entrenched user base for whom there is no direct desire to go through a disruptive change to adopt ADS.

        - - - - - - - + + + + + + + With Windows NT, Microsoft introduced the ability to allow different security domains to effect a mechanism so users from one domain may be given access rights and privileges in another domain. The language that describes this capability is couched in terms of @@ -97,41 +97,41 @@ is the trusting domain. With NT3.x/4.0 all trust relationships are always in one so if users in both domains are to have privileges and rights in each others' domain, then it is necessary to establish two relationships, one in each direction.

        - - - - - + + + + + Further, in an NT4-style MS security domain, all trusts are nontransitive. This means that if there are three domains (let's call them red, white, and blue), where red and white have a trust relationship, and white and blue have a trust relationship, then it holds that there is no implied trust between the red and blue domains. Relationships are explicit and not transitive.

        - - - - - - - + + + + + + + New to MS Windows 2000 ADS security contexts is the fact that trust relationships are two-way by default. Also, all inter-ADS domain trusts are transitive. In the case of the red, white, and blue domains, with Windows 2000 and ADS, the red and blue domains can trust each other. This is an inherent feature of ADS domains. Samba-3 implements MS Windows NT4-style interdomain trusts and interoperates with MS Windows 200x ADS security domains in similar manner to MS Windows NT4-style domains. -

        Native MS Windows NT4 Trusts Configuration

        - - - +

        Native MS Windows NT4 Trusts Configuration

        + + + There are two steps to creating an interdomain trust relationship. To effect a two-way trust relationship, it is necessary for each domain administrator to create a trust account for the other domain to use in verifying security credentials. -

        Creating an NT4 Domain Trust

        - - - - - +

        Creating an NT4 Domain Trust

        + + + + + For MS Windows NT4, all domain trust relationships are configured using the Domain User Manager. This is done from the Domain User Manager Policies entry on the menu bar. From the Policy menu, select @@ -142,26 +142,26 @@ to enter the name of the remote domain that will be able to assign access rights your domain. You will also need to enter a password for this trust relationship, which the trusting domain will use when authenticating users from the trusted domain. The password needs to be typed twice (for standard confirmation). -

        Completing an NT4 Domain Trust

        - - - - - - +

        Completing an NT4 Domain Trust

        + + + + + + A trust relationship will work only when the other (trusting) domain makes the appropriate connections with the trusted domain. To consummate the trust relationship, the administrator launches the Domain User Manager from the menu selects Policies, then select Trust Relationships, and clicks on the Add button next to the box that is labeled Trusted Domains. A panel opens in which must be entered the name of the remote domain as well as the password assigned to that trust. -

        Interdomain Trust Facilities

        - - - - - - +

        Interdomain Trust Facilities

        + + + + + + A two-way trust relationship is created when two one-way trusts are created, one in each direction. Where a one-way trust has been established between two MS Windows NT4 domains (let's call them DomA and DomB), the following facilities are created: @@ -201,26 +201,26 @@ DomA and DomB), the following facilities are created:

      2. Global groups from the trusted domain can be made members in local groups on MS Windows domain member machines. -

    Configuring Samba NT-Style Domain Trusts

    - +

    Configuring Samba NT-Style Domain Trusts

    + This description is meant to be a fairly short introduction about how to set up a Samba server so that it can participate in interdomain trust relationships. Trust relationship support in Samba is at an early stage, so do not be surprised if something does not function as it should.

    - - - - + + + + Each of the procedures described next assumes the peer domain in the trust relationship is controlled by a Windows NT4 server. However, the remote end could just as well be another Samba-3 domain. It can be clearly seen, after reading this document, that combining Samba-specific parts of what's written in the following sections leads to trust between domains in a purely Samba environment.

    Samba as the Trusted Domain

    - - - - - + + + + + In order to set the Samba PDC to be the trusted party of the relationship, you first need to create a special account for the domain that will be the trusting party. To do that, you can use the smbpasswd utility. Creating the trusted domain account is @@ -239,19 +239,19 @@ where -a means to add a new account into the passdb database and -i means to “create this account with the Interdomain trust flag”.

    - - - - + + + + The account name will be “rumba$” (the name of the remote domain). If this fails, you should check that the trust account has been added to the system password database (/etc/passwd). If it has not been added, you can add it manually and then repeat the previous step.

    - - - - + + + + After issuing this command, you will be asked to enter the password for the account. You can use any password you want, but be aware that Windows NT will not change this password until 7 days following account creation. After the command returns successfully, you can look at the entry for the new account (in the standard way as @@ -259,47 +259,47 @@ appropriate for your configuration) and see that the account's name is really RU “I” flag set in the flags field. Now you are ready to confirm the trust by establishing it from Windows NT Server.

    - - - - - + + + + + Open User Manager for Domains and from the Policies menu, select Trust Relationships.... Beside the Trusted domains list box, click the Add... button. You will be prompted for the trusted domain name and the relationship password. Type in SAMBA, as this is the name of the remote domain and the password used at the time of account creation. Click on OK and, if everything went without incident, you will see the Trusted domain relationship successfully established message. -

    Samba as the Trusting Domain

    - - +

    Samba as the Trusting Domain

    + + This time activities are somewhat reversed. Again, we'll assume that your domain controlled by the Samba PDC is called SAMBA and the NT-controlled domain is called RUMBA.

    The very first step is to add an account for the SAMBA domain on RUMBA's PDC.

    - - - + + + Launch the Domain User Manager, then from the menu select Policies, Trust Relationships. Now, next to the Trusting Domains box, press the Add button and type in the name of the trusted domain (SAMBA) and the password to use in securing the relationship.

    - - + + The password can be arbitrarily chosen. It is easy to change the password from the Samba server whenever you want. After you confirm the password, your account is ready for use. Now its Samba's turn.

    Using your favorite shell while logged in as root, issue this command: - +

    root# net rpc trustdom establish rumba

    - - - + + + You will be prompted for the password you just typed on your Windows NT4 Server box. An error message, "NT_STATUS_NOLOGON_INTERDOMAIN_TRUST_ACCOUNT," that may be reported periodically is of no concern and may safely be ignored. @@ -311,20 +311,20 @@ relationship has just been established.

    Note

    You have to run this command as root because you must have write access to the secrets.tdb file. -

    NT4-Style Domain Trusts with Windows 2000

    - - - - +

    NT4-Style Domain Trusts with Windows 2000

    + + + + Although Domain User Manager is not present in Windows 2000, it is also possible to establish an NT4-style trust relationship with a Windows 2000 domain controller running in mixed mode as the trusting server. It should also be possible for Samba to trust a Windows 2000 server; however, more testing is still needed in this area.

    - - - - + + + + After creating the interdomain trust account on the Samba server as described previously, open Active Directory Domains and Trusts on the AD controller of the domain whose resources you wish Samba users to have access to. Remember that since NT4-style @@ -338,11 +338,11 @@ Press this button and, just as with NT4, you will be prompted for the trusted do password. Press OK and after a moment, Active Directory will respond with The trusted domain has been added and the trust has been verified. Your Samba users can now be granted access to resources in the AD domain. -

    Common Errors

    +

    Common Errors

    Interdomain trust relationships should not be attempted on networks that are unstable or that suffer regular outages. Network stability and integrity are key concerns with distributed trusted domains. -

    Browsing of Trusted Domain Fails

    +

    Browsing of Trusted Domain Fails

    Browsing from a machine in a trusted Windows 200x domain to a Windows 200x member of a trusting Samba domain, I get the following error: 

    @@ -360,7 +360,7 @@ seems to be fine. By default, when you unjoin a domain (the Windows 200x
 domain), the computer tries to automatically disable the computer account in 
 the domain.  If you are running as an account that has privileges to do this 
 when you unjoin the machine, it is done; otherwise it is not done.
-

    Problems with LDAP ldapsam and Older Versions of smbldap-tools

    +

    Problems with LDAP ldapsam and Older Versions of smbldap-tools

    If you use the smbldap-useradd script to create a trust account to set up interdomain trusts, the process of setting up the trust will fail. The account that was created in the LDAP database will have an account diff --git a/docs/htmldocs/Samba3-HOWTO/IntroSMB.html b/docs/htmldocs/Samba3-HOWTO/IntroSMB.html index e93880a579..8619580647 100644 --- a/docs/htmldocs/Samba3-HOWTO/IntroSMB.html +++ b/docs/htmldocs/Samba3-HOWTO/IntroSMB.html @@ -1,4 +1,4 @@ -Introduction

    Introduction
    Prev   Next

    Introduction

    John H. Terpstra

    Samba Team

    June 29, 2003

    Table of Contents

    What Is Samba?
    Why This Book?
    Book Structure and Layout

    “ +Introduction

    Introduction
    Prev   Next

    Introduction

    John H. Terpstra

    Samba Team

    June 29, 2003

    Table of Contents

    What Is Samba?
    Why This Book?
    Book Structure and Layout

    “ A man's gift makes room for him before great men. Gifts are like hooks that can catch hold of the mind taking it beyond the reach of forces that otherwise might constrain it. ” --- Anon. @@ -15,7 +15,7 @@ that it is hard to find the information they think they need. So if you are a Microsoft certified specialist, this book should meet your needs rather well. If you are a UNIX or Linux administrator, there is no need to feel badly you should have no difficulty finding answers to your current concerns also. -

    What Is Samba?

    +

    What Is Samba?

    Samba is a big, complex project. The Samba project is ambitious and exciting. The team behind Samba is a group of some thirty individuals who are spread the world over and come from an interesting range of backgrounds. This team @@ -45,7 +45,7 @@ should have no difficulty finding answers to your current concerns also. be done. User feedback drives Samba development. Samba-3 in particular incorporates a huge amount of work done as a result of user requests, suggestions and direct code contributions. -

    Why This Book?

    +

    Why This Book?

    There is admittedly a large number of Samba books on the market today and each book has its place. Despite the apparent plethora of books, Samba as a project continues to receive much criticism for failing to provide @@ -97,7 +97,7 @@ should have no difficulty finding answers to your current concerns also. are very different from that of the UNIX administrator. This book has been arranged and the information presented from the perspective of someone with previous Microsoft Windows network administrative training and experience. -

    Book Structure and Layout

    +

    Book Structure and Layout

    This book is presented in six parts:

    General Installation

    Designed to help you get Samba-3 running quickly. diff --git a/docs/htmldocs/Samba3-HOWTO/NT4Migration.html b/docs/htmldocs/Samba3-HOWTO/NT4Migration.html index e2ed5b3c2d..5ae4da74f1 100644 --- a/docs/htmldocs/Samba3-HOWTO/NT4Migration.html +++ b/docs/htmldocs/Samba3-HOWTO/NT4Migration.html @@ -1,37 +1,37 @@ -Chapter 36. Migration from NT4 PDC to Samba-3 PDC

    Chapter 36. Migration from NT4 PDC to Samba-3 PDC
    Prev Part IV. Migration and Updating Next

    Chapter 36. Migration from NT4 PDC to Samba-3 PDC

    John H. Terpstra

    Samba Team

    April 3, 2003

    Table of Contents

    Planning and Getting Started
    Objectives
    Steps in Migration Process
    Migration Options
    Planning for Success
    Samba-3 Implementation Choices

    - - +Chapter 36. Migration from NT4 PDC to Samba-3 PDC

    Chapter 36. Migration from NT4 PDC to Samba-3 PDC
    Prev Part IV. Migration and Updating Next

    Chapter 36. Migration from NT4 PDC to Samba-3 PDC

    John H. Terpstra

    Samba Team

    April 3, 2003

    Table of Contents

    Planning and Getting Started
    Objectives
    Steps in Migration Process
    Migration Options
    Planning for Success
    Samba-3 Implementation Choices

    + + This is a rough guide to assist those wishing to migrate from NT4 domain control to Samba-3-based domain control. -

    Planning and Getting Started

    - +

    Planning and Getting Started

    + In the IT world there is often a saying that all problems are encountered because of poor planning. The corollary to this saying is that not all problems can be anticipated and planned for. Then again, good planning will anticipate most show-stopper-type situations.

    - + Those wishing to migrate from MS Windows NT4 domain control to a Samba-3 domain control environment would do well to develop a detailed migration plan. So here are a few pointers to help migration get underway. -

    Objectives

    - +

    Objectives

    + The key objective for most organizations is to make the migration from MS Windows NT4 to Samba-3 domain control as painless as possible. One of the challenges you may experience in your migration process may well be convincing management that the new environment should remain in place. Many who have introduced open source technologies have experienced pressure to return to a Microsoft-based platform solution at the first sign of trouble.

    - + Before attempting a migration to a Samba-3-controlled network, make every possible effort to gain all-round commitment to the change. Know precisely why the change is important for the organization. Possible motivations to make a change include: -

    • Improve network manageability.

    • Obtain better user-level functionality.

    • Reduce network operating costs.

    • Reduce exposure caused by Microsoft withdrawal of NT4 support.

    • Avoid MS License 6 implications.

    • Reduce organization's dependency on Microsoft.

    - - - - - - +

    • Improve network manageability.

    • Obtain better user-level functionality.

    • Reduce network operating costs.

    • Reduce exposure caused by Microsoft withdrawal of NT4 support.

    • Avoid MS License 6 implications.

    • Reduce organization's dependency on Microsoft.

    + + + + + + Make sure everyone knows that Samba-3 is not MS Windows NT4. Samba-3 offers an alternative solution that is both different from MS Windows NT4 and offers advantages compared with it. Gain recognition that Samba-3 lacks many of the @@ -39,32 +39,32 @@ features that Microsoft has promoted as core values in migration from MS Windows MS Windows 2000 and beyond (with or without Active Directory services).

    What are the features that Samba-3 cannot provide? -

    • Active Directory Server.

    • Group Policy Objects (in Active Directory).

    • Machine Policy Objects.

    • Logon Scripts in Active Directory.

    • Software Application and Access Controls in Active Directory.

    +

    • Active Directory Server.

    • Group Policy Objects (in Active Directory).

    • Machine Policy Objects.

    • Logon Scripts in Active Directory.

    • Software Application and Access Controls in Active Directory.

    The features that Samba-3 does provide and that may be of compelling interest to your site include: -

    • Lower cost of ownership.

    • Global availability of support with no strings attached.

    • Dynamic SMB servers (can run more than one SMB/CIFS server per UNIX/Linux system).

    • Creation of on-the-fly logon scripts.

    • Creation of on-the-fly policy files.

    • Greater stability, reliability, performance, and availability.

    • Manageability via an SSH connection.

    • Flexible choices of backend authentication technologies (tdbsam, ldapsam).

    • Ability to implement a full single-sign-on architecture.

    • Ability to distribute authentication systems for absolute minimum wide-area network bandwidth demand.

    - +

    • Lower cost of ownership.

    • Global availability of support with no strings attached.

    • Dynamic SMB servers (can run more than one SMB/CIFS server per UNIX/Linux system).

    • Creation of on-the-fly logon scripts.

    • Creation of on-the-fly policy files.

    • Greater stability, reliability, performance, and availability.

    • Manageability via an SSH connection.

    • Flexible choices of backend authentication technologies (tdbsam, ldapsam).

    • Ability to implement a full single-sign-on architecture.

    • Ability to distribute authentication systems for absolute minimum wide-area network bandwidth demand.

    + Before migrating a network from MS Windows NT4 to Samba-3, consider all necessary factors. Users should be educated about changes they may experience so the change will be a welcome one and not become an obstacle to the work they need to do. The following sections explain factors that will help ensure a successful migration. -

    Domain Layout

    - - - - - - - - - - - - - - - - +

    Domain Layout

    + + + + + + + + + + + + + + + + Samba-3 can be configured as a domain controller, a backup domain controller (probably best called a secondary controller), a domain member, or a standalone server. The Windows network security domain context should be sized and scoped before implementation. Particular attention needs to be @@ -74,36 +74,36 @@ authentication backend, then the same database can be used by several different complex organization, there can be a single LDAP database, which itself can be distributed (have a master server and multiple slave servers) that can simultaneously serve multiple domains.

    - + From a design perspective, the number of users per server as well as the number of servers per domain should be scaled taking into consideration server capacity and network bandwidth.

    - - - - - - + + + + + + A physical network segment may house several domains. Each may span multiple network segments. Where domains span routed network segments, consider and test the performance implications of the design and layout of a network. A centrally located domain controller that is designed to serve multiple routed network segments may result in severe performance problems. Check the response time (ping timing) between the remote segment and the PDC. If it's long (more than 100 ms), locate a BDC on the remote segment to serve as the local authentication and access control server. -

    Server Share and Directory Layout

    - - +

    Server Share and Directory Layout

    + + There are cardinal rules to effective network design that cannot be broken with impunity. The most important rule: Simplicity is king in every well-controlled network. Every part of the infrastructure must be managed; the more complex it is, the greater will be the demand of keeping systems secure and functional.

    - - - - - - + + + + + + Keep in mind the nature of how data must be shared. Physical disk space layout should be considered carefully. Some data must be backed up. The simpler the disk layout, the easier it will be to keep track of backup needs. Identify what backup media will meet your needs; consider backup to tape, @@ -111,18 +111,18 @@ CD-ROM or DVD-ROM, or other offline storage medium. Plan and implement for minim maintenance. Leave nothing to chance in your design; above all, do not leave backups to chance: backup, test, and validate every backup; create a disaster recovery plan and prove that it works.

    - - - + + + Users should be grouped according to data access control needs. File and directory access is best controlled via group permissions, and the use of the “sticky bit” on group-controlled directories may substantially avoid file access complaints from Samba share users.

    - - - - - + + + + + Inexperienced network administrators often attempt elaborate techniques to set access controls on files, directories, shares, as well as in share definitions. Keep your design and implementation simple and document your design extensively. Have others @@ -131,8 +131,8 @@ Remember, job security through complex design and implementation may cause loss and downtime to users as the new administrator learns to untangle your knots. Keep access controls simple and effective, and make sure that users will never be interrupted by obtuse complexity. -

    Logon Scripts

    - +

    Logon Scripts

    + Logon scripts can help to ensure that all users gain the share and printer connections they need.

    Logon scripts can be created on the fly so all commands executed are specific to the @@ -140,55 +140,55 @@ rights and privileges granted to the user. The preferred controls should be effe group membership so group information can be used to create a custom logon script using the root preexec parameters to the NETLOGON share.

    - + Some sites prefer to use a tool such as kixstart to establish a controlled user environment. In any case, you may wish to do a Google search for logon script process controls. In particular, you may wish to explore the use of the Microsoft Knowledge Base article KB189105 that deals with how to add printers without user intervention via the logon script process. -

    Profile Migration/Creation

    +

    Profile Migration/Creation

    User and group profiles may be migrated using the tools described in the section titled Desktop Profile Management.

    - - + + Profiles may also be managed using the Samba-3 tool profiles. This tool allows the MS Windows NT-style security identifiers (SIDs) that are stored inside the profile NTuser.DAT file to be changed to the SID of the Samba-3 domain. -

    User and Group Accounts

    - - - - +

    User and Group Accounts

    + + + + It is possible to migrate all account settings from an MS Windows NT4 domain to Samba-3. Before attempting to migrate user and group accounts, you are STRONGLY advised to create in Samba-3 the groups that are present on the MS Windows NT4 domain AND to map them to suitable UNIX/Linux groups. By following this simple advice, all user and group attributes should migrate painlessly. -

    Steps in Migration Process

    +

    Steps in Migration Process

    The approximate migration process is described below.

    • You have an NT4 PDC that has the users, groups, policies, and profiles to be migrated.

    • - - - + + + Samba-3 is set up as a domain controller with netlogon share, profile share, and so on. Configure the smb.conf file to function as a BDC: domain master = No. -

    Procedure 36.1. The Account Migration Process

    1. - +

    Procedure 36.1. The Account Migration Process

    1. + Create a BDC account in the old NT4 domain for the Samba server using NT Server Manager. Samba must not be running.

    2. - + net rpc join -S NT4PDC -w DOMNAME -U Administrator%passwd

    3. - + net rpc vampire -S NT4PDC -U administrator%passwd

    4. pdbedit -L

      Note: Did the users migrate?

    5. - - + + Now assign each of the UNIX groups to NT groups: (It may be useful to copy this text to a script called initGroups.sh) 

      @@ -208,11 +208,11 @@ net groupmap add ntgroup="QA Team"   unixgroup=qateam    type=d

    6. net groupmap list

      Check that all groups are recognized.

    Migrate all the profiles, then migrate all policy files. -

    Migration Options

    +

    Migration Options

    Sites that wish to migrate from MS Windows NT4 domain control to a Samba-based solution generally fit into three basic categories. Following table shows the possibilities.

    Table 36.1. The Three Major Site Types

    Number of UsersDescription
    < 50

    Want simple conversion with no pain.

    50 - 250

    Want new features; can manage some inhouse complexity.

    > 250

    Solution/implementation must scale well; complex needs. - Cross-departmental decision process. Local expertise in most areas.


    Planning for Success

    + Cross-departmental decision process. Local expertise in most areas.


    Planning for Success

    There are three basic choices for sites that intend to migrate from MS Windows NT4 to Samba-3:

    • @@ -233,31 +233,31 @@ Minimize downstream problems by: Testing the full roll-out program, including workstation deployment.

    Following table lists the conversion choices given the type of migration being contemplated. -

    Table 36.2. Nature of the Conversion Choices

    Simple InstallUpgrade DecisionsRedesign Decisions

    Make use of minimal OS-specific features

    Translate NT4 features to new host OS features

    Improve on NT4 functionality, enhance management capabilities

    Move all accounts from NT4 into Samba-3

    Copy and improve

    Authentication regime (database location and access)

    Make least number of operational changes

    Make progressive improvements

    Desktop management methods

    Take least amount of time to migrate

    Minimize user impact

    Better control of Desktops/Users

    Live versus isolated conversion

    Maximize functionality

    Identify Needs for: Manageability, Scalability, Security, Availability

    Integrate Samba-3, then migrate while users are active, then change of control (swap out)

    Take advantage of lower maintenance opportunity


    Samba-3 Implementation Choices

    Authentication Database/Backend

    +

    Table 36.2. Nature of the Conversion Choices

    Simple InstallUpgrade DecisionsRedesign Decisions

    Make use of minimal OS-specific features

    Translate NT4 features to new host OS features

    Improve on NT4 functionality, enhance management capabilities

    Move all accounts from NT4 into Samba-3

    Copy and improve

    Authentication regime (database location and access)

    Make least number of operational changes

    Make progressive improvements

    Desktop management methods

    Take least amount of time to migrate

    Minimize user impact

    Better control of Desktops/Users

    Live versus isolated conversion

    Maximize functionality

    Identify Needs for: Manageability, Scalability, Security, Availability

    Integrate Samba-3, then migrate while users are active, then change of control (swap out)

    Take advantage of lower maintenance opportunity


    Samba-3 Implementation Choices

    Authentication Database/Backend

    Samba-3 can use an external authentication backend:

    • Winbind (external Samba or NT4/200x server).

    • External server could use Active Directory or NT4 domain.

    • Can use pam_mkhomedir.so to autocreate home directories.

    • Samba-3 can use a local authentication backend: smbpasswd, tdbsam, ldapsam

    Access Control Points

    Samba permits Access Control points to be set: -

    • On the share itself using share ACLs.

    • On the file system using UNIX permissions on files and directories.

      Note: Can enable Posix ACLs in file system also.

    • Through Samba share parameters not recommended except as last resort.

    Policies (migrate or create new ones)

    - - +

    • On the share itself using share ACLs.

    • On the file system using UNIX permissions on files and directories.

      Note: Can enable Posix ACLs in file system also.

    • Through Samba share parameters not recommended except as last resort.

    Policies (migrate or create new ones)

    + + Exercise great caution when making registry changes; use the right tool and be aware that changes made through NT4-style NTConfig.POL files can leave permanent changes. - - - + + +

    • Using Group Policy Editor (NT4).

    • Watch out for tattoo effect.

    User and Group Profiles

    - - + + Platform-specific, so use platform tool to change from a local to a roaming profile. Can use new profiles tool to change SIDs (NTUser.DAT).

    Logon Scripts

    Know how they work.

    User and Group Mapping to UNIX/Linux

    - + User and group mapping code is new. Many problems have been experienced as network administrators who are familiar with Samba-2.2.x migrate to Samba-3. Carefully study the chapters that document the new password backend behavior and the new group mapping functionality. @@ -274,6 +274,6 @@ being contemplated. (Linux 8 chars, NT4 up to 254 chars).

  • Add/Delete Machines: Applied only to domain members (Note: machine names may be limited to 16 characters).

  • Use net groupmap to connect NT4 groups to UNIX groups.

  • Add/Delete Groups: Note OS limits on size and nature. Linux limit is 16 char, no spaces, and no uppercase chars (groupadd).

    • Migration Tools

    - + Domain Control (NT4-Style) Profiles, Policies, Access Controls, Security

    • Samba: net, rpcclient, smbpasswd, pdbedit, profiles

    • Windows: NT4 Domain User Manager, Server Manager (NEXUS)

    Prev Up Next
    Chapter 35. Updating and Upgrading Samba Home Chapter 37. SWAT: The Samba Web Administration Tool
    diff --git a/docs/htmldocs/Samba3-HOWTO/NetCommand.html b/docs/htmldocs/Samba3-HOWTO/NetCommand.html index 78d2e7670e..a7e50f5da4 100644 --- a/docs/htmldocs/Samba3-HOWTO/NetCommand.html +++ b/docs/htmldocs/Samba3-HOWTO/NetCommand.html @@ -1,16 +1,16 @@ -Chapter 13. Remote and Local Management: The Net Command
    Chapter 13. Remote and Local Management: The Net Command
    Prev Part III. Advanced Configuration Next

    Chapter 13. Remote and Local Management: The Net Command

    John H. Terpstra

    Samba Team

    Volker Lendecke

    Samba Team

    Guenther Deschner

    SuSE

    May 9, 2005

    Table of Contents

    Overview
    Administrative Tasks and Methods
    UNIX and Windows Group Management
    Adding, Renaming, or Deletion of Group Accounts
    Manipulating Group Memberships
    Nested Group Support
    UNIX and Windows User Management
    Adding User Accounts
    Deletion of User Accounts
    Managing User Accounts
    User Mapping
    Administering User Rights and Privileges
    Managing Trust Relationships
    Machine Trust Accounts
    Interdomain Trusts
    Managing Security Identifiers (SIDS)
    Share Management
    Creating, Editing, and Removing Shares
    Creating and Changing Share ACLs
    Share, Directory, and File Migration
    Printer Migration
    Controlling Open Files
    Session and Connection Management
    Printers and ADS
    Manipulating the Samba Cache
    Managing IDMAP UID/SID Mappings
    Creating an IDMAP Database Dump File
    Restoring the IDMAP Database Dump File
    Other Miscellaneous Operations

    - - +Chapter 13. Remote and Local Management: The Net Command

    Chapter 13. Remote and Local Management: The Net Command
    Prev Part III. Advanced Configuration Next

    Chapter 13. Remote and Local Management: The Net Command

    John H. Terpstra

    Samba Team

    Volker Lendecke

    Samba Team

    Guenther Deschner

    SuSE

    May 9, 2005

    Table of Contents

    Overview
    Administrative Tasks and Methods
    UNIX and Windows Group Management
    Adding, Renaming, or Deletion of Group Accounts
    Manipulating Group Memberships
    Nested Group Support
    UNIX and Windows User Management
    Adding User Accounts
    Deletion of User Accounts
    Managing User Accounts
    User Mapping
    Administering User Rights and Privileges
    Managing Trust Relationships
    Machine Trust Accounts
    Interdomain Trusts
    Managing Security Identifiers (SIDS)
    Share Management
    Creating, Editing, and Removing Shares
    Creating and Changing Share ACLs
    Share, Directory, and File Migration
    Printer Migration
    Controlling Open Files
    Session and Connection Management
    Printers and ADS
    Manipulating the Samba Cache
    Managing IDMAP UID/SID Mappings
    Creating an IDMAP Database Dump File
    Restoring the IDMAP Database Dump File
    Other Miscellaneous Operations

    + + The net command is one of the new features of Samba-3 and is an attempt to provide a useful tool for the majority of remote management operations necessary for common tasks. The net tool is flexible by design and is intended for command-line use as well as for scripted control application.

    - - - + + + Originally introduced with the intent to mimic the Microsoft Windows command that has the same name, the net command has morphed into a very powerful instrument that has become an essential part of the Samba network administrator's toolbox. The Samba Team has introduced tools, such as @@ -22,27 +22,27 @@ provided should look at the net command before sear

    A Samba-3 administrator cannot afford to gloss over this chapter because to do so will almost certainly cause the infliction of self-induced pain, agony, and desperation. Be warned: this is an important chapter. -

    Overview

    - - +

    Overview

    - + + + The tasks that follow the installation of a Samba-3 server, whether standalone or domain member, of a domain controller (PDC or BDC) begins with the need to create administrative rights. Of course, the creation of user and group accounts is essential for both a standalone server and a PDC. In the case of a BDC or a Domain Member server (DMS), domain user and group accounts are obtained from the central domain authentication backend.

    - - - + + + Regardless of the type of server being installed, local UNIX groups must be mapped to the Windows networking domain global group accounts. Do you ask why? Because Samba always limits its access to the resources of the host server by way of traditional UNIX UID and GID controls. This means that local @@ -50,41 +50,41 @@ the infliction of self-induced pain, agony, and desperation. Be warned: this is global groups can be given access rights based on UIDs and GIDs local to the server that is hosting Samba. Such mappings are implemented using the net command.

    - - - + + + UNIX systems that are hosting a Samba-3 server that is running as a member (PDC, BDC, or DMS) must have a machine security account in the domain authentication database (or directory). The creation of such security (or trust) accounts is also handled using the net command.

    - - - + + + The establishment of interdomain trusts is achieved using the net command also, as may a plethora of typical administrative duties such as user management, group management, share and printer management, file and printer migration, security identifier management, and so on.

    - - + + The overall picture should be clear now: the net command plays a central role on the Samba-3 stage. This role will continue to be developed. The inclusion of this chapter is evidence of its importance, one that has grown in complexity to the point that it is no longer considered prudent to cover its use fully in the online UNIX man pages. -

    Administrative Tasks and Methods

    - - +

    Administrative Tasks and Methods

    - + + + The basic operations of the net command are documented here. This documentation is not exhaustive, and thus it is incomplete. Since the primary focus is on migration from Windows servers to a Samba server, the emphasis is on the use of the Distributed Computing Environment Remote Procedure Call (DCE RPC) @@ -94,36 +94,36 @@ the infliction of self-induced pain, agony, and desperation. Be warned: this is automatically fall back via the ads, rpc, and rap modes. Please refer to the man page for a more comprehensive overview of the capabilities of this utility. -

    UNIX and Windows Group Management

    - - - - - +

    UNIX and Windows Group Management

    + + + + + As stated, the focus in most of this chapter is on use of the net rpc family of operations that are supported by Samba. Most of them are supported by the net ads mode when used in connection with Active Directory. The net rap operating mode is also supported for some of these operations. RAP protocols are used by IBM OS/2 and by several earlier SMB servers.

    - - + + Samba's net tool implements sufficient capability to permit all common administrative tasks to be completed from the command line. In this section each of the essential user and group management facilities are explored.

    - - - - + + + + Samba-3 recognizes two types of groups: domain groups and local groups. Domain groups can contain (have as members) only domain user accounts. Local groups can contain local users, domain users, and domain groups as members.

    The purpose of a local group is to permit file permission to be set for a group account that, like the usual UNIX/Linux group, is persistent across redeployment of a Windows file server. -

    Adding, Renaming, or Deletion of Group Accounts

    +

    Adding, Renaming, or Deletion of Group Accounts

    Samba provides file and print services to Windows clients. The file system resources it makes available to the Windows environment must, of necessity, be provided in a manner that is compatible with the Windows networking environment. UNIX groups are created and deleted as required to serve operational @@ -143,11 +143,11 @@ the infliction of self-induced pain, agony, and desperation. Be warned: this is between the UNIX group account and its members to the respective Windows group accounts. It goes on to show how UNIX group members automatically pass-through to Windows group membership as soon as a logical mapping has been created. -

    Adding or Creating a New Group

    +

    Adding or Creating a New Group

    Before attempting to add a Windows group account, the currently available groups can be listed as shown here: - - + + 

     root#  net rpc group list -Uroot%not24get
 Password:
@@ -163,7 +163,7 @@ Engineers
 	
    
 	A Windows group account called “SupportEngrs” can be added by executing the following
 command:
-
+
 
     root#  net rpc group add "SupportEngrs" -Uroot%not24get
 
    
@@ -183,9 +183,9 @@ Engineers
 SupportEngrs

    - - + + The following demonstrates that the POSIX (UNIX/Linux system account) group has been created by calling the add group script = /opt/IDEALX/sbin/smbldap-groupadd -p "%g" interface script: @@ -205,7 +205,7 @@ SupportEngrs:x:1003: The following demonstrates that the use of the net command to add a group account results in immediate mapping of the POSIX group that has been created to the Windows group account as shown here: - + 

     root#  net groupmap list
 Domain Admins (S-1-5-21-72630-4128915-11681869-512) -> Domain Admins
@@ -218,19 +218,19 @@ Domain Computers (S-1-5-21-72630-4128915-11681869-553) -> Domain Computers
 Engineers (S-1-5-21-72630-4128915-11681869-3005) -> Engineers
 SupportEngrs (S-1-5-21-72630-4128915-11681869-3007) -> SupportEngrs

    -

    Mapping Windows Groups to UNIX Groups

    - - +

    Mapping Windows Groups to UNIX Groups

    + + Windows groups must be mapped to UNIX system (POSIX) groups so that file system access controls can be asserted in a manner that is consistent with the methods appropriate to the operating system that is hosting the Samba server.

    - - + + All file system (file and directory) access controls, within the file system of a UNIX/Linux server that is hosting a Samba server, are implemented using a UID/GID identity tuple. Samba does not in any way override or replace UNIX file system semantics. Thus it is necessary that all Windows networking operations that @@ -238,22 +238,22 @@ SupportEngrs (S-1-5-21-72630-4128915-11681869-3007) -> SupportEngrs account. The user account must also map to a locally known UID. Note that the net command does not call any RPC-functions here but directly accesses the passdb.

    - - - + + + Samba depends on default mappings for the Domain Admins, Domain Users, and Domain Guests global groups. Additional groups may be added as shown in the examples just given. There are times when it is necessary to map an existing UNIX group account to a Windows group. This operation, in effect, creates a Windows group account as a consequence of creation of the mapping.

    - - - + + + The operations that are permitted include: add, modify, and delete. An example of each operation is shown here.

    Note

    @@ -290,15 +290,15 @@ SupportEngrs (S-1-5-21-72630-4128915-11681869-3007) -> SupportEngrs Supported mapping types are 'd' (domain global) and 'l' (domain local), a domain local group in Samba is treated as local to the individual Samba server. Local groups can be used with Samba to enable multiple nested group support. -

    Deleting a Group Account

    - +

    Deleting a Group Account

    + A group account may be deleted by executing the following command: 

     root#  net rpc group delete SupportEngineers -Uroot%not24get

    Validation of the deletion is advisable. The same commands may be executed as shown above. -

    Rename Group Accounts

    Note

    +

    Rename Group Accounts

    Note

    This command is not documented in the man pages; it is implemented in the source code, but it does not work at this time. The example given documents, from the source code, how it should work. Watch the release notes of a future release to see when this may have been fixed. @@ -306,7 +306,7 @@ SupportEngrs (S-1-5-21-72630-4128915-11681869-3007) -> SupportEngrs Sometimes it is necessary to rename a group account. Good administrators know how painful some managers' demands can be if this simple request is ignored. The following command demonstrates how the Windows group “SupportEngrs” can be renamed to “CustomerSupport”: - + 

     root#  net rpc group rename SupportEngrs \
     CustomerSupport -Uroot%not24get
@@ -349,7 +349,7 @@ Engineers (S-1-5-21-72630-412605-116429-3001) -> Engineers
 	Given that the user ajt is already a member of the UNIX/Linux group and, via the
 	group mapping, a member of the Windows group, an attempt to add this account again should fail. This is
 	demonstrated here:
-
+
 
     root#  net rpc group addmem "MIDEARTH\Engineers" ajt -Uroot%not24get
 Could not add ajt to MIDEARTH\Engineers: NT_STATUS_MEMBER_IN_GROUP
@@ -359,7 +359,7 @@ Could not add ajt to MIDEARTH\Engineers: NT_STATUS_MEMBER_IN_GROUP
 	
    
 	To permit the user ajt to be added using the net rpc group utility,
 	this account must first be removed. The removal and confirmation of its effect is shown here:
-
+
 
     root#  net rpc group delmem "MIDEARTH\Engineers" ajt -Uroot%not24get
 root#  getent group Engineers
@@ -383,7 +383,7 @@ MIDEARTH\ajt
 	In this example the members of the Windows Domain Users account are validated using
 	the net rpc group utility. Note the this contents of the UNIX/Linux group was shown
 	four paragraphs earlier. The Windows (domain) group membership is shown here:
-
+
 
     root#  net rpc group members "Domain Users" -Uroot%not24get
 MIDEARTH\jht
@@ -440,11 +440,11 @@ DOM\jht
 
     root#  net rpc group delmem demo "DOM\jht" -Uroot%not24get
 
    
-	
    Managing Nest Groups on Workstations from the Samba Server
    
+	
    Managing Nest Groups on Workstations from the Samba Server
    
 	Windows network administrators often ask on the Samba mailing list how it is possible to grant everyone
 	administrative rights on their own workstation. This is of course a very bad practice, but commonly done
 	to avoid user complaints. Here is how it can be done remotely from a Samba PDC or BDC:
-
+
 
     root#  net rpc group addmem "Administrators" "Domain Users" \
     -S WINPC032 -Uadministrator%secret
@@ -452,19 +452,19 @@ DOM\jht
 	
    
 	This can be scripted, and can therefore be performed as a user logs onto the domain from a Windows
 	workstation. Here is a simple example that shows how this can be done.
-	
    Procedure 13.1. Automating User Addition to the Workstation Power Users Group
    Example 13.1. Script to Auto-add Domain Users to Workstation Power Users Group
    +	
    Procedure 13.1. Automating User Addition to the Workstation Power Users Group
    Example 13.1. Script to Auto-add Domain Users to Workstation Power Users Group
     #!/bin/bash
 
 /usr/bin/net rpc group addmem "Power Users" "DOMAIN_NAME\$1" \
                    -UAdministrator%secret -S $2
 
 exit 0
-

    Example 13.2. A Magic Netlogon Share
     
    [netlogon]
    comment = Netlogon Share
    path = /var/lib/samba/netlogon
    root preexec = /etc/samba/scripts/autopoweruser.sh %U %m
    read only = Yes
    guest ok = Yes

    1. 
+

    Example 13.2. A Magic Netlogon Share
     
    [netlogon]
    comment = Netlogon Share
    path = /var/lib/samba/netlogon
    root preexec = /etc/samba/scripts/autopoweruser.sh %U %m
    read only = Yes
    guest ok = Yes

    1. 
 		Create the script shown in “Script to Auto-add Domain Users to Workstation Power Users Group” and locate it in
 		the directory /etc/samba/scripts, named as autopoweruser.sh.
-
-
-
+
+
+
 		
    2. 
 		Set the permissions on this script to permit it to be executed as part of the logon process:
 
      @@ -484,15 +484,15 @@ exit 0
 	in which case there is little justification for the use of this procedure. The key justification
 	for the use of this method is that it will guarantee that all users have appropriate rights on
 	the workstation.
-	
    UNIX and Windows User Management
    
-
-
+

    UNIX and Windows User Management

    + + Every Windows network user account must be translated to a UNIX/Linux user account. In actual fact, the only account information the UNIX/Linux Samba server needs is a UID. The UID is available either from a system (POSIX) account or from a pool (range) of UID numbers that is set aside for the purpose @@ -516,8 +516,8 @@ net rpc password <username> [<password>] -Uadmin_username%admin_pass

    The following demonstrates the addition of an account to the server FRODO: - - + + 

     root#  net rpc user add jacko -S FRODO -Uroot%not24get
 Added user jacko
@@ -528,24 +528,24 @@ Added user jacko
 root#  net rpc user password jacko f4sth0rse \
     -S FRODO -Uroot%not24get

    -

    Deletion of User Accounts

    +

    Deletion of User Accounts

    Deletion of a user account can be done using the following syntax: 

     net [<method>] user DELETE <name> [misc. options] [targets]

    The following command will delete the user account jacko: - + 

     root#  net rpc user delete jacko -Uroot%not24get
 Deleted user account

    -

    Managing User Accounts

    +

    Managing User Accounts

    Two basic user account operations are routinely used: change of password and querying which groups a user is a member of. The change of password operation is shown in “Adding User Accounts”.

    The ability to query Windows group membership can be essential. Here is how a remote server may be interrogated to find which groups a user is a member of: - + 

     root#  net rpc user info jacko -S SAURON -Uroot%not24get
 net rpc user info jacko -S SAURON -Uroot%not24get
@@ -558,14 +558,14 @@ Emergency Services

    It is also possible to rename user accounts: -oldusername newusername +oldusername newusername Note that this operation does not yet work against Samba Servers. It is, however, possible to rename useraccounts on Windows Servers. -

    User Mapping

    - - +

    User Mapping

    + + In some situations it is unavoidable that a user's Windows logon name will differ from the login ID that user has on the Samba server. It is possible to create a special file on the Samba server that will permit the Windows user name to be mapped to a different UNIX/Linux user name. The smb.conf @@ -581,22 +581,22 @@ marygee: geeringm In this example the Windows user account “William Parsons” will be mapped to the UNIX user parsonsw, and the Windows user account “geeringm” will be mapped to the UNIX user marygee. -

    Administering User Rights and Privileges

    - - +

    Administering User Rights and Privileges

    + + With all versions of Samba earlier than 3.0.11 the only account on a Samba server that could manage users, groups, shares, printers, and such was the root account. This caused problems for some users and was a frequent source of scorn over the necessity to hand out the credentials for the most security-sensitive account on a UNIX/Linux system.

    - - + + New to Samba version 3.0.11 is the ability to delegate administrative privileges as necessary to either a normal user or to groups of users. The significance of the administrative privileges is documented in “User Rights and Privileges”. Examples of use of the net for user rights and privilege @@ -632,15 +632,15 @@ No privileges assigned

    The net command can be used to obtain the currently supported capabilities for rights and privileges using this method: - - - + + + 

     root#  net rpc rights list -U root%not24get
      SeMachineAccountPrivilege  Add machines to domain
@@ -659,7 +659,7 @@ No privileges assigned
 	In this example, all rights are assigned to the Domain Admins group. This is a good
 	idea since members of this group are generally expected to be all-powerful. This assignment makes that
 	the reality:
-
+
 
     root#  net rpc rights grant "MIDEARTH\Domain Admins" \
     SeMachineAccountPrivilege SePrintOperatorPrivilege \
@@ -678,7 +678,7 @@ Successfully granted rights.
 
    
 	
    
 	The following step permits validation of the changes just made:
-
+
 
     root#  net rpc rights list accounts -U root%not24get
 MIDEARTH\jht
@@ -712,17 +712,17 @@ SeAddUsersPrivilege
 SeRemoteShutdownPrivilege
 SeDiskOperatorPrivilege
 
    
-

    Managing Trust Relationships

    +

    Managing Trust Relationships

    There are essentially two types of trust relationships: the first is between domain controllers and domain member machines (network clients), the second is between domains (called interdomain trusts). All Samba servers that participate in domain security require a domain membership trust account, as do like Windows NT/200x/XP workstations. -

    Machine Trust Accounts

    +

    Machine Trust Accounts

    The net command looks in the smb.conf file to obtain its own configuration settings. Thus, the following command 'knows' which domain to join from the smb.conf file.

    A Samba server domain trust account can be validated as shown in this example: - + 

     root#  net rpc testjoin
 Join to 'MIDEARTH' is OK
@@ -735,7 +735,7 @@ Join to domain 'WORLDOCEAN' is not valid

    The equivalent command for joining a Samba server to a Windows ADS domain is shown here: - + 

     root#  net ads testjoin
 Using short domain name -- TAKEAWAY
@@ -750,7 +750,7 @@ Join to domain is not valid
 	
    
 	The following demonstrates the process of creating a machine trust account in the target domain for the
 	Samba server from which the command is executed:
-
+
 
     root#  net rpc join -S FRODO -Uroot%not24get
 Joined domain MIDEARTH.
@@ -765,7 +765,7 @@ merlin$:1009:9B4489D6B90461FD6A3EC3AB96147E16:\
 	The S in the square brackets means this is a server (PDC/BDC) account. The domain join can be cast to join
 	purely as a workstation, in which case the S is replaced with a W (indicating a workstation account). The
 	following command can be used to affect this:
-
+
 
     root#  net rpc join member -S FRODO -Uroot%not24get
 Joined domain MIDEARTH.
@@ -773,7 +773,7 @@ Joined domain MIDEARTH.
 	Note that the command-line parameter member makes this join specific. By default
 	the type is deduced from the smb.conf file configuration. To specifically join as a PDC or BDC, the
 	command-line parameter will be [PDC | BDC]. For example:
-
+
 
     root#  net rpc join bdc -S FRODO -Uroot%not24get
 Joined domain MIDEARTH.
@@ -781,7 +781,7 @@ Joined domain MIDEARTH.
 	It is best to let Samba figure out the domain join type from the settings in the smb.conf file.
 	
    
 	The command to join a Samba server to a Windows ADS domain is shown here:
-
+
 
     root#  net ads join -UAdministrator%not24get
 Using short domain name -- GDANSK
@@ -792,7 +792,7 @@ Joined 'FRANDIMITZ' to realm 'GDANSK.ABMAS.BIZ'
 	Windows machine is withdrawn from the domain, the domain membership account is not automatically removed
 	either. Inactive domain member accounts can be removed using any convenient tool. If necessary, the
 	machine account can be removed using the following net command:
-
+
 
     root#  net rpc user delete HERRING\$ -Uroot%not24get
 Deleted user account.
@@ -802,26 +802,26 @@ Deleted user account.
 	
    
 	A Samba-3 server that is a Windows ADS domain member can execute the following command to detach from the
 	domain:
-
+
 
     root#  net ads leave
 
    
 	
    
 	Detailed information regarding an ADS domain can be obtained by a Samba DMS machine by executing the
 	following:
-
+
 
     root#  net ads status
 
    
 	The volume of information is extensive. Please refer to the book “Samba-3 by Example”,
 	Chapter 7 for more information regarding its use. This book may be obtained either in print or online from
 	the Samba-3 by Example.
-

    Interdomain Trusts

    +

    Interdomain Trusts

    Interdomain trust relationships form the primary mechanism by which users from one domain can be granted access rights and privileges in another domain.

    To discover what trust relationships are in effect, execute this command: - + 

     root#  net rpc trustdom list -Uroot%not24get
 Trusted domains list:
@@ -837,7 +837,7 @@ none
 	It is necessary to create a trust account in the local domain. A domain controller in a second domain can
 	create a trusted connection with this account. That means that the foreign domain is being trusted
 	to access resources in the local domain. This command creates the local trust account:
-
+
 
     root#  net rpc trustdom add DAMNATION f00db4r -Uroot%not24get
 
    
@@ -850,7 +850,7 @@ DAMNATION$:1016:9AC1F121DF897688AAD3B435B51404EE: \
 	A trust account will always have an I in the field within the square brackets.
 	
    
 	If the trusting domain is not capable of being reached, the following command will fail:
-
+
 
     root#  net rpc trustdom list -Uroot%not24get
 Trusted domains list:
@@ -876,7 +876,7 @@ DAMNATION           domain controller is not responding
 	Where a trust account has been created on a foreign domain, Samba is able to establish the trust (connect with)
 	the foreign account. In the process it creates a one-way trust to the resources on the remote domain. This
 	command achieves the objective of joining the trust relationship:
-
+
 
     root#  net rpc trustdom establish DAMNATION
 Password: xxxxxxx	== f00db4r
@@ -897,7 +897,7 @@ DAMNATION           S-1-5-21-1385457007-882775198-1210191635
 	
    
 	Sometimes it is necessary to remove the ability for local users to access a foreign domain. The trusting
 	connection can be revoked as shown here:
-
+
 
     root#  net rpc trustdom revoke DAMNATION -Uroot%not24get
 
    
@@ -907,21 +907,21 @@ DAMNATION           S-1-5-21-1385457007-882775198-1210191635
 root#  net rpc trustdom del DAMNATION -Uroot%not24get
 
    
 
-

    Managing Security Identifiers (SIDS)

    - - - - - +

    Managing Security Identifiers (SIDS)

    + + + + + The basic security identifier that is used by all Windows networking operations is the Windows security identifier (SID). All Windows network machines (servers and workstations), users, and groups are identified by their respective SID. All desktop profiles are also encoded with user and group SIDs that are specific to the SID of the domain to which the user belongs.

    - - - - + + + + It is truly prudent to store the machine and/or domain SID in a file for safekeeping. Why? Because a change in hostname or in the domain (workgroup) name may result in a change in the SID. When you have the SID on hand, it is a simple matter to restore it. The alternative is to suffer the pain of @@ -929,7 +929,7 @@ DAMNATION S-1-5-21-1385457007-882775198-1210191635

    First, do not forget to store the local SID in a file. It is a good idea to put this in the directory in which the smb.conf file is also stored. Here is a simple action to achieve this: - + 

     root#  net getlocalsid > /etc/samba/my-sid

    @@ -945,7 +945,7 @@ SID for domain MERLIN is: S-1-5-21-726309263-4128913605-1168186429 If ever it becomes necessary to restore the SID that has been stored in the my-sid file, simply copy the SID (the string of characters that begins with S-1-5-21) to the command line shown here: - + 

     root#  net setlocalsid S-1-5-21-1385457007-882775198-1210191635

    @@ -956,7 +956,7 @@ SID for domain MERLIN is: S-1-5-21-726309263-4128913605-1168186429 DMS and workstation clients should have their own machine SID to avoid any potential namespace collision. Here is the way that the BDC SID can be synchronized to that of the PDC (this is the default NT4 domain practice also): - + 

     root#  net rpc getsid -S FRODO -Uroot%not24get
 Storing SID S-1-5-21-726309263-4128913605-1168186429 \
@@ -964,12 +964,12 @@ Storing SID S-1-5-21-726309263-4128913605-1168186429 \

    Usually it is not necessary to specify the target server (-S FRODO) or the administrator account credentials (-Uroot%not24get). -

    Share Management

    +

    Share Management

    Share management is central to all file serving operations. Typical share operations include:

    • Creation/change/deletion of shares

    • Setting/changing ACLs on shares

    • Moving shares from one server to another

    • Change of permissions of share contents

    Each of these are dealt with here insofar as they involve the use of the net command. Operations outside of this command are covered elsewhere in this document. -

    Creating, Editing, and Removing Shares

    +

    Creating, Editing, and Removing Shares

    A share can be added using the net rpc share command capabilities. The target machine may be local or remote and is specified by the -S option. It must be noted that the addition and deletion of shares using this tool depends on the availability of a suitable @@ -982,7 +982,7 @@ Storing SID S-1-5-21-726309263-4128913605-1168186429 \ utility. In the first step a share called Bulge is added. The sharepoint within the file system is the directory /data. The command that can be executed to perform the addition of this share is shown here: - + 

     root#  net rpc share add Bulge=/data -S MERLIN -Uroot%not24get

    @@ -1003,7 +1003,7 @@ ADMIN$

    Often it is desirable also to permit a share to be removed using a command-line tool. The following step permits the share that was previously added to be removed: - + 

     root#  net rpc share delete Bulge -S MERLIN -Uroot%not24get

    @@ -1019,15 +1019,15 @@ IPC$ ADMIN$ kyocera

    -

    Creating and Changing Share ACLs

    +

    Creating and Changing Share ACLs

    At this time the net tool cannot be used to manage ACLs on Samba shares. In MS Windows language this is called Share Permissions.

    It is possible to set ACLs on Samba shares using either the SRVTOOLS NT4 Domain Server Manager or using the Computer Management MMC snap-in. Neither is covered here, but see “File, Directory, and Share Access Controls”. -

    Share, Directory, and File Migration

    - +

    Share, Directory, and File Migration

    + Shares and files can be migrated in the same manner as user, machine, and group accounts. It is possible to preserve access control settings (ACLs) as well as security settings throughout the migration process. The net rpc vampire facility is used @@ -1064,7 +1064,7 @@ kyocera

  • Printer settings may not be fully or may be incorrectly migrated. This might in particular happen when migrating a Windows 2003 print server to Samba. -

    • Share Migration

    +

    Share Migration

    The net rpc share migrate command operation permits the migration of plain share stanzas. A stanza contains the parameters within which a file or print share are defined. The use of this migration method will create share stanzas that have as parameters the file @@ -1091,7 +1091,7 @@ net rpc share MIGRATE SHARES <share-name> -S <source> When the parameter <share-name> is omitted, all shares will be migrated. The potentially large list of available shares on the system that is being migrated can be limited using the --exclude switch. For example: - + 

     root#  net rpc share migrate shares myshare\
          -S win2k -U administrator%secret"
@@ -1104,13 +1104,13 @@ net rpc share MIGRATE SHARES <share-name> -S <source>
 	identical on both systems. One precaution worth taking before commencement of migration of shares is
 	to validate that the migrated accounts (on the Samba server) have the needed rights and privileges.
 	This can be done as shown here:
-
+
 
     root#  net rpc right list accounts -Uroot%not24get
 
    
 	The steps taken so far perform only the migration of shares. Directories and directory contents
 	are not migrated by the steps covered up to this point.
-

    File and Directory Migration

    +

    File and Directory Migration

    Everything covered to this point has been done in preparation for the migration of file and directory data. For many people preparation is potentially boring and the real excitement only begins when file data can be used. The next steps demonstrate the techniques that can be used to transfer (migrate) @@ -1161,7 +1161,7 @@ net rpc share MIGRATE FILES <share-name> -S <source>

    An example for migration of files from a machine called nt4box to the Samba server from which the process will be handled is shown here: - + 

     root#  net rpc share migrate files -S nt4box --acls \
     --attrs -U administrator%secret
@@ -1170,17 +1170,17 @@ net rpc share MIGRATE FILES <share-name> -S <source>
 	This command  will migrate all files and directories from all file shares on the Windows server called
 	nt4box to the Samba server from which migration is initiated. Files that are group-owned
 	will be owned by the user account administrator.
-

    Share-ACL Migration

    +

    Share-ACL Migration

    It is possible to have share-ACLs (security descriptors) that won't allow you, even as Administrator, to copy any files or directories into it. Therefor the migration of the share-ACLs has been put into a separate function: - + 

     root#  net rpc share migrate security -S nt4box -U administrator%secret

    This command will only copy the share-ACL of each share on nt4box to your local samba-system. -

    Simultaneous Share and File Migration

    +

    Simultaneous Share and File Migration

    The operating mode shown here is just a combination of the previous three. It first migrates share definitions and then all shared files and directories and finally migrates the share-ACLs: 

    @@ -1189,12 +1189,12 @@ net rpc share MIGRATE ALL <share-name> -S <source>

    An example of simultaneous migration is shown here: - + 

     root#  net rpc share migrate all -S w2k3server -U administrator%secret

    This will generate a complete server clone of the w2k3server server. -

    Printer Migration

    +

    Printer Migration

    The installation of a new server, as with the migration to a new network environment, often is similar to building a house; progress is very rapid from the laying of foundations up to the stage at which the house can be locked up, but the finishing off appears to take longer and longer as building @@ -1231,29 +1231,29 @@ net rpc share MIGRATE ALL <share-name> -S <source>

    Printer migration from a Windows print server (NT4 or 200x) is shown. This instruction causes the printer share to be created together with the underlying print queue: - + 

     net rpc printer MIGRATE PRINTERS [printer] [misc. options] [targets]

    Printer drivers can be migrated from the Windows print server to the Samba server using this command-line instruction: - + 

     net rpc printer MIGRATE DRIVERS [printer] [misc. options] [targets]

    Printer forms can be migrated with the following operation: - + 

     net rpc printer MIGRATE FORMS [printer] [misc. options] [targets]

    Printer security settings (ACLs) can be migrated from the Windows server to the Samba server using this command: - + 

     net rpc printer MIGRATE SECURITY [printer] [misc. options] [targets]

    Printer configuration settings include factors such as paper size and default paper orientation. These can be migrated from the Windows print server to the Samba server with this command: - + 

     net rpc printer MIGRATE SETTINGS [printer] [misc. options] [targets]

    @@ -1263,14 +1263,14 @@ net rpc printer MIGRATE SETTINGS [printer] [misc. options] [targets] 

     net rpc printer MIGRATE ALL [printer] [misc. options] [targets]

    -

    Controlling Open Files

    +

    Controlling Open Files

    The man page documents the net file function suite, which provides the tools to close open files using either RAP or RPC function calls. Please refer to the man page for specific usage information. -

    Session and Connection Management

    +

    Session and Connection Management

    The session management interface of the net session command uses the old RAP method to obtain the list of connections to the Samba server, as shown here: - + 

     root#  net rap session -S MERLIN -Uroot%not24get
 Computer             User name            Client Type        Opens Idle time
@@ -1285,11 +1285,11 @@ Computer             User name            Client Type        Opens Idle time
 
     root#  net rap session close marvel -Uroot%not24get
 
    
-

    Printers and ADS

    +

    Printers and ADS

    When Samba-3 is used within an MS Windows ADS environment, printers shared via Samba will not be browseable until they have been published to the ADS domain. Information regarding published printers may be obtained from the ADS server by executing the net ads print info command following this syntax: - + 

     net ads printer info <printer_name> <server_name> -Uadministrator%secret

    @@ -1297,26 +1297,26 @@ net ads printer info <printer_name> <server_name> -Uadministrator%se returned.

    To publish (make available) a printer to ADS, execute the following command: - + 

     net ads printer publish <printer_name> -Uadministrator%secret

    This publishes a printer from the local Samba server to ADS.

    Removal of a Samba printer from ADS is achieved by executing this command: - + 

     net ads printer remove <printer_name> -Uadministrator%secret

    A generic search (query) can also be made to locate a printer across the entire ADS domain by executing: - + 

     net ads printer search <printer_name> -Uadministrator%secret

    -

    Manipulating the Samba Cache

    +

    Manipulating the Samba Cache

    Please refer to the net command man page for information regarding cache management. -

    Managing IDMAP UID/SID Mappings

    +

    Managing IDMAP UID/SID Mappings

    The IDMAP UID to SID, and SID to UID, mappings that are created by winbindd can be backed up to a text file. The text file can be manually edited, although it is highly recommended that you attempt this only if you know precisely what you are doing. @@ -1327,7 +1327,7 @@ net ads printer search <printer_name> -Uadministrator%secret

    Winbind must be shut down to dump the IDMAP file. Before restoring a dump file, shut down winbindd and delete the old winbindd_idmap.tdb file. -

    Creating an IDMAP Database Dump File

    +

    Creating an IDMAP Database Dump File

    The IDMAP database can be dumped to a text file as shown here: 

     net idmap dump <full_path_and_tdb_filename> > dumpfile.txt
@@ -1337,7 +1337,7 @@ net idmap dump <full_path_and_tdb_filename> > dumpfile.txt
 
     net idmap dump /var/lib/samba/winbindd_idmap.tdb > idmap_dump.txt
 
    
-

    Restoring the IDMAP Database Dump File

    +

    Restoring the IDMAP Database Dump File

    The IDMAP dump file can be restored using the following command: 

     net idmap restore <full_path_and_tdb_filename> < dumpfile.txt
@@ -1350,7 +1350,7 @@ net idmap restore /var/lib/samba/winbindd_idmap.tdb < idmap_dump.txt

    Other Miscellaneous Operations

    The following command is useful for obtaining basic statistics regarding a Samba domain. This command does not work with current Windows XP Professional clients. - + 

     root#  net rpc info
 Domain Name: RAPIDFLY
@@ -1363,7 +1363,7 @@ Num local groups: 6
 	
    
 	Another useful tool is the net time tool set. This tool may be used to query the
 	current time on the target server as shown here:
-
+
 
     root#  net time -S SAURON
 Tue May 17 00:50:43 2005
@@ -1371,19 +1371,19 @@ Tue May 17 00:50:43 2005
 	In the event that it is the intent to pass the time information obtained to the UNIX
 	/bin/time, it is a good idea to obtain the time from the target server in a format
 	that is ready to be passed through. This may be done by executing:
-
+
 
     root#  net time system -S FRODO
 051700532005.16
 
    
 	The time can be set on a target server by executing:
-
+
 
     root#  net time set -S MAGGOT -U Administrator%not24get
 Tue May 17 00:55:30 MDT 2005
 
    
 	It is possible to obtain the time zone of a server by executing the following command against it:
-
+
 
     root#  net time zone -S SAURON
 -0600
diff --git a/docs/htmldocs/Samba3-HOWTO/NetworkBrowsing.html b/docs/htmldocs/Samba3-HOWTO/NetworkBrowsing.html
index b62bad110f..0d23033a3d 100644
--- a/docs/htmldocs/Samba3-HOWTO/NetworkBrowsing.html
+++ b/docs/htmldocs/Samba3-HOWTO/NetworkBrowsing.html
@@ -1,36 +1,36 @@
-Chapter 10. Network Browsing
    Chapter 10. Network Browsing
    Prev Part III. Advanced Configuration Next
    Chapter 10. Network Browsing
    John H. Terpstra
    Samba Team
    Jelmer R. Vernooij
    The Samba Team
    Jonathan Johnson
    Sutinen Consulting, Inc.
    July 5, 1998
    Updated: September 20, 2006
    Table of Contents
    Features and Benefits
    What Is Browsing?
    Discussion
    NetBIOS over TCP/IP
    TCP/IP without NetBIOS
    DNS and Active Directory
    How Browsing Functions
    Configuring Workgroup Browsing
    Domain Browsing Configuration
    Forcing Samba to Be the Master
    Making Samba the Domain Master
    Note about Broadcast Addresses
    Multiple Interfaces
    Use of the Remote Announce Parameter
    Use of the Remote Browse Sync Parameter
    WINS: The Windows Internetworking Name Server
    WINS Server Configuration
    WINS Replication
    Static WINS Entries
    Helpful Hints
    Windows Networking Protocols
    Name Resolution Order
    Technical Overview of Browsing
    Browsing Support in Samba
    Problem Resolution
    Cross-Subnet Browsing
    Common Errors
    Flushing the Samba NetBIOS Name Cache
    Server Resources Cannot Be Listed
    I Get an "Unable to browse the network" Error
    Browsing of Shares and Directories is Very Slow
    Invalid Cached Share References Affects Network Browsing
    
-
-
-
-
+Chapter 10. Network Browsing
    Chapter 10. Network Browsing
    Prev Part III. Advanced Configuration Next
    Chapter 10. Network Browsing
    John H. Terpstra
    Samba Team
    Jelmer R. Vernooij
    The Samba Team
    Jonathan Johnson
    Sutinen Consulting, Inc.
    July 5, 1998
    Updated: September 20, 2006
    Table of Contents
    Features and Benefits
    What Is Browsing?
    Discussion
    NetBIOS over TCP/IP
    TCP/IP without NetBIOS
    DNS and Active Directory
    How Browsing Functions
    Configuring Workgroup Browsing
    Domain Browsing Configuration
    Forcing Samba to Be the Master
    Making Samba the Domain Master
    Note about Broadcast Addresses
    Multiple Interfaces
    Use of the Remote Announce Parameter
    Use of the Remote Browse Sync Parameter
    WINS: The Windows Internetworking Name Server
    WINS Server Configuration
    WINS Replication
    Static WINS Entries
    Helpful Hints
    Windows Networking Protocols
    Name Resolution Order
    Technical Overview of Browsing
    Browsing Support in Samba
    Problem Resolution
    Cross-Subnet Browsing
    Common Errors
    Flushing the Samba NetBIOS Name Cache
    Server Resources Cannot Be Listed
    I Get an "Unable to browse the network" Error
    Browsing of Shares and Directories is Very Slow
    Invalid Cached Share References Affects Network Browsing
    
+
+
+
+
 This chapter contains detailed information as well as a fast-track guide to
 implementing browsing across subnets and/or across workgroups (or domains).
 WINS is the best tool for resolution of NetBIOS names to IP addresses; however, WINS is
 not involved in browse list handling except by way of name-to-address resolution.
 
    Note
    
-
+
 What is WINS?
 
    
 WINS is a facility that provides resolution of a NetBIOS name to its IP address. WINS is like a
 Dynamic-DNS service for NetBIOS networking names.
 
    Note
    
-
-
-
-
+
+
+
+
 MS Windows 2000 and later versions can be configured to operate with no NetBIOS
 over TCP/IP. Samba-3 and later versions also support this mode of operation.
 When the use of NetBIOS over TCP/IP has been disabled, the primary
 means for resolution of MS Windows machine names is via DNS and Active Directory.
 The following information assumes that your site is running NetBIOS over TCP/IP.
-
    Features and Benefits
    
+
    Features and Benefits
    
 Charles Dickens once referred to the past in these words: “It was the best of times,
 it was the worst of times.” The more we look back, the more we long for what was and
 hope it never returns.
 
    
-
-
-
+
+
+
 For many MS Windows network administrators, that statement sums up their feelings about
 NetBIOS networking precisely. For those who mastered NetBIOS networking, its fickle
 nature was just par for the course. For those who never quite managed to tame its
@@ -43,40 +43,40 @@ thousands of seeds per square meter, a seed longevity of more than 7 years, and
 ability to germinate at any time of year, given the right conditions, are some of the
 features that make it such a persistent weed.
 
    
-
-
-
-
-
+
+
+
+
+
 In this chapter we explore vital aspects of Server Message Block (SMB) networking with
 a particular focus on SMB as implemented through running NetBIOS (Network Basic
 Input/Output System) over TCP/IP. Since Samba does not implement SMB or NetBIOS over
 any other protocols, we need to know how to configure our network environment and simply
 remember to use nothing but TCP/IP on all our MS Windows network clients.
 
    
-
-
+
+
 Samba provides the ability to implement a WINS (Windows Internetworking Name Server)
 and implements extensions to Microsoft's implementation of WINS. These extensions
 help Samba to effect stable WINS operations beyond the normal scope of MS WINS.
 
    
-
-
-
+
+
+
 WINS is exclusively a service that applies only to those systems
 that run NetBIOS over TCP/IP. MS Windows 200x/XP have the capacity to operate with
 support for NetBIOS disabled, in which case WINS is of no relevance. Samba supports this also.
 
    
-
-
-
+
+
+
 For those networks on which NetBIOS has been disabled (i.e., WINS is not required),
 the use of DNS is necessary for hostname resolution.
-
    What Is Browsing?
    
-
-
-
-
+
    What Is Browsing?
    
+
+
+
+
 To most people, browsing means they can see the MS Windows and Samba servers
 in the Network Neighborhood, and when the computer icon for a particular server is
 clicked, it opens up and shows the shares and printers available on the target server.
@@ -84,9 +84,9 @@ clicked, it opens up and shows the shares and printers available on the target s
 What seems so simple is in fact a complex interaction of different technologies.
 The technologies (or methods) employed in making all of this work include:
 
    • MS Windows machines register their presence to the network.
    • Machines announce themselves to other machines on the network.
    • One or more machines on the network collate the local announcements.
    • The client machine finds the machine that has the collated list of machines.
    • The client machine is able to resolve the machine names to IP addresses.
    • The client machine is able to connect to a target machine.
    
-
-
-
+
+
+
 The Samba application that controls browse list management and name resolution is
 called nmbd. The configuration parameters involved in nmbd's operation are:
 
    
@@ -99,33 +99,33 @@ WINS options:
 Those marked with an (*) are the only options that commonly may need to be modified. Even if none of these
 parameters is set, nmbd will still do its job.
 
    
-
-
-
-
-
+
+
+
+
+
 For Samba, the WINS Server and WINS Support are mutually exclusive options. When nmbd is
 started it will fail to execute if both options are set in the smb.conf file. The nmbd
 understands that when it spawns an instance of itself to run as a WINS server that it has to use its own WINS
 server also.
 
    Discussion
    
-
-
-
-
+
+
+
+
 All MS Windows networking uses SMB-based messaging.  SMB messaging may be implemented with or without NetBIOS.
 MS Windows 200x supports NetBIOS over TCP/IP for backwards compatibility. Microsoft appears intent on phasing
 out NetBIOS support.
-
    NetBIOS over TCP/IP
    
-
-
-
-
+
    NetBIOS over TCP/IP
    
+
+
+
+
 Samba implements NetBIOS, as does MS Windows NT/200x/XP, by encapsulating it over TCP/IP.
 NetBIOS-based networking uses broadcast messaging to effect browse list management. When running NetBIOS over
 TCP/IP, this uses UDP-based messaging.  UDP messages can be broadcast or unicast.
 
    
-
+
 Normally, only unicast UDP messaging can be forwarded by routers. The remote announce
 parameter to smb.conf helps to project browse announcements to remote network segments via unicast UDP.
 Similarly, the remote browse sync parameter of smb.conf implements browse list
@@ -133,54 +133,54 @@ collation using unicast UDP.
 
    
 The methods used by MS Windows to perform name lookup requests (name resolution) is determined by a
 configuration parameter called the NetBIOS node-type. There are four basic NetBIOS node types:
-
    • b-node (type 0x01): The Windows client will use only
+
      • b-node (type 0x01): The Windows client will use only
 	NetBIOS broadcast requests using UDP broadcast.
      • p-node (type 0x02): The Windows client will use point-to-point
 	(NetBIOS unicast) requests using UDP unicast directed to a WINS server.
      • m-node (type 0x04): The Windows client will first use
 	NetBIOS broadcast requests using UDP broadcast, then it will use (NetBIOS unicast)
 	requests using UDP unicast directed to a WINS server.
      • h-node (type 0x08): The Windows client will use
 	(NetBIOS unicast) requests using UDP unicast directed to a WINS server, then it will use
 	NetBIOS broadcast requests using UDP broadcast.
      
-
-
-
-
-
-
+
+
+
+
+
+
 The default Windows network client (or server) network configuration enables NetBIOS over TCP/IP
 and b-node configuration. The use of WINS makes most sense with h-node (hybrid mode) operation so that
 in the event of a WINS breakdown or non-availability, the client can use broadcast-based name resolution.
 
      
-
-
-
-
-
-
-
+
+
+
+
+
+
+
 In those networks where Samba is the only SMB server technology, wherever possible nmbd
 should be configured on one machine as the WINS server. This makes it easy to manage the browsing environment.
 If each network segment is configured with its own Samba WINS server, then the only way to get cross-segment
 browsing to work is by using the remote announce and the remote browse sync parameters to your smb.conf file.
 
      
-
+
 If only one WINS server is used for an entire multisegment network, then
 the use of the remote announce and the
 remote browse sync parameters should not be necessary.
 
      
-
+
 As of Samba-3, WINS replication is being worked on. The bulk of the code has been committed, but it still
 needs maturation. This is not a supported feature of the Samba-3.0.20 release. Hopefully, this will become a
 supported feature of one of the Samba-3 release series. The delay is caused by the fact that this feature has
 not been of sufficient significance to inspire someone to pay a developer to complete it.
 
      
-
-
-
-
-
-
-
-
+
+
+
+
+
+
+
+
 Right now Samba WINS does not support MS-WINS replication. This means that when setting up Samba as a WINS
 server, there must only be one nmbd configured as a WINS server on the network. Some
 sites have used multiple Samba WINS servers for redundancy (one server per subnet) and then used
@@ -194,15 +194,15 @@ based networking is a life of compromise and trade-offs. WINS stores information
 DNS; consequently, DNS is a poor substitute for WINS given that when NetBIOS over TCP/IP is used, Windows
 clients are designed to use WINS.
 
      
-
-
-
+
+
+
 Lastly, take note that browse lists are a collection of unreliable broadcast
 messages that are repeated at intervals of not more than 15 minutes. This means
 that it will take time to establish a browse list, and it can take up to 45
 minutes to stabilize, particularly across network segments.
 
      
-
+
 When an MS Windows 200x/XP system attempts to resolve a host name to an IP address, it follows a defined path:
 
      1. 
 	Checks the hosts file. It is located in %SystemRoot%\System32\Drivers\etc.
@@ -217,46 +217,46 @@ When an MS Windows 200x/XP system attempts to resolve a host name to an IP addre
 	
      2. 
 	Looks up entries in LMHOSTS, located in %SystemRoot%\System32\Drivers\etc.
 	
      
-
-
-
-
+
+
+
+
 Given the nature of how the NetBIOS over TCP/IP protocol is implemented, only WINS is capable of resolving
 with any reliability name lookups for service-oriented names such as TEMPTATION<1C>  a NetBIOS
 name query that seeks to find network logon servers. DNS has no concept of service-oriented names such as
 this. In fact, the Microsoft ADS implementation specifically manages a whole range of extended
 service-oriented DNS entries. This type of facility is not implemented and is not supported for the NetBIOS
 over TCP/IP protocol namespace.
-
    TCP/IP without NetBIOS
    
-
-
-
+
    TCP/IP without NetBIOS
    
+
+
+
 All TCP/IP-enabled systems use various forms of hostname resolution. The primary
 methods for TCP/IP hostname resolution involve either a static file (/etc/hosts)
 or the Domain Name System (DNS). DNS is the technology that makes
 the Internet usable. DNS-based hostname resolution is supported by nearly all
 TCP/IP-enabled systems. Only a few embedded TCP/IP systems do not support DNS.
 
    
-
-
-
-
+
+
+
+
 Windows 200x/XP can register its hostname with a Dynamic DNS server (DDNS). It is possible to force register with a
 dynamic DNS server in Windows 200x/XP using ipconfig /registerdns.
 
    
-
-
-
+
+
+
 With Active Directory, a correctly functioning DNS server is absolutely essential. In the absence of a working
 DNS server that has been correctly configured, MS Windows clients and servers will be unable to locate each
 other, so network services consequently will be severely impaired.
 
    
-
-
-
-
-
-
+
+
+
+
+
+
 Use of raw SMB over TCP/IP (No NetBIOS layer) can be done only with Active Directory domains. Samba is not an
 Active Directory domain controller: ergo, it is not possible to run Samba as a domain controller and at the same
 time not use NetBIOS. Where Samba is used as an Active Directory domain member server
@@ -265,11 +265,11 @@ an Active Directory domain, however, if NetBIOS over TCP/IP is disabled, it is n
 appropriate DNS entries for the Samba DMS because they will not be automatically generated either by Samba, or
 by the ADS environment.
 
    DNS and Active Directory
    
-
-
-
-
-
+
+
+
+
+
 Occasionally we hear from UNIX network administrators who want to use a UNIX-based DDNS server in place
 of the Microsoft DNS server. While this might be desirable to some, the MS Windows 200x DNS server is
 autoconfigured to work with Active Directory. It is possible to use BIND version 8 or 9, but it will almost
@@ -277,9 +277,9 @@ certainly be necessary to create service records (SRV records) so MS Active Dire
 hostnames to locate essential network services.  The following are some of the default service records that
 Active Directory requires:
 
    
-
-
-
+
+
+
 The use of DDNS is highly recommended with Active Directory, in which case the use of BIND9 is preferred for
 its ability to adequately support the SRV (service) records that are needed for Active Directory. Of course,
 when running ADS, it makes sense to use Microsoft's own DDNS server because of the natural affinity between ADS
@@ -370,40 +370,40 @@ noldor.quenya.org. 1200  IN      A       10.1.1.17
 ;; WHEN: Wed Oct  7 14:39:31 2004
 ;; MSG SIZE  rcvd: 171
 
    
-

    How Browsing Functions

    - - - - - +

    How Browsing Functions

    + + + + + MS Windows machines register their NetBIOS names (i.e., the machine name for each service type in operation) on startup. The exact method by which this name registration takes place is determined by whether or not the MS Windows client/server has been given a WINS server address, whether or not LMHOSTS lookup is enabled, whether or not DNS for NetBIOS name resolution is enabled, and so on.

    - - - + + + In the case where there is no WINS server, all name registrations as well as name lookups are done by UDP broadcast. This isolates name resolution to the local subnet, unless LMHOSTS is used to list all names and IP addresses. In such situations, Samba provides a means by which the Samba server name may be forcibly injected into the browse list of a remote MS Windows network (using the remote announce parameter).

    - - - + + + Where a WINS server is used, the MS Windows client will use UDP unicast to register with the WINS server. Such packets can be routed, and thus WINS allows name resolution to function across routed networks.

    - - - - - - + + + + + + During the startup process, an election takes place to create a local master browser (LMB) if one does not already exist. On each NetBIOS network one machine will be elected to function as the domain master browser (DMB). This domain browsing has nothing to do with MS security Domain Control. Instead, the DMB serves the @@ -413,14 +413,14 @@ way every master browser will eventually obtain a complete list of all machines the election criteria used, the machine with the highest uptime, or the most senior protocol version or other criteria, will win the election as DMB.

    - - - - - - - - + + + + + + + + Where a WINS server is used, the DMB registers its IP address with the WINS server using the name of the domain and the NetBIOS name type 1B (e.g., DOMAIN<1B>). All LMBs register their IP addresses with the WINS server, also with the name of the domain and the NetBIOS name type of 1D. The 1B name is unique to one @@ -428,20 +428,20 @@ server within the domain security context, and only one 1D name is registered fo Machines that have registered the 1D name will be authoritive browse list maintainers for the network segment they are on. The DMB is responsible for synchronizing the browse lists it obtains from the LMBs.

    - + Clients wishing to browse the network make use of this list but also depend on the availability of correct name resolution to the respective IP address or addresses.

    - + Any configuration that breaks name resolution and/or browsing intrinsics will annoy users because they will have to put up with protracted inability to use the network services.

    - - - - - - + + + + + + Samba supports a feature that allows forced synchronization of browse lists across routed networks using the remote browse sync parameter in the smb.conf file. This causes Samba to contact the LMB on a remote network and to request browse list synchronization. This effectively bridges two networks that @@ -451,12 +451,12 @@ browse list synchronization and that is distinct from name-to-address resolutio for cross-subnet browsing to function correctly, it is essential that a name-to-address resolution mechanism be provided. This mechanism could be via DNS, /etc/hosts, and so on.

    Configuring Workgroup Browsing

    - - - - - - + + + + + + To configure cross-subnet browsing on a network containing machines in a workgroup, not an NT domain, you need to set up one Samba server to be the DMB (note that this is not the same as a Primary Domain Controller, although in an NT domain the same machine plays both roles). The role of a DMB is to collate the browse lists @@ -464,72 +464,72 @@ from LMB on all the subnets that have a machine participating in the workgroup. as a DMB, each subnet would be an isolated workgroup unable to see any machines on another subnet. It is the presence of a DMB that makes cross-subnet browsing possible for a workgroup.

    - + In a workgroup environment the DMB must be a Samba server, and there must only be one DMB per workgroup name. To set up a Samba server as a DMB, set the following option in the [global] section of the smb.conf file:

    -

    domain master = yes

    +

    domain master = yes

    - - + + The DMB should preferably be the LMB for its own subnet. In order to achieve this, set the following options in the [global] section of the smb.conf file as shown in Domain Master Browser smb.conf -

    Example 10.1. Domain Master Browser smb.conf

    [global]
    domain master = yes
    local master = yes
    preferred master = yes
    os level = 65

    - - +

    Example 10.1. Domain Master Browser smb.conf

    [global]
    domain master = yes
    local master = yes
    preferred master = yes
    os level = 65

    + + The DMB may be the same machine as the WINS server, if necessary.

    - - - + + + Next, you should ensure that each of the subnets contains a machine that can act as an LMB for the workgroup. Any MS Windows NT/200x/XP machine should be able to do this, as will Windows 9x/Me machines (although these tend to get rebooted more often, so it is not such a good idea to use them). To make a Samba server an LMB, set the following options in the [global] section of the smb.conf file as shown in Local master browser smb.conf -

    Example 10.2. Local master browser smb.conf

    [global]
    domain master = no
    local master = yes
    preferred master = yes
    os level = 65

    - +

    Example 10.2. Local master browser smb.conf

    [global]
    domain master = no
    local master = yes
    preferred master = yes
    os level = 65

    + Do not do this for more than one Samba server on each subnet, or they will war with each other over which is to be the LMB.

    - - + + The local master parameter allows Samba to act as a LMB. The preferred master causes nmbd to force a browser election on startup and the os level parameter sets Samba high enough so it should win any browser elections.

    - + If you have an NT machine on the subnet that you wish to be the LMB, you can disable Samba from becoming an LMB by setting the following options in the [global] section of the smb.conf file as shown in smb.conf for Not Being a Master Browser.

    -

    Example 10.3. smb.conf for Not Being a Master Browser

    [global]
    domain master = no
    local master = no
    preferred master = no
    os level = 0


    -

    Domain Browsing Configuration

    - - - - +

    Example 10.3. smb.conf for Not Being a Master Browser

    [global]
    domain master = no
    local master = no
    preferred master = no
    os level = 0


    +

    Domain Browsing Configuration

    + + + + If you are adding Samba servers to a Windows NT domain, then you must not set up a Samba server as a DMB. By default, a Windows NT PDC for a domain is also the DMB for that domain. Network browsing may break if a Samba server other than the PDC registers the DMB NetBIOS name (DOMAIN<1B>) with WINS.

    - + For subnets other than the one containing the Windows NT PDC, you may set up Samba servers as LMBs as described. To make a Samba server a Local Master Browser, set the following options in the [global] section of the smb.conf file as shown in Local Master Browser smb.conf -

    Example 10.4. Local Master Browser smb.conf

    [global]
    domain master = no
    local master = yes
    preferred master = yes
    os level = 65

    - - +

    Example 10.4. Local Master Browser smb.conf

    [global]
    domain master = no
    local master = yes
    preferred master = yes
    os level = 65

    + + If you wish to have a Samba server fight the election with machines on the same subnet, you may set the os level parameter to lower levels. By doing this you can tune the order of machines that will become LMBs if they are running. For more details on this, refer to Forcing Samba to Be the Master.

    - - - + + + If you have Windows NT machines that are members of the domain on all subnets and you are sure they will always be running, you can disable Samba from taking part in browser elections and ever becoming an LMB by setting the following options in the [global] section of the smb.conf file as shown @@ -537,13 +537,13 @@ in

    Example 10.5. smb.conf for Not Being a master browser

    [global]domain master = nolocal master = nopreferred master = noos level = 0


    Forcing Samba to Be the Master

    - - - - - - - + + + + + + + Who becomes the master browser is determined by an election process using broadcasts. Each election packet contains a number of parameters that determine what precedence (bias) a host should have in the election. By default Samba uses a low precedence and thus loses elections to just about every Windows network server or @@ -557,10 +557,10 @@ An os level of two would make not MS Windows NT/200x Server. An MS Windows NT/200x Server domain controller uses level 32. The maximum os level is 255.

    - - - - + + + + If you want Samba to force an election on startup, set the preferred master global option in smb.conf to yes. Samba will then have a slight advantage over other potential master browsers that are not preferred master browsers. Use this parameter with care, because if @@ -568,34 +568,34 @@ you have two hosts (whether they are Windows 9x/Me or NT/200x/XP or Samba) on th with preferred master to yes, then periodically and continually they will force an election in order to become the LMB.

    - - - - - + + + + + If you want Samba to be a DMB, then it is recommended that you also set preferred master to yes, because Samba will not become a DMB for the whole of your LAN or WAN if it is not also a LMB on its own broadcast isolated subnet.

    - - - - - + + + + + It is possible to configure two Samba servers to attempt to become the DMB for a domain. The first server that comes up will be the DMB. All other Samba servers will attempt to become the DMB every 5 minutes. They will find that another Samba server is already the DMB and will fail. This provides automatic redundancy should the current DMB fail. The network bandwidth overhead of browser elections is relatively small, requiring approximately four UDP packets per machine per election. The maximum size of a UDP packet is 576 bytes. -

    Making Samba the Domain Master

    - - - - +

    Making Samba the Domain Master

    + + + + The domain master browser is responsible for collating the browse lists of multiple subnets so browsing can occur between subnets. You can make Samba act as the domain master browser by setting domain master = yes in smb.conf. By default it will not be a domain master browser.

    - - + + Do not set Samba to be the domain master for a workgroup that has the same name as an NT/200x domain. If Samba is configured to be the domain master for a workgroup that is present on the same network as a Windows NT/200x domain that has the same name, network browsing problems will certainly be experienced. @@ -603,26 +603,26 @@ NT/200x domain that has the same name, network browsing problems will certainly When Samba is the domain master and the master browser, it will listen for master announcements (made roughly every 12 minutes) from LMBs on other subnets and then contact them to synchronize browse lists.

    - - + + If you want Samba to be the domain master, you should also set the os level high enough to make sure it wins elections, and set preferred master to yes, to get Samba to force an election on startup.

    - - + + All servers (including Samba) and clients should be using a WINS server to resolve NetBIOS names. If your clients are only using broadcasting to resolve NetBIOS names, then two things will occur:

    1. - - + + LMBs will be unable to find a DMB because they will be looking only on the local subnet.

    2. - + If a client happens to get hold of a domain-wide browse list and a user attempts to access a host in that list, it will be unable to resolve the NetBIOS name of that host.

    - + If, however, both Samba and your clients are using a WINS server, then:

    1. LMBs will contact the WINS server and, as long as Samba has registered that it is a DMB with the WINS @@ -631,44 +631,44 @@ If, however, both Samba and your clients are using a WINS server, then: When a client receives a domain-wide browse list and a user attempts to access a host in that list, it will contact the WINS server to resolve the NetBIOS name of that host. As long as that host has registered its NetBIOS name with the same WINS server, the user will be able to see that host.. -

    Note about Broadcast Addresses

    - +

    Note about Broadcast Addresses

    + If your network uses a zero-based broadcast address (for example, if it ends in a 0), then you will strike problems. Windows for Workgroups does not seem to support a zeros broadcast, and you will probably find that browsing and name lookups will not work. -

    Multiple Interfaces

    - +

    Multiple Interfaces

    + Samba supports machines with multiple network interfaces. If you have multiple interfaces, you will need to use the interfaces option in smb.conf to configure them. For example, the machine you are working with has 4 network interfaces; eth0, eth1, eth2, eth3 and only interfaces eth1 and eth4 should be used by Samba. In this case, the following smb.conf file entries would permit that intent: -

    interfaces = eth1, eth4
    bind interfaces only = Yes

    - - - - - - - +

    interfaces = eth1, eth4
    bind interfaces only = Yes

    + + + + + + + The bind interfaces only = Yes is necessary to exclude TCP/IP session services (ports 135, 139, and 445) over the interfaces that are not specified. Please be aware that nmbd will listen for incoming UDP port 137 packets on the unlisted interfaces, but it will not answer them. It will, however, send its broadcast packets over the unlisted interfaces. Total isolation of ethernet interface requires the use of a firewall to block ports 137 and 138 (UDP), and ports 135, 139, and 445 (TCP) on all network interfaces that must not be able to access the Samba server. -

    Use of the Remote Announce Parameter

    +

    Use of the Remote Announce Parameter

    The remote announce parameter of smb.conf can be used to forcibly ensure that all the NetBIOS names on a network get announced to a remote network. The syntax of the remote announce parameter is: -

    remote announce = 192.168.12.23 [172.16.21.255] ...

    +

    remote announce = 192.168.12.23 [172.16.21.255] ...

    or -

    remote announce = 192.168.12.23/MIDEARTH [172.16.21.255/ELVINDORF] ...

    +

    remote announce = 192.168.12.23/MIDEARTH [172.16.21.255/ELVINDORF] ...

    where:

    192.168.12.23 and 172.16.21.255

    - - + + is either the LMB IP address or the broadcast address of the remote network. That is, the LMB is at 192.168.1.23, or the address could be given as 172.16.21.255 where the netmask is assumed to be 24 bits (255.255.255.0). When the remote announcement is made to the broadcast @@ -678,24 +678,24 @@ where: workgroup name of the remote network, our NetBIOS machine names will end up looking like they belong to that workgroup. This may cause name resolution problems and should be avoided.

    -

    Use of the Remote Browse Sync Parameter

    - - +

    Use of the Remote Browse Sync Parameter

    + + The remote browse sync parameter of smb.conf is used to announce to another LMB that it must synchronize its NetBIOS name list with our Samba LMB. This works only if the Samba server that has this option is simultaneously the LMB on its network segment.

    The syntax of the remote browse sync parameter is: -

    - - +

    + + where 192.168.10.40 is either the IP address of the remote LMB or the network broadcast address of the remote segment. -

    WINS: The Windows Internetworking Name Server

    - - - +

    WINS: The Windows Internetworking Name Server

    + + + Use of WINS (either Samba WINS or MS Windows NT Server WINS) is highly recommended. Every NetBIOS machine registers its name together with a name_type value for each of several types of service it has available. @@ -704,18 +704,18 @@ It also registers its name if it is running the LanManager-compatible server service (used to make shares and printers available to other users) by registering the server (the type 0x20) name.

    - - + + All NetBIOS names are up to 15 characters in length. The name_type variable is added to the end of the name, thus creating a 16 character name. Any name that is shorter than 15 characters is padded with spaces to the 15th character. Thus, all NetBIOS names are 16 characters long (including the name_type information).

    - - - - + + + + WINS can store these 16-character names as they get registered. A client that wants to log onto the network can ask the WINS server for a list of all names that have registered the NetLogon service name_type. This saves @@ -725,21 +725,21 @@ information can only be provided via WINS or via a statically configured lmhosts file that must reside on all clients in the absence of WINS.

    - - - - - + + + + + WINS also forces browse list synchronization by all LMBs. LMBs must synchronize their browse list with the DMB, and WINS helps the LMB to identify its DMB. By definition this will work only within a single workgroup. Note that the DMB has nothing to do with what is referred to as an MS Windows NT domain. The latter is a reference to a security environment, while the DMB refers to the master controller for browse list information only.

    - - - - + + + + WINS will work correctly only if every client TCP/IP protocol stack is configured to use the WINS servers. Any client that is not configured to use the WINS server will continue to use only broadcast-based @@ -756,16 +756,16 @@ To configure Samba to register with a WINS server, just add

    Important

    Never use wins support = yes together with wins server = 10.0.0.18 particularly not using its own IP address. Specifying both will cause nmbd to refuse to start! -

    WINS Server Configuration

    - +

    WINS Server Configuration

    + Either a Samba server or a Windows NT server machine may be set up as a WINS server. To configure a Samba server to be a WINS server, you must add to the smb.conf file on the selected Server the following line to the [global] section:

    -

    wins support = yes

    +

    wins support = yes

    - + Versions of Samba prior to 1.9.17 had this parameter default to yes. If you have any older versions of Samba on your network, it is strongly suggested you upgrade to a recent version, or at the very @@ -774,14 +774,14 @@ least set the parameter to “no” on all th Machines configured with wins support = yes will keep a list of all NetBIOS names registered with them, acting as a DNS for NetBIOS names.

    - + It is strongly recommended to set up only one WINS server. Do not set the wins support = yes option on more than one Samba server on a network.

    - - - - - + + + + + To configure Windows NT/200x Server as a WINS server, install and configure the WINS service. See the Windows NT/200x documentation for details. Windows NT/200x WINS servers can replicate to each other, allowing more than one to be set up in a complex subnet environment. Because Microsoft refuses to document the replication @@ -789,14 +789,14 @@ protocols, Samba cannot currently participate in these replications. It is possi replication protocol may be defined in the future, in which case more than one Samba machine could be set up as a WINS server. Currently only one Samba server should have the wins support = yes parameter set.

    - - + + After the WINS server has been configured, you must ensure that all machines participating on the network are configured with the address of this WINS server. If your WINS server is a Samba machine, fill in the Samba machine IP address in the Primary WINS Server field of the Control Panel->Network->Protocols->TCP->WINS Server dialogs in Windows 9x/Me or Windows NT/200x. To tell a Samba server the IP address of the WINS server, add the following line to the [global] section of all smb.conf files: -

    wins server = <name or IP address>

    +

    wins server = <name or IP address>

    where <name or IP address> is either the DNS name of the WINS server machine or its IP address.

    @@ -806,18 +806,18 @@ server acting as the WINS server itself. If you set both the wins server = <name> option then nmbd will fail to start.

    - - - - + + + + There are two possible scenarios for setting up cross-subnet browsing. The first details setting up cross-subnet browsing on a network containing Windows 9x/Me, Samba, and Windows NT/200x machines that are not configured as part of a Windows NT domain. The second details setting up cross-subnet browsing on networks that contain NT domains. -

    WINS Replication

    - - +

    WINS Replication

    + + Samba-3 does not support native WINS replication. There was an approach to implement it, called wrepld, but it was never ready for action and the development is now discontinued.

    @@ -825,11 +825,11 @@ Meanwhile, there is a project named samba4WINS, wh run the Samba-4 WINS server parallel to Samba-3 since version 3.0.21. More information about samba4WINS are available at http://ftp.sernet.de/pub/samba4WINS. -

    Static WINS Entries

    - - - - +

    Static WINS Entries

    + + + + Adding static entries to your Samba WINS server is actually fairly easy. All you have to do is add a line to wins.dat, typically located in /usr/local/samba/var/locks or /var/run/samba.

    @@ -837,8 +837,8 @@ Entries in wins.dat take the form of: 

     "NAME#TYPE" TTL ADDRESS+ FLAGS

    - - + + where NAME is the NetBIOS name, TYPE is the NetBIOS type, TTL is the time-to-live as an absolute time in seconds, ADDRESS+ is one or more addresses corresponding to the registration, and FLAGS are the NetBIOS flags for the registration. @@ -856,47 +856,47 @@ To make a NetBIOS name static (permanent), simply set the TTL to 0, like this: "MADMAN#03" 0 192.168.1.2 66R

    - - - - - - - + + + + + + + The NetBIOS flags may be interpreted as additive hexadecimal values: 00 - Broadcast node registration, 20 - Peer node registration, 40 - Meta node registration, 60 - Hybrid node registration, 02 - Permanent name, 04 - Active name, 80 - Group name. The 'R' indicates this is a registration record. Thus 66R means: Hybrid node active and permanent NetBIOS name. These values may be found in the nameserv.h header file from the Samba source code repository. These are the values for the NB flags.

    - + Though this method works with early Samba-3 versions, there is a possibility that it may change in future versions if WINS replication is added. -

    Helpful Hints

    +

    Helpful Hints

    The following hints should be carefully considered because they are stumbling points for many new network administrators. -

    Windows Networking Protocols

    - - +

    Windows Networking Protocols

    + + A common cause of browsing problems results from the installation of more than one protocol on an MS Windows machine.

    Warning

    Do not use more than one protocol on MS Windows clients.

    - - + + Every NetBIOS machine takes part in a process of electing the LMB (and DMB) every 15 minutes. A set of election criteria is used to determine the order of precedence for winning this election process. A machine running Samba or Windows NT will be biased, so the most suitable machine will predictably win and thus retain its role.

    - - - - - - + + + + + + The election process is fought out, so to speak over every NetBIOS network interface. In the case of a Windows 9x/Me machine that has both TCP/IP and IPX installed and has NetBIOS enabled over both protocols, the election will be decided over both protocols. As often happens, if the Windows 9x/Me machine is @@ -904,8 +904,8 @@ the only one with both protocols, then the LMB may be won on the NetBIOS interfa Samba will then lose the LMB role because Windows 9x/Me will insist it knows who the LMB is. Samba will then cease to function as an LMB, and browse list operation on all TCP/IP-only machines will therefore fail.

    - - + + Windows 95, 98, 98se, and Me are referred to generically as Windows 9x/Me. The Windows NT4, 200x, and XP use common protocols. These are roughly referred to as the Windows NT family, but it should be recognized that 2000 and XP/2003 introduce new protocol extensions that cause them to behave differently from MS Windows NT4. @@ -913,31 +913,31 @@ Generally, where a server does not support the newer or extended protocol, these protocols.

    The safest rule of all to follow is: Use only one protocol! -

    Name Resolution Order

    - - +

    Name Resolution Order

    + + Resolution of NetBIOS names to IP addresses can take place using a number of methods. The only ones that can provide NetBIOS name_type information are:

    • WINS the best tool.

    • LMHOSTS static and hard to maintain.

    • Broadcast uses UDP and cannot resolve names across remote segments.

    Alternative means of name resolution include:

    • Static /etc/hosts hard to maintain and lacks name_type info.

    • DNS is a good choice but lacks essential NetBIOS name_type information.

    - - + + Many sites want to restrict DNS lookups and avoid broadcast name resolution traffic. The name resolve order parameter is of great help here. The syntax of the name resolve order parameter is: -

    name resolve order = wins lmhosts bcast host

    +

    name resolve order = wins lmhosts bcast host

    or -

    name resolve order = wins lmhosts (eliminates bcast and host)

    +

    name resolve order = wins lmhosts (eliminates bcast and host)

    The default is: -

    name resolve order = host lmhost wins bcast

    - +

    name resolve order = host lmhost wins bcast

    + where “host” refers to the native methods used by the UNIX system to implement the gethostbyname() function call. This is normally controlled by /etc/host.conf, /etc/nsswitch.conf and /etc/resolv.conf. -

    Technical Overview of Browsing

    - +

    Technical Overview of Browsing

    + SMB networking provides a mechanism by which clients can access a list of machines in a network called browse list. This list contains machines that are ready to offer file and/or print services @@ -947,48 +947,48 @@ list is heavily used by all SMB clients. Configuration of SMB browsing has been problematic for some Samba users, hence this document.

    - - - + + + MS Windows 2000 and later versions, as with Samba-3 and later versions, can be configured to not use NetBIOS over TCP/IP. When configured this way, it is imperative that name resolution (using DNS/LDAP/ADS) be correctly configured and operative. Browsing will not work if name resolution from SMB machine names to IP addresses does not function correctly.

    - - + + Where NetBIOS over TCP/IP is enabled, use of a WINS server is highly recommended to aid the resolution of NetBIOS (SMB) names to IP addresses. WINS allows remote segment clients to obtain NetBIOS name_type information that cannot be provided by any other means of name resolution. -

    Browsing Support in Samba

    - - - - +

    Browsing Support in Samba

    + + + + Samba facilitates browsing. The browsing is supported by nmbd and is also controlled by options in the smb.conf file. Samba can act as an LMB for a workgroup, and the ability to support domain logons and scripts is now available.

    - - - + + + Samba can also act as a DMB for a workgroup. This means that it will collate lists from LMBs into a wide-area network server list. In order for browse clients to resolve the names they may find in this list, it is recommended that both Samba and your clients use a WINS server.

    - + Do not set Samba to be the domain master for a workgroup that has the same name as an NT Domain. On each wide-area network, you must only ever have one DMB per workgroup, regardless of whether it is NT, Samba, or any other type of domain master that is providing this service.

    Note

    - - + + nmbd can be configured as a WINS server, but it is not necessary to specifically use Samba as your WINS server. MS Windows NT4, Server or Advanced Server 200x can be configured as @@ -997,40 +997,40 @@ a WAN, it is recommended that you use the Microsoft WINS server capabilities. In a Samba-only environment, it is recommended that you use one and only one Samba server as the WINS server.

    - + To get browsing to work, you need to run nmbd as usual, but must use the workgroup option in smb.conf to control what workgroup Samba becomes a part of.

    - + Samba also has a useful option for a Samba server to offer itself for browsing on another subnet. It is recommended that this option is used only for “unusual” purposes: announcements over the Internet, for example. See remote announce in the smb.conf man page. -

    Problem Resolution

    - - +

    Problem Resolution

    + + If something does not work, the log.nmbd file will help to track down the problem. Try a log level of 2 or 3 for finding problems. Also note that the current browse list usually gets stored in text form in a file called browse.dat.

    - - + + If it does not work, you should still be able to type the server name as \\SERVER in filemanager, then press enter, and filemanager should display the list of available shares.

    - - + + Some people find browsing fails because they do not have the global guest account set to a valid account. Remember that the IPC$ connection that lists the shares is done as guest and so you must have a valid guest account.

    Note

    - - - - - + + + + + The IPC$ share is used by all SMB/CIFS clients to obtain the list of resources that is available on the server. This is the source of the list of shares and printers when browsing an SMB/CIFS server (also Windows machines) using the Windows Explorer to browse resources through the Windows Network @@ -1038,10 +1038,10 @@ Neighborhood (also called My Network Places) through to a Windows server. At thi a connection to the \\server\IPC4 resource. Clicking on a share will then open up a connection to the \\server\share.

    - - - - + + + + MS Windows 2000 and later (as with Samba) can be configured to disallow anonymous (i.e., guest account) access to the IPC$ share. In that case, the MS Windows 2000/XP/2003 machine acting as an SMB/CIFS client will use the @@ -1049,22 +1049,22 @@ name of the currently logged-in user to query the IPC$ share. MS Windows 9x/Me clients are not able to do this and thus will not be able to browse server resources.

    - + The other big problem people have is that their broadcast address, netmask, or IP address is wrong (specified with the interfaces option in smb.conf) -

    Cross-Subnet Browsing

    - - +

    Cross-Subnet Browsing

    + + Since the release of Samba 1.9.17 (alpha1), Samba has supported the replication of browse lists across subnet boundaries. This section describes how to set this feature up in different settings.

    - - - - - - + + + + + + To see browse lists that span TCP/IP subnets (i.e., networks separated by routers that do not pass broadcast traffic), you must set up at least one WINS server. The WINS server acts as a DNS for NetBIOS names. This will allow NetBIOS name-to-IP address translation to be completed by a direct query of the WINS server. This is @@ -1076,33 +1076,33 @@ announce are designed to get around the natural limitations that pre propagation. The hacks are not a universal solution and they should not be used in place of WINS, they are considered last resort methods.

    - - - - + + + + Remember, for browsing across subnets to work correctly, all machines, be they Windows 95, Windows NT, or Samba servers, must have the IP address of a WINS server given to them by a DHCP server or by manual configuration: for Windows 9x/Me and Windows NT/200x/XP, this is in the TCP/IP Properties, under Network settings; for Samba, this is in the smb.conf file.

    - - - + + + It is possible to operate Samba-3 without NetBIOS over TCP/IP. If you do this, be warned that if used outside of MS ADS, this will forgo network browsing support. ADS permits network browsing support through DNS, providing appropriate DNS records are inserted for all Samba servers. -

    Behavior of Cross-Subnet Browsing

    - - +

    Behavior of Cross-Subnet Browsing

    + + Cross-subnet browsing is a complicated dance, containing multiple moving parts. It has taken Microsoft several years to get the code that correctly achieves this, and Samba lags behind in some areas. Samba is capable of cross-subnet browsing when configured correctly.

    Consider a network set up as in Cross-Subnet Browsing Example.

    Figure 10.1. Cross-Subnet Browsing Example.

    Cross-Subnet Browsing Example.

    - - - + + + This consists of three subnets (1, 2, 3) connected by two routers (R1, R2), which do not pass broadcasts. Subnet 1 has five machines on it, subnet 2 has four machines, and subnet 3 has four machines. Assume for the moment that all machines are configured to be in the same workgroup (for simplicity's sake). Machine N1_C on @@ -1110,9 +1110,9 @@ subnet 1 is configured as the DMB (i.e., it will collate the browse lists for th configured as a WINS server, and all the other machines are configured to register their NetBIOS names with it.

    - - - + + + As these machines are booted up, elections for master browsers take place on each of the three subnets. Assume that machine N1_C wins on subnet 1, N2_B wins on subnet 2, and N3_D wins on @@ -1120,19 +1120,19 @@ subnet 3. These machines are known as LMBs for their particular subnet. N1_C has an advantage in winning as the LMB on subnet 1 because it is set up as DMB.

    - - + + On each of the three networks, machines that are configured to offer sharing services will broadcast that they are offering these services. The LMB on each subnet will receive these broadcasts and keep a record of the fact that the machine is offering a service. This list of records is the basis of the browse list. For this case, assume that all the machines are configured to offer services, so all machines will be on the browse list.

    - - - - - + + + + + For each network, the LMB on that network is considered authoritative for all the names it receives via local broadcast. This is because a machine seen by the LMB @@ -1143,7 +1143,7 @@ the LMBs learn about when collating their browse lists have not been directly seen. These records are called non-authoritative.

    - + At this point the browse lists appear as shown in Browse Subnet Example 1 (these are the machines you would see in your network neighborhood if you looked in it on a particular network right now). @@ -1152,19 +1152,19 @@ right now).

    At this point all the subnets are separate, and no machine is seen across any of the subnets.

    - - - - + + + + Now examine subnet 2 in Browse Subnet Example 2. As soon as N2_B has become the LMB, it looks for a DMB with which to synchronize its browse list. It does this by querying the WINS server (N2_D) for the IP address associated with the NetBIOS name WORKGROUP<1B>. This name was registered by the DMB (N1_C) with the WINS server as soon as it was started.

    - - - - + + + + Once N2_B knows the address of the DMB, it tells it that is the LMB for subnet 2 by sending a MasterAnnouncement packet as a UDP port 138 packet. It then synchronizes with it by doing a NetServerEnum2 call. This tells the DMB to send it all the server names it knows @@ -1174,14 +1174,14 @@ lists look like those in

    Table 10.2. Browse Subnet Example 2

    SubnetBrowse MasterList
    Subnet1N1_CN1_A, N1_B, N1_C, N1_D, N1_E, N2_A(*), N2_B(*), N2_C(*), N2_D(*)
    Subnet2N2_BN2_A, N2_B, N2_C, N2_D, N1_A(*), N1_B(*), N1_C(*), N1_D(*), N1_E(*)
    Subnet3N3_DN3_A, N3_B, N3_C, N3_D

    - + Servers with an (*) after them are non-authoritative names.

    - + At this point users looking in their Network Neighborhood on subnets 1 or 2 will see all the servers on both; users on subnet 3 will still see only the servers on their own subnet.

    - + The same sequence of events that occurred for N2_B now occurs for the LMB on subnet 3 (N3_D). When it synchronizes browse lists with the DMB (N1_A) it gets both the server entries on subnet 1 and those on subnet 2. After N3_D has synchronized with N1_C and vica versa, the browse lists will appear as shown in Browse Subnet Example 3 @@ -1195,9 +1195,9 @@ At this point, users looking in their Network Neighborhood on subnets 1 or 3 will see all the servers on all subnets, while users on subnet 2 will still see only the servers on subnets 1 and 2, but not 3.

    - - - + + + Finally, the LMB for subnet 2 (N2_B) will sync again with the DMB (N1_C) and will receive the missing server entries. Finally, as when a steady state (if no machines @@ -1218,7 +1218,7 @@ steady-state operation.

    If either router R1 or R2 fails, the following will occur:

    1. - + Names of computers on each side of the inaccessible network fragments will be maintained for as long as 36 minutes in the Network Neighborhood lists. @@ -1226,26 +1226,26 @@ If either router R1 or R2 fails, the following will occur: Attempts to connect to these inaccessible computers will fail, but the names will not be removed from the Network Neighborhood lists.

    2. - - - + + + If one of the fragments is cut off from the WINS server, it will only be able to access servers on its local subnet using subnet-isolated broadcast NetBIOS name resolution. The effect is similar to that of losing access to a DNS server. -

    Common Errors

    - - +

    Common Errors

    + + Many questions are asked on the mailing lists regarding browsing. The majority of browsing problems originate from incorrect configuration of NetBIOS name resolution. Some are of particular note. -

    Flushing the Samba NetBIOS Name Cache

    +

    Flushing the Samba NetBIOS Name Cache

    How Can One Flush the Samba NetBIOS Name Cache without Restarting Samba?

    - - - - + + + + Samba's nmbd process controls all browse list handling. Under normal circumstances it is safe to restart nmbd. This will effectively flush the Samba NetBIOS name cache and cause it to be rebuilt. This does not make certain that a rogue machine name will not reappear @@ -1255,47 +1255,47 @@ want to clear a rogue machine from the list, every machine on the network must b shut down and restarted after all machines are down. Failing a complete restart, the only other thing you can do is wait until the entry times out and is then flushed from the list. This may take a long time on some networks (perhaps months). -

    Server Resources Cannot Be Listed

    “My Client Reports "‘This server is not configured to list shared resources."’”

    +

    Server Resources Cannot Be Listed

    “My Client Reports "‘This server is not configured to list shared resources."’”

    Your guest account is probably invalid for some reason. Samba uses the guest account for browsing in smbd. Check that your guest account is valid. -

    Also see guest account in the smb.conf man page.

    I Get an "Unable to browse the network" Error

    This error can have multiple causes: - +

    Also see guest account in the smb.conf man page.

    I Get an "Unable to browse the network" Error

    This error can have multiple causes: +

    • There is no LMB. Configure nmbd or any other machine to serve as LMB.

    • You cannot log onto the machine that is the LMB. Can you log on to it as a guest user?

    • There is no IP connectivity to the LMB. - Can you reach it by broadcast?

    Browsing of Shares and Directories is Very Slow

    “ - + Can you reach it by broadcast?

    Browsing of Shares and Directories is Very Slow

    “ + There are only two machines on a test network. One is a Samba server, the other a Windows XP machine. Authentication and logons work perfectly, but when I try to explore shares on the Samba server, the Windows XP client becomes unresponsive. Sometimes it does not respond for some minutes. Eventually, Windows Explorer will respond and displays files and directories without problem. ”

    “ - + But, the share is immediately available from a command shell (cmd, followed by exploration with DOS command. Is this a Samba problem, or is it a Windows problem? How can I solve this? ”

    Here are a few possibilities:

    Bad Networking Hardware

    - - - - - + + + + + Most common defective hardware problems center around low cost or defective hubs, routers, network interface controllers (NICs), and bad wiring. If one piece of hardware is defective, the whole network may suffer. Bad networking hardware can cause data corruption. Most bad networking hardware problems are accompanied by an increase in apparent network traffic, but not all.

    The Windows XP WebClient

    - + A number of sites have reported similar slow network browsing problems and found that when the WebClient service is turned off, the problem disappears. This is certainly something that should be explored because it is a simple solution if it works.

    Inconsistent WINS Configuration

    - - + + This type of problem is common when one client is configured to use a WINS server (that is a TCP/IP configuration setting) and there is no WINS server on the network. Alternatively, this will happen if there is a WINS server and Samba is not configured to use it. The use of @@ -1303,14 +1303,14 @@ Here are a few possibilities: of NetBIOS over TCP/IP is disabled on all clients, Samba should not be configured as a WINS server, nor should it be configured to use one.

    Incorrect DNS Configuration

    - - + + If use of NetBIOS over TCP/IP is disabled, Active Directory is in use and the DNS server has been incorrectly configured. For further information refer to DNS and Active Directory. -

    Invalid Cached Share References Affects Network Browsing

    - - +

    Invalid Cached Share References Affects Network Browsing

    + + Cached references on your MS Windows client (workstation or server) to shares or servers that no longer exist can cause MS Windows Explorer to appear unresponsive as it tries to connect to these shares. After a delay (can take a long time) it times out and browsing will appear to be mostly normal again. @@ -1328,7 +1328,7 @@ Removal of stale network links needs to be done on a per-user basis. Alternately shortcuts from the MS Windows Explorer in My Network Places just by right-clicking them and selecting Delete.

    - + Samba users have reported that these stale references negatively affect network browsing with Windows, Samba, and Novell servers. It is suspected to be a universal problem not directly related to the Samba server. Samba users may experience this more often due to Samba being somewhat viewed as an experimenter's diff --git a/docs/htmldocs/Samba3-HOWTO/Other-Clients.html b/docs/htmldocs/Samba3-HOWTO/Other-Clients.html index 9d8e6c1136..5628351c0c 100644 --- a/docs/htmldocs/Samba3-HOWTO/Other-Clients.html +++ b/docs/htmldocs/Samba3-HOWTO/Other-Clients.html @@ -1,17 +1,17 @@ -Chapter 43. Samba and Other CIFS Clients

    Chapter 43. Samba and Other CIFS Clients
    Prev Part VI. Reference Section Next

    Chapter 43. Samba and Other CIFS Clients

    Jelmer R. Vernooij

    The Samba Team

    John H. Terpstra

    Samba Team

    Dan Shearer

    Samba Team

    Jim McDonough

    OS/2 
    IBM

    5 Mar 2001

    Table of Contents

    Macintosh Clients
    OS2 Client
    Configuring OS/2 Warp Connect or OS/2 Warp 4
    Configuring Other Versions of OS/2
    Printer Driver Download for OS/2 Clients
    Windows for Workgroups
    Latest TCP/IP Stack from Microsoft
    Delete .pwl Files After Password Change
    Configuring Windows for Workgroups Password Handling
    Password Case Sensitivity
    Use TCP/IP as Default Protocol
    Speed Improvement
    Windows 95/98
    Speed Improvement
    Windows 2000 Service Pack 2
    Windows NT 3.1

    This chapter contains client-specific information.

    Macintosh Clients

    - +Chapter 44. Samba and Other CIFS Clients

    Chapter 44. Samba and Other CIFS Clients
    Prev Part VI. Reference Section Next

    Chapter 44. Samba and Other CIFS Clients

    Jelmer R. Vernooij

    The Samba Team

    John H. Terpstra

    Samba Team

    Dan Shearer

    Samba Team

    Jim McDonough

    OS/2 
    IBM

    5 Mar 2001

    Table of Contents

    Macintosh Clients
    OS2 Client
    Configuring OS/2 Warp Connect or OS/2 Warp 4
    Configuring Other Versions of OS/2
    Printer Driver Download for OS/2 Clients
    Windows for Workgroups
    Latest TCP/IP Stack from Microsoft
    Delete .pwl Files After Password Change
    Configuring Windows for Workgroups Password Handling
    Password Case Sensitivity
    Use TCP/IP as Default Protocol
    Speed Improvement
    Windows 95/98
    Speed Improvement
    Windows 2000 Service Pack 2
    Windows NT 3.1

    This chapter contains client-specific information.

    Macintosh Clients

    + Yes. Thursby has a CIFS client/server called DAVE. They test it against Windows 95, Windows NT/200x/XP, and Samba for compatibility issues. At the time of this writing, DAVE was at version 5.1. Please refer to Thursby's Web site for more information regarding this product.

    - - + + Alternatives include two free implementations of AppleTalk for several kinds of UNIX machines and several more commercial ones. These products allow you to run file services and print services natively to Macintosh users, with no additional support required on the Macintosh. The two free implementations are Netatalk and CAP. What Samba offers MS Windows users, these packages offer to Macs. For more info on these packages, Samba, and Linux (and other UNIX-based systems), see http://www.eats.com/linux_mac_win.html. -

    Newer versions of the Macintosh (Mac OS X) include Samba.

    OS2 Client

    Configuring OS/2 Warp Connect or OS/2 Warp 4

    Basically, you need three components:

    • The File and Print Client (IBM peer)

    • TCP/IP (Internet support)

    • The “NetBIOS over TCP/IP” driver (TCPBEUI)

    Installing the first two together with the base operating +

    Newer versions of the Macintosh (Mac OS X) include Samba.

    OS2 Client

    Configuring OS/2 Warp Connect or OS/2 Warp 4

    Basically, you need three components:

    • The File and Print Client (IBM peer)

    • TCP/IP (Internet support)

    • The “NetBIOS over TCP/IP” driver (TCPBEUI)

    Installing the first two together with the base operating system on a blank system is explained in the Warp manual. If Warp has already been installed, but you now want to install the networking support, use the “Selective Install for Networking” @@ -26,7 +26,7 @@ packages offer to Macs. For more info on these packages, Samba, and Linux (and to the Names List or specify a WINS server (NetBIOS Nameserver in IBM and RFC terminology). For Warp Connect, you may need to download an update for IBM Peer to bring it on - the same level as Warp 4. See the IBM OS/2 Warp Web page

    Configuring Other Versions of OS/2

    This sections deals with configuring OS/2 Warp 3 (not Connect), OS/2 1.2, 1.3 or 2.x.

    You can use the free Microsoft LAN Manager 2.2c Client for OS/2 that is + the same level as Warp 4. See the IBM OS/2 Warp Web page

    Configuring Other Versions of OS/2

    This sections deals with configuring OS/2 Warp 3 (not Connect), OS/2 1.2, 1.3 or 2.x.

    You can use the free Microsoft LAN Manager 2.2c Client for OS/2 that is available from ftp://ftp.microsoft.com/BusSys/Clients/LANMAN.OS2/. In a nutshell, edit @@ -37,7 +37,7 @@ packages offer to Macs. For more info on these packages, Samba, and Linux (and

    before you install the client. Also, do not use the included NE2000 driver because it is buggy. Try the NE2000 or NS2000 driver from ftp://ftp.cdrom.com/pub/os2/network/ndis/ instead. -

    Printer Driver Download for OS/2 Clients

    Create a share called [PRINTDRV] that is +

    Printer Driver Download for OS/2 Clients

    Create a share called [PRINTDRV] that is world-readable. Copy your OS/2 driver files there. The .EA_ files must still be separate, so you will need to use the original install files and not copy an installed driver from an OS/2 system.

    Install the NT driver first for that printer. Then, add to your smb.conf a parameter, @@ -50,7 +50,7 @@ packages offer to Macs. For more info on these packages, Samba, and Linux (and you the driver is not available. On the second attempt, it will work. This is fixed simply by adding the device name to the mapping, after which it will work on the first attempt. -

    Windows for Workgroups

    Latest TCP/IP Stack from Microsoft

    Use the latest TCP/IP stack from Microsoft if you use Windows +

    Windows for Workgroups

    Latest TCP/IP Stack from Microsoft

    Use the latest TCP/IP stack from Microsoft if you use Windows for Workgroups. The early TCP/IP stacks had lots of bugs.

    Microsoft has released an incremental upgrade to its TCP/IP 32-bit VxD drivers. The latest release can be found at ftp.microsoft.com, located in /Softlib/MSLFILES/TCP32B.EXE. There is an @@ -60,7 +60,7 @@ update.txt file there that describes the problems that were fixed. New files inc NETSTAT.EXE, and NBTSTAT.EXE.

    More information about this patch is available in Knowledge Base article 99891. -

    Delete .pwl Files After Password Change

    +

    Delete .pwl Files After Password Change

    Windows for Workgroups does a lousy job with passwords. When you change passwords on either the UNIX box or the PC, the safest thing to do is delete the .pwl files in the Windows directory. The PC will complain about not finding the files, but will soon get over it, @@ -70,16 +70,16 @@ If you do not do this, you may find that Windows for Workgroups remembers and us password, even if you told it a new one.

    Often Windows for Workgroups will totally ignore a password you give it in a dialog box. -

    Configuring Windows for Workgroups Password Handling

    - +

    Configuring Windows for Workgroups Password Handling

    + There is a program call admincfg.exe on the last disk (disk 8) of the WFW 3.11 disk set. To install it, type EXPAND A:\ADMINCFG.EX_ C:\WINDOWS\ADMINCFG.EXE. Then add an icon for it via the Program Manager New menu. This program allows you to control how WFW handles passwords, Disable Password Caching and so on, for use with security = user. -

    Password Case Sensitivity

    Windows for Workgroups uppercases the password before sending it to the server. +

    Password Case Sensitivity

    Windows for Workgroups uppercases the password before sending it to the server. UNIX passwords can be case-sensitive though. Check the smb.conf information on password level to specify what characters -Samba should try to uppercase when checking.

    Use TCP/IP as Default Protocol

    To support print queue reporting, you may find +Samba should try to uppercase when checking.

    Use TCP/IP as Default Protocol

    To support print queue reporting, you may find that you have to use TCP/IP as the default protocol under Windows for Workgroups. For some reason, if you leave NetBEUI as the default, it may break the print queue reporting on some systems. @@ -94,7 +94,7 @@ performance with a large value (16384 or larger). Other people have reported that anything over 3072 slows things down enormously. One person even reported a speed drop of a factor of 30 when he went from 3072 to 8192. -

    Windows 95/98

    +

    Windows 95/98

    When using Windows 95 OEM SR2, the following updates are recommended where Samba is being used. Please note that the changes documented in Speed Improvement will affect you once these @@ -109,11 +109,11 @@ install the OLEUPD.EXE fix. This fix may stop your machine from hanging for an extended period when exiting Outlook, and you may notice a significant speedup when accessing network neighborhood services. -

    Speed Improvement

    +

    Speed Improvement

    Configure the Windows 95 TCP/IP registry settings to give better performance. I use a program called MTUSPEED.exe that I got off the Internet. There are various other utilities of this type freely available. -

    Windows 2000 Service Pack 2

    +

    Windows 2000 Service Pack 2

    There are several annoyances with Windows 2000 SP2, one of which only appears when using a Samba server to host user profiles to Windows 2000 SP2 clients in a Windows domain. This assumes @@ -132,8 +132,8 @@ for more details on this option. Also note that the nt acl support parameter was formally a global parameter in releases prior to Samba 2.2.2.

    -Following example provides a minimal profile share. -

    Example 43.1. Minimal Profile Share

    [profile]
    path = /export/profile
    create mask = 0600
    directory mask = 0700
    nt acl support = no
    read only = no

    +Following example provides a minimal profile share. +

    Example 44.1. Minimal Profile Share

    [profile]
    path = /export/profile
    create mask = 0600
    directory mask = 0700
    nt acl support = no
    read only = no

    The reason for this bug is that the Windows 200x SP2 client copies the security descriptor for the profile that contains the Samba server's SID, and not the domain SID. The client @@ -145,7 +145,7 @@ When the nt acl support the Windows 200x client a response to the QuerySecurityDescriptor trans2 call, which causes the client to set a default ACL for the profile. This default ACL includes:

    DOMAIN\user “Full Control”>

    Note

    This bug does not occur when using Winbind to -create accounts on the Samba host for Domain users.

    Windows NT 3.1

    If you have problems communicating across routers with Windows +create accounts on the Samba host for Domain users.

    Windows NT 3.1

    If you have problems communicating across routers with Windows NT 3.1 workstations, read this Microsoft Knowledge Base article:. -

    Prev Up Next
    Chapter 42. Portability Home Chapter 44. Samba Performance Tuning
    +

    Prev Up Next
    Chapter 43. Portability Home Chapter 45. Samba Performance Tuning
    diff --git a/docs/htmldocs/Samba3-HOWTO/PolicyMgmt.html b/docs/htmldocs/Samba3-HOWTO/PolicyMgmt.html index 8c03f049a0..e78412ffd8 100644 --- a/docs/htmldocs/Samba3-HOWTO/PolicyMgmt.html +++ b/docs/htmldocs/Samba3-HOWTO/PolicyMgmt.html @@ -1,24 +1,24 @@ -Chapter 26. System and Account Policies
    Chapter 26. System and Account Policies
    Prev Part III. Advanced Configuration Next

    Chapter 26. System and Account Policies

    John H. Terpstra

    Samba Team

    April 3 2003

    Table of Contents

    Features and Benefits
    Creating and Managing System Policies
    Windows 9x/ME Policies
    Windows NT4-Style Policy Files
    MS Windows 200x/XP Professional Policies
    Managing Account/User Policies
    Management Tools
    Samba Editreg Toolset
    Windows NT4/200x
    Samba PDC
    System Startup and Logon Processing Overview
    Common Errors
    Policy Does Not Work

    - +Chapter 26. System and Account Policies

    Chapter 26. System and Account Policies
    Prev Part III. Advanced Configuration Next

    Chapter 26. System and Account Policies

    John H. Terpstra

    Samba Team

    April 3 2003

    Table of Contents

    Features and Benefits
    Creating and Managing System Policies
    Windows 9x/ME Policies
    Windows NT4-Style Policy Files
    MS Windows 200x/XP Professional Policies
    Managing Account/User Policies
    Management Tools
    Samba Editreg Toolset
    Windows NT4/200x
    Samba PDC
    System Startup and Logon Processing Overview
    Common Errors
    Policy Does Not Work

    + This chapter summarizes the current state of knowledge derived from personal practice and knowledge from Samba mailing list subscribers. Before reproduction of posted information, every effort has been made to validate the information given. Where additional information was uncovered through this validation, it is provided also. -

    Features and Benefits

    - - - +

    Features and Benefits

    + + + When MS Windows NT 3.5 was introduced, the hot new topic was the ability to implement Group Policies for users and groups. Then along came MS Windows NT4 and a few sites started to adopt this capability. How do we know that? By the number of “boo-boos” (or mistakes) administrators made and then requested help to resolve.

    - - - - - + + + + + By the time that MS Windows 2000 and Active Directory was released, administrators got the message: Group Policies are a good thing! They can help reduce administrative costs and actually make happier users. But adoption of the true @@ -27,16 +27,16 @@ and machines were picked up on rather slowly. This was obvious from the Samba mailing list back in 2000 and 2001 when there were few postings regarding GPOs and how to replicate them in a Samba environment.

    - + Judging by the traffic volume since mid 2002, GPOs have become a standard part of the deployment in many sites. This chapter reviews techniques and methods that can be used to exploit opportunities for automation of control over user desktops and network client workstations. -

    Creating and Managing System Policies

    - - - - +

    Creating and Managing System Policies

    + + + + Under MS Windows platforms, particularly those following the release of MS Windows NT4 and MS Windows 95, it is possible to create a type of file that would be placed in the NETLOGON share of a domain controller. As the client logs onto the network, @@ -44,9 +44,9 @@ this file is read and the contents initiate changes to the registry of the clien machine. This file allows changes to be made to those parts of the registry that affect users, groups of users, or machines.

    - - - + + + For MS Windows 9x/Me, this file must be called Config.POL and may be generated using a tool called poledit.exe, better known as the Policy Editor. The policy editor was provided on the Windows 98 installation CD-ROM, but @@ -54,12 +54,12 @@ disappeared again with the introduction of MS Windows Me. From comments of MS Windows network administrators, it would appear that this tool became a part of the MS Windows Me Resource Kit.

    - + MS Windows NT4 server products include the System Policy Editor under Start -> Programs -> Administrative Tools. For MS Windows NT4 and later clients, this file must be called NTConfig.POL.

    - + New with the introduction of MS Windows 2000 was the Microsoft Management Console or MMC. This tool is the new wave in the ever-changing landscape of Microsoft methods for management of network access and security. Every new Microsoft product @@ -67,10 +67,10 @@ or technology seems to make the old rules obsolete and introduces newer and more complex tools and methods. To Microsoft's credit, the MMC does appear to be a step forward, but improved functionality comes at a great price.

    - - - - + + + + Before embarking on the configuration of network and system policies, it is highly advisable to read the documentation available from Microsoft's Web site regarding @@ -80,16 +80,16 @@ be read and understood. Try searching on the Microsoft Web site for “

    What follows is a brief discussion with some helpful notes. The information provided here is incomplete you are warned. -

    Windows 9x/ME Policies

    - - +

    Windows 9x/ME Policies

    + + You need the Windows 98 Group Policy Editor to set up Group Profiles under Windows 9x/Me. It can be found on the original full-product Windows 98 installation CD-ROM under tools\reskit\netadmin\poledit. Install this using the Add/Remove Programs facility, and then click on Have Disk.

    - - + + Use the Group Policy Editor to create a policy file that specifies the location of user profiles and/or My Documents, and so on. Then save these settings in a file called Config.POL that needs to be placed in the @@ -99,25 +99,25 @@ here is incomplete you are warned.

    Further details are covered in the Windows 98 Resource Kit documentation.

    - + If you do not take the correct steps, then every so often Windows 9x/Me will check the integrity of the registry and restore its settings from the backup copy of the registry it stores on each Windows 9x/Me machine. So, you will occasionally notice things changing back to the original settings.

    - - + + Install the Group Policy handler for Windows 9x/Me to pick up Group Policies. Look on the Windows 98 CD-ROM in \tools\reskit\netadmin\poledit. Install Group Policies on a Windows 9x/Me client by double-clicking on grouppol.inf. Log off and on again a couple of times and see if Windows 98 picks up Group Policies. Unfortunately, this needs to be done on every Windows 9x/Me machine that uses Group Policies. -

    Windows NT4-Style Policy Files

    - - - - +

    Windows NT4-Style Policy Files

    + + + + To create or edit ntconfig.pol, you must use the NT Server Policy Editor, poledit.exe, which is included with NT4 Server but not with NT workstation. There is a Policy Editor on an NT4 @@ -126,19 +126,19 @@ here is incomplete you are warned. workstation/server, it will not work with NT clients. However, the files from the NT Server will run happily enough on an NT4 workstation.

    - - - - + + + + You need poledit.exe, common.adm, and winnt.adm. It is convenient to put the two *.adm files in the c:\winnt\inf directory, which is where the binary will look for them unless told otherwise. This directory is normally “hidden.”

    - - - - + + + + The Windows NT Policy Editor is also included with the Service Pack 3 (and later) for Windows NT 4.0. Extract the files using servicepackname /x that's Nt4sp6ai.exe /x for Service Pack 6a. The Policy Editor, @@ -146,17 +146,17 @@ here is incomplete you are warned. be extracted as well. It is also possible to download the policy template files for Office97 and get a copy of the Policy Editor. Another possible location is with the Zero Administration Kit available for download from Microsoft. -

    Registry Spoiling

    - - +

    Registry Spoiling

    + + With NT4-style registry-based policy changes, a large number of settings are not automatically reversed as the user logs off. The settings that were in the NTConfig.POL file were applied to the client machine registry and apply to the hive key HKEY_LOCAL_MACHINE are permanent until explicitly reversed. This is known as tattooing. It can have serious consequences downstream, and the administrator must be extremely careful not to lock out the ability to manage the machine at a later date. -

    MS Windows 200x/XP Professional Policies

    - +

    MS Windows 200x/XP Professional Policies

    + Windows NT4 system policies allow the setting of registry parameters specific to users, groups, and computers (client workstations) that are members of the NT4-style domain. Such policy files will work with MS Windows 200x/XP clients also. @@ -165,8 +165,8 @@ here is incomplete you are warned. a superset of capabilities compared with NT4-style policies. Obviously, the tool used to create them is different, and the mechanism for implementing them is much improved.

    - - + + The older NT4-style registry-based policies are known as Administrative Templates in MS Windows 2000/XP GPOs. The latter includes the ability to set various security configurations, enforce Internet Explorer browser settings, change and redirect aspects of the @@ -175,23 +175,23 @@ here is incomplete you are warned. feature is the ability to make available particular software Windows applications to particular users and/or groups.

    - - - + + + Remember, NT4 policy files are named NTConfig.POL and are stored in the root of the NETLOGON share on the domain controllers. A Windows NT4 user enters a username and password and selects the domain name to which the logon will attempt to take place. During the logon process, the client machine reads the NTConfig.POL file from the NETLOGON share on the authenticating server and modifies the local registry values according to the settings in this file.

    - - - - - - - - + + + + + + + + Windows 200x GPOs are feature-rich. They are not stored in the NETLOGON share, but rather part of a Windows 200x policy file is stored in the Active Directory itself and the other part is stored in a shared (and replicated) volume called the SYSVOL folder. This folder is present on all Active @@ -199,7 +199,7 @@ here is incomplete you are warned. Group Policy Container (GPC), and the part that is stored in the replicated share called SYSVOL is known as the Group Policy Template (GPT).

    - + With NT4 clients, the policy file is read and executed only as each user logs onto the network. MS Windows 200x policies are much more complex GPOs are processed and applied at client machine startup (machine specific part), and when the user logs onto the network, the user-specific part @@ -207,19 +207,19 @@ here is incomplete you are warned. to any number of concurrently applicable (and applied) policy sets (GPOs). Active Directory allows the administrator to also set filters over the policy settings. No such equivalent capability exists with NT4-style policy files. -

    Administration of Windows 200x/XP Policies

    - - - - - +

    Administration of Windows 200x/XP Policies

    + + + + + Instead of using the tool called the System Policy Editor, commonly called Poledit (from the executable name poledit.exe), GPOs are created and managed using a Microsoft Management Console (MMC) snap-in as follows:

    1. Go to the Windows 200x/XP menu Start->Programs->Administrative Tools and select the MMC snap-in called Active Directory Users and Computers

    2. - + Select the domain or organizational unit (OU) that you wish to manage, then right-click to open the context menu for that object, and select the Properties.

    3. @@ -237,13 +237,13 @@ here is incomplete you are warned. refer to the Microsoft Windows Resource Kit for your particular version of MS Windows.

      Note

      - - - + + + The MS Windows 2000 Resource Kit contains a tool called gpolmig.exe. This tool can be used to migrate an NT4 NTConfig.POL file into a Windows 200x style GPO. Be VERY careful how you use this powerful tool. Please refer to the resource kit manuals for specific usage information. -

    Custom System Policy Templates

    +

    Custom System Policy Templates

    Over the past year, there has been a bit of talk regarding the creation of customized templates for the Windows Sytem Policy Editor. A recent announcement on the Samba mailing list is worthy of mention. @@ -256,15 +256,15 @@ here is incomplete you are warned.

    For further information please see the Petersen Computer Consulting web site. There is a download link for the template file. -

    Managing Account/User Policies

    - - - +

    Managing Account/User Policies

    + + + Policies can define a specific user's settings or the settings for a group of users. The resulting policy file contains the registry settings for all users, groups, and computers that will be using the policy file. Separate policy files for each user, group, or computer are not necessary.

    - + If you create a policy that will be automatically downloaded from validating domain controllers, you should name the file NTConfig.POL. As system administrator, you have the option of renaming the policy file and, by modifying the Windows NT-based workstation, directing the computer to update @@ -272,46 +272,46 @@ the policy from a manual path. You can do this by either manually changing the r the System Policy Editor. This can even be a local path such that each machine has its own policy file, but if a change is necessary to all machines, it must be made individually to each workstation.

    - - + + When a Windows NT4/200x/XP machine logs onto the network, the client looks in the NETLOGON share on the authenticating domain controller for the presence of the NTConfig.POL file. If one exists, it is downloaded, parsed, and then applied to the user's part of the registry.

    - - - - + + + + MS Windows 200x/XP clients that log onto an MS Windows Active Directory security domain may additionally acquire policy settings through GPOs that are defined and stored in Active Directory itself. The key benefit of using AD GPOs is that they impose no registry spoiling effect. This has considerable advantage compared with the use of NTConfig.POL (NT4) style policy updates.

    - - + + In addition to user access controls that may be imposed or applied via system and/or group policies in a manner that works in conjunction with user profiles, the user management environment under MS Windows NT4/200x/XP allows per-domain as well as per-user account restrictions to be applied. Common restrictions that are frequently used include:

    - +

    • Logon hours

    • Password aging

    • Permitted logon from certain machines only

    • Account type (local or global)

    • User rights

    - - + + Samba-3.0.20 does not yet implement all account controls that are common to MS Windows NT4/200x/XP. While it is possible to set many controls using the Domain User Manager for MS Windows NT4, only password expiry is functional today. Most of the remaining controls at this time have only stub routines that may eventually be completed to provide actual control. Do not be misled by the fact that a parameter can be set using the NT4 Domain User Manager or in the NTConfig.POL. -

    Management Tools

    +

    Management Tools

    Anyone who wishes to create or manage Group Policies will need to be familiar with a number of tools. The following sections describe a few key tools that will help you to create a low-maintenance user environment. -

    Samba Editreg Toolset

    - - - +

    Samba Editreg Toolset

    + + + A new tool called editreg is under development. This tool can be used to edit registry files (called NTUser.DAT) that are stored in user and group profiles. NTConfig.POL files have the same structure as the @@ -320,33 +320,33 @@ environment. permit the building of new NTConfig.POL files with extended capabilities. It is proving difficult to realize this capability, so do not be surprised if this feature does not materialize. Formal capabilities will be announced at the time that this tool is released for production use. -

    Windows NT4/200x

    - - - +

    Windows NT4/200x

    + + + The tools that may be used to configure these types of controls from the MS Windows environment are the NT4 User Manager for Domains, the NT4 System and Group Policy Editor, and the Registry Editor (regedt32.exe). Under MS Windows 200x/XP, this is done using the MMC with appropriate “snap-ins,” the registry editor, and potentially also the NT4 System and Group Policy Editor. -

    Samba PDC

    - - - - +

    Samba PDC

    + + + + With a Samba domain controller, the new tools for managing user account and policy information include: smbpasswd, pdbedit, net, and rpcclient. The administrator should read the man pages for these tools and become familiar with their use. -

    System Startup and Logon Processing Overview

    +

    System Startup and Logon Processing Overview

    The following attempts to document the order of processing the system and user policies following a system reboot and as part of the user logon:

    1. - - + + Network starts, then Remote Procedure Call System Service (RPCSS) and multiple universal naming convention provider (MUP) start.

    2. - - + + Where Active Directory is involved, an ordered list of GPOs is downloaded and applied. The list may include GPOs that:

      • Apply to the location of machines in a directory.

      • Apply only when settings have changed.

      • Depend on configuration of the scope of applicability: local, @@ -371,10 +371,10 @@ reboot and as part of the user logon:

      • The user interface as determined from the GPOs is presented. Note: In a Samba domain (like an NT4 domain), machine (system) policies are applied at startup; user policies are applied at logon. -

    Common Errors

    +

    Common Errors

    Policy-related problems can be quite difficult to diagnose and even more difficult to rectify. The following collection demonstrates only basic issues. -

    Policy Does Not Work

    +

    Policy Does Not Work

    “We have created the Config.POL file and put it in the NETLOGON share. It has made no difference to our Win XP Pro machines, they just do not see it. It worked fine with Win 98 but does not work any longer since we upgraded to Win XP Pro. Any hints?” diff --git a/docs/htmldocs/Samba3-HOWTO/Portability.html b/docs/htmldocs/Samba3-HOWTO/Portability.html index 4bbb6acf04..dfddaeb113 100644 --- a/docs/htmldocs/Samba3-HOWTO/Portability.html +++ b/docs/htmldocs/Samba3-HOWTO/Portability.html @@ -1,11 +1,11 @@ -Chapter 42. Portability

    Chapter 42. Portability
    Prev Part VI. Reference Section Next

    Chapter 42. Portability

    Jelmer R. Vernooij

    The Samba Team

    John H. Terpstra

    Samba Team

    Table of Contents

    HPUX
    SCO UNIX
    DNIX
    Red Hat Linux
    AIX: Sequential Read Ahead
    Solaris
    Locking Improvements
    Winbind on Solaris 9

    - - +Chapter 43. Portability

    Chapter 43. Portability
    Prev Part VI. Reference Section Next

    Chapter 43. Portability

    Jelmer R. Vernooij

    The Samba Team

    John H. Terpstra

    Samba Team

    Table of Contents

    HPUX
    SCO UNIX
    DNIX
    Red Hat Linux
    AIX: Sequential Read Ahead
    Solaris
    Locking Improvements
    Winbind on Solaris 9

    + + Samba works on a wide range of platforms, but the interface all the platforms provide is not always compatible. This chapter contains -platform-specific information about compiling and using Samba.

    HPUX

    - - +platform-specific information about compiling and using Samba.

    HPUX

    + + Hewlett-Packard's implementation of supplementary groups is nonstandard (for historical reasons). There are two group files, /etc/group and /etc/logingroup; the system maps UIDs to numbers using the former, but @@ -23,11 +23,11 @@ allowed range.

    This is documented in the HP manual pages under setgroups(2) and passwd(4).

    - - + + On HP-UX you must use gcc or the HP ANSI compiler. The free compiler that comes with HP-UX is not ANSI compliant and cannot compile Samba. -

    SCO UNIX

    +

    SCO UNIX

    If you run an old version of SCO UNIX, you may need to get important TCP/IP patches for Samba to work correctly. Without the patch, you may encounter corrupt data transfers using Samba. @@ -43,7 +43,7 @@ binary packages you will install. This is important if you wish to avoid data co problems with your installation. To build Samba for SCO UNIX products may require significant patching of Samba source code. It is much easier to obtain binary packages directly from SCO. -

    DNIX

    +

    DNIX

    DNIX has a problem with seteuid() and setegid(). These routines are needed for Samba to work correctly, but they were left out of the DNIX C library for some reason. @@ -100,14 +100,14 @@ LIBSM = setegid.o seteuid.o -ln You should then remove the line: 

     #define NO_EID
-

    from the DNIX section of includes.h.

    Red Hat Linux

    +

    from the DNIX section of includes.h.

    Red Hat Linux

    By default during installation, some versions of Red Hat Linux add an entry to /etc/hosts as follows: 

     127.0.0.1 loopback "hostname"."domainname"

    - + This causes Samba to loop back onto the loopback interface. The result is that Samba fails to communicate correctly with the world and therefore may fail to correctly negotiate who @@ -115,7 +115,7 @@ is the master browse list holder and who is the master browser.

    Corrective action: Delete the entry after the word "loopback" in the line starting 127.0.0.1. -

    AIX: Sequential Read Ahead

    +

    AIX: Sequential Read Ahead

    Disabling sequential read ahead can improve Samba performance significantly when there is a relatively high level of multiprogramming (many smbd processes or mixed with another workload), not an abundance of physical memory or slower @@ -134,7 +134,7 @@ For AIX 5.2 and later jfs2 filesystems: ioo -o j

    If you have a mix of jfs and jfs2 filesystems on the same host, simply use both ioo commands. -

    Solaris

    Locking Improvements

    Some people have been experiencing problems with F_SETLKW64/fcntl +

    Solaris

    Locking Improvements

    Some people have been experiencing problems with F_SETLKW64/fcntl when running Samba on Solaris. The built-in file-locking mechanism was not scalable. Performance would degrade to the point where processes would get into loops of trying to lock a file. It would try a lock, then fail, @@ -150,4 +150,4 @@ and rebuild Samba.

    Thanks to Joe Meslovich for reporting this.

    Winbind on Solaris 9

    Nsswitch on Solaris 9 refuses to use the Winbind NSS module. This behavior is fixed by Sun in patch 112960-14. -

    Prev Up Next
    Chapter 41. How to Compile Samba Home Chapter 43. Samba and Other CIFS Clients
    +

    Prev Up Next
    Chapter 42. How to Compile Samba Home Chapter 44. Samba and Other CIFS Clients
    diff --git a/docs/htmldocs/Samba3-HOWTO/ProfileMgmt.html b/docs/htmldocs/Samba3-HOWTO/ProfileMgmt.html index d668a55379..02fb036863 100644 --- a/docs/htmldocs/Samba3-HOWTO/ProfileMgmt.html +++ b/docs/htmldocs/Samba3-HOWTO/ProfileMgmt.html @@ -1,42 +1,42 @@ -Chapter 27. Desktop Profile Management
    Chapter 27. Desktop Profile Management
    Prev Part III. Advanced Configuration Next

    Chapter 27. Desktop Profile Management

    John H. Terpstra

    Samba Team

    April 3 2003

    Table of Contents

    Features and Benefits
    Roaming Profiles
    Samba Configuration for Profile Handling
    Windows Client Profile Configuration Information
    User Profile Hive Cleanup Service
    Sharing Profiles between Windows 9x/Me and NT4/200x/XP Workstations
    Profile Migration from Windows NT4/200x Server to Samba
    Mandatory Profiles
    Creating and Managing Group Profiles
    Default Profile for Windows Users
    MS Windows 9x/Me
    MS Windows NT4 Workstation
    MS Windows 200x/XP
    Common Errors
    Configuring Roaming Profiles for a Few Users or Groups
    Cannot Use Roaming Profiles
    Changing the Default Profile
    Debugging Roaming Profiles and NT4-style Domain Policies

    Features and Benefits

    - +Chapter 27. Desktop Profile Management

    Chapter 27. Desktop Profile Management
    Prev Part III. Advanced Configuration Next

    Chapter 27. Desktop Profile Management

    John H. Terpstra

    Samba Team

    April 3 2003

    Table of Contents

    Features and Benefits
    Roaming Profiles
    Samba Configuration for Profile Handling
    Windows Client Profile Configuration Information
    User Profile Hive Cleanup Service
    Sharing Profiles between Windows 9x/Me and NT4/200x/XP Workstations
    Profile Migration from Windows NT4/200x Server to Samba
    Mandatory Profiles
    Creating and Managing Group Profiles
    Default Profile for Windows Users
    MS Windows 9x/Me
    MS Windows NT4 Workstation
    MS Windows 200x/XP
    Common Errors
    Configuring Roaming Profiles for a Few Users or Groups
    Cannot Use Roaming Profiles
    Changing the Default Profile
    Debugging Roaming Profiles and NT4-style Domain Policies

    Features and Benefits

    + Roaming profiles are feared by some, hated by a few, loved by many, and a godsend for some administrators.

    - + Roaming profiles allow an administrator to make available a consistent user desktop as the user moves from one machine to another. This chapter provides much information regarding how to configure and manage roaming profiles.

    - + While roaming profiles might sound like nirvana to some, they are a real and tangible problem to others. In particular, users of mobile computing tools, where often there may not be a sustained network connection, are often better served by purely local profiles. This chapter provides information to help the Samba administrator deal with those situations. -

    Roaming Profiles

    Warning

    +

    Roaming Profiles

    Warning

    Roaming profiles support is different for Windows 9x/Me and Windows NT4/200x.

    Before discussing how to configure roaming profiles, it is useful to see how Windows 9x/Me and Windows NT4/200x clients implement these features.

    - + Windows 9x/Me clients send a NetUserGetInfo request to the server to get the user's profiles location. However, the response does not have room for a separate profiles location field, only the user's home share. This means that Windows 9x/Me profiles are restricted to being stored in the user's home directory.

    - - + + Windows NT4/200x clients send a NetSAMLogon RPC request, which contains many fields including a separate field for the location of the user's profiles. -

    Samba Configuration for Profile Handling

    +

    Samba Configuration for Profile Handling

    This section documents how to configure Samba for MS Windows client profile support. -

    NT4/200x User Profiles

    +

    NT4/200x User Profiles

    For example, to support Windows NT4/200x clients, set the following in the [global] section of the smb.conf file: -

    logon path = \\profileserver\profileshare\profilepath\%U\moreprofilepath

    +

    logon path = \\profileserver\profileshare\profilepath\%U\moreprofilepath

    This is typically implemented like: -

    logon path = \\%L\Profiles\%U

    +

    logon path = \\%L\Profiles\%U

    where “%L” translates to the name of the Samba server and “%U” translates to the username.

    The default for this option is \\%N\%U\profile, namely, \\sambaserver\username\profile. @@ -45,55 +45,55 @@ a Samba server for the profiles, you must make the share that is specified in th browseable. Please refer to the man page for smb.conf regarding the different semantics of “%L” and “%N”, as well as “%U” and “%u”.

    Note

    - - + + MS Windows NT/200x clients at times do not disconnect a connection to a server between logons. It is recommended to not use the homes metaservice name as part of the profile share path. -

    Windows 9x/Me User Profiles

    - - +

    Windows 9x/Me User Profiles

    + + To support Windows 9x/Me clients, you must use the logon home parameter. Samba has been fixed so net use /home now works as well and it, too, relies on the logon home parameter.

    - - - + + + By using the logon home parameter, you are restricted to putting Windows 9x/Me profiles in the user's home directory. But wait! There is a trick you can use. If you set the following in the [global] section of your smb.conf file: -

    logon home = \\%L\%U\.profiles

    +

    logon home = \\%L\%U\.profiles

    then your Windows 9x/Me clients will dutifully put their clients in a subdirectory of your home directory called .profiles (making them hidden).

    - + Not only that, but net use /home will also work because of a feature in Windows 9x/Me. It removes any directory stuff off the end of the home directory area and only uses the server and share portion. That is, it looks like you specified \\%L\%U for logon home. -

    Mixed Windows Windows 9x/Me and NT4/200x User Profiles

    +

    Mixed Windows Windows 9x/Me and NT4/200x User Profiles

    You can support profiles for Windows 9x and Windows NT clients by setting both the logon home and logon path parameters. For example, -

    logon home = \\%L\%U\.profiles
    logon path = \\%L\profiles\%U

    - +

    logon home = \\%L\%U\.profiles
    logon path = \\%L\profiles\%U

    + Windows 9x/Me and NT4 and later profiles should not be stored in the same location because Windows NT4 and later will experience problems with mixed profile environments. -

    Disabling Roaming Profile Support

    - +

    Disabling Roaming Profile Support

    + The question often asked is, “How may I enforce use of local profiles?” or “How do I disable roaming profiles?”

    - + There are three ways of doing this: -

    In smb.conf

    +

    In smb.conf

    Affect the following settings and ALL clients will be forced to use a local profile: logon home = and logon path =

    The arguments to these parameters must be left blank. It is necessary to include the = sign to specifically assign the empty value.

    MS Windows Registry:

    - - + + Use the Microsoft Management Console (MMC) gpedit.msc to instruct your MS Windows XP machine to use only a local profile. This, of course, modifies registry settings. The full path to the option is: @@ -116,11 +116,11 @@ Disable: Prevent Roaming Profile Change from Propagating to the Server Consult the MS Windows registry guide for your particular MS Windows version for more information about which registry keys to change to enforce use of only local user profiles.

    Note

    - + The specifics of how to convert a local profile to a roaming profile, or a roaming profile to a local one, vary according to the version of MS Windows you are running. Consult the Microsoft MS Windows Resource Kit for your version of Windows for specific information. -

    Windows Client Profile Configuration Information

    Windows 9x/Me Profile Setup

    +

    Windows Client Profile Configuration Information

    Windows 9x/Me Profile Setup

    When a user first logs in on Windows 9x, the file user.DAT is created, as are folders Start Menu, Desktop, Programs, and Nethood. These directories and their contents will be merged with the local versions @@ -128,8 +128,8 @@ stored in c:\windows\profiles\username on subseque each. You will need to use the [global] options preserve case = yes, short preserve case = yes, and case sensitive = no in order to maintain capital letters in shortcuts in any of the profile folders.

    - - + + The user.DAT file contains all the user's preferences. If you wish to enforce a set of preferences, rename their user.DAT file to user.MAN, and deny them write access to this file.

    1. @@ -144,16 +144,16 @@ rename their user.DAT file to Client for Microsoft Networks. Press OK, and this time allow the computer to reboot.

    - - - - + + + + Under Windows 9x/Me, profiles are downloaded from the Primary Logon. If you have the Primary Logon as “Client for Novell Networks”, then the profiles and logon script will be downloaded from your Novell server. If you have the Primary Logon as “Windows Logon”, then the profiles will be loaded from the local machine a bit against the concept of roaming profiles, it would seem!

    - + You will now find that the Microsoft Networks Login box contains [user, password, domain] instead of just [user, password]. Type in the Samba server's domain name (or any other domain known to exist, but bear in mind that the user will be authenticated against this domain and profiles downloaded from it @@ -168,28 +168,28 @@ contents of the directory specified in the Desktop, Start Menu, Programs, and Nethood folders have been created.

    - - - + + + These folders will be cached locally on the client and updated when the user logs off (if you haven't made them read-only by then). You will find that if the user creates further folders or shortcuts, the client will merge the profile contents downloaded with the contents of the profile directory already on the local client, taking the newest folders and shortcut from each set.

    - - - - + + + + If you have made the folders/files read-only on the Samba server, then you will get errors from the Windows 9x/Me machine on logon and logout as it attempts to merge the local and remote profile. Basically, if you have any errors reported by the Windows 9x/Me machine, check the UNIX file permissions and ownership rights on the profile directory contents, on the Samba server.

    - - - - - + + + + + If you have problems creating user profiles, you can reset the user's local desktop cache, as shown below. When this user next logs in, the user will be told that he/she is logging in “for the first time”. @@ -214,7 +214,7 @@ time”. described above) and delete the user.DAT or user.MAN file for the user, making a backup if required.

    Warning

    - + Before deleting the contents of the directory listed in the ProfilePath (this is likely to be c:\windows\profiles\username), ask whether the owner has any important files stored on his or her desktop or start menu. Delete the contents of the @@ -224,19 +224,19 @@ This will have the effect of removing the local (read-only hidden system file) < in their profile directory, as well as the local “desktop,” “nethood,” “start menu,” and “programs” folders.

    - - - - + + + + If all else fails, increase Samba's debug log levels to between 3 and 10, and/or run a packet sniffer program such as ethereal or netmon.exe, and look for error messages.

    - - + + If you have access to an Windows NT4/200x server, then first set up roaming profiles and/or netlogons on the Windows NT4/200x server. Make a packet trace, or examine the example packet traces provided with Windows NT4/200x server, and see what the differences are with the equivalent Samba trace. -

    Windows NT4 Workstation

    +

    Windows NT4 Workstation

    When a user first logs in to a Windows NT workstation, the profile NTuser.DAT is created. The profile location can be now specified through the logon path parameter.

    @@ -244,22 +244,22 @@ There is a parameter that is now available for use with NT Profiles: H: or any other drive, and should be used in conjunction with the new logon home parameter.

    - - + + The entry for the NT4 profile is a directory, not a file. The NT help on profiles mentions that a directory is also created with a .PDS extension. The user, while logging in, must have write permission to create the full profile path (and the folder with the .PDS extension for those situations where it might be created).

    - + In the profile directory, Windows NT4 creates more folders than Windows 9x/Me. It creates Application Data and others, as well as Desktop, Nethood, Start Menu, and Programs. The profile itself is stored in a file NTuser.DAT. Nothing appears to be stored in the .PDS directory, and its purpose is currently unknown.

    - - + + You can use the System Control Panel to copy a local profile onto a Samba server (see NT help on profiles; it is also capable of firing up the correct location in the System Control Panel for you). The NT help file also mentions that renaming @@ -267,7 +267,7 @@ a Samba server (see NT help on profiles; it is also capable of firing up the cor

    The case of the profile is significant. The file must be called NTuser.DAT or, for a mandatory profile, NTuser.MAN. -

    Windows 2000/XP Professional

    +

    Windows 2000/XP Professional

    You must first convert the profile from a local profile to a domain profile on the MS Windows workstation as follows:

    1. Log on as the local workstation administrator.

    2. Right-click on the My Computer icon, and select Properties.

    3. Click on the User Profiles tab.

    4. Select the profile you wish to convert (click it once).

    5. Click on the Copy To button.

    6. In the Permitted to use box, click on the @@ -280,7 +280,7 @@ Done. You now have a profile that can be edited using the Samba

      Note

      Under Windows NT/200x, the use of mandatory profiles forces the use of MS Exchange storage of mail data and keeps it out of the desktop profile. That keeps desktop profiles from becoming unusable. -

    Windows XP Service Pack 1

    +

    Windows XP Service Pack 1

    There is a security check new to Windows XP (or maybe only Windows XP service pack 1). It can be disabled via a group policy in the Active Directory. The policy is called: 

    @@ -296,18 +296,18 @@ Computer Configuration\Administrative Templates\System\User Profiles\
 	
    1. On the XP workstation, log in with an administrative account.
    2. Click on Start -> Run.
    3. Type mmc.
    4. Click on OK.
    5. A Microsoft Management Console should appear.
    6. Click on File -> Add/Remove Snap-in -> Add.
    7. Double-click on Group Policy.
    8. Click on Finish -> Close.
    9. Click on OK.
    10. In the “Console Root” window expand Local Computer Policy ->
 		Computer Configuration -> Administrative Templates -> 
 		System -> User Profiles.
    11. Double-click on Do not check for user ownership of Roaming Profile Folders.
    12. Select Enabled.
    13. Click on OK.
    14. Close the whole console. You do not need to save the settings (this refers to the
-	console settings rather than the policies you have changed).
    15. Reboot.

    User Profile Hive Cleanup Service

    + console settings rather than the policies you have changed).

  • Reboot.

    • User Profile Hive Cleanup Service

    There are certain situations that cause a cached local copy of roaming profile not to be deleted on exit, even if the policy to force such deletion is set. To deal with that situation, a special service was created. The application UPHClean (User Profile Hive Cleanup) can be installed as a service on Windows NT4/2000/XP Professional and Windows 2003.

    The UPHClean software package can be downloaded from the User Profile Hive Cleanup -Service[7] +Service[7] web site. -

    Sharing Profiles between Windows 9x/Me and NT4/200x/XP Workstations

    - - +

    Sharing Profiles between Windows 9x/Me and NT4/200x/XP Workstations

    + + Sharing of desktop profiles between Windows versions is not recommended. Desktop profiles are an evolving phenomenon, and profiles for later versions of MS Windows clients add features that may interfere with earlier versions of MS Windows clients. Probably the more salient reason to not mix profiles is @@ -319,20 +319,20 @@ If you then want to share the same Start Menu and Desktop with Windows 9x/Me, yo location for the profiles. The smb.conf parameters that need to be common are logon path and logon home.

    - - + + If you have this set up correctly, you will find separate user.DAT and NTuser.DAT files in the same profile directory. -

    Profile Migration from Windows NT4/200x Server to Samba

    - +

    Profile Migration from Windows NT4/200x Server to Samba

    + There is nothing to stop you from specifying any path that you like for the location of users' profiles. Therefore, you could specify that the profile be stored on a Samba server or any other SMB server, as long as that SMB server supports encrypted passwords.

    Windows NT4 Profile Management Tools

    - + Unfortunately, the resource kit information is specific to the version of MS Windows NT4/200x. The correct resource kit is required for each platform. -

    Here is a quick guide:

    Procedure 27.1. Profile Migration Procedure

    1. On your NT4 domain controller, right-click on My Computer, then select +

      Here is a quick guide:

      Procedure 27.1. Profile Migration Procedure

      1. On your NT4 domain controller, right-click on My Computer, then select Properties, then the tab labeled User Profiles.

      2. Select a user profile you want to migrate and click on it.

        Note

        I am using the term “migrate” loosely. You can copy a profile to create a group profile. You can give the user Everyone rights to the profile you copy this to. That is what you need to do, since your Samba domain is not a member of a trust relationship with your NT4 @@ -340,21 +340,21 @@ correct resource kit is required for each platform. c:\temp\foobar

      3. Click on Change in the Permitted to use box.

      4. Click on the group “Everyone”, click on OK. This closes the “choose user” box.

      5. Now click on OK.

      Follow these steps for every profile you need to migrate. -

    Side Bar Notes

    - - +

    Side Bar Notes

    + + You should obtain the SID of your NT4 domain. You can use the net rpc info to do this. See The Net Command Chapter, Other Miscellaneous Operations for more information. -

    moveuser.exe

    - +

    moveuser.exe

    + The Windows 200x professional resource kit has moveuser.exe. moveuser.exe changes the security of a profile from one user to another. This allows the account domain to change and/or the username to change.

    This command is like the Samba profiles tool. -

    Get SID

    - - +

    Get SID

    + + You can identify the SID by using GetSID.exe from the Windows NT Server 4.0 Resource Kit.

    Windows NT 4.0 stores the local profile information in the registry under the following key: @@ -364,60 +364,60 @@ Under the ProfileList key, there will be subkeys named with the SIDs of the user on to this computer. (To find the profile information for the user whose locally cached profile you want to move, find the SID for the user with the GetSID.exe utility.) Inside the appropriate user's subkey, you will see a string value named ProfileImagePath. -

    Mandatory Profiles

    - +

    Mandatory Profiles

    + A mandatory profile is a profile that the user does not have the ability to overwrite. During the user's session, it may be possible to change the desktop environment; however, as the user logs out, all changes made will be lost. If it is desired to not allow the user any ability to change the desktop environment, then this must be done through policy settings. See System and Account Policies.

    Note

    - - - + + + Under NO circumstances should the profile directory (or its contents) be made read-only because this may render the profile unusable. Where it is essential to make a profile read-only within the UNIX file system, this can be done, but then you absolutely must use the fake-permissions VFS module to instruct MS Windows NT/200x/XP clients that the Profile has write permission for the user. See fake_perms VFS module.

    - - + + For MS Windows NT4/200x/XP, the procedure shown in Profile Migration from Windows NT4/200x Server to Samba can also be used to create mandatory profiles. To convert a group profile into a mandatory profile, simply locate the NTUser.DAT file in the copied profile and rename it to NTUser.MAN.

    - + For MS Windows 9x/Me, it is the User.DAT file that must be renamed to User.MAN to effect a mandatory profile. -

    Creating and Managing Group Profiles

    - - - - +

    Creating and Managing Group Profiles

    + + + + Most organizations are arranged into departments. There is a nice benefit in this fact, since usually most users in a department require the same desktop applications and the same desktop layout. MS Windows NT4/200x/XP will allow the use of group profiles. A group profile is a profile that is created first using a template (example) user. Then using the profile migration tool (see above), the profile is assigned access rights for the user group that needs to be given access to the group profile.

    - + The next step is rather important. Instead of assigning a group profile to users (Using User Manager) on a “per-user” basis, the group itself is assigned the now modified profile.

    Note

    Be careful with group profiles. If the user who is a member of a group also has a personal profile, then the result will be a fusion (merge) of the two. -

    Default Profile for Windows Users

    - - +

    Default Profile for Windows Users

    + + MS Windows 9x/Me and NT4/200x/XP will use a default profile for any user for whom a profile does not already exist. Armed with a knowledge of where the default profile is located on the Windows workstation, and knowing which registry keys affect the path from which the default profile is created, it is possible to modify the default profile to one that has been optimized for the site. This has significant administrative advantages. -

    MS Windows 9x/Me

    - - +

    MS Windows 9x/Me

    + + To enable default per-use profiles in Windows 9x/Me, you can either use the Windows 98 System Policy Editor or change the registry directly.

    @@ -427,12 +427,12 @@ Next click on the Local Computer icon, click on User Profiles, and click on the enable box. Remember to save the registry changes.

    - + To modify the registry directly, launch the Registry Editor (regedit.exe) and select the hive HKEY_LOCAL_MACHINE\Network\Logon. Now add a DWORD type key with the name “User Profiles.” To enable user profiles to set the value to 1; to disable user profiles set it to 0. -

    User Profile Handling with Windows 9x/Me

    +

    User Profile Handling with Windows 9x/Me

    When a user logs on to a Windows 9x/Me machine, the local profile path, HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\ProfileList, is checked for an existing entry for that user. @@ -448,7 +448,7 @@ If a user profile is not found in either location, the default user profile from 9x/Me machine is used and copied to a newly created folder for the logged on user. At log off, any changes that the user made are written to the user's local profile. If the user has a roaming profile, the changes are written to the user's profile on the server. -

    MS Windows NT4 Workstation

    +

    MS Windows NT4 Workstation

    On MS Windows NT4, the default user profile is obtained from the location %SystemRoot%\Profiles, which in a default installation will translate to C:\Windows NT\Profiles. Under this directory on a clean install, there will be three @@ -462,7 +462,7 @@ per user depending on the profile settings chosen/created.

    When a new user first logs onto an MS Windows NT4 machine, a new profile is created from:

    • All Users settings.

    • Default User settings (contains the default NTUser.DAT file).

    - + When a user logs on to an MS Windows NT4 machine that is a member of a Microsoft security domain, the following steps are followed for profile handling:

    1. The user's account information that is obtained during the logon process @@ -474,11 +474,11 @@ the following steps are followed for profile handling: location.

    2. If the user account has a profile path, but at its location a profile does not exist, then a new profile is created in the %SystemRoot%\Profiles\%USERNAME% directory from reading the Default User profile.

    3. - - - - - + + + + + If the NETLOGON share on the authenticating server (logon server) contains a policy file (NTConfig.POL), then its contents are applied to the NTUser.DAT, which is applied to the HKEY_CURRENT_USER @@ -500,7 +500,7 @@ winlogon\"DeleteRoamingCache"=dword:0000000 In this case, the local copy (in %SystemRoot%\Profiles\%USERNAME%) will be deleted on logout.

      - + Under MS Windows NT4, default locations for common resources like My Documents may be redirected to a network share by modifying the following registry keys. These changes may be made via use of the System Policy Editor. To do so may require that you create your own template @@ -519,7 +519,7 @@ HKEY_CURRENT_USER \Explorer \User Shell Folders

      - +

      The above hive key contains a list of automatically managed folders. The default entries are shown in the next table.

      Table 27.1. User Shell Folder Registry Keys Default Values

      NameDefault Value
      AppData%USERPROFILE%\Application Data
      Desktop%USERPROFILE%\Desktop
      Favorites%USERPROFILE%\Favorites
      NetHood%USERPROFILE%\NetHood
      PrintHood%USERPROFILE%\PrintHood
      Programs%USERPROFILE%\Start Menu\Programs
      Recent%USERPROFILE%\Recent
      SendTo%USERPROFILE%\SendTo
      Start Menu %USERPROFILE%\Start Menu
      Startup%USERPROFILE%\Start Menu\Programs\Startup

      The registry key that contains the location of the default profile settings is: @@ -529,24 +529,24 @@ User Shell Folders

      The default entries are shown in Defaults of Profile Settings Registry Keys. -

      Table 27.2. Defaults of Profile Settings Registry Keys

      Common Desktop%SystemRoot%\Profiles\All Users\Desktop
      Common Programs%SystemRoot%\Profiles\All Users\Programs
      Common Start Menu%SystemRoot%\Profiles\All Users\Start Menu
      Common Startup%SystemRoot%\Profiles\All Users\Start Menu\Programs\Startup

    MS Windows 200x/XP

    Note

    - - - - +

    Table 27.2. Defaults of Profile Settings Registry Keys

    Common Desktop%SystemRoot%\Profiles\All Users\Desktop
    Common Programs%SystemRoot%\Profiles\All Users\Programs
    Common Start Menu%SystemRoot%\Profiles\All Users\Start Menu
    Common Startup%SystemRoot%\Profiles\All Users\Start Menu\Programs\Startup

    MS Windows 200x/XP

    Note

    + + + + MS Windows XP Home Edition does use default per-user profiles, but cannot participate in domain security, cannot log onto an NT/ADS-style domain, and thus can obtain the profile only from itself. While there are benefits in doing this, the beauty of those MS Windows clients that can participate in domain logon processes is that they allow the administrator to create a global default profile and enforce it through the use of Group Policy Objects (GPOs).

    - + When a new user first logs onto an MS Windows 200x/XP machine, the default profile is obtained from C:\Documents and Settings\Default User. The administrator can modify or change the contents of this location, and MS Windows 200x/XP will gladly use it. This is far from the optimum arrangement, since it will involve copying a new default profile to every MS Windows 200x/XP client workstation.

    - + When MS Windows 200x/XP participates in a domain security context, and if the default user profile is not found, then the client will search for a default profile in the NETLOGON share of the authenticating server. In MS Windows parlance, it is %LOGONSERVER%\NETLOGON\Default User, @@ -568,7 +568,7 @@ profile are controlled by entries on Windows 200x/XP is:

    the next table - +

    Table 27.3. Defaults of Default User Profile Paths Registry Keys

    NameDefault Value
    AppData%USERPROFILE%\Application Data
    Cache%USERPROFILE%\Local Settings\Temporary Internet Files
    Cookies%USERPROFILE%\Cookies
    Desktop%USERPROFILE%\Desktop
    Favorites%USERPROFILE%\Favorites
    History%USERPROFILE%\Local Settings\History
    Local AppData%USERPROFILE%\Local Settings\Application Data
    Local Settings%USERPROFILE%\Local Settings
    My Pictures%USERPROFILE%\My Documents\My Pictures
    NetHood%USERPROFILE%\NetHood
    Personal%USERPROFILE%\My Documents
    PrintHood%USERPROFILE%\PrintHood
    Programs%USERPROFILE%\Start Menu\Programs
    Recent%USERPROFILE%\Recent
    SendTo%USERPROFILE%\SendTo
    Start Menu%USERPROFILE%\Start Menu
    Startup%USERPROFILE%\Start Menu\Programs\Startup
    Templates%USERPROFILE%\Templates

    There is also an entry called “Default” that has no value set. The default entry is of type REG_SZ; all the others are of type REG_EXPAND_SZ.

    It makes a huge difference to the speed of handling roaming user profiles if all the folders are stored on a dedicated location on a network server. This means that it will not be necessary to write @@ -589,13 +589,13 @@ MS Windows user as seen by the Linux/UNIX file system.

    Please note that (default or custom) to it.

    MS Windows 200x/XP profiles may be local or roaming. A roaming profile is cached locally unless the following registry key is created: - + 

     HKEY_LOCAL_MACHINE\SYSTEM\Software\Microsoft\Windows NT\CurrentVersion\
 	winlogon\"DeleteRoamingCache"=dword:00000001

    In this case, the local cache copy is deleted on logout. -

    Common Errors

    +

    Common Errors

    The following are some typical errors, problems, and questions that have been asked on the Samba mailing lists. -

    Configuring Roaming Profiles for a Few Users or Groups

    +

    Configuring Roaming Profiles for a Few Users or Groups

    With Samba-2.2.x, the choice you have is to enable or disable roaming profiles support. It is a global-only setting. The default is to have roaming profiles, and the default path will locate them in the user's home directory. @@ -605,7 +605,7 @@ to apply only to certain machines, then on those machines on which roaming profi it is necessary to disable roaming profile handling in the registry of each such machine.

    With Samba-3, you can have a global profile setting in smb.conf, and you can override this by -per-user settings using the Domain User Manager (as with MS Windows NT4/200x).

    In any case, you can configure only one profile per user. That profile can be either:

    • A profile unique to that user.

    • A mandatory profile (one the user cannot change).

    • A group profile (really should be mandatory that is, unchangable).

    Cannot Use Roaming Profiles

    A user requested the following: “ I do not want roaming profiles to be implemented. I want +per-user settings using the Domain User Manager (as with MS Windows NT4/200x).

    In any case, you can configure only one profile per user. That profile can be either:

    • A profile unique to that user.

    • A mandatory profile (one the user cannot change).

    • A group profile (really should be mandatory that is, unchangable).

    Cannot Use Roaming Profiles

    A user requested the following: “ I do not want roaming profiles to be implemented. I want to give users a local profile alone. I am totally lost with this error. For the past two days I tried everything, I googled around but found no useful pointers. Please help me. ”

    The choices are:

    Local profiles

    I know of no registry keys that will allow autodeletion of LOCAL profiles on log out.

    Roaming profiles

    As a user logs onto the network, a centrally @@ -625,18 +625,18 @@ workstation, but they harvest the fruits of folly (and ignorance).

    The p changed as well as good discipline make for a problem-free site.

    Microsoft's answer to the PST problem is to store all email in an MS Exchange Server backend. This removes the need for a PST file.

    Local profiles mean:

    • If each machine is used by many users, then much local disk storage is needed for local profiles.

    • Every workstation the user logs into has - its own profile; these can be very different from machine to machine.

    On the other hand, use of roaming profiles means:

    • The network administrator can control the desktop environment of all users.

    • Use of mandatory profiles drastically reduces network management overheads.

    • In the long run, users will experience fewer problems.

    Changing the Default Profile

    “When the client logs onto the domain controller, it searches + its own profile; these can be very different from machine to machine.

    On the other hand, use of roaming profiles means:

    • The network administrator can control the desktop environment of all users.

    • Use of mandatory profiles drastically reduces network management overheads.

    • In the long run, users will experience fewer problems.

    Changing the Default Profile

    “When the client logs onto the domain controller, it searches for a profile to download. Where do I put this default profile?”

    - + First, the Samba server needs to be configured as a domain controller. This can be done by -setting in smb.conf:

    security = user
    os level = 32 (or more)
    domain logons = Yes

    There must be a [netlogon] share that is world readable. It is +setting in smb.conf:

    security = user
    os level = 32 (or more)
    domain logons = Yes

    There must be a [netlogon] share that is world readable. It is a good idea to add a logon script to preset printer and drive connections. There is also a facility for automatically synchronizing the workstation time clock with that of the logon server (another good thing to do).

    Note

    To invoke autodeletion of roaming profiles from the local workstation cache (disk storage), use the Group Policy Editor to create a file called NTConfig.POL with the appropriate entries. This file needs to be located in the netlogon share root directory.

    Windows clients need to be members of the domain. Workgroup machines do not use network logons, -so they do not interoperate with domain profiles.

    For roaming profiles, add to smb.conf:

    logon path = \\%N\profiles\%U
    # Default logon drive is Z:
    logon drive = H:
    # This requires a PROFILES share that is world writable.

    Debugging Roaming Profiles and NT4-style Domain Policies

    +so they do not interoperate with domain profiles.

    For roaming profiles, add to smb.conf:

    logon path = \\%N\profiles\%U
    # Default logon drive is Z:
    logon drive = H:
    # This requires a PROFILES share that is world writable.

    Debugging Roaming Profiles and NT4-style Domain Policies

    Roaming profiles and domain policies are implemented via USERENV.DLL. Microsoft Knowledge Base articles 221833 and 154120 diff --git a/docs/htmldocs/Samba3-HOWTO/SWAT.html b/docs/htmldocs/Samba3-HOWTO/SWAT.html index fe45b1083d..6c8ac95424 100644 --- a/docs/htmldocs/Samba3-HOWTO/SWAT.html +++ b/docs/htmldocs/Samba3-HOWTO/SWAT.html @@ -1,27 +1,27 @@ -Chapter 37. SWAT: The Samba Web Administration Tool

    Chapter 37. SWAT: The Samba Web Administration Tool
    Prev Part IV. Migration and Updating Next

    Chapter 37. SWAT: The Samba Web Administration Tool

    John H. Terpstra

    Samba Team

    April 21, 2003

    Table of Contents

    Features and Benefits
    Guidelines and Technical Tips
    Validate SWAT Installation
    Enabling SWAT for Use
    Securing SWAT through SSL
    Enabling SWAT Internationalization Support
    Overview and Quick Tour
    The SWAT Home Page
    Global Settings
    Share Settings
    Printers Settings
    The SWAT Wizard
    The Status Page
    The View Page
    The Password Change Page

    - - - +Chapter 37. SWAT: The Samba Web Administration Tool

    Chapter 37. SWAT: The Samba Web Administration Tool
    Prev Part IV. Migration and Updating Next

    Chapter 37. SWAT: The Samba Web Administration Tool

    John H. Terpstra

    Samba Team

    April 21, 2003

    Table of Contents

    Features and Benefits
    Guidelines and Technical Tips
    Validate SWAT Installation
    Enabling SWAT for Use
    Securing SWAT through SSL
    Enabling SWAT Internationalization Support
    Overview and Quick Tour
    The SWAT Home Page
    Global Settings
    Share Settings
    Printers Settings
    The SWAT Wizard
    The Status Page
    The View Page
    The Password Change Page

    + + + There are many and varied opinions regarding the usefulness of SWAT. No matter how hard one tries to produce the perfect configuration tool, it remains an object of personal taste. SWAT is a tool that allows Web-based configuration of Samba. It has a wizard that may help to get Samba configured quickly, it has context-sensitive help on each smb.conf parameter, it provides for monitoring of current state of connection information, and it allows networkwide MS Windows network password management. -

    Features and Benefits

    - +

    Features and Benefits

    + SWAT is a facility that is part of the Samba suite. The main executable is called swat and is invoked by the internetworking super daemon. See appropriate section for details.

    - + SWAT uses integral Samba components to locate parameters supported by the particular version of Samba. Unlike tools and utilities that are external to Samba, SWAT is always up to date as known Samba parameters change. SWAT provides context-sensitive help for each configuration parameter, directly from man page entries.

    - - - + + + Some network administrators believe that it is a good idea to write systems documentation inside configuration files, and for them SWAT will always be a nasty tool. SWAT does not store the configuration file in any intermediate form; rather, it stores only the @@ -30,38 +30,38 @@ those parameters that are at other than the default settings. The result is that as well as parameters that are no longer supported, will be lost from the smb.conf file. Additionally, the parameters will be written back in internal ordering.

    Note

    - + Before using SWAT, please be warned SWAT will completely replace your smb.conf with a fully optimized file that has been stripped of all comments you might have placed there and only nondefault settings will be written to the file. -

    Guidelines and Technical Tips

    - +

    Guidelines and Technical Tips

    + This section aims to unlock the dark secrets behind how SWAT may be made to work, how it can be made more secure, and how to solve internationalization support problems. -

    Validate SWAT Installation

    - +

    Validate SWAT Installation

    + The very first step that should be taken before attempting to configure a host system for SWAT operation is to check that it is installed. This may seem a trivial point to some, but several Linux distributions do not install SWAT by default, even though they do ship an installable binary support package containing SWAT on the distribution media.

    - + When you have confirmed that SWAT is installed, it is necessary to validate that the installation includes the binary swat file as well as all the supporting text and Web files. A number of operating system distributions in the past have failed to include the necessary support files, even though the swat binary executable file was installed.

    - - + + Finally, when you are sure that SWAT has been fully installed, please check that SWAT is enabled in the control file for the internetworking super-daemon (inetd or xinetd) that is used on your operating system platform. -

    Locating the SWAT File

    - - - +

    Locating the SWAT File

    + + + To validate that SWAT is installed, first locate the swat binary file on the system. It may be found under the following directories:

    /usr/local/samba/bin the default Samba location
    /usr/sbin the default location on most Linux systems
    /opt/samba/bin

    @@ -71,9 +71,9 @@ by the administrator who compiled and installed Samba. There are a number of methods that may be used to locate the swat binary file. The following methods may be helpful.

    - - - + + + If swat is in your current operating system search path, it will be easy to find it. You can ask what are the command-line options for swat as shown here: 

    @@ -91,7 +91,7 @@ Common samba options:
   -l, --log-basename=LOGFILEBASE       Basename for log/debug files
   -V, --version                        Print version

    -

    Locating the SWAT Support Files

    +

    Locating the SWAT Support Files

    Now that you have found that swat is in the search path, it is easy to identify where the file is located. Here is another simple way this may be done: 

    @@ -173,7 +173,7 @@ implementation. The control file (or files) can be located in the file
 or in a similar location.
 
    
 The control entry for the older style file might be:
-
+
 
     	# swat is the Samba Web Administration Tool
 	swat stream tcp nowait.400 root /usr/sbin/swat swat
@@ -201,10 +201,10 @@ In the above, the default setting for disable
 This means that SWAT is disabled. To enable use of SWAT, set this parameter to no
 as shown.
 
    
-
-
-
-
+
+
+
+
 Both of the previous examples assume that the swat binary has been
 located in the /usr/sbin directory. In addition to the above,
 SWAT will use a directory access point from which it will load its Help files
@@ -212,8 +212,8 @@ as well as other control information. The default location for this on most Linu
 systems is in the directory /usr/share/samba/swat. The default
 location using Samba defaults will be /usr/local/samba/swat.
 
    
-
-
+
+
 Access to SWAT will prompt for a logon. If you log onto SWAT as any non-root user,
 the only permission allowed is to view certain aspects of configuration as well as
 access to the password change facility. The buttons that will be exposed to the non-root
@@ -225,21 +225,21 @@ As long as you log onto SWAT as the user rootHOME, GLOBALS, SHARES, PRINTERS, 
 WIZARD, STATUS, VIEW, and PASSWORD.
-

    Securing SWAT through SSL

    - - +

    Securing SWAT through SSL

    + + Many people have asked about how to set up SWAT with SSL to allow for secure remote administration of Samba. Here is a method that works, courtesy of Markus Krieger.

    Modifications to the SWAT setup are as follows:

    1. - + Install OpenSSL.

    2. - - + + Generate certificate and private key. - + 

       root# /usr/bin/openssl req -new -x509 -days 365 -nodes -config \
 	/usr/share/doc/packages/stunnel/stunnel.cnf \
@@ -247,7 +247,7 @@ Modifications to the SWAT setup are as follows:

    3. Remove SWAT entry from [x]inetd.

    4. - + Start stunnel. 

      @@ -255,7 +255,7 @@ Modifications to the SWAT setup are as follows:
 	 -l /usr/local/samba/bin/swat swat

    Afterward, simply connect to SWAT by using the URL https://myhost:901, accept the certificate, and the SSL connection is up. -

    Enabling SWAT Internationalization Support

    +

    Enabling SWAT Internationalization Support

    SWAT can be configured to display its messages to match the settings of the language configurations of your Web browser. It will be passed to SWAT in the Accept-Language header of the HTTP request. @@ -267,14 +267,14 @@ To enable this feature:

  • Set your browsers language setting.

    • - - - - + + + + The name of the msg file is the same as the language ID sent by the browser. For example, en means English, ja means Japanese, fr means French.

    - + If you do not like some of messages, or there are no msg files for your locale, you can create them simply by copying the en.msg files to the directory for “your language ID.msg” and filling in proper strings @@ -284,20 +284,20 @@ to each “msgstr”. For example, in

    - + and so on. If you find a mistake or create a new msg file, please email it to us so we will consider it in the next release of Samba. The msg file should be encoded in UTF-8.

    - + Note that if you enable this feature and the display charset is not matched to your browser's setting, the SWAT display may be corrupted. In a future version of Samba, SWAT will always display messages with UTF-8 encoding. You will then not need to set this smb.conf file parameter. -

    Overview and Quick Tour

    +

    Overview and Quick Tour

    SWAT is a tool that may be used to configure Samba or just to obtain useful links to important reference materials such as the contents of this book as well as other documents that have been found useful for solving Windows networking problems. -

    The SWAT Home Page

    +

    The SWAT Home Page

    The SWAT title page provides access to the latest Samba documentation. The manual page for each Samba component is accessible from this page, as are the Samba3-HOWTO (this document) as well as the O'Reilly book “Using Samba.” @@ -312,7 +312,7 @@ because it runs SWAT without authentication and with full administrative ability changes to smb.conf as well as general operation with root privileges. The option that creates this ability is the -a flag to SWAT. Do not use this in a production environment. -

    Global Settings

    +

    Global Settings

    The GLOBALS button exposes a page that allows configuration of the global parameters in smb.conf. There are two levels of exposure of the parameters:

    • @@ -332,7 +332,7 @@ your changes will be lost. SWAT has context-sensitive help. To find out what each parameter is for, simply click on the Help link to the left of the configuration parameter. -

    Share Settings

    +

    Share Settings

    To affect a currently configured share, simply click on the pull-down button between the Choose Share and the Delete Share buttons and select the share you wish to operate on. To edit the settings, @@ -343,7 +343,7 @@ click on the To create a new share, next to the button labeled Create Share, enter into the text field the name of the share to be created, then click on the Create Share button. -

    Printers Settings

    +

    Printers Settings

    To affect a currently configured printer, simply click on the pull-down button between the Choose Printer and the Delete Printer buttons and select the printer you wish to operate on. To edit the settings, @@ -354,7 +354,7 @@ click on the To create a new printer, next to the button labeled Create Printer, enter into the text field the name of the share to be created, then click on the Create Printer button. -

    The SWAT Wizard

    +

    The SWAT Wizard

    The purpose of the SWAT Wizard is to help the Microsoft-knowledgeable network administrator to configure Samba with a minimum of effort.

    @@ -370,7 +370,7 @@ Finally, there are a limited set of options that determine what type of server S will be configured for, whether it will be a WINS server, participate as a WINS client, or operate with no WINS support. By clicking one button, you can elect to expose (or not) user home directories. -

    The Status Page

    +

    The Status Page

    The status page serves a limited purpose. First, it allows control of the Samba daemons. The key daemons that create the Samba server environment are smbd, nmbd, and winbindd.

    @@ -381,11 +381,11 @@ conditions with minimal effort.

    Finally, the status page may be used to terminate specific smbd client connections in order to free files that may be locked. -

    The View Page

    +

    The View Page

    The view page allows you to view the optimized smb.conf file and, if you are particularly masochistic, permits you also to see all possible global configuration parameters and their settings. -

    The Password Change Page

    +

    The Password Change Page

    The password change page is a popular tool that allows the creation, deletion, deactivation, and reactivation of MS Windows networking users on the local machine. You can also use this tool to change a local password for a user account. diff --git a/docs/htmldocs/Samba3-HOWTO/SambaHA.html b/docs/htmldocs/Samba3-HOWTO/SambaHA.html index ade4fadaf0..bcd607be3e 100644 --- a/docs/htmldocs/Samba3-HOWTO/SambaHA.html +++ b/docs/htmldocs/Samba3-HOWTO/SambaHA.html @@ -1,17 +1,17 @@ -Chapter 32. High Availability

    Chapter 32. High Availability
    Prev Part III. Advanced Configuration Next

    Chapter 32. High Availability

    John H. Terpstra

    Samba Team

    Jeremy Allison

    Samba Team

    Table of Contents

    Features and Benefits
    Technical Discussion
    The Ultimate Goal
    Why Is This So Hard?
    A Simple Solution
    High-Availability Server Products
    MS-DFS: The Poor Man's Cluster
    Conclusions

    Features and Benefits

    - - - +Chapter 32. High Availability

    Chapter 32. High Availability
    Prev Part III. Advanced Configuration Next

    Chapter 32. High Availability

    John H. Terpstra

    Samba Team

    Jeremy Allison

    Samba Team

    Table of Contents

    Features and Benefits
    Technical Discussion
    The Ultimate Goal
    Why Is This So Hard?
    A Simple Solution
    High-Availability Server Products
    MS-DFS: The Poor Man's Cluster
    Conclusions

    Features and Benefits

    + + + Network administrators are often concerned about the availability of file and print services. Network users are inclined toward intolerance of the services they depend on to perform vital task responsibilities.

    A sign in a computer room served to remind staff of their responsibilities. It read:

    - - - - + + + + All humans fail, in both great and small ways we fail continually. Machines fail too. Computers are machines that are managed by humans, the fallout from failure can be spectacular. Your responsibility is to deal with failure, to anticipate it @@ -21,9 +21,9 @@ Are your actions part of the problem or part of the solution? If we are to deal with failure in a planned and productive manner, then first we must understand the problem. That is the purpose of this chapter.

    - - - + + + Parenthetically, in the following discussion there are seeds of information on how to provision a network infrastructure against failure. Our purpose here is not to provide a lengthy dissertation on the subject of high availability. Additionally, we have made @@ -32,37 +32,37 @@ solutions; instead we present an overview of the issues in the hope that someone rise to the challenge of providing a detailed document that is focused purely on presentation of the current state of knowledge and practice in high availability as it applies to the deployment of Samba and other CIFS/SMB technologies. -

    Technical Discussion

    - - - +

    Technical Discussion

    + + + The following summary was part of a presentation by Jeremy Allison at the SambaXP 2003 conference that was held at Goettingen, Germany, in April 2003. Material has been added from other sources, but it was Jeremy who inspired the structure that follows. -

    The Ultimate Goal

    - - - +

    The Ultimate Goal

    + + + All clustering technologies aim to achieve one or more of the following:

    • Obtain the maximum affordable computational power.

    • Obtain faster program execution.

    • Deliver unstoppable services.

    • Avert points of failure.

    • Exact most effective utilization of resources.

    A clustered file server ideally has the following properties: - - - - -

    • All clients can connect transparently to any server.

    • A server can fail and clients are transparently reconnected to another server.

    • All servers serve out the same set of files.

    • All file changes are immediately seen on all servers.

      • Requires a distributed file system.

    • Infinite ability to scale by adding more servers or disks.

    Why Is This So Hard?

    + + + + +

    • All clients can connect transparently to any server.

    • A server can fail and clients are transparently reconnected to another server.

    • All servers serve out the same set of files.

    • All file changes are immediately seen on all servers.

      • Requires a distributed file system.

    • Infinite ability to scale by adding more servers or disks.

    Why Is This So Hard?

    In short, the problem is one of state.

    • - + All TCP/IP connections are dependent on state information.

      - + The TCP connection involves a packet sequence number. This sequence number would need to be dynamically updated on all machines in the cluster to effect seamless TCP failover.

    • - - + + CIFS/SMB (the Windows networking protocols) uses TCP connections.

      This means that from a basic design perspective, failover is not @@ -71,91 +71,91 @@ from other sources, but it was Jeremy who inspired the structure that follows. All current SMB clusters are failover solutions they rely on the clients to reconnect. They provide server failover, but clients can lose information due to a server failure. - +

  • Servers keep state information about client connections. -

    • CIFS/SMB involves a lot of state.

    • Every file open must be compared with other open files +

      • CIFS/SMB involves a lot of state.

      • Every file open must be compared with other open files to check share modes.

      -

    The Front-End Challenge

    - - - - - - - +

    • The Front-End Challenge

    + + + + + + + To make it possible for a cluster of file servers to appear as a single server that has one name and one IP address, the incoming TCP data streams from clients must be processed by the front-end virtual server. This server must de-multiplex the incoming packets at the SMB protocol layer level and then feed the SMB packet to different servers in the cluster.

    - - + + One could split all IPC$ connections and RPC calls to one server to handle printing and user lookup requirements. RPC printing handles are shared between different IPC4 sessions it is hard to split this across clustered servers!

    Conceptually speaking, all other servers would then provide only file services. This is a simpler problem to concentrate on. -

    Demultiplexing SMB Requests

    - - - - +

    Demultiplexing SMB Requests

    + + + + De-multiplexing of SMB requests requires knowledge of SMB state information, all of which must be held by the front-end virtual server. This is a perplexing and complicated problem to solve.

    - - - + + + Windows XP and later have changed semantics so state information (vuid, tid, fid) must match for a successful operation. This makes things simpler than before and is a positive step forward.

    - - + + SMB requests are sent by vuid to their associated server. No code exists today to effect this solution. This problem is conceptually similar to the problem of correctly handling requests from multiple requests from Windows 2000 Terminal Server in Samba.

    - + One possibility is to start by exposing the server pool to clients directly. This could eliminate the de-multiplexing step. -

    The Distributed File System Challenge

    - +

    The Distributed File System Challenge

    + There exists many distributed file systems for UNIX and Linux.

    - - - - - - + + + + + + Many could be adopted to backend our cluster, so long as awareness of SMB semantics is kept in mind (share modes, locking, and oplock issues in particular). Common free distributed file systems include: - - - - + + + +

    • NFS

    • AFS

    • OpenGFS

    • Lustre

    - + The server pool (cluster) can use any distributed file system backend if all SMB semantics are performed within this pool. -

    Restrictive Constraints on Distributed File Systems

    - - - - +

    Restrictive Constraints on Distributed File Systems

    + + + + Where a clustered server provides purely SMB services, oplock handling may be done within the server pool without imposing a need for this to be passed to the backend file system pool.

    - - + + On the other hand, where the server pool also provides NFS or other file services, it will be essential that the implementation be oplock-aware so it can interoperate with SMB services. This is a significant challenge today. A failure @@ -163,25 +163,25 @@ from other sources, but it was Jeremy who inspired the structure that follows. sorely noted by users of Microsoft Windows clients.

    Last, all state information must be shared across the server pool. -

    Server Pool Communications

    - - - - +

    Server Pool Communications

    + + + + Most backend file systems support POSIX file semantics. This makes it difficult to push SMB semantics back into the file system. POSIX locks have different properties and semantics from SMB locks.

    - - - + + + All smbd processes in the server pool must of necessity communicate very quickly. For this, the current tdb file structure that Samba uses is not suitable for use across a network. Clustered smbds must use something else. -

    Server Pool Communications Demands

    +

    Server Pool Communications Demands

    High-speed interserver communications in the server pool is a design prerequisite for a fully functional system. Possibilities for this include: -

    • +

      • Proprietary shared memory bus (example: Myrinet or SCI [scalable coherent interface]). These are high-cost items.

      • @@ -191,7 +191,7 @@ from other sources, but it was Jeremy who inspired the structure that follows.

      We have yet to identify metrics for performance demands to enable this to happen effectively. -

    Required Modifications to Samba

    +

    Required Modifications to Samba

    Samba needs to be significantly modified to work with a high-speed server interconnect system to permit transparent failover clustering.

    @@ -200,8 +200,8 @@ from other sources, but it was Jeremy who inspired the structure that follows. The locking database, oplock notifications, and the share mode database.

  • - - + + Failure semantics need to be defined. Samba behaves the same way as Windows. When oplock messages fail, a file open request is allowed, but this is potentially dangerous in a clustered environment. So how should interserver @@ -209,58 +209,58 @@ from other sources, but it was Jeremy who inspired the structure that follows.

  • Should this be implemented using a point-to-point lock manager, or can this be done using multicast techniques? -

    • A Simple Solution

    - - - +

    A Simple Solution

    + + + Allowing failover servers to handle different functions within the exported file system removes the problem of requiring a distributed locking protocol.

    - - + + If only one server is active in a pair, the need for high-speed server interconnect is avoided. This allows the use of existing high-availability solutions, instead of inventing a new one. This simpler solution comes at a price the cost of which is the need to manage a more complex file name space. Since there is now not a single file system, administrators must remember where all services are located a complexity not easily dealt with.

    - + The virtual server is still needed to redirect requests to backend servers. Backend file space integrity is the responsibility of the administrator. -

    High-Availability Server Products

    - - - - - +

    High-Availability Server Products

    + + + + + Failover servers must communicate in order to handle resource failover. This is essential for high-availability services. The use of a dedicated heartbeat is a common technique to introduce some intelligence into the failover process. This is often done over a dedicated link (LAN or serial).

    - - - - - + + + + + Many failover solutions (like Red Hat Cluster Manager and Microsoft Wolfpack) can use a shared SCSI of Fiber Channel disk storage array for failover communication. Information regarding Red Hat high availability solutions for Samba may be obtained from www.redhat.com.

    - + The Linux High Availability project is a resource worthy of consultation if your desire is to build a highly available Samba file server solution. Please consult the home page at www.linux-ha.org/.

    - - + + Front-end server complexity remains a challenge for high availability because it must deal gracefully with backend failures, while at the same time providing continuity of service to all network clients. -

    MS-DFS: The Poor Man's Cluster

    - - +

    MS-DFS: The Poor Man's Cluster

    + + MS-DFS links can be used to redirect clients to disparate backend servers. This pushes complexity back to the network client, something already included by Microsoft. MS-DFS creates the illusion of a simple, continuous file system name space that works even @@ -268,4 +268,4 @@ from other sources, but it was Jeremy who inspired the structure that follows.

    Above all, at the cost of complexity of management, a distributed system (pseudo-cluster) can be created using existing Samba functionality. -

    Conclusions

    • Transparent SMB clustering is hard to do!

    • Client failover is the best we can do today.

    • Much more work is needed before a practical and manageable high-availability transparent cluster solution will be possible.

    • MS-DFS can be used to create the illusion of a single transparent cluster.

    Prev Up Next
    Chapter 31. Backup Techniques Home Chapter 33. Handling Large Directories
    +

    Conclusions

    • Transparent SMB clustering is hard to do!

    • Client failover is the best we can do today.

    • Much more work is needed before a practical and manageable high-availability transparent cluster solution will be possible.

    • MS-DFS can be used to create the illusion of a single transparent cluster.

    Prev Up Next
    Chapter 31. Backup Techniques Home Chapter 33. Handling Large Directories
    diff --git a/docs/htmldocs/Samba3-HOWTO/ServerType.html b/docs/htmldocs/Samba3-HOWTO/ServerType.html index ad216dd937..f0611aeddb 100644 --- a/docs/htmldocs/Samba3-HOWTO/ServerType.html +++ b/docs/htmldocs/Samba3-HOWTO/ServerType.html @@ -1,6 +1,6 @@ -Chapter 3. Server Types and Security Modes
    Chapter 3. Server Types and Security Modes
    Prev Part II. Server Configuration Basics Next

    Chapter 3. Server Types and Security Modes

    Andrew Tridgell

    Samba Team

    Jelmer R. Vernooij

    The Samba Team

    John H. Terpstra

    Samba Team

    Table of Contents

    Features and Benefits
    Server Types
    Samba Security Modes
    User Level Security
    Share-Level Security
    Domain Security Mode (User-Level Security)
    ADS Security Mode (User-Level Security)
    Server Security (User Level Security)
    Password Checking
    Common Errors
    What Makes Samba a Server?
    What Makes Samba a Domain Controller?
    What Makes Samba a Domain Member?
    Constantly Losing Connections to Password Server
    Stand-alone Server is converted to Domain Controller Now User accounts don't work

    - +Chapter 3. Server Types and Security Modes

    Chapter 3. Server Types and Security Modes
    Prev Part II. Server Configuration Basics Next

    Chapter 3. Server Types and Security Modes

    Andrew Tridgell

    Samba Team

    Jelmer R. Vernooij

    The Samba Team

    John H. Terpstra

    Samba Team

    Table of Contents

    Features and Benefits
    Server Types
    Samba Security Modes
    User Level Security
    Share-Level Security
    Domain Security Mode (User-Level Security)
    ADS Security Mode (User-Level Security)
    Server Security (User Level Security)
    Password Checking
    Common Errors
    What Makes Samba a Server?
    What Makes Samba a Domain Controller?
    What Makes Samba a Domain Member?
    Constantly Losing Connections to Password Server
    Stand-alone Server is converted to Domain Controller Now User accounts don't work

    + This chapter provides information regarding the types of server that Samba may be configured to be. A Microsoft network administrator who wishes to migrate to or use Samba will want to know the meaning, within a Samba context, of terms familiar to the MS Windows administrator. This means that it is essential also to @@ -14,7 +14,7 @@ A question often asked is, “Why would I want to use Sa highlights features and benefits. We hope that the information provided will help to answer this question. Be warned though, we want to be fair and reasonable, so not all features are positive toward Samba. The benefit may be on the side of our competition. -

    Features and Benefits

    +

    Features and Benefits

    Two men were walking down a dusty road, when one suddenly kicked up a small red stone. It hurt his toe and lodged in his sandal. He took the stone out and cursed it with a passion and fury befitting his anguish. The other looked at the stone and said, “This is a garnet. @@ -25,8 +25,8 @@ Like it or not, Samba is like that stone. Treat it the right way and it can brin pleasure, but if you are forced to use it and have no time for its secrets, then it can be a source of discomfort.

    - - + + Samba started out as a project that sought to provide interoperability for MS Windows 3.x clients with a UNIX server. It has grown up a lot since its humble beginnings and now provides features and functionality fit for large-scale deployment. It also has some warts. In sections @@ -34,41 +34,41 @@ like this one, we tell of both.

    So, what are the benefits of the features mentioned in this chapter?

    • - + Samba-3 can replace an MS Windows NT4 domain controller.

    • - + Samba-3 offers excellent interoperability with MS Windows NT4-style domains as well as natively with Microsoft Active Directory domains.

    • - + Samba-3 permits full NT4-style interdomain trusts.

    • - - + + Samba has security modes that permit more flexible authentication than is possible with MS Windows NT4 domain controllers.

    • - - + + Samba-3 permits use of multiple concurrent account database backends. (Encrypted passwords that are stored in the account database are in formats that are unique to Windows networking).

    • - + The account database backends can be distributed and replicated using multiple methods. This gives Samba-3 greater flexibility than MS Windows NT4 and in many cases a significantly higher utility than Active Directory domains with MS Windows 200x. -

    Server Types

    - +

    Server Types

    + Administrators of Microsoft networks often refer to three different types of servers:

    • Domain Controller

      • Primary Domain Controller (PDC)

      • Backup Domain Controller (BDC)

      • ADS Domain Controller

    • Domain Member Server

      • Active Directory Domain Server

      • NT4 Style Domain Domain Server

    • Standalone Server

    - - - - + + + + The chapters covering domain control (Domain Control), backup domain control (Backup Domain Control), and domain membership (Domain Membership) provide @@ -76,27 +76,27 @@ pertinent information regarding Samba configuration for each of these server rol You are strongly encouraged to become intimately familiar with these chapters because they lay the foundation for deployment of Samba domain security.

    - + A Standalone server is autonomous in respect of the source of its account backend. Refer to Standalone Servers to gain a wider appreciation of what is meant by a server being configured as a standalone server. -

    Samba Security Modes

    - +

    Samba Security Modes

    + In this section, the function and purpose of Samba's security modes are described. An accurate understanding of how Samba implements each security mode as well as how to configure MS Windows clients for each mode will significantly reduce user complaints and administrator heartache.

    - - + + Microsoft Windows networking uses a protocol that was originally called the Server Message Block (SMB) protocol. Since some time around 1996 the protocol has been better known as the Common Internet Filesystem (CIFS) protocol.

    - - + + In the SMB/CIFS networking world, there are only two types of security: user-level and share level. We refer to these collectively as security levels. In implementing these two security levels, Samba provides flexibilities that are not available with MS Windows @@ -116,43 +116,43 @@ available and whether an action is allowed. The term client refers to all agents whether it is a Windows workstation, a Windows server, another Samba server, or any vanilla SMB or CIFS client application (e.g., smbclient) that make use of services provided by an SMB/CIFS server. -

    User Level Security

    - +

    User Level Security

    + We describe user-level security first because its simpler. In user-level security, the client sends a session setup request directly following protocol negotiation. This request provides a username and password. The server can either accept or reject that username/password combination. At this stage the server has no idea what share the client will eventually try to connect to, so it can't base the accept/reject on anything other than:

    1. the username/password.

    2. the name of the client machine.

    - + If the server accepts the username/password credentials, the client expects to be able to mount shares (using a tree connection) without further specifying a password. It expects that all access rights will be as the username/password credentials set that was specified in the initial session setup.

    - + It is also possible for a client to send multiple session setup requests. When the server responds, it gives the client a uid to use as an authentication tag for that username/password. The client can maintain multiple authentication contexts in this way (WinDD is an example of an application that does this).

    - - - - - + + + + + Windows networking user account names are case-insensitive, meaning that upper-case and lower-case characters in the account name are considered equivalent. They are said to be case-preserving, but not case significant. Windows and LanManager systems previous to Windows NT version 3.10 have case-insensitive passwords that were not necessarilty case-preserving. All Windows NT family systems treat passwords as case-preserving and case-sensitive. -

    Example Configuration

    +

    Example Configuration

    The smb.conf parameter that sets user-level security is: -

    security = user

    +

    security = user

    This is the default setting since Samba-2.2.x. -

    Share-Level Security

    - - +

    Share-Level Security

    + + In share-level security, the client authenticates itself separately for each share. It sends a password along with each tree connection request (share mount), but it does not explicitly send a username with this operation. The client expects a password to be associated with each share, independent of the user. This means @@ -171,9 +171,9 @@ home directories) and any users listed in the - - + + + Where the list of possible user names is not provided, Samba makes a UNIX system call to find the user account that has a password that matches the one provided from the standard account database. On a system that has no name service switch (NSS) facility, such lookups will be from the /etc/passwd @@ -184,21 +184,21 @@ passwd: files nis ldap shadow: files nis ldap group: files nis ldap

    - - - + + + In the example shown here (not likely to be used in practice) the lookup will check /etc/passwd and /etc/group, if not found it will check NIS, then LDAP. -

    Example Configuration

    +

    Example Configuration

    The smb.conf parameter that sets share-level security is: -

    security = share

    Domain Security Mode (User-Level Security)

    - - - - - - +

    security = share

    Domain Security Mode (User-Level Security)

    + + + + + + Domain security provides a mechanism for storing all user and group accounts in a central, shared, account repository. The centralized account repository is shared between domain (security) controllers. Servers that act as domain controllers provide authentication and validation services to all machines that participate in @@ -207,21 +207,21 @@ maintaining the integrity of the security account database. Backup domain contro logon and authentication services. Usually, BDCs will answer network logon requests more responsively than will a PDC.

    - - - - + + + + When Samba is operating in security = domain mode, the Samba server has a domain security trust account (a machine account) and causes all authentication requests to be passed through to the domain controllers. In other words, this configuration makes the Samba server a domain member server, even when it is in fact acting as a domain controller. All machines that participate in domain security must have a machine account in the security database.

    - - + + Within the domain security environment, the underlying security architecture uses user-level security. Even machines that are domain members must authenticate on startup. The machine account consists of an account entry in the accounts database, the name of which is the NetBIOS name of the machine and of which the password @@ -231,30 +231,30 @@ it cannot be trusted. The machine account is referred to as a machine trust acco

    There are three possible domain member configurations:

    1. Primary domain controller (PDC) - of which there is one per domain.

    2. Backup domain controller (BDC) - of which there can be any number per domain.

    3. Domain member server (DMS) - of which there can be any number per domain.

    - + We will discuss each of these in separate chapters. For now, we are most interested in basic DMS configuration. -

    Example Configuration

    +

    Example Configuration

    Samba as a Domain Member Server

    - + This method involves addition of the following parameters in the smb.conf file: -

    security = domain
    workgroup = MIDEARTH

    +

    security = domain
    workgroup = MIDEARTH

    In order for this method to work, the Samba server needs to join the MS Windows NT security domain. This is done as follows: - - + +

    1. On the MS Windows NT domain controller, using the Server Manager, add a machine account for the Samba server.

    2. On the UNIX/Linux system execute:

      root# net rpc join -U administrator%password

    Note

    - + Samba-2.2.4 and later Samba 2.2.x series releases can autojoin a Windows NT4-style domain just by executing: 

     root# smbpasswd -j DOMAIN_NAME -r PDC_NAME \
 	 -U Administrator%password

    - + Samba-3 can do the same by executing: 

     root# net rpc join -U Administrator%password
@@ -262,26 +262,26 @@ Samba-3 can do the same by executing:
 It is not necessary with Samba-3 to specify the DOMAIN_NAME or the
 PDC_NAME, as it figures this out from the smb.conf file settings.

    - - - + + + Use of this mode of authentication requires there to be a standard UNIX account for each user in order to assign a UID once the account has been authenticated by the Windows domain controller. This account can be blocked to prevent logons by clients other than MS Windows through means such as setting an invalid shell in the /etc/passwd entry. The best way to allocate an invalid shell to a user account is to set the shell to the file /bin/false.

    - - + + Domain controllers can be located anywhere that is convenient. The best advice is to have a BDC on every physical network segment, and if the PDC is on a remote network segment the use of WINS (see Network Browsing for more information) is almost essential.

    An alternative to assigning UIDs to Windows users on a Samba member server is presented in Winbind, Winbind: Use of Domain Accounts.

    For more information regarding domain membership, Domain Membership. -

    ADS Security Mode (User-Level Security)

    - - +

    ADS Security Mode (User-Level Security)

    + + Both Samba-2.2, and Samba-3 can join an Active Directory domain using NT4 style RPC based security. This is possible if the domain is run in native mode. Active Directory in native mode perfectly allows NT4-style domain members. This is contrary to popular belief. @@ -292,24 +292,24 @@ your machines are running Windows 2000 and above and all use Kerberos. In this c domain, would still require NT-compatible authentication data. Samba in AD-member mode can accept Kerberos tickets.

    - - + + Sites that use Microsoft Windows active directory services (ADS) should be aware of the significance of the terms: native mode and mixed mode ADS operation. The term realm is used to describe a Kerberos-based security architecture (such as is used by Microsoft ADS). -

    Example Configuration

    realm = your.kerberos.REALM
    security = ADS

    +

    Example Configuration

    realm = your.kerberos.REALM
    security = ADS

    The following parameter may be required: -

    password server = your.kerberos.server

    +

    password server = your.kerberos.server

    Please refer to Domain Membership, and Samba ADS Domain Membership for more information regarding this configuration option. -

    Server Security (User Level Security)

    +

    Server Security (User Level Security)

    Server security mode is left over from the time when Samba was not capable of acting as a domain member server. It is highly recommended not to use this feature. Server security mode has many drawbacks that include:

    • Potential account lockout on MS Windows NT4/200x password servers.

    • Lack of assurance that the password server is the one specified.

    • Does not work with Winbind, which is particularly needed when storing profiles remotely.

    • This mode may open connections to the password server and keep them open for extended periods.

    • Security on the Samba server breaks badly when the remote password server suddenly shuts down.

    • With this mode there is NO security account in the domain that the password server belongs to for the Samba server.

    - - + + In server security mode the Samba server reports to the client that it is in user-level security. The client then does a session setup as described earlier. The Samba server takes the username/password that the client sends and attempts to log into the password server by sending exactly the same @@ -317,8 +317,8 @@ username/password that it got from the client. If that server is in user-level s password, then Samba accepts the client's connection. This parameter allows the Samba server to use another SMB server as the password server.

    - - + + You should also note that at the start of all this, when the server tells the client what security level it is in, it also tells the client if it supports encryption. If it does, it supplies the client with a random cryptkey. The client will then send all @@ -330,24 +330,24 @@ user mode server. This requires an additional parameter

    Note

    - - + + When Samba is running in server security mode, it is essential that the parameter password server is set to the precise NetBIOS machine name of the target authentication server. Samba cannot determine this from NetBIOS name lookups because the choice of the target authentication server is arbitrary and cannot be determined from a domain name. In essence, a Samba server that is in server security mode is operating in what used to be known as workgroup mode. -

    Example Configuration

    +

    Example Configuration

    Using MS Windows NT as an Authentication Server

    This method involves the additions of the following parameters in the smb.conf file: -

    encrypt passwords = Yes
    security = server
    password server = "NetBIOS_name_of_a_DC"

    +

    encrypt passwords = Yes
    security = server
    password server = "NetBIOS_name_of_a_DC"

    There are two ways of identifying whether or not a username and password pair is valid. One uses the reply information provided as part of the authentication messaging process, the other uses just an error code.

    - - + + The downside of this mode of configuration is that for security reasons Samba will send the password server a bogus username and a bogus password, and if the remote server fails to reject the bogus username and password pair, then an alternative mode of @@ -356,15 +356,15 @@ certain number of failed authentication attempts, this will result in user locko

    Use of this mode of authentication requires a standard UNIX account for the user. This account can be blocked to prevent logons by non-SMB/CIFS clients. -

    Password Checking

    +

    Password Checking

    MS Windows clients may use encrypted passwords as part of a challenge/response authentication model (a.k.a. NTLMv1 and NTLMv2) or alone, or clear-text strings for simple password-based authentication. It should be realized that with the SMB protocol, the password is passed over the network either in plaintext or encrypted, but not both in the same authentication request.

    - - + + When encrypted passwords are used, a password that has been entered by the user is encrypted in two ways:

    • An MD4 hash of the unicode of the password @@ -375,12 +375,12 @@ is encrypted in two ways: form two 56-bit DES keys to encrypt a "magic" 8-byte value. The resulting 16 bytes form the LanMan hash.

    - + MS Windows 95 pre-service pack 1 and MS Windows NT versions 3.x and version 4.0 pre-service pack 3 will use either mode of password authentication. All versions of MS Windows that follow these versions no longer support plain-text passwords by default.

    - + MS Windows clients have a habit of dropping network mappings that have been idle for 10 minutes or longer. When the user attempts to use the mapped drive connection that has been dropped, the client re-establishes the connection using @@ -396,13 +396,13 @@ a good idea to re-enable plaintext password support in such clients. The following parameters can be used to work around the issue of Windows 9x/Me clients uppercasing usernames and passwords before transmitting them to the SMB server when using clear-text authentication: -

    +

    By default Samba will convert to lowercase the username before attempting to lookup the user in the database of local system accounts. Because UNIX usernames conventionally only contain lowercase characters, the username-level parameter is rarely needed.

    - + However, passwords on UNIX systems often make use of mixed-case characters. This means that in order for a user on a Windows 9x/Me client to connect to a Samba server using clear-text authentication, the password level must be set to the maximum number of uppercase letters that @@ -414,7 +414,7 @@ of the password string and try them one by one until a match is located (or all The best option to adopt is to enable support for encrypted passwords wherever Samba is used. Most attempts to apply the registry change to re-enable plaintext passwords will eventually lead to user complaints and unhappiness. -

    Common Errors

    +

    Common Errors

    We all make mistakes. It is okay to make mistakes, as long as they are made in the right places and at the right time. A mistake that causes lost productivity is seldom tolerated; however, a mistake made in a developmental test lab is expected. @@ -424,7 +424,7 @@ on the Samba mailing lists. Many of these are avoidable by doing your homework b a Samba implementation. Some are the result of a misunderstanding of the English language, which has many phrases that are potentially vague and may be highly confusing to those for whom English is not their native tongue. -

    What Makes Samba a Server?

    +

    What Makes Samba a Server?

    To some, the nature of the Samba security mode is obvious, but entirely wrong all the same. It is assumed that security = server means that Samba will act as a server. Not so! This setting means that Samba will try @@ -433,15 +433,15 @@ to use another SMB server as its source for user authentication alone. Samba is a server regardless of which security mode is chosen. When Samba is used outside of a domain security context, it is best to leave the security mode at the default setting. By default Samba-3 uses user-mode security. -

    What Makes Samba a Domain Controller?

    - +

    What Makes Samba a Domain Controller?

    + The smb.conf parameter security = domain does not really make Samba behave as a domain controller. This setting means we want Samba to be a domain member. See Samba as a PDC for more information. -

    What Makes Samba a Domain Member?

    +

    What Makes Samba a Domain Member?

    Guess! So many others do. But whatever you do, do not think that security = user makes Samba act as a domain member. Read the manufacturer's manual before the warranty expires. See Domain Membership, for more information. -

    Constantly Losing Connections to Password Server

    “ +

    Constantly Losing Connections to Password Server

    “ Why does server_validate() simply give up rather than re-establish its connection to the password server? Though I am not fluent in the SMB protocol, perhaps the cluster server process passes along to its client workstation the session key it receives from the password @@ -451,7 +451,7 @@ connection whose session key would be different. So server_validate() must give Indeed. That's why security = server is at best a nasty hack. Please use security = domain; security = server mode is also known as pass-through authentication. -

    Stand-alone Server is converted to Domain Controller Now User accounts don't work

    “ +

    Stand-alone Server is converted to Domain Controller Now User accounts don't work

    “ When I try to log in to the DOMAIN, the eventlog shows tried credentials DOMAIN/username; effective credentials SERVER/username ”

    diff --git a/docs/htmldocs/Samba3-HOWTO/StandAloneServer.html b/docs/htmldocs/Samba3-HOWTO/StandAloneServer.html index 202dbe3b3f..4180a9ebed 100644 --- a/docs/htmldocs/Samba3-HOWTO/StandAloneServer.html +++ b/docs/htmldocs/Samba3-HOWTO/StandAloneServer.html @@ -1,22 +1,22 @@ -Chapter 7. Standalone Servers

    Chapter 7. Standalone Servers
    Prev Part II. Server Configuration Basics Next

    Chapter 7. Standalone Servers

    John H. Terpstra

    Samba Team

    Table of Contents

    Features and Benefits
    Background
    Example Configuration
    Reference Documentation Server
    Central Print Serving
    Common Errors

    - - - +Chapter 7. Standalone Servers

    Chapter 7. Standalone Servers
    Prev Part II. Server Configuration Basics Next

    Chapter 7. Standalone Servers

    John H. Terpstra

    Samba Team

    Table of Contents

    Features and Benefits
    Background
    Example Configuration
    Reference Documentation Server
    Central Print Serving
    Common Errors

    + + + Standalone servers are independent of domain controllers on the network. They are not domain members and function more like workgroup servers. In many cases a standalone server is configured with a minimum of security control with the intent that all data served will be readily accessible to all users. -

    Features and Benefits

    - - +

    Features and Benefits

    + + Standalone servers can be as secure or as insecure as needs dictate. They can have simple or complex configurations. Above all, despite the hoopla about domain security, they remain a common installation.

    - - - + + + If all that is needed is a server for read-only files, or for printers alone, it may not make sense to effect a complex installation. For example, a drafting office needs to store old drawings and reference @@ -24,26 +24,26 @@ standards. Noone can write files to the server because it is legislatively important that all documents remain unaltered. A share-mode read-only standalone server is an ideal solution.

    - - - + + + Another situation that warrants simplicity is an office that has many printers that are queued off a single central server. Everyone needs to be able to print to the printers, there is no need to effect any access controls, and no files will be served from the print server. Again, a share-mode standalone server makes a great solution. -

    Background

    - - - +

    Background

    + + + The term standalone server means that it will provide local authentication and access control for all resources that are available from it. In general this means that there will be a local user database. In more technical terms, it means resources on the machine will be made available in either share mode or in user mode.

    - - - + + + No special action is needed other than to create user accounts. Standalone servers do not provide network logon services. This means that machines that use this server do not perform a domain logon to it. Whatever logon facility @@ -52,51 +52,51 @@ necessary to accommodate any network user so the logon name he or she uses will be translated (mapped) locally on the standalone server to a locally known user name. There are several ways this can be done.

    - - - + + + Samba tends to blur the distinction a little in defining a standalone server. This is because the authentication database may be local or on a remote server, even if from the SMB protocol perspective the Samba server is not a member of a domain security context.

    - - - - - - - - + + + + + + + + Through the use of Pluggable Authentication Modules (PAM) (see the chapter on PAM) and the name service switcher (NSS), which maintains the UNIX-user database, the source of authentication may reside on another server. We would be inclined to call this the authentication server. This means that the Samba server may use the local UNIX/Linux system password database (/etc/passwd or /etc/shadow), may use a local smbpasswd file, or may use an LDAP backend, or even via PAM and Winbind another CIFS/SMB server for authentication. -

    Example Configuration

    - - +

    Example Configuration

    + + The example Reference Documentation Server and Central Print Serving are designed to inspire simplicity. It is too easy to attempt a high level of creativity and to introduce too much complexity in server and network design.

    Reference Documentation Server

    - - - - + + + + Configuration of a read-only data server that everyone can access is very simple. By default, all shares are read-only, unless set otherwise in the smb.conf file. The example - Reference Documentation Server is the smb.conf file that will do this. Assume that all the reference documents are stored in the directory /export, and the documents are owned by a user other than nobody. No home directories are shared, and there are no users in the /etc/passwd UNIX system database. This is a simple system to administer. -

    Example 7.1. smb.conf for Reference Documentation Server

    # Global parameters
    [global]
    workgroup = MIDEARTH
    netbios name = GANDALF
    security = SHARE
    passdb backend = guest
    wins server = 192.168.1.1
    [data]
    comment = Data
    path = /export
    guest only = Yes

     

    +

    Example 7.1. smb.conf for Reference Documentation Server

    # Global parameters
    [global]
    workgroup = MIDEARTH
    netbios name = GANDALF
    security = SHARE
    passdb backend = guest
    wins server = 192.168.1.1
    [data]
    comment = Data
    path = /export
    guest only = Yes

     

    I would have spoken more briefly, if I'd had more time to prepare.

    		 
     --Mark Twain

    - - - - + + + + In this example, the machine name is set to GANDALF, and the workgroup is set to the name of the local workgroup (MIDEARTH) so the machine will appear together with systems with which users are familiar. The only password backend required is the “guest” @@ -107,8 +107,8 @@ A US Air Force Colonel was renowned for saying: “Bette sound reasons for avoiding complexity as well as for avoiding a technically perfect solution. Unfortunately, many network administrators still need to learn the art of doing just enough to keep out of trouble.

    Central Print Serving

    - - + + Configuration of a simple print server is easy if you have all the right tools on your system.

    Assumptions

    1. The print server must require no administration. @@ -122,17 +122,17 @@ Configuration of a simple print server is easy if you have all the right tools o All workstations will use only PostScript drivers. The printer driver of choice is the one shipped with the Windows OS for the Apple Color LaserWriter.

    - - - + + + In this example our print server will spool all incoming print jobs to /var/spool/samba until the job is ready to be submitted by Samba to the CUPS print processor. Since all incoming connections will be as the anonymous (guest) user, two things will be required to enable anonymous printing.

    Enabling Anonymous Printing

    • - - - + + + The UNIX/Linux system must have a guest account. The default for this is usually the account nobody. To find the correct name to use for your version of Samba, do the @@ -140,13 +140,13 @@ the anonymous (guest) user, two things will be required to enable anonymous prin 

       $ testparm -s -v | grep "guest account"

      - + Make sure that this account exists in your system password database (/etc/passwd).

      - - - + + + It is a good idea either to set a password on this account, or else to lock it from UNIX use. Assuming that the guest account is called pcguest, it can be locked by executing: @@ -155,12 +155,12 @@ the anonymous (guest) user, two things will be required to enable anonymous prin

      The exact command may vary depending on your UNIX/Linux distribution.

    • - - - - - - + + + + + + The directory into which Samba will spool the file must have write access for the guest account. The following commands will ensure that this directory is available for use: @@ -171,31 +171,31 @@ the anonymous (guest) user, two things will be required to enable anonymous prin

    The contents of the smb.conf file is shown in the Anonymous Printing example. -

    Example 7.2. smb.conf for Anonymous Printing

    # Global parameters
    [global]
    workgroup = MIDEARTH
    netbios name = GANDALF
    security = SHARE
    passdb backend = guest
    printing = cups
    printcap name = cups
    [printers]
    comment = All Printers
    path = /var/spool/samba
    printer admin = root
    guest ok = Yes
    printable = Yes
    use client driver = Yes
    browseable = No

    Note

    - - - - - +

    Example 7.2. smb.conf for Anonymous Printing

    # Global parameters
    [global]
    workgroup = MIDEARTH
    netbios name = GANDALF
    security = SHARE
    passdb backend = guest
    printing = cups
    printcap name = cups
    [printers]
    comment = All Printers
    path = /var/spool/samba
    printer admin = root
    guest ok = Yes
    printable = Yes
    use client driver = Yes
    browseable = No

    Note

    + + + + + On CUPS-enabled systems there is a facility to pass raw data directly to the printer without intermediate processing via CUPS print filters. Where use of this mode of operation is desired, it is necessary to configure a raw printing device. It is also necessary to enable the raw mime handler in the /etc/mime.conv and /etc/mime.types files. Refer to CUPS Printing Support, Explicitly Enable raw Printing for application/octet-stream.

    - - - - + + + + The example in the Anonymous Printing example uses CUPS for direct printing via the CUPS libarary API. This means that all printers will be exposed to Windows users without need to configure a printcap file. If there is necessity to expose only a sub-set of printers, or to define a special type of printer (for example, a PDF filter) the printcap name = cups can be replaced with the entry printcap name = /etc/samba/myprintcap. In this case the file specified should contain a list of the printer names that should be exposed to Windows network users. -

    Common Errors

    - - +

    Common Errors

    + + The greatest mistake so often made is to make a network configuration too complex. It pays to use the simplest solution that will meet the needs of the moment.

    Prev Up Next
    Chapter 6. Domain Membership Home Chapter 8. MS Windows Network Configuration Guide
    diff --git a/docs/htmldocs/Samba3-HOWTO/TOSHpreface.html b/docs/htmldocs/Samba3-HOWTO/TOSHpreface.html index 896e4a717a..8db6de19b2 100644 --- a/docs/htmldocs/Samba3-HOWTO/TOSHpreface.html +++ b/docs/htmldocs/Samba3-HOWTO/TOSHpreface.html @@ -1,4 +1,4 @@ -Preface
    Preface
    Prev   Next

    Preface

    Table of Contents

    Conventions Used

    +Preface

    Preface
    Prev   Next

    Preface

    Table of Contents

    Conventions Used

    The editors wish to thank you for your decision to purchase this book. The Official Samba-3 HOWTO and Reference Guide is the result of many years of accumulation of information, feedback, tips, hints, and happy solutions. @@ -28,7 +28,7 @@ to any one of the following: We wish to advise that only original and unencumbered material can be published. Please do not submit content that is not your own work unless proof of consent from the copyright holder accompanies your submission. -

    Conventions Used

    +

    Conventions Used

    The following notation conventions are used throughout this book:

    • TOSHARG2 is used as an abbreviation for the book, “The Official Samba-3 diff --git a/docs/htmldocs/Samba3-HOWTO/VFS.html b/docs/htmldocs/Samba3-HOWTO/VFS.html index 1058b01772..f317dd8331 100644 --- a/docs/htmldocs/Samba3-HOWTO/VFS.html +++ b/docs/htmldocs/Samba3-HOWTO/VFS.html @@ -1,51 +1,51 @@ -Chapter 23. Stackable VFS modules

      Chapter 23. Stackable VFS modules
      Prev Part III. Advanced Configuration Next

      Chapter 23. Stackable VFS modules

      Jelmer R. Vernooij

      The Samba Team

      John H. Terpstra

      Samba Team

      Tim Potter

      Samba Team

      Simo Sorce

      original vfs_skel README 

      Alexander Bokovoy

      original vfs_netatalk docs 

      Stefan Metzmacher

      Update for multiple modules 

      Ed Riddle

      original shadow_copy docs 

      Table of Contents

      Features and Benefits
      Discussion
      Included Modules
      audit
      default_quota
      extd_audit
      fake_perms
      recycle
      netatalk
      shadow_copy
      VFS Modules Available Elsewhere
      DatabaseFS
      vscan
      vscan-clamav

      Features and Benefits

      - - - +Chapter 23. Stackable VFS modules

      Chapter 23. Stackable VFS modules
      Prev Part III. Advanced Configuration Next

      Chapter 23. Stackable VFS modules

      Jelmer R. Vernooij

      The Samba Team

      John H. Terpstra

      Samba Team

      Tim Potter

      Samba Team

      Simo Sorce

      original vfs_skel README 

      Alexander Bokovoy

      original vfs_netatalk docs 

      Stefan Metzmacher

      Update for multiple modules 

      Ed Riddle

      original shadow_copy docs 

      Table of Contents

      Features and Benefits
      Discussion
      Included Modules
      audit
      default_quota
      extd_audit
      fake_perms
      recycle
      netatalk
      shadow_copy
      VFS Modules Available Elsewhere
      DatabaseFS
      vscan
      vscan-clamav

      Features and Benefits

      + + + Stackable VFS (Virtual File System) modules support was new to Samba-3 and has proven quite popular. Samba passes each request to access the UNIX file system through the loaded VFS modules. This chapter covers the modules that come with the Samba source and provides references to some external modules. -

      Discussion

      - - +

      Discussion

      + + If not supplied with your platform distribution binary Samba package, you may have problems compiling these modules, as shared libraries are compiled and linked in different ways on different systems. They currently have been tested against GNU/Linux and IRIX.

      - - - + + + To use the VFS modules, create a share similar to the one below. The important parameter is the vfs objects parameter where you can list one or more VFS modules by name. For example, to log all access to files and put deleted files in a recycle bin, see the smb.conf with VFS modules example: -

      Example 23.1. smb.conf with VFS modules

      [audit]
      comment = Audited /data directory
      path = /data
      vfs objects = audit recycle
      writeable = yes
      browseable = yes

      - - - +

      Example 23.1. smb.conf with VFS modules

      [audit]
      comment = Audited /data directory
      path = /data
      vfs objects = audit recycle
      writeable = yes
      browseable = yes

      + + + The modules are used in the order in which they are specified. Let's say that you want to both have a virus scanner module and a recycle bin module. It is wise to put the virus scanner module as the first one so that it is the first to get run and may detect a virus immediately, before any action is performed on that file. vfs objects = vscan-clamav recycle

      - - + + Samba will attempt to load modules from the /lib directory in the root directory of the Samba installation (usually /usr/lib/samba/vfs or /usr/local/samba/lib/vfs).

      - - - - + + + + Some modules can be used twice for the same share. This can be done using a configuration similar to the one shown in the smb.conf with multiple VFS modules. -

      Example 23.2. smb.conf with multiple VFS modules

      [test]
      comment = VFS TEST
      path = /data
      writeable = yes
      browseable = yes
      vfs objects = example:example1 example example:test
      example1: parameter = 1
      example: parameter = 5
      test: parameter = 7


      -

      Included Modules

      audit

      - +

      Example 23.2. smb.conf with multiple VFS modules

      [test]
      comment = VFS TEST
      path = /data
      writeable = yes
      browseable = yes
      vfs objects = example:example1 example example:test
      example1: parameter = 1
      example: parameter = 5
      test: parameter = 7


      +

      Included Modules

      audit

      + A simple module to audit file access to the syslog facility. The following operations are logged:

      • share

      • connect/disconnect

      • directory opens/create/remove

      • file open/close/rename/unlink/chmod

      -

      default_quota

      +

      default_quota

      This module allows the default quota values, in the windows explorer GUI, to be stored on a Samba-3 server. The challenge is that linux filesystems only store quotas for users and groups, but no default quotas.

      @@ -117,17 +117,17 @@ quotasettings: gid = 65534 quotasettings: gid nolimit = no ...

      -

      extd_audit

      - - - +

      extd_audit

      + + + This module is identical with the audit module above except that it sends audit logs to both syslog as well as the smbd log files. The log level for this module is set in the smb.conf file.

      Valid settings and the information that will be recorded are shown in the next table. -

      Table 23.1. Extended Auditing Log Information

      Log LevelLog Details - File and Directory Operations
      0Make Directory, Remove Directory, Unlink
      1Open Directory, Rename File, Change Permissions/ACLs
      2Open & Close File
      10Maximum Debug Level

      Configuration of Auditing

      - +

      Table 23.1. Extended Auditing Log Information

      Log LevelLog Details - File and Directory Operations
      0Make Directory, Remove Directory, Unlink
      1Open Directory, Rename File, Change Permissions/ACLs
      2Open & Close File
      10Maximum Debug Level

      Configuration of Auditing

      + This auditing tool is more felxible than most people readily will recognize. There are a number of ways by which useful logging information can be recorded.

      • Syslog can be used to record all transaction. This can be disabled by setting @@ -145,26 +145,26 @@ quotasettings: gid nolimit = no it is essential that the max log size = 0 be set in the smb.conf file.

      fake_perms

      - - - - + + + + This module was created to allow Roaming Profile files and directories to be set (on the Samba server under UNIX) as read only. This module will, if installed on the Profiles share, report to the client that the Profile files and directories are writeable. This satisfies the client even though the files will never be overwritten as the client logs out or shuts down. -

      recycle

      - - - +

      recycle

      + + + A Recycle Bin-like module. Where used, unlink calls will be intercepted and files moved to the recycle directory instead of being deleted. This gives the same effect as the Recycle Bin on Windows computers.

      - - - - + + + + The Recycle Bin will not appear in Windows Explorer views of the network file system (share) nor on any mapped drive. Instead, a directory @@ -179,10 +179,10 @@ quotasettings: gid nolimit = no file was deleted.

      Supported options for the recycle module are as follow:

      recycle:repository

      - + Path of the directory where deleted files should be moved.

      recycle:directory_mode

      - + Set it to the octal mode you want for the recycle directory. With this mode the recycle directory will be created if it not exists and the first file is deleted. @@ -191,7 +191,7 @@ quotasettings: gid nolimit = no If directory_mode not exists, the default mode 0700 is used.

      recycle:subdir_mode

      - + Set it to the octal mode you want for the sub directories of the recycle directory. With this mode the sub directories will be created. @@ -199,48 +199,48 @@ quotasettings: gid nolimit = no sub directories will be created with the mode from directory_mode.

      recycle:keeptree

      - + Specifies whether the directory structure should be kept or if the files in the directory that is being deleted should be kept separately in the recycle bin.

      recycle:versions

      - + If this option is set, two files with the same name that are deleted will both be kept in the recycle bin. Newer deleted versions of a file will be called “Copy #x of filename”.

      recycle:touch

      - + Specifies whether a file's access date should be touched when the file is moved to the recycle bin.

      recycle:touch_mtime

      - + Specifies whether a file's last modify date date should be touched when the file is moved to the recycle bin.

      recycle:maxsize

      - + Files that are larger than the number of bytes specified by this parameter will not be put into the recycle bin.

      recycle:exclude

      - + List of files that should not be put into the recycle bin when deleted, but deleted in the regular way.

      recycle:exclude_dir

      - + Contains a list of directories. When files from these directories are deleted, they are not put into the recycle bin but are deleted in the regular way.

      recycle:noversions

      - + Specifies a list of paths (wildcards such as * and ? are supported) for which no versioning should be used. Only useful when recycle:versions is enabled.

      -

      netatalk

      - +

      netatalk

      + A netatalk module will ease co-existence of Samba and netatalk file sharing services.

      Advantages compared to the old netatalk module: -

      • Does not care about creating .AppleDouble forks, just keeps them in sync.

      • If a share in smb.conf does not contain .AppleDouble item in hide or veto list, it will be added automatically.

      -

      shadow_copy

      Warning

      - +

      • Does not care about creating .AppleDouble forks, just keeps them in sync.

      • If a share in smb.conf does not contain .AppleDouble item in hide or veto list, it will be added automatically.

      +

      shadow_copy

      Warning

      + THIS IS NOT A BACKUP, ARCHIVAL, OR VERSION CONTROL SOLUTION!

      - + With Samba or Windows servers, shadow_copy is designed to be an end-user tool only. It does not replace or enhance your backup and archival solutions and should in no way be considered as such. Additionally, if you need version control, implement a version control system. You have been warned. @@ -251,12 +251,12 @@ quotasettings: gid nolimit = no additional requirements for pre-Windows XP clients. I did not test this functionality with any pre-Windows XP clients. You should be able to get more information about MS Shadow Copy from the Microsoft's site.

      - - - - - - + + + + + + The shadow_copy VFS module requires some underlying file system setup with some sort of Logical Volume Manager (LVM) such as LVM1, LVM2, or EVMS. Setting up LVM is beyond the scope of this document; however, we will outline the steps we took to test this functionality for example purposes only. You need @@ -269,9 +269,9 @@ quotasettings: gid nolimit = no See Learning Linux LVM, Part 1 and Learning Linux LWM, Part 2 for Daniel Robbins' well-written, two part tutorial on Linux and LVM using LVM - source code and reiserfs.

    Shadow Copy Setup

    - - + source code and reiserfs.

    Shadow Copy Setup

    + + At the time of this writing, not much testing has been done. I tested the shadow copy VFS module with a specific scenario which was not deployed in a production environment, but more as a proof of concept. The scenario involved a Samba-3 file server on Debian Sarge with an XFS file system and LVM1. I do NOT recommend @@ -286,8 +286,8 @@ quotasettings: gid nolimit = no It doesn't matter if it is a Domain Controller or Member File Server, but it is assumed that you have a working Samba 3.0.3 or later server running.

  • Install & Configure LVM.  - - + + Before you can make shadow copies available to the client, you have to create the shadow copies. This is done by taking some sort of file system snapshot. Snapshots are a typical feature of Logical Volume Managers such as LVM, so we first need to have that setup. @@ -295,69 +295,69 @@ quotasettings: gid nolimit = no The following is provided as an example and will be most helpful for Debian users. Again, this was tested using the "testing" or "Sarge" distribution.

    • - - - - - + + + + + Install lvm10 and devfsd packages if you have not done so already. On Debian systems, you are warned of the interaction of devfs and lvm1 which requires the use of devfs filenames. Running apt-get update && apt-get install lvm10 devfsd xfsprogs should do the trick for this example.

    • - - - - - + + + + + Now you need to create a volume. You will need to create a partition (or partitions) to add to your volume. Use your favorite partitioning tool (e.g., Linux fdisk, cfdisk, etc.). The partition type should be set to 0x8e for "Linux LVM." In this example, we will use /dev/hdb1.

      - - - + + + Once you have the Linux LVM partition (type 0x8e), you can run a series of commands to create the LVM volume. You can use several disks and/or partitions, but we will use only one in this example. You may also need to load the kernel module with something like modprobe lvm-mod and set your system up to load it on reboot by adding it to (/etc/modules).

    • - + Create the physical volume with pvcreate /dev/hdb1

    • - - + + Create the volume group and add /dev/hda1 to it with vgcreate shadowvol /dev/hdb1

      - + You can use vgdisplay to review information about the volume group.

    • - + Now you can create the logical volume with something like lvcreate -L400M -nsh_test shadowvol

      - + This creates the logical volume of 400 MBs named "sh_test" in the volume group we created called shadowvol. If everything is working so far, you should see them in /dev/shadowvol.

    • - + Now we should be ready to format the logical volume we named sh_test with mkfs.xfs /dev/shadowvol/sh_test

      - - - - - + + + + + You can format the logical volume with any file system you choose, but make sure to use one that allows you to take advantage of the additional features of LVM such as freezing, resizing, and growing your file systems.

      - - - + + + Now we have an LVM volume where we can play with the shadow_copy VFS module.

    • - - - + + + Now we need to prepare the directory with something like 

       root#  mkdir -p /data/shadow_share
@@ -366,19 +366,19 @@ quotasettings:	gid nolimit = no
 			you can use it.  If in doubt, use chmod 777 /data/shadow_share and tighten the permissions
 			once you get things working.

    • - + Mount the LVM volume using something like mount /dev/shadowvol/sh_test /data/shadow_share

      - + You may also want to edit your /etc/fstab so that this partition mounts during the system boot.

  • Install & Configure the shadow_copy VFS Module.  Finally we get to the actual shadow_copy VFS module. The shadow_copy VFS module should be available in Samba 3.0.3 and higher. The smb.conf configuration is pretty standard. Here is our example of a share configured with the shadow_copy VFS module: -

    Example 23.3. Share With shadow_copy VFS

    [shadow_share]
    comment = Shadow Copy Enabled Share
    path = /data/shadow_share
    vfs objects = shadow_copy
    writeable = yes
    browseable = yes

  • Create Snapshots and Make Them Available to shadow_copy.so.  - - - +

    Example 23.3. Share With shadow_copy VFS

    [shadow_share]
    comment = Shadow Copy Enabled Share
    path = /data/shadow_share
    vfs objects = shadow_copy
    writeable = yes
    browseable = yes

  • Create Snapshots and Make Them Available to shadow_copy.so.  + + + Before you can browse the shadow copies, you must create them and mount them. This will most likely be done with a script that runs as a cron job. With this particular solution, the shadow_copy VFS module is used to browse LVM snapshots. Those snapshots are not created by the module. They are not made available by the @@ -404,15 +404,15 @@ mount /dev/shadowvol/$SNAPNAME \ your XP client you can right-click on specific files or in the empty space of the shadow_share and view the "properties." If anything has changed, then you will see it on the "Previous Versions" tab of the properties window. -

    • VFS Modules Available Elsewhere

    - +

    VFS Modules Available Elsewhere

    + This section contains a listing of various other VFS modules that have been posted but do not currently reside in the Samba CVS tree for one reason or another (e.g., it is easy for the maintainer to have his or her own CVS tree).

    No statements about the stability or functionality of any module should be implied due to its presence here. -

    DatabaseFS

    - +

    DatabaseFS

    + URL: Taylors University DatabaeFS

    By Eric Lorimer.

    @@ -425,13 +425,13 @@ beyond the table it requires to run.

    Any feedback would be appreciated: comments, suggestions, patches, and so on. If nothing else, it might prove useful for someone else who wishes to create a virtual filesystem. -

    vscan

    URL: +

    vscan

    URL: Open Anti-Virus vscan

    - + samba-vscan is a proof-of-concept module for Samba, which provides on-access anti-virus support for files shared using Samba. samba-vscan supports various virus scanners and is maintained by Rainer Link. -

    vscan-clamav

    +

    vscan-clamav

    Samba users have been using the RPMS from SerNet without a problem. OpenSUSE Linux users have also used the vscan scanner for quite some time with excellent results. It does impact overall write performance though. diff --git a/docs/htmldocs/Samba3-HOWTO/apa.html b/docs/htmldocs/Samba3-HOWTO/apa.html index 5db6b03028..b9213e5416 100644 --- a/docs/htmldocs/Samba3-HOWTO/apa.html +++ b/docs/htmldocs/Samba3-HOWTO/apa.html @@ -1,50 +1,50 @@ -Appendix A.  GNU General Public License version 3

    Appendix A.  +Appendix A.  GNU General Public License version 3
    Appendix A.  GNU General Public License version 3 -
    Prev   Next

    Appendix A.  +

    Prev   Next

    Appendix A.  GNU General Public License version 3 -

    Table of Contents

    A. +

    Table of Contents

    A. Preamble -
    A. +
    A. TERMS AND CONDITIONS -
    A. +
    A. 0. Definitions. -
    A. +
    A. 1. Source Code. -
    A. +
    A. 2. Basic Permissions. -
    A. +
    A. 3. Protecting Users’ Legal Rights From Anti-Circumvention Law. -
    A. +
    A. 4. Conveying Verbatim Copies. -
    A. +
    A. 5. Conveying Modified Source Versions. -
    A. +
    A. 6. Conveying Non-Source Forms. -
    A. +
    A. 7. Additional Terms. -
    A. +
    A. 8. Termination. -
    A. +
    A. 9. Acceptance Not Required for Having Copies. -
    A. +
    A. 10. Automatic Licensing of Downstream Recipients. -
    A. +
    A. 11. Patents. -
    A. +
    A. 12. No Surrender of Others’ Freedom. -
    A. +
    A. 13. Use with the ???TITLE??? Affero General Public License. -
    A. +
    A. 14. Revised Versions of this License. -
    A. +
    A. 15. Disclaimer of Warranty. -
    A. +
    A. 16. Limitation of Liability. -
    A. +
    A. 17. Interpretation of Sections 15 and 16. -
    A. +
    A. END OF TERMS AND CONDITIONS -
    A. +
    A. How to Apply These Terms to Your New Programs

    Version 3, 29 June 2007 @@ -54,7 +54,7 @@

    Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed. -

    +

    Preamble

    The GNU General Public License is a free, copyleft @@ -118,9 +118,9 @@

    The precise terms and conditions for copying, distribution and modification follow. -

    +

    TERMS AND CONDITIONS -

    +

    0. Definitions.

    “This License” refers to version 3 of the GNU @@ -162,7 +162,7 @@ License, and how to view a copy of this License. If the interface presents a list of user commands or options, such as a menu, a prominent item in the list meets this criterion. -

    +

    1. Source Code.

    The “source code” for a work means the preferred form of the @@ -202,7 +202,7 @@ automatically from other parts of the Corresponding Source.

    The Corresponding Source for a work in source code form is that same work. -

    +

    2. Basic Permissions.

    All rights granted under this License are granted for the term of copyright @@ -227,7 +227,7 @@ Conveying under any other circumstances is permitted solely under the conditions stated below. Sublicensing is not allowed; section 10 makes it unnecessary. -

    +

    3. Protecting Users’ Legal Rights From Anti-Circumvention Law.

    No covered work shall be deemed part of an effective technological measure @@ -242,7 +242,7 @@ the work as a means of enforcing, against the work’s users, your or third parties’ legal rights to forbid circumvention of technological measures. -

    +

    4. Conveying Verbatim Copies.

    You may convey verbatim copies of the Program’s source code as you @@ -255,7 +255,7 @@

    You may charge any price or no price for each copy that you convey, and you may offer support or warranty protection for a fee. -

    +

    5. Conveying Modified Source Versions.

    You may convey a work based on the Program, or the modifications to produce @@ -291,7 +291,7 @@ or legal rights of the compilation’s users beyond what the individual works permit. Inclusion of a covered work in an aggregate does not cause this License to apply to the other parts of the aggregate. -

    +

    6. Conveying Non-Source Forms.

    You may convey a covered work in object code form under the terms of @@ -386,7 +386,7 @@ (and with an implementation available to the public in source code form), and must require no special password or key for unpacking, reading or copying. -

    +

    7. Additional Terms.

    “Additional permissions” are terms that supplement the terms of @@ -450,7 +450,7 @@ Additional terms, permissive or non-permissive, may be stated in the form of a separately written license, or stated as exceptions; the above requirements apply either way. -

    +

    8. Termination.

    You may not propagate or modify a covered work except as expressly provided @@ -476,7 +476,7 @@ License. If your rights have been terminated and not permanently reinstated, you do not qualify to receive new licenses for the same material under section 10. -

    +

    9. Acceptance Not Required for Having Copies.

    You are not required to accept this License in order to receive or run a @@ -487,7 +487,7 @@ These actions infringe copyright if you do not accept this License. Therefore, by modifying or propagating a covered work, you indicate your acceptance of this License to do so. -

    +

    10. Automatic Licensing of Downstream Recipients.

    Each time you convey a covered work, the recipient automatically receives a @@ -512,7 +512,7 @@ or counterclaim in a lawsuit) alleging that any patent claim is infringed by making, using, selling, offering for sale, or importing the Program or any portion of it. -

    +

    11. Patents.

    A “contributor” is a copyright holder who authorizes use under @@ -579,7 +579,7 @@ Nothing in this License shall be construed as excluding or limiting any implied license or other defenses to infringement that may otherwise be available to you under applicable patent law. -

    +

    12. No Surrender of Others’ Freedom.

    If conditions are imposed on you (whether by court order, agreement or @@ -591,7 +591,7 @@ to collect a royalty for further conveying from those to whom you convey the Program, the only way you could satisfy both those terms and this License would be to refrain entirely from conveying the Program. -

    +

    13. Use with the GNU Affero General Public License.

    Notwithstanding any other provision of this License, you have permission to @@ -602,7 +602,7 @@ requirements of the GNU Affero General Public License, section 13, concerning interaction through a network will apply to the combination as such. -

    +

    14. Revised Versions of this License.

    The Free Software Foundation may publish revised and/or new versions of the @@ -627,7 +627,7 @@ Later license versions may give you additional or different permissions. However, no additional obligations are imposed on any author or copyright holder as a result of your choosing to follow a later version. -

    +

    15. Disclaimer of Warranty.

    THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE @@ -638,7 +638,7 @@ THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION. -

    +

    16. Limitation of Liability.

    IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING WILL @@ -650,7 +650,7 @@ PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. -

    +

    17. Interpretation of Sections 15 and 16.

    If the disclaimer of warranty and limitation of liability provided above @@ -659,9 +659,9 @@ waiver of all civil liability in connection with the Program, unless a warranty or assumption of liability accompanies a copy of the Program in return for a fee. -

    +

    END OF TERMS AND CONDITIONS -

    +

    How to Apply These Terms to Your New Programs

    If you develop a new program, and you want it to be of the greatest possible @@ -716,4 +716,4 @@ under certain conditions; type ‘show c’ proprietary applications with the library. If this is what you want to do, use the GNU Lesser General Public License instead of this License. But first, please read http://www.gnu.org/philosophy/why-not-lgpl.html. -

    Prev   Next
    Chapter 47. DNS and DHCP Configuration Guide Home Glossary
    +

    Prev   Next
    Chapter 48. DNS and DHCP Configuration Guide Home Glossary
    diff --git a/docs/htmldocs/Samba3-HOWTO/bugreport.html b/docs/htmldocs/Samba3-HOWTO/bugreport.html index 297e7a3175..eb01148b99 100644 --- a/docs/htmldocs/Samba3-HOWTO/bugreport.html +++ b/docs/htmldocs/Samba3-HOWTO/bugreport.html @@ -1,6 +1,6 @@ -Chapter 40. Reporting Bugs
    Chapter 40. Reporting Bugs
    Prev Part V. Troubleshooting Next

    Chapter 40. Reporting Bugs

    John H. Terpstra

    Samba Team

    Jelmer R. Vernooij

    The Samba Team

    Andrew Tridgell

    Samba Team

    27 June 1997

    Table of Contents

    Introduction
    General Information
    Debug Levels
    Debugging-Specific Operations
    Internal Errors
    Attaching to a Running Process
    Patches

    Introduction

    - - +Chapter 40. Reporting Bugs

    Chapter 40. Reporting Bugs
    Prev Part V. Troubleshooting Next

    Chapter 40. Reporting Bugs

    John H. Terpstra

    Samba Team

    Jelmer R. Vernooij

    The Samba Team

    Andrew Tridgell

    Samba Team

    27 June 1997

    Table of Contents

    Introduction
    General Information
    Debug Levels
    Debugging-Specific Operations
    Internal Errors
    Attaching to a Running Process
    Patches

    Introduction

    + + Please report bugs using Samba's Bugzilla facilities and take the time to read this file before you submit a bug report. Also, check to see if it has changed between releases, as we may be changing the bug reporting mechanism at some point. @@ -12,9 +12,9 @@ we can possibly answer, so you have a much higher chance of a response and a fix if you send us a “developer-friendly” bug report that lets us fix it fast.

    - - - + + + If you post the bug to the comp.protocols.smb newsgroup or the mailing list, do not assume that we will read it. If you suspect that your problem is not a bug but a configuration problem, it is better to send @@ -24,7 +24,7 @@ that list who may be able to help you. You may also like to look though the recent mailing list archives, which are conveniently accessible on the Samba Web pages at http://samba.org/samba/. -

    General Information

    +

    General Information

    Before submitting a bug report, check your config for silly errors. Look in your log files for obvious messages that tell you've misconfigured something. Run testparm to check your config @@ -42,13 +42,13 @@ be quite useful. Depending on the problem, a log level of between 3 and 10 showing the problem may be appropriate. A higher level gives more detail but may use too much disk space.

    - - + + To set the debug level, use the log level in your smb.conf. You may also find it useful to set the log level higher for just one machine and keep separate logs for each machine. To do this, add the following lines to your main smb.conf file: -

    log level = 10
    log file = /usr/local/samba/lib/log.%m
    include = /usr/local/samba/lib/smb.conf.%m

    +

    log level = 10
    log file = /usr/local/samba/lib/log.%m
    include = /usr/local/samba/lib/smb.conf.%m

    and create a file /usr/local/samba/lib/smb.conf.machine where machine is the name of the client you wish to debug. In that file put any smb.conf commands you want; for example, log level may be useful. This also allows @@ -61,23 +61,23 @@ As the log level value is in debugging information. For most debugging operations, you may not need a setting higher than 3. Nearly all bugs can be tracked at a setting of 10, but be prepared for a large volume of log data. -

    Debugging-Specific Operations

    - - - - +

    Debugging-Specific Operations

    + + + + Samba-3.x permits debugging (logging) of specific functional components without unnecessarily cluttering the log files with detailed logs for all operations. An example configuration to achieve this is shown in:

    -

    log level = 0 tdb:3 passdb:5 auth:4 vfs:2
    max log size = 0
    log file = /var/log/samba/%U.%m.log

    +

    log level = 0 tdb:3 passdb:5 auth:4 vfs:2
    max log size = 0
    log file = /var/log/samba/%U.%m.log

    This will cause the level of detail to be expanded to the debug class (log level) passed to each functional area per the value shown above. The first value passed to the log level of 0 means turn off all unnecessary debugging except the debug classes set for the functional areas as specified. The table shown in Debuggable Functions may be used to attain very precise analysis of each SMB operation Samba is conducting. -

    Table 40.1. Debuggable Functions

    Function NameFunction Name
    allpassdb
    tdbsam
    printdriversauth
    lanmanwinbind
    smbvfs
    rpc_parseidmap
    rpc_srvquota
    rpc_cliacls

    Internal Errors

    +

    Table 40.1. Debuggable Functions

    Function NameFunction Name
    allpassdb
    tdbsam
    printdriversauth
    lanmanwinbind
    smbvfs
    rpc_parseidmap
    rpc_srvquota
    rpc_cliacls

    Internal Errors

    If you get the message “INTERNAL ERROR” in your log files, it means that Samba got an unexpected signal while running. It is probably a segmentation fault and almost certainly means a bug in Samba (unless @@ -91,35 +91,35 @@ include it in your bug report. You should also detail how to reproduce the problem, if possible. Please make this reasonably detailed.

    - + You may also find that a core file appeared in a corefiles subdirectory of the directory where you keep your Samba log files. This file is the most useful tool for tracking down the bug. To use it, you do this: - - + + 

     $ gdb smbd core

    - - + + adding appropriate paths to smbd and core so gdb can find them. If you do not have gdb, try dbx. Then within the debugger, use the command where to give a stack trace of where the problem occurred. Include this in your report.

    - + If you know any assembly language, do a disass of the routine where the problem occurred (if it's in a library routine, then disassemble the routine that called it) and try to work out exactly where the problem is by looking at the surrounding code. Even if you do not know assembly, including this information in the bug report can be useful. -

    Attaching to a Running Process

    - - - +

    Attaching to a Running Process

    + + + Unfortunately, some UNIXes (in particular some recent Linux kernels) refuse to dump a core file if the task has changed UID (which smbd does often). To debug with this sort of system, you could try to attach @@ -145,15 +145,15 @@ of the spinning process and type: 

     root#  gdb /usr/local/samba/sbin/smbd

    - + then “attach `pid'” (of the spinning process), then type “bt” to get a backtrace to see where the smbd is in the call path. -

    Patches

    - - +

    Patches

    + + The best sort of bug report is one that includes a fix! If you send us patches, please use diff -u format if your version of diff supports it; otherwise, use diff -c4. Make sure you do the diff against a clean version of the source and let me know exactly what version you used. -

    Prev Up Next
    Chapter 39. Analyzing and Solving Samba Problems Home Part VI. Reference Section
    +

    Prev Up Next
    Chapter 39. Analyzing and Solving Samba Problems Home Chapter 41. Managing TDB Files
    diff --git a/docs/htmldocs/Samba3-HOWTO/cfgsmarts.html b/docs/htmldocs/Samba3-HOWTO/cfgsmarts.html index d2cbe33242..e056408f00 100644 --- a/docs/htmldocs/Samba3-HOWTO/cfgsmarts.html +++ b/docs/htmldocs/Samba3-HOWTO/cfgsmarts.html @@ -1,52 +1,52 @@ -Chapter 34. Advanced Configuration Techniques
    Chapter 34. Advanced Configuration Techniques
    Prev Part III. Advanced Configuration Next

    Chapter 34. Advanced Configuration Techniques

    John H. Terpstra

    Samba Team

    June 30, 2005

    Table of Contents

    Implementation
    Multiple Server Hosting
    Multiple Virtual Server Personalities
    Multiple Virtual Server Hosting

    - - +Chapter 34. Advanced Configuration Techniques

    Chapter 34. Advanced Configuration Techniques
    Prev Part III. Advanced Configuration Next

    Chapter 34. Advanced Configuration Techniques

    John H. Terpstra

    Samba Team

    June 30, 2005

    Table of Contents

    Implementation
    Multiple Server Hosting
    Multiple Virtual Server Personalities
    Multiple Virtual Server Hosting

    + + Since the release of the first edition of this book there have been repeated requests to better document configuration techniques that may help a network administrator to get more out of Samba. Some users have asked for documentation regarding the use of the include = file-name parameter.

    - - + + Commencing around mid-2004 there has been increasing interest in the ability to host multiple Samba servers on one machine. There has also been an interest in the hosting of multiple Samba server personalities on one server.

    - - + + Feedback from technical reviewers made the inclusion of this chapter a necessity. So, here is an answer the questions that have to date not been adequately addressed. Additional user input is welcome as it will help this chapter to mature. What is presented here is just a small beginning.

    - - - + + + There are a number of ways in which multiple servers can be hosted on a single Samba server. Multiple server hosting makes it possible to host multiple domain controllers on one machine. Each such machine is independent, and each can be stopped or started without affecting another.

    - - - + + + Sometimes it is desirable to host multiple servers, each with its own security mode. For example, a single UNIX/Linux host may be a domain member server (DMS) as well as a generic anonymous print server. In this case, only domain member machines and domain users can access the DMS, but even guest users can access the generic print server. Another example of a situation where it may be beneficial to host a generic (anonymous) server is to host a CDROM server.

    - - + + Some environments dictate the need to have separate servers, each with their own resources, each of which are accessible only by certain users or groups. This is one of the simple, but highly effective, ways that Samba can replace many physical Windows servers in one Samba installation. -

    Implementation

    -

    Multiple Server Hosting

    - - - - - - - +

    Implementation

    +

    Multiple Server Hosting

    + + + + + + + The use of multiple server hosting involves running multiple separate instances of Samba, each with it's own configuration file. This method is complicated by the fact that each instance of nmbd, smbd and winbindd must have write access to entirely separate TDB files. The ability to keep separate the TDB files used by @@ -54,58 +54,58 @@ must have write access to entirely separate TDB files. The ability to keep separ own default TDB directories, or by configuring these in the smb.conf file, in which case each instance of nmbd, smbd and winbindd must be told to start up with its own smb.conf configuration file.

    - - - - + + + + Each instance should operate on its own IP address (that independent IP address can be an IP Alias). Each instance of nmbd, smbd and winbindd should listen only on its own IP socket. This can be secured using the socket address parameter. Each instance of the Samba server will have its own SID also, this means that the servers are discrete and independent of each other.

    - - - - - - - - - + + + + + + + + + The user of multiple server hosting is non-trivial, and requires careful configuration of each aspect of process management and start up. The smb.conf parameters that must be carefully configured includes: private dir, pid directory,lock directory, interfaces, bind interfaces only, netbios name, workgroup, socket address.

    - - - + + + Those who elect to create multiple Samba servers should have the ability to read and follow the Samba source code, and to modify it as needed. This mode of deployment is considered beyond the scope of this book. However, if someone will contribute more comprehensive documentation we will gladly review it, and if it is suitable extend this section of this chapter. Until such documentation becomes available the hosting of multiple samba servers on a single host is considered not supported for Samba-3 by the Samba Team. -

    Multiple Virtual Server Personalities

    - - - +

    Multiple Virtual Server Personalities

    + + + Samba has the ability to host multiple virtual servers, each of which have their own personality. This is achieved by configuring an smb.conf file that is common to all personalities hosted. Each server personality is hosted using its own netbios alias name, and each has its own distinct [global] section. Each server may have its own stanzas for services and meta-services.

    - - - + + + When hosting multiple virtual servers, each with their own personality, each can be in a different workgroup. Only the primary server can be a domain member or a domain controller. The personality is defined by the combination of the security mode it is operating in, the netbios aliases it has, and the workgroup that is defined for it.

    - - - - - - + + + + + + This configuration style can be used either with NetBIOS names, or using NetBIOS-less SMB over TCP services. If run using NetBIOS mode (the most common method) it is important that the parameter smb ports = 139 should be specified in the primary smb.conf file. Failure to do this will result in Samba operating over TCP port 445 and problematic operation at best, and at worst only being able to obtain @@ -114,10 +114,10 @@ TCP port 139 means that the use of the %L macro is the value of this parameter is set at 139 445 then the %L macro is not serviceable.

    - - - - + + + + It is possible to host multiple servers, each with their own personality, using port 445 (the NetBIOS-less SMB port), in which case the %i macro can be used to provide separate server identities (by IP Address). Each can have its own security mode. It will be necessary to use the @@ -125,7 +125,7 @@ IP Address). Each can have its own netbios name parameters to create the virtual servers. This method is considerably more complex than that using NetBIOS names only using TCP port 139.

    - + Consider an example environment that consists of a standalone, user-mode security Samba server and a read-only Windows 95 file server that has to be replaced. Instead of replacing the Windows 95 machine with a new PC, it is possible to add this server as a read-only anonymous file server that is hosted on the Samba server. Here @@ -135,46 +135,46 @@ The Samba server is called ELASTIC, its workgroup n The CDROM server is called CDSERVER and its workgroup is ARTSDEPT. A possible implementation is shown here:

    - - - - + + + + The smb.conf file for the master server is shown in Elastic smb.conf File. This file is placed in the /etc/samba directory. Only the nmbd and the smbd daemons are needed. When started the server will appear in Windows Network Neighborhood as the machine ELASTIC under the workgroup ROBINSNEST. It is helpful if the Windows clients that must access this server are also in the workgroup ROBINSNEST as this will make browsing much more reliable. -

    Example 34.1. Elastic smb.conf File

    # Global parameters
    [global]
    workgroup = ROBINSNEST
    netbios name = ELASTIC
    netbios aliases = CDSERVER
    smb ports = 139
    printcap name = cups
    disable spoolss = Yes
    show add printer wizard = No
    printing = cups
    include = /etc/samba/smb-%L.conf
    [homes]
    comment = Home Directories
    valid users = %S
    read only = No
    browseable = No
    [office]
    comment = Data
    path = /data
    read only = No
    [printers]
    comment = All Printers
    path = /var/spool/samba
    create mask = 0600
    guest ok = Yes
    printable = Yes
    use client driver = Yes
    browseable = No

    - +

    Example 34.1. Elastic smb.conf File

    # Global parameters
    [global]
    workgroup = ROBINSNEST
    netbios name = ELASTIC
    netbios aliases = CDSERVER
    smb ports = 139
    printcap name = cups
    disable spoolss = Yes
    show add printer wizard = No
    printing = cups
    include = /etc/samba/smb-%L.conf
    [homes]
    comment = Home Directories
    valid users = %S
    read only = No
    browseable = No
    [office]
    comment = Data
    path = /data
    read only = No
    [printers]
    comment = All Printers
    path = /var/spool/samba
    create mask = 0600
    guest ok = Yes
    printable = Yes
    use client driver = Yes
    browseable = No

    + The configuration file for the CDROM server is listed in CDROM Server smb-cdserver.conf file. This file is called smb-cdserver.conf and it should be located in the /etc/samba directory. Machines that are in the workgroup ARTSDEPT will be able to browse this server freely. -

    Example 34.2. CDROM Server smb-cdserver.conf file

    # Global parameters
    [global]
    workgroup = ARTSDEPT
    netbios name = CDSERVER
    map to guest = Bad User
    guest ok = Yes
    [carousel]
    comment = CDROM Share
    path = /export/cddata
    read only = Yes
    guest ok = Yes

    - - - - +

    Example 34.2. CDROM Server smb-cdserver.conf file

    # Global parameters
    [global]
    workgroup = ARTSDEPT
    netbios name = CDSERVER
    map to guest = Bad User
    guest ok = Yes
    [carousel]
    comment = CDROM Share
    path = /export/cddata
    read only = Yes
    guest ok = Yes

    + + + + The two servers have different resources and are in separate workgroups. The server ELASTIC can only be accessed by uses who have an appropriate account on the host server. All users will be able to access the CDROM data that is stored in the /export/cddata directory. File system permissions should set so that the others user has read-only access to the directory and its contents. The files can be owned by root (any user other than the nobody account). -

    Multiple Virtual Server Hosting

    - - - +

    Multiple Virtual Server Hosting

    + + + In this example, the requirement is for a primary domain controller for the domain called MIDEARTH. The PDC will be called MERLIN. An extra machine called SAURON is required. Each machine will have only its own shares. Both machines belong to the same domain/workgroup.

    - - - + + + The master smb.conf file is shown in the Master smb.conf File Global Section. The two files that specify the share information for each server are shown in the smb-merlin.conf File Share Section, and the smb-sauron.conf File Share Section. All three files are locate in the /etc/samba directory. -

    Example 34.3. Master smb.conf File Global Section

    # Global parameters
    [global]
    workgroup = MIDEARTH
    netbios name = MERLIN
    netbios aliases = SAURON
    passdb backend = tdbsam
    smb ports = 139
    syslog = 0
    printcap name = CUPS
    show add printer wizard = No
    add user script = /usr/sbin/useradd -m '%u'
    delete user script = /usr/sbin/userdel -r '%u'
    add group script = /usr/sbin/groupadd '%g'
    delete group script = /usr/sbin/groupdel '%g'
    add user to group script = /usr/sbin/usermod -G '%g' '%u'
    add machine script = /usr/sbin/useradd -s /bin/false -d /var/lib/nobody '%u'
    logon script = scripts\login.bat
    logon path =
    logon drive = X:
    domain logons = Yes
    preferred master = Yes
    wins support = Yes
    printing = CUPS
    include = /etc/samba/smb-%L.conf

    Example 34.4. MERLIN smb-merlin.conf File Share Section

    # Global parameters
    [global]
    workgroup = MIDEARTH
    netbios name = MERLIN
    [homes]
    comment = Home Directories
    valid users = %S
    read only = No
    browseable = No
    [office]
    comment = Data
    path = /data
    read only = No
    [netlogon]
    comment = NETLOGON
    path = /var/lib/samba/netlogon
    read only = Yes
    browseable = No
    [printers]
    comment = All Printers
    path = /var/spool/samba
    printable = Yes
    use client driver = Yes
    browseable = No

    Example 34.5. SAURON smb-sauron.conf File Share Section

    # Global parameters
    [global]
    workgroup = MIDEARTH
    netbios name = SAURON
    [www]
    comment = Web Pages
    path = /srv/www/htdocs
    read only = No

    Prev Up Next
    Chapter 33. Handling Large Directories Home Part IV. Migration and Updating
    +

    Example 34.3. Master smb.conf File Global Section

    # Global parameters
    [global]
    workgroup = MIDEARTH
    netbios name = MERLIN
    netbios aliases = SAURON
    passdb backend = tdbsam
    smb ports = 139
    syslog = 0
    printcap name = CUPS
    show add printer wizard = No
    add user script = /usr/sbin/useradd -m '%u'
    delete user script = /usr/sbin/userdel -r '%u'
    add group script = /usr/sbin/groupadd '%g'
    delete group script = /usr/sbin/groupdel '%g'
    add user to group script = /usr/sbin/usermod -G '%g' '%u'
    add machine script = /usr/sbin/useradd -s /bin/false -d /var/lib/nobody '%u'
    logon script = scripts\login.bat
    logon path =
    logon drive = X:
    domain logons = Yes
    preferred master = Yes
    wins support = Yes
    printing = CUPS
    include = /etc/samba/smb-%L.conf

    Example 34.4. MERLIN smb-merlin.conf File Share Section

    # Global parameters
    [global]
    workgroup = MIDEARTH
    netbios name = MERLIN
    [homes]
    comment = Home Directories
    valid users = %S
    read only = No
    browseable = No
    [office]
    comment = Data
    path = /data
    read only = No
    [netlogon]
    comment = NETLOGON
    path = /var/lib/samba/netlogon
    read only = Yes
    browseable = No
    [printers]
    comment = All Printers
    path = /var/spool/samba
    printable = Yes
    use client driver = Yes
    browseable = No

    Example 34.5. SAURON smb-sauron.conf File Share Section

    # Global parameters
    [global]
    workgroup = MIDEARTH
    netbios name = SAURON
    [www]
    comment = Web Pages
    path = /srv/www/htdocs
    read only = No

    Prev Up Next
    Chapter 33. Handling Large Directories Home Part IV. Migration and Updating
    diff --git a/docs/htmldocs/Samba3-HOWTO/ch-ldap-tls.html b/docs/htmldocs/Samba3-HOWTO/ch-ldap-tls.html index c734558944..59d3b72c1d 100644 --- a/docs/htmldocs/Samba3-HOWTO/ch-ldap-tls.html +++ b/docs/htmldocs/Samba3-HOWTO/ch-ldap-tls.html @@ -1,40 +1,40 @@ -Chapter 45. LDAP and Transport Layer Security
    Chapter 45. LDAP and Transport Layer Security
    Prev Part VI. Reference Section Next

    Chapter 45. LDAP and Transport Layer Security

    Gavin Henry

    Suretec Systems Limited, UK

    July 8, 2005

    Table of Contents

    Introduction
    Configuring
    Generating the Certificate Authority
    Generating the Server Certificate
    Installing the Certificates
    Testing
    Troubleshooting

    Introduction

    - - +Chapter 46. LDAP and Transport Layer Security

    Chapter 46. LDAP and Transport Layer Security
    Prev Part VI. Reference Section Next

    Chapter 46. LDAP and Transport Layer Security

    Gavin Henry

    Suretec Systems Limited, UK

    July 8, 2005

    Table of Contents

    Introduction
    Configuring
    Generating the Certificate Authority
    Generating the Server Certificate
    Installing the Certificates
    Testing
    Troubleshooting

    Introduction

    + + Up until now, we have discussed the straightforward configuration of OpenLDAP™, with some advanced features such as ACLs. This does not however, deal with the fact that the network transmissions are still in plain text. This is where Transport Layer Security (TLS) comes in.

    - + OpenLDAP™ clients and servers are capable of using the Transport Layer Security (TLS) framework to provide integrity and confidentiality protections in accordance with RFC 2830; Lightweight Directory Access Protocol (v3): Extension for Transport Layer Security.

    - + TLS uses X.509 certificates. All servers are required to have valid certificates, whereas client certificates are optional. We will only be discussing server certificates.

    Tip

    - - - + + + The DN of a server certificate must use the CN attribute to name the server, and the CN must carry the server's fully qualified domain name (FQDN). Additional alias names and wildcards may be present in the subjectAltName certificate extension. More details on server certificate names are in RFC2830.

    We will discuss this more in the next sections.

    Configuring

    - + Now on to the good bit.

    Generating the Certificate Authority

    - + In order to create the relevant certificates, we need to become our own Certificate Authority (CA). - [8] This is necessary, so we can sign the server certificate. + [8] This is necessary, so we can sign the server certificate.

    - - We will be using the OpenSSL [9] software for this, which is included with every great Linux® distribution. + + We will be using the OpenSSL [9] software for this, which is included with every great Linux® distribution.

    - TLS is used for many types of servers, but the instructions[10] presented here, are tailored for OpenLDAP. + TLS is used for many types of servers, but the instructions[10] presented here, are tailored for OpenLDAP.

    Note

    The Common Name (CN), in the following example, MUST be the fully qualified domain name (FQDN) of your ldap server. @@ -51,7 +51,7 @@ root# cd myCA

    - Now generate the CA:[11] + Now generate the CA:[11] 

     
 root#  /usr/share/ssl/misc/CA.pl -newca
@@ -209,7 +209,7 @@ TLS_CACERT /etc/openldap/cacert.pem
 	
    
 	That's all there is to it. Now on to the section called “Testing”

    Testing

    - + This is the easy part. Restart the server: 

     
@@ -220,7 +220,7 @@ Starting slapd:                                            [  OK  ]

    Then, using ldapsearch, test an anonymous search with the - -ZZ[12] option: + -ZZ[12] option: 

     
 root#  ldapsearch -x -b "dc=ldap,dc=abmas,dc=biz" \
@@ -265,7 +265,7 @@ sambaNextGroupRid: 67109863

    If you have any problems, please read the section called “Troubleshooting”

    Troubleshooting

    - + The most common error when configuring TLS, as I have already mentioned numerous times, is that the Common Name (CN) you entered in the section called “Generating the Server Certificate” is NOT the Fully Qualified Domain Name (FQDN) of your ldap server. @@ -275,13 +275,13 @@ your have the wrong permissions on the servercrt.pemchmod 640, as per the section called “Installing the Certificates”.

    For anything else, it's best to read through your ldap logfile or join the OpenLDAP mailing list. -


    [8] We could however, get our generated server certificate signed by proper CAs, like Thawte and VeriSign, which +


    [8] We could however, get our generated server certificate signed by proper CAs, like Thawte and VeriSign, which you pay for, or the free ones, via CAcert -

    [9] The downside to +

    [9] The downside to making our own CA, is that the certificate is not automatically recognized by clients, like the commercial - ones are.

    [10] For information straight from the + ones are.

    [10] For information straight from the horse's mouth, please visit http://www.openssl.org/docs/HOWTO/; the main OpenSSL - site.

    [11] Your CA.pl or CA.sh might not be + site.

    [11] Your CA.pl or CA.sh might not be in the same location as mine is, you can find it by using the locate command, i.e., locate CA.pl. If the command complains about the database being too old, run - updatedb as root to update it.

    [12] See man ldapsearch

    Prev Up Next
    Chapter 44. Samba Performance Tuning Home Chapter 46. Samba Support
    + updatedb as root to update it.

    [12] See man ldapsearch

    Prev Up Next
    Chapter 45. Samba Performance Tuning Home Chapter 47. Samba Support
    diff --git a/docs/htmldocs/Samba3-HOWTO/ch46.html b/docs/htmldocs/Samba3-HOWTO/ch46.html deleted file mode 100644 index eecd090290..0000000000 --- a/docs/htmldocs/Samba3-HOWTO/ch46.html +++ /dev/null @@ -1,106 +0,0 @@ -Chapter 46. Samba Support
    Chapter 46. Samba Support
    Prev Part VI. Reference Section Next

    Chapter 46. Samba Support

    Table of Contents

    Free Support
    Commercial Support

    - -One of the most difficult to answer questions in the information technology industry is, “What is -support?”. That question irritates some folks, as much as common answers may annoy others. -

    - -The most aggravating situation pertaining to support is typified when, as a Linux user, a call is made to -an Internet service provider who, instead of listening to the problem to find a solution, blandly replies: -“Oh, Linux? We do not support Linux!”. It has happened to me, and similar situations happen -through-out the IT industry. Answers like that are designed to inform us that there are some customers -that a business just does not want to deal with, and well may we feel the anguish of the rejection that -is dished out. -

    -One way to consider support is to view it as consisting of the right answer, in the right place, -at the right time, no matter the situation. Support is all that it takes to take away pain, disruption, -inconvenience, loss of productivity, disorientation, uncertainty, and real or perceived risk. -

    - - - -One of the forces that has become a driving force for the adoption of open source software is the fact that -many IT businesses have provided services that have perhaps failed to deliver what the customer expected, or -that have been found wanting for other reasons. -

    - - -In recognition of the need for needs satisfaction as the primary experience an information technology user or -consumer expects, the information provided in this chapter may help someone to avoid an unpleasant experience -in respect of problem resolution. -

    - - - -In the open source software arena there are two support options: free support and paid-for (commercial) -support. -

    Free Support

    - - - - - - - Free support may be obtained from friends, colleagues, user groups, mailing lists, and interactive help - facilities. An example of an interactive dacility is the Internet relay chat (IRC) channels that host user - supported mutual assistance. -

    - - - - - - The Samba project maintains a mailing list that is commonly used to discuss solutions to Samba deployments. - Information regarding subscription to the Samba mailing list can be found on the Samba web site. The public mailing list that can be used to obtain - free, user contributed, support is called the samba list. The email address for this list - is at mail:samba@samba.org. Information regarding the Samba IRC channels may be found on - the Samba IRC web page. -

    - - - - - As a general rule, it is considered poor net behavior to contact a Samba Team member directly - for free support. Most active members of the Samba Team work exceptionally long hours to assist - users who have demonstrated a qualified problem. Some team members may respond to direct email - or telephone contact, with requests for assistance, by requesting payment. A few of the Samba - Team members actually provide professional paid-for Samba support and it is therefore wise - to show appropriate discretion and reservation in all direct contact. -

    - - - - When you stumble across a Samba bug, often the quickest way to get it resolved is by posting - a bug report. All such reports are mailed to - the responsible code maintainer for action. The better the report, and the more serious it is, - the sooner it will be dealt with. On the other hand, if the responsible person can not duplicate - the reported bug it is likely to be rejected. It is up to you to provide sufficient information - that will permit the problem to be reproduced. -

    - - We all recognize that sometimes free support does not provide the answer that is sought within - the time-frame required. At other times the problem is elusive and you may lack the experience - necessary to isolate the problem and thus to resolve it. This is a situation where is may be - prudent to purchase paid-for support. -

    Commercial Support

    - There are six basic support oriented services that are most commonly sought by Samba sites: -

    • Assistance with network design

    • Staff Training

    • Assistance with Samba network deployment and installation

    • Priority telephone or email Samba configuration assistance

    • Trouble-shooting and diagnostic assistance

    • Provision of quality assured ready-to-install Samba binary packages

    - - - Information regarding companies that provide professional Samba support can be obtained by performing a Google - search, as well as by reference to the Samba Support web page. Companies who notify the Samba Team - that they provide commercial support are given a free listing that is sorted by the country of origin. - Multiple listings are permitted, however no guarantee is offered. It is left to you to qualify a support - provider and to satisfy yourself that both the company and its staff are able to deliver what is required of - them. -

    - - The policy within the Samba Team is to treat all commercial support providers equally and to show no - preference. As a result, Samba Team members who provide commercial support are lumped in with everyone else. - You are encouraged to obtain the services needed from a company in your local area. The open source movement - is pro-community; so do what you can to help a local business to prosper. -

    - - Open source software support can be found in any quality, at any price and in any place you can - to obtain it. Over 180 companies around the world provide Samba support, there is no excuse for - suffering in the mistaken belief that Samba is unsupported software it is supported. -

    Prev Up Next
    Chapter 45. LDAP and Transport Layer Security Home Chapter 47. DNS and DHCP Configuration Guide
    diff --git a/docs/htmldocs/Samba3-HOWTO/ch47.html b/docs/htmldocs/Samba3-HOWTO/ch47.html new file mode 100644 index 0000000000..7654b80389 --- /dev/null +++ b/docs/htmldocs/Samba3-HOWTO/ch47.html @@ -0,0 +1,106 @@ +Chapter 47. Samba Support
    Chapter 47. Samba Support
    Prev Part VI. Reference Section Next

    Chapter 47. Samba Support

    Table of Contents

    Free Support
    Commercial Support

    + +One of the most difficult to answer questions in the information technology industry is, “What is +support?”. That question irritates some folks, as much as common answers may annoy others. +

    + +The most aggravating situation pertaining to support is typified when, as a Linux user, a call is made to +an Internet service provider who, instead of listening to the problem to find a solution, blandly replies: +“Oh, Linux? We do not support Linux!”. It has happened to me, and similar situations happen +through-out the IT industry. Answers like that are designed to inform us that there are some customers +that a business just does not want to deal with, and well may we feel the anguish of the rejection that +is dished out. +

    +One way to consider support is to view it as consisting of the right answer, in the right place, +at the right time, no matter the situation. Support is all that it takes to take away pain, disruption, +inconvenience, loss of productivity, disorientation, uncertainty, and real or perceived risk. +

    + + + +One of the forces that has become a driving force for the adoption of open source software is the fact that +many IT businesses have provided services that have perhaps failed to deliver what the customer expected, or +that have been found wanting for other reasons. +

    + + +In recognition of the need for needs satisfaction as the primary experience an information technology user or +consumer expects, the information provided in this chapter may help someone to avoid an unpleasant experience +in respect of problem resolution. +

    + + + +In the open source software arena there are two support options: free support and paid-for (commercial) +support. +

    Free Support

    + + + + + + + Free support may be obtained from friends, colleagues, user groups, mailing lists, and interactive help + facilities. An example of an interactive dacility is the Internet relay chat (IRC) channels that host user + supported mutual assistance. +

    + + + + + + The Samba project maintains a mailing list that is commonly used to discuss solutions to Samba deployments. + Information regarding subscription to the Samba mailing list can be found on the Samba web site. The public mailing list that can be used to obtain + free, user contributed, support is called the samba list. The email address for this list + is at mail:samba@samba.org. Information regarding the Samba IRC channels may be found on + the Samba IRC web page. +

    + + + + + As a general rule, it is considered poor net behavior to contact a Samba Team member directly + for free support. Most active members of the Samba Team work exceptionally long hours to assist + users who have demonstrated a qualified problem. Some team members may respond to direct email + or telephone contact, with requests for assistance, by requesting payment. A few of the Samba + Team members actually provide professional paid-for Samba support and it is therefore wise + to show appropriate discretion and reservation in all direct contact. +

    + + + + When you stumble across a Samba bug, often the quickest way to get it resolved is by posting + a bug report. All such reports are mailed to + the responsible code maintainer for action. The better the report, and the more serious it is, + the sooner it will be dealt with. On the other hand, if the responsible person can not duplicate + the reported bug it is likely to be rejected. It is up to you to provide sufficient information + that will permit the problem to be reproduced. +

    + + We all recognize that sometimes free support does not provide the answer that is sought within + the time-frame required. At other times the problem is elusive and you may lack the experience + necessary to isolate the problem and thus to resolve it. This is a situation where is may be + prudent to purchase paid-for support. +

    Commercial Support

    + There are six basic support oriented services that are most commonly sought by Samba sites: +

    • Assistance with network design

    • Staff Training

    • Assistance with Samba network deployment and installation

    • Priority telephone or email Samba configuration assistance

    • Trouble-shooting and diagnostic assistance

    • Provision of quality assured ready-to-install Samba binary packages

    + + + Information regarding companies that provide professional Samba support can be obtained by performing a Google + search, as well as by reference to the Samba Support web page. Companies who notify the Samba Team + that they provide commercial support are given a free listing that is sorted by the country of origin. + Multiple listings are permitted, however no guarantee is offered. It is left to you to qualify a support + provider and to satisfy yourself that both the company and its staff are able to deliver what is required of + them. +

    + + The policy within the Samba Team is to treat all commercial support providers equally and to show no + preference. As a result, Samba Team members who provide commercial support are lumped in with everyone else. + You are encouraged to obtain the services needed from a company in your local area. The open source movement + is pro-community; so do what you can to help a local business to prosper. +

    + + Open source software support can be found in any quality, at any price and in any place you can + to obtain it. Over 180 companies around the world provide Samba support, there is no excuse for + suffering in the mistaken belief that Samba is unsupported software it is supported. +

    Prev Up Next
    Chapter 46. LDAP and Transport Layer Security Home Chapter 48. DNS and DHCP Configuration Guide
    diff --git a/docs/htmldocs/Samba3-HOWTO/classicalprinting.html b/docs/htmldocs/Samba3-HOWTO/classicalprinting.html index 95075b5213..da1a9d6a26 100644 --- a/docs/htmldocs/Samba3-HOWTO/classicalprinting.html +++ b/docs/htmldocs/Samba3-HOWTO/classicalprinting.html @@ -1,22 +1,22 @@ -Chapter 21. Classical Printing Support
    Chapter 21. Classical Printing Support
    Prev Part III. Advanced Configuration Next

    Chapter 21. Classical Printing Support

    Kurt Pfeifle

    Danka Deutschland GmbH

    Gerald (Jerry) Carter

    Samba Team

    John H. Terpstra

    Samba Team

    May 31, 2003

    Table of Contents

    Features and Benefits
    Technical Introduction
    Client to Samba Print Job Processing
    Printing-Related Configuration Parameters
    Simple Print Configuration
    Verifying Configuration with testparm
    Rapid Configuration Validation
    Extended Printing Configuration
    Detailed Explanation Settings
    Printing Developments Since Samba-2.2
    Point'n'Print Client Drivers on Samba Servers
    The Obsoleted [printer$] Section
    Creating the [print$] Share
    [print$] Stanza Parameters
    The [print$] Share Directory
    Installing Drivers into [print$]
    Add Printer Wizard Driver Installation
    Installing Print Drivers Using rpcclient
    Client Driver Installation Procedure
    First Client Driver Installation
    Setting Device Modes on New Printers
    Additional Client Driver Installation
    Always Make First Client Connection as root or “printer admin”
    Other Gotchas
    Setting Default Print Options for Client Drivers
    Supporting Large Numbers of Printers
    Adding New Printers with the Windows NT APW
    Error Message: “Cannot connect under a different Name”
    Take Care When Assembling Driver Files
    Samba and Printer Ports
    Avoiding Common Client Driver Misconfiguration
    The Imprints Toolset
    What Is Imprints?
    Creating Printer Driver Packages
    The Imprints Server
    The Installation Client
    Adding Network Printers without User Interaction
    The addprinter Command
    Migration of Classical Printing to Samba
    Publishing Printer Information in Active Directory or LDAP
    Common Errors
    I Give My Root Password but I Do Not Get Access
    My Print Jobs Get Spooled into the Spooling Directory, but Then Get Lost

    Features and Benefits

    - +Chapter 21. Classical Printing Support

    Chapter 21. Classical Printing Support
    Prev Part III. Advanced Configuration Next

    Chapter 21. Classical Printing Support

    Kurt Pfeifle

    Danka Deutschland GmbH

    Gerald (Jerry) Carter

    Samba Team

    John H. Terpstra

    Samba Team

    May 31, 2003

    Table of Contents

    Features and Benefits
    Technical Introduction
    Client to Samba Print Job Processing
    Printing-Related Configuration Parameters
    Simple Print Configuration
    Verifying Configuration with testparm
    Rapid Configuration Validation
    Extended Printing Configuration
    Detailed Explanation Settings
    Printing Developments Since Samba-2.2
    Point'n'Print Client Drivers on Samba Servers
    The Obsoleted [printer$] Section
    Creating the [print$] Share
    [print$] Stanza Parameters
    The [print$] Share Directory
    Installing Drivers into [print$]
    Add Printer Wizard Driver Installation
    Installing Print Drivers Using rpcclient
    Client Driver Installation Procedure
    First Client Driver Installation
    Setting Device Modes on New Printers
    Additional Client Driver Installation
    Always Make First Client Connection as root or “printer admin”
    Other Gotchas
    Setting Default Print Options for Client Drivers
    Supporting Large Numbers of Printers
    Adding New Printers with the Windows NT APW
    Error Message: “Cannot connect under a different Name”
    Take Care When Assembling Driver Files
    Samba and Printer Ports
    Avoiding Common Client Driver Misconfiguration
    The Imprints Toolset
    What Is Imprints?
    Creating Printer Driver Packages
    The Imprints Server
    The Installation Client
    Adding Network Printers without User Interaction
    The addprinter Command
    Migration of Classical Printing to Samba
    Publishing Printer Information in Active Directory or LDAP
    Common Errors
    I Give My Root Password but I Do Not Get Access
    My Print Jobs Get Spooled into the Spooling Directory, but Then Get Lost

    Features and Benefits

    + Printing is often a mission-critical service for the users. Samba can provide this service reliably and seamlessly for a client network consisting of Windows workstations.

    - - - - - - - - - - - - - - + + + + + + + + + + + + + + A Samba print service may be run on a standalone or domain member server, side by side with file serving functions, or on a dedicated print server. It can be made as tightly or as loosely secured as needs dictate. Configurations may be simple or complex. Available authentication schemes are essentially the same as @@ -30,23 +30,23 @@ efficient in case of large numbers of printers. If a central accounting of print page and supplying the raw data for all sorts of statistical reports) is required, this function is best supported by the newer Common UNIX Printing System (CUPS) as the print subsystem underneath the Samba hood.

    - - + + This chapter outlines the fundamentals of Samba printing as implemented by the more traditional UNIX BSD- and System V-style printing systems. Much of the information in this chapter applies also to CUPS. If you use CUPS, you may be tempted to jump to the next chapter, but you will certainly miss a few things if you do. For further information refer to CUPS Printing Support.

    Note

    - - - + + + Most of the following examples have been verified on Windows XP Professional clients. Where this document describes the responses to commands given, bear in mind that Windows 200x/XP clients are quite similar but may differ in minor details. Windows NT4 is somewhat different again. -

    Technical Introduction

    - - - +

    Technical Introduction

    + + + Samba's printing support always relies on the installed print subsystem of the UNIX OS it runs on. Samba is a middleman. It takes print files from Windows (or other SMB) clients and passes them to the real printing system for further processing; therefore, it needs to communicate with both sides: the Windows print @@ -54,42 +54,42 @@ clients and the UNIX printing system. Hence, we must differentiate between the v of which behave differently, as well as the various UNIX print subsystems, which themselves have different features and are accessed differently.

    - - + + This chapter deals with the traditional way of UNIX printing. The next chapter covers in great detail the more modern CUPS.

    Important

    - + CUPS users, be warned: do not just jump on to the next chapter. You might miss important information only found here!

    - - - - + + + + It is apparent from postings on the Samba mailing list that print configuration is one of the most problematic aspects of Samba administration today. Many new Samba administrators have the impression that Samba performs some sort of print processing. Rest assured, Samba does not perform any type of print processing. It does not do any form of print filtering.

    - - - - + + + + Samba obtains from its clients a data stream (print job) that it spools to a local spool area. When the entire print job has been received, Samba invokes a local UNIX/Linux print command and passes the spooled file to it. It is up to the local system printing subsystems to correctly process the print job and to submit it to the printer. -

    Client to Samba Print Job Processing

    +

    Client to Samba Print Job Processing

    Successful printing from a Windows client via a Samba print server to a UNIX printer involves six (potentially seven) stages:

    1. Windows opens a connection to the printer share.

    2. Samba must authenticate the user.

    3. Windows sends a copy of the print file over the network into Samba's spooling area.

    4. Windows closes the connection.

    5. Samba invokes the print command to hand the file over to the UNIX print subsystem's spooling area.

    6. The UNIX print subsystem processes the print job.

    7. The print file may need to be explicitly deleted from the Samba spooling area. This item depends on your print spooler - configuration settings.

    Printing-Related Configuration Parameters

    - - - + configuration settings.

    Printing-Related Configuration Parameters

    + + + There are a number of configuration parameters to control Samba's printing behavior. Please refer to the man page for smb.conf for an overview of these. As with other parameters, there are global-level (tagged with a G in the listings) and service-level (S) parameters. @@ -103,20 +103,20 @@ page for smb.conf for an overview of these. As wit or service-level shares (provided they do not have a different setting defined for the same parameter, thus overriding the global default). -

    Simple Print Configuration

    - - - - +

    Simple Print Configuration

    + + + + Simple Configuration with BSD Printing shows a simple printing configuration. If you compare this with your own, you may find additional parameters that have been preconfigured by your OS vendor. Following is a discussion and explanation of the parameters. This example does not use many parameters. However, in many environments these are enough to provide a valid smb.conf file that enables all clients to print. -

    Example 21.1. Simple Configuration with BSD Printing

    [global]
    printing = bsd
    load printers = yes
    [printers]
    path = /var/spool/samba
    printable = yes
    public = yes
    writable = no

    - - - +

    Example 21.1. Simple Configuration with BSD Printing

    [global]
    printing = bsd
    load printers = yes
    [printers]
    path = /var/spool/samba
    printable = yes
    public = yes
    writable = no

    + + + This is only an example configuration. Samba assigns default values to all configuration parameters. The defaults are conservative and sensible. When a parameter is specified in the smb.conf file, this overwrites the default value. The testparm utility when run as root is capable of reporting all @@ -124,26 +124,26 @@ settings, both default as well as smb.conf file se misconfigured settings. The complete output is easily 360 lines and more, so you may want to pipe it through a pager program.

    - - - + + + The syntax for the configuration file is easy to grasp. You should know that is not very picky about its syntax. As has been explained elsewhere in this book, Samba tolerates some spelling errors (such as browseable instead of browsable), and spelling is case-insensitive. It is permissible to use Yes/No or True/False for Boolean settings. Lists of names may be separated by commas, spaces, or tabs. -

    Verifying Configuration with testparm

    - - - - - - - - - - - +

    Verifying Configuration with testparm

    + + + + + + + + + + + To see all (or at least most) printing-related settings in Samba, including the implicitly used ones, try the command outlined below. This command greps for all occurrences of lp, print, spool, driver, @@ -194,11 +194,11 @@ may be important in your future dealings with Samba. The testparm in Samba-3 behaves differently from that in 2.2.x: used without the “-v” switch, it only shows you the settings actually written into! To see the complete configuration used, add the “-v” parameter to testparm. -

    Rapid Configuration Validation

    - - - - +

    Rapid Configuration Validation

    + + + + Should you need to troubleshoot at any stage, please always come back to this point first and verify if testparm shows the parameters you expect. To give you a warning from personal experience, try to just comment out the load printers parameter. If your 2.2.x system behaves like @@ -211,8 +211,8 @@ mine, you'll see this: root# testparm -v /etc/samba/smb.conf | egrep "(load printers)" load printers = Yes

    - - + + I assumed that commenting out of this setting should prevent Samba from publishing my printers, but it still did. It took some time to figure out the reason. But I am no longer fooled ... at least not by this. @@ -226,7 +226,7 @@ the reason. But I am no longer fooled ... at least not by this. root# testparm -s -v smb.conf.simpleprinting | egrep "(load printers)" load printers = No

    - + Only when the parameter is explicitly set to load printers = No would Samba conform with my intentions. So, my strong advice is:

    • Never rely on commented-out parameters.

    • Always set parameters explicitly as you intend them to @@ -237,8 +237,8 @@ The following is the most minimal configuration file: root# cat /etc/samba/smb.conf-minimal [printers]

      - - + + This example should show that you can use testparm to test any Samba configuration file. Actually, we encourage you not to change your working system (unless you know exactly what you are doing). Don't rely on the assumption that changes will only take effect after you restart smbd! @@ -276,10 +276,10 @@ be if you used this minimalistic configuration. Here is what you can expect to f

      testparm issued two warnings:

      • We did not specify the [printers] section as printable.

      • We did not tell Samba which spool directory to use.

      - - - + + + However, this was not fatal, and Samba will default to values that will work. Please, do not rely on this and do not use this example. This was included to encourage you to be careful to design and specify your setup to do precisely what you require. The outcome on your system may vary for some parameters given, since Samba may @@ -288,15 +288,15 @@ have been built with different compile-time options. Internal whitespace in a parameter value is retained verbatim. This means that a line consisting of, for example, -

      # This defines LPRng as the printing system
      printing = lprng

      +

      # This defines LPRng as the printing system
      printing = lprng

      will regard the whole of the string after the = sign as the value you want to define. This is an invalid value that will be ignored, and a default value will be used in its place. -

    Extended Printing Configuration

    - +

    Extended Printing Configuration

    + Extended BSD Printing Configuration shows a more verbose configuration for print-related settings in a BSD-style printing environment. What follows is a discussion and explanation of the various parameters. We chose to use BSD-style printing here because it is still the most commonly used @@ -304,22 +304,22 @@ system on legacy UNIX/Linux installations. New installations predominantly use C separate chapter. The example explicitly names many parameters that do not need to be specified because they are set by default. You could use a much leaner smb.conf file, or you can use testparm or SWAT to optimize the smb.conf file to remove all parameters that are set at default. -

    Example 21.2. Extended BSD Printing Configuration

    [global]
    printing = bsd
    load printers = yes
    show add printer wizard = yes
    printcap name = /etc/printcap
    printer admin = @ntadmin, root
    max print jobs = 100
    lpq cache time = 20
    use client driver = no
    [printers]
    comment = All Printers
    printable = yes
    path = /var/spool/samba
    browseable = no
    guest ok = yes
    public = yes
    read only = yes
    writable = no
    [my_printer_name]
    comment = Printer with Restricted Access
    path = /var/spool/samba_my_printer
    printer admin = kurt
    browseable = yes
    printable = yes
    writable = no
    hosts allow = 0.0.0.0
    hosts deny = turbo_xp, 10.160.50.23, 10.160.51.60
    guest ok = no

    - - - +

    Example 21.2. Extended BSD Printing Configuration

    [global]
    printing = bsd
    load printers = yes
    show add printer wizard = yes
    printcap name = /etc/printcap
    printer admin = @ntadmin, root
    max print jobs = 100
    lpq cache time = 20
    use client driver = no
    [printers]
    comment = All Printers
    printable = yes
    path = /var/spool/samba
    browseable = no
    guest ok = yes
    public = yes
    read only = yes
    writable = no
    [my_printer_name]
    comment = Printer with Restricted Access
    path = /var/spool/samba_my_printer
    printer admin = kurt
    browseable = yes
    printable = yes
    writable = no
    hosts allow = 0.0.0.0
    hosts deny = turbo_xp, 10.160.50.23, 10.160.51.60
    guest ok = no

    + + + This is an example configuration. You may not find all the settings that are in the configuration file that was provided by the OS vendor. Samba configuration parameters, if not explicitly set, default to a sensible value. To see all settings, as root use the testparm utility. testparm gives warnings for misconfigured settings. -

    Detailed Explanation Settings

    +

    Detailed Explanation Settings

    The following is a discussion of the settings from Extended BSD Printing Configuration Extended BSD Printing Configuration. -

    The [global] Section

    - +

    The [global] Section

    + The [global] section is one of four special sections (along with [homes], [printers], and [print$]). The [global] contains all parameters that apply to the server as a whole. It is the place for parameters that have only a global meaning. It may also contain service-level parameters that define @@ -327,33 +327,33 @@ default settings for all other sections and shares. This way you can simplify th setting the same value repeatedly. (Within each individual section or share, you may, however, override these globally set share settings and specify other values).

    printing = bsd

    - - + - + + Causes Samba to use default print commands applicable for the BSD (also known as RFC 1179 style or LPR/LPD) printing system. In general, the printing parameter informs Samba about the print subsystem it should expect. Samba supports CUPS, LPD, LPRNG, SYSV, HPUX, AIX, QNX, and PLP. Each of these systems defaults to a different print command (and other queue control commands).

    Caution

    - - + + The printing parameter is normally a service-level parameter. Since it is included here in the [global] section, it will take effect for all printer shares that are not defined differently. Samba-3 no longer supports the SOFTQ printing system.

    load printers = yes

    - + Tells Samba to create automatically all available printer shares. Available printer shares are discovered by scanning the printcap file. All created printer shares are also loaded for browsing. If you use this parameter, you do not need to specify separate shares for each printer. Each automatically created printer @@ -361,11 +361,11 @@ globally set share settings and specify other values). load printers = no setting will allow you to specify each UNIX printer you want to share separately, leaving out some you do not want to be publicly visible and available).

    show add printer wizard = yes

    - + Setting is normally enabled by default (even if the parameter is not specified in smb.conf). It causes the Add Printer Wizard icon to appear in the Printers folder of the Samba host's share listing (as shown in Network Neighborhood or by the net @@ -374,23 +374,23 @@ globally set share settings and specify other values). the [print$] share and associate it with a printer (if the respective queue exists before the action), or exchange a printer's driver for any other previously uploaded driver.

    max print jobs = 100

    - + Sets the upper limit to 100 print jobs being active on the Samba server at any one time. Should a client submit a job that exceeds this number, a "no more space available on server" type of error message will be returned by Samba to the client. A setting of zero (the default) means there is no limit at all.

    printcap name = /etc/printcap

    - + Tells Samba where to look for a list of available printer names. Where CUPS is used, make sure that a printcap file is written. This is controlled by the Printcap directive in the cupsd.conf file.

    printer admin = @ntadmin

    - - + + Members of the ntadmin group should be able to add drivers and set printer properties (ntadmin is only an example name; it needs to be a valid UNIX group name); root is implicitly always a printer admin. The @ sign precedes group names @@ -399,20 +399,20 @@ globally set share settings and specify other values). Samba-2.2). In larger installations, the printer admin parameter is normally a per-share parameter. This permits different groups to administer each printer share.

    lpq cache time = 20

    - + Controls the cache time for the results of the lpq command. It prevents the lpq command being called too often and reduces the load on a heavily used print server.

    use client driver = no

    - + If set to yes, only takes effect for Windows NT/200x/XP clients (and not for Win 95/98/ME). Its default value is No (or False). It must not be enabled on print shares (with a yes or true setting) that have valid drivers installed on the Samba server. For more detailed explanations, see the smb.conf man page.

    The [printers] Section

    - + The printers section is the second special section. If a section with this name appears in the smb.conf, users are able to connect to any printer specified in the Samba host's printcap file, because Samba on startup then creates a printer share for every printer name it finds in the printcap file. You could regard this @@ -468,9 +468,9 @@ Settings inside this container must be share-level parameters. connection), but only via print spooling operations. Normal write operations are not permitted.

    writable = no

    Is a synonym for read only = yes. -

    Any [my_printer_name] Section

    - +

    Any [my_printer_name] Section

    + If a [my_printer_name] section appears in the smb.conf file, which includes the parameter printable = yes Samba will configure it as a printer share. Windows 9x/Me clients may have problems with connecting or loading printer drivers if the share name has more @@ -502,11 +502,11 @@ finds one, it will connect to this and will not connect to a printer with the sa you can see, you could name IP addresses as well as NetBIOS hostnames here.

    guest ok = no

    This printer is not open for the guest account. -

    Print Commands

    - - - - +

    Print Commands

    + + + + In each section defining a printer (or in the [printers] section), a print command parameter may be defined. It sets a command to process the files that have been placed into the Samba print spool directory for that printer. (That spool directory was, @@ -518,8 +518,8 @@ command that just copies the print file to a temporary location for further inve to debug printing. If you craft your own print commands (or even develop print command shell scripts), make sure you pay attention to the need to remove the files from the Samba spool directory. Otherwise, your hard disk may soon suffer from shortage of free space. -

    Default UNIX System Printing Commands

    - +

    Default UNIX System Printing Commands

    + You learned earlier that Samba, in most cases, uses its built-in settings for many parameters if it cannot find an explicitly stated one in its configuration file. The same is true for the print command. The default print command varies depending on the printing parameter setting. In the commands listed in Default Printing Settings , you will @@ -528,29 +528,29 @@ J, and so on. These letters stand for printer name, spool file, and explained in more detail in Default Printing Settings presents an overview of key printing options but excludes the special case of CUPS, is discussed in CUPS Printing Support.

    Table 21.1. Default Printing Settings

    SettingDefault Printing Commands
    printing = bsd|aix|lprng|plpprint command is lpr -r -P%p %s
    printing = sysv|hpuxprint command is lp -c -P%p %s; rm %s
    printing = qnxprint command is lp -r -P%p -s %s
    printing = bsd|aix|lprng|plplpq command is lpq -P%p
    printing = sysv|hpuxlpq command is lpstat -o%p
    printing = qnxlpq command is lpq -P%p
    printing = bsd|aix|lprng|plplprm command is lprm -P%p %j
    printing = sysv|hpuxlprm command is cancel %p-%j
    printing = qnxlprm command is cancel %p-%j
    printing = bsd|aix|lprng|plplppause command is lp -i %p-%j -H hold
    printing = sysv|hpuxlppause command (...is empty)
    printing = qnxlppause command (...is empty)
    printing = bsd|aix|lprng|plplpresume command is lp -i %p-%j -H resume
    printing = sysv|hpuxlpresume command (...is empty)
    printing = qnxlpresume command (...is empty)

    - - - - + + + + For printing = CUPS, if Samba is compiled against libcups, it uses the CUPS API to submit jobs. (It is a good idea also to set printcap = cups in case your cupsd.conf is set to write its autogenerated printcap file to an unusual place). Otherwise, Samba maps to the System V printing commands with the -oraw option for printing; that is, it uses lp -c -d%p -oraw; rm %s. With printing = cups, and if Samba is compiled against libcups, any manually set print command will be ignored! -

    Custom Print Commands

    - - +

    Custom Print Commands

    + + After a print job has finished spooling to a service, the print command will be used by Samba via a system() call to process the spool file. Usually the command specified will submit the spool file to the host's printing subsystem. But there is no requirement at all that this must be the case. The print subsystem may not remove the spool file on its own, so whatever command you specify, you should ensure that the spool file is deleted after it has been processed.

    - + - + There is no difficulty with using your own customized print commands with the traditional printing systems. However, if you do not wish to roll your own, you should be well informed about the default built-in commands that Samba uses for each printing subsystem (see Default Printing @@ -566,20 +566,20 @@ The print command must contain at least one occurrence of the %p will be silently removed from the print command. In this case, the job is sent to the default printer.

    - - + + If specified in the [global] section, the print command given will be used for any printable service that does not have its own print command specified. If there is neither a specified print command for a printable service nor a global print command, spool files will be created but not processed! Most importantly, print files will not be removed, so they will consume disk space.

    - + Printing may fail on some UNIX systems when using the nobody account. If this happens, create an alternative guest account and give it the privilege to print. Set up this guest account in the [global] section with the guest account parameter.

    - + You can form quite complex print commands. You need to realize that print commands are just @@ -589,15 +589,15 @@ in the Samba print command is %$variable print command example, the following will log a print job to /tmp/print.log, print the file, then remove it. The semicolon (“;” is the usual separator for commands in shell scripts: -

    print command = echo Printing %s >> /tmp/print.log; lpr -P %p %s; rm %s

    +

    print command = echo Printing %s >> /tmp/print.log; lpr -P %p %s; rm %s

    You may have to vary your own command considerably from this example depending on how you normally print files on your system. The default for the print command parameter varies depending on the setting of the printing parameter. Another example is:

    print command = /usr/local/samba/bin/myprintscript %p %s

    Printing Developments Since Samba-2.2

    - - + + Prior to Samba-2.2.x, print server support for Windows clients was limited to LanMan printing calls. This is the same protocol level as Windows 9x/Me PCs offer when they share printers. Beginning with the 2.2.0 release, Samba started to support the native Windows NT printing mechanisms. These @@ -606,24 +606,24 @@ MS-RPCs use the SPOOLSS named pipe for al

    The additional functionality provided by the new SPOOLSS support includes:

    • - + Support for downloading printer driver files to Windows 95/98/NT/2000 clients upon demand (Point'n'Print).

    • - + Uploading of printer drivers via the Windows NT Add Printer Wizard (APW) or the Imprints tool set.

    • - - + + Support for the native MS-RPC printing calls such as StartDocPrinter, EnumJobs(), and so on. (See the MSDN documentation for more information on the Win32 printing API).

    • - + Support for NT Access Control Lists (ACL) on printer objects.

    • @@ -641,10 +641,10 @@ permits the installation of local printers that are not shared. This is an artif any Windows NT machine (server or client) may be used by a user as a workstation. Samba will publish all printers that are made available, either by default or by specific declaration via printer-specific shares.

      - + - - + + Windows NT/200x/XP Professional clients do not have to use the standard SMB printer share; they can print directly to any printer on another Windows NT host using MS-RPC. This, of course, assumes that @@ -659,13 +659,13 @@ it not necessary for printer drivers to be installed on a Samba host in order to Windows clients?” The answer to this is no, it is not necessary.

      - + Windows NT/2000 clients can, of course, also run their APW to install drivers locally (which then connect to a Samba-served print queue). This is the same method used by Windows 9x/Me clients. (However, a bug existed in Samba 2.2.0 that made Windows NT/2000 clients require that the Samba server possess a valid driver for the printer. This was fixed in Samba 2.2.1).

      - + But it is a new capability to install the printer drivers into the [print$] share of the Samba server, and a big convenience, too. Then all clients @@ -702,8 +702,8 @@ system, which is responsible for all further processing, as needed. be sent to the client.

      - - + + These parameters, including the printer driver file parameter, are now removed and cannot be used in installations of Samba-3. The share name [print$] is now used for the location of downloadable printer @@ -713,7 +713,7 @@ system, which is responsible for all further processing, as needed. of its ACLs) to support printer driver downloads and uploads. This does not mean Windows 9x/Me clients are now thrown aside. They can use Samba's [print$] share support just fine. -

    Creating the [print$] Share

    +

    Creating the [print$] Share

    In order to support the uploading and downloading of printer driver files, you must first configure a file share named [print$]. The public name of this share is hard coded @@ -724,13 +724,13 @@ You should modify the server's file to add the global parameters and create the [print$] file share (of course, some of the parameter values, such as path, are arbitrary and should be replaced with appropriate values for your site). See [print\$] Example. -

    Example 21.3. [print$] Example

    [global]
    # members of the ntadmin group should be able to add drivers and set
    # printer properties. root is implicitly always a 'printer admin'.
    printer admin = @ntadmin
    # ...
    [printers]
    # ...
    [print$]
    comment = Printer Driver Download Area
    path = /etc/samba/drivers
    browseable = yes
    guest ok = yes
    read only = yes
    write list = @ntadmin, root

    +

    Example 21.3. [print$] Example

    [global]
    # members of the ntadmin group should be able to add drivers and set
    # printer properties. root is implicitly always a 'printer admin'.
    printer admin = @ntadmin
    # ...
    [printers]
    # ...
    [print$]
    comment = Printer Driver Download Area
    path = /etc/samba/drivers
    browseable = yes
    guest ok = yes
    read only = yes
    write list = @ntadmin, root

    Of course, you also need to ensure that the directory named by the path parameter exists on the UNIX file system.

    [print$] Stanza Parameters

    - - + + The [print$] is a special section in smb.conf. It contains settings relevant to @@ -777,7 +777,7 @@ The following parameters are frequently needed in this share section: can copy files to the share. If this is a non-root account, then the account should also be mentioned in the global printer admin parameter. See the smb.conf man page for more information on configuring file shares. -

    The [print$] Share Directory

    +

    The [print$] Share Directory

    In order for a Windows NT print server to support the downloading of driver files by multiple client architectures, you must create several subdirectories within the [print$] service (i.e., the UNIX directory named by the path @@ -882,7 +882,7 @@ We provide detailed hints for each of these steps in the paragraphs that follow.

    Identifying Driver Files

    - + To find out about the driver files, you have two options. You can check the contents of the driver CDROM that came with your printer. Study the *.inf files located on the CD-ROM. This may not be possible, since the *.inf file might be missing. Unfortunately, vendors have now started @@ -905,8 +905,8 @@ driver files named on the printout. You'll need to recognize what Windows (and S Help File, and (optionally) Dependent Driver Files (this may vary slightly for Windows NT). You need to note all filenames for the next steps.

    - - + + Another method to quickly test the driver filenames and related paths is provided by the rpcclient utility. Run it with enumdrivers or with the @@ -950,8 +950,8 @@ Printer Driver Info 3:

    - - + + You may notice that this driver has quite a large number of Dependent files (there are worse cases, however). Also, strangely, the Driver File is tagged here @@ -961,7 +961,7 @@ You may notice that this driver has quite a large number of W32X86 (i.e., the Windows NT 2000/XP clients) onto a Windows PC. This PC can also host the Windows 9x/Me drivers, even if it runs on Windows NT, 2000, or XP.

    - + Since the [print$] share is usually accessible through the Network @@ -1056,8 +1056,8 @@ putting file HDNIS01Aux.dll as \W32X86\HDNIS01Aux.dll putting file HDNIS01_de.NTF as \W32X86\HDNIS01_de.NTF

    - - + + Whew that was a lot of typing! Most drivers are a lot smaller many have only three generic PostScript driver files plus one PPD. While we did retrieve the files from the 2 subdirectory of the W32X86 directory from the Windows box, we do not put them @@ -1066,7 +1066,7 @@ subdirectory of the W32X86 directory from the Wind for the Windows 9x/Me architecture into the WIN40/ subdirectory should you need them).

    smbclient to Confirm Driver Installation

    - + For now we verify that our files are there. This can be done with smbclient, too (but, of course, you can log in via SSH also and do this through a standard UNIX shell access): 

    @@ -1107,7 +1107,7 @@ ADOBEPSU.HLP                        A    18082  Sat May  3 23:18:45 2003
 PDFcreator2.PPD                     A    15746  Sun Apr 20 22:24:07 2003
               40976 blocks of size 262144. 709 blocks available

    - + Notice that there are already driver files present in the 2 subdirectory (probably from a @@ -1117,10 +1117,10 @@ like you retrieve ordinary files from a file share, by opening print$ in Windows install them per Point'n'Print. The reason is that Samba does not yet know that these files are something special, namely printer driver files, and it does not know to which print queue(s) these driver files belong. -

    Running rpcclient with adddriver

    - - - +

    Running rpcclient with adddriver

    + + + Next, you must tell Samba about the special category of the files you just uploaded into the [print$] share. This is done by the adddriver command. It will prompt Samba to register the driver files into its internal TDB database files. The @@ -1144,16 +1144,16 @@ cmd = adddriver "Windows NT x86" \ Printer Driver dm9110 successfully installed.

    - - - + + + After this step, the driver should be recognized by Samba on the print server. You need to be very careful when typing the command. Don't exchange the order of the fields. Some changes would lead to an NT_STATUS_UNSUCCESSFUL error message. These become obvious. Other changes might install the driver files successfully but render the driver unworkable. So take care! Hints about the syntax of the adddriver command are in the man page. provides a more detailed description, should you need it. -

    Checking adddriver Completion

    +

    Checking adddriver Completion

    One indication for Samba's recognition of the files as driver files is the successfully installed message. Another one is the fact that our files have been moved by the adddriver command into the 2 subdirectory. You can check this @@ -1198,17 +1198,17 @@ again with smbclient:

    Another verification is that the timestamp of the printing TDB files is now updated (and possibly their file size has increased). -

    Check Samba for Driver Recognition

    - +

    Check Samba for Driver Recognition

    + Now the driver should be registered with Samba. We can easily verify this and will do so in a moment. However, this driver is not yet associated with a particular printer. We may check the driver status of the files by at least three methods:

    • - - - - - + + + + + From any Windows client browse Network Neighborhood, find the Samba host, and open the Samba Printers and Faxes folder. Select any printer icon, right-click and select the printer Properties. Click the Advanced @@ -1218,7 +1218,7 @@ status of the files by at least three methods: see only its own architecture's list. If you do not have every driver installed for each platform, the list will differ if you look at it from Windows95/98/ME or Windows NT/2000/XP.)

    • - + From a Windows 200x/XP client (not Windows NT) browse Network Neighborhood, search for the Samba server, open the server's Printers folder, and right-click on the white background (with no printer highlighted). Select Server @@ -1247,8 +1247,8 @@ status of the files by at least three methods: for Windows NT 4.0 or 2000. To have it present for Windows 95, 98, and Me, you'll have to repeat the whole procedure with the WIN40 architecture and subdirectory. -

    Specific Driver Name Flexibility

    - +

    Specific Driver Name Flexibility

    + You can name the driver as you like. If you repeat the adddriver step with the same files as before but with a different driver name, it will work the same: 

    @@ -1271,18 +1271,18 @@ cmd = adddriver "Windows NT x86" \
 
 Printer Driver mydrivername successfully installed.

    - - - + + + You will be able to bind that driver to any print queue (however, you are responsible that you associate drivers to queues that make sense with respect to target printers). You cannot run the rpcclient adddriver command repeatedly. Each run consumes the files you had put into the [print$] share by moving them into the respective subdirectories, so you must execute an smbclient ... put command before each rpcclient ... adddriver command. -

    Running rpcclient with setdriver

    - - +

    Running rpcclient with setdriver

    + + Samba needs to know which printer owns which driver. Create a mapping of the driver to a printer, and store this information in Samba's memory, the TDB files. The rpcclient setdriver command achieves exactly this: @@ -1309,11 +1309,11 @@ The setdriver command will only succeed if the prin bug in 2.2.x prevented Samba from recognizing freshly installed printers. You had to restart Samba, or at least send an HUP signal to all running smbd processes to work around this: kill -HUP `pidof smbd`. -

    Client Driver Installation Procedure

    +

    Client Driver Installation Procedure

    As Don Quixote said, “The proof of the pudding is in the eating.” The proof for our setup lies in the printing. So let's install the printer driver onto the client PCs. This is not as straightforward as it may seem. Read on. -

    First Client Driver Installation

    +

    First Client Driver Installation

    Especially important is the installation onto the first client PC (for each architectural platform separately). Once this is done correctly, all further clients are easy to set up and shouldn't need further attention. What follows is a description for the recommended first procedure. You now work from a client @@ -1347,7 +1347,7 @@ appeared in your local Printer folder (ch Settings -> Control Panel -> Printers and Faxes).

    - + Most likely you are tempted to try to print a test page. After all, you now can open the printer properties, and on the General tab there is a button offering to do just that. But chances are that you get an error message saying "Unable to print Test Page." The @@ -1359,18 +1359,18 @@ driver. We now explain what that means.

    Setting Device Modes on New Printers

    For a printer to be truly usable by a Windows NT/200x/XP client, it must possess:

    • - + A valid device mode generated by the driver for the printer (defining things like paper size, orientation and duplex settings).

    • - + A complete set of printer driver data generated by the driver.

    - - - - - + + + + + If either of these is incomplete, the clients can produce less than optimal output at best. In the worst cases, unreadable garbage or nothing at all comes from the printer, or it produces a harvest of error messages when attempting to print. Samba stores the named values and all printing-related information in @@ -1396,7 +1396,7 @@ to set it on the Samba server. The easiest means of doing so is to simply change the server's printer. This executes enough of the printer driver program on the client for the desired effect to happen and feeds back the new device mode to our Samba server. You can use the native Windows NT/200x/XP printer properties page from a Window client for this: -

    Procedure 21.1. Procedure to Initialize the Printer Driver Settings

    1. +

      Procedure 21.1. Procedure to Initialize the Printer Driver Settings

      1. Browse the Network Neighborhood.

      2. Find the Samba server. @@ -1426,13 +1426,13 @@ device mode to Samba, which now stores it in its TDB files. Once the driver is i you can follow the analogous steps by accessing the local Printers folder, too, if you are a Samba printer admin user. From now on, printing should work as expected.

        - + Samba includes a service-level parameter name default devmode for generating a default device mode for a printer. Some drivers function well with Samba's default set of properties. Others may crash the client's spooler service. So use this parameter with caution. It is always better to have the client generate a valid device mode for the printer and store it on the server for you. -

      Additional Client Driver Installation

      - +

      Additional Client Driver Installation

      + Every additional driver may be installed in the same way as just described. Browse Network Neighborhood, open the Printers folder on Samba server, right-click on Printer, and choose Connect.... Once this completes (should be @@ -1445,14 +1445,14 @@ using this command on Windows 200x/XP Professional workstations: rundll32 shell32.dll,SHHelpShortcuts_RunDLL PrintersFolder

      or this command on Windows NT 4.0 workstations: - + 

       rundll32 shell32.dll,Control_RunDLL MAIN.CPL @2

      You can enter the commands either inside a DOS box window or in the Run command... field from the Start menu. -

      Always Make First Client Connection as root or “printer admin”

      +

      Always Make First Client Connection as root or “printer admin”

      After you installed the driver on the Samba server (in its [print$] share), you should always make sure that your first client installation completes correctly. Make it a habit for yourself to build the very first connection from a client as printer admin. This is to make @@ -1467,7 +1467,7 @@ back again. Next, modify the other settings (for example, you do not want the de Letter when you are all using A4, right? You may want to set the printer for duplex as the default, and so on).

      - + To connect as root to a Samba printer, try this command from a Windows 200x/XP DOS box command prompt: 

       C:\> runas /netonly /user:root "rundll32 printui.dll,PrintUIEntry /p /t3 /n 
@@ -1481,13 +1481,13 @@ by all clients. Alternatively, instead of root you can name one other member of
 Now all the other users downloading and installing the driver the same way (using
 Point'n'Print) will have the same defaults set for them. If you miss this step, you'll get a
 lot of help desk calls from your users, but maybe you like to talk to people.
-

    Other Gotchas

    +

    Other Gotchas

    Your driver is installed. It is now ready for Point'n'Print installation by the clients. You may have tried to download and use it on your first client machine, but wait. Let's make sure you are acquainted first with a few tips and tricks you may find useful. For example, suppose you did not set the defaults on the printer, as advised in the preceding paragraphs. Your users complain about various issues (such as, “We need to set the paper size for each job from Letter to A4 and it will not store it”). -

    Setting Default Print Options for Client Drivers

    +

    Setting Default Print Options for Client Drivers

    The last sentence might be viewed with mixed feelings by some users and Admins. They have struggled for hours and could not arrive at a point where their settings seemed to be saved. It is not their fault. The confusing thing is that in the multitabbed dialog that pops up when you right-click on the printer name and select @@ -1536,7 +1536,7 @@ days of Windows NT, so it is only natural to try the same way with Windows 200x/ there is now a different path to arrive at an identical-looking, but functionally different, dialog to set defaults for all users.

    Tip

    Try (on Windows 200x/XP) to run this command (as a user with the right privileges): - +

    rundll32 printui.dll,PrintUIEntry /p /t3 /n\\SAMBA-SERVER\printersharename

    @@ -1547,7 +1547,7 @@ rundll32 printui.dll,PrintUIEntry /p /t0 /n\\SAMBA To see the tab with the Printing Preferences button (the one that does not set systemwide defaults), you can start the commands from inside a DOS box or from Start -> Run. -

    Supporting Large Numbers of Printers

    +

    Supporting Large Numbers of Printers

    One issue that has arisen during the recent development phase of Samba is the need to support driver downloads for hundreds of printers. Using Windows NT APW for this task is somewhat awkward (to say the least). If you do not want to acquire RSS pains from the printer installation clicking orgy alone, you need @@ -1630,7 +1630,7 @@ It may not be easy to recognize that the first call to enu “dm9110” printer with an empty string where the driver should have been listed (between the two commas in the description field). After the setdriver command succeeds, all is well. -

    Adding New Printers with the Windows NT APW

    +

    Adding New Printers with the Windows NT APW

    By default, Samba exhibits all printer shares defined in smb.conf in the Printers folder. Also located in this folder is the Windows NT Add Printer Wizard icon. The APW will be shown only if:

    • @@ -1670,11 +1670,11 @@ share is still not defined, an error of "Access Denied"< necessarily a root account. A map to guest = bad user may have connected you unwittingly under the wrong privilege. You should check it by using the smbstatus command. -

    Error Message: “Cannot connect under a different Name”

    +

    Error Message: “Cannot connect under a different Name”

    Once you are connected with the wrong credentials, there is no means to reverse the situation other than to close all Explorer windows, and perhaps reboot.

    • - + The net use \\SAMBA-SERVER\sharename /user:root gives you an error message: “Multiple connections to a server or a shared resource by the same user utilizing several user names are not allowed. Disconnect all previous connections to the server, @@ -1700,7 +1700,7 @@ The easiest way to forcefully terminate all connections from your client to a se C:\> net use * /delete

      This will also disconnect all mapped drives and will allow you create fresh connection as required. -

    Take Care When Assembling Driver Files

    +

    Take Care When Assembling Driver Files

    You need to be extremely careful when you take notes about the files belonging to a particular driver. Don't confuse the files for driver version “0” (for Windows 9x/Me, going into [print$]/WIN/0/), driver version 2 (kernel mode driver for Windows NT, @@ -1831,11 +1831,11 @@ comparison: In my example were even more differences than shown here. Conclusion: you must be careful to select the correct driver files for each driver version. Don't rely on the names alone, and don't interchange files belonging to different driver versions. -

    Samba and Printer Ports

    - - - - +

    Samba and Printer Ports

    + + + + Windows NT/2000 print servers associate a port with each printer. These normally take the form of LPT1:, COM1:, FILE:, and so on. Samba must also support the concept of ports associated with a printer. By default, only one printer port, named “Samba @@ -1844,22 +1844,22 @@ print; rather it is a requirement of Windows clients. They insist on being told they request this information; otherwise, they throw an error message at you. So Samba fakes the port information to keep the Windows clients happy.

    - + Samba does not support the concept of Printer Pooling internally either. Printer pooling assigns a logical printer to multiple ports as a form of load balancing or failover.

    If you require multiple ports to be defined for some reason or another (my users and my boss should not know that they are working with Samba), configure the enumports command, which can be used to define an external program that generates a listing of ports on a system. -

    Avoiding Common Client Driver Misconfiguration

    +

    Avoiding Common Client Driver Misconfiguration

    So now the printing works, but there are still problems. Most jobs print well, some do not print at all. Some jobs have problems with fonts, which do not look good. Some jobs print fast and some are dead-slow. We cannot cover it all, but we want to encourage you to read the brief paragraph about “Avoiding the Wrong PostScript Driver Settings” in CUPS Printing Chapter, Avoiding Critical PostScript Driver Settings on the Client. -

    The Imprints Toolset

    - +

    The Imprints Toolset

    + The Imprints tool set provides a UNIX equivalent of the Windows NT APW. For complete information, please refer to the Imprints Web site as well as the documentation included with the Imprints source distribution. This section provides only a brief introduction @@ -1871,7 +1871,7 @@ printing used in Samba. If you wish to volunteer, please coordinate your efforts mailing list. The toolset is still in usable form, but only for a series of older printer models where there are prepared packages to use. Packages for more up-to-date print devices are needed if Imprints should have a future. Information regarding the Imprints toolset can be obtained from the Imprints home page. -

    What Is Imprints?

    +

    What Is Imprints?

    Imprints is a collection of tools for supporting these goals:

    • Providing a central repository of information regarding Windows NT and 95/98 printer driver packages. @@ -1880,19 +1880,19 @@ Imprints is a collection of tools for supporting these goals:

    • Providing an installation client that will obtain printer drivers from a central Internet (or intranet) Imprints Server repository and install them on remote Samba and Windows NT4 print servers. -

    Creating Printer Driver Packages

    +

    Creating Printer Driver Packages

    The process of creating printer driver packages is beyond the scope of this document (refer to Imprints.txt, included with the Samba distribution for more information). In short, an Imprints driver package is a gzipped tarball containing the driver files, related INF files, and a control file needed by the installation client. -

    The Imprints Server

    +

    The Imprints Server

    The Imprints server is really a database server that may be queried via standard HTTP mechanisms. Each printer entry in the database has an associated URL for the actual downloading of the package. Each package is digitally signed via GnuPG, which can be used to verify that the package downloaded is actually the one referred in the Imprints database. It is strongly recommended that this security check not be disabled. -

    The Installation Client

    +

    The Installation Client

    More information regarding the Imprints installation client is available from the documentation file Imprints-Client-HOWTO.ps that is included with the Imprints source package. The Imprints installation client comes in two forms: @@ -1922,7 +1922,7 @@ requirement internally; therefore, “How can you use th

    The way of sidestepping this limitation is to require that all Imprints printer driver packages include both the Intel Windows NT and 95/98 printer drivers and that the NT driver is installed first. -

    Adding Network Printers without User Interaction

    +

    Adding Network Printers without User Interaction

    The following MS Knowledge Base article may be of some help if you need to handle Windows 2000 clients: How to Add Printers with No User Interaction in Windows 2000, (Microsoft KB 189105). It also applies to Windows XP Professional clients. The ideas sketched out in this section are inspired by this @@ -1981,7 +1981,7 @@ Since network printers are installed per user, this much simplifies the process up to date. The few extra seconds at logon time will not really be noticeable. Printers can be centrally added, changed, and deleted at will on the server with no user intervention required from the clients (you just need to keep the logon scripts up to date). -

    The addprinter Command

    +

    The addprinter Command

    The addprinter command can be configured to be a shell script or program executed by Samba. It is triggered by running the APW from a client against the Samba print server. The APW asks the user to fill in several fields (such as printer name, driver to be used, comment, port monitor, @@ -1989,7 +1989,7 @@ and so on). These parameters are passed on to Samba by the APW. If the addprinte way that it can create a new printer (through writing correct printcap entries on legacy systems or by executing the lpadmin command on more modern systems) and create the associated share, then the APW will in effect really create a new printer on Samba and the UNIX print subsystem! -

    Migration of Classical Printing to Samba

    +

    Migration of Classical Printing to Samba

    The basic NT-style printer driver management has not changed considerably in 3.0 over the 2.2.x releases (apart from many small improvements). Here migration should be quite easy, especially if you followed previous advice to stop using deprecated parameters in your setup. For migrations from an existing 2.0.x @@ -2019,11 +2019,11 @@ follow several paths. Here are possible scenarios for migration: solution is to use the Windows NT APW to install the NT drivers and the 9x/Me drivers. This can be scripted using smbclient and rpcclient. See the Imprints installation client on the Imprints web site for example. See also the discussion of rpcclient usage in CUPS Printing. -

    Publishing Printer Information in Active Directory or LDAP

    +

    Publishing Printer Information in Active Directory or LDAP

    This topic has also been addressed in Remote and Local Management The Net Command. If you wish to volunteer your services to help document this further, please contact John H. Terpstra. -

    Common Errors

    I Give My Root Password but I Do Not Get Access

    +

    Common Errors

    I Give My Root Password but I Do Not Get Access

    Do not confuse the root password, which is valid for the UNIX system (and in most cases stored in the form of a one-way hash in a file named /etc/shadow), with the password used to authenticate against Samba. Samba does not know the UNIX password. Root access to Samba resources @@ -2034,7 +2034,7 @@ command as follows: New SMB password: secret Retype new SMB password: secret

    -

    My Print Jobs Get Spooled into the Spooling Directory, but Then Get Lost

    +

    My Print Jobs Get Spooled into the Spooling Directory, but Then Get Lost

    Do not use the existing UNIX print system spool directory for the Samba spool directory. It may seem convenient and a savings of space, but it only leads to problems. The two must be separate. The UNIX/Linux system print spool directory (e.g., /var/spool/cups) is typically owned by a diff --git a/docs/htmldocs/Samba3-HOWTO/compiling.html b/docs/htmldocs/Samba3-HOWTO/compiling.html index 2e912ee701..0ff79c6fc4 100644 --- a/docs/htmldocs/Samba3-HOWTO/compiling.html +++ b/docs/htmldocs/Samba3-HOWTO/compiling.html @@ -1,9 +1,9 @@ -Chapter 41. How to Compile Samba

    Chapter 41. How to Compile Samba
    Prev Part VI. Reference Section Next

    Chapter 41. How to Compile Samba

    Jelmer R. Vernooij

    The Samba Team

    John H. Terpstra

    Samba Team

    Andrew Tridgell

    Samba Team

    22 May 2001

    18 March 2003

    June 2005

    Table of Contents

    Access Samba Source Code via Subversion
    Introduction
    Subversion Access to samba.org
    Accessing the Samba Sources via rsync and ftp
    Verifying Samba's PGP Signature
    Building the Binaries
    Compiling Samba with Active Directory Support
    Starting the smbd nmbd and winbindd
    Starting from inetd.conf
    Alternative: Starting smbd as a Daemon

    +Chapter 42. How to Compile Samba

    Chapter 42. How to Compile Samba
    Prev Part VI. Reference Section Next

    Chapter 42. How to Compile Samba

    Jelmer R. Vernooij

    The Samba Team

    John H. Terpstra

    Samba Team

    Andrew Tridgell

    Samba Team

    22 May 2001

    18 March 2003

    June 2005

    Table of Contents

    Access Samba Source Code via Subversion
    Introduction
    Subversion Access to samba.org
    Accessing the Samba Sources via rsync and ftp
    Verifying Samba's PGP Signature
    Building the Binaries
    Compiling Samba with Active Directory Support
    Starting the smbd nmbd and winbindd
    Starting from inetd.conf
    Alternative: Starting smbd as a Daemon

    You can obtain the Samba source file from the Samba Web site. To obtain a development version, you can download Samba from Subversion or using rsync. -

    Access Samba Source Code via Subversion

    Introduction

    - +

    Access Samba Source Code via Subversion

    Introduction

    + Samba is developed in an open environment. Developers use a Subversion to “checkin” (also known as “commit”) new source code. Samba's various Subversion branches can @@ -12,13 +12,13 @@ detailed in this chapter.

    This chapter is a modified version of the instructions found at the Samba Web site. -

    Subversion Access to samba.org

    +

    Subversion Access to samba.org

    The machine samba.org runs a publicly accessible Subversion repository for access to the source code of several packages, including Samba, rsync, distcc, ccache, and jitterbug. There are two main ways of accessing the Subversion server on this host. -

    Access via ViewCVS

    - +

    Access via ViewCVS

    + You can access the source code via your favorite WWW browser. This allows you to access the contents of individual files in the repository and also to look at the revision history and commit logs of individual files. You can also ask for a diff @@ -26,8 +26,8 @@ listing between any two versions on the repository.

    Use the URL http://viewcvs.samba.org/. -

    Access via Subversion

    - +

    Access via Subversion

    + You can also access the source code via a normal Subversion client. This gives you much more control over what you can do with the repository and allows you to check out whole source trees and keep them up to date via normal Subversion commands. This is the preferred method of access if you are a developer and not just a @@ -37,7 +37,7 @@ a Subversion client. Your distribution might include one, or you can download th sources from http://subversion.tigris.org/.

    To gain access via anonymous Subversion, use the following steps. -

    Procedure 41.1. Retrieving Samba using Subversion

    1. +

      Procedure 42.1. Retrieving Samba using Subversion

      1. Install a recent copy of Subversion. All you really need is a copy of the Subversion client binary.

      2. @@ -62,9 +62,9 @@ To gain access via anonymous Subversion, use the following steps. 

         	svn update

        -

    Accessing the Samba Sources via rsync and ftp

    - - +

    Accessing the Samba Sources via rsync and ftp

    + + pserver.samba.org also exports unpacked copies of most parts of the Subversion tree at the Samba pserver location and also via anonymous rsync at the Samba rsync server location. I recommend using rsync rather @@ -74,9 +74,9 @@ To gain access via anonymous Subversion, use the following steps. The disadvantage of the unpacked trees is that they do not support automatic merging of local changes as Subversion does. rsync access is most convenient for an initial install. -

    Verifying Samba's PGP Signature

    - - +

    Verifying Samba's PGP Signature

    + + It is strongly recommended that you verify the PGP signature for any source file before installing it. Even if you're not downloading from a mirror site, verifying PGP signatures should be a standard reflex. Many people today use the GNU GPG tool set in place of PGP. @@ -87,7 +87,7 @@ With that said, go ahead and download the following files: $ wget http://us1.samba.org/samba/ftp/samba-3.0.20.tar.asc $ wget http://us1.samba.org/samba/ftp/samba-pubkey.asc

    - + The first file is the PGP signature for the Samba source file; the other is the Samba public PGP key itself. Import the public PGP key with: 

    @@ -105,9 +105,9 @@ example of what you would not want to see would be:
 
     gpg: BAD signature from “Samba Distribution Verification Key”
 
    
-

    Building the Binaries

    - - +

    Building the Binaries

    + + After the source tarball has been unpacked, the next step involves configuration to match Samba to your operating system platform. If your source directory does not contain the configure script, @@ -120,7 +120,7 @@ gpg: BAD signature from “Samba Distribution Verificati root# ./autogen.sh

    - + To build the binaries, run the program ./configure in the source directory. This should automatically configure Samba for your operating system. If you have unusual @@ -135,7 +135,7 @@ gpg: BAD signature from “Samba Distribution Verificati root# ./configure [... arguments ...]

    - + Execute the following create the binaries: 

     root#  make
@@ -164,7 +164,7 @@ gpg: BAD signature from “Samba Distribution Verificati

    As you can see from this, building and installing Samba does not need to result in disaster! -

    Compiling Samba with Active Directory Support

    +

    Compiling Samba with Active Directory Support

    In order to compile Samba with ADS support, you need to have installed on your system:

    • @@ -187,13 +187,13 @@ gpg: BAD signature from “Samba Distribution Verificati If it does not, configure did not find your KRB5 libraries or your LDAP libraries. Look in config.log to figure out why and fix it. -

      Installing the Required Packages for Debian

      On Debian, you need to install the following packages:

      +

      Installing the Required Packages for Debian

      On Debian, you need to install the following packages:

      • libkrb5-dev

      • krb5-user

      -

      Installing the Required Packages for Red Hat Linux

      On Red Hat Linux, this means you should have at least:

      +

      Installing the Required Packages for Red Hat Linux

      On Red Hat Linux, this means you should have at least:

      • krb5-workstation (for kinit)

      • krb5-libs (for linking with)

      • krb5-devel (because you are compiling from source)

      in addition to the standard development environment.

      If these files are not installed on your system, you should check the installation CDs to find which has them and install the files using your tool of choice. If in doubt - about what tool to use, refer to the Red Hat Linux documentation.

      SuSE Linux Package Requirements

      + about what tool to use, refer to the Red Hat Linux documentation.

      SuSE Linux Package Requirements

      SuSE Linux installs Heimdal packages that may be required to allow you to build binary packages. You should verify that the development libraries have been installed on your system. @@ -204,7 +204,7 @@ gpg: BAD signature from “Samba Distribution Verificati the maximum capabilities that are available. You should consider using SuSE-provided packages where they are available.

    Starting the smbd nmbd and winbindd

    - + You must choose to start smbd, winbindd and nmbd either as daemons or from inetd. Don't try to do both! Either you can put them in inetd.conf and have them started on demand by @@ -216,7 +216,7 @@ gpg: BAD signature from “Samba Distribution Verificati

    The main advantage of starting smbd and nmbd using the recommended daemon method is that they will respond slightly more quickly to an initial connection request. -

    Starting from inetd.conf

    Note

    The following will be different if +

    Starting from inetd.conf

    Note

    The following will be different if you use NIS, NIS+, or LDAP to distribute services maps.

    Look at your /etc/services. What is defined at port 139/tcp? If nothing is defined, then add a line like this:

    netbios-ssn     139/tcp

    Similarly for 137/udp, you should have an entry like:

    netbios-ns	137/udp

    @@ -225,12 +225,12 @@ gpg: BAD signature from “Samba Distribution Verificati netbios-ssn stream tcp nowait root /usr/local/samba/sbin/smbd smbd netbios-ns dgram udp wait root /usr/local/samba/sbin/nmbd nmbd

    -

    +

    The exact syntax of /etc/inetd.conf varies between UNIXes. Look at the other entries in inetd.conf for a guide.

    - + Some distributions use xinetd instead of inetd. Consult the xinetd manual for configuration information.

    Note

    Some UNIXes already have entries like netbios_ns @@ -238,7 +238,7 @@ netbios-ns dgram udp wait root /usr/local/samba/sbin/nmbd nmbd You must edit /etc/services or /etc/inetd.conf to make them consistent.

    Note

    - + On many systems you may need to use the interfaces option in smb.conf to specify the IP address and netmask of your interfaces. Run @@ -253,13 +253,13 @@ netbios-ns dgram udp wait root /usr/local/samba/sbin/nmbd nmbd

    Restart inetd, perhaps just send it a HUP, like this: - + 

     root# killall -HUP inetd

    -

    Alternative: Starting smbd as a Daemon

    - - +

    Alternative: Starting smbd as a Daemon

    + + To start the server as a daemon, you should create a script something like this one, perhaps calling it startsmb. 

    @@ -278,7 +278,7 @@ netbios-ns dgram udp wait root /usr/local/samba/sbin/nmbd nmbd
 	If you use the SVR4-style init system, you may like to look at the
 	examples/svr4-startup script to make Samba fit
 	into that system.
-

    Starting Samba for Red Hat Linux

    +

    Starting Samba for Red Hat Linux

    Red Hat Linux has not always included all Samba components in the standard installation. So versions of Red Hat Linux do not install the winbind utility, even though it is present on the installation CDROM media. Check to see if the winbindd is present @@ -311,7 +311,7 @@ netbios-ns dgram udp wait root /usr/local/samba/sbin/nmbd nmbd root# chkconfig winbind on

    Samba will be started automatically at every system reboot. -

    Starting Samba for Novell SUSE Linux

    +

    Starting Samba for Novell SUSE Linux

    Novell SUSE Linux products automatically install all essential Samba components in a default installation. Configure your smb.conf file, then execute the following to start Samba: 

    @@ -327,4 +327,4 @@ netbios-ns dgram udp wait root /usr/local/samba/sbin/nmbd nmbd
 root#  chkconfig winbind on

    The Samba services will now be started automatically following a system reboot. -

    Prev Up Next
    Part VI. Reference Section Home Chapter 42. Portability
    +

    Prev Up Next
    Part VI. Reference Section Home Chapter 43. Portability
    diff --git a/docs/htmldocs/Samba3-HOWTO/diagnosis.html b/docs/htmldocs/Samba3-HOWTO/diagnosis.html index 7ee0b00340..1162e466b1 100644 --- a/docs/htmldocs/Samba3-HOWTO/diagnosis.html +++ b/docs/htmldocs/Samba3-HOWTO/diagnosis.html @@ -1,5 +1,5 @@ -Chapter 38. The Samba Checklist
    Chapter 38. The Samba Checklist
    Prev Part V. Troubleshooting Next

    Chapter 38. The Samba Checklist

    Andrew Tridgell

    Samba Team

    Jelmer R. Vernooij

    The Samba Team

    Dan Shearer

    Samba Team

    Wed Jan 15

    Table of Contents

    Introduction
    Assumptions
    The Tests

    Introduction

    - +Chapter 38. The Samba Checklist

    Chapter 38. The Samba Checklist
    Prev Part V. Troubleshooting Next

    Chapter 38. The Samba Checklist

    Andrew Tridgell

    Samba Team

    Jelmer R. Vernooij

    The Samba Team

    Dan Shearer

    Samba Team

    Wed Jan 15

    Table of Contents

    Introduction
    Assumptions
    The Tests

    Introduction

    + This file contains a list of tests you can perform to validate your Samba server. It also tells you what the likely cause of the problem is if it fails any one of these steps. If it passes all these tests, @@ -14,7 +14,7 @@ to solve a problem. If you send one of the Samba mailing lists an email saying, “It does not work,” and you have not followed this test procedure, you should not be surprised if your email is ignored. -

    Assumptions

    +

    Assumptions

    In all of the tests, it is assumed you have a Samba server called BIGSERVER and a PC called ACLIENT, both in workgroup TESTGROUP.

    @@ -24,31 +24,31 @@ It is also assumed you know the name of an available share in your smb.conf. I for our examples this share is called tmp. You can add a tmp share like this by adding the lines shown in the next example. -

    Example 38.1. smb.conf with [tmp] Share

    [tmp]
    comment = temporary files
    path = /tmp
    read only = yes

    Note

    +

    Example 38.1. smb.conf with [tmp] Share

    [tmp]
    comment = temporary files
    path = /tmp
    read only = yes

    Note

    These tests assume version 3.0.0 or later of the Samba suite. Some commands shown did not exist in earlier versions.

    - - - + + + Please pay attention to the error messages you receive. If any error message reports that your server is being unfriendly, you should first check that your IP name resolution is correctly set up. Make sure your /etc/resolv.conf file points to name servers that really do exist.

    - - - - + + + + Also, if you do not have DNS server access for name resolution, please check that the settings for your smb.conf file results in dns proxy = no. The best way to check this is with testparm smb.conf.

    - - - - - + + + + + It is helpful to monitor the log files during testing by using the tail -F log_file_name in a separate terminal console (use ctrl-alt-F1 through F6 or multiple terminals in X). @@ -59,36 +59,36 @@ depending on how or if you specified logging in your smb.

    If you make changes to your smb.conf file while going through these test, remember to restart smbd and nmbd. -

    The Tests

    Procedure 38.1. Diagnosing Your Samba Server

    1. - +

    The Tests

    Procedure 38.1. Diagnosing Your Samba Server

    1. + In the directory in which you store your smb.conf file, run the command testparm smb.conf. If it reports any errors, then your smb.conf configuration file is faulty.

      Note

      - - + + Your smb.conf file may be located in /etc/samba or in /usr/local/samba/lib.

    2. - + Run the command ping BIGSERVER from the PC and ping ACLIENT from the UNIX box. If you do not get a valid response, then your TCP/IP software is not correctly installed.

      You will need to start a “DOS prompt” window on the PC to run ping.

      - - - + + + If you get a message saying “host not found” or a similar message, then your DNS software or /etc/hosts file is not correctly set up. If using DNS, check that the /etc/resolv.conf has correct, current, entries in it. It is possible to run Samba without DNS entries for the server and client, but it is assumed you do have correct entries for the remainder of these tests.

      - - - + + + Another reason why ping might fail is if your host is running firewall software. You will need to relax the rules to let in the workstation in question, perhaps by allowing access from another subnet (on Linux @@ -98,8 +98,8 @@ or iptables). Modern Linux distributions install ipchains/iptables by default. This is a common problem that is often overlooked.

    - - + + If you wish to check what firewall rules may be present in a system under test, simply run iptables -L -v, or if ipchains-based firewall rules are in use, ipchains -L -v. @@ -133,12 +133,12 @@ Chain reject_func (0 references) Run the command smbclient -L BIGSERVER on the UNIX box. You should get back a list of available shares.

    - - - - - - + + + + + + If you get an error message containing the string “bad password”, then you probably have either an incorrect hosts allow, hosts deny, or valid users line in your @@ -146,15 +146,15 @@ you probably have either an incorrect hosts allowhosts allow, hosts deny, valid users, or invalid users lines.

    - + If you get a message connection refused response, then the smbd server may not be running. If you installed it in inetd.conf, then you probably edited that file incorrectly. If you installed it as a daemon, then check that it is running and check that the netbios-ssn port is in a LISTEN state using netstat -a.

    Note

    - - + + Some UNIX/Linux systems use xinetd in place of inetd. Check your system documentation for the location of the control files for your particular system implementation of @@ -171,36 +171,36 @@ files exist. There are a number of reasons for which smbd may refuse or decline a session request. The most common of these involve one or more of the smb.conf file entries as shown in the next example. -

    Example 38.2. Configuration for Allowing Connections Only from a Certain Subnet

    [globals]
    hosts deny = ALL
    hosts allow = xxx.xxx.xxx.xxx/yy
    interfaces = eth0
    bind interfaces only = Yes

    - +

    Example 38.2. Configuration for Allowing Connections Only from a Certain Subnet

    [globals]
    hosts deny = ALL
    hosts allow = xxx.xxx.xxx.xxx/yy
    interfaces = eth0
    bind interfaces only = Yes

    + In Configuration for Allowing Connections Only from a Certain Subnet, no allowance has been made for any session requests that will automatically translate to the loopback adapter address 127.0.0.1. To solve this problem, change these lines as shown in the following example. -

    Example 38.3. Configuration for Allowing Connections from a Certain Subnet and localhost

    [globals]
    hosts deny = ALL
    hosts allow = xxx.xxx.xxx.xxx/yy 127.
    interfaces = eth0 lo

    - - +

    Example 38.3. Configuration for Allowing Connections from a Certain Subnet and localhost

    [globals]
    hosts deny = ALL
    hosts allow = xxx.xxx.xxx.xxx/yy 127.
    interfaces = eth0 lo

    + + Another common cause of these two errors is having something already running on port 139, such as Samba (smbd is running from inetd already) or Digital's Pathworks. Check your inetd.conf file before trying to start smbd as a daemon it can avoid a lot of frustration!

    - - - - - + + + + + And yet another possible cause for failure of this test is when the subnet mask and/or broadcast address settings are incorrect. Please check that the network interface IP address/broadcast address/subnet mask settings are correct and that Samba has correctly noted these in the log.nmbd file.

  • - + Run the command nmblookup -B BIGSERVER __SAMBA__. You should get back the IP address of your Samba server.

    - - - + + + If you do not, then nmbd is incorrectly installed. Check your inetd.conf if you run it from there, or that the daemon is running and listening to UDP port 137.

    @@ -209,7 +209,7 @@ parameters on the command line. If this is the case, then create a one-line script that contains the right parameters and run that from inetd.

  • - + Run the command nmblookup -B ACLIENT `*'.

    You should get the PC's IP address back. If you do not, then the client @@ -228,7 +228,7 @@ not catch all of the responses in the short time it listens. You should see the got a positive name query response messages from several hosts.

    - + If this does not give a result similar to the previous test, then nmblookup isn't correctly getting your broadcast address through its automatic mechanism. In this case you should experiment with the interfaces option in smb.conf to manually configure your IP address, broadcast, and netmask.

    @@ -238,7 +238,7 @@ If your PC and server aren't on the same subnet, then you will need to use the This test will probably fail if your subnet mask and broadcast address are not correct. (Refer to test 3 notes above).

  • - + Run the command smbclient //BIGSERVER/TMP. You should then be prompted for a password. You should use the password of the account with which you are logged into the UNIX box. If you want to test with @@ -266,20 +266,20 @@ If it says “bad password,smbpasswd -a username

    • - - - - + + + + Once connected, you should be able to use the commands dir, get, put, and so on. Type help command for instructions. You should especially check that the amount of free disk space shown is correct when you type dir.

  • - + On the PC, type the command net view \\BIGSERVER. You will need to do this from within a DOS prompt window. You should get back a list of shares available on the server.

    - + If you get a message network name not found or similar error, then NetBIOS name resolution is not working. This is usually caused by a problem in nmbd. To overcome it, you could do one of the following (you only need to choose one of them): diff --git a/docs/htmldocs/Samba3-HOWTO/domain-member.html b/docs/htmldocs/Samba3-HOWTO/domain-member.html index b194e56298..2b70e75319 100644 --- a/docs/htmldocs/Samba3-HOWTO/domain-member.html +++ b/docs/htmldocs/Samba3-HOWTO/domain-member.html @@ -1,14 +1,14 @@ -Chapter 6. Domain Membership

    Chapter 6. Domain Membership
    Prev Part II. Server Configuration Basics Next

    Chapter 6. Domain Membership

    John H. Terpstra

    Samba Team

    Jeremy Allison

    Samba Team

    Gerald (Jerry) Carter

    Samba Team

    Andrew Tridgell

    Samba Team

    Jelmer R. Vernooij

    The Samba Team

    Guenther Deschner

    LDAP updates 
    SuSE

    Table of Contents

    Features and Benefits
    MS Windows Workstation/Server Machine Trust Accounts
    Manual Creation of Machine Trust Accounts
    Managing Domain Machine Accounts using NT4 Server Manager
    On-the-Fly Creation of Machine Trust Accounts
    Making an MS Windows Workstation or Server a Domain Member
    Domain Member Server
    Joining an NT4-type Domain with Samba-3
    Why Is This Better Than security = server?
    Samba ADS Domain Membership
    Configure smb.conf
    Configure /etc/krb5.conf
    Create the Computer Account
    Testing Server Setup
    Testing with smbclient
    Notes
    Sharing User ID Mappings between Samba Domain Members
    Common Errors
    Cannot Add Machine Back to Domain
    Adding Machine to Domain Fails
    I Can't Join a Windows 2003 PDC

    - - - +Chapter 6. Domain Membership

    Chapter 6. Domain Membership
    Prev Part II. Server Configuration Basics Next

    Chapter 6. Domain Membership

    John H. Terpstra

    Samba Team

    Jeremy Allison

    Samba Team

    Gerald (Jerry) Carter

    Samba Team

    Andrew Tridgell

    Samba Team

    Jelmer R. Vernooij

    The Samba Team

    Guenther Deschner

    LDAP updates 
    SuSE

    Table of Contents

    Features and Benefits
    MS Windows Workstation/Server Machine Trust Accounts
    Manual Creation of Machine Trust Accounts
    Managing Domain Machine Accounts using NT4 Server Manager
    On-the-Fly Creation of Machine Trust Accounts
    Making an MS Windows Workstation or Server a Domain Member
    Domain Member Server
    Joining an NT4-type Domain with Samba-3
    Why Is This Better Than security = server?
    Samba ADS Domain Membership
    Configure smb.conf
    Configure /etc/krb5.conf
    Create the Computer Account
    Testing Server Setup
    Testing with smbclient
    Notes
    Sharing User ID Mappings between Samba Domain Members
    Common Errors
    Cannot Add Machine Back to Domain
    Adding Machine to Domain Fails
    I Can't Join a Windows 2003 PDC

    + + + Domain membership is a subject of vital concern. Samba must be able to participate as a member server in a Microsoft domain security context, and Samba must be capable of providing domain machine member trust accounts; otherwise it would not be able to offer a viable option for many users.

    - - + + This chapter covers background information pertaining to domain membership, the Samba configuration for it, and MS Windows client procedures for joining a domain. Why is this necessary? Because both are areas in which there exists @@ -16,10 +16,10 @@ within the current MS Windows networking world, and particularly in the UNIX/Linux networking and administration world, a considerable level of misinformation, incorrect understanding, and lack of knowledge. Hopefully this chapter will fill the voids. -

    Features and Benefits

    - - - +

    Features and Benefits

    + + + MS Windows workstations and servers that want to participate in domain security need to be made domain members. Participating in domain security is often called single sign-on, or SSO for short. This @@ -27,68 +27,68 @@ chapter describes the process that must be followed to make a workstation (or another server be it an MS Windows NT4/200x server) or a Samba server a member of an MS Windows domain security context.

    - - - + + + Samba-3 can join an MS Windows NT4-style domain as a native member server, an MS Windows Active Directory domain as a native member server, or a Samba domain control network. Domain membership has many advantages:

    • - + MS Windows workstation users get the benefit of SSO.

    • - - - + + + Domain user access rights and file ownership/access controls can be set from the single Domain Security Account Manager (SAM) database (works with domain member servers as well as with MS Windows workstations that are domain members).

    • - - + + Only MS Windows NT4/200x/XP Professional workstations that are domain members can use network logon facilities.

    • - - - + + + Domain member workstations can be better controlled through the use of policy files (NTConfig.POL) and desktop profiles.

    • - - - + + + Through the use of logon scripts, users can be given transparent access to network applications that run off application servers.

    • - - - - + + + + Network administrators gain better application and user access management abilities because there is no need to maintain user accounts on any network client or server other than the central domain database (either NT4/Samba SAM-style domain, NT4 domain that is backend-ed with an LDAP directory, or via an Active Directory infrastructure).

    MS Windows Workstation/Server Machine Trust Accounts

    - - - + + + A Machine Trust Account is an account that is used to authenticate a client machine (rather than a user) to the domain controller server. In Windows terminology, this is known as a “computer account.” The purpose of the machine trust account is to prevent a rogue user and domain controller from colluding to gain access to a domain member workstation.

    - - - - + + + + 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, participating in domain security operations, and gaining access to domain user/group @@ -96,10 +96,10 @@ accounts. Windows NT/200x/XP Professional clients use machine trust accounts, bu 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.

    - - - - + + + + A Windows NT4 PDC stores each Machine Trust Account in the Windows Registry. The introduction of MS Windows 2000 saw the introduction of Active Directory, the new repository for Machine Trust Accounts. A Samba PDC, however, stores @@ -107,69 +107,69 @@ each Machine Trust Account in two parts, as follows:

    • - - - + + + A domain security account (stored in the passdb backend) that has been configured in the smb.conf file. The precise nature of the account information that is stored depends on the type of backend database that has been chosen.

      - - - - - + + + + + The older format of this data is the smbpasswd database that contains the UNIX login ID, the UNIX user identifier (UID), and the LanMan and NT-encrypted passwords. There is also some other information in this file that we do not need to concern ourselves with here.

      - - - + + + The two newer database types are called ldapsam and tdbsam. Both store considerably more data than the older smbpasswd file did. The extra information enables new user account controls to be implemented.

    • - - + + A corresponding UNIX account, typically stored in /etc/passwd. Work is in progress to allow a simplified mode of operation that does not require UNIX user accounts, but this has not been a feature of the early releases of Samba-3, and is not currently planned for release either.

    - + There are three ways to create Machine Trust Accounts:

    • - + Manual creation from the UNIX/Linux command line. Here, both the Samba and corresponding UNIX account are created by hand.

    • - - + + Using the MS Windows NT4 Server Manager, either from an NT4 domain member server or using the Nexus toolkit available from the Microsoft Web site. This tool can be run from any MS Windows machine as long as the user is logged on as the administrator account.

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

    - - + + Neither MS Windows NT4/200x/XP Professional, nor Samba, provide any method for enforcing the method of machine trust account creation. This is a matter of the administrator's choice. -

    Manual Creation of Machine Trust Accounts

    - - - - +

    Manual Creation of Machine Trust Accounts

    + + + + The first step in manually creating a Machine Trust Account is to manually create the corresponding UNIX account in /etc/passwd. This can be done using vipw or another “adduser” command @@ -183,25 +183,25 @@ a Linux-based Samba server: root# passwd -l machine_name$

    - - - + + + In the example above there is an existing system group “machines” which is used as the primary group for all machine accounts. In the following examples the “machines” group numeric GID is 100.

    - - + + On *BSD systems, this can be done using the chpass utility: 

     root# chpass -a \
 'machine_name$:*:101:100::0:0:Windows machine_name:/dev/null:/sbin/nologin'

    - - - + + + The /etc/passwd entry will list the machine name with a “$” appended, and will not have a password, will have a null shell and no home directory. For example, a machine named “doppy” would have an @@ -210,9 +210,9 @@ home directory. For example, a machine named “doppymachine_nickname:/dev/null:/bin/false

    - - - + + + in which machine_nickname can be any descriptive name for the client, such as BasementComputer. machine_name absolutely must be the NetBIOS @@ -220,9 +220,9 @@ name of the client to be joined to the domain. The “$< appended to the NetBIOS name of the client or Samba will not recognize this as a Machine Trust Account.

    - - - + + + 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 @@ -232,48 +232,48 @@ as shown here: root# smbpasswd -a -m machine_name

    - - - + + + where machine_name is the machine's NetBIOS name. The RID of the new machine account is generated from the UID of the corresponding UNIX account.

    Join the client to the domain immediately

    - - - - - + + + + + Manually creating a Machine Trust Account using this method is the equivalent of creating a Machine Trust Account on a Windows NT PDC using - + the Server Manager. From the time at which the account is created to the time the client joins the domain and changes the password, your domain is vulnerable to an intruder joining your domain using a machine with the same NetBIOS name. A PDC inherently trusts members of the domain and will serve out a large degree of user information to such clients. You have been warned! -

    Managing Domain Machine Accounts using NT4 Server Manager

    - - - +

    Managing Domain Machine Accounts using NT4 Server Manager

    + + + A working add machine script is essential for machine trust accounts to be automatically created. This applies no matter whether you use automatic account creation or the NT4 Domain Server Manager.

    - - - - + + + + If the machine from which you are trying to manage the domain is an MS Windows NT4 workstation or MS Windows 200x/XP Professional, the tool of choice is the package called SRVTOOLS.EXE. When executed in the target directory it will unpack SrvMgr.exe and UsrMgr.exe (both are domain management tools for MS Windows NT4 workstation).

    - - + + If your workstation is a Microsoft Windows 9x/Me family product, you should download the Nexus.exe package from the Microsoft Web site. When executed from the target directory, it will unpack the same tools but for use on @@ -283,10 +283,10 @@ Further information about these tools may be obtained from Knowledge Base articl 173673, and 172540

    - - + + Launch the srvmgr.exe (Server Manager for Domains) and follow these steps: -

    Procedure 6.1. Server Manager Account Machine Account Management

    1. +

      Procedure 6.1. Server Manager Account Machine Account Management

      1. From the menu select Computer.

      2. Click Select Domain. @@ -303,82 +303,82 @@ Launch the srvmgr.exe (Server Manager for Domains) Add NT Workstation of Server, then enter the machine name in the field provided, and click the Add button. -

    On-the-Fly Creation of Machine Trust Accounts

    - +

    • On-the-Fly Creation of Machine Trust Accounts

    + The third (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.

    - - - + + + 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 add machine script option in smb.conf. This method is not required; however, corresponding UNIX accounts may also be created manually.

    - - + + Here is an example for a Red Hat Linux system: -

    [global]
    add machine script = /usr/sbin/useradd -d /var/lib/nobody -g 100 -s /bin/false -M %u

    -

    Making an MS Windows Workstation or Server a Domain Member

    +

    [global]
    add machine script = /usr/sbin/useradd -d /var/lib/nobody -g 100 -s /bin/false -M %u

    +

    Making an MS Windows Workstation or Server a Domain Member

    The procedure for making an MS Windows workstation or server a member of the domain varies with the version of Windows. -

    Windows 200x/XP Professional Client

    - - - - +

    Windows 200x/XP Professional Client

    + + + + When the user elects to make the client a domain member, Windows 200x prompts for an account and password that has privileges to create machine accounts in the domain. A Samba administrator 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.

    - - + + For security reasons, the password for this administrator account should be set to a password that is other than that used for the root user in /etc/passwd.

    - - - - + + + + The name of the account that is used to create domain member machine trust accounts can be anything the network administrator may choose. If it is other than root, then this is easily mapped to root in the file named in the smb.conf parameter username map = /etc/samba/smbusers.

    - - - + + + The session key of the Samba administrator 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. -

    Windows NT4 Client

    - - - +

    Windows NT4 Client

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

    - - - + + + 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 administrator account when prompted). -

    Samba Client

    - +

    Samba Client

    + Joining a Samba client to a domain is documented in the next section.

    Domain Member Server

    - - - + + + This mode of server operation involves the Samba machine being made a member of a domain security context. This means by definition that all user authentication will be done from a centrally defined authentication regime. @@ -387,106 +387,106 @@ server, or it may be provided from an Active Directory server (ADS) running on MS Windows 2000 or later.

    - - - - + - + + + + Of course it should be clear that the authentication backend itself could be from any distributed directory architecture server that is supported by Samba. This can be LDAP (from OpenLDAP), or Sun's iPlanet, or Novell e-Directory Server, and so on.

    Note

    - - - + + + When Samba is configured to use an LDAP or other identity management and/or directory service, it is Samba that continues to perform user and machine authentication. It should be noted that the LDAP server does not perform authentication handling in place of what Samba is designed to do.

    - - - + + + Please refer to Domain Control, for more information regarding how to create a domain machine account for a domain member server as well as for information on how to enable the Samba domain member machine to join the domain and be fully trusted by it. -

    Joining an NT4-type Domain with Samba-3

    Assumptions lists names that are used in the remainder of this chapter.

    Table 6.1. Assumptions

    Samba DMS NetBIOS name:SERV1
    Windows 200x/NT domain name:MIDEARTH
    Domain's PDC NetBIOS name:DOMPDC
    Domain's BDC NetBIOS names:DOMBDC1 and DOMBDC2

    - +

    Joining an NT4-type Domain with Samba-3

    Assumptions lists names that are used in the remainder of this chapter.

    Table 6.1. Assumptions

    Samba DMS NetBIOS name:SERV1
    Windows 200x/NT domain name:MIDEARTH
    Domain's PDC NetBIOS name:DOMPDC
    Domain's BDC NetBIOS names:DOMBDC1 and DOMBDC2

    + First, you must edit your smb.conf file to tell Samba it should now use domain security.

    - - - + + + Change (or add) your security line in the [global] section of your smb.conf to read: -

    security = domain

    +

    security = domain

    Note that if the parameter security = user is used, this machine would function as a standalone server and not as a domain member server. Domain security mode causes Samba to work within the domain security context.

    Next change the workgroup line in the [global] section to read: -

    workgroup = MIDEARTH

    +

    workgroup = MIDEARTH

    This is the name of the domain we are joining.

    - - + + You must also have the parameter encrypt passwords set to yes in order for your users to authenticate to the NT PDC. This is the default setting if this parameter is not specified. There is no need to specify this parameter, but if it is specified in the smb.conf file, it must be set to Yes.

    - - - - + + + + Finally, add (or modify) a password server line in the [global] section to read: -

    password server = DOMPDC DOMBDC1 DOMBDC2

    +

    password server = DOMPDC DOMBDC1 DOMBDC2

    These are the PDC and BDCs Samba will attempt to contact in order to authenticate users. Samba will try to contact each of these servers in order, so you may want to rearrange this list in order to spread out the authentication load among Domain Controllers.

    - - - + + + Alternatively, if you want smbd to determine automatically the list of domain controllers to use for authentication, you may set this line to be: -

    password server = *

    - +

    password server = *

    + This method allows Samba to use exactly the same mechanism that NT does. The method either uses broadcast-based name resolution, performs a WINS database lookup in order to find a domain controller against which to authenticate, or locates the domain controller using DNS name resolution.

    To join the domain, run this command: - + 

     root# net rpc join -S DOMPDC -UAdministrator%password

    - - - - + + + + If the -S DOMPDC argument is not given, the domain name will be obtained from smb.conf and the NetBIOS name of the PDC will be obtained either using a WINS lookup or via NetBIOS broadcast based name look up.

    - - - + + + The machine is joining the domain DOM, and the PDC for that domain (the only machine that has write access to the domain SAM database) is DOMPDC; therefore, use the -S option. The Administrator%password is the login name and @@ -497,9 +497,9 @@ Where the older NT4-style domain architecture is used: Joined domain DOM.

    - - - + + + Where Active Directory is used, the command used to join the ADS domain is: 

     root#  net ads join -UAdministrator%password
@@ -512,64 +512,64 @@ And the following output is indicative of a successful outcome:
 Refer to the net man page and to the chapter on remote
 administration for further information.
 
    
-
-
-
+
+
+
 This process joins the server to the domain without separately having to create the machine
 trust account on the PDC beforehand.
 
    
-
-
-
-
+
+
+
+
 This command goes through the machine account password change protocol, then writes the new (random) machine
 account password for this Samba server into a file in the same directory in which a smbpasswd file would be
 normally stored. The trust account information that is needed by the DMS is written into the file
 /usr/local/samba/private/secrets.tdb or /etc/samba/secrets.tdb.
 
    
-
-
+
+
 This file is created and owned by root and is not readable by any other user. It is
 the key to the domain-level security for your system and should be treated as carefully 
 as a shadow password file.
 
    
-
-
-
+
+
+
 Finally, restart your Samba daemons and get ready for clients to begin using domain
 security. The way you can restart your Samba daemons depends on your distribution,
 but in most cases the following will suffice:
 
     root# /etc/init.d/samba restart
 
    
-

    Why Is This Better Than security = server?

    - - - +

    Why Is This Better Than security = server?

    + + + Currently, domain security in Samba does not free you from having to create local UNIX users to represent the users attaching to your server. This means that if domain user DOM\fred attaches to your domain security Samba server, there needs to be a local UNIX user fred to represent that user in the UNIX file system. This is similar to the older Samba security mode security = server, where Samba would pass through the authentication request to a Windows NT server in the same way as a Windows 95 or Windows 98 server would.

    - - - + + + Please refer to Winbind: Use of Domain Accounts, for information on a system to automatically assign UNIX UIDs and GIDs to Windows NT domain users and groups.

    - - - + + + The advantage of domain-level security is that the authentication in domain-level security is passed down the authenticated RPC channel in exactly the same way that an NT server would do it. This means Samba servers now participate in domain trust relationships in exactly the same way NT servers do (i.e., you can add Samba servers into a resource domain and have the authentication passed on from a resource domain PDC to an account domain PDC).

    - - - + + + In addition, with security = server, every Samba daemon on a server has to keep a connection open to the authenticating server for as long as that daemon lasts. This can drain the connection resources on a Microsoft NT server and cause it to run out of available connections. With @@ -577,10 +577,10 @@ connection resources on a Microsoft NT server and cause it to run out of availab only for as long as is necessary to authenticate the user and then drop the connection, thus conserving PDC connection resources.

    - - - - + + + + Finally, acting in the same manner as an NT server authenticating to a PDC means that as part of the authentication reply, the Samba server gets the user identification information such as the user SID, the list of NT groups the user belongs to, and so on. @@ -589,58 +589,58 @@ Much of the text of this document was first published in the Web magazine LinuxWorld as the article http://www.linuxworld.com/linuxworld/lw-1998-10/lw-10-samba.html Doing the NIS/NT Samba.

    Samba ADS Domain Membership

    - - - - + + + + This is a rough guide to setting up Samba-3 with Kerberos authentication against a Windows 200x KDC. A familiarity with Kerberos is assumed. -

    Configure smb.conf

    +

    Configure smb.conf

    You must use at least the following three options in smb.conf: -

    realm = your.kerberos.REALM
    security = ADS
    # The following parameter need only be specified if present.
    # The default setting if not present is Yes.
    encrypt passwords = yes

    - - - +

    realm = your.kerberos.REALM
    security = ADS
    # The following parameter need only be specified if present.
    # The default setting if not present is Yes.
    encrypt passwords = yes

    - + + + + In case samba cannot correctly identify the appropriate ADS server using the realm name, use the password server option in smb.conf: -

    password server = your.kerberos.server

    +

    password server = your.kerberos.server

    The most common reason for which Samba may not be able to locate the ADS domain controller is a consequence of sites maintaining some DNS servers on UNIX systems without regard for the DNS requirements of the ADS infrastructure. There is no harm in specifying a preferred ADS domain controller using the password server.

    Note

    - - + + You do not need an smbpasswd file, and older clients will be authenticated as if security = domain, although it will not do any harm and allows you to have local users not in the domain. -

    Configure /etc/krb5.conf

    - - - - +

    Configure /etc/krb5.conf

    + + + + With both MIT and Heimdal Kerberos, it is unnecessary to configure the /etc/krb5.conf, and it may be detrimental.

    - - - - + + + + Microsoft ADS automatically create SRV records in the DNS zone _kerberos._tcp.REALM.NAME for each KDC in the realm. This is part of the installation and configuration process used to create an Active Directory domain. A KDC is a Kerberos Key Distribution Center and forms an integral part of the Microsoft active directory infrastructure.

    - - - - - + + + + + UNIX systems can use kinit and the DES-CBC-MD5 or DES-CBC-CRC encryption types to authenticate to the Windows 2000 KDC. For further information regarding Windows 2000 ADS kerberos interoperability please refer to the Microsoft Windows 2000 Kerberos Interoperability @@ -648,18 +648,18 @@ guide. Another very useful document that may be referred to for general informat interoperability is RFC1510. This RFC explains much of the magic behind the operation of Kerberos.

    - - - + + + MIT's, as well as Heimdal's, recent KRB5 libraries default to checking for SRV records, so they will automatically find the KDCs. In addition, krb5.conf only allows specifying a single KDC, even there if there may be more than one. Using the DNS lookup allows the KRB5 libraries to use whichever KDCs are available.

    - + When manually configuring krb5.conf, the minimal configuration is: 

     [libdefaults]
@@ -674,7 +674,7 @@ When manually configuring krb5.conf, the minimal c
 	.kerberos.server = YOUR.KERBEROS.REALM

    - + When using Heimdal versions before 0.6, use the following configuration settings: 

     [libdefaults]
@@ -691,16 +691,16 @@ When using Heimdal versions before 0.6, use the following configuration settings
         .kerberos.server = YOUR.KERBEROS.REALM

    - - + + Test your config by doing a kinit USERNAME@REALM and making sure that your password is accepted by the Win2000 KDC.

    - - - + + + With Heimdal versions earlier than 0.6.x you can use only newly created accounts in ADS or accounts that have had the password changed once after migration, or in case of Administrator after installation. At the @@ -708,50 +708,50 @@ moment, a Windows 2003 KDC can only be used with Heimdal releases later than 0.6 (and no default etypes in krb5.conf). Unfortunately, this whole area is still in a state of flux.

    Note

    - - - + + + The realm must be in uppercase or you will get a “Cannot find KDC for requested realm while getting initial credentials” error (Kerberos is case-sensitive!).

    Note

    - - - + + + Time between the two servers must be synchronized. You will get a “kinit(v5): Clock skew too great while getting initial credentials” if the time difference (clock skew) is more than five minutes.

    - - + + Clock skew limits are configurable in the Kerberos protocols. The default setting is five minutes.

    - - - - + + + + You also must ensure that you can do a reverse DNS lookup on the IP address of your KDC. Also, the name that this reverse lookup maps to must either be the NetBIOS name of the KDC (i.e., the hostname with no domain attached) or it can be the NetBIOS name followed by the realm.

    - - - + + + The easiest way to ensure you get this right is to add a /etc/hosts entry mapping the IP address of your KDC to its NetBIOS name. If you do not get this correct, then you will get a local error when you try to join the realm.

    - - - + + + If all you want is Kerberos support in smbclient, then you can skip directly to Testing with smbclient now. Create the Computer Account and Testing Server Setup are needed only if you want Kerberos support for smbd and winbindd.

    Create the Computer Account

    - - - + + + As a user who has write permission on the Samba private directory (usually root), run: 

     root#  net ads join -U Administrator%password
@@ -760,12 +760,12 @@ The Administrator account can be any account that has been designated in the ADS
 permission to add machines to the ADS domain. It is, of course, a good idea to use an account other than Administrator.
 On the UNIX/Linux system, this command must be executed by an account that has UID=0 (root).
 
    
-
-
-
-
-
+
+
 
+
+
+
 When making a Windows client a member of an ADS domain within a complex organization, you
 may want to create the machine trust account within a particular organizational unit. Samba-3 permits
 this to be done using the following syntax:
@@ -775,10 +775,10 @@ this to be done using the following syntax:

    Your ADS manager will be able to advise what should be specified for the "organizational_unit" parameter.

    - - - + + + For example, you may want to create the machine trust account in a container called “Servers” under the organizational directory “Computers/BusinessUnit/Department,” like this: 

    @@ -789,90 +789,90 @@ This command will place the Samba server machine trust account in the container
 before executing this command.  Please note that forward slashes must be used, because backslashes are both
 valid characters in an OU name and used as escapes for other characters.  If you need a backslash in an OU 
 name, it may need to be quadrupled to pass through the shell escape and ldap escape.
-
    Possible Errors
    
+
    Possible Errors
    
 
    ADS support not compiled in
    
-	
-	
-	
+	
+	
+	
 	Samba must be reconfigured (remove config.cache) and recompiled (make clean all install) after the
 	Kerberos libraries and headers files are installed.
 	
    net ads join prompts for user name
    
-	
-	
+	
+	
 	You need to log in to the domain using kinit
 	USERNAME@REALM.
 	USERNAME must be a user who has rights to add a machine to the domain.
 	
    Unsupported encryption/or checksum types
    
-	
-	
-	
+	
+	
+	
 	Make sure that the /etc/krb5.conf is correctly configured
 	for the type and version of Kerberos installed on the system.
 	
    
 
    Testing Server Setup
    
-
-
-
+
+
+
 If the join was successful, you will see a new computer account with the
 NetBIOS name of your Samba server in Active Directory (in the “Computers”
 folder under Users and Computers.
 
    
-
-
-
+
+
+
 On a Windows 2000 client, try net use * \\server\share. You should
 be logged in with Kerberos without needing to know a password. If this fails, then run
 klist tickets. Did you get a ticket for the server? Does it have
 an encryption type of DES-CBC-MD5? 
 
    Note
    
-
-
-
+
+
+
 Samba can use both DES-CBC-MD5 encryption as well as ARCFOUR-HMAC-MD5 encoding.
 
    Testing with smbclient
    
-
-
-
+
+
+
 On your Samba server try to log in to a Windows 2000 server or your Samba
 server using smbclient and Kerberos. Use smbclient as usual, but
 specify the -k option to choose Kerberos authentication.
-
    Notes
    
-
-
-
+
    Notes
    
+
+
+
 You must change the administrator password at least once after installing a domain controller, 
 to create the right encryption types.
 
    
-
-
-
+
+
+
 Windows 200x does not seem to create the _kerberos._udp and
 _ldap._tcp in the default DNS setup. Perhaps this will be fixed later in service packs.
-

    Sharing User ID Mappings between Samba Domain Members

    - - - +

    Sharing User ID Mappings between Samba Domain Members

    + + + Samba maps UNIX users and groups (identified by UIDs and GIDs) to Windows users and groups (identified by SIDs). These mappings are done by the idmap subsystem of Samba.

    - - - + + + In some cases it is useful to share these mappings between Samba domain members, so name->id mapping is identical on all machines. This may be needed in particular when sharing files over both CIFS and NFS.

    - - + + To use the LDAP ldap idmap suffix, set: -

    ldap idmap suffix = ou=Idmap

    +

    ldap idmap suffix = ou=Idmap

    See the smb.conf man page entry for the ldap idmap suffix parameter for further information.

    - - - + + + Do not forget to specify also the ldap admin dn and to make certain to set the LDAP administrative password into the secrets.tdb using: 

    @@ -880,9 +880,9 @@ and to make certain to set the LDAP administrative password into the 
    
 In place of ldap-admin-password, substitute the LDAP administration password for your
 system.
-

    Common Errors

    - - +

    Common Errors

    + + In the process of adding/deleting/re-adding domain member machine trust accounts, there are many traps for the unwary player and many “little” things that can go wrong. It is particularly interesting how often subscribers on the Samba mailing list have concluded @@ -890,16 +890,16 @@ after repeated failed attempts to add a machine account that it is necessary to MS Windows on the machine. In truth, it is seldom necessary to reinstall because of this type of problem. The real solution is often quite simple, and with an understanding of how MS Windows networking functions, it is easy to overcome. -

    Cannot Add Machine Back to Domain

    - - +

    Cannot Add Machine Back to Domain

    + + “A Windows workstation was reinstalled. The original domain machine trust account was deleted and added immediately. The workstation will not join the domain if I use the same machine name. Attempts to add the machine fail with a message that the machine already exists on the network I know it does not. Why is this failing?”

    - - + + The original name is still in the NetBIOS name cache and must expire after machine account deletion before adding that same name as a domain member again. The best advice is to delete the old account and then add the machine with a new name. Alternately, the name cache can be flushed and @@ -907,14 +907,14 @@ reloaded with current data using the nbtstat comman 

     C:\>  nbtstat -R

    -

    Adding Machine to Domain Fails

    - - +

    Adding Machine to Domain Fails

    + + “Adding a Windows 200x or XP Professional machine to the Samba PDC Domain fails with a message that says, "The machine could not be added at this time, there is a network problem. Please try again later." Why?”

    - + You should check that there is an add machine script in your smb.conf file. If there is not, please add one that is appropriate for your OS platform. If a script has been defined, you will need to debug its operation. Increase the log level @@ -923,38 +923,38 @@ operation is failing.

    Possible causes include:

    • - - + + The script does not actually exist, or could not be located in the path specified.

      - - + + Corrective action: Fix it. Make sure when run manually that the script will add both the UNIX system account and the Samba SAM account.

    • - - + + The machine could not be added to the UNIX system accounts file /etc/passwd.

      - - + + Corrective action: Check that the machine name is a legal UNIX system account name. If the UNIX utility useradd is called, then make sure that the machine name you are trying to add can be added using this tool. Useradd on some systems will not allow any uppercase characters nor will it allow spaces in the name.

    - - - + + + The add machine script does not create the machine account in the Samba backend database; it is there only to create a UNIX system account to which the Samba backend database account can be mapped. -

    I Can't Join a Windows 2003 PDC

    - - - - +

    I Can't Join a Windows 2003 PDC

    + + + + Windows 2003 requires SMB signing. Client-side SMB signing has been implemented in Samba-3.0. Set client use spnego = yes when communicating with a Windows 2003 server. This will not interfere with other Windows clients that do not diff --git a/docs/htmldocs/Samba3-HOWTO/go01.html b/docs/htmldocs/Samba3-HOWTO/go01.html index 8794c66cc3..8e55187b20 100644 --- a/docs/htmldocs/Samba3-HOWTO/go01.html +++ b/docs/htmldocs/Samba3-HOWTO/go01.html @@ -1,4 +1,4 @@ -Glossary

    Glossary
    Prev   Next

    Glossary

    Access Control List

    +Glossary

    Glossary
    Prev   Next

    Glossary

    Access Control List

    A detailed list of permissions granted to users or groups with respect to file and network resource access. See “File, Directory, and Share Access Controls”, for details.

    Active Directory Service

    diff --git a/docs/htmldocs/Samba3-HOWTO/groupmapping.html b/docs/htmldocs/Samba3-HOWTO/groupmapping.html index 4d87198534..48040782c5 100644 --- a/docs/htmldocs/Samba3-HOWTO/groupmapping.html +++ b/docs/htmldocs/Samba3-HOWTO/groupmapping.html @@ -1,38 +1,38 @@ -Chapter 12. Group Mapping: MS Windows and UNIX

    Chapter 12. Group Mapping: MS Windows and UNIX
    Prev Part III. Advanced Configuration Next

    Chapter 12. Group Mapping: MS Windows and UNIX

    John H. Terpstra

    Samba Team

    Jean François Micouleau

    Gerald (Jerry) Carter

    Samba Team

    Table of Contents

    Features and Benefits
    Discussion
    Warning: User Private Group Problems
    Nested Groups: Adding Windows Domain Groups to Windows Local Groups
    Important Administrative Information
    Default Users, Groups, and Relative Identifiers
    Example Configuration
    Configuration Scripts
    Sample smb.conf Add Group Script
    Script to Configure Group Mapping
    Common Errors
    Adding Groups Fails
    Adding Domain Users to the Workstation Power Users Group

    - - - - - - +Chapter 12. Group Mapping: MS Windows and UNIX

    Chapter 12. Group Mapping: MS Windows and UNIX
    Prev Part III. Advanced Configuration Next

    Chapter 12. Group Mapping: MS Windows and UNIX

    John H. Terpstra

    Samba Team

    Jean François Micouleau

    Gerald (Jerry) Carter

    Samba Team

    Table of Contents

    Features and Benefits
    Discussion
    Warning: User Private Group Problems
    Nested Groups: Adding Windows Domain Groups to Windows Local Groups
    Important Administrative Information
    Default Users, Groups, and Relative Identifiers
    Example Configuration
    Configuration Scripts
    Sample smb.conf Add Group Script
    Script to Configure Group Mapping
    Common Errors
    Adding Groups Fails
    Adding Domain Users to the Workstation Power Users Group

    + + + + + + Starting with Samba-3, new group mapping functionality is available to create associations between Windows group SIDs and UNIX group GIDs. The groupmap subcommand included with the net tool can be used to manage these associations.

    - - + + The new facility for mapping NT groups to UNIX system groups allows the administrator to decide which NT domain groups are to be exposed to MS Windows clients. Only those NT groups that map to a UNIX group that has a value other than the default (-1) will be exposed in group selection lists in tools that access domain users and groups.

    Warning

    - - + + The domain admin group parameter has been removed in Samba-3 and should no longer be specified in smb.conf. In Samba-2.2.x, this parameter was used to give the listed users membership in the Domain Admins Windows group, which gave local admin rights on their workstations (in default configurations). -

    Features and Benefits

    +

    Features and Benefits

    Samba allows the administrator to create MS Windows NT4/200x group accounts and to arbitrarily associate them with UNIX/Linux group accounts.

    - - - - - - - + + + + + + + Group accounts can be managed using the MS Windows NT4 or MS Windows 200x/XP Professional MMC tools. Appropriate interface scripts should be provided in smb.conf if it is desired that UNIX/Linux system accounts should be automatically created when these tools are used. In the absence of these scripts, and @@ -41,19 +41,19 @@ idmap uid/idmap gid parameters in the smb.conf file.

    Figure 12.1. IDMAP: Group SID-to-GID Resolution.

    IDMAP: Group SID-to-GID Resolution.

    Figure 12.2. IDMAP: GID Resolution to Matching SID.

    IDMAP: GID Resolution to Matching SID.

    - - - - + + + + In both cases, when winbindd is not running, only locally resolvable groups can be recognized. Please refer to IDMAP: Group SID-to-GID Resolution and IDMAP: GID Resolution to Matching SID. The net groupmap is used to establish UNIX group to NT SID mappings as shown in IDMAP: storing group mappings.

    Figure 12.3. IDMAP Storing Group Mappings.

    IDMAP Storing Group Mappings.

    - - - - + + + + Administrators should be aware that where smb.conf group interface scripts make direct calls to the UNIX/Linux system tools (the shadow utilities, groupadd, groupdel, and groupmod), the resulting UNIX/Linux group names will be subject @@ -62,48 +62,48 @@ Engineering Managers will attempt to create an identically named UNIX/Linux group, an attempt that will of course fail.

    - - + + There are several possible workarounds for the operating system tools limitation. One method is to use a script that generates a name for the UNIX/Linux system group that fits the operating system limits and that then just passes the UNIX/Linux group ID (GID) back to the calling Samba interface. This will provide a dynamic workaround solution.

    - + Another workaround is to manually create a UNIX/Linux group, then manually create the MS Windows NT4/200x group on the Samba server, and then use the net groupmap tool to connect the two to each other. -

    Discussion

    - - +

    Discussion

    + + When you install MS Windows NT4/200x on a computer, the installation program creates default users and groups, notably the Administrators group, and gives that group privileges necessary to perform essential system tasks, such as the ability to change the date and time or to kill (or close) any process running on the local machine.

    - + The Administrator user is a member of the Administrators group, and thus inherits Administrators group privileges. If a joe user is created to be a member of the Administrators group, joe has exactly the same rights as the user Administrator.

    - - - - + + + + When an MS Windows NT4/200x/XP machine is made a domain member, the “Domain Admins” group of the PDC is added to the local Administrators group of the workstation. Every member of the Domain Admins group inherits the rights of the local Administrators group when logging on the workstation.

    - - + + The following steps describe how to make Samba PDC users members of the Domain Admins group.

    1. Create a UNIX group (usually in /etc/group); let's call it domadm.

    2. - + Add to this group the users that must be “Administrators”. For example, if you want joe, john, and mary to be administrators, your entry in /etc/group will look like this: @@ -117,13 +117,13 @@ root# net groupmap add ntgroup="Domain Admins" unixgroup=domadm rid=512 type=d

      - + The quotes around “Domain Admins” are necessary due to the space in the group name. Also make sure to leave no white space surrounding the equal character (=).

    Now joe, john, and mary are domain administrators.

    - + It is possible to map any arbitrary UNIX group to any Windows NT4/200x group as well as to make any UNIX group a Windows domain group. For example, if you wanted to include a UNIX group (e.g., acct) in an ACL on a local file or printer on a Domain Member machine, @@ -135,54 +135,54 @@ The ntgroup value must be in quotes if it contains space characters to prevent the space from being interpreted as a command delimiter.

    - - + + Be aware that the RID parameter is an unsigned 32-bit integer that should normally start at 1000. However, this RID must not overlap with any RID assigned to a user. Verification for this is done differently depending on the passdb backend you are using. Future versions of the tools may perform the verification automatically, but for now the burden is on you. -

    Warning: User Private Group Problems

    - - - +

    Warning: User Private Group Problems

    + + + Windows does not permit user and group accounts to have the same name. This has serious implications for all sites that use private group accounts. A private group account is an administrative practice whereby users are each given their own group account. Red Hat Linux, as well as several free distributions of Linux, by default create private groups.

    - - + + When mapping a UNIX/Linux group to a Windows group account, all conflict can be avoided by assuring that the Windows domain group name does not overlap with any user account name. -

    Nested Groups: Adding Windows Domain Groups to Windows Local Groups

    - +

    Nested Groups: Adding Windows Domain Groups to Windows Local Groups

    + This functionality is known as nested groups and was first added to Samba-3.0.3.

    - + All MS Windows products since the release of Windows NT 3.10 support the use of nested groups. Many Windows network administrators depend on this capability because it greatly simplifies security administration.

    - - - - - - - + + + + + + + The nested group architecture was designed with the premise that day-to-day user and group membership management should be performed on the domain security database. The application of group security should be implemented on domain member servers using only local groups. On the domain member server, all file system security controls are then limited to use of the local groups, which will contain domain global groups and domain global users.

    - - - + + + You may ask, What are the benefits of this arrangement? The answer is obvious to those who have plumbed the dark depths of Windows networking architecture. Consider for a moment a server on which are stored 200,000 files, each with individual domain user and domain group settings. The company that owns the @@ -190,10 +190,10 @@ it is made a member of a different domain. Who would you think now owns all the files and directories? Answer: Account Unknown.

    - - - - + + + + Unraveling the file ownership mess is an unenviable administrative task that can be avoided simply by using local groups to control all file and directory access control. In this case, only the members of the local groups will have been lost. The files and directories in the storage subsystem will still @@ -201,14 +201,14 @@ to delete the Account Unknown membership entries inside local groups with appropriate entries for domain global groups in the new domain that the server has been made a member of.

    - - + + Another prominent example of the use of nested groups involves implementation of administrative privileges on domain member workstations and servers. Administrative privileges are given to all members of the built-in local group Administrators on each domain member machine. To ensure that all domain @@ -217,10 +217,10 @@ logged into the domain as a member of the Domain Admins group is also granted local administrative privileges on each domain member.

    - - - + + + UNIX/Linux has no concept of support for nested groups, and thus Samba has for a long time not supported them either. The problem is that you would have to enter UNIX groups as auxiliary members of a group in /etc/group. This does not work because it was not a design requirement at the time @@ -228,11 +228,11 @@ /etc/group entries on demand by obtaining user and group information from the domain controller that the Samba server is a member of.

    - - + + In effect, Samba supplements the /etc/group data via the dynamic libnss_winbind mechanism. Beginning with Samba-3.0.3, this facility is used to provide local groups in the same manner as Windows. It works by expanding the local groups on the @@ -242,13 +242,13 @@ group. By definition, it can only contain user objects, which can then be faked to be member of the UNIX/Linux group demo.

    - - + + To enable the use of nested groups, winbindd must be used with NSS winbind. Creation and administration of the local groups is done best via the Windows Domain User Manager or its Samba equivalent, the utility net rpc group. Creating the local group @@ -256,8 +256,8 @@ 

     	root#  net rpc group add demo -L -Uroot%not24get

    - - + + Here the -L switch means that you want to create a local group. It may be necessary to add -S and -U switches for accessing the correct host with appropriate user or root privileges. Adding and removing group members can be done via the addmem and delmem subcommands of @@ -266,10 +266,10 @@ 

     	net rpc group addmem demo "DOM\Domain Users"

    - - + + Having completed these two steps, the execution of getent group demo will show demo members of the global Domain Users group as members of the group demo. This also works with any local or domain user. In case the domain DOM trusts @@ -277,46 +277,46 @@ demo. The users from the foreign domain who are members of the group that has been added to the demo group now have the same local access permissions as local domain users have. -

    Important Administrative Information

    +

    Important Administrative Information

    Administrative rights are necessary in two specific forms:

    1. For Samba-3 domain controllers and domain member servers/clients.

    2. To manage domain member Windows workstations.

    - - + + Versions of Samba up to and including 3.0.10 do not provide a means for assigning rights and privileges that are necessary for system administration tasks from a Windows domain member client machine, so domain administration tasks such as adding, deleting, and changing user and group account information, and managing workstation domain membership accounts, can be handled by any account other than root.

    - - - + + + Samba-3.0.11 introduced a new privilege management interface (see User Rights and Privileges) that permits these tasks to be delegated to non-root (i.e., accounts other than the equivalent of the MS Windows Administrator) accounts.

    - - + + Administrative tasks on a Windows domain member workstation can be done by anyone who is a member of the Domain Admins group. This group can be mapped to any convenient UNIX group. -

    Applicable Only to Versions Earlier than 3.0.11

    - +

    Applicable Only to Versions Earlier than 3.0.11

    + Administrative tasks on UNIX/Linux systems, such as adding users or groups, requires root-level privilege. The addition of a Windows client to a Samba domain involves the addition of a user account for the Windows client.

    - - + + Many UNIX administrators continue to request that the Samba Team make it possible to add Windows workstations, or the ability to add, delete, or modify user accounts, without requiring root privileges. Such a request violates every understanding of basic UNIX system security.

    - - + + There is no safe way to provide access on a UNIX/Linux system without providing root-level privileges. Provision of root privileges can be done either by logging on to the Domain as the user root or by permitting particular users to @@ -324,15 +324,15 @@ can use tools like the NT4 Domain User Manager and the NT4 Domain Server Manager to manage user and group accounts as well as domain member server and client accounts. This level of privilege is also needed to manage share-level ACLs. -

    Default Users, Groups, and Relative Identifiers

    - - - - +

    Default Users, Groups, and Relative Identifiers

    + + - + + + When first installed, Windows NT4/200x/XP are preconfigured with certain user, group, and alias entities. Each has a well-known RID. These must be preserved for continued integrity of operation. Samba must be provisioned with certain essential domain groups that require @@ -340,23 +340,23 @@ domain groups are automatically created. It is the LDAP administrator's responsibility to create (provision) the default NT groups.

    - - + + Each essential domain group must be assigned its respective well-known RID. The default users, groups, aliases, and RIDs are shown in Well-Known User Default RIDs.

    Note

    - - - + + + It is the administrator's responsibility to create the essential domain groups and to assign each its default RID.

    - - + + It is permissible to create any domain group that may be necessary; just make certain that the essential domain groups (well known) have been created and assigned their default RIDs. Other groups you create may be assigned any arbitrary RID you care to use. @@ -365,12 +365,12 @@ will be available for use as an NT domain group.

    Table 12.1. Well-Known User Default RIDs

    Well-Known EntityRIDTypeEssential
    Domain Administrator500UserNo
    Domain Guest501UserNo
    Domain KRBTGT502UserNo
    Domain Admins512GroupYes
    Domain Users513GroupYes
    Domain Guests514GroupYes
    Domain Computers515GroupNo
    Domain Controllers516GroupNo
    Domain Certificate Admins517GroupNo
    Domain Schema Admins518GroupNo
    Domain Enterprise Admins519GroupNo
    Domain Policy Admins520GroupNo
    Builtin Admins544AliasNo
    Builtin users545AliasNo
    Builtin Guests546AliasNo
    Builtin Power Users547AliasNo
    Builtin Account Operators548AliasNo
    Builtin System Operators549AliasNo
    Builtin Print Operators550AliasNo
    Builtin Backup Operators551AliasNo
    Builtin Replicator552AliasNo
    Builtin RAS Servers553AliasNo


    -

    Example Configuration

    - +

    Example Configuration

    + You can list the various groups in the mapping database by executing net groupmap list. Here is an example:

    - + 

     root#  net groupmap list
 Domain Admins (S-1-5-21-2547222302-1596225915-2414751004-512) -> domadmin
@@ -379,15 +379,15 @@ Domain Guests (S-1-5-21-2547222302-1596225915-2414751004-514) -> domguest

    For complete details on net groupmap, refer to the net(8) man page. -

    Configuration Scripts

    +

    Configuration Scripts

    Everyone needs tools. Some of us like to create our own, others prefer to use canned tools (i.e., prepared by someone else for general use). -

    Sample smb.conf Add Group Script

    - - +

    Sample smb.conf Add Group Script

    - - + + + + A script to create complying group names for use by the Samba group interfaces is provided in smbgrpadd.sh. This script adds a temporary entry in the /etc/group file and then renames @@ -415,15 +415,15 @@ exit 0 The smb.conf entry for the above script shown in the configuration of smb.conf for the add group Script demonstrates how it may be used. -

    Example 12.2. Configuration of smb.conf for the add group Script

    [global]
    add group script = /path_to_tool/smbgrpadd.sh "%g"


    -

    Script to Configure Group Mapping

    - +

    Example 12.2. Configuration of smb.conf for the add group Script

    [global]
    add group script = /path_to_tool/smbgrpadd.sh "%g"


    +

    Script to Configure Group Mapping

    + In our example we have created a UNIX/Linux group called ntadmin. Our script will create the additional groups Orks, Elves, and Gnomes. It is a good idea to save this shell script for later use just in case you ever need to rebuild your mapping database. For the sake of convenience we elect to save this script as a file called initGroups.sh. This script is given in intGroups.sh. - +

    Example 12.3. Script to Set Group Mapping

     #!/bin/bash
 
@@ -450,32 +450,32 @@ net groupmap add ntgroup="Gnomes" unixgroup=Gnomes type=d
 	trouble. Commencing with Samba-3.0.23 this annomaly has been fixed - thus all Windows groups
 	must now be manually and explicitly created and mapped to a valid UNIX GID by the Samba 
 	administrator.
-

    Common Errors

    +

    Common Errors

    At this time there are many little surprises for the unwary administrator. In a real sense it is imperative that every step of automated control scripts be carefully tested manually before putting it into active service. -

    Adding Groups Fails

    - +

    Adding Groups Fails

    + This is a common problem when the groupadd is called directly by the Samba interface script for the add group script in the smb.conf file.

    - - + + The most common cause of failure is an attempt to add an MS Windows group account that has an uppercase character and/or a space character in it.

    - + There are three possible workarounds. First, use only group names that comply with the limitations of the UNIX/Linux groupadd system tool. Second, it involves the use of the script mentioned earlier in this chapter, and third is the option is to manually create a UNIX/Linux group account that can substitute for the MS Windows group name, then use the procedure listed above to map that group to the MS Windows group. -

    Adding Domain Users to the Workstation Power Users Group

    “ +

    Adding Domain Users to the Workstation Power Users Group

    “ What must I do to add domain users to the Power Users group? ”

    - + The Power Users group is a group that is local to each Windows 200x/XP Professional workstation. You cannot add the Domain Users group to the Power Users group automatically, it must be done on each workstation by logging in as the local workstation administrator and diff --git a/docs/htmldocs/Samba3-HOWTO/idmapper.html b/docs/htmldocs/Samba3-HOWTO/idmapper.html index a236599c22..67fb9117b8 100644 --- a/docs/htmldocs/Samba3-HOWTO/idmapper.html +++ b/docs/htmldocs/Samba3-HOWTO/idmapper.html @@ -1,11 +1,11 @@ -Chapter 14. Identity Mapping (IDMAP)

    Chapter 14. Identity Mapping (IDMAP)
    Prev Part III. Advanced Configuration Next

    Chapter 14. Identity Mapping (IDMAP)

    John H. Terpstra

    Samba Team

    Table of Contents

    Samba Server Deployment Types and IDMAP
    Standalone Samba Server
    Domain Member Server or Domain Member Client
    Primary Domain Controller
    Backup Domain Controller
    Examples of IDMAP Backend Usage
    Default Winbind TDB
    IDMAP_RID with Winbind
    IDMAP Storage in LDAP Using Winbind
    IDMAP and NSS Using LDAP from ADS with RFC2307bis Schema Extension

    - - - - +Chapter 14. Identity Mapping (IDMAP)

    Chapter 14. Identity Mapping (IDMAP)
    Prev Part III. Advanced Configuration Next

    Chapter 14. Identity Mapping (IDMAP)

    John H. Terpstra

    Samba Team

    Table of Contents

    Samba Server Deployment Types and IDMAP
    Standalone Samba Server
    Domain Member Server or Domain Member Client
    Primary Domain Controller
    Backup Domain Controller
    Examples of IDMAP Backend Usage
    Default Winbind TDB
    IDMAP_RID with Winbind
    IDMAP Storage in LDAP Using Winbind
    IDMAP and NSS Using LDAP from ADS with RFC2307bis Schema Extension

    + + + - - + + + The Microsoft Windows operating system has a number of features that impose specific challenges to interoperability with the operating systems on which Samba is implemented. This chapter deals explicitly with the mechanisms Samba-3 (version 3.0.8 and later) uses to overcome one of the @@ -16,24 +16,24 @@ to UNIX UIDs and GIDs. To ensure sufficient coverage, each possible Samba deployment type is discussed. This is followed by an overview of how the IDMAP facility may be implemented.

    - - - - + + + + The IDMAP facility is of concern where more than one Samba server (or Samba network client) is installed in a domain. Where there is a single Samba server, do not be too concerned regarding the IDMAP infrastructure the default behavior of Samba is nearly always sufficient. Where mulitple Samba servers are used it is often necessary to move data off one server and onto another, and that is where the fun begins!

    - - - - - - - - + + + + + + + + Where user and group account information is stored in an LDAP directory every server can have the same consistent UID and GID for users and groups. This is achieved using NSS and the nss_ldap tool. Samba can be configured to use only local accounts, in which case the scope of the IDMAP problem is somewhat @@ -41,75 +41,75 @@ reduced. This works reasonably well if the servers belong to a single domain, an are not needed. On the other hand, if the Samba servers are NT4 domain members, or ADS domain members, or if there is a need to keep the security name-space separate (i.e., the user DOMINICUS\FJones must not be given access to the account resources of the user -FRANCISCUS\FJones[4] free from inadvertent cross-over, close attention should be given +FRANCISCUS\FJones[4] free from inadvertent cross-over, close attention should be given to the way that the IDMAP facility is configured.

    - - - - - - + + + + + + The use of IDMAP is important where the Samba server will be accessed by workstations or servers from more than one domain, in which case it is important to run winbind so it can handle the resolution (ID mapping) of foreign SIDs to local UNIX UIDs and GIDs.

    - + The use of the IDMAP facility requires the execution of the winbindd upon Samba startup. -

    Samba Server Deployment Types and IDMAP

    - +

    Samba Server Deployment Types and IDMAP

    + There are four basic server deployment types, as documented in the chapter on Server Types and Security Modes. -

    Standalone Samba Server

    - - - +

    Standalone Samba Server

    + + + A standalone Samba server is an implementation that is not a member of a Windows NT4 domain, a Windows 200X Active Directory domain, or a Samba domain.

    - - - + + + By definition, this means that users and groups will be created and controlled locally, and the identity of a network user must match a local UNIX/Linux user login. The IDMAP facility is therefore of little to no interest, winbind will not be necessary, and the IDMAP facility will not be relevant or of interest. -

    Domain Member Server or Domain Member Client

    - - - - - +

    Domain Member Server or Domain Member Client

    + + + + + Samba-3 can act as a Windows NT4 PDC or BDC, thereby providing domain control protocols that are compatible with Windows NT4. Samba-3 file and print sharing protocols are compatible with all versions of MS Windows products. Windows NT4, as with MS Active Directory, extensively makes use of Windows SIDs.

    - - - + + + Samba-3 domain member servers and clients must interact correctly with MS Windows SIDs. Incoming Windows SIDs must be translated to local UNIX UIDs and GIDs. Outgoing information from the Samba server must provide to MS Windows clients and servers appropriate SIDs.

    - - + + A Samba member of a Windows networking domain (NT4-style or ADS) can be configured to handle identity mapping in a variety of ways. The mechanism it uses depends on whether or not the winbindd daemon is used and how the winbind functionality is configured. The configuration options are briefly described here:

    Winbind is not used; users and groups are local:

    - - - - - - - - - - - + + + + + + + + + + + Where winbindd is not used Samba (smbd) uses the underlying UNIX/Linux mechanisms to resolve the identity of incoming network traffic. This is done using the LoginID (account name) in the @@ -119,51 +119,51 @@ on Server Types and Security Modes. we are implying that they are stored only on the local system, in the /etc/passwd and /etc/group respectively.

    - - + + For example, when the user BERYLIUM\WambatW tries to open a connection to a Samba server the incoming SessionSetupAndX request will make a system call to look up the user WambatW in the /etc/passwd file.

    - - - - - - - - + + + + + + + + This configuration may be used with standalone Samba servers, domain member servers (NT4 or ADS), and for a PDC that uses either an smbpasswd or a tdbsam-based Samba passdb backend.

    Winbind is not used; users and groups resolved via NSS:

    - - - - - - + + + + + + In this situation user and group accounts are treated as if they are local accounts. The only way in which this differs from having local accounts is that the accounts are stored in a repository that can be shared. In practice this means that they will reside in either an NIS-type database or else in LDAP.

    - - - - - - - + + + + + + + This configuration may be used with standalone Samba servers, domain member servers (NT4 or ADS), and for a PDC that uses either an smbpasswd or a tdbsam-based Samba passdb backend.

    Winbind/NSS with the default local IDMAP table:

    - - - - + + + + There are many sites that require only a simple Samba server or a single Samba server that is a member of a Windows NT4 domain or an ADS domain. A typical example is an appliance like file server on which no local accounts are configured and @@ -171,21 +171,21 @@ on Server Types and Security Modes. domain. The domain control can be provided by Samba-3, MS Windows NT4, or MS Windows Active Directory.

    - - - - - + + + + + Winbind is a great convenience in this situation. All that is needed is a range of UID numbers and GID numbers that can be defined in the smb.conf file. The /etc/nsswitch.conf file is configured to use winbind, which does all the difficult work of mapping incoming SIDs to appropriate UIDs and GIDs. The SIDs are allocated a UID/GID in the order in which winbind receives them.

    - - - - + + + + This configuration is not convenient or practical in sites that have more than one Samba server and that require the same UID or GID for the same user or group across all servers. One of the hazards of this method is that in the event that the winbind @@ -194,10 +194,10 @@ on Server Types and Security Modes. result that MS Windows files that are stored on the Samba server may now not belong to the rightful owners.

    Winbind/NSS uses RID based IDMAP:

    - - - - + + + + The IDMAP_RID facility is new to Samba version 3.0.8. It was added to make life easier for a number of sites that are committed to use of MS ADS, that do not apply an ADS schema extension, and that do not have an installed an LDAP directory server just for @@ -205,14 +205,14 @@ on Server Types and Security Modes. domains, and not multiple domain trees) and you want a simple cookie-cutter solution to the IDMAP table problem, then IDMAP_RID is an obvious choice.

    - - - - - - - - + + + + + + + + This facility requires the allocation of the idmap uid and the idmap gid ranges, and within the idmap uid it is possible to allocate a subset of this range for automatic mapping of the relative @@ -222,23 +222,23 @@ on Server Types and Security Modes. a SID is encountered that has the value S-1-5-21-34567898-12529001-32973135-1234, the resulting UID will be 1000 + 1234 = 2234.

    Winbind with an NSS/LDAP backend-based IDMAP facility:

    - - - - - - - - + + + + + + + + In this configuration winbind resolved SIDs to UIDs and GIDs from the idmap uid and idmap gid ranges specified in the smb.conf file, but instead of using a local winbind IDMAP table, it is stored in an LDAP directory so that all domain member machines (clients and servers) can share a common IDMAP table.

    - - - + + + It is important that all LDAP IDMAP clients use only the master LDAP server because the idmap backend facility in the smb.conf file does not correctly handle LDAP redirects. @@ -247,17 +247,17 @@ on Server Types and Security Modes. domain member servers. It is a neat method for assuring that UIDs, GIDs, and the matching SIDs are consistent across all servers.

    - - + + The use of the LDAP-based passdb backend requires use of the PADL nss_ldap utility or an equivalent. In this situation winbind is used to handle foreign SIDs, that is, SIDs from standalone Windows clients (i.e., not a member of our domain) as well as SIDs from another domain. The foreign UID/GID is mapped from allocated ranges (idmap uid and idmap gid) in precisely the same manner as when using winbind with a local IDMAP table.

    - - - + + + The nss_ldap tool set can be used to access UIDs and GIDs via LDAP as well as via Active Directory. In order to use Active Directory, it is necessary to modify the ADS schema by installing either the AD4UNIX schema extension or using the Microsoft Services for UNIX @@ -266,11 +266,11 @@ on Server Types and Security Modes. installed to permit the UNIX credentials to be set and managed from the ADS User and Computer Management tool. Each account must be separately UNIX-enabled before the UID and GID data can be used by Samba. -

    Primary Domain Controller

    - - - - +

    Primary Domain Controller

    + + + + Microsoft Windows domain security systems generate the user and group SID as part of the process of creation of an account. Windows does not have a concept of the UNIX UID or a GID; rather, it has its own type of security descriptor. When Samba is used as a domain controller, it provides a method @@ -278,50 +278,50 @@ on Server Types and Security Modes. adds an RID that is calculated algorithmically from a base value that can be specified in the smb.conf file, plus twice (2x) the UID or GID. This method is called “algorithmic mapping”.

    - + For example, if a user has a UID of 4321, and the algorithmic RID base has a value of 1000, the RID will be 1000 + (2 x 4321) = 9642. Thus, if the domain SID is S-1-5-21-89238497-92787123-12341112, the resulting SID is S-1-5-21-89238497-92787123-12341112-9642.

    - - - - + + + + The foregoing type of SID is produced by Samba as an automatic function and is either produced on the fly (as is the case when using a passdb backend = [tdbsam | smbpasswd]), or may be stored as a permanent part of an account in an LDAP-based ldapsam.

    - - - - - - - - - + + + + + + + + + ADS uses a directory schema that can be extended to accommodate additional account attributes such as UIDs and GIDs. The installation of Microsoft Service for UNIX 3.5 will expand the normal ADS schema to include UNIX account attributes. These must of course be managed separately through a snap-in module to the normal ADS account management MMC interface.

    - - - - + + + + Security identifiers used within a domain must be managed to avoid conflict and to preserve itegrity. In an NT4 domain context, the PDC manages the distribution of all security credentials to the backup domain controllers (BDCs). At this time the only passdb backend for a Samba domain controller that is suitable for such information is an LDAP backend. -

    Backup Domain Controller

    - - - - - - - +

    Backup Domain Controller

    + + + + + + + BDCs have read-only access to security credentials that are stored in LDAP. Changes in user or group account information are passed by the BDC to the PDC. Only the PDC can write changes to the directory. @@ -330,27 +330,27 @@ on Server Types and Security Modes. have access to the master (writable) LDAP server. Samba-3 at this time does not handle LDAP redirects in the IDMAP backend. This means that it is is unsafe to use a slave (replicate) LDAP server with the IDMAP facility. -

    Examples of IDMAP Backend Usage

    - +

    Examples of IDMAP Backend Usage

    - - + + + Anyone who wishes to use winbind will find the following example configurations helpful. Remember that in the majority of cases winbind is of primary interest for use with domain member servers (DMSs) and domain member clients (DMCs). -

    Default Winbind TDB

    +

    Default Winbind TDB

    Two common configurations are used:

    • Networks that have an NT4 PDC (with or without BDCs) or a Samba PDC (with or without BDCs).

    • Networks that use MS Windows 200x ADS. -

    NT4-Style Domains (Includes Samba Domains)

    +

    NT4-Style Domains (Includes Samba Domains)

    NT4 Domain Member Server smb.con is a simple example of an NT4 DMS smb.conf file that shows only the global section. -

    Example 14.1. NT4 Domain Member Server smb.conf

    # Global parameters
    [global]
    workgroup = MEGANET2
    security = DOMAIN
    idmap uid = 10000-20000
    idmap gid = 10000-20000
    template primary group = "Domain Users"
    template shell = /bin/bash

    - - +

    Example 14.1. NT4 Domain Member Server smb.conf

    # Global parameters
    [global]
    workgroup = MEGANET2
    security = DOMAIN
    idmap uid = 10000-20000
    idmap gid = 10000-20000
    template primary group = "Domain Users"
    template shell = /bin/bash

    + + The use of winbind requires configuration of NSS. Edit the /etc/nsswitch.conf so it includes the following entries: 

    @@ -373,37 +373,37 @@ hosts:  files [dns] wins
 root#  net rpc join -UAdministrator%password
 Joined domain MEGANET2.

    - + The success of the join can be confirmed with the following command: 

     root#  net rpc testjoin
 Join to 'MIDEARTH' is OK

    A failed join would report an error message like the following: - + 

     root#  net rpc testjoin
 [2004/11/05 16:34:12, 0] utils/net_rpc_join.c:net_rpc_join_ok(66)
 Join to domain 'MEGANET2' is not valid

  • - - - + + + Start the nmbd, winbind, and smbd daemons in the order shown. -

    • ADS Domains

    - - +

    ADS Domains

    + + The procedure for joining an ADS domain is similar to the NT4 domain join, except the smb.conf file will have the contents shown in ADS Domain Member Server smb.conf -

    Example 14.2. ADS Domain Member Server smb.conf

    # Global parameters
    [global]
    workgroup = BUTTERNET
    netbios name = GARGOYLE
    realm = BUTTERNET.BIZ
    security = ADS
    template shell = /bin/bash
    idmap uid = 500-10000000
    idmap gid = 500-10000000
    winbind use default domain = Yes
    winbind nested groups = Yes
    printer admin = "BUTTERNET\Domain Admins"

    - - - - - - - +

    Example 14.2. ADS Domain Member Server smb.conf

    # Global parameters
    [global]
    workgroup = BUTTERNET
    netbios name = GARGOYLE
    realm = BUTTERNET.BIZ
    security = ADS
    template shell = /bin/bash
    idmap uid = 500-10000000
    idmap gid = 500-10000000
    winbind use default domain = Yes
    winbind nested groups = Yes
    printer admin = "BUTTERNET\Domain Admins"

    + + + + + + + ADS DMS operation requires use of kerberos (KRB). For this to work, the krb5.conf must be configured. The exact requirements depends on which version of MIT or Heimdal Kerberos is being used. It is sound advice to use only the latest version, which at this time are MIT Kerberos version @@ -416,7 +416,7 @@ Join to domain 'MEGANET2' is not valid Edit the /etc/nsswitch.conf file as shown above.

  • Execute: - + 

     root#  net ads join -UAdministrator%password
 Joined domain BUTTERNET.
@@ -436,30 +436,30 @@ GARGOYLE$@'s password:
   ads_connect: No results returned
 Join to domain is not valid

    - - - - + + + + The specific error message may differ from the above because it depends on the type of failure that may have occurred. Increase the log level to 10, repeat the test, and then examine the log files produced to identify the nature of the failure.

  • Start the nmbd, winbind, and smbd daemons in the order shown. -

    • IDMAP_RID with Winbind

    - - - - +

    IDMAP_RID with Winbind

    + + + + The idmap_rid facility is a new tool that, unlike native winbind, creates a predictable mapping of MS Windows SIDs to UNIX UIDs and GIDs. The key benefit of this method of implementing the Samba IDMAP facility is that it eliminates the need to store the IDMAP data in a central place. The downside is that it can be used only within a single ADS domain and is not compatible with trusted domain implementations.

    - - - - + + + + This alternate method of SID to UID/GID mapping can be achieved using the idmap_rid plug-in. This plug-in uses the RID of the user SID to derive the UID and GID by adding the RID to a base value specified. This utility requires that the parameter @@ -467,19 +467,19 @@ Join to domain is not valid with multiple domain environments. The idmap uid and idmap gid ranges must be specified.

    - - + + The idmap_rid facility can be used both for NT4/Samba-style domains and Active Directory. To use this with an NT4 domain, do not include the realm parameter; additionally, the method used to join the domain uses the net rpc join process.

    An example smb.conf file for and ADS domain environment is shown in ADS Domain Member smb.conf using idmap_rid. -

    Example 14.3. ADS Domain Member smb.conf using idmap_rid

    # Global parameters
    [global]
    workgroup = KPAK
    netbios name = BIGJOE
    realm = CORP.KPAK.COM
    server string = Office Server
    security = ADS
    allow trusted domains = No
    idmap backend = idmap_rid:KPAK=500-100000000
    idmap uid = 500-100000000
    idmap gid = 500-100000000
    template shell = /bin/bash
    winbind use default domain = Yes
    winbind enum users = No
    winbind enum groups = No
    winbind nested groups = Yes
    printer admin = "Domain Admins"

    - - - - +

    Example 14.3. ADS Domain Member smb.conf using idmap_rid

    # Global parameters
    [global]
    workgroup = KPAK
    netbios name = BIGJOE
    realm = CORP.KPAK.COM
    server string = Office Server
    security = ADS
    allow trusted domains = No
    idmap backend = idmap_rid:KPAK=500-100000000
    idmap uid = 500-100000000
    idmap gid = 500-100000000
    template shell = /bin/bash
    winbind use default domain = Yes
    winbind enum users = No
    winbind enum groups = No
    winbind nested groups = Yes
    printer admin = "Domain Admins"

    + + + + In a large domain with many users it is imperative to disable enumeration of users and groups. For example, at a site that has 22,000 users in Active Directory the winbind-based user and group resolution is unavailable for nearly 12 minutes following first startup of @@ -488,8 +488,8 @@ Join to domain is not valid or groups using the getent passwd and getent group commands. It will be possible to perform the lookup for individual users, as shown in the following procedure.

    - - + + The use of this tool requires configuration of NSS as per the native use of winbind. Edit the /etc/nsswitch.conf so it has the following parameters: 

    @@ -515,7 +515,7 @@ Using short domain name -- KPAK
 Joined 'BIGJOE' to realm 'CORP.KPAK.COM'

    - + An invalid or failed join can be detected by executing: 

     root#  net ads testjoin
@@ -531,14 +531,14 @@ Join to domain is not valid
 		Start the nmbd, winbind, and smbd daemons in the order shown.
 		
  • 
 		Validate the operation of this configuration by executing:
-		
+		
 
     root#  getent passwd administrator
 administrator:x:1000:1013:Administrator:/home/BE/administrator:/bin/bash
 
    
-

    • IDMAP Storage in LDAP Using Winbind

    - - +

    IDMAP Storage in LDAP Using Winbind

    + + The storage of IDMAP information in LDAP can be used with both NT4/Samba-3-style domains and ADS domains. OpenLDAP is a commonly used LDAP server for this purpose, although any standards-complying LDAP server can be used. It is therefore possible to deploy this IDMAP @@ -547,15 +547,15 @@ administrator:x:1000:1013:Administrator:/home/BE/administrator:/bin/bash

    An example is for an ADS domain is shown in ADS Domain Member Server using LDAP. -

    Example 14.4. ADS Domain Member Server using LDAP

    # Global parameters
    [global]
    workgroup = SNOWSHOW
    netbios name = GOODELF
    realm = SNOWSHOW.COM
    server string = Samba Server
    security = ADS
    log level = 1 ads:10 auth:10 sam:10 rpc:10
    ldap admin dn = cn=Manager,dc=SNOWSHOW,dc=COM
    ldap idmap suffix = ou=Idmap
    ldap suffix = dc=SNOWSHOW,dc=COM
    idmap backend = ldap:ldap://ldap.snowshow.com
    idmap uid = 150000-550000
    idmap gid = 150000-550000
    template shell = /bin/bash
    winbind use default domain = Yes

    - +

    Example 14.4. ADS Domain Member Server using LDAP

    # Global parameters
    [global]
    workgroup = SNOWSHOW
    netbios name = GOODELF
    realm = SNOWSHOW.COM
    server string = Samba Server
    security = ADS
    log level = 1 ads:10 auth:10 sam:10 rpc:10
    ldap admin dn = cn=Manager,dc=SNOWSHOW,dc=COM
    ldap idmap suffix = ou=Idmap
    ldap suffix = dc=SNOWSHOW,dc=COM
    idmap backend = ldap:ldap://ldap.snowshow.com
    idmap uid = 150000-550000
    idmap gid = 150000-550000
    template shell = /bin/bash
    winbind use default domain = Yes

    + In the case of an NT4 or Samba-3-style domain the realm is not used, and the command used to join the domain is net rpc join. The above example also demonstrates advanced error-reporting techniques that are documented in Reporting Bugs.

    - - - + + + Where MIT kerberos is installed (version 1.3.4 or later), edit the /etc/krb5.conf file so it has the following contents: 

    @@ -610,8 +610,8 @@ hosts:  files wins
 ...

    - - + + You will need the PADL nss_ldap tool set for this solution. Configure the /etc/ldap.conf file so it has the information needed. The following is an example of a working file: @@ -674,21 +674,21 @@ Joined 'GOODELF' to realm 'SNOWSHOW.COM'

  • Start the nmbd, winbind, and smbd daemons in the order shown.

    • - + Follow the diagnositic procedures shown earlier in this chapter to identify success or failure of the join. In many cases a failure is indicated by a silent return to the command prompt with no indication of the reason for failure. -

    IDMAP and NSS Using LDAP from ADS with RFC2307bis Schema Extension

    - - +

    IDMAP and NSS Using LDAP from ADS with RFC2307bis Schema Extension

    + + The use of this method is messy. The information provided in the following is for guidance only and is very definitely not complete. This method does work; it is used in a number of large sites and has an acceptable level of performance.

    An example smb.conf file is shown in ADS Domain Member Server using RFC2307bis Schema Extension Date via NSS. -

    Example 14.5. ADS Domain Member Server using RFC2307bis Schema Extension Date via NSS

    # Global parameters
    [global]
    workgroup = BOBBY
    realm = BOBBY.COM
    security = ADS
    idmap uid = 150000-550000
    idmap gid = 150000-550000
    template shell = /bin/bash
    winbind cache time = 5
    winbind use default domain = Yes
    winbind trusted domains only = Yes
    winbind nested groups = Yes

    - +

    Example 14.5. ADS Domain Member Server using RFC2307bis Schema Extension Date via NSS

    # Global parameters
    [global]
    workgroup = BOBBY
    realm = BOBBY.COM
    security = ADS
    idmap uid = 150000-550000
    idmap gid = 150000-550000
    template shell = /bin/bash
    winbind cache time = 5
    winbind use default domain = Yes
    winbind trusted domains only = Yes
    winbind nested groups = Yes

    + The DMS must be joined to the domain using the usual procedure. Additionally, it is necessary to build and install the PADL nss_ldap tool set. Be sure to build this tool set with the following: @@ -697,7 +697,7 @@ RFC2307bis Schema Extension Date via NSS. make install

    - + The following /etc/nsswitch.conf file contents are required: 

     ...
@@ -709,21 +709,21 @@ hosts:  files wins
 ...

    - - + + The /etc/ldap.conf file must be configured also. Refer to the PADL documentation and source code for nss_ldap to specific instructions.

    The next step involves preparation of the ADS schema. This is briefly discussed in the remaining part of this chapter. -

    IDMAP, Active Directory, and MS Services for UNIX 3.5

    - +

    IDMAP, Active Directory, and MS Services for UNIX 3.5

    + The Microsoft Windows Service for UNIX (SFU) version 3.5 is available for free download from the Microsoft Web site. You will need to download this tool and install it following Microsoft instructions. -

    IDMAP, Active Directory and AD4UNIX

    +

    IDMAP, Active Directory and AD4UNIX

    Instructions for obtaining and installing the AD4UNIX tool set can be found from the Geekcomix Web site. -


    [4] DOMINICUS\FJonesFRANCISCUS\FJonesFJones
    Prev Up Next
    Chapter 13. Remote and Local Management: The Net Command Home Chapter 15. User Rights and Privileges
    +


    [4] DOMINICUS\FJonesFRANCISCUS\FJonesFJones
    Prev Up Next
    Chapter 13. Remote and Local Management: The Net Command Home Chapter 15. User Rights and Privileges
    diff --git a/docs/htmldocs/Samba3-HOWTO/index.html b/docs/htmldocs/Samba3-HOWTO/index.html index bb8e3d57df..5c88173ef2 100644 --- a/docs/htmldocs/Samba3-HOWTO/index.html +++ b/docs/htmldocs/Samba3-HOWTO/index.html @@ -1,50 +1,50 @@ -The Official Samba 3.2.x HOWTO and Reference Guide
    The Official Samba 3.2.x HOWTO and Reference Guide
       Next

    The Official Samba 3.2.x HOWTO and Reference Guide

    Edited by

    Jelmer R. Vernooij

    The Samba Team

    Edited by

    John H. Terpstra

    Samba Team

    Edited by

    Gerald (Jerry) Carter

    Samba Team

    Table of Contents

    About the Cover Artwork
    Attribution
    Foreword
    Preface
    Conventions Used
    Introduction
    What Is Samba?
    Why This Book?
    Book Structure and Layout
    I. General Installation
    1. How to Install and Test SAMBA
    Obtaining and Installing Samba
    Configuring Samba (smb.conf)
    Configuration File Syntax
    TDB Database File Information
    Starting Samba
    Example Configuration
    SWAT
    List Shares Available on the Server
    Connect with a UNIX Client
    Connect from a Remote SMB Client
    What If Things Don't Work?
    Still Stuck?
    Common Errors
    Large Number of smbd Processes
    Error Message: open_oplock_ipc
    “The network name cannot be found”
    2. Fast Start: Cure for Impatience
    Features and Benefits
    Description of Example Sites
    Worked Examples
    Standalone Server
    Domain Member Server
    Domain Controller
    II. Server Configuration Basics
    3. Server Types and Security Modes
    Features and Benefits
    Server Types
    Samba Security Modes
    User Level Security
    Share-Level Security
    Domain Security Mode (User-Level Security)
    ADS Security Mode (User-Level Security)
    Server Security (User Level Security)
    Password Checking
    Common Errors
    What Makes Samba a Server?
    What Makes Samba a Domain Controller?
    What Makes Samba a Domain Member?
    Constantly Losing Connections to Password Server
    Stand-alone Server is converted to Domain Controller Now User accounts don't work
    4. Domain Control
    Features and Benefits
    Single Sign-On and Domain Security
    Basics of Domain Control
    Domain Controller Types
    Preparing for Domain Control
    Domain Control: Example Configuration
    Samba ADS Domain Control
    Domain and Network Logon Configuration
    Domain Network Logon Service
    Security Mode and Master Browsers
    Common Errors
    “$” Cannot Be Included in Machine Name
    Joining Domain Fails Because of Existing Machine Account
    The System Cannot Log You On (C000019B)
    The Machine Trust Account Is Not Accessible
    Account Disabled
    Domain Controller Unavailable
    Cannot Log onto Domain Member Workstation After Joining Domain
    5. Backup Domain Control
    Features and Benefits
    Essential Background Information
    MS Windows NT4-style Domain Control
    LDAP Configuration Notes
    Active Directory Domain Control
    What Qualifies a Domain Controller on the Network?
    How Does a Workstation find its Domain Controller?
    Backup Domain Controller Configuration
    Example Configuration
    Common Errors
    Machine Accounts Keep Expiring
    Can Samba Be a Backup Domain Controller to an NT4 PDC?
    How Do I Replicate the smbpasswd File?
    Can I Do This All with LDAP?
    6. Domain Membership
    Features and Benefits
    MS Windows Workstation/Server Machine Trust Accounts
    Manual Creation of Machine Trust Accounts
    Managing Domain Machine Accounts using NT4 Server Manager
    On-the-Fly Creation of Machine Trust Accounts
    Making an MS Windows Workstation or Server a Domain Member
    Domain Member Server
    Joining an NT4-type Domain with Samba-3
    Why Is This Better Than security = server?
    Samba ADS Domain Membership
    Configure smb.conf
    Configure /etc/krb5.conf
    Create the Computer Account
    Testing Server Setup
    Testing with smbclient
    Notes
    Sharing User ID Mappings between Samba Domain Members
    Common Errors
    Cannot Add Machine Back to Domain
    Adding Machine to Domain Fails
    I Can't Join a Windows 2003 PDC
    7. Standalone Servers
    Features and Benefits
    Background
    Example Configuration
    Reference Documentation Server
    Central Print Serving
    Common Errors
    8. MS Windows Network Configuration Guide
    Features and Benefits
    Technical Details
    TCP/IP Configuration
    Joining a Domain: Windows 2000/XP Professional
    Domain Logon Configuration: Windows 9x/Me
    Common Errors
    III. Advanced Configuration
    9. Important and Critical Change Notes for the Samba 3.x Series
    Important Samba-3.2.x Change Notes
    Important Samba-3.0.x Change Notes
    User and Group Changes
    Essential Group Mappings
    Passdb Changes
    Group Mapping Changes in Samba-3.0.23
    LDAP Changes in Samba-3.0.23
    10. Network Browsing
    Features and Benefits
    What Is Browsing?
    Discussion
    NetBIOS over TCP/IP
    TCP/IP without NetBIOS
    DNS and Active Directory
    How Browsing Functions
    Configuring Workgroup Browsing
    Domain Browsing Configuration
    Forcing Samba to Be the Master
    Making Samba the Domain Master
    Note about Broadcast Addresses
    Multiple Interfaces
    Use of the Remote Announce Parameter
    Use of the Remote Browse Sync Parameter
    WINS: The Windows Internetworking Name Server
    WINS Server Configuration
    WINS Replication
    Static WINS Entries
    Helpful Hints
    Windows Networking Protocols
    Name Resolution Order
    Technical Overview of Browsing
    Browsing Support in Samba
    Problem Resolution
    Cross-Subnet Browsing
    Common Errors
    Flushing the Samba NetBIOS Name Cache
    Server Resources Cannot Be Listed
    I Get an "Unable to browse the network" Error
    Browsing of Shares and Directories is Very Slow
    Invalid Cached Share References Affects Network Browsing
    11. Account Information Databases
    Features and Benefits
    Backward Compatibility Account Storage Systems
    New Account Storage Systems
    Technical Information
    Important Notes About Security
    Mapping User Identifiers between MS Windows and UNIX
    Mapping Common UIDs/GIDs on Distributed Machines
    Comments Regarding LDAP
    LDAP Directories and Windows Computer Accounts
    Account Management Tools
    The smbpasswd Tool
    The pdbedit Tool
    Password Backends
    Plaintext
    smbpasswd: Encrypted Password Database
    tdbsam
    ldapsam
    Common Errors
    Users Cannot Logon
    Configuration of auth methods
    12. Group Mapping: MS Windows and UNIX
    Features and Benefits
    Discussion
    Warning: User Private Group Problems
    Nested Groups: Adding Windows Domain Groups to Windows Local Groups
    Important Administrative Information
    Default Users, Groups, and Relative Identifiers
    Example Configuration
    Configuration Scripts
    Sample smb.conf Add Group Script
    Script to Configure Group Mapping
    Common Errors
    Adding Groups Fails
    Adding Domain Users to the Workstation Power Users Group
    13. Remote and Local Management: The Net Command
    Overview
    Administrative Tasks and Methods
    UNIX and Windows Group Management
    Adding, Renaming, or Deletion of Group Accounts
    Manipulating Group Memberships
    Nested Group Support
    UNIX and Windows User Management
    Adding User Accounts
    Deletion of User Accounts
    Managing User Accounts
    User Mapping
    Administering User Rights and Privileges
    Managing Trust Relationships
    Machine Trust Accounts
    Interdomain Trusts
    Managing Security Identifiers (SIDS)
    Share Management
    Creating, Editing, and Removing Shares
    Creating and Changing Share ACLs
    Share, Directory, and File Migration
    Printer Migration
    Controlling Open Files
    Session and Connection Management
    Printers and ADS
    Manipulating the Samba Cache
    Managing IDMAP UID/SID Mappings
    Creating an IDMAP Database Dump File
    Restoring the IDMAP Database Dump File
    Other Miscellaneous Operations
    14. Identity Mapping (IDMAP)
    Samba Server Deployment Types and IDMAP
    Standalone Samba Server
    Domain Member Server or Domain Member Client
    Primary Domain Controller
    Backup Domain Controller
    Examples of IDMAP Backend Usage
    Default Winbind TDB
    IDMAP_RID with Winbind
    IDMAP Storage in LDAP Using Winbind
    IDMAP and NSS Using LDAP from ADS with RFC2307bis Schema Extension
    15. User Rights and Privileges
    Rights Management Capabilities
    Using the “net rpc rights” Utility
    Description of Privileges
    Privileges Suppored by Windows 2000 Domain Controllers
    The Administrator Domain SID
    Common Errors
    What Rights and Privileges Will Permit Windows Client Administration?
    16. File, Directory, and Share Access Controls
    Features and Benefits
    File System Access Controls
    MS Windows NTFS Comparison with UNIX File Systems
    Managing Directories
    File and Directory Access Control
    Share Definition Access Controls
    User- and Group-Based Controls
    File and Directory Permissions-Based Controls
    Miscellaneous Controls
    Access Controls on Shares
    Share Permissions Management
    MS Windows Access Control Lists and UNIX Interoperability
    Managing UNIX Permissions Using NT Security Dialogs
    Viewing File Security on a Samba Share
    Viewing File Ownership
    Viewing File or Directory Permissions
    Modifying File or Directory Permissions
    Interaction with the Standard Samba “create mask” Parameters
    Interaction with the Standard Samba File Attribute Mapping
    Windows NT/200X ACLs and POSIX ACLs Limitations
    Common Errors
    Users Cannot Write to a Public Share
    File Operations Done as root with force user Set
    MS Word with Samba Changes Owner of File
    17. File and Record Locking
    Features and Benefits
    Discussion
    Opportunistic Locking Overview
    Samba Oplocks Control
    Example Configuration
    MS Windows Oplocks and Caching Controls
    Workstation Service Entries
    Server Service Entries
    Persistent Data Corruption
    Common Errors
    locking.tdb Error Messages
    Problems Saving Files in MS Office on Windows XP
    Long Delays Deleting Files over Network with XP SP1
    Additional Reading
    18. Securing Samba
    Introduction
    Features and Benefits
    Technical Discussion of Protective Measures and Issues
    Using Host-Based Protection
    User-Based Protection
    Using Interface Protection
    Using a Firewall
    Using IPC$ Share-Based Denials
    NTLMv2 Security
    Upgrading Samba
    Common Errors
    Smbclient Works on Localhost, but the Network Is Dead
    Why Can Users Access Other Users' Home Directories?
    19. Interdomain Trust Relationships
    Features and Benefits
    Trust Relationship Background
    Native MS Windows NT4 Trusts Configuration
    Creating an NT4 Domain Trust
    Completing an NT4 Domain Trust
    Interdomain Trust Facilities
    Configuring Samba NT-Style Domain Trusts
    Samba as the Trusted Domain
    Samba as the Trusting Domain
    NT4-Style Domain Trusts with Windows 2000
    Common Errors
    Browsing of Trusted Domain Fails
    Problems with LDAP ldapsam and Older Versions of smbldap-tools
    20. Hosting a Microsoft Distributed File System Tree
    Features and Benefits
    Common Errors
    MSDFS UNIX Path Is Case-Critical
    21. Classical Printing Support
    Features and Benefits
    Technical Introduction
    Client to Samba Print Job Processing
    Printing-Related Configuration Parameters
    Simple Print Configuration
    Verifying Configuration with testparm
    Rapid Configuration Validation
    Extended Printing Configuration
    Detailed Explanation Settings
    Printing Developments Since Samba-2.2
    Point'n'Print Client Drivers on Samba Servers
    The Obsoleted [printer$] Section
    Creating the [print$] Share
    [print$] Stanza Parameters
    The [print$] Share Directory
    Installing Drivers into [print$]
    Add Printer Wizard Driver Installation
    Installing Print Drivers Using rpcclient
    Client Driver Installation Procedure
    First Client Driver Installation
    Setting Device Modes on New Printers
    Additional Client Driver Installation
    Always Make First Client Connection as root or “printer admin”
    Other Gotchas
    Setting Default Print Options for Client Drivers
    Supporting Large Numbers of Printers
    Adding New Printers with the Windows NT APW
    Error Message: “Cannot connect under a different Name”
    Take Care When Assembling Driver Files
    Samba and Printer Ports
    Avoiding Common Client Driver Misconfiguration
    The Imprints Toolset
    What Is Imprints?
    Creating Printer Driver Packages
    The Imprints Server
    The Installation Client
    Adding Network Printers without User Interaction
    The addprinter Command
    Migration of Classical Printing to Samba
    Publishing Printer Information in Active Directory or LDAP
    Common Errors
    I Give My Root Password but I Do Not Get Access
    My Print Jobs Get Spooled into the Spooling Directory, but Then Get Lost
    22. CUPS Printing Support
    Introduction
    Features and Benefits
    Overview
    Basic CUPS Support Configuration
    Linking smbd with libcups.so
    Simple smb.conf Settings for CUPS
    More Complex CUPS smb.conf Settings
    Advanced Configuration
    Central Spooling vs. “Peer-to-Peer” Printing
    Raw Print Serving: Vendor Drivers on Windows Clients
    Installation of Windows Client Drivers
    Explicitly Enable “raw” Printing for application/octet-stream
    Driver Upload Methods
    Advanced Intelligent Printing with PostScript Driver Download
    GDI on Windows, PostScript on UNIX
    Windows Drivers, GDI, and EMF
    UNIX Printfile Conversion and GUI Basics
    PostScript and Ghostscript
    Ghostscript: The Software RIP for Non-PostScript Printers
    PostScript Printer Description (PPD) Specification
    Using Windows-Formatted Vendor PPDs
    CUPS Also Uses PPDs for Non-PostScript Printers
    The CUPS Filtering Architecture
    MIME Types and CUPS Filters
    MIME Type Conversion Rules
    Filtering Overview
    Prefilters
    pstops
    pstoraster
    imagetops and imagetoraster
    rasterto [printers specific]
    CUPS Backends
    The Role of cupsomatic/foomatic
    The Complete Picture
    mime.convs
    “Raw” Printing
    application/octet-stream Printing
    PostScript Printer Descriptions for Non-PostScript Printers
    cupsomatic/foomatic-rip Versus Native CUPS Printing
    Examples for Filtering Chains
    Sources of CUPS Drivers/PPDs
    Printing with Interface Scripts
    Network Printing (Purely Windows)
    From Windows Clients to an NT Print Server
    Driver Execution on the Client
    Driver Execution on the Server
    Network Printing (Windows Clients and UNIX/Samba Print -Servers)
    From Windows Clients to a CUPS/Samba Print Server
    Samba Receiving Job-Files and Passing Them to CUPS
    Network PostScript RIP
    PPDs for Non-PS Printers on UNIX
    PPDs for Non-PS Printers on Windows
    Windows Terminal Servers (WTS) as CUPS Clients
    Printer Drivers Running in “Kernel Mode” Cause Many -Problems
    Workarounds Impose Heavy Limitations
    CUPS: A “Magical Stone”?
    PostScript Drivers with No Major Problems, Even in Kernel -Mode
    Configuring CUPS for Driver Download
    cupsaddsmb: The Unknown Utility
    Prepare Your smb.conf for cupsaddsmb
    CUPS “PostScript Driver for Windows NT/200x/XP”
    Recognizing Different Driver Files
    Acquiring the Adobe Driver Files
    ESP Print Pro PostScript Driver for Windows NT/200x/XP
    Caveats to Be Considered
    Windows CUPS PostScript Driver Versus Adobe Driver
    Run cupsaddsmb (Quiet Mode)
    Run cupsaddsmb with Verbose Output
    Understanding cupsaddsmb
    How to Recognize If cupsaddsmb Completed Successfully
    cupsaddsmb with a Samba PDC
    cupsaddsmb Flowchart
    Installing the PostScript Driver on a Client
    Avoiding Critical PostScript Driver Settings on the Client
    Installing PostScript Driver Files Manually Using rpcclient
    A Check of the rpcclient man Page
    Understanding the rpcclient man Page
    Producing an Example by Querying a Windows Box
    Requirements for adddriver and setdriver to Succeed
    Manual Driver Installation in 15 Steps
    Troubleshooting Revisited
    The Printing *.tdb Files
    Trivial Database Files
    Binary Format
    Losing *.tdb Files
    Using tdbbackup
    CUPS Print Drivers from Linuxprinting.org
    foomatic-rip and Foomatic Explained
    foomatic-rip and Foomatic PPD Download and Installation
    Page Accounting with CUPS
    Setting Up Quotas
    Correct and Incorrect Accounting
    Adobe and CUPS PostScript Drivers for Windows Clients
    The page_log File Syntax
    Possible Shortcomings
    Future Developments
    Other Accounting Tools
    Additional Material
    Autodeletion or Preservation of CUPS Spool Files
    CUPS Configuration Settings Explained
    Preconditions
    Manual Configuration
    Printing from CUPS to Windows-Attached Printers
    More CUPS Filtering Chains
    Common Errors
    Windows 9x/Me Client Can't Install Driver
    “cupsaddsmb” Keeps Asking for Root Password in Never-ending Loop
    “cupsaddsmb” or “rpcclient addriver” Emit Error
    “cupsaddsmb” Errors
    Client Can't Connect to Samba Printer
    New Account Reconnection from Windows 200x/XP Troubles
    Avoid Being Connected to the Samba Server as the Wrong User
    Upgrading to CUPS Drivers from Adobe Drivers
    Can't Use “cupsaddsmb” on Samba Server, Which Is a PDC
    Deleted Windows 200x Printer Driver Is Still Shown
    Windows 200x/XP Local Security Policies
    Administrator Cannot Install Printers for All Local Users
    Print Change, Notify Functions on NT Clients
    Win XP-SP1
    Print Options for All Users Can't Be Set on Windows 200x/XP
    Most Common Blunders in Driver Settings on Windows Clients
    cupsaddsmb Does Not Work with Newly Installed Printer
    Permissions on /var/spool/samba/ Get Reset After Each Reboot
    Print Queue Called “lp” Mishandles Print Jobs
    Location of Adobe PostScript Driver Files for “cupsaddsmb”
    Overview of the CUPS Printing Processes
    23. Stackable VFS modules
    Features and Benefits
    Discussion
    Included Modules
    audit
    default_quota
    extd_audit
    fake_perms
    recycle
    netatalk
    shadow_copy
    VFS Modules Available Elsewhere
    DatabaseFS
    vscan
    vscan-clamav
    24. Winbind: Use of Domain Accounts
    Features and Benefits
    Introduction
    What Winbind Provides
    Target Uses
    Handling of Foreign SIDs
    How Winbind Works
    Microsoft Remote Procedure Calls
    Microsoft Active Directory Services
    Name Service Switch
    Pluggable Authentication Modules
    User and Group ID Allocation
    Result Caching
    Installation and Configuration
    Introduction
    Requirements
    Testing Things Out
    Conclusion
    Common Errors
    NSCD Problem Warning
    Winbind Is Not Resolving Users and Groups
    25. Advanced Network Management
    Features and Benefits
    Remote Server Administration
    Remote Desktop Management
    Remote Management from NoMachine.Com
    Remote Management with ThinLinc
    Network Logon Script Magic
    Adding Printers without User Intervention
    Limiting Logon Connections
    26. System and Account Policies
    Features and Benefits
    Creating and Managing System Policies
    Windows 9x/ME Policies
    Windows NT4-Style Policy Files
    MS Windows 200x/XP Professional Policies
    Managing Account/User Policies
    Management Tools
    Samba Editreg Toolset
    Windows NT4/200x
    Samba PDC
    System Startup and Logon Processing Overview
    Common Errors
    Policy Does Not Work
    27. Desktop Profile Management
    Features and Benefits
    Roaming Profiles
    Samba Configuration for Profile Handling
    Windows Client Profile Configuration Information
    User Profile Hive Cleanup Service
    Sharing Profiles between Windows 9x/Me and NT4/200x/XP Workstations
    Profile Migration from Windows NT4/200x Server to Samba
    Mandatory Profiles
    Creating and Managing Group Profiles
    Default Profile for Windows Users
    MS Windows 9x/Me
    MS Windows NT4 Workstation
    MS Windows 200x/XP
    Common Errors
    Configuring Roaming Profiles for a Few Users or Groups
    Cannot Use Roaming Profiles
    Changing the Default Profile
    Debugging Roaming Profiles and NT4-style Domain Policies
    28. PAM-Based Distributed Authentication
    Features and Benefits
    Technical Discussion
    PAM Configuration Syntax
    Example System Configurations
    smb.conf PAM Configuration
    Remote CIFS Authentication Using winbindd.so
    Password Synchronization Using pam_smbpass.so
    Common Errors
    pam_winbind Problem
    Winbind Is Not Resolving Users and Groups
    29. Integrating MS Windows Networks with Samba
    Features and Benefits
    Background Information
    Name Resolution in a Pure UNIX/Linux World
    /etc/hosts
    /etc/resolv.conf
    /etc/host.conf
    /etc/nsswitch.conf
    Name Resolution as Used within MS Windows Networking
    The NetBIOS Name Cache
    The LMHOSTS File
    HOSTS File
    DNS Lookup
    WINS Lookup
    Common Errors
    Pinging Works Only One Way
    Very Slow Network Connections
    Samba Server Name-Change Problem
    30. Unicode/Charsets
    Features and Benefits
    What Are Charsets and Unicode?
    Samba and Charsets
    Conversion from Old Names
    Japanese Charsets
    Basic Parameter Setting
    Individual Implementations
    Migration from Samba-2.2 Series
    Common Errors
    CP850.so Can't Be Found
    31. Backup Techniques
    Features and Benefits
    Discussion of Backup Solutions
    BackupPC
    Rsync
    Amanda
    BOBS: Browseable Online Backup System
    32. High Availability
    Features and Benefits
    Technical Discussion
    The Ultimate Goal
    Why Is This So Hard?
    A Simple Solution
    High-Availability Server Products
    MS-DFS: The Poor Man's Cluster
    Conclusions
    33. Handling Large Directories
    34. Advanced Configuration Techniques
    Implementation
    Multiple Server Hosting
    Multiple Virtual Server Personalities
    Multiple Virtual Server Hosting
    IV. Migration and Updating
    35. Updating and Upgrading Samba
    Key Update Requirements
    Upgrading from Samba-3.0.x to Samba-3.2.0
    Upgrading from Samba-2.x to Samba-3.0.25
    Quick Migration Guide
    New Featuers in Samba-3.x Series
    New Features in Samba-3.2.x Series
    New Features in Samba-3.0.x
    New Functionality
    36. Migration from NT4 PDC to Samba-3 PDC
    Planning and Getting Started
    Objectives
    Steps in Migration Process
    Migration Options
    Planning for Success
    Samba-3 Implementation Choices
    37. SWAT: The Samba Web Administration Tool
    Features and Benefits
    Guidelines and Technical Tips
    Validate SWAT Installation
    Enabling SWAT for Use
    Securing SWAT through SSL
    Enabling SWAT Internationalization Support
    Overview and Quick Tour
    The SWAT Home Page
    Global Settings
    Share Settings
    Printers Settings
    The SWAT Wizard
    The Status Page
    The View Page
    The Password Change Page
    V. Troubleshooting
    38. The Samba Checklist
    Introduction
    Assumptions
    The Tests
    39. Analyzing and Solving Samba Problems
    Diagnostics Tools
    Debugging with Samba Itself
    Tcpdump
    Ethereal
    The Windows Network Monitor
    Useful URLs
    Getting Mailing List Help
    How to Get Off the Mailing Lists
    40. Reporting Bugs
    Introduction
    General Information
    Debug Levels
    Debugging-Specific Operations
    Internal Errors
    Attaching to a Running Process
    Patches
    VI. Reference Section
    41. How to Compile Samba
    Access Samba Source Code via Subversion
    Introduction
    Subversion Access to samba.org
    Accessing the Samba Sources via rsync and ftp
    Verifying Samba's PGP Signature
    Building the Binaries
    Compiling Samba with Active Directory Support
    Starting the smbd nmbd and winbindd
    Starting from inetd.conf
    Alternative: Starting smbd as a Daemon
    42. Portability
    HPUX
    SCO UNIX
    DNIX
    Red Hat Linux
    AIX: Sequential Read Ahead
    Solaris
    Locking Improvements
    Winbind on Solaris 9
    43. Samba and Other CIFS Clients
    Macintosh Clients
    OS2 Client
    Configuring OS/2 Warp Connect or OS/2 Warp 4
    Configuring Other Versions of OS/2
    Printer Driver Download for OS/2 Clients
    Windows for Workgroups
    Latest TCP/IP Stack from Microsoft
    Delete .pwl Files After Password Change
    Configuring Windows for Workgroups Password Handling
    Password Case Sensitivity
    Use TCP/IP as Default Protocol
    Speed Improvement
    Windows 95/98
    Speed Improvement
    Windows 2000 Service Pack 2
    Windows NT 3.1
    44. Samba Performance Tuning
    Comparisons
    Socket Options
    Read Size
    Max Xmit
    Log Level
    Read Raw
    Write Raw
    Slow Logins
    Client Tuning
    Samba Performance Problem Due to Changing Linux Kernel
    Corrupt tdb Files
    Samba Performance is Very Slow
    45. LDAP and Transport Layer Security
    Introduction
    Configuring
    Generating the Certificate Authority
    Generating the Server Certificate
    Installing the Certificates
    Testing
    Troubleshooting
    46. Samba Support
    Free Support
    Commercial Support
    47. DNS and DHCP Configuration Guide
    Features and Benefits
    Example Configuration
    Dynamic DNS
    DHCP Server
    A. +The Official Samba 3.2.x HOWTO and Reference Guide
    The Official Samba 3.2.x HOWTO and Reference Guide
       Next

    The Official Samba 3.2.x HOWTO and Reference Guide

    Edited by

    Jelmer R. Vernooij

    The Samba Team

    Edited by

    John H. Terpstra

    Samba Team

    Edited by

    Gerald (Jerry) Carter

    Samba Team

    Table of Contents

    About the Cover Artwork
    Attribution
    Foreword
    Preface
    Conventions Used
    Introduction
    What Is Samba?
    Why This Book?
    Book Structure and Layout
    I. General Installation
    1. How to Install and Test SAMBA
    Obtaining and Installing Samba
    Configuring Samba (smb.conf)
    Configuration File Syntax
    TDB Database File Information
    Starting Samba
    Example Configuration
    SWAT
    List Shares Available on the Server
    Connect with a UNIX Client
    Connect from a Remote SMB Client
    What If Things Don't Work?
    Still Stuck?
    Common Errors
    Large Number of smbd Processes
    Error Message: open_oplock_ipc
    “The network name cannot be found”
    2. Fast Start: Cure for Impatience
    Features and Benefits
    Description of Example Sites
    Worked Examples
    Standalone Server
    Domain Member Server
    Domain Controller
    II. Server Configuration Basics
    3. Server Types and Security Modes
    Features and Benefits
    Server Types
    Samba Security Modes
    User Level Security
    Share-Level Security
    Domain Security Mode (User-Level Security)
    ADS Security Mode (User-Level Security)
    Server Security (User Level Security)
    Password Checking
    Common Errors
    What Makes Samba a Server?
    What Makes Samba a Domain Controller?
    What Makes Samba a Domain Member?
    Constantly Losing Connections to Password Server
    Stand-alone Server is converted to Domain Controller Now User accounts don't work
    4. Domain Control
    Features and Benefits
    Single Sign-On and Domain Security
    Basics of Domain Control
    Domain Controller Types
    Preparing for Domain Control
    Domain Control: Example Configuration
    Samba ADS Domain Control
    Domain and Network Logon Configuration
    Domain Network Logon Service
    Security Mode and Master Browsers
    Common Errors
    “$” Cannot Be Included in Machine Name
    Joining Domain Fails Because of Existing Machine Account
    The System Cannot Log You On (C000019B)
    The Machine Trust Account Is Not Accessible
    Account Disabled
    Domain Controller Unavailable
    Cannot Log onto Domain Member Workstation After Joining Domain
    5. Backup Domain Control
    Features and Benefits
    Essential Background Information
    MS Windows NT4-style Domain Control
    LDAP Configuration Notes
    Active Directory Domain Control
    What Qualifies a Domain Controller on the Network?
    How Does a Workstation find its Domain Controller?
    Backup Domain Controller Configuration
    Example Configuration
    Common Errors
    Machine Accounts Keep Expiring
    Can Samba Be a Backup Domain Controller to an NT4 PDC?
    How Do I Replicate the smbpasswd File?
    Can I Do This All with LDAP?
    6. Domain Membership
    Features and Benefits
    MS Windows Workstation/Server Machine Trust Accounts
    Manual Creation of Machine Trust Accounts
    Managing Domain Machine Accounts using NT4 Server Manager
    On-the-Fly Creation of Machine Trust Accounts
    Making an MS Windows Workstation or Server a Domain Member
    Domain Member Server
    Joining an NT4-type Domain with Samba-3
    Why Is This Better Than security = server?
    Samba ADS Domain Membership
    Configure smb.conf
    Configure /etc/krb5.conf
    Create the Computer Account
    Testing Server Setup
    Testing with smbclient
    Notes
    Sharing User ID Mappings between Samba Domain Members
    Common Errors
    Cannot Add Machine Back to Domain
    Adding Machine to Domain Fails
    I Can't Join a Windows 2003 PDC
    7. Standalone Servers
    Features and Benefits
    Background
    Example Configuration
    Reference Documentation Server
    Central Print Serving
    Common Errors
    8. MS Windows Network Configuration Guide
    Features and Benefits
    Technical Details
    TCP/IP Configuration
    Joining a Domain: Windows 2000/XP Professional
    Domain Logon Configuration: Windows 9x/Me
    Common Errors
    III. Advanced Configuration
    9. Important and Critical Change Notes for the Samba 3.x Series
    Important Samba-3.2.x Change Notes
    Important Samba-3.0.x Change Notes
    User and Group Changes
    Essential Group Mappings
    Passdb Changes
    Group Mapping Changes in Samba-3.0.23
    LDAP Changes in Samba-3.0.23
    10. Network Browsing
    Features and Benefits
    What Is Browsing?
    Discussion
    NetBIOS over TCP/IP
    TCP/IP without NetBIOS
    DNS and Active Directory
    How Browsing Functions
    Configuring Workgroup Browsing
    Domain Browsing Configuration
    Forcing Samba to Be the Master
    Making Samba the Domain Master
    Note about Broadcast Addresses
    Multiple Interfaces
    Use of the Remote Announce Parameter
    Use of the Remote Browse Sync Parameter
    WINS: The Windows Internetworking Name Server
    WINS Server Configuration
    WINS Replication
    Static WINS Entries
    Helpful Hints
    Windows Networking Protocols
    Name Resolution Order
    Technical Overview of Browsing
    Browsing Support in Samba
    Problem Resolution
    Cross-Subnet Browsing
    Common Errors
    Flushing the Samba NetBIOS Name Cache
    Server Resources Cannot Be Listed
    I Get an "Unable to browse the network" Error
    Browsing of Shares and Directories is Very Slow
    Invalid Cached Share References Affects Network Browsing
    11. Account Information Databases
    Features and Benefits
    Backward Compatibility Account Storage Systems
    New Account Storage Systems
    Technical Information
    Important Notes About Security
    Mapping User Identifiers between MS Windows and UNIX
    Mapping Common UIDs/GIDs on Distributed Machines
    Comments Regarding LDAP
    LDAP Directories and Windows Computer Accounts
    Account Management Tools
    The smbpasswd Tool
    The pdbedit Tool
    Password Backends
    Plaintext
    smbpasswd: Encrypted Password Database
    tdbsam
    ldapsam
    Common Errors
    Users Cannot Logon
    Configuration of auth methods
    12. Group Mapping: MS Windows and UNIX
    Features and Benefits
    Discussion
    Warning: User Private Group Problems
    Nested Groups: Adding Windows Domain Groups to Windows Local Groups
    Important Administrative Information
    Default Users, Groups, and Relative Identifiers
    Example Configuration
    Configuration Scripts
    Sample smb.conf Add Group Script
    Script to Configure Group Mapping
    Common Errors
    Adding Groups Fails
    Adding Domain Users to the Workstation Power Users Group
    13. Remote and Local Management: The Net Command
    Overview
    Administrative Tasks and Methods
    UNIX and Windows Group Management
    Adding, Renaming, or Deletion of Group Accounts
    Manipulating Group Memberships
    Nested Group Support
    UNIX and Windows User Management
    Adding User Accounts
    Deletion of User Accounts
    Managing User Accounts
    User Mapping
    Administering User Rights and Privileges
    Managing Trust Relationships
    Machine Trust Accounts
    Interdomain Trusts
    Managing Security Identifiers (SIDS)
    Share Management
    Creating, Editing, and Removing Shares
    Creating and Changing Share ACLs
    Share, Directory, and File Migration
    Printer Migration
    Controlling Open Files
    Session and Connection Management
    Printers and ADS
    Manipulating the Samba Cache
    Managing IDMAP UID/SID Mappings
    Creating an IDMAP Database Dump File
    Restoring the IDMAP Database Dump File
    Other Miscellaneous Operations
    14. Identity Mapping (IDMAP)
    Samba Server Deployment Types and IDMAP
    Standalone Samba Server
    Domain Member Server or Domain Member Client
    Primary Domain Controller
    Backup Domain Controller
    Examples of IDMAP Backend Usage
    Default Winbind TDB
    IDMAP_RID with Winbind
    IDMAP Storage in LDAP Using Winbind
    IDMAP and NSS Using LDAP from ADS with RFC2307bis Schema Extension
    15. User Rights and Privileges
    Rights Management Capabilities
    Using the “net rpc rights” Utility
    Description of Privileges
    Privileges Suppored by Windows 2000 Domain Controllers
    The Administrator Domain SID
    Common Errors
    What Rights and Privileges Will Permit Windows Client Administration?
    16. File, Directory, and Share Access Controls
    Features and Benefits
    File System Access Controls
    MS Windows NTFS Comparison with UNIX File Systems
    Managing Directories
    File and Directory Access Control
    Share Definition Access Controls
    User- and Group-Based Controls
    File and Directory Permissions-Based Controls
    Miscellaneous Controls
    Access Controls on Shares
    Share Permissions Management
    MS Windows Access Control Lists and UNIX Interoperability
    Managing UNIX Permissions Using NT Security Dialogs
    Viewing File Security on a Samba Share
    Viewing File Ownership
    Viewing File or Directory Permissions
    Modifying File or Directory Permissions
    Interaction with the Standard Samba “create mask” Parameters
    Interaction with the Standard Samba File Attribute Mapping
    Windows NT/200X ACLs and POSIX ACLs Limitations
    Common Errors
    Users Cannot Write to a Public Share
    File Operations Done as root with force user Set
    MS Word with Samba Changes Owner of File
    17. File and Record Locking
    Features and Benefits
    Discussion
    Opportunistic Locking Overview
    Samba Oplocks Control
    Example Configuration
    MS Windows Oplocks and Caching Controls
    Workstation Service Entries
    Server Service Entries
    Persistent Data Corruption
    Common Errors
    locking.tdb Error Messages
    Problems Saving Files in MS Office on Windows XP
    Long Delays Deleting Files over Network with XP SP1
    Additional Reading
    18. Securing Samba
    Introduction
    Features and Benefits
    Technical Discussion of Protective Measures and Issues
    Using Host-Based Protection
    User-Based Protection
    Using Interface Protection
    Using a Firewall
    Using IPC$ Share-Based Denials
    NTLMv2 Security
    Upgrading Samba
    Common Errors
    Smbclient Works on Localhost, but the Network Is Dead
    Why Can Users Access Other Users' Home Directories?
    19. Interdomain Trust Relationships
    Features and Benefits
    Trust Relationship Background
    Native MS Windows NT4 Trusts Configuration
    Creating an NT4 Domain Trust
    Completing an NT4 Domain Trust
    Interdomain Trust Facilities
    Configuring Samba NT-Style Domain Trusts
    Samba as the Trusted Domain
    Samba as the Trusting Domain
    NT4-Style Domain Trusts with Windows 2000
    Common Errors
    Browsing of Trusted Domain Fails
    Problems with LDAP ldapsam and Older Versions of smbldap-tools
    20. Hosting a Microsoft Distributed File System Tree
    Features and Benefits
    Common Errors
    MSDFS UNIX Path Is Case-Critical
    21. Classical Printing Support
    Features and Benefits
    Technical Introduction
    Client to Samba Print Job Processing
    Printing-Related Configuration Parameters
    Simple Print Configuration
    Verifying Configuration with testparm
    Rapid Configuration Validation
    Extended Printing Configuration
    Detailed Explanation Settings
    Printing Developments Since Samba-2.2
    Point'n'Print Client Drivers on Samba Servers
    The Obsoleted [printer$] Section
    Creating the [print$] Share
    [print$] Stanza Parameters
    The [print$] Share Directory
    Installing Drivers into [print$]
    Add Printer Wizard Driver Installation
    Installing Print Drivers Using rpcclient
    Client Driver Installation Procedure
    First Client Driver Installation
    Setting Device Modes on New Printers
    Additional Client Driver Installation
    Always Make First Client Connection as root or “printer admin”
    Other Gotchas
    Setting Default Print Options for Client Drivers
    Supporting Large Numbers of Printers
    Adding New Printers with the Windows NT APW
    Error Message: “Cannot connect under a different Name”
    Take Care When Assembling Driver Files
    Samba and Printer Ports
    Avoiding Common Client Driver Misconfiguration
    The Imprints Toolset
    What Is Imprints?
    Creating Printer Driver Packages
    The Imprints Server
    The Installation Client
    Adding Network Printers without User Interaction
    The addprinter Command
    Migration of Classical Printing to Samba
    Publishing Printer Information in Active Directory or LDAP
    Common Errors
    I Give My Root Password but I Do Not Get Access
    My Print Jobs Get Spooled into the Spooling Directory, but Then Get Lost
    22. CUPS Printing Support
    Introduction
    Features and Benefits
    Overview
    Basic CUPS Support Configuration
    Linking smbd with libcups.so
    Simple smb.conf Settings for CUPS
    More Complex CUPS smb.conf Settings
    Advanced Configuration
    Central Spooling vs. “Peer-to-Peer” Printing
    Raw Print Serving: Vendor Drivers on Windows Clients
    Installation of Windows Client Drivers
    Explicitly Enable “raw” Printing for application/octet-stream
    Driver Upload Methods
    Advanced Intelligent Printing with PostScript Driver Download
    GDI on Windows, PostScript on UNIX
    Windows Drivers, GDI, and EMF
    UNIX Printfile Conversion and GUI Basics
    PostScript and Ghostscript
    Ghostscript: The Software RIP for Non-PostScript Printers
    PostScript Printer Description (PPD) Specification
    Using Windows-Formatted Vendor PPDs
    CUPS Also Uses PPDs for Non-PostScript Printers
    The CUPS Filtering Architecture
    MIME Types and CUPS Filters
    MIME Type Conversion Rules
    Filtering Overview
    Prefilters
    pstops
    pstoraster
    imagetops and imagetoraster
    rasterto [printers specific]
    CUPS Backends
    The Role of cupsomatic/foomatic
    The Complete Picture
    mime.convs
    “Raw” Printing
    application/octet-stream Printing
    PostScript Printer Descriptions for Non-PostScript Printers
    cupsomatic/foomatic-rip Versus Native CUPS Printing
    Examples for Filtering Chains
    Sources of CUPS Drivers/PPDs
    Printing with Interface Scripts
    Network Printing (Purely Windows)
    From Windows Clients to an NT Print Server
    Driver Execution on the Client
    Driver Execution on the Server
    Network Printing (Windows Clients and UNIX/Samba Print +Servers)
    From Windows Clients to a CUPS/Samba Print Server
    Samba Receiving Job-Files and Passing Them to CUPS
    Network PostScript RIP
    PPDs for Non-PS Printers on UNIX
    PPDs for Non-PS Printers on Windows
    Windows Terminal Servers (WTS) as CUPS Clients
    Printer Drivers Running in “Kernel Mode” Cause Many +Problems
    Workarounds Impose Heavy Limitations
    CUPS: A “Magical Stone”?
    PostScript Drivers with No Major Problems, Even in Kernel +Mode
    Configuring CUPS for Driver Download
    cupsaddsmb: The Unknown Utility
    Prepare Your smb.conf for cupsaddsmb
    CUPS “PostScript Driver for Windows NT/200x/XP”
    Recognizing Different Driver Files
    Acquiring the Adobe Driver Files
    ESP Print Pro PostScript Driver for Windows NT/200x/XP
    Caveats to Be Considered
    Windows CUPS PostScript Driver Versus Adobe Driver
    Run cupsaddsmb (Quiet Mode)
    Run cupsaddsmb with Verbose Output
    Understanding cupsaddsmb
    How to Recognize If cupsaddsmb Completed Successfully
    cupsaddsmb with a Samba PDC
    cupsaddsmb Flowchart
    Installing the PostScript Driver on a Client
    Avoiding Critical PostScript Driver Settings on the Client
    Installing PostScript Driver Files Manually Using rpcclient
    A Check of the rpcclient man Page
    Understanding the rpcclient man Page
    Producing an Example by Querying a Windows Box
    Requirements for adddriver and setdriver to Succeed
    Manual Driver Installation in 15 Steps
    Troubleshooting Revisited
    The Printing *.tdb Files
    Trivial Database Files
    Binary Format
    Losing *.tdb Files
    Using tdbbackup
    CUPS Print Drivers from Linuxprinting.org
    foomatic-rip and Foomatic Explained
    foomatic-rip and Foomatic PPD Download and Installation
    Page Accounting with CUPS
    Setting Up Quotas
    Correct and Incorrect Accounting
    Adobe and CUPS PostScript Drivers for Windows Clients
    The page_log File Syntax
    Possible Shortcomings
    Future Developments
    Other Accounting Tools
    Additional Material
    Autodeletion or Preservation of CUPS Spool Files
    CUPS Configuration Settings Explained
    Preconditions
    Manual Configuration
    Printing from CUPS to Windows-Attached Printers
    More CUPS Filtering Chains
    Common Errors
    Windows 9x/Me Client Can't Install Driver
    “cupsaddsmb” Keeps Asking for Root Password in Never-ending Loop
    “cupsaddsmb” or “rpcclient addriver” Emit Error
    “cupsaddsmb” Errors
    Client Can't Connect to Samba Printer
    New Account Reconnection from Windows 200x/XP Troubles
    Avoid Being Connected to the Samba Server as the Wrong User
    Upgrading to CUPS Drivers from Adobe Drivers
    Can't Use “cupsaddsmb” on Samba Server, Which Is a PDC
    Deleted Windows 200x Printer Driver Is Still Shown
    Windows 200x/XP Local Security Policies
    Administrator Cannot Install Printers for All Local Users
    Print Change, Notify Functions on NT Clients
    Windows XP SP1
    Print Options for All Users Can't Be Set on Windows 200x/XP
    Most Common Blunders in Driver Settings on Windows Clients
    cupsaddsmb Does Not Work with Newly Installed Printer
    Permissions on /var/spool/samba/ Get Reset After Each Reboot
    Print Queue Called “lp” Mishandles Print Jobs
    Location of Adobe PostScript Driver Files for “cupsaddsmb”
    Overview of the CUPS Printing Processes
    23. Stackable VFS modules
    Features and Benefits
    Discussion
    Included Modules
    audit
    default_quota
    extd_audit
    fake_perms
    recycle
    netatalk
    shadow_copy
    VFS Modules Available Elsewhere
    DatabaseFS
    vscan
    vscan-clamav
    24. Winbind: Use of Domain Accounts
    Features and Benefits
    Introduction
    What Winbind Provides
    Target Uses
    Handling of Foreign SIDs
    How Winbind Works
    Microsoft Remote Procedure Calls
    Microsoft Active Directory Services
    Name Service Switch
    Pluggable Authentication Modules
    User and Group ID Allocation
    Result Caching
    Installation and Configuration
    Introduction
    Requirements
    Testing Things Out
    Conclusion
    Common Errors
    NSCD Problem Warning
    Winbind Is Not Resolving Users and Groups
    25. Advanced Network Management
    Features and Benefits
    Remote Server Administration
    Remote Desktop Management
    Remote Management from NoMachine.Com
    Remote Management with ThinLinc
    Network Logon Script Magic
    Adding Printers without User Intervention
    Limiting Logon Connections
    26. System and Account Policies
    Features and Benefits
    Creating and Managing System Policies
    Windows 9x/ME Policies
    Windows NT4-Style Policy Files
    MS Windows 200x/XP Professional Policies
    Managing Account/User Policies
    Management Tools
    Samba Editreg Toolset
    Windows NT4/200x
    Samba PDC
    System Startup and Logon Processing Overview
    Common Errors
    Policy Does Not Work
    27. Desktop Profile Management
    Features and Benefits
    Roaming Profiles
    Samba Configuration for Profile Handling
    Windows Client Profile Configuration Information
    User Profile Hive Cleanup Service
    Sharing Profiles between Windows 9x/Me and NT4/200x/XP Workstations
    Profile Migration from Windows NT4/200x Server to Samba
    Mandatory Profiles
    Creating and Managing Group Profiles
    Default Profile for Windows Users
    MS Windows 9x/Me
    MS Windows NT4 Workstation
    MS Windows 200x/XP
    Common Errors
    Configuring Roaming Profiles for a Few Users or Groups
    Cannot Use Roaming Profiles
    Changing the Default Profile
    Debugging Roaming Profiles and NT4-style Domain Policies
    28. PAM-Based Distributed Authentication
    Features and Benefits
    Technical Discussion
    PAM Configuration Syntax
    Example System Configurations
    smb.conf PAM Configuration
    Remote CIFS Authentication Using winbindd.so
    Password Synchronization Using pam_smbpass.so
    Common Errors
    pam_winbind Problem
    Winbind Is Not Resolving Users and Groups
    29. Integrating MS Windows Networks with Samba
    Features and Benefits
    Background Information
    Name Resolution in a Pure UNIX/Linux World
    /etc/hosts
    /etc/resolv.conf
    /etc/host.conf
    /etc/nsswitch.conf
    Name Resolution as Used within MS Windows Networking
    The NetBIOS Name Cache
    The LMHOSTS File
    HOSTS File
    DNS Lookup
    WINS Lookup
    Common Errors
    Pinging Works Only One Way
    Very Slow Network Connections
    Samba Server Name-Change Problem
    30. Unicode/Charsets
    Features and Benefits
    What Are Charsets and Unicode?
    Samba and Charsets
    Conversion from Old Names
    Japanese Charsets
    Basic Parameter Setting
    Individual Implementations
    Migration from Samba-2.2 Series
    Common Errors
    CP850.so Can't Be Found
    31. Backup Techniques
    Features and Benefits
    Discussion of Backup Solutions
    BackupPC
    Rsync
    Amanda
    BOBS: Browseable Online Backup System
    32. High Availability
    Features and Benefits
    Technical Discussion
    The Ultimate Goal
    Why Is This So Hard?
    A Simple Solution
    High-Availability Server Products
    MS-DFS: The Poor Man's Cluster
    Conclusions
    33. Handling Large Directories
    34. Advanced Configuration Techniques
    Implementation
    Multiple Server Hosting
    Multiple Virtual Server Personalities
    Multiple Virtual Server Hosting
    IV. Migration and Updating
    35. Updating and Upgrading Samba
    Key Update Requirements
    Upgrading from Samba-3.0.x to Samba-3.2.0
    Upgrading from Samba-2.x to Samba-3.0.25
    Quick Migration Guide
    New Featuers in Samba-3.x Series
    New Features in Samba-3.2.x Series
    New Features in Samba-3.0.x
    New Functionality
    36. Migration from NT4 PDC to Samba-3 PDC
    Planning and Getting Started
    Objectives
    Steps in Migration Process
    Migration Options
    Planning for Success
    Samba-3 Implementation Choices
    37. SWAT: The Samba Web Administration Tool
    Features and Benefits
    Guidelines and Technical Tips
    Validate SWAT Installation
    Enabling SWAT for Use
    Securing SWAT through SSL
    Enabling SWAT Internationalization Support
    Overview and Quick Tour
    The SWAT Home Page
    Global Settings
    Share Settings
    Printers Settings
    The SWAT Wizard
    The Status Page
    The View Page
    The Password Change Page
    V. Troubleshooting
    38. The Samba Checklist
    Introduction
    Assumptions
    The Tests
    39. Analyzing and Solving Samba Problems
    Diagnostics Tools
    Debugging with Samba Itself
    Tcpdump
    Ethereal
    The Windows Network Monitor
    Useful URLs
    Getting Mailing List Help
    How to Get Off the Mailing Lists
    40. Reporting Bugs
    Introduction
    General Information
    Debug Levels
    Debugging-Specific Operations
    Internal Errors
    Attaching to a Running Process
    Patches
    41. Managing TDB Files
    Features and Benefits
    Managing TDB Files
    VI. Reference Section
    42. How to Compile Samba
    Access Samba Source Code via Subversion
    Introduction
    Subversion Access to samba.org
    Accessing the Samba Sources via rsync and ftp
    Verifying Samba's PGP Signature
    Building the Binaries
    Compiling Samba with Active Directory Support
    Starting the smbd nmbd and winbindd
    Starting from inetd.conf
    Alternative: Starting smbd as a Daemon
    43. Portability
    HPUX
    SCO UNIX
    DNIX
    Red Hat Linux
    AIX: Sequential Read Ahead
    Solaris
    Locking Improvements
    Winbind on Solaris 9
    44. Samba and Other CIFS Clients
    Macintosh Clients
    OS2 Client
    Configuring OS/2 Warp Connect or OS/2 Warp 4
    Configuring Other Versions of OS/2
    Printer Driver Download for OS/2 Clients
    Windows for Workgroups
    Latest TCP/IP Stack from Microsoft
    Delete .pwl Files After Password Change
    Configuring Windows for Workgroups Password Handling
    Password Case Sensitivity
    Use TCP/IP as Default Protocol
    Speed Improvement
    Windows 95/98
    Speed Improvement
    Windows 2000 Service Pack 2
    Windows NT 3.1
    45. Samba Performance Tuning
    Comparisons
    Socket Options
    Read Size
    Max Xmit
    Log Level
    Read Raw
    Write Raw
    Slow Logins
    Client Tuning
    Samba Performance Problem Due to Changing Linux Kernel
    Corrupt tdb Files
    Samba Performance is Very Slow
    46. LDAP and Transport Layer Security
    Introduction
    Configuring
    Generating the Certificate Authority
    Generating the Server Certificate
    Installing the Certificates
    Testing
    Troubleshooting
    47. Samba Support
    Free Support
    Commercial Support
    48. DNS and DHCP Configuration Guide
    Features and Benefits
    Example Configuration
    Dynamic DNS
    DHCP Server
    A. GNU General Public License version 3 -
    A. +
    A. Preamble -
    A. +
    A. TERMS AND CONDITIONS -
    A. +
    A. 0. Definitions. -
    A. +
    A. 1. Source Code. -
    A. +
    A. 2. Basic Permissions. -
    A. +
    A. 3. Protecting Users’ Legal Rights From Anti-Circumvention Law. -
    A. +
    A. 4. Conveying Verbatim Copies. -
    A. +
    A. 5. Conveying Modified Source Versions. -
    A. +
    A. 6. Conveying Non-Source Forms. -
    A. +
    A. 7. Additional Terms. -
    A. +
    A. 8. Termination. -
    A. +
    A. 9. Acceptance Not Required for Having Copies. -
    A. +
    A. 10. Automatic Licensing of Downstream Recipients. -
    A. +
    A. 11. Patents. -
    A. +
    A. 12. No Surrender of Others’ Freedom. -
    A. +
    A. 13. Use with the ???TITLE??? Affero General Public License. -
    A. +
    A. 14. Revised Versions of this License. -
    A. +
    A. 15. Disclaimer of Warranty. -
    A. +
    A. 16. Limitation of Liability. -
    A. +
    A. 17. Interpretation of Sections 15 and 16. -
    A. +
    A. END OF TERMS AND CONDITIONS -
    A. +
    A. How to Apply These Terms to Your New Programs -
    Glossary
    Index

    List of Figures

    4.1. An Example Domain.
    8.1. Network Bridge Configuration.
    8.2. Internet Protocol (TCP/IP) Properties.
    8.3. Advanced Network Settings
    8.4. DNS Configuration.
    8.5. WINS Configuration
    8.6. Local Area Connection Properties.
    8.7. Internet Protocol (TCP/IP) Properties.
    8.8. Advanced Network Settings.
    8.9. DNS Configuration.
    8.10. WINS Configuration.
    8.11. The Windows Me Network Configuration Panel.
    8.12. IP Address.
    8.13. DNS Configuration.
    8.14. WINS Configuration.
    8.15. The General Panel.
    8.16. The Computer Name Panel.
    8.17. The Computer Name Changes Panel.
    8.18. The Computer Name Changes Panel Domain MIDEARTH.
    8.19. Computer Name Changes Username and Password Panel.
    8.20. The Network Panel.
    8.21. Client for Microsoft Networks Properties Panel.
    8.22. Identification Panel.
    8.23. Access Control Panel.
    10.1. Cross-Subnet Browsing Example.
    11.1. IDMAP: Resolution of SIDs to UIDs.
    11.2. IDMAP: Resolution of UIDs to SIDs.
    12.1. IDMAP: Group SID-to-GID Resolution.
    12.2. IDMAP: GID Resolution to Matching SID.
    12.3. IDMAP Storing Group Mappings.
    16.1. Overview of UNIX permissions field.
    19.1. Trusts overview.
    22.1. Windows Printing to a Local Printer.
    22.2. Printing to a PostScript Printer.
    22.3. Ghostscript as a RIP for Non-PostScript Printers.
    22.4. Prefiltering in CUPS to Form PostScript.
    22.5. Adding Device-Specific Print Options.
    22.6. PostScript to Intermediate Raster Format.
    22.7. CUPS-Raster Production Using Ghostscript.
    22.8. Image Format to CUPS-Raster Format Conversion.
    22.9. Raster to Printer-Specific Formats.
    22.10. cupsomatic/foomatic Processing Versus Native CUPS.
    22.11. PDF to Socket Chain.
    22.12. PDF to USB Chain.
    22.13. Print Driver Execution on the Client.
    22.14. Print Driver Execution on the Server.
    22.15. Printing via CUPS/Samba Server.
    22.16. cupsaddsmb Flowchart.
    22.17. Filtering Chain 1.
    22.18. Filtering Chain with cupsomatic
    22.19. CUPS Printing Overview.
    24.1. Winbind Idmap
    39.1. Starting a Capture.
    39.2. Main Ethereal Data Window.

    List of Tables

    1.1. Persistent TDB File Descriptions
    1.2. Temporary TDB File Descriptions
    5.1. Domain Backend Account Distribution Options
    6.1. Assumptions
    9.1. Essential Domain Group Mappings
    10.1. Browse Subnet Example 1
    10.2. Browse Subnet Example 2
    10.3. Browse Subnet Example 3
    10.4. Browse Subnet Example 4
    11.1. NT4 Domain v's Samba Policy Controls
    11.2. Samba SAM Account Control Block Flags
    11.3. Attributes in the sambaSamAccount ObjectClass (LDAP), Part A
    11.4. Attributes in the sambaSamAccount ObjectClass (LDAP), Part B
    11.5. Possible ldap passwd sync Values
    12.1. Well-Known User Default RIDs
    15.1. Current Privilege Capabilities
    16.1. Managing Directories with UNIX and Windows
    16.2. User- and Group-Based Controls
    16.3. File and Directory Permission-Based Controls
    16.4. Other Controls
    16.5. How Windows File ACLs Map to UNIX POSIX File ACLs
    21.1. Default Printing Settings
    22.1. PPDs Shipped with CUPS
    23.1. Extended Auditing Log Information
    27.1. User Shell Folder Registry Keys Default Values
    27.2. Defaults of Profile Settings Registry Keys
    27.3. Defaults of Default User Profile Paths Registry Keys
    28.1. Options recognized by pam_smbpass
    29.1. Unique NetBIOS Names
    29.2. Group Names
    30.1. Japanese Character Sets in Samba-2.2 and Samba-3
    35.1. Samba-2.2.x TDB File Descriptions
    36.1. The Three Major Site Types
    36.2. Nature of the Conversion Choices
    40.1. Debuggable Functions

    List of Examples

    1.1. A minimal smb.conf
    1.2. Another simple smb.conf File
    2.1. Anonymous Read-Only Server Configuration
    2.2. Modified Anonymous Read-Write smb.conf
    2.3. Anonymous Print Server smb.conf
    2.4. Secure Office Server smb.conf
    2.5. Member Server smb.conf (Globals)
    2.6. Member Server smb.conf (Shares and Services)
    2.7. Engineering Office smb.conf (globals)
    2.8. Engineering Office smb.conf (shares and services)
    2.9. LDAP backend smb.conf for PDC
    2.10. Remote LDAP BDC smb.conf
    4.1. smb.conf for being a PDC
    4.2. smb.conf for being a PDC
    5.1. Minimal smb.conf for a PDC in Use with a BDC LDAP Server on PDC
    5.2. Multiple LDAP Servers in smb.conf
    5.3. Minimal Setup for Being a BDC
    7.1. smb.conf for Reference Documentation Server
    7.2. smb.conf for Anonymous Printing
    10.1. Domain Master Browser smb.conf
    10.2. Local master browser smb.conf
    10.3. smb.conf for Not Being a Master Browser
    10.4. Local Master Browser smb.conf
    10.5. smb.conf for Not Being a master browser
    11.1. Example Configuration with the LDAP idmap Backend
    11.2. Configuration with LDAP
    12.1. smbgrpadd.sh
    12.2. Configuration of smb.conf for the add group Script
    12.3. Script to Set Group Mapping
    13.1. Script to Auto-add Domain Users to Workstation Power Users Group
    13.2. A Magic Netlogon Share
    14.1. NT4 Domain Member Server smb.conf
    14.2. ADS Domain Member Server smb.conf
    14.3. ADS Domain Member smb.conf using idmap_rid
    14.4. ADS Domain Member Server using LDAP
    14.5. ADS Domain Member Server using RFC2307bis Schema Extension Date via NSS
    16.1. Example File
    17.1. Share with Some Files Oplocked
    17.2. Configuration with Oplock Break Contention Limit
    20.1. smb.conf with DFS Configured
    21.1. Simple Configuration with BSD Printing
    21.2. Extended BSD Printing Configuration
    21.3. [print$] Example
    22.1. Simplest Printing-Related smb.conf
    22.2. Overriding Global CUPS Settings for One Printer
    22.3. smb.conf for cupsaddsmb Usage
    23.1. smb.conf with VFS modules
    23.2. smb.conf with multiple VFS modules
    23.3. Share With shadow_copy VFS
    24.1. smb.conf for Winbind Setup
    25.1. Script to Enforce Single Resource Logon
    30.1. VFS CAP
    34.1. Elastic smb.conf File
    34.2. CDROM Server smb-cdserver.conf file
    34.3. Master smb.conf File Global Section
    34.4. MERLIN smb-merlin.conf File Share Section
    34.5. SAURON smb-sauron.conf File Share Section
    38.1. smb.conf with [tmp] Share
    38.2. Configuration for Allowing Connections Only from a Certain Subnet
    38.3. Configuration for Allowing Connections from a Certain Subnet and localhost
    43.1. Minimal Profile Share
       Next
       About the Cover Artwork
    +
    Glossary
    Index

    List of Figures

    4.1. An Example Domain.
    8.1. Network Bridge Configuration.
    8.2. Internet Protocol (TCP/IP) Properties.
    8.3. Advanced Network Settings
    8.4. DNS Configuration.
    8.5. WINS Configuration
    8.6. Local Area Connection Properties.
    8.7. Internet Protocol (TCP/IP) Properties.
    8.8. Advanced Network Settings.
    8.9. DNS Configuration.
    8.10. WINS Configuration.
    8.11. The Windows Me Network Configuration Panel.
    8.12. IP Address.
    8.13. DNS Configuration.
    8.14. WINS Configuration.
    8.15. The General Panel.
    8.16. The Computer Name Panel.
    8.17. The Computer Name Changes Panel.
    8.18. The Computer Name Changes Panel Domain MIDEARTH.
    8.19. Computer Name Changes Username and Password Panel.
    8.20. The Network Panel.
    8.21. Client for Microsoft Networks Properties Panel.
    8.22. Identification Panel.
    8.23. Access Control Panel.
    10.1. Cross-Subnet Browsing Example.
    11.1. IDMAP: Resolution of SIDs to UIDs.
    11.2. IDMAP: Resolution of UIDs to SIDs.
    12.1. IDMAP: Group SID-to-GID Resolution.
    12.2. IDMAP: GID Resolution to Matching SID.
    12.3. IDMAP Storing Group Mappings.
    16.1. Overview of UNIX permissions field.
    19.1. Trusts overview.
    22.1. Windows Printing to a Local Printer.
    22.2. Printing to a PostScript Printer.
    22.3. Ghostscript as a RIP for Non-PostScript Printers.
    22.4. Prefiltering in CUPS to Form PostScript.
    22.5. Adding Device-Specific Print Options.
    22.6. PostScript to Intermediate Raster Format.
    22.7. CUPS-Raster Production Using Ghostscript.
    22.8. Image Format to CUPS-Raster Format Conversion.
    22.9. Raster to Printer-Specific Formats.
    22.10. cupsomatic/foomatic Processing Versus Native CUPS.
    22.11. PDF to Socket Chain.
    22.12. PDF to USB Chain.
    22.13. Print Driver Execution on the Client.
    22.14. Print Driver Execution on the Server.
    22.15. Printing via CUPS/Samba Server.
    22.16. cupsaddsmb Flowchart.
    22.17. Filtering Chain 1.
    22.18. Filtering Chain with cupsomatic
    22.19. CUPS Printing Overview.
    24.1. Winbind Idmap
    39.1. Starting a Capture.
    39.2. Main Ethereal Data Window.

    List of Tables

    1.1. Persistent TDB File Descriptions
    1.2. Temporary TDB File Descriptions
    5.1. Domain Backend Account Distribution Options
    6.1. Assumptions
    9.1. Essential Domain Group Mappings
    10.1. Browse Subnet Example 1
    10.2. Browse Subnet Example 2
    10.3. Browse Subnet Example 3
    10.4. Browse Subnet Example 4
    11.1. NT4 Domain v's Samba Policy Controls
    11.2. Samba SAM Account Control Block Flags
    11.3. Attributes in the sambaSamAccount ObjectClass (LDAP), Part A
    11.4. Attributes in the sambaSamAccount ObjectClass (LDAP), Part B
    11.5. Possible ldap passwd sync Values
    12.1. Well-Known User Default RIDs
    15.1. Current Privilege Capabilities
    16.1. Managing Directories with UNIX and Windows
    16.2. User- and Group-Based Controls
    16.3. File and Directory Permission-Based Controls
    16.4. Other Controls
    16.5. How Windows File ACLs Map to UNIX POSIX File ACLs
    21.1. Default Printing Settings
    22.1. PPDs Shipped with CUPS
    23.1. Extended Auditing Log Information
    27.1. User Shell Folder Registry Keys Default Values
    27.2. Defaults of Profile Settings Registry Keys
    27.3. Defaults of Default User Profile Paths Registry Keys
    28.1. Options recognized by pam_smbpass
    29.1. Unique NetBIOS Names
    29.2. Group Names
    30.1. Japanese Character Sets in Samba-2.2 and Samba-3
    35.1. Samba-2.2.x TDB File Descriptions
    36.1. The Three Major Site Types
    36.2. Nature of the Conversion Choices
    40.1. Debuggable Functions
    41.1. Samba's Trivial Database Files

    List of Examples

    1.1. A minimal smb.conf
    1.2. Another simple smb.conf File
    2.1. Anonymous Read-Only Server Configuration
    2.2. Modified Anonymous Read-Write smb.conf
    2.3. Anonymous Print Server smb.conf
    2.4. Secure Office Server smb.conf
    2.5. Member Server smb.conf (Globals)
    2.6. Member Server smb.conf (Shares and Services)
    2.7. Engineering Office smb.conf (globals)
    2.8. Engineering Office smb.conf (shares and services)
    2.9. LDAP backend smb.conf for PDC
    2.10. Remote LDAP BDC smb.conf
    4.1. smb.conf for being a PDC
    4.2. smb.conf for being a PDC
    5.1. Minimal smb.conf for a PDC in Use with a BDC LDAP Server on PDC
    5.2. Multiple LDAP Servers in smb.conf
    5.3. Minimal Setup for Being a BDC
    7.1. smb.conf for Reference Documentation Server
    7.2. smb.conf for Anonymous Printing
    10.1. Domain Master Browser smb.conf
    10.2. Local master browser smb.conf
    10.3. smb.conf for Not Being a Master Browser
    10.4. Local Master Browser smb.conf
    10.5. smb.conf for Not Being a master browser
    11.1. Example Configuration with the LDAP idmap Backend
    11.2. Configuration with LDAP
    12.1. smbgrpadd.sh
    12.2. Configuration of smb.conf for the add group Script
    12.3. Script to Set Group Mapping
    13.1. Script to Auto-add Domain Users to Workstation Power Users Group
    13.2. A Magic Netlogon Share
    14.1. NT4 Domain Member Server smb.conf
    14.2. ADS Domain Member Server smb.conf
    14.3. ADS Domain Member smb.conf using idmap_rid
    14.4. ADS Domain Member Server using LDAP
    14.5. ADS Domain Member Server using RFC2307bis Schema Extension Date via NSS
    16.1. Example File
    17.1. Share with Some Files Oplocked
    17.2. Configuration with Oplock Break Contention Limit
    20.1. smb.conf with DFS Configured
    21.1. Simple Configuration with BSD Printing
    21.2. Extended BSD Printing Configuration
    21.3. [print$] Example
    22.1. Simplest Printing-Related smb.conf
    22.2. Overriding Global CUPS Settings for One Printer
    22.3. smb.conf for cupsaddsmb Usage
    23.1. smb.conf with VFS modules
    23.2. smb.conf with multiple VFS modules
    23.3. Share With shadow_copy VFS
    24.1. smb.conf for Winbind Setup
    25.1. Script to Enforce Single Resource Logon
    30.1. VFS CAP
    34.1. Elastic smb.conf File
    34.2. CDROM Server smb-cdserver.conf file
    34.3. Master smb.conf File Global Section
    34.4. MERLIN smb-merlin.conf File Share Section
    34.5. SAURON smb-sauron.conf File Share Section
    38.1. smb.conf with [tmp] Share
    38.2. Configuration for Allowing Connections Only from a Certain Subnet
    38.3. Configuration for Allowing Connections from a Certain Subnet and localhost
    44.1. Minimal Profile Share
       Next
       About the Cover Artwork
    diff --git a/docs/htmldocs/Samba3-HOWTO/install.html b/docs/htmldocs/Samba3-HOWTO/install.html index 6532bad8f3..95d4dbae40 100644 --- a/docs/htmldocs/Samba3-HOWTO/install.html +++ b/docs/htmldocs/Samba3-HOWTO/install.html @@ -1,32 +1,32 @@ -Chapter 1. How to Install and Test SAMBA
    Chapter 1. How to Install and Test SAMBA
    Prev Part I. General Installation Next

    Chapter 1. How to Install and Test SAMBA

    Andrew Tridgell

    Samba Team

    Jelmer R. Vernooij

    The Samba Team

    John H. Terpstra

    Samba Team

    Karl Auer

    Samba Team

    Dan Shearer

    Samba Team

    Table of Contents

    Obtaining and Installing Samba
    Configuring Samba (smb.conf)
    Configuration File Syntax
    TDB Database File Information
    Starting Samba
    Example Configuration
    SWAT
    List Shares Available on the Server
    Connect with a UNIX Client
    Connect from a Remote SMB Client
    What If Things Don't Work?
    Still Stuck?
    Common Errors
    Large Number of smbd Processes
    Error Message: open_oplock_ipc
    “The network name cannot be found”

    Obtaining and Installing Samba

    - +Chapter 1. How to Install and Test SAMBA

    Chapter 1. How to Install and Test SAMBA
    Prev Part I. General Installation Next

    Chapter 1. How to Install and Test SAMBA

    Andrew Tridgell

    Samba Team

    Jelmer R. Vernooij

    The Samba Team

    John H. Terpstra

    Samba Team

    Karl Auer

    Samba Team

    Dan Shearer

    Samba Team

    Table of Contents

    Obtaining and Installing Samba
    Configuring Samba (smb.conf)
    Configuration File Syntax
    TDB Database File Information
    Starting Samba
    Example Configuration
    SWAT
    List Shares Available on the Server
    Connect with a UNIX Client
    Connect from a Remote SMB Client
    What If Things Don't Work?
    Still Stuck?
    Common Errors
    Large Number of smbd Processes
    Error Message: open_oplock_ipc
    “The network name cannot be found”

    Obtaining and Installing Samba

    + Binary packages of Samba are included in almost any Linux or UNIX distribution. There are also some packages available at the Samba home page. Refer to the manual of your operating system for details on installing packages for your specific operating system.

    - - If you need to compile Samba from source, check How to Compile Samba. -

    Configuring Samba (smb.conf)

    - - + + If you need to compile Samba from source, check How to Compile Samba. +

    Configuring Samba (smb.conf)

    + + Samba's configuration is stored in the smb.conf file, which usually resides in /etc/samba/smb.conf or /usr/local/samba/lib/smb.conf. You can either edit this file yourself or do it using one of the many graphical tools that are available, such as the Web-based interface SWAT, that is included with Samba. -

    Configuration File Syntax

    - +

    Configuration File Syntax

    + The smb.conf file uses the same syntax as the various old .ini files in Windows 3.1: Each file consists of various sections, which are started by putting the section name between brackets ([]) on a new line. Each contains zero or more key/value pairs separated by an equality sign (=). The file is just a plaintext file, so you can open and edit it with your favorite editing tool.

    - - - - - - + + + + + + Each section in the smb.conf file represents either a share or a meta-service on the Samba server. The section [global] is special, since it contains settings that apply to the whole Samba server. Samba supports a number of meta-services, each of which serves its own purpose. For example, the @@ -35,12 +35,12 @@ and that specifies the location of the intermediate spool directory into which print jobs are received from Windows clients prior to being dispatched to the UNIX/Linux print spooler.

    - - - - - - + + + + + + The printers meta-service will cause every printer that is either specified in a printcap file, via the lpstat, or via the CUPS API, to be published as a shared print queue. The printers stanza in the smb.conf file can @@ -49,20 +49,20 @@ available as Windows print queues. If a comment parameter is specified, the value of it will be displayed as part of the printer name in Windows Explorer browse lists.

    - + Each section of the smb.conf file that specifies a share, or a meta-service, is called a stanza. The global stanza specifies settings that affect all the other stanzas in the smb.conf file. Configuration parameters are documented in the smb.conf man page. Some parameters can be used only in the global stanza, some only in share or meta-service stanzas, and some can be used globally or just within a share or meta-service stanza.

    - + A minimal smb.conf contains a very minimal smb.conf. - -

    Example 1.1. A minimal smb.conf

    [global]
    workgroup = WKG
    netbios name = MYNAME
    [share1]
    path = /tmp
    [share2]
    path = /my_shared_folder
    comment = Some random files

    TDB Database File Information

    + +

    Example 1.1. A minimal smb.conf

    [global]
    workgroup = WKG
    netbios name = MYNAME
    [share1]
    path = /tmp
    [share2]
    path = /my_shared_folder
    comment = Some random files

    TDB Database File Information

    This section contains brief descriptions of the databases that are used by Samba-3.

    - + The directory in which Samba stores the tdb files is determined by compile-time directives. Samba-3 stores tdb files in two locations. The best way to determine these locations is to execute the following command: @@ -80,7 +80,7 @@ Therefore the remaining control files will, in the example shown, be stored in the /var/lib/samba directory.

    - + The persistent tdb files are described in the Persistent TDB File Descriptions table. All persistent tdb files should be regularly backed up. Use the tdbbackup utility to backup the tdb files. All persistent tdb files must be @@ -106,27 +106,27 @@ information so that clients that have temporarily disconnected can reconnect without needing to renegotiate the connection setup process.

    		no
    sessionid

    Temporary cache for miscellaneous session information and for utmp handling.

    		no
    unexpected

    Stores packets received for which no process is actively listening.

    		no
    winbindd_cache

    Cache of Identity information received from an NT4 domain or from ADS. Includes user - lists, etc.

    		yes

    Starting Samba

    - + lists, etc.

    yes

    Starting Samba

    + Samba essentially consists of two or three daemons. A daemon is a UNIX application that runs in the background and provides services. An example of a service is the Apache Web server for which the daemon is called httpd. In the case of Samba there are three daemons, two of which are needed as a minimum.

    The Samba server is made up of the following daemons:

    nmbd

    - - + + This daemon handles all name registration and resolution requests. It is the primary vehicle involved in network browsing. It handles all UDP-based protocols. The nmbd daemon should be the first command started as part of the Samba startup process.

    smbd

    - - + + This daemon handles all TCP/IP-based connection services for file- and print-based operations. It also manages local authentication. It should be started immediately following the startup of nmbd.

    winbindd

    - - + + This daemon should be started when Samba is a member of a Windows NT4 or ADS domain. It is also needed when Samba has trust relationships with another domain. The winbindd daemon will check the smb.conf file for the presence of the idmap uid and idmap gid @@ -134,36 +134,36 @@ for UID and GID allocation. If these parameters are not specified, winbindd will start but it will not be able to allocate UIDs or GIDs.

    - + When Samba has been packaged by an operating system vendor, the startup process is typically a custom feature of its integration into the platform as a whole. Please refer to your operating system platform administration manuals for specific information pertaining to correct management of Samba startup. -

    Example Configuration

    - - - - - +

    Example Configuration

    + + + + + There are sample configuration files in the examples subdirectory in the source code distribution tarball package. It is suggested you read them carefully so you can see how the options go together in practice. See the man page for all the options. It might be worthwhile to start out with the smb.conf.default configuration file and adapt it to your needs. It contains plenty of comments.

    - + The simplest useful configuration file would contain something like that shown in Another simple smb.conf File. - -

    Example 1.2. Another simple smb.conf File

    [global]
    workgroup = MIDEARTH
    [homes]
    guest ok = no
    read only = no

    - - - - + +

    Example 1.2. Another simple smb.conf File

    [global]
    workgroup = MIDEARTH
    [homes]
    guest ok = no
    read only = no

    + + + + This will allow connections by anyone with an account on the server, using either their login name or homes as the service name. (Note: The workgroup that Samba should appear in must also be set. The default workgroup name is WORKGROUP.)

    - + Make sure you put the smb.conf file in the correct place. Note, the correct location of this file depends on how the binary files were built. You can discover the correct location by executing from the directory that contains the smbd command file: @@ -171,13 +171,13 @@ root# smbd -b | grep smb.conf

    - + For more information about security settings for the [homes] share, please refer to Securing Samba. -

    Test Your Config File with testparm

    - - - +

    Test Your Config File with testparm

    + + + It's important to validate the contents of the smb.conf file using the testparm program. If testparm runs correctly, it will list the loaded services. If not, it will give an error message. Make sure it runs correctly and that the services look reasonable before proceeding. Enter the command: @@ -189,10 +189,10 @@

    Always run testparm again whenever the smb.conf file is changed!

    - - - - + + + + The smb.conf file is constantly checked by the Samba daemons smbd and every instance of itself that it spawns, nmbd and winbindd. It is good practice to keep this file as small as possible. Many administrators prefer to document Samba configuration settings @@ -205,8 +205,8 @@

    This administrative method makes it possible to maintain detailed configuration change records while at the same time keeping the working smb.conf file size to the minimum necessary. -

    SWAT

    - +

    SWAT

    + SWAT is a Web-based interface that can be used to facilitate the configuration of Samba. SWAT might not be available in the Samba package that shipped with your platform, but in a separate package. If it is necesaary to built SWAT please read the SWAT man page regarding compilation, installation, and @@ -221,7 +221,7 @@ machine leaves your connection open to password sniffing because passwords will be sent over the wire in the clear.

    More information about SWAT can be found in The Samba Web Administration Tool. -

    List Shares Available on the Server

    +

    List Shares Available on the Server

    To list shares that are available from the configured Samba server, execute the following command: 

    @@ -235,7 +235,7 @@
 	before it will list the shares. See the smbclient man page for details.
 	You can force it to list the shares without a password by adding the option
 	-N to the command line. 
-

    Connect with a UNIX Client

    +

    Connect with a UNIX Client

    Enter the following command: 

     $ smbclient  //yourhostname/aservice
@@ -244,7 +244,7 @@
 	file. Try your username if you just have a [homes] section in the smb.conf file.
    Example: If the UNIX host is called bambi and a valid login name
 	is fred, you would type:
     $ smbclient //bambi/fred
-

    Connect from a Remote SMB Client

    +

    Connect from a Remote SMB Client

    Now that Samba is working correctly locally, you can try to access it from other clients. Within a few minutes, the Samba host should be listed in the Network Neighborhood on all Windows clients of its subnet. Try browsing the server from another client or "mounting" it. @@ -265,7 +265,7 @@ be sent to the printer that owns the spoolservice that has been specified. 

    C:\> print filename
-

    What If Things Don't Work?

    +

    What If Things Don't Work?

    You might want to read The Samba Checklist. If you are still stuck, refer to Analyzing and Solving Samba Problems. Samba has been successfully installed at thousands of sites worldwide. It is unlikely that your particular problem is @@ -277,7 +277,7 @@ Simply choose from the first five chapters the network design that most closely matches site needs, then follow the simple step-by-step procedure to deploy it. Later, when you have a working network you may well want to refer back to this book for further insight into opportunities for improvement. -

    Still Stuck?

    +

    Still Stuck?

    The best advice under the stress of abject frustration is to cool down! That may be challenging of itself, but while you are angry or annoyed your ability to seek out a solution is somewhat undermined. A cool head clears the way to finding the answer you are looking for. Just remember, @@ -286,9 +286,9 @@

    Now that you have cooled down a bit, please refer to the Samba Checklist for a process that can be followed to identify the cause of your problem. -

    Common Errors

    +

    Common Errors

    The following questions and issues are raised repeatedly on the Samba mailing list. -

    Large Number of smbd Processes

    +

    Large Number of smbd Processes

    Samba consists of three core programs: nmbd, smbd, and winbindd. nmbd is the name server message daemon, smbd is the server message daemon, and winbindd is the daemon that handles communication with domain controllers.

    @@ -301,14 +301,14 @@ The following questions and issues are raised repeatedly on the Samba mailing li

    winbindd will run as one or two daemons, depending on whether or not it is being run in split mode (in which case there will be two instances). -

    Error Message: open_oplock_ipc

    +

    Error Message: open_oplock_ipc

    An error message is observed in the log files when smbd is started: “open_oplock_ipc: Failed to get local UDP socket for address 100007f. Error was Cannot assign requested.”

    Your loopback device isn't working correctly. Make sure it is configured correctly. The loopback device is an internal (virtual) network device with the IP address 127.0.0.1. Read your OS documentation for details on how to configure the loopback on your system. -

    “The network name cannot be found”

    +

    “The network name cannot be found”

    This error can be caused by one of these misconfigurations:

    • You specified a nonexisting path for the share in smb.conf.

    • The user you are trying to access the share with does not diff --git a/docs/htmldocs/Samba3-HOWTO/integrate-ms-networks.html b/docs/htmldocs/Samba3-HOWTO/integrate-ms-networks.html index 04ab8a2408..16c732d1ef 100644 --- a/docs/htmldocs/Samba3-HOWTO/integrate-ms-networks.html +++ b/docs/htmldocs/Samba3-HOWTO/integrate-ms-networks.html @@ -1,18 +1,18 @@ -Chapter 29. Integrating MS Windows Networks with Samba

      Chapter 29. Integrating MS Windows Networks with Samba
      Prev Part III. Advanced Configuration Next

      Chapter 29. Integrating MS Windows Networks with Samba

      John H. Terpstra

      Samba Team

      (Jan 01 2001)

      Table of Contents

      Features and Benefits
      Background Information
      Name Resolution in a Pure UNIX/Linux World
      /etc/hosts
      /etc/resolv.conf
      /etc/host.conf
      /etc/nsswitch.conf
      Name Resolution as Used within MS Windows Networking
      The NetBIOS Name Cache
      The LMHOSTS File
      HOSTS File
      DNS Lookup
      WINS Lookup
      Common Errors
      Pinging Works Only One Way
      Very Slow Network Connections
      Samba Server Name-Change Problem

      - +Chapter 29. Integrating MS Windows Networks with Samba

      Chapter 29. Integrating MS Windows Networks with Samba
      Prev Part III. Advanced Configuration Next

      Chapter 29. Integrating MS Windows Networks with Samba

      John H. Terpstra

      Samba Team

      (Jan 01 2001)

      Table of Contents

      Features and Benefits
      Background Information
      Name Resolution in a Pure UNIX/Linux World
      /etc/hosts
      /etc/resolv.conf
      /etc/host.conf
      /etc/nsswitch.conf
      Name Resolution as Used within MS Windows Networking
      The NetBIOS Name Cache
      The LMHOSTS File
      HOSTS File
      DNS Lookup
      WINS Lookup
      Common Errors
      Pinging Works Only One Way
      Very Slow Network Connections
      Samba Server Name-Change Problem

      + This chapter deals with NetBIOS over TCP/IP name to IP address resolution. If your MS Windows clients are not configured to use NetBIOS over TCP/IP, then this section does not apply to your installation. If your installation involves the use of NetBIOS over TCP/IP, then this chapter may help you to resolve networking problems.

      Note

      - - + + NetBIOS over TCP/IP has nothing to do with NetBEUI. NetBEUI is NetBIOS over Logical Link Control (LLC). On modern networks it is highly advised to not run NetBEUI at all. Note also that there is no such thing as NetBEUI over TCP/IP the existence of such a protocol is a complete and utter misapprehension. -

      Features and Benefits

      +

      Features and Benefits

      Many MS Windows network administrators have never been exposed to basic TCP/IP networking as it is implemented in a UNIX/Linux operating system. Likewise, many UNIX and Linux administrators have not been exposed to the intricacies of MS Windows TCP/IP-based @@ -20,12 +20,12 @@ networking (and may have no desire to be, either).

      This chapter gives a short introduction to the basics of how a name can be resolved to its IP address for each operating system environment. -

      Background Information

      - - - - - +

      Background Information

      + + + + + Since the introduction of MS Windows 2000, it is possible to run MS Windows networking without the use of NetBIOS over TCP/IP. NetBIOS over TCP/IP uses UDP port 137 for NetBIOS name resolution and uses TCP port 139 for NetBIOS session services. When NetBIOS over @@ -36,43 +36,43 @@ When using Windows 2000 or later clients, if NetBIOS over TCP/IP is not disabled the client will use UDP port 137 (NetBIOS Name Service, also known as the Windows Internet Name Service, or WINS), TCP port 139, and TCP port 445 (for actual file and print traffic).

      - - - - - - + + + + + + When NetBIOS over TCP/IP is disabled, the use of DNS is essential. Most installations that disable NetBIOS over TCP/IP today use MS Active Directory Service (ADS). ADS requires - dynamic DNS with Service Resource -Records (SRV RR) and with Incremental Zone Transfers (IXFR). + dynamic DNS with Service Resource +Records (SRV RR) and with Incremental Zone Transfers (IXFR). Use of DHCP with ADS is recommended as a further means of maintaining central control over the client workstation network configuration. -

      Name Resolution in a Pure UNIX/Linux World

      +

      Name Resolution in a Pure UNIX/Linux World

      The key configuration files covered in this section are: -

      • /etc/hosts

      • /etc/resolv.conf

      • /etc/host.conf

      • /etc/nsswitch.conf

      /etc/hosts

      +

      • /etc/hosts

      • /etc/resolv.conf

      • /etc/host.conf

      • /etc/nsswitch.conf

      /etc/hosts

      This file contains a static list of IP addresses and names. 

       127.0.0.1	localhost localhost.localdomain
 192.168.1.1	bigbox.quenya.org	bigbox	alias4box

      - - + + The purpose of /etc/hosts is to provide a name resolution mechanism so users do not need to remember IP addresses.

      - - - + + + Network packets that are sent over the physical network transport layer communicate not via IP addresses but rather using the Media Access Control address, or MAC address. IP addresses are currently 32 bits in length and are typically presented as four decimal numbers that are separated by a dot (or period) for example, 168.192.1.1.

      - + MAC addresses use 48 bits (or 6 bytes) and are typically represented as two-digit hexadecimal numbers separated by colons: 40:8e:0a:12:34:56.

      @@ -84,14 +84,14 @@ interface, the assignment of an IP address makes sense from a network management address can be assigned per MAC address. One address must be the primary IP address this is the address that will be returned in the Address Resolution Protocol (ARP) reply.

      - + When a user or a process wants to communicate with another machine, the protocol implementation ensures that the “machine name” or “host name” is resolved to an IP address in a manner that is controlled by the TCP/IP configuration control files. The file /etc/hosts is one such file.

      - + When the IP address of the destination interface has been determined, a protocol called ARP/RARP is used to identify the MAC address of the target interface. ARP is a broadcast-oriented method that uses User Datagram Protocol (UDP) to send a request to all interfaces on the local network segment using the all 1s MAC address. @@ -99,7 +99,7 @@ Network interfaces are programmed to respond to two MAC addresses only; their ow address ff:ff:ff:ff:ff:ff. The reply packet from an ARP request will contain the MAC address and the primary IP address for each interface.

      - + The /etc/hosts file is foundational to all UNIX/Linux TCP/IP installations and as a minimum will contain the localhost and local network interface IP addresses and the @@ -107,7 +107,7 @@ primary names by which they are known within the local machine. This file helps to prime the pump so a basic level of name resolution can exist before any other method of name resolution becomes available. -

      /etc/resolv.conf

      +

      /etc/resolv.conf

      This file tells the name resolution libraries:

      • The name of the domain to which the machine belongs. @@ -117,8 +117,8 @@ This file tells the name resolution libraries:

      • The name or IP address of available domain name servers that may be asked to perform name-to-address translation lookups. -

      /etc/host.conf

      - +

    /etc/host.conf

    + /etc/host.conf is the primary means by which the setting in /etc/resolv.conf may be effected. It is a critical configuration file. This file controls the order by which name resolution may proceed. The typical structure is: @@ -127,8 +127,8 @@ order hosts,bind multi on

    Both addresses should be returned. Please refer to the man page for host.conf for further details. -

    /etc/nsswitch.conf

    - +

    /etc/nsswitch.conf

    + This file controls the actual name resolution targets. The file typically has resolver object specifications as follows: 

    @@ -160,11 +160,11 @@ It should be noted that unless a network request/message must be
 sent, TCP/IP networks are silent. All TCP/IP communications assume a 
 principal of speaking only when necessary.
 
    
-
-
-
-
-
+
+
+
+
+
 Starting with version 2.2.0, Samba has Linux support for extensions to 
 the name service switch infrastructure so Linux clients will 
 be able to obtain resolution of MS Windows NetBIOS names to IP 
@@ -177,11 +177,11 @@ the /etc/nsswitch.conf file. At this point, it
 will be possible to ping any MS Windows machine by its NetBIOS 
 machine name, as long as that machine is within the workgroup to 
 which both the Samba machine and the MS Windows machine belong.
-

    Name Resolution as Used within MS Windows Networking

    - - - - +

    Name Resolution as Used within MS Windows Networking

    + + + + MS Windows networking is predicated on the name each machine is given. This name is known variously (and inconsistently) as the “computer name,” “machine name,” “networking name,” “NetBIOS name,” or “SMB name.” All terms mean the same thing with the @@ -195,16 +195,16 @@ registered for each service type that is provided by the client/server. Unique NetBIOS names and group names tables list typical NetBIOS name/service type registrations.

    Table 29.1. Unique NetBIOS Names

    MACHINENAME<00>Server Service is running on MACHINENAME
    MACHINENAME<03>Generic machine name (NetBIOS name)
    MACHINENAME<20>LanMan server service is running on MACHINENAME
    WORKGROUP<1b>Domain master browser

    Table 29.2. Group Names

    WORKGROUP<03>Generic name registered by all members of WORKGROUP
    WORKGROUP<1c>Domain cntrollers/netlogon servers
    WORKGROUP<1d>Local master browsers
    WORKGROUP<1e>Browser election service

    - + It should be noted that all NetBIOS machines register their own names as per Unique NetBIOS names and group names. This is in vast contrast to TCP/IP installations where the system administrator traditionally determines in the /etc/hosts or in the DNS database what names are associated with each IP address.

    - - - + + + One further point of clarification should be noted. The /etc/hosts file and the DNS records do not provide the NetBIOS name information that MS Windows clients depend on to locate the type of service that may @@ -216,8 +216,8 @@ registered the name type *<1C>. A logon request is then sent to each IP address that is returned in the enumerated list of IP addresses. Whichever machine first replies, it then ends up providing the logon services.

    - - + + The name “workgroup” or “domain” really can be confusing, since these have the added significance of indicating what is the security architecture of the MS Windows network. The term “workgroup” indicates @@ -230,14 +230,14 @@ will simply opt to have no security at all. It is possible to have user-level security in a workgroup environment, thus requiring the use of a username and a matching password.

    - - - - - - - - + + + + + + + + MS Windows networking is thus predetermined to use machine names for all local and remote machine message passing. The protocol used is called Server Message Block (SMB), and this is implemented using @@ -252,10 +252,10 @@ NBT or NetBT, the NetBIOS over TCP/IP. MS Windows machines use a complex array of name resolution mechanisms. Since we are primarily concerned with TCP/IP, this demonstration is limited to this area. -

    The NetBIOS Name Cache

    - - - +

    The NetBIOS Name Cache

    + + + All MS Windows machines employ an in-memory buffer in which is stored the NetBIOS names and IP addresses for all external machines that machine has communicated with over the @@ -263,7 +263,7 @@ past 10 to 15 minutes. It is more efficient to obtain an IP address for a machine from the local cache than it is to go through all the configured name resolution mechanisms.

    - + If a machine whose name is in the local name cache is shut down before the name is expired and flushed from the cache, then an attempt to exchange a message with that machine will be subject @@ -271,14 +271,14 @@ to timeout delays. Its name is in the cache, so a name resolution lookup will succeed, but the machine cannot respond. This can be frustrating for users but is a characteristic of the protocol.

    - - - + + + The MS Windows utility that allows examination of the NetBIOS name cache is called “nbtstat.” The Samba equivalent is called nmblookup. -

    The LMHOSTS File

    - +

    The LMHOSTS File

    + This file is usually located in MS Windows NT 4.0 or Windows 200x/XP in the directory %SystemRoot%\SYSTEM32\DRIVERS\ETC and contains the IP address and the machine name in matched pairs. The LMHOSTS file @@ -363,15 +363,15 @@ It typically looks like this: # so keeping the number of comments to a minimum will improve performance. # Therefore it is not advisable to simply add lmhosts file entries onto the # end of this file. -

    HOSTS File

    +

    HOSTS File

    This file is usually located in MS Windows NT 4.0 or Windows 200x/XP in the directory %SystemRoot%\SYSTEM32\DRIVERS\ETC and contains the IP address and the IP hostname in matched pairs. It can be used by the name resolution infrastructure in MS Windows, depending on how the TCP/IP environment is configured. This file is in every way the equivalent of the UNIX/Linux /etc/hosts file. -

    DNS Lookup

    - +

    DNS Lookup

    + This capability is configured in the TCP/IP setup area in the network configuration facility. If enabled, an elaborate name resolution sequence is followed, the precise nature of which is dependent on how the NetBIOS @@ -382,10 +382,10 @@ cache. If that fails, then DNS, HOSTS, and LMHOSTS are checked. If set to Node Type 8, then a NetBIOS Unicast (over UDP Unicast) is sent to the WINS server to obtain a lookup before DNS, HOSTS, LMHOSTS, or broadcast lookup is used. -

    WINS Lookup

    - - - +

    WINS Lookup

    + + + A WINS (Windows Internet Name Server) service is the equivalent of the rfc1001/1002 specified NBNS (NetBIOS Name Server). A WINS server stores the names and IP addresses that are registered by a Windows client @@ -393,19 +393,19 @@ if the TCP/IP setup has been given at least one WINS server IP address.

    To configure Samba to be a WINS server, the following parameter needs to be added to the smb.conf file: -

    wins support = Yes

    - +

    wins support = Yes

    + To configure Samba to use a WINS server, the following parameters are needed in the smb.conf file: -

    wins support = No
    wins server = xxx.xxx.xxx.xxx

    +

    wins support = No
    wins server = xxx.xxx.xxx.xxx

    where xxx.xxx.xxx.xxx is the IP address of the WINS server.

    For information about setting up Samba as a WINS server, read -Network Browsing.

    Common Errors

    +Network Browsing.

    Common Errors

    TCP/IP network configuration problems find every network administrator sooner or later. The cause can be anything from keyboard mishaps to forgetfulness to simple mistakes to carelessness. Of course, no one is ever deliberately careless! -

    Pinging Works Only One Way

    +

    Pinging Works Only One Way

    “I can ping my Samba server from Windows, but I cannot ping my Windows machine from the Samba server.”

    @@ -415,10 +415,10 @@ carelessness. Of course, no one is ever deliberately careless!

    Due to inconsistent netmasks, the Windows machine was on network 192.168.1.0/24, while the Samba server was on network 192.168.1.128/25 logically a different network. -

    Very Slow Network Connections

    +

    Very Slow Network Connections

    A common cause of slow network response includes:

    • Client is configured to use DNS and the DNS server is down.

    • Client is configured to use remote DNS server, but the - remote connection is down.

    • Client is configured to use a WINS server, but there is no WINS server.

    • Client is not configured to use a WINS server, but there is a WINS server.

    • Firewall is filtering out DNS or WINS traffic.

    Samba Server Name-Change Problem

    + remote connection is down.

  • Client is configured to use a WINS server, but there is no WINS server.

  • Client is not configured to use a WINS server, but there is a WINS server.

  • Firewall is filtering out DNS or WINS traffic.

    • Samba Server Name-Change Problem

    “The name of the Samba server was changed, Samba was restarted, and now the Samba server cannot be pinged by its new name from an MS Windows NT4 workstation, but it does still respond to pinging using the old name. Why?” diff --git a/docs/htmldocs/Samba3-HOWTO/introduction.html b/docs/htmldocs/Samba3-HOWTO/introduction.html index b25548828a..bd5092d203 100644 --- a/docs/htmldocs/Samba3-HOWTO/introduction.html +++ b/docs/htmldocs/Samba3-HOWTO/introduction.html @@ -1,5 +1,5 @@ -Part I. General Installation

    Part I. General Installation
    Prev   Next

    Part I. General Installation

    Preparing Samba for Configuration

    +Part I. General Installation

    Part I. General Installation
    Prev   Next

    Part I. General Installation

    Preparing Samba for Configuration

    This section of the Samba-HOWTO-Collection contains general info on how to install Samba and how to configure the parts of Samba you will most likely need. PLEASE read this. -

    Table of Contents

    1. How to Install and Test SAMBA
    Obtaining and Installing Samba
    Configuring Samba (smb.conf)
    Configuration File Syntax
    TDB Database File Information
    Starting Samba
    Example Configuration
    SWAT
    List Shares Available on the Server
    Connect with a UNIX Client
    Connect from a Remote SMB Client
    What If Things Don't Work?
    Still Stuck?
    Common Errors
    Large Number of smbd Processes
    Error Message: open_oplock_ipc
    “The network name cannot be found”
    2. Fast Start: Cure for Impatience
    Features and Benefits
    Description of Example Sites
    Worked Examples
    Standalone Server
    Domain Member Server
    Domain Controller
    Prev   Next
    Introduction Home Chapter 1. How to Install and Test SAMBA
    +

    Table of Contents

    1. How to Install and Test SAMBA
    Obtaining and Installing Samba
    Configuring Samba (smb.conf)
    Configuration File Syntax
    TDB Database File Information
    Starting Samba
    Example Configuration
    SWAT
    List Shares Available on the Server
    Connect with a UNIX Client
    Connect from a Remote SMB Client
    What If Things Don't Work?
    Still Stuck?
    Common Errors
    Large Number of smbd Processes
    Error Message: open_oplock_ipc
    “The network name cannot be found”
    2. Fast Start: Cure for Impatience
    Features and Benefits
    Description of Example Sites
    Worked Examples
    Standalone Server
    Domain Member Server
    Domain Controller
    Prev   Next
    Introduction Home Chapter 1. How to Install and Test SAMBA
    diff --git a/docs/htmldocs/Samba3-HOWTO/ix01.html b/docs/htmldocs/Samba3-HOWTO/ix01.html index 2c40c6d4e3..4662743721 100644 --- a/docs/htmldocs/Samba3-HOWTO/ix01.html +++ b/docs/htmldocs/Samba3-HOWTO/ix01.html @@ -1,9 +1,9 @@ -Index
    Index
    Prev   

    Index

    Symbols

    "Printers" folder, Caveats to Be Considered, Installing the PostScript Driver on a Client, Manual Driver Installation in 15 Steps
    $, Manual Creation of Machine Trust Accounts
    %i macro, Multiple Virtual Server Personalities
    %L, Multiple Virtual Server Personalities
    %PDF, MIME Types and CUPS Filters
    %SystemRoot%\System32\config, MS Windows NT4-style Domain Control
    ../source/nsswitch, Configure Winbind and PAM
    .ai, MIME Types and CUPS Filters
    .AppleDouble, netatalk
    .eps, MIME Types and CUPS Filters
    .pdf, MIME Types and CUPS Filters
    .PDS extension, Windows NT4 Workstation
    .profiles, Windows 9x/Me User Profiles
    .ps, MIME Types and CUPS Filters
    .recycle, recycle
    /bin/false, Example Configuration, User Rights and Privileges
    /dev/null, User Rights and Privileges
    /dev/shadowvol, Shadow Copy Setup
    /etc/cups/, MIME Types and CUPS Filters
    /etc/cups/mime.convs, Raw Print Serving: Vendor Drivers on Windows Clients, Explicitly Enable “raw” Printing for application/octet-stream, MIME Type Conversion Rules, application/octet-stream Printing
    /etc/cups/mime.types, Raw Print Serving: Vendor Drivers on Windows Clients, Explicitly Enable “raw” Printing for application/octet-stream, application/octet-stream Printing
    /etc/fstab, Shadow Copy Setup
    /etc/group, Share-Level Security, Discussion, Nested Groups: Adding Windows Domain Groups to Windows Local Groups, Sample smb.conf Add Group Script, Domain Member Server or Domain Member Client, The [global] Section, Features and Benefits, HPUX
    /etc/groups, Anatomy of /etc/pam.d Entries
    /etc/host.conf, Name Resolution in a Pure UNIX/Linux World, /etc/host.conf
    /etc/hosts, Configure /etc/krb5.conf, How Browsing Functions, Name Resolution in a Pure UNIX/Linux World, /etc/hosts, Name Resolution as Used within MS Windows Networking, The Tests
    /etc/hosts>, /etc/hosts
    /etc/inetd.conf, Linux/FreeBSD-Specific PAM Configuration, Starting from inetd.conf
    /etc/init.d/samba, Joining an NT4-type Domain with Samba-3, Linux
    /etc/init.d/samba.server, Solaris
    /etc/init.d/smb, Linux
    /etc/krb5.conf, Configure /etc/krb5.conf, Possible Errors, ADS Domains, IDMAP Storage in LDAP Using Winbind
    /etc/ldap.conf, IDMAP Storage in LDAP Using Winbind, IDMAP and NSS Using LDAP from ADS with RFC2307bis Schema Extension
    /etc/logingroup, HPUX
    /etc/mime.conv, Central Print Serving
    /etc/mime.types, Central Print Serving
    /etc/nsswitch.conf, Domain Member Server or Domain Member Client, NT4-Style Domains (Includes Samba Domains), IDMAP_RID with Winbind, IDMAP and NSS Using LDAP from ADS with RFC2307bis Schema Extension, Name Service Switch, Configure nsswitch.conf and the Winbind Libraries on Linux and Solaris, Name Resolution in a Pure UNIX/Linux World, /etc/nsswitch.conf
    /etc/openldap/slapd.conf, The Primary Domain Controller
    /etc/openldap/sldap.conf, Accounts and Groups Management
    /etc/pam.conf, Solaris-Specific Configuration, Features and Benefits, Technical Discussion, Anatomy of /etc/pam.d Entries
    /etc/pam.d, Requirements, Testing Things Out, Configure Winbind and PAM, Features and Benefits
    /etc/pam.d/, Pluggable Authentication Modules, Technical Discussion
    /etc/pam.d/ftp, Linux/FreeBSD-Specific PAM Configuration
    /etc/pam.d/login, Linux/FreeBSD-Specific PAM Configuration
    /etc/pam.d/samba, Linux/FreeBSD-Specific PAM Configuration
    /etc/passwd, Share-Level Security, Example Configuration, “$” Cannot Be Included in Machine Name, MS Windows Workstation/Server Machine Trust Accounts, Manual Creation of Machine Trust Accounts, Windows 200x/XP Professional Client, Adding Machine to Domain Fails, Background, Reference Documentation Server, Central Print Serving, Backward Compatibility Account Storage Systems, Plaintext, Schema and Relationship to the RFC 2307 posixAccount, Applicable Only to Versions Earlier than 3.0.11, Domain Member Server or Domain Member Client, Samba as the Trusted Domain, Features and Benefits, Starting and Testing the winbindd Daemon, Features and Benefits
    /etc/printcap, Basic CUPS Support Configuration
    /etc/resolv.conf, Name Resolution in a Pure UNIX/Linux World, Assumptions, The Tests
    /etc/samba, Multiple Virtual Server Personalities, Multiple Virtual Server Hosting, The Tests
    /etc/samba/scripts, Managing Nest Groups on Workstations from the Samba Server
    /etc/samba/secrets.tdb, Joining an NT4-type Domain with Samba-3
    /etc/samba/smb.conf, Configuring Samba (smb.conf)
    /etc/samba/smbpasswd, Plaintext
    /etc/samba/smbusers, User Mapping
    /etc/shadow, Background, Backward Compatibility Account Storage Systems
    /etc/smbpasswd, Plaintext
    /etc/ssl/certs/slapd.pem, LDAP Configuration Notes
    /etc/xinetd.d, Linux/FreeBSD-Specific PAM Configuration
    /etc/xinetd.d/telnet, Linux/FreeBSD-Specific PAM Configuration
    /export, Reference Documentation Server
    /lib/libnss_example.so, Name Service Switch
    /lib/libnss_files.so, Name Service Switch
    /lib/security, Configure Winbind and PAM, PAM Configuration Syntax
    /lib/security/, Pluggable Authentication Modules
    /opt/samba/bin, Locating the SWAT File
    /tmp, File and Directory Access Control
    /usr/bin/openssl, Securing SWAT through SSL
    /usr/lib/samba/vfs, Discussion
    /usr/lib/security, NSS Winbind on AIX, Configure Winbind and PAM
    /usr/lib/security/methods.cfg, NSS Winbind on AIX
    /usr/local/lib, Configure nsswitch.conf and the Winbind Libraries on Linux and Solaris
    /usr/local/samba, Starting and Testing the winbindd Daemon
    /usr/local/samba/bin, Linux, Solaris, Locating the SWAT File
    /usr/local/samba/lib, The Tests
    /usr/local/samba/lib/vfs, Discussion
    /usr/local/samba/private/secrets.tdb, Joining an NT4-type Domain with Samba-3
    /usr/local/samba/swat, Enabling SWAT for Use
    /usr/local/samba/var, Access Controls on Shares, Assumptions
    /usr/local/samba/var/locks, Static WINS Entries
    /usr/sbin, Locating the SWAT File, Enabling SWAT for Use
    /usr/share/samba/swat, Enabling SWAT for Use
    /var/locks/*.tdb, Corrupt tdb Files
    /var/log/samba, Assumptions
    /var/run/samba, Static WINS Entries
    /var/spool/cups/, Autodeletion or Preservation of CUPS Spool Files
    /var/spool/samba, Central Print Serving, Autodeletion or Preservation of CUPS Spool Files
    250-user limit, tdbsam
    3.0.11, The Administrator Domain SID
    4,500 user accounts, tdbsam
    4294967295, Interdomain Trust Relationships
    8.3 file names, MS Windows NTFS Comparison with UNIX File Systems
    >Domain User Manager, Creating an NT4 Domain Trust
    \\%L\%U\.profiles, Windows 9x/Me User Profiles
    \\SERVER, Problem Resolution
    _kerberos.REALM.NAME, Configure /etc/krb5.conf
    _kerberos._udp, Notes
    _ldap._tcp, Notes
    _ldap._tcp.pdc._msdcs.quenya.org, NetBIOS Over TCP/IP Disabled

    , Configuration File Syntax, Example Configuration, Anonymous Read-Only Document Server, Anonymous Read-Write Document Server, Anonymous Print Server, Secure Read-Write File and Print Server, Example Configuration, Example: Engineering Office, The Primary Domain Controller, Backup Domain Controller, Example Configuration, Example Configuration, Example Configuration, Example Configuration, Example Configuration, Password Checking, Single Sign-On and Domain Security, Domain Control: Example Configuration, Example Configuration, Example PDC Configuration, LDAP Configuration Notes, Example Configuration, Manual Creation of Machine Trust Accounts, On-the-Fly Creation of Machine Trust Accounts, Samba Client, Joining an NT4-type Domain with Samba-3, Configure smb.conf, Configure /etc/krb5.conf, Sharing User ID Mappings between Samba Domain Members, Reference Documentation Server, Central Print Serving, Configuring Workgroup Browsing, Domain Browsing Configuration, Multiple Interfaces, Use of the Remote Announce Parameter, Use of the Remote Browse Sync Parameter, WINS Server Configuration, Name Resolution Order, Mapping Common UIDs/GIDs on Distributed Machines, Configuring Samba, Sample smb.conf Add Group Script, Managing Nest Groups on Workstations from the Samba Server, NT4-Style Domains (Includes Samba Domains), ADS Domains, IDMAP_RID with Winbind, IDMAP Storage in LDAP Using Winbind, IDMAP and NSS Using LDAP from ADS with RFC2307bis Schema Extension, Using the “net rpc rights” Utility, File, Directory, and Share Access Controls, Interaction with the Standard Samba “create mask” Parameters, Users Cannot Write to a Public Share, MS Word with Samba Changes Owner of File, Disabling Oplocks, Disabling Kernel Oplocks, Features and Benefits, Using Host-Based Protection, User-Based Protection, Using Interface Protection, Using IPC$ Share-Based Denials , Why Can Users Access Other Users' Home Directories?, Interdomain Trust Relationships, Features and Benefits, MSDFS UNIX Path Is Case-Critical, Simple Print Configuration, Rapid Configuration Validation, Extended Printing Configuration, Custom Print Commands, Creating the [print$] Share, Identifying Driver Files, Simple smb.conf Settings for CUPS, More Complex CUPS smb.conf Settings, From Windows Clients to a CUPS/Samba Print Server, Prepare Your smb.conf for cupsaddsmb, Discussion, Shadow Copy Setup, Features and Benefits, Configure smb.conf, Linux, Solaris-Specific Configuration, Remote Management from NoMachine.Com, NT4/200x User Profiles, Windows 9x/Me User Profiles, Mixed Windows Windows 9x/Me and NT4/200x User Profiles, Changing the Default Profile, The NetBIOS Name Cache, WINS Lookup, Basic Parameter Setting, Individual Implementations, Handling Large Directories, Advanced Configuration Techniques, Multiple Virtual Server Personalities, Multiple Virtual Server Hosting, IdMap LDAP Support, Assumptions, The Tests, Debug Levels, Debugging-Specific Operations, Windows 2000 Service Pack 2 (see SSO)
    backend, Domain Controller Types
    logon
    service, Essential Background Information

    A

    abbreviated keystrokes, TCP/IP Configuration
    aborting shutdown, Description of Privileges
    accept connections, Using Interface Protection
    access, User and Group Changes
    Access, Using the “net rpc rights” Utility
    access authentication, Mapping Common UIDs/GIDs on Distributed Machines
    access control, Features and Benefits, Single Sign-On and Domain Security, Background, Access Controls on Shares, Advanced Network Management
    Access Control, Domain Logon Configuration: Windows 9x/Me
    Access Control Entries (see ACE)
    Access Control List, File, Directory, and Share Access Controls
    access control needs, Server Share and Directory Layout
    access controls, Features and Benefits, Comments Regarding LDAP, The pdbedit Tool, Mapping Windows Groups to UNIX Groups, Features and Benefits, Protecting Directories and Files from Deletion
    Access Controls, Objectives
    access denied, Using IPC$ Share-Based Denials
    access policies, Domain Account Policy Managment
    access rights, Features and Benefits, Overview, Trust Relationship Background
    account, Example Configuration, Features and Benefits, Windows 200x/XP Professional Client, Anatomy of /etc/pam.d Entries
    backend, Features and Benefits
    database, Domain Security Mode (User-Level Security)
    backends, Features and Benefits
    account access controls, New Account Storage Systems
    account attributes, Primary Domain Controller
    account backends, Account Information Databases
    account containers, Initialize the LDAP Database
    account control block (see ACB)
    account control flags, Account Flags Management
    account controls, MS Windows Workstation/Server Machine Trust Accounts
    Account Controls, Managing Account/User Policies
    account database, Password Backends
    account deleted, Deleting Accounts
    account encode_bits, Account Flags Management
    account flag order, Account Flags Management
    Account Flags, Listing User and Machine Accounts
    account flags, Account Flags Management
    account import/export, The pdbedit Tool, Account Import/Export
    account information, MS Windows NT4-style Domain Control, MS Windows Workstation/Server Machine Trust Accounts, Schema and Relationship to the RFC 2307 posixAccount, UNIX and Windows User Management
    account information database, Mapping User Identifiers between MS Windows and UNIX
    account management, Primary Domain Controller
    account name, Domain Member Server or Domain Member Client, User Rights and Privileges, Samba as the Trusted Domain
    account policies, Preparing for Domain Control
    account policy, The pdbedit Tool
    account restrictions, Managing Account/User Policies
    account security, The pdbedit Tool
    account storage backends, Passdb Backends and Authentication
    account storage mechanisms, Account Information Databases
    account storage system, Account Information Databases
    Account Unknown, Nested Groups: Adding Windows Domain Groups to Windows Local Groups
    accountability, The pdbedit Tool
    accounts, Introduction
    ACL, User and Group Changes, Security and sambaSamAccount, Nested Groups: Adding Windows Domain Groups to Windows Local Groups, Description of Privileges, Features and Benefits, Printing Developments Since Samba-2.2, Introduction
    ACLs, File, Directory, and Share Access Controls, The Obsoleted [printer$] Section
    File System, File and Directory Access Control
    POSIX, File, Directory, and Share Access Controls, Features and Benefits
    share, Features and Benefits
    Windows, Features and Benefits
    ACLs on share, Windows 200x/XP
    ACLs on shares, Features and Benefits
    across network segments, NetBIOS over TCP/IP
    active directory, Features and Benefits, Features and Benefits, Single Sign-On and Domain Security, Preparing for Domain Control, Samba ADS Domain Control
    Active Directory, Active Directory Domain Control, Samba ADS Domain Membership, UNIX and Windows Group Management, Standalone Samba Server, Domain Member Server or Domain Member Client, IDMAP_RID with Winbind, Interdomain Trust Relationships
    Active Directory Server, Objectives
    AD4UNIX, Domain Member Server or Domain Member Client
    ADAM, IDMAP Storage in LDAP Using Winbind
    add a user account, Adding User Accounts
    add client machines, Using the “net rpc rights” Utility
    add domain users and groups to a local group, What Rights and Privileges Will Permit Windows Client Administration?
    add drivers, The [global] Section
    add machine script, On-the-Fly Creation of Machine Trust Accounts, Using the “net rpc rights” Utility, Changes in Behavior
    Add Printer Wizard, Features and Benefits, The [global] Section, Printing Developments Since Samba-2.2
    add printer wizard, Driver Upload Methods
    add user script, User Account Management, Changes in Behavior
    add/delete/change share, Description of Privileges
    adddriver, Installing Driver Files into [print$], Running rpcclient with adddriver, Specific Driver Name Flexibility, A Check of the rpcclient man Page, Troubleshooting Revisited
    additional driver, Additional Client Driver Installation
    additional privileges, Description of Privileges
    addmem, Nested Groups: Adding Windows Domain Groups to Windows Local Groups
    AddPrinterDriver(), A Check of the rpcclient man Page
    admincfg.exe, Configuring Windows for Workgroups Password Handling
    administrative actions, Using the “net rpc rights” Utility
    administrative duties, Overview
    administrative privileges, Nested Groups: Adding Windows Domain Groups to Windows Local Groups, Join the Samba Server to the PDC Domain
    administrative responsibilities, Trust Relationship Background
    administrative rights, Description of Privileges, What Rights and Privileges Will Permit Windows Client Administration?
    administrative rights and privileges, What Rights and Privileges Will Permit Windows Client Administration?
    Administrative Templates, MS Windows 200x/XP Professional Policies
    Administrator, Discussion, Important Administrative Information, Join the Samba Server to the PDC Domain
    administrator account, Windows 200x/XP Professional Client, Windows NT4 Client
    Administrator account, Create the Computer Account
    administrator password, Notes
    Administrator%password, Joining an NT4-type Domain with Samba-3
    Adobe, GDI on Windows, PostScript on UNIX, PostScript Drivers with No Major Problems, Even in Kernel -Mode, The Grand Unification Achieved
    Adobe driver, Windows CUPS PostScript Driver Versus Adobe Driver
    Adobe driver files, Recognizing Different Driver Files
    Adobe PostScript, Caveats to Be Considered, Adobe and CUPS PostScript Drivers for Windows Clients
    Adobe PostScript driver, Installing the PostScript Driver on a Client
    Adobe PPD, CUPS Print Drivers from Linuxprinting.org
    Adobe specifications, The Role of cupsomatic/foomatic
    ADS, ADS Security Mode (User-Level Security), Single Sign-On and Domain Security, Domain Controller Types, Features and Benefits, MS Windows Workstation/Server Machine Trust Accounts, Domain Member Server, Joining an NT4-type Domain with Samba-3, Configure smb.conf, Configure /etc/krb5.conf, Create the Computer Account, Testing Server Setup, Network Browsing, TCP/IP without NetBIOS, DNS and Active Directory, Cross-Subnet Browsing, Account Information Databases, New Account Storage Systems, Comments Regarding LDAP, Accounts and Groups Management, Administrative Tasks and Methods, Domain Member Server or Domain Member Client, Primary Domain Controller, IDMAP Storage in LDAP Using Winbind, User Rights and Privileges, Interdomain Trust Relationships, Features and Benefits, Trust Relationship Background, NT4-Style Domain Trusts with Windows 2000, Printing Developments Since Samba-2.2, Features and Benefits, Result Caching, Features and Benefits, MS Windows 200x/XP Professional Policies, Managing Account/User Policies, System Startup and Logon Processing Overview, MS Windows 200x/XP, PAM-Based Distributed Authentication, Features and Benefits, Background Information, New Features in Samba-3.0.x, Passdb Backends and Authentication, Objectives, Features and Benefits (see Active Directory)
    ADS DC, Configure smb.conf
    ADS domain, Domain Member Server or Domain Member Client, ADS Domains
    ADS domain members, Identity Mapping (IDMAP)
    ADS manager, Create the Computer Account
    ADS schema, Primary Domain Controller
    Advanced TCP/IP configuration, MS Windows XP Professional
    advantages, Objectives
    affect users, Creating and Managing System Policies
    affordable power, The Ultimate Goal
    AFPL, Ghostscript: The Software RIP for Non-PostScript Printers
    AFPL Ghostscript, pstoraster
    AFS, The Distributed File System Challenge
    AIX, Mapping Common UIDs/GIDs on Distributed Machines, The [global] Section, NSS Winbind on AIX
    algorithmic mapping, Primary Domain Controller
    alias group, Nested Groups: Adding Windows Domain Groups to Windows Local Groups
    allow access, Using Host-Based Protection
    allow trusted domains, IDMAP_RID with Winbind
    already exists, Cannot Add Machine Back to Domain
    alternative solution, Objectives
    Amanda, Amanda
    analyzes data, Diagnostics Tools
    anonymous, Central Print Serving
    print server, Anonymous Print Server
    read-write server, Anonymous Read-Write Document Server
    anonymous access, Problem Resolution
    anonymous file server, Multiple Virtual Server Personalities
    anonymous server, Advanced Configuration Techniques
    ANSI compiler, HPUX
    anticipate failure, Features and Benefits
    API, smbpasswd: Encrypted Password Database
    Appliances, Target Uses
    application servers, Features and Benefits
    application/cups.vnd-postscript, Windows CUPS PostScript Driver Versus Adobe Driver
    application/octet-stream, Explicitly Enable “raw” Printing for application/octet-stream, MIME Type Conversion Rules, application/octet-stream Printing
    application/pdf, MIME Types and CUPS Filters, MIME Type Conversion Rules
    application/postscript, MIME Types and CUPS Filters, MIME Type Conversion Rules, Prefilters, pstops, Windows CUPS PostScript Driver Versus Adobe Driver
    application/vnd.cups-postscript, Prefilters, pstops
    application/vnd.cups-raster, PostScript Printer Descriptions for Non-PostScript Printers
    application/vnd.cups-raw, Explicitly Enable “raw” Printing for application/octet-stream
    application/x-shell, MIME Type Conversion Rules
    apt-get, Shadow Copy Setup
    ARCFOUR-HMAC-MD5, Testing Server Setup
    architecture, Comments Regarding LDAP
    ARP/RARP, /etc/hosts
    ASCII, MIME Types and CUPS Filters, What Are Charsets and Unicode?, Japanese Charsets
    ASCII text, Prefilters
    assign rights, Using the “net rpc rights” Utility
    assigned RID, Discussion
    assistance, Free Support
    associations, Group Mapping: MS Windows and UNIX
    attach gdb, Debugging with Samba Itself
    attribute, OpenLDAP Configuration
    attributes, New Schema
    audit file access, audit
    audit module, extd_audit
    auth, Anatomy of /etc/pam.d Entries
    authenticate, MS Windows Workstation/Server Machine Trust Accounts, Joining an NT4-type Domain with Samba-3
    authenticate users, Joining an NT4-type Domain with Samba-3
    authenticated, Configure smb.conf
    authenticating server, MS Windows NT4 Workstation
    authentication, Features and Benefits, Domain Security Mode (User-Level Security), Single Sign-On and Domain Security, Domain Controller Types, The Special Case of Windows 9x/Me, Why Is This Better Than security = server?, Important Notes About Security, Comments Regarding LDAP, Account Import/Export, Overview, Configure Winbind and PAM, Features and Benefits
    backend, Domain Member Server
    authentication agents, Single Sign-On and Domain Security
    authentication architecture, Single Sign-On and Domain Security
    authentication backend, Domain Layout
    authentication control, Introduction
    authentication database, Features and Benefits
    authentication management, Pluggable Authentication Modules
    authentication mechanisms, Introduction
    authentication methods, Pluggable Authentication Modules
    authentication module API, NSS Winbind on AIX
    authentication regime, Domain Member Server
    authentication reply, Why Is This Better Than security = server?
    authentication server, MS Windows NT4-style Domain Control
    authentication service, Linux/FreeBSD-Specific PAM Configuration
    authentication system, Single Sign-On and Domain Security, New Features in Samba-3.0.x
    authenticatior, Domain Controller Types
    authoritative, Behavior of Cross-Subnet Browsing
    authoritive, How Browsing Functions
    authorization, Pluggable Authentication Modules
    auto-reconnect, Important Notes About Security
    autogen.sh, Building the Binaries
    autogenerated printcap, Default UNIX System Printing Commands
    automatic account creation, Managing Domain Machine Accounts using NT4 Server Manager
    automatic mapping, Domain Member Server or Domain Member Client
    automatic reconnects, Advantages of Encrypted Passwords
    automatic redundancy, Forcing Samba to Be the Master
    autopoweruser.sh, Managing Nest Groups on Workstations from the Samba Server
    autotyping, MIME Types and CUPS Filters
    AUXILIARY, Schema and Relationship to the RFC 2307 posixAccount
    auxiliary members, Nested Groups: Adding Windows Domain Groups to Windows Local Groups
    availability, Features and Benefits, Objectives
    available, Central Print Serving
    available port, Samba and Printer Ports
    available printerd, The [global] Section
    available rights, Using the “net rpc rights” Utility
    average print run, Advanced Intelligent Printing with PostScript Driver Download

    B

    b-node, NetBIOS over TCP/IP
    back up, Requirements
    backed up, Server Share and Directory Layout
    backend, The Distributed File System Challenge
    backend authentication, Objectives
    backend database, Domain Controller Types, MS Windows Workstation/Server Machine Trust Accounts, Adding Machine to Domain Fails
    backend failures, High-Availability Server Products
    backend file system pool, Restrictive Constraints on Distributed File Systems
    backends, Passdb Changes, Printing from CUPS to Windows-Attached Printers
    backup, Features and Benefits, Server Share and Directory Layout
    backup domain controller, Domain Layout
    backup solution, Discussion of Backup Solutions
    BackupPC, BackupPC
    bad hardware, Browsing of Shares and Directories is Very Slow
    bad logon attempts, Changing User Accounts
    Bad networking hardware, Browsing of Shares and Directories is Very Slow
    bad password, The Tests
    banner pages, Windows CUPS PostScript Driver Versus Adobe Driver, Run cupsaddsmb (Quiet Mode)
    barriers, Introduction
    Batch Oplock, Opportunistic Locking Overview
    BDC, Domain Security Mode (User-Level Security), Example Configuration, Single Sign-On and Domain Security, Domain Controller Types, Features and Benefits, MS Windows NT4-style Domain Control, LDAP Configuration Notes, Active Directory Domain Control, Backup Domain Controller Configuration, Example Configuration, Can Samba Be a Backup Domain Controller to an NT4 PDC?, Joining an NT4-type Domain with Samba-3, Why Is This Better Than security = server?, New Account Storage Systems, Advantages of Encrypted Passwords, Mapping Common UIDs/GIDs on Distributed Machines, tdbsam, Overview, Domain Member Server or Domain Member Client, Primary Domain Controller, Backup Domain Controller, Join the Samba Server to the PDC Domain, Remote Management from NoMachine.Com, Domain Layout, Steps in Migration Process
    BDCs, Domain Layout
    behavior approximately same, Quick Migration Guide
    between domains, Configuring Samba NT-Style Domain Trusts
    bias, Forcing Samba to Be the Master
    binary format TDB, New Account Storage Systems
    BIND, Dynamic DNS
    bind interfaces only, Multiple Server Hosting
    BIND9, DNS and Active Directory
    BIND9.NET, Features and Benefits
    bindery-enabled, Features and Benefits
    block device, File and Directory Access Control
    block incoming packets, Using a Firewall
    BOBS, BOBS: Browseable Online Backup System
    bogus, Example Configuration
    boot disk`, Requirements
    bridge, File, Directory, and Share Access Controls
    bridges networks, How Browsing Functions
    brlock.tdb, The Printing *.tdb Files
    (see also TDB)
    broadcast, What Qualifies a Domain Controller on the Network?, NetBIOS over TCP/IP
    broadcast address, Problem Resolution, The Tests
    broadcast isolated subnet, Forcing Samba to Be the Master
    broadcast messages, NetBIOS over TCP/IP
    broadcast messaging, How Does a Workstation find its Domain Controller?
    Broadcast node, Static WINS Entries
    broadcast request, The Special Case of Windows 9x/Me
    broadcast traffic, Cross-Subnet Browsing
    broadcast-based, NetBIOS over TCP/IP
    broadcast-based name resolution, Joining an NT4-type Domain with Samba-3
    broadcasts, Forcing Samba to Be the Master, Behavior of Cross-Subnet Browsing
    browse across subnet, Cross-Subnet Browsing
    browse list, Preparing for Domain Control, How Browsing Functions, WINS: The Windows Internetworking Name Server, Behavior of Cross-Subnet Browsing
    browse list handling, Network Browsing
    browse list maintainers, How Browsing Functions
    browse list management, Security Mode and Master Browsers, What Is Browsing?
    browse lists, Making Samba the Domain Master, Cross-Subnet Browsing, Behavior of Cross-Subnet Browsing
    browse resources, Problem Resolution
    browse server resources, Problem Resolution
    browse shares, Using IPC$ Share-Based Denials
    browse.dat, Problem Resolution
    browseable, Configuration File Syntax
    browser election, Configuring Workgroup Browsing
    browser elections, Domain Browsing Configuration, Forcing Samba to Be the Master
    BrowseShortNames, Print Queue Called “lp” Mishandles Print Jobs
    browsing, The Special Case of Windows 9x/Me, What Is Browsing?, Making Samba the Domain Master, Browsing Support in Samba
    browsing across subnets, Network Browsing, Cross-Subnet Browsing
    browsing another subnet, Browsing Support in Samba
    browsing intrinsics, How Browsing Functions
    browsing problems, Windows Networking Protocols, Common Errors, I Get an "Unable to browse the network" Error
    BSD, “$” Cannot Be Included in Machine Name, Manual Creation of Machine Trust Accounts, Features and Benefits
    BSD Printing, Simple Print Configuration
    BSD-style printing, Extended Printing Configuration
    bug report, Free Support
    bug reports, Introduction
    Bugzilla, Introduction
    built-in commands, Custom Print Commands
    bypasses privilege, Using the “net rpc rights” Utility
    byte ranges, Discussion
    byte-range lock, Discussion
    byte-range locking, Discussion, Opportunistic Locking Overview

    C

    c:\winnt\inf, Windows NT4-Style Policy Files
    C:\WinNT\System32\config, MS Windows NT4-style Domain Control
    cached
    password, Password Checking
    cached encrypted password, Important Notes About Security
    cached in memory, Advantages of Non-Encrypted Passwords
    cached local file, Opportunistic Locking Overview
    cached locally, Windows 9x/Me Profile Setup
    cached references, Invalid Cached Share References Affects Network Browsing
    caching, Opportunistic Locking Overview
    caching reads, Opportunistic Locking Overview
    caching scheme, Result Caching
    caching writes, Opportunistic Locking Overview
    called name, Using Host-Based Protection
    cannot join domain, Common Errors
    canonicalize files, Handling Large Directories
    CAP, Japanese Charsets, Basic Parameter Setting, Macintosh Clients
    cap-share, Basic Parameter Setting
    capability to delete, Protecting Directories and Files from Deletion
    CAP_LINUX_IMMUTABLE, Protecting Directories and Files from Deletion
    case options, Handling Large Directories
    case sensitivity, PAM Configuration Syntax
    case-insensitive, User Level Security, Simple Print Configuration, Handling Large Directories
    case-preserving, User Level Security
    central environment, Comments Regarding LDAP
    centralized
    authentication, Single Sign-On and Domain Security
    centralized identity management, Single Sign-On and Domain Security
    centrally managed, Features and Benefits
    certificate, Securing SWAT through SSL
    Certificate Authority (see CA)
    cfdisk, Shadow Copy Setup
    challenge/response mechanis, Important Notes About Security
    change capabilities, The smbpasswd Tool
    change motivations, Objectives
    change password, Notes
    change passwords, The smbpasswd Tool
    changed parameters, Upgrading from Samba-2.x to Samba-3.0.25
    changes password, Manual Creation of Machine Trust Accounts
    character device, File and Directory Access Control
    character set, What Are Charsets and Unicode?
    character sets, Samba and Charsets, New Features in Samba-3.0.x
    charset, What Are Charsets and Unicode?
    charset conversion, Conversion from Old Names
    chattr, Protecting Directories and Files from Deletion
    check for locks, Discussion
    check logs, Adding Machine to Domain Fails
    checksum-search, Rsync
    chmod, Central Print Serving, Shadow Copy Setup
    chown, Central Print Serving, Viewing File Ownership, Features and Benefits
    chpass, Manual Creation of Machine Trust Accounts
    CIFS, Sharing User ID Mappings between Samba Domain Members
    CIFS function calls, User Rights and Privileges
    CIFS/SMB, Features and Benefits, Why Is This So Hard?
    Citrix, Remote Management with ThinLinc
    clear purpose preferred, Discussion of Backup Solutions
    clear-text, Password Checking, Important Notes About Security, Security and sambaSamAccount
    clear-text passwords, Important Notes About Security
    client client instructions, Features and Benefits
    Client for Microsoft Networks, Domain Logon Configuration: Windows 9x/Me
    Client for Novell Networks, Windows 9x/Me Profile Setup
    client-server mode, The smbpasswd Tool
    client-side caching, Opportunistic Locking Overview
    client-side data caching, Opportunistic Locking Overview, PDM Data Shares
    clock skew, Configure /etc/krb5.conf
    cluster servers, The Front-End Challenge
    clustered file server, The Ultimate Goal
    Clustered smbds, Server Pool Communications
    clustering technologies, The Ultimate Goal
    cluttering, Debugging-Specific Operations
    cmd, Browsing of Shares and Directories is Very Slow, What Rights and Privileges Will Permit Windows Client Administration?
    cmd shell, What Rights and Privileges Will Permit Windows Client Administration?
    CN, LDAP Configuration Notes, Introduction
    code maintainer, Free Support
    codepages, Features and Benefits
    collating, Making Samba the Domain Master
    collisions, Samba Performance Problem Due to Changing Linux Kernel
    color, UNIX Printfile Conversion and GUI Basics
    COM1:, Samba and Printer Ports
    command-line, Remote and Local Management: The Net Command
    command-line utility, Using the “net rpc rights” Utility
    commenting out setting, Rapid Configuration Validation
    commercial Linux products, File, Directory, and Share Access Controls
    commercial support, Samba Support, Commercial Support
    commit the settings, MS Windows 2000
    Common Internet Filesystem (see CIFS)
    Common restrictions, Managing Account/User Policies
    Common UNIX Printing System (see CUPS)
    common.adm, Windows NT4-Style Policy Files
    comp.protocols.smb, Introduction
    compatible, Important Notes About Security, Portability
    compile, Obtaining and Installing Samba
    compile-time options, Rapid Configuration Validation
    complex file name space, A Simple Solution
    complex organization, Domain Layout
    complexity, Example Configuration
    compliance, The pdbedit Tool
    complicated, Behavior of Cross-Subnet Browsing
    complicated problem, Demultiplexing SMB Requests
    comprehensive documentation, Multiple Server Hosting
    Computer Account, Windows NT4 Client
    computer account, Testing Server Setup
    computer accounts, Account Information Databases, LDAP Directories and Windows Computer Accounts, User Rights and Privileges
    Computer Management, Access Controls on Shares, Windows 200x/XP
    Computer Name, Joining a Domain: Windows 2000/XP Professional
    computer name, Domain Logon Configuration: Windows 9x/Me, Name Resolution as Used within MS Windows Networking
    concurrent access, Opportunistic Locking Overview
    Conectiva, Forums, Downloads, Tutorials, Howtos (Also for Mac OS X and Commercial UNIX)
    config.cache, Possible Errors
    CONFIG.POL, The Special Case of Windows 9x/Me
    Config.POL, Creating and Managing System Policies, Windows 9x/ME Policies
    configuration
    documentation, Test Your Config File with testparm
    configuration files, Features and Benefits
    configuration problem, Introduction
    configuration syntax, Simple Print Configuration
    configuration techniques, Advanced Configuration Techniques
    configuration too complex, Common Errors
    configuration tool, SWAT: The Samba Web Administration Tool
    configuration wizard, Joining a Domain: Windows 2000/XP Professional
    configure, Building the Binaries
    configuring a firewall, Using a Firewall
    confirm address, Using Interface Protection
    confirm the password, Samba as the Trusting Domain
    confirm the trust, Samba as the Trusted Domain
    connect transparently, The Ultimate Goal
    connection resources, Why Is This Better Than security = server?
    connections, Example Configuration
    connections.tdb, The Printing *.tdb Files
    (see also TDB)
    consistent case, Handling Large Directories
    console, Linux/FreeBSD-Specific PAM Configuration
    consumer expects, Samba Support
    container, Create the Computer Account
    continuity of service, High-Availability Server Products
    contribute, Multiple Server Hosting
    Control Panel, Joining a Domain: Windows 2000/XP Professional
    convert
    domain member server, Domain Controller Types
    converted, Technical Information
    copy'n'paste, Remote Management from NoMachine.Com
    core files, Internal Errors
    core graphic engine, Windows Drivers, GDI, and EMF
    core values, Objectives
    corrupted file, Domain Member Server or Domain Member Client
    cosine.schema, OpenLDAP Configuration
    country of origin, Commercial Support
    CP850, Samba and Charsets
    CP932, Basic Parameter Setting
    cracker, Using Interface Protection
    create, Managing Directories
    Create a Computer Account, Windows NT4 Client
    create a domain machine account, Domain Member Server
    create domain member, Windows 200x/XP Professional Client
    create machine trust account, Joining an NT4-type Domain with Samba-3
    create partition, Shadow Copy Setup
    Create the Computer Account, Configure /etc/krb5.conf
    create user accounts, Background
    create volume, Shadow Copy Setup
    credentials, User Level Security, Single Sign-On and Domain Security, LDAP Configuration Notes, Configure /etc/krb5.conf, Joining a Domain: Windows 2000/XP Professional, Administering User Rights and Privileges, User Rights and Privileges
    credentials validation, NetBIOS Over TCP/IP Enabled
    critical aspects of configuration, Features and Benefits
    crle, Configure nsswitch.conf and the Winbind Libraries on Linux and Solaris
    cron, Backup Domain Controller Configuration
    cross post, Getting Mailing List Help
    cross-segment browsing, NetBIOS over TCP/IP
    cross-subnet browsing, How Browsing Functions, Configuring Workgroup Browsing, WINS Server Configuration, Behavior of Cross-Subnet Browsing
    CUPS, Features and Benefits, Technical Introduction, Extended Printing Configuration, The [global] Section, Features and Benefits, Overview, Basic CUPS Support Configuration, Using Windows-Formatted Vendor PPDs
    Page Accounting, Page Accounting with CUPS
    quotas, Setting Up Quotas
    CUPS API, Configuration File Syntax, Default UNIX System Printing Commands
    CUPS backends, CUPS Backends
    CUPS filtering, CUPS Also Uses PPDs for Non-PostScript Printers, The CUPS Filtering Architecture
    CUPS filtering chain, CUPS Backends
    CUPS libarary API, Central Print Serving
    CUPS PostScript, Caveats to Be Considered
    CUPS PostScript driver, Windows CUPS PostScript Driver Versus Adobe Driver
    CUPS print filters, Central Print Serving
    CUPS raster, The CUPS Filtering Architecture, pstoraster
    CUPS-PPD, cupsomatic, pdqomatic, lpdomatic, directomatic
    cups.hlp, Caveats to Be Considered
    cupsaddsmb, Driver Upload Methods, cupsaddsmb: The Unknown Utility, Caveats to Be Considered, Run cupsaddsmb (Quiet Mode), Run cupsaddsmb with Verbose Output, Understanding cupsaddsmb, cupsaddsmb with a Samba PDC, cupsaddsmb Flowchart, Installing the PostScript Driver on a Client, Requirements for adddriver and setdriver to Succeed
    cupsd.conf, Default UNIX System Printing Commands, Basic CUPS Support Configuration, mime.convs, Autodeletion or Preservation of CUPS Spool Files
    cupsomatic, Using Windows-Formatted Vendor PPDs, The CUPS Filtering Architecture, The Role of cupsomatic/foomatic, cupsomatic/foomatic-rip Versus Native CUPS Printing, CUPS Print Drivers from Linuxprinting.org, cupsomatic, pdqomatic, lpdomatic, directomatic
    custom scripts, smbpasswd: Encrypted Password Database
    customer expected, Samba Support
    customers, Samba Support
    customized print commands, Custom Print Commands

    D

    daemon, Starting Samba, Interdomain Trust Relationships, Requirements, Alternative: Starting smbd as a Daemon
    daemon running, Starting and Testing the winbindd Daemon
    daemons, Restarting
    damaged data, Account Flags Management
    data caching, Opportunistic Locking Overview
    data corruption, Browsing of Shares and Directories is Very Slow, UNIX or NFS Client-Accessed Files
    data interchange, File, Directory, and Share Access Controls
    data stream, Technical Introduction
    database, MS Windows Workstation/Server Machine Trust Accounts, Quick Migration Guide
    DatabaseFS, DatabaseFS
    DAVE, Macintosh Clients
    dbx, Internal Errors
    DCE RPC, Join the Samba Server to the PDC Domain
    DDK, PostScript Drivers with No Major Problems, Even in Kernel -Mode, CUPS “PostScript Driver for Windows NT/200x/XP”
    DDNS, TCP/IP without NetBIOS, DNS and Active Directory, Background Information
    de-multiplex, The Front-End Challenge
    de-multiplexing, Demultiplexing SMB Requests
    Debian, Shadow Copy Setup
    Debian Sarge, Shadow Copy Setup
    debug, Internal Errors
    debug level, Debugging with Samba Itself, Debug Levels
    debugging, Debugging with Samba Itself, Debugging-Specific Operations
    debugging passwords, Debugging with Samba Itself
    debugging problems, Debugging with Samba Itself
    dedicated heartbeat, High-Availability Server Products
    dedicated print server, Features and Benefits
    default accounts, Domain Control: Example Configuration
    default aliases, Default Users, Groups, and Relative Identifiers
    default behavior, Identity Mapping (IDMAP)
    default devmode, Setting Device Modes on New Printers
    default DNS setup, Notes
    default gateways, MS Windows XP Professional
    default groups, Default Users, Groups, and Relative Identifiers
    default mapping, Group Mapping Changes in Samba-3.0.23
    default mappings, Mapping Windows Groups to UNIX Groups
    default print command, Default UNIX System Printing Commands
    default print commands, The [global] Section
    default printer, Custom Print Commands
    default printing, Features and Benefits
    default profile, Default Profile for Windows Users, Changing the Default Profile
    default settings, Account Flags Management
    default shells, Starting and Testing the winbindd Daemon
    Default User, MS Windows 200x/XP
    default users, Default Users, Groups, and Relative Identifiers
    defective hardware, Browsing of Shares and Directories is Very Slow
    deferred open, Opportunistic Locking Overview
    defined shares, Why Can Users Access Other Users' Home Directories?
    delegate administrative privileges, Administering User Rights and Privileges
    delegated, Important Administrative Information
    delegation, Trust Relationship Background
    delete, Managing Directories
    delete a file, Protecting Directories and Files from Deletion
    delete roaming profiles, MS Windows 200x/XP
    delete user script, Deleting Accounts
    deleted files, recycle
    deleted parameters, Removed Parameters
    delmem, Nested Groups: Adding Windows Domain Groups to Windows Local Groups
    demote, Domain Controller Types
    demoted, MS Windows NT4-style Domain Control
    denial of service, Using Interface Protection
    deny, Using IPC$ Share-Based Denials
    deny access, Using a Firewall
    deny modes, Discussion
    deny-none, Opportunistic Locking Overview
    DENY_ALL, Discussion
    DENY_DOS, Discussion
    DENY_FCB, Discussion
    DENY_NONE, Discussion
    DENY_READ, Discussion
    DENY_WRITE, Discussion
    deployment, Free Support
    deployment guidelines, Caution Regarding LDAP and Samba
    DES-CBC-CRC, Configure /etc/krb5.conf
    DES-CBC-MD5, Configure /etc/krb5.conf, Testing Server Setup
    desirable solution, What Rights and Privileges Will Permit Windows Client Administration?
    desktop cache, Windows 9x/Me Profile Setup
    desktop profile, Domain Control: Example Configuration, MS Windows NT4-style Domain Control
    desktop profiles, Features and Benefits, Managing Security Identifiers (SIDS)
    deterents, Introduction
    development libraries, Requirements
    devfsd package, Shadow Copy Setup
    device mode, Setting Device Modes on New Printers
    device-specific commands, PostScript Printer Descriptions for Non-PostScript Printers
    DFS, Features and Benefits (see MS-DFS, Distributed File Systems)
    DFS junction, Features and Benefits
    DFS links, Features and Benefits
    DFS root, Features and Benefits
    DFS server, Features and Benefits
    DFS tree, Features and Benefits
    DFS-aware, Features and Benefits
    DFS-aware clients, Features and Benefits
    DHCP, TCP/IP Configuration, MS Windows XP Professional, MS Windows 2000, MS Windows Me, Cross-Subnet Browsing, Background Information, Features and Benefits
    DHCP servers, Comments Regarding LDAP
    DHCP-enabled, MS Windows 2000
    DHCP-enabled operation, MS Windows XP Professional
    diagnostic, IDMAP Storage in LDAP Using Winbind
    diagnostic tools, Debugging with Samba Itself
    diff, Patches
    differences, Rsync
    different resources, Multiple Virtual Server Personalities
    differently encrypted passwords, Technical Information
    differing protocol, Quick Migration Guide
    dir, The Tests
    direct internet access, Introduction
    directory, Active Directory Domain Control, Central Print Serving, Backup Domain Controller
    directory access control, Nested Groups: Adding Windows Domain Groups to Windows Local Groups
    directory access permissions, File, Directory, and Share Access Controls
    directory controls, File, Directory, and Share Access Controls
    Directory Information Tree (see DIT)
    directory permissions, File, Directory, and Share Access Controls, Protecting Directories and Files from Deletion
    directory schema, Primary Domain Controller
    Directory Separators, MS Windows NTFS Comparison with UNIX File Systems
    directory server, ldapsam
    directory_mode, recycle
    disable LMB, Configuring Workgroup Browsing
    disable locking, Features and Benefits
    disable roaming profiles, Disabling Roaming Profile Support
    disabling oplocks, PDM Data Shares
    disass, Internal Errors
    disaster recovery, Server Share and Directory Layout
    disconnect a connection, NT4/200x User Profiles
    disk, Advantages of Encrypted Passwords
    disk space, Server Share and Directory Layout
    disparate information systems, Single Sign-On and Domain Security
    display PostScript, UNIX Printfile Conversion and GUI Basics
    displayName, OpenLDAP Configuration
    distort, UNIX Printfile Conversion and GUI Basics
    distribute authentication systems, Objectives
    distributed, Features and Benefits, Domain Control: Example Configuration
    distributed account, New Account Storage Systems
    Distributed Computing Environment (see DCE)
    distributed directory, Domain Member Server
    distributed file system, The Ultimate Goal (see DFS)
    Distributed File Systems, The Distributed File System Challenge
    distributed file systems, The Distributed File System Challenge
    distributed locking protocol, A Simple Solution
    distribution, Example Configuration, Joining an NT4-type Domain with Samba-3
    dithering algorithm, The Role of cupsomatic/foomatic
    DMB, Preparing for Domain Control, Domain Control: Example Configuration, Security Mode and Master Browsers, What Qualifies a Domain Controller on the Network?, How Browsing Functions, Configuring Workgroup Browsing, Domain Browsing Configuration, Forcing Samba to Be the Master, Making Samba the Domain Master, WINS: The Windows Internetworking Name Server, Windows Networking Protocols, Behavior of Cross-Subnet Browsing
    DMB for a workgroup, Browsing Support in Samba
    DMC, Examples of IDMAP Backend Usage
    DMS, Domain Security Mode (User-Level Security), Overview, Examples of IDMAP Backend Usage, Advanced Configuration Techniques
    DN, LDAP Configuration Notes, Introduction
    DNS, Preparing for Domain Control, How Does a Workstation find its Domain Controller?, NetBIOS Over TCP/IP Disabled, Configure smb.conf, Configure /etc/krb5.conf, MS Windows XP Professional, MS Windows 2000, MS Windows Me, Network Browsing, Features and Benefits, NetBIOS over TCP/IP, TCP/IP without NetBIOS, How Browsing Functions, Cross-Subnet Browsing, Initialize the LDAP Database, Name Service Switch, Background Information, DNS Lookup, The Tests, Features and Benefits, Example Configuration
    Active Directory, DNS and Active Directory
    Dynamic, Background Information, Dynamic DNS
    SRV records, DNS and Active Directory
    DNS Configuration, Browsing of Shares and Directories is Very Slow
    DNS lookup, Configure /etc/krb5.conf
    DNS name resolution, Joining an NT4-type Domain with Samba-3
    dns proxy, Assumptions
    DNS server, Behavior of Cross-Subnet Browsing
    DNS server access, Assumptions
    DNS server settings, MS Windows XP Professional, MS Windows 2000
    DNS servers, Comments Regarding LDAP
    DNS zon, Configure /etc/krb5.conf
    DNS/LDAP/ADS, Technical Overview of Browsing
    document design, Server Share and Directory Layout
    documentation, LDAP Directories and Windows Computer Accounts, Features and Benefits, Analyzing and Solving Samba Problems
    domain, The Special Case of Windows 9x/Me, Adding User Accounts, Name Resolution as Used within MS Windows Networking
    control, Server Types
    role, Domain Controller Types
    controller, Features and Benefits, Domain Security Mode (User-Level Security), Domain Control, Features and Benefits
    convert, Domain Controller Types
    hierarchy, Domain Controller Types
    controllers, Domain Security Mode (User-Level Security)
    groups, UNIX and Windows Group Management
    master
    browser, Preparing for Domain Control
    member, Server Types, Features and Benefits, Domain Controller Types
    server, Features and Benefits
    member server, Features and Benefits
    security, Domain Security Mode (User-Level Security)
    protocols, Features and Benefits
    trust account, Features and Benefits
    domain access, Identity Mapping (IDMAP)
    domain account access policies, Domain Account Policy Managment
    domain admin group, Group Mapping: MS Windows and UNIX
    domain Administrator, The Administrator Domain SID
    Domain Admins, Group Mapping Changes in Samba-3.0.23, Discussion, Nested Groups: Adding Windows Domain Groups to Windows Local Groups, Important Administrative Information, Mapping Windows Groups to UNIX Groups, Using the “net rpc rights” Utility
    Domain Admins group, Discussion
    domain authentication, Overview
    domain context, Domain Layout
    domain control, Basics of Domain Control, Security Mode and Master Browsers, Common Errors, Features and Benefits, Domain Member Server or Domain Member Client, Migration from NT4 PDC to Samba-3 PDC
    backup, Server Types
    primary, Server Types
    domain control database (see SAM)
    domain controller, Security Mode and Master Browsers, Essential Background Information, MS Windows NT4-style Domain Control, Active Directory Domain Control, NetBIOS Over TCP/IP Enabled, MS Windows Workstation/Server Machine Trust Accounts, User Rights and Privileges, What Winbind Provides, Join the Samba Server to the PDC Domain, Creating and Managing System Policies, Features and Benefits, Domain Layout, Steps in Migration Process
    Domain Controller, Caveats to Be Considered
    domain controllers, Samba ADS Domain Control, Joining an NT4-type Domain with Samba-3, MS Windows 200x/XP Professional Policies, Advanced Configuration Techniques, New Features in Samba-3.0.x
    domain environment, Important Notes About Security
    domain global, What Rights and Privileges Will Permit Windows Client Administration?
    domain global group, Overview, What Rights and Privileges Will Permit Windows Client Administration?
    domain global groups, Nested Groups: Adding Windows Domain Groups to Windows Local Groups
    domain global user, What Rights and Privileges Will Permit Windows Client Administration?
    domain global users, Nested Groups: Adding Windows Domain Groups to Windows Local Groups
    domain group, Features and Benefits
    domain group settings, Nested Groups: Adding Windows Domain Groups to Windows Local Groups
    domain groups, Group Mapping Changes in Samba-3.0.23, Group Mapping: MS Windows and UNIX, Default Users, Groups, and Relative Identifiers
    Domain Groups, Accounts and Groups Management
    Domain Guests, Mapping Windows Groups to UNIX Groups
    domain information, New Schema
    domain join, ADS Domains, Join the Samba Server to the PDC Domain
    domain joining, Joining a Domain: Windows 2000/XP Professional
    domain logon, Domain Control: Example Configuration, Domain and Network Logon Configuration, Domain Network Logon Service, Example PDC Configuration, Domain Logon Configuration: Windows 9x/Me
    domain logon server, Windows 9x/Me Profile Setup
    domain logons, The Special Case of Windows 9x/Me, Browsing Support in Samba, Important Notes About Security
    domain management tools, Managing Domain Machine Accounts using NT4 Server Manager
    domain master, Domain Control: Example Configuration, Browsing Support in Samba
    domain member, Domain Security Mode (User-Level Security), Preparing for Domain Control, Domain Membership, Features and Benefits, Windows 200x/XP Professional Client, Common Errors, Joining a Domain: Windows 2000/XP Professional, Important Notes About Security, Discussion, Overview, Handling of Foreign SIDs, Domain Layout
    Domain Member, Domain Member Server or Domain Member Client
    joining, Example Configuration
    domain member client, Important Administrative Information
    Domain Member Client (see DMC)
    domain member server, Example Configuration, Domain Member Server, Joining an NT4-type Domain with Samba-3, TCP/IP without NetBIOS, Nested Groups: Adding Windows Domain Groups to Windows Local Groups, Domain Member Server or Domain Member Client, Features and Benefits
    Domain Member Server (see DMS)
    domain member servers, Example Configuration, Mapping Common UIDs/GIDs on Distributed Machines, Nested Groups: Adding Windows Domain Groups to Windows Local Groups, User Rights and Privileges
    domain member workstations, Nested Groups: Adding Windows Domain Groups to Windows Local Groups
    domain members, Features and Benefits, Domain Browsing Configuration, Introduction
    domain membership, Preparing for Domain Control, Domain Control: Example Configuration, Domain Membership
    domain name, Domain Logon Configuration: Windows 9x/Me
    Domain Name System (see DNS)
    domain non-member, Handling of Foreign SIDs
    domain policies, Windows NT4-Style Policy Files
    domain radio button, Joining a Domain: Windows 2000/XP Professional
    domain security, Features and Benefits, MS Windows NT4-style Domain Control, Domain Membership, Features and Benefits, Domain Member Server, Joining an NT4-type Domain with Samba-3, Why Is This Better Than security = server?, Joining a Domain: Windows 2000/XP Professional, Important Notes About Security, Nested Groups: Adding Windows Domain Groups to Windows Local Groups, Primary Domain Controller, Trust Relationship Background, Join the Samba Server to the PDC Domain, MS Windows 200x/XP
    domain security account, MS Windows Workstation/Server Machine Trust Accounts
    Domain Server Manager, Applicable Only to Versions Earlier than 3.0.11
    domain SID, Backup Domain Controller Configuration, Managing Security Identifiers (SIDS)
    domain trust, Features and Benefits, Creating an NT4 Domain Trust
    domain user, Domain Logon Configuration: Windows 9x/Me, Features and Benefits, What Winbind Provides
    domain user accounts, UNIX and Windows Group Management
    domain user manager, User Account Management
    Domain User Manager, Nested Groups: Adding Windows Domain Groups to Windows Local Groups, Applicable Only to Versions Earlier than 3.0.11, Managing Account/User Policies
    Domain Users, Nested Groups: Adding Windows Domain Groups to Windows Local Groups, Mapping Windows Groups to UNIX Groups
    domain users, Requirements, Linux/FreeBSD-Specific PAM Configuration, Conclusion
    Domain Users group, Adding Domain Users to the Workstation Power Users Group
    domain-level, Why Is This Better Than security = server?
    domain-level security, Joining an NT4-type Domain with Samba-3
    domain-wide browse list, Making Samba the Domain Master
    DOMAIN<1B>, Security Mode and Master Browsers
    DOMAIN<1C>, The Special Case of Windows 9x/Me, Security Mode and Master Browsers
    DOMAIN<1D>, Security Mode and Master Browsers
    draft, The Role of cupsomatic/foomatic
    Drive Identification, MS Windows NTFS Comparison with UNIX File Systems
    driver, Verifying Configuration with testparm
    driver CDROM, Identifying Driver Files
    driver download, [print$] Stanza Parameters
    Driver File, Identifying Driver Files
    driver files, Identifying Driver Files
    Driver Path, Identifying Driver Files
    dual-daemon winbindd, New Features in Samba-3.0.x
    due diligence, Discussion of Backup Solutions
    duplex, Examples for Filtering Chains
    duplex printing, Examples for Filtering Chains
    duplicate, LDAP Configuration Notes
    duplication of information, Introduction
    DVI, MIME Types and CUPS Filters, Prefilters
    Dynamic DNS (see DDNS)
    Dynamic Host Configuration Protocol (see DHCP)
    dynamic link loader, Configure nsswitch.conf and the Winbind Libraries on Linux and Solaris
    dynamic registration files, Dynamic DNS
    Dynamic SMB servers, Objectives
    dynamically loadable library modules, Features and Benefits

    E

    e-Directory, Single Sign-On and Domain Security, Domain Member Server
    EAs, File and Directory Access Control
    economically wise, Features and Benefits
    eDirectory, Comments Regarding LDAP
    editreg, Samba Editreg Toolset
    efficient authentication, Features and Benefits
    election, Security Mode and Master Browsers, How Browsing Functions, Domain Browsing Configuration, Forcing Samba to Be the Master
    election criteria, How Browsing Functions
    election packet, Forcing Samba to Be the Master
    election process, Forcing Samba to Be the Master
    EMF, Windows Drivers, GDI, and EMF, From Windows Clients to an NT Print Server, Driver Execution on the Server
    enables clients to print, Simple Print Configuration
    enables NetBIOS over TCP/IP, NetBIOS over TCP/IP
    encapsulating, NetBIOS over TCP/IP
    encoding, Testing Server Setup
    encryped password, Domain Control: Example Configuration
    encrypted, Features and Benefits, Password Checking, Important Notes About Security
    encrypted password, Advantages of Encrypted Passwords
    encrypted passwords, Password Checking, Features and Benefits, Technical Information, Important Notes About Security, Advantages of Encrypted Passwords, Profile Migration from Windows NT4/200x Server to Samba, Passdb Backends and Authentication
    encrypted session, Security and sambaSamAccount
    encryption, Server Security (User Level Security)
    encryption key, Windows 200x/XP Professional Client
    encryption types, Configure /etc/krb5.conf, Notes
    enforcing, MS Windows Workstation/Server Machine Trust Accounts
    English, Japanese Charsets, Enabling SWAT Internationalization Support
    Enhanced MetaFile (see EMF)
    enterprise, smbpasswd: Encrypted Password Database
    enumdrivers, Identifying Driver Files, A Check of the rpcclient man Page
    enumerate domain groups, Microsoft Remote Procedure Calls
    enumerate domain users, Microsoft Remote Procedure Calls
    EnumJobs(), Printing Developments Since Samba-2.2
    enumprinters, A Check of the rpcclient man Page
    environment variables, Custom Print Commands
    EPM (see ESP meta packager)
    Epson Stylus, Examples for Filtering Chains
    Epson Stylus inkjet, Foomatic Database-Generated PPDs
    equivalence, Privileges Suppored by Windows 2000 Domain Controllers
    equivalent rights and privileges, The Administrator Domain SID
    error message, ADS Domains, Running rpcclient with adddriver
    error messages, Assumptions
    errors that can afflict, Common Errors
    ESC/P, Driver Execution on the Server
    ESP, Ghostscript: The Software RIP for Non-PostScript Printers
    Ghostscript, The CUPS Filtering Architecture, cupsomatic/foomatic-rip Versus Native CUPS Printing
    meta packager, CUPS “PostScript Driver for Windows NT/200x/XP”
    Print Pro, Sources of CUPS Drivers/PPDs, ESP Print Pro PostScript Driver for Windows NT/200x/XP
    ESP Ghostscript, The CUPS Filtering Architecture
    established, Samba as the Trusted Domain
    ethereal, Windows 9x/Me Profile Setup, Tcpdump, Ethereal, The Windows Network Monitor
    Ethernet adapters, Using Interface Protection
    EUC-JP, Japanese Charsets, Basic Parameter Setting
    eucJP-ms locale, Basic Parameter Setting
    Event Viewer, Remote Server Administration
    Everyone - Full Control, Access Controls on Shares
    Everyone group, Printing Developments Since Samba-2.2
    EVMS, shadow_copy
    examples, Example Configuration
    examples/LDAP, New Account Storage Systems
    execute, File and Directory Access Control
    existing LDAP DIT, Caution Regarding LDAP and Samba
    expands control abilities, New Account Storage Systems
    expired password, Changing User Accounts
    explicit trust, Trust Relationship Background
    explicitly set, Rapid Configuration Validation
    exploit opportunities, Features and Benefits
    exploitation, Using Interface Protection
    exported file system, A Simple Solution
    exposed, Using a Firewall
    extd_audit module, extd_audit
    Extended Attributes, File, Directory, and Share Access Controls
    extended attributes, Protecting Directories and Files from Deletion
    Extended BSD Printing, Extended Printing Configuration
    extended characters, What Are Charsets and Unicode?
    extended protocol, Windows Networking Protocols
    extended SAM, New Account Storage Systems
    extra machine, Multiple Virtual Server Hosting

    F

    fail, Features and Benefits
    failed join, NT4-Style Domains (Includes Samba Domains), IDMAP_RID with Winbind
    failed logins, Account Management Tools
    failover communication, High-Availability Server Products
    failover process, High-Availability Server Products
    failover servers, A Simple Solution
    fails, Adding Machine to Domain Fails
    failure, ADS Domains
    failure semantics, Required Modifications to Samba
    fake-permissions module, Mandatory Profiles
    fake_permissions, Domain Control: Example Configuration
    fake_perms, fake_perms, Mandatory Profiles
    fdisk, Shadow Copy Setup
    Federated Identity Management (see FIM)
    federated organizations, Single Sign-On and Domain Security
    federated-identity, Single Sign-On and Domain Security
    Fiber Channel, High-Availability Server Products
    fickle, Features and Benefits
    fid, Demultiplexing SMB Requests
    file access permissions, File, Directory, and Share Access Controls
    File Naming Conventions, MS Windows NTFS Comparison with UNIX File Systems
    file ownership, Features and Benefits
    file serving, Features and Benefits
    File System, MS Windows NTFS Comparison with UNIX File Systems
    case sensitivity, MS Windows NTFS Comparison with UNIX File Systems
    feature comparison, MS Windows NTFS Comparison with UNIX File Systems
    UNIX, MS Windows NTFS Comparison with UNIX File Systems
    Windows, MS Windows NTFS Comparison with UNIX File Systems
    file system capabilities, Protecting Directories and Files from Deletion
    FILE:, Samba and Printer Ports
    filemanager, Problem Resolution
    filename mangling, New Features in Samba-3.0.x
    filter, MIME Types and CUPS Filters
    Filter Oplock, Opportunistic Locking Overview
    FilterLimit, mime.convs
    filters, MIME Types and CUPS Filters
    FIM, Single Sign-On and Domain Security, Comments Regarding LDAP
    firewall, Introduction, Using Interface Protection, The Tests
    firewall active, Using a Firewall
    firewall setups, Using a Firewall
    fixed IP address, MS Windows XP Professional, MS Windows 2000
    fixed IP addresses, TCP/IP Configuration
    flush local locks, Opportunistic Locking Overview
    flush name cache, Flushing the Samba NetBIOS Name Cache
    foomatic, Using Windows-Formatted Vendor PPDs, The CUPS Filtering Architecture, The Role of cupsomatic/foomatic, cupsomatic/foomatic-rip Versus Native CUPS Printing, foomatic-rip and Foomatic Explained, Foomatic's Strange Name
    Foomatic database, Foomatic Database-Generated PPDs
    Foomatic Printer, The Role of cupsomatic/foomatic
    Foomatic tutorial, The Grand Unification Achieved
    foomatic-rip, The CUPS Filtering Architecture, The Role of cupsomatic/foomatic, cupsomatic/foomatic-rip Versus Native CUPS Printing, CUPS Print Drivers from Linuxprinting.org, foomatic-rip and Foomatic Explained, The Grand Unification Achieved
    Foomatic/cupsomatic, cupsomatic/foomatic-rip Versus Native CUPS Printing
    force an election, Forcing Samba to Be the Master
    force election, Making Samba the Domain Master
    forced synchronization, How Browsing Functions
    foreign domain, Mapping User Identifiers between MS Windows and UNIX, Nested Groups: Adding Windows Domain Groups to Windows Local Groups
    foreign SID, Handling of Foreign SIDs
    foreign user, Handling of Foreign SIDs
    FQDN, Introduction
    framing error, Samba Performance Problem Due to Changing Linux Kernel
    free support, Samba Support, Free Support
    FreeBSD, “$” Cannot Be Included in Machine Name, Basic Parameter Setting
    freezing, Shadow Copy Setup
    French, Enabling SWAT Internationalization Support
    front-end virtual server, The Front-End Challenge, Demultiplexing SMB Requests
    frustrating experience, LDAP Directories and Windows Computer Accounts
    FTP, Advantages of Non-Encrypted Passwords
    ftp, Rsync, Accessing the Samba Sources via rsync and ftp
    ftp access, Linux/FreeBSD-Specific PAM Configuration
    ftp service, Linux/FreeBSD-Specific PAM Configuration
    ftp services, Linux/FreeBSD-Specific PAM Configuration
    ftpd, Anatomy of /etc/pam.d Entries
    full rights, Nested Groups: Adding Windows Domain Groups to Windows Local Groups
    functional components, Debugging-Specific Operations
    functionality, Objectives

    G

    gateway address, MS Windows XP Professional
    gcc, Debugging with Samba Itself, HPUX
    gdb, Debugging with Samba Itself, Internal Errors, Attaching to a Running Process
    GDI, GDI on Windows, PostScript on UNIX, Windows Drivers, GDI, and EMF, From Windows Clients to an NT Print Server, Driver Execution on the Server
    general security service application programming interface (see GSSAPI)
    generic PostScript, MIME Types and CUPS Filters
    generic raster, pstoraster
    generic raster format, The CUPS Filtering Architecture
    genlogon.pl, Network Logon Script Magic
    Gentoo, Samba Performance Problem Due to Changing Linux Kernel
    Germany, Technical Discussion
    get, The Tests
    getdriver, Identifying Driver Files, Installing Driver Files into [print$]
    getdriverdir, A Check of the rpcclient man Page
    getent, Adding or Creating a New Group, IDMAP_RID with Winbind, Starting and Testing the winbindd Daemon
    getent group demo, Nested Groups: Adding Windows Domain Groups to Windows Local Groups
    gethostbyname() function call, Name Resolution Order
    getpwnam, Schema and Relationship to the RFC 2307 posixAccount, Domain Member Server or Domain Member Client
    getpwnam() call, Changes in Behavior
    GetSID.exe, Get SID
    GhostScript, PostScript and Ghostscript, Ghostscript: The Software RIP for Non-PostScript Printers
    (see also PostScript)
    Ghostscript, The CUPS Filtering Architecture, PostScript Printer Descriptions for Non-PostScript Printers
    ESP (see ESP - GhostScript)
    GID, Example Configuration, Manual Creation of Machine Trust Accounts, Why Is This Better Than security = server?, Sharing User ID Mappings between Samba Domain Members, User and Group Changes, Passdb Changes, Group Mapping Changes in Samba-3.0.23, Mapping Common UIDs/GIDs on Distributed Machines, Features and Benefits, Overview, Mapping Windows Groups to UNIX Groups, Identity Mapping (IDMAP), Domain Member Server or Domain Member Client, Primary Domain Controller, Features and Benefits, Handling of Foreign SIDs, Starting and Testing the winbindd Daemon
    GID numbers, Domain Member Server or Domain Member Client
    GID range, Interdomain Trust Relationships
    GIF, MIME Types and CUPS Filters
    Gimp-Print, rasterto [printers specific], Driver Development Outside
    global print command, Custom Print Commands
    global right, Description of Privileges
    global section, The [global] Section
    Global support, Objectives
    global-level, Printing-Related Configuration Parameters
    GNOME, Remote Management from NoMachine.Com
    GNU Ghostscript, The CUPS Filtering Architecture, pstoraster
    GNU GPL, BackupPC
    GNU tar, Amanda
    GNU/Linux, Discussion
    GPG, Verifying Samba's PGP Signature
    GPL, Remote Management from NoMachine.Com
    gpolmig.exe, Administration of Windows 200x/XP Policies
    GPOs, Features and Benefits, MS Windows 200x/XP Professional Policies, Administration of Windows 200x/XP Policies, Managing Account/User Policies, System Startup and Logon Processing Overview, MS Windows 200x/XP
    grace time, Changing User Accounts
    grant rights, Using the “net rpc rights” Utility
    graphical objects, UNIX Printfile Conversion and GUI Basics
    graphically illustrated client configuration, Features and Benefits
    grayscale, The Role of cupsomatic/foomatic
    greater scalability, New Account Storage Systems
    greatest mistake, Common Errors
    grep, Configure nsswitch.conf and the Winbind Libraries on Linux and Solaris
    group, Example Configuration, User and Group Changes, LDAP Directories and Windows Computer Accounts, File and Directory Access Control
    account, Domain Control: Example Configuration
    mapping, Features and Benefits
    group account, Important Administrative Information, Backup Domain Controller
    group accounts, Domain Logon Configuration: Windows 9x/Me, Caution Regarding LDAP and Samba, Features and Benefits, Warning: User Private Group Problems, Domain Member Server or Domain Member Client
    group management, Overview, UNIX and Windows Group Management
    group mapping, User and Group Changes, Group Mapping: MS Windows and UNIX
    group mappings, Group Mapping Changes in Samba-3.0.23, Features and Benefits
    group membership, Nested Groups: Adding Windows Domain Groups to Windows Local Groups
    group ownership, Features and Benefits
    group permissions, User and Group Changes, Server Share and Directory Layout
    Group Policies, Features and Benefits
    group policies, Features and Benefits
    group policy, Domain Control: Example Configuration
    Group Policy, Windows 9x/ME Policies
    Group Policy Container (see GPC)
    Group Policy Editor, Windows 9x/ME Policies, Windows NT4/200x, Samba-3 Implementation Choices
    Group Policy Objects, Objectives (see GPO)
    group policy objects (see GPOs)
    Group Policy Template (see GPT)
    group privileges, Discussion
    group profiles, Creating and Managing Group Profiles
    group SID, Managing Security Identifiers (SIDS)
    groupadd, Features and Benefits, Sample smb.conf Add Group Script, Adding Groups Fails
    groupadd limitations, Sample smb.conf Add Group Script
    groupdel, Features and Benefits
    groupmap, Group Mapping: MS Windows and UNIX
    groupmod, Features and Benefits
    grouppol.inf, Windows 9x/ME Policies
    groups, UNIX and Windows Group Management, Features and Benefits
    domain, Discussion
    mapping, Group Mapping: MS Windows and UNIX
    nested, Nested Groups: Adding Windows Domain Groups to Windows Local Groups
    groups of users, Administering User Rights and Privileges
    growing, Shadow Copy Setup
    GSSAPI, Single Sign-On and Domain Security
    gtklp, Foomatic Database-Generated PPDs
    guest, Domain Control: Example Configuration, Reference Documentation Server
    guest account, Central Print Serving, Problem Resolution, Custom Print Commands, The Tests
    GUI, Overview

    H

    h-node, NetBIOS over TCP/IP
    harvesting password hashes, Security and sambaSamAccount
    hashed password equivalent, Important Notes About Security
    headers files, Possible Errors
    Heimdal, Configure /etc/krb5.conf, ADS Domains, Features and Benefits
    Heimdal kerberos, ADS Domains, IDMAP Storage in LDAP Using Winbind
    help, Free Support
    help command, The Tests
    heterogeneous computing, Features and Benefits
    HEX, Japanese Charsets
    hi-res photo, The Role of cupsomatic/foomatic
    high availability, Features and Benefits
    high order ports, Using a Firewall
    high-availability, Opportunistic Locking Overview
    high-availability services, High-Availability Server Products
    high-speed server interconnect, A Simple Solution
    higher availability, Features and Benefits
    HKEY_CURRENT_USER, MS Windows NT4 Workstation
    HKEY_LOCAL_MACHINE, Registry Spoiling
    holy grail, Features and Benefits
    home directories, New Account Storage Systems, Starting and Testing the winbindd Daemon
    home directory, Manual Creation of Machine Trust Accounts, smbpasswd: Encrypted Password Database
    home directory template, Linux/FreeBSD-Specific PAM Configuration
    home drive, Example PDC Configuration
    host multiple servers, Multiple Virtual Server Personalities
    host security, Features and Benefits
    host-based protection, Features and Benefits
    hostname, Configure /etc/krb5.conf
    hosts allow, The Tests
    hosts deny, The Tests
    house-keeping, Description of Privileges
    HOWTO documents, Caution Regarding LDAP and Samba
    HP JetDirect, Examples for Filtering Chains
    HP Photosmart, Foomatic Database-Generated PPDs
    HP-GL, MIME Types and CUPS Filters
    HP-GL., Prefilters
    hpgltops, MIME Type Conversion Rules
    HPIJS, Driver Development Outside
    HPUX, The [global] Section
    http, Rsync
    hybrid, NetBIOS over TCP/IP
    Hybrid node, Static WINS Entries

    I

    IANA, pstoraster
    ID mapping, Example Configuration, New Features in Samba-3.0.x
    ID mapping database, User and Group ID Allocation
    ID range, Features and Benefits
    IDEALX, ldapsam
    Identification, Domain Logon Configuration: Windows 9x/Me
    identify, ADS Domains
    identity, Standalone Samba Server
    identity information, Single Sign-On and Domain Security
    identity management, Single Sign-On and Domain Security, Domain Member Server
    centralized, Single Sign-On and Domain Security
    identity resolution, Features and Benefits
    IDMAP, Group Mapping Changes in Samba-3.0.23, Features and Benefits, Identity Mapping (IDMAP), Standalone Samba Server, Domain Member Server or Domain Member Client, IDMAP_RID with Winbind
    idmap, New Schema
    idmap backend, Example Configuration, Mapping Common UIDs/GIDs on Distributed Machines, Domain Member Server or Domain Member Client, Features and Benefits, IdMap LDAP Support
    IDMAP backend, Mapping Common UIDs/GIDs on Distributed Machines
    idmap gid, Mapping User Identifiers between MS Windows and UNIX, Domain Member Server or Domain Member Client, IDMAP_RID with Winbind, Features and Benefits
    idmap GID, New Schema
    IDMAP infrastructure, Identity Mapping (IDMAP)
    idmap uid, Mapping User Identifiers between MS Windows and UNIX, Features and Benefits, Domain Member Server or Domain Member Client, IDMAP_RID with Winbind, Features and Benefits
    idmap UID, New Schema
    idmap_ad, Mapping Common UIDs/GIDs on Distributed Machines
    idmap_ldap module, New Schema
    idmap_rid, Domain Member Server or Domain Member Client, IDMAP_RID with Winbind
    IETF, Overview
    ifconfig, Starting from inetd.conf, Samba Performance Problem Due to Changing Linux Kernel
    ignore connection, Using Interface Protection
    imagetoraster, imagetops and imagetoraster
    immutible, Protecting Directories and Files from Deletion
    impersonate, Security and sambaSamAccount
    implementing oplocks, Advanced Samba Oplocks Parameters
    Implicit Classes, Print Queue Called “lp” Mishandles Print Jobs
    important announcements, Upgrading Samba
    Imprints, The Imprints Toolset
    imprints, Driver Upload Methods
    include, Advanced Configuration Techniques
    independent, Background, Multiple Server Hosting
    individual domain user, Nested Groups: Adding Windows Domain Groups to Windows Local Groups
    individual section, The [global] Section
    inetd, Validate SWAT Installation, The Tests, Starting the smbd nmbd and winbindd, Starting from inetd.conf
    inetd.conf, The Tests
    inetorgperson.schema, OpenLDAP Configuration
    inf file, Identifying Driver Files
    infrastructure, Comments Regarding LDAP, Target Uses
    inheritance, Protecting Directories and Files from Deletion
    inherits rights, Discussion
    initdb.ldif, The Primary Domain Controller
    initGroups.sh, Example: Engineering Office, Script to Configure Group Mapping, Steps in Migration Process
    inktype, The Role of cupsomatic/foomatic
    insecure, Features and Benefits, Using Host-Based Protection
    inspire simplicity, Example Configuration
    inspired structure, Technical Discussion
    install drivers, Features and Benefits, Point'n'Print Client Drivers on Samba Servers
    interactive help, Free Support
    interdomain
    trust
    account, Features and Benefits
    trustrs, Features and Benefits
    interdomain connection, Samba as the Trusting Domain
    interdomain trust, Configuring Samba NT-Style Domain Trusts, NT4-Style Domain Trusts with Windows 2000
    interdomain trust accounts, Account Information Databases, Caution Regarding LDAP and Samba
    interdomain trusts, Overview, Features and Benefits
    Interdomain Trusts, Interdomain Trust Relationships
    Completing, Completing an NT4 Domain Trust
    creating, Native MS Windows NT4 Trusts Configuration
    Facilities, Interdomain Trust Facilities
    interface, MS Windows XP Professional
    interface scripts, User Account Management
    interface-based exclusion, Features and Benefits
    interfaces, Using Interface Protection, Multiple Server Hosting
    intermediate information, Caution Regarding LDAP and Samba
    intermediate tools, Comments Regarding LDAP
    internal ordering, Features and Benefits
    internationalization support, Guidelines and Technical Tips
    Internet, Using Host-Based Protection, Using Interface Protection
    Internet Engineering Task Force (see IETF)
    Internet Printing Protocol (see IPP)
    Internet Protocol TCP/IP, MS Windows Me
    Internetworking Packet Exchange (see IPX)
    internetworking super daemon, Features and Benefits
    interoperability, Features and Benefits, Features and Benefits, Single Sign-On and Domain Security, Identity Mapping (IDMAP), File, Directory, and Share Access Controls, Features and Benefits, Restrictive Constraints on Distributed File Systems
    intolerance, Features and Benefits
    invalid shell, Example Configuration
    invalid users, The Tests
    IP address, The Tests
    IP address automatically, MS Windows XP Professional, MS Windows 2000
    IP addresses, /etc/hosts
    IP aliases, MS Windows XP Professional
    IPC$, The Special Case of Windows 9x/Me, Problem Resolution, Using IPC$ Share-Based Denials
    IPC$ connections, The Front-End Challenge
    ipchains, The Tests
    ipconfig, TCP/IP without NetBIOS
    iPlanet, Domain Member Server
    IPP, Understanding cupsaddsmb
    IPP client, Administrator Cannot Install Printers for All Local Users
    iptables, The Tests
    IPX, Windows Networking Protocols
    IRC, Free Support
    IRIX, Discussion, Basic Parameter Setting
    ISC
    DHCP, Features and Benefits
    DNS, Features and Benefits
    ISC DHCP server, MS Windows XP Professional, MS Windows Me
    isolated workgroup, Configuring Workgroup Browsing
    IXFR, Background Information

    J

    Japanese, Japanese Charsets, Enabling SWAT Internationalization Support
    Japanese locale, Basic Parameter Setting
    Japanese UNIX, Basic Parameter Setting
    Java, Remote Management with ThinLinc, Basic Parameter Setting
    JIS X 0208, Japanese Charsets
    join, NT4-Style Domains (Includes Samba Domains)
    join client, Description of Privileges
    join domain, Joining Domain Fails Because of Existing Machine Account
    join the ADS domain, Joining an NT4-type Domain with Samba-3
    join the domain, Domain Member Server, Joining an NT4-type Domain with Samba-3
    join the machine, Windows NT4 Client
    joined client, MS Windows Workstation/Server Machine Trust Accounts
    Joined domain, Joining an NT4-type Domain with Samba-3
    joining domain, Join the Samba Server to the PDC Domain
    joining the domain, Joining an NT4-type Domain with Samba-3
    JPEG, MIME Types and CUPS Filters

    K

    KB 129202, Additional Reading
    KB 224992, Additional Reading
    KB 296264, Additional Reading
    KB 811492, Long Delays Deleting Files over Network with XP SP1
    KB 812937, Problems Saving Files in MS Office on Windows XP
    KDC, Samba ADS Domain Membership, Configure /etc/krb5.conf
    KDE, Remote Management from NoMachine.Com
    KDE konqueror, Remote Management from NoMachine.Com
    KDE session, Remote Management from NoMachine.Com
    KDEPrint, Overview
    kerberos, Features and Benefits, Configure /etc/krb5.conf, ADS Domains
    Kerberos, Samba ADS Domain Membership, Configure /etc/krb5.conf, Possible Errors, Testing with smbclient, Trust Relationship Background, Microsoft Active Directory Services, Features and Benefits, Passdb Backends and Authentication
    /etc/krb5.conf, Configure /etc/krb5.conf
    Kerberos authentication, Testing with smbclient
    killall, Starting from inetd.conf
    kinit, Configure /etc/krb5.conf, Create the Computer Account, Possible Errors
    kixstart, Logon Scripts
    kprinter, Foomatic Database-Generated PPDs
    KRB, ADS Domains
    KRB5, Configure /etc/krb5.conf
    krb5.conf, Configure /etc/krb5.conf

    L

    LAN, Forcing Samba to Be the Master, Remote Management with ThinLinc, High-Availability Server Products, Diagnostics Tools
    LanMan, Features and Benefits, Essential Background Information, MS Windows Workstation/Server Machine Trust Accounts, Technical Information, Printing Developments Since Samba-2.2
    LanMan logon service, Preparing for Domain Control
    LanMan passwords, Backward Compatibility Account Storage Systems
    LanManager, User Level Security, Domain Logon Configuration: Windows 9x/Me
    LanManager-compatible, WINS: The Windows Internetworking Name Server
    LanManger password, Listing User and Machine Accounts
    laptops, BackupPC
    large directory, Handling Large Directories
    large domain, IDMAP_RID with Winbind
    large numbers of files, Handling Large Directories
    large organizations, Trust Relationship Background
    last change time, Listing User and Machine Accounts
    latency, Slow and/or Unreliable Networks
    laws, The pdbedit Tool
    LCT (see last change time)
    LDAP, Features and Benefits, Single Sign-On and Domain Security, Domain Controller Types, LDAP Configuration Notes, Backup Domain Controller Configuration, How Do I Replicate the smbpasswd File?, Can I Do This All with LDAP?, Features and Benefits, Domain Member Server, Sharing User ID Mappings between Samba Domain Members, Account Information Databases, New Account Storage Systems, Important Notes About Security, Mapping Common UIDs/GIDs on Distributed Machines, Comments Regarding LDAP, Caution Regarding LDAP and Samba, LDAP Directories and Windows Computer Accounts, ldapsam, Supported LDAP Servers, Schema and Relationship to the RFC 2307 posixAccount, Initialize the LDAP Database, Configuring Samba, Default Users, Groups, and Relative Identifiers, Identity Mapping (IDMAP), Domain Member Server or Domain Member Client, Backup Domain Controller, Interdomain Trust Relationships, Features and Benefits, Trust Relationship Background, Printing Developments Since Samba-2.2, Microsoft Active Directory Services, Features and Benefits, Passdb Backends and Authentication, Domain Layout
    directories, Comments Regarding LDAP
    master, LDAP Configuration Notes
    server, LDAP Configuration Notes
    slave, Features and Benefits, LDAP Configuration Notes
    LDAP administration password, Backup Domain Controller Configuration
    LDAP administrative password, Sharing User ID Mappings between Samba Domain Members
    LDAP backend, Background, Primary Domain Controller, Quick Migration Guide
    LDAP backends, Mapping Common UIDs/GIDs on Distributed Machines
    LDAP database, Example Configuration, Initialize the LDAP Database, Domain Layout
    LDAP deployment, Comments Regarding LDAP
    LDAP directory, Comments Regarding LDAP, Account Flags Management, ldapsam, New Features in Samba-3.0.x
    ldap group suffix, New Schema, New Suffix for Searching
    LDAP idmap Backend, Mapping Common UIDs/GIDs on Distributed Machines
    ldap idmap suffix, Sharing User ID Mappings between Samba Domain Members, New Schema, New Suffix for Searching
    ldap machine suffix, New Suffix for Searching
    LDAP queries, New Suffix for Searching
    LDAP redirects, Domain Member Server or Domain Member Client
    LDAP schema, LDAP Changes in Samba-3.0.23
    LDAP server, Domain Member Server or Domain Member Client
    ldap suffix, New Schema, New Suffix for Searching
    ldap user suffix, New Suffix for Searching
    LDAP-based, Mapping Common UIDs/GIDs on Distributed Machines, Interdomain Trust Relationships
    LDAP., LDAP Directories and Windows Computer Accounts
    LDAP/Kerberos, New Features in Samba-3.0.x
    LDAPS, Security and sambaSamAccount
    ldapsam, Domain Control: Example Configuration, MS Windows Workstation/Server Machine Trust Accounts, Account Information Databases, smbpasswd: Encrypted Password Database, ldapsam, Supported LDAP Servers, Default Users, Groups, and Relative Identifiers, Primary Domain Controller, New Schema, Objectives
    ldapsam_compat, Backward Compatibility Account Storage Systems, New Schema
    ldapsearch, New Schema
    LDAPv3, Security and sambaSamAccount
    ldconfig, Configure nsswitch.conf and the Winbind Libraries on Linux and Solaris
    ldd, Linking smbd with libcups.so
    LDIF, Initialize the LDAP Database, New Schema
    LDIF file, Initialize the LDAP Database
    legacy systems, Single Sign-On and Domain Security
    legal UNIX system account name, Adding Machine to Domain Fails
    Level1 Oplock, Opportunistic Locking Overview
    Level1 oplock, Opportunistic Locking Overview
    Level2 Oplock, Opportunistic Locking Overview
    LGPL, ldapsam
    libcups, Default UNIX System Printing Commands, Linking smbd with libcups.so
    libcups.so, Linking smbd with libcups.so
    libcups.so.2, Linking smbd with libcups.so
    Liberty Alliance, Single Sign-On and Domain Security
    libiconv, Basic Parameter Setting
    libnss_winbind, Nested Groups: Adding Windows Domain Groups to Windows Local Groups, Configure nsswitch.conf and the Winbind Libraries on Linux and Solaris
    libnss_winbind.so, Name Service Switch, Configure nsswitch.conf and the Winbind Libraries on Linux and Solaris
    libnss_wins.so, /etc/nsswitch.conf
    libraries, Configure /etc/krb5.conf
    licensing, Objectives
    limitations, Trust Relationship Background
    linewidth, UNIX Printfile Conversion and GUI Basics
    link loader configuration, Configure nsswitch.conf and the Winbind Libraries on Linux and Solaris
    Links
    hard, MS Windows NTFS Comparison with UNIX File Systems
    soft, MS Windows NTFS Comparison with UNIX File Systems
    Linux, Mapping Common UIDs/GIDs on Distributed Machines, Remote Management with ThinLinc, Features and Benefits, Basic Parameter Setting
    Linux High Availability project, High-Availability Server Products
    Linux LVM, Shadow Copy Setup
    Linux LVM partition, Shadow Copy Setup
    LinuxKongress2002, The Grand Unification Achieved
    Linuxprinting.org, The Role of cupsomatic/foomatic, CUPS Print Drivers from Linuxprinting.org, Driver Development Outside
    list of domain controllers, Joining an NT4-type Domain with Samba-3
    listen for connections, Using Interface Protection
    listen own socket, Multiple Server Hosting
    LLC, Integrating MS Windows Networks with Samba
    LM/NT password hashes, smbpasswd: Encrypted Password Database, Security and sambaSamAccount
    LMB, Preparing for Domain Control, How Browsing Functions, Configuring Workgroup Browsing, Domain Browsing Configuration, Forcing Samba to Be the Master, Making Samba the Domain Master, Use of the Remote Browse Sync Parameter, WINS: The Windows Internetworking Name Server, Windows Networking Protocols, Browsing Support in Samba, Behavior of Cross-Subnet Browsing (see Local Master Browser)
    LMHOSTS, How Browsing Functions, The LMHOSTS File
    lmhosts, WINS: The Windows Internetworking Name Server
    load balancing, Features and Benefits
    loaded modules, Features and Benefits
    loading printer drivers, Any [my_printer_name] Section
    local
    groups, UNIX and Windows Group Management
    master
    browser, Preparing for Domain Control
    local access permissions, Nested Groups: Adding Windows Domain Groups to Windows Local Groups
    local accounts, Domain Member Server or Domain Member Client
    local administrative privileges, Nested Groups: Adding Windows Domain Groups to Windows Local Groups
    Local Area Connection, MS Windows XP Professional
    Local Area Connection Properties, MS Windows 2000
    local authentication, Background
    local authentication database, Background
    local cache, The NetBIOS Name Cache
    local disk, BackupPC
    local domain, Handling of Foreign SIDs
    local group, What Rights and Privileges Will Permit Windows Client Administration?
    local groups, Nested Groups: Adding Windows Domain Groups to Windows Local Groups, Domain Member Server or Domain Member Client, Name Service Switch
    Local Machine Trust Account, Machine Accounts Keep Expiring
    Local Master Browser, NetBIOS over TCP/IP, Domain Browsing Configuration, Use of the Remote Announce Parameter
    local master browser (see LMB)
    local names, NetBIOS over TCP/IP
    local print driver, [print$] Stanza Parameters
    local profile, Disabling Roaming Profile Support, Windows 9x/Me Profile Setup
    local profiles, Features and Benefits
    local registry values, MS Windows 200x/XP Professional Policies
    Local security policies, Windows 200x/XP Local Security Policies
    local smbpasswd file, Background
    local spool area, Technical Introduction
    local subnet, Forcing Samba to Be the Master
    local system printing, Technical Introduction
    local UNIX groups, Overview
    local user, Standalone Samba Server, Restarting
    local user account, Mapping User Identifiers between MS Windows and UNIX
    local users, Domain Member Server or Domain Member Client, Name Service Switch
    locale, Enabling SWAT Internationalization Support
    localhost, Using Host-Based Protection
    locally known UID, Mapping Windows Groups to UNIX Groups
    locate domain controller, How Does a Workstation find its Domain Controller?
    Lock caching, Opportunistic Locking Overview
    lock directory, Multiple Server Hosting
    lock password, Central Print Serving
    lock the account, Changing User Accounts
    locking, File and Record Locking, Features and Benefits, Discussion, The Distributed File System Challenge
    locking protocol, Features and Benefits
    locking semantics, Features and Benefits, Discussion
    locking.tdb, The Printing *.tdb Files
    (see also TDB)
    lockout, Example Configuration
    log files, Assumptions
    monitoring, Assumptions
    log level, ADS Domains, Windows 9x/Me Profile Setup, Debugging with Samba Itself, Debug Levels
    log.nmbd, Problem Resolution, The Tests
    logging, Configuration of Auditing, Debugging-Specific Operations
    logical directories, Features and Benefits
    Logical Link Control (see LLC)
    logical volume, Shadow Copy Setup
    Logical Volume Manager (see LVM)
    Login, Advantages of Non-Encrypted Passwords
    login, Linux/FreeBSD-Specific PAM Configuration, Features and Benefits
    login id, Listing User and Machine Accounts
    login name, Example Configuration
    login shells, Comments Regarding LDAP
    LoginID, Domain Member Server or Domain Member Client
    logon, Domain Security Mode (User-Level Security)
    logon authentication, NetBIOS Over TCP/IP Disabled
    logon drive, Domain Control: Example Configuration
    logon home, Domain Control: Example Configuration, Windows 9x/Me User Profiles
    logon name, User Mapping
    logon path, Domain Control: Example Configuration
    logon processing, Domain Control: Example Configuration
    logon requests, Essential Background Information, NetBIOS Over TCP/IP Enabled, Can Samba Be a Backup Domain Controller to an NT4 PDC?
    logon script, Domain Control: Example Configuration, Features and Benefits
    Logon Scripts, Objectives
    Logon scripts, Logon Scripts
    logon server, The Special Case of Windows 9x/Me, MS Windows NT4 Workstation
    logons, NT4/200x User Profiles
    lookups, smbpasswd: Encrypted Password Database
    loopback adapter, The Tests
    loopback interface, Using Interface Protection, Red Hat Linux
    lower-case, User Level Security
    lowercase filenames, Handling Large Directories
    lp, Verifying Configuration with testparm, Print Queue Called “lp” Mishandles Print Jobs
    lpadmin, “Raw” Printing, Printing with Interface Scripts, CUPS Print Drivers from Linuxprinting.org, Setting Up Quotas
    LPD, The [global] Section
    lpinfo, CUPS Backends
    lpq cache time, The [global] Section
    lpq command, The [global] Section
    LPRNG, The [global] Section
    lpstat, Configuration File Syntax, Troubleshooting Revisited
    LPT1:, Samba and Printer Ports
    LsaEnumTrustedDomains, Debugging with Samba Itself
    LTSP, Remote Management from NoMachine.Com
    Lustre, The Distributed File System Challenge
    lvcreate, Shadow Copy Setup
    LVM, shadow_copy, Shadow Copy Setup
    LVM snapshots, Shadow Copy Setup
    LVM volume, Shadow Copy Setup
    lvm10 package, Shadow Copy Setup

    M

    m-node, NetBIOS over TCP/IP
    MAC address, /etc/hosts
    MAC Addresses, /etc/hosts
    Mac OS X , Basic Parameter Setting
    machine, LDAP Directories and Windows Computer Accounts
    account, Domain Security Mode (User-Level Security)
    machine account, Features and Benefits, Domain Controller Types, LDAP Configuration Notes, Account Flags Management, tdbsam, User Rights and Privileges
    machine account password
    change protocol, Joining an NT4-type Domain with Samba-3
    machine accounts, Manual Creation of Machine Trust Accounts, LDAP Directories and Windows Computer Accounts, Account Management Tools, User Rights and Privileges
    machine accounts database, MS Windows NT4-style Domain Control
    machine authentication, Domain Member Server
    machine name, /etc/hosts, Name Resolution as Used within MS Windows Networking
    Machine Policy Objects, Objectives
    machine SID, Managing Security Identifiers (SIDS)
    machine trust account, Features and Benefits, Preparing for Domain Control, The Special Case of Windows 9x/Me, Domain Membership, Windows 200x/XP Professional Client, Create the Computer Account, Cannot Add Machine Back to Domain
    create privilege, Windows 200x/XP Professional Client
    creation, MS Windows Workstation/Server Machine Trust Accounts
    password, Preparing for Domain Control, MS Windows Workstation/Server Machine Trust Accounts
    Machine Trust Account, MS Windows Workstation/Server Machine Trust Accounts, Manual Creation of Machine Trust Accounts, Windows NT4 Client
    creation, On-the-Fly Creation of Machine Trust Accounts
    password, Manual Creation of Machine Trust Accounts
    UNIX account, On-the-Fly Creation of Machine Trust Accounts
    Machine Trust Accounts, Machine Accounts Keep Expiring, MS Windows Workstation/Server Machine Trust Accounts
    creating, MS Windows Workstation/Server Machine Trust Accounts
    machine trust accounts, How Do I Replicate the smbpasswd File?, Managing Domain Machine Accounts using NT4 Server Manager, Common Errors, Account Information Databases, Caution Regarding LDAP and Samba
    machine_name, Manual Creation of Machine Trust Accounts
    machine_nickname, Manual Creation of Machine Trust Accounts
    Macintosh, Basic Parameter Setting
    macros, Custom Print Commands
    mail, Comments Regarding LDAP
    mailing list, Free Support
    mailing lists, Free Support
    maintaining ids, New Features in Samba-3.0.x
    major changes, New Functionality
    make, /etc/nsswitch.conf, Building the Binaries
    man, Features and Benefits
    man page, Configure smb.conf
    man pages, Overview
    man-in-the-middle, User Rights and Privileges
    manage accounts, The pdbedit Tool
    manage drivers, Features and Benefits
    manage groups, Administering User Rights and Privileges
    manage printers, Administering User Rights and Privileges
    manage privileges, Rights Management Capabilities
    manage roaming profiles, Features and Benefits
    manage share permissions, Windows NT4 Workstation/Server
    manage share-level ACL, Applicable Only to Versions Earlier than 3.0.11
    manage shares, Administering User Rights and Privileges
    manage users, Administering User Rights and Privileges
    manageability, Objectives
    Manageability, Objectives
    managed by humans, Features and Benefits
    management bottleneck, Multiuser Databases
    management costs, Comments Regarding LDAP
    management overheads, Single Sign-On and Domain Security
    management procedures, Single Sign-On and Domain Security
    management tools, Account Management Tools
    managing rights, Using the “net rpc rights” Utility
    mandatory profiles, Mandatory Profiles
    Mandrake, Forums, Downloads, Tutorials, Howtos (Also for Mac OS X and Commercial UNIX)
    Mandriva, Forums, Downloads, Tutorials, Howtos (Also for Mac OS X and Commercial UNIX)
    manual UNIX account creation, MS Windows Workstation/Server Machine Trust Accounts
    manual WINS server entries, MS Windows XP Professional, MS Windows 2000
    manually configured, MS Windows Me
    manually configured DNS settings, MS Windows XP Professional
    map, Windows 200x/XP Professional Client, User and Group Accounts
    mapped, Important Administrative Information, Overview, Mapping Windows Groups to UNIX Groups
    mapping, Mapping User Identifiers between MS Windows and UNIX, Mapping Windows Groups to UNIX Groups
    mapping home directory, Why Can Users Access Other Users' Home Directories?
    mapping printer driver, Running rpcclient with setdriver
    mappings, Sharing User ID Mappings between Samba Domain Members
    maps UNIX users and groups, Sharing User ID Mappings between Samba Domain Members
    master browser, Forcing Samba to Be the Master
    master browsers, Behavior of Cross-Subnet Browsing
    master server, Domain Layout
    master smb.conf, Multiple Virtual Server Hosting
    MasterAnnouncement, Behavior of Cross-Subnet Browsing
    match case, Handling Large Directories
    maximum value, Interdomain Trust Relationships
    mbd kept spawning, Corrupt tdb Files
    Meccano set, Discussion of Backup Solutions
    mechanism, Joining an NT4-type Domain with Samba-3
    media type, The Role of cupsomatic/foomatic
    member, Preparing for Domain Control, Using the “net rpc rights” Utility
    member machine, Nested Groups: Adding Windows Domain Groups to Windows Local Groups
    memory, Advantages of Encrypted Passwords
    messages.tdb, The Printing *.tdb Files
    (see also TDB)
    messaging systems, Comments Regarding LDAP
    Meta node, Static WINS Entries
    meta-directory, Single Sign-On and Domain Security
    meta-service, Configuration File Syntax
    meta-services, Multiple Virtual Server Personalities
    Microsoft Active Directory, Features and Benefits
    Microsoft Developer Network CDs, The Windows Network Monitor
    Microsoft driver, PostScript Drivers with No Major Problems, Even in Kernel -Mode
    Microsoft management console (see MMC)
    Microsoft Remote Procedure Call (see MSRPC)
    Microsoft Windows 9x/Me, Managing Domain Machine Accounts using NT4 Server Manager
    Microsoft Wolfpack, High-Availability Server Products
    middle-ware, Comments Regarding LDAP
    migrate, Server Types and Security Modes, Migration from NT4 PDC to Samba-3 PDC
    migrate account settings, User and Group Accounts
    migrate group, User and Group Accounts
    migrate user, User and Group Accounts
    migrating, New Features in Samba-3.0.x
    migration, Objectives
    migration plan, Planning and Getting Started
    migration process, Objectives
    MIME, MIME Types and CUPS Filters, MIME Type Conversion Rules, Filtering Overview, application/octet-stream Printing
    filters, MIME Types and CUPS Filters
    raw, Anonymous Print Server, Central Print Serving, Explicitly Enable “raw” Printing for application/octet-stream
    MIME conversion rules, The CUPS Filtering Architecture
    MIME recognition, The CUPS Filtering Architecture
    MIME type, Explicitly Enable “raw” Printing for application/octet-stream, The CUPS Filtering Architecture, Prefilters, application/octet-stream Printing
    mime.types, MIME Types and CUPS Filters
    minimal
    configuration, Configuration File Syntax
    minimal configuration, Configuration File Syntax
    minimum security control, Standalone Servers
    misconfigurations, Test Your Config File with testparm
    misconfigured settings, Simple Print Configuration
    misinformation, Domain Membership
    mission-critical, Opportunistic Locking Overview, Features and Benefits
    MIT, Configure /etc/krb5.conf, ADS Domains
    MIT kerberos, ADS Domains, IDMAP Storage in LDAP Using Winbind
    MIT Kerberos, Features and Benefits
    mixed mode, ADS Security Mode (User-Level Security), NT4-Style Domain Trusts with Windows 2000
    mixed profile, Mixed Windows Windows 9x/Me and NT4/200x User Profiles
    mkdir, Central Print Serving, Shadow Copy Setup
    mkfs.xfs, Shadow Copy Setup
    MMC, Features and Benefits, Features and Benefits, Domain Member Server or Domain Member Client, Primary Domain Controller, Access Controls on Shares, Windows 200x/XP, Creating and Managing System Policies, Windows NT4/200x, Disabling Roaming Profile Support
    MMC snap-in, Administration of Windows 200x/XP Policies
    modem/ISDN, Remote Management from NoMachine.Com
    moderately secure, Features and Benefits
    modprobe, Shadow Copy Setup
    module, Shadow Copy Setup
    modules, Features and Benefits, Discussion
    more than one protocol, Windows Networking Protocols
    mount, Share-Level Security, Shadow Copy Setup
    mouse-over, Remote Management from NoMachine.Com
    moveuser.exe, moveuser.exe
    MS DCE RPC, Join the Samba Server to the PDC Domain
    MS Windows 2000, Active Directory Domain Control
    MS Windows NT4/200x, New Account Storage Systems
    MS Windows SID, Domain Member Server or Domain Member Client
    MS WINS, Features and Benefits
    MS-DFS, MS-DFS: The Poor Man's Cluster
    MS-RPC, Printing Developments Since Samba-2.2
    MS-WINS replication, NetBIOS over TCP/IP
    msdfs links, Features and Benefits
    msg, Enabling SWAT Internationalization Support
    msg file, Enabling SWAT Internationalization Support
    MSRPC, Microsoft Remote Procedure Calls, Name Service Switch
    multibyte character sets, New Features in Samba-3.0.x
    multibyte charsets, What Are Charsets and Unicode?
    multiple backends, Password Backends
    multiple domains, Domain Layout
    multiple hosting, Advanced Configuration Techniques
    multiple modules, Discussion
    multiple network interfaces, Multiple Interfaces
    multiple network segments, Domain Layout
    multiple personality, Multiple Virtual Server Personalities
    multiple server hosting, Multiple Server Hosting
    multiple server personalities, Advanced Configuration Techniques
    multiple servers, Advanced Configuration Techniques, Multiple Server Hosting
    multiple universal naming convention provider (see MUP)
    multiple VFS, Discussion
    multiple virtual servers, Multiple Virtual Server Personalities
    multiple Windows workgroups or domains, MS Windows Me
    multiple WINS servers, NetBIOS over TCP/IP
    Multiuser databases, Multiuser Databases
    mutual assistance, Free Support
    mutually exclusive options, What Is Browsing?
    My Network Places, MS Windows Me, Problem Resolution
    Myrinet, Server Pool Communications Demands

    N

    n security context, How Browsing Functions
    n-memory buffer, The NetBIOS Name Cache
    name conflict, Any [my_printer_name] Section
    name lookup, Domain Controller Types, The NetBIOS Name Cache
    name lookups, NetBIOS over TCP/IP, How Browsing Functions
    name registration, What Qualifies a Domain Controller on the Network?
    name resolution, What Is Browsing?, NetBIOS over TCP/IP, How Browsing Functions, Technical Overview of Browsing, Common Errors, /etc/hosts, Assumptions
    name resolution across routed networks, How Browsing Functions
    name resolve order, Name Resolution Order
    name service switch (see NSS)
    name-to-address, WINS: The Windows Internetworking Name Server
    nameserv.h, Static WINS Entries
    name_type, WINS: The Windows Internetworking Name Server, Name Resolution Order
    native ACLs, Features and Benefits
    native dump, Amanda
    native member, Domain Controller Types, Features and Benefits
    native mode, ADS Security Mode (User-Level Security), Microsoft Active Directory Services
    NBT, Name Resolution as Used within MS Windows Networking
    nbtstat, Cannot Add Machine Back to Domain, The NetBIOS Name Cache
    necessary rights, Using the “net rpc rights” Utility
    negotiate, Important Notes About Security
    negotiating the charset, What Are Charsets and Unicode?
    nested group, Nested Groups: Adding Windows Domain Groups to Windows Local Groups
    Nested Group Support, What Rights and Privileges Will Permit Windows Client Administration?
    nested groups, Nested Groups: Adding Windows Domain Groups to Windows Local Groups
    net, Account Management Tools, Group Mapping: MS Windows and UNIX, Remote and Local Management: The Net Command, Overview, Administrative Tasks and Methods, UNIX and Windows Group Management, What Rights and Privileges Will Permit Windows Client Administration?
    ads, UNIX and Windows Group Management
    join, Joining an NT4-type Domain with Samba-3, Create the Computer Account, Machine Trust Accounts, ADS Domains
    leave, Machine Trust Accounts
    printer info, Printers and ADS
    printer publish, Printers and ADS
    printer remove, Printers and ADS
    printer search, Printers and ADS
    status, Machine Trust Accounts
    testjoin, Machine Trust Accounts
    getlocalsid, User and Group Changes, Managing Security Identifiers (SIDS), New Schema
    groupmap, Example: Engineering Office, User and Group Changes, Features and Benefits, Example Configuration, Steps in Migration Process
    add, Mapping Windows Groups to UNIX Groups
    delete, Mapping Windows Groups to UNIX Groups
    list, Example Configuration, Adding or Creating a New Group
    modify, Mapping Windows Groups to UNIX Groups
    localgroup, What Rights and Privileges Will Permit Windows Client Administration?
    rap, UNIX and Windows Group Management
    session, Session and Connection Management
    rpc, Example Configuration, Example Configuration, Features and Benefits, UNIX and Windows Group Management
    getsid, Backup Domain Controller Configuration, Managing Security Identifiers (SIDS)
    group, Nested Groups: Adding Windows Domain Groups to Windows Local Groups, Adding or Creating a New Group
    group add, Adding or Creating a New Group
    group addmem, Manipulating Group Memberships, Managing Nest Groups on Workstations from the Samba Server
    group delete, Deleting a Group Account
    group delmem, Manipulating Group Memberships
    group list, Adding or Creating a New Group
    group members, Manipulating Group Memberships
    group rename, Rename Group Accounts
    info, Other Miscellaneous Operations, Side Bar Notes
    join, Example Configuration, Joining an NT4-type Domain with Samba-3, Machine Trust Accounts, Join the Samba Server to the PDC Domain, Steps in Migration Process
    join bdc, Machine Trust Accounts
    join member, Machine Trust Accounts
    list, Using the “net rpc rights” Utility
    printer migrate drivers, Printer Migration
    printer migrate forms, Printer Migration
    printer migrate printers, Printer Migration
    printer migrate security, Printer Migration
    printer migrate settings, Printer Migration
    right list accounts, Share Migration
    rights grant, Administering User Rights and Privileges, Using the “net rpc rights” Utility
    rights list, Administering User Rights and Privileges
    rights list accounts, Administering User Rights and Privileges
    share add, Creating, Editing, and Removing Shares
    share delete, Creating, Editing, and Removing Shares
    share migrate, Share Migration
    share migrate all, Simultaneous Share and File Migration
    share migrate files, File and Directory Migration
    share migrate security, Share-ACL Migration
    testjoin, Machine Trust Accounts
    trustdom add, Interdomain Trusts
    trustdom establish, Interdomain Trusts, Samba as the Trusting Domain
    trustdom list, Interdomain Trusts
    trustdom revoke, Interdomain Trusts
    user add, Adding User Accounts
    user delete, Deletion of User Accounts, Machine Trust Accounts
    user info, Managing User Accounts
    user password, Adding User Accounts
    user rename, Managing User Accounts
    vampire, User and Group Changes, Share, Directory, and File Migration, Steps in Migration Process
    setlocalsid, Managing Security Identifiers (SIDS)
    time, Other Miscellaneous Operations
    set, Other Miscellaneous Operations
    system, Other Miscellaneous Operations
    zone, Other Miscellaneous Operations
    use, Testing Server Setup
    NET, Samba PDC
    net command, New Features in Samba-3.0.x
    net getlocalsid, The Administrator Domain SID
    net groupmap, New Schema
    net rpc user add, Description of Privileges
    net tool, Passdb Backends and Authentication
    net use, Error Message: “Cannot connect under a different Name”
    net use /home, Windows 9x/Me User Profiles
    net use lpt1:, Installing the PostScript Driver on a Client
    net view, The [global] Section, The Tests
    netatalk, netatalk
    NetAtalk, Basic Parameter Setting
    Netatalk, Macintosh Clients
    NetBEUI, Integrating MS Windows Networks with Samba
    NetBIOS, Domain Security Mode (User-Level Security), Features and Benefits, What Qualifies a Domain Controller on the Network?, How Does a Workstation find its Domain Controller?, Example Configuration, Features and Benefits, Discussion, TCP/IP without NetBIOS, Technical Overview of Browsing, Integrating MS Windows Networks with Samba, Name Resolution as Used within MS Windows Networking, The NetBIOS Name Cache
    brooadcast, Preparing for Domain Control
    name, Domain Security Mode (User-Level Security)
    netbios alias, Multiple Virtual Server Personalities
    netbios aliases, Multiple Virtual Server Personalities
    NetBIOS broadcast, Joining an NT4-type Domain with Samba-3
    NetBIOS disabled, Features and Benefits
    NetBIOS flags, Static WINS Entries
    NetBIOS name, Security Mode and Master Browsers, Manual Creation of Machine Trust Accounts, Joining an NT4-type Domain with Samba-3, Name Resolution as Used within MS Windows Networking, Multiple Virtual Server Personalities
    netbios name, Multiple Server Hosting
    NetBIOS name cache, Cannot Add Machine Back to Domain, Flushing the Samba NetBIOS Name Cache
    NetBIOS name length, WINS: The Windows Internetworking Name Server
    NetBIOS name resolution, Behavior of Cross-Subnet Browsing
    NetBIOS Name Server (see NBNS)
    NetBIOS name type, How Browsing Functions
    NetBIOS names, Name Resolution Order, /etc/nsswitch.conf
    NetBIOS network interface, Windows Networking Protocols
    NetBIOS networking, Features and Benefits
    NetBIOS over TCP/IP, Network Browsing, Features and Benefits, NetBIOS over TCP/IP, Technical Overview of Browsing, Cross-Subnet Browsing, Background Information
    NetBIOS over TCP/IP disabled, Browsing of Shares and Directories is Very Slow
    NetBIOS-less, TCP/IP without NetBIOS, Multiple Virtual Server Personalities
    NetBIOS-less SMB, Multiple Virtual Server Personalities
    NetBIOSless SMB over TCP/IP, NetBIOS over TCP/IP
    NetBT, Name Resolution as Used within MS Windows Networking
    netlogon, Domain Controller Types
    NETLOGON, Preparing for Domain Control, Domain Control: Example Configuration, Creating and Managing System Policies, MS Windows 200x/XP Professional Policies, Managing Account/User Policies, MS Windows NT4 Workstation, MS Windows 200x/XP
    Netlogon, Essential Background Information
    NetLogon service, WINS: The Windows Internetworking Name Server
    netlogon share, Backup Domain Controller Configuration, Steps in Migration Process
    Netmon, The Windows Network Monitor
    Netmon., Installing Network Monitor on an NT Workstation
    netmon.exe, Windows 9x/Me Profile Setup
    NetSAMLogon, Roaming Profiles
    Netscape's Directory Server, Supported LDAP Servers
    NetServerEnum2, Behavior of Cross-Subnet Browsing
    NetUserGetInfo, The Special Case of Windows 9x/Me, Roaming Profiles
    NetWare, Name Resolution as Used within MS Windows Networking
    NetWare Bindery, Features and Benefits
    NetWare Core Protocol-based server, Features and Benefits
    NetWkstaUserLogon, The Special Case of Windows 9x/Me
    network
    browsing, Features and Benefits
    logon, Domain Control: Example Configuration
    service, Security Mode and Master Browsers
    performance, Domain Controller Types
    wide-area, MS Windows NT4-style Domain Control
    network access controls, File, Directory, and Share Access Controls
    network access profile, MS Windows NT4-style Domain Control
    network administrator, File, Directory, and Share Access Controls
    network administrator's toolbox, Remote and Local Management: The Net Command
    network administrators, Server Share and Directory Layout
    network analyzer, Diagnostics Tools
    network bandwidth, Forcing Samba to Be the Master, Domain Layout
    Network Basic Extended User Interface (see NetBEUI)
    Network Basic Input/Output System (see NetBIOS)
    Network Bridge, MS Windows XP Professional
    Network Bridge Configuration, MS Windows XP Professional
    network browsing problems, Making Samba the Domain Master, Browsing of Shares and Directories is Very Slow
    network client, Features and Benefits, Identity Mapping (IDMAP)
    network clients, MS Windows 2000
    network configuration problems, TCP/IP Configuration
    network difficulty, Features and Benefits
    network environment, Remote Desktop Management
    Network ID, Joining a Domain: Windows 2000/XP Professional
    network interface, Using Interface Protection, The Tests
    network logon, The Special Case of Windows 9x/Me, Features and Benefits, Domain Logon Configuration: Windows 9x/Me
    network logon services, The Special Case of Windows 9x/Me
    network membership, Technical Details
    Network Monitor, The Windows Network Monitor
    Network Monitor Tools and Agent, Installing Network Monitor on an NT Workstation
    Network Neighborhood, What Is Browsing?, Problem Resolution, Behavior of Cross-Subnet Browsing, The [global] Section, Check Samba for Driver Recognition
    network neighborhood, Behavior of Cross-Subnet Browsing
    network policies, Creating and Managing System Policies
    network security, Domain Layout
    network segment, NetBIOS over TCP/IP, How Browsing Functions, Domain Layout
    Network settings, Cross-Subnet Browsing
    network sniffer, Advantages of Encrypted Passwords
    network storage, BackupPC
    network traffic, Domain Member Server or Domain Member Client
    networked workstation, Name Service Switch
    networking advocates, Discussion of Backup Solutions
    networking environment, Caution Regarding LDAP and Samba
    networking systems, Common Errors
    networks access, Samba Performance is Very Slow
    Networks Properties, Domain Logon Configuration: Windows 9x/Me
    new account, Samba as the Trusted Domain
    new parameters, New Parameters
    newsgroup, Introduction
    Nexus toolkit, MS Windows Workstation/Server Machine Trust Accounts
    Nexus.exe, Features and Benefits, Managing Domain Machine Accounts using NT4 Server Manager, Remote Server Administration
    NFS, Sharing User ID Mappings between Samba Domain Members, Mapping Common UIDs/GIDs on Distributed Machines, Remote Management with ThinLinc, The Distributed File System Challenge, Restrictive Constraints on Distributed File Systems, IdMap LDAP Support
    NFS clients, UNIX or NFS Client-Accessed Files
    NIS, Share-Level Security, Backup Domain Controller Configuration, Schema and Relationship to the RFC 2307 posixAccount, Domain Member Server or Domain Member Client, Name Service Switch
    NIS database, Pluggable Authentication Modules
    nmbd, Starting Samba, Test Your Config File with testparm, Secure Read-Write File and Print Server, Example Configuration, What Is Browsing?, NetBIOS over TCP/IP, Browsing Support in Samba, Flushing the Samba NetBIOS Name Cache, NT4-Style Domains (Includes Samba Domains), Testing Things Out, Linux, Solaris, Multiple Server Hosting, Multiple Virtual Server Personalities, The Tests, Debugging with Samba Itself, Corrupt tdb Files
    nmblookup, The NetBIOS Name Cache, The Tests
    No NetBIOS layer, TCP/IP without NetBIOS
    no network logon service, Background
    no printcap file, Central Print Serving
    nobody, Central Print Serving
    nobody account, Custom Print Commands, Multiple Virtual Server Personalities
    node-type, NetBIOS over TCP/IP
    NoMachine, Remote Management from NoMachine.Com
    NoMachine.Com, Remote Management from NoMachine.Com
    non-authentication-based account management, Anatomy of /etc/pam.d Entries
    non-authoritative, Behavior of Cross-Subnet Browsing
    non-LDAP
    backend, Features and Benefits
    non-member Windows client, Mapping User Identifiers between MS Windows and UNIX
    non-PostScript, CUPS Also Uses PPDs for Non-PostScript Printers, PostScript Printer Descriptions for Non-PostScript Printers
    non-PostScript printers, Prefilters, Foomatic Database-Generated PPDs
    nonhierarchical, Trust Relationship Background
    nontransitive, Trust Relationship Background
    normal color, The Role of cupsomatic/foomatic
    normal user, Administering User Rights and Privileges
    not domain member, Background
    not domain members, Standalone Servers
    not part of domain, WINS Server Configuration
    not stored anywhere, Advantages of Encrypted Passwords
    not transitive, NT4-Style Domain Trusts with Windows 2000
    Novell, Domain Member Server, Windows 9x/Me Profile Setup
    Novell eDirectory server, Features and Benefits
    NSS, Background, Mapping Common UIDs/GIDs on Distributed Machines, LDAP Directories and Windows Computer Accounts, ldapsam, Schema and Relationship to the RFC 2307 posixAccount, Accounts and Groups Management, Nested Groups: Adding Windows Domain Groups to Windows Local Groups, Identity Mapping (IDMAP), Domain Member Server or Domain Member Client, IDMAP_RID with Winbind, Features and Benefits, What Winbind Provides, How Winbind Works, Name Service Switch, Configure Winbind and PAM, Conclusion
    nsswitch.conf, Share-Level Security
    nss_ldap, Example Configuration, Mapping Common UIDs/GIDs on Distributed Machines, LDAP Directories and Windows Computer Accounts, Identity Mapping (IDMAP), Domain Member Server or Domain Member Client, IDMAP and NSS Using LDAP from ADS with RFC2307bis Schema Extension
    nss_winbind.so.1, Configure nsswitch.conf and the Winbind Libraries on Linux and Solaris
    NT domain, What Winbind Provides
    NT groups, Why Is This Better Than security = server?, Default Users, Groups, and Relative Identifiers
    NT migration scripts, ldapsam
    NT password, Listing User and Machine Accounts
    NT Server Manager, Windows NT4 Workstation/Server
    NT-controlled domain, Samba as the Trusting Domain
    NT-encrypted password, MS Windows Workstation/Server Machine Trust Accounts
    NT-encrypted passwords, Backward Compatibility Account Storage Systems
    NT4, Domain Member Server or Domain Member Client
    NT4 Domain, Standalone Samba Server
    NT4 domain, Domain Member Server or Domain Member Client, Features and Benefits
    NT4 domain members, Identity Mapping (IDMAP)
    NT4 style policy updates, Managing Account/User Policies
    NT4 User Manager for Domains, Using the “net rpc rights” Utility
    NT4-style, NT4-Style Domain Trusts with Windows 2000
    NT4-style domain, Interdomain Trust Relationships
    NT4-style domains, Trust Relationship Background
    Nt4sp6ai.exe, Windows NT4-Style Policy Files
    NTConfig.POL, Domain Control: Example Configuration, Features and Benefits, Windows 9x/ME Policies, Registry Spoiling, MS Windows 200x/XP Professional Policies, Administration of Windows 200x/XP Policies, Managing Account/User Policies, Samba Editreg Toolset, MS Windows NT4 Workstation, Samba-3 Implementation Choices
    ntconfig.pol, Windows NT4-Style Policy Files
    ntdrivers.tdb, Setting Device Modes on New Printers, The Printing *.tdb Files
    (see also TDB)
    ntforms.tdb, Setting Device Modes on New Printers, The Printing *.tdb Files
    (see also TDB)
    NTFS, User and Group Changes, MS Windows NTFS Comparison with UNIX File Systems
    NTLMv2, NTLMv2 Security
    ntlm_auth, Single Sign-On and Domain Security
    ntprinters.tdb, Setting Device Modes on New Printers, The Printing *.tdb Files
    (see also TDB)
    NTUser.DAT, Samba Editreg Toolset, Mandatory Profiles, Samba-3 Implementation Choices
    NTuser.DAT, Windows NT4 Workstation, Sharing Profiles between Windows 9x/Me and NT4/200x/XP Workstations, Profile Migration/Creation
    NTuser.MAN, Windows NT4 Workstation
    NTUser.MAN, Mandatory Profiles
    NT_STATUS_LOGON_FAILURE, Changes in Behavior
    NT_STATUS_UNSUCCESSFUL, Running rpcclient with adddriver
    null shell, Manual Creation of Machine Trust Accounts
    NX, Remote Management from NoMachine.Com

    O

    object class, New Schema
    object class declaration, New Schema
    object module dependencies, Configure nsswitch.conf and the Winbind Libraries on Linux and Solaris
    ObjectClass, Schema and Relationship to the RFC 2307 posixAccount
    ObjectClasses, Schema and Relationship to the RFC 2307 posixAccount, OpenLDAP Configuration
    obtuse complexity, Server Share and Directory Layout
    office server, Secure Read-Write File and Print Server
    OID, Schema and Relationship to the RFC 2307 posixAccount
    old sambaAccount, New Schema
    Omni, Driver Development Outside
    on the fly, Windows NT4 Client
    on-the-fly, Primary Domain Controller
    on-the-fly logon scripts, Objectives
    on-the-fly policy files, Objectives
    one direction, Trust Relationship Background
    one domain, Identity Mapping (IDMAP)
    one-way trust, Interdomain Trust Facilities
    only one WINS server, WINS Server Configuration
    OpenGFS, The Distributed File System Challenge
    OpenLDAP, Single Sign-On and Domain Security, LDAP Configuration Notes, Domain Member Server, LDAP Changes in Samba-3.0.23, New Account Storage Systems, Supported LDAP Servers, Schema and Relationship to the RFC 2307 posixAccount, OpenLDAP Configuration, Features and Benefits
    OpenLDAP backend, Backward Compatibility Account Storage Systems
    OpenSSL, Securing SWAT through SSL, Generating the Certificate Authority
    operating costs, Objectives
    operating system search path, Locating the SWAT File
    oplock, The Distributed File System Challenge
    oplock break, Opportunistic Locking Overview, Beware of Force User
    oplock handling, Restrictive Constraints on Distributed File Systems
    oplock mechanism, Advanced Samba Oplocks Parameters
    oplock messages, Required Modifications to Samba
    oplock parameters, Advanced Samba Oplocks Parameters
    oplocks, Opportunistic Locking Overview
    oplocks disabled, Multiuser Databases
    oplocks management, PDM Data Shares
    opportunistic locking, Features and Benefits, Opportunistic Locking Overview
    Opportunistic locking, Opportunistic Locking Overview
    optional, Anatomy of /etc/pam.d Entries
    ordinary connection, Samba as the Trusting Domain
    Organization for the Advancement of Structured Information Standards (see OASIS)
    organizational directory, Create the Computer Account
    organizational unit, Create the Computer Account (see OU)
    os level, Domain Control: Example Configuration
    OSS/Free Software, Remote Management from NoMachine.Com
    other, File and Directory Access Control
    output duplexing, pstops
    outside threat, Using Host-Based Protection
    own home directory, Why Can Users Access Other Users' Home Directories?
    ownership, Viewing File Ownership
    ownership cost, Objectives
    ownership rights, Windows 9x/Me Profile Setup

    P

    p-node, NetBIOS over TCP/IP
    package, Example Configuration
    packages, Obtaining and Installing Samba
    packet sniffer, Windows 9x/Me Profile Setup
    packet trace, Windows 9x/Me Profile Setup
    PADL, Mapping Common UIDs/GIDs on Distributed Machines, LDAP Directories and Windows Computer Accounts, Domain Member Server or Domain Member Client, IDMAP Storage in LDAP Using Winbind
    PADL Software, Mapping Common UIDs/GIDs on Distributed Machines
    page description languages (see PDL)
    pager program, Simple Print Configuration
    page_log, The page_log File Syntax
    paid-for support, Samba Support
    PAM, Background, Backward Compatibility Account Storage Systems, Mapping Common UIDs/GIDs on Distributed Machines, Plaintext, ldapsam, How Winbind Works, Pluggable Authentication Modules, Requirements, Testing Things Out, Configure nsswitch.conf and the Winbind Libraries on Linux and Solaris, Configure Winbind and PAM, Conclusion, Features and Benefits, Technical Discussion
    PAM authentication module, PAM Configuration Syntax
    PAM configuration, Requirements
    PAM management, PAM-Based Distributed Authentication
    PAM module, NSS Winbind on AIX
    PAM modules, Features and Benefits
    PAM-capable, Features and Benefits
    pam-devel, Configure nsswitch.conf and the Winbind Libraries on Linux and Solaris
    PAM-enabled, What Winbind Provides, PAM-Based Distributed Authentication, Features and Benefits
    PAM-specific tokens, PAM Configuration Syntax
    pam_krb5.so, Features and Benefits
    pam_ldap, Mapping Common UIDs/GIDs on Distributed Machines
    pam_ldap.so, Features and Benefits
    pam_mkhomedir, Linux/FreeBSD-Specific PAM Configuration
    pam_ncp_auth.so, Features and Benefits
    pam_pwdb.so, Features and Benefits
    pam_securetty.so, Linux/FreeBSD-Specific PAM Configuration
    pam_smbpass.so, PAM-Based Distributed Authentication, Features and Benefits
    pam_smbpasswd.so, Features and Benefits
    pam_smb_auth.so, Features and Benefits
    pam_unix.so, Linux/FreeBSD-Specific PAM Configuration, Features and Benefits
    pam_unix2.so, Features and Benefits
    pam_userdb.so, Features and Benefits
    pam_winbind.so, Pluggable Authentication Modules, Configure Winbind and PAM, Linux/FreeBSD-Specific PAM Configuration, Features and Benefits
    parameters, Rapid Configuration Validation
    paranoid, Starting and Testing the winbindd Daemon
    passdb, Machine Accounts Keep Expiring
    passdb backend, Domain Control: Example Configuration, Group Mapping Changes in Samba-3.0.23, Account Information Databases, Comments Regarding LDAP, The smbpasswd Tool, The pdbedit Tool, Deleting Accounts, tdbsam, Default Users, Groups, and Relative Identifiers, Domain Member Server or Domain Member Client, Primary Domain Controller, The Administrator Domain SID, Interdomain Trust Relationships, Features and Benefits, New Suffix for Searching
    passdb backends, smbpasswd: Encrypted Password Database, New Features in Samba-3.0.x
    passed across the network, Advantages of Encrypted Passwords
    passwd, Central Print Serving, LDAP Directories and Windows Computer Accounts, The smbpasswd Tool, Name Service Switch, Features and Benefits
    password, MS Windows NT4-style Domain Control, Samba as the Trusted Domain, Samba as the Trusting Domain, Anatomy of /etc/pam.d Entries
    plaintext, The Special Case of Windows 9x/Me
    password aging, Account Management Tools
    password assigned, Completing an NT4 Domain Trust
    password backend, Reference Documentation Server, Listing User and Machine Accounts
    password backends, Account Information Databases
    password change facility, Enabling SWAT for Use
    password database, Backup Domain Controller Configuration, Samba as the Trusted Domain
    password encryption, Plaintext
    password expiration, smbpasswd: Encrypted Password Database
    password expired, Changing User Accounts
    password history, Single Sign-On and Domain Security
    password management, Pluggable Authentication Modules
    password prompt, Advantages of Encrypted Passwords
    password scheme, Important Notes About Security
    password server, Server Security (User Level Security), Configure smb.conf
    password uniqueness, Single Sign-On and Domain Security
    passwords, Introduction
    patch, Patches
    path specified, Adding Machine to Domain Fails
    pauses, Samba Performance is Very Slow
    PBM, MIME Types and CUPS Filters
    PCL, GDI on Windows, PostScript on UNIX, Windows Drivers, GDI, and EMF, UNIX Printfile Conversion and GUI Basics, Printing with Interface Scripts, Driver Execution on the Server, Network PostScript RIP
    pdbedit, Example: Engineering Office, Account Management Tools, The pdbedit Tool, User Account Management, Listing User and Machine Accounts, Adding User Accounts, Deleting Accounts, Changing User Accounts, Account Flags Management, Account Import/Export, The Administrator Domain SID, Samba PDC, Quick Migration Guide, Passdb Backends and Authentication, Steps in Migration Process, Samba-3 Implementation Choices
    pdb_ldap, Can I Do This All with LDAP?
    PDC, Domain Security Mode (User-Level Security), Example Configuration, Domain Controller Types, Security Mode and Master Browsers, Features and Benefits, MS Windows NT4-style Domain Control, Example PDC Configuration, LDAP Configuration Notes, What Qualifies a Domain Controller on the Network?, Backup Domain Controller Configuration, Example Configuration, Can Samba Be a Backup Domain Controller to an NT4 PDC?, MS Windows Workstation/Server Machine Trust Accounts, Manual Creation of Machine Trust Accounts, Joining an NT4-type Domain with Samba-3, Why Is This Better Than security = server?, Adding Machine to Domain Fails, Configuring Workgroup Browsing, Domain Browsing Configuration, New Account Storage Systems, Advantages of Encrypted Passwords, tdbsam, LDAP Special Attributes for sambaSamAccounts, Discussion, Overview, Domain Member Server or Domain Member Client, Primary Domain Controller, Samba as the Trusted Domain, Samba as the Trusting Domain, cupsaddsmb with a Samba PDC, Handling of Foreign SIDs, Microsoft Remote Procedure Calls, Pluggable Authentication Modules, Result Caching, Introduction, Join the Samba Server to the PDC Domain, Starting and Testing the winbindd Daemon, Remote Management from NoMachine.Com, New Schema, Domain Layout, Getting Mailing List Help, Corrupt tdb Files
    PDF, Simple smb.conf Settings for CUPS, Windows Drivers, GDI, and EMF, PostScript Printer Description (PPD) Specification, MIME Types and CUPS Filters, Prefilters, Examples for Filtering Chains
    pdf, MIME Type Conversion Rules
    PDF distilling, PostScript Printer Description (PPD) Specification
    PDF filter, Central Print Serving
    pdftops, MIME Type Conversion Rules, Examples for Filtering Chains
    pdftosocket, Examples for Filtering Chains
    PDL, GDI on Windows, PostScript on UNIX, PostScript and Ghostscript, PostScript Printer Description (PPD) Specification
    PDM, PDM Data Shares
    peer domain, Configuring Samba NT-Style Domain Trusts
    Peer node, Static WINS Entries
    per-share access control, Access Controls on Shares
    performance, Handling Large Directories, Objectives
    performance advantage, Features and Benefits
    performance degradation, Handling Large Directories
    performance enhancement, Opportunistic Locking Overview
    performance improvement, Slow and/or Unreliable Networks
    performance-based, tdbsam
    performed as root, Using the “net rpc rights” Utility
    perimeter firewall, Features and Benefits
    permanent changes, Samba-3 Implementation Choices
    Permanent name, Static WINS Entries
    permissions, Why Can Users Access Other Users' Home Directories?, Shadow Copy Setup
    file/directory ACLs, Managing UNIX Permissions Using NT Security Dialogs
    share, Share Definition Access Controls
    share ACLs, Access Controls on Shares
    UNIX file and directory, Features and Benefits
    Permissions, Windows 200x/XP
    permissions and controls, Features and Benefits
    PGP, Verifying Samba's PGP Signature
    phasing out NetBIOS, Discussion
    Photo-CD, MIME Types and CUPS Filters
    physical locations, Features and Benefits
    physical network transport layer, /etc/hosts
    PID, Attaching to a Running Process
    pid directory, Multiple Server Hosting
    ping, Domain Layout, The Tests
    pipe device, File and Directory Access Control
    PJL, Network PostScript RIP, Windows CUPS PostScript Driver Versus Adobe Driver, Adobe and CUPS PostScript Drivers for Windows Clients
    PJL-header, Adobe and CUPS PostScript Drivers for Windows Clients
    plague network users, TCP/IP Configuration
    plain-text
    passwords, Password Checking
    plaintext, Backward Compatibility Account Storage Systems
    plaintext authentication, Backward Compatibility Account Storage Systems
    plaintext password, The Special Case of Windows 9x/Me, How Do I Replicate the smbpasswd File?
    plaintext passwords, Technical Information, Important Notes About Security
    platforms, Portability
    PLP, The [global] Section
    Pluggable Authentication Modules (see PAM)
    PNG, Ghostscript: The Software RIP for Non-PostScript Printers, MIME Types and CUPS Filters
    PNM, MIME Types and CUPS Filters
    point 'n' print, Installation of Windows Client Drivers, Run cupsaddsmb (Quiet Mode), Manual Driver Installation in 15 Steps
    Point'n'Print, Features and Benefits, Printing Developments Since Samba-2.2, Point'n'Print Client Drivers on Samba Servers, smbclient to Confirm Driver Installation
    point'n'print, Driver Upload Methods, The Role of cupsomatic/foomatic, Installing the PostScript Driver on a Client
    Poledit, Administration of Windows 200x/XP Policies
    poledit.exe, Creating and Managing System Policies, Windows NT4-Style Policy Files, Administration of Windows 200x/XP Policies
    Policies, Creating and Managing System Policies, Managing Account/User Policies
    policies, Samba-3 Implementation Choices
    policy editor, Creating and Managing System Policies
    Policy Editor, Windows NT4-Style Policy Files
    policy file , Managing Account/User Policies
    policy files, Features and Benefits
    policy settings, The pdbedit Tool
    port 135, Multiple Interfaces
    Port 135/TCP, Using a Firewall
    port 137, Multiple Interfaces, The Tests
    Port 137/UDP, Using a Firewall
    port 138, Multiple Interfaces
    Port 138/UDP, Using a Firewall
    port 139, Multiple Interfaces
    Port 139/TCP, Using a Firewall
    port 445, Multiple Interfaces
    Port 445/TCP, Using a Firewall
    ports, Verifying Configuration with testparm, Ethereal
    POSIX, Backup Domain Controller Configuration, LDAP Directories and Windows Computer Accounts, Accounts and Groups Management, Adding or Creating a New Group
    POSIX account, User Account Management, UNIX and Windows User Management
    POSIX ACLs, File and Directory Access Control, Protecting Directories and Files from Deletion
    POSIX ACLS, Samba-3 Implementation Choices
    POSIX identity, Caution Regarding LDAP and Samba
    POSIX locks, Server Pool Communications
    POSIX semantics, Server Pool Communications
    POSIX user accounts, Interdomain Trust Relationships
    posixAccount, Schema and Relationship to the RFC 2307 posixAccount, OpenLDAP Configuration
    posixGroup, OpenLDAP Configuration, Accounts and Groups Management
    PostScript, Simple smb.conf Settings for CUPS, Advanced Intelligent Printing with PostScript Driver Download, GDI on Windows, PostScript on UNIX, Windows Drivers, GDI, and EMF, UNIX Printfile Conversion and GUI Basics, PostScript and Ghostscript, PostScript Printer Description (PPD) Specification, Using Windows-Formatted Vendor PPDs, MIME Types and CUPS Filters, Prefilters, pstops, PostScript Printer Descriptions for Non-PostScript Printers, Examples for Filtering Chains, Driver Execution on the Server, Network PostScript RIP, CUPS: A “Magical Stone”?, PostScript Drivers with No Major Problems, Even in Kernel -Mode, CUPS “PostScript Driver for Windows NT/200x/XP”
    (see also Ghostscript)
    RIP, PostScript and Ghostscript
    PostScript driver, Installing Driver Files into [print$]
    PostScript interpreter, PostScript and Ghostscript
    PostScript Printer Description (see PPD)
    PostScript printers, Printing from CUPS to Windows-Attached Printers
    potential master browsers, Forcing Samba to Be the Master
    potential printer, [print$] Stanza Parameters
    Power Users, What Rights and Privileges Will Permit Windows Client Administration?
    powerful, Domain Controller Types
    PPD, Installing Driver Files into [print$], PostScript and Ghostscript, PostScript Printer Description (PPD) Specification, CUPS Also Uses PPDs for Non-PostScript Printers, MIME Types and CUPS Filters, “Raw” Printing, PostScript Printer Descriptions for Non-PostScript Printers, PPDs for Non-PS Printers on UNIX, PPDs for Non-PS Printers on Windows, CUPS: A “Magical Stone”?, Installing the PostScript Driver on a Client, Adobe and CUPS PostScript Drivers for Windows Clients, Printing from CUPS to Windows-Attached Printers
    CUPS (see CUPS-PPD)
    PPD-aware, PostScript and Ghostscript
    PPDs, Using Windows-Formatted Vendor PPDs, The Role of cupsomatic/foomatic, The Grand Unification Achieved
    PPP, Using Interface Protection
    precedence, Forcing Samba to Be the Master
    preferred master, Domain Control: Example Configuration
    prefilter, imagetops and imagetoraster
    prefilters, Prefilters
    primary domain controller, Multiple Virtual Server Hosting
    primary group, Manual Creation of Machine Trust Accounts
    Primary Logon, Windows 9x/Me Profile Setup
    Primary WINS Server, WINS Server Configuration
    print, Verifying Configuration with testparm
    queue, Configuration File Syntax
    spooler, Configuration File Syntax
    print accounting, Features and Benefits
    print command, Print Commands
    print commands, Custom Print Commands
    print configuration, Technical Introduction, Verifying Configuration with testparm
    print environment, Simple Print Configuration
    print filtering, Technical Introduction
    print job, Custom Print Commands
    print jobs, The [global] Section
    print processing, Technical Introduction
    print queue, Point'n'Print Client Drivers on Samba Servers, smbclient to Confirm Driver Installation, Specific Driver Name Flexibility, CUPS Backends
    print quota, Advanced Intelligent Printing with PostScript Driver Download
    print server, Central Print Serving, Features and Benefits
    print service, Features and Benefits
    print spooling, Microsoft Remote Procedure Calls
    print spooling system, Overview
    print statistics, Advanced Intelligent Printing with PostScript Driver Download
    print subsystem, Technical Introduction, Print Commands
    print test page, First Client Driver Installation
    printcap, Configuration File Syntax, The [global] Section, The [printers] Section
    Printcap, Basic CUPS Support Configuration
    printcap name, Central Print Serving
    PrintcapFormat, Basic CUPS Support Configuration
    printer attributes publishing, New Features in Samba-3.0.x
    printer default permissions, Printing Developments Since Samba-2.2
    printer driver, The Obsoleted [printer$] Section, Creating the [print$] Share, Simple smb.conf Settings for CUPS
    printer driver data, Setting Device Modes on New Printers
    printer driver file, The Obsoleted [printer$] Section
    printer driver files, smbclient to Confirm Driver Installation
    printer drivers, Point'n'Print Client Drivers on Samba Servers, The Grand Unification Achieved
    printer icon, Check Samba for Driver Recognition
    printer management, Overview
    printer management system, Overview
    printer migration, Overview
    printer monitor, Samba Performance is Very Slow
    printer objects, Printing Developments Since Samba-2.2
    Printer Pooling, Samba and Printer Ports
    printer queue, Printing Developments Since Samba-2.2
    printer share, The [global] Section
    printer shares , Verifying Configuration with testparm, The [global] Section
    printer$ share, The Obsoleted [printer$] Section
    printers, Configuration File Syntax, Features and Benefits
    Printers, The [global] Section
    printers admin, Description of Privileges
    Printers and Faxes, Check Samba for Driver Recognition
    printers available, What Is Browsing?
    printers section, The [printers] Section
    printing, The [global] Section
    printing behavior, Printing-Related Configuration Parameters
    printing calls, Printing Developments Since Samba-2.2
    printing now, Samba Performance is Very Slow
    printing support, Features and Benefits, Technical Introduction
    printing system, Technical Introduction
    printing systems, Comments Regarding LDAP
    printing-related settings, Verifying Configuration with testparm
    printing.tdb, Setting Device Modes on New Printers, The Printing *.tdb Files
    (see also TDB)
    PrintPro (see ESP Print Pro)
    private dir, Multiple Server Hosting
    private groups, Warning: User Private Group Problems
    private key, Securing SWAT through SSL
    private network, Introduction
    private networks, Using Host-Based Protection
    private/MACHINE.SID, Backup Domain Controller Configuration
    private/secrets.tdb, Backup Domain Controller Configuration
    privilege, Applicable Only to Versions Earlier than 3.0.11, Description of Privileges
    privilege management, Important Administrative Information, Administering User Rights and Privileges
    privilege model, Rights Management Capabilities
    privilege-granting applications, Technical Discussion
    privileged accounts, Using the “net rpc rights” Utility
    privileges, Single Sign-On and Domain Security, Windows 200x/XP Professional Client, Applicable Only to Versions Earlier than 3.0.11, Rights Management Capabilities, Description of Privileges, Trust Relationship Background, Printing Developments Since Samba-2.2
    privileges assigned, Using the “net rpc rights” Utility
    problem report, Free Support
    problem resolution, Samba Support
    problematic print, Technical Introduction
    Process data management, PDM Data Shares
    professional support, Free Support
    profile, Domain Control: Example Configuration, The Special Case of Windows 9x/Me, MS Windows NT4-style Domain Control, New Account Storage Systems, Technical Information
    profile access rights, Creating and Managing Group Profiles
    profile contents, Sharing Profiles between Windows 9x/Me and NT4/200x/XP Workstations
    profile directory, Windows 9x/Me Profile Setup
    profile migration tool, Creating and Managing Group Profiles
    profile path, Example PDC Configuration, Windows 9x/Me Profile Setup, Windows NT4 Workstation
    profile sharing, Sharing Profiles between Windows 9x/Me and NT4/200x/XP Workstations
    Profile Type, Disabling Roaming Profile Support
    ProfilePath, Windows 9x/Me Profile Setup
    profiles, The Special Case of Windows 9x/Me
    Profiles, Creating and Managing System Policies
    project, Free Support
    promiscuous mode, The Windows Network Monitor
    promote, Domain Controller Types
    promoted, MS Windows NT4-style Domain Control
    propagate, Features and Benefits
    Properties, MS Windows Me, Domain Logon Configuration: Windows 9x/Me
    protect directories, Protecting Directories and Files from Deletion
    protect files, Protecting Directories and Files from Deletion
    protection against attackers, Using IPC$ Share-Based Denials
    protocol stack settings, MS Windows 2000
    provided services, Samba Support
    provisioned, Single Sign-On and Domain Security
    pstops, Prefilters, pstops, Examples for Filtering Chains, Adobe and CUPS PostScript Drivers for Windows Clients
    pstoraster, pstoraster, cupsomatic/foomatic-rip Versus Native CUPS Printing, Adobe and CUPS PostScript Drivers for Windows Clients
    publish printers, Printing Developments Since Samba-2.2
    publishing printers, Rapid Configuration Validation
    PulseAudio, Remote Management with ThinLinc
    punching, pstops
    purchase support, Free Support
    put, The Tests
    pvcreate, Shadow Copy Setup

    Q

    QNX, The [global] Section
    qualified problem, Free Support
    queue control, The [global] Section
    quota controls, Comments Regarding LDAP

    R

    RAID, BackupPC
    random machine account password, Joining an NT4-type Domain with Samba-3
    range, UNIX and Windows User Management
    range of hosts, Using Host-Based Protection
    RAP, UNIX and Windows Group Management
    raster, Prefilters, Foomatic Database-Generated PPDs
    raster driver, The CUPS Filtering Architecture
    raster drivers, pstoraster
    raster image processor (see RIP)
    raster images, UNIX Printfile Conversion and GUI Basics
    rasterization, pstoraster, cupsomatic/foomatic-rip Versus Native CUPS Printing
    rastertoalps, rasterto [printers specific]
    rastertobj, rasterto [printers specific]
    rastertoepson, rasterto [printers specific], Examples for Filtering Chains
    rastertoescp, rasterto [printers specific]
    rastertohp, rasterto [printers specific]
    rastertopcl, rasterto [printers specific]
    rastertoprinter, rasterto [printers specific]
    rastertosomething, cupsomatic/foomatic-rip Versus Native CUPS Printing
    rastertoturboprint, rasterto [printers specific]
    raw mode, application/octet-stream Printing
    raw print, cupsaddsmb Flowchart
    raw printers, Overview
    raw printing, Anonymous Print Server, Central Print Serving, Raw Print Serving: Vendor Drivers on Windows Clients, Explicitly Enable “raw” Printing for application/octet-stream
    raw SMB, Features and Benefits
    raw SMB over TCP/IP, TCP/IP without NetBIOS
    rawprinter, “Raw” Printing
    rcp, Rsync
    rdesktop, Remote Management from NoMachine.Com
    rdesktop/RDP, Remote Management from NoMachine.Com
    read, File and Directory Access Control
    read directory into memory, Handling Large Directories
    read only, fake_perms
    server, Anonymous Read-Only Document Server
    Read-ahead, Opportunistic Locking Overview
    read-only, Features and Benefits, Reference Documentation Server
    read-only access, Backup Domain Controller, Multiple Virtual Server Personalities
    read-only files, Features and Benefits
    read-write access, The Obsoleted [printer$] Section
    realm, ADS Security Mode (User-Level Security), NetBIOS Over TCP/IP Disabled, Configure smb.conf, Configure /etc/krb5.conf, IDMAP_RID with Winbind, IDMAP Storage in LDAP Using Winbind
    rebooted, Joining a Domain: Windows 2000/XP Professional, Configuring Workgroup Browsing
    rebooting server, Description of Privileges
    recompiling, Multiple Server Hosting
    reconfiguration, MS Windows NT4-style Domain Control
    record locking, Discussion
    recycle, recycle
    recycle bin, Discussion
    recycle directory, recycle
    recycle:exclude, recycle
    recycle:exclude_dir, recycle
    recycle:keeptree, recycle
    recycle:maxsize, recycle
    recycle:noversions, recycle
    recycle:repository, recycle
    recycle:subdir_mode, recycle
    recycle:touch, recycle
    recycle:versions, recycle
    Red Hat Cluster Manager, High-Availability Server Products
    Red Hat Linux, LDAP Configuration Notes, On-the-Fly Creation of Machine Trust Accounts, Warning: User Private Group Problems
    redirect, Example Configuration
    redirection, What Winbind Provides
    redirector, Opportunistic Locking Overview
    redundancy, NetBIOS over TCP/IP
    reference documents, Reference Documentation Server
    refusing connection, Using Interface Protection
    regedit.exe, MS Windows 9x/Me
    regedt32, MS Windows NT4 Workstation
    regedt32.exe, Windows NT4/200x
    register driver files, Running rpcclient with adddriver
    register NetBIOS names, How Browsing Functions
    registered, WINS: The Windows Internetworking Name Server, Check Samba for Driver Recognition
    registers, Domain Browsing Configuration
    registry, Domain Controller Types, Technical Information, Features and Benefits, Creating and Managing System Policies, Windows 9x/ME Policies, MS Windows 200x/XP Professional Policies, MS Windows 9x/Me
    registry change, Important Notes About Security
    registry keys, Default Profile for Windows Users
    registry settings, Managing Account/User Policies
    regulations, The pdbedit Tool
    rejoin, Managing Security Identifiers (SIDS)
    relationship password, Samba as the Trusted Domain
    relative identifier, smbpasswd: Encrypted Password Database (see RID)
    Relative Identifier (see RID)
    Relative Identifiers (see RID)
    reliability, Features and Benefits, Objectives
    Remote Access Dial-In User Service (see RADIUS)
    remote announce, Cross-Subnet Browsing
    remote browse sync, Cross-Subnet Browsing
    remote desktop capabilities, Remote Management from NoMachine.Com
    remote desktop management, Remote Desktop Management
    remote domain, Creating an NT4 Domain Trust, Completing an NT4 Domain Trust, Samba as the Trusted Domain
    remote login, Remote Management from NoMachine.Com
    remote management, Remote and Local Management: The Net Command, Microsoft Remote Procedure Calls
    Remote Procedure Call (see RPC)
    Remote Procedure Call System Service (see RPCSS)
    remote profile, Windows 9x/Me Profile Setup
    remote segment, Use of the Remote Browse Sync Parameter, Domain Layout
    Remote X, Remote Management from NoMachine.Com
    Remote X protocol, Remote Management from NoMachine.Com
    remote-update protocol, Rsync
    rename, Managing Directories
    render, Raw Print Serving: Vendor Drivers on Windows Clients
    rendering, cupsomatic/foomatic-rip Versus Native CUPS Printing
    repeated intervals, NetBIOS over TCP/IP
    replicate, Backup Domain Controller Configuration, smbpasswd: Encrypted Password Database
    replicated, Features and Benefits, Features and Benefits, Active Directory Domain Control, Backup Domain Controller Configuration, MS Windows 200x/XP Professional Policies
    replicated SYSVOL, MS Windows 200x/XP Professional Policies
    replication, Features and Benefits, LDAP Configuration Notes
    browse lists, Cross-Subnet Browsing
    SAM, Domain Controller Types, Features and Benefits, MS Windows NT4-style Domain Control, Backup Domain Controller Configuration, Can Samba Be a Backup Domain Controller to an NT4 PDC?, How Do I Replicate the smbpasswd File?
    WINS, NetBIOS over TCP/IP, WINS Server Configuration, WINS Replication
    replication protocols, WINS Server Configuration
    repository, Domain Member Server or Domain Member Client
    requesting payment, Free Support
    required, Anatomy of /etc/pam.d Entries
    requisite, Anatomy of /etc/pam.d Entries
    research, Discussion of Backup Solutions
    resizing, Shadow Copy Setup
    resolution, The Role of cupsomatic/foomatic
    resolution of NetBIOS names, Network Browsing
    resolve NetBIOS names, Making Samba the Domain Master
    resolver functions, Name Service Switch
    resource failover, High-Availability Server Products
    resource kit, Administration of Windows 200x/XP Policies, Windows NT4 Profile Management Tools
    resource-based exclusion, Features and Benefits
    response, IDMAP_RID with Winbind
    restrict DNS, Name Resolution Order
    reviewers, Advanced Configuration Techniques
    revoke privileges, Using the “net rpc rights” Utility
    RFC 1001, Example Configuration
    RFC 1002, Example Configuration
    RFC 1179, The [global] Section
    RFC 2307, Mapping Common UIDs/GIDs on Distributed Machines
    RFC 2307., Schema and Relationship to the RFC 2307 posixAccount
    RFC 2830, Introduction
    rfc2307bis, IDMAP and NSS Using LDAP from ADS with RFC2307bis Schema Extension
    RFC2830, LDAP Configuration Notes
    RFCs, Analyzing and Solving Samba Problems
    rich database backend, New Account Storage Systems
    rich directory backend, New Account Storage Systems
    RID, Features and Benefits, Manual Creation of Machine Trust Accounts, User and Group Changes, Discussion, Default Users, Groups, and Relative Identifiers, Domain Member Server or Domain Member Client, Primary Domain Controller, IDMAP_RID with Winbind, The Administrator Domain SID, User and Group ID Allocation, New Schema
    RID 500, The Administrator Domain SID
    RID base, Primary Domain Controller
    right to join domain, Description of Privileges
    rights, Single Sign-On and Domain Security, The Special Case of Windows 9x/Me, Possible Errors, Rights Management Capabilities
    rights and privilege, Administering User Rights and Privileges
    rights and privileges, Important Administrative Information, The Administrator Domain SID
    rights assigned, Rights Management Capabilities, Using the “net rpc rights” Utility
    RIP, PostScript Printer Descriptions for Non-PostScript Printers
    rlogind, Anatomy of /etc/pam.d Entries
    Roaming Profile, fake_perms
    roaming profiles, Preparing for Domain Control, Features and Benefits, Disabling Roaming Profile Support, Windows 9x/Me Profile Setup
    rogue machine, Flushing the Samba NetBIOS Name Cache
    rogue user, MS Windows Workstation/Server Machine Trust Accounts
    root, Windows 200x/XP Professional Client, Joining a Domain: Windows 2000/XP Professional, User Rights and Privileges
    root account, User Rights and Privileges, The Administrator Domain SID
    root user, Using the “net rpc rights” Utility
    rotate, UNIX Printfile Conversion and GUI Basics
    RPC, Why Is This Better Than security = server?, Features and Benefits, Join the Samba Server to the PDC Domain, Roaming Profiles
    RPC calls, Conclusion, The Front-End Challenge
    RPC modules, New Features in Samba-3.0.x
    rpc.lockd, Discussion
    rpcclient, Remote and Local Management: The Net Command, Identifying Driver Files, Specific Driver Name Flexibility, Troubleshooting Revisited, Samba PDC
    adddriver, Run cupsaddsmb with Verbose Output, Understanding cupsaddsmb, Installing PostScript Driver Files Manually Using rpcclient, Understanding the rpcclient man Page, Requirements for adddriver and setdriver to Succeed, Manual Driver Installation in 15 Steps
    enumdrivers, Installing PostScript Driver Files Manually Using rpcclient, Manual Driver Installation in 15 Steps
    enumports, Installing PostScript Driver Files Manually Using rpcclient
    enumprinters, Installing PostScript Driver Files Manually Using rpcclient, Requirements for adddriver and setdriver to Succeed, Manual Driver Installation in 15 Steps, Troubleshooting Revisited
    getdriver, Producing an Example by Querying a Windows Box, Manual Driver Installation in 15 Steps
    getprinter, Producing an Example by Querying a Windows Box, Manual Driver Installation in 15 Steps, Troubleshooting Revisited
    setdriver, Caveats to Be Considered, Run cupsaddsmb with Verbose Output, Understanding cupsaddsmb, Installing PostScript Driver Files Manually Using rpcclient, Requirements for adddriver and setdriver to Succeed, Manual Driver Installation in 15 Steps
    rsh, BackupPC
    rsync, Backup Domain Controller Configuration, How Do I Replicate the smbpasswd File?, Mapping Common UIDs/GIDs on Distributed Machines, smbpasswd: Encrypted Password Database, BackupPC, Rsync, Accessing the Samba Sources via rsync and ftp
    rsyncd, BackupPC
    runas, Always Make First Client Connection as root or “printer admin”
    rundll32, Additional Client Driver Installation, Setting Default Print Options for Client Drivers, Manual Driver Installation in 15 Steps, Adding Printers without User Intervention

    S

    SAM, Features and Benefits, Domain Controller Types, MS Windows NT4-style Domain Control, Machine Accounts Keep Expiring, Can Samba Be a Backup Domain Controller to an NT4 PDC?, How Do I Replicate the smbpasswd File?, Features and Benefits, User and Group Changes, Backward Compatibility Account Storage Systems, Mapping User Identifiers between MS Windows and UNIX, Result Caching
    delta file, MS Windows NT4-style Domain Control
    replication, Domain Controller Types, MS Windows NT4-style Domain Control
    SAM backend, Mapping Common UIDs/GIDs on Distributed Machines, Comments Regarding LDAP
    LDAP, Features and Benefits
    ldapsam, Features and Benefits, New Account Storage Systems, Mapping Common UIDs/GIDs on Distributed Machines, ldapsam
    ldapsam_compat, Features and Benefits
    non-LDAP, Features and Benefits
    smbpasswd, Features and Benefits, smbpasswd: Encrypted Password Database
    tdbsam, Features and Benefits, New Account Storage Systems, tdbsam
    Samba 1.9.17, WINS Server Configuration
    Samba account, Manual Creation of Machine Trust Accounts
    Samba administrator, Introduction
    Samba backend database, Adding Machine to Domain Fails
    Samba daemons, Joining an NT4-type Domain with Samba-3
    Samba differences, Upgrading from Samba-2.x to Samba-3.0.25
    Samba mailing lists, Features and Benefits
    Samba private directory, Create the Computer Account
    Samba SAM, Mapping User Identifiers between MS Windows and UNIX
    Samba SAM account, Adding Machine to Domain Fails
    Samba SAM account flags, Account Flags Management
    Samba schema, New Account Storage Systems
    Samba security, Features and Benefits
    Samba-2.2.x LDAP schema, Backward Compatibility Account Storage Systems
    Samba-3-compatible LDAP backend, Quick Migration Guide
    Samba-PDC-LDAP-HOWTO, ldapsam
    samba-to-samba trusts, Interdomain Trust Relationships
    samba-vscan, vscan
    samba.schema, Schema and Relationship to the RFC 2307 posixAccount, OpenLDAP Configuration, New Schema
    sambaDomain, New Schema
    sambaGroupMapping, New Schema
    sambaHomeDrive, LDAP Special Attributes for sambaSamAccounts
    sambaHomePath, LDAP Special Attributes for sambaSamAccounts
    sambaIdmapEntry, New Schema
    sambaLogonScript, LDAP Special Attributes for sambaSamAccounts
    SambaNTPassword, Security and sambaSamAccount
    sambaProfilePath, LDAP Special Attributes for sambaSamAccounts
    SambaSAMAccount, Backup Domain Controller Configuration, Account Management Tools, Adding User Accounts, Deleting Accounts, Changing User Accounts, tdbsam
    sambaSamAccount, LDAP Directories and Windows Computer Accounts, Schema and Relationship to the RFC 2307 posixAccount, OpenLDAP Configuration, Accounts and Groups Management, LDAP Special Attributes for sambaSamAccounts, New Schema
    sambaSAMAccount, Security and sambaSamAccount
    sambaSID, LDAP Changes in Samba-3.0.23
    sambaUNIXIdPool, New Schema
    SambaXP conference, Technical Discussion
    samdb interface, smbpasswd: Encrypted Password Database
    same domain/workgroup, Multiple Virtual Server Hosting
    Sarbanes-Oxley, The pdbedit Tool
    scalability, Features and Benefits, Features and Benefits, Account Information Databases, tdbsam, Features and Benefits
    scalable, Comments Regarding LDAP
    scalable backend, Features and Benefits
    scalable coherent interface (see SCI)
    scale, UNIX Printfile Conversion and GUI Basics
    scanner module, Discussion
    schannel, Cannot Log onto Domain Member Workstation After Joining Domain
    schema, IDMAP and NSS Using LDAP from ADS with RFC2307bis Schema Extension
    schema file, New Account Storage Systems
    scp, Rsync
    script, Adding Machine to Domain Fails
    scripted control, Remote and Local Management: The Net Command
    scripts, Browsing Support in Samba, Caution Regarding LDAP and Samba
    SCSI, High-Availability Server Products
    SeAddUsersPrivilege, Administering User Rights and Privileges, Rights Management Capabilities, Description of Privileges
    SeAssignPrimaryTokenPrivilege, Privileges Suppored by Windows 2000 Domain Controllers
    SeAuditPrivilege, Privileges Suppored by Windows 2000 Domain Controllers
    SeBackupPrivilege, Administering User Rights and Privileges, Privileges Suppored by Windows 2000 Domain Controllers
    SeChangeNotifyPrivilege, Privileges Suppored by Windows 2000 Domain Controllers
    Seclib, Viewing File Ownership
    secondary controller, Domain Layout
    SeCreateGlobalPrivilege, Privileges Suppored by Windows 2000 Domain Controllers
    SeCreatePagefilePrivilege, Privileges Suppored by Windows 2000 Domain Controllers
    SeCreatePermanentPrivilege, Privileges Suppored by Windows 2000 Domain Controllers
    SeCreateTokenPrivilege, Privileges Suppored by Windows 2000 Domain Controllers
    secret, Important Notes About Security
    secrets.tdb, Backup Domain Controller Configuration, Sharing User ID Mappings between Samba Domain Members, Initialize the LDAP Database, The Printing *.tdb Files
    (see also TDB)
    section name, Configuration File Syntax
    secure, Features and Benefits
    secure access, Single Sign-On and Domain Security
    secure authentication, User Rights and Privileges
    secure communications, Security and sambaSamAccount
    secured networks, Introduction
    security, Samba Security Modes, Preparing for Domain Control, Introduction, Multiple Virtual Server Personalities
    controllers, Domain Security Mode (User-Level Security)
    modes, Features and Benefits
    settings, Example Configuration
    security = user, Joining an NT4-type Domain with Samba-3
    security account, Overview
    Security Account Manager (see SAM)
    Security Assertion Markup Language (see SAML)
    security context, Domain Member Server
    security contexts, Trust Relationship Background
    security credentials, Backup Domain Controller, Native MS Windows NT4 Trusts Configuration
    security domain, Trust Relationship Background
    security domains, Trust Relationship Background
    security flaw, Why Can Users Access Other Users' Home Directories?
    security hole, Using IPC$ Share-Based Denials
    security identifier, Managing Security Identifiers (SIDS) (see SID)
    security level, Server Security (User Level Security)
    security levels, Samba Security Modes
    security mode, Server Types and Security Modes, Security Mode and Master Browsers
    Security Mode, Samba Security Modes
    security modes, Samba Security Modes
    security name-space, Identity Mapping (IDMAP)
    security policies, Why Can Users Access Other Users' Home Directories?
    security settings, New Features in Samba-3.0.x
    security structure, Trust Relationship Background
    security vulnerability, Upgrading Samba
    security-aware, application/octet-stream Printing
    SeDebugPrivilege, Privileges Suppored by Windows 2000 Domain Controllers
    SeDiskOperatorPrivilege, Administering User Rights and Privileges, Rights Management Capabilities, Description of Privileges
    SeEnableDelegationPrivilege, Privileges Suppored by Windows 2000 Domain Controllers
    SeImpersonatePrivilege, Privileges Suppored by Windows 2000 Domain Controllers
    SeIncreaseBasePriorityPrivilege, Privileges Suppored by Windows 2000 Domain Controllers
    SeIncreaseQuotaPrivilege, Privileges Suppored by Windows 2000 Domain Controllers
    SeLoadDriverPrivilege, Privileges Suppored by Windows 2000 Domain Controllers
    SeLockMemoryPrivilege, Privileges Suppored by Windows 2000 Domain Controllers
    SeMachineAccountPrivilege, Administering User Rights and Privileges, Rights Management Capabilities, Description of Privileges, Privileges Suppored by Windows 2000 Domain Controllers
    SeManageVolumePrivilege, Privileges Suppored by Windows 2000 Domain Controllers
    separate instances, Multiple Server Hosting
    separate servers, Advanced Configuration Techniques
    separate shares, The [global] Section
    separate workgroups, Multiple Virtual Server Personalities
    SePrintOperatorPrivilege, Administering User Rights and Privileges, Rights Management Capabilities, Description of Privileges
    SeProfileSingleProcessPrivilege, Privileges Suppored by Windows 2000 Domain Controllers
    SeRemoteShutdownPrivilege, Administering User Rights and Privileges, Rights Management Capabilities, Description of Privileges, Privileges Suppored by Windows 2000 Domain Controllers
    SeRestorePrivilege, Administering User Rights and Privileges, Privileges Suppored by Windows 2000 Domain Controllers
    server failure, Why Is This So Hard?
    Server Manager, MS Windows Workstation/Server Machine Trust Accounts, Manual Creation of Machine Trust Accounts, Managing Domain Machine Accounts using NT4 Server Manager, Remote Server Administration
    Server Manager for Domains, Managing Domain Machine Accounts using NT4 Server Manager
    Server Message Block (see SMB)
    server pool, The Distributed File System Challenge, Restrictive Constraints on Distributed File Systems
    Server Type, Server Types
    Domain Controller, Domain Controller
    Domain Member, Domain Member Server, Example Configuration, Features and Benefits
    Stand-alone, Standalone Server
    server type, Overview
    domain member, Example Configuration
    Server Types, Samba Server Deployment Types and IDMAP
    server-mode, What Makes Samba a Domain Controller?
    service name, Example Configuration
    service-level, Printing-Related Configuration Parameters, The [global] Section
    services provided, Samba Support
    SeSecurityPrivilege, Privileges Suppored by Windows 2000 Domain Controllers
    SeShutdownPrivilege, Privileges Suppored by Windows 2000 Domain Controllers
    session, Anatomy of /etc/pam.d Entries
    session services, Features and Benefits
    session setup, User Level Security, Server Security (User Level Security)
    sessionid.tdb, The Printing *.tdb Files
    (see also TDB)
    SessionSetupAndX, Domain Member Server or Domain Member Client
    SeSyncAgentPrivilege, Privileges Suppored by Windows 2000 Domain Controllers
    SeSystemEnvironmentPrivilege, Privileges Suppored by Windows 2000 Domain Controllers
    SeSystemProfilePrivilege, Privileges Suppored by Windows 2000 Domain Controllers
    SeSystemtimePrivilege, Privileges Suppored by Windows 2000 Domain Controllers
    set a password, Central Print Serving
    set group id (see SGID)
    set printer properties, The [global] Section
    set user id (see SUID)
    SeTakeOwnershipPrivilege, Administering User Rights and Privileges, Rights Management Capabilities, Description of Privileges, Privileges Suppored by Windows 2000 Domain Controllers
    SeTcbPrivilege, Privileges Suppored by Windows 2000 Domain Controllers
    setdriver, A Check of the rpcclient man Page, Requirements for adddriver and setdriver to Succeed
    SetPrinter(), A Check of the rpcclient man Page
    setting up directories, File and Directory Access Control
    SeUndockPrivilege, Privileges Suppored by Windows 2000 Domain Controllers
    severely impaired, TCP/IP without NetBIOS
    SFU, IDMAP, Active Directory, and MS Services for UNIX 3.5
    SFU 3.5, Primary Domain Controller
    SGI-RGB, MIME Types and CUPS Filters
    SGID, File and Directory Access Control
    shadow, LDAP Directories and Windows Computer Accounts
    shadow copies, Shadow Copy Setup
    shadow password file, Joining an NT4-type Domain with Samba-3
    shadow utilities, Features and Benefits
    shadow_copy, shadow_copy, Shadow Copy Setup
    shadow_copy module, shadow_copy
    share, Configuration File Syntax, File, Directory, and Share Access Controls, The [global] Section
    share access, Access Controls on Shares
    share ACLs, Samba-3 Implementation Choices
    share management, Overview
    share modes, The Distributed File System Challenge
    share permissions, Windows NT4 Workstation/Server
    Share Permissions, Windows 200x/XP
    share settings, Features and Benefits
    share stanza controls, Samba-3 Implementation Choices
    share-level, Samba Security Modes, Share-Level Security, Features and Benefits
    share-level ACLs, Applicable Only to Versions Earlier than 3.0.11
    share-mode, Features and Benefits
    share-mode security, Security Mode and Master Browsers
    share-mode server, Features and Benefits
    shared secret, MS Windows Workstation/Server Machine Trust Accounts
    shares, What Is Browsing?
    shares and files, Requirements
    share_info.tdb, Access Controls on Shares, The Printing *.tdb Files
    (see also TDB)
    Sharing, Windows 200x/XP
    shell scripts, Print Commands
    shift, UNIX Printfile Conversion and GUI Basics
    Shift_JIS, Japanese Charsets, Basic Parameter Setting
    shortcuts, TCP/IP Configuration, Windows 9x/Me Profile Setup
    Shortcuts, MS Windows NTFS Comparison with UNIX File Systems
    show-stopper-type, Planning and Getting Started
    SID, Features and Benefits, The System Cannot Log You On (C000019B), Backup Domain Controller Configuration, Example Configuration, Why Is This Better Than security = server?, Sharing User ID Mappings between Samba Domain Members, User and Group Changes, Group Mapping Changes in Samba-3.0.23, Technical Information, Mapping User Identifiers between MS Windows and UNIX, LDAP Directories and Windows Computer Accounts, Group Mapping: MS Windows and UNIX, Features and Benefits, Managing Security Identifiers (SIDS), Identity Mapping (IDMAP), Domain Member Server or Domain Member Client, Primary Domain Controller, IDMAP_RID with Winbind, Rights Management Capabilities, The Administrator Domain SID, Features and Benefits, Handling of Foreign SIDs, Side Bar Notes, Get SID, Multiple Server Hosting, New Features in Samba-3.0.x, Profile Migration/Creation
    SID management, Overview
    SID-to-GID, Features and Benefits
    SIDs, Samba-3 Implementation Choices
    signing, Cannot Log onto Domain Member Workstation After Joining Domain
    simple access controls, Server Share and Directory Layout
    simple configuration, Example Configuration
    simple guide, Upgrading from Samba-2.x to Samba-3.0.25
    Simple Object Access Protocol (see SOAP)
    simple operation, New Account Storage Systems
    simple print server, Central Print Serving
    simple printing, Simple Print Configuration
    simplest
    configuration, Example Configuration
    simplicity, Features and Benefits
    Simplicity is king, Server Share and Directory Layout
    single DHCP server, MS Windows Me
    single repository, Account Information Databases
    single server, The Front-End Challenge
    single sign-on, Features and Benefits (see SSO)
    Single Sign-On, Caveats to Be Considered
    single-byte charsets, What Are Charsets and Unicode?
    single-logon, The Special Case of Windows 9x/Me
    single-sign-on, Objectives
    single-user mode, Requirements
    slapadd, Initialize the LDAP Database
    slapd, OpenLDAP Configuration
    slapd.conf, LDAP Changes in Samba-3.0.23, OpenLDAP Configuration, Security and sambaSamAccount
    slapd.pem, LDAP Configuration Notes
    slapindex, LDAP Changes in Samba-3.0.23
    slappasswd, Initialize the LDAP Database
    slave servers, Domain Layout
    slow browsing, Browsing of Shares and Directories is Very Slow
    slow network, Samba Performance Problem Due to Changing Linux Kernel
    slow network browsing, Invalid Cached Share References Affects Network Browsing
    slow performance, Samba Performance is Very Slow
    smart printers, Overview
    SMB, Server Security (User Level Security), I Can't Join a Windows 2003 PDC, Background, Features and Benefits, NetBIOS over TCP/IP, Technical Overview of Browsing, Using Interface Protection, Printing Developments Since Samba-2.2, Name Resolution as Used within MS Windows Networking, BackupPC, The Front-End Challenge, Server Pool Communications, Analyzing and Solving Samba Problems
    SMB encryption, Advantages of Encrypted Passwords
    SMB locks, Server Pool Communications
    SMB name, Name Resolution as Used within MS Windows Networking
    SMB networking, Diagnostics Tools
    SMB password, The smbpasswd Tool
    SMB Password, Features and Benefits
    SMB password encryption, Important Notes About Security
    smb ports, Multiple Virtual Server Personalities
    SMB printers, Administrator Cannot Install Printers for All Local Users
    SMB requests, Demultiplexing SMB Requests
    SMB semantics, The Distributed File System Challenge
    SMB server, Advantages of Encrypted Passwords
    SMB Server, Features and Benefits
    SMB services, Restrictive Constraints on Distributed File Systems
    SMB signing, I Can't Join a Windows 2003 PDC, New Features in Samba-3.0.x
    SMB state information, Demultiplexing SMB Requests
    SMB-based messaging, Discussion
    smb-cdserver.conf, Multiple Virtual Server Personalities
    smb.conf, Multiple Virtual Server Personalities
    SMB/CIFS, What Qualifies a Domain Controller on the Network?, I Can't Join a Windows 2003 PDC, Important Notes About Security, What Are Charsets and Unicode?
    SMB/CIFS server, Password Backends
    smbclient, Testing with smbclient, Installing Driver Files into [print$], smbclient to Confirm Driver Installation, BackupPC, The Tests, Debugging with Samba Itself
    smbd, Starting Samba, Example Configuration, Test Your Config File with testparm, Secure Read-Write File and Print Server, Example Configuration, smbpasswd: Encrypted Password Database, Schema and Relationship to the RFC 2307 posixAccount, Configuring Samba, Domain Member Server or Domain Member Client, NT4-Style Domains (Includes Samba Domains), Description of Privileges, Verifying Configuration with testparm, Rapid Configuration Validation, extd_audit, Features and Benefits, Testing Things Out, Join the Samba Server to the PDC Domain, Linux, Solaris, Server Pool Communications, Handling Large Directories, Multiple Server Hosting, Multiple Virtual Server Personalities, Debugging with Samba Itself
    smbgroupedit, Remote and Local Management: The Net Command
    smbgrpadd.sh, Sample smb.conf Add Group Script
    smbHome, LDAP Special Attributes for sambaSamAccounts
    smbldap-groupadd, Adding or Creating a New Group
    smbldap-tools, ldapsam
    smbpasswd, Example Configuration, Domain Control: Example Configuration, Backup Domain Controller Configuration, How Do I Replicate the smbpasswd File?, MS Windows Workstation/Server Machine Trust Accounts, Configure smb.conf, Sharing User ID Mappings between Samba Domain Members, Group Mapping Changes in Samba-3.0.23, Account Information Databases, Backward Compatibility Account Storage Systems, Account Management Tools, The smbpasswd Tool, The pdbedit Tool, User Account Management, Account Import/Export, smbpasswd: Encrypted Password Database, ldapsam, Schema and Relationship to the RFC 2307 posixAccount, Initialize the LDAP Database, Domain Member Server or Domain Member Client, Samba as the Trusted Domain, Samba PDC, Passdb Backends and Authentication, New Schema
    smbpasswd format, Listing User and Machine Accounts
    smbpasswd plaintext database, smbpasswd: Encrypted Password Database
    SMBsessetupX, The Special Case of Windows 9x/Me
    smbspool, Printing from CUPS to Windows-Attached Printers
    smbstatus, Avoid Being Connected to the Samba Server as the Wrong User, Attaching to a Running Process
    SMBtconX, The Special Case of Windows 9x/Me
    smbusers, User-Based Protection
    SMS, The Windows Network Monitor
    Snapshots, Shadow Copy Setup
    sniffer, The Special Case of Windows 9x/Me, Diagnostics Tools
    socket, Multiple Server Hosting
    socket address, Multiple Server Hosting
    SOFTQ printing system, The [global] Section
    Solaris, Mapping Common UIDs/GIDs on Distributed Machines, Configure Winbind and PAM, Remote Management with ThinLinc, Features and Benefits, Basic Parameter Setting
    Solaris 9, Solaris
    source code, Example Configuration
    space character, Adding Groups Fails
    special account, User Rights and Privileges, Samba as the Trusted Domain
    special section, [print$] Stanza Parameters
    special sections, The [global] Section
    special stanza, [print$] Stanza Parameters
    specific restrictions, Access Controls on Shares
    Specify an IP address, MS Windows Me
    spinning process, Attaching to a Running Process
    spool, Verifying Configuration with testparm
    directory, Configuration File Syntax
    spool files, Custom Print Commands
    spooled file, Technical Introduction
    spooler., Configuration File Syntax
    spooling, Custom Print Commands, Central Spooling vs. “Peer-to-Peer” Printing
    central, Central Spooling vs. “Peer-to-Peer” Printing
    peer-to-peer, Central Spooling vs. “Peer-to-Peer” Printing
    spooling path, Verifying Configuration with testparm
    spooling-only, Raw Print Serving: Vendor Drivers on Windows Clients
    SPOOLSS, Printing Developments Since Samba-2.2
    SQL, Passdb Changes
    SQUID, Single Sign-On and Domain Security
    SRV records, Configure /etc/krb5.conf, DNS and Active Directory
    SRV RR, Background Information
    SrvMgr.exe, Managing Domain Machine Accounts using NT4 Server Manager
    srvmgr.exe, Managing Domain Machine Accounts using NT4 Server Manager
    SRVTOOLS.EXE, Managing Domain Machine Accounts using NT4 Server Manager, Remote Server Administration
    ssh, Backup Domain Controller Configuration, How Do I Replicate the smbpasswd File?, smbpasswd: Encrypted Password Database, BackupPC
    SSH, smbclient to Confirm Driver Installation, Remote Management with ThinLinc
    SSL, Securing SWAT through SSL
    SSO, Single Sign-On and Domain Security, Features and Benefits, Comments Regarding LDAP
    stability, Objectives
    stack trace, Internal Errors
    stale network links, Invalid Cached Share References Affects Network Browsing
    stand-alone server, Standalone Samba Server
    standalone, Server Types, Preparing for Domain Control, Overview, Domain Member Server or Domain Member Client
    standalone filter, pstoraster
    standalone server, Joining an NT4-type Domain with Samba-3, Standalone Servers, Features and Benefits, Background, Adding User Accounts, Features and Benefits, Domain Layout
    standard confirmation, Creating an NT4 Domain Trust
    stanza, Configuration File Syntax, Handling Large Directories
    stapling, pstops
    StartDocPrinter, Printing Developments Since Samba-2.2
    starting samba
    nmbd, Starting Samba, Secure Read-Write File and Print Server, Example Configuration
    smbd, Starting Samba, Secure Read-Write File and Print Server, Example Configuration
    winbindd, Starting Samba, Example Configuration, Features and Benefits
    startsmb, Alternative: Starting smbd as a Daemon
    StartTLS, Security and sambaSamAccount
    startup
    process, Starting Samba
    startup script, Starting and Testing the winbindd Daemon
    state, Why Is This So Hard?
    state information, Why Is This So Hard?
    state of knowledge, Features and Benefits
    static WINS entries, Static WINS Entries
    status32 codes, New Features in Samba-3.0.x
    sticky bit, File and Directory Access Control, Server Share and Directory Layout
    storage mechanism, Account Management Tools
    storage methods, The smbpasswd Tool
    stphoto2.ppd, Examples for Filtering Chains
    strange delete semantics, Handling Large Directories
    stripped of comments, Features and Benefits
    strptime, Changing User Accounts
    stunnel, Securing SWAT through SSL
    su, Anatomy of /etc/pam.d Entries
    subnet mask, MS Windows XP Professional, MS Windows Me, The Tests
    subnets, NetBIOS over TCP/IP, Configuring Workgroup Browsing
    subscription, Free Support
    subsuffix parameters, New Suffix for Searching
    Subversion, Introduction, Access via Subversion
    successful join, Testing Server Setup
    successful migration, Objectives
    sufficient, Anatomy of /etc/pam.d Entries
    suffixes, MIME Types and CUPS Filters
    SUID, File and Directory Access Control
    Sun, Domain Member Server
    Sun ONE iDentity server, Features and Benefits
    Sun Solaris, Features and Benefits
    SUN-Raster, MIME Types and CUPS Filters
    support, Samba Support
    support exposure, Objectives
    SVN
    web, Access via ViewCVS
    SVRTOOLS.EXE, Features and Benefits
    SWAT, Configuring Samba (smb.conf), SWAT: The Samba Web Administration Tool
    swat, SWAT, Validate SWAT Installation, Locating the SWAT File, Enabling SWAT for Use
    enable, Enabling SWAT for Use
    security, Securing SWAT through SSL
    SWAT binary support, Validate SWAT Installation
    swat command-line options, Locating the SWAT File
    SWAT permission allowed, Enabling SWAT for Use
    symbolic links, Features and Benefits
    synchronization, Domain Controller Types, Security Mode and Master Browsers, WINS: The Windows Internetworking Name Server, Behavior of Cross-Subnet Browsing
    synchronization problems, Introduction
    synchronize, Backup Domain Controller Configuration, Configure /etc/krb5.conf, Use of the Remote Browse Sync Parameter, Behavior of Cross-Subnet Browsing
    synchronized, Backup Domain Controller Configuration
    syntax tolerates spelling errors, Simple Print Configuration
    system access controls, New Account Storage Systems
    system accounts, User Account Management
    system administrator, User Rights and Privileges
    system groups, Mapping Windows Groups to UNIX Groups
    system interface scripts, User Rights and Privileges
    system policies, Creating and Managing System Policies
    System Policy Editor, Creating and Managing System Policies, Administration of Windows 200x/XP Policies, MS Windows 9x/Me
    system security, Applicable Only to Versions Earlier than 3.0.11
    system tools, Features and Benefits
    SYSV, The [global] Section
    SYSVOL, MS Windows 200x/XP Professional Policies

    T

    tail, Assumptions
    take ownership, Description of Privileges
    Take Ownership, Viewing File Ownership
    tape, Server Share and Directory Layout
    tar, BackupPC
    tarball, Example Configuration
    tattoo effect, Samba-3 Implementation Choices
    TCP, Multiple Interfaces, Why Is This So Hard?
    TCP data streams, The Front-End Challenge
    TCP failover, Why Is This So Hard?
    TCP port, Features and Benefits
    TCP port 139, Background Information, Multiple Virtual Server Personalities
    TCP port 445, Background Information, Multiple Virtual Server Personalities
    tcp ports, Join the Samba Server to the PDC Domain
    TCP/IP, MS Windows XP Professional, MS Windows Me, Features and Benefits, Windows Networking Protocols
    TCP/IP configuration, MS Windows XP Professional, MS Windows Me
    TCP/IP configuration panel, MS Windows 2000
    TCP/IP protocol configuration, Technical Details
    TCP/IP protocol settings, MS Windows XP Professional, MS Windows 2000
    TCP/IP protocol stack, WINS: The Windows Internetworking Name Server
    TCP/IP-only, Windows Networking Protocols
    tcpdump, Tcpdump
    TDB, New Account Storage Systems, Running rpcclient with setdriver, The Printing *.tdb Files, Trivial Database Files, Multiple Server Hosting
    backing up (see tdbbackup)
    tdb, User and Group ID Allocation, Server Pool Communications
    tdb data files, TDB Data Files
    TDB database, Running rpcclient with adddriver
    TDB database files, Setting Device Modes on New Printers
    tdb file backup, TDB Data Files
    tdb file descriptions, TDB Database File Information, TDB Data Files
    tdb file locations, TDB Database File Information
    tdb files, Access Controls on Shares
    tdbbackup, Using tdbbackup, Corrupt tdb Files
    tdbdump, Access Controls on Shares
    tdbsam, Domain Control: Example Configuration, Group Mapping Changes in Samba-3.0.23, Account Information Databases, Technical Information, Listing User and Machine Accounts, smbpasswd: Encrypted Password Database, tdbsam, Default Users, Groups, and Relative Identifiers, Domain Member Server or Domain Member Client, Objectives
    tdbsam databases, Password Backends
    technical reviewers, Advanced Configuration Techniques
    Telnet, Advantages of Non-Encrypted Passwords
    telnet logins, Linux/FreeBSD-Specific PAM Configuration
    template, Creating and Managing Group Profiles
    temporary location, Print Commands
    terminal server, Remote Management with ThinLinc
    Terminal Server, Demultiplexing SMB Requests
    Testing Server Setup, Configure /etc/krb5.conf
    testparm, Test Your Config File with testparm, Central Print Serving, Simple Print Configuration, Verifying Configuration with testparm, Rapid Configuration Validation, Extended Printing Configuration, Assumptions, The Tests, Debugging with Samba Itself
    tethereal, Tcpdump
    text/plain, MIME Type Conversion Rules
    texttops, MIME Type Conversion Rules
    thin client, Remote Management with ThinLinc
    ThinLinc, Remote Management with ThinLinc
    tid, Demultiplexing SMB Requests
    TIFF, MIME Types and CUPS Filters
    TightVNC, Remote Management from NoMachine.Com, Remote Management with ThinLinc
    time difference, Configure /etc/krb5.conf
    time format, Changing User Accounts
    time-to-live (see TTL)
    tool, Windows 200x/XP
    tools, Central Print Serving, Caution Regarding LDAP and Samba
    tools\reskit\netadmin\poledit, Windows 9x/ME Policies
    traditional printing, Custom Print Commands
    training course, Discussion of Backup Solutions
    transfer differences, Rsync
    transformation, MIME Types and CUPS Filters
    transitive, Trust Relationship Background
    transparent access, Features and Benefits
    transparently reconnected, The Ultimate Goal
    transport connection loss, Opportunistic Locking Overview
    Transport Layer Seccurity, TLS
    Configuring, Configuring
    Introduction, Introduction
    transport layer security (see TLS)
    Transport Layer Security, TLS
    Testing, Testing
    Troubleshooting, Troubleshooting
    trigger, Preparing for Domain Control, MS Windows NT4-style Domain Control
    trivial database, New Account Storage Systems (see TDB)
    troubleshoot, Rapid Configuration Validation
    troubleshooting, Printing from CUPS to Windows-Attached Printers
    Tru64 UNIX, Basic Parameter Setting
    trust, Features and Benefits, LDAP Directories and Windows Computer Accounts
    account, Domain Security Mode (User-Level Security)
    trust account, Domain Security Mode (User-Level Security), Account Flags Management, NT4-Style Domain Trusts with Windows 2000
    interdomain, Features and Benefits
    machine, Features and Benefits
    trust account password, Features and Benefits
    trust accounts, LDAP Directories and Windows Computer Accounts, Overview
    trust established, Interdomain Trust Facilities
    trust relationship, Trust Relationship Background, Completing an NT4 Domain Trust, Interdomain Trust Facilities, Configuring Samba NT-Style Domain Trusts, NT4-Style Domain Trusts with Windows 2000
    trust relationships, Interdomain Trust Relationships, Features and Benefits, Trust Relationship Background, Creating an NT4 Domain Trust, New Features in Samba-3.0.x
    trusted, Behavior of Cross-Subnet Browsing, User Rights and Privileges
    trusted domain, Nested Groups: Adding Windows Domain Groups to Windows Local Groups, Interdomain Trust Relationships, Trust Relationship Background, Completing an NT4 Domain Trust, Samba as the Trusting Domain, Name Service Switch
    trusted domain name, Samba as the Trusted Domain
    trusted party, Samba as the Trusted Domain
    trusting domain, Interdomain Trust Relationships, Trust Relationship Background, Completing an NT4 Domain Trust
    trusting party, Samba as the Trusted Domain
    trusts, Interdomain Trust Relationships, Trust Relationship Background
    TTL, Static WINS Entries
    turn oplocks off, Advanced Samba Oplocks Parameters
    turnkey solution, LDAP Directories and Windows Computer Accounts
    two-up, Examples for Filtering Chains
    two-way
    propagation, Features and Benefits
    two-way trust, Trust Relationship Background, Native MS Windows NT4 Trusts Configuration, Interdomain Trust Facilities

    U

    UCS-2, Japanese Charsets
    UDP, Preparing for Domain Control, NetBIOS over TCP/IP, How Browsing Functions, Forcing Samba to Be the Master, Multiple Interfaces, Cross-Subnet Browsing
    UDP port 137, Background Information
    udp ports, Join the Samba Server to the PDC Domain
    UDP unicast, How Browsing Functions
    UID, Example Configuration, MS Windows Workstation/Server Machine Trust Accounts, Manual Creation of Machine Trust Accounts, Why Is This Better Than security = server?, Sharing User ID Mappings between Samba Domain Members, Technical Information, Mapping User Identifiers between MS Windows and UNIX, Mapping Common UIDs/GIDs on Distributed Machines, LDAP Directories and Windows Computer Accounts, Listing User and Machine Accounts, Features and Benefits, Overview, Mapping Windows Groups to UNIX Groups, UNIX and Windows User Management, Identity Mapping (IDMAP), Domain Member Server or Domain Member Client, Primary Domain Controller, User Rights and Privileges, Features and Benefits, Handling of Foreign SIDs, Starting and Testing the winbindd Daemon
    uid, OpenLDAP Configuration
    UID numbers, Domain Member Server or Domain Member Client
    UID range, Interdomain Trust Relationships
    unauthorized, MS Windows Workstation/Server Machine Trust Accounts
    unauthorized access, File, Directory, and Share Access Controls
    UNC notation, Identifying Driver Files
    unexpected.tdb, The Printing *.tdb Files
    (see also TDB)
    unicast, NetBIOS over TCP/IP
    unicode, What Are Charsets and Unicode?
    Unicode, Samba and Charsets, New Features in Samba-3.0.x
    Unicode UTF-8, Basic Parameter Setting
    unified logon, Introduction
    UNIX, Basic Parameter Setting
    server, Features and Benefits
    UNIX account, MS Windows Workstation/Server Machine Trust Accounts, Manual Creation of Machine Trust Accounts, On-the-Fly Creation of Machine Trust Accounts
    unix charset, Basic Parameter Setting
    UNIX Domain Socket, File and Directory Access Control
    UNIX domain socket, How Winbind Works
    UNIX file system access controls, Features and Benefits
    UNIX group, Mapping Windows Groups to UNIX Groups
    UNIX groups, Group Mapping: MS Windows and UNIX, What Winbind Provides
    UNIX home directories, Why Can Users Access Other Users' Home Directories?
    UNIX host system, User Rights and Privileges
    UNIX ID, User and Group ID Allocation
    UNIX locking, Discussion
    UNIX login ID, MS Windows Workstation/Server Machine Trust Accounts
    UNIX permissions, Samba-3 Implementation Choices
    UNIX printer, The [global] Section
    UNIX printing, Technical Introduction
    UNIX system account, Adding Machine to Domain Fails
    UNIX system accounts, User Rights and Privileges
    UNIX system files, Features and Benefits
    UNIX user identifier (see UID)
    UNIX users, Why Is This Better Than security = server?, What Winbind Provides
    UNIX-style encrypted passwords, Technical Information
    UNIX-user database, Background
    UNIX/Linux group, Warning: User Private Group Problems
    UNIX/Linux user account, UNIX and Windows User Management
    unlink calls, recycle
    unlinked, File and Directory Access Control
    unmapped groups, User and Group Changes
    unmapped users, User and Group Changes
    unprivileged account names, Reference Documentation Server
    unsigned drivers, Windows 200x/XP Local Security Policies
    unstoppable services, The Ultimate Goal
    unsupported encryption, Possible Errors
    unsupported software, Commercial Support
    updates, Upgrading Samba
    upload drivers, Features and Benefits
    uploaded driver, The [global] Section
    uploaded drivers, Point'n'Print Client Drivers on Samba Servers
    uploading, Point'n'Print Client Drivers on Samba Servers
    upper-case, User Level Security
    uppercase, Configure /etc/krb5.conf, Adding Machine to Domain Fails, Handling Large Directories
    uppercase character, Adding Groups Fails
    USB, Examples for Filtering Chains
    use computer anywhere, Features and Benefits
    user, User and Group Changes, LDAP Directories and Windows Computer Accounts, File and Directory Access Control
    user access management, Features and Benefits
    user account, LDAP Directories and Windows Computer Accounts, User Account Management, Account Flags Management, smbpasswd: Encrypted Password Database, UNIX and Windows User Management
    Adding/Deleting, The smbpasswd Tool
    user account database, MS Windows NT4-style Domain Control
    user accounts, Caution Regarding LDAP and Samba, Domain Member Server or Domain Member Client, User Rights and Privileges
    User Accounts
    Adding/Deleting, The pdbedit Tool, Accounts and Groups Management
    user and group, What Winbind Provides
    user and trust accounts, Account Information Databases
    user attributes, smbpasswd: Encrypted Password Database
    user authentication, Microsoft Remote Procedure Calls
    user database, Backup Domain Controller Configuration, Plaintext
    user encoded, Managing Security Identifiers (SIDS)
    user groups, Free Support
    user logons, User Rights and Privileges
    user management, The smbpasswd Tool, Overview, UNIX and Windows Group Management
    User Management, The pdbedit Tool, Accounts and Groups Management
    User Manager, Samba as the Trusted Domain, Samba as the Trusting Domain, Remote Server Administration, Creating and Managing Group Profiles
    User Manager for Domains, Remote Server Administration
    user or group, Using the “net rpc rights” Utility
    user profiles, Windows 9x/Me Profile Setup
    User Rights and Privileges, The Administrator Domain SID
    user-level, Samba Security Modes, User Level Security
    User-level access control, Domain Logon Configuration: Windows 9x/Me
    user-level security, Advantages of Encrypted Passwords
    user-mode security, Security Mode and Master Browsers
    user.DAT, Windows 9x/Me Profile Setup, Sharing Profiles between Windows 9x/Me and NT4/200x/XP Workstations
    user.MAN, Windows 9x/Me Profile Setup
    User.MAN, Mandatory Profiles
    useradd, Manual Creation of Machine Trust Accounts, On-the-Fly Creation of Machine Trust Accounts
    username, MS Windows NT4-style Domain Control
    username and password, Joining a Domain: Windows 2000/XP Professional
    username map, User Mapping
    userPassword, Initialize the LDAP Database
    users, Features and Benefits
    UsrMgr.exe, Managing Domain Machine Accounts using NT4 Server Manager
    UTF-8, Samba and Charsets, Basic Parameter Setting
    UTF-8 encoding, Enabling SWAT Internationalization Support

    V

    valid username/password, Using IPC$ Share-Based Denials
    valid users, The Tests
    validate, Test Your Config File with testparm, Introduction
    validate every backup, Server Share and Directory Layout
    validation, Single Sign-On and Domain Security, System and Account Policies
    vendor-provided drivers, Raw Print Serving: Vendor Drivers on Windows Clients
    verifiable, Behavior of Cross-Subnet Browsing
    verify, Rapid Configuration Validation
    version control, shadow_copy
    VFS, Domain Control: Example Configuration, Discussion
    VFS module, shadow_copy, Mandatory Profiles
    VFS modules, Discussion, VFS Modules Available Elsewhere
    vgcreate, Shadow Copy Setup
    vgdisplay, Shadow Copy Setup
    vipw, “$” Cannot Be Included in Machine Name, Manual Creation of Machine Trust Accounts
    Virtual File System (see VFS)
    virtual server, The Front-End Challenge, A Simple Solution
    virus scanner, Discussion
    Visual Studio, PostScript Drivers with No Major Problems, Even in Kernel -Mode
    vital task, Features and Benefits
    VNC/RFB, Remote Management from NoMachine.Com
    volume group, Shadow Copy Setup
    volunteers, Getting Mailing List Help
    vscan, vscan
    vuid, Demultiplexing SMB Requests

    W

    W32X86, Identifying Driver Files, PostScript Drivers with No Major Problems, Even in Kernel -Mode, Caveats to Be Considered
    W32X86/2, Using Windows-Formatted Vendor PPDs
    WAN, Forcing Samba to Be the Master, Slow and/or Unreliable Networks
    wbinfo, Starting and Testing the winbindd Daemon
    Web-based configuration, SWAT: The Samba Web Administration Tool
    WebClient, Browsing of Shares and Directories is Very Slow
    Welcome, Joining a Domain: Windows 2000/XP Professional
    well known RID, The Administrator Domain SID
    well-controlled network, Server Share and Directory Layout
    well-known RID, Default Users, Groups, and Relative Identifiers
    wide-area network bandwidth, Features and Benefits
    win election, Making Samba the Domain Master
    Win32 printing API, Printing Developments Since Samba-2.2
    WIN40, Identifying Driver Files, Obtaining Driver Files from Windows Client [print$] Shares, Caveats to Be Considered
    winbind, Why Is This Better Than security = server?, Nested Groups: Adding Windows Domain Groups to Windows Local Groups, Domain Member Server or Domain Member Client, Examples of IDMAP Backend Usage, NT4-Style Domains (Includes Samba Domains), Interdomain Trust Relationships, Features and Benefits, Configure smb.conf
    Winbind, Background, Target Uses, Microsoft Active Directory Services, Pluggable Authentication Modules, User and Group ID Allocation, Result Caching, Introduction, Configure nsswitch.conf and the Winbind Libraries on Linux and Solaris, NSS Winbind on AIX, Starting and Testing the winbindd Daemon, Linux/FreeBSD-Specific PAM Configuration, Conclusion, PAM-Based Distributed Authentication, Features and Benefits
    Winbind architecture, New Features in Samba-3.0.x
    Winbind hooks, What Winbind Provides
    Winbind services, Starting and Testing the winbindd Daemon
    Winbind-based authentication, PAM-Based Distributed Authentication
    winbind.so, Solaris-Specific Configuration
    winbindd, Starting Samba, Test Your Config File with testparm, Example Configuration, Example Configuration, Group Mapping Changes in Samba-3.0.23, LDAP Directories and Windows Computer Accounts, Features and Benefits, Nested Groups: Adding Windows Domain Groups to Windows Local Groups, UNIX and Windows User Management, Identity Mapping (IDMAP), Domain Member Server or Domain Member Client, Interdomain Trust Relationships, Features and Benefits, How Winbind Works, Requirements, Testing Things Out, Configure nsswitch.conf and the Winbind Libraries on Linux and Solaris, Configure smb.conf, Starting and Testing the winbindd Daemon, Solaris, Configure Winbind and PAM, Multiple Server Hosting
    winbindd daemon, Linux
    Windows, Identity Mapping (IDMAP), Basic Parameter Setting
    Windows 2000, Configure /etc/krb5.conf, Testing Server Setup, Network Browsing, Trust Relationship Background
    Windows 2000 Professional TCP/IP, MS Windows 2000
    Windows 2000 server, NT4-Style Domain Trusts with Windows 2000
    Windows 2003, Configure /etc/krb5.conf, I Can't Join a Windows 2003 PDC
    Windows 200x/XP, NetBIOS over TCP/IP, Features and Benefits
    Windows 9x/Me, Domain Logon Configuration: Windows 9x/Me, WINS Server Configuration, Windows Networking Protocols, Remote Server Administration
    Windows 9x/Me/XP Home, MS Windows Workstation/Server Machine Trust Accounts
    Windows account management, What Winbind Provides
    Windows client, What Rights and Privileges Will Permit Windows Client Administration?
    Windows client failover, Opportunistic Locking Overview
    Windows domain, Changes in Behavior
    Windows Explorer, Problem Resolution, Identifying Driver Files
    Windows group, Group Mapping: MS Windows and UNIX, Warning: User Private Group Problems, Mapping Windows Groups to UNIX Groups, User Rights and Privileges
    Windows group account, The Administrator Domain SID
    Windows groups, Mapping Windows Groups to UNIX Groups
    Windows Internet Name Server (see WINS)
    Windows Logon, Windows 9x/Me Profile Setup
    Windows Me TCP/IP, MS Windows Me
    Windows Millennium, MS Windows Me
    Windows Millennium edition (Me) TCP/IP, MS Windows Me
    Windows network clients, Features and Benefits
    Windows NT domain name, Domain Logon Configuration: Windows 9x/Me
    Windows NT PostScript driver, Printing from CUPS to Windows-Attached Printers
    Windows NT Server, Samba as the Trusted Domain
    Windows NT/2000/XP, Check Samba for Driver Recognition
    Windows NT/200x, WINS Server Configuration, Introduction
    Windows NT/200x/XP, The [global] Section
    Windows NT/200x/XP Professional, MS Windows Workstation/Server Machine Trust Accounts, Joining a Domain: Windows 2000/XP Professional, Common Errors
    Windows NT3.10, Essential Background Information
    Windows NT4, Windows NT4 Workstation/Server, Features and Benefits
    Windows NT4 domains, Interdomain Trust Facilities
    Windows NT4 Server, Configuring Samba NT-Style Domain Trusts
    Windows NT4/200X, LDAP Directories and Windows Computer Accounts
    Windows NT4/200x, Discussion
    Windows NT4/200x/XP, NetBIOS Over TCP/IP Enabled, Default Users, Groups, and Relative Identifiers, Windows 200x/XP
    Windows NT4/2kX/XPPro, User Rights and Privileges
    Windows PPD, 690 “Perfect” Printers
    Windows privilege model, Rights Management Capabilities
    Windows Registry, MS Windows Workstation/Server Machine Trust Accounts
    windows registry settings, Windows 9x/Me Profile Setup
    default profile locations, MS Windows NT4 Workstation, MS Windows 200x/XP
    profile path, Windows 9x/Me Profile Setup
    roaming profiles, Disabling Roaming Profile Support
    Windows Resource Kit, Disabling Roaming Profile Support
    Windows Security Identifiers (see SID)
    Windows Terminal server, Remote Management from NoMachine.Com
    Windows Terminal Server, Remote Management with ThinLinc
    Windows user, User Rights and Privileges
    Windows user accounts, UNIX and Windows User Management
    Windows workstation., What Rights and Privileges Will Permit Windows Client Administration?
    Windows XP Home, Important Notes About Security
    Windows XP Home edition, Features and Benefits, The Special Case of MS Windows XP Home Edition, Domain Logon Configuration: Windows 9x/Me
    Windows XP Home Edition, MS Windows 200x/XP
    Windows XP Professional, MS Windows XP Professional, Features and Benefits
    Windows XP Professional TCP/IP, MS Windows 2000
    Windows XP TCP/IP, MS Windows XP Professional
    Windows95/98/ME, Check Samba for Driver Recognition
    winnt.adm, Windows NT4-Style Policy Files
    WINS, Features and Benefits, Domain Controller Types, Preparing for Domain Control, What Qualifies a Domain Controller on the Network?, Joining an NT4-type Domain with Samba-3, Reference Documentation Server, MS Windows XP Professional, MS Windows 2000, MS Windows Me, Network Browsing, Features and Benefits, What Is Browsing?, NetBIOS over TCP/IP, How Browsing Functions, Domain Browsing Configuration, Making Samba the Domain Master, WINS: The Windows Internetworking Name Server, WINS Server Configuration, Technical Overview of Browsing, Browsing Support in Samba, Cross-Subnet Browsing, Behavior of Cross-Subnet Browsing, WINS Lookup, Example Configuration
    wins, /etc/nsswitch.conf
    WINS Configuration, Browsing of Shares and Directories is Very Slow
    WINS lookup, Joining an NT4-type Domain with Samba-3
    WINS replication, WINS Replication, Static WINS Entries
    WINS Server, What Is Browsing?
    WINS server, How Browsing Functions, Configuring Workgroup Browsing, Making Samba the Domain Master, WINS Server Configuration, Browsing Support in Samba, Browsing of Shares and Directories is Very Slow
    WINS server address, How Browsing Functions
    WINS server settings, MS Windows Me
    WINS servers, WINS: The Windows Internetworking Name Server
    WINS service, WINS Server Configuration
    WINS Support, What Is Browsing?
    wins.dat, Static WINS Entries
    without Administrator account, The Administrator Domain SID
    without ADS, Objectives
    work-flow protocol, Single Sign-On and Domain Security
    workgroup, Server Security (User Level Security), Preparing for Domain Control, The Special Case of Windows 9x/Me, Domain Logon Configuration: Windows 9x/Me, Configuring Workgroup Browsing, Making Samba the Domain Master, Name Resolution as Used within MS Windows Networking, Multiple Server Hosting, Multiple Virtual Server Personalities
    membership, Preparing for Domain Control
    workstations, Technical Information
    world-writable, File and Directory Access Control
    write, File and Directory Access Control
    write access, Protecting Directories and Files from Deletion
    Write caching, Opportunistic Locking Overview
    write changes, Backup Domain Controller
    write permission, Create the Computer Account
    writeable, fake_perms
    WYSIWYG, Windows Drivers, GDI, and EMF

    X

    X Window - System, Windows Drivers, GDI, and EMF, UNIX Printfile Conversion and GUI Basics
    X.509 certificates, Introduction
    XFS file system, Shadow Copy Setup
    xfsprogs, Shadow Copy Setup
    xinetd, Validate SWAT Installation, Starting from inetd.conf (see inetd)
    XML, Passdb Changes
    XML-based datasets, Foomatic Database-Generated PPDs
    xpp, Foomatic Database-Generated PPDs
    Xprint, Windows Drivers, GDI, and EMF, UNIX Printfile Conversion and GUI Basics
    xxxxBSD, Features and Benefits

    Y

    yppasswd, The smbpasswd Tool

    Z

    Zero Administration Kit, Windows NT4-Style Policy Files
    zero-based broadcast, Note about Broadcast Addresses
    Prev   
    Glossary Home 
    +Index
    Index
    Prev   

    Index

    Symbols

    "Printers" folder, Caveats to Be Considered, Installing the PostScript Driver on a Client, Manual Driver Installation in 15 Steps
    $, Manual Creation of Machine Trust Accounts
    %i macro, Multiple Virtual Server Personalities
    %L, Multiple Virtual Server Personalities
    %PDF, MIME Types and CUPS Filters
    %SystemRoot%\System32\config, MS Windows NT4-style Domain Control
    ../source/nsswitch, Configure Winbind and PAM
    .ai, MIME Types and CUPS Filters
    .AppleDouble, netatalk
    .eps, MIME Types and CUPS Filters
    .pdf, MIME Types and CUPS Filters
    .PDS extension, Windows NT4 Workstation
    .profiles, Windows 9x/Me User Profiles
    .ps, MIME Types and CUPS Filters
    .recycle, recycle
    /bin/false, Example Configuration, User Rights and Privileges
    /dev/null, User Rights and Privileges
    /dev/shadowvol, Shadow Copy Setup
    /etc/cups/, MIME Types and CUPS Filters
    /etc/cups/mime.convs, Raw Print Serving: Vendor Drivers on Windows Clients, Explicitly Enable “raw” Printing for application/octet-stream, MIME Type Conversion Rules, application/octet-stream Printing
    /etc/cups/mime.types, Raw Print Serving: Vendor Drivers on Windows Clients, Explicitly Enable “raw” Printing for application/octet-stream, application/octet-stream Printing
    /etc/fstab, Shadow Copy Setup
    /etc/group, Share-Level Security, Discussion, Nested Groups: Adding Windows Domain Groups to Windows Local Groups, Sample smb.conf Add Group Script, Domain Member Server or Domain Member Client, The [global] Section, Features and Benefits, HPUX
    /etc/groups, Anatomy of /etc/pam.d Entries
    /etc/host.conf, Name Resolution in a Pure UNIX/Linux World, /etc/host.conf
    /etc/hosts, Configure /etc/krb5.conf, How Browsing Functions, Name Resolution in a Pure UNIX/Linux World, /etc/hosts, Name Resolution as Used within MS Windows Networking, The Tests
    /etc/hosts>, /etc/hosts
    /etc/inetd.conf, Linux/FreeBSD-Specific PAM Configuration, Starting from inetd.conf
    /etc/init.d/samba, Joining an NT4-type Domain with Samba-3, Linux
    /etc/init.d/samba.server, Solaris
    /etc/init.d/smb, Linux
    /etc/krb5.conf, Configure /etc/krb5.conf, Possible Errors, ADS Domains, IDMAP Storage in LDAP Using Winbind
    /etc/ldap.conf, IDMAP Storage in LDAP Using Winbind, IDMAP and NSS Using LDAP from ADS with RFC2307bis Schema Extension
    /etc/logingroup, HPUX
    /etc/mime.conv, Central Print Serving
    /etc/mime.types, Central Print Serving
    /etc/nsswitch.conf, Domain Member Server or Domain Member Client, NT4-Style Domains (Includes Samba Domains), IDMAP_RID with Winbind, IDMAP and NSS Using LDAP from ADS with RFC2307bis Schema Extension, Name Service Switch, Configure nsswitch.conf and the Winbind Libraries on Linux and Solaris, Name Resolution in a Pure UNIX/Linux World, /etc/nsswitch.conf
    /etc/openldap/slapd.conf, The Primary Domain Controller
    /etc/openldap/sldap.conf, Accounts and Groups Management
    /etc/pam.conf, Solaris-Specific Configuration, Features and Benefits, Technical Discussion, Anatomy of /etc/pam.d Entries
    /etc/pam.d, Requirements, Testing Things Out, Configure Winbind and PAM, Features and Benefits
    /etc/pam.d/, Pluggable Authentication Modules, Technical Discussion
    /etc/pam.d/ftp, Linux/FreeBSD-Specific PAM Configuration
    /etc/pam.d/login, Linux/FreeBSD-Specific PAM Configuration
    /etc/pam.d/samba, Linux/FreeBSD-Specific PAM Configuration
    /etc/passwd, Share-Level Security, Example Configuration, “$” Cannot Be Included in Machine Name, MS Windows Workstation/Server Machine Trust Accounts, Manual Creation of Machine Trust Accounts, Windows 200x/XP Professional Client, Adding Machine to Domain Fails, Background, Reference Documentation Server, Central Print Serving, Backward Compatibility Account Storage Systems, Plaintext, Schema and Relationship to the RFC 2307 posixAccount, Applicable Only to Versions Earlier than 3.0.11, Domain Member Server or Domain Member Client, Samba as the Trusted Domain, Features and Benefits, Starting and Testing the winbindd Daemon, Features and Benefits
    /etc/printcap, Basic CUPS Support Configuration
    /etc/resolv.conf, Name Resolution in a Pure UNIX/Linux World, Assumptions, The Tests
    /etc/samba, Multiple Virtual Server Personalities, Multiple Virtual Server Hosting, The Tests
    /etc/samba/scripts, Managing Nest Groups on Workstations from the Samba Server
    /etc/samba/secrets.tdb, Joining an NT4-type Domain with Samba-3
    /etc/samba/smb.conf, Configuring Samba (smb.conf)
    /etc/samba/smbpasswd, Plaintext
    /etc/samba/smbusers, User Mapping
    /etc/shadow, Background, Backward Compatibility Account Storage Systems
    /etc/smbpasswd, Plaintext
    /etc/ssl/certs/slapd.pem, LDAP Configuration Notes
    /etc/xinetd.d, Linux/FreeBSD-Specific PAM Configuration
    /etc/xinetd.d/telnet, Linux/FreeBSD-Specific PAM Configuration
    /export, Reference Documentation Server
    /lib/libnss_example.so, Name Service Switch
    /lib/libnss_files.so, Name Service Switch
    /lib/security, Configure Winbind and PAM, PAM Configuration Syntax
    /lib/security/, Pluggable Authentication Modules
    /opt/samba/bin, Locating the SWAT File
    /tmp, File and Directory Access Control
    /usr/bin/openssl, Securing SWAT through SSL
    /usr/lib/samba/vfs, Discussion
    /usr/lib/security, NSS Winbind on AIX, Configure Winbind and PAM
    /usr/lib/security/methods.cfg, NSS Winbind on AIX
    /usr/local/lib, Configure nsswitch.conf and the Winbind Libraries on Linux and Solaris
    /usr/local/samba, Starting and Testing the winbindd Daemon
    /usr/local/samba/bin, Linux, Solaris, Locating the SWAT File
    /usr/local/samba/lib, The Tests
    /usr/local/samba/lib/vfs, Discussion
    /usr/local/samba/private/secrets.tdb, Joining an NT4-type Domain with Samba-3
    /usr/local/samba/swat, Enabling SWAT for Use
    /usr/local/samba/var, Access Controls on Shares, Assumptions
    /usr/local/samba/var/locks, Static WINS Entries
    /usr/sbin, Locating the SWAT File, Enabling SWAT for Use
    /usr/share/samba/swat, Enabling SWAT for Use
    /var/locks/*.tdb, Corrupt tdb Files
    /var/log/samba, Assumptions
    /var/run/samba, Static WINS Entries
    /var/spool/cups/, Autodeletion or Preservation of CUPS Spool Files
    /var/spool/samba, Central Print Serving, Autodeletion or Preservation of CUPS Spool Files
    250-user limit, tdbsam
    3.0.11, The Administrator Domain SID
    4,500 user accounts, tdbsam
    4294967295, Interdomain Trust Relationships
    8.3 file names, MS Windows NTFS Comparison with UNIX File Systems
    >Domain User Manager, Creating an NT4 Domain Trust
    \\%L\%U\.profiles, Windows 9x/Me User Profiles
    \\SERVER, Problem Resolution
    _kerberos.REALM.NAME, Configure /etc/krb5.conf
    _kerberos._udp, Notes
    _ldap._tcp, Notes
    _ldap._tcp.pdc._msdcs.quenya.org, NetBIOS Over TCP/IP Disabled

    , Configuration File Syntax, Example Configuration, Anonymous Read-Only Document Server, Anonymous Read-Write Document Server, Anonymous Print Server, Secure Read-Write File and Print Server, Example Configuration, Example: Engineering Office, The Primary Domain Controller, Backup Domain Controller, Example Configuration, Example Configuration, Example Configuration, Example Configuration, Example Configuration, Password Checking, Single Sign-On and Domain Security, Domain Control: Example Configuration, Example Configuration, Example PDC Configuration, LDAP Configuration Notes, Example Configuration, Manual Creation of Machine Trust Accounts, On-the-Fly Creation of Machine Trust Accounts, Samba Client, Joining an NT4-type Domain with Samba-3, Configure smb.conf, Configure /etc/krb5.conf, Sharing User ID Mappings between Samba Domain Members, Reference Documentation Server, Central Print Serving, Configuring Workgroup Browsing, Domain Browsing Configuration, Multiple Interfaces, Use of the Remote Announce Parameter, Use of the Remote Browse Sync Parameter, WINS Server Configuration, Name Resolution Order, Mapping Common UIDs/GIDs on Distributed Machines, Configuring Samba, Sample smb.conf Add Group Script, Managing Nest Groups on Workstations from the Samba Server, NT4-Style Domains (Includes Samba Domains), ADS Domains, IDMAP_RID with Winbind, IDMAP Storage in LDAP Using Winbind, IDMAP and NSS Using LDAP from ADS with RFC2307bis Schema Extension, Using the “net rpc rights” Utility, File, Directory, and Share Access Controls, Interaction with the Standard Samba “create mask” Parameters, Users Cannot Write to a Public Share, MS Word with Samba Changes Owner of File, Disabling Oplocks, Disabling Kernel Oplocks, Features and Benefits, Using Host-Based Protection, User-Based Protection, Using Interface Protection, Using IPC$ Share-Based Denials , Why Can Users Access Other Users' Home Directories?, Interdomain Trust Relationships, Features and Benefits, MSDFS UNIX Path Is Case-Critical, Simple Print Configuration, Rapid Configuration Validation, Extended Printing Configuration, Custom Print Commands, Creating the [print$] Share, Identifying Driver Files, Simple smb.conf Settings for CUPS, More Complex CUPS smb.conf Settings, From Windows Clients to a CUPS/Samba Print Server, Prepare Your smb.conf for cupsaddsmb, Discussion, Shadow Copy Setup, Features and Benefits, Configure smb.conf, Linux, Solaris-Specific Configuration, Remote Management from NoMachine.Com, NT4/200x User Profiles, Windows 9x/Me User Profiles, Mixed Windows Windows 9x/Me and NT4/200x User Profiles, Changing the Default Profile, The NetBIOS Name Cache, WINS Lookup, Basic Parameter Setting, Individual Implementations, Handling Large Directories, Advanced Configuration Techniques, Multiple Virtual Server Personalities, Multiple Virtual Server Hosting, IdMap LDAP Support, Assumptions, The Tests, Debug Levels, Debugging-Specific Operations, Windows 2000 Service Pack 2 (see SSO)
    backend, Domain Controller Types
    logon
    service, Essential Background Information

    A

    abbreviated keystrokes, TCP/IP Configuration
    aborting shutdown, Description of Privileges
    accept connections, Using Interface Protection
    access, User and Group Changes
    Access, Using the “net rpc rights” Utility
    access authentication, Mapping Common UIDs/GIDs on Distributed Machines
    access control, Features and Benefits, Single Sign-On and Domain Security, Background, Access Controls on Shares, Advanced Network Management
    Access Control, Domain Logon Configuration: Windows 9x/Me
    Access Control Entries (see ACE)
    Access Control List, File, Directory, and Share Access Controls
    access control needs, Server Share and Directory Layout
    access controls, Features and Benefits, Comments Regarding LDAP, The pdbedit Tool, Mapping Windows Groups to UNIX Groups, Features and Benefits, Protecting Directories and Files from Deletion
    Access Controls, Objectives
    access denied, Using IPC$ Share-Based Denials
    access policies, Domain Account Policy Managment
    access rights, Features and Benefits, Overview, Trust Relationship Background
    account, Example Configuration, Features and Benefits, Windows 200x/XP Professional Client, Anatomy of /etc/pam.d Entries
    backend, Features and Benefits
    database, Domain Security Mode (User-Level Security)
    backends, Features and Benefits
    account access controls, New Account Storage Systems
    account attributes, Primary Domain Controller
    account backends, Account Information Databases
    account containers, Initialize the LDAP Database
    account control block (see ACB)
    account control flags, Account Flags Management
    account controls, MS Windows Workstation/Server Machine Trust Accounts
    Account Controls, Managing Account/User Policies
    account database, Password Backends
    account deleted, Deleting Accounts
    account encode_bits, Account Flags Management
    account flag order, Account Flags Management
    Account Flags, Listing User and Machine Accounts
    account flags, Account Flags Management
    account import/export, The pdbedit Tool, Account Import/Export
    account information, MS Windows NT4-style Domain Control, MS Windows Workstation/Server Machine Trust Accounts, Schema and Relationship to the RFC 2307 posixAccount, UNIX and Windows User Management
    account information database, Mapping User Identifiers between MS Windows and UNIX
    account management, Primary Domain Controller
    account name, Domain Member Server or Domain Member Client, User Rights and Privileges, Samba as the Trusted Domain
    account policies, Preparing for Domain Control
    account policy, The pdbedit Tool
    account restrictions, Managing Account/User Policies
    account security, The pdbedit Tool
    account storage backends, Passdb Backends and Authentication
    account storage mechanisms, Account Information Databases
    account storage system, Account Information Databases
    Account Unknown, Nested Groups: Adding Windows Domain Groups to Windows Local Groups
    accountability, The pdbedit Tool
    accounts, Introduction
    ACL, User and Group Changes, Security and sambaSamAccount, Nested Groups: Adding Windows Domain Groups to Windows Local Groups, Description of Privileges, Features and Benefits, Printing Developments Since Samba-2.2, Introduction
    ACLs, File, Directory, and Share Access Controls, The Obsoleted [printer$] Section
    File System, File and Directory Access Control
    POSIX, File, Directory, and Share Access Controls, Features and Benefits
    share, Features and Benefits
    Windows, Features and Benefits
    ACLs on share, Windows 200x/XP
    ACLs on shares, Features and Benefits
    across network segments, NetBIOS over TCP/IP
    active directory, Features and Benefits, Features and Benefits, Single Sign-On and Domain Security, Preparing for Domain Control, Samba ADS Domain Control
    Active Directory, Active Directory Domain Control, Samba ADS Domain Membership, UNIX and Windows Group Management, Standalone Samba Server, Domain Member Server or Domain Member Client, IDMAP_RID with Winbind, Interdomain Trust Relationships
    Active Directory Server, Objectives
    AD4UNIX, Domain Member Server or Domain Member Client
    ADAM, IDMAP Storage in LDAP Using Winbind
    add a user account, Adding User Accounts
    add client machines, Using the “net rpc rights” Utility
    add domain users and groups to a local group, What Rights and Privileges Will Permit Windows Client Administration?
    add drivers, The [global] Section
    add machine script, On-the-Fly Creation of Machine Trust Accounts, Using the “net rpc rights” Utility, Changes in Behavior
    Add Printer Wizard, Features and Benefits, The [global] Section, Printing Developments Since Samba-2.2
    add printer wizard, Driver Upload Methods
    add user script, User Account Management, Changes in Behavior
    add/delete/change share, Description of Privileges
    adddriver, Installing Driver Files into [print$], Running rpcclient with adddriver, Specific Driver Name Flexibility, A Check of the rpcclient man Page, Troubleshooting Revisited
    additional driver, Additional Client Driver Installation
    additional privileges, Description of Privileges
    addmem, Nested Groups: Adding Windows Domain Groups to Windows Local Groups
    AddPrinterDriver(), A Check of the rpcclient man Page
    admincfg.exe, Configuring Windows for Workgroups Password Handling
    administrative actions, Using the “net rpc rights” Utility
    administrative duties, Overview
    administrative privileges, Nested Groups: Adding Windows Domain Groups to Windows Local Groups, Join the Samba Server to the PDC Domain
    administrative responsibilities, Trust Relationship Background
    administrative rights, Description of Privileges, What Rights and Privileges Will Permit Windows Client Administration?
    administrative rights and privileges, What Rights and Privileges Will Permit Windows Client Administration?
    Administrative Templates, MS Windows 200x/XP Professional Policies
    Administrator, Discussion, Important Administrative Information, Join the Samba Server to the PDC Domain
    administrator account, Windows 200x/XP Professional Client, Windows NT4 Client
    Administrator account, Create the Computer Account
    administrator password, Notes
    Administrator%password, Joining an NT4-type Domain with Samba-3
    Adobe, GDI on Windows, PostScript on UNIX, PostScript Drivers with No Major Problems, Even in Kernel +Mode, The Grand Unification Achieved
    Adobe driver, Windows CUPS PostScript Driver Versus Adobe Driver
    Adobe driver files, Recognizing Different Driver Files
    Adobe PostScript, Caveats to Be Considered, Adobe and CUPS PostScript Drivers for Windows Clients
    Adobe PostScript driver, Installing the PostScript Driver on a Client
    Adobe PPD, CUPS Print Drivers from Linuxprinting.org
    Adobe specifications, The Role of cupsomatic/foomatic
    ADS, ADS Security Mode (User-Level Security), Single Sign-On and Domain Security, Domain Controller Types, Features and Benefits, MS Windows Workstation/Server Machine Trust Accounts, Domain Member Server, Joining an NT4-type Domain with Samba-3, Configure smb.conf, Configure /etc/krb5.conf, Create the Computer Account, Testing Server Setup, Network Browsing, TCP/IP without NetBIOS, DNS and Active Directory, Cross-Subnet Browsing, Account Information Databases, New Account Storage Systems, Comments Regarding LDAP, Accounts and Groups Management, Administrative Tasks and Methods, Domain Member Server or Domain Member Client, Primary Domain Controller, IDMAP Storage in LDAP Using Winbind, User Rights and Privileges, Interdomain Trust Relationships, Features and Benefits, Trust Relationship Background, NT4-Style Domain Trusts with Windows 2000, Printing Developments Since Samba-2.2, Features and Benefits, Result Caching, Features and Benefits, MS Windows 200x/XP Professional Policies, Managing Account/User Policies, System Startup and Logon Processing Overview, MS Windows 200x/XP, PAM-Based Distributed Authentication, Features and Benefits, Background Information, New Features in Samba-3.0.x, Passdb Backends and Authentication, Objectives, Features and Benefits (see Active Directory)
    ADS DC, Configure smb.conf
    ADS domain, Domain Member Server or Domain Member Client, ADS Domains
    ADS domain members, Identity Mapping (IDMAP)
    ADS manager, Create the Computer Account
    ADS schema, Primary Domain Controller
    Advanced TCP/IP configuration, MS Windows XP Professional
    advantages, Objectives
    affect users, Creating and Managing System Policies
    affordable power, The Ultimate Goal
    AFPL, Ghostscript: The Software RIP for Non-PostScript Printers
    AFPL Ghostscript, pstoraster
    AFS, The Distributed File System Challenge
    AIX, Mapping Common UIDs/GIDs on Distributed Machines, The [global] Section, NSS Winbind on AIX
    algorithmic mapping, Primary Domain Controller
    alias group, Nested Groups: Adding Windows Domain Groups to Windows Local Groups
    allow access, Using Host-Based Protection
    allow trusted domains, IDMAP_RID with Winbind
    already exists, Cannot Add Machine Back to Domain
    alternative solution, Objectives
    Amanda, Amanda
    analyzes data, Diagnostics Tools
    anonymous, Central Print Serving
    print server, Anonymous Print Server
    read-write server, Anonymous Read-Write Document Server
    anonymous access, Problem Resolution
    anonymous file server, Multiple Virtual Server Personalities
    anonymous server, Advanced Configuration Techniques
    ANSI compiler, HPUX
    anticipate failure, Features and Benefits
    API, smbpasswd: Encrypted Password Database
    Appliances, Target Uses
    application servers, Features and Benefits
    application/cups.vnd-postscript, Windows CUPS PostScript Driver Versus Adobe Driver
    application/octet-stream, Explicitly Enable “raw” Printing for application/octet-stream, MIME Type Conversion Rules, application/octet-stream Printing
    application/pdf, MIME Types and CUPS Filters, MIME Type Conversion Rules
    application/postscript, MIME Types and CUPS Filters, MIME Type Conversion Rules, Prefilters, pstops, Windows CUPS PostScript Driver Versus Adobe Driver
    application/vnd.cups-postscript, Prefilters, pstops
    application/vnd.cups-raster, PostScript Printer Descriptions for Non-PostScript Printers
    application/vnd.cups-raw, Explicitly Enable “raw” Printing for application/octet-stream
    application/x-shell, MIME Type Conversion Rules
    apt-get, Shadow Copy Setup
    ARCFOUR-HMAC-MD5, Testing Server Setup
    architecture, Comments Regarding LDAP
    ARP/RARP, /etc/hosts
    ASCII, MIME Types and CUPS Filters, What Are Charsets and Unicode?, Japanese Charsets
    ASCII text, Prefilters
    assign rights, Using the “net rpc rights” Utility
    assigned RID, Discussion
    assistance, Free Support
    associations, Group Mapping: MS Windows and UNIX
    attach gdb, Debugging with Samba Itself
    attribute, OpenLDAP Configuration
    attributes, New Schema
    audit file access, audit
    audit module, extd_audit
    auth, Anatomy of /etc/pam.d Entries
    authenticate, MS Windows Workstation/Server Machine Trust Accounts, Joining an NT4-type Domain with Samba-3
    authenticate users, Joining an NT4-type Domain with Samba-3
    authenticated, Configure smb.conf
    authenticating server, MS Windows NT4 Workstation
    authentication, Features and Benefits, Domain Security Mode (User-Level Security), Single Sign-On and Domain Security, Domain Controller Types, The Special Case of Windows 9x/Me, Why Is This Better Than security = server?, Important Notes About Security, Comments Regarding LDAP, Account Import/Export, Overview, Configure Winbind and PAM, Features and Benefits
    backend, Domain Member Server
    authentication agents, Single Sign-On and Domain Security
    authentication architecture, Single Sign-On and Domain Security
    authentication backend, Domain Layout
    authentication control, Introduction
    authentication database, Features and Benefits
    authentication management, Pluggable Authentication Modules
    authentication mechanisms, Introduction
    authentication methods, Pluggable Authentication Modules
    authentication module API, NSS Winbind on AIX
    authentication regime, Domain Member Server
    authentication reply, Why Is This Better Than security = server?
    authentication server, MS Windows NT4-style Domain Control
    authentication service, Linux/FreeBSD-Specific PAM Configuration
    authentication system, Single Sign-On and Domain Security, New Features in Samba-3.0.x
    authenticatior, Domain Controller Types
    authoritative, Behavior of Cross-Subnet Browsing
    authoritive, How Browsing Functions
    authorization, Pluggable Authentication Modules
    auto-reconnect, Important Notes About Security
    autogen.sh, Building the Binaries
    autogenerated printcap, Default UNIX System Printing Commands
    automatic account creation, Managing Domain Machine Accounts using NT4 Server Manager
    automatic mapping, Domain Member Server or Domain Member Client
    automatic reconnects, Advantages of Encrypted Passwords
    automatic redundancy, Forcing Samba to Be the Master
    autopoweruser.sh, Managing Nest Groups on Workstations from the Samba Server
    autotyping, MIME Types and CUPS Filters
    AUXILIARY, Schema and Relationship to the RFC 2307 posixAccount
    auxiliary members, Nested Groups: Adding Windows Domain Groups to Windows Local Groups
    availability, Features and Benefits, Objectives
    available, Central Print Serving
    available port, Samba and Printer Ports
    available printerd, The [global] Section
    available rights, Using the “net rpc rights” Utility
    average print run, Advanced Intelligent Printing with PostScript Driver Download

    B

    b-node, NetBIOS over TCP/IP
    back up, Requirements
    backed up, Server Share and Directory Layout
    backend, The Distributed File System Challenge
    backend authentication, Objectives
    backend database, Domain Controller Types, MS Windows Workstation/Server Machine Trust Accounts, Adding Machine to Domain Fails
    backend failures, High-Availability Server Products
    backend file system pool, Restrictive Constraints on Distributed File Systems
    backends, Passdb Changes, Printing from CUPS to Windows-Attached Printers
    backup, Features and Benefits, Server Share and Directory Layout, Features and Benefits
    backup domain controller, Domain Layout
    backup solution, Discussion of Backup Solutions
    BackupPC, BackupPC
    bad hardware, Browsing of Shares and Directories is Very Slow
    bad logon attempts, Changing User Accounts
    Bad networking hardware, Browsing of Shares and Directories is Very Slow
    bad password, The Tests
    banner pages, Windows CUPS PostScript Driver Versus Adobe Driver, Run cupsaddsmb (Quiet Mode)
    barriers, Introduction
    Batch Oplock, Opportunistic Locking Overview
    BDC, Domain Security Mode (User-Level Security), Example Configuration, Single Sign-On and Domain Security, Domain Controller Types, Features and Benefits, MS Windows NT4-style Domain Control, LDAP Configuration Notes, Active Directory Domain Control, Backup Domain Controller Configuration, Example Configuration, Can Samba Be a Backup Domain Controller to an NT4 PDC?, Joining an NT4-type Domain with Samba-3, Why Is This Better Than security = server?, New Account Storage Systems, Advantages of Encrypted Passwords, Mapping Common UIDs/GIDs on Distributed Machines, tdbsam, Overview, Domain Member Server or Domain Member Client, Primary Domain Controller, Backup Domain Controller, Join the Samba Server to the PDC Domain, Remote Management from NoMachine.Com, Domain Layout, Steps in Migration Process
    BDCs, Domain Layout
    behavior approximately same, Quick Migration Guide
    between domains, Configuring Samba NT-Style Domain Trusts
    bias, Forcing Samba to Be the Master
    binary format TDB, New Account Storage Systems
    BIND, Dynamic DNS
    bind interfaces only, Multiple Server Hosting
    BIND9, DNS and Active Directory
    BIND9.NET, Features and Benefits
    bindery-enabled, Features and Benefits
    block device, File and Directory Access Control
    block incoming packets, Using a Firewall
    BOBS, BOBS: Browseable Online Backup System
    bogus, Example Configuration
    boot disk`, Requirements
    bridge, File, Directory, and Share Access Controls
    bridges networks, How Browsing Functions
    brlock.tdb, The Printing *.tdb Files
    (see also TDB)
    broadcast, What Qualifies a Domain Controller on the Network?, NetBIOS over TCP/IP
    broadcast address, Problem Resolution, The Tests
    broadcast isolated subnet, Forcing Samba to Be the Master
    broadcast messages, NetBIOS over TCP/IP
    broadcast messaging, How Does a Workstation find its Domain Controller?
    Broadcast node, Static WINS Entries
    broadcast request, The Special Case of Windows 9x/Me
    broadcast traffic, Cross-Subnet Browsing
    broadcast-based, NetBIOS over TCP/IP
    broadcast-based name resolution, Joining an NT4-type Domain with Samba-3
    broadcasts, Forcing Samba to Be the Master, Behavior of Cross-Subnet Browsing
    browse across subnet, Cross-Subnet Browsing
    browse list, Preparing for Domain Control, How Browsing Functions, WINS: The Windows Internetworking Name Server, Behavior of Cross-Subnet Browsing
    browse list handling, Network Browsing
    browse list maintainers, How Browsing Functions
    browse list management, Security Mode and Master Browsers, What Is Browsing?
    browse lists, Making Samba the Domain Master, Cross-Subnet Browsing, Behavior of Cross-Subnet Browsing
    browse resources, Problem Resolution
    browse server resources, Problem Resolution
    browse shares, Using IPC$ Share-Based Denials
    browse.dat, Problem Resolution
    browseable, Configuration File Syntax
    browser election, Configuring Workgroup Browsing
    browser elections, Domain Browsing Configuration, Forcing Samba to Be the Master
    BrowseShortNames, Print Queue Called “lp” Mishandles Print Jobs
    browsing, The Special Case of Windows 9x/Me, What Is Browsing?, Making Samba the Domain Master, Browsing Support in Samba
    browsing across subnets, Network Browsing, Cross-Subnet Browsing
    browsing another subnet, Browsing Support in Samba
    browsing intrinsics, How Browsing Functions
    browsing problems, Windows Networking Protocols, Common Errors, I Get an "Unable to browse the network" Error
    BSD, “$” Cannot Be Included in Machine Name, Manual Creation of Machine Trust Accounts, Features and Benefits
    BSD Printing, Simple Print Configuration
    BSD-style printing, Extended Printing Configuration
    bug report, Free Support
    bug reports, Introduction
    Bugzilla, Introduction
    built-in commands, Custom Print Commands
    bypasses privilege, Using the “net rpc rights” Utility
    byte ranges, Discussion
    byte-range lock, Discussion
    byte-range locking, Discussion, Opportunistic Locking Overview

    C

    c:\winnt\inf, Windows NT4-Style Policy Files
    C:\WinNT\System32\config, MS Windows NT4-style Domain Control
    cached
    password, Password Checking
    cached encrypted password, Important Notes About Security
    cached in memory, Advantages of Non-Encrypted Passwords
    cached local file, Opportunistic Locking Overview
    cached locally, Windows 9x/Me Profile Setup
    cached references, Invalid Cached Share References Affects Network Browsing
    caching, Opportunistic Locking Overview
    caching reads, Opportunistic Locking Overview
    caching scheme, Result Caching
    caching writes, Opportunistic Locking Overview
    called name, Using Host-Based Protection
    cannot join domain, Common Errors
    canonicalize files, Handling Large Directories
    CAP, Japanese Charsets, Basic Parameter Setting, Macintosh Clients
    cap-share, Basic Parameter Setting
    capability to delete, Protecting Directories and Files from Deletion
    CAP_LINUX_IMMUTABLE, Protecting Directories and Files from Deletion
    case options, Handling Large Directories
    case sensitivity, PAM Configuration Syntax
    case-insensitive, User Level Security, Simple Print Configuration, Handling Large Directories
    case-preserving, User Level Security
    central environment, Comments Regarding LDAP
    centralized
    authentication, Single Sign-On and Domain Security
    centralized identity management, Single Sign-On and Domain Security
    centrally managed, Features and Benefits
    certificate, Securing SWAT through SSL
    Certificate Authority (see CA)
    cfdisk, Shadow Copy Setup
    challenge/response mechanis, Important Notes About Security
    change capabilities, The smbpasswd Tool
    change motivations, Objectives
    change password, Notes
    change passwords, The smbpasswd Tool
    changed parameters, Upgrading from Samba-2.x to Samba-3.0.25
    changes password, Manual Creation of Machine Trust Accounts
    character device, File and Directory Access Control
    character set, What Are Charsets and Unicode?
    character sets, Samba and Charsets, New Features in Samba-3.0.x
    charset, What Are Charsets and Unicode?
    charset conversion, Conversion from Old Names
    chattr, Protecting Directories and Files from Deletion
    check for locks, Discussion
    check logs, Adding Machine to Domain Fails
    checksum-search, Rsync
    chmod, Central Print Serving, Shadow Copy Setup
    chown, Central Print Serving, Viewing File Ownership, Features and Benefits
    chpass, Manual Creation of Machine Trust Accounts
    CIFS, Sharing User ID Mappings between Samba Domain Members
    CIFS function calls, User Rights and Privileges
    CIFS/SMB, Features and Benefits, Why Is This So Hard?
    Citrix, Remote Management with ThinLinc
    clear purpose preferred, Discussion of Backup Solutions
    clear-text, Password Checking, Important Notes About Security, Security and sambaSamAccount
    clear-text passwords, Important Notes About Security
    client client instructions, Features and Benefits
    Client for Microsoft Networks, Domain Logon Configuration: Windows 9x/Me
    Client for Novell Networks, Windows 9x/Me Profile Setup
    client-server mode, The smbpasswd Tool
    client-side caching, Opportunistic Locking Overview
    client-side data caching, Opportunistic Locking Overview, PDM Data Shares
    clock skew, Configure /etc/krb5.conf
    cluster servers, The Front-End Challenge
    clustered file server, The Ultimate Goal
    Clustered smbds, Server Pool Communications
    clustering technologies, The Ultimate Goal
    cluttering, Debugging-Specific Operations
    cmd, Browsing of Shares and Directories is Very Slow, What Rights and Privileges Will Permit Windows Client Administration?
    cmd shell, What Rights and Privileges Will Permit Windows Client Administration?
    CN, LDAP Configuration Notes, Introduction
    code maintainer, Free Support
    codepages, Features and Benefits
    collating, Making Samba the Domain Master
    collisions, Samba Performance Problem Due to Changing Linux Kernel
    color, UNIX Printfile Conversion and GUI Basics
    COM1:, Samba and Printer Ports
    command-line, Remote and Local Management: The Net Command
    command-line utility, Using the “net rpc rights” Utility
    commenting out setting, Rapid Configuration Validation
    commercial Linux products, File, Directory, and Share Access Controls
    commercial support, Samba Support, Commercial Support
    commit the settings, MS Windows 2000
    Common Internet Filesystem (see CIFS)
    Common restrictions, Managing Account/User Policies
    Common UNIX Printing System (see CUPS)
    common.adm, Windows NT4-Style Policy Files
    comp.protocols.smb, Introduction
    compatible, Important Notes About Security, Portability
    compile, Obtaining and Installing Samba
    compile-time options, Rapid Configuration Validation
    complex file name space, A Simple Solution
    complex organization, Domain Layout
    complexity, Example Configuration
    compliance, The pdbedit Tool
    complicated, Behavior of Cross-Subnet Browsing
    complicated problem, Demultiplexing SMB Requests
    comprehensive documentation, Multiple Server Hosting
    Computer Account, Windows NT4 Client
    computer account, Testing Server Setup
    computer accounts, Account Information Databases, LDAP Directories and Windows Computer Accounts, User Rights and Privileges
    Computer Management, Access Controls on Shares, Windows 200x/XP
    Computer Name, Joining a Domain: Windows 2000/XP Professional
    computer name, Domain Logon Configuration: Windows 9x/Me, Name Resolution as Used within MS Windows Networking
    concurrent access, Opportunistic Locking Overview
    Conectiva, Forums, Downloads, Tutorials, Howtos (Also for Mac OS X and Commercial UNIX)
    config.cache, Possible Errors
    CONFIG.POL, The Special Case of Windows 9x/Me
    Config.POL, Creating and Managing System Policies, Windows 9x/ME Policies
    configuration
    documentation, Test Your Config File with testparm
    configuration files, Features and Benefits
    configuration problem, Introduction
    configuration syntax, Simple Print Configuration
    configuration techniques, Advanced Configuration Techniques
    configuration too complex, Common Errors
    configuration tool, SWAT: The Samba Web Administration Tool
    configuration wizard, Joining a Domain: Windows 2000/XP Professional
    configure, Building the Binaries
    configuring a firewall, Using a Firewall
    confirm address, Using Interface Protection
    confirm the password, Samba as the Trusting Domain
    confirm the trust, Samba as the Trusted Domain
    connect transparently, The Ultimate Goal
    connection resources, Why Is This Better Than security = server?
    connections, Example Configuration
    connections.tdb, The Printing *.tdb Files
    (see also TDB)
    consistent case, Handling Large Directories
    console, Linux/FreeBSD-Specific PAM Configuration
    consumer expects, Samba Support
    container, Create the Computer Account
    continuity of service, High-Availability Server Products
    contribute, Multiple Server Hosting
    Control Panel, Joining a Domain: Windows 2000/XP Professional
    convert
    domain member server, Domain Controller Types
    converted, Technical Information
    copy'n'paste, Remote Management from NoMachine.Com
    core files, Internal Errors
    core graphic engine, Windows Drivers, GDI, and EMF
    core values, Objectives
    corrupted file, Domain Member Server or Domain Member Client
    cosine.schema, OpenLDAP Configuration
    country of origin, Commercial Support
    CP850, Samba and Charsets
    CP932, Basic Parameter Setting
    cracker, Using Interface Protection
    create, Managing Directories
    Create a Computer Account, Windows NT4 Client
    create a domain machine account, Domain Member Server
    create domain member, Windows 200x/XP Professional Client
    create machine trust account, Joining an NT4-type Domain with Samba-3
    create partition, Shadow Copy Setup
    Create the Computer Account, Configure /etc/krb5.conf
    create user accounts, Background
    create volume, Shadow Copy Setup
    credentials, User Level Security, Single Sign-On and Domain Security, LDAP Configuration Notes, Configure /etc/krb5.conf, Joining a Domain: Windows 2000/XP Professional, Administering User Rights and Privileges, User Rights and Privileges
    credentials validation, NetBIOS Over TCP/IP Enabled
    critical aspects of configuration, Features and Benefits
    crle, Configure nsswitch.conf and the Winbind Libraries on Linux and Solaris
    cron, Backup Domain Controller Configuration
    cross post, Getting Mailing List Help
    cross-segment browsing, NetBIOS over TCP/IP
    cross-subnet browsing, How Browsing Functions, Configuring Workgroup Browsing, WINS Server Configuration, Behavior of Cross-Subnet Browsing
    CUPS, Features and Benefits, Technical Introduction, Extended Printing Configuration, The [global] Section, Features and Benefits, Overview, Basic CUPS Support Configuration, Using Windows-Formatted Vendor PPDs
    Page Accounting, Page Accounting with CUPS
    quotas, Setting Up Quotas
    CUPS API, Configuration File Syntax, Default UNIX System Printing Commands
    CUPS backends, CUPS Backends
    CUPS filtering, CUPS Also Uses PPDs for Non-PostScript Printers, The CUPS Filtering Architecture
    CUPS filtering chain, CUPS Backends
    CUPS libarary API, Central Print Serving
    CUPS PostScript, Caveats to Be Considered
    CUPS PostScript driver, Windows CUPS PostScript Driver Versus Adobe Driver
    CUPS print filters, Central Print Serving
    CUPS raster, The CUPS Filtering Architecture, pstoraster
    CUPS-PPD, cupsomatic, pdqomatic, lpdomatic, directomatic
    cups.hlp, Caveats to Be Considered
    cupsaddsmb, Driver Upload Methods, cupsaddsmb: The Unknown Utility, Caveats to Be Considered, Run cupsaddsmb (Quiet Mode), Run cupsaddsmb with Verbose Output, Understanding cupsaddsmb, cupsaddsmb with a Samba PDC, cupsaddsmb Flowchart, Installing the PostScript Driver on a Client, Requirements for adddriver and setdriver to Succeed
    cupsd.conf, Default UNIX System Printing Commands, Basic CUPS Support Configuration, mime.convs, Autodeletion or Preservation of CUPS Spool Files
    cupsomatic, Using Windows-Formatted Vendor PPDs, The CUPS Filtering Architecture, The Role of cupsomatic/foomatic, cupsomatic/foomatic-rip Versus Native CUPS Printing, CUPS Print Drivers from Linuxprinting.org, cupsomatic, pdqomatic, lpdomatic, directomatic
    currupted, Features and Benefits
    custom scripts, smbpasswd: Encrypted Password Database
    customer expected, Samba Support
    customers, Samba Support
    customized print commands, Custom Print Commands

    D

    daemon, Starting Samba, Interdomain Trust Relationships, Requirements, Alternative: Starting smbd as a Daemon
    daemon running, Starting and Testing the winbindd Daemon
    daemons, Restarting
    damaged data, Account Flags Management
    data caching, Opportunistic Locking Overview
    data corruption, Browsing of Shares and Directories is Very Slow, UNIX or NFS Client-Accessed Files
    data interchange, File, Directory, and Share Access Controls
    data stream, Technical Introduction
    database, MS Windows Workstation/Server Machine Trust Accounts, Quick Migration Guide
    DatabaseFS, DatabaseFS
    DAVE, Macintosh Clients
    dbx, Internal Errors
    DCE RPC, Join the Samba Server to the PDC Domain
    DDK, PostScript Drivers with No Major Problems, Even in Kernel +Mode, CUPS “PostScript Driver for Windows NT/200x/XP”
    DDNS, TCP/IP without NetBIOS, DNS and Active Directory, Background Information
    de-multiplex, The Front-End Challenge
    de-multiplexing, Demultiplexing SMB Requests
    Debian, Shadow Copy Setup
    Debian Sarge, Shadow Copy Setup
    debug, Internal Errors
    debug level, Debugging with Samba Itself, Debug Levels
    debugging, Debugging with Samba Itself, Debugging-Specific Operations
    debugging passwords, Debugging with Samba Itself
    debugging problems, Debugging with Samba Itself
    dedicated heartbeat, High-Availability Server Products
    dedicated print server, Features and Benefits
    default accounts, Domain Control: Example Configuration
    default aliases, Default Users, Groups, and Relative Identifiers
    default behavior, Identity Mapping (IDMAP)
    default devmode, Setting Device Modes on New Printers
    default DNS setup, Notes
    default gateways, MS Windows XP Professional
    default groups, Default Users, Groups, and Relative Identifiers
    default mapping, Group Mapping Changes in Samba-3.0.23
    default mappings, Mapping Windows Groups to UNIX Groups
    default print command, Default UNIX System Printing Commands
    default print commands, The [global] Section
    default printer, Custom Print Commands
    default printing, Features and Benefits
    default profile, Default Profile for Windows Users, Changing the Default Profile
    default settings, Account Flags Management
    default shells, Starting and Testing the winbindd Daemon
    Default User, MS Windows 200x/XP
    default users, Default Users, Groups, and Relative Identifiers
    defective hardware, Browsing of Shares and Directories is Very Slow
    deferred open, Opportunistic Locking Overview
    defined shares, Why Can Users Access Other Users' Home Directories?
    delegate administrative privileges, Administering User Rights and Privileges
    delegated, Important Administrative Information
    delegation, Trust Relationship Background
    delete, Managing Directories
    delete a file, Protecting Directories and Files from Deletion
    delete roaming profiles, MS Windows 200x/XP
    delete user script, Deleting Accounts
    deleted files, recycle
    deleted parameters, Removed Parameters
    delmem, Nested Groups: Adding Windows Domain Groups to Windows Local Groups
    demote, Domain Controller Types
    demoted, MS Windows NT4-style Domain Control
    denial of service, Using Interface Protection
    deny, Using IPC$ Share-Based Denials
    deny access, Using a Firewall
    deny modes, Discussion
    deny-none, Opportunistic Locking Overview
    DENY_ALL, Discussion
    DENY_DOS, Discussion
    DENY_FCB, Discussion
    DENY_NONE, Discussion
    DENY_READ, Discussion
    DENY_WRITE, Discussion
    deployment, Free Support
    deployment guidelines, Caution Regarding LDAP and Samba
    DES-CBC-CRC, Configure /etc/krb5.conf
    DES-CBC-MD5, Configure /etc/krb5.conf, Testing Server Setup
    desirable solution, What Rights and Privileges Will Permit Windows Client Administration?
    desktop cache, Windows 9x/Me Profile Setup
    desktop profile, Domain Control: Example Configuration, MS Windows NT4-style Domain Control
    desktop profiles, Features and Benefits, Managing Security Identifiers (SIDS)
    deterents, Introduction
    development libraries, Requirements
    devfsd package, Shadow Copy Setup
    device mode, Setting Device Modes on New Printers
    device-specific commands, PostScript Printer Descriptions for Non-PostScript Printers
    DFS, Features and Benefits (see MS-DFS, Distributed File Systems)
    DFS junction, Features and Benefits
    DFS links, Features and Benefits
    DFS root, Features and Benefits
    DFS server, Features and Benefits
    DFS tree, Features and Benefits
    DFS-aware, Features and Benefits
    DFS-aware clients, Features and Benefits
    DHCP, TCP/IP Configuration, MS Windows XP Professional, MS Windows 2000, MS Windows Me, Cross-Subnet Browsing, Background Information, Features and Benefits
    DHCP servers, Comments Regarding LDAP
    DHCP-enabled, MS Windows 2000
    DHCP-enabled operation, MS Windows XP Professional
    diagnostic, IDMAP Storage in LDAP Using Winbind
    diagnostic tools, Debugging with Samba Itself
    diff, Patches
    differences, Rsync
    different resources, Multiple Virtual Server Personalities
    differently encrypted passwords, Technical Information
    differing protocol, Quick Migration Guide
    dir, The Tests
    direct internet access, Introduction
    directory, Active Directory Domain Control, Central Print Serving, Backup Domain Controller
    directory access control, Nested Groups: Adding Windows Domain Groups to Windows Local Groups
    directory access permissions, File, Directory, and Share Access Controls
    directory controls, File, Directory, and Share Access Controls
    Directory Information Tree (see DIT)
    directory permissions, File, Directory, and Share Access Controls, Protecting Directories and Files from Deletion
    directory schema, Primary Domain Controller
    Directory Separators, MS Windows NTFS Comparison with UNIX File Systems
    directory server, ldapsam
    directory_mode, recycle
    disable LMB, Configuring Workgroup Browsing
    disable locking, Features and Benefits
    disable roaming profiles, Disabling Roaming Profile Support
    disabling oplocks, PDM Data Shares
    disass, Internal Errors
    disaster recovery, Server Share and Directory Layout
    disconnect a connection, NT4/200x User Profiles
    disk, Advantages of Encrypted Passwords
    disk space, Server Share and Directory Layout
    disparate information systems, Single Sign-On and Domain Security
    display PostScript, UNIX Printfile Conversion and GUI Basics
    displayName, OpenLDAP Configuration
    distort, UNIX Printfile Conversion and GUI Basics
    distribute authentication systems, Objectives
    distributed, Features and Benefits, Domain Control: Example Configuration
    distributed account, New Account Storage Systems
    Distributed Computing Environment (see DCE)
    distributed directory, Domain Member Server
    distributed file system, The Ultimate Goal (see DFS)
    Distributed File Systems, The Distributed File System Challenge
    distributed file systems, The Distributed File System Challenge
    distributed locking protocol, A Simple Solution
    distribution, Example Configuration, Joining an NT4-type Domain with Samba-3
    dithering algorithm, The Role of cupsomatic/foomatic
    DMB, Preparing for Domain Control, Domain Control: Example Configuration, Security Mode and Master Browsers, What Qualifies a Domain Controller on the Network?, How Browsing Functions, Configuring Workgroup Browsing, Domain Browsing Configuration, Forcing Samba to Be the Master, Making Samba the Domain Master, WINS: The Windows Internetworking Name Server, Windows Networking Protocols, Behavior of Cross-Subnet Browsing
    DMB for a workgroup, Browsing Support in Samba
    DMC, Examples of IDMAP Backend Usage
    DMS, Domain Security Mode (User-Level Security), Overview, Examples of IDMAP Backend Usage, Advanced Configuration Techniques
    DN, LDAP Configuration Notes, Introduction
    DNS, Preparing for Domain Control, How Does a Workstation find its Domain Controller?, NetBIOS Over TCP/IP Disabled, Configure smb.conf, Configure /etc/krb5.conf, MS Windows XP Professional, MS Windows 2000, MS Windows Me, Network Browsing, Features and Benefits, NetBIOS over TCP/IP, TCP/IP without NetBIOS, How Browsing Functions, Cross-Subnet Browsing, Initialize the LDAP Database, Name Service Switch, Background Information, DNS Lookup, The Tests, Features and Benefits, Example Configuration
    Active Directory, DNS and Active Directory
    Dynamic, Background Information, Dynamic DNS
    SRV records, DNS and Active Directory
    DNS Configuration, Browsing of Shares and Directories is Very Slow
    DNS lookup, Configure /etc/krb5.conf
    DNS name resolution, Joining an NT4-type Domain with Samba-3
    dns proxy, Assumptions
    DNS server, Behavior of Cross-Subnet Browsing
    DNS server access, Assumptions
    DNS server settings, MS Windows XP Professional, MS Windows 2000
    DNS servers, Comments Regarding LDAP
    DNS zon, Configure /etc/krb5.conf
    DNS/LDAP/ADS, Technical Overview of Browsing
    document design, Server Share and Directory Layout
    documentation, LDAP Directories and Windows Computer Accounts, Features and Benefits, Analyzing and Solving Samba Problems
    domain, The Special Case of Windows 9x/Me, Adding User Accounts, Name Resolution as Used within MS Windows Networking
    control, Server Types
    role, Domain Controller Types
    controller, Features and Benefits, Domain Security Mode (User-Level Security), Domain Control, Features and Benefits
    convert, Domain Controller Types
    hierarchy, Domain Controller Types
    controllers, Domain Security Mode (User-Level Security)
    groups, UNIX and Windows Group Management
    master
    browser, Preparing for Domain Control
    member, Server Types, Features and Benefits, Domain Controller Types
    server, Features and Benefits
    member server, Features and Benefits
    security, Domain Security Mode (User-Level Security)
    protocols, Features and Benefits
    trust account, Features and Benefits
    domain access, Identity Mapping (IDMAP)
    domain account access policies, Domain Account Policy Managment
    domain admin group, Group Mapping: MS Windows and UNIX
    domain Administrator, The Administrator Domain SID
    Domain Admins, Group Mapping Changes in Samba-3.0.23, Discussion, Nested Groups: Adding Windows Domain Groups to Windows Local Groups, Important Administrative Information, Mapping Windows Groups to UNIX Groups, Using the “net rpc rights” Utility
    Domain Admins group, Discussion
    domain authentication, Overview
    domain context, Domain Layout
    domain control, Basics of Domain Control, Security Mode and Master Browsers, Common Errors, Features and Benefits, Domain Member Server or Domain Member Client, Migration from NT4 PDC to Samba-3 PDC
    backup, Server Types
    primary, Server Types
    domain control database (see SAM)
    domain controller, Security Mode and Master Browsers, Essential Background Information, MS Windows NT4-style Domain Control, Active Directory Domain Control, NetBIOS Over TCP/IP Enabled, MS Windows Workstation/Server Machine Trust Accounts, User Rights and Privileges, What Winbind Provides, Join the Samba Server to the PDC Domain, Creating and Managing System Policies, Features and Benefits, Domain Layout, Steps in Migration Process
    Domain Controller, Caveats to Be Considered
    domain controllers, Samba ADS Domain Control, Joining an NT4-type Domain with Samba-3, MS Windows 200x/XP Professional Policies, Advanced Configuration Techniques, New Features in Samba-3.0.x
    domain environment, Important Notes About Security
    domain global, What Rights and Privileges Will Permit Windows Client Administration?
    domain global group, Overview, What Rights and Privileges Will Permit Windows Client Administration?
    domain global groups, Nested Groups: Adding Windows Domain Groups to Windows Local Groups
    domain global user, What Rights and Privileges Will Permit Windows Client Administration?
    domain global users, Nested Groups: Adding Windows Domain Groups to Windows Local Groups
    domain group, Features and Benefits
    domain group settings, Nested Groups: Adding Windows Domain Groups to Windows Local Groups
    domain groups, Group Mapping Changes in Samba-3.0.23, Group Mapping: MS Windows and UNIX, Default Users, Groups, and Relative Identifiers
    Domain Groups, Accounts and Groups Management
    Domain Guests, Mapping Windows Groups to UNIX Groups
    domain information, New Schema
    domain join, ADS Domains, Join the Samba Server to the PDC Domain
    domain joining, Joining a Domain: Windows 2000/XP Professional
    domain logon, Domain Control: Example Configuration, Domain and Network Logon Configuration, Domain Network Logon Service, Example PDC Configuration, Domain Logon Configuration: Windows 9x/Me
    domain logon server, Windows 9x/Me Profile Setup
    domain logons, The Special Case of Windows 9x/Me, Browsing Support in Samba, Important Notes About Security
    domain management tools, Managing Domain Machine Accounts using NT4 Server Manager
    domain master, Domain Control: Example Configuration, Browsing Support in Samba
    domain member, Domain Security Mode (User-Level Security), Preparing for Domain Control, Domain Membership, Features and Benefits, Windows 200x/XP Professional Client, Common Errors, Joining a Domain: Windows 2000/XP Professional, Important Notes About Security, Discussion, Overview, Handling of Foreign SIDs, Domain Layout
    Domain Member, Domain Member Server or Domain Member Client
    joining, Example Configuration
    domain member client, Important Administrative Information
    Domain Member Client (see DMC)
    domain member server, Example Configuration, Domain Member Server, Joining an NT4-type Domain with Samba-3, TCP/IP without NetBIOS, Nested Groups: Adding Windows Domain Groups to Windows Local Groups, Domain Member Server or Domain Member Client, Features and Benefits
    Domain Member Server (see DMS)
    domain member servers, Example Configuration, Mapping Common UIDs/GIDs on Distributed Machines, Nested Groups: Adding Windows Domain Groups to Windows Local Groups, User Rights and Privileges
    domain member workstations, Nested Groups: Adding Windows Domain Groups to Windows Local Groups
    domain members, Features and Benefits, Domain Browsing Configuration, Introduction
    domain membership, Preparing for Domain Control, Domain Control: Example Configuration, Domain Membership
    domain name, Domain Logon Configuration: Windows 9x/Me
    Domain Name System (see DNS)
    domain non-member, Handling of Foreign SIDs
    domain policies, Windows NT4-Style Policy Files
    domain radio button, Joining a Domain: Windows 2000/XP Professional
    domain security, Features and Benefits, MS Windows NT4-style Domain Control, Domain Membership, Features and Benefits, Domain Member Server, Joining an NT4-type Domain with Samba-3, Why Is This Better Than security = server?, Joining a Domain: Windows 2000/XP Professional, Important Notes About Security, Nested Groups: Adding Windows Domain Groups to Windows Local Groups, Primary Domain Controller, Trust Relationship Background, Join the Samba Server to the PDC Domain, MS Windows 200x/XP
    domain security account, MS Windows Workstation/Server Machine Trust Accounts
    Domain Server Manager, Applicable Only to Versions Earlier than 3.0.11
    domain SID, Backup Domain Controller Configuration, Managing Security Identifiers (SIDS)
    domain trust, Features and Benefits, Creating an NT4 Domain Trust
    domain user, Domain Logon Configuration: Windows 9x/Me, Features and Benefits, What Winbind Provides
    domain user accounts, UNIX and Windows Group Management
    domain user manager, User Account Management
    Domain User Manager, Nested Groups: Adding Windows Domain Groups to Windows Local Groups, Applicable Only to Versions Earlier than 3.0.11, Managing Account/User Policies
    Domain Users, Nested Groups: Adding Windows Domain Groups to Windows Local Groups, Mapping Windows Groups to UNIX Groups
    domain users, Requirements, Linux/FreeBSD-Specific PAM Configuration, Conclusion
    Domain Users group, Adding Domain Users to the Workstation Power Users Group
    domain-level, Why Is This Better Than security = server?
    domain-level security, Joining an NT4-type Domain with Samba-3
    domain-wide browse list, Making Samba the Domain Master
    DOMAIN<1B>, Security Mode and Master Browsers
    DOMAIN<1C>, The Special Case of Windows 9x/Me, Security Mode and Master Browsers
    DOMAIN<1D>, Security Mode and Master Browsers
    draft, The Role of cupsomatic/foomatic
    Drive Identification, MS Windows NTFS Comparison with UNIX File Systems
    driver, Verifying Configuration with testparm
    driver CDROM, Identifying Driver Files
    driver download, [print$] Stanza Parameters
    Driver File, Identifying Driver Files
    driver files, Identifying Driver Files
    Driver Path, Identifying Driver Files
    dual-daemon winbindd, New Features in Samba-3.0.x
    due diligence, Discussion of Backup Solutions
    duplex, Examples for Filtering Chains
    duplex printing, Examples for Filtering Chains
    duplicate, LDAP Configuration Notes
    duplication of information, Introduction
    DVI, MIME Types and CUPS Filters, Prefilters
    Dynamic DNS (see DDNS)
    Dynamic Host Configuration Protocol (see DHCP)
    dynamic link loader, Configure nsswitch.conf and the Winbind Libraries on Linux and Solaris
    dynamic registration files, Dynamic DNS
    Dynamic SMB servers, Objectives
    dynamically loadable library modules, Features and Benefits

    E

    e-Directory, Single Sign-On and Domain Security, Domain Member Server
    EAs, File and Directory Access Control
    economically wise, Features and Benefits
    eDirectory, Comments Regarding LDAP
    editreg, Samba Editreg Toolset
    efficient authentication, Features and Benefits
    election, Security Mode and Master Browsers, How Browsing Functions, Domain Browsing Configuration, Forcing Samba to Be the Master
    election criteria, How Browsing Functions
    election packet, Forcing Samba to Be the Master
    election process, Forcing Samba to Be the Master
    EMF, Windows Drivers, GDI, and EMF, From Windows Clients to an NT Print Server, Driver Execution on the Server
    enables clients to print, Simple Print Configuration
    enables NetBIOS over TCP/IP, NetBIOS over TCP/IP
    encapsulating, NetBIOS over TCP/IP
    encoding, Testing Server Setup
    encryped password, Domain Control: Example Configuration
    encrypted, Features and Benefits, Password Checking, Important Notes About Security
    encrypted password, Advantages of Encrypted Passwords
    encrypted passwords, Password Checking, Features and Benefits, Technical Information, Important Notes About Security, Advantages of Encrypted Passwords, Profile Migration from Windows NT4/200x Server to Samba, Passdb Backends and Authentication
    encrypted session, Security and sambaSamAccount
    encryption, Server Security (User Level Security)
    encryption key, Windows 200x/XP Professional Client
    encryption types, Configure /etc/krb5.conf, Notes
    enforcing, MS Windows Workstation/Server Machine Trust Accounts
    English, Japanese Charsets, Enabling SWAT Internationalization Support
    Enhanced MetaFile (see EMF)
    enterprise, smbpasswd: Encrypted Password Database
    enumdrivers, Identifying Driver Files, A Check of the rpcclient man Page
    enumerate domain groups, Microsoft Remote Procedure Calls
    enumerate domain users, Microsoft Remote Procedure Calls
    EnumJobs(), Printing Developments Since Samba-2.2
    enumprinters, A Check of the rpcclient man Page
    environment variables, Custom Print Commands
    EPM (see ESP meta packager)
    Epson Stylus, Examples for Filtering Chains
    Epson Stylus inkjet, Foomatic Database-Generated PPDs
    equivalence, Privileges Suppored by Windows 2000 Domain Controllers
    equivalent rights and privileges, The Administrator Domain SID
    error message, ADS Domains, Running rpcclient with adddriver
    error messages, Assumptions
    errors that can afflict, Common Errors
    ESC/P, Driver Execution on the Server
    ESP, Ghostscript: The Software RIP for Non-PostScript Printers
    Ghostscript, The CUPS Filtering Architecture, cupsomatic/foomatic-rip Versus Native CUPS Printing
    meta packager, CUPS “PostScript Driver for Windows NT/200x/XP”
    Print Pro, Sources of CUPS Drivers/PPDs, ESP Print Pro PostScript Driver for Windows NT/200x/XP
    ESP Ghostscript, The CUPS Filtering Architecture
    established, Samba as the Trusted Domain
    ethereal, Windows 9x/Me Profile Setup, Tcpdump, Ethereal, The Windows Network Monitor
    Ethernet adapters, Using Interface Protection
    EUC-JP, Japanese Charsets, Basic Parameter Setting
    eucJP-ms locale, Basic Parameter Setting
    Event Viewer, Remote Server Administration
    Everyone - Full Control, Access Controls on Shares
    Everyone group, Printing Developments Since Samba-2.2
    EVMS, shadow_copy
    examples, Example Configuration
    examples/LDAP, New Account Storage Systems
    execute, File and Directory Access Control
    existing LDAP DIT, Caution Regarding LDAP and Samba
    expands control abilities, New Account Storage Systems
    expired password, Changing User Accounts
    explicit trust, Trust Relationship Background
    explicitly set, Rapid Configuration Validation
    exploit opportunities, Features and Benefits
    exploitation, Using Interface Protection
    exported file system, A Simple Solution
    exposed, Using a Firewall
    extd_audit module, extd_audit
    Extended Attributes, File, Directory, and Share Access Controls
    extended attributes, Protecting Directories and Files from Deletion
    Extended BSD Printing, Extended Printing Configuration
    extended characters, What Are Charsets and Unicode?
    extended protocol, Windows Networking Protocols
    extended SAM, New Account Storage Systems
    extra machine, Multiple Virtual Server Hosting

    F

    fail, Features and Benefits
    failed join, NT4-Style Domains (Includes Samba Domains), IDMAP_RID with Winbind
    failed logins, Account Management Tools
    failover communication, High-Availability Server Products
    failover process, High-Availability Server Products
    failover servers, A Simple Solution
    fails, Adding Machine to Domain Fails
    failure, ADS Domains
    failure semantics, Required Modifications to Samba
    fake-permissions module, Mandatory Profiles
    fake_permissions, Domain Control: Example Configuration
    fake_perms, fake_perms, Mandatory Profiles
    fdisk, Shadow Copy Setup
    Federated Identity Management (see FIM)
    federated organizations, Single Sign-On and Domain Security
    federated-identity, Single Sign-On and Domain Security
    Fiber Channel, High-Availability Server Products
    fickle, Features and Benefits
    fid, Demultiplexing SMB Requests
    file access permissions, File, Directory, and Share Access Controls
    File Naming Conventions, MS Windows NTFS Comparison with UNIX File Systems
    file ownership, Features and Benefits
    file serving, Features and Benefits
    File System, MS Windows NTFS Comparison with UNIX File Systems
    case sensitivity, MS Windows NTFS Comparison with UNIX File Systems
    feature comparison, MS Windows NTFS Comparison with UNIX File Systems
    UNIX, MS Windows NTFS Comparison with UNIX File Systems
    Windows, MS Windows NTFS Comparison with UNIX File Systems
    file system capabilities, Protecting Directories and Files from Deletion
    FILE:, Samba and Printer Ports
    filemanager, Problem Resolution
    filename mangling, New Features in Samba-3.0.x
    filter, MIME Types and CUPS Filters
    Filter Oplock, Opportunistic Locking Overview
    FilterLimit, mime.convs
    filters, MIME Types and CUPS Filters
    FIM, Single Sign-On and Domain Security, Comments Regarding LDAP
    firewall, Introduction, Using Interface Protection, The Tests
    firewall active, Using a Firewall
    firewall setups, Using a Firewall
    fixed IP address, MS Windows XP Professional, MS Windows 2000
    fixed IP addresses, TCP/IP Configuration
    flush local locks, Opportunistic Locking Overview
    flush name cache, Flushing the Samba NetBIOS Name Cache
    foomatic, Using Windows-Formatted Vendor PPDs, The CUPS Filtering Architecture, The Role of cupsomatic/foomatic, cupsomatic/foomatic-rip Versus Native CUPS Printing, foomatic-rip and Foomatic Explained, Foomatic's Strange Name
    Foomatic database, Foomatic Database-Generated PPDs
    Foomatic Printer, The Role of cupsomatic/foomatic
    Foomatic tutorial, The Grand Unification Achieved
    foomatic-rip, The CUPS Filtering Architecture, The Role of cupsomatic/foomatic, cupsomatic/foomatic-rip Versus Native CUPS Printing, CUPS Print Drivers from Linuxprinting.org, foomatic-rip and Foomatic Explained, The Grand Unification Achieved
    Foomatic/cupsomatic, cupsomatic/foomatic-rip Versus Native CUPS Printing
    force an election, Forcing Samba to Be the Master
    force election, Making Samba the Domain Master
    forced synchronization, How Browsing Functions
    foreign domain, Mapping User Identifiers between MS Windows and UNIX, Nested Groups: Adding Windows Domain Groups to Windows Local Groups
    foreign SID, Handling of Foreign SIDs
    foreign user, Handling of Foreign SIDs
    FQDN, Introduction
    framing error, Samba Performance Problem Due to Changing Linux Kernel
    free support, Samba Support, Free Support
    FreeBSD, “$” Cannot Be Included in Machine Name, Basic Parameter Setting
    freezing, Shadow Copy Setup
    French, Enabling SWAT Internationalization Support
    front-end virtual server, The Front-End Challenge, Demultiplexing SMB Requests
    frustrating experience, LDAP Directories and Windows Computer Accounts
    FTP, Advantages of Non-Encrypted Passwords
    ftp, Rsync, Accessing the Samba Sources via rsync and ftp
    ftp access, Linux/FreeBSD-Specific PAM Configuration
    ftp service, Linux/FreeBSD-Specific PAM Configuration
    ftp services, Linux/FreeBSD-Specific PAM Configuration
    ftpd, Anatomy of /etc/pam.d Entries
    full rights, Nested Groups: Adding Windows Domain Groups to Windows Local Groups
    functional components, Debugging-Specific Operations
    functionality, Objectives

    G

    gateway address, MS Windows XP Professional
    gcc, Debugging with Samba Itself, HPUX
    gdb, Debugging with Samba Itself, Internal Errors, Attaching to a Running Process
    GDI, GDI on Windows, PostScript on UNIX, Windows Drivers, GDI, and EMF, From Windows Clients to an NT Print Server, Driver Execution on the Server
    general security service application programming interface (see GSSAPI)
    generic PostScript, MIME Types and CUPS Filters
    generic raster, pstoraster
    generic raster format, The CUPS Filtering Architecture
    genlogon.pl, Network Logon Script Magic
    Gentoo, Samba Performance Problem Due to Changing Linux Kernel
    Germany, Technical Discussion
    get, The Tests
    getdriver, Identifying Driver Files, Installing Driver Files into [print$]
    getdriverdir, A Check of the rpcclient man Page
    getent, Adding or Creating a New Group, IDMAP_RID with Winbind, Starting and Testing the winbindd Daemon
    getent group demo, Nested Groups: Adding Windows Domain Groups to Windows Local Groups
    gethostbyname() function call, Name Resolution Order
    getpwnam, Schema and Relationship to the RFC 2307 posixAccount, Domain Member Server or Domain Member Client
    getpwnam() call, Changes in Behavior
    GetSID.exe, Get SID
    GhostScript, PostScript and Ghostscript, Ghostscript: The Software RIP for Non-PostScript Printers
    (see also PostScript)
    Ghostscript, The CUPS Filtering Architecture, PostScript Printer Descriptions for Non-PostScript Printers
    ESP (see ESP + GhostScript)
    GID, Example Configuration, Manual Creation of Machine Trust Accounts, Why Is This Better Than security = server?, Sharing User ID Mappings between Samba Domain Members, User and Group Changes, Passdb Changes, Group Mapping Changes in Samba-3.0.23, Mapping Common UIDs/GIDs on Distributed Machines, Features and Benefits, Overview, Mapping Windows Groups to UNIX Groups, Identity Mapping (IDMAP), Domain Member Server or Domain Member Client, Primary Domain Controller, Features and Benefits, Handling of Foreign SIDs, Starting and Testing the winbindd Daemon
    GID numbers, Domain Member Server or Domain Member Client
    GID range, Interdomain Trust Relationships
    GIF, MIME Types and CUPS Filters
    global print command, Custom Print Commands
    global right, Description of Privileges
    global section, The [global] Section
    Global support, Objectives
    global-level, Printing-Related Configuration Parameters
    GNOME, Remote Management from NoMachine.Com
    GNU Ghostscript, The CUPS Filtering Architecture, pstoraster
    GNU GPL, BackupPC
    GNU tar, Amanda
    GNU/Linux, Discussion
    GPG, Verifying Samba's PGP Signature
    GPL, Remote Management from NoMachine.Com
    gpolmig.exe, Administration of Windows 200x/XP Policies
    GPOs, Features and Benefits, MS Windows 200x/XP Professional Policies, Administration of Windows 200x/XP Policies, Managing Account/User Policies, System Startup and Logon Processing Overview, MS Windows 200x/XP
    grace time, Changing User Accounts
    grant rights, Using the “net rpc rights” Utility
    graphical objects, UNIX Printfile Conversion and GUI Basics
    graphically illustrated client configuration, Features and Benefits
    grayscale, The Role of cupsomatic/foomatic
    greater scalability, New Account Storage Systems
    greatest mistake, Common Errors
    grep, Configure nsswitch.conf and the Winbind Libraries on Linux and Solaris
    group, Example Configuration, User and Group Changes, LDAP Directories and Windows Computer Accounts, File and Directory Access Control
    account, Domain Control: Example Configuration
    mapping, Features and Benefits
    group account, Important Administrative Information, Backup Domain Controller
    group accounts, Domain Logon Configuration: Windows 9x/Me, Caution Regarding LDAP and Samba, Features and Benefits, Warning: User Private Group Problems, Domain Member Server or Domain Member Client
    group management, Overview, UNIX and Windows Group Management
    group mapping, User and Group Changes, Group Mapping: MS Windows and UNIX
    group mappings, Group Mapping Changes in Samba-3.0.23, Features and Benefits
    group membership, Nested Groups: Adding Windows Domain Groups to Windows Local Groups
    group ownership, Features and Benefits
    group permissions, User and Group Changes, Server Share and Directory Layout
    Group Policies, Features and Benefits
    group policies, Features and Benefits
    group policy, Domain Control: Example Configuration
    Group Policy, Windows 9x/ME Policies
    Group Policy Container (see GPC)
    Group Policy Editor, Windows 9x/ME Policies, Windows NT4/200x, Samba-3 Implementation Choices
    Group Policy Objects, Objectives (see GPO)
    group policy objects (see GPOs)
    Group Policy Template (see GPT)
    group privileges, Discussion
    group profiles, Creating and Managing Group Profiles
    group SID, Managing Security Identifiers (SIDS)
    groupadd, Features and Benefits, Sample smb.conf Add Group Script, Adding Groups Fails
    groupadd limitations, Sample smb.conf Add Group Script
    groupdel, Features and Benefits
    groupmap, Group Mapping: MS Windows and UNIX
    groupmod, Features and Benefits
    grouppol.inf, Windows 9x/ME Policies
    groups, UNIX and Windows Group Management, Features and Benefits
    domain, Discussion
    mapping, Group Mapping: MS Windows and UNIX
    nested, Nested Groups: Adding Windows Domain Groups to Windows Local Groups
    groups of users, Administering User Rights and Privileges
    growing, Shadow Copy Setup
    GSSAPI, Single Sign-On and Domain Security
    gtklp, Foomatic Database-Generated PPDs
    guest, Domain Control: Example Configuration, Reference Documentation Server
    guest account, Central Print Serving, Problem Resolution, Custom Print Commands, The Tests
    GUI, Overview
    Gutenprint, rasterto [printers specific], Driver Development Outside

    H

    h-node, NetBIOS over TCP/IP
    harvesting password hashes, Security and sambaSamAccount
    hashed password equivalent, Important Notes About Security
    headers files, Possible Errors
    Heimdal, Configure /etc/krb5.conf, ADS Domains, Features and Benefits
    Heimdal kerberos, ADS Domains, IDMAP Storage in LDAP Using Winbind
    help, Free Support
    help command, The Tests
    heterogeneous computing, Features and Benefits
    HEX, Japanese Charsets
    hi-res photo, The Role of cupsomatic/foomatic
    high availability, Features and Benefits
    high order ports, Using a Firewall
    high-availability, Opportunistic Locking Overview
    high-availability services, High-Availability Server Products
    high-speed server interconnect, A Simple Solution
    higher availability, Features and Benefits
    HKEY_CURRENT_USER, MS Windows NT4 Workstation
    HKEY_LOCAL_MACHINE, Registry Spoiling
    holy grail, Features and Benefits
    home directories, New Account Storage Systems, Starting and Testing the winbindd Daemon
    home directory, Manual Creation of Machine Trust Accounts, smbpasswd: Encrypted Password Database
    home directory template, Linux/FreeBSD-Specific PAM Configuration
    home drive, Example PDC Configuration
    host multiple servers, Multiple Virtual Server Personalities
    host security, Features and Benefits
    host-based protection, Features and Benefits
    hostname, Configure /etc/krb5.conf
    hosts allow, The Tests
    hosts deny, The Tests
    house-keeping, Description of Privileges
    HOWTO documents, Caution Regarding LDAP and Samba
    HP JetDirect, Examples for Filtering Chains
    HP Photosmart, Foomatic Database-Generated PPDs
    HP-GL, MIME Types and CUPS Filters
    HP-GL., Prefilters
    hpgltops, MIME Type Conversion Rules
    HPIJS, Driver Development Outside
    HPUX, The [global] Section
    http, Rsync
    hybrid, NetBIOS over TCP/IP
    Hybrid node, Static WINS Entries

    I

    IANA, pstoraster
    ID mapping, Example Configuration, New Features in Samba-3.0.x
    ID mapping database, User and Group ID Allocation
    ID range, Features and Benefits
    IDEALX, ldapsam
    Identification, Domain Logon Configuration: Windows 9x/Me
    identify, ADS Domains
    identity, Standalone Samba Server
    identity information, Single Sign-On and Domain Security
    identity management, Single Sign-On and Domain Security, Domain Member Server
    centralized, Single Sign-On and Domain Security
    identity resolution, Features and Benefits
    IDMAP, Group Mapping Changes in Samba-3.0.23, Features and Benefits, Identity Mapping (IDMAP), Standalone Samba Server, Domain Member Server or Domain Member Client, IDMAP_RID with Winbind
    idmap, New Schema
    idmap backend, Example Configuration, Mapping Common UIDs/GIDs on Distributed Machines, Domain Member Server or Domain Member Client, Features and Benefits, IdMap LDAP Support
    IDMAP backend, Mapping Common UIDs/GIDs on Distributed Machines
    idmap gid, Mapping User Identifiers between MS Windows and UNIX, Domain Member Server or Domain Member Client, IDMAP_RID with Winbind, Features and Benefits
    idmap GID, New Schema
    IDMAP infrastructure, Identity Mapping (IDMAP)
    idmap uid, Mapping User Identifiers between MS Windows and UNIX, Features and Benefits, Domain Member Server or Domain Member Client, IDMAP_RID with Winbind, Features and Benefits
    idmap UID, New Schema
    idmap_ad, Mapping Common UIDs/GIDs on Distributed Machines
    idmap_ldap module, New Schema
    idmap_rid, Domain Member Server or Domain Member Client, IDMAP_RID with Winbind
    IETF, Overview
    ifconfig, Starting from inetd.conf, Samba Performance Problem Due to Changing Linux Kernel
    ignore connection, Using Interface Protection
    imagetoraster, imagetops and imagetoraster
    immutible, Protecting Directories and Files from Deletion
    impersonate, Security and sambaSamAccount
    implementing oplocks, Advanced Samba Oplocks Parameters
    Implicit Classes, Print Queue Called “lp” Mishandles Print Jobs
    important announcements, Upgrading Samba
    Imprints, The Imprints Toolset
    imprints, Driver Upload Methods
    include, Advanced Configuration Techniques
    independent, Background, Multiple Server Hosting
    individual domain user, Nested Groups: Adding Windows Domain Groups to Windows Local Groups
    individual section, The [global] Section
    inetd, Validate SWAT Installation, The Tests, Starting the smbd nmbd and winbindd, Starting from inetd.conf
    inetd.conf, The Tests
    inetorgperson.schema, OpenLDAP Configuration
    inf file, Identifying Driver Files
    infrastructure, Comments Regarding LDAP, Target Uses
    inheritance, Protecting Directories and Files from Deletion
    inherits rights, Discussion
    initdb.ldif, The Primary Domain Controller
    initGroups.sh, Example: Engineering Office, Script to Configure Group Mapping, Steps in Migration Process
    inktype, The Role of cupsomatic/foomatic
    insecure, Features and Benefits, Using Host-Based Protection
    inspire simplicity, Example Configuration
    inspired structure, Technical Discussion
    install drivers, Features and Benefits, Point'n'Print Client Drivers on Samba Servers
    interactive help, Free Support
    interdomain
    trust
    account, Features and Benefits
    trustrs, Features and Benefits
    interdomain connection, Samba as the Trusting Domain
    interdomain trust, Configuring Samba NT-Style Domain Trusts, NT4-Style Domain Trusts with Windows 2000
    interdomain trust accounts, Account Information Databases, Caution Regarding LDAP and Samba
    interdomain trusts, Overview, Features and Benefits
    Interdomain Trusts, Interdomain Trust Relationships
    Completing, Completing an NT4 Domain Trust
    creating, Native MS Windows NT4 Trusts Configuration
    Facilities, Interdomain Trust Facilities
    interface, MS Windows XP Professional
    interface scripts, User Account Management
    interface-based exclusion, Features and Benefits
    interfaces, Using Interface Protection, Multiple Server Hosting
    intermediate information, Caution Regarding LDAP and Samba
    intermediate tools, Comments Regarding LDAP
    internal ordering, Features and Benefits
    internationalization support, Guidelines and Technical Tips
    Internet, Using Host-Based Protection, Using Interface Protection
    Internet Engineering Task Force (see IETF)
    Internet Printing Protocol (see IPP)
    Internet Protocol TCP/IP, MS Windows Me
    Internetworking Packet Exchange (see IPX)
    internetworking super daemon, Features and Benefits
    interoperability, Features and Benefits, Features and Benefits, Single Sign-On and Domain Security, Identity Mapping (IDMAP), File, Directory, and Share Access Controls, Features and Benefits, Restrictive Constraints on Distributed File Systems
    intolerance, Features and Benefits
    invalid shell, Example Configuration
    invalid users, The Tests
    IP address, The Tests
    IP address automatically, MS Windows XP Professional, MS Windows 2000
    IP addresses, /etc/hosts
    IP aliases, MS Windows XP Professional
    IPC$, The Special Case of Windows 9x/Me, Problem Resolution, Using IPC$ Share-Based Denials
    IPC$ connections, The Front-End Challenge
    ipchains, The Tests
    ipconfig, TCP/IP without NetBIOS
    iPlanet, Domain Member Server
    IPP, Understanding cupsaddsmb
    IPP client, Administrator Cannot Install Printers for All Local Users
    iptables, The Tests
    IPX, Windows Networking Protocols
    IRC, Free Support
    IRIX, Discussion, Basic Parameter Setting
    ISC
    DHCP, Features and Benefits
    DNS, Features and Benefits
    ISC DHCP server, MS Windows XP Professional, MS Windows Me
    isolated workgroup, Configuring Workgroup Browsing
    IXFR, Background Information

    J

    Japanese, Japanese Charsets, Enabling SWAT Internationalization Support
    Japanese locale, Basic Parameter Setting
    Japanese UNIX, Basic Parameter Setting
    Java, Remote Management with ThinLinc, Basic Parameter Setting
    JIS X 0208, Japanese Charsets
    join, NT4-Style Domains (Includes Samba Domains)
    join client, Description of Privileges
    join domain, Joining Domain Fails Because of Existing Machine Account
    join the ADS domain, Joining an NT4-type Domain with Samba-3
    join the domain, Domain Member Server, Joining an NT4-type Domain with Samba-3
    join the machine, Windows NT4 Client
    joined client, MS Windows Workstation/Server Machine Trust Accounts
    Joined domain, Joining an NT4-type Domain with Samba-3
    joining domain, Join the Samba Server to the PDC Domain
    joining the domain, Joining an NT4-type Domain with Samba-3
    JPEG, MIME Types and CUPS Filters

    K

    KB 129202, Additional Reading
    KB 224992, Additional Reading
    KB 296264, Additional Reading
    KB 811492, Long Delays Deleting Files over Network with XP SP1
    KB 812937, Problems Saving Files in MS Office on Windows XP
    KDC, Samba ADS Domain Membership, Configure /etc/krb5.conf
    KDE, Remote Management from NoMachine.Com
    KDE konqueror, Remote Management from NoMachine.Com
    KDE session, Remote Management from NoMachine.Com
    KDEPrint, Overview
    kerberos, Features and Benefits, Configure /etc/krb5.conf, ADS Domains
    Kerberos, Samba ADS Domain Membership, Configure /etc/krb5.conf, Possible Errors, Testing with smbclient, Trust Relationship Background, Microsoft Active Directory Services, Features and Benefits, Passdb Backends and Authentication
    /etc/krb5.conf, Configure /etc/krb5.conf
    Kerberos authentication, Testing with smbclient
    killall, Starting from inetd.conf
    kinit, Configure /etc/krb5.conf, Create the Computer Account, Possible Errors
    kixstart, Logon Scripts
    kprinter, Foomatic Database-Generated PPDs
    KRB, ADS Domains
    KRB5, Configure /etc/krb5.conf
    krb5.conf, Configure /etc/krb5.conf

    L

    LAN, Forcing Samba to Be the Master, Remote Management with ThinLinc, High-Availability Server Products, Diagnostics Tools
    LanMan, Features and Benefits, Essential Background Information, MS Windows Workstation/Server Machine Trust Accounts, Technical Information, Printing Developments Since Samba-2.2
    LanMan logon service, Preparing for Domain Control
    LanMan passwords, Backward Compatibility Account Storage Systems
    LanManager, User Level Security, Domain Logon Configuration: Windows 9x/Me
    LanManager-compatible, WINS: The Windows Internetworking Name Server
    LanManger password, Listing User and Machine Accounts
    laptops, BackupPC
    large directory, Handling Large Directories
    large domain, IDMAP_RID with Winbind
    large numbers of files, Handling Large Directories
    large organizations, Trust Relationship Background
    last change time, Listing User and Machine Accounts
    latency, Slow and/or Unreliable Networks
    laws, The pdbedit Tool
    LCT (see last change time)
    LDAP, Features and Benefits, Single Sign-On and Domain Security, Domain Controller Types, LDAP Configuration Notes, Backup Domain Controller Configuration, How Do I Replicate the smbpasswd File?, Can I Do This All with LDAP?, Features and Benefits, Domain Member Server, Sharing User ID Mappings between Samba Domain Members, Account Information Databases, New Account Storage Systems, Important Notes About Security, Mapping Common UIDs/GIDs on Distributed Machines, Comments Regarding LDAP, Caution Regarding LDAP and Samba, LDAP Directories and Windows Computer Accounts, ldapsam, Supported LDAP Servers, Schema and Relationship to the RFC 2307 posixAccount, Initialize the LDAP Database, Configuring Samba, Default Users, Groups, and Relative Identifiers, Identity Mapping (IDMAP), Domain Member Server or Domain Member Client, Backup Domain Controller, Interdomain Trust Relationships, Features and Benefits, Trust Relationship Background, Printing Developments Since Samba-2.2, Microsoft Active Directory Services, Features and Benefits, Passdb Backends and Authentication, Domain Layout
    directories, Comments Regarding LDAP
    master, LDAP Configuration Notes
    server, LDAP Configuration Notes
    slave, Features and Benefits, LDAP Configuration Notes
    LDAP administration password, Backup Domain Controller Configuration
    LDAP administrative password, Sharing User ID Mappings between Samba Domain Members
    LDAP backend, Background, Primary Domain Controller, Quick Migration Guide
    LDAP backends, Mapping Common UIDs/GIDs on Distributed Machines
    LDAP database, Example Configuration, Initialize the LDAP Database, Domain Layout
    LDAP deployment, Comments Regarding LDAP
    LDAP directory, Comments Regarding LDAP, Account Flags Management, ldapsam, New Features in Samba-3.0.x
    ldap group suffix, New Schema, New Suffix for Searching
    LDAP idmap Backend, Mapping Common UIDs/GIDs on Distributed Machines
    ldap idmap suffix, Sharing User ID Mappings between Samba Domain Members, New Schema, New Suffix for Searching
    ldap machine suffix, New Suffix for Searching
    LDAP queries, New Suffix for Searching
    LDAP redirects, Domain Member Server or Domain Member Client
    LDAP schema, LDAP Changes in Samba-3.0.23
    LDAP server, Domain Member Server or Domain Member Client
    ldap suffix, New Schema, New Suffix for Searching
    ldap user suffix, New Suffix for Searching
    LDAP-based, Mapping Common UIDs/GIDs on Distributed Machines, Interdomain Trust Relationships
    LDAP., LDAP Directories and Windows Computer Accounts
    LDAP/Kerberos, New Features in Samba-3.0.x
    LDAPS, Security and sambaSamAccount
    ldapsam, Domain Control: Example Configuration, MS Windows Workstation/Server Machine Trust Accounts, Account Information Databases, smbpasswd: Encrypted Password Database, ldapsam, Supported LDAP Servers, Default Users, Groups, and Relative Identifiers, Primary Domain Controller, New Schema, Objectives
    ldapsam_compat, Backward Compatibility Account Storage Systems, New Schema
    ldapsearch, New Schema
    LDAPv3, Security and sambaSamAccount
    ldconfig, Configure nsswitch.conf and the Winbind Libraries on Linux and Solaris
    ldd, Linking smbd with libcups.so
    LDIF, Initialize the LDAP Database, New Schema
    LDIF file, Initialize the LDAP Database
    legacy systems, Single Sign-On and Domain Security
    legal UNIX system account name, Adding Machine to Domain Fails
    Level1 Oplock, Opportunistic Locking Overview
    Level1 oplock, Opportunistic Locking Overview
    Level2 Oplock, Opportunistic Locking Overview
    LGPL, ldapsam
    libcups, Default UNIX System Printing Commands, Linking smbd with libcups.so
    libcups.so, Linking smbd with libcups.so
    libcups.so.2, Linking smbd with libcups.so
    Liberty Alliance, Single Sign-On and Domain Security
    libiconv, Basic Parameter Setting
    libnss_winbind, Nested Groups: Adding Windows Domain Groups to Windows Local Groups, Configure nsswitch.conf and the Winbind Libraries on Linux and Solaris
    libnss_winbind.so, Name Service Switch, Configure nsswitch.conf and the Winbind Libraries on Linux and Solaris
    libnss_wins.so, /etc/nsswitch.conf
    libraries, Configure /etc/krb5.conf
    licensing, Objectives
    limitations, Trust Relationship Background
    linewidth, UNIX Printfile Conversion and GUI Basics
    link loader configuration, Configure nsswitch.conf and the Winbind Libraries on Linux and Solaris
    Links
    hard, MS Windows NTFS Comparison with UNIX File Systems
    soft, MS Windows NTFS Comparison with UNIX File Systems
    Linux, Mapping Common UIDs/GIDs on Distributed Machines, Remote Management with ThinLinc, Features and Benefits, Basic Parameter Setting
    Linux High Availability project, High-Availability Server Products
    Linux LVM, Shadow Copy Setup
    Linux LVM partition, Shadow Copy Setup
    LinuxKongress2002, The Grand Unification Achieved
    Linuxprinting.org, The Role of cupsomatic/foomatic, CUPS Print Drivers from Linuxprinting.org, Driver Development Outside
    list of domain controllers, Joining an NT4-type Domain with Samba-3
    listen for connections, Using Interface Protection
    listen own socket, Multiple Server Hosting
    LLC, Integrating MS Windows Networks with Samba
    LM/NT password hashes, smbpasswd: Encrypted Password Database, Security and sambaSamAccount
    LMB, Preparing for Domain Control, How Browsing Functions, Configuring Workgroup Browsing, Domain Browsing Configuration, Forcing Samba to Be the Master, Making Samba the Domain Master, Use of the Remote Browse Sync Parameter, WINS: The Windows Internetworking Name Server, Windows Networking Protocols, Browsing Support in Samba, Behavior of Cross-Subnet Browsing (see Local Master Browser)
    LMHOSTS, How Browsing Functions, The LMHOSTS File
    lmhosts, WINS: The Windows Internetworking Name Server
    load balancing, Features and Benefits
    loaded modules, Features and Benefits
    loading printer drivers, Any [my_printer_name] Section
    local
    groups, UNIX and Windows Group Management
    master
    browser, Preparing for Domain Control
    local access permissions, Nested Groups: Adding Windows Domain Groups to Windows Local Groups
    local accounts, Domain Member Server or Domain Member Client
    local administrative privileges, Nested Groups: Adding Windows Domain Groups to Windows Local Groups
    Local Area Connection, MS Windows XP Professional
    Local Area Connection Properties, MS Windows 2000
    local authentication, Background
    local authentication database, Background
    local cache, The NetBIOS Name Cache
    local disk, BackupPC
    local domain, Handling of Foreign SIDs
    local group, What Rights and Privileges Will Permit Windows Client Administration?
    local groups, Nested Groups: Adding Windows Domain Groups to Windows Local Groups, Domain Member Server or Domain Member Client, Name Service Switch
    Local Machine Trust Account, Machine Accounts Keep Expiring
    Local Master Browser, NetBIOS over TCP/IP, Domain Browsing Configuration, Use of the Remote Announce Parameter
    local master browser (see LMB)
    local names, NetBIOS over TCP/IP
    local print driver, [print$] Stanza Parameters
    local profile, Disabling Roaming Profile Support, Windows 9x/Me Profile Setup
    local profiles, Features and Benefits
    local registry values, MS Windows 200x/XP Professional Policies
    Local security policies, Windows 200x/XP Local Security Policies
    local smbpasswd file, Background
    local spool area, Technical Introduction
    local subnet, Forcing Samba to Be the Master
    local system printing, Technical Introduction
    local UNIX groups, Overview
    local user, Standalone Samba Server, Restarting
    local user account, Mapping User Identifiers between MS Windows and UNIX
    local users, Domain Member Server or Domain Member Client, Name Service Switch
    locale, Enabling SWAT Internationalization Support
    localhost, Using Host-Based Protection
    locally known UID, Mapping Windows Groups to UNIX Groups
    locate domain controller, How Does a Workstation find its Domain Controller?
    Lock caching, Opportunistic Locking Overview
    lock directory, Multiple Server Hosting
    lock password, Central Print Serving
    lock the account, Changing User Accounts
    locking, File and Record Locking, Features and Benefits, Discussion, The Distributed File System Challenge
    locking protocol, Features and Benefits
    locking semantics, Features and Benefits, Discussion
    locking.tdb, The Printing *.tdb Files
    (see also TDB)
    lockout, Example Configuration
    log files, Assumptions
    monitoring, Assumptions
    log level, ADS Domains, Windows 9x/Me Profile Setup, Debugging with Samba Itself, Debug Levels
    log.nmbd, Problem Resolution, The Tests
    logging, Configuration of Auditing, Debugging-Specific Operations
    logical directories, Features and Benefits
    Logical Link Control (see LLC)
    logical volume, Shadow Copy Setup
    Logical Volume Manager (see LVM)
    Login, Advantages of Non-Encrypted Passwords
    login, Linux/FreeBSD-Specific PAM Configuration, Features and Benefits
    login id, Listing User and Machine Accounts
    login name, Example Configuration
    login shells, Comments Regarding LDAP
    LoginID, Domain Member Server or Domain Member Client
    logon, Domain Security Mode (User-Level Security)
    logon authentication, NetBIOS Over TCP/IP Disabled
    logon drive, Domain Control: Example Configuration
    logon home, Domain Control: Example Configuration, Windows 9x/Me User Profiles
    logon name, User Mapping
    logon path, Domain Control: Example Configuration
    logon processing, Domain Control: Example Configuration
    logon requests, Essential Background Information, NetBIOS Over TCP/IP Enabled, Can Samba Be a Backup Domain Controller to an NT4 PDC?
    logon script, Domain Control: Example Configuration, Features and Benefits
    Logon Scripts, Objectives
    Logon scripts, Logon Scripts
    logon server, The Special Case of Windows 9x/Me, MS Windows NT4 Workstation
    logons, NT4/200x User Profiles
    lookups, smbpasswd: Encrypted Password Database
    loopback adapter, The Tests
    loopback interface, Using Interface Protection, Red Hat Linux
    lower-case, User Level Security
    lowercase filenames, Handling Large Directories
    lp, Verifying Configuration with testparm, Print Queue Called “lp” Mishandles Print Jobs
    lpadmin, “Raw” Printing, Printing with Interface Scripts, CUPS Print Drivers from Linuxprinting.org, Setting Up Quotas
    LPD, The [global] Section
    lpinfo, CUPS Backends
    lpq cache time, The [global] Section
    lpq command, The [global] Section
    LPRNG, The [global] Section
    lpstat, Configuration File Syntax, Troubleshooting Revisited
    LPT1:, Samba and Printer Ports
    LsaEnumTrustedDomains, Debugging with Samba Itself
    LTSP, Remote Management from NoMachine.Com
    Lustre, The Distributed File System Challenge
    lvcreate, Shadow Copy Setup
    LVM, shadow_copy, Shadow Copy Setup
    LVM snapshots, Shadow Copy Setup
    LVM volume, Shadow Copy Setup
    lvm10 package, Shadow Copy Setup

    M

    m-node, NetBIOS over TCP/IP
    MAC address, /etc/hosts
    MAC Addresses, /etc/hosts
    Mac OS X , Basic Parameter Setting
    machine, LDAP Directories and Windows Computer Accounts
    account, Domain Security Mode (User-Level Security)
    machine account, Features and Benefits, Domain Controller Types, LDAP Configuration Notes, Account Flags Management, tdbsam, User Rights and Privileges
    machine account password
    change protocol, Joining an NT4-type Domain with Samba-3
    machine accounts, Manual Creation of Machine Trust Accounts, LDAP Directories and Windows Computer Accounts, Account Management Tools, User Rights and Privileges
    machine accounts database, MS Windows NT4-style Domain Control
    machine authentication, Domain Member Server
    machine name, /etc/hosts, Name Resolution as Used within MS Windows Networking
    Machine Policy Objects, Objectives
    machine SID, Managing Security Identifiers (SIDS)
    machine trust account, Features and Benefits, Preparing for Domain Control, The Special Case of Windows 9x/Me, Domain Membership, Windows 200x/XP Professional Client, Create the Computer Account, Cannot Add Machine Back to Domain
    create privilege, Windows 200x/XP Professional Client
    creation, MS Windows Workstation/Server Machine Trust Accounts
    password, Preparing for Domain Control, MS Windows Workstation/Server Machine Trust Accounts
    Machine Trust Account, MS Windows Workstation/Server Machine Trust Accounts, Manual Creation of Machine Trust Accounts, Windows NT4 Client
    creation, On-the-Fly Creation of Machine Trust Accounts
    password, Manual Creation of Machine Trust Accounts
    UNIX account, On-the-Fly Creation of Machine Trust Accounts
    Machine Trust Accounts, Machine Accounts Keep Expiring, MS Windows Workstation/Server Machine Trust Accounts
    creating, MS Windows Workstation/Server Machine Trust Accounts
    machine trust accounts, How Do I Replicate the smbpasswd File?, Managing Domain Machine Accounts using NT4 Server Manager, Common Errors, Account Information Databases, Caution Regarding LDAP and Samba
    machine_name, Manual Creation of Machine Trust Accounts
    machine_nickname, Manual Creation of Machine Trust Accounts
    Macintosh, Basic Parameter Setting
    macros, Custom Print Commands
    mail, Comments Regarding LDAP
    mailing list, Free Support
    mailing lists, Free Support
    maintaining ids, New Features in Samba-3.0.x
    major changes, New Functionality
    make, /etc/nsswitch.conf, Building the Binaries
    man, Features and Benefits
    man page, Configure smb.conf
    man pages, Overview
    man-in-the-middle, User Rights and Privileges
    manage accounts, The pdbedit Tool
    manage drivers, Features and Benefits
    manage groups, Administering User Rights and Privileges
    manage printers, Administering User Rights and Privileges
    manage privileges, Rights Management Capabilities
    manage roaming profiles, Features and Benefits
    manage share permissions, Windows NT4 Workstation/Server
    manage share-level ACL, Applicable Only to Versions Earlier than 3.0.11
    manage shares, Administering User Rights and Privileges
    manage users, Administering User Rights and Privileges
    manageability, Objectives
    Manageability, Objectives
    managed by humans, Features and Benefits
    management bottleneck, Multiuser Databases
    management costs, Comments Regarding LDAP
    management overheads, Single Sign-On and Domain Security
    management procedures, Single Sign-On and Domain Security
    management tools, Account Management Tools
    managing rights, Using the “net rpc rights” Utility
    mandatory profiles, Mandatory Profiles
    Mandrake, Forums, Downloads, Tutorials, Howtos (Also for Mac OS X and Commercial UNIX)
    Mandriva, Forums, Downloads, Tutorials, Howtos (Also for Mac OS X and Commercial UNIX)
    manual UNIX account creation, MS Windows Workstation/Server Machine Trust Accounts
    manual WINS server entries, MS Windows XP Professional, MS Windows 2000
    manually configured, MS Windows Me
    manually configured DNS settings, MS Windows XP Professional
    map, Windows 200x/XP Professional Client, User and Group Accounts
    mapped, Important Administrative Information, Overview, Mapping Windows Groups to UNIX Groups
    mapping, Mapping User Identifiers between MS Windows and UNIX, Mapping Windows Groups to UNIX Groups
    mapping home directory, Why Can Users Access Other Users' Home Directories?
    mapping printer driver, Running rpcclient with setdriver
    mappings, Sharing User ID Mappings between Samba Domain Members
    maps UNIX users and groups, Sharing User ID Mappings between Samba Domain Members
    master browser, Forcing Samba to Be the Master
    master browsers, Behavior of Cross-Subnet Browsing
    master server, Domain Layout
    master smb.conf, Multiple Virtual Server Hosting
    MasterAnnouncement, Behavior of Cross-Subnet Browsing
    match case, Handling Large Directories
    maximum value, Interdomain Trust Relationships
    mbd kept spawning, Corrupt tdb Files
    Meccano set, Discussion of Backup Solutions
    mechanism, Joining an NT4-type Domain with Samba-3
    media type, The Role of cupsomatic/foomatic
    member, Preparing for Domain Control, Using the “net rpc rights” Utility
    member machine, Nested Groups: Adding Windows Domain Groups to Windows Local Groups
    memory, Advantages of Encrypted Passwords
    messages.tdb, The Printing *.tdb Files
    (see also TDB)
    messaging systems, Comments Regarding LDAP
    Meta node, Static WINS Entries
    meta-directory, Single Sign-On and Domain Security
    meta-service, Configuration File Syntax
    meta-services, Multiple Virtual Server Personalities
    Microsoft Active Directory, Features and Benefits
    Microsoft Developer Network CDs, The Windows Network Monitor
    Microsoft driver, PostScript Drivers with No Major Problems, Even in Kernel +Mode
    Microsoft management console (see MMC)
    Microsoft Remote Procedure Call (see MSRPC)
    Microsoft Windows 9x/Me, Managing Domain Machine Accounts using NT4 Server Manager
    Microsoft Wolfpack, High-Availability Server Products
    middle-ware, Comments Regarding LDAP
    migrate, Server Types and Security Modes, Migration from NT4 PDC to Samba-3 PDC
    migrate account settings, User and Group Accounts
    migrate group, User and Group Accounts
    migrate user, User and Group Accounts
    migrating, New Features in Samba-3.0.x
    migration, Objectives
    migration plan, Planning and Getting Started
    migration process, Objectives
    MIME, MIME Types and CUPS Filters, MIME Type Conversion Rules, Filtering Overview, application/octet-stream Printing
    filters, MIME Types and CUPS Filters
    raw, Anonymous Print Server, Central Print Serving, Explicitly Enable “raw” Printing for application/octet-stream
    MIME conversion rules, The CUPS Filtering Architecture
    MIME recognition, The CUPS Filtering Architecture
    MIME type, Explicitly Enable “raw” Printing for application/octet-stream, The CUPS Filtering Architecture, Prefilters, application/octet-stream Printing
    mime.types, MIME Types and CUPS Filters
    minimal
    configuration, Configuration File Syntax
    minimal configuration, Configuration File Syntax
    minimum security control, Standalone Servers
    misconfigurations, Test Your Config File with testparm
    misconfigured settings, Simple Print Configuration
    misinformation, Domain Membership
    mission-critical, Opportunistic Locking Overview, Features and Benefits
    MIT, Configure /etc/krb5.conf, ADS Domains
    MIT kerberos, ADS Domains, IDMAP Storage in LDAP Using Winbind
    MIT Kerberos, Features and Benefits
    mixed mode, ADS Security Mode (User-Level Security), NT4-Style Domain Trusts with Windows 2000
    mixed profile, Mixed Windows Windows 9x/Me and NT4/200x User Profiles
    mkdir, Central Print Serving, Shadow Copy Setup
    mkfs.xfs, Shadow Copy Setup
    MMC, Features and Benefits, Features and Benefits, Domain Member Server or Domain Member Client, Primary Domain Controller, Access Controls on Shares, Windows 200x/XP, Creating and Managing System Policies, Windows NT4/200x, Disabling Roaming Profile Support
    MMC snap-in, Administration of Windows 200x/XP Policies
    modem/ISDN, Remote Management from NoMachine.Com
    moderately secure, Features and Benefits
    modprobe, Shadow Copy Setup
    module, Shadow Copy Setup
    modules, Features and Benefits, Discussion
    more than one protocol, Windows Networking Protocols
    mount, Share-Level Security, Shadow Copy Setup
    mouse-over, Remote Management from NoMachine.Com
    moveuser.exe, moveuser.exe
    MS DCE RPC, Join the Samba Server to the PDC Domain
    MS Windows 2000, Active Directory Domain Control
    MS Windows NT4/200x, New Account Storage Systems
    MS Windows SID, Domain Member Server or Domain Member Client
    MS WINS, Features and Benefits
    MS-DFS, MS-DFS: The Poor Man's Cluster
    MS-RPC, Printing Developments Since Samba-2.2
    MS-WINS replication, NetBIOS over TCP/IP
    msdfs links, Features and Benefits
    msg, Enabling SWAT Internationalization Support
    msg file, Enabling SWAT Internationalization Support
    MSRPC, Microsoft Remote Procedure Calls, Name Service Switch
    multibyte character sets, New Features in Samba-3.0.x
    multibyte charsets, What Are Charsets and Unicode?
    multiple backends, Password Backends
    multiple domains, Domain Layout
    multiple hosting, Advanced Configuration Techniques
    multiple modules, Discussion
    multiple network interfaces, Multiple Interfaces
    multiple network segments, Domain Layout
    multiple personality, Multiple Virtual Server Personalities
    multiple server hosting, Multiple Server Hosting
    multiple server personalities, Advanced Configuration Techniques
    multiple servers, Advanced Configuration Techniques, Multiple Server Hosting
    multiple universal naming convention provider (see MUP)
    multiple VFS, Discussion
    multiple virtual servers, Multiple Virtual Server Personalities
    multiple Windows workgroups or domains, MS Windows Me
    multiple WINS servers, NetBIOS over TCP/IP
    Multiuser databases, Multiuser Databases
    mutual assistance, Free Support
    mutually exclusive options, What Is Browsing?
    My Network Places, MS Windows Me, Problem Resolution
    Myrinet, Server Pool Communications Demands

    N

    n security context, How Browsing Functions
    n-memory buffer, The NetBIOS Name Cache
    name conflict, Any [my_printer_name] Section
    name lookup, Domain Controller Types, The NetBIOS Name Cache
    name lookups, NetBIOS over TCP/IP, How Browsing Functions
    name registration, What Qualifies a Domain Controller on the Network?
    name resolution, What Is Browsing?, NetBIOS over TCP/IP, How Browsing Functions, Technical Overview of Browsing, Common Errors, /etc/hosts, Assumptions
    name resolution across routed networks, How Browsing Functions
    name resolve order, Name Resolution Order
    name service switch (see NSS)
    name-to-address, WINS: The Windows Internetworking Name Server
    nameserv.h, Static WINS Entries
    name_type, WINS: The Windows Internetworking Name Server, Name Resolution Order
    native ACLs, Features and Benefits
    native dump, Amanda
    native member, Domain Controller Types, Features and Benefits
    native mode, ADS Security Mode (User-Level Security), Microsoft Active Directory Services
    NBT, Name Resolution as Used within MS Windows Networking
    nbtstat, Cannot Add Machine Back to Domain, The NetBIOS Name Cache
    necessary rights, Using the “net rpc rights” Utility
    negotiate, Important Notes About Security
    negotiating the charset, What Are Charsets and Unicode?
    nested group, Nested Groups: Adding Windows Domain Groups to Windows Local Groups
    Nested Group Support, What Rights and Privileges Will Permit Windows Client Administration?
    nested groups, Nested Groups: Adding Windows Domain Groups to Windows Local Groups
    net, Account Management Tools, Group Mapping: MS Windows and UNIX, Remote and Local Management: The Net Command, Overview, Administrative Tasks and Methods, UNIX and Windows Group Management, What Rights and Privileges Will Permit Windows Client Administration?
    ads, UNIX and Windows Group Management
    join, Joining an NT4-type Domain with Samba-3, Create the Computer Account, Machine Trust Accounts, ADS Domains
    leave, Machine Trust Accounts
    printer info, Printers and ADS
    printer publish, Printers and ADS
    printer remove, Printers and ADS
    printer search, Printers and ADS
    status, Machine Trust Accounts
    testjoin, Machine Trust Accounts
    getlocalsid, User and Group Changes, Managing Security Identifiers (SIDS), New Schema
    groupmap, Example: Engineering Office, User and Group Changes, Features and Benefits, Example Configuration, Steps in Migration Process
    add, Mapping Windows Groups to UNIX Groups
    delete, Mapping Windows Groups to UNIX Groups
    list, Example Configuration, Adding or Creating a New Group
    modify, Mapping Windows Groups to UNIX Groups
    localgroup, What Rights and Privileges Will Permit Windows Client Administration?
    rap, UNIX and Windows Group Management
    session, Session and Connection Management
    rpc, Example Configuration, Example Configuration, Features and Benefits, UNIX and Windows Group Management
    getsid, Backup Domain Controller Configuration, Managing Security Identifiers (SIDS)
    group, Nested Groups: Adding Windows Domain Groups to Windows Local Groups, Adding or Creating a New Group
    group add, Adding or Creating a New Group
    group addmem, Manipulating Group Memberships, Managing Nest Groups on Workstations from the Samba Server
    group delete, Deleting a Group Account
    group delmem, Manipulating Group Memberships
    group list, Adding or Creating a New Group
    group members, Manipulating Group Memberships
    group rename, Rename Group Accounts
    info, Other Miscellaneous Operations, Side Bar Notes
    join, Example Configuration, Joining an NT4-type Domain with Samba-3, Machine Trust Accounts, Join the Samba Server to the PDC Domain, Steps in Migration Process
    join bdc, Machine Trust Accounts
    join member, Machine Trust Accounts
    list, Using the “net rpc rights” Utility
    printer migrate drivers, Printer Migration
    printer migrate forms, Printer Migration
    printer migrate printers, Printer Migration
    printer migrate security, Printer Migration
    printer migrate settings, Printer Migration
    right list accounts, Share Migration
    rights grant, Administering User Rights and Privileges, Using the “net rpc rights” Utility
    rights list, Administering User Rights and Privileges
    rights list accounts, Administering User Rights and Privileges
    share add, Creating, Editing, and Removing Shares
    share delete, Creating, Editing, and Removing Shares
    share migrate, Share Migration
    share migrate all, Simultaneous Share and File Migration
    share migrate files, File and Directory Migration
    share migrate security, Share-ACL Migration
    testjoin, Machine Trust Accounts
    trustdom add, Interdomain Trusts
    trustdom establish, Interdomain Trusts, Samba as the Trusting Domain
    trustdom list, Interdomain Trusts
    trustdom revoke, Interdomain Trusts
    user add, Adding User Accounts
    user delete, Deletion of User Accounts, Machine Trust Accounts
    user info, Managing User Accounts
    user password, Adding User Accounts
    user rename, Managing User Accounts
    vampire, User and Group Changes, Share, Directory, and File Migration, Steps in Migration Process
    setlocalsid, Managing Security Identifiers (SIDS)
    time, Other Miscellaneous Operations
    set, Other Miscellaneous Operations
    system, Other Miscellaneous Operations
    zone, Other Miscellaneous Operations
    use, Testing Server Setup
    NET, Samba PDC
    net command, New Features in Samba-3.0.x
    net getlocalsid, The Administrator Domain SID
    net groupmap, New Schema
    net rpc user add, Description of Privileges
    net tool, Passdb Backends and Authentication
    net use, Error Message: “Cannot connect under a different Name”
    net use /home, Windows 9x/Me User Profiles
    net use lpt1:, Installing the PostScript Driver on a Client
    net view, The [global] Section, The Tests
    netatalk, netatalk
    NetAtalk, Basic Parameter Setting
    Netatalk, Macintosh Clients
    NetBEUI, Integrating MS Windows Networks with Samba
    NetBIOS, Domain Security Mode (User-Level Security), Features and Benefits, What Qualifies a Domain Controller on the Network?, How Does a Workstation find its Domain Controller?, Example Configuration, Features and Benefits, Discussion, TCP/IP without NetBIOS, Technical Overview of Browsing, Integrating MS Windows Networks with Samba, Name Resolution as Used within MS Windows Networking, The NetBIOS Name Cache
    brooadcast, Preparing for Domain Control
    name, Domain Security Mode (User-Level Security)
    netbios alias, Multiple Virtual Server Personalities
    netbios aliases, Multiple Virtual Server Personalities
    NetBIOS broadcast, Joining an NT4-type Domain with Samba-3
    NetBIOS disabled, Features and Benefits
    NetBIOS flags, Static WINS Entries
    NetBIOS name, Security Mode and Master Browsers, Manual Creation of Machine Trust Accounts, Joining an NT4-type Domain with Samba-3, Name Resolution as Used within MS Windows Networking, Multiple Virtual Server Personalities
    netbios name, Multiple Server Hosting
    NetBIOS name cache, Cannot Add Machine Back to Domain, Flushing the Samba NetBIOS Name Cache
    NetBIOS name length, WINS: The Windows Internetworking Name Server
    NetBIOS name resolution, Behavior of Cross-Subnet Browsing
    NetBIOS Name Server (see NBNS)
    NetBIOS name type, How Browsing Functions
    NetBIOS names, Name Resolution Order, /etc/nsswitch.conf
    NetBIOS network interface, Windows Networking Protocols
    NetBIOS networking, Features and Benefits
    NetBIOS over TCP/IP, Network Browsing, Features and Benefits, NetBIOS over TCP/IP, Technical Overview of Browsing, Cross-Subnet Browsing, Background Information
    NetBIOS over TCP/IP disabled, Browsing of Shares and Directories is Very Slow
    NetBIOS-less, TCP/IP without NetBIOS, Multiple Virtual Server Personalities
    NetBIOS-less SMB, Multiple Virtual Server Personalities
    NetBIOSless SMB over TCP/IP, NetBIOS over TCP/IP
    NetBT, Name Resolution as Used within MS Windows Networking
    netlogon, Domain Controller Types
    NETLOGON, Preparing for Domain Control, Domain Control: Example Configuration, Creating and Managing System Policies, MS Windows 200x/XP Professional Policies, Managing Account/User Policies, MS Windows NT4 Workstation, MS Windows 200x/XP
    Netlogon, Essential Background Information
    NetLogon service, WINS: The Windows Internetworking Name Server
    netlogon share, Backup Domain Controller Configuration, Steps in Migration Process
    Netmon, The Windows Network Monitor
    Netmon., Installing Network Monitor on an NT Workstation
    netmon.exe, Windows 9x/Me Profile Setup
    NetSAMLogon, Roaming Profiles
    Netscape's Directory Server, Supported LDAP Servers
    NetServerEnum2, Behavior of Cross-Subnet Browsing
    NetUserGetInfo, The Special Case of Windows 9x/Me, Roaming Profiles
    NetWare, Name Resolution as Used within MS Windows Networking
    NetWare Bindery, Features and Benefits
    NetWare Core Protocol-based server, Features and Benefits
    NetWkstaUserLogon, The Special Case of Windows 9x/Me
    network
    browsing, Features and Benefits
    logon, Domain Control: Example Configuration
    service, Security Mode and Master Browsers
    performance, Domain Controller Types
    wide-area, MS Windows NT4-style Domain Control
    network access controls, File, Directory, and Share Access Controls
    network access profile, MS Windows NT4-style Domain Control
    network administrator, File, Directory, and Share Access Controls
    network administrator's toolbox, Remote and Local Management: The Net Command
    network administrators, Server Share and Directory Layout
    network analyzer, Diagnostics Tools
    network bandwidth, Forcing Samba to Be the Master, Domain Layout
    Network Basic Extended User Interface (see NetBEUI)
    Network Basic Input/Output System (see NetBIOS)
    Network Bridge, MS Windows XP Professional
    Network Bridge Configuration, MS Windows XP Professional
    network browsing problems, Making Samba the Domain Master, Browsing of Shares and Directories is Very Slow
    network client, Features and Benefits, Identity Mapping (IDMAP)
    network clients, MS Windows 2000
    network configuration problems, TCP/IP Configuration
    network difficulty, Features and Benefits
    network environment, Remote Desktop Management
    Network ID, Joining a Domain: Windows 2000/XP Professional
    network interface, Using Interface Protection, The Tests
    network logon, The Special Case of Windows 9x/Me, Features and Benefits, Domain Logon Configuration: Windows 9x/Me
    network logon services, The Special Case of Windows 9x/Me
    network membership, Technical Details
    Network Monitor, The Windows Network Monitor
    Network Monitor Tools and Agent, Installing Network Monitor on an NT Workstation
    Network Neighborhood, What Is Browsing?, Problem Resolution, Behavior of Cross-Subnet Browsing, The [global] Section, Check Samba for Driver Recognition
    network neighborhood, Behavior of Cross-Subnet Browsing
    network policies, Creating and Managing System Policies
    network security, Domain Layout
    network segment, NetBIOS over TCP/IP, How Browsing Functions, Domain Layout
    Network settings, Cross-Subnet Browsing
    network sniffer, Advantages of Encrypted Passwords
    network storage, BackupPC
    network traffic, Domain Member Server or Domain Member Client
    networked workstation, Name Service Switch
    networking advocates, Discussion of Backup Solutions
    networking environment, Caution Regarding LDAP and Samba
    networking systems, Common Errors
    networks access, Samba Performance is Very Slow
    Networks Properties, Domain Logon Configuration: Windows 9x/Me
    new account, Samba as the Trusted Domain
    new parameters, New Parameters
    newsgroup, Introduction
    Nexus toolkit, MS Windows Workstation/Server Machine Trust Accounts
    Nexus.exe, Features and Benefits, Managing Domain Machine Accounts using NT4 Server Manager, Remote Server Administration
    NFS, Sharing User ID Mappings between Samba Domain Members, Mapping Common UIDs/GIDs on Distributed Machines, Remote Management with ThinLinc, The Distributed File System Challenge, Restrictive Constraints on Distributed File Systems, IdMap LDAP Support
    NFS clients, UNIX or NFS Client-Accessed Files
    NIS, Share-Level Security, Backup Domain Controller Configuration, Schema and Relationship to the RFC 2307 posixAccount, Domain Member Server or Domain Member Client, Name Service Switch
    NIS database, Pluggable Authentication Modules
    nmbd, Starting Samba, Test Your Config File with testparm, Secure Read-Write File and Print Server, Example Configuration, What Is Browsing?, NetBIOS over TCP/IP, Browsing Support in Samba, Flushing the Samba NetBIOS Name Cache, NT4-Style Domains (Includes Samba Domains), Testing Things Out, Linux, Solaris, Multiple Server Hosting, Multiple Virtual Server Personalities, The Tests, Debugging with Samba Itself, Corrupt tdb Files
    nmblookup, The NetBIOS Name Cache, The Tests
    No NetBIOS layer, TCP/IP without NetBIOS
    no network logon service, Background
    no printcap file, Central Print Serving
    nobody, Central Print Serving
    nobody account, Custom Print Commands, Multiple Virtual Server Personalities
    node-type, NetBIOS over TCP/IP
    NoMachine, Remote Management from NoMachine.Com
    NoMachine.Com, Remote Management from NoMachine.Com
    non-authentication-based account management, Anatomy of /etc/pam.d Entries
    non-authoritative, Behavior of Cross-Subnet Browsing
    non-LDAP
    backend, Features and Benefits
    non-member Windows client, Mapping User Identifiers between MS Windows and UNIX
    non-PostScript, CUPS Also Uses PPDs for Non-PostScript Printers, PostScript Printer Descriptions for Non-PostScript Printers
    non-PostScript printers, Prefilters, Foomatic Database-Generated PPDs
    nonhierarchical, Trust Relationship Background
    nontransitive, Trust Relationship Background
    normal color, The Role of cupsomatic/foomatic
    normal user, Administering User Rights and Privileges
    not domain member, Background
    not domain members, Standalone Servers
    not part of domain, WINS Server Configuration
    not stored anywhere, Advantages of Encrypted Passwords
    not transitive, NT4-Style Domain Trusts with Windows 2000
    Novell, Domain Member Server, Windows 9x/Me Profile Setup
    Novell eDirectory server, Features and Benefits
    NSS, Background, Mapping Common UIDs/GIDs on Distributed Machines, LDAP Directories and Windows Computer Accounts, ldapsam, Schema and Relationship to the RFC 2307 posixAccount, Accounts and Groups Management, Nested Groups: Adding Windows Domain Groups to Windows Local Groups, Identity Mapping (IDMAP), Domain Member Server or Domain Member Client, IDMAP_RID with Winbind, Features and Benefits, What Winbind Provides, How Winbind Works, Name Service Switch, Configure Winbind and PAM, Conclusion
    nsswitch.conf, Share-Level Security
    nss_ldap, Example Configuration, Mapping Common UIDs/GIDs on Distributed Machines, LDAP Directories and Windows Computer Accounts, Identity Mapping (IDMAP), Domain Member Server or Domain Member Client, IDMAP and NSS Using LDAP from ADS with RFC2307bis Schema Extension
    nss_winbind.so.1, Configure nsswitch.conf and the Winbind Libraries on Linux and Solaris
    NT domain, What Winbind Provides
    NT groups, Why Is This Better Than security = server?, Default Users, Groups, and Relative Identifiers
    NT migration scripts, ldapsam
    NT password, Listing User and Machine Accounts
    NT Server Manager, Windows NT4 Workstation/Server
    NT-controlled domain, Samba as the Trusting Domain
    NT-encrypted password, MS Windows Workstation/Server Machine Trust Accounts
    NT-encrypted passwords, Backward Compatibility Account Storage Systems
    NT4, Domain Member Server or Domain Member Client
    NT4 Domain, Standalone Samba Server
    NT4 domain, Domain Member Server or Domain Member Client, Features and Benefits
    NT4 domain members, Identity Mapping (IDMAP)
    NT4 style policy updates, Managing Account/User Policies
    NT4 User Manager for Domains, Using the “net rpc rights” Utility
    NT4-style, NT4-Style Domain Trusts with Windows 2000
    NT4-style domain, Interdomain Trust Relationships
    NT4-style domains, Trust Relationship Background
    Nt4sp6ai.exe, Windows NT4-Style Policy Files
    NTConfig.POL, Domain Control: Example Configuration, Features and Benefits, Windows 9x/ME Policies, Registry Spoiling, MS Windows 200x/XP Professional Policies, Administration of Windows 200x/XP Policies, Managing Account/User Policies, Samba Editreg Toolset, MS Windows NT4 Workstation, Samba-3 Implementation Choices
    ntconfig.pol, Windows NT4-Style Policy Files
    ntdrivers.tdb, Setting Device Modes on New Printers, The Printing *.tdb Files
    (see also TDB)
    ntforms.tdb, Setting Device Modes on New Printers, The Printing *.tdb Files
    (see also TDB)
    NTFS, User and Group Changes, MS Windows NTFS Comparison with UNIX File Systems
    NTLMv2, NTLMv2 Security
    ntlm_auth, Single Sign-On and Domain Security
    ntprinters.tdb, Setting Device Modes on New Printers, The Printing *.tdb Files
    (see also TDB)
    NTUser.DAT, Samba Editreg Toolset, Mandatory Profiles, Samba-3 Implementation Choices
    NTuser.DAT, Windows NT4 Workstation, Sharing Profiles between Windows 9x/Me and NT4/200x/XP Workstations, Profile Migration/Creation
    NTuser.MAN, Windows NT4 Workstation
    NTUser.MAN, Mandatory Profiles
    NT_STATUS_LOGON_FAILURE, Changes in Behavior
    NT_STATUS_UNSUCCESSFUL, Running rpcclient with adddriver
    null shell, Manual Creation of Machine Trust Accounts
    NX, Remote Management from NoMachine.Com

    O

    object class, New Schema
    object class declaration, New Schema
    object module dependencies, Configure nsswitch.conf and the Winbind Libraries on Linux and Solaris
    ObjectClass, Schema and Relationship to the RFC 2307 posixAccount
    ObjectClasses, Schema and Relationship to the RFC 2307 posixAccount, OpenLDAP Configuration
    obtuse complexity, Server Share and Directory Layout
    office server, Secure Read-Write File and Print Server
    OID, Schema and Relationship to the RFC 2307 posixAccount
    old sambaAccount, New Schema
    Omni, Driver Development Outside
    on the fly, Windows NT4 Client
    on-the-fly, Primary Domain Controller
    on-the-fly logon scripts, Objectives
    on-the-fly policy files, Objectives
    one direction, Trust Relationship Background
    one domain, Identity Mapping (IDMAP)
    one-way trust, Interdomain Trust Facilities
    only one WINS server, WINS Server Configuration
    OpenGFS, The Distributed File System Challenge
    OpenLDAP, Single Sign-On and Domain Security, LDAP Configuration Notes, Domain Member Server, LDAP Changes in Samba-3.0.23, New Account Storage Systems, Supported LDAP Servers, Schema and Relationship to the RFC 2307 posixAccount, OpenLDAP Configuration, Features and Benefits
    OpenLDAP backend, Backward Compatibility Account Storage Systems
    OpenSSL, Securing SWAT through SSL, Generating the Certificate Authority
    operating costs, Objectives
    operating system search path, Locating the SWAT File
    oplock, The Distributed File System Challenge
    oplock break, Opportunistic Locking Overview, Beware of Force User
    oplock handling, Restrictive Constraints on Distributed File Systems
    oplock mechanism, Advanced Samba Oplocks Parameters
    oplock messages, Required Modifications to Samba
    oplock parameters, Advanced Samba Oplocks Parameters
    oplocks, Opportunistic Locking Overview
    oplocks disabled, Multiuser Databases
    oplocks management, PDM Data Shares
    opportunistic locking, Features and Benefits, Opportunistic Locking Overview
    Opportunistic locking, Opportunistic Locking Overview
    optional, Anatomy of /etc/pam.d Entries
    ordinary connection, Samba as the Trusting Domain
    Organization for the Advancement of Structured Information Standards (see OASIS)
    organizational directory, Create the Computer Account
    organizational unit, Create the Computer Account (see OU)
    os level, Domain Control: Example Configuration
    OSS/Free Software, Remote Management from NoMachine.Com
    other, File and Directory Access Control
    output duplexing, pstops
    outside threat, Using Host-Based Protection
    own home directory, Why Can Users Access Other Users' Home Directories?
    ownership, Viewing File Ownership
    ownership cost, Objectives
    ownership rights, Windows 9x/Me Profile Setup

    P

    p-node, NetBIOS over TCP/IP
    package, Example Configuration
    packages, Obtaining and Installing Samba
    packet sniffer, Windows 9x/Me Profile Setup
    packet trace, Windows 9x/Me Profile Setup
    PADL, Mapping Common UIDs/GIDs on Distributed Machines, LDAP Directories and Windows Computer Accounts, Domain Member Server or Domain Member Client, IDMAP Storage in LDAP Using Winbind
    PADL Software, Mapping Common UIDs/GIDs on Distributed Machines
    page description languages (see PDL)
    pager program, Simple Print Configuration
    page_log, The page_log File Syntax
    paid-for support, Samba Support
    PAM, Background, Backward Compatibility Account Storage Systems, Mapping Common UIDs/GIDs on Distributed Machines, Plaintext, ldapsam, How Winbind Works, Pluggable Authentication Modules, Requirements, Testing Things Out, Configure nsswitch.conf and the Winbind Libraries on Linux and Solaris, Configure Winbind and PAM, Conclusion, Features and Benefits, Technical Discussion
    PAM authentication module, PAM Configuration Syntax
    PAM configuration, Requirements
    PAM management, PAM-Based Distributed Authentication
    PAM module, NSS Winbind on AIX
    PAM modules, Features and Benefits
    PAM-capable, Features and Benefits
    pam-devel, Configure nsswitch.conf and the Winbind Libraries on Linux and Solaris
    PAM-enabled, What Winbind Provides, PAM-Based Distributed Authentication, Features and Benefits
    PAM-specific tokens, PAM Configuration Syntax
    pam_krb5.so, Features and Benefits
    pam_ldap, Mapping Common UIDs/GIDs on Distributed Machines
    pam_ldap.so, Features and Benefits
    pam_mkhomedir, Linux/FreeBSD-Specific PAM Configuration
    pam_ncp_auth.so, Features and Benefits
    pam_pwdb.so, Features and Benefits
    pam_securetty.so, Linux/FreeBSD-Specific PAM Configuration
    pam_smbpass.so, PAM-Based Distributed Authentication, Features and Benefits
    pam_smbpasswd.so, Features and Benefits
    pam_smb_auth.so, Features and Benefits
    pam_unix.so, Linux/FreeBSD-Specific PAM Configuration, Features and Benefits
    pam_unix2.so, Features and Benefits
    pam_userdb.so, Features and Benefits
    pam_winbind.so, Pluggable Authentication Modules, Configure Winbind and PAM, Linux/FreeBSD-Specific PAM Configuration, Features and Benefits
    parameters, Rapid Configuration Validation
    paranoid, Starting and Testing the winbindd Daemon
    passdb, Machine Accounts Keep Expiring
    passdb backend, Domain Control: Example Configuration, Group Mapping Changes in Samba-3.0.23, Account Information Databases, Comments Regarding LDAP, The smbpasswd Tool, The pdbedit Tool, Deleting Accounts, tdbsam, Default Users, Groups, and Relative Identifiers, Domain Member Server or Domain Member Client, Primary Domain Controller, The Administrator Domain SID, Interdomain Trust Relationships, Features and Benefits, New Suffix for Searching
    passdb backends, smbpasswd: Encrypted Password Database, New Features in Samba-3.0.x
    passed across the network, Advantages of Encrypted Passwords
    passwd, Central Print Serving, LDAP Directories and Windows Computer Accounts, The smbpasswd Tool, Name Service Switch, Features and Benefits
    password, MS Windows NT4-style Domain Control, Samba as the Trusted Domain, Samba as the Trusting Domain, Anatomy of /etc/pam.d Entries
    plaintext, The Special Case of Windows 9x/Me
    password aging, Account Management Tools
    password assigned, Completing an NT4 Domain Trust
    password backend, Reference Documentation Server, Listing User and Machine Accounts
    password backends, Account Information Databases
    password change facility, Enabling SWAT for Use
    password database, Backup Domain Controller Configuration, Samba as the Trusted Domain
    password encryption, Plaintext
    password expiration, smbpasswd: Encrypted Password Database
    password expired, Changing User Accounts
    password history, Single Sign-On and Domain Security
    password management, Pluggable Authentication Modules
    password prompt, Advantages of Encrypted Passwords
    password scheme, Important Notes About Security
    password server, Server Security (User Level Security), Configure smb.conf
    password uniqueness, Single Sign-On and Domain Security
    passwords, Introduction
    patch, Patches
    path specified, Adding Machine to Domain Fails
    pauses, Samba Performance is Very Slow
    PBM, MIME Types and CUPS Filters
    PCL, GDI on Windows, PostScript on UNIX, Windows Drivers, GDI, and EMF, UNIX Printfile Conversion and GUI Basics, Printing with Interface Scripts, Driver Execution on the Server, Network PostScript RIP
    pdbedit, Example: Engineering Office, Account Management Tools, The pdbedit Tool, User Account Management, Listing User and Machine Accounts, Adding User Accounts, Deleting Accounts, Changing User Accounts, Account Flags Management, Account Import/Export, The Administrator Domain SID, Samba PDC, Quick Migration Guide, Passdb Backends and Authentication, Steps in Migration Process, Samba-3 Implementation Choices
    pdb_ldap, Can I Do This All with LDAP?
    PDC, Domain Security Mode (User-Level Security), Example Configuration, Domain Controller Types, Security Mode and Master Browsers, Features and Benefits, MS Windows NT4-style Domain Control, Example PDC Configuration, LDAP Configuration Notes, What Qualifies a Domain Controller on the Network?, Backup Domain Controller Configuration, Example Configuration, Can Samba Be a Backup Domain Controller to an NT4 PDC?, MS Windows Workstation/Server Machine Trust Accounts, Manual Creation of Machine Trust Accounts, Joining an NT4-type Domain with Samba-3, Why Is This Better Than security = server?, Adding Machine to Domain Fails, Configuring Workgroup Browsing, Domain Browsing Configuration, New Account Storage Systems, Advantages of Encrypted Passwords, tdbsam, LDAP Special Attributes for sambaSamAccounts, Discussion, Overview, Domain Member Server or Domain Member Client, Primary Domain Controller, Samba as the Trusted Domain, Samba as the Trusting Domain, cupsaddsmb with a Samba PDC, Handling of Foreign SIDs, Microsoft Remote Procedure Calls, Pluggable Authentication Modules, Result Caching, Introduction, Join the Samba Server to the PDC Domain, Starting and Testing the winbindd Daemon, Remote Management from NoMachine.Com, New Schema, Domain Layout, Getting Mailing List Help, Corrupt tdb Files
    PDF, Simple smb.conf Settings for CUPS, Windows Drivers, GDI, and EMF, PostScript Printer Description (PPD) Specification, MIME Types and CUPS Filters, Prefilters, Examples for Filtering Chains
    pdf, MIME Type Conversion Rules
    PDF distilling, PostScript Printer Description (PPD) Specification
    PDF filter, Central Print Serving
    pdftops, MIME Type Conversion Rules, Examples for Filtering Chains
    pdftosocket, Examples for Filtering Chains
    PDL, GDI on Windows, PostScript on UNIX, PostScript and Ghostscript, PostScript Printer Description (PPD) Specification
    PDM, PDM Data Shares
    peer domain, Configuring Samba NT-Style Domain Trusts
    Peer node, Static WINS Entries
    per-share access control, Access Controls on Shares
    performance, Handling Large Directories, Objectives
    performance advantage, Features and Benefits
    performance degradation, Handling Large Directories
    performance enhancement, Opportunistic Locking Overview
    performance improvement, Slow and/or Unreliable Networks
    performance-based, tdbsam
    performed as root, Using the “net rpc rights” Utility
    perimeter firewall, Features and Benefits
    permanent changes, Samba-3 Implementation Choices
    Permanent name, Static WINS Entries
    permissions, Why Can Users Access Other Users' Home Directories?, Shadow Copy Setup
    file/directory ACLs, Managing UNIX Permissions Using NT Security Dialogs
    share, Share Definition Access Controls
    share ACLs, Access Controls on Shares
    UNIX file and directory, Features and Benefits
    Permissions, Windows 200x/XP
    permissions and controls, Features and Benefits
    PGP, Verifying Samba's PGP Signature
    phasing out NetBIOS, Discussion
    Photo-CD, MIME Types and CUPS Filters
    physical locations, Features and Benefits
    physical network transport layer, /etc/hosts
    PID, Attaching to a Running Process
    pid directory, Multiple Server Hosting
    ping, Domain Layout, The Tests
    pipe device, File and Directory Access Control
    PJL, Network PostScript RIP, Windows CUPS PostScript Driver Versus Adobe Driver, Adobe and CUPS PostScript Drivers for Windows Clients
    PJL-header, Adobe and CUPS PostScript Drivers for Windows Clients
    plague network users, TCP/IP Configuration
    plain-text
    passwords, Password Checking
    plaintext, Backward Compatibility Account Storage Systems
    plaintext authentication, Backward Compatibility Account Storage Systems
    plaintext password, The Special Case of Windows 9x/Me, How Do I Replicate the smbpasswd File?
    plaintext passwords, Technical Information, Important Notes About Security
    platforms, Portability
    PLP, The [global] Section
    Pluggable Authentication Modules (see PAM)
    PNG, Ghostscript: The Software RIP for Non-PostScript Printers, MIME Types and CUPS Filters
    PNM, MIME Types and CUPS Filters
    point 'n' print, Installation of Windows Client Drivers, Run cupsaddsmb (Quiet Mode), Manual Driver Installation in 15 Steps
    Point'n'Print, Features and Benefits, Printing Developments Since Samba-2.2, Point'n'Print Client Drivers on Samba Servers, smbclient to Confirm Driver Installation
    point'n'print, Driver Upload Methods, The Role of cupsomatic/foomatic, Installing the PostScript Driver on a Client
    Poledit, Administration of Windows 200x/XP Policies
    poledit.exe, Creating and Managing System Policies, Windows NT4-Style Policy Files, Administration of Windows 200x/XP Policies
    Policies, Creating and Managing System Policies, Managing Account/User Policies
    policies, Samba-3 Implementation Choices
    policy editor, Creating and Managing System Policies
    Policy Editor, Windows NT4-Style Policy Files
    policy file , Managing Account/User Policies
    policy files, Features and Benefits
    policy settings, The pdbedit Tool
    port 135, Multiple Interfaces
    Port 135/TCP, Using a Firewall
    port 137, Multiple Interfaces, The Tests
    Port 137/UDP, Using a Firewall
    port 138, Multiple Interfaces
    Port 138/UDP, Using a Firewall
    port 139, Multiple Interfaces
    Port 139/TCP, Using a Firewall
    port 445, Multiple Interfaces
    Port 445/TCP, Using a Firewall
    ports, Verifying Configuration with testparm, Ethereal
    POSIX, Backup Domain Controller Configuration, LDAP Directories and Windows Computer Accounts, Accounts and Groups Management, Adding or Creating a New Group
    POSIX account, User Account Management, UNIX and Windows User Management
    POSIX ACLs, File and Directory Access Control, Protecting Directories and Files from Deletion
    POSIX ACLS, Samba-3 Implementation Choices
    POSIX identity, Caution Regarding LDAP and Samba
    POSIX locks, Server Pool Communications
    POSIX semantics, Server Pool Communications
    POSIX user accounts, Interdomain Trust Relationships
    posixAccount, Schema and Relationship to the RFC 2307 posixAccount, OpenLDAP Configuration
    posixGroup, OpenLDAP Configuration, Accounts and Groups Management
    PostScript, Simple smb.conf Settings for CUPS, Advanced Intelligent Printing with PostScript Driver Download, GDI on Windows, PostScript on UNIX, Windows Drivers, GDI, and EMF, UNIX Printfile Conversion and GUI Basics, PostScript and Ghostscript, PostScript Printer Description (PPD) Specification, Using Windows-Formatted Vendor PPDs, MIME Types and CUPS Filters, Prefilters, pstops, PostScript Printer Descriptions for Non-PostScript Printers, Examples for Filtering Chains, Driver Execution on the Server, Network PostScript RIP, CUPS: A “Magical Stone”?, PostScript Drivers with No Major Problems, Even in Kernel +Mode, CUPS “PostScript Driver for Windows NT/200x/XP”
    (see also Ghostscript)
    RIP, PostScript and Ghostscript
    PostScript driver, Installing Driver Files into [print$]
    PostScript interpreter, PostScript and Ghostscript
    PostScript Printer Description (see PPD)
    PostScript printers, Printing from CUPS to Windows-Attached Printers
    potential master browsers, Forcing Samba to Be the Master
    potential printer, [print$] Stanza Parameters
    Power Users, What Rights and Privileges Will Permit Windows Client Administration?
    powerful, Domain Controller Types
    PPD, Installing Driver Files into [print$], PostScript and Ghostscript, PostScript Printer Description (PPD) Specification, CUPS Also Uses PPDs for Non-PostScript Printers, MIME Types and CUPS Filters, “Raw” Printing, PostScript Printer Descriptions for Non-PostScript Printers, PPDs for Non-PS Printers on UNIX, PPDs for Non-PS Printers on Windows, CUPS: A “Magical Stone”?, Installing the PostScript Driver on a Client, Adobe and CUPS PostScript Drivers for Windows Clients, Printing from CUPS to Windows-Attached Printers
    CUPS (see CUPS-PPD)
    PPD-aware, PostScript and Ghostscript
    PPDs, Using Windows-Formatted Vendor PPDs, The Role of cupsomatic/foomatic, The Grand Unification Achieved
    PPP, Using Interface Protection
    precedence, Forcing Samba to Be the Master
    preferred master, Domain Control: Example Configuration
    prefilter, imagetops and imagetoraster
    prefilters, Prefilters
    primary domain controller, Multiple Virtual Server Hosting
    primary group, Manual Creation of Machine Trust Accounts
    Primary Logon, Windows 9x/Me Profile Setup
    Primary WINS Server, WINS Server Configuration
    print, Verifying Configuration with testparm
    queue, Configuration File Syntax
    spooler, Configuration File Syntax
    print accounting, Features and Benefits
    print command, Print Commands
    print commands, Custom Print Commands
    print configuration, Technical Introduction, Verifying Configuration with testparm
    print environment, Simple Print Configuration
    print filtering, Technical Introduction
    print job, Custom Print Commands
    print jobs, The [global] Section
    print processing, Technical Introduction
    print queue, Point'n'Print Client Drivers on Samba Servers, smbclient to Confirm Driver Installation, Specific Driver Name Flexibility, CUPS Backends
    print quota, Advanced Intelligent Printing with PostScript Driver Download
    print server, Central Print Serving, Features and Benefits
    print service, Features and Benefits
    print spooling, Microsoft Remote Procedure Calls
    print spooling system, Overview
    print statistics, Advanced Intelligent Printing with PostScript Driver Download
    print subsystem, Technical Introduction, Print Commands
    print test page, First Client Driver Installation
    printcap, Configuration File Syntax, The [global] Section, The [printers] Section
    Printcap, Basic CUPS Support Configuration
    printcap name, Central Print Serving
    PrintcapFormat, Basic CUPS Support Configuration
    printer attributes publishing, New Features in Samba-3.0.x
    printer default permissions, Printing Developments Since Samba-2.2
    printer driver, The Obsoleted [printer$] Section, Creating the [print$] Share, Simple smb.conf Settings for CUPS
    printer driver data, Setting Device Modes on New Printers
    printer driver file, The Obsoleted [printer$] Section
    printer driver files, smbclient to Confirm Driver Installation
    printer drivers, Point'n'Print Client Drivers on Samba Servers, The Grand Unification Achieved
    printer icon, Check Samba for Driver Recognition
    printer management, Overview
    printer management system, Overview
    printer migration, Overview
    printer monitor, Samba Performance is Very Slow
    printer objects, Printing Developments Since Samba-2.2
    Printer Pooling, Samba and Printer Ports
    printer queue, Printing Developments Since Samba-2.2
    printer share, The [global] Section
    printer shares , Verifying Configuration with testparm, The [global] Section
    printer$ share, The Obsoleted [printer$] Section
    printers, Configuration File Syntax, Features and Benefits
    Printers, The [global] Section
    printers admin, Description of Privileges
    Printers and Faxes, Check Samba for Driver Recognition
    printers available, What Is Browsing?
    printers section, The [printers] Section
    printing, The [global] Section
    printing behavior, Printing-Related Configuration Parameters
    printing calls, Printing Developments Since Samba-2.2
    printing now, Samba Performance is Very Slow
    printing support, Features and Benefits, Technical Introduction
    printing system, Technical Introduction
    printing systems, Comments Regarding LDAP
    printing-related settings, Verifying Configuration with testparm
    printing.tdb, Setting Device Modes on New Printers, The Printing *.tdb Files
    (see also TDB)
    PrintPro (see ESP Print Pro)
    private dir, Multiple Server Hosting
    private groups, Warning: User Private Group Problems
    private key, Securing SWAT through SSL
    private network, Introduction
    private networks, Using Host-Based Protection
    private/MACHINE.SID, Backup Domain Controller Configuration
    private/secrets.tdb, Backup Domain Controller Configuration
    privilege, Applicable Only to Versions Earlier than 3.0.11, Description of Privileges
    privilege management, Important Administrative Information, Administering User Rights and Privileges
    privilege model, Rights Management Capabilities
    privilege-granting applications, Technical Discussion
    privileged accounts, Using the “net rpc rights” Utility
    privileges, Single Sign-On and Domain Security, Windows 200x/XP Professional Client, Applicable Only to Versions Earlier than 3.0.11, Rights Management Capabilities, Description of Privileges, Trust Relationship Background, Printing Developments Since Samba-2.2
    privileges assigned, Using the “net rpc rights” Utility
    problem report, Free Support
    problem resolution, Samba Support
    problematic print, Technical Introduction
    Process data management, PDM Data Shares
    professional support, Free Support
    profile, Domain Control: Example Configuration, The Special Case of Windows 9x/Me, MS Windows NT4-style Domain Control, New Account Storage Systems, Technical Information
    profile access rights, Creating and Managing Group Profiles
    profile contents, Sharing Profiles between Windows 9x/Me and NT4/200x/XP Workstations
    profile directory, Windows 9x/Me Profile Setup
    profile migration tool, Creating and Managing Group Profiles
    profile path, Example PDC Configuration, Windows 9x/Me Profile Setup, Windows NT4 Workstation
    profile sharing, Sharing Profiles between Windows 9x/Me and NT4/200x/XP Workstations
    Profile Type, Disabling Roaming Profile Support
    ProfilePath, Windows 9x/Me Profile Setup
    profiles, The Special Case of Windows 9x/Me
    Profiles, Creating and Managing System Policies
    project, Free Support
    promiscuous mode, The Windows Network Monitor
    promote, Domain Controller Types
    promoted, MS Windows NT4-style Domain Control
    propagate, Features and Benefits
    Properties, MS Windows Me, Domain Logon Configuration: Windows 9x/Me
    protect directories, Protecting Directories and Files from Deletion
    protect files, Protecting Directories and Files from Deletion
    protection against attackers, Using IPC$ Share-Based Denials
    protocol stack settings, MS Windows 2000
    provided services, Samba Support
    provisioned, Single Sign-On and Domain Security
    pstops, Prefilters, pstops, Examples for Filtering Chains, Adobe and CUPS PostScript Drivers for Windows Clients
    pstoraster, pstoraster, cupsomatic/foomatic-rip Versus Native CUPS Printing, Adobe and CUPS PostScript Drivers for Windows Clients
    publish printers, Printing Developments Since Samba-2.2
    publishing printers, Rapid Configuration Validation
    PulseAudio, Remote Management with ThinLinc
    punching, pstops
    purchase support, Free Support
    put, The Tests
    pvcreate, Shadow Copy Setup

    Q

    QNX, The [global] Section
    qualified problem, Free Support
    queue control, The [global] Section
    quota controls, Comments Regarding LDAP

    R

    RAID, BackupPC
    random machine account password, Joining an NT4-type Domain with Samba-3
    range, UNIX and Windows User Management
    range of hosts, Using Host-Based Protection
    RAP, UNIX and Windows Group Management
    raster, Prefilters, Foomatic Database-Generated PPDs
    raster driver, The CUPS Filtering Architecture
    raster drivers, pstoraster
    raster image processor (see RIP)
    raster images, UNIX Printfile Conversion and GUI Basics
    rasterization, pstoraster, cupsomatic/foomatic-rip Versus Native CUPS Printing
    rastertoalps, rasterto [printers specific]
    rastertobj, rasterto [printers specific]
    rastertoepson, rasterto [printers specific], Examples for Filtering Chains
    rastertoescp, rasterto [printers specific]
    rastertohp, rasterto [printers specific]
    rastertopcl, rasterto [printers specific]
    rastertoprinter, rasterto [printers specific]
    rastertosomething, cupsomatic/foomatic-rip Versus Native CUPS Printing
    rastertoturboprint, rasterto [printers specific]
    raw mode, application/octet-stream Printing
    raw print, cupsaddsmb Flowchart
    raw printers, Overview
    raw printing, Anonymous Print Server, Central Print Serving, Raw Print Serving: Vendor Drivers on Windows Clients, Explicitly Enable “raw” Printing for application/octet-stream
    raw SMB, Features and Benefits
    raw SMB over TCP/IP, TCP/IP without NetBIOS
    rawprinter, “Raw” Printing
    rcp, Rsync
    rdesktop, Remote Management from NoMachine.Com
    rdesktop/RDP, Remote Management from NoMachine.Com
    read, File and Directory Access Control
    read directory into memory, Handling Large Directories
    read only, fake_perms
    server, Anonymous Read-Only Document Server
    Read-ahead, Opportunistic Locking Overview
    read-only, Features and Benefits, Reference Documentation Server
    read-only access, Backup Domain Controller, Multiple Virtual Server Personalities
    read-only files, Features and Benefits
    read-write access, The Obsoleted [printer$] Section
    realm, ADS Security Mode (User-Level Security), NetBIOS Over TCP/IP Disabled, Configure smb.conf, Configure /etc/krb5.conf, IDMAP_RID with Winbind, IDMAP Storage in LDAP Using Winbind
    rebooted, Joining a Domain: Windows 2000/XP Professional, Configuring Workgroup Browsing
    rebooting server, Description of Privileges
    recompiling, Multiple Server Hosting
    reconfiguration, MS Windows NT4-style Domain Control
    record locking, Discussion
    recycle, recycle
    recycle bin, Discussion
    recycle directory, recycle
    recycle:exclude, recycle
    recycle:exclude_dir, recycle
    recycle:keeptree, recycle
    recycle:maxsize, recycle
    recycle:noversions, recycle
    recycle:repository, recycle
    recycle:subdir_mode, recycle
    recycle:touch, recycle
    recycle:versions, recycle
    Red Hat Cluster Manager, High-Availability Server Products
    Red Hat Linux, LDAP Configuration Notes, On-the-Fly Creation of Machine Trust Accounts, Warning: User Private Group Problems
    redirect, Example Configuration
    redirection, What Winbind Provides
    redirector, Opportunistic Locking Overview
    redundancy, NetBIOS over TCP/IP
    reference documents, Reference Documentation Server
    refusing connection, Using Interface Protection
    regedit.exe, MS Windows 9x/Me
    regedt32, MS Windows NT4 Workstation
    regedt32.exe, Windows NT4/200x
    register driver files, Running rpcclient with adddriver
    register NetBIOS names, How Browsing Functions
    registered, WINS: The Windows Internetworking Name Server, Check Samba for Driver Recognition
    registers, Domain Browsing Configuration
    registry, Domain Controller Types, Technical Information, Features and Benefits, Creating and Managing System Policies, Windows 9x/ME Policies, MS Windows 200x/XP Professional Policies, MS Windows 9x/Me
    registry change, Important Notes About Security
    registry keys, Default Profile for Windows Users
    registry settings, Managing Account/User Policies
    regulations, The pdbedit Tool
    rejoin, Managing Security Identifiers (SIDS)
    relationship password, Samba as the Trusted Domain
    relative identifier, smbpasswd: Encrypted Password Database (see RID)
    Relative Identifier (see RID)
    Relative Identifiers (see RID)
    reliability, Features and Benefits, Objectives
    Remote Access Dial-In User Service (see RADIUS)
    remote announce, Cross-Subnet Browsing
    remote browse sync, Cross-Subnet Browsing
    remote desktop capabilities, Remote Management from NoMachine.Com
    remote desktop management, Remote Desktop Management
    remote domain, Creating an NT4 Domain Trust, Completing an NT4 Domain Trust, Samba as the Trusted Domain
    remote login, Remote Management from NoMachine.Com
    remote management, Remote and Local Management: The Net Command, Microsoft Remote Procedure Calls
    Remote Procedure Call (see RPC)
    Remote Procedure Call System Service (see RPCSS)
    remote profile, Windows 9x/Me Profile Setup
    remote segment, Use of the Remote Browse Sync Parameter, Domain Layout
    Remote X, Remote Management from NoMachine.Com
    Remote X protocol, Remote Management from NoMachine.Com
    remote-update protocol, Rsync
    rename, Managing Directories
    render, Raw Print Serving: Vendor Drivers on Windows Clients
    rendering, cupsomatic/foomatic-rip Versus Native CUPS Printing
    repeated intervals, NetBIOS over TCP/IP
    replicate, Backup Domain Controller Configuration, smbpasswd: Encrypted Password Database
    replicated, Features and Benefits, Features and Benefits, Active Directory Domain Control, Backup Domain Controller Configuration, MS Windows 200x/XP Professional Policies
    replicated SYSVOL, MS Windows 200x/XP Professional Policies
    replication, Features and Benefits, LDAP Configuration Notes
    browse lists, Cross-Subnet Browsing
    SAM, Domain Controller Types, Features and Benefits, MS Windows NT4-style Domain Control, Backup Domain Controller Configuration, Can Samba Be a Backup Domain Controller to an NT4 PDC?, How Do I Replicate the smbpasswd File?
    WINS, NetBIOS over TCP/IP, WINS Server Configuration, WINS Replication
    replication protocols, WINS Server Configuration
    repository, Domain Member Server or Domain Member Client
    requesting payment, Free Support
    required, Anatomy of /etc/pam.d Entries
    requisite, Anatomy of /etc/pam.d Entries
    research, Discussion of Backup Solutions
    resizing, Shadow Copy Setup
    resolution, The Role of cupsomatic/foomatic
    resolution of NetBIOS names, Network Browsing
    resolve NetBIOS names, Making Samba the Domain Master
    resolver functions, Name Service Switch
    resource failover, High-Availability Server Products
    resource kit, Administration of Windows 200x/XP Policies, Windows NT4 Profile Management Tools
    resource-based exclusion, Features and Benefits
    response, IDMAP_RID with Winbind
    restore, Features and Benefits
    restrict DNS, Name Resolution Order
    reviewers, Advanced Configuration Techniques
    revoke privileges, Using the “net rpc rights” Utility
    RFC 1001, Example Configuration
    RFC 1002, Example Configuration
    RFC 1179, The [global] Section
    RFC 2307, Mapping Common UIDs/GIDs on Distributed Machines
    RFC 2307., Schema and Relationship to the RFC 2307 posixAccount
    RFC 2830, Introduction
    rfc2307bis, IDMAP and NSS Using LDAP from ADS with RFC2307bis Schema Extension
    RFC2830, LDAP Configuration Notes
    RFCs, Analyzing and Solving Samba Problems
    rich database backend, New Account Storage Systems
    rich directory backend, New Account Storage Systems
    RID, Features and Benefits, Manual Creation of Machine Trust Accounts, User and Group Changes, Discussion, Default Users, Groups, and Relative Identifiers, Domain Member Server or Domain Member Client, Primary Domain Controller, IDMAP_RID with Winbind, The Administrator Domain SID, User and Group ID Allocation, New Schema
    RID 500, The Administrator Domain SID
    RID base, Primary Domain Controller
    right to join domain, Description of Privileges
    rights, Single Sign-On and Domain Security, The Special Case of Windows 9x/Me, Possible Errors, Rights Management Capabilities
    rights and privilege, Administering User Rights and Privileges
    rights and privileges, Important Administrative Information, The Administrator Domain SID
    rights assigned, Rights Management Capabilities, Using the “net rpc rights” Utility
    RIP, PostScript Printer Descriptions for Non-PostScript Printers
    rlogind, Anatomy of /etc/pam.d Entries
    Roaming Profile, fake_perms
    roaming profiles, Preparing for Domain Control, Features and Benefits, Disabling Roaming Profile Support, Windows 9x/Me Profile Setup
    rogue machine, Flushing the Samba NetBIOS Name Cache
    rogue user, MS Windows Workstation/Server Machine Trust Accounts
    root, Windows 200x/XP Professional Client, Joining a Domain: Windows 2000/XP Professional, User Rights and Privileges
    root account, User Rights and Privileges, The Administrator Domain SID
    root user, Using the “net rpc rights” Utility
    rotate, UNIX Printfile Conversion and GUI Basics
    RPC, Why Is This Better Than security = server?, Features and Benefits, Join the Samba Server to the PDC Domain, Roaming Profiles
    RPC calls, Conclusion, The Front-End Challenge
    RPC modules, New Features in Samba-3.0.x
    rpc.lockd, Discussion
    rpcclient, Remote and Local Management: The Net Command, Identifying Driver Files, Specific Driver Name Flexibility, Troubleshooting Revisited, Samba PDC
    adddriver, Run cupsaddsmb with Verbose Output, Understanding cupsaddsmb, Installing PostScript Driver Files Manually Using rpcclient, Understanding the rpcclient man Page, Requirements for adddriver and setdriver to Succeed, Manual Driver Installation in 15 Steps
    enumdrivers, Installing PostScript Driver Files Manually Using rpcclient, Manual Driver Installation in 15 Steps
    enumports, Installing PostScript Driver Files Manually Using rpcclient
    enumprinters, Installing PostScript Driver Files Manually Using rpcclient, Requirements for adddriver and setdriver to Succeed, Manual Driver Installation in 15 Steps, Troubleshooting Revisited
    getdriver, Producing an Example by Querying a Windows Box, Manual Driver Installation in 15 Steps
    getprinter, Producing an Example by Querying a Windows Box, Manual Driver Installation in 15 Steps, Troubleshooting Revisited
    setdriver, Caveats to Be Considered, Run cupsaddsmb with Verbose Output, Understanding cupsaddsmb, Installing PostScript Driver Files Manually Using rpcclient, Requirements for adddriver and setdriver to Succeed, Manual Driver Installation in 15 Steps
    rsh, BackupPC
    rsync, Backup Domain Controller Configuration, How Do I Replicate the smbpasswd File?, Mapping Common UIDs/GIDs on Distributed Machines, smbpasswd: Encrypted Password Database, BackupPC, Rsync, Accessing the Samba Sources via rsync and ftp
    rsyncd, BackupPC
    runas, Always Make First Client Connection as root or “printer admin”
    rundll32, Additional Client Driver Installation, Setting Default Print Options for Client Drivers, Manual Driver Installation in 15 Steps, Adding Printers without User Intervention

    S

    SAM, Features and Benefits, Domain Controller Types, MS Windows NT4-style Domain Control, Machine Accounts Keep Expiring, Can Samba Be a Backup Domain Controller to an NT4 PDC?, How Do I Replicate the smbpasswd File?, Features and Benefits, User and Group Changes, Backward Compatibility Account Storage Systems, Mapping User Identifiers between MS Windows and UNIX, Result Caching
    delta file, MS Windows NT4-style Domain Control
    replication, Domain Controller Types, MS Windows NT4-style Domain Control
    SAM backend, Mapping Common UIDs/GIDs on Distributed Machines, Comments Regarding LDAP
    LDAP, Features and Benefits
    ldapsam, Features and Benefits, New Account Storage Systems, Mapping Common UIDs/GIDs on Distributed Machines, ldapsam
    ldapsam_compat, Features and Benefits
    non-LDAP, Features and Benefits
    smbpasswd, Features and Benefits, smbpasswd: Encrypted Password Database
    tdbsam, Features and Benefits, New Account Storage Systems, tdbsam
    Samba 1.9.17, WINS Server Configuration
    Samba account, Manual Creation of Machine Trust Accounts
    Samba administrator, Introduction
    Samba backend database, Adding Machine to Domain Fails
    Samba daemons, Joining an NT4-type Domain with Samba-3
    Samba differences, Upgrading from Samba-2.x to Samba-3.0.25
    Samba mailing lists, Features and Benefits
    Samba private directory, Create the Computer Account
    Samba SAM, Mapping User Identifiers between MS Windows and UNIX
    Samba SAM account, Adding Machine to Domain Fails
    Samba SAM account flags, Account Flags Management
    Samba schema, New Account Storage Systems
    Samba security, Features and Benefits
    Samba-2.2.x LDAP schema, Backward Compatibility Account Storage Systems
    Samba-3-compatible LDAP backend, Quick Migration Guide
    Samba-PDC-LDAP-HOWTO, ldapsam
    samba-to-samba trusts, Interdomain Trust Relationships
    samba-vscan, vscan
    samba.schema, Schema and Relationship to the RFC 2307 posixAccount, OpenLDAP Configuration, New Schema
    sambaDomain, New Schema
    sambaGroupMapping, New Schema
    sambaHomeDrive, LDAP Special Attributes for sambaSamAccounts
    sambaHomePath, LDAP Special Attributes for sambaSamAccounts
    sambaIdmapEntry, New Schema
    sambaLogonScript, LDAP Special Attributes for sambaSamAccounts
    SambaNTPassword, Security and sambaSamAccount
    sambaProfilePath, LDAP Special Attributes for sambaSamAccounts
    SambaSAMAccount, Backup Domain Controller Configuration, Account Management Tools, Adding User Accounts, Deleting Accounts, Changing User Accounts, tdbsam
    sambaSamAccount, LDAP Directories and Windows Computer Accounts, Schema and Relationship to the RFC 2307 posixAccount, OpenLDAP Configuration, Accounts and Groups Management, LDAP Special Attributes for sambaSamAccounts, New Schema
    sambaSAMAccount, Security and sambaSamAccount
    sambaSID, LDAP Changes in Samba-3.0.23
    sambaUNIXIdPool, New Schema
    SambaXP conference, Technical Discussion
    samdb interface, smbpasswd: Encrypted Password Database
    same domain/workgroup, Multiple Virtual Server Hosting
    Sarbanes-Oxley, The pdbedit Tool
    scalability, Features and Benefits, Features and Benefits, Account Information Databases, tdbsam, Features and Benefits
    scalable, Comments Regarding LDAP
    scalable backend, Features and Benefits
    scalable coherent interface (see SCI)
    scale, UNIX Printfile Conversion and GUI Basics
    scanner module, Discussion
    schannel, Cannot Log onto Domain Member Workstation After Joining Domain
    schema, IDMAP and NSS Using LDAP from ADS with RFC2307bis Schema Extension
    schema file, New Account Storage Systems
    scp, Rsync
    script, Adding Machine to Domain Fails
    scripted control, Remote and Local Management: The Net Command
    scripts, Browsing Support in Samba, Caution Regarding LDAP and Samba
    SCSI, High-Availability Server Products
    SeAddUsersPrivilege, Administering User Rights and Privileges, Rights Management Capabilities, Description of Privileges
    SeAssignPrimaryTokenPrivilege, Privileges Suppored by Windows 2000 Domain Controllers
    SeAuditPrivilege, Privileges Suppored by Windows 2000 Domain Controllers
    SeBackupPrivilege, Administering User Rights and Privileges, Privileges Suppored by Windows 2000 Domain Controllers
    SeChangeNotifyPrivilege, Privileges Suppored by Windows 2000 Domain Controllers
    Seclib, Viewing File Ownership
    secondary controller, Domain Layout
    SeCreateGlobalPrivilege, Privileges Suppored by Windows 2000 Domain Controllers
    SeCreatePagefilePrivilege, Privileges Suppored by Windows 2000 Domain Controllers
    SeCreatePermanentPrivilege, Privileges Suppored by Windows 2000 Domain Controllers
    SeCreateTokenPrivilege, Privileges Suppored by Windows 2000 Domain Controllers
    secret, Important Notes About Security
    secrets.tdb, Backup Domain Controller Configuration, Sharing User ID Mappings between Samba Domain Members, Initialize the LDAP Database, The Printing *.tdb Files
    (see also TDB)
    section name, Configuration File Syntax
    secure, Features and Benefits
    secure access, Single Sign-On and Domain Security
    secure authentication, User Rights and Privileges
    secure communications, Security and sambaSamAccount
    secured networks, Introduction
    security, Samba Security Modes, Preparing for Domain Control, Introduction, Multiple Virtual Server Personalities
    controllers, Domain Security Mode (User-Level Security)
    modes, Features and Benefits
    settings, Example Configuration
    security = user, Joining an NT4-type Domain with Samba-3
    security account, Overview
    Security Account Manager (see SAM)
    Security Assertion Markup Language (see SAML)
    security context, Domain Member Server
    security contexts, Trust Relationship Background
    security credentials, Backup Domain Controller, Native MS Windows NT4 Trusts Configuration
    security domain, Trust Relationship Background
    security domains, Trust Relationship Background
    security flaw, Why Can Users Access Other Users' Home Directories?
    security hole, Using IPC$ Share-Based Denials
    security identifier, Managing Security Identifiers (SIDS) (see SID)
    security level, Server Security (User Level Security)
    security levels, Samba Security Modes
    security mode, Server Types and Security Modes, Security Mode and Master Browsers
    Security Mode, Samba Security Modes
    security modes, Samba Security Modes
    security name-space, Identity Mapping (IDMAP)
    security policies, Why Can Users Access Other Users' Home Directories?
    security settings, New Features in Samba-3.0.x
    security structure, Trust Relationship Background
    security vulnerability, Upgrading Samba
    security-aware, application/octet-stream Printing
    SeDebugPrivilege, Privileges Suppored by Windows 2000 Domain Controllers
    SeDiskOperatorPrivilege, Administering User Rights and Privileges, Rights Management Capabilities, Description of Privileges
    SeEnableDelegationPrivilege, Privileges Suppored by Windows 2000 Domain Controllers
    SeImpersonatePrivilege, Privileges Suppored by Windows 2000 Domain Controllers
    SeIncreaseBasePriorityPrivilege, Privileges Suppored by Windows 2000 Domain Controllers
    SeIncreaseQuotaPrivilege, Privileges Suppored by Windows 2000 Domain Controllers
    SeLoadDriverPrivilege, Privileges Suppored by Windows 2000 Domain Controllers
    SeLockMemoryPrivilege, Privileges Suppored by Windows 2000 Domain Controllers
    SeMachineAccountPrivilege, Administering User Rights and Privileges, Rights Management Capabilities, Description of Privileges, Privileges Suppored by Windows 2000 Domain Controllers
    SeManageVolumePrivilege, Privileges Suppored by Windows 2000 Domain Controllers
    separate instances, Multiple Server Hosting
    separate servers, Advanced Configuration Techniques
    separate shares, The [global] Section
    separate workgroups, Multiple Virtual Server Personalities
    SePrintOperatorPrivilege, Administering User Rights and Privileges, Rights Management Capabilities, Description of Privileges
    SeProfileSingleProcessPrivilege, Privileges Suppored by Windows 2000 Domain Controllers
    SeRemoteShutdownPrivilege, Administering User Rights and Privileges, Rights Management Capabilities, Description of Privileges, Privileges Suppored by Windows 2000 Domain Controllers
    SeRestorePrivilege, Administering User Rights and Privileges, Privileges Suppored by Windows 2000 Domain Controllers
    server failure, Why Is This So Hard?
    Server Manager, MS Windows Workstation/Server Machine Trust Accounts, Manual Creation of Machine Trust Accounts, Managing Domain Machine Accounts using NT4 Server Manager, Remote Server Administration
    Server Manager for Domains, Managing Domain Machine Accounts using NT4 Server Manager
    Server Message Block (see SMB)
    server pool, The Distributed File System Challenge, Restrictive Constraints on Distributed File Systems
    Server Type, Server Types
    Domain Controller, Domain Controller
    Domain Member, Domain Member Server, Example Configuration, Features and Benefits
    Stand-alone, Standalone Server
    server type, Overview
    domain member, Example Configuration
    Server Types, Samba Server Deployment Types and IDMAP
    server-mode, What Makes Samba a Domain Controller?
    service name, Example Configuration
    service-level, Printing-Related Configuration Parameters, The [global] Section
    services provided, Samba Support
    SeSecurityPrivilege, Privileges Suppored by Windows 2000 Domain Controllers
    SeShutdownPrivilege, Privileges Suppored by Windows 2000 Domain Controllers
    session, Anatomy of /etc/pam.d Entries
    session services, Features and Benefits
    session setup, User Level Security, Server Security (User Level Security)
    sessionid.tdb, The Printing *.tdb Files
    (see also TDB)
    SessionSetupAndX, Domain Member Server or Domain Member Client
    SeSyncAgentPrivilege, Privileges Suppored by Windows 2000 Domain Controllers
    SeSystemEnvironmentPrivilege, Privileges Suppored by Windows 2000 Domain Controllers
    SeSystemProfilePrivilege, Privileges Suppored by Windows 2000 Domain Controllers
    SeSystemtimePrivilege, Privileges Suppored by Windows 2000 Domain Controllers
    set a password, Central Print Serving
    set group id (see SGID)
    set printer properties, The [global] Section
    set user id (see SUID)
    SeTakeOwnershipPrivilege, Administering User Rights and Privileges, Rights Management Capabilities, Description of Privileges, Privileges Suppored by Windows 2000 Domain Controllers
    SeTcbPrivilege, Privileges Suppored by Windows 2000 Domain Controllers
    setdriver, A Check of the rpcclient man Page, Requirements for adddriver and setdriver to Succeed
    SetPrinter(), A Check of the rpcclient man Page
    setting up directories, File and Directory Access Control
    SeUndockPrivilege, Privileges Suppored by Windows 2000 Domain Controllers
    severely impaired, TCP/IP without NetBIOS
    SFU, IDMAP, Active Directory, and MS Services for UNIX 3.5
    SFU 3.5, Primary Domain Controller
    SGI-RGB, MIME Types and CUPS Filters
    SGID, File and Directory Access Control
    shadow, LDAP Directories and Windows Computer Accounts
    shadow copies, Shadow Copy Setup
    shadow password file, Joining an NT4-type Domain with Samba-3
    shadow utilities, Features and Benefits
    shadow_copy, shadow_copy, Shadow Copy Setup
    shadow_copy module, shadow_copy
    share, Configuration File Syntax, File, Directory, and Share Access Controls, The [global] Section
    share access, Access Controls on Shares
    share ACLs, Samba-3 Implementation Choices
    share management, Overview
    share modes, The Distributed File System Challenge
    share permissions, Windows NT4 Workstation/Server
    Share Permissions, Windows 200x/XP
    share settings, Features and Benefits
    share stanza controls, Samba-3 Implementation Choices
    share-level, Samba Security Modes, Share-Level Security, Features and Benefits
    share-level ACLs, Applicable Only to Versions Earlier than 3.0.11
    share-mode, Features and Benefits
    share-mode security, Security Mode and Master Browsers
    share-mode server, Features and Benefits
    shared secret, MS Windows Workstation/Server Machine Trust Accounts
    shares, What Is Browsing?
    shares and files, Requirements
    share_info.tdb, Access Controls on Shares, The Printing *.tdb Files
    (see also TDB)
    Sharing, Windows 200x/XP
    shell scripts, Print Commands
    shift, UNIX Printfile Conversion and GUI Basics
    Shift_JIS, Japanese Charsets, Basic Parameter Setting
    shortcuts, TCP/IP Configuration, Windows 9x/Me Profile Setup
    Shortcuts, MS Windows NTFS Comparison with UNIX File Systems
    show-stopper-type, Planning and Getting Started
    SID, Features and Benefits, The System Cannot Log You On (C000019B), Backup Domain Controller Configuration, Example Configuration, Why Is This Better Than security = server?, Sharing User ID Mappings between Samba Domain Members, User and Group Changes, Group Mapping Changes in Samba-3.0.23, Technical Information, Mapping User Identifiers between MS Windows and UNIX, LDAP Directories and Windows Computer Accounts, Group Mapping: MS Windows and UNIX, Features and Benefits, Managing Security Identifiers (SIDS), Identity Mapping (IDMAP), Domain Member Server or Domain Member Client, Primary Domain Controller, IDMAP_RID with Winbind, Rights Management Capabilities, The Administrator Domain SID, Features and Benefits, Handling of Foreign SIDs, Side Bar Notes, Get SID, Multiple Server Hosting, New Features in Samba-3.0.x, Profile Migration/Creation
    SID management, Overview
    SID-to-GID, Features and Benefits
    SIDs, Samba-3 Implementation Choices
    signing, Cannot Log onto Domain Member Workstation After Joining Domain
    simple access controls, Server Share and Directory Layout
    simple configuration, Example Configuration
    simple guide, Upgrading from Samba-2.x to Samba-3.0.25
    Simple Object Access Protocol (see SOAP)
    simple operation, New Account Storage Systems
    simple print server, Central Print Serving
    simple printing, Simple Print Configuration
    simplest
    configuration, Example Configuration
    simplicity, Features and Benefits
    Simplicity is king, Server Share and Directory Layout
    single DHCP server, MS Windows Me
    single repository, Account Information Databases
    single server, The Front-End Challenge
    single sign-on, Features and Benefits (see SSO)
    Single Sign-On, Caveats to Be Considered
    single-byte charsets, What Are Charsets and Unicode?
    single-logon, The Special Case of Windows 9x/Me
    single-sign-on, Objectives
    single-user mode, Requirements
    slapadd, Initialize the LDAP Database
    slapd, OpenLDAP Configuration
    slapd.conf, LDAP Changes in Samba-3.0.23, OpenLDAP Configuration, Security and sambaSamAccount
    slapd.pem, LDAP Configuration Notes
    slapindex, LDAP Changes in Samba-3.0.23
    slappasswd, Initialize the LDAP Database
    slave servers, Domain Layout
    slow browsing, Browsing of Shares and Directories is Very Slow
    slow network, Samba Performance Problem Due to Changing Linux Kernel
    slow network browsing, Invalid Cached Share References Affects Network Browsing
    slow performance, Samba Performance is Very Slow
    smart printers, Overview
    SMB, Server Security (User Level Security), I Can't Join a Windows 2003 PDC, Background, Features and Benefits, NetBIOS over TCP/IP, Technical Overview of Browsing, Using Interface Protection, Printing Developments Since Samba-2.2, Name Resolution as Used within MS Windows Networking, BackupPC, The Front-End Challenge, Server Pool Communications, Analyzing and Solving Samba Problems
    SMB encryption, Advantages of Encrypted Passwords
    SMB locks, Server Pool Communications
    SMB name, Name Resolution as Used within MS Windows Networking
    SMB networking, Diagnostics Tools
    SMB password, The smbpasswd Tool
    SMB Password, Features and Benefits
    SMB password encryption, Important Notes About Security
    smb ports, Multiple Virtual Server Personalities
    SMB printers, Administrator Cannot Install Printers for All Local Users
    SMB requests, Demultiplexing SMB Requests
    SMB semantics, The Distributed File System Challenge
    SMB server, Advantages of Encrypted Passwords
    SMB Server, Features and Benefits
    SMB services, Restrictive Constraints on Distributed File Systems
    SMB signing, I Can't Join a Windows 2003 PDC, New Features in Samba-3.0.x
    SMB state information, Demultiplexing SMB Requests
    SMB-based messaging, Discussion
    smb-cdserver.conf, Multiple Virtual Server Personalities
    smb.conf, Multiple Virtual Server Personalities
    SMB/CIFS, What Qualifies a Domain Controller on the Network?, I Can't Join a Windows 2003 PDC, Important Notes About Security, What Are Charsets and Unicode?
    SMB/CIFS server, Password Backends
    smbclient, Testing with smbclient, Installing Driver Files into [print$], smbclient to Confirm Driver Installation, BackupPC, The Tests, Debugging with Samba Itself
    smbd, Starting Samba, Example Configuration, Test Your Config File with testparm, Secure Read-Write File and Print Server, Example Configuration, smbpasswd: Encrypted Password Database, Schema and Relationship to the RFC 2307 posixAccount, Configuring Samba, Domain Member Server or Domain Member Client, NT4-Style Domains (Includes Samba Domains), Description of Privileges, Verifying Configuration with testparm, Rapid Configuration Validation, extd_audit, Features and Benefits, Testing Things Out, Join the Samba Server to the PDC Domain, Linux, Solaris, Server Pool Communications, Handling Large Directories, Multiple Server Hosting, Multiple Virtual Server Personalities, Debugging with Samba Itself
    smbgroupedit, Remote and Local Management: The Net Command
    smbgrpadd.sh, Sample smb.conf Add Group Script
    smbHome, LDAP Special Attributes for sambaSamAccounts
    smbldap-groupadd, Adding or Creating a New Group
    smbldap-tools, ldapsam
    smbpasswd, Example Configuration, Domain Control: Example Configuration, Backup Domain Controller Configuration, How Do I Replicate the smbpasswd File?, MS Windows Workstation/Server Machine Trust Accounts, Configure smb.conf, Sharing User ID Mappings between Samba Domain Members, Group Mapping Changes in Samba-3.0.23, Account Information Databases, Backward Compatibility Account Storage Systems, Account Management Tools, The smbpasswd Tool, The pdbedit Tool, User Account Management, Account Import/Export, smbpasswd: Encrypted Password Database, ldapsam, Schema and Relationship to the RFC 2307 posixAccount, Initialize the LDAP Database, Domain Member Server or Domain Member Client, Samba as the Trusted Domain, Samba PDC, Passdb Backends and Authentication, New Schema
    smbpasswd format, Listing User and Machine Accounts
    smbpasswd plaintext database, smbpasswd: Encrypted Password Database
    SMBsessetupX, The Special Case of Windows 9x/Me
    smbspool, Printing from CUPS to Windows-Attached Printers
    smbstatus, Avoid Being Connected to the Samba Server as the Wrong User, Attaching to a Running Process
    SMBtconX, The Special Case of Windows 9x/Me
    smbusers, User-Based Protection
    SMS, The Windows Network Monitor
    Snapshots, Shadow Copy Setup
    sniffer, The Special Case of Windows 9x/Me, Diagnostics Tools
    socket, Multiple Server Hosting
    socket address, Multiple Server Hosting
    SOFTQ printing system, The [global] Section
    Solaris, Mapping Common UIDs/GIDs on Distributed Machines, Configure Winbind and PAM, Remote Management with ThinLinc, Features and Benefits, Basic Parameter Setting
    Solaris 9, Solaris
    source code, Example Configuration
    space character, Adding Groups Fails
    special account, User Rights and Privileges, Samba as the Trusted Domain
    special section, [print$] Stanza Parameters
    special sections, The [global] Section
    special stanza, [print$] Stanza Parameters
    specific restrictions, Access Controls on Shares
    Specify an IP address, MS Windows Me
    spinning process, Attaching to a Running Process
    spool, Verifying Configuration with testparm
    directory, Configuration File Syntax
    spool files, Custom Print Commands
    spooled file, Technical Introduction
    spooler., Configuration File Syntax
    spooling, Custom Print Commands, Central Spooling vs. “Peer-to-Peer” Printing
    central, Central Spooling vs. “Peer-to-Peer” Printing
    peer-to-peer, Central Spooling vs. “Peer-to-Peer” Printing
    spooling path, Verifying Configuration with testparm
    spooling-only, Raw Print Serving: Vendor Drivers on Windows Clients
    SPOOLSS, Printing Developments Since Samba-2.2
    SQL, Passdb Changes
    SQUID, Single Sign-On and Domain Security
    SRV records, Configure /etc/krb5.conf, DNS and Active Directory
    SRV RR, Background Information
    SrvMgr.exe, Managing Domain Machine Accounts using NT4 Server Manager
    srvmgr.exe, Managing Domain Machine Accounts using NT4 Server Manager
    SRVTOOLS.EXE, Managing Domain Machine Accounts using NT4 Server Manager, Remote Server Administration
    ssh, Backup Domain Controller Configuration, How Do I Replicate the smbpasswd File?, smbpasswd: Encrypted Password Database, BackupPC
    SSH, smbclient to Confirm Driver Installation, Remote Management with ThinLinc
    SSL, Securing SWAT through SSL
    SSO, Single Sign-On and Domain Security, Features and Benefits, Comments Regarding LDAP
    stability, Objectives
    stack trace, Internal Errors
    stale network links, Invalid Cached Share References Affects Network Browsing
    stand-alone server, Standalone Samba Server
    standalone, Server Types, Preparing for Domain Control, Overview, Domain Member Server or Domain Member Client
    standalone filter, pstoraster
    standalone server, Joining an NT4-type Domain with Samba-3, Standalone Servers, Features and Benefits, Background, Adding User Accounts, Features and Benefits, Domain Layout
    standard confirmation, Creating an NT4 Domain Trust
    stanza, Configuration File Syntax, Handling Large Directories
    stapling, pstops
    StartDocPrinter, Printing Developments Since Samba-2.2
    starting samba
    nmbd, Starting Samba, Secure Read-Write File and Print Server, Example Configuration
    smbd, Starting Samba, Secure Read-Write File and Print Server, Example Configuration
    winbindd, Starting Samba, Example Configuration, Features and Benefits
    startsmb, Alternative: Starting smbd as a Daemon
    StartTLS, Security and sambaSamAccount
    startup
    process, Starting Samba
    startup script, Starting and Testing the winbindd Daemon
    state, Why Is This So Hard?
    state information, Why Is This So Hard?
    state of knowledge, Features and Benefits
    static WINS entries, Static WINS Entries
    status32 codes, New Features in Samba-3.0.x
    sticky bit, File and Directory Access Control, Server Share and Directory Layout
    storage mechanism, Account Management Tools
    storage methods, The smbpasswd Tool
    stphoto2.ppd, Examples for Filtering Chains
    strange delete semantics, Handling Large Directories
    stripped of comments, Features and Benefits
    strptime, Changing User Accounts
    stunnel, Securing SWAT through SSL
    su, Anatomy of /etc/pam.d Entries
    subnet mask, MS Windows XP Professional, MS Windows Me, The Tests
    subnets, NetBIOS over TCP/IP, Configuring Workgroup Browsing
    subscription, Free Support
    subsuffix parameters, New Suffix for Searching
    Subversion, Introduction, Access via Subversion
    successful join, Testing Server Setup
    successful migration, Objectives
    sufficient, Anatomy of /etc/pam.d Entries
    suffixes, MIME Types and CUPS Filters
    SUID, File and Directory Access Control
    Sun, Domain Member Server
    Sun ONE iDentity server, Features and Benefits
    Sun Solaris, Features and Benefits
    SUN-Raster, MIME Types and CUPS Filters
    support, Samba Support
    support exposure, Objectives
    SVN
    web, Access via ViewCVS
    SVRTOOLS.EXE, Features and Benefits
    SWAT, Configuring Samba (smb.conf), SWAT: The Samba Web Administration Tool
    swat, SWAT, Validate SWAT Installation, Locating the SWAT File, Enabling SWAT for Use
    enable, Enabling SWAT for Use
    security, Securing SWAT through SSL
    SWAT binary support, Validate SWAT Installation
    swat command-line options, Locating the SWAT File
    SWAT permission allowed, Enabling SWAT for Use
    symbolic links, Features and Benefits
    synchronization, Domain Controller Types, Security Mode and Master Browsers, WINS: The Windows Internetworking Name Server, Behavior of Cross-Subnet Browsing
    synchronization problems, Introduction
    synchronize, Backup Domain Controller Configuration, Configure /etc/krb5.conf, Use of the Remote Browse Sync Parameter, Behavior of Cross-Subnet Browsing
    synchronized, Backup Domain Controller Configuration
    syntax tolerates spelling errors, Simple Print Configuration
    system access controls, New Account Storage Systems
    system accounts, User Account Management
    system administrator, User Rights and Privileges
    system groups, Mapping Windows Groups to UNIX Groups
    system interface scripts, User Rights and Privileges
    system policies, Creating and Managing System Policies
    System Policy Editor, Creating and Managing System Policies, Administration of Windows 200x/XP Policies, MS Windows 9x/Me
    system security, Applicable Only to Versions Earlier than 3.0.11
    system tools, Features and Benefits
    SYSV, The [global] Section
    SYSVOL, MS Windows 200x/XP Professional Policies

    T

    tail, Assumptions
    take ownership, Description of Privileges
    Take Ownership, Viewing File Ownership
    tape, Server Share and Directory Layout
    tar, BackupPC
    tarball, Example Configuration
    tattoo effect, Samba-3 Implementation Choices
    TCP, Multiple Interfaces, Why Is This So Hard?
    TCP data streams, The Front-End Challenge
    TCP failover, Why Is This So Hard?
    TCP port, Features and Benefits
    TCP port 139, Background Information, Multiple Virtual Server Personalities
    TCP port 445, Background Information, Multiple Virtual Server Personalities
    tcp ports, Join the Samba Server to the PDC Domain
    TCP/IP, MS Windows XP Professional, MS Windows Me, Features and Benefits, Windows Networking Protocols
    TCP/IP configuration, MS Windows XP Professional, MS Windows Me
    TCP/IP configuration panel, MS Windows 2000
    TCP/IP protocol configuration, Technical Details
    TCP/IP protocol settings, MS Windows XP Professional, MS Windows 2000
    TCP/IP protocol stack, WINS: The Windows Internetworking Name Server
    TCP/IP-only, Windows Networking Protocols
    tcpdump, Tcpdump
    TDB, New Account Storage Systems, Running rpcclient with setdriver, The Printing *.tdb Files, Trivial Database Files, Multiple Server Hosting
    backing up (see tdbbackup)
    tdb, User and Group ID Allocation, Server Pool Communications, Features and Benefits
    tdb data files, TDB Data Files
    TDB database, Running rpcclient with adddriver
    TDB database files, Setting Device Modes on New Printers
    tdb file backup, TDB Data Files
    tdb file descriptions, TDB Database File Information, TDB Data Files
    tdb file locations, TDB Database File Information
    tdb files, Access Controls on Shares
    tdbbackup, Using tdbbackup, Corrupt tdb Files
    tdbdump, Access Controls on Shares
    tdbsam, Domain Control: Example Configuration, Group Mapping Changes in Samba-3.0.23, Account Information Databases, Technical Information, Listing User and Machine Accounts, smbpasswd: Encrypted Password Database, tdbsam, Default Users, Groups, and Relative Identifiers, Domain Member Server or Domain Member Client, Objectives
    tdbsam databases, Password Backends
    technical reviewers, Advanced Configuration Techniques
    Telnet, Advantages of Non-Encrypted Passwords
    telnet logins, Linux/FreeBSD-Specific PAM Configuration
    template, Creating and Managing Group Profiles
    temporary location, Print Commands
    terminal server, Remote Management with ThinLinc
    Terminal Server, Demultiplexing SMB Requests
    Testing Server Setup, Configure /etc/krb5.conf
    testparm, Test Your Config File with testparm, Central Print Serving, Simple Print Configuration, Verifying Configuration with testparm, Rapid Configuration Validation, Extended Printing Configuration, Assumptions, The Tests, Debugging with Samba Itself
    tethereal, Tcpdump
    text/plain, MIME Type Conversion Rules
    texttops, MIME Type Conversion Rules
    thin client, Remote Management with ThinLinc
    ThinLinc, Remote Management with ThinLinc
    tid, Demultiplexing SMB Requests
    TIFF, MIME Types and CUPS Filters
    TightVNC, Remote Management from NoMachine.Com, Remote Management with ThinLinc
    time difference, Configure /etc/krb5.conf
    time format, Changing User Accounts
    time-to-live (see TTL)
    tool, Windows 200x/XP
    tools, Central Print Serving, Caution Regarding LDAP and Samba
    tools\reskit\netadmin\poledit, Windows 9x/ME Policies
    traditional printing, Custom Print Commands
    training course, Discussion of Backup Solutions
    transfer differences, Rsync
    transformation, MIME Types and CUPS Filters
    transitive, Trust Relationship Background
    transparent access, Features and Benefits
    transparently reconnected, The Ultimate Goal
    transport connection loss, Opportunistic Locking Overview
    Transport Layer Seccurity, TLS
    Configuring, Configuring
    Introduction, Introduction
    transport layer security (see TLS)
    Transport Layer Security, TLS
    Testing, Testing
    Troubleshooting, Troubleshooting
    trigger, Preparing for Domain Control, MS Windows NT4-style Domain Control
    trivial database, New Account Storage Systems (see TDB)
    Trivial Database, Features and Benefits
    troubleshoot, Rapid Configuration Validation
    troubleshooting, Printing from CUPS to Windows-Attached Printers
    Tru64 UNIX, Basic Parameter Setting
    trust, Features and Benefits, LDAP Directories and Windows Computer Accounts
    account, Domain Security Mode (User-Level Security)
    trust account, Domain Security Mode (User-Level Security), Account Flags Management, NT4-Style Domain Trusts with Windows 2000
    interdomain, Features and Benefits
    machine, Features and Benefits
    trust account password, Features and Benefits
    trust accounts, LDAP Directories and Windows Computer Accounts, Overview
    trust established, Interdomain Trust Facilities
    trust relationship, Trust Relationship Background, Completing an NT4 Domain Trust, Interdomain Trust Facilities, Configuring Samba NT-Style Domain Trusts, NT4-Style Domain Trusts with Windows 2000
    trust relationships, Interdomain Trust Relationships, Features and Benefits, Trust Relationship Background, Creating an NT4 Domain Trust, New Features in Samba-3.0.x
    trusted, Behavior of Cross-Subnet Browsing, User Rights and Privileges
    trusted domain, Nested Groups: Adding Windows Domain Groups to Windows Local Groups, Interdomain Trust Relationships, Trust Relationship Background, Completing an NT4 Domain Trust, Samba as the Trusting Domain, Name Service Switch
    trusted domain name, Samba as the Trusted Domain
    trusted party, Samba as the Trusted Domain
    trusting domain, Interdomain Trust Relationships, Trust Relationship Background, Completing an NT4 Domain Trust
    trusting party, Samba as the Trusted Domain
    trusts, Interdomain Trust Relationships, Trust Relationship Background
    TTL, Static WINS Entries
    turn oplocks off, Advanced Samba Oplocks Parameters
    turnkey solution, LDAP Directories and Windows Computer Accounts
    two-up, Examples for Filtering Chains
    two-way
    propagation, Features and Benefits
    two-way trust, Trust Relationship Background, Native MS Windows NT4 Trusts Configuration, Interdomain Trust Facilities

    U

    UCS-2, Japanese Charsets
    UDP, Preparing for Domain Control, NetBIOS over TCP/IP, How Browsing Functions, Forcing Samba to Be the Master, Multiple Interfaces, Cross-Subnet Browsing
    UDP port 137, Background Information
    udp ports, Join the Samba Server to the PDC Domain
    UDP unicast, How Browsing Functions
    UID, Example Configuration, MS Windows Workstation/Server Machine Trust Accounts, Manual Creation of Machine Trust Accounts, Why Is This Better Than security = server?, Sharing User ID Mappings between Samba Domain Members, Technical Information, Mapping User Identifiers between MS Windows and UNIX, Mapping Common UIDs/GIDs on Distributed Machines, LDAP Directories and Windows Computer Accounts, Listing User and Machine Accounts, Features and Benefits, Overview, Mapping Windows Groups to UNIX Groups, UNIX and Windows User Management, Identity Mapping (IDMAP), Domain Member Server or Domain Member Client, Primary Domain Controller, User Rights and Privileges, Features and Benefits, Handling of Foreign SIDs, Starting and Testing the winbindd Daemon
    uid, OpenLDAP Configuration
    UID numbers, Domain Member Server or Domain Member Client
    UID range, Interdomain Trust Relationships
    unauthorized, MS Windows Workstation/Server Machine Trust Accounts
    unauthorized access, File, Directory, and Share Access Controls
    UNC notation, Identifying Driver Files
    unexpected.tdb, The Printing *.tdb Files
    (see also TDB)
    unicast, NetBIOS over TCP/IP
    unicode, What Are Charsets and Unicode?
    Unicode, Samba and Charsets, New Features in Samba-3.0.x
    Unicode UTF-8, Basic Parameter Setting
    unified logon, Introduction
    UNIX, Basic Parameter Setting
    server, Features and Benefits
    UNIX account, MS Windows Workstation/Server Machine Trust Accounts, Manual Creation of Machine Trust Accounts, On-the-Fly Creation of Machine Trust Accounts
    unix charset, Basic Parameter Setting
    UNIX Domain Socket, File and Directory Access Control
    UNIX domain socket, How Winbind Works
    UNIX file system access controls, Features and Benefits
    UNIX group, Mapping Windows Groups to UNIX Groups
    UNIX groups, Group Mapping: MS Windows and UNIX, What Winbind Provides
    UNIX home directories, Why Can Users Access Other Users' Home Directories?
    UNIX host system, User Rights and Privileges
    UNIX ID, User and Group ID Allocation
    UNIX locking, Discussion
    UNIX login ID, MS Windows Workstation/Server Machine Trust Accounts
    UNIX permissions, Samba-3 Implementation Choices
    UNIX printer, The [global] Section
    UNIX printing, Technical Introduction
    UNIX system account, Adding Machine to Domain Fails
    UNIX system accounts, User Rights and Privileges
    UNIX system files, Features and Benefits
    UNIX user identifier (see UID)
    UNIX users, Why Is This Better Than security = server?, What Winbind Provides
    UNIX-style encrypted passwords, Technical Information
    UNIX-user database, Background
    UNIX/Linux group, Warning: User Private Group Problems
    UNIX/Linux user account, UNIX and Windows User Management
    unlink calls, recycle
    unlinked, File and Directory Access Control
    unmapped groups, User and Group Changes
    unmapped users, User and Group Changes
    unprivileged account names, Reference Documentation Server
    unsigned drivers, Windows 200x/XP Local Security Policies
    unstoppable services, The Ultimate Goal
    unsupported encryption, Possible Errors
    unsupported software, Commercial Support
    updates, Upgrading Samba
    upload drivers, Features and Benefits
    uploaded driver, The [global] Section
    uploaded drivers, Point'n'Print Client Drivers on Samba Servers
    uploading, Point'n'Print Client Drivers on Samba Servers
    upper-case, User Level Security
    uppercase, Configure /etc/krb5.conf, Adding Machine to Domain Fails, Handling Large Directories
    uppercase character, Adding Groups Fails
    USB, Examples for Filtering Chains
    use computer anywhere, Features and Benefits
    user, User and Group Changes, LDAP Directories and Windows Computer Accounts, File and Directory Access Control
    user access management, Features and Benefits
    user account, LDAP Directories and Windows Computer Accounts, User Account Management, Account Flags Management, smbpasswd: Encrypted Password Database, UNIX and Windows User Management
    Adding/Deleting, The smbpasswd Tool
    user account database, MS Windows NT4-style Domain Control
    user accounts, Caution Regarding LDAP and Samba, Domain Member Server or Domain Member Client, User Rights and Privileges
    User Accounts
    Adding/Deleting, The pdbedit Tool, Accounts and Groups Management
    user and group, What Winbind Provides
    user and trust accounts, Account Information Databases
    user attributes, smbpasswd: Encrypted Password Database
    user authentication, Microsoft Remote Procedure Calls
    user database, Backup Domain Controller Configuration, Plaintext
    user encoded, Managing Security Identifiers (SIDS)
    user groups, Free Support
    user logons, User Rights and Privileges
    user management, The smbpasswd Tool, Overview, UNIX and Windows Group Management
    User Management, The pdbedit Tool, Accounts and Groups Management
    User Manager, Samba as the Trusted Domain, Samba as the Trusting Domain, Remote Server Administration, Creating and Managing Group Profiles
    User Manager for Domains, Remote Server Administration
    user or group, Using the “net rpc rights” Utility
    user profiles, Windows 9x/Me Profile Setup
    User Rights and Privileges, The Administrator Domain SID
    user-level, Samba Security Modes, User Level Security
    User-level access control, Domain Logon Configuration: Windows 9x/Me
    user-level security, Advantages of Encrypted Passwords
    user-mode security, Security Mode and Master Browsers
    user.DAT, Windows 9x/Me Profile Setup, Sharing Profiles between Windows 9x/Me and NT4/200x/XP Workstations
    user.MAN, Windows 9x/Me Profile Setup
    User.MAN, Mandatory Profiles
    useradd, Manual Creation of Machine Trust Accounts, On-the-Fly Creation of Machine Trust Accounts
    username, MS Windows NT4-style Domain Control
    username and password, Joining a Domain: Windows 2000/XP Professional
    username map, User Mapping
    userPassword, Initialize the LDAP Database
    users, Features and Benefits
    UsrMgr.exe, Managing Domain Machine Accounts using NT4 Server Manager
    UTF-8, Samba and Charsets, Basic Parameter Setting
    UTF-8 encoding, Enabling SWAT Internationalization Support

    V

    valid username/password, Using IPC$ Share-Based Denials
    valid users, The Tests
    validate, Test Your Config File with testparm, Introduction
    validate every backup, Server Share and Directory Layout
    validation, Single Sign-On and Domain Security, System and Account Policies
    vendor-provided drivers, Raw Print Serving: Vendor Drivers on Windows Clients
    verifiable, Behavior of Cross-Subnet Browsing
    verify, Rapid Configuration Validation
    version control, shadow_copy
    VFS, Domain Control: Example Configuration, Discussion
    VFS module, shadow_copy, Mandatory Profiles
    VFS modules, Discussion, VFS Modules Available Elsewhere
    vgcreate, Shadow Copy Setup
    vgdisplay, Shadow Copy Setup
    vipw, “$” Cannot Be Included in Machine Name, Manual Creation of Machine Trust Accounts
    Virtual File System (see VFS)
    virtual server, The Front-End Challenge, A Simple Solution
    virus scanner, Discussion
    Visual Studio, PostScript Drivers with No Major Problems, Even in Kernel +Mode
    vital task, Features and Benefits
    VNC/RFB, Remote Management from NoMachine.Com
    volume group, Shadow Copy Setup
    volunteers, Getting Mailing List Help
    vscan, vscan
    vuid, Demultiplexing SMB Requests

    W

    W32X86, Identifying Driver Files, PostScript Drivers with No Major Problems, Even in Kernel +Mode, Caveats to Be Considered
    W32X86/2, Using Windows-Formatted Vendor PPDs
    WAN, Forcing Samba to Be the Master, Slow and/or Unreliable Networks
    wbinfo, Starting and Testing the winbindd Daemon
    Web-based configuration, SWAT: The Samba Web Administration Tool
    WebClient, Browsing of Shares and Directories is Very Slow
    Welcome, Joining a Domain: Windows 2000/XP Professional
    well known RID, The Administrator Domain SID
    well-controlled network, Server Share and Directory Layout
    well-known RID, Default Users, Groups, and Relative Identifiers
    wide-area network bandwidth, Features and Benefits
    win election, Making Samba the Domain Master
    Win32 printing API, Printing Developments Since Samba-2.2
    WIN40, Identifying Driver Files, Obtaining Driver Files from Windows Client [print$] Shares, Caveats to Be Considered
    winbind, Why Is This Better Than security = server?, Nested Groups: Adding Windows Domain Groups to Windows Local Groups, Domain Member Server or Domain Member Client, Examples of IDMAP Backend Usage, NT4-Style Domains (Includes Samba Domains), Interdomain Trust Relationships, Features and Benefits, Configure smb.conf
    Winbind, Background, Target Uses, Microsoft Active Directory Services, Pluggable Authentication Modules, User and Group ID Allocation, Result Caching, Introduction, Configure nsswitch.conf and the Winbind Libraries on Linux and Solaris, NSS Winbind on AIX, Starting and Testing the winbindd Daemon, Linux/FreeBSD-Specific PAM Configuration, Conclusion, PAM-Based Distributed Authentication, Features and Benefits
    Winbind architecture, New Features in Samba-3.0.x
    Winbind hooks, What Winbind Provides
    Winbind services, Starting and Testing the winbindd Daemon
    Winbind-based authentication, PAM-Based Distributed Authentication
    winbind.so, Solaris-Specific Configuration
    winbindd, Starting Samba, Test Your Config File with testparm, Example Configuration, Example Configuration, Group Mapping Changes in Samba-3.0.23, LDAP Directories and Windows Computer Accounts, Features and Benefits, Nested Groups: Adding Windows Domain Groups to Windows Local Groups, UNIX and Windows User Management, Identity Mapping (IDMAP), Domain Member Server or Domain Member Client, Interdomain Trust Relationships, Features and Benefits, How Winbind Works, Requirements, Testing Things Out, Configure nsswitch.conf and the Winbind Libraries on Linux and Solaris, Configure smb.conf, Starting and Testing the winbindd Daemon, Solaris, Configure Winbind and PAM, Multiple Server Hosting
    winbindd daemon, Linux
    Windows, Identity Mapping (IDMAP), Basic Parameter Setting
    Windows 2000, Configure /etc/krb5.conf, Testing Server Setup, Network Browsing, Trust Relationship Background
    Windows 2000 Professional TCP/IP, MS Windows 2000
    Windows 2000 server, NT4-Style Domain Trusts with Windows 2000
    Windows 2003, Configure /etc/krb5.conf, I Can't Join a Windows 2003 PDC
    Windows 200x/XP, NetBIOS over TCP/IP, Features and Benefits
    Windows 9x/Me, Domain Logon Configuration: Windows 9x/Me, WINS Server Configuration, Windows Networking Protocols, Remote Server Administration
    Windows 9x/Me/XP Home, MS Windows Workstation/Server Machine Trust Accounts
    Windows account management, What Winbind Provides
    Windows client, What Rights and Privileges Will Permit Windows Client Administration?
    Windows client failover, Opportunistic Locking Overview
    Windows domain, Changes in Behavior
    Windows Explorer, Problem Resolution, Identifying Driver Files
    Windows group, Group Mapping: MS Windows and UNIX, Warning: User Private Group Problems, Mapping Windows Groups to UNIX Groups, User Rights and Privileges
    Windows group account, The Administrator Domain SID
    Windows groups, Mapping Windows Groups to UNIX Groups
    Windows Internet Name Server (see WINS)
    Windows Logon, Windows 9x/Me Profile Setup
    Windows Me TCP/IP, MS Windows Me
    Windows Millennium, MS Windows Me
    Windows Millennium edition (Me) TCP/IP, MS Windows Me
    Windows network clients, Features and Benefits
    Windows NT domain name, Domain Logon Configuration: Windows 9x/Me
    Windows NT PostScript driver, Printing from CUPS to Windows-Attached Printers
    Windows NT Server, Samba as the Trusted Domain
    Windows NT/2000/XP, Check Samba for Driver Recognition
    Windows NT/200x, WINS Server Configuration, Introduction
    Windows NT/200x/XP, The [global] Section
    Windows NT/200x/XP Professional, MS Windows Workstation/Server Machine Trust Accounts, Joining a Domain: Windows 2000/XP Professional, Common Errors
    Windows NT3.10, Essential Background Information
    Windows NT4, Windows NT4 Workstation/Server, Features and Benefits
    Windows NT4 domains, Interdomain Trust Facilities
    Windows NT4 Server, Configuring Samba NT-Style Domain Trusts
    Windows NT4/200X, LDAP Directories and Windows Computer Accounts
    Windows NT4/200x, Discussion
    Windows NT4/200x/XP, NetBIOS Over TCP/IP Enabled, Default Users, Groups, and Relative Identifiers, Windows 200x/XP
    Windows NT4/2kX/XPPro, User Rights and Privileges
    Windows PPD, 690 “Perfect” Printers
    Windows privilege model, Rights Management Capabilities
    Windows Registry, MS Windows Workstation/Server Machine Trust Accounts
    windows registry settings, Windows 9x/Me Profile Setup
    default profile locations, MS Windows NT4 Workstation, MS Windows 200x/XP
    profile path, Windows 9x/Me Profile Setup
    roaming profiles, Disabling Roaming Profile Support
    Windows Resource Kit, Disabling Roaming Profile Support
    Windows Security Identifiers (see SID)
    Windows Terminal server, Remote Management from NoMachine.Com
    Windows Terminal Server, Remote Management with ThinLinc
    Windows user, User Rights and Privileges
    Windows user accounts, UNIX and Windows User Management
    Windows workstation., What Rights and Privileges Will Permit Windows Client Administration?
    Windows XP Home, Important Notes About Security
    Windows XP Home edition, Features and Benefits, The Special Case of MS Windows XP Home Edition, Domain Logon Configuration: Windows 9x/Me
    Windows XP Home Edition, MS Windows 200x/XP
    Windows XP Professional, MS Windows XP Professional, Features and Benefits
    Windows XP Professional TCP/IP, MS Windows 2000
    Windows XP TCP/IP, MS Windows XP Professional
    Windows95/98/ME, Check Samba for Driver Recognition
    winnt.adm, Windows NT4-Style Policy Files
    WINS, Features and Benefits, Domain Controller Types, Preparing for Domain Control, What Qualifies a Domain Controller on the Network?, Joining an NT4-type Domain with Samba-3, Reference Documentation Server, MS Windows XP Professional, MS Windows 2000, MS Windows Me, Network Browsing, Features and Benefits, What Is Browsing?, NetBIOS over TCP/IP, How Browsing Functions, Domain Browsing Configuration, Making Samba the Domain Master, WINS: The Windows Internetworking Name Server, WINS Server Configuration, Technical Overview of Browsing, Browsing Support in Samba, Cross-Subnet Browsing, Behavior of Cross-Subnet Browsing, WINS Lookup, Example Configuration
    wins, /etc/nsswitch.conf
    WINS Configuration, Browsing of Shares and Directories is Very Slow
    WINS lookup, Joining an NT4-type Domain with Samba-3
    WINS replication, WINS Replication, Static WINS Entries
    WINS Server, What Is Browsing?
    WINS server, How Browsing Functions, Configuring Workgroup Browsing, Making Samba the Domain Master, WINS Server Configuration, Browsing Support in Samba, Browsing of Shares and Directories is Very Slow
    WINS server address, How Browsing Functions
    WINS server settings, MS Windows Me
    WINS servers, WINS: The Windows Internetworking Name Server
    WINS service, WINS Server Configuration
    WINS Support, What Is Browsing?
    wins.dat, Static WINS Entries
    without Administrator account, The Administrator Domain SID
    without ADS, Objectives
    work-flow protocol, Single Sign-On and Domain Security
    workgroup, Server Security (User Level Security), Preparing for Domain Control, The Special Case of Windows 9x/Me, Domain Logon Configuration: Windows 9x/Me, Configuring Workgroup Browsing, Making Samba the Domain Master, Name Resolution as Used within MS Windows Networking, Multiple Server Hosting, Multiple Virtual Server Personalities
    membership, Preparing for Domain Control
    workstations, Technical Information
    world-writable, File and Directory Access Control
    write, File and Directory Access Control
    write access, Protecting Directories and Files from Deletion
    Write caching, Opportunistic Locking Overview
    write changes, Backup Domain Controller
    write permission, Create the Computer Account
    writeable, fake_perms
    WYSIWYG, Windows Drivers, GDI, and EMF

    X

    X Window + System, Windows Drivers, GDI, and EMF, UNIX Printfile Conversion and GUI Basics
    X.509 certificates, Introduction
    XFS file system, Shadow Copy Setup
    xfsprogs, Shadow Copy Setup
    xinetd, Validate SWAT Installation, Starting from inetd.conf (see inetd)
    XML, Passdb Changes
    XML-based datasets, Foomatic Database-Generated PPDs
    xpp, Foomatic Database-Generated PPDs
    Xprint, Windows Drivers, GDI, and EMF, UNIX Printfile Conversion and GUI Basics
    xxxxBSD, Features and Benefits

    Y

    yppasswd, The smbpasswd Tool

    Z

    Zero Administration Kit, Windows NT4-Style Policy Files
    zero-based broadcast, Note about Broadcast Addresses
    Prev   
    Glossary Home 
    diff --git a/docs/htmldocs/Samba3-HOWTO/largefile.html b/docs/htmldocs/Samba3-HOWTO/largefile.html index e2831792c2..1d4dab0614 100644 --- a/docs/htmldocs/Samba3-HOWTO/largefile.html +++ b/docs/htmldocs/Samba3-HOWTO/largefile.html @@ -1,39 +1,39 @@ Chapter 33. Handling Large Directories
    Chapter 33. Handling Large Directories
    Prev Part III. Advanced Configuration Next

    Chapter 33. Handling Large Directories

    Jeremy Allison

    Samba Team

    John H. Terpstra

    Samba Team

    March 5, 2005

    - - - + + + Samba-3.0.12 and later implements a solution for sites that have experienced performance degradation due to the problem of using Samba-3 with applications that need large numbers of files (100,000 or more) per directory.

    - - + + The key was fixing the directory handling to read only the current list requested instead of the old (up to samba-3.0.11) behavior of reading the entire directory into memory before doling out names. Normally this would have broken OS/2 applications, which have very strange delete semantics, but by stealing logic from Samba4 (thanks, Tridge), the current code in 3.0.12 handles this correctly.

    - - + + To set up an application that needs large numbers of files per directory in a way that does not damage performance unduly, follow these steps:

    - + First, you need to canonicalize all the files in the directory to have one case, upper or lower take your pick (I chose upper because all my files were already uppercase names). Then set up a new custom share for the application as follows: -

    [bigshare]
    path = /data/manyfilesdir
    read only = no
    case sensitive = True
    default case = upper
    preserve case = no
    short preserve case = no

    +

    [bigshare]
    path = /data/manyfilesdir
    read only = no
    case sensitive = True
    default case = upper
    preserve case = no
    short preserve case = no

    - - - + + + Of course, use your own path and settings, but set the case options to match the case of all the files in your directory. The path should point at the large directory needed for the application any new files created in there and in any paths under it will be forced by smbd into uppercase, but smbd will no longer have to scan the directory for names: it knows that if a file does not exist in uppercase, then it doesn't exist at all.

    - - - + + + The secret to this is really in the case sensitive = True line. This tells smbd never to scan for case-insensitive versions of names. So if an application asks for a file called FOO, and it cannot be found by a simple stat call, then smbd will return file not @@ -41,9 +41,9 @@ found immediately without scanning the containing directory for a version of a d xxx case xxx lines make this work by forcing a consistent case on all files created by smbd.

    - - - + + + Remember, all files and directories under the path directory must be in uppercase with this smb.conf stanza because smbd will not be able to find lowercase filenames with these settings. Also note that this is done on a per-share basis, allowing this parameter to be set only for a share servicing an application with diff --git a/docs/htmldocs/Samba3-HOWTO/locking.html b/docs/htmldocs/Samba3-HOWTO/locking.html index 1a91cf5037..6d7bf3a225 100644 --- a/docs/htmldocs/Samba3-HOWTO/locking.html +++ b/docs/htmldocs/Samba3-HOWTO/locking.html @@ -1,19 +1,19 @@ -Chapter 17. File and Record Locking

    Chapter 17. File and Record Locking
    Prev Part III. Advanced Configuration Next

    Chapter 17. File and Record Locking

    Jeremy Allison

    Samba Team

    Jelmer R. Vernooij

    The Samba Team

    John H. Terpstra

    Samba Team

    Eric Roseme

    HP Oplocks Usage Recommendations Whitepaper

    Table of Contents

    Features and Benefits
    Discussion
    Opportunistic Locking Overview
    Samba Oplocks Control
    Example Configuration
    MS Windows Oplocks and Caching Controls
    Workstation Service Entries
    Server Service Entries
    Persistent Data Corruption
    Common Errors
    locking.tdb Error Messages
    Problems Saving Files in MS Office on Windows XP
    Long Delays Deleting Files over Network with XP SP1
    Additional Reading

    - +Chapter 17. File and Record Locking

    Chapter 17. File and Record Locking
    Prev Part III. Advanced Configuration Next

    Chapter 17. File and Record Locking

    Jeremy Allison

    Samba Team

    Jelmer R. Vernooij

    The Samba Team

    John H. Terpstra

    Samba Team

    Eric Roseme

    HP Oplocks Usage Recommendations Whitepaper

    Table of Contents

    Features and Benefits
    Discussion
    Opportunistic Locking Overview
    Samba Oplocks Control
    Example Configuration
    MS Windows Oplocks and Caching Controls
    Workstation Service Entries
    Server Service Entries
    Persistent Data Corruption
    Common Errors
    locking.tdb Error Messages
    Problems Saving Files in MS Office on Windows XP
    Long Delays Deleting Files over Network with XP SP1
    Additional Reading

    + One area that causes trouble for many network administrators is locking. The extent of the problem is readily evident from searches over the Internet. -

    Features and Benefits

    - +

    Features and Benefits

    + Samba provides all the same locking semantics that MS Windows clients expect and that MS Windows NT4/200x servers also provide.

    - + The term locking has exceptionally broad meaning and covers a range of functions that are all categorized under this one term.

    - - - + + + Opportunistic locking is a desirable feature when it can enhance the perceived performance of applications on a networked client. However, the opportunistic locking protocol is not robust and therefore can @@ -23,27 +23,27 @@ system management of opportunistic locking and/or recovering from repetitive errors can offset the perceived performance advantage that it is intended to provide.

    - + The MS Windows network administrator needs to be aware that file and record locking semantics (behavior) can be controlled either in Samba or by way of registry settings on the MS Windows client.

    Note

    - + Sometimes it is necessary to disable locking control settings on the Samba server as well as on each MS Windows client! -

    Discussion

    - - +

    Discussion

    + + There are two types of locking that need to be performed by an SMB server. The first is record locking that allows a client to lock a range of bytes in an open file. The second is the deny modes that are specified when a file is open.

    - - - - - + + + + + Record locking semantics under UNIX are very different from record locking under Windows. Versions of Samba before 2.2 have tried to use the native fcntl() UNIX system call to implement proper record locking between different Samba clients. @@ -53,15 +53,15 @@ depending on the client OS. The UNIX locking only supports byte ranges up to 2^3 So it is not possible to correctly satisfy a lock request above 2^31. There are many more differences, too many to be listed here.

    - - + + Samba 2.2 and above implement record locking completely independently of the underlying UNIX system. If a byte-range lock that the client requests happens to fall into the range of 0 to 2^31, Samba hands this request down to the UNIX system. No other locks can be seen by UNIX, anyway.

    - - + + Strictly speaking, an SMB server should check for locks before every read and write call on a file. Unfortunately, with the way fcntl() works, this can be slow and may overstress the rpc.lockd. This is almost always unnecessary because clients are @@ -70,57 +70,57 @@ important to them. By default, Samba only makes locking calls when explicitly as to by a client, but if you set strict locking = yes, it will make lock checking calls on every read and write call.

    - + You can also disable byte-range locking completely by using locking = no. This is useful for those shares that do not support locking or do not need it (such as CD-ROMs). In this case, Samba fakes the return codes of locking calls to tell clients that everything is okay.

    - - - - - - - + + + + + + + The second class of locking is the deny modes. These are set by an application when it opens a file to determine what types of access should be allowed simultaneously with its open. A client may ask for DENY_NONE, DENY_READ, DENY_WRITE, or DENY_ALL. There are also special compatibility modes called DENY_FCB and DENY_DOS. -

    Opportunistic Locking Overview

    - - - +

    Opportunistic Locking Overview

    + + + Opportunistic locking (oplocks) is invoked by the Windows file system (as opposed to an API) via registry entries (on the server and the client) for the purpose of enhancing network performance when accessing a file residing on a server. Performance is enhanced by caching the file locally on the client that allows the following:

    Read-ahead:

    - + The client reads the local copy of the file, eliminating network latency.

    Write caching:

    - + The client writes to the local copy of the file, eliminating network latency.

    Lock caching:

    - + The client caches application locks locally, eliminating network latency.

    - - - + + + The performance enhancement of oplocks is due to the opportunity of exclusive access to the file even if it is opened with deny-none because Windows monitors the file's status for concurrent access from other processes.

    Windows Defines Four Kinds of Oplocks:

    Level1 Oplock

    - - - - + + + + The redirector sees that the file was opened with deny none (allowing concurrent access), verifies that no other process is accessing the file, checks that @@ -128,10 +128,10 @@ other processes. access to the file. The client now performs operations on the cached local file.

    - - - - + + + + If a second process attempts to open the file, the open is deferred while the redirector "breaks" the original oplock. The oplock break signals the caching client to @@ -145,31 +145,31 @@ other processes. second process is granted limited or no access, despite the oplock break.

    Level2 Oplock

    - - - + + + Performs like a Level1 oplock, except caching is only operative for reads. All other operations are performed on the server disk copy of the file.

    Filter Oplock

    - + Does not allow write or delete file access.

    Batch Oplock

    - + Manipulates file openings and closings and allows caching of file attributes.

    - + An important detail is that oplocks are invoked by the file system, not an application API. Therefore, an application can close an oplocked file, but the file system does not relinquish the oplock. When the oplock break is issued, the file system then simply closes the file in preparation for the subsequent open by the second process.

    - - + + Opportunistic locking is actually an improper name for this feature. The true benefit of this feature is client-side data caching, and oplocks is merely a notification mechanism for writing data back to the @@ -179,7 +179,7 @@ between the server and the caching client. If this exchange is faulty (usually due to timing out for any number of reasons), then the client-side caching benefit is negated.

    - + The actual decision that a user or administrator should consider is whether it is sensible to share among multiple users data that will be cached locally on a client. In many cases the answer is no. @@ -189,15 +189,15 @@ caching. Turn it “on” when client-side ca reliable. Turn it “off” when client-side caching is redundant, unreliable, or counterproductive.

    - + Oplocks is by default set to “on” by Samba on all configured shares, so careful attention should be given to each case to determine if the potential benefit is worth the potential for delays. The following recommendations will help to characterize the environment where oplocks may be effectively configured.

    - - + + Windows oplocks is a lightweight performance-enhancing feature. It is not a robust and reliable protocol. Every implementation of oplocks should be evaluated as a @@ -208,7 +208,7 @@ South Pacific atoll, on a high-availability server, serving a mission-critical multiuser corporate database during a tropical storm. This configuration will likely encounter problems with oplocks.

    - + Oplocks can be beneficial to perceived client performance when treated as a configuration toggle for client-side data caching. If the data caching is likely to be interrupted, then oplock usage should be @@ -222,8 +222,8 @@ to ensure that if a client loses connectivity with a file server, a failover replacement will be available immediately to provide continuous data availability.

    - - + + Windows client failover behavior is more at risk of application interruption than other platforms because it is dependent upon an established TCP transport connection. If the connection is interrupted @@ -233,9 +233,9 @@ correctly from a transport connection loss; therefore, most applications will experience some sort of interruption at worst, abort and require restarting.

    - - - + + + If a client session has been caching writes and reads locally due to oplocks, it is likely that the data will be lost when the application restarts or recovers from the TCP interrupt. When the TCP @@ -250,7 +250,7 @@ In mission-critical, high-availability environments, careful attention should be given to oplocks. Ideally, comprehensive testing should be done with all affected applications with oplocks enabled and disabled. -

    Exclusively Accessed Shares

    +

    Exclusively Accessed Shares

    Oplocks is most effective when it is confined to shares that are exclusively accessed by a single user, or by only one user at a time. Because the true value of oplocks is the local @@ -259,7 +259,7 @@ mechanism will cause a delay.

    Home directories are the most obvious examples of where the performance benefit of oplocks can be safely realized. -

    Multiple-Accessed Shares or Files

    +

    Multiple-Accessed Shares or Files

    As each additional user accesses a file in a share with oplocks enabled, the potential for delays and resulting perceived poor performance increases. When multiple users are accessing a file on a @@ -271,9 +271,9 @@ of the caching user. As each additional client attempts to access a file with oplocks set, the potential performance improvement is negated and eventually results in a performance bottleneck. -

    UNIX or NFS Client-Accessed Files

    - - +

    UNIX or NFS Client-Accessed Files

    + + Local UNIX and NFS clients access files without a mandatory file-locking mechanism. Thus, these client platforms are incapable of initiating an oplock break request from the server to a Windows client @@ -283,10 +283,10 @@ exposes the file to likely data corruption.

    If files are shared between Windows clients and either local UNIX or NFS users, turn oplocks off. -

    Slow and/or Unreliable Networks

    - - - +

    Slow and/or Unreliable Networks

    + + + The biggest potential performance improvement for oplocks occurs when the client-side caching of reads and writes delivers the most differential over sending those reads and writes over the wire. @@ -301,20 +301,20 @@ the most advantageous scenario in which to utilize oplocks. If the network is slow, unreliable, or a WAN, then do not configure oplocks if there is any chance of multiple users regularly opening the same file. -

    Multiuser Databases

    - - - +

    Multiuser Databases

    + + + Multiuser databases clearly pose a risk due to their very nature they are typically heavily accessed by numerous users at random intervals. Placing a multiuser database on a share with oplocks enabled will likely result in a locking management bottleneck on the Samba server. Whether the database application is developed in-house or a commercially available product, ensure that the share has oplocks disabled. -

    PDM Data Shares

    - - - - - +

    PDM Data Shares

    + + + + + Process data management (PDM) applications such as IMAN, Enovia, and Clearcase are increasing in usage with Windows client platforms and therefore with SMB datastores. PDM applications manage multiuser environments for critical data security and access. The typical PDM environment is usually associated with sophisticated client @@ -322,8 +322,8 @@ design applications that will load data locally as demanded. In addition, the PD monitor the data state of each client. In this case, client-side data caching is best left to the local application and PDM server to negotiate and maintain. It is appropriate to eliminate the client OS from any caching tasks, and the server from any oplocks management, by disabling oplocks on the share. -

    Beware of Force User

    - +

    Beware of Force User

    + Samba includes an smb.conf parameter called force user that changes the user accessing a share from the incoming user to whatever user is defined by the smb.conf variable. If oplocks is enabled on a share, the change in user access causes an oplock break to be sent to the client, even if the @@ -338,10 +338,10 @@ Avoid the combination of the following: Slow or unreliable networks.

  • Oplocks enabled. -

    • Advanced Samba Oplocks Parameters

    - - - +

    Advanced Samba Oplocks Parameters

    + + + Samba provides oplock parameters that allow the administrator to adjust various properties of the oplock mechanism to account for timing and usage levels. These parameters provide good @@ -350,13 +350,13 @@ likely cause problems. The parameters are oplock break wait time, and oplock contention limit.

    - + For most users, administrators, and environments, if these parameters are required, then the better option is simply to turn oplocks off. The Samba SWAT help text for both parameters reads: “Do not change this parameter unless you have read and understood the Samba oplock code.” This is good advice. -

    Mission-Critical, High-Availability

    +

    Mission-Critical, High-Availability

    In mission-critical, high-availability environments, data integrity is often a priority. Complex and expensive configurations are implemented to ensure that if a client loses connectivity with a file server, a @@ -386,7 +386,7 @@ In mission-critical, high-availability environments, careful attention should be given to oplocks. Ideally, comprehensive testing should be done with all affected applications with oplocks enabled and disabled. -

    Samba Oplocks Control

    +

    Samba Oplocks Control

    Oplocks is a unique Windows file locking feature. It is not really file locking, but is included in most discussions of Windows file locking, so is considered a de facto locking feature. @@ -436,23 +436,23 @@ of your client sending oplock breaks and will instead want to disable oplocks fo

    Another factor to consider is the perceived performance of file access. If oplocks provide no measurable speed benefit on your network, it might not be worth the hassle of dealing with them. -

    Example Configuration

    +

    Example Configuration

    In the following section we examine two distinct aspects of Samba locking controls. -

    Disabling Oplocks

    +

    Disabling Oplocks

    You can disable oplocks on a per-share basis with the following:

    -

    [acctdata]
    oplocks = False
    level2 oplocks = False

    +

    [acctdata]
    oplocks = False
    level2 oplocks = False

    The default oplock type is Level1. Level2 oplocks are enabled on a per-share basis in the smb.conf file.

    Alternately, you could disable oplocks on a per-file basis within the share:

    -

    veto oplock files = /*.mdb/*.MDB/*.dbf/*.DBF/

    +

    veto oplock files = /*.mdb/*.MDB/*.dbf/*.DBF/

    If you are experiencing problems with oplocks, as apparent from Samba's log entries, you may want to play it safe and disable oplocks and Level2 oplocks. -

    Disabling Kernel Oplocks

    +

    Disabling Kernel Oplocks

    Kernel oplocks is an smb.conf parameter that notifies Samba (if the UNIX kernel has the capability to send a Windows client an oplock break) when a UNIX process is attempting to open the file that is @@ -465,7 +465,7 @@ send an oplock break, then the kernel oplocks parameter enables Samba to send the oplock break. Kernel oplocks are enabled on a per-server basis in the smb.conf file.

    -

    kernel oplocks = yes

    +

    kernel oplocks = yes

    The default is no.

    Veto oplocks is an smb.conf parameter that identifies specific files for @@ -480,14 +480,14 @@ caching without the risk of data corruption. Veto oplocks can be enabled on a per-share basis, or globally for the entire server, in the smb.conf file as shown in “Share with Some Files Oplocked”.

    -

    Example 17.1. Share with Some Files Oplocked

    [global]
    veto oplock files = /filename.htm/*.txt/
    [share_name]
    veto oplock files = /*.exe/filename.ext/


    +

    Example 17.1. Share with Some Files Oplocked

    [global]
    veto oplock files = /filename.htm/*.txt/
    [share_name]
    veto oplock files = /*.exe/filename.ext/


    oplock break wait time is an smb.conf parameter that adjusts the time interval for Samba to reply to an oplock break request. Samba recommends: “Do not change this parameter unless you have read and understood the Samba oplock code.” Oplock break wait time can only be configured globally in the smb.conf file as shown:

    -

    oplock break wait time = 0 (default)

    +

    oplock break wait time = 0 (default)

    Oplock break contention limit is an smb.conf parameter that limits the response of the Samba server to grant an oplock if the configured @@ -496,8 +496,8 @@ number of contending clients reaches the limit specified by the parameter. Samba Oplock break contention limit can be enabled on a per-share basis, or globally for the entire server, in the smb.conf file as shown in “Configuration with Oplock Break Contention Limit”.

    -

    Example 17.2. Configuration with Oplock Break Contention Limit

    [global]
    oplock break contention limit = 2 (default)
    [share_name]
    oplock break contention limit = 2 (default)


    -

    MS Windows Oplocks and Caching Controls

    +

    Example 17.2. Configuration with Oplock Break Contention Limit

    [global]
    oplock break contention limit = 2 (default)
    [share_name]
    oplock break contention limit = 2 (default)


    +

    MS Windows Oplocks and Caching Controls

    There is a known issue when running applications (like Norton Antivirus) on a Windows 2000/ XP workstation computer that can affect any application attempting to access shared database files across a network. This is a result of a default setting configured in the Windows 2000/XP @@ -512,7 +512,7 @@ All Windows operating systems in the NT family that act as database servers for (meaning that data files are stored there and accessed by other Windows PCs) may need to have oplocks disabled in order to minimize the risk of data file corruption. This includes Windows 9x/Me, Windows NT, Windows 200x, and Windows XP. -[5] +[5]

    If you are using a Windows NT family workstation in place of a server, you must also disable oplocks on that workstation. For example, if you use a @@ -590,7 +590,7 @@ An illustration of how Level2 oplocks work follows: station holds any oplock on the file. Because the workstations can have no cached writes or locks at this point, they need not respond to the break-to-none advisory; all they need do is invalidate locally cashed read-ahead data. -

    Workstation Service Entries

    +

    Workstation Service Entries

     	\HKEY_LOCAL_MACHINE\System\
 		CurrentControlSet\Services\LanmanWorkstation\Parameters
 
@@ -599,7 +599,7 @@ An illustration of how Level2 oplocks work follows:

    This indicates whether the redirector should use oplocks performance enhancement. This parameter should be disabled only to isolate problems. -

    Server Service Entries

    +

    Server Service Entries

     	\HKEY_LOCAL_MACHINE\System\
 		CurrentControlSet\Services\LanmanServer\Parameters
 
@@ -628,7 +628,7 @@ the server disables raw I/O and oplocks for this connection.
 This specifies the time that the server waits for a client to respond to an oplock break
 request. Smaller values can allow detection of crashed clients more quickly but can
 potentially cause loss of cached data.
-

    Persistent Data Corruption

    +

    Persistent Data Corruption

    If you have applied all of the settings discussed in this chapter but data corruption problems and other symptoms persist, here are some additional things to check out.

    @@ -639,7 +639,7 @@ rebuild the data files in question. This involves creating a new data file with same definition as the file to be rebuilt and transferring the data from the old file to the new one. There are several known methods for doing this that can be found in our knowledge base. -

    Common Errors

    +

    Common Errors

    In some sites locking problems surface as soon as a server is installed; in other sites locking problems may not surface for a long time. Almost without exception, when a locking problem does surface, it will cause embarrassment and potential data corruption. @@ -669,7 +669,7 @@ so far: report on Samba Bugzilla without delay. Make sure that you give as much information as you possibly can to help isolate the cause and to allow replication of the problem (an essential step in problem isolation and correction). -

    locking.tdb Error Messages

    +

    locking.tdb Error Messages

    “ We are seeing lots of errors in the Samba logs, like: ” @@ -683,29 +683,29 @@ tdb(/usr/local/samba_2.2.7/var/locks/locking.tdb): rec_read bad magic ”

    This error indicates a corrupted tdb. Stop all instances of smbd, delete locking.tdb, and restart smbd. -

    Problems Saving Files in MS Office on Windows XP

    This is a bug in Windows XP. More information can be +

    Problems Saving Files in MS Office on Windows XP

    This is a bug in Windows XP. More information can be found in Microsoft Knowledge Base article 812937

    . -

    Long Delays Deleting Files over Network with XP SP1

    “It sometimes takes approximately 35 seconds to delete files over the network after XP SP1 has been applied.”

    This is a bug in Windows XP. More information can be found in +

    Long Delays Deleting Files over Network with XP SP1

    “It sometimes takes approximately 35 seconds to delete files over the network after XP SP1 has been applied.”

    This is a bug in Windows XP. More information can be found in Microsoft Knowledge Base article 811492

    . -

    Additional Reading

    +

    Additional Reading

    You may want to check for an updated documentation regarding file and record locking issues on the Microsoft Support web site. Additionally, search for the word locking on the Samba web site.

    Section of the Microsoft MSDN Library on opportunistic locking:

    - + Microsoft Knowledge Base, “Maintaining Transactional Integrity with OPLOCKS”, Microsoft Corporation, April 1999, Microsoft KB Article 224992.

    - + Microsoft Knowledge Base, “Configuring Opportunistic Locking in Windows 2000”, Microsoft Corporation, April 2001 Microsoft KB Article 296264.

    - + Microsoft Knowledge Base, “PC Ext: Explanation of Opportunistic Locking on Windows NT”, Microsoft Corporation, April 1995 Microsoft KB Article 129202. -


    [5] Microsoft has documented this in Knowledge Base article 300216.

    Prev Up Next
    Chapter 16. File, Directory, and Share Access Controls Home Chapter 18. Securing Samba
    +


    [5] Microsoft has documented this in Knowledge Base article 300216.

    Prev Up Next
    Chapter 16. File, Directory, and Share Access Controls Home Chapter 18. Securing Samba
    diff --git a/docs/htmldocs/Samba3-HOWTO/migration.html b/docs/htmldocs/Samba3-HOWTO/migration.html index f959f0f902..7047247f24 100644 --- a/docs/htmldocs/Samba3-HOWTO/migration.html +++ b/docs/htmldocs/Samba3-HOWTO/migration.html @@ -1 +1 @@ -Part IV. Migration and Updating
    Part IV. Migration and Updating
    Prev   Next

    Part IV. Migration and Updating

    Table of Contents

    35. Updating and Upgrading Samba
    Key Update Requirements
    Upgrading from Samba-3.0.x to Samba-3.2.0
    Upgrading from Samba-2.x to Samba-3.0.25
    Quick Migration Guide
    New Featuers in Samba-3.x Series
    New Features in Samba-3.2.x Series
    New Features in Samba-3.0.x
    New Functionality
    36. Migration from NT4 PDC to Samba-3 PDC
    Planning and Getting Started
    Objectives
    Steps in Migration Process
    Migration Options
    Planning for Success
    Samba-3 Implementation Choices
    37. SWAT: The Samba Web Administration Tool
    Features and Benefits
    Guidelines and Technical Tips
    Validate SWAT Installation
    Enabling SWAT for Use
    Securing SWAT through SSL
    Enabling SWAT Internationalization Support
    Overview and Quick Tour
    The SWAT Home Page
    Global Settings
    Share Settings
    Printers Settings
    The SWAT Wizard
    The Status Page
    The View Page
    The Password Change Page
    Prev   Next
    Chapter 34. Advanced Configuration Techniques Home Chapter 35. Updating and Upgrading Samba
    +Part IV. Migration and Updating
    Part IV. Migration and Updating
    Prev   Next

    Part IV. Migration and Updating

    Table of Contents

    35. Updating and Upgrading Samba
    Key Update Requirements
    Upgrading from Samba-3.0.x to Samba-3.2.0
    Upgrading from Samba-2.x to Samba-3.0.25
    Quick Migration Guide
    New Featuers in Samba-3.x Series
    New Features in Samba-3.2.x Series
    New Features in Samba-3.0.x
    New Functionality
    36. Migration from NT4 PDC to Samba-3 PDC
    Planning and Getting Started
    Objectives
    Steps in Migration Process
    Migration Options
    Planning for Success
    Samba-3 Implementation Choices
    37. SWAT: The Samba Web Administration Tool
    Features and Benefits
    Guidelines and Technical Tips
    Validate SWAT Installation
    Enabling SWAT for Use
    Securing SWAT through SSL
    Enabling SWAT Internationalization Support
    Overview and Quick Tour
    The SWAT Home Page
    Global Settings
    Share Settings
    Printers Settings
    The SWAT Wizard
    The Status Page
    The View Page
    The Password Change Page
    Prev   Next
    Chapter 34. Advanced Configuration Techniques Home Chapter 35. Updating and Upgrading Samba
    diff --git a/docs/htmldocs/Samba3-HOWTO/msdfs.html b/docs/htmldocs/Samba3-HOWTO/msdfs.html index aa34e1c8fa..8b18d6627b 100644 --- a/docs/htmldocs/Samba3-HOWTO/msdfs.html +++ b/docs/htmldocs/Samba3-HOWTO/msdfs.html @@ -1,94 +1,56 @@ -Chapter 20. Hosting a Microsoft Distributed File System Tree
    Chapter 20. Hosting a Microsoft Distributed File System Tree
    Prev Part III. Advanced Configuration Next

    Chapter 20. Hosting a Microsoft Distributed File System Tree

    Shirish Kalele

    Samba Team & Veritas Software


    -
    -

    John H. Terpstra

    Samba Team

    12 Jul 2000

    Table of Contents

    Features and Benefits
    Common Errors
    MSDFS UNIX Path Is Case-Critical

    Features and Benefits

    - - - - - - The distributed file system (DFS) provides a means of separating the logical - view of files and directories that users see from the actual physical locations - of these resources on the network. It allows for higher availability, smoother - storage expansion, load balancing, and so on. +Chapter 41. Managing TDB Files

    Chapter 41. Managing TDB Files
    Prev Part V. Troubleshooting Next

    Chapter 41. Managing TDB Files

    John H. Terpstra

    Samba Team

    May 28, 2008

    Table of Contents

    Features and Benefits
    Managing TDB Files

    Features and Benefits

    + + + Samba uses a lightweight database called Trivial Database (tdb) in which it stores persistent and transient data. + Some tdb files can be disposed of before restarting Samba, but others are used to store information that is vital + to Samba configuration and behavior. The following information is provided to help administrators who are seeking + to better manage their Samba installations.

    - - - - For information about DFS, refer to the Microsoft - documentation. This document explains how to host a DFS tree on a UNIX machine (for DFS-aware clients - to browse) using Samba. + + + + + Those who package Samba for commercial distribution with operating systems and appliances would do well to take + note that tdb files can get corrupted, and for this reason ought to be backed up regularly. An appropriate time + is at system shutdown (backup) and startup (restore from backup). +

    Table 41.1. Samba's Trivial Database Files

    File namePreserveDescription
    account_policy.tdbY

    NT account policy settings such as pw expiration, etc...

    brlock.tdbN

    Byte range locks.

    browse.datN

    Browse lists - gets rebuilt automatically.

    connections.tdbN

    Share connections. Used to enforce max connections, etc.

    gencache.tdbN

    Generic caching database.

    group_mapping.tdbY

    Stores group mapping information. Not used when using LDAP backend.

    lang_en.tdbY

    Stores language encoding information.

    locking.tdbN

    Stores share mode and oplock information.

    login_cache.tdbN

    Keeps a log of bad pw attempts.

    messages.tdbN

    Used to keep track of Samba internal messaging.

    netsamlogon_cache.tdbY

    + Cache of user net_info_3 struct from net_samlogon() + requests from domain member machines. +

    ntdrivers.tdbY

    Stores installed printer driver information.

    ntforms.tdbY

    Stores installed printer forms information.

    ntprinters.tdbY

    Stores installed printers information.

    printing directoryY

    Directory containing tdb per print queue of cached lpq output.

    registry.tdbY

    Windows registry skeleton (connect via regedit.exe).

    sessionid.tdbN

    Session information to support utmp = yes capabilities.

    share_info.tdbY

    Stores share-level ACL configuration settings. + Default ACL is Everyone - Full Control. +

    unexpected.tdbN

    + Unexpected packet queue needed to support windows clients that respond on a + different port that the originating reques. +

    winbindd_cache.tdbN

    Winbind's cache of user lists.

    winbindd_idmap.tdbY

    Winbind's local IDMAP database.

    wins.datN

    + WINS database iused only when wins support = yes + has been set. This gets rebuilt or updated at every restart. +

    wins.tdbY

    + The working permanent storage for all WINS data. This database is used only + when wins support = yes has been set in the smb.conf file. + Note: This retains all manually configured WINS entries. Manual setting can be done use the net utility. +

    secrets.tdbY

    + This tdb file stores internal settings such as the machine and the domain SID, secret passwords + that are used with LDAP, the machine secret token, etc. This is an essential file that is stored + in a secure area. Vendors locate this in various folders. Check smbd -b to + find its location on your system. +

    schannel_store.tdbY

    + This stores secure channel access token information used with SMB signing. +

    passdb.tdbY

    + This stores the Samba SAM account information when using a tdbsam password backend. +


    Managing TDB Files

    + The tdbbackup utility is a tool that may be used to backup samba tdb files. + This tool may also be used to verify the integrity of the tdb files prior to Samba startup or + during normal operation. If it finds file damage it will search for a prior backup the backup + file from which the damaged tdb file will be restored. The tdbbackup + utility can safely be run at any time. It was designed so that it can be used at any time to + validate the integrity of tdb files, even during Samba operation.

    - - - - - A Samba server can be made a DFS server by setting the global Boolean host msdfs - parameter in the smb.conf file. You designate a share as a DFS root using the share-level Boolean - msdfs root parameter. A DFS root directory on Samba hosts DFS links in the form of - symbolic links that point to other servers. For example, a symbolic link - junction->msdfs:storage1\share1 in the share directory acts as the DFS junction. When - DFS-aware clients attempt to access the junction link, they are redirected to the storage location (in this - case, \\storage1\share1). -

    - - - - - DFS trees on Samba work with all DFS-aware clients ranging from Windows 95 to 200x. - The following sample configuration shows how to setup a DFS tree on a Samba server. - In the /export/dfsroot directory, you set up your DFS links to - other servers on the network. -

    -root# cd /export/dfsroot
-root# chown root /export/dfsroot
-root# chmod 755 /export/dfsroot
-root# ln -s msdfs:storageA\\shareA linka
-root# ln -s msdfs:serverB\\share,serverC\\share linkb
+	It is recommended to backup all tdb files as part of the Samba start-up scripts on a Samba
+	server. The following command syntax can be used:
+	
    +myserver# > cd /var/lib/samba
+myserver@ > tdbbackup *.tdb
 
    
-
    Example 20.1. smb.conf with DFS Configured
     
    [global]
    netbios name = GANDALF
    host msdfs   = yes
     
    [dfs]
    path = /export/dfsroot
    msdfs root = yes

    
-
-
-
-	You should set up the permissions and ownership of the directory acting as the DFS root so that only
-	designated users can create, delete, or modify the msdfs links. Also note that symlink names should be all
-	lowercase. This limitation exists to have Samba avoid trying all the case combinations to get at the link
-	name. Finally, set up the symbolic links to point to the network shares you want and start Samba.
-	
    
-
-
-	Users on DFS-aware clients can now browse the DFS tree on the Samba server at
-	\\samba\dfs. Accessing links linka or linkb (which appear as directories to the client)
-	takes users directly to the appropriate shares on the network.
-

    Common Errors

    • Windows clients need to be rebooted - if a previously mounted non-DFS share is made a DFS - root, or vice versa. A better way is to introduce a - new share and make it the DFS root.

    • Currently, there's a restriction that msdfs - symlink names should all be lowercase.

    • For security purposes, the directory - acting as the root of the DFS tree should have ownership - and permissions set so only designated users can - modify the symbolic links in the directory.

    MSDFS UNIX Path Is Case-Critical

    - A network administrator sent advice to the Samba mailing list - after long sessions trying to determine why DFS was not working. - His advice is worth noting. -

    “ - I spent some time trying to figure out why my particular - DFS root wasn't working. I noted in the documentation that - the symlink should be in all lowercase. It should be - amended that the entire path to the symlink should all be - in lowercase as well. - ”

    - “For example, I had a share defined as such:” -

    [pub]
    path = /export/home/Shares/public_share
    msdfs root = yes

    - “and I could not make my Windows 9x/Me (with the dfs client installed) follow this symlink:” - 

    -		damage1 -> msdfs:damage\test-share
-

    -

    - “Running a debug level of 10 reveals:” - 

    -		[2003/08/20 11:40:33, 5] msdfs/msdfs.c:is_msdfs_link(176)
-		  is_msdfs_link: /export/home/shares/public_share/* does not exist.
-

    - “Curious. So I changed the directory name from .../Shares/... to - .../shares/... (along with my service definition) and it worked!” -

    Prev Up Next
    Chapter 19. Interdomain Trust Relationships Home Chapter 21. Classical Printing Support
    + The default extension is .bak. Any alternate extension can be specified + by executing tdbbackup -s 'new_extension' *.tdb as part of your startup script. +

    Prev Up Next
    Chapter 40. Reporting Bugs Home Part VI. Reference Section
    diff --git a/docs/htmldocs/Samba3-HOWTO/optional.html b/docs/htmldocs/Samba3-HOWTO/optional.html index c5a86a4400..5475cab6c2 100644 --- a/docs/htmldocs/Samba3-HOWTO/optional.html +++ b/docs/htmldocs/Samba3-HOWTO/optional.html @@ -1,7 +1,7 @@ -Part III. Advanced Configuration
    Part III. Advanced Configuration
    Prev   Next

    Part III. Advanced Configuration

    Valuable Nuts and Bolts Information

    +Part III. Advanced Configuration

    Part III. Advanced Configuration
    Prev   Next

    Part III. Advanced Configuration

    Valuable Nuts and Bolts Information

    Samba has several features that you might want or might not want to use. The chapters in this part each cover specific Samba features. -

    Table of Contents

    9. Important and Critical Change Notes for the Samba 3.x Series
    Important Samba-3.2.x Change Notes
    Important Samba-3.0.x Change Notes
    User and Group Changes
    Essential Group Mappings
    Passdb Changes
    Group Mapping Changes in Samba-3.0.23
    LDAP Changes in Samba-3.0.23
    10. Network Browsing
    Features and Benefits
    What Is Browsing?
    Discussion
    NetBIOS over TCP/IP
    TCP/IP without NetBIOS
    DNS and Active Directory
    How Browsing Functions
    Configuring Workgroup Browsing
    Domain Browsing Configuration
    Forcing Samba to Be the Master
    Making Samba the Domain Master
    Note about Broadcast Addresses
    Multiple Interfaces
    Use of the Remote Announce Parameter
    Use of the Remote Browse Sync Parameter
    WINS: The Windows Internetworking Name Server
    WINS Server Configuration
    WINS Replication
    Static WINS Entries
    Helpful Hints
    Windows Networking Protocols
    Name Resolution Order
    Technical Overview of Browsing
    Browsing Support in Samba
    Problem Resolution
    Cross-Subnet Browsing
    Common Errors
    Flushing the Samba NetBIOS Name Cache
    Server Resources Cannot Be Listed
    I Get an "Unable to browse the network" Error
    Browsing of Shares and Directories is Very Slow
    Invalid Cached Share References Affects Network Browsing
    11. Account Information Databases
    Features and Benefits
    Backward Compatibility Account Storage Systems
    New Account Storage Systems
    Technical Information
    Important Notes About Security
    Mapping User Identifiers between MS Windows and UNIX
    Mapping Common UIDs/GIDs on Distributed Machines
    Comments Regarding LDAP
    LDAP Directories and Windows Computer Accounts
    Account Management Tools
    The smbpasswd Tool
    The pdbedit Tool
    Password Backends
    Plaintext
    smbpasswd: Encrypted Password Database
    tdbsam
    ldapsam
    Common Errors
    Users Cannot Logon
    Configuration of auth methods
    12. Group Mapping: MS Windows and UNIX
    Features and Benefits
    Discussion
    Warning: User Private Group Problems
    Nested Groups: Adding Windows Domain Groups to Windows Local Groups
    Important Administrative Information
    Default Users, Groups, and Relative Identifiers
    Example Configuration
    Configuration Scripts
    Sample smb.conf Add Group Script
    Script to Configure Group Mapping
    Common Errors
    Adding Groups Fails
    Adding Domain Users to the Workstation Power Users Group
    13. Remote and Local Management: The Net Command
    Overview
    Administrative Tasks and Methods
    UNIX and Windows Group Management
    Adding, Renaming, or Deletion of Group Accounts
    Manipulating Group Memberships
    Nested Group Support
    UNIX and Windows User Management
    Adding User Accounts
    Deletion of User Accounts
    Managing User Accounts
    User Mapping
    Administering User Rights and Privileges
    Managing Trust Relationships
    Machine Trust Accounts
    Interdomain Trusts
    Managing Security Identifiers (SIDS)
    Share Management
    Creating, Editing, and Removing Shares
    Creating and Changing Share ACLs
    Share, Directory, and File Migration
    Printer Migration
    Controlling Open Files
    Session and Connection Management
    Printers and ADS
    Manipulating the Samba Cache
    Managing IDMAP UID/SID Mappings
    Creating an IDMAP Database Dump File
    Restoring the IDMAP Database Dump File
    Other Miscellaneous Operations
    14. Identity Mapping (IDMAP)
    Samba Server Deployment Types and IDMAP
    Standalone Samba Server
    Domain Member Server or Domain Member Client
    Primary Domain Controller
    Backup Domain Controller
    Examples of IDMAP Backend Usage
    Default Winbind TDB
    IDMAP_RID with Winbind
    IDMAP Storage in LDAP Using Winbind
    IDMAP and NSS Using LDAP from ADS with RFC2307bis Schema Extension
    15. User Rights and Privileges
    Rights Management Capabilities
    Using the “net rpc rights” Utility
    Description of Privileges
    Privileges Suppored by Windows 2000 Domain Controllers
    The Administrator Domain SID
    Common Errors
    What Rights and Privileges Will Permit Windows Client Administration?
    16. File, Directory, and Share Access Controls
    Features and Benefits
    File System Access Controls
    MS Windows NTFS Comparison with UNIX File Systems
    Managing Directories
    File and Directory Access Control
    Share Definition Access Controls
    User- and Group-Based Controls
    File and Directory Permissions-Based Controls
    Miscellaneous Controls
    Access Controls on Shares
    Share Permissions Management
    MS Windows Access Control Lists and UNIX Interoperability
    Managing UNIX Permissions Using NT Security Dialogs
    Viewing File Security on a Samba Share
    Viewing File Ownership
    Viewing File or Directory Permissions
    Modifying File or Directory Permissions
    Interaction with the Standard Samba “create mask” Parameters
    Interaction with the Standard Samba File Attribute Mapping
    Windows NT/200X ACLs and POSIX ACLs Limitations
    Common Errors
    Users Cannot Write to a Public Share
    File Operations Done as root with force user Set
    MS Word with Samba Changes Owner of File
    17. File and Record Locking
    Features and Benefits
    Discussion
    Opportunistic Locking Overview
    Samba Oplocks Control
    Example Configuration
    MS Windows Oplocks and Caching Controls
    Workstation Service Entries
    Server Service Entries
    Persistent Data Corruption
    Common Errors
    locking.tdb Error Messages
    Problems Saving Files in MS Office on Windows XP
    Long Delays Deleting Files over Network with XP SP1
    Additional Reading
    18. Securing Samba
    Introduction
    Features and Benefits
    Technical Discussion of Protective Measures and Issues
    Using Host-Based Protection
    User-Based Protection
    Using Interface Protection
    Using a Firewall
    Using IPC$ Share-Based Denials
    NTLMv2 Security
    Upgrading Samba
    Common Errors
    Smbclient Works on Localhost, but the Network Is Dead
    Why Can Users Access Other Users' Home Directories?
    19. Interdomain Trust Relationships
    Features and Benefits
    Trust Relationship Background
    Native MS Windows NT4 Trusts Configuration
    Creating an NT4 Domain Trust
    Completing an NT4 Domain Trust
    Interdomain Trust Facilities
    Configuring Samba NT-Style Domain Trusts
    Samba as the Trusted Domain
    Samba as the Trusting Domain
    NT4-Style Domain Trusts with Windows 2000
    Common Errors
    Browsing of Trusted Domain Fails
    Problems with LDAP ldapsam and Older Versions of smbldap-tools
    20. Hosting a Microsoft Distributed File System Tree
    Features and Benefits
    Common Errors
    MSDFS UNIX Path Is Case-Critical
    21. Classical Printing Support
    Features and Benefits
    Technical Introduction
    Client to Samba Print Job Processing
    Printing-Related Configuration Parameters
    Simple Print Configuration
    Verifying Configuration with testparm
    Rapid Configuration Validation
    Extended Printing Configuration
    Detailed Explanation Settings
    Printing Developments Since Samba-2.2
    Point'n'Print Client Drivers on Samba Servers
    The Obsoleted [printer$] Section
    Creating the [print$] Share
    [print$] Stanza Parameters
    The [print$] Share Directory
    Installing Drivers into [print$]
    Add Printer Wizard Driver Installation
    Installing Print Drivers Using rpcclient
    Client Driver Installation Procedure
    First Client Driver Installation
    Setting Device Modes on New Printers
    Additional Client Driver Installation
    Always Make First Client Connection as root or “printer admin”
    Other Gotchas
    Setting Default Print Options for Client Drivers
    Supporting Large Numbers of Printers
    Adding New Printers with the Windows NT APW
    Error Message: “Cannot connect under a different Name”
    Take Care When Assembling Driver Files
    Samba and Printer Ports
    Avoiding Common Client Driver Misconfiguration
    The Imprints Toolset
    What Is Imprints?
    Creating Printer Driver Packages
    The Imprints Server
    The Installation Client
    Adding Network Printers without User Interaction
    The addprinter Command
    Migration of Classical Printing to Samba
    Publishing Printer Information in Active Directory or LDAP
    Common Errors
    I Give My Root Password but I Do Not Get Access
    My Print Jobs Get Spooled into the Spooling Directory, but Then Get Lost
    22. CUPS Printing Support
    Introduction
    Features and Benefits
    Overview
    Basic CUPS Support Configuration
    Linking smbd with libcups.so
    Simple smb.conf Settings for CUPS
    More Complex CUPS smb.conf Settings
    Advanced Configuration
    Central Spooling vs. “Peer-to-Peer” Printing
    Raw Print Serving: Vendor Drivers on Windows Clients
    Installation of Windows Client Drivers
    Explicitly Enable “raw” Printing for application/octet-stream
    Driver Upload Methods
    Advanced Intelligent Printing with PostScript Driver Download
    GDI on Windows, PostScript on UNIX
    Windows Drivers, GDI, and EMF
    UNIX Printfile Conversion and GUI Basics
    PostScript and Ghostscript
    Ghostscript: The Software RIP for Non-PostScript Printers
    PostScript Printer Description (PPD) Specification
    Using Windows-Formatted Vendor PPDs
    CUPS Also Uses PPDs for Non-PostScript Printers
    The CUPS Filtering Architecture
    MIME Types and CUPS Filters
    MIME Type Conversion Rules
    Filtering Overview
    Prefilters
    pstops
    pstoraster
    imagetops and imagetoraster
    rasterto [printers specific]
    CUPS Backends
    The Role of cupsomatic/foomatic
    The Complete Picture
    mime.convs
    “Raw” Printing
    application/octet-stream Printing
    PostScript Printer Descriptions for Non-PostScript Printers
    cupsomatic/foomatic-rip Versus Native CUPS Printing
    Examples for Filtering Chains
    Sources of CUPS Drivers/PPDs
    Printing with Interface Scripts
    Network Printing (Purely Windows)
    From Windows Clients to an NT Print Server
    Driver Execution on the Client
    Driver Execution on the Server
    Network Printing (Windows Clients and UNIX/Samba Print -Servers)
    From Windows Clients to a CUPS/Samba Print Server
    Samba Receiving Job-Files and Passing Them to CUPS
    Network PostScript RIP
    PPDs for Non-PS Printers on UNIX
    PPDs for Non-PS Printers on Windows
    Windows Terminal Servers (WTS) as CUPS Clients
    Printer Drivers Running in “Kernel Mode” Cause Many -Problems
    Workarounds Impose Heavy Limitations
    CUPS: A “Magical Stone”?
    PostScript Drivers with No Major Problems, Even in Kernel -Mode
    Configuring CUPS for Driver Download
    cupsaddsmb: The Unknown Utility
    Prepare Your smb.conf for cupsaddsmb
    CUPS “PostScript Driver for Windows NT/200x/XP”
    Recognizing Different Driver Files
    Acquiring the Adobe Driver Files
    ESP Print Pro PostScript Driver for Windows NT/200x/XP
    Caveats to Be Considered
    Windows CUPS PostScript Driver Versus Adobe Driver
    Run cupsaddsmb (Quiet Mode)
    Run cupsaddsmb with Verbose Output
    Understanding cupsaddsmb
    How to Recognize If cupsaddsmb Completed Successfully
    cupsaddsmb with a Samba PDC
    cupsaddsmb Flowchart
    Installing the PostScript Driver on a Client
    Avoiding Critical PostScript Driver Settings on the Client
    Installing PostScript Driver Files Manually Using rpcclient
    A Check of the rpcclient man Page
    Understanding the rpcclient man Page
    Producing an Example by Querying a Windows Box
    Requirements for adddriver and setdriver to Succeed
    Manual Driver Installation in 15 Steps
    Troubleshooting Revisited
    The Printing *.tdb Files
    Trivial Database Files
    Binary Format
    Losing *.tdb Files
    Using tdbbackup
    CUPS Print Drivers from Linuxprinting.org
    foomatic-rip and Foomatic Explained
    foomatic-rip and Foomatic PPD Download and Installation
    Page Accounting with CUPS
    Setting Up Quotas
    Correct and Incorrect Accounting
    Adobe and CUPS PostScript Drivers for Windows Clients
    The page_log File Syntax
    Possible Shortcomings
    Future Developments
    Other Accounting Tools
    Additional Material
    Autodeletion or Preservation of CUPS Spool Files
    CUPS Configuration Settings Explained
    Preconditions
    Manual Configuration
    Printing from CUPS to Windows-Attached Printers
    More CUPS Filtering Chains
    Common Errors
    Windows 9x/Me Client Can't Install Driver
    “cupsaddsmb” Keeps Asking for Root Password in Never-ending Loop
    “cupsaddsmb” or “rpcclient addriver” Emit Error
    “cupsaddsmb” Errors
    Client Can't Connect to Samba Printer
    New Account Reconnection from Windows 200x/XP Troubles
    Avoid Being Connected to the Samba Server as the Wrong User
    Upgrading to CUPS Drivers from Adobe Drivers
    Can't Use “cupsaddsmb” on Samba Server, Which Is a PDC
    Deleted Windows 200x Printer Driver Is Still Shown
    Windows 200x/XP Local Security Policies
    Administrator Cannot Install Printers for All Local Users
    Print Change, Notify Functions on NT Clients
    Win XP-SP1
    Print Options for All Users Can't Be Set on Windows 200x/XP
    Most Common Blunders in Driver Settings on Windows Clients
    cupsaddsmb Does Not Work with Newly Installed Printer
    Permissions on /var/spool/samba/ Get Reset After Each Reboot
    Print Queue Called “lp” Mishandles Print Jobs
    Location of Adobe PostScript Driver Files for “cupsaddsmb”
    Overview of the CUPS Printing Processes
    23. Stackable VFS modules
    Features and Benefits
    Discussion
    Included Modules
    audit
    default_quota
    extd_audit
    fake_perms
    recycle
    netatalk
    shadow_copy
    VFS Modules Available Elsewhere
    DatabaseFS
    vscan
    vscan-clamav
    24. Winbind: Use of Domain Accounts
    Features and Benefits
    Introduction
    What Winbind Provides
    Target Uses
    Handling of Foreign SIDs
    How Winbind Works
    Microsoft Remote Procedure Calls
    Microsoft Active Directory Services
    Name Service Switch
    Pluggable Authentication Modules
    User and Group ID Allocation
    Result Caching
    Installation and Configuration
    Introduction
    Requirements
    Testing Things Out
    Conclusion
    Common Errors
    NSCD Problem Warning
    Winbind Is Not Resolving Users and Groups
    25. Advanced Network Management
    Features and Benefits
    Remote Server Administration
    Remote Desktop Management
    Remote Management from NoMachine.Com
    Remote Management with ThinLinc
    Network Logon Script Magic
    Adding Printers without User Intervention
    Limiting Logon Connections
    26. System and Account Policies
    Features and Benefits
    Creating and Managing System Policies
    Windows 9x/ME Policies
    Windows NT4-Style Policy Files
    MS Windows 200x/XP Professional Policies
    Managing Account/User Policies
    Management Tools
    Samba Editreg Toolset
    Windows NT4/200x
    Samba PDC
    System Startup and Logon Processing Overview
    Common Errors
    Policy Does Not Work
    27. Desktop Profile Management
    Features and Benefits
    Roaming Profiles
    Samba Configuration for Profile Handling
    Windows Client Profile Configuration Information
    User Profile Hive Cleanup Service
    Sharing Profiles between Windows 9x/Me and NT4/200x/XP Workstations
    Profile Migration from Windows NT4/200x Server to Samba
    Mandatory Profiles
    Creating and Managing Group Profiles
    Default Profile for Windows Users
    MS Windows 9x/Me
    MS Windows NT4 Workstation
    MS Windows 200x/XP
    Common Errors
    Configuring Roaming Profiles for a Few Users or Groups
    Cannot Use Roaming Profiles
    Changing the Default Profile
    Debugging Roaming Profiles and NT4-style Domain Policies
    28. PAM-Based Distributed Authentication
    Features and Benefits
    Technical Discussion
    PAM Configuration Syntax
    Example System Configurations
    smb.conf PAM Configuration
    Remote CIFS Authentication Using winbindd.so
    Password Synchronization Using pam_smbpass.so
    Common Errors
    pam_winbind Problem
    Winbind Is Not Resolving Users and Groups
    29. Integrating MS Windows Networks with Samba
    Features and Benefits
    Background Information
    Name Resolution in a Pure UNIX/Linux World
    /etc/hosts
    /etc/resolv.conf
    /etc/host.conf
    /etc/nsswitch.conf
    Name Resolution as Used within MS Windows Networking
    The NetBIOS Name Cache
    The LMHOSTS File
    HOSTS File
    DNS Lookup
    WINS Lookup
    Common Errors
    Pinging Works Only One Way
    Very Slow Network Connections
    Samba Server Name-Change Problem
    30. Unicode/Charsets
    Features and Benefits
    What Are Charsets and Unicode?
    Samba and Charsets
    Conversion from Old Names
    Japanese Charsets
    Basic Parameter Setting
    Individual Implementations
    Migration from Samba-2.2 Series
    Common Errors
    CP850.so Can't Be Found
    31. Backup Techniques
    Features and Benefits
    Discussion of Backup Solutions
    BackupPC
    Rsync
    Amanda
    BOBS: Browseable Online Backup System
    32. High Availability
    Features and Benefits
    Technical Discussion
    The Ultimate Goal
    Why Is This So Hard?
    A Simple Solution
    High-Availability Server Products
    MS-DFS: The Poor Man's Cluster
    Conclusions
    33. Handling Large Directories
    34. Advanced Configuration Techniques
    Implementation
    Multiple Server Hosting
    Multiple Virtual Server Personalities
    Multiple Virtual Server Hosting
    Prev   Next
    Chapter 8. MS Windows Network Configuration Guide Home Chapter 9. Important and Critical Change Notes for the Samba 3.x Series
    +

    Table of Contents

    9. Important and Critical Change Notes for the Samba 3.x Series
    Important Samba-3.2.x Change Notes
    Important Samba-3.0.x Change Notes
    User and Group Changes
    Essential Group Mappings
    Passdb Changes
    Group Mapping Changes in Samba-3.0.23
    LDAP Changes in Samba-3.0.23
    10. Network Browsing
    Features and Benefits
    What Is Browsing?
    Discussion
    NetBIOS over TCP/IP
    TCP/IP without NetBIOS
    DNS and Active Directory
    How Browsing Functions
    Configuring Workgroup Browsing
    Domain Browsing Configuration
    Forcing Samba to Be the Master
    Making Samba the Domain Master
    Note about Broadcast Addresses
    Multiple Interfaces
    Use of the Remote Announce Parameter
    Use of the Remote Browse Sync Parameter
    WINS: The Windows Internetworking Name Server
    WINS Server Configuration
    WINS Replication
    Static WINS Entries
    Helpful Hints
    Windows Networking Protocols
    Name Resolution Order
    Technical Overview of Browsing
    Browsing Support in Samba
    Problem Resolution
    Cross-Subnet Browsing
    Common Errors
    Flushing the Samba NetBIOS Name Cache
    Server Resources Cannot Be Listed
    I Get an "Unable to browse the network" Error
    Browsing of Shares and Directories is Very Slow
    Invalid Cached Share References Affects Network Browsing
    11. Account Information Databases
    Features and Benefits
    Backward Compatibility Account Storage Systems
    New Account Storage Systems
    Technical Information
    Important Notes About Security
    Mapping User Identifiers between MS Windows and UNIX
    Mapping Common UIDs/GIDs on Distributed Machines
    Comments Regarding LDAP
    LDAP Directories and Windows Computer Accounts
    Account Management Tools
    The smbpasswd Tool
    The pdbedit Tool
    Password Backends
    Plaintext
    smbpasswd: Encrypted Password Database
    tdbsam
    ldapsam
    Common Errors
    Users Cannot Logon
    Configuration of auth methods
    12. Group Mapping: MS Windows and UNIX
    Features and Benefits
    Discussion
    Warning: User Private Group Problems
    Nested Groups: Adding Windows Domain Groups to Windows Local Groups
    Important Administrative Information
    Default Users, Groups, and Relative Identifiers
    Example Configuration
    Configuration Scripts
    Sample smb.conf Add Group Script
    Script to Configure Group Mapping
    Common Errors
    Adding Groups Fails
    Adding Domain Users to the Workstation Power Users Group
    13. Remote and Local Management: The Net Command
    Overview
    Administrative Tasks and Methods
    UNIX and Windows Group Management
    Adding, Renaming, or Deletion of Group Accounts
    Manipulating Group Memberships
    Nested Group Support
    UNIX and Windows User Management
    Adding User Accounts
    Deletion of User Accounts
    Managing User Accounts
    User Mapping
    Administering User Rights and Privileges
    Managing Trust Relationships
    Machine Trust Accounts
    Interdomain Trusts
    Managing Security Identifiers (SIDS)
    Share Management
    Creating, Editing, and Removing Shares
    Creating and Changing Share ACLs
    Share, Directory, and File Migration
    Printer Migration
    Controlling Open Files
    Session and Connection Management
    Printers and ADS
    Manipulating the Samba Cache
    Managing IDMAP UID/SID Mappings
    Creating an IDMAP Database Dump File
    Restoring the IDMAP Database Dump File
    Other Miscellaneous Operations
    14. Identity Mapping (IDMAP)
    Samba Server Deployment Types and IDMAP
    Standalone Samba Server
    Domain Member Server or Domain Member Client
    Primary Domain Controller
    Backup Domain Controller
    Examples of IDMAP Backend Usage
    Default Winbind TDB
    IDMAP_RID with Winbind
    IDMAP Storage in LDAP Using Winbind
    IDMAP and NSS Using LDAP from ADS with RFC2307bis Schema Extension
    15. User Rights and Privileges
    Rights Management Capabilities
    Using the “net rpc rights” Utility
    Description of Privileges
    Privileges Suppored by Windows 2000 Domain Controllers
    The Administrator Domain SID
    Common Errors
    What Rights and Privileges Will Permit Windows Client Administration?
    16. File, Directory, and Share Access Controls
    Features and Benefits
    File System Access Controls
    MS Windows NTFS Comparison with UNIX File Systems
    Managing Directories
    File and Directory Access Control
    Share Definition Access Controls
    User- and Group-Based Controls
    File and Directory Permissions-Based Controls
    Miscellaneous Controls
    Access Controls on Shares
    Share Permissions Management
    MS Windows Access Control Lists and UNIX Interoperability
    Managing UNIX Permissions Using NT Security Dialogs
    Viewing File Security on a Samba Share
    Viewing File Ownership
    Viewing File or Directory Permissions
    Modifying File or Directory Permissions
    Interaction with the Standard Samba “create mask” Parameters
    Interaction with the Standard Samba File Attribute Mapping
    Windows NT/200X ACLs and POSIX ACLs Limitations
    Common Errors
    Users Cannot Write to a Public Share
    File Operations Done as root with force user Set
    MS Word with Samba Changes Owner of File
    17. File and Record Locking
    Features and Benefits
    Discussion
    Opportunistic Locking Overview
    Samba Oplocks Control
    Example Configuration
    MS Windows Oplocks and Caching Controls
    Workstation Service Entries
    Server Service Entries
    Persistent Data Corruption
    Common Errors
    locking.tdb Error Messages
    Problems Saving Files in MS Office on Windows XP
    Long Delays Deleting Files over Network with XP SP1
    Additional Reading
    18. Securing Samba
    Introduction
    Features and Benefits
    Technical Discussion of Protective Measures and Issues
    Using Host-Based Protection
    User-Based Protection
    Using Interface Protection
    Using a Firewall
    Using IPC$ Share-Based Denials
    NTLMv2 Security
    Upgrading Samba
    Common Errors
    Smbclient Works on Localhost, but the Network Is Dead
    Why Can Users Access Other Users' Home Directories?
    19. Interdomain Trust Relationships
    Features and Benefits
    Trust Relationship Background
    Native MS Windows NT4 Trusts Configuration
    Creating an NT4 Domain Trust
    Completing an NT4 Domain Trust
    Interdomain Trust Facilities
    Configuring Samba NT-Style Domain Trusts
    Samba as the Trusted Domain
    Samba as the Trusting Domain
    NT4-Style Domain Trusts with Windows 2000
    Common Errors
    Browsing of Trusted Domain Fails
    Problems with LDAP ldapsam and Older Versions of smbldap-tools
    20. Hosting a Microsoft Distributed File System Tree
    Features and Benefits
    Common Errors
    MSDFS UNIX Path Is Case-Critical
    21. Classical Printing Support
    Features and Benefits
    Technical Introduction
    Client to Samba Print Job Processing
    Printing-Related Configuration Parameters
    Simple Print Configuration
    Verifying Configuration with testparm
    Rapid Configuration Validation
    Extended Printing Configuration
    Detailed Explanation Settings
    Printing Developments Since Samba-2.2
    Point'n'Print Client Drivers on Samba Servers
    The Obsoleted [printer$] Section
    Creating the [print$] Share
    [print$] Stanza Parameters
    The [print$] Share Directory
    Installing Drivers into [print$]
    Add Printer Wizard Driver Installation
    Installing Print Drivers Using rpcclient
    Client Driver Installation Procedure
    First Client Driver Installation
    Setting Device Modes on New Printers
    Additional Client Driver Installation
    Always Make First Client Connection as root or “printer admin”
    Other Gotchas
    Setting Default Print Options for Client Drivers
    Supporting Large Numbers of Printers
    Adding New Printers with the Windows NT APW
    Error Message: “Cannot connect under a different Name”
    Take Care When Assembling Driver Files
    Samba and Printer Ports
    Avoiding Common Client Driver Misconfiguration
    The Imprints Toolset
    What Is Imprints?
    Creating Printer Driver Packages
    The Imprints Server
    The Installation Client
    Adding Network Printers without User Interaction
    The addprinter Command
    Migration of Classical Printing to Samba
    Publishing Printer Information in Active Directory or LDAP
    Common Errors
    I Give My Root Password but I Do Not Get Access
    My Print Jobs Get Spooled into the Spooling Directory, but Then Get Lost
    22. CUPS Printing Support
    Introduction
    Features and Benefits
    Overview
    Basic CUPS Support Configuration
    Linking smbd with libcups.so
    Simple smb.conf Settings for CUPS
    More Complex CUPS smb.conf Settings
    Advanced Configuration
    Central Spooling vs. “Peer-to-Peer” Printing
    Raw Print Serving: Vendor Drivers on Windows Clients
    Installation of Windows Client Drivers
    Explicitly Enable “raw” Printing for application/octet-stream
    Driver Upload Methods
    Advanced Intelligent Printing with PostScript Driver Download
    GDI on Windows, PostScript on UNIX
    Windows Drivers, GDI, and EMF
    UNIX Printfile Conversion and GUI Basics
    PostScript and Ghostscript
    Ghostscript: The Software RIP for Non-PostScript Printers
    PostScript Printer Description (PPD) Specification
    Using Windows-Formatted Vendor PPDs
    CUPS Also Uses PPDs for Non-PostScript Printers
    The CUPS Filtering Architecture
    MIME Types and CUPS Filters
    MIME Type Conversion Rules
    Filtering Overview
    Prefilters
    pstops
    pstoraster
    imagetops and imagetoraster
    rasterto [printers specific]
    CUPS Backends
    The Role of cupsomatic/foomatic
    The Complete Picture
    mime.convs
    “Raw” Printing
    application/octet-stream Printing
    PostScript Printer Descriptions for Non-PostScript Printers
    cupsomatic/foomatic-rip Versus Native CUPS Printing
    Examples for Filtering Chains
    Sources of CUPS Drivers/PPDs
    Printing with Interface Scripts
    Network Printing (Purely Windows)
    From Windows Clients to an NT Print Server
    Driver Execution on the Client
    Driver Execution on the Server
    Network Printing (Windows Clients and UNIX/Samba Print +Servers)
    From Windows Clients to a CUPS/Samba Print Server
    Samba Receiving Job-Files and Passing Them to CUPS
    Network PostScript RIP
    PPDs for Non-PS Printers on UNIX
    PPDs for Non-PS Printers on Windows
    Windows Terminal Servers (WTS) as CUPS Clients
    Printer Drivers Running in “Kernel Mode” Cause Many +Problems
    Workarounds Impose Heavy Limitations
    CUPS: A “Magical Stone”?
    PostScript Drivers with No Major Problems, Even in Kernel +Mode
    Configuring CUPS for Driver Download
    cupsaddsmb: The Unknown Utility
    Prepare Your smb.conf for cupsaddsmb
    CUPS “PostScript Driver for Windows NT/200x/XP”
    Recognizing Different Driver Files
    Acquiring the Adobe Driver Files
    ESP Print Pro PostScript Driver for Windows NT/200x/XP
    Caveats to Be Considered
    Windows CUPS PostScript Driver Versus Adobe Driver
    Run cupsaddsmb (Quiet Mode)
    Run cupsaddsmb with Verbose Output
    Understanding cupsaddsmb
    How to Recognize If cupsaddsmb Completed Successfully
    cupsaddsmb with a Samba PDC
    cupsaddsmb Flowchart
    Installing the PostScript Driver on a Client
    Avoiding Critical PostScript Driver Settings on the Client
    Installing PostScript Driver Files Manually Using rpcclient
    A Check of the rpcclient man Page
    Understanding the rpcclient man Page
    Producing an Example by Querying a Windows Box
    Requirements for adddriver and setdriver to Succeed
    Manual Driver Installation in 15 Steps
    Troubleshooting Revisited
    The Printing *.tdb Files
    Trivial Database Files
    Binary Format
    Losing *.tdb Files
    Using tdbbackup
    CUPS Print Drivers from Linuxprinting.org
    foomatic-rip and Foomatic Explained
    foomatic-rip and Foomatic PPD Download and Installation
    Page Accounting with CUPS
    Setting Up Quotas
    Correct and Incorrect Accounting
    Adobe and CUPS PostScript Drivers for Windows Clients
    The page_log File Syntax
    Possible Shortcomings
    Future Developments
    Other Accounting Tools
    Additional Material
    Autodeletion or Preservation of CUPS Spool Files
    CUPS Configuration Settings Explained
    Preconditions
    Manual Configuration
    Printing from CUPS to Windows-Attached Printers
    More CUPS Filtering Chains
    Common Errors
    Windows 9x/Me Client Can't Install Driver
    “cupsaddsmb” Keeps Asking for Root Password in Never-ending Loop
    “cupsaddsmb” or “rpcclient addriver” Emit Error
    “cupsaddsmb” Errors
    Client Can't Connect to Samba Printer
    New Account Reconnection from Windows 200x/XP Troubles
    Avoid Being Connected to the Samba Server as the Wrong User
    Upgrading to CUPS Drivers from Adobe Drivers
    Can't Use “cupsaddsmb” on Samba Server, Which Is a PDC
    Deleted Windows 200x Printer Driver Is Still Shown
    Windows 200x/XP Local Security Policies
    Administrator Cannot Install Printers for All Local Users
    Print Change, Notify Functions on NT Clients
    Windows XP SP1
    Print Options for All Users Can't Be Set on Windows 200x/XP
    Most Common Blunders in Driver Settings on Windows Clients
    cupsaddsmb Does Not Work with Newly Installed Printer
    Permissions on /var/spool/samba/ Get Reset After Each Reboot
    Print Queue Called “lp” Mishandles Print Jobs
    Location of Adobe PostScript Driver Files for “cupsaddsmb”
    Overview of the CUPS Printing Processes
    23. Stackable VFS modules
    Features and Benefits
    Discussion
    Included Modules
    audit
    default_quota
    extd_audit
    fake_perms
    recycle
    netatalk
    shadow_copy
    VFS Modules Available Elsewhere
    DatabaseFS
    vscan
    vscan-clamav
    24. Winbind: Use of Domain Accounts
    Features and Benefits
    Introduction
    What Winbind Provides
    Target Uses
    Handling of Foreign SIDs
    How Winbind Works
    Microsoft Remote Procedure Calls
    Microsoft Active Directory Services
    Name Service Switch
    Pluggable Authentication Modules
    User and Group ID Allocation
    Result Caching
    Installation and Configuration
    Introduction
    Requirements
    Testing Things Out
    Conclusion
    Common Errors
    NSCD Problem Warning
    Winbind Is Not Resolving Users and Groups
    25. Advanced Network Management
    Features and Benefits
    Remote Server Administration
    Remote Desktop Management
    Remote Management from NoMachine.Com
    Remote Management with ThinLinc
    Network Logon Script Magic
    Adding Printers without User Intervention
    Limiting Logon Connections
    26. System and Account Policies
    Features and Benefits
    Creating and Managing System Policies
    Windows 9x/ME Policies
    Windows NT4-Style Policy Files
    MS Windows 200x/XP Professional Policies
    Managing Account/User Policies
    Management Tools
    Samba Editreg Toolset
    Windows NT4/200x
    Samba PDC
    System Startup and Logon Processing Overview
    Common Errors
    Policy Does Not Work
    27. Desktop Profile Management
    Features and Benefits
    Roaming Profiles
    Samba Configuration for Profile Handling
    Windows Client Profile Configuration Information
    User Profile Hive Cleanup Service
    Sharing Profiles between Windows 9x/Me and NT4/200x/XP Workstations
    Profile Migration from Windows NT4/200x Server to Samba
    Mandatory Profiles
    Creating and Managing Group Profiles
    Default Profile for Windows Users
    MS Windows 9x/Me
    MS Windows NT4 Workstation
    MS Windows 200x/XP
    Common Errors
    Configuring Roaming Profiles for a Few Users or Groups
    Cannot Use Roaming Profiles
    Changing the Default Profile
    Debugging Roaming Profiles and NT4-style Domain Policies
    28. PAM-Based Distributed Authentication
    Features and Benefits
    Technical Discussion
    PAM Configuration Syntax
    Example System Configurations
    smb.conf PAM Configuration
    Remote CIFS Authentication Using winbindd.so
    Password Synchronization Using pam_smbpass.so
    Common Errors
    pam_winbind Problem
    Winbind Is Not Resolving Users and Groups
    29. Integrating MS Windows Networks with Samba
    Features and Benefits
    Background Information
    Name Resolution in a Pure UNIX/Linux World
    /etc/hosts
    /etc/resolv.conf
    /etc/host.conf
    /etc/nsswitch.conf
    Name Resolution as Used within MS Windows Networking
    The NetBIOS Name Cache
    The LMHOSTS File
    HOSTS File
    DNS Lookup
    WINS Lookup
    Common Errors
    Pinging Works Only One Way
    Very Slow Network Connections
    Samba Server Name-Change Problem
    30. Unicode/Charsets
    Features and Benefits
    What Are Charsets and Unicode?
    Samba and Charsets
    Conversion from Old Names
    Japanese Charsets
    Basic Parameter Setting
    Individual Implementations
    Migration from Samba-2.2 Series
    Common Errors
    CP850.so Can't Be Found
    31. Backup Techniques
    Features and Benefits
    Discussion of Backup Solutions
    BackupPC
    Rsync
    Amanda
    BOBS: Browseable Online Backup System
    32. High Availability
    Features and Benefits
    Technical Discussion
    The Ultimate Goal
    Why Is This So Hard?
    A Simple Solution
    High-Availability Server Products
    MS-DFS: The Poor Man's Cluster
    Conclusions
    33. Handling Large Directories
    34. Advanced Configuration Techniques
    Implementation
    Multiple Server Hosting
    Multiple Virtual Server Personalities
    Multiple Virtual Server Hosting
    Prev   Next
    Chapter 8. MS Windows Network Configuration Guide Home Chapter 9. Important and Critical Change Notes for the Samba 3.x Series
    diff --git a/docs/htmldocs/Samba3-HOWTO/pam.html b/docs/htmldocs/Samba3-HOWTO/pam.html index db64175152..824d95ee98 100644 --- a/docs/htmldocs/Samba3-HOWTO/pam.html +++ b/docs/htmldocs/Samba3-HOWTO/pam.html @@ -1,30 +1,30 @@ -Chapter 28. PAM-Based Distributed Authentication
    Chapter 28. PAM-Based Distributed Authentication
    Prev Part III. Advanced Configuration Next

    Chapter 28. PAM-Based Distributed Authentication

    John H. Terpstra

    Samba Team

    Stephen Langasek

    May 31, 2003

    Table of Contents

    Features and Benefits
    Technical Discussion
    PAM Configuration Syntax
    Example System Configurations
    smb.conf PAM Configuration
    Remote CIFS Authentication Using winbindd.so
    Password Synchronization Using pam_smbpass.so
    Common Errors
    pam_winbind Problem
    Winbind Is Not Resolving Users and Groups

    - - - - +Chapter 28. PAM-Based Distributed Authentication

    Chapter 28. PAM-Based Distributed Authentication
    Prev Part III. Advanced Configuration Next

    Chapter 28. PAM-Based Distributed Authentication

    John H. Terpstra

    Samba Team

    Stephen Langasek

    May 31, 2003

    Table of Contents

    Features and Benefits
    Technical Discussion
    PAM Configuration Syntax
    Example System Configurations
    smb.conf PAM Configuration
    Remote CIFS Authentication Using winbindd.so
    Password Synchronization Using pam_smbpass.so
    Common Errors
    pam_winbind Problem
    Winbind Is Not Resolving Users and Groups

    + + + + This chapter should help you to deploy Winbind-based authentication on any PAM-enabled UNIX/Linux system. Winbind can be used to enable user-level application access authentication from any MS Windows NT domain, MS Windows 200x Active Directory-based domain, or any Samba-based domain environment. It will also help you to configure PAM-based local host access controls that are appropriate to your Samba configuration.

    - - + + In addition to knowing how to configure Winbind into PAM, you will learn generic PAM management possibilities and in particular how to deploy tools like pam_smbpass.so to your advantage.

    Note

    The use of Winbind requires more than PAM configuration alone. Please refer to Winbind: Use of Domain Accounts, for further information regarding Winbind. -

    Features and Benefits

    - - - - - - - - +

    Features and Benefits

    + + + + + + + + A number of UNIX systems (e.g., Sun Solaris), as well as the xxxxBSD family and Linux, now utilize the Pluggable Authentication Modules (PAM) facility to provide all authentication, authorization, and resource control services. Prior to the introduction of PAM, a decision @@ -33,17 +33,17 @@ would require the provision of alternatives for all programs that provide securi Such a choice would involve provision of alternatives to programs such as login, passwd, chown, and so on.

    - - - - + + + + PAM provides a mechanism that disconnects these security programs from the underlying authentication/authorization infrastructure. PAM is configured by making appropriate modifications to one file, /etc/pam.conf (Solaris), or by editing individual control files that are located in /etc/pam.d.

    - - + + On PAM-enabled UNIX/Linux systems, it is an easy matter to configure the system to use any authentication backend so long as the appropriate dynamically loadable library modules are available for it. The backend may be local to the system or may be centralized on a @@ -51,94 +51,94 @@ remote server.

    PAM support modules are available for:

    /etc/passwd

    - - - - - - + + + + + + There are several PAM modules that interact with this standard UNIX user database. The most common are called pam_unix.so, pam_unix2.so, pam_pwdb.so and pam_userdb.so.

    Kerberos

    - - - - - + + + + + The pam_krb5.so module allows the use of any Kerberos-compliant server. This tool is used to access MIT Kerberos, Heimdal Kerberos, and potentially Microsoft Active Directory (if enabled).

    LDAP

    - - - - - - + + + + + + The pam_ldap.so module allows the use of any LDAP v2- or v3-compatible backend server. Commonly used LDAP backend servers include OpenLDAP v2.0 and v2.1, Sun ONE iDentity server, Novell eDirectory server, and Microsoft Active Directory.

    NetWare Bindery

    - - - - + + + + The pam_ncp_auth.so module allows authentication off any bindery-enabled NetWare Core Protocol-based server.

    SMB Password

    - - - + + + This module, called pam_smbpass.so, allows user authentication of the passdb backend that is configured in the Samba smb.conf file.

    SMB Server

    - - + + The pam_smb_auth.so module is the original MS Windows networking authentication tool. This module has been somewhat outdated by the Winbind module.

    Winbind

    - - - - + + + + The pam_winbind.so module allows Samba to obtain authentication from any MS Windows domain controller. It can just as easily be used to authenticate users for access to any PAM-enabled application.

    RADIUS

    - + There is a PAM RADIUS (Remote Access Dial-In User Service) authentication module. In most cases, administrators need to locate the source code for this tool and compile and install it themselves. RADIUS protocols are used by many routers and terminal servers.

    - - + + Of the modules listed, Samba provides the pam_smbpasswd.so and the pam_winbind.so modules alone.

    - - - - + + + + Once configured, these permit a remarkable level of flexibility in the location and use of distributed Samba domain controllers that can provide wide-area network bandwidth, efficient authentication services for PAM-capable systems. In effect, this allows the deployment of centrally managed and maintained distributed authentication from a single-user account database. -

    Technical Discussion

    - - - - +

    Technical Discussion

    + + + + PAM is designed to provide system administrators with a great deal of flexibility in configuration of the privilege-granting applications of their system. The local configuration of system security controlled by PAM is contained in one of two places: either the single system file /etc/pam.conf or the /etc/pam.d/ directory. -

    PAM Configuration Syntax

    - - +

    PAM Configuration Syntax

    + + In this section we discuss the correct syntax of and generic options respected by entries to these files. PAM-specific tokens in the configuration file are case insensitive. The module paths, however, are case sensitive, since they indicate a file's name and reflect the case dependence of typical file systems. The @@ -148,8 +148,8 @@ In addition to the lines described below, there are two special characters provi of the system administrator: comments are preceded by a “#” and extend to the next end-of-line; also, module specification lines may be extended with a “\”-escaped newline.

    - - + + If the PAM authentication module (loadable link library file) is located in the default location, then it is not necessary to specify the path. In the case of Linux, the default location is /lib/security. If the module @@ -157,12 +157,12 @@ is located outside the default, then the path must be specified as: 

     auth  required  /other_path/pam_strange_module.so

    -

    Anatomy of /etc/pam.d Entries

    +

    Anatomy of /etc/pam.d Entries

    The remaining information in this subsection was taken from the documentation of the Linux-PAM project. For more information on PAM, see the Official Linux-PAM home page.

    - + A general configuration line of the /etc/pam.conf file has the following form: 

     service-name   module-type   control-flag   module-path   args
@@ -172,9 +172,9 @@ We explain the meaning of each of these tokens. The second (and more recently ad
 way of configuring Linux-PAM is via the contents of the /etc/pam.d/ directory.
 Once we have explained the meaning of the tokens, we describe this method.
 
    service-name
    
-
-
-
+
+
+
 		The name of the service associated with this entry. Frequently, the service-name is the conventional
 		name of the given application  for example, ftpd, rlogind and
 		su, and so on.
@@ -186,28 +186,28 @@ Once we have explained the meaning of the tokens, we describe this method.
 		
    module-type
    
 		One of (currently) four types of module. The four types are as follows:
 		
    • 
-
-
+
+
 			auth: This module type provides two aspects of authenticating the user.
 			It establishes that the user is who he or she claims to be by instructing the application
 			to prompt the user for a password or other means of identification. Second, the module can
 			grant group membership (independently of the /etc/groups file)
 			or other privileges through its credential-granting properties.
 			
    • 
-
-
+
+
 			account: This module performs non-authentication-based account management.
 			It is typically used to restrict/permit access to a service based on the time of day, currently
 		 	available system resources (maximum number of users), or perhaps the location of the user 
 			login. For example, the “root” login may be permitted only on the console.
 			
    • 
-
+
 			session: Primarily, this module is associated with doing things that need
 			to be done for the user before and after he or she can be given service. Such things include logging
 			information concerning the opening and closing of some data exchange with a user, mounting
 			directories, and so on.
 			
    • 
-
+
 			password: This last module type is required for updating the authentication
 			token associated with the user. Typically, there is one module for each
 			“challenge/response” authentication (auth) module type.
@@ -221,10 +221,10 @@ Once we have explained the meaning of the tokens, we describe this method.
 		/etc/pam.conf file; earlier entries are executed before later ones.
 		As of Linux-PAM v0.60, this control-flag can be defined with one of two syntaxes.
 		
      
-
-
-
-
+
+
+
+
 		The simpler (and historical) syntax for the control-flag is a single keyword defined to indicate the
 		severity of concern associated with the success or failure of a specific module. There are four such
 		keywords: required, requisite,
@@ -350,13 +350,13 @@ user_name=“%u” and password=PASSWORD(R
 		Any line in one of the configuration files that is not formatted correctly will generally tend (erring on the
 		side of caution) to make the authentication process fail. A corresponding error is written to the system log files
 		with a call to syslog(3). 
-

    Example System Configurations

    +

    Example System Configurations

    The following is an example /etc/pam.d/login configuration file. This example had all options uncommented and is probably not usable because it stacks many conditions before allowing successful completion of the login process. Essentially, all conditions can be disabled by commenting them out, except the calls to pam_pwdb.so. -

    PAM: Original Login Config

    +

    PAM: Original Login Config

     #%PAM-1.0
 # The PAM configuration file for the “login” service
@@ -373,7 +373,7 @@ session      required    pam_pwdb.so
 # password   required    pam_cracklib.so retry=3
 password     required    pam_pwdb.so shadow md5

    -

    PAM: Login Using pam_smbpass

    +

    PAM: Login Using pam_smbpass

    PAM allows use of replaceable modules. Those available on a sample system include:

    $/bin/ls /lib/security 

    @@ -456,7 +456,7 @@ authentication to be configured in a single central file. The
 on the basis that it allows for easier administration. As with all issues in 
 life, though, every decision has trade-offs, so you may want to examine the 
 PAM documentation for further helpful information.
-

    smb.conf PAM Configuration

    +

    smb.conf PAM Configuration

    There is an option in smb.conf called obey pam restrictions. The following is from the online help for this option in SWAT:

    @@ -466,7 +466,7 @@ is to use PAM for clear-text authentication only and to ignore any account or se ignores PAM for authentication in the case of encrypt passwords = yes. The reason is that PAM modules cannot support the challenge/response authentication mechanism needed in the presence of SMB password encryption. -

    Default: obey pam restrictions = no

    Remote CIFS Authentication Using winbindd.so

    +

    Default: obey pam restrictions = no

    Remote CIFS Authentication Using winbindd.so

    All operating systems depend on the provision of user credentials acceptable to the platform. UNIX requires the provision of a user identifier (UID) as well as a group identifier (GID). These are both simple integer numbers that are obtained from a password backend such @@ -493,7 +493,7 @@ the reduction of wide-area network authentication traffic. The RID to UNIX ID database is the only location where the user and group mappings are stored by winbindd. If this file is deleted or corrupted, there is no way for winbindd to determine which user and group IDs correspond to Windows NT user and group RIDs. -

    Password Synchronization Using pam_smbpass.so

    +

    Password Synchronization Using pam_smbpass.so

    pam_smbpass is a PAM module that can be used on conforming systems to keep the smbpasswd (Samba password) database in sync with the UNIX password file. PAM is an API supported @@ -511,7 +511,7 @@ Options recognized by this module are shown in pam_smbpass.so in the format of the Linux /etc/pam.d/ files structure. Those wishing to implement this tool on other platforms will need to adapt this appropriately. -

    Password Synchronization Configuration

    +

    Password Synchronization Configuration

    The following is a sample PAM configuration that shows the use of pam_smbpass to make sure private/smbpasswd is kept in sync when /etc/passwd (/etc/shadow) is changed. It is useful when an expired password might be changed by an @@ -528,7 +528,7 @@ password requisite pam_cracklib.so retry=3 password requisite pam_unix.so shadow md5 use_authtok try_first_pass password required pam_smbpass.so nullok use_authtok try_first_pass session required pam_unix.so -

    Password Migration Configuration

    +

    Password Migration Configuration

    The following PAM configuration shows the use of pam_smbpass to migrate from plaintext to encrypted passwords for Samba. Unlike other methods, this can be used for users who have never connected to Samba shares: @@ -548,7 +548,7 @@ password requisite pam_cracklib.so retry=3 password requisite pam_unix.so shadow md5 use_authtok try_first_pass password optional pam_smbpass.so nullok use_authtok try_first_pass session required pam_unix.so -

    Mature Password Configuration

    +

    Mature Password Configuration

    The following is a sample PAM configuration for a mature smbpasswd installation. private/smbpasswd is fully populated, and we consider it an error if the SMB password does not exist or does not match the UNIX password. @@ -564,7 +564,7 @@ password requisite pam_cracklib.so retry=3 password requisite pam_unix.so shadow md5 use_authtok try_first_pass password required pam_smbpass.so use_authtok use_first_pass session required pam_unix.so -

    Kerberos Password Integration Configuration

    +

    Kerberos Password Integration Configuration

    The following is a sample PAM configuration that shows pam_smbpass used together with pam_krb5. This could be useful on a Samba PDC that is also a member of a Kerberos realm. @@ -581,10 +581,10 @@ password requisite pam_cracklib.so retry=3 password optional pam_smbpass.so nullok use_authtok try_first_pass password required pam_krb5.so use_authtok try_first_pass session required pam_krb5.so -

    Common Errors

    +

    Common Errors

    PAM can be fickle and sensitive to configuration glitches. Here we look at a few cases from the Samba mailing list. -

    pam_winbind Problem

    +

    pam_winbind Problem

    A user reported, I have the following PAM configuration: 

    @@ -608,7 +608,7 @@ password required /lib/security/pam_stack.so service=system-auth
 	/etc/pam.d/system-auth and copy only what you need from it into your
 	/etc/pam.d/login file. Alternatively, if you want all services to use
 	Winbind, you can put the Winbind-specific stuff in /etc/pam.d/system-auth.
-

    Winbind Is Not Resolving Users and Groups

    +

    Winbind Is Not Resolving Users and Groups

    “ My smb.conf file is correctly configured. I have specified idmap uid = 12000 diff --git a/docs/htmldocs/Samba3-HOWTO/passdb.html b/docs/htmldocs/Samba3-HOWTO/passdb.html index 42af0a81d0..b9b5e7d872 100644 --- a/docs/htmldocs/Samba3-HOWTO/passdb.html +++ b/docs/htmldocs/Samba3-HOWTO/passdb.html @@ -1,18 +1,18 @@ -Chapter 11. Account Information Databases

    Chapter 11. Account Information Databases
    Prev Part III. Advanced Configuration Next

    Chapter 11. Account Information Databases

    Jelmer R. Vernooij

    The Samba Team

    John H. Terpstra

    Samba Team

    Gerald (Jerry) Carter

    Samba Team

    Jeremy Allison

    Samba Team

    Guenther Deschner

    LDAP updates 
    SuSE

    Olivier (lem) Lemaire

    IDEALX

    May 24, 2003

    Table of Contents

    Features and Benefits
    Backward Compatibility Account Storage Systems
    New Account Storage Systems
    Technical Information
    Important Notes About Security
    Mapping User Identifiers between MS Windows and UNIX
    Mapping Common UIDs/GIDs on Distributed Machines
    Comments Regarding LDAP
    LDAP Directories and Windows Computer Accounts
    Account Management Tools
    The smbpasswd Tool
    The pdbedit Tool
    Password Backends
    Plaintext
    smbpasswd: Encrypted Password Database
    tdbsam
    ldapsam
    Common Errors
    Users Cannot Logon
    Configuration of auth methods

    - - +Chapter 11. Account Information Databases

    Chapter 11. Account Information Databases
    Prev Part III. Advanced Configuration Next

    Chapter 11. Account Information Databases

    Jelmer R. Vernooij

    The Samba Team

    John H. Terpstra

    Samba Team

    Gerald (Jerry) Carter

    Samba Team

    Jeremy Allison

    Samba Team

    Guenther Deschner

    LDAP updates 
    SuSE

    Olivier (lem) Lemaire

    IDEALX

    May 24, 2003

    Table of Contents

    Features and Benefits
    Backward Compatibility Account Storage Systems
    New Account Storage Systems
    Technical Information
    Important Notes About Security
    Mapping User Identifiers between MS Windows and UNIX
    Mapping Common UIDs/GIDs on Distributed Machines
    Comments Regarding LDAP
    LDAP Directories and Windows Computer Accounts
    Account Management Tools
    The smbpasswd Tool
    The pdbedit Tool
    Password Backends
    Plaintext
    smbpasswd: Encrypted Password Database
    tdbsam
    ldapsam
    Common Errors
    Users Cannot Logon
    Configuration of auth methods

    + + Early releases of Samba-3 implemented new capability to work concurrently with multiple account backends. This capability was removed beginning with release of Samba 3.0.23. Commencing with Samba 3.0.23 it is possible to work with only one specified passwd backend.

    - - + + The three passdb backends that are fully maintained (actively supported) by the Samba Team are: smbpasswd (being obsoleted), tdbsam (a tdb-based binary file format), and ldapsam (LDAP directory). Of these, only the ldapsam backend @@ -23,30 +23,30 @@ In a strict sense, there are three supported account storage and access systems. obsolete (smbpasswd). It is recommended to use the tdbsam method for all simple systems. Use ldapsam for larger and more complex networks.

    - - - + + + In a strict and literal sense, the passdb backends are account storage mechanisms (or methods) alone. The choice of terminology can be misleading, however we are stuck with this choice of wording. This chapter documents the nature of the account storage system with a focus on user and trust accounts. Trust accounts have two forms, machine trust accounts (computer accounts) and interdomain trust accounts. These are all treated as user-like entities. -

    Features and Benefits

    +

    Features and Benefits

    Samba-3 provides for complete backward compatibility with Samba-2.2.x functionality as follows: - - - -

    Backward Compatibility Account Storage Systems

    Plaintext

    - - + + + +

    Backward Compatibility Account Storage Systems

    Plaintext

    + + This isn't really a backend at all, but is listed here for simplicity. Samba can be configured to pass plaintext authentication requests to the traditional UNIX/Linux /etc/passwd and /etc/shadow-style subsystems. On systems that have Pluggable Authentication Modules @@ -54,10 +54,10 @@ as follows: protocol limitations imposed by MS Windows clients apply likewise. Please refer to Technical Information, for more information regarding the limitations of plaintext password usage.

    smbpasswd

    - - + + This option allows continued use of the smbpasswd file that maintains a plain ASCII (text) layout that includes the MS Windows LanMan and NT-encrypted passwords as well as a field that stores some @@ -69,32 +69,32 @@ as follows: This backend should be used only for backward compatibility with older versions of Samba. It may be deprecated in future releases.

    ldapsam_compat (Samba-2.2 LDAP Compatibility)

    - - + + There is a password backend option that allows continued operation with an existing OpenLDAP backend that uses the Samba-2.2.x LDAP schema extension. This option is provided primarily as a migration tool, although there is no reason to force migration at this time. This tool will eventually be deprecated. -

    New Account Storage Systems

    +

    New Account Storage Systems

    Samba-3 introduces a number of new password backend capabilities. - - + +

    tdbsam

    - - + + This backend provides a rich database backend for local servers. This backend is not suitable for multiple domain controllers (i.e., PDC + one or more BDC) installations.

    - - - + + + The tdbsam password backend stores the old smbpasswd information plus the extended MS Windows NT/200x SAM information into a binary format TDB (trivial database) file. @@ -102,63 +102,63 @@ Samba-3 introduces a number of new password backend capabilities. to implement the same account and system access controls that are possible with MS Windows NT4/200x-based systems.

    - - + + The inclusion of the tdbsam capability is a direct response to user requests to allow simple site operation without the overhead of the complexities of running OpenLDAP. It is recommended to use this only for sites that have fewer than 250 users. For larger sites or implementations, the use of OpenLDAP or of Active Directory integration is strongly recommended.

    ldapsam

    - - + + This provides a rich directory backend for distributed account installation.

    - - - + + + Samba-3 has a new and extended LDAP implementation that requires configuration of OpenLDAP with a new format Samba schema. The new format schema file is included in the examples/LDAP directory of the Samba distribution.

    - - + + The new LDAP implementation significantly expands the control abilities that were possible with prior versions of Samba. It is now possible to specify “per-user” profile settings, home directories, account access controls, and much more. Corporate sites will see that the Samba Team has listened to their requests both for capability and greater scalability.

    Technical Information

    - - + + Old Windows clients send plaintext passwords over the wire. Samba can check these passwords by encrypting them and comparing them to the hash stored in the UNIX user database.

    - - + + Newer Windows clients send encrypted passwords (LanMan and NT hashes) instead of plaintext passwords over the wire. The newest clients will send only encrypted passwords and refuse to send plaintext passwords unless their registry is tweaked.

    - - + + Many people ask why Samba cannot simply use the UNIX password database. Windows requires passwords that are encrypted in its own format. The UNIX passwords can't be converted to UNIX-style encrypted passwords. Because of that, you can't use the standard UNIX user database, and you have to store the LanMan and NT hashes somewhere else.

    - - + + In addition to differently encrypted passwords, Windows also stores certain data for each user that is not stored in a UNIX user database: for example, workstations the user may logon from, the location where the user's profile is stored, and so on. Samba retrieves and stores this @@ -166,18 +166,18 @@ Samba-3 introduces a number of new password backend capabilities. tdbsam, and plain text file. For more information, see the man page for smb.conf regarding the passdb backend parameter.

    Figure 11.1. IDMAP: Resolution of SIDs to UIDs.

    IDMAP: Resolution of SIDs to UIDs.

    - - - + + + The resolution of SIDs to UIDs is fundamental to correct operation of Samba. In both cases shown, if winbindd is not running or cannot be contacted, then only local SID/UID resolution is possible. See resolution of SIDs to UIDs and resolution of UIDs to SIDs diagrams. -

    Figure 11.2. IDMAP: Resolution of UIDs to SIDs.

    IDMAP: Resolution of UIDs to SIDs.

    Important Notes About Security

    - - +

    Figure 11.2. IDMAP: Resolution of UIDs to SIDs.

    IDMAP: Resolution of UIDs to SIDs.

    Important Notes About Security

    + + The UNIX and SMB password encryption techniques seem similar on the surface. This similarity is, however, only skin deep. The UNIX scheme typically sends clear-text passwords over the network when logging in. This is bad. The SMB encryption scheme @@ -191,217 +191,217 @@ Samba-3 introduces a number of new password backend capabilities. passwords of all your users. Its contents must be kept secret, and the file should be protected accordingly.

    - - + + Ideally, we would like a password scheme that involves neither plaintext passwords on the network nor plaintext passwords on disk. Unfortunately, this is not available because Samba is stuck with having to be compatible with other SMB systems (Windows NT, Windows for Workgroups, Windows 9x/Me).

    - - + + Windows NT 4.0 Service Pack 3 changed the default setting so plaintext passwords are disabled from being sent over the wire. This mandates either the use of encrypted password support or editing the Windows NT registry to re-enable plaintext passwords.

    - - + + The following versions of Microsoft Windows do not support full domain security protocols, although they may log onto a domain environment:

    • MS DOS Network client 3.0 with the basic network redirector installed.

    • Windows 95 with the network redirector update installed.

    • Windows 98 [Second Edition].

    • Windows Me.

    Note

    - - + + MS Windows XP Home does not have facilities to become a domain member, and it cannot participate in domain logons.

    The following versions of MS Windows fully support domain security protocols.

    • Windows NT 3.5x.

    • Windows NT 4.0.

    • Windows 2000 Professional.

    • Windows 200x Server/Advanced Server.

    • Windows XP Professional.

    - - + + All current releases of Microsoft SMB/CIFS clients support authentication via the SMB challenge/response mechanism described here. Enabling clear-text authentication does not disable the ability of the client to participate in encrypted authentication. Instead, it allows the client to negotiate either plaintext or encrypted password handling.

    - - + + MS Windows clients will cache the encrypted password alone. Where plaintext passwords are re-enabled through the appropriate registry change, the plaintext password is never cached. This means that in the event that a network connections should become disconnected (broken), only the cached (encrypted) password will be sent to the resource server to effect an auto-reconnect. If the resource server does not support encrypted passwords, the auto-reconnect will fail. Use of encrypted passwords is strongly advised. -

    Advantages of Encrypted Passwords

    • - - +

      Advantages of Encrypted Passwords

      • + + Plaintext passwords are not passed across the network. Someone using a network sniffer cannot just record passwords going to the SMB server.

      • - - - + + + Plaintext passwords are not stored anywhere in memory or on disk.

      • - - + + Windows NT does not like talking to a server that does not support encrypted passwords. It will refuse to browse the server if the server is also in user-level security mode. It will insist on prompting the user for the password on each connection, which is very annoying. The only thing you can do to stop this is to use SMB encryption.

      • - - + + Encrypted password support allows automatic share (resource) reconnects.

      • - - + + Encrypted passwords are essential for PDC/BDC operation. -

      Advantages of Non-Encrypted Passwords

      • - +

      Advantages of Non-Encrypted Passwords

      • + Plaintext passwords are not kept on disk and are not cached in memory.

      • - - + + Plaintext passwords use the same password file as other UNIX services, such as Login and FTP.

      • - - + + Use of other services (such as Telnet and FTP) that send plaintext passwords over the network makes sending them for SMB not such a big deal. -

    Mapping User Identifiers between MS Windows and UNIX

    - - - +

    Mapping User Identifiers between MS Windows and UNIX

    + + + Every operation in UNIX/Linux requires a user identifier (UID), just as in MS Windows NT4/200x this requires a security identifier (SID). Samba provides two means for mapping an MS Windows user to a UNIX/Linux UID.

    - - - - + + + + First, all Samba SAM database accounts require a UNIX/Linux UID that the account will map to. As users are added to the account information database, Samba will call the add user script interface to add the account to the Samba host OS. In essence all accounts in the local SAM require a local user account.

    - - - + + + The second way to map Windows SID to UNIX UID is via the idmap uid and idmap gid parameters in smb.conf. Please refer to the man page for information about these parameters. These parameters are essential when mapping users from a remote (non-member Windows client or a member of a foreign domain) SAM server.

    Mapping Common UIDs/GIDs on Distributed Machines

    - - - - + + - + + + Samba-3 has a special facility that makes it possible to maintain identical UIDs and GIDs on all servers in a distributed network. A distributed network is one where there exists a PDC, one or more BDCs, and/or one or more domain member servers. Why is this important? This is important if files are being shared over more than one protocol (e.g., NFS) and where users are copying files across UNIX/Linux systems using tools such as rsync.

    - - - + - + + + The special facility is enabled using a parameter called idmap backend. The default setting for this parameter is an empty string. Technically it is possible to use an LDAP-based idmap backend for UIDs and GIDs, but it makes most sense when this is done for network configurations that also use LDAP for the SAM backend. Example Configuration with the LDAP idmap Backend shows that configuration. -

    Example 11.1. Example Configuration with the LDAP idmap Backend

    [global]
    idmap backend = ldap:ldap://ldap-server.quenya.org:636
    # Alternatively, this could be specified as:
    idmap backend = ldap:ldaps://ldap-server.quenya.org

    - - +

    Example 11.1. Example Configuration with the LDAP idmap Backend

    [global]
    idmap backend = ldap:ldap://ldap-server.quenya.org:636
    # Alternatively, this could be specified as:
    idmap backend = ldap:ldaps://ldap-server.quenya.org

    + + A network administrator who wants to make significant use of LDAP backends will sooner or later be exposed to the excellent work done by PADL Software. PADL http://www.padl.com have produced and released to open source an array of tools that might be of interest. These tools include:

    • - - - - + + - + + + nss_ldap: An LDAP name service switch (NSS) module to provide native name service support for AIX, Linux, Solaris, and other operating systems. This tool can be used for centralized storage and retrieval of UIDs and GIDs.

    • - - - + + + pam_ldap: A PAM module that provides LDAP integration for UNIX/Linux system access authentication.

    • - - + + idmap_ad: An IDMAP backend that supports the Microsoft Services for UNIX RFC 2307 schema available from the PADL Web site. -

    Comments Regarding LDAP

    - - - +

    Comments Regarding LDAP

    + + + There is much excitement and interest in LDAP directories in the information technology world today. The LDAP architecture was designed to be highly scalable. It was also designed for use across a huge number of potential areas of application encompassing a wide range of operating systems and platforms. LDAP technologies are at the heart of the current generations of Federated Identity Management (FIM) solutions that can underlie a corporate Single Sign-On (SSO) environment.

    - - + + LDAP implementations have been built across a wide variety of platforms. It lies at the core of Microsoft Windows Active Directory services (ADS), Novell's eDirectory, as well as many others. Implementation of the directory services LDAP involves interaction with legacy as well as new generation applications, all of which depend on some form of authentication services.

    - - - + - + + + UNIX services can utilize LDAP directory information for authentication and access controls through intermediate tools and utilities. The total environment that consists of the LDAP directory and the middle-ware tools and utilities makes it possible for all user access to the UNIX platform @@ -410,12 +410,12 @@ Samba-3 introduces a number of new password backend capabilities. shells, mail and messaging systems, quota controls, printing systems, DNS servers, DHCP servers, and also Samba.

    - - - + + + Many sites are installing LDAP for the first time in order to provide a scalable passdb backend for Samba. Others are faced with the need to adapt an existing LDAP directory to new uses such as for the Samba SAM backend. Whatever your particular need and attraction to Samba may be, @@ -423,37 +423,37 @@ Samba-3 introduces a number of new password backend capabilities. are of a durable nature for the site. These have far-reaching implications that affect long-term information systems management costs.

    - - + + Do not rush into an LDAP deployment. Take the time to understand how the design of the Directory Information Tree (DIT) may impact current and future site needs, as well as the ability to meet them. The way that Samba SAM information should be stored within the DIT varies from site to site and with each implementation new experience is gained. It is well understood by LDAP veterans that first implementations create awakening, second implementations of LDAP create fear, and third-generation deployments bring peace and tranquility. -

    Caution Regarding LDAP and Samba

    - - +

    Caution Regarding LDAP and Samba

    - + + + Samba requires UNIX POSIX identity information as well as a place to store information that is specific to Samba and the Windows networking environment. The most used information that must be dealt with includes: user accounts, group accounts, machine trust accounts, interdomain trust accounts, and intermediate information specific to Samba internals.

    - - + + The example deployment guidelines in this book, as well as other books and HOWTO documents available from the internet may not fit with established directory designs and implementations. The existing DIT may not be able to accommodate the simple information layout proposed in common sources. Additionally, you may find that the common scripts and tools that are used to provision the LDAP directory for use with Samba may not suit your needs.

    - + It is not uncommon, for sites that have existing LDAP DITs to find necessity to generate a set of site-specific scripts and utilities to make it possible to deploy Samba within the scope of site operations. The way that user and group accounts are distributed throughout @@ -461,63 +461,63 @@ Samba-3 introduces a number of new password backend capabilities. the journey to it may be challenging. Take time to understand site needs and do not rush into deployment.

    - - + + Above all, do not blindly use scripts and tools that are not suitable for your site. Check and validate all scripts before you execute them to make sure that the existing infrastructure will not be damaged by inadvertent use of an inappropriate tool. -

    LDAP Directories and Windows Computer Accounts

    - - - +

    LDAP Directories and Windows Computer Accounts

    + + + Samba doesn't provide a turnkey solution to LDAP. It is best to deal with the design and configuration of an LDAP directory prior to integration with Samba. A working knowledge of LDAP makes Samba integration easy, and the lack of a working knowledge of LDAP can make it a frustrating experience.

    - - - + + + Computer (machine) accounts can be placed wherever you like in an LDAP directory subject to some constraints that are described in this chapter.

    - - - - - - - + + + + + + + The POSIX and sambaSamAccount components of computer (machine) accounts are both used by Samba. Thus, machine accounts are treated inside Samba in the same way that Windows NT4/200X treats them. A user account and a machine account are indistinquishable from each other, except that the machine account ends in a $ character, as do trust accounts.

    - - - - - + + + + + The need for Windows user, group, machine, trust, and other accounts to be tied to a valid UNIX UID is a design decision that was made a long way back in the history of Samba development. It is unlikely that this decision will be reversed or changed during the remaining life of the Samba-3.x series.

    - - - + + + The resolution of a UID from the Windows SID is achieved within Samba through a mechanism that must refer back to the host operating system on which Samba is running. The NSS is the preferred mechanism that shields applications (like Samba) from the need to know everything about every host OS it runs on.

    - - - - - - - + + + + + + + Samba asks the host OS to provide a UID via the “passwd”, “shadow”, and “group” facilities in the NSS control (configuration) file. The best tool for achieving this is left up to the UNIX administrator to determine. It is not imposed by @@ -525,64 +525,64 @@ Samba-3 introduces a number of new password backend capabilities. possible to do this via LDAP, and for that Samba provides the appropriate hooks so that all account entities can be located in an LDAP directory.

    - - - - - + + + + + For many the weapon of choice is to use the PADL nss_ldap utility. This utility must be configured so that computer accounts can be resolved to a POSIX/UNIX account UID. That is fundamentally an LDAP design question. The information provided on the Samba list and in the documentation is directed at providing working examples only. The design of an LDAP directory is a complex subject that is beyond the scope of this documentation.

    Account Management Tools

    - - - + + + Samba provides two tools for management of user and machine accounts: smbpasswd and pdbedit.

    - - - + + + The pdbedit can be used to manage account policies in addition to Samba user account information. The policy management capability is used to administer domain default settings for password aging and management controls to handle failed login attempts.

    - - - - + + + + Some people are confused when reference is made to smbpasswd because the name refers to a storage mechanism for SambaSAMAccount information, but it is also the name of a utility tool. That tool is destined to eventually be replaced by new functionality that is being added to the net toolset (see the Net Command. -

    The smbpasswd Tool

    - - - - - +

    The smbpasswd Tool

    + + + + + The smbpasswd utility is similar to the passwd and yppasswd programs. It maintains the two 32 byte password fields in the passdb backend. This utility operates independently of the actual account and password storage methods used (as specified by the passdb backend in the smb.conf file.

    - - + + smbpasswd works in a client-server mode where it contacts the local smbd to change the user's password on its behalf. This has enormous benefits.

    - - + + smbpasswd has the capability to change passwords on Windows NT servers (this only works when the request is sent to the NT PDC if changing an NT domain user's password).

    - - + + smbpasswd can be used to:

    • add user or machine accounts.

    • delete user or machine accounts.

    • enable user or machine accounts.

    • disable user or machine accounts.

    • set to NULL user passwords.

    • manage interdomain trust accounts.

    To run smbpasswd as a normal user, just type: @@ -601,56 +601,56 @@ is being added to the net toolset (see + When invoked by an ordinary user, the command will allow only the user to change his or her own SMB password.

    - - + + When run by root, smbpasswd may take an optional argument specifying the username whose SMB password you wish to change. When run as root, smbpasswd does not prompt for or check the old password value, thus allowing root to set passwords for users who have forgotten their passwords.

    - - - - + + + + smbpasswd is designed to work in the way familiar to UNIX users who use the passwd or yppasswd commands. While designed for administrative use, this tool provides essential user-level password change capabilities.

    - + For more details on using smbpasswd, refer to the man page (the definitive reference).

    The pdbedit Tool

    - - - - + + + + pdbedit is a tool that can be used only by root. It is used to manage the passdb backend, as well as domain-wide account policy settings. pdbedit can be used to:

    • add, remove, or modify user accounts.

    • list user accounts.

    • migrate user accounts.

    • migrate group accounts.

    • manage account policies.

    • manage domain access policy settings.

    - + Under the terms of the Sarbanes-Oxley Act of 2002, American businesses and organizations are mandated to implement a series of internal controls and procedures to communicate, store, and protect financial data. The Sarbanes-Oxley Act has far reaching implications in respect of:

    1. Who has access to information systems that store financial data.

    2. How personal and financial information is treated among employees and business partners.

    3. How security vulnerabilities are managed.

    4. Security and patch level maintenance for all information systems.

    5. How information systems changes are documented and tracked.

    6. How information access controls are implemented and managed.

    7. Auditability of all information systems in respect of change and security.

    8. Disciplinary procedures and controls to ensure privacy.

    - - + + In short, the Sarbanes-Oxley Act of 2002 is an instrument that enforces accountability in respect of business related information systems so as to ensure the compliance of all information systems that are used to store personal information and particularly for financial records processing. Similar accountabilities are being demanded around the world.

    - - - - - + + + + + The need to be familiar with the Samba tools and facilities that permit information systems operation in compliance with government laws and regulations is clear to all. The pdbedit is currently the only Samba tool that provides the capacity to manage account and systems access controls @@ -660,27 +660,27 @@ is being added to the net toolset (see NT4 Domain v's Samba Policy Controls.

    Table 11.1. NT4 Domain v's Samba Policy Controls

    NT4 policy Name

    Samba Policy Name

    NT4 Range

    Samba Range

    Samba Default

    Maximum Password Age

    maximum password age

    0 - 999 (days)

    0 - 4294967295 (sec)

    4294967295

    Minimum Password Age

    minimum password age

    0 - 999 (days)

    0 - 4294967295 (sec)

    0

    Mimimum Password Length

    min password length

    1 - 14 (Chars)

    0 - 4294967295 (Chars)

    5

    Password Uniqueness

    password history

    0 - 23 (#)

    0 - 4294967295 (#)

    0

    Account Lockout - Reset count after

    reset count minutes

    1 - 99998 (min)

    0 - 4294967295 (min)

    30

    Lockout after bad logon attempts

    bad lockout attempt

    0 - 998 (#)

    0 - 4294967295 (#)

    0

    *** Not Known ***

    disconnect time

    TBA

    0 - 4294967295

    0

    Lockout Duration

    lockout duration

    1 - 99998 (min)

    0 - 4294967295 (min)

    30

    Users must log on in order to change password

    user must logon to change password

    0/1

    0 - 4294967295

    0

    *** Registry Setting ***

    refuse machine password change

    0/1

    0 - 4294967295

    0


    - - - - + + + + The pdbedit tool is the only one that can manage the account security and policy settings. It is capable of all operations that smbpasswd can do as well as a superset of them.

    - - - + + + One particularly important purpose of the pdbedit is to allow the import/export of account information from one passdb backend to another. -

    User Account Management

    - - - - - - - +

    User Account Management

    + + + + + + + The pdbedit tool, like the smbpasswd tool, requires that a POSIX user account already exists in the UNIX/Linux system accounts database (backend). Neither tool will call out to the operating system to create a user account because this is @@ -690,13 +690,13 @@ is being added to the net toolset (see pdbedit tool does not make use of these interface scripts.

    - - + + Before attempting to use the pdbedit tool to manage user and machine accounts, make certain that a system (POSIX) account has already been created. -

    Listing User and Machine Accounts

    - - +

    Listing User and Machine Accounts

    + + The following is an example of the user account information that is stored in a tdbsam password backend. This listing was produced by running: 

    @@ -723,7 +723,7 @@ Password can change:  Sat, 14 Dec 2002 14:37:03 GMT
 Password must change: Mon, 18 Jan 2038 20:14:07 GMT

    - + Accounts can also be listed in the older smbpasswd format: 

     root# pdbedit -Lw
@@ -748,29 +748,29 @@ frodo$:1008:15891DC6B843ECA41249940C814E316B:
 marvel$:1011:BF709959C3C94E0B3958B7B84A3BB6F3:
      C610EFE9A385A3E8AA46ADFD576E6881:[W          ]:LCT-40F07A4

    - - - - - - + + + + + + The account information that was returned by this command in order from left to right consists of the following colon separated data:

    • Login ID.

    • UNIX UID.

    • Microsoft LanManager password hash (password converted to upper-case then hashed.

    • Microsoft NT password hash (hash of the case-preserved password).

    • Samba SAM Account Flags.

    • The LCT data (password last change time).

    - - + + The Account Flags parameters are documented in the pdbedit man page, and are briefly documented in the Account Flags Management section.

    - + The LCT data consists of 8 hexadecimal characters representing the time since January 1, 1970, of the time when the password was last changed. -

    Adding User Accounts

    - - - - - +

    Adding User Accounts

    + + + + + The pdbedit can be used to add a user account to a standalone server or to a domain. In the example shown here the account for the user vlaan has been created before attempting to add the SambaSAMAccount. @@ -802,11 +802,11 @@ Last bad password : 0 Bad password count : 0 Logon hours : FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF

    -

    Deleting Accounts

    - - - - +

    Deleting Accounts

    + + + + An account can be deleted from the SambaSAMAccount database 

     root#  pdbedit -x vlaan
@@ -814,16 +814,16 @@ Logon hours         : FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF
 		The account is removed without further screen output. The account is removed only from the
 		SambaSAMAccount (passdb backend) database, it is not removed from the UNIX account backend.
 		
    
-
-
+
+
 		The use of the NT4 domain user manager to delete an account will trigger the delete user
 		script, but not the pdbedit tool.
-
    Changing User Accounts

    - +

    Changing User Accounts

    + Refer to the pdbedit man page for a full synopsis of all operations that are available with this tool.

    - + An example of a simple change in the user account information is the change of the full name information shown here: 

    @@ -835,9 +835,9 @@ Home Directory:       \\frodo\vlaan
 ...

    - - - + + + Let us assume for a moment that a user's password has expired and the user is unable to change the password at this time. It may be necessary to give the user additional grace time so that it is possible to continue to work with the account and the original password. This @@ -852,8 +852,8 @@ Last bad password : Thu, 03 Jan 2002 15:08:35 GMT Bad password count : 2 ...

    - - + + The user has recorded 2 bad logon attempts and the next will lock the account, but the password is also expired. Here is how this account can be reset: 

    @@ -885,49 +885,49 @@ Password can change:  Thu, 03 Jan 2002 15:08:35 GMT
 Password must change: Fri, 01 Jan 2010 00:00:00 GMT
 ...

    - - + + Refer to the strptime man page for specific time format information.

    - - + + Please refer to the pdbedit man page for further information relating to SambaSAMAccount management.

    Account Flags Management

    - - - - + + + + The Samba SAM account flags are properly called the ACB (account control block) within the Samba source code. In some parts of the Samba source code they are referred to as the account encode_bits, and also as the account control flags.

    - - - - - + + + + + The manual adjustment of user, machine (workstation or server) or an inter-domain trust account account flgas should not be necessary under normal conditions of use of Samba. On the other hand, where this information becomes corrupted for some reason, the ability to correct the damaged data is certainly useful. The tool of choice by which such correction can be affected is the pdbedit utility.

    - - + + There have been a few requests for information regarding the account flags from developers who are creating their own Samba management tools. An example of a need for information regarding the proper management of the account flags is evident when developing scripts that will be used to manage an LDAP directory.

    - - + + The account flag field can contain up to 16 characters. Presently, only 11 are in use. These are listed in Samba SAM Account Control Block Flags. The order in which the flags are specified to the pdbedit command is not important. In fact, they can be set without problem in any order in the SambaAcctFlags record in the LDAP directory.

    Table 11.2. Samba SAM Account Control Block Flags

    FlagDescription
    DAccount is disabled.
    HA home directory is required.
    IAn inter-domain trust account.
    LAccount has been auto-locked.
    MAn MNS (Microsoft network service) logon account.
    NPassword not required.
    SA server trust account.
    TTemporary duplicate account entry.
    UA normal user account.
    WA workstation trust account.
    XPassword does not expire.

    - - + + An example of use of the pdbedit utility to set the account control flags is shown here: 

    @@ -955,7 +955,7 @@ Last bad password   : 0
 Bad password count  : 0
 Logon hours         : FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF

    - + The flags can be reset to the default settings by executing: 

     root#  pdbedit -r -c "[]" jht
@@ -982,9 +982,9 @@ Last bad password   : 0
 Bad password count  : 0
 Logon hours         : FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF

    -

    Domain Account Policy Managment

    - - +

    Domain Account Policy Managment

    + + To view the domain account access policies that may be configured execute: 

     root#  pdbedit -P ?
@@ -1032,134 +1032,134 @@ Account policies must be set individually on each PDC and BDC. At this time (Sam
 account policies are not replicated automatically. This may be fixed before Samba 3.0.20 ships or some
 time there after. Please check the WHATSNEW.txt file in the Samba-3 tarball for specific update notiations
 regarding this facility.
-

    Account Import/Export

    - - - +

    Account Import/Export

    + + + The pdbedit tool allows import/export of authentication (account) databases from one backend to another. For example, to import/export accounts from an old smbpasswd database to a tdbsam backend:

    1. - + 

       root# pdbedit -i smbpasswd -e tdbsam

    2. - + Replace the smbpasswd with tdbsam in the passdb backend configuration in smb.conf. -

    Password Backends

    - - +

    Password Backends

    + + Samba offers flexibility in backend account database design. The flexibility is immediately obvious as one begins to explore this capability. Recent changes to Samba (since 3.0.23) have removed the mulitple backend feature in order to simplify problems that broke some installations. This removal has made the internal operation of Samba-3 more consistent and predictable.

    - - + + Beginning with Samba 3.0.23 it is no longer possible to specify use of mulitple passdb backends. Earlier versions of Samba-3 made it possible to specify multiple password backends, and even multiple backends of the same type. The multiple passdb backend capability caused many problems with name to SID and SID to name ID resolution. The Samba team wrestled with the challenges and decided that this feature needed to be removed. -

    Plaintext

    - - - - - - +

    Plaintext

    + + + + + + Older versions of Samba retrieved user information from the UNIX user database and eventually some other fields from the file /etc/samba/smbpasswd or /etc/smbpasswd. When password encryption is disabled, no SMB-specific data is stored at all. Instead, all operations are conducted via the way that the Samba host OS will access its /etc/passwd database. On most Linux systems, for example, all user and group resolution is done via PAM. -

    smbpasswd: Encrypted Password Database

    - - - - +

    smbpasswd: Encrypted Password Database

    + + + + Traditionally, when configuring encrypt passwords = yes in Samba's smb.conf file, user account information such as username, LM/NT password hashes, password change times, and account flags have been stored in the smbpasswd(5) file. There are several disadvantages to this approach for sites with large numbers of users (counted in the thousands).

    • - + The first problem is that all lookups must be performed sequentially. Given that there are approximately two lookups per domain logon (one during intial logon validation and one for a session connection setup, such as when mapping a network drive or printer), this is a performance bottleneck for large sites. What is needed is an indexed approach such as that used in databases.

    • - - - - - + + + + + The second problem is that administrators who desire to replicate an smbpasswd file to more than one Samba server are left to use external tools such as rsync(1) and ssh(1) and write custom, in-house scripts.

    • - - - - - + + + + + Finally, the amount of information that is stored in an smbpasswd entry leaves no room for additional attributes such as a home directory, password expiration time, or even a relative identifier (RID).

    - - - - + + + + As a result of these deficiencies, a more robust means of storing user attributes used by smbd was developed. The API that defines access to user accounts is commonly referred to as the samdb interface (previously, this was called the passdb API and is still so named in the Samba source code trees).

    - - - - - + + + + + Samba provides an enhanced set of passdb backends that overcome the deficiencies of the smbpasswd plaintext database. These are tdbsam and ldapsam. Of these, ldapsam will be of most interest to large corporate or enterprise sites. -

    tdbsam

    - - - +

    tdbsam

    + + + Samba can store user and machine account data in a “TDB” (trivial database). Using this backend does not require any additional configuration. This backend is recommended for new installations that do not require LDAP.

    - - - - + + + + As a general guide, the Samba Team does not recommend using the tdbsam backend for sites that have 250 or more users. Additionally, tdbsam is not capable of scaling for use in sites that require PDB/BDC implementations that require replication of the account database. Clearly, for reason of scalability, the use of ldapsam should be encouraged.

    - - - + + + The recommendation of a 250-user limit is purely based on the notion that this would generally involve a site that has routed networks, possibly spread across more than one physical location. The Samba Team has not at this time established the performance-based scalability limits of the tdbsam architecture.

    - - - - + + + + There are sites that have thousands of users and yet require only one server. One site recently reported having 4,500 user accounts on one UNIX system and reported excellent performance with the tdbsam passdb backend. @@ -1167,26 +1167,26 @@ to be removed. is not one pertaining to a limitation in the TDB storage system, it is based only on the need for a reliable distribution mechanism for the SambaSAMAccount backend. -

    ldapsam

    - - - +

    ldapsam

    + + + There are a few points to stress that the ldapsam does not provide. The LDAP support referred to in this documentation does not include:

    • A means of retrieving user account information from a Windows 200x Active Directory server.

    • A means of replacing /etc/passwd.

    - - - - + + + + The second item can be accomplished by using LDAP NSS and PAM modules. LGPL versions of these libraries can be obtained from PADL Software. More information about the configuration of these packages may be found in LDAP, System Administration by Gerald Carter, Chapter 6, Replacing NIS".

    - - - + + + This document describes how to use an LDAP directory for storing Samba user account information traditionally stored in the smbpasswd(5) file. It is assumed that the reader already has a basic understanding of LDAP concepts @@ -1199,28 +1199,28 @@ to be removed. Server

    Two additional Samba resources that may prove to be helpful are:

    • - + The Samba-PDC-LDAP-HOWTO maintained by Ignacio Coupeau.

    • - - - + + + The NT migration scripts from IDEALX that are geared to manage users and groups in such a Samba-LDAP domain controller configuration. Idealx also produced the smbldap-tools and the Interactive Console Management tool. -

    Supported LDAP Servers

    - - - - +

    Supported LDAP Servers

    + + + + The LDAP ldapsam code was developed and tested using the OpenLDAP 2.x server and client libraries. The same code should work with Netscape's Directory Server and client SDK. However, there are bound to be compile errors and bugs. These should not be hard to fix. Please submit fixes via the process outlined in Reporting Bugs.

    Samba is capable of working with any standards-compliant LDAP server. -

    Schema and Relationship to the RFC 2307 posixAccount

    +

    Schema and Relationship to the RFC 2307 posixAccount

    Samba-3.0 includes the necessary schema file for OpenLDAP 2.x in the examples/LDAP/samba.schema directory of the source code distribution tarball. The schema entry for the sambaSamAccount ObjectClass is shown here: @@ -1236,21 +1236,21 @@ ObjectClass (1.3.6.1.4.1.7165.2.2.6 NAME 'sambaSamAccount' SUP top AUXILIARY sambaPrimaryGroupSID $ sambaDomainName ))

    - - - + + + The samba.schema file has been formatted for OpenLDAP 2.0/2.1. The Samba Team owns the OID space used by the above schema and recommends its use. If you translate the schema to be used with Netscape DS, please submit the modified schema file as a patch to jerry@samba.org.

    - - - - - - - + + + + + + + Just as the smbpasswd file is meant to store information that provides information additional to a user's /etc/passwd entry, so is the sambaSamAccount object meant to supplement the UNIX user account information. A sambaSamAccount is an @@ -1259,15 +1259,15 @@ ObjectClass (1.3.6.1.4.1.7165.2.2.6 NAME 'sambaSamAccount' SUP top AUXILIARY for Samba account handling. However, there are several fields (e.g., uid) that overlap with the posixAccount ObjectClass outlined in RFC 2307. This is by design.

    - - - - - - - - - + + + + + + + + + In order to store all user account information (UNIX and Samba) in the directory, it is necessary to use the sambaSamAccount and posixAccount ObjectClasses in combination. However, smbd will still obtain the user's UNIX account @@ -1276,11 +1276,11 @@ ObjectClass (1.3.6.1.4.1.7165.2.2.6 NAME 'sambaSamAccount' SUP top AUXILIARY and functioning correctly. This division of information makes it possible to store all Samba account information in LDAP, but still maintain UNIX account information in NIS while the network is transitioning to a full LDAP infrastructure. -

    OpenLDAP Configuration

    - - - - +

    OpenLDAP Configuration

    + + + + To include support for the sambaSamAccount object in an OpenLDAP directory server, first copy the samba.schema file to slapd's configuration directory. The samba.schema file can be found in the directory examples/LDAP @@ -1289,14 +1289,14 @@ ObjectClass (1.3.6.1.4.1.7165.2.2.6 NAME 'sambaSamAccount' SUP top AUXILIARY root# cp samba.schema /etc/openldap/schema/

    - - - - - - - - + + + + + + + + Next, include the samba.schema file in slapd.conf. The sambaSamAccount object contains two attributes that depend on other schema files. The uid attribute is defined in cosine.schema and @@ -1316,10 +1316,10 @@ include /etc/openldap/schema/samba.schema ....

    - - - - + + + + It is recommended that you maintain some indices on some of the most useful attributes, as in the following example, to speed up searches made on sambaSamAccount ObjectClasses (and possibly posixAccount and posixGroup as well): @@ -1357,11 +1357,11 @@ index default sub 

     root# /etc/init.d/slapd restart

    -

    Initialize the LDAP Database

    - - - - +

    Initialize the LDAP Database

    + + + + Before you can add accounts to the LDAP database, you must create the account containers that they will be stored in. The following LDIF file should be modified to match your needs (DNS entries, and so on): @@ -1423,15 +1423,15 @@ objectclass: simpleSecurityObject userPassword: {SSHA}c3ZM9tBaBo9autm1dL3waDS21+JSfQVz

    - - + + The userPassword shown above should be generated using slappasswd.

    - - + + The following command will then load the contents of the LDIF file into the LDAP database. - + 

     $ slapadd -v -l initldap.dif

    @@ -1439,16 +1439,16 @@ userPassword: {SSHA}c3ZM9tBaBo9autm1dL3waDS21+JSfQVz Do not forget to secure your LDAP server with an adequate access control list as well as an admin password.

    Note

    - + Before Samba can access the LDAP server, you need to store the LDAP admin password in the Samba-3 secrets.tdb database by: - + 

     root# smbpasswd -w secret

    -

    Configuring Samba

    - - +

    Configuring Samba

    + + The following parameters are available in smb.conf only if your version of Samba was built with LDAP support. Samba automatically builds with LDAP support if the LDAP libraries are found. The best method to verify that Samba was built with LDAP support is: @@ -1467,19 +1467,19 @@ userPassword: {SSHA}c3ZM9tBaBo9autm1dL3waDS21+JSfQVz that includes HAVE_LDAP_H it is necessary to discover why the LDAP headers and libraries were not found during compilation.

    LDAP-related smb.conf options include these: -

    passdb backend = ldapsam:url

    +

    passdb backend = ldapsam:url

    These are described in the smb.conf man page and so are not repeated here. However, an example for use with an LDAP directory is shown in the Configuration with LDAP. -

    Example 11.2. Configuration with LDAP

    [global]
    security = user
    encrypt passwords = yes
    netbios name = MORIA
    workgroup = NOLDOR
    # LDAP related parameters:
    # Define the DN used when binding to the LDAP servers.
    # The password for this DN is not stored in smb.conf
    # Set it using 'smbpasswd -w secret' to store the
    # passphrase in the secrets.tdb file.
    # If the "ldap admin dn" value changes, it must be reset.
    ldap admin dn = "cn=Manager,dc=quenya,dc=org"
    # SSL directory connections can be configured by:
    # ('off', 'start tls', or 'on' (default))
    ldap ssl = start tls
    # syntax: passdb backend = ldapsam:ldap://server-name[:port]
    passdb backend = ldapsam:ldap://frodo.quenya.org
    # smbpasswd -x delete the entire dn-entry
    ldap delete dn = no
    # The machine and user suffix are added to the base suffix
    # wrote WITHOUT quotes. NULL suffixes by default
    ldap user suffix = ou=People
    ldap group suffix = ou=Groups
    ldap machine suffix = ou=Computers
    # Trust UNIX account information in LDAP
    # (see the smb.conf man page for details)
    # Specify the base DN to use when searching the directory
    ldap suffix = dc=quenya,dc=org

    Accounts and Groups Management

    - - +

    Example 11.2. Configuration with LDAP

    [global]
    security = user
    encrypt passwords = yes
    netbios name = MORIA
    workgroup = NOLDOR
    # LDAP related parameters:
    # Define the DN used when binding to the LDAP servers.
    # The password for this DN is not stored in smb.conf
    # Set it using 'smbpasswd -w secret' to store the
    # passphrase in the secrets.tdb file.
    # If the "ldap admin dn" value changes, it must be reset.
    ldap admin dn = "cn=Manager,dc=quenya,dc=org"
    # SSL directory connections can be configured by:
    # ('off', 'start tls', or 'on' (default))
    ldap ssl = start tls
    # syntax: passdb backend = ldapsam:ldap://server-name[:port]
    passdb backend = ldapsam:ldap://frodo.quenya.org
    # smbpasswd -x delete the entire dn-entry
    ldap delete dn = no
    # The machine and user suffix are added to the base suffix
    # wrote WITHOUT quotes. NULL suffixes by default
    ldap user suffix = ou=People
    ldap group suffix = ou=Groups
    ldap machine suffix = ou=Computers
    # Trust UNIX account information in LDAP
    # (see the smb.conf man page for details)
    # Specify the base DN to use when searching the directory
    ldap suffix = dc=quenya,dc=org

    Accounts and Groups Management

    + + Because user accounts are managed through the sambaSamAccount ObjectClass, you should modify your existing administration tools to deal with sambaSamAccount attributes.

    - - - + + + Machine accounts are managed with the sambaSamAccount ObjectClass, just like user accounts. However, it is up to you to store those accounts in a different tree of your LDAP namespace. You should use @@ -1488,36 +1488,36 @@ userPassword: {SSHA}c3ZM9tBaBo9autm1dL3waDS21+JSfQVz NSS and PAM accordingly (usually, in the /etc/openldap/sldap.conf configuration file).

    - - - - + + + + In Samba-3, the group management system is based on POSIX groups. This means that Samba makes use of the posixGroup ObjectClass. For now, there is no NT-like group system management (global and local groups). Samba-3 knows only about Domain Groups and, unlike MS Windows 2000 and Active Directory, Samba-3 does not support nested groups. -

    Security and sambaSamAccount

    - +

    Security and sambaSamAccount

    + There are two important points to remember when discussing the security of sambaSAMAccount entries in the directory.

    • Never retrieve the SambaLMPassword or - + SambaNTPassword attribute values over an unencrypted LDAP session.

    • Never allow non-admin users to view the SambaLMPassword or SambaNTPassword attribute values.

    - - - + + + These password hashes are clear-text equivalents and can be used to impersonate the user without deriving the original clear-text strings. For more information on the details of LM/NT password hashes, refer to the Account Information Database section.

    - - - - + + + + To remedy the first security issue, the ldap ssl smb.conf parameter defaults to require an encrypted session (ldap ssl = on) using the default port of 636 when contacting the directory server. When using an OpenLDAP server, it @@ -1525,16 +1525,16 @@ userPassword: {SSHA}c3ZM9tBaBo9autm1dL3waDS21+JSfQVz In either case, you are strongly encouraged to use secure communications protocols (so do not set ldap ssl = off).

    - - - + + + Note that the LDAPS protocol is deprecated in favor of the LDAPv3 StartTLS extended operation. However, the OpenLDAP library still provides support for the older method of securing communication between clients and servers.

    - - - + + + The second security precaution is to prevent non-administrative users from harvesting password hashes from the directory. This can be done using the following ACL in slapd.conf: @@ -1545,7 +1545,7 @@ access to attrs=SambaLMPassword,SambaNTPassword by dn="cn=Samba Admin,ou=People,dc=quenya,dc=org" write by * none

    -

    LDAP Special Attributes for sambaSamAccounts

    The sambaSamAccount ObjectClass is composed of the attributes shown in next tables: Part A, and Part B. +

    LDAP Special Attributes for sambaSamAccounts

    The sambaSamAccount ObjectClass is composed of the attributes shown in next tables: Part A, and Part B.

    Table 11.3. Attributes in the sambaSamAccount ObjectClass (LDAP), Part A

    sambaLMPasswordThe LanMan password 16-byte hash stored as a character representation of a hexadecimal string.
    sambaNTPasswordThe NT password 16-byte hash stored as a character representation of a hexadecimal string.
    sambaPwdLastSetThe integer time in seconds since 1970 when the @@ -1580,16 +1580,16 @@ access to attrs=SambaLMPassword,SambaNTPassword
    sambaSIDThe security identifier(SID) of the user. The Windows equivalent of UNIX UIDs.
    sambaPrimaryGroupSIDThe security identifier (SID) of the primary group of the user.
    sambaDomainNameDomain the user is part of.

    - - + + The majority of these parameters are only used when Samba is acting as a PDC of a domain (refer to Domain Control, for details on how to configure Samba as a PDC). The following four attributes are only stored with the sambaSamAccount entry if the values are non-default values: -

    • sambaHomePath

    • sambaLogonScript

    • sambaProfilePath

    • sambaHomeDrive

    - - - +

    • sambaHomePath

    • sambaLogonScript

    • sambaProfilePath

    • sambaHomeDrive

    + + + These attributes are only stored with the sambaSamAccount entry if the values are non-default values. For example, assume MORIA has now been configured as a PDC and that logon home = \\%L\%u was defined in @@ -1600,7 +1600,7 @@ access to attrs=SambaLMPassword,SambaNTPassword of the logon home parameter is used in its place. Samba will only write the attribute value to the directory entry if the value is something other than the default (e.g., \\MOBY\becky). -

    Example LDIF Entries for a sambaSamAccount

    +

    Example LDIF Entries for a sambaSamAccount

    The following is a working LDIF that demonstrates the use of the SambaSamAccount ObjectClass: 

     dn: uid=guest2, ou=People,dc=quenya,dc=org
@@ -1645,7 +1645,7 @@ sambaPwdCanChange: 0
 sambaPwdMustChange: 2147483647
 sambaNTPassword: 878D8014606CDA29677A44EFA1353FC7

    -

    Password Synchronization

    +

    Password Synchronization

    Samba-3 and later can update the non-Samba (LDAP) password stored with an account. When using pam_ldap, this allows changing both UNIX and Windows passwords at once.

    The ldap passwd sync options can have the values shown in @@ -1654,7 +1654,7 @@ sambaNTPassword: 878D8014606CDA29677A44EFA1353FC7 and the password fields.

    no

    Only update SambaNTPassword and SambaLMPassword.

    only

    Only update the LDAP password and let the LDAP server worry about the other fields. This option is only available on some LDAP servers and - only when the LDAP server supports LDAP_EXOP_X_MODIFY_PASSWD.


    More information can be found in the smb.conf man page.

    Using OpenLDAP Overlay for Password Syncronization

    + only when the LDAP server supports LDAP_EXOP_X_MODIFY_PASSWD.


    More information can be found in the smb.conf man page.

    Using OpenLDAP Overlay for Password Syncronization

    Howard Chu has written a special overlay called smbk5pwd. This tool modifies the SambaNTPassword, SambaLMPassword and Heimdal hashes in an OpenLDAP entry when an LDAP_EXOP_X_MODIFY_PASSWD operation is performed. @@ -1662,8 +1662,8 @@ sambaNTPassword: 878D8014606CDA29677A44EFA1353FC7 The overlay is shipped with OpenLDAP-2.3 and can be found in the contrib/slapd-modules/smbk5pwd subdirectory. This module can also be used with OpenLDAP-2.2. -

    Common Errors

    Users Cannot Logon

    “I've installed Samba, but now I can't log on with my UNIX account! ”

    Make sure your user has been added to the current Samba passdb backend. - Read the Account Management Tools, for details.

    Configuration of auth methods

    +

    Common Errors

    Users Cannot Logon

    “I've installed Samba, but now I can't log on with my UNIX account! ”

    Make sure your user has been added to the current Samba passdb backend. + Read the Account Management Tools, for details.

    Configuration of auth methods

    When explicitly setting an auth methods parameter, guest must be specified as the first entry on the line for example, auth methods = guest sam. diff --git a/docs/htmldocs/Samba3-HOWTO/pr02.html b/docs/htmldocs/Samba3-HOWTO/pr02.html index a645d5b0d4..67f73ae35b 100644 --- a/docs/htmldocs/Samba3-HOWTO/pr02.html +++ b/docs/htmldocs/Samba3-HOWTO/pr02.html @@ -78,16 +78,18 @@

    Reporting Bugs

    -

    How to Compile Samba +

    Managing TDB Files +

    +

    How to Compile Samba

    -

    Portability +

    Portability

    -

    Samba and Other CIFS Clients +

    Samba and Other CIFS Clients

    -

    Samba Performance Tuning +

    Samba Performance Tuning

    -

    LDAP and Transport Layer Security +

    LDAP and Transport Layer Security

    -

    DNS and DHCP Configuration Guide +

    DNS and DHCP Configuration Guide

    Prev   Next
    About the Cover Artwork Home Foreword
    diff --git a/docs/htmldocs/Samba3-HOWTO/pr03.html b/docs/htmldocs/Samba3-HOWTO/pr03.html index 0f80022e0e..95531ed26c 100644 --- a/docs/htmldocs/Samba3-HOWTO/pr03.html +++ b/docs/htmldocs/Samba3-HOWTO/pr03.html @@ -1,4 +1,4 @@ -Foreword
    Foreword
    Prev   Next

    Foreword

    +Foreword

    Foreword
    Prev   Next

    Foreword

    When John first asked me to write an introductory piece for his latest book, I was somewhat mystified as to why he chose me. A conversation with John provided some of the rationale, and he left it to me to fill in the rest of the story. So, if you are willing to endure a little bit of background, I will diff --git a/docs/htmldocs/Samba3-HOWTO/problems.html b/docs/htmldocs/Samba3-HOWTO/problems.html index 38b16c57af..2d336a9285 100644 --- a/docs/htmldocs/Samba3-HOWTO/problems.html +++ b/docs/htmldocs/Samba3-HOWTO/problems.html @@ -1,40 +1,40 @@ -Chapter 39. Analyzing and Solving Samba Problems

    Chapter 39. Analyzing and Solving Samba Problems
    Prev Part V. Troubleshooting Next

    Chapter 39. Analyzing and Solving Samba Problems

    Gerald (Jerry) Carter

    Samba Team

    Jelmer R. Vernooij

    The Samba Team

    David Bannon

    Samba Team

    Dan Shearer

    Samba Team

    8 Apr 2003

    Table of Contents

    Diagnostics Tools
    Debugging with Samba Itself
    Tcpdump
    Ethereal
    The Windows Network Monitor
    Useful URLs
    Getting Mailing List Help
    How to Get Off the Mailing Lists

    - - - +Chapter 39. Analyzing and Solving Samba Problems

    Chapter 39. Analyzing and Solving Samba Problems
    Prev Part V. Troubleshooting Next

    Chapter 39. Analyzing and Solving Samba Problems

    Gerald (Jerry) Carter

    Samba Team

    Jelmer R. Vernooij

    The Samba Team

    David Bannon

    Samba Team

    Dan Shearer

    Samba Team

    8 Apr 2003

    Table of Contents

    Diagnostics Tools
    Debugging with Samba Itself
    Tcpdump
    Ethereal
    The Windows Network Monitor
    Useful URLs
    Getting Mailing List Help
    How to Get Off the Mailing Lists

    + + + There are many sources of information available in the form of mailing lists, RFCs, and documentation. The documentation that comes with the Samba distribution contains good explanations of general SMB topics such as browsing. -

    Diagnostics Tools

    - - - - - +

    Diagnostics Tools

    + + + + + With SMB networking, it is often not immediately clear what the cause is of a certain problem. Samba itself provides rather useful information, but in some cases you might have to fall back to using a sniffer. A sniffer is a program that listens on your LAN, analyzes the data sent on it, and displays it on the screen. -

    Debugging with Samba Itself

    - - - - - - - +

    Debugging with Samba Itself

    + + + + + + + One of the best diagnostic tools for debugging problems is Samba itself. You can use the -d option for both smbd and nmbd to specify the debug level at which to run. See the man pages for smbd, nmbd, and smb.conf for more information regarding debugging options. The debug level (log level) can range from 1 (the default) to 10 (100 for debugging passwords).

    - - - - - - - + + + + + + + Another helpful method of debugging is to compile Samba using the gcc -g flag. This will include debug information in the binaries and allow you to attach gdb to the running smbd/nmbd process. To attach gdb to an smbd process @@ -46,52 +46,52 @@ between pressing ctrl-alt-delete and actually typin gdb and continue.

    Some useful Samba commands worth investigating are: - - + + 

     $ testparm | more
 $ smbclient -L //{netbios name of server}

    -

    Tcpdump

    - - - +

    Tcpdump

    + + + Tcpdump was the first UNIX sniffer with SMB support. It is a command-line utility and now, its SMB support is somewhat lagging that of ethereal and tethereal. -

    Ethereal

    - +

    Ethereal

    + Ethereal is a graphical sniffer, available for both UNIX (Gtk) and Windows. Ethereal's SMB support is quite good. For details on the use of ethereal, read the well-written Ethereal User Guide.

    Figure 39.1. Starting a Capture.

    Starting a Capture.

    - + Listen for data on ports 137, 138, 139, and 445. For example, use the filter port 137, port 138, port 139, or port 445 as seen in Starting a Capture snapshot.

    A console version of ethereal is available as well and is called tethereal. -

    Figure 39.2. Main Ethereal Data Window.

    Main Ethereal Data Window.

    The Windows Network Monitor

    - - - - - - +

    Figure 39.2. Main Ethereal Data Window.

    Main Ethereal Data Window.

    The Windows Network Monitor

    + + + + + + For tracing things on Microsoft Windows NT, Network Monitor (aka Netmon) is available on Microsoft Developer Network CDs, the Windows NT Server install CD, and the SMS CDs. The version of Netmon that ships with SMS allows for dumping packets between any two computers (i.e., placing the network interface in promiscuous mode). 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. -

    Installing Network Monitor on an NT Workstation

    - +

    Installing Network Monitor on an NT Workstation

    + Installing Netmon on an NT workstation requires a couple of steps. The following are instructions 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 versions of Windows NT version of Netmon. You will need both the Microsoft Windows NT Server 4.0 Install CD and the Workstation 4.0 Install CD.

    - + Initially you will need to install Network Monitor Tools and Agent on the NT Server to do this:

    • Go to Start -> Settings -> Control Panel -> @@ -110,16 +110,16 @@ Network Monitor Agent from the Workstation install CD. 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. -

    Installing Network Monitor on Windows 9x/Me

    +

    Installing Network Monitor on Windows 9x/Me

    To install Netmon on Windows 9x/Me, install the Network Monitor Agent from the Windows 9x/Me CD (\admin\nettools\netmon). There is a readme file included 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. -

    Useful URLs

    • See how Scott Merrill simulates a BDC behavior at +

    Useful URLs

    Getting Mailing List Help

    + ftp://ftp.microsoft.com/developr/drg/CIFS/

    Getting Mailing List Help

    There are a number of Samba-related mailing lists. Go to http://samba.org, click on your nearest mirror, and then click on Support. Next, click on Samba-related mailing lists. @@ -130,12 +130,12 @@ It has been requested that you do not post questions about Samba-TNG to the mainstream Samba lists.

    If you do post a message to one of the lists, please observe the following guidelines:

    • - + 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 timelines are “best guess,” and nothing more.

    • - + Always mention what version of Samba you are using and what operating system it's running under. You should list the relevant sections of your smb.conf file, at least the options in [global] @@ -150,7 +150,7 @@ If you do post a message to one of the lists, please observe the following guide to mailing lists really irritate the thousands of people who end up having to deal with such bad netiquet bahavior.

    • - + Don't cross post. Work out which is the best list to post to and see what happens. Do not post to both samba-ntdom and samba-technical. Many people active on the lists subscribe to more @@ -163,7 +163,7 @@ If you do post a message to one of the lists, please observe the following guide the pipe to the error), you can send the *.CAP file as well.

    • 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 - smb.conf in their attach directory?

    How to Get Off the Mailing Lists

    To have your name removed from a Samba mailing list, go to the same + smb.conf in their attach directory?

    How to Get Off the Mailing Lists

    To have your name removed from a Samba mailing list, go to the same place where you went to subscribe to it, go to http://lists.samba.org, click on your nearest mirror, click on Support, and diff --git a/docs/htmldocs/Samba3-HOWTO/rights.html b/docs/htmldocs/Samba3-HOWTO/rights.html index 80b665ea72..13bf152d0a 100644 --- a/docs/htmldocs/Samba3-HOWTO/rights.html +++ b/docs/htmldocs/Samba3-HOWTO/rights.html @@ -1,8 +1,8 @@ -Chapter 15. User Rights and Privileges

    Chapter 15. User Rights and Privileges
    Prev Part III. Advanced Configuration Next

    Chapter 15. User Rights and Privileges

    Gerald (Jerry) Carter

    Samba Team

    John H. Terpstra

    Samba Team

    Table of Contents

    Rights Management Capabilities
    Using the “net rpc rights” Utility
    Description of Privileges
    Privileges Suppored by Windows 2000 Domain Controllers
    The Administrator Domain SID
    Common Errors
    What Rights and Privileges Will Permit Windows Client Administration?

    - - - - +Chapter 15. User Rights and Privileges

    Chapter 15. User Rights and Privileges
    Prev Part III. Advanced Configuration Next

    Chapter 15. User Rights and Privileges

    Gerald (Jerry) Carter

    Samba Team

    John H. Terpstra

    Samba Team

    Table of Contents

    Rights Management Capabilities
    Using the “net rpc rights” Utility
    Description of Privileges
    Privileges Suppored by Windows 2000 Domain Controllers
    The Administrator Domain SID
    Common Errors
    What Rights and Privileges Will Permit Windows Client Administration?

    + + + + The administration of Windows user, group, and machine accounts in the Samba domain-controlled network necessitates interfacing between the MS Windows networking environment and the UNIX operating system environment. The right @@ -10,21 +10,21 @@ networking environment and the UNIX operating system environment. The right (set) to non-administrative users both in Windows NT4 domains and Active Directory domains.

    - - - - + + + + The addition of Windows NT4/2kX/XPPro machines to the domain necessitates the creation of a machine account for each machine added. The machine account is a necessity that is used to validate that the machine can be trusted to permit user logons.

    - - - - - - + + + + + + Machine accounts are analogous to user accounts, and thus in implementing them on a UNIX machine that is hosting Samba (i.e., on which Samba is running), it is necessary to create a special type of user account. Machine accounts differ from normal user accounts in that the account name (login ID) is terminated with a @@ -34,11 +34,11 @@ log into the UNIX environment as a system user and therefore is set to have a sh account is used only to authenticate domain member machines during start-up. This security measure is designed to block man-in-the-middle attempts to violate network integrity.

    Note

    - - - - - + + + + + Machine (computer) accounts are used in the Windows NT OS family to store security credentials for domain member servers and workstations. When the domain member starts up, it goes through a validation process that includes an exchange of @@ -47,20 +47,20 @@ using the credentials known for it by domain controllers, the machine will be re all access by domain users. The computer account is essential to the way that MS Windows secures authentication.

    - - - - + + + + The creation of UNIX system accounts has traditionally been the sole right of the system administrator, better known as the root account. It is possible in the UNIX environment to create multiple users who have the same UID. Any UNIX user who has a UID=0 is inherently the same as the root account user.

    - - - - + + + + All versions of Samba call system interface scripts that permit CIFS function calls that are used to manage users, groups, and machine accounts in the UNIX environment. All versions of Samba up to and including version 3.0.10 @@ -70,27 +70,27 @@ interface scripts. The requirement to do this has understandably met with some disdain and consternation among Samba administrators, particularly where it became necessary to permit people who should not possess root-level access to the UNIX host system. -

    Rights Management Capabilities

    - - - - +

    Rights Management Capabilities

    + + + + Samba 3.0.11 introduced support for the Windows privilege model. This model allows certain rights to be assigned to a user or group SID. In order to enable this feature, enable privileges = yes must be defined in the global section of the smb.conf file.

    - - - + + + Currently, the rights supported in Samba-3 are listed in “Current Privilege Capabilities”. The remainder of this chapter explains how to manage and use these privileges on Samba servers. -

    Table 15.1. Current Privilege Capabilities

    PrivilegeDescription

    SeMachineAccountPrivilege

    Add machines to domain

    SePrintOperatorPrivilege

    Manage printers

    SeAddUsersPrivilege

    Add users and groups to the domain

    SeRemoteShutdownPrivilege

    Force shutdown from a remote system

    SeDiskOperatorPrivilege

    Manage disk share

    SeTakeOwnershipPrivilege

    Take ownership of files or other objects


    Using the “net rpc rights” Utility

    - - - - - +

    Table 15.1. Current Privilege Capabilities

    PrivilegeDescription

    SeMachineAccountPrivilege

    Add machines to domain

    SePrintOperatorPrivilege

    Manage printers

    SeAddUsersPrivilege

    Add users and groups to the domain

    SeRemoteShutdownPrivilege

    Force shutdown from a remote system

    SeDiskOperatorPrivilege

    Manage disk share

    SeTakeOwnershipPrivilege

    Take ownership of files or other objects


    Using the “net rpc rights” Utility

    + + + + + There are two primary means of managing the rights assigned to users and groups on a Samba server. The NT4 User Manager for Domains may be used from any Windows NT4, 2000, or XP Professional domain member client to @@ -101,10 +101,10 @@ performing the necessary administrative actions.

    The net rpc rights utility in Samba 3.0.11 has three new subcommands:

    list [name|accounts]

    - - - - + + + + When called with no arguments, net rpc list simply lists the available rights on the server. When passed a specific user or group name, the tool lists the privileges @@ -113,10 +113,10 @@ The net rpc rights utility in Samba 3.0.11 has thre net rpc rights list returns a list of all privileged accounts on the server and the assigned rights.

    grant <user> <right [right ...]>

    - - - - + + + + When called with no arguments, this function is used to assign a list of rights to a specified user or group. For example, to grant the members of the Domain Admins group on a Samba domain controller, @@ -126,7 +126,7 @@ The net rpc rights utility in Samba 3.0.11 has thre 'DOMAIN\Domain Admins' SeMachineAccountPrivilege

    The following syntax has the same result: - + 

     root#  net rpc rights grant 'DOMAIN\Domain Admins' \
      SeMachineAccountPrivilege -S server -U domadmin
@@ -139,66 +139,66 @@ The net rpc rights utility in Samba 3.0.11 has thre
 		This command is similar in format to net rpc rights grant.  Its
 		effect is to remove an assigned right (or list of rights) from a user or group.

    Note

    - - - + + + You must be connected as a member of the Domain Admins group to be able to grant or revoke privileges assigned to an account. This capability is inherent to the Domain Admins group and is not configurable. There are no default rights and privileges, except the ability for a member of the Domain Admins group to assign them. This means that all administrative rights and privileges (other than the ability to assign them) must be explicitly assigned, even for the Domain Admins group.

    - - - - + + + + By default, no privileges are initially assigned to any account because certain actions will be performed as root once smbd determines that a user has the necessary rights. For example, when joining a client to a Windows domain, add machine script must be executed with superuser rights in most cases. For this reason, you should be very careful about handing out privileges to accounts.

    - - - + + + Access as the root user (UID=0) bypasses all privilege checks. -

    Description of Privileges

    - - - +

    Description of Privileges

    + + + The privileges that have been implemented in Samba-3.0.11 are shown below. It is possible, and likely, that additional privileges may be implemented in later releases of Samba. It is also likely that any privileges currently implemented but not used may be removed from future releases as a housekeeping matter, so it is important that the successful as well as unsuccessful use of these facilities should be reported on the Samba mailing lists.

    SeAddUsersPrivilege

    - - - + + + This right determines whether or not smbd will allow the user to create new user or group accounts via such tools as net rpc user add or NT4 User Manager for Domains.

    SeDiskOperatorPrivilege

    - - - + + + Accounts that possess this right will be able to execute scripts defined by the add/delete/change share command in smb.conf file as root. Such users will also be able to modify the ACL associated with file shares on the Samba server.

    SeMachineAccountPrivilege

    - - - + + + This right controls whether or not the user can join client machines to a Samba-controlled domain.

    SePrintOperatorPrivilege

    - - - - - + + + + + This privilege operates identically to the printer admin option in the smb.conf file (see section 5 man page for smb.conf) except that it is a global right (not on a per-printer basis). @@ -207,44 +207,44 @@ mailing lists. the security descriptor associated with the printer object in the ntprinters.tdb file.

    SeRemoteShutdownPrivilege

    - - - + + + Samba provides two hooks for shutting down or rebooting the server and for aborting a previously issued shutdown command. Since this is an operation normally limited by the operating system to the root user, an account must possess this right to be able to execute either of these hooks.

    SeTakeOwnershipPrivilege

    - - + + This right permits users to take ownership of files and directories. -

    Privileges Suppored by Windows 2000 Domain Controllers

    +

    Privileges Suppored by Windows 2000 Domain Controllers

    For reference purposes, a Windows NT4 Primary Domain Controller reports support for the following privileges: - - - - - - - - - - - - - - - - - - - - - - - + + + + + + + + + + + + + + + + + + + + + + + 

              SeCreateTokenPrivilege  Create a token object
   SeAssignPrimaryTokenPrivilege  Replace a process level token
@@ -271,35 +271,35 @@ SeIncreaseBasePriorityPrivilege  Increase scheduling priority
       SeRemoteShutdownPrivilege  Force shutdown from a remote system

    And Windows 200x/XP Domain Controllers and workstations reports to support the following privileges: - - - - - - - - - - - - - - - - - - - - - - - - - - - - - + + + + + + + + + + + + + + + + + + + + + + + + + + + + + 

              SeCreateTokenPrivilege  Create a token object
   SeAssignPrimaryTokenPrivilege  Replace a process level token
@@ -332,15 +332,15 @@ SeIncreaseBasePriorityPrivilege  Increase scheduling priority
          SeImpersonatePrivilege  Impersonate a client after authentication
         SeCreateGlobalPrivilege  Create global objects

    - + The Samba Team is implementing only those privileges that are logical and useful in the UNIX/Linux environment. Many of the Windows 200X/XP privileges have no direct equivalence in UNIX. -

    The Administrator Domain SID

    - - - - - +

    The Administrator Domain SID

    + + + + + Please note that every Windows NT4 and later server requires a domain Administrator account. Samba versions commencing with 3.0.11 permit Administrative duties to be performed via assigned rights and privileges (see User Rights and Privileges). An account in the server's passdb backend can @@ -350,60 +350,60 @@ controller, run the following command: root# net getlocalsid SID for domain FOO is: S-1-5-21-4294955119-3368514841-2087710299

    - + You may assign the domain administrator RID to an account using the pdbedit command as shown here: - + 

     root#  pdbedit -U S-1-5-21-4294955119-3368514841-2087710299-500 -u root -r

    Note

    - - - - + + + + The RID 500 is the well known standard value of the default Administrator account. It is the RID that confers the rights and privileges that the Administrator account has on a Windows machine or domain. Under UNIX/Linux the equivalent is UID=0 (the root account).

    - - - - + + + + Releases of Samba version 3.0.11 and later make it possible to operate without an Administrator account provided equivalent rights and privileges have been established for a Windows user or a Windows group account. -

    Common Errors

    What Rights and Privileges Will Permit Windows Client Administration?

    - - - - +

    Common Errors

    What Rights and Privileges Will Permit Windows Client Administration?

    + + + + When a Windows NT4 (or later) client joins a domain, the domain global Domain Admins group is added to the membership of the local Administrators group on the client. Any user who is a member of the domain global Domain Admins group will have administrative rights on the Windows client.

    - - - - - + + + + + This is often not the most desirable solution because it means that the user will have administrative rights and privileges on domain servers also. The Power Users group on Windows client workstations permits local administration of the workstation alone. Any domain global user or domain global group can be added to the membership of the local workstation group Power Users.

    - - - - + + + + See Nested Group Support for an example of how to add domain users and groups to a local group that is on a Windows workstation. The use of the net command permits this to be done from the Samba server.

    - - - + + + Another way this can be done is to log onto the Windows workstation as the user Administrator, then open a cmd shell, then execute: 

    diff --git a/docs/htmldocs/Samba3-HOWTO/samba-bdc.html b/docs/htmldocs/Samba3-HOWTO/samba-bdc.html
index 799f6ba7cc..2a85152b51 100644
--- a/docs/htmldocs/Samba3-HOWTO/samba-bdc.html
+++ b/docs/htmldocs/Samba3-HOWTO/samba-bdc.html
@@ -1,18 +1,18 @@
-Chapter 5. Backup Domain Control
    Chapter 5. Backup Domain Control
    Prev Part II. Server Configuration Basics Next
    Chapter 5. Backup Domain Control
    John H. Terpstra
    Samba Team
    Volker Lendecke
    Samba Team
    Guenther Deschner
    LDAP updates 
    SuSE
    Table of Contents
    Features and Benefits
    Essential Background Information
    MS Windows NT4-style Domain Control
    LDAP Configuration Notes
    Active Directory Domain Control
    What Qualifies a Domain Controller on the Network?
    How Does a Workstation find its Domain Controller?
    Backup Domain Controller Configuration
    Example Configuration
    Common Errors
    Machine Accounts Keep Expiring
    Can Samba Be a Backup Domain Controller to an NT4 PDC?
    How Do I Replicate the smbpasswd File?
    Can I Do This All with LDAP?
    
+Chapter 5. Backup Domain Control
    Chapter 5. Backup Domain Control
    Prev Part II. Server Configuration Basics Next
    Chapter 5. Backup Domain Control
    John H. Terpstra
    Samba Team
    Volker Lendecke
    Samba Team
    Guenther Deschner
    LDAP updates 
    SuSE
    Table of Contents
    Features and Benefits
    Essential Background Information
    MS Windows NT4-style Domain Control
    LDAP Configuration Notes
    Active Directory Domain Control
    What Qualifies a Domain Controller on the Network?
    How Does a Workstation find its Domain Controller?
    Backup Domain Controller Configuration
    Example Configuration
    Common Errors
    Machine Accounts Keep Expiring
    Can Samba Be a Backup Domain Controller to an NT4 PDC?
    How Do I Replicate the smbpasswd File?
    Can I Do This All with LDAP?
    
 Before you continue reading this section, please make sure that you are comfortable
 with configuring a Samba domain controller as described in Domain Control.
-
    Features and Benefits
    
+
    Features and Benefits
    
 This is one of the most difficult chapters to summarize. It does not matter what we say here, for someone will
 still draw conclusions and/or approach the Samba Team with expectations that are either not yet capable of
 being delivered or that can be achieved far more effectively using a totally different approach. In the event
 that you should have a persistent concern that is not addressed in this book, please email John H. Terpstra clearly setting out your requirements and/or question, and
 we will do our best to provide a solution.
 
    
-
-
-
-
-
+
+
+
+
+
 Samba-3 can act as a Backup Domain Controller (BDC) to another Samba Primary Domain Controller (PDC). A
 Samba-3 PDC can operate with an LDAP account backend. The LDAP backend can be either a common master LDAP
 server or a slave server. The use of a slave LDAP server has the benefit that when the master is down, clients
@@ -21,22 +21,22 @@ an effective solution for large organizations. If you use an LDAP slave server f
 ensure the master's continued availability  if the slave finds its master down at the wrong time,
 you will have stability and operational problems.
 
    
-
-
-
-
+
+
+
+
 While it is possible to run a Samba-3 BDC with a non-LDAP backend, that backend must allow some form of
 "two-way" propagation of changes from the BDC to the master.  At this time only LDAP delivers the capability
 to propagate identity database changes from the BDC to the PDC. The BDC can use a slave LDAP server, while it
 is preferable for the PDC to use as its primary an LDAP master server.
 
    
-
-
-
+
 
-
-
-
+
+
+
+
+
 The use of a non-LDAP backend SAM database is particularly problematic because domain member
 servers and workstations periodically change the Machine Trust Account password. The new
 password is then stored only locally. This means that in the absence of a centrally stored
@@ -46,10 +46,10 @@ PDC (master) copy of the SAM. If the PDC SAM is then replicated to BDCs, this re
 overwriting the SAM that contains the updated (changed) trust account password with resulting
 breakage of the domain trust.
 
    
-
-
-
-
+
+
+
+
 Considering the number of comments and questions raised concerning how to configure a BDC,
 let's consider each possible option and look at the pros and cons for each possible solution.
 The Domain Backend Account Distribution Options table below lists 
@@ -70,30 +70,30 @@ possible design configurations for a PDC/BDC infrastructure.
 	Not an elegant solution due to the delays in synchronization
         and also suffers
         from the issue of domain trust breakdown.
-	

    Essential Background Information
    
-
-
-
+

    Essential Background Information

    + + + A domain controller is a machine that is able to answer logon requests from network workstations. Microsoft LanManager and IBM LanServer were two early products that provided this capability. The technology has become known as the LanMan Netlogon service.

    - - + + When MS Windows NT3.10 was first released, it supported a new style of Domain Control and with it a new form of the network logon service that has extended functionality. This service became known as the NT NetLogon Service. The nature of this service has changed with the evolution of MS Windows NT and today provides a complex array of services that are implemented over an intricate spectrum of technologies. -

    MS Windows NT4-style Domain Control

    - - - +

    MS Windows NT4-style Domain Control

    - - + + + + + Whenever a user logs into a Windows NT4/200x/XP Professional workstation, the workstation connects to a domain controller (authentication server) to validate that the username and password the user entered are valid. If the information entered @@ -101,11 +101,11 @@ does not match account information that has been stored in the domain control database (the SAM, or Security Account Manager database), a set of error codes is returned to the workstation that has made the authentication request.

    - - - + + + When the username/password pair has been validated, the domain controller (authentication server) will respond with full enumeration of the account information that has been stored regarding that user in the user and machine accounts database @@ -117,11 +117,11 @@ network access time limits, account validity information, machine names from whi user may access the network, and much more. All this information was stored in the SAM in all versions of MS Windows NT (3.10, 3.50, 3.51, 4.0).

    - - - - - + + + + + The account information (user and machine) on domain controllers is stored in two files, one containing the security information and the other the SAM. These are stored in files by the same name in the %SystemRoot%\System32\config directory. @@ -131,24 +131,24 @@ on the network.

    There are two situations in which it is desirable to install BDCs:

    • - - + + On the local network that the PDC is on, if there are many workstations and/or where the PDC is generally very busy. In this case the BDCs will pick up network logon requests and help to add robustness to network services.

    • - + At each remote site, to reduce wide-area network traffic and to add stability to remote network operations. The design of the network, and the strategic placement of BDCs, together with an implementation that localizes as much of network to client interchange as possible, will help to minimize wide-area network bandwidth needs (and thus costs).

    - - - - + + + + The interoperation of a PDC and its BDCs in a true Windows NT4 environment is worth mentioning here. The PDC contains the master copy of the SAM. In the event that an administrator makes a change to the user account database while physically present @@ -160,50 +160,50 @@ of SAM synchronization. The PDC will then request the delta from the BDC and app it to the master SAM. The PDC will then contact all the BDCs in the domain and trigger them to obtain the update and then apply that to their own copy of the SAM.

    - - - - + + + + Samba-3 cannot participate in true SAM replication and is therefore not able to employ precisely the same protocols used by MS Windows NT4. A Samba-3 BDC will not create SAM update delta files. It will not interoperate with a PDC (NT4 or Samba) to synchronize the SAM from delta files that are held by BDCs.

    - - + + Samba-3 cannot function as a BDC to an MS Windows NT4 PDC, and Samba-3 cannot function correctly as a PDC to an MS Windows NT4 BDC. Both Samba-3 and MS Windows NT4 can function as a BDC to its own type of PDC.

    - - - + + + The BDC is said to hold a read-only of the SAM from which it is able to process network logon requests and authenticate users. The BDC can continue to provide this service, particularly while, for example, the wide-area network link to the PDC is down. A BDC plays a very important role in both the maintenance of domain security as well as in network integrity.

    - - - + + + In the event that the NT4 PDC should need to be taken out of service, or if it dies, one of the NT4 BDCs can be promoted to a PDC. If this happens while the original NT4 PDC is online, it is automatically demoted to an NT4 BDC. This is an important aspect of domain controller management. The tool that is used to effect a promotion or a demotion is the Server Manager for Domains. It should be noted that Samba-3 BDCs cannot be promoted in this manner because reconfiguration of Samba requires changes to the smb.conf file. It is easy enough to manuall change the smb.conf file and then restart relevant Samba network services. -

    Example PDC Configuration

    - - +

    Example PDC Configuration

    + + Beginning with Version 2.2, Samba officially supports domain logons for all current Windows clients, including Windows NT4, 2003, and XP Professional. For Samba to be enabled as a PDC, some parameters in the [global] section of the smb.conf have to be set. Refer to the Minimal smb.conf for a PDC in Use with a BDC LDAP Server on PDC section for an example of the minimum required settings. -

    Example 5.1. Minimal smb.conf for a PDC in Use with a BDC LDAP Server on PDC

    workgroup = MIDEARTH
    passdb backend = ldapsam://localhost:389
    domain master = yes
    domain logons = yes
    ldap suffix = dc=quenya,dc=org
    ldap user suffix = ou=Users
    ldap group suffix = ou=Groups
    ldap machine suffix = ou=Computers
    ldap idmap suffix = ou=Idmap
    ldap admin dn = cn=sambadmin,dc=quenya,dc=org

    - - +

    Example 5.1. Minimal smb.conf for a PDC in Use with a BDC LDAP Server on PDC

    workgroup = MIDEARTH
    passdb backend = ldapsam://localhost:389
    domain master = yes
    domain logons = yes
    ldap suffix = dc=quenya,dc=org
    ldap user suffix = ou=Users
    ldap group suffix = ou=Groups
    ldap machine suffix = ou=Computers
    ldap idmap suffix = ou=Idmap
    ldap admin dn = cn=sambadmin,dc=quenya,dc=org

    + + Several other things like a [homes] and a [netlogon] share also need to be set along with settings for the profile path, the user's home drive, and so on. This is not covered in this chapter; for more information please refer to Domain Control. @@ -211,34 +211,34 @@ Refer to book “Samba-3 by Example” that may be obtained from local and on-line book stores. -

    LDAP Configuration Notes

    - - - +

    LDAP Configuration Notes

    + + + When configuring a master and a slave LDAP server, it is advisable to use the master LDAP server for the PDC and slave LDAP servers for the BDCs. It is not essential to use slave LDAP servers; however, many administrators will want to do so in order to provide redundant services. Of course, one or more BDCs may use any slave LDAP server. Then again, it is entirely possible to use a single LDAP server for the entire network.

    - - - - - + + + + + When configuring a master LDAP server that will have slave LDAP servers, do not forget to configure this in the /etc/openldap/slapd.conf file. It must be noted that the DN of a server certificate must use the CN attribute to name the server, and the CN must carry the servers' fully qualified domain name. Additional alias names and wildcards may be present in the subjectAltName certificate extension. More details on server certificate names are in RFC2830.

    - - - - - - - + + + + + + + It does not really fit within the scope of this document, but a working LDAP installation is basic to LDAP-enabled Samba operation. When using an OpenLDAP server with Transport Layer Security (TLS), the machine name in /etc/ssl/certs/slapd.pem must be the same as in @@ -247,12 +247,12 @@ name in /etc/ssl/certs/slapd.pem must be the same access this LDAP server from a slave LDAP server (i.e., a Samba BDC) unless the certificate is re-created with a correct hostname.

    - - - - + + + + Do not install a Samba PDC so that is uses an LDAP slave server. Joining client machines to the domain will fail in this configuration because the change to the machine account in the LDAP tree must take place on the master LDAP server. This is not replicated rapidly enough to the slave server that the PDC queries. It @@ -279,23 +279,23 @@ Possible PDC/BDC plus LDAP configurations include: In order to have a fallback configuration (secondary) LDAP server, you would specify the secondary LDAP server in the smb.conf file as shown in the Multiple LDAP Servers in smb.conf example. -

    Example 5.2. Multiple LDAP Servers in smb.conf

    passdb backend = ldapsam:"ldap://master.quenya.org ldap://slave.quenya.org"

    Active Directory Domain Control

    - - - - - +

    Example 5.2. Multiple LDAP Servers in smb.conf

    passdb backend = ldapsam:"ldap://master.quenya.org ldap://slave.quenya.org"

    Active Directory Domain Control

    + + + + + As of the release of MS Windows 2000 and Active Directory, this information is now stored in a directory that can be replicated and for which partial or full administrative control can be delegated. Samba-3 is not able to be a domain controller within an Active Directory tree, and it cannot be an Active Directory server. This means that Samba-3 also cannot act as a BDC to an Active Directory domain controller. -

    What Qualifies a Domain Controller on the Network?

    - - - - +

    What Qualifies a Domain Controller on the Network?

    + + + + Every machine that is a domain controller for the domain MIDEARTH has to register the NetBIOS group name MIDEARTH<1C> with the WINS server and/or by broadcast on the local network. The PDC also registers the unique NetBIOS name MIDEARTH<1B> with the WINS server. @@ -303,30 +303,30 @@ The name type <1B> name is normally reserved for the Domain Master Browser that has nothing to do with anything related to authentication, but the Microsoft domain implementation requires the DMB to be on the same machine as the PDC.

    - - - + + + Where a WINS server is not used, broadcast name registrations alone must suffice. Refer to Network Browsing,Discussion for more information regarding TCP/IP network protocols and how SMB/CIFS names are handled. -

    How Does a Workstation find its Domain Controller?

    - - +

    How Does a Workstation find its Domain Controller?

    + + There are two different mechanisms to locate a domain controller: one method is used when NetBIOS over TCP/IP is enabled and the other when it has been disabled in the TCP/IP network configuration.

    - - + + Where NetBIOS over TCP/IP is disabled, all name resolution involves the use of DNS, broadcast messaging over UDP, as well as Active Directory communication technologies. In this type of environment all machines require appropriate DNS entries. More information may be found in DNS and Active Directory. -

    NetBIOS Over TCP/IP Enabled

    - - - +

    NetBIOS Over TCP/IP Enabled

    + + + An MS Windows NT4/200x/XP Professional workstation in the domain MIDEARTH that wants a local user to be authenticated has to find the domain controller for MIDEARTH. It does this by doing a NetBIOS name query for the group name MIDEARTH<1C>. It assumes that each @@ -334,26 +334,26 @@ of the machines it gets back from the queries is a domain controller and can ans requests. To not open security holes, both the workstation and the selected domain controller authenticate each other. After that the workstation sends the user's credentials (name and password) to the local domain controller for validation. -

    NetBIOS Over TCP/IP Disabled

    - - - +

    NetBIOS Over TCP/IP Disabled

    + + + An MS Windows NT4/200x/XP Professional workstation in the realm quenya.org that has a need to affect user logon authentication will locate the domain controller by re-querying DNS servers for the _ldap._tcp.pdc._msdcs.quenya.org record. More information regarding this subject may be found in DNS and Active Directory. -

    Backup Domain Controller Configuration

    - +

    Backup Domain Controller Configuration

    + The creation of a BDC requires some steps to prepare the Samba server before smbd is executed for the first time. These steps are as follows:

    • - - - - + - + + + + The domain SID has to be the same on the PDC and the BDC. In Samba versions pre-2.2.5, the domain SID was stored in the file private/MACHINE.SID. For all versions of Samba released since 2.2.5 the domain SID is stored in the file private/secrets.tdb. This file is unique to each @@ -361,19 +361,19 @@ The creation of a BDC requires some steps to prepare the Samba server before the PDC domain SID with the newly created BDC SID. There is a procedure that will allow the BDC to aquire the domain SID. This is described here.

      - - - - - + + + + + To retrieve the domain SID from the PDC or an existing BDC and store it in the secrets.tdb, execute: 

       root# net rpc getsid

    • - - - + + + Specification of the ldap admin dn is obligatory. This also requires the LDAP administration password to be set in the secrets.tdb using the smbpasswd -w mysecret. @@ -381,10 +381,10 @@ The creation of a BDC requires some steps to prepare the Samba server before The ldap suffix parameter and the ldap idmap suffix parameter must be specified in the smb.conf file.

    • - - - - + + + + The UNIX user database has to be synchronized from the PDC to the BDC. This means that both the /etc/passwd and /etc/group have to be replicated from the PDC @@ -395,14 +395,14 @@ The creation of a BDC requires some steps to prepare the Samba server before a PDC failure. NIS is by no means the only method to synchronize passwords. An LDAP solution would also work.

    • - - - - + - - + + + + + The Samba password database must be replicated from the PDC to the BDC. Although it is possible to synchronize the smbpasswd file with rsync and ssh, this method @@ -417,63 +417,63 @@ The creation of a BDC requires some steps to prepare the Samba server before intervals administrators are not normally aware that this is happening or when it takes place.

      - - - + + + The use of LDAP for both the POSIX (UNIX user and group) accounts and for the SambaSAMAccount data automatically ensures that all account change information will be written to the shared directory. This eliminates the need for any special action to synchronize account information because LDAP will meet that requirement.

    • - - - - - + + + + + The netlogon share has to be replicated from the PDC to the BDC. This can be done manually whenever login scripts are changed, or it can be done automatically using a cron job that will replicate the directory structure in this share using a tool like rsync. The use of rsync for replication of the netlogon data is not critical to network security and is one that can be manually managed given that the administrator will make all changes to the netlogon share as part of a conscious move. -

    Example Configuration

    +

    Example Configuration

    Finally, the BDC has to be capable of being found by the workstations. This can be done by configuring the Samba smb.conf file [global] section as shown in Minimal Setup for Being a BDC. -

    Example 5.3. Minimal Setup for Being a BDC

    workgroup = MIDEARTH
    passdb backend = ldapsam:ldap://slave-ldap.quenya.org
    domain master = no
    domain logons = yes
    ldap suffix = dc=abmas,dc=biz
    ldap user suffix = ou=Users
    ldap group suffix = ou=Groups
    ldap machine suffix = ou=Computers
    ldap idmap suffix = ou=Idmap
    ldap admin dn = cn=sambadmin,dc=quenya,dc=org
    idmap backend = ldap:ldap://master-ldap.quenya.org
    idmap uid = 10000-20000
    idmap gid = 10000-20000

    +

    Example 5.3. Minimal Setup for Being a BDC

    workgroup = MIDEARTH
    passdb backend = ldapsam:ldap://slave-ldap.quenya.org
    domain master = no
    domain logons = yes
    ldap suffix = dc=abmas,dc=biz
    ldap user suffix = ou=Users
    ldap group suffix = ou=Groups
    ldap machine suffix = ou=Computers
    ldap idmap suffix = ou=Idmap
    ldap admin dn = cn=sambadmin,dc=quenya,dc=org
    idmap backend = ldap:ldap://master-ldap.quenya.org
    idmap uid = 10000-20000
    idmap gid = 10000-20000

    Fully documented working example network configurations using OpenLDAP and Samba as available in the book “Samba-3 by Example” that may be obtained from local and on-line book stores.

    - - - - + + + + This configuration causes the BDC to register only the name MIDEARTH<1C> with the WINS server. This is not a problem, as the name MIDEARTH<1C> is a NetBIOS group name that is meant to be registered by more than one machine. The parameter domain master = no forces the BDC not to register MIDEARTH<1B>, which is a unique NetBIOS name that is reserved for the PDC.

    - - - - - + + - - + + + + + The idmap backend will redirect the winbindd utility to use the LDAP database to store all mappings for Windows SIDs to UIDs and GIDs for UNIX accounts in a repository that is shared. The BDC will however depend on local resolution of UIDs and GIDs via NSS and the nss_ldap utility.

    Note

    - - - - + + + + Samba-3 has introduced a new ID mapping facility. One of the features of this facility is that it allows greater flexibility in how user and group IDs are handled in respect to NT domain user and group SIDs. One of the new facilities provides for explicitly ensuring that UNIX/Linux UID and GID values @@ -481,27 +481,27 @@ will be consistent on the PDC, all BDCs, and all domain member servers. The para is called idmap backend. Please refer to the man page for smb.conf for more information regarding its behavior.

    - - - + + + The use of the idmap backend = ldap:ldap://master.quenya.org option on a BDC only makes sense where ldapsam is used on a PDC. The purpose of an LDAP-based idmap backend is also to allow a domain member (without its own passdb backend) to use winbindd to resolve Windows network users and groups to common UID/GIDs. In other words, this option is generally intended for use on BDCs and on domain member servers. -

    Common Errors

    - +

    Common Errors

    + Domain control was a new area for Samba, but there are now many examples that we may refer to. Updated information will be published as they become available and may be found in later Samba releases or from the Samba Web site; refer in particular to the WHATSNEW.txt in the Samba release tarball. The book, “Samba-3 by Example” documents well tested and proven configuration examples. You can obtain a copy of this book for the Samba web site. -

    Machine Accounts Keep Expiring

    - - - - +

    Machine Accounts Keep Expiring

    + + + + This problem will occur when the passdb (SAM) files are copied from a central server but the local BDC is acting as a PDC. This results in the application of Local Machine Trust Account password updates to the local SAM. Such updates @@ -513,43 +513,43 @@ to proceed and the account expiry error will be reported.

    The solution is to use a more robust passdb backend, such as the ldapsam backend, setting up a slave LDAP server for each BDC and a master LDAP server for the PDC. -

    Can Samba Be a Backup Domain Controller to an NT4 PDC?

    - - +

    Can Samba Be a Backup Domain Controller to an NT4 PDC?

    + + No. The native NT4 SAM replication protocols have not yet been fully implemented.

    - - - + + + Can I get the benefits of a BDC with Samba? Yes, but only to a Samba PDC.The main reason for implementing a BDC is availability. If the PDC is a Samba machine, a second Samba machine can be set up to service logon requests whenever the PDC is down. -

    How Do I Replicate the smbpasswd File?

    - - - +

    How Do I Replicate the smbpasswd File?

    + + + Replication of the smbpasswd file is sensitive. It has to be done whenever changes to the SAM are made. Every user's password change is done in the smbpasswd file and has to be replicated to the BDC. So replicating the smbpasswd file very often is necessary.

    - - - + + + As the smbpasswd file contains plaintext password equivalents, it must not be sent unencrypted over the wire. The best way to set up smbpasswd replication from the PDC to the BDC is to use the utility rsync. rsync can use ssh as a transport. ssh itself can be set up to accept only rsync transfer without requiring the user to type a password.

    - - + + As said a few times before, use of this method is broken and flawed. Machine trust accounts will go out of sync, resulting in a broken domain. This method is not recommended. Try using LDAP instead. -

    Can I Do This All with LDAP?

    - - +

    Can I Do This All with LDAP?

    + + The simple answer is yes. Samba's pdb_ldap code supports binding to a replica LDAP server and will also follow referrals and rebind to the master if it ever needs to make a modification to the database. (Normally BDCs are read-only, so diff --git a/docs/htmldocs/Samba3-HOWTO/samba-pdc.html b/docs/htmldocs/Samba3-HOWTO/samba-pdc.html index fff0a47ea9..3f33f293a7 100644 --- a/docs/htmldocs/Samba3-HOWTO/samba-pdc.html +++ b/docs/htmldocs/Samba3-HOWTO/samba-pdc.html @@ -1,10 +1,10 @@ -Chapter 4. Domain Control

    Chapter 4. Domain Control
    Prev Part II. Server Configuration Basics Next

    Chapter 4. Domain Control

    John H. Terpstra

    Samba Team

    Gerald (Jerry) Carter

    Samba Team

    David Bannon

    Samba Team

    Guenther Deschner

    LDAP updates 
    SuSE

    Table of Contents

    Features and Benefits
    Single Sign-On and Domain Security
    Basics of Domain Control
    Domain Controller Types
    Preparing for Domain Control
    Domain Control: Example Configuration
    Samba ADS Domain Control
    Domain and Network Logon Configuration
    Domain Network Logon Service
    Security Mode and Master Browsers
    Common Errors
    “$” Cannot Be Included in Machine Name
    Joining Domain Fails Because of Existing Machine Account
    The System Cannot Log You On (C000019B)
    The Machine Trust Account Is Not Accessible
    Account Disabled
    Domain Controller Unavailable
    Cannot Log onto Domain Member Workstation After Joining Domain

    +Chapter 4. Domain Control

    Chapter 4. Domain Control
    Prev Part II. Server Configuration Basics Next

    Chapter 4. Domain Control

    John H. Terpstra

    Samba Team

    Gerald (Jerry) Carter

    Samba Team

    David Bannon

    Samba Team

    Guenther Deschner

    LDAP updates 
    SuSE

    Table of Contents

    Features and Benefits
    Single Sign-On and Domain Security
    Basics of Domain Control
    Domain Controller Types
    Preparing for Domain Control
    Domain Control: Example Configuration
    Samba ADS Domain Control
    Domain and Network Logon Configuration
    Domain Network Logon Service
    Security Mode and Master Browsers
    Common Errors
    “$” Cannot Be Included in Machine Name
    Joining Domain Fails Because of Existing Machine Account
    The System Cannot Log You On (C000019B)
    The Machine Trust Account Is Not Accessible
    Account Disabled
    Domain Controller Unavailable
    Cannot Log onto Domain Member Workstation After Joining Domain

    There are many who approach MS Windows networking with incredible misconceptions. That's okay, because it gives the rest of us plenty of opportunity to be of assistance. Those who really want help are well advised to become familiar with information that is already available.

    - + You are advised not to tackle this section without having first understood and mastered some basics. MS Windows networking is not particularly forgiving of misconfiguration. Users of MS Windows networking are likely to complain @@ -32,14 +32,14 @@ organization. Where is the right place to make mistakes? Only out of harms way. If you are going to make mistakes, then please do it on a test network, away from users, and in such a way as to not inflict pain on others. Do your learning on a test network. -

    Features and Benefits

    - +

    Features and Benefits

    + What is the key benefit of Microsoft Domain Security?

    - - - - + + + + In a word, single sign-on, or SSO for short. To many, this is the Holy Grail of MS Windows NT and beyond networking. SSO allows users in a well-designed network to log onto any workstation that is a member of the domain that contains their user account (or in a domain that has an appropriate trust @@ -47,24 +47,24 @@ relationship with the domain they are visiting) and they will be able to log ont resources (shares, files, and printers) as if they are sitting at their home (personal) workstation. This is a feature of the domain security protocols.

    - - - - + + + + The benefits of domain security are available to those sites that deploy a Samba PDC. A domain provides a unique network security identifier (SID). Domain user and group security identifiers are comprised of the network SID plus a relative identifier (RID) that is unique to the account. User and group SIDs (the network SID plus the RID) can be used to create access control lists (ACLs) attached to network resources to provide organizational access control. UNIX systems recognize only local security identifiers.

    - + A SID represents a security context. For example, every Windows machine has local accounts within the security context of the local machine which has a unique SID. Every domain (NT4, ADS, Samba) contains accounts that exist within the domain security context which is defined by the domain SID.

    - - + + A domain member server will have a SID that differs from the domain SID. The domain member server can be configured to regard all domain users as local users. It can also be configured to recognize domain users and groups as non-local. SIDs are persistent. A typical domain of user SID looks like this: @@ -82,9 +82,9 @@ S-1-5-21-726309263-4128913605-1168186429-500

    The result is that every account in the Windows networking world has a globally unique security identifier.

    Note

    - - - + + + Network clients of an MS Windows domain security environment must be domain members to be able to gain access to the advanced features provided. Domain membership involves more than just setting the workgroup name to the domain name. It requires the creation of a domain trust account for the workstation (called a machine @@ -92,44 +92,44 @@ account). Refer to

    • - + Samba-3 supports the use of a choice of backends that may be used in which user, group and machine accounts may be stored. Multiple passwd backends can be used in combination, either as additive backend data sets, or as fail-over data sets.

      - - - - - + + + + + An LDAP passdb backend confers the benefit that the account backend can be distributed and replicated, which is of great value because it confers scalability and provides a high degree of reliability.

    • - - - + + + Windows NT4 domain trusts. Samba-3 supports workstation and server (machine) trust accounts. It also supports Windows NT4 style interdomain trust accounts, which further assists in network scalability and interoperability.

    • - - - - - + + + + + Operation without NetBIOS over TCP/IP, rather using the raw SMB over TCP/IP. Note, this is feasible only when operating as a Microsoft active directory domain member server. When acting as a Samba domain controller the use of NetBIOS is necessary to provide network browsing support.

    • - - - + + + Samba-3 provides NetBIOS name services (WINS), NetBIOS over TCP/IP (TCP port 139) session services, SMB over TCP/IP (TCP port 445) session services, and Microsoft compatible ONC DCE RPC services (TCP port 135) services.

    • - + Management of users and groups via the User Manager for Domains. This can be done on any MS Windows client using the Nexus.exe toolkit for Windows 9x/Me, or using the SRVTOOLS.EXE package for MS Windows NT4/200x/XP platforms. These packages are available from Microsoft's Web site. @@ -139,55 +139,55 @@ The following functionalities are new to the Samba-3 release:

    The following functionalities are not provided by Samba-3:

    • - - + + SAM replication with Windows NT4 domain controllers (i.e., a Samba PDC and a Windows NT BDC, or vice versa). This means Samba cannot operate as a BDC when the PDC is Microsoft-based Windows NT PDC. Samba-3 can not participate in replication of account data to Windows PDCs and BDCs.

    • - - + + Acting as a Windows 2000 active directory domain controller (i.e., Kerberos and Active Directory). In point of fact, Samba-3 does have some Active Directory domain control ability that is at this time purely experimental. Active directory domain control is one of the features that is being developed in Samba-4, the next generation Samba release. At this time there are no plans to enable active directory domain control support during the Samba-3 series life-cycle.

    • - - - + + + The Windows 200x/XP Microsoft Management Console (MMC) cannot be used to manage a Samba-3 server. For this you can use only the MS Windows NT4 Domain Server Manager and the MS Windows NT4 Domain User Manager. Both are part of the SVRTOOLS.EXE package mentioned later.

    - - + + Windows 9x/Me/XP Home clients are not true members of a domain for reasons outlined in this chapter. The protocol for support of Windows 9x/Me-style network (domain) logons is completely different from NT4/Windows 200x-type domain logons and has been officially supported for some time. These clients use the old LanMan network logon facilities that are supported in Samba since approximately the Samba-1.9.15 series.

    - + Samba-3 implements group mapping between Windows NT groups and UNIX groups (this is really quite complicated to explain in a short space). This is discussed more fully in Group Mapping: MS Windows and UNIX.

    - - - + + + Samba-3, like an MS Windows NT4 PDC or a Windows 200x Active Directory, needs to store user and Machine Trust Account information in a suitable backend data-store. Refer to MS Windows Workstation/Server Machine Trust Accounts. With Samba-3 there can be multiple backends for this. A complete discussion of account database backends can be found in Account Information Databases. -

    Single Sign-On and Domain Security

    - - - - - - - +

    Single Sign-On and Domain Security

    + + + + + + + When network administrators are asked to describe the benefits of Windows NT4 and active directory networking the most often mentioned feature is that of single sign-on (SSO). Many companies have implemented SSO solutions. The mode of implementation of a single sign-on solution is an important factor in the practice of @@ -197,16 +197,16 @@ uncommon that users may need to remember more than ten login IDs and passwords. when the password for each system must be changed at regular intervals, and particularly so where password uniqueness and history limits are applied.

    - + There is a broadly held perception that SSO is the answer to the problem of users having to deal with too many information system access credentials (username/password pairs). Many elaborate schemes have been devised to make it possible to deliver a user-friendly SSO solution. The trouble is that if this implementation is not done correctly, the site may end up paying dearly by way of complexity and management overheads. Simply put, many SSO solutions are an administrative nightmare.

    - - - + + + SSO implementations utilize centralization of all user account information. Depending on environmental complexity and the age of the systems over which a SSO solution is implemented, it may not be possible to change the solution architecture so as to accomodate a new identity management and user authentication system. @@ -215,11 +215,11 @@ behalf of the user. The software that gets layered over the old system may simpl authentication system. This means that the addition of SSO increases over-all information systems complexity. Ideally, the implementation of SSO should reduce complexity and reduce administative overheads.

    - - - + - + + + The initial goal of many network administrators is often to create and use a centralized identity management system. It is often assumed that such a centralized system will use a single authentication infrastructure that can be used by all information systems. The Microsoft Windows NT4 security domain architecture and the @@ -232,14 +232,14 @@ system it uses because its implementation will be excessively invasive from a re because application software has built-in dependencies on particular elements of the way user authentication and access control were designed and built.

    - - - - - - + + + - + + + + Over the past decade an industry has been developed around the various methods that have been built to get around the key limitations of legacy information technology systems. One approach that is often used involves the use of a meta-directory. The meta-directory stores user credentials for all disparate information systems @@ -248,22 +248,22 @@ rigidly enforced work-flow protocol for managing user rights and privileges with are provisioned by the new infrastructure makes possible user access to all systems using a single set of user credentials.

    - - - - + + + + The Organization for the Advancement of Structured Information Standards (OASIS) has developed the Security Assertion Markup Language (SAML), a structured method for communication of authentication information. The over-all umbrella name for the technologies and methods that deploy SAML is called Federated Identity Management (FIM). FIM depends on each system in the complex maze of disparate information systems to authenticate their respective users and vouch for secure access to the services each provides.

    - - - - - - + + + + + + SAML documents can be wrapped in a Simple Object Access Protocol (SOAP) message for the computer-to-computer communications needed for Web services. Or they may be passed between Web servers of federated organizations that share live services. The Liberty Alliance, an industry group formed to promote federated-identity @@ -273,11 +273,11 @@ converge when the SAML 2.0 standard is introduced. A few Web access-management p but implemention of the technology mostly requires customization to integrate applications and develop user interfaces. In a nust-shell, that is why FIM is a big and growing industry.

    - - - - + + + + Ignoring the bigger picture, which is beyond the scope of this book, the migration of all user and group management to a centralized system is a step in the right direction. It is essential for interoperability reasons to locate the identity management system data in a directory such as Microsoft Active Directory @@ -286,20 +286,20 @@ access (such as LDAP) and that can be coupled with a flexible array of authentic kerberos) that use the protocols that are defined by the various general security service application programming interface (GSSAPI) services.

    - - - + + + A growing number of companies provide authentication agents for disparate legacy platforms to permit the use of LDAP systems. Thus the use of OpenLDAP, the dominant open source software implementation of the light weight directory access protocol standard. This fact, means that by providing support in Samba for the use of LDAP and Microsoft ADS make Samba a highly scalable and forward reaching organizational networking technology.

    - - - - - + + + + + Microsoft ADS provides purely proprietary services that, with limitation, can be extended to provide a centralized authentication infrastructure. Samba plus LDAP provides a similar opportunity for extension of a centralized authentication architecture, but it is the fact that the Samba Team are pro-active in introducing @@ -307,29 +307,29 @@ the extension of authentication services, using LDAP or otherwise, to applicatio source proxy server) through tools such as the ntlm_auth utility, that does much to create sustainable choice and competition in the FIM market place.

    - - - + + + Primary domain control, if it is to be scalable to meet the needs of large sites, must therefore be capable of using LDAP. The rapid adoption of OpenLDAP, and Samba configurations that use it, is ample proof that the era of the directory has started. Samba-3 does not demand the use of LDAP, but the demand for a mechanism by which user and group identity information can be distributed makes it an an unavoidable option.

    - - - + + + At this time, the use of Samba based BDCs, necessitates the use of LDAP. The most commonly used LDAP implementation used by Samba sites is OpenLDAP. It is possible to use any standards compliant LDAP server. Those known to work includes those manufactured by: IBM, CA, Novell (e-Directory), and others. -

    Basics of Domain Control

    - +

    Basics of Domain Control

    + Over the years, public perceptions of what domain control really is has taken on an almost mystical nature. Before we branch into a brief overview of domain control, there are three basic types of domain controllers. -

    Domain Controller Types

    • NT4 style Primary Domain Controller

    • NT4 style Backup Domain Controller

    • ADS Domain Controller

    - - - - +

    Domain Controller Types

    • NT4 style Primary Domain Controller

    • NT4 style Backup Domain Controller

    • ADS Domain Controller

    + + + + The Primary Domain Controller or PDC plays an important role in MS Windows NT4. In Windows 200x domain control architecture, this role is held by domain controllers. Folklore dictates that because of its role in the MS Windows network, the domain controller should be the most powerful and most @@ -337,37 +337,37 @@ capable machine in the network. As strange as it may seem to say this here, goo dictates that the entire infrastructure needs to be balanced. It is advisable to invest more in standalone (domain member) servers than in the domain controllers.

    - - - - + + + + In the case of MS Windows NT4-style domains, it is the PDC that initiates a new domain control database. This forms a part of the Windows registry called the Security Account Manager (SAM). It plays a key part in NT4-type domain user authentication and in synchronization of the domain authentication database with BDCs.

    - - - - + + + + With MS Windows 200x Server-based Active Directory domains, one domain controller initiates a potential hierarchy of domain controllers, each with its own area of delegated control. The master domain controller has the ability to override any downstream controller, but a downline controller has control only over its downline. With Samba-3, this functionality can be implemented using an LDAP-based user and machine account backend.

    - - + + New to Samba-3 is the ability to use a backend database that holds the same type of data as the NT4-style SAM -database (one of the registry files)[1] +database (one of the registry files)[1]

    - - - - - + + + + + The Backup Domain Controller or BDC plays a key role in servicing network authentication requests. The BDC is biased to answer logon requests in preference to the PDC. On a network segment that has a BDC and a PDC, the BDC will most likely service network logon requests. The PDC will answer network logon @@ -379,13 +379,13 @@ the UDP broadcast protocol. This means that the netlogon server that the windows by a number of variables, thus there is no simple determinant of whether a PDC or a BDC will serve a particular logon authentication request.

    - - + + A Windows NT4 BDC can be promoted to a PDC. If the PDC is online at the time that a BDC is promoted to PDC, the previous PDC is automatically demoted to a BDC. With Samba-3, this is not an automatic operation; the PDC and BDC must be manually configured, and other appropriate changes also need to be made.

    - + With MS Windows NT4, a decision is made at installation to determine what type of machine the server will be. It is possible to promote a BDC to a PDC, and vice versa. The only method Microsoft provide to convert a Windows NT4 domain controller to a domain member server or a standalone server is to reinstall it. The install @@ -393,28 +393,28 @@ time choices offered are:

    • Primary Domain Controller the one that seeds the domain SAM.

    • Backup Domain Controller one that obtains a copy of the domain SAM.

    • Domain Member Server one that has no copy of the domain SAM; rather it obtains authentication from a domain controller for all access controls.

    • Standalone Server one that plays no part in SAM synchronization, has its own authentication database, and plays no role in domain security.

    Note

    - + Algin Technology LLC provide a commercial tool that makes it possible to promote a Windows NT4 standalone server to a PDC or a BDC, and also permits this process to be reversed. Refer to the Algin web site for further information.

    - - + + Samba-3 servers can readily be converted to and from domain controller roles through simple changes to the smb.conf file. Samba-3 is capable of acting fully as a native member of a Windows 200x server Active Directory domain.

    - + For the sake of providing a complete picture, MS Windows 2000 domain control configuration is done after the server has been installed. Please refer to Microsoft documentation for the procedures that should be followed to convert a domain member server to or from a domain control, and to install or remove active directory service support.

    - - + + New to Samba-3 is the ability to function fully as an MS Windows NT4-style domain controller, excluding the SAM replication components. However, please be aware that Samba-3 also supports the MS Windows 200x domain control protocols.

    - + At this time any appearance that Samba-3 is capable of acting as a domain controller in native ADS mode is limited and experimental in nature. This functionality should not be used until the Samba Team offers formal support for it. At such a time, the documentation will be revised to duly reflect all @@ -422,19 +422,19 @@ configuration and management requirements. Samba can act as a NT4-style domain c environment. However, there are certain compromises:

    • No machine policy files.

    • No Group Policy Objects.

    • No synchronously executed Active Directory logon scripts.

    • Can't use Active Directory management tools to manage users and machines.

    • Registry changes tattoo the main registry, while with Active Directory they do not leave permanent changes in effect.

    • Without Active Directory you cannot perform the function of exporting specific - applications to specific users or groups.

    Preparing for Domain Control

    - - - - + applications to specific users or groups.

    Preparing for Domain Control

    + + + + There are two ways that MS Windows machines may interact with each other, with other servers, and with domain controllers: either as standalone systems, more commonly called workgroup members, or as full participants in a security system, more commonly called domain members.

    - - - + + + It should be noted that workgroup membership involves no special configuration other than the machine being configured so the network configuration has a commonly used name for its workgroup entry. It is not uncommon for the name WORKGROUP to be used for this. With this mode of configuration, there are no Machine Trust @@ -442,16 +442,16 @@ Accounts, and any concept of membership as such is limited to the fact that all neighborhood to be logically grouped together. Again, just to be clear: workgroup mode does not involve security machine accounts.

    - - - + + + Domain member machines have a machine trust account in the domain accounts database. A special procedure must be followed on each machine to effect domain membership. This procedure, which can be done only by the local machine Administrator account, creates the domain machine account (if it does not exist), and then initializes that account. When the client first logs onto the domain, a machine trust account password change will be automatically triggered.

    Note

    - + When Samba is configured as a domain controller, secure network operation demands that all MS Windows NT4/200x/XP Professional clients should be configured as domain members. If a machine is not made a member of the domain, then it will operate like a workgroup @@ -460,14 +460,14 @@ information regarding domain membership.

    The following are necessary for configuring Samba-3 as an MS Windows NT4-style PDC for MS Windows NT4/200x/XP clients: -

    • Configuration of basic TCP/IP and MS Windows networking.

    • Correct designation of the server role (security = user).

    • Consistent configuration of name resolution.[2]

    • Domain logons for Windows NT4/200x/XP Professional clients.

    • Configuration of roaming profiles or explicit configuration to force local profile usage.

    • Configuration of network/system policies.

    • Adding and managing domain user accounts.

    • Configuring MS Windows NT4/2000 Professional and Windows XP Professional client machines to become domain members.

    +

    • Configuration of basic TCP/IP and MS Windows networking.

    • Correct designation of the server role (security = user).

    • Consistent configuration of name resolution.[2]

    • Domain logons for Windows NT4/200x/XP Professional clients.

    • Configuration of roaming profiles or explicit configuration to force local profile usage.

    • Configuration of network/system policies.

    • Adding and managing domain user accounts.

    • Configuring MS Windows NT4/2000 Professional and Windows XP Professional client machines to become domain members.

    The following provisions are required to serve MS Windows 9x/Me clients:

    • Configuration of basic TCP/IP and MS Windows networking.

    • Correct designation of the server role (security = user).

    • Network logon configuration (since Windows 9x/Me/XP Home are not technically domain members, they do not really participate in the security aspects of Domain logons as such).

    • Roaming profile configuration.

    • Configuration of system policy handling.

    • Installation of the network driver “Client for MS Windows Networks” and configuration to log onto the domain.

    • Placing Windows 9x/Me clients in user-level security if it is desired to allow all client-share access to be controlled according to domain user/group identities.

    • Adding and managing domain user accounts.

    Note

    - - + + Roaming profiles and system/network policies are advanced network administration topics that are covered in Desktop Profile Management and System and Account Policies of this document. However, these are not @@ -475,102 +475,102 @@ necessarily specific to a Samba PDC as much as they are related to Windows NT ne

    A domain controller is an SMB/CIFS server that:

    • - - - - - + + + + + Registers and advertises itself as a domain controller (through NetBIOS broadcasts as well as by way of name registrations either by Mailslot Broadcasts over UDP broadcast, to a WINS server over UDP unicast, or via DNS and Active Directory).

    • - - + + Provides the NETLOGON service. (This is actually a collection of services that runs over multiple protocols. These include the LanMan logon service, the Netlogon service, the Local Security Account service, and variations of them.)

    • Provides a share called NETLOGON.

    - - - - - + + + + + It is rather easy to configure Samba to provide these. Each Samba domain controller must provide the NETLOGON service that Samba calls the domain logons functionality (after the name of the parameter in the smb.conf file). Additionally, one server in a Samba-3 domain must advertise itself as the -domain master browser.[3] This causes the PDC to claim a domain-specific NetBIOS name that identifies +domain master browser.[3] This causes the PDC to claim a domain-specific NetBIOS name that identifies it as a DMB for its given domain or workgroup. Local master browsers (LMBs) in the same domain or workgroup on broadcast-isolated subnets then ask for a complete copy of the browse list for the whole wide-area network. Browser clients then contact their LMB, and will receive the domain-wide browse list instead of just the list for their broadcast-isolated subnet. -

    Domain Control: Example Configuration

    +

    Domain Control: Example Configuration

    The first step in creating a working Samba PDC is to understand the parameters necessary in smb.conf. An example smb.conf for acting as a PDC can be found in the smb.conf file for an example PDC. -

    Example 4.1. smb.conf for being a PDC

    [global]
    passdb backend = tdbsam
    os level = 33
    preferred master = auto
    domain master = yes
    local master = yes
    security = user
    domain logons = yes
    logon path = \\%N\profiles\%U
    logon drive = H:
    logon home = \\homeserver\%U\winprofile
    logon script = logon.cmd
    [netlogon]
    path = /var/lib/samba/netlogon
    read only = yes
    [profiles]
    path = /var/lib/samba/profiles
    read only = no
    create mask = 0600
    directory mask = 0700

    +

    Example 4.1. smb.conf for being a PDC

    [global]
    passdb backend = tdbsam
    os level = 33
    preferred master = auto
    domain master = yes
    local master = yes
    security = user
    domain logons = yes
    logon path = \\%N\profiles\%U
    logon drive = H:
    logon home = \\homeserver\%U\winprofile
    logon script = logon.cmd
    [netlogon]
    path = /var/lib/samba/netlogon
    read only = yes
    [profiles]
    path = /var/lib/samba/profiles
    read only = no
    create mask = 0600
    directory mask = 0700

    The basic options shown in this example are explained as follows:

    passdb backend

    - - - - - + + + + + This contains all the user and group account information. Acceptable values for a PDC are: smbpasswd, tdbsam, and ldapsam. The “guest” entry provides default accounts and is included by default; there is no need to add it explicitly.

    - - - - + + + + Where use of BDCs is intended, the only logical choice is to use LDAP so the passdb backend can be distributed. The tdbsam and smbpasswd files cannot effectively be distributed and therefore should not be used.

    Domain Control Parameters

    - - - - + + + + The parameters os level, preferred master, domain master, security, encrypt passwords, and domain logons play a central role in assuring domain control and network logon support.

    - - + + The os level must be set at or above a value of 32. A domain controller must be the DMB, must be set in user mode security, must support Microsoft-compatible encrypted passwords, and must provide the network logon service (domain logons). Encrypted passwords must be enabled. For more details on how to do this, refer to Account Information Databases.

    Environment Parameters

    - - - - + + + + The parameters logon path, logon home, logon drive, and logon script are environment support settings that help to facilitate client logon operations and that help to provide automated control facilities to ease network management overheads. Please refer to the man page information for these parameters.

    NETLOGON Share

    - - - - - + + + + + The NETLOGON share plays a central role in domain logon and domain membership support. This share is provided on all Microsoft domain controllers. It is used to provide logon scripts, to store group policy files (NTConfig.POL), as well as to locate other common tools that may be needed for logon processing. This is an essential share on a domain controller.

    PROFILE Share

    - - - - - + + + + + This share is used to store user desktop profiles. Each user must have a directory at the root of this share. This directory must be write-enabled for the user and must be globally read-enabled. Samba-3 has a VFS module called “fake_permissions” that may be installed on this share. This will @@ -580,12 +580,12 @@ The basic options shown in smb.conf parameters are the essentials alone:

    -

    netbios name = BELERIAND
    workgroup = MIDEARTH
    domain logons = Yes
    domain master = Yes
    security = User

    +

    netbios name = BELERIAND
    workgroup = MIDEARTH
    domain logons = Yes
    domain master = Yes
    security = User

    The additional parameters shown in the longer listing in this section just make for a more complete explanation. -

    Samba ADS Domain Control

    - +

    Samba ADS Domain Control

    + Samba-3 is not, and cannot act as, an Active Directory server. It cannot truly function as an Active Directory PDC. The protocols for some of the functionality of Active Directory domain controllers has been partially implemented on an experimental only basis. Please do not expect Samba-3 to support these protocols. Do not @@ -594,24 +594,24 @@ features or may change their behavior. This is mentioned for the benefit of thos capabilities in Samba-3 and who have asked when this functionality will be completed. The answer is maybe someday or maybe never!

    - - + + To be sure, Samba-3 is designed to provide most of the functionality that Microsoft Windows NT4-style domain controllers have. Samba-3 does not have all the capabilities of Windows NT4, but it does have a number of features that Windows NT4 domain controllers do not have. In short, Samba-3 is not NT4 and it is not Windows Server 200x: it is not an Active Directory server. We hope this is plain and simple enough for all to understand. -

    Domain and Network Logon Configuration

    - +

    Domain and Network Logon Configuration

    + The subject of network or domain logons is discussed here because it forms an integral part of the essential functionality that is provided by a domain controller. -

    Domain Network Logon Service

    - +

    Domain Network Logon Service

    + All domain controllers must run the netlogon service (domain logons in Samba). One domain controller must be configured with domain master = Yes (the PDC); on all BDCs set the parameter domain master = No. -

    Example Configuration

    Example 4.2. smb.conf for being a PDC

    [global]
    domain logons = Yes
    domain master = (Yes on PDC, No on BDCs)
    [netlogon]
    comment = Network Logon Service
    path = /var/lib/samba/netlogon
    guest ok = Yes
    browseable = No

    The Special Case of MS Windows XP Home Edition

    - +

    Example Configuration

    Example 4.2. smb.conf for being a PDC

    [global]
    domain logons = Yes
    domain master = (Yes on PDC, No on BDCs)
    [netlogon]
    comment = Network Logon Service
    path = /var/lib/samba/netlogon
    guest ok = Yes
    browseable = No

    The Special Case of MS Windows XP Home Edition

    + To be completely clear: If you want MS Windows XP Home Edition to integrate with your MS Windows NT4 or Active Directory domain security, understand it cannot be done. The only option is to purchase the upgrade from MS Windows XP Home Edition to @@ -625,12 +625,12 @@ Now that this has been said, please do not ask the mailing list or email any of Samba Team members with your questions asking how to make this work. It can't be done. If it can be done, then to do so would violate your software license agreement with Microsoft, and we recommend that you do not do that. -

    The Special Case of Windows 9x/Me

    - - - - - +

    The Special Case of Windows 9x/Me

    + + + + + A domain and a workgroup are exactly the same in terms of network browsing. The difference is that a distributable authentication database is associated with a domain, for secure login access to a @@ -638,22 +638,22 @@ network. Also, different access rights can be granted to users if they successfully authenticate against a domain logon server. Samba-3 does this now in the same way as MS Windows NT/200x.

    - + The SMB client logging on to a domain has an expectation that every other server in the domain should accept the same authentication information. 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.

    - - - + + + Issues related to the single-logon network model are discussed in this section. Samba supports domain logons, network logon scripts, and user profiles for MS Windows for Workgroups and MS Windows 9x/Me clients, which are the focus of this section.

    - + When an SMB client in a domain wishes to log on, it broadcasts 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 ill advised) to create a domain where the user database is not shared between servers; @@ -669,8 +669,8 @@ MS Windows XP Home edition is not able to join a domain and does not permit the Before launching into the configuration instructions, it is worthwhile to look at how a Windows 9x/Me client performs a logon:

    1. - - + + The client broadcasts (to the IP broadcast address of the subnet it is in) a NetLogon request. This is sent to the NetBIOS name DOMAIN<1C> at the NetBIOS layer. The client chooses the first response it receives, which @@ -679,13 +679,13 @@ performs a logon: type that is registered by domain controllers (SMB/CIFS servers that provide the netlogon service).

    2. - - - + + + The client connects to that server, logs on (does an SMBsessetupX) and then connects to the IPC$ share (using an SMBtconX).

    3. - + The client does a NetWkstaUserLogon request, which retrieves the name of the user's logon script.

    4. @@ -693,60 +693,60 @@ performs a logon: If it is found and can be read, it is retrieved and executed by the client. After this, the client disconnects from the NetLogon share.

    5. - - + + The client 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 than the user's home share, profiles for Windows 9x clients must reside in the user home directory.

    6. - + The client connects to the user's home share and searches for the user's profile. As it turns out, you can specify the user's home share as a share name and path. For example, \\server\fred\.winprofile. If the profiles are found, they are implemented.

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

    The main difference between a PDC and a Windows 9x/Me logon server configuration is:

    • - - + + Password encryption is not required for a Windows 9x/Me logon server. But note that beginning with MS Windows 98 the default setting is that plaintext password support is disabled. It can be re-enabled with the registry changes that are documented in System and Account Policies.

    • - + Windows 9x/Me clients do not require and do not use Machine Trust Accounts.

    - + A Samba PDC will act as a Windows 9x/Me logon server; after all, it does provide the network logon services that MS Windows 9x/Me expect to find.

    Note

    - + Use of plaintext passwords is strongly discouraged. Where used they are easily detected using a sniffer tool to examine network traffic. -

    Security Mode and Master Browsers

    - - - +

    Security Mode and Master Browsers

    + + + 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 it is okay to configure Samba as a domain controller that operates with security mode other than user-mode. The only security mode that will not work due to technical reasons is share-mode security. Domain and server mode security are really just a variation on SMB user-level security.

    - - - - - - - + + + + + + + Actually, this issue is also closely tied to the debate on whether Samba must be the DMB for its workgroup when operating as a domain controller. In a pure Microsoft Windows NT domain, the PDC wins the election to be the DMB, and then registers the DOMAIN<1B> NetBIOS name. This is not the name used by Windows clients @@ -757,11 +757,11 @@ DMB, if it loses that election it will report a continuous and rapid sequence of Windows event logger complaining that it has lost the election to become a DMB. For this reason, in networks where a Samba server is the PDC it is wise to configure the Samba domain controller as the DMB.

    Note

    - - - - - + + + + + SMB/CIFS servers that register the DOMAIN<1C> name do so because they provide the network logon service. Server that register the DOMAIN<1B> name are DMBs meaning that they are responsible for browse list synchronization across all machines that have registered the DOMAIN<1D> name. The later @@ -782,15 +782,15 @@ Configuring a Samba box as a domain controller for a domain that already by defi PDC is asking for trouble. Therefore, you should always configure the Samba domain controller to be the DMB for its domain and set security = user. This is the only officially supported mode of operation. -

    Common Errors

    “$” Cannot Be Included in Machine Name

    - - - +

    Common Errors

    “$” Cannot Be Included in Machine Name

    + + + A machine account, typically stored in /etc/passwd, takes the form of the machine name with a “$” appended. Some BSD systems will not create a user with a “$” in the name. Recent versions of FreeBSD have removed this limitation, but older releases are still in common use.

    - + The problem is only in the program used to make the entry. Once made, it works perfectly. Create a user without the “$”. Then use vipw to edit the entry, adding the “$”. Or create the whole entry with vipw if you like; make sure you use a unique user login ID. @@ -798,8 +798,8 @@ Or create the whole entry with vipw if you like; make sure you use a unique user The UNIX tool vipw is a common tool for directly editing the /etc/passwd file. The use of vipw will ensure that shadow files (where used) will remain current with the passwd file. This is important for security reasons. -

    Joining Domain Fails Because of Existing Machine Account

    - +

    Joining Domain Fails Because of Existing Machine Account

    + “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.”

    @@ -814,12 +814,12 @@ This will break all network connections. Further, if the machine is already a “member of a workgroup” that is the same name as the domain you are joining (bad idea), you will get this message. Change the workgroup name to something else it does not matter what reboot, and try again. -

    The System Cannot Log You On (C000019B)

    “ +

    The System Cannot 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 cannot 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 @@ -836,7 +836,7 @@ Workstation Machine Trust Accounts work only with the domain (or network) SID. I domain members (workstations) will not be able to log onto the domain. The original domain SID can be recovered from the secrets.tdb file. The alternative is to visit each workstation to rejoin it to the domain. -

    The Machine Trust Account Is Not Accessible

    +

    The Machine Trust Account 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?”

    @@ -858,16 +858,16 @@ by alternative settings in the NSS /etc/nsswitch.conf

    Some people have also reported that inconsistent subnet masks between the Samba server and the NT client can cause this problem. Make sure that these are consistent for both client and server. -

    Account Disabled

    “When I attempt to log in to a Samba domain from a NT4/W200x workstation, +

    Account Disabled

    “When I attempt to log in to a Samba domain from a NT4/W200x workstation, I get a message about my account being disabled.”

    Enable the user accounts with smbpasswd -e username . This is normally done as an account is created. -

    Domain Controller Unavailable

    “Until a few minutes after Samba has started, clients get the error `Domain Controller Unavailable'”

    +

    Domain Controller Unavailable

    “Until a few minutes after Samba has started, clients get the error `Domain Controller Unavailable'”

    A domain controller has to announce its role on the network. This usually takes a while. Be patient for up to 15 minutes, then try again. -

    Cannot Log onto Domain Member Workstation After Joining Domain

    - - +

    Cannot Log onto Domain Member Workstation After Joining Domain

    + + After successfully joining the domain, user logons fail with one of two messages: one to the effect that the domain controller cannot be found; the other claims that the account does not exist in the domain or that the password is incorrect. This may be due to incompatible @@ -884,7 +884,7 @@ Control Panel. The Policy settings are found in the Local Policies/Security Opti Secure Channel:..., and Digitally sign....

    It is important that these be set consistently with the Samba-3 server settings. -


    [1] See also Account Information -Databases.

    .

    [2] See Network Browsing, and - Integrating MS Windows Networks with Samba.

    [3] See Network +


    [1] See also Account Information +Databases.

    .

    [2] See Network Browsing, and + Integrating MS Windows Networks with Samba.

    [3] See Network Browsing.

    Prev Up Next
    Chapter 3. Server Types and Security Modes Home Chapter 5. Backup Domain Control
    diff --git a/docs/htmldocs/Samba3-HOWTO/securing-samba.html b/docs/htmldocs/Samba3-HOWTO/securing-samba.html index d9ff4361c4..6aacd7a61c 100644 --- a/docs/htmldocs/Samba3-HOWTO/securing-samba.html +++ b/docs/htmldocs/Samba3-HOWTO/securing-samba.html @@ -1,11 +1,11 @@ -Chapter 18. Securing Samba
    Chapter 18. Securing Samba
    Prev Part III. Advanced Configuration Next

    Chapter 18. Securing Samba

    Andrew Tridgell

    Samba Team

    John H. Terpstra

    Samba Team

    May 26, 2003

    Table of Contents

    Introduction
    Features and Benefits
    Technical Discussion of Protective Measures and Issues
    Using Host-Based Protection
    User-Based Protection
    Using Interface Protection
    Using a Firewall
    Using IPC$ Share-Based Denials
    NTLMv2 Security
    Upgrading Samba
    Common Errors
    Smbclient Works on Localhost, but the Network Is Dead
    Why Can Users Access Other Users' Home Directories?

    Introduction

    - - - - - - - +Chapter 18. Securing Samba

    Chapter 18. Securing Samba
    Prev Part III. Advanced Configuration Next

    Chapter 18. Securing Samba

    Andrew Tridgell

    Samba Team

    John H. Terpstra

    Samba Team

    May 26, 2003

    Table of Contents

    Introduction
    Features and Benefits
    Technical Discussion of Protective Measures and Issues
    Using Host-Based Protection
    User-Based Protection
    Using Interface Protection
    Using a Firewall
    Using IPC$ Share-Based Denials
    NTLMv2 Security
    Upgrading Samba
    Common Errors
    Smbclient Works on Localhost, but the Network Is Dead
    Why Can Users Access Other Users' Home Directories?

    Introduction

    + + + + + + + The information contained in this chapter applies in general to all Samba installations. Security is everyone's concern in the information technology world. A surprising number of Samba servers are being installed on machines that have direct internet access, thus security is made more critical than it would have been had the @@ -22,11 +22,11 @@ on it!” Security concerns are just like that. You need to know a little about the subject to appreciate how obvious most of it really is. The challenge for most of us is to discover that first morsel of knowledge with which we may unlock the secrets of the masters. -

    Features and Benefits

    - - - - +

    Features and Benefits

    + + + + There are three levels at which security principles must be observed in order to render a site at least moderately secure. They are the perimeter firewall, the configuration of the host server that is running Samba, and Samba itself. @@ -34,154 +34,154 @@ server that is running Samba, and Samba itself. Samba permits a most flexible approach to network security. As far as possible Samba implements the latest protocols to permit more secure MS Windows file and print operations.

    - - - + + + Samba can be secured from connections that originate from outside the local network. This can be done using host-based protection, using Samba's implementation of a technology known as “tcpwrappers,” or it may be done be using interface-based exclusion so smbd will bind only to specifically permitted interfaces. It is also possible to set specific share- or resource-based exclusions, for example, on the [IPC$] autoshare. The [IPC$] share is used for browsing purposes as well as to establish TCP/IP connections.

    - - - + + + Another method by which Samba may be secured is by setting Access Control Entries (ACEs) in an Access Control List (ACL) on the shares themselves. This is discussed in File, Directory, and Share Access Controls. -

    Technical Discussion of Protective Measures and Issues

    +

    Technical Discussion of Protective Measures and Issues

    The key challenge of security is that protective measures suffice at best only to close the door on known exploits and breach techniques. Never assume that because you have followed these few measures, the Samba server is now an impenetrable fortress! Given the history of information systems so far, it is only a matter of time before someone will find yet another vulnerability. -

    Using Host-Based Protection

    - - - +

    Using Host-Based Protection

    + + + In many installations of Samba, the greatest threat comes from outside your immediate network. By default, Samba accepts connections from any host, which means that if you run an insecure version of Samba on a host that is directly connected to the Internet, you can be especially vulnerable.

    - - + + One of the simplest fixes in this case is to use the hosts allow and hosts deny options in the Samba smb.conf configuration file to allow access to your server only from a specific range of hosts. An example might be: -

    hosts allow = 127.0.0.1 192.168.2.0/24 192.168.3.0/24
    hosts deny = 0.0.0.0/0

    +

    hosts allow = 127.0.0.1 192.168.2.0/24 192.168.3.0/24
    hosts deny = 0.0.0.0/0

    - - - + + + The above will allow SMB connections only from localhost (your own computer) and from the two private networks 192.168.2 and 192.168.3. All other connections will be refused as soon as the client sends its first packet. The refusal will be marked as not listening on called name error. -

    User-Based Protection

    +

    User-Based Protection

    If you want to restrict access to your server to valid users only, then the following method may be of use. In the smb.conf [global] section put: -

    valid users = @smbusers, jacko

    +

    valid users = @smbusers, jacko

    - + This restricts all server access either to the user jacko or to members of the system group smbusers. -

    Using Interface Protection

    - - - +

    Using Interface Protection

    + + + By default, Samba accepts connections on any network interface that it finds on your system. That means if you have an ISDN line or a PPP connection to the Internet then Samba will accept connections on those links. This may not be what you want.

    You can change this behavior using options like this: -

    interfaces = eth* lo
    bind interfaces only = yes

    +

    interfaces = eth* lo
    bind interfaces only = yes

    - - - - + + + + This tells Samba to listen for connections only on interfaces with a name starting with eth such as eth0 or eth1, plus on the loopback interface called lo. The name you will need to use depends on what OS you are using. In the above, I used the common name for Ethernet adapters on Linux.

    - - - - + + + + If you use the above and someone tries to make an SMB connection to your host over a PPP interface called ppp0, then [s]he will get a TCP connection refused reply. In that case, no Samba code is run at all, because the operating system has been told not to pass connections from that interface to any Samba process. However, the refusal helps a would-be cracker by confirming that the IP address provides valid active services.

    - - - - - + + + + + A better response would be to ignore the connection (from, for example, ppp0) altogether. The advantage of ignoring the connection attempt, as compared with refusing it, is that it foils those who probe an interface with the sole intention of finding valid IP addresses for later use in exploitation or denial of service attacks. This method of dealing with potential malicious activity demands the use of appropriate firewall mechanisms.

    Using a Firewall

    - - - + + + Many people use a firewall to deny access to services they do not want exposed outside their network. This can be a good idea, although I recommend using it in conjunction with the above methods so you are protected even if your firewall is not active for some reason.

    If you are setting up a firewall, you need to know what TCP and UDP ports to allow and block. Samba uses the following: - - - - - + + + + +

    Port 135/TCP - used by smbd
    Port 137/UDP - used by nmbd
    Port 138/UDP - used by nmbd
    Port 139/TCP - used by smbd
    Port 445/TCP - used by smbd

    - + The last one is important because many older firewall setups may not be aware of it, given that this port was only added to the protocol in recent years.

    - - - + + + When configuring a firewall, the high order ports (1024-65535) are often used for outgoing connections and therefore should be permitted through the firewall. It is prudent to block incoming packets on the high order ports except for established connections. -

    Using IPC$ Share-Based Denials

    - - - +

    Using IPC$ Share-Based Denials

    + + + If the above methods are not suitable, then you could also place a more specific deny on the IPC$ share that is used in the recently discovered security hole. This allows you to offer access to other shares while denying access to IPC$ from potentially untrustworthy hosts.

    To do this you could use: -

    [IPC$]
    hosts allow = 192.168.115.0/24 127.0.0.1
    hosts deny = 0.0.0.0/0

    +

    [IPC$]
    hosts allow = 192.168.115.0/24 127.0.0.1
    hosts deny = 0.0.0.0/0

    - - - + + + This instructs Samba that IPC$ connections are not allowed from anywhere except the two listed network addresses (localhost and the 192.168.115 subnet). Connections to other shares are still allowed. Because the IPC$ share is the only share that is always accessible anonymously, this provides some level of protection against attackers who do not know a valid username/password for your host.

    - - - + + + If you use this method, then clients will be given an `access denied' reply when they try to access the IPC$ share. Those clients will not be able to browse shares and may also be unable to access some other resources. This is not recommended unless for some reason you cannot use one of the other methods just discussed. -

    NTLMv2 Security

    - +

    NTLMv2 Security

    + To configure NTLMv2 authentication, the following registry keys are worth knowing about: 

    @@ -201,20 +201,20 @@ before someone will find yet another vulnerability.
 	The value 0x00080000 means permit only NTLMv2 session security. If either NtlmMinClientSec or
 	NtlmMinServerSec is set to 0x00080000, the connection will fail if NTLMv2
 	session security is negotiated.
-

    Upgrading Samba

    - - - +

    Upgrading Samba

    + + + Please check regularly on http://www.samba.org/ for updates and important announcements. Occasionally security releases are made, and it is highly recommended to upgrade Samba promptly when a security vulnerability is discovered. Check with your OS vendor for OS-specific upgrades. -

    Common Errors

    +

    Common Errors

    If all Samba and host platform configurations were really as intuitive as one might like them to be, this chapter would not be necessary. Security issues are often vexing for a support person to resolve, not because of the complexity of the problem, but because most administrators who post what turns out to be a security problem request are totally convinced that the problem is with Samba. -

    Smbclient Works on Localhost, but the Network Is Dead

    +

    Smbclient Works on Localhost, but the Network Is Dead

    This is a common problem. Linux vendors tend to install a default firewall. With the default firewall in place, only traffic on the loopback adapter (IP address 127.0.0.1) is allowed through the firewall. @@ -222,10 +222,10 @@ problem request are totally convinced that the problem is with Samba. The solution is either to remove the firewall (stop it) or modify the firewall script to allow SMB networking traffic through. See the Using a Firewall section. -

    Why Can Users Access Other Users' Home Directories?

    +

    Why Can Users Access Other Users' Home Directories?

    “ - - + + We are unable to keep individual users from mapping to any other user's home directory once they have supplied a valid password! They only need to enter their own password. I have not found any method to configure Samba so that users may map only their own home directory. @@ -233,20 +233,20 @@ problem request are totally convinced that the problem is with Samba.

    “ User xyzzy can map his home directory. Once mapped, user xyzzy can also map anyone else's home directory. ”

    - - + + This is not a security flaw, it is by design. Samba allows users to have exactly the same access to the UNIX file system as when they were logged on to the UNIX box, except that it only allows such views onto the file system as are allowed by the defined shares.

    - - + + If your UNIX home directories are set up so that one user can happily cd into another user's directory and execute ls, the UNIX security solution is to change file permissions on the user's home directories so that the cd and ls are denied.

    - - + + Samba tries very hard not to second guess the UNIX administrator's security policies and trusts the UNIX admin to set the policies and permissions he or she desires.

    @@ -255,9 +255,9 @@ problem request are totally convinced that the problem is with Samba.

    The only user works in conjunction with the users = list, so to get the behavior you require, add the line: -

    users = %S

    +

    users = %S

    This is equivalent to adding -

    valid users = %S

    +

    valid users = %S

    to the definition of the [homes] share, as recommended in the smb.conf man page.

    Prev Up Next
    Chapter 17. File and Record Locking Home Chapter 19. Interdomain Trust Relationships
    diff --git a/docs/htmldocs/Samba3-HOWTO/speed.html b/docs/htmldocs/Samba3-HOWTO/speed.html index 371b0bea14..fe1e01a9de 100644 --- a/docs/htmldocs/Samba3-HOWTO/speed.html +++ b/docs/htmldocs/Samba3-HOWTO/speed.html @@ -1,4 +1,4 @@ -Chapter 44. Samba Performance Tuning
    Chapter 44. Samba Performance Tuning
    Prev Part VI. Reference Section Next

    Chapter 44. Samba Performance Tuning

    Paul Cochrane

    Dundee Limb Fitting Centre

    Jelmer R. Vernooij

    The Samba Team

    John H. Terpstra

    Samba Team

    Table of Contents

    Comparisons
    Socket Options
    Read Size
    Max Xmit
    Log Level
    Read Raw
    Write Raw
    Slow Logins
    Client Tuning
    Samba Performance Problem Due to Changing Linux Kernel
    Corrupt tdb Files
    Samba Performance is Very Slow

    Comparisons

    +Chapter 45. Samba Performance Tuning

    Chapter 45. Samba Performance Tuning
    Prev Part VI. Reference Section Next

    Chapter 45. Samba Performance Tuning

    Paul Cochrane

    Dundee Limb Fitting Centre

    Jelmer R. Vernooij

    The Samba Team

    John H. Terpstra

    Samba Team

    Table of Contents

    Comparisons
    Socket Options
    Read Size
    Max Xmit
    Log Level
    Read Raw
    Write Raw
    Slow Logins
    Client Tuning
    Samba Performance Problem Due to Changing Linux Kernel
    Corrupt tdb Files
    Samba Performance is Very Slow

    Comparisons

    The Samba server uses TCP to talk to the client, so if you are trying to see if it performs well, you should really compare it to programs that use the same protocol. The most readily available @@ -20,7 +20,7 @@ suspect the biggest factor is not Samba versus some other system, but the hardware and drivers used on the various systems. Given similar hardware, Samba should certainly be competitive in speed with other systems. -

    Socket Options

    +

    Socket Options

    There are a number of socket options that can greatly affect the performance of a TCP-based server like Samba.

    @@ -44,7 +44,7 @@ There have been reports that setting socket options can seriously degrade Samba performance on the loopback adaptor (IP Address 127.0.0.1). It is strongly recommended that before specifying any settings for socket options, the effect first be quantitatively measured on the server being configured. -

    Read Size

    +

    Read Size

    The option read size affects the overlap of disk reads/writes with network reads/writes. If the amount of data being transferred in several of the SMB commands (currently SMBwrite, SMBwriteX, and @@ -61,7 +61,7 @@ The default value is 16384, but little experimentation has been done as yet to determine the optimal value, and it is likely that the best value will vary greatly between systems anyway. A value over 65536 is pointless and will cause you to allocate memory unnecessarily. -

    Max Xmit

    +

    Max Xmit

    At startup the client and server negotiate a maximum transmit size, which limits the size of nearly all SMB commands. You can set the maximum size that Samba will negotiate using the max xmit option @@ -74,12 +74,12 @@ It defaults to 65536 bytes (the maximum), but it is possible that some clients may perform better with a smaller transmit unit. Trying values of less than 2048 is likely to cause severe problems. In most cases the default is the best option. -

    Log Level

    +

    Log Level

    If you set the log level (also known as debug level) higher than 2, then you may suffer a large drop in performance. This is because the server flushes the log file after each operation, which can be quite expensive. -

    Read Raw

    +

    Read Raw

    The read raw operation is designed to be an optimized, low-latency file read operation. A server may choose to not support it, however, and Samba makes support for read raw optional, with it @@ -90,26 +90,26 @@ get lower performance using it than they get using the conventional read operations, so you might like to try read raw = no and see what happens on your network. It might lower, raise, or not affect your performance. Only testing can really tell. -

    Write Raw

    +

    Write Raw

    The write raw operation is designed to be an optimized, low-latency file write operation. A server may choose to not support it, however, and Samba makes support for write raw optional, with it being enabled by default.

    Some machines may find write raw slower than normal write, in which case you may wish to change this option. -

    Slow Logins

    +

    Slow Logins

    Slow logins are almost always due to the password checking time. Using the lowest practical password level will improve things. -

    Client Tuning

    +

    Client Tuning

    Often a speed problem can be traced to the client. The client (for example Windows for Workgroups) can often be tuned for better TCP performance. Check the sections on the various clients in -Samba and Other CIFS Clients. -

    Samba Performance Problem Due to Changing Linux Kernel

    +Samba and Other CIFS Clients. +

    Samba Performance Problem Due to Changing Linux Kernel

    A user wrote the following to the mailing list:

    - - + + I am running Gentoo on my server and Samba 2.2.8a. Recently I changed kernel versions from linux-2.4.19-gentoo-r10 to linux-2.4.20-wolk4.0s. Now I have a performance issue with Samba. Many of you will probably say, “Move to vanilla sources!” Well, I @@ -120,16 +120,16 @@ server and Windows, and it is terribly slow.

    The answer he was given is:

    - - - + + + Grab the mii-tool and check the duplex settings on the NIC. My guess is that it is a link layer issue, not an application layer problem. Also run ifconfig and verify that the framing error, collisions, and so on, look normal for ethernet. -

    Corrupt tdb Files

    - - - +

    Corrupt tdb Files

    + + + Our Samba PDC server has been hosting three TB of data to our 500+ users [Windows NT/XP] for the last three years using Samba without a problem. Today all shares went very slow. Also, the main smbd kept spawning new processes, so we had 1600+ running SMDB's (normally we average 250). It crashed the SUN E3500 cluster twice. @@ -138,28 +138,28 @@ After a lot of searching, I decided to rm /var/locks/*.tdb Question: Is there any method of keeping the *.tdb files in top condition, or how can I detect early corruption?

    - - + + Answer: Yes, run tdbbackup each time after stopping nmbd and before starting nmbd.

    Question: What I also would like to mention is that the service latency seems a lot lower than before the locks cleanup. Any ideas on keeping it top notch?

    Answer: Yes. Same answer as for previous question! -

    Samba Performance is Very Slow

    - +

    Samba Performance is Very Slow

    + A site reported experiencing very baffling symptoms with MYOB Premier opening and accessing its data files. Some operations on the file would take between 40 and 45 seconds.

    - - + + It turned out that the printer monitor program running on the Windows clients was causing the problems. From the logs, we saw activity coming through with pauses of about 1 second.

    - - + + Stopping the monitor software resulted in the networks access at normal (quick) speed. Restarting the program caused the speed to slow down again. The printer was a Canon LBP-810 and the relevant task was @@ -171,4 +171,4 @@ trying the application at every step of the installation of other software process (we had to do this many times).

    Moral of the story: Check everything (other software included)! -

    Prev Up Next
    Chapter 43. Samba and Other CIFS Clients Home Chapter 45. LDAP and Transport Layer Security
    +

    Prev Up Next
    Chapter 44. Samba and Other CIFS Clients Home Chapter 46. LDAP and Transport Layer Security
    diff --git a/docs/htmldocs/Samba3-HOWTO/troubleshooting.html b/docs/htmldocs/Samba3-HOWTO/troubleshooting.html index 7e789386b4..3614ceae8f 100644 --- a/docs/htmldocs/Samba3-HOWTO/troubleshooting.html +++ b/docs/htmldocs/Samba3-HOWTO/troubleshooting.html @@ -1 +1 @@ -Part V. Troubleshooting
    Part V. Troubleshooting
    Prev   Next

    Part V. Troubleshooting

    Table of Contents

    38. The Samba Checklist
    Introduction
    Assumptions
    The Tests
    39. Analyzing and Solving Samba Problems
    Diagnostics Tools
    Debugging with Samba Itself
    Tcpdump
    Ethereal
    The Windows Network Monitor
    Useful URLs
    Getting Mailing List Help
    How to Get Off the Mailing Lists
    40. Reporting Bugs
    Introduction
    General Information
    Debug Levels
    Debugging-Specific Operations
    Internal Errors
    Attaching to a Running Process
    Patches
    Prev   Next
    Chapter 37. SWAT: The Samba Web Administration Tool Home Chapter 38. The Samba Checklist
    +Part V. Troubleshooting
    Part V. Troubleshooting
    Prev   Next

    Part V. Troubleshooting

    Table of Contents

    38. The Samba Checklist
    Introduction
    Assumptions
    The Tests
    39. Analyzing and Solving Samba Problems
    Diagnostics Tools
    Debugging with Samba Itself
    Tcpdump
    Ethereal
    The Windows Network Monitor
    Useful URLs
    Getting Mailing List Help
    How to Get Off the Mailing Lists
    40. Reporting Bugs
    Introduction
    General Information
    Debug Levels
    Debugging-Specific Operations
    Internal Errors
    Attaching to a Running Process
    Patches
    41. Managing TDB Files
    Features and Benefits
    Managing TDB Files
    Prev   Next
    Chapter 37. SWAT: The Samba Web Administration Tool Home Chapter 38. The Samba Checklist
    diff --git a/docs/htmldocs/Samba3-HOWTO/type.html b/docs/htmldocs/Samba3-HOWTO/type.html index 17086e344f..58b57f69ab 100644 --- a/docs/htmldocs/Samba3-HOWTO/type.html +++ b/docs/htmldocs/Samba3-HOWTO/type.html @@ -1,5 +1,5 @@ -Part II. Server Configuration Basics
    Part II. Server Configuration Basics
    Prev   Next

    Part II. Server Configuration Basics

    First Steps in Server Configuration

    +Part II. Server Configuration Basics

    Part II. Server Configuration Basics
    Prev   Next

    Part II. Server Configuration Basics

    First Steps in Server Configuration

    Samba can operate in various modes within SMB networks. This HOWTO section contains information on configuring Samba to function as the type of server your network requires. Please read this section carefully. -

    Table of Contents

    3. Server Types and Security Modes
    Features and Benefits
    Server Types
    Samba Security Modes
    User Level Security
    Share-Level Security
    Domain Security Mode (User-Level Security)
    ADS Security Mode (User-Level Security)
    Server Security (User Level Security)
    Password Checking
    Common Errors
    What Makes Samba a Server?
    What Makes Samba a Domain Controller?
    What Makes Samba a Domain Member?
    Constantly Losing Connections to Password Server
    Stand-alone Server is converted to Domain Controller Now User accounts don't work
    4. Domain Control
    Features and Benefits
    Single Sign-On and Domain Security
    Basics of Domain Control
    Domain Controller Types
    Preparing for Domain Control
    Domain Control: Example Configuration
    Samba ADS Domain Control
    Domain and Network Logon Configuration
    Domain Network Logon Service
    Security Mode and Master Browsers
    Common Errors
    “$” Cannot Be Included in Machine Name
    Joining Domain Fails Because of Existing Machine Account
    The System Cannot Log You On (C000019B)
    The Machine Trust Account Is Not Accessible
    Account Disabled
    Domain Controller Unavailable
    Cannot Log onto Domain Member Workstation After Joining Domain
    5. Backup Domain Control
    Features and Benefits
    Essential Background Information
    MS Windows NT4-style Domain Control
    LDAP Configuration Notes
    Active Directory Domain Control
    What Qualifies a Domain Controller on the Network?
    How Does a Workstation find its Domain Controller?
    Backup Domain Controller Configuration
    Example Configuration
    Common Errors
    Machine Accounts Keep Expiring
    Can Samba Be a Backup Domain Controller to an NT4 PDC?
    How Do I Replicate the smbpasswd File?
    Can I Do This All with LDAP?
    6. Domain Membership
    Features and Benefits
    MS Windows Workstation/Server Machine Trust Accounts
    Manual Creation of Machine Trust Accounts
    Managing Domain Machine Accounts using NT4 Server Manager
    On-the-Fly Creation of Machine Trust Accounts
    Making an MS Windows Workstation or Server a Domain Member
    Domain Member Server
    Joining an NT4-type Domain with Samba-3
    Why Is This Better Than security = server?
    Samba ADS Domain Membership
    Configure smb.conf
    Configure /etc/krb5.conf
    Create the Computer Account
    Testing Server Setup
    Testing with smbclient
    Notes
    Sharing User ID Mappings between Samba Domain Members
    Common Errors
    Cannot Add Machine Back to Domain
    Adding Machine to Domain Fails
    I Can't Join a Windows 2003 PDC
    7. Standalone Servers
    Features and Benefits
    Background
    Example Configuration
    Reference Documentation Server
    Central Print Serving
    Common Errors
    8. MS Windows Network Configuration Guide
    Features and Benefits
    Technical Details
    TCP/IP Configuration
    Joining a Domain: Windows 2000/XP Professional
    Domain Logon Configuration: Windows 9x/Me
    Common Errors
    Prev   Next
    Chapter 2. Fast Start: Cure for Impatience Home Chapter 3. Server Types and Security Modes
    +

    Table of Contents

    3. Server Types and Security Modes
    Features and Benefits
    Server Types
    Samba Security Modes
    User Level Security
    Share-Level Security
    Domain Security Mode (User-Level Security)
    ADS Security Mode (User-Level Security)
    Server Security (User Level Security)
    Password Checking
    Common Errors
    What Makes Samba a Server?
    What Makes Samba a Domain Controller?
    What Makes Samba a Domain Member?
    Constantly Losing Connections to Password Server
    Stand-alone Server is converted to Domain Controller Now User accounts don't work
    4. Domain Control
    Features and Benefits
    Single Sign-On and Domain Security
    Basics of Domain Control
    Domain Controller Types
    Preparing for Domain Control
    Domain Control: Example Configuration
    Samba ADS Domain Control
    Domain and Network Logon Configuration
    Domain Network Logon Service
    Security Mode and Master Browsers
    Common Errors
    “$” Cannot Be Included in Machine Name
    Joining Domain Fails Because of Existing Machine Account
    The System Cannot Log You On (C000019B)
    The Machine Trust Account Is Not Accessible
    Account Disabled
    Domain Controller Unavailable
    Cannot Log onto Domain Member Workstation After Joining Domain
    5. Backup Domain Control
    Features and Benefits
    Essential Background Information
    MS Windows NT4-style Domain Control
    LDAP Configuration Notes
    Active Directory Domain Control
    What Qualifies a Domain Controller on the Network?
    How Does a Workstation find its Domain Controller?
    Backup Domain Controller Configuration
    Example Configuration
    Common Errors
    Machine Accounts Keep Expiring
    Can Samba Be a Backup Domain Controller to an NT4 PDC?
    How Do I Replicate the smbpasswd File?
    Can I Do This All with LDAP?
    6. Domain Membership
    Features and Benefits
    MS Windows Workstation/Server Machine Trust Accounts
    Manual Creation of Machine Trust Accounts
    Managing Domain Machine Accounts using NT4 Server Manager
    On-the-Fly Creation of Machine Trust Accounts
    Making an MS Windows Workstation or Server a Domain Member
    Domain Member Server
    Joining an NT4-type Domain with Samba-3
    Why Is This Better Than security = server?
    Samba ADS Domain Membership
    Configure smb.conf
    Configure /etc/krb5.conf
    Create the Computer Account
    Testing Server Setup
    Testing with smbclient
    Notes
    Sharing User ID Mappings between Samba Domain Members
    Common Errors
    Cannot Add Machine Back to Domain
    Adding Machine to Domain Fails
    I Can't Join a Windows 2003 PDC
    7. Standalone Servers
    Features and Benefits
    Background
    Example Configuration
    Reference Documentation Server
    Central Print Serving
    Common Errors
    8. MS Windows Network Configuration Guide
    Features and Benefits
    Technical Details
    TCP/IP Configuration
    Joining a Domain: Windows 2000/XP Professional
    Domain Logon Configuration: Windows 9x/Me
    Common Errors
    Prev   Next
    Chapter 2. Fast Start: Cure for Impatience Home Chapter 3. Server Types and Security Modes
    diff --git a/docs/htmldocs/Samba3-HOWTO/unicode.html b/docs/htmldocs/Samba3-HOWTO/unicode.html index ca5b710b90..2cdf5b3082 100644 --- a/docs/htmldocs/Samba3-HOWTO/unicode.html +++ b/docs/htmldocs/Samba3-HOWTO/unicode.html @@ -1,5 +1,5 @@ -Chapter 30. Unicode/Charsets
    Chapter 30. Unicode/Charsets
    Prev Part III. Advanced Configuration Next

    Chapter 30. Unicode/Charsets

    Jelmer R. Vernooij

    The Samba Team

    John H. Terpstra

    Samba Team

    TAKAHASHI Motonobu

    Japanese character support 

    25 March 2003

    Table of Contents

    Features and Benefits
    What Are Charsets and Unicode?
    Samba and Charsets
    Conversion from Old Names
    Japanese Charsets
    Basic Parameter Setting
    Individual Implementations
    Migration from Samba-2.2 Series
    Common Errors
    CP850.so Can't Be Found

    Features and Benefits

    - +Chapter 30. Unicode/Charsets

    Chapter 30. Unicode/Charsets
    Prev Part III. Advanced Configuration Next

    Chapter 30. Unicode/Charsets

    Jelmer R. Vernooij

    The Samba Team

    John H. Terpstra

    Samba Team

    TAKAHASHI Motonobu

    Japanese character support 

    25 March 2003

    Table of Contents

    Features and Benefits
    What Are Charsets and Unicode?
    Samba and Charsets
    Conversion from Old Names
    Japanese Charsets
    Basic Parameter Setting
    Individual Implementations
    Migration from Samba-2.2 Series
    Common Errors
    CP850.so Can't Be Found

    Features and Benefits

    + Every industry eventually matures. One of the great areas of maturation is in the focus that has been given over the past decade to make it possible for anyone anywhere to use a computer. It has not always been that way. In fact, not so long @@ -11,19 +11,19 @@ language support for all computer users, the efforts of the Openi18n organization is deserving of special mention.

    - + Samba-2.x supported a single locale through a mechanism called codepages. Samba-3 is destined to become a truly transglobal file- and printer-sharing platform. -

    What Are Charsets and Unicode?

    - +

    What Are Charsets and Unicode?

    + Computers communicate in numbers. In texts, each number is translated to a corresponding letter. The meaning that will be assigned to a certain number depends on the character set (charset) that is used.

    - - + + A charset can be seen as a table that is used to translate numbers to letters. Not all computers use the same charset (there are charsets with German umlauts, Japanese characters, and so on). The American Standard Code @@ -31,36 +31,36 @@ for Information Interchange (ASCII) encoding system has been the normative chara encoding scheme used by computers to date. This employs a charset that contains 256 characters. Using this mode of encoding, each character takes exactly one byte.

    - - + + There are also charsets that support extended characters, but those need at least twice as much storage space as does ASCII encoding. Such charsets can contain 256 * 256 = 65536 characters, which is more than all possible characters one could think of. They are called multibyte charsets because they use more then one byte to store one character.

    - + One standardized multibyte charset encoding scheme is known as unicode. A big advantage of using a multibyte charset is that you only need one. There is no need to make sure two computers use the same charset when they are communicating.

    - - - + + + Old Windows clients use single-byte charsets, named codepages, by Microsoft. However, there is no support for negotiating the charset to be used in the SMB/CIFS protocol. Thus, you have to make sure you are using the same charset when talking to an older client. Newer clients (Windows NT, 200x, XP) talk Unicode over the wire. -

    Samba and Charsets

    - - +

    Samba and Charsets

    + + As of Samba-3, Samba can (and will) talk Unicode over the wire. Internally, Samba knows of three kinds of character sets:

    unix charset

    - - + + This is the charset used internally by your operating system. The default is UTF-8, which is fine for most systems and covers all characters in all languages. The default @@ -73,26 +73,26 @@ Samba knows of three kinds of character sets: The default depends on the charsets you have installed on your system. Run testparm -v | grep "dos charset" to see what the default is on your system. -

    Conversion from Old Names

    - +

    Conversion from Old Names

    + Because previous Samba versions did not do any charset conversion, characters in filenames are usually not correct in the UNIX charset but only for the local charset used by the DOS/Windows clients.

    Bjoern Jacke has written a utility named convmv that can convert whole directory structures to different charsets with one single command. -

    Japanese Charsets

    +

    Japanese Charsets

    Setting up Japanese charsets is quite difficult. This is mainly because:

    • - + The Windows character set is extended from the original legacy Japanese standard (JIS X 0208) and is not standardized. This means that the strictly standardized implementation cannot support the full Windows character set.

    • - - - - - + + + + + Mainly for historical reasons, there are several encoding methods in Japanese, which are not fully compatible with each other. There are two major encoding methods. One is the Shift_JIS series used in Windows @@ -112,24 +112,24 @@ Setting up Japanese charsets is quite difficult. This is mainly because: names may be different on different systems. This means that the value of the charset parameters depends on the implementation of iconv() you are using.

      - - - - + + + + Though 2-byte fixed UCS-2 encoding is used in Windows internally, Shift_JIS series encoding is usually used in Japanese environments as ASCII encoding is in English environments. -

    Basic Parameter Setting

    - +

    Basic Parameter Setting

    + The dos charset and display charset should be set to the locale compatible with the character set and encoding method used on Windows. This is usually CP932 but sometimes has a different name.

    - - - + + + The unix charset can be either Shift_JIS series, EUC-JP series, or UTF-8. UTF-8 is always available, but the availability of other locales and the name itself depends on the system. @@ -166,8 +166,8 @@ Setting up Japanese charsets is quite difficult. This is mainly because: only. It is good practice to verify that the Japanized free software can work with Shift_JIS.

    EUC-JP series

    - - + + EUC-JP series means a locale that is equivalent to the industry standard called EUC-JP, widely used in Japanese UNIX (although EUC contains specifications for languages other than Japanese, such as @@ -176,16 +176,16 @@ Setting up Japanese charsets is quite difficult. This is mainly because: Windows on Samba, the filename on UNIX becomes 0xb6a6, 0xcdad, “.txt” (an 8-byte BINARY string).

    - - - - - - - - - - + + + + + + + + + + Since EUC-JP is usually used on open source UNIX, Linux, and FreeBSD, and on commercial-based UNIX, Solaris, IRIX, and Tru64 UNIX as Japanese locale (however, it is also possible on Solaris to use Shift_JIS and UTF-8, and on Tru64 UNIX it is possible to use Shift_JIS). To use EUC-JP series, most Japanese filenames created from @@ -198,7 +198,7 @@ Setting up Japanese charsets is quite difficult. This is mainly because: commands that cannot handle non-ASCII filenames may be aborted during parsing filenames.

    - + Moreover, if you built Samba using differently installed libiconv, the eucJP-ms locale included in libiconv and EUC-JP series locale included in the operating system may not be compatible. In this case, you may need to @@ -223,9 +223,9 @@ Setting up Japanese charsets is quite difficult. This is mainly because: must be handled carefully, so you had better not touch filenames written from Windows on UNIX.

    - - - + + + In addition, although it is not directly concerned with Samba, since there is a delicate difference between the iconv() function, which is generally used on UNIX, and the functions used on other platforms, @@ -233,14 +233,14 @@ Setting up Japanese charsets is quite difficult. This is mainly because: Shift_JIS and Unicode UTF-8 must be done with care and recognition of the limitations involved in the process.

    - + Although Mac OS X uses UTF-8 as its encoding method for filenames, it uses an extended UTF-8 specification that Samba cannot handle, so UTF-8 locale is not available for Mac OS X.

    Shift_JIS series + vfs_cap (CAP encoding)

    - - - + + + CAP encoding means a specification used in CAP and NetAtalk, file server software for Macintosh. In the case of CAP encoding, for example, if a Japanese filename consists of 0x8ba4 and 0x974c, and @@ -269,14 +269,14 @@ Setting up Japanese charsets is quite difficult. This is mainly because:

    To use CAP encoding on Samba-3, you should use the unix charset parameter and VFS as in the VFS CAP smb.conf file. -

    Example 30.1. VFS CAP

    [global]
    # the locale name "CP932" may be different
    dos charset = CP932
    unix charset = CP932
    [cap-share]
    vfs option = cap

    - - - - +

    Example 30.1. VFS CAP

    [global]
    # the locale name "CP932" may be different
    dos charset = CP932
    unix charset = CP932
    [cap-share]
    vfs option = cap

    + + + + You should set CP932 if using GNU libiconv for unix charset. With this setting, filenames in the “cap-share” share are written with CAP encoding. -

    Individual Implementations

    +

    Individual Implementations

    Here is some additional information regarding individual implementations:

    GNU libiconv

    To handle Japanese correctly, you should apply the patch @@ -299,15 +299,15 @@ display charset = CP932 to glibc-2.2.5/2.3.1/2.3.2 or should use the patch-merged versions, glibc-2.3.3 or later.

    Using the above glibc, these setting are available: -

    dos charset = CP932
    unix charset = CP932 / eucJP-ms / UTF-8
    display charset = CP932

    +

    dos charset = CP932
    unix charset = CP932 / eucJP-ms / UTF-8
    display charset = CP932

    Other Japanese locales (for example, Shift_JIS and EUC-JP) should not be used because of the lack of the compatibility with Windows. -

    Migration from Samba-2.2 Series

    +

    Migration from Samba-2.2 Series

    Prior to Samba-2.2 series, the “coding system” parameter was used. The default codepage in Samba 2.x was code page 850. In the Samba-3 series this has been replaced with the unix charset parameter. Japanese Character Sets in Samba-2.2 and Samba-3 shows the mapping table when migrating from the Samba-2.2 series to Samba-3. -

    Table 30.1. Japanese Character Sets in Samba-2.2 and Samba-3

    Samba-2.2 Coding SystemSamba-3 unix charset
    SJISShift_JIS series
    EUCEUC-JP series
    EUC3[a]EUC-JP series
    CAPShift_JIS series + VFS
    HEXcurrently none
    UTF8UTF-8
    UTF8-Mac[b]currently none
    othersnone

    [a] Only exists in Japanese Samba version

    [b] Only exists in Japanese Samba version


    Common Errors

    CP850.so Can't Be Found

    “Samba is complaining about a missing CP850.so file.”

    +

    Table 30.1. Japanese Character Sets in Samba-2.2 and Samba-3

    Samba-2.2 Coding SystemSamba-3 unix charset
    SJISShift_JIS series
    EUCEUC-JP series
    EUC3[a]EUC-JP series
    CAPShift_JIS series + VFS
    HEXcurrently none
    UTF8UTF-8
    UTF8-Mac[b]currently none
    othersnone

    [a] Only exists in Japanese Samba version

    [b] Only exists in Japanese Samba version


    Common Errors

    CP850.so Can't Be Found

    “Samba is complaining about a missing CP850.so file.”

    CP850 is the default dos charset. The dos charset is used to convert data to the codepage used by your DOS clients. If you do not have any DOS clients, you can safely ignore this message.

    diff --git a/docs/htmldocs/Samba3-HOWTO/upgrading-to-3.0.html b/docs/htmldocs/Samba3-HOWTO/upgrading-to-3.0.html index 5708d52c12..bac3f2d885 100644 --- a/docs/htmldocs/Samba3-HOWTO/upgrading-to-3.0.html +++ b/docs/htmldocs/Samba3-HOWTO/upgrading-to-3.0.html @@ -1,8 +1,8 @@ -Chapter 35. Updating and Upgrading Samba

    Chapter 35. Updating and Upgrading Samba
    Prev Part IV. Migration and Updating Next

    Chapter 35. Updating and Upgrading Samba

    Jelmer R. Vernooij

    The Samba Team

    John H. Terpstra

    Samba Team

    Gerald (Jerry) Carter

    Samba Team

    August 16, 2007

    Table of Contents

    Key Update Requirements
    Upgrading from Samba-3.0.x to Samba-3.2.0
    Upgrading from Samba-2.x to Samba-3.0.25
    Quick Migration Guide
    New Featuers in Samba-3.x Series
    New Features in Samba-3.2.x Series
    New Features in Samba-3.0.x
    New Functionality

    +Chapter 35. Updating and Upgrading Samba

    Chapter 35. Updating and Upgrading Samba
    Prev Part IV. Migration and Updating Next

    Chapter 35. Updating and Upgrading Samba

    Jelmer R. Vernooij

    The Samba Team

    John H. Terpstra

    Samba Team

    Gerald (Jerry) Carter

    Samba Team

    August 16, 2007

    Table of Contents

    Key Update Requirements
    Upgrading from Samba-3.0.x to Samba-3.2.0
    Upgrading from Samba-2.x to Samba-3.0.25
    Quick Migration Guide
    New Featuers in Samba-3.x Series
    New Features in Samba-3.2.x Series
    New Features in Samba-3.0.x
    New Functionality

    This chapter provides a detailed record of changes made during the 3.x series releases. At this time this series consists of the 3.0.x series that is under the GNU GPL version 2 license, and the Samba 3.2.x series that is being released under the terms of the GNU GPL version 3 license. -

    Key Update Requirements

    +

    Key Update Requirements

    Samba is a fluid product in which there may be significant changes between releases. Some of these changes are brought about as a result of changes in the protocols that are used by Microsoft Windows network clients as a result of security or functionality updates through official Microsoft patches and updates. Samba must track @@ -13,113 +13,113 @@ all changes that apply to a new release will apply to follow-on releases also. F 3.0.23 affect all releases up to an including 3.0.25 and later. Samba 3.2.x was originaly cut from Samba 3.0.25 before 3.2.0-specific changes were applied. Unless a 3.0.x series feature is specifically revoked, the behavior of the 3.2.x series can be expected to follow the earlier pattern. -

    Upgrading from Samba-3.0.x to Samba-3.2.0

    +

    Upgrading from Samba-3.0.x to Samba-3.2.0

    Upgrading from Samba-2.x to Samba-3.0.25

    - - - + + + This chapter deals exclusively with the differences between Samba-3.0.25 and Samba-2.2.8a. It points out where configuration parameters have changed, and provides a simple guide for the move from 2.2.x to 3.0.25. -

    Quick Migration Guide

    +

    Quick Migration Guide

    Samba-3.0.25 default behavior should be approximately the same as Samba-2.2.x. The default behavior when the new parameter passdb backend is not defined in the smb.conf file provides the same default behavior as Samba-2.2.x with encrypt passwords = Yes and will use the smbpasswd database.

    - - + + So why say that behavior should be approximately the same as Samba-2.2.x? Because Samba-3.0.25 can negotiate new protocols, such as support for native Unicode, that may result in differing protocol code paths being taken. The new behavior under such circumstances is not exactly the same as the old one. The good news is that the domain and machine SIDs will be preserved across the upgrade.

    - - - - + + + + If the Samba-2.2.x system is using an LDAP backend, and there is no time to update the LDAP database, then make sure that passdb backend = ldapsam_compat is specified in the smb.conf file. For the rest, behavior should remain more or less the same. At a later date, when there is time to implement a new Samba-3-compatible LDAP backend, it is possible to migrate the old LDAP database to the new one through use of the pdbedit. See The pdbedit Command. -

    New Featuers in Samba-3.x Series

    -

    New Features in Samba-3.2.x Series

    -

    New Features in Samba-3.0.x

    +

    New Featuers in Samba-3.x Series

    +

    New Features in Samba-3.2.x Series

    +

    New Features in Samba-3.0.x

    The major new features are:

    1. - - + + Active Directory support. This release is able to join an ADS realm as a member server and authenticate users using LDAP/Kerberos.

    2. - - + + Unicode support. Samba will now negotiate Unicode on the wire, and internally there is a much better infrastructure for multibyte and Unicode character sets.

    3. - + New authentication system. The internal authentication system has been almost completely rewritten. Most of the changes are internal, but the new authoring system is also very configurable.

    4. - + New filename mangling system. The filename mangling system has been completely rewritten. An internal database now stores mangling maps persistently.

    5. - + New “net” command. A new “net” command has been added. It is somewhat similar to the “net” command in Windows. Eventually, we plan to replace a bunch of other utilities (such as smbpasswd) with subcommands in “net”.

    6. - + Samba now negotiates NT-style status32 codes on the wire. This considerably improves error handling.

    7. - + Better Windows 200x/XP printing support, including publishing printer attributes in Active Directory.

    8. - - - + + + New loadable RPC modules for passdb backends and character sets.

    9. - + New default dual-daemon winbindd support for better performance.

    10. - - - + + + Support for migrating from a Windows NT 4.0 domain to a Samba domain and maintaining user, group, and domain SIDs.

    11. - - + + Support for establishing trust relationships with Windows NT 4.0 domain controllers.

    12. - - - + + + Initial support for a distributed Winbind architecture using an LDAP directory for storing SID to UID/GID mappings.

    13. Major updates to the Samba documentation tree.

    14. - - + + Full support for client and server SMB signing to ensure compatibility with default Windows 2003 security settings.

    Plus lots of other improvements! -

    Configuration Parameter Changes

    +

    Configuration Parameter Changes

    This section contains a brief listing of changes to smb.conf options since the Samba-2.2.x series up to and including Samba-3.0.25.

    @@ -130,83 +130,83 @@ Whenever a Samba update or upgrade is performed it is highly recommended to read WHATSNEW.txt that is part of the Samba distribution tarball. This file may also be obtain on-line from the Samba web site, in the right column, under Current Stable Release, by clicking on Release Notes. -

    Removed Parameters

    +

    Removed Parameters

    In alphabetical order, these are the parameters eliminated from Samba-2.2.x through 3.0.25. -

    • admin log

    • alternate permissions

    • character set

    • client codepage

    • code page directory

    • coding system

    • domain admin group

    • domain guest group

    • enable rid algorithm

    • enable svcctl

    • force unknown acl user

    • hosts equiv

    • ldap filter

    • min password length

    • nt smb support

    • post script

    • printer admin

    • printer driver

    • printer driver file

    • printer driver location

    • read size

    • source environment

    • status

    • strip dot

    • total print jobs

    • unicode

    • use rhosts

    • valid chars

    • vfs options

    • winbind enable local accounts

    • winbind max idle children

    • wins partners

    New Parameters

    The following new parameters have been released up to and including Samba 3.0.25 (grouped by function:)

    Remote Management

    • abort shutdown script

    • shutdown script

    User and Group Account Management

    • add group script

    • add machine script

    • add user to group script

    • algorithmic rid base

    • delete group script

    • delete user from group script

    • passdb backend

    • rename user script

    • set primary group script

    • username map script

    Authentication

    • auth methods

    • ldap password sync

    • passdb expand explicit

    • realm

    Protocol Options

    • add port command

    • afs token lifetime

    • client lanman auth

    • client NTLMv2 auth

    • client schannel

    • client signing

    • client use spnego

    • defer sharing violations

    • disable netbios

    • dmapi support

    • enable privileges

    • use kerberos keytab

    • log nt token command

    • ntlm auth

    • paranoid server security

    • sendfile

    • server schannel

    • server signing

    • smb ports

    • svcctl list

    • use spnego

    File Service

    • allocation roundup size

    • acl check permissions

    • acl group control

    • acl map full control

    • aio read size

    • aio write size

    • dfree cache time

    • dfree command

    • ea support

    • enable asu support

    • fam change notify

    • force unknown acl user

    • get quota command

    • hide special files

    • hide unwriteable files

    • inherit owner

    • hostname lookups

    • kernel change notify

    • mangle prefix

    • map acl inherit

    • map read only

    • max stat cache size

    • msdfs proxy

    • open files database hash size

    • set quota command

    • store dos attributes

    • use sendfile

    • usershare allow guests

    • usershare max shares

    • usershare owner only

    • usershare path

    • usershare prefix allow list

    • usershare prefix deny list

    • usershare template share

    • vfs objects

    Printing

    • cups options

    • cups server

    • force printername

    • iprint server

    • max reported print jobs

    • printcap cache time

    Unicode and Character Sets

    • display charset

    • dos charset

    • UNIX charset

    SID to UID/GID Mappings

    • idmap backend

    • idmap gid

    • idmap uid

    • username map script

    • winbind nss info

    • winbind offline logon

    • winbind refresh tickets

    • winbind trusted domains only

    • template primary group

    LDAP

    • ldap delete dn

    • ldap group suffix

    • ldap idmap suffix

    • ldap machine suffix

    • ldap passwd sync

    • ldap replication sleep

    • ldap timeout

    • ldap user suffix

    General Configuration

    • eventlog list

    • preload modules

    • reset on zero vc

    • privatedir

    Modified Parameters (Changes in Behavior)

    • acl group control (new default is No, deprecated parameter)

    • change notify timeout (scope changed)

    • dos filemode (disabled by default)

    • dos filetimes (enabled by default)

    • enable asu support (disabled by default)

    • enable privileges (enabled by default)

    • encrypt passwords (enabled by default)

    • host msdfs (enabled by default)

    • mangling method (set to hash2 by default)

    • map to guest

    • only user (deprecated)

    • passwd chat

    • passwd program

    • password server

    • restrict anonymous (integer value)

    • security (new ads value)

    • strict locking (auto by default)

    • winbind cache time (increased to 5 minutes)

    • winbind enum groups (disabled by default)

    • winbind enum users (disabled by default)

    • winbind nested groups (enabled by default)

    • winbind uid (deprecated in favor of idmap uid)

    • winbind gid (deprecated in favor of idmap gid)

    • winbindd nss info

    • write cache (deprecated)

    New Functionality

    - +

    • admin log

    • alternate permissions

    • character set

    • client codepage

    • code page directory

    • coding system

    • domain admin group

    • domain guest group

    • enable rid algorithm

    • enable svcctl

    • force unknown acl user

    • hosts equiv

    • ldap filter

    • min password length

    • nt smb support

    • post script

    • printer admin

    • printer driver

    • printer driver file

    • printer driver location

    • read size

    • source environment

    • status

    • strip dot

    • total print jobs

    • unicode

    • use rhosts

    • valid chars

    • vfs options

    • winbind enable local accounts

    • winbind max idle children

    • wins partners

    New Parameters

    The following new parameters have been released up to and including Samba 3.0.25 (grouped by function:)

    Remote Management

    • abort shutdown script

    • shutdown script

    User and Group Account Management

    • add group script

    • add machine script

    • add user to group script

    • algorithmic rid base

    • delete group script

    • delete user from group script

    • passdb backend

    • rename user script

    • set primary group script

    • username map script

    Authentication

    • auth methods

    • ldap password sync

    • passdb expand explicit

    • realm

    Protocol Options

    • add port command

    • afs token lifetime

    • client lanman auth

    • client NTLMv2 auth

    • client schannel

    • client signing

    • client use spnego

    • defer sharing violations

    • disable netbios

    • dmapi support

    • enable privileges

    • use kerberos keytab

    • log nt token command

    • ntlm auth

    • paranoid server security

    • sendfile

    • server schannel

    • server signing

    • smb ports

    • svcctl list

    • use spnego

    File Service

    • allocation roundup size

    • acl check permissions

    • acl group control

    • acl map full control

    • aio read size

    • aio write size

    • dfree cache time

    • dfree command

    • ea support

    • enable asu support

    • fam change notify

    • force unknown acl user

    • get quota command

    • hide special files

    • hide unwriteable files

    • inherit owner

    • hostname lookups

    • kernel change notify

    • mangle prefix

    • map acl inherit

    • map read only

    • max stat cache size

    • msdfs proxy

    • open files database hash size

    • set quota command

    • store dos attributes

    • use sendfile

    • usershare allow guests

    • usershare max shares

    • usershare owner only

    • usershare path

    • usershare prefix allow list

    • usershare prefix deny list

    • usershare template share

    • vfs objects

    Printing

    • cups options

    • cups server

    • force printername

    • iprint server

    • max reported print jobs

    • printcap cache time

    Unicode and Character Sets

    • display charset

    • dos charset

    • UNIX charset

    SID to UID/GID Mappings

    • idmap backend

    • idmap gid

    • idmap uid

    • username map script

    • winbind nss info

    • winbind offline logon

    • winbind refresh tickets

    • winbind trusted domains only

    • template primary group

    LDAP

    • ldap delete dn

    • ldap group suffix

    • ldap idmap suffix

    • ldap machine suffix

    • ldap passwd sync

    • ldap replication sleep

    • ldap timeout

    • ldap user suffix

    General Configuration

    • eventlog list

    • preload modules

    • reset on zero vc

    • privatedir

    Modified Parameters (Changes in Behavior)

    • acl group control (new default is No, deprecated parameter)

    • change notify timeout (scope changed)

    • dos filemode (disabled by default)

    • dos filetimes (enabled by default)

    • enable asu support (disabled by default)

    • enable privileges (enabled by default)

    • encrypt passwords (enabled by default)

    • host msdfs (enabled by default)

    • mangling method (set to hash2 by default)

    • map to guest

    • only user (deprecated)

    • passwd chat

    • passwd program

    • password server

    • restrict anonymous (integer value)

    • security (new ads value)

    • strict locking (auto by default)

    • winbind cache time (increased to 5 minutes)

    • winbind enum groups (disabled by default)

    • winbind enum users (disabled by default)

    • winbind nested groups (enabled by default)

    • winbind uid (deprecated in favor of idmap uid)

    • winbind gid (deprecated in favor of idmap gid)

    • winbindd nss info

    • write cache (deprecated)

    New Functionality

    + The major changes in behavior since that Samba-2.2.x series are documented in this section. Please refer to the WHATSNEW.txt file that ships with every release of Samba to obtain detailed information regarding the changes that have been made during the life of the current Samba release. -

    TDB Data Files

    +

    TDB Data Files

    Refer to Installation, Chapter 1, Chapter 1 for information pertaining to the Samba-3 data files, their location and the information that must be preserved across server migrations, updates and upgrades.

    - + Please remember to back up your existing ${lock directory}/*tdb before upgrading to Samba-3. If necessary, Samba will upgrade databases as they are opened. Downgrading from Samba-3 to 2.2, or reversion to an earlier version of Samba-3 from a later release, is an unsupported path.

    - + The old Samba-2.2.x tdb files are described in the next table.

    Table 35.1. Samba-2.2.x TDB File Descriptions

    NameDescriptionBackup?
    account_policyUser policy settingsyes
    brlockByte-range file locking information.no
    connections

    Client connection information

    		no
    lockingTemporary file locking data.no
    messages

    Temporary storage of messages being processed by smbd.

    		no
    ntdrivers

    Stores per-printer driver information.

    		yes
    ntforms

    Stores per-printer forms information.

    		yes
    ntprinters

    Stores the per-printer devmode configuration settings.

    		yes
    printing/*.tdb

    Cached output from lpq command created on a per-print-service basis.

    		no
    registry

    Read-only Samba registry skeleton that provides support for - exporting various database tables via the winreg RPCs.

    		no
    sessionid

    Temporary cache for miscellaneous session information.

    		no
    share_infoShare ACL settings.yes
    unexpected

    Packets received for which no process was listening.

    		no
    winbindd_cache

    Cache of identity information received from an NT4 or an ADS domain.

    		yes
    winbindd_idmap

    New ID map table from SIDS to UNIX UIDs/GIDs.

    		yes

    Changes in Behavior

    + exporting various database tables via the winreg RPCs.

    nosessionid

    Temporary cache for miscellaneous session information.

    noshare_infoShare ACL settings.yesunexpected

    Packets received for which no process was listening.

    nowinbindd_cache

    Cache of identity information received from an NT4 or an ADS domain.

    yeswinbindd_idmap

    New ID map table from SIDS to UNIX UIDs/GIDs.

    yes

    Changes in Behavior

    The following issues are known changes in behavior between Samba-2.2 and Samba-3 that may affect certain installations of Samba.

    1. - - - + + + When operating as a member of a Windows domain, Samba-2.2 would map any users authenticated by the remote DC to the “guest account” if a UID could not be obtained via the getpwnam() call. Samba-3 rejects the connection with the error message “NT_STATUS_LOGON_FAILURE.” There is no current workaround to re-establish the Samba-2.2 behavior.

    2. - - + + When adding machines to a Samba-2.2 controlled domain, the “add user script” was used to create the UNIX identity of the machine trust account. Samba-3 introduces a new “add machine script” that must be specified for this purpose. Samba-3 will not fall back to using the “add user script” in the absence of an “add machine script”. -

    Passdb Backends and Authentication

    +

    Passdb Backends and Authentication

    There have been a few new changes that Samba administrators should be aware of when moving to Samba-3.

    1. - + Encrypted passwords have been enabled by default in order to interoperate better with out-of-the-box Windows client installations. This does mean that either (a) a Samba account must be created for each user, or (b) “encrypt passwords = no” must be explicitly defined in smb.conf.

    2. - - - + + + Inclusion of new security = ads option for integration with an Active Directory domain using the native Windows Kerberos 5 and LDAP protocols.

    - + Samba-3 also includes the possibility of setting up chains of authentication methods (auth methods) and account storage backends (passdb backend). Please refer to the smb.conf man page and Account Information Databases, for details. While both parameters assume sane default values, it is likely that you will need to understand what the values actually mean in order to ensure Samba operates correctly.

    - - - + + + Certain functions of the smbpasswd tool have been split between the new smbpasswd utility, the net tool, and the new pdbedit utility. See the respective man pages for details. -

    LDAP

    +

    LDAP

    This section outlines the new features effecting Samba/LDAP integration. -

    New Schema

    - - - - +

    New Schema

    + + + + A new object class (sambaSamAccount) has been introduced to replace the old sambaAccount. This change aids in the renaming of attributes to prevent clashes with attributes from other vendors. There is a @@ -214,29 +214,29 @@ In alphabetical order, these are the parameters eliminated from Samba-2.2.x thro file to the new schema.

    Example: - + 

     		$ ldapsearch .... -LLL -b "ou=people,dc=..." > old.ldif
 		$ convertSambaAccount --sid <DOM SID> --input old.ldif --output new.ldif

    - + The <DOM SID> can be obtained by running 

     $ net getlocalsid <DOMAINNAME>

    - + on the Samba PDC as root.

    Under Samba-2.x the domain SID can be obtained by executing: - + 

     $ smbpasswd -S <DOMAINNAME>

    - - - - + + + + The old sambaAccount schema may still be used by specifying the ldapsam_compat passdb backend. However, the sambaAccount and associated attributes have been moved to the historical section of @@ -246,53 +246,53 @@ In alphabetical order, these are the parameters eliminated from Samba-2.2.x thro

    Other new object classes and their uses include:

    • - - - - - - + + + + + + sambaDomain domain information used to allocate RIDs for users and groups as necessary. The attributes are added in “ldap suffix” directory entry automatically if an idmap UID/GID range has been set and the “ldapsam” passdb backend has been selected.

    • - - - + + + sambaGroupMapping an object representing the relationship between a posixGroup and a Windows group/SID. These entries are stored in the “ldap group suffix” and managed by the “net groupmap” command.

    • - - - - + + + + sambaUNIXIdPool created in the “ldap idmap suffix” entry automatically and contains the next available “idmap UID” and “idmap GID”.

    • - - + + sambaIdmapEntry object storing a mapping between a SID and a UNIX UID/GID. These objects are created by the idmap_ldap module as needed. -

    New Suffix for Searching

    - - - - - - - +

    New Suffix for Searching

    + + + + + + + The following new smb.conf parameters have been added to aid in directing certain LDAP queries when passdb backend = ldapsam://... has been specified.

    • ldap suffix used to search for user and computer accounts.

    • ldap user suffix used to store user accounts.

    • ldap machine suffix used to store machine trust accounts.

    • ldap group suffix location of posixGroup/sambaGroupMapping entries.

    • ldap idmap suffix location of sambaIdmapEntry objects.

    - - + + If an ldap suffix is defined, it will be appended to all of the remaining subsuffix parameters. In this case, the order of the suffix listings in smb.conf is important. Always place the ldap suffix first @@ -300,13 +300,13 @@ In alphabetical order, these are the parameters eliminated from Samba-2.2.x thro

    Due to a limitation in Samba's smb.conf parsing, you should not surround the domain names with quotation marks. -

    IdMap LDAP Support

    - +

    IdMap LDAP Support

    + Samba-3 supports an LDAP backend for the idmap subsystem. The following options inform Samba that the idmap table should be stored on the directory server onterose in the ou=Idmap,dc=quenya,dc=org partition. -

    [global]
    ...
    idmap backend = ldap:ldap://onterose/
    ldap idmap suffix = ou=Idmap
    idmap uid = 40000-50000
    idmap gid = 40000-50000

    - +

    [global]
    ...
    idmap backend = ldap:ldap://onterose/
    ldap idmap suffix = ou=Idmap
    idmap uid = 40000-50000
    idmap gid = 40000-50000

    + This configuration allows Winbind installations on multiple servers to share a UID/GID number space, thus avoiding the interoperability problems with NFS that were present in Samba-2.2. diff --git a/docs/htmldocs/Samba3-HOWTO/winbind.html b/docs/htmldocs/Samba3-HOWTO/winbind.html index f8f00b4fc6..1091d19ae6 100644 --- a/docs/htmldocs/Samba3-HOWTO/winbind.html +++ b/docs/htmldocs/Samba3-HOWTO/winbind.html @@ -1,23 +1,23 @@ -Chapter 24. Winbind: Use of Domain Accounts

    Chapter 24. Winbind: Use of Domain Accounts
    Prev Part III. Advanced Configuration Next

    Chapter 24. Winbind: Use of Domain Accounts

    Tim Potter

    Samba Team

    Andrew Tridgell

    Samba Team

    Naag Mummaneni

    Notes for Solaris 

    John Trostel

    SNAP

    Jelmer R. Vernooij

    The Samba Team

    John H. Terpstra

    Samba Team

    June 15, 2005

    Table of Contents

    Features and Benefits
    Introduction
    What Winbind Provides
    Target Uses
    Handling of Foreign SIDs
    How Winbind Works
    Microsoft Remote Procedure Calls
    Microsoft Active Directory Services
    Name Service Switch
    Pluggable Authentication Modules
    User and Group ID Allocation
    Result Caching
    Installation and Configuration
    Introduction
    Requirements
    Testing Things Out
    Conclusion
    Common Errors
    NSCD Problem Warning
    Winbind Is Not Resolving Users and Groups

    Features and Benefits

    - - +Chapter 24. Winbind: Use of Domain Accounts

    Chapter 24. Winbind: Use of Domain Accounts
    Prev Part III. Advanced Configuration Next

    Chapter 24. Winbind: Use of Domain Accounts

    Tim Potter

    Samba Team

    Andrew Tridgell

    Samba Team

    Naag Mummaneni

    Notes for Solaris 

    John Trostel

    SNAP

    Jelmer R. Vernooij

    The Samba Team

    John H. Terpstra

    Samba Team

    June 15, 2005

    Table of Contents

    Features and Benefits
    Introduction
    What Winbind Provides
    Target Uses
    Handling of Foreign SIDs
    How Winbind Works
    Microsoft Remote Procedure Calls
    Microsoft Active Directory Services
    Name Service Switch
    Pluggable Authentication Modules
    User and Group ID Allocation
    Result Caching
    Installation and Configuration
    Introduction
    Requirements
    Testing Things Out
    Conclusion
    Common Errors
    NSCD Problem Warning
    Winbind Is Not Resolving Users and Groups

    Features and Benefits

    + + Integration of UNIX and Microsoft Windows NT through a unified logon has been considered a “holy grail” in heterogeneous computing environments for a long time.

    - - - - + + + + There is one other facility without which UNIX and Microsoft Windows network interoperability would suffer greatly. It is imperative that there be a mechanism for sharing files across UNIX systems and to be able to assign domain user and group ownerships with integrity.

    - - - - + + + + winbind is a component of the Samba suite of programs that solves the unified logon problem. Winbind uses a UNIX implementation of Microsoft RPC calls, Pluggable Authentication Modules (PAMs), and the name service switch (NSS) to @@ -27,23 +27,23 @@

    Winbind provides three separate functions:

    • - - + + Authentication of user credentials (via PAM). This makes it possible to log onto a UNIX/Linux system using user and group accounts from a Windows NT4 (including a Samba domain) or an Active Directory domain.

    • - - + + Identity resolution (via NSS). This is the default when winbind is not used.

    • - - - - - - - + + + + + + + Winbind maintains a database called winbind_idmap.tdb in which it stores mappings between UNIX UIDs, GIDs, and NT SIDs. This mapping is used only for users and groups that do not have a local UID/GID. It stores the UID/GID @@ -52,23 +52,23 @@ then instead of using a local mapping, Winbind will obtain this information from the LDAP database.

    Note

    - - - - - - + + + + + + If winbindd is not running, smbd (which calls winbindd) will fall back to using purely local information from /etc/passwd and /etc/group and no dynamic mapping will be used. On an operating system that has been enabled with the NSS, the resolution of user and group information will be accomplished via NSS. -

    Figure 24.1. Winbind Idmap

    Winbind Idmap

    Introduction

    It is well known that UNIX and Microsoft Windows NT have +

    Figure 24.1. Winbind Idmap

    Winbind Idmap

    Introduction

    It is well known that UNIX and Microsoft Windows NT have different models for representing user and group information and use different technologies for implementing them. This fact has made it difficult to integrate the two systems in a satisfactory manner.

    - - + + One common solution in use today has been to create identically named user accounts on both the UNIX and Windows systems and use the Samba suite of programs to provide file and print services @@ -81,29 +81,29 @@

  • Authenticating Windows NT users.

  • Password changing for Windows NT users.

    • - - + + Ideally, a prospective solution to the unified logon problem would satisfy all the above components without duplication of information on the UNIX machines and without creating additional tasks for the system administrator when maintaining users and groups on either system. The Winbind system provides a simple and elegant solution to all three components of the unified logon - problem.

    What Winbind Provides

    - - - - + problem.

    What Winbind Provides

    + + + + Winbind unifies UNIX and Windows NT account management by allowing a UNIX box to become a full member of an NT domain. Once this is done, the UNIX box will see NT users and groups as if they were “native” UNIX users and groups, allowing the NT domain to be used in much the same manner that NIS+ is used within UNIX-only environments.

    - - - - + + + + The end result is that whenever a program on the UNIX machine asks the operating system to look up a user or group name, the query will be resolved by asking the @@ -112,26 +112,26 @@ (via the NSS name resolution modules in the C library), this redirection to the NT domain controller is completely transparent.

    - - + + Users on the UNIX machine can then use NT user and group names as they would “native” UNIX names. They can chown files so they are owned by NT domain users or even login to the UNIX machine and run a UNIX X-Window session as a domain user.

    - + The only obvious indication that Winbind is being used is that user and group names take the form DOMAIN\user and DOMAIN\group. This is necessary because it allows Winbind to determine that redirection to a domain controller is wanted for a particular lookup and which trusted domain is being referenced.

    - - + + Additionally, Winbind provides an authentication service that hooks into the PAM system to provide authentication via an NT domain to any PAM-enabled applications. This capability solves the problem of synchronizing passwords between systems, since all passwords are stored in a single - location (on the domain controller).

    Target Uses

    - + location (on the domain controller).

    Target Uses

    + Winbind is targeted at organizations that have an existing NT-based domain infrastructure into which they wish to put UNIX workstations or servers. Winbind will allow these @@ -139,40 +139,40 @@ maintain a separate account infrastructure. This greatly simplifies the administrative overhead of deploying UNIX workstations into an NT-based organization.

    - - + + Another interesting way in which we expect Winbind to be used is as a central part of UNIX-based appliances. Appliances that provide file and print services to Microsoft-based networks will be able to use Winbind to provide seamless integration of - the appliance into the domain.

    Handling of Foreign SIDs

    - + the appliance into the domain.

    Handling of Foreign SIDs

    + The term foreign SID is often met with the reaction that it is not relevant to a particular environment. The following documents an interchange that took place on the Samba mailing list. It is a good example of the confusion often expressed regarding the use of winbind.

    - + Fact: Winbind is needed to handle users who use workstations that are NOT part of the local domain.

    - + Response: “Why? I've used Samba with workstations that are not part of my domains lots of times without using winbind. I thought winbind was for using Samba as a member server in a domain controlled by another Samba/Windows PDC.”

    - - - + + + If the Samba server will be accessed from a domain other than the local Samba domain, or if there will be access from machines that are not local domain members, winbind will permit the allocation of UIDs and GIDs from the assigned pool that will keep the identity of the foreign user separate from users that are members of the Samba domain.

    - - - - + + + + This means that winbind is eminently useful in cases where a single Samba PDC on a local network is combined with both domain member and domain non-member workstations. If winbind is not used, the user george on a Windows workstation that is not a domain @@ -181,49 +181,49 @@ is that the local user george will be treated as the account DOMAIN\george and the foreign (non-member of the domain) account will be treated as MACHINE\george because each has a different SID. -

    How Winbind Works

    - - - - +

    How Winbind Works

    + + + + The Winbind system is designed around a client/server architecture. A long-running winbindd daemon listens on a UNIX domain socket waiting for requests to arrive. These requests are generated by the NSS and PAM clients and are processed sequentially.

    The technologies used to implement Winbind are described - in detail below.

    Microsoft Remote Procedure Calls

    - - - - - + in detail below.

    Microsoft Remote Procedure Calls

    + + + + + Over the last few years, efforts have been underway by various Samba Team members to implement various aspects of the Microsoft Remote Procedure Call (MSRPC) system. This system is used for most network-related operations between Windows NT machines, including remote management, user authentication, and print spooling. Although initially this work was done to aid the implementation of Primary Domain Controller (PDC) functionality in Samba, it has also yielded a body of code that can be used for other purposes.

    - - - + + + Winbind uses various MSRPC calls to enumerate domain users and groups and to obtain detailed information about individual users or groups. Other MSRPC calls can be used to authenticate NT domain users and to change user passwords. By directly querying a Windows PDC for user and group information, Winbind maps the NT account information onto UNIX user and group names. -

    Microsoft Active Directory Services

    - - - - +

    Microsoft Active Directory Services

    + + + + Since late 2001, Samba has gained the ability to interact with Microsoft Windows 2000 using its “native mode” protocols rather than the NT4 RPC services. Using LDAP and Kerberos, a domain member running Winbind can enumerate users and groups in exactly the same way as a Windows 200x client would, and in so doing provide a much more efficient and effective Winbind implementation. -

    Name Service Switch

    - - - - +

    Name Service Switch

    + + + + The NSS is a feature that is present in many UNIX operating systems. It allows system information such as hostnames, mail aliases, and user information to be resolved from different sources. For example, a standalone @@ -232,20 +232,20 @@ may first attempt to resolve system information from local files, and then consult an NIS database for user information or a DNS server for hostname information.

    - - - - - + + + + + The NSS application programming interface allows Winbind to present itself as a source of system information when resolving UNIX usernames and groups. Winbind uses this interface and information obtained from a Windows NT server using MSRPC calls to provide a new source of account enumeration. Using standard UNIX library calls, you can enumerate the users and groups on a UNIX machine running Winbind and see all users and groups in an NT domain plus any trusted domain as though they were local users and groups.

    - - - + + + The primary control file for NSS is /etc/nsswitch.conf. When a UNIX application makes a request to do a lookup, the C library looks in /etc/nsswitch.conf for a line that matches the service type being requested; for example, the “passwd” service type is used when @@ -254,46 +254,46 @@ 

     passwd: files example

    - - - + + + then the C library will first load a module called /lib/libnss_files.so followed by the module /lib/libnss_example.so. The C library will dynamically load each of these modules in turn and call resolver functions within the modules to try to resolve the request. Once the request is resolved, the C library returns the result to the application.

    - - - + + + This NSS interface provides an easy way for Winbind to hook into the operating system. All that needs to be done is to put libnss_winbind.so in /lib/ then add “winbind” into /etc/nsswitch.conf at the appropriate place. The C library will then call Winbind to resolve user and group names. -

    Pluggable Authentication Modules

    - - - - +

    Pluggable Authentication Modules

    + + + + PAMs provide a system for abstracting authentication and authorization technologies. With a PAM module, it is possible to specify different authentication methods for different system applications without having to recompile these applications. PAM is also useful for implementing a particular policy for authorization. For example, a system administrator may only allow console logins from users stored in the local password file but only allow users resolved from an NIS database to log in over the network.

    - - - - - + + + + + Winbind uses the authentication management and password management PAM interface to integrate Windows NT users into a UNIX system. This allows Windows NT users to log in to a UNIX machine and be authenticated against a suitable PDC. These users can also change their passwords and have this change take effect directly on the PDC.

    - - - - + + + + PAM is configured by providing control files in the directory /etc/pam.d/ for each of the services that require authentication. When an authentication request is made by an application, the PAM code in the C library looks up this control file to determine what modules to load to do the @@ -301,10 +301,10 @@ passwd: files example very easy: simply copy the pam_winbind.so module to /lib/security/, and the PAM control files for relevant services are updated to allow authentication via Winbind. See the PAM documentation in PAM-Based Distributed Authentication, for more information. -

    User and Group ID Allocation

    - - - +

    User and Group ID Allocation

    + + + When a user or group is created under Windows NT/200x, it is allocated a numerical relative identifier (RID). This is slightly different from UNIX, which has a range of numbers that are used to identify users and the same range used to identify groups. It is Winbind's job to convert RIDs to UNIX ID numbers and vice versa. @@ -313,18 +313,18 @@ passwd: files example allocated the next UNIX ID from the range. The same process applies for Windows NT groups. Over time, Winbind will have mapped all Windows NT users and groups to UNIX user IDs and group IDs.

    - - - - + + + + The results of this mapping are stored persistently in an ID mapping database held in a tdb database. This ensures that RIDs are mapped to UNIX IDs in a consistent way. -

    Result Caching

    - - - - - +

    Result Caching

    + + + + + An active directory system can generate a lot of user and group name lookups. To reduce the network cost of these lookups, Winbind uses a caching scheme based on the SAM sequence number supplied by NT domain controllers. User or group information returned by a PDC is cached by Winbind along with a sequence number @@ -332,66 +332,66 @@ passwd: files example information is modified. If a cached entry has expired, the sequence number is requested from the PDC and compared against the sequence number of the cached entry. If the sequence numbers do not match, then the cached information is discarded and up-to-date information is requested directly from the PDC. -

    Installation and Configuration

    Introduction

    - - - +

    Installation and Configuration

    Introduction

    + + + This section describes the procedures used to get Winbind up and running. Winbind is capable of providing access and authentication control for Windows Domain users through an NT or Windows 200x PDC for regular services, such as telnet and ftp, as well for Samba services.

    • Why should I do this?

      - - - - + + + + This allows the Samba administrator to rely on the authentication mechanisms on the Windows NT/200x PDC for the authentication of domain members. Windows NT/200x users no longer need to have separate accounts on the Samba server.

    • Who should be reading this document?

      - - + + This document is designed for system administrators. If you are implementing Samba on a file server and wish to (fairly easily) integrate existing Windows NT/200x users from your PDC onto the Samba server, this document is for you. -

    Requirements

    - - - +

    Requirements

    + + + If you have a Samba configuration file that you are currently using, BACK IT UP! If your system already uses PAM, back up the /etc/pam.d directory contents! If you haven't already made a boot disk, MAKE ONE NOW!

    - - - + + + Messing with the PAM configuration files can make it nearly impossible to log in to your machine. That's why you want to be able to boot back into your machine in single-user mode and restore your /etc/pam.d to the original state it was in if you get frustrated with the way things are going.

    - - + + The latest version of Samba-3 includes a functioning winbindd daemon. Please refer to the main Samba Web page, or better yet, your closest Samba mirror site for instructions on downloading the source code.

    - - - - + + + + To allow domain users the ability to access Samba shares and files, as well as potentially other services provided by your Samba machine, PAM must be set up properly on your machine. In order to compile the Winbind modules, you should have at least the PAM development libraries installed on your system. Please refer to the PAM Web site http://www.kernel.org/pub/linux/libs/pam/. -

    Testing Things Out

    - - - - - +

    Testing Things Out

    + + + + + Before starting, it is probably best to kill off all the Samba-related daemons running on your server. Kill off all smbd, nmbd, and winbindd processes that may be running. To use PAM, make sure that you have the standard PAM package that supplies the /etc/pam.d @@ -399,11 +399,11 @@ directory structure, including the PAM modules that are used by PAM-aware servic and the /usr/doc and /usr/man entries for PAM. Winbind is built better in Samba if the pam-devel package is also installed. This package includes the header files needed to compile PAM-aware applications. -

    Configure nsswitch.conf and the Winbind Libraries on Linux and Solaris

    - - - - +

    Configure nsswitch.conf and the Winbind Libraries on Linux and Solaris

    + + + + PAM is a standard component of most current generation UNIX/Linux systems. Unfortunately, few systems install the pam-devel libraries that are needed to build PAM-enabled Samba. Additionally, Samba-3 may auto-install the Winbind files into their correct locations on your system, so before you get too far down @@ -413,7 +413,7 @@ necessary. You may only need to configure

    The libraries needed to run the winbindd daemon through nsswitch need to be copied to their proper locations:

    - + 

     root# cp ../samba/source/nsswitch/libnss_winbind.so /lib

    @@ -422,14 +422,14 @@ I also found it necessary to make the following symbolic link:

    root# ln -s /lib/libnss_winbind.so /lib/libnss_winbind.so.2

    And, in the case of Sun Solaris: - + 

     root# ln -s /usr/lib/libnss_winbind.so /usr/lib/libnss_winbind.so.1
 root# ln -s /usr/lib/libnss_winbind.so /usr/lib/nss_winbind.so.1
 root# ln -s /usr/lib/libnss_winbind.so /usr/lib/nss_winbind.so.2

    - + As root, edit /etc/nsswitch.conf to allow user and group entries to be visible from the winbindd daemon. My /etc/nsswitch.conf file looked like this after editing: 

    @@ -437,11 +437,11 @@ passwd:     files winbind
 shadow:     files
 group:      files winbind

    - - - - - + + + + + The libraries needed by the winbindd daemon will be automatically entered into the ldconfig cache the next time your system reboots, but it is faster (and you do not need to reboot) if you do it manually: @@ -453,11 +453,11 @@ search path that is used by the dynamic link loader. The use of the ldconfig command so that we may see proof that this library is indeed recognized by the dynamic link loader.

    - - - - - + + + + + The Sun Solaris dynamic link loader management tool is called crle. The use of this tool is necessary to instruct the dynamic link loader to search directories that contain library files that were not supplied as part of the original operating system platform. @@ -480,13 +480,13 @@ Command line:

    From this it is apparent that the /usr/local/lib directory is included in the search dynamic link libraries in order to satisfy object module dependencies. -

    NSS Winbind on AIX

    (This section is only for those running AIX.)

    - - - - - - +

    NSS Winbind on AIX

    (This section is only for those running AIX.)

    + + + + + + The Winbind AIX identification module gets built as libnss_winbind.so in the nsswitch directory of the Samba source. This file can be copied to /usr/lib/security, and the AIX naming convention would indicate that it should be named WINBIND. A stanza like the following: @@ -504,50 +504,50 @@ describes the System Management Guide: Operating System and Devices. -

    Configure smb.conf

    - - - +

    Configure smb.conf

    + + + Several parameters are needed in the smb.conf file to control the behavior of winbindd. These are described in more detail in the winbindd(8) man page. My smb.conf file, as shown in the smb.conf for Winbind Setup, was modified to include the necessary entries in the [global] section. -

    Example 24.1. smb.conf for Winbind Setup

    [global]
    # separate domain and username with '\', like DOMAIN\username
    winbind separator = \
    # use uids from 10000 to 20000 for domain users
    idmap uid = 10000-20000
    # use gids from 10000 to 20000 for domain groups
    idmap gid = 10000-20000
    # allow enumeration of winbind users and groups
    winbind enum users = yes
    winbind enum groups = yes
    # give winbind users a real shell (only needed if they have telnet access)
    template homedir = /home/winnt/%D/%U
    template shell = /bin/bash

    Join the Samba Server to the PDC Domain

    - - - +

    Example 24.1. smb.conf for Winbind Setup

    [global]
    # separate domain and username with '\', like DOMAIN\username
    winbind separator = \
    # use uids from 10000 to 20000 for domain users
    idmap uid = 10000-20000
    # use gids from 10000 to 20000 for domain groups
    idmap gid = 10000-20000
    # allow enumeration of winbind users and groups
    winbind enum users = yes
    winbind enum groups = yes
    # give winbind users a real shell (only needed if they have telnet access)
    template homedir = /home/winnt/%D/%U
    template shell = /bin/bash

    Join the Samba Server to the PDC Domain

    + + + All machines that will participate in domain security should be members of the domain. This applies also to the PDC and all BDCs.

    - - - - - - - - - + + + + + + + + + The process of joining a domain requires the use of the net rpc join command. This process communicates with the domain controller it will register with (usually the PDC) via MS DCE RPC. This means, of course, that the smbd process must be running on the target domain controller. It is therefore necessary to temporarily start Samba on a PDC so that it can join its own domain.

    - - - + + + Enter the following command to make the Samba server join the domain, where PDC is the name of your PDC and Administrator is a domain user who has administrative privileges in the domain.

    Note

    - - - - + + + + Before attempting to join a machine to the domain, verify that Samba is running on the target domain controller (usually PDC) and that it is capable of being reached via ports 137/udp, 135/tcp, 139/tcp, and 445/tcp (if Samba or Windows Server 2Kx).

    - + The use of the net rpc join facility is shown here: 

     root# /usr/local/samba/bin/net rpc join -S PDC -U Administrator
@@ -555,10 +555,10 @@ The use of the net rpc join facility is shown here:
 The proper response to the command should be “Joined the domain
 DOMAIN” where DOMAIN
 is your domain name.
-

    Starting and Testing the winbindd Daemon

    - - - +

    Starting and Testing the winbindd Daemon

    + + + Eventually, you will want to modify your Samba startup script to automatically invoke the winbindd daemon when the other parts of Samba start, but it is possible to test out just the Winbind portion first. To start up Winbind services, enter the following command as root: @@ -567,27 +567,27 @@ Winbind services, enter the following command as root:

    Use the appropriate path to the location of the winbindd executable file.

    Note

    - - + + The command to start up Winbind services assumes that Samba has been installed in the /usr/local/samba directory tree. You may need to search for the location of Samba files if this is not the location of winbindd on your system.

    - - + + I'm always paranoid and like to make sure the daemon is really running. 

     root# ps -ae | grep winbindd

    - + This command should produce output like the following if the daemon is running. 

     3025 ?        00:00:00 winbindd

    - - + + Now, for the real test, try to get some information about the users on your PDC: 

     root# /usr/local/samba/bin/wbinfo -u
@@ -605,8 +605,8 @@ CEO\TsInternetUser
 Obviously, I have named my domain “CEO” and my winbind separator is
 “\”.
 
    
-
-
+
+
 You can do the same sort of thing to get group information from the PDC:
 
     root# /usr/local/samba/bin/wbinfo -g
@@ -620,13 +620,13 @@ CEO\Schema Admins
 CEO\Enterprise Admins
 CEO\Group Policy Creator Owners
 
    
-
-
-
-
-
-
-
+
+
+
+
+
+
+
 The function getent can now be used to get unified lists of both local and PDC users and
 groups. Try the following command:
 
    @@ -640,16 +640,16 @@ The same thing can be done for groups with the command:
 
     root# getent group
 
    
-

    Fix the init.d Startup Scripts

    Linux

    - - - - - - - - - +

    Fix the init.d Startup Scripts

    Linux

    + + + + + + + + + The winbindd daemon needs to start up after the smbd and nmbd daemons are running. To accomplish this task, you need to modify the startup scripts of your system. They are located at /etc/init.d/smb in Red Hat Linux and in /etc/init.d/samba in Debian @@ -710,16 +710,16 @@ stop() { echo "" return $RETVAL } -

    Solaris

    +

    Solaris

    Winbind does not work on Solaris 9; see Winbind on Solaris 9 section for details.

    - - - - - - + + + + + + On Solaris, you need to modify the /etc/init.d/samba.server startup script. It usually only starts smbd and nmbd but should now start winbindd, too. If you have Samba installed in /usr/local/samba/bin, the file could contains something like this: @@ -780,28 +780,28 @@ in the script above with: 

     /usr/local/samba/sbin/winbindd -B

    -

    Restarting

    - - +

    Restarting

    + + If you restart the smbd, nmbd, and winbindd daemons at this point, you should be able to connect to the Samba server as a domain member just as if you were a local user. -

    Configure Winbind and PAM

    - - - - +

    Configure Winbind and PAM

    + + + + If you have made it this far, you know that winbindd and Samba are working together. If you want to use Winbind to provide authentication for other services, keep reading. The PAM configuration files need to be altered in this step. (Did you remember to make backups of your original /etc/pam.d files? If not, do it now.)

    - - - - - - + + + + + + You will need a PAM module to use winbindd with these other services. This module will be compiled in the ../source/nsswitch directory by invoking the command: 

    @@ -814,22 +814,22 @@ copied to the location of your other PAM security modules. On my Red Hat system,
 
     root# cp ../samba/source/nsswitch/pam_winbind.so /lib/security
 
    
-
    Linux/FreeBSD-Specific PAM Configuration
    
-
+
    Linux/FreeBSD-Specific PAM Configuration
    
+
 The /etc/pam.d/samba file does not need to be changed. I just left this file as it was:
 
     auth    required  /lib/security/pam_stack.so service=system-auth
 account required  /lib/security/pam_stack.so service=system-auth
 
    
-
-
-
-
-
-
-
-
-
+
+
+
+
+
+
+
+
+
 The other services that I modified to allow the use of Winbind as an authentication service were the normal
 login on the console (or a terminal session), telnet logins, and ftp service. In order to enable these
 services, you may first need to change the entries in /etc/xinetd.d (or
@@ -843,20 +843,20 @@ to
 
     	enable = yes
 
    
-
-
-
+
+
+
 For ftp services to work properly, you will also need to either have individual directories for the domain
 users already present on the server or change the home directory template to a general directory for all
 domain users. These can be easily set using the smb.conf global entry template homedir.
 
    Note
    
-
+
 The directory in template homedir is not created automatically! Use pam_mkhomedir or
 pre-create the directories of users to make sure users can log in on UNIX with their own home directory.
 
    
-
-
-
+
+
+
 The /etc/pam.d/ftp file can be changed to allow Winbind ftp access in a manner similar to
 the samba file. My /etc/pam.d/ftp file was changed to look like this:
 
    @@ -869,7 +869,7 @@ account    sufficient   /lib/security/pam_winbind.so
 account    required     /lib/security/pam_stack.so service=system-auth
 session    required     /lib/security/pam_stack.so service=system-auth
 
    
-
+
 The /etc/pam.d/login file can be changed in nearly the same way. It now looks like this:
 
     auth       required     /lib/security/pam_securetty.so
@@ -883,17 +883,17 @@ password   required     /lib/security/pam_stack.so service=system-auth
 session    required     /lib/security/pam_stack.so service=system-auth
 session    optional     /lib/security/pam_console.so
 
    
-
-
-
+
+
+
 In this case, I added the 
    auth sufficient /lib/security/pam_winbind.so
     lines
 as before, but also added the 
    required pam_securetty.so
     above it to disallow
 root logins over the network. I also added a 
    sufficient /lib/security/pam_unix.so
 use_first_pass
     line after the winbind.so line to get rid of annoying
 double prompts for passwords.
-
    Solaris-Specific Configuration
    
-
-
+
    Solaris-Specific Configuration
    
+
+
 The /etc/pam.conf needs to be changed. I changed this file so my Domain
 users can log on both locally as well as with telnet. The following are the changes
 that I made. You can customize the pam.conf file as per your requirements, but
@@ -960,22 +960,22 @@ dtsession auth required /usr/lib/security/$ISA/pam_unix.so.1
 #other session optional /usr/lib/security/$ISA/pam_krb5.so.1
 #other password optional /usr/lib/security/$ISA/pam_krb5.so.1 try_first_pass

    - + I also added a try_first_pass line after the winbind.so line to get rid of annoying double prompts for passwords.

    Now restart your Samba and try connecting through your application that you configured in the pam.conf. -

    Conclusion

    - - - - - +

    Conclusion

    + + + + + The Winbind system, through the use of the NSS, PAMs, and appropriate Microsoft RPC calls, have allowed us to provide seamless integration of Microsoft Windows NT domain users on a UNIX system. The result is a great reduction in the administrative cost of running a mixed UNIX and NT network. -

    Common Errors

    +

    Common Errors

    Winbind has a number of limitations in its current released version that we hope to overcome in future releases:

    • Winbind is currently only available for the Linux, Solaris, AIX, and IRIX operating systems, although @@ -989,14 +989,14 @@ reduction in the administrative cost of running a mixed UNIX and NT network.

    • Currently the Winbind PAM module does not take into account possible workstation and logon time restrictions that may be set for Windows NT users; this is instead up to the PDC to enforce. -

    NSCD Problem Warning

    Warning

    +

    NSCD Problem Warning

    Warning

    Do not under any circumstances run nscd on any system on which winbindd is running.

    If nscd is running on the UNIX/Linux system, then even though NSSWITCH is correctly configured, it will not be possible to resolve domain users and groups for file and directory controls. -

    Winbind Is Not Resolving Users and Groups

    “ +

    Winbind Is Not Resolving Users and Groups

    “ My smb.conf file is correctly configured. I have specified idmap uid = 12000, and idmap gid = 3000-3500 and winbind is running. When I do the following, it all works fine. -- cgit v1.2.3