From 99bde6889d3d8b7a9e950c86c30e82662e1dacdd Mon Sep 17 00:00:00 2001 From: Gerald Carter Date: Tue, 9 Sep 2003 02:58:53 +0000 Subject: syncing files from 3.0 into HEAD again (This used to be commit bca0bba209255d0effbae6a3d3b6d298f0952c3a) --- docs/htmldocs/AccessControls.html | 531 +- docs/htmldocs/AdvancedNetworkManagement.html | 18 +- docs/htmldocs/Appendixes.html | 7 +- docs/htmldocs/Backup.html | 8 +- docs/htmldocs/CUPS-printing.html | 1984 ++---- docs/htmldocs/ClientConfig.html | 4 +- docs/htmldocs/DNSDHCP.html | 4 +- docs/htmldocs/FastStart.html | 4 +- docs/htmldocs/Further-Resources.html | 6 +- docs/htmldocs/InterdomainTrusts.html | 184 +- docs/htmldocs/IntroSMB.html | 16 +- docs/htmldocs/NT4Migration.html | 236 +- docs/htmldocs/NetworkBrowsing.html | 348 +- docs/htmldocs/Other-Clients.html | 72 +- docs/htmldocs/PolicyMgmt.html | 59 +- docs/htmldocs/Portability.html | 22 +- docs/htmldocs/ProfileMgmt.html | 246 +- docs/htmldocs/SWAT.html | 45 +- docs/htmldocs/Samba-Developers-Guide.html | 455 +- docs/htmldocs/Samba-HOWTO-Collection.html | 9373 ++++++++++++-------------- docs/htmldocs/SambaHA.html | 4 +- docs/htmldocs/ServerType.html | 187 +- docs/htmldocs/StandAloneServer.html | 69 +- docs/htmldocs/VFS.html | 73 +- docs/htmldocs/bugreport.html | 38 +- docs/htmldocs/compiling.html | 87 +- docs/htmldocs/diagnosis.html | 73 +- docs/htmldocs/domain-member.html | 254 +- docs/htmldocs/groupmapping.html | 134 +- docs/htmldocs/install.html | 124 +- docs/htmldocs/integrate-ms-networks.html | 356 +- docs/htmldocs/introduction.html | 7 +- docs/htmldocs/ix01.html | 40 +- docs/htmldocs/lmhosts.5.html | 8 +- docs/htmldocs/locking.html | 143 +- docs/htmldocs/log2pcap.1.html | 29 + docs/htmldocs/migration.html | 2 +- docs/htmldocs/mount.cifs.8.html | 103 + docs/htmldocs/msdfs.html | 51 +- docs/htmldocs/net.8.html | 29 +- docs/htmldocs/nmbd.8.html | 32 +- docs/htmldocs/nmblookup.1.html | 22 +- docs/htmldocs/ntlm_auth.1.html | 10 +- docs/htmldocs/optional.html | 59 +- docs/htmldocs/pam.html | 179 +- docs/htmldocs/passdb.html | 465 +- docs/htmldocs/pdbedit.8.html | 30 +- docs/htmldocs/pr01.html | 5 + docs/htmldocs/pr02.html | 1 + docs/htmldocs/printing.html | 766 +-- docs/htmldocs/problems.html | 51 +- docs/htmldocs/rpcclient.1.html | 33 +- docs/htmldocs/samba-bdc.html | 105 +- docs/htmldocs/samba-doc.html | 72 + docs/htmldocs/samba-pdc.html | 382 +- docs/htmldocs/samba.7.html | 4 +- docs/htmldocs/samba.css | 80 + docs/htmldocs/securing-samba.html | 82 +- docs/htmldocs/smb.conf.5.html | 497 +- docs/htmldocs/smbcacls.1.html | 14 +- docs/htmldocs/smbclient.1.html | 23 +- docs/htmldocs/smbcontrol.1.html | 7 +- docs/htmldocs/smbcquotas.1.html | 8 +- docs/htmldocs/smbd.8.html | 23 +- docs/htmldocs/smbmount.8.html | 8 +- docs/htmldocs/smbpasswd.5.html | 15 +- docs/htmldocs/smbpasswd.8.html | 19 +- docs/htmldocs/smbsh.1.html | 24 +- docs/htmldocs/smbspool.8.html | 2 +- docs/htmldocs/smbstatus.1.html | 8 +- docs/htmldocs/smbtar.1.html | 2 +- docs/htmldocs/smbtree.1.html | 12 +- docs/htmldocs/speed.html | 52 +- docs/htmldocs/swat.8.html | 12 +- docs/htmldocs/testprns.1.html | 10 +- docs/htmldocs/troubleshooting.html | 2 +- docs/htmldocs/type.html | 8 +- docs/htmldocs/unicode.html | 55 +- docs/htmldocs/upgrading-to-3.0.html | 195 +- docs/htmldocs/vfstest.1.html | 10 +- docs/htmldocs/wbinfo.1.html | 89 +- docs/htmldocs/winbind.html | 163 +- docs/htmldocs/winbindd.8.html | 49 +- 83 files changed, 9083 insertions(+), 10035 deletions(-) create mode 100644 docs/htmldocs/log2pcap.1.html create mode 100644 docs/htmldocs/mount.cifs.8.html create mode 100644 docs/htmldocs/pr01.html create mode 100644 docs/htmldocs/pr02.html create mode 100644 docs/htmldocs/samba-doc.html create mode 100644 docs/htmldocs/samba.css (limited to 'docs/htmldocs') diff --git a/docs/htmldocs/AccessControls.html b/docs/htmldocs/AccessControls.html index 044d347107..7330836f36 100644 --- a/docs/htmldocs/AccessControls.html +++ b/docs/htmldocs/AccessControls.html @@ -1,23 +1,20 @@ -Chapter 13. File, Directory and Share Access Controls
Chapter 13. File, Directory and Share Access Controls
Prev Part III. Advanced Configuration Next

Chapter 13. File, Directory and Share Access Controls

John H. Terpstra

Samba Team

Jeremy Allison

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
Common Errors
Users can not write to a public share
I have set force user and Samba still makes root the owner of all the files - I touch!

+Chapter 13. File, Directory and Share Access Controls

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

Chapter 13. 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
Common Errors
Users can not write to a public share
I have set force user but Samba still makes root the owner of all the files I touch!
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 what is the best way to -provide users with the type of access they need while protecting resources from the consequences -of untoward access capabilities. +administrators are often confused regarding network access controls and how to +provide users with the access they need while protecting resources from unauthorised access.

-Unix administrators frequently are not familiar with the MS Windows environment and in particular +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 can not completely hide, even -though it does try to make the chasm transparent. -

+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 +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. @@ -26,25 +23,24 @@ The purpose of this chapter is to present each of the points of control that are 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 it should be borne in mind that Samba was created to -provide a means of interoperability and interchange of data between two operating environments -that are quite different. It was never the intent to make Unix/Linux like MS Windows NT. Instead -the purpose was an 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

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

Samba offers a lot of 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 + UNIX File and Directory Permissions

    - Samba honours and implements Unix file system access controls. Users + Samba honours 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 connection setup process. Samba uses this user identity to validate whether or not the user should be given access to file system resources (files and directories). This chapter provides an overview for those - to whom the Unix permissions and controls are a little strange or unknown. + to whom the UNIX permissions and controls are a little strange or unknown.

  • Samba Share Definitions

    @@ -63,22 +59,22 @@ shrink. 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 + MS Windows ACLs through UNIX POSIX ACLs

    - The use of POSIX ACLs on Unix/Linux is possible ONLY if the underlying + 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 + available to you. Current UNIX technology platforms have native support for POSIX ACLs. There are patches for the Linux kernel that provide this also. 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 +implement a totally divergent file system technology from what is provided in the UNIX operating system environment. Firstly we should consider what the most significant differences are, then we shall look at how Samba helps to bridge the differences. -

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 +

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 behaviour that differs from unix file system behaviour then somehow Samba is responsible for emulating that in a transparent and consistent manner. @@ -88,128 +84,108 @@ at how Samba helps to bridge the differences. but for the greater part we will stay within the bounds of default behaviour. Those wishing to explore to depths of control ability should review the smb.conf man page.

File System Feature Comparison

Name Space

- MS Windows NT4 / 200x/ XP files names may be up to 254 characters long, Unix file names + MS Windows NT4 / 200x/ XP files names may be up to 254 characters long, UNIX file names may be 1023 characters long. In MS Windows file extensions indicate particular file types, - in Unix this is not so rigorously observed as all names are considered arbitrary. + in UNIX this is not so rigorously observed as all names are considered arbitrary.

- What MS Windows calls a Folder, Unix calls a directory, + What MS Windows calls a Folder, UNIX calls a directory.

Case Sensitivity

- MS Windows file names are generally Upper Case if made up of 8.3 (ie: 8 character file name + + MS Windows file names are generally upper case if made up of 8.3 (ie: 8 character file name and 3 character extension. If longer than 8.3 file names are Case Preserving, and Case Insensitive.

- Unix file and directory names are Case Sensitive and Case Preserving. Samba implements the - MS Windows file name behaviour, but it does so as a user application. The Unix file system + UNIX file and directory names are case sensitive and case preserving. Samba implements the + MS Windows file name behaviour, but it does so as a user application. The UNIX file system provides no mechanism to perform case insensitive file name lookups. MS Windows does this by default. This means that Samba has to carry the processing overhead to provide features - that are NOT native to the Unix operating system environment. + that are NOT native to the UNIX operating system environment.

- Consider the following, all are unique Unix names but one single MS Windows file name: + Consider the following, all are unique UNIX names but one single MS Windows file name: MYFILE.TXT MyFile.txt myfile.txt - So clearly, In an MS Windows file name space these three files CAN NOT co-exist! But in Unix + So clearly, In an MS Windows file name space these three files CAN NOT co-exist! But in UNIX they can. So what should Samba do if all three are present? Answer, the one that is lexically first will be accessible to MS Windows users, the others are invisible and unaccessible - any other solution would be suicidal.

Directory Separators

- MS Windows and DOS uses the back-slash '\' as a directory delimiter, Unix uses the forward-slash '/' + MS Windows and DOS uses the back-slash '\' as a directory delimiter, UNIX uses the forward-slash '/' as it's directory delimiter. This is transparently handled by Samba.

Drive Identification

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

File Naming Conventions

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

Links and Short-Cuts

+ + + + MS Windows make use of "links and Short-Cuts" 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 + 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.

- Symbolic links are files in Unix that contain the actual location of the data (file OR directory). An + Symbolic links are files in UNIX that contain the actual location of the data (file OR directory). An operation (like read or write) will operate directly on the file referenced. Symbolic links are also referred to as 'soft links'. A hard link is something that MS Windows is NOT familiar with. It allows one physical file to be known simultaneously by more than one file name.

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

Managing Directories

+ 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/education. +

Managing Directories

There are three basic operations for managing directories, create, delete, rename. -

Table 13.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 13.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 foundational training manuals and reference materials - regarding file and directory permissions maintenance. Much can be achieved with the basic Unix permissions + 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 Access Control Lists (ACLs) or Extended Attributes (EAs).

- Unix/Linux file and directory access permissions involves setting three (3) primary sets of data and one (1) control set. - A Unix file listing looks as follows:- + UNIX/Linux file and directory access permissions involves setting three (3) primary sets of data and one (1) control set. + A UNIX file listing looks as follows:- - 

-	jht@frodo:~/stuff> ls -la
-	total 632
-	drwxr-xr-x   13 jht   users      816 2003-05-12 22:56 .
-	drwxr-xr-x   37 jht   users     3800 2003-05-12 22:29 ..
-	d---------    2 jht   users       48 2003-05-12 22:29 muchado00
-	d--x--x--x    2 jht   users       48 2003-05-12 22:29 muchado01
-	dr-xr-xr-x    2 jht   users       48 2003-05-12 22:29 muchado02
-	drwxrwxrwx    2 jht   users       48 2003-05-12 22:29 muchado03
-	drw-rw-rw-    2 jht   users       48 2003-05-12 22:29 muchado04
-	d-w--w--w-    2 jht   users       48 2003-05-12 22:29 muchado05
-	dr--r--r--    2 jht   users       48 2003-05-12 22:29 muchado06
-	drwxrwxrwt    2 jht   users       48 2003-05-12 22:29 muchado07
-	drwsrwsrwx    2 jht   users       48 2003-05-12 22:29 muchado08
-	----------    1 jht   users     1242 2003-05-12 22:31 mydata00.lst
-	---x--x--x    1 jht   users     1674 2003-05-12 22:33 mydata01.lst
-	--w--w--w-    1 jht   users     7754 2003-05-12 22:33 mydata02.lst
-	--wx-wx-wx    1 jht   users   260179 2003-05-12 22:33 mydata03.lst
-	-r--r--r--    1 jht   users    21017 2003-05-12 22:32 mydata04.lst
-	-r-xr-xr-x    1 jht   users   206339 2003-05-12 22:32 mydata05.lst
-	-rw-rw-rw-    1 jht   users    41105 2003-05-12 22:32 mydata06.lst
-	-rwxrwxrwx    1 jht   users    19312 2003-05-12 22:32 mydata07.lst
-	jht@frodo:~/stuff>
-

+

+$ ls -la
+total 632
+drwxr-xr-x   13 maryo   gnomes      816 2003-05-12 22:56 .
+drwxrwxr-x   37 maryo   gnomes     3800 2003-05-12 22:29 ..
+dr-xr-xr-x    2 maryo   gnomes       48 2003-05-12 22:29 muchado02
+drwxrwxrwx    2 maryo   gnomes       48 2003-05-12 22:29 muchado03
+drw-rw-rw-    2 maryo   gnomes       48 2003-05-12 22:29 muchado04
+d-w--w--w-    2 maryo   gnomes       48 2003-05-12 22:29 muchado05
+dr--r--r--    2 maryo   gnomes       48 2003-05-12 22:29 muchado06
+drwsrwsrwx    2 maryo   gnomes       48 2003-05-12 22:29 muchado08
+----------    1 maryo   gnomes     1242 2003-05-12 22:31 mydata00.lst
+--w--w--w-    1 maryo   gnomes     7754 2003-05-12 22:33 mydata02.lst
+-r--r--r--    1 maryo   gnomes    21017 2003-05-12 22:32 mydata04.lst
+-rw-rw-rw-    1 maryo   gnomes    41105 2003-05-12 22:32 mydata06.lst
+$ 
+

- The columns above represent (from left to right): permissions, no blocks used, owner, group, size (bytes), access date, access time, file name. -

- The permissions field is made up of: - - 

-	 JRV: Put this into a diagram of some sort
-	[ type  ] [ users ] [ group ] [ others ]   [File, Directory Permissions]
-	[ d | l ] [ r w x ] [ r w x ] [ r w x  ]
-	  |   |     | | |     | | |     | | |
-	  |   |     | | |     | | |     | | |-----> Can Execute, List files
-	  |   |     | | |     | | |     | |-------> Can Write,   Create files
-	  |   |     | | |     | | |     |---------> Can Read,    Read files
-	  |   |     | | |     | | |---------------> Can Execute, List files
-	  |   |     | | |     | |-----------------> Can Write,   Create files
-	  |   |     | | |     |-------------------> Can Read,    Read files
-	  |   |     | | |-------------------------> Can Execute, List files
-	  |   |     | |---------------------------> Can Write,   Create files
-	  |   |     |-----------------------------> Can Read,    Read files
-	  |   |-----------------------------------> Is a symbolic Link
-	  |---------------------------------------> Is a directory
-

+ The columns above represent (from left to right): permissions, number of hard links to file, owner, group, size (bytes), access date, access time, file name.

+ An overview of the permissions field can be found in the image below. +

Figure 13.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 'Can NOT' and is represented as a '-' character. -

Example 13.1. Example File

+	
Example 13.1. Example File
 		-rwxr-x---   Means: The owner (user) can read, write, execute
 		                    the group can read and execute
 		                    everyone else can NOT do anything with it
 		

 
 	

-	Additional possibilities in the [type] field are: c = character device, b = block device, p = pipe device, s = Unix Domain Socket.
+	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 or group ID on execution (s),
@@ -228,101 +204,101 @@ at how Samba helps to bridge the differences.
 	the (x) execute flags are not set files can not be listed (seen) in the directory by anyone. The group can read files in the
 	directory but can NOT create new files. NOTE: 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.
-

Share Definition Access Controls

+

Share Definition Access Controls

The following parameters in the smb.conf file sections that 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 very useful. In some situations it is distinctly desirable to affect all - file system operations as if a single user is doing this, the use of the force user and - force group behaviour will achieve this. In other situations it may be necessary to affect a + file system operations as if a single user is doing this, the use of the force user and + force group behaviour will achieve this. In other situations it may be necessary to affect a paranoia level of control to ensure that only particular authorised persons will be able to access a share or - it's contents, here the use of the valid users or the invalid users may + it's contents, here the use of the valid users or the invalid users may be most useful.

As always, it is highly advisable to use the least difficult to maintain and the least ambiguous method for controlling access. Remember, that when you leave the scene someone else will need to provide assistance and if that person finds too great a mess, or if they do not understand what you have done then there is risk of Samba being removed and an alternative solution being adopted. -

Table 13.2. User and Group Based Controls

Control ParameterDescription - Action - Notes
admin users

+

Table 13.2. User and Group Based Controls

Control ParameterDescription - Action - Notes
admin users

List of users who will be granted administrative privileges on the share. They will do all file operations as the super-user (root). Any user in this list will be able to do anything they like on the share, irrespective of file permissions. -

force group

+

force group

Specifies a UNIX group name that will be assigned as the default primary group for all users connecting to this service. -

force user

+

force user

Specifies a UNIX user name that will be assigned as the default user for all users connecting to this service. This is useful for sharing files. Incorrect use can cause security problems. -

guest ok

+

guest ok

If this parameter is set for a service, then no password is required to connect to the service. Privileges will be those of the guest account. -

invalid users

+

invalid users

List of users that should not be allowed to login to this service. -

only user

+

only user

Controls whether connections with usernames not in the user list will be allowed. -

read list

+

read list

List of users that are given read-only access to a service. Users in this list will not be given write access, no matter what the read only option is set to. -

username

+

username

Refer to the smb.conf man page for more information - this is a complex and potentially misused parameter. -

valid users

+

valid users

List of users that should be allowed to login to this service. -

write list

+

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

The following file and directory permission based controls, if misused, can result in considerable difficulty to diagnose the cause of mis-configuration. Use them sparingly and carefully. By gradually introducing each one by one undesirable side-effects may be detected. In the event of a problem, always comment all of them out and then gradually re-introduce them in a controlled fashion. -

Table 13.3. File and Directory Permission Based Controls

Control ParameterDescription - Action - Notes
create mask

+

Table 13.3. File and Directory Permission Based Controls

Control ParameterDescription - Action - Notes
create mask

Refer to the smb.conf man page. -

directory mask

+

directory mask

The octal modes used when converting DOS modes to UNIX modes when creating UNIX directories. See also: directory security mask. -

dos filemode

+

dos filemode

Enabling this parameter allows a user who has write access to the file to modify the permissions on it. -

force create mode

+

force create mode

This parameter specifies a set of UNIX mode bit permissions that will always be set on a file created by Samba. -

force directory mode

+

force directory mode

This parameter specifies a set of UNIX mode bit permissions that will always be set on a directory created by Samba. -

force directory security mode

+

force directory security mode

Controls UNIX permission bits modified when a Windows NT client is manipulating UNIX permissions on a directory -

force security mode

+

force security mode

Controls UNIX permission bits modified when a Windows NT client manipulates UNIX permissions. -

hide unreadable

+

hide unreadable

Prevents clients from seeing the existence of files that cannot be read. -

hide unwriteable files

+

hide unwriteable files

Prevents clients from seeing the existence of files that cannot be written to. Unwriteable directories are shown as usual. -

nt acl support

+

nt acl support

This parameter controls whether smbd will attempt to map UNIX permissions into Windows NT access control lists. -

security mask

+

security mask

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

Miscellaneous Controls

- The following are documented because of the prevalence of administrators creating inadvertant barriers to file +

Miscellaneous Controls

+ The following are documented because of the prevalence of administrators creating inadvertent barriers to file access by not understanding the full implications of smb.conf file settings. -

Table 13.4. Other Controls

Control ParameterDescription - Action - Notes
case sensitive, default case, short preserve case

+

Table 13.4. Other Controls

Control ParameterDescription - Action - Notes
case sensitive, default case, short preserve case

This means that all file name lookup will be done in a case sensitive manner. Files will be created with the precise filename Samba received from the MS Windows client. -

csc policy

+

csc policy

Client Side Caching Policy - parallels MS Windows client side file caching capabilities. -

dont descend

+

dont descend

Allows to specify a comma-delimited list of directories that the server should always show as empty. -

dos filetime resolution

+

dos filetime resolution

This option is mainly used as a compatibility option for Visual C++ when used against Samba shares. -

dos filetimes

+

dos filetimes

DOS and Windows allows users to change file time stamps if they can write to the file. POSIX semantics prevent this. This options allows DOS and Windows behaviour. -

fake oplocks

+

fake oplocks

Oplocks are the way that SMB clients get permission from a server to locally cache file operations. If a server grants an oplock then the client is free to assume that it is the only one accessing the file and it will aggressively cache file data. -

hide dot files, hide files, veto files

+

hide dot files, hide files, veto files

Note: MS Windows Explorer allows over-ride of files marked as hidden so they will still be visible. -

read only

+

read only

If this parameter is yes, then users of a service may not create or modify files in the service's directory. -

veto files

+

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 a very effective way to limit who can @@ -339,9 +315,9 @@ Before using any of the following options please refer to the man page for /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: tdbdump share_info.tdb. -

Share Permissions Management

+

Share Permissions Management

The best tool for the task is platform dependant. Choose the best tool for your environment. -

Windows NT4 Workstation/Server

+

Windows NT4 Workstation/Server

The tool you need to use to manage share permissions on a Samba 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 Microsoft - see details below. @@ -351,9 +327,9 @@ Before using any of the following options please refer to the man page for

  • Now click on the share that you wish to manage, then click on the Properties tab, next click on 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 access control lists on the share itself are set using native - tools, usually from filemanager. For example, in Windows 200x: right click on the shared folder, + 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.

    @@ -380,71 +356,70 @@ Before using any of the following options please refer to the man page for no access means that MaryK who is part of the group Everyone will have no access even if this user is given explicit full control access. -

    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.

    Note that this ability is careful not to compromise - the security of the UNIX host Samba is running on, and - still obeys all the file permission rules that a Samba - administrator can set.

    Note

    - All access to Unix/Linux system file via Samba is controlled at - the operating system file access control level. When trying to - figure out file access problems it is vitally important to identify - 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 +

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

    + Note that this ability is careful not to compromise the security of the UNIX host Samba is running on, and + still obeys all the file permission rules that a Samba administrator can set. +

    + Samba does not attempt to go beyond POSIX ACLs, so that the various finer-grained access control + options provided in Windows are actually ignore. +

    Note

    + All access to UNIX/Linux system files via Samba is controlled by the operating system file access controls. + 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

    From an NT4/2000/XP client, single-click with the right - mouse button 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 tab Security and you - will see three buttons, Permissions, - Auditing, and Ownership. - The Auditing button will cause either - an error message A requested privilege is not held - by the client to appear if the user is not the - NT Administrator, or a dialog which is intended to allow an - Administrator to add auditing requirements to a file if the - user is logged on as the NT Administrator. This dialog is - non-functional with a Samba share at this time, as the only - useful button, the Add button will not currently - allow a list of users to be seen.

    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 of the form :

    "SERVER\user (Long name)"

    Where SERVER is the NetBIOS name of - the Samba server, user is the user name of - the UNIX user who owns the file, and (Long name) - is the descriptive string identifying the user (normally found in the - GECOS field of the UNIX password database). Click on the - Close button to remove this dialog.

    If the parameter nt acl support - is set to false then 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 on - it will display a dialog box complaining that the user 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 - operation in UNIX, available only to the root - user. As clicking on this button causes 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 filesystem 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, available from the main Samba ftp site.

    Viewing File or Directory Permissions

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

    "SERVER\ +

    Viewing File Security on a Samba Share

    + From an NT4/2000/XP client, single-click with the right mouse button 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 tab + Security and you will see three buttons, Permissions, + Auditing, and Ownership. The Auditing + button will cause either an error message A requested privilege is not held by the client + to appear if the user is not the NT Administrator, or a dialog which is intended to allow an Administrator + to add auditing requirements to a file if the user is logged on as the NT Administrator. This dialog is + non-functional with a Samba share at this time, as the only useful button, the Add + button will not currently allow a list of users to be seen. +

    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 of the form: +

    + "SERVER\user (Long name)" +

    + Where SERVER is the NetBIOS name of the Samba server, user + is the user name of the UNIX user who owns the file, and (Long name) is the + descriptive string identifying the user (normally found in the GECOS field of the UNIX password database). + Click on the Close button to remove this dialog. +

    + If the parameter nt acl support is set to false + then 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 on it will display a dialog box complaining that the user 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 + operation in UNIX, available only to the root user. As clicking on this button causes + 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 filesystem 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, available from the main Samba FTP site.

    Viewing File or Directory Permissions

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

    "SERVER\ user - (Long name)"

    Where SERVER is the NetBIOS name of - the Samba server, user is the user name of - the UNIX user who owns the file, and (Long name) - is the descriptive string identifying the user (normally found in the - GECOS field of the UNIX password database).

    If the parameter nt acl support - is set to false then the file owner will - be shown as the NT user "Everyone" and the - permissions will be shown as NT "Full Control".

    The permissions field is displayed differently for files - and directories, so I'll describe the way file permissions - are displayed first.

    File Permissions

    The standard UNIX user/group/world triplet and + (Long name)"

    Where SERVER is the NetBIOS name of the Samba server, + user is the user name of the UNIX user who owns the file, and + (Long name) is the descriptive string identifying the user (normally found in the + GECOS field of the UNIX password database).

    + If the parameter nt acl support is set to false + then the file owner will be shown as the NT user "Everyone" and the permissions will be + shown as NT "Full Control". +

    + The permissions field is displayed differently for files and directories, so I'll describe the way file permissions + are displayed first. +

    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 @@ -459,14 +434,14 @@ Before using any of the following options please refer to the man page for or full control then usually the permissions will be prefixed by the words "Special Access" in the NT display list.

    But what happens if the file has no permissions allowed - for a particular UNIX user group or world component ? In order + for a particular UNIX user group or world component? In order to allow "no permissions" to be seen and modified then Samba overloads the NT "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 will - be given below.

    Directory Permissions

    Directories on an NT NTFS file system have two + be given below.

    Directory Permissions

    Directories on an NT NTFS file system have two different sets of permissions. The first set of permissions is the ACL set on the directory itself, this is usually displayed in the first set of parentheses in the normal "RW" @@ -477,12 +452,12 @@ Before using any of the following options please refer to the man page for permissions that any file created within this directory would inherit.

    Samba synthesises 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 and directory permissions is as simple + created by Samba on this share would receive.

    Modifying file or directory permissions

    Modifying file and directory permissions is as simple as changing the displayed permissions in the dialog box, and clicking the OK button. 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 need to also be taken into account.

    If the parameter nt acl support + attributes that need to also be taken into account.

    If the parameter nt acl support is set to false then any attempt to set security permissions will fail with an "Access Denied" message.

    The first thing to note is that the "Add" @@ -511,59 +486,56 @@ Before using any of the following options please refer to the man page for 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 + ) highlighted.

    Interaction with the standard Samba create mask parameters

    There are four parameters to control interaction with the standard Samba create mask parameters. These are : -

    security mask
    force security mode
    directory security mask
    force directory security mode

    +

    • security mask

    • force security mode

    • directory security mask

    • force directory security mode

    Once a user clicks OK to apply the permissions Samba maps the given permissions into a user/group/world r/w/x triplet set, and then will check the changed permissions for a - file against the bits set in the - security mask parameter. Any bits that + file against the bits set in the + security mask parameter. Any bits that were changed that are not set to '1' in this parameter are left alone - in the file permissions.

    Essentially, zero bits in the security mask + in the file permissions.

    Essentially, zero bits in the security mask mask may be treated as a set of bits the user is not allowed to change, and one bits are those the user is allowed to change.

    If not set explicitly this parameter is set to the same value as - the create mask - parameter. To allow a user to modify all the + the create mask parameter. To allow a user to modify all the user/group/world permissions on a file, set this parameter to 0777.

    Next Samba checks the changed permissions for a file against - the bits set in the - force security mode parameter. Any bits + the bits set in the + force security mode parameter. Any bits that were changed that correspond to bits set to '1' in this parameter are forced to be set.

    Essentially, bits set in the force security mode parameter may be treated as a set of bits that, when modifying security on a file, the user has always set to be 'on'.

    If not set explicitly this parameter is set to the same value - as the force - create mode parameter. + as the force create mode parameter. To allow a user to modify all the user/group/world permissions on a file - with no restrictions set this parameter to 000.

    The security mask and force + with no restrictions set this parameter to 000.

    The security mask and force security mode parameters are applied to the change request in that order.

    For a directory Samba will perform the same operations as described above for a file except using the parameter directory security mask instead of security mask, and force directory security mode parameter instead of force security mode - .

    The directory security mask parameter + .

    The directory security mask parameter by default is set to the same value as the directory mask parameter and the force directory security mode parameter by default is set to the same value as - the force directory mode parameter.

    In this way Samba enforces the permission restrictions that + the force directory mode parameter.

    In this way Samba enforces the permission restrictions that an administrator can set on a Samba share, whilst still allowing users to modify the permission bits within that restriction.

    If you want to set up a share that allows users full control in modifying the permission bits on their files and directories and doesn't 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

    Samba maps some of the DOS attribute bits (such as "read +

    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 dialog and the permission bits set by the file attribute mapping. -

    One way this can show up is if a file has no UNIX read access +

    One way this can show up is if a file has no UNIX read access for the owner it will show up as "read only" in the standard file attributes tabbed dialog. Unfortunately this dialog is the same one that contains the security info in another tab.

    What this can mean is that if the owner changes the permissions @@ -575,10 +547,10 @@ Before using any of the following options please refer to the man page for OK to get back to the attributes dialog you should always hit Cancel rather than OK to ensure that your changes - are not overridden.

    Common Errors

    + are not overridden.

    Common Errors

    File, Directory and Share access problems are very common on the mailing list. The following are examples taken from the mailing list in recent times. -

    Users can not write to a public share

    +

    Users can not write to a public share

    “ We are facing some troubles with file / directory permissions. I can log on the domain as admin user(root), and there's a public share, on which everyone needs to have permission to create / modify files, but only @@ -587,74 +559,83 @@ are examples taken from the mailing list in recent times. ”

    There are many ways to solve this problem, here are a few hints: -

    Procedure 13.3. Example Solution:

    1. +

      1. Go to the top of the directory that is shared

      2. Set the ownership to what ever public owner and group you want - 

        -			find 'directory_name' -type d -exec chown user.group {}\;
-			find 'directory_name' -type d -exec chmod 6775 'directory_name'
-			find 'directory_name' -type f -exec chmod 0775 {} \;
-			find 'directory_name' -type f -exec chown user.group {}\;
-

        +

        +$ find 'directory_name' -type d -exec chown user.group {}\;
+$ find 'directory_name' -type d -exec chmod 6775 'directory_name'
+$ find 'directory_name' -type f -exec chmod 0775 {} \;
+$ find 'directory_name' -type f -exec chown user.group {}\;
+

        Note

        The above will set the 'sticky bit' on all directories. Read your - Unix/Linux man page on what that does. It causes the OS to assign + UNIX/Linux man page on what that does. It causes the OS to assign to all files created in the directories the ownership of the directory.

      3. Directory is: /foodbar - 

        -				$ chown jack.engr /foodbar
-

        -

        Note

        -

        This is the same as doing:

        - 

        -					$ chown jack /foodbar
-					$ chgrp engr /foodbar
-

        -

      4. Now do: +

        +$ chown jack.engr /foodbar
+

        +

        Note

        This is the same as doing:

        +$ chown jack /foodbar
+$ chgrp engr /foodbar
+

      5. Now do: - 

        -				$ chmod 6775 /foodbar
-				$ ls -al /foodbar/..
-

        +

        +$ chmod 6775 /foodbar
+$ ls -al /foodbar/..
+

        You should see: - 

        -				drwsrwsr-x  2 jack  engr    48 2003-02-04 09:55 foodbar
-

        +

        +drwsrwsr-x  2 jack  engr    48 2003-02-04 09:55 foodbar
+

      6. Now do: - 

        -				$ su - jill
-				$ cd /foodbar
-				$ touch Afile
-				$ ls -al
-

        +

        +$ su - jill
+$ cd /foodbar
+$ touch Afile
+$ ls -al
+

        You should see that the file Afile created by Jill will have ownership and permissions of Jack, as follows: - 

        -		-rw-r--r--  1 jack  engr     0 2003-02-04 09:57 Afile
-

        +

        +-rw-r--r--  1 jack  engr     0 2003-02-04 09:57 Afile
+

      7. Now in your smb.conf for the share add: - 

        -		force create mode = 0775
-		force directory mode = 6775
-

        +

        force create mode = 0775
        force direcrtory mode = 6775

        Note

        The above are only needed if your users are not members of the group you have used. ie: Within the OS do not have write permission on the directory.

        An alternative is to set in the smb.conf entry for the share: - 

        -		force user = jack
-		force group = engr
-

        -

    I have set force user and Samba still makes root the owner of all the files - I touch!

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

    Prev Up Next
    Chapter 12. Mapping MS Windows and Unix Groups Home Chapter 14. File and Record Locking
    +

    force user = jack
    force group = engr

    +

    I have set force user but Samba still makes root the owner of all the files I touch!

    + 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

    + Question: “When userB saves a word document that is owned by userA the updated file is now owned by userB. + Why is Samba doing this? How do I fix this?” +

    + Answer: Word does the following when you modify/change a Word document: Word Creates a NEW document with + a temporary name, Word then closes the old document and deletes it, Word then renames the new document to the original document name. + There is NO mechanism by which Samba CAN IN ANY WAY know that the new document really should be owned by the owners + of the original file. Samba has no way of knowing that the file will be renamed by MS Word. As far as Samba is able + to tell, the file that gets created is a NEW file, not one that the application (Word) is updating. +

    + There is a work-around to solve the permissions problem. That work-around involves understanding how you can manage file + system behaviour from within the smb.conf file, as well as understanding how Unix file systems work. Set on the directory + 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

    +

    + These two settings will ensure that all directories and files that get created in the share will be read/writable by the + owner and group set on the directory itself. +

    Prev Up Next
    Chapter 12. Mapping MS Windows and UNIX Groups Home Chapter 14. File and Record Locking
    diff --git a/docs/htmldocs/AdvancedNetworkManagement.html b/docs/htmldocs/AdvancedNetworkManagement.html index 296c684e24..1052f45e92 100644 --- a/docs/htmldocs/AdvancedNetworkManagement.html +++ b/docs/htmldocs/AdvancedNetworkManagement.html @@ -1,8 +1,8 @@ -Chapter 22. Advanced Network Management
    Chapter 22. Advanced Network Management
    Prev Part III. Advanced Configuration Next

    Chapter 22. Advanced Network Management

    John H. Terpstra

    Samba Team

    April 3 2003

    Table of Contents

    Features and Benefits
    Remote Server Administration
    Remote Desktop Management
    Remote Management from NoMachines.Com
    Network Logon Script Magic
    Adding printers without user intervention
    Common Errors

    +Chapter 22. Advanced Network Management

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

    Chapter 22. Advanced Network Management

    John H. Terpstra

    Samba Team

    April 3 2003

    Table of Contents

    Features and Benefits
    Remote Server Administration
    Remote Desktop Management
    Remote Management from NoMachines.Com
    Network Logon Script Magic
    Adding printers without user intervention
    Common Errors

    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 makes everything work more harmoniously. A key part of every network environment solution is the ability to remotely @@ -12,7 +12,7 @@ network operations.

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

    Remote Server Administration

    +

    Remote Server Administration

    How do I get 'User Manager' and 'Server Manager'?

    Since I don't need to buy an NT4 Server, how do I get the 'User Manager for Domains', @@ -26,12 +26,12 @@ Click here to download the archived file Windows NT 4.0 version of the 'User Manager for Domains' and 'Server Manager' are available from Microsoft via ftp from ftp://ftp.microsoft.com/Softlib/MSLFILES/SRVTOOLS.EXE -

    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 solutions 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 NoMachines.Com

    +

    Remote Management from NoMachines.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. @@ -119,7 +119,7 @@ is the best tool in your network environment. NoMachine are encouraging and offering help to OSS/Free Software implementations for such a frontend too, even if it means competition to them (they have written to this effect even to the LTSP, KDE and GNOME developer mailing lists) -

    Network Logon Script Magic

    +

    Network Logon Script Magic

    This section needs work. Volunteer contributions most welcome. Please send your patches or updates to John Terpstra.

    @@ -209,7 +209,7 @@ This is the genlogon.pl file:

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

    http://www.craigelachie.org/rhacer/ntlogon
    http://www.kixtart.org
    http://support.microsoft.com/default.asp?scid=kb;en-us;189105

    Adding printers without user intervention

    +

    http://www.craigelachie.org/rhacer/ntlogon
    http://www.kixtart.org
    http://support.microsoft.com/default.asp?scid=kb;en-us;189105

    Adding printers without user intervention

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

    @@ -217,8 +217,8 @@ Printers may be added automatically during logon script processing through the u

    See the documentation in the Microsoft knowledgebase article no: 189105. -

    Common Errors

    +

    Common Errors

    The information provided in this chapter has been reproduced from postings on the samba@samba.org mailing list. No implied endorsement or recommendation is offered. Administrators should conduct their own evaluation of alternatives and are encouraged to draw their own conclusions. -

    Prev Up Next
    Chapter 21. Integrated Logon Support using Winbind Home Chapter 23. System and Account Policies
    +

    Prev Up Next
    Chapter 21. Winbind: Use of Domain Accounts Home Chapter 23. System and Account Policies
    diff --git a/docs/htmldocs/Appendixes.html b/docs/htmldocs/Appendixes.html index 854437acde..6d77a0ba65 100644 --- a/docs/htmldocs/Appendixes.html +++ b/docs/htmldocs/Appendixes.html @@ -1,4 +1,3 @@ -Part VI. Appendixes
    Part VI. Appendixes
    Prev   Next

    Appendixes

    Table of Contents

    36. How to compile SAMBA
    Access Samba source code via CVS
    Introduction
    CVS 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 and nmbd
    Starting from inetd.conf
    Alternative: starting it as a daemon
    Common Errors
    37. Portability
    HPUX
    SCO Unix
    DNIX
    RedHat Linux Rembrandt-II
    AIX
    Sequential Read Ahead
    Solaris
    Locking improvements
    Winbind on Solaris 9
    38. Samba and other CIFS clients
    Macintosh clients?
    OS2 Client
    How can I configure OS/2 Warp Connect or - OS/2 Warp 4 as a client for Samba?
    How can I configure OS/2 Warp 3 (not Connect), - OS/2 1.2, 1.3 or 2.x for Samba?
    How do I get printer driver download working - for OS/2 clients?
    Windows for Workgroups
    Use latest TCP/IP stack from Microsoft
    Delete .pwl files after password change
    Configure WfW password handling
    Case handling of passwords
    Use TCP/IP as default protocol
    Speed improvement
    Windows '95/'98
    Speed improvement
    Windows 2000 Service Pack 2
    Windows NT 3.1
    39. Samba Performance Tuning
    Comparisons
    Socket options
    Read size
    Max xmit
    Log level
    Read raw
    Write raw
    Slow Logins
    Client tuning
    Samba performance problem due changing kernel
    Corrupt tdb Files
    40. DNS and DHCP Configuration Guide
    Note
    41. Further Resources
    Websites
    Related updates from Microsoft
    Books
    Prev Up Next
    Chapter 35. Reporting Bugs Home Chapter 36. How to compile SAMBA
    +Part VI. Appendixes
    Part VI. Appendixes
    Prev   Next

    Appendixes

    Table of Contents

    36. How to compile Samba
    Access Samba source code via CVS
    Introduction
    CVS 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 and nmbd
    Starting from inetd.conf
    Alternative: starting it as a daemon
    37. Portability
    HPUX
    SCO UNIX
    DNIX
    RedHat Linux Rembrandt-II
    AIX
    Sequential Read Ahead
    Solaris
    Locking improvements
    Winbind on Solaris 9
    38. Samba and other CIFS clients
    Macintosh clients?
    OS2 Client
    Configuring OS/2 Warp Connect or + OS/2 Warp 4 as a client for Samba
    Configuring OS/2 Warp 3 (not Connect), + OS/2 1.2, 1.3 or 2.x for Samba
    Printer driver download for for OS/2 clients?
    Windows for Workgroups
    Latest TCP/IP stack from Microsoft
    Delete .pwl files after password change
    Configuring WfW password handling
    Case handling of passwords
    Use TCP/IP as default protocol
    Speed improvement
    Windows '95/'98
    Speed improvement
    Windows 2000 Service Pack 2
    Windows NT 3.1
    39. Samba Performance Tuning
    Comparisons
    Socket options
    Read size
    Max xmit
    Log level
    Read raw
    Write raw
    Slow Logins
    Client tuning
    Samba performance problem due changing kernel
    Corrupt tdb Files
    40. DNS and DHCP Configuration Guide
    Note
    41. Further Resources
    Websites
    Related updates from Microsoft
    Prev Up Next
    Chapter 35. Reporting Bugs Home Chapter 36. How to compile Samba
    diff --git a/docs/htmldocs/Backup.html b/docs/htmldocs/Backup.html index 9fac452023..f19bd6d2b3 100644 --- a/docs/htmldocs/Backup.html +++ b/docs/htmldocs/Backup.html @@ -1,13 +1,11 @@ -Chapter 28. Samba Backup Techniques
    Chapter 28. Samba Backup Techniques
    Prev Part III. Advanced Configuration Next

    Chapter 28. Samba Backup Techniques

    John H. Terpstra

    Samba Team

    Table of Contents

    Note
    Features and Benefits

    Note

    +Chapter 28. Samba Backup Techniques

    Chapter 28. Samba Backup Techniques
    Prev Part III. Advanced Configuration Next

    Chapter 28. Samba Backup Techniques

    John H. Terpstra

    Samba Team

    Table of Contents

    Note
    Features and Benefits

    Note

    This chapter did not make it into this release. It is planned for the published release of this document. -If you have something to contribute for this section please email it to -jht@samba.org/ -

    Features and Benefits

    +

    Features and Benefits

    We need feedback from people who are backing up samba servers. We would like to know what software tools you are using to backup your samba server/s.

    In particular, if you have any success and / or failure stories you could share with other users this would be appreciated. -

    Prev Up Next
    Chapter 27. Unicode/Charsets Home Chapter 29. High Availability Options
    +

    Prev Up Next
    Chapter 27. Unicode/Charsets Home Chapter 29. High Availability Options
    diff --git a/docs/htmldocs/CUPS-printing.html b/docs/htmldocs/CUPS-printing.html index 46ca8e15f7..8bfe11405f 100644 --- a/docs/htmldocs/CUPS-printing.html +++ b/docs/htmldocs/CUPS-printing.html @@ -1,54 +1,59 @@ -Chapter 19. CUPS Printing Support in Samba 3.0
    Chapter 19. CUPS Printing Support in Samba 3.0
    Prev Part III. Advanced Configuration Next

    Chapter 19. CUPS Printing Support in Samba 3.0

    Kurt Pfeifle

    Danka Deutschland GmbH

    Ciprian Vizitiu

    drawings

    (3 June 2003)

    Table of Contents

    Introduction
    Features and Benefits
    Overview
    Basic Configuration of CUPS support
    Linking of smbd with libcups.so
    Simple smb.conf Settings for CUPS
    More complex smb.conf Settings for -CUPS
    Advanced Configuration
    Central spooling vs. "Peer-to-Peer" printing
    CUPS/Samba as a "spooling-only" Print Server; "raw" printing -with Vendor Drivers on Windows Clients
    Driver Installation Methods on Windows Clients
    Explicitly enable "raw" printing for -application/octet-stream!
    Three familiar Methods for driver upload plus a new one
    Using CUPS/Samba in an advanced Way -- 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
    CUPS can use all 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
    Filter Requirements
    Prefilters
    pstops
    pstoraster
    imagetops and imagetoraster
    rasterto [printers specific]
    CUPS Backends
    cupsomatic/Foomatic -- how do they fit into the Picture?
    The Complete Picture
    mime.convs
    "Raw" printing
    "application/octet-stream" printing
    PostScript Printer Descriptions (PPDs) for non-PS Printers
    Difference between cupsomatic/foomatic-rip and -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 -- UNIX/Samba Print -Servers)
    From Windows Clients to a CUPS/Samba Print Server
    Samba receiving Jobfiles and passing them to CUPS
    Network PostScript RIP: CUPS Filters on Server -- clients use -PostScript Driver with CUPS-PPDs
    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
    Setting up CUPS for driver Download
    cupsaddsmb: the unknown Utility
    Prepare your smb.conf for -cupsaddsmb
    CUPS Package of "PostScript Driver for WinNT/2k/XP"
    Recognize the different Driver Files
    Acquiring the Adobe Driver Files
    ESP Print Pro Package of "PostScript Driver for -WinNT/2k/XP"
    Caveats to be considered
    What are the Benefits of using the "CUPS PostScript Driver for -Windows NT/2k/XP" as compared to the Adobe Driver?
    Run "cupsaddsmb" (quiet Mode)
    Run "cupsaddsmb" with verbose Output
    Understanding cupsaddsmb
    How to recognize if cupsaddsm 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
    What is required for adddriver and setdriver to succeed
    Manual Commandline Driver Installation in 15 little 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
    Auto-Deletion or Preservation of CUPS Spool Files
    CUPS Configuration Settings explained
    Pre-conditions
    Manual Configuration
    When not to use Samba to print to -CUPS
    In Case of Trouble.....
    Where to find Documentation
    How to ask for Help
    Where to find Help
    Appendix
    Printing from CUPS to Windows attached -Printers
    More CUPS filtering Chains
    Trouble Shooting Guidelines to fix typical Samba printing -Problems
    An Overview of the CUPS Printing Processes

    Introduction

    Features and Benefits

    - The Common Unix Print System (CUPS) has become very popular. All - big Linux distributions now ship it as their default printing - system. But to many it is still a very mystical tool. Normally it - "just works" (TM). People tend to regard it as a sort of "black box", - which they don't want to look into, as long as it works OK. But once +Chapter 19. CUPS Printing Support in Samba 3.0

    Chapter 19. CUPS Printing Support in Samba 3.0
    Prev Part III. Advanced Configuration Next

    Chapter 19. CUPS Printing Support in Samba 3.0

    Kurt Pfeifle

    Danka Deutschland GmbH

    Ciprian Vizitiu

    drawings

    Jelmer R. Vernooij

    drawings
    The Samba Team

    (3 June 2003)

    Table of Contents

    Introduction
    Features and Benefits
    Overview
    Basic Configuration of CUPS support
    Linking of smbd with libcups.so
    Simple smb.conf Settings for CUPS
    More complex smb.conf Settings for +CUPS
    Advanced Configuration
    Central spooling vs. "Peer-to-Peer" printing
    CUPS/Samba as a "spooling-only" Print Server; "raw" printing +with Vendor Drivers on Windows Clients
    Driver Installation Methods on Windows Clients
    Explicitly enable "raw" printing for +application/octet-stream!
    Three familiar Methods for driver upload plus a new one
    Using CUPS/Samba in an advanced Way -- 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
    CUPS can use all 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
    Filter Requirements
    Prefilters
    pstops
    pstoraster
    imagetops and imagetoraster
    rasterto [printers specific]
    CUPS Backends
    cupsomatic/Foomatic -- how do they fit into the Picture?
    The Complete Picture
    mime.convs
    "Raw" printing
    "application/octet-stream" printing
    PostScript Printer Descriptions (PPDs) for non-PS Printers
    Difference between cupsomatic/foomatic-rip and +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 -- UNIX/Samba Print +Servers)
    From Windows Clients to a CUPS/Samba Print Server
    Samba receiving Jobfiles and passing them to CUPS
    Network PostScript RIP: CUPS Filters on Server -- clients use +PostScript Driver with CUPS-PPDs
    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
    Setting up CUPS for driver Download
    cupsaddsmb: the unknown Utility
    Prepare your smb.conf for cupsaddsmb
    CUPS Package of "PostScript Driver for WinNT/2k/XP"
    Recognize the different Driver Files
    Acquiring the Adobe Driver Files
    ESP Print Pro Package of "PostScript Driver for +WinNT/2k/XP"
    Caveats to be considered
    Benefits of using "CUPS PostScript Driver for +Windows NT/2k/XP" instead of 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
    What is required 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
    Auto-Deletion or Preservation of CUPS Spool Files
    CUPS Configuration Settings explained
    Pre-conditions
    Manual Configuration
    In Case of Trouble.....
    Printing from CUPS to Windows attached +Printers
    More CUPS filtering Chains
    Common Errors
    Win9x client can't install driver
    "cupsaddsmb" keeps asking for root password in + neverending loop
    "cupsaddsmb" gives "No PPD file for printer..." + message while PPD file is present
    Client can't connect to Samba printer
    Can't reconnect to Samba under new account + from Win2K/XP
    Avoid being connected to the Samba server as the + "wrong" user
    Upgrading to CUPS drivers from Adobe drivers on + NT/2K/XP clients gives problems
    Can't use "cupsaddsmb" on Samba server which is + a PDC
    Deleted Win2K printer driver is still shown
    Win2K/XP "Local Security + Policies"
    WinXP clients: "Administrator can not install + printers for all local users"
    "Print Change Notify" functions on + NT-clients
    WinXP-SP1
    Print options for all users can't be set on Win2K/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
    Printer named "lp" +intermittently swallows jobs and spits out completely different +ones
    Location of Adobe PostScript driver files necessary for "cupsaddsmb"
    An Overview of the CUPS Printing Processes

    Introduction

    Features and Benefits

    + The Common UNIX Print System (CUPS) has become very popular. All + major Linux distributions now ship it as their default printing + system. To many it is still a very mystical tool. Mostly, it + "just works" (TM). People tend to regard it as a "black box" + which they don't want to look into, as long as it works. But once there is a little problem, they are in trouble to find out where to - start debugging it. Also, even the most recent and otherwise excellent - printed Samba documentation has only limited attention paid to CUPS - printing, leaving out important pieces or even writing plain wrong - things about it. This demands rectification. But before you dive into - this chapter, make sure that you don't forget to refer to the - "Classical Printing" chapter also. It contains a lot of information - that is relevant for CUPS too. + start debugging it. Refer to the "Classical Printing" chapter also, it + contains a lot of information that is relevant for CUPS.

    CUPS sports quite a few unique and powerful features. While their basic functions may be grasped quite easily, they are also new. Because they are different from other, more traditional printing systems, it is best to try and not apply any prior knowledge about - printing upon this new system. Rather try to start understand CUPS - from the beginning. This documentation will lead you here to a - complete understanding of CUPS, if you study all of the material - contained. But lets start with the most basic things first. Maybe this - is all you need for now. Then you can skip most of the other - paragraphs. -

    Overview

    + printing upon 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

    CUPS is more than just a print spooling system. It is a complete printer management system that complies with the new IPP (Internet Printing Protocol). IPP is an industry and IETF (Internet Engineering Task Force) standard for network printing. Many of its functions can be managed remotely (or locally) via a web browser (giving you a - platform-independent access to the CUPS print server). In addition it - has the traditional commandline and several more modern GUI interfaces + platform-independent access to the CUPS print server). Additionally, it + has the traditional command line and several more modern GUI interfaces (GUI interfaces developed by 3rd parties, like KDE's overwhelming KDEPrint).

    @@ -60,80 +65,53 @@ Problems

    An Overview of the C argue that CUPS is better! In any case, let us now move on to explore how one may configure CUPS for interfacing with MS Windows print clients via Samba. -

    Basic Configuration of CUPS support

    - Printing with CUPS in the most basic smb.conf - setup in Samba 3.0 (as was true for 2.2.x) only needs two - settings: printing = cups and printcap - = cups. CUPS itself doesn't need a printcap file - anymore. However, the cupsd.conf configuration - file knows two related directives: they control if such a file should - be automatically created and maintained by CUPS for the convenience of - third party applications (example: Printcap - /etc/printcap and PrintcapFormat - BSD). These legacy programs often require the existence of - printcap file containing printernames or they will refuse to - print. Make sure CUPS is set to generate and maintain a printcap! For - details see man cupsd.conf and other CUPS-related - documentation, like the wealth of documents on your CUPS server +

    Basic Configuration of CUPS support

    + Printing with CUPS in the most basic smb.conf setup in Samba 3.0 (as was true for 2.2.x) only needs two + settings: 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 file will be automatically created and maintained by CUPS for the convenience of third party + applications (example: Printcap /etc/printcap and PrintcapFormat BSD). + Legacy programs often require the existence of a printcap file containing printer names or they will refuse to + 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 on your CUPS server itself: http://localhost:631/documentation.html. -

    Linking of smbd with libcups.so

    - Samba has a very special relationship to CUPS. The reason is: Samba - can be compiled with CUPS library support. Most recent installations - have this support enabled, and per default CUPS linking is compiled +

    Linking of smbd with libcups.so

    + Samba has a very special relationship to CUPS. Samba can be compiled with CUPS library support. + Most recent installations have this support enabled. Per 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 then.

    - If SAMBA is compiled against libcups, then printcap = - cups uses the CUPS API to list printers, submit jobs, - query queues, etc. Otherwise it maps to the System V commands with an - additional -oraw option for printing. On a Linux - system, you can use the ldd utility to find out - details (ldd may not be present on other OS platforms, or its function - may be embodied by a different command): - 

    -				transmeta:/home/kurt # ldd `which smbd`
-				libssl.so.0.9.6 => /usr/lib/libssl.so.0.9.6 (0x4002d000)
-				libcrypto.so.0.9.6 => /usr/lib/libcrypto.so.0.9.6 (0x4005a000)
-				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. This is an - important point to remember! -

    Tip

    Should you require -- for any reason -- to set your own - print commands, you can still do this by setting printing = - sysv. However, you'll loose all the benefits from the - close CUPS/Samba integration. You are on your own then to manually - configure the rest of the printing system commands (most important: - print command; other commands are - lppause command, lpresume command, lpq command, lprm - command, queuepause command and queue resume - command).

    Simple smb.conf Settings for CUPS

    - To summarize, here is the simplest printing-related setup - for smb.conf to enable basic CUPS support: + When Samba is compiled against libcups, printcap = cups + uses the CUPS API to list printers, submit jobs, query queues, etc. Otherwise it maps to the System V + commands with an additional -oraw option for printing. On a Linux + system, you can use the ldd utility to find out details (ldd may not be present on + other OS platforms, or its function may be embodied by a different command): 

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

    +root# ldd `which smbd` +libssl.so.0.9.6 => /usr/lib/libssl.so.0.9.6 (0x4002d000) +libcrypto.so.0.9.6 => /usr/lib/libcrypto.so.0.9.6 (0x4005a000) +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. + This is an important point to remember! +

    Tip

    Should it be necessary, for any reason, to set your own print commands, you can do this by setting + printing = sysv. However, you will loose all the benefits + of tight CUPS/Samba integration. When you do this you must manually configure the printing system commands + (most important: print command; other commands are + lppause command, + lpresume command, + lpq command, + lprm command, + queuepause command and + queue resume command).

    Simple smb.conf Settings for CUPS

    + To summarize, here is the simplest printing-related setup for smb.conf to enable basic CUPS support: +

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

    This is all you need for basic printing setup for CUPS. It will print all Graphic, Text, PDF and PostScript file submitted from Windows clients. However, most of your Windows users would not know how to @@ -148,67 +126,29 @@ Problems

    An Overview of the C printer is not a PostScript device, the print data stream is "binary", sensible only for the target printer. Read on to learn which problem this may cause and how to avoid it. -

    More complex smb.conf Settings for +

    More complex smb.conf Settings for CUPS

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

    -
- [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
-         writeable = 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 there for my testing purposes. It doesn't -even 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 jobfile. Moreover, the printer -admin of this share is "kurt" (not the "@ntadmins" group); -guest access is not allowed; the share isn't announced in Network -Neighbourhood (so you need to know it is there), and it is only -allowing access from three hosts. To prevent CUPS kicking in and -taking over the print jobs for that share, we need to set -printing = sysv and printcap = -lpstat. -

    Advanced Configuration

    -Before we dive into all the configuration options, let's clarify a few +

    Example 19.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
    writeable = 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 there 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 jobfile. Moreover, the +printer admin of this share is "kurt" (not the "@ntadmins" group); +guest access is not allowed; the share isn not published to the Network Neighbourhood (so you need to know it is there), and it only +allows access from only three hosts. To prevent CUPS kicking in and taking over the print jobs for that share, we need to set +printing = sysv and +printcap = lpstat. +

    Advanced Configuration

    +Before we delve into all the configuration options, let us clarify a few points. Network printing needs to be organized and setup correctly. Often this is not done correctly. Legacy systems -or small LANs in business environments often lack a clear design and -good housekeeping. -

    Central spooling vs. "Peer-to-Peer" printing

    +or small business LAN environments often lack design and good housekeeping. +

    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. Generally, this is a bad idea. It often blocks one client's +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 also might freeze the first client's application while it is waiting to get rid of the job. Also, there are frequent complaints about various jobs @@ -217,18 +157,18 @@ is the usage of a "print server": it routes all jobs through one central system, which responds immediately, takes jobs from multiple concurrent clients at the same time and in turn transfers them to the printer(s) in the correct order. -

    CUPS/Samba as a "spooling-only" Print Server; "raw" printing -with Vendor Drivers on Windows Clients

    -Most traditionally configured Unix print servers acting on behalf of +

    CUPS/Samba as a "spooling-only" Print Server; "raw" printing +with 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 Samba. This approach meant that the Windows clients were expected to -prepare the print job file in such a way that it became fit to be fed to -the printing device. Here a native (vendor-supplied) Windows printer +prepare the print job file that it s ready to be sent to the printing +device. Here a native (vendor-supplied) Windows printer driver for the target device needed to be installed on each and every client.

    -Of course you can setup CUPS, Samba and your Windows clients in the +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 Samba client to fully render the print job (file). The file must be @@ -236,21 +176,23 @@ sent in a format that is suitable for direct delivery to the printer. Clients need to run the vendor-provided drivers to do this. In this case CUPS will NOT do any print file format conversion work. -

    Driver Installation Methods on Windows Clients

    +

    Driver Installation Methods on Windows Clients

    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; it uses a \\sambaserver\printershare -type of connection.

    • deposit and prepare the drivers (for later download) on +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 +"Point and Print" to get drivers semi-automatically installed the first time they access the printer; with this method NT/2K/XP clients use the SPOOLSS/MS-RPC type printing calls.

    The second method is recommended for use over the first. -

    Explicitly enable "raw" printing for -application/octet-stream!

    +

    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 @@ -263,16 +205,12 @@ be uncommented to allow RAW mode operation. In/etc/cups/mime.types make sure this line is present: 

    -
  application/octet-stream
-

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

    -
+
      application/octet-stream   application/vnd.cups-raw   0   - 
-
 
    
 If these two files are not set up correctly for raw Windows client
 printing, you may encounter the dreaded Unable to
@@ -281,7 +219,7 @@ convert file 0 in your CUPS error_log file.
 mime.types file does not
 enforce "raw" printing, it only
 allows it.
-

    Background.  +

    Background.  CUPS being 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 @@ -298,7 +236,7 @@ This is all you need to know to get the CUPS/Samba combo printing locally installed. If you are not interested in background information about more advanced CUPS/Samba printing, simply skip the remaining sections of this chapter. -

    Three familiar Methods for driver upload plus a new one

    +

    Three familiar Methods for driver upload plus a new one

    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 @@ -306,23 +244,25 @@ Samba host (so that the Windows clients can download and use them via "Point'n'Print") please also refer to the previous chapter of this HOWTO Collection. 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" +

      • the GUI, "Add Printer Wizard" upload-from-a-Windows-client method;

      • the commandline, "smbclient/rpcclient" upload-from-a-UNIX-workstation -method;

      • the Imprints Toolset +method;

      • + + the Imprints Toolset method.

      These 3 methods apply to CUPS all the same. A new and more convenient way to load the Windows drivers into Samba is provided -provided if you use CUPS: -

      • the cupsaddsmb +if you use CUPS: +

        • the cupsaddsmb utility.

        cupsaddsmb is discussed in much detail further below. But we will first explore the CUPS filtering system and compare the Windows and UNIX printing architectures. -

    Using CUPS/Samba in an advanced Way -- intelligent printing -with PostScript Driver Download

    -Still reading on? Good. Let's go into more detail then. We now know +

    Using CUPS/Samba in an advanced Way -- intelligent printing +with PostScript Driver Download

    +Are you still following this? Good. Let's go into more detail then. We now know how to set up a "dump" printserver, that is, a server which is spooling printjobs "raw", leaving the print data untouched.

    @@ -343,13 +283,13 @@ server meeting these requirements, you'll first need to learn about how CUPS works and how you can enable its features.

    What follows is the comparison of some fundamental concepts for -Windows and Unix printing; then is the time for a description of the +Windows and UNIX printing; then is the time for a description of the CUPS filtering system, how it works and how you can tweak it. -

    GDI on Windows -- PostScript on Unix

    +

    GDI on Windows -- PostScript on UNIX

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

    +

    You can't expect for most file formats to just throw them towards printers and they get printed. There needs to be a file format conversion in between. The problem is: there is no common standard for @@ -361,7 +301,7 @@ into semi-official "standards", by being the most widely used PDLs many manufacturers who "roll their own" (their reasons may be unacceptable license fees for using printer-embedded PostScript interpreters, etc.). -

    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 GDI (Graphical Device @@ -378,16 +318,17 @@ the GDI, produces often a file format called EMF (Enh MetaFile). 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 their -(BSD-Unix-based, did you know??) Mac OS X and Darwin Operating -Systems.Their Core Graphic Engine uses a -PDF derivate for all display work. +(BSD-UNIX-based, did you know??) Mac OS X and Darwin Operating +Systems. Their Core Graphic Engine uses a +PDF derivative for all display work.

    -

    Figure 19.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 +

    Figure 19.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. That gives at least some common ground. Unfortunately, @@ -406,7 +347,7 @@ ready for prime time.) You can see this 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.  +

    Background.  The PostScript programming language is an "invention" by Adobe Inc., but its specifications have been published to the full. Its strength lies in its powerful abilities to describe graphical objects (fonts, @@ -422,9 +363,9 @@ form and you will be reading its PostScript code, the language instructions which need to be 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 +

    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: these devices have a built-in PostScript language "interpreter", also called a Raster Image @@ -434,33 +375,35 @@ spit out your printed pages. Their RIP is doing all the hard work of converting the PostScript drawing commands into a bitmap picture as you see it on paper, in a resolution as done by your printer. This is no different to PostScript printing of a file from a Windows origin. -

    Note

    Traditional Unix programs and printing systems -- while +

    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, punching... Therefore -Unix users for a long time couldn't choose many of the supported +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.... ;-) +is CUPS....

    -

    Figure 19.2. Printing to a Postscript Printer

    Printing to a Postscript Printer

    -

    +

    Figure 19.2. Printing to a Postscript Printer

    Printing to a Postscript Printer

    +

    However, there are other types of printers out there. These don't know how to print PostScript. They use their own Page Description Language (PDL, often proprietary). To print to them is much -more demanding. Since your Unix applications mostly produce +more demanding. Since your UNIX applications mostly produce PostScript, and since these devices don't understand PostScript, you need to convert the printfiles 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 to do a +UNIX platforms. It is a RIP in software, capable to do a lot of file format conversions, for a very broad spectrum of hardware devices as well as software file formats. Ghostscript technology and drivers is what enables PostScript printing to non-PostScript hardware.

    -

    Figure 19.3. Ghostscript as a RIP for non-postscript printers

    Ghostscript as a RIP for non-postscript printers

    +

    Figure 19.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" of your Ghostscript version. If you specify e.g. a parameter of @@ -473,12 +416,12 @@ 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 got some -deficiencies. Therefore ESP Ghostscript was developed as an +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, RedHat 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 Page Description Language (PDL) to represent the page layout in a device independent way, real world print jobs are @@ -504,15 +447,16 @@ user selections are somehow written (in the form of special 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). -

    CUPS can use all Windows-formatted Vendor PPDs

    +

    CUPS can use all Windows-formatted Vendor PPDs

    CUPS can handle all spec-compliant PPDs as supplied by the manufacturers for their PostScript models. Even if a -Unix/Linux-illiterate vendor might not have mentioned our favorite +UNIX/Linux-illiterate vendor might not have mentioned our favorite OS in his manuals and brochures -- you can safely trust this: if you get hold of the Windows NT version of the PPD, you can use it unchanged in CUPS and thus access the full @@ -524,6 +468,8 @@ immediately. CUPS in all versions after 1.1.19 has a much more strict internal PPD parsing and checking code enabled; in case of printing trouble this online resource should be one of your first pitstops.

    Warning

    + + For real PostScript printers don't use the Foomatic or cupsomatic PPDs from Linuxprinting.org. With these devices the original @@ -536,7 +482,7 @@ your LAN has the PostScript driver installed, just use access the Windows directory where all printer driver files are stored. First look in the W32X86/2 subdir 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 @@ -544,7 +490,7 @@ 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 @@ -570,23 +516,27 @@ Make sure your Ghostscript version has the "cups" device compiled in 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 re-compile or use ESP Ghostscript. The +Ghostscript and re-compile or use ESP Ghostscript. The superior alternative is ESP Ghostscript: it supports not just CUPS, but 300 other devices too (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 setup to use external rendering paths. One of the most common ones is provided by the Foomatic/cupsomatic concept, from Linuxprinting.org. This uses the classical Ghostscript approach, doing everything in one step. It doesn't use the "cups" device, but one of the many others. However, even for Foomatic/cupsomatic usage, best results and + broadest printer model support is provided by ESP Ghostscript (more about cupsomatic/Foomatic, particularly the new version called now foomatic-rip, follows below). -

    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 @@ -595,10 +545,10 @@ auto-typing 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 either a .pdf suffix, or if the magic @@ -607,9 +557,7 @@ 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>%!)
-

    Its meaning: if the filename has one of the suffixes .ai, .eps, @@ -639,7 +587,7 @@ CUPS can handle ASCII text, HP-GL, PDF, PostScript, DVI and a lot of image formats (GIF. PNG, TIFF, JPEG, Photo-CD, SUN-Raster, PNM, PBM, SGI-RGB and some 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 @@ -648,39 +596,31 @@ conversion filter which can produce the output from the input type and virtual costs associated with this conversion. One example line reads like this: 

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

    Filter Requirements

    +

    Filter Requirements

    There are many more combinations named in mime.convs. However, you are not limited to use the ones pre-defined there. You can plug in any filter you like into the CUPS framework. It must meet, or must be made @@ -696,13 +636,13 @@ filenames or stdin as input and write to printer job user title copies options [filename]

    Printer

    The name of the printer queue (normally this is the name of the filter being run)

    job

    The numeric job ID for the job being -printed

    Printer

    The string from the originating-user-name -attribute

    Printer

    The string from the job-name attribute

    Printer

    The numeric value from the number-copies -attribute

    Printer

    The job options

    Printer

    (Optionally) The print request file (if missing, +printed

    user

    The string from the originating-user-name +attribute

    title

    The string from the job-name attribute

    copies

    The numeric value from the number-copies +attribute

    options

    The job options

    filename

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

    Prefilters

    -As was said, PostScript is the central file format to any Unix based +filters to make them work with CUPS.

    Prefilters

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

    @@ -719,8 +659,8 @@ MIME type application/vnd.cups-postscript (not application/postscript), meaning it has the print options already embedded into the file.

    -

    Figure 19.4. Prefiltering in CUPS to form Postscript

    Prefiltering in CUPS to form Postscript

    -

    pstops

    +

    Figure 19.4. Prefiltering in CUPS to form Postscript

    Prefiltering in CUPS to form Postscript

    +

    pstops

    pstopsis the filter to convert application/postscript to application/vnd.cups-postscript. It was said @@ -728,7 +668,7 @@ above that this filter inserts all device-specific print options (commands to the printer to ask for the duplexing of output, or stapling an punching it, etc.) into the PostScript file.

    -

    Figure 19.5. Adding Device-specific Print Options

    Adding Device-specific Print Options

    +

    Figure 19.5. Adding Device-specific Print Options

    Adding Device-specific Print Options

    This is not all: other tasks performed by it are:

    • @@ -740,7 +680,7 @@ putting 2 or more logical pages on one sheet of paper (the 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; @@ -749,20 +689,20 @@ yet meant to be printable. Its aim is to serve as a general purpose input format for more specialized raster drivers, that are able to generate device-specific printer data.

    -

    Figure 19.6. Postscript to intermediate Raster format

    Postscript to intermediate Raster format

    +

    Figure 19.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 following downstream raster drivers. Its MIME type is registered with IANA and its specification is of course completely open. It is designed to make it very easy and inexpensive for -manufacturers to develop Linux and Unix raster drivers for their +manufacturers to develop Linux and UNIX raster drivers for their printer models, should they choose to do so. CUPS always takes care for the first stage of rasterization so these vendors don't need to care about Ghostscript complications (in fact, there is currently more than one vendor financing the development of CUPS raster drivers).

    -

    Figure 19.7. CUPS-raster production using Ghostscript

    CUPS-raster production using Ghostscript

    +

    Figure 19.7. CUPS-raster production using Ghostscript

    CUPS-raster production using Ghostscript

    CUPS versions before version 1.1.15 were shipping a binary (or source code) standalone filter, named "pstoraster". pstoraster was derived @@ -776,7 +716,7 @@ integrated back into Ghostscript (now based on GNU Ghostscript version parameter. If your Ghostscript doesn't show a success on asking for gs -h |grep cups, you might not be able to print. Update your Ghostscript then! -

    imagetops and imagetoraster

    +

    imagetops and imagetoraster

    Above 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 @@ -784,13 +724,13 @@ intermediate PostScript stage. It is used more often than the above mentioned prefilters. Here is a summarizing flowchart of image file filtering:

    -

    Figure 19.8. Image format to CUPS-raster format conversion

    Image format to CUPS-raster format conversion

    -

    rasterto [printers specific]

    +

    Figure 19.8. Image format to CUPS-raster format conversion

    Image format to CUPS-raster format conversion

    +

    rasterto [printers specific]

    CUPS ships with quite some different raster drivers processing CUPS raster. On my system I find in /usr/lib/cups/filter/ these: -rastertoalps, rastertobj, rastertoepson, rastertoescp, -rastertopcl, rastertoturboprint, rastertoapdk, rastertodymo, -rastertoescp, rastertohp and +rastertoalps, rastertobj, rastertoepson, rastertoescp, +rastertopcl, rastertoturboprint, rastertoapdk, rastertodymo, +rastertoescp, rastertohp and rastertoprinter. Don't worry if you have less than this; some of these are installed by commercial add-ons to CUPS (like rastertoturboprint), others (like @@ -798,8 +738,8 @@ than this; some of these are installed by commercial add-ons to CUPS development projects (such as Gimp-Print) wanting to cooperate as closely as possible with CUPS.

    -

    Figure 19.9. Raster to Printer Specific formats

    Raster to Printer Specific formats

    -

    CUPS Backends

    +

    Figure 19.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 @@ -854,7 +794,7 @@ This backend sends printfiles to printers shared by a Windows host. An example for CUPS device-URIs to use are: smb://workgroup/server/printersharename Or -Smb://server/printersharename +smb://server/printersharename or smb://username:password@workgroup/server/printersharename or @@ -880,13 +820,11 @@ printername). 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 -utility. Used with the -v parameter, it lists +utility. Used with the -v parameter, it lists all available backends: 

    -
- lpinfo -v
-
-

    cupsomatic/Foomatic -- how do they fit into the Picture?

    +$ lpinfo -v +

    cupsomatic/Foomatic -- how do they fit into the Picture?

    "cupsomatic" filters may be the most widely used on CUPS installations. You must be clear about the fact that these were not developed by the CUPS people. They are a "Third Party" add-on to @@ -900,9 +838,7 @@ Printer & Driver Database at Linuxprinting.org. You can recognize these PPDs from the line calling the cupsomatic filter: 

    -
  *cupsFilter: "application/vnd.cups-postscript  0  cupsomatic"
-

    This line you may find amongst the first 40 or so lines of the PPD file. If you have such a PPD installed, the printer shows up in the @@ -911,7 +847,7 @@ the driver description. cupsomatic is a Perl script that runs Ghostscript, with all the complicated commandline options auto-constructed from the selected PPD and commandline options give to the printjob. -

    +

    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 @@ -936,11 +872,11 @@ print-options from page to page, in the middle of a job. And the best thing is: the new foomatic-rip now works seamlessly with all legacy spoolers too (like LPRng, BSD-LPD, PDQ, PPR etc.), providing for them access to use PPDs for their printing! -

    The Complete Picture

    +

    The Complete Picture

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

    mime.convs

    +

    mime.convs

    CUPS auto-constructs all possible filtering chain paths for any given MIME type, and every printer installed. But how does it decide in favor or against a specific alternative? (There may often be cases, @@ -957,7 +893,7 @@ cost. This is a very efficient way to limit the load of any CUPS server by setting an appropriate "FilterLimit" value. A FilterLimit of 200 allows roughly 1 job at a time, while a FilterLimit of 1000 allows approximately 5 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 @@ -966,9 +902,7 @@ printing can happen on any queue if the "-o raw" option is specified on the command line. You can also set up raw-only queues by simply not associating any PPD with it. This command: 

    -
- lpadmin -P rawprinter -v socket://11.12.13.14:9100 -E
-
+$ lpadmin -P rawprinter -v socket://11.12.13.14:9100 -E

    sets up a queue named "rawprinter", connected via the "socket" protocol (a.k.a. "HP JetDirect") to the device at IP address @@ -980,7 +914,7 @@ CUPS will automatically treat each job sent to a queue as a "raw" one, 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 @@ -989,9 +923,7 @@ you will probably have experienced the fact that printjobs originating from Windows clients were not printed. You may have found an error message in your CUPS logs like: 

    -
  Unable to convert file 0 to printable format for job
-

    To enable the printing of "application/octet-stream" files, edit these two files: @@ -1000,20 +932,16 @@ Both contain entries (at the end of the respective files) which 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
-
 
    
 This line (with no specific auto-typing rule set) makes all files
 not otherwise auto-typed a member of application/octet-stream. In
 /etc/cups/mime.convs, have this
 line: 
 
    -
  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 @@ -1038,7 +966,7 @@ be one that is known to CUPS and an allowed one. The file 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 (PPDs) for non-PS Printers

    +

    PostScript Printer Descriptions (PPDs) for non-PS 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 jobfile. CUPS has extended this @@ -1051,10 +979,8 @@ printers the Ghostscript RIP runs on the host computer.

    PPDs for a non-PS 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
-
 
    
 It is the last piece in the CUPS filtering puzzle. This line tells the
 CUPS daemon to use as a last filter "rastertoprinter".  This filter
@@ -1070,24 +996,12 @@ CUPS by default ships only a few generic PPDs, but they are good for
 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):
-
    deskjet.ppd
    older HP inkjet printers and compatible
-
    deskjet2.ppd
    newer HP inkjet printers and compatible
-
    dymo.ppd
    label printers
-
    epson9.ppd
    Epson 24pin impact printers and compatible
-
    epson24.ppd
    Epson 24pin impact printers and compatible
-
    okidata9.ppd
    Okidata 9pin impact printers and compatible
-
    okidat24.ppd
    Okidata 24pin impact printers and compatible
-
    stcolor.ppd
    older Epson Stylus Color printers
-
    stcolor2.ppd
    newer Epson Stylus Color printers
-
    stphoto.ppd
    older Epson Stylus Photo printers
-
    stphoto2.ppd
    newer Epson Stylus Photo printers
-
    laserjet.ppd
    all PCL printers. Further below is a discussion
-of several other driver/PPD-packages suitable fur use with CUPS.
-

    Difference between cupsomatic/foomatic-rip and -native CUPS printing

    +

    Table 19.1. PPD's 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 24pin impact printers and compatible
    epson24.ppdEpson 24pin impact printers and compatible
    okidata9.ppdOkidata 9pin impact printers and compatible
    okidat24.ppdOkidata 24pin 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. Further below is a discussion of several other driver/PPD-packages suitable for use with CUPS.

    Difference between cupsomatic/foomatic-rip and +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 comes the "rasterdriver" step. It uses various @@ -1097,7 +1011,7 @@ Shareware/Non-Free, some are proprietary.

    Often this produces better quality (and has several more advantages) than other methods.

    -

    Figure 19.10. cupsomatic/foomatic processing versus Native CUPS

    cupsomatic/foomatic processing versus Native CUPS

    +

    Figure 19.10. cupsomatic/foomatic processing versus Native CUPS

    cupsomatic/foomatic processing versus Native CUPS

    One other method is the cupsomatic/foomatic-rip way. Note that cupsomatic is not made by the CUPS @@ -1111,6 +1025,8 @@ other (non-CUPS) spoolers. An upgrade to foomatic-rip is strongly advised, especially if you are upgrading to a recent version of CUPS too.

    + + Both the cupsomatic (old) and the foomatic-rip (new) methods from Linuxprinting.org use the traditional Ghostscript print file processing, doing everything in a single step. It therefore relies on @@ -1132,7 +1048,7 @@ installation: Therefore the printfile bypasses the "pstoraster" filter cupsomatic hands the rendered file directly to the CUPS backend. The flowchart above 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.

    @@ -1152,10 +1068,8 @@ PPD) into the new PostScript file; the file now is of PostScript MIME type application/vnd.cups-postscript;

  • the file goes to the socket backend, which transfers the job to the printers.

    • -The resulting filter chain therefore is: -

    -pdftops --> pstops --> socket
-

    + The resulting filter chain therefore is as drawn in the image below. +

    Figure 19.11. PDF to socket chain

    PDF to socket chain

    Assume your 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 @@ -1179,45 +1093,43 @@ does its work (as is indicated in the printer's PPD), creating the printer-specific raster data and embedding any user-selected print-options into the print data stream;

  • the file goes to the usb backend, which transfers the job to the printers.

    • -The resulting filter chain therefore is: -

    -pdftops --> pstops --> pstoraster --> rastertoepson --> usb
-

    Sources of CUPS drivers / PPDs

    + The resulting filter chain therefore is as drawn in the image below. +

    Figure 19.12. PDF to USB chain

    PDF to USB chain

    Sources of CUPS drivers / PPDs

    On the internet you can find now many thousand CUPS-PPD files (with their companion filters), in many national languages, supporting more than 1000 non-PostScript models. -

    • ESP -PrintPro (http://wwwl.easysw.com/printpro/) (commercial, +

      • ESP +PrintPro (commercial, non-Free) is packaged with more than 3000 PPDs, ready for successful use "out of the box" on Linux, Mac OS X, IBM-AIX, -HP-UX, Sun-Solaris, SGI-IRIX, Compaq Tru64, Digital Unix and some +HP-UX, Sun-Solaris, SGI-IRIX, Compaq Tru64, Digital UNIX and some more commercial Unices (it is written by the CUPS developers themselves and its sales help finance the further development of CUPS, as they feed their creators).

      • the Gimp-Print-Project -(http://gimp-print.sourceforge.net/) (GPL, Free Software) + (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;

      • TurboPrint -(http://www.turboprint.com/) (Shareware, non-Free) supports + (Shareware, non-Free) supports roughly the same amount of printers in excellent quality;

      • OMNI -(http://www-124.ibm.com/developerworks/oss/linux/projects/omni/) + (LPGL, Free) is a package made by IBM, now containing support for more than 400 printers, stemming from the inheritance of IBM OS/2 Know-How ported over to Linux (CUPS support is in a Beta-stage at present);

      • HPIJS -(http://hpinkjet.sourceforge.net/) (BSD-style licenses, Free) + (BSD-style licenses, Free) supports around 150 of HP's own printers and is also providing excellent print quality now (currently available only via the Foomatic path);

      • Foomatic/cupsomatic -(http://www.linuxprinting.org/) (LPGL, Free) from + (LPGL, Free) from Linuxprinting.org are providing PPDs for practically every Ghostscript filter known to the world (including Omni, Gimp-Print and HPIJS).

      Note

      The cupsomatic/Foomatic trick from Linuxprinting.org works differently from the other drivers. This is explained elsewhere in this document. -

    Printing with Interface Scripts

    +

    Printing with Interface Scripts

    CUPS also supports the usage 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 @@ -1230,61 +1142,60 @@ realm. On HP-UX platforms they are more often used. You can use any working interface script on CUPS too. Just install the printer with the -i option: 

    -
- lpadmin -p pclprinter -v socket://11.12.13.14:9100 -i /path/to/interface-script
-
+root# lpadmin -p pclprinter -v socket://11.12.13.14:9100 \
+  -i /path/to/interface-script

    Interface scripts might be the "unknown animal" to many. However, with CUPS they provide the most easy way to plug in your own custom-written filtering script or program into one specific print queue (some information about the traditional usage of interface scripts is to be 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 -

    • execute the driver locally and render the GDI output +

      • execute the driver locally and render the GDI output (EMF) into the printer specific format on their own, or

      • send the GDI output (EMF) to the server, where the driver is executed to render the printer specific output.

      Both print paths are shown in the flowcharts below. -

    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 jobfile and try to convert it in any -way. This is what traditional Unix-based print server can do too; and +way. This is what traditional UNIX-based print server can do too; and at a better performance and more reliably than NT print server. This is what most Samba administrators probably are familiar with. One advantage of this setup is that this "spooling-only" print server may -be used even if no driver(s) for Unix are available it is sufficient +be used even if no driver(s) for UNIX are available it is sufficient to have the Windows client drivers available and installed on the clients.

    -

    Figure 19.11. Print Driver execution on the Client

    Print Driver execution on the Client

    -

    Driver Execution on the Server

    +

    Figure 19.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 clients 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 +the printer-specific language. It is not possible for UNIX to do the same. Currently there is no program or method to convert a Windows -client's GDI output on a Unix server into something a printer could +client's GDI output on a UNIX server into something a printer could understand.

    -

    Figure 19.12. Print Driver execution on the Server

    Print Driver execution on the Server

    +

    Figure 19.14. Print Driver execution on the Server

    Print Driver execution on the Server

    However, there is something similar possible with CUPS. Read on... -

    Network Printing (Windows clients -- UNIX/Samba Print +

    Network Printing (Windows clients -- UNIX/Samba Print Servers)

    Since UNIX print servers cannot execute the Win32 program code on their platform, the picture is somewhat different. However, this doesn't limit your options all that much. In the contrary, you may have a way here to implement printing features which 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 powerful features for the benefit of your Windows network printing clients: @@ -1296,12 +1207,11 @@ printer is a non-PostScript model. It also requires that you have a "driver" on the CUPS server.

    Firstly, to enable CUPS based printing through Samba the -following options should be set in your smb.conf file [globals] +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 +(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 it's application program interface (API) - as long as Samba has been compiled with CUPS library (libcups) @@ -1310,12 +1220,12 @@ other print commands are set up, then printing will use the System V AT&T command set, with the -oraw option automatically passing through (if you want your own defined print commands to work with a Samba that has CUPS support compiled in, -simply use printing = sysv). +simply use printing = sysv).

    -

    Figure 19.13. Printing via CUPS/samba server

    Printing via CUPS/samba server

    -

    Samba receiving Jobfiles and passing them to CUPS

    +

    Figure 19.15. Printing via CUPS/samba server

    Printing via CUPS/samba server

    +

    Samba receiving Jobfiles and passing them to CUPS

    Samba must use its own spool directory (it is set -by a line similar to path = /var/spool/samba, +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 @@ -1331,8 +1241,8 @@ 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 they run on different machines, you need to make sure the Samba host gets access to printing on CUPS. -

    Network PostScript RIP: CUPS Filters on Server -- clients use -PostScript Driver with CUPS-PPDs

    +

    Network PostScript RIP: CUPS Filters on Server -- clients use +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 (PostScript Printer Descriptions) are always a component of @@ -1351,7 +1261,7 @@ or see if you have lphelp on your system). There are also some different GUI frontends 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 doesn't limit itself to "real" PostScript printers in its usage of PPDs. The CUPS developers have extended the scope of the PPD concept, to also describe available device and driver options for @@ -1368,7 +1278,7 @@ 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 WindowsNT/2K/XP"; you can also use the Adobe one, with @@ -1384,13 +1294,13 @@ which always remain unfiltered per definition;

  • enable clients to driver, even for many different target printers.

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

    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 need often 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

    The reason is that in Win NT printer drivers run in "Kernel Mode", this introduces a high risk for the stability of the system @@ -1404,10 +1314,10 @@ of Death" on a regular basis? PostScript drivers generally are very well tested. They are not known to cause any problems, even though they run in Kernel Mode too. This might be because there have so far only been 2 different PostScript -drivers the ones from Adobe and the one from Microsoft. Both are +drivers: the ones from Adobe and the one from Microsoft. Both are very well tested and are as stable as you ever can imagine on Windows. The CUPS driver is derived from the Microsoft one. -

    Workarounds impose Heavy Limitations

    +

    Workarounds impose Heavy Limitations

    In many cases, in an attempt to work around this problem, site administrators have resorted to restrict the allowed drivers installed on their WTS to one generic PCL- and one PostScript driver. This @@ -1415,7 +1325,7 @@ however restricts the clients in the amount of printer options available for them; 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 3 different PostScript @@ -1427,8 +1337,8 @@ is a certain price for this too: a CUPS 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 -Mode

    +

    PostScript Drivers with no major problems -- even in Kernel +Mode

    More recent printer drivers on W2K and XP don't run in Kernel mode (unlike Win NT) any more. However, both operating systems can still use the NT drivers, running in Kernel mode (you can roughly tell which @@ -1444,14 +1354,14 @@ development efforts. This is what the CUPS people have done. The license doesn't allow them to publish the whole of the source code. However, they have released the "diff" under the GPL, and if you are owner of an "MS DDK for Win NT", you can check the driver yourself. -

    Setting up CUPS for driver Download

    +

    Setting up 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 the previous chapter. In reality, this is a pure Samba business, and only relates to the Samba/Win 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 @@ -1476,53 +1386,26 @@ job-billing)

    However, currently only Windows NT, 2000, and XP are supported by the CUPS drivers. You will need to get the respective part of Adobe driver too 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 following settings in 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           # setting depends on your requirements
-         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 Package of "PostScript Driver for WinNT/2k/XP"

    -CUPS users may get the exactly same packages fromhttp://www.cups.org/software.html. +

    Example 19.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 Package of "PostScript Driver for WinNT/2k/XP"

    +CUPS users may get the exactly same packages from http://www.cups.org/software.html. It is a separate package from the CUPS base software files, tagged as -CUPS 1.1.x Windows NT/2k/XP Printer Driver for SAMBA +CUPS 1.1.x Windows NT/2k/XP Printer Driver for Samba (tar.gz, 192k). The filename to download is cups-samba-1.1.x.tar.gz. Upon untar-/unzip-ing, it will reveal these files: 

    -
-# tar xvzf cups-samba-1.1.19.tar.gz 
-
-   cups-samba.install
-   cups-samba.license
-   cups-samba.readme
-   cups-samba.remove
-   cups-samba.ss
-
+root# tar xvzf cups-samba-1.1.19.tar.gz
+cups-samba.install
+cups-samba.license
+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 @@ -1532,26 +1415,20 @@ too). Then it puts the content into /usr/share/cups/drivers/. This content includes 3 files: 

    -
-# tar tv cups-samba.ss
-
-    cupsdrvr.dll
-    cupsui.dll
-    cups.hlp  
-
+root# tar tv cups-samba.ss
+cupsdrvr.dll
+cupsui.dll
+cups.hlp

    The cups-samba.install shell scripts is easy to handle: 

    -
-# ./cups-samba.install
-
-   [....]
-   Installing software...
-   Updating file permissions...
-   Running post-install commands...
-   Installation is complete.        
-
+root# ./cups-samba.install
+[....]
+Installing software...
+Updating file permissions...
+Running post-install commands...
+Installation is complete.

    The script should automatically put the driver files into the /usr/share/cups/drivers/ directory. @@ -1564,10 +1441,8 @@ copy/move the file (after running the ./cups-samba.install script) manually to the right place. 

    -
-   cp /usr/share/drivers/cups.hlp /usr/share/cups/drivers/
-
-

    +root# cp /usr/share/drivers/cups.hlp /usr/share/cups/drivers/ +

    This new CUPS PostScript driver is currently binary-only, but free of charge. No complete source code is provided (yet). The reason is this: it has been developed with the help of the Microsoft Driver @@ -1576,42 +1451,27 @@ 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 of Visual Studio and a DDK will be able to compile for him/herself. -

    Recognize the different Driver Files

    +

    Recognize the different Driver Files

    The CUPS drivers don't 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
-
-

    +

    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 the Windows NT/2000/XP clients. The set of files is different for 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
+
    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

    +

    Note

    If both, the Adobe driver files and the CUPS driver files for the support of WinNT/2k/XP are present in , the Adobe ones will be ignored and the CUPS ones will be used. If you prefer -- for whatever reason -- to use Adobe-only drivers, move away the 3 CUPS driver files. The Win95/98/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 website as single files and the self-extracting and/or self-installing Windows-exe is @@ -1624,12 +1484,12 @@ Generic PostScript printer. After this, the client's where you can get them with smbclient from the CUPS host. A more detailed description about this is in the next (the CUPS printing) chapter. -

    ESP Print Pro Package of "PostScript Driver for -WinNT/2k/XP"

    +

    ESP Print Pro Package of "PostScript Driver for +WinNT/2k/XP"

    Users of the ESP Print Pro software are able to install their "Samba Drivers" package for this purpose with no problem. Retrieve the driver files from the normal download area of the ESP Print Pro software -athttp://www.easysw.com/software.html. +at http://www.easysw.com/software.html. You need to locate the link labelled "SAMBA" amongst the Download Printer Drivers for ESP Print Pro 4.x area and download the package. Once installed, you can prepare any @@ -1640,7 +1500,7 @@ driver files; i.e. mainly setup the [print$] share, etc. 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 @@ -1651,6 +1511,7 @@ tree with WIN40 and "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 @@ -1672,6 +1533,7 @@ installations in the /usr/share/cups/drivers/ directory. The new cupsaddsmb (from 1.1.16) will automatically prefer "its own" drivers if it finds both.

  • + Should your Win 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/2k/XP @@ -1679,8 +1541,7 @@ will fail at first. You need to wipe the old driver from the clients first. It is not enough to "delete" the printer, as the driver files will still be kept by the clients and re-used if you try to re-install the printer. To really get rid of the Adobe driver files on the -clients, open the "Printers" folder (possibly via Start ---> Settings --> Control Panel --> Printers), +clients, open the "Printers" folder (possibly via Start, Settings, Control Panel, Printers), right-click onto the folder background and select Server Properties. When the new dialog opens, select the Drivers tab. On the list select the driver you @@ -1690,20 +1551,23 @@ which uses that particular driver. You need to "delete" all printers using this driver in the "Printers" folder first. You will need Administrator privileges to do this.

  • + 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 elsewhere in the "Samba HOWTO Collection": either change +as described in the printing chapter: either change a driver for an existing printer by running the "Printer Properties" dialog, or use rpcclient with the setdriver sub-command.

    • -

    What are the Benefits of using the "CUPS PostScript Driver for -Windows NT/2k/XP" as compared to the Adobe Driver?

    +

    Benefits of using "CUPS PostScript Driver for +Windows NT/2k/XP" instead of Adobe Driver

    You are interested in a comparison between the CUPS and the Adobe PostScript drivers? For our purposes these are the most important items which weigh in favor of the CUPS ones:

    • no hassle with the Adobe EULA

    • no hassle with the question “Where do I -get the ADOBE*.* driver files from?”

    • the Adobe drivers (on request of the printer PPD +get the ADOBE*.* driver files from?”

    • + + 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 printfile starts with <1B >%-12345X or @@ -1712,8 +1576,10 @@ of %!PS). This leads to the CUPS daemon auto-typing 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 + 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 @@ -1743,7 +1609,7 @@ not disturb any other applications as 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/2K/XP to be released soon (probably alongside the first Beta release for CUPS -1.2).

    Run "cupsaddsmb" (quiet Mode)

    +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 @@ -1752,124 +1618,111 @@ associated with this printer is copied from Windows client installations via Point'n'Print. Before we can run the command successfully, we need to be sure that we can authenticate towards Samba. If you have a small network you are probably using user -level security (security = user). Probably your -root has already a Samba account. Otherwise, create it now, using -smbpasswd: -

    -
- #  smbpasswd -a root 
- New SMB password: [type in password 'secret']
- Retype new SMB password: [type in password 'secret']
-
-

    +level security (security = user). +

    Here is an example of a successfully run cupsaddsmb command. 

    -
- #  cupsaddsmb -U root infotec_IS2027
- Password for root required to access localhost via SAMBA: [type in password 'secret']
-
+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 +-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 +-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:

    Warning

    You will see the root password for the Samba account printed on -screen. If you use remote access, the password will go over the wire -unencrypted! -

    -
-  # cupsaddsmb -U root -v infotec_2105
-  Password for root required to access localhost via SAMBA:
-  Running command: smbclient //localhost/print\$ -N -U'root%secret' -c 'mkdir W32X86;put   \
-                   /var/spool/cups/tmp/3e98bf2d333b5 W32X86/infotec_2105.ppd;put           \
-                   /usr/share/cups/drivers/cupsdrvr.dll W32X86/cupsdrvr.dll;put            \
-                   /usr/share/cups/drivers/cupsui.dll W32X86/cupsui.dll;put                \
-                   /usr/share/cups/drivers/cups.hlp W32X86/cups.hlp'
-  added interface ip=10.160.51.60 bcast=10.160.51.255 nmask=255.255.252.0
-  Domain=[CUPS-PRINT] OS=[Unix] Server=[Samba 2.2.7a]
-  NT_STATUS_OBJECT_NAME_COLLISION making remote directory \W32X86
-  putting file /var/spool/cups/tmp/3e98bf2d333b5 as \W32X86/infotec_2105.ppd (2328.8 kb/s) \
-               (average 2328.8 kb/s)
-  putting file /usr/share/cups/drivers/cupsdrvr.dll as \W32X86/cupsdrvr.dll (9374.3 kb/s)  \
-               (average 5206.6 kb/s)
-  putting file /usr/share/cups/drivers/cupsui.dll as \W32X86/cupsui.dll (8107.2 kb/s)      \
-               (average 5984.1 kb/s)
-  putting file /usr/share/cups/drivers/cups.hlp as \W32X86/cups.hlp (3475.0 kb/s)          \
-               (average 5884.7 kb/s)
+screen. 
+
    +root# cupsaddsmb -U root -v infotec_2105
+Password for root required to access localhost via GANDALF:
+Running command: smbclient //localhost/print\$ -N -U'root%secret' \
+    -c 'mkdir W32X86; \
+    put /var/spool/cups/tmp/3e98bf2d333b5 W32X86/infotec_2105.ppd; \
+	put /usr/share/cups/drivers/cupsdrvr.dll W32X86/cupsdrvr.dll; \
+    put /usr/share/cups/drivers/cupsui.dll W32X86/cupsui.dll; \
+    put /usr/share/cups/drivers/cups.hlp W32X86/cups.hlp'
+added interface ip=10.160.51.60 bcast=10.160.51.255 nmask=255.255.252.0
+Domain=[CUPS-PRINT] OS=[UNIX] Server=[Samba 2.2.7a]
+NT_STATUS_OBJECT_NAME_COLLISION making remote directory \W32X86
+putting file /var/spool/cups/tmp/3e98bf2d333b5 as \W32X86/infotec_2105.ppd
+putting file /usr/share/cups/drivers/cupsdrvr.dll as \W32X86/cupsdrvr.dll
+putting file /usr/share/cups/drivers/cupsui.dll as \W32X86/cupsui.dll
+putting file /usr/share/cups/drivers/cups.hlp as \W32X86/cups.hlp
   
-  Running command: rpcclient localhost -N -U'root%secret' -c 'adddriver "Windows NT x86"   \
-                   "infotec_2105:cupsdrvr.dll:infotec_2105.ppd:cupsui.dll:cups.hlp:NULL:   \
-                   RAW:NULL"'
-  cmd = adddriver "Windows NT x86" "infotec_2105:cupsdrvr.dll:infotec_2105.ppd:cupsui.dll: \
-                   cups.hlp:NULL:RAW:NULL"
-  Printer Driver infotec_2105 successfully installed.
+Running command: rpcclient localhost -N -U'root%secret' 
+   -c 'adddriver "Windows NT x86"   \
+   "infotec_2105:cupsdrvr.dll:infotec_2105.ppd:cupsui.dll:cups.hlp:NULL:   \
+    RAW:NULL"'
+cmd = adddriver "Windows NT x86" \
+    "infotec_2105:cupsdrvr.dll:infotec_2105.ppd:cupsui.dll:cups.hlp:NULL:RAW:NULL"
+Printer Driver infotec_2105 successfully installed.
   
-  Running command: smbclient //localhost/print\$ -N -U'root%secret' -c 'mkdir WIN40;put    \
-                   /var/spool/cups/tmp/3e98bf2d333b5 WIN40/infotec_2105.PPD; put           \
-                   /usr/share/cups/drivers/ADFONTS.MFM WIN40/ADFONTS.MFM;put               \
-                   /usr/share/cups/drivers/ADOBEPS4.DRV WIN40/ADOBEPS4.DRV;put             \
-                   /usr/share/cups/drivers/ADOBEPS4.HLP WIN40/ADOBEPS4.HLP;put             \
-                   /usr/share/cups/drivers/DEFPRTR2.PPD WIN40/DEFPRTR2.PPD;put             \
-                   /usr/share/cups/drivers/ICONLIB.DLL
-  WIN40/ICONLIB.DLL;put /usr/share/cups/drivers/PSMON.DLL WIN40/PSMON.DLL;'
+Running command: smbclient //localhost/print\$ -N -U'root%secret' \
+-c 'mkdir WIN40; \
+    put /var/spool/cups/tmp/3e98bf2d333b5 WIN40/infotec_2105.PPD; \
+	put /usr/share/cups/drivers/ADFONTS.MFM WIN40/ADFONTS.MFM;   \
+    put /usr/share/cups/drivers/ADOBEPS4.DRV WIN40/ADOBEPS4.DRV; \
+    put /usr/share/cups/drivers/ADOBEPS4.HLP WIN40/ADOBEPS4.HLP; \
+    put /usr/share/cups/drivers/DEFPRTR2.PPD WIN40/DEFPRTR2.PPD; \
+	put /usr/share/cups/drivers/ICONLIB.DLL WIN40/ICONLIB.DLL; \
+	put /usr/share/cups/drivers/PSMON.DLL WIN40/PSMON.DLL;'
   added interface ip=10.160.51.60 bcast=10.160.51.255 nmask=255.255.252.0
-  Domain=[CUPS-PRINT] OS=[Unix] Server=[Samba 2.2.7a]
+  Domain=[CUPS-PRINT] OS=[UNIX] Server=[Samba 2.2.7a]
   NT_STATUS_OBJECT_NAME_COLLISION making remote directory \WIN40
-  putting file /var/spool/cups/tmp/3e98bf2d333b5 as \WIN40/infotec_2105.PPD (2328.8 kb/s)  \
-               (average 2328.8 kb/s)
-  putting file /usr/share/cups/drivers/ADFONTS.MFM as \WIN40/ADFONTS.MFM (9368.0 kb/s)     \
-               (average 6469.6 kb/s)
-  putting file /usr/share/cups/drivers/ADOBEPS4.DRV as \WIN40/ADOBEPS4.DRV (9958.2 kb/s)   \
-               (average 8404.3 kb/s)
-  putting file /usr/share/cups/drivers/ADOBEPS4.HLP as \WIN40/ADOBEPS4.HLP (8341.5 kb/s)   \
-               (average 8398.6 kb/s)
-  putting file /usr/share/cups/drivers/DEFPRTR2.PPD as \WIN40/DEFPRTR2.PPD (2195.9 kb/s)   \
-               (average 8254.3 kb/s)
-  putting file /usr/share/cups/drivers/ICONLIB.DLL as \WIN40/ICONLIB.DLL (8239.9 kb/s)     \
-               (average 8253.6 kb/s)
-  putting file /usr/share/cups/drivers/PSMON.DLL as \WIN40/PSMON.DLL (6222.2 kb/s)         \
-               (average 8188.5 kb/s)
+  putting file /var/spool/cups/tmp/3e98bf2d333b5 as \WIN40/infotec_2105.PPD
+  putting file /usr/share/cups/drivers/ADFONTS.MFM as \WIN40/ADFONTS.MFM
+  putting file /usr/share/cups/drivers/ADOBEPS4.DRV as \WIN40/ADOBEPS4.DRV
+  putting file /usr/share/cups/drivers/ADOBEPS4.HLP as \WIN40/ADOBEPS4.HLP
+  putting file /usr/share/cups/drivers/DEFPRTR2.PPD as \WIN40/DEFPRTR2.PPD
+  putting file /usr/share/cups/drivers/ICONLIB.DLL as \WIN40/ICONLIB.DLL
+  putting file /usr/share/cups/drivers/PSMON.DLL as \WIN40/PSMON.DLL
   
-  Running command: rpcclient localhost -N -U'root%secret' -c 'adddriver "Windows 4.0"      \
-                   "infotec_2105:ADOBEPS4.DRV:infotec_2105.PPD:NULL:ADOBEPS4.HLP:          \
-                   PSMON.DLL:RAW:ADOBEPS4.DRV,infotec_2105.PPD,ADOBEPS4.HLP,PSMON.DLL,     \
-                   ADFONTS.MFM,DEFPRTR2.PPD,ICONLIB.DLL"'
+  Running command: rpcclient localhost -N -U'root%secret' \
+   -c 'adddriver "Windows 4.0"      \
+   "infotec_2105:ADOBEPS4.DRV:infotec_2105.PPD:NULL:ADOBEPS4.HLP: \
+   PSMON.DLL:RAW:ADOBEPS4.DRV,infotec_2105.PPD,ADOBEPS4.HLP,PSMON.DLL, \
+    ADFONTS.MFM,DEFPRTR2.PPD,ICONLIB.DLL"'
   cmd = adddriver "Windows 4.0" "infotec_2105:ADOBEPS4.DRV:infotec_2105.PPD:NULL:          \
-                   ADOBEPS4.HLP:PSMON.DLL:RAW:ADOBEPS4.DRV,infotec_2105.PPD,ADOBEPS4.HLP,  \
+    ADOBEPS4.HLP:PSMON.DLL:RAW:ADOBEPS4.DRV,infotec_2105.PPD,ADOBEPS4.HLP,  \
                    PSMON.DLL,ADFONTS.MFM,DEFPRTR2.PPD,ICONLIB.DLL"
   Printer Driver infotec_2105 successfully installed.
   
-  Running command: rpcclient localhost -N -U'root%secret'                                  \
-                             -c 'setdriver infotec_2105 infotec_2105'
+  Running command: rpcclient localhost -N -U'root%secret'  \
+   -c 'setdriver infotec_2105 infotec_2105'
   cmd = setdriver infotec_2105 infotec_2105
   Successfully set infotec_2105 to driver infotec_2105.

    -If you look closely, you'll discover your root password was transfered +If you look closely, you'll discover your root password was transferred unencrypted over the wire, so beware! Also, if you look further her, you'll discover error messages like NT_STATUS_OBJECT_NAME_COLLISION in between. They occur, because the directories WIN40 and W32X86 already existed in the [print$] driver download share (from a previous driver installation). They are harmless here. -

    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 +

      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 Win95/98/ME) and W32X86/ (for WinNT/2k/XP) sub - directories;

      4. connect via rpcclient to the Samba server and + directories;

      5. + + connect via rpcclient to the Samba server and execute the "adddriver" command with the correct -parameters;

      6. connect via rpcclient to the Samba server a second +parameters;

      7. + + connect via rpcclient to the Samba server a second time and execute the "setdriver" command.

      Note, that you can run the cupsaddsmb utility with parameters to specify one remote host as Samba host and a second remote host as CUPS @@ -1878,10 +1731,8 @@ good idea try it and see more clearly what is going on (though in real life most people will have their CUPS and Samba servers run on the same host): 

      -
- # cupsaddsmb -H sambaserver -h cupsserver -v printername
-
-

    How to recognize if cupsaddsm completed successfully

    +root# cupsaddsmb -H sambaserver -h cupsserver -v printername +

    How to recognize if cupsaddsmb completed successfully

    You must always check if the utility completed successfully in all fields. You need as a minimum these 3 messages amongst the output: @@ -1892,7 +1743,7 @@ installed. # (for the WIN40 == Win9x/ME architecture...)

  • Successfully set [printerXPZ] to driver [printerXYZ].

    • These messages probably not easily recognized in the general -output. If you run cupsaddsmb with the -a +output. If you run cupsaddsmb with the -a parameter (which tries to prepare all active CUPS printer drivers for download), you might miss if individual printers drivers had problems to install properly. Here a redirection of the @@ -1902,32 +1753,30 @@ It is impossible to see any diagnostic output if you don't run cupsaddsmb in verbose mode. Therefore we strongly recommend to not use the default quiet mode. It will hide any problems from you which might occur. -

    cupsaddsmb with a Samba PDC

    +

    cupsaddsmb with a Samba PDC

    You can't get the standard cupsaddsmb command to run on a Samba PDC? You are asked for the password credential all over again and again and the command just will not take off at all? Try one of these variations: 

    -
- # cupsaddsmb -U DOMAINNAME\\root -v printername
- # cupsaddsmb -H SAMBA-PDC -U DOMAINNAME\\root -v printername
- # cupsaddsmb -H SAMBA-PDC -U DOMAINNAME\\root -h cups-server -v printername
-
+root# cupsaddsmb -U MIDEARTH\\root -v printername
+root# cupsaddsmb -H SAURON -U MIDEARTH\\root -v printername
+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

    Here is a chart about the procedures, commandflows and dataflows of the "cupaddsmb" command. Note again: cupsaddsmb is not intended to, and does not work with, "raw" queues!

    -

    Figure 19.14. cupsaddsmb flowchart

    cupsaddsmb flowchart

    -

    Installing the PostScript Driver on a Client

    +

    Figure 19.16. cupsaddsmb flowchart

    cupsaddsmb flowchart

    +

    Installing the PostScript Driver on a Client

    After cupsaddsmb 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 +

      • open the Printers share of Samba in Network Neighbourhood;

      • right-click on the printer in question;

      • from the opening context-menu select Install... or @@ -1942,6 +1791,7 @@ an application like Winword, the new printer will appears in a \\SambaServer\PrinterName entry in the dropdown list of available printers.

        Note

        + cupsaddsmb will only reliably work with CUPS version 1.1.15 or higher and Samba from 2.2.4. If it doesn't work, or if the automatic printer driver download to the clients doesn't succeed, you can still manually @@ -1949,16 +1799,14 @@ install the CUPS printer PPD on top of the Adobe PostScript driver on clients. Then point the client's printer queue to the Samba printer share for a UNC type of connection: 

        -
-  net use lpt1: \\sambaserver\printershare /user:ntadmin
-
+C:\> net use lpt1: \\sambaserver\printershare /user:ntadmin

        should you desire to use the CUPS networked PostScript RIP functions. (Note that user "ntadmin" needs to be a valid Samba user with the required privileges to access the printershare) This would set up the printer connection in the traditional LanMan way (not using MS-RPC). -

      Avoiding critical PostScript Driver Settings on the +

      Avoiding critical PostScript Driver Settings on the Client

      Soooo: printing works, but there are still problems. Most jobs print well, some don't print at all. Some jobs have problems with fonts, @@ -1984,7 +1832,7 @@ get a printout at all) (Adobe)

    • Sometimes you can choose : 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 +Error Handler (Adobe)

    Installing PostScript Driver Files manually (using rpcclient)

    Of course you can run all the commands which are embedded into the cupsaddsmb convenience utility yourself, one by one, and hereby upload @@ -1992,9 +1840,18 @@ and prepare the driver files for future client downloads.

    1. prepare Samba (a CUPS printqueue 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 + [print$]

    5. + + run rpcclient adddriver +(for each client architecture you want to support):

    6. + + 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 sub-commands. enumprinters, @@ -2005,7 +1862,7 @@ the MS-RPC protocol. You can use it to query (and command) a Win NT (or 2K/XP) PC too. MS-RPC is used by Windows clients, amongst other things, to benefit from the "Point'n'Print" features. Samba can now mimic this too. -

    A Check of the rpcclient man Page

    +

    A Check of the rpcclient man Page

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

    @@ -2038,18 +1895,16 @@ 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 for obtaining 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 linebreaks: -

    -
+
      adddriver "Architecture" \
            "LongPrinterName:DriverFile:DataFile:ConfigFile:HelpFile:\
            LanguageMonitorFile:DataType:ListOfFiles,Comma-separated"
-
 
    
 What the man pages denotes as a simple <config>
 keyword, does in reality consist of 8 colon-separated fields. The
@@ -2074,22 +1929,22 @@ 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 which we've read just
 now.
-

    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 UNIX or Linux workstation with the Samba utilities installed. Then type the following command: 

    -
- rpcclient -U'USERNAME%PASSWORD' NT-SERVER-NAME -c 'getdriver printername 3'
-
+root# rpcclient -U'USERNAME%PASSWORD' NT-SERVER-NAME -c 'getdriver printername 3'

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

    -
-# rpcclient -U'Danka%xxxx' W2KSERVER -c'getdriver "DANKA InfoStream Virtual Printer" 3'
+
    +root# rpcclient -U'Danka%xxxx' W2KSERVER \
+	-c'getdriver "DANKA InfoStream Virtual Printer" 3'
  cmd = getdriver "DANKA InfoStream Virtual Printer" 3
 
  [Windows NT x86]
@@ -2119,15 +1974,16 @@ Some printer drivers list additional files under the label
 ListOfFiles,Comma-separated. For the CUPS
 PostScript drivers we don't need any (nor would we for the Adobe
 PostScript driver): therefore the field will get a "NULL" entry.
-

    What is required for adddriver and setdriver to succeed

    +

    What is required for adddriver and setdriver to succeed

    From the manpage (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 setdriver) need to encounter the following pre-conditions to complete successfully: -

    • you are connected as "printer admin", or root (note, +

      • you are connected as printer admin, or root (note, that this is not the "Printer Operators" group in NT, but the printer admin group, as defined in the [global] section of @@ -2142,7 +1998,10 @@ to escape the "$": smbclient //sambaserver/print\$ root);

      • the user you're connecting as must be able to write to the [print$] share and create subdirectories;

      • the printer you are going to setup for the Windows -clients, needs to be installed in CUPS already;

      • the CUPS printer must be known to Samba, otherwise the +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 @@ -2150,30 +2009,25 @@ 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 shortly ago and encounter problems: try restarting -Samba.

    Manual Commandline Driver Installation in 15 little Steps

    +Samba.

    Manual Driver Installation in 15 Steps

    We are going to install a printer driver now by manually executing all required commands. As 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. -

    First Step: Install the Printer on CUPS

    -
-# lpadmin -p mysmbtstprn -v socket://10.160.51.131:9100 -E -P /home/kurt/canonIR85.ppd
-
+
    Procedure 19.1. Manual Driver Installation installation
    1. Install the Printer on CUPS
      +root# lpadmin -p mysmbtstprn -v socket://10.160.51.131:9100 -E -P canonIR85.ppd
 
      
 This installs printer with the name mysmbtstprn
 to the CUPS system. The printer is accessed via a socket
 (a.k.a. JetDirect or Direct TCP/IP) connection. You need to be root
 for this step
-
    Second Step (optional): Check if the Printer is recognized by
-Samba
    -
- # rpcclient -Uroot%xxxx -c 'enumprinters' localhost | grep -C2 mysmbtstprn
-
-        flags:[0x800000]
-        name:[\\kde-bitshop\mysmbtstprn]
-        description:[\\kde-bitshop\mysmbtstprn,,mysmbtstprn]
-        comment:[mysmbtstprn]
-
+
  • (optional) Check if the Printer is recognized by
+Samba
    +root# rpcclient -Uroot%xxxx -c 'enumprinters' localhost | grep -C2 mysmbtstprn
+flags:[0x800000]
+name:[\\kde-bitshop\mysmbtstprn]
+description:[\\kde-bitshop\mysmbtstprn,,mysmbtstprn]
+comment:[mysmbtstprn]
 
    
 This should show the printer in the list. If not, stop and re-start
 the Samba daemon (smbd), or send a HUP signal: kill -HUP
@@ -2185,24 +2039,25 @@ already. You need to know root's Samba password (as set by the
 following steps. Alternatively you can authenticate as one of the
 users from the "write list" as defined in smb.conf for
 [print$].
-
    • Third Step (optional): Check if Samba knows a Driver for the
-Printer
    -
-#  rpcclient -Uroot%xxxx -c 'getprinter mysmbtstprn 2' localhost | grep driver
-         drivername:[]
+
  • (optional) Check if Samba knows a Driver for the
+Printer
    +root# rpcclient -Uroot%xxxx -c 'getprinter mysmbtstprn 2' localhost \
+			| grep driver 
+drivername:[]
+
+root# rpcclient -Uroot%xxxx -c 'getprinter mysmbtstprn 2' localhost \
+	| grep -C4 driv
+servername:[\\kde-bitshop]
+printername:[\\kde-bitshop\mysmbtstprn]
+sharename:[mysmbtstprn]
+portname:[Samba Printer Port]
+drivername:[]
+comment:[mysmbtstprn]
+location:[]
+sepfile:[]
+printprocessor:[winprint]
  
-#  rpcclient -Uroot%xxxx -c 'getprinter mysmbtstprn 2' localhost | grep -C4 driv
-        servername:[\\kde-bitshop]
-        printername:[\\kde-bitshop\mysmbtstprn]
-        sharename:[mysmbtstprn]
-        portname:[Samba Printer Port]
-        drivername:[]
-        comment:[mysmbtstprn]
-        location:[]
-        sepfile:[]
-        printprocessor:[winprint]
- 
-#  rpcclient -U root%xxxx -c 'getdriver mysmbtstprn' localhost
+root# rpcclient -U root%xxxx -c 'getdriver mysmbtstprn' localhost
  result was WERR_UNKNOWN_PRINTER_DRIVER
 
 
    
@@ -2211,16 +2066,14 @@ This step was done for the purpose of demonstrating this condition. An
 attempt to connect to the printer at this stage will prompt the
 message along the lines: "The server has not the required printer
 driver installed".
-
    • Fourth Step: Put all required Driver Files into Samba's
-[print$]
    -
-#  smbclient //localhost/print\$ -U 'root%xxxx'                        \ 
-                              -c 'cd W32X86;                                             \
-                                  put /etc/cups/ppd/mysmbtstprn.ppd mysmbtstprn.PPD;     \
-                                  put /usr/share/cups/drivers/cupsui.dll cupsui.dll;     \
-                                  put /usr/share/cups/drivers/cupsdrvr.dll cupsdrvr.dll; \
-                                  put /usr/share/cups/drivers/cups.hlp cups.hlp'
-
+
  • Put all required Driver Files into Samba's
+[print$]
    +root# smbclient //localhost/print\$ -U 'root%xxxx' \
+	-c 'cd W32X86; \
+	put /etc/cups/ppd/mysmbtstprn.ppd mysmbtstprn.PPD; \ 
+	put /usr/share/cups/drivers/cupsui.dll cupsui.dll; \
+	put /usr/share/cups/drivers/cupsdrvr.dll cupsdrvr.dll; \
+	put /usr/share/cups/drivers/cups.hlp cups.hlp'
 
    
 (Note that this command should be entered in one long single
 line. Line-breaks and the line-end indicating "\" has been inserted
@@ -2230,31 +2083,26 @@ present in the [print$] share. However, client
 would still not be able to install them, because Samba does not yet
 treat them as driver files. A client asking for the driver would still
 be presented with a "not installed here" message.
-
    • Fifth Step: Verify where the Driver Files are now
    -
-#  ls -l /etc/samba/drivers/W32X86/
- total 669
- drwxr-sr-x    2 root     ntadmin       532 May 25 23:08 2
- drwxr-sr-x    2 root     ntadmin       670 May 16 03:15 3
- -rwxr--r--    1 root     ntadmin     14234 May 25 23:21 cups.hlp
- -rwxr--r--    1 root     ntadmin    278380 May 25 23:21 cupsdrvr.dll
- -rwxr--r--    1 root     ntadmin    215848 May 25 23:21 cupsui.dll
- -rwxr--r--    1 root     ntadmin    169458 May 25 23:21 mysmbtstprn.PPD
-
+
  • Verify where the Driver Files are now
    +root# ls -l /etc/samba/drivers/W32X86/
+total 669
+drwxr-sr-x    2 root     ntadmin       532 May 25 23:08 2
+drwxr-sr-x    2 root     ntadmin       670 May 16 03:15 3
+-rwxr--r--    1 root     ntadmin     14234 May 25 23:21 cups.hlp
+-rwxr--r--    1 root     ntadmin    278380 May 25 23:21 cupsdrvr.dll
+-rwxr--r--    1 root     ntadmin    215848 May 25 23:21 cupsui.dll
+-rwxr--r--    1 root     ntadmin    169458 May 25 23:21 mysmbtstprn.PPD
 
    
 The driver files now are in the W32X86 architecture "root" of
 [print$].
-
    • Sixth Step: Tell Samba that these are
+
  • Tell Samba that these are
 Driver Files
-(adddriver)
    • -
-#  rpcclient -Uroot%xxxx -c `adddriver "Windows NT x86" "mydrivername: \
-                                          cupsdrvr.dll:mysmbtstprn.PPD:                  \
-                                          cupsui.dll:cups.hlp:NULL:RAW[:]NULL"             \
-                                          localhost
-
- Printer Driver mydrivername successfully installed.
-
+(adddriver)
    +root# rpcclient -Uroot%xxxx -c `adddriver "Windows NT x86" "mydrivername: \
+  cupsdrvr.dll:mysmbtstprn.PPD: \
+  cupsui.dll:cups.hlp:NULL:RAW:NULL" \
+  localhost
+Printer Driver mydrivername successfully installed.
 
    
 Note that your cannot repeat this step if it fails. It could fail even
 as a result of a simple typo. It will most likely have moved a part of
@@ -2265,49 +2113,41 @@ driver. It is normally a good idea to use the same name as is used for
 the printername; however, in big installations you may use this driver
 for a number of printers which have obviously different names. So the
 name of the driver is not fixed.
-
    Seventh Step: Verify where the Driver Files are now
    -
-#  ls -l /etc/samba/drivers/W32X86/
- total 1
- drwxr-sr-x    2 root     ntadmin       532 May 25 23:22 2
- drwxr-sr-x    2 root     ntadmin       670 May 16 03:15 3
-
- 
-#  ls -l /etc/samba/drivers/W32X86/2
- total 5039
- [....]
- -rwxr--r--    1 root     ntadmin     14234 May 25 23:21 cups.hlp
- -rwxr--r--    1 root     ntadmin    278380 May 13 13:53 cupsdrvr.dll
- -rwxr--r--    1 root     ntadmin    215848 May 13 13:53 cupsui.dll
- -rwxr--r--    1 root     ntadmin    169458 May 25 23:21 mysmbtstprn.PPD
-
+
  • Verify where the Driver Files are now
    +root# ls -l /etc/samba/drivers/W32X86/
+total 1
+drwxr-sr-x    2 root     ntadmin       532 May 25 23:22 2
+drwxr-sr-x    2 root     ntadmin       670 May 16 03:15 3
+
+root# ls -l /etc/samba/drivers/W32X86/2
+total 5039
+[....]
+-rwxr--r--    1 root     ntadmin     14234 May 25 23:21 cups.hlp
+-rwxr--r--    1 root     ntadmin    278380 May 13 13:53 cupsdrvr.dll
+-rwxr--r--    1 root     ntadmin    215848 May 13 13:53 cupsui.dll
+-rwxr--r--    1 root     ntadmin    169458 May 25 23:21 mysmbtstprn.PPD
 
    
 Notice how step 6 did also move the driver files to the appropriate
 subdirectory. Compare with the situation after step 5.
-
    • Eighth Step (optional): Verify if Samba now recognizes the
-Driver
    -
-#  rpcclient -Uroot%xxxx -c 'enumdrivers 3' localhost | grep -B2 -A5 mydrivername
-
- Printer Driver Info 3:
-        Version: [2]
-        Driver Name: [mydrivername]
-        Architecture: [Windows NT x86]
-        Driver Path: [\\kde-bitshop\print$\W32X86\2\cupsdrvr.dll]
-        Datafile: [\\kde-bitshop\print$\W32X86\2\mysmbtstprn.PPD]
-        Configfile: [\\kde-bitshop\print$\W32X86\2\cupsui.dll]
-        Helpfile: [\\kde-bitshop\print$\W32X86\2\cups.hlp]
-
+
  • (optional) Verify if Samba now recognizes the
+Driver
    +root# rpcclient -Uroot%xxxx -c 'enumdrivers 3' localhost \
+	| grep -B2 -A5 mydrivername
+Printer Driver Info 3:
+Version: [2]
+Driver Name: [mydrivername]
+Architecture: [Windows NT x86]
+Driver Path: [\\kde-bitshop\print$\W32X86\2\cupsdrvr.dll]
+Datafile: [\\kde-bitshop\print$\W32X86\2\mysmbtstprn.PPD]
+Configfile: [\\kde-bitshop\print$\W32X86\2\cupsui.dll]
+Helpfile: [\\kde-bitshop\print$\W32X86\2\cups.hlp]
 
    
 Remember, this command greps for the name you did choose for the
 driver in step Six. This command must succeed before you can proceed.
-
    • Ninth Step: Tell Samba which Printer should use these Driver
-Files (setdriver)
    -
-#  rpcclient -Uroot%xxxx -c 'setdriver mysmbtstprn mydrivername' localhost
- 
- Successfully set mysmbtstprn to driver mydrivername
-
+
  • Tell Samba which Printer should use these Driver
+Files (setdriver)
    +root# rpcclient -Uroot%xxxx -c 'setdriver mysmbtstprn mydrivername' localhost
+Successfully set mysmbtstprn to driver mydrivername
 
    
 Since you can bind any printername (=printqueue) to any driver, this
 is a very convenient way to setup many queues which use the same
@@ -2315,50 +2155,53 @@ driver. You don't need to repeat all the previous steps for the
 setdriver command to succeed. The only pre-conditions are:
 enumdrivers must find the driver and
 enumprinters must find the printer.
-
    • Tenth Step (optional): Verify if Samba has this Association
-recognized
    -
-#  rpcclient -Uroot%xxxx -c 'getprinter mysmbtstprn 2' localhost | grep driver
-       drivername:[mydrivername]
+
  • (optional) Verify if Samba has this Association
+recognized
    +root# rpcclient -Uroot%xxxx -c 'getprinter mysmbtstprn 2' localhost \
+  | grep driver
+drivername:[mydrivername]
  
-#  rpcclient -Uroot%xxxx -c 'getprinter mysmbtstprn 2' localhost | grep -C4 driv
-       servername:[\\kde-bitshop]
-       printername:[\\kde-bitshop\mysmbtstprn]
-       sharename:[mysmbtstprn]
-       portname:[Done]
-       drivername:[mydrivername]
-       comment:[mysmbtstprn]
-       location:[]
-       sepfile:[]
-       printprocessor:[winprint]
+root# rpcclient -Uroot%xxxx -c 'getprinter mysmbtstprn 2' localhost \
+  | grep -C4 driv
+servername:[\\kde-bitshop]
+printername:[\\kde-bitshop\mysmbtstprn]
+sharename:[mysmbtstprn]
+portname:[Done]
+drivername:[mydrivername]
+comment:[mysmbtstprn]
+location:[]
+sepfile:[]
+printprocessor:[winprint]
  
-#  rpcclient -U root%xxxx -c 'getdriver mysmbtstprn' localhost
- [Windows NT x86]
- Printer Driver Info 3:
-       Version: [2]
-       Driver Name: [mydrivername]
-       Architecture: [Windows NT x86]
-       Driver Path: [\\kde-bitshop\print$\W32X86\2\cupsdrvr.dll]
-       Datafile: [\\kde-bitshop\print$\W32X86\2\mysmbtstprn.PPD]
-       Configfile: [\\kde-bitshop\print$\W32X86\2\cupsui.dll]
-       Helpfile: [\\kde-bitshop\print$\W32X86\2\cups.hlp]
-       Monitorname: []
-       Defaultdatatype: [RAW]
-       Monitorname: []
-       Defaultdatatype: [RAW]
+root# rpcclient -U root%xxxx -c 'getdriver mysmbtstprn' localhost
+[Windows NT x86]
+Printer Driver Info 3:
+     Version: [2]
+     Driver Name: [mydrivername]
+     Architecture: [Windows NT x86]
+     Driver Path: [\\kde-bitshop\print$\W32X86\2\cupsdrvr.dll]
+     Datafile: [\\kde-bitshop\print$\W32X86\2\mysmbtstprn.PPD]
+     Configfile: [\\kde-bitshop\print$\W32X86\2\cupsui.dll]
+     Helpfile: [\\kde-bitshop\print$\W32X86\2\cups.hlp]
+     Monitorname: []
+     Defaultdatatype: [RAW]
+     Monitorname: []
+     Defaultdatatype: [RAW]
  
-#  rpcclient -Uroot%xxxx -c 'enumprinters' localhost | grep mysmbtstprn
-       name:[\\kde-bitshop\mysmbtstprn]
-       description:[\\kde-bitshop\mysmbtstprn,mydrivername,mysmbtstprn]
-       comment:[mysmbtstprn]
+root# rpcclient -Uroot%xxxx -c 'enumprinters' localhost | grep mysmbtstprn
+     name:[\\kde-bitshop\mysmbtstprn]
+     description:[\\kde-bitshop\mysmbtstprn,mydrivername,mysmbtstprn]
+     comment:[mysmbtstprn]
 
 
    
+
 Compare these results with the ones from steps 2 and 3. Note that
 every single of these commands show the driver is installed.  Even
 the enumprinters command now lists the driver
 on the "description" line.
-
    • Eleventh Step (optional): Tickle the Driver into a correct
-Device Mode
    
+
  • (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 Neighbourhood, go to the Samba server, look
@@ -2375,39 +2218,32 @@ It is important that you execute this step as a Samba printer admin
 to do this on Windows XP. It uses a commandline, which you may type
 into the "DOS box" (type root's smbpassword when prompted):
 
    -
- C:\> runas /netonly /user:root "rundll32 printui.dll,PrintUIEntry /in /n \\sambacupsserver\mysmbtstprn"
-
+C:\> runas /netonly /user:root "rundll32 printui.dll,PrintUIEntry /in /n\
+			\\sambacupsserver\mysmbtstprn"
 
    
-Change any printer setting once (like "portrait"
---> "landscape"), click "Apply"; change the setting
+Change any printer setting once (like changing "portrait" to
+	"landscape"), click Apply; change the setting
 back.
-
    • Twelfth Step: Install the Printer on a Client
-("Point'n'Print")
    -
- C:\> rundll32 printui.dll,PrintUIEntry /in /n "\\sambacupsserver\mysmbtstprn"
-
+
  • Install the Printer on a Client
+("Point'n'Print")
    +C:\> rundll32 printui.dll,PrintUIEntry /in /n "\\sambacupsserver\mysmbtstprn"
 
    
 If it doesn't work it could be a permission problem with the
 [print$] share.
-
    • Thirteenth Step (optional): Print a Test Page
    -
- C:\> rundll32 printui.dll,PrintUIEntry /p /n "\\sambacupsserver\mysmbtstprn"
-
+
  • Thirteenth Step (optional): Print a Test Page
    +C:\> rundll32 printui.dll,PrintUIEntry /p /n "\\sambacupsserver\mysmbtstprn"
 
    
 Then hit [TAB] 5 times, [ENTER] twice, [TAB] once and [ENTER] again
 and march to the printer.
-
    • Fourteenth Step (recommended): Study the Test Page
    
+
  • Fourteenth Step (recommended): Study the Test Page
    
 Hmmm.... just kidding! By now you know everything about printer
 installations and you don't need to read a word. Just put it in a
 frame and bolt it to the wall with the heading "MY FIRST
 RPCCLIENT-INSTALLED PRINTER" - why not just throw it away!
-
    • Fifteenth Step (obligatory): Enjoy. Jump. Celebrate your
-Success
    -
-# echo "Cheeeeerioooooo! Success..." >> /var/log/samba/log.smbd     
-
-

    Troubleshooting revisited

    +

  • Fifteenth Step (obligatory): Enjoy. Jump. Celebrate your +Success

    +root# echo "Cheeeeerioooooo! Success..." >> /var/log/samba/log.smbd
+

    • Troubleshooting revisited

    The setdriver command will fail, if in Samba's mind the queue is not already there. You had promising messages about the: 

    @@ -2422,7 +2258,8 @@ a disappointing message like this one beneath?
  result was NT_STATUS_UNSUCCESSFUL

    -It is not good enough that you + +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 @@ -2431,26 +2268,35 @@ fails unless you re-start Samba or send a HUP to all smbd processes. To verify if this is the reason why Samba doesn't execute the setdriver command successfully, check if Samba "sees" the printer: -

    -
-# rpcclient transmeta -N -U'root%secret' -c 'enumprinters 0'| grep  ir85wm
+
    +root# rpcclient transmeta -N -U'root%secret' -c 'enumprinters 0'| grep  ir85wm
         printername:[ir85wm]
-
 
    
 An alternative command could be this: 
-
    -
-# rpcclient transmeta -N -U'root%secret' -c 'getprinter ir85wm' 
+
    +root# rpcclient transmeta -N -U'root%secret' -c 'getprinter ir85wm' 
         cmd = getprinter ir85wm
         flags:[0x800000]
         name:[\\transmeta\ir85wm]
         description:[\\transmeta\ir85wm,ir85wm,DPD]
         comment:[CUPS PostScript-Treiber for WinNT/2K/XP]
-
 
    
 BTW, 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, @@ -2465,12 +2311,12 @@ tdb-suffix appearing in every Samba installation. They are 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 are saved by writing into -the Registry. Samba and Unix obviously don't have such a kind of +the Registry. Samba and UNIX obviously don't have such a kind of Registry. Samba instead keeps track of all client related information in a series of *.tdb files. (TDB = Trivial Data Base). These are often located in /var/lib/samba/ @@ -2478,7 +2324,7 @@ 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 proofed tradition on UNIX." @@ -2491,7 +2337,7 @@ 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 @@ -2501,13 +2347,12 @@ etc.). In cases of trouble, a deletion of the old printing-related *.tdb files may be the only option. You need to re-create all print related setup after that. Or you have made a backup of the *.tdb files in time. -

    Using tdbbackup

    +

    Using tdbbackup

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

    -
-# tdbbackup
+root# tdbbackup
  Usage: tdbbackup [options] <fname...>
  
  Version:3.0a
@@ -2518,32 +2363,30 @@ with no argument, it prints a little usage message:

    Here is how I backed up my printing.tdb file: 

    -
-# ls 
- .           browse.dat       locking.tdb     ntdrivers.tdb   printing.tdb    share_info.tdb
- ..          connections.tdb  messages.tdb    ntforms.tdb     printing.tdbkp  unexpected.tdb
- brlock.tdb  gmon.out         namelist.debug  ntprinters.tdb  sessionid.tdb
+root# ls
+.              browse.dat       locking.tdb     ntdrivers.tdb   printing.tdb
+..             share_info.tdb   connections.tdb messages.tdb    ntforms.tdb
+printing.tdbkp unexpected.tdb   brlock.tdb      gmon.out        namelist.debug  
+ntprinters.tdb sessionid.tdb
  
- kde-bitshop:/var/lock/samba # tdbbackup -s .bak printing.tdb
+root# tdbbackup -s .bak printing.tdb
  printing.tdb : 135 records
  
- kde-bitshop:/var/lock/samba # ls -l printing.tdb*
+root# ls -l printing.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: -

    -
-lpadmin -p laserjet4plus -v parallel:/dev/lp0 -E -m laserjet.ppd
-
+
    +root# lpadmin -p laserjet4plus -v parallel:/dev/lp0 -E -m laserjet.ppd
 
    
-The -m switch will retrieve the
+The -m switch will retrieve the
 laserjet.ppd from the standard repository for
 not-yet-installed-PPDs, which CUPS typically stores in
 /usr/share/cups/model. Alternatively, you may use
--P /path/to/your.ppd.
+-P /path/to/your.ppd.
 
    
 The generic laserjet.ppd however does not support every special option
 for every LaserJet-compatible model. It constitutes a sort of "least
@@ -2555,6 +2398,7 @@ best used for each printer. Its database is kept current by 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 be replaced by the new, much
 more powerful "foomatic-rip". foomatic-rip is the successor of
 cupsomatic. cupsomatic is no longer maintained. Here is the new URL
@@ -2565,7 +2409,7 @@ not work with PPDs generated for the old cupsomatic. The new-style
 PPDs are 100% compliant to the Adobe PPD specification. They are
 intended to be used by Samba and the cupsaddsmb utility also, to
 provide the driver files for the Windows clients also!
-
    foomatic-rip and Foomatic explained
    
+
    foomatic-rip and Foomatic explained
    
 Nowadays most Linux distros rely on the utilities of Linuxprinting.org
 to create their printing related software (which, BTW, works on all
 UNIXes and on Mac OS X or Darwin too). It is not known as well as it
@@ -2582,7 +2426,7 @@ its Foomatic<
 database. Currently there are 245 drivers
 in the database: many drivers support various models, and many models
 may be driven by different drivers; it's your choice!
-
    690 "perfect" Printers
    
+
    690 "perfect" Printers
    
 At present there are 690 devices dubbed as working "perfectly", 181
 "mostly", 96 "partially" and 46 are "Paperweights". Keeping in mind
 that most of these are non-PostScript models (PostScript printers are
@@ -2593,7 +2437,7 @@ doesn't 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
@@ -2607,7 +2451,7 @@ 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"
@@ -2630,7 +2474,7 @@ developments available for CUPS;
  • It made available a lot of addit
 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
@@ -2664,8 +2508,8 @@ Foomatic up to versions 2.0.x required (ugly) Perl data structures
 attached the Linuxprinting.org PPDs for CUPS. It had a different
 "*omatic" script for every spooler, as well as different printer
 configuration files..
-
    7.13.1.5.The Grand Unification
-achieved...
    
+
    The Grand Unification
+achieved...
    
 This all has changed in Foomatic versions 2.9 (Beta) and released as
 "stable" 3.0. This has now achieved the convergence of all *omatic
 scripts: it is called the foomatic-rip.
@@ -2700,7 +2544,7 @@ sizes for many printers; and it 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
@@ -2713,7 +2557,7 @@ the work is currently done in three projects. These are:
 
    • Omni
 -- a Free Software project by IBM which tries to convert their printer
 driver knowledge from good-ol' OS/2 times into a modern, modular,
-universal driver architecture for Linux/Unix (still Beta).  This
+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 their own
 range of models (very mature, printing in most cases is perfect and
@@ -2723,8 +2567,8 @@ 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. But @@ -2744,7 +2588,7 @@ of the Foomatic project. 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 @@ -2769,7 +2613,7 @@ GUI tools (like KDE's marvellous "gtklp", "xpp" and the CUPS web interface) read the PPD too 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 @@ -2783,11 +2627,11 @@ link.

  • You'll arrive at a page listing all drivers working with this model (for all printers, there will always be one recommended driver. Try this one first).

  • In our case ("HP LaserJet 4 Plus"), we'll arrive here: -http://www.linuxprinting.org/show_printer.cgi?recnum=HP-LaserJet_4_Plus + http://www.linuxprinting.org/show_printer.cgi?recnum=HP-LaserJet_4_Plus

  • The recommended driver is "ljet4".

  • There are several links provided here. You should visit them all, if you are not familiar with the Linuxprinting.org database.

  • There is a link to the database page for the "ljet4": -http://www.linuxprinting.org/show_driver.cgi?driver=ljet4 + http://www.linuxprinting.org/show_driver.cgi?driver=ljet4 On the driver's page, you'll find important and detailed information about how to use that driver within the various available spoolers.

  • Another link may lead you to the homepage of the @@ -2828,9 +2672,7 @@ the /usr/share/cups/model/ path and re-start cupsd).

  • Then install the printer with a suitable commandline, e.g.: 

    -
-lpadmin -p laserjet4plus -v parallel:/dev/lp0 -E -P path/to/my-printer.ppd
-
+root# lpadmin -p laserjet4plus -v parallel:/dev/lp0 -E -P path/to/my-printer.ppd

  • Note again this: for all the new-style "Foomatic-PPDs" from Linuxprinting.org, you also need a special "CUPS filter" named "foomatic-rip".Get the latest version of "foomatic-rip" from: http://www.linuxprinting.org/foomatic2.9/download.cgi?filename=foomatic-rip&show=0 @@ -2868,7 +2710,7 @@ 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 don't work with -foomatic-rip).

    • Page Accounting with CUPS

    +foomatic-rip).

    Page Accounting with CUPS

    Often there are questions regarding "print quotas" wherein Samba users (that is, Windows clients) should not be able to print beyond a certain amount of pages or data volume per day, week or month. This @@ -2881,18 +2723,17 @@ Of course one could "hack" things with one's own scripts. But then there is CUPS. CUPS supports "quotas" which can be based on sizes of jobs or on the number of pages or both, and are spanning any time period you want. -

    Setting up Quotas

    +

    Setting up Quotas

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

    -
-  lpadmin -p quotaprinter -o job-quota-period=604800 -o job-k-limit=1024 -o job-page-limit=100
-
+
    +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 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 "1". Some printfiles don't pass it (eg: image files) but then those are mostly 1 @@ -2906,8 +2747,8 @@ driver there) to have the chance to get 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 will be working for currently about 1,000 different printer models, -see http://www.linuxprinting.org/printer_list.cgi). -

    Adobe and CUPS PostScript Drivers for Windows Clients

    +see the driver list at linuxprinting.org/. +

    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 @@ -2920,14 +2761,14 @@ From CUPS-1.1.16 onward you can use the "CUPS PostScript Driver for Windows NT/2K/XP 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 Win9x/ME clients. But it guarantees: -

    • to not write an PJL-header

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

      • to not write an 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 printfile

      You can read more about the setup of this combination in the manpage 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 single page of a job:

    • Printer name

    • User name

    • Job ID

    • Time of printing

    • the page number

    • the number of copies

    • a billing information string @@ -2936,20 +2777,18 @@ single page of a job: Here is an extract of my CUPS server's page_log file to illustrate the format and included items: 

      -
-        infotec_IS2027 kurt 401 [22/Apr/2003:10:28:43 +0100] 1 3 #marketing 10.160.50.13
-        infotec_IS2027 kurt 401 [22/Apr/2003:10:28:43 +0100] 2 3 #marketing 10.160.50.13
-        infotec_IS2027 kurt 401 [22/Apr/2003:10:28:43 +0100] 3 3 #marketing 10.160.50.13
-        infotec_IS2027 kurt 401 [22/Apr/2003:10:28:43 +0100] 4 3 #marketing 10.160.50.13
-        DigiMaster9110 boss 402 [22/Apr/2003:10:33:22 +0100] 1 440 finance-dep 10.160.51.33
-
+infotec_IS2027 kurt 401 [22/Apr/2003:10:28:43 +0100] 1 3 #marketing 10.160.50.13
+infotec_IS2027 kurt 401 [22/Apr/2003:10:28:43 +0100] 2 3 #marketing 10.160.50.13
+infotec_IS2027 kurt 401 [22/Apr/2003:10:28:43 +0100] 3 3 #marketing 10.160.50.13
+infotec_IS2027 kurt 401 [22/Apr/2003:10:28:43 +0100] 4 3 #marketing 10.160.50.13
+DigiMaster9110 boss 402 [22/Apr/2003:10:33:22 +0100] 1 440 finance-dep 10.160.51.33

      This was job ID "401", printed on "infotec_IS2027" by user "kurt", a 64-page job printed in 3 copies and billed to "#marketing", sent from IP address 10.160.50.13. 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, etc.)

    • in reality, CUPS counts the job pages that are being @@ -2958,12 +2797,12 @@ processed in software (that is, going thr printing device. Thus if there is a jam while printing the 5th sheet out of 1000 and the job is aborted by the printer, the "page count" will still show the figure of 1000 for that job

    • all quotas are the same for all users (no flexibility -to give the boss a higher quota than the clerk) no support for +to give the boss a higher quota than the clerk), no support for groups

    • no means to read out the current balance or the "used-up" number of current quota

    • a user having used up 99 sheets of 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 doesn't 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 @@ -2971,9 +2810,9 @@ directly to the printer and will increase the count in sync with the actual printing process: thus a jam at the 5th sheet will lead to a stop in the counting)

    • quotas will be handled more flexibly

    • probably there will be support for users to inquire 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

    PrintAnalyzer, pyKota, printbill, LogReport. -

    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" @@ -2994,10 +2833,8 @@ where "normally" the native CUPS "pstoraster" filter would k in. cupsomatic by-passes pstoraster, "kidnaps" the printfile from CUPS away and re-directs it to go through Ghostscript. CUPS accepts this, because the associated CUPS-O-Matic-/Foomatic-PPD specifies: -

    -
-   *cupsFilter:  "application/vnd.cups-postscript 0 cupsomatic"
-
+
    +  *cupsFilter:  "application/vnd.cups-postscript 0 cupsomatic"
 
    
 This line persuades CUPS to hand the file to cupsomatic, once it has
 successfully converted it to the MIME type
@@ -3009,30 +2846,24 @@ Jobs arriving from Windows which are auto-typed
 CUPS is widely configurable and flexible, even regarding its filtering
 mechanism. Another workaround in some situations would be to have in
 /etc/cups/mime.types entries as follows:
-
    -
-   application/postscript           application/vnd.cups-raw  0  -
-   application/vnd.cups-postscript  application/vnd.cups-raw  0  -
-
+
    + application/postscript           application/vnd.cups-raw  0  -
+ application/vnd.cups-postscript  application/vnd.cups-raw  0  -
 
    
 This would prevent all Postscript files from being filtered (rather,
 they will through the virtual nullfilter
 denoted with "-").  This could only be useful for PS printers. If you
 want to print PS code on non-PS printers (provided they support ASCII
 text printing) an entry as follows could be useful:
-
    -
-   */*           application/vnd.cups-raw  0  -
-
+
    + */*           application/vnd.cups-raw  0  -
 
    
 and would effectively send all files to the
 backend without further processing.
 
    
 Lastly, you could have the following entry:
-
    -
-   application/vnd.cups-postscript  application/vnd.cups-raw  0  my_PJL_stripping_filter
-
+
    +application/vnd.cups-postscript application/vnd.cups-raw 0 my_PJL_stripping_filter
 
    
 You will need to write a my_PJL_stripping_filter
 (could be a shellscript) that parses the PostScript and removes the
@@ -3051,16 +2882,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, etc.).
-

    Auto-Deletion or Preservation of CUPS Spool Files

    +

    Auto-Deletion 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 +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

    @@ -3084,34 +2914,32 @@ maximum to 0 disables this functionality. The default setting is

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

    Pre-conditions

    +

    Pre-conditions

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

    • a Samba-smbd which is compiled against "libcups" (Check on Linux by running "ldd `which smbd`")

    • a Samba-smb.conf setting of -"printing = cups"

    • another Samba-smb.conf setting of -"printcap = cups"

    Note

    + printing = cups

  • another Samba-smb.conf setting of + printcap = cups

    • Note

    In this case all other manually set printing-related commands (like -"print command", "lpq command", "lprm command", "lppause command" or -"lpresume command") are ignored and they should normally have no +print command, +lpq command, +lprm command, +lppause command or +lpresume command) are ignored and they should normally have no influence what-so-ever on your printing. -

    Manual Configuration

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

    Manual Configuration

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

    When not to use Samba to print to -CUPS

    -[TO BE DONE] -

    In Case of Trouble.....

    +

    In Case of Trouble.....

    If you have more problems, post the output of these commands to the CUPS or Samba mailing lists (choose the one which seems more relevant to your problem): 

    -
-   grep -v ^# /etc/cups/cupsd.conf | grep -v ^$
-   grep -v ^# /etc/samba/smb.conf | grep -v ^$ | grep -v "^;"
-
+$ grep -v ^# /etc/cups/cupsd.conf | grep -v ^$
+$ grep -v ^# /etc/samba/smb.conf | grep -v ^$ | grep -v "^;"

    (adapt paths as needed). These commands leave out the empty lines and lines with comments, providing the "naked settings" in a @@ -3119,18 +2947,12 @@ compact way. Don't forget to name the CUPS and Samba versions you are using! This saves bandwidth and makes for easier readability for experts (and you are expecting experts to read them, right? ;-) -

    Where to find Documentation

    -[TO BE DONE] -

    How to ask for Help

    -[TO BE DONE] -

    Where to find Help

    -[TO BE DONE] -

    Appendix

    Printing from CUPS to Windows attached -Printers

    +

    Printing from CUPS to Windows attached +Printers

    From time to time the question arises, how you can print to a Windows attached printer from Samba. Normally the local connection -"Windows host <--> printer" would be done by USB or parallel +from Windows host to printer would be done by USB or parallel cable, but this doesn't matter to Samba. From here only an SMB connection needs to be opened to the Windows host. Of course, this printer must be "shared" first. As you have learned by now, CUPS uses @@ -3142,33 +2964,29 @@ is in the CUPS backend directory. This resides usually in file there. It should be a symlink to smbspool which file must exist and be executable: 

    -
- # ls -l /usr/lib/cups/backend/   
- total 253
- drwxr-xr-x    3 root     root          720 Apr 30 19:04 .
- drwxr-xr-x    6 root     root          125 Dec 19 17:13 ..
- -rwxr-xr-x    1 root     root        10692 Feb 16 21:29 canon
- -rwxr-xr-x    1 root     root        10692 Feb 16 21:29 epson
- lrwxrwxrwx    1 root     root            3 Apr 17 22:50 http -> ipp
- -rwxr-xr-x    1 root     root        17316 Apr 17 22:50 ipp
- -rwxr-xr-x    1 root     root        15420 Apr 20 17:01 lpd
- -rwxr-xr-x    1 root     root         8656 Apr 20 17:01 parallel
- -rwxr-xr-x    1 root     root         2162 Mar 31 23:15 pdfdistiller
- lrwxrwxrwx    1 root     root           25 Apr 30 19:04 ptal -> /usr/local/sbin/ptal-cups
- -rwxr-xr-x    1 root     root         6284 Apr 20 17:01 scsi
- lrwxrwxrwx    1 root     root           17 Apr  2 03:11 smb -> /usr/bin/smbspool
- -rwxr-xr-x    1 root     root         7912 Apr 20 17:01 socket
- -rwxr-xr-x    1 root     root         9012 Apr 20 17:01 usb
-
-# ls -l `which smbspool`
- -rwxr-xr-x    1 root     root       563245 Dec 28 14:49 /usr/bin/smbspool
-
+root# ls -l /usr/lib/cups/backend/
+total 253
+drwxr-xr-x    3 root     root          720 Apr 30 19:04 .
+drwxr-xr-x    6 root     root          125 Dec 19 17:13 ..
+-rwxr-xr-x    1 root     root        10692 Feb 16 21:29 canon
+-rwxr-xr-x    1 root     root        10692 Feb 16 21:29 epson
+lrwxrwxrwx    1 root     root            3 Apr 17 22:50 http -> ipp
+-rwxr-xr-x    1 root     root        17316 Apr 17 22:50 ipp
+-rwxr-xr-x    1 root     root        15420 Apr 20 17:01 lpd
+-rwxr-xr-x    1 root     root         8656 Apr 20 17:01 parallel
+-rwxr-xr-x    1 root     root         2162 Mar 31 23:15 pdfdistiller
+lrwxrwxrwx    1 root     root           25 Apr 30 19:04 ptal -> /usr/sbin/ptal-cups
+-rwxr-xr-x    1 root     root         6284 Apr 20 17:01 scsi
+lrwxrwxrwx    1 root     root           17 Apr  2 03:11 smb -> /usr/bin/smbspool
+-rwxr-xr-x    1 root     root         7912 Apr 20 17:01 socket
+-rwxr-xr-x    1 root     root         9012 Apr 20 17:01 usb
+
+root# ls -l `which smbspool`
+-rwxr-xr-x    1 root     root       563245 Dec 28 14:49 /usr/bin/smbspool

    If this symlink doesn't exist, create it: 

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

    smbspool has been written by Mike Sweet from the CUPS folks. It is included and ships with Samba. It may also be used with print @@ -3185,9 +3003,8 @@ the Windows host, etc.

    To install a printer with the smb backend on CUPS, use this command: 

    -
-# lpadmin -p winprinter -v smb://WINDOWSNETBIOSNAME/printersharename -P /path/to/PPD
-
+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 @@ -3196,13 +3013,7 @@ 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 for: you can include the required parameters as part of the smb:// device-URI. Like this: -

    -
- smb://WORKGROUP/WINDOWSNETBIOSNAME/printersharename 
- smb://username:password@WORKGROUP/WINDOWSNETBIOSNAME/printersharename
- smb://username:password@WINDOWSNETBIOSNAME/printersharename
-
-

    +

    • smb://WORKGROUP/WINDOWSNETBIOSNAME/printersharename

    • smb://username:password@WORKGROUP/WINDOWSNETBIOSNAME/printersharename

    • smb://username:password@WINDOWSNETBIOSNAME/printersharename

    Note that the device-URI will be visible in the process list of the Samba server (e.g. when someone uses the ps -aux command on Linux), even if the username and passwords are sanitized @@ -3213,337 +3024,41 @@ doesn't require a password! 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 don't necessarily need to have smbd running (but who wants that? :-). -

    More CUPS filtering Chains

    +

    More CUPS filtering Chains

    The following diagrams reveal how CUPS handles print jobs. -

    -#########################################################################
-#
-# CUPS in and of itself has this (general) filter chain (CAPITAL
-# letters are FILE-FORMATS or MIME types, other are filters (this is
-# true for pre-1.1.15 of pre-4.3 versions of CUPS and ESP PrintPro):
-#
-# SOMETHNG-FILEFORMAT
-#      |
-#      V
-#     somethingtops
-#      |
-#      V
-# APPLICATION/POSTSCRIPT
-#      |
-#      V
-#     pstops
-#      |
-#      V
-# APPLICATION/VND.CUPS-POSTSCRIPT
-#      |
-#      V
-#     pstoraster   # as shipped with CUPS, independent from any Ghostscipt
-#      |           # installation on the system
-#      |  (= "postscipt interpreter")
-#      V
-# APPLICATION/VND.CUPS-RASTER
-#      |
-#      V
-#     rastertosomething  (e.g. Gimp-Print filters may be plugged in here)
-#      |   (= "raster driver")
-#      V
-# SOMETHING-DEVICE-SPECIFIC
-#      |
-#      V
-#     backend
-#
-#
-# ESP PrintPro has some enhanced "rastertosomething" filters as compared to
-# CUPS, and also a somewhat improved "pstoraster" filter.
-#
-# NOTE: Gimp-Print and some other 3rd-Party-Filters (like TurboPrint) to
-#       CUPS and ESP PrintPro plug-in where rastertosomething is noted.
-#
-#########################################################################
-
    -#########################################################################
-#
-# This is how "cupsomatic" comes into play:
-# =========================================
-#
-# SOMETHNG-FILEFORMAT
-#      |
-#      V
-#    somethingtops
-#      |
-#      V
-# APPLICATION/POSTSCRIPT
-#      |
-#      V
-#    pstops
-#      |
-#      V
-# APPLICATION/VND.CUPS-POSTSCRIPT ----------------+
-#      |                                          V
-#      V                                         cupsomatic
-#    pstoraster                                  (constructs complicated
-#      |  (= "postscipt interpreter")            Ghostscript commandline
-#      |                                         to let the file be
-#      V                                         processed by a
-# APPLICATION/VND.CUPS-RASTER                    "-sDEVICE=s.th."
-#      |                                         call...)
-#      V                                          |
-#    rastertosomething                            V
-#      |    (= "raster driver")     +-------------------------+
-#      |                            | Ghostscript at work.... |
-#      V                            |                         |
-# SOMETHING-DEVICE-SPECIFIC         *-------------------------+
-#      |                                          |
-#      V                                          |
-#    backend <------------------------------------+
-#      |
-#      V
-#    THE PRINTER
-#
-#
-# Note, that cupsomatic "kidnaps" the printfile after the
-# "APPLICATION/VND.CUPS-POSTSCRPT" stage and deviates it gh
-# the CUPS-external, systemwide Ghostscript installation, bypassing the
-# "pstoraster" filter (therefore also bypassing the CUPS-raster-drivers
-# "rastertosomething", and hands the rasterized file directly to the CUPS
-# backend...
-#
-# cupsomatic is not made by the CUPS developers. It is an independent
-# contribution to printing development, made by people from
-# Linuxprinting.org. (see also http://www.cups.org/cups-help.html)
-#
-# NOTE: Gimp-Print and some other 3rd-Party-Filters (like TurboPrint) to
-#       CUPS and ESP PrintPro plug-in where rastertosomething is noted.
-#
-#########################################################################
-
    -#########################################################################
-#
-# And this is how it works for ESP PrintPro from 4.3:
-# ===================================================
-#
-# SOMETHNG-FILEFORMAT
-#      |
-#      V
-#     somethingtops
-#      |
-#      V
-# APPLICATION/POSTSCRIPT
-#      |
-#      V
-#     pstops
-#      |
-#      V
-# APPLICATION/VND.CUPS-POSTSCRIPT
-#      |
-#      V
-#     gsrip
-#      |  (= "postscipt interpreter")
-#      V
-# APPLICATION/VND.CUPS-RASTER
-#      |
-#      V
-#     rastertosomething  (e.g. Gimp-Print filters may be plugged in here)
-#      |   (= "raster driver")
-#      V
-# SOMETHING-DEVICE-SPECIFIC
-#      |
-#      V
-#     backend
-#
-# NOTE: Gimp-Print and some other 3rd-Party-Filters (like TurboPrint) to
-#       CUPS and ESP PrintPro plug-in where rastertosomething is noted.
-#
-#########################################################################
-
    -#########################################################################
-#
-# This is how "cupsomatic" would come into play with ESP PrintPro:
-# ================================================================
-#
-#
-# SOMETHNG-FILEFORMAT
-#      |
-#      V
-#    somethingtops
-#      |
-#      V
-# APPLICATION/POSTSCRIPT
-#      |
-#      V
-#    pstops
-#      |
-#      V
-# APPLICATION/VND.CUPS-POSTSCRIPT ----------------+
-#      |                                          V
-#      V                                         cupsomatic
-#    gsrip                                       (constructs complicated
-#      |  (= "postscipt interpreter")            Ghostscript commandline
-#      |                                         to let the file be
-#      V                                         processed by a
-# APPLICATION/VND.CUPS-RASTER                    "-sDEVICE=s.th."
-#      |                                         call...)
-#      V                                          |
-#    rastertosomething                            V
-#      |   (= "raster driver")      +-------------------------+
-#      |                            | Ghostscript at work.... |
-#      V                            |                         |
-# SOMETHING-DEVICE-SPECIFIC         *-------------------------+
-#      |                                          |
-#      V                                          |
-#    backend <------------------------------------+
-#      |
-#      V
-#    THE PRINTER
-#
-# NOTE: Gimp-Print and some other 3rd-Party-Filters (like TurboPrint) to
-#       CUPS and ESP PrintPro plug-in where rastertosomething is noted.
-#
-#########################################################################
-
    -#########################################################################
-#
-# And this is how it works for CUPS from 1.1.15:
-# ==============================================
-#
-# SOMETHNG-FILEFORMAT
-#      |
-#      V
-#     somethingtops
-#      |
-#      V
-# APPLICATION/POSTSCRIPT
-#      |
-#      V
-#     pstops
-#      |
-#      V
-# APPLICATION/VND.CUPS-POSTSCRIPT-----+
-#                  +------------------v------------------------------+
-#                  | Ghostscript                                     |
-#                  | at work...                                      |
-#                  | (with                                           |
-#                  | "-sDEVICE=cups")                                |
-#                  |                                                 |
-#                  |         (= "postscipt interpreter")             |
-#                  |                                                 |
-#                  +------------------v------------------------------+
-#                                     |
-# APPLICATION/VND.CUPS-RASTER >-------+
-#      |
-#      V
-#     rastertosomething
-#      |   (= "raster driver")
-#      V
-# SOMETHING-DEVICE-SPECIFIC
-#      |
-#      V
-#     backend
-#
-#
-# NOTE: since version 1.1.15 CUPS "outsourced" the pstoraster process to
-#       Ghostscript. GNU Ghostscript needs to be patched to handle the
-#       CUPS requirement; ESP Ghostscript has this builtin. In any case,
-#       "gs -h" needs to show up a "cups" device. pstoraster is now a
-#       calling an appropriate "gs -sDEVICE=cups..." commandline to do
-#       the job. It will output "application/vnd.cup-raster", which will
-#       be finally processed by a CUPS raster driver "rastertosomething"
-#       Note the difference to "cupsomatic", which will not output
-#       CUPS-raster, but a final version of the printfile, ready to be
-#       sent to the printer. cupsomatic also doesn't use the "cups"
-#       devicemode in Ghostscript, but one of the classical devicemodes....
-#
-# NOTE: Gimp-Print and some other 3rd-Party-Filters (like TurboPrint) to
-#       CUPS and ESP PrintPro plug-in where rastertosomething is noted.
-#
-#########################################################################
-
    -#########################################################################
-#
-# And this is how it works for CUPS from 1.1.15, with cupsomatic included:
-# ========================================================================
-#
-# SOMETHNG-FILEFORMAT
-#      |
-#      V
-#     somethingtops
-#      |
-#      V
-# APPLICATION/POSTSCRIPT
-#      |
-#      V
-#     pstops
-#      |
-#      V
-# APPLICATION/VND.CUPS-POSTSCRIPT-----+
-#                  +------------------v------------------------------+
-#                  | Ghostscript        . Ghostscript at work....    |
-#                  | at work...         . (with "-sDEVICE=           |
-#                  | (with              .            s.th."          |
-#                  | "-sDEVICE=cups")   .                            |
-#                  |                    .                            |
-#                  | (CUPS standard)    .      (cupsomatic)          |
-#                  |                    .                            |
-#                  |          (= "postscript interpreter")           |
-#                  |                    .                            |
-#                  +------------------v--------------v---------------+
-#                                     |              |
-# APPLICATION/VND.CUPS-RASTER >-------+              |
-#      |                                             |
-#      V                                             |
-#     rastertosomething                              |
-#      |   (= "raster driver")                       |
-#      V                                             |
-# SOMETHING-DEVICE-SPECIFIC >------------------------+
-#      |
-#      V
-#     backend
-#
-#
-# NOTE: Gimp-Print and some other 3rd-Party-Filters (like TurboPrint) to
-#       CUPS and ESP PrintPro plug-in where rastertosomething is noted.
-#
-##########################################################################
-

    Trouble Shooting Guidelines to fix typical Samba printing -Problems

    -This is a short description of how to debug printing problems -with Samba. This describes how to debug problems with printing from -a SMB client to a Samba server, not the other way around. -

    Win9x client can't install driver

    For Win9x clients require the printer names to be 8 +

    Figure 19.17. Filtering chain 1

    Filtering chain 1

    Figure 19.18. Filtering chain with cupsomatic

    Filtering chain with cupsomatic

    Note

    +Gimp-Print and some other 3rd-Party-Filters (like TurboPrint) to +CUPS and ESP PrintPro plug-in where rastertosomething is noted. +

    Common Errors

    Win9x client can't install driver

    For Win9x clients require the printer names to be 8 chars (or "8 plus 3 chars suffix") max; otherwise the driver files won't get transferred when you want to download them from -Samba.

    testparm

    Run testparm: It will tell you if -smb.conf parameters are in the wrong -section. Many people have had the "printer admin" parameter in the -[printers] section and experienced -problems. "testparm" will tell you if it sees -this.

    "cupsaddsmb" keeps asking for a root password in a -neverending loop

    Have you security = user? Have +Samba.

    "cupsaddsmb" keeps asking for root password in + neverending loop

    Have you security = user? Have you used smbpasswd to give root a Samba account? You can do 2 things: open another terminal and execute smbpasswd -a root to create the account, and continue with entering the password into the first terminal. Or break out of the loop by hitting ENTER twice (without trying to type a -password).

    "cupsaddsmb" gives "No PPD file for printer..." -message (but I swear there is one!)

    • Have you enabled printer sharing on CUPS? This means: +password).

    "cupsaddsmb" gives "No PPD file for printer..." + message while PPD file is present

    Have you enabled printer sharing on CUPS? This means: do you have a <Location /printers>....</Location> section in CUPS server's cupsd.conf which doesn't deny access to the host you run "cupsaddsmb" from? It could be an issue if you use cupsaddsmb remotely, or if you use it with a --h parameter: cupsaddsmb -H -sambaserver -h cupsserver -v printername. -

  • Is your +-h parameter: cupsaddsmb -H + sambaserver -h cupsserver -v printername. +

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

    • I can't connect client 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?

    I can't reconnect to Samba under a new account -from Win2K/XP

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

    Can't reconnect to Samba under new account + from Win2K/XP

    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 won't be any byte transfered on the wire to Samba, but still you'll see a stupid error message which makes you think that Samba has denied access. Use @@ -3556,61 +3071,59 @@ indicating a renewed connection attempt? Shut all Explorer Windows. This makes Windows forget what it has cached in its memory as established connections. Then re-connect as the right user. Best method is to use a DOS terminal window and first -do net use z: \\SAMBAHOST\print$ /user:root. Check +do net use z: \\GANDALF\print$ /user:root. Check with smbstatus that you are connected under a different account. Now open the "Printers" folder (on the Samba server in the Network Neighbourhood), right-click the printer in question and select -Connect...

    Avoid being connected to the Samba server as the -"wrong" user

    You see per smbstatus that you are +Connect...

    Avoid being connected to the Samba server as the + "wrong" user

    You see per smbstatus that you are connected as user "nobody"; while you wanted to be "root" or -"printeradmin"? This is probably due to map to guest = bad -user, which silently connects you under the guest account, +"printeradmin"? This is probably due to +map to guest = bad user, which silently connects 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 on -NT/2K/XP clients gives problems

    First delete all "old" Adobe-using printers. Then +map to guest, if you want to prevent +this.

    Upgrading to CUPS drivers from Adobe drivers on + NT/2K/XP clients gives problems

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

    I can't use "cupsaddsmb"on a 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).

    I deleted a printer on Win2K; but I still see -its driver

    Deleting a printer on the client won't delete the +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 Win2K printer driver is still shown

    Deleting a printer on the client won't 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.

    Win2K/XP "Local Security -Policies"

    Local Security Policies may not +other printer uses the same driver.

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

    WinXP clients: "Administrator can not install -printers for all local users"

    Windows XP handles SMB printers on a "per-user" basis. +all.

    WinXP clients: "Administrator can not 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. To have a printer available for everybody, you might want to use the built-in IPP client capabilities of WinXP. Add a printer with the print path of http://cupsserver:631/printers/printername. 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, +users.

    "Print Change Notify" functions on + NT-clients

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

    WinXP-SP1

    WinXP-SP1 introduced a Point and Print +XP).

    WinXP-SP1

    WinXP-SP1 introduced a Point and Print Restriction Policy (this restriction doesn't apply to "Administrator" or "Power User" groups of users). In Group Policy -Object Editor: go to User Configuration --> -Administrative Templates --> Control Panel --> +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 in order to make -driver downloads from Samba possible.

    I can't set and save default print options for all -users on Win2K/XP

    How are you doing it? I bet the wrong way (it is not +driver downloads from Samba possible.

    Print options for all users can't be set on Win2K/XP

    How are you doing it? I bet the wrong way (it is not very easy to find out, though). There are 3 different ways to bring you to a dialog that seems to set everything. All three dialogs look the same. Only one of them @@ -3650,13 +3163,13 @@ Do you see any difference? I don't either... However, only the last one, which you arrived at with steps "C.1.-6." will save any settings permanently and be the defaults for new users. If you want all clients to get the same defaults, you need to conduct these steps as -Administrator (printer admin in +Administrator (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. -above).

    What are the most common blunders in driver -settings on Windows clients?

    Don't use Optimize for +above).

    Most common blunders in driver + settings on Windows clients

    Don't use Optimize for Speed: use Optimize for Portability instead (Adobe PS Driver) Don't use Page Independence: No: always @@ -3668,8 +3181,8 @@ 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.

    I can't make cupsaddsmb work -with newly installed printer

    Symptom: the last command of +there is a choice.

    cupsaddsmb does not work + with newly installed printer

    Symptom: the last command of cupsaddsmb doesn't complete successfully: cmd = setdriver printername printername result was NT_STATUS_UNSUCCESSFUL then possibly the printer was not yet @@ -3678,23 +3191,23 @@ Neighbourhood? 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.

    My permissions on +again.

    Permissions on /var/spool/samba/ get reset after each -reboot

    Have you by accident set the CUPS spool directory to +reboot

    Have you 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] +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] +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.

    My printers work fine: just the printer named "lp" +printing will not work reliably.

    Printer named "lp" intermittently swallows jobs and spits out completely different -ones

    It is a very bad idea to name any printer "lp". This -is the traditional Unix name for the default printer. CUPS may be set +ones

    It is a very 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 loadbalancing the jobs across them in a round-robin fashion. Chances @@ -3703,31 +3216,10 @@ receive his jobs and send your own to his device unwittingly. To have tight control over the printer names, set BrowseShortNames No. It will present any printer as "printername@cupshost" then, giving you a better control over what may happen in a large -networked environment.

    How do I "watch" my Samba server?

    You can use tail -f -/var/log/samba/log.smbd (you may need a different path) to -see a live scrolling of all log messages. smbcontrol smbd -debuglevel tells you which verbosity goes into the -logs. smbcontrol smbd debug 3 sets the verbosity to -a quite high level (you can choose from 0 to 10 or 100). This works -"on the fly", without the need to restart the smbd daemon. Don't use -more than 3 initially; or you'll drown in an ocean of -messages.

    I can't use Samba from my WinXP Home box, while -access from WinXP Prof works flawlessly

    You have our condolences! WinXP home has been -completely neutered by Microsoft as compared to WinXP Prof: you can -not log into a WinNT domain. It cannot join a Win NT domain as a -member server. While it is possible to access domain resources, users -don't have "single sign-on". They need to supply username and password -each time they connect to a resource. Logon scripts and roaming -profiles are not supported. It can serve file and print shares; but -only in "share-mode security" level. It can not use "user-mode -security" (what Windows 95/98/ME still can -do).

    Where do I find the Adobe PostScript driver files -I need for "cupsaddsmb"?

    Use smbclient to connect to any +networked environment.

    Location of Adobe PostScript driver files necessary 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 website.

    An Overview of the CUPS Printing Processes

    -

    Figure 19.15. CUPS Printing Overview

    CUPS Printing Overview

    -

    Prev Up Next
    Chapter 18. Classical Printing Support Home Chapter 20. Stackable VFS modules
    +files from the Adobe website.

    An Overview of the CUPS Printing Processes

    Figure 19.19. CUPS Printing Overview

    CUPS Printing Overview
    Prev Up Next
    Chapter 18. Classical Printing Support Home Chapter 20. Stackable VFS modules
    diff --git a/docs/htmldocs/ClientConfig.html b/docs/htmldocs/ClientConfig.html index 395be92345..ab34354e2d 100644 --- a/docs/htmldocs/ClientConfig.html +++ b/docs/htmldocs/ClientConfig.html @@ -1,4 +1,4 @@ -Chapter 9. MS Windows Network Configuration Guide
    Chapter 9. MS Windows Network Configuration Guide
    Prev Part II. Server Configuration Basics Next

    Chapter 9. MS Windows Network Configuration Guide

    John H. Terpstra

    Samba Team

    Table of Contents

    Note

    Note

    +Chapter 9. MS Windows Network Configuration Guide

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

    Chapter 9. MS Windows Network Configuration Guide

    John H. Terpstra

    Samba Team

    Table of Contents

    Note

    Note

    This chapter did not make it into this release. It is planned for the published release of this document. -

    Prev Up Next
    Chapter 8. Stand-Alone Servers Home Part III. Advanced Configuration
    +

    Prev Up Next
    Chapter 8. Stand-Alone Servers Home Part III. Advanced Configuration
    diff --git a/docs/htmldocs/DNSDHCP.html b/docs/htmldocs/DNSDHCP.html index dadf6b989a..1472c1925b 100644 --- a/docs/htmldocs/DNSDHCP.html +++ b/docs/htmldocs/DNSDHCP.html @@ -1,4 +1,4 @@ -Chapter 40. DNS and DHCP Configuration Guide
    Chapter 40. DNS and DHCP Configuration Guide
    Prev Part VI. Appendixes Next

    Chapter 40. DNS and DHCP Configuration Guide

    John H. Terpstra

    Samba Team

    Table of Contents

    Note

    Note

    +Chapter 40. DNS and DHCP Configuration Guide

    Chapter 40. DNS and DHCP Configuration Guide
    Prev Part VI. Appendixes Next

    Chapter 40. DNS and DHCP Configuration Guide

    John H. Terpstra

    Samba Team

    Table of Contents

    Note

    Note

    This chapter did not make it into this release. It is planned for the published release of this document. -

    Prev Up Next
    Chapter 39. Samba Performance Tuning Home Chapter 41. Further Resources
    +

    Prev Up Next
    Chapter 39. Samba Performance Tuning Home Chapter 41. Further Resources
    diff --git a/docs/htmldocs/FastStart.html b/docs/htmldocs/FastStart.html index dbb85dea6e..64c38702fd 100644 --- a/docs/htmldocs/FastStart.html +++ b/docs/htmldocs/FastStart.html @@ -1,4 +1,4 @@ -Chapter 3. Fast Start for the Impatient
    Chapter 3. Fast Start for the Impatient
    Prev Part I. General Installation Next

    Chapter 3. Fast Start for the Impatient

    John H. Terpstra

    Samba Team

    Table of Contents

    Note

    Note

    +Chapter 3. Fast Start for the Impatient

    Chapter 3. Fast Start for the Impatient
    Prev Part I. General Installation Next

    Chapter 3. Fast Start for the Impatient

    John H. Terpstra

    Samba Team

    Table of Contents

    Note

    Note

    This chapter did not make it into this release. It is planned for the published release of this document. -

    Prev Up Next
    Chapter 2. How to Install and Test SAMBA Home Part II. Server Configuration Basics
    +

    Prev Up Next
    Chapter 2. How to Install and Test SAMBA Home Part II. Server Configuration Basics
    diff --git a/docs/htmldocs/Further-Resources.html b/docs/htmldocs/Further-Resources.html index 8030190ed4..8464c480c2 100644 --- a/docs/htmldocs/Further-Resources.html +++ b/docs/htmldocs/Further-Resources.html @@ -1,4 +1,4 @@ -Chapter 41. Further Resources
    Chapter 41. Further Resources
    Prev Part VI. Appendixes Next

    Chapter 41. Further Resources

    Jelmer R. Vernooij

    The Samba Team

    David Lechnyr

    Unofficial HOWTO

    May 1, 2003

    Table of Contents

    Websites
    Related updates from Microsoft
    Books

    Websites

    Prev Up Next
    Chapter 40. DNS and DHCP Configuration Guide Home Index
    diff --git a/docs/htmldocs/InterdomainTrusts.html b/docs/htmldocs/InterdomainTrusts.html index 8938b84c42..8422c52073 100644 --- a/docs/htmldocs/InterdomainTrusts.html +++ b/docs/htmldocs/InterdomainTrusts.html @@ -1,10 +1,11 @@ -Chapter 16. Interdomain Trust Relationships
    Chapter 16. Interdomain Trust Relationships
    Prev Part III. Advanced Configuration Next

    Chapter 16. Interdomain Trust Relationships

    John H. Terpstra

    Samba Team

    Rafal Szczesniak

    Samba Team

    April 3, 2003

    Table of Contents

    Features and Benefits
    Trust Relationship Background
    Native MS Windows NT4 Trusts Configuration
    NT4 as the Trusting Domain (ie. creating the trusted account)
    NT4 as the Trusted Domain (ie. creating trusted account's password)
    Configuring Samba NT-style Domain Trusts
    Samba-3 as the Trusting Domain
    Samba-3 as the Trusted Domain
    Common Errors
    Tell me about Trust Relationships using Samba

    +Chapter 16. Interdomain Trust Relationships

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

    Chapter 16. 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
    Inter-Domain 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

    Samba-3 supports NT4 style domain trust relationships. This is feature that many sites will want to use if they migrate to Samba-3 from and NT4 style domain and do NOT want to adopt Active Directory or an LDAP based authentication back end. This section explains some background information regarding trust relationships and how to create them. It is now -possible for Samba-3 to NT4 trust (and vice versa), as well as Samba3 to Samba3 trusts. -

    Features and Benefits

    +possible for Samba-3 to trust NT4 (and vice versa), as well as to create Samba3-to-Samba3 +trusts. +

    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 similar scalability as is possible with MS Windows NT4. @@ -14,10 +15,10 @@ database such as LDAP, and given it's ability to run in Primary as well as Backu modes, the administrator would be well advised to consider alternatives to the use of Interdomain trusts simply because by the very nature of how this works it 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.x/4.0 type security domains employ a non-hierarchical security structure. The limitations of this architecture as it affects the scalability of MS Windows networking -in large organisations is well known. Additionally, the flat-name space that results from +in large organisations is well known. Additionally, the flat namespace that results from this design significantly impacts the delegation of administrative responsibilities in large and diverse organisations.

    @@ -43,45 +44,91 @@ relationship, and WHITE and BLUE have a trust relationship, then it holds that t implied trust between the RED and BLUE domains. ie: 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 above, 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

    -There are two steps to creating an interdomain trust relationship. -

    NT4 as the Trusting Domain (ie. creating the trusted account)

    +

    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

    For MS Windows NT4, all domain trust relationships are configured using the -Domain User Manager. To affect a two way trust relationship it is -necessary for each domain administrator to make available (for use by an external domain) it's -security resources. This is done from the Domain User Manager Policies entry on the menu bar. -From the Policy menu, select Trust Relationships, then -next to the lower box that is labelled Permitted to Trust this Domain are two -buttons, Add and Remove. The Add -button will open a panel in which needs to be entered the remote domain that will be able to assign -user rights to your domain. In addition it is necessary to enter a password -that is specific to this trust relationship. The password needs to be -typed twice (for standard confirmation). -

    NT4 as the Trusted Domain (ie. creating trusted account's password)

    +Domain User Manager. This is done from the Domain User Manager Policies +entry on the menu bar. From the Policy menu, select +Trust Relationships. Next to the lower box labelled +Permitted to Trust this Domain are two buttons, Add +and Remove. The Add button will open a panel in which +to enter the name of the remote domain that will be able to assign access rights to users in +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

    + 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 will launch the Domain User Manager, from the menu select Policies, then select Trust Relationships, then click on the Add button that is next to the box that is labelled Trusted Domains. A panel will open in which must be entered the name of the remote domain as well as the password assigned to that trust. -

    Configuring Samba NT-style Domain Trusts

    +

    Inter-Domain 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: +

    Figure 16.1. Trusts overview

    Trusts overview

    • + DomA (completes the trust connection) Trusts DomB +

    • + DomA is the Trusting domain +

    • + DomB is the Trusted domain (originates the trust account) +

    • + Users in DomB can access resources in DomA +

    • + Users in DomA can NOT access resources in DomB +

    • + Global groups from DomB CAN be used in DomA +

    • + Global groups from DomA can NOT be used in DomB +

    • + DomB DOES appear in the logon dialog box on client workstations in DomA +

    • + DomA does NOT appear in the logon dialog box on client workstations in DomB +

    • + Users / Groups in a trusting domain can NOT be granted rights, permissions or access + to a trusted domain. +

    • + The trusting domain CAN access and use accounts (Users / Global Groups) in the + trusted domain. +

    • + Administrators of the trusted domain CAN be granted admininstrative rights in the + trusting domain. +

    • + Users in a trusted domain CAN be given rights and privileges in the trusting + domain. +

    • + Trusted domain Global Groups CAN be given rights and permissions in the trusting + domain. +

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

    This description is meant to be a fairly short introduction about how to set up a Samba server so that it could participate in interdomain trust relationships. Trust relationship support in Samba is in its early stage, so lot of things don't work yet.

    -Each of the procedures described below is treated as they were performed with Windows NT4 Server on -one end. 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 below leads to trust -between domains in purely Samba environment. -

    Samba-3 as the Trusting Domain

    -In order to set the Samba PDC to be the trusted party of the relationship first you need -to create special account for the domain that will be the trusting party. To do that, +Each of the procedures described below 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 below 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 very similar to creating a trusted machine account. Suppose, your domain is called SAMBA, and the remote domain is called RUMBA. The first step @@ -89,9 +136,9 @@ will be to issue this command from your favourite shell: 

     root#  smbpasswd -a -i rumba
-	New SMB password: XXXXXXXX
-	Retype SMB password: XXXXXXXX
-	Added user rumba$
+New SMB password: XXXXXXXX
+Retype SMB password: XXXXXXXX
+Added user rumba$

    where -a means to add a new account into the @@ -104,29 +151,29 @@ After issuing this command you'll 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 depending on your configuration) and see that account's name is -really RUMBA$ and it has 'I' flag in the flags field. Now you're ready to confirm +(in the standard way as appropriate for your configuration) and see that account's name is +really RUMBA$ and it has the 'I' flag set in the flags field. Now you're ready to confirm the trust by establishing it from Windows NT Server. -

    -Open User Manager for Domains and from menu -Policies select Trust Relationships.... -Right beside Trusted domains list box press the +

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

    Samba-3 as the Trusted 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 NT-controlled domain is called RUMBA.

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

    +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 Trusted Domains box press the Add -button, and type in the name of the trusted domain (SAMBA) and password securing +Now, next to the Trusted 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 @@ -138,38 +185,39 @@ Using your favourite shell while being 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. -Do not worry if you see an error message that mentions a returned code of -NT_STATUS_NOLOGON_INTERDOMAIN_TRUST_ACCOUNT. It means the +Do not worry if you see an error message that mentions a return code of +NT_STATUS_NOLOGON_INTERDOMAIN_TRUST_ACCOUNT. It means the password you gave is correct and the NT4 Server says the account is ready for interdomain connection and not for ordinary -connection. After that, be patient it can take a while (especially -in large networks), you should see the Success message. +connection. After that, be patient; it can take a while (especially +in large networks), but eventually you should see the Success message. Congratulations! Your trust relationship has just been established.

    Note

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

    Common Errors

    +

    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 above, 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 trusts are not transitive, if you want +your users to have access to multiple mixed-mode domains in your AD forest, you will need to +repeat this process for each of those domains. With Active Directory Domains +and Trusts open, right-click on the name of the Active Directory domain that +will trust our Samba domain and choose Properties, then click on +the Trusts tab. In the upper part of the panel, you will see a list box +labelled Domains trusted by this domain:, and an +Add... button next to it. Press this button, and just as with NT4, you +will be prompted for the trusted domain name and the relationship 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 acess to resources in the AD domain. +

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

    Tell me about Trust Relationships using Samba

    - Like many, I administer multiple LANs connected together using NT trust - relationships. This was implemented about 4 years ago. I now have the - occasion to consider performing this same task again, but this time, I - would like to implement it solely through samba - no Microsoft PDCs - anywhere. -

    - I have read documentation on samba.org regarding NT-style trust - relationships and am now wondering, can I do what I want to? I already - have successfully implemented 2 samba servers, but they are not PDCs. - They merely act as file servers. I seem to remember, and it appears to - be true (according to samba.org) that trust relationships are a - challenge. -

    - Please provide any helpful feedback that you may have. -

    - These are almost complete in Samba 3.0 snapshots. The main catch - is getting winbindd to be able to allocate UID/GIDs for trusted - users/groups. See the updated Samba HOWTO collection for more - details. -

    Prev Up Next
    Chapter 15. Securing Samba Home Chapter 17. Hosting a Microsoft Distributed File System tree on Samba
    +

    Prev Up Next
    Chapter 15. Securing Samba Home Chapter 17. Hosting a Microsoft Distributed File System tree on Samba
    diff --git a/docs/htmldocs/IntroSMB.html b/docs/htmldocs/IntroSMB.html index f9c2539112..51a22f14fa 100644 --- a/docs/htmldocs/IntroSMB.html +++ b/docs/htmldocs/IntroSMB.html @@ -1,4 +1,4 @@ -Chapter 1. Introduction to Samba
    Chapter 1. Introduction to Samba
    Prev Part I. General Installation Next

    Chapter 1. Introduction to Samba

    David Lechnyr

    Unofficial HOWTO

    April 14, 2003

    Table of Contents

    Background
    Terminology
    Related Projects
    SMB Methodology
    Epilogue
    Miscellaneous

    “ +Chapter 1. Introduction to Samba

    Chapter 1. Introduction to Samba
    Prev Part I. General Installation Next

    Chapter 1. Introduction to Samba

    David Lechnyr

    Unofficial HOWTO

    April 14, 2003

    Table of Contents

    Background
    Terminology
    Related Projects
    SMB Methodology
    Epilogue
    Miscellaneous

    “ "If you understand what you're doing, you're not learning anything." -- Anonymous ”

    @@ -7,7 +7,7 @@ transport protocol. In fact, it can support any SMB/CIFS-enabled client. One of strengths is that you can use it to blend your mix of Windows and Linux machines together without requiring a separate Windows NT/2000/2003 Server. Samba is actively being developed by a global team of about 30 active programmers and was originally developed by Andrew Tridgell. -

    Background

    +

    Background

    Once long ago, there was a buzzword referred to as DCE/RPC. This stood for Distributed Computing Environment/Remote Procedure Calls and conceptually was a good idea. It was originally developed by Apollo/HP as NCA 1.0 (Network Computing Architecture) and only @@ -33,7 +33,7 @@ been dutifully waded through during the information-gathering stages of this pro are *still* many missing pieces... While often tedious, at least the way has been generously littered with occurrences of clapping hand to forehead and muttering 'crikey, what are they thinking? -

    Terminology

    • +

    Terminology

    • SMB: Acronym for "Server Message Block". This is Microsoft's file and printer sharing protocol.

    • CIFS: Acronym for "Common Internet File System". Around 1996, Microsoft apparently @@ -83,7 +83,7 @@ thinking? W3K: Acronym for Windows 2003 Server

    If you plan on getting help, make sure to subscribe to the Samba Mailing List (available at http://www.samba.org). -

    Related Projects

    +

    Related Projects

    There are currently two network filesystem client projects for Linux that are directly related to Samba: SMBFS and CIFS VFS. These are both available in the Linux kernel itself.

    • @@ -105,7 +105,7 @@ nothing to do with acting as a file and print server for SMB/CIFS clients. There are other Open Source CIFS client implementations, such as the jCIFS project which provides an SMB client toolkit written in Java. -

    SMB Methodology

    +

    SMB Methodology

    Traditionally, SMB uses UDP port 137 (NetBIOS name service, or netbios-ns), UDP port 138 (NetBIOS datagram service, or netbios-dgm), and TCP port 139 (NetBIOS session service, or netbios-ssn). Anyone looking at their network with a good @@ -137,7 +137,7 @@ up a single file. In general, SMB sessions are established in the following orde A good way to examine this process in depth is to try out SecurityFriday's SWB program. It allows you to walk through the establishment of a SMB/CIFS session step by step. -

    Epilogue

    “ +

    Epilogue

    “ What's fundamentally wrong is that nobody ever had any taste when they did it. Microsoft has been very much into making the user interface look good, but internally it's just a complete mess. And even people who program for Microsoft @@ -166,9 +166,9 @@ not the completely clueless user who probably sits there shivering thinking That's what's really irritating to me." ”

    -- Linus Torvalds, from an interview with BOOT Magazine, Sept 1998 -

    Miscellaneous

    +

    Miscellaneous

    This chapter is Copyright 2003 David Lechnyr (david at lechnyr dot com). Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.2 or any later version published by the Free Software Foundation. A copy of the license is available at http://www.gnu.org/licenses/fdl.txt. -

    Prev Up Next
    Part I. General Installation Home Chapter 2. How to Install and Test SAMBA
    +

    Prev Up Next
    Part I. General Installation Home Chapter 2. How to Install and Test SAMBA
    diff --git a/docs/htmldocs/NT4Migration.html b/docs/htmldocs/NT4Migration.html index 72c6269f0e..b561492644 100644 --- a/docs/htmldocs/NT4Migration.html +++ b/docs/htmldocs/NT4Migration.html @@ -1,7 +1,7 @@ -Chapter 31. Migration from NT4 PDC to Samba-3 PDC
    Chapter 31. Migration from NT4 PDC to Samba-3 PDC
    Prev Part IV. Migration and Updating Next

    Chapter 31. 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 Implementation Choices

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

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

    Chapter 31. 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. @@ -9,65 +9,62 @@ and planned for. Then again, good planning will anticipate most show stopper typ 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 under way. -

    Objectives

    +

    Objectives

    The key objective for most organisations will be 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 one of 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.

    -It is strongly advised that before attempting a migration to a Samba-3 controlled network -that every possible effort be made to gain all-round commitment to the change. Firstly, you -should know precisely why the change is important for the organisation. -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 organisation's dependency on Microsoft

    -It is vital that it be well recognised that Samba-3 is NOT MS Windows NT4. Samba-3 offers -an alternative solution that is both different from MS Windows NT4 and that offers some -advantages compared with it. It should also be recognised that Samba-3 lacks many of the +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 organisation. 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 organisation's dependency on Microsoft

    +Make sure that 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 that offers +advantages compared with it. Gain recognition that Samba-3 lacks many of the features that Microsoft has promoted as core values in migration from MS Windows NT4 to MS Windows 2000 and beyond (with or without Active Directory services).

    What are the features that Samba-3 can NOT 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 includes: -

    Lower Cost of Ownership
    Global availability of support with no strings attached
    Dynamic SMB Servers (ie:Can run more than one 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 back-end authentication technologies (tdbsam, ldapsam, mysqlsam)
    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 it is vital that all necessary factors are -considered. Users should be educated about changes they may experience so that the change will be a -welcome one and not become an obstacle to the work they need to do. The following are some of the -factors that will go into a successful migration: -

    Domain Layout

    +

    • Lower Cost of Ownership

    • Global availability of support with no strings attached

    • Dynamic SMB Servers (ie:Can run more than one 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 back-end authentication technologies (tdbsam, ldapsam, mysqlsam)

    • 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 that the change will be a welcome one +and not become an obstacle to the work they need to do. The following are factors that will +help ensure a successful migration: +

    Domain Layout

    Samba-3 can be configured as a domain controller, a back-up domain controller (probably best called a secondary controller), a domain member, or as a stand-alone server. The Windows network security domain context should be sized and scoped before implementation. Particular attention needs to be paid to the location of the primary domain controller (PDC) as well as backup controllers (BDCs). -It should be noted that one way in which Samba-3 differs from Microsoft technology is that if one -chooses to use an LDAP authentication backend then the same database can be used by several different -domains. This means that in a complex organisation there can be a single LDAP database, that itself -can be distributed, that can simultaneously serve multiple domains (that can also be widely distributed). +One way in which Samba-3 differs from Microsoft technology is that if one chooses to use an LDAP +authentication backend then the same database can be used by several different domains. In a +complex organisation there can be a single LDAP database, which itself can be distributed (ie: Have +a master server and multiple slave servers) that can simultaneously serve multiple domains.

    -It is recommended that from a design perspective, the number of users per server, as well as the number -of servers, per domain should be scaled according to needs and should also consider server capacity -and network bandwidth. +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 of which may span multiple network segments. -Where domains span routed network segments it is most advisable to consider and test the performance -implications of the design and layout of a network. A Centrally located domain controller that is being -designed to serve multiple routed network segments may result in severe performance problems if the -response time (eg: ping timing) between the remote segment and the PDC is more than 100 ms. In situations -where the delay is too long it is highly recommended to locate a backup controller (BDC) to serve as -the local authentication and access control server. -

    Server Share and Directory Layout

    -There are few cardinal rules to effective network design that can be broken with impunity. -The most important rule of effective network management is that 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. +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 (eg: ping timing) between the remote segment and the PDC. If long (more than 100 ms) +locate a backup controller (BDC) on the remote segmanet to serve as the local authentication and +access control server. +

    Server Share and Directory Layout

    +There are cardinal rules to effective network design. These can not 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.

    -The nature of the data that must be stored needs to be born in mind when deciding how many -shares must be created. The physical disk space layout should also be taken into account -when designing where share points will be created. Keep in mind that all data needs to be -backed up, thus the simpler the disk layout the easier it will be to keep track of what must -be backed up to tape or other off-line storage medium. Always plan and implement for minimum +Keep in mind the nature of how data must be share. 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 backed needs. Identify what back media will be meet needs, consider backup to tape +, CD-ROM or (DVD-ROM), or other off-line storage medium. Plan and implement for minimum maintenance. Leave nothing to chance in your design, above all, do not leave backups to chance: Backup and test, validate every backup, create a disaster recovery plan and prove that it works.

    @@ -75,54 +72,70 @@ Users should be grouped according to data access control needs. File and directo 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.

    -Many network administrators who are new to the game will attempt to use elaborate techniques -to set access controls, on files, directories, shares, as well as in share definitions. -There is the ever present danger that that administrator's successor will not understand the -complex mess that has been inherited. Remember, apparent job security through complex design -and implementation may ultimately cause loss of operations and downtime to users as the new -administrator learns to untangle your web. Keep access controls simple and effective and -make sure that users will never be interrupted by the stupidity of complexity. -

    Logon Scripts

    -Please refer to the section of this document on Advanced Network Administration for information -regarding the network logon script options for Samba-3. Logon scripts can help to ensure that -all users gain share and printer connections they need. +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 +audit your documentation. Do not create a complex mess that your successor will not understand. +Remember, job security through complex design and implementation may cause loss of operations +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 stupid +complexity. +

    Logon Scripts

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

    -Logon scripts can be created on-the-fly so that all commands executed are specific to the -rights and privileges granted to the user. The preferred controls should be affected through +Logon scripts can be created 'on-the-fly' so that all commands executed are specific to the +rights and priviliges granted to the user. The preferred controls should be affected through group membership so that group information can be used to custom create a logon script using -the root preexec parameters to the NETLOGON share. +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 knowledgebase 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 it is STRONGLY advised to create in Samba-3 the -groups that are present on the MS Windows NT4 domain AND to connect these to -suitable Unix/Linux groups. Following this simple advice will mean that all user and group attributes +groups that are present on the MS Windows NT4 domain AND to map these 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 will have an NT4 PDC that has the users, groups, policies and profiles to be migrated

    • -Samba-3 set up as a DC with netlogon share, profile share, etc. -

    Procedure 31.1. The Account Migration Process

    1. Create a BDC account for the samba server using NT Server Manager

      1. Samba must NOT be running

    2. rpcclient NT4PDC -U Administrator%passwd

      1. lsaquery

      2. Note the SID returned

    3. net getsid -S NT4PDC -w DOMNAME -U Administrator%passwd

      1. Note the SID

    4. net getlocalsid

      1. Note the SID, now check that all three SIDS reported are the same!

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

    6. net rpc vampire -S NT4PDC -U administrator%passwd

    7. pdbedit -L

      1. Note - did the users migrate?

    8. initGrps.sh DOMNAME

    9. net groupmap list

      1. Now check that all groups are recognised

    10. net rpc vampire -S NT4PDC -U administrator%passwd

    11. pdbedit -Lv

      1. Note - check that all group membership has been migrated

    -Now it is time to migrate all the profiles, then migrate all policy files. -More later. -

    Migration Options

    -Based on feedback from many sites as well as from actual installation and maintenance -experience sites that wish to migrate from MS Windows NT4 Domain Control to a Samba -based solution fit into three basic categories. -

    Table 31.1. The 3 Major Site Types

    Number of UsersDescription
    < 50

    Want simple conversion with NO pain

    50 - 250

    Want new features, can manage some in-house complexity

    > 250

    Solution/Implementation MUST scale well, complex needs. Cross departmental decision process. Local expertise in most areas

    Planning for Success

    +Samba-3 set up as a DC with netlogon share, profile share, etc. Configure the smb.conf file +to fucntion as a BDC. ie: domain master = No. +

    Procedure 31.1. The Account Migration Process

    1. Create a BDC account for the samba server using NT Server Manager

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

      1. Note - did the users migrate?

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

      +#!/bin/bash
+#### Keep this as a shell script for future re-use
+			
+# First assign well known domain global groups
+net groupmap modify ntgroup="Domain Admins" unixgroup=ntadmins
+net groupmap modify ntgroup="Domain Guests" unixgroup=nobody
+net groupmap modify ntgroup="Domain Users" unixgroup=users
+
+# Now for our added domain global groups
+net groupmap add ntgroup="Designers" unixgroup=designers type=d rid=3200
+net groupmap add ntgroup="Engineers" unixgroup=engineers type=d rid=3210
+net groupmap add ntgroup="QA Team"   unixgroup=qateam    type=d rid=3220
+

      +

    6. net groupmap list

      1. Now check that all groups are recognised

    +Now migrate all the profiles, then migrate all policy files. +

    Migration Options

    +Sites that wish to migrate from MS Windows NT4 Domain Control to a Samba based solution +generally fit into three basic categories. +

    Table 31.1. The 3 Major Site Types

    Number of UsersDescription
    < 50

    Want simple conversion with NO pain

    50 - 250

    Want new features, can manage some in-house complexity

    > 250

    Solution/Implementation MUST scale well, complex needs. 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.

    • @@ -132,7 +145,7 @@ to Samba-3.

    • Complete Redesign (completely new solution)

    -No matter what choice you make, the following rules will minimise down-stream problems: +Minimise down-stream problems by:

    • Take sufficient time

    • @@ -141,62 +154,25 @@ No matter what choice you make, the following rules will minimise down-stream pr Test ALL assumptions

    • Test full roll-out program, including workstation deployment -

    Table 31.2. Nature of the Conversion Choices

    SimpleUpgradedRedesign

    Make use of minimal OS specific features

    Translate NT4 features to new host OS features

    Decide:

    Suck 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

    Minimise user impact

    Better Control of Desktops / Users

    Live versus Isolated Conversion

    Maximise functionality

    Identify Needs for: Manageability, Scalability, Security, Availability

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

    Take advantage of lower maintenance opportunity

    Samba Implementation Choices

    -Authentication database back end
-	Winbind (external Samba or NT4/200x server)
-	Can use pam_mkhomedir.so to auto-create home dirs
-	External server could use Active Directory or NT4 Domain
-
-Database type
-	smbpasswd, tdbsam, ldapsam, mysqlsam
-
-Access Control Points
-	On the Share itself (Use NT4 Server Manager)
-	On the file system
-	Unix permissions on files and directories
-	Enable Posix ACLs in file system?
-	Through Samba share parameters
-		Not recommended - except as only resort
-
-Policies (migrate or create new ones)
-	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
-	username map facility may be needed
-	Use 'net groupmap' to connect NT4 groups to Unix groups
-	Use pdbedit to set/change user configuration
-NOTE:
-If migrating to LDAP back end it may be easier to dump initial LDAP database
-to LDIF, then edit, then reload into LDAP
-
-	OS specific scripts / programs may be needed
-		Add / delete Users
-			Note OS limits on size of name (Linux 8 chars)
-				NT4 up to 254 chars
-		Add / delete machines
-			Applied only to domain members (note up to 16 chars)
-		Add / delete Groups
-			Note OS limits on size and nature
-				Linux limit is 16 char,
-				no spaces and no upper case chars (groupadd)
-
-Migration Tools
-	Domain Control (NT4 Style)
-	Profiles, Policies, Access Controls, Security
-
-Migration Tools
-	Samba: net, rpcclient, smbpasswd, pdbedit, profiles
-	Windows: NT4 Domain User Manager, Server Manager (NEXUS)
-
-Authentication
-	New SAM back end (smbpasswd, tdbsam, ldapsam, mysqlsam)
-

    -

    Prev Up Next
    Chapter 30. Upgrading from Samba-2.x to Samba-3.0.0 Home Chapter 32. SWAT - The Samba Web Administration Tool
    +

    Table 31.2. Nature of the Conversion Choices

    SimpleUpgradedRedesign

    Make use of minimal OS specific features

    Translate NT4 features to new host OS features

    Decide:

    Suck 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

    Minimise user impact

    Better Control of Desktops / Users

    Live versus Isolated Conversion

    Maximise functionality

    Identify Needs for: Manageability, Scalability, Security, Availability

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

    Take advantage of lower maintenance opportunity

    Samba-3 Implementation Choices

    Authentication database/back end:

    + 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 auto-create home dirs

    +

    + Samba-3 can use a local authentication backend: +

    • smbpasswd, tdbsam, ldapsam, mysqlsam

    +

    Access Control Points:

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

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

    • username map facility may be needed

    • Use 'net groupmap' to connect NT4 groups to Unix groups

    • Use pdbedit to set/change user configuration

      + NOTE: When migrating to LDAP back, end it may be easier to dump initial + LDAP database to LDIF, then edit, then reload into LDAP +

    OS specific scripts/programs may be needed:

    • Add/Delete Users: Note OS limits on size of name + (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 upper case 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 30. Upgrading from Samba-2.x to Samba-3.0.0 Home Chapter 32. SWAT - The Samba Web Administration Tool
    diff --git a/docs/htmldocs/NetworkBrowsing.html b/docs/htmldocs/NetworkBrowsing.html index eb4d9858ca..4507c0067f 100644 --- a/docs/htmldocs/NetworkBrowsing.html +++ b/docs/htmldocs/NetworkBrowsing.html @@ -1,4 +1,4 @@ -Chapter 10. Samba / MS Windows Network Browsing Guide
    Chapter 10. Samba / MS Windows Network Browsing Guide
    Prev Part III. Advanced Configuration Next

    Chapter 10. Samba / MS Windows Network Browsing Guide

    John H. Terpstra

    Samba Team

    July 5, 1998

    Updated: April 21, 2003

    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
    Setting up WORKGROUP Browsing
    Setting up DOMAIN Browsing
    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
    Setting up a WINS server
    WINS Replication
    Static WINS Entries
    Helpful Hints
    Windows Networking Protocols
    Name Resolution Order
    Technical Overview of browsing
    Browsing support in Samba
    Problem resolution
    Browsing across subnets
    Common Errors
    How can one flush the Samba NetBIOS name cache without restarting Samba?
    My client reports "This server is not configured to list shared resources"

    +Chapter 10. Samba / MS Windows Network Browsing Guide

    Chapter 10. Samba / MS Windows Network Browsing Guide
    Prev Part III. Advanced Configuration Next

    Chapter 10. Samba / MS Windows Network Browsing Guide

    John H. Terpstra

    Samba Team

    Jelmer R. Vernooij

    The Samba Team

    July 5, 1998

    Updated: April 21, 2003

    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
    Setting up WORKGROUP Browsing
    Setting up DOMAIN Browsing
    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
    Setting up a WINS server
    WINS Replication
    Static WINS Entries
    Helpful Hints
    Windows Networking Protocols
    Name Resolution Order
    Technical Overview of browsing
    Browsing support in Samba
    Problem resolution
    Browsing across subnets
    Common Errors
    How can one flush the Samba NetBIOS name cache without restarting Samba?
    My client reports "This server is not configured to list shared resources"
    I get an Unable to browse the network error

    This document 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. WINS is @@ -9,11 +9,11 @@ over TCP/IP. Samba-3 and later also supports this mode of operation. When the use of NetBIOS over TCP/IP has been disabled then 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

    Someone once referred to the past in terms of: They were the worst of times, they were the best of times. The more we look back, them 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 @@ -38,63 +38,55 @@ help Samba to affect stable WINS operations beyond the normal scope of MS WINS.

    Please note that 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 turn off -support for NetBIOS, in which case WINS is of no relevance. Samba-3 supports this also. +support for NetBIOS, in which case WINS is of no relevance. Samba supports this also.

    For those networks on which NetBIOS has been disabled (ie: WINS is NOT required) the use of DNS is necessary for host name resolution. -

    What is Browsing?

    +

    What is Browsing?

    To most people browsing means that 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.

    What seems so simple is in fact a very complex interaction of different technologies. The technologies (or methods) employed in making all of this work includes: -

    MS Windows machines register their presence to the network
    Machines announce themselves to other machines on the network
    One or more machine on the network collates 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

    +

    • MS Windows machines register their presence to the network

    • Machines announce themselves to other machines on the network

    • One or more machine on the network collates 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: -

    -		
-	Browsing options:
-	-----------------
-		* os level
-		  lm announce
-		  lm interval
-		* preferred master
-		* local master
-		* domain master
-		  browse list
-		  enhanced browsing
-
-	Name Resolution Method:
-	-----------------------
-		* name resolve order
-
-	WINS options:
-	-------------
-		  dns proxy
-		  wins proxy
-		* wins server
-		* wins support
-		  wins hook
-

    +

    Browsing options: os level(*), + lm announce, + lm interval, + preferred master(*), + local master(*), + domain master(*), + browse list, + enhanced browsing. +

    Name Resolution Method: + name resolve order(*). +

    WINS options: + dns proxy, + wins proxy, + wins server(*), + wins support(*), + wins hook. +

    For Samba, the WINS Server and WINS Support are mutually exclusive options. Those marked with an '*' are the only options that commonly MAY need to be modified. Even if not one of these parameters is set nmbd will still do it's job. -

    Discussion

    +

    Discussion

    Firstly, all MS Windows networking uses SMB (Server Message Block) based messaging. SMB messaging may be implemented with or without NetBIOS. MS Windows 200x supports NetBIOS over TCP/IP for backwards compatibility. Microsoft is 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. MS Windows products can do likewise. NetBIOS based networking uses broadcast messaging to affect 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 +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 +remote browse sync parameter of smb.conf implements browse list collation using unicast UDP.

    Secondly, in those networks where Samba is the only SMB server technology, @@ -102,12 +94,13 @@ wherever possible nmbd should be configured on one (1) server. This makes it easy to manage the browsing environment. If each network segment is configured with it's 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 +remote announce and the remote browse sync parameters to your smb.conf file.

    + If only one WINS server is used for an entire multi-segment network then -the use of the remote announce and the -remote browse sync parameters should NOT be necessary. +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 @@ -118,7 +111,7 @@ 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 -remote browse sync and remote announce +remote browse sync and remote announce to affect browse list collation across all segments. Note that this means clients will only resolve local names, and must be configured to use DNS to resolve names on other subnets in order to resolve the IP addresses of the servers they can see @@ -129,7 +122,10 @@ 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 stabilise, particularly across network segments. -

    TCP/IP - without NetBIOS

    +

    TCP/IP - without NetBIOS

    + + + All TCP/IP using systems use various forms of host name resolution. The primary methods for TCP/IP hostname resolutions involves either a static file (/etc/hosts ) or DNS (the Domain Name System). DNS is the technology that makes @@ -152,7 +148,7 @@ it follows a defined path:

  • Looks up entries in LMHOSTS. It is located in C:\WinNT\System32\Drivers\etc. -

    • +

    Windows 200x / XP can register it's host name with a Dynamic DNS server. You can force register with a Dynamic DNS server in Windows 200x / XP using: ipconfig /registerdns @@ -165,8 +161,8 @@ consequently network services will be severely impaired. The use of Dynamic DNS is highly recommended with Active Directory, in which case the use of BIND9 is preferred for it's ability to adequately support the SRV (service) records that are needed for Active Directory. -

    DNS and Active Directory

    -Occasionally we hear from Unix network administrators who want to use a Unix based Dynamic +

    DNS and Active Directory

    +Occasionally we hear from UNIX network administrators who want to use a UNIX based Dynamic DNS server in place of the Microsoft DNS server. While this might be desirable to some, the MS Windows 200x DNS server is auto-configured to work with Active Directory. It is possible to use BIND version 8 or 9, but it will almost certainly be necessary to create service records @@ -187,7 +183,7 @@ The following are some of the default service records that Active Directory requ

  • _ldap._tcp.Site.gc.ms-dcs.DomainTree

    Used by MS Windows clients to locate site configuration dependent Global Catalog server. -

    • How Browsing Functions

    +

    How Browsing Functions

    MS Windows machines register their NetBIOS names (ie: the machine name for each service type in operation) on start up. The exact method by which this name registration @@ -201,7 +197,7 @@ 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). +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 @@ -229,20 +225,18 @@ 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 synchronisation -of browse lists across routed networks using the remote -browse sync parameter in the smb.conf file. +of browse lists across routed networks using the remote browse sync parameter in the smb.conf file. This causes Samba to contact the local master browser on a remote network and to request browse list synchronisation. This effectively bridges two networks that are separated by routers. The two remote networks may use either broadcast based name resolution or WINS -based name resolution, but it should be noted that the remote -browse sync parameter provides browse list synchronisation - and +based name resolution, but it should be noted that the remote browse sync parameter provides browse list synchronisation - and that is distinct from name to address resolution, in other words, 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. -

    Setting up WORKGROUP Browsing

    +

    Setting up WORKGROUP Browsing

    To set up cross subnet browsing on a network containing machines in up to be in a WORKGROUP, not an NT Domain you need to set up one Samba server to be the Domain Master Browser (note that this is *NOT* @@ -261,20 +255,13 @@ workgroup name. To set up a Samba server as a domain master browser, set the following option in the [global] section of the smb.conf file :

    -

    -	domain master = yes
-

    +

    domain master = yes

    -The domain master browser should also preferrably be the local master +The domain master browser should also preferably be the local master browser for its own subnet. In order to achieve this set the following options in the [global] section of the smb.conf file :

    -

    -	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 domain master browser may be the same machine as the WINS server, if you require. @@ -288,20 +275,15 @@ to use these). To make a Samba server a local master browser set the following options in the [global] section of the smb.conf file :

    -

    -	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 local master browser.

    -The local master parameter allows Samba to act as a -local master browser. The preferred master causes nmbd -to force a browser election on startup and the os level +The local master parameter allows Samba to act as a +local master browser. The preferred master causes nmbd +to force a browser election on startup and the os level parameter sets Samba high enough so that it should win any browser elections.

    If you have an NT machine on the subnet that you wish to @@ -310,13 +292,8 @@ becoming a local master browser by setting the following options in the [global] section of the smb.conf file :

    -

    -	domain master = no
-	local master = no
-	preferred master = no
-	os level = 0
-

    -

    Setting up DOMAIN Browsing

    +

    Example 10.3. smb.conf for not being a master browser

    [global]
    domain master = no
    local master = no
    preferred master = no
    os level = 0

    +

    Setting up DOMAIN Browsing

    If you are adding Samba servers to a Windows NT Domain then you must not set up a Samba server as a domain master browser. By default, a Windows NT Primary Domain Controller for a domain @@ -328,18 +305,13 @@ with WINS instead of the PDC. For subnets other than the one containing the Windows NT PDC you may set up Samba servers as local master browsers as described. To make a Samba server a local master browser set -the following options in the [global] section +the following options in the [global] section of the smb.conf file :

    -

    -	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 +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 local master browsers if they are running. For more details on this see the section @@ -353,38 +325,33 @@ ever becoming a local master browser by setting following options in the [global] section of the smb.conf file :

    -

    -        domain master = no
-        local master = no
-        preferred master = no
-        os level = 0
-

    +

    Example 10.5. smb.conf for not being a master browser

    [global]
    domain master = no
    local master = no
    preferred master = no
    os level = 0

    Forcing Samba to be the master

    -Who becomes the master browser is determined by an election +Who becomes the master browser is determined by an election process using broadcasts. Each election packet contains a number of parameters which determine what precedence (bias) a host should have in the election. By default Samba uses a very low precedence and thus loses elections to just about anyone else.

    -If you want Samba to win elections then just set the os level global +If you want Samba to win elections then just set the os level global option in smb.conf to a higher number. It defaults to 0. Using 34 would make it win all elections over every other system (except other samba systems!)

    -A os level of 2 would make it beat WfWg and Win95, but not MS Windows +A os level of 2 would make it beat WfWg and Win95, but not MS Windows NT/2K Server. A MS Windows NT/2K Server domain controller uses level 32.

    The maximum os level is 255

    If you want Samba to force an election on startup, then set the -preferred master global option in smb.conf to yes. Samba will +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, as if you have two hosts (whether they are Windows 95 or NT or -Samba) on the same local subnet both set with preferred master to +Samba) on the same local subnet both set with preferred master to yes, then periodically and continually they will force an election in order to become the local master browser.

    -If you want Samba to be a domain master browser, then it is -recommended that you also set preferred master to yes, because + If you want Samba to be a domain master browser, then it is +recommended that you also set preferred master to yes, because Samba will not become a domain master browser for the whole of your LAN or WAN if it is not also a local master browser on its own broadcast isolated subnet. @@ -396,10 +363,10 @@ attempt to become the domain master browser every 5 minutes. They will find that another Samba server is already the domain master browser and will fail. This provides automatic redundancy, should the current domain master browser fail. -

    Making Samba the domain master

    +

    Making Samba the domain master

    The domain master is responsible for collating the browse lists of multiple subnets so that browsing can occur between subnets. You can -make Samba act as the domain master by setting domain master = yes +make Samba act as the domain master by setting domain master = yes in smb.conf. By default it will not be a domain master.

    Note that you should not set Samba to be the domain master for a @@ -411,8 +378,8 @@ master browsers on other subnets and then contact them to synchronise browse lists.

    If you want Samba to be the domain master then I suggest you 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 +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.

    Note that all your servers (including Samba) and clients should be @@ -438,31 +405,31 @@ If, however, both Samba and your clients are using a WINS server, then: 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 "0" 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 0's broadcast and you will probably find that browsing and name lookups won't work. -

    Multiple interfaces

    +

    Multiple interfaces

    Samba now supports machines with multiple network interfaces. If you -have multiple interfaces then you will need to use the interfaces +have multiple interfaces then you will need to use the interfaces option in smb.conf to configure them. -

    Use of the Remote Announce parameter

    -The remote announce parameter of +

    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 = a.b.c.d [e.f.g.h] ...
-

    +The syntax of the remote announce parameter is: +

    remote announce = a.b.c.d [e.f.g.h] ...

    or -

    -	remote announce = a.b.c.d/WORKGROUP [e.f.g.h/WORKGROUP] ...
-

    +

    remote announce = a.b.c.d/WORKGROUP [e.f.g.h/WORKGROUP] ...

    where:

    a.b.c.d and -e.f.g.h

    is either the LMB (Local Master Browser) IP address +e.f.g.h

    + + + + is either the LMB (Local Master Browser) IP address or the broadcast address of the remote network. ie: the LMB is at 192.168.1.10, or the address could be given as 192.168.1.255 where the netmask @@ -478,22 +445,20 @@ 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

    -The remote browse sync parameter of +

    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 synchronise its NetBIOS name list with our Samba LMB. It 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: +The syntax of the remote browse sync parameter is: -

    -remote browse sync = a.b.c.d
-

    +

    remote browse sync = a.b.c.d

    where a.b.c.d is either the IP address of the remote LMB or else is 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. @@ -534,36 +499,34 @@ lookup attempts by other clients and will therefore cause workstation access errors.

    To configure Samba as a WINS server just add -wins support = yes to the smb.conf -file [globals] section. +wins support = yes to the smb.conf +file [global] section.

    To configure Samba to register with a WINS server just add -wins server = a.b.c.d to your smb.conf file [globals] section. +wins server = a.b.c.d to your smb.conf file [global] section.

    Important

    -Never use both wins support = yes together -with wins server = a.b.c.d +Never use both wins support = yes together +with wins server = a.b.c.d particularly not using it's own IP address. Specifying both will cause nmbd to refuse to start! -

    Setting up a WINS server

    +

    Setting up a WINS server

    Either a Samba machine or a Windows NT Server machine may be set up as a WINS server. To set a Samba machine to be a WINS server you must add the following option to the smb.conf file on the selected machine : -in the [globals] section add the line +in the [global] section add the line

    -

    -	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 least set the parameter to 'no' on all these machines.

    -Machines with wins support = yes will keep a list of +Machines with wins support = yes will keep a list of all NetBIOS names registered with them, acting as a DNS for NetBIOS names.

    You should set up only ONE WINS server. Do NOT set the -wins support = yes option on more than one Samba +wins support = yes option on more than one Samba server.

    To set up a Windows NT Server as a WINS server you need to set up @@ -575,7 +538,7 @@ participate in these replications. It is possible in the future that a Samba->Samba WINS replication protocol may be defined, in which case more than one Samba machine could be set up as a WINS server but currently only one Samba server should have the -wins support = yes parameter set. +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 @@ -586,17 +549,15 @@ in Windows 95 or Windows NT. 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.

    Note that this line MUST NOT BE SET in the smb.conf file of the Samba server acting as the WINS server itself. If you set both the -wins support = yes option and the -wins server = <name> option then +wins support = yes option and the +wins server = <name> option then nmbd will fail to start.

    There are two possible scenarios for setting up cross subnet browsing. @@ -604,13 +565,13 @@ The first details setting up cross subnet browsing on a network containing Windows 95, Samba and Windows NT 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 permits WINS replication through the use of the wrepld utility. This tool is not currently capable of being used as it is still in active development. As soon as this tool becomes moderately functional we will prepare man pages and enhance this section of the documentation to provide usage and technical details. -

    Static WINS Entries

    -Adding static entries to your Samba-3 WINS server is actually fairly easy. +

    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.

    @@ -639,10 +600,10 @@ To make it static, all that has to be done is set the TTL to 0: Though this method works with early Samba-3 versions, there's 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 as they are stumbling points for many new network administrators. -

    Windows Networking Protocols

    Warning

    +

    Windows Networking Protocols

    Warning

    Do NOT use more than one (1) protocol on MS Windows machines

    A very common cause of browsing problems results from installing more than @@ -672,34 +633,27 @@ differently from MS Windows NT4. Generally, where a server does NOT support the newer or extended protocol, these will fall back to the NT4 protocols.

    The safest rule of all to follow it this - 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: is static and hard to maintain.
    Broadcast: uses UDP and can not resolve names across remote segments.

    +

    • WINS: the best tool!

    • LMHOSTS: is static and hard to maintain.

    • Broadcast: uses UDP and can not resolve names across remote segments.

    Alternative means of name resolution includes: -

    /etc/hosts: is static, hard to maintain, and lacks name_type info
    DNS: is a good choice but lacks essential name_type info.

    +

    • /etc/hosts: is static, hard to maintain, and lacks name_type info

    • DNS: is a good choice but lacks essential name_type info.

    Many sites want to restrict DNS lookups and want to 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
-

    +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

    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
-

    -where "host" refers the the native methods used by the Unix system +

    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, a so-called browse list. This list +of machines in a network, a so-called browse list. This list contains machines that are ready to offer file and/or print services to other machines within the network. Thus it does not include machines which aren't currently able to do server tasks. The browse @@ -717,7 +671,7 @@ 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 can NOT 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 a local browse master for a workgroup and the ability @@ -744,15 +698,15 @@ WINS server capabilities. In a Samba-only environment, it is recommended that you use one and only one Samba server as your WINS server.

    To get browsing to work you need to run nmbd as usual, but will need -to use the workgroup option in smb.conf +to 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 only used for 'unusual' purposes: announcements over the internet, for -example. See remote announce in the +example. See remote announce in the smb.conf man page. -

    Problem resolution

    +

    Problem resolution

    If something doesn't work then hopefully the log.nmbd file will help you track down the problem. Try a debug level of 2 or 3 for finding problems. Also note that the current browse list usually gets stored @@ -763,7 +717,7 @@ type the server name as \\SERVER in filemanager then hit enter and filemanager should display the list of available shares.

    Some people find browsing fails because they don't have the global -guest account set to a valid account. Remember that the +guest account set to a valid account. Remember that the IPC$ connection that lists the shares is done as guest, and thus you must have a valid guest account.

    @@ -777,7 +731,7 @@ 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) -

    Browsing across subnets

    +

    Browsing across subnets

    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. @@ -798,32 +752,14 @@ 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 Win95 and WinNT, this is in the TCP/IP Properties, under Network settings) for Samba this is in the smb.conf file. -

    How does cross subnet browsing work ?

    +

    How does cross subnet browsing work ?

    Cross subnet browsing is a complicated dance, containing multiple moving parts. It has taken Microsoft several years to get the code that achieves this correct, and Samba lags behind in some areas. Samba is capable of cross subnet browsing when configured correctly.

    -Consider a network set up as follows : -

    - -

    -                                   (DMB)
-             N1_A      N1_B        N1_C       N1_D        N1_E
-              |          |           |          |           |
-          -------------------------------------------------------
-            |          subnet 1                       |
-          +---+                                      +---+
-          |R1 | Router 1                  Router 2   |R2 |
-          +---+                                      +---+
-            |                                          |
-            |  subnet 2              subnet 3          |
-  --------------------------       ------------------------------------
-  |     |     |      |               |        |         |           |
- N2_A  N2_B  N2_C   N2_D           N3_A     N3_B      N3_C        N3_D 
-                    (WINS)
-

    -

    + Consider a network set up as in the diagram below. +

    Figure 10.1. Cross subnet browsing example

    Cross subnet browsing example

    Consisting of 3 subnets (1, 2, 3) connected by two routers (R1, R2) - these do not pass broadcasts. Subnet 1 has 5 machines on it, subnet 2 has 4 machines, subnet 3 has 4 machines. Assume @@ -865,7 +801,7 @@ At this point the browse lists look as follows (these are the machines you would see in your network neighborhood if you looked in it on a particular network right now).

    -

    Table 10.1. Browse subnet example 1

    SubnetBrowse MasterList
    Subnet1N1_CN1_A, N1_B, N1_C, N1_D, N1_E
    Subnet2N2_BN2_A, N2_B, N2_C, N2_D
    Subnet3N3_DN3_A, N3_B, N3_C, N3_D

    +

    Table 10.1. Browse subnet example 1

    SubnetBrowse MasterList
    Subnet1N1_CN1_A, N1_B, N1_C, N1_D, N1_E
    Subnet2N2_BN2_A, N2_B, N2_C, N2_D
    Subnet3N3_DN3_A, N3_B, N3_C, N3_D

    Note that at this point all the subnets are separate, no machine is seen across any of the subnets. @@ -887,7 +823,9 @@ the MasterAnnouncement packet it schedules a synchronization request to the sender of that packet. After both synchronizations are done the browse lists look like :

    -

    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

    +

    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 a (*) after them are non-authoritative names.

    @@ -895,14 +833,17 @@ 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 only see the servers on their own subnet.

    -The same sequence of events that occured for N2_B now occurs +The same sequence of events that occurred for N2_B now occurs for the local master browser on subnet 3 (N3_D). When it synchronizes browse lists with the domain master browser (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 look like.

    -

    Table 10.3. Browse subnet example 3

    SubnetBrowse MasterList
    Subnet1N1_CN1_A, N1_B, N1_C, N1_D, N1_E, N2_A(*), N2_B(*), N2_C(*), N2_D(*), N3_A(*), N3_B(*), N3_C(*), N3_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, N1_A(*), N1_B(*), N1_C(*), N1_D(*), N1_E(*), N2_A(*), N2_B(*), N2_C(*), N2_D(*)

    +

    Table 10.3. Browse subnet example 3

    SubnetBrowse MasterList
    Subnet1N1_CN1_A, N1_B, N1_C, N1_D, N1_E, +N2_A(*), N2_B(*), N2_C(*), N2_D(*), N3_A(*), N3_B(*), N3_C(*), N3_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, N1_A(*), +N1_B(*), N1_C(*), N1_D(*), N1_E(*), N2_A(*), N2_B(*), N2_C(*), N2_D(*)

    Servers with a (*) after them are non-authoritative names.

    @@ -915,7 +856,13 @@ with the domain master browser (N1_C) and will receive the missing server entries. Finally - and as a steady state (if no machines are removed or shut off) the browse lists will look like :

    -

    Table 10.4. Browse subnet example 4

    SubnetBrowse MasterList
    Subnet1N1_CN1_A, N1_B, N1_C, N1_D, N1_E, N2_A(*), N2_B(*), N2_C(*), N2_D(*), N3_A(*), N3_B(*), N3_C(*), N3_D(*)
    Subnet2N2_BN2_A, N2_B, N2_C, N2_D, N1_A(*), N1_B(*), N1_C(*), N1_D(*), N1_E(*), N3_A(*), N3_B(*), N3_C(*), N3_D(*)
    Subnet3N3_DN3_A, N3_B, N3_C, N3_D, N1_A(*), N1_B(*), N1_C(*), N1_D(*), N1_E(*), N2_A(*), N2_B(*), N2_C(*), N2_D(*)

    +

    Table 10.4. Browse subnet example 4

    SubnetBrowse MasterList
    Subnet1N1_CN1_A, N1_B, N1_C, N1_D, N1_E, +N2_A(*), N2_B(*), N2_C(*), N2_D(*), N3_A(*), N3_B(*), +N3_C(*), N3_D(*)
    Subnet2N2_BN2_A, N2_B, N2_C, N2_D, N1_A(*), +N1_B(*), N1_C(*), N1_D(*), N1_E(*), N3_A(*), N3_B(*), +N3_C(*), N3_D(*)
    Subnet3N3_DN3_A, N3_B, N3_C, N3_D, N1_A(*), +N1_B(*), N1_C(*), N1_D(*), N1_E(*), N2_A(*), N2_B(*), +N2_C(*), N2_D(*)

    Servers with a (*) after them are non-authoritative names.

    @@ -936,11 +883,11 @@ If either router R1 or R2 fails the following will occur: be able to access servers on its local subnet, by using subnet-isolated broadcast NetBIOS name resolution. The effects are 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 out of incorrect configuration of NetBIOS name resolution. Some are of particular note. -

    How can one flush the Samba NetBIOS name cache without restarting Samba?

    +

    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. Note that this does NOT make certain that a rogue machine name will not re-appear @@ -950,8 +897,11 @@ want to clear a rogue machine from the list then every machine on the network wi shut down and restarted at 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 (months). -

    My client reports "This server is not configured to list shared resources"

    +

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

    See also guest account in the smb.conf man page.

    Prev Up Next
    Part III. Advanced Configuration Home Chapter 11. Account Information Databases
    +

    See also 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 local master browser. Configure nmbd + or any other machine to serve as local master browser.

    • You can not log onto the machine that is the local master + browser. Can you logon to it as guest user?

    • There is no IP connectivity to the local master browser. + Can you reach it by broadcast?

    Prev Up Next
    Part III. Advanced Configuration Home Chapter 11. Account Information Databases
    diff --git a/docs/htmldocs/Other-Clients.html b/docs/htmldocs/Other-Clients.html index a5e7740cf0..dffa1122ac 100644 --- a/docs/htmldocs/Other-Clients.html +++ b/docs/htmldocs/Other-Clients.html @@ -1,8 +1,7 @@ -Chapter 38. Samba and other CIFS clients
    Chapter 38. Samba and other CIFS clients
    Prev Part VI. Appendixes Next

    Chapter 38. Samba and other CIFS clients

    Jim McDonough

    IBM

    Jelmer R. Vernooij

    The Samba Team

    5 Mar 2001

    Table of Contents

    Macintosh clients?
    OS2 Client
    How can I configure OS/2 Warp Connect or - OS/2 Warp 4 as a client for Samba?
    How can I configure OS/2 Warp 3 (not Connect), - OS/2 1.2, 1.3 or 2.x for Samba?
    How do I get printer driver download working - for OS/2 clients?
    Windows for Workgroups
    Use latest TCP/IP stack from Microsoft
    Delete .pwl files after password change
    Configure WfW password handling
    Case handling of passwords
    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 now has a CIFS Client / Server called DAVE +Chapter 38. Samba and other CIFS clients

    Chapter 38. Samba and other CIFS clients
    Prev Part VI. Appendixes Next

    Chapter 38. Samba and other CIFS clients

    Jelmer R. Vernooij

    The 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 as a client for Samba
    Configuring OS/2 Warp 3 (not Connect), + OS/2 1.2, 1.3 or 2.x for Samba
    Printer driver download for for OS/2 clients?
    Windows for Workgroups
    Latest TCP/IP stack from Microsoft
    Delete .pwl files after password change
    Configuring WfW password handling
    Case handling of passwords
    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 now has a CIFS Client / Server called DAVE

    They test it against Windows 95, Windows NT and samba for compatibility issues. At the time of writing, DAVE was at version @@ -21,10 +20,8 @@ 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 -

    OS2 Client

    How can I configure OS/2 Warp Connect or - OS/2 Warp 4 as a client for Samba?

    A more complete answer to this question can be - found on - http://carol.wins.uva.nl/~leeuw/samba/warp.html.

    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 as a client for Samba

    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" @@ -39,14 +36,12 @@ packages, Samba, and Linux (and other UNIX-based systems) see 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 webpage mentioned above.

    How can I configure OS/2 Warp 3 (not Connect), - OS/2 1.2, 1.3 or 2.x for Samba?

    You can use the free Microsoft LAN Manager 2.2c Client + the same level as Warp 4. See the webpage mentioned above.

    Configuring OS/2 Warp 3 (not Connect), + OS/2 1.2, 1.3 or 2.x for Samba

    You can use the free Microsoft LAN Manager 2.2c Client for OS/2 from ftp://ftp.microsoft.com/BusSys/Clients/LANMAN.OS2/. - See - http://carol.wins.uva.nl/~leeuw/lanman.html for - more information on how to install and use this client. In + In a nutshell, edit the file \OS2VER in the root directory of the OS/2 boot partition and add the lines:

     		20=setup.exe
@@ -57,14 +52,12 @@ packages, Samba, and Linux (and other UNIX-based systems) see
 		or NS2000 driver from 
 		
  		ftp://ftp.cdrom.com/pub/os2/network/ndis/ instead.
-

    How do I get printer driver download working - for OS/2 clients?

    First, create a share called [PRINTDRV] that is +

    Printer driver download for for OS/2 clients?

    First, create a share called [PRINTDRV] that is world-readable. Copy your OS/2 driver files there. Note that 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, os2 driver map = - filename. Then, in the file + add to your smb.conf a parameter, os2 driver map = filename. Then, in the file specified by filename, map the name of the NT driver name to the OS/2 driver name as follows:

    nt driver name = os2 driver name.device name, e.g.:

    @@ -74,7 +67,7 @@ packages, Samba, and Linux (and other UNIX-based systems) see 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

    Use 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 their TCP/IP 32-Bit @@ -89,7 +82,7 @@ fixed. New files include WINSOCK.DLL, TRACERT.EXE, NETSTAT.EXE, and NBTSTAT.EXE. -

    Delete .pwl files after password change

    +

    Delete .pwl files after password change

    WfWg does a lousy job with passwords. I find that if I change my password on either the unix box or the PC the safest thing to do is to delete the .pwl files in the windows directory. The PC will complain about not finding the files, but will soon get over it, allowing you to enter the new password. @@ -98,20 +91,20 @@ If you don't do this you may find that WfWg remembers and uses the old password, even if you told it a new one.

    Often WfWg will totally ignore a password you give it in a dialog box. -

    Configure WfW password handling

    +

    Configuring WfW 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. ie disable Password Caching etc -for use with security = user -

    Case handling of passwords

    Windows for Workgroups uppercases the password before sending it to the server. Unix passwords can be case-sensitive though. Check the smb.conf(5) 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 +for use with security = user +

    Case handling of passwords

    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 that you have to use TCP/IP as the default protocol under WfWg. For some reason if you leave NetBEUI as the default it may break the print queue reporting on some systems. -It is presumably a WfWg bug.

    Speed improvement

    -Note that some people have found that setting DefaultRcvWindow in +It is presumably a WfWg bug.

    Speed improvement

    + Note that some people have found that setting DefaultRcvWindow in the [MSTCP] section of the SYSTEM.INI file under WfWg to 3072 gives a big improvement. I don't know why. @@ -121,7 +114,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. I don't know why. -

    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 above change will affect you once these updates have been installed. @@ -135,11 +128,11 @@ install the OLEUPD.EXE fix. This fix may stop your machine from hanging for an extended period when exiting Outlook and you may also notice a significant speedup when accessing network neighborhood services. -

    Speed improvement

    +

    Speed improvement

    Configure the win95 TCPIP registry settings to give better performance. I use a program called MTUSPEED.exe which I got off the net. 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 @@ -148,26 +141,19 @@ likely occur if it is not.

    In order to serve profiles successfully to Windows 2000 SP2 clients (when not operating as a PDC), Samba must have -nt acl support = no +nt acl support = no added to the file share which houses the roaming profiles. If this is not done, then the Windows 2000 SP2 client will complain about not being able to access the profile (Access Denied) and create multiple copies of it on disk (DOMAIN.user.001, DOMAIN.user.002, etc...). See the -smb.conf(5) man page +smb.conf man page for more details on this option. Also note that the -nt acl support parameter was formally a global parameter in +nt acl support parameter was formally a global parameter in releases prior to Samba 2.2.2.

    The following is a minimal profile share: -

    -	[profile]
-		path = /export/profile
-		create mask = 0600
-		directory mask = 0700
-		nt acl support = no
-		read only = no
-

    +

    Example 38.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 Win2k SP2 client copies the security descriptor for the profile which contains the Samba server's SID, and not the domain SID. The client @@ -175,12 +161,12 @@ compares the SID for SAMBA\user and realizes it is different that the one assigned to DOMAIN\user. Hence the reason for the access denied message.

    -By disabling the nt acl support parameter, Samba will send +By disabling the nt acl support parameter, Samba will send the Win2k 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 -NT 3.1 workstations, read this Microsoft Knowledge Base article. +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 37. Portability Home Chapter 39. Samba Performance Tuning
    +

    Prev Up Next
    Chapter 37. Portability Home Chapter 39. Samba Performance Tuning
    diff --git a/docs/htmldocs/PolicyMgmt.html b/docs/htmldocs/PolicyMgmt.html index 775cd6cc16..754ca9b686 100644 --- a/docs/htmldocs/PolicyMgmt.html +++ b/docs/htmldocs/PolicyMgmt.html @@ -1,10 +1,10 @@ -Chapter 23. System and Account Policies
    Chapter 23. System and Account Policies
    Prev Part III. Advanced Configuration Next

    Chapter 23. 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
    Samba Editreg Toolset
    Windows NT4/200x
    Samba PDC
    System Startup and Logon Processing Overview
    Common Errors
    Policy Does Not Work

    +Chapter 23. System and Account Policies

    Chapter 23. System and Account Policies
    Prev Part III. Advanced Configuration Next

    Chapter 23. 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
    Samba Editreg Toolset
    Windows NT4/200x
    Samba PDC
    System Startup and Logon Processing Overview
    Common Errors
    Policy Does Not Work

    This chapter summarises the current state of knowledge derived from personal practice and knowledge from samba mailing list subscribers. Before reproduction of posted information effort has been made to validate the information provided. Where additional information was uncovered through this validation it is provided also. -

    Features and Benefits

    +

    Features and Benefits

    When MS Windows NT3.5 was introduced the hot new topic was the ability to implement Group Policies for users and group. Then along came MS Windows NT4 and a few sites started to adopt this capability. How do we know that? By way of the number of "booboos" @@ -23,9 +23,9 @@ the deployment in many sites. This chapter reviews techniques and methods that c be used to exploit opportunities for automation of control over user desktops and network client workstations.

    -A tool new to Samba-3 may become an important part of the future Samba Administrators' +A tool new to Samba may become an important part of the future Samba Administrators' arsenal. The editreg tool is described in this document. -

    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 @@ -54,13 +54,13 @@ 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 -Implementing Profiles and Policies in Windows NT 4.0 from http://www.microsoft.com/ntserver/management/deployment/planguide/prof_policies.asp available from Microsoft. +Implementing Profiles and Policies in Windows NT 4.0 available from Microsoft. There are a large number of documents in addition to this old one that should also be read and understood. Try searching on the Microsoft web site for "Group Policies".

    What follows is a very 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 Win98 Group Policy Editor to set Group Profiles up under Windows 9x/Me. It can be found on the Original full product Win98 installation CD under tools/reskit/netadmin/poledit. Install this using the @@ -86,7 +86,7 @@ here is incomplete - you are warned. grouppol.inf. Log off and on again a couple of times and see if Win98 picks up group policies. Unfortunately this needs to be done on every Win9x/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 NT Workstation. There is a Policy Editor on a NT4 @@ -107,14 +107,14 @@ here is incomplete - you are warned. be extracted as well. It is also possible to downloaded 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. Since the settings that were in the NTConfig.POL file were applied to the client machine registry and that apply to the hive key HKEY_LOCAL_MACHINE are permanent until explicitly reversed. This is known as tattooing. It can have serious consequences down-stream 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 allows setting of registry parameters specific to users, groups and computers (client workstations) that are members of the NT4 style domain. Such policy file will work with MS Windows 2000 / XP clients also. @@ -151,7 +151,7 @@ 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 Win2K / XP Policies

    +

    Administration of Win2K / 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. @@ -177,10 +177,10 @@ here is incomplete - you are warned. 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. -

    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 not necessary. +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 @@ -203,20 +203,27 @@ in a manner that works in conjunction with user profiles, the user management en MS Windows NT4/200x/XP allows per domain as well as per user account restrictions to be applied. Common restrictions that are frequently used includes:

    -

    Logon Hours
    Password Aging
    Permitted Logon from certain machines only
    Account type (Local or Global)
    User Rights

    -

    Samba Editreg Toolset

    - Describe in detail the benefits of editreg and how to use it. -

    Windows NT4/200x

    +

    • Logon Hours

    • Password Aging

    • Permitted Logon from certain machines only

    • Account type (Local or Global)

    • User Rights

    +

    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 NTUser.DAT file and can be editted using + this tool. editreg is being built with the intent to enable NTConfig.POL + files to be saved in text format and to permit the building of new NTConfig.POL files with + extended capabilities. It is proving difficult to realise this capability, so do not be surprised + if this feature does not materialise. Formal capabilities will be announced at the time that + this tool is released for production use. +

    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, the registry editor (regedt32.exe). Under MS Windows 200x/XP this is done using the Microsoft Management Console (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 of user account and policy information includes: smbpasswd, pdbedit, net, 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 of system and user policies following a system reboot and as part of the user logon:

    1. @@ -225,7 +232,7 @@ reboot and as part of the user logon:

    2. Where Active Directory is involved, an ordered list of Group Policy Objects (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 scope of applicability: local, site, domain, organizational unit, etc.

      +

      • Apply to the location of machines in a Directory

      • Apply only when settings have changed

      • Depend on configuration of scope of applicability: local, site, domain, organizational unit, etc.

      No desktop user interface is presented until the above have been processed.

    3. Execution of start-up scripts (hidden and synchronous by default). @@ -236,7 +243,7 @@ reboot and as part of the user logon:

    4. An ordered list of User GPOs is obtained. The list contents depends on what is configured in respect of: -

      Is user a domain member, thus subject to particular policies
      Loopback enablement, and the state of the loopback policy (Merge or Replace)
      Location of the Active Directory itself
      Has the list of GPOs changed. No processing is needed if not changed.

      +

      • Is user a domain member, thus subject to particular policies

      • Loopback enablement, and the state of the loopback policy (Merge or Replace)

      • Location of the Active Directory itself

      • Has the list of GPOs changed. No processing is needed if not changed.

    5. User Policies are applied from Active Directory. Note: There are several types.

    6. @@ -246,15 +253,15 @@ reboot and as part of the user logon:

    7. The User Interface as determined from the GPOs is presented. Note: In a Samba domain (like and NT4 Domain) machine (system) policies are applied at start-up, User policies are applied at logon. -

    Common Errors

    +

    Common Errors

    Policy related problems can be very difficult to diagnose and even more difficult to rectify. The following collection demonstrates only basic issues. -

    Policy Does Not Work

    -Question: We have created the config.pol file and put it in the NETLOGON share. +

    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 don't see it. IT worked fine with Win 98 but does not -work any longer since we upgraded to Win XP Pro. Any hints? +work any longer since we upgraded to Win XP Pro. Any hints?”

    -ANSWER: Policy files are NOT portable between Windows 9x / Me and MS Windows NT4 / 200x / XP based +Policy files are NOT portable between Windows 9x / Me and MS Windows NT4 / 200x / XP based platforms. You need to use the NT4 Group Policy Editor to create a file called NTConfig.POL so that it is in the correct format for your MS Windows XP Pro clients. -

    Prev Up Next
    Chapter 22. Advanced Network Management Home Chapter 24. Desktop Profile Management
    +

    Prev Up Next
    Chapter 22. Advanced Network Management Home Chapter 24. Desktop Profile Management
    diff --git a/docs/htmldocs/Portability.html b/docs/htmldocs/Portability.html index bb2c20ac9f..50d14207d0 100644 --- a/docs/htmldocs/Portability.html +++ b/docs/htmldocs/Portability.html @@ -1,6 +1,6 @@ -Chapter 37. Portability
    Chapter 37. Portability
    Prev Part VI. Appendixes Next

    Chapter 37. Portability

    Jelmer R. Vernooij

    The Samba Team

    Table of Contents

    HPUX
    SCO Unix
    DNIX
    RedHat Linux Rembrandt-II
    AIX
    Sequential Read Ahead
    Solaris
    Locking improvements
    Winbind on Solaris 9

    Samba works on a wide range of platforms but the interface all the +Chapter 37. Portability

    Chapter 37. Portability
    Prev Part VI. Appendixes Next

    Chapter 37. Portability

    Jelmer R. Vernooij

    The Samba Team

    Table of Contents

    HPUX
    SCO UNIX
    DNIX
    RedHat Linux Rembrandt-II
    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

    HP's implementation of supplementary groups is, er, non-standard (for hysterical reasons). There are two group files, /etc/group and /etc/logingroup; the system maps UIDs to numbers using the former, but @@ -20,15 +20,15 @@ allowed range. On HPUX 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

    -If you run an old version of SCO Unix then you may need to get important +

    SCO UNIX

    +If you run an old version of SCO UNIX then 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.

    The patch you need is UOD385 Connection Drivers SLS. It is available from SCO (ftp.sco.com, directory SLS, files uod385a.Z and uod385a.ltr.Z). -

    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. @@ -73,8 +73,8 @@ _seteuid:

    after creating the above files you then assemble them using 

    -	$ as seteuid.s
-	$ as setegid.s
+$ as seteuid.s
+$ as setegid.s

    that should produce the files seteuid.o and setegid.o @@ -87,7 +87,7 @@ LIBSM = setegid.o seteuid.o -ln You should then remove the line: 

     #define NO_EID
-

    from the DNIX section of includes.h

    RedHat Linux Rembrandt-II

    +

    from the DNIX section of includes.h

    RedHat Linux Rembrandt-II

    By default RedHat Rembrandt-II during installation adds an entry to /etc/hosts as follows: 

    @@ -101,10 +101,10 @@ 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 using vmtune -r 0 improves Samba performance significantly. -

    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, @@ -125,4 +125,4 @@ and rebuild samba. Nsswitch on Solaris 9 refuses to use the winbind nss module. This behavior is fixed by Sun in patch 113476-05 which as of March 2003 is not in any roll-up packages. -

    Prev Up Next
    Chapter 36. How to compile SAMBA Home Chapter 38. Samba and other CIFS clients
    +

    Prev Up Next
    Chapter 36. How to compile Samba Home Chapter 38. Samba and other CIFS clients
    diff --git a/docs/htmldocs/ProfileMgmt.html b/docs/htmldocs/ProfileMgmt.html index 0b9a40df62..765ae4b0c4 100644 --- a/docs/htmldocs/ProfileMgmt.html +++ b/docs/htmldocs/ProfileMgmt.html @@ -1,4 +1,4 @@ -Chapter 24. Desktop Profile Management
    Chapter 24. Desktop Profile Management
    Prev Part III. Advanced Configuration Next

    Chapter 24. 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
    Sharing Profiles between W9x/Me and NT4/200x/XP workstations
    Profile Migration from Windows NT4/200x Server to Samba
    Mandatory profiles
    Creating/Managing Group Profiles
    Default Profile for Windows Users
    MS Windows 9x/Me
    MS Windows NT4 Workstation
    MS Windows 200x/XP
    Common Errors
    How does one set up roaming profiles for just one (or a few) user/s or group/s?
    Can NOT use Roaming Profiles
    Changing the default profile

    Features and Benefits

    +Chapter 24. Desktop Profile Management

    Chapter 24. Desktop Profile Management
    Prev Part III. Advanced Configuration Next

    Chapter 24. 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
    Sharing Profiles between W9x/Me and NT4/200x/XP workstations
    Profile Migration from Windows NT4/200x Server to Samba
    Mandatory profiles
    Creating/Managing Group Profiles
    Default Profile for Windows Users
    MS Windows 9x/Me
    MS Windows NT4 Workstation
    MS Windows 200x/XP
    Common Errors
    Setting up roaming profiles for just a few user's or group's?
    Can NOT use Roaming Profiles
    Changing the default profile

    Features and Benefits

    Roaming Profiles are feared by some, hated by a few, loved by many, and a Godsend for some administrators.

    @@ -11,7 +11,7 @@ problem to others. In particular, users of mobile computing tools, where often t be a sustained network connection, are often better served by purely Local Profiles. This chapter provides information to help the Samba administrator to deal with those situations also. -

    Roaming Profiles

    Warning

    +

    Roaming Profiles

    Warning

    Roaming profiles support is different for Win9x / Me and Windows NT4/200x.

    Before discussing how to configure roaming profiles, it is useful to see how @@ -24,21 +24,17 @@ 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

    To support Windows NT4/200x clients, in the [global] section of smb.conf set the following (for example):

    -

    -	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 user name

    The default for this option is \\%N\%U\profile, @@ -51,31 +47,26 @@ semantics of %L and %N, as well as %U and %u. MS Windows NT/2K clients at times do not disconnect a connection to a server between logons. It is recommended to NOT use the homes meta-service name as part of the profile share path. -

    Windows 9x / Me User Profiles

    - To support Windows 9x / Me clients, you must use the logon home parameter. Samba has +

    Windows 9x / Me User Profiles

    + To support Windows 9x / Me clients, you must use the logon home parameter. Samba has now been fixed so that 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 Win9x / 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 (thus 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 9x / Me and Windows NT4/200x User Profiles

    +specified \\%L\%U for logon home. +

    Mixed Windows 9x / Me and Windows NT4/200x User Profiles

    You can support profiles for both Win9X and WinNT clients by setting both the -logon home and logon path parameters. For example: -

    -	logon home = \\%L\%u\.profiles
-	logon path = \\%L\profiles\%u
-

    Disabling Roaming Profile Support

    +logon home and logon path parameters. For example: +

    logon home = \\%L\%u\.profiles
    logon path = \\%L\profiles\%u

    Disabling Roaming Profile Support

    A question often asked is “How may I enforce use of local profiles?” or “How do I disable Roaming Profiles?”

    @@ -83,13 +74,11 @@ There are three ways of doing this:

    In smb.conf

    Affect the following settings and ALL clients will be forced to use a local profile: - 

    -			logon home =
-			logon path =
-

    +

    logon home
    logon path

    MS Windows Registry:

    By using the Microsoft Management Console 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: + 

     	Local Computer Policy\
 		Computer Configuration\
@@ -112,15 +101,15 @@ profiles.
 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 stored in c:\windows\profiles\username on subsequent logins, taking the most recent from 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 +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 @@ -153,11 +142,11 @@ domain and profiles downloaded from it, if that domain logon server supports it), user name and user's password.

    Once the user has been successfully validated, the Windows 9x / Me machine -will inform you that The user has not logged on before' and asks you - if you wish to save the user's preferences? Select yes. +will inform you that The user has not logged on before and asks you +Do you wish to save the user's preferences?. Select yes.

    Once the Windows 9x / Me client comes up with the desktop, you should be able -to examine the contents of the directory specified in the logon path +to examine the contents of the directory specified in the logon path on the samba server and verify that the Desktop, Start Menu, Programs and Nethood folders have been created.

    @@ -171,14 +160,14 @@ the newest folders and short-cuts 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 the remote profile. Basically, if -you have any errors reported by the Windows 9x / Me machine, check the Unix file +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 then next logs in, they will be told that they are logging in "for the first time". -

    Warning

    +

    Warning

    Before deleting the contents of the directory listed in the ProfilePath (this is likely to be c:\windows\profiles\username), ask them if they @@ -189,7 +178,7 @@ they will be told that they are logging in "for the first time". This will have the effect of removing the local (read-only hidden system file) user.DAT in their profile directory, as well as the local "desktop", "nethood", "start menu" and "programs" folders. -

    1. +

    1. instead of logging in under the [user, password, domain] dialog, press escape.

    2. @@ -206,7 +195,7 @@ they will be told that they are logging in "for the first time".

    3. log off the windows 9x / Me client.

    4. - check the contents of the profile path (see logon path described + check the contents of the profile path (see logon path described above), and delete the user.DAT or user.MAN file for the user, making a backup if required.

    @@ -218,14 +207,14 @@ If you have access to an Windows NT4/200x server, then first set up roaming prof 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. +through the logon path parameter.

    There is a parameter that is now available for use with NT Profiles: -logon drive. This should be set to H: or any other drive, and -should be used in conjunction with the new "logon home" parameter. +logon drive. This should be set to 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 @@ -247,7 +236,7 @@ turns a profile into a mandatory one.

    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. @@ -266,8 +255,7 @@ profile on the MS Windows workstation as follows: Click on the 'Look in" area that lists the machine name, when you click here it will open up a selection box. Click on the domain to which the profile must be accessible. -

      Note

      You will need to log on if a logon box opens up. Eg: In the connect - as: MIDEARTH\root, password: mypassword.

    2. +

      Note

      You will need to log on if a logon box opens up. Eg: In the connect as: DOMAIN\root, password: mypassword.

    3. To make the profile capable of being used by anyone select 'Everyone'

    4. Click OK. The Selection box will close. @@ -275,12 +263,12 @@ profile on the MS Windows workstation as follows: Now click on the Ok button to create the profile in the path you nominated.

    -Done. You now have a profile that can be edited using the samba-3.0.0 +Done. You now have a profile that can be edited using the samba profiles tool.

    Note

    Under NT/2K the use of mandatory profiles forces the use of MS Exchange storage of mail data. That keeps desktop profiles usable. -

    Note

    1. +

    Procedure 24.2. Windows XP Service Pack 1

    1. This 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 Active Directory. The policy is:

      Computer Configuration\Administrative Templates\System\User @@ -297,7 +285,7 @@ On the XP workstation log in with an Administrator account.

    2. Click: Start, Run

    3. Type: mmc

    4. Click: OK

    5. A Microsoft Management Console should appear.

    6. Click: File, Add/Remove Snap-in..., Add

    7. Double-Click: Group Policy

    8. Click: Finish, Close

    9. Click: OK

    10. In the "Console Root" window:

    11. Expand: Local Computer Policy, Computer Configuration, Administrative Templates, System, User Profiles

    12. Double-Click: Do not check for user ownership of Roaming Profile Folders

    13. Select: Enabled

    14. Click: OK

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

    16. Reboot

    Sharing Profiles between W9x/Me and NT4/200x/XP workstations

    + changed).

  • Reboot

    • Sharing Profiles between W9x/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 @@ -308,18 +296,18 @@ version resulting in loss of profile information content when that user logs on again with the newer version of MS Windows.

    If you then want to share the same Start Menu / Desktop with W9x/Me, you will -need to specify a common location for the profiles. The smb.conf parameters -that need to be common are logon path and -logon home. +need to specify a common 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 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

    +

    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.

    @@ -336,17 +324,13 @@ domain is not a member of a trust relationship with your NT4 PDC.

    c:\temp\foobar

  • Click on the button Change in the Permitted to use box.

  • Click on the group 'Everyone' and then click OK. This closes the 'choose user' box.

  • Now click OK.

    • Follow the above 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 smbpasswd to do -this. Read the man page.

    -With Samba-3.0.0 alpha code you can import all you NT4 domain accounts -using the net samsync method. This way you can retain your profile -settings as well as all your users. -

    moveuser.exe

    +this. Read the man page.

    moveuser.exe

    The W2K 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 user name to change. -

    Get SID

    +

    Get SID

    You can identify the SID by using GetSID.exe from the Windows NT Server 4.0 Resource Kit.

    @@ -359,7 +343,7 @@ users who have logged 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 of 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, but as the user logs out all changes made will be lost. If it is desired to NOT allow the @@ -375,7 +359,7 @@ 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 affect a mandatory profile. -

    Creating/Managing Group Profiles

    +

    Creating/Managing Group Profiles

    Most organisations are arranged into departments. There is a nice benefit in this fact since usually most users in a department will require the same desktop applications and the same desktop layout. MS Windows NT4/200x/XP will allow the @@ -390,14 +374,14 @@ 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 optimised 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.

    @@ -409,7 +393,7 @@ select User Profiles, click on the enable box. Do To modify the registry directly, launch the Registry Editor (regedit.exe), select the hive HKEY_LOCAL_MACHINE\Network\Logon. Now add a DWORD type key with the name "User Profiles", to enable user profiles set the value to 1, to disable user profiles set it to 0. -

    How User Profiles Are Handled in Windows 9x / Me?

    +

    How User Profiles Are Handled in 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: @@ -425,7 +409,7 @@ If a User Profile is not found in either location, the Default User Profile from machine is used and is 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:\WinNT\Profiles. Under this directory on a clean install there will be @@ -436,7 +420,7 @@ system users. The Default User directory contains menu customisable 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)

    +

    • All Users settings

    • Default User settings (contains the default NTUser.DAT file)

    When a user logs onto an MS Windows NT4 machine that is a member of a Microsoft security domain the following steps are followed in respect of profile handling:

    1. @@ -468,8 +452,8 @@ will stored in the %SystemRoot%\Profiles\%USERNAME% lo also remain stored in the same way, unless the following registry key is created: 

      -	HKEY_LOCAL_MACHINE\SYSTEM\Software\Microsoft\Windows NT\CurrentVersion\winlogon\
-	"DeleteRoamingCache"=dword:00000001
+HKEY_LOCAL_MACHINE\SYSTEM\Software\Microsoft\Windows NT\CurrentVersion\
+winlogon\"DeleteRoamingCache"=dword:00000001

      In which case, the local copy (in %SystemRoot%\Profiles\%USERNAME%) will be @@ -488,7 +472,7 @@ are controlled by entries on Windows NT4 is:

      The above hive key contains a list of automatically managed folders. The default entries are:

      -

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

      +

      Table 24.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:

      @@ -496,8 +480,8 @@ The registry key that contains the location of the default profile settings is:

      The default entries are: -

      Table 24.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 24.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 can not participate in domain security, can not 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 @@ -546,7 +530,7 @@ are controlled by entries on Windows 200x/XP is:

    The above hive key contains a list of automatically managed folders. The default entries are:

    -

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

    +

    Table 24.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. @@ -562,18 +546,21 @@ You could also use:

    \\SambaServer\FolderShare\%USERNAME%

    in which case the default folders will be stored in the server named SambaServer in the share called FolderShare under a directory that has the name of the MS Windows -user as seen by the Linux/Unix file system. +user as seen by the Linux/UNIX file system.

    Please note that once you have created a default profile share, you MUST migrate a user's profile (default or custom) to it.

    MS Windows 200x/XP profiles may be Local or Roaming. A roaming profile will be cached locally unless the following registry key is created: -

    HKEY_LOCAL_MACHINE\SYSTEM\Software\Microsoft\Windows NT\CurrentVersion\winlogon\"DeleteRoamingCache"=dword:00000001

    +

    +

    +HKEY_LOCAL_MACHINE\SYSTEM\Software\Microsoft\Windows NT\CurrentVersion\
+	winlogon\"DeleteRoamingCache"=dword:00000001

    In which case, the local cache copy will be deleted on logout. -

    Common Errors

    +

    Common Errors

    The following are some typical errors/problems/questions that have been asked. -

    How does one set up roaming profiles for just one (or a few) user/s or group/s?

    +

    Setting up roaming profiles for just a few user's or group's?

    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 @@ -585,42 +572,40 @@ those machines on which roaming profile support is NOT wanted it is then necessary to disable roaming profile handling in the registry of each such machine.

    -With samba-3.0.0 (soon to be released) you can have a global profile -setting in smb.conf _AND_ you can over-ride this by per-user settings +With samba-3 you can have a global profile +setting in smb.conf _AND_ you can over-ride this by per-user settings using the Domain User Manager (as with MS Windows NT4/ Win 2Kx).

    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 can not change)
    A group profile (really should be mandatory ie:unchangable)

    Can NOT use Roaming Profiles

    +

    • A profile unique to that user

    • A mandatory profile (one the user can not change)

    • A group profile (really should be mandatory ie:unchangable)

    Can NOT use Roaming Profiles

    +A user requested the following: “ - I dont want Roaming profile to be implemented, I just want to give users - local profiles only. -... - Please help me I am totally lost with this error from past two days I tried - everything and googled around quite a bit but of no help. Please help me. +I do not want Roaming profiles to be implemented. I want to give users a local profile alone. ... +Please help me 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. ”

    -Your choices are: - - -

    Local profiles

    - I know of no registry keys that will allow auto-deletion of LOCAL profiles on log out -

    Roaming profiles

    -

    can use auto-delete on logout option
    requires a registry key change on workstation

    - - Your choices are: - -

    Personal Roaming profiles

    - - should be preserved on a central server - - workstations 'cache' (store) a local copy - - used in case the profile can not be downloaded - at next logon -

    Group profiles

    - loaded from a central place

    Mandatory profiles

    - - can be personal or group - - can NOT be changed (except by an administrator -

    +The choices are: +

    Local profiles:

    + I know of no registry keys that will allow auto-deletion of LOCAL profiles on log out +

    Roaming profiles:

    + As a user logs onto the network a centrally stored profile is copied to the workstation + to form a local profile. This local profile will persist (remain on the workstation disk) + unless a registry key is changed that will cause this profile to be automatically deleted + on logout. +

    +The Roaming Profile choices are: +

    Personal Roaming profiles

    + These are typically stored in a profile share on a central (or conveniently located + local) server. +

    + Workstations 'cache' (store) a local copy of the profile. This cached copy is used when + the profile can not be downloaded at next logon. +

    Group profiles

    These are loaded from a central profile server

    Mandatory profiles

    + Mandatory profiles can be created for a user as well as for any group that a user + is a member of. Mandatory profiles can NOT be changed by ordinary users. Only the administrator + can change or reconfigure a mandatory profile.

    - -

    A WinNT4/2K/XP profile can vary in size from 130KB to off the scale. Outlook PST files are most often part of the profile and can be many GB in size. On average (in a well controlled environment) roaming profile size of @@ -634,47 +619,34 @@ controls of how they can be changed as well as good discipline make up for a problem free site.

    Microsoft's answer to the PST problem is to store all email in an MS -Exchange Server back-end. But this is another story ...! -

    -So, having LOCAL profiles means: - -

    If lots of users user each machine - lot's of local disk storage needed for local profiles
    Every workstation the user logs into has it's own profile - can be very different from machine to machine

    - -On the other hand, having roaming profiles means: -

    The network administrator can control EVERY aspect of user profiles
    With the use of mandatory profiles - a drastic reduction in network management overheads
    User unhappiness about not being able to change their profiles soon fades as they get used to being able to work reliably

    - +Exchange Server back-end. This removes the need for a PST file.

    -I have managed and installed MANY NT/2K networks and have NEVER found one -where users who move from machine to machine are happy with local -profiles. In the long run local profiles bite them. -

    Changing the default profile

    “ -When the client tries to logon to the PDC it looks for a profile to download -where do I put this default profile. +LOCAL profiles mean: +

    • If each machine is used my many users then much local disk storage is needed for local profiles

    • Every workstation the user logs into has it's 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 drasitcally reduces network management overheads.

    • In the long run users will be experience fewer problems.

    Changing the default profile

    +Question: +“ +When the client logs onto the domain controller it searches for a profile to download, +where do I put this default profile? ”

    -Firstly, your samba server need to be configured as a domain controller. -

    -	server = user
-    os level = 32 (or more)
-	domain logons = Yes
-

    -Plus you need to have a [netlogon] share that is world readable. +Firstly, 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 an [netlogon] share that is world readable. It is a good idea to add a logon script to pre-set 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 auto-deletion of roaming profile from the local -workstation cache (disk storage) you need to use the Group Policy Editor +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.

    -Oh, of course the windows clients need to be members of the domain. -Workgroup machines do NOT do network logons - so they never see domain -profiles. +Windows clients need to be members of the domain. Workgroup machines do NOT use network logons so +they do not interoperate with domain profiles.

    -Secondly, for roaming profiles you need: - - logon path = \\%N\profiles\%U (with some such path) - logon drive = H: (Z: is the default) - - Plus you need a PROFILES share that is world writable. -

    Prev Up Next
    Chapter 23. System and Account Policies Home Chapter 25. PAM based Distributed Authentication
    +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.

    +

    Prev Up Next
    Chapter 23. System and Account Policies Home Chapter 25. PAM based Distributed Authentication
    diff --git a/docs/htmldocs/SWAT.html b/docs/htmldocs/SWAT.html index b4067d75d8..30df1ed778 100644 --- a/docs/htmldocs/SWAT.html +++ b/docs/htmldocs/SWAT.html @@ -1,4 +1,4 @@ -Chapter 32. SWAT - The Samba Web Administration Tool
    Chapter 32. SWAT - The Samba Web Administration Tool
    Prev Part IV. Migration and Updating Next

    Chapter 32. SWAT - The Samba Web Administration Tool

    John H. Terpstra

    Samba Team

    April 21, 2003

    Table of Contents

    Features and Benefits
    Enabling SWAT for use
    Securing SWAT through SSL
    The SWAT Home Page
    Global Settings
    Share Settings
    Printers Settings
    The SWAT Wizard
    The Status Page
    The View Page
    The Password Change Page

    +Chapter 32. SWAT - The Samba Web Administration Tool

    Chapter 32. SWAT - The Samba Web Administration Tool
    Prev Part IV. Migration and Updating Next

    Chapter 32. SWAT - The Samba Web Administration Tool

    John H. Terpstra

    Samba Team

    April 21, 2003

    Table of Contents

    Features and Benefits
    Enabling SWAT for use
    Securing SWAT through SSL
    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 or otherwise 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 will allow web based configuration @@ -6,7 +6,7 @@ of samba. It has a wizard that may help to get samba configured quickly, it has sensitive help on each smb.conf parameter, it provides for monitoring of current state of connection information, and it allows network wide MS Windows network password management. -

    Features and Benefits

    +

    Features and Benefits

    There are network administrators who believe that it is a good idea to write systems documentation inside configuration files, for them SWAT will aways be a nasty tool. SWAT does not store the configuration file in any intermediate form, rather, it stores only the @@ -18,9 +18,9 @@ internal ordering. So before using SWAT please be warned - SWAT will completely replace your smb.conf with a fully optimised file that has been stripped of all comments you might have placed there and only non-default settings will be written to the file. -

    Enabling SWAT for use

    +

    Enabling SWAT for use

    SWAT should be installed to run via the network super daemon. Depending on which system -your Unix/Linux system has you will have either an inetd or +your UNIX/Linux system has you will have either an inetd or xinetd based system.

    The nature and location of the network super-daemon varies with the operating system @@ -72,7 +72,7 @@ So long as you log onto SWAT as the user rootHOME, GLOBALS, SHARES, PRINTERS, WIZARD, STATUS, VIEW, PASSWORD. -

    Securing SWAT through SSL

    +

    Securing SWAT through SSL

    Lots of people have asked about how to setup SWAT with SSL to allow for secure remote administration of Samba. Here is a method that works, courtesy of Markus Krieger

    @@ -82,22 +82,22 @@ Modifications to the swat setup are as following:

  • generate certificate and private key - 

    +
     root# /usr/bin/openssl req -new -x509 -days 365 -nodes -config \
- 	/usr/share/doc/packages/stunnel/stunnel.cnf \
+	/usr/share/doc/packages/stunnel/stunnel.cnf \
 	-out /etc/stunnel/stunnel.pem -keyout /etc/stunnel/stunnel.pem
-

  • +

  • remove swat-entry from [x]inetd

  • start stunnel - 

    +
     root# stunnel -p /etc/stunnel/stunnel.pem -d 901 \
 	 -l /usr/local/samba/bin/swat swat 
-

    • +

    afterwords simply contact to swat by using the URL https://myhost:901, accept the certificate and the SSL connection is up. -

    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 Samba-HOWTO-Collection (this document) as well as the O'Reilly book "Using Samba". @@ -105,15 +105,14 @@ document) as well as the O'Reilly book "Using Samba". Administrators who wish to validate their samba configuration may obtain useful information from the man pages for the diagnostic utilities. These are available from the SWAT home page also. One diagnostic tool that is NOT mentioned on this page, but that is particularly -useful is ethereal, available from -http://www.ethereal.com. +useful is ethereal.

    Warning

    SWAT can be configured to run in demo mode. This is NOT recommended as it runs SWAT without authentication and with full administrative ability. ie: Allows 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 any production environment. -

    Global Settings

    +

    Global Settings

    The Globals button will expose a page that allows configuration of the global parameters in smb.conf. There are three levels of exposure of the parameters:

    • @@ -126,8 +125,8 @@ in smb.conf. There are three levels of exposure of the parameters: will want to tamper with.

    To switch to other than Basic editing ability click on either the -Advanced or the Developer dial, then click the -Commit Changes button. +Advanced or the Developer button. You may also +do this by clicking on the radio button, then click the Commit Changes button.

    After making any changes to configuration parameters make sure that you click on the Commit Changes button before moving to another area otherwise @@ -135,7 +134,7 @@ your changes will be immediately lost.

    Note

    SWAT has context sensitive help. To find out what each parameter is for simply click 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, select the share you wish to operate on, then to edit the settings click on the @@ -145,7 +144,7 @@ select the share you wish to operate on, then to edit the settings click on the To create a new share, next to the button labelled 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, select the printer you wish to operate on, then to edit the settings click on the @@ -155,7 +154,7 @@ select the printer you wish to operate on, then to edit the settings click on th To create a new printer, next to the button labelled 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 if the SWAT Wizard is to help the Microsoft knowledgeable network administrator to configure Samba with a minimum of effort.

    @@ -171,7 +170,7 @@ Finally, there are a limited set of options that will determine what type of ser will be configured for, whether it will be a WINS server, participate as a WINS client, or operate with no WINS support. By clicking on 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. Firstly, it allows control of the samba daemons. The key daemons that create the samba server environment are: smbd, nmbd, winbindd.

    @@ -182,11 +181,11 @@ conditions with minimal effort.

    Lastly, 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

    This page allows the administrator to view the optimised smb.conf file and, if you are particularly masochistic, will permit 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. This tool allows the creation, deletion, deactivation and reactivation of MS Windows networking users on the local machine. Alternatively, you can use this tool to change a local password for a user account. @@ -197,4 +196,4 @@ required.

    One popular use for this tool is to change user passwords across a range of remote MS Windows servers. -

    Prev Up Next
    Chapter 31. Migration from NT4 PDC to Samba-3 PDC Home Part V. Troubleshooting
    +

    Prev Up Next
    Chapter 31. Migration from NT4 PDC to Samba-3 PDC Home Part V. Troubleshooting
    diff --git a/docs/htmldocs/Samba-Developers-Guide.html b/docs/htmldocs/Samba-Developers-Guide.html index 603c87d574..97e48f3e27 100644 --- a/docs/htmldocs/Samba-Developers-Guide.html +++ b/docs/htmldocs/Samba-Developers-Guide.html @@ -12,10 +12,7 @@ Please send updates to Jelmer Vernooij. This documentation is distributed under the GNU General Public License (GPL) version 2. A copy of the license is included with the Samba source distribution. A copy can be found on-line at http://www.fsf.org/licenses/gpl.txt -">

    SAMBA Developers Guide

    SAMBA Team

    Attributions.  -

    Definition of NetBIOS Protocol and Name Resolution Modes

    • Luke Leighton

    Samba Architecture

    • Dan Shearer

    The samba DEBUG system

    • Chris Hertel

    Coding Suggestions

    • Steve French

    • Simo Sorce

    • Andrew Bartlett

    • Tim Potter

    • Martin Pool

    Samba Internals
    The smb.conf file

    • Chris Hertel

    NetBIOS in a Unix World

    • Andrew Tridgell

    Tracing samba system calls

    • Andrew Tridgell

    Finding useful information on windows
    NT Domain RPC's
    Samba Printing Internals

    • Gerald Carter

    Samba WINS Internals

    • Gerald Carter

    The Upcoming SAM System

    • Andrew Bartlett

    LanMan and NT Password Encryption
    Modules
    RPC Pluggable Modules
    VFS Modules
    Notes to packagers

    • Jelmer Vernooij

    Contributing code

    - -

    Abstract

    +">

    SAMBA Developers Guide

    Abstract

    Last Update : Fri Jun 6 00:45:54 CEST 2003

    This book is a collection of documents that might be useful for @@ -29,15 +26,15 @@ Please send updates to Jelmer Ve This documentation is distributed under the GNU General Public License (GPL) version 2. A copy of the license is included with the Samba source distribution. A copy can be found on-line at http://www.fsf.org/licenses/gpl.txt -

    Table of Contents

    1. Definition of NetBIOS Protocol and Name Resolution Modes
    NETBIOS
    BROADCAST NetBIOS
    NBNS NetBIOS
    2. Samba Architecture
    Introduction
    Multithreading and Samba
    Threading smbd
    Threading nmbd
    nbmd Design
    3. The samba DEBUG system
    New Output Syntax
    The DEBUG() Macro
    The DEBUGADD() Macro
    The DEBUGLVL() Macro
    New Functions
    dbgtext()
    dbghdr()
    format_debug_text()
    4. Coding Suggestions
    5. Samba Internals
    Character Handling
    The new functions
    Macros in byteorder.h
    CVAL(buf,pos)
    PVAL(buf,pos)
    SCVAL(buf,pos,val)
    SVAL(buf,pos)
    IVAL(buf,pos)
    SVALS(buf,pos)
    IVALS(buf,pos)
    SSVAL(buf,pos,val)
    SIVAL(buf,pos,val)
    SSVALS(buf,pos,val)
    SIVALS(buf,pos,val)
    RSVAL(buf,pos)
    RIVAL(buf,pos)
    RSSVAL(buf,pos,val)
    RSIVAL(buf,pos,val)
    LAN Manager Samba API
    Parameters
    Return value
    Code character table
    6. The smb.conf file
    Lexical Analysis
    Handling of Whitespace
    Handling of Line Continuation
    Line Continuation Quirks
    Syntax
    About params.c
    7. NetBIOS in a Unix World
    Introduction
    Usernames
    File Ownership
    Passwords
    Locking
    Deny Modes
    Trapdoor UIDs
    Port numbers
    Protocol Complexity
    8. Tracing samba system calls
    9. Finding useful information on windows
    Netlogon debugging output
    10. NT Domain RPC's
    Introduction
    Sources
    Credits
    Notes and Structures
    Notes
    Enumerations
    Structures
    MSRPC over Transact Named Pipe
    MSRPC Pipes
    Header
    Tail
    RPC Bind / Bind Ack
    NTLSA Transact Named Pipe
    LSA Open Policy
    LSA Query Info Policy
    LSA Enumerate Trusted Domains
    LSA Open Secret
    LSA Close
    LSA Lookup SIDS
    LSA Lookup Names
    NETLOGON rpc Transact Named Pipe
    LSA Request Challenge
    LSA Authenticate 2
    LSA Server Password Set
    LSA SAM Logon
    LSA SAM Logoff
    \\MAILSLOT\NET\NTLOGON
    Query for PDC
    SAM Logon
    SRVSVC Transact Named Pipe
    Net Share Enum
    Net Server Get Info
    Cryptographic side of NT Domain Authentication
    Definitions
    Protocol
    Comments
    SIDs and RIDs
    Well-known SIDs
    Well-known RIDS
    11. Samba Printing Internals
    Abstract
    +

    Table of Contents

    Attributions
    1. Definition of NetBIOS Protocol and Name Resolution Modes
    NETBIOS
    BROADCAST NetBIOS
    NBNS NetBIOS
    2. Samba Architecture
    Introduction
    Multithreading and Samba
    Threading smbd
    Threading nmbd
    nbmd Design
    3. The samba DEBUG system
    New Output Syntax
    The DEBUG() Macro
    The DEBUGADD() Macro
    The DEBUGLVL() Macro
    New Functions
    dbgtext()
    dbghdr()
    format_debug_text()
    4. Coding Suggestions
    5. Samba Internals
    Character Handling
    The new functions
    Macros in byteorder.h
    CVAL(buf,pos)
    PVAL(buf,pos)
    SCVAL(buf,pos,val)
    SVAL(buf,pos)
    IVAL(buf,pos)
    SVALS(buf,pos)
    IVALS(buf,pos)
    SSVAL(buf,pos,val)
    SIVAL(buf,pos,val)
    SSVALS(buf,pos,val)
    SIVALS(buf,pos,val)
    RSVAL(buf,pos)
    RIVAL(buf,pos)
    RSSVAL(buf,pos,val)
    RSIVAL(buf,pos,val)
    LAN Manager Samba API
    Parameters
    Return value
    Code character table
    6. The smb.conf file
    Lexical Analysis
    Handling of Whitespace
    Handling of Line Continuation
    Line Continuation Quirks
    Syntax
    About params.c
    7. NetBIOS in a Unix World
    Introduction
    Usernames
    File Ownership
    Passwords
    Locking
    Deny Modes
    Trapdoor UIDs
    Port numbers
    Protocol Complexity
    8. Tracing samba system calls
    9. Finding useful information on windows
    Netlogon debugging output
    10. NT Domain RPC's
    Introduction
    Sources
    Credits
    Notes and Structures
    Notes
    Enumerations
    Structures
    MSRPC over Transact Named Pipe
    MSRPC Pipes
    Header
    Tail
    RPC Bind / Bind Ack
    NTLSA Transact Named Pipe
    LSA Open Policy
    LSA Query Info Policy
    LSA Enumerate Trusted Domains
    LSA Open Secret
    LSA Close
    LSA Lookup SIDS
    LSA Lookup Names
    NETLOGON rpc Transact Named Pipe
    LSA Request Challenge
    LSA Authenticate 2
    LSA Server Password Set
    LSA SAM Logon
    LSA SAM Logoff
    \\MAILSLOT\NET\NTLOGON
    Query for PDC
    SAM Logon
    SRVSVC Transact Named Pipe
    Net Share Enum
    Net Server Get Info
    Cryptographic side of NT Domain Authentication
    Definitions
    Protocol
    Comments
    SIDs and RIDs
    Well-known SIDs
    Well-known RIDS
    11. Samba Printing Internals
    Abstract
    Printing Interface to Various Back ends -
    +
    Print Queue TDB's -
    +
    ChangeID and Client Caching of Printer Information -
    +
    Windows NT/2K Printer Change Notify -
    12. Samba WINS Internals
    WINS Failover
    13. The Upcoming SAM System
    Security in the 'new SAM'
    Standalone from UNIX
    Handles and Races in the new SAM
    Layers
    Application
    SAM Interface
    SAM Modules
    SAM Modules
    Special Module: sam_passdb
    sam_ads
    Memory Management
    Testing
    14. LanMan and NT Password Encryption
    Introduction
    How does it work?
    The smbpasswd file
    15. Modules
    Advantages
    Loading modules
    Static modules
    Shared modules
    Writing modules
    Static/Shared selection in configure.in
    16. RPC Pluggable Modules
    About
    General Overview
    17. VFS Modules
    The Samba (Posix) VFS layer
    The general interface
    Possible VFS operation layers
    The Interaction between the Samba VFS subsystem and the modules
    Initialization and registration
    How the Modules handle per connection data
    Upgrading to the New VFS Interface
    Upgrading from 2.2.* and 3.0aplha modules
    Some Notes
    Implement TRANSPARENT functions
    Implement OPAQUE functions
    18. Notes to packagers
    Versioning
    Modules
    19. Contributing code

    Chapter 1. Definition of NetBIOS Protocol and Name Resolution Modes

    Luke Leighton

    12 June 1997

    Table of Contents

    NETBIOS
    BROADCAST NetBIOS
    NBNS NetBIOS

    NETBIOS

    +

    12. Samba WINS Internals
    WINS Failover
    13. The Upcoming SAM System
    Security in the 'new SAM'
    Standalone from UNIX
    Handles and Races in the new SAM
    Layers
    Application
    SAM Interface
    SAM Modules
    SAM Modules
    Special Module: sam_passdb
    sam_ads
    Memory Management
    Testing
    14. LanMan and NT Password Encryption
    Introduction
    How does it work?
    The smbpasswd file
    15. Modules
    Advantages
    Loading modules
    Static modules
    Shared modules
    Writing modules
    Static/Shared selection in configure.in
    16. RPC Pluggable Modules
    About
    General Overview
    17. VFS Modules
    The Samba (Posix) VFS layer
    The general interface
    Possible VFS operation layers
    The Interaction between the Samba VFS subsystem and the modules
    Initialization and registration
    How the Modules handle per connection data
    Upgrading to the New VFS Interface
    Upgrading from 2.2.* and 3.0aplha modules
    Some Notes
    Implement TRANSPARENT functions
    Implement OPAQUE functions
    18. Notes to packagers
    Versioning
    Modules
    19. Contributing code

    Attributions

    Definition of NetBIOS Protocol and Name Resolution Modes

    • Luke Leighton

    Samba Architecture

    • Dan Shearer

    The samba DEBUG system

    • Chris Hertel

    Coding Suggestions

    • Steve French

    • Simo Sorce

    • Andrew Bartlett

    • Tim Potter

    • Martin Pool

    Samba Internals

    The smb.conf file

    • Chris Hertel

    NetBIOS in a Unix World

    • Andrew Tridgell

    Tracing samba system calls

    • Andrew Tridgell

    Finding useful information on windows

    NT Domain RPC's

    Samba Printing Internals

    • Gerald Carter

    Samba WINS Internals

    • Gerald Carter

    The Upcoming SAM System

    • Andrew Bartlett

    LanMan and NT Password Encryption

    Modules

    RPC Pluggable Modules

    VFS Modules

    Notes to packagers

    • Jelmer Vernooij

    Contributing code

    Chapter 1. Definition of NetBIOS Protocol and Name Resolution Modes

    Luke Leighton

    12 June 1997

    Table of Contents

    NETBIOS
    BROADCAST NetBIOS
    NBNS NetBIOS

    NETBIOS

    NetBIOS runs over the following tranports: TCP/IP; NetBEUI and IPX/SPX. Samba only uses NetBIOS over TCP/IP. For details on the TCP/IP NetBIOS Session Service NetBIOS Datagram Service, and NetBIOS Names, see @@ -78,7 +75,7 @@ NetBIOS names are either UNIQUE or GROUP. Only one application can claim a UNIQUE NetBIOS name on a network.

    There are two kinds of NetBIOS Name resolution: Broadcast and Point-to-Point. -

    BROADCAST NetBIOS

    +

    BROADCAST NetBIOS

    Clients can claim names, and therefore offer services on successfully claimed names, on their broadcast-isolated subnet. One way to get NetBIOS services (such as browsing: see ftp.microsoft.com/drg/developr/CIFS/browdiff.txt; and @@ -90,7 +87,7 @@ find that some of your hosts spend 95 percent of their time dealing with broadcast traffic. [If you have IPX/SPX on your LAN or WAN, you will find that this is already happening: a packet analyzer will show, roughly every twelve minutes, great swathes of broadcast traffic!]. -

    NBNS NetBIOS

    +

    NBNS NetBIOS

    rfc1001.txt describes, amongst other things, the implementation and use of, a 'NetBIOS Name Service'. NT/AS offers 'Windows Internet Name Service' which is fully rfc1001/2 compliant, but has had to take specific action @@ -131,7 +128,7 @@ WINS Clients therefore claim names from the WINS server. If the WINS server allows them to register a name, the client's NetBIOS session service can then offer services on this name. Other WINS clients will then contact the WINS server to resolve a NetBIOS name. -

    Chapter 2. Samba Architecture

    Dan Shearer

    November 1997

    Table of Contents

    Introduction
    Multithreading and Samba
    Threading smbd
    Threading nmbd
    nbmd Design

    Introduction

    +

    Chapter 2. Samba Architecture

    Dan Shearer

    November 1997

    Table of Contents

    Introduction
    Multithreading and Samba
    Threading smbd
    Threading nmbd
    nbmd Design

    Introduction

    This document gives a general overview of how Samba works internally. The Samba Team has tried to come up with a model which is the best possible compromise between elegance, portability, security @@ -142,7 +139,7 @@ It also tries to answer some of the frequently asked questions such as:

    1. Is Samba secure when running on Unix? The xyz platform? What about the root priveliges issue? -

    2. Pros and cons of multithreading in various parts of Samba

    3. Why not have a separate process for name resolution, WINS, and browsing?

    Multithreading and Samba

    +

  • Pros and cons of multithreading in various parts of Samba

  • Why not have a separate process for name resolution, WINS, and browsing?

    • Multithreading and Samba

    People sometimes tout threads as a uniformly good thing. They are very nice in their place but are quite inappropriate for smbd. nmbd is another matter, and multi-threading it would be very nice. @@ -159,7 +156,7 @@ smbd multi-threaded. Multi-threading would actually make Samba much slower, less scalable, less portable and much less robust. The fact that we use a separate process for each connection is one of Samba's biggest advantages. -

    Threading smbd

    +

    Threading smbd

    A few problems that would arise from a threaded smbd are:

    1. It's not only to create threads instead of processes, but you @@ -184,7 +181,7 @@ A few problems that would arise from a threaded smbd are:

    2. we couldn't use the system locking calls as the locking context of fcntl() is a process, not a thread. -

    Threading nmbd

    +

    Threading nmbd

    This would be ideal, but gets sunk by portability requirements.

    Andrew tried to write a test threads library for nmbd that used only @@ -211,7 +208,7 @@ packet that arrives. Having a pool of processes is possible but is nasty to program cleanly due to the enormous amount of shared data (in complex structures) between the processes. We can't rely on each platform having a shared memory system. -

    nbmd Design

    +

    nbmd Design

    Originally Andrew used recursion to simulate a multi-threaded environment, which use the stack enormously and made for really confusing debugging sessions. Luke Leighton rewrote it to use a @@ -228,11 +225,11 @@ a single process.

    Then Jeremy rewrote nmbd. The packet data in nmbd isn't what's on the wire. It's a nice format that is very amenable to processing but still -keeps the idea of a distinct packet. See "struct packet_struct" in +keeps the idea of a distinct packet. See "struct packet_struct" in nameserv.h. It has all the detail but none of the on-the-wire mess. This makes it ideal for using in disk or memory-based databases for browsing and WINS support. -

    Chapter 3. The samba DEBUG system

    Chris Hertel

    July 1998

    Table of Contents

    New Output Syntax
    The DEBUG() Macro
    The DEBUGADD() Macro
    The DEBUGLVL() Macro
    New Functions
    dbgtext()
    dbghdr()
    format_debug_text()

    New Output Syntax

    +

    Chapter 3. The samba DEBUG system

    Chris Hertel

    July 1998

    Table of Contents

    New Output Syntax
    The DEBUG() Macro
    The DEBUGADD() Macro
    The DEBUGLVL() Macro
    New Functions
    dbgtext()
    dbghdr()
    format_debug_text()

    New Output Syntax

    The syntax of a debugging log file is represented as: 

       >debugfile< :== { >debugmsg< }
@@ -285,16 +282,16 @@ by a newline.
 Note that in the above example the function names are not listed on
 the header line. That's because the example above was generated on an
 SGI Indy, and the SGI compiler doesn't support the __FUNCTION__ macro.
-

    The DEBUG() Macro

    +

    The DEBUG() Macro

    Use of the DEBUG() macro is unchanged. DEBUG() takes two parameters. The first is the message level, the second is the body of a function call to the Debug1() function.

    That's confusing.

    Here's an example which may help a bit. If you would write

    -printf( "This is a %s message.\n", "debug" );
+printf( "This is a %s message.\n", "debug" );

    to send the output to stdout, then you would write 

    -DEBUG( 0, ( "This is a %s message.\n", "debug" ) );
+DEBUG( 0, ( "This is a %s message.\n", "debug" ) );

    to send the output to the debug file. All of the normal printf() formatting escapes work. @@ -319,12 +316,12 @@ DEBUG() is called, the new input is simply appended. DEBUG() has been used to write partial lines. Here's a simple (dumb) example of the kind of thing I'm talking about: 

    -    DEBUG( 0, ("The test returned " ) );
+    DEBUG( 0, ("The test returned " ) );
     if( test() )
-      DEBUG(0, ("True") );
+      DEBUG(0, ("True") );
     else
-      DEBUG(0, ("False") );
-    DEBUG(0, (".\n") );
+      DEBUG(0, ("False") );
+    DEBUG(0, (".\n") );

    Without the format buffer, the output (assuming test() returned true) would look like this: @@ -336,35 +333,35 @@ would look like this: [1998/07/30 16:00:51, 0] file.c:function(261) .

    Which isn't much use. The format buffer kludge fixes this problem. -

    The DEBUGADD() Macro

    +

    The DEBUGADD() Macro

    In addition to the kludgey solution to the broken line problem described above, there is a clean solution. The DEBUGADD() macro never generates a header. It will append new text to the current debug message even if the format buffer is empty. The syntax of the DEBUGADD() macro is the same as that of the DEBUG() macro. 

    -    DEBUG( 0, ("This is the first line.\n" ) );
-    DEBUGADD( 0, ("This is the second line.\nThis is the third line.\n" ) );
+    DEBUG( 0, ("This is the first line.\n" ) );
+    DEBUGADD( 0, ("This is the second line.\nThis is the third line.\n" ) );

    Produces

         [1998/07/30 16:00:51, 0] file.c:function(512)
       This is the first line.
       This is the second line.
       This is the third line.
-

    The DEBUGLVL() Macro

    +

    The DEBUGLVL() Macro

    One of the problems with the DEBUG() macro was that DEBUG() lines tended to get a bit long. Consider this example from nmbd_sendannounce.c: 

    -  DEBUG(3,("send_local_master_announcement: type %x for name %s on subnet %s for workgroup %s\n",
+  DEBUG(3,("send_local_master_announcement: type %x for name %s on subnet %s for workgroup %s\n",
             type, global_myname, subrec->subnet_name, work->work_group));

    One solution to this is to break it down using DEBUG() and DEBUGADD(), as follows: 

    -  DEBUG( 3, ( "send_local_master_announcement: " ) );
-  DEBUGADD( 3, ( "type %x for name %s ", type, global_myname ) );
-  DEBUGADD( 3, ( "on subnet %s ", subrec->subnet_name ) );
-  DEBUGADD( 3, ( "for workgroup %s\n", work->work_group ) );
+  DEBUG( 3, ( "send_local_master_announcement: " ) );
+  DEBUGADD( 3, ( "type %x for name %s ", type, global_myname ) );
+  DEBUGADD( 3, ( "on subnet %s ", subrec->subnet_name ) );
+  DEBUGADD( 3, ( "for workgroup %s\n", work->work_group ) );

    A similar, but arguably nicer approach is to use the DEBUGLVL() macro. This macro returns True if the message level is less than or equal to @@ -372,10 +369,10 @@ the global DEBUGLEVEL value, so: 

       if( DEBUGLVL( 3 ) )
     {
-    dbgtext( "send_local_master_announcement: " );
-    dbgtext( "type %x for name %s ", type, global_myname );
-    dbgtext( "on subnet %s ", subrec->subnet_name );
-    dbgtext( "for workgroup %s\n", work->work_group );
+    dbgtext( "send_local_master_announcement: " );
+    dbgtext( "type %x for name %s ", type, global_myname );
+    dbgtext( "on subnet %s ", subrec->subnet_name );
+    dbgtext( "for workgroup %s\n", work->work_group );
     }

    (The dbgtext() function is explained below.)

    There are a few advantages to this scheme:

    1. The test is performed only once. @@ -385,7 +382,7 @@ within the DEBUGLVL() block.

    2. Processing that is only relevant to debug output can be contained within the DEBUGLVL() block. -

    New Functions

    dbgtext()

    +

    New Functions

    dbgtext()

    This function prints debug message text to the debug file (and possibly to syslog) via the format buffer. The function uses a variable argument list just like printf() or Debug1(). The @@ -394,7 +391,7 @@ and then passed to format_debug_text(). If you use DEBUGLVL() you will probably print the body of the message using dbgtext(). -

    dbghdr()

    +

    dbghdr()

    This is the function that writes a debug message header. Headers are not processed via the format buffer. Also note that if the format buffer is not empty, a call to dbghdr() will not @@ -402,7 +399,7 @@ produce any output. See the comments in dbghdr() for more info.

    It is not likely that this function will be called directly. It is used by DEBUG() and DEBUGADD(). -

    format_debug_text()

    +

    format_debug_text()

    This is a static function in debug.c. It stores the output text for the body of the message in a buffer until it encounters a newline. When the newline character is found, the buffer is @@ -484,7 +481,7 @@ Here are some other suggestions: reason: consistency

  • don't explicitly extern functions (they are autogenerated by - "make proto" into proto.h) + "make proto" into proto.h) reason: consistency

  • use endian safe macros when unpacking SMBs (see byteorder.h and @@ -553,7 +550,7 @@ The suggestions above are simply that, suggestions, but the information may help in reducing the routine rework done on new code. The preceeding list is expected to change routinely as new support routines and macros are added. -

    • Chapter 5. Samba Internals

    8 May 1996

    Table of Contents

    Character Handling
    The new functions
    Macros in byteorder.h
    CVAL(buf,pos)
    PVAL(buf,pos)
    SCVAL(buf,pos,val)
    SVAL(buf,pos)
    IVAL(buf,pos)
    SVALS(buf,pos)
    IVALS(buf,pos)
    SSVAL(buf,pos,val)
    SIVAL(buf,pos,val)
    SSVALS(buf,pos,val)
    SIVALS(buf,pos,val)
    RSVAL(buf,pos)
    RIVAL(buf,pos)
    RSSVAL(buf,pos,val)
    RSIVAL(buf,pos,val)
    LAN Manager Samba API
    Parameters
    Return value
    Code character table

    Character Handling

    +

    Chapter 5. Samba Internals

    8 May 1996

    Table of Contents

    Character Handling
    The new functions
    Macros in byteorder.h
    CVAL(buf,pos)
    PVAL(buf,pos)
    SCVAL(buf,pos,val)
    SVAL(buf,pos)
    IVAL(buf,pos)
    SVALS(buf,pos)
    IVALS(buf,pos)
    SSVAL(buf,pos,val)
    SIVAL(buf,pos,val)
    SSVALS(buf,pos,val)
    SIVALS(buf,pos,val)
    RSVAL(buf,pos)
    RIVAL(buf,pos)
    RSSVAL(buf,pos,val)
    RSIVAL(buf,pos,val)
    LAN Manager Samba API
    Parameters
    Return value
    Code character table

    Character Handling

    This section describes character set handling in Samba, as implemented in Samba 3.0 and above

    @@ -563,12 +560,12 @@ strings to/from DOS codepages. The problem is that there was no way of telling if a particular char* is in dos codepage or unix codepage. This led to a nightmare of code that tried to cope with particular cases without handlingt the general case. -

    The new functions

    +

    The new functions

    The new system works like this:

    1. - all char* strings inside Samba are "unix" strings. These are - multi-byte strings that are in the charset defined by the "unix - charset" option in smb.conf. + all char* strings inside Samba are "unix" strings. These are + multi-byte strings that are in the charset defined by the "unix + charset" option in smb.conf.

    2. there is no single fixed character set for unix strings, but any character set that is used does need the following properties: @@ -621,32 +618,32 @@ The new system works like this: like strchr_m(). I know this is very slow, and we will eventually speed it up but right now we want this stuff correct not fast.

    3. - all lp_ functions now return unix strings. The magic "DOS" flag on + all lp_ functions now return unix strings. The magic "DOS" flag on parameters is gone.

    4. all vfs functions take unix strings. Don't convert when passing to them -

    Macros in byteorder.h

    +

    Macros in byteorder.h

    This section describes the macros defined in byteorder.h. These macros are used extensively in the Samba code. -

    CVAL(buf,pos)

    +

    CVAL(buf,pos)

    returns the byte at offset pos within buffer buf as an unsigned character. -

    PVAL(buf,pos)

    returns the value of CVAL(buf,pos) cast to type unsigned integer.

    SCVAL(buf,pos,val)

    sets the byte at offset pos within buffer buf to value val.

    SVAL(buf,pos)

    +

    PVAL(buf,pos)

    returns the value of CVAL(buf,pos) cast to type unsigned integer.

    SCVAL(buf,pos,val)

    sets the byte at offset pos within buffer buf to value val.

    SVAL(buf,pos)

    returns the value of the unsigned short (16 bit) little-endian integer at offset pos within buffer buf. An integer of this type is sometimes - refered to as "USHORT". -

    IVAL(buf,pos)

    returns the value of the unsigned 32 bit little-endian integer at offset -pos within buffer buf.

    SVALS(buf,pos)

    returns the value of the signed short (16 bit) little-endian integer at -offset pos within buffer buf.

    IVALS(buf,pos)

    returns the value of the signed 32 bit little-endian integer at offset pos -within buffer buf.

    SSVAL(buf,pos,val)

    sets the unsigned short (16 bit) little-endian integer at offset pos within -buffer buf to value val.

    SIVAL(buf,pos,val)

    sets the unsigned 32 bit little-endian integer at offset pos within buffer -buf to the value val.

    SSVALS(buf,pos,val)

    sets the short (16 bit) signed little-endian integer at offset pos within -buffer buf to the value val.

    SIVALS(buf,pos,val)

    sets the signed 32 bit little-endian integer at offset pos withing buffer -buf to the value val.

    RSVAL(buf,pos)

    returns the value of the unsigned short (16 bit) big-endian integer at -offset pos within buffer buf.

    RIVAL(buf,pos)

    returns the value of the unsigned 32 bit big-endian integer at offset -pos within buffer buf.

    RSSVAL(buf,pos,val)

    sets the value of the unsigned short (16 bit) big-endian integer at + refered to as "USHORT". +

    IVAL(buf,pos)

    returns the value of the unsigned 32 bit little-endian integer at offset +pos within buffer buf.

    SVALS(buf,pos)

    returns the value of the signed short (16 bit) little-endian integer at +offset pos within buffer buf.

    IVALS(buf,pos)

    returns the value of the signed 32 bit little-endian integer at offset pos +within buffer buf.

    SSVAL(buf,pos,val)

    sets the unsigned short (16 bit) little-endian integer at offset pos within +buffer buf to value val.

    SIVAL(buf,pos,val)

    sets the unsigned 32 bit little-endian integer at offset pos within buffer +buf to the value val.

    SSVALS(buf,pos,val)

    sets the short (16 bit) signed little-endian integer at offset pos within +buffer buf to the value val.

    SIVALS(buf,pos,val)

    sets the signed 32 bit little-endian integer at offset pos withing buffer +buf to the value val.

    RSVAL(buf,pos)

    returns the value of the unsigned short (16 bit) big-endian integer at +offset pos within buffer buf.

    RIVAL(buf,pos)

    returns the value of the unsigned 32 bit big-endian integer at offset +pos within buffer buf.

    RSSVAL(buf,pos,val)

    sets the value of the unsigned short (16 bit) big-endian integer at offset pos within buffer buf to value val. -refered to as "USHORT".

    RSIVAL(buf,pos,val)

    sets the value of the unsigned 32 bit big-endian integer at offset -pos within buffer buf to value val.

    LAN Manager Samba API

    +refered to as "USHORT".

    RSIVAL(buf,pos,val)

    sets the value of the unsigned 32 bit big-endian integer at offset +pos within buffer buf to value val.

    LAN Manager Samba API

    This section describes the functions need to make a LAN Manager RPC call. This information had been obtained by examining the Samba code and the LAN Manager 2.0 API documentation. It should not be considered entirely @@ -659,7 +656,7 @@ call_api(int prcnt, int drcnt, int mprcnt, int mdrcnt,

    This function is defined in client.c. It uses an SMB transaction to call a remote api. -

    Parameters

    The parameters are as follows:

    1. +

      Parameters

      The parameters are as follows:

      1. prcnt: the number of bytes of parameters begin sent.

      2. drcnt: the number of bytes of data begin sent. @@ -692,8 +689,8 @@ in the manual, not the data which is actually passed. An ASCIIZ string describing the data structure which ought to be returned.

      3. Any parameters which appear in the function call, as defined in the LAN -Manager API documentation, after the "Server" and up to and including the -"uLevel" parameters. +Manager API documentation, after the "Server" and up to and including the +"uLevel" parameters.

      4. An unsigned 16 bit integer which gives the size in bytes of the buffer we will use to receive the returned array of data structures. Presumably this @@ -704,7 +701,7 @@ substructures apply, this string is of zero length.

      The code in client.c always calls call_api() with no data. It is unclear when a non-zero length data buffer would be sent. -

      Return value

      +

      Return value

      The returned parameters (pointed to by rparam), in their order of appearance are:

      1. An unsigned 16 bit integer which contains the API function's return code. @@ -721,9 +718,9 @@ It is also possible that this may sometimes be the number of bytes returned.

      When call_api() returns, rparam points to the returned parameters. The first if these is the result code. It will be zero if the API call -suceeded. This value by be read with "SVAL(rparam,0)". +suceeded. This value by be read with "SVAL(rparam,0)".

      -The second parameter may be read as "SVAL(rparam,2)". It is a 16 bit offset +The second parameter may be read as "SVAL(rparam,2)". It is a 16 bit offset which indicates what the base address of the returned data buffer was when it was built on the server. It should be used to correct pointer before use. @@ -732,10 +729,10 @@ The returned data buffer contains the array of returned data structures. Note that all pointers must be adjusted before use. The function fix_char_ptr() in client.c can be used for this purpose.

      -The third parameter (which may be read as "SVAL(rparam,4)") has something to +The third parameter (which may be read as "SVAL(rparam,4)") has something to do with indicating the amount of data returned or possibly the amount of data which can be returned if enough buffer space is allowed. -

    Code character table

    +

    Code character table

    Certain data structures are described by means of ASCIIz strings containing code characters. These are the code characters:

    1. @@ -758,7 +755,7 @@ r pointer to returned data buffer??? L length in bytes of returned data buffer???

    2. h number of bytes of information available??? -

    Chapter 6. The smb.conf file

    Chris Hertel

    November 1997

    Table of Contents

    Lexical Analysis
    Handling of Whitespace
    Handling of Line Continuation
    Line Continuation Quirks
    Syntax
    About params.c

    Lexical Analysis

    +

    Chapter 6. The smb.conf file

    Chris Hertel

    November 1997

    Table of Contents

    Lexical Analysis
    Handling of Whitespace
    Handling of Line Continuation
    Line Continuation Quirks
    Syntax
    About params.c

    Lexical Analysis

    Basically, the file is processed on a line by line basis. There are four types of lines that are recognized by the lexical analyzer (params.c): @@ -785,7 +782,7 @@ ignores them. The latter two line types are scanned for These are the only tokens passed to the parameter loader (loadparm.c). Parameter names and values are divided from one another by an equal sign: '='. -

    Handling of Whitespace

    +

    Handling of Whitespace

    Whitespace is defined as all characters recognized by the isspace() function (see ctype(3C)) except for the newline character ('\n') The newline is excluded because it identifies the end of the line. @@ -800,7 +797,7 @@ the exception of carriage return characters ('\r'), all of which are removed.

  • Leading and trailing whitespace is removed from names and values. -

    • Handling of Line Continuation

    +

    Handling of Line Continuation

    Long section header and parameter lines may be extended across multiple lines by use of the backslash character ('\\'). Line continuation is ignored for blank and comment lines. @@ -823,7 +820,7 @@ line, plus the four preceeding the word 'with' in the second line. Line continuation characters are ignored on blank lines and at the end of comments. They are *only* recognized within section and parameter lines. -

    Line Continuation Quirks

    Note the following example:

    +

    Line Continuation Quirks

    Note the following example:

     	param name = parameter value string \
     \
     with line continuation.
@@ -847,7 +844,7 @@ terminating character, and the rest of the line is ignored.  The lines

    are read as

     	[section name]
     param name = value
-

    Syntax

    The syntax of the smb.conf file is as follows:

    +

    Syntax

    The syntax of the smb.conf file is as follows:

       <file>            :==  { <section> } EOF
   <section>         :==  <section header> { <parameter line> }
   <section header>  :==  '[' NAME ']'
@@ -866,12 +863,12 @@ terminating character, and the rest of the line is ignored.  The lines
 	A parameter line is divided into a NAME and a VALUE.  The *first*
 	equal sign on the line separates the NAME from the VALUE.  The
 	VALUE is terminated by a newline character (NL = '\n').
-

    About params.c

    +

    About params.c

    The parsing of the config file is a bit unusual if you are used to lex, yacc, bison, etc. Both lexical analysis (scanning) and parsing are performed by params.c. Values are loaded via callbacks to loadparm.c. -

    Chapter 7. NetBIOS in a Unix World

    Andrew Tridgell

    April 1995

    Table of Contents

    Introduction
    Usernames
    File Ownership
    Passwords
    Locking
    Deny Modes
    Trapdoor UIDs
    Port numbers
    Protocol Complexity

    Introduction

    +

    Chapter 7. NetBIOS in a Unix World

    Andrew Tridgell

    April 1995

    Table of Contents

    Introduction
    Usernames
    File Ownership
    Passwords
    Locking
    Deny Modes
    Trapdoor UIDs
    Port numbers
    Protocol Complexity

    Introduction

    This is a short document that describes some of the issues that confront a SMB implementation on unix, and how Samba copes with them. They may help people who are looking at unix<->PC @@ -879,7 +876,7 @@ interoperability.

    It was written to help out a person who was writing a paper on unix to PC connectivity. -

    Usernames

    +

    Usernames

    The SMB protocol has only a loose username concept. Early SMB protocols (such as CORE and COREPLUS) have no username concept at all. Even in later protocols clients often attempt operations @@ -890,20 +887,20 @@ Unix security is based around username/password pairs. A unix box should not allow clients to do any substantive operation without some sort of validation.

    -The problem mostly manifests itself when the unix server is in "share -level" security mode. This is the default mode as the alternative -"user level" security mode usually forces a client to connect to the +The problem mostly manifests itself when the unix server is in "share +level" security mode. This is the default mode as the alternative +"user level" security mode usually forces a client to connect to the server as the same user for each connected share, which is inconvenient in many sites.

    -In "share level" security the client normally gives a username in the -"session setup" protocol, but does not supply an accompanying -password. The client then connects to resources using the "tree -connect" protocol, and supplies a password. The problem is that the +In "share level" security the client normally gives a username in the +"session setup" protocol, but does not supply an accompanying +password. The client then connects to resources using the "tree +connect" protocol, and supplies a password. The problem is that the user on the PC types the username and the password in different contexts, unaware that they need to go together to give access to the server. The username is normally the one the user typed in when they -"logged onto" the PC (this assumes Windows for Workgroups). The +"logged onto" the PC (this assumes Windows for Workgroups). The password is the one they chose when connecting to the disk or printer.

    The user often chooses a totally different username for their login as @@ -916,9 +913,9 @@ in the vast majority of cases. The methods include username maps, the service%user syntax, the saving of session setup usernames for later validation and the derivation of the username from the service name (either directly or via the user= option). -

    File Ownership

    -The commonly used SMB protocols have no way of saying "you can't do -that because you don't own the file". They have, in fact, no concept +

    File Ownership

    +The commonly used SMB protocols have no way of saying "you can't do +that because you don't own the file". They have, in fact, no concept of file ownership at all.

    This brings up all sorts of interesting problems. For example, when @@ -928,13 +925,13 @@ receive the wrong date. This is because the utime() call under unix only succeeds for the owner of the file, or root, even if the file is world writeable. For security reasons Samba does all file operations as the validated user, not root, so the utime() fails. This can stuff -up shared development diectories as programs like "make" will not get +up shared development diectories as programs like "make" will not get file time comparisons right.

    There are several possible solutions to this problem, including username mapping, and forcing a specific username for particular shares. -

    Passwords

    +

    Passwords

    Many SMB clients uppercase passwords before sending them. I have no idea why they do this. Interestingly WfWg uppercases the password only if the server is running a protocol greater than COREPLUS, so @@ -943,20 +940,20 @@ obviously it isn't just the data entry routines that are to blame. Unix passwords are case sensitive. So if users use mixed case passwords they are in trouble.

    -Samba can try to cope with this by either using the "password level" +Samba can try to cope with this by either using the "password level" option which causes Samba to try the offered password with up to the -specified number of case changes, or by using the "password server" +specified number of case changes, or by using the "password server" option which allows Samba to do its validation via another machine (typically a WinNT server).

    Samba supports the password encryption method used by SMB clients. Note that the use of password encryption in Microsoft -networking leads to password hashes that are "plain text equivalent". +networking leads to password hashes that are "plain text equivalent". This means that it is *VERY* important to ensure that the Samba smbpasswd file containing these password hashes is only readable by the root user. See the documentation ENCRYPTION.txt for more details. -

    Locking

    +

    Locking

    Since samba 2.2, samba supports other types of locking as well. This section is outdated.

    @@ -981,14 +978,14 @@ a unix environment because few unix programs use byte range locking. The stress of huge numbers of lock requests from dos/windows clients can kill the daemon on some systems.

    -The second major problem is the "opportunistic locking" requested by +The second major problem is the "opportunistic locking" requested by some clients. If a client requests opportunistic locking then it is asking the server to notify it if anyone else tries to do something on the same file, at which time the client will say if it is willing to give up its lock. Unix has no simple way of implementing opportunistic locking, and currently Samba has no support for it. -

    Deny Modes

    -When a SMB client opens a file it asks for a particular "deny mode" to +

    Deny Modes

    +When a SMB client opens a file it asks for a particular "deny mode" to be placed on the file. These modes (DENY_NONE, DENY_READ, DENY_WRITE, DENY_ALL, DENY_FCB and DENY_DOS) specify what actions should be allowed by anyone else who tries to use the file at the same time. If @@ -1001,7 +998,7 @@ directory or a shared memory implementation. The lock file method is clumsy and consumes processing and file resources, the shared memory implementation is vastly prefered and is turned on by default for those systems that support it. -

    Trapdoor UIDs

    +

    Trapdoor UIDs

    A SMB session can run with several uids on the one socket. This happens when a user connects to two shares with different usernames. To cope with this the unix server needs to switch uids @@ -1009,11 +1006,11 @@ within the one process. On some unixes (such as SCO) this is not possible. This means that on those unixes the client is restricted to a single uid.

    -Note that you can also get the "trapdoor uid" message for other +Note that you can also get the "trapdoor uid" message for other reasons. Please see the FAQ for details. -

    Port numbers

    -There is a convention that clients on sockets use high "unprivilaged" -port numbers (>1000) and connect to servers on low "privilaged" port +

    Port numbers

    +There is a convention that clients on sockets use high "unprivilaged" +port numbers (>1000) and connect to servers on low "privilaged" port numbers. This is enforced in Unix as non-root users can't open a socket for listening on port numbers less than 1000.

    @@ -1034,13 +1031,13 @@ to any of these OSes unless they are running as root. The answer comes back, but it goes to port 137 which the unix user can't listen on. Interestingly WinNT3.1 got this right - it sends node status responses back to the source port in the request. -

    Protocol Complexity

    -There are many "protocol levels" in the SMB protocol. It seems that +

    Protocol Complexity

    +There are many "protocol levels" in the SMB protocol. It seems that each time new functionality was added to a Microsoft operating system, they added the equivalent functions in a new protocol level of the SMB -protocol to "externalise" the new capabilities. +protocol to "externalise" the new capabilities.

    -This means the protocol is very "rich", offering many ways of doing +This means the protocol is very "rich", offering many ways of doing each file operation. This means SMB servers need to be complex and large. It also means it is very difficult to make them bug free. It is not just Samba that suffers from this problem, other servers such as @@ -1048,19 +1045,19 @@ WinNT don't support every variation of every call and it has almost certainly been a headache for MS developers to support the myriad of SMB calls that are available.

    -There are about 65 "top level" operations in the SMB protocol (things +There are about 65 "top level" operations in the SMB protocol (things like SMBread and SMBwrite). Some of these include hundreds of sub-functions (SMBtrans has at least 120 sub-functions, like DosPrintQAdd and NetSessionEnum). All of them take several options that can change the way they work. Many take dozens of possible -"information levels" that change the structures that need to be -returned. Samba supports all but 2 of the "top level" functions. It +"information levels" that change the structures that need to be +returned. Samba supports all but 2 of the "top level" functions. It supports only 8 (so far) of the SMBtrans sub-functions. Even NT doesn't support them all.

    -Samba currently supports up to the "NT LM 0.12" protocol, which is the +Samba currently supports up to the "NT LM 0.12" protocol, which is the one preferred by Win95 and WinNT3.5. Luckily this protocol level has a -"capabilities" field which specifies which super-duper new-fangled +"capabilities" field which specifies which super-duper new-fangled options the server suports. This helps to make the implementation of this protocol level much easier.

    @@ -1105,13 +1102,13 @@ You'll notice that it produces a LOT of output. It is showing you the arguments to every system call that the program makes and the result. Very little happens in a program without a system call so you get lots of output. You'll also find that it produces a lot of -"preamble" stuff showing the loading of shared libraries etc. Ignore +"preamble" stuff showing the loading of shared libraries etc. Ignore this (unless its going wrong!)

    For example, the only line that really matters in the strace echo hello output is: 

    -write(1, "hello\n", 6)                  = 6
+write(1, "hello\n", 6)                  = 6

    all the rest is just setting up to run the program.

    Ok, now you're familiar with strace. To use it on Samba you need to strace the running smbd daemon. The way I tend ot use it is to first @@ -1121,10 +1118,10 @@ find which process ID that client is attached to, then as root I do stderr output from this command to a file for later perusal. For example, if I'm using a csh style shell:

    strace -f -p 3872 >& strace.out

    or with a sh style shell:

    strace -f -p 3872 > strace.out 2>&1

    -Note the "-f" option. This is only available on some systems, and +Note the "-f" option. This is only available on some systems, and allows you to trace not just the current process, but any children it forks. This is great for finding printing problems caused by the -"print command" being wrong. +"print command" being wrong.

    Once you are attached you then can do whatever it is on the client that is causing problems and you will capture all the system calls @@ -1135,20 +1132,20 @@ output for strings that I know will appear when the problem happens. For example, if I am having touble with permissions on a file I would search for that files name in the strace output and look at the surrounding lines. Another trick is to match up file descriptor -numbers and "follow" what happens to an open file until it is closed. +numbers and "follow" what happens to an open file until it is closed.

    Beyond this you will have to use your initiative. To give you an idea of what you are looking for here is a piece of strace output that shows that /dev/null is not world writeable, which causes printing to fail with Samba: 

    -[pid 28268] open("/dev/null", O_RDWR)   = -1 EACCES (Permission denied)
-[pid 28268] open("/dev/null", O_WRONLY) = -1 EACCES (Permission denied)
+[pid 28268] open("/dev/null", O_RDWR)   = -1 EACCES (Permission denied)
+[pid 28268] open("/dev/null", O_WRONLY) = -1 EACCES (Permission denied)

    The process is trying to first open /dev/null read-write then read-only. Both fail. This means /dev/null has incorrect permissions. -

    Chapter 9. Finding useful information on windows

    Jelmer R. Vernooij

    The Samba Team

    Andrew Tridgell

    Samba Team

    Table of Contents

    Netlogon debugging output

    Netlogon debugging output

    1. stop netlogon service on PDC

    2. rename original netlogon.dll to netlogon.dll.original

    3. copy checked version of netlogon.dll to system32 directory

    4. set HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Netlogon\Parameters\DBFlag to 0x20000004

    5. start netlogon service on PDC

    Chapter 10. NT Domain RPC's

    Luke Leighton

    Duncan Stansfield

    01 November 97(version 0.0.24)

    Table of Contents

    Introduction
    Sources
    Credits
    Notes and Structures
    Notes
    Enumerations
    Structures
    MSRPC over Transact Named Pipe
    MSRPC Pipes
    Header
    Tail
    RPC Bind / Bind Ack
    NTLSA Transact Named Pipe
    LSA Open Policy
    LSA Query Info Policy
    LSA Enumerate Trusted Domains
    LSA Open Secret
    LSA Close
    LSA Lookup SIDS
    LSA Lookup Names
    NETLOGON rpc Transact Named Pipe
    LSA Request Challenge
    LSA Authenticate 2
    LSA Server Password Set
    LSA SAM Logon
    LSA SAM Logoff
    \\MAILSLOT\NET\NTLOGON
    Query for PDC
    SAM Logon
    SRVSVC Transact Named Pipe
    Net Share Enum
    Net Server Get Info
    Cryptographic side of NT Domain Authentication
    Definitions
    Protocol
    Comments
    SIDs and RIDs
    Well-known SIDs
    Well-known RIDS

    Introduction

    +

    Chapter 9. Finding useful information on windows

    Jelmer R. Vernooij

    The Samba Team

    Andrew Tridgell

    Samba Team

    Table of Contents

    Netlogon debugging output

    Netlogon debugging output

    1. stop netlogon service on PDC

    2. rename original netlogon.dll to netlogon.dll.original

    3. copy checked version of netlogon.dll to system32 directory

    4. set HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Netlogon\Parameters\DBFlag to 0x20000004

    5. start netlogon service on PDC

    Chapter 10. NT Domain RPC's

    Luke Leighton

    Duncan Stansfield

    01 November 97(version 0.0.24)

    Table of Contents

    Introduction
    Sources
    Credits
    Notes and Structures
    Notes
    Enumerations
    Structures
    MSRPC over Transact Named Pipe
    MSRPC Pipes
    Header
    Tail
    RPC Bind / Bind Ack
    NTLSA Transact Named Pipe
    LSA Open Policy
    LSA Query Info Policy
    LSA Enumerate Trusted Domains
    LSA Open Secret
    LSA Close
    LSA Lookup SIDS
    LSA Lookup Names
    NETLOGON rpc Transact Named Pipe
    LSA Request Challenge
    LSA Authenticate 2
    LSA Server Password Set
    LSA SAM Logon
    LSA SAM Logoff
    \\MAILSLOT\NET\NTLOGON
    Query for PDC
    SAM Logon
    SRVSVC Transact Named Pipe
    Net Share Enum
    Net Server Get Info
    Cryptographic side of NT Domain Authentication
    Definitions
    Protocol
    Comments
    SIDs and RIDs
    Well-known SIDs
    Well-known RIDS

    Introduction

    This document contains information to provide an NT workstation with login services, without the need for an NT server. It is the sgml version of http://mailhost.cb1.com/~lkcl/cifsntdomain.txt, controlled by Luke.

    @@ -1181,7 +1178,7 @@ NT workstation, and enabling full debugging in NETLOGON. This is achieved by setting the following REG_SZ registry key to 0x1ffffff:

    HKLM\SYSTEM\CurrentControlSet\Services\Netlogon\Parameters

    Incorrect direct editing of the registry can cause your machine to fail. Then again, so can incorrect implementation of this -protocol. See "Liability:" above.

    +protocol. See "Liability:" above.

    Bear in mind that each packet over-the-wire will have its origin in an API call. Therefore, there are likely to be structures, enumerations and defines that are usefully documented elsewhere. @@ -1194,12 +1191,12 @@ Failure to return this error code will make the workstation report that it is already a member of the domain.

  • the cryptographic side of the NetrServerPasswordSet command, which would allow the workstation to change its password. This password is used to generate the long-term session key. [It is possible to reject this -command, and keep the default workstation password].

    • Sources

    cket Traces from Netmonitor (Service Pack 1 and above)
    ul Ashton and Luke Leighton's other "NT Domain" doc.
    FS documentation - cifs6.txt
    FS documentation - cifsrap2.txt

    Credits

    Paul Ashton: loads of work with Net Monitor; understanding the NT authentication system; reference implementation of the NT domain support on which this document is originally based.
    Duncan Stansfield: low-level analysis of MSRPC Pipes.
    Linus Nordberg: producing c-code from Paul's crypto spec.
    Windows Sourcer development team

    Notes and Structures

    Notes

    1. -In the SMB Transact pipes, some "Structures", described here, appear to be +command, and keep the default workstation password].

    Sources

    cket Traces from Netmonitor (Service Pack 1 and above)
    ul Ashton and Luke Leighton's other "NT Domain" doc.
    FS documentation - cifs6.txt
    FS documentation - cifsrap2.txt

    Credits

    Paul Ashton: loads of work with Net Monitor; understanding the NT authentication system; reference implementation of the NT domain support on which this document is originally based.
    Duncan Stansfield: low-level analysis of MSRPC Pipes.
    Linus Nordberg: producing c-code from Paul's crypto spec.
    Windows Sourcer development team

    Notes and Structures

    Notes

    1. +In the SMB Transact pipes, some "Structures", described here, appear to be 4-byte aligned with the SMB header, at their start. Exactly which -"Structures" need aligning is not precisely known or documented. +"Structures" need aligning is not precisely known or documented.

    2. -In the UDP NTLOGON Mailslots, some "Structures", described here, appear to be +In the UDP NTLOGON Mailslots, some "Structures", described here, appear to be 2-byte aligned with the start of the mailslot, at their start.

    3. Domain SID is of the format S-revision-version-auth1-auth2...authN. @@ -1222,15 +1219,15 @@ into or taken out of the SMB data stream. if the count is non-zero, then the pointer is also non-zero. immediately following the pointer is the count again, followed by an array of container sub-structures. the count appears a third time after the last sub-structure. -

    Enumerations

    MSRPC Header type

    command number in the msrpc packet header

    MSRPC_Request:

    0x00

    MSRPC_Response:

    0x02

    MSRPC_Bind:

    0x0B

    MSRPC_BindAck:

    0x0C

    MSRPC Packet info

    The meaning of these flags is undocumented

    FirstFrag:

    0x01

    LastFrag:

    0x02

    NotaFrag:

    0x04

    RecRespond:

    0x08

    NoMultiplex:

    0x10

    NotForIdemp:

    0x20

    NotforBcast:

    0x40

    NoUuid:

    0x80

    Structures

    VOID *

    sizeof VOID* is 32 bits.

    char

    sizeof char is 8 bits.

    UTIME

    UTIME is 32 bits, indicating time in seconds since 01jan1970. documented in cifs6.txt (section 3.5 page, page 30).

    NTTIME

    NTTIME is 64 bits. documented in cifs6.txt (section 3.5 page, page 30).

    DOM_SID (domain SID structure)

    UINT32

    num of sub-authorities in domain SID

    UINT8

    SID revision number

    UINT8

    num of sub-authorities in domain SID

    UINT8[6]

    6 bytes for domain SID - Identifier Authority.

    UINT16[n_subauths]

    domain SID sub-authorities

    Note: the domain SID is documented elsewhere. -

    STR (string)

    STR (string) is a char[] : a null-terminated string of ascii characters.

    UNIHDR (unicode string header)

    UINT16

    length of unicode string

    UINT16

    max length of unicode string

    UINT32

    4 - undocumented.

    UNIHDR2 (unicode string header plus buffer pointer)

    UNIHDR

    unicode string header

    VOID*

    undocumented buffer pointer

    UNISTR (unicode string)

    UINT16[]

    null-terminated string of unicode characters.

    NAME (length-indicated unicode string)

    UINT32

    length of unicode string

    UINT16[]

    null-terminated string of unicode characters.

    UNISTR2 (aligned unicode string)

    UINT8[]

    padding to get unicode string 4-byte aligned with the start of the SMB header.

    UINT32

    max length of unicode string

    UINT32

    0 - undocumented

    UINT32

    length of unicode string

    UINT16[]

    string of uncode characters

    OBJ_ATTR (object attributes)

    UINT32

    0x18 - length (in bytes) including the length field.

    VOID*

    0 - root directory (pointer)

    VOID*

    0 - object name (pointer)

    UINT32

    0 - attributes (undocumented)

    VOID*

    0 - security descriptior (pointer)

    UINT32

    0 - security quality of service

    POL_HND (LSA policy handle)

    char[20]

    policy handle

    DOM_SID2 (domain SID structure, SIDS stored in unicode)

    UINT32

    5 - SID type

    UINT32

    0 - undocumented

    UNIHDR2

    domain SID unicode string header

    UNISTR

    domain SID unicode string

    Note: there is a conflict between the unicode string header and the unicode string itself as to which to use to indicate string length. this will need to be resolved.

    Note: the SID type indicates, for example, an alias; a well-known group etc. this is documented somewhere.

    DOM_RID (domain RID structure)

    UINT32

    5 - well-known SID. 1 - user SID (see ShowACLs)

    UINT32

    5 - undocumented

    UINT32

    domain RID

    UINT32

    0 - domain index out of above reference domains

    LOG_INFO (server, account, client structure)

    Note: logon server name starts with two '\' characters and is upper case.

    Note: account name is the logon client name from the LSA Request Challenge, with a $ on the end of it, in upper case.

    VOID*

    undocumented buffer pointer

    UNISTR2

    logon server unicode string

    UNISTR2

    account name unicode string

    UINT16

    sec_chan - security channel type

    UNISTR2

    logon client machine unicode string

    CLNT_SRV (server, client names structure)

    Note: logon server name starts with two '\' characters and is upper case.

    VOID*

    undocumented buffer pointer

    UNISTR2

    logon server unicode string

    VOID*

    undocumented buffer pointer

    UNISTR2

    logon client machine unicode string

    CREDS (credentials + time stamp)

    char[8]

    credentials

    UTIME

    time stamp

    CLNT_INFO2 (server, client structure, client credentials)

    Note: whenever this structure appears in a request, you must take a copy of the client-calculated credentials received, because they will beused in subsequent credential checks. the presumed intention is to - maintain an authenticated request/response trail.

    CLNT_SRV

    client and server names

    UINT8[]

    ???? padding, for 4-byte alignment with SMB header.

    VOID*

    pointer to client credentials.

    CREDS

    client-calculated credentials + client time

    CLNT_INFO (server, account, client structure, client credentials)

    Note: whenever this structure appears in a request, you must take a copy of the client-calculated credentials received, because they will be used in subsequent credential checks. the presumed intention is to maintain an authenticated request/response trail.

    LOG_INFO

    logon account info

    CREDS

    client-calculated credentials + client time

    ID_INFO_1 (id info structure, auth level 1)

    VOID*

    ptr_id_info_1

    UNIHDR

    domain name unicode header

    UINT32

    param control

    UINT64

    logon ID

    UNIHDR

    user name unicode header

    UNIHDR

    workgroup name unicode header

    char[16]

    arc4 LM OWF Password

    char[16]

    arc4 NT OWF Password

    UNISTR2

    domain name unicode string

    UNISTR2

    user name unicode string

    UNISTR2

    workstation name unicode string

    SAM_INFO (sam logon/logoff id info structure)

    Note: presumably, the return credentials is supposedly for the server to verify that the credential chain hasn't been compromised.

    CLNT_INFO2

    client identification/authentication info

    VOID*

    pointer to return credentials.

    CRED

    return credentials - ignored.

    UINT16

    logon level

    UINT16

    switch value

    +

    Enumerations

    MSRPC Header type

    command number in the msrpc packet header

    MSRPC_Request:

    0x00

    MSRPC_Response:

    0x02

    MSRPC_Bind:

    0x0B

    MSRPC_BindAck:

    0x0C

    MSRPC Packet info

    The meaning of these flags is undocumented

    FirstFrag:

    0x01

    LastFrag:

    0x02

    NotaFrag:

    0x04

    RecRespond:

    0x08

    NoMultiplex:

    0x10

    NotForIdemp:

    0x20

    NotforBcast:

    0x40

    NoUuid:

    0x80

    Structures

    VOID *

    sizeof VOID* is 32 bits.

    char

    sizeof char is 8 bits.

    UTIME

    UTIME is 32 bits, indicating time in seconds since 01jan1970. documented in cifs6.txt (section 3.5 page, page 30).

    NTTIME

    NTTIME is 64 bits. documented in cifs6.txt (section 3.5 page, page 30).

    DOM_SID (domain SID structure)

    UINT32

    num of sub-authorities in domain SID

    UINT8

    SID revision number

    UINT8

    num of sub-authorities in domain SID

    UINT8[6]

    6 bytes for domain SID - Identifier Authority.

    UINT16[n_subauths]

    domain SID sub-authorities

    Note: the domain SID is documented elsewhere. +

    STR (string)

    STR (string) is a char[] : a null-terminated string of ascii characters.

    UNIHDR (unicode string header)

    UINT16

    length of unicode string

    UINT16

    max length of unicode string

    UINT32

    4 - undocumented.

    UNIHDR2 (unicode string header plus buffer pointer)

    UNIHDR

    unicode string header

    VOID*

    undocumented buffer pointer

    UNISTR (unicode string)

    UINT16[]

    null-terminated string of unicode characters.

    NAME (length-indicated unicode string)

    UINT32

    length of unicode string

    UINT16[]

    null-terminated string of unicode characters.

    UNISTR2 (aligned unicode string)

    UINT8[]

    padding to get unicode string 4-byte aligned with the start of the SMB header.

    UINT32

    max length of unicode string

    UINT32

    0 - undocumented

    UINT32

    length of unicode string

    UINT16[]

    string of uncode characters

    OBJ_ATTR (object attributes)

    UINT32

    0x18 - length (in bytes) including the length field.

    VOID*

    0 - root directory (pointer)

    VOID*

    0 - object name (pointer)

    UINT32

    0 - attributes (undocumented)

    VOID*

    0 - security descriptior (pointer)

    UINT32

    0 - security quality of service

    POL_HND (LSA policy handle)

    char[20]

    policy handle

    DOM_SID2 (domain SID structure, SIDS stored in unicode)

    UINT32

    5 - SID type

    UINT32

    0 - undocumented

    UNIHDR2

    domain SID unicode string header

    UNISTR

    domain SID unicode string

    Note: there is a conflict between the unicode string header and the unicode string itself as to which to use to indicate string length. this will need to be resolved.

    Note: the SID type indicates, for example, an alias; a well-known group etc. this is documented somewhere.

    DOM_RID (domain RID structure)

    UINT32

    5 - well-known SID. 1 - user SID (see ShowACLs)

    UINT32

    5 - undocumented

    UINT32

    domain RID

    UINT32

    0 - domain index out of above reference domains

    LOG_INFO (server, account, client structure)

    Note: logon server name starts with two '\' characters and is upper case.

    Note: account name is the logon client name from the LSA Request Challenge, with a $ on the end of it, in upper case.

    VOID*

    undocumented buffer pointer

    UNISTR2

    logon server unicode string

    UNISTR2

    account name unicode string

    UINT16

    sec_chan - security channel type

    UNISTR2

    logon client machine unicode string

    CLNT_SRV (server, client names structure)

    Note: logon server name starts with two '\' characters and is upper case.

    VOID*

    undocumented buffer pointer

    UNISTR2

    logon server unicode string

    VOID*

    undocumented buffer pointer

    UNISTR2

    logon client machine unicode string

    CREDS (credentials + time stamp)

    char[8]

    credentials

    UTIME

    time stamp

    CLNT_INFO2 (server, client structure, client credentials)

    Note: whenever this structure appears in a request, you must take a copy of the client-calculated credentials received, because they will beused in subsequent credential checks. the presumed intention is to + maintain an authenticated request/response trail.

    CLNT_SRV

    client and server names

    UINT8[]

    ???? padding, for 4-byte alignment with SMB header.

    VOID*

    pointer to client credentials.

    CREDS

    client-calculated credentials + client time

    CLNT_INFO (server, account, client structure, client credentials)

    Note: whenever this structure appears in a request, you must take a copy of the client-calculated credentials received, because they will be used in subsequent credential checks. the presumed intention is to maintain an authenticated request/response trail.

    LOG_INFO

    logon account info

    CREDS

    client-calculated credentials + client time

    ID_INFO_1 (id info structure, auth level 1)

    VOID*

    ptr_id_info_1

    UNIHDR

    domain name unicode header

    UINT32

    param control

    UINT64

    logon ID

    UNIHDR

    user name unicode header

    UNIHDR

    workgroup name unicode header

    char[16]

    arc4 LM OWF Password

    char[16]

    arc4 NT OWF Password

    UNISTR2

    domain name unicode string

    UNISTR2

    user name unicode string

    UNISTR2

    workstation name unicode string

    SAM_INFO (sam logon/logoff id info structure)

    Note: presumably, the return credentials is supposedly for the server to verify that the credential chain hasn't been compromised.

    CLNT_INFO2

    client identification/authentication info

    VOID*

    pointer to return credentials.

    CRED

    return credentials - ignored.

    UINT16

    logon level

    UINT16

    switch value

             switch (switch_value)
         case 1:
         {
             ID_INFO_1     id_info_1;
         }
-

    GID (group id info)

    UINT32

    group id

    UINT32

    user attributes (only used by NT 3.1 and 3.51)

    DOM_REF (domain reference info)

    VOID*

    undocumented buffer pointer.

    UINT32

    num referenced domains?

    VOID*

    undocumented domain name buffer pointer.

    UINT32

    32 - max number of entries

    UINT32

    4 - num referenced domains?

    UNIHDR2

    domain name unicode string header

    UNIHDR2[num_ref_doms-1]

    referenced domain unicode string headers

    UNISTR

    domain name unicode string

    DOM_SID[num_ref_doms]

    referenced domain SIDs

    DOM_INFO (domain info, levels 3 and 5 are the same))

    UINT8[]

    ??? padding to get 4-byte alignment with start of SMB header

    UINT16

    domain name string length * 2

    UINT16

    domain name string length * 2

    VOID*

    undocumented domain name string buffer pointer

    VOID*

    undocumented domain SID string buffer pointer

    UNISTR2

    domain name (unicode string)

    DOM_SID

    domain SID

    USER_INFO (user logon info)

    Note: it would be nice to know what the 16 byte user session key is for.

    NTTIME

    logon time

    NTTIME

    logoff time

    NTTIME

    kickoff time

    NTTIME

    password last set time

    NTTIME

    password can change time

    NTTIME

    password must change time

    UNIHDR

    username unicode string header

    UNIHDR

    user's full name unicode string header

    UNIHDR

    logon script unicode string header

    UNIHDR

    profile path unicode string header

    UNIHDR

    home directory unicode string header

    UNIHDR

    home directory drive unicode string header

    UINT16

    logon count

    UINT16

    bad password count

    UINT32

    User ID

    UINT32

    Group ID

    UINT32

    num groups

    VOID*

    undocumented buffer pointer to groups.

    UINT32

    user flags

    char[16]

    user session key

    UNIHDR

    logon server unicode string header

    UNIHDR

    logon domain unicode string header

    VOID*

    undocumented logon domain id pointer

    char[40]

    40 undocumented padding bytes. future expansion?

    UINT32

    0 - num_other_sids?

    VOID*

    NULL - undocumented pointer to other domain SIDs.

    UNISTR2

    username unicode string

    UNISTR2

    user's full name unicode string

    UNISTR2

    logon script unicode string

    UNISTR2

    profile path unicode string

    UNISTR2

    home directory unicode string

    UNISTR2

    home directory drive unicode string

    UINT32

    num groups

    GID[num_groups]

    group info

    UNISTR2

    logon server unicode string

    UNISTR2

    logon domain unicode string

    DOM_SID

    domain SID

    DOM_SID[num_sids]

    other domain SIDs?

    SH_INFO_1_PTR (pointers to level 1 share info strings)

    Note: see cifsrap2.txt section5, page 10.

    0 for shi1_type indicates a Disk.
    1 for shi1_type indicates a Print Queue.
    2 for shi1_type indicates a Device.
    3 for shi1_type indicates an IPC pipe.
    0x8000 0000 (top bit set in shi1_type) indicates a hidden share.
    VOID*

    shi1_netname - pointer to net name

    UINT32

    shi1_type - type of share. 0 - undocumented.

    VOID*

    shi1_remark - pointer to comment.

    SH_INFO_1_STR (level 1 share info strings)

    UNISTR2

    shi1_netname - unicode string of net name

    UNISTR2

    shi1_remark - unicode string of comment.

    SHARE_INFO_1_CTR

    share container with 0 entries:

    UINT32

    0 - EntriesRead

    UINT32

    0 - Buffer

    share container with > 0 entries:

    UINT32

    EntriesRead

    UINT32

    non-zero - Buffer

    UINT32

    EntriesRead

    SH_INFO_1_PTR[EntriesRead]

    share entry pointers

    SH_INFO_1_STR[EntriesRead]

    share entry strings

    UINT8[]

    padding to get unicode string 4-byte aligned with start of the SMB header.

    UINT32

    EntriesRead

    UINT32

    0 - padding

    SERVER_INFO_101

    Note: see cifs6.txt section 6.4 - the fields described therein will be of assistance here. for example, the type listed below is the same as fServerType, which is described in 6.4.1.

    SV_TYPE_WORKSTATION

    0x00000001 All workstations

    SV_TYPE_SERVER

    0x00000002 All servers

    SV_TYPE_SQLSERVER

    0x00000004 Any server running with SQL server

    SV_TYPE_DOMAIN_CTRL

    0x00000008 Primary domain controller

    SV_TYPE_DOMAIN_BAKCTRL

    0x00000010 Backup domain controller

    SV_TYPE_TIME_SOURCE

    0x00000020 Server running the timesource service

    SV_TYPE_AFP

    0x00000040 Apple File Protocol servers

    SV_TYPE_NOVELL

    0x00000080 Novell servers

    SV_TYPE_DOMAIN_MEMBER

    0x00000100 Domain Member

    SV_TYPE_PRINTQ_SERVER

    0x00000200 Server sharing print queue

    SV_TYPE_DIALIN_SERVER

    0x00000400 Server running dialin service.

    SV_TYPE_XENIX_SERVER

    0x00000800 Xenix server

    SV_TYPE_NT

    0x00001000 NT server

    SV_TYPE_WFW

    0x00002000 Server running Windows for

    SV_TYPE_SERVER_NT

    0x00008000 Windows NT non DC server

    SV_TYPE_POTENTIAL_BROWSER

    0x00010000 Server that can run the browser service

    SV_TYPE_BACKUP_BROWSER

    0x00020000 Backup browser server

    SV_TYPE_MASTER_BROWSER

    0x00040000 Master browser server

    SV_TYPE_DOMAIN_MASTER

    0x00080000 Domain Master Browser server

    SV_TYPE_LOCAL_LIST_ONLY

    0x40000000 Enumerate only entries marked "local"

    SV_TYPE_DOMAIN_ENUM

    0x80000000 Enumerate Domains. The pszServer and pszDomain parameters must be NULL.

    UINT32

    500 - platform_id

    VOID*

    pointer to name

    UINT32

    5 - major version

    UINT32

    4 - minor version

    UINT32

    type (SV_TYPE_... bit field)

    VOID*

    pointer to comment

    UNISTR2

    sv101_name - unicode string of server name

    UNISTR2

    sv_101_comment - unicode string of server comment.

    UINT8[]

    padding to get unicode string 4-byte aligned with start of the SMB header.

    MSRPC over Transact Named Pipe

    For details on the SMB Transact Named Pipe, see cifs6.txt

    MSRPC Pipes

    +

    GID (group id info)

    UINT32

    group id

    UINT32

    user attributes (only used by NT 3.1 and 3.51)

    DOM_REF (domain reference info)

    VOID*

    undocumented buffer pointer.

    UINT32

    num referenced domains?

    VOID*

    undocumented domain name buffer pointer.

    UINT32

    32 - max number of entries

    UINT32

    4 - num referenced domains?

    UNIHDR2

    domain name unicode string header

    UNIHDR2[num_ref_doms-1]

    referenced domain unicode string headers

    UNISTR

    domain name unicode string

    DOM_SID[num_ref_doms]

    referenced domain SIDs

    DOM_INFO (domain info, levels 3 and 5 are the same))

    UINT8[]

    ??? padding to get 4-byte alignment with start of SMB header

    UINT16

    domain name string length * 2

    UINT16

    domain name string length * 2

    VOID*

    undocumented domain name string buffer pointer

    VOID*

    undocumented domain SID string buffer pointer

    UNISTR2

    domain name (unicode string)

    DOM_SID

    domain SID

    USER_INFO (user logon info)

    Note: it would be nice to know what the 16 byte user session key is for.

    NTTIME

    logon time

    NTTIME

    logoff time

    NTTIME

    kickoff time

    NTTIME

    password last set time

    NTTIME

    password can change time

    NTTIME

    password must change time

    UNIHDR

    username unicode string header

    UNIHDR

    user's full name unicode string header

    UNIHDR

    logon script unicode string header

    UNIHDR

    profile path unicode string header

    UNIHDR

    home directory unicode string header

    UNIHDR

    home directory drive unicode string header

    UINT16

    logon count

    UINT16

    bad password count

    UINT32

    User ID

    UINT32

    Group ID

    UINT32

    num groups

    VOID*

    undocumented buffer pointer to groups.

    UINT32

    user flags

    char[16]

    user session key

    UNIHDR

    logon server unicode string header

    UNIHDR

    logon domain unicode string header

    VOID*

    undocumented logon domain id pointer

    char[40]

    40 undocumented padding bytes. future expansion?

    UINT32

    0 - num_other_sids?

    VOID*

    NULL - undocumented pointer to other domain SIDs.

    UNISTR2

    username unicode string

    UNISTR2

    user's full name unicode string

    UNISTR2

    logon script unicode string

    UNISTR2

    profile path unicode string

    UNISTR2

    home directory unicode string

    UNISTR2

    home directory drive unicode string

    UINT32

    num groups

    GID[num_groups]

    group info

    UNISTR2

    logon server unicode string

    UNISTR2

    logon domain unicode string

    DOM_SID

    domain SID

    DOM_SID[num_sids]

    other domain SIDs?

    SH_INFO_1_PTR (pointers to level 1 share info strings)

    Note: see cifsrap2.txt section5, page 10.

    0 for shi1_type indicates a Disk.
    1 for shi1_type indicates a Print Queue.
    2 for shi1_type indicates a Device.
    3 for shi1_type indicates an IPC pipe.
    0x8000 0000 (top bit set in shi1_type) indicates a hidden share.
    VOID*

    shi1_netname - pointer to net name

    UINT32

    shi1_type - type of share. 0 - undocumented.

    VOID*

    shi1_remark - pointer to comment.

    SH_INFO_1_STR (level 1 share info strings)

    UNISTR2

    shi1_netname - unicode string of net name

    UNISTR2

    shi1_remark - unicode string of comment.

    SHARE_INFO_1_CTR

    share container with 0 entries:

    UINT32

    0 - EntriesRead

    UINT32

    0 - Buffer

    share container with > 0 entries:

    UINT32

    EntriesRead

    UINT32

    non-zero - Buffer

    UINT32

    EntriesRead

    SH_INFO_1_PTR[EntriesRead]

    share entry pointers

    SH_INFO_1_STR[EntriesRead]

    share entry strings

    UINT8[]

    padding to get unicode string 4-byte aligned with start of the SMB header.

    UINT32

    EntriesRead

    UINT32

    0 - padding

    SERVER_INFO_101

    Note: see cifs6.txt section 6.4 - the fields described therein will be of assistance here. for example, the type listed below is the same as fServerType, which is described in 6.4.1.

    SV_TYPE_WORKSTATION

    0x00000001 All workstations

    SV_TYPE_SERVER

    0x00000002 All servers

    SV_TYPE_SQLSERVER

    0x00000004 Any server running with SQL server

    SV_TYPE_DOMAIN_CTRL

    0x00000008 Primary domain controller

    SV_TYPE_DOMAIN_BAKCTRL

    0x00000010 Backup domain controller

    SV_TYPE_TIME_SOURCE

    0x00000020 Server running the timesource service

    SV_TYPE_AFP

    0x00000040 Apple File Protocol servers

    SV_TYPE_NOVELL

    0x00000080 Novell servers

    SV_TYPE_DOMAIN_MEMBER

    0x00000100 Domain Member

    SV_TYPE_PRINTQ_SERVER

    0x00000200 Server sharing print queue

    SV_TYPE_DIALIN_SERVER

    0x00000400 Server running dialin service.

    SV_TYPE_XENIX_SERVER

    0x00000800 Xenix server

    SV_TYPE_NT

    0x00001000 NT server

    SV_TYPE_WFW

    0x00002000 Server running Windows for

    SV_TYPE_SERVER_NT

    0x00008000 Windows NT non DC server

    SV_TYPE_POTENTIAL_BROWSER

    0x00010000 Server that can run the browser service

    SV_TYPE_BACKUP_BROWSER

    0x00020000 Backup browser server

    SV_TYPE_MASTER_BROWSER

    0x00040000 Master browser server

    SV_TYPE_DOMAIN_MASTER

    0x00080000 Domain Master Browser server

    SV_TYPE_LOCAL_LIST_ONLY

    0x40000000 Enumerate only entries marked "local"

    SV_TYPE_DOMAIN_ENUM

    0x80000000 Enumerate Domains. The pszServer and pszDomain parameters must be NULL.

    UINT32

    500 - platform_id

    VOID*

    pointer to name

    UINT32

    5 - major version

    UINT32

    4 - minor version

    UINT32

    type (SV_TYPE_... bit field)

    VOID*

    pointer to comment

    UNISTR2

    sv101_name - unicode string of server name

    UNISTR2

    sv_101_comment - unicode string of server comment.

    UINT8[]

    padding to get unicode string 4-byte aligned with start of the SMB header.

    MSRPC over Transact Named Pipe

    For details on the SMB Transact Named Pipe, see cifs6.txt

    MSRPC Pipes

    The MSRPC is conducted over an SMB Transact Pipe with a name of \PIPE\. You must first obtain a 16 bit file handle, by sending a SMBopenX with the pipe name \PIPE\srvsvc for @@ -1269,21 +1266,21 @@ To be resolved: lkcl/01nov97 there appear to be two additional bytes after the null-terminated \PIPE\ name for the RPC pipe. Values seen so far are listed below:

             initial SMBopenX request:         RPC API command 0x26 params:
-        "\\PIPE\\lsarpc"                  0x65 0x63; 0x72 0x70; 0x44 0x65;
-        "\\PIPE\\srvsvc"                  0x73 0x76; 0x4E 0x00; 0x5C 0x43;
-

    Header

    [section to be rewritten, following receipt of work by Duncan Stansfield]

    Interesting note: if you set packed data representation to 0x0100 0000 -then all 4-byte and 2-byte word ordering is turned around!

    The start of each of the NTLSA and NETLOGON named pipes begins with:

    offset: 00

    Variable type: UINT8

    Variable data: 5 - RPC major version

    offset: 01

    Variable type: UINT8

    Variable data: 0 - RPC minor version

    offset: 02

    Variable type: UINT8

    Variable data: 2 - RPC response packet

    offset: 03

    Variable type: UINT8

    Variable data: 3 - (FirstFrag bit-wise or with LastFrag)

    offset: 04

    Variable type: UINT32

    Variable data: 0x1000 0000 - packed data representation

    offset: 08

    Variable type: UINT16

    Variable data: fragment length - data size (bytes) inc header and tail.

    offset: 0A

    Variable type: UINT16

    Variable data: 0 - authentication length

    offset: 0C

    Variable type: UINT32

    Variable data: call identifier. matches 12th UINT32 of incoming RPC data.

    offset: 10

    Variable type: UINT32

    Variable data: allocation hint - data size (bytes) minus header and tail.

    offset: 14

    Variable type: UINT16

    Variable data: 0 - presentation context identifier

    offset: 16

    Variable type: UINT8

    Variable data: 0 - cancel count

    offset: 17

    Variable type: UINT8

    Variable data: in replies: 0 - reserved; in requests: opnum - see #defines.

    offset: 18

    Variable type: ......

    Variable data: start of data (goes on for allocation_hint bytes)

    RPC_Packet for request, response, bind and bind acknowledgement

    UINT8 versionmaj

    reply same as request (0x05)

    UINT8 versionmin

    reply same as request (0x00)

    UINT8 type

    one of the MSRPC_Type enums

    UINT8 flags

    reply same as request (0x00 for Bind, 0x03 for Request)

    UINT32 representation

    reply same as request (0x00000010)

    UINT16 fraglength

    the length of the data section of the SMB trans packet

    UINT16 authlength

    UINT32 callid

    call identifier. (e.g. 0x00149594)

    * stub USE TvPacket

    the remainder of the packet depending on the "type"

    Interface identification

    the interfaces are numbered. as yet I haven't seen more than one interface used on the same pipe name srvsvc

    +        "\\PIPE\\lsarpc"                  0x65 0x63; 0x72 0x70; 0x44 0x65;
+        "\\PIPE\\srvsvc"                  0x73 0x76; 0x4E 0x00; 0x5C 0x43;
+

    Header

    [section to be rewritten, following receipt of work by Duncan Stansfield]

    Interesting note: if you set packed data representation to 0x0100 0000 +then all 4-byte and 2-byte word ordering is turned around!

    The start of each of the NTLSA and NETLOGON named pipes begins with:

    offset: 00

    Variable type: UINT8

    Variable data: 5 - RPC major version

    offset: 01

    Variable type: UINT8

    Variable data: 0 - RPC minor version

    offset: 02

    Variable type: UINT8

    Variable data: 2 - RPC response packet

    offset: 03

    Variable type: UINT8

    Variable data: 3 - (FirstFrag bit-wise or with LastFrag)

    offset: 04

    Variable type: UINT32

    Variable data: 0x1000 0000 - packed data representation

    offset: 08

    Variable type: UINT16

    Variable data: fragment length - data size (bytes) inc header and tail.

    offset: 0A

    Variable type: UINT16

    Variable data: 0 - authentication length

    offset: 0C

    Variable type: UINT32

    Variable data: call identifier. matches 12th UINT32 of incoming RPC data.

    offset: 10

    Variable type: UINT32

    Variable data: allocation hint - data size (bytes) minus header and tail.

    offset: 14

    Variable type: UINT16

    Variable data: 0 - presentation context identifier

    offset: 16

    Variable type: UINT8

    Variable data: 0 - cancel count

    offset: 17

    Variable type: UINT8

    Variable data: in replies: 0 - reserved; in requests: opnum - see #defines.

    offset: 18

    Variable type: ......

    Variable data: start of data (goes on for allocation_hint bytes)

    RPC_Packet for request, response, bind and bind acknowledgement

    UINT8 versionmaj

    reply same as request (0x05)

    UINT8 versionmin

    reply same as request (0x00)

    UINT8 type

    one of the MSRPC_Type enums

    UINT8 flags

    reply same as request (0x00 for Bind, 0x03 for Request)

    UINT32 representation

    reply same as request (0x00000010)

    UINT16 fraglength

    the length of the data section of the SMB trans packet

    UINT16 authlength

    UINT32 callid

    call identifier. (e.g. 0x00149594)

    * stub USE TvPacket

    the remainder of the packet depending on the "type"

    Interface identification

    the interfaces are numbered. as yet I haven't seen more than one interface used on the same pipe name srvsvc

     abstract (0x4B324FC8, 0x01D31670, 0x475A7812, 0x88E16EBF, 0x00000003)
 transfer (0x8A885D04, 0x11C91CEB, 0x0008E89F, 0x6048102B, 0x00000002)
-

    RPC_Iface RW

    UINT8 byte[16]

    16 bytes of number

    UINT32 version

    the interface number

    RPC_ReqBind RW

    the remainder of the packet after the header if "type" was Bind in the response header, "type" should be BindAck

    UINT16 maxtsize

    maximum transmission fragment size (0x1630)

    UINT16 maxrsize

    max receive fragment size (0x1630)

    UINT32 assocgid

    associated group id (0x0)

    UINT32 numelements

    the number of elements (0x1)

    UINT16 contextid

    presentation context identifier (0x0)

    UINT8 numsyntaxes

    the number of syntaxes (has always been 1?)(0x1)

    UINT8[]

    4-byte alignment padding, against SMB header

    * abstractint USE RPC_Iface

    num and vers. of interface client is using

    * transferint USE RPC_Iface

    num and vers. of interface to use for replies

    RPC_Address RW

    UINT16 length

    length of the string including null terminator

    * port USE string

    the string above in single byte, null terminated form

    RPC_ResBind RW

    the response to place after the header in the reply packet

    UINT16 maxtsize

    same as request

    UINT16 maxrsize

    same as request

    UINT32 assocgid

    zero

    * secondaddr USE RPC_Address

    the address string, as described earlier

    UINT8[]

    4-byte alignment padding, against SMB header

    UINT8 numresults

    the number of results (0x01)

    UINT8[]

    4-byte alignment padding, against SMB header

    UINT16 result

    result (0x00 = accept)

    UINT16 reason

    reason (0x00 = no reason specified)

    * transfersyntax USE RPC_Iface

    the transfer syntax from the request

    RPC_ReqNorm RW

    the remainder of the packet after the header for every other other request

    UINT32 allochint

    the size of the stub data in bytes

    UINT16 prescontext

    presentation context identifier (0x0)

    UINT16 opnum

    operation number (0x15)

    * stub USE TvPacket

    a packet dependent on the pipe name (probably the interface) and the op number)

    RPC_ResNorm RW

    UINT32 allochint

    # size of the stub data in bytes

    UINT16 prescontext

    # presentation context identifier (same as request)

    UINT8 cancelcount

    # cancel count? (0x0)

    UINT8 reserved

    # 0 - one byte padding

    * stub USE TvPacket

    # the remainder of the reply

    Tail

    The end of each of the NTLSA and NETLOGON named pipes ends with:

    ......

    end of data

    UINT32

    return code

    RPC Bind / Bind Ack

    +

    RPC_Iface RW

    UINT8 byte[16]

    16 bytes of number

    UINT32 version

    the interface number

    RPC_ReqBind RW

    the remainder of the packet after the header if "type" was Bind in the response header, "type" should be BindAck

    UINT16 maxtsize

    maximum transmission fragment size (0x1630)

    UINT16 maxrsize

    max receive fragment size (0x1630)

    UINT32 assocgid

    associated group id (0x0)

    UINT32 numelements

    the number of elements (0x1)

    UINT16 contextid

    presentation context identifier (0x0)

    UINT8 numsyntaxes

    the number of syntaxes (has always been 1?)(0x1)

    UINT8[]

    4-byte alignment padding, against SMB header

    * abstractint USE RPC_Iface

    num and vers. of interface client is using

    * transferint USE RPC_Iface

    num and vers. of interface to use for replies

    RPC_Address RW

    UINT16 length

    length of the string including null terminator

    * port USE string

    the string above in single byte, null terminated form

    RPC_ResBind RW

    the response to place after the header in the reply packet

    UINT16 maxtsize

    same as request

    UINT16 maxrsize

    same as request

    UINT32 assocgid

    zero

    * secondaddr USE RPC_Address

    the address string, as described earlier

    UINT8[]

    4-byte alignment padding, against SMB header

    UINT8 numresults

    the number of results (0x01)

    UINT8[]

    4-byte alignment padding, against SMB header

    UINT16 result

    result (0x00 = accept)

    UINT16 reason

    reason (0x00 = no reason specified)

    * transfersyntax USE RPC_Iface

    the transfer syntax from the request

    RPC_ReqNorm RW

    the remainder of the packet after the header for every other other request

    UINT32 allochint

    the size of the stub data in bytes

    UINT16 prescontext

    presentation context identifier (0x0)

    UINT16 opnum

    operation number (0x15)

    * stub USE TvPacket

    a packet dependent on the pipe name (probably the interface) and the op number)

    RPC_ResNorm RW

    UINT32 allochint

    # size of the stub data in bytes

    UINT16 prescontext

    # presentation context identifier (same as request)

    UINT8 cancelcount

    # cancel count? (0x0)

    UINT8 reserved

    # 0 - one byte padding

    * stub USE TvPacket

    # the remainder of the reply

    Tail

    The end of each of the NTLSA and NETLOGON named pipes ends with:

    ......

    end of data

    UINT32

    return code

    RPC Bind / Bind Ack

    RPC Binds are the process of associating an RPC pipe (e.g \PIPE\lsarpc) -with a "transfer syntax" (see RPC_Iface structure). The purpose for doing +with a "transfer syntax" (see RPC_Iface structure). The purpose for doing this is unknown.

    Note: The RPC_ResBind SMB Transact request is sent with two uint16 setup parameters. The first is 0x0026; the second is the file handle returned by the SMBopenX Transact response.

    Note: The RPC_ResBind members maxtsize, maxrsize and assocgid are the same in the response as the same members in the RPC_ReqBind. The RPC_ResBind member transfersyntax is the same in the response as the

    Note: The RPC_ResBind response member secondaddr contains the name of what is presumed to be the service behind the RPC pipe. The - mapping identified so far is:

    initial SMBopenX request:

    RPC_ResBind response:

    "\\PIPE\\srvsvc"

    "\\PIPE\\ntsvcs"

    "\\PIPE\\samr"

    "\\PIPE\\lsass"

    "\\PIPE\\lsarpc"

    "\\PIPE\\lsass"

    "\\PIPE\\wkssvc"

    "\\PIPE\\wksvcs"

    "\\PIPE\\NETLOGON"

    "\\PIPE\\NETLOGON"

    Note: The RPC_Packet fraglength member in both the Bind Request and Bind Acknowledgment must contain the length of the entire RPC data, including the RPC_Packet header.

    Request:

    RPC_Packet
    RPC_ReqBind

    Response:

    RPC_Packet
    RPC_ResBind

    NTLSA Transact Named Pipe

    The sequence of actions taken on this pipe are:

    Establish a connection to the IPC$ share (SMBtconX). use encrypted passwords.
    Open an RPC Pipe with the name "\\PIPE\\lsarpc". Store the file handle.
    Using the file handle, send a Set Named Pipe Handle state to 0x4300.
    Send an LSA Open Policy request. Store the Policy Handle.
    Using the Policy Handle, send LSA Query Info Policy requests, etc.
    Using the Policy Handle, send an LSA Close.
    Close the IPC$ share.

    Defines for this pipe, identifying the query are:

    LSA Open Policy:

    0x2c

    LSA Query Info Policy:

    0x07

    LSA Enumerate Trusted Domains:

    0x0d

    LSA Open Secret:

    0xff

    LSA Lookup SIDs:

    0xfe

    LSA Lookup Names:

    0xfd

    LSA Close:

    0x00

    LSA Open Policy

    Note: The policy handle can be anything you like.

    Request

    VOID*

    buffer pointer

    UNISTR2

    server name - unicode string starting with two '\'s

    OBJ_ATTR

    object attributes

    UINT32

    1 - desired access

    Response

    POL_HND

    LSA policy handle

    return

    0 - indicates success

    LSA Query Info Policy

    Note: The info class in response must be the same as that in the request.

    Request

    POL_HND

    LSA policy handle

    UINT16

    info class (also a policy handle?)

    Response

    VOID*

    undocumented buffer pointer

    UINT16

    info class (same as info class in request).

    +	mapping identified so far is:
    initial SMBopenX request:
    RPC_ResBind response:
    "\\PIPE\\srvsvc"
    "\\PIPE\\ntsvcs"
    "\\PIPE\\samr"
    "\\PIPE\\lsass"
    "\\PIPE\\lsarpc"
    "\\PIPE\\lsass"
    "\\PIPE\\wkssvc"
    "\\PIPE\\wksvcs"
    "\\PIPE\\NETLOGON"
    "\\PIPE\\NETLOGON"
    Note:	The RPC_Packet fraglength member in both the Bind Request and Bind Acknowledgment must contain the length of the entire RPC data, including the RPC_Packet header.
    Request:
    RPC_Packet
    RPC_ReqBind
    Response:
    RPC_Packet
    RPC_ResBind

    NTLSA Transact Named Pipe

    The sequence of actions taken on this pipe are:

    Establish a connection to the IPC$ share (SMBtconX). use encrypted passwords.
    Open an RPC Pipe with the name "\\PIPE\\lsarpc". Store the file handle.
    Using the file handle, send a Set Named Pipe Handle state to 0x4300.
    Send an LSA Open Policy request. Store the Policy Handle.
    Using the Policy Handle, send LSA Query Info Policy requests, etc.
    Using the Policy Handle, send an LSA Close.
    Close the IPC$ share.

    Defines for this pipe, identifying the query are:

    LSA Open Policy:

    0x2c

    LSA Query Info Policy:

    0x07

    LSA Enumerate Trusted Domains:

    0x0d

    LSA Open Secret:

    0xff

    LSA Lookup SIDs:

    0xfe

    LSA Lookup Names:

    0xfd

    LSA Close:

    0x00

    LSA Open Policy

    Note: The policy handle can be anything you like.

    Request

    VOID*

    buffer pointer

    UNISTR2

    server name - unicode string starting with two '\'s

    OBJ_ATTR

    object attributes

    UINT32

    1 - desired access

    Response

    POL_HND

    LSA policy handle

    return

    0 - indicates success

    LSA Query Info Policy

    Note: The info class in response must be the same as that in the request.

    Request

    POL_HND

    LSA policy handle

    UINT16

    info class (also a policy handle?)

    Response

    VOID*

    undocumented buffer pointer

    UINT16

    info class (same as info class in request).

     switch (info class)
 case 3:
 case 5:
@@ -1292,11 +1289,11 @@ DOM_INFO domain info, levels 3 and 5 (are the same).
 }
 
 return    0 - indicates success
-

    LSA Enumerate Trusted Domains

    Request

    no extra data

    Response

    UINT32

    0 - enumeration context

    UINT32

    0 - entries read

    UINT32

    0 - trust information

    return

    0x8000 001a - "no trusted domains" success code

    LSA Open Secret

    Request

    no extra data

    Response

    UINT32

    0 - undocumented

    UINT32

    0 - undocumented

    UINT32

    0 - undocumented

    UINT32

    0 - undocumented

    UINT32

    0 - undocumented

    return 0x0C00 0034 - "no such secret" success code

    LSA Close

    Request

    POL_HND

    policy handle to be closed

    Response

    POL_HND

    0s - closed policy handle (all zeros)

    return 0 - indicates success

    LSA Lookup SIDS

    Note: num_entries in response must be same as num_entries in request.

    Request

    POL_HND

    LSA policy handle

    UINT32

    num_entries

    VOID*

    undocumented domain SID buffer pointer

    VOID*

    undocumented domain name buffer pointer

    VOID*[num_entries] undocumented domain SID pointers to be looked up. -

    DOM_SID[num_entries] domain SIDs to be looked up.

    char[16]

    completely undocumented 16 bytes.

    Response

    DOM_REF

    domain reference response

    UINT32

    num_entries (listed above)

    VOID*

    undocumented buffer pointer

    UINT32

    num_entries (listed above)

    DOM_SID2[num_entries]

    domain SIDs (from Request, listed above).

    UINT32

    num_entries (listed above)

    return 0 - indicates success

    LSA Lookup Names

    Note: num_entries in response must be same as num_entries in request.

    Request

    POL_HND

    LSA policy handle

    UINT32

    num_entries

    UINT32

    num_entries

    VOID*

    undocumented domain SID buffer pointer

    VOID*

    undocumented domain name buffer pointer

    NAME[num_entries]

    names to be looked up.

    char[]

    undocumented bytes - falsely translated SID structure?

    Response

    DOM_REF

    domain reference response

    UINT32

    num_entries (listed above)

    VOID*

    undocumented buffer pointer

    UINT32

    num_entries (listed above)

    DOM_RID[num_entries]

    domain SIDs (from Request, listed above).

    UINT32

    num_entries (listed above)

    return 0 - indicates success

    NETLOGON rpc Transact Named Pipe

    The sequence of actions taken on this pipe are:

    tablish a connection to the IPC$ share (SMBtconX). use encrypted passwords.
    en an RPC Pipe with the name "\\PIPE\\NETLOGON". Store the file handle.
    ing the file handle, send a Set Named Pipe Handle state to 0x4300.
    eate Client Challenge. Send LSA Request Challenge. Store Server Challenge.
    lculate Session Key. Send an LSA Auth 2 Challenge. Store Auth2 Challenge.
    lc/Verify Client Creds. Send LSA Srv PW Set. Calc/Verify Server Creds.
    lc/Verify Client Creds. Send LSA SAM Logon . Calc/Verify Server Creds.
    lc/Verify Client Creds. Send LSA SAM Logoff. Calc/Verify Server Creds.
    ose the IPC$ share.

    Defines for this pipe, identifying the query are

    LSA Request Challenge:

    0x04

    LSA Server Password Set:

    0x06

    LSA SAM Logon:

    0x02

    LSA SAM Logoff:

    0x03

    LSA Auth 2:

    0x0f

    LSA Logon Control:

    0x0e

    LSA Request Challenge

    Note: logon server name starts with two '\' characters and is upper case.

    Note: logon client is the machine, not the user.

    Note: the initial LanManager password hash, against which the challenge is issued, is the machine name itself (lower case). there will becalls issued (LSA Server Password Set) which will change this, later. refusing these calls allows you to always deal with the same password (i.e the LM# of the machine name in lower case).

    Request

    VOID*

    undocumented buffer pointer

    UNISTR2

    logon server unicode string

    UNISTR2

    logon client unicode string

    char[8]

    client challenge

    Response

    char[8]

    server challenge

    return 0 - indicates success

    LSA Authenticate 2

    Note: in between request and response, calculate the client credentials, and check them against the client-calculated credentials (this process uses the previously received client credentials).

    Note: neg_flags in the response is the same as that in the request.

    Note: you must take a copy of the client-calculated credentials received here, because they will be used in subsequent authentication packets.

    Request

    LOG_INFO

    client identification info

    char[8]

    client-calculated credentials

    UINT8[]

    padding to 4-byte align with start of SMB header.

    UINT32

    neg_flags - negotiated flags (usual value is 0x0000 01ff)

    Response

    char[8]

    server credentials.

    UINT32

    neg_flags - same as neg_flags in request.

    return 0 - indicates success. failure value unknown.

    LSA Server Password Set

    Note: the new password is suspected to be a DES encryption using the old password to generate the key.

    Note: in between request and response, calculate the client credentials, and check them against the client-calculated credentials (this process uses the previously received client credentials).

    Note: the server credentials are constructed from the client-calculated credentials and the client time + 1 second.

    Note: you must take a copy of the client-calculated credentials received here, because they will be used in subsequent authentication packets.

    Request

    CLNT_INFO

    client identification/authentication info

    char[]

    new password - undocumented.

    Response

    CREDS

    server credentials. server time stamp appears to be ignored.

    return 0 - indicates success; 0xC000 006a indicates failure

    LSA SAM Logon

    +

    LSA Enumerate Trusted Domains

    Request

    no extra data

    Response

    UINT32

    0 - enumeration context

    UINT32

    0 - entries read

    UINT32

    0 - trust information

    return

    0x8000 001a - "no trusted domains" success code

    LSA Open Secret

    Request

    no extra data

    Response

    UINT32

    0 - undocumented

    UINT32

    0 - undocumented

    UINT32

    0 - undocumented

    UINT32

    0 - undocumented

    UINT32

    0 - undocumented

    return 0x0C00 0034 - "no such secret" success code

    LSA Close

    Request

    POL_HND

    policy handle to be closed

    Response

    POL_HND

    0s - closed policy handle (all zeros)

    return 0 - indicates success

    LSA Lookup SIDS

    Note: num_entries in response must be same as num_entries in request.

    Request

    POL_HND

    LSA policy handle

    UINT32

    num_entries

    VOID*

    undocumented domain SID buffer pointer

    VOID*

    undocumented domain name buffer pointer

    VOID*[num_entries] undocumented domain SID pointers to be looked up. +

    DOM_SID[num_entries] domain SIDs to be looked up.

    char[16]

    completely undocumented 16 bytes.

    Response

    DOM_REF

    domain reference response

    UINT32

    num_entries (listed above)

    VOID*

    undocumented buffer pointer

    UINT32

    num_entries (listed above)

    DOM_SID2[num_entries]

    domain SIDs (from Request, listed above).

    UINT32

    num_entries (listed above)

    return 0 - indicates success

    LSA Lookup Names

    Note: num_entries in response must be same as num_entries in request.

    Request

    POL_HND

    LSA policy handle

    UINT32

    num_entries

    UINT32

    num_entries

    VOID*

    undocumented domain SID buffer pointer

    VOID*

    undocumented domain name buffer pointer

    NAME[num_entries]

    names to be looked up.

    char[]

    undocumented bytes - falsely translated SID structure?

    Response

    DOM_REF

    domain reference response

    UINT32

    num_entries (listed above)

    VOID*

    undocumented buffer pointer

    UINT32

    num_entries (listed above)

    DOM_RID[num_entries]

    domain SIDs (from Request, listed above).

    UINT32

    num_entries (listed above)

    return 0 - indicates success

    NETLOGON rpc Transact Named Pipe

    The sequence of actions taken on this pipe are:

    tablish a connection to the IPC$ share (SMBtconX). use encrypted passwords.
    en an RPC Pipe with the name "\\PIPE\\NETLOGON". Store the file handle.
    ing the file handle, send a Set Named Pipe Handle state to 0x4300.
    eate Client Challenge. Send LSA Request Challenge. Store Server Challenge.
    lculate Session Key. Send an LSA Auth 2 Challenge. Store Auth2 Challenge.
    lc/Verify Client Creds. Send LSA Srv PW Set. Calc/Verify Server Creds.
    lc/Verify Client Creds. Send LSA SAM Logon . Calc/Verify Server Creds.
    lc/Verify Client Creds. Send LSA SAM Logoff. Calc/Verify Server Creds.
    ose the IPC$ share.

    Defines for this pipe, identifying the query are

    LSA Request Challenge:

    0x04

    LSA Server Password Set:

    0x06

    LSA SAM Logon:

    0x02

    LSA SAM Logoff:

    0x03

    LSA Auth 2:

    0x0f

    LSA Logon Control:

    0x0e

    LSA Request Challenge

    Note: logon server name starts with two '\' characters and is upper case.

    Note: logon client is the machine, not the user.

    Note: the initial LanManager password hash, against which the challenge is issued, is the machine name itself (lower case). there will becalls issued (LSA Server Password Set) which will change this, later. refusing these calls allows you to always deal with the same password (i.e the LM# of the machine name in lower case).

    Request

    VOID*

    undocumented buffer pointer

    UNISTR2

    logon server unicode string

    UNISTR2

    logon client unicode string

    char[8]

    client challenge

    Response

    char[8]

    server challenge

    return 0 - indicates success

    LSA Authenticate 2

    Note: in between request and response, calculate the client credentials, and check them against the client-calculated credentials (this process uses the previously received client credentials).

    Note: neg_flags in the response is the same as that in the request.

    Note: you must take a copy of the client-calculated credentials received here, because they will be used in subsequent authentication packets.

    Request

    LOG_INFO

    client identification info

    char[8]

    client-calculated credentials

    UINT8[]

    padding to 4-byte align with start of SMB header.

    UINT32

    neg_flags - negotiated flags (usual value is 0x0000 01ff)

    Response

    char[8]

    server credentials.

    UINT32

    neg_flags - same as neg_flags in request.

    return 0 - indicates success. failure value unknown.

    LSA Server Password Set

    Note: the new password is suspected to be a DES encryption using the old password to generate the key.

    Note: in between request and response, calculate the client credentials, and check them against the client-calculated credentials (this process uses the previously received client credentials).

    Note: the server credentials are constructed from the client-calculated credentials and the client time + 1 second.

    Note: you must take a copy of the client-calculated credentials received here, because they will be used in subsequent authentication packets.

    Request

    CLNT_INFO

    client identification/authentication info

    char[]

    new password - undocumented.

    Response

    CREDS

    server credentials. server time stamp appears to be ignored.

    return 0 - indicates success; 0xC000 006a indicates failure

    LSA SAM Logon

    Note: valid_user is True iff the username and password hash are valid for the requested domain. -

    Request

    SAM_INFO

    sam_id structure

    Response

    VOID*

    undocumented buffer pointer

    CREDS

    server credentials. server time stamp appears to be ignored.

    +
    Request
    SAM_INFO
    sam_id structure
    Response
    VOID*
    undocumented buffer pointer
    CREDS
    server credentials.  server time stamp appears to be ignored.
     if (valid_user)
 {
 	UINT16      3 - switch value indicating USER_INFO structure.
@@ -1316,16 +1313,16 @@ else
 
     return    0xC000 0064 - NT_STATUS_NO_SUCH_USER.
 }
-

    LSA SAM Logoff

    +

    LSA SAM Logoff

    Note: presumably, the SAM_INFO structure is validated, and a (currently undocumented) error code returned if the Logoff is invalid. -

    Request

    SAM_INFO

    sam_id structure

    Response

    VOID*

    undocumented buffer pointer

    CREDS

    server credentials. server time stamp appears to be ignored.

    return 0 - indicates success. undocumented failure indication.

    \\MAILSLOT\NET\NTLOGON

    +

    Request

    SAM_INFO

    sam_id structure

    Response

    VOID*

    undocumented buffer pointer

    CREDS

    server credentials. server time stamp appears to be ignored.

    return 0 - indicates success. undocumented failure indication.

    \\MAILSLOT\NET\NTLOGON

    Note: mailslots will contain a response mailslot, to which the response should be sent. the target NetBIOS name is REQUEST_NAME<20>, where REQUEST_NAME is the name of the machine that sent the request. -

    Query for PDC

    Note: NTversion, LMNTtoken, LM20token in response are the same as those given in the request.

    Request

    UINT16

    0x0007 - Query for PDC

    STR

    machine name

    STR

    response mailslot

    UINT8[]

    padding to 2-byte align with start of mailslot.

    UNISTR

    machine name

    UINT32

    NTversion

    UINT16

    LMNTtoken

    UINT16

    LM20token

    Response

    UINT16

    0x000A - Respose to Query for PDC

    STR

    machine name (in uppercase)

    UINT8[]

    padding to 2-byte align with start of mailslot.

    UNISTR

    machine name

    UNISTR

    domain name

    UINT32

    NTversion (same as received in request)

    UINT16

    LMNTtoken (same as received in request)

    UINT16

    LM20token (same as received in request)

    SAM Logon

    Note: machine name in response is preceded by two '\' characters.

    Note: NTversion, LMNTtoken, LM20token in response are the same as those given in the request.

    Note: user name in the response is presumably the same as that in the request.

    Request

    UINT16

    0x0012 - SAM Logon

    UINT16

    request count

    UNISTR

    machine name

    UNISTR

    user name

    STR

    response mailslot

    UINT32

    alloweable account

    UINT32

    domain SID size

    char[sid_size]

    domain SID, of sid_size bytes.

    UINT8[]

    ???? padding to 4? 2? -byte align with start of mailslot.

    UINT32

    NTversion

    UINT16

    LMNTtoken

    UINT16

    LM20token

    Response

    UINT16

    0x0013 - Response to SAM Logon

    UNISTR

    machine name

    UNISTR

    user name - workstation trust account

    UNISTR

    domain name

    UINT32

    NTversion

    UINT16

    LMNTtoken

    UINT16

    LM20token

    SRVSVC Transact Named Pipe

    Defines for this pipe, identifying the query are:

    Net Share Enum

    0x0f

    Net Server Get Info

    0x15

    Net Share Enum

    Note: share level and switch value in the response are presumably the same as those in the request.

    Note: cifsrap2.txt (section 5) may be of limited assistance here.

    Request

    VOID*

    pointer (to server name?)

    UNISTR2

    server name

    UINT8[]

    padding to get unicode string 4-byte aligned with the start of the SMB header.

    UINT32

    share level

    UINT32

    switch value

    VOID*

    pointer to SHARE_INFO_1_CTR

    SHARE_INFO_1_CTR

    share info with 0 entries

    UINT32

    preferred maximum length (0xffff ffff)

    Response

    UINT32

    share level

    UINT32

    switch value

    VOID*

    pointer to SHARE_INFO_1_CTR

    SHARE_INFO_1_CTR

    share info (only added if share info ptr is non-zero)

    return 0 - indicates success

    Net Server Get Info

    Note: level is the same value as in the request.

    Request

    UNISTR2

    server name

    UINT32

    switch level

    Response

    UINT32

    switch level

    VOID*

    pointer to SERVER_INFO_101

    SERVER_INFO_101

    server info (only added if server info ptr is non-zero)

    return 0 - indicates success

    Cryptographic side of NT Domain Authentication

    Definitions

    Add(A1,A2)

    Intel byte ordered addition of corresponding 4 byte words in arrays A1 and A2

    E(K,D)

    DES ECB encryption of 8 byte data D using 7 byte key K

    lmowf()

    Lan man hash

    ntowf()

    NT hash

    PW

    md4(machine_password) == md4(lsadump $machine.acc) == +

    Query for PDC

    Note: NTversion, LMNTtoken, LM20token in response are the same as those given in the request.

    Request

    UINT16

    0x0007 - Query for PDC

    STR

    machine name

    STR

    response mailslot

    UINT8[]

    padding to 2-byte align with start of mailslot.

    UNISTR

    machine name

    UINT32

    NTversion

    UINT16

    LMNTtoken

    UINT16

    LM20token

    Response

    UINT16

    0x000A - Respose to Query for PDC

    STR

    machine name (in uppercase)

    UINT8[]

    padding to 2-byte align with start of mailslot.

    UNISTR

    machine name

    UNISTR

    domain name

    UINT32

    NTversion (same as received in request)

    UINT16

    LMNTtoken (same as received in request)

    UINT16

    LM20token (same as received in request)

    SAM Logon

    Note: machine name in response is preceded by two '\' characters.

    Note: NTversion, LMNTtoken, LM20token in response are the same as those given in the request.

    Note: user name in the response is presumably the same as that in the request.

    Request

    UINT16

    0x0012 - SAM Logon

    UINT16

    request count

    UNISTR

    machine name

    UNISTR

    user name

    STR

    response mailslot

    UINT32

    alloweable account

    UINT32

    domain SID size

    char[sid_size]

    domain SID, of sid_size bytes.

    UINT8[]

    ???? padding to 4? 2? -byte align with start of mailslot.

    UINT32

    NTversion

    UINT16

    LMNTtoken

    UINT16

    LM20token

    Response

    UINT16

    0x0013 - Response to SAM Logon

    UNISTR

    machine name

    UNISTR

    user name - workstation trust account

    UNISTR

    domain name

    UINT32

    NTversion

    UINT16

    LMNTtoken

    UINT16

    LM20token

    SRVSVC Transact Named Pipe

    Defines for this pipe, identifying the query are:

    Net Share Enum

    0x0f

    Net Server Get Info

    0x15

    Net Share Enum

    Note: share level and switch value in the response are presumably the same as those in the request.

    Note: cifsrap2.txt (section 5) may be of limited assistance here.

    Request

    VOID*

    pointer (to server name?)

    UNISTR2

    server name

    UINT8[]

    padding to get unicode string 4-byte aligned with the start of the SMB header.

    UINT32

    share level

    UINT32

    switch value

    VOID*

    pointer to SHARE_INFO_1_CTR

    SHARE_INFO_1_CTR

    share info with 0 entries

    UINT32

    preferred maximum length (0xffff ffff)

    Response

    UINT32

    share level

    UINT32

    switch value

    VOID*

    pointer to SHARE_INFO_1_CTR

    SHARE_INFO_1_CTR

    share info (only added if share info ptr is non-zero)

    return 0 - indicates success

    Net Server Get Info

    Note: level is the same value as in the request.

    Request

    UNISTR2

    server name

    UINT32

    switch level

    Response

    UINT32

    switch level

    VOID*

    pointer to SERVER_INFO_101

    SERVER_INFO_101

    server info (only added if server info ptr is non-zero)

    return 0 - indicates success

    Cryptographic side of NT Domain Authentication

    Definitions

    Add(A1,A2)

    Intel byte ordered addition of corresponding 4 byte words in arrays A1 and A2

    E(K,D)

    DES ECB encryption of 8 byte data D using 7 byte key K

    lmowf()

    Lan man hash

    ntowf()

    NT hash

    PW

    md4(machine_password) == md4(lsadump $machine.acc) == pwdump(machine$) (initially) == md4(lmowf(unicode(machine))) -

    ARC4(K,Lk,D,Ld)

    ARC4 encryption of data D of length Ld with key K of length Lk

    v[m..n(,l)]

    subset of v from bytes m to n, optionally padded with zeroes to length l

    Cred(K,D)

    E(K[7..7,7],E(K[0..6],D)) computes a credential

    Time()

    4 byte current time

    Cc,Cs

    8 byte client and server challenges Rc,Rs: 8 byte client and server credentials

    Protocol

    +
    ARC4(K,Lk,D,Ld)
    ARC4 encryption of data D of length Ld with key K of length Lk
    v[m..n(,l)]
    subset of v from bytes m to n, optionally padded with zeroes to length l
    Cred(K,D)
    E(K[7..7,7],E(K[0..6],D)) computes a credential
    Time()
    4 byte current time
    Cc,Cs
    8 byte client and server challenges Rc,Rs: 8 byte client and server credentials

    Protocol

     C->S ReqChal,Cc
 S->C Cs
 
    @@ -1361,7 +1358,7 @@ S: Ts = Time()
 S->C Cred(Ks,Cred(Ks,Rc+Tc+1)),userinfo(logon script,UID,SIDs,etc)
 C: assert(Rs == Cred(Ks,Cred(Rc+Tc+1))
 C: Rc = Cred(Ks,Rc+Tc+1)
-

    Comments

    +

    Comments

    On first joining the domain the session key could be computed by anyone listening in on the network as the machine password has a well known value. Until the machine is rebooted it will use this session @@ -1382,30 +1379,30 @@ returned by the server. The password OWFs should NOT be sent over the network reversibly encrypted. They should be sent using ARC4(Ks,md4(owf)) with the server computing the same function using the owf values in the SAM. -

    SIDs and RIDs

    +

    SIDs and RIDs

    SIDs and RIDs are well documented elsewhere.

    A SID is an NT Security ID (see DOM_SID structure). They are of the form:

    revision-NN-SubAuth1-SubAuth2-SubAuth3...
    revision-0xNNNNNNNNNNNN-SubAuth1-SubAuth2-SubAuth3...

    currently, the SID revision is 1. The Sub-Authorities are known as Relative IDs (RIDs). -

    Well-known SIDs

    Universal well-known SIDs

    Null SID

    S-1-0-0

    World

    S-1-1-0

    Local

    S-1-2-0

    Creator Owner ID

    S-1-3-0

    Creator Group ID

    S-1-3-1

    Creator Owner Server ID

    S-1-3-2

    Creator Group Server ID

    S-1-3-3

    (Non-unique IDs)

    S-1-4

    NT well-known SIDs

    NT Authority

    S-1-5

    Dialup

    S-1-5-1

    Network

    S-1-5-2

    Batch

    S-1-5-3

    Interactive

    S-1-5-4

    Service

    S-1-5-6

    AnonymousLogon(aka null logon session)

    S-1-5-7

    Proxy

    S-1-5-8

    ServerLogon(aka domain controller account)

    S-1-5-8

    (Logon IDs)

    S-1-5-5-X-Y

    (NT non-unique IDs)

    S-1-5-0x15-...

    (Built-in domain)

    s-1-5-0x20

    Well-known RIDS

    +

    Well-known SIDs

    Universal well-known SIDs

    Null SID

    S-1-0-0

    World

    S-1-1-0

    Local

    S-1-2-0

    Creator Owner ID

    S-1-3-0

    Creator Group ID

    S-1-3-1

    Creator Owner Server ID

    S-1-3-2

    Creator Group Server ID

    S-1-3-3

    (Non-unique IDs)

    S-1-4

    NT well-known SIDs

    NT Authority

    S-1-5

    Dialup

    S-1-5-1

    Network

    S-1-5-2

    Batch

    S-1-5-3

    Interactive

    S-1-5-4

    Service

    S-1-5-6

    AnonymousLogon(aka null logon session)

    S-1-5-7

    Proxy

    S-1-5-8

    ServerLogon(aka domain controller account)

    S-1-5-8

    (Logon IDs)

    S-1-5-5-X-Y

    (NT non-unique IDs)

    S-1-5-0x15-...

    (Built-in domain)

    s-1-5-0x20

    Well-known RIDS

    A RID is a sub-authority value, as part of either a SID, or in the case of Group RIDs, part of the DOM_GID structure, in the USER_INFO_1 structure, in the LSA SAM Logon response. -

    Well-known RID users

    Groupname: DOMAIN_USER_RID_ADMIN

    ????: 0x0000

    RID: 01F4

    Groupname: DOMAIN_USER_RID_GUEST

    ????: 0x0000

    RID: 01F5

    Well-known RID groups

    Groupname: DOMAIN_GROUP_RID_ADMINS

    ????: 0x0000

    RID: 0200

    Groupname: DOMAIN_GROUP_RID_USERS

    ????: 0x0000

    RID: 0201

    Groupname: DOMAIN_GROUP_RID_GUESTS

    ????: 0x0000

    RID: 0202

    Well-known RID aliases

    Groupname: DOMAIN_ALIAS_RID_ADMINS

    ????: 0x0000

    RID: 0220

    Groupname: DOMAIN_ALIAS_RID_USERS

    ????: 0x0000

    RID: 0221

    Groupname: DOMAIN_ALIAS_RID_GUESTS

    ????: 0x0000

    RID: 0222

    Groupname: DOMAIN_ALIAS_RID_POWER_USERS

    ????: 0x0000

    RID: 0223

    Groupname: DOMAIN_ALIAS_RID_ACCOUNT_OPS

    ????: 0x0000

    RID: 0224

    Groupname: DOMAIN_ALIAS_RID_SYSTEM_OPS

    ????: 0x0000

    RID: 0225

    Groupname: DOMAIN_ALIAS_RID_PRINT_OPS

    ????: 0x0000

    RID: 0226

    Groupname: DOMAIN_ALIAS_RID_BACKUP_OPS

    ????: 0x0000

    RID: 0227

    Groupname: DOMAIN_ALIAS_RID_REPLICATOR

    ????: 0x0000

    RID: 0228

    Chapter 11. Samba Printing Internals

    Gerald Carter

    October 2002

    Table of Contents

    Abstract
    +

    Well-known RID users

    Groupname: DOMAIN_USER_RID_ADMIN

    ????: 0x0000

    RID: 01F4

    Groupname: DOMAIN_USER_RID_GUEST

    ????: 0x0000

    RID: 01F5

    Well-known RID groups

    Groupname: DOMAIN_GROUP_RID_ADMINS

    ????: 0x0000

    RID: 0200

    Groupname: DOMAIN_GROUP_RID_USERS

    ????: 0x0000

    RID: 0201

    Groupname: DOMAIN_GROUP_RID_GUESTS

    ????: 0x0000

    RID: 0202

    Well-known RID aliases

    Groupname: DOMAIN_ALIAS_RID_ADMINS

    ????: 0x0000

    RID: 0220

    Groupname: DOMAIN_ALIAS_RID_USERS

    ????: 0x0000

    RID: 0221

    Groupname: DOMAIN_ALIAS_RID_GUESTS

    ????: 0x0000

    RID: 0222

    Groupname: DOMAIN_ALIAS_RID_POWER_USERS

    ????: 0x0000

    RID: 0223

    Groupname: DOMAIN_ALIAS_RID_ACCOUNT_OPS

    ????: 0x0000

    RID: 0224

    Groupname: DOMAIN_ALIAS_RID_SYSTEM_OPS

    ????: 0x0000

    RID: 0225

    Groupname: DOMAIN_ALIAS_RID_PRINT_OPS

    ????: 0x0000

    RID: 0226

    Groupname: DOMAIN_ALIAS_RID_BACKUP_OPS

    ????: 0x0000

    RID: 0227

    Groupname: DOMAIN_ALIAS_RID_REPLICATOR

    ????: 0x0000

    RID: 0228

    Chapter 11. Samba Printing Internals

    Gerald Carter

    October 2002

    Table of Contents

    Abstract
    Printing Interface to Various Back ends -
    +
    Print Queue TDB's -
    +
    ChangeID and Client Caching of Printer Information -
    +
    Windows NT/2K Printer Change Notify -

    Abstract

    +

    Abstract

    The purpose of this document is to provide some insight into Samba's printing functionality and also to describe the semantics of certain features of Windows client printing. -

    +

    Printing Interface to Various Back ends

    Samba uses a table of function pointers to seven functions. The @@ -1416,10 +1413,10 @@ Currently there are only two printing back end implementations defined.

    • a generic set of functions for working with standard UNIX printing subsystems

    • a set of CUPS specific functions (this is only enabled if - the CUPS libraries were located at compile time).

    + the CUPS libraries were located at compile time).

    Print Queue TDB's

    -Samba provides periodic caching of the output from the "lpq command" +Samba provides periodic caching of the output from the "lpq command" for performance reasons. This cache time is configurable in seconds. Obviously the longer the cache time the less often smbd will be required to exec a copy of lpq. However, the accuracy of the print @@ -1439,7 +1436,7 @@ There are two ways in which a a print job can be entered into a print queue's TDB. The first is to submit the job from a Windows client which will insert the job information directly into the TDB. The second method is to have the print job picked up by executing the -"lpq command". +"lpq command". 

     /* included from printing.h */
 struct printjob {
@@ -1460,9 +1457,9 @@ struct printjob {
 };

    The current manifestation of the printjob structure contains a field -for the UNIX job id returned from the "lpq command" and a Windows job +for the UNIX job id returned from the "lpq command" and a Windows job ID (32-bit bounded by PRINT_MAX_JOBID). When a print job is returned -by the "lpq command" that does not match an existing job in the queue's +by the "lpq command" that does not match an existing job in the queue's TDB, a 32-bit job ID above the <*vance doesn't know what word is missing here*> is generating by adding UNIX_JOB_START to the id reported by lpq.

    @@ -1477,7 +1474,7 @@ steps ( refer to print.c:print_queue_update() ): stored in LOCK/printer_name. If so, then do not update the TDB.

  • Lock the mutex entry in the TDB and store our own pid. Check that this succeeded, else fail.

  • Store the updated time stamp for the new cache - listing

  • Retrieve the queue listing via "lpq command"

  • +	listing

  • Retrieve the queue listing via "lpq command"

  •  	foreach job in the queue
      	{
 		if the job is a UNIX job, create a new entry;
@@ -1492,7 +1489,7 @@ steps ( refer to print.c:print_queue_update() ):
 	}

  • Delete any jobs in the TDB that are not in the in the lpq listing

  • Store the print queue status in the TDB

  • update the cache time stamp again

    • Note that it is the contents of this TDB that is returned to Windows -clients and not the actual listing from the "lpq command". +clients and not the actual listing from the "lpq command".

    The NT_DEVICEMODE stored as part of the printjob structure is used to store a pointer to a non-default DeviceMode associated with the print @@ -1505,11 +1502,11 @@ and the job has the printer's device mode associated with it by default. Only non-default Device Mode are stored with print jobs in the print queue TDB. Otherwise, the Device Mode is obtained from the printer object when the client issues a GetJob(level == 2) request. -

    +

    ChangeID and Client Caching of Printer Information

    [To be filled in later] -

    +

    Windows NT/2K Printer Change Notify

    When working with Windows NT+ clients, it is possible for a @@ -1607,13 +1604,13 @@ handle for notification. Samba currently uses the snum of the printer for this which can break if the list of services has been modified since the notification handle was registered.

  • The size is either (a) the string length in UNICODE for strings, (b) the size in bytes of the security descriptor, or (c) 0 for -data values.

    • Chapter 12. Samba WINS Internals

    Gerald Carter

    October 2002

    Table of Contents

    WINS Failover

    WINS Failover

    +data values.

    Chapter 12. Samba WINS Internals

    Gerald Carter

    October 2002

    Table of Contents

    WINS Failover

    WINS Failover

    The current Samba codebase possesses the capability to use groups of WINS servers that share a common namespace for NetBIOS name registration and resolution. The formal parameter syntax is 

     	WINS_SERVER_PARAM 	= SERVER [ SEPARATOR SERVER_LIST ]
-	WINS_SERVER_PARAM 	= "wins server"
+	WINS_SERVER_PARAM 	= "wins server"
 	SERVER 			= ADDR[:TAG]
 	ADDR 			= ip_addr | fqdn
 	TAG 			= string
@@ -1626,7 +1623,7 @@ A simple example of a valid wins server setting is
 	wins server = 192.168.1.2 192.168.1.3

    In the event that no TAG is defined in for a SERVER in the list, smbd assigns a default -TAG of "*". A TAG is used to group servers of a shared NetBIOS namespace together. Upon +TAG of "*". A TAG is used to group servers of a shared NetBIOS namespace together. Upon startup, nmbd will attempt to register the netbios name value with one server in each tagged group.

    @@ -1637,7 +1634,7 @@ interface names in the tags is only by convention and is not a technical require wins server = 192.168.1.2:eth0 192.168.1.3:eth0 192.168.2.2:eth1

    Using this configuration, nmbd would attempt to register the server's NetBIOS name -with one WINS server in each group. Because the "eth0" group has two servers, the +with one WINS server in each group. Because the "eth0" group has two servers, the second server would only be used when a registration (or resolution) request to the first server in that group timed out.

    @@ -1649,7 +1646,7 @@ If a timeout occurs when querying a specific WINS server, that server is marked prevent further timeouts and the next server in the WINS group is contacted. Once marked as dead, Samba will not attempt to contact that server for name registration/resolution queries for a period of 10 minutes. -

    Chapter 13. The Upcoming SAM System

    Andrew Bartlett

    1 October 2002

    Table of Contents

    Security in the 'new SAM'
    Standalone from UNIX
    Handles and Races in the new SAM
    Layers
    Application
    SAM Interface
    SAM Modules
    SAM Modules
    Special Module: sam_passdb
    sam_ads
    Memory Management
    Testing

    Security in the 'new SAM'

    One of the biggest problems with passdb is it's implementation of +

    Chapter 13. The Upcoming SAM System

    Andrew Bartlett

    1 October 2002

    Table of Contents

    Security in the 'new SAM'
    Standalone from UNIX
    Handles and Races in the new SAM
    Layers
    Application
    SAM Interface
    SAM Modules
    SAM Modules
    Special Module: sam_passdb
    sam_ads
    Memory Management
    Testing

    Security in the 'new SAM'

    One of the biggest problems with passdb is it's implementation of 'security'. Access control is on a 'are you root at the moment' basis, and it has no concept of NT ACLs. Things like ldapsam had to add 'magic' 'are you root' checks.

    We took this very seriously when we started work, and the new structure @@ -1709,7 +1706,7 @@ actual data store (like the LDAP server).

    Finally, we have generic get_sec_desc() and set_sec_desc() routines to allow external ACL manipulation. These do lookups based on SID. -

    Standalone from UNIX

    +

    Standalone from UNIX

    One of the primary tenants of the 'new SAM' is that it would not attempt to deal with 'what unix id for that'. This would be left to the 'SMS' (Sid Mapping System') or SID farm, and probably administered via @@ -1719,7 +1716,7 @@ Accounts not preexisting in unix would be served up via winbind.

    This is an *optional* part, and my preferred end-game. We have a fare way to go before things like winbind up to it however. -

    Handles and Races in the new SAM

    +

    Handles and Races in the new SAM

    One of the things that the 'new SAM' work has tried to face is both compatibility with existing code, and a closer alignment to the SAMR interface. I consider SAMR to be a 'primary customer' to the this work, @@ -1744,11 +1741,11 @@ have *really* changed. 'conflicting' updates: Currently we don't deal with this (in passdb or the new sam stuff), but the design is sufficiently flexible to 'deny' a second update. I don't foresee locking records however. -

    Layers

    Application

    +

    Layers

    Application

    This is where smbd, samtest and whatever end-user replacement we have for pdbedit sits. They use only the SAM interface, and do not get 'special knowledge' of what is below them. -

    SAM Interface

    +

    SAM Interface

    This level 'owns' the various handle structures, the get/set routines on those structures and provides the public interface. The application layer may initialize a 'context' to be passed to all interface routines, @@ -1759,7 +1756,7 @@ abstraction to the modules below, and arrange for their initial loading.

    We could possibly add ACL checking at this layer, to avoid discrepancies in implementation modules. -

    SAM Modules

    +

    SAM Modules

    These do not communicate with the application directly, only by setting values in the handles, and receiving requests from the interface. These modules are responsible for translating values from the handle's @@ -1767,13 +1764,13 @@ modules are responsible for translating values from the handle's to 'know' things like it's own domain SID, domain name, and any other state attached to the SAM. Simpler modules may call back to some helper routine. -

    SAM Modules

    Special Module: sam_passdb

    +

    SAM Modules

    Special Module: sam_passdb

    In order for there to be a smooth transition, kai is writing a module that reads existing passdb backends, and translates them into SAM replies. (Also pulling data from the account policy DB etc). We also intend to write a module that does the reverse - gives the SAM a passdb interface. -

    sam_ads

    +

    sam_ads

    This is the first of the SAM modules to be committed to the tree - mainly because I needed to coordinate work with metze (who authored most of it). This module aims to use Samba's libads code to provide an @@ -1785,7 +1782,7 @@ the construction of an Samba AD DC.

    We also intend to construct a Samba 2.2/3.0 compatible ldap module, again using libads code. -

    Memory Management

    +

    Memory Management

    The 'new SAM' development effort also concerned itself with getting a sane implementation of memory management. It was decided that we would be (as much as possible) talloc based, using an 'internal talloc @@ -1814,7 +1811,7 @@ NT_USER_TOKEN *access_token, uint32 access_desired, const DOM_SID NTSTATUS sam_enum_accounts(const SAM_CONTEXT *context, const NT_USER_TOKEN *access_token, const DOM_SID *domainsid, uint16 acct_ctrl, int32 *account_count, SAM_ACCOUNT_ENUM **accounts) -

    Testing

    +

    Testing

    Testing is vital in any piece of software, and Samba is certainly no exception. In designing this new subsystem, we have taken care to ensure it is easily tested, independent of outside protocols. @@ -1843,13 +1840,13 @@ Because the 'new SAM' is NT ACL based, there will be a command to specify an arbitrary NT ACL, but for now it uses 'system' by default.

    Chapter 14. LanMan and NT Password Encryption

    Jeremy Allison

    Samba Team



    -

    19 Apr 1999

    Table of Contents

    Introduction
    How does it work?
    The smbpasswd file

    Introduction

    With the development of LanManager and Windows NT +

    19 Apr 1999

    Table of Contents

    Introduction
    How does it work?
    The smbpasswd file

    Introduction

    With the development of LanManager and Windows NT compatible password encryption for Samba, it is now able to validate user connections in exactly the same way as a LanManager or Windows NT server.

    This document describes how the SMB password encryption algorithm works and what issues there are in choosing whether you want to use it. You should read it carefully, especially - the part about security and the "PROS and CONS" section.

    How does it work?

    LanManager encryption is somewhat similar to UNIX + the part about security and the "PROS and CONS" section.

    How does it work?

    LanManager encryption is somewhat similar to UNIX password encryption. The server uses a file containing a hashed value of a user's password. This is created by taking the user's plaintext password, capitalising it, and either @@ -1857,7 +1854,7 @@ specify an arbitrary NT ACL, but for now it uses 'system' by default. This 14 byte value is used as two 56 bit DES keys to encrypt a 'magic' eight byte value, forming a 16 byte value which is stored by the server and client. Let this value be known as - the "hashed password".

    Windows NT encryption is a higher quality mechanism, + the "hashed password".

    Windows NT encryption is a higher quality mechanism, consisting of doing an MD4 hash on a Unicode version of the user's password. This also produces a 16 byte hash value that is non-reversible.

    When a client (LanManager, Windows for WorkGroups, Windows @@ -1866,11 +1863,11 @@ specify an arbitrary NT ACL, but for now it uses 'system' by default. protocol that the client and server will use. In the reply to this request the Samba server generates and appends an 8 byte, random value - this is stored in the Samba server after the reply is sent - and is known as the "challenge". The challenge is different for + and is known as the "challenge". The challenge is different for every client connection.

    The client then uses the hashed password (16 byte values described above), appended with 5 null bytes, as three 56 bit DES keys, each of which is used to encrypt the challenge 8 byte - value, forming a 24 byte value known as the "response".

    In the SMB call SMBsessionsetupX (when user level security + value, forming a 24 byte value known as the "response".

    In the SMB call SMBsessionsetupX (when user level security is selected) or the call SMBtconX (when share level security is selected), the 24 byte response is returned by the client to the Samba server. For Windows NT protocol levels the above calculation @@ -1886,7 +1883,7 @@ specify an arbitrary NT ACL, but for now it uses 'system' by default. know the correct password and is denied access.

    Note that the Samba server never knows or stores the cleartext of the user's password - just the 16 byte hashed values derived from it. Also note that the cleartext password or 16 byte hashed values - are never transmitted over the network - thus increasing security.

    The smbpasswd file

    In order for Samba to participate in the above protocol + are never transmitted over the network - thus increasing security.

    The smbpasswd file

    In order for Samba to participate in the above protocol it must be able to look up the 16 byte hashed values given a user name. Unfortunately, as the UNIX password value is also a one way hash function (ie. it is impossible to retrieve the cleartext of the user's @@ -1927,7 +1924,7 @@ username:uid:XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX:XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX: to 32 ascii hexadecimal digits (0-9, A-F). These are an ascii representation of the 16 byte hashed value of a user's password.

    To set a user to have no password (not recommended), edit the file using vi, and replace the first 11 characters with the ascii text - "NO PASSWORD" (minus the quotes).

    For example, to clear the password for user bob, his smbpasswd file + "NO PASSWORD" (minus the quotes).

    For example, to clear the password for user bob, his smbpasswd file entry would look like :

     bob:100:NO PASSWORDXXXXXXXXXXXXXXXXXXXXX:XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX:
 	[U          ]:LCT-00000000:Bob's full name:/bobhome:/bobshell
@@ -1943,10 +1940,10 @@ bob:100:NO PASSWORDXXXXXXXXXXXXXXXXXXXXX:XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX:
 	to enable this on your server.
    Note : This file should be protected very 
 	carefully. Anyone with access to this file can (with enough knowledge of 
 	the protocols) gain access to your SMB server. The file is thus more 
-	sensitive than a normal unix /etc/passwd file.

    Chapter 15. Modules

    Jelmer Vernooij

    Samba Team

    19 March 2003

    Table of Contents

    Advantages
    Loading modules
    Static modules
    Shared modules
    Writing modules
    Static/Shared selection in configure.in

    Advantages

    + sensitive than a normal unix /etc/passwd file.

    Chapter 15. Modules

    Jelmer Vernooij

    Samba Team

    19 March 2003

    Table of Contents

    Advantages
    Loading modules
    Static modules
    Shared modules
    Writing modules
    Static/Shared selection in configure.in

    Advantages

    The new modules system has the following advantages:

    Transparent loading of static and shared modules (no need -for a subsystem to know about modules)
    Simple selection between shared and static modules at configure time
    "preload modules" option for increasing performance for stable modules
    No nasty #define stuff anymore
    All backends are available as plugin now (including pdb_ldap and pdb_tdb)

    Loading modules

    +for a subsystem to know about modules)Simple selection between shared and static modules at configure time"preload modules" option for increasing performance for stable modulesNo nasty #define stuff anymoreAll backends are available as plugin now (including pdb_ldap and pdb_tdb)

    Loading modules

    Some subsystems in samba use different backends. These backends can be either statically linked in to samba or available as a plugin. A subsystem should have a function that allows a module to register itself. For example, @@ -1956,7 +1953,7 @@ NTSTATUS smb_register_passdb(int version, const char *name, pdb_init_function in

    This function will be called by the initialisation function of the module to register itself. -

    Static modules

    +

    Static modules

    The modules system compiles a list of initialisation functions for the static modules of each subsystem. This is a define. For example, it is here currently (from include/config.h): @@ -1966,7 +1963,7 @@ it is here currently (from include/config.h):

    These functions should be called before the subsystem is used. That should be done when the subsystem is initialised or first used. -

    Shared modules

    +

    Shared modules

    If a subsystem needs a certain backend, it should check if it has already been registered. If the backend hasn't been registered already, the subsystem should call smb_probe_module(char *subsystem, char *backend). @@ -1976,7 +1973,7 @@ is a slash, smb_probe_module() tries to load the module from the absolute path specified in 'backend'.

    After smb_probe_module() has been executed, the subsystem should check again if the module has been registered. -

    Writing modules

    +

    Writing modules

    Each module has an initialisation function. For modules that are included with samba this name is 'subsystem_backend_init'. For external modules (that will never be built-in, but only available as a module) this name is always 'init_module'. (In the case of modules included with samba, the configure system will add a #define subsystem_backend_init() init_module()). The prototype for these functions is: @@ -1987,11 +1984,11 @@ registration functions. The function should return NT_STATUS_OK on success and NT_STATUS_UNSUCCESSFUL or a more useful nt error code on failure.

    For example, pdb_ldap_init() contains: 

     NTSTATUS pdb_ldap_init(void)
 {
-smb_register_passdb(PASSDB_INTERFACE_VERSION, "ldapsam", pdb_init_ldapsam);
-smb_register_passdb(PASSDB_INTERFACE_VERSION, "ldapsam_nua", pdb_init_ldapsam_nua);
+smb_register_passdb(PASSDB_INTERFACE_VERSION, "ldapsam", pdb_init_ldapsam);
+smb_register_passdb(PASSDB_INTERFACE_VERSION, "ldapsam_nua", pdb_init_ldapsam_nua);
 	return NT_STATUS_OK;
 }
-

    Static/Shared selection in configure.in

    +

    Static/Shared selection in configure.in

    Some macros in configure.in generate the various defines and substs that are necessary for the system to work correct. All modules that should be built by default have to be added to the variable 'default_modules'. @@ -2001,22 +1998,24 @@ On the bottom of configure.in, SMB_MODULE() should be called for each module and SMB_SUBSYSTEM() for each subsystem.

    Syntax:

     SMB_MODULE(subsystem_backend, object files, plugin name, subsystem name, static_action, shared_action)
-SMB_SUBSYSTEM(subsystem)
-

    Also, make sure to add the correct directives to -Makefile.in. @SUBSYSTEM_STATIC@ -will be replaced with a list of objects files of the modules that need to -be linked in statically. @SUBSYSTEM_MODULES@ will +SMB_SUBSYSTEM(subsystem,depfile) +

    The depfile for a certain subsystem is the file that calls the +initialisation functions for the statically built in modules.

    +@SUBSYSTEM_MODULES@ in Makefile.in will be replaced with the names of the plugins to build.

    You must make sure all .c files that contain defines that can be changed by ./configure are rebuilded in the 'modules_clean' make target. Practically, this means all c files that contain static_init_subsystem; calls need to be rebuilded. -

    Chapter 16. RPC Pluggable Modules

    Anthony Liguori

    IBM

    Jelmer Vernooij

    Samba Team

    January 2003

    Table of Contents

    About
    General Overview

    About

    +

    Note

    +There currently also is a configure.in command called SMB_MODULE_PROVIVES(). +This is used for modules that register multiple things. It should not +be used as probing will most likely disappear in the future.

    Chapter 16. RPC Pluggable Modules

    Anthony Liguori

    IBM

    Jelmer Vernooij

    Samba Team

    January 2003

    Table of Contents

    About
    General Overview

    About

    This document describes how to make use the new RPC Pluggable Modules features of Samba 3.0. This architecture was added to increase the maintainability of Samba allowing RPC Pipes to be worked on separately from the main CVS branch. The RPM architecture will also allow third-party vendors to add functionality to Samba through plug-ins. -

    General Overview

    +

    General Overview

    When an RPC call is sent to smbd, smbd tries to load a shared library by the name librpc_<pipename>.so to handle the call if it doesn't know how to handle the call internally. For instance, LSA calls @@ -2033,7 +2032,7 @@ NTSTATUS rpc_pipe_register_commands(int version, const char *clnt, const char *s argument.

    clnt

    the Client name of the named pipe

    srv

    the Server name of the named pipe

    cmds

    a list of api_structs that map RPC ordinal numbers to function calls

    size

    the number of api_structs contained in cmds

    See rpc_server/srv_reg.c and rpc_server/srv_reg_nt.c for a small example of how to use this library. -

    Chapter 17. VFS Modules

    Alexander Bokovoy

    Stefan Metzmacher

    27 May 2003

    Table of Contents

    The Samba (Posix) VFS layer
    The general interface
    Possible VFS operation layers
    The Interaction between the Samba VFS subsystem and the modules
    Initialization and registration
    How the Modules handle per connection data
    Upgrading to the New VFS Interface
    Upgrading from 2.2.* and 3.0aplha modules
    Some Notes
    Implement TRANSPARENT functions
    Implement OPAQUE functions

    The Samba (Posix) VFS layer

    The general interface

    +

    Chapter 17. VFS Modules

    Alexander Bokovoy

    Stefan Metzmacher

    27 May 2003

    Table of Contents

    The Samba (Posix) VFS layer
    The general interface
    Possible VFS operation layers
    The Interaction between the Samba VFS subsystem and the modules
    Initialization and registration
    How the Modules handle per connection data
    Upgrading to the New VFS Interface
    Upgrading from 2.2.* and 3.0aplha modules
    Some Notes
    Implement TRANSPARENT functions
    Implement OPAQUE functions

    The Samba (Posix) VFS layer

    The general interface

    Each VFS operation has a vfs_op_type, a function pointer and a handle pointer in the struct vfs_ops and tree macros to make it easier to call the operations. (Take a look at include/vfs.h and include/vfs_macros.h.) @@ -2129,7 +2128,7 @@ DO NOT ACCESS conn->vfs.ops.* directly !!! (tofd), (fsp), (fromfd), (header), (offset), (count))) ... -

    Possible VFS operation layers

    +

    Possible VFS operation layers

    These values are used by the VFS subsystem when building the conn->vfs and conn->vfs_opaque structs for a connection with multiple VFS modules. Internally, Samba differentiates only opaque and transparent layers at this process. @@ -2158,7 +2157,7 @@ typedef enum _vfs_op_layer { SMB_VFS_LAYER_SCANNER /* - Checks data and possibly initiates additional */ /* file activity like logging to files _inside_ samba VFS */ } vfs_op_layer; -

    The Interaction between the Samba VFS subsystem and the modules

    Initialization and registration

    +

    The Interaction between the Samba VFS subsystem and the modules

    Initialization and registration

    As each Samba module a VFS module should have a 

    NTSTATUS vfs_example_init(void);

    function if it's staticly linked to samba or 

    NTSTATUS init_module(void);

    function if it's a shared module. @@ -2196,9 +2195,9 @@ static vfs_op_tuple example_op_tuples[] = { NTSTATUS init_module(void) { - return smb_register_vfs(SMB_VFS_INTERFACE_VERSION, "example", example_op_tuples); + return smb_register_vfs(SMB_VFS_INTERFACE_VERSION, "example", example_op_tuples); } -

    How the Modules handle per connection data

    Each VFS function has as first parameter a pointer to the modules vfs_handle_struct. +

    How the Modules handle per connection data

    Each VFS function has as first parameter a pointer to the modules vfs_handle_struct. 

     typedef struct vfs_handle_struct {
 	struct vfs_handle_struct  *next, *prev;
@@ -2208,7 +2207,7 @@ typedef struct vfs_handle_struct {
 	void *data;
 	void (*free_data)(void **data);
 } vfs_handle_struct;
-
    param

    this is the module parameter specified in the vfs objects parameter.

    e.g. for 'vfs objects = example:test' param would be "test".

    vfs_next

    This vfs_ops struct contains the information for calling the next module operations. +

    param

    this is the module parameter specified in the vfs objects parameter.

    e.g. for 'vfs objects = example:test' param would be "test".

    vfs_next

    This vfs_ops struct contains the information for calling the next module operations. Use the SMB_VFS_NEXT_* macros to call a next module operations and don't access handle->vfs_next.ops.* directly!

    conn

    This is a pointer back to the connection_struct to witch the handle belongs.

    data

    This is a pointer for holding module private data. You can alloc data with connection life time on the handle->conn->mem_ctx TALLOC_CTX. @@ -2218,14 +2217,14 @@ you can set this function pointer to NULL.

    Some useful MAC 

     #define SMB_VFS_HANDLE_GET_DATA(handle, datap, type, ret) { \
 	if (!(handle)||((datap=(type *)(handle)->data)==NULL)) { \
-		DEBUG(0,("%s() failed to get vfs_handle->data!\n",FUNCTION_MACRO)); \
+		DEBUG(0,("%s() failed to get vfs_handle->data!\n",FUNCTION_MACRO)); \
 		ret; \
 	} \
 }
 
 #define SMB_VFS_HANDLE_SET_DATA(handle, datap, free_fn, type, ret) { \
 	if (!(handle)) { \
-		DEBUG(0,("%s() failed to set handle->data!\n",FUNCTION_MACRO)); \
+		DEBUG(0,("%s() failed to set handle->data!\n",FUNCTION_MACRO)); \
 		ret; \
 	} else { \
 		if ((handle)->free_data) { \
@@ -2299,20 +2298,20 @@ you can set this function pointer to NULL.

    Some useful MAC (handle)->vfs_next.handles.sendfile,\ (tofd), (fsp), (fromfd), (header), (offset), (count))) ... -

    Upgrading to the New VFS Interface

    Upgrading from 2.2.* and 3.0aplha modules

    1. -Add "vfs_handle_struct *handle, " as first parameter to all vfs operation functions. +

    Upgrading to the New VFS Interface

    Upgrading from 2.2.* and 3.0aplha modules

    1. +Add "vfs_handle_struct *handle, " as first parameter to all vfs operation functions. e.g. example_connect(connection_struct *conn, const char *service, const char *user); -> example_connect(vfs_handle_struct *handle, connection_struct *conn, const char *service, const char *user);

    2. -Replace "default_vfs_ops." with "smb_vfs_next_". +Replace "default_vfs_ops." with "smb_vfs_next_". e.g. default_vfs_ops.connect(conn, service, user); -> smb_vfs_next_connect(conn, service, user);

    3. -Uppercase all "smb_vfs_next_*" functions. +Uppercase all "smb_vfs_next_*" functions. e.g. smb_vfs_next_connect(conn, service, user); -> SMB_VFS_NEXT_CONNECT(conn, service, user);

    4. -Add "handle, " as first parameter to all SMB_VFS_NEXT_*() calls. +Add "handle, " as first parameter to all SMB_VFS_NEXT_*() calls. e.g. SMB_VFS_NEXT_CONNECT(conn, service, user); -> SMB_VFS_NEXT_CONNECT(handle, conn, service, user);

    5. @@ -2412,7 +2411,7 @@ e.g. 

       NTSTATUS init_module(void)
 {
-	return smb_register_vfs(SMB_VFS_INTERFACE_VERSION,"example",example_op_tuples);
+	return smb_register_vfs(SMB_VFS_INTERFACE_VERSION,"example",example_op_tuples);
 }

    6. @@ -2448,14 +2447,14 @@ static int example_connect(vfs_handle_struct *handle, /* alloc our private data */ data = (struct example_privates *)talloc_zero(conn->mem_ctx, sizeof(struct example_privates)); if (!data) { - DEBUG(0,("talloc_zero() failed\n")); + DEBUG(0,("talloc_zero() failed\n")); return -1; } /* init out private data */ - data->some_string = talloc_strdup(conn->mem_ctx,"test"); + data->some_string = talloc_strdup(conn->mem_ctx,"test"); if (!data->some_string) { - DEBUG(0,("talloc_strdup() failed\n")); + DEBUG(0,("talloc_strdup() failed\n")); return -1; } @@ -2481,7 +2480,7 @@ static int example_close(vfs_handle_struct *handle, files_struct *fsp, int fd) SMB_VFS_HANDLE_GET_DATA(handle, data, struct example_privates, return -1); /* do something here...*/ - DEBUG(0,("some_string: %s\n",data->some_string)); + DEBUG(0,("some_string: %s\n",data->some_string)); return SMB_VFS_NEXT_CLOSE(handle, fsp, fd); } @@ -2495,7 +2494,7 @@ static void free_example_privates(void **datap) SAFE_FREE(data->some_string); SAFE_FREE(data); - datap = NULL; + *datap = NULL; return; } @@ -2509,14 +2508,14 @@ static int example_connect(vfs_handle_struct *handle, /* alloc our private data */ data = (struct example_privates *)malloc(sizeof(struct example_privates)); if (!data) { - DEBUG(0,("malloc() failed\n")); + DEBUG(0,("malloc() failed\n")); return -1; } /* init out private data */ - data->some_string = strdup(conn->mem_ctx,"test"); + data->some_string = strdup("test"); if (!data->some_string) { - DEBUG(0,("strdup() failed\n")); + DEBUG(0,("strdup() failed\n")); return -1; } @@ -2526,7 +2525,7 @@ static int example_connect(vfs_handle_struct *handle, * we need to specify a free_function because we used malloc() and strdup(). * (return -1 if something failed.) */ - SMB_VFS_HANDLE_SET_DATA(handle, data, NULL, struct example_privates, return -1); + SMB_VFS_HANDLE_SET_DATA(handle, data, free_example_privates, struct example_privates, return -1); return SMB_VFS_NEXT_CONNECT(handle,conn,service,user); } @@ -2541,7 +2540,7 @@ static int example_close(vfs_handle_struct *handle, files_struct *fsp, int fd) SMB_VFS_HANDLE_GET_DATA(handle, data, struct example_privates, return -1); /* do something here...*/ - DEBUG(0,("some_string: %s\n",data->some_string)); + DEBUG(0,("some_string: %s\n",data->some_string)); return SMB_VFS_NEXT_CLOSE(handle, fsp, fd); } @@ -2562,7 +2561,7 @@ for your module.

    7. Compiling & Testing...

      ./configure --enable-developer ...
      make
      Try to fix all compiler warnings
      make
      Testing, Testing, Testing ...

      -

    Some Notes

    Implement TRANSPARENT functions

    +

    Some Notes

    Implement TRANSPARENT functions

    Avoid writing functions like this: 

    @@ -2573,7 +2572,7 @@ static int example_close(vfs_handle_struct *handle, files_struct *fsp, int fd)

    Overload only the functions you really need to! -

    Implement OPAQUE functions

    +

    Implement OPAQUE functions

    If you want to just implement a better version of a default samba opaque function (e.g. like a disk_free() function for a special filesystem) @@ -2589,16 +2588,16 @@ e.g. for a readonly filesystem. static int example_rename(vfs_handle_struct *handle, connection_struct *conn, char *oldname, char *newname) { - DEBUG(10,("function rename() not allowed on vfs 'example'\n")); + DEBUG(10,("function rename() not allowed on vfs 'example'\n")); errno = ENOSYS; return -1; } -

    Chapter 18. Notes to packagers

    Jelmer Vernooij

    Table of Contents

    Versioning
    Modules

    Versioning

    Please, please update the version number in +

    Chapter 18. Notes to packagers

    Jelmer Vernooij

    Table of Contents

    Versioning
    Modules

    Versioning

    Please, please update the version number in source/include/version.h to include the versioning of your package. This makes it easier to distinguish standard samba builds from custom-build samba builds (distributions often patch packages). For example, a good version would be: 

     Version 2.999+3.0.alpha21-5 for Debian
-

    Modules

    Samba now has support for building parts of samba as plugins. This +

    Modules

    Samba now has support for building parts of samba as plugins. This makes it possible to, for example, put ldap or mysql support in a seperate package, thus making it possible to have a normal samba package not depending on ldap or mysql. To build as much parts of samba diff --git a/docs/htmldocs/Samba-HOWTO-Collection.html b/docs/htmldocs/Samba-HOWTO-Collection.html index 27faf25f17..566f0b4068 100644 --- a/docs/htmldocs/Samba-HOWTO-Collection.html +++ b/docs/htmldocs/Samba-HOWTO-Collection.html @@ -16,20 +16,13 @@ insignificant number of ideas for inclusion (if not content itself) has been obt from a number of Unofficial HOWTOs - to each such author a big "Thank-you" is also offered. Please keep publishing your Unofficial HOWTOs - they are a source of inspiration and application knowledge that is most to be desired by many Samba users and administrators. -">

    SAMBA Project Documentation

    Edited by

    Jelmer R. Vernooij

    John H. Terpstra

    Gerald (Jerry) Carter

    -This documentation is distributed under the GNU General Public License (GPL) -version 2. A copy of the license is included with the Samba source -distribution. A copy can be found on-line at http://www.fsf.org/licenses/gpl.txt -

    Attributions.  -

    Introduction to Samba
    How to Install and Test SAMBA
    Fast Start for the Impatient
    Server Types and Security Modes
    Domain Control
    Backup Domain Control
    Domain Membership
    Stand-Alone Servers
    MS Windows Network Configuration Guide
    Samba / MS Windows Network Browsing Guide
    Account Information Databases
    Mapping MS Windows and Unix Groups
    File, Directory and Share Access Controls
    File and Record Locking
    Securing Samba
    Interdomain Trust Relationships
    Hosting a Microsoft Distributed File System tree on Samba
    Classical Printing Support
    CUPS Printing Support in Samba 3.0
    Stackable VFS modules

    • Jelmer Vernooij <jelmer@samba.org>

    • John Terpstra <jht@samba.org>

    • Tim Potter

    • Simo Sorce (original vfs_skel README)

    • Alexander Bokovoy (original vfs_netatalk docs)

    • Stefan Metzmacher (Update for multiple modules)

    Integrated Logon Support using Winbind
    Advanced Network Management
    System and Account Policies
    Desktop Profile Management
    PAM based Distributed Authentication
    Integrating MS Windows networks with Samba
    Unicode/Charsets
    Samba Backup Techniques
    High Availability Options
    Upgrading from Samba-2.x to Samba-3.0.0
    Migration from NT4 PDC to Samba-3 PDC
    SWAT - The Samba Web Administration Tool
    The Samba checklist
    Analysing and solving samba problems
    Reporting Bugs
    How to compile SAMBA
    Portability
    Samba and other CIFS clients
    Samba Performance Tuning
    DNS and DHCP Configuration Guide
    Further Resources

    - -

    Monday April 21, 2003

    Abstract

    +">

    SAMBA Project Documentation

    Edited by

    Jelmer R. Vernooij

    John H. Terpstra

    Gerald (Jerry) Carter

    Monday April 21, 2003

    Abstract

    This book is a collection of HOWTOs added to Samba documentation over the years. Samba is always under development, and so is its' documentation. This release of the documentation represents a major revision or layout as well as contents. The most recent version of this document can be found at http://www.samba.org/ -on the "Documentation" page. Please send updates to +on the "Documentation" page. Please send updates to Jelmer Vernooij, John H. Terpstra or Gerald (Jerry) Carter. @@ -38,47 +31,53 @@ The Samba-Team would like to express sincere thanks to the many people who have or without their knowledge contributed to this update. The size and scope of this project would not have been possible without significant community contribution. A not insignificant number of ideas for inclusion (if not content itself) has been obtained -from a number of Unofficial HOWTOs - to each such author a big "Thank-you" is also offered. +from a number of Unofficial HOWTOs - to each such author a big "Thank-you" is also offered. Please keep publishing your Unofficial HOWTOs - they are a source of inspiration and application knowledge that is most to be desired by many Samba users and administrators. -

    Table of Contents

    I. General Installation
    1. Introduction to Samba
    Background
    Terminology
    Related Projects
    SMB Methodology
    Epilogue
    Miscellaneous
    2. How to Install and Test SAMBA
    Obtaining and installing samba
    Configuring samba (smb.conf)
    Example Configuration
    SWAT
    Try listing the shares available on your - server
    Try connecting with the unix client
    Try connecting from a DOS, WfWg, Win9x, WinNT, - Win2k, OS/2, etc... client
    What If Things Don't Work?
    Common Errors
    Why are so many smbd processes eating memory?
    I'm getting "open_oplock_ipc: Failed to get local UDP socket for address 100007f. Error was Cannot assign requested" in the logs
    3. Fast Start for the Impatient
    Note
    II. Server Configuration Basics
    4. 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)
    Seamless Windows Network Integration
    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
    5. Domain Control
    Features and Benefits
    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 Problems and Errors
    I cannot include a '$' in a machine name
    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.
    The system can not log you on (C000019B)....
    The machine trust account for this computer either does not -exist or is not accessible.
    When I attempt to login to a Samba Domain from a NT4/W2K workstation, -I get a message about my account being disabled.
    Until a few minutes after Samba has started, clients get the error "Domain Controller Unavailable"
    6. Backup Domain Control
    Features And Benefits
    Essential Background Information
    MS Windows NT4 Style Domain Control
    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, what can I do?
    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?
    7. Domain Membership
    Features and Benefits
    MS Windows Workstation/Server Machine Trust Accounts
    Manual Creation of Machine Trust Accounts
    Using NT4 Server Manager to Add Machine Accounts to the Domain
    "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
    Setup your smb.conf
    Setup your /etc/krb5.conf
    Create the computer account
    Test your server setup
    Testing with smbclient
    Notes
    Common Errors
    Can Not Add Machine Back to Domain
    Adding Machine to Domain Fails
    8. Stand-Alone Servers
    Features and Benefits
    Background
    Example Configuration
    Reference Documentation Server
    Central Print Serving
    Common Errors
    9. MS Windows Network Configuration Guide
    Note
    III. Advanced Configuration
    10. Samba / MS Windows Network Browsing Guide
    Features and Benefits
    What is Browsing?
    Discussion
    NetBIOS over TCP/IP
    TCP/IP - without NetBIOS
    DNS and Active Directory
    How Browsing Functions
    Setting up WORKGROUP Browsing
    Setting up DOMAIN Browsing
    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
    Setting up a WINS server
    WINS Replication
    Static WINS Entries
    Helpful Hints
    Windows Networking Protocols
    Name Resolution Order
    Technical Overview of browsing
    Browsing support in Samba
    Problem resolution
    Browsing across subnets
    Common Errors
    How can one flush the Samba NetBIOS name cache without restarting Samba?
    My client reports "This server is not configured to list shared resources"
    11. Account Information Databases
    Features and Benefits
    Technical Information
    Important Notes About Security
    Mapping User Identifiers between MS Windows and Unix
    Account Management Tools
    The smbpasswd Command
    The pdbedit Command
    Password Backends
    Plain Text
    smbpasswd - Encrypted Password Database
    tdbsam
    ldapsam
    MySQL
    XML
    Common Errors
    Users can not logon - Users not in Samba SAM
    Users are being added to the wrong backend database
    auth methods does not work
    12. Mapping MS Windows and Unix Groups
    Features and Benefits
    Discussion
    Example Configuration
    Configuration Scripts
    Sample smb.conf add group script
    Script to configure Group Mapping
    Common Errors
    Adding Groups Fails
    Adding MS Windows Groups to MS Windows Groups Fails
    13. 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
    Common Errors
    Users can not write to a public share
    I have set force user and Samba still makes root the owner of all the files - I touch!
    14. File and Record Locking
    Features and Benefits
    Discussion
    Opportunistic Locking Overview
    Samba Opportunistic Locking Control
    Example Configuration
    MS Windows Opportunistic Locking and Caching Controls
    Workstation Service Entries
    Server Service Entries
    Persistent Data Corruption
    Common Errors
    locking.tdb error messages
    Additional Reading
    15. 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 a IPC$ share deny
    NTLMv2 Security
    Upgrading Samba
    Common Errors
    Smbclient works on localhost, but the network is dead
    Why can users access home directories of other users?
    16. Interdomain Trust Relationships
    Features and Benefits
    Trust Relationship Background
    Native MS Windows NT4 Trusts Configuration
    NT4 as the Trusting Domain (ie. creating the trusted account)
    NT4 as the Trusted Domain (ie. creating trusted account's password)
    Configuring Samba NT-style Domain Trusts
    Samba-3 as the Trusting Domain
    Samba-3 as the Trusted Domain
    Common Errors
    Tell me about Trust Relationships using Samba
    17. Hosting a Microsoft Distributed File System tree on Samba
    Features and Benefits
    Common Errors
    18. Classical Printing Support
    Features and Benefits
    Technical Introduction
    What happens if you send a Job from a Client
    Printing Related Configuration Parameters
    Parameters Recommended for Use
    Parameters for Backwards Compatibility
    Parameters no longer in use
    A simple Configuration to Print with Samba-3
    Verification of "Settings in Use" with testparm
    A little Experiment to warn you
    Extended Sample Configuration to Print with Samba-3
    Detailed Explanation of the Example's Settings
    The [global] Section
    The [printers] Section
    Any [my_printer_name] Section
    Print Commands
    Default Print Commands for various Unix Print Subsystems
    Setting up your own Print Commands
    Innovations in Samba Printing since 2.2
    Client Drivers on Samba Server for Point'n'Print
    The [printer$] Section is removed from Samba-3
    Creating the [print$] Share
    Parameters in the [print$] Section
    Subdirectory Structure in [print$]
    Installing Drivers into [print$]
    Setting Drivers for existing Printers with a Client GUI
    Setting Drivers for existing Printers with -rpcclient
    "The Proof of the Pudding lies in the Eating" (Client Driver Install -Procedure)
    The first Client Driver Installation
    IMPORTANT! Setting Device Modes on new Printers
    Further Client Driver Install Procedures
    Always make first Client Connection as root or "printer admin"
    Other Gotchas
    Setting Default Print Options for the Client Drivers
    Supporting large Numbers of Printers
    Adding new Printers with the Windows NT APW
    Weird Error Message Cannot connect under a -different Name
    Be careful when assembling Driver Files
    Samba and Printer Ports
    Avoiding the most common Misconfigurations of the Client Driver
    The Imprints Toolset
    What is Imprints?
    Creating Printer Driver Packages
    The Imprints Server
    The Installation Client
    Add Network Printers at Logon without User Interaction
    The addprinter command
    Migration of "Classical" printing to Samba-3
    Publishing Printer Information in Active Directory or LDAP
    Common Errors and Problems
    I give my root password but I don't get access
    My printjobs get spooled into the spooling directory, but then get lost
    19. CUPS Printing Support in Samba 3.0
    Introduction
    Features and Benefits
    Overview
    Basic Configuration of CUPS support
    Linking of smbd with libcups.so
    Simple smb.conf Settings for CUPS
    More complex smb.conf Settings for -CUPS
    Advanced Configuration
    Central spooling vs. "Peer-to-Peer" printing
    CUPS/Samba as a "spooling-only" Print Server; "raw" printing -with Vendor Drivers on Windows Clients
    Driver Installation Methods on Windows Clients
    Explicitly enable "raw" printing for -application/octet-stream!
    Three familiar Methods for driver upload plus a new one
    Using CUPS/Samba in an advanced Way -- 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
    CUPS can use all 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
    Filter Requirements
    Prefilters
    pstops
    pstoraster
    imagetops and imagetoraster
    rasterto [printers specific]
    CUPS Backends
    cupsomatic/Foomatic -- how do they fit into the Picture?
    The Complete Picture
    mime.convs
    "Raw" printing
    "application/octet-stream" printing
    PostScript Printer Descriptions (PPDs) for non-PS Printers
    Difference between cupsomatic/foomatic-rip and -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 -- UNIX/Samba Print -Servers)
    From Windows Clients to a CUPS/Samba Print Server
    Samba receiving Jobfiles and passing them to CUPS
    Network PostScript RIP: CUPS Filters on Server -- clients use -PostScript Driver with CUPS-PPDs
    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
    Setting up CUPS for driver Download
    cupsaddsmb: the unknown Utility
    Prepare your smb.conf for -cupsaddsmb
    CUPS Package of "PostScript Driver for WinNT/2k/XP"
    Recognize the different Driver Files
    Acquiring the Adobe Driver Files
    ESP Print Pro Package of "PostScript Driver for -WinNT/2k/XP"
    Caveats to be considered
    What are the Benefits of using the "CUPS PostScript Driver for -Windows NT/2k/XP" as compared to the Adobe Driver?
    Run "cupsaddsmb" (quiet Mode)
    Run "cupsaddsmb" with verbose Output
    Understanding cupsaddsmb
    How to recognize if cupsaddsm 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
    What is required for adddriver and setdriver to succeed
    Manual Commandline Driver Installation in 15 little 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
    Auto-Deletion or Preservation of CUPS Spool Files
    CUPS Configuration Settings explained
    Pre-conditions
    Manual Configuration
    When not to use Samba to print to -CUPS
    In Case of Trouble.....
    Where to find Documentation
    How to ask for Help
    Where to find Help
    Appendix
    Printing from CUPS to Windows attached -Printers
    More CUPS filtering Chains
    Trouble Shooting Guidelines to fix typical Samba printing -Problems
    An Overview of the CUPS Printing Processes
    20. Stackable VFS modules
    Features and Benefits
    Discussion
    Included modules
    audit
    extd_audit
    fake_perms
    recycle
    netatalk
    VFS modules available elsewhere
    DatabaseFS
    vscan
    Common Errors
    21. Integrated Logon Support using Winbind
    Features and Benefits
    Introduction
    What Winbind Provides
    Target Uses
    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
    22. Advanced Network Management
    Features and Benefits
    Remote Server Administration
    Remote Desktop Management
    Remote Management from NoMachines.Com
    Network Logon Script Magic
    Adding printers without user intervention
    Common Errors
    23. 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
    Samba Editreg Toolset
    Windows NT4/200x
    Samba PDC
    System Startup and Logon Processing Overview
    Common Errors
    Policy Does Not Work
    24. Desktop Profile Management
    Features and Benefits
    Roaming Profiles
    Samba Configuration for Profile Handling
    Windows Client Profile Configuration Information
    Sharing Profiles between W9x/Me and NT4/200x/XP workstations
    Profile Migration from Windows NT4/200x Server to Samba
    Mandatory profiles
    Creating/Managing Group Profiles
    Default Profile for Windows Users
    MS Windows 9x/Me
    MS Windows NT4 Workstation
    MS Windows 200x/XP
    Common Errors
    How does one set up roaming profiles for just one (or a few) user/s or group/s?
    Can NOT use Roaming Profiles
    Changing the default profile
    25. 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
    26. 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
    My Boomerang Won't Come Back
    Very Slow Network Connections
    Samba server name change problem
    27. Unicode/Charsets
    Features and Benefits
    What are charsets and unicode?
    Samba and charsets
    Conversion from old names
    Japanese charsets
    28. Samba Backup Techniques
    Note
    Features and Benefits
    29. High Availability Options
    Note
    IV. Migration and Updating
    30. Upgrading from Samba-2.x to Samba-3.0.0
    Charsets
    Obsolete configuration options
    Password Backend
    31. Migration from NT4 PDC to Samba-3 PDC
    Planning and Getting Started
    Objectives
    Steps In Migration Process
    Migration Options
    Planning for Success
    Samba Implementation Choices
    32. SWAT - The Samba Web Administration Tool
    Features and Benefits
    Enabling SWAT for use
    Securing SWAT through SSL
    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
    33. The Samba checklist
    Introduction
    Assumptions
    The tests
    Still having troubles?
    34. Analysing and solving samba problems
    Diagnostics tools
    Installing 'Network Monitor' on an NT Workstation or a Windows 9x box
    Useful URLs
    Getting help from the mailing lists
    How to get off the mailing lists
    35. Reporting Bugs
    Introduction
    General info
    Debug levels
    Internal errors
    Attaching to a running process
    Patches
    VI. Appendixes
    36. How to compile SAMBA
    Access Samba source code via CVS
    Introduction
    CVS 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 and nmbd
    Starting from inetd.conf
    Alternative: starting it as a daemon
    Common Errors
    37. Portability
    HPUX
    SCO Unix
    DNIX
    RedHat Linux Rembrandt-II
    AIX
    Sequential Read Ahead
    Solaris
    Locking improvements
    Winbind on Solaris 9
    38. Samba and other CIFS clients
    Macintosh clients?
    OS2 Client
    How can I configure OS/2 Warp Connect or - OS/2 Warp 4 as a client for Samba?
    How can I configure OS/2 Warp 3 (not Connect), - OS/2 1.2, 1.3 or 2.x for Samba?
    How do I get printer driver download working - for OS/2 clients?
    Windows for Workgroups
    Use latest TCP/IP stack from Microsoft
    Delete .pwl files after password change
    Configure WfW password handling
    Case handling of passwords
    Use TCP/IP as default protocol
    Speed improvement
    Windows '95/'98
    Speed improvement
    Windows 2000 Service Pack 2
    Windows NT 3.1
    39. Samba Performance Tuning
    Comparisons
    Socket options
    Read size
    Max xmit
    Log level
    Read raw
    Write raw
    Slow Logins
    Client tuning
    Samba performance problem due changing kernel
    Corrupt tdb Files
    40. DNS and DHCP Configuration Guide
    Note
    41. Further Resources
    Websites
    Related updates from Microsoft
    Books
    Index

    List of Figures

    19.1. Windows Printing to a local Printer
    19.2. Printing to a Postscript Printer
    19.3. Ghostscript as a RIP for non-postscript printers
    19.4. Prefiltering in CUPS to form Postscript
    19.5. Adding Device-specific Print Options
    19.6. Postscript to intermediate Raster format
    19.7. CUPS-raster production using Ghostscript
    19.8. Image format to CUPS-raster format conversion
    19.9. Raster to Printer Specific formats
    19.10. cupsomatic/foomatic processing versus Native CUPS
    19.11. Print Driver execution on the Client
    19.12. Print Driver execution on the Server
    19.13. Printing via CUPS/samba server
    19.14. cupsaddsmb flowchart
    19.15. CUPS Printing Overview

    List of Tables

    7.1. Assumptions
    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. Attributes in the sambaSamAccount objectclass (LDAP)
    11.2. Basic smb.conf options for MySQL passdb backend
    11.3. MySQL field names for MySQL passdb backend
    13.1. Managing directories with unix and windows
    13.2. User and Group Based Controls
    13.3. File and Directory Permission Based Controls
    13.4. Other Controls
    20.1. Extended Auditing Log Information
    24.1. User Shell Folder registry keys default values
    24.2. Defaults of profile settings registry keys
    24.3. Defaults of default user profile paths registry keys
    25.1. Options recognized by pam_smbpass
    31.1. The 3 Major Site Types
    31.2. Nature of the Conversion Choices

    List of Examples

    12.1. smbgrpadd.sh
    13.1. Example File

    General Installation

    Preparing Samba for Configuration

    This section of the Samba-HOWTO-Collection contains general info on how to install samba +

    Table of Contents

    Legal Notice
    Attributions
    I. General Installation
    1. Introduction to Samba
    Background
    Terminology
    Related Projects
    SMB Methodology
    Epilogue
    Miscellaneous
    2. How to Install and Test SAMBA
    Obtaining and installing samba
    Configuring samba (smb.conf)
    Example Configuration
    SWAT
    Try listing the shares available on your + server
    Try connecting with the unix client
    Try connecting from another SMB client
    What If Things Don't Work?
    Common Errors
    Large number of smbd processes
    "open_oplock_ipc: Failed to get local UDP socket for address 100007f. Error was Cannot assign requested"
    "The network name cannot be found"
    3. Fast Start for the Impatient
    Note
    II. Server Configuration Basics
    4. 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
    5. Domain Control
    Features and Benefits
    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 can not log you on (C000019B)....
    The machine trust account not accessible
    Account disabled
    Domain Controller Unavailable
    Can not log onto domain member workstation after joining domain
    6. Backup Domain Control
    Features And Benefits
    Essential Background Information
    MS Windows NT4 Style Domain Control
    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, what can I do?
    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?
    7. Domain Membership
    Features and Benefits
    MS Windows Workstation/Server Machine Trust Accounts
    Manual Creation of Machine Trust Accounts
    Using NT4 Server Manager to Add Machine Accounts to the Domain
    "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
    Setup your smb.conf
    Setup your /etc/krb5.conf
    Create the computer account
    Test your server setup
    Testing with smbclient
    Notes
    Common Errors
    Can Not Add Machine Back to Domain
    Adding Machine to Domain Fails
    8. Stand-Alone Servers
    Features and Benefits
    Background
    Example Configuration
    Reference Documentation Server
    Central Print Serving
    Common Errors
    9. MS Windows Network Configuration Guide
    Note
    III. Advanced Configuration
    10. Samba / MS Windows Network Browsing Guide
    Features and Benefits
    What is Browsing?
    Discussion
    NetBIOS over TCP/IP
    TCP/IP - without NetBIOS
    DNS and Active Directory
    How Browsing Functions
    Setting up WORKGROUP Browsing
    Setting up DOMAIN Browsing
    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
    Setting up a WINS server
    WINS Replication
    Static WINS Entries
    Helpful Hints
    Windows Networking Protocols
    Name Resolution Order
    Technical Overview of browsing
    Browsing support in Samba
    Problem resolution
    Browsing across subnets
    Common Errors
    How can one flush the Samba NetBIOS name cache without restarting Samba?
    My client reports "This server is not configured to list shared resources"
    I get an Unable to browse the network error
    11. Account Information Databases
    Features and Benefits
    Backwards Compatibility Backends
    New Backends
    Technical Information
    Important Notes About Security
    Mapping User Identifiers between MS Windows and UNIX
    Mapping Common UIDs/GIDs on Distributed Machines
    Account Management Tools
    The smbpasswd Command
    The pdbedit Command
    Password Backends
    Plain Text
    smbpasswd - Encrypted Password Database
    tdbsam
    ldapsam
    MySQL
    XML
    Common Errors
    Users can not logon
    Users being added to wrong backend database
    auth methods does not work
    12. Mapping MS Windows and UNIX Groups
    Features and Benefits
    Discussion
    Example Configuration
    Configuration Scripts
    Sample smb.conf add group script
    Script to configure Group Mapping
    Common Errors
    Adding Groups Fails
    Adding MS Windows Groups to MS Windows Groups Fails
    Adding Domain Users to the Power Users group
    13. 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
    Common Errors
    Users can not write to a public share
    I have set force user but Samba still makes root the owner of all the files I touch!
    MS Word with Samba changes owner of file
    14. File and Record Locking
    Features and Benefits
    Discussion
    Opportunistic Locking Overview
    Samba Opportunistic Locking Control
    Example Configuration
    MS Windows Opportunistic Locking 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
    15. 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 a IPC$ share deny
    NTLMv2 Security
    Upgrading Samba
    Common Errors
    Smbclient works on localhost, but the network is dead
    Why can users access home directories of other users?
    16. 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
    Inter-Domain 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
    17. Hosting a Microsoft Distributed File System tree on Samba
    Features and Benefits
    Common Errors
    18. Classical Printing Support
    Features and Benefits
    Technical Introduction
    What happens if you send a Job from a Client
    Printing Related Configuration Parameters
    Parameters Recommended for Use
    A simple Configuration to Print
    Verification of "Settings in Use" with testparm
    A little Experiment to warn you
    Extended Sample Configuration to Print
    Detailed Explanation of the Example's Settings
    The [global] Section
    The [printers] Section
    Any [my_printer_name] Section
    Print Commands
    Default Print Commands for various UNIX Print Subsystems
    Setting up your own Print Commands
    Innovations in Samba Printing since 2.2
    Client Drivers on Samba Server for Point'n'Print
    The [printer$] Section is removed from Samba 3
    Creating the [print$] Share
    Parameters in the [print$] Section
    Subdirectory Structure in [print$]
    Installing Drivers into [print$]
    Setting Drivers for existing Printers with a Client GUI
    Setting Drivers for existing Printers with +rpcclient
    Client Driver Install Procedure
    The first Client Driver Installation
    IMPORTANT! Setting Device Modes on new Printers
    Further Client Driver Install Procedures
    Always make first Client Connection as root or "printer admin"
    Other Gotchas
    Setting Default Print Options for the Client Drivers
    Supporting large Numbers of Printers
    Adding new Printers with the Windows NT APW
    Weird Error Message Cannot connect under a +different Name
    Be careful when assembling Driver Files
    Samba and Printer Ports
    Avoiding the most common Misconfigurations of the Client Driver
    The Imprints Toolset
    What is Imprints?
    Creating Printer Driver Packages
    The Imprints Server
    The Installation Client
    Add Network Printers at Logon 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 don't get access
    My printjobs get spooled into the spooling directory, but then get lost
    19. CUPS Printing Support in Samba 3.0
    Introduction
    Features and Benefits
    Overview
    Basic Configuration of CUPS support
    Linking of smbd with libcups.so
    Simple smb.conf Settings for CUPS
    More complex smb.conf Settings for +CUPS
    Advanced Configuration
    Central spooling vs. "Peer-to-Peer" printing
    CUPS/Samba as a "spooling-only" Print Server; "raw" printing +with Vendor Drivers on Windows Clients
    Driver Installation Methods on Windows Clients
    Explicitly enable "raw" printing for +application/octet-stream!
    Three familiar Methods for driver upload plus a new one
    Using CUPS/Samba in an advanced Way -- 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
    CUPS can use all 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
    Filter Requirements
    Prefilters
    pstops
    pstoraster
    imagetops and imagetoraster
    rasterto [printers specific]
    CUPS Backends
    cupsomatic/Foomatic -- how do they fit into the Picture?
    The Complete Picture
    mime.convs
    "Raw" printing
    "application/octet-stream" printing
    PostScript Printer Descriptions (PPDs) for non-PS Printers
    Difference between cupsomatic/foomatic-rip and +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 -- UNIX/Samba Print +Servers)
    From Windows Clients to a CUPS/Samba Print Server
    Samba receiving Jobfiles and passing them to CUPS
    Network PostScript RIP: CUPS Filters on Server -- clients use +PostScript Driver with CUPS-PPDs
    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
    Setting up CUPS for driver Download
    cupsaddsmb: the unknown Utility
    Prepare your smb.conf for cupsaddsmb
    CUPS Package of "PostScript Driver for WinNT/2k/XP"
    Recognize the different Driver Files
    Acquiring the Adobe Driver Files
    ESP Print Pro Package of "PostScript Driver for +WinNT/2k/XP"
    Caveats to be considered
    Benefits of using "CUPS PostScript Driver for +Windows NT/2k/XP" instead of 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
    What is required 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
    Auto-Deletion or Preservation of CUPS Spool Files
    CUPS Configuration Settings explained
    Pre-conditions
    Manual Configuration
    In Case of Trouble.....
    Printing from CUPS to Windows attached +Printers
    More CUPS filtering Chains
    Common Errors
    Win9x client can't install driver
    "cupsaddsmb" keeps asking for root password in + neverending loop
    "cupsaddsmb" gives "No PPD file for printer..." + message while PPD file is present
    Client can't connect to Samba printer
    Can't reconnect to Samba under new account + from Win2K/XP
    Avoid being connected to the Samba server as the + "wrong" user
    Upgrading to CUPS drivers from Adobe drivers on + NT/2K/XP clients gives problems
    Can't use "cupsaddsmb" on Samba server which is + a PDC
    Deleted Win2K printer driver is still shown
    Win2K/XP "Local Security + Policies"
    WinXP clients: "Administrator can not install + printers for all local users"
    "Print Change Notify" functions on + NT-clients
    WinXP-SP1
    Print options for all users can't be set on Win2K/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
    Printer named "lp" +intermittently swallows jobs and spits out completely different +ones
    Location of Adobe PostScript driver files necessary for "cupsaddsmb"
    An Overview of the CUPS Printing Processes
    20. Stackable VFS modules
    Features and Benefits
    Discussion
    Included modules
    audit
    extd_audit
    fake_perms
    recycle
    netatalk
    VFS modules available elsewhere
    DatabaseFS
    vscan
    21. Winbind: Use of Domain Accounts
    Features and Benefits
    Introduction
    What Winbind Provides
    Target Uses
    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
    22. Advanced Network Management
    Features and Benefits
    Remote Server Administration
    Remote Desktop Management
    Remote Management from NoMachines.Com
    Network Logon Script Magic
    Adding printers without user intervention
    Common Errors
    23. 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
    Samba Editreg Toolset
    Windows NT4/200x
    Samba PDC
    System Startup and Logon Processing Overview
    Common Errors
    Policy Does Not Work
    24. Desktop Profile Management
    Features and Benefits
    Roaming Profiles
    Samba Configuration for Profile Handling
    Windows Client Profile Configuration Information
    Sharing Profiles between W9x/Me and NT4/200x/XP workstations
    Profile Migration from Windows NT4/200x Server to Samba
    Mandatory profiles
    Creating/Managing Group Profiles
    Default Profile for Windows Users
    MS Windows 9x/Me
    MS Windows NT4 Workstation
    MS Windows 200x/XP
    Common Errors
    Setting up roaming profiles for just a few user's or group's?
    Can NOT use Roaming Profiles
    Changing the default profile
    25. 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
    26. 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 in one way
    Very Slow Network Connections
    Samba server name change problem
    27. Unicode/Charsets
    Features and Benefits
    What are charsets and unicode?
    Samba and charsets
    Conversion from old names
    Japanese charsets
    Common errors
    CP850.so can't be found
    28. Samba Backup Techniques
    Note
    Features and Benefits
    29. High Availability Options
    Note
    IV. Migration and Updating
    30. Upgrading from Samba-2.x to Samba-3.0.0
    New Features in Samba-3
    Configuration Parameter Changes
    Removed Parameters
    New Parameters
    Modified Parameters (changes in behavior):
    New Functionality
    Databases
    Changes in Behavior
    Charsets
    Passdb Backends and Authentication
    Charsets
    LDAP
    31. 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
    32. SWAT - The Samba Web Administration Tool
    Features and Benefits
    Enabling SWAT for use
    Securing SWAT through SSL
    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
    33. The Samba checklist
    Introduction
    Assumptions
    The tests
    34. Analysing and solving samba problems
    Diagnostics tools
    Debugging with Samba itself
    Tcpdump
    Ethereal
    The Windows Network Monitor
    Useful URLs
    Getting help from the mailing lists
    How to get off the mailing lists
    35. Reporting Bugs
    Introduction
    General info
    Debug levels
    Internal errors
    Attaching to a running process
    Patches
    VI. Appendixes
    36. How to compile Samba
    Access Samba source code via CVS
    Introduction
    CVS 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 and nmbd
    Starting from inetd.conf
    Alternative: starting it as a daemon
    37. Portability
    HPUX
    SCO UNIX
    DNIX
    RedHat Linux Rembrandt-II
    AIX
    Sequential Read Ahead
    Solaris
    Locking improvements
    Winbind on Solaris 9
    38. Samba and other CIFS clients
    Macintosh clients?
    OS2 Client
    Configuring OS/2 Warp Connect or + OS/2 Warp 4 as a client for Samba
    Configuring OS/2 Warp 3 (not Connect), + OS/2 1.2, 1.3 or 2.x for Samba
    Printer driver download for for OS/2 clients?
    Windows for Workgroups
    Latest TCP/IP stack from Microsoft
    Delete .pwl files after password change
    Configuring WfW password handling
    Case handling of passwords
    Use TCP/IP as default protocol
    Speed improvement
    Windows '95/'98
    Speed improvement
    Windows 2000 Service Pack 2
    Windows NT 3.1
    39. Samba Performance Tuning
    Comparisons
    Socket options
    Read size
    Max xmit
    Log level
    Read raw
    Write raw
    Slow Logins
    Client tuning
    Samba performance problem due changing kernel
    Corrupt tdb Files
    40. DNS and DHCP Configuration Guide
    Note
    41. Further Resources
    Websites
    Related updates from Microsoft
    Index

    List of Figures

    5.1. An Example Domain
    10.1. Cross subnet browsing example
    11.1. IDMAP
    12.1. IDMAP groups
    13.1. Overview of unix permissions field
    16.1. Trusts overview
    19.1. Windows Printing to a local Printer
    19.2. Printing to a Postscript Printer
    19.3. Ghostscript as a RIP for non-postscript printers
    19.4. Prefiltering in CUPS to form Postscript
    19.5. Adding Device-specific Print Options
    19.6. Postscript to intermediate Raster format
    19.7. CUPS-raster production using Ghostscript
    19.8. Image format to CUPS-raster format conversion
    19.9. Raster to Printer Specific formats
    19.10. cupsomatic/foomatic processing versus Native CUPS
    19.11. PDF to socket chain
    19.12. PDF to USB chain
    19.13. Print Driver execution on the Client
    19.14. Print Driver execution on the Server
    19.15. Printing via CUPS/samba server
    19.16. cupsaddsmb flowchart
    19.17. Filtering chain 1
    19.18. Filtering chain with cupsomatic
    19.19. CUPS Printing Overview

    List of Tables

    7.1. Assumptions
    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. Attributes in the sambaSamAccount objectclass (LDAP)
    11.2. Basic smb.conf options for MySQL passdb backend
    11.3. MySQL field names for MySQL passdb backend
    13.1. Managing directories with unix and windows
    13.2. User and Group Based Controls
    13.3. File and Directory Permission Based Controls
    13.4. Other Controls
    19.1. PPD's shipped with CUPS
    20.1. Extended Auditing Log Information
    24.1. User Shell Folder registry keys default values
    24.2. Defaults of profile settings registry keys
    24.3. Defaults of default user profile paths registry keys
    25.1. Options recognized by pam_smbpass
    26.1. Unique NetBIOS names
    26.2. Group Names
    30.1. TDB File Descriptions
    31.1. The 3 Major Site Types
    31.2. Nature of the Conversion Choices

    List of Examples

    2.1. Simplest possible smb.conf file
    5.1. smb.conf for being a PDC
    5.2. smb.conf for being a PDC
    6.1. Minimal smb.conf for being a PDC
    6.2. Minimal setup for being a BDC
    8.1. smb.conf for Reference Documentation Server
    8.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.
    11.2. Configuration with LDAP
    12.1. smbgrpadd.sh
    13.1. Example File
    14.1. Share with some files oplocked
    14.2.
    17.1. smb.conf with DFS configured
    18.1. Simple configuration with BSD printing
    18.2. Extended configuration with BSD printing
    18.3. [print\$] example
    19.1. Simplest printing-related smb.conf
    19.2. Overriding global CUPS settings for one printer
    19.3. smb.conf for cupsaddsmb usage
    20.1. smb.conf with VFS modules
    20.2. smb.conf with multiple VFS modules
    21.1. smb.conf for winbind set-up
    33.1. smb.conf with [tmp] share
    38.1. Minimal profile share

    Legal Notice

    +This documentation is distributed under the GNU General Public License (GPL) +version 2. A copy of the license is included with the Samba source +distribution. A copy can be found on-line at http://www.fsf.org/licenses/gpl.txt +

    Attributions

    Introduction to Samba

    How to Install and Test SAMBA

    Fast Start for the Impatient

    Server Types and Security Modes

    Domain Control

    Backup Domain Control

    Domain Membership

    Stand-Alone Servers

    MS Windows Network Configuration Guide

    Samba / MS Windows Network Browsing Guide

    Account Information Databases

    Mapping MS Windows and UNIX Groups

    File, Directory and Share Access Controls

    File and Record Locking

    Securing Samba

    Interdomain Trust Relationships

    Hosting a Microsoft Distributed File System tree on Samba

    Classical Printing Support

    CUPS Printing Support in Samba 3.0

    Stackable VFS modules

    • Jelmer R. Vernooij <jelmer@samba.org>

    • John H. Terpstra <jht@samba.org>

    • Tim Potter

    • Simo Sorce (original vfs_skel README)

    • Alexander Bokovoy (original vfs_netatalk docs)

    • Stefan Metzmacher (Update for multiple modules)

    Advanced Network Management

    System and Account Policies

    Desktop Profile Management

    PAM based Distributed Authentication

    Integrating MS Windows networks with Samba

    Unicode/Charsets

    Samba Backup Techniques

    High Availability Options

    Upgrading from Samba-2.x to Samba-3.0.0

    Migration from NT4 PDC to Samba-3 PDC

    SWAT - The Samba Web Administration Tool

    The Samba checklist

    Analysing and solving samba problems

    Reporting Bugs

    How to compile Samba

    Portability

    Samba and other CIFS clients

    Samba Performance Tuning

    DNS and DHCP Configuration Guide

    Further Resources

    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. Introduction to Samba
    Background
    Terminology
    Related Projects
    SMB Methodology
    Epilogue
    Miscellaneous
    2. How to Install and Test SAMBA
    Obtaining and installing samba
    Configuring samba (smb.conf)
    Example Configuration
    SWAT
    Try listing the shares available on your - server
    Try connecting with the unix client
    Try connecting from a DOS, WfWg, Win9x, WinNT, - Win2k, OS/2, etc... client
    What If Things Don't Work?
    Common Errors
    Why are so many smbd processes eating memory?
    I'm getting "open_oplock_ipc: Failed to get local UDP socket for address 100007f. Error was Cannot assign requested" in the logs
    3. Fast Start for the Impatient
    Note

    Chapter 1. Introduction to Samba

    David Lechnyr

    Unofficial HOWTO

    April 14, 2003

    Table of Contents

    Background
    Terminology
    Related Projects
    SMB Methodology
    Epilogue
    Miscellaneous

    “ -"If you understand what you're doing, you're not learning anything." +PLEASE read this.

    Table of Contents

    1. Introduction to Samba
    Background
    Terminology
    Related Projects
    SMB Methodology
    Epilogue
    Miscellaneous
    2. How to Install and Test SAMBA
    Obtaining and installing samba
    Configuring samba (smb.conf)
    Example Configuration
    SWAT
    Try listing the shares available on your + server
    Try connecting with the unix client
    Try connecting from another SMB client
    What If Things Don't Work?
    Common Errors
    Large number of smbd processes
    "open_oplock_ipc: Failed to get local UDP socket for address 100007f. Error was Cannot assign requested"
    "The network name cannot be found"
    3. Fast Start for the Impatient
    Note

    Chapter 1. Introduction to Samba

    David Lechnyr

    Unofficial HOWTO

    April 14, 2003

    Table of Contents

    Background
    Terminology
    Related Projects
    SMB Methodology
    Epilogue
    Miscellaneous

    “ +"If you understand what you're doing, you're not learning anything." -- Anonymous ”

    Samba is a file and print server for Windows-based clients using TCP/IP as the underlying @@ -86,7 +85,7 @@ transport protocol. In fact, it can support any SMB/CIFS-enabled client. One of strengths is that you can use it to blend your mix of Windows and Linux machines together without requiring a separate Windows NT/2000/2003 Server. Samba is actively being developed by a global team of about 30 active programmers and was originally developed by Andrew Tridgell. -

    Background

    +

    Background

    Once long ago, there was a buzzword referred to as DCE/RPC. This stood for Distributed Computing Environment/Remote Procedure Calls and conceptually was a good idea. It was originally developed by Apollo/HP as NCA 1.0 (Network Computing Architecture) and only @@ -94,12 +93,12 @@ ran over UDP. When there was a need to run it over TCP so that it would be compa with DECnet 3.0, it was redesigned, submitted to The Open Group, and officially became known as DCE/RPC. Microsoft came along and decided, rather than pay $20 per seat to license this technology, to reimplement DCE/RPC themselves as MSRPC. From this, the -concept continued in the form of SMB (Server Message Block, or the "what") using the -NetBIOS (Network Basic Input/Output System, or the "how") compatibility layer. You can +concept continued in the form of SMB (Server Message Block, or the "what") using the +NetBIOS (Network Basic Input/Output System, or the "how") compatibility layer. You can run SMB (i.e., transport) over several different protocols; many different implementations arose as a result, including NBIPX (NetBIOS over IPX, NwLnkNb, or NWNBLink) and NBT (NetBIOS over TCP/IP, or NetBT). As the years passed, NBT became the most common form -of implementation until the advance of "Direct-Hosted TCP" -- the Microsoft marketing +of implementation until the advance of "Direct-Hosted TCP" -- the Microsoft marketing term for eliminating NetBIOS entirely and running SMB by itself across TCP port 445 only. As of yet, direct-hosted TCP has yet to catch on.

    @@ -112,23 +111,23 @@ been dutifully waded through during the information-gathering stages of this pro are *still* many missing pieces... While often tedious, at least the way has been generously littered with occurrences of clapping hand to forehead and muttering 'crikey, what are they thinking? -

    Terminology

    • - SMB: Acronym for "Server Message Block". This is Microsoft's file and printer sharing protocol. +

    Terminology

    • + SMB: Acronym for "Server Message Block". This is Microsoft's file and printer sharing protocol.

    • - CIFS: Acronym for "Common Internet File System". Around 1996, Microsoft apparently - decided that SMB needed the word "Internet" in it, so they changed it to CIFS. + CIFS: Acronym for "Common Internet File System". Around 1996, Microsoft apparently + decided that SMB needed the word "Internet" in it, so they changed it to CIFS.

    • Direct-Hosted: A method of providing file/printer sharing services over port 445/tcp only using DNS for name resolution instead of WINS.

    • - IPC: Acronym for "Inter-Process Communication". A method to communicate specific + IPC: Acronym for "Inter-Process Communication". A method to communicate specific information between programs.

    • Marshalling: - A method of serializing (i.e., sequential ordering of) variable data suitable for transmission via a network connection or storing in a file. The source data can be re-created using a similar process called unmarshalling.

    • - NetBIOS: Acronym for "Network Basic Input/Output System". This is not a protocol; + NetBIOS: Acronym for "Network Basic Input/Output System". This is not a protocol; it is a method of communication across an existing protocol. This is a standard which was originally developed for IBM by Sytek in 1983. To exaggerate the analogy a bit, it can help to think of this in comparison your computer's BIOS -- it controls the @@ -139,15 +138,15 @@ thinking? brilliant people tend to interchange NetBIOS with terms like NetBEUI without a second thought; this will cause no end (and no doubt) of confusion.

    • - NetBEUI: Acronym for the "NetBIOS Extended User Interface". Unlike NetBIOS, NetBEUI + NetBEUI: Acronym for the "NetBIOS Extended User Interface". Unlike NetBIOS, NetBEUI is a protocol, not a standard. It is also not routable, so traffic on one side of a router will be unable to communicate with the other side. Understanding NetBEUI is not essential to deciphering SMB; however it helps to point out that it is not the same as NetBIOS and to improve your score in trivia at parties. NetBEUI was originally - referred to by Microsoft as "NBF", or "The Windows NT NetBEUI Frame protocol driver". + referred to by Microsoft as "NBF", or "The Windows NT NetBEUI Frame protocol driver". It is not often heard from these days.

    • - NBT: Acronym for "NetBIOS over TCP"; also known as "NetBT". Allows the continued use + NBT: Acronym for "NetBIOS over TCP"; also known as "NetBT". Allows the continued use of NetBIOS traffic proxied over TCP/IP. As a result, NetBIOS names are made to IP addresses and NetBIOS name types are conceptually equivalent to TCP/IP ports. This is how file and printer sharing are accomplished in Windows 95/98/ME. They @@ -162,7 +161,7 @@ thinking? W3K: Acronym for Windows 2003 Server

    If you plan on getting help, make sure to subscribe to the Samba Mailing List (available at http://www.samba.org). -

    Related Projects

    +

    Related Projects

    There are currently two network filesystem client projects for Linux that are directly related to Samba: SMBFS and CIFS VFS. These are both available in the Linux kernel itself.

    • @@ -184,21 +183,21 @@ nothing to do with acting as a file and print server for SMB/CIFS clients. There are other Open Source CIFS client implementations, such as the jCIFS project which provides an SMB client toolkit written in Java. -

    SMB Methodology

    +

    SMB Methodology

    Traditionally, SMB uses UDP port 137 (NetBIOS name service, or netbios-ns), UDP port 138 (NetBIOS datagram service, or netbios-dgm), and TCP port 139 (NetBIOS session service, or netbios-ssn). Anyone looking at their network with a good packet sniffer will be amazed at the amount of traffic generated by just opening up a single file. In general, SMB sessions are established in the following order:

    • - "TCP Connection" - establish 3-way handshake (connection) to port 139/tcp + "TCP Connection" - establish 3-way handshake (connection) to port 139/tcp or 445/tcp.

    • - "NetBIOS Session Request" - using the following "Calling Names": The local + "NetBIOS Session Request" - using the following "Calling Names": The local machine's NetBIOS name plus the 16th character 0x00; The server's NetBIOS name plus the 16th character 0x20

    • - "SMB Negotiate Protocol" - determine the protocol dialect to use, which will + "SMB Negotiate Protocol" - determine the protocol dialect to use, which will be one of the following: PC Network Program 1.0 (Core) - share level security mode only; Microsoft Networks 1.03 (Core Plus) - share level security mode only; Lanman1.0 (LAN Manager 1.0) - uses Challenge/Response @@ -216,7 +215,7 @@ up a single file. In general, SMB sessions are established in the following orde A good way to examine this process in depth is to try out SecurityFriday's SWB program. It allows you to walk through the establishment of a SMB/CIFS session step by step. -

    Epilogue

    “ +

    Epilogue

    “ What's fundamentally wrong is that nobody ever had any taste when they did it. Microsoft has been very much into making the user interface look good, but internally it's just a complete mess. And even people who program for Microsoft @@ -240,61 +239,52 @@ halts in the middle of something that shouldn't be strange. Normally it works fine and then once in a blue moon for some completely unknown reason, it's dead, and nobody knows why. Not Microsoft, not the experienced user and certainly not the completely clueless user who probably sits there shivering thinking -"What did I do wrong?" when they didn't do anything wrong at all. +"What did I do wrong?" when they didn't do anything wrong at all. ”

    “ -That's what's really irritating to me." +That's what's really irritating to me." ”

    -- Linus Torvalds, from an interview with BOOT Magazine, Sept 1998 -

    Miscellaneous

    +

    Miscellaneous

    This chapter is Copyright 2003 David Lechnyr (david at lechnyr dot com). Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.2 or any later version published by the Free Software Foundation. A copy of the license is available at http://www.gnu.org/licenses/fdl.txt. -

    Chapter 2. How to Install and Test SAMBA

    Andrew Tridgell

    Samba Team

    Jelmer R. Vernooij

    The Samba Team

    John H. Terpstra

    Samba Team

    Karl Auer

    Table of Contents

    Obtaining and installing samba
    Configuring samba (smb.conf)
    Example Configuration
    SWAT
    Try listing the shares available on your - server
    Try connecting with the unix client
    Try connecting from a DOS, WfWg, Win9x, WinNT, - Win2k, OS/2, etc... client
    What If Things Don't Work?
    Common Errors
    Why are so many smbd processes eating memory?
    I'm getting "open_oplock_ipc: Failed to get local UDP socket for address 100007f. Error was Cannot assign requested" in the logs

    Obtaining and installing samba

    +

    Chapter 2. How to Install and Test SAMBA

    Andrew Tridgell

    Samba Team

    Jelmer R. Vernooij

    The Samba Team

    John H. Terpstra

    Samba Team

    Karl Auer

    Table of Contents

    Obtaining and installing samba
    Configuring samba (smb.conf)
    Example Configuration
    SWAT
    Try listing the shares available on your + server
    Try connecting with the unix client
    Try connecting from another SMB client
    What If Things Don't Work?
    Common Errors
    Large number of smbd processes
    "open_oplock_ipc: Failed to get local UDP socket for address 100007f. Error was Cannot assign requested"
    "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 + UNIX distribution. There are also some packages available at the samba homepage. -

    If you need to compile samba from source, check the - appropriate appendix chapter.

    If you have already installed samba, or if your operating system +

    If you need to compile samba from source, check + the chapter about compiling samba from scratch.

    If you have already installed samba, or if your operating system was pre-installed with samba, then you may not need to bother with this chapter. On the other hand, you may want to read this chapter anyhow - for information about updating samba.

    Configuring samba (smb.conf)

    + for information about updating samba.

    Configuring samba (smb.conf)

    Samba's configuration is stored in the smb.conf file, that 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. -

    Example Configuration

    +

    Example Configuration

    There are sample configuration files in the examples subdirectory in the distribution. I suggest you read them carefully so you can see how the options go together in practice. See the man page for all the options.

    The simplest useful configuration file would be something like this:

    - 

    -	[global]
-		workgroup = MYGROUP
-
-	[homes]
-		guest ok = no
-		read only = no
-

    +

    Example 2.1. Simplest possible 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. + their login name or homes" as the service name. (Note that the workgroup that Samba must also be set.)

    - Make sure you put the smb.conf file in the same place - you specified in the Makefile (the default is to - look for it in /usr/local/samba/lib/). + Make sure you put the smb.conf file in the correct place + (usually in /etc/samba).

    For more information about security settings for the - [homes] share please refer to the chapter - Securing Samba. -

    Test your config file with testparm

    + [homes] share please refer to + "Securing Samba". +

    Test your config file with testparm

    It's important that you test the validity of your smb.conf file using the testparm program. If testparm runs OK then it will list the loaded services. If not it will give an error message. @@ -302,7 +292,7 @@ Software Foundation. A copy of the license is available at http://www.gnu.org/li Make sure it runs OK and that the services look reasonable before proceeding.

    Always run testparm again when you change smb.conf! -

    SWAT

    +

    SWAT

    SWAT is a web-based interface that helps you configure samba. SWAT might not be available in the samba package on your platform, but in a separate package. Please read the swat manpage @@ -318,9 +308,10 @@ Software Foundation. A copy of the license is available at http://www.gnu.org/li machine but connecting from a remote machine leaves your connection open to password sniffing as passwords will be sent in the clear over the wire. -

    Try listing the shares available on your - server

    $ smbclient -L - yourhostname

    You should get back a list of shares available on +

    Try listing the shares available on your + server

    +$ smbclient -L yourhostname
+

    You should get back a list of shares available on your server. If you don't then something is incorrectly setup. Note that this method can also be used to see what shares are available on other LanManager clients (such as WfWg).

    If you choose user level security then you may find @@ -328,68 +319,31 @@ Software Foundation. A copy of the license is available at http://www.gnu.org/li See the smbclient man page for details. (you can force it to list the shares without a password by adding the option -U% to the command line. This will not work - with non-Samba servers)

    Try connecting with the unix client

    $ smbclient - //yourhostname/aservice

    Typically the yourhostname + with non-Samba servers)

    Try connecting with the unix client

    +

    +$ smbclient  //yourhostname/aservice
+

    Typically the yourhostname would be the name of the host where you installed smbd. The aservice is any service you have defined in the smb.conf file. Try your user name if you just have a [homes] section in smb.conf.

    For example if your unix host is bambi - and your login name is fred you would type:

    $ smbclient //bambi/fred -

    Try connecting from a DOS, WfWg, Win9x, WinNT, - Win2k, OS/2, etc... client

    Try mounting disks. eg:

    C:\WINDOWS\> net use d: \\servername\service -

    Try printing. eg:

    C:\WINDOWS\> net use lpt1: - \\servername\spoolservice

    C:\WINDOWS\> print filename -

    What If Things Don't Work?

    Then you might read the file chapter - Diagnosis and the - FAQ. If you are still stuck then try to follow - the Analysing and Solving Problems chapter - Samba has been successfully installed at thousands of sites worldwide, - so maybe someone else has hit your problem and has overcome it.

    Common Errors

    -The following questions and issues get raised on the samba mailing list over and over again. -

    Why are so many smbd processes eating memory?

    -“ -Site that is running Samba on an AIX box. They are sharing out about 2 terabytes using samba. -Samba was installed using smitty and the binaries. We seem to be experiencing a memory problem -with this box. When I do a svmon -Pu the monitoring program shows that smbd has several -processes of smbd running: -” -

    - “ -Is samba suppose to start this many different smbd processes? Or does it run as one smbd process? Also -is it normal for it to be taking up this much memory? -” -

    + and your login name is fred you would type:

    +$ smbclient //bambi/fred
+

    Try connecting from another SMB client

    Try mounting disks. from a DOS, Windows or OS/2 client, eg:

    +C:\> net use d: \\servername\service
+

    Try printing. eg:

    -Inuse * 4096 = amount of memory being used by this process
-
-     Pid Command        Inuse      Pin     Pgsp  Virtual   64-bit    Mthrd
-   20950 smbd           33098     1906      181     5017        N        N
-   22262 smbd            9104     1906      5410
-   21060 smbd            9048     1906      181     5479        N        N
-   25972 smbd            8678     1906      181     5109        N        N
-   24524 smbd            8674     1906      181     5105        N        N
-   19262 smbd            8582     1906      181     5013        N        N
-   20722 smbd            8572     1906      181     5003        N        N
-   21454 smbd            8572     1906      181     5003        N        N
-   28946 smbd            8567     1906      181     4996        N        N
-   24076 smbd            8566     1906      181     4996        N        N
-   20138 smbd            8566     1906      181     4996        N        N
-   17608 smbd            8565     1906      181     4996        N        N
-   21820 smbd            8565     1906      181     4996        N        N
-   26940 smbd            8565     1906      181     4996        N        N
-   19884 smbd            8565     1906      181     4996        N        N
-    9912 smbd            8565     1906      181     4996        N        N
-   25800 smbd            8564     1906      181     4995        N        N
-   20452 smbd            8564     1906      181     4995        N        N
-   18592 smbd            8562     1906      181     4993        N        N
-   28216 smbd            8521     1906      181     4954        N        N
-   19110 smbd            8404     1906      181     4862        N        N
-
-   Total memory used:  841,592,832 bytes
+C:\> net use lpt1:	\\servername\spoolservice

    -

    +

    C:\> print filename
+

    What If Things Don't Work?

    Then you might read the file chapter diagnosis + and the FAQ. If you are still stuck then refer to "Analysing and solving problems". + Samba has been successfully installed at thousands of sites worldwide, + so maybe someone else has hit your problem and has overcome it.

    Common Errors

    +The following questions and issues get raised on the samba mailing list over and over again. +

    Large number of smbd processes

    Samba consists on three core programs: nmbd, smbd, winbindd. nmbd is the name server message daemon, smbd is the server message daemon, winbindd is the daemon that @@ -403,19 +357,20 @@ two (2) instances - one to handle the WINS requests. connection made. That is why you are seeing so many of them, one (1) per client connection.

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

    I'm getting "open_oplock_ipc: Failed to get local UDP socket for address 100007f. Error was Cannot assign requested" in the logs

    Your loopback device isn't working correctly. Make sure it's running.

    Chapter 3. Fast Start for the Impatient

    John H. Terpstra

    Samba Team

    Table of Contents

    Note

    Note

    +run in "split mode" (in which case there will be two instances). +

    "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's configured properly. 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"

    + This error can be caused by one of these misconfigurations: +

    • You specified an nonexisting path for the share in smb.conf

    • The user you are trying to access the share with does not + have sufficient permissions to access the path for the share. Both read (r) and access (x) should be possible.

    • The share you are trying to access does not exist.

    Chapter 3. Fast Start for the Impatient

    John H. Terpstra

    Samba Team

    Table of Contents

    Note

    Note

    This chapter did not make it into this release. It is planned for the published release of this document. -

    Server Configuration Basics

    First Steps in Server Configuration

    +

    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

    4. 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)
    Seamless Windows Network Integration
    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
    5. Domain Control
    Features and Benefits
    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 Problems and Errors
    I cannot include a '$' in a machine name
    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.
    The system can not log you on (C000019B)....
    The machine trust account for this computer either does not -exist or is not accessible.
    When I attempt to login to a Samba Domain from a NT4/W2K workstation, -I get a message about my account being disabled.
    Until a few minutes after Samba has started, clients get the error "Domain Controller Unavailable"
    6. Backup Domain Control
    Features And Benefits
    Essential Background Information
    MS Windows NT4 Style Domain Control
    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, what can I do?
    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?
    7. Domain Membership
    Features and Benefits
    MS Windows Workstation/Server Machine Trust Accounts
    Manual Creation of Machine Trust Accounts
    Using NT4 Server Manager to Add Machine Accounts to the Domain
    "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
    Setup your smb.conf
    Setup your /etc/krb5.conf
    Create the computer account
    Test your server setup
    Testing with smbclient
    Notes
    Common Errors
    Can Not Add Machine Back to Domain
    Adding Machine to Domain Fails
    8. Stand-Alone Servers
    Features and Benefits
    Background
    Example Configuration
    Reference Documentation Server
    Central Print Serving
    Common Errors
    9. MS Windows Network Configuration Guide
    Note

    Chapter 4. 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)
    Seamless Windows Network Integration
    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

    +

    Table of Contents

    4. 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
    5. Domain Control
    Features and Benefits
    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 can not log you on (C000019B)....
    The machine trust account not accessible
    Account disabled
    Domain Controller Unavailable
    Can not log onto domain member workstation after joining domain
    6. Backup Domain Control
    Features And Benefits
    Essential Background Information
    MS Windows NT4 Style Domain Control
    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, what can I do?
    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?
    7. Domain Membership
    Features and Benefits
    MS Windows Workstation/Server Machine Trust Accounts
    Manual Creation of Machine Trust Accounts
    Using NT4 Server Manager to Add Machine Accounts to the Domain
    "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
    Setup your smb.conf
    Setup your /etc/krb5.conf
    Create the computer account
    Test your server setup
    Testing with smbclient
    Notes
    Common Errors
    Can Not Add Machine Back to Domain
    Adding Machine to Domain Fails
    8. Stand-Alone Servers
    Features and Benefits
    Background
    Example Configuration
    Reference Documentation Server
    Central Print Serving
    Common Errors
    9. MS Windows Network Configuration Guide
    Note

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

    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 to use Samba will want to know what, within a Samba context, terms familiar to MS Windows @@ -425,10 +380,11 @@ modes function BEFORE we get into the details of how to configure the server its The chapter provides an overview of the security modes of which Samba is capable and how these relate to MS Windows servers and clients.

    -Firstly we should recognise the question so often asked, "Why would I want to use Samba?" -So, in those chapters where the answer may be important you will see a section that highlights -features and benefits. These may be for or against Samba. -

    Features and Benefits

    +A question often asked is, "Why would I want to use Samba?" Most chapters contain a section +that 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 towards Samba so the benefit may be on the side of our competition. +

    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 fitting his anguish. The other looked at the stone and said, that is a garnet - I @@ -440,7 +396,7 @@ pleasure, but if you are forced upon it and have no time for its secrets then it 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 +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 like this one we will tell of both.

    @@ -464,14 +420,14 @@ So now, what are the benefits of features mentioned in this chapter? greater flexibility than MS Windows NT4 and in many cases a significantly higher utility than Active Directory domains with MS Windows 200x. -

    Server Types

    Administrators of Microsoft networks often refer to three -different type of servers:

    • Domain Controller

      Primary Domain Controller
      Backup Domain Controller
      ADS Domain Controller

    • Domain Member Server

      Active Directory Member Server
      NT4 Style Domain Member Server

    • Stand Alone Server

    +

    Server Types

    Administrators of Microsoft networks often refer to three +different type of servers:

    • Domain Controller

      • Primary Domain Controller

      • Backup Domain Controller

      • ADS Domain Controller

    • Domain Member Server

      • Active Directory Domain Server

      • NT4 Style Domain Domain Server

    • Stand Alone Server

    The chapters covering Domain Control, Backup Domain Control and Domain Membership provide -pertinent information regarding Samba-3 configuration for each of these server roles. +pertinent information regarding Samba configuration for each of these server roles. The reader is strongly encouraged to become intimately familiar with the information presented. -

    Samba Security Modes

    -In this section the function and purpose of Samba's security +

    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. @@ -486,7 +442,7 @@ ways that allow the security levels to be implemented. In actual fact, Samba imp ADS, and SERVER modes. They are documented in this chapter.

    -A SMB server tells the client at startup what security level + A SMB server tells the client at startup what security level it is running. There are two options: share level and user level. Which of these two the client receives affects the way the client then tries to authenticate itself. It does not directly affect @@ -494,8 +450,8 @@ the way the client then tries to authenticate itself. It does not directly affec but it fits in with the client/server approach of SMB. In SMB everything is initiated and controlled by the client, and the server can only tell the client what is available and whether an action is allowed. -

    User Level Security

    -We will describe user level security first, as it's simpler. +

    User Level Security

    +We will describe user level security first, as it's simpler. In user level security, the client will send a session setup command directly after the protocol negotiation. This contains a username and password. The server can either accept or reject that @@ -512,13 +468,11 @@ It is also possible for a client to send multiple ses 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). -

    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

    Ok, now for share level security. In share level security, the client authenticates itself separately for each share. It will send a password along with each tree connection (share mount). It does not explicitly send a @@ -538,104 +492,92 @@ level security. They normally send a valid username but no password. Samba recor this username in a list of possible usernames. When the client then does a tree connection it also adds to this list the name of the share they try to connect to (useful for home directories) and any users -listed in the user = smb.conf line. The password is then checked +listed in the user smb.conf line. The password is then checked in turn against these possible usernames. If a match is found then the client is authenticated as that user. -

    Example Configuration

    +

    Example Configuration

    The smb.conf parameter that sets Share Level Security is: -

    -	security = share
-

    +

    security = share

    Please note that there are reports that recent MS Windows clients do not like to work with share mode security servers. You are strongly discouraged from using share level security. -

    Domain Security Mode (User Level Security)

    -When Samba is operating in security = domain mode, +

    Domain Security Mode (User Level Security)

    +When Samba is operating in security = domain mode, the Samba server has a domain security trust account (a machine account) and will cause all authentication requests to be passed through to the domain controllers. -

    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 = "name_of_NT_domain"
-

    +

    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. Next, on the Unix/Linux system execute:

      root# smbpasswd -j DOMAIN_NAME -r PDC_NAME (samba-2.x)

      root# net join -U administrator%password (samba-3)

    Note

    -As of Samba-2.2.4 the Samba 2.2.x series can auto-join a Windows NT4 style Domain just -by executing: +

  • Next, on the UNIX/Linux system execute:

    root# net rpc join -U administrator%password

    • Note

    +Samba-2.2.4 and later can auto-join a Windows NT4 style Domain just by executing: 

    -root# smbpasswd -j DOMAIN_NAME -r PDC_NAME -U Administrator%password
+root# smbpasswd -j DOMAIN_NAME -r PDC_NAME \
+	 -U Administrator%password

    -As of Samba-3 the same can be done by executing: +Samba-3 can do the same by executing: 

    -root# net join -U Administrator%password
+root# net rpc join -U Administrator%password

    -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. +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 does require there to be a standard Unix account -for each user in order to assign a uid once the account has been authenticated by +Use of this mode of authentication does require there to be a standard UNIX account +for each user in order to assign a UID once the account has been authenticated by the remote Windows DC. This account can be blocked to prevent logons by clients other than -MS Windows through things such as setting an invalid shell in the +MS Windows through means such as setting an invalid shell in the /etc/passwd entry.

    An alternative to assigning UIDs to Windows users on a Samba member server is -presented in the Winbind Overview chapter -in this HOWTO collection. +presented in the chapter about winbind.

    -For more information of being a domain member, see the Domain -Member section of this Howto. -

    ADS Security Mode (User Level Security)

    + For more information of being a domain member, see the chapter about domain membership. +

    ADS Security Mode (User Level Security)

    Both Samba 2.2 and 3.0 can join an Active Directory domain. This is -possible even if the domain is run in native mode. Active Directory in -native mode perfectly allows NT4-style domain members, contrary to +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. The only thing that Active Directory in native mode prohibits is Backup Domain Controllers running NT4.

    -If you are running Active Directory starting with Samba 3.0 you can -however join as a native AD member. Why would you want to do that? +If you are using Active Directory, starting with Samba-3 you can +join as a native AD member. Why would you want to do that? Your security policy might prohibit the use of NT-compatible authentication protocols. All your machines are running Windows 2000 -and above and all use full Kerberos. In this case Samba as a NT4-style +and above and all use Kerberos. In this case Samba as a NT4-style domain would still require NT-compatible authentication data. Samba in -AD-member mode can accept Kerberos. -

    Example Configuration

    -	realm = your.kerberos.REALM
-	security = ADS
-

    - The following parameter may be required: -

    -	ads server = your.kerberos.server
-

    -Please refer to the Domain Membership and Active Directory -Membership sections for more information regarding this configuration option. -

    Server Security (User Level Security)

    +AD-member mode can accept Kerberos tickets. +

    Example Configuration

    realm = your.kerberos.REALM
    security = ADS

    +The following parameter may be required: +

    ads server = your.kerberos.server

    +Please refer to the chapter on domain membership +for more information regarding this configuration option. +

    Server Security (User Level Security)

    Server security mode is a 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 draw backs. The draw backs 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, 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.

    +

    • 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, 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 login to the -password server by sending exactly the same username/password that +password server by sending exactly the same username/password that it got from the client. If that server is in user level security and accepts the password, then Samba accepts the clients connection. This allows the Samba server to use another SMB -server as the password server. +server as the password server.

    You should also note that at the very start of all this, where the server tells the client what security level it is in, it also tells the client if it supports encryption. If it does then it supplies the client with a random cryptkey. The client will then send all passwords in encrypted form. Samba supports this type of encryption by default.

    -The parameter security = server means that Samba reports to clients that +The parameter security = server means that Samba reports to clients that it is running in user mode but actually passes off all authentication requests to another user mode server. This requires an additional -parameter password server that points to the real authentication server. +parameter password server that points to the real authentication server. That real authentication server can be another Samba server or can be a Windows NT server, the later natively capable of encrypted password support.

    Note

    @@ -646,17 +588,13 @@ lookups because the choice of the target authentication server is arbitrary and 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"
-

    -There are two ways of identifying whether or not a username and password pair was valid -or not. One uses the reply information provided as part of the authentication messaging +

    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 was valid. +One uses the reply information provided as part of the authentication messaging process, the other uses just an error code.

    The down-side of this mode of configuration is the fact that for security reasons Samba @@ -665,9 +603,9 @@ server fails to reject the username and password pair then an alternative mode o identification of validation is used. Where a site uses password lock out after a certain number of failed authentication attempts this will result in user lockouts.

    -Use of this mode of authentication does require there to be a standard Unix account +Use of this mode of authentication does require there to be a standard UNIX account for the user, though this account can be blocked to prevent logons by non-SMB/CIFS clients. -

    Seamless Windows Network Integration

    +

    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, @@ -681,7 +619,7 @@ is encrypted in two ways:

  • The password is converted to upper case, and then padded or truncated to 14 bytes. This string is then appended with 5 bytes of NULL characters and split to - form two 56 bit DES keys to encrypt a "magic" 8 byte value. + 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, MS Windows NT versions 3.x and version 4.0 @@ -704,29 +642,26 @@ is definitely not a good idea to re-enable plain text password support in such c The following parameters can be used to work around the issue of Windows 9x clients upper casing usernames and password before transmitting them to the SMB server when using clear text authentication. -

    -        password level = integer
-        username level = integer
-

    +

    password level = integer
    username level = integer

    By default Samba will lower case the username before attempting to lookup the user in the database of local system accounts. Because UNIX usernames conventionally -only contain lower case character, the username level parameter +only contain lower-case character, the username level parameter is rarely needed.

    -However, passwords on UNIX systems often make use of mixed case characters. +However, passwords on UNIX systems often make use of mixed-case characters. This means that in order for a user on a Windows 9x client to connect to a Samba -server using clear text authentication, the password level -must be set to the maximum number of upper case letter which could -appear is a password. Note that the server OS uses the traditional DES version -of crypt(), a password level of 8 will result in case +server using clear text authentication, the password level +must be set to the maximum number of upper case letters which could +appear in a password. Note that if the server OS uses the traditional DES version +of crypt(), a password level of 8 will result in case insensitive passwords as seen from Windows users. This will also result in longer login times as Samba has to compute the permutations of the password string and try them one by one until a match is located (or all combinations fail).

    -The best option to adopt is to enable support for encrypted passwords where ever +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 plain text passwords will eventually lead to user complaints and unhappiness. -

    Common Errors

    +

    Common Errors

    We all make mistakes. It is Ok to make mistakes, so long as they are made in the right places and at the right time. A mistake that causes lost productivity is seldom tolerated. A mistake made in a developmental test lab is expected. @@ -736,32 +671,29 @@ on the Samba mailing lists. Many of these are avoidable by doing you homework be a Samba implementation. Some are the result of misunderstanding of the English language. The English language has many turns of phrase 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 very obvious, but entirely -wrong all the same. It is assumed that security = server means that Samba +wrong all the same. It is assumed that security = server means that Samba will act as a server. Not so! See above - this setting means that Samba will try to use another SMB server as its source of user authentication alone. -

    What makes Samba a Domain Controller?

    -The smb.conf parameter security = domain does NOT really make Samba behave +

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

    What makes Samba a Domain Member?

    -Guess! So many others do. But whatever you do, do NOT think that security = user +

    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 manufacturers manual before the warranty expires! See -the Domain Member section of this Howto for more information. -

    Constantly Losing Connections to Password Server

    +the chapter about domain membership for more information. +

    Constantly Losing Connections to Password Server

    + “ Why does server_validate() simply give up rather than re-establishing 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 server, which means the password hashes submitted by the client would not work on a subsequent -connection, whose session key would be different. So server_validate() must give up. -

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

    Chapter 5. Domain Control

    John H. Terpstra

    Samba Team

    Gerald (Jerry) Carter

    Samba Team

    David Bannon

    Samba Team

    Table of Contents

    Features and Benefits
    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 Problems and Errors
    I cannot include a '$' in a machine name
    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.
    The system can not log you on (C000019B)....
    The machine trust account for this computer either does not -exist or is not accessible.
    When I attempt to login to a Samba Domain from a NT4/W2K workstation, -I get a message about my account being disabled.
    Until a few minutes after Samba has started, clients get the error "Domain Controller Unavailable"

    The Essence of Learning:  +connection, whose session key would be different. So server_validate() must give up.” +

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

    Chapter 5. Domain Control

    John H. Terpstra

    Samba Team

    Gerald (Jerry) Carter

    Samba Team

    David Bannon

    Samba Team

    Table of Contents

    Features and Benefits
    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 can not log you on (C000019B)....
    The machine trust account not accessible
    Account disabled
    Domain Controller Unavailable
    Can not log onto domain member workstation after joining domain

    The Essence of Learning:  There are many who approach MS Windows networking with incredible misconceptions. That's OK, because it gives the rest of us plenty of opportunity to be of assistance. Those who really want help would be well advised to become familiar with information @@ -769,18 +701,18 @@ that is already available.

    The reader is advised NOT to tackle this section without having first understood and mastered some basics. MS Windows networking is not particularly forgiving of -misconfiguration. Users of MS Windows networking are likely to complain bitterly -of persistent niggles that may be caused by broken network or system configuration. +misconfiguration. Users of MS Windows networking are likely to complain +of persistent niggles that may be caused by a broken network configuration. To a great many people however, MS Windows networking starts with a domain controller that in some magical way is expected to solve all ills. -

    +

    Figure 5.1. An Example Domain

    An Example Domain

    From the Samba mailing list one can readily identify many common networking issues. If you are not clear on the following subjects, then it will do much good to read the sections of this HOWTO that deal with it. These are the most common causes of MS Windows networking problems: -

    Basic TCP/IP configuration
    NetBIOS name resolution
    Authentication configuration
    User and Group configuration
    Basic File and Directory Permission Control in Unix/Linux
    Understanding of how MS Windows clients interoperate in a network - environment

    -Do not be put off; on the surface of it MS Windows networking seems so simple that any fool +

    • Basic TCP/IP configuration

    • NetBIOS name resolution

    • Authentication configuration

    • User and Group configuration

    • Basic File and Directory Permission Control in UNIX/Linux

    • Understanding of how MS Windows clients interoperate in a network + environment

    +Do not be put off; on the surface of it MS Windows networking seems so simple that anyone can do it. In fact, it is not a good idea to set up an MS Windows network with inadequate training and preparation. But let's get our first indelible principle out of the way: It is perfectly OK to make mistakes! In the right place and at @@ -791,7 +723,7 @@ burden on an organisation. Where is the right place to make mistakes? Only out of harm's way! If you are going to make mistakes, then please do this on a test network, away from users and in such a way as to not inflict pain on others. Do your learning on a test network. -

    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 @@ -802,13 +734,18 @@ and they will be able to log onto the network and access resources (shares, file 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 fully available to those sites that deploy a Samba PDC. +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 +know only of local security identifiers.

    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 account). Please refer to the chapter on -Domain Membership for more information. +setting up samba as a domain member for more information.

    The following functionalities are new to the Samba-3 release:

    • @@ -816,8 +753,7 @@ The following functionalities are new to the Samba-3 release:

    • Adding users via the User Manager for Domains. This can be done on any MS Windows client using the Nexus toolkit that is available from Microsoft's web site. - At some later date Samba-3 may get support for the use of the Microsoft Management - Console for user management. + Samba-3 supports the use of the Microsoft Management Console for user management.

    • Introduces replaceable and multiple user account (authentication) back ends. In the case where the back end is placed in an LDAP database, @@ -831,14 +767,18 @@ 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) + (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 or + replicate account data to Windows-BDC's.

      • Acting as a Windows 2000 Domain Controller (i.e. Kerberos and Active Directory) - In point of fact, Samba-3 DOES have some Active Directory Domain Control ability that is at this time purely experimental AND that is certain to change as it becomes a fully supported feature some time - during the Samba-3 (or later) life cycle. + during the Samba-3 (or later) life cycle. However, Active Directory is + more then just SMB - it's also LDAP, Kerberos, DHCP and other protocols + (with proprietary extensions, of course).

      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 @@ -847,67 +787,33 @@ for some time. These clients use the old LanMan Network Logon facilities that ar in Samba since approximately the Samba-1.9.15 series.

      Samba-3 has an implementation of group mapping between Windows NT groups -and Unix groups (this is really quite complicated to explain in a short space). This is -discussed more fully in the Group Mapping chapter. +and UNIX groups (this is really quite complicated to explain in a short space). This is +discussed more fully in the chapter on group mapping.

      Samba-3, like an MS Windows NT4 PDC or a Windows 200x Active Directory, needs to store -user and machine trust account information in a suitable backend data store. With Samba-3 -there can be multiple back-ends for this including: -

      • - smbpasswd - the plain ASCII file stored used by - earlier versions of Samba. This file configuration option requires - a Unix/Linux system account for EVERY entry (ie: both for user and for - machine accounts). This file will be located in the private - directory (default is /usr/local/samba/lib/private or on linux /etc/samba). -

      • - tdbsam - a binary database backend that will be - stored in the private directory in a file called - passdb.tdb. The key benefit of this binary format - file is that it can store binary objects that can not be accommodated - in the traditional plain text smbpasswd file. These permit the extended - account controls that MS Windows NT4 and later also have. -

      • - ldapsam - An LDAP based back-end. Permits the - LDAP server to be specified. eg: ldap://localhost or ldap://frodo.murphy.com. - Like the tdbsam, ldapsam permits the storing of extended account attributes - for control of things like: Permitted access times, password activation and - expiry, permitted points of access (workstation names), per user profile - location, and much more. -

      • - ldapsam_compat - An LDAP back-end that maintains backwards - compatibility with the behaviour of samba-2.2.x. You should use this in the process - of migrating from samba-2.2.x to samba-3 if you do not want to rebuild your LDAP - database. -

      -Read the chapter about Account Information Database for details -regarding the choices available and how to configure them. -

      Note

      -The new tdbsam and ldapsam account backends store substantially more information than -smbpasswd is capable of. The new backend database includes capacity to specify -per user settings for many parameters, over-riding global settings given in the -smb.conf file. eg: logon drive, logon home, logon path, etc. -Thus, with samba-3 it is possible to have a default system configuration for profiles, -and on a per user basis to over-ride this for those users who should not be subject -to the default configuration. -

    Basics of Domain Control

    +user and machine trust account information in a suitable backend data store. +Refer to the section on machine trust accounts. With Samba-3 there can be multiple +back-ends for this. A complete discussion of account database backends can be found in +the chapter on Account Information Databases. +

    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

    • Primary Domain Controller

    • Backup Domain Controller

    • ADS Domain Controller

    +

    Domain Controller Types

    • Primary Domain Controller

    • Backup Domain Controller

    • ADS Domain Controller

    The Primary Domain Controller or PDC plays an important role in the MS -Windows NT4 and Windows 200x Domain Control architecture, but not in the manner that so many -expect. There is folk lore that dictates that because of it's role in the MS Windows -network, the PDC should be the most powerful and most capable machine in the network. +Windows NT4. In Windows 200x Domain Control architecture this role is held by domain controllers. +There is folk lore that dictates that because of it's role in the MS Windows +network, the domain controllers should be the most powerful and most capable machine in the network. As strange as it may seem to say this here, good over all network performance dictates that -the entire infrastructure needs to be balanced. It is advisable to invest more in the Backup -Domain Controllers and Stand-Alone (or Domain Member) servers than in the PDC. +the entire infrastructure needs to be balanced. It is advisable to invest more in Stand-Alone +(or Domain Member) servers than in the domain controllers.

    -In the case of MS Windows NT4 style domains, it is the PDC seeds the Domain Control database, -a part of the Windows registry called the SAM (Security Account Manager). It plays a key +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 SAM (Security Account Manager). It plays a key part in NT4 type domain user authentication and in synchronisation of the domain authentication database with Backup Domain Controllers.

    -With MS Windows 200x Server based Active Directory domains, one domain controller seeds a potential +With MS Windows 200x Server based Active Directory domains, one domain controller initiates a potential hierarchy of domain controllers, each with their own area of delegated control. The master domain controller has the ability to override any down-stream controller, but a down-line controller has control only over it's down-line. With Samba-3 this functionality can be implemented using an @@ -915,9 +821,7 @@ LDAP based user and machine account back end.

    New to Samba-3 is the ability to use a back-end database that holds the same type of data as the NT4 style SAM (Security Account Manager) database (one of the registry files). -The Samba-3 SAM can be specified via the smb.conf file parameter -passwd backend and valid options include -smbpasswd, tdbsam, ldapsam, nisplussam, xmlsam, mysqlsam, guest. +[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. @@ -941,11 +845,14 @@ excluding the SAM replication components. However, please be aware that Samba-3 MS Windows 200x domain control protocols also.

    At this time any appearance that Samba-3 is capable of acting as an -ADS Domain Controller is limited and experimental in nature. +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 configuration and -management requirements. -

    Preparing for Domain Control

    +management requirements. Samba can act as a NT4-style DC in a Windows 2000/XP +environment. However, there are certain compromises: + +

    • No machine policy files

    • No Group Policy Objects

    • No synchronously executed AD logon scripts

    • Can't use ANY Active Directory management tools to manage users and machines

    • Registry changes tattoo the main registry, while with AD they do NOT. ie: Leave permanent changes in effect

    • Without AD you can not peprform the function of exporting specific 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 Stand-Alone systems, more commonly called Workgroup members, or as full participants in a security system, @@ -967,23 +874,22 @@ Domain it triggers a machine password change.

    Note

    When running a Domain all MS Windows NT / 200x / XP Professional clients should be configured as full Domain Members - IF A SECURE NETWORK IS WANTED. If the machine is NOT made a member of the -Domain, then it will operate like a workgroup (stand-alone) machine. Please refer the -Domain Membership chapter for information regarding - HOW to make your MS Windows clients Domain members. +Domain, then it will operate like a workgroup (stand-alone) machine. Please refer to +the chapter on domain membership for information regarding HOW to make your MS Windows clients Domain members.

    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 (See chapter on Browsing and on - MS Windows network Integration)
    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 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 (See chapter on Network Browsing and on + Integrating Unix into Windows networks)

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

    +

    • Configuration of basic TCP/IP and MS Windows Networking

    • Correct designation of the Server Role (security = user)

    • Network Logon Configuration (Since Windows 9x / 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 the Profile Management and -Policy Management chapters of this document. However, these are not necessarily specific -to a Samba PDC as much as they are related to Windows NT networking concepts. +Policy Management chapters of this document. However, these are not +necessarily specific to a Samba PDC as much as they are related to Windows NT networking concepts.

    A Domain Controller is an SMB/CIFS server that:

    • @@ -998,120 +904,86 @@ A Domain Controller is an SMB/CIFS server that: Provides a share called NETLOGON

    For Samba to provide these is rather easy to configure. Each Samba Domain Controller must provide -the NETLOGON service which Samba calls the domain logons functionality +the NETLOGON service which Samba calls the domain logons functionality (after the name of the parameter in the smb.conf file). Additionally, one (1) server in a Samba-3 -Domain must advertise itself as the domain master browser. This causes the Primary Domain Controller +Domain must advertise itself as the domain master browser[2]. This causes the Primary Domain Controller to claim domain specific NetBIOS name that identifies it as a domain master browser for its given domain/workgroup. Local master browsers in the same domain/workgroup on broadcast-isolated subnets then ask for a complete copy of the browse list for the whole wide area network. Browser clients will then contact their local master browser, and will receive the domain-wide browse list, instead of just the list for their broadcast-isolated subnet. -

    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. Here we attempt to explain the parameters that are covered in -the smb.conf man page. -

    -Here is an example smb.conf for acting as a PDC: -

    -	[global]
-	    ; Basic server settings
-	    netbios name = POGO
-	    workgroup = NARNIA
-
-	    ; User and Machine Account Backends
-	    ; Choices are: tdbsam, smbpasswd, ldapsam, mysqlsam, xmlsam, guest
-	    passdb backend = ldapsam, guest
-
-	    ; we should act as the domain and local master browser
-	    os level = 64
-	    preferred master = yes
-	    domain master = yes
-	    local master = yes
-	    
-	    ; security settings (must user security = user)
-	    security = user
-	    
-	    ; encrypted passwords are a requirement for a PDC (default = Yes)
-	    encrypt passwords = yes
-	    
-	    ; support domain logons
-	    domain logons = yes
-	    
-	    ; where to store user profiles?
-	    logon path = \\%N\profiles\%u
-	    
-	    ; where is a user's home directory and where should it be mounted at?
-	    logon drive = H:
-	    logon home = \\homeserver\%u\winprofile
-	    
-	    ; specify a generic logon script for all users
-	    ; this is a relative **DOS** path to the [netlogon] share
-	    logon script = logon.cmd
-
-	; necessary share for domain controller
-	[netlogon]
-	    path = /usr/local/samba/lib/netlogon
-	    read only = yes
-	    write list = ntadmin
-	    
-	; share for storing user profiles
-	[profiles]
-	    path = /export/smb/ntprofile
-	    read only = no
-	    create mask = 0600
-	    directory mask = 0700
-

    Note

    +in smb.conf. An example smb.conf for acting as a PDC can be found in the example +for being a PDC. +

    +

    Example 5.1. smb.conf for being a PDC

    [global]
    netbios name = BELERIAND
    workgroup = MIDEARTH
    passdb backend = ldapsam, guest
    os level = 33
    preferred master = yes
    domain master = yes
    local master = yes
    security = user
    encrypt passwords = yes
    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
    write list = ntadmin
    [profiles]
    path = /var/lib/samba/profiles
    read only = no
    create mask = 0600
    directory mask = 0700

    +

    +The basic options shown above are explained as follows: +

    passdb backend

    + This contains all the user and group account information. Acceptable values for a PDC + are: smbpasswd, tdbsam, ldapsam. The 'guest' entry provides needed + default accounts.

    + Where is is intended to use backup domain controllers (BDCs) the only logical choice is + to use LDAP so that the passdb backend can be distributed. The tdbsam and smbpasswd files + can not effectively be distributed and therefore should not be used. +

    Domain Control Parameters

    + The parameters os level, preferred master, domain master, security, + encrypt passwords, 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 domain master browser, 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 the chapter on account information databases. +

    Environment Parameters

    + The parameters logon path, logon home, logon drive, 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. Eash 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 + allow a Samba administrator to make the directory read only to everyone. Of course this is useful + only after the profile has been properly created. +

    Note

    The above parameters make for a full set of parameters that may define the server's mode -of operation. The following parameters are the essentials alone: - -

    -	workgroup = NARNIA
-	domain logons = Yes
-	domain master = Yes
-	security = User
-

    - -The additional parameters shown in the longer listing above just makes for a -more complete environment. -

    -There are a couple of points to emphasize in the above configuration. -

    • - Encrypted passwords must be enabled. For more details on how - to do this, refer to Account Information Database chapter. -

    • - The server must support domain logons and have a - [netlogon] share -

    • - The server must be the domain master browser in order for Windows - client to locate the server as a DC. Please refer to the various - Network Browsing documentation included with this distribution for - details. -

    Samba ADS Domain Control

    -Samba-3 is not and can not act as an Active Directory Server. It can not truly function as +of operation. The following smb.conf parameters are the essentials alone: +

    +

    netbios name = BELERIAND
    workgroup = MIDEARTH
    domain logons = Yes
    domain master = Yes
    security = User

    +

    +The additional parameters shown in the longer listing above just makes for +more complete explanation. +

    Samba ADS Domain Control

    +Samba-3 is not, and can not act as, an Active Directory Server. It can not truly function as an Active Directory Primary Domain Controller. The protocols for some of the functionality -the Active Directory Domain Controllers is have been partially implemented on an experimental -only basis. Please do NOT expect Samba-3 to support these protocols - nor should you depend -on any such functionality either now or in the future. The Samba-Team may well remove such -experimental features or may change their behaviour. -

    Domain and Network Logon Configuration

    -The subject of Network or Domain Logons is discussed here because it rightly forms +the 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 depend +on any such functionality either now or in the future. The Samba-Team may remove these +experimental features or may change their behaviour. This is mentioned for the benefit of those +who have discovered secret capabilities in samba-3 and who have asked when this functionality will be +completed. The answer is: Maybe 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 contollers do not have. In short, Samba-3 is not NT4 and it +is not Windows Server 200x and it is not an Active Directory server. We hope this is plain and simple +enough for all to understand. +

    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 Primary Domain Controller); on ALL Backup Domain Controllers domain master = No +in Samba). One Domain Controller must be configured with domain master = Yes +(the Primary Domain Controller); on ALL Backup Domain Controllers domain master = No must be set. -

    Example Configuration

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

    Note

    +

    Example Configuration

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

    Note

    MS Windows XP Home Edition does not have the ability to join any type of Domain security facility. Unlike, MS Windows 9x / Me, MS Windows XP Home Edition also completely lacks the ability to log onto a network. @@ -1123,8 +995,10 @@ MS Windows XP Professional.

    Now that this has been said, please do NOT ask the mailing list, or email any of the Samba-Team members with your questions asking how to make this work. It can't be done. -

    The Special Case of Windows 9x / Me

    -A domain and a workgroup are exactly the same thing in terms of network +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

    +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 network. Also, different access rights can be granted to users if they @@ -1145,7 +1019,7 @@ which are the focus of this section. When an SMB client in a domain wishes to logon, 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 very stupid) to create a domain where the user +It is possible (but ill advised ) to create a domain where the user database is not shared between servers, i.e. they are effectively workgroup servers advertising themselves as participating in a domain. This demonstrates how authentication is quite different from but closely @@ -1196,14 +1070,17 @@ The main difference between a PDC and a Windows 9x logon server configuration is

    • Password encryption is not required for a Windows 9x logon server. But note that beginning with MS Windows 98 the default setting is that plain-text - password support has been disabled. It can be re-enabled with the registry + password support is disabled. It can be re-enabled with the registry changes that are documented in the chapter on Policies.

    • Windows 9x/ME clients do not require and do not use machine trust accounts.

    A Samba PDC will act as a Windows 9x logon server; after all, it does provide the network logon services that MS Windows 9x / Me expect to find. -

    Security Mode and Master Browsers

    +

    Note

    +Use of plain-text passwords is strongly discouraged. Where used they are easily detected +using a sniffer tool to examine network traffic. +

    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 or not it is ok to configure Samba as a Domain Controller in security @@ -1220,24 +1097,25 @@ are two distinctly different functions), it is not a good idea to do so. You should remember that the DC must register the DOMAIN<#1b> NetBIOS name. This is the name used by Windows clients to locate the DC. Windows clients do not distinguish between the DC and the DMB. +A DMB is a Domain Master Browser - see Domain Master Browser. For this reason, it is very wise to configure the Samba DC as the DMB.

    Now back to the issue of configuring a Samba DC to use a mode other -than security = user. If a Samba host is configured to use +than security = user. If a Samba host is configured to use another SMB server or DC in order to validate user connection requests, then it is a fact that some other machine on the network -(the password server) knows more about the user than the Samba host. +(the password server) knows more about the user than the Samba host. 99% of the time, this other host is a domain controller. Now -in order to operate in domain mode security, the workgroup parameter +in order to operate in domain mode security, the workgroup parameter must be set to the name of the Windows NT domain (which already has a domain controller). If the domain does NOT already have a Domain Controller then you do not yet have a Domain!

    Configuring a Samba box as a DC for a domain that already by definition has a PDC is asking for trouble. Therefore, you should always configure the Samba DC -to be the DMB for its domain and set security = user. +to be the DMB for its domain and set security = user. This is the only officially supported mode of operation. -

    Common Problems and Errors

    I cannot include a '$' in a 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. FreeBSD (and other BSD systems?) won't create a user with a '$' in their name. @@ -1245,24 +1123,26 @@ systems?) won't create a user with a '$' in their name. 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 ID! -

    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.

    +

    Note

    +The UNIX tool vipw is a common tool for directly editting the /etc/passwd file. +

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

    This happens if you try to create a machine trust account from the machine itself and already have a connection (e.g. mapped drive) to a share (or IPC$) on the Samba PDC. The following command will remove all network drive connections: 

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

    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 can not log you on (C000019B)....

    I joined the domain successfully but after upgrading +

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

    “I joined the domain successfully but after upgrading to a newer version of the Samba code I get the message, The system can not log you on (C000019B), Please try again or consult your -system administrator when attempting to logon. +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 @@ -1277,14 +1157,18 @@ The reset or change the domain SID you can use the net command as follows: root# net getlocalsid 'OLDNAME' root# net setlocalsid 'SID'

    -

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

    -When I try to join the domain I get the message The machine account +

    +Workstation machine trust accounts work only with the Domain (or network) SID. If this SID changes +then 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 re-join +it to the domain. +

    The machine trust account 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? +wrong?”

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

    @@ -1300,31 +1184,42 @@ 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. -

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

    +

    Account disabled

    “When I attempt to login to a Samba Domain from a NT4/W2K 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. -

    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 on the network who it is. This usually takes a while. -

    Chapter 6. Backup Domain Control

    John H. Terpstra

    Samba Team

    Volker Lendecke

    Samba Team

    Table of Contents

    Features And Benefits
    Essential Background Information
    MS Windows NT4 Style Domain Control
    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, what can I do?
    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?

    +

    Can not 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 can not be found, the other claiming that the + account does not exist in the domain or that the password is incorrect.

    This may be due to incompatible settings between + the Windows client and the Samba-3 server for schannel (secure channel) settings + or smb signing settings. Check your samba settings for + client schannel, server schannel, client signing, server signing by executing: + testparm -v | more and looking for the value of these parameters. +

    + Also use the Microsoft Management Console - Local Security Settings. This tool is available from the + Control Panel. The Policy settings are found in the Local Policies / Securty Options area and are prefixed by + Secure Channel: ..., and Digitally sign .... +

    + It is important that these be set consistently with the Samba-3 server settings. +


    [1] See also the chapter on Account Information Databases.

    [2] See also the chapter about network browsing

    Chapter 6. Backup Domain Control

    John H. Terpstra

    Samba Team

    Volker Lendecke

    Samba Team

    Table of Contents

    Features And Benefits
    Essential Background Information
    MS Windows NT4 Style Domain Control
    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, what can I do?
    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 in this section, please make sure that you are comfortable -with configuring a Samba Domain Controller as described in the -Domain Control chapter. -

    Features And Benefits

    +with configuring a Samba Domain Controller as described in chapter on setting up Samba as a PDC. +

    Features And Benefits

    This is one of the most difficult chapters to summarise. 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. Since this HOWTO is already so large and -extensive, we have taken the decision to provide sufficient (but not comprehensive) -information regarding Backup Domain Control. In the event that you should have a persistent -concern that is not addressed in this HOWTO document then please email +effectively using a totally different approach. In the event that you should have a persistent +concern that is not addressed in this book then 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 is capable of acting as a Backup Domain Controller to another Samba Primary Domain -Controller. A Samba-3 PDC can operate with an LDAP Account backend. The Samba-3 BDC can -operate with a slave LDAP server for the Account backend. This effectively gives samba a high -degree of scalability. This is a very sweet (nice) solution for large organisations. +Controller. 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 may still be able to log onto the network. +This effectively gives samba a high degree of scalability iand is a very sweet (nice) solution +for large organisations.

    While it is possible to run a Samba-3 BDC with non-LDAP backend, the administrator will need to figure out precisely what is the best way to replicate (copy / distribute) the @@ -1349,8 +1244,9 @@ lets consider each possible option and look at the pro's and con's for each theo

    Arguments Against: Complexity

  • - Passdb Backend is tdbsam based, BDCs use cron based "net rpc vampire" to - suck down the Accounts database from the PDC + Passdb Backend is tdbsam based, BDCs use cron based net rpc vampire to + obtain the Accounts database from the PDC and place them into the Samba SAM. + net rpc vampire is a Samba function of the "net" command.

    Arguments For: It would be a nice solution

    @@ -1371,7 +1267,7 @@ lets consider each possible option and look at the pro's and con's for each theo Arguments Against: All machine trust accounts and user accounts will be locally maintained. Domain users will NOT be able to roam from office to office. This is a broken and flawed solution. Do NOT do this. -

    • 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. @@ -1381,7 +1277,7 @@ and with it a new form of the network logon service that has extended functional 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 very complex array of services that are implemented over a complex 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 the username and password that the user entered are valid. If the information entered @@ -1439,32 +1335,29 @@ one of the BDCs can be promoted to a PDC. If this happens while the original PDC line then it is automatically demoted to a BDC. This is an important aspect of Domain Controller management. The tool that is used to affect a promotion or a demotion is the Server Manager for Domains. -

    Example PDC Configuration

    +

    Example PDC Configuration

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

    -	workgroup = SAMBA
-	domain master = yes
-	domain logons = yes
-

    -Several other things like a [homes] and a [netlogon] share also need to be set along with +

    Example 6.1. Minimal smb.conf for being a PDC

    workgroup = MIDEARTH
    domain master = yes
    domain logons = yes

    +Several other things like a [homes] and a +[netlogon] share also need to be set along with settings for the profile path, the users home drive, etc.. This will not be covered in this -chapter, for more information please refer to the chapter on Domain Control. -

    Active Directory Domain Control

    +chapter, for more information please refer to the chapter about samba as a PDC. +

    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 can not be an Active Directory server. This means that Samba-3 also can NOT act as a Backup Domain Controller 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 SAMBA has to register the NetBIOS group name SAMBA<#1c> with the WINS server and/or by broadcast on the local network. The PDC also registers the unique NetBIOS name SAMBA<#1b> with the WINS server. The name type <#1b> name is normally reserved for the Domain Master Browser, a role that has nothing to do with anything related to authentication, but the Microsoft Domain implementation requires the domain master browser to be on the same machine as the PDC. -

    How does a Workstation find its domain controller?

    +

    How does a Workstation find its domain controller?

    An MS Windows NT4 / 200x / XP Professional workstation in the domain SAMBA that wants a local user to be authenticated has to find the domain controller for SAMBA. It does this by doing a NetBIOS name query for the group name SAMBA<#1c>. It assumes that each @@ -1472,22 +1365,22 @@ 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. -

    Backup Domain Controller Configuration

    +

    Backup Domain Controller Configuration

    Several things have to be done:

    • The domain SID has to be the same on the PDC and the BDC. This used to be stored in the file private/MACHINE.SID. This file is not created - anymore since Samba 2.2.5 or even earlier. Nowadays the domain SID is - stored in the file private/secrets.tdb. Simply copying the secrets.tdb + since Samba 2.2.5. Nowadays the domain SID is stored in the file + private/secrets.tdb. Simply copying the secrets.tdb from the PDC to the BDC does not work, as the BDC would generate a new SID for itself and override the domain SID with this new BDC SID.

      To retrieve the domain SID from the PDC or an existing BDC and store it in the secrets.tdb, execute: 

      -	root# net rpc getsid
-

    • - The Unix user database has to be synchronized from the PDC to the +root# net rpc getsid +

    • + 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 to the BDC. This can be done manually whenever changes are made, or the PDC is set up as a NIS master @@ -1507,23 +1400,30 @@ Several things have to be done: BDC. This can be done manually whenever login scripts are changed, or it can be done automatically together with the smbpasswd synchronization. -

    Example Configuration

    +

    Example Configuration

    Finally, the BDC has to be found by the workstations. This can be done by setting: -

    -	workgroup = SAMBA
-	domain master = no
-	domain logons = yes
-

    -in the [global]-section of the smb.conf of the BDC. This makes the BDC +

    Example 6.2. Minimal setup for being a BDC

    workgroup = MIDEARTH
    domain master = no
    domain logons = yes
    idmap backend = ldapsam://slave-ldap.quenya.org

    +In the [global]-section of the smb.conf of the BDC. This makes the BDC only register the name SAMBA<#1c> with the WINS server. This is no problem as the name SAMBA<#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 SAMBA<#1b> which as a unique NetBIOS +be registered by more than one machine. The parameter +domain master = no +forces the BDC not to register SAMBA<#1b> which as a unique NetBIOS name is reserved for the Primary Domain Controller. -

    Common Errors

    +

    +The idmap backend will redirect the winbindd utility to +use the LDAP database to resolve all UIDs and GIDs for UNIX accounts. +

    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 of NT Domain User and Group +SIDs. One of the new facilities provides for explicitly ensuring that UNIX / Linux UID and GID values +will be consistent on the PDC, all BDCs and all Domain Member servers. The parameter that controls this +is called idmap backend. Please refer to the man page for smb.conf for more information +regarding it's behaviour. Do NOT set this parameter except where an LDAP backend (ldapsam) is in use. +

    Common Errors

    As this is a rather new area for Samba there are not many examples that we may refer to. Keep watching for updates to this section. -

    Machine Accounts keep expiring, what can I do?

    +

    Machine Accounts keep expiring, what can I do?

    This problem will occur when occur when the passdb (SAM) files are copied from a central server but the local Backup Domain Controllers. Local machine trust account password updates are not copied back to the central server. The newer machine account password is then over @@ -1534,18 +1434,15 @@ to proceed and the account expiry error will be reported.

    The solution: use a more robust passdb backend, such as the ldapsam backend, setting up an 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?

    With version 2.2, no. The native NT4 SAM replication protocols have not yet been fully implemented. The Samba Team is working on understanding and implementing the protocols, -but this work has not been finished for version 2.2. -

    -With version 3.0, the work on both the replication protocols and a suitable storage -mechanism has progressed, and some form of NT4 BDC support is expected soon. +but this work has not been finished for Samba-3.

    -Can I get the benefits of a BDC with Samba? Yes. The main reason for implementing a +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. @@ -1559,12 +1456,12 @@ 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 very 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 this will not occur often). -

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

    Table of Contents

    Features and Benefits
    MS Windows Workstation/Server Machine Trust Accounts
    Manual Creation of Machine Trust Accounts
    Using NT4 Server Manager to Add Machine Accounts to the Domain
    "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
    Setup your smb.conf
    Setup your /etc/krb5.conf
    Create the computer account
    Test your server setup
    Testing with smbclient
    Notes
    Common Errors
    Can Not Add Machine Back to Domain
    Adding Machine to Domain Fails

    +

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

    Table of Contents

    Features and Benefits
    MS Windows Workstation/Server Machine Trust Accounts
    Manual Creation of Machine Trust Accounts
    Using NT4 Server Manager to Add Machine Accounts to the Domain
    "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
    Setup your smb.conf
    Setup your /etc/krb5.conf
    Create the computer account
    Test your server setup
    Testing with smbclient
    Notes
    Common Errors
    Can Not Add Machine Back to Domain
    Adding Machine to Domain Fails

    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, @@ -1574,12 +1471,11 @@ This chapter covers background information pertaining to domain membership, 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 within the current MS Windows networking world and particularly in the -Unix/Linux networking and administration world, a considerable level of +UNIX/Linux networking and administration world, a considerable level of mis-information, incorrect understanding, and a lack of knowledge. Hopefully this chapter will fill the voids. -

    Features and Benefits

    -MS Windows workstations and servers that want to participate in domain -security need to +

    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 chapter describes the process that must be followed to make a workstation @@ -1614,11 +1510,11 @@ Domain membership has many advantages: client or server, other than the central Domain database (either NT4/Samba SAM style Domain, NT4 Domain that is back ended with an LDAP directory, or via an Active Directory infrastructure) -

    MS Windows Workstation/Server Machine Trust Accounts

    +

    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." +this is known as a "Computer Account."

    The password of a machine trust account acts as the shared secret for secure communication with the Domain Controller. This is a security @@ -1639,12 +1535,12 @@ as follows:

    • A Domain Security Account (stored in the - passdb backend that has been configured 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 - which contains the unix login ID, the Unix user identifier (UID), and the + which 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.

      @@ -1653,57 +1549,70 @@ as follows: older smbpasswd file did. The extra information enables new user account controls to be used.

    • - A corresponding Unix account, typically stored in + 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 + simplified mode of operation that does not require UNIX user accounts, but this may not be a feature of the early releases of Samba-3.

    -

    +

    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. + 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 so long as the user is logged on as the administrator account.

    • - "On-the-fly" creation. The Samba machine trust account is automatically + "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 + (For security, this is the recommended method.) The corresponding UNIX account may be created automatically or manually. -

    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. +create the corresponding UNIX account in /etc/passwd. This can be done using vipw or another 'add user' command -that is normally used to create new Unix accounts. The following is an example for a Linux based Samba server: -

    -root# /usr/sbin/useradd -g 100 -d /dev/null -c "machine nickname" -s /bin/false machine_name$ +that is normally used to create new UNIX accounts. The following is an example for a Linux based Samba server: + + + +

    +

    +root# /usr/sbin/useradd -g 100 -d /dev/null -c "machine nickname" \
+   -s /bin/false machine_name$ 
+
 root# passwd -l machine_name$
+

    + On *BSD systems, this can be done using the chpass utility:

    -root# chpass -a "machine_name$:*:101:100::0:0:Workstation machine_name:/dev/null:/sbin/nologin" +

    +root# chpass -a \
+  "machine_name$:*:101:100::0:0:Workstation machine_name:/dev/null:/sbin/nologin"
+

    The /etc/passwd entry will list the machine name -with a "$" appended, won't have a password, will have a null shell and no +with a "$" appended, won't have a password, will have a null shell and no home directory. For example a machine named 'doppy' would have an /etc/passwd entry like this: 

    -doppy$:x:505:501:machine_nickname:/dev/null:/bin/false
+doppy$:x:505:100:machine_nickname:/dev/null:/bin/false

    Above, machine_nickname can be any descriptive name for the client, i.e., BasementComputer. machine_name absolutely must be the NetBIOS -name of the client to be joined to the domain. The "$" must be +name of the client to be joined to the domain. The "$" must be appended to the NetBIOS name of the client or Samba will not recognize this as a machine trust account.

    -Now that the corresponding Unix account has been created, the next step is to create +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 smbpasswd(8) command +machine trust account password. This can be done using the +smbpasswd command as shown here: 

    @@ -1712,28 +1621,32 @@ as shown here:
 
    
 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.
+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 which the client joins the domain and 
 	changes the password, your domain is vulnerable to an intruder joining 
 	your domain using a machine with the same NetBIOS name.  A PDC inherently 
 	trusts members of the domain and will serve out a large degree of user 
 	information to such clients.  You have been warned!
-

    Using NT4 Server Manager to Add Machine Accounts to the Domain

    +

    Using NT4 Server Manager to Add Machine Accounts to the Domain

    If the machine from which you are trying to manage the domain is an -MS Windows NT4 workstation +MS Windows NT4 workstation or MS Windows 200x / XP Professional then the tool of choice is the package called SRVTOOLS.EXE. -When executed in the target directory this will unpack -SrvMge.exe and UsrMgr.exe (both are -Domain Management tools for MS Windows NT4 workstation. +When executed in the target directory this will unpack SrvMge.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 this will unpack the same tools but for use on +this platform.

    -If your workstation is any other MS Windows product you should download the -Nexus.exe package from the Microsoft web site. When executed -from the target directory this will unpack the same tools but for use on -MS Windows 9x/Me/200x/XP. +Further information about these tools may be obtained from the following locations: +http://support.microsoft.com/default.aspx?scid=kb;en-us;173673 +http://support.microsoft.com/default.aspx?scid=kb;en-us;172540

    Launch the srvmgr.exe (Server Manager for Domains) and follow these steps:

    Procedure 7.1. Server Manager Account Machine Account Management

    1. @@ -1753,25 +1666,21 @@ Launch the srvmgr.exe (Server Manager for Domains) and fo Add NT Workstation of Server, then enter the machine name in the field provided, then click the Add button. -

    "On-the-Fly" Creation of Machine Trust Accounts

    +

    "On-the-Fly" Creation of Machine Trust Accounts

    The second (and recommended) way of creating machine trust accounts is simply to allow the Samba server to create them as needed when the client is joined to the domain. -

    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 +

    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.

    Below is an example for a RedHat Linux system. -

    -[global]
-   # <...remainder of parameters...>
-   add machine script = /usr/sbin/useradd -d /dev/null -g 100 -s /bin/false -M %u 
-

    Making an MS Windows Workstation or Server a Domain Member

    +

    [global]
    # <...remainder of parameters...>
    add machine script = /usr/sbin/useradd -d /dev/null -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 of server a member of the domain varies with the version of Windows: -

    Windows 200x XP Professional

    +

    Windows 200x XP Professional

    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 administrative account (i.e., a Samba account that has root privileges on the @@ -1785,13 +1694,13 @@ with the version of Windows: The name of the account that is used to create domain member machine accounts can be anything the network administrator may choose. If it is other than root then this is easily mapped to root using the file pointed to be the smb.conf parameter - username map = /etc/samba/smbusers. + username map = /etc/samba/smbusers.

    The session key of the Samba administrative account acts as an encryption key for setting the password of the machine trust account. The machine trust account will be created on-the-fly, or updated if it already exists. -

    Windows NT4

    +

    Windows NT4

    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. @@ -1804,8 +1713,8 @@ with the version of Windows: Domain. In this case, joining the domain proceeds as above for Windows 2000 (i.e., you must supply a Samba administrative account when prompted). -

    Samba

    Joining a Samba client to a domain is documented in - the Domain Member Server section of this chapter chapter. +

    Samba

    Joining a Samba client to a domain is documented in + the domain member chapter.

    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 @@ -1821,46 +1730,38 @@ This can be LDAP (from OpenLDAP), or Sun's iPlanet, of NetWare Directory Server, etc.

    -Please refer to the Domain Control chapter +Please refer to the chapter on setting up a PDC for more information regarding how to create a domain machine account for a domain member server as well as for information regarding how to enable the Samba domain member machine to join the domain and to be fully trusted by it. -

    Joining an NT4 type Domain with Samba-3

    -

    Table 7.1. Assumptions

    NetBIOS name:SERV1
    Win2K/NT domain name:DOM
    Domain's PDC NetBIOS name:DOMPDC
    Domain's BDC NetBIOS names:DOMBDC1 and DOMBDC2

    +

    Joining an NT4 type Domain with Samba-3

    +

    Table 7.1. Assumptions

    NetBIOS name:SERV1
    Win2K/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 + Change (or add) your + security line in the [global] section of your smb.conf to read:

    -

    -security = domain
-

    +

    security = domain

    -Next change the -workgroup line in the [global] +Next change the workgroup line in the [global] section to read:

    -

    -workgroup = DOM
-

    +

    workgroup = MIDEARTH

    as this is the name of the domain we are joining.

    -You must also have the parameter -encrypt passwords set to yes +You must also have the parameter +encrypt passwords set to yes in order for your users to authenticate to the NT PDC.

    -Finally, add (or modify) a -password server line in the [global] +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 primary and backup domain controllers Samba will attempt to contact in order to authenticate users. Samba will @@ -1872,9 +1773,7 @@ Alternatively, if you want smbd to automatically determine 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. This method either broadcasts or uses a WINS database in order to @@ -1883,7 +1782,7 @@ find domain controllers to authenticate against. In order to actually join the domain, you must run this command: 

    -root# net join -S DOMPDC -UAdministrator%password
+root# net rpc join -S DOMPDC -UAdministrator%password

    If the -S DOMPDC argument is not given then @@ -1900,8 +1799,8 @@ you will see the message: Joined domain DOM. or Joined 'SERV1' to realm 'MYREALM'

    -in your terminal window. See the -net(8) man page for more details. +in your terminal window. See the +net man page for more details.

    This process joins the server to the domain without having to create the machine trust account on the PDC beforehand. @@ -1919,21 +1818,25 @@ 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! -

    Why is this better than security = server?

    +clients to begin using domain security! The way you can restart your +samba daemons depends on your distribution, but in most cases running +

    +	root# /etc/init.d/samba restart
+

    +does the job. +

    Why is this better than security = server?

    Currently, domain security in Samba doesn't free you from -having to create local Unix users to represent the users attaching +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 +to be a local UNIX user fred to represent that user in the UNIX filesystem. This is very similar to the older Samba security mode -security = server, +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 the Winbind chapter -for information on a system to automatically -assign UNIX uids and gids to Windows NT Domain users and groups. + Please refer to the chapter on winbind for information on a system +to automatically assign UNIX uids and gids to Windows NT Domain users and groups.

    The advantage to domain-level security is that the authentication in domain-level security is passed down the authenticated @@ -1943,11 +1846,11 @@ 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 +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 security = domain, +out of available connections. With security = domain, however, the Samba daemons connect to the PDC/BDC only for as long as is necessary to authenticate the user, and then drop the connection, thus conserving PDC connection resources. @@ -1961,41 +1864,39 @@ Much of the text of this document was first published in the Web magazine LinuxWorld as the article Doing the NIS/NT Samba. -

    Samba ADS Domain Membership

    +

    Samba ADS Domain Membership

    This is a rough guide to setting up Samba 3.0 with Kerberos authentication against a Windows2000 KDC. A familiarity with Kerberos is assumed. -

    Setup your smb.conf

    +

    Setup your smb.conf

    You must use at least the following 3 options in smb.conf: -

    -	realm = your.kerberos.REALM
-	security = ADS
-	encrypt passwords = yes
-

    +

    realm = your.kerberos.REALM
    security = ADS
    encrypt passwords = yes

    In case samba can't figure out your ads server using your realm name, use the -ads server option in smb.conf: -

    -	ads server = your.kerberos.server
-

    +ads server option in smb.conf: +

    ads server = your.kerberos.server

    Note

    You do not need a smbpasswd file, and older clients will be authenticated as -if security = domain, although it won't do any harm and +if security = domain, although it won't do any harm and allows you to have local users not in the domain. It is expected that the above required options will change soon when active directory integration will get better. -

    Setup your /etc/krb5.conf

    +

    Setup your /etc/krb5.conf

    The minimal configuration for krb5.conf is: 

    +[libdefaults]
+   default_realm = YOUR.KERBEROS.REALM
+
 	[realms]
-	    YOUR.KERBEROS.REALM = {
-		kdc = your.kerberos.server
+	YOUR.KERBEROS.REALM = {
+	kdc = your.kerberos.server
 	    }
-

    +

    Test your config by doing a kinit USERNAME@REALM and making sure that your password is accepted by the Win2000 KDC.

    Note

    The realm must be uppercase or you will get Cannot find KDC for -requested realm while getting initial credentials error. +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 @@ -2020,60 +1921,60 @@ is only needed if you want Kerberos support for smbd

    Create the computer account

    As a user that has write permission on the Samba private directory (usually root) run: -

    -	root# net join -U Administrator%password
+
    +root#  net ads join -U Administrator%password
 
    
-
    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 libs and headers are installed.
-	
    net join prompts for user name
    You need to login to the domain using kinit
+	
    net ads join prompts for user name
    You need to login to the domain using kinit
 	USERNAME@REALM.
 	USERNAME must be a user who has rights to add a machine
 	to the domain.  
    
 
    Test your 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"
+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 encoding type of DES-CBC-MD5 ? 
-
    Testing with smbclient
    
+
    Testing with smbclient
    
 On your Samba server try to login to a Win2000 server or your Samba
 server using smbclient and Kerberos. Use smbclient as usual, but
-specify the -k option to choose Kerberos authentication.
-
    Notes
    
+specify the -k option to choose Kerberos authentication.
+
    Notes
    
 You must change administrator password at least once after DC 
 install, to create the right encoding types
 
    
 W2k doesn't seem to create the _kerberos._udp and _ldap._tcp in
-their defaults DNS setup. Maybe fixed in service packs?
-

    Common Errors

    +their defaults DNS setup. Maybe this will be fixed later in service packs. +

    Common Errors

    In the process of adding / deleting / re-adding domain member machine accounts there are many traps for the unwary player and there are many “little” things that can go wrong. It is particularly interesting how often subscribers on the samba mailing list have concluded -after repeated failed attempts to add a machine account that it is necessary to "re-install" +after repeated failed attempts to add a machine account that it is necessary to "re-install" MS Windows on t he machine. In truth, it is seldom necessary to reinstall because of this type of problem. The real solution is often very simple, and with understanding of how MS Windows -networking functions. easily overcome. -

    Can Not Add Machine Back to Domain

    -Problem: A Windows workstation was reinstalled. The original domain machine +networking functions easy to overcome. +

    Can Not Add Machine Back to Domain

    +“ A Windows workstation was reinstalled. The original domain machine 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 doesn't. Why is this failing? +exists on the network - I know it doesn't. 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 to add the machine with a new name. -

    Adding Machine to Domain Fails

    -Adding a Windows 200x or XP Professional machine to the Samba PDC Domain fails with a +

    Adding Machine to Domain Fails

    + “Adding a Windows 200x or XP Professional machine to the Samba PDC Domain fails with a message that, The machine could not be added at this time, there is a network problem. -Please try again later. Why? + Please try again later. Why?”

    -You should check that there is an add machine script in your smb.conf +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 it's operation. Increase the log level +has been defined you will need to debug it's operation. Increase the log level in the smb.conf file to level 10, then try to rejoin the domain. Check the logs to see which operation is failing.

    @@ -2082,21 +1983,21 @@ Possible causes include: The script does not actually exist, or could not be located in the path specified.

    Corrective Action: Fix it. Make sure that when run manually - that the script will add both the Unix system account _and_ the Samba SAM account. + 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 + 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. ie: If the Unix utility useradd is called + Corrective Action: Check that the machine name is a legal UNIX + system account name. ie: 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 upper case characters nor will it allow spaces in the name. -

    • Chapter 8. Stand-Alone Servers

    John H. Terpstra

    Samba Team

    Table of Contents

    Features and Benefits
    Background
    Example Configuration
    Reference Documentation Server
    Central Print Serving
    Common Errors

    +

    Chapter 8. Stand-Alone Servers

    John H. Terpstra

    Samba Team

    Table of Contents

    Features and Benefits
    Background
    Example Configuration
    Reference Documentation Server
    Central Print Serving
    Common Errors

    Stand-Alone servers are independent of Domain Controllers on the network. They are NOT domain members and function more like workgroup servers. In many cases a stand-alone 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

    Stand-Alone 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 very common installation. @@ -2113,7 +2014,7 @@ that are queued off a single central server. Everyone needs to be able to print to the printers, there is no need to affect any access controls and no files will be served from the print server. Again a share mode stand-alone server makes a great solution. -

    Background

    +

    Background

    The term stand-alone server means that the server will provide local authentication and access control for all resources that are available from it. In general this means that there will be a @@ -2135,50 +2036,37 @@ local or on a remote server, even if from the Samba protocol perspective the Samba server is NOT a member of a domain security context.

    Through the use of PAM (Pluggable Authentication Modules) and nsswitch -(the name service switcher) the source of authentication may reside on +(the name service switcher, 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 +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 back end, or even via PAM and Winbind another CIFS/SMB server for authentication. -

    Example Configuration

    +

    Example Configuration

    The following examples 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

    +

    Reference Documentation Server

    Configuration of a read-only data server that EVERYONE can access is very simple. Here is the smb.conf file that will do this. Assume that all the reference documents are stored in the directory /export, that the documents are owned by a user other than nobody. No home directories are shared, that are no users in the /etc/passwd -Unix system database. This is a very simple system to administer. -

    -	# Global parameters
-	[global]
-		workgroup = MYGROUP
-		netbios name = REFDOCS
-		security = SHARE
-		passdb backend = guest
-		wins server = 192.168.1.1
-
-	[data]
-		comment = Data
-		path = /export
-		guest only = Yes
-

    +UNIX system database. This is a very simple system to administer. +

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

    In the above example the machine name is set to REFDOCS, the workgroup is set to the name of the local workgroup so that the machine will appear in with systems users are familiar -with. The only password backend required is the "guest" backend so as to allow default +with. The only password backend required is the "guest" backend so as to allow default unprivileged account names to be used. Given that there is a WINS server on this network we do use it. -

    Central Print Serving

    +

    Central Print Serving

    Configuration of a simple print server is very simple if you have all the right tools on your system.

    Assumptions:

    1. The print server must require no administration

    2. The print spooling and processing system on our print server will be CUPS. - (Please refer to the CUPS Printing chapter for more information). + (Please refer to the chapter about CUPS for more information).

    3. All printers that the print server will service will be network printers. They will be correctly configured, by the administrator, @@ -2192,76 +2080,67 @@ In this example our print server will spool all incoming print jobs to Samba to the CUPS print processor. Since all incoming connections will be as the anonymous (guest) user, two things will be required:

      Enabling Anonymous Printing

      • - The Unix/Linux system must have a guest account. + 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 following: - 

        -$ testparm -s -v | grep "guest account"
-

        +

        +$ testparm -s -v | grep "guest account"
+

        Then make sure that this account exists in your system password database (/etc/passwd).

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

        +
         root# mkdir /var/spool/samba
 root# chown nobody.nobody /var/spool/samba
 root# chmod a+rwt /var/spool/samba
-	
        
-

      -

      -	# Global parameters
-	[global]
-		workgroup = MYGROUP
-		netbios name = PTRSVR1
-		security = SHARE
-		passdb backend = guest
-		wins server = 192.168.1.1
-
-	[printers]
-		comment = All Printers
-		path = /var/spool/samba
-		printer admin = root
-		guest ok = Yes
-		printable = Yes
-		printing = cups
-		use client driver = Yes
-		browseable = No

      -

    Common Errors

    +

    +

    Example 8.2. smb.conf for anonymous printing

    # Global parameters
    [global]
    workgroup = MIDEARTH
    netbios name = GANDALF
    security = SHARE
    passdb backend = guest
    wins server = noldor
    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

    +

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

    Chapter 9. MS Windows Network Configuration Guide

    John H. Terpstra

    Samba Team

    Table of Contents

    Note

    Note

    +

    Chapter 9. MS Windows Network Configuration Guide

    John H. Terpstra

    Samba Team

    Table of Contents

    Note

    Note

    This chapter did not make it into this release. It is planned for the published release of this document. -

    Advanced Configuration

    Valuable Nuts and Bolts Information

    +

    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

    10. Samba / MS Windows Network Browsing Guide
    Features and Benefits
    What is Browsing?
    Discussion
    NetBIOS over TCP/IP
    TCP/IP - without NetBIOS
    DNS and Active Directory
    How Browsing Functions
    Setting up WORKGROUP Browsing
    Setting up DOMAIN Browsing
    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
    Setting up a WINS server
    WINS Replication
    Static WINS Entries
    Helpful Hints
    Windows Networking Protocols
    Name Resolution Order
    Technical Overview of browsing
    Browsing support in Samba
    Problem resolution
    Browsing across subnets
    Common Errors
    How can one flush the Samba NetBIOS name cache without restarting Samba?
    My client reports "This server is not configured to list shared resources"
    11. Account Information Databases
    Features and Benefits
    Technical Information
    Important Notes About Security
    Mapping User Identifiers between MS Windows and Unix
    Account Management Tools
    The smbpasswd Command
    The pdbedit Command
    Password Backends
    Plain Text
    smbpasswd - Encrypted Password Database
    tdbsam
    ldapsam
    MySQL
    XML
    Common Errors
    Users can not logon - Users not in Samba SAM
    Users are being added to the wrong backend database
    auth methods does not work
    12. Mapping MS Windows and Unix Groups
    Features and Benefits
    Discussion
    Example Configuration
    Configuration Scripts
    Sample smb.conf add group script
    Script to configure Group Mapping
    Common Errors
    Adding Groups Fails
    Adding MS Windows Groups to MS Windows Groups Fails
    13. 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
    Common Errors
    Users can not write to a public share
    I have set force user and Samba still makes root the owner of all the files - I touch!
    14. File and Record Locking
    Features and Benefits
    Discussion
    Opportunistic Locking Overview
    Samba Opportunistic Locking Control
    Example Configuration
    MS Windows Opportunistic Locking and Caching Controls
    Workstation Service Entries
    Server Service Entries
    Persistent Data Corruption
    Common Errors
    locking.tdb error messages
    Additional Reading
    15. 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 a IPC$ share deny
    NTLMv2 Security
    Upgrading Samba
    Common Errors
    Smbclient works on localhost, but the network is dead
    Why can users access home directories of other users?
    16. Interdomain Trust Relationships
    Features and Benefits
    Trust Relationship Background
    Native MS Windows NT4 Trusts Configuration
    NT4 as the Trusting Domain (ie. creating the trusted account)
    NT4 as the Trusted Domain (ie. creating trusted account's password)
    Configuring Samba NT-style Domain Trusts
    Samba-3 as the Trusting Domain
    Samba-3 as the Trusted Domain
    Common Errors
    Tell me about Trust Relationships using Samba
    17. Hosting a Microsoft Distributed File System tree on Samba
    Features and Benefits
    Common Errors
    18. Classical Printing Support
    Features and Benefits
    Technical Introduction
    What happens if you send a Job from a Client
    Printing Related Configuration Parameters
    Parameters Recommended for Use
    Parameters for Backwards Compatibility
    Parameters no longer in use
    A simple Configuration to Print with Samba-3
    Verification of "Settings in Use" with testparm
    A little Experiment to warn you
    Extended Sample Configuration to Print with Samba-3
    Detailed Explanation of the Example's Settings
    The [global] Section
    The [printers] Section
    Any [my_printer_name] Section
    Print Commands
    Default Print Commands for various Unix Print Subsystems
    Setting up your own Print Commands
    Innovations in Samba Printing since 2.2
    Client Drivers on Samba Server for Point'n'Print
    The [printer$] Section is removed from Samba-3
    Creating the [print$] Share
    Parameters in the [print$] Section
    Subdirectory Structure in [print$]
    Installing Drivers into [print$]
    Setting Drivers for existing Printers with a Client GUI
    Setting Drivers for existing Printers with -rpcclient
    "The Proof of the Pudding lies in the Eating" (Client Driver Install -Procedure)
    The first Client Driver Installation
    IMPORTANT! Setting Device Modes on new Printers
    Further Client Driver Install Procedures
    Always make first Client Connection as root or "printer admin"
    Other Gotchas
    Setting Default Print Options for the Client Drivers
    Supporting large Numbers of Printers
    Adding new Printers with the Windows NT APW
    Weird Error Message Cannot connect under a -different Name
    Be careful when assembling Driver Files
    Samba and Printer Ports
    Avoiding the most common Misconfigurations of the Client Driver
    The Imprints Toolset
    What is Imprints?
    Creating Printer Driver Packages
    The Imprints Server
    The Installation Client
    Add Network Printers at Logon without User Interaction
    The addprinter command
    Migration of "Classical" printing to Samba-3
    Publishing Printer Information in Active Directory or LDAP
    Common Errors and Problems
    I give my root password but I don't get access
    My printjobs get spooled into the spooling directory, but then get lost
    19. CUPS Printing Support in Samba 3.0
    Introduction
    Features and Benefits
    Overview
    Basic Configuration of CUPS support
    Linking of smbd with libcups.so
    Simple smb.conf Settings for CUPS
    More complex smb.conf Settings for -CUPS
    Advanced Configuration
    Central spooling vs. "Peer-to-Peer" printing
    CUPS/Samba as a "spooling-only" Print Server; "raw" printing -with Vendor Drivers on Windows Clients
    Driver Installation Methods on Windows Clients
    Explicitly enable "raw" printing for -application/octet-stream!
    Three familiar Methods for driver upload plus a new one
    Using CUPS/Samba in an advanced Way -- 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
    CUPS can use all 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
    Filter Requirements
    Prefilters
    pstops
    pstoraster
    imagetops and imagetoraster
    rasterto [printers specific]
    CUPS Backends
    cupsomatic/Foomatic -- how do they fit into the Picture?
    The Complete Picture
    mime.convs
    "Raw" printing
    "application/octet-stream" printing
    PostScript Printer Descriptions (PPDs) for non-PS Printers
    Difference between cupsomatic/foomatic-rip and -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 -- UNIX/Samba Print -Servers)
    From Windows Clients to a CUPS/Samba Print Server
    Samba receiving Jobfiles and passing them to CUPS
    Network PostScript RIP: CUPS Filters on Server -- clients use -PostScript Driver with CUPS-PPDs
    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
    Setting up CUPS for driver Download
    cupsaddsmb: the unknown Utility
    Prepare your smb.conf for -cupsaddsmb
    CUPS Package of "PostScript Driver for WinNT/2k/XP"
    Recognize the different Driver Files
    Acquiring the Adobe Driver Files
    ESP Print Pro Package of "PostScript Driver for -WinNT/2k/XP"
    Caveats to be considered
    What are the Benefits of using the "CUPS PostScript Driver for -Windows NT/2k/XP" as compared to the Adobe Driver?
    Run "cupsaddsmb" (quiet Mode)
    Run "cupsaddsmb" with verbose Output
    Understanding cupsaddsmb
    How to recognize if cupsaddsm 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
    What is required for adddriver and setdriver to succeed
    Manual Commandline Driver Installation in 15 little 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
    Auto-Deletion or Preservation of CUPS Spool Files
    CUPS Configuration Settings explained
    Pre-conditions
    Manual Configuration
    When not to use Samba to print to -CUPS
    In Case of Trouble.....
    Where to find Documentation
    How to ask for Help
    Where to find Help
    Appendix
    Printing from CUPS to Windows attached -Printers
    More CUPS filtering Chains
    Trouble Shooting Guidelines to fix typical Samba printing -Problems
    An Overview of the CUPS Printing Processes
    20. Stackable VFS modules
    Features and Benefits
    Discussion
    Included modules
    audit
    extd_audit
    fake_perms
    recycle
    netatalk
    VFS modules available elsewhere
    DatabaseFS
    vscan
    Common Errors
    21. Integrated Logon Support using Winbind
    Features and Benefits
    Introduction
    What Winbind Provides
    Target Uses
    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
    22. Advanced Network Management
    Features and Benefits
    Remote Server Administration
    Remote Desktop Management
    Remote Management from NoMachines.Com
    Network Logon Script Magic
    Adding printers without user intervention
    Common Errors
    23. 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
    Samba Editreg Toolset
    Windows NT4/200x
    Samba PDC
    System Startup and Logon Processing Overview
    Common Errors
    Policy Does Not Work
    24. Desktop Profile Management
    Features and Benefits
    Roaming Profiles
    Samba Configuration for Profile Handling
    Windows Client Profile Configuration Information
    Sharing Profiles between W9x/Me and NT4/200x/XP workstations
    Profile Migration from Windows NT4/200x Server to Samba
    Mandatory profiles
    Creating/Managing Group Profiles
    Default Profile for Windows Users
    MS Windows 9x/Me
    MS Windows NT4 Workstation
    MS Windows 200x/XP
    Common Errors
    How does one set up roaming profiles for just one (or a few) user/s or group/s?
    Can NOT use Roaming Profiles
    Changing the default profile
    25. 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
    26. 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
    My Boomerang Won't Come Back
    Very Slow Network Connections
    Samba server name change problem
    27. Unicode/Charsets
    Features and Benefits
    What are charsets and unicode?
    Samba and charsets
    Conversion from old names
    Japanese charsets
    28. Samba Backup Techniques
    Note
    Features and Benefits
    29. High Availability Options
    Note

    Chapter 10. Samba / MS Windows Network Browsing Guide

    John H. Terpstra

    Samba Team

    July 5, 1998

    Updated: April 21, 2003

    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
    Setting up WORKGROUP Browsing
    Setting up DOMAIN Browsing
    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
    Setting up a WINS server
    WINS Replication
    Static WINS Entries
    Helpful Hints
    Windows Networking Protocols
    Name Resolution Order
    Technical Overview of browsing
    Browsing support in Samba
    Problem resolution
    Browsing across subnets
    Common Errors
    How can one flush the Samba NetBIOS name cache without restarting Samba?
    My client reports "This server is not configured to list shared resources"

    +

    Table of Contents

    10. Samba / MS Windows Network Browsing Guide
    Features and Benefits
    What is Browsing?
    Discussion
    NetBIOS over TCP/IP
    TCP/IP - without NetBIOS
    DNS and Active Directory
    How Browsing Functions
    Setting up WORKGROUP Browsing
    Setting up DOMAIN Browsing
    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
    Setting up a WINS server
    WINS Replication
    Static WINS Entries
    Helpful Hints
    Windows Networking Protocols
    Name Resolution Order
    Technical Overview of browsing
    Browsing support in Samba
    Problem resolution
    Browsing across subnets
    Common Errors
    How can one flush the Samba NetBIOS name cache without restarting Samba?
    My client reports "This server is not configured to list shared resources"
    I get an Unable to browse the network error
    11. Account Information Databases
    Features and Benefits
    Backwards Compatibility Backends
    New Backends
    Technical Information
    Important Notes About Security
    Mapping User Identifiers between MS Windows and UNIX
    Mapping Common UIDs/GIDs on Distributed Machines
    Account Management Tools
    The smbpasswd Command
    The pdbedit Command
    Password Backends
    Plain Text
    smbpasswd - Encrypted Password Database
    tdbsam
    ldapsam
    MySQL
    XML
    Common Errors
    Users can not logon
    Users being added to wrong backend database
    auth methods does not work
    12. Mapping MS Windows and UNIX Groups
    Features and Benefits
    Discussion
    Example Configuration
    Configuration Scripts
    Sample smb.conf add group script
    Script to configure Group Mapping
    Common Errors
    Adding Groups Fails
    Adding MS Windows Groups to MS Windows Groups Fails
    Adding Domain Users to the Power Users group
    13. 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
    Common Errors
    Users can not write to a public share
    I have set force user but Samba still makes root the owner of all the files I touch!
    MS Word with Samba changes owner of file
    14. File and Record Locking
    Features and Benefits
    Discussion
    Opportunistic Locking Overview
    Samba Opportunistic Locking Control
    Example Configuration
    MS Windows Opportunistic Locking 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
    15. 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 a IPC$ share deny
    NTLMv2 Security
    Upgrading Samba
    Common Errors
    Smbclient works on localhost, but the network is dead
    Why can users access home directories of other users?
    16. 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
    Inter-Domain 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
    17. Hosting a Microsoft Distributed File System tree on Samba
    Features and Benefits
    Common Errors
    18. Classical Printing Support
    Features and Benefits
    Technical Introduction
    What happens if you send a Job from a Client
    Printing Related Configuration Parameters
    Parameters Recommended for Use
    A simple Configuration to Print
    Verification of "Settings in Use" with testparm
    A little Experiment to warn you
    Extended Sample Configuration to Print
    Detailed Explanation of the Example's Settings
    The [global] Section
    The [printers] Section
    Any [my_printer_name] Section
    Print Commands
    Default Print Commands for various UNIX Print Subsystems
    Setting up your own Print Commands
    Innovations in Samba Printing since 2.2
    Client Drivers on Samba Server for Point'n'Print
    The [printer$] Section is removed from Samba 3
    Creating the [print$] Share
    Parameters in the [print$] Section
    Subdirectory Structure in [print$]
    Installing Drivers into [print$]
    Setting Drivers for existing Printers with a Client GUI
    Setting Drivers for existing Printers with +rpcclient
    Client Driver Install Procedure
    The first Client Driver Installation
    IMPORTANT! Setting Device Modes on new Printers
    Further Client Driver Install Procedures
    Always make first Client Connection as root or "printer admin"
    Other Gotchas
    Setting Default Print Options for the Client Drivers
    Supporting large Numbers of Printers
    Adding new Printers with the Windows NT APW
    Weird Error Message Cannot connect under a +different Name
    Be careful when assembling Driver Files
    Samba and Printer Ports
    Avoiding the most common Misconfigurations of the Client Driver
    The Imprints Toolset
    What is Imprints?
    Creating Printer Driver Packages
    The Imprints Server
    The Installation Client
    Add Network Printers at Logon 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 don't get access
    My printjobs get spooled into the spooling directory, but then get lost
    19. CUPS Printing Support in Samba 3.0
    Introduction
    Features and Benefits
    Overview
    Basic Configuration of CUPS support
    Linking of smbd with libcups.so
    Simple smb.conf Settings for CUPS
    More complex smb.conf Settings for +CUPS
    Advanced Configuration
    Central spooling vs. "Peer-to-Peer" printing
    CUPS/Samba as a "spooling-only" Print Server; "raw" printing +with Vendor Drivers on Windows Clients
    Driver Installation Methods on Windows Clients
    Explicitly enable "raw" printing for +application/octet-stream!
    Three familiar Methods for driver upload plus a new one
    Using CUPS/Samba in an advanced Way -- 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
    CUPS can use all 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
    Filter Requirements
    Prefilters
    pstops
    pstoraster
    imagetops and imagetoraster
    rasterto [printers specific]
    CUPS Backends
    cupsomatic/Foomatic -- how do they fit into the Picture?
    The Complete Picture
    mime.convs
    "Raw" printing
    "application/octet-stream" printing
    PostScript Printer Descriptions (PPDs) for non-PS Printers
    Difference between cupsomatic/foomatic-rip and +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 -- UNIX/Samba Print +Servers)
    From Windows Clients to a CUPS/Samba Print Server
    Samba receiving Jobfiles and passing them to CUPS
    Network PostScript RIP: CUPS Filters on Server -- clients use +PostScript Driver with CUPS-PPDs
    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
    Setting up CUPS for driver Download
    cupsaddsmb: the unknown Utility
    Prepare your smb.conf for cupsaddsmb
    CUPS Package of "PostScript Driver for WinNT/2k/XP"
    Recognize the different Driver Files
    Acquiring the Adobe Driver Files
    ESP Print Pro Package of "PostScript Driver for +WinNT/2k/XP"
    Caveats to be considered
    Benefits of using "CUPS PostScript Driver for +Windows NT/2k/XP" instead of 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
    What is required 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
    Auto-Deletion or Preservation of CUPS Spool Files
    CUPS Configuration Settings explained
    Pre-conditions
    Manual Configuration
    In Case of Trouble.....
    Printing from CUPS to Windows attached +Printers
    More CUPS filtering Chains
    Common Errors
    Win9x client can't install driver
    "cupsaddsmb" keeps asking for root password in + neverending loop
    "cupsaddsmb" gives "No PPD file for printer..." + message while PPD file is present
    Client can't connect to Samba printer
    Can't reconnect to Samba under new account + from Win2K/XP
    Avoid being connected to the Samba server as the + "wrong" user
    Upgrading to CUPS drivers from Adobe drivers on + NT/2K/XP clients gives problems
    Can't use "cupsaddsmb" on Samba server which is + a PDC
    Deleted Win2K printer driver is still shown
    Win2K/XP "Local Security + Policies"
    WinXP clients: "Administrator can not install + printers for all local users"
    "Print Change Notify" functions on + NT-clients
    WinXP-SP1
    Print options for all users can't be set on Win2K/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
    Printer named "lp" +intermittently swallows jobs and spits out completely different +ones
    Location of Adobe PostScript driver files necessary for "cupsaddsmb"
    An Overview of the CUPS Printing Processes
    20. Stackable VFS modules
    Features and Benefits
    Discussion
    Included modules
    audit
    extd_audit
    fake_perms
    recycle
    netatalk
    VFS modules available elsewhere
    DatabaseFS
    vscan
    21. Winbind: Use of Domain Accounts
    Features and Benefits
    Introduction
    What Winbind Provides
    Target Uses
    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
    22. Advanced Network Management
    Features and Benefits
    Remote Server Administration
    Remote Desktop Management
    Remote Management from NoMachines.Com
    Network Logon Script Magic
    Adding printers without user intervention
    Common Errors
    23. 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
    Samba Editreg Toolset
    Windows NT4/200x
    Samba PDC
    System Startup and Logon Processing Overview
    Common Errors
    Policy Does Not Work
    24. Desktop Profile Management
    Features and Benefits
    Roaming Profiles
    Samba Configuration for Profile Handling
    Windows Client Profile Configuration Information
    Sharing Profiles between W9x/Me and NT4/200x/XP workstations
    Profile Migration from Windows NT4/200x Server to Samba
    Mandatory profiles
    Creating/Managing Group Profiles
    Default Profile for Windows Users
    MS Windows 9x/Me
    MS Windows NT4 Workstation
    MS Windows 200x/XP
    Common Errors
    Setting up roaming profiles for just a few user's or group's?
    Can NOT use Roaming Profiles
    Changing the default profile
    25. 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
    26. 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 in one way
    Very Slow Network Connections
    Samba server name change problem
    27. Unicode/Charsets
    Features and Benefits
    What are charsets and unicode?
    Samba and charsets
    Conversion from old names
    Japanese charsets
    Common errors
    CP850.so can't be found
    28. Samba Backup Techniques
    Note
    Features and Benefits
    29. High Availability Options
    Note

    Chapter 10. Samba / MS Windows Network Browsing Guide

    John H. Terpstra

    Samba Team

    Jelmer R. Vernooij

    The Samba Team

    July 5, 1998

    Updated: April 21, 2003

    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
    Setting up WORKGROUP Browsing
    Setting up DOMAIN Browsing
    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
    Setting up a WINS server
    WINS Replication
    Static WINS Entries
    Helpful Hints
    Windows Networking Protocols
    Name Resolution Order
    Technical Overview of browsing
    Browsing support in Samba
    Problem resolution
    Browsing across subnets
    Common Errors
    How can one flush the Samba NetBIOS name cache without restarting Samba?
    My client reports "This server is not configured to list shared resources"
    I get an Unable to browse the network error

    This document 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. WINS is @@ -2272,11 +2151,11 @@ over TCP/IP. Samba-3 and later also supports this mode of operation. When the use of NetBIOS over TCP/IP has been disabled then 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

    Someone once referred to the past in terms of: They were the worst of times, they were the best of times. The more we look back, them 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 @@ -2301,63 +2180,55 @@ help Samba to affect stable WINS operations beyond the normal scope of MS WINS.

    Please note that 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 turn off -support for NetBIOS, in which case WINS is of no relevance. Samba-3 supports this also. +support for NetBIOS, in which case WINS is of no relevance. Samba supports this also.

    For those networks on which NetBIOS has been disabled (ie: WINS is NOT required) the use of DNS is necessary for host name resolution. -

    What is Browsing?

    +

    What is Browsing?

    To most people browsing means that 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.

    What seems so simple is in fact a very complex interaction of different technologies. The technologies (or methods) employed in making all of this work includes: -

    MS Windows machines register their presence to the network
    Machines announce themselves to other machines on the network
    One or more machine on the network collates 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

    +

    • MS Windows machines register their presence to the network

    • Machines announce themselves to other machines on the network

    • One or more machine on the network collates 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: -

    -		
-	Browsing options:
-	-----------------
-		* os level
-		  lm announce
-		  lm interval
-		* preferred master
-		* local master
-		* domain master
-		  browse list
-		  enhanced browsing
-
-	Name Resolution Method:
-	-----------------------
-		* name resolve order
-
-	WINS options:
-	-------------
-		  dns proxy
-		  wins proxy
-		* wins server
-		* wins support
-		  wins hook
-

    +

    Browsing options: os level(*), + lm announce, + lm interval, + preferred master(*), + local master(*), + domain master(*), + browse list, + enhanced browsing. +

    Name Resolution Method: + name resolve order(*). +

    WINS options: + dns proxy, + wins proxy, + wins server(*), + wins support(*), + wins hook. +

    For Samba, the WINS Server and WINS Support are mutually exclusive options. Those marked with an '*' are the only options that commonly MAY need to be modified. Even if not one of these parameters is set nmbd will still do it's job. -

    Discussion

    +

    Discussion

    Firstly, all MS Windows networking uses SMB (Server Message Block) based messaging. SMB messaging may be implemented with or without NetBIOS. MS Windows 200x supports NetBIOS over TCP/IP for backwards compatibility. Microsoft is 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. MS Windows products can do likewise. NetBIOS based networking uses broadcast messaging to affect 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 +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 +remote browse sync parameter of smb.conf implements browse list collation using unicast UDP.

    Secondly, in those networks where Samba is the only SMB server technology, @@ -2365,12 +2236,13 @@ wherever possible nmbd should be configured on one (1) server. This makes it easy to manage the browsing environment. If each network segment is configured with it's 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 +remote announce and the remote browse sync parameters to your smb.conf file.

    + If only one WINS server is used for an entire multi-segment network then -the use of the remote announce and the -remote browse sync parameters should NOT be necessary. +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 @@ -2381,7 +2253,7 @@ 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 -remote browse sync and remote announce +remote browse sync and remote announce to affect browse list collation across all segments. Note that this means clients will only resolve local names, and must be configured to use DNS to resolve names on other subnets in order to resolve the IP addresses of the servers they can see @@ -2392,7 +2264,10 @@ 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 stabilise, particularly across network segments. -

    TCP/IP - without NetBIOS

    +

    TCP/IP - without NetBIOS

    + + + All TCP/IP using systems use various forms of host name resolution. The primary methods for TCP/IP hostname resolutions involves either a static file (/etc/hosts ) or DNS (the Domain Name System). DNS is the technology that makes @@ -2415,7 +2290,7 @@ it follows a defined path:

  • Looks up entries in LMHOSTS. It is located in C:\WinNT\System32\Drivers\etc. -

    • +

    Windows 200x / XP can register it's host name with a Dynamic DNS server. You can force register with a Dynamic DNS server in Windows 200x / XP using: ipconfig /registerdns @@ -2428,8 +2303,8 @@ consequently network services will be severely impaired. The use of Dynamic DNS is highly recommended with Active Directory, in which case the use of BIND9 is preferred for it's ability to adequately support the SRV (service) records that are needed for Active Directory. -

    DNS and Active Directory

    -Occasionally we hear from Unix network administrators who want to use a Unix based Dynamic +

    DNS and Active Directory

    +Occasionally we hear from UNIX network administrators who want to use a UNIX based Dynamic DNS server in place of the Microsoft DNS server. While this might be desirable to some, the MS Windows 200x DNS server is auto-configured to work with Active Directory. It is possible to use BIND version 8 or 9, but it will almost certainly be necessary to create service records @@ -2450,7 +2325,7 @@ The following are some of the default service records that Active Directory requ

  • _ldap._tcp.Site.gc.ms-dcs.DomainTree

    Used by MS Windows clients to locate site configuration dependent Global Catalog server. -

    • How Browsing Functions

    +

    How Browsing Functions

    MS Windows machines register their NetBIOS names (ie: the machine name for each service type in operation) on start up. The exact method by which this name registration @@ -2464,7 +2339,7 @@ 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). +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 @@ -2492,20 +2367,18 @@ 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 synchronisation -of browse lists across routed networks using the remote -browse sync parameter in the smb.conf file. +of browse lists across routed networks using the remote browse sync parameter in the smb.conf file. This causes Samba to contact the local master browser on a remote network and to request browse list synchronisation. This effectively bridges two networks that are separated by routers. The two remote networks may use either broadcast based name resolution or WINS -based name resolution, but it should be noted that the remote -browse sync parameter provides browse list synchronisation - and +based name resolution, but it should be noted that the remote browse sync parameter provides browse list synchronisation - and that is distinct from name to address resolution, in other words, 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. -

    Setting up WORKGROUP Browsing

    +

    Setting up WORKGROUP Browsing

    To set up cross subnet browsing on a network containing machines in up to be in a WORKGROUP, not an NT Domain you need to set up one Samba server to be the Domain Master Browser (note that this is *NOT* @@ -2524,20 +2397,13 @@ workgroup name. To set up a Samba server as a domain master browser, set the following option in the [global] section of the smb.conf file :

    -

    -	domain master = yes
-

    +

    domain master = yes

    -The domain master browser should also preferrably be the local master +The domain master browser should also preferably be the local master browser for its own subnet. In order to achieve this set the following options in the [global] section of the smb.conf file :

    -

    -	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 domain master browser may be the same machine as the WINS server, if you require. @@ -2551,20 +2417,15 @@ to use these). To make a Samba server a local master browser set the following options in the [global] section of the smb.conf file :

    -

    -	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 local master browser.

    -The local master parameter allows Samba to act as a -local master browser. The preferred master causes nmbd -to force a browser election on startup and the os level +The local master parameter allows Samba to act as a +local master browser. The preferred master causes nmbd +to force a browser election on startup and the os level parameter sets Samba high enough so that it should win any browser elections.

    If you have an NT machine on the subnet that you wish to @@ -2573,13 +2434,8 @@ becoming a local master browser by setting the following options in the [global] section of the smb.conf file :

    -

    -	domain master = no
-	local master = no
-	preferred master = no
-	os level = 0
-

    -

    Setting up DOMAIN Browsing

    +

    Example 10.3. smb.conf for not being a master browser

    [global]
    domain master = no
    local master = no
    preferred master = no
    os level = 0

    +

    Setting up DOMAIN Browsing

    If you are adding Samba servers to a Windows NT Domain then you must not set up a Samba server as a domain master browser. By default, a Windows NT Primary Domain Controller for a domain @@ -2591,18 +2447,13 @@ with WINS instead of the PDC. For subnets other than the one containing the Windows NT PDC you may set up Samba servers as local master browsers as described. To make a Samba server a local master browser set -the following options in the [global] section +the following options in the [global] section of the smb.conf file :

    -

    -	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 +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 local master browsers if they are running. For more details on this see the section @@ -2616,38 +2467,33 @@ ever becoming a local master browser by setting following options in the [global] section of the smb.conf file :

    -

    -        domain master = no
-        local master = no
-        preferred master = no
-        os level = 0
-

    +

    Example 10.5. smb.conf for not being a master browser

    [global]
    domain master = no
    local master = no
    preferred master = no
    os level = 0

    Forcing Samba to be the master

    -Who becomes the master browser is determined by an election +Who becomes the master browser is determined by an election process using broadcasts. Each election packet contains a number of parameters which determine what precedence (bias) a host should have in the election. By default Samba uses a very low precedence and thus loses elections to just about anyone else.

    -If you want Samba to win elections then just set the os level global +If you want Samba to win elections then just set the os level global option in smb.conf to a higher number. It defaults to 0. Using 34 would make it win all elections over every other system (except other samba systems!)

    -A os level of 2 would make it beat WfWg and Win95, but not MS Windows +A os level of 2 would make it beat WfWg and Win95, but not MS Windows NT/2K Server. A MS Windows NT/2K Server domain controller uses level 32.

    The maximum os level is 255

    If you want Samba to force an election on startup, then set the -preferred master global option in smb.conf to yes. Samba will +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, as if you have two hosts (whether they are Windows 95 or NT or -Samba) on the same local subnet both set with preferred master to +Samba) on the same local subnet both set with preferred master to yes, then periodically and continually they will force an election in order to become the local master browser.

    -If you want Samba to be a domain master browser, then it is -recommended that you also set preferred master to yes, because + If you want Samba to be a domain master browser, then it is +recommended that you also set preferred master to yes, because Samba will not become a domain master browser for the whole of your LAN or WAN if it is not also a local master browser on its own broadcast isolated subnet. @@ -2659,10 +2505,10 @@ attempt to become the domain master browser every 5 minutes. They will find that another Samba server is already the domain master browser and will fail. This provides automatic redundancy, should the current domain master browser fail. -

    Making Samba the domain master

    +

    Making Samba the domain master

    The domain master is responsible for collating the browse lists of multiple subnets so that browsing can occur between subnets. You can -make Samba act as the domain master by setting domain master = yes +make Samba act as the domain master by setting domain master = yes in smb.conf. By default it will not be a domain master.

    Note that you should not set Samba to be the domain master for a @@ -2674,8 +2520,8 @@ master browsers on other subnets and then contact them to synchronise browse lists.

    If you want Samba to be the domain master then I suggest you 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 +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.

    Note that all your servers (including Samba) and clients should be @@ -2701,31 +2547,31 @@ If, however, both Samba and your clients are using a WINS server, then: 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

    -If your network uses a "0" based broadcast address (for example if it +

    Note about broadcast addresses

    +If your network uses a "0" 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 0's broadcast and you will probably find that browsing and name lookups won't work. -

    Multiple interfaces

    +

    Multiple interfaces

    Samba now supports machines with multiple network interfaces. If you -have multiple interfaces then you will need to use the interfaces +have multiple interfaces then you will need to use the interfaces option in smb.conf to configure them. -

    Use of the Remote Announce parameter

    -The remote announce parameter of +

    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 = a.b.c.d [e.f.g.h] ...
-

    +The syntax of the remote announce parameter is: +

    remote announce = a.b.c.d [e.f.g.h] ...

    or -

    -	remote announce = a.b.c.d/WORKGROUP [e.f.g.h/WORKGROUP] ...
-

    +

    remote announce = a.b.c.d/WORKGROUP [e.f.g.h/WORKGROUP] ...

    where:

    a.b.c.d and -e.f.g.h

    is either the LMB (Local Master Browser) IP address +e.f.g.h

    + + + + is either the LMB (Local Master Browser) IP address or the broadcast address of the remote network. ie: the LMB is at 192.168.1.10, or the address could be given as 192.168.1.255 where the netmask @@ -2741,22 +2587,20 @@ 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

    -The remote browse sync parameter of +

    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 synchronise its NetBIOS name list with our Samba LMB. It 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: +The syntax of the remote browse sync parameter is: -

    -remote browse sync = a.b.c.d
-

    +

    remote browse sync = a.b.c.d

    where a.b.c.d is either the IP address of the remote LMB or else is 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. @@ -2797,36 +2641,34 @@ lookup attempts by other clients and will therefore cause workstation access errors.

    To configure Samba as a WINS server just add -wins support = yes to the smb.conf -file [globals] section. +wins support = yes to the smb.conf +file [global] section.

    To configure Samba to register with a WINS server just add -wins server = a.b.c.d to your smb.conf file [globals] section. +wins server = a.b.c.d to your smb.conf file [global] section.

    Important

    -Never use both wins support = yes together -with wins server = a.b.c.d +Never use both wins support = yes together +with wins server = a.b.c.d particularly not using it's own IP address. Specifying both will cause nmbd to refuse to start! -

    Setting up a WINS server

    +

    Setting up a WINS server

    Either a Samba machine or a Windows NT Server machine may be set up as a WINS server. To set a Samba machine to be a WINS server you must add the following option to the smb.conf file on the selected machine : -in the [globals] section add the line +in the [global] section add the line

    -

    -	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 least set the parameter to 'no' on all these machines.

    -Machines with wins support = yes will keep a list of +Machines with wins support = yes will keep a list of all NetBIOS names registered with them, acting as a DNS for NetBIOS names.

    You should set up only ONE WINS server. Do NOT set the -wins support = yes option on more than one Samba +wins support = yes option on more than one Samba server.

    To set up a Windows NT Server as a WINS server you need to set up @@ -2838,7 +2680,7 @@ participate in these replications. It is possible in the future that a Samba->Samba WINS replication protocol may be defined, in which case more than one Samba machine could be set up as a WINS server but currently only one Samba server should have the -wins support = yes parameter set. +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 @@ -2849,17 +2691,15 @@ in Windows 95 or Windows NT. 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.

    Note that this line MUST NOT BE SET in the smb.conf file of the Samba server acting as the WINS server itself. If you set both the -wins support = yes option and the -wins server = <name> option then +wins support = yes option and the +wins server = <name> option then nmbd will fail to start.

    There are two possible scenarios for setting up cross subnet browsing. @@ -2867,20 +2707,20 @@ The first details setting up cross subnet browsing on a network containing Windows 95, Samba and Windows NT 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 permits WINS replication through the use of the wrepld utility. This tool is not currently capable of being used as it is still in active development. As soon as this tool becomes moderately functional we will prepare man pages and enhance this section of the documentation to provide usage and technical details. -

    Static WINS Entries

    -Adding static entries to your Samba-3 WINS server is actually fairly easy. +

    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.

    Entries in wins.dat take the form of 

    -"NAME#TYPE" TTL ADDRESS+ FLAGS
+"NAME#TYPE" TTL ADDRESS+ FLAGS

    where NAME is the NetBIOS name, TYPE is the NetBIOS type, TTL is the @@ -2890,22 +2730,22 @@ flags for the registration.

    A typical dynamic entry looks like: 

    -"MADMAN#03" 1055298378 192.168.1.2 66R
+"MADMAN#03" 1055298378 192.168.1.2 66R

    To make it static, all that has to be done is set the TTL to 0: 

    -"MADMAN#03" 0 192.168.1.2 66R
+"MADMAN#03" 0 192.168.1.2 66R

    Though this method works with early Samba-3 versions, there's 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 as they are stumbling points for many new network administrators. -

    Windows Networking Protocols

    Warning

    +

    Windows Networking Protocols

    Warning

    Do NOT use more than one (1) protocol on MS Windows machines

    A very common cause of browsing problems results from installing more than @@ -2917,7 +2757,7 @@ of precedence for winning this election process. A machine running Samba or Windows NT will be biased so that the most suitable machine will predictably win and thus retain it's role.

    -The election process is "fought out" so to speak over every NetBIOS network +The election process is "fought out" so to speak over every NetBIOS network interface. In the case of a Windows 9x 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 machine is @@ -2935,34 +2775,27 @@ differently from MS Windows NT4. Generally, where a server does NOT support the newer or extended protocol, these will fall back to the NT4 protocols.

    The safest rule of all to follow it this - 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: is static and hard to maintain.
    Broadcast: uses UDP and can not resolve names across remote segments.

    +

    • WINS: the best tool!

    • LMHOSTS: is static and hard to maintain.

    • Broadcast: uses UDP and can not resolve names across remote segments.

    Alternative means of name resolution includes: -

    /etc/hosts: is static, hard to maintain, and lacks name_type info
    DNS: is a good choice but lacks essential name_type info.

    +

    • /etc/hosts: is static, hard to maintain, and lacks name_type info

    • DNS: is a good choice but lacks essential name_type info.

    Many sites want to restrict DNS lookups and want to 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
-

    +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

    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
-

    -where "host" refers the the native methods used by the Unix system +

    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, a so-called browse list. This list +of machines in a network, a so-called browse list. This list contains machines that are ready to offer file and/or print services to other machines within the network. Thus it does not include machines which aren't currently able to do server tasks. The browse @@ -2980,7 +2813,7 @@ 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 can NOT 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 a local browse master for a workgroup and the ability @@ -3007,15 +2840,15 @@ WINS server capabilities. In a Samba-only environment, it is recommended that you use one and only one Samba server as your WINS server.

    To get browsing to work you need to run nmbd as usual, but will need -to use the workgroup option in smb.conf +to 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 only used for 'unusual' purposes: announcements over the internet, for -example. See remote announce in the +example. See remote announce in the smb.conf man page. -

    Problem resolution

    +

    Problem resolution

    If something doesn't work then hopefully the log.nmbd file will help you track down the problem. Try a debug level of 2 or 3 for finding problems. Also note that the current browse list usually gets stored @@ -3026,7 +2859,7 @@ type the server name as \\SERVER in filemanager then hit enter and filemanager should display the list of available shares.

    Some people find browsing fails because they don't have the global -guest account set to a valid account. Remember that the +guest account set to a valid account. Remember that the IPC$ connection that lists the shares is done as guest, and thus you must have a valid guest account.

    @@ -3038,9 +2871,9 @@ name of the currently logged in user to query the IPC$ share. MS Windows server resources.

    The other big problem people have is that their broadcast address, -netmask or IP address is wrong (specified with the "interfaces" option +netmask or IP address is wrong (specified with the "interfaces" option in smb.conf) -

    Browsing across subnets

    +

    Browsing across subnets

    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. @@ -3061,32 +2894,14 @@ 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 Win95 and WinNT, this is in the TCP/IP Properties, under Network settings) for Samba this is in the smb.conf file. -

    How does cross subnet browsing work ?

    +

    How does cross subnet browsing work ?

    Cross subnet browsing is a complicated dance, containing multiple moving parts. It has taken Microsoft several years to get the code that achieves this correct, and Samba lags behind in some areas. Samba is capable of cross subnet browsing when configured correctly.

    -Consider a network set up as follows : -

    - -

    -                                   (DMB)
-             N1_A      N1_B        N1_C       N1_D        N1_E
-              |          |           |          |           |
-          -------------------------------------------------------
-            |          subnet 1                       |
-          +---+                                      +---+
-          |R1 | Router 1                  Router 2   |R2 |
-          +---+                                      +---+
-            |                                          |
-            |  subnet 2              subnet 3          |
-  --------------------------       ------------------------------------
-  |     |     |      |               |        |         |           |
- N2_A  N2_B  N2_C   N2_D           N3_A     N3_B      N3_C        N3_D 
-                    (WINS)
-

    -

    + Consider a network set up as in the diagram below. +

    Figure 10.1. Cross subnet browsing example

    Cross subnet browsing example

    Consisting of 3 subnets (1, 2, 3) connected by two routers (R1, R2) - these do not pass broadcasts. Subnet 1 has 5 machines on it, subnet 2 has 4 machines, subnet 3 has 4 machines. Assume @@ -3128,7 +2943,7 @@ At this point the browse lists look as follows (these are the machines you would see in your network neighborhood if you looked in it on a particular network right now).

    -

    Table 10.1. Browse subnet example 1

    SubnetBrowse MasterList
    Subnet1N1_CN1_A, N1_B, N1_C, N1_D, N1_E
    Subnet2N2_BN2_A, N2_B, N2_C, N2_D
    Subnet3N3_DN3_A, N3_B, N3_C, N3_D

    +

    Table 10.1. Browse subnet example 1

    SubnetBrowse MasterList
    Subnet1N1_CN1_A, N1_B, N1_C, N1_D, N1_E
    Subnet2N2_BN2_A, N2_B, N2_C, N2_D
    Subnet3N3_DN3_A, N3_B, N3_C, N3_D

    Note that at this point all the subnets are separate, no machine is seen across any of the subnets. @@ -3150,7 +2965,9 @@ the MasterAnnouncement packet it schedules a synchronization request to the sender of that packet. After both synchronizations are done the browse lists look like :

    -

    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

    +

    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 a (*) after them are non-authoritative names.

    @@ -3158,14 +2975,17 @@ 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 only see the servers on their own subnet.

    -The same sequence of events that occured for N2_B now occurs +The same sequence of events that occurred for N2_B now occurs for the local master browser on subnet 3 (N3_D). When it synchronizes browse lists with the domain master browser (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 look like.

    -

    Table 10.3. Browse subnet example 3

    SubnetBrowse MasterList
    Subnet1N1_CN1_A, N1_B, N1_C, N1_D, N1_E, N2_A(*), N2_B(*), N2_C(*), N2_D(*), N3_A(*), N3_B(*), N3_C(*), N3_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, N1_A(*), N1_B(*), N1_C(*), N1_D(*), N1_E(*), N2_A(*), N2_B(*), N2_C(*), N2_D(*)

    +

    Table 10.3. Browse subnet example 3

    SubnetBrowse MasterList
    Subnet1N1_CN1_A, N1_B, N1_C, N1_D, N1_E, +N2_A(*), N2_B(*), N2_C(*), N2_D(*), N3_A(*), N3_B(*), N3_C(*), N3_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, N1_A(*), +N1_B(*), N1_C(*), N1_D(*), N1_E(*), N2_A(*), N2_B(*), N2_C(*), N2_D(*)

    Servers with a (*) after them are non-authoritative names.

    @@ -3178,7 +2998,13 @@ with the domain master browser (N1_C) and will receive the missing server entries. Finally - and as a steady state (if no machines are removed or shut off) the browse lists will look like :

    -

    Table 10.4. Browse subnet example 4

    SubnetBrowse MasterList
    Subnet1N1_CN1_A, N1_B, N1_C, N1_D, N1_E, N2_A(*), N2_B(*), N2_C(*), N2_D(*), N3_A(*), N3_B(*), N3_C(*), N3_D(*)
    Subnet2N2_BN2_A, N2_B, N2_C, N2_D, N1_A(*), N1_B(*), N1_C(*), N1_D(*), N1_E(*), N3_A(*), N3_B(*), N3_C(*), N3_D(*)
    Subnet3N3_DN3_A, N3_B, N3_C, N3_D, N1_A(*), N1_B(*), N1_C(*), N1_D(*), N1_E(*), N2_A(*), N2_B(*), N2_C(*), N2_D(*)

    +

    Table 10.4. Browse subnet example 4

    SubnetBrowse MasterList
    Subnet1N1_CN1_A, N1_B, N1_C, N1_D, N1_E, +N2_A(*), N2_B(*), N2_C(*), N2_D(*), N3_A(*), N3_B(*), +N3_C(*), N3_D(*)
    Subnet2N2_BN2_A, N2_B, N2_C, N2_D, N1_A(*), +N1_B(*), N1_C(*), N1_D(*), N1_E(*), N3_A(*), N3_B(*), +N3_C(*), N3_D(*)
    Subnet3N3_DN3_A, N3_B, N3_C, N3_D, N1_A(*), +N1_B(*), N1_C(*), N1_D(*), N1_E(*), N2_A(*), N2_B(*), +N2_C(*), N2_D(*)

    Servers with a (*) after them are non-authoritative names.

    @@ -3199,11 +3025,11 @@ If either router R1 or R2 fails the following will occur: be able to access servers on its local subnet, by using subnet-isolated broadcast NetBIOS name resolution. The effects are 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 out of incorrect configuration of NetBIOS name resolution. Some are of particular note. -

    How can one flush the Samba NetBIOS name cache without restarting Samba?

    +

    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. Note that this does NOT make certain that a rogue machine name will not re-appear @@ -3213,33 +3039,37 @@ want to clear a rogue machine from the list then every machine on the network wi shut down and restarted at 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 (months). -

    My client reports "This server is not configured to list shared resources"

    +

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

    See also guest account in the smb.conf man page.

    Chapter 11. Account Information Databases

    Jelmer R. Vernooij

    The Samba Team

    Gerald (Jerry) Carter

    Samba Team

    Jeremy Allison

    Samba Team

    John H. Terpstra

    Samba Team

    Olivier (lem) Lemaire

    IDEALX

    May 24, 2003

    Table of Contents

    Features and Benefits
    Technical Information
    Important Notes About Security
    Mapping User Identifiers between MS Windows and Unix
    Account Management Tools
    The smbpasswd Command
    The pdbedit Command
    Password Backends
    Plain Text
    smbpasswd - Encrypted Password Database
    tdbsam
    ldapsam
    MySQL
    XML
    Common Errors
    Users can not logon - Users not in Samba SAM
    Users are being added to the wrong backend database
    auth methods does not work

    -Samba-3 implements a new capability to work concurrently with multiple account backends. -The possible new combinations of password backends allows Samba-3 a degree of flexibility +

    See also 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 local master browser. Configure nmbd + or any other machine to serve as local master browser.

    • You can not log onto the machine that is the local master + browser. Can you logon to it as guest user?

    • There is no IP connectivity to the local master browser. + Can you reach it by broadcast?

    Chapter 11. Account Information Databases

    Jelmer R. Vernooij

    The Samba Team

    Gerald (Jerry) Carter

    Samba Team

    Jeremy Allison

    Samba Team

    John H. Terpstra

    Samba Team

    Olivier (lem) Lemaire

    IDEALX

    May 24, 2003

    Table of Contents

    Features and Benefits
    Backwards Compatibility Backends
    New Backends
    Technical Information
    Important Notes About Security
    Mapping User Identifiers between MS Windows and UNIX
    Mapping Common UIDs/GIDs on Distributed Machines
    Account Management Tools
    The smbpasswd Command
    The pdbedit Command
    Password Backends
    Plain Text
    smbpasswd - Encrypted Password Database
    tdbsam
    ldapsam
    MySQL
    XML
    Common Errors
    Users can not logon
    Users being added to wrong backend database
    auth methods does not work

    +Samba 3 implements a new capability to work concurrently with multiple account backends. +The possible new combinations of password backends allows Samba 3 a degree of flexibility and scalability that previously could be achieved only with MS Windows Active Directory. This chapter describes the new functionality and how to get the most out of it.

    In the course of development of Samba-3, a number of requests were received to provide the ability to migrate MS Windows NT4 SAM accounts to Samba-3 without the need to provide -matching Unix/Linux accounts. We called this the Non Unix Accounts (NUA) +matching UNIX/Linux accounts. We called this the Non UNIX Accounts (NUA) capability. The intent was that an administrator could decide to use the tdbsam -backend and by simply specifying "passdb backend = tdbsam_nua, guest" -this would allow Samba-3 to implement a solution that did not use Unix accounts per se. Late +backend and by simply specifying passdb backend = tdbsam_nua +this would allow Samba-3 to implement a solution that did not use UNIX accounts per se. Late in the development cycle, the team doing this work hit upon some obstacles that prevents this solution from being used. Given the delays with Samba-3 release a decision was made to NOT deliver this functionality until a better method of recognising NT Group SIDs from NT User SIDs could be found. This feature may thus return during the life cycle for the Samba-3 series.

    Note

    -Samba-3.0.0 does NOT support Non-Unix Account (NUA) operation. -

    Features and Benefits

    +Samba-3 does NOT support Non-UNIX Account (NUA) operation for user accounts. +Samba-3 does support NUA operation for machine accounts. +

    Features and Benefits

    Samba-3 provides for complete backwards compatibility with Samba-2.2.x functionality as follows: -

    Backwards Compatibility Backends

    Plain Text:

    - This option uses nothing but the Unix/Linux /etc/passwd +

    Backwards Compatibility Backends

    Plain Text:

    + This option uses nothing but the UNIX/Linux /etc/passwd style back end. On systems that have PAM (Pluggable Authentication Modules) support all PAM modules are supported. The behaviour is just as it was with Samba-2.2.x, and the protocol limitations imposed by MS Windows clients @@ -3261,13 +3091,9 @@ as follows: This option is provided primarily as a migration tool, although there is no reason to force migration at this time. Note that this tool will eventually be deprecated. -

    +

    New Backends

    Samba-3 introduces the following new password backend capabilities: -

    New Backends

    guest:

    - This is always required as the last backend specified. - It provides the ability to handle guest account requirements for access to - resources like IPC$ which is used for browsing. -

    tdbsam:

    +

    tdbsam:

    This backend provides a rich database backend for local servers. This backend is NOT suitable for multiple domain controller (ie: PDC + one or more BDC) installations. @@ -3293,7 +3119,7 @@ Samba-3 introduces the following new password backend capabilities:

    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 + "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 to allow greater scalability.

    mysqlsam (MySQL based backend):

    @@ -3309,10 +3135,7 @@ Samba-3 introduces the following new password backend capabilities: The xmlsam option can be useful for account migration between database backends or backups. Use of this tool will allow the data to be edited before migration into another backend format. -

    nisplussam:

    - The NIS+ based passdb backend. Takes name NIS domain as an - optional argument. Only works with Sun NIS+ servers. -

    Technical Information

    +

    Technical Information

    Old windows clients send plain text passwords over the wire. Samba can check these passwords by crypting them and comparing them to the hash stored in the unix user database.

    @@ -3327,16 +3150,16 @@ Samba-3 introduces the following new password backend capabilities: In addition to differently encrypted passwords, windows also stores certain data for each user that is not stored in a unix user database. e.g: workstations the user may logon from, the location where the users' profile is stored, and so on. Samba retrieves and stores this - information using a passdb backend. Commonly available backends are LDAP, plain text + information using a passdb backend. Commonly available backends are LDAP, plain text file, MySQL and nisplus. For more information, see the man page for smb.conf regarding the - passdb backend parameter. -

    Important Notes About Security

    + passdb backend parameter. +

    Figure 11.1. IDMAP

    IDMAP

    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 never sends the cleartext password over the network but it does store the 16 byte hashed values on disk. This is also bad. Why? Because the 16 byte hashed values - are a "password equivalent". You cannot derive the user's password from them, but + are a "password equivalent". You cannot derive the user's password from them, but they could potentially be used in a modified client to gain access to a server. This would require considerable technical knowledge on behalf of the attacker but is perfectly possible. You should thus treat the data stored in whatever passdb @@ -3354,12 +3177,12 @@ Samba-3 introduces the following new password backend capabilities:

    The following versions of MS 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 [se]
    Windows Me

    Note

    +

    • MS DOS Network client 3.0 with the basic network redirector installed

    • Windows 95 with the network redirector update installed

    • Windows 98 [se]

    • Windows Me

    Note

    MS Windows XP Home does not have facilities to become a domain member and it can not 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

    +

    • Windows NT 3.5x

    • Windows NT 4.0

    • Windows 2000 Professional

    • Windows 200x Server/Advanced Server

    • Windows XP Professional

    All current release 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. @@ -3372,7 +3195,7 @@ Samba-3 introduces the following new password backend capabilities: (broken) only the cached (encrypted) password will be sent to the resource server to affect a 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

    • Plain text passwords are not passed across +

      Advantages of Encrypted Passwords

      • Plain text passwords are not passed across the network. Someone using a network sniffer cannot just record passwords going to the SMB server.

      • Plain text passwords are not stored anywhere in memory or on disk.

      • WinNT doesn't like talking to a server @@ -3383,32 +3206,44 @@ Samba-3 introduces the following new password backend capabilities: only things 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

      • Plain text passwords are not kept + operation.

      Advantages of non-encrypted passwords

      • Plain text passwords are not kept on disk, and are NOT cached in memory.

      • Uses same password file as other unix services such as login and ftp

      • Use of other services (such as telnet and ftp) which send plain text passwords over the net, so sending them for SMB - isn't such a big deal.

    Mapping User Identifiers between MS Windows and Unix

    - Every operation in Unix/Linux requires a user identifier (UID), just as in + isn't such a big deal.

    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. + two means for mapping an MS Windows user to a UNIX/Linux UID.

    Firstly, all Samba SAM (Security Account Manager database) accounts require - a Unix/Linux UID that the account will map to. As users are added to the account - information database, Samba-3 will call the add user script - interface to add the account to the Samba host OS. In essence, all accounts in + 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 affect Windows SID to Unix UID mapping is via the + The second way to affect Windows SID to UNIX UID mapping is via the idmap uid, 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 SAM server. -

    Account Management Tools

    -Samba-3 provides two (2) tools for management of User and machine accounts. These tools are +

    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 (eg: 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. Administrators should NOT set this + parameter except when an LDAP based passdb backend is in use. An example of use is: +

    +

    Example 11.1. 

    [global]
    idmap backend = ldapsam://ldap-server.quenya.org:636

    +

    Account Management Tools

    +Samba provides two (2) tools for management of User and machine accounts. These tools are called smbpasswd and pdbedit. A third tool is under development but is NOT expected to ship in time for Samba-3.0.0. The new tool will be a TCL/TK GUI tool that looks much like the MS Windows NT4 Domain User Manager - hopefully this will be announced in time for the Samba-3.0.1 release. -

    The smbpasswd Command

    +

    The smbpasswd Command

    The smbpasswd utility is a utility similar to the passwd or yppasswd programs. It maintains the two 32 byte password fields in the passdb backend. @@ -3422,19 +3257,19 @@ be announced in time for the Samba-3.0.1 release. 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

    +

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

    - 

    -		$ smbpasswd
-		Old SMB password: secret
-

    +

    +$ smbpasswd
+Old SMB password: secret
+

    For secret type old value here - or hit return if there was no old password - 

    -		New SMB Password: new secret
-		Repeat New SMB Password: new secret
-

    +

    +New SMB Password: new secret
+Repeat New SMB Password: new secret
+

    If the old value does not match the current value stored for that user, or the two new values do not match each other, then the password will not be changed. @@ -3454,10 +3289,10 @@ be announced in time for the Samba-3.0.1 release.

    For more details on using smbpasswd refer to the man page (the definitive reference). -

    The pdbedit Command

    +

    The pdbedit Command

    pdbedit is a tool that can be used only by root. It is used to manage the passdb backend. pdbedit can be used to: -

    add, remove or modify user accounts
    listing user accounts
    migrate user accounts

    +

    • add, remove or modify user accounts

    • listing user accounts

    • migrate user accounts

    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 super set of them. @@ -3469,50 +3304,60 @@ be announced in time for the Samba-3.0.1 release. The following is an example of the user account information that is stored in a tdbsam password backend. This listing was produced by running: 

    -		$ pdbedit -Lv met
-		Unix username:        met
-		NT username:
-		Account Flags:        [UX         ]
-		User SID:             S-1-5-21-1449123459-1407424037-3116680435-2004
-		Primary Group SID:    S-1-5-21-1449123459-1407424037-3116680435-1201
-		Full Name:            Melissa E Terpstra
-		Home Directory:       \\frodo\met\Win9Profile
-		HomeDir Drive:        H:
-		Logon Script:         scripts\logon.bat
-		Profile Path:         \\frodo\Profiles\met
-		Domain:               MIDEARTH
-		Account desc:
-		Workstations:         melbelle
-		Munged dial:
-		Logon time:           0
-		Logoff time:          Mon, 18 Jan 2038 20:14:07 GMT
-		Kickoff time:         Mon, 18 Jan 2038 20:14:07 GMT
-		Password last set:    Sat, 14 Dec 2002 14:37:03 GMT
-		Password can change:  Sat, 14 Dec 2002 14:37:03 GMT
-		Password must change: Mon, 18 Jan 2038 20:14:07 GMT
-

    Password Backends

    -Samba-3 offers the greatest flexibility in backend account database design of any SMB/CIFS server +$ pdbedit -Lv met +UNIX username: met +NT username: +Account Flags: [UX ] +User SID: S-1-5-21-1449123459-1407424037-3116680435-2004 +Primary Group SID: S-1-5-21-1449123459-1407424037-3116680435-1201 +Full Name: Melissa E Terpstra +Home Directory: \\frodo\met\Win9Profile +HomeDir Drive: H: +Logon Script: scripts\logon.bat +Profile Path: \\frodo\Profiles\met +Domain: MIDEARTH +Account desc: +Workstations: melbelle +Munged dial: +Logon time: 0 +Logoff time: Mon, 18 Jan 2038 20:14:07 GMT +Kickoff time: Mon, 18 Jan 2038 20:14:07 GMT +Password last set: Sat, 14 Dec 2002 14:37:03 GMT +Password can change: Sat, 14 Dec 2002 14:37:03 GMT +Password must change: Mon, 18 Jan 2038 20:14:07 GMT +

    + The pdbedit tool allows migration of authentication (account) + databases from one backend to another. For example: To migrate accounts from an + old smbpasswd database to a tdbsam + backend: +

    1. + Set the passdb backend = tdbsam, smbpasswd. +

    2. + Execute: +

      +root# pdbedit -i smbpassed -e tdbsam
+

      +

    3. + Now remove the smbpasswd from the passdb backend + configuration in smb.conf. +

    Password Backends

    +Samba offers the greatest flexibility in backend account database design of any SMB/CIFS server technology available today. The flexibility is immediately obvious as one begins to explore this capability.

    It is possible to specify not only multiple different password backends, but even multiple backends of the same type. For example, to use two different tdbsam databases:

    -

    -[globals]
-		passdb backend = tdbsam:/etc/samba/passdb.tdb, \
-		tdbsam:/etc/samba/old-passdb.tdb, guest
-

    -

    Plain Text

    +

    passdb backend = tdbsam:/etc/samba/passdb.tdb, tdbsam:/etc/samba/old-passdb.tdb

    +

    Plain Text

    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. eg: On Linux systems that is done via PAM. -

    smbpasswd - Encrypted Password Database

    - Traditionally, when configuring encrypt - passwords = yes in Samba's smb.conf file, user account +

    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 very large numbers of users (counted @@ -3538,10 +3383,10 @@ backends of the same type. For example, to use two different tdbsam databases: is commonly referred to as the samdb interface (previously this was called the passdb API, and is still so named in the Samba CVS trees).

    - Samba-3 provides an enhanced set of passdb backends that overcome the deficiencies + Samba provides an enhanced set of passdb backends that overcome the deficiencies of the smbpasswd plain text database. These are tdbsam, ldapsam, and xmlsam. Of these ldapsam will be of most interest to large corporate or enterprise sites. -

    tdbsam

    Samba can store user and machine account data in a "TDB" (Trivial Database). +

    tdbsam

    Samba can store user and machine account data in a "TDB" (Trivial Database). Using this backend doesn't require any additional configuration. This backend is recommended for new installations that do not require LDAP.

    @@ -3549,7 +3394,7 @@ backends of the same type. For example, to use two different tdbsam databases: that have 250 or more users. Additionally, tdbsam is not capable of scaling for use in sites that require PDB/BDC implementations that requires replication of the account database. Clearly, for reason of scalability, the use of ldapsam should be encouraged. -

    ldapsam

    +

    ldapsam

    There are a few points to stress that the ldapsam does not provide. The LDAP support referred to in the this documentation does not include:

    • A means of retrieving user account information from @@ -3557,8 +3402,8 @@ backends of the same type. For example, to use two different tdbsam databases: The second item can be accomplished by using LDAP NSS and PAM modules. LGPL versions of these libraries can be obtained from PADL Software (http://www.padl.com/). More - information about the configuration of these packages may be found at "LDAP, - System Administration; Gerald Carter, O'Reilly; Chapter 6: Replacing NIS". + information about the configuration of these packages may be found at "LDAP, + System Administration; Gerald Carter, O'Reilly; Chapter 6: Replacing NIS". Refer to http://safari.oreilly.com/?XmlId=1-56592-491-6 for those who might wish to know more about configuration and administration of an OpenLDAP server. @@ -3572,28 +3417,30 @@ backends of the same type. For example, to use two different tdbsam databases: and has a working directory server already installed. For more information on LDAP architectures and Directories, please refer to the following sites.

      + http://iplanet.netscape.com/directory

    Two additional Samba resources which 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 group in such a Samba-LDAP Domain Controller configuration. -

    Supported LDAP Servers

    +

    Supported LDAP Servers

    The LDAP ldapsam code has been developed and tested using the OpenLDAP 2.0 and 2.1 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 Bug reporting facility. -

    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.0 in examples/LDAP/samba.schema. The sambaSamAccount objectclass is given here: 

    -objectclass ( 1.3.6.1.4.1.7165.2.2.3 NAME 'sambaSamAccount' SUP top AUXILIARY
-    DESC 'Samba Auxiliary Account'
-    MUST ( uid $ rid )
-    MAY  ( cn $ lmPassword $ ntPassword $ pwdLastSet $ logonTime $
-           logoffTime $ kickoffTime $ pwdCanChange $ pwdMustChange $ acctFlags $
-           displayName $ smbHome $ homeDrive $ scriptPath $ profilePath $
-           description $ userWorkstations $ primaryGroupID $ domain ))
+objectclass ( 1.3.6.1.4.1.7165.2.2.6 NAME 'sambaSamAccount' SUP top AUXILIARY
+    DESC 'Samba 3.0 Auxiliary SAM Account'
+    MUST ( uid $ sambaSID )
+    MAY  ( cn $ sambaLMPassword $ sambaNTPassword $ sambaPwdLastSet $
+          sambaLogonTime $ sambaLogoffTime $ sambaKickoffTime $
+          sambaPwdCanChange $ sambaPwdMustChange $ sambaAcctFlags $
+          displayName $ sambaHomePath $ sambaHomeDrive $ sambaLogonScript $
+          sambaProfilePath $ description $ sambaUserWorkstations $
+          sambaPrimaryGroupSID $ sambaDomainName ))

    The samba.schema file has been formatted for OpenLDAP 2.0/2.1. @@ -3617,7 +3464,7 @@ objectclass ( 1.3.6.1.4.1.7165.2.2.3 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 @@ -3651,7 +3498,7 @@ include /etc/openldap/schema/nis.schema like in the following example, to speed up searches made on sambaSamAccount objectclasses (and possibly posixAccount and posixGroup as well).

    -

    +
     # Indices to maintain
 ## required by OpenLDAP
 index objectclass             eq
@@ -3678,7 +3525,7 @@ index   default               sub
 		Create the new index by executing:
 		
    
 
    -./sbin/slapindex -f slapd.conf
+root# ./sbin/slapindex -f slapd.conf
 
    
 
    
 		Remember to restart slapd after making these changes:
@@ -3686,34 +3533,34 @@ index   default               sub
 
     root# /etc/init.d/slapd restart
 
    
-

    Initialise the LDAP database

    +

    Initialise 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 (ie: Your DNS entries, etc.).

    -

    +
     # Organization for Samba Base
-dn: dc=plainjoe,dc=org
+dn: dc=quenya,dc=org
 objectclass: dcObject
 objectclass: organization
-dc: plainjoe
-o: Terpstra Org Network
+dc: quenya
+o: Quenya Org Network
 description: The Samba-3 Network LDAP Example
 
 # Organizational Role for Directory Management
-dn: cn=Manager,dc=plainjoe,dc=org
+dn: cn=Manager,dc=quenya,dc=org
 objectclass: organizationalRole
 cn: Manager
 description: Directory Manager
 
 # Setting up container for users
-dn: ou=People,dc=plainjoe,dc=org
+dn: ou=People,dc=quenya,dc=org
 objectclass: top
 objectclass: organizationalUnit
 ou: People
 
 # Setting up admin handle for People OU
-dn: cn=admin,ou=People,dc=plainjoe,dc=org
+dn: cn=admin,ou=People,dc=quenya,dc=org
 cn: admin
 objectclass: top
 objectclass: organizationalRole
@@ -3735,70 +3582,39 @@ userPassword: {SSHA}c3ZM9tBaBo9autm1dL3waDS21+JSfQVz
 		
    Note
    
 		Before Samba can access the LDAP server you need to store the LDAP admin password
 		into the Samba-3 secrets.tdb database by:
-		
    -root#  smbpasswd -w secret
-		
    
-

    Configuring Samba

    +

    +root# smbpasswd -w secret
+

    +

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

    +

    LDAP related smb.conf options: + passdb backend = ldapsam:url, + ldap ssl, + ldap admin dn, + ldap suffix, + ldap filter, + ldap machine suffix, + ldap user suffix, + ldap delete dn, + ldap passwd sync, + ldap trust ids. +

    These are described in the smb.conf man page and so will not be repeated here. However, a sample smb.conf file for use with an LDAP directory could appear as

    -

    -## /usr/local/samba/lib/smb.conf
-[global]
-     security = user
-     encrypt passwords = yes
-
-     netbios name = TASHTEGO
-     workgroup = NARNIA
-
-     # ldap related parameters
-
-     # define the DN to use when binding to the directory servers
-     # The password for this DN is not stored in smb.conf.  Rather it
-     # must be set by using 'smbpasswd -w secretpw' to store the
-     # passphrase in the secrets.tdb file.  If the "ldap admin dn" values
-     # change, this password will need to be reset.
-     ldap admin dn = "cn=Samba Manager,ou=people,dc=samba,dc=org"
-
-     # Define the SSL option when connecting to the directory
-     # ('off', 'start tls', or 'on' (default))
-     ldap ssl = start tls
-
-     # syntax: passdb backend = ldapsam:ldap://server-name[:port]
-     passdb backend = ldapsam:ldap://funball.samba.org, guest
-
-     # smbpasswd -x delete the entire dn-entry
-     ldap delete dn = no
-
-     # the machine and user suffix added to the base suffix
-     # wrote WITHOUT quotes. NULL suffixes by default
-     ldap user suffix = ou=People
-     ldap machine suffix = ou=Systems
-
-     # Trust unix account information in LDAP
-     #  (see the smb.conf manpage for details)
-     ldap trust ids = Yes
-
-     # specify the base DN to use when searching the directory
-     ldap suffix = "ou=people,dc=samba,dc=org"
-
-     # generally the default ldap search filter is ok
-     # ldap filter = "(&(uid=%u)(objectclass=sambaSamAccount))"
-

    -

    Accounts and Groups management

    +

    Example 11.2. Configuration with LDAP

    [global]
    security = user
    encrypt passwords = yes
    netbios name = TASHTEGO
    workgroup = NARNIA
    # ldap related parameters
    # define the DN to use when binding to the directory servers
    # The password for this DN is not stored in smb.conf. Rather it
    # must be set by using 'smbpasswd -w secretpw' to store the
    # passphrase in the secrets.tdb file. If the "ldap admin dn" values
    # change, this password will need to be reset.
    ldap admin dn = "cn=Samba Manager,ou=people,dc=samba,dc=org"
    # Define the SSL option when connecting to the directory
    # ('off', 'start tls', or 'on' (default))
    ldap ssl = start tls
    # syntax: passdb backend = ldapsam:ldap://server-name[:port]
    passdb backend = ldapsam:ldap://funball.samba.org
    # smbpasswd -x delete the entire dn-entry
    ldap delete dn = no
    # the machine and user suffix added to the base suffix
    # wrote WITHOUT quotes. NULL suffixes by default
    ldap user suffix = ou=People
    ldap machine suffix = ou=Systems
    # Trust unix account information in LDAP
    # (see the smb.conf manpage for details)
    ldap trust ids = Yes
    # specify the base DN to use when searching the directory
    ldap suffix = "ou=people,dc=samba,dc=org"
    # generally the default ldap search filter is ok
    ldap filter = "(&(uid=%u)(objectclass=sambaSamAccount))"

    +

    Accounts and Groups management

    As users accounts are managed through the sambaSamAccount objectclass, you should modify your existing administration tools to deal with sambaSamAccount attributes.

    Machines accounts are managed with the sambaSamAccount objectclass, just like users accounts. However, it's up to you to store those accounts in a different tree of your LDAP namespace: you should use - "ou=Groups,dc=plainjoe,dc=org" to store groups and - "ou=People,dc=plainjoe,dc=org" to store users. Just configure your + "ou=Groups,dc=quenya,dc=org" to store groups and + "ou=People,dc=quenya,dc=org" to store users. Just configure your NSS and PAM accordingly (usually, in the /etc/ldap.conf configuration file).

    @@ -3806,7 +3622,7 @@ userPassword: {SSHA}c3ZM9tBaBo9autm1dL3waDS21+JSfQVz 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). -

    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 lmPassword or @@ -3817,13 +3633,13 @@ userPassword: {SSHA}c3ZM9tBaBo9autm1dL3waDS21+JSfQVz on the details of LM/NT password hashes, refer to the Account Information Database section of this chapter.

      - To remedy the first security issue, the ldap ssl smb.conf parameter defaults - to require an encrypted session (ldap ssl = on) using + 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 is possible to use the use the StartTLS LDAP extended operation in the place of LDAPS. In either case, you are strongly discouraged to disable this security - (ldap ssl = off). + (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 @@ -3834,86 +3650,85 @@ userPassword: {SSHA}c3ZM9tBaBo9autm1dL3waDS21+JSfQVz following ACL in slapd.conf: 

      -## allow the "ldap admin dn" access, but deny everyone else
+## allow the "ldap admin dn" access, but deny everyone else
 access to attrs=lmPassword,ntPassword
-     by dn="cn=Samba Admin,ou=people,dc=plainjoe,dc=org" write
+     by dn="cn=Samba Admin,ou=people,dc=quenya,dc=org" write
      by * none

      -

    LDAP special attributes for sambaSamAccounts

    +

    LDAP special attributes for sambaSamAccounts

    The sambaSamAccount objectclass is composed of the following attributes:

    -

    Table 11.1. Attributes in the sambaSamAccount objectclass (LDAP)

    lmPasswordthe LANMAN password 16-byte hash stored as a character - representation of a hexadecimal string.
    ntPasswordthe NT password hash 16-byte stored as a character - representation of a hexadecimal string.
    pwdLastSetThe integer time in seconds since 1970 when the - lmPassword and ntPassword attributes were last set. -
    acctFlagsstring of 11 characters surrounded by square brackets [] +

    Table 11.1. Attributes in the sambaSamAccount objectclass (LDAP)

    sambaLMPasswordthe LANMAN password 16-byte hash stored as a character +representation of a hexadecimal string.
    sambaNTPasswordthe NT password hash 16-byte stored as a character + representation of a hexadecimal string.
    sambaPwdLastSetThe integer time in seconds since 1970 when the + sambaLMPassword and sambaNTPassword attributes were last set. +
    sambaAcctFlagsstring of 11 characters surrounded by square brackets [] representing account flags such as U (user), W(workstation), X(no password expiration), I(Domain trust account), H(Home dir required), S(Server trust account), - and D(disabled).
    logonTimeInteger value currently unused
    logoffTimeInteger value currently unused
    kickoffTimeInteger value currently unused
    pwdCanChangeInteger value currently unused
    pwdMustChangeInteger value currently unused
    homeDrivespecifies the drive letter to which to map the - UNC path specified by homeDirectory. The drive letter must be specified in the form "X:" - where X is the letter of the drive to map. Refer to the "logon drive" parameter in the - smb.conf(5) man page for more information.
    scriptPathThe scriptPath property specifies the path of + and D(disabled).
    sambaLogonTimeInteger value currently unused
    sambaLogoffTimeInteger value currently unused
    sambaKickoffTimeInteger value currently unused
    sambaPwdCanChangeInteger value currently unused
    sambaPwdMustChangeInteger value currently unused
    sambaHomeDrivespecifies the drive letter to which to map the + UNC path specified by sambaHomePath. The drive letter must be specified in the form "X:" + where X is the letter of the drive to map. Refer to the "logon drive" parameter in the + smb.conf(5) man page for more information.
    sambaLogonScriptThe sambaLogonScript property specifies the path of the user's logon script, .CMD, .EXE, or .BAT file. The string can be null. The path - is relative to the netlogon share. Refer to the "logon script" parameter in the - smb.conf(5) man page for more information.
    profilePathspecifies a path to the user's profile. + is relative to the netlogon share. Refer to the logon script parameter in the + smb.conf man page for more information.
    sambaProfilePathspecifies a path to the user's profile. This value can be a null string, a local absolute path, or a UNC path. Refer to the - "logon path" parameter in the smb.conf(5) man page for more information.
    smbHomeThe homeDirectory property specifies the path of - the home directory for the user. The string can be null. If homeDrive is set and specifies - a drive letter, homeDirectory should be a UNC path. The path must be a network - UNC path of the form \\server\share\directory. This value can be a null string. - Refer to the logon home parameter in the smb.conf man page for more information. -
    userWorkstationcharacter string value currently unused. -
    ridthe integer representation of the user's relative identifier - (RID).
    primaryGroupIDthe relative identifier (RID) of the primary group - of the user.
    domaindomain the user is part of.

    + logon path parameter in the smb.conf man page for more information.

    sambaHomePathThe sambaHomePath property specifies the path of +the home directory for the user. The string can be null. If sambaHomeDrive is set and specifies +a drive letter, sambaHomePath should be a UNC path. The path must be a network +UNC path of the form \\server\share\directory. This value can be a null string. +Refer to the logon home parameter in the smb.conf man page for more information. +
    sambaUserWorkstationscharacter string value currently unused. +
    sambaSIDThe security identifier(SID) of the user. The windows equivalent of unix uid's.
    sambaPrimaryGroupSIDthe relative identifier (RID) 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 the Samba as a primary domain controller chapter for details on how to configure Samba as a Primary Domain Controller). The following four attributes are only stored with the sambaSamAccount entry if the values are non-default values: -

    smbHome
    scriptPath
    logonPath
    homeDrive

    +

    • sambaHomePath

    • sambaLogonScript

    • sambaProfilePath

    • sambaHomeDrive

    These attributes are only stored with the sambaSamAccount entry if the values are non-default values. For example, assume TASHTEGO has now been - configured as a PDC and that logon home = \\%L\%u was defined in - its smb.conf file. When a user named "becky" logons to the domain, - the logon home string is expanded to \\TASHTEGO\becky. - If the smbHome attribute exists in the entry "uid=becky,ou=people,dc=samba,dc=org", + configured as a PDC and that logon home = \\%L\%u was defined in + its smb.conf file. When a user named "becky" logons to the domain, + the logon home string is expanded to \\TASHTEGO\becky. + If the smbHome attribute exists in the entry "uid=becky,ou=people,dc=samba,dc=org", this value is used. However, if this attribute does not exist, then the value - of the logon home parameter is used in its place. Samba + 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 with the inclusion of the posixAccount objectclass: 

    -	dn: uid=guest2, ou=people,dc=plainjoe,dc=org
-	ntPassword: 878D8014606CDA29677A44EFA1353FC7
-	pwdMustChange: 2147483647
-	primaryGroupID: 1201
-	lmPassword: 552902031BEDE9EFAAD3B435B51404EE
-	pwdLastSet: 1010179124
-	logonTime: 0
+	dn: uid=guest2, ou=people,dc=quenya,dc=org
+	sambaNTPassword: 878D8014606CDA29677A44EFA1353FC7
+	sambaPwdMustChange: 2147483647
+	sambaPrimaryGroupSID: S-1-5-21-2447931902-1787058256-3961074038-513
+	sambaNTPassword: 552902031BEDE9EFAAD3B435B51404EE
+	sambaPwdLastSet: 1010179124
+	sambaLogonTime: 0
 	objectClass: sambaSamAccount
 	uid: guest2
-	kickoffTime: 2147483647
-	acctFlags: [UX         ]
-	logoffTime: 2147483647
-	rid: 19006
-	pwdCanChange: 0
+	sambaKickoffTime: 2147483647
+	sambaAcctFlags: [UX         ]
+	sambaLogoffTime: 2147483647
+	sambaSID: S-1-5-21-2447931902-1787058256-3961074038-5006
+	sambaPwdCanChange: 0

    The following is an LDIF entry for using both the sambaSamAccount and posixAccount objectclasses: 

    -	dn: uid=gcarter, ou=people,dc=plainjoe,dc=org
-	logonTime: 0
+	dn: uid=gcarter, ou=people,dc=quenya,dc=org
+	sambaLogonTime: 0
 	displayName: Gerald Carter
-	lmPassword: 552902031BEDE9EFAAD3B435B51404EE
-	primaryGroupID: 1201
+	sambaLMPassword: 552902031BEDE9EFAAD3B435B51404EE
+	sambaPrimaryGroupSID: S-1-5-21-2447931902-1787058256-3961074038-1201
 	objectClass: posixAccount
 	objectClass: sambaSamAccount
-	acctFlags: [UX         ]
+	sambaAcctFlags: [UX         ]
 	userPassword: {crypt}BpM2ej8Rkzogo
 	uid: gcarter
 	uidNumber: 9000
@@ -3921,60 +3736,59 @@ access to attrs=lmPassword,ntPassword
 	loginShell: /bin/bash
 	logoffTime: 2147483647
 	gidNumber: 100
-	kickoffTime: 2147483647
-	pwdLastSet: 1010179230
-	rid: 19000
+	sambaKickoffTime: 2147483647
+	sambaPwdLastSet: 1010179230
+	sambaSID: S-1-5-21-2447931902-1787058256-3961074038-5004
 	homeDirectory: /home/tashtego/gcarter
-	pwdCanChange: 0
-	pwdMustChange: 2147483647
-	ntPassword: 878D8014606CDA29677A44EFA1353FC7
+	sambaPwdCanChange: 0
+	sambaPwdMustChange: 2147483647
+	sambaNTPassword: 878D8014606CDA29677A44EFA1353FC7

    -

    Password synchronisation

    +

    Password synchronisation

    Since version 3.0 samba 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 following values:

    yes

    When the user changes his password, update +

    The ldap passwd sync options can have the following values:

    yes

    When the user changes his password, update ntPassword, lmPassword - and the password fields.

    no

    Only update ntPassword and lmPassword.

    only

    Only update the LDAP password and let the LDAP server worry - about the other fields. This option is only available when the LDAP server supports LDAP_EXOP_X_MODIFY_PASSWD.

    More information can be found in the smb.conf manpage. -

    MySQL

    + and the password fields.

    no

    Only update ntPassword and lmPassword.

    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. [3]

    More information can be found in the smb.conf manpage. +

    MySQL

    Every so often someone will come along with a great new idea. Storing of user accounts in an SQL backend is one of them. Those who want to do this are in the best position to know what the specific benefits are to them. This may sound like a cop-out, but in truth we can not attempt to document every nitty little detail why certain things of marginal utility to the bulk of Samba users might make sense to the rest. In any case, the following instructions should help the determined SQL user to implement a working system. -

    Creating the database

    +

    Creating the database

    You either can set up your own table and specify the field names to pdb_mysql (see below for the column names) or use the default table. The file examples/pdb/mysql/mysql.dump contains the correct queries to create the required tables. Use the command : - 

    $ mysql -uusername -hhostname -ppassword \
-databasename < /path/to/samba/examples/pdb/mysql/mysql.dump

    -

    Configuring

    This plugin lacks some good documentation, but here is some short info:

    Add a the following to the passdb backend variable in your smb.conf: - 

    -			passdb backend = [other-plugins] mysql:identifier [other-plugins]
-

    +

    +$ mysql -uusername -hhostname -ppassword \
+databasename < /path/to/samba/examples/pdb/mysql/mysql.dump
+

    +

    Configuring

    This plugin lacks some good documentation, but here is some short info:

    Add a the following to the passdb backend variable in your smb.conf: +

    passdb backend = [other-plugins] mysql:identifier [other-plugins]

    The identifier can be any string you like, as long as it doesn't collide with the identifiers of other plugins or other instances of pdb_mysql. If you - specify multiple pdb_mysql.so entries in passdb backend, you also need to + specify multiple pdb_mysql.so entries in passdb backend, you also need to use different identifiers!

    Additional options can be given through the smb.conf file in the [global] section.

    -

    Table 11.2. Basic smb.conf options for MySQL passdb backend

    FieldContents
    identifier:mysql hosthost name, defaults to 'localhost'
    identifier:mysql password 
    identifier:mysql userdefaults to 'samba'
    identifier:mysql databasedefaults to 'samba'
    identifier:mysql portdefaults to 3306
    identifier:tableName of the table containing users

    +

    Table 11.2. Basic smb.conf options for MySQL passdb backend

    FieldContents
    mysql hosthost name, defaults to 'localhost'
    mysql password 
    mysql userdefaults to 'samba'
    mysql databasedefaults to 'samba'
    mysql portdefaults to 3306
    tableName of the table containing users

    Warning

    Since the password for the MySQL user is stored in the - smb.conf file, you should make the the smb.conf file + smb.conf file, you should make the smb.conf file readable only to the user that runs Samba This is considered a security bug and will be fixed soon.

    Names of the columns in this table (I've added column types those columns should have first):

    -

    Table 11.3. MySQL field names for MySQL passdb backend

    FieldTypeContents
    identifier:logon time columnint(9) 
    identifier:logoff time columnint(9) 
    identifier:kickoff time columnint(9) 
    identifier:pass last set time columnint(9) 
    identifier:pass can change time columnint(9) 
    identifier:pass must change time columnint(9) 
    identifier:username columnvarchar(255)unix username
    identifier:domain columnvarchar(255)NT domain user is part of
    identifier:nt username columnvarchar(255)NT username
    identifier:fullname columnvarchar(255)Full name of user
    identifier:home dir columnvarchar(255)Unix homedir path
    identifier:dir drive columnvarchar(2)Directory drive path (eg: 'H:')
    identifier:logon script columnvarchar(255)Batch file to run on client side when logging on
    identifier:profile path columnvarchar(255)Path of profile
    identifier:acct desc columnvarchar(255)Some ASCII NT user data
    identifier:workstations columnvarchar(255)Workstations user can logon to (or NULL for all)
    identifier:unknown string columnvarchar(255)unknown string
    identifier:munged dial columnvarchar(255)?
    identifier:user sid columnvarchar(255)NT user SID
    identifier:group sid columnvarchar(255)NT group ID
    identifier:lanman pass columnvarchar(255)encrypted lanman password
    identifier:nt pass columnvarchar(255)encrypted nt passwd
    identifier:plain pass columnvarchar(255)plaintext password
    identifier:acct control columnint(9)nt user data
    identifier:unknown 3 columnint(9)unknown
    identifier:logon divs columnint(9)?
    identifier:hours len columnint(9)?
    identifier:unknown 5 columnint(9)unknown
    identifier:unknown 6 columnint(9)unknown

    +

    Table 11.3. MySQL field names for MySQL passdb backend

    FieldTypeContents
    logon time columnint(9) 
    logoff time columnint(9) 
    kickoff time columnint(9) 
    pass last set time columnint(9) 
    pass can change time columnint(9) 
    pass must change time columnint(9) 
    username columnvarchar(255)unix username
    domain columnvarchar(255)NT domain user is part of
    nt username columnvarchar(255)NT username
    fullname columnvarchar(255)Full name of user
    home dir columnvarchar(255)UNIX homedir path
    dir drive columnvarchar(2)Directory drive path (eg: 'H:')
    logon script columnvarchar(255)Batch file to run on client side when logging on
    profile path columnvarchar(255)Path of profile
    acct desc columnvarchar(255)Some ASCII NT user data
    workstations columnvarchar(255)Workstations user can logon to (or NULL for all)
    unknown string columnvarchar(255)unknown string
    munged dial columnvarchar(255)?
    user sid columnvarchar(255)NT user SID
    group sid columnvarchar(255)NT group ID
    lanman pass columnvarchar(255)encrypted lanman password
    nt pass columnvarchar(255)encrypted nt passwd
    plain pass columnvarchar(255)plaintext password
    acct control columnint(9)nt user data
    unknown 3 columnint(9)unknown
    logon divs columnint(9)?
    hours len columnint(9)?
    unknown 5 columnint(9)unknown
    unknown 6 columnint(9)unknown

    Eventually, you can put a colon (:) after the name of each column, which should specify the column to update when updating the table. You can also specify nothing behind the colon - then the data from the field will not be updated. -

    Using plaintext passwords or encrypted password

    +

    Using plaintext passwords or encrypted password

    I strongly discourage the use of plaintext passwords, however, you can use them:

    If you would like to use plaintext passwords, set @@ -3984,7 +3798,7 @@ access to attrs=lmPassword,ntPassword

    If you use encrypted passwords, set the 'identifier:plain pass column' to 'NULL' (without the quotes). This is the default. -

    Getting non-column data from the table

    +

    Getting non-column data from the table

    It is possible to have not all data in the database and making some 'constant'.

    For example, you can set 'identifier:fullname column' to : @@ -3999,80 +3813,73 @@ access to attrs=lmPassword,ntPassword

    To import data, use: $ pdbedit -i xml:filename -

    Common Errors

    Users can not logon - Users not in Samba SAM

    - People forget to put their users in their backend and then complain Samba won't authorize them. -

    Users are being added to the wrong backend database

    +

    Common Errors

    Users can not 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 section Account Management Tools for details.

    Users being added to wrong backend database

    A few complaints have been received from users that just moved to Samba-3. The following smb.conf file entries were causing problems, new accounts were being added to the old smbpasswd file, not to the tdbsam passdb.tdb file:

    - 

    -	[globals]
-		...
-		passdb backend = smbpasswd, tdbsam, guest
-		...
-

    +

    [global]
    ...
    passdb backend = smbpasswd, tdbsam
    ...

    Samba will add new accounts to the first entry in the passdb backend parameter entry. If you want to update to the tdbsam, then change the entry to:

    - 

    -	[globals]
-		...
-		passdb backend = tdbsam, smbpasswd, guest
-		...
-

    -

    auth methods does not work

    - If you explicitly set an 'auth methods' parameter, guest must be specified as the first - entry on the line. Eg: auth methods = guest sam. +

    [globals]
    ...
    passdb backend = tdbsam, smbpasswd
    ...

    +

    auth methods does not work

    + If you explicitly set an auth methods parameter, guest must be specified as the first + entry on the line. Eg: auth methods = guest sam.

    - This is the exact opposite of the requirement for the passdb backed + This is the exact opposite of the requirement for the passdb backend option, where it must be the LAST parameter on the line. -

    Chapter 12. Mapping MS Windows and Unix Groups

    Jean François Micouleau

    Gerald (Jerry) Carter

    Samba Team

    John H. Terpstra

    Samba Team

    Table of Contents

    Features and Benefits
    Discussion
    Example Configuration
    Configuration Scripts
    Sample smb.conf add group script
    Script to configure Group Mapping
    Common Errors
    Adding Groups Fails
    Adding MS Windows Groups to MS Windows Groups Fails

    +


    [3] Only when the LDAP server supports LDAP_EXOP_X_MODIFY_PASSWD

    Chapter 12. Mapping MS Windows and UNIX Groups

    Jean François Micouleau

    Gerald (Jerry) Carter

    Samba Team

    John H. Terpstra

    Samba Team

    Table of Contents

    Features and Benefits
    Discussion
    Example Configuration
    Configuration Scripts
    Sample smb.conf add group script
    Script to configure Group Mapping
    Common Errors
    Adding Groups Fails
    Adding MS Windows Groups to MS Windows Groups Fails
    Adding Domain Users to the Power Users group

    Starting with Samba-3, new group mapping functionality is available to create associations - between Windows group SIDs and UNIX groups. The groupmap subcommand + between Windows group SIDs and UNIX groups. The groupmap subcommand included with the net tool can be used to manage these associations.

    Warning

    The first immediate reason to use the group mapping on a Samba PDC, is that + the domain admin group has been removed and should no longer be specified in smb.conf. 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 MMC tools - so long as appropriate interface scripts have been provided to smb.conf. -

    + 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 + so long as winbind is running, Samba accounts group accounts that are created using these tools will be + allocated UNIX UIDs/GIDs from the parameters set by the idmap uid/idmap gid settings + in the smb.conf file. +

    Figure 12.1. IDMAP groups

    IDMAP groups

    Administrators should be aware that where smb.conf group interface scripts make - direct calls to the Unix/Linux system tools (eg: the shadow utilities, groupadd, - groupdel, groupmod) then the resulting Unix/Linux group names will be subject + direct calls to the UNIX/Linux system tools (eg: the shadow utilities, groupadd, + groupdel, groupmod) then the resulting UNIX/Linux group names will be subject to any limits imposed by these tools. If the tool does NOT allow upper case characters or space characters, then the creation of an MS Windows NT4 / 200x style group of - Engineering Managers will attempt to create an identically named - Unix/Linux group, an attempt that will of course fail! -

    + Engineering Managers will attempt to create an identically named + UNIX/Linux group, an attempt that will of course fail! +

    There are several possible work-arounds 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) + 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 work-around solution.

    - Another work-around is to manually create a Unix/Linux group, then manually create the + Another work-around 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 installing 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 privileges to perform essential system tasks. eg: 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 'Administrator' group, 'joe' has exactly the same rights as 'Administrator'.

    - When an MS Windows NT4 / W200x is made a domain member, the "Domain Admins" group of the + When an MS Windows NT4 / W200x 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 Administrators' group inherits the rights of the local 'Administrators' group when logging on the workstation. @@ -4087,58 +3894,58 @@ access to attrs=lmPassword,ntPassword domadm:x:502:joe,john,mary

  • - Map this domadm group to the "Domain Admins" group by running the command: + Map this domadm group to the "Domain Admins" group by running the command:

    - 

    -		root# net groupmap add ntgroup="Domain Admins" unixgroup=domadm
-

    -

    - The quotes around "Domain Admins" are necessary due to the space in the group name. +

    +root# net groupmap add ntgroup="Domain Admins" unixgroup=domadm
+

    +

    + The quotes around "Domain Admins" are necessary due to the space in the group name. Also make sure to leave no whitespace 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 making any UNIX group a Windows domain group. For example, if you wanted to include a UNIX group (e.g. acct) in a ACL on a local file or printer on a domain member machine, you would flag that group as a domain group by running the following on the Samba PDC:

    - 

    -	root# net groupmap add rid=1000 ntgroup="Accounting" unixgroup=acct
-

    +

    +root# net groupmap add rid=1000 ntgroup="Accounting" unixgroup=acct
+

    Be aware that the RID parameter is a unsigned 32 bit integer that should normally start at 1000. However, this rid must not overlap with any RID assigned - to a user. Verifying this is done differently depending on on the passdb backend + to a user. Verifying 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. -

    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
-		System Administrators (S-1-5-21-2547222302-1596225915-2414751004-1002) -> sysadmin
-		Domain Admins (S-1-5-21-2547222302-1596225915-2414751004-512) -> domadmin
-		Domain Users (S-1-5-21-2547222302-1596225915-2414751004-513) -> domuser
-		Domain Guests (S-1-5-21-2547222302-1596225915-2414751004-514) -> domguest
-

    +

    +root#  net groupmap list
+System Administrators (S-1-5-21-2547222302-1596225915-2414751004-1002) -> sysadmin
+Domain Admins (S-1-5-21-2547222302-1596225915-2414751004-512) -> domadmin
+Domain Users (S-1-5-21-2547222302-1596225915-2414751004-513) -> domuser
+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 (ie: prepared by someone else for general use). -

    Sample smb.conf add group script

    - A script to great complying group names for use by the Samba group interfaces: +

    Sample smb.conf add group script

    + A script to create complying group names for use by the Samba group interfaces:

    -

    Example 12.1. smbgrpadd.sh

    +
    Example 12.1. smbgrpadd.sh
     
 #!/bin/bash
 
 # Add the group using normal system groupadd tool.
 groupadd smbtmpgrp00
 
-thegid=`cat /etc/group | grep smbtmpgrp00 | cut -d ":" -f3`
+thegid=`cat /etc/group | grep smbtmpgrp00 | cut -d ":" -f3`
 
 # Now change the name to what we want for the MS Windows networking end
 cp /etc/group /etc/group.bak
@@ -4150,81 +3957,91 @@ exit 0
 
    
 
    
 		The smb.conf entry for the above script would look like:
-		
    -		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 Engineers, Marketoids, Gnomes: +

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

     #!/bin/bash
 
-net groupmap modify ntgroup="Domain Admins" unixgroup=ntadmin
-net groupmap modify ntgroup="Domain Users" unixgroup=users
-net groupmap modify ntgroup="Domain Guests" unixgroup=nobody
-net groupmap modify ntgroup="Administrators" unixgroup=root
-net groupmap modify ntgroup="Users" unixgroup=users
-net groupmap modify ntgroup="Guests" unixgroup=nobody
-net groupmap modify ntgroup="System Operators" unixgroup=sys
-net groupmap modify ntgroup="Account Operators" unixgroup=root
-net groupmap modify ntgroup="Backup Operators" unixgroup=bin
-net groupmap modify ntgroup="Print Operators" unixgroup=lp
-net groupmap modify ntgroup="Replicators" unixgroup=daemon
-net groupmap modify ntgroup="Power Users" unixgroup=sys
+net groupmap modify ntgroup="Domain Admins" unixgroup=ntadmin
+net groupmap modify ntgroup="Domain Users" unixgroup=users
+net groupmap modify ntgroup="Domain Guests" unixgroup=nobody
+net groupmap modify ntgroup="Administrators" unixgroup=root
+net groupmap modify ntgroup="Users" unixgroup=users
+net groupmap modify ntgroup="Guests" unixgroup=nobody
+net groupmap modify ntgroup="System Operators" unixgroup=sys
+net groupmap modify ntgroup="Account Operators" unixgroup=root
+net groupmap modify ntgroup="Backup Operators" unixgroup=bin
+net groupmap modify ntgroup="Print Operators" unixgroup=lp
+net groupmap modify ntgroup="Replicators" unixgroup=daemon
+net groupmap modify ntgroup="Power Users" unixgroup=sys
 
-#groupadd Engineers
-#groupadd Marketoids
-#groupadd Gnomes
+groupadd Orks
+groupadd Elves
+groupadd Gnomes
 
-#net groupmap add ntgroup="Engineers"  unixgroup=Engineers    type=d
-#net groupmap add ntgroup="Marketoids" unixgroup=Marketoids   type=d
-#net groupmap add ntgroup="Gnomes"     unixgroup=Gnomes       type=d
+net groupmap add ntgroup="Orks"       unixgroup=Orks         type=d
+net groupmap add ntgroup="Elves"      unixgroup=Elves        type=d
+net groupmap add ntgroup="Gnomes"     unixgroup=Gnomes       type=d

    Of course it is expected that the administrator will modify this to suit local needs. For information regarding the use of the net groupmap tool please refer to the man page. -

    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 must be carefully tested manually before putting them 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 + 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 either an upper case character and/or a space character in it.

    There are three possible work-arounds. Firstly, use only group names that comply - with the limitations of the Unix/Linux groupadd system tool. + with the limitations of the UNIX/Linux groupadd system tool. The second involves use of the script mentioned earlier in this chapter, and the - third option is to manually create a Unix/Linux group account that can substitute + third 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 MS Windows Groups to MS Windows Groups Fails

    +

    Adding MS Windows Groups to MS Windows Groups Fails

    Samba-3 does NOT support nested groups from the MS Windows control environment. -

    Chapter 13. File, Directory and Share Access Controls

    John H. Terpstra

    Samba Team

    Jeremy Allison

    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
    Common Errors
    Users can not write to a public share
    I have set force user and Samba still makes root the owner of all the files - I touch!

    +

    Adding Domain Users to the 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 can not add the Domain Users group to the Power Users + group automatically, this must be done on each workstation by logging in as the local workstation + administrator and then using click on Start / Control Panel / Users and Passwords + now click on the 'Advanced' tab, then on the 'Advanced' Button. +

    + Now click on 'Groups', then double click on 'Power Users'. This will launch the panel to add users + or groups to the local machine 'Power Uses' group. Click on the 'Add' button, select the domain + from which the 'Domain Users' group is to be added, double click on the 'Domain Users' group, then + click on the 'Ok' button. Note: If a logon box is presented during this process please remember to + enter the connect as DOMAIN\UserName. ie: For the domain MIDEARTH and the user 'root' enter + MIDEARTH\root. +

    Chapter 13. 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
    Common Errors
    Users can not write to a public share
    I have set force user but Samba still makes root the owner of all the files I touch!
    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 what is the best way to -provide users with the type of access they need while protecting resources from the consequences -of untoward access capabilities. +administrators are often confused regarding network access controls and how to +provide users with the access they need while protecting resources from unauthorised access.

    -Unix administrators frequently are not familiar with the MS Windows environment and in particular +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 can not completely hide, even -though it does try to make the chasm transparent. -

    +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 +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. @@ -4233,25 +4050,24 @@ The purpose of this chapter is to present each of the points of control that are 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 it should be borne in mind that Samba was created to -provide a means of interoperability and interchange of data between two operating environments -that are quite different. It was never the intent to make Unix/Linux like MS Windows NT. Instead -the purpose was an 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

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

    Samba offers a lot of 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 + UNIX File and Directory Permissions

      - Samba honours and implements Unix file system access controls. Users + Samba honours 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 connection setup process. Samba uses this user identity to validate whether or not the user should be given access to file system resources (files and directories). This chapter provides an overview for those - to whom the Unix permissions and controls are a little strange or unknown. + to whom the UNIX permissions and controls are a little strange or unknown.

    • Samba Share Definitions

      @@ -4270,22 +4086,22 @@ shrink. 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 + MS Windows ACLs through UNIX POSIX ACLs

      - The use of POSIX ACLs on Unix/Linux is possible ONLY if the underlying + 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 + available to you. Current UNIX technology platforms have native support for POSIX ACLs. There are patches for the Linux kernel that provide this also. 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 +implement a totally divergent file system technology from what is provided in the UNIX operating system environment. Firstly we should consider what the most significant differences are, then we shall look at how Samba helps to bridge the differences. -

    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 +

    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 behaviour that differs from unix file system behaviour then somehow Samba is responsible for emulating that in a transparent and consistent manner. @@ -4295,128 +4111,108 @@ at how Samba helps to bridge the differences. but for the greater part we will stay within the bounds of default behaviour. Those wishing to explore to depths of control ability should review the smb.conf man page.

    File System Feature Comparison

    Name Space

    - MS Windows NT4 / 200x/ XP files names may be up to 254 characters long, Unix file names + MS Windows NT4 / 200x/ XP files names may be up to 254 characters long, UNIX file names may be 1023 characters long. In MS Windows file extensions indicate particular file types, - in Unix this is not so rigorously observed as all names are considered arbitrary. + in UNIX this is not so rigorously observed as all names are considered arbitrary.

    - What MS Windows calls a Folder, Unix calls a directory, + What MS Windows calls a Folder, UNIX calls a directory.

    Case Sensitivity

    - MS Windows file names are generally Upper Case if made up of 8.3 (ie: 8 character file name + + MS Windows file names are generally upper case if made up of 8.3 (ie: 8 character file name and 3 character extension. If longer than 8.3 file names are Case Preserving, and Case Insensitive.

    - Unix file and directory names are Case Sensitive and Case Preserving. Samba implements the - MS Windows file name behaviour, but it does so as a user application. The Unix file system + UNIX file and directory names are case sensitive and case preserving. Samba implements the + MS Windows file name behaviour, but it does so as a user application. The UNIX file system provides no mechanism to perform case insensitive file name lookups. MS Windows does this by default. This means that Samba has to carry the processing overhead to provide features - that are NOT native to the Unix operating system environment. + that are NOT native to the UNIX operating system environment.

    - Consider the following, all are unique Unix names but one single MS Windows file name: + Consider the following, all are unique UNIX names but one single MS Windows file name: MYFILE.TXT MyFile.txt myfile.txt - So clearly, In an MS Windows file name space these three files CAN NOT co-exist! But in Unix + So clearly, In an MS Windows file name space these three files CAN NOT co-exist! But in UNIX they can. So what should Samba do if all three are present? Answer, the one that is lexically first will be accessible to MS Windows users, the others are invisible and unaccessible - any other solution would be suicidal.

    Directory Separators

    - MS Windows and DOS uses the back-slash '\' as a directory delimiter, Unix uses the forward-slash '/' + MS Windows and DOS uses the back-slash '\' as a directory delimiter, UNIX uses the forward-slash '/' as it's directory delimiter. This is transparently handled by Samba.

    Drive Identification

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

    File Naming Conventions

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

    Links and Short-Cuts

    - MS Windows make use of "links and Short-Cuts" 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 + + + + + MS Windows make use of "links and Short-Cuts" 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.

    - Symbolic links are files in Unix that contain the actual location of the data (file OR directory). An + Symbolic links are files in UNIX that contain the actual location of the data (file OR directory). An operation (like read or write) will operate directly on the file referenced. Symbolic links are also referred to as 'soft links'. A hard link is something that MS Windows is NOT familiar with. It allows one physical file to be known simultaneously by more than one file name.

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

    Managing Directories

    + 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/education. +

    Managing Directories

    There are three basic operations for managing directories, create, delete, rename. -

    Table 13.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 13.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 foundational training manuals and reference materials - regarding file and directory permissions maintenance. Much can be achieved with the basic Unix permissions + 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 Access Control Lists (ACLs) or Extended Attributes (EAs).

    - Unix/Linux file and directory access permissions involves setting three (3) primary sets of data and one (1) control set. - A Unix file listing looks as follows:- + UNIX/Linux file and directory access permissions involves setting three (3) primary sets of data and one (1) control set. + A UNIX file listing looks as follows:- - 

    -	jht@frodo:~/stuff> ls -la
-	total 632
-	drwxr-xr-x   13 jht   users      816 2003-05-12 22:56 .
-	drwxr-xr-x   37 jht   users     3800 2003-05-12 22:29 ..
-	d---------    2 jht   users       48 2003-05-12 22:29 muchado00
-	d--x--x--x    2 jht   users       48 2003-05-12 22:29 muchado01
-	dr-xr-xr-x    2 jht   users       48 2003-05-12 22:29 muchado02
-	drwxrwxrwx    2 jht   users       48 2003-05-12 22:29 muchado03
-	drw-rw-rw-    2 jht   users       48 2003-05-12 22:29 muchado04
-	d-w--w--w-    2 jht   users       48 2003-05-12 22:29 muchado05
-	dr--r--r--    2 jht   users       48 2003-05-12 22:29 muchado06
-	drwxrwxrwt    2 jht   users       48 2003-05-12 22:29 muchado07
-	drwsrwsrwx    2 jht   users       48 2003-05-12 22:29 muchado08
-	----------    1 jht   users     1242 2003-05-12 22:31 mydata00.lst
-	---x--x--x    1 jht   users     1674 2003-05-12 22:33 mydata01.lst
-	--w--w--w-    1 jht   users     7754 2003-05-12 22:33 mydata02.lst
-	--wx-wx-wx    1 jht   users   260179 2003-05-12 22:33 mydata03.lst
-	-r--r--r--    1 jht   users    21017 2003-05-12 22:32 mydata04.lst
-	-r-xr-xr-x    1 jht   users   206339 2003-05-12 22:32 mydata05.lst
-	-rw-rw-rw-    1 jht   users    41105 2003-05-12 22:32 mydata06.lst
-	-rwxrwxrwx    1 jht   users    19312 2003-05-12 22:32 mydata07.lst
-	jht@frodo:~/stuff>
-

    -

    - The columns above represent (from left to right): permissions, no blocks used, owner, group, size (bytes), access date, access time, file name. +

    +$ ls -la
+total 632
+drwxr-xr-x   13 maryo   gnomes      816 2003-05-12 22:56 .
+drwxrwxr-x   37 maryo   gnomes     3800 2003-05-12 22:29 ..
+dr-xr-xr-x    2 maryo   gnomes       48 2003-05-12 22:29 muchado02
+drwxrwxrwx    2 maryo   gnomes       48 2003-05-12 22:29 muchado03
+drw-rw-rw-    2 maryo   gnomes       48 2003-05-12 22:29 muchado04
+d-w--w--w-    2 maryo   gnomes       48 2003-05-12 22:29 muchado05
+dr--r--r--    2 maryo   gnomes       48 2003-05-12 22:29 muchado06
+drwsrwsrwx    2 maryo   gnomes       48 2003-05-12 22:29 muchado08
+----------    1 maryo   gnomes     1242 2003-05-12 22:31 mydata00.lst
+--w--w--w-    1 maryo   gnomes     7754 2003-05-12 22:33 mydata02.lst
+-r--r--r--    1 maryo   gnomes    21017 2003-05-12 22:32 mydata04.lst
+-rw-rw-rw-    1 maryo   gnomes    41105 2003-05-12 22:32 mydata06.lst
+$ 
+

    - The permissions field is made up of: - - 

    -	 JRV: Put this into a diagram of some sort
-	[ type  ] [ users ] [ group ] [ others ]   [File, Directory Permissions]
-	[ d | l ] [ r w x ] [ r w x ] [ r w x  ]
-	  |   |     | | |     | | |     | | |
-	  |   |     | | |     | | |     | | |-----> Can Execute, List files
-	  |   |     | | |     | | |     | |-------> Can Write,   Create files
-	  |   |     | | |     | | |     |---------> Can Read,    Read files
-	  |   |     | | |     | | |---------------> Can Execute, List files
-	  |   |     | | |     | |-----------------> Can Write,   Create files
-	  |   |     | | |     |-------------------> Can Read,    Read files
-	  |   |     | | |-------------------------> Can Execute, List files
-	  |   |     | |---------------------------> Can Write,   Create files
-	  |   |     |-----------------------------> Can Read,    Read files
-	  |   |-----------------------------------> Is a symbolic Link
-	  |---------------------------------------> Is a directory
-

    + The columns above represent (from left to right): permissions, number of hard links to file, owner, group, size (bytes), access date, access time, file name.

    + An overview of the permissions field can be found in the image below. +

    Figure 13.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 'Can NOT' and is represented as a '-' character. -

    Example 13.1. Example File

    +	
    Example 13.1. Example File
     		-rwxr-x---   Means: The owner (user) can read, write, execute
 		                    the group can read and execute
 		                    everyone else can NOT do anything with it
 		
    
 
 	
    
-	Additional possibilities in the [type] field are: c = character device, b = block device, p = pipe device, s = Unix Domain Socket.
+	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 or group ID on execution (s),
@@ -4435,101 +4231,101 @@ at how Samba helps to bridge the differences.
 	the (x) execute flags are not set files can not be listed (seen) in the directory by anyone. The group can read files in the
 	directory but can NOT create new files. NOTE: 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.
-

    Share Definition Access Controls

    +

    Share Definition Access Controls

    The following parameters in the smb.conf file sections that 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 very useful. In some situations it is distinctly desirable to affect all - file system operations as if a single user is doing this, the use of the force user and - force group behaviour will achieve this. In other situations it may be necessary to affect a + file system operations as if a single user is doing this, the use of the force user and + force group behaviour will achieve this. In other situations it may be necessary to affect a paranoia level of control to ensure that only particular authorised persons will be able to access a share or - it's contents, here the use of the valid users or the invalid users may + it's contents, here the use of the valid users or the invalid users may be most useful.

    As always, it is highly advisable to use the least difficult to maintain and the least ambiguous method for controlling access. Remember, that when you leave the scene someone else will need to provide assistance and if that person finds too great a mess, or if they do not understand what you have done then there is risk of Samba being removed and an alternative solution being adopted. -

    Table 13.2. User and Group Based Controls

    Control ParameterDescription - Action - Notes
    admin users

    +

    Table 13.2. User and Group Based Controls

    Control ParameterDescription - Action - Notes
    admin users

    List of users who will be granted administrative privileges on the share. They will do all file operations as the super-user (root). Any user in this list will be able to do anything they like on the share, irrespective of file permissions. -

    force group

    +

    force group

    Specifies a UNIX group name that will be assigned as the default primary group for all users connecting to this service. -

    force user

    +

    force user

    Specifies a UNIX user name that will be assigned as the default user for all users connecting to this service. This is useful for sharing files. Incorrect use can cause security problems. -

    guest ok

    +

    guest ok

    If this parameter is set for a service, then no password is required to connect to the service. Privileges will be those of the guest account. -

    invalid users

    +

    invalid users

    List of users that should not be allowed to login to this service. -

    only user

    +

    only user

    Controls whether connections with usernames not in the user list will be allowed. -

    read list

    +

    read list

    List of users that are given read-only access to a service. Users in this list will not be given write access, no matter what the read only option is set to. -

    username

    +

    username

    Refer to the smb.conf man page for more information - this is a complex and potentially misused parameter. -

    valid users

    +

    valid users

    List of users that should be allowed to login to this service. -

    write list

    +

    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

    The following file and directory permission based controls, if misused, can result in considerable difficulty to diagnose the cause of mis-configuration. Use them sparingly and carefully. By gradually introducing each one by one undesirable side-effects may be detected. In the event of a problem, always comment all of them out and then gradually re-introduce them in a controlled fashion. -

    Table 13.3. File and Directory Permission Based Controls

    Control ParameterDescription - Action - Notes
    create mask

    +

    Table 13.3. File and Directory Permission Based Controls

    Control ParameterDescription - Action - Notes
    create mask

    Refer to the smb.conf man page. -

    directory mask

    +

    directory mask

    The octal modes used when converting DOS modes to UNIX modes when creating UNIX directories. See also: directory security mask. -

    dos filemode

    +

    dos filemode

    Enabling this parameter allows a user who has write access to the file to modify the permissions on it. -

    force create mode

    +

    force create mode

    This parameter specifies a set of UNIX mode bit permissions that will always be set on a file created by Samba. -

    force directory mode

    +

    force directory mode

    This parameter specifies a set of UNIX mode bit permissions that will always be set on a directory created by Samba. -

    force directory security mode

    +

    force directory security mode

    Controls UNIX permission bits modified when a Windows NT client is manipulating UNIX permissions on a directory -

    force security mode

    +

    force security mode

    Controls UNIX permission bits modified when a Windows NT client manipulates UNIX permissions. -

    hide unreadable

    +

    hide unreadable

    Prevents clients from seeing the existence of files that cannot be read. -

    hide unwriteable files

    +

    hide unwriteable files

    Prevents clients from seeing the existence of files that cannot be written to. Unwriteable directories are shown as usual. -

    nt acl support

    +

    nt acl support

    This parameter controls whether smbd will attempt to map UNIX permissions into Windows NT access control lists. -

    security mask

    +

    security mask

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

    Miscellaneous Controls

    - The following are documented because of the prevalence of administrators creating inadvertant barriers to file +

    Miscellaneous Controls

    + The following are documented because of the prevalence of administrators creating inadvertent barriers to file access by not understanding the full implications of smb.conf file settings. -

    Table 13.4. Other Controls

    Control ParameterDescription - Action - Notes
    case sensitive, default case, short preserve case

    +

    Table 13.4. Other Controls

    Control ParameterDescription - Action - Notes
    case sensitive, default case, short preserve case

    This means that all file name lookup will be done in a case sensitive manner. Files will be created with the precise filename Samba received from the MS Windows client. -

    csc policy

    +

    csc policy

    Client Side Caching Policy - parallels MS Windows client side file caching capabilities. -

    dont descend

    +

    dont descend

    Allows to specify a comma-delimited list of directories that the server should always show as empty. -

    dos filetime resolution

    +

    dos filetime resolution

    This option is mainly used as a compatibility option for Visual C++ when used against Samba shares. -

    dos filetimes

    +

    dos filetimes

    DOS and Windows allows users to change file time stamps if they can write to the file. POSIX semantics prevent this. This options allows DOS and Windows behaviour. -

    fake oplocks

    +

    fake oplocks

    Oplocks are the way that SMB clients get permission from a server to locally cache file operations. If a server grants an oplock then the client is free to assume that it is the only one accessing the file and it will aggressively cache file data. -

    hide dot files, hide files, veto files

    +

    hide dot files, hide files, veto files

    Note: MS Windows Explorer allows over-ride of files marked as hidden so they will still be visible. -

    read only

    +

    read only

    If this parameter is yes, then users of a service may not create or modify files in the service's directory. -

    veto files

    +

    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 a very effective way to limit who can @@ -4546,9 +4342,9 @@ Before using any of the following options please refer to the man page for /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: tdbdump share_info.tdb. -

    Share Permissions Management

    +

    Share Permissions Management

    The best tool for the task is platform dependant. Choose the best tool for your environment. -

    Windows NT4 Workstation/Server

    +

    Windows NT4 Workstation/Server

    The tool you need to use to manage share permissions on a Samba 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 Microsoft - see details below. @@ -4558,9 +4354,9 @@ Before using any of the following options please refer to the man page for

  • Now click on the share that you wish to manage, then click on the Properties tab, next click on 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 access control lists on the share itself are set using native - tools, usually from filemanager. For example, in Windows 200x: right click on the shared folder, + 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.

    @@ -4587,72 +4383,71 @@ Before using any of the following options please refer to the man page for no access means that MaryK who is part of the group Everyone will have no access even if this user is given explicit full control access. -

    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.

    Note that this ability is careful not to compromise - the security of the UNIX host Samba is running on, and - still obeys all the file permission rules that a Samba - administrator can set.

    Note

    - All access to Unix/Linux system file via Samba is controlled at - the operating system file access control level. When trying to - figure out file access problems it is vitally important to identify - 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 +

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

    + Note that this ability is careful not to compromise the security of the UNIX host Samba is running on, and + still obeys all the file permission rules that a Samba administrator can set. +

    + Samba does not attempt to go beyond POSIX ACLs, so that the various finer-grained access control + options provided in Windows are actually ignore. +

    Note

    + All access to UNIX/Linux system files via Samba is controlled by the operating system file access controls. + 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

    From an NT4/2000/XP client, single-click with the right - mouse button 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 tab Security and you - will see three buttons, Permissions, - Auditing, and Ownership. - The Auditing button will cause either - an error message A requested privilege is not held - by the client to appear if the user is not the - NT Administrator, or a dialog which is intended to allow an - Administrator to add auditing requirements to a file if the - user is logged on as the NT Administrator. This dialog is - non-functional with a Samba share at this time, as the only - useful button, the Add button will not currently - allow a list of users to be seen.

    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 of the form :

    "SERVER\user (Long name)"

    Where SERVER is the NetBIOS name of - the Samba server, user is the user name of - the UNIX user who owns the file, and (Long name) - is the descriptive string identifying the user (normally found in the - GECOS field of the UNIX password database). Click on the - Close button to remove this dialog.

    If the parameter nt acl support - is set to false then 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 on - it will display a dialog box complaining that the user 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 - operation in UNIX, available only to the root - user. As clicking on this button causes 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 filesystem 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, available from the main Samba ftp site.

    Viewing File or Directory Permissions

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

    "SERVER\ +

    Viewing File Security on a Samba Share

    + From an NT4/2000/XP client, single-click with the right mouse button 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 tab + Security and you will see three buttons, Permissions, + Auditing, and Ownership. The Auditing + button will cause either an error message A requested privilege is not held by the client + to appear if the user is not the NT Administrator, or a dialog which is intended to allow an Administrator + to add auditing requirements to a file if the user is logged on as the NT Administrator. This dialog is + non-functional with a Samba share at this time, as the only useful button, the Add + button will not currently allow a list of users to be seen. +

    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 of the form: +

    + "SERVER\user (Long name)" +

    + Where SERVER is the NetBIOS name of the Samba server, user + is the user name of the UNIX user who owns the file, and (Long name) is the + descriptive string identifying the user (normally found in the GECOS field of the UNIX password database). + Click on the Close button to remove this dialog. +

    + If the parameter nt acl support is set to false + then 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 on it will display a dialog box complaining that the user 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 + operation in UNIX, available only to the root user. As clicking on this button causes + 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 filesystem 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, available from the main Samba FTP site.

    Viewing File or Directory Permissions

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

    "SERVER\ user - (Long name)"

    Where SERVER is the NetBIOS name of - the Samba server, user is the user name of - the UNIX user who owns the file, and (Long name) - is the descriptive string identifying the user (normally found in the - GECOS field of the UNIX password database).

    If the parameter nt acl support - is set to false then the file owner will - be shown as the NT user "Everyone" and the - permissions will be shown as NT "Full Control".

    The permissions field is displayed differently for files - and directories, so I'll describe the way file permissions - are displayed first.

    File Permissions

    The standard UNIX user/group/world triplet and - the corresponding "read", "write", "execute" permissions + (Long name)"

    Where SERVER is the NetBIOS name of the Samba server, + user is the user name of the UNIX user who owns the file, and + (Long name) is the descriptive string identifying the user (normally found in the + GECOS field of the UNIX password database).

    + If the parameter nt acl support is set to false + then the file owner will be shown as the NT user "Everyone" and the permissions will be + shown as NT "Full Control". +

    + The permissions field is displayed differently for files and directories, so I'll describe the way file permissions + are displayed first. +

    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 permissions. The UNIX world permissions are mapped into @@ -4663,20 +4458,20 @@ Before using any of the following options please refer to the man page for icon respectively followed by the list of permissions allowed for the UNIX user and group.

    As many UNIX permission sets don't map into common NT names such as read, - "change" or full control then + "change" or full control then usually the permissions will be prefixed by the words - "Special Access" in the NT display list.

    But what happens if the file has no permissions allowed - for a particular UNIX user group or world component ? In order - to allow "no permissions" to be seen and modified then Samba - overloads the NT "Take Ownership" ACL attribute + "Special Access" in the NT display list.

    But what happens if the file has no permissions allowed + for a particular UNIX user group or world component? In order + to allow "no permissions" to be seen and modified then Samba + overloads the NT "Take Ownership" ACL attribute (which has no meaning in UNIX) and reports a component with - no permissions as having the NT "O" bit set. + 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 will - be given below.

    Directory Permissions

    Directories on an NT NTFS file system have two + be given below.

    Directory Permissions

    Directories on an NT NTFS file system have two different sets of permissions. The first set of permissions is the ACL set on the directory itself, this is usually displayed - in the first set of parentheses in the normal "RW" + 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 above, and is displayed in the same way.

    The second set of directory permissions has no real meaning @@ -4684,15 +4479,15 @@ Before using any of the following options please refer to the man page for permissions that any file created within this directory would inherit.

    Samba synthesises 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 and directory permissions is as simple + created by Samba on this share would receive.

    Modifying file or directory permissions

    Modifying file and directory permissions is as simple as changing the displayed permissions in the dialog box, and clicking the OK button. 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 need to also be taken into account.

    If the parameter nt acl support + attributes that need to also be taken into account.

    If the parameter nt acl support is set to false then any attempt to set - security permissions will fail with an "Access Denied" - message.

    The first thing to note is that the "Add" + security permissions will fail with an "Access Denied" + message.

    The first thing to note is that the "Add" button will not return a list of users in Samba (it will give an error message of The remote procedure call failed and did not execute). This means that you can only @@ -4701,13 +4496,13 @@ Before using any of the following options please refer to the man page for

    If a permission triplet (either user, group, or world) is removed from the list of permissions in the NT dialog box, then when the OK button is pressed it will - be applied as "no permissions" on the UNIX side. If you then - view the permissions again the "no permissions" entry will appear - as the NT "O" flag, as described above. This + be applied as "no permissions" on the UNIX side. If you then + view the permissions again the "no permissions" entry will appear + as the NT "O" flag, as described above. This allows you to add permissions back to a file or directory once - you have removed them from a triplet component.

    As UNIX supports only the "r", "w" and "x" bits of - an NT ACL then if other NT security attributes such as "Delete - access" are selected then they will be ignored when applied on + you have removed them from a triplet component.

    As UNIX supports only the "r", "w" and "x" bits of + an NT ACL then if other NT security attributes such as "Delete + access" are selected then they will be ignored when applied on the Samba server.

    When setting permissions on a directory the second set of permissions (in the second set of parentheses) is by default applied to all files within that directory. If this @@ -4717,61 +4512,58 @@ Before using any of the following options please refer to the man page for 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 + Ownership permission (displayed as "O" + ) highlighted.

    Interaction with the standard Samba create mask parameters

    There are four parameters to control interaction with the standard Samba create mask parameters. These are : -

    security mask
    force security mode
    directory security mask
    force directory security mode

    +

    • security mask

    • force security mode

    • directory security mask

    • force directory security mode

    Once a user clicks OK to apply the permissions Samba maps the given permissions into a user/group/world r/w/x triplet set, and then will check the changed permissions for a - file against the bits set in the - security mask parameter. Any bits that + file against the bits set in the + security mask parameter. Any bits that were changed that are not set to '1' in this parameter are left alone - in the file permissions.

    Essentially, zero bits in the security mask + in the file permissions.

    Essentially, zero bits in the security mask mask may be treated as a set of bits the user is not allowed to change, and one bits are those the user is allowed to change.

    If not set explicitly this parameter is set to the same value as - the create mask - parameter. To allow a user to modify all the + the create mask parameter. To allow a user to modify all the user/group/world permissions on a file, set this parameter to 0777.

    Next Samba checks the changed permissions for a file against - the bits set in the - force security mode parameter. Any bits + the bits set in the + force security mode parameter. Any bits that were changed that correspond to bits set to '1' in this parameter are forced to be set.

    Essentially, bits set in the force security mode parameter may be treated as a set of bits that, when modifying security on a file, the user has always set to be 'on'.

    If not set explicitly this parameter is set to the same value - as the force - create mode parameter. + as the force create mode parameter. To allow a user to modify all the user/group/world permissions on a file - with no restrictions set this parameter to 000.

    The security mask and force + with no restrictions set this parameter to 000.

    The security mask and force security mode parameters are applied to the change request in that order.

    For a directory Samba will perform the same operations as described above for a file except using the parameter directory security mask instead of security mask, and force directory security mode parameter instead of force security mode - .

    The directory security mask parameter + .

    The directory security mask parameter by default is set to the same value as the directory mask parameter and the force directory security mode parameter by default is set to the same value as - the force directory mode parameter.

    In this way Samba enforces the permission restrictions that + the force directory mode parameter.

    In this way Samba enforces the permission restrictions that an administrator can set on a Samba share, whilst still allowing users to modify the permission bits within that restriction.

    If you want to set up a share that allows users full control in modifying the permission bits on their files and directories and doesn't 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

    Samba maps some of the DOS attribute bits (such as "read - only") into the UNIX permissions of a file. This means there can +

    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 dialog and the permission bits set by the file attribute mapping. -

    One way this can show up is if a file has no UNIX read access - for the owner it will show up as "read only" in the standard +

    One way this can show up is if a file has no UNIX read access + for the owner it will show up as "read only" in the standard file attributes tabbed dialog. Unfortunately this dialog is the same one that contains the security info in another tab.

    What this can mean is that if the owner changes the permissions to allow themselves read access using the security dialog, clicks @@ -4782,10 +4574,10 @@ Before using any of the following options please refer to the man page for OK to get back to the attributes dialog you should always hit Cancel rather than OK to ensure that your changes - are not overridden.

    Common Errors

    + are not overridden.

    Common Errors

    File, Directory and Share access problems are very common on the mailing list. The following are examples taken from the mailing list in recent times. -

    Users can not write to a public share

    +

    Users can not write to a public share

    “ We are facing some troubles with file / directory permissions. I can log on the domain as admin user(root), and there's a public share, on which everyone needs to have permission to create / modify files, but only @@ -4794,80 +4586,89 @@ are examples taken from the mailing list in recent times. ”

    There are many ways to solve this problem, here are a few hints: -

    Procedure 13.3. Example Solution:

    1. +

      1. Go to the top of the directory that is shared

      2. Set the ownership to what ever public owner and group you want - 

        -			find 'directory_name' -type d -exec chown user.group {}\;
-			find 'directory_name' -type d -exec chmod 6775 'directory_name'
-			find 'directory_name' -type f -exec chmod 0775 {} \;
-			find 'directory_name' -type f -exec chown user.group {}\;
-

        +

        +$ find 'directory_name' -type d -exec chown user.group {}\;
+$ find 'directory_name' -type d -exec chmod 6775 'directory_name'
+$ find 'directory_name' -type f -exec chmod 0775 {} \;
+$ find 'directory_name' -type f -exec chown user.group {}\;
+

        Note

        The above will set the 'sticky bit' on all directories. Read your - Unix/Linux man page on what that does. It causes the OS to assign + UNIX/Linux man page on what that does. It causes the OS to assign to all files created in the directories the ownership of the directory.

      3. Directory is: /foodbar - 

        -				$ chown jack.engr /foodbar
-

        -

        Note

        -

        This is the same as doing:

        - 

        -					$ chown jack /foodbar
-					$ chgrp engr /foodbar
-

        -

      4. Now do: +

        +$ chown jack.engr /foodbar
+

        +

        Note

        This is the same as doing:

        +$ chown jack /foodbar
+$ chgrp engr /foodbar
+

      5. Now do: - 

        -				$ chmod 6775 /foodbar
-				$ ls -al /foodbar/..
-

        +

        +$ chmod 6775 /foodbar
+$ ls -al /foodbar/..
+

        You should see: - 

        -				drwsrwsr-x  2 jack  engr    48 2003-02-04 09:55 foodbar
-

        +

        +drwsrwsr-x  2 jack  engr    48 2003-02-04 09:55 foodbar
+

      6. Now do: - 

        -				$ su - jill
-				$ cd /foodbar
-				$ touch Afile
-				$ ls -al
-

        -

        +

        +$ su - jill
+$ cd /foodbar
+$ touch Afile
+$ ls -al
+

        +

        You should see that the file Afile created by Jill will have ownership and permissions of Jack, as follows: - 

        -		-rw-r--r--  1 jack  engr     0 2003-02-04 09:57 Afile
-

        +

        +-rw-r--r--  1 jack  engr     0 2003-02-04 09:57 Afile
+

      7. Now in your smb.conf for the share add: - 

        -		force create mode = 0775
-		force directory mode = 6775
-

        +

        force create mode = 0775
        force direcrtory mode = 6775

        Note

        The above are only needed if your users are not members of the group you have used. ie: Within the OS do not have write permission on the directory.

        An alternative is to set in the smb.conf entry for the share: - 

        -		force user = jack
-		force group = engr
-

        -

    I have set force user and Samba still makes root the owner of all the files - I touch!

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

    Chapter 14. 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 Opportunistic Locking Control
    Example Configuration
    MS Windows Opportunistic Locking and Caching Controls
    Workstation Service Entries
    Server Service Entries
    Persistent Data Corruption
    Common Errors
    locking.tdb error messages
    Additional Reading

    +

    force user = jack
    force group = engr

    +

    I have set force user but Samba still makes root the owner of all the files I touch!

    + 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

    + Question: “When userB saves a word document that is owned by userA the updated file is now owned by userB. + Why is Samba doing this? How do I fix this?” +

    + Answer: Word does the following when you modify/change a Word document: Word Creates a NEW document with + a temporary name, Word then closes the old document and deletes it, Word then renames the new document to the original document name. + There is NO mechanism by which Samba CAN IN ANY WAY know that the new document really should be owned by the owners + of the original file. Samba has no way of knowing that the file will be renamed by MS Word. As far as Samba is able + to tell, the file that gets created is a NEW file, not one that the application (Word) is updating. +

    + There is a work-around to solve the permissions problem. That work-around involves understanding how you can manage file + system behaviour from within the smb.conf file, as well as understanding how Unix file systems work. Set on the directory + 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

    +

    + These two settings will ensure that all directories and files that get created in the share will be read/writable by the + owner and group set on the directory itself. +

    Chapter 14. 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 Opportunistic Locking Control
    Example Configuration
    MS Windows Opportunistic Locking 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 which 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 provide also.

    @@ -4889,13 +4690,13 @@ settings on the MS Windows client.

    Note

    Sometimes it is necessary to disable locking control settings BOTH on the Samba server as well as on each MS Windows client! -

    Discussion

    +

    Discussion

    There are two types of locking which need to be performed by a SMB server. The first is record locking which allows a client to lock a range of bytes in a open file. The second is the deny modes that are specified when a file is open.

    -Record locking semantics under Unix is very different from record locking under +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. This can not be fully correct due to several reasons. The simplest is the fact @@ -4906,29 +4707,29 @@ many more differences, too many to be listed here.

    Samba 2.2 and above implements record locking completely independent of the underlying unix system. If a byte range lock that the client requests happens -to fall into the range 0-2^31, Samba hands this request down to the Unix system. +to fall into the range 0-2^31, Samba hands this request down to the UNIX system. All other locks can not be seen by unix anyway.

    -Strictly a 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 +Strictly 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 over-stress the rpc.lockd. It is also almost always unnecessary as clients are supposed to independently make locking calls before reads and writes anyway if locking is important to them. By default Samba only makes locking calls when explicitly asked -to by a client, but if you set strict locking = yes then it +to by a client, but if you set strict locking = yes then it will make lock checking calls on every read and write.

    -You can also disable by range locking completely using locking = no. +You can also disable byte range locking completely using locking = no. This is useful for those shares that don't support locking or don't need it (such as cdroms). In this case Samba fakes the return codes of locking calls to tell clients that everything is OK.

    -The second class of locking is the deny modes. These +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 client) for the purpose of enhancing network performance when accessing a file @@ -4954,7 +4755,7 @@ other processes. 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 + is deferred while the redirector "breaks" the original oplock. The oplock break signals the caching client to write the local file back to the server, flush the local locks, and discard read-ahead data. The break is @@ -4994,12 +4795,12 @@ The actual decision that a user or administrator should consider is whether it is sensible to share amongst multiple users data that will be cached locally on a client. In many cases the answer is no. Deciding when to cache or not cache data is the real question, and thus -"opportunistic locking" should be treated as a toggle for client-side -caching. Turn it "ON" when client-side caching is desirable and -reliable. Turn it "OFF" when client-side caching is redundant, +"opportunistic locking" should be treated as a toggle for client-side +caching. Turn it "ON" when client-side caching is desirable and +reliable. Turn it "OFF" when client-side caching is redundant, unreliable, or counter-productive.

    -Opportunistic locking is by default set to "on" by Samba on all +Opportunistic locking 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 @@ -5051,7 +4852,7 @@ In mission critical high availability environments, careful attention should be given to opportunistic locking. Ideally, comprehensive testing should be done with all affected applications with oplocks enabled and disabled. -

    Exclusively Accessed Shares

    +

    Exclusively Accessed Shares

    Opportunistic locking 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 opportunistic locking is the local @@ -5060,7 +4861,7 @@ mechanism will cause a delay.

    Home directories are the most obvious examples of where the performance benefit of opportunistic locking 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 opportunistic locking enabled, the potential for delays and resulting perceived poor performance increases. When multiple users are accessing a file on a @@ -5072,17 +4873,17 @@ 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

    -Local Unix and NFS clients access files without a mandatory +

    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 -that has a file cached. Local Unix or NFS file access can therefore +that has a file cached. Local UNIX or NFS file access can therefore write to a file that has been cached by a Windows client, which exposes the file to likely data corruption.

    -If files are shared between Windows clients, and either local Unix +If files are shared between Windows clients, and either local UNIX or NFS users, then turn opportunistic locking off. -

    Slow and/or Unreliable Networks

    +

    Slow and/or Unreliable Networks

    The biggest potential performance improvement for opportunistic locking occurs when the client-side caching of reads and writes delivers the most differential over sending those reads and writes over the wire. @@ -5097,7 +4898,7 @@ the most advantageous scenario to utilize opportunistic locking. If the network is slow, unreliable, or a WAN, then do not configure opportunistic locking if there is any chance of multiple users regularly opening the same file. -

    Multi-User Databases

    +

    Multi-User Databases

    Multi-user databases clearly pose a risk due to their very nature - they are typically heavily accessed by numerous users at random intervals. Placing a multi-user database on a share with opportunistic @@ -5105,7 +4906,7 @@ locking 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 opportunistic locking 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 SMB data stores. PDM applications manage multi-user @@ -5118,8 +4919,8 @@ 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 oplock management, by disabling opportunistic locking on the share. -

    Beware of Force User

    -Samba includes an smb.conf parameter called force user that changes +

    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 opportunistic locking is enabled on a share, the change in user access causes an oplock break to be sent @@ -5131,26 +4932,26 @@ to overcome the lost oplock break.

    Avoid the combination of the following:

    • - force user in the smb.conf share configuration. + force user in the smb.conf share configuration.

    • Slow or unreliable networks

    • Opportunistic Locking Enabled -

    Advanced Samba Opportunistic Locking Parameters

    +

    Advanced Samba Opportunistic Locking Parameters

    Samba provides opportunistic locking parameters that allow the administrator to adjust various properties of the oplock mechanism to account for timing and usage levels. These parameters provide good versatility for implementing oplocks in environments where they would likely cause problems. The parameters are: -oplock break wait time, -oplock contention limit. +oplock break wait time, +oplock contention limit.

    For most users, administrators, and environments, if these parameters are required, then the better option is to simply 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." +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 @@ -5180,10 +4981,10 @@ In mission critical high availability environments, careful attention should be given to opportunistic locking. Ideally, comprehensive testing should be done with all affected applications with oplocks enabled and disabled. -

    Samba Opportunistic Locking Control

    +

    Samba Opportunistic Locking Control

    Opportunistic Locking 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 defacto locking feature. +file locking, so is considered a de facto locking feature. Opportunistic Locking is actually part of the Windows client file caching mechanism. It is not a particularly robust or reliable feature when implemented on the variety of customized networks that exist in @@ -5202,7 +5003,7 @@ file, the first client receives a break and must synchronise the file back to th This can give significant performance gains in some cases; some programs insist on synchronising the contents of the entire file back to the server for a single change.

    -Level1 Oplocks (aka just plain "oplocks") is another term for opportunistic locking. +Level1 Oplocks (aka just plain "oplocks") is another term for opportunistic locking.

    Level2 Oplocks provides opportunistic locking for a file that will be treated as read only. Typically this is used on files that are read-only or @@ -5214,7 +5015,7 @@ file locking with the under lying OS, SGI IRIX and Linux are the only two OS's t oplock aware at this time.

    Unless your system supports kernel oplocks, you should disable oplocks if you are -accessing the same files from both Unix/Linux and SMB clients. Regardless, oplocks should +accessing the same files from both UNIX/Linux and SMB clients. Regardless, oplocks should always be disabled if you are sharing a database file (e.g., Microsoft Access) between multiple clients, as any break the first client receives will affect synchronisation of the entire file (not just the single record), which will result in a noticeable performance @@ -5230,29 +5031,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 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 @@ -5265,11 +5060,8 @@ 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.

    -

    -[global]
-kernel oplocks = yes
-

    -The default is "no". +

    kernel oplocks = yes

    +The default is "no".

    Veto OpLocks is an smb.conf parameter that identifies specific files for which Oplocks are disabled. When a Windows client opens a file that @@ -5283,41 +5075,26 @@ 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:

    -

    <title>Example Veto OpLock Settings</title>
-[global]
-        veto oplock files = /filename.htm/*.txt/
-
-[share_name]
-        veto oplock files = /*.exe/filename.ext/
-

    +

    Example 14.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 + 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 +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:

    -

    -[global]
-          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 number of contending clients reaches the limit specified by the -parameter. Samba recommends "DO NOT CHANGE THIS PARAMETER UNLESS YOU -HAVE READ AND UNDERSTOOD THE SAMBA OPLOCK CODE." Oplock Break +parameter. Samba recommends "DO NOT CHANGE THIS PARAMETER UNLESS YOU +HAVE READ AND UNDERSTOOD THE SAMBA OPLOCK CODE." Oplock Break Contention Limit can be enable on a per-share basis, or globally for the entire server, in the smb.conf file:

    -

    -[global]
-          oplock break contention limit =  2 (default)
-
-[share_name]
-         oplock break contention limit =  2 (default)
-

    -

    MS Windows Opportunistic Locking and Caching Controls

    +

    Example 14.2. 

    [global]
    oplock break contention limit = 2 (default)
    [share_name]
    oplock break contention limit = 2 (default)

    +

    MS Windows Opportunistic Locking and Caching Controls

    There is a known issue when running applications (like Norton Anti-Virus) 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 @@ -5409,7 +5186,7 @@ An illustration of how level II oplocks work: 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
 
@@ -5418,7 +5195,7 @@ An illustration of how level II oplocks work:

    Indicates whether the redirector should use opportunistic-locking (oplock) 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
 
@@ -5447,8 +5224,8 @@ the server disables raw I/O and opportunistic locking for this connection.
 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

    -If you have applied all of the settings discussed in this paper but data corruption problems +

    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:

    We have credible reports from developers that faulty network hardware, such as a single @@ -5458,7 +5235,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. @@ -5488,18 +5265,23 @@ so far: report on https://bugzilla.samba.org without delay. Make sure that you give as much information as you possibly can to help isolate the cause and to allow reproduction of the problem (an essential step in problem isolation and correction). -

    locking.tdb error messages

    - 

    -	> We are seeing lots of errors in the samba logs like:
-	>
-	>    tdb(/usr/local/samba_2.2.7/var/locks/locking.tdb): rec_read bad magic
-	> 0x4d6f4b61 at offset=36116
-	>
-	> What do these mean?
-

    +

    locking.tdb error messages

    + “ + We are seeing lots of errors in the samba logs like: +” +

    +tdb(/usr/local/samba_2.2.7/var/locks/locking.tdb): rec_read bad magic
+ 0x4d6f4b61 at offset=36116
+

    +“ + What do these mean? + ”

    Corrupted tdb. Stop all instances of smbd, delete locking.tdb, restart smbd. -

    Additional Reading

    +

    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 + Microsoft Knowledge Base article 811492.

    Additional Reading

    You may want to check for an updated version of this white paper on our Web site from time to time. Many of our white papers are updated as information changes. For those papers, the Last Edited date is always at the top of the paper. @@ -5511,27 +5293,27 @@ Windows Base Services > Files and I/O > SDK Documentation > File Storag > About File Systems > Opportunistic Locks, Microsoft Corporation. http://msdn.microsoft.com/library/en-us/fileio/storage_5yk3.asp

    -Microsoft Knowledge Base Article Q224992 "Maintaining Transactional Integrity with OPLOCKS", +Microsoft Knowledge Base Article Q224992 "Maintaining Transactional Integrity with OPLOCKS", Microsoft Corporation, April 1999, http://support.microsoft.com/default.aspx?scid=kb;en-us;Q224992.

    -Microsoft Knowledge Base Article Q296264 "Configuring Opportunistic Locking in Windows 2000", +Microsoft Knowledge Base Article Q296264 "Configuring Opportunistic Locking in Windows 2000", Microsoft Corporation, April 2001, http://support.microsoft.com/default.aspx?scid=kb;en-us;Q296264.

    -Microsoft Knowledge Base Article Q129202 "PC Ext: Explanation of Opportunistic Locking on Windows NT", +Microsoft Knowledge Base Article Q129202 "PC Ext: Explanation of Opportunistic Locking on Windows NT", Microsoft Corporation, April 1995, http://support.microsoft.com/default.aspx?scid=kb;en-us;Q129202. -

    Chapter 15. 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 a IPC$ share deny
    NTLMv2 Security
    Upgrading Samba
    Common Errors
    Smbclient works on localhost, but the network is dead
    Why can users access home directories of other users?

    Introduction

    +

    Chapter 15. 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 a IPC$ share deny
    NTLMv2 Security
    Upgrading Samba
    Common Errors
    Smbclient works on localhost, but the network is dead
    Why can users access home directories of other users?

    Introduction

    This note was attached to the Samba 2.2.8 release notes as it contained an important security fix. The information contained here applies to Samba installations in general.

    -A new apprentice reported for duty to the Chief Engineer of a boiler house. He said, "Here I am, -if you will show me the boiler I'll start working on it." Then engineer replied, "You're leaning -on it!" +A new apprentice reported for duty to the Chief Engineer of a boiler house. He said, "Here I am, +if you will show me the boiler I'll start working on it." Then engineer replied, "You're leaning +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 level at which security principals must be observed in order to render a site at least moderately secure. These are: the perimeter firewall, the configuration of the host server that is running Samba, and Samba itself. @@ -5541,60 +5323,52 @@ the latest protocols to permit more secure MS Windows file and print operations.

    Samba may be secured from connections that originate from outside the local network. This may 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 +known as "tcpwrappers", or it may be done be using interface based exclusion so that smbd will bind only to specifically permitted interfaces. It is also -possible to set specific share or resource based exclusions, eg: on the IPC$ -auto-share. The IPC$ share is used for browsing purposes as well as to establish +possible to set specific share or resource based exclusions, eg: on the [IPC$] +auto-share. 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 way of setting Access Control Entries in an Access Control List on the shares themselves. This is discussed in the chapter on File, Directory and Share Access Control. -

    Technical Discussion of Protective Measures and Issues

    +

    Technical Discussion of Protective Measures and Issues

    The key challenge of security is the fact 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 that 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 for outside your immediate network. By default Samba will accept 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 only + 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 only allow access to your server 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 only allow SMB connections 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 a 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 [globals] section put: - 

    -		valid users = @smbusers, jacko
-

    + method may be of use. In the smb.conf [global] section put: +

    valid users = @smbusers, jacko

    What this does is, it restricts all server access to either the user jacko or to members of the system group smbusers. -

    Using interface protection

    +

    Using interface protection

    By default Samba will accept connections on any network interface that it finds on your system. That means if you have a 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 behaviour using options like the following: - 

    -		interfaces = eth* lo
-		bind interfaces only = yes
-

    +

    interfaces = eth* lo
    bind interfaces only = yes

    This tells Samba to only listen for connections on interfaces with a name starting with 'eth' such as eth0, eth1, plus on the loopback interface called 'lo'. The name you will need to use depends on what @@ -5606,7 +5380,7 @@ before someone will find yet another vulnerability. connection refused reply. In that case no Samba code is run at all as the operating system has been told not to pass connections from that interface to any samba process. -

    Using a firewall

    +

    Using a firewall

    Many people use a firewall to deny access to services that they don't want exposed outside their network. This can be a very good idea, although I would recommend using it in conjunction with the above @@ -5619,7 +5393,7 @@ before someone will find yet another vulnerability. The last one is important as many older firewall setups may not be aware of it, given that this port was only added to the protocol in recent years. -

    Using a IPC$ share deny

    +

    Using a IPC$ share deny

    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 @@ -5627,11 +5401,7 @@ before someone will find yet another vulnerability. hosts.

    To do that 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 would tell Samba that IPC$ connections are not allowed from anywhere but the two listed places (localhost and a local subnet). Connections to other shares would still be allowed. As the @@ -5646,42 +5416,44 @@ before someone will find yet another vulnerability.

    This is not recommended unless you cannot use one of the other methods listed above for some reason. -

    NTLMv2 Security

    +

    NTLMv2 Security

    To configure NTLMv2 authentication the following registry keys are worth knowing about:

    - 

    +		
     		[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa]
-		"lmcompatibilitylevel"=dword:00000003
-
+		"lmcompatibilitylevel"=dword:00000003
+		
    
+	
    
 		0x3 - Send NTLMv2 response only. Clients will use NTLMv2 authentication,
 		use NTLMv2 session security if the server supports it. Domain
 		controllers accept LM, NTLM and NTLMv2 authentication.
-
+	
    
+		
     		[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa\MSV1_0]
-		"NtlmMinClientSec"=dword:00080000
-
+		"NtlmMinClientSec"=dword:00080000
+		
    
+	
    
 		0x80000 - NTLMv2 session security. If either NtlmMinClientSec or
 		NtlmMinServerSec is set to 0x80000, the connection will fail if NTLMv2
 		session security is not 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 when a security vulnerability -is discovered. -

    Common Errors

    +is discovered. Check with your OS vendor for OS specific upgrades. +

    Common Errors

    If all of samba and host platform configuration were really as intuitive as one might like then this section would not be necessary. Security issues are often vexing for a support person to resolve, not because of the complexity of the problem, but for reason that 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 very common problem. Red Hat Linux (as do others) will install a default firewall. With the default firewall in place only traffic on the loopback adapter (IP address 127.0.0.1) will be allowed through the firewall.

    The solution is either to remove the firewall (stop it) or to modify the firewall script to allow SMB networking traffic through. See section above in this chapter. -

    Why can users access home directories of other users?

    +

    Why can users access home directories of other users?

    “ 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 @@ -5710,27 +5482,24 @@ out to be a security problem request are totally convinced that the problem is w the policies and permissions he or she desires.

    Samba does allow the setup you require when you have set the - only user = yes option on the share, is that you have not set the + only user = yes option on the share, is that you have not set the valid users list for the share.

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

    -	valid users = %S
-

    +

    valid users = %S

    to the definition of the [homes] share, as recommended in the smb.conf man page. -

    Chapter 16. Interdomain Trust Relationships

    John H. Terpstra

    Samba Team

    Rafal Szczesniak

    Samba Team

    April 3, 2003

    Table of Contents

    Features and Benefits
    Trust Relationship Background
    Native MS Windows NT4 Trusts Configuration
    NT4 as the Trusting Domain (ie. creating the trusted account)
    NT4 as the Trusted Domain (ie. creating trusted account's password)
    Configuring Samba NT-style Domain Trusts
    Samba-3 as the Trusting Domain
    Samba-3 as the Trusted Domain
    Common Errors
    Tell me about Trust Relationships using Samba

    +

    Chapter 16. 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
    Inter-Domain 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

    Samba-3 supports NT4 style domain trust relationships. This is feature that many sites will want to use if they migrate to Samba-3 from and NT4 style domain and do NOT want to adopt Active Directory or an LDAP based authentication back end. This section explains some background information regarding trust relationships and how to create them. It is now -possible for Samba-3 to NT4 trust (and vice versa), as well as Samba3 to Samba3 trusts. -

    Features and Benefits

    +possible for Samba-3 to trust NT4 (and vice versa), as well as to create Samba3-to-Samba3 +trusts. +

    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 similar scalability as is possible with MS Windows NT4. @@ -5740,10 +5509,10 @@ database such as LDAP, and given it's ability to run in Primary as well as Backu modes, the administrator would be well advised to consider alternatives to the use of Interdomain trusts simply because by the very nature of how this works it 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.x/4.0 type security domains employ a non-hierarchical security structure. The limitations of this architecture as it affects the scalability of MS Windows networking -in large organisations is well known. Additionally, the flat-name space that results from +in large organisations is well known. Additionally, the flat namespace that results from this design significantly impacts the delegation of administrative responsibilities in large and diverse organisations.

    @@ -5769,45 +5538,91 @@ relationship, and WHITE and BLUE have a trust relationship, then it holds that t implied trust between the RED and BLUE domains. ie: 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 above, 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

    -There are two steps to creating an interdomain trust relationship. -

    NT4 as the Trusting Domain (ie. creating the trusted account)

    +

    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

    For MS Windows NT4, all domain trust relationships are configured using the -Domain User Manager. To affect a two way trust relationship it is -necessary for each domain administrator to make available (for use by an external domain) it's -security resources. This is done from the Domain User Manager Policies entry on the menu bar. -From the Policy menu, select Trust Relationships, then -next to the lower box that is labelled Permitted to Trust this Domain are two -buttons, Add and Remove. The Add -button will open a panel in which needs to be entered the remote domain that will be able to assign -user rights to your domain. In addition it is necessary to enter a password -that is specific to this trust relationship. The password needs to be -typed twice (for standard confirmation). -

    NT4 as the Trusted Domain (ie. creating trusted account's password)

    +Domain User Manager. This is done from the Domain User Manager Policies +entry on the menu bar. From the Policy menu, select +Trust Relationships. Next to the lower box labelled +Permitted to Trust this Domain are two buttons, Add +and Remove. The Add button will open a panel in which +to enter the name of the remote domain that will be able to assign access rights to users in +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

    + 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 will launch the Domain User Manager, from the menu select Policies, then select Trust Relationships, then click on the Add button that is next to the box that is labelled Trusted Domains. A panel will open in which must be entered the name of the remote domain as well as the password assigned to that trust. -

    Configuring Samba NT-style Domain Trusts

    +

    Inter-Domain 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: +

    Figure 16.1. Trusts overview

    Trusts overview

    • + DomA (completes the trust connection) Trusts DomB +

    • + DomA is the Trusting domain +

    • + DomB is the Trusted domain (originates the trust account) +

    • + Users in DomB can access resources in DomA +

    • + Users in DomA can NOT access resources in DomB +

    • + Global groups from DomB CAN be used in DomA +

    • + Global groups from DomA can NOT be used in DomB +

    • + DomB DOES appear in the logon dialog box on client workstations in DomA +

    • + DomA does NOT appear in the logon dialog box on client workstations in DomB +

    • + Users / Groups in a trusting domain can NOT be granted rights, permissions or access + to a trusted domain. +

    • + The trusting domain CAN access and use accounts (Users / Global Groups) in the + trusted domain. +

    • + Administrators of the trusted domain CAN be granted admininstrative rights in the + trusting domain. +

    • + Users in a trusted domain CAN be given rights and privileges in the trusting + domain. +

    • + Trusted domain Global Groups CAN be given rights and permissions in the trusting + domain. +

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

    This description is meant to be a fairly short introduction about how to set up a Samba server so that it could participate in interdomain trust relationships. Trust relationship support in Samba is in its early stage, so lot of things don't work yet.

    -Each of the procedures described below is treated as they were performed with Windows NT4 Server on -one end. 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 below leads to trust -between domains in purely Samba environment. -

    Samba-3 as the Trusting Domain

    -In order to set the Samba PDC to be the trusted party of the relationship first you need -to create special account for the domain that will be the trusting party. To do that, +Each of the procedures described below 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 below 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 very similar to creating a trusted machine account. Suppose, your domain is called SAMBA, and the remote domain is called RUMBA. The first step @@ -5815,9 +5630,9 @@ will be to issue this command from your favourite shell: 

     root#  smbpasswd -a -i rumba
-	New SMB password: XXXXXXXX
-	Retype SMB password: XXXXXXXX
-	Added user rumba$
+New SMB password: XXXXXXXX
+Retype SMB password: XXXXXXXX
+Added user rumba$

    where -a means to add a new account into the @@ -5830,29 +5645,29 @@ After issuing this command you'll 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 depending on your configuration) and see that account's name is -really RUMBA$ and it has 'I' flag in the flags field. Now you're ready to confirm +(in the standard way as appropriate for your configuration) and see that account's name is +really RUMBA$ and it has the 'I' flag set in the flags field. Now you're ready to confirm the trust by establishing it from Windows NT Server. -

    -Open User Manager for Domains and from menu -Policies select Trust Relationships.... -Right beside Trusted domains list box press the +

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

    Samba-3 as the Trusted 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 NT-controlled domain is called RUMBA.

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

    +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 Trusted Domains box press the Add -button, and type in the name of the trusted domain (SAMBA) and password securing +Now, next to the Trusted 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 @@ -5864,61 +5679,60 @@ Using your favourite shell while being 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. -Do not worry if you see an error message that mentions a returned code of -NT_STATUS_NOLOGON_INTERDOMAIN_TRUST_ACCOUNT. It means the +Do not worry if you see an error message that mentions a return code of +NT_STATUS_NOLOGON_INTERDOMAIN_TRUST_ACCOUNT. It means the password you gave is correct and the NT4 Server says the account is ready for interdomain connection and not for ordinary -connection. After that, be patient it can take a while (especially -in large networks), you should see the Success message. +connection. After that, be patient; it can take a while (especially +in large networks), but eventually you should see the Success message. Congratulations! Your trust relationship has just been established.

    Note

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

    Common Errors

    +

    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 above, 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 trusts are not transitive, if you want +your users to have access to multiple mixed-mode domains in your AD forest, you will need to +repeat this process for each of those domains. With Active Directory Domains +and Trusts open, right-click on the name of the Active Directory domain that +will trust our Samba domain and choose Properties, then click on +the Trusts tab. In the upper part of the panel, you will see a list box +labelled Domains trusted by this domain:, and an +Add... button next to it. Press this button, and just as with NT4, you +will be prompted for the trusted domain name and the relationship 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 acess to resources in the AD domain. +

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

    Tell me about Trust Relationships using Samba

    - Like many, I administer multiple LANs connected together using NT trust - relationships. This was implemented about 4 years ago. I now have the - occasion to consider performing this same task again, but this time, I - would like to implement it solely through samba - no Microsoft PDCs - anywhere. -

    - I have read documentation on samba.org regarding NT-style trust - relationships and am now wondering, can I do what I want to? I already - have successfully implemented 2 samba servers, but they are not PDCs. - They merely act as file servers. I seem to remember, and it appears to - be true (according to samba.org) that trust relationships are a - challenge. -

    - Please provide any helpful feedback that you may have. -

    - These are almost complete in Samba 3.0 snapshots. The main catch - is getting winbindd to be able to allocate UID/GIDs for trusted - users/groups. See the updated Samba HOWTO collection for more - details. -

    Chapter 17. Hosting a Microsoft Distributed File System tree on Samba

    Shirish Kalele

    Samba Team & Veritas Software


    +

    Chapter 17. Hosting a Microsoft Distributed File System tree on Samba

    Shirish Kalele

    Samba Team & Veritas Software



    -

    12 Jul 2000

    Table of Contents

    Features and Benefits
    Common Errors

    Features and Benefits

    +

    12 Jul 2000

    Table of Contents

    Features and Benefits
    Common Errors

    Features and Benefits

    The Distributed File System (or 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 etc.

    - For information about DFS, refer to - - Microsoft documentation at http://www.microsoft.com/NTServer/nts/downloads/winfeatures/NTSDistrFile/AdminGuide.asp. + 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 + This document explains how to host a DFS tree on a UNIX machine (for DFS-aware clients to browse) using Samba.

    - To enable SMB-based DFS for Samba, configure it with the --with-msdfs + To enable SMB-based DFS for Samba, configure it with the --with-msdfs option. Once built, 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 + 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, @@ -5927,23 +5741,14 @@ distributed trusted domains. DFS trees on Samba work with all DFS-aware clients ranging from Windows 95 to 200x.

    Here's an example of setting up a DFS tree on a Samba server. - 

    -# The smb.conf file:
-[global]
-	netbios name = SMOKEY
-	host msdfs   = yes
-
-[dfs]
-	path = /export/dfsroot
-	msdfs root = yes
-

    In the /export/dfsroot directory we set up our dfs links to +

    Example 17.1. smb.conf with DFS configured

    [global]
    netbios name = GANDALF
    host msdfs = yes
    [dfs]
    path = /export/dfsroot
    msdfs root = yes

    In the /export/dfsroot directory we set up our 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
-

    You should set up the permissions and ownership of +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 +

    You should set up the permissions and ownership of the directory acting as the DFS root such that only designated users can create, delete or modify the msdfs links. Also note that symlink names should be all lowercase. This limitation exists @@ -5952,22 +5757,21 @@ distributed trusted domains. 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 + 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 + 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 that only designated users can - modify the symbolic links in the directory.

    Chapter 18. Classical Printing Support

    Kurt Pfeifle

    Danka Deutschland GmbH

    Gerald (Jerry) Carter

    Samba Team

    May 32, 2003

    Table of Contents

    Features and Benefits
    Technical Introduction
    What happens if you send a Job from a Client
    Printing Related Configuration Parameters
    Parameters Recommended for Use
    Parameters for Backwards Compatibility
    Parameters no longer in use
    A simple Configuration to Print with Samba-3
    Verification of "Settings in Use" with testparm
    A little Experiment to warn you
    Extended Sample Configuration to Print with Samba-3
    Detailed Explanation of the Example's Settings
    The [global] Section
    The [printers] Section
    Any [my_printer_name] Section
    Print Commands
    Default Print Commands for various Unix Print Subsystems
    Setting up your own Print Commands
    Innovations in Samba Printing since 2.2
    Client Drivers on Samba Server for Point'n'Print
    The [printer$] Section is removed from Samba-3
    Creating the [print$] Share
    Parameters in the [print$] Section
    Subdirectory Structure in [print$]
    Installing Drivers into [print$]
    Setting Drivers for existing Printers with a Client GUI
    Setting Drivers for existing Printers with -rpcclient
    "The Proof of the Pudding lies in the Eating" (Client Driver Install -Procedure)
    The first Client Driver Installation
    IMPORTANT! Setting Device Modes on new Printers
    Further Client Driver Install Procedures
    Always make first Client Connection as root or "printer admin"
    Other Gotchas
    Setting Default Print Options for the Client Drivers
    Supporting large Numbers of Printers
    Adding new Printers with the Windows NT APW
    Weird Error Message Cannot connect under a -different Name
    Be careful when assembling Driver Files
    Samba and Printer Ports
    Avoiding the most common Misconfigurations of the Client Driver
    The Imprints Toolset
    What is Imprints?
    Creating Printer Driver Packages
    The Imprints Server
    The Installation Client
    Add Network Printers at Logon without User Interaction
    The addprinter command
    Migration of "Classical" printing to Samba-3
    Publishing Printer Information in Active Directory or LDAP
    Common Errors and Problems
    I give my root password but I don't get access
    My printjobs get spooled into the spooling directory, but then get lost

    Features and Benefits

    + modify the symbolic links in the directory.

    Chapter 18. Classical Printing Support

    Kurt Pfeifle

    Danka Deutschland GmbH

    Gerald (Jerry) Carter

    Samba Team

    May 31, 2003

    Table of Contents

    Features and Benefits
    Technical Introduction
    What happens if you send a Job from a Client
    Printing Related Configuration Parameters
    Parameters Recommended for Use
    A simple Configuration to Print
    Verification of "Settings in Use" with testparm
    A little Experiment to warn you
    Extended Sample Configuration to Print
    Detailed Explanation of the Example's Settings
    The [global] Section
    The [printers] Section
    Any [my_printer_name] Section
    Print Commands
    Default Print Commands for various UNIX Print Subsystems
    Setting up your own Print Commands
    Innovations in Samba Printing since 2.2
    Client Drivers on Samba Server for Point'n'Print
    The [printer$] Section is removed from Samba 3
    Creating the [print$] Share
    Parameters in the [print$] Section
    Subdirectory Structure in [print$]
    Installing Drivers into [print$]
    Setting Drivers for existing Printers with a Client GUI
    Setting Drivers for existing Printers with +rpcclient
    Client Driver Install Procedure
    The first Client Driver Installation
    IMPORTANT! Setting Device Modes on new Printers
    Further Client Driver Install Procedures
    Always make first Client Connection as root or "printer admin"
    Other Gotchas
    Setting Default Print Options for the Client Drivers
    Supporting large Numbers of Printers
    Adding new Printers with the Windows NT APW
    Weird Error Message Cannot connect under a +different Name
    Be careful when assembling Driver Files
    Samba and Printer Ports
    Avoiding the most common Misconfigurations of the Client Driver
    The Imprints Toolset
    What is Imprints?
    Creating Printer Driver Packages
    The Imprints Server
    The Installation Client
    Add Network Printers at Logon 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 don't get access
    My printjobs 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-3.0 print service may be run on a Standalone or a Domain +A Samba print service may be run on a Standalone or a Domain member server, side by side with file serving functions, or on a dedicated print server. It can be made as tight or as loosely secured as needs dictate. Configurations may be simple or complex. Available @@ -5975,10 +5779,10 @@ authentication schemes are essentially the same as described for file services in previous chapters. Overall, Samba's printing support is now able to replace an NT or Windows 2000 print server full-square, with additional benefits in many cases. Clients may download and -install drivers and printers through their familiar "Point'n'Print" -mechanism. Printer installations executed by "Logon Scripts" are no +install drivers and printers through their familiar "Point'n'Print" +mechanism. Printer installations executed by "Logon Scripts" are no problem. Administrators can upload and manage drivers to be used by -clients through the familiar "Add Printer Wizard". As an additional +clients through the familiar "Add Printer Wizard". As an additional benefit, driver and printer management may be run from the command line or through scripts, making it more efficient in case of large numbers of printers. If a central accounting of print jobs (tracking every @@ -5991,24 +5795,24 @@ implemented by the more traditional UNIX (BSD- and System V-style) printing systems. Many things apply to CUPS, the newer Common UNIX Printing System, too; so if you use CUPS, you might be tempted to jump to the next chapter -- but you will certainly miss a few things if you -do so. Better read this chapter too. +do so. Better to read this chapter too.

    Note

    Most of the given examples have been verified on Windows XP Professional clients. Where this document describes the responses to commands given, bear in mind that Windows 2000 clients are very similar, but may differ in details. Windows NT 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 +subsystem of the UNIX OS it runs on. Samba is a "middleman". It takes printfiles from Windows (or other SMB) clients and passes them to the real printing system for further processing. Therefore it needs to -"talk" to two sides: to the Windows print clients and to the Unix +"talk" to two sides: to the Windows print clients and to the UNIX printing system. Hence we must differentiate between the various client OS types each of which behave differently, as well as the various UNIX print subsystems, which themselves have different features and are accessed differently. This part of the Samba HOWTO -Collection deals with the "traditional" way of Unix printing first; +Collection deals with the "traditional" way of UNIX printing first; the next chapter covers in great detail the more modern Common UNIX Printing System (CUPS). @@ -6016,113 +5820,104 @@ the next chapter covers in great detail the more modern

    Important

    CUPS users, be warned: don't just jump on to the next chapter. You might miss important information contained only here!

    -

    What happens if you send a Job from a Client

    +

    What happens if you send a Job from a Client

    To successfully print a job from a Windows client via a Samba print server to a UNIX printer, there are 6 (potentially 7) stages: -

    1. Windows opens a connection to the printershare

    2. Samba must authenticate the user

    3. Windows sends a copy of the printfile over the network +

      1. Windows opens a connection to the printer share

      2. Samba must authenticate the user

      3. Windows sends a copy of the printfile over the network into Samba's spooling area

      4. Windows closes the connection again

      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 +to the UNIX print subsystem's spooling area

      7. The UNIX print subsystem processes the print job

      8. The printfile may need to be explicitly deleted -from the Samba spooling area.

    Printing Related Configuration Parameters

    +from the Samba spooling area.

    Printing Related Configuration Parameters

    There are a number of configuration parameters in controlling Samba's printing behaviour. Please also refer to the man page for smb.conf to acquire an overview about these. As with other parameters, there are -Global Level (tagged with a "G" in the listings) and -Service Level ("S") parameters. +Global Level (tagged with a "G" in the listings) and +Service Level ("S") parameters.

    Service Level Parameters

    These may go into the -[global] section of -. In this case they define the default +[global] section of smb.conf. +In this case they define the default behaviour of all individual or service level shares (provided those don't have a different setting defined for the same parameter, thus overriding the global default).

    Global Parameters

    These may not go into individual -shares. If they go in by error, the "testparm" utility can discover -this (if you run it) and tell you so.

    Parameters Recommended for Use

    The following smb.conf parameters directly -related to printing are used in Samba-3. See also the +shares. If they go in by error, the "testparm" utility can discover +this (if you run it) and tell you so.

    Parameters Recommended for Use

    The following smb.conf parameters directly +related to printing are used in Samba. See also the smb.conf man page for detailed explanations: -

    List of printing related parameters in Samba-3.  -

    Global level parameters:

    • addprinter command (G)

    • deleteprinter command (G)

    • disable spoolss (G)

    • enumports command (G)

    • load printers (G)

    • lpq cache time (G)

    • os2 driver map (G)

    • printcap name (G), printcap (G)

    • show add printer wizard (G)

    • total print jobs (G)

    • use client driver (G)

    - -

    Service level parameters:

    • hosts allow (S)

    • hosts deny (S)

    • lppause command (S)

    • lpq command (S)

    • lpresume command (S)

    • lprm command (S)

    • max print jobs (S)

    • min print space (S)

    • print command (S)

    • printable (S), print ok (S)

    • printer name (S), printer (S)

    • printer admin (S)

    • printing = [cups|bsd|lprng...] (S)

    • queuepause command (S)

    • queueresume command (S)

    • total print jobs (S)

    +

    Global level parameters: addprinter command, +deleteprinter command, +disable spoolss, +enumports command, +load printers, +lpq cache time, +os2 driver map, +printcap name, printcap, +show add printer wizard, +total print jobs, +use client driver. +

    Service level parameters: hosts allow, +hosts deny, +lppause command, +lpq command, +lpresume command, +lprm command, +max print jobs, +min print space, +print command, +printable, print ok , +printer name, printer, +printer admin, +printing = [cups|bsd|lprng...], +queuepause command, +queueresume command, +total print jobs.

    Samba's printing support implements the Microsoft Remote Procedure Calls (MS-RPC) methods for printing. These are used by Windows NT (and -later) print servers. The old "LanMan" protocol is still supported as +later) print servers. The old "LanMan" protocol is still supported as a fallback resort, and for older clients to use. More details will follow further beneath. -

    Parameters for Backwards Compatibility

    -Two new parameters that were added in Samba 2.2.2, are still present -in Samba-3.0. Both of these options are described in the -smb.conf man page and are disabled by -default. Use them with caution! -

    disable spoolss(G)

    This is -provided for better support of Samba 2.0.x backwards capability. It -will disable Samba's support for MS-RPC printing and yield identical -printing behaviour to Samba 2.0.x.

    use client driver (G)

    was provided -for using local printer drivers on Windows NT/2000 clients. It does -not apply to Windows 95/98/ME clients.

    Parameters "for backward compatibility only", use with caution.  -

    • disable spoolss (G)

    • use client driver (S)

    -

    Parameters no longer in use

    -Samba users upgrading from 2.2.x to 3.0 need to be aware that some -previously available settings are no longer supported (as was -announced some time ago). Here is a list of them: -

    "old" parameters, removed in Samba-3.  -The following smb.conf parameters have been -deprecated already in Samba 2.2 and are now completely removed from -Samba-3. You cannot use them in new 3.0 installations: - -

    • printer driver file (G)

    • total print jobs (G)

    • postscript (S)

    • printer driver (S)

    • printer driver location (S)

    -

    A simple Configuration to Print with Samba-3

    +

    A simple Configuration to Print

    Here is a very simple example configuration for print related settings -in the file. If you compare it with your -own system's , you probably find some +in the file. If you compare it with your own system's , you probably find some additional parameters included there (as pre-configured by your OS vendor). Further below is a discussion and explanation of the parameters. Note, that this example doesn't use many parameters. However, in many environments these are enough to provide a valid - which enables all clients to print. -

    - [global]
-         printing = bsd
-         load printers = yes
-
- [printers]
-         path = /var/spool/samba
-         printable = yes
-         public = yes
-         writable = no
-

    -This is only an example configuration. Many settings, if not -explicitly set to a specific value, are used and set by Samba -implicitly to its own default, because these have been compiled in. -To see all settings, let root use the testparm -utility. testparm also gives warnings if you have -mis-configured certain things. Its complete output is easily 340 lines -and more. You may want to pipe it through a pager program. +smb.conf file which enables all clients to print. +

    Example 18.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. On the whole 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 setting, both default as well as smb.conf file +settings. Testparm gives warnings for all mis-configured +settings. The complete output is easily 340 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. It has been explained elsewhere in this document. A short -reminder: It even tolerates some spelling errors (like "browsable" -instead of "browseable"). Most spelling is case-insensitive. Also, you -can use "Yes|No" or "True|False" for boolean settings. Lists of names +reminder: It even tolerates some spelling errors (like "browsable" +instead of "browseable"). Most spelling is case-insensitive. Also, you +can use "Yes|No" or "True|False" for boolean settings. Lists of names may be separated by commas, spaces or tabs. -

    Verification of "Settings in Use" with testparm

    +

    Verification of "Settings in Use" with testparm

    To see all (or at least most) printing related settings in Samba, including the implicitly used ones, try the command outlined below -(hit "ENTER" twice!). It greps for all occurrences of "lp", "print", -"spool", "driver", "ports" and "[" in testparm's output and gives you +(hit "ENTER" twice!). It greps for all occurrences of "lp", "print", +"spool", "driver", "ports" and "[" in testparm's output and gives you a nice overview about the running smbd's print configuration. (Note that this command does not show individually created printer shares, or the spooling paths in each case). Here is the output of my Samba setup, with exactly the same settings in as shown above: 

    -root# testparm -v | egrep "(lp|print|spool|driver|ports|\[)"
+root# testparm -v | egrep "(lp|print|spool|driver|ports|\[)"
  Load smb config files from /etc/samba/smb.conf.simpleprinting
- Processing section "[homes]"
- Processing section "[printers]"
+ Processing section "[homes]"
+ Processing section "[printers]"
  
  [global]
         smb ports = 445 139
@@ -6159,21 +5954,21 @@ as shown above:
 You can easily verify which settings were implicitly added by Samba's
 default behaviour. Don't forget about this point: it may
 be important in your future dealings with Samba.
-
    Note
     testparm in Samba-3.0 behaves differently from 2.2.x: used
-without the "-v" switch it only shows you the settings actually
+
    Note
     testparm in samba 3 behaves differently from 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.
    A little Experiment to warn you
    
+configuration used, add the "-v" parameter to testparm.

    A little Experiment to warn you

    Should you need to troubleshoot at any stage, please always come back -to this point first and verify if "testparm" shows the parameters you +to this point first and verify if "testparm" shows the parameters you expect! To give you an example from personal experience as a warning, -try to just "comment out" the load printers" +try to just "comment out" the load printers" parameter. If your 2.2.x system behaves like mine, you'll see this: 

    -root# grep "load printers" /etc/samba/smb.conf
+root# grep "load printers" /etc/samba/smb.conf
  #      load printers = Yes
-        # This setting is commented ooouuuuut!!
-
-root# testparm -v /etc/samba/smb.conf | egrep "(load printers)"
+ # This setting is commented ooouuuuut!!
+ 
+root# testparm -v /etc/samba/smb.conf | egrep "(load printers)"
         load printers = Yes

    @@ -6182,20 +5977,20 @@ prevent Samba from publishing my printers, it still did! Oh Boy -- it cost me quite some time to find out the reason. But I am not fooled any more... at least not by this ;-) 

    -root# grep -A1 "load printers" /etc/samba/smb.conf
+root# grep -A1 "load printers" /etc/samba/smb.conf
         load printers = No
         # This setting is what I mean!!
  #      load printers = Yes
         # This setting is commented ooouuuuut!!
 
-root# testparm -v smb.conf.simpleprinting | egrep "(load printers)"
+root# testparm -v smb.conf.simpleprinting | egrep "(load printers)"
         load printers = No

    Only when setting the parameter explicitly to -"load printers = No" +"load printers = No" would Samba recognize my intentions. So my strong advice is: -

    • Never rely on "commented out" parameters!

    • Always set it up explicitly as you intend it to +

      • Never rely on "commented out" parameters!

      • Always set it up explicitly as you intend it to behave.

      • Use testparm to uncover hidden settings which might not reflect your intentions.

      You can have a working Samba print configuration with this @@ -6219,8 +6014,8 @@ ask testparm what the Samba print configuration would be, if you used this minimalistic file as your real : 

      -root#  testparm -v /etc/samba/smb.conf-minimal | egrep "(print|lpq|spool|driver|ports|[)"
- Processing section "[printers]"
+root# testparm -v smb.conf-minimal | egrep "(print|lpq|spool|driver|ports|[)"
+ Processing section "[printers]"
  WARNING: [printers] service MUST be printable!
  No path in service printers - using /tmp
 
@@ -6252,8 +6047,8 @@ testparm issued 2 warnings:
 [printers] section as printable,
 and

    • because we didn't tell it which spool directory to use.

    -However, this was not fatal, and Samba-3.0 will default to values that -will work here. But, please!, don't rely on this and don't use this +However, this was not fatal, and samba will default to values that +will work here. Please, don't rely on this and don't use this example! This was only meant to make you careful to design and specify your setup to be what you really want it to be. The outcome on your system may vary for some parameters, since you may have a Samba built @@ -6265,61 +6060,20 @@ comment sign at the front). At first I regarded this as a bug in my Samba version(s). But the man page states: “Internal whitespace in a parameter value is retained verbatim.” This means that a line consisting of, for example, -

    -printing = lprng     #This defines LPRng as the printing system"
-

    -will regard the whole of the string after the "=" +

    # 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. And this is an invalid value that will be ignored, and a default value used instead.] -

    Extended Sample Configuration to Print with Samba-3

    -Here we show a more verbose example configuration for print related -settings in an . Below is a discussion +

    Extended Sample Configuration to Print

    + In the extended BSD configuration example we show a more verbose example configuration for print related + settings in BSD-printing style environment . Below is a discussion and explanation of the various parameters. We chose to use BSD-style printing here, because we guess it is still the most commonly used system on legacy Linux installations (new installs now predominantly have CUPS, which is discussed entirely in the next chapter of this document). Note, that this example explicitly names many parameters -which don't need to be stated because they are set by default. You -might be able to do with a leaner .

    Tip

    -if you read access it with the Samba Web Administration Tool (SWAT), -and then write it to disk again, it will be optimized in a way such -that it doesn't contain any superfluous parameters and comments. SWAT -organizes the file for best performance. Remember that each smbd -re-reads the Samba configuration once a minute, and that each -connection spawns an smbd process of its own, so it is not a bad idea -to optimize the in environments with -hundreds or thousands of clients.

    - [global]
-         printing = bsd
-         load printers = yes
-         show add printer wizard = yes
-         printcap name = /etc/printcap
-         printer admin = @ntadmin, root
-         total 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
-         writeable = no
-         hosts allow = 0.0.0.0
-         hosts deny = turbo_xp, 10.160.50.23, 10.160.51.60
-         guest ok = no
-

    +which don't need to be specified because they are set by default. You +might be able to do with a leaner smb.conf file.

    Example 18.2. Extended configuration with BSD printing

    [global]
    printing = bsd
    load printers = yes
    show add printer wizard = yes
    printcap name = /etc/printcap
    printer admin = @ntadmin, root
    total 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
    writeable = no
    hosts allow = 0.0.0.0
    hosts deny = turbo_xp, 10.160.50.23, 10.160.51.60
    guest ok = no

    This also is only an example configuration. You may not find all the settings in your own (as pre-configured by your OS @@ -6329,32 +6083,32 @@ default, because these have been compiled in. To see all settings, let root use the testparm utility. testparm also gives warnings if you have mis-configured certain things.. -

    Detailed Explanation of the Example's Settings

    +

    Detailed Explanation of the Example's Settings

    Following is a discussion of the settings from above shown example. -

    The [global] Section

    +

    The [global] Section

    The [global] section is one of 4 special sections (along with [[homes], [printers] and [print$]...) It contains all parameters which apply to the server as a whole. It is the place for parameters which -have only a "global" meaning (G). It may also contain service level -parameters (S) which then define default settings for all other +have only a "global" meaning. It may also contain service level +parameters which then define default settings for all other sections and shares. This way you can simplify the configuration and avoid setting the same value repeatedly. (Within each individual -section or share you may however override these globally set "share -level" settings and specify other values). -

    printing = bsd

    this causes Samba to use default print commands +section or share you may however override these globally set "share +level" settings and specify other values). +

    printing = bsd

    this causes Samba to use default print commands applicable for the BSD (a.k.a. RFC 1179 style or LPR/LPD) printing -system. In general, the "printing" parameter informs Samba about the +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 +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.0 no longer -supports the SOFTQ printing system.

    load printers = yes

    this tells Samba to create automatically all -available printer shares. "Available" printer shares are discovered by +printer shares that are not defined differently. Samba 3 no longer +supports the SOFTQ printing system.

    load printers = yes

    this 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 @@ -6362,8 +6116,7 @@ share will clone the configuration options found in the [printers] section. (A load printers = no setting will allow you to specify each UNIX printer you want to share separately, leaving out some you don't want to be -publicly visible and available).

    show add printer wizard = -yes

    this setting is normally +publicly visible and available).

    show add printer wizard = yes

    this setting is normally enabled by default (even if the parameter is not written into the ). It makes the Add Printer Wizard icon show up in the Printers folder of the Samba host's @@ -6374,38 +6127,38 @@ will not suffice!). The Add Printer Wizard lets you upload printer drivers to the [print$] share and associate it with a printer (if the respective queue exists there before the action), or exchange a printer's driver against any other previously -uploaded driver.

    total print jobs = 100

    this setting sets the upper limit to 100 print jobs +uploaded driver.

    total print jobs = 100

    this setting sets the upper limit to 100 print jobs being active on the Samba server at any one time. Should a client submit a job which 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 "0" (the default) means there is +Samba to the client. A setting of "0" (the default) means there is no limit at all! -

    printcap name = /etc/printcap

    this tells Samba where to look for a list of +

    printcap name = /etc/printcap

    this tells Samba where to look for a list of available printer names. (If you use CUPS, make sure that a printcap -file is written: this is controlled by the "Printcap" directive of +file is written: this is controlled by the "Printcap" directive of cupsd.conf). -

    printer admin = @ntadmin

    members of the ntadmin group should be able to add -drivers and set printer properties ("ntadmin" is only an example name, +

    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 in +printer admin. The "@" sign precedes group names in . A printer admin can do anything to printers via the remote administration interfaces offered by MS-RPC -(see below). Note that the printer admin +(see below). Note that the printer admin parameter is normally a share level parameter, so you may associate different groups to different printer shares in larger installations, -if you use the printer admin parameter on the +if you use the printer admin parameter on the share levels). -

    lpq cache time = 20

    this controls the cache time for the results of the +

    lpq cache time = 20

    this controls the cache time for the results of the lpq command. It prevents the lpq command being called too often and reduces load on a heavily used print server. -

    use client driver = no

    if set to yes, this setting only +

    use client driver = no

    if set to yes, this setting only takes effect for Win NT/2k/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) which have valid drivers installed on the Samba server! For more detailed explanations see the man page of smb.conf. -

    The [printers] Section

    +

    The [printers] Section

    This 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, @@ -6415,59 +6168,58 @@ section as a general convenience shortcut to share all printers with minimal configuration. It is also a container for settings which should apply as default to all printers. (For more details see the smb.conf man page.) Settings inside this -container must be share level parameters (S). -

    comment = All printers

    the comment is shown next to +container must be share level parameters. +

    comment = All printers

    the comment is shown next to the share if a client queries the server, either via Network Neighbourhood or with the net view command to list available shares. -

    printable = yes

    please note well, that the +

    printable = yes

    please note well, that the [printers] service must be declared as printable. If you specify otherwise, smbd will refuse to load at startup. This parameter allows connected clients to open, write to and submit spool files into the -directory specified with the path parameter for +directory specified with the path parameter for this service. It is used by Samba to differentiate printer shares from -file shares.

    path = /var/spool/samba

    this must point to a directory used by Samba to spool +file shares.

    path = /var/spool/samba

    this must point to a directory used by Samba to spool incoming print files. It must not be the same as the spool directory specified in the configuration of your UNIX print subsystem! The path would typically point to a directory -which is world writeable, with the "sticky" bit set to it. -

    browseable = no

    this is always set to no if -printable = yes. It makes the +which is world writeable, with the "sticky" bit set to it. +

    browseable = no

    this is always set to no if +printable = yes. It makes the [printer] share itself invisible in the list of available shares in a net view command or in the Explorer browse list. (Note that you will of course see the individual printers). -

    guest ok = yes

    +

    guest ok = yes

    if set to yes, then no password is required to connect to the printers service. Access will be granted with the -privileges of the guest account. On many systems the -guest account will map to a user named "nobody". This user is in the UNIX +privileges of the guest account. On many systems the +guest account will map to a user named "nobody". This user is in the UNIX passwd file with an empty password, but with no valid UNIX login. (Note: on some systems the guest account might not have the privilege to be able to print. Test this by logging in as your guest user using su - guest and run a system print command like -

    lpr -P printername /etc/motd

    public = yes

    this is a synonym for guest ok = -yes. Since we have guest ok = yes, +

    lpr -P printername /etc/motd

    public = yes

    this is a synonym for guest ok = yes. Since we have guest ok = yes, it really doesn't need to be here! (This leads to the interesting question: “What, if I by accident have to contradictory settings for the same share?” The answer is: the last one encountered by -Samba wins. The "winner" is shown by testparm. Testparm doesn't +Samba wins. The "winner" is shown by testparm. Testparm doesn't complain about different settings of the same parameter for the same -share! You can test this by setting up multiple lines for the "guest -account" parameter with different usernames, and then run testparm to +share! You can test this by setting up multiple lines for the "guest +account" parameter with different usernames, and then run testparm to see which one is actually used by Samba.) -

    read only = yes

    this normally (for other types of shares) prevents +

    read only = yes

    this normally (for other types of shares) prevents users creating or modifying files in the service's directory. However, -in a "printable" service, it is always allowed to +in a "printable" service, it is always allowed to write to the directory (if user privileges allow the connection), but -only via print spooling operations. "Normal" write operations are not -allowed.

    writeable = no

    -synonym for read only = yes -

    Any [my_printer_name] Section

    +only via print spooling operations. "Normal" write operations are not +allowed.

    writeable = no

    +synonym for read only = yes +

    Any [my_printer_name] Section

    If a section appears in the , which is -tagged as printable = yes, Samba presents it as +tagged as printable = yes, Samba presents it as a printer share to its clients. Note, that Win95/98/ME clients may have problems with connecting or loading printer drivers if the share name has more than 8 characters! Also be very careful if you give a @@ -6476,66 +6228,65 @@ client's connection request to a certain sharename, Samba always tries to find file shares with that name first; if it finds one, it will connect to this and will never ultimately connect to a printer with the same name! -

    comment = Printer with Restricted Access

    the comment says it all. -

    path = /var/spool/samba_my_printer

    here we set the spooling area for this printer to +

    comment = Printer with Restricted Access

    the comment says it all. +

    path = /var/spool/samba_my_printer

    here we set the spooling area for this printer to another directory than the default. It is not a requirement to set it differently, but the option is available. -

    printer admin = kurt

    the printer admin definition is different for this +

    printer admin = kurt

    the printer admin definition is different for this explicitly defined printer share from the general [printers] share. It is not a requirement; we did it to show that it is possible if you want it. -

    browseable = yes

    we also made this printer browseable (so that the +

    browseable = yes

    we also made this printer browseable (so that the clients may conveniently find it when browsing the Network Neighbourhood). -

    printable = yes

    see explanation in last subsection. -

    writeable = no

    see explanation in last subsection. -

    hosts allow = 10.160.50.,10.160.51.

    here we exercise a certain degree of access control -by using the hosts allow and hosts deny parameters. Note, that +

    printable = yes

    see explanation in last subsection. +

    writeable = no

    see explanation in last subsection. +

    hosts allow = 10.160.50.,10.160.51.

    here we exercise a certain degree of access control +by using the hosts allow and hosts deny parameters. Note, that this is not by any means a safe bet. It is not a way to secure your printers. This line accepts all clients from a certain subnet in a first evaluation of access control -

    hosts deny = turbo_xp,10.160.50.23,10.160.51.60 -

    all listed hosts are not allowed here (even if they -belong to the "allowed subnets"). As you can see, you could name IP +

    hosts deny = turbo_xp,10.160.50.23,10.160.51.60

    all listed hosts are not allowed here (even if they +belong to the "allowed subnets"). As 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

    +

    guest ok = no

    this printer is not open for the guest account! +

    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 which have been placed into the Samba print spool directory for that printer. (That spool directory was, if you -remember, set up with the path +remember, set up with the path parameter). Typically, this command will submit the spool file to the Samba host's print subsystem, using the suitable system print command. But there is no requirement that this needs to be the case. For debugging purposes or some other reason you may want to do -something completely different than "print" the file. An example is a +something completely different than "print" the file. An example is a command that just copies the print file to a temporary location for further investigation when you need 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 Print Commands for various Unix Print Subsystems

    +

    Default Print Commands for various UNIX Print Subsystems

    You learned earlier on, that Samba in most cases uses its built-in settings for many parameters if it can not 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 +print command. The default print command varies +depending on the printing parameter setting. In the commands listed below, you will notice some parameters of the form %X where X is p, s, J etc. These letters stand for -"printername", "spoolfile" and "job ID" respectively. They are +"printername", "spoolfile" and "job ID" respectively. They are explained in more detail further below. Here is an overview (excluding the special case of CUPS, which is discussed in the next chapter): -

    If this setting is active......this is used in lieu of an explicit command:
    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)

    +

    If this setting is active......this is used in lieu of an explicit command:
    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)

    We excluded the special CUPS case here, because it is discussed in the next chapter. Just a short summary. For printing = CUPS: If SAMBA is compiled against libcups, it uses the CUPS API to submit jobs, etc. (It is a good idea also to set -printcap = cups in case your +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, i.e. it uses @@ -6546,7 +6297,7 @@ manually set print command will be ignored! Having listed the above mappings here, you should note that there used to be a bug in recent 2.2.x versions which prevented the mapping from taking effect. It lead to the -"bsd|aix|lprng|plp" settings taking effect for all other systems, for +"bsd|aix|lprng|plp" settings taking effect for all other systems, for the most important commands (the print command, the lpq command and the lprm command). The lppause command and the @@ -6558,9 +6309,9 @@ check which command takes effect. Then check that this command is adequate and actually works for your installed print subsystem. It is always a good idea to explicitly set up your configuration files the way you want them to work and not rely on any built-in defaults. -

    Setting up your own Print Commands

    +

    Setting up your own Print Commands

    After a print job has finished spooling to a service, the -print command will be used by Samba via a +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 @@ -6571,7 +6322,7 @@ processed.

    There is no difficulty with using your own customized print commands with the traditional printing systems. However, if you don't wish to -"roll your own", you should be well informed about the default +"roll your own", you should be well informed about the default built-in commands that Samba uses for each printing subsystem (see the table above). In all the commands listed in the last paragraphs you see parameters of the form %X These are @@ -6601,7 +6352,7 @@ spool files will be created but not processed! And (most importantly): print files will not be removed, so they will start filling your Samba hard disk.

    -Note that printing may fail on some UNIXes from the "nobody" +Note that printing may fail on some UNIXes from the "nobody" account. If this happens, create an alternative guest account and supply it with the privilege to print. Set up this guest account in the [global] section with the guest @@ -6613,22 +6364,16 @@ expand the included environment variables as usual. (The syntax to include a UNIX environment variable $variable in or in the Samba print command is %$variable.) To give you a working -print command example, the following will log a +print command example, the following will log a print job to /tmp/print.log, print the file, then remove it. Note that ';' 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
-

    Innovations in Samba Printing since 2.2

    +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

    Innovations in Samba Printing since 2.2

    Before version 2.2.0, Samba's print server support for Windows clients was limited to the level of LanMan printing calls. This is the same protocol level as Windows 9x PCs offer when @@ -6643,16 +6388,14 @@ The additional functionality provided by the new SPOOLSS support includes: 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 (refer to http://imprints.sourceforge.net); +Imprints tool set.

  • Support for the native MS-RPC printing calls such as -StartDocPrinter, EnumJobs(), etc... (See the MSDN documentation -at http://msdn.microsoft.com/ -for more information on the Win32 printing API);

  • Support for NT Access Control + StartDocPrinter, EnumJobs(), etc... (See the MSDN documentation for more information on the Win32 printing API);

  • Support for NT Access Control Lists (ACL) on printer objects;

  • Improved support for printer queue manipulation through the use of internal databases for spooled job information (implemented by various *.tdb files).

    • -One other benefit of an update is this: Samba-3 is able to publish +One other benefit of an update is this: Samba 3 is able to publish all its printers in Active Directory (or LDAP)!

    One slight difference is here: it is possible on a Windows NT print @@ -6666,10 +6409,10 @@ rather they can print directly to any printer on another Windows NT host using MS-RPC. This of course assumes that the printing client has the necessary privileges on the remote host serving the printer. The default permissions assigned by Windows NT to a printer gives the -"Print" permissions to the well-known Everyone -group. (The older clients of type Win9x can only print to "shared" +"Print" permissions to the well-known Everyone +group. (The older clients of type Win9x can only print to "shared" printers). -

    Client Drivers on Samba Server for Point'n'Print

    +

    Client Drivers on Samba Server for Point'n'Print

    There is still confusion about what all this means: Is it or is it not a requirement for printer drivers to be installed on a Samba host in order to support printing from Windows clients? The @@ -6702,12 +6445,12 @@ etc.).

    Please take additional note of the following fact: Samba does not use these uploaded drivers in any way to process spooled files. Drivers are utilized entirely by the clients, who -download and install them via the "Point'n'Print" mechanism supported +download and install them via the "Point'n'Print" mechanism supported by Samba. The clients use these drivers to generate print files in the -format the printer (or the Unix print system) requires. Print files -received by Samba are handed over to the Unix printing system, which +format the printer (or the UNIX print system) requires. Print files +received by Samba are handed over to the UNIX printing system, which is responsible for all further processing, if needed. -

    The [printer$] Section is removed from Samba-3

    +

    The [printer$] Section is removed from Samba 3

    [print$] vs. [printer$] .  Versions of Samba prior to 2.2 made it possible to use a share @@ -6723,7 +6466,7 @@ files associated with that printer. Another parameter named printer driver provided a means of defining the printer driver name to be sent to the client. These parameters, including the printer driver file parameter, -are now removed and can not be used in installations of Samba-3.0. +are now removed and can not be used in installations of samba-3. Now the share name [print$] is used for the location of downloadable printer drivers. It is taken from the [print$] service created by Windows NT PCs when @@ -6733,10 +6476,10 @@ access (in the context of its ACLs) in order to support printer driver down- and uploads. Don't fear -- this does not mean Windows 9x clients are thrown aside now. They can use Samba's [print$] share support just fine. -

    Creating the [print$] Share

    +

    Creating the [print$] Share

    In order to support the up- and downloading of printer driver files, you must first configure a file share named -[print$]. The "public" name of this share is +[print$]. The "public" name of this share is hard coded in Samba's internals (because it is hard coded in the MS Windows clients too). It cannot be renamed since Windows clients are programmed to search for a service of exactly this name if they want @@ -6747,42 +6490,25 @@ 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): -

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

    Parameters in the [print$] Section

    +path parameter exists on the UNIX file system. +

    Parameters in the [print$] Section

    [print$] is a special section in . It contains settings relevant to potential printer driver download and local installation by clients. -

    comment = Printer Driver -Download Area

    the comment appears next to the share name if it is +

    comment = Printer Driver + Download Area

    the comment appears next to the share name if it is listed in a share list (usually Windows clients won't see it often but it will also appear up in a smbclient -L sambaserver - output).

    path = /etc/samba/printers

    this is the path to the location of the Windows + output).

    path = /etc/samba/printers

    this is the path to the location of the Windows driver file deposit from the UNIX point of -view.

    browseable = no

    this makes the [print$] share -"invisible" in Network Neighbourhood to clients. However, you can -still "mount" it from any client using the net use -g:\\sambaserver\print$ command in a "DOS box" or the -"Connect network drive" menu from Windows -Explorer.

    guest ok = yes

    this gives read only access to this share for all +view.

    browseable = no

    this makes the [print$] share +"invisible" in Network Neighbourhood to clients. However, you can +still "mount" it from any client using the net use +g:\\sambaserver\print$ command in a "DOS box" or the +"Connect network drive" menu from Windows +Explorer.

    guest ok = yes

    this gives read only access to this share for all guest users. Access may be used to download and install printer drivers on clients. The requirement for guest ok = yes depends upon how your site is configured. If users @@ -6795,28 +6521,28 @@ validated by the Domain Controller in order to logon to the Windows NT session), then guest access is not necessary. Of course, in a workgroup environment where you just want to be able to print without worrying about silly accounts and security, then configure the share -for guest access. You'll probably want to add map to guest -= Bad User in the [global] section +for guest access. You'll probably want to add map to guest = Bad User in the +[global] section as well. Make sure you understand what this parameter does before using it. -

    read only = yes

    as we don't want everybody to upload driver files (or +

    read only = yes

    as we don't want everybody to upload driver files (or even change driver settings) we tagged this share as not -writeable.

    write list = @ntadmin,root

    since the [print$] was made -read only by the previous setting, we need to create a "write list" -also. UNIX groups (denoted with a leading "@" character) and users +writeable.

    write list = @ntadmin,root

    since the [print$] was made +read only by the previous setting, we need to create a "write list" +also. UNIX groups (denoted with a leading "@" character) and users listed here are allowed write access (as an exception to the general -public's "read-only" access), which they need to update files on the +public's "read-only" access), which they need to update files on the share. Normally you will want to only name administrative level user accounts in this setting. Check the file system permissions to make sure these accounts 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 +printer admin parameter. See the man page for more information on -configuring file shares.

    Subdirectory Structure in [print$]

    +configuring file shares.

    Subdirectory Structure in [print$]

    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 +(i.e. the UNIX directory named by the path parameter). These correspond to each of the supported client architectures. Samba follows this model as well. Just like the name of the [print$] share itself, the subdirectories @@ -6828,11 +6554,11 @@ Therefore, create a directory tree below the to support. 

     [print$]--+--
-          |--W32X86           # serves drivers to "Windows NT x86"
-          |--WIN40            # serves drivers to "Windows 95/98"
-          |--W32ALPHA         # serves drivers to "Windows NT Alpha_AXP"
-          |--W32MIPS          # serves drivers to "Windows NT R4000"
-          |--W32PPC           # serves drivers to "Windows NT PowerPC"
+          |--W32X86           # serves drivers to "Windows NT x86"
+          |--WIN40            # serves drivers to "Windows 95/98"
+          |--W32ALPHA         # serves drivers to "Windows NT Alpha_AXP"
+          |--W32MIPS          # serves drivers to "Windows NT R4000"
+          |--W32PPC           # serves drivers to "Windows NT PowerPC"

    Required permissions

    In order to add a new driver to your Samba host, one of two conditions must hold true: @@ -6851,7 +6577,7 @@ client workstation. Open Network Neighbourhood or Once you have located the server, navigate to its Printers and Faxes folder. You should see an initial listing of printers that matches the printer shares defined on your Samba host. -

    Installing Drivers into [print$]

    +

    Installing Drivers into [print$]

    You have successfully created the [print$] share in ? And Samba has re-read its configuration? Good. But you are not yet ready to take off. The @@ -6869,11 +6595,11 @@ Properties and Add Printer Wizard

    The latter option is probably the easier one (even if the only entrance to this realm seems a little bit weird at first). -

    Setting Drivers for existing Printers with a Client GUI

    +

    Setting Drivers for existing Printers with a Client GUI

    The initial listing of printers in the Samba host's Printers folder accessed from a client's Explorer -will have no real printer driver assigned to them. By default, in -Samba-3 (as in 2.2.1 and later) this driver name is set to a NULL +will have no real printer driver assigned to them. By default +this driver name is set to a NULL string. This must be changed now. The local Add Printer Wizard, run from NT/2000/XP clients, will help us in this task. @@ -6904,18 +6630,18 @@ Once the APW is started, the procedure is exactly the same as the one you are familiar with in Windows (we assume here that you are familiar with the printer driver installations procedure on Windows NT). Make sure your connection is in fact setup as a user with -printer admin privileges (if in doubt, use +printer admin privileges (if in doubt, use smbstatus to check for this). If you wish to install printer drivers for client operating systems other than Windows NT x86, you will need to use the Sharing tab of the printer properties dialog.

    Assuming you have connected with an administrative (or root) account -(as named by the printer admin parameter), +(as named by the printer admin parameter), you will also be able to modify other printer properties such as ACLs and default device settings using this dialog. For the default device settings, please consider the advice given further below. -

    Setting Drivers for existing Printers with +

    Setting Drivers for existing Printers with rpcclient

    The second way to install printer drivers into [print$] and set them up in a valid way can be @@ -6930,7 +6656,7 @@ time with the setdriver subcommand.

    We will provide detailed hints for each of these steps in the next few paragraphs. -

    Identifying the Driver Files

    +

    Identifying the Driver Files

    To find out about the driver files, you have two options: you could investigate the driver CD which comes with your printer. Study the *.inf file on the CD, if it is contained. This @@ -6978,35 +6704,35 @@ create scripts to automate the procedure for a large number of printers and drivers. Note the different quotes used to overcome the different spaces in between words: 

    -root# rpcclient -U'Danka%xxxx' -c 'getdriver "Heidelberg Digimaster 9110 (PS)" 3' TURBO_XP
-  cmd = getdriver "Heidelberg Digimaster 9110 (PS)" 3
-
-  [Windows NT x86]
-  Printer Driver Info 3:
-          Version: [2]
-          Driver Name: [Heidelberg Digimaster 9110 (PS)]
-          Architecture: [Windows NT x86]
-          Driver Path: [C:\WINNT\System32\spool\DRIVERS\W32X86\2\HDNIS01_de.DLL]
-          Datafile: [C:\WINNT\System32\spool\DRIVERS\W32X86\2\Hddm91c1_de.ppd]
-          Configfile: [C:\WINNT\System32\spool\DRIVERS\W32X86\2\HDNIS01U_de.DLL]
-          Helpfile: [C:\WINNT\System32\spool\DRIVERS\W32X86\2\HDNIS01U_de.HLP]
+root# rpcclient -U'Danka%xxxx' -c \
+	'getdriver "Heidelberg Digimaster 9110 (PS)" 3' TURBO_XP
+cmd = getdriver "Heidelberg Digimaster 9110 (PS)" 3
+
+[Windows NT x86]
+Printer Driver Info 3:
+  Version: [2]
+  Driver Name: [Heidelberg Digimaster 9110 (PS)]
+  Architecture: [Windows NT x86]
+  Driver Path: [C:\WINNT\System32\spool\DRIVERS\W32X86\2\HDNIS01_de.DLL]
+  Datafile: [C:\WINNT\System32\spool\DRIVERS\W32X86\2\Hddm91c1_de.ppd]
+  Configfile: [C:\WINNT\System32\spool\DRIVERS\W32X86\2\HDNIS01U_de.DLL]
+  Helpfile: [C:\WINNT\System32\spool\DRIVERS\W32X86\2\HDNIS01U_de.HLP]
   
-          Dependentfiles: [C:\WINNT\System32\spool\DRIVERS\W32X86\2\Hddm91c1_de.DLL]
-          Dependentfiles: [C:\WINNT\System32\spool\DRIVERS\W32X86\2\Hddm91c1_de.INI]
-          Dependentfiles: [C:\WINNT\System32\spool\DRIVERS\W32X86\2\Hddm91c1KMMin.DLL]
-          Dependentfiles: [C:\WINNT\System32\spool\DRIVERS\W32X86\2\Hddm91c1_de.dat]
-          Dependentfiles: [C:\WINNT\System32\spool\DRIVERS\W32X86\2\Hddm91c1_de.cat]
-          Dependentfiles: [C:\WINNT\System32\spool\DRIVERS\W32X86\2\Hddm91c1_de.def]
-          Dependentfiles: [C:\WINNT\System32\spool\DRIVERS\W32X86\2\Hddm91c1_de.hre]
-          Dependentfiles: [C:\WINNT\System32\spool\DRIVERS\W32X86\2\Hddm91c1_de.vnd]
-          Dependentfiles: [C:\WINNT\System32\spool\DRIVERS\W32X86\2\Hddm91c1_de.hlp]
-          Dependentfiles: [C:\WINNT\System32\spool\DRIVERS\W32X86\2\Hddm91c1_de_reg.HLP]
-          Dependentfiles: [C:\WINNT\System32\spool\DRIVERS\W32X86\2\HDNIS01Aux.dll]
-          Dependentfiles: [C:\WINNT\System32\spool\DRIVERS\W32X86\2\HDNIS01_de.NTF]
+  Dependentfiles: [C:\WINNT\System32\spool\DRIVERS\W32X86\2\Hddm91c1_de.DLL]
+  Dependentfiles: [C:\WINNT\System32\spool\DRIVERS\W32X86\2\Hddm91c1_de.INI]
+  Dependentfiles: [C:\WINNT\System32\spool\DRIVERS\W32X86\2\Hddm91c1KMMin.DLL]
+  Dependentfiles: [C:\WINNT\System32\spool\DRIVERS\W32X86\2\Hddm91c1_de.dat]
+  Dependentfiles: [C:\WINNT\System32\spool\DRIVERS\W32X86\2\Hddm91c1_de.cat]
+  Dependentfiles: [C:\WINNT\System32\spool\DRIVERS\W32X86\2\Hddm91c1_de.def]
+  Dependentfiles: [C:\WINNT\System32\spool\DRIVERS\W32X86\2\Hddm91c1_de.hre]
+  Dependentfiles: [C:\WINNT\System32\spool\DRIVERS\W32X86\2\Hddm91c1_de.vnd]
+  Dependentfiles: [C:\WINNT\System32\spool\DRIVERS\W32X86\2\Hddm91c1_de.hlp]
+  Dependentfiles: [C:\WINNT\System32\spool\DRIVERS\W32X86\2\Hddm91c1_de_reg.HLP]
+  Dependentfiles: [C:\WINNT\System32\spool\DRIVERS\W32X86\2\HDNIS01Aux.dll]
+  Dependentfiles: [C:\WINNT\System32\spool\DRIVERS\W32X86\2\HDNIS01_de.NTF]
   
-          Monitorname: []
-          Defaultdatatype: []
-
+  Monitorname: []
+  Defaultdatatype: []

    You may notice, that this driver has quite a big number of Dependentfiles (I know worse cases however). Also, @@ -7023,17 +6749,17 @@ can also host the Win9x drivers, even if itself runs on Windows NT, Since the [print$] share is usually accessible through the Network Neighbourhood, you can also use the UNC notation from Windows Explorer to poke at it. The Win9x driver files will end -up in subdirectory "0" of the "WIN40" directory. The full path to +up in subdirectory "0" of the "WIN40" directory. The full path to access them will be \\WINDOWSHOST\print$\WIN40\0\.

    Note

    more recent drivers on Windows 2000 and Windows XP are -installed into the "3" subdirectory instead of the "2". The version 2 +installed into the "3" subdirectory instead of the "2". The version 2 of drivers, as used in Windows NT, were running in Kernel Mode. Windows 2000 changed this. While it still can use the Kernel Mode drivers (if this is enabled by the Admin), its native mode for printer drivers is User Mode execution. This requires drivers designed for -this. These type of drivers install into the "3" subdirectory. -

    Collecting the Driver Files from a Windows Host's +this. These type of drivers install into the "3" subdirectory. +

    Collecting the Driver Files from a Windows Host's [print$] Share

    Now we need to collect all the driver files we identified. in our previous step. Where do we get them from? Well, why not retrieve them @@ -7046,15 +6772,15 @@ listing is edited to include linebreaks for readability: root# smbclient //TURBO_XP/print\$ -U'Danka%xxxx' \ -c 'cd W32X86/2;mget HD*_de.* \ hd*ppd Hd*_de.* Hddm*dll HDN*Aux.DLL' - added interface ip=10.160.51.60 bcast=10.160.51.255 nmask=255.255.252.0 - Got a positive name query response from 10.160.50.8 ( 10.160.50.8 ) - Domain=[DEVELOPMENT] OS=[Windows 5.1] Server=[Windows 2000 LAN Manager] - Get file Hddm91c1_de.ABD? n - Get file Hddm91c1_de.def? y - getting file \W32X86\2\Hddm91c1_de.def of size 428 as Hddm91c1_de.def (22.0 kb/s) (average 22.0 kb/s) - Get file Hddm91c1_de.DLL? y - getting file \W32X86\2\Hddm91c1_de.DLL of size 876544 as Hddm91c1_de.DLL (737.3 kb/s) (average 737.3 kb/s) - [...] +added interface ip=10.160.51.60 bcast=10.160.51.255 nmask=255.255.252.0 +Got a positive name query response from 10.160.50.8 ( 10.160.50.8 ) +Domain=[DEVELOPMENT] OS=[Windows 5.1] Server=[Windows 2000 LAN Manager] +Get file Hddm91c1_de.ABD? n +Get file Hddm91c1_de.def? y +getting file \W32X86\2\Hddm91c1_de.def of size 428 as Hddm91c1_de.def +Get file Hddm91c1_de.DLL? y +getting file \W32X86\2\Hddm91c1_de.DLL of size 876544 as Hddm91c1_de.DLL +[...]

    After this command is complete, the files are in our current local @@ -7069,7 +6795,7 @@ files for these architectures are in the WIN40/0/ subdir. Once we are complete, we can run smbclient ... put to store the collected files on the Samba server's [print$] share. -

    Depositing the Driver Files into [print$]

    +

    Depositing the Driver Files into [print$]

    So, now we are going to put the driver files into the [print$] share. Remember, the UNIX path to this share has been defined previously in your @@ -7080,9 +6806,9 @@ your [print$] share maps to the UNIX path go here:

    • for all Windows NT, 2000 and XP clients into /etc/samba/drivers/W32X86/ but -*not*(yet) into the "2" subdir!

    • for all Windows 95, 98 and ME clients into +*not*(yet) into the "2" subdir!

    • for all Windows 95, 98 and ME clients into /etc/samba/drivers/WIN40/ -- but *not* -(yet) into the "0" subdir!

    +(yet) into the "0" subdir!

    We again use smbclient to transfer the driver files across the network. We specify the same files and paths as were leaked to us by running getdriver against the original @@ -7090,7 +6816,8 @@ running getdriver against the original store the files into a Samba/UNIX print server's [print$] share... 

    -root# smbclient //SAMBA-CUPS/print\$ -U'root%xxxx' -c 'cd W32X86; put HDNIS01_de.DLL; \
+		root# smbclient //SAMBA-CUPS/print\$ -U'root%xxxx' -c \
+ 'cd W32X86; put HDNIS01_de.DLL; \
   put Hddm91c1_de.ppd; put HDNIS01U_de.DLL;        \
   put HDNIS01U_de.HLP; put Hddm91c1_de.DLL;        \
   put Hddm91c1_de.INI; put Hddm91c1KMMin.DLL;      \
@@ -7099,78 +6826,77 @@ store the files into a Samba/UNIX print s
   put Hddm91c1_de.vnd; put Hddm91c1_de.hlp;        \
   put Hddm91c1_de_reg.HLP; put HDNIS01Aux.dll;     \
   put HDNIS01_de.NTF'
- added interface ip=10.160.51.60 bcast=10.160.51.255 nmask=255.255.252.0
- Got a positive name query response from 10.160.51.162 ( 10.160.51.162 )
- Domain=[CUPS-PRINT] OS=[Unix] Server=[Samba 2.2.7a]
- putting file HDNIS01_de.DLL as \W32X86\HDNIS01_de.DLL (4465.5 kb/s) (average 4465.5 kb/s)
- putting file Hddm91c1_de.ppd as \W32X86\Hddm91c1_de.ppd (12876.8 kb/s) (average 4638.9 kb/s)
- putting file HDNIS01U_de.DLL as \W32X86\HDNIS01U_de.DLL (20249.8 kb/s) (average 5828.3 kb/s)
- putting file HDNIS01U_de.HLP as \W32X86\HDNIS01U_de.HLP (9652.8 kb/s) (average 5899.8 kb/s)
- putting file Hddm91c1_de.DLL as \W32X86\Hddm91c1_de.DLL (23777.7 kb/s) (average 10400.6 kb/s)
- putting file Hddm91c1_de.INI as \W32X86\Hddm91c1_de.INI (98.6 kb/s) (average 10329.0 kb/s)
- putting file Hddm91c1KMMin.DLL as \W32X86\Hddm91c1KMMin.DLL (22931.5 kb/s) (average 10501.7 kb/s)
- putting file Hddm91c1_de.dat as \W32X86\Hddm91c1_de.dat (2462.8 kb/s) (average 10393.0 kb/s)
- putting file Hddm91c1_de.dat as \W32X86\Hddm91c1_de.dat (4925.3 kb/s) (average 10356.3 kb/s)
- putting file Hddm91c1_de.def as \W32X86\Hddm91c1_de.def (417.9 kb/s) (average 10290.1 kb/s)
- putting file Hddm91c1_de.hre as \W32X86\Hddm91c1_de.hre (22571.3 kb/s) (average 11338.5 kb/s)
- putting file Hddm91c1_de.vnd as \W32X86\Hddm91c1_de.vnd (3384.6 kb/s) (average 10754.3 kb/s)
- putting file Hddm91c1_de.hlp as \W32X86\Hddm91c1_de.hlp (18406.8 kb/s) (average 10839.8 kb/s)
- putting file Hddm91c1_de_reg.HLP as \W32X86\Hddm91c1_de_reg.HLP (20278.3 kb/s) (average 11386.3 kb/s)
- putting file HDNIS01Aux.dll as \W32X86\HDNIS01Aux.dll (14994.6 kb/s) (average 11405.2 kb/s)
- putting file HDNIS01_de.NTF as \W32X86\HDNIS01_de.NTF (23390.2 kb/s) (average 13170.8 kb/s)
-
+added interface ip=10.160.51.60 bcast=10.160.51.255 nmask=255.255.252.0
+Got a positive name query response from 10.160.51.162 ( 10.160.51.162 )
+Domain=[CUPS-PRINT] OS=[UNIX] Server=[Samba 2.2.7a]
+putting file HDNIS01_de.DLL as \W32X86\HDNIS01_de.DLL
+putting file Hddm91c1_de.ppd as \W32X86\Hddm91c1_de.ppd
+putting file HDNIS01U_de.DLL as \W32X86\HDNIS01U_de.DLL
+putting file HDNIS01U_de.HLP as \W32X86\HDNIS01U_de.HLP
+putting file Hddm91c1_de.DLL as \W32X86\Hddm91c1_de.DLL
+putting file Hddm91c1_de.INI as \W32X86\Hddm91c1_de.INI
+putting file Hddm91c1KMMin.DLL as \W32X86\Hddm91c1KMMin.DLL
+putting file Hddm91c1_de.dat as \W32X86\Hddm91c1_de.dat
+putting file Hddm91c1_de.dat as \W32X86\Hddm91c1_de.dat
+putting file Hddm91c1_de.def as \W32X86\Hddm91c1_de.def
+putting file Hddm91c1_de.hre as \W32X86\Hddm91c1_de.hre
+putting file Hddm91c1_de.vnd as \W32X86\Hddm91c1_de.vnd
+putting file Hddm91c1_de.hlp as \W32X86\Hddm91c1_de.hlp
+putting file Hddm91c1_de_reg.HLP as \W32X86\Hddm91c1_de_reg.HLP
+putting file HDNIS01Aux.dll as \W32X86\HDNIS01Aux.dll
+putting file HDNIS01_de.NTF as \W32X86\HDNIS01_de.NTF

    Phewww -- that was a lot of typing! Most drivers are a lot smaller -- many only having 3 generic PostScript driver files plus 1 PPD. Note, -that while we did retrieve the files from the "2" subdirectory of the -"W32X86" directory from the Windows box, we don't +that while we did retrieve the files from the "2" subdirectory of the +"W32X86" directory from the Windows box, we don't put them (for now) in this same subdirectory of the Samba box! This re-location will automatically be done by the adddriver command which we will run shortly (and don't forget to also put the files for the Win95/98/ME architecture into the WIN40/ subdirectory should you need them). -

    Check if the Driver Files are there (with smbclient)

    +

    Check if the Driver Files are there (with smbclient)

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

    -root# smbclient //SAMBA-CUPS/print\$ -U 'root%xxxx' -c 'cd W32X86; pwd; dir; cd 2; pwd; dir'
+root# smbclient //SAMBA-CUPS/print\$ -U 'root%xxxx' \
+	-c 'cd W32X86; pwd; dir; cd 2; pwd; dir'
  added interface ip=10.160.51.60 bcast=10.160.51.255 nmask=255.255.252.0
- Got a positive name query response from 10.160.51.162 ( 10.160.51.162 )
- Domain=[CUPS-PRINT] OS=[Unix] Server=[Samba 2.2.7a]
-
-  Current directory is \\SAMBA-CUPS\print$\W32X86\
-  .                                   D        0  Sun May  4 03:56:35 2003
-  ..                                  D        0  Thu Apr 10 23:47:40 2003
-  2                                   D        0  Sun May  4 03:56:18 2003
-  HDNIS01Aux.dll                      A    15356  Sun May  4 03:58:59 2003
-  Hddm91c1KMMin.DLL                   A    46966  Sun May  4 03:58:59 2003
-  HDNIS01_de.DLL                      A   434400  Sun May  4 03:58:59 2003
-  HDNIS01_de.NTF                      A   790404  Sun May  4 03:56:35 2003
-  Hddm91c1_de.DLL                     A   876544  Sun May  4 03:58:59 2003
-  Hddm91c1_de.INI                     A      101  Sun May  4 03:58:59 2003
-  Hddm91c1_de.dat                     A     5044  Sun May  4 03:58:59 2003
-  Hddm91c1_de.def                     A      428  Sun May  4 03:58:59 2003
-  Hddm91c1_de.hlp                     A    37699  Sun May  4 03:58:59 2003
-  Hddm91c1_de.hre                     A   323584  Sun May  4 03:58:59 2003
-  Hddm91c1_de.ppd                     A    26373  Sun May  4 03:58:59 2003
-  Hddm91c1_de.vnd                     A    45056  Sun May  4 03:58:59 2003
-  HDNIS01U_de.DLL                     A   165888  Sun May  4 03:58:59 2003
-  HDNIS01U_de.HLP                     A    19770  Sun May  4 03:58:59 2003
-  Hddm91c1_de_reg.HLP                 A   228417  Sun May  4 03:58:59 2003
-                40976 blocks of size 262144. 709 blocks available
-
-  Current directory is \\SAMBA-CUPS\print$\W32X86\2\
-  .                                   D        0  Sun May  4 03:56:18 2003
-  ..                                  D        0  Sun May  4 03:56:35 2003
-  ADOBEPS5.DLL                        A   434400  Sat May  3 23:18:45 2003
-  laserjet4.ppd                       A     9639  Thu Apr 24 01:05:32 2003
-  ADOBEPSU.DLL                        A   109568  Sat May  3 23:18:45 2003
-  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
-
+Got a positive name query response from 10.160.51.162 ( 10.160.51.162 )
+Domain=[CUPS-PRINT] OS=[UNIX] Server=[Samba 2.2.7a]
+
+Current directory is \\SAMBA-CUPS\print$\W32X86\
+.                                   D        0  Sun May  4 03:56:35 2003
+..                                  D        0  Thu Apr 10 23:47:40 2003
+2                                   D        0  Sun May  4 03:56:18 2003
+HDNIS01Aux.dll                      A    15356  Sun May  4 03:58:59 2003
+Hddm91c1KMMin.DLL                   A    46966  Sun May  4 03:58:59 2003
+HDNIS01_de.DLL                      A   434400  Sun May  4 03:58:59 2003
+HDNIS01_de.NTF                      A   790404  Sun May  4 03:56:35 2003
+Hddm91c1_de.DLL                     A   876544  Sun May  4 03:58:59 2003
+Hddm91c1_de.INI                     A      101  Sun May  4 03:58:59 2003
+Hddm91c1_de.dat                     A     5044  Sun May  4 03:58:59 2003
+Hddm91c1_de.def                     A      428  Sun May  4 03:58:59 2003
+Hddm91c1_de.hlp                     A    37699  Sun May  4 03:58:59 2003
+Hddm91c1_de.hre                     A   323584  Sun May  4 03:58:59 2003
+Hddm91c1_de.ppd                     A    26373  Sun May  4 03:58:59 2003
+Hddm91c1_de.vnd                     A    45056  Sun May  4 03:58:59 2003
+HDNIS01U_de.DLL                     A   165888  Sun May  4 03:58:59 2003
+HDNIS01U_de.HLP                     A    19770  Sun May  4 03:58:59 2003
+Hddm91c1_de_reg.HLP                 A   228417  Sun May  4 03:58:59 2003
+              40976 blocks of size 262144. 709 blocks available
+
+Current directory is \\SAMBA-CUPS\print$\W32X86\2\
+.                                   D        0  Sun May  4 03:56:18 2003
+..                                  D        0  Sun May  4 03:56:35 2003
+ADOBEPS5.DLL                        A   434400  Sat May  3 23:18:45 2003
+laserjet4.ppd                       A     9639  Thu Apr 24 01:05:32 2003
+ADOBEPSU.DLL                        A   109568  Sat May  3 23:18:45 2003
+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 subdir (probably from a previous @@ -7183,7 +6909,7 @@ Point'n'Print. The reason is: Samba doesn't know yet that these files are something special, namely printer driver files and it doesn't know yet to which print queue(s) these driver files belong. -

    Running rpcclient with +

    Running rpcclient with adddriver

    So, next you must tell Samba about the special category of the files you just uploaded into the [print$] share. This @@ -7192,21 +6918,23 @@ prompt Samba to register the driver files into its internal TDB database files. The following command and its output has been edited, again, for readability: 

    -root# rpcclient -Uroot%xxxx -c 'adddriver "Windows NT x86" "dm9110:HDNIS01_de.DLL: \
-  Hddm91c1_de.ppd:HDNIS01U_de.DLL:HDNIS01U_de.HLP:   \
-  NULL:RAW:Hddm91c1_de.DLL,Hddm91c1_de.INI,          \
-  Hddm91c1_de.dat,Hddm91c1_de.def,Hddm91c1_de.hre,   \
-  Hddm91c1_de.vnd,Hddm91c1_de.hlp,Hddm91c1KMMin.DLL, \
-  HDNIS01Aux.dll,HDNIS01_de.NTF,                     \
-  Hddm91c1_de_reg.HLP' SAMBA-CUPS
+		root# rpcclient -Uroot%xxxx -c 'adddriver "Windows NT x86" \
+"dm9110:HDNIS01_de.DLL: \
+Hddm91c1_de.ppd:HDNIS01U_de.DLL:HDNIS01U_de.HLP:   \
+ NULL:RAW:Hddm91c1_de.DLL,Hddm91c1_de.INI,          \
+ Hddm91c1_de.dat,Hddm91c1_de.def,Hddm91c1_de.hre,   \
+ Hddm91c1_de.vnd,Hddm91c1_de.hlp,Hddm91c1KMMin.DLL, \
+ HDNIS01Aux.dll,HDNIS01_de.NTF,                     \
+ Hddm91c1_de_reg.HLP' SAMBA-CUPS
 
- cmd = adddriver "Windows NT x86" "dm9110:HDNIS01_de.DLL:Hddm91c1_de.ppd:HDNIS01U_de.DLL:    \
-  HDNIS01U_de.HLP:NULL:RAW:Hddm91c1_de.DLL,Hddm91c1_de.INI, \
-  Hddm91c1_de.dat,Hddm91c1_de.def,Hddm91c1_de.hre,          \
-  Hddm91c1_de.vnd,Hddm91c1_de.hlp,Hddm91c1KMMin.DLL,        \
-  HDNIS01Aux.dll,HDNIS01_de.NTF,Hddm91c1_de_reg.HLP"
+cmd = adddriver "Windows NT x86" \
+"dm9110:HDNIS01_de.DLL:Hddm91c1_de.ppd:HDNIS01U_de.DLL:    \
+ HDNIS01U_de.HLP:NULL:RAW:Hddm91c1_de.DLL,Hddm91c1_de.INI, \
+ Hddm91c1_de.dat,Hddm91c1_de.def,Hddm91c1_de.hre,          \
+ Hddm91c1_de.vnd,Hddm91c1_de.hlp,Hddm91c1KMMin.DLL,        \
+ HDNIS01Aux.dll,HDNIS01_de.NTF,Hddm91c1_de_reg.HLP"
 
- Printer Driver dm9110 successfully installed.
+Printer Driver dm9110 successfully installed.

    After this step the driver should be recognized by Samba on the print @@ -7218,7 +6946,7 @@ files successfully, but render the driver unworkable. So take care! Hints about the syntax of the adddriver command are in the man page. The CUPS printing chapter of this HOWTO collection provides a more detailed description, if you should need it. -

    Check how Driver Files have been moved after +

    Check how Driver Files have been moved after adddriver finished

    One indication for Samba's recognition of the files as driver files is the successfully installed message. @@ -7227,9 +6955,9 @@ Another one is the fact, that our files have been moved by the subdirectory. You can check this again with smbclient: 

    -root# smbclient //SAMBA-CUPS/print\$ -Uroot%xxxx -c 'cd W32X86;dir;pwd;cd 2;dir;pwd'
+root# smbclient //SAMBA-CUPS/print\$ -Uroot%xx -c 'cd W32X86;dir;pwd;cd 2;dir;pwd'
  added interface ip=10.160.51.162 bcast=10.160.51.255 nmask=255.255.252.0
- Domain=[CUPS-PRINT] OS=[Unix] Server=[Samba 2.2.7a]
+ Domain=[CUPS-PRINT] OS=[UNIX] Server=[Samba 2.2.7a]
 
   Current directory is \\SAMBA-CUPS\print$\W32X86\
   .                                   D        0  Sun May  4 04:32:48 2003
@@ -7266,7 +6994,7 @@ subdirectory. You can check this again with

    Another verification is that the timestamp of the printing TDB files is now updated (and possibly their filesize has increased). -

    Check if the Driver is recognized by Samba

    +

    Check if the Driver is recognized by Samba

    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 @@ -7291,13 +7019,13 @@ right-click the white background (with no printer highlighted). Select Drivers tab you will see the new driver listed now. This view enables you to also inspect the list of files belonging to that driver (this doesn't work on Windows NT, but only on -Windows 2000 and Windows XP. WinNT doesn't provide the "Drivers" +Windows 2000 and Windows XP. WinNT doesn't provide the "Drivers" tab).. An alternative, much quicker method for Windows 2000/XP to start this dialog is by typing into a DOS box (you must of course adapt the name to your Samba server instead of SAMBA-CUPS):

    rundll32 printui.dll,PrintUIEntry /s /t2 /n\\SAMBA-CUPS

  • from a UNIX prompt run this command (or a variant thereof), where SAMBA-CUPS is the name of the Samba -host and "xxxx" represents the actual Samba password assigned to root: +host and "xxxx" represents the actual Samba password assigned to root:

    rpcclient -U'root%xxxx' -c 'enumdrivers' SAMBA-CUPS

    You will see a listing of all drivers Samba knows about. Your new one should be amongst them. But it is only listed under the [Windows NT @@ -7310,27 +7038,27 @@ time. Our new driver only shows up 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. -

    • A side note: you are not bound to specific driver names

    +

    A side note: you are not bound to specific driver names

    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: 

     root# rpcclient -Uroot%xxxx                                        \
-      -c 'adddriver "Windows NT x86"                     \
-      "myphantasydrivername:HDNIS01_de.DLL:              \
-      Hddm91c1_de.ppd:HDNIS01U_de.DLL:HDNIS01U_de.HLP:   \
-      NULL:RAW:Hddm91c1_de.DLL,Hddm91c1_de.INI,          \
-      Hddm91c1_de.dat,Hddm91c1_de.def,Hddm91c1_de.hre,   \
-      Hddm91c1_de.vnd,Hddm91c1_de.hlp,Hddm91c1KMMin.DLL, \
-      HDNIS01Aux.dll,HDNIS01_de.NTF,Hddm91c1_de_reg.HLP' SAMBA-CUPS
+  -c 'adddriver "Windows NT x86"                     \
+  "myphantasydrivername:HDNIS01_de.DLL:              \
+  Hddm91c1_de.ppd:HDNIS01U_de.DLL:HDNIS01U_de.HLP:   \
+  NULL:RAW:Hddm91c1_de.DLL,Hddm91c1_de.INI,          \
+  Hddm91c1_de.dat,Hddm91c1_de.def,Hddm91c1_de.hre,   \
+  Hddm91c1_de.vnd,Hddm91c1_de.hlp,Hddm91c1KMMin.DLL, \
+  HDNIS01Aux.dll,HDNIS01_de.NTF,Hddm91c1_de_reg.HLP' SAMBA-CUPS
   
 
- cmd = adddriver "Windows NT x86" 
-                 "myphantasydrivername:HDNIS01_de.DLL:Hddm91c1_de.ppd:HDNIS01U_de.DLL:\
+ cmd = adddriver "Windows NT x86" 
+                 "myphantasydrivername:HDNIS01_de.DLL:Hddm91c1_de.ppd:HDNIS01U_de.DLL:\
                   HDNIS01U_de.HLP:NULL:RAW:Hddm91c1_de.DLL,Hddm91c1_de.INI,           \
                   Hddm91c1_de.dat,Hddm91c1_de.def,Hddm91c1_de.hre,                    \
                   Hddm91c1_de.vnd,Hddm91c1_de.hlp,Hddm91c1KMMin.DLL,                  \
-                  HDNIS01Aux.dll,HDNIS01_de.NTF,Hddm91c1_de_reg.HLP"
+                  HDNIS01Aux.dll,HDNIS01_de.NTF,Hddm91c1_de_reg.HLP"
 
  Printer Driver myphantasydrivername successfully installed.
 
@@ -7339,16 +7067,16 @@ You will also be able to bind that driver to any print queue (however,
 you are responsible yourself that you associate drivers to queues
 which make sense to the target printer). Note, that you can't run the
 rpcclient adddriver command
-repeatedly. Each run "consumes" the files you had put into the
+repeatedly. Each run "consumes" the files you had put into the
 [print$] share by moving them into the
 respective subdirectories. So you must precede an
 smbclient ... put command before each
-rpcclient ...  adddriver" command.
-

    La Grande Finale: Running rpcclient with +rpcclient ... adddriver" command. +

    Running rpcclient with setdriver

    Samba still needs to know which printer's driver this is. It needs to create a mapping of the driver to a printer, and -store this info in its "memory", the TDB files. The rpcclient +store this info in its "memory", the TDB files. The rpcclient setdriver command achieves exactly this: 

     root# rpcclient -U'root%xxxx' -c 'setdriver dm9110 myphantasydrivername' SAMBA-CUPS
@@ -7364,8 +7092,8 @@ name I intended:

    The syntax of the command is rpcclient -U'root%sambapassword' -c 'setdriver -"printername" -"drivername' +"printername" +"drivername' SAMBA-Hostname . -- Now we have done *most* of the work. But not yet all....

    Note

    @@ -7374,26 +7102,25 @@ known to Samba already. A bug in 2.2.x prevented Samba from recognizing freshly installed printers. You had to restart Samba, or at least send a HUP signal to all running smbd processes to work around this: -kill -HUP `pidof smbd`.

    "The Proof of the Pudding lies in the Eating" (Client Driver Install -Procedure)

    +kill -HUP `pidof smbd`.

    Client Driver Install Procedure

    A famous philosopher said once: “The Proof of the Pudding lies 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. -

    The first Client Driver Installation

    +

    The 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 setup and shouldn't need further attention. What follows is a description for the recommended first procedure. You work now from a client workstation. First you should guarantee that your connection is not unwittingly mapped to -bad user "nobody". In a DOS box type: +bad user "nobody". In a DOS box type:

    net use \\SAMBA-SERVER\print$ /user:root

    Replace root, if needed, by another valid printer admin user as given in the definition. Should you already be connected as a different user, you'll get an error message. There is no easy way to get rid of that connection, because -Windows doesn't seem to know a concept of "logging off" from a share +Windows doesn't seem to know a concept of "logging off" from a share connection (don't confuse this with logging off from the local workstation; that is a different matter). You can try to close all Windows file explorer and Internet Explorer @@ -7414,16 +7141,16 @@ samba-server) should now have appeared in your -- Printers and Faxes).

    Most likely you are now tempted to try and print a test page. After -all, you now can open the printer properties and on the "General" tab, +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 reason might be that there is not yet a -valid Device Mode set for the driver, or that the "Printer Driver -Data" set is still incomplete. +valid Device Mode set for the driver, or that the "Printer Driver +Data" set is still incomplete.

    -You must now make sure that a valid "Device Mode" is set for the +You must now make sure that a valid "Device Mode" is set for the driver. Don't fear -- we will explain now what that means. -

    IMPORTANT! Setting Device Modes on new Printers

    +

    IMPORTANT! Setting Device Modes on new Printers

    In order for a printer to be truly usable by a Windows NT/2K/XP client, it must possess:

    • a valid Device Mode generated by @@ -7450,7 +7177,7 @@ This can be achieved by accessing the drivers remotely from an NT (or 2k/XP) client, as is discussed in the next paragraphs.

      Be aware, that a valid Device Mode can only be initiated by a -printer admin, or root (the reason should be +printer admin, or root (the reason should be obvious). Device Modes can only correctly be set by executing the printer driver program itself. Since Samba can not execute this Win32 platform driver code, it sets this field initially to NULL (which is @@ -7460,9 +7187,9 @@ are uploaded to the [print$] share with the help of the APW or rpcclient.

      The generation and setting of a first valid Device Mode however -requires some "tickling" from a client, to set it on the Samba +requires some "tickling" from a client, to set it on the Samba server. The easiest means of doing so is to simply change the page -orientation on the server's printer. This "executes" enough of the +orientation on 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/2K/XP printer properties page from a Window client @@ -7474,7 +7201,7 @@ followed the last section's description)

    • At the bottom of the con Connect... entry further above, you need to click that one first to achieve the driver installation as shown in the last section)

    • Go to the Advanced tab; click on -Printing Defaults...

    • Change the "Portrait" page setting to "Landscape" (and +Printing Defaults...

    • Change the "Portrait" page setting to "Landscape" (and back)

    • (Oh, and make sure to apply changes between swapping the page orientation to cause the change to actually take effect...).

    • While you're at it, you may optionally also want to @@ -7495,7 +7222,7 @@ 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. -

    Further Client Driver Install Procedures

    +

    Further Client Driver Install Procedures

    Every further driver may be done by any user, along the lines described above: Browse network, open printers folder on Samba server, right-click printer and choose Connect.... Once @@ -7515,12 +7242,12 @@ 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 that the very first connection from a client as -printer admin. This is to make sure that: +printer admin. This is to make sure that:

    • a first valid Device Mode is really initialized (see above for more explanation details), and that

    • the default print settings of your printer for all @@ -7534,30 +7261,33 @@ set to Letter, when you are all using

      To connect as root to a Samba printer, try this command from a Windows 2K/XP DOS box command prompt: -

      runas /netonly /user:root "rundll32 printui.dll,PrintUIEntry /p /t3 /n \\SAMBA-SERVER\printername" +

      +C:\> runas /netonly /user:root "rundll32 printui.dll,PrintUIEntry /p /t3 /n 
+	\\SAMBA-SERVER\printername"
+

      You will be prompted for root's Samba-password; type it, wait a few seconds, click on Printing Defaults... and proceed to set the job options as should be used as defaults by all clients. Alternatively, instead of root you can name one other member -of the printer admins from the setting. +of the printer admin from the setting.

      Now all the other users downloading and installing the driver the same way (called Point'n'Print) will have the same defaults set for them. If you miss this step you'll get a lot of helpdesk calls from your users. But maybe you like to talk to people.... ;-) -

    Other Gotchas

    +

    Other Gotchas

    Your driver is installed. It is ready for Point'n'Print installation by the clients now. You may have tried to download and use it onto your first client machine now. But wait... let's make you acquainted first with a few tips and tricks you may find useful. For -example, suppose you didn't manage to "set the defaults" on the +example, suppose you didn't manage to "set the defaults" on the printer, as advised in the preceding paragraphs? And your users complain about various issues (such as “We need to set the paper size for each job from Letter to A4 and it won't store it!”) -

    Setting Default Print Options for the Client Drivers

    +

    Setting Default Print Options for the Client Drivers

    The last sentence might be viewed with mixed feelings by some users and admins. They have struggled for hours and hours and couldn't arrive at a point were their settings seemed to be saved. It is not their @@ -7565,8 +7295,8 @@ fault. The confusing thing is this: in the multi-tabbed dialog that pops up when you right-click the printer name and select Properties..., you can arrive at two identically looking dialogs, each claiming that they help you to set printer options, -in three different ways. Here is the definite answer to the "Samba -Default Driver Setting FAQ": +in three different ways. Here is the definite answer to the "Samba +Default Driver Setting FAQ":

    “I can't set and save default print options for all users on Win2K/XP! Why not?”  How are you doing it? I bet the wrong way.... (it is not very @@ -7578,7 +7308,7 @@ dialogs look the same. Only one of them Administrator to do this for all users. Here is how I reproduce it in on XP Professional: -

    1. The first "wrong" way: +

      1. The first "wrong" way:

        1. Open the Printers folder.

        2. Right-click on the printer @@ -7586,7 +7316,7 @@ folder.

        3. Right-click on the printer select in context menu Printing Preferences...

        4. Look at this dialog closely and remember what it looks like.

        -

      2. The second "wrong" way: +

      3. The second "wrong" way:

        1. Open the Printers folder.

        2. Right-click on the printer (remoteprinter on @@ -7595,16 +7325,16 @@ cupshost) and select in the context menu tab

        3. Click on the button Printing Preferences...

        4. A new dialog opens. Keep this dialog open and go back to the parent dialog.

        -

      4. The third, the "correct" way: (should you do +

      5. The third, the "correct" way: (should you do this from the beginning, just carry out steps 1. and 2. from second -"way" above) +"way" above)

        1. Click on the Advanced -tab. (Hmmm... if everything is "Grayed Out", then you are not logged +tab. (Hmmm... if everything is "Grayed Out", then you are not logged in as a user with enough privileges).

        2. Click on the Printing Defaults... button.

        3. On any of the two new tabs, click on the Advanced... button.

        4. A new dialog opens. Compare this one to the other, -identical looking one from "B.5" or A.3".

        +identical looking one from "B.5" or A.3".

    Do you see any difference in the two settings dialogs? I don't @@ -7612,24 +7342,24 @@ either. However, only the last one, which you arrived at with steps C.1.-6. will permanently save any settings which will then become the defaults for new users. If you want all clients to have the same defaults, you need to conduct these steps as administrator -(printer admin in ) +(printer admin in ) before a client downloads the driver (the clients can later set their own per-user defaults by following the procedures A. or B. above...). (This is new: Windows 2000 and Windows XP allow per-user default settings and the ones the administrator gives them, before they set up their own). -The "parents" of the identically looking dialogs have a slight +The "parents" of the identically looking dialogs have a slight difference in their window names: one is called Default Print Values for Printer Foo on Server -Bar" (which is the one you need) and the other is -called "Print Settings for Printer Foo on Server -Bar". The last one is the one you arrive at when you +Bar" (which is the one you need) and the other is +called "Print Settings for Printer Foo on Server +Bar". The last one is the one you arrive at when you right-click on the printer and select Print Settings.... This is the one what you were taught to use back in the days of Windows NT! So it is only natural to try the same way with Win2k or WinXP. You wouldn't dream -that there is now a different "clicking path" to arrive at an +that there is now a different "clicking path" to arrive at an identically looking, but functionally different dialog to set defaults for all users!

    Tip

    Try (on Win2000 and WinXP) to run this command (as a user @@ -7644,9 +7374,9 @@ rundll32 printui.dll,PrintUIEntry /p /t0 /n\\SAMBA-SE

    to see the tab with the Printing Preferences... button (the one which doesn't set system-wide defaults). You can -start the commands from inside a DOS box" or from the Start +start the commands from inside a DOS box" or from the Start -- Run... menu. -

    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 100's of printers. Using Windows NT APW here is somewhat awkward (to say the least). If you @@ -7696,7 +7426,8 @@ following is an example of how this could be accomplished: 

    -root# rpcclient SAMBA-CUPS -U root%secret -c 'setdriver dm9110 "Heidelberg Digimaster 9110 (PS)"'
+root# rpcclient SAMBA-CUPS -U root%secret -c \
+  'setdriver dm9110 "Heidelberg Digimaster 9110 (PS)"'
  cmd = setdriver dm9110 Heidelberg Digimaster 9110 (PPD)
  Successfully set dm9110 to driver Heidelberg Digimaster 9110 (PS).

    @@ -7706,7 +7437,8 @@ following is an example of how this could be accomplished: cmd = enumprinters flags:[0x800000] name:[\\SAMBA-CUPS\dm9110] - description:[\\SAMBA-CUPS\dm9110,Heidelberg Digimaster 9110 (PS),110ppm HiVolume DANKA Stuttgart] + description:[\\SAMBA-CUPS\dm9110,Heidelberg Digimaster 9110 (PS),\ + 110ppm HiVolume DANKA Stuttgart] comment:[110ppm HiVolume DANKA Stuttgart] [....]

    @@ -7722,18 +7454,19 @@ following is an example of how this could be accomplished: cmd = enumprinters flags:[0x800000] name:[\\SAMBA-CUPS\dm9110] - description:[\\SAMBA-CUPS\dm9110,myphantasydrivername,110ppm HiVolume DANKA Stuttgart] + description:[\\SAMBA-CUPS\dm9110,myphantasydrivername,\ + 110ppm HiVolume DANKA Stuttgart] comment:[110ppm HiVolume DANKA Stuttgart] [....]

    It may be not easy to recognize: but the first call to -enumprinters showed the "dm9110" printer with an +enumprinters showed the "dm9110" printer with an empty string where the driver should have been listed (between the 2 -commas in the "description" field). After the +commas in the "description" field). After the setdriver command succeeded, all is well. (The CUPS Printing chapter has more info about the installation of printer drivers with the help of rpcclient). -

    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 @@ -7741,29 +7474,29 @@ is the Windows NT Add Printer Wizard icon. The APW will be shown only if:

    • ...the connected user is able to successfully execute an OpenPrinterEx(\\server) with administrative -privileges (i.e. root or printer admin). +privileges (i.e. root or printer admin).

      Tip

      Try this from a Windows 2K/XP DOS box command prompt:

      runas /netonly /user:root rundll32 printui.dll,PrintUIEntry /p /t0 /n \\SAMBA-SERVER\printersharename

      and click on Printing Preferences...

    • ... contains the setting -show add printer wizard = yes (the +show add printer wizard = yes (the default).

    The APW can do various things:

    • upload a new driver to the Samba [print$] share;

    • associate an uploaded driver with an existing (but -still "driverless") print queue;

    • exchange the currently used driver for an existing +still "driverless") print queue;

    • exchange the currently used driver for an existing print queue with one that has been uploaded before;

    • add an entirely new printer to the Samba host (only in -conjunction with a working add printer command; -a corresponding delete printer command for +conjunction with a working add printer command; +a corresponding delete printer command for removing entries from the Printers... folder may be provided too)

    The last one (add a new printer) requires more effort than the previous ones. In order to use the APW to successfully add a printer -to a Samba server, the add printer command must +to a Samba server, the add printer command must have a defined value. The program hook must successfully add the -printer to the Unix print system (i.e. to +printer to the UNIX print system (i.e. to /etc/printcap, /etc/cups/printers.conf or other appropriate files) and to if necessary. @@ -7773,13 +7506,11 @@ exist, smbd will execute the add printer command and reparse to the to attempt to locate the new printer share. If the share is still not defined, an error of Access Denied is -returned to the client. Note that the add printer -command is executed under the context of the connected -user, not necessarily a root account. A map to guest = bad -user may have connected you unwittingly under the wrong +returned to the client. Note that the add printer command is executed under the context of the connected +user, not 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. -

    Weird Error Message Cannot connect under a +

    Weird 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 @@ -7789,7 +7520,7 @@ perhaps reboot. connections to a server or a shared resource by the same user utilizing the several user names are not allowed. Disconnect all previous connections to the server, resp. the shared resource, and try -again.

  • Every attempt to "connect a network drive" to +again.

  • Every attempt to "connect a network drive" to \\SAMBASERVER\\print$ to z: is countered by the pertinacious message. This network folder is currently connected under different credentials (username and password). @@ -7809,20 +7540,20 @@ message. You close all Explorer Windows and start it again. You try to connect - and this times it works! Windows seems to cache connection info somewhere and doesn't keep it up to date (if you are unlucky you might need to reboot to get rid of the error message). -

    • Be careful when assembling Driver Files

    +

    Be careful when assembling Driver Files

    You need to be very careful when you take notes about the files and belonging to a particular driver. Don't confuse the files for driver -version "0" (for Win95/98/ME, going into -[print$]/WIN/0/), driver version "2" (Kernel Mode +version "0" (for Win95/98/ME, going into +[print$]/WIN/0/), driver version "2" (Kernel Mode driver for WinNT, going into [print$]/W32X86/2/ may be used on Win2K/XP too), and driver version -"3" (non-Kernel Mode driver going into +"3" (non-Kernel Mode driver going into [print$]/W32X86/3/ can not be used on WinNT). Very often these different driver versions contain files carrying the same name; but still the files are very different! Also, if you look at them from the Windows Explorer (they reside in %WINDOWS%\system32\spool\drivers\W32X86\) you -will probably see names in capital letters, while an "enumdrivers" +will probably see names in capital letters, while an "enumdrivers" command from Samba would show mixed or lower case letters. So it is easy to confuse them. If you install them manually using rpcclient and subcommands, you may even succeed @@ -7895,7 +7626,7 @@ reasons: Defaultdatatype: []

    -If we write the "version 2" files and the "version 3" files +If we write the "version 2" files and the "version 3" files into different text files and compare the result, we see this picture: 

    @@ -7933,7 +7664,7 @@ comparison:
 
     root# for i in cns3g.hlp cns3gui.dll cns3g.dll; do                  \
            smbclient //10.160.50.8/print\$ -U 'Administrator%xxxx' \
-           -c "cd W32X86/3; dir $i; cd .. ; cd 2; dir $i";      \
+           -c "cd W32X86/3; dir $i; cd .. ; cd 2; dir $i";      \
 		   done
 
   CNS3G.HLP               A   122981  Thu May 30 02:31:00 2002
@@ -7950,39 +7681,39 @@ In my example were even more differences than shown here.  Conclusion:
 you must be very careful to select the correct driver files for each
 driver version. Don't rely on the names alone. 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:, etc. Samba must also support the concept of ports associated with a printer. By -default, only one printer port, named "Samba Printer Port", exists on -a system. Samba does not really need such a "port" in order to print; +default, only one printer port, named "Samba Printer Port", exists on +a system. Samba does not really need such a "port" in order to print; it rather is a requirement of Windows clients. They insist on being told about an available port when they request this info, otherwise they throw an error message at you. So Samba fakes the port information to keep the Windows clients happy.

    -Note that Samba does not support the concept of "Printer Pooling" +Note that 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 fail over.

    If you require that multiple ports be defined for some reason or another (“My users and my Boss should not know that they are working with Samba”), possesses a -enumports command which can be used to define +enumports command which can be used to define an external program that generates a listing of ports on a system. -

    Avoiding the most common Misconfigurations of the Client Driver

    +

    Avoiding the most common Misconfigurations of the Client Driver

    So - printing works, but there are still problems. Most jobs print well, some don't print at all. Some jobs have problems with fonts, which don't look good at all. Some jobs print fast, and some are dead-slow. We can't cover it all; but we want to encourage you to read -the little paragraph about "Avoiding the wrong PostScript Driver -Settings" in the CUPS Printing part of this document. -

    The Imprints Toolset

    +the little paragraph about "Avoiding the wrong PostScript Driver +Settings" in the CUPS Printing part of this document. +

    The Imprints Toolset

    The Imprints tool set provides a UNIX equivalent of the Windows NT Add Printer Wizard. For complete information, please refer to the Imprints web site -athttp://imprints.sourceforge.net/ +at http://imprints.sourceforge.net/ as well as the documentation included with the imprints source distribution. This section will only provide a brief introduction to the features of Imprints. @@ -7995,20 +7726,20 @@ coordinate your efforts on the samba-technical 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.

    What is Imprints?

    +future.

    What is Imprints?

    Imprints is a collection of tools for supporting these goals:

    • Providing a central repository information regarding Windows NT and 95/98 printer driver packages

    • Providing the tools necessary for creating the Imprints printer driver packages.

    • Providing an installation client which 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

    +servers.

    Creating Printer Driver Packages

    The process of creating printer driver packages is beyond the scope of this document (refer to Imprints.txt also 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 @@ -8016,7 +7747,7 @@ package is digitally signed via GnuPG which can be used to verify that 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 in the Imprints-Client-HOWTO.ps file included with the imprints source package. @@ -8037,9 +7768,9 @@ wrapped around smbclient and rpcclient

  • rpcclient: Issue an AddPrinterEx() MS-RPC to actually create the printer

    • One of the problems encountered when implementing the Imprints tool set was the name space issues between various supported client -architectures. For example, Windows NT includes a driver named "Apple -LaserWriter II NTX v51.8" and Windows 95 calls its version of this -driver "Apple LaserWriter II NTX" +architectures. For example, Windows NT includes a driver named "Apple +LaserWriter II NTX v51.8" and Windows 95 calls its version of this +driver "Apple LaserWriter II NTX"

    The problem is how to know what client drivers have been uploaded for a printer. An astute reader will remember that the Windows NT Printer @@ -8057,7 +7788,7 @@ if is has not already been installed? 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 NT driver is installed first. -

    Add Network Printers at Logon without User Interaction

    +

    Add Network Printers at Logon 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. ( http://support.microsoft.com/default.aspx?scid=kb;en-us;189105 @@ -8067,7 +7798,7 @@ The ideas sketched out below are inspired by this article. It describes a commandline method which can be applied to install network and local printers and their drivers. This is most useful if integrated in Logon Scripts. You can see what options are -available by typing in a command prompt ("DOS box") this: +available by typing in a command prompt ("DOS box") this:

    rundll32 printui.dll,PrintUIEntry /?

    A window pops up which shows you all of the commandline switches available. An extensive list of examples is also provided. This is @@ -8077,22 +7808,16 @@ what a client logon script might contain, with a short explanation of what the lines actually do (it works if 2k/XP Windows clients access printers via Samba, but works for Windows-based print servers too): 

    -rundll32 printui.dll,PrintUIEntry /dn /n "\\sambacupsserver\infotec2105-IPDS" /q
-rundll32 printui.dll,PrintUIEntry /in /n "\\sambacupsserver\infotec2105-PS"
-rundll32 printui.dll,PrintUIEntry /y /n "\\sambacupsserver\infotec2105-PS"
+rundll32 printui.dll,PrintUIEntry /dn /n "\\sambacupsserver\infotec2105-IPDS" /q
+rundll32 printui.dll,PrintUIEntry /in /n "\\sambacupsserver\infotec2105-PS"
+rundll32 printui.dll,PrintUIEntry /y /n "\\sambacupsserver\infotec2105-PS"

    Here is a list of the used commandline parameters: -

    /dn

    deletes a network printer

    /q

    quiet modus

    /n

    names a printer

    /in

    adds a network printer connection

    /y

    sets printer as default printer

    -I have tested this with a Samba 2.2.7a and a Samba-3alpha24 -installation and Windows XP Professional clients. Note that this -specific command set works with network print queues (installing -local print queues requires different parameters, but this is of no -interest here). -

    • Line 1 deletes a possibly existing previous network +

      /dn

      deletes a network printer

      /q

      quiet modus

      /n

      names a printer

      /in

      adds a network printer connection

      /y

      sets printer as default printer

      • Line 1 deletes a possibly existing previous network printer infotec2105-IPDS (which had used native Windows drivers with LPRng that were removed from the server which was converted to CUPS). The /q at the end eliminates -"Confirm" or error dialog boxes popping up. They should not be +"Confirm" or error dialog boxes popping up. They should not be presented to the user logging on.

      • Line 2 adds the new printer infotec2105-PS (which actually is same physical device but is now run by the new CUPS printing system and associated @@ -8108,7 +7833,7 @@ default printer). The default printer selection may of course be different for different users.

      Note that the second line only works if the printer infotec2105-PS has an already working print queue -on "sambacupsserver", and if the printer drivers have successfully been +on "sambacupsserver", and if the printer drivers have successfully been uploaded (via APW , smbclient/rpcclient or cupsaddsmb) into the @@ -8124,7 +7849,7 @@ every time a user logs in; it's really quick anyway (1 to 2 seconds).

      The additional benefits for this are:

      • It puts in place any printer default setup changes -automatically at every user logon.

      • It allows for "roaming" users' login into the domain from +automatically at every user logon.

      • It allows for "roaming" users' login into the domain from different workstations.

      Since network printers are installed per user this much simplifies the process of keeping the installation up-to-date. The extra few seconds @@ -8132,7 +7857,7 @@ 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 on 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 @@ -8144,25 +7869,24 @@ on legacy systems, or execute the lpadmin command on more modern systems) and create the associated share in , then the APW will in effect really create a new printer on Samba and the UNIX print subsystem! -

    Migration of "Classical" printing to Samba-3

    -The basic "NT-style" printer driver management has not changed +

    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 setup, or if you -continued "Win9x-style" printing in your Samba 2.2 installations, it +continued "Win9x-style" printing in your Samba 2.2 installations, it is more of an effort. Please read the appropriate release notes and the HOWTO Collection for 2.2. You can follow several paths. Here are possible scenarios for migration:

    • You need to study and apply the new Windows NT printer -and driver support. Previously used parameters "printer -driver file", " printer driver" and -"printer driver location" are no longer +and driver support. Previously used parameters printer +driver file, printer driver and +printer driver location are no longer supported.

    • If you want to take advantage of WinNT printer driver support you also need to migrate the Win9x/ME drivers to the new setup.

    • An existing printers.def file -(the one specified in the now removed parameter printer -driver file = ...) will work no longer with Samba-3.0. In + (the one specified in the now removed parameter printer driver file) will work no longer with samba 3. In 3.0, smbd attempts to locate a Win9x/ME driver files for the printer in [print$] and additional settings in the TDB and only there; if it fails it will not (as 2.2.x @@ -8170,7 +7894,7 @@ used to do) drop down to using a printers.def (and all associated parameters). The make_printerdef tool is removed and there is no backwards compatibility for this.

    • You need to install a Windows 9x driver into the [print$] share for a printer on your Samba -host. The driver files will be stored in the "WIN40/0" subdirectory of +host. The driver files will be stored in the "WIN40/0" subdirectory of [print$], and some other settings and info go into the printing-related TDBs.

    • If you want to migrate an existing printers.def file into the new setup, the current @@ -8178,162 +7902,137 @@ only solution is to use the Windows NT APW to install the NT drivers and the 9x drivers. This can be scripted using smbclient and rpcclient. See the Imprints installation client at:

      -http://imprints.sourceforge.net/ + http://imprints.sourceforge.net/

      for an example. See also the discussion of rpcclient usage in the -"CUPS Printing" section.

    Publishing Printer Information in Active Directory or LDAP

    +"CUPS Printing" section.

    Publishing Printer Information in Active Directory or LDAP

    We will publish an update to this section shortly. -

    Common Errors and Problems

    -Here are a few typical errors and problems people have -encountered. You can avoid them. Read on. -

    I give my root password but I don't get access

    -Don't confuse the root password which is valid for the Unix system +

    Common Errors

    I give my root password but I don't get access

    +Don't 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 doesn't know the UNIX password; for root to access Samba resources via Samba-type access, a Samba account for root must be created first. This is often done with the smbpasswd command. -

    My printjobs get spooled into the spooling directory, but then get lost

    -Don't use the existing Unix print system spool directory for the Samba +

    My printjobs get spooled into the spooling directory, but then get lost

    +Don't use the existing UNIX print system spool directory for the Samba spool directory. It may seem convenient and a saving of space, but it only leads to problems. The two must be separate. -

    Chapter 19. CUPS Printing Support in Samba 3.0

    Kurt Pfeifle

    Danka Deutschland GmbH

    Ciprian Vizitiu

    drawings

    (3 June 2003)

    Table of Contents

    Introduction
    Features and Benefits
    Overview
    Basic Configuration of CUPS support
    Linking of smbd with libcups.so
    Simple smb.conf Settings for CUPS
    More complex smb.conf Settings for -CUPS
    Advanced Configuration
    Central spooling vs. "Peer-to-Peer" printing
    CUPS/Samba as a "spooling-only" Print Server; "raw" printing -with Vendor Drivers on Windows Clients
    Driver Installation Methods on Windows Clients
    Explicitly enable "raw" printing for -application/octet-stream!
    Three familiar Methods for driver upload plus a new one
    Using CUPS/Samba in an advanced Way -- 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
    CUPS can use all 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
    Filter Requirements
    Prefilters
    pstops
    pstoraster
    imagetops and imagetoraster
    rasterto [printers specific]
    CUPS Backends
    cupsomatic/Foomatic -- how do they fit into the Picture?
    The Complete Picture
    mime.convs
    "Raw" printing
    "application/octet-stream" printing
    PostScript Printer Descriptions (PPDs) for non-PS Printers
    Difference between cupsomatic/foomatic-rip and -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 -- UNIX/Samba Print -Servers)
    From Windows Clients to a CUPS/Samba Print Server
    Samba receiving Jobfiles and passing them to CUPS
    Network PostScript RIP: CUPS Filters on Server -- clients use -PostScript Driver with CUPS-PPDs
    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
    Setting up CUPS for driver Download
    cupsaddsmb: the unknown Utility
    Prepare your smb.conf for -cupsaddsmb
    CUPS Package of "PostScript Driver for WinNT/2k/XP"
    Recognize the different Driver Files
    Acquiring the Adobe Driver Files
    ESP Print Pro Package of "PostScript Driver for -WinNT/2k/XP"
    Caveats to be considered
    What are the Benefits of using the "CUPS PostScript Driver for -Windows NT/2k/XP" as compared to the Adobe Driver?
    Run "cupsaddsmb" (quiet Mode)
    Run "cupsaddsmb" with verbose Output
    Understanding cupsaddsmb
    How to recognize if cupsaddsm 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
    What is required for adddriver and setdriver to succeed
    Manual Commandline Driver Installation in 15 little 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
    Auto-Deletion or Preservation of CUPS Spool Files
    CUPS Configuration Settings explained
    Pre-conditions
    Manual Configuration
    When not to use Samba to print to -CUPS
    In Case of Trouble.....
    Where to find Documentation
    How to ask for Help
    Where to find Help
    Appendix
    Printing from CUPS to Windows attached -Printers
    More CUPS filtering Chains
    Trouble Shooting Guidelines to fix typical Samba printing -Problems
    An Overview of the CUPS Printing Processes

    Introduction

    Features and Benefits

    - The Common Unix Print System (CUPS) has become very popular. All - big Linux distributions now ship it as their default printing - system. But to many it is still a very mystical tool. Normally it - "just works" (TM). People tend to regard it as a sort of "black box", - which they don't want to look into, as long as it works OK. But once +

    Chapter 19. CUPS Printing Support in Samba 3.0

    Kurt Pfeifle

    Danka Deutschland GmbH

    Ciprian Vizitiu

    drawings

    Jelmer R. Vernooij

    drawings
    The Samba Team

    (3 June 2003)

    Table of Contents

    Introduction
    Features and Benefits
    Overview
    Basic Configuration of CUPS support
    Linking of smbd with libcups.so
    Simple smb.conf Settings for CUPS
    More complex smb.conf Settings for +CUPS
    Advanced Configuration
    Central spooling vs. "Peer-to-Peer" printing
    CUPS/Samba as a "spooling-only" Print Server; "raw" printing +with Vendor Drivers on Windows Clients
    Driver Installation Methods on Windows Clients
    Explicitly enable "raw" printing for +application/octet-stream!
    Three familiar Methods for driver upload plus a new one
    Using CUPS/Samba in an advanced Way -- 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
    CUPS can use all 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
    Filter Requirements
    Prefilters
    pstops
    pstoraster
    imagetops and imagetoraster
    rasterto [printers specific]
    CUPS Backends
    cupsomatic/Foomatic -- how do they fit into the Picture?
    The Complete Picture
    mime.convs
    "Raw" printing
    "application/octet-stream" printing
    PostScript Printer Descriptions (PPDs) for non-PS Printers
    Difference between cupsomatic/foomatic-rip and +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 -- UNIX/Samba Print +Servers)
    From Windows Clients to a CUPS/Samba Print Server
    Samba receiving Jobfiles and passing them to CUPS
    Network PostScript RIP: CUPS Filters on Server -- clients use +PostScript Driver with CUPS-PPDs
    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
    Setting up CUPS for driver Download
    cupsaddsmb: the unknown Utility
    Prepare your smb.conf for cupsaddsmb
    CUPS Package of "PostScript Driver for WinNT/2k/XP"
    Recognize the different Driver Files
    Acquiring the Adobe Driver Files
    ESP Print Pro Package of "PostScript Driver for +WinNT/2k/XP"
    Caveats to be considered
    Benefits of using "CUPS PostScript Driver for +Windows NT/2k/XP" instead of 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
    What is required 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
    Auto-Deletion or Preservation of CUPS Spool Files
    CUPS Configuration Settings explained
    Pre-conditions
    Manual Configuration
    In Case of Trouble.....
    Printing from CUPS to Windows attached +Printers
    More CUPS filtering Chains
    Common Errors
    Win9x client can't install driver
    "cupsaddsmb" keeps asking for root password in + neverending loop
    "cupsaddsmb" gives "No PPD file for printer..." + message while PPD file is present
    Client can't connect to Samba printer
    Can't reconnect to Samba under new account + from Win2K/XP
    Avoid being connected to the Samba server as the + "wrong" user
    Upgrading to CUPS drivers from Adobe drivers on + NT/2K/XP clients gives problems
    Can't use "cupsaddsmb" on Samba server which is + a PDC
    Deleted Win2K printer driver is still shown
    Win2K/XP "Local Security + Policies"
    WinXP clients: "Administrator can not install + printers for all local users"
    "Print Change Notify" functions on + NT-clients
    WinXP-SP1
    Print options for all users can't be set on Win2K/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
    Printer named "lp" +intermittently swallows jobs and spits out completely different +ones
    Location of Adobe PostScript driver files necessary for "cupsaddsmb"
    An Overview of the CUPS Printing Processes

    Introduction

    Features and Benefits

    + The Common UNIX Print System (CUPS) has become very popular. All + major Linux distributions now ship it as their default printing + system. To many it is still a very mystical tool. Mostly, it + "just works" (TM). People tend to regard it as a "black box" + which they don't want to look into, as long as it works. But once there is a little problem, they are in trouble to find out where to - start debugging it. Also, even the most recent and otherwise excellent - printed Samba documentation has only limited attention paid to CUPS - printing, leaving out important pieces or even writing plain wrong - things about it. This demands rectification. But before you dive into - this chapter, make sure that you don't forget to refer to the - "Classical Printing" chapter also. It contains a lot of information - that is relevant for CUPS too. + start debugging it. Refer to the "Classical Printing" chapter also, it + contains a lot of information that is relevant for CUPS.

    CUPS sports quite a few unique and powerful features. While their basic functions may be grasped quite easily, they are also new. Because they are different from other, more traditional printing systems, it is best to try and not apply any prior knowledge about - printing upon this new system. Rather try to start understand CUPS - from the beginning. This documentation will lead you here to a - complete understanding of CUPS, if you study all of the material - contained. But lets start with the most basic things first. Maybe this - is all you need for now. Then you can skip most of the other - paragraphs. -

    Overview

    + printing upon 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

    CUPS is more than just a print spooling system. It is a complete printer management system that complies with the new IPP (Internet Printing Protocol). IPP is an industry and IETF (Internet Engineering Task Force) standard for network printing. Many of its functions can be managed remotely (or locally) via a web browser (giving you a - platform-independent access to the CUPS print server). In addition it - has the traditional commandline and several more modern GUI interfaces + platform-independent access to the CUPS print server). Additionally, it + has the traditional command line and several more modern GUI interfaces (GUI interfaces developed by 3rd parties, like KDE's overwhelming KDEPrint).

    - CUPS allows creation of "raw" printers (ie: NO print file - format translation) as well as "smart" printers (i.e. CUPS does + CUPS allows creation of "raw" printers (ie: 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 similar capabilities 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 move on to explore how one may configure CUPS for interfacing with MS Windows print clients via Samba. -

    Basic Configuration of CUPS support

    - Printing with CUPS in the most basic smb.conf - setup in Samba 3.0 (as was true for 2.2.x) only needs two - settings: printing = cups and printcap - = cups. CUPS itself doesn't need a printcap file - anymore. However, the cupsd.conf configuration - file knows two related directives: they control if such a file should - be automatically created and maintained by CUPS for the convenience of - third party applications (example: Printcap - /etc/printcap and PrintcapFormat - BSD). These legacy programs often require the existence of - printcap file containing printernames or they will refuse to - print. Make sure CUPS is set to generate and maintain a printcap! For - details see man cupsd.conf and other CUPS-related - documentation, like the wealth of documents on your CUPS server +

    Basic Configuration of CUPS support

    + Printing with CUPS in the most basic smb.conf setup in Samba 3.0 (as was true for 2.2.x) only needs two + settings: 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 file will be automatically created and maintained by CUPS for the convenience of third party + applications (example: Printcap /etc/printcap and PrintcapFormat BSD). + Legacy programs often require the existence of a printcap file containing printer names or they will refuse to + 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 on your CUPS server itself: http://localhost:631/documentation.html. -

    Linking of smbd with libcups.so

    - Samba has a very special relationship to CUPS. The reason is: Samba - can be compiled with CUPS library support. Most recent installations - have this support enabled, and per default CUPS linking is compiled +

    Linking of smbd with libcups.so

    + Samba has a very special relationship to CUPS. Samba can be compiled with CUPS library support. + Most recent installations have this support enabled. Per 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 then.

    - If SAMBA is compiled against libcups, then printcap = - cups uses the CUPS API to list printers, submit jobs, - query queues, etc. Otherwise it maps to the System V commands with an - additional -oraw option for printing. On a Linux - system, you can use the ldd utility to find out - details (ldd may not be present on other OS platforms, or its function - may be embodied by a different command): + When Samba is compiled against libcups, printcap = cups + uses the CUPS API to list printers, submit jobs, query queues, etc. Otherwise it maps to the System V + commands with an additional -oraw option for printing. On a Linux + system, you can use the ldd utility to find out details (ldd may not be present on + other OS platforms, or its function may be embodied by a different command): 

    -				transmeta:/home/kurt # ldd `which smbd`
-				libssl.so.0.9.6 => /usr/lib/libssl.so.0.9.6 (0x4002d000)
-				libcrypto.so.0.9.6 => /usr/lib/libcrypto.so.0.9.6 (0x4005a000)
-				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. This is an - important point to remember! -

    Tip

    Should you require -- for any reason -- to set your own - print commands, you can still do this by setting printing = - sysv. However, you'll loose all the benefits from the - close CUPS/Samba integration. You are on your own then to manually - configure the rest of the printing system commands (most important: - print command; other commands are - lppause command, lpresume command, lpq command, lprm - command, queuepause command and queue resume - command).

    Simple smb.conf Settings for CUPS

    - To summarize, here is the simplest printing-related setup - for smb.conf to enable basic CUPS support: - 

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

    +root# ldd `which smbd` +libssl.so.0.9.6 => /usr/lib/libssl.so.0.9.6 (0x4002d000) +libcrypto.so.0.9.6 => /usr/lib/libcrypto.so.0.9.6 (0x4005a000) +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. + This is an important point to remember! +

    Tip

    Should it be necessary, for any reason, to set your own print commands, you can do this by setting + printing = sysv. However, you will loose all the benefits + of tight CUPS/Samba integration. When you do this you must manually configure the printing system commands + (most important: print command; other commands are + lppause command, + lpresume command, + lpq command, + lprm command, + queuepause command and + queue resume command).

    Simple smb.conf Settings for CUPS

    + To summarize, here is the simplest printing-related setup for smb.conf to enable basic CUPS support: +

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

    This is all you need for basic printing setup for CUPS. It will print all Graphic, Text, PDF and PostScript file submitted from Windows clients. However, most of your Windows users would not know how to @@ -8343,92 +8042,54 @@ Problems

    An Overview of the CUPS Printing Proce driver. Your users also very rarely send files from the command line. Unlike UNIX clients, they hardly submit graphic, text or PDF formatted files directly to the spooler. They nearly exclusively print - from GUI applications, with a "printer driver" hooked in between the + from GUI applications, with a "printer driver" hooked in between the applications native format and the print data stream. If the backend - printer is not a PostScript device, the print data stream is "binary", + printer is not a PostScript device, the print data stream is "binary", sensible only for the target printer. Read on to learn which problem this may cause and how to avoid it. -

    More complex smb.conf Settings for +

    More complex smb.conf Settings for CUPS

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

    -
- [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
-         writeable = 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 there for my testing purposes. It doesn't -even 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 jobfile. Moreover, the printer -admin of this share is "kurt" (not the "@ntadmins" group); -guest access is not allowed; the share isn't announced in Network -Neighbourhood (so you need to know it is there), and it is only -allowing access from three hosts. To prevent CUPS kicking in and -taking over the print jobs for that share, we need to set -printing = sysv and printcap = -lpstat. -

    Advanced Configuration

    -Before we dive into all the configuration options, let's clarify a few +

    Example 19.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
    writeable = 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 there 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 jobfile. Moreover, the +printer admin of this share is "kurt" (not the "@ntadmins" group); +guest access is not allowed; the share isn not published to the Network Neighbourhood (so you need to know it is there), and it only +allows access from only three hosts. To prevent CUPS kicking in and taking over the print jobs for that share, we need to set +printing = sysv and +printcap = lpstat. +

    Advanced Configuration

    +Before we delve into all the configuration options, let us clarify a few points. Network printing needs to be organized and setup correctly. Often this is not done correctly. Legacy systems -or small LANs in business environments often lack a clear design and -good housekeeping. -

    Central spooling vs. "Peer-to-Peer" printing

    +or small business LAN environments often lack design and good housekeeping. +

    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. Generally, this is a bad idea. It often blocks one client's +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 also might freeze the first client's application while it is waiting to get rid of the job. Also, there are frequent complaints about various jobs being printed with their pages mixed with each other. A better concept -is the usage of a "print server": it routes all jobs through one +is the usage of a "print server": it routes all jobs through one central system, which responds immediately, takes jobs from multiple concurrent clients at the same time and in turn transfers them to the printer(s) in the correct order. -

    CUPS/Samba as a "spooling-only" Print Server; "raw" printing -with Vendor Drivers on Windows Clients

    -Most traditionally configured Unix print servers acting on behalf of +

    CUPS/Samba as a "spooling-only" Print Server; "raw" printing +with 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 +task was to manage the "raw" spooling of all jobs handed to them by Samba. This approach meant that the Windows clients were expected to -prepare the print job file in such a way that it became fit to be fed to -the printing device. Here a native (vendor-supplied) Windows printer +prepare the print job file that it s ready to be sent to the printing +device. Here a native (vendor-supplied) Windows printer driver for the target device needed to be installed on each and every client.

    -Of course you can setup CUPS, Samba and your Windows clients in the +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 Samba client to fully render the print job (file). The file must be @@ -8436,24 +8097,26 @@ sent in a format that is suitable for direct delivery to the printer. Clients need to run the vendor-provided drivers to do this. In this case CUPS will NOT do any print file format conversion work. -

    Driver Installation Methods on Windows Clients

    +

    Driver Installation Methods on Windows Clients

    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; it uses a \\sambaserver\printershare -type of connection.

    • deposit and prepare the drivers (for later download) on +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 +"Point and Print" to get drivers semi-automatically installed the first time they access the printer; with this method NT/2K/XP clients use the SPOOLSS/MS-RPC type printing calls.

    The second method is recommended for use over the first. -

    Explicitly enable "raw" printing for -application/octet-stream!

    +

    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 +that it should allow "raw" printing of deliberate (binary) file formats. The CUPS files that need to be correctly set for RAW mode printers to work are:

    • /etc/cups/mime.types @@ -8463,68 +8126,66 @@ be uncommented to allow RAW mode operation. In/etc/cups/mime.types make sure this line is present: 

      -
  application/octet-stream
-

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

      -
+
        application/octet-stream   application/vnd.cups-raw   0   - 
-
 
      
 If these two files are not set up correctly for raw Windows client
 printing, you may encounter the dreaded Unable to
 convert file 0 in your CUPS error_log file. 
 
      Note
      editing the mime.convs and the
 mime.types file does not
-enforce "raw" printing, it only
+enforce "raw" printing, it only
 allows it.
-
      Background. 
+

    Background.  CUPS being 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 the least -the loss of a lot of paper and ink. "Unknown" data are tagged by CUPS +"Denial of Service" attack on your printer(s), causing at the least +the loss of a lot of paper and ink. "Unknown" data are tagged by CUPS as MIME type: application/octet-stream and not allowed to go to the printer. By default, you can only send other -(known) MIME types "raw". Sending data "raw" means that CUPS does not +(known) MIME types "raw". Sending data "raw" means that CUPS does not try to convert them and passes them to the printer untouched (see next chapter for even more background explanations).

    This is all you need to know to get the CUPS/Samba combo printing -"raw" files prepared by Windows clients, which have vendor drivers +"raw" files prepared by Windows clients, which have vendor drivers locally installed. If you are not interested in background information about more advanced CUPS/Samba printing, simply skip the remaining sections of this chapter. -

    Three familiar Methods for driver upload plus a new one

    +

    Three familiar Methods for driver upload plus a new one

    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 Samba host (so that the Windows clients can download and use them via -"Point'n'Print") please also refer to the previous chapter of this +"Point'n'Print") please also refer to the previous chapter of this HOWTO Collection. 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" +

      • the GUI, "Add Printer Wizard" upload-from-a-Windows-client -method;

      • the commandline, "smbclient/rpcclient" +method;

      • the commandline, "smbclient/rpcclient" upload-from-a-UNIX-workstation -method;

      • the Imprints Toolset +method;

      • + + the Imprints Toolset method.

      These 3 methods apply to CUPS all the same. A new and more convenient way to load the Windows drivers into Samba is provided -provided if you use CUPS: -

      • the cupsaddsmb +if you use CUPS: +

        • the cupsaddsmb utility.

        cupsaddsmb is discussed in much detail further below. But we will first explore the CUPS filtering system and compare the Windows and UNIX printing architectures. -

    Using CUPS/Samba in an advanced Way -- intelligent printing -with PostScript Driver Download

    -Still reading on? Good. Let's go into more detail then. We now know -how to set up a "dump" printserver, that is, a server which is spooling -printjobs "raw", leaving the print data untouched. +

    Using CUPS/Samba in an advanced Way -- intelligent printing +with PostScript Driver Download

    +Are you still following this? Good. Let's go into more detail then. We now know +how to set up a "dump" printserver, that is, a server which is spooling +printjobs "raw", leaving the print data untouched.

    Possibly you need to setup CUPS in a more smart way. The reasons could be manifold: @@ -8535,33 +8196,33 @@ peaks in printing? Which departments prints how much?

  • Maybe you are asked to setup a print quota system: users should not be able to print more jobs, once they have surpassed a given limit per period?

  • Maybe your previous network printing setup is a mess -and shall be re-organized from a clean beginning?

  • Maybe you have experiencing too many "Blue Screens", -originating from poorly debugged printer drivers running in NT "kernel -mode"?

    • +and shall be re-organized from a clean beginning?

  • Maybe you have experiencing too many "Blue Screens", +originating from poorly debugged printer drivers running in NT "kernel +mode"?

    • These goals cannot be achieved by a raw print server. To build a server meeting these requirements, you'll first need to learn about how CUPS works and how you can enable its features.

    What follows is the comparison of some fundamental concepts for -Windows and Unix printing; then is the time for a description of the +Windows and UNIX printing; then is the time for a description of the CUPS filtering system, how it works and how you can tweak it. -

    GDI on Windows -- PostScript on Unix

    +

    GDI on Windows -- PostScript on UNIX

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

    +

    You can't expect for most file formats to just throw them towards printers and they get printed. There needs to be a file format conversion in between. The problem is: 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 HP), have developed -into semi-official "standards", by being the most widely used PDLs +into semi-official "standards", by being the most widely used PDLs (Page Description Languages), there are still -many manufacturers who "roll their own" (their reasons may be +many manufacturers who "roll their own" (their reasons may be unacceptable license fees for using printer-embedded PostScript interpreters, etc.). -

    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 GDI (Graphical Device @@ -8571,23 +8232,24 @@ all Windows programs, to draw pictures, fonts and documents on screen as well as on paper (=print). Therefore printer driver developers can standardize on a well-defined GDI output for their own driver -input. Achieving WYSIWYG ("What You See Is What You Get") is +input. Achieving WYSIWYG ("What You See Is What You Get") is relatively easy, because the on-screen graphic primitives, as well as the on-paper drawn objects, come from one common source. This source, the GDI, produces often a file format called EMF (Enhanced MetaFile). 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 their -(BSD-Unix-based, did you know??) Mac OS X and Darwin Operating -Systems.Their Core Graphic Engine uses a -PDF derivate for all display work. +(BSD-UNIX-based, did you know??) Mac OS X and Darwin Operating +Systems. Their Core Graphic Engine uses a +PDF derivative for all display work.

    -

    Figure 19.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 +

    Figure 19.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. That gives at least some common ground. Unfortunately, @@ -8597,17 +8259,17 @@ the same document is displayed on screen and how it is presented on paper. WYSIWYG is more difficult to achieve. This goes back to the time decades ago, when the predecessors of X.org, designing the UNIX foundations and protocols for Graphical User -Interfaces refused to take over responsibility for "paper output" +Interfaces refused to take over responsibility for "paper output" also, as some had demanded at the time, and restricted itself to -"on-screen only". (For some years now, the "Xprint" project has been +"on-screen only". (For some years now, the "Xprint" project has been under development, attempting to build printing support into the X framework, including a PostScript and a PCL driver, but it is not yet ready for prime time.) You can see this unfavorable inheritance up to -the present day by looking into the various "font" directories on your +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 Inc., +

    Background.  +The PostScript programming language is an "invention" by Adobe Inc., but its specifications have been published to the full. Its strength lies in its powerful abilities to describe graphical objects (fonts, shapes, patterns, lines, curves, dots...), their attributes (color, @@ -8616,69 +8278,71 @@ shift...) them. Because of its open specification, anybody with the skill can start writing his own implementation of a PostScript interpreter and use it to display PostScript files on screen or on paper. Most graphical output devices are based on the concept of -"raster images" or "pixels" (one notable exception are pen +"raster images" or "pixels" (one notable exception are pen plotters). Of course, you can look at a PostScript file in its textual form and you will be reading its PostScript code, the language instructions which need to be 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 +

    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: these devices have a built-in PostScript -language "interpreter", also called a Raster Image +language "interpreter", also called a Raster Image Processor (RIP), (which makes them more expensive than other types of printers); throw PostScript towards them, and they will spit out your printed pages. Their RIP is doing all the hard work of converting the PostScript drawing commands into a bitmap picture as you see it on paper, in a resolution as done by your printer. This is no different to PostScript printing of 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 +

    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, punching... Therefore -Unix users for a long time couldn't choose many of the supported +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.... ;-) +is CUPS....

    -

    Figure 19.2. Printing to a Postscript Printer

    Printing to a Postscript Printer

    -

    +

    Figure 19.2. Printing to a Postscript Printer

    Printing to a Postscript Printer

    +

    However, there are other types of printers out there. These don't know how to print PostScript. They use their own Page Description Language (PDL, often proprietary). To print to them is much -more demanding. Since your Unix applications mostly produce +more demanding. Since your UNIX applications mostly produce PostScript, and since these devices don't understand PostScript, you need to convert the printfiles 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 to do a +UNIX platforms. It is a RIP in software, capable to do a lot of file format conversions, for a very broad spectrum of hardware devices as well as software file formats. Ghostscript technology and drivers is what enables PostScript printing to non-PostScript hardware.

    -

    Figure 19.3. Ghostscript as a RIP for non-postscript printers

    Ghostscript as a RIP for non-postscript printers

    +

    Figure 19.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" of your +Use the "gs -h" command to check for all built-in "devices" of your Ghostscript version. If you specify e.g. 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 commandline is the most important +file. Naming a "device" on the commandline is the most important single parameter to tell Ghostscript how exactly it should render the 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" 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 got some -deficiencies. Therefore ESP Ghostscript was developed as an +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, RedHat and Debian. It includes -the "cups" device (essential to print to non-PS printers from CUPS). -

    PostScript Printer Description (PPD) Specification

    +the "cups" device (essential to print to non-PS printers from CUPS). +

    PostScript Printer Description (PPD) Specification

    While PostScript in essence is a Page Description Language (PDL) to represent the page layout in a device independent way, real world print jobs are @@ -8704,15 +8368,16 @@ user selections are somehow written (in the form of special 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). -

    CUPS can use all Windows-formatted Vendor PPDs

    +

    CUPS can use all Windows-formatted Vendor PPDs

    CUPS can handle all spec-compliant PPDs as supplied by the manufacturers for their PostScript models. Even if a -Unix/Linux-illiterate vendor might not have mentioned our favorite +UNIX/Linux-illiterate vendor might not have mentioned our favorite OS in his manuals and brochures -- you can safely trust this: if you get hold of the Windows NT version of the PPD, you can use it unchanged in CUPS and thus access the full @@ -8724,6 +8389,8 @@ immediately. CUPS in all versions after 1.1.19 has a much more strict internal PPD parsing and checking code enabled; in case of printing trouble this online resource should be one of your first pitstops.

    Warning

    + + For real PostScript printers don't use the Foomatic or cupsomatic PPDs from Linuxprinting.org. With these devices the original @@ -8736,7 +8403,7 @@ your LAN has the PostScript driver installed, just use access the Windows directory where all printer driver files are stored. First look in the W32X86/2 subdir 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 @@ -8744,7 +8411,7 @@ 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 @@ -8760,33 +8427,37 @@ given input data format.

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

    • the first stage uses a Ghostscript device named "cups" +

      • 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" which converts +called "CUPS raster". +

      • the second stage uses a "raster driver" which converts the generic CUPS raster to a device specific raster.

      -Make sure your Ghostscript version has the "cups" device compiled in +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 +0 in your CUPS error_log file. To have "cups" as a device in your Ghostscript, you either need to patch GNU -Ghostscript and re-compile or use ESP Ghostscript. The +Ghostscript and re-compile or use ESP Ghostscript. The superior alternative is ESP Ghostscript: it supports not just CUPS, but 300 other devices too (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 setup to use external rendering paths. One of the most common ones is provided by the Foomatic/cupsomatic concept, from Linuxprinting.org. This uses the classical Ghostscript approach, doing everything in one -step. It doesn't use the "cups" device, but one of the many +step. It doesn't use the "cups" device, but one of the many others. However, even for Foomatic/cupsomatic usage, best results and + broadest printer model support is provided by ESP Ghostscript (more about cupsomatic/Foomatic, particularly the new version called now foomatic-rip, follows below). -

      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 @@ -8795,10 +8466,10 @@ auto-typing 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 either a .pdf suffix, or if the magic @@ -8807,9 +8478,7 @@ 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>%!)
-

      Its meaning: if the filename has one of the suffixes .ai, .eps, @@ -8839,7 +8508,7 @@ CUPS can handle ASCII text, HP-GL, PDF, PostScript, DVI and a lot of image formats (GIF. PNG, TIFF, JPEG, Photo-CD, SUN-Raster, PNM, PBM, SGI-RGB and some 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 @@ -8848,39 +8517,31 @@ conversion filter which can produce the output from the input type and virtual costs associated with this conversion. One example line reads like this: 

      -
  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:
+to work on "text/plain" as well as on "application/x-shell". (Hint:
 this differentiation is needed for the syntax highlighting feature of
-"texttops").
-

      Filter Requirements

      +"texttops"). +

      Filter Requirements

      There are many more combinations named in mime.convs. However, you are not limited to use the ones pre-defined there. You can plug in any filter you like into the CUPS framework. It must meet, or must be made @@ -8890,24 +8551,24 @@ needs, and put in the right lines in mime.types and mime.convs, then it will work seamlessly inside CUPS!

      Tip

      -The mentioned "CUPS requirements" for filters are simple. Take +The mentioned "CUPS requirements" for filters are simple. Take filenames or stdin as input and write to stdout. They should take these 5 or 6 arguments: printer job user title copies options [filename]

      Printer

      The name of the printer queue (normally this is the name of the filter being run)

      job

      The numeric job ID for the job being -printed

      Printer

      The string from the originating-user-name -attribute

      Printer

      The string from the job-name attribute

      Printer

      The numeric value from the number-copies -attribute

      Printer

      The job options

      Printer

      (Optionally) The print request file (if missing, +printed

      user

      The string from the originating-user-name +attribute

      title

      The string from the job-name attribute

      copies

      The numeric value from the number-copies +attribute

      options

      The job options

      filename

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

      Prefilters

      -As was said, PostScript is the central file format to any Unix based +filters to make them work with CUPS.

    Prefilters

    +As was said, 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 is happening if you send one of the supported non-PS formats -to print? Then CUPS runs "pre-filters" on these input formats to +to print? Then CUPS runs "pre-filters" on these input formats to generate PostScript first. There are pre-filters to create PS from ASCII text, PDF, DVI or HP-GL. The outcome of these filters is always of MIME type application/postscript (meaning that @@ -8919,8 +8580,8 @@ MIME type application/vnd.cups-postscript (not application/postscript), meaning it has the print options already embedded into the file.

    -

    Figure 19.4. Prefiltering in CUPS to form Postscript

    Prefiltering in CUPS to form Postscript

    -

    pstops

    +

    Figure 19.4. Prefiltering in CUPS to form Postscript

    Prefiltering in CUPS to form Postscript

    +

    pstops

    pstopsis the filter to convert application/postscript to application/vnd.cups-postscript. It was said @@ -8928,19 +8589,19 @@ above that this filter inserts all device-specific print options (commands to the printer to ask for the duplexing of output, or stapling an punching it, etc.) into the PostScript file.

    -

    Figure 19.5. Adding Device-specific Print Options

    Adding Device-specific Print Options

    +

    Figure 19.5. Adding Device-specific Print Options

    Adding Device-specific Print Options

    This is not all: other tasks performed by it are:

    • selecting the range of pages to be printed (if you choose to -print only pages "3, 6, 8-11, 16, 19-21", or only the odd numbered +print only pages "3, 6, 8-11, 16, 19-21", or only the odd numbered ones)

    • putting 2 or more logical pages on one sheet of paper (the -so-called "number-up" function) +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; @@ -8949,34 +8610,34 @@ yet meant to be printable. Its aim is to serve as a general purpose input format for more specialized raster drivers, that are able to generate device-specific printer data.

    -

    Figure 19.6. Postscript to intermediate Raster format

    Postscript to intermediate Raster format

    +

    Figure 19.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 following downstream raster drivers. Its MIME type is registered with IANA and its specification is of course completely open. It is designed to make it very easy and inexpensive for -manufacturers to develop Linux and Unix raster drivers for their +manufacturers to develop Linux and UNIX raster drivers for their printer models, should they choose to do so. CUPS always takes care for the first stage of rasterization so these vendors don't need to care about Ghostscript complications (in fact, there is currently more than one vendor financing the development of CUPS raster drivers).

    -

    Figure 19.7. CUPS-raster production using Ghostscript

    CUPS-raster production using Ghostscript

    +

    Figure 19.7. CUPS-raster production using Ghostscript

    CUPS-raster production using Ghostscript

    CUPS versions before version 1.1.15 were shipping a binary (or source -code) standalone filter, named "pstoraster". pstoraster was derived +code) standalone filter, named "pstoraster". pstoraster was derived from GNU Ghostscript 5.50, and could be installed besides and in addition to any GNU or AFPL Ghostscript package without conflicting.

    From version 1.1.15, this has changed. The functions for this has been integrated back into Ghostscript (now based on GNU Ghostscript version -7.05). The "pstoraster" filter is now a simple shell script calling +7.05). The "pstoraster" filter is now a simple shell script calling gs with the -sDEVICE=cups parameter. If your Ghostscript doesn't show a success on asking for gs -h |grep cups, you might not be able to print. Update your Ghostscript then! -

    imagetops and imagetoraster

    +

    imagetops and imagetoraster

    Above 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 @@ -8984,13 +8645,13 @@ intermediate PostScript stage. It is used more often than the above mentioned prefilters. Here is a summarizing flowchart of image file filtering:

    -

    Figure 19.8. Image format to CUPS-raster format conversion

    Image format to CUPS-raster format conversion

    -

    rasterto [printers specific]

    +

    Figure 19.8. Image format to CUPS-raster format conversion

    Image format to CUPS-raster format conversion

    +

    rasterto [printers specific]

    CUPS ships with quite some different raster drivers processing CUPS raster. On my system I find in /usr/lib/cups/filter/ these: -rastertoalps, rastertobj, rastertoepson, rastertoescp, -rastertopcl, rastertoturboprint, rastertoapdk, rastertodymo, -rastertoescp, rastertohp and +rastertoalps, rastertobj, rastertoepson, rastertoescp, +rastertopcl, rastertoturboprint, rastertoapdk, rastertodymo, +rastertoescp, rastertohp and rastertoprinter. Don't worry if you have less than this; some of these are installed by commercial add-ons to CUPS (like rastertoturboprint), others (like @@ -8998,13 +8659,13 @@ than this; some of these are installed by commercial add-ons to CUPS development projects (such as Gimp-Print) wanting to cooperate as closely as possible with CUPS.

    -

    Figure 19.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 +

    Figure 19.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 -"protocol" of sending printjobs over the network, or for every local -interface. Every CUPS printqueue needs to have a CUPS "device-URI" +"protocol" of sending printjobs over the network, or for every local +interface. Every CUPS printqueue needs to have a CUPS "device-URI" associated with it. The device URI is the way to encode the backend used to send the job to its destination. Network device-URIs are using two slashes in their syntax, local device URIs only one, as you can @@ -9031,8 +8692,8 @@ This backend sends printfiles to LPR/LPD connected network printers. An example for the CUPS device-URI to use is: lpd://remote_host_name/remote_queue_name

    AppSocket/HP JetDirect

    -This backend sends printfiles to AppSocket (a.k.a. "HP -JetDirect") connected network printers. An example for the CUPS +This backend sends printfiles to AppSocket (a.k.a. "HP +JetDirect") connected network printers. An example for the CUPS device-URI to use is: socket://10.11.12.13:9100

    ipp

    @@ -9054,7 +8715,7 @@ This backend sends printfiles to printers shared by a Windows host. An example for CUPS device-URIs to use are: smb://workgroup/server/printersharename Or -Smb://server/printersharename +smb://server/printersharename or smb://username:password@workgroup/server/printersharename or @@ -9067,11 +8728,11 @@ root user create it: ln -s `which smbspool`

    It is easy to write your own backends as Shell or Perl scripts, if you need any modification or extension to the CUPS print system. One -reason could be that you want to create "special" printers which send -the printjobs as email (through a "mailto:/" backend), convert them to -PDF (through a "pdfgen:/" backend) or dump them to "/dev/null" (In +reason could be that you want to create "special" printers which send +the printjobs as email (through a "mailto:/" backend), convert them to +PDF (through a "pdfgen:/" backend) or dump them to "/dev/null" (In fact I have the system-wide default printer set up to be connected to -a "devnull:/" backend: there are just too many people sending jobs +a "devnull:/" backend: there are just too many people sending jobs without specifying a printer, or scripts and programs which don't name a printer. The system-wide default deletes the job and sends a polite mail back to the $USER asking him to always specify a correct @@ -9080,29 +8741,25 @@ printername). 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 -utility. Used with the -v parameter, it lists +utility. Used with the -v parameter, it lists all available backends: 

    -
- lpinfo -v
-
-

    cupsomatic/Foomatic -- how do they fit into the Picture?

    -"cupsomatic" filters may be the most widely used on CUPS +$ lpinfo -v +

    cupsomatic/Foomatic -- how do they fit into the Picture?

    +"cupsomatic" filters may be the most widely used on CUPS installations. You must be clear about the fact that these were not -developed by the CUPS people. They are a "Third Party" add-on to +developed by the CUPS people. They are a "Third Party" add-on to CUPS. They utilize the traditional Ghostscript devices to render jobs for CUPS. When troubleshooting, you should know about the difference. Here the whole rendering process is done in one stage, -inside Ghostscript, using an appropriate "device" for the target -printer. cupsomatic uses PPDs which are generated from the "Foomatic" +inside Ghostscript, using an appropriate "device" for the target +printer. cupsomatic uses PPDs which are generated from the "Foomatic" Printer & Driver Database at Linuxprinting.org.

    You can recognize these PPDs from the line calling the cupsomatic filter: 

    -
- *cupsFilter: "application/vnd.cups-postscript  0  cupsomatic"
-
+ *cupsFilter: "application/vnd.cups-postscript  0  cupsomatic"

    This line you may find amongst the first 40 or so lines of the PPD file. If you have such a PPD installed, the printer shows up in the @@ -9111,18 +8768,18 @@ the driver description. cupsomatic is a Perl script that runs Ghostscript, with all the complicated commandline options auto-constructed from the selected PPD and commandline options give to the printjob. -

    +

    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, +to download them with "Point'n'Print" to Windows clients. A better, and more powerful successor is now in a very stable Beta-version available: it is called foomatic-rip. To use foomatic-rip as a filter with CUPS, you need the new-type PPDs. These have a similar, but different line: 

     
- *cupsFilter: "application/vnd.cups-postscript  0  foomatic-rip"
+ *cupsFilter: "application/vnd.cups-postscript  0  foomatic-rip"

    The PPD generating engine at Linuxprinting.org has been revamped. @@ -9136,11 +8793,11 @@ print-options from page to page, in the middle of a job. And the best thing is: the new foomatic-rip now works seamlessly with all legacy spoolers too (like LPRng, BSD-LPD, PDQ, PPR etc.), providing for them access to use PPDs for their printing! -

    The Complete Picture

    +

    The Complete Picture

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

    mime.convs

    +

    mime.convs

    CUPS auto-constructs all possible filtering chain paths for any given MIME type, and every printer installed. But how does it decide in favor or against a specific alternative? (There may often be cases, @@ -9148,39 +8805,37 @@ where there is a choice of two or more possible filtering chains for the same target printer). Simple: you may have noticed the figures in the 3rd column of the mime.convs file. They represent virtual costs assigned to this filter. Every possible filtering chain will sum up to -a total "filter cost". CUPS decides for the most "inexpensive" route. +a total "filter cost". CUPS decides for the most "inexpensive" route.

    Tip

    The setting of FilterLimit 1000 in cupsd.conf will not allow more filters to run concurrently than will consume a total of 1000 virtual filter cost. This is a very efficient way to limit the load of any CUPS -server by setting an appropriate "FilterLimit" value. A FilterLimit of +server by setting an appropriate "FilterLimit" value. A FilterLimit of 200 allows roughly 1 job at a time, while a FilterLimit of 1000 allows approximately 5 jobs maximum at a time. -

    "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" +

    "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 happen on any queue if the "-o raw" option is specified +printing can happen on any queue if the "-o raw" option is specified on the command line. You can also set up raw-only queues by simply not associating any PPD with it. This command: 

    -
- lpadmin -P rawprinter -v socket://11.12.13.14:9100 -E
-
+$ lpadmin -P rawprinter -v socket://11.12.13.14:9100 -E

    -sets up a queue named "rawprinter", connected via the "socket" -protocol (a.k.a. "HP JetDirect") to the device at IP address +sets up a queue named "rawprinter", connected via the "socket" +protocol (a.k.a. "HP JetDirect") to the device at IP address 11.12.1.3.14, using port 9100. (If you had added a PPD with -P /path/to/PPD to this command line, you would -have installed a "normal" printqueue. +have installed a "normal" printqueue.

    -CUPS will automatically treat each job sent to a queue as a "raw" one, +CUPS will automatically treat each job sent to a queue as a "raw" one, 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 @@ -9189,56 +8844,50 @@ you will probably have experienced the fact that printjobs originating from Windows clients were not printed. You may have found an error message in your CUPS logs like: 

    -
  Unable to convert file 0 to printable format for job
-

    -To enable the printing of "application/octet-stream" files, edit +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) which 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
-
 
    
 This line (with no specific auto-typing rule set) makes all files
 not otherwise auto-typed a member of application/octet-stream. In
 /etc/cups/mime.convs, have this
 line: 
 
    -
  application/octet-stream   application/vnd.cups-raw   0   -
-
-
    
+

    This line tells CUPS to use the Null Filter -(denoted as "-", doing... nothing at all) on +(denoted as "-", doing... nothing at all) on application/octet-stream, and tag the result as application/vnd.cups-raw. This last one is always a green light to the CUPS scheduler to now hand the file over -to the "backend" connecting to the printer and sending it over. +to the "backend" connecting to the printer and sending it over.

    Note

    Editing the mime.convs and the mime.types file does not -enforce "raw" printing, it only +enforce "raw" printing, it only allows it.

    Background.  CUPS being 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 Denial of Service attack on your printer(s), causing at least the loss -of a lot of paper and ink...) "Unknown" data are regarded by CUPS +of a lot of paper and ink...) "Unknown" data are regarded by CUPS as MIME type application/octet-stream. While you -can send data "raw", the MIME type for these must +can send data "raw", the MIME type for these must be one that is known to CUPS and an allowed one. The file -/etc/cups/mime.types defines the "rules" how CUPS +/etc/cups/mime.types defines the "rules" 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 (PPDs) for non-PS Printers

    +

    PostScript Printer Descriptions (PPDs) for non-PS 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 jobfile. CUPS has extended this @@ -9251,18 +8900,16 @@ printers the Ghostscript RIP runs on the host computer.

    PPDs for a non-PS 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
-
 
    
 It is the last piece in the CUPS filtering puzzle. This line tells the
-CUPS daemon to use as a last filter "rastertoprinter".  This filter
-should be served as input an "application/vnd.cups-raster" MIME type
+CUPS daemon to use as a last filter "rastertoprinter".  This filter
+should be served as input an "application/vnd.cups-raster" MIME type
 file. Therefore CUPS should auto-construct 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 this
-the last filter has done its work ("rastertoprinter" is a Gimp-Print
+taken as input to the specified "rastertoprinter" filter. After this
+the last filter has done its work ("rastertoprinter" is a Gimp-Print
 filter), the file should go to the backend, which sends it to the
 output device.
 
    
@@ -9270,34 +8917,22 @@ CUPS by default ships only a few generic PPDs, but they are good for
 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):
-
    deskjet.ppd
    older HP inkjet printers and compatible
-
    deskjet2.ppd
    newer HP inkjet printers and compatible
-
    dymo.ppd
    label printers
-
    epson9.ppd
    Epson 24pin impact printers and compatible
-
    epson24.ppd
    Epson 24pin impact printers and compatible
-
    okidata9.ppd
    Okidata 9pin impact printers and compatible
-
    okidat24.ppd
    Okidata 24pin impact printers and compatible
-
    stcolor.ppd
    older Epson Stylus Color printers
-
    stcolor2.ppd
    newer Epson Stylus Color printers
-
    stphoto.ppd
    older Epson Stylus Photo printers
-
    stphoto2.ppd
    newer Epson Stylus Photo printers
-
    laserjet.ppd
    all PCL printers. Further below is a discussion
-of several other driver/PPD-packages suitable fur use with CUPS.
-

    Difference between cupsomatic/foomatic-rip and -native CUPS printing

    +

    Table 19.1. PPD's 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 24pin impact printers and compatible
    epson24.ppdEpson 24pin impact printers and compatible
    okidata9.ppdOkidata 9pin impact printers and compatible
    okidat24.ppdOkidata 24pin 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. Further below is a discussion of several other driver/PPD-packages suitable for use with CUPS.

    Difference between cupsomatic/foomatic-rip and +native CUPS printing

    Native CUPS rasterization works in two steps.

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

    • -Second comes the "rasterdriver" step. It uses various +Second comes the "rasterdriver" step. It uses various device-specific filters; there are several vendors who provide good quality filters for this step, some are Free Software, some are Shareware/Non-Free, some are proprietary.

    Often this produces better quality (and has several more advantages) than other methods.

    -

    Figure 19.10. cupsomatic/foomatic processing versus Native CUPS

    cupsomatic/foomatic processing versus Native CUPS

    +

    Figure 19.10. cupsomatic/foomatic processing versus Native CUPS

    cupsomatic/foomatic processing versus Native CUPS

    One other method is the cupsomatic/foomatic-rip way. Note that cupsomatic is not made by the CUPS @@ -9311,6 +8946,8 @@ other (non-CUPS) spoolers. An upgrade to foomatic-rip is strongly advised, especially if you are upgrading to a recent version of CUPS too.

    + + Both the cupsomatic (old) and the foomatic-rip (new) methods from Linuxprinting.org use the traditional Ghostscript print file processing, doing everything in a single step. It therefore relies on @@ -9323,22 +8960,22 @@ 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 printfile after the +cupsomatic "kidnaps" the printfile after the application/vnd.cups-postscript stage and deviates it through the CUPS-external, system wide Ghostscript -installation: Therefore the printfile bypasses the "pstoraster" filter +installation: Therefore the printfile bypasses the "pstoraster" filter (and thus also bypasses the CUPS-raster-drivers -"rastertosomething"). After Ghostscript finished its rasterization, +"rastertosomething"). After Ghostscript finished its rasterization, cupsomatic hands the rendered file directly to the CUPS backend. The flowchart above 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 a HP JetDirect-connected PostScript printer, but you want to print the pages 3-5, 7, 11-13 -only, and you want to print them "2-up" and "duplex": +only, and you want to print them "2-up" and "duplex":

    • your print options (page selection as required, 2-up, duplex) are passed to CUPS on the commandline;

    • the (complete) PDF file is sent to CUPS and autotyped as application/pdf;

    • the file therefore first must pass the @@ -9346,16 +8983,14 @@ duplex) are passed to CUPS on the commandline;

    • the (complete) PDF MIME type application/postscript (a preview here would still show all pages of the original PDF);

    • the file then passes the pstops filter which applies the commandline options: it selects the pages -2-5, 7 and 11-13, creates and imposed layout "2 pages on 1 sheet" and -inserts the correct "duplex" command (as is defined in the printer's +2-5, 7 and 11-13, creates and imposed layout "2 pages on 1 sheet" and +inserts the correct "duplex" command (as is defined in the printer's PPD) into the new PostScript file; the file now is of PostScript MIME type application/vnd.cups-postscript;

    • the file goes to the socket backend, which transfers the job to the printers.

    -The resulting filter chain therefore is: -

    -pdftops --> pstops --> socket
-

    + The resulting filter chain therefore is as drawn in the image below. +

    Figure 19.11. PDF to socket chain

    PDF to socket chain

    Assume your 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 @@ -9365,10 +9000,10 @@ duplex) are passed to CUPS on the commandline;

  • the (complete) PDF application/pdf;

  • the file therefore first must pass the pdftops pre-filter, 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 which applies +would still show all pages of the original PDF);

  • the file then passes the "pstops" filter which applies the commandline options: it selects the pages 2-5, 7 and 11-13, -creates and imposed layout "2 pages on 1 sheet" and inserts the -correct "duplex" command... (OOoops -- this printer and his PPD +creates and imposed layout "2 pages on 1 sheet" and inserts the +correct "duplex" command... (OOoops -- this printer and his PPD don't support duplex printing at all -- this option will be ignored then) into the new PostScript file; the file now is of PostScript MIME type @@ -9379,46 +9014,44 @@ does its work (as is indicated in the printer's PPD), creating the printer-specific raster data and embedding any user-selected print-options into the print data stream;

  • the file goes to the usb backend, which transfers the job to the printers.

    • -The resulting filter chain therefore is: -

    -pdftops --> pstops --> pstoraster --> rastertoepson --> usb
-

    Sources of CUPS drivers / PPDs

    + The resulting filter chain therefore is as drawn in the image below. +

    Figure 19.12. PDF to USB chain

    PDF to USB chain

    Sources of CUPS drivers / PPDs

    On the internet you can find now many thousand CUPS-PPD files (with their companion filters), in many national languages, supporting more than 1000 non-PostScript models. -

    • ESP -PrintPro (http://wwwl.easysw.com/printpro/) (commercial, +

      • ESP +PrintPro (commercial, non-Free) is packaged with more than 3000 PPDs, ready for -successful use "out of the box" on Linux, Mac OS X, IBM-AIX, -HP-UX, Sun-Solaris, SGI-IRIX, Compaq Tru64, Digital Unix and some +successful use "out of the box" on Linux, Mac OS X, IBM-AIX, +HP-UX, Sun-Solaris, SGI-IRIX, Compaq Tru64, Digital UNIX and some more commercial Unices (it is written by the CUPS developers themselves and its sales help finance the further development of CUPS, as they feed their creators).

      • the Gimp-Print-Project -(http://gimp-print.sourceforge.net/) (GPL, Free Software) + (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;

      • TurboPrint -(http://www.turboprint.com/) (Shareware, non-Free) supports + (Shareware, non-Free) supports roughly the same amount of printers in excellent quality;

      • OMNI -(http://www-124.ibm.com/developerworks/oss/linux/projects/omni/) + (LPGL, Free) is a package made by IBM, now containing support for more than 400 printers, stemming from the inheritance of IBM OS/2 Know-How ported over to Linux (CUPS support is in a Beta-stage at present);

      • HPIJS -(http://hpinkjet.sourceforge.net/) (BSD-style licenses, Free) + (BSD-style licenses, Free) supports around 150 of HP's own printers and is also providing excellent print quality now (currently available only via the Foomatic path);

      • Foomatic/cupsomatic -(http://www.linuxprinting.org/) (LPGL, Free) from + (LPGL, Free) from Linuxprinting.org are providing PPDs for practically every Ghostscript filter known to the world (including Omni, Gimp-Print and HPIJS).

      Note

      The cupsomatic/Foomatic trick from Linuxprinting.org works differently from the other drivers. This is explained elsewhere in this document. -

    Printing with Interface Scripts

    -CUPS also supports the usage of "interface scripts" as known from +

    Printing with Interface Scripts

    +CUPS also supports the usage 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 scripts are specific to printer models. They have a similar role as @@ -9430,61 +9063,60 @@ realm. On HP-UX platforms they are more often used. You can use any working interface script on CUPS too. Just install the printer with the -i option: 

    -
- lpadmin -p pclprinter -v socket://11.12.13.14:9100 -i /path/to/interface-script
-
+root# lpadmin -p pclprinter -v socket://11.12.13.14:9100 \
+  -i /path/to/interface-script

    -Interface scripts might be the "unknown animal" to many. However, +Interface scripts might be the "unknown animal" to many. However, with CUPS they provide the most easy way to plug in your own custom-written filtering script or program into one specific print queue (some information about the traditional usage of interface scripts is to be 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 +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 -

    • execute the driver locally and render the GDI output +

      • execute the driver locally and render the GDI output (EMF) into the printer specific format on their own, or

      • send the GDI output (EMF) to the server, where the driver is executed to render the printer specific output.

      Both print paths are shown in the flowcharts below. -

    Driver Execution on the Client

    -In the first case the print server must spool the file as "raw", +

    Driver Execution on the Client

    +In the first case the print server must spool the file as "raw", meaning it shouldn't touch the jobfile and try to convert it in any -way. This is what traditional Unix-based print server can do too; and +way. This is what traditional UNIX-based print server can do too; and at a better performance and more reliably than NT print server. This is what most Samba administrators probably are familiar with. One -advantage of this setup is that this "spooling-only" print server may -be used even if no driver(s) for Unix are available it is sufficient +advantage of this setup is that this "spooling-only" print server may +be used even if no driver(s) for UNIX are available it is sufficient to have the Windows client drivers available and installed on the clients.

    -

    Figure 19.11. Print Driver execution on the Client

    Print Driver execution on the Client

    -

    Driver Execution on the Server

    +

    Figure 19.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 clients 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 +the printer-specific language. It is not possible for UNIX to do the same. Currently there is no program or method to convert a Windows -client's GDI output on a Unix server into something a printer could +client's GDI output on a UNIX server into something a printer could understand.

    -

    Figure 19.12. Print Driver execution on the Server

    Print Driver execution on the Server

    +

    Figure 19.14. Print Driver execution on the Server

    Print Driver execution on the Server

    However, there is something similar possible with CUPS. Read on... -

    Network Printing (Windows clients -- UNIX/Samba Print +

    Network Printing (Windows clients -- UNIX/Samba Print Servers)

    Since UNIX print servers cannot execute the Win32 program code on their platform, the picture is somewhat different. However, this doesn't limit your options all that much. In the contrary, you may have a way here to implement printing features which 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 powerful features for the benefit of your Windows network printing clients: @@ -9493,15 +9125,14 @@ server.

  • Let the CUPS server render the PostScript into device specific raster format.

    • This requires the clients to use a PostScript driver (even if the printer is a non-PostScript model. It also requires that you have a -"driver" on the CUPS server. +"driver" on the CUPS server.

    Firstly, to enable CUPS based printing through Samba the -following options should be set in your smb.conf file [globals] +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 +(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 it's application program interface (API) - as long as Samba has been compiled with CUPS library (libcups) @@ -9510,12 +9141,12 @@ other print commands are set up, then printing will use the System V AT&T command set, with the -oraw option automatically passing through (if you want your own defined print commands to work with a Samba that has CUPS support compiled in, -simply use printing = sysv). +simply use printing = sysv).

    -

    Figure 19.13. Printing via CUPS/samba server

    Printing via CUPS/samba server

    -

    Samba receiving Jobfiles and passing them to CUPS

    +

    Figure 19.15. Printing via CUPS/samba server

    Printing via CUPS/samba server

    +

    Samba receiving Jobfiles and passing them to CUPS

    Samba must use its own spool directory (it is set -by a line similar to path = /var/spool/samba, +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 @@ -9525,14 +9156,14 @@ directive, in a line that defaults to RequestRoot /var/spool/cups). CUPS checks the access rights of its spool dir and resets it to healthy values with every re-start. We have seen quite some people who had used a common spooling space for Samba -and CUPS, and were struggling for weeks with this "problem". +and CUPS, and were struggling for weeks with this "problem".

    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 they run on different machines, you +allow "localhost" to print. If they run on different machines, you need to make sure the Samba host gets access to printing on CUPS. -

    Network PostScript RIP: CUPS Filters on Server -- clients use -PostScript Driver with CUPS-PPDs

    +

    Network PostScript RIP: CUPS Filters on Server -- clients use +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 (PostScript Printer Descriptions) are always a component of @@ -9540,7 +9171,7 @@ PostScript printer drivers on MS Windows or Apple Mac OS systems. They are ASCII files containing user-selectable print options, mapped to appropriate PostScript, PCL or PJL commands for the target printer. Printer driver GUI dialogs translate these options -"on-the-fly" into buttons and drop-down lists for the user to select. +"on-the-fly" into buttons and drop-down lists for the user to select.

    CUPS can load, without any conversions, the PPD file from any Windows (NT is recommended) PostScript driver and handle the options. There is @@ -9551,8 +9182,8 @@ or see if you have lphelp on your system). There are also some different GUI frontends 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

    -CUPS doesn't limit itself to "real" PostScript printers in its usage +

    PPDs for non-PS Printers on UNIX

    +CUPS doesn't limit itself to "real" PostScript printers in its usage 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. @@ -9568,10 +9199,10 @@ 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 WindowsNT/2K/XP"; you can also use the Adobe one, with +"core" PostScript driver (now recommended is the "CUPS PostScript +Driver for WindowsNT/2K/XP"; you can also use the Adobe one, with limitations). This feature enables CUPS to do a few tricks no other spooler can do:

    • act as a networked PostScript RIP (Raster Image @@ -9579,35 +9210,35 @@ Processor), handling printfiles from all client platforms in a uniform way;

    • act as a central accounting and billing server, since all files are passed through the pstops filter and are therefore logged in the CUPS page_log file. -NOTE: this can not happen with "raw" print jobs, +NOTE: this can not happen with "raw" print jobs, which always remain unfiltered per definition;

    • enable clients to consolidate on a single PostScript driver, even for many different target printers.

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

    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 need often 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

    -The reason is that in Win NT printer drivers run in "Kernel -Mode", this introduces a high risk for the stability of the system +The reason is that in Win NT printer drivers run in "Kernel +Mode", this introduces 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 there! Especially notorious is the example of the PCL printer driver that had an additional sound module running, to notify users via soundcard of their finished jobs. Do I -need to say that this one was also reliably causing "Blue Screens -of Death" on a regular basis? +need to say that this one was also reliably causing "Blue Screens +of Death" on a regular basis?

    PostScript drivers generally are very well tested. They are not known to cause any problems, even though they run in Kernel Mode too. This might be because there have so far only been 2 different PostScript -drivers the ones from Adobe and the one from Microsoft. Both are +drivers: the ones from Adobe and the one from Microsoft. Both are very well tested and are as stable as you ever can imagine on Windows. The CUPS driver is derived from the Microsoft one. -

    Workarounds impose Heavy Limitations

    +

    Workarounds impose Heavy Limitations

    In many cases, in an attempt to work around this problem, site administrators have resorted to restrict the allowed drivers installed on their WTS to one generic PCL- and one PostScript driver. This @@ -9615,7 +9246,7 @@ however restricts the clients in the amount of printer options available for them; 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 3 different PostScript @@ -9625,14 +9256,14 @@ used with many different PPDs). The clients will be able to (again) chose paper trays, duplex printing and other settings. However, there is a certain price for this too: a CUPS 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, +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 -Mode

    +

    PostScript Drivers with no major problems -- even in Kernel +Mode

    More recent printer drivers on W2K and XP don't run in Kernel mode (unlike Win NT) any more. 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" +is which as the drivers in subdirectory "2" of "W32X86" are "old" ones). As was said before, the Adobe as well as the Microsoft PostScript drivers are not known to cause any stability problems. The CUPS driver is derived from the Microsoft one. There is a simple @@ -9642,16 +9273,16 @@ includes the source code of the Microsoft driver, and licensees of Visual Studio are allowed to use and modify it for their own driver development efforts. This is what the CUPS people have done. The license doesn't allow them to publish the whole of the source code. -However, they have released the "diff" under the GPL, and if you are -owner of an "MS DDK for Win NT", you can check the driver yourself. -

    Setting up CUPS for driver Download

    +However, they have released the "diff" under the GPL, and if you are +owner of an "MS DDK for Win NT", you can check the driver yourself. +

    Setting up 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" +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 the previous chapter. In reality, this is a pure Samba business, and only relates to the Samba/Win 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 @@ -9676,82 +9307,49 @@ job-billing)

    However, currently only Windows NT, 2000, and XP are supported by the CUPS drivers. You will need to get the respective part of Adobe driver too 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 following settings in 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           # setting depends on your requirements
-         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 Package of "PostScript Driver for WinNT/2k/XP"

    -CUPS users may get the exactly same packages fromhttp://www.cups.org/software.html. +

    Example 19.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 Package of "PostScript Driver for WinNT/2k/XP"

    +CUPS users may get the exactly same packages from http://www.cups.org/software.html. It is a separate package from the CUPS base software files, tagged as -CUPS 1.1.x Windows NT/2k/XP Printer Driver for SAMBA +CUPS 1.1.x Windows NT/2k/XP Printer Driver for Samba (tar.gz, 192k). The filename to download is cups-samba-1.1.x.tar.gz. Upon untar-/unzip-ing, it will reveal these files: 

    -
-# tar xvzf cups-samba-1.1.19.tar.gz 
-
-   cups-samba.install
-   cups-samba.license
-   cups-samba.readme
-   cups-samba.remove
-   cups-samba.ss
-
-

    +root# tar xvzf cups-samba-1.1.19.tar.gz +cups-samba.install +cups-samba.license +cups-samba.readme +cups-samba.remove +cups-samba.ss +

    + + These have been packaged with the ESP meta packager software -"EPM". The *.install and +"EPM". The *.install and *.remove files are simple shell scripts, which untars the *.ss (the *.ss is -nothing else but a tar-archive, which can be untar-ed by "tar" +nothing else but a tar-archive, which can be untar-ed by "tar" too). Then it puts the content into /usr/share/cups/drivers/. This content includes 3 files: 

    -
-# tar tv cups-samba.ss
-
-    cupsdrvr.dll
-    cupsui.dll
-    cups.hlp  
-
+root# tar tv cups-samba.ss
+cupsdrvr.dll
+cupsui.dll
+cups.hlp

    The cups-samba.install shell scripts is easy to handle: 

    -
-# ./cups-samba.install
-
-   [....]
-   Installing software...
-   Updating file permissions...
-   Running post-install commands...
-   Installation is complete.        
-
+root# ./cups-samba.install
+[....]
+Installing software...
+Updating file permissions...
+Running post-install commands...
+Installation is complete.

    The script should automatically put the driver files into the /usr/share/cups/drivers/ directory. @@ -9764,54 +9362,37 @@ copy/move the file (after running the ./cups-samba.install script) manually to the right place. 

    -
-   cp /usr/share/drivers/cups.hlp /usr/share/cups/drivers/
-
-

    +root# cp /usr/share/drivers/cups.hlp /usr/share/cups/drivers/ +

    This new CUPS PostScript driver is currently binary-only, but free of charge. No complete source code is provided (yet). The reason is this: it has been developed with the help of the Microsoft Driver Developer Kit (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 of +the "diff" in source code under the GPL, so anybody with a license of Visual Studio and a DDK will be able to compile for him/herself. -

    Recognize the different Driver Files

    -The CUPS drivers don't support the "older" Windows 95/98/ME, but only +

    Recognize the different Driver Files

    +The CUPS drivers don't 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
-
-

    +

    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 the Windows NT/2000/XP clients. The set of files is different for 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
    
 
- [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

    +

    Note

    If both, the Adobe driver files and the CUPS driver files for the support of WinNT/2k/XP are present in , the Adobe ones will be ignored and the CUPS ones will be used. If you prefer -- for whatever reason -- to use Adobe-only drivers, move away the 3 CUPS driver files. The Win95/98/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 website as single files and the self-extracting and/or self-installing Windows-exe is @@ -9824,13 +9405,13 @@ Generic PostScript printer. After this, the client's where you can get them with smbclient from the CUPS host. A more detailed description about this is in the next (the CUPS printing) chapter. -

    ESP Print Pro Package of "PostScript Driver for -WinNT/2k/XP"

    -Users of the ESP Print Pro software are able to install their "Samba -Drivers" package for this purpose with no problem. Retrieve the driver +

    ESP Print Pro Package of "PostScript Driver for +WinNT/2k/XP"

    +Users of the ESP Print Pro software are able to install their "Samba +Drivers" package for this purpose with no problem. Retrieve the driver files from the normal download area of the ESP Print Pro software -athttp://www.easysw.com/software.html. -You need to locate the link labelled "SAMBA" amongst the +at http://www.easysw.com/software.html. +You need to locate the link labelled "SAMBA" amongst the Download Printer Drivers for ESP Print Pro 4.x area and download the package. Once installed, you can prepare any driver by simply highlighting the printer in the Printer Manager GUI @@ -9840,7 +9421,7 @@ driver files; i.e. mainly setup the [print$] share, etc. 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 @@ -9848,9 +9429,10 @@ ready to be put into Samba's [print$] share (w /etc/samba/drivers/ and contains a subdir tree with WIN40 and W32X86 branches): You do this by running -"cupsaddsmb" (see also man cupsaddsmb for +"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 @@ -9870,62 +9452,67 @@ It is not harmful if you still have the ADOBE*.* driver files from previous installations in the /usr/share/cups/drivers/ directory. The new cupsaddsmb (from 1.1.16) will -automatically prefer "its own" drivers if it finds both. +automatically prefer "its own" drivers if it finds both.

  • + Should your Win 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/2k/XP will fail at first. You need to wipe the old driver from the clients -first. It is not enough to "delete" the printer, as the driver files +first. It is not enough to "delete" the printer, as the driver files will still be kept by the clients and re-used if you try to re-install the printer. To really get rid of the Adobe driver files on the -clients, open the "Printers" folder (possibly via Start ---> Settings --> Control Panel --> Printers), +clients, open the "Printers" folder (possibly via Start, Settings, Control Panel, Printers), right-click onto the folder background and select Server Properties. When the new dialog opens, select the Drivers tab. On the list select the driver you want to delete and click on the Delete button. This will only work if there is not one single printer left -which uses that particular driver. You need to "delete" all printers -using this driver in the "Printers" folder first. You will need +which uses that particular driver. You need to "delete" all printers +using this driver in the "Printers" folder first. You will need Administrator privileges to do this.

  • + 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 elsewhere in the "Samba HOWTO Collection": either change -a driver for an existing printer by running the "Printer Properties" +as described in the printing chapter: either change +a driver for an existing printer by running the "Printer Properties" dialog, or use rpcclient with the setdriver sub-command.

    • -

    What are the Benefits of using the "CUPS PostScript Driver for -Windows NT/2k/XP" as compared to the Adobe Driver?

    +

    Benefits of using "CUPS PostScript Driver for +Windows NT/2k/XP" instead of Adobe Driver

    You are interested in a comparison between the CUPS and the Adobe PostScript drivers? For our purposes these are the most important items which weigh in favor of the CUPS ones:

    • no hassle with the Adobe EULA

    • no hassle with the question “Where do I -get the ADOBE*.* driver files from?”

    • the Adobe drivers (on request of the printer PPD +get the ADOBE*.* driver files from?”

    • + + 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 printfile starts with <1B >%-12345X or <escape>%-12345X instead of %!PS). This leads to the CUPS daemon auto-typing the incoming file as a print-ready file, -not initiating a pass through the "pstops" filter (to speak more +not initiating a pass through the "pstops" filter (to speak more technically, it is not 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 "mis-configure" the +of "1" is logged in a standard setup)

    • the Adobe driver has more options to "mis-configure" 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 will be guaranteed to be auto-typed always as generic MIME type application/postscript, -thusly passing through the CUPS "pstops" filter and logging the +thusly 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 Win NT/2k/XP clients. Such @@ -9943,7 +9530,7 @@ not disturb any other applications as 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/2K/XP to be released soon (probably alongside the first Beta release for CUPS -1.2).

    Run "cupsaddsmb" (quiet Mode)

    +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 @@ -9952,125 +9539,112 @@ associated with this printer is copied from Windows client installations via Point'n'Print. Before we can run the command successfully, we need to be sure that we can authenticate towards Samba. If you have a small network you are probably using user -level security (security = user). Probably your -root has already a Samba account. Otherwise, create it now, using -smbpasswd: -

    -
- #  smbpasswd -a root 
- New SMB password: [type in password 'secret']
- Retype new SMB password: [type in password 'secret']
-
-

    +level security (security = user). +

    Here is an example of a successfully run cupsaddsmb command. 

    -
- #  cupsaddsmb -U root infotec_IS2027
- Password for root required to access localhost via SAMBA: [type in password 'secret']
-
+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 +-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 +-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:

    Warning

    You will see the root password for the Samba account printed on -screen. If you use remote access, the password will go over the wire -unencrypted! -

    -
-  # cupsaddsmb -U root -v infotec_2105
-  Password for root required to access localhost via SAMBA:
-  Running command: smbclient //localhost/print\$ -N -U'root%secret' -c 'mkdir W32X86;put   \
-                   /var/spool/cups/tmp/3e98bf2d333b5 W32X86/infotec_2105.ppd;put           \
-                   /usr/share/cups/drivers/cupsdrvr.dll W32X86/cupsdrvr.dll;put            \
-                   /usr/share/cups/drivers/cupsui.dll W32X86/cupsui.dll;put                \
-                   /usr/share/cups/drivers/cups.hlp W32X86/cups.hlp'
-  added interface ip=10.160.51.60 bcast=10.160.51.255 nmask=255.255.252.0
-  Domain=[CUPS-PRINT] OS=[Unix] Server=[Samba 2.2.7a]
-  NT_STATUS_OBJECT_NAME_COLLISION making remote directory \W32X86
-  putting file /var/spool/cups/tmp/3e98bf2d333b5 as \W32X86/infotec_2105.ppd (2328.8 kb/s) \
-               (average 2328.8 kb/s)
-  putting file /usr/share/cups/drivers/cupsdrvr.dll as \W32X86/cupsdrvr.dll (9374.3 kb/s)  \
-               (average 5206.6 kb/s)
-  putting file /usr/share/cups/drivers/cupsui.dll as \W32X86/cupsui.dll (8107.2 kb/s)      \
-               (average 5984.1 kb/s)
-  putting file /usr/share/cups/drivers/cups.hlp as \W32X86/cups.hlp (3475.0 kb/s)          \
-               (average 5884.7 kb/s)
+screen. 
+
    +root# cupsaddsmb -U root -v infotec_2105
+Password for root required to access localhost via GANDALF:
+Running command: smbclient //localhost/print\$ -N -U'root%secret' \
+    -c 'mkdir W32X86; \
+    put /var/spool/cups/tmp/3e98bf2d333b5 W32X86/infotec_2105.ppd; \
+	put /usr/share/cups/drivers/cupsdrvr.dll W32X86/cupsdrvr.dll; \
+    put /usr/share/cups/drivers/cupsui.dll W32X86/cupsui.dll; \
+    put /usr/share/cups/drivers/cups.hlp W32X86/cups.hlp'
+added interface ip=10.160.51.60 bcast=10.160.51.255 nmask=255.255.252.0
+Domain=[CUPS-PRINT] OS=[UNIX] Server=[Samba 2.2.7a]
+NT_STATUS_OBJECT_NAME_COLLISION making remote directory \W32X86
+putting file /var/spool/cups/tmp/3e98bf2d333b5 as \W32X86/infotec_2105.ppd
+putting file /usr/share/cups/drivers/cupsdrvr.dll as \W32X86/cupsdrvr.dll
+putting file /usr/share/cups/drivers/cupsui.dll as \W32X86/cupsui.dll
+putting file /usr/share/cups/drivers/cups.hlp as \W32X86/cups.hlp
   
-  Running command: rpcclient localhost -N -U'root%secret' -c 'adddriver "Windows NT x86"   \
-                   "infotec_2105:cupsdrvr.dll:infotec_2105.ppd:cupsui.dll:cups.hlp:NULL:   \
-                   RAW:NULL"'
-  cmd = adddriver "Windows NT x86" "infotec_2105:cupsdrvr.dll:infotec_2105.ppd:cupsui.dll: \
-                   cups.hlp:NULL:RAW:NULL"
-  Printer Driver infotec_2105 successfully installed.
+Running command: rpcclient localhost -N -U'root%secret' 
+   -c 'adddriver "Windows NT x86"   \
+   "infotec_2105:cupsdrvr.dll:infotec_2105.ppd:cupsui.dll:cups.hlp:NULL:   \
+    RAW:NULL"'
+cmd = adddriver "Windows NT x86" \
+    "infotec_2105:cupsdrvr.dll:infotec_2105.ppd:cupsui.dll:cups.hlp:NULL:RAW:NULL"
+Printer Driver infotec_2105 successfully installed.
   
-  Running command: smbclient //localhost/print\$ -N -U'root%secret' -c 'mkdir WIN40;put    \
-                   /var/spool/cups/tmp/3e98bf2d333b5 WIN40/infotec_2105.PPD; put           \
-                   /usr/share/cups/drivers/ADFONTS.MFM WIN40/ADFONTS.MFM;put               \
-                   /usr/share/cups/drivers/ADOBEPS4.DRV WIN40/ADOBEPS4.DRV;put             \
-                   /usr/share/cups/drivers/ADOBEPS4.HLP WIN40/ADOBEPS4.HLP;put             \
-                   /usr/share/cups/drivers/DEFPRTR2.PPD WIN40/DEFPRTR2.PPD;put             \
-                   /usr/share/cups/drivers/ICONLIB.DLL
-  WIN40/ICONLIB.DLL;put /usr/share/cups/drivers/PSMON.DLL WIN40/PSMON.DLL;'
+Running command: smbclient //localhost/print\$ -N -U'root%secret' \
+-c 'mkdir WIN40; \
+    put /var/spool/cups/tmp/3e98bf2d333b5 WIN40/infotec_2105.PPD; \
+	put /usr/share/cups/drivers/ADFONTS.MFM WIN40/ADFONTS.MFM;   \
+    put /usr/share/cups/drivers/ADOBEPS4.DRV WIN40/ADOBEPS4.DRV; \
+    put /usr/share/cups/drivers/ADOBEPS4.HLP WIN40/ADOBEPS4.HLP; \
+    put /usr/share/cups/drivers/DEFPRTR2.PPD WIN40/DEFPRTR2.PPD; \
+	put /usr/share/cups/drivers/ICONLIB.DLL WIN40/ICONLIB.DLL; \
+	put /usr/share/cups/drivers/PSMON.DLL WIN40/PSMON.DLL;'
   added interface ip=10.160.51.60 bcast=10.160.51.255 nmask=255.255.252.0
-  Domain=[CUPS-PRINT] OS=[Unix] Server=[Samba 2.2.7a]
+  Domain=[CUPS-PRINT] OS=[UNIX] Server=[Samba 2.2.7a]
   NT_STATUS_OBJECT_NAME_COLLISION making remote directory \WIN40
-  putting file /var/spool/cups/tmp/3e98bf2d333b5 as \WIN40/infotec_2105.PPD (2328.8 kb/s)  \
-               (average 2328.8 kb/s)
-  putting file /usr/share/cups/drivers/ADFONTS.MFM as \WIN40/ADFONTS.MFM (9368.0 kb/s)     \
-               (average 6469.6 kb/s)
-  putting file /usr/share/cups/drivers/ADOBEPS4.DRV as \WIN40/ADOBEPS4.DRV (9958.2 kb/s)   \
-               (average 8404.3 kb/s)
-  putting file /usr/share/cups/drivers/ADOBEPS4.HLP as \WIN40/ADOBEPS4.HLP (8341.5 kb/s)   \
-               (average 8398.6 kb/s)
-  putting file /usr/share/cups/drivers/DEFPRTR2.PPD as \WIN40/DEFPRTR2.PPD (2195.9 kb/s)   \
-               (average 8254.3 kb/s)
-  putting file /usr/share/cups/drivers/ICONLIB.DLL as \WIN40/ICONLIB.DLL (8239.9 kb/s)     \
-               (average 8253.6 kb/s)
-  putting file /usr/share/cups/drivers/PSMON.DLL as \WIN40/PSMON.DLL (6222.2 kb/s)         \
-               (average 8188.5 kb/s)
+  putting file /var/spool/cups/tmp/3e98bf2d333b5 as \WIN40/infotec_2105.PPD
+  putting file /usr/share/cups/drivers/ADFONTS.MFM as \WIN40/ADFONTS.MFM
+  putting file /usr/share/cups/drivers/ADOBEPS4.DRV as \WIN40/ADOBEPS4.DRV
+  putting file /usr/share/cups/drivers/ADOBEPS4.HLP as \WIN40/ADOBEPS4.HLP
+  putting file /usr/share/cups/drivers/DEFPRTR2.PPD as \WIN40/DEFPRTR2.PPD
+  putting file /usr/share/cups/drivers/ICONLIB.DLL as \WIN40/ICONLIB.DLL
+  putting file /usr/share/cups/drivers/PSMON.DLL as \WIN40/PSMON.DLL
   
-  Running command: rpcclient localhost -N -U'root%secret' -c 'adddriver "Windows 4.0"      \
-                   "infotec_2105:ADOBEPS4.DRV:infotec_2105.PPD:NULL:ADOBEPS4.HLP:          \
-                   PSMON.DLL:RAW:ADOBEPS4.DRV,infotec_2105.PPD,ADOBEPS4.HLP,PSMON.DLL,     \
-                   ADFONTS.MFM,DEFPRTR2.PPD,ICONLIB.DLL"'
-  cmd = adddriver "Windows 4.0" "infotec_2105:ADOBEPS4.DRV:infotec_2105.PPD:NULL:          \
-                   ADOBEPS4.HLP:PSMON.DLL:RAW:ADOBEPS4.DRV,infotec_2105.PPD,ADOBEPS4.HLP,  \
-                   PSMON.DLL,ADFONTS.MFM,DEFPRTR2.PPD,ICONLIB.DLL"
+  Running command: rpcclient localhost -N -U'root%secret' \
+   -c 'adddriver "Windows 4.0"      \
+   "infotec_2105:ADOBEPS4.DRV:infotec_2105.PPD:NULL:ADOBEPS4.HLP: \
+   PSMON.DLL:RAW:ADOBEPS4.DRV,infotec_2105.PPD,ADOBEPS4.HLP,PSMON.DLL, \
+    ADFONTS.MFM,DEFPRTR2.PPD,ICONLIB.DLL"'
+  cmd = adddriver "Windows 4.0" "infotec_2105:ADOBEPS4.DRV:infotec_2105.PPD:NULL:          \
+    ADOBEPS4.HLP:PSMON.DLL:RAW:ADOBEPS4.DRV,infotec_2105.PPD,ADOBEPS4.HLP,  \
+                   PSMON.DLL,ADFONTS.MFM,DEFPRTR2.PPD,ICONLIB.DLL"
   Printer Driver infotec_2105 successfully installed.
   
-  Running command: rpcclient localhost -N -U'root%secret'                                  \
-                             -c 'setdriver infotec_2105 infotec_2105'
+  Running command: rpcclient localhost -N -U'root%secret'  \
+   -c 'setdriver infotec_2105 infotec_2105'
   cmd = setdriver infotec_2105 infotec_2105
   Successfully set infotec_2105 to driver infotec_2105.

    -If you look closely, you'll discover your root password was transfered +If you look closely, you'll discover your root password was transferred unencrypted over the wire, so beware! Also, if you look further her, you'll discover error messages like NT_STATUS_OBJECT_NAME_COLLISION in between. They occur, because the directories WIN40 and W32X86 already existed in the [print$] driver download share (from a previous driver installation). They are harmless here. -

    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 +

      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 Win95/98/ME) and W32X86/ (for WinNT/2k/XP) sub - directories;

      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.

      + directories;

    2. + + connect via rpcclient to the Samba server and +execute the "adddriver" command with the correct +parameters;

    3. + + connect via rpcclient to the Samba server a second +time and execute the "setdriver" command.

    Note, that 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 @@ -10078,10 +9652,8 @@ good idea try it and see more clearly what is going on (though in real life most people will have their CUPS and Samba servers run on the same host): 

    -
- # cupsaddsmb -H sambaserver -h cupsserver -v printername
-
-

    How to recognize if cupsaddsm completed successfully

    +root# cupsaddsmb -H sambaserver -h cupsserver -v printername +

    How to recognize if cupsaddsmb completed successfully

    You must always check if the utility completed successfully in all fields. You need as a minimum these 3 messages amongst the output: @@ -10092,7 +9664,7 @@ installed. # (for the WIN40 == Win9x/ME architecture...)

  • Successfully set [printerXPZ] to driver [printerXYZ].

    • These messages probably not easily recognized in the general -output. If you run cupsaddsmb with the -a +output. If you run cupsaddsmb with the -a parameter (which tries to prepare all active CUPS printer drivers for download), you might miss if individual printers drivers had problems to install properly. Here a redirection of the @@ -10102,46 +9674,45 @@ It is impossible to see any diagnostic output if you don't run cupsaddsmb in verbose mode. Therefore we strongly recommend to not use the default quiet mode. It will hide any problems from you which might occur. -

    cupsaddsmb with a Samba PDC

    +

    cupsaddsmb with a Samba PDC

    You can't get the standard cupsaddsmb command to run on a Samba PDC? You are asked for the password credential all over again and again and the command just will not take off at all? Try one of these variations: 

    -
- # cupsaddsmb -U DOMAINNAME\\root -v printername
- # cupsaddsmb -H SAMBA-PDC -U DOMAINNAME\\root -v printername
- # cupsaddsmb -H SAMBA-PDC -U DOMAINNAME\\root -h cups-server -v printername
-
+root# cupsaddsmb -U MIDEARTH\\root -v printername
+root# cupsaddsmb -H SAURON -U MIDEARTH\\root -v printername
+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

    +"escape" the second one). +

    cupsaddsmb Flowchart

    Here is a chart about the procedures, commandflows and -dataflows of the "cupaddsmb" command. Note again: cupsaddsmb is -not intended to, and does not work with, "raw" queues! +dataflows of the "cupaddsmb" command. Note again: cupsaddsmb is +not intended to, and does not work with, "raw" queues!

    -

    Figure 19.14. cupsaddsmb flowchart

    cupsaddsmb flowchart

    -

    Installing the PostScript Driver on a Client

    +

    Figure 19.16. cupsaddsmb flowchart

    cupsaddsmb flowchart

    +

    Installing the PostScript Driver on a Client

    After cupsaddsmb 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 +via "Point'n'Print". From a Windows client, browse to the CUPS/Samba server; -

    • open the Printers +

      • open the Printers share of Samba in Network Neighbourhood;

      • 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 +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 +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 will appears in a \\SambaServer\PrinterName entry in the dropdown list of available printers.

      Note

      + cupsaddsmb will only reliably work with CUPS version 1.1.15 or higher and Samba from 2.2.4. If it doesn't work, or if the automatic printer driver download to the clients doesn't succeed, you can still manually @@ -10149,16 +9720,14 @@ install the CUPS printer PPD on top of the Adobe PostScript driver on clients. Then point the client's printer queue to the Samba printer share for a UNC type of connection: 

      -
-  net use lpt1: \\sambaserver\printershare /user:ntadmin
-
+C:\> net use lpt1: \\sambaserver\printershare /user:ntadmin

      should you desire to use the CUPS networked PostScript RIP -functions. (Note that user "ntadmin" needs to be a valid Samba user +functions. (Note that user "ntadmin" needs to be a valid Samba user with the required privileges to access the printershare) This would set up the printer connection in the traditional LanMan way (not using MS-RPC). -

    Avoiding critical PostScript Driver Settings on the +

    Avoiding critical PostScript Driver Settings on the Client

    Soooo: printing works, but there are still problems. Most jobs print well, some don't print at all. Some jobs have problems with fonts, @@ -10184,7 +9753,7 @@ get a printout at all) (Adobe)

  • Sometimes you can choose : 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 +Error Handler (Adobe)

    Installing PostScript Driver Files manually (using rpcclient)

    Of course you can run all the commands which are embedded into the cupsaddsmb convenience utility yourself, one by one, and hereby upload @@ -10192,10 +9761,19 @@ and prepare the driver files for future client downloads.

    1. prepare Samba (a CUPS printqueue 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 + [print$]

    5. + + run rpcclient adddriver +(for each client architecture you want to support):

    6. + + run rpcclient setdriver.

    -We are going to do this now. First, read the man page on "rpcclient" + + + + + +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 sub-commands. enumprinters, enumdrivers, enumports, @@ -10203,9 +9781,9 @@ sub-commands. enumprinters, the most interesting ones. rpcclient implements an important part of the MS-RPC protocol. You can use it to query (and command) a Win NT (or 2K/XP) PC too. MS-RPC is used by Windows clients, amongst other -things, to benefit from the "Point'n'Print" features. Samba can now +things, to benefit from the "Point'n'Print" features. Samba can now mimic this too. -

    A Check of the rpcclient man Page

    +

    A Check of the rpcclient man Page

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

    @@ -10225,9 +9803,9 @@ Help File Name:\ Language Monitor Name:\ Default Data Type:\ Comma Separated list of Files -

    Any empty fields should be enter as the string "NULL".

    Samba does not need to support the concept of Print Monitors +

    Any empty fields should be enter as the string "NULL".

    Samba does not need to support the concept of Print Monitors since these only apply to local printers whose driver can make use of -a bi-directional link for communication. This field should be "NULL". +a bi-directional link for communication. This field should be "NULL". On a remote NT print server, the Print Monitor for a driver must already be installed prior to adding the driver or else the RPC will fail @@ -10238,34 +9816,32 @@ 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 for obtaining 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 and indicated the breaks with "\". Usually you would type the command in one line without the linebreaks: -

    -
- adddriver "Architecture" \
-           "LongPrinterName:DriverFile:DataFile:ConfigFile:HelpFile:\
-           LanguageMonitorFile:DataType:ListOfFiles,Comma-separated"
-
+
    + adddriver "Architecture" \
+           "LongPrinterName:DriverFile:DataFile:ConfigFile:HelpFile:\
+           LanguageMonitorFile:DataType:ListOfFiles,Comma-separated"
 
    
 What the man pages denotes as a simple <config>
 keyword, does in reality consist of 8 colon-separated fields. The
 last field may take multiple (in some, very insane, cases, even
 20 different additional files. This might sound confusing at first.
-Note, that what the man pages names the "LongPrinterName" in
-reality should rather be called the "Driver Name". You can name it
+Note, that what the man pages names the "LongPrinterName" in
+reality should rather be called the "Driver Name". You can name it
 anything you want, as long as you use this name later in the
 rpcclient ... setdriver command. For
 practical reasons, many name the driver the same as the
 printer.
 
    
 True: it isn't simple at all. I hear you asking:
-How do I know which files are "Driver
-File", "Data File", "Config File", "Help File" and "Language
-Monitor File" in each case? -- For an answer you may
+How do I know which files are "Driver
+File", "Data File", "Config File", "Help File" and "Language
+Monitor File" in each case? -- For an answer you may
 want to have a look at how a Windows NT box with a shared printer
 presents the files to us. Remember, that this whole procedure has
 to be developed by the Samba Team by overhearing the traffic caused
@@ -10274,23 +9850,23 @@ 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 which we've read just
 now.
-

    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 UNIX or Linux workstation with the Samba utilities installed. Then type the following command: 

    -
- rpcclient -U'USERNAME%PASSWORD' NT-SERVER-NAME -c 'getdriver printername 3'
-
+root# rpcclient -U'USERNAME%PASSWORD' NT-SERVER-NAME -c 'getdriver printername 3'

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

    -
-# rpcclient -U'Danka%xxxx' W2KSERVER -c'getdriver "DANKA InfoStream Virtual Printer" 3'
- cmd = getdriver "DANKA InfoStream Virtual Printer" 3
+
    +root# rpcclient -U'Danka%xxxx' W2KSERVER \
+	-c'getdriver "DANKA InfoStream Virtual Printer" 3'
+ cmd = getdriver "DANKA InfoStream Virtual Printer" 3
 
  [Windows NT x86]
  Printer Driver Info 3:
@@ -10315,34 +9891,38 @@ example from my installation:
 
 
    
 Some printer drivers list additional files under the label
-"Dependentfiles": these would go into the last field
+"Dependentfiles": these would go into the last field
 ListOfFiles,Comma-separated. For the CUPS
 PostScript drivers we don't need any (nor would we for the Adobe
-PostScript driver): therefore the field will get a "NULL" entry.
-

    What is required for adddriver and setdriver to succeed

    +PostScript driver): therefore the field will get a "NULL" entry. +

    What is required for adddriver and setdriver to succeed

    From the manpage (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 setdriver) need to encounter the following pre-conditions to complete successfully: -

    • you are connected as "printer admin", or root (note, -that this is not the "Printer Operators" group in +

      • you are connected as printer admin, or root (note, +that this is not the "Printer Operators" group in NT, but the printer admin group, as defined in the [global] section of smb.conf);

      • copy all required driver files to \\sambaserver\print$\w32x86 and \\sambaserver\print$\win40 as appropriate. They -will end up in the "0" respective "2" subdirectories later -- for now +will end up in the "0" respective "2" subdirectories later -- for now don't put them there, they'll be automatically used by the adddriver subcommand.! (if you use -"smbclient" to put the driver files into the share, note that you need -to escape the "$": smbclient //sambaserver/print\$ -U +"smbclient" to put the driver files into the share, note that you need +to escape the "$": smbclient //sambaserver/print\$ -U root);

      • the user you're connecting as must be able to write to the [print$] share and create subdirectories;

      • the printer you are going to setup for the Windows -clients, needs to be installed in CUPS already;

      • the CUPS printer must be known to Samba, otherwise the +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 @@ -10350,164 +9930,145 @@ 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 shortly ago and encounter problems: try restarting -Samba.

    Manual Commandline Driver Installation in 15 little Steps

    +Samba.

    Manual Driver Installation in 15 Steps

    We are going to install a printer driver now by manually executing all required commands. As 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. -

    First Step: Install the Printer on CUPS

    -
-# lpadmin -p mysmbtstprn -v socket://10.160.51.131:9100 -E -P /home/kurt/canonIR85.ppd
-
+
    Procedure 19.1. Manual Driver Installation installation
    1. Install the Printer on CUPS
      +root# lpadmin -p mysmbtstprn -v socket://10.160.51.131:9100 -E -P canonIR85.ppd
 
      
 This installs printer with the name mysmbtstprn
 to the CUPS system. The printer is accessed via a socket
 (a.k.a. JetDirect or Direct TCP/IP) connection. You need to be root
 for this step
-
    Second Step (optional): Check if the Printer is recognized by
-Samba
    -
- # rpcclient -Uroot%xxxx -c 'enumprinters' localhost | grep -C2 mysmbtstprn
-
-        flags:[0x800000]
-        name:[\\kde-bitshop\mysmbtstprn]
-        description:[\\kde-bitshop\mysmbtstprn,,mysmbtstprn]
-        comment:[mysmbtstprn]
-
+
  • (optional) Check if the Printer is recognized by
+Samba
    +root# rpcclient -Uroot%xxxx -c 'enumprinters' localhost | grep -C2 mysmbtstprn
+flags:[0x800000]
+name:[\\kde-bitshop\mysmbtstprn]
+description:[\\kde-bitshop\mysmbtstprn,,mysmbtstprn]
+comment:[mysmbtstprn]
 
    
 This should show the printer in the list. If not, stop and re-start
 the Samba daemon (smbd), or send a HUP signal: kill -HUP
 `pidof smbd`. Check again.  Troubleshoot and repeat until
-success. Note the "empty" field between the two commas in the
-"description" line. Here would the driver name appear if there was one
+success. Note the "empty" field between the two commas in the
+"description" line. Here would the driver name appear if there was one
 already. You need to know root's Samba password (as set by the
 smbpasswd command) for this step and most of the
 following steps. Alternatively you can authenticate as one of the
-users from the "write list" as defined in smb.conf for
+users from the "write list" as defined in smb.conf for
 [print$].
-
    • Third Step (optional): Check if Samba knows a Driver for the
-Printer
    -
-#  rpcclient -Uroot%xxxx -c 'getprinter mysmbtstprn 2' localhost | grep driver
-         drivername:[]
+
  • (optional) Check if Samba knows a Driver for the
+Printer
    +root# rpcclient -Uroot%xxxx -c 'getprinter mysmbtstprn 2' localhost \
+			| grep driver 
+drivername:[]
+
+root# rpcclient -Uroot%xxxx -c 'getprinter mysmbtstprn 2' localhost \
+	| grep -C4 driv
+servername:[\\kde-bitshop]
+printername:[\\kde-bitshop\mysmbtstprn]
+sharename:[mysmbtstprn]
+portname:[Samba Printer Port]
+drivername:[]
+comment:[mysmbtstprn]
+location:[]
+sepfile:[]
+printprocessor:[winprint]
  
-#  rpcclient -Uroot%xxxx -c 'getprinter mysmbtstprn 2' localhost | grep -C4 driv
-        servername:[\\kde-bitshop]
-        printername:[\\kde-bitshop\mysmbtstprn]
-        sharename:[mysmbtstprn]
-        portname:[Samba Printer Port]
-        drivername:[]
-        comment:[mysmbtstprn]
-        location:[]
-        sepfile:[]
-        printprocessor:[winprint]
- 
-#  rpcclient -U root%xxxx -c 'getdriver mysmbtstprn' localhost
+root# rpcclient -U root%xxxx -c 'getdriver mysmbtstprn' localhost
  result was WERR_UNKNOWN_PRINTER_DRIVER
 
 
    
 Neither method of the three commands shown above should show a driver.
 This step was done for the purpose of demonstrating this condition. An
 attempt to connect to the printer at this stage will prompt the
-message along the lines: "The server has not the required printer
-driver installed".
-
    • Fourth Step: Put all required Driver Files into Samba's
-[print$]
    -
-#  smbclient //localhost/print\$ -U 'root%xxxx'                        \ 
-                              -c 'cd W32X86;                                             \
-                                  put /etc/cups/ppd/mysmbtstprn.ppd mysmbtstprn.PPD;     \
-                                  put /usr/share/cups/drivers/cupsui.dll cupsui.dll;     \
-                                  put /usr/share/cups/drivers/cupsdrvr.dll cupsdrvr.dll; \
-                                  put /usr/share/cups/drivers/cups.hlp cups.hlp'
-
+message along the lines: "The server has not the required printer
+driver installed".
+
  • Put all required Driver Files into Samba's
+[print$]
    +root# smbclient //localhost/print\$ -U 'root%xxxx' \
+	-c 'cd W32X86; \
+	put /etc/cups/ppd/mysmbtstprn.ppd mysmbtstprn.PPD; \ 
+	put /usr/share/cups/drivers/cupsui.dll cupsui.dll; \
+	put /usr/share/cups/drivers/cupsdrvr.dll cupsdrvr.dll; \
+	put /usr/share/cups/drivers/cups.hlp cups.hlp'
 
    
 (Note that this command should be entered in one long single
-line. Line-breaks and the line-end indicating "\" has been inserted
+line. Line-breaks and the line-end indicating "\" has been inserted
 for readability reasons.) This step is required
 for the next one to succeed. It makes the driver files physically
 present in the [print$] share. However, clients
 would still not be able to install them, because Samba does not yet
 treat them as driver files. A client asking for the driver would still
-be presented with a "not installed here" message.
-
    • Fifth Step: Verify where the Driver Files are now
    -
-#  ls -l /etc/samba/drivers/W32X86/
- total 669
- drwxr-sr-x    2 root     ntadmin       532 May 25 23:08 2
- drwxr-sr-x    2 root     ntadmin       670 May 16 03:15 3
- -rwxr--r--    1 root     ntadmin     14234 May 25 23:21 cups.hlp
- -rwxr--r--    1 root     ntadmin    278380 May 25 23:21 cupsdrvr.dll
- -rwxr--r--    1 root     ntadmin    215848 May 25 23:21 cupsui.dll
- -rwxr--r--    1 root     ntadmin    169458 May 25 23:21 mysmbtstprn.PPD
-
-
    
-The driver files now are in the W32X86 architecture "root" of
+be presented with a "not installed here" message.
+
  • Verify where the Driver Files are now
    +root# ls -l /etc/samba/drivers/W32X86/
+total 669
+drwxr-sr-x    2 root     ntadmin       532 May 25 23:08 2
+drwxr-sr-x    2 root     ntadmin       670 May 16 03:15 3
+-rwxr--r--    1 root     ntadmin     14234 May 25 23:21 cups.hlp
+-rwxr--r--    1 root     ntadmin    278380 May 25 23:21 cupsdrvr.dll
+-rwxr--r--    1 root     ntadmin    215848 May 25 23:21 cupsui.dll
+-rwxr--r--    1 root     ntadmin    169458 May 25 23:21 mysmbtstprn.PPD
+
    
+The driver files now are in the W32X86 architecture "root" of
 [print$].
-
    • Sixth Step: Tell Samba that these are
+
  • Tell Samba that these are
 Driver Files
-(adddriver)
    • -
-#  rpcclient -Uroot%xxxx -c `adddriver "Windows NT x86" "mydrivername: \
-                                          cupsdrvr.dll:mysmbtstprn.PPD:                  \
-                                          cupsui.dll:cups.hlp:NULL:RAW[:]NULL"             \
-                                          localhost
-
- Printer Driver mydrivername successfully installed.
-
+(adddriver)
    +root# rpcclient -Uroot%xxxx -c `adddriver "Windows NT x86" "mydrivername: \
+  cupsdrvr.dll:mysmbtstprn.PPD: \
+  cupsui.dll:cups.hlp:NULL:RAW:NULL" \
+  localhost
+Printer Driver mydrivername successfully installed.
 
    
 Note that your cannot repeat this step if it fails. It could fail even
 as a result of a simple typo. It will most likely have moved a part of
-the driver files into the "2" subdirectory. If this step fails, you
+the driver files into the "2" subdirectory. If this step fails, you
 need to go back to the fourth step and repeat it, before you can try
 this one again. In this step you need to choose a name for your
 driver. It is normally a good idea to use the same name as is used for
 the printername; however, in big installations you may use this driver
 for a number of printers which have obviously different names. So the
 name of the driver is not fixed.
-
    Seventh Step: Verify where the Driver Files are now
    -
-#  ls -l /etc/samba/drivers/W32X86/
- total 1
- drwxr-sr-x    2 root     ntadmin       532 May 25 23:22 2
- drwxr-sr-x    2 root     ntadmin       670 May 16 03:15 3
-
- 
-#  ls -l /etc/samba/drivers/W32X86/2
- total 5039
- [....]
- -rwxr--r--    1 root     ntadmin     14234 May 25 23:21 cups.hlp
- -rwxr--r--    1 root     ntadmin    278380 May 13 13:53 cupsdrvr.dll
- -rwxr--r--    1 root     ntadmin    215848 May 13 13:53 cupsui.dll
- -rwxr--r--    1 root     ntadmin    169458 May 25 23:21 mysmbtstprn.PPD
-
+
  • Verify where the Driver Files are now
    +root# ls -l /etc/samba/drivers/W32X86/
+total 1
+drwxr-sr-x    2 root     ntadmin       532 May 25 23:22 2
+drwxr-sr-x    2 root     ntadmin       670 May 16 03:15 3
+
+root# ls -l /etc/samba/drivers/W32X86/2
+total 5039
+[....]
+-rwxr--r--    1 root     ntadmin     14234 May 25 23:21 cups.hlp
+-rwxr--r--    1 root     ntadmin    278380 May 13 13:53 cupsdrvr.dll
+-rwxr--r--    1 root     ntadmin    215848 May 13 13:53 cupsui.dll
+-rwxr--r--    1 root     ntadmin    169458 May 25 23:21 mysmbtstprn.PPD
 
    
 Notice how step 6 did also move the driver files to the appropriate
 subdirectory. Compare with the situation after step 5.
-
    • Eighth Step (optional): Verify if Samba now recognizes the
-Driver
    -
-#  rpcclient -Uroot%xxxx -c 'enumdrivers 3' localhost | grep -B2 -A5 mydrivername
-
- Printer Driver Info 3:
-        Version: [2]
-        Driver Name: [mydrivername]
-        Architecture: [Windows NT x86]
-        Driver Path: [\\kde-bitshop\print$\W32X86\2\cupsdrvr.dll]
-        Datafile: [\\kde-bitshop\print$\W32X86\2\mysmbtstprn.PPD]
-        Configfile: [\\kde-bitshop\print$\W32X86\2\cupsui.dll]
-        Helpfile: [\\kde-bitshop\print$\W32X86\2\cups.hlp]
-
+
  • (optional) Verify if Samba now recognizes the
+Driver
    +root# rpcclient -Uroot%xxxx -c 'enumdrivers 3' localhost \
+	| grep -B2 -A5 mydrivername
+Printer Driver Info 3:
+Version: [2]
+Driver Name: [mydrivername]
+Architecture: [Windows NT x86]
+Driver Path: [\\kde-bitshop\print$\W32X86\2\cupsdrvr.dll]
+Datafile: [\\kde-bitshop\print$\W32X86\2\mysmbtstprn.PPD]
+Configfile: [\\kde-bitshop\print$\W32X86\2\cupsui.dll]
+Helpfile: [\\kde-bitshop\print$\W32X86\2\cups.hlp]
 
    
 Remember, this command greps for the name you did choose for the
 driver in step Six. This command must succeed before you can proceed.
-
    • Ninth Step: Tell Samba which Printer should use these Driver
-Files (setdriver)
    -
-#  rpcclient -Uroot%xxxx -c 'setdriver mysmbtstprn mydrivername' localhost
- 
- Successfully set mysmbtstprn to driver mydrivername
-
+
  • Tell Samba which Printer should use these Driver
+Files (setdriver)
    +root# rpcclient -Uroot%xxxx -c 'setdriver mysmbtstprn mydrivername' localhost
+Successfully set mysmbtstprn to driver mydrivername
 
    
 Since you can bind any printername (=printqueue) to any driver, this
 is a very convenient way to setup many queues which use the same
@@ -10515,99 +10076,95 @@ driver. You don't need to repeat all the previous steps for the
 setdriver command to succeed. The only pre-conditions are:
 enumdrivers must find the driver and
 enumprinters must find the printer.
-
    • Tenth Step (optional): Verify if Samba has this Association
-recognized
    -
-#  rpcclient -Uroot%xxxx -c 'getprinter mysmbtstprn 2' localhost | grep driver
-       drivername:[mydrivername]
+
  • (optional) Verify if Samba has this Association
+recognized
    +root# rpcclient -Uroot%xxxx -c 'getprinter mysmbtstprn 2' localhost \
+  | grep driver
+drivername:[mydrivername]
  
-#  rpcclient -Uroot%xxxx -c 'getprinter mysmbtstprn 2' localhost | grep -C4 driv
-       servername:[\\kde-bitshop]
-       printername:[\\kde-bitshop\mysmbtstprn]
-       sharename:[mysmbtstprn]
-       portname:[Done]
-       drivername:[mydrivername]
-       comment:[mysmbtstprn]
-       location:[]
-       sepfile:[]
-       printprocessor:[winprint]
+root# rpcclient -Uroot%xxxx -c 'getprinter mysmbtstprn 2' localhost \
+  | grep -C4 driv
+servername:[\\kde-bitshop]
+printername:[\\kde-bitshop\mysmbtstprn]
+sharename:[mysmbtstprn]
+portname:[Done]
+drivername:[mydrivername]
+comment:[mysmbtstprn]
+location:[]
+sepfile:[]
+printprocessor:[winprint]
  
-#  rpcclient -U root%xxxx -c 'getdriver mysmbtstprn' localhost
- [Windows NT x86]
- Printer Driver Info 3:
-       Version: [2]
-       Driver Name: [mydrivername]
-       Architecture: [Windows NT x86]
-       Driver Path: [\\kde-bitshop\print$\W32X86\2\cupsdrvr.dll]
-       Datafile: [\\kde-bitshop\print$\W32X86\2\mysmbtstprn.PPD]
-       Configfile: [\\kde-bitshop\print$\W32X86\2\cupsui.dll]
-       Helpfile: [\\kde-bitshop\print$\W32X86\2\cups.hlp]
-       Monitorname: []
-       Defaultdatatype: [RAW]
-       Monitorname: []
-       Defaultdatatype: [RAW]
+root# rpcclient -U root%xxxx -c 'getdriver mysmbtstprn' localhost
+[Windows NT x86]
+Printer Driver Info 3:
+     Version: [2]
+     Driver Name: [mydrivername]
+     Architecture: [Windows NT x86]
+     Driver Path: [\\kde-bitshop\print$\W32X86\2\cupsdrvr.dll]
+     Datafile: [\\kde-bitshop\print$\W32X86\2\mysmbtstprn.PPD]
+     Configfile: [\\kde-bitshop\print$\W32X86\2\cupsui.dll]
+     Helpfile: [\\kde-bitshop\print$\W32X86\2\cups.hlp]
+     Monitorname: []
+     Defaultdatatype: [RAW]
+     Monitorname: []
+     Defaultdatatype: [RAW]
  
-#  rpcclient -Uroot%xxxx -c 'enumprinters' localhost | grep mysmbtstprn
-       name:[\\kde-bitshop\mysmbtstprn]
-       description:[\\kde-bitshop\mysmbtstprn,mydrivername,mysmbtstprn]
-       comment:[mysmbtstprn]
+root# rpcclient -Uroot%xxxx -c 'enumprinters' localhost | grep mysmbtstprn
+     name:[\\kde-bitshop\mysmbtstprn]
+     description:[\\kde-bitshop\mysmbtstprn,mydrivername,mysmbtstprn]
+     comment:[mysmbtstprn]
 
 
    
+
 Compare these results with the ones from steps 2 and 3. Note that
 every single of these commands show the driver is installed.  Even
 the enumprinters command now lists the driver
-on the "description" line.
-
    • Eleventh Step (optional): Tickle the Driver into a correct
-Device Mode
    
+on the "description" line.
+
  • (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 Neighbourhood, go to the Samba server, look
 for the shares. You should see all shared Samba printers.
 Double-click on the one in question. The driver should get
 installed, and the network connection set up. An alternative way is to
-open the "Printers (and Faxes)" folder, right-click on the printer in
-question and select "Connect" or "Install". As a result, a new printer
-should have appeared in your client's local "Printers (and Faxes)"
-folder, named something like "printersharename on Sambahostname".
+open the "Printers (and Faxes)" folder, right-click on the printer in
+question and select "Connect" or "Install". As a result, a new printer
+should have appeared in your client's local "Printers (and Faxes)"
+folder, named something like "printersharename on Sambahostname".
 
    
 It is important that you execute this step as a Samba printer admin
 (as defined in smb.conf). Here is another method
 to do this on Windows XP. It uses a commandline, which you may type
-into the "DOS box" (type root's smbpassword when prompted):
+into the "DOS box" (type root's smbpassword when prompted):
 
    -
- C:\> runas /netonly /user:root "rundll32 printui.dll,PrintUIEntry /in /n \\sambacupsserver\mysmbtstprn"
-
+C:\> runas /netonly /user:root "rundll32 printui.dll,PrintUIEntry /in /n\
+			\\sambacupsserver\mysmbtstprn"
 
    
-Change any printer setting once (like "portrait"
---> "landscape"), click "Apply"; change the setting
+Change any printer setting once (like changing "portrait" to
+	"landscape"), click Apply; change the setting
 back.
-
    • Twelfth Step: Install the Printer on a Client
-("Point'n'Print")
    -
- C:\> rundll32 printui.dll,PrintUIEntry /in /n "\\sambacupsserver\mysmbtstprn"
-
+
  • Install the Printer on a Client
+("Point'n'Print")
    +C:\> rundll32 printui.dll,PrintUIEntry /in /n "\\sambacupsserver\mysmbtstprn"
 
    
 If it doesn't work it could be a permission problem with the
 [print$] share.
-
    • Thirteenth Step (optional): Print a Test Page
    -
- C:\> rundll32 printui.dll,PrintUIEntry /p /n "\\sambacupsserver\mysmbtstprn"
-
+
  • Thirteenth Step (optional): Print a Test Page
    +C:\> rundll32 printui.dll,PrintUIEntry /p /n "\\sambacupsserver\mysmbtstprn"
 
    
 Then hit [TAB] 5 times, [ENTER] twice, [TAB] once and [ENTER] again
 and march to the printer.
-
    • Fourteenth Step (recommended): Study the Test Page
    
+
  • Fourteenth Step (recommended): Study the Test Page
    
 Hmmm.... just kidding! By now you know everything about printer
 installations and you don't need to read a word. Just put it in a
-frame and bolt it to the wall with the heading "MY FIRST
-RPCCLIENT-INSTALLED PRINTER" - why not just throw it away!
-
    • Fifteenth Step (obligatory): Enjoy. Jump. Celebrate your
-Success
    -
-# echo "Cheeeeerioooooo! Success..." >> /var/log/samba/log.smbd     
-
-

    Troubleshooting revisited

    +frame and bolt it to the wall with the heading "MY FIRST +RPCCLIENT-INSTALLED PRINTER" - why not just throw it away! +

  • Fifteenth Step (obligatory): Enjoy. Jump. Celebrate your +Success

    +root# echo "Cheeeeerioooooo! Success..." >> /var/log/samba/log.smbd
+

    • Troubleshooting revisited

    The setdriver command will fail, if in Samba's mind the queue is not already there. You had promising messages about the: 

    @@ -10615,42 +10172,52 @@ already there. You had promising messages about the:
  Printer Driver ABC successfully installed.

    -after the "adddriver" parts of the procedure? But you are also seeing +after the "adddriver" parts of the procedure? But you are also seeing a disappointing message like this one beneath? 

     
  result was NT_STATUS_UNSUCCESSFUL

    -It is not good enough that you + +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 queuelist. The recognition of newly installed CUPS printers fails unless you re-start Samba or send a HUP to all smbd processes. To verify if this is the reason why Samba doesn't -execute the setdriver command successfully, check if Samba "sees" +execute the setdriver command successfully, check if Samba "sees" the printer: -

    -
-# rpcclient transmeta -N -U'root%secret' -c 'enumprinters 0'| grep  ir85wm
+
    +root# rpcclient transmeta -N -U'root%secret' -c 'enumprinters 0'| grep  ir85wm
         printername:[ir85wm]
-
 
    
 An alternative command could be this: 
-
    -
-# rpcclient transmeta -N -U'root%secret' -c 'getprinter ir85wm' 
+
    +root# rpcclient transmeta -N -U'root%secret' -c 'getprinter ir85wm' 
         cmd = getprinter ir85wm
         flags:[0x800000]
         name:[\\transmeta\ir85wm]
         description:[\\transmeta\ir85wm,ir85wm,DPD]
         comment:[CUPS PostScript-Treiber for WinNT/2K/XP]
-
 
    
 BTW, 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, @@ -10665,12 +10232,12 @@ tdb-suffix appearing in every Samba installation. They are 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, +"Registry". Client queries are answered by reading from the registry, Administrator or user configuration settings are saved by writing into -the Registry. Samba and Unix obviously don't have such a kind of +the Registry. Samba and UNIX obviously don't have such a kind of Registry. Samba instead keeps track of all client related information in a series of *.tdb files. (TDB = Trivial Data Base). These are often located in /var/lib/samba/ @@ -10678,10 +10245,10 @@ 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 proofed tradition on UNIX." +written in a binary format. "Why not ASCII?", you may ask. "After all, +ASCII configuration files are a good and proofed tradition on UNIX." -- The reason for this design decision by the Samba Team is mainly performance. Samba needs to be fast; it runs a separate smbd process for each client connection, in some @@ -10691,7 +10258,7 @@ 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 @@ -10701,13 +10268,12 @@ etc.). In cases of trouble, a deletion of the old printing-related *.tdb files may be the only option. You need to re-create all print related setup after that. Or you have made a backup of the *.tdb files in time. -

    Using tdbbackup

    +

    Using tdbbackup

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

    -
-# tdbbackup
+root# tdbbackup
  Usage: tdbbackup [options] <fname...>
  
  Version:3.0a
@@ -10718,36 +10284,34 @@ with no argument, it prints a little usage message:

    Here is how I backed up my printing.tdb file: 

    -
-# ls 
- .           browse.dat       locking.tdb     ntdrivers.tdb   printing.tdb    share_info.tdb
- ..          connections.tdb  messages.tdb    ntforms.tdb     printing.tdbkp  unexpected.tdb
- brlock.tdb  gmon.out         namelist.debug  ntprinters.tdb  sessionid.tdb
+root# ls
+.              browse.dat       locking.tdb     ntdrivers.tdb   printing.tdb
+..             share_info.tdb   connections.tdb messages.tdb    ntforms.tdb
+printing.tdbkp unexpected.tdb   brlock.tdb      gmon.out        namelist.debug  
+ntprinters.tdb sessionid.tdb
  
- kde-bitshop:/var/lock/samba # tdbbackup -s .bak printing.tdb
+root# tdbbackup -s .bak printing.tdb
  printing.tdb : 135 records
  
- kde-bitshop:/var/lock/samba # ls -l printing.tdb*
+root# ls -l printing.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: -

    -
-lpadmin -p laserjet4plus -v parallel:/dev/lp0 -E -m laserjet.ppd
-
+
    +root# lpadmin -p laserjet4plus -v parallel:/dev/lp0 -E -m laserjet.ppd
 
    
-The -m switch will retrieve the
+The -m switch will retrieve the
 laserjet.ppd from the standard repository for
 not-yet-installed-PPDs, which CUPS typically stores in
 /usr/share/cups/model. Alternatively, you may use
--P /path/to/your.ppd.
+-P /path/to/your.ppd.
 
    
 The generic laserjet.ppd however does not support every special option
-for every LaserJet-compatible model. It constitutes a sort of "least
-denominator" of all the models. If for some reason it is ruled out to
+for every LaserJet-compatible model. It constitutes a sort of "least
+denominator" of all the models. If for some reason it is ruled out to
 you to pay for the commercially available ESP Print Pro drivers, your
 first move should be to consult the database on http://www.linuxprinting.org/printer_list.cgi.
 Linuxprinting.org has excellent recommendations about which driver is
@@ -10755,8 +10319,9 @@ best used for each printer. Its database is kept current by 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 be replaced by the new, much
-more powerful "foomatic-rip". foomatic-rip is the successor of
+
+The former "cupsomatic" concept is now be replaced by the new, much
+more powerful "foomatic-rip". foomatic-rip is the successor of
 cupsomatic. cupsomatic is no longer maintained. Here is the new URL
 to the Foomatic-3.0 database:http://www.linuxprinting.org/driver_list.cgi.
 If you upgrade to foomatic-rip, don't forget to also upgrade to the
@@ -10765,7 +10330,7 @@ not work with PPDs generated for the old cupsomatic. The new-style
 PPDs are 100% compliant to the Adobe PPD specification. They are
 intended to be used by Samba and the cupsaddsmb utility also, to
 provide the driver files for the Windows clients also!
-
    foomatic-rip and Foomatic explained
    
+
    foomatic-rip and Foomatic explained
    
 Nowadays most Linux distros rely on the utilities of Linuxprinting.org
 to create their printing related software (which, BTW, works on all
 UNIXes and on Mac OS X or Darwin too). It is not known as well as it
@@ -10782,63 +10347,63 @@ its Foomatic<
 database. Currently there are 245 drivers
 in the database: many drivers support various models, and many models
 may be driven by different drivers; it's your choice!
-
    690 "perfect" Printers
    
-At present there are 690 devices dubbed as working "perfectly", 181
-"mostly", 96 "partially" and 46 are "Paperweights". Keeping in mind
+
    690 "perfect" Printers
    
+At present there are 690 devices dubbed as working "perfectly", 181
+"mostly", 96 "partially" and 46 are "Paperweights". Keeping in mind
 that most of these are non-PostScript models (PostScript printers are
 automatically supported supported by CUPS to perfection, by using
 their own manufacturer-provided Windows-PPD...), and that a
-multifunctional device never qualifies as working "perfectly" if it
+multifunctional device never qualifies as working "perfectly" if it
 doesn't 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
+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 which he authored. As a side-project to this document,
 which served many Linux users and admins to guide their first steps in
 this complicated and delicate setup (to a scientist, printing is
-"applying a structured deposition of distinct patterns of ink or toner
-particles on paper substrates" ;-), he started to
+"applying a structured deposition of distinct patterns of ink or toner
+particles on paper substrates" ;-), he started to
 build in a little 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
    
-"Why the funny name?", you ask. When it really took off, around spring
+
    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"
+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. CUPS also shipped with its own
-built-in rasterization filter ("pstoraster", derived from
+built-in rasterization filter ("pstoraster", derived from
 Ghostscript). On the other hand, CUPS provided brilliant support for
 controlling all printer options through
-standardized and well-defined "PPD files" (PostScript Printers
+standardized and well-defined "PPD files" (PostScript Printers
 Description files). Plus, CUPS was designed to be easily extensible.
 
    
 Grant already had in his database a respectable compilation
-of facts about a many more printers, and the Ghostscript "drivers"
+of facts about a many more printers, and the Ghostscript "drivers"
 they run with. His idea, to generate PPDs from the database info
 and use them to make standard Ghostscript filters work within CUPS,
-proved to work very well. It also "killed several birds with one
-stone":
+proved to work very well. It also "killed several birds with one
+stone":
 
    • It made all current and future Ghostscript filter
 developments available for CUPS;
    • It made available a lot of additional printer models
-to CUPS users (because often the "traditional" Ghostscript way of
+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
 required to be copied into the CUPS system to make it work. To
-"configure" the way cupsomatic controls the Ghostscript rendering
+"configure" the way cupsomatic controls the Ghostscript rendering
 process, it needs a CUPS-PPD. This PPD is generated directly from the
 contents of the database. For CUPS and the respective printer/filter
-combo another Perl script named "CUPS-O-Matic" did the PPD
+combo another Perl script named "CUPS-O-Matic" did the PPD
 generation. After that was working, Grant implemented within a few
 days a similar thing for two other spoolers. Names chosen for the
 config-generator scripts were PDQ-O-Matic
@@ -10856,25 +10421,25 @@ printers. He also developed the support for other spoolers, like
 PPR (via ppromatic),
 GNUlpr and
 LPRng (both via an extended
-lpdomatic) and "spoolerless" printing (directomatic)....
+lpdomatic) and "spoolerless" printing (directomatic)....
 
    
-So, to answer your question: "Foomatic" is the general name for all
-the overlapping code and data behind the "*omatic" scripts.... --
+So, to answer your question: "Foomatic" is the general name for all
+the overlapping code and data behind the "*omatic" scripts.... --
 Foomatic up to versions 2.0.x required (ugly) Perl data structures
 attached the Linuxprinting.org PPDs for CUPS. It had a different
-"*omatic" script for every spooler, as well as different printer
+"*omatic" script for every spooler, as well as different printer
 configuration files..
-
    7.13.1.5.The Grand Unification
-achieved...
    
+
    The Grand Unification
+achieved...
    
 This all has changed in Foomatic versions 2.9 (Beta) and released as
-"stable" 3.0. This has now achieved the convergence of all *omatic
+"stable" 3.0. This has now achieved the convergence of all *omatic
 scripts: it is called the foomatic-rip.
 This single script is the unification of the previously different
 spooler-specific *omatic scripts. foomatic-rip is used by all the
 different spoolers alike. Because foomatic-rip can read PPDs (both the
 original PostScript printer PPDs and the Linuxprinting.org-generated
 ones), all of a sudden all supported spoolers can have the power of
-PPDs at their disposal; users only need to plug "foomatic-rip" into
+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.
 
    
@@ -10900,7 +10465,7 @@ sizes for many printers; and it 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
@@ -10913,7 +10478,7 @@ the work is currently done in three projects. These are:
 
    • Omni
 -- a Free Software project by IBM which tries to convert their printer
 driver knowledge from good-ol' OS/2 times into a modern, modular,
-universal driver architecture for Linux/Unix (still Beta).  This
+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 their own
 range of models (very mature, printing in most cases is perfect and
@@ -10923,9 +10488,9 @@ 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
    
-Linuxprinting.org today is the one-stop "shop" to download printer
+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.  But
 it's not just for GNU/Linux: users and admins of commercial UNIX
@@ -10944,17 +10509,17 @@ of the Foomatic project.
 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 +organized in a way that it can generate "PPD" files "on the fly" from its internal XML-based datasets. While these PPDs are modelled to the -Adobe specification of "PostScript Printer Descriptions" (PPDs), the +Adobe specification of "PostScript Printer Descriptions" (PPDs), the Linuxprinting.org/Foomatic-PPDs don't normally drive PostScript printers: they are used to describe all the bells and whistles you could ring or blow on an Epson Stylus inkjet, or a HP Photosmart or -what-have-you. The main "trick" is one little additional line, not -envisaged by the PPD specification, starting with the "*cupsFilter" +what-have-you. The main "trick" is one little additional line, not +envisaged by the PPD specification, starting with the "*cupsFilter" keyword: it tells the CUPS daemon how to proceed with the PostScript print file (old-style Foomatic-PPDs named the cupsomatic filter script, while the new-style @@ -10965,12 +10530,12 @@ filter or internal device setting it should ask from Ghostscript to convert the PostScript printjob into a raster format ready for the target device. This usage of PPDs to describe the options of non-PS printers was the invention of the CUPS developers. The rest is easy: -GUI tools (like KDE's marvellous "kprinter", -or the GNOME "gtklp", "xpp" and the CUPS +GUI tools (like KDE's marvellous "kprinter", +or the GNOME "gtklp", "xpp" and the CUPS web interface) read the PPD too 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

    -Here are the steps to install a foomatic-rip driven "LaserJet 4 Plus" +

    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 foomatic-rip utility. going directly to @@ -10982,12 +10547,12 @@ Linuxprinting.org ensures you to get the latest driver/PPD files): link.

  • You'll arrive at a page listing all drivers working with this model (for all printers, there will always be one recommended driver. Try this one -first).

  • In our case ("HP LaserJet 4 Plus"), we'll arrive here: -http://www.linuxprinting.org/show_printer.cgi?recnum=HP-LaserJet_4_Plus -

  • The recommended driver is "ljet4".

  • There are several links provided here. You should +first).

  • In our case ("HP LaserJet 4 Plus"), we'll arrive here: + http://www.linuxprinting.org/show_printer.cgi?recnum=HP-LaserJet_4_Plus +

  • The recommended driver is "ljet4".

  • There are several links provided here. You should visit them all, if you are not familiar with the Linuxprinting.org -database.

  • There is a link to the database page for the "ljet4": -http://www.linuxprinting.org/show_driver.cgi?driver=ljet4 +database.

  • There is a link to the database page for the "ljet4": + http://www.linuxprinting.org/show_driver.cgi?driver=ljet4 On the driver's page, you'll find important and detailed information about how to use that driver within the various available spoolers.

  • Another link may lead you to the homepage of the @@ -10996,7 +10561,7 @@ setup instructions for CUPS (http://www.linuxprinting.org/pdq-doc.html), LPD, LPRng and GNUlpr (http://www.linuxprinting.org/lpd-doc.html) as well as PPR (http://www.linuxprinting.org/ppr-doc.html) -or "spooler-less" printing (http://www.linuxprinting.org/direct-doc.html +or "spooler-less" printing (http://www.linuxprinting.org/direct-doc.html ).

  • You can view the PPD in your browser through this link: http://www.linuxprinting.org/ppd-o-matic.cgi?driver=ljet4&printer=HP-LaserJet_4_Plus&show=1

  • You can also (most importantly) @@ -11006,18 +10571,18 @@ model and the driver; this is, once installed, working transparently for the user. Later you'll only need to choose resolution, paper size etc. from the web-based menu, or from the print dialog GUI, or from the commandline.

  • Should you have ended up on the driver's page (http://www.linuxprinting.org/show_driver.cgi?driver=ljet4), -you can choose to use the "PPD-O-Matic" online PPD generator -program.

  • Select the exact model and check either "download" or -"display PPD file" and click on "Generate PPD file".

  • If you save the PPD file from the browser view, please -don't use "cut'n'past" (since it could possibly damage line endings -and tabs, which makes the PPD likely to fail its duty), but use "Save -as..." in your browser's menu. (Best is to use the "download" option +you can choose to use the "PPD-O-Matic" online PPD generator +program.

  • Select the exact model and check either "download" or +"display PPD file" and click on "Generate PPD file".

  • If you save the PPD file from the browser view, please +don't use "cut'n'past" (since it could possibly damage line endings +and tabs, which makes the PPD likely to fail its duty), but use "Save +as..." in your browser's menu. (Best is to use the "download" option from the web page directly).

  • Another very interesting part on each driver page is the Show execution details button. If you select your printer model and click that button, you will get displayed a complete Ghostscript command line, enumerating all options available for that driver/printermodel combo. This is a great way to -"Learn Ghostscript By Doing". It is also an excellent "cheat sheet" +"Learn Ghostscript By Doing". It is also an excellent "cheat sheet" for all experienced users who need to re-construct a good command line for that damn printing script, but can't remember the exact syntax. ;-)

  • Some time during your visit to Linuxprinting.org, save @@ -11028,12 +10593,10 @@ the /usr/share/cups/model/ path and re-start cupsd).

  • Then install the printer with a suitable commandline, e.g.: 

    -
-lpadmin -p laserjet4plus -v parallel:/dev/lp0 -E -P path/to/my-printer.ppd
-
-

  • Note again this: for all the new-style "Foomatic-PPDs" -from Linuxprinting.org, you also need a special "CUPS filter" named -"foomatic-rip".Get the latest version of "foomatic-rip" from: http://www.linuxprinting.org/foomatic2.9/download.cgi?filename=foomatic-rip&show=0 +root# lpadmin -p laserjet4plus -v parallel:/dev/lp0 -E -P path/to/my-printer.ppd +

  • Note again this: for all the new-style "Foomatic-PPDs" +from Linuxprinting.org, you also need a special "CUPS filter" named +"foomatic-rip".Get the latest version of "foomatic-rip" from: http://www.linuxprinting.org/foomatic2.9/download.cgi?filename=foomatic-rip&show=0

  • The foomatic-rip Perlscript itself also makes some interesting reading (http://www.linuxprinting.org/foomatic2.9/download.cgi?filename=foomatic-rip&show=1), because it is very well documented by Till's inline comments (even @@ -11041,8 +10604,8 @@ non-Perl hackers will learn quite a bit about printing by reading it... ;-)

  • Save foomatic-rip either directly in /usr/lib/cups/filter/foomatic-rip or somewhere in your $PATH (and don't forget to make it world-executable). Again, -don't save by "copy'n'paste" but use the appropriate link, or the -"Save as..." menu item in your browser.

  • If you save foomatic-rip in your $PATH, create a symlink: +don't save by "copy'n'paste" but use the appropriate link, or the +"Save as..." menu item in your browser.

  • If you save foomatic-rip in your $PATH, create a symlink: cd /usr/lib/cups/filter/ ; ln -s `which foomatic-rip`. For CUPS to discover this new available filter at startup, you need to re-start @@ -11058,18 +10621,18 @@ data should look like and which printer commands to embed into the data stream.

    You need: -

    • A "foomatic+something" PPD -- but it this not enough +

      • A "foomatic+something" PPD -- but it this not enough to print with CUPS (it is only one important -component)

      • The "foomatic-rip" filter script (Perl) in +component)

      • The "foomatic-rip" filter script (Perl) in /usr/lib/cups/filters/

      • Perl to make foomatic-rip run

      • Ghostscript (because it is doing the main work, controlled by the PPD/foomatic-rip combo) to produce the raster data fit for your printermodel'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 +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 don't work with -foomatic-rip).

    • Page Accounting with CUPS

    -Often there are questions regarding "print quotas" wherein Samba users +foomatic-rip).

    Page Accounting with CUPS

    +Often there are questions regarding "print quotas" wherein Samba users (that is, Windows clients) should not be able to print beyond a certain amount of pages or data volume per day, week or month. This feature is dependent on the real print subsystem you're using. @@ -11077,58 +10640,57 @@ Samba's part is always to receive the job files from the clients (filtered or unfiltered) and hand it over to this printing subsystem.

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

    Setting up Quotas

    +

    Setting up Quotas

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

    -
-  lpadmin -p quotaprinter -o job-quota-period=604800 -o job-k-limit=1024 -o job-page-limit=100
-
+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 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 "1". Some +"pstops" filter, otherwise it uses a "dummy" count of "1". Some printfiles don't pass it (eg: image files) but then those are mostly 1 page jobs anyway. This also means that proprietary drivers for the target printer running on the client computers and CUPS/Samba, which -then spool these files as "raw" (i.e. leaving them untouched, not -filtering them), will be counted as "1-pagers" too! +then spool these files as "raw" (i.e. leaving them untouched, not +filtering them), will be counted as "1-pagers" too!

    You need to send PostScript from the clients (i.e. run a PostScript driver there) to have the chance to get 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 will be working for currently about 1,000 different printer models, -see http://www.linuxprinting.org/printer_list.cgi). -

    Adobe and CUPS PostScript Drivers for Windows Clients

    +see the driver list at linuxprinting.org/. +

    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 +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 "PJL"-header in front of +depending on the "PPD" being used, wrote a "PJL"-header in front of the real PostScript which caused CUPS to skip pstops and go directly -to the "pstoraster" stage). +to the "pstoraster" stage).

    -From CUPS-1.1.16 onward you can use the "CUPS PostScript Driver for -Windows NT/2K/XP 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 +From CUPS-1.1.16 onward you can use the "CUPS PostScript Driver for +Windows NT/2K/XP 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 Win9x/ME clients. But it guarantees: -

    • to not write an 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 +

      • to not write an 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 printfile

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

    The page_log File Syntax

    -These are the items CUPS logs in the "page_log" for every +

    The page_log File Syntax

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

    • Printer name

    • User name

    • Job ID

    • Time of printing

    • the page number

    • the number of copies

    • a billing information string (optional)

    • the host which sent the job (included since version @@ -11136,103 +10698,93 @@ single page of a job: Here is an extract of my CUPS server's page_log file to illustrate the format and included items: 

      -
-        infotec_IS2027 kurt 401 [22/Apr/2003:10:28:43 +0100] 1 3 #marketing 10.160.50.13
-        infotec_IS2027 kurt 401 [22/Apr/2003:10:28:43 +0100] 2 3 #marketing 10.160.50.13
-        infotec_IS2027 kurt 401 [22/Apr/2003:10:28:43 +0100] 3 3 #marketing 10.160.50.13
-        infotec_IS2027 kurt 401 [22/Apr/2003:10:28:43 +0100] 4 3 #marketing 10.160.50.13
-        DigiMaster9110 boss 402 [22/Apr/2003:10:33:22 +0100] 1 440 finance-dep 10.160.51.33
-
-

      -This was job ID "401", printed on "infotec_IS2027" by user "kurt", a -64-page job printed in 3 copies and billed to "#marketing", sent -from IP address 10.160.50.13. 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

    +infotec_IS2027 kurt 401 [22/Apr/2003:10:28:43 +0100] 1 3 #marketing 10.160.50.13 +infotec_IS2027 kurt 401 [22/Apr/2003:10:28:43 +0100] 2 3 #marketing 10.160.50.13 +infotec_IS2027 kurt 401 [22/Apr/2003:10:28:43 +0100] 3 3 #marketing 10.160.50.13 +infotec_IS2027 kurt 401 [22/Apr/2003:10:28:43 +0100] 4 3 #marketing 10.160.50.13 +DigiMaster9110 boss 402 [22/Apr/2003:10:33:22 +0100] 1 440 finance-dep 10.160.51.33 +

    +This was job ID "401", printed on "infotec_IS2027" by user "kurt", a +64-page job printed in 3 copies and billed to "#marketing", sent +from IP address 10.160.50.13. 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

    What flaws or shortcomings are there with this quota system?

    • the ones named above (wrongly logged job in case of printer hardware failure, etc.)

    • in reality, CUPS counts the job pages that are being processed in software (that is, going through the -"RIP") rather than the physical sheets successfully leaving the +"RIP") rather than the physical sheets successfully leaving the printing device. Thus if there is a jam while printing the 5th sheet out -of 1000 and the job is aborted by the printer, the "page count" will +of 1000 and the job is aborted by the printer, the "page count" will still show the figure of 1000 for that job

    • all quotas are the same for all users (no flexibility -to give the boss a higher quota than the clerk) no support for +to give the boss a higher quota than the clerk), no support for groups

    • no means to read out the current balance or the -"used-up" number of current quota

    • a user having used up 99 sheets of 100 quota will +"used-up" number of current quota

    • a user having used up 99 sheets of 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 doesn't 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 +

      • page counting will go into the "backends" (these talk directly to the printer and will increase the count in sync with the actual printing process: thus a jam at the 5th sheet will lead to a stop in the counting)

      • quotas will be handled more flexibly

      • probably there will be support for users to inquire -their "accounts" in advance

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

    Other Accounting Tools

    +their "accounts" in advance

  • probably there will be support for some other tools +around this topic

    • Other Accounting Tools

    PrintAnalyzer, pyKota, printbill, LogReport. -

    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" -which need "passthrough feature" enabled. "Raw" queues don't do any +"raw" printer and all files will go directly there as received by the +spooler. The exceptions are file types "application/octet-stream" +which need "passthrough feature" enabled. "Raw" queues don't do any filtering at all, they hand the file directly to the CUPS backend. This backend is responsible for the sending of the data to the device -(as in the "device URI" notation: lpd://, socket://, +(as in the "device URI" notation: lpd://, socket://, smb://, ipp://, http://, parallel:/, serial:/, usb:/ etc.)

    -"cupsomatic"/Foomatic are not native CUPS drivers +"cupsomatic"/Foomatic are not native CUPS drivers and they don't ship with CUPS. They are a Third Party add-on, developed at Linuxprinting.org. As such, they are a brilliant hack to make all models (driven by Ghostscript drivers/filters in traditional spoolers) also work via CUPS, with the same (good or bad!) quality as -in these other spoolers. "cupsomatic" is only a vehicle to execute a +in these other spoolers. "cupsomatic" is only a vehicle to execute a ghostscript commandline at that stage in the CUPS filtering chain, -where "normally" the native CUPS "pstoraster" filter would kick -in. cupsomatic by-passes pstoraster, "kidnaps" the printfile from CUPS +where "normally" the native CUPS "pstoraster" filter would kick +in. cupsomatic by-passes pstoraster, "kidnaps" the printfile from CUPS away and re-directs it to go through Ghostscript. CUPS accepts this, because the associated CUPS-O-Matic-/Foomatic-PPD specifies: -

    -
-   *cupsFilter:  "application/vnd.cups-postscript 0 cupsomatic"
-
+
    +  *cupsFilter:  "application/vnd.cups-postscript 0 cupsomatic"
 
    
 This line persuades CUPS to hand the file to cupsomatic, once it has
 successfully converted it to the MIME type
-"application/vnd.cups-postscript". This conversion will not happen for
+"application/vnd.cups-postscript". This conversion will not happen for
 Jobs arriving from Windows which are auto-typed
-"application/octet-stream", with the according changes in
+"application/octet-stream", with the according changes in
 /etc/cups/mime.types in place.
 
    
 CUPS is widely configurable and flexible, even regarding its filtering
 mechanism. Another workaround in some situations would be to have in
 /etc/cups/mime.types entries as follows:
-
    -
-   application/postscript           application/vnd.cups-raw  0  -
-   application/vnd.cups-postscript  application/vnd.cups-raw  0  -
-
+
    + application/postscript           application/vnd.cups-raw  0  -
+ application/vnd.cups-postscript  application/vnd.cups-raw  0  -
 
    
 This would prevent all Postscript files from being filtered (rather,
 they will through the virtual nullfilter
-denoted with "-").  This could only be useful for PS printers. If you
+denoted with "-").  This could only be useful for PS printers. If you
 want to print PS code on non-PS printers (provided they support ASCII
 text printing) an entry as follows could be useful:
-
    -
-   */*           application/vnd.cups-raw  0  -
-
+
    + */*           application/vnd.cups-raw  0  -
 
    
 and would effectively send all files to the
 backend without further processing.
 
    
 Lastly, you could have the following entry:
-
    -
-   application/vnd.cups-postscript  application/vnd.cups-raw  0  my_PJL_stripping_filter
-
+
    +application/vnd.cups-postscript application/vnd.cups-raw 0 my_PJL_stripping_filter
 
    
 You will need to write a my_PJL_stripping_filter
 (could be a shellscript) that parses the PostScript and removes the
@@ -11241,39 +10793,38 @@ unwanted PJL. This would need to conform to CUPS filter design
 username, jobtitle, copies, print options and possibly the
 filename). It would be installed as world executable into
 /usr/lib/cups/filters/ and will be called by CUPS
-if it encounters a MIME type "application/vnd.cups-postscript".
+if it encounters a MIME type "application/vnd.cups-postscript".
 
    
 CUPS can handle -o job-hold-until=indefinite.
-This keeps the job in the queue "on hold". It will only be printed
+This keeps the job in the queue "on hold". It will only be printed
 upon manual release by the printer operator. This is a requirement in
-many "central reproduction departments", where a few operators manage
+many "central reproduction departments", where a few operators manage
 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, etc.).
-

    Auto-Deletion 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 +

    Auto-Deletion 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

    This keeps some details of jobs in cupsd's mind (well it keeps the -"c12345", "c12346" etc. files in the CUPS spool directory, which do a +"c12345", "c12346" etc. files in the CUPS spool directory, which do a similar job as the old-fashioned BSD-LPD control files). This is set -to "Yes" as a default. +to "Yes" as a default.

    PreserveJobFiles Yes

    This keeps the job files themselves in cupsd's mind -(well it keeps the "d12345", "d12346" etc. files in the CUPS spool -directory...). This is set to "No" as the CUPS +(well it keeps the "d12345", "d12346" etc. files in the CUPS spool +directory...). This is set to "No" as the CUPS default. -

    "MaxJobs 500"

    +

    "MaxJobs 500"

    This directive controls the maximum number of jobs that are kept in memory. Once the number of jobs reaches the limit, the oldest completed job is automatically purged from the system to @@ -11282,468 +10833,153 @@ pending or active then the new job will be rejected. Setting the maximum to 0 disables this functionality. The default setting is 0.

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

    Pre-conditions

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

    Pre-conditions

    For everything to work as announced, you need to have three things: -

    • a Samba-smbd which is compiled against "libcups" (Check -on Linux by running "ldd `which smbd`")

    • a Samba-smb.conf setting of -"printing = cups"

    • another Samba-smb.conf setting of -"printcap = cups"

    Note

    +

    • a Samba-smbd which is compiled against "libcups" (Check +on Linux by running "ldd `which smbd`")

    • a Samba-smb.conf setting of + printing = cups

    • another Samba-smb.conf setting of + printcap = cups

    Note

    In this case all other manually set printing-related commands (like -"print command", "lpq command", "lprm command", "lppause command" or -"lpresume command") are ignored and they should normally have no +print command, +lpq command, +lprm command, +lppause command or +lpresume command) are ignored and they should normally have no influence what-so-ever on your printing. -

    Manual Configuration

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

    Manual Configuration

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

    When not to use Samba to print to -CUPS

    -[TO BE DONE] -

    In Case of Trouble.....

    +

    In Case of Trouble.....

    If you have more problems, post the output of these commands to the CUPS or Samba mailing lists (choose the one which seems more relevant to your problem): 

    -
-   grep -v ^# /etc/cups/cupsd.conf | grep -v ^$
-   grep -v ^# /etc/samba/smb.conf | grep -v ^$ | grep -v "^;"
-
+$ grep -v ^# /etc/cups/cupsd.conf | grep -v ^$
+$ grep -v ^# /etc/samba/smb.conf | grep -v ^$ | grep -v "^;"

    (adapt paths as needed). These commands leave out the empty -lines and lines with comments, providing the "naked settings" in a +lines and lines with comments, providing the "naked settings" in a compact way. Don't forget to name the CUPS and Samba versions you are using! This saves bandwidth and makes for easier readability for experts (and you are expecting experts to read them, right? ;-) -

    Where to find Documentation

    -[TO BE DONE] -

    How to ask for Help

    -[TO BE DONE] -

    Where to find Help

    -[TO BE DONE] -

    Appendix

    Printing from CUPS to Windows attached -Printers

    +

    Printing from CUPS to Windows attached +Printers

    From time to time the question arises, how you can print to a Windows attached printer from Samba. Normally the local connection -"Windows host <--> printer" would be done by USB or parallel +from Windows host to printer would be done by USB or parallel cable, but this doesn't matter to Samba. From here only an SMB connection needs to be opened to the Windows host. Of course, this -printer must be "shared" first. As you have learned by now, CUPS uses +printer must be "shared" first. As you have learned by now, CUPS uses backends to talk to printers and other servers. To talk to Windows shared printers you need to use the smb (surprise, surprise!) backend. Check if this is in the CUPS backend directory. This resides usually in -/usr/lib/cups/backend/. You need to find a "smb" +/usr/lib/cups/backend/. You need to find a "smb" file there. It should be a symlink to smbspool which file must exist and be executable: 

    -
- # ls -l /usr/lib/cups/backend/   
- total 253
- drwxr-xr-x    3 root     root          720 Apr 30 19:04 .
- drwxr-xr-x    6 root     root          125 Dec 19 17:13 ..
- -rwxr-xr-x    1 root     root        10692 Feb 16 21:29 canon
- -rwxr-xr-x    1 root     root        10692 Feb 16 21:29 epson
- lrwxrwxrwx    1 root     root            3 Apr 17 22:50 http -> ipp
- -rwxr-xr-x    1 root     root        17316 Apr 17 22:50 ipp
- -rwxr-xr-x    1 root     root        15420 Apr 20 17:01 lpd
- -rwxr-xr-x    1 root     root         8656 Apr 20 17:01 parallel
- -rwxr-xr-x    1 root     root         2162 Mar 31 23:15 pdfdistiller
- lrwxrwxrwx    1 root     root           25 Apr 30 19:04 ptal -> /usr/local/sbin/ptal-cups
- -rwxr-xr-x    1 root     root         6284 Apr 20 17:01 scsi
- lrwxrwxrwx    1 root     root           17 Apr  2 03:11 smb -> /usr/bin/smbspool
- -rwxr-xr-x    1 root     root         7912 Apr 20 17:01 socket
- -rwxr-xr-x    1 root     root         9012 Apr 20 17:01 usb
-
-# ls -l `which smbspool`
- -rwxr-xr-x    1 root     root       563245 Dec 28 14:49 /usr/bin/smbspool
-
+root# ls -l /usr/lib/cups/backend/
+total 253
+drwxr-xr-x    3 root     root          720 Apr 30 19:04 .
+drwxr-xr-x    6 root     root          125 Dec 19 17:13 ..
+-rwxr-xr-x    1 root     root        10692 Feb 16 21:29 canon
+-rwxr-xr-x    1 root     root        10692 Feb 16 21:29 epson
+lrwxrwxrwx    1 root     root            3 Apr 17 22:50 http -> ipp
+-rwxr-xr-x    1 root     root        17316 Apr 17 22:50 ipp
+-rwxr-xr-x    1 root     root        15420 Apr 20 17:01 lpd
+-rwxr-xr-x    1 root     root         8656 Apr 20 17:01 parallel
+-rwxr-xr-x    1 root     root         2162 Mar 31 23:15 pdfdistiller
+lrwxrwxrwx    1 root     root           25 Apr 30 19:04 ptal -> /usr/sbin/ptal-cups
+-rwxr-xr-x    1 root     root         6284 Apr 20 17:01 scsi
+lrwxrwxrwx    1 root     root           17 Apr  2 03:11 smb -> /usr/bin/smbspool
+-rwxr-xr-x    1 root     root         7912 Apr 20 17:01 socket
+-rwxr-xr-x    1 root     root         9012 Apr 20 17:01 usb
+
+root# ls -l `which smbspool`
+-rwxr-xr-x    1 root     root       563245 Dec 28 14:49 /usr/bin/smbspool

    If this symlink doesn't exist, create it: 

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

    smbspool has been 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 this means to convert the print data on the CUPS/Samba -host to a format that the printer can digest (the Windows host is -unable to convert any files you may send). This also means you should -be able to print to the printer if it were hooked directly at your -Samba/CUPS host. For troubleshooting purposes, this is what you -should do, to determine if that part of the process chain is in -order. Then proceed to fix the network connection/authentication to -the Windows host, etc. -

    -To install a printer with the smb backend on CUPS, use this command: -

    -
-# 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 -for: you can include the required parameters as part of the -smb:// device-URI. Like this: -

    -
- smb://WORKGROUP/WINDOWSNETBIOSNAME/printersharename 
- smb://username:password@WORKGROUP/WINDOWSNETBIOSNAME/printersharename
- smb://username:password@WINDOWSNETBIOSNAME/printersharename
-
-

    -Note that the device-URI will be visible in the process list of the -Samba server (e.g. when someone uses the ps -aux -command on Linux), even if the username and passwords are sanitized -before they get written into the log files. So this is an inherently -insecure option. However it is the only one. Don't use it if you want -to protect your passwords. Better share the printer in a way that -doesn't require a password! 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 don't necessarily need to have smbd running -(but who wants that? :-). -

    More CUPS filtering Chains

    -The following diagrams reveal how CUPS handles print jobs. -

    -#########################################################################
-#
-# CUPS in and of itself has this (general) filter chain (CAPITAL
-# letters are FILE-FORMATS or MIME types, other are filters (this is
-# true for pre-1.1.15 of pre-4.3 versions of CUPS and ESP PrintPro):
-#
-# SOMETHNG-FILEFORMAT
-#      |
-#      V
-#     somethingtops
-#      |
-#      V
-# APPLICATION/POSTSCRIPT
-#      |
-#      V
-#     pstops
-#      |
-#      V
-# APPLICATION/VND.CUPS-POSTSCRIPT
-#      |
-#      V
-#     pstoraster   # as shipped with CUPS, independent from any Ghostscipt
-#      |           # installation on the system
-#      |  (= "postscipt interpreter")
-#      V
-# APPLICATION/VND.CUPS-RASTER
-#      |
-#      V
-#     rastertosomething  (e.g. Gimp-Print filters may be plugged in here)
-#      |   (= "raster driver")
-#      V
-# SOMETHING-DEVICE-SPECIFIC
-#      |
-#      V
-#     backend
-#
-#
-# ESP PrintPro has some enhanced "rastertosomething" filters as compared to
-# CUPS, and also a somewhat improved "pstoraster" filter.
-#
-# NOTE: Gimp-Print and some other 3rd-Party-Filters (like TurboPrint) to
-#       CUPS and ESP PrintPro plug-in where rastertosomething is noted.
-#
-#########################################################################
-
    -#########################################################################
-#
-# This is how "cupsomatic" comes into play:
-# =========================================
-#
-# SOMETHNG-FILEFORMAT
-#      |
-#      V
-#    somethingtops
-#      |
-#      V
-# APPLICATION/POSTSCRIPT
-#      |
-#      V
-#    pstops
-#      |
-#      V
-# APPLICATION/VND.CUPS-POSTSCRIPT ----------------+
-#      |                                          V
-#      V                                         cupsomatic
-#    pstoraster                                  (constructs complicated
-#      |  (= "postscipt interpreter")            Ghostscript commandline
-#      |                                         to let the file be
-#      V                                         processed by a
-# APPLICATION/VND.CUPS-RASTER                    "-sDEVICE=s.th."
-#      |                                         call...)
-#      V                                          |
-#    rastertosomething                            V
-#      |    (= "raster driver")     +-------------------------+
-#      |                            | Ghostscript at work.... |
-#      V                            |                         |
-# SOMETHING-DEVICE-SPECIFIC         *-------------------------+
-#      |                                          |
-#      V                                          |
-#    backend <------------------------------------+
-#      |
-#      V
-#    THE PRINTER
-#
-#
-# Note, that cupsomatic "kidnaps" the printfile after the
-# "APPLICATION/VND.CUPS-POSTSCRPT" stage and deviates it gh
-# the CUPS-external, systemwide Ghostscript installation, bypassing the
-# "pstoraster" filter (therefore also bypassing the CUPS-raster-drivers
-# "rastertosomething", and hands the rasterized file directly to the CUPS
-# backend...
-#
-# cupsomatic is not made by the CUPS developers. It is an independent
-# contribution to printing development, made by people from
-# Linuxprinting.org. (see also http://www.cups.org/cups-help.html)
-#
-# NOTE: Gimp-Print and some other 3rd-Party-Filters (like TurboPrint) to
-#       CUPS and ESP PrintPro plug-in where rastertosomething is noted.
-#
-#########################################################################
-
    -#########################################################################
-#
-# And this is how it works for ESP PrintPro from 4.3:
-# ===================================================
-#
-# SOMETHNG-FILEFORMAT
-#      |
-#      V
-#     somethingtops
-#      |
-#      V
-# APPLICATION/POSTSCRIPT
-#      |
-#      V
-#     pstops
-#      |
-#      V
-# APPLICATION/VND.CUPS-POSTSCRIPT
-#      |
-#      V
-#     gsrip
-#      |  (= "postscipt interpreter")
-#      V
-# APPLICATION/VND.CUPS-RASTER
-#      |
-#      V
-#     rastertosomething  (e.g. Gimp-Print filters may be plugged in here)
-#      |   (= "raster driver")
-#      V
-# SOMETHING-DEVICE-SPECIFIC
-#      |
-#      V
-#     backend
-#
-# NOTE: Gimp-Print and some other 3rd-Party-Filters (like TurboPrint) to
-#       CUPS and ESP PrintPro plug-in where rastertosomething is noted.
-#
-#########################################################################
-
    -#########################################################################
-#
-# This is how "cupsomatic" would come into play with ESP PrintPro:
-# ================================================================
-#
-#
-# SOMETHNG-FILEFORMAT
-#      |
-#      V
-#    somethingtops
-#      |
-#      V
-# APPLICATION/POSTSCRIPT
-#      |
-#      V
-#    pstops
-#      |
-#      V
-# APPLICATION/VND.CUPS-POSTSCRIPT ----------------+
-#      |                                          V
-#      V                                         cupsomatic
-#    gsrip                                       (constructs complicated
-#      |  (= "postscipt interpreter")            Ghostscript commandline
-#      |                                         to let the file be
-#      V                                         processed by a
-# APPLICATION/VND.CUPS-RASTER                    "-sDEVICE=s.th."
-#      |                                         call...)
-#      V                                          |
-#    rastertosomething                            V
-#      |   (= "raster driver")      +-------------------------+
-#      |                            | Ghostscript at work.... |
-#      V                            |                         |
-# SOMETHING-DEVICE-SPECIFIC         *-------------------------+
-#      |                                          |
-#      V                                          |
-#    backend <------------------------------------+
-#      |
-#      V
-#    THE PRINTER
-#
-# NOTE: Gimp-Print and some other 3rd-Party-Filters (like TurboPrint) to
-#       CUPS and ESP PrintPro plug-in where rastertosomething is noted.
-#
-#########################################################################
-
    -#########################################################################
-#
-# And this is how it works for CUPS from 1.1.15:
-# ==============================================
-#
-# SOMETHNG-FILEFORMAT
-#      |
-#      V
-#     somethingtops
-#      |
-#      V
-# APPLICATION/POSTSCRIPT
-#      |
-#      V
-#     pstops
-#      |
-#      V
-# APPLICATION/VND.CUPS-POSTSCRIPT-----+
-#                  +------------------v------------------------------+
-#                  | Ghostscript                                     |
-#                  | at work...                                      |
-#                  | (with                                           |
-#                  | "-sDEVICE=cups")                                |
-#                  |                                                 |
-#                  |         (= "postscipt interpreter")             |
-#                  |                                                 |
-#                  +------------------v------------------------------+
-#                                     |
-# APPLICATION/VND.CUPS-RASTER >-------+
-#      |
-#      V
-#     rastertosomething
-#      |   (= "raster driver")
-#      V
-# SOMETHING-DEVICE-SPECIFIC
-#      |
-#      V
-#     backend
-#
-#
-# NOTE: since version 1.1.15 CUPS "outsourced" the pstoraster process to
-#       Ghostscript. GNU Ghostscript needs to be patched to handle the
-#       CUPS requirement; ESP Ghostscript has this builtin. In any case,
-#       "gs -h" needs to show up a "cups" device. pstoraster is now a
-#       calling an appropriate "gs -sDEVICE=cups..." commandline to do
-#       the job. It will output "application/vnd.cup-raster", which will
-#       be finally processed by a CUPS raster driver "rastertosomething"
-#       Note the difference to "cupsomatic", which will not output
-#       CUPS-raster, but a final version of the printfile, ready to be
-#       sent to the printer. cupsomatic also doesn't use the "cups"
-#       devicemode in Ghostscript, but one of the classical devicemodes....
-#
-# NOTE: Gimp-Print and some other 3rd-Party-Filters (like TurboPrint) to
-#       CUPS and ESP PrintPro plug-in where rastertosomething is noted.
-#
-#########################################################################
-
    -#########################################################################
-#
-# And this is how it works for CUPS from 1.1.15, with cupsomatic included:
-# ========================================================================
-#
-# SOMETHNG-FILEFORMAT
-#      |
-#      V
-#     somethingtops
-#      |
-#      V
-# APPLICATION/POSTSCRIPT
-#      |
-#      V
-#     pstops
-#      |
-#      V
-# APPLICATION/VND.CUPS-POSTSCRIPT-----+
-#                  +------------------v------------------------------+
-#                  | Ghostscript        . Ghostscript at work....    |
-#                  | at work...         . (with "-sDEVICE=           |
-#                  | (with              .            s.th."          |
-#                  | "-sDEVICE=cups")   .                            |
-#                  |                    .                            |
-#                  | (CUPS standard)    .      (cupsomatic)          |
-#                  |                    .                            |
-#                  |          (= "postscript interpreter")           |
-#                  |                    .                            |
-#                  +------------------v--------------v---------------+
-#                                     |              |
-# APPLICATION/VND.CUPS-RASTER >-------+              |
-#      |                                             |
-#      V                                             |
-#     rastertosomething                              |
-#      |   (= "raster driver")                       |
-#      V                                             |
-# SOMETHING-DEVICE-SPECIFIC >------------------------+
-#      |
-#      V
-#     backend
-#
-#
-# NOTE: Gimp-Print and some other 3rd-Party-Filters (like TurboPrint) to
-#       CUPS and ESP PrintPro plug-in where rastertosomething is noted.
-#
-##########################################################################
-

    Trouble Shooting Guidelines to fix typical Samba printing -Problems

    -This is a short description of how to debug printing problems -with Samba. This describes how to debug problems with printing from -a SMB client to a Samba server, not the other way around. -

    Win9x client can't install driver

    For Win9x clients require the printer names to be 8 -chars (or "8 plus 3 chars suffix") max; otherwise the driver files +set up printer "winprinter" on CUPS, you need to have a "driver" for +it. Essentially this means to convert the print data on the CUPS/Samba +host to a format that the printer can digest (the Windows host is +unable to convert any files you may send). This also means you should +be able to print to the printer if it were hooked directly at your +Samba/CUPS host. For troubleshooting purposes, this is what you +should do, to determine if that part of the process chain is in +order. Then proceed to fix the network connection/authentication to +the Windows host, etc. +

    +To install a printer with the smb backend on CUPS, use this command: +

    +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 +for: you can include the required parameters as part of the +smb:// device-URI. Like this: +

    • smb://WORKGROUP/WINDOWSNETBIOSNAME/printersharename

    • smb://username:password@WORKGROUP/WINDOWSNETBIOSNAME/printersharename

    • smb://username:password@WINDOWSNETBIOSNAME/printersharename

    +Note that the device-URI will be visible in the process list of the +Samba server (e.g. when someone uses the ps -aux +command on Linux), even if the username and passwords are sanitized +before they get written into the log files. So this is an inherently +insecure option. However it is the only one. Don't use it if you want +to protect your passwords. Better share the printer in a way that +doesn't require a password! 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 don't necessarily need to have smbd running +(but who wants that? :-). +

    More CUPS filtering Chains

    +The following diagrams reveal how CUPS handles print jobs. +

    Figure 19.17. Filtering chain 1

    Filtering chain 1

    Figure 19.18. Filtering chain with cupsomatic

    Filtering chain with cupsomatic

    Note

    +Gimp-Print and some other 3rd-Party-Filters (like TurboPrint) to +CUPS and ESP PrintPro plug-in where rastertosomething is noted. +

    Common Errors

    Win9x client can't install driver

    For Win9x clients require the printer names to be 8 +chars (or "8 plus 3 chars suffix") max; otherwise the driver files won't get transferred when you want to download them from -Samba.

    testparm

    Run testparm: It will tell you if -smb.conf parameters are in the wrong -section. Many people have had the "printer admin" parameter in the -[printers] section and experienced -problems. "testparm" will tell you if it sees -this.

    "cupsaddsmb" keeps asking for a root password in a -neverending loop

    Have you security = user? Have +Samba.

    "cupsaddsmb" keeps asking for root password in + neverending loop

    Have you security = user? Have you used smbpasswd to give root a Samba account? You can do 2 things: open another terminal and execute smbpasswd -a root to create the account, and continue with entering the password into the first terminal. Or break out of the loop by hitting ENTER twice (without trying to type a -password).

    "cupsaddsmb" gives "No PPD file for printer..." -message (but I swear there is one!)

    • Have you enabled printer sharing on CUPS? This means: +password).

    "cupsaddsmb" gives "No PPD file for printer..." + message while PPD file is present

    Have you enabled printer sharing on CUPS? This means: do you have a <Location /printers>....</Location> section in CUPS server's cupsd.conf which doesn't deny access to -the host you run "cupsaddsmb" from? It could be +the host you run "cupsaddsmb" from? It could be an issue if you use cupsaddsmb remotely, or if you use it with a --h parameter: cupsaddsmb -H -sambaserver -h cupsserver -v printername. -

  • Is your -"TempDir" directive in +-h parameter: cupsaddsmb -H + sambaserver -h cupsserver -v printername. +

    Is your +"TempDir" directive in cupsd.conf set to a valid value and is it writeable? -

    • I can't connect client 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?

    I can't reconnect to Samba under a new account -from Win2K/XP

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

    Can't reconnect to Samba under new account + from Win2K/XP

    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 won't be any byte transfered on the wire to Samba, but still you'll see a stupid error message which makes you think that Samba has denied access. Use @@ -11751,73 +10987,71 @@ message which makes you think that Samba has denied access. Use PIDs. You still can't re-connect and get the dreaded You can't connect with a second account from the same machine message, as soon as you are trying? And you -don't see any single byte arriving at Samba (see logs; use "ethereal") +don't see any single byte arriving at Samba (see logs; use "ethereal") indicating a renewed connection attempt? Shut all Explorer Windows. This makes Windows forget what it has cached in its memory as established connections. Then re-connect as the right user. Best method is to use a DOS terminal window and first -do net use z: \\SAMBAHOST\print$ /user:root. Check +do net use z: \\GANDALF\print$ /user:root. Check with smbstatus that you are connected under a -different account. Now open the "Printers" folder (on the Samba server +different account. Now open the "Printers" folder (on the Samba server in the Network Neighbourhood), right-click the printer in question and select -Connect...

    Avoid being connected to the Samba server as the -"wrong" user

    You see per smbstatus that you are -connected as user "nobody"; while you wanted to be "root" or -"printeradmin"? This is probably due to map to guest = bad -user, which silently connects you under the guest account, +Connect...

    Avoid being connected to the Samba server as the + "wrong" user

    You see per smbstatus that you are +connected as user "nobody"; while you wanted to be "root" or +"printeradmin"? This is probably due to +map to guest = bad user, which silently connects 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 on -NT/2K/XP clients gives problems

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

    I can't use "cupsaddsmb"on a 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).

    I deleted a printer on Win2K; but I still see -its driver

    Deleting a printer on the client won't delete the +map to guest, if you want to prevent +this.

    Upgrading to CUPS drivers from Adobe drivers on + NT/2K/XP clients gives problems

    First delete all "old" Adobe-using printers. Then +delete all "old" Adobe drivers. (On Win2K/XP, right-click in +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 +this way: cupsaddsmb -U DOMAINNAME\\root -v +printername> (note the two backslashes: the first one is +required to "escape" the second one).

    Deleted Win2K printer driver is still shown

    Deleting a printer on the client won't 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 +"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.

    Win2K/XP "Local Security -Policies"

    Local Security Policies may not -allow the installation of unsigned drivers. "Local Security Policies" +other printer uses the same driver.

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

    WinXP clients: "Administrator can not install -printers for all local users"

    Windows XP handles SMB printers on a "per-user" basis. +all.

    WinXP clients: "Administrator can not 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. To have a printer available for everybody, you might want to use the built-in IPP client capabilities of WinXP. Add a printer with the print path of http://cupsserver:631/printers/printername. -Still looking into this one: maybe a "logon script" could +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 (re-named to +users.

    "Print Change Notify" functions on + NT-clients

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

    WinXP-SP1

    WinXP-SP1 introduced a Point and Print +XP).

    WinXP-SP1

    WinXP-SP1 introduced a Point and Print Restriction Policy (this restriction doesn't apply to -"Administrator" or "Power User" groups of users). In Group Policy -Object Editor: go to User Configuration --> -Administrative Templates --> Control Panel --> +"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 in order to make -driver downloads from Samba possible.

    I can't set and save default print options for all -users on Win2K/XP

    How are you doing it? I bet the wrong way (it is not +driver downloads from Samba possible.

    Print options for all users can't be set on Win2K/XP

    How are you doing it? I bet the wrong way (it is not very easy to find out, though). There are 3 different ways to bring you to a dialog that seems to set everything. All three dialogs look the same. 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: -

    1. The first "wrong" way: +

      1. The first "wrong" way:

        1. Open the Printers folder.

        2. Right-click on the printer @@ -11825,7 +11059,7 @@ folder.

        3. Right-click on the printer select in context menu Printing Preferences...

        4. Look at this dialog closely and remember what it looks like.

        -

      2. The second "wrong" way: +

      3. The second "wrong" way:

        1. Open the Printers folder.

        2. Right-click on the printer (remoteprinter on @@ -11834,29 +11068,29 @@ cupshost) and select in the context menu tab

        3. Click on the button Printing Preferences...

        4. A new dialog opens. Keep this dialog open and go back to the parent dialog.

        -

      4. The third, the "correct" way: (should you do +

      5. The third, the "correct" way: (should you do this from the beginning, just carry out steps 1. and 2. from second -"way" above) +"way" above)

        1. Click on the Advanced -tab. (Hmmm... if everything is "Grayed Out", then you are not logged +tab. (Hmmm... if everything is "Grayed Out", then you are not logged in as a user with enough privileges).

        2. Click on the Printing Defaults... button.

        3. On any of the two new tabs, click on the Advanced... button.

        4. A new dialog opens. Compare this one to the other, -identical looking one from "B.5" or A.3".

        +identical looking one from "B.5" or A.3".

    Do you see any difference? I don't either... However, only the last -one, which you arrived at with steps "C.1.-6." will save any settings +one, which you arrived at with steps "C.1.-6." will save any settings permanently and be the defaults for new users. If you want all clients to get the same defaults, you need to conduct these steps as -Administrator (printer admin in +Administrator (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. -above).

    What are the most common blunders in driver -settings on Windows clients?

    Don't use Optimize for +above).

    Most common blunders in driver + settings on Windows clients

    Don't use Optimize for Speed: use Optimize for Portability instead (Adobe PS Driver) Don't use Page Independence: No: always @@ -11868,91 +11102,63 @@ 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.

    I can't make cupsaddsmb work -with newly installed printer

    Symptom: the last command of +there is a choice.

    cupsaddsmb does not work + with newly installed printer

    Symptom: the last command of cupsaddsmb doesn't complete successfully: 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 +"recognized" by Samba. Did it show up in Network Neighbourhood? 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.

    My permissions on +again.

    Permissions on /var/spool/samba/ get reset after each -reboot

    Have you by accident set the CUPS spool directory to +reboot

    Have you 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] +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] +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.

    My printers work fine: just the printer named "lp" +printing will not work reliably.

    Printer named "lp" intermittently swallows jobs and spits out completely different -ones

    It is a very 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 +ones

    It is a very 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 loadbalancing the jobs across them in a round-robin fashion. Chances -are high that someone else has an "lp" named printer too. You may +are high that someone else has an "lp" named printer too. You may receive his jobs and send your own to his device unwittingly. To have tight control over the printer names, set BrowseShortNames -No. It will present any printer as "printername@cupshost" +No. It will present any printer as "printername@cupshost" then, giving you a better control over what may happen in a large -networked environment.

    How do I "watch" my Samba server?

    You can use tail -f -/var/log/samba/log.smbd (you may need a different path) to -see a live scrolling of all log messages. smbcontrol smbd -debuglevel tells you which verbosity goes into the -logs. smbcontrol smbd debug 3 sets the verbosity to -a quite high level (you can choose from 0 to 10 or 100). This works -"on the fly", without the need to restart the smbd daemon. Don't use -more than 3 initially; or you'll drown in an ocean of -messages.

    I can't use Samba from my WinXP Home box, while -access from WinXP Prof works flawlessly

    You have our condolences! WinXP home has been -completely neutered by Microsoft as compared to WinXP Prof: you can -not log into a WinNT domain. It cannot join a Win NT domain as a -member server. While it is possible to access domain resources, users -don't have "single sign-on". They need to supply username and password -each time they connect to a resource. Logon scripts and roaming -profiles are not supported. It can serve file and print shares; but -only in "share-mode security" level. It can not use "user-mode -security" (what Windows 95/98/ME still can -do).

    Where do I find the Adobe PostScript driver files -I need for "cupsaddsmb"?

    Use smbclient to connect to any +networked environment.

    Location of Adobe PostScript driver files necessary 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 website.

    An Overview of the CUPS Printing Processes

    -

    Figure 19.15. CUPS Printing Overview

    CUPS Printing Overview

    -

    Chapter 20. Stackable VFS modules

    Jelmer R. Vernooij

    The Samba Team

    John H. Terpstra

    Samba Team

    Tim Potter

    Simo Sorce

    original vfs_skel README

    Alexander Bokovoy

    original vfs_netatalk docs

    Stefan Metzmacher

    Update for multiple modules

    Table of Contents

    Features and Benefits
    Discussion
    Included modules
    audit
    extd_audit
    fake_perms
    recycle
    netatalk
    VFS modules available elsewhere
    DatabaseFS
    vscan
    Common Errors

    Features and Benefits

    +files from the Adobe website.

    An Overview of the CUPS Printing Processes

    Figure 19.19. CUPS Printing Overview

    CUPS Printing Overview

    Chapter 20. Stackable VFS modules

    Jelmer R. Vernooij

    The Samba Team

    John H. Terpstra

    Samba Team

    Tim Potter

    Simo Sorce

    original vfs_skel README

    Alexander Bokovoy

    original vfs_netatalk docs

    Stefan Metzmacher

    Update for multiple modules

    Table of Contents

    Features and Benefits
    Discussion
    Included modules
    audit
    extd_audit
    fake_perms
    recycle
    netatalk
    VFS modules available elsewhere
    DatabaseFS
    vscan

    Features and Benefits

    Since Samba-3, there is support for stackable VFS(Virtual File System) modules. Samba passes each request to access the unix file system thru the loaded VFS modules. This chapter covers all the modules that come with the samba source and references to some external modules. -

    Discussion

    +

    Discussion

    If not supplied with your platform distribution binary Samba package you may have problems to compile 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 +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: -

    -[audit]
-        comment = Audited /data directory
-        path = /data
-        vfs objects = audit recycle
-        writeable = yes
-        browseable = yes
-

    +

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

    @@ -11964,46 +11170,52 @@ directory in the root directory of the samba installation (usually Some modules can be used twice for the same share. This can be done using a configuration similar to the one below. -

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

    -

    extd_audit

    +

    • share

    • connect/disconnect

    • directory opens/create/remove

    • file open/close/rename/unlink/chmod

    +

    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 file/s. The loglevel for this module is set in the smb.conf file.

    The logging information that will be written to the smbd log file is controlled by - the log level parameter in smb.conf. The + the log level parameter in smb.conf. The following information will be recorded: -

    Table 20.1. Extended Auditing Log Information

    Log LevelLog Details - File and Directory Operations
    0Creation / Deletion
    1Create / Delete / Rename / Permission Changes
    2Create / Delete / Rename / Perm Change / Open / Close

    fake_perms

    +

    Table 20.1. Extended Auditing Log Information

    Log LevelLog Details - File and Directory Operations
    0Creation / Deletion
    1Create / Delete / Rename / Permission Changes
    2Create / Delete / Rename / Perm Change / Open / Close

    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 will report to the client that the Profile files and directories are writable. 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. When used any unlink call will be intercepted and files moved to the recycle - directory instead of being deleted. + directory instead of being deleted. This gives the same + effect as the "Recycle Bin" on Windows computers.

    Supported options: -

    recycle:repository

    FIXME

    recycle:keeptree

    FIXME

    recycle:versions

    FIXME

    recycle:touch

    FIXME

    recycle:maxsize

    FIXME

    recycle:exclude

    FIXME

    recycle:exclude_dir

    FIXME

    recycle:noversions

    FIXME

    -

    netatalk

    +

    recycle:repository

    Relative path of the directory where deleted files should be moved to

    recycle:keeptree

    Specifies whether the directory structure should + be kept or if the files in the directory that is being + deleted should be kept seperately 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: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 deleted in the regular way. +

    recycle:noversions

    Opposite of recycle:versions. If both options are specified, this one takes precedence.

    +

    netatalk

    A netatalk module, that will ease co-existence of samba and netatalk file sharing services.

    Advantages compared to the old netatalk module: -

    it doesn't care about creating of .AppleDouble forks, just keeps them in sync
    if a share in smb.conf doesn't contain .AppleDouble item in hide or veto list, it will be added automatically

    -

    VFS modules available elsewhere

    +

    • it doesn't care about creating of .AppleDouble forks, just keeps them in sync

    • if a share in smb.conf doesn't contain .AppleDouble item in hide or veto list, it will be added automatically

    +

    VFS modules available elsewhere

    This section contains a listing of various other VFS modules that have been posted but don't currently reside in the Samba CVS tree for one reason or another (e.g. it is easy for the maintainer @@ -12011,14 +11223,14 @@ 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: http://www.css.tayloru.edu/~elorimer/databasefs/index.php

    By Eric Lorimer.

    I have created a VFS module which implements a fairly complete read-only filesystem. It presents information from a database as a filesystem in a modular and generic way to allow different databases to be used (originally designed for organizing MP3s under directories such as - "Artists," "Song Keywords," etc... I have since applied it to a student + "Artists," "Song Keywords," etc... I have since applied it to a student roster database very easily). The directory structure is stored in the database itself and the module makes no assumptions about the database structure beyond the table it requires to run. @@ -12026,25 +11238,47 @@ should be implied due to its presence here. Any feedback would be appreciated: comments, suggestions, patches, etc... If nothing else, hopefully it might prove useful for someone else who wishes to create a virtual filesystem. -

    vscan

    URL: http://www.openantivirus.org/

    +

    vscan

    URL: http://www.openantivirus.org/

    samba-vscan is a proof-of-concept module for Samba, which uses the VFS (virtual file system) features of Samba 2.2.x/3.0 alphaX. Of course, Samba has to be compiled with VFS support. samba-vscan supports various virus scanners and is maintained by Rainer Link. -

    Common Errors

    -There must be some gotchas we should record here! Jelmer??? -

    Chapter 21. Integrated Logon Support using Winbind

    Tim Potter

    Samba Team

    Andrew Tridgell

    Samba Team

    Naag Mummaneni

    Jelmer R. Vernooij

    The Samba Team

    John H. Terpstra

    Samba Team

    27 June 2002

    Table of Contents

    Features and Benefits
    Introduction
    What Winbind Provides
    Target Uses
    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

    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. We present - winbind, a component of the Samba suite - of programs as a solution to the unified logon problem. Winbind - uses a UNIX implementation - of Microsoft RPC calls, Pluggable Authentication Modules, and the Name - Service Switch to allow Windows NT domain users to appear and operate - as UNIX users on a UNIX machine. This paper describes the winbind - system, explaining the functionality it provides, how it is configured, - and how it works internally.

    Introduction

    It is well known that UNIX and Microsoft Windows NT have +

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

    27 June 2002

    Table of Contents

    Features and Benefits
    Introduction
    What Winbind Provides
    Target Uses
    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

    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 + solves the unified logon problem. Winbind uses a UNIX implementation of Microsoft + RPC calls, Pluggable Authentication Modules, and the Name Service Switch to + allow Windows NT domain users to appear and operate as UNIX users on a UNIX + machine. This chapter describes the winbind system, explaining the functionality + it provides, how it is configured, and how it works internally. +

    + Winbind provides three separate functions: +

    • + Authentication of user credentials (via PAM) +

    • + Identity resolution (via NSS)` +

    • + Windindd 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 stored the UID/GID + allocated from the idmap uid/gid range that it has mapped to the NT SID. + If idmap backend has been specified as ldapsam:url + then instead of using a local mapping winbindd will obtain this information + from the LDAP database. +

    Note

    + If winbindd is not running, then 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. +

    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 @@ -12065,7 +11299,7 @@ There must be some gotchas we should record here! Jelmer??? 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

    Winbind unifies UNIX and Windows NT account management by + problem.

    What Winbind Provides

    Winbind unifies UNIX and Windows NT account management by allowing a UNIX box to become a full member of a 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 @@ -12078,7 +11312,7 @@ There must be some gotchas we should record here! Jelmer??? (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 use "native" UNIX names. They can chown files + names as they would use "native" UNIX names. They can chown files so that 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 @@ -12089,7 +11323,7 @@ There must be some gotchas we should record here! Jelmer??? to provide authentication via a 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

    Winbind is targeted at organizations that have an + 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 organizations to deploy UNIX workstations without having to @@ -12099,12 +11333,12 @@ There must be some gotchas we should record here! Jelmer??? 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.

    How Winbind Works

    The winbind system is designed around a client/server + the appliance into the domain.

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

    The technologies used to implement winbind are described - in detail below.

    Microsoft Remote Procedure Calls

    Over the last few years, efforts have been underway + in detail below.

    Microsoft Remote Procedure Calls

    Over the last few years, efforts have been underway by various Samba Team members to decode various aspects of the Microsoft Remote Procedure Call (MSRPC) system. This system is used for most network related operations between @@ -12117,7 +11351,7 @@ There must be some gotchas we should record here! Jelmer??? 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

    + NT account information onto UNIX user and group names.

    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. @@ -12126,7 +11360,7 @@ There must be some gotchas we should record here! Jelmer??? same way as a Win2k client would, and in so doing provide a much more efficient and effective winbind implementation. -

    Name Service Switch

    The Name Service Switch, or NSS, is a feature that is +

    Name Service Switch

    The Name Service Switch, or 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 @@ -12147,8 +11381,8 @@ There must be some gotchas we should record here! Jelmer??? When a UNIX application makes a request to do a lookup the C library looks in /etc/nsswitch.conf for a line which matches the service type being requested, for - example the "passwd" service type is used when user or group names - are looked up. This config line species which implementations + example the "passwd" service type is used when user or group names + are looked up. This config line specifies which implementations of that service should be tried and in what order. If the passwd config line is:

     passwd: files example
@@ -12161,9 +11395,9 @@ passwd: files example
 		result to the application.
    This NSS interface provides a very 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 
+		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, also known as PAM, + resolve user and group names.

    Pluggable Authentication Modules

    Pluggable Authentication Modules, also known as PAM, is 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 @@ -12188,7 +11422,7 @@ passwd: files example is copied to /lib/security/ and the PAM control files for relevant services are updated to allow authentication via winbind. See the PAM documentation - for more details.

    User and Group ID Allocation

    When a user or group is created under Windows NT + for more details.

    User and Group ID Allocation

    When a user or group is created under Windows NT is it allocated a numerical relative identifier (RID). This is slightly different to UNIX which has a range of numbers that are used to identify users, and the same range in which to identify @@ -12201,7 +11435,7 @@ passwd: files example 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

    An active system can generate a lot of user and group + RIDs are mapped to UNIX IDs in a consistent way.

    Result Caching

    An active 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 @@ -12212,23 +11446,12 @@ passwd: files example 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

    -Many thanks to John Trostel jtrostel@snapserver.com -for providing the HOWTO for this section. -

    -This HOWTO describes how to get winbind services up and running -to control access and authenticate users on your Linux box using -the winbind services which come with SAMBA 3.0. -

    Introduction

    + from the PDC.

    Installation and Configuration

    Introduction

    This section describes the procedures used to get winbind up and -running on a RedHat 7.1 system. Winbind is capable of providing access +running. Winbind is capable of providing access and authentication control for Windows Domain users through an NT or Win2K PDC for 'regular' services, such as telnet a nd ftp, as well for SAMBA services. -

    -This HOWTO has been written from a 'RedHat-centric' perspective, so if -you are using another distribution, you may have to modify the instructions -somewhat to fit the way your distribution works.

    • Why should I to this?

      This allows the SAMBA administrator to rely on the @@ -12244,7 +11467,7 @@ somewhat to fit the way your distribution works. SAMBA server, this HOWTO is for you. That said, I am no NT or PAM expert, so you may find a better or easier way to accomplish these tasks. -

    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 @@ -12271,33 +11494,18 @@ winbind modules, you should have at least the pam libraries resident on your system. For recent RedHat systems (7.1, for instance), that means pam-0.74-22. For best results, it is helpful to also install the development packages in pam-devel-0.74-22. -

    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, you will want to make sure that you have the -standard PAM package (for RedHat) which supplies the /etc/pam.d +standard PAM package which supplies the /etc/pam.d directory structure, including the pam modules are used by pam-aware services, several pam libraries, and the /usr/doc and /usr/man entries for pam. Winbind built better in SAMBA if the pam-devel package was also installed. This package includes the header files needed to compile pam-aware applications. -

    Configure and compile SAMBA

    -The configuration and compilation of SAMBA is pretty straightforward. -The first three steps may not be necessary depending upon -whether or not you have previously built the Samba binaries. -

    -root# autoconf
-root# make clean
-root# rm config.cache
-root# ./configure
-root# make
-root# make install
-

    -This will, by default, install SAMBA in /usr/local/samba. -See the main SAMBA documentation if you want to install SAMBA somewhere else. -It will also build the winbindd executable and libraries. -

    Configure nsswitch.conf and the +

    Configure nsswitch.conf and the winbind libraries on Linux and Solaris

    The libraries needed to run the winbindd daemon through nsswitch need to be copied to their proper locations, so @@ -12332,7 +11540,7 @@ is faster (and you don't need to reboot) if you do it manually:

    This makes libnss_winbind available to winbindd and echos back a check to you. -

    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 @@ -12347,45 +11555,30 @@ supports identification, but there have been success reports using the standard winbind pam module for authentication. Use caution configuring loadable authentication modules as it is possible to make it impossible to logon to the system. More information about the AIX authentication -module API can be found at "Kernel Extensions and Device Support -Programming Concepts for AIX": +module API can be found at "Kernel Extensions and Device Support +Programming Concepts for AIX": Chapter 18. Loadable Authentication Module Programming Interface and more information on administering the modules at -"System Management Guide: Operating System and Devices". -

    Configure smb.conf

    +"System Management Guide: Operating System and Devices". +

    Configure smb.conf

    Several parameters are needed in the smb.conf file to control the behavior of winbindd. Configure smb.conf These are described in more detail in the winbindd(8) man page. My smb.conf file was modified to include the following entries in the [global] section: -

    -[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 21.1. smb.conf for winbind set-up

    [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
    winbind 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

    Enter the following command to make the SAMBA server join the PDC domain, where DOMAIN is the name of your Windows domain and Administrator is a domain user who has administrative privileges in the domain.

    -root# /usr/local/samba/bin/net join -S PDC -U Administrator +root# /usr/local/samba/bin/net rpc join -S PDC -U Administrator

    -The proper response to the command should be: "Joined the domain -DOMAIN" where DOMAIN +The proper response to the command should be: "Joined the domain +DOMAIN" where DOMAIN is your DOMAIN name. -

    Start up the winbindd daemon and test it!

    +

    Start up the winbindd daemon and test it!

    Eventually, you will want to modify your smb 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 @@ -12427,8 +11620,7 @@ your PDC. For example, I get the following response: CEO+krbtgt CEO+TsInternetUser

    -Obviously, I have named my domain 'CEO' and my winbind -separator is '+'. + 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: @@ -12457,7 +11649,7 @@ directories and default shells. 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. @@ -12469,18 +11661,18 @@ startup script starts up smbd, 

     stop() {
-        KIND="SMB"
-        echo -n $"Shutting down $KIND services: "
+        KIND="SMB"
+        echo -n $"Shutting down $KIND services: "
         killproc smbd
         RETVAL=$?
         echo
-        KIND="NMB"
-        echo -n $"Shutting down $KIND services: "
+        KIND="NMB"
+        echo -n $"Shutting down $KIND services: "
         killproc nmbd
         RETVAL2=$?
         echo
-        KIND="Winbind"
-        echo -n $"Shutting down $KIND services: "
+        KIND="Winbind"
+        echo -n $"Shutting down $KIND services: "
         killproc winbindd
         RETVAL3=$?
         [ $RETVAL -eq 0 -a $RETVAL2 -eq 0 -a $RETVAL3 -eq 0 ] && \
 		 rm -f /var/lock/subsys/smb
-        echo ""
+        echo ""
         return $RETVAL
 }
-
    Solaris

    Winbind doesn't work on Solaris 9, see the Portability chapter for details.

    On Solaris, you need to modify the +

    Solaris

    Winbind doesn't work on Solaris 9, see the Portability chapter 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, @@ -12542,12 +11734,12 @@ the file could contains something like this: pid=`/usr/bin/ps -e | /usr/bin/grep -w $1 | /usr/bin/sed -e 's/^ *//' -e 's/ .*//'` - [ "$pid" != "" ] && kill $pid + [ "$pid" != "" ] && kill $pid } # Start/stop processes required for samba server - case "$1" in + case "$1" in 'start') # @@ -12572,7 +11764,7 @@ the file could contains something like this: ;; *) - echo "Usage: /etc/init.d/samba.server { start | stop }" + echo "Usage: /etc/init.d/samba.server { start | stop }" ;; esac

    @@ -12586,11 +11778,11 @@ in the script above with: 

     	/usr/local/samba/bin/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 @@ -12610,7 +11802,7 @@ your other pam security modules. On my RedHat system, this was the modules reside in /usr/lib/security.

    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: 

    @@ -12637,7 +11829,7 @@ 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.
+template homedir.
 
    
 The /etc/pam.d/ftp file can be changed 
 to allow winbind ftp access in a manner similar to the
@@ -12670,10 +11862,10 @@ same way.  It now looks like this:
 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
+
    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 that my Domain users can logon both locally as well as telnet.The following are the changes that I made.You can customize the pam.conf file as per your requirements,but @@ -12681,7 +11873,7 @@ be sure of those changes because in the worst case it will leave your system nearly impossible to boot. 

     	#
-	#ident	"@(#)pam.conf	1.14	99/09/16 SMI"
+	#ident	"@(#)pam.conf	1.14	99/09/16 SMI"
 	#
 	# Copyright (c) 1996-1999, Sun Microsystems, Inc.
 	# All Rights Reserved.
@@ -12745,15 +11937,15 @@ annoying double prompts for passwords.
 
    
 Now restart your Samba and try connecting through your application that you
 configured in the pam.conf.
-

    Conclusion

    The winbind system, through the use of the Name Service +

    Conclusion

    The winbind system, through the use of the Name Service Switch, Pluggable Authentication Modules, 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

    Winbind has a number of limitations in its current + cost of running a mixed UNIX and NT network.

    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 and IRIX operating systems, although ports to other operating + the Linux, Solaris, AIX and IRIX operating systems, although ports to other operating systems are certainly possible. For such ports to be feasible, we require the C library of the target operating system to support the Name Service Switch and Pluggable Authentication @@ -12765,11 +11957,18 @@ configured in the pam.conf. containing this information is corrupted or destroyed.

    • Currently the winbind PAM module does not take into account possible workstation and logon time restrictions that may be been set for Windows NT users, this is - instead up to the PDC to enforce.

    Chapter 22. Advanced Network Management

    John H. Terpstra

    Samba Team

    April 3 2003

    Table of Contents

    Features and Benefits
    Remote Server Administration
    Remote Desktop Management
    Remote Management from NoMachines.Com
    Network Logon Script Magic
    Adding printers without user intervention
    Common Errors

    + instead up to the PDC to enforce.

    NSCD Problem Warning

    Note

    + Do NOT under ANY circumstances run nscd on any system + on which winbind 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. +

    Chapter 22. Advanced Network Management

    John H. Terpstra

    Samba Team

    April 3 2003

    Table of Contents

    Features and Benefits
    Remote Server Administration
    Remote Desktop Management
    Remote Management from NoMachines.Com
    Network Logon Script Magic
    Adding printers without user intervention
    Common Errors

    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 makes everything work more harmoniously. A key part of every network environment solution is the ability to remotely @@ -12779,7 +11978,7 @@ network operations.

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

    Remote Server Administration

    +

    Remote Server Administration

    How do I get 'User Manager' and 'Server Manager'?

    Since I don't need to buy an NT4 Server, how do I get the 'User Manager for Domains', @@ -12793,12 +11992,12 @@ Click here to download the archived file Windows NT 4.0 version of the 'User Manager for Domains' and 'Server Manager' are available from Microsoft via ftp from ftp://ftp.microsoft.com/Softlib/MSLFILES/SRVTOOLS.EXE -

    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 solutions 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 NoMachines.Com

    +

    Remote Management from NoMachines.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. @@ -12817,7 +12016,7 @@ is the best tool in your network environment. > Any ideas/experience would be appreciated :)

    - Answer provided: Check out the new offer from NoMachine, "NX" software: + Answer provided: Check out the new offer from NoMachine, "NX" software: http://www.nomachine.com/.

    It implements a very easy-to-use interface to the remote X protocol as @@ -12830,18 +12029,18 @@ is the best tool in your network environment.

    I could test drive their (public) RedHat 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) + which popped up immediately on "mouse-over". From inside that (remote X) session I started a rdesktop session on another, a Windows XP machine. To test the performance, I played Pinball. I am proud to announce here that my score was 631750 points at first try...

    - NX performs better on my local LAN than any of the other "pure" + NX performs better on my local LAN than any of the other "pure" connection methods I am using 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 + 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 something right!

    @@ -12886,7 +12085,7 @@ is the best tool in your network environment. NoMachine are encouraging and offering help to OSS/Free Software implementations for such a frontend too, even if it means competition to them (they have written to this effect even to the LTSP, KDE and GNOME developer mailing lists) -

    Network Logon Script Magic

    +

    Network Logon Script Magic

    This section needs work. Volunteer contributions most welcome. Please send your patches or updates to John Terpstra.

    @@ -12928,31 +12127,31 @@ This is the genlogon.pl file: # Log client connection #($sec,$min,$hour,$mday,$mon,$year,$wday,$yday,$isdst) = localtime(time); ($sec,$min,$hour,$mday,$mon,$year,$wday,$yday,$isdst) = localtime(time); - open LOG, ">>/var/log/samba/netlogon.log"; - print LOG "$mon/$mday/$year $hour:$min:$sec - User $ARGV[0] logged into $ARGV[1]\n"; + open LOG, ">>/var/log/samba/netlogon.log"; + print LOG "$mon/$mday/$year $hour:$min:$sec - User $ARGV[0] logged into $ARGV[1]\n"; close LOG; # Start generating logon script - open LOGON, ">/shared/netlogon/$ARGV[0].bat"; - print LOGON "\@ECHO OFF\r\n"; + open LOGON, ">/shared/netlogon/$ARGV[0].bat"; + print LOGON "\@ECHO OFF\r\n"; # Connect shares just use by Software Development group - if ($ARGV[1] eq "SOFTDEV" || $ARGV[0] eq "softdev") + if ($ARGV[1] eq "SOFTDEV" || $ARGV[0] eq "softdev") { - print LOGON "NET USE M: \\\\$ARGV[2]\\SOURCE\r\n"; + print LOGON "NET USE M: \\\\$ARGV[2]\\SOURCE\r\n"; } # Connect shares just use by Technical Support staff - if ($ARGV[1] eq "SUPPORT" || $ARGV[0] eq "support") + if ($ARGV[1] eq "SUPPORT" || $ARGV[0] eq "support") { - print LOGON "NET USE S: \\\\$ARGV[2]\\SUPPORT\r\n"; + print LOGON "NET USE S: \\\\$ARGV[2]\\SUPPORT\r\n"; } # Connect shares just used by Administration staff - If ($ARGV[1] eq "ADMIN" || $ARGV[0] eq "admin") + If ($ARGV[1] eq "ADMIN" || $ARGV[0] eq "admin") { - print LOGON "NET USE L: \\\\$ARGV[2]\\ADMIN\r\n"; - print LOGON "NET USE K: \\\\$ARGV[2]\\MKTING\r\n"; + print LOGON "NET USE L: \\\\$ARGV[2]\\ADMIN\r\n"; + print LOGON "NET USE K: \\\\$ARGV[2]\\MKTING\r\n"; } # Now connect Printers. We handle just two or three users a little @@ -12962,13 +12161,13 @@ This is the genlogon.pl file: if ($ARGV[0] eq 'jim' || $ARGV[0] eq 'yvonne') { - print LOGON "NET USE LPT2: \\\\$ARGV[2]\\LJET3\r\n"; - print LOGON "NET USE LPT3: \\\\$ARGV[2]\\FAXQ\r\n"; + print LOGON "NET USE LPT2: \\\\$ARGV[2]\\LJET3\r\n"; + print LOGON "NET USE LPT3: \\\\$ARGV[2]\\FAXQ\r\n"; } else { - print LOGON "NET USE LPT1: \\\\$ARGV[2]\\LJET3\r\n"; - print LOGON "NET USE LPT3: \\\\$ARGV[2]\\FAXQ\r\n"; + print LOGON "NET USE LPT1: \\\\$ARGV[2]\\LJET3\r\n"; + print LOGON "NET USE LPT3: \\\\$ARGV[2]\\FAXQ\r\n"; } # All done! Close the output file. @@ -12976,7 +12175,7 @@ This is the genlogon.pl file:

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

    http://www.craigelachie.org/rhacer/ntlogon
    http://www.kixtart.org
    http://support.microsoft.com/default.asp?scid=kb;en-us;189105

    Adding printers without user intervention

    +

    http://www.craigelachie.org/rhacer/ntlogon
    http://www.kixtart.org
    http://support.microsoft.com/default.asp?scid=kb;en-us;189105

    Adding printers without user intervention

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

    @@ -12984,20 +12183,20 @@ Printers may be added automatically during logon script processing through the u

    See the documentation in the Microsoft knowledgebase article no: 189105. -

    Common Errors

    +

    Common Errors

    The information provided in this chapter has been reproduced from postings on the samba@samba.org mailing list. No implied endorsement or recommendation is offered. Administrators should conduct their own evaluation of alternatives and are encouraged to draw their own conclusions. -

    Chapter 23. 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
    Samba Editreg Toolset
    Windows NT4/200x
    Samba PDC
    System Startup and Logon Processing Overview
    Common Errors
    Policy Does Not Work

    +

    Chapter 23. 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
    Samba Editreg Toolset
    Windows NT4/200x
    Samba PDC
    System Startup and Logon Processing Overview
    Common Errors
    Policy Does Not Work

    This chapter summarises the current state of knowledge derived from personal practice and knowledge from samba mailing list subscribers. Before reproduction of posted information effort has been made to validate the information provided. Where additional information was uncovered through this validation it is provided also. -

    Features and Benefits

    +

    Features and Benefits

    When MS Windows NT3.5 was introduced the hot new topic was the ability to implement Group Policies for users and group. Then along came MS Windows NT4 and a few sites -started to adopt this capability. How do we know that? By way of the number of "booboos" +started to adopt this capability. How do we know that? By way of the number of "booboos" (or mistakes) administrators made and then requested help to resolve.

    By the time that MS Windows 2000 and Active Directory was released, administrators @@ -13013,9 +12212,9 @@ the deployment in many sites. This chapter reviews techniques and methods that c be used to exploit opportunities for automation of control over user desktops and network client workstations.

    -A tool new to Samba-3 may become an important part of the future Samba Administrators' +A tool new to Samba may become an important part of the future Samba Administrators' arsenal. The editreg tool is described in this document. -

    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 @@ -13044,13 +12243,13 @@ 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 -Implementing Profiles and Policies in Windows NT 4.0 from http://www.microsoft.com/ntserver/management/deployment/planguide/prof_policies.asp available from Microsoft. +Implementing Profiles and Policies in Windows NT 4.0 available from Microsoft. There are a large number of documents in addition to this old one that should also -be read and understood. Try searching on the Microsoft web site for "Group Policies". +be read and understood. Try searching on the Microsoft web site for "Group Policies".

    What follows is a very 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 Win98 Group Policy Editor to set Group Profiles up under Windows 9x/Me. It can be found on the Original full product Win98 installation CD under tools/reskit/netadmin/poledit. Install this using the @@ -13076,7 +12275,7 @@ here is incomplete - you are warned. grouppol.inf. Log off and on again a couple of times and see if Win98 picks up group policies. Unfortunately this needs to be done on every Win9x/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 NT Workstation. There is a Policy Editor on a NT4 @@ -13097,14 +12296,14 @@ here is incomplete - you are warned. be extracted as well. It is also possible to downloaded 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. Since the settings that were in the NTConfig.POL file were applied to the client machine registry and that apply to the hive key HKEY_LOCAL_MACHINE are permanent until explicitly reversed. This is known as tattooing. It can have serious consequences down-stream 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 allows setting of registry parameters specific to users, groups and computers (client workstations) that are members of the NT4 style domain. Such policy file will work with MS Windows 2000 / XP clients also. @@ -13141,7 +12340,7 @@ 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 Win2K / XP Policies

    +

    Administration of Win2K / 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. @@ -13167,10 +12366,10 @@ here is incomplete - you are warned. 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. -

    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 not necessary. +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 @@ -13193,20 +12392,27 @@ in a manner that works in conjunction with user profiles, the user management en MS Windows NT4/200x/XP allows per domain as well as per user account restrictions to be applied. Common restrictions that are frequently used includes:

    -

    Logon Hours
    Password Aging
    Permitted Logon from certain machines only
    Account type (Local or Global)
    User Rights

    -

    Samba Editreg Toolset

    - Describe in detail the benefits of editreg and how to use it. -

    Windows NT4/200x

    +

    • Logon Hours

    • Password Aging

    • Permitted Logon from certain machines only

    • Account type (Local or Global)

    • User Rights

    +

    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 NTUser.DAT file and can be editted using + this tool. editreg is being built with the intent to enable NTConfig.POL + files to be saved in text format and to permit the building of new NTConfig.POL files with + extended capabilities. It is proving difficult to realise this capability, so do not be surprised + if this feature does not materialise. Formal capabilities will be announced at the time that + this tool is released for production use. +

    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, the registry editor (regedt32.exe). Under MS Windows 200x/XP this is done using the Microsoft Management Console (MMC) with appropriate - "snap-ins", the registry editor, and potentially also the NT4 System and Group Policy Editor. -

    Samba PDC

    + "snap-ins", the registry editor, and potentially also the NT4 System and Group Policy Editor. +

    Samba PDC

    With a Samba Domain Controller, the new tools for managing of user account and policy information includes: smbpasswd, pdbedit, net, 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 of system and user policies following a system reboot and as part of the user logon:

    1. @@ -13215,7 +12421,7 @@ reboot and as part of the user logon:

    2. Where Active Directory is involved, an ordered list of Group Policy Objects (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 scope of applicability: local, site, domain, organizational unit, etc.

      +

      • Apply to the location of machines in a Directory

      • Apply only when settings have changed

      • Depend on configuration of scope of applicability: local, site, domain, organizational unit, etc.

      No desktop user interface is presented until the above have been processed.

    3. Execution of start-up scripts (hidden and synchronous by default). @@ -13226,7 +12432,7 @@ reboot and as part of the user logon:

    4. An ordered list of User GPOs is obtained. The list contents depends on what is configured in respect of: -

      Is user a domain member, thus subject to particular policies
      Loopback enablement, and the state of the loopback policy (Merge or Replace)
      Location of the Active Directory itself
      Has the list of GPOs changed. No processing is needed if not changed.

      +

      • Is user a domain member, thus subject to particular policies

      • Loopback enablement, and the state of the loopback policy (Merge or Replace)

      • Location of the Active Directory itself

      • Has the list of GPOs changed. No processing is needed if not changed.

    5. User Policies are applied from Active Directory. Note: There are several types.

    6. @@ -13236,18 +12442,18 @@ reboot and as part of the user logon:

    7. The User Interface as determined from the GPOs is presented. Note: In a Samba domain (like and NT4 Domain) machine (system) policies are applied at start-up, User policies are applied at logon. -

    Common Errors

    +

    Common Errors

    Policy related problems can be very difficult to diagnose and even more difficult to rectify. The following collection demonstrates only basic issues. -

    Policy Does Not Work

    -Question: We have created the config.pol file and put it in the NETLOGON share. +

    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 don't see it. IT worked fine with Win 98 but does not -work any longer since we upgraded to Win XP Pro. Any hints? +work any longer since we upgraded to Win XP Pro. Any hints?”

    -ANSWER: Policy files are NOT portable between Windows 9x / Me and MS Windows NT4 / 200x / XP based +Policy files are NOT portable between Windows 9x / Me and MS Windows NT4 / 200x / XP based platforms. You need to use the NT4 Group Policy Editor to create a file called NTConfig.POL so that it is in the correct format for your MS Windows XP Pro clients. -

    Chapter 24. 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
    Sharing Profiles between W9x/Me and NT4/200x/XP workstations
    Profile Migration from Windows NT4/200x Server to Samba
    Mandatory profiles
    Creating/Managing Group Profiles
    Default Profile for Windows Users
    MS Windows 9x/Me
    MS Windows NT4 Workstation
    MS Windows 200x/XP
    Common Errors
    How does one set up roaming profiles for just one (or a few) user/s or group/s?
    Can NOT use Roaming Profiles
    Changing the default profile

    Features and Benefits

    +

    Chapter 24. 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
    Sharing Profiles between W9x/Me and NT4/200x/XP workstations
    Profile Migration from Windows NT4/200x Server to Samba
    Mandatory profiles
    Creating/Managing Group Profiles
    Default Profile for Windows Users
    MS Windows 9x/Me
    MS Windows NT4 Workstation
    MS Windows 200x/XP
    Common Errors
    Setting up roaming profiles for just a few user's or group's?
    Can NOT use Roaming Profiles
    Changing the default profile

    Features and Benefits

    Roaming Profiles are feared by some, hated by a few, loved by many, and a Godsend for some administrators.

    @@ -13260,7 +12466,7 @@ problem to others. In particular, users of mobile computing tools, where often t be a sustained network connection, are often better served by purely Local Profiles. This chapter provides information to help the Samba administrator to deal with those situations also. -

    Roaming Profiles

    Warning

    +

    Roaming Profiles

    Warning

    Roaming profiles support is different for Win9x / Me and Windows NT4/200x.

    Before discussing how to configure roaming profiles, it is useful to see how @@ -13273,21 +12479,17 @@ 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

    To support Windows NT4/200x clients, in the [global] section of smb.conf set the following (for example):

    -

    -	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 user name

    The default for this option is \\%N\%U\profile, @@ -13300,31 +12502,26 @@ semantics of %L and %N, as well as %U and %u. MS Windows NT/2K clients at times do not disconnect a connection to a server between logons. It is recommended to NOT use the homes meta-service name as part of the profile share path. -

    Windows 9x / Me User Profiles

    - To support Windows 9x / Me clients, you must use the logon home parameter. Samba has +

    Windows 9x / Me User Profiles

    + To support Windows 9x / Me clients, you must use the logon home parameter. Samba has now been fixed so that 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 Win9x / 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 (thus 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 9x / Me and Windows NT4/200x User Profiles

    +specified \\%L\%U for logon home. +

    Mixed Windows 9x / Me and Windows NT4/200x User Profiles

    You can support profiles for both Win9X and WinNT clients by setting both the -logon home and logon path parameters. For example: -

    -	logon home = \\%L\%u\.profiles
-	logon path = \\%L\profiles\%u
-

    Disabling Roaming Profile Support

    +logon home and logon path parameters. For example: +

    logon home = \\%L\%u\.profiles
    logon path = \\%L\profiles\%u

    Disabling Roaming Profile Support

    A question often asked is “How may I enforce use of local profiles?” or “How do I disable Roaming Profiles?”

    @@ -13332,13 +12529,11 @@ There are three ways of doing this:

    In smb.conf

    Affect the following settings and ALL clients will be forced to use a local profile: - 

    -			logon home =
-			logon path =
-

    +

    logon home
    logon path

    MS Windows Registry:

    By using the Microsoft Management Console 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: + 

     	Local Computer Policy\
 		Computer Configuration\
@@ -13361,15 +12556,15 @@ profiles.
 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 stored in c:\windows\profiles\username on subsequent logins, taking the most recent from 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 +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 @@ -13402,11 +12597,11 @@ domain and profiles downloaded from it, if that domain logon server supports it), user name and user's password.

    Once the user has been successfully validated, the Windows 9x / Me machine -will inform you that The user has not logged on before' and asks you - if you wish to save the user's preferences? Select yes. +will inform you that The user has not logged on before and asks you +Do you wish to save the user's preferences?. Select yes.

    Once the Windows 9x / Me client comes up with the desktop, you should be able -to examine the contents of the directory specified in the logon path +to examine the contents of the directory specified in the logon path on the samba server and verify that the Desktop, Start Menu, Programs and Nethood folders have been created.

    @@ -13420,14 +12615,14 @@ the newest folders and short-cuts 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 the remote profile. Basically, if -you have any errors reported by the Windows 9x / Me machine, check the Unix file +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 then next logs in, -they will be told that they are logging in "for the first time". -

    Warning

    +they will be told that they are logging in "for the first time". +

    Warning

    Before deleting the contents of the directory listed in the ProfilePath (this is likely to be c:\windows\profiles\username), ask them if they @@ -13437,8 +12632,8 @@ they will be told that they are logging in "for the first time".

    This will have the effect of removing the local (read-only hidden system file) user.DAT in their profile directory, as well as the - local "desktop", "nethood", "start menu" and "programs" folders. -

    1. + local "desktop", "nethood", "start menu" and "programs" folders. +

    1. instead of logging in under the [user, password, domain] dialog, press escape.

    2. @@ -13455,7 +12650,7 @@ they will be told that they are logging in "for the first time".

    3. log off the windows 9x / Me client.

    4. - check the contents of the profile path (see logon path described + check the contents of the profile path (see logon path described above), and delete the user.DAT or user.MAN file for the user, making a backup if required.

    @@ -13467,14 +12662,14 @@ If you have access to an Windows NT4/200x server, then first set up roaming prof 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. +through the logon path parameter.

    There is a parameter that is now available for use with NT Profiles: -logon drive. This should be set to H: or any other drive, and -should be used in conjunction with the new "logon home" parameter. +logon drive. This should be set to 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 @@ -13496,7 +12691,7 @@ turns a profile into a mandatory one.

    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. @@ -13512,11 +12707,10 @@ profile on the MS Windows workstation as follows:

    2. In the Permitted to use box, click on the Change button.

    3. - Click on the 'Look in" area that lists the machine name, when you click + Click on the 'Look in" area that lists the machine name, when you click here it will open up a selection box. Click on the domain to which the profile must be accessible. -

      Note

      You will need to log on if a logon box opens up. Eg: In the connect - as: MIDEARTH\root, password: mypassword.

    4. +

      Note

      You will need to log on if a logon box opens up. Eg: In the connect as: DOMAIN\root, password: mypassword.

    5. To make the profile capable of being used by anyone select 'Everyone'

    6. Click OK. The Selection box will close. @@ -13524,12 +12718,12 @@ profile on the MS Windows workstation as follows: Now click on the Ok button to create the profile in the path you nominated.

    -Done. You now have a profile that can be edited using the samba-3.0.0 +Done. You now have a profile that can be edited using the samba profiles tool.

    Note

    Under NT/2K the use of mandatory profiles forces the use of MS Exchange storage of mail data. That keeps desktop profiles usable. -

    Note

    1. +

    Procedure 24.2. Windows XP Service Pack 1

    1. This 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 Active Directory. The policy is:

      Computer Configuration\Administrative Templates\System\User @@ -13543,10 +12737,10 @@ the following (N.B. I don't know for sure that this will work in the same way as a domain group policy):

    2. On the XP workstation log in with an Administrator account. -

    3. Click: Start, Run

    4. Type: mmc

    5. Click: OK

    6. A Microsoft Management Console should appear.

    7. Click: File, Add/Remove Snap-in..., Add

    8. Double-Click: Group Policy

    9. Click: Finish, Close

    10. Click: OK

    11. In the "Console Root" window:

    12. Expand: Local Computer Policy, Computer Configuration, +

    13. Click: Start, Run

    14. Type: mmc

    15. Click: OK

    16. A Microsoft Management Console should appear.

    17. Click: File, Add/Remove Snap-in..., Add

    18. Double-Click: Group Policy

    19. Click: Finish, Close

    20. Click: OK

    21. In the "Console Root" window:

    22. Expand: Local Computer Policy, Computer Configuration, Administrative Templates, System, User Profiles

    23. Double-Click: Do not check for user ownership of Roaming Profile Folders

    24. Select: Enabled

    25. Click: OK

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

    27. Reboot

    Sharing Profiles between W9x/Me and NT4/200x/XP workstations

    + changed).

  • Reboot

    • Sharing Profiles between W9x/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 @@ -13557,18 +12751,18 @@ version resulting in loss of profile information content when that user logs on again with the newer version of MS Windows.

    If you then want to share the same Start Menu / Desktop with W9x/Me, you will -need to specify a common location for the profiles. The smb.conf parameters -that need to be common are logon path and -logon home. +need to specify a common 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 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

    +

    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.

    @@ -13578,24 +12772,20 @@ On your NT4 Domain Controller, right click on My Computer< select the tab labelled User Profiles.

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

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

  • Click the Copy To button.

  • In the box labelled Copy Profile to add your new path, eg: c:\temp\foobar

  • Click on the button Change in the Permitted to use box.

  • Click on the group 'Everyone' and then click OK. This closes the 'choose user' box.

  • Now click OK.

    • Follow the above 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 smbpasswd to do -this. Read the man page.

    -With Samba-3.0.0 alpha code you can import all you NT4 domain accounts -using the net samsync method. This way you can retain your profile -settings as well as all your users. -

    moveuser.exe

    +this. Read the man page.

    moveuser.exe

    The W2K 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 user name to change. -

    Get SID

    +

    Get SID

    You can identify the SID by using GetSID.exe from the Windows NT Server 4.0 Resource Kit.

    @@ -13608,7 +12798,7 @@ users who have logged 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 of 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, but as the user logs out all changes made will be lost. If it is desired to NOT allow the @@ -13624,7 +12814,7 @@ 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 affect a mandatory profile. -

    Creating/Managing Group Profiles

    +

    Creating/Managing Group Profiles

    Most organisations are arranged into departments. There is a nice benefit in this fact since usually most users in a department will require the same desktop applications and the same desktop layout. MS Windows NT4/200x/XP will allow the @@ -13634,19 +12824,19 @@ profile is assigned access rights for the user group that needs to be given acce to the group profile.

    The next step is rather important. Please note: Instead of assigning a group profile -to users (ie: Using User Manager) on a "per user" basis, the group itself is assigned +to users (ie: 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 optimised 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.

    @@ -13657,8 +12847,8 @@ select User Profiles, click on the enable box. Do

    To modify the registry directly, launch the Registry Editor (regedit.exe), select the hive HKEY_LOCAL_MACHINE\Network\Logon. Now add a DWORD type key with the name -"User Profiles", to enable user profiles set the value to 1, to disable user profiles set it to 0. -

    How User Profiles Are Handled in Windows 9x / Me?

    +"User Profiles", to enable user profiles set the value to 1, to disable user profiles set it to 0. +

    How User Profiles Are Handled in 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: @@ -13674,7 +12864,7 @@ If a User Profile is not found in either location, the Default User Profile from machine is used and is 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:\WinNT\Profiles. Under this directory on a clean install there will be @@ -13685,7 +12875,7 @@ system users. The Default User directory contains menu customisable 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)

    +

    • All Users settings

    • Default User settings (contains the default NTUser.DAT file)

    When a user logs onto an MS Windows NT4 machine that is a member of a Microsoft security domain the following steps are followed in respect of profile handling:

    1. @@ -13717,8 +12907,8 @@ will stored in the %SystemRoot%\Profiles\%USERNAME% lo also remain stored in the same way, unless the following registry key is created: 

      -	HKEY_LOCAL_MACHINE\SYSTEM\Software\Microsoft\Windows NT\CurrentVersion\winlogon\
-	"DeleteRoamingCache"=dword:00000001
+HKEY_LOCAL_MACHINE\SYSTEM\Software\Microsoft\Windows NT\CurrentVersion\
+winlogon\"DeleteRoamingCache"=dword:00000001

      In which case, the local copy (in %SystemRoot%\Profiles\%USERNAME%) will be @@ -13737,7 +12927,7 @@ are controlled by entries on Windows NT4 is:

      The above hive key contains a list of automatically managed folders. The default entries are:

      -

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

      +

      Table 24.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:

      @@ -13745,8 +12935,8 @@ The registry key that contains the location of the default profile settings is:

      The default entries are: -

      Table 24.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 24.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 can not participate in domain security, can not 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 @@ -13795,9 +12985,9 @@ are controlled by entries on Windows 200x/XP is:

    The above hive key contains a list of automatically managed folders. The default entries are:

    -

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

    +

    Table 24.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 +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 @@ -13811,18 +13001,21 @@ You could also use:

    \\SambaServer\FolderShare\%USERNAME%

    in which case the default folders will be stored in the server named SambaServer in the share called FolderShare under a directory that has the name of the MS Windows -user as seen by the Linux/Unix file system. +user as seen by the Linux/UNIX file system.

    Please note that once you have created a default profile share, you MUST migrate a user's profile (default or custom) to it.

    MS Windows 200x/XP profiles may be Local or Roaming. A roaming profile will be cached locally unless the following registry key is created: -

    HKEY_LOCAL_MACHINE\SYSTEM\Software\Microsoft\Windows NT\CurrentVersion\winlogon\"DeleteRoamingCache"=dword:00000001

    +

    +

    +HKEY_LOCAL_MACHINE\SYSTEM\Software\Microsoft\Windows NT\CurrentVersion\
+	winlogon\"DeleteRoamingCache"=dword:00000001

    In which case, the local cache copy will be deleted on logout. -

    Common Errors

    +

    Common Errors

    The following are some typical errors/problems/questions that have been asked. -

    How does one set up roaming profiles for just one (or a few) user/s or group/s?

    +

    Setting up roaming profiles for just a few user's or group's?

    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 @@ -13834,42 +13027,40 @@ those machines on which roaming profile support is NOT wanted it is then necessary to disable roaming profile handling in the registry of each such machine.

    -With samba-3.0.0 (soon to be released) you can have a global profile -setting in smb.conf _AND_ you can over-ride this by per-user settings +With samba-3 you can have a global profile +setting in smb.conf _AND_ you can over-ride this by per-user settings using the Domain User Manager (as with MS Windows NT4/ Win 2Kx).

    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 can not change)
    A group profile (really should be mandatory ie:unchangable)

    Can NOT use Roaming Profiles

    +

    • A profile unique to that user

    • A mandatory profile (one the user can not change)

    • A group profile (really should be mandatory ie:unchangable)

    Can NOT use Roaming Profiles

    +A user requested the following: “ - I dont want Roaming profile to be implemented, I just want to give users - local profiles only. -... - Please help me I am totally lost with this error from past two days I tried - everything and googled around quite a bit but of no help. Please help me. +I do not want Roaming profiles to be implemented. I want to give users a local profile alone. ... +Please help me 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. ”

    -Your choices are: - - -

    Local profiles

    - I know of no registry keys that will allow auto-deletion of LOCAL profiles on log out -

    Roaming profiles

    -

    can use auto-delete on logout option
    requires a registry key change on workstation

    - - Your choices are: - -

    Personal Roaming profiles

    - - should be preserved on a central server - - workstations 'cache' (store) a local copy - - used in case the profile can not be downloaded - at next logon -

    Group profiles

    - loaded from a central place

    Mandatory profiles

    - - can be personal or group - - can NOT be changed (except by an administrator -

    +The choices are: +

    Local profiles:

    + I know of no registry keys that will allow auto-deletion of LOCAL profiles on log out +

    Roaming profiles:

    + As a user logs onto the network a centrally stored profile is copied to the workstation + to form a local profile. This local profile will persist (remain on the workstation disk) + unless a registry key is changed that will cause this profile to be automatically deleted + on logout. +

    +The Roaming Profile choices are: +

    Personal Roaming profiles

    + These are typically stored in a profile share on a central (or conveniently located + local) server. +

    + Workstations 'cache' (store) a local copy of the profile. This cached copy is used when + the profile can not be downloaded at next logon. +

    Group profiles

    These are loaded from a central profile server

    Mandatory profiles

    + Mandatory profiles can be created for a user as well as for any group that a user + is a member of. Mandatory profiles can NOT be changed by ordinary users. Only the administrator + can change or reconfigure a mandatory profile.

    - -

    A WinNT4/2K/XP profile can vary in size from 130KB to off the scale. Outlook PST files are most often part of the profile and can be many GB in size. On average (in a well controlled environment) roaming profile size of @@ -13883,52 +13074,39 @@ controls of how they can be changed as well as good discipline make up for a problem free site.

    Microsoft's answer to the PST problem is to store all email in an MS -Exchange Server back-end. But this is another story ...! -

    -So, having LOCAL profiles means: - -

    If lots of users user each machine - lot's of local disk storage needed for local profiles
    Every workstation the user logs into has it's own profile - can be very different from machine to machine

    - -On the other hand, having roaming profiles means: -

    The network administrator can control EVERY aspect of user profiles
    With the use of mandatory profiles - a drastic reduction in network management overheads
    User unhappiness about not being able to change their profiles soon fades as they get used to being able to work reliably

    - +Exchange Server back-end. This removes the need for a PST file.

    -I have managed and installed MANY NT/2K networks and have NEVER found one -where users who move from machine to machine are happy with local -profiles. In the long run local profiles bite them. -

    Changing the default profile

    “ -When the client tries to logon to the PDC it looks for a profile to download -where do I put this default profile. +LOCAL profiles mean: +

    • If each machine is used my many users then much local disk storage is needed for local profiles

    • Every workstation the user logs into has it's 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 drasitcally reduces network management overheads.

    • In the long run users will be experience fewer problems.

    Changing the default profile

    +Question: +“ +When the client logs onto the domain controller it searches for a profile to download, +where do I put this default profile? ”

    -Firstly, your samba server need to be configured as a domain controller. -

    -	server = user
-    os level = 32 (or more)
-	domain logons = Yes
-

    -Plus you need to have a [netlogon] share that is world readable. +Firstly, 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 an [netlogon] share that is world readable. It is a good idea to add a logon script to pre-set 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 auto-deletion of roaming profile from the local -workstation cache (disk storage) you need to use the Group Policy Editor +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.

    -Oh, of course the windows clients need to be members of the domain. -Workgroup machines do NOT do network logons - so they never see domain -profiles. +Windows clients need to be members of the domain. Workgroup machines do NOT use network logons so +they do not interoperate with domain profiles.

    -Secondly, for roaming profiles you need: - - logon path = \\%N\profiles\%U (with some such path) - logon drive = H: (Z: is the default) - - Plus you need a PROFILES share that is world writable. -

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

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

    +

    Chapter 25. 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 you 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 +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. @@ -13936,9 +13114,9 @@ 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 require more than PAM configuration alone. Please refer to the Winbind chapter. -

    Features and Benefits

    -A number of Unix systems (eg: Sun Solaris), as well as the xxxxBSD family and Linux, +The use of Winbind require more than PAM configuration alone. Please refer to the Winbind chapter. +

    Features and Benefits

    +A number of UNIX systems (eg: 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 to use an alternative to the system password database (/etc/passwd) @@ -13951,38 +13129,38 @@ authentication/authorization infrastructure. PAM is configured either through o /etc/pam.conf (Solaris), or by editing individual 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 +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 centralised on a remote server.

    PAM support modules are available for: -

    /etc/passwd

    -

    - There are several PAM modules that interact with this standard Unix user +

    /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

    -

    +

    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

    -

    +

    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, Microsoft Active Directory. -

    NetWare Bindery

    -

    +

    NetWare Bindery:

    The pam_ncp_auth.so module allows authentication off any bindery enabled NetWare Core Protocol based server. -

    SMB Password

    -

    +

    SMB Password:

    This module, called pam_smbpass.so, will allow user authentication off the passdb backend that is configured in the Samba smb.conf file. -

    SMB Server

    -

    +

    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

    -

    +

    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

    -

    +

    RADIUS:

    There is a PAM RADIUS (Remote Access Dial-In User Service) authentication module. In most cases the administrator will need to locate the source code for this tool and compile and install it themselves. RADIUS protocols are @@ -13995,12 +13173,12 @@ of distributed samba domain controllers that can provide wide are network bandwi 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 the system administrator 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. @@ -14015,32 +13193,31 @@ 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 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 
-
-http://ftp.kernel.org/pub/linux/libs/pam The Official Linux-PAM home page.
+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
 
    
 
    
 Below, we explain the meaning of each of these tokens. The second (and more recently adopted)
 way of configuring Linux-PAM is via the contents of the /etc/pam.d/ directory.
 Once we have explained the meaning of the above tokens, we will describe this method.
-
    service-name
    -
    
+
    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', etc. .
 		
    
 		There is a special service-name, reserved for defining a default authentication mechanism. It has
 		the name `OTHER' and may be specified in either lower or upper case characters. Note, when there
 		is a module specified for a named service, the `OTHER' entries are ignored.
-		
    module-type
    -
    
+		
    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.
@@ -14062,7 +13239,7 @@ Once we have explained the meaning of the above tokens, we will describe this me
 			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'
 			based authentication (auth) module-type.
-			
    control-flag
    -
    
+			
    control-flag:
    
 		The control-flag is used to indicate how the PAM library will react to the success or failure of the
 		module it is associated with. Since modules can be stacked (modules of the same type execute in series,
 		one after another), the control-flags determine the relative importance of each module. The application
@@ -14106,9 +13283,9 @@ Once we have explained the meaning of the above tokens, we will describe this me
 		The more elaborate (newer) syntax is much more specific and gives the administrator a great deal of control
 		over how the user is authenticated. This form of the control flag is delimited with square brackets and
 		consists of a series of value=action tokens:
-		
    -		[value1=action1 value2=action2 ...]
-		
    
+		
    +[value1=action1 value2=action2 ...]
+
    
 		Here, value1 is one of the following return values: success; open_err; symbol_err; service_err;
 		system_err; buf_err; perm_denied; auth_err; cred_insufficient; authinfo_unavail; user_unknown; maxtries;
 		new_authtok_reqd; acct_expired; session_err; cred_unavail; cred_expired; cred_err; no_module_data; conv_err;
@@ -14163,7 +13340,7 @@ Once we have explained the meaning of the above tokens, we will describe this me
 		[ ... value=action ... ] control syntax, it is possible for an application to be configured
 		to support binary prompts with compliant clients, but to gracefully fall over into an alternative authentication
 		mode for older, legacy, applications.
-		
    module-path
    -
    
+		
    module-path:
    
 		The path-name of the dynamically loadable object file; the pluggable module itself. If the first character of the
 		module path is `/', it is assumed to be a complete path. If this is not the case, the given module path is appended
 		to the default module path: /lib/security (but see the notes above).
@@ -14174,7 +13351,7 @@ Once we have explained the meaning of the above tokens, we will describe this me
 		to syslog(3). For a list of generic options see the next section.
 		
    
 		Note, if you wish to include spaces in an argument, you should surround that argument with square brackets. For example:
-		
    +		
     squid auth required pam_mysql.so user=passwd_query passwd=mada \
         db=eminence [query=select user_name from internet_service where \
                      user_name='%u' and password=PASSWORD('%p') and \
@@ -14182,19 +13359,19 @@ squid auth required pam_mysql.so user=passwd_query passwd=mada \
 
    
 		Note, when using this convention, you can include `[' characters inside the string, and if you wish to include a `]'
 		character inside the string that will survive the argument parsing, you should use `\['. In other words:
-		
    +		
     [..[..\]..]    -->   ..[..]..
 
    
 		Any line in (one of) the configuration file(s), 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 been uncommented is probably not usable as 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
 #
@@ -14209,10 +13386,10 @@ session      required    pam_pwdb.so
 # session    optional    pam_lastlog.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 -

    +
     pam_access.so    pam_ftp.so          pam_limits.so     
 pam_ncp_auth.so  pam_rhosts_auth.so  pam_stress.so     
 pam_cracklib.so  pam_group.so        pam_listfile.so   
@@ -14236,7 +13413,7 @@ hashes. This database is stored in either
 /usr/local/samba/private/smbpasswd, 
 /etc/samba/smbpasswd, or in 
 /etc/samba.d/smbpasswd, depending on the 
-Samba implementation for your Unix/Linux system. The 
+Samba implementation for your UNIX/Linux system. The 
 pam_smbpass.so module is provided by 
 Samba version 2.2.1 or later. It can be compiled by specifying the 
 --with-pam_smbpass options when running Samba's
@@ -14244,7 +13421,7 @@ Samba version 2.2.1 or later. It can be compiled by specifying the
 on the pam_smbpass module, see the documentation
 in the source/pam_smbpass directory of the Samba 
 source distribution.
-
    +
     #%PAM-1.0
 # The PAM configuration file for the `login' service
 #
@@ -14255,7 +13432,7 @@ password    required    pam_smbpass.so nodelay
 
    
 The following is the PAM configuration file for a particular 
 Linux system. The default condition uses pam_pwdb.so.
-
    +
     #%PAM-1.0
 # The PAM configuration file for the `samba' service
 #
@@ -14269,7 +13446,7 @@ smbpasswd database even for basic samba authentication. Such a
 decision could also be made for the passwd program and would 
 thus allow the smbpasswd passwords to be changed using the passwd 
 program.
-
    +
     #%PAM-1.0
 # The PAM configuration file for the `samba' service
 #
@@ -14288,24 +13465,24 @@ 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 makes trade-offs, so you may want examine the 
 PAM documentation for further helpful information.
-

    smb.conf PAM Configuration

    -There is an option in smb.conf called obey pam restrictions. +

    smb.conf PAM Configuration

    + There is an option in smb.conf called obey pam restrictions. The following is from the on-line help for this option in SWAT;

    -When Samba-3 is configured to enable PAM support (i.e. +When Samba is configured to enable PAM support (i.e. --with-pam), this parameter will control whether or not Samba should obey PAM's account and session management directives. The default behavior is to use PAM for clear text authentication only and to ignore any account or session management. Note that Samba always ignores PAM for authentication in the case of -encrypt passwords = yes. +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 users credentials acceptable to the platform. -Unix requires the provision of a user identifier (UID) as well as a group identifier (GID). +UNIX requires the provision of a user identifier (UID) as well as a group identifier (GID). These are both simple integer type numbers that are obtained from a password backend such as /etc/passwd.

    @@ -14329,7 +13506,7 @@ Microsoft Active Directory Service (ADS) in so far as reduction of wide area net 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 which can be used on conforming systems to keep the smbpasswd (Samba password) database in sync with the unix password file. PAM (Pluggable Authentication Modules) is an API supported @@ -14342,24 +13519,23 @@ concerned about the presence of suid root binaries on your system, it is recommended that you use pam_winbind instead.

    Options recognized by this module are as follows: -

    Table 25.1. Options recognized by pam_smbpass

    debuglog more debugging info
    auditlike debug, but also logs unknown usernames
    use_first_passdon't prompt the user for passwords; take them from PAM_ items instead
    try_first_passtry to get the password from a previous PAM module, fall back to prompting the user
    use_authtoklike try_first_pass, but *fail* if the new PAM_AUTHTOK has not been previously set. (intended for stacking password modules only)
    not_set_passdon't make passwords used by this module available to other modules.
    nodelaydon't insert ~1 second delays on authentication failure.
    nulloknull passwords are allowed.
    nonullnull passwords are not allowed. Used to override the Samba configuration.
    migrateonly meaningful in an "auth" context; used to update smbpasswd file with a password used for successful authentication.
    smbconf=filespecify an alternate path to the smb.conf file.

    +

    Table 25.1. Options recognized by pam_smbpass

    debuglog more debugging info
    auditlike debug, but also logs unknown usernames
    use_first_passdon't prompt the user for passwords; take them from PAM_ items instead
    try_first_passtry to get the password from a previous PAM module, fall back to prompting the user
    use_authtoklike try_first_pass, but *fail* if the new PAM_AUTHTOK has not been previously set. (intended for stacking password modules only)
    not_set_passdon't make passwords used by this module available to other modules.
    nodelaydon't insert ~1 second delays on authentication failure.
    nulloknull passwords are allowed.
    nonullnull passwords are not allowed. Used to override the Samba configuration.
    migrateonly meaningful in an "auth" context; used to update smbpasswd file with a password used for successful authentication.
    smbconf=filespecify an alternate path to the smb.conf file.

    -Thanks go to the following people: -

    Andrew Morgan, for providing the Linux-PAM - framework, without which none of this would have happened
    Christian Gafton and Andrew Morgan again, for the - pam_pwdb module upon which pam_smbpass was originally based
    Luke Leighton for being receptive to the idea, +

    • Andrew Morgan, for providing the Linux-PAM + framework, without which none of this would have happened

    • Christian Gafton and Andrew Morgan again, for the + pam_pwdb module upon which pam_smbpass was originally based

    • Luke Leighton for being receptive to the idea, and for the occasional good-natured complaint about the project's status - that keep me working on it :)

    . + that keep me working on it :)

    .

    The following are examples of the use of pam_smbpass.so in the format of Linux /etc/pam.d/ files structure. Those wishing to implement this tool on other platforms will need to adapt this appropriately. -

    Password Synchronisation Configuration

    +

    Password Synchronisation Configuration

    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. Useful when an expired password might be changed by an application (such as ssh). -

    +
     #%PAM-1.0
 # password-sync
 #
@@ -14370,13 +13546,13 @@ 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

    A sample PAM configuration that 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: password migration takes place when users ftp in, login using ssh, pop their mail, etc. -

    +
     #%PAM-1.0
 # password-migration
 #
@@ -14389,11 +13565,11 @@ 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

    A sample PAM configuration for a 'mature' smbpasswd installation. private/smbpasswd is fully populated, and we consider it an error if -the smbpasswd doesn't exist or doesn't match the Unix password. -

    +the smbpasswd doesn't exist or doesn't match the UNIX password.
+
     #%PAM-1.0
 # password-mature
 #
@@ -14404,11 +13580,11 @@ 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

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

    +
     #%PAM-1.0
 # kdc-pdc
 #
@@ -14420,13 +13596,15 @@ 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 a very fickle and sensitive to configuration glitches. Here we look at a few cases from the Samba mailing list. -

    pam_winbind problem

    - I have the following PAM configuration: +

    pam_winbind problem

    + “ + I have the following PAM configuration: + ”

    -

    +
     auth required /lib/security/pam_securetty.so
 auth sufficient /lib/security/pam_winbind.so
 auth sufficient /lib/security/pam_unix.so use_first_pass nullok
@@ -14436,18 +13614,61 @@ account required /lib/security/pam_stack.so service=system-auth
 account required /lib/security/pam_winbind.so
 password required /lib/security/pam_stack.so service=system-auth
 
    
-
    
-	When I open a new console with [ctrl][alt][F1], then I cant log in with my user "pitie".
-	I've tried with user "scienceu+pitie" also.
 	
    
-	Answer: The problem may lie with your inclusion of pam_stack.so
+		“
+	When I open a new console with [ctrl][alt][F1], then I cant log in with my user "pitie".
+	I've tried with user "scienceu+pitie" also.
+”
+	
    
+		The problem may lie with your inclusion of pam_stack.so
 	service=system-auth. That file often contains a lot of stuff that may
 	duplicate what you're already doing. Try commenting out the pam_stack lines
 	for auth and account and see if things work. If they do, look at
 	/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.
-

    Chapter 26. 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
    My Boomerang Won't Come Back
    Very Slow Network Connections
    Samba server name change problem

    +

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

    +root# wbinfo -u
+MIDEARTH+maryo
+MIDEARTH+jackb
+MIDEARTH+ameds
+...
+MIDEARTH+root
+
+root# wbinfo -g
+MIDEARTH+Domain Users
+MIDEARTH+Domain Admins
+MIDEARTH+Domain Guests
+...
+MIDEARTH+Accounts
+
+root# getent passwd
+root:x:0:0:root:/root:/bin/bash
+bin:x:1:1:bin:/bin:/bin/bash
+...
+maryo:x:15000:15003:Mary Orville:/home/MIDEARTH/maryo:/bin/false
+

    + “ + But the following command just fails: +” +

    +root# chown 'maryo' a_file
+chown: `maryo': invalid user
+

    +“ +This is driving me nuts! What can be wrong? +” +

    + Your system is likely running nscd, the name service + caching daemon. Shut it down, do NOT restart it! You will find your problem resolved. +

    Chapter 26. 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 in one way
    Very Slow Network Connections
    Samba server name change problem

    This section 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 use of @@ -14458,15 +13679,15 @@ NetBIOS over TCP/IP then this section may help you to resolve networking problem 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 mis-apprehension. -

    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 +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 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 it's 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 @@ -14479,17 +13700,19 @@ Name Service or WINS), TCP port 139 AND TCP port 445 (for actual file and print

    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). + Use of DHCP with ADS is recommended as a further means of maintaining central control over 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

    -Contains a static list of IP Addresses and names. +

    • /etc/hosts

    • /etc/resolv.conf

    • /etc/host.conf

    • /etc/nsswitch.conf

    /etc/hosts

    +Contains a static list of IP addresses and names. eg: -

    -	127.0.0.1	localhost localhost.localdomain
-	192.168.1.1	bigbox.caldera.com	bigbox	alias4box
+
    +127.0.0.1	localhost localhost.localdomain
+192.168.1.1	bigbox.caldera.com	bigbox	alias4box
 
    
 The purpose of /etc/hosts is to provide a 
 name resolution mechanism so that uses do not need to remember 
@@ -14497,10 +13720,10 @@ 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 
+Access Control address, or MAC address. IP addresses are currently 
 32 bits in length and are typically presented as four (4) decimal 
 numbers that are separated by a dot (or period). eg: 168.192.1.1.
-
    
+
    
 MAC Addresses use 48 bits (or 6 bytes) and are typically represented 
 as two digit hexadecimal numbers separated by colons. eg: 
 40:8e:0a:12:34:56
@@ -14517,8 +13740,8 @@ be assigned per MAC address. One address must be the primary IP address,
 this is the address that will be returned in the 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 
+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.
 
    
@@ -14533,15 +13756,15 @@ MAC addresses only; their own unique address and the 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 
+UNIX/Linux TCP/IP installations and as a minimum will contain 
 the localhost and local network interface IP addresses and the 
 primary names by which they are known within the local machine. 
 This file helps to prime the pump so that 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 @@ -14551,41 +13774,41 @@ 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 affected. It is a critical configuration file. This file controls the order by which name resolution may proceed. The typical structure is: -

    -	order hosts,bind
-	multi on
+
    +order hosts,bind
+multi on
 
    
 then 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: -

    -	# /etc/nsswitch.conf
-	#
-	# Name Service Switch configuration file.
-	#
+
    +# /etc/nsswitch.conf
+#
+# Name Service Switch configuration file.
+#
 
-	passwd:		compat
-	# Alternative entries for password authentication are:
-	# passwd:	compat files nis ldap winbind
-	shadow:		compat
-	group:		compat
+passwd:		compat
+# Alternative entries for password authentication are:
+# passwd:	compat files nis ldap winbind
+shadow:		compat
+group:		compat
 
-	hosts:		files nis dns
-	# Alternative entries for host name resolution are:
-	# hosts:	files dns nis nis+ hesiod db compat ldap wins
-	networks:	nis files dns
+hosts:		files nis dns
+# Alternative entries for host name resolution are:
+# hosts:	files dns nis nis+ hesiod db compat ldap wins
+networks:	nis files dns
 
-	ethers:		nis files
-	protocols:	nis files
-	rpc:		nis files
-	services:	nis files
+ethers:		nis files
+protocols:	nis files
+rpc:		nis files
+services:	nis files
 
    
 Of course, each of these mechanisms requires that the appropriate 
 facilities and/or services are correctly configured.
@@ -14593,27 +13816,27 @@ facilities and/or services are correctly configured.
 It should be noted that unless a network request/message must be 
 sent, TCP/IP networks are silent. All TCP/IP communications assumes 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 that linux clients will 
 be able to obtain resolution of MS Windows NetBIOS names to IP 
 Addresses. To gain this functionality Samba needs to be compiled 
-with appropriate arguments to the make command (ie: make 
+with appropriate arguments to the make command (i.e.: make 
 nsswitch/libnss_wins.so). The resulting library should 
 then be installed in the /lib directory and 
-the "wins" parameter needs to be added to the "hosts:" line in 
+the "wins" parameter needs to be added to the "hosts:" line in 
 the /etc/nsswitch.conf file. At this point it 
-will be possible to ping any MS Windows machine by it's NetBIOS 
+will be possible to ping any MS Windows machine by its NetBIOS 
 machine name, so 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 about the name each machine is given. This name is known variously (and inconsistently) as -the "computer name", "machine name", "networking name", "netbios name", -"SMB name". All terms mean the same thing with the exception of -"netbios name" which can apply also to the name of the workgroup or the -domain name. The terms "workgroup" and "domain" are really just a -simply name with which the machine is associated. All NetBIOS names +the "computer name", "machine name", "networking name", "netbios name", +or "SMB name". All terms mean the same thing with the exception of +"netbios name" which can apply also to the name of the workgroup or the +domain name. The terms "workgroup" and "domain" are really just a +simple name with which the machine is associated. All NetBIOS names are exactly 16 characters in length. The 16th character is reserved. It is used to store a one byte value that indicates service level information for the NetBIOS name that is registered. A NetBIOS machine @@ -14621,25 +13844,14 @@ name is therefore registered for each service type that is provided by the client/server.

    The following are typical NetBIOS name/service type registrations: -

    -	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
-
-	Group Names:
-		WORKGROUP<03> = Generic Name registered by all members of WORKGROUP
-		WORKGROUP<1c> = Domain Controllers / Netlogon Servers
-		WORKGROUP<1d> = Local Master Browsers
-		WORKGROUP<1e> = Internet Name Resolvers
-

    +

    Table 26.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 26.2. Group Names

    WORKGROUP<03>Generic Name registered by all members of WORKGROUP
    WORKGROUP<1c>Domain Controllers / Netlogon Servers
    WORKGROUP<1d>Local Master Browsers
    WORKGROUP<1e>Internet Name Resolvers

    + It should be noted that all NetBIOS machines register their own names as per the above. This is in vast contrast to TCP/IP installations where traditionally the system administrator will determine 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 type information that MS Windows clients depend on to locate the type of service that may @@ -14648,12 +13860,12 @@ wants to locate a domain logon server. It finds this service and the IP address of a server that provides it by performing a lookup (via a NetBIOS broadcast) for enumeration of all machines that have 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. Which -ever machine first replies then ends up providing the logon services. +IP address that is returned in the enumerated list of IP addresses. +Whichever machine first replies then ends up providing the logon services.

    -The name "workgroup" or "domain" really can be confusing since these +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 +architecture of the MS Windows network. The term "workgroup" indicates that the primary nature of the network environment is that of a peer-to-peer design. In a WORKGROUP all machines are responsible for their own security, and generally such security is limited to use of @@ -14677,7 +13889,7 @@ 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 that machine has communicated with over the @@ -14691,11 +13903,11 @@ an attempt to exchange a message with that machine will be subject to time-out delays. i.e.: Its name is in the cache, so a name resolution lookup will succeed, but the machine can not respond. This can be frustrating for users - but it is a characteristic of the protocol. -

    +

    The MS Windows utility that allows examination of the NetBIOS -name cache is called "nbtstat". The Samba equivalent of this +name cache is called "nbtstat". The Samba equivalent of this is called nmblookup. -

    The LMHOSTS file

    +

    The LMHOSTS file

    This file is usually located in MS Windows NT 4.0 or 2000 in C:\WINNT\SYSTEM32\DRIVERS\ETC and contains the IP Address and the machine name in matched pairs. The @@ -14703,102 +13915,103 @@ the IP Address and the machine name in matched pairs. The to IP address mapping.

    It typically looks like: -

    -	# Copyright (c) 1998 Microsoft Corp.
-	#
-	# This is a sample LMHOSTS file used by the Microsoft Wins Client (NetBIOS
-	# over TCP/IP) stack for Windows98
-	#
-	# This file contains the mappings of IP addresses to NT computernames
-	# (NetBIOS) names.  Each entry should be kept on an individual line.
-	# The IP address should be placed in the first column followed by the
-	# corresponding computername. The address and the computername
-	# should be separated by at least one space or tab. The "#" character
-	# is generally used to denote the start of a comment (see the exceptions
-	# below).
-	#
-	# This file is compatible with Microsoft LAN Manager 2.x TCP/IP lmhosts
-	# files and offers the following extensions:
-	#
-	#      #PRE
-	#      #DOM:<domain>
-	#      #INCLUDE <filename>
-	#      #BEGIN_ALTERNATE
-	#      #END_ALTERNATE
-	#      \0xnn (non-printing character support)
-	#
-	# Following any entry in the file with the characters "#PRE" will cause
-	# the entry to be preloaded into the name cache. By default, entries are
-	# not preloaded, but are parsed only after dynamic name resolution fails.
-	#
-	# Following an entry with the "#DOM:<domain>" tag will associate the
-	# entry with the domain specified by <domain>. This affects how the
-	# browser and logon services behave in TCP/IP environments. To preload
-	# the host name associated with #DOM entry, it is necessary to also add a
-	# #PRE to the line. The <domain> is always preloaded although it will not
-	# be shown when the name cache is viewed.
-	#
-	# Specifying "#INCLUDE <filename>" will force the RFC NetBIOS (NBT)
-	# software to seek the specified <filename> and parse it as if it were
-	# local. <filename> is generally a UNC-based name, allowing a
-	# centralized lmhosts file to be maintained on a server.
-	# It is ALWAYS necessary to provide a mapping for the IP address of the
-	# server prior to the #INCLUDE. This mapping must use the #PRE directive.
-	# In addition the share "public" in the example below must be in the
-	# LanManServer list of "NullSessionShares" in order for client machines to
-	# be able to read the lmhosts file successfully. This key is under
-	# \machine\system\currentcontrolset\services\lanmanserver\parameters\nullsessionshares
-	# in the registry. Simply add "public" to the list found there.
-	#
-	# The #BEGIN_ and #END_ALTERNATE keywords allow multiple #INCLUDE
-	# statements to be grouped together. Any single successful include
-	# will cause the group to succeed.
-	#
-	# Finally, non-printing characters can be embedded in mappings by
-	# first surrounding the NetBIOS name in quotations, then using the
-	# \0xnn notation to specify a hex value for a non-printing character.
-	#
-	# The following example illustrates all of these extensions:
-	#
-	# 102.54.94.97     rhino         #PRE #DOM:networking  #net group's DC
-	# 102.54.94.102    "appname  \0x14"                    #special app server
-	# 102.54.94.123    popular            #PRE             #source server
-	# 102.54.94.117    localsrv           #PRE             #needed for the include
-	#
-	# #BEGIN_ALTERNATE
-	# #INCLUDE \\localsrv\public\lmhosts
-	# #INCLUDE \\rhino\public\lmhosts
-	# #END_ALTERNATE
-	#
-	# In the above example, the "appname" server contains a special
-	# character in its name, the "popular" and "localsrv" server names are
-	# preloaded, and the "rhino" server name is specified so it can be used
-	# to later #INCLUDE a centrally maintained lmhosts file if the "localsrv"
-	# system is unavailable.
-	#
-	# Note that the whole file is parsed including comments on each lookup,
-	# 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

    +

    +# Copyright (c) 1998 Microsoft Corp.
+#
+# This is a sample LMHOSTS file used by the Microsoft Wins Client (NetBIOS
+# over TCP/IP) stack for Windows98
+#
+# This file contains the mappings of IP addresses to NT computernames
+# (NetBIOS) names.  Each entry should be kept on an individual line.
+# The IP address should be placed in the first column followed by the
+# corresponding computername. The address and the computername
+# should be separated by at least one space or tab. The "#" character
+# is generally used to denote the start of a comment (see the exceptions
+# below).
+#
+# This file is compatible with Microsoft LAN Manager 2.x TCP/IP lmhosts
+# files and offers the following extensions:
+#
+#      #PRE
+#      #DOM:<domain>
+#      #INCLUDE <filename>
+#      #BEGIN_ALTERNATE
+#      #END_ALTERNATE
+#      \0xnn (non-printing character support)
+#
+# Following any entry in the file with the characters "#PRE" will cause
+# the entry to be preloaded into the name cache. By default, entries are
+# not preloaded, but are parsed only after dynamic name resolution fails.
+#
+# Following an entry with the "#DOM:<domain>" tag will associate the
+# entry with the domain specified by <domain>. This affects how the
+# browser and logon services behave in TCP/IP environments. To preload
+# the host name associated with #DOM entry, it is necessary to also add a
+# #PRE to the line. The <domain> is always preloaded although it will not
+# be shown when the name cache is viewed.
+#
+# Specifying "#INCLUDE <filename>" will force the RFC NetBIOS (NBT)
+# software to seek the specified <filename> and parse it as if it were
+# local. <filename> is generally a UNC-based name, allowing a
+# centralized lmhosts file to be maintained on a server.
+# It is ALWAYS necessary to provide a mapping for the IP address of the
+# server prior to the #INCLUDE. This mapping must use the #PRE directive.
+# In addition the share "public" in the example below must be in the
+# LanManServer list of "NullSessionShares" in order for client machines to
+# be able to read the lmhosts file successfully. This key is under
+# \machine\system\currentcontrolset\services\lanmanserver\
+# parameters\nullsessionshares
+# in the registry. Simply add "public" to the list found there.
+#
+# The #BEGIN_ and #END_ALTERNATE keywords allow multiple #INCLUDE
+# statements to be grouped together. Any single successful include
+# will cause the group to succeed.
+#
+# Finally, non-printing characters can be embedded in mappings by
+# first surrounding the NetBIOS name in quotations, then using the
+# \0xnn notation to specify a hex value for a non-printing character.
+#
+# The following example illustrates all of these extensions:
+#
+# 102.54.94.97     rhino         #PRE #DOM:networking  #net group's DC
+# 102.54.94.102    "appname  \0x14"                    #special app server
+# 102.54.94.123    popular            #PRE             #source server
+# 102.54.94.117    localsrv           #PRE             #needed for the include
+#
+# #BEGIN_ALTERNATE
+# #INCLUDE \\localsrv\public\lmhosts
+# #INCLUDE \\rhino\public\lmhosts
+# #END_ALTERNATE
+#
+# In the above example, the "appname" server contains a special
+# character in its name, the "popular" and "localsrv" server names are
+# preloaded, and the "rhino" server name is specified so it can be used
+# to later #INCLUDE a centrally maintained lmhosts file if the "localsrv"
+# system is unavailable.
+#
+# Note that the whole file is parsed including comments on each lookup,
+# 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

    This file is usually located in MS Windows NT 4.0 or 2000 in C:\WINNT\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

    +every way the equivalent of the UNIX/Linux /etc/hosts file. +

    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 dependant on what the NetBIOS -Node Type parameter is configured to. A Node Type of 0 means use -NetBIOS broadcast (over UDP broadcast) is first used if the name +configuration facility. If enabled, an elaborate name resolution sequence +is followed the precise nature of which is dependant on how the NetBIOS +Node Type parameter is configured. A Node Type of 0 means that +NetBIOS broadcast (over UDP broadcast) is used if the name that is the subject of a name lookup is not found in the NetBIOS name 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 @@ -14806,24 +14019,20 @@ 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. -

    Common Errors

    +

    For information about setting up Samba as a WINS server, read + the chapter on network browsing.

    Common Errors

    TCP/IP network configuration problems find every network administrator sooner or later. The cause can be anything from keyboard mishaps, forgetfulness, simple mistakes, and carelessness. Of course, no one is every deliberately careless! -

    My Boomerang Won't Come Back

    - Well, the real complaint said, "I can ping my samba server from Windows, but I can - not ping my Windows machine from the samba server." +

    Pinging works only in one way

    + “I can ping my samba server from Windows, but I can + not ping my Windows machine from the samba server.”

    The Windows machine was at IP Address 192.168.1.2 with netmask 255.255.255.0, the Samba server (Linux) was at IP Address 192.168.1.130 with netmask 255.255.255.128. @@ -14831,49 +14040,49 @@ carelessness. Of course, no one is every 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 causes of slow network response includes: -

    • Client is configured to use DNS and DNS server is down

    • Client is configured to use remote DNS server, but 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 our DNS or WINS traffic

    Samba server name change problem

    - The name of the samba server was changed, samba was restarted, samba server can not be +

    • Client is configured to use DNS and DNS server is down

    • Client is configured to use remote DNS server, but 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 our DNS or WINS traffic

    Samba server name change problem

    + “The name of the samba server was changed, samba was restarted, samba server can not be pinged by new name from MS Windows NT4 Workstation, but it does still respond to ping using - the old name. Why? + the old name. Why?”

    From this description three (3) things are rather obvious:

    • WINS is NOT in use, only broadcast based name resolution is used

    • The samba server was renamed and restarted within the last 10-15 minutes

    • The old samba server name is still in the NetBIOS name cache on the MS Windows NT4 Workstation

    To find what names are present in the NetBIOS name cache on the MS Windows NT4 machine, open a cmd shell, then:

    - 

    -	C:\temp\>nbtstat -n
+
    +C:\> nbtstat -n
 
-	              NetBIOS Local Name Table
+              NetBIOS Local Name Table
 
-	   Name                 Type          Status
-	------------------------------------------------
-	SLACK            <03>  UNIQUE      Registered
-	ADMINISTRATOR    <03>  UNIQUE      Registered
-	SLACK            <00>  UNIQUE      Registered
-	SARDON           <00>  GROUP       Registered
-	SLACK            <20>  UNIQUE      Registered
-	SLACK            <1F>  UNIQUE      Registered
+   Name                 Type          Status
+------------------------------------------------
+FRODO            <03>  UNIQUE      Registered
+ADMINSTRATOR     <03>  UNIQUE      Registered
+FRODO            <00>  UNIQUE      Registered
+SARDON           <00>  GROUP       Registered
+FRODO            <20>  UNIQUE      Registered
+FRODO            <1F>  UNIQUE      Registered
 
 
-	C:\Temp\>nbtstat -c
+C:\> nbtstat -c
 
-	             NetBIOS Remote Cache Name Table
+             NetBIOS Remote Cache Name Table
 
-	   Name                 Type       Host Address     Life [sec]
-	--------------------------------------------------------------
-	FRODO            <20>  UNIQUE      192.168.1.1          240
+   Name                 Type       Host Address     Life [sec]
+--------------------------------------------------------------
+GANDALF	<20>  UNIQUE      192.168.1.1          240
 
-	C:\Temp\>
-	
    
+C:\> 
+

    - In the above example, FRODO is the Samba server and SLACK is the MS Windows NT4 Workstation. - The first listing shows the contents of the Local Name Table (ie: Identity information on + In the above example, GANDALF is the Samba server and FRODO is the MS Windows NT4 Workstation. + The first listing shows the contents of the Local Name Table (i.e.: Identity information on the MS Windows workstation), the second shows the NetBIOS name in the NetBIOS name cache. The name cache contains the remote machines known to this workstation. -

    Chapter 27. Unicode/Charsets

    Jelmer R. Vernooij

    The Samba Team

    TAKAHASHI Motonobu

    25 March 2003

    Table of Contents

    Features and Benefits
    What are charsets and unicode?
    Samba and charsets
    Conversion from old names
    Japanese charsets

    Features and Benefits

    +

    Chapter 27. Unicode/Charsets

    Jelmer R. Vernooij

    The Samba Team

    TAKAHASHI Motonobu

    25 March 2003

    Table of Contents

    Features and Benefits
    What are charsets and unicode?
    Samba and charsets
    Conversion from old names
    Japanese charsets
    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 @@ -14881,14 +14090,13 @@ ago it was common for software to be written for exclusive use in the country of origin.

    Of all the effort that has been brought to bear on providing native language support -for all computer users, the efforts of the Openi18n organisation is deserving of -special mention. For more information about Openi18n please refer to: -http://www.openi18n.org/. +for all computer users, the efforts of the Openi18n organisation 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 trans-global file and printer sharing platform. -

    What are charsets and unicode?

    +

    What are charsets and unicode?

    Computers communicate in numbers. In texts, each number will be translated to a corresponding letter. The meaning that will be assigned to a certain number depends on the character set(charset) @@ -14905,84 +14113,233 @@ is more then all possible characters one could think of. They are called multibyte charsets (because they use more then one byte to store one character).

    -A standardised multibyte charset is unicode, info is available at -www.unicode.org. -A big advantage of using a multibyte charset is that you only need one; no -need to make sure two computers use the same charset when they are + A standardised multibyte charset is 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 used to use single-byte charsets, named +

    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 protocol. Thus, you -have to make sure you are using the same charset when talking to an old client. +have to make sure you are using the same charset when talking to an older client. Newer clients (Windows NT, 2K, XP) talk unicode over the wire. -

    Samba and charsets

    +

    Samba and charsets

    As of samba 3.0, samba can (and will) talk unicode over the wire. Internally, samba knows of three kinds of character sets: -

    unix charset

    +

    unix charset

    This is the charset used internally by your operating system. - The default is ASCII, which is fine for most - systems. -

    display charset

    This is the charset samba will use to print messages + The default is UTF-8, which is fine for most + systems. The default in previous samba releases was ASCII. +

    display charset

    This is the charset samba will use to print messages on your screen. It should generally be the same as the unix charset. -

    dos charset

    This is the charset samba uses when communicating with +

    dos charset

    This is the charset samba uses when communicating with DOS and Windows 9x clients. It will talk unicode to all newer clients. The default depends on the charsets you have installed on your system. - Run testparm -v | grep "dos charset" to see + Run testparm -v | grep "dos charset" to see what the default is on your system. -

    Conversion from old names

    Because previous samba versions did not do any charset conversion, +

    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.

    The following script from Steve Langasek converts all -filenames from CP850 to the iso8859-15 charset.

    -#find /path/to/share -type f -exec bash -c 'CP="{}"; ISO=`echo -n "$CP" | iconv -f cp850 \ - -t iso8859-15`; if [ "$CP" != "$ISO" ]; then mv "$CP" "$ISO"; fi' \; - -

    Japanese charsets

    Samba doesn't work correctly with Japanese charsets yet. Here are -points of attention when setting it up:

    • You should set mangling method = -hash

    • There are various iconv() implementations around and not +for the local charset used by the DOS/Windows clients.

      Bjoern Jacke has written a utility named convm that can convert whole directory + structures to different charsets with one single command. +

    Japanese charsets

    Samba doesn't work correctly with Japanese charsets yet. Here are +points of attention when setting it up:

    • You should set mangling method = hash

    • There are various iconv() implementations around and not all of them work equally well. glibc2's iconv() has a critical problem in CP932. libiconv-1.8 works with CP932 but still has some problems and -does not work with EUC-JP.

    • You should set dos charset = CP932, not -Shift_JIS, SJIS...

    • Currently only unix charset = CP932 +does not work with EUC-JP.

    • You should set dos charset = CP932, not +Shift_JIS, SJIS...

    • Currently only unix charset = CP932 will work (but still has some problems...) because of iconv() issues. -unix charset = EUC-JP doesn't work well because of -iconv() issues.

    • Currently Samba 3.0 does not support unix charset -= UTF8-MAC/CAP/HEX/JIS*

    More information (in Japanese) is available at: http://www.atmarkit.co.jp/flinux/special/samba3/samba3a.html.

    Chapter 28. Samba Backup Techniques

    John H. Terpstra

    Samba Team

    Table of Contents

    Note
    Features and Benefits

    Note

    +unix charset = EUC-JP doesn't work well because of +iconv() issues.

  • Currently Samba 3.0 does not support unix charset = UTF8-MAC/CAP/HEX/JIS*

    • More information (in Japanese) is available at: http://www.atmarkit.co.jp/flinux/special/samba3/samba3a.html.

    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 don't have any dos clients, you can safely ignore this message.

    CP850 should be supported by your local iconv implementation. Make sure you have all the required packages installed. If you compiled samba from source, make sure configure found iconv.

    Chapter 28. Samba Backup Techniques

    John H. Terpstra

    Samba Team

    Table of Contents

    Note
    Features and Benefits

    Note

    This chapter did not make it into this release. It is planned for the published release of this document. -If you have something to contribute for this section please email it to -jht@samba.org/ -

    Features and Benefits

    +

    Features and Benefits

    We need feedback from people who are backing up samba servers. We would like to know what software tools you are using to backup your samba server/s.

    In particular, if you have any success and / or failure stories you could share with other users this would be appreciated. -

    Chapter 29. High Availability Options

    John H. Terpstra

    Samba Team

    Table of Contents

    Note

    Note

    +

    Chapter 29. High Availability Options

    John H. Terpstra

    Samba Team

    Table of Contents

    Note

    Note

    This chapter did not make it into this release. It is planned for the published release of this document. -

    Migration and Updating

    Table of Contents

    30. Upgrading from Samba-2.x to Samba-3.0.0
    Charsets
    Obsolete configuration options
    Password Backend
    31. Migration from NT4 PDC to Samba-3 PDC
    Planning and Getting Started
    Objectives
    Steps In Migration Process
    Migration Options
    Planning for Success
    Samba Implementation Choices
    32. SWAT - The Samba Web Administration Tool
    Features and Benefits
    Enabling SWAT for use
    Securing SWAT through SSL
    The SWAT Home Page
    Global Settings
    Share Settings
    Printers Settings
    The SWAT Wizard
    The Status Page
    The View Page
    The Password Change Page

    Chapter 30. Upgrading from Samba-2.x to Samba-3.0.0

    Jelmer R. Vernooij

    The Samba Team

    25 October 2002

    Table of Contents

    Charsets
    Obsolete configuration options
    Password Backend

    Charsets

    You might experience problems with special characters -when communicating with old DOS clients. Codepage -support has changed in samba 3.0. Read the chapter -Unicode support for details. -

    Obsolete configuration options

    -In 3.0, the following configuration options have been removed. -

    printer driver (replaced by new driver procedures)
    printer driver file (replaced by new driver procedures)
    printer driver location (replaced by new driver procedures)
    use rhosts
    postscript
    client code page (replaced by dos charset)
    vfs path
    vfs options

    Password Backend

    -Effective with the release of samba-3 it is now imperative that the password backend -be correctly defined in smb.conf. -

    -Those migrating from samba-2.x with plaintext password support need the following: -passdb backend = guest. -

    -Those migrating from samba-2.x with encrypted password support should add to smb.conf -passdb backend = smbpasswd, guest. -

    -LDAP using Samba-2.x systems can continue to operate with the following entry -passdb backend = ldapsam_compat, guest. -

    Chapter 31. 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 Implementation Choices

    +

    Migration and Updating

    Table of Contents

    30. Upgrading from Samba-2.x to Samba-3.0.0
    New Features in Samba-3
    Configuration Parameter Changes
    Removed Parameters
    New Parameters
    Modified Parameters (changes in behavior):
    New Functionality
    Databases
    Changes in Behavior
    Charsets
    Passdb Backends and Authentication
    Charsets
    LDAP
    31. 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
    32. SWAT - The Samba Web Administration Tool
    Features and Benefits
    Enabling SWAT for use
    Securing SWAT through SSL
    The SWAT Home Page
    Global Settings
    Share Settings
    Printers Settings
    The SWAT Wizard
    The Status Page
    The View Page
    The Password Change Page

    Chapter 30. Upgrading from Samba-2.x to Samba-3.0.0

    Jelmer R. Vernooij

    The Samba Team

    John H. Terpstra

    Samba Team

    Gerald (Jerry) Carter

    Samba Team

    June 30, 2003

    Table of Contents

    New Features in Samba-3
    Configuration Parameter Changes
    Removed Parameters
    New Parameters
    Modified Parameters (changes in behavior):
    New Functionality
    Databases
    Changes in Behavior
    Charsets
    Passdb Backends and Authentication
    Charsets
    LDAP

    New Features in Samba-3

    +Major new features: +

    1. + Active Directory support. This release is able to join a 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 now a much better infrastructure for multi-byte + 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 auth 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. This needs lots of testing. +

    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", at the moment only a few things are + implemented. +

    6. + Samba now negotiates NT-style status32 codes on the wire. This + improves error handling a lot. +

    7. + Better Windows 2000/XP/2003 printing support including publishing + printer attributes in active directory +

    8. + New loadable RPC modules +

    9. + New dual-daemon winbindd support (-B) 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. +

    +Plus lots of other improvements! +

    Configuration Parameter Changes

    +This section contains a brief listing of changes to smb.conf options +in the 3.0.0 release. Please refer to the smb.conf(5) man page for +complete descriptions of new or modified parameters. +

    Removed Parameters

    (order alphabetically):

    • admin log

    • alternate permissions

    • character set

    • client codepage

    • code page directory

    • coding system

    • domain admin group

    • domain guest group

    • force unknown acl user

    • nt smb support

    • post script

    • printer driver

    • printer driver file

    • printer driver location

    • status

    • total print jobs

    • use rhosts

    • valid chars

    • vfs options

    New Parameters

    (new parameters have been 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

    • set primary group script

    Authentication

    • auth methods

    • ads server

    • realm

    Protocol Options

    • client lanman auth

    • client NTLMv2 auth

    • client schannel

    • client signing

    • client use spnego

    • disable netbios

    • ntlm auth

    • paranoid server security

    • server schannel

    • smb ports

    • use spnego

    File Service

    • get quota command

    • hide special files

    • hide unwriteable files

    • hostname lookups

    • kernel change notify

    • mangle prefix

    • msdfs proxy

    • set quota command

    • use sendfile

    • vfs objects

    Printing

    • max reported print jobs

    UNICODE and Character Sets

    • display charset

    • dos charset

    • unicode

    • unix charset

    SID to uid/gid Mappings

    • idmap backend

    • idmap gid

    • idmap only

    • idmap uid

    LDAP

    • ldap delete dn

    • ldap group suffix

    • ldap idmap suffix

    • ldap machine suffix

    • ldap passwd sync

    • ldap trust ids

    • ldap user suffix

    General Configuration

    • preload modules

    • privatedir

    Modified Parameters (changes in behavior):

    • encrypt passwords (enabled by default)

    • mangling method (set to 'hash2' by default)

    • passwd chat

    • passwd program

    • restrict anonymous (integer value)

    • security (new 'ads' value)

    • strict locking (enabled by default)

    • winbind cache time (increased to 5 minutes)

    • winbind uid (deprecated in favor of 'idmap uid')

    • winbind gid (deprecated in favor of 'idmap gid')

    New Functionality

    Databases

    + This section contains brief descriptions of any new databases + introduced in Samba 3.0. Please remember to backup your existing + ${lock directory}/*tdb before upgrading to Samba 3.0. Samba will + upgrade databases as they are opened (if necessary), but downgrading + from 3.0 to 2.2 is an unsupported path. +

    Table 30.1. TDB File Descriptions

    NameDescriptionBackup?
    account_policyUser policy settingsyes
    gencacheGeneric caching dbno
    group_mapping

    Mapping table from Windows groups/SID to unix groups

    		yes
    idmap

    new ID map table from SIDS to UNIX uids/gids

    		yes
    namecacheName resolution cache entriesno
    netlogon_unigrp

    Cache of universal group membership obtained when operating + as a member of a Windows domain

    		no
    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 db tables via the winreg RPCs

    		no

    Changes in Behavior

    + The following issues are known changes in behavior between Samba 2.2 and + Samba 3.0 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.0 + rejects the connection as NT_STATUS_LOGON_FAILURE. There is no + current work around to re-establish the 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.0 introduces a new 'add machine + script' that must be specified for this purpose. Samba 3.0 will + not fall back to using the 'add user script' in the absence of + an 'add machine script' +

    Charsets

    + You might experience problems with special characters when communicating with old DOS + clients. Codepage support has changed in samba 3.0. Read the chapter + Unicode support for details. +

    Passdb Backends and Authentication

    + There have been a few new changes that Samba administrators should be + aware of when moving to Samba 3.0. +

    1. + Encrypted passwords have been enabled by default in order to + inter-operate 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.0 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 the chapter about 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(8) tool have been split between the + new smbpasswd(8) utility, the net(8) tool, and the new pdbedit(8) + utility. See the respective man pages for details. +

    Charsets

    + You might experience problems with special characters when communicating with old DOS + clients. Codepage support has changed in samba 3.0. Read the chapter + Unicode support for details. +

    LDAP

    + This section outlines the new features affecting Samba / LDAP integration. +

    New Schema

    + A new object class (sambaSamAccount) has been introduced to replace + the old sambaAccount. This change aids us in the renaming of attributes + to prevent clashes with attributes from other vendors. There is a + conversion script (examples/LDAP/convertSambaAccount) to modify and LDIF + file to the new schema. +

    + Example: + 

    +		$ ldapsearch .... -b "ou=people,dc=..." > old.ldif
+		$ convertSambaAccount <DOM SID> old.ldif new.ldif
+

    + The <DOM SID> can be obtained by running 'net getlocalsid <DOMAINNAME> + on the Samba PDC as root. +

    + 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 + the schema file and must be uncommented before use if needed. + The 2.2 object class declaration for a sambaAccount has not changed + in the 3.0 samba.schema file. +

    + 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

    + 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 sub-suffix parameters. In this case, the order of the suffix + listings in smb.conf is important. Always place the 'ldap suffix' first + in the list. +

    + Due to a limitation in Samba's smb.conf parsing, you should not surround + the DN's with quotation marks. +

    IdMap LDAP support

    + Samba 3.0 supports an ldap backend for the idmap subsystem. The + following options would inform Samba that the idmap table should be + stored on the directory server onterose in the "ou=idmap,dc=plainjoe, + dc=org" partition. +

    [global]
    ...
    idmap backend = ldap:ldap://onterose/
    ldap idmap suffix = ou=idmap,dc=plainjoe,dc=org
    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. +

    Chapter 31. 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. @@ -14990,120 +14347,133 @@ and planned for. Then again, good planning will anticipate most show stopper typ 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 under way. -

    Objectives

    +

    Objectives

    The key objective for most organisations will be 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 one of 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.

    -It is strongly advised that before attempting a migration to a Samba-3 controlled network -that every possible effort be made to gain all-round commitment to the change. Firstly, you -should know precisely why the change is important for the organisation. -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 organisation's dependency on Microsoft

    -It is vital that it be well recognised that Samba-3 is NOT MS Windows NT4. Samba-3 offers -an alternative solution that is both different from MS Windows NT4 and that offers some -advantages compared with it. It should also be recognised that Samba-3 lacks many of the +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 organisation. 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 organisation's dependency on Microsoft

    +Make sure that 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 that offers +advantages compared with it. Gain recognition that Samba-3 lacks many of the features that Microsoft has promoted as core values in migration from MS Windows NT4 to MS Windows 2000 and beyond (with or without Active Directory services).

    What are the features that Samba-3 can NOT 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 includes: -

    Lower Cost of Ownership
    Global availability of support with no strings attached
    Dynamic SMB Servers (ie:Can run more than one 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 back-end authentication technologies (tdbsam, ldapsam, mysqlsam)
    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 it is vital that all necessary factors are -considered. Users should be educated about changes they may experience so that the change will be a -welcome one and not become an obstacle to the work they need to do. The following are some of the -factors that will go into a successful migration: -

    Domain Layout

    +

    • Lower Cost of Ownership

    • Global availability of support with no strings attached

    • Dynamic SMB Servers (ie:Can run more than one 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 back-end authentication technologies (tdbsam, ldapsam, mysqlsam)

    • 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 that the change will be a welcome one +and not become an obstacle to the work they need to do. The following are factors that will +help ensure a successful migration: +

    Domain Layout

    Samba-3 can be configured as a domain controller, a back-up domain controller (probably best called a secondary controller), a domain member, or as a stand-alone server. The Windows network security domain context should be sized and scoped before implementation. Particular attention needs to be paid to the location of the primary domain controller (PDC) as well as backup controllers (BDCs). -It should be noted that one way in which Samba-3 differs from Microsoft technology is that if one -chooses to use an LDAP authentication backend then the same database can be used by several different -domains. This means that in a complex organisation there can be a single LDAP database, that itself -can be distributed, that can simultaneously serve multiple domains (that can also be widely distributed). -

    -It is recommended that from a design perspective, the number of users per server, as well as the number -of servers, per domain should be scaled according to needs and should also consider server capacity -and network bandwidth. -

    -A physical network segment may house several domains, each of which may span multiple network segments. -Where domains span routed network segments it is most advisable to consider and test the performance -implications of the design and layout of a network. A Centrally located domain controller that is being -designed to serve multiple routed network segments may result in severe performance problems if the -response time (eg: ping timing) between the remote segment and the PDC is more than 100 ms. In situations -where the delay is too long it is highly recommended to locate a backup controller (BDC) to serve as -the local authentication and access control server. -

    Server Share and Directory Layout

    -There are few cardinal rules to effective network design that can be broken with impunity. -The most important rule of effective network management is that 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. -

    -The nature of the data that must be stored needs to be born in mind when deciding how many -shares must be created. The physical disk space layout should also be taken into account -when designing where share points will be created. Keep in mind that all data needs to be -backed up, thus the simpler the disk layout the easier it will be to keep track of what must -be backed up to tape or other off-line storage medium. Always plan and implement for minimum +One way in which Samba-3 differs from Microsoft technology is that if one chooses to use an LDAP +authentication backend then the same database can be used by several different domains. In a +complex organisation there can be a single LDAP database, which itself can be distributed (ie: 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 (eg: ping timing) between the remote segment and the PDC. If long (more than 100 ms) +locate a backup controller (BDC) on the remote segmanet to serve as the local authentication and +access control server. +

    Server Share and Directory Layout

    +There are cardinal rules to effective network design. These can not 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 share. 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 backed needs. Identify what back media will be meet needs, consider backup to tape +, CD-ROM or (DVD-ROM), or other off-line storage medium. Plan and implement for minimum maintenance. Leave nothing to chance in your design, above all, do not leave backups to chance: Backup and test, 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 +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.

    -Many network administrators who are new to the game will attempt to use elaborate techniques -to set access controls, on files, directories, shares, as well as in share definitions. -There is the ever present danger that that administrator's successor will not understand the -complex mess that has been inherited. Remember, apparent job security through complex design -and implementation may ultimately cause loss of operations and downtime to users as the new -administrator learns to untangle your web. Keep access controls simple and effective and -make sure that users will never be interrupted by the stupidity of complexity. -

    Logon Scripts

    -Please refer to the section of this document on Advanced Network Administration for information -regarding the network logon script options for Samba-3. Logon scripts can help to ensure that -all users gain share and printer connections they need. -

    -Logon scripts can be created on-the-fly so that all commands executed are specific to the -rights and privileges granted to the user. The preferred controls should be affected through +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 +audit your documentation. Do not create a complex mess that your successor will not understand. +Remember, job security through complex design and implementation may cause loss of operations +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 stupid +complexity. +

    Logon Scripts

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

    +Logon scripts can be created 'on-the-fly' so that all commands executed are specific to the +rights and priviliges granted to the user. The preferred controls should be affected through group membership so that group information can be used to custom create a logon script using -the root preexec parameters to the NETLOGON share. +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 knowledgebase 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 it is STRONGLY advised to create in Samba-3 the -groups that are present on the MS Windows NT4 domain AND to connect these to -suitable Unix/Linux groups. Following this simple advice will mean that all user and group attributes +groups that are present on the MS Windows NT4 domain AND to map these 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 will have an NT4 PDC that has the users, groups, policies and profiles to be migrated

    • -Samba-3 set up as a DC with netlogon share, profile share, etc. -

    Procedure 31.1. The Account Migration Process

    1. Create a BDC account for the samba server using NT Server Manager

      1. Samba must NOT be running

    2. rpcclient NT4PDC -U Administrator%passwd

      1. lsaquery

      2. Note the SID returned

    3. net getsid -S NT4PDC -w DOMNAME -U Administrator%passwd

      1. Note the SID

    4. net getlocalsid

      1. Note the SID, now check that all three SIDS reported are the same!

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

    6. net rpc vampire -S NT4PDC -U administrator%passwd

    7. pdbedit -L

      1. Note - did the users migrate?

    8. initGrps.sh DOMNAME

    9. net groupmap list

      1. Now check that all groups are recognised

    10. net rpc vampire -S NT4PDC -U administrator%passwd

    11. pdbedit -Lv

      1. Note - check that all group membership has been migrated

    -Now it is time to migrate all the profiles, then migrate all policy files. -More later. -

    Migration Options

    -Based on feedback from many sites as well as from actual installation and maintenance -experience sites that wish to migrate from MS Windows NT4 Domain Control to a Samba -based solution fit into three basic categories. -

    Table 31.1. The 3 Major Site Types

    Number of UsersDescription
    < 50

    Want simple conversion with NO pain

    50 - 250

    Want new features, can manage some in-house complexity

    > 250

    Solution/Implementation MUST scale well, complex needs. Cross departmental decision process. Local expertise in most areas

    Planning for Success

    +Samba-3 set up as a DC with netlogon share, profile share, etc. Configure the smb.conf file +to fucntion as a BDC. ie: domain master = No. +

    Procedure 31.1. The Account Migration Process

    1. Create a BDC account for the samba server using NT Server Manager

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

      1. Note - did the users migrate?

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

      +#!/bin/bash
+#### Keep this as a shell script for future re-use
+			
+# First assign well known domain global groups
+net groupmap modify ntgroup="Domain Admins" unixgroup=ntadmins
+net groupmap modify ntgroup="Domain Guests" unixgroup=nobody
+net groupmap modify ntgroup="Domain Users" unixgroup=users
+
+# Now for our added domain global groups
+net groupmap add ntgroup="Designers" unixgroup=designers type=d rid=3200
+net groupmap add ntgroup="Engineers" unixgroup=engineers type=d rid=3210
+net groupmap add ntgroup="QA Team"   unixgroup=qateam    type=d rid=3220
+

      +

    6. net groupmap list

      1. Now check that all groups are recognised

    +Now migrate all the profiles, then migrate all policy files. +

    Migration Options

    +Sites that wish to migrate from MS Windows NT4 Domain Control to a Samba based solution +generally fit into three basic categories. +

    Table 31.1. The 3 Major Site Types

    Number of UsersDescription
    < 50

    Want simple conversion with NO pain

    50 - 250

    Want new features, can manage some in-house complexity

    > 250

    Solution/Implementation MUST scale well, complex needs. 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.

    • @@ -15113,7 +14483,7 @@ to Samba-3.

    • Complete Redesign (completely new solution)

    -No matter what choice you make, the following rules will minimise down-stream problems: +Minimise down-stream problems by:

    • Take sufficient time

    • @@ -15122,65 +14492,28 @@ No matter what choice you make, the following rules will minimise down-stream pr Test ALL assumptions

    • Test full roll-out program, including workstation deployment -

    Table 31.2. Nature of the Conversion Choices

    SimpleUpgradedRedesign

    Make use of minimal OS specific features

    Translate NT4 features to new host OS features

    Decide:

    Suck 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

    Minimise user impact

    Better Control of Desktops / Users

    Live versus Isolated Conversion

    Maximise functionality

    Identify Needs for: Manageability, Scalability, Security, Availability

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

    Take advantage of lower maintenance opportunity

    Samba Implementation Choices

    -Authentication database back end
-	Winbind (external Samba or NT4/200x server)
-	Can use pam_mkhomedir.so to auto-create home dirs
-	External server could use Active Directory or NT4 Domain
-
-Database type
-	smbpasswd, tdbsam, ldapsam, mysqlsam
-
-Access Control Points
-	On the Share itself (Use NT4 Server Manager)
-	On the file system
-	Unix permissions on files and directories
-	Enable Posix ACLs in file system?
-	Through Samba share parameters
-		Not recommended - except as only resort
-
-Policies (migrate or create new ones)
-	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
-	username map facility may be needed
-	Use 'net groupmap' to connect NT4 groups to Unix groups
-	Use pdbedit to set/change user configuration
-NOTE:
-If migrating to LDAP back end it may be easier to dump initial LDAP database
-to LDIF, then edit, then reload into LDAP
-
-	OS specific scripts / programs may be needed
-		Add / delete Users
-			Note OS limits on size of name (Linux 8 chars)
-				NT4 up to 254 chars
-		Add / delete machines
-			Applied only to domain members (note up to 16 chars)
-		Add / delete Groups
-			Note OS limits on size and nature
-				Linux limit is 16 char,
-				no spaces and no upper case chars (groupadd)
-
-Migration Tools
-	Domain Control (NT4 Style)
-	Profiles, Policies, Access Controls, Security
-
-Migration Tools
-	Samba: net, rpcclient, smbpasswd, pdbedit, profiles
-	Windows: NT4 Domain User Manager, Server Manager (NEXUS)
-
-Authentication
-	New SAM back end (smbpasswd, tdbsam, ldapsam, mysqlsam)
-

    -

    Chapter 32. SWAT - The Samba Web Administration Tool

    John H. Terpstra

    Samba Team

    April 21, 2003

    Table of Contents

    Features and Benefits
    Enabling SWAT for use
    Securing SWAT through SSL
    The SWAT Home Page
    Global Settings
    Share Settings
    Printers Settings
    The SWAT Wizard
    The Status Page
    The View Page
    The Password Change Page

    +

    Table 31.2. Nature of the Conversion Choices

    SimpleUpgradedRedesign

    Make use of minimal OS specific features

    Translate NT4 features to new host OS features

    Decide:

    Suck 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

    Minimise user impact

    Better Control of Desktops / Users

    Live versus Isolated Conversion

    Maximise functionality

    Identify Needs for: Manageability, Scalability, Security, Availability

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

    Take advantage of lower maintenance opportunity

    Samba-3 Implementation Choices

    Authentication database/back end:

    + 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 auto-create home dirs

    +

    + Samba-3 can use a local authentication backend: +

    • smbpasswd, tdbsam, ldapsam, mysqlsam

    +

    Access Control Points:

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

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

    • username map facility may be needed

    • Use 'net groupmap' to connect NT4 groups to Unix groups

    • Use pdbedit to set/change user configuration

      + NOTE: When migrating to LDAP back, end it may be easier to dump initial + LDAP database to LDIF, then edit, then reload into LDAP +

    OS specific scripts/programs may be needed:

    • Add/Delete Users: Note OS limits on size of name + (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 upper case 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)

    +

    Chapter 32. SWAT - The Samba Web Administration Tool

    John H. Terpstra

    Samba Team

    April 21, 2003

    Table of Contents

    Features and Benefits
    Enabling SWAT for use
    Securing SWAT through SSL
    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 or otherwise 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 will allow web based configuration @@ -15188,7 +14521,7 @@ of samba. It has a wizard that may help to get samba configured quickly, it has sensitive help on each smb.conf parameter, it provides for monitoring of current state of connection information, and it allows network wide MS Windows network password management. -

    Features and Benefits

    +

    Features and Benefits

    There are network administrators who believe that it is a good idea to write systems documentation inside configuration files, for them SWAT will aways be a nasty tool. SWAT does not store the configuration file in any intermediate form, rather, it stores only the @@ -15200,9 +14533,9 @@ internal ordering. So before using SWAT please be warned - SWAT will completely replace your smb.conf with a fully optimised file that has been stripped of all comments you might have placed there and only non-default settings will be written to the file. -

    Enabling SWAT for use

    +

    Enabling SWAT for use

    SWAT should be installed to run via the network super daemon. Depending on which system -your Unix/Linux system has you will have either an inetd or +your UNIX/Linux system has you will have either an inetd or xinetd based system.

    The nature and location of the network super-daemon varies with the operating system @@ -15254,7 +14587,7 @@ So long as you log onto SWAT as the user rootHOME, GLOBALS, SHARES, PRINTERS, WIZARD, STATUS, VIEW, PASSWORD. -

    Securing SWAT through SSL

    +

    Securing SWAT through SSL

    Lots of people have asked about how to setup SWAT with SSL to allow for secure remote administration of Samba. Here is a method that works, courtesy of Markus Krieger

    @@ -15264,38 +14597,37 @@ Modifications to the swat setup are as following:

  • generate certificate and private key - 

    +
     root# /usr/bin/openssl req -new -x509 -days 365 -nodes -config \
- 	/usr/share/doc/packages/stunnel/stunnel.cnf \
+	/usr/share/doc/packages/stunnel/stunnel.cnf \
 	-out /etc/stunnel/stunnel.pem -keyout /etc/stunnel/stunnel.pem
-

  • +

  • remove swat-entry from [x]inetd

  • start stunnel - 

    +
     root# stunnel -p /etc/stunnel/stunnel.pem -d 901 \
 	 -l /usr/local/samba/bin/swat swat 
-

    • +

    afterwords simply contact to swat by using the URL https://myhost:901, accept the certificate and the SSL connection is up. -

    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 Samba-HOWTO-Collection (this -document) as well as the O'Reilly book "Using Samba". +document) as well as the O'Reilly book "Using Samba".

    Administrators who wish to validate their samba configuration may obtain useful information from the man pages for the diagnostic utilities. These are available from the SWAT home page also. One diagnostic tool that is NOT mentioned on this page, but that is particularly -useful is ethereal, available from -http://www.ethereal.com. +useful is ethereal.

    Warning

    SWAT can be configured to run in demo mode. This is NOT recommended as it runs SWAT without authentication and with full administrative ability. ie: Allows 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 any production environment. -

    Global Settings

    +

    Global Settings

    The Globals button will expose a page that allows configuration of the global parameters in smb.conf. There are three levels of exposure of the parameters:

    • @@ -15308,8 +14640,8 @@ in smb.conf. There are three levels of exposure of the parameters: will want to tamper with.

    To switch to other than Basic editing ability click on either the -Advanced or the Developer dial, then click the -Commit Changes button. +Advanced or the Developer button. You may also +do this by clicking on the radio button, then click the Commit Changes button.

    After making any changes to configuration parameters make sure that you click on the Commit Changes button before moving to another area otherwise @@ -15317,7 +14649,7 @@ your changes will be immediately lost.

    Note

    SWAT has context sensitive help. To find out what each parameter is for simply click 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, select the share you wish to operate on, then to edit the settings click on the @@ -15327,7 +14659,7 @@ select the share you wish to operate on, then to edit the settings click on the To create a new share, next to the button labelled 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, select the printer you wish to operate on, then to edit the settings click on the @@ -15337,7 +14669,7 @@ select the printer you wish to operate on, then to edit the settings click on th To create a new printer, next to the button labelled 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 if the SWAT Wizard is to help the Microsoft knowledgeable network administrator to configure Samba with a minimum of effort.

    @@ -15353,7 +14685,7 @@ Finally, there are a limited set of options that will determine what type of ser will be configured for, whether it will be a WINS server, participate as a WINS client, or operate with no WINS support. By clicking on 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. Firstly, it allows control of the samba daemons. The key daemons that create the samba server environment are: smbd, nmbd, winbindd.

    @@ -15364,11 +14696,11 @@ conditions with minimal effort.

    Lastly, 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

    This page allows the administrator to view the optimised smb.conf file and, if you are particularly masochistic, will permit 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. This tool allows the creation, deletion, deactivation and reactivation of MS Windows networking users on the local machine. Alternatively, you can use this tool to change a local password for a user account. @@ -15379,7 +14711,7 @@ required.

    One popular use for this tool is to change user passwords across a range of remote MS Windows servers. -

    Troubleshooting

    Table of Contents

    33. The Samba checklist
    Introduction
    Assumptions
    The tests
    Still having troubles?
    34. Analysing and solving samba problems
    Diagnostics tools
    Installing 'Network Monitor' on an NT Workstation or a Windows 9x box
    Useful URLs
    Getting help from the mailing lists
    How to get off the mailing lists
    35. Reporting Bugs
    Introduction
    General info
    Debug levels
    Internal errors
    Attaching to a running process
    Patches

    Chapter 33. The Samba checklist

    Andrew Tridgell

    Samba Team

    Jelmer R. Vernooij

    The Samba Team

    Wed Jan 15

    Table of Contents

    Introduction
    Assumptions
    The tests
    Still having troubles?

    Introduction

    +

    Troubleshooting

    Table of Contents

    33. The Samba checklist
    Introduction
    Assumptions
    The tests
    34. Analysing and solving samba problems
    Diagnostics tools
    Debugging with Samba itself
    Tcpdump
    Ethereal
    The Windows Network Monitor
    Useful URLs
    Getting help from the mailing lists
    How to get off the mailing lists
    35. Reporting Bugs
    Introduction
    General info
    Debug levels
    Internal errors
    Attaching to a running process
    Patches

    Chapter 33. The Samba checklist

    Andrew Tridgell

    Samba Team

    Jelmer R. Vernooij

    The 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 @@ -15391,10 +14723,10 @@ the earlier tests. However, do not stop at the first error as there have been some instances when continuing with the tests has helped to solve a problem.

    -If you send one of the samba mailing lists an email saying "it doesn't work" +If you send one of the samba mailing lists an email saying "it doesn't work" and you have not followed this test procedure then 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.

    @@ -15404,14 +14736,7 @@ It is also assumed you know the name of an available share in your smb.conf. I will assume this share is called tmp. You can add a tmp share like this by adding the following to smb.conf: -

    -
-[tmp]
- comment = temporary files 
- path = /tmp
- read only = yes
-
-

    +

    Example 33.1. smb.conf with [tmp] share

    [tmp]
    comment = temporary files
    path = /tmp
    read only = yes

    Note

    These tests assume version 3.0 or later of the samba suite. Some commands shown did not exist in earlier versions. @@ -15424,7 +14749,7 @@ 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). @@ -15435,7 +14760,7 @@ depending on how or if you specified logging in your smb.co

    If you make changes to your smb.conf file while going through these test, don't forget to restart smbd and nmbd. -

    The tests

    Procedure 33.1. Diagnosing your samba server

    1. +

    The tests

    Procedure 33.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. @@ -15448,7 +14773,7 @@ Run the command ping BIGSERVER from the PC and the unix box. If you don't get a valid response then your TCP/IP software is not correctly installed.

      -Note that you will need to start a "dos prompt" window on the PC to +Note that 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 similar then your DNS @@ -15468,7 +14793,7 @@ This is a common problem that is often overlooked. Run the command smbclient -L BIGSERVER on the unix box. You should get a list of available shares back.

      -If you get a error message containing the string "Bad password" then +If you get a error message containing the string "Bad password" then you probably have either an incorrect hosts allow, hosts deny or valid users line in your smb.conf, or your guest account is not @@ -15481,13 +14806,15 @@ 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 file/s for your particular system implementation of this network super daemon.

      If you get a session request failed then the server refused the -connection. If it says "Your server software is being unfriendly" then +connection. If it says "Your server software is being unfriendly" then its probably because you have invalid command line parameters to smbd, or a similar fatal problem with the initial startup of smbd. Also check your config file (smb.conf) for syntax errors with testparm @@ -15497,26 +14824,20 @@ 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 following smb.conf file entries: -

      -	hosts deny = ALL
-	hosts allow = xxx.xxx.xxx.xxx/yy
-	bind interfaces only = Yes
-

      +

      hosts deny = ALL
      hosts allow = xxx.xxx.xxx.xxx/yy
      bind interfaces only = Yes

      In the above, 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 to: -

      -	hosts deny = ALL
-	hosts allow = xxx.xxx.xxx.xxx/yy 127.
-

      -Do not use the bind interfaces only parameter where you +

      hosts deny = ALL
      hosts allow = xxx.xxx.xxx.xxx/yy 127.

      +Do not use the bind interfaces only parameter where you may wish to use the samba password change facility, or where smbclient may need to access a local service for name resolution or for local resource -connections. (Note: the bind interfaces only parameter deficiency +connections. (Note: the bind interfaces only parameter deficiency where it will not allow connections to the loopback address will be fixed soon).

      + Another common cause of these two errors is having something already running on port 139, such as Samba (ie: smbd is running from inetd already) or @@ -15559,20 +14880,20 @@ messages from several hosts. If this doesn't give a similar result 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 +interfaces option in smb.conf to manually configure your IP address, broadcast and netmask.

      If your PC and server aren't on the same subnet then you will need to -use the -B option to set the broadcast address to that of the PCs +use the -B option to set the broadcast address to that of the PCs subnet.

      This test will probably fail if your subnet mask and broadcast address are not correct. (Refer to TEST 3 notes above). -

    2. +

    3. Run the command smbclient //BIGSERVER/TMP. You should then be prompted for a password. You should use the password of the account you are logged into the unix box with. If you want to test with -another account then add the -U accountname option to the end of +another account then add the -U accountname option to the end of the command line. eg: smbclient //bigserver/tmp -Ujohndoe

      Note

      @@ -15582,21 +14903,20 @@ as follows:

      Once you enter the password you should get the smb> prompt. If you don't then look at the error message. If it says invalid network -name then the service "tmp" is not correctly setup in your smb.conf. +name then the service "tmp" is not correctly setup in your smb.conf.

      If it says bad password then the likely causes are:

      1. you have shadow passwords (or some other password system) but didn't compile in support for them in smbd

      2. - your valid users configuration is incorrect + your valid users configuration is incorrect

      3. - you have a mixed case password and you haven't enabled the password - level option at a high enough level + you have a mixed case password and you haven't enabled the password level option at a high enough level

      4. - the path = line in smb.conf is incorrect. Check it with testparm + the path line in smb.conf is incorrect. Check it with testparm

      5. - you enabled password encryption but didn't map unix to samba users + you enabled password encryption but didn't map unix to samba users. Run 

        smbpasswd -a username

        .

      Once connected you should be able to use the commands dir get put etc. @@ -15605,7 +14925,7 @@ especially check that the amount of free disk space shown is correct when you type dir.

    4. 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 +need to do this from within a "dos prompt" window. You should get back a list of available shares on the server.

      If you get a network name not found or similar error then netbios @@ -15646,14 +14966,13 @@ installed or your smb.conf is incorrect. make sure your hosts and other config lines in smb.conf are correct.

      It's also possible that the server can't work out what user name to -connect you as. To see if this is the problem add the line user = -username to the [tmp] section of +connect you as. To see if this is the problem add the line user = username to the [tmp] section of smb.conf where username is the username corresponding to the password you typed. If you find this fixes things you may need the username mapping option.

      It might also be the case that your client only sends encrypted passwords -and you have encrypt passwords = no in smb.conf +and you have encrypt passwords = no in smb.conf Turn it back on to fix.

    5. Run the command nmblookup -M testgroup where @@ -15664,30 +14983,33 @@ master browser for that workgroup. If you don't then the election process has failed. Wait a minute to see if it is just being slow then try again. If it still fails after that then look at the browsing options you have set in smb.conf. Make -sure you have preferred master = yes to ensure that +sure you have preferred master = yes to ensure that an election is held at startup.

    6. ->From file manager try to browse the server. Your samba server should +From file manager try to browse the server. Your samba server should appear in the browse list of your local workgroup (or the one you -specified in smb.conf). You should be able to double click on the name -of the server and get a list of shares. If you get a "invalid -password" error when you do then you are probably running WinNT and it +specified in smb.conf). You should be able to double click on the name +of the server and get a list of shares. If you get a "invalid +password" error when you do then you are probably running WinNT and it is refusing to browse a server that has no encrypted password capability and is in user level security mode. In this case either set -security = server AND -password server = Windows_NT_Machine in your -smb.conf file, or make sure encrypted passwords is -set to "yes". -

    Still having troubles?

    Read the chapter on -Analysing and Solving Problems. -

    Chapter 34. Analysing and solving samba problems

    Gerald (Jerry) Carter

    Samba Team

    Jelmer R. Vernooij

    The Samba Team

    David Bannon

    Samba Team

    8 Apr 2003

    Table of Contents

    Diagnostics tools
    Installing 'Network Monitor' on an NT Workstation or a Windows 9x box
    Useful URLs
    Getting help from the mailing lists
    How to get off the mailing lists

    +security = server AND +password server = Windows_NT_Machine in your +smb.conf file, or make sure encrypt passwords is +set to "yes". +

    Chapter 34. Analysing and solving samba problems

    Gerald (Jerry) Carter

    Samba Team

    Jelmer R. Vernooij

    The Samba Team

    David Bannon

    Samba Team

    8 Apr 2003

    Table of Contents

    Diagnostics tools
    Debugging with Samba itself
    Tcpdump
    Ethereal
    The Windows Network Monitor
    Useful URLs
    Getting help from the mailing lists
    How to get off the mailing lists

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

    Diagnostics tools

    +general SMB topics such as browsing.

    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, analyses the data sent on it and displays it +on the screen.

    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 what -debug level at which to run. See the man pages on smbd, nmbd and +debug level at which to run. See the man pages on smbd, nmbd and smb.conf for more information on debugging options. The debug level can range from 1 (the default) to 10 (100 for debugging passwords).

    @@ -15706,14 +15028,19 @@ typing in your password, you can attach gdb and continue.

    Some useful samba commands worth investigating: 

    -	$ testparm | more
-	$ smbclient -L //{netbios name of server}
-

    -An SMB enabled version of tcpdump is available from -http://www.tcpdup.org/. -Ethereal, another good packet sniffer for Unix and Win32 -hosts, can be downloaded from http://www.ethereal.com. -

    +$ testparm | more +$ smbclient -L //{netbios name of server} +

    Tcpdump

    Tcpdump was the first +unix sniffer with SMB support. It is a command-line utility and +nowadays, it's SMB support is somewhat less then that of ethereal +and tethereal.

    Ethereal

    +Ethereal is a graphical +sniffer, available for both unix (Gtk) and Windows. Ethereal's +SMB support is very good.

    For details on the use of ethereal, read the well-written +ethereal User Guide.

    +Listen for data on ports 137, 138, 139 and 445. E.g. +use the filter port 137 or port 138 or port 139 or port 445.

    A console version of ethereal is available as well and is called +tethereal.

    The Windows Network Monitor

    For tracing things on the Microsoft Windows NT, Network Monitor (aka. netmon) is available on the Microsoft Developer Network CD's, the Windows NT Server install CD and the SMS CD's. The version of @@ -15723,7 +15050,7 @@ 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 or a Windows 9x box

    +

    Installing 'Network Monitor' on an NT Workstation

    Installing netmon on an NT workstation requires a couple of steps. The following are for installing Netmon V4.00.349, which comes with Microsoft Windows NT Server 4.0, on Microsoft Windows NT @@ -15756,17 +15083,17 @@ Now copy the files from the NT Server in %SYSTEMROOT%\Syste 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 an 9x Workstation

    To install Netmon on a Windows 9x box install the network monitor agent from the Windows 9x CD (\admin\nettools\netmon). There is a readme file located with the netmon driver files on the CD if you need information on how to do this. Copy the files from a working Netmon installation. -

    Useful URLs

    • See how Scott Merrill simulates a BDC behavior at +

    Useful URLs

    Getting help from the mailing lists

    + ftp://ftp.microsoft.com/developr/drg/CIFS/

    Getting help from the mailing lists

    There are a number of Samba related mailing lists. Go to http://samba.org, click on your nearest mirror and then click on Support and then click on Samba related mailing lists. @@ -15776,10 +15103,10 @@ For questions relating to Samba TNG go to It has been requested that you don't post questions about Samba-TNG to the main stream Samba lists.

    If you post a message to one of the lists please observe the following guide lines : -

    • Always remember that the developers are volunteers, they are +

      • Always remember that the developers are volunteers, they are not paid and they never guarantee to produce a particular feature at a particular time. Any time lines are 'best guess' and nothing more. -

      • Always mention what version of samba you are using and what +

      • Always mention what version of samba you are using and what operating system its running under. You should probably list the relevant sections of your smb.conf file, at least the options in [global] that affect PDC support.

      • In addition to the version, if you obtained Samba via @@ -15800,15 +15127,14 @@ error messages.

      • (Possibly) If you have a complete netmon trace ( 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 +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 you went to to get on it. Go to http://lists.samba.org, click on your nearest mirror and then click on Support and -then click on Samba related mailing lists. Or perhaps see -here +then click on Samba related mailing lists.

    Please don't post messages to the list asking to be removed, you will just be referred to the above address (unless that process failed in some way...) -

    Chapter 35. Reporting Bugs

    Jelmer R. Vernooij

    The Samba Team

    Someone; Tridge or Karl Auer perhaps?

    27 June 1997

    Table of Contents

    Introduction
    General info
    Debug levels
    Internal errors
    Attaching to a running process
    Patches

    Introduction

    Please report bugs using +

    Chapter 35. Reporting Bugs

    Jelmer R. Vernooij

    The Samba Team

    Andrew Tridgell

    Samba Team

    27 June 1997

    Table of Contents

    Introduction
    General info
    Debug levels
    Internal errors
    Attaching to a running process
    Patches

    Introduction

    Please report bugs using bugzilla.

    Please take the time to read this file before you submit a bug report. Also, please see if it has changed between releases, as we @@ -15818,7 +15144,7 @@ Please also do as much as you can yourself to help track down the bug. Samba is maintained by a dedicated group of people who volunteer their time, skills and efforts. We receive far more mail about it than we can possibly answer, so you have a much higher chance of an answer -and a fix if you send us a "developer friendly" bug report that lets +and a fix if you send us a "developer friendly" bug report that lets us fix it fast.

    Do not assume that if you post the bug to the comp.protocols.smb @@ -15830,7 +15156,7 @@ that list that 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 info

    +

    General info

    Before submitting a bug report check your config for silly errors. Look in your log files for obvious messages that tell you that you've misconfigured something and run testparm to test your config @@ -15842,42 +15168,38 @@ This is very important. If you include part of a log file with your bug report then be sure to annotate it with exactly what you were doing on the client at the time, and exactly what the results were. -

    Debug levels

    +

    Debug levels

    If the bug has anything to do with Samba behaving incorrectly as a server (like refusing to open a file) then the log files will probably be very 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 +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 use: -

    -log level = 10
-log file = /usr/local/samba/lib/log.%m
-include = /usr/local/samba/lib/smb.conf.%m
-

    +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

    then 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 you to +log level may be useful. This also allows you to experiment with different security systems, protocol levels etc on just one machine.

    -The smb.conf entry log level -is synonymous with the parameter debuglevel that has +The smb.conf entry log level +is synonymous with the parameter debuglevel that has been used in older versions of Samba and is being retained for backwards compatibility of smb.conf files.

    -As the log level value is increased you will record +As the log level value is increased you will record a significantly increasing level of 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 VERY large volume of log data. -

    Internal errors

    +

    Internal errors

    If you get a INTERNAL ERROR message 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 @@ -15890,13 +15212,13 @@ 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
+
    +$ gdb smbd core
 
    
 adding appropriate paths to smbd and core so gdb can find them. If you
 don't have gdb then try dbx. Then within the debugger
@@ -15910,7 +15232,7 @@ 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
 don't know assembly, including this info 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 @@ -15920,34 +15242,33 @@ to the running process using Then use c to continue and try to cause the core dump using the client. The debugger should catch the fault and tell you where it occurred. -

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

    Appendixes

    Table of Contents

    36. How to compile SAMBA
    Access Samba source code via CVS
    Introduction
    CVS 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 and nmbd
    Starting from inetd.conf
    Alternative: starting it as a daemon
    Common Errors
    37. Portability
    HPUX
    SCO Unix
    DNIX
    RedHat Linux Rembrandt-II
    AIX
    Sequential Read Ahead
    Solaris
    Locking improvements
    Winbind on Solaris 9
    38. Samba and other CIFS clients
    Macintosh clients?
    OS2 Client
    How can I configure OS/2 Warp Connect or - OS/2 Warp 4 as a client for Samba?
    How can I configure OS/2 Warp 3 (not Connect), - OS/2 1.2, 1.3 or 2.x for Samba?
    How do I get printer driver download working - for OS/2 clients?
    Windows for Workgroups
    Use latest TCP/IP stack from Microsoft
    Delete .pwl files after password change
    Configure WfW password handling
    Case handling of passwords
    Use TCP/IP as default protocol
    Speed improvement
    Windows '95/'98
    Speed improvement
    Windows 2000 Service Pack 2
    Windows NT 3.1
    39. Samba Performance Tuning
    Comparisons
    Socket options
    Read size
    Max xmit
    Log level
    Read raw
    Write raw
    Slow Logins
    Client tuning
    Samba performance problem due changing kernel
    Corrupt tdb Files
    40. DNS and DHCP Configuration Guide
    Note
    41. Further Resources
    Websites
    Related updates from Microsoft
    Books

    Chapter 36. How to compile SAMBA

    Jelmer R. Vernooij

    The Samba Team

    Someone; Jerry perhaps?

    22 May 2001

    18 March 2003

    Table of Contents

    Access Samba source code via CVS
    Introduction
    CVS 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 and nmbd
    Starting from inetd.conf
    Alternative: starting it as a daemon
    Common Errors

    +

    Appendixes

    Table of Contents

    36. How to compile Samba
    Access Samba source code via CVS
    Introduction
    CVS 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 and nmbd
    Starting from inetd.conf
    Alternative: starting it as a daemon
    37. Portability
    HPUX
    SCO UNIX
    DNIX
    RedHat Linux Rembrandt-II
    AIX
    Sequential Read Ahead
    Solaris
    Locking improvements
    Winbind on Solaris 9
    38. Samba and other CIFS clients
    Macintosh clients?
    OS2 Client
    Configuring OS/2 Warp Connect or + OS/2 Warp 4 as a client for Samba
    Configuring OS/2 Warp 3 (not Connect), + OS/2 1.2, 1.3 or 2.x for Samba
    Printer driver download for for OS/2 clients?
    Windows for Workgroups
    Latest TCP/IP stack from Microsoft
    Delete .pwl files after password change
    Configuring WfW password handling
    Case handling of passwords
    Use TCP/IP as default protocol
    Speed improvement
    Windows '95/'98
    Speed improvement
    Windows 2000 Service Pack 2
    Windows NT 3.1
    39. Samba Performance Tuning
    Comparisons
    Socket options
    Read size
    Max xmit
    Log level
    Read raw
    Write raw
    Slow Logins
    Client tuning
    Samba performance problem due changing kernel
    Corrupt tdb Files
    40. DNS and DHCP Configuration Guide
    Note
    41. Further Resources
    Websites
    Related updates from Microsoft

    Chapter 36. How to compile Samba

    Jelmer R. Vernooij

    The Samba Team

    Andrew Tridgell

    Samba Team

    22 May 2001

    18 March 2003

    Table of Contents

    Access Samba source code via CVS
    Introduction
    CVS 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 and nmbd
    Starting from inetd.conf
    Alternative: starting it as a daemon

    You can obtain the samba source from the samba website. To obtain a development version, you can download samba from CVS or using rsync. -

    Access Samba source code via CVS

    Introduction

    +

    Access Samba source code via CVS

    Introduction

    Samba is developed in an open environment. Developers use CVS -(Concurrent Versioning System) to "checkin" (also known as -"commit") new source code. Samba's various CVS branches can +(Concurrent Versioning System) to "checkin" (also known as +"commit") new source code. Samba's various CVS branches can be accessed via anonymous CVS using the instructions detailed in this chapter.

    This chapter is a modified version of the instructions found at http://samba.org/samba/cvs.html -

    CVS Access to samba.org

    +

    CVS Access to samba.org

    The machine samba.org runs a publicly accessible CVS 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 CVS server on this host. -

    Access via CVSweb

    +

    Access via CVSweb

    You can access the source code via your favourite WWW browser. This allows you to access the contents of individual files in the repository and also to look at the revision @@ -15955,7 +15276,7 @@ history and commit logs of individual files. You can also ask for a diff listing between any two versions on the repository.

    Use the URL : http://samba.org/cgi-bin/cvsweb -

    Access via cvs

    +

    Access via cvs

    You can also access the source code via a normal cvs client. This gives you much more control over what you can do with the repository and allows you to checkout whole source trees @@ -15995,7 +15316,7 @@ on this system just substitute the correct package name

    CVS branches other then HEAD can be obtained by using the -r and defining a tag name. A list of branch tag names - can be found on the "Development" page of the samba web site. A common + can be found on the "Development" page of the samba web site. A common request is to obtain the latest 3.0 release code. This could be done by using the following command:

    @@ -16005,7 +15326,7 @@ on this system just substitute the correct package name the following command from within the samba directory:

    cvs update -d -P -

    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 CVS tree at ftp://pserver.samba.org/pub/unpacked and also via anonymous rsync at rsync://pserver.samba.org/ftp/unpacked/. I recommend using rsync rather than ftp. @@ -16014,7 +15335,7 @@ on this system just substitute the correct package name The disadvantage of the unpacked trees is that they do not support automatic merging of local changes like CVS does. rsync access is most convenient for an initial install. -

    Verifying Samba's PGP signature

    +

    Verifying Samba's PGP signature

    In these days of insecurity, it's 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 @@ -16022,39 +15343,43 @@ standard reflex.

    With that said, go ahead and download the following files: 

    -$  wget http://us1.samba.org/samba/ftp/samba-2.2.8a.tar.asc
-$  wget http://us1.samba.org/samba/ftp/samba-pubkey.asc
+$ wget http://us1.samba.org/samba/ftp/samba-2.2.8a.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: 

    -	$ gpg --import samba-pubkey.asc
+$ gpg --import samba-pubkey.asc

    And verify the Samba source code integrity with: 

    -	$ gzip -d samba-2.2.8a.tar.gz
-	$ gpg --verify samba-2.2.8a.tar.asc
+$ gzip -d samba-2.2.8a.tar.gz
+$ gpg --verify samba-2.2.8a.tar.asc

    -If you receive a message like, "Good signature from Samba Distribution -Verification Key..." +If you receive a message like, "Good signature from Samba Distribution +Verification Key..." then all is well. The warnings about trust relationships can be ignored. An example of what you would not want to see would be: -

    - gpg: BAD signature from "Samba Distribution Verification Key" -

    Building the Binaries

    To do this, first run the program ./configure +

    + + gpg: BAD signature from "Samba Distribution Verification Key" + +

    Building the Binaries

    + To do this, first run the program ./configure in the source directory. This should automatically configure Samba for your operating system. If you have unusual - needs then you may wish to run

    root# ./configure --help -

    first to see what special options you can enable. - Then executing

    root# make

    will create the binaries. Once it's successfully - compiled you can use

    root# make install

    to install the binaries and manual pages. You can - separately install the binaries and/or man pages using

    root# make installbin -

    and

    root# make installman -

    Note that if you are upgrading for a previous version + needs then you may wish to run

    root# ./configure --help
+

    first to see what special options you can enable. + Then executing

    root# make

    will create the binaries. Once it's successfully + compiled you can use 

    root# make install

    to install the binaries and manual pages. You can + separately install the binaries and/or man pages using

    root# make installbin
+

    and

    root# make installman
+

    Note that if you are upgrading for a previous version of Samba you might like to know that the old versions of - the binaries will be renamed with a ".old" extension. You - can go back to the previous version with

    root# make revert -

    if you find this version a disaster!

    Compiling samba with Active Directory support

    In order to compile samba with ADS support, you need to have installed + the binaries will be renamed with a ".old" extension. You + can go back to the previous version with

    root# make revert
+

    if you find this version a disaster!

    Compiling samba with Active Directory support

    In order to compile samba with ADS support, you need to have installed on your system:

    • the MIT kerberos development libraries (either install from the sources or use a package). The Heimdal libraries will not work.

    • the OpenLDAP development libraries.

    If your kerberos libraries are in a non-standard location then @@ -16066,16 +15391,17 @@ example of what you would not want to see would be: #define HAVE_LDAP 1

    If it doesn't then 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:

    -

    libkrb5-dev
    krb5-user

    -

    Installing the required packages for RedHat

    On RedHat this means you should have at least:

    -

    krb5-workstation (for kinit)
    krb5-libs (for linking with)
    krb5-devel (because you are compiling from source)

    + out why and fix it.

    Installing the required packages for Debian

    On Debian you need to install the following packages:

    +

    • libkrb5-dev

    • krb5-user

    +

    Installing the required packages for RedHat

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

    Note that these are not standard on a RedHat install, and you may need - to get them off CD2.

    Starting the smbd and nmbd

    You must choose to start smbd and nmbd either + to get them off CD2.

    Starting the smbd and nmbd

    You must choose to start smbd 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 inetd, or you can start them as + by inetd or xinetd, + or you can start them as daemons either from the command line or in /etc/rc.local. See the man pages for details on the command line options. Take particular care to read @@ -16083,7 +15409,7 @@ example of what you would not want to see would be: Samba. In many cases you must be root.

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

    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

    Next edit your /etc/inetd.conf @@ -16092,12 +15418,13 @@ example of what you would not want to see would be: netbios-ns dgram udp wait root /usr/local/samba/bin/nmbd nmbd

    The exact syntax of /etc/inetd.conf varies between unixes. Look at the other entries in inetd.conf - for a guide.

    Note

    Some unixes already have entries like netbios_ns + 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 (note the underscore) in /etc/services. You must either 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 +

    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 ifconfig as root if you don't know what the broadcast is for your @@ -16108,8 +15435,9 @@ example of what you would not want to see would be: This means you shouldn't use spaces between the options and arguments, or you should use a script, and start the script from inetd.

    Restart inetd, perhaps just send - it a HUP. If you have installed an earlier version of nmbd then - you may need to kill nmbd as well.

    Alternative: starting it as a daemon

    To start the server as a daemon you should create + it a HUP. 

    +			root# killall -HUP inetd
+

    Alternative: starting it as a daemon

    To start the server as a daemon you should create a script something like this one, perhaps calling it startsmb.

     		#!/bin/sh
@@ -16121,17 +15449,9 @@ example of what you would not want to see would be:
 		
    To kill it send a kill signal to the processes 
 			nmbd and smbd.
    Note
    If you use the SVR4 style init system then 
 		you may like to look at the examples/svr4-startup
-		script to make Samba fit into that system.

    Common Errors

    “ -I'm using gcc 3 and I've compiled Samba-3 from the CVS and the -binaries are very large files (40 Mb and 20 Mb). I've the same result with ---enable-shared ? -” -

    -The dwarf format used by GCC 3 for storing debugging symbols is very inefficient. -Strip the binaries, don't compile with -g or compile with -gstabs. -

    Chapter 37. Portability

    Jelmer R. Vernooij

    The Samba Team

    Table of Contents

    HPUX
    SCO Unix
    DNIX
    RedHat Linux Rembrandt-II
    AIX
    Sequential Read Ahead
    Solaris
    Locking improvements
    Winbind on Solaris 9

    Samba works on a wide range of platforms but the interface all the + script to make Samba fit into that system.

    Chapter 37. Portability

    Jelmer R. Vernooij

    The Samba Team

    Table of Contents

    HPUX
    SCO UNIX
    DNIX
    RedHat Linux Rembrandt-II
    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

    HP's implementation of supplementary groups is, er, non-standard (for hysterical reasons). There are two group files, /etc/group and /etc/logingroup; the system maps UIDs to numbers using the former, but @@ -16151,15 +15471,15 @@ allowed range. On HPUX 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

    -If you run an old version of SCO Unix then you may need to get important +

    SCO UNIX

    +If you run an old version of SCO UNIX then 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.

    The patch you need is UOD385 Connection Drivers SLS. It is available from SCO (ftp.sco.com, directory SLS, files uod385a.Z and uod385a.ltr.Z). -

    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. @@ -16204,8 +15524,8 @@ _seteuid:

    after creating the above files you then assemble them using 

    -	$ as seteuid.s
-	$ as setegid.s
+$ as seteuid.s
+$ as setegid.s

    that should produce the files seteuid.o and setegid.o @@ -16218,11 +15538,11 @@ LIBSM = setegid.o seteuid.o -ln You should then remove the line: 

     #define NO_EID
-

    from the DNIX section of includes.h

    RedHat Linux Rembrandt-II

    +

    from the DNIX section of includes.h

    RedHat Linux Rembrandt-II

    By default RedHat Rembrandt-II during installation adds an entry to /etc/hosts as follows: 

    -	127.0.0.1 loopback "hostname"."domainname"
+	127.0.0.1 loopback "hostname"."domainname"

    This causes Samba to loop back onto the loopback interface. @@ -16232,10 +15552,10 @@ 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 using vmtune -r 0 improves Samba performance significantly. -

    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, @@ -16256,11 +15576,10 @@ and rebuild samba. Nsswitch on Solaris 9 refuses to use the winbind nss module. This behavior is fixed by Sun in patch 113476-05 which as of March 2003 is not in any roll-up packages. -

    Chapter 38. Samba and other CIFS clients

    Jim McDonough

    IBM

    Jelmer R. Vernooij

    The Samba Team

    5 Mar 2001

    Table of Contents

    Macintosh clients?
    OS2 Client
    How can I configure OS/2 Warp Connect or - OS/2 Warp 4 as a client for Samba?
    How can I configure OS/2 Warp 3 (not Connect), - OS/2 1.2, 1.3 or 2.x for Samba?
    How do I get printer driver download working - for OS/2 clients?
    Windows for Workgroups
    Use latest TCP/IP stack from Microsoft
    Delete .pwl files after password change
    Configure WfW password handling
    Case handling of passwords
    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 now has a CIFS Client / Server called DAVE +

    Chapter 38. Samba and other CIFS clients

    Jelmer R. Vernooij

    The 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 as a client for Samba
    Configuring OS/2 Warp 3 (not Connect), + OS/2 1.2, 1.3 or 2.x for Samba
    Printer driver download for for OS/2 clients?
    Windows for Workgroups
    Latest TCP/IP stack from Microsoft
    Delete .pwl files after password change
    Configuring WfW password handling
    Case handling of passwords
    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 now has a CIFS Client / Server called DAVE

    They test it against Windows 95, Windows NT and samba for compatibility issues. At the time of writing, DAVE was at version @@ -16279,32 +15598,28 @@ 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 -

    OS2 Client

    How can I configure OS/2 Warp Connect or - OS/2 Warp 4 as a client for Samba?

    A more complete answer to this question can be - found on - http://carol.wins.uva.nl/~leeuw/samba/warp.html.

    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 as a client for Samba

    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" - object in the "System Setup" folder.

    Adding the "NetBIOS over TCP/IP" driver is not described + networking support, use the "Selective Install for Networking" + object in the "System Setup" folder.

    Adding the "NetBIOS over TCP/IP" driver is not described in the manual and just barely in the online documentation. Start - MPTS.EXE, click on OK, click on "Configure LAPS" and click - on "IBM OS/2 NETBIOS OVER TCP/IP" in 'Protocols'. This line + MPTS.EXE, click on OK, click on "Configure LAPS" and click + on "IBM OS/2 NETBIOS OVER TCP/IP" in 'Protocols'. This line is then moved to 'Current Configuration'. Select that line, - click on "Change number" and increase it from 0 to 1. Save this + click on "Change number" and increase it from 0 to 1. Save this configuration.

    If the Samba server(s) is not on your local subnet, you can optionally add IP names and addresses of these servers - to the "Names List", or specify a WINS server ('NetBIOS + 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 webpage mentioned above.

    How can I configure OS/2 Warp 3 (not Connect), - OS/2 1.2, 1.3 or 2.x for Samba?

    You can use the free Microsoft LAN Manager 2.2c Client + the same level as Warp 4. See the webpage mentioned above.

    Configuring OS/2 Warp 3 (not Connect), + OS/2 1.2, 1.3 or 2.x for Samba

    You can use the free Microsoft LAN Manager 2.2c Client for OS/2 from ftp://ftp.microsoft.com/BusSys/Clients/LANMAN.OS2/. - See - http://carol.wins.uva.nl/~leeuw/lanman.html for - more information on how to install and use this client. In + In a nutshell, edit the file \OS2VER in the root directory of the OS/2 boot partition and add the lines:

     		20=setup.exe
@@ -16315,14 +15630,12 @@ packages, Samba, and Linux (and other UNIX-based systems) see
 		or NS2000 driver from 
 		
  		ftp://ftp.cdrom.com/pub/os2/network/ndis/ instead.
-

    How do I get printer driver download working - for OS/2 clients?

    First, create a share called [PRINTDRV] that is +

    Printer driver download for for OS/2 clients?

    First, create a share called [PRINTDRV] that is world-readable. Copy your OS/2 driver files there. Note that 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, os2 driver map = - filename. Then, in the file + add to your smb.conf a parameter, os2 driver map = filename. Then, in the file specified by filename, map the name of the NT driver name to the OS/2 driver name as follows:

    nt driver name = os2 driver name.device name, e.g.:

    @@ -16332,7 +15645,7 @@ packages, Samba, and Linux (and other UNIX-based systems) see 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

    Use 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 their TCP/IP 32-Bit @@ -16347,7 +15660,7 @@ fixed. New files include WINSOCK.DLL, TRACERT.EXE, NETSTAT.EXE, and NBTSTAT.EXE. -

    Delete .pwl files after password change

    +

    Delete .pwl files after password change

    WfWg does a lousy job with passwords. I find that if I change my password on either the unix box or the PC the safest thing to do is to delete the .pwl files in the windows directory. The PC will complain about not finding the files, but will soon get over it, allowing you to enter the new password. @@ -16356,20 +15669,20 @@ If you don't do this you may find that WfWg remembers and uses the old password, even if you told it a new one.

    Often WfWg will totally ignore a password you give it in a dialog box. -

    Configure WfW password handling

    +

    Configuring WfW 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. ie disable Password Caching etc -for use with security = user -

    Case handling of passwords

    Windows for Workgroups uppercases the password before sending it to the server. Unix passwords can be case-sensitive though. Check the smb.conf(5) 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 +for use with security = user +

    Case handling of passwords

    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 that you have to use TCP/IP as the default protocol under WfWg. For some reason if you leave NetBEUI as the default it may break the print queue reporting on some systems. -It is presumably a WfWg bug.

    Speed improvement

    -Note that some people have found that setting DefaultRcvWindow in +It is presumably a WfWg bug.

    Speed improvement

    + Note that some people have found that setting DefaultRcvWindow in the [MSTCP] section of the SYSTEM.INI file under WfWg to 3072 gives a big improvement. I don't know why. @@ -16379,7 +15692,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. I don't know why. -

    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 above change will affect you once these updates have been installed. @@ -16393,11 +15706,11 @@ install the OLEUPD.EXE fix. This fix may stop your machine from hanging for an extended period when exiting Outlook and you may also notice a significant speedup when accessing network neighborhood services. -

    Speed improvement

    +

    Speed improvement

    Configure the win95 TCPIP registry settings to give better performance. I use a program called MTUSPEED.exe which I got off the net. 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 @@ -16406,26 +15719,19 @@ likely occur if it is not.

    In order to serve profiles successfully to Windows 2000 SP2 clients (when not operating as a PDC), Samba must have -nt acl support = no +nt acl support = no added to the file share which houses the roaming profiles. If this is not done, then the Windows 2000 SP2 client will complain about not being able to access the profile (Access Denied) and create multiple copies of it on disk (DOMAIN.user.001, DOMAIN.user.002, etc...). See the -smb.conf(5) man page +smb.conf man page for more details on this option. Also note that the -nt acl support parameter was formally a global parameter in +nt acl support parameter was formally a global parameter in releases prior to Samba 2.2.2.

    The following is a minimal profile share: -

    -	[profile]
-		path = /export/profile
-		create mask = 0600
-		directory mask = 0700
-		nt acl support = no
-		read only = no
-

    +

    Example 38.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 Win2k SP2 client copies the security descriptor for the profile which contains the Samba server's SID, and not the domain SID. The client @@ -16433,15 +15739,15 @@ compares the SID for SAMBA\user and realizes it is different that the one assigned to DOMAIN\user. Hence the reason for the access denied message.

    -By disabling the nt acl support parameter, Samba will send +By disabling the nt acl support parameter, Samba will send the Win2k 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 -NT 3.1 workstations, read this Microsoft Knowledge Base article. +

    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 +NT 3.1 workstations, read this Microsoft Knowledge Base article. -

    Chapter 39. 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 changing kernel
    Corrupt tdb Files

    Comparisons

    +

    Chapter 39. 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 changing kernel
    Corrupt tdb Files

    Comparisons

    The Samba server uses TCP to talk to the client. Thus 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 @@ -16463,14 +15769,14 @@ suspect the biggest factor is not Samba vs 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.

    The socket options that Samba uses are settable both on the command line with the -O option, or in the smb.conf file.

    -The socket options section of the smb.conf manual page describes how +The socket options section of the smb.conf manual page describes how to set these and gives recommendations.

    Getting the socket options right can make a big difference to your @@ -16479,11 +15785,11 @@ much. The correct settings are very dependent on your local network.

    The socket option TCP_NODELAY is the one that seems to make the biggest single difference for most networks. Many people report that -adding socket options = TCP_NODELAY doubles the read +adding socket options = TCP_NODELAY doubles the read performance of a Samba drive. The best explanation I have seen for this is that the Microsoft TCP/IP stack is slow in sending tcp ACKs. -

    Read size

    -The option read size affects the overlap of disk +

    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 SMBreadbraw) is larger than this value then the server begins writing @@ -16499,10 +15805,10 @@ The default value is 16384, but very little experimentation has been done 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

    -At startup the client and server negotiate a maximum transmit size, +

    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 +maximum size that Samba will negotiate using the max xmit option in smb.conf. Note that this is the maximum size of SMB requests that Samba will accept, but not the maximum size that the *client* will accept. The client maximum receive size is sent to Samba by the client and Samba @@ -16513,41 +15819,41 @@ 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

    -If you set the log level (also known as debug level) higher than 2 +

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

    Read raw

    -The read raw operation is designed to be an optimised, low-latency +

    Read raw

    +The read raw operation is designed to be an optimised, low-latency file read operation. A server may choose to not support it, -however. and Samba makes support for read raw optional, with it +however. and Samba makes support for read raw optional, with it being enabled by default.

    -In some cases clients don't handle read raw very well and actually +In some cases clients don't handle read raw very well and actually 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 +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

    -The write raw operation is designed to be an optimised, low-latency +

    Write raw

    +The write raw operation is designed to be an optimised, low-latency file write operation. A server may choose to not support it, -however. and Samba makes support for write raw optional, with 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 +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

    +the lowest practical password level will improve things. +

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

    Samba performance problem due changing kernel

    +

    Samba performance problem due changing kernel

    Hi everyone. I am running Gentoo on my server and samba 2.2.8a. Recently I changed kernel version from linux-2.4.19-gentoo-r10 to linux-2.4.20-wolk4.0s. And now I have performance issue with samba. Ok @@ -16562,7 +15868,7 @@ Grab 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, etc... look normal for ethernet. -

    Corrupt tdb Files

    +

    Corrupt tdb Files

    Well today it happened, Our first major problem using samba. Our samba PDC server has been hosting 3 TB of data to our 500+ users [Windows NT/XP] for the last 3 years using samba, no problem. @@ -16580,12 +15886,12 @@ Q2) What I also would like to mention is that the service latency seems a lot lower then before the locks cleanup, any ideas on keeping it top notch?

    A2) Yes! Same answer as for Q1! -

    Chapter 40. DNS and DHCP Configuration Guide

    John H. Terpstra

    Samba Team

    Table of Contents

    Note

    Note

    +

    Chapter 40. DNS and DHCP Configuration Guide

    John H. Terpstra

    Samba Team

    Table of Contents

    Note

    Note

    This chapter did not make it into this release. It is planned for the published release of this document. -

    Chapter 41. Further Resources

    Jelmer R. Vernooij

    The Samba Team

    David Lechnyr

    Unofficial HOWTO

    May 1, 2003

    Table of Contents

    Websites
    Related updates from Microsoft
    Books

    Websites

    • +

    Chapter 41. Further Resources

    Jelmer R. Vernooij

    The Samba Team

    May 1, 2003

    Table of Contents

    Websites
    Related updates from Microsoft

    Websites

    Related updates from Microsoft

    Related updates from Microsoft

    Books

    Index

    +

    Index

    Symbols

    "Domain Admins" group, Discussion
    "Domain Users" group, Adding Domain Users to the Power Users group
    "Printers" folder, Caveats to be considered, Installing the PostScript Driver on a Client, Manual Driver Installation in 15 Steps
    "raw" printing, CUPS/Samba as a "spooling-only" Print Server; "raw" printing +with Vendor Drivers on Windows Clients
    /etc/host.conf, /etc/host.conf
    /etc/hosts, /etc/hosts
    /etc/nsswitch.conf, /etc/nsswitch.conf
    8.3
    file names, MS Windows NTFS Comparison with UNIX File Systems

    A

    ACLs, File, Directory and Share Access Controls
    Active Directory, Samba ADS Domain Membership
    add group script, Adding Groups Fails
    add machine script, The machine trust account not accessible, Adding Machine to Domain Fails
    add printer command, Adding new Printers with the Windows NT APW
    add printer wizard, Three familiar Methods for driver upload plus a new one
    add user script, Mapping User Identifiers between MS Windows and UNIX
    addprinter command, Parameters Recommended for Use
    admin users, User and Group Based Controls, I have set force user but Samba still makes root the owner of all the files I touch!
    Administrator, Discussion
    ADS (see Active Directory)
    ads server, Setup your smb.conf
    application/cups.vnd-postscript, Benefits of using "CUPS PostScript Driver for +Windows NT/2k/XP" instead of 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
    application/postscript, Benefits of using "CUPS PostScript Driver for +Windows NT/2k/XP" instead of Adobe Driver
    application/vnd.cups-raster, PostScript Printer Descriptions (PPDs) for non-PS Printers
    application/vnd.cups-raw, Explicitly enable "raw" printing for +application/octet-stream!
    auth methods, auth methods does not work, Passdb Backends and Authentication

    B

    bind interfaces only, The tests
    brlock.tdb, The printing *.tdb Files
    (see also TDB)
    browse list, What is Browsing?, Technical Overview of browsing
    browseable, The [printers] Section, Any [my_printer_name] Section, Parameters in the [print$] Section

    C

    case sensitive, Miscellaneous Controls, Windows 9x / Me Profile Setup
    chpass, Manual Creation of Machine Trust Accounts
    comment, The [printers] Section, Any [my_printer_name] Section, Parameters in the [print$] Section
    configure, Building the Binaries
    connections.tdb, The printing *.tdb Files
    (see also TDB)
    core files, Internal errors
    create mask, File and Directory Permissions Based Controls, Interaction with the standard Samba create mask + parameters
    csc policy, Miscellaneous Controls
    CUPS
    Page Accounting, Page Accounting with CUPS
    quotas, Setting up Quotas
    CUPS-PPD, cupsomatic, pdqomatic, lpdomatic, directomatic
    cupsaddsmb, Three familiar Methods for driver upload plus a new one, 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
    cupsomatic, CUPS can use all Windows-formatted Vendor PPDs, The CUPS Filtering Architecture, cupsomatic/Foomatic -- how do they fit into the Picture?, Difference between cupsomatic/foomatic-rip and +native CUPS printing, cupsomatic, pdqomatic, lpdomatic, directomatic
    CVS, Access Samba source code via CVS
    web, Access via CVSweb

    D

    daemon, Alternative: starting it as a daemon
    DDK, PostScript Drivers with no major problems -- even in Kernel +Mode, CUPS Package of "PostScript Driver for WinNT/2k/XP"
    debug, Internal errors
    debug level, Debugging with Samba itself, Log level
    debuglevel, Debug levels
    default case, Miscellaneous Controls
    delete printer command, Adding new Printers with the Windows NT APW
    deleteprinter command, Parameters Recommended for Use
    DHCP, Background Information
    diff, Patches
    directory mask, File and Directory Permissions Based Controls
    directory security mask, Interaction with the standard Samba create mask + parameters
    disable spoolss, Parameters Recommended for Use
    display charset, Samba and charsets
    DNS, TCP/IP - without NetBIOS, DNS Lookup
    Active Directory, DNS and Active Directory
    Dynamic, Background Information
    dns proxy, What is Browsing?
    domain admin group, Mapping MS Windows and UNIX Groups
    domain logons, Preparing for Domain Control
    domain master, Domain Network Logon Service, Example Configuration, What is Browsing?, Making Samba the domain master
    dont descend, Miscellaneous Controls
    dos charset, Samba and charsets, Japanese charsets, CP850.so can't be found
    dos filemode, File and Directory Permissions Based Controls
    dos filetime resolution, Miscellaneous Controls
    dos filetimes, Miscellaneous Controls

    E

    EMF, Windows Drivers, GDI and EMF, From Windows Clients to an NT Print Server, Driver Execution on the Server
    encrypt passwords, Joining an NT4 type Domain with Samba-3, smbpasswd - Encrypted Password Database, smb.conf PAM Configuration, The tests
    enhanced browsing, What is Browsing?
    enumports command, Parameters Recommended for Use, Samba and Printer Ports
    EPM (see ESP meta packager)
    ESC/P, Driver Execution on the Server
    ESP
    Ghostscript, The CUPS Filtering Architecture, Difference between cupsomatic/foomatic-rip and +native CUPS printing
    meta packager, CUPS Package of "PostScript Driver for WinNT/2k/XP"
    Print Pro, Sources of CUPS drivers / PPDs, ESP Print Pro Package of "PostScript Driver for +WinNT/2k/XP"
    Extended Attributes, File, Directory and Share Access Controls

    F

    fake oplocks, Miscellaneous Controls
    File System, File System Access Controls
    foomatic, CUPS can use all Windows-formatted Vendor PPDs, The CUPS Filtering Architecture, cupsomatic/Foomatic -- how do they fit into the Picture?, Difference between cupsomatic/foomatic-rip and +native CUPS printing, foomatic-rip and Foomatic explained, Foomatic's strange Name
    foomatic-rip, Difference between cupsomatic/foomatic-rip and +native CUPS printing, CUPS Print Drivers from Linuxprinting.org, foomatic-rip and Foomatic explained, The Grand Unification +achieved...
    force create mode, File and Directory Permissions Based Controls, Interaction with the standard Samba create mask + parameters
    force directory mode, File and Directory Permissions Based Controls, Interaction with the standard Samba create mask + parameters
    force directory security mode, File and Directory Permissions Based Controls, Interaction with the standard Samba create mask + parameters
    force group, User and Group Based Controls
    force security mode, File and Directory Permissions Based Controls, Interaction with the standard Samba create mask + parameters
    force user, User and Group Based Controls, I have set force user but Samba still makes root the owner of all the files I touch!, Beware of Force User
    ftp, Accessing the samba sources via rsync and ftp

    G

    gdb, Internal errors
    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
    GhostScript, PostScript and Ghostscript, Ghostscript -- the Software RIP for non-PostScript Printers
    (see also PostScript)
    Ghostscript
    ESP (see ESP GhostScript)
    GID, Features and Benefits
    GPG, Verifying Samba's PGP signature
    groupadd, Features and Benefits
    groupdel, Features and Benefits
    groups
    domain, Discussion
    mapping, Mapping MS Windows and UNIX Groups
    nested, Adding MS Windows Groups to MS Windows Groups Fails
    guest account, Problem resolution, My client reports "This server is not configured to list shared resources", The [printers] Section
    guest ok, User and Group Based Controls, The [printers] Section, Any [my_printer_name] Section, Parameters in the [print$] Section

    H

    hide dot files, Miscellaneous Controls
    hide files, Miscellaneous Controls
    hide unreadable, File and Directory Permissions Based Controls
    hide unwriteable files, File and Directory Permissions Based Controls
    host msdfs, Features and Benefits
    hosts allow, Using host based protection, Parameters Recommended for Use, Any [my_printer_name] Section
    hosts deny, Using host based protection, Parameters Recommended for Use, Any [my_printer_name] Section

    I

    idmap gid, Features and Benefits, Winbind is not resolving users and groups
    idmap uid, Features and Benefits, Winbind is not resolving users and groups
    ifconfig, Starting from inetd.conf
    imprints, Three familiar Methods for driver upload plus a new one
    inetd, The tests, Starting the smbd and nmbd, Starting from inetd.conf
    Interdomain Trusts, Interdomain Trust Relationships
    completing, Completing an NT4 Domain Trust
    creating, Native MS Windows NT4 Trusts Configuration
    Facilities, Inter-Domain Trust Facilities
    interfaces, Multiple interfaces, The tests, Starting from inetd.conf
    invalid users, User and Group Based Controls
    IPP, Understanding cupsaddsmb

    K

    KDC, Samba ADS Domain Membership
    Kerberos, Samba ADS Domain Membership
    kinit, Setup your /etc/krb5.conf

    L

    ldap admin dn, Configuring Samba
    ldap delete dn, Configuring Samba
    ldap filter, Configuring Samba
    ldap machine suffix, Configuring Samba
    ldap passwd sync, Configuring Samba, Password synchronisation
    ldap ssl, Configuring Samba, Security and sambaSamAccount
    ldap suffix, Configuring Samba
    ldap trust ids, Configuring Samba
    ldap user suffix, Configuring Samba
    libnss_wins.so, /etc/nsswitch.conf
    Links
    hard, MS Windows NTFS Comparison with UNIX File Systems
    soft, MS Windows NTFS Comparison with UNIX File Systems
    Linuxprinting.org, CUPS Print Drivers from Linuxprinting.org
    lm announce, What is Browsing?
    lm interval, What is Browsing?
    LMB (see Local Master Browser)
    LMHOSTS, The LMHOSTS file
    load printers, Parameters Recommended for Use, A little Experiment to warn you, The [global] Section
    local master, What is Browsing?, Setting up WORKGROUP Browsing
    Local Master Browser, Use of the Remote Announce parameter
    locking, Discussion
    locking.tdb, The printing *.tdb Files
    (see also TDB)
    log files
    monitoring, Assumptions
    log level, Adding Machine to Domain Fails, extd_audit, Debug levels
    logon drive, Windows NT4 Workstation
    logon home, LDAP special attributes for sambaSamAccounts, Windows 9x / Me User Profiles, Mixed Windows 9x / Me and Windows NT4/200x User Profiles, Windows NT4 Workstation, Sharing Profiles between W9x/Me and NT4/200x/XP workstations
    logon path, LDAP special attributes for sambaSamAccounts, Mixed Windows 9x / Me and Windows NT4/200x User Profiles, Windows 9x / Me Profile Setup, Windows NT4 Workstation, Sharing Profiles between W9x/Me and NT4/200x/XP workstations
    logon script, LDAP special attributes for sambaSamAccounts
    lpadmin, CUPS Print Drivers from Linuxprinting.org, Setting up Quotas
    lppause command, Parameters Recommended for Use, Linking of smbd with libcups.so, From Windows Clients to a CUPS/Samba Print Server, Pre-conditions
    lpq cache time, Parameters Recommended for Use, The [global] Section
    lpq command, Parameters Recommended for Use, Linking of smbd with libcups.so, Pre-conditions
    lpresume command, Parameters Recommended for Use, Linking of smbd with libcups.so, Pre-conditions
    lprm command, Parameters Recommended for Use, Linking of smbd with libcups.so, Pre-conditions
    lpstat, Troubleshooting revisited

    M

    MAC Addresses, /etc/hosts
    machine trust accounts, MS Windows Workstation/Server Machine Trust Accounts
    creating, MS Windows Workstation/Server Machine Trust Accounts
    make, Building the Binaries
    mangling method, Japanese charsets
    map to guest, Parameters in the [print$] Section, Adding new Printers with the Windows NT APW, Can't reconnect to Samba under new account + from Win2K/XP, Avoid being connected to the Samba server as the + "wrong" user
    max print jobs, Parameters Recommended for Use
    max xmit, Max xmit
    messages.tdb, The printing *.tdb Files
    (see also TDB)
    MIME, MIME types and CUPS Filters, MIME type Conversion Rules, Filter Requirements, "application/octet-stream" printing
    min print space, Parameters Recommended for Use
    msdfs root, Features and Benefits

    N

    name resolve order, What is Browsing?
    nbtstat, The NetBIOS Name Cache
    NetBIOS, Features and Benefits, TCP/IP - without NetBIOS, Integrating MS Windows networks with Samba, Name resolution as used within MS Windows networking
    NetBIOS-less, TCP/IP - without NetBIOS
    nmblookup, The NetBIOS Name Cache
    nt acl support, File and Directory Permissions Based Controls, Viewing file ownership, Viewing File or Directory Permissions, Modifying file or directory permissions, Windows 2000 Service Pack 2
    ntdrivers.tdb, The printing *.tdb Files
    (see also TDB)
    ntforms.tdb, The printing *.tdb Files
    (see also TDB)
    NTFS, File System Access Controls
    ntprinters.tdb, The printing *.tdb Files
    (see also TDB)

    O

    obey pam restrictions, smb.conf PAM Configuration
    only user, User and Group Based Controls, Why can users access home directories of other users?
    oplock break wait time, Advanced Samba Opportunistic Locking Parameters, Disabling Kernel OpLocks
    oplock contention limit, Advanced Samba Opportunistic Locking Parameters
    os level, What is Browsing?, Setting up WORKGROUP Browsing, Setting up DOMAIN Browsing, Forcing Samba to be the master, Making Samba the domain master
    os2 driver map, Parameters Recommended for Use, Printer driver download for for OS/2 clients?

    P

    page_log, The page_log File Syntax
    passdb backend, MS Windows Workstation/Server Machine Trust Accounts, Account Information Databases, Technical Information, The pdbedit Command, Configuring Samba, Configuring, Users can not logon, auth methods does not work, Passdb Backends and Authentication
    password level, Password checking, The tests, Case handling of passwords, Slow Logins
    password server, Server Security (User Level Security), Security Mode and Master Browsers, Joining an NT4 type Domain with Samba-3, The tests
    patch, Patches
    path, "The network name cannot be found", The [printers] Section, Any [my_printer_name] Section, Print Commands, Creating the [print$] Share, Parameters in the [print$] Section, Subdirectory Structure in [print$], Samba receiving Jobfiles and passing them to CUPS, Auto-Deletion or Preservation of CUPS Spool Files, Permissions on +/var/spool/samba/ get reset after each +reboot, The tests
    PCL, GDI on Windows -- PostScript on UNIX, UNIX Printfile Conversion and GUI Basics, Driver Execution on the Server, Network PostScript RIP: CUPS Filters on Server -- clients use +PostScript Driver with CUPS-PPDs
    PDF, Windows Drivers, GDI and EMF, PostScript Printer Description (PPD) Specification
    pdf, MIME type Conversion Rules
    PDL, GDI on Windows -- PostScript on UNIX, PostScript and Ghostscript
    PJL, Network PostScript RIP: CUPS Filters on Server -- clients use +PostScript Driver with CUPS-PPDs, Benefits of using "CUPS PostScript Driver for +Windows NT/2k/XP" instead of Adobe Driver, Adobe and CUPS PostScript Drivers for Windows Clients
    point and print, Driver Installation Methods on Windows Clients, Three familiar Methods for driver upload plus a new one, cupsomatic/Foomatic -- how do they fit into the Picture?, Run "cupsaddsmb" (quiet Mode), Installing the PostScript Driver on a Client, Manual Driver Installation in 15 Steps
    PostScript, Using CUPS/Samba in an advanced Way -- intelligent printing +with PostScript Driver Download, GDI on Windows -- PostScript on UNIX, UNIX Printfile Conversion and GUI Basics, PostScript and Ghostscript, Prefilters, Driver Execution on the Server, Network PostScript RIP: CUPS Filters on Server -- clients use +PostScript Driver with CUPS-PPDs, CUPS: a "Magical Stone"?, CUPS Package of "PostScript Driver for WinNT/2k/XP"
    (see also Ghostscript)
    RIP, PostScript and Ghostscript
    PPD, PostScript and Ghostscript, PostScript Printer Description (PPD) Specification, PostScript Printer Descriptions (PPDs) for non-PS 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
    CUPS (see CUPS-PPD)
    preferred master, What is Browsing?, Setting up WORKGROUP Browsing, Forcing Samba to be the master, Making Samba the domain master, The tests
    preserve case, Windows 9x / Me Profile Setup
    print command, Parameters Recommended for Use, The [global] Section, Default Print Commands for various UNIX Print Subsystems, Setting up your own Print Commands, Linking of smbd with libcups.so, From Windows Clients to a CUPS/Samba Print Server, Pre-conditions, Manual Configuration
    print ok , Parameters Recommended for Use
    printable, Parameters Recommended for Use, The [printers] Section, Any [my_printer_name] Section
    printcap, Parameters Recommended for Use, Default Print Commands for various UNIX Print Subsystems, Basic Configuration of CUPS support, Linking of smbd with libcups.so, More complex smb.conf Settings for +CUPS, From Windows Clients to a CUPS/Samba Print Server, Pre-conditions
    printcap name, Parameters Recommended for Use, The [global] Section
    printer, Parameters Recommended for Use
    printer admin, Parameters Recommended for Use, The [global] Section, Any [my_printer_name] Section, Parameters in the [print$] Section, Setting Drivers for existing Printers with a Client GUI, IMPORTANT! Setting Device Modes on new Printers, Always make first Client Connection as root or "printer admin", Setting Default Print Options for the Client Drivers, Adding new Printers with the Windows NT APW, More complex smb.conf Settings for +CUPS, What is required for adddriver and setdriver to succeed, Print options for all users can't be set on Win2K/XP
    printer name, Parameters Recommended for Use
    printing, Parameters Recommended for Use, The [global] Section, Default Print Commands for various UNIX Print Subsystems, Setting up your own Print Commands, Basic Configuration of CUPS support, Linking of smbd with libcups.so, More complex smb.conf Settings for +CUPS, From Windows Clients to a CUPS/Samba Print Server, Pre-conditions, Manual Configuration
    printing.tdb, The printing *.tdb Files
    (see also TDB)
    PrintPro (see ESP Print Pro)
    public, The [printers] Section

    Q

    queue resume command, Linking of smbd with libcups.so
    queuepause command, Parameters Recommended for Use, Linking of smbd with libcups.so
    queueresume command, Parameters Recommended for Use

    R

    read list, User and Group Based Controls
    read only, Miscellaneous Controls, The [printers] Section, Parameters in the [print$] Section
    read raw, Read raw
    read size, Read size
    remote announce, NetBIOS over TCP/IP, How Browsing Functions, Use of the Remote Announce parameter, Browsing support in Samba
    remote browse sync, NetBIOS over TCP/IP, How Browsing Functions, Use of the Remote Browse Sync parameter
    root preexec, Logon Scripts
    rpcclient
    adddriver, Run "cupsaddsmb" with verbose Output, Understanding cupsaddsmb, Installing PostScript Driver Files manually (using +rpcclient), Understanding the rpcclient man page, What is required 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), What is required 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), What is required for adddriver and setdriver to succeed, Manual Driver Installation in 15 Steps
    rsync, Accessing the samba sources via rsync and ftp

    S

    secrets.tdb, The printing *.tdb Files
    (see also TDB)
    security, Samba Security Modes, Domain Security Mode (User Level Security), Server Security (User Level Security), What makes Samba a SERVER?, What makes Samba a Domain Controller?, What makes Samba a Domain Member?, Constantly Losing Connections to Password Server, Preparing for Domain Control, Security Mode and Master Browsers, Joining an NT4 type Domain with Samba-3, Why is this better than security = server?, Setup your smb.conf, Run "cupsaddsmb" (quiet Mode), "cupsaddsmb" keeps asking for root password in + neverending loop, Passdb Backends and Authentication, The tests, Configuring WfW password handling
    security mask, File and Directory Permissions Based Controls, Interaction with the standard Samba create mask + parameters
    Server Manager, MS Windows Workstation/Server Machine Trust Accounts, Manual Creation of Machine Trust Accounts
    sessionid.tdb, The printing *.tdb Files
    (see also TDB)
    share_info.tdb, The printing *.tdb Files
    (see also TDB)
    short preserve case, Miscellaneous Controls, Windows 9x / Me Profile Setup
    Short-Cuts, MS Windows NTFS Comparison with UNIX File Systems
    show add printer wizard, Parameters Recommended for Use, The [global] Section, Adding new Printers with the Windows NT APW
    SID, Features and Benefits
    Single Sign On, Caveats to be considered
    smbclient, Testing with smbclient, The tests
    socket options, Socket options
    spooling
    central, Central spooling vs. "Peer-to-Peer" printing
    peer-to-peer, Central spooling vs. "Peer-to-Peer" printing
    spooling-only, CUPS/Samba as a "spooling-only" Print Server; "raw" printing +with Vendor Drivers on Windows Clients
    strict locking, Discussion

    T

    TDB, The printing *.tdb Files, Trivial DataBase Files
    backing up (see tdbbackup)
    tdbbackup, Using tdbbackup
    template homedir, Linux/FreeBSD-specific PAM configuration
    testparm, The tests
    text/plain, MIME type Conversion Rules
    total print jobs, Parameters Recommended for Use, The [global] Section

    U

    UDP, NetBIOS over TCP/IP
    UID, Features and Benefits
    unexpected.tdb, The printing *.tdb Files
    (see also TDB)
    unix charset, Samba and charsets, Japanese charsets
    use client driver, Parameters Recommended for Use, The [global] Section
    user, Share Level Security, The tests
    User Manager, Samba as the Trusted Domain, Samba as the Trusting Domain
    useradd, Manual Creation of Machine Trust Accounts
    username, User and Group Based Controls
    username level, Password checking
    username map, Windows 200x XP Professional

    V

    valid users, User and Group Based Controls, The tests
    veto files, Miscellaneous Controls
    vfs objects, Discussion
    vipw, Manual Creation of Machine Trust Accounts

    W

    winbind separator, Start up the winbindd daemon and test it!
    WINS, What is Browsing?, NetBIOS over TCP/IP, WINS Lookup
    wins hook, What is Browsing?
    wins proxy, What is Browsing?
    wins server, What is Browsing?, WINS - The Windows Internetworking Name Server, Setting up a WINS server
    wins support, What is Browsing?, WINS - The Windows Internetworking Name Server, Setting up a WINS server
    workgroup, Security Mode and Master Browsers, Joining an NT4 type Domain with Samba-3, Browsing support in Samba
    write list, User and Group Based Controls, Parameters in the [print$] Section
    write raw, Write raw
    writeable, The [printers] Section, Any [my_printer_name] Section
    WYSIWYG, Windows Drivers, GDI and EMF

    X

    X Window System, UNIX Printfile Conversion and GUI Basics
    xinetd, Starting from inetd.conf (see inetd)
    Xprint, UNIX Printfile Conversion and GUI Basics
    diff --git a/docs/htmldocs/SambaHA.html b/docs/htmldocs/SambaHA.html index ba82f6ad0f..39ab6b91d8 100644 --- a/docs/htmldocs/SambaHA.html +++ b/docs/htmldocs/SambaHA.html @@ -1,4 +1,4 @@ -Chapter 29. High Availability Options
    Chapter 29. High Availability Options
    Prev Part III. Advanced Configuration Next

    Chapter 29. High Availability Options

    John H. Terpstra

    Samba Team

    Table of Contents

    Note

    Note

    +Chapter 29. High Availability Options

    Chapter 29. High Availability Options
    Prev Part III. Advanced Configuration Next

    Chapter 29. High Availability Options

    John H. Terpstra

    Samba Team

    Table of Contents

    Note

    Note

    This chapter did not make it into this release. It is planned for the published release of this document. -

    Prev Up Next
    Chapter 28. Samba Backup Techniques Home Part IV. Migration and Updating
    +

    Prev Up Next
    Chapter 28. Samba Backup Techniques Home Part IV. Migration and Updating
    diff --git a/docs/htmldocs/ServerType.html b/docs/htmldocs/ServerType.html index 01f03662ae..7b5b7117a6 100644 --- a/docs/htmldocs/ServerType.html +++ b/docs/htmldocs/ServerType.html @@ -1,4 +1,4 @@ -Chapter 4. Server Types and Security Modes
    Chapter 4. Server Types and Security Modes
    Prev Part II. Server Configuration Basics Next

    Chapter 4. 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)
    Seamless Windows Network Integration
    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

    +Chapter 4. Server Types and Security Modes

    Chapter 4. Server Types and Security Modes
    Prev Part II. Server Configuration Basics Next

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

    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 to use Samba will want to know what, within a Samba context, terms familiar to MS Windows @@ -8,10 +8,11 @@ modes function BEFORE we get into the details of how to configure the server its The chapter provides an overview of the security modes of which Samba is capable and how these relate to MS Windows servers and clients.

    -Firstly we should recognise the question so often asked, "Why would I want to use Samba?" -So, in those chapters where the answer may be important you will see a section that highlights -features and benefits. These may be for or against Samba. -

    Features and Benefits

    +A question often asked is, "Why would I want to use Samba?" Most chapters contain a section +that 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 towards Samba so the benefit may be on the side of our competition. +

    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 fitting his anguish. The other looked at the stone and said, that is a garnet - I @@ -23,7 +24,7 @@ pleasure, but if you are forced upon it and have no time for its secrets then it 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 +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 like this one we will tell of both.

    @@ -47,14 +48,14 @@ So now, what are the benefits of features mentioned in this chapter? greater flexibility than MS Windows NT4 and in many cases a significantly higher utility than Active Directory domains with MS Windows 200x. -

    Server Types

    Administrators of Microsoft networks often refer to three -different type of servers:

    • Domain Controller

      Primary Domain Controller
      Backup Domain Controller
      ADS Domain Controller

    • Domain Member Server

      Active Directory Member Server
      NT4 Style Domain Member Server

    • Stand Alone Server

    +

    Server Types

    Administrators of Microsoft networks often refer to three +different type of servers:

    • Domain Controller

      • Primary Domain Controller

      • Backup Domain Controller

      • ADS Domain Controller

    • Domain Member Server

      • Active Directory Domain Server

      • NT4 Style Domain Domain Server

    • Stand Alone Server

    The chapters covering Domain Control, Backup Domain Control and Domain Membership provide -pertinent information regarding Samba-3 configuration for each of these server roles. +pertinent information regarding Samba configuration for each of these server roles. The reader is strongly encouraged to become intimately familiar with the information presented. -

    Samba Security Modes

    -In this section the function and purpose of Samba's security +

    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. @@ -69,7 +70,7 @@ ways that allow the security levels to be implemented. In actual fact, Samba imp ADS, and SERVER modes. They are documented in this chapter.

    -A SMB server tells the client at startup what security level + A SMB server tells the client at startup what security level it is running. There are two options: share level and user level. Which of these two the client receives affects the way the client then tries to authenticate itself. It does not directly affect @@ -77,8 +78,8 @@ the way the client then tries to authenticate itself. It does not directly affec but it fits in with the client/server approach of SMB. In SMB everything is initiated and controlled by the client, and the server can only tell the client what is available and whether an action is allowed. -

    User Level Security

    -We will describe user level security first, as it's simpler. +

    User Level Security

    +We will describe user level security first, as it's simpler. In user level security, the client will send a session setup command directly after the protocol negotiation. This contains a username and password. The server can either accept or reject that @@ -95,13 +96,11 @@ It is also possible for a client to send multiple ses 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). -

    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

    Ok, now for share level security. In share level security, the client authenticates itself separately for each share. It will send a password along with each tree connection (share mount). It does not explicitly send a @@ -121,104 +120,92 @@ level security. They normally send a valid username but no password. Samba recor this username in a list of possible usernames. When the client then does a tree connection it also adds to this list the name of the share they try to connect to (useful for home directories) and any users -listed in the user = smb.conf line. The password is then checked +listed in the user smb.conf line. The password is then checked in turn against these possible usernames. If a match is found then the client is authenticated as that user. -

    Example Configuration

    +

    Example Configuration

    The smb.conf parameter that sets Share Level Security is: -

    -	security = share
-

    +

    security = share

    Please note that there are reports that recent MS Windows clients do not like to work with share mode security servers. You are strongly discouraged from using share level security. -

    Domain Security Mode (User Level Security)

    -When Samba is operating in security = domain mode, +

    Domain Security Mode (User Level Security)

    +When Samba is operating in security = domain mode, the Samba server has a domain security trust account (a machine account) and will cause all authentication requests to be passed through to the domain controllers. -

    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 = "name_of_NT_domain"
-

    +

    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. Next, on the Unix/Linux system execute:

      root# smbpasswd -j DOMAIN_NAME -r PDC_NAME (samba-2.x)

      root# net join -U administrator%password (samba-3)

    Note

    -As of Samba-2.2.4 the Samba 2.2.x series can auto-join a Windows NT4 style Domain just -by executing: +

  • Next, on the UNIX/Linux system execute:

    root# net rpc join -U administrator%password

    • Note

    +Samba-2.2.4 and later can auto-join a Windows NT4 style Domain just by executing: 

    -root# smbpasswd -j DOMAIN_NAME -r PDC_NAME -U Administrator%password
+root# smbpasswd -j DOMAIN_NAME -r PDC_NAME \
+	 -U Administrator%password

    -As of Samba-3 the same can be done by executing: +Samba-3 can do the same by executing: 

    -root# net join -U Administrator%password
+root# net rpc join -U Administrator%password

    -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. +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 does require there to be a standard Unix account -for each user in order to assign a uid once the account has been authenticated by +Use of this mode of authentication does require there to be a standard UNIX account +for each user in order to assign a UID once the account has been authenticated by the remote Windows DC. This account can be blocked to prevent logons by clients other than -MS Windows through things such as setting an invalid shell in the +MS Windows through means such as setting an invalid shell in the /etc/passwd entry.

    An alternative to assigning UIDs to Windows users on a Samba member server is -presented in the Winbind Overview chapter -in this HOWTO collection. +presented in the chapter about winbind.

    -For more information of being a domain member, see the Domain -Member section of this Howto. -

    ADS Security Mode (User Level Security)

    + For more information of being a domain member, see the chapter about domain membership. +

    ADS Security Mode (User Level Security)

    Both Samba 2.2 and 3.0 can join an Active Directory domain. This is -possible even if the domain is run in native mode. Active Directory in -native mode perfectly allows NT4-style domain members, contrary to +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. The only thing that Active Directory in native mode prohibits is Backup Domain Controllers running NT4.

    -If you are running Active Directory starting with Samba 3.0 you can -however join as a native AD member. Why would you want to do that? +If you are using Active Directory, starting with Samba-3 you can +join as a native AD member. Why would you want to do that? Your security policy might prohibit the use of NT-compatible authentication protocols. All your machines are running Windows 2000 -and above and all use full Kerberos. In this case Samba as a NT4-style +and above and all use Kerberos. In this case Samba as a NT4-style domain would still require NT-compatible authentication data. Samba in -AD-member mode can accept Kerberos. -

    Example Configuration

    -	realm = your.kerberos.REALM
-	security = ADS
-

    - The following parameter may be required: -

    -	ads server = your.kerberos.server
-

    -Please refer to the Domain Membership and Active Directory -Membership sections for more information regarding this configuration option. -

    Server Security (User Level Security)

    +AD-member mode can accept Kerberos tickets. +

    Example Configuration

    realm = your.kerberos.REALM
    security = ADS

    +The following parameter may be required: +

    ads server = your.kerberos.server

    +Please refer to the chapter on domain membership +for more information regarding this configuration option. +

    Server Security (User Level Security)

    Server security mode is a 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 draw backs. The draw backs 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, 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.

    +

    • 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, 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 login to the -password server by sending exactly the same username/password that +password server by sending exactly the same username/password that it got from the client. If that server is in user level security and accepts the password, then Samba accepts the clients connection. This allows the Samba server to use another SMB -server as the password server. +server as the password server.

    You should also note that at the very start of all this, where the server tells the client what security level it is in, it also tells the client if it supports encryption. If it does then it supplies the client with a random cryptkey. The client will then send all passwords in encrypted form. Samba supports this type of encryption by default.

    -The parameter security = server means that Samba reports to clients that +The parameter security = server means that Samba reports to clients that it is running in user mode but actually passes off all authentication requests to another user mode server. This requires an additional -parameter password server that points to the real authentication server. +parameter password server that points to the real authentication server. That real authentication server can be another Samba server or can be a Windows NT server, the later natively capable of encrypted password support.

    Note

    @@ -229,17 +216,13 @@ lookups because the choice of the target authentication server is arbitrary and 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"
-

    -There are two ways of identifying whether or not a username and password pair was valid -or not. One uses the reply information provided as part of the authentication messaging +

    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 was valid. +One uses the reply information provided as part of the authentication messaging process, the other uses just an error code.

    The down-side of this mode of configuration is the fact that for security reasons Samba @@ -248,9 +231,9 @@ server fails to reject the username and password pair then an alternative mode o identification of validation is used. Where a site uses password lock out after a certain number of failed authentication attempts this will result in user lockouts.

    -Use of this mode of authentication does require there to be a standard Unix account +Use of this mode of authentication does require there to be a standard UNIX account for the user, though this account can be blocked to prevent logons by non-SMB/CIFS clients. -

    Seamless Windows Network Integration

    +

    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, @@ -287,29 +270,26 @@ is definitely not a good idea to re-enable plain text password support in such c The following parameters can be used to work around the issue of Windows 9x clients upper casing usernames and password before transmitting them to the SMB server when using clear text authentication. -

    -        password level = integer
-        username level = integer
-

    +

    password level = integer
    username level = integer

    By default Samba will lower case the username before attempting to lookup the user in the database of local system accounts. Because UNIX usernames conventionally -only contain lower case character, the username level parameter +only contain lower-case character, the username level parameter is rarely needed.

    -However, passwords on UNIX systems often make use of mixed case characters. +However, passwords on UNIX systems often make use of mixed-case characters. This means that in order for a user on a Windows 9x client to connect to a Samba -server using clear text authentication, the password level -must be set to the maximum number of upper case letter which could -appear is a password. Note that the server OS uses the traditional DES version -of crypt(), a password level of 8 will result in case +server using clear text authentication, the password level +must be set to the maximum number of upper case letters which could +appear in a password. Note that if the server OS uses the traditional DES version +of crypt(), a password level of 8 will result in case insensitive passwords as seen from Windows users. This will also result in longer login times as Samba has to compute the permutations of the password string and try them one by one until a match is located (or all combinations fail).

    -The best option to adopt is to enable support for encrypted passwords where ever +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 plain text passwords will eventually lead to user complaints and unhappiness. -

    Common Errors

    +

    Common Errors

    We all make mistakes. It is Ok to make mistakes, so long as they are made in the right places and at the right time. A mistake that causes lost productivity is seldom tolerated. A mistake made in a developmental test lab is expected. @@ -319,25 +299,26 @@ on the Samba mailing lists. Many of these are avoidable by doing you homework be a Samba implementation. Some are the result of misunderstanding of the English language. The English language has many turns of phrase 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 very obvious, but entirely -wrong all the same. It is assumed that security = server means that Samba +wrong all the same. It is assumed that security = server means that Samba will act as a server. Not so! See above - this setting means that Samba will try to use another SMB server as its source of user authentication alone. -

    What makes Samba a Domain Controller?

    -The smb.conf parameter security = domain does NOT really make Samba behave +

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

    What makes Samba a Domain Member?

    -Guess! So many others do. But whatever you do, do NOT think that security = user +

    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 manufacturers manual before the warranty expires! See -the Domain Member section of this Howto for more information. -

    Constantly Losing Connections to Password Server

    +the chapter about domain membership for more information. +

    Constantly Losing Connections to Password Server

    + “ Why does server_validate() simply give up rather than re-establishing 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 server, which means the password hashes submitted by the client would not work on a subsequent -connection, whose session key would be different. So server_validate() must give up. +connection, whose session key would be different. So server_validate() must give up.”

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

    Prev Up Next
    Part II. Server Configuration Basics Home Chapter 5. Domain Control
    + 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. +

    Prev Up Next
    Part II. Server Configuration Basics Home Chapter 5. Domain Control
    diff --git a/docs/htmldocs/StandAloneServer.html b/docs/htmldocs/StandAloneServer.html index a3bdf439af..f85fdfe3fc 100644 --- a/docs/htmldocs/StandAloneServer.html +++ b/docs/htmldocs/StandAloneServer.html @@ -1,9 +1,9 @@ -Chapter 8. Stand-Alone Servers
    Chapter 8. Stand-Alone Servers
    Prev Part II. Server Configuration Basics Next

    Chapter 8. Stand-Alone Servers

    John H. Terpstra

    Samba Team

    Table of Contents

    Features and Benefits
    Background
    Example Configuration
    Reference Documentation Server
    Central Print Serving
    Common Errors

    +Chapter 8. Stand-Alone Servers

    Chapter 8. Stand-Alone Servers
    Prev Part II. Server Configuration Basics Next

    Chapter 8. Stand-Alone Servers

    John H. Terpstra

    Samba Team

    Table of Contents

    Features and Benefits
    Background
    Example Configuration
    Reference Documentation Server
    Central Print Serving
    Common Errors

    Stand-Alone servers are independent of Domain Controllers on the network. They are NOT domain members and function more like workgroup servers. In many cases a stand-alone 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

    Stand-Alone 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 very common installation. @@ -20,7 +20,7 @@ that are queued off a single central server. Everyone needs to be able to print to the printers, there is no need to affect any access controls and no files will be served from the print server. Again a share mode stand-alone server makes a great solution. -

    Background

    +

    Background

    The term stand-alone server means that the server will provide local authentication and access control for all resources that are available from it. In general this means that there will be a @@ -42,50 +42,37 @@ local or on a remote server, even if from the Samba protocol perspective the Samba server is NOT a member of a domain security context.

    Through the use of PAM (Pluggable Authentication Modules) and nsswitch -(the name service switcher) the source of authentication may reside on +(the name service switcher, 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 +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 back end, or even via PAM and Winbind another CIFS/SMB server for authentication. -

    Example Configuration

    +

    Example Configuration

    The following examples 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

    +

    Reference Documentation Server

    Configuration of a read-only data server that EVERYONE can access is very simple. Here is the smb.conf file that will do this. Assume that all the reference documents are stored in the directory /export, that the documents are owned by a user other than nobody. No home directories are shared, that are no users in the /etc/passwd -Unix system database. This is a very simple system to administer. -

    -	# Global parameters
-	[global]
-		workgroup = MYGROUP
-		netbios name = REFDOCS
-		security = SHARE
-		passdb backend = guest
-		wins server = 192.168.1.1
-
-	[data]
-		comment = Data
-		path = /export
-		guest only = Yes
-

    +UNIX system database. This is a very simple system to administer. +

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

    In the above example the machine name is set to REFDOCS, the workgroup is set to the name of the local workgroup so that the machine will appear in with systems users are familiar with. The only password backend required is the "guest" backend so as to allow default unprivileged account names to be used. Given that there is a WINS server on this network we do use it. -

    Central Print Serving

    +

    Central Print Serving

    Configuration of a simple print server is very simple if you have all the right tools on your system.

    Assumptions:

    1. The print server must require no administration

    2. The print spooling and processing system on our print server will be CUPS. - (Please refer to the CUPS Printing chapter for more information). + (Please refer to the chapter about CUPS for more information).

    3. All printers that the print server will service will be network printers. They will be correctly configured, by the administrator, @@ -99,45 +86,27 @@ In this example our print server will spool all incoming print jobs to Samba to the CUPS print processor. Since all incoming connections will be as the anonymous (guest) user, two things will be required:

      Enabling Anonymous Printing

      • - The Unix/Linux system must have a guest account. + 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 following: - 

        +
         $ testparm -s -v | grep "guest account"
-	
        
+

        Then make sure that this account exists in your system password database (/etc/passwd).

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

        +
         root# mkdir /var/spool/samba
 root# chown nobody.nobody /var/spool/samba
 root# chmod a+rwt /var/spool/samba
-	
        
-

      -

      -	# Global parameters
-	[global]
-		workgroup = MYGROUP
-		netbios name = PTRSVR1
-		security = SHARE
-		passdb backend = guest
-		wins server = 192.168.1.1
-
-	[printers]
-		comment = All Printers
-		path = /var/spool/samba
-		printer admin = root
-		guest ok = Yes
-		printable = Yes
-		printing = cups
-		use client driver = Yes
-		browseable = No

      -

    Common Errors

    +

    +

    Example 8.2. smb.conf for anonymous printing

    # Global parameters
    [global]
    workgroup = MIDEARTH
    netbios name = GANDALF
    security = SHARE
    passdb backend = guest
    wins server = noldor
    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

    +

    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 7. Domain Membership Home Chapter 9. MS Windows Network Configuration Guide
    +

    Prev Up Next
    Chapter 7. Domain Membership Home Chapter 9. MS Windows Network Configuration Guide
    diff --git a/docs/htmldocs/VFS.html b/docs/htmldocs/VFS.html index 6b520d792a..ffa767e6c9 100644 --- a/docs/htmldocs/VFS.html +++ b/docs/htmldocs/VFS.html @@ -1,26 +1,19 @@ -Chapter 20. Stackable VFS modules
    Chapter 20. Stackable VFS modules
    Prev Part III. Advanced Configuration Next

    Chapter 20. Stackable VFS modules

    Jelmer R. Vernooij

    The Samba Team

    John H. Terpstra

    Samba Team

    Tim Potter

    Simo Sorce

    original vfs_skel README

    Alexander Bokovoy

    original vfs_netatalk docs

    Stefan Metzmacher

    Update for multiple modules

    Table of Contents

    Features and Benefits
    Discussion
    Included modules
    audit
    extd_audit
    fake_perms
    recycle
    netatalk
    VFS modules available elsewhere
    DatabaseFS
    vscan
    Common Errors

    Features and Benefits

    +Chapter 20. Stackable VFS modules

    Chapter 20. Stackable VFS modules
    Prev Part III. Advanced Configuration Next

    Chapter 20. Stackable VFS modules

    Jelmer R. Vernooij

    The Samba Team

    John H. Terpstra

    Samba Team

    Tim Potter

    Simo Sorce

    original vfs_skel README

    Alexander Bokovoy

    original vfs_netatalk docs

    Stefan Metzmacher

    Update for multiple modules

    Table of Contents

    Features and Benefits
    Discussion
    Included modules
    audit
    extd_audit
    fake_perms
    recycle
    netatalk
    VFS modules available elsewhere
    DatabaseFS
    vscan

    Features and Benefits

    Since Samba-3, there is support for stackable VFS(Virtual File System) modules. Samba passes each request to access the unix file system thru the loaded VFS modules. This chapter covers all the modules that come with the samba source and references to some external modules. -

    Discussion

    +

    Discussion

    If not supplied with your platform distribution binary Samba package you may have problems to compile 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 +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: -

    -[audit]
-        comment = Audited /data directory
-        path = /data
-        vfs objects = audit recycle
-        writeable = yes
-        browseable = yes
-

    +

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

    @@ -32,46 +25,52 @@ directory in the root directory of the samba installation (usually Some modules can be used twice for the same share. This can be done using a configuration similar to the one below. -

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

    -

    extd_audit

    +

    • share

    • connect/disconnect

    • directory opens/create/remove

    • file open/close/rename/unlink/chmod

    +

    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 file/s. The loglevel for this module is set in the smb.conf file.

    The logging information that will be written to the smbd log file is controlled by - the log level parameter in smb.conf. The + the log level parameter in smb.conf. The following information will be recorded: -

    Table 20.1. Extended Auditing Log Information

    Log LevelLog Details - File and Directory Operations
    0Creation / Deletion
    1Create / Delete / Rename / Permission Changes
    2Create / Delete / Rename / Perm Change / Open / Close

    fake_perms

    +

    Table 20.1. Extended Auditing Log Information

    Log LevelLog Details - File and Directory Operations
    0Creation / Deletion
    1Create / Delete / Rename / Permission Changes
    2Create / Delete / Rename / Perm Change / Open / Close

    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 will report to the client that the Profile files and directories are writable. 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. When used any unlink call will be intercepted and files moved to the recycle - directory instead of being deleted. + directory instead of being deleted. This gives the same + effect as the "Recycle Bin" on Windows computers.

    Supported options: -

    recycle:repository

    FIXME

    recycle:keeptree

    FIXME

    recycle:versions

    FIXME

    recycle:touch

    FIXME

    recycle:maxsize

    FIXME

    recycle:exclude

    FIXME

    recycle:exclude_dir

    FIXME

    recycle:noversions

    FIXME

    -

    netatalk

    +

    recycle:repository

    Relative path of the directory where deleted files should be moved to

    recycle:keeptree

    Specifies whether the directory structure should + be kept or if the files in the directory that is being + deleted should be kept seperately 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: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 deleted in the regular way. +

    recycle:noversions

    Opposite of recycle:versions. If both options are specified, this one takes precedence.

    +

    netatalk

    A netatalk module, that will ease co-existence of samba and netatalk file sharing services.

    Advantages compared to the old netatalk module: -

    it doesn't care about creating of .AppleDouble forks, just keeps them in sync
    if a share in smb.conf doesn't contain .AppleDouble item in hide or veto list, it will be added automatically

    -

    VFS modules available elsewhere

    +

    • it doesn't care about creating of .AppleDouble forks, just keeps them in sync

    • if a share in smb.conf doesn't contain .AppleDouble item in hide or veto list, it will be added automatically

    +

    VFS modules available elsewhere

    This section contains a listing of various other VFS modules that have been posted but don't currently reside in the Samba CVS tree for one reason or another (e.g. it is easy for the maintainer @@ -79,7 +78,7 @@ 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: http://www.css.tayloru.edu/~elorimer/databasefs/index.php

    By Eric Lorimer.

    I have created a VFS module which implements a fairly complete read-only @@ -94,12 +93,10 @@ should be implied due to its presence here. Any feedback would be appreciated: comments, suggestions, patches, etc... If nothing else, hopefully it might prove useful for someone else who wishes to create a virtual filesystem. -

    vscan

    URL: http://www.openantivirus.org/

    +

    vscan

    URL: http://www.openantivirus.org/

    samba-vscan is a proof-of-concept module for Samba, which uses the VFS (virtual file system) features of Samba 2.2.x/3.0 alphaX. Of course, Samba has to be compiled with VFS support. samba-vscan supports various virus scanners and is maintained by Rainer Link. -

    Common Errors

    -There must be some gotchas we should record here! Jelmer??? -

    Prev Up Next
    Chapter 19. CUPS Printing Support in Samba 3.0 Home Chapter 21. Integrated Logon Support using Winbind
    +

    Prev Up Next
    Chapter 19. CUPS Printing Support in Samba 3.0 Home Chapter 21. Winbind: Use of Domain Accounts
    diff --git a/docs/htmldocs/bugreport.html b/docs/htmldocs/bugreport.html index 9ae4797d31..49eb2117ca 100644 --- a/docs/htmldocs/bugreport.html +++ b/docs/htmldocs/bugreport.html @@ -1,4 +1,4 @@ -Chapter 35. Reporting Bugs
    Chapter 35. Reporting Bugs
    Prev Part V. Troubleshooting Next

    Chapter 35. Reporting Bugs

    Jelmer R. Vernooij

    The Samba Team

    Someone; Tridge or Karl Auer perhaps?

    27 June 1997

    Table of Contents

    Introduction
    General info
    Debug levels
    Internal errors
    Attaching to a running process
    Patches

    Introduction

    Please report bugs using +Chapter 35. Reporting Bugs

    Chapter 35. Reporting Bugs
    Prev Part V. Troubleshooting Next

    Chapter 35. Reporting Bugs

    Jelmer R. Vernooij

    The Samba Team

    Andrew Tridgell

    Samba Team

    27 June 1997

    Table of Contents

    Introduction
    General info
    Debug levels
    Internal errors
    Attaching to a running process
    Patches

    Introduction

    Please report bugs using bugzilla.

    Please take the time to read this file before you submit a bug report. Also, please see if it has changed between releases, as we @@ -20,7 +20,7 @@ that list that 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 info

    +

    General info

    Before submitting a bug report check your config for silly errors. Look in your log files for obvious messages that tell you that you've misconfigured something and run testparm to test your config @@ -32,42 +32,38 @@ This is very important. If you include part of a log file with your bug report then be sure to annotate it with exactly what you were doing on the client at the time, and exactly what the results were. -

    Debug levels

    +

    Debug levels

    If the bug has anything to do with Samba behaving incorrectly as a server (like refusing to open a file) then the log files will probably be very 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 +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 use: -

    -log level = 10
-log file = /usr/local/samba/lib/log.%m
-include = /usr/local/samba/lib/smb.conf.%m
-

    +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

    then 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 you to +log level may be useful. This also allows you to experiment with different security systems, protocol levels etc on just one machine.

    -The smb.conf entry log level -is synonymous with the parameter debuglevel that has +The smb.conf entry log level +is synonymous with the parameter debuglevel that has been used in older versions of Samba and is being retained for backwards compatibility of smb.conf files.

    -As the log level value is increased you will record +As the log level value is increased you will record a significantly increasing level of 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 VERY large volume of log data. -

    Internal errors

    +

    Internal errors

    If you get a INTERNAL ERROR message 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 @@ -80,13 +76,13 @@ 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
+
    +$ gdb smbd core
 
    
 adding appropriate paths to smbd and core so gdb can find them. If you
 don't have gdb then try dbx. Then within the debugger
@@ -100,7 +96,7 @@ 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
 don't know assembly, including this info 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 @@ -110,10 +106,10 @@ to the running process using Then use c to continue and try to cause the core dump using the client. The debugger should catch the fault and tell you where it occurred. -

    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 34. Analysing and solving samba problems Home Part VI. Appendixes
    +

    Prev Up Next
    Chapter 34. Analysing and solving samba problems Home Part VI. Appendixes
    diff --git a/docs/htmldocs/compiling.html b/docs/htmldocs/compiling.html index d8b85602d9..95cdb0f581 100644 --- a/docs/htmldocs/compiling.html +++ b/docs/htmldocs/compiling.html @@ -1,8 +1,8 @@ -Chapter 36. How to compile SAMBA
    Chapter 36. How to compile SAMBA
    Prev Part VI. Appendixes Next

    Chapter 36. How to compile SAMBA

    Jelmer R. Vernooij

    The Samba Team

    Someone; Jerry perhaps?

    22 May 2001

    18 March 2003

    Table of Contents

    Access Samba source code via CVS
    Introduction
    CVS 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 and nmbd
    Starting from inetd.conf
    Alternative: starting it as a daemon
    Common Errors

    +Chapter 36. How to compile Samba

    Chapter 36. How to compile Samba
    Prev Part VI. Appendixes Next

    Chapter 36. How to compile Samba

    Jelmer R. Vernooij

    The Samba Team

    Andrew Tridgell

    Samba Team

    22 May 2001

    18 March 2003

    Table of Contents

    Access Samba source code via CVS
    Introduction
    CVS 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 and nmbd
    Starting from inetd.conf
    Alternative: starting it as a daemon

    You can obtain the samba source from the samba website. To obtain a development version, you can download samba from CVS or using rsync. -

    Access Samba source code via CVS

    Introduction

    +

    Access Samba source code via CVS

    Introduction

    Samba is developed in an open environment. Developers use CVS (Concurrent Versioning System) to "checkin" (also known as "commit") new source code. Samba's various CVS branches can @@ -11,12 +11,12 @@ detailed in this chapter.

    This chapter is a modified version of the instructions found at http://samba.org/samba/cvs.html -

    CVS Access to samba.org

    +

    CVS Access to samba.org

    The machine samba.org runs a publicly accessible CVS 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 CVS server on this host. -

    Access via CVSweb

    +

    Access via CVSweb

    You can access the source code via your favourite WWW browser. This allows you to access the contents of individual files in the repository and also to look at the revision @@ -24,7 +24,7 @@ history and commit logs of individual files. You can also ask for a diff listing between any two versions on the repository.

    Use the URL : http://samba.org/cgi-bin/cvsweb -

    Access via cvs

    +

    Access via cvs

    You can also access the source code via a normal cvs client. This gives you much more control over what you can do with the repository and allows you to checkout whole source trees @@ -74,7 +74,7 @@ on this system just substitute the correct package name the following command from within the samba directory:

    cvs update -d -P -

    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 CVS tree at ftp://pserver.samba.org/pub/unpacked and also via anonymous rsync at rsync://pserver.samba.org/ftp/unpacked/. I recommend using rsync rather than ftp. @@ -83,7 +83,7 @@ on this system just substitute the correct package name The disadvantage of the unpacked trees is that they do not support automatic merging of local changes like CVS does. rsync access is most convenient for an initial install. -

    Verifying Samba's PGP signature

    +

    Verifying Samba's PGP signature

    In these days of insecurity, it's 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 @@ -91,39 +91,43 @@ standard reflex.

    With that said, go ahead and download the following files: 

    -$  wget http://us1.samba.org/samba/ftp/samba-2.2.8a.tar.asc
-$  wget http://us1.samba.org/samba/ftp/samba-pubkey.asc
+$ wget http://us1.samba.org/samba/ftp/samba-2.2.8a.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: 

    -	$ gpg --import samba-pubkey.asc
+$ gpg --import samba-pubkey.asc

    And verify the Samba source code integrity with: 

    -	$ gzip -d samba-2.2.8a.tar.gz
-	$ gpg --verify samba-2.2.8a.tar.asc
+$ gzip -d samba-2.2.8a.tar.gz
+$ gpg --verify samba-2.2.8a.tar.asc

    If you receive a message like, "Good signature from Samba Distribution Verification Key..." then all is well. The warnings about trust relationships can be ignored. An example of what you would not want to see would be: -

    +

    + gpg: BAD signature from "Samba Distribution Verification Key" -

    Building the Binaries

    To do this, first run the program ./configure + +

    Building the Binaries

    + To do this, first run the program ./configure in the source directory. This should automatically configure Samba for your operating system. If you have unusual - needs then you may wish to run

    root# ./configure --help -

    first to see what special options you can enable. - Then executing

    root# make

    will create the binaries. Once it's successfully - compiled you can use

    root# make install

    to install the binaries and manual pages. You can - separately install the binaries and/or man pages using

    root# make installbin -

    and

    root# make installman -

    Note that if you are upgrading for a previous version + needs then you may wish to run

    root# ./configure --help
+

    first to see what special options you can enable. + Then executing

    root# make

    will create the binaries. Once it's successfully + compiled you can use 

    root# make install

    to install the binaries and manual pages. You can + separately install the binaries and/or man pages using

    root# make installbin
+

    and

    root# make installman
+

    Note that if you are upgrading for a previous version of Samba you might like to know that the old versions of the binaries will be renamed with a ".old" extension. You - can go back to the previous version with

    root# make revert -

    if you find this version a disaster!

    Compiling samba with Active Directory support

    In order to compile samba with ADS support, you need to have installed + can go back to the previous version with

    root# make revert
+

    if you find this version a disaster!

    Compiling samba with Active Directory support

    In order to compile samba with ADS support, you need to have installed on your system:

    • the MIT kerberos development libraries (either install from the sources or use a package). The Heimdal libraries will not work.

    • the OpenLDAP development libraries.

    If your kerberos libraries are in a non-standard location then @@ -135,16 +139,17 @@ example of what you would not want to see would be: #define HAVE_LDAP 1

    If it doesn't then 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:

    -

    libkrb5-dev
    krb5-user

    -

    Installing the required packages for RedHat

    On RedHat this means you should have at least:

    -

    krb5-workstation (for kinit)
    krb5-libs (for linking with)
    krb5-devel (because you are compiling from source)

    + out why and fix it.

    Installing the required packages for Debian

    On Debian you need to install the following packages:

    +

    • libkrb5-dev

    • krb5-user

    +

    Installing the required packages for RedHat

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

    Note that these are not standard on a RedHat install, and you may need - to get them off CD2.

    Starting the smbd and nmbd

    You must choose to start smbd and nmbd either + to get them off CD2.

    Starting the smbd and nmbd

    You must choose to start smbd 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 inetd, or you can start them as + by inetd or xinetd, + or you can start them as daemons either from the command line or in /etc/rc.local. See the man pages for details on the command line options. Take particular care to read @@ -152,7 +157,7 @@ example of what you would not want to see would be: Samba. In many cases you must be root.

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

    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

    Next edit your /etc/inetd.conf @@ -161,12 +166,13 @@ example of what you would not want to see would be: netbios-ns dgram udp wait root /usr/local/samba/bin/nmbd nmbd

    The exact syntax of /etc/inetd.conf varies between unixes. Look at the other entries in inetd.conf - for a guide.

    Note

    Some unixes already have entries like netbios_ns + 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 (note the underscore) in /etc/services. You must either 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 +

    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 ifconfig as root if you don't know what the broadcast is for your @@ -177,8 +183,9 @@ example of what you would not want to see would be: This means you shouldn't use spaces between the options and arguments, or you should use a script, and start the script from inetd.

    Restart inetd, perhaps just send - it a HUP. If you have installed an earlier version of nmbd then - you may need to kill nmbd as well.

    Alternative: starting it as a daemon

    To start the server as a daemon you should create + it a HUP. 

    +			root# killall -HUP inetd
+

    Alternative: starting it as a daemon

    To start the server as a daemon you should create a script something like this one, perhaps calling it startsmb.

     		#!/bin/sh
@@ -190,12 +197,4 @@ example of what you would not want to see would be:
 		
    To kill it send a kill signal to the processes 
 			nmbd and smbd.
    Note
    If you use the SVR4 style init system then 
 		you may like to look at the examples/svr4-startup
-		script to make Samba fit into that system.

    Common Errors

    “ -I'm using gcc 3 and I've compiled Samba-3 from the CVS and the -binaries are very large files (40 Mb and 20 Mb). I've the same result with ---enable-shared ? -” -

    -The dwarf format used by GCC 3 for storing debugging symbols is very inefficient. -Strip the binaries, don't compile with -g or compile with -gstabs. -

    Prev Up Next
    Part VI. Appendixes Home Chapter 37. Portability
    + script to make Samba fit into that system.

    Prev Up Next
    Part VI. Appendixes Home Chapter 37. Portability
    diff --git a/docs/htmldocs/diagnosis.html b/docs/htmldocs/diagnosis.html index ff3099ac72..ea84661d30 100644 --- a/docs/htmldocs/diagnosis.html +++ b/docs/htmldocs/diagnosis.html @@ -1,4 +1,4 @@ -Chapter 33. The Samba checklist
    Chapter 33. The Samba checklist
    Prev Part V. Troubleshooting Next

    Chapter 33. The Samba checklist

    Andrew Tridgell

    Samba Team

    Jelmer R. Vernooij

    The Samba Team

    Wed Jan 15

    Table of Contents

    Introduction
    Assumptions
    The tests
    Still having troubles?

    Introduction

    +Chapter 33. The Samba checklist

    Chapter 33. The Samba checklist
    Prev Part V. Troubleshooting Next

    Chapter 33. The Samba checklist

    Andrew Tridgell

    Samba Team

    Jelmer R. Vernooij

    The 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 @@ -13,7 +13,7 @@ to solve a problem. If you send one of the samba mailing lists an email saying "it doesn't work" and you have not followed this test procedure then 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.

    @@ -23,14 +23,7 @@ It is also assumed you know the name of an available share in your smb.conf. I will assume this share is called tmp. You can add a tmp share like this by adding the following to smb.conf: -

    -
-[tmp]
- comment = temporary files 
- path = /tmp
- read only = yes
-
-

    +

    Example 33.1. smb.conf with [tmp] share

    [tmp]
    comment = temporary files
    path = /tmp
    read only = yes

    Note

    These tests assume version 3.0 or later of the samba suite. Some commands shown did not exist in earlier versions. @@ -43,7 +36,7 @@ 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). @@ -54,7 +47,7 @@ depending on how or if you specified logging in your smb.co

    If you make changes to your smb.conf file while going through these test, don't forget to restart smbd and nmbd. -

    The tests

    Procedure 33.1. Diagnosing your samba server

    1. +

    The tests

    Procedure 33.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. @@ -100,6 +93,8 @@ 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 file/s for your particular system implementation of @@ -116,26 +111,20 @@ 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 following smb.conf file entries: -

      -	hosts deny = ALL
-	hosts allow = xxx.xxx.xxx.xxx/yy
-	bind interfaces only = Yes
-

      +

      hosts deny = ALL
      hosts allow = xxx.xxx.xxx.xxx/yy
      bind interfaces only = Yes

      In the above, 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 to: -

      -	hosts deny = ALL
-	hosts allow = xxx.xxx.xxx.xxx/yy 127.
-

      -Do not use the bind interfaces only parameter where you +

      hosts deny = ALL
      hosts allow = xxx.xxx.xxx.xxx/yy 127.

      +Do not use the bind interfaces only parameter where you may wish to use the samba password change facility, or where smbclient may need to access a local service for name resolution or for local resource -connections. (Note: the bind interfaces only parameter deficiency +connections. (Note: the bind interfaces only parameter deficiency where it will not allow connections to the loopback address will be fixed soon).

      + Another common cause of these two errors is having something already running on port 139, such as Samba (ie: smbd is running from inetd already) or @@ -178,20 +167,20 @@ messages from several hosts. If this doesn't give a similar result 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 +interfaces option in smb.conf to manually configure your IP address, broadcast and netmask.

      If your PC and server aren't on the same subnet then you will need to -use the -B option to set the broadcast address to that of the PCs +use the -B option to set the broadcast address to that of the PCs subnet.

      This test will probably fail if your subnet mask and broadcast address are not correct. (Refer to TEST 3 notes above). -

    2. +

    3. Run the command smbclient //BIGSERVER/TMP. You should then be prompted for a password. You should use the password of the account you are logged into the unix box with. If you want to test with -another account then add the -U accountname option to the end of +another account then add the -U accountname option to the end of the command line. eg: smbclient //bigserver/tmp -Ujohndoe

      Note

      @@ -208,14 +197,13 @@ If it says bad password then the likely causes ar you have shadow passwords (or some other password system) but didn't compile in support for them in smbd

    4. - your valid users configuration is incorrect + your valid users configuration is incorrect

    5. - you have a mixed case password and you haven't enabled the password - level option at a high enough level + you have a mixed case password and you haven't enabled the password level option at a high enough level

    6. - the path = line in smb.conf is incorrect. Check it with testparm + the path line in smb.conf is incorrect. Check it with testparm

    7. - you enabled password encryption but didn't map unix to samba users + you enabled password encryption but didn't map unix to samba users. Run 

      smbpasswd -a username

      .

    Once connected you should be able to use the commands dir get put etc. @@ -265,14 +253,13 @@ installed or your smb.conf is incorrect. make sure your hosts and other config lines in smb.conf are correct.

    It's also possible that the server can't work out what user name to -connect you as. To see if this is the problem add the line user = -username to the [tmp] section of +connect you as. To see if this is the problem add the line user = username to the [tmp] section of smb.conf where username is the username corresponding to the password you typed. If you find this fixes things you may need the username mapping option.

    It might also be the case that your client only sends encrypted passwords -and you have encrypt passwords = no in smb.conf +and you have encrypt passwords = no in smb.conf Turn it back on to fix.

  • Run the command nmblookup -M testgroup where @@ -283,20 +270,18 @@ master browser for that workgroup. If you don't then the election process has failed. Wait a minute to see if it is just being slow then try again. If it still fails after that then look at the browsing options you have set in smb.conf. Make -sure you have preferred master = yes to ensure that +sure you have preferred master = yes to ensure that an election is held at startup.

  • ->From file manager try to browse the server. Your samba server should +From file manager try to browse the server. Your samba server should appear in the browse list of your local workgroup (or the one you -specified in smb.conf). You should be able to double click on the name +specified in smb.conf). You should be able to double click on the name of the server and get a list of shares. If you get a "invalid password" error when you do then you are probably running WinNT and it is refusing to browse a server that has no encrypted password capability and is in user level security mode. In this case either set -security = server AND -password server = Windows_NT_Machine in your -smb.conf file, or make sure encrypted passwords is +security = server AND +password server = Windows_NT_Machine in your +smb.conf file, or make sure encrypt passwords is set to "yes". -

    • Still having troubles?

    Read the chapter on -Analysing and Solving Problems. -

    Prev Up Next
    Part V. Troubleshooting Home Chapter 34. Analysing and solving samba problems
    +

    Prev Up Next
    Part V. Troubleshooting Home Chapter 34. Analysing and solving samba problems
    diff --git a/docs/htmldocs/domain-member.html b/docs/htmldocs/domain-member.html index 59040dfebc..313c6e0fc7 100644 --- a/docs/htmldocs/domain-member.html +++ b/docs/htmldocs/domain-member.html @@ -1,4 +1,4 @@ -Chapter 7. Domain Membership
    Chapter 7. Domain Membership
    Prev Part II. Server Configuration Basics Next

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

    Table of Contents

    Features and Benefits
    MS Windows Workstation/Server Machine Trust Accounts
    Manual Creation of Machine Trust Accounts
    Using NT4 Server Manager to Add Machine Accounts to the Domain
    "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
    Setup your smb.conf
    Setup your /etc/krb5.conf
    Create the computer account
    Test your server setup
    Testing with smbclient
    Notes
    Common Errors
    Can Not Add Machine Back to Domain
    Adding Machine to Domain Fails

    +Chapter 7. Domain Membership

    Chapter 7. Domain Membership
    Prev Part II. Server Configuration Basics Next

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

    Table of Contents

    Features and Benefits
    MS Windows Workstation/Server Machine Trust Accounts
    Manual Creation of Machine Trust Accounts
    Using NT4 Server Manager to Add Machine Accounts to the Domain
    "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
    Setup your smb.conf
    Setup your /etc/krb5.conf
    Create the computer account
    Test your server setup
    Testing with smbclient
    Notes
    Common Errors
    Can Not 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, @@ -8,12 +8,11 @@ This chapter covers background information pertaining to domain membership, 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 within the current MS Windows networking world and particularly in the -Unix/Linux networking and administration world, a considerable level of +UNIX/Linux networking and administration world, a considerable level of mis-information, incorrect understanding, and a lack of knowledge. Hopefully this chapter will fill the voids. -

    Features and Benefits

    -MS Windows workstations and servers that want to participate in domain -security need to +

    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 chapter describes the process that must be followed to make a workstation @@ -48,7 +47,7 @@ Domain membership has many advantages: client or server, other than the central Domain database (either NT4/Samba SAM style Domain, NT4 Domain that is back ended with an LDAP directory, or via an Active Directory infrastructure) -

    MS Windows Workstation/Server Machine Trust Accounts

    +

    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, @@ -73,12 +72,12 @@ as follows:

    • A Domain Security Account (stored in the - passdb backend that has been configured 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 - which contains the unix login ID, the Unix user identifier (UID), and the + which 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.

      @@ -87,17 +86,18 @@ as follows: older smbpasswd file did. The extra information enables new user account controls to be used.

    • - A corresponding Unix account, typically stored in + 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 + simplified mode of operation that does not require UNIX user accounts, but this may not be a feature of the early releases of Samba-3.

    -

    +

    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. + 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 so long as the user is @@ -105,28 +105,39 @@ There are three ways to create machine trust accounts:

    • "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 + (For security, this is the recommended method.) The corresponding UNIX account may be created automatically or manually. -

    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. +create the corresponding UNIX account in /etc/passwd. This can be done using vipw or another 'add user' command -that is normally used to create new Unix accounts. The following is an example for a Linux based Samba server: -

    -root# /usr/sbin/useradd -g 100 -d /dev/null -c "machine nickname" -s /bin/false machine_name$ +that is normally used to create new UNIX accounts. The following is an example for a Linux based Samba server: + + + +

    +

    +root# /usr/sbin/useradd -g 100 -d /dev/null -c "machine nickname" \
+   -s /bin/false machine_name$ 
+
 root# passwd -l machine_name$
+

    + On *BSD systems, this can be done using the chpass utility:

    -root# chpass -a "machine_name$:*:101:100::0:0:Workstation machine_name:/dev/null:/sbin/nologin" +

    +root# chpass -a \
+  "machine_name$:*:101:100::0:0:Workstation machine_name:/dev/null:/sbin/nologin"
+

    The /etc/passwd entry will list the machine name with a "$" appended, won't have a password, will have a null shell and no home directory. For example a machine named 'doppy' would have an /etc/passwd entry like this: 

    -doppy$:x:505:501:machine_nickname:/dev/null:/bin/false
+doppy$:x:505:100:machine_nickname:/dev/null:/bin/false

    Above, machine_nickname can be any descriptive name for the client, i.e., BasementComputer. @@ -135,9 +146,10 @@ name of the client to be joined to the domain. The "$" must be appended to the NetBIOS name of the client or Samba will not recognize this as a machine trust account.

    -Now that the corresponding Unix account has been created, the next step is to create +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 smbpasswd(8) command +machine trust account password. This can be done using the +smbpasswd command as shown here: 

    @@ -146,28 +158,32 @@ as shown here:
 
    
 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.
+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 which the client joins the domain and 
 	changes the password, your domain is vulnerable to an intruder joining 
 	your domain using a machine with the same NetBIOS name.  A PDC inherently 
 	trusts members of the domain and will serve out a large degree of user 
 	information to such clients.  You have been warned!
-

    Using NT4 Server Manager to Add Machine Accounts to the Domain

    +

    Using NT4 Server Manager to Add Machine Accounts to the Domain

    If the machine from which you are trying to manage the domain is an -MS Windows NT4 workstation +MS Windows NT4 workstation or MS Windows 200x / XP Professional then the tool of choice is the package called SRVTOOLS.EXE. -When executed in the target directory this will unpack -SrvMge.exe and UsrMgr.exe (both are -Domain Management tools for MS Windows NT4 workstation. +When executed in the target directory this will unpack SrvMge.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 this will unpack the same tools but for use on +this platform.

    -If your workstation is any other MS Windows product you should download the -Nexus.exe package from the Microsoft web site. When executed -from the target directory this will unpack the same tools but for use on -MS Windows 9x/Me/200x/XP. +Further information about these tools may be obtained from the following locations: +http://support.microsoft.com/default.aspx?scid=kb;en-us;173673 +http://support.microsoft.com/default.aspx?scid=kb;en-us;172540

    Launch the srvmgr.exe (Server Manager for Domains) and follow these steps:

    Procedure 7.1. Server Manager Account Machine Account Management

    1. @@ -187,25 +203,21 @@ Launch the srvmgr.exe (Server Manager for Domains) and fo Add NT Workstation of Server, then enter the machine name in the field provided, then click the Add button. -

    "On-the-Fly" Creation of Machine Trust Accounts

    +

    "On-the-Fly" Creation of Machine Trust Accounts

    The second (and recommended) way of creating machine trust accounts is simply to allow the Samba server to create them as needed when the client is joined to the domain. -

    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 +

    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.

    Below is an example for a RedHat Linux system. -

    -[global]
-   # <...remainder of parameters...>
-   add machine script = /usr/sbin/useradd -d /dev/null -g 100 -s /bin/false -M %u 
-

    Making an MS Windows Workstation or Server a Domain Member

    +

    [global]
    # <...remainder of parameters...>
    add machine script = /usr/sbin/useradd -d /dev/null -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 of server a member of the domain varies with the version of Windows: -

    Windows 200x XP Professional

    +

    Windows 200x XP Professional

    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 administrative account (i.e., a Samba account that has root privileges on the @@ -219,13 +231,13 @@ with the version of Windows: The name of the account that is used to create domain member machine accounts can be anything the network administrator may choose. If it is other than root then this is easily mapped to root using the file pointed to be the smb.conf parameter - username map = /etc/samba/smbusers. + username map = /etc/samba/smbusers.

    The session key of the Samba administrative account acts as an encryption key for setting the password of the machine trust account. The machine trust account will be created on-the-fly, or updated if it already exists. -

    Windows NT4

    +

    Windows NT4

    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. @@ -238,8 +250,8 @@ with the version of Windows: Domain. In this case, joining the domain proceeds as above for Windows 2000 (i.e., you must supply a Samba administrative account when prompted). -

    Samba

    Joining a Samba client to a domain is documented in - the Domain Member Server section of this chapter chapter. +

    Samba

    Joining a Samba client to a domain is documented in + the domain member chapter.

    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 @@ -255,46 +267,38 @@ This can be LDAP (from OpenLDAP), or Sun's iPlanet, of NetWare Directory Server, etc.

    -Please refer to the Domain Control chapter +Please refer to the chapter on setting up a PDC for more information regarding how to create a domain machine account for a domain member server as well as for information regarding how to enable the Samba domain member machine to join the domain and to be fully trusted by it. -

    Joining an NT4 type Domain with Samba-3

    -

    Table 7.1. Assumptions

    NetBIOS name:SERV1
    Win2K/NT domain name:DOM
    Domain's PDC NetBIOS name:DOMPDC
    Domain's BDC NetBIOS names:DOMBDC1 and DOMBDC2

    +

    Joining an NT4 type Domain with Samba-3

    +

    Table 7.1. Assumptions

    NetBIOS name:SERV1
    Win2K/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 + Change (or add) your + security line in the [global] section of your smb.conf to read:

    -

    -security = domain
-

    +

    security = domain

    -Next change the -workgroup line in the [global] +Next change the workgroup line in the [global] section to read:

    -

    -workgroup = DOM
-

    +

    workgroup = MIDEARTH

    as this is the name of the domain we are joining.

    -You must also have the parameter -encrypt passwords set to yes +You must also have the parameter +encrypt passwords set to yes in order for your users to authenticate to the NT PDC.

    -Finally, add (or modify) a -password server line in the [global] +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 primary and backup domain controllers Samba will attempt to contact in order to authenticate users. Samba will @@ -306,9 +310,7 @@ Alternatively, if you want smbd to automatically determine 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. This method either broadcasts or uses a WINS database in order to @@ -317,7 +319,7 @@ find domain controllers to authenticate against. In order to actually join the domain, you must run this command: 

    -root# net join -S DOMPDC -UAdministrator%password
+root# net rpc join -S DOMPDC -UAdministrator%password

    If the -S DOMPDC argument is not given then @@ -334,8 +336,8 @@ you will see the message: Joined domain DOM. or Joined 'SERV1' to realm 'MYREALM'

    -in your terminal window. See the -net(8) man page for more details. +in your terminal window. See the +net man page for more details.

    This process joins the server to the domain without having to create the machine trust account on the PDC beforehand. @@ -353,21 +355,25 @@ 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! -

    Why is this better than security = server?

    +clients to begin using domain security! The way you can restart your +samba daemons depends on your distribution, but in most cases running +

    +	root# /etc/init.d/samba restart
+

    +does the job. +

    Why is this better than security = server?

    Currently, domain security in Samba doesn't free you from -having to create local Unix users to represent the users attaching +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 +to be a local UNIX user fred to represent that user in the UNIX filesystem. This is very similar to the older Samba security mode -security = server, +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 the Winbind chapter -for information on a system to automatically -assign UNIX uids and gids to Windows NT Domain users and groups. + Please refer to the chapter on winbind for information on a system +to automatically assign UNIX uids and gids to Windows NT Domain users and groups.

    The advantage to domain-level security is that the authentication in domain-level security is passed down the authenticated @@ -377,11 +383,11 @@ 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 +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 security = domain, +out of available connections. With security = domain, however, the Samba daemons connect to the PDC/BDC only for as long as is necessary to authenticate the user, and then drop the connection, thus conserving PDC connection resources. @@ -395,41 +401,39 @@ Much of the text of this document was first published in the Web magazine LinuxWorld as the article Doing the NIS/NT Samba. -

    Samba ADS Domain Membership

    +

    Samba ADS Domain Membership

    This is a rough guide to setting up Samba 3.0 with Kerberos authentication against a Windows2000 KDC. A familiarity with Kerberos is assumed. -

    Setup your smb.conf

    +

    Setup your smb.conf

    You must use at least the following 3 options in smb.conf: -

    -	realm = your.kerberos.REALM
-	security = ADS
-	encrypt passwords = yes
-

    +

    realm = your.kerberos.REALM
    security = ADS
    encrypt passwords = yes

    In case samba can't figure out your ads server using your realm name, use the -ads server option in smb.conf: -

    -	ads server = your.kerberos.server
-

    +ads server option in smb.conf: +

    ads server = your.kerberos.server

    Note

    You do not need a smbpasswd file, and older clients will be authenticated as -if security = domain, although it won't do any harm and +if security = domain, although it won't do any harm and allows you to have local users not in the domain. It is expected that the above required options will change soon when active directory integration will get better. -

    Setup your /etc/krb5.conf

    +

    Setup your /etc/krb5.conf

    The minimal configuration for krb5.conf is: 

    +[libdefaults]
+   default_realm = YOUR.KERBEROS.REALM
+
 	[realms]
-	    YOUR.KERBEROS.REALM = {
-		kdc = your.kerberos.server
+	YOUR.KERBEROS.REALM = {
+	kdc = your.kerberos.server
 	    }
-

    +

    Test your config by doing a kinit USERNAME@REALM and making sure that your password is accepted by the Win2000 KDC.

    Note

    The realm must be uppercase or you will get Cannot find KDC for -requested realm while getting initial credentials error. +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 @@ -454,13 +458,13 @@ is only needed if you want Kerberos support for smbd

    Create the computer account

    As a user that has write permission on the Samba private directory (usually root) run: -

    -	root# net join -U Administrator%password
+
    +root#  net ads join -U Administrator%password
 
    
-
    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 libs and headers are installed.
-	
    net join prompts for user name
    You need to login to the domain using kinit
+	
    net ads join prompts for user name
    You need to login to the domain using kinit
 	USERNAME@REALM.
 	USERNAME must be a user who has rights to add a machine
 	to the domain.  
    
@@ -473,41 +477,41 @@ On a Windows 2000 client try net use * \\server\shareklist tickets. Did you get a ticket for the
 server? Does it have an encoding type of DES-CBC-MD5 ? 
-
    Testing with smbclient
    
+
    Testing with smbclient
    
 On your Samba server try to login to a Win2000 server or your Samba
 server using smbclient and Kerberos. Use smbclient as usual, but
-specify the -k option to choose Kerberos authentication.
-
    Notes
    
+specify the -k option to choose Kerberos authentication.
+
    Notes
    
 You must change administrator password at least once after DC 
 install, to create the right encoding types
 
    
 W2k doesn't seem to create the _kerberos._udp and _ldap._tcp in
-their defaults DNS setup. Maybe fixed in service packs?
-
    Common Errors
    
+their defaults DNS setup. Maybe this will be fixed later in service packs.
+

    Common Errors

    In the process of adding / deleting / re-adding domain member machine accounts there are many traps for the unwary player and there are many “little” things that can go wrong. It is particularly interesting how often subscribers on the samba mailing list have concluded after repeated failed attempts to add a machine account that it is necessary to "re-install" MS Windows on t he machine. In truth, it is seldom necessary to reinstall because of this type of problem. The real solution is often very simple, and with understanding of how MS Windows -networking functions. easily overcome. -

    Can Not Add Machine Back to Domain

    -Problem: A Windows workstation was reinstalled. The original domain machine +networking functions easy to overcome. +

    Can Not Add Machine Back to Domain

    +“ A Windows workstation was reinstalled. The original domain machine 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 doesn't. Why is this failing? +exists on the network - I know it doesn't. 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 to add the machine with a new name. -

    Adding Machine to Domain Fails

    -Adding a Windows 200x or XP Professional machine to the Samba PDC Domain fails with a +

    Adding Machine to Domain Fails

    + “Adding a Windows 200x or XP Professional machine to the Samba PDC Domain fails with a message that, The machine could not be added at this time, there is a network problem. -Please try again later. Why? + Please try again later. Why?”

    -You should check that there is an add machine script in your smb.conf +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 it's operation. Increase the log level +has been defined you will need to debug it's operation. Increase the log level in the smb.conf file to level 10, then try to rejoin the domain. Check the logs to see which operation is failing.

    @@ -516,13 +520,15 @@ Possible causes include: The script does not actually exist, or could not be located in the path specified.

    Corrective Action: Fix it. Make sure that when run manually - that the script will add both the Unix system account _and_ the Samba SAM account. + 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 + 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. ie: If the Unix utility useradd is called + Corrective Action: Check that the machine name is a legal UNIX + system account name. ie: 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 upper case characters nor will it allow spaces in the name. -

    • Prev Up Next
    Chapter 6. Backup Domain Control Home Chapter 8. Stand-Alone Servers
    +

    I can't join a Windows 2003 PDC

    Windows 2003 requires SMB signing. Client side SMB signing has + only been implemented partially in Samba 3.0. Set client use spnego = no when communicating + with a windows 2003 server.

    Prev Up Next
    Chapter 6. Backup Domain Control Home Chapter 8. Stand-Alone Servers
    diff --git a/docs/htmldocs/groupmapping.html b/docs/htmldocs/groupmapping.html index 39fb34ce62..39d317e8cf 100644 --- a/docs/htmldocs/groupmapping.html +++ b/docs/htmldocs/groupmapping.html @@ -1,43 +1,48 @@ -Chapter 12. Mapping MS Windows and Unix Groups
    Chapter 12. Mapping MS Windows and Unix Groups
    Prev Part III. Advanced Configuration Next

    Chapter 12. Mapping MS Windows and Unix Groups

    Jean François Micouleau

    Gerald (Jerry) Carter

    Samba Team

    John H. Terpstra

    Samba Team

    Table of Contents

    Features and Benefits
    Discussion
    Example Configuration
    Configuration Scripts
    Sample smb.conf add group script
    Script to configure Group Mapping
    Common Errors
    Adding Groups Fails
    Adding MS Windows Groups to MS Windows Groups Fails

    +Chapter 12. Mapping MS Windows and UNIX Groups

    Chapter 12. Mapping MS Windows and UNIX Groups
    Prev Part III. Advanced Configuration Next

    Chapter 12. Mapping MS Windows and UNIX Groups

    Jean François Micouleau

    Gerald (Jerry) Carter

    Samba Team

    John H. Terpstra

    Samba Team

    Table of Contents

    Features and Benefits
    Discussion
    Example Configuration
    Configuration Scripts
    Sample smb.conf add group script
    Script to configure Group Mapping
    Common Errors
    Adding Groups Fails
    Adding MS Windows Groups to MS Windows Groups Fails
    Adding Domain Users to the Power Users group

    Starting with Samba-3, new group mapping functionality is available to create associations - between Windows group SIDs and UNIX groups. The groupmap subcommand + between Windows group SIDs and UNIX groups. The groupmap subcommand included with the net tool can be used to manage these associations.

    Warning

    The first immediate reason to use the group mapping on a Samba PDC, is that + the domain admin group has been removed and should no longer be specified in smb.conf. 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 MMC tools - so long as appropriate interface scripts have been provided to smb.conf. -

    + 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 + so long as winbind is running, Samba accounts group accounts that are created using these tools will be + allocated UNIX UIDs/GIDs from the parameters set by the idmap uid/idmap gid settings + in the smb.conf file. +

    Figure 12.1. IDMAP groups

    IDMAP groups

    Administrators should be aware that where smb.conf group interface scripts make - direct calls to the Unix/Linux system tools (eg: the shadow utilities, groupadd, - groupdel, groupmod) then the resulting Unix/Linux group names will be subject + direct calls to the UNIX/Linux system tools (eg: the shadow utilities, groupadd, + groupdel, groupmod) then the resulting UNIX/Linux group names will be subject to any limits imposed by these tools. If the tool does NOT allow upper case characters or space characters, then the creation of an MS Windows NT4 / 200x style group of - Engineering Managers will attempt to create an identically named - Unix/Linux group, an attempt that will of course fail! -

    + Engineering Managers will attempt to create an identically named + UNIX/Linux group, an attempt that will of course fail! +

    There are several possible work-arounds 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) + 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 work-around solution.

    - Another work-around is to manually create a Unix/Linux group, then manually create the + Another work-around 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 installing 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 privileges to perform essential system tasks. eg: 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 'Administrator' group, 'joe' has exactly the same rights as 'Administrator'. @@ -59,49 +64,49 @@

  • Map this domadm group to the "Domain Admins" group by running the command:

    - 

    -		root# net groupmap add ntgroup="Domain Admins" unixgroup=domadm
-

    -

    +

    +root# net groupmap add ntgroup="Domain Admins" unixgroup=domadm
+

    +

    The quotes around "Domain Admins" are necessary due to the space in the group name. Also make sure to leave no whitespace 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 making any UNIX group a Windows domain group. For example, if you wanted to include a UNIX group (e.g. acct) in a ACL on a local file or printer on a domain member machine, you would flag that group as a domain group by running the following on the Samba PDC:

    - 

    -	root# net groupmap add rid=1000 ntgroup="Accounting" unixgroup=acct
-

    +

    +root# net groupmap add rid=1000 ntgroup="Accounting" unixgroup=acct
+

    Be aware that the RID parameter is a unsigned 32 bit integer that should normally start at 1000. However, this rid must not overlap with any RID assigned - to a user. Verifying this is done differently depending on on the passdb backend + to a user. Verifying 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. -

    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
-		System Administrators (S-1-5-21-2547222302-1596225915-2414751004-1002) -> sysadmin
-		Domain Admins (S-1-5-21-2547222302-1596225915-2414751004-512) -> domadmin
-		Domain Users (S-1-5-21-2547222302-1596225915-2414751004-513) -> domuser
-		Domain Guests (S-1-5-21-2547222302-1596225915-2414751004-514) -> domguest
-

    +

    +root#  net groupmap list
+System Administrators (S-1-5-21-2547222302-1596225915-2414751004-1002) -> sysadmin
+Domain Admins (S-1-5-21-2547222302-1596225915-2414751004-512) -> domadmin
+Domain Users (S-1-5-21-2547222302-1596225915-2414751004-513) -> domuser
+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 (ie: prepared by someone else for general use). -

    Sample smb.conf add group script

    - A script to great complying group names for use by the Samba group interfaces: +

    Sample smb.conf add group script

    + A script to create complying group names for use by the Samba group interfaces:

    -

    Example 12.1. smbgrpadd.sh

    +
    Example 12.1. smbgrpadd.sh
     
 #!/bin/bash
 
@@ -120,12 +125,10 @@ exit 0
 
    
 
    
 		The smb.conf entry for the above script would look like:
-		
    -		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 Engineers, Marketoids, Gnomes: +

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

     #!/bin/bash
@@ -143,36 +146,51 @@ net groupmap modify ntgroup="Print Operators" unixgroup=lp
 net groupmap modify ntgroup="Replicators" unixgroup=daemon
 net groupmap modify ntgroup="Power Users" unixgroup=sys
 
-#groupadd Engineers
-#groupadd Marketoids
-#groupadd Gnomes
+groupadd Orks
+groupadd Elves
+groupadd Gnomes
 
-#net groupmap add ntgroup="Engineers"  unixgroup=Engineers    type=d
-#net groupmap add ntgroup="Marketoids" unixgroup=Marketoids   type=d
-#net groupmap add ntgroup="Gnomes"     unixgroup=Gnomes       type=d
+net groupmap add ntgroup="Orks"       unixgroup=Orks         type=d
+net groupmap add ntgroup="Elves"      unixgroup=Elves        type=d
+net groupmap add ntgroup="Gnomes"     unixgroup=Gnomes       type=d

    Of course it is expected that the administrator will modify this to suit local needs. For information regarding the use of the net groupmap tool please refer to the man page. -

    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 must be carefully tested manually before putting them 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 + 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 either an upper case character and/or a space character in it.

    There are three possible work-arounds. Firstly, use only group names that comply - with the limitations of the Unix/Linux groupadd system tool. + with the limitations of the UNIX/Linux groupadd system tool. The second involves use of the script mentioned earlier in this chapter, and the - third option is to manually create a Unix/Linux group account that can substitute + third 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 MS Windows Groups to MS Windows Groups Fails

    +

    Adding MS Windows Groups to MS Windows Groups Fails

    Samba-3 does NOT support nested groups from the MS Windows control environment. -

    Prev Up Next
    Chapter 11. Account Information Databases Home Chapter 13. File, Directory and Share Access Controls
    +

    Adding Domain Users to the 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 can not add the Domain Users group to the Power Users + group automatically, this must be done on each workstation by logging in as the local workstation + administrator and then using click on Start / Control Panel / Users and Passwords + now click on the 'Advanced' tab, then on the 'Advanced' Button. +

    + Now click on 'Groups', then double click on 'Power Users'. This will launch the panel to add users + or groups to the local machine 'Power Uses' group. Click on the 'Add' button, select the domain + from which the 'Domain Users' group is to be added, double click on the 'Domain Users' group, then + click on the 'Ok' button. Note: If a logon box is presented during this process please remember to + enter the connect as DOMAIN\UserName. ie: For the domain MIDEARTH and the user 'root' enter + MIDEARTH\root. +

    Prev Up Next
    Chapter 11. Account Information Databases Home Chapter 13. File, Directory and Share Access Controls
    diff --git a/docs/htmldocs/install.html b/docs/htmldocs/install.html index 154b9705e1..02264c558d 100644 --- a/docs/htmldocs/install.html +++ b/docs/htmldocs/install.html @@ -1,48 +1,39 @@ -Chapter 2. How to Install and Test SAMBA
    Chapter 2. How to Install and Test SAMBA
    Prev Part I. General Installation Next

    Chapter 2. How to Install and Test SAMBA

    Andrew Tridgell

    Samba Team

    Jelmer R. Vernooij

    The Samba Team

    John H. Terpstra

    Samba Team

    Karl Auer

    Table of Contents

    Obtaining and installing samba
    Configuring samba (smb.conf)
    Example Configuration
    SWAT
    Try listing the shares available on your - server
    Try connecting with the unix client
    Try connecting from a DOS, WfWg, Win9x, WinNT, - Win2k, OS/2, etc... client
    What If Things Don't Work?
    Common Errors
    Why are so many smbd processes eating memory?
    I'm getting "open_oplock_ipc: Failed to get local UDP socket for address 100007f. Error was Cannot assign requested" in the logs

    Obtaining and installing samba

    +Chapter 2. How to Install and Test SAMBA

    Chapter 2. How to Install and Test SAMBA
    Prev Part I. General Installation Next

    Chapter 2. How to Install and Test SAMBA

    Andrew Tridgell

    Samba Team

    Jelmer R. Vernooij

    The Samba Team

    John H. Terpstra

    Samba Team

    Karl Auer

    Table of Contents

    Obtaining and installing samba
    Configuring samba (smb.conf)
    Example Configuration
    SWAT
    Try listing the shares available on your + server
    Try connecting with the unix client
    Try connecting from another SMB client
    What If Things Don't Work?
    Common Errors
    Large number of smbd processes
    "open_oplock_ipc: Failed to get local UDP socket for address 100007f. Error was Cannot assign requested"
    "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 + UNIX distribution. There are also some packages available at the samba homepage. -

    If you need to compile samba from source, check the - appropriate appendix chapter.

    If you have already installed samba, or if your operating system +

    If you need to compile samba from source, check + the chapter about compiling samba from scratch.

    If you have already installed samba, or if your operating system was pre-installed with samba, then you may not need to bother with this chapter. On the other hand, you may want to read this chapter anyhow - for information about updating samba.

    Configuring samba (smb.conf)

    + for information about updating samba.

    Configuring samba (smb.conf)

    Samba's configuration is stored in the smb.conf file, that 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. -

    Example Configuration

    +

    Example Configuration

    There are sample configuration files in the examples subdirectory in the distribution. I suggest you read them carefully so you can see how the options go together in practice. See the man page for all the options.

    The simplest useful configuration file would be something like this:

    - 

    -	[global]
-		workgroup = MYGROUP
-
-	[homes]
-		guest ok = no
-		read only = no
-

    +

    Example 2.1. Simplest possible 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. + their login name or homes" as the service name. (Note that the workgroup that Samba must also be set.)

    - Make sure you put the smb.conf file in the same place - you specified in the Makefile (the default is to - look for it in /usr/local/samba/lib/). + Make sure you put the smb.conf file in the correct place + (usually in /etc/samba).

    For more information about security settings for the - [homes] share please refer to the chapter - Securing Samba. -

    Test your config file with testparm

    + [homes] share please refer to + "Securing Samba". +

    Test your config file with testparm

    It's important that you test the validity of your smb.conf file using the testparm program. If testparm runs OK then it will list the loaded services. If not it will give an error message. @@ -50,7 +41,7 @@ Make sure it runs OK and that the services look reasonable before proceeding.

    Always run testparm again when you change smb.conf! -

    SWAT

    +

    SWAT

    SWAT is a web-based interface that helps you configure samba. SWAT might not be available in the samba package on your platform, but in a separate package. Please read the swat manpage @@ -66,9 +57,10 @@ machine but connecting from a remote machine leaves your connection open to password sniffing as passwords will be sent in the clear over the wire. -

    Try listing the shares available on your - server

    $ smbclient -L - yourhostname

    You should get back a list of shares available on +

    Try listing the shares available on your + server

    +$ smbclient -L yourhostname
+

    You should get back a list of shares available on your server. If you don't then something is incorrectly setup. Note that this method can also be used to see what shares are available on other LanManager clients (such as WfWg).

    If you choose user level security then you may find @@ -76,68 +68,31 @@ See the smbclient man page for details. (you can force it to list the shares without a password by adding the option -U% to the command line. This will not work - with non-Samba servers)

    Try connecting with the unix client

    $ smbclient - //yourhostname/aservice

    Typically the yourhostname + with non-Samba servers)

    Try connecting with the unix client

    +

    +$ smbclient  //yourhostname/aservice
+

    Typically the yourhostname would be the name of the host where you installed smbd. The aservice is any service you have defined in the smb.conf file. Try your user name if you just have a [homes] section in smb.conf.

    For example if your unix host is bambi - and your login name is fred you would type:

    $ smbclient //bambi/fred -

    Try connecting from a DOS, WfWg, Win9x, WinNT, - Win2k, OS/2, etc... client

    Try mounting disks. eg:

    C:\WINDOWS\> net use d: \\servername\service -

    Try printing. eg:

    C:\WINDOWS\> net use lpt1: - \\servername\spoolservice

    C:\WINDOWS\> print filename -

    What If Things Don't Work?

    Then you might read the file chapter - Diagnosis and the - FAQ. If you are still stuck then try to follow - the Analysing and Solving Problems chapter - Samba has been successfully installed at thousands of sites worldwide, - so maybe someone else has hit your problem and has overcome it.

    Common Errors

    -The following questions and issues get raised on the samba mailing list over and over again. -

    Why are so many smbd processes eating memory?

    -“ -Site that is running Samba on an AIX box. They are sharing out about 2 terabytes using samba. -Samba was installed using smitty and the binaries. We seem to be experiencing a memory problem -with this box. When I do a svmon -Pu the monitoring program shows that smbd has several -processes of smbd running: -” -

    - “ -Is samba suppose to start this many different smbd processes? Or does it run as one smbd process? Also -is it normal for it to be taking up this much memory? -” -

    + and your login name is fred you would type:

    +$ smbclient //bambi/fred
+

    Try connecting from another SMB client

    Try mounting disks. from a DOS, Windows or OS/2 client, eg:

    +C:\> net use d: \\servername\service
+

    Try printing. eg:

    -Inuse * 4096 = amount of memory being used by this process
-
-     Pid Command        Inuse      Pin     Pgsp  Virtual   64-bit    Mthrd
-   20950 smbd           33098     1906      181     5017        N        N
-   22262 smbd            9104     1906      5410
-   21060 smbd            9048     1906      181     5479        N        N
-   25972 smbd            8678     1906      181     5109        N        N
-   24524 smbd            8674     1906      181     5105        N        N
-   19262 smbd            8582     1906      181     5013        N        N
-   20722 smbd            8572     1906      181     5003        N        N
-   21454 smbd            8572     1906      181     5003        N        N
-   28946 smbd            8567     1906      181     4996        N        N
-   24076 smbd            8566     1906      181     4996        N        N
-   20138 smbd            8566     1906      181     4996        N        N
-   17608 smbd            8565     1906      181     4996        N        N
-   21820 smbd            8565     1906      181     4996        N        N
-   26940 smbd            8565     1906      181     4996        N        N
-   19884 smbd            8565     1906      181     4996        N        N
-    9912 smbd            8565     1906      181     4996        N        N
-   25800 smbd            8564     1906      181     4995        N        N
-   20452 smbd            8564     1906      181     4995        N        N
-   18592 smbd            8562     1906      181     4993        N        N
-   28216 smbd            8521     1906      181     4954        N        N
-   19110 smbd            8404     1906      181     4862        N        N
-
-   Total memory used:  841,592,832 bytes
+C:\> net use lpt1:	\\servername\spoolservice

    -

    +

    C:\> print filename
+

    What If Things Don't Work?

    Then you might read the file chapter diagnosis + and the FAQ. If you are still stuck then refer to "Analysing and solving problems". + Samba has been successfully installed at thousands of sites worldwide, + so maybe someone else has hit your problem and has overcome it.

    Common Errors

    +The following questions and issues get raised on the samba mailing list over and over again. +

    Large number of smbd processes

    Samba consists on three core programs: nmbd, smbd, winbindd. nmbd is the name server message daemon, smbd is the server message daemon, winbindd is the daemon that @@ -152,4 +107,9 @@ connection made. That is why you are seeing so many of them, one (1) per client

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

    I'm getting "open_oplock_ipc: Failed to get local UDP socket for address 100007f. Error was Cannot assign requested" in the logs

    Your loopback device isn't working correctly. Make sure it's running.

    Prev Up Next
    Chapter 1. Introduction to Samba Home Chapter 3. Fast Start for the Impatient
    +

    "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's configured properly. 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"

    + This error can be caused by one of these misconfigurations: +

    • You specified an nonexisting path for the share in smb.conf

    • The user you are trying to access the share with does not + have sufficient permissions to access the path for the share. Both read (r) and access (x) should be possible.

    • The share you are trying to access does not exist.

    Prev Up Next
    Chapter 1. Introduction to Samba Home Chapter 3. Fast Start for the Impatient
    diff --git a/docs/htmldocs/integrate-ms-networks.html b/docs/htmldocs/integrate-ms-networks.html index 083aeed9f3..73971d2a72 100644 --- a/docs/htmldocs/integrate-ms-networks.html +++ b/docs/htmldocs/integrate-ms-networks.html @@ -1,4 +1,4 @@ -Chapter 26. Integrating MS Windows networks with Samba
    Chapter 26. Integrating MS Windows networks with Samba
    Prev Part III. Advanced Configuration Next

    Chapter 26. 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
    My Boomerang Won't Come Back
    Very Slow Network Connections
    Samba server name change problem

    +Chapter 26. Integrating MS Windows networks with Samba

    Chapter 26. Integrating MS Windows networks with Samba
    Prev Part III. Advanced Configuration Next

    Chapter 26. 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 in one way
    Very Slow Network Connections
    Samba server name change problem

    This section 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 use of @@ -9,15 +9,15 @@ NetBIOS over TCP/IP then this section may help you to resolve networking problem 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 mis-apprehension. -

    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 +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 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 it's 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 @@ -30,17 +30,19 @@ Name Service or WINS), TCP port 139 AND TCP port 445 (for actual file and print

    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). + Use of DHCP with ADS is recommended as a further means of maintaining central control over 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

    -Contains a static list of IP Addresses and names. +

    • /etc/hosts

    • /etc/resolv.conf

    • /etc/host.conf

    • /etc/nsswitch.conf

    /etc/hosts

    +Contains a static list of IP addresses and names. eg: -

    -	127.0.0.1	localhost localhost.localdomain
-	192.168.1.1	bigbox.caldera.com	bigbox	alias4box
+
    +127.0.0.1	localhost localhost.localdomain
+192.168.1.1	bigbox.caldera.com	bigbox	alias4box
 
    
 The purpose of /etc/hosts is to provide a 
 name resolution mechanism so that uses do not need to remember 
@@ -48,10 +50,10 @@ 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 
+Access Control address, or MAC address. IP addresses are currently 
 32 bits in length and are typically presented as four (4) decimal 
 numbers that are separated by a dot (or period). eg: 168.192.1.1.
-
    
+
    
 MAC Addresses use 48 bits (or 6 bytes) and are typically represented 
 as two digit hexadecimal numbers separated by colons. eg: 
 40:8e:0a:12:34:56
@@ -84,15 +86,15 @@ MAC addresses only; their own unique address and the 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 
+UNIX/Linux TCP/IP installations and as a minimum will contain 
 the localhost and local network interface IP addresses and the 
 primary names by which they are known within the local machine. 
 This file helps to prime the pump so that 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 @@ -102,41 +104,41 @@ 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 affected. It is a critical configuration file. This file controls the order by which name resolution may proceed. The typical structure is: -

    -	order hosts,bind
-	multi on
+
    +order hosts,bind
+multi on
 
    
 then 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: -

    -	# /etc/nsswitch.conf
-	#
-	# Name Service Switch configuration file.
-	#
+
    +# /etc/nsswitch.conf
+#
+# Name Service Switch configuration file.
+#
 
-	passwd:		compat
-	# Alternative entries for password authentication are:
-	# passwd:	compat files nis ldap winbind
-	shadow:		compat
-	group:		compat
+passwd:		compat
+# Alternative entries for password authentication are:
+# passwd:	compat files nis ldap winbind
+shadow:		compat
+group:		compat
 
-	hosts:		files nis dns
-	# Alternative entries for host name resolution are:
-	# hosts:	files dns nis nis+ hesiod db compat ldap wins
-	networks:	nis files dns
+hosts:		files nis dns
+# Alternative entries for host name resolution are:
+# hosts:	files dns nis nis+ hesiod db compat ldap wins
+networks:	nis files dns
 
-	ethers:		nis files
-	protocols:	nis files
-	rpc:		nis files
-	services:	nis files
+ethers:		nis files
+protocols:	nis files
+rpc:		nis files
+services:	nis files
 
    
 Of course, each of these mechanisms requires that the appropriate 
 facilities and/or services are correctly configured.
@@ -144,27 +146,27 @@ facilities and/or services are correctly configured.
 It should be noted that unless a network request/message must be 
 sent, TCP/IP networks are silent. All TCP/IP communications assumes 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 that linux clients will 
 be able to obtain resolution of MS Windows NetBIOS names to IP 
 Addresses. To gain this functionality Samba needs to be compiled 
-with appropriate arguments to the make command (ie: make 
+with appropriate arguments to the make command (i.e.: make 
 nsswitch/libnss_wins.so). The resulting library should 
 then be installed in the /lib directory and 
 the "wins" parameter needs to be added to the "hosts:" line in 
 the /etc/nsswitch.conf file. At this point it 
-will be possible to ping any MS Windows machine by it's NetBIOS 
+will be possible to ping any MS Windows machine by its NetBIOS 
 machine name, so 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 about the name each machine is given. This name is known variously (and inconsistently) as the "computer name", "machine name", "networking name", "netbios name", -"SMB name". All terms mean the same thing with the exception of +or "SMB name". All terms mean the same thing with the exception of "netbios name" which can apply also to the name of the workgroup or the domain name. The terms "workgroup" and "domain" are really just a -simply name with which the machine is associated. All NetBIOS names +simple name with which the machine is associated. All NetBIOS names are exactly 16 characters in length. The 16th character is reserved. It is used to store a one byte value that indicates service level information for the NetBIOS name that is registered. A NetBIOS machine @@ -172,25 +174,14 @@ name is therefore registered for each service type that is provided by the client/server.

    The following are typical NetBIOS name/service type registrations: -

    -	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
-
-	Group Names:
-		WORKGROUP<03> = Generic Name registered by all members of WORKGROUP
-		WORKGROUP<1c> = Domain Controllers / Netlogon Servers
-		WORKGROUP<1d> = Local Master Browsers
-		WORKGROUP<1e> = Internet Name Resolvers
-

    +

    Table 26.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 26.2. Group Names

    WORKGROUP<03>Generic Name registered by all members of WORKGROUP
    WORKGROUP<1c>Domain Controllers / Netlogon Servers
    WORKGROUP<1d>Local Master Browsers
    WORKGROUP<1e>Internet Name Resolvers

    + It should be noted that all NetBIOS machines register their own names as per the above. This is in vast contrast to TCP/IP installations where traditionally the system administrator will determine 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 type information that MS Windows clients depend on to locate the type of service that may @@ -199,8 +190,8 @@ wants to locate a domain logon server. It finds this service and the IP address of a server that provides it by performing a lookup (via a NetBIOS broadcast) for enumeration of all machines that have 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. Which -ever machine first replies then ends up providing the logon services. +IP address that is returned in the enumerated list of IP addresses. +Whichever machine first replies 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 @@ -228,7 +219,7 @@ 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 that machine has communicated with over the @@ -242,11 +233,11 @@ an attempt to exchange a message with that machine will be subject to time-out delays. i.e.: Its name is in the cache, so a name resolution lookup will succeed, but the machine can not respond. This can be frustrating for users - but it is a characteristic of the protocol. -

    +

    The MS Windows utility that allows examination of the NetBIOS name cache is called "nbtstat". The Samba equivalent of this is called nmblookup. -

    The LMHOSTS file

    +

    The LMHOSTS file

    This file is usually located in MS Windows NT 4.0 or 2000 in C:\WINNT\SYSTEM32\DRIVERS\ETC and contains the IP Address and the machine name in matched pairs. The @@ -254,102 +245,103 @@ the IP Address and the machine name in matched pairs. The to IP address mapping.

    It typically looks like: -

    -	# Copyright (c) 1998 Microsoft Corp.
-	#
-	# This is a sample LMHOSTS file used by the Microsoft Wins Client (NetBIOS
-	# over TCP/IP) stack for Windows98
-	#
-	# This file contains the mappings of IP addresses to NT computernames
-	# (NetBIOS) names.  Each entry should be kept on an individual line.
-	# The IP address should be placed in the first column followed by the
-	# corresponding computername. The address and the computername
-	# should be separated by at least one space or tab. The "#" character
-	# is generally used to denote the start of a comment (see the exceptions
-	# below).
-	#
-	# This file is compatible with Microsoft LAN Manager 2.x TCP/IP lmhosts
-	# files and offers the following extensions:
-	#
-	#      #PRE
-	#      #DOM:<domain>
-	#      #INCLUDE <filename>
-	#      #BEGIN_ALTERNATE
-	#      #END_ALTERNATE
-	#      \0xnn (non-printing character support)
-	#
-	# Following any entry in the file with the characters "#PRE" will cause
-	# the entry to be preloaded into the name cache. By default, entries are
-	# not preloaded, but are parsed only after dynamic name resolution fails.
-	#
-	# Following an entry with the "#DOM:<domain>" tag will associate the
-	# entry with the domain specified by <domain>. This affects how the
-	# browser and logon services behave in TCP/IP environments. To preload
-	# the host name associated with #DOM entry, it is necessary to also add a
-	# #PRE to the line. The <domain> is always preloaded although it will not
-	# be shown when the name cache is viewed.
-	#
-	# Specifying "#INCLUDE <filename>" will force the RFC NetBIOS (NBT)
-	# software to seek the specified <filename> and parse it as if it were
-	# local. <filename> is generally a UNC-based name, allowing a
-	# centralized lmhosts file to be maintained on a server.
-	# It is ALWAYS necessary to provide a mapping for the IP address of the
-	# server prior to the #INCLUDE. This mapping must use the #PRE directive.
-	# In addition the share "public" in the example below must be in the
-	# LanManServer list of "NullSessionShares" in order for client machines to
-	# be able to read the lmhosts file successfully. This key is under
-	# \machine\system\currentcontrolset\services\lanmanserver\parameters\nullsessionshares
-	# in the registry. Simply add "public" to the list found there.
-	#
-	# The #BEGIN_ and #END_ALTERNATE keywords allow multiple #INCLUDE
-	# statements to be grouped together. Any single successful include
-	# will cause the group to succeed.
-	#
-	# Finally, non-printing characters can be embedded in mappings by
-	# first surrounding the NetBIOS name in quotations, then using the
-	# \0xnn notation to specify a hex value for a non-printing character.
-	#
-	# The following example illustrates all of these extensions:
-	#
-	# 102.54.94.97     rhino         #PRE #DOM:networking  #net group's DC
-	# 102.54.94.102    "appname  \0x14"                    #special app server
-	# 102.54.94.123    popular            #PRE             #source server
-	# 102.54.94.117    localsrv           #PRE             #needed for the include
-	#
-	# #BEGIN_ALTERNATE
-	# #INCLUDE \\localsrv\public\lmhosts
-	# #INCLUDE \\rhino\public\lmhosts
-	# #END_ALTERNATE
-	#
-	# In the above example, the "appname" server contains a special
-	# character in its name, the "popular" and "localsrv" server names are
-	# preloaded, and the "rhino" server name is specified so it can be used
-	# to later #INCLUDE a centrally maintained lmhosts file if the "localsrv"
-	# system is unavailable.
-	#
-	# Note that the whole file is parsed including comments on each lookup,
-	# 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

    +

    +# Copyright (c) 1998 Microsoft Corp.
+#
+# This is a sample LMHOSTS file used by the Microsoft Wins Client (NetBIOS
+# over TCP/IP) stack for Windows98
+#
+# This file contains the mappings of IP addresses to NT computernames
+# (NetBIOS) names.  Each entry should be kept on an individual line.
+# The IP address should be placed in the first column followed by the
+# corresponding computername. The address and the computername
+# should be separated by at least one space or tab. The "#" character
+# is generally used to denote the start of a comment (see the exceptions
+# below).
+#
+# This file is compatible with Microsoft LAN Manager 2.x TCP/IP lmhosts
+# files and offers the following extensions:
+#
+#      #PRE
+#      #DOM:<domain>
+#      #INCLUDE <filename>
+#      #BEGIN_ALTERNATE
+#      #END_ALTERNATE
+#      \0xnn (non-printing character support)
+#
+# Following any entry in the file with the characters "#PRE" will cause
+# the entry to be preloaded into the name cache. By default, entries are
+# not preloaded, but are parsed only after dynamic name resolution fails.
+#
+# Following an entry with the "#DOM:<domain>" tag will associate the
+# entry with the domain specified by <domain>. This affects how the
+# browser and logon services behave in TCP/IP environments. To preload
+# the host name associated with #DOM entry, it is necessary to also add a
+# #PRE to the line. The <domain> is always preloaded although it will not
+# be shown when the name cache is viewed.
+#
+# Specifying "#INCLUDE <filename>" will force the RFC NetBIOS (NBT)
+# software to seek the specified <filename> and parse it as if it were
+# local. <filename> is generally a UNC-based name, allowing a
+# centralized lmhosts file to be maintained on a server.
+# It is ALWAYS necessary to provide a mapping for the IP address of the
+# server prior to the #INCLUDE. This mapping must use the #PRE directive.
+# In addition the share "public" in the example below must be in the
+# LanManServer list of "NullSessionShares" in order for client machines to
+# be able to read the lmhosts file successfully. This key is under
+# \machine\system\currentcontrolset\services\lanmanserver\
+# parameters\nullsessionshares
+# in the registry. Simply add "public" to the list found there.
+#
+# The #BEGIN_ and #END_ALTERNATE keywords allow multiple #INCLUDE
+# statements to be grouped together. Any single successful include
+# will cause the group to succeed.
+#
+# Finally, non-printing characters can be embedded in mappings by
+# first surrounding the NetBIOS name in quotations, then using the
+# \0xnn notation to specify a hex value for a non-printing character.
+#
+# The following example illustrates all of these extensions:
+#
+# 102.54.94.97     rhino         #PRE #DOM:networking  #net group's DC
+# 102.54.94.102    "appname  \0x14"                    #special app server
+# 102.54.94.123    popular            #PRE             #source server
+# 102.54.94.117    localsrv           #PRE             #needed for the include
+#
+# #BEGIN_ALTERNATE
+# #INCLUDE \\localsrv\public\lmhosts
+# #INCLUDE \\rhino\public\lmhosts
+# #END_ALTERNATE
+#
+# In the above example, the "appname" server contains a special
+# character in its name, the "popular" and "localsrv" server names are
+# preloaded, and the "rhino" server name is specified so it can be used
+# to later #INCLUDE a centrally maintained lmhosts file if the "localsrv"
+# system is unavailable.
+#
+# Note that the whole file is parsed including comments on each lookup,
+# 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

    This file is usually located in MS Windows NT 4.0 or 2000 in C:\WINNT\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

    +every way the equivalent of the UNIX/Linux /etc/hosts file. +

    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 dependant on what the NetBIOS -Node Type parameter is configured to. A Node Type of 0 means use -NetBIOS broadcast (over UDP broadcast) is first used if the name +configuration facility. If enabled, an elaborate name resolution sequence +is followed the precise nature of which is dependant on how the NetBIOS +Node Type parameter is configured. A Node Type of 0 means that +NetBIOS broadcast (over UDP broadcast) is used if the name that is the subject of a name lookup is not found in the NetBIOS name 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 @@ -357,24 +349,20 @@ 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. -

    Common Errors

    +

    For information about setting up Samba as a WINS server, read + the chapter on network browsing.

    Common Errors

    TCP/IP network configuration problems find every network administrator sooner or later. The cause can be anything from keyboard mishaps, forgetfulness, simple mistakes, and carelessness. Of course, no one is every deliberately careless! -

    My Boomerang Won't Come Back

    - Well, the real complaint said, "I can ping my samba server from Windows, but I can - not ping my Windows machine from the samba server." +

    Pinging works only in one way

    + “I can ping my samba server from Windows, but I can + not ping my Windows machine from the samba server.”

    The Windows machine was at IP Address 192.168.1.2 with netmask 255.255.255.0, the Samba server (Linux) was at IP Address 192.168.1.130 with netmask 255.255.255.128. @@ -382,46 +370,46 @@ carelessness. Of course, no one is every 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 causes of slow network response includes: -

    • Client is configured to use DNS and DNS server is down

    • Client is configured to use remote DNS server, but 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 our DNS or WINS traffic

    Samba server name change problem

    - The name of the samba server was changed, samba was restarted, samba server can not be +

    • Client is configured to use DNS and DNS server is down

    • Client is configured to use remote DNS server, but 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 our DNS or WINS traffic

    Samba server name change problem

    + “The name of the samba server was changed, samba was restarted, samba server can not be pinged by new name from MS Windows NT4 Workstation, but it does still respond to ping using - the old name. Why? + the old name. Why?”

    From this description three (3) things are rather obvious:

    • WINS is NOT in use, only broadcast based name resolution is used

    • The samba server was renamed and restarted within the last 10-15 minutes

    • The old samba server name is still in the NetBIOS name cache on the MS Windows NT4 Workstation

    To find what names are present in the NetBIOS name cache on the MS Windows NT4 machine, open a cmd shell, then:

    - 

    -	C:\temp\>nbtstat -n
+
    +C:\> nbtstat -n
 
-	              NetBIOS Local Name Table
+              NetBIOS Local Name Table
 
-	   Name                 Type          Status
-	------------------------------------------------
-	SLACK            <03>  UNIQUE      Registered
-	ADMINISTRATOR    <03>  UNIQUE      Registered
-	SLACK            <00>  UNIQUE      Registered
-	SARDON           <00>  GROUP       Registered
-	SLACK            <20>  UNIQUE      Registered
-	SLACK            <1F>  UNIQUE      Registered
+   Name                 Type          Status
+------------------------------------------------
+FRODO            <03>  UNIQUE      Registered
+ADMINSTRATOR     <03>  UNIQUE      Registered
+FRODO            <00>  UNIQUE      Registered
+SARDON           <00>  GROUP       Registered
+FRODO            <20>  UNIQUE      Registered
+FRODO            <1F>  UNIQUE      Registered
 
 
-	C:\Temp\>nbtstat -c
+C:\> nbtstat -c
 
-	             NetBIOS Remote Cache Name Table
+             NetBIOS Remote Cache Name Table
 
-	   Name                 Type       Host Address     Life [sec]
-	--------------------------------------------------------------
-	FRODO            <20>  UNIQUE      192.168.1.1          240
+   Name                 Type       Host Address     Life [sec]
+--------------------------------------------------------------
+GANDALF	<20>  UNIQUE      192.168.1.1          240
 
-	C:\Temp\>
-	
    
+C:\> 
+

    - In the above example, FRODO is the Samba server and SLACK is the MS Windows NT4 Workstation. - The first listing shows the contents of the Local Name Table (ie: Identity information on + In the above example, GANDALF is the Samba server and FRODO is the MS Windows NT4 Workstation. + The first listing shows the contents of the Local Name Table (i.e.: Identity information on the MS Windows workstation), the second shows the NetBIOS name in the NetBIOS name cache. The name cache contains the remote machines known to this workstation. -

    Prev Up Next
    Chapter 25. PAM based Distributed Authentication Home Chapter 27. Unicode/Charsets
    +

    Prev Up Next
    Chapter 25. PAM based Distributed Authentication Home Chapter 27. Unicode/Charsets
    diff --git a/docs/htmldocs/introduction.html b/docs/htmldocs/introduction.html index 94419cff04..10cb806270 100644 --- a/docs/htmldocs/introduction.html +++ b/docs/htmldocs/introduction.html @@ -1,5 +1,4 @@ -Part I. General Installation
    Part I. General Installation
    Prev   Next

    General Installation

    Preparing Samba for Configuration

    This section of the Samba-HOWTO-Collection contains general info on how to install samba +Part I. General Installation

    Part I. General Installation
    Prev   Next

    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. Introduction to Samba
    Background
    Terminology
    Related Projects
    SMB Methodology
    Epilogue
    Miscellaneous
    2. How to Install and Test SAMBA
    Obtaining and installing samba
    Configuring samba (smb.conf)
    Example Configuration
    SWAT
    Try listing the shares available on your - server
    Try connecting with the unix client
    Try connecting from a DOS, WfWg, Win9x, WinNT, - Win2k, OS/2, etc... client
    What If Things Don't Work?
    Common Errors
    Why are so many smbd processes eating memory?
    I'm getting "open_oplock_ipc: Failed to get local UDP socket for address 100007f. Error was Cannot assign requested" in the logs
    3. Fast Start for the Impatient
    Note
    Prev Up Next
    SAMBA Project Documentation Home Chapter 1. Introduction to Samba
    +PLEASE read this.

    Table of Contents

    1. Introduction to Samba
    Background
    Terminology
    Related Projects
    SMB Methodology
    Epilogue
    Miscellaneous
    2. How to Install and Test SAMBA
    Obtaining and installing samba
    Configuring samba (smb.conf)
    Example Configuration
    SWAT
    Try listing the shares available on your + server
    Try connecting with the unix client
    Try connecting from another SMB client
    What If Things Don't Work?
    Common Errors
    Large number of smbd processes
    "open_oplock_ipc: Failed to get local UDP socket for address 100007f. Error was Cannot assign requested"
    "The network name cannot be found"
    3. Fast Start for the Impatient
    Note
    Prev Up Next
    Attributions Home Chapter 1. Introduction to Samba
    diff --git a/docs/htmldocs/ix01.html b/docs/htmldocs/ix01.html index 4f706aed70..6e09e98de4 100644 --- a/docs/htmldocs/ix01.html +++ b/docs/htmldocs/ix01.html @@ -1 +1,39 @@ -Index
    Index
    Prev   

    Index

    Prev Up 
    Chapter 41. Further Resources Home 
    +Index
    Index
    Prev   

    Index

    Symbols

    "Domain Admins" group, Discussion
    "Domain Users" group, Adding Domain Users to the Power Users group
    "Printers" folder, Caveats to be considered, Installing the PostScript Driver on a Client, Manual Driver Installation in 15 Steps
    "raw" printing, CUPS/Samba as a "spooling-only" Print Server; "raw" printing +with Vendor Drivers on Windows Clients
    /etc/host.conf, /etc/host.conf
    /etc/hosts, /etc/hosts
    /etc/nsswitch.conf, /etc/nsswitch.conf
    8.3
    file names, MS Windows NTFS Comparison with UNIX File Systems

    A

    ACLs, File, Directory and Share Access Controls
    Active Directory, Samba ADS Domain Membership
    add group script, Adding Groups Fails
    add machine script, The machine trust account not accessible, Adding Machine to Domain Fails
    add printer command, Adding new Printers with the Windows NT APW
    add printer wizard, Three familiar Methods for driver upload plus a new one
    add user script, Mapping User Identifiers between MS Windows and UNIX
    addprinter command, Parameters Recommended for Use
    admin users, User and Group Based Controls, I have set force user but Samba still makes root the owner of all the files I touch!
    Administrator, Discussion
    ADS (see Active Directory)
    ads server, Setup your smb.conf
    application/cups.vnd-postscript, Benefits of using "CUPS PostScript Driver for +Windows NT/2k/XP" instead of 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
    application/postscript, Benefits of using "CUPS PostScript Driver for +Windows NT/2k/XP" instead of Adobe Driver
    application/vnd.cups-raster, PostScript Printer Descriptions (PPDs) for non-PS Printers
    application/vnd.cups-raw, Explicitly enable "raw" printing for +application/octet-stream!
    auth methods, auth methods does not work, Passdb Backends and Authentication

    B

    bind interfaces only, The tests
    brlock.tdb, The printing *.tdb Files
    (see also TDB)
    browse list, What is Browsing?, Technical Overview of browsing
    browseable, The [printers] Section, Any [my_printer_name] Section, Parameters in the [print$] Section

    C

    case sensitive, Miscellaneous Controls, Windows 9x / Me Profile Setup
    chpass, Manual Creation of Machine Trust Accounts
    client use spnego, I can't join a Windows 2003 PDC
    comment, The [printers] Section, Any [my_printer_name] Section, Parameters in the [print$] Section
    configure, Building the Binaries
    connections.tdb, The printing *.tdb Files
    (see also TDB)
    core files, Internal errors
    create mask, File and Directory Permissions Based Controls, Interaction with the standard Samba create mask + parameters
    csc policy, Miscellaneous Controls
    CUPS
    Page Accounting, Page Accounting with CUPS
    quotas, Setting up Quotas
    CUPS-PPD, cupsomatic, pdqomatic, lpdomatic, directomatic
    cupsaddsmb, Three familiar Methods for driver upload plus a new one, 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
    cupsomatic, CUPS can use all Windows-formatted Vendor PPDs, The CUPS Filtering Architecture, cupsomatic/Foomatic -- how do they fit into the Picture?, Difference between cupsomatic/foomatic-rip and +native CUPS printing, cupsomatic, pdqomatic, lpdomatic, directomatic
    CVS, Access Samba source code via CVS
    web, Access via CVSweb

    D

    daemon, Alternative: starting it as a daemon
    DDK, PostScript Drivers with no major problems -- even in Kernel +Mode, CUPS Package of "PostScript Driver for WinNT/2k/XP"
    debug, Internal errors
    debug level, Debugging with Samba itself, Log level
    debuglevel, Debug levels
    default case, Miscellaneous Controls
    delete printer command, Adding new Printers with the Windows NT APW
    deleteprinter command, Parameters Recommended for Use
    DHCP, Background Information
    diff, Patches
    directory mask, File and Directory Permissions Based Controls
    directory security mask, Interaction with the standard Samba create mask + parameters
    disable spoolss, Parameters Recommended for Use
    display charset, Samba and charsets
    DNS, TCP/IP - without NetBIOS, DNS Lookup
    Active Directory, DNS and Active Directory
    Dynamic, Background Information
    dns proxy, What is Browsing?
    domain admin group, Mapping MS Windows and UNIX Groups
    domain logons, Preparing for Domain Control
    domain master, Domain Network Logon Service, Example Configuration, What is Browsing?, Making Samba the domain master
    dont descend, Miscellaneous Controls
    dos charset, Samba and charsets, Japanese charsets, CP850.so can't be found
    dos filemode, File and Directory Permissions Based Controls
    dos filetime resolution, Miscellaneous Controls
    dos filetimes, Miscellaneous Controls

    E

    EMF, Windows Drivers, GDI and EMF, From Windows Clients to an NT Print Server, Driver Execution on the Server
    encrypt passwords, Joining an NT4 type Domain with Samba-3, smbpasswd - Encrypted Password Database, smb.conf PAM Configuration, The tests
    enhanced browsing, What is Browsing?
    enumports command, Parameters Recommended for Use, Samba and Printer Ports
    EPM (see ESP meta packager)
    ESC/P, Driver Execution on the Server
    ESP
    Ghostscript, The CUPS Filtering Architecture, Difference between cupsomatic/foomatic-rip and +native CUPS printing
    meta packager, CUPS Package of "PostScript Driver for WinNT/2k/XP"
    Print Pro, Sources of CUPS drivers / PPDs, ESP Print Pro Package of "PostScript Driver for +WinNT/2k/XP"
    Extended Attributes, File, Directory and Share Access Controls

    F

    fake oplocks, Miscellaneous Controls
    File System, File System Access Controls
    foomatic, CUPS can use all Windows-formatted Vendor PPDs, The CUPS Filtering Architecture, cupsomatic/Foomatic -- how do they fit into the Picture?, Difference between cupsomatic/foomatic-rip and +native CUPS printing, foomatic-rip and Foomatic explained, Foomatic's strange Name
    foomatic-rip, Difference between cupsomatic/foomatic-rip and +native CUPS printing, CUPS Print Drivers from Linuxprinting.org, foomatic-rip and Foomatic explained, The Grand Unification +achieved...
    force create mode, File and Directory Permissions Based Controls, Interaction with the standard Samba create mask + parameters
    force directory mode, File and Directory Permissions Based Controls, Interaction with the standard Samba create mask + parameters
    force directory security mode, File and Directory Permissions Based Controls, Interaction with the standard Samba create mask + parameters
    force group, User and Group Based Controls
    force security mode, File and Directory Permissions Based Controls, Interaction with the standard Samba create mask + parameters
    force user, User and Group Based Controls, I have set force user but Samba still makes root the owner of all the files I touch!, Beware of Force User
    ftp, Accessing the samba sources via rsync and ftp

    G

    gdb, Internal errors
    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
    GhostScript, PostScript and Ghostscript, Ghostscript -- the Software RIP for non-PostScript Printers
    (see also PostScript)
    Ghostscript
    ESP (see ESP GhostScript)
    GID, Features and Benefits
    GPG, Verifying Samba's PGP signature
    groupadd, Features and Benefits
    groupdel, Features and Benefits
    groups
    domain, Discussion
    mapping, Mapping MS Windows and UNIX Groups
    nested, Adding MS Windows Groups to MS Windows Groups Fails
    guest account, Problem resolution, My client reports "This server is not configured to list shared resources", The [printers] Section
    guest ok, User and Group Based Controls, The [printers] Section, Any [my_printer_name] Section, Parameters in the [print$] Section

    H

    hide dot files, Miscellaneous Controls
    hide files, Miscellaneous Controls
    hide unreadable, File and Directory Permissions Based Controls
    hide unwriteable files, File and Directory Permissions Based Controls
    host msdfs, Features and Benefits
    hosts allow, Using host based protection, Parameters Recommended for Use, Any [my_printer_name] Section
    hosts deny, Using host based protection, Parameters Recommended for Use, Any [my_printer_name] Section

    I

    idmap gid, Features and Benefits, Winbind is not resolving users and groups
    idmap uid, Features and Benefits, Winbind is not resolving users and groups
    ifconfig, Starting from inetd.conf
    imprints, Three familiar Methods for driver upload plus a new one
    inetd, The tests, Starting the smbd and nmbd, Starting from inetd.conf
    Interdomain Trusts, Interdomain Trust Relationships
    completing, Completing an NT4 Domain Trust
    creating, Native MS Windows NT4 Trusts Configuration
    Facilities, Inter-Domain Trust Facilities
    interfaces, Multiple interfaces, The tests, Starting from inetd.conf
    invalid users, User and Group Based Controls
    IPP, Understanding cupsaddsmb

    K

    KDC, Samba ADS Domain Membership
    Kerberos, Samba ADS Domain Membership
    kinit, Setup your /etc/krb5.conf

    L

    ldap admin dn, Configuring Samba
    ldap delete dn, Configuring Samba
    ldap filter, Configuring Samba
    ldap machine suffix, Configuring Samba
    ldap passwd sync, Configuring Samba, Password synchronisation
    ldap ssl, Configuring Samba, Security and sambaSamAccount
    ldap suffix, Configuring Samba
    ldap trust ids, Configuring Samba
    ldap user suffix, Configuring Samba
    libnss_wins.so, /etc/nsswitch.conf
    Links
    hard, MS Windows NTFS Comparison with UNIX File Systems
    soft, MS Windows NTFS Comparison with UNIX File Systems
    Linuxprinting.org, CUPS Print Drivers from Linuxprinting.org
    lm announce, What is Browsing?
    lm interval, What is Browsing?
    LMB (see Local Master Browser)
    LMHOSTS, The LMHOSTS file
    load printers, Parameters Recommended for Use, A little Experiment to warn you, The [global] Section
    local master, What is Browsing?, Setting up WORKGROUP Browsing
    Local Master Browser, Use of the Remote Announce parameter
    locking, Discussion
    locking.tdb, The printing *.tdb Files
    (see also TDB)
    log files
    monitoring, Assumptions
    log level, Adding Machine to Domain Fails, extd_audit, Debug levels
    logon drive, Windows NT4 Workstation
    logon home, LDAP special attributes for sambaSamAccounts, Windows 9x / Me User Profiles, Mixed Windows 9x / Me and Windows NT4/200x User Profiles, Windows NT4 Workstation, Sharing Profiles between W9x/Me and NT4/200x/XP workstations
    logon path, LDAP special attributes for sambaSamAccounts, Mixed Windows 9x / Me and Windows NT4/200x User Profiles, Windows 9x / Me Profile Setup, Windows NT4 Workstation, Sharing Profiles between W9x/Me and NT4/200x/XP workstations
    logon script, LDAP special attributes for sambaSamAccounts
    lpadmin, CUPS Print Drivers from Linuxprinting.org, Setting up Quotas
    lppause command, Parameters Recommended for Use, Linking of smbd with libcups.so, From Windows Clients to a CUPS/Samba Print Server, Pre-conditions
    lpq cache time, Parameters Recommended for Use, The [global] Section
    lpq command, Parameters Recommended for Use, Linking of smbd with libcups.so, Pre-conditions
    lpresume command, Parameters Recommended for Use, Linking of smbd with libcups.so, Pre-conditions
    lprm command, Parameters Recommended for Use, Linking of smbd with libcups.so, Pre-conditions
    lpstat, Troubleshooting revisited

    M

    MAC Addresses, /etc/hosts
    machine trust accounts, MS Windows Workstation/Server Machine Trust Accounts
    creating, MS Windows Workstation/Server Machine Trust Accounts
    make, Building the Binaries
    mangling method, Japanese charsets
    map to guest, Parameters in the [print$] Section, Adding new Printers with the Windows NT APW, Can't reconnect to Samba under new account + from Win2K/XP, Avoid being connected to the Samba server as the + "wrong" user
    max print jobs, Parameters Recommended for Use
    max xmit, Max xmit
    messages.tdb, The printing *.tdb Files
    (see also TDB)
    MIME, MIME types and CUPS Filters, MIME type Conversion Rules, Filter Requirements, "application/octet-stream" printing
    min print space, Parameters Recommended for Use
    msdfs root, Features and Benefits

    N

    name resolve order, What is Browsing?
    nbtstat, The NetBIOS Name Cache
    NetBIOS, Features and Benefits, TCP/IP - without NetBIOS, Integrating MS Windows networks with Samba, Name resolution as used within MS Windows networking
    NetBIOS-less, TCP/IP - without NetBIOS
    nmblookup, The NetBIOS Name Cache
    nt acl support, File and Directory Permissions Based Controls, Viewing file ownership, Viewing File or Directory Permissions, Modifying file or directory permissions, Windows 2000 Service Pack 2
    ntdrivers.tdb, The printing *.tdb Files
    (see also TDB)
    ntforms.tdb, The printing *.tdb Files
    (see also TDB)
    NTFS, File System Access Controls
    ntprinters.tdb, The printing *.tdb Files
    (see also TDB)

    O

    obey pam restrictions, smb.conf PAM Configuration
    only user, User and Group Based Controls, Why can users access home directories of other users?
    oplock break wait time, Advanced Samba Opportunistic Locking Parameters, Disabling Kernel OpLocks
    oplock contention limit, Advanced Samba Opportunistic Locking Parameters
    os level, What is Browsing?, Setting up WORKGROUP Browsing, Setting up DOMAIN Browsing, Forcing Samba to be the master, Making Samba the domain master
    os2 driver map, Parameters Recommended for Use, Printer driver download for for OS/2 clients?

    P

    page_log, The page_log File Syntax
    passdb backend, MS Windows Workstation/Server Machine Trust Accounts, Account Information Databases, Technical Information, The pdbedit Command, Configuring Samba, Configuring, Users can not logon, auth methods does not work, Passdb Backends and Authentication
    password level, Password checking, The tests, Case handling of passwords, Slow Logins
    password server, Server Security (User Level Security), Security Mode and Master Browsers, Joining an NT4 type Domain with Samba-3, The tests
    patch, Patches
    path, "The network name cannot be found", The [printers] Section, Any [my_printer_name] Section, Print Commands, Creating the [print$] Share, Parameters in the [print$] Section, Subdirectory Structure in [print$], Samba receiving Jobfiles and passing them to CUPS, Auto-Deletion or Preservation of CUPS Spool Files, Permissions on +/var/spool/samba/ get reset after each +reboot, The tests
    PCL, GDI on Windows -- PostScript on UNIX, UNIX Printfile Conversion and GUI Basics, Driver Execution on the Server, Network PostScript RIP: CUPS Filters on Server -- clients use +PostScript Driver with CUPS-PPDs
    PDF, Windows Drivers, GDI and EMF, PostScript Printer Description (PPD) Specification
    pdf, MIME type Conversion Rules
    PDL, GDI on Windows -- PostScript on UNIX, PostScript and Ghostscript
    PJL, Network PostScript RIP: CUPS Filters on Server -- clients use +PostScript Driver with CUPS-PPDs, Benefits of using "CUPS PostScript Driver for +Windows NT/2k/XP" instead of Adobe Driver, Adobe and CUPS PostScript Drivers for Windows Clients
    point and print, Driver Installation Methods on Windows Clients, Three familiar Methods for driver upload plus a new one, cupsomatic/Foomatic -- how do they fit into the Picture?, Run "cupsaddsmb" (quiet Mode), Installing the PostScript Driver on a Client, Manual Driver Installation in 15 Steps
    PostScript, Using CUPS/Samba in an advanced Way -- intelligent printing +with PostScript Driver Download, GDI on Windows -- PostScript on UNIX, UNIX Printfile Conversion and GUI Basics, PostScript and Ghostscript, Prefilters, Driver Execution on the Server, Network PostScript RIP: CUPS Filters on Server -- clients use +PostScript Driver with CUPS-PPDs, CUPS: a "Magical Stone"?, CUPS Package of "PostScript Driver for WinNT/2k/XP"
    (see also Ghostscript)
    RIP, PostScript and Ghostscript
    PPD, PostScript and Ghostscript, PostScript Printer Description (PPD) Specification, PostScript Printer Descriptions (PPDs) for non-PS 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
    CUPS (see CUPS-PPD)
    preferred master, What is Browsing?, Setting up WORKGROUP Browsing, Forcing Samba to be the master, Making Samba the domain master, The tests
    preserve case, Windows 9x / Me Profile Setup
    print command, Parameters Recommended for Use, The [global] Section, Default Print Commands for various UNIX Print Subsystems, Setting up your own Print Commands, Linking of smbd with libcups.so, From Windows Clients to a CUPS/Samba Print Server, Pre-conditions, Manual Configuration
    print ok , Parameters Recommended for Use
    printable, Parameters Recommended for Use, The [printers] Section, Any [my_printer_name] Section
    printcap, Parameters Recommended for Use, Default Print Commands for various UNIX Print Subsystems, Basic Configuration of CUPS support, Linking of smbd with libcups.so, More complex smb.conf Settings for +CUPS, From Windows Clients to a CUPS/Samba Print Server, Pre-conditions
    printcap name, Parameters Recommended for Use, The [global] Section
    printer, Parameters Recommended for Use
    printer admin, Parameters Recommended for Use, The [global] Section, Any [my_printer_name] Section, Parameters in the [print$] Section, Setting Drivers for existing Printers with a Client GUI, IMPORTANT! Setting Device Modes on new Printers, Always make first Client Connection as root or "printer admin", Setting Default Print Options for the Client Drivers, Adding new Printers with the Windows NT APW, More complex smb.conf Settings for +CUPS, What is required for adddriver and setdriver to succeed, Print options for all users can't be set on Win2K/XP
    printer name, Parameters Recommended for Use
    printing, Parameters Recommended for Use, The [global] Section, Default Print Commands for various UNIX Print Subsystems, Setting up your own Print Commands, Basic Configuration of CUPS support, Linking of smbd with libcups.so, More complex smb.conf Settings for +CUPS, From Windows Clients to a CUPS/Samba Print Server, Pre-conditions, Manual Configuration
    printing.tdb, The printing *.tdb Files
    (see also TDB)
    PrintPro (see ESP Print Pro)
    public, The [printers] Section

    Q

    queue resume command, Linking of smbd with libcups.so
    queuepause command, Parameters Recommended for Use, Linking of smbd with libcups.so
    queueresume command, Parameters Recommended for Use

    R

    read list, User and Group Based Controls
    read only, Miscellaneous Controls, The [printers] Section, Parameters in the [print$] Section
    read raw, Read raw
    read size, Read size
    remote announce, NetBIOS over TCP/IP, How Browsing Functions, Use of the Remote Announce parameter, Browsing support in Samba
    remote browse sync, NetBIOS over TCP/IP, How Browsing Functions, Use of the Remote Browse Sync parameter
    root preexec, Logon Scripts
    rpcclient
    adddriver, Run "cupsaddsmb" with verbose Output, Understanding cupsaddsmb, Installing PostScript Driver Files manually (using +rpcclient), Understanding the rpcclient man page, What is required 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), What is required 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), What is required for adddriver and setdriver to succeed, Manual Driver Installation in 15 Steps
    rsync, Accessing the samba sources via rsync and ftp

    S

    secrets.tdb, The printing *.tdb Files
    (see also TDB)
    security, Samba Security Modes, Domain Security Mode (User Level Security), Server Security (User Level Security), What makes Samba a SERVER?, What makes Samba a Domain Controller?, What makes Samba a Domain Member?, Constantly Losing Connections to Password Server, Preparing for Domain Control, Security Mode and Master Browsers, Joining an NT4 type Domain with Samba-3, Why is this better than security = server?, Setup your smb.conf, Run "cupsaddsmb" (quiet Mode), "cupsaddsmb" keeps asking for root password in + neverending loop, Passdb Backends and Authentication, The tests, Configuring WfW password handling
    security mask, File and Directory Permissions Based Controls, Interaction with the standard Samba create mask + parameters
    Server Manager, MS Windows Workstation/Server Machine Trust Accounts, Manual Creation of Machine Trust Accounts
    sessionid.tdb, The printing *.tdb Files
    (see also TDB)
    share_info.tdb, The printing *.tdb Files
    (see also TDB)
    short preserve case, Miscellaneous Controls, Windows 9x / Me Profile Setup
    Short-Cuts, MS Windows NTFS Comparison with UNIX File Systems
    show add printer wizard, Parameters Recommended for Use, The [global] Section, Adding new Printers with the Windows NT APW
    SID, Features and Benefits
    Single Sign On, Caveats to be considered
    smbclient, Testing with smbclient, The tests
    socket options, Socket options
    spooling
    central, Central spooling vs. "Peer-to-Peer" printing
    peer-to-peer, Central spooling vs. "Peer-to-Peer" printing
    spooling-only, CUPS/Samba as a "spooling-only" Print Server; "raw" printing +with Vendor Drivers on Windows Clients
    strict locking, Discussion

    T

    TDB, The printing *.tdb Files, Trivial DataBase Files
    backing up (see tdbbackup)
    tdbbackup, Using tdbbackup
    template homedir, Linux/FreeBSD-specific PAM configuration
    testparm, The tests
    text/plain, MIME type Conversion Rules
    total print jobs, Parameters Recommended for Use, The [global] Section

    U

    UDP, NetBIOS over TCP/IP
    UID, Features and Benefits
    unexpected.tdb, The printing *.tdb Files
    (see also TDB)
    unix charset, Samba and charsets, Japanese charsets
    use client driver, Parameters Recommended for Use, The [global] Section
    user, Share Level Security, The tests
    User Manager, Samba as the Trusted Domain, Samba as the Trusting Domain
    useradd, Manual Creation of Machine Trust Accounts
    username, User and Group Based Controls
    username level, Password checking
    username map, Windows 200x XP Professional

    V

    valid users, User and Group Based Controls, The tests
    veto files, Miscellaneous Controls
    vfs objects, Discussion
    vipw, Manual Creation of Machine Trust Accounts

    W

    winbind separator, Start up the winbindd daemon and test it!
    WINS, What is Browsing?, NetBIOS over TCP/IP, WINS Lookup
    wins hook, What is Browsing?
    wins proxy, What is Browsing?
    wins server, What is Browsing?, WINS - The Windows Internetworking Name Server, Setting up a WINS server
    wins support, What is Browsing?, WINS - The Windows Internetworking Name Server, Setting up a WINS server
    workgroup, Security Mode and Master Browsers, Joining an NT4 type Domain with Samba-3, Browsing support in Samba
    write list, User and Group Based Controls, Parameters in the [print$] Section
    write raw, Write raw
    writeable, The [printers] Section, Any [my_printer_name] Section
    WYSIWYG, Windows Drivers, GDI and EMF

    X

    X Window System, UNIX Printfile Conversion and GUI Basics
    xinetd, Starting from inetd.conf (see inetd)
    Xprint, UNIX Printfile Conversion and GUI Basics
    Prev Up 
    Chapter 41. Further Resources Home 
    diff --git a/docs/htmldocs/lmhosts.5.html b/docs/htmldocs/lmhosts.5.html index b96ddf8ddb..f0a1d02172 100644 --- a/docs/htmldocs/lmhosts.5.html +++ b/docs/htmldocs/lmhosts.5.html @@ -18,10 +18,10 @@ 192.9.200.20 NTSERVER#20 192.9.200.21 SAMBASERVER

    Contains three IP to NetBIOS name mappings. The first - and third will be returned for any queries for the names "TESTPC" - and "SAMBASERVER" respectively, whatever the type component of - the NetBIOS name requested.

    The second mapping will be returned only when the "0x20" name - type for a name "NTSERVER" is queried. Any other name type will not + and third will be returned for any queries for the names "TESTPC" + and "SAMBASERVER" respectively, whatever the type component of + the NetBIOS name requested.

    The second mapping will be returned only when the "0x20" name + type for a name "NTSERVER" is queried. Any other name type will not be resolved.

    The default location of the lmhosts file is in the same directory as the smb.conf(5) file.

    VERSION

    This man page is correct for version 3.0 of the Samba suite.

    SEE ALSO

    smbclient(1), smb.conf(5), and smbpasswd(8)

    AUTHOR

    The original Samba software and related utilities diff --git a/docs/htmldocs/locking.html b/docs/htmldocs/locking.html index a128cac7ce..07228df19d 100644 --- a/docs/htmldocs/locking.html +++ b/docs/htmldocs/locking.html @@ -1,7 +1,7 @@ -Chapter 14. File and Record Locking

    Chapter 14. File and Record Locking
    Prev Part III. Advanced Configuration Next

    Chapter 14. 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 Opportunistic Locking Control
    Example Configuration
    MS Windows Opportunistic Locking and Caching Controls
    Workstation Service Entries
    Server Service Entries
    Persistent Data Corruption
    Common Errors
    locking.tdb error messages
    Additional Reading

    +Chapter 14. File and Record Locking

    Chapter 14. File and Record Locking
    Prev Part III. Advanced Configuration Next

    Chapter 14. 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 Opportunistic Locking Control
    Example Configuration
    MS Windows Opportunistic Locking 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 which 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 provide also.

    @@ -23,13 +23,13 @@ settings on the MS Windows client.

    Note

    Sometimes it is necessary to disable locking control settings BOTH on the Samba server as well as on each MS Windows client! -

    Discussion

    +

    Discussion

    There are two types of locking which need to be performed by a SMB server. The first is record locking which allows a client to lock a range of bytes in a open file. The second is the deny modes that are specified when a file is open.

    -Record locking semantics under Unix is very different from record locking under +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. This can not be fully correct due to several reasons. The simplest is the fact @@ -40,29 +40,29 @@ many more differences, too many to be listed here.

    Samba 2.2 and above implements record locking completely independent of the underlying unix system. If a byte range lock that the client requests happens -to fall into the range 0-2^31, Samba hands this request down to the Unix system. +to fall into the range 0-2^31, Samba hands this request down to the UNIX system. All other locks can not be seen by unix anyway.

    -Strictly a 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 +Strictly 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 over-stress the rpc.lockd. It is also almost always unnecessary as clients are supposed to independently make locking calls before reads and writes anyway if locking is important to them. By default Samba only makes locking calls when explicitly asked -to by a client, but if you set strict locking = yes then it +to by a client, but if you set strict locking = yes then it will make lock checking calls on every read and write.

    -You can also disable by range locking completely using locking = no. +You can also disable byte range locking completely using locking = no. This is useful for those shares that don't support locking or don't need it (such as cdroms). In this case Samba fakes the return codes of locking calls to tell clients that everything is OK.

    -The second class of locking is the deny modes. These +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 client) for the purpose of enhancing network performance when accessing a file @@ -185,7 +185,7 @@ In mission critical high availability environments, careful attention should be given to opportunistic locking. Ideally, comprehensive testing should be done with all affected applications with oplocks enabled and disabled. -

    Exclusively Accessed Shares

    +

    Exclusively Accessed Shares

    Opportunistic locking 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 opportunistic locking is the local @@ -194,7 +194,7 @@ mechanism will cause a delay.

    Home directories are the most obvious examples of where the performance benefit of opportunistic locking 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 opportunistic locking enabled, the potential for delays and resulting perceived poor performance increases. When multiple users are accessing a file on a @@ -206,17 +206,17 @@ 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

    -Local Unix and NFS clients access files without a mandatory +

    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 -that has a file cached. Local Unix or NFS file access can therefore +that has a file cached. Local UNIX or NFS file access can therefore write to a file that has been cached by a Windows client, which exposes the file to likely data corruption.

    -If files are shared between Windows clients, and either local Unix +If files are shared between Windows clients, and either local UNIX or NFS users, then turn opportunistic locking off. -

    Slow and/or Unreliable Networks

    +

    Slow and/or Unreliable Networks

    The biggest potential performance improvement for opportunistic locking occurs when the client-side caching of reads and writes delivers the most differential over sending those reads and writes over the wire. @@ -231,7 +231,7 @@ the most advantageous scenario to utilize opportunistic locking. If the network is slow, unreliable, or a WAN, then do not configure opportunistic locking if there is any chance of multiple users regularly opening the same file. -

    Multi-User Databases

    +

    Multi-User Databases

    Multi-user databases clearly pose a risk due to their very nature - they are typically heavily accessed by numerous users at random intervals. Placing a multi-user database on a share with opportunistic @@ -239,7 +239,7 @@ locking 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 opportunistic locking 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 SMB data stores. PDM applications manage multi-user @@ -252,8 +252,8 @@ 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 oplock management, by disabling opportunistic locking on the share. -

    Beware of Force User

    -Samba includes an smb.conf parameter called force user that changes +

    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 opportunistic locking is enabled on a share, the change in user access causes an oplock break to be sent @@ -265,26 +265,26 @@ to overcome the lost oplock break.

    Avoid the combination of the following:

    • - force user in the smb.conf share configuration. + force user in the smb.conf share configuration.

    • Slow or unreliable networks

    • Opportunistic Locking Enabled -

    Advanced Samba Opportunistic Locking Parameters

    +

    Advanced Samba Opportunistic Locking Parameters

    Samba provides opportunistic locking parameters that allow the administrator to adjust various properties of the oplock mechanism to account for timing and usage levels. These parameters provide good versatility for implementing oplocks in environments where they would likely cause problems. The parameters are: -oplock break wait time, -oplock contention limit. +oplock break wait time, +oplock contention limit.

    For most users, administrators, and environments, if these parameters are required, then the better option is to simply 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 @@ -314,10 +314,10 @@ In mission critical high availability environments, careful attention should be given to opportunistic locking. Ideally, comprehensive testing should be done with all affected applications with oplocks enabled and disabled. -

    Samba Opportunistic Locking Control

    +

    Samba Opportunistic Locking Control

    Opportunistic Locking 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 defacto locking feature. +file locking, so is considered a de facto locking feature. Opportunistic Locking is actually part of the Windows client file caching mechanism. It is not a particularly robust or reliable feature when implemented on the variety of customized networks that exist in @@ -348,7 +348,7 @@ file locking with the under lying OS, SGI IRIX and Linux are the only two OS's t oplock aware at this time.

    Unless your system supports kernel oplocks, you should disable oplocks if you are -accessing the same files from both Unix/Linux and SMB clients. Regardless, oplocks should +accessing the same files from both UNIX/Linux and SMB clients. Regardless, oplocks should always be disabled if you are sharing a database file (e.g., Microsoft Access) between multiple clients, as any break the first client receives will affect synchronisation of the entire file (not just the single record), which will result in a noticeable performance @@ -364,29 +364,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 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 @@ -399,10 +393,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.

    -

    -[global]
-kernel oplocks = yes
-

    +

    kernel oplocks = yes

    The default is "no".

    Veto OpLocks is an smb.conf parameter that identifies specific files for @@ -417,24 +408,15 @@ 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:

    -

    <title>Example Veto OpLock Settings</title>
-[global]
-        veto oplock files = /filename.htm/*.txt/
-
-[share_name]
-        veto oplock files = /*.exe/filename.ext/
-

    +

    Example 14.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 + 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:

    -

    -[global]
-          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 @@ -444,14 +426,8 @@ HAVE READ AND UNDERSTOOD THE SAMBA OPLOCK CODE." Oplock Break Contention Limit can be enable on a per-share basis, or globally for the entire server, in the smb.conf file:

    -

    -[global]
-          oplock break contention limit =  2 (default)
-
-[share_name]
-         oplock break contention limit =  2 (default)
-

    -

    MS Windows Opportunistic Locking and Caching Controls

    +

    Example 14.2. 

    [global]
    oplock break contention limit = 2 (default)
    [share_name]
    oplock break contention limit = 2 (default)

    +

    MS Windows Opportunistic Locking and Caching Controls

    There is a known issue when running applications (like Norton Anti-Virus) 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 @@ -543,7 +519,7 @@ An illustration of how level II oplocks work: 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
 
@@ -552,7 +528,7 @@ An illustration of how level II oplocks work:

    Indicates whether the redirector should use opportunistic-locking (oplock) 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
 
@@ -581,8 +557,8 @@ the server disables raw I/O and opportunistic locking for this connection.
 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

    -If you have applied all of the settings discussed in this paper but data corruption problems +

    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:

    We have credible reports from developers that faulty network hardware, such as a single @@ -592,7 +568,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. @@ -622,18 +598,23 @@ so far: report on https://bugzilla.samba.org without delay. Make sure that you give as much information as you possibly can to help isolate the cause and to allow reproduction of the problem (an essential step in problem isolation and correction). -

    locking.tdb error messages

    - 

    -	> We are seeing lots of errors in the samba logs like:
-	>
-	>    tdb(/usr/local/samba_2.2.7/var/locks/locking.tdb): rec_read bad magic
-	> 0x4d6f4b61 at offset=36116
-	>
-	> What do these mean?
-

    +

    locking.tdb error messages

    + “ + We are seeing lots of errors in the samba logs like: +” +

    +tdb(/usr/local/samba_2.2.7/var/locks/locking.tdb): rec_read bad magic
+ 0x4d6f4b61 at offset=36116
+

    +“ + What do these mean? + ”

    Corrupted tdb. Stop all instances of smbd, delete locking.tdb, restart smbd. -

    Additional Reading

    +

    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 + Microsoft Knowledge Base article 811492.

    Additional Reading

    You may want to check for an updated version of this white paper on our Web site from time to time. Many of our white papers are updated as information changes. For those papers, the Last Edited date is always at the top of the paper. @@ -653,4 +634,4 @@ Microsoft Corporation, April 2001, http://support.microsoft.com/default.aspx?scid=kb;en-us;Q129202. -

    Prev Up Next
    Chapter 13. File, Directory and Share Access Controls Home Chapter 15. Securing Samba
    +

    Prev Up Next
    Chapter 13. File, Directory and Share Access Controls Home Chapter 15. Securing Samba
    diff --git a/docs/htmldocs/log2pcap.1.html b/docs/htmldocs/log2pcap.1.html new file mode 100644 index 0000000000..c84bbdbb4d --- /dev/null +++ b/docs/htmldocs/log2pcap.1.html @@ -0,0 +1,29 @@ +log2pcap

    Name

    log2pcap — Extract network traces from Samba log files

    Synopsis

    log2pcap [-h] [-q] [logfile] [pcap_file]

    DESCRIPTION

    This tool is part of the Samba(7) suite.

    log2pcap reads in a + samba log file and generates a pcap file (readable + by most sniffers, such as ethereal or tcpdump) based on the packet + dumps in the log file.

    The log file must have a log level + of at least 5 to get the SMB header/parameters + right, 10 to get the first 512 data bytes of the + packet and 50 to get the whole packet. +

    OPTIONS

    -h

    If this parameter is + specified the output file will be a + hex dump, in a format that is readable + by the text2pcap utility.

    -q

    Be quiet. No warning messages about missing + or incomplete data will be given.

    logfile

    + Samba log file. log2pcap will try to read the log from stdin + if the log file is not specified. +

    pcap_file

    + Name of the output file to write the pcap (or hexdump) data to. + If this argument is not specified, output data will be written + to stdout. +

    -h|--help

    Print a summary of command line options. +

    EXAMPLES

    Extract all network traffic from all samba log files:

    +	$ cat /var/log/* | log2pcap > trace.pcap
+

    Convert to pcap using text2pcap:

    +	$ log2pcap -h samba.log | text2pcap -T 139,139 - trace.pcap
+

    VERSION

    This man page is correct for version 3.0 of the Samba suite.

    BUGS

    Only SMB data is extracted from the samba logs, no LDAP, + NetBIOS lookup or other data.

    The generated TCP and IP headers don't contain a valid + checksum.

    SEE ALSO

    text2pcap(1), ethereal(1)

    AUTHOR

    The original Samba software and related utilities + were created by Andrew Tridgell. Samba is now developed + by the Samba Team as an Open Source project similar + to the way the Linux kernel is developed.

    This manpage was written by Jelmer Vernooij.

    diff --git a/docs/htmldocs/migration.html b/docs/htmldocs/migration.html index b8027a62ea..36b6edb0b1 100644 --- a/docs/htmldocs/migration.html +++ b/docs/htmldocs/migration.html @@ -1 +1 @@ -Part IV. Migration and Updating
    Part IV. Migration and Updating
    Prev   Next

    Migration and Updating

    Table of Contents

    30. Upgrading from Samba-2.x to Samba-3.0.0
    Charsets
    Obsolete configuration options
    Password Backend
    31. Migration from NT4 PDC to Samba-3 PDC
    Planning and Getting Started
    Objectives
    Steps In Migration Process
    Migration Options
    Planning for Success
    Samba Implementation Choices
    32. SWAT - The Samba Web Administration Tool
    Features and Benefits
    Enabling SWAT for use
    Securing SWAT through SSL
    The SWAT Home Page
    Global Settings
    Share Settings
    Printers Settings
    The SWAT Wizard
    The Status Page
    The View Page
    The Password Change Page
    Prev Up Next
    Chapter 29. High Availability Options Home Chapter 30. Upgrading from Samba-2.x to Samba-3.0.0
    +Part IV. Migration and Updating
    Part IV. Migration and Updating
    Prev   Next

    Migration and Updating

    Table of Contents

    30. Upgrading from Samba-2.x to Samba-3.0.0
    New Features in Samba-3
    Configuration Parameter Changes
    Removed Parameters
    New Parameters
    Modified Parameters (changes in behavior):
    New Functionality
    Databases
    Changes in Behavior
    Charsets
    Passdb Backends and Authentication
    Charsets
    LDAP
    31. 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
    32. SWAT - The Samba Web Administration Tool
    Features and Benefits
    Enabling SWAT for use
    Securing SWAT through SSL
    The SWAT Home Page
    Global Settings
    Share Settings
    Printers Settings
    The SWAT Wizard
    The Status Page
    The View Page
    The Password Change Page
    Prev Up Next
    Chapter 29. High Availability Options Home Chapter 30. Upgrading from Samba-2.x to Samba-3.0.0
    diff --git a/docs/htmldocs/mount.cifs.8.html b/docs/htmldocs/mount.cifs.8.html new file mode 100644 index 0000000000..766e00fd11 --- /dev/null +++ b/docs/htmldocs/mount.cifs.8.html @@ -0,0 +1,103 @@ +mount.cifs

    Name

    mount.cifs — mount using the Common Internet File System (CIFS)

    Synopsis

    mount.cifs {service} {mount-point} [-o options]

    DESCRIPTION

    This tool is part of the Samba(7) suite.

    mount.cifs mounts a Linux CIFS filesystem. It +is usually invoked indirectly by +the mount(8) command when using the +"-t cifs" option. This command only works in Linux, and the kernel must +support the cifs filesystem. The CIFS protocol is the successor to the +SMB protocol and is supported by most Windows servers and many other +commercial servers and Network Attached Storage appliances as well as +by the popular Open Source server Samba. +

    + The mount.cifs utility attaches the UNC name (exported network resource) to + the local directory mount-point. It is possible to set the mode for mount.cifs to +setuid root to allow non-root users to mount shares to directories for which they +have write permission. +

    + Options to mount.cifs are specified as a comma-separated +list of key=value pairs. It is possible to send options other +than those listed here, assuming that cifs supports them. If +you get mount failures, check your kernel log for errors on +unknown options. +

    mount.cifs is a daemon. After mounting it keeps running until + the mounted resource is unmounted (usually via the umount utility) +

    OPTIONS

    username=arg

    specifies the username to connect as. If + this is not given, then the environment variable USER is used. This option can also take the +form "user%password" or "user/workgroup" or +"user/workgroup%password" to allow the password and workgroup +to be specified as part of the username. +

    password=arg

    specifies the CIFS password. If this +option is not given then the environment variable +PASSWD is used. If it can find +no password mount.cifs will prompt +for a passeword, unless the guest option is +given. +

    Note that password which contain the arguement delimiter +character (i.e. a comma ',') will failed to be parsed correctly +on the command line. However, the same password defined +in the PASSWD environment variable or a credentials file (see +below) will be read correctly. +

    credentials=filename

    + specifies a file that contains a username + and/or password. The format of the file is: + 

    +.nf
+		username = value
+		password = value
+.fi
+

    +This is preferred over having passwords in plaintext in a +shared file, such as /etc/fstab. Be sure to protect any +credentials file properly. +

    uid=arg

    sets the uid that will own all files on + the mounted filesystem. + It may be specified as either a username or a numeric uid. + This parameter is ignored when the target server supports + the CIFS Unix extensions.

    gid=arg

    sets the gid that will own all files on +the mounted filesystem. +It may be specified as either a groupname or a numeric +gid. This parameter is ignored when the target server supports +the CIFS Unix extensions. +

    port=arg

    sets the port number on the server to attempt to contact to negotiate +CIFS support. If the CIFS server is not listening on this port or +if it is not specified, the default ports will be tried i.e. +port 445 is tried and if no response then port 139 is tried. +

    file_mode=arg

    If the server does not support the CIFS Unix extensions this + overrides default file mode which will be used locally.

    dir_mode=arg

    If the server does not support the CIFS Unix extensions this + overrides the default mode for directories.

    ip=arg

    sets the destination host or IP address.

    domain=arg

    sets the domain (workgroup) of the user

    guest

    don't prompt for a password

    ro

    mount read-only

    rw

    mount read-write

    rsize

    default network read size

    wsize

    default network write size

    ENVIRONMENT VARIABLES

    + The variable USER may contain the username of the +person using the client. This information is used only if the +protocol level is high enough to support session-level +passwords. The variable can be used to set both username and +password by using the format username%password. +

    + The variable PASSWD may contain the password of the +person using the client. This information is used only if the +protocol level is high enough to support session-level +passwords. +

    + The variable PASSWD_FILE may contain the pathname +of a file to read the password from. A single line of input is +read and used as the password. +

    NOTES

    This command may be used only by root.

    CONFIGURATION

    +The primary mechanism for making configuration changes and for reading +debug information for the cifs vfs is via the Linux /proc filesystem. +In the directory /proc/fs/cifs are various configuration files and +pseudo files which can display debug information. For more +information see the kernel file fs/cifs/README +

    BUGS

    Passwords and other options containing , can not be handled. +For passwords an alternative way of passing them is in a credentials +file or in the PASSWD environment.

    The credentials file does not handle usernames or passwords with + leading space.

    +Note that the typical response to a bug report is suggestion +to try the latest version first. So please try doing that first, +and always include which versions you use of relevant software +when reporting bugs (minimum: samba, kernel, distribution) +

    VERSION

    This man page is correct for version 3.0 of + the Samba suite.

    SEE ALSO

    + Documentation/filesystems/cifs.txt and fs/cifs/README in the linux kernel + source tree may contain additional options and information. +

    AUTHOR

    Steve French

    The syntax and manpage were loosely based on that of smbmount. It + was converted to Docbook/XML by Jelmer Vernooij.

    The current maintainer of the Linux cifs vfs and the userspace + tool mount.cifs is Steve French. + The SAMBA Mailing list + is the preferred place to ask questions regarding these programs. +

    diff --git a/docs/htmldocs/msdfs.html b/docs/htmldocs/msdfs.html index d01b8f4c5d..9fdf906ed0 100644 --- a/docs/htmldocs/msdfs.html +++ b/docs/htmldocs/msdfs.html @@ -1,24 +1,22 @@ -Chapter 17. Hosting a Microsoft Distributed File System tree on Samba
    Chapter 17. Hosting a Microsoft Distributed File System tree on Samba
    Prev Part III. Advanced Configuration Next

    Chapter 17. Hosting a Microsoft Distributed File System tree on Samba

    Shirish Kalele

    Samba Team & Veritas Software


    +Chapter 17. Hosting a Microsoft Distributed File System tree on Samba

    Chapter 17. Hosting a Microsoft Distributed File System tree on Samba
    Prev Part III. Advanced Configuration Next

    Chapter 17. Hosting a Microsoft Distributed File System tree on Samba

    Shirish Kalele

    Samba Team & Veritas Software



    -

    12 Jul 2000

    Table of Contents

    Features and Benefits
    Common Errors

    Features and Benefits

    +

    12 Jul 2000

    Table of Contents

    Features and Benefits
    Common Errors

    Features and Benefits

    The Distributed File System (or 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 etc.

    - For information about DFS, refer to - - Microsoft documentation at http://www.microsoft.com/NTServer/nts/downloads/winfeatures/NTSDistrFile/AdminGuide.asp. + 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 + This document explains how to host a DFS tree on a UNIX machine (for DFS-aware clients to browse) using Samba.

    - To enable SMB-based DFS for Samba, configure it with the --with-msdfs + To enable SMB-based DFS for Samba, configure it with the --with-msdfs option. Once built, 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 + 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, @@ -27,23 +25,14 @@ DFS trees on Samba work with all DFS-aware clients ranging from Windows 95 to 200x.

    Here's an example of setting up a DFS tree on a Samba server. - 

    -# The smb.conf file:
-[global]
-	netbios name = SMOKEY
-	host msdfs   = yes
-
-[dfs]
-	path = /export/dfsroot
-	msdfs root = yes
-

    In the /export/dfsroot directory we set up our dfs links to +

    Example 17.1. smb.conf with DFS configured

    [global]
    netbios name = GANDALF
    host msdfs = yes
    [dfs]
    path = /export/dfsroot
    msdfs root = yes

    In the /export/dfsroot directory we set up our 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
-

    You should set up the permissions and ownership of +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 +

    You should set up the permissions and ownership of the directory acting as the DFS root such that only designated users can create, delete or modify the msdfs links. Also note that symlink names should be all lowercase. This limitation exists @@ -52,11 +41,11 @@ 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 + 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 + 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 that only designated users can - modify the symbolic links in the directory.

    Prev Up Next
    Chapter 16. Interdomain Trust Relationships Home Chapter 18. Classical Printing Support
    + modify the symbolic links in the directory.

    Prev Up Next
    Chapter 16. Interdomain Trust Relationships Home Chapter 18. Classical Printing Support
    diff --git a/docs/htmldocs/net.8.html b/docs/htmldocs/net.8.html index 13e4be81be..a98700e42f 100644 --- a/docs/htmldocs/net.8.html +++ b/docs/htmldocs/net.8.html @@ -24,16 +24,15 @@ Defaults to trying 445 first, then 139.

    -n <primary NetBIOS name>

    This option allows you to override the NetBIOS name that Samba uses for itself. This is identical -to setting the NetBIOS -name parameter in the smb.conf(5) file. However, a command +to setting the netbios name parameter in the smb.conf file. +However, a command line setting will take precedence over settings in -smb.conf(5).

    -s <configuration file>

    The file specified contains the +smb.conf.

    -s <configuration file>

    The file specified contains the configuration details required by the server. The information in this file includes server-specific information such as what printcap file to use, as well as descriptions of all the services that the server is -to provide. See -smb.conf(5) for more information. +to provide. See smb.conf for more information. The default configuration file name is determined at compile time.

    -S server

    Name of target server. You should specify either @@ -54,12 +53,18 @@ amounts of log data, and should only be used when investigating a problem. Levels above 3 are designed for use only by developers and generate HUGE amounts of log data, most of which is extremely cryptic.

    Note that specifying this parameter here will -override the log -level parameter in the -smb.conf(5) file.

    COMMANDS

    TIME

    The NET TIME command allows you to view the time on a remote server +override the log level parameter +in the smb.conf file.

    COMMANDS

    CHANGESECRETPW

    This command allows the Samba machine account password to be set from an external application +to a machine account password that has already been stored in Active Directory. DO NOT USE this command +unless you know exactly what you are doing. The use of this command requires that the force flag (-f) +be used also. There will be NO command prompt. Whatever information is piped into stdin, either by +typing at the command line or otherwise, will be stored as the literal machine password. Do NOT use +this without care and attention as it will overwrite a legitimate machine password without warning. +YOU HAVE BEEN WARNED. +

    TIME

    The NET TIME command allows you to view the time on a remote server or synchronise the time on the local server with the time on the remote server.

    TIME

    Without any options, the NET TIME command displays the time on the remote server. -

    TIME SYSTEM

    Displays the time on the remote server in a format ready for /bin/date

    TIME SET

    Tries to set the date and time of the local server to that on +

    TIME SYSTEM

    Displays the time on the remote server in a format ready for /bin/date

    TIME SET

    Tries to set the date and time of the local server to that on the remote server using /bin/date.

    TIME ZONE

    Displays the timezone in hours from GMT on the remote computer.

    [RPC|ADS] JOIN [TYPE] [-U username[%password]] [options]

    Join a domain. If the account already exists on the server, and [TYPE] is MEMBER, the machine will attempt to join automatically. @@ -104,8 +109,8 @@ can be controlled using 'NET CACHE'.

    All the timeout parameters support th List all current items in the cache.

    CACHE FLUSH

    Remove all the current items from the cache.

    GETLOCALSID [DOMAIN]

    Print the SID of the specified domain, or if the parameter is omitted, the SID of the domain the local server is in.

    SETLOCALSID S-1-5-21-x-y-z

    Sets domain sid for the local server to the specified SID.

    GROUPMAP

    Manage the mappings between Windows group SIDs and UNIX groups. -Parameters take the for "parameter=value". Common options include:

    • unixgroup - Name of the UNIX group

    • ntgroup - Name of the Windows NT group (must be - resolvable to a SID

    • rid - Unsigned 32-bit integer

    • sid - Full SID in the form of "S-1-..."

    • type - Type of the group; either 'domain', 'local', +Parameters take the for "parameter=value". Common options include:

      • unixgroup - Name of the UNIX group

      • ntgroup - Name of the Windows NT group (must be + resolvable to a SID

      • rid - Unsigned 32-bit integer

      • sid - Full SID in the form of "S-1-..."

      • type - Type of the group; either 'domain', 'local', or 'builtin'

      • comment - Freeform text description of the group

      GROUPMAP ADD

      Add a new group mapping entry

      net groupmap add {rid=int|sid=string} unixgroup=string [type={domain|local|builtin}] [ntgroup=string] [comment=string]

      GROUPMAP DELETE

      Delete a group mapping entry

      net groupmap delete {ntgroup=string|sid=SID}

      GROUPMAP MODIFY

      Update en existing group entry

      net groupmap modify {ntgroup=string|sid=SID} [unixgroup=string] [comment=string] [type={domain|local}

      GROUPMAP LIST

      List existing group mapping entries

      net groupmap list [verbose] [ntgroup=string] [sid=SID]

    MAXRID

    Prints out the highest RID currently in use on the local server (by the active 'passdb backend').

    RPC INFO

    Print information about the domain of the remote server, @@ -131,7 +136,7 @@ local server. Can only be run an a BDC.

    GETSID

    Fetch domain SID and store it in the local secrets.tdb.

    ADS LEAVE

    Make the remote host leave the domain it is part of.

    ADS STATUS

    Print out status of machine account of the local machine in ADS. Prints out quite some debug info. Aimed at developers, regular users should use NET ADS TESTJOIN.

    ADS PRINTER

    ADS PRINTER INFO [PRINTER] [SERVER]

    -Lookup info for PRINTER on SERVER. The printer name defaults to "*", the +Lookup info for PRINTER on SERVER. The printer name defaults to "*", the server name defaults to the local host.

    ADS PRINTER PUBLISH PRINTER

    Publish specified printer using ADS.

    ADS PRINTER REMOVE PRINTER

    Remove specified printer from ADS directory.

    ADS SEARCH EXPRESSION ATTRIBUTES...

    Perform a raw LDAP search on a ADS server and dump the results. The expression is a standard LDAP search expression, and the attributes are a list of LDAP fields to show in the results.

    Example: net ads search '(objectCategory=group)' sAMAccountName diff --git a/docs/htmldocs/nmbd.8.html b/docs/htmldocs/nmbd.8.html index c282bde89d..f3e514fa77 100644 --- a/docs/htmldocs/nmbd.8.html +++ b/docs/htmldocs/nmbd.8.html @@ -4,12 +4,12 @@ those produced by SMB/CIFS clients such as Windows 95/98/ME, Windows NT, Windows 2000, Windows XP and LanManager clients. It also participates in the browsing protocols which make up the - Windows "Network Neighborhood" view.

    SMB/CIFS clients, when they start up, may wish to + Windows "Network Neighborhood" view.

    SMB/CIFS clients, when they start up, may wish to locate an SMB/CIFS server. That is, they wish to know what IP number a specified host is using.

    Amongst other services, nmbd will listen for such requests, and if its own NetBIOS name is specified it will respond with the IP number of the host it - is running on. Its "own NetBIOS name" is by + is running on. Its "own NetBIOS name" is by default the primary DNS name of the host it is running on, but this can be overridden with the -n option (see OPTIONS below). Thus nmbd will @@ -42,7 +42,7 @@

    -S

    If specified, this parameter causes nmbd to log to standard output rather than a file.

    -i

    If this parameter is specified it causes the - server to run "interactively", not as a daemon, even if the + server to run "interactively", not as a daemon, even if the server is executed on the command line of a shell. Setting this parameter negates the implicit daemon mode when run from the command line. nmbd also logs to standard @@ -51,8 +51,7 @@

    -H <filename>

    NetBIOS lmhosts file. The lmhosts file is a list of NetBIOS names to IP addresses that is loaded by the nmbd server and used via the name - resolution mechanism name resolve - order described in smb.conf(5) to resolve any + resolution mechanism name resolve order described in smb.conf(5) to resolve any NetBIOS name queries needed by the server. Note that the contents of this file are NOT used by nmbd to answer any name queries. @@ -67,8 +66,7 @@ configuration details required by the server. The information in this file includes server-specific information such as what printcap file to use, as well as descriptions of all the services that the server is -to provide. See -smb.conf(5) for more information. +to provide. See smb.conf for more information. The default configuration file name is determined at compile time.

    -d|--debug=debuglevel

    debuglevel is an integer from 0 to 10. The default value if this parameter is @@ -82,10 +80,9 @@ amounts of log data, and should only be used when investigating a problem. Levels above 3 are designed for use only by developers and generate HUGE amounts of log data, most of which is extremely cryptic.

    Note that specifying this parameter here will -override the log -level parameter in the -smb.conf(5) file.

    -l|--logfile=logbasename

    File name for log/debug files. The extension -".client" will be appended. The log file is +override the log level parameter +in the smb.conf file.

    -l|--logfile=logbasename

    File name for log/debug files. The extension +".client" will be appended. The log file is never removed by the client.

    -p <UDP port number>

    UDP port number is a positive integer value. This option changes the default UDP port number (normally 137) @@ -94,29 +91,26 @@ never removed by the client. won't need help!

    FILES

    /etc/inetd.conf

    If the server is to be run by the inetd meta-daemon, this file must contain suitable startup information for the - meta-daemon. See the install document - for details. + meta-daemon.

    /etc/rc

    or whatever initialization script your system uses).

    If running the server as a daemon at startup, this file will need to contain an appropriate startup - sequence for the server. See the "How to Install and Test SAMBA" document - for details.

    /etc/services

    If running the server via the + sequence for the server.

    /etc/services

    If running the server via the meta-daemon inetd, this file must contain a mapping of service name (e.g., netbios-ssn) to service port (e.g., 139) and protocol type (e.g., tcp). - See the "How to Install and Test SAMBA" - document for details.

    /usr/local/samba/lib/smb.conf

    This is the default location of +

    /usr/local/samba/lib/smb.conf

    This is the default location of the smb.conf(5) server configuration file. Other common places that systems install this file are /usr/samba/lib/smb.conf and /etc/samba/smb.conf.

    When run as a WINS server (see the - wins support + wins support parameter in the smb.conf(5) man page), nmbd will store the WINS database in the file wins.dat in the var/locks directory configured under wherever Samba was configured to install itself.

    If nmbd is acting as a - browse master (see the local master + browse master (see the local master parameter in the smb.conf(5) man page, nmbd will store the browsing database in the file browse.dat in the var/locks directory diff --git a/docs/htmldocs/nmblookup.1.html b/docs/htmldocs/nmblookup.1.html index 46c17ce706..10131752b3 100644 --- a/docs/htmldocs/nmblookup.1.html +++ b/docs/htmldocs/nmblookup.1.html @@ -6,9 +6,9 @@ are done over UDP.

    OPTIONS

    -M

    Searches for a master browser by looking up the NetBIOS name name with a type of 0x1d. If - name is "-" then it does a lookup on the special name + name is "-" then it does a lookup on the special name __MSBROWSE__. Please note that in order to - use the name "-", you need to make sure "-" isn't parsed as an + use the name "-", you need to make sure "-" isn't parsed as an argument, e.g. use : nmblookup -M -- -.

    -R

    Set the recursion desired bit in the packet to do a recursive lookup. This is used when sending a name @@ -28,10 +28,10 @@

    -A

    Interpret name as an IP Address and do a node status query on this address.

    -n <primary NetBIOS name>

    This option allows you to override the NetBIOS name that Samba uses for itself. This is identical -to setting the NetBIOS -name parameter in the smb.conf(5) file. However, a command +to setting the netbios name parameter in the smb.conf file. +However, a command line setting will take precedence over settings in -smb.conf(5).

    -i <scope>

    This specifies a NetBIOS scope that +smb.conf.

    -i <scope>

    This specifies a NetBIOS scope that nmblookup will use to communicate with when generating NetBIOS names. For details on the use of NetBIOS scopes, see rfc1001.txt and rfc1002.txt. NetBIOS scopes are @@ -43,7 +43,7 @@ smb.conf. If the domain specified is the same as the servers NetBIOS name, it causes the client to log on using the servers local SAM (as opposed to the Domain SAM).

    -O socket options

    TCP socket options to set on the client socket. See the socket options parameter in -the smb.conf(5) manual page for the list of valid +the smb.conf manual page for the list of valid options.

    -h|--help

    Print a summary of command line options.

    -B <broadcast address>

    Send the query to the given broadcast address. Without this option the default behavior of nmblookup is to send the @@ -59,8 +59,7 @@ configuration details required by the server. The information in this file includes server-specific information such as what printcap file to use, as well as descriptions of all the services that the server is -to provide. See -smb.conf(5) for more information. +to provide. See smb.conf for more information. The default configuration file name is determined at compile time.

    -d|--debug=debuglevel

    debuglevel is an integer from 0 to 10. The default value if this parameter is @@ -74,10 +73,9 @@ amounts of log data, and should only be used when investigating a problem. Levels above 3 are designed for use only by developers and generate HUGE amounts of log data, most of which is extremely cryptic.

    Note that specifying this parameter here will -override the log -level parameter in the -smb.conf(5) file.

    -l|--logfile=logbasename

    File name for log/debug files. The extension -".client" will be appended. The log file is +override the log level parameter +in the smb.conf file.

    -l|--logfile=logbasename

    File name for log/debug files. The extension +".client" will be appended. The log file is never removed by the client.

    -T

    This causes any IP addresses found in the lookup to be looked up via a reverse DNS lookup into a diff --git a/docs/htmldocs/ntlm_auth.1.html b/docs/htmldocs/ntlm_auth.1.html index d2ee979d4d..27dfee1a0f 100644 --- a/docs/htmldocs/ntlm_auth.1.html +++ b/docs/htmldocs/ntlm_auth.1.html @@ -17,8 +17,7 @@ configuration details required by the server. The information in this file includes server-specific information such as what printcap file to use, as well as descriptions of all the services that the server is -to provide. See -smb.conf(5) for more information. +to provide. See smb.conf for more information. The default configuration file name is determined at compile time.

    -d|--debug=debuglevel

    debuglevel is an integer from 0 to 10. The default value if this parameter is @@ -32,10 +31,9 @@ amounts of log data, and should only be used when investigating a problem. Levels above 3 are designed for use only by developers and generate HUGE amounts of log data, most of which is extremely cryptic.

    Note that specifying this parameter here will -override the log -level parameter in the -smb.conf(5) file.

    -l|--logfile=logbasename

    File name for log/debug files. The extension -".client" will be appended. The log file is +override the log level parameter +in the smb.conf file.

    -l|--logfile=logbasename

    File name for log/debug files. The extension +".client" will be appended. The log file is never removed by the client.

    -h|--help

    Print a summary of command line options.

    VERSION

    This man page is correct for version 3.0 of the Samba diff --git a/docs/htmldocs/optional.html b/docs/htmldocs/optional.html index 1c300521bc..bd76a344f8 100644 --- a/docs/htmldocs/optional.html +++ b/docs/htmldocs/optional.html @@ -1,26 +1,35 @@ -Part III. Advanced Configuration

    Part III. Advanced Configuration
    Prev   Next

    Advanced Configuration

    Valuable Nuts and Bolts Information

    +Part III. Advanced Configuration

    Part III. Advanced Configuration
    Prev   Next

    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

    10. Samba / MS Windows Network Browsing Guide
    Features and Benefits
    What is Browsing?
    Discussion
    NetBIOS over TCP/IP
    TCP/IP - without NetBIOS
    DNS and Active Directory
    How Browsing Functions
    Setting up WORKGROUP Browsing
    Setting up DOMAIN Browsing
    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
    Setting up a WINS server
    WINS Replication
    Static WINS Entries
    Helpful Hints
    Windows Networking Protocols
    Name Resolution Order
    Technical Overview of browsing
    Browsing support in Samba
    Problem resolution
    Browsing across subnets
    Common Errors
    How can one flush the Samba NetBIOS name cache without restarting Samba?
    My client reports "This server is not configured to list shared resources"
    11. Account Information Databases
    Features and Benefits
    Technical Information
    Important Notes About Security
    Mapping User Identifiers between MS Windows and Unix
    Account Management Tools
    The smbpasswd Command
    The pdbedit Command
    Password Backends
    Plain Text
    smbpasswd - Encrypted Password Database
    tdbsam
    ldapsam
    MySQL
    XML
    Common Errors
    Users can not logon - Users not in Samba SAM
    Users are being added to the wrong backend database
    auth methods does not work
    12. Mapping MS Windows and Unix Groups
    Features and Benefits
    Discussion
    Example Configuration
    Configuration Scripts
    Sample smb.conf add group script
    Script to configure Group Mapping
    Common Errors
    Adding Groups Fails
    Adding MS Windows Groups to MS Windows Groups Fails
    13. 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
    Common Errors
    Users can not write to a public share
    I have set force user and Samba still makes root the owner of all the files - I touch!
    14. File and Record Locking
    Features and Benefits
    Discussion
    Opportunistic Locking Overview
    Samba Opportunistic Locking Control
    Example Configuration
    MS Windows Opportunistic Locking and Caching Controls
    Workstation Service Entries
    Server Service Entries
    Persistent Data Corruption
    Common Errors
    locking.tdb error messages
    Additional Reading
    15. 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 a IPC$ share deny
    NTLMv2 Security
    Upgrading Samba
    Common Errors
    Smbclient works on localhost, but the network is dead
    Why can users access home directories of other users?
    16. Interdomain Trust Relationships
    Features and Benefits
    Trust Relationship Background
    Native MS Windows NT4 Trusts Configuration
    NT4 as the Trusting Domain (ie. creating the trusted account)
    NT4 as the Trusted Domain (ie. creating trusted account's password)
    Configuring Samba NT-style Domain Trusts
    Samba-3 as the Trusting Domain
    Samba-3 as the Trusted Domain
    Common Errors
    Tell me about Trust Relationships using Samba
    17. Hosting a Microsoft Distributed File System tree on Samba
    Features and Benefits
    Common Errors
    18. Classical Printing Support
    Features and Benefits
    Technical Introduction
    What happens if you send a Job from a Client
    Printing Related Configuration Parameters
    Parameters Recommended for Use
    Parameters for Backwards Compatibility
    Parameters no longer in use
    A simple Configuration to Print with Samba-3
    Verification of "Settings in Use" with testparm
    A little Experiment to warn you
    Extended Sample Configuration to Print with Samba-3
    Detailed Explanation of the Example's Settings
    The [global] Section
    The [printers] Section
    Any [my_printer_name] Section
    Print Commands
    Default Print Commands for various Unix Print Subsystems
    Setting up your own Print Commands
    Innovations in Samba Printing since 2.2
    Client Drivers on Samba Server for Point'n'Print
    The [printer$] Section is removed from Samba-3
    Creating the [print$] Share
    Parameters in the [print$] Section
    Subdirectory Structure in [print$]
    Installing Drivers into [print$]
    Setting Drivers for existing Printers with a Client GUI
    Setting Drivers for existing Printers with -rpcclient
    "The Proof of the Pudding lies in the Eating" (Client Driver Install -Procedure)
    The first Client Driver Installation
    IMPORTANT! Setting Device Modes on new Printers
    Further Client Driver Install Procedures
    Always make first Client Connection as root or "printer admin"
    Other Gotchas
    Setting Default Print Options for the Client Drivers
    Supporting large Numbers of Printers
    Adding new Printers with the Windows NT APW
    Weird Error Message Cannot connect under a -different Name
    Be careful when assembling Driver Files
    Samba and Printer Ports
    Avoiding the most common Misconfigurations of the Client Driver
    The Imprints Toolset
    What is Imprints?
    Creating Printer Driver Packages
    The Imprints Server
    The Installation Client
    Add Network Printers at Logon without User Interaction
    The addprinter command
    Migration of "Classical" printing to Samba-3
    Publishing Printer Information in Active Directory or LDAP
    Common Errors and Problems
    I give my root password but I don't get access
    My printjobs get spooled into the spooling directory, but then get lost
    19. CUPS Printing Support in Samba 3.0
    Introduction
    Features and Benefits
    Overview
    Basic Configuration of CUPS support
    Linking of smbd with libcups.so
    Simple smb.conf Settings for CUPS
    More complex smb.conf Settings for -CUPS
    Advanced Configuration
    Central spooling vs. "Peer-to-Peer" printing
    CUPS/Samba as a "spooling-only" Print Server; "raw" printing -with Vendor Drivers on Windows Clients
    Driver Installation Methods on Windows Clients
    Explicitly enable "raw" printing for -application/octet-stream!
    Three familiar Methods for driver upload plus a new one
    Using CUPS/Samba in an advanced Way -- 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
    CUPS can use all 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
    Filter Requirements
    Prefilters
    pstops
    pstoraster
    imagetops and imagetoraster
    rasterto [printers specific]
    CUPS Backends
    cupsomatic/Foomatic -- how do they fit into the Picture?
    The Complete Picture
    mime.convs
    "Raw" printing
    "application/octet-stream" printing
    PostScript Printer Descriptions (PPDs) for non-PS Printers
    Difference between cupsomatic/foomatic-rip and -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 -- UNIX/Samba Print -Servers)
    From Windows Clients to a CUPS/Samba Print Server
    Samba receiving Jobfiles and passing them to CUPS
    Network PostScript RIP: CUPS Filters on Server -- clients use -PostScript Driver with CUPS-PPDs
    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
    Setting up CUPS for driver Download
    cupsaddsmb: the unknown Utility
    Prepare your smb.conf for -cupsaddsmb
    CUPS Package of "PostScript Driver for WinNT/2k/XP"
    Recognize the different Driver Files
    Acquiring the Adobe Driver Files
    ESP Print Pro Package of "PostScript Driver for -WinNT/2k/XP"
    Caveats to be considered
    What are the Benefits of using the "CUPS PostScript Driver for -Windows NT/2k/XP" as compared to the Adobe Driver?
    Run "cupsaddsmb" (quiet Mode)
    Run "cupsaddsmb" with verbose Output
    Understanding cupsaddsmb
    How to recognize if cupsaddsm 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
    What is required for adddriver and setdriver to succeed
    Manual Commandline Driver Installation in 15 little 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
    Auto-Deletion or Preservation of CUPS Spool Files
    CUPS Configuration Settings explained
    Pre-conditions
    Manual Configuration
    When not to use Samba to print to -CUPS
    In Case of Trouble.....
    Where to find Documentation
    How to ask for Help
    Where to find Help
    Appendix
    Printing from CUPS to Windows attached -Printers
    More CUPS filtering Chains
    Trouble Shooting Guidelines to fix typical Samba printing -Problems
    An Overview of the CUPS Printing Processes
    20. Stackable VFS modules
    Features and Benefits
    Discussion
    Included modules
    audit
    extd_audit
    fake_perms
    recycle
    netatalk
    VFS modules available elsewhere
    DatabaseFS
    vscan
    Common Errors
    21. Integrated Logon Support using Winbind
    Features and Benefits
    Introduction
    What Winbind Provides
    Target Uses
    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
    22. Advanced Network Management
    Features and Benefits
    Remote Server Administration
    Remote Desktop Management
    Remote Management from NoMachines.Com
    Network Logon Script Magic
    Adding printers without user intervention
    Common Errors
    23. 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
    Samba Editreg Toolset
    Windows NT4/200x
    Samba PDC
    System Startup and Logon Processing Overview
    Common Errors
    Policy Does Not Work
    24. Desktop Profile Management
    Features and Benefits
    Roaming Profiles
    Samba Configuration for Profile Handling
    Windows Client Profile Configuration Information
    Sharing Profiles between W9x/Me and NT4/200x/XP workstations
    Profile Migration from Windows NT4/200x Server to Samba
    Mandatory profiles
    Creating/Managing Group Profiles
    Default Profile for Windows Users
    MS Windows 9x/Me
    MS Windows NT4 Workstation
    MS Windows 200x/XP
    Common Errors
    How does one set up roaming profiles for just one (or a few) user/s or group/s?
    Can NOT use Roaming Profiles
    Changing the default profile
    25. 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
    26. 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
    My Boomerang Won't Come Back
    Very Slow Network Connections
    Samba server name change problem
    27. Unicode/Charsets
    Features and Benefits
    What are charsets and unicode?
    Samba and charsets
    Conversion from old names
    Japanese charsets
    28. Samba Backup Techniques
    Note
    Features and Benefits
    29. High Availability Options
    Note
    Prev Up Next
    Chapter 9. MS Windows Network Configuration Guide Home Chapter 10. Samba / MS Windows Network Browsing Guide
    +

    Table of Contents

    10. Samba / MS Windows Network Browsing Guide
    Features and Benefits
    What is Browsing?
    Discussion
    NetBIOS over TCP/IP
    TCP/IP - without NetBIOS
    DNS and Active Directory
    How Browsing Functions
    Setting up WORKGROUP Browsing
    Setting up DOMAIN Browsing
    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
    Setting up a WINS server
    WINS Replication
    Static WINS Entries
    Helpful Hints
    Windows Networking Protocols
    Name Resolution Order
    Technical Overview of browsing
    Browsing support in Samba
    Problem resolution
    Browsing across subnets
    Common Errors
    How can one flush the Samba NetBIOS name cache without restarting Samba?
    My client reports "This server is not configured to list shared resources"
    I get an Unable to browse the network error
    11. Account Information Databases
    Features and Benefits
    Backwards Compatibility Backends
    New Backends
    Technical Information
    Important Notes About Security
    Mapping User Identifiers between MS Windows and UNIX
    Mapping Common UIDs/GIDs on Distributed Machines
    Account Management Tools
    The smbpasswd Command
    The pdbedit Command
    Password Backends
    Plain Text
    smbpasswd - Encrypted Password Database
    tdbsam
    ldapsam
    MySQL
    XML
    Common Errors
    Users can not logon
    Users being added to wrong backend database
    auth methods does not work
    12. Mapping MS Windows and UNIX Groups
    Features and Benefits
    Discussion
    Example Configuration
    Configuration Scripts
    Sample smb.conf add group script
    Script to configure Group Mapping
    Common Errors
    Adding Groups Fails
    Adding MS Windows Groups to MS Windows Groups Fails
    Adding Domain Users to the Power Users group
    13. 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
    Common Errors
    Users can not write to a public share
    I have set force user but Samba still makes root the owner of all the files I touch!
    MS Word with Samba changes owner of file
    14. File and Record Locking
    Features and Benefits
    Discussion
    Opportunistic Locking Overview
    Samba Opportunistic Locking Control
    Example Configuration
    MS Windows Opportunistic Locking 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
    15. 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 a IPC$ share deny
    NTLMv2 Security
    Upgrading Samba
    Common Errors
    Smbclient works on localhost, but the network is dead
    Why can users access home directories of other users?
    16. 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
    Inter-Domain 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
    17. Hosting a Microsoft Distributed File System tree on Samba
    Features and Benefits
    Common Errors
    18. Classical Printing Support
    Features and Benefits
    Technical Introduction
    What happens if you send a Job from a Client
    Printing Related Configuration Parameters
    Parameters Recommended for Use
    A simple Configuration to Print
    Verification of "Settings in Use" with testparm
    A little Experiment to warn you
    Extended Sample Configuration to Print
    Detailed Explanation of the Example's Settings
    The [global] Section
    The [printers] Section
    Any [my_printer_name] Section
    Print Commands
    Default Print Commands for various UNIX Print Subsystems
    Setting up your own Print Commands
    Innovations in Samba Printing since 2.2
    Client Drivers on Samba Server for Point'n'Print
    The [printer$] Section is removed from Samba 3
    Creating the [print$] Share
    Parameters in the [print$] Section
    Subdirectory Structure in [print$]
    Installing Drivers into [print$]
    Setting Drivers for existing Printers with a Client GUI
    Setting Drivers for existing Printers with +rpcclient
    Client Driver Install Procedure
    The first Client Driver Installation
    IMPORTANT! Setting Device Modes on new Printers
    Further Client Driver Install Procedures
    Always make first Client Connection as root or "printer admin"
    Other Gotchas
    Setting Default Print Options for the Client Drivers
    Supporting large Numbers of Printers
    Adding new Printers with the Windows NT APW
    Weird Error Message Cannot connect under a +different Name
    Be careful when assembling Driver Files
    Samba and Printer Ports
    Avoiding the most common Misconfigurations of the Client Driver
    The Imprints Toolset
    What is Imprints?
    Creating Printer Driver Packages
    The Imprints Server
    The Installation Client
    Add Network Printers at Logon 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 don't get access
    My printjobs get spooled into the spooling directory, but then get lost
    19. CUPS Printing Support in Samba 3.0
    Introduction
    Features and Benefits
    Overview
    Basic Configuration of CUPS support
    Linking of smbd with libcups.so
    Simple smb.conf Settings for CUPS
    More complex smb.conf Settings for +CUPS
    Advanced Configuration
    Central spooling vs. "Peer-to-Peer" printing
    CUPS/Samba as a "spooling-only" Print Server; "raw" printing +with Vendor Drivers on Windows Clients
    Driver Installation Methods on Windows Clients
    Explicitly enable "raw" printing for +application/octet-stream!
    Three familiar Methods for driver upload plus a new one
    Using CUPS/Samba in an advanced Way -- 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
    CUPS can use all 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
    Filter Requirements
    Prefilters
    pstops
    pstoraster
    imagetops and imagetoraster
    rasterto [printers specific]
    CUPS Backends
    cupsomatic/Foomatic -- how do they fit into the Picture?
    The Complete Picture
    mime.convs
    "Raw" printing
    "application/octet-stream" printing
    PostScript Printer Descriptions (PPDs) for non-PS Printers
    Difference between cupsomatic/foomatic-rip and +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 -- UNIX/Samba Print +Servers)
    From Windows Clients to a CUPS/Samba Print Server
    Samba receiving Jobfiles and passing them to CUPS
    Network PostScript RIP: CUPS Filters on Server -- clients use +PostScript Driver with CUPS-PPDs
    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
    Setting up CUPS for driver Download
    cupsaddsmb: the unknown Utility
    Prepare your smb.conf for cupsaddsmb
    CUPS Package of "PostScript Driver for WinNT/2k/XP"
    Recognize the different Driver Files
    Acquiring the Adobe Driver Files
    ESP Print Pro Package of "PostScript Driver for +WinNT/2k/XP"
    Caveats to be considered
    Benefits of using "CUPS PostScript Driver for +Windows NT/2k/XP" instead of 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
    What is required 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
    Auto-Deletion or Preservation of CUPS Spool Files
    CUPS Configuration Settings explained
    Pre-conditions
    Manual Configuration
    In Case of Trouble.....
    Printing from CUPS to Windows attached +Printers
    More CUPS filtering Chains
    Common Errors
    Win9x client can't install driver
    "cupsaddsmb" keeps asking for root password in + neverending loop
    "cupsaddsmb" gives "No PPD file for printer..." + message while PPD file is present
    Client can't connect to Samba printer
    Can't reconnect to Samba under new account + from Win2K/XP
    Avoid being connected to the Samba server as the + "wrong" user
    Upgrading to CUPS drivers from Adobe drivers on + NT/2K/XP clients gives problems
    Can't use "cupsaddsmb" on Samba server which is + a PDC
    Deleted Win2K printer driver is still shown
    Win2K/XP "Local Security + Policies"
    WinXP clients: "Administrator can not install + printers for all local users"
    "Print Change Notify" functions on + NT-clients
    WinXP-SP1
    Print options for all users can't be set on Win2K/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
    Printer named "lp" +intermittently swallows jobs and spits out completely different +ones
    Location of Adobe PostScript driver files necessary for "cupsaddsmb"
    An Overview of the CUPS Printing Processes
    20. Stackable VFS modules
    Features and Benefits
    Discussion
    Included modules
    audit
    extd_audit
    fake_perms
    recycle
    netatalk
    VFS modules available elsewhere
    DatabaseFS
    vscan
    21. Winbind: Use of Domain Accounts
    Features and Benefits
    Introduction
    What Winbind Provides
    Target Uses
    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
    22. Advanced Network Management
    Features and Benefits
    Remote Server Administration
    Remote Desktop Management
    Remote Management from NoMachines.Com
    Network Logon Script Magic
    Adding printers without user intervention
    Common Errors
    23. 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
    Samba Editreg Toolset
    Windows NT4/200x
    Samba PDC
    System Startup and Logon Processing Overview
    Common Errors
    Policy Does Not Work
    24. Desktop Profile Management
    Features and Benefits
    Roaming Profiles
    Samba Configuration for Profile Handling
    Windows Client Profile Configuration Information
    Sharing Profiles between W9x/Me and NT4/200x/XP workstations
    Profile Migration from Windows NT4/200x Server to Samba
    Mandatory profiles
    Creating/Managing Group Profiles
    Default Profile for Windows Users
    MS Windows 9x/Me
    MS Windows NT4 Workstation
    MS Windows 200x/XP
    Common Errors
    Setting up roaming profiles for just a few user's or group's?
    Can NOT use Roaming Profiles
    Changing the default profile
    25. 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
    26. 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 in one way
    Very Slow Network Connections
    Samba server name change problem
    27. Unicode/Charsets
    Features and Benefits
    What are charsets and unicode?
    Samba and charsets
    Conversion from old names
    Japanese charsets
    Common errors
    CP850.so can't be found
    28. Samba Backup Techniques
    Note
    Features and Benefits
    29. High Availability Options
    Note
    Prev Up Next
    Chapter 9. MS Windows Network Configuration Guide Home Chapter 10. Samba / MS Windows Network Browsing Guide
    diff --git a/docs/htmldocs/pam.html b/docs/htmldocs/pam.html index a0221b57e0..8edbdb26ca 100644 --- a/docs/htmldocs/pam.html +++ b/docs/htmldocs/pam.html @@ -1,6 +1,6 @@ -Chapter 25. PAM based Distributed Authentication
    Chapter 25. PAM based Distributed Authentication
    Prev Part III. Advanced Configuration Next

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

    +Chapter 25. PAM based Distributed Authentication

    Chapter 25. PAM based Distributed Authentication
    Prev Part III. Advanced Configuration Next

    Chapter 25. 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 you 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 +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. @@ -8,9 +8,9 @@ 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 require more than PAM configuration alone. Please refer to the Winbind chapter. -

    Features and Benefits

    -A number of Unix systems (eg: Sun Solaris), as well as the xxxxBSD family and Linux, +The use of Winbind require more than PAM configuration alone. Please refer to the Winbind chapter. +

    Features and Benefits

    +A number of UNIX systems (eg: 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 to use an alternative to the system password database (/etc/passwd) @@ -23,38 +23,38 @@ authentication/authorization infrastructure. PAM is configured either through o /etc/pam.conf (Solaris), or by editing individual 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 +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 centralised on a remote server.

    PAM support modules are available for: -

    /etc/passwd

    -

    - There are several PAM modules that interact with this standard Unix user +

    /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

    -

    +

    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

    -

    +

    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, Microsoft Active Directory. -

    NetWare Bindery

    -

    +

    NetWare Bindery:

    The pam_ncp_auth.so module allows authentication off any bindery enabled NetWare Core Protocol based server. -

    SMB Password

    -

    +

    SMB Password:

    This module, called pam_smbpass.so, will allow user authentication off the passdb backend that is configured in the Samba smb.conf file. -

    SMB Server

    -

    +

    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

    -

    +

    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

    -

    +

    RADIUS:

    There is a PAM RADIUS (Remote Access Dial-In User Service) authentication module. In most cases the administrator will need to locate the source code for this tool and compile and install it themselves. RADIUS protocols are @@ -67,12 +67,12 @@ of distributed samba domain controllers that can provide wide are network bandwi 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 the system administrator 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. @@ -87,32 +87,31 @@ 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 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 
-
-http://ftp.kernel.org/pub/linux/libs/pam The Official Linux-PAM home page.
+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
 
    
 
    
 Below, we explain the meaning of each of these tokens. The second (and more recently adopted)
 way of configuring Linux-PAM is via the contents of the /etc/pam.d/ directory.
 Once we have explained the meaning of the above tokens, we will describe this method.
-
    service-name
    -
    
+
    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', etc. .
 		
    
 		There is a special service-name, reserved for defining a default authentication mechanism. It has
 		the name `OTHER' and may be specified in either lower or upper case characters. Note, when there
 		is a module specified for a named service, the `OTHER' entries are ignored.
-		
    module-type
    -
    
+		
    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.
@@ -134,7 +133,7 @@ Once we have explained the meaning of the above tokens, we will describe this me
 			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'
 			based authentication (auth) module-type.
-			
    control-flag
    -
    
+			
    control-flag:
    
 		The control-flag is used to indicate how the PAM library will react to the success or failure of the
 		module it is associated with. Since modules can be stacked (modules of the same type execute in series,
 		one after another), the control-flags determine the relative importance of each module. The application
@@ -178,9 +177,9 @@ Once we have explained the meaning of the above tokens, we will describe this me
 		The more elaborate (newer) syntax is much more specific and gives the administrator a great deal of control
 		over how the user is authenticated. This form of the control flag is delimited with square brackets and
 		consists of a series of value=action tokens:
-		
    -		[value1=action1 value2=action2 ...]
-		
    
+		
    +[value1=action1 value2=action2 ...]
+
    
 		Here, value1 is one of the following return values: success; open_err; symbol_err; service_err;
 		system_err; buf_err; perm_denied; auth_err; cred_insufficient; authinfo_unavail; user_unknown; maxtries;
 		new_authtok_reqd; acct_expired; session_err; cred_unavail; cred_expired; cred_err; no_module_data; conv_err;
@@ -235,7 +234,7 @@ Once we have explained the meaning of the above tokens, we will describe this me
 		[ ... value=action ... ] control syntax, it is possible for an application to be configured
 		to support binary prompts with compliant clients, but to gracefully fall over into an alternative authentication
 		mode for older, legacy, applications.
-		
    module-path
    -
    
+		
    module-path:
    
 		The path-name of the dynamically loadable object file; the pluggable module itself. If the first character of the
 		module path is `/', it is assumed to be a complete path. If this is not the case, the given module path is appended
 		to the default module path: /lib/security (but see the notes above).
@@ -246,7 +245,7 @@ Once we have explained the meaning of the above tokens, we will describe this me
 		to syslog(3). For a list of generic options see the next section.
 		
    
 		Note, if you wish to include spaces in an argument, you should surround that argument with square brackets. For example:
-		
    +		
     squid auth required pam_mysql.so user=passwd_query passwd=mada \
         db=eminence [query=select user_name from internet_service where \
                      user_name='%u' and password=PASSWORD('%p') and \
@@ -254,19 +253,19 @@ squid auth required pam_mysql.so user=passwd_query passwd=mada \
 
    
 		Note, when using this convention, you can include `[' characters inside the string, and if you wish to include a `]'
 		character inside the string that will survive the argument parsing, you should use `\['. In other words:
-		
    +		
     [..[..\]..]    -->   ..[..]..
 
    
 		Any line in (one of) the configuration file(s), 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 been uncommented is probably not usable as 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
 #
@@ -281,10 +280,10 @@ session      required    pam_pwdb.so
 # session    optional    pam_lastlog.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 -

    +
     pam_access.so    pam_ftp.so          pam_limits.so     
 pam_ncp_auth.so  pam_rhosts_auth.so  pam_stress.so     
 pam_cracklib.so  pam_group.so        pam_listfile.so   
@@ -308,7 +307,7 @@ hashes. This database is stored in either
 /usr/local/samba/private/smbpasswd, 
 /etc/samba/smbpasswd, or in 
 /etc/samba.d/smbpasswd, depending on the 
-Samba implementation for your Unix/Linux system. The 
+Samba implementation for your UNIX/Linux system. The 
 pam_smbpass.so module is provided by 
 Samba version 2.2.1 or later. It can be compiled by specifying the 
 --with-pam_smbpass options when running Samba's
@@ -316,7 +315,7 @@ Samba version 2.2.1 or later. It can be compiled by specifying the
 on the pam_smbpass module, see the documentation
 in the source/pam_smbpass directory of the Samba 
 source distribution.
-
    +
     #%PAM-1.0
 # The PAM configuration file for the `login' service
 #
@@ -327,7 +326,7 @@ password    required    pam_smbpass.so nodelay
 
    
 The following is the PAM configuration file for a particular 
 Linux system. The default condition uses pam_pwdb.so.
-
    +
     #%PAM-1.0
 # The PAM configuration file for the `samba' service
 #
@@ -341,7 +340,7 @@ smbpasswd database even for basic samba authentication. Such a
 decision could also be made for the passwd program and would 
 thus allow the smbpasswd passwords to be changed using the passwd 
 program.
-
    +
     #%PAM-1.0
 # The PAM configuration file for the `samba' service
 #
@@ -360,24 +359,24 @@ 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 makes trade-offs, so you may want examine the 
 PAM documentation for further helpful information.
-

    smb.conf PAM Configuration

    -There is an option in smb.conf called obey pam restrictions. +

    smb.conf PAM Configuration

    + There is an option in smb.conf called obey pam restrictions. The following is from the on-line help for this option in SWAT;

    -When Samba-3 is configured to enable PAM support (i.e. +When Samba is configured to enable PAM support (i.e. --with-pam), this parameter will control whether or not Samba should obey PAM's account and session management directives. The default behavior is to use PAM for clear text authentication only and to ignore any account or session management. Note that Samba always ignores PAM for authentication in the case of -encrypt passwords = yes. +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 users credentials acceptable to the platform. -Unix requires the provision of a user identifier (UID) as well as a group identifier (GID). +UNIX requires the provision of a user identifier (UID) as well as a group identifier (GID). These are both simple integer type numbers that are obtained from a password backend such as /etc/passwd.

    @@ -401,7 +400,7 @@ Microsoft Active Directory Service (ADS) in so far as reduction of wide area net 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 which can be used on conforming systems to keep the smbpasswd (Samba password) database in sync with the unix password file. PAM (Pluggable Authentication Modules) is an API supported @@ -414,24 +413,23 @@ concerned about the presence of suid root binaries on your system, it is recommended that you use pam_winbind instead.

    Options recognized by this module are as follows: -

    Table 25.1. Options recognized by pam_smbpass

    debuglog more debugging info
    auditlike debug, but also logs unknown usernames
    use_first_passdon't prompt the user for passwords; take them from PAM_ items instead
    try_first_passtry to get the password from a previous PAM module, fall back to prompting the user
    use_authtoklike try_first_pass, but *fail* if the new PAM_AUTHTOK has not been previously set. (intended for stacking password modules only)
    not_set_passdon't make passwords used by this module available to other modules.
    nodelaydon't insert ~1 second delays on authentication failure.
    nulloknull passwords are allowed.
    nonullnull passwords are not allowed. Used to override the Samba configuration.
    migrateonly meaningful in an "auth" context; used to update smbpasswd file with a password used for successful authentication.
    smbconf=filespecify an alternate path to the smb.conf file.

    +

    Table 25.1. Options recognized by pam_smbpass

    debuglog more debugging info
    auditlike debug, but also logs unknown usernames
    use_first_passdon't prompt the user for passwords; take them from PAM_ items instead
    try_first_passtry to get the password from a previous PAM module, fall back to prompting the user
    use_authtoklike try_first_pass, but *fail* if the new PAM_AUTHTOK has not been previously set. (intended for stacking password modules only)
    not_set_passdon't make passwords used by this module available to other modules.
    nodelaydon't insert ~1 second delays on authentication failure.
    nulloknull passwords are allowed.
    nonullnull passwords are not allowed. Used to override the Samba configuration.
    migrateonly meaningful in an "auth" context; used to update smbpasswd file with a password used for successful authentication.
    smbconf=filespecify an alternate path to the smb.conf file.

    -Thanks go to the following people: -

    Andrew Morgan, for providing the Linux-PAM - framework, without which none of this would have happened
    Christian Gafton and Andrew Morgan again, for the - pam_pwdb module upon which pam_smbpass was originally based
    Luke Leighton for being receptive to the idea, +

    • Andrew Morgan, for providing the Linux-PAM + framework, without which none of this would have happened

    • Christian Gafton and Andrew Morgan again, for the + pam_pwdb module upon which pam_smbpass was originally based

    • Luke Leighton for being receptive to the idea, and for the occasional good-natured complaint about the project's status - that keep me working on it :)

    . + that keep me working on it :)

    .

    The following are examples of the use of pam_smbpass.so in the format of Linux /etc/pam.d/ files structure. Those wishing to implement this tool on other platforms will need to adapt this appropriately. -

    Password Synchronisation Configuration

    +

    Password Synchronisation Configuration

    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. Useful when an expired password might be changed by an application (such as ssh). -

    +
     #%PAM-1.0
 # password-sync
 #
@@ -442,13 +440,13 @@ 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

    A sample PAM configuration that 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: password migration takes place when users ftp in, login using ssh, pop their mail, etc. -

    +
     #%PAM-1.0
 # password-migration
 #
@@ -461,11 +459,11 @@ 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

    A sample PAM configuration for a 'mature' smbpasswd installation. private/smbpasswd is fully populated, and we consider it an error if -the smbpasswd doesn't exist or doesn't match the Unix password. -

    +the smbpasswd doesn't exist or doesn't match the UNIX password.
+
     #%PAM-1.0
 # password-mature
 #
@@ -476,11 +474,11 @@ 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

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

    +
     #%PAM-1.0
 # kdc-pdc
 #
@@ -492,13 +490,15 @@ 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 a very fickle and sensitive to configuration glitches. Here we look at a few cases from the Samba mailing list. -

    pam_winbind problem

    - I have the following PAM configuration: +

    pam_winbind problem

    + “ + I have the following PAM configuration: + ”

    -

    +
     auth required /lib/security/pam_securetty.so
 auth sufficient /lib/security/pam_winbind.so
 auth sufficient /lib/security/pam_unix.so use_first_pass nullok
@@ -508,15 +508,58 @@ account required /lib/security/pam_stack.so service=system-auth
 account required /lib/security/pam_winbind.so
 password required /lib/security/pam_stack.so service=system-auth
 
    
-
    
+	
    
+		“
 	When I open a new console with [ctrl][alt][F1], then I cant log in with my user "pitie".
 	I've tried with user "scienceu+pitie" also.
+”
 	
    
-	Answer: The problem may lie with your inclusion of pam_stack.so
+		The problem may lie with your inclusion of pam_stack.so
 	service=system-auth. That file often contains a lot of stuff that may
 	duplicate what you're already doing. Try commenting out the pam_stack lines
 	for auth and account and see if things work. If they do, look at
 	/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.
-
    Prev Up Next
    Chapter 24. Desktop Profile Management Home Chapter 26. Integrating MS Windows networks with Samba
    +

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

    +root# wbinfo -u
+MIDEARTH+maryo
+MIDEARTH+jackb
+MIDEARTH+ameds
+...
+MIDEARTH+root
+
+root# wbinfo -g
+MIDEARTH+Domain Users
+MIDEARTH+Domain Admins
+MIDEARTH+Domain Guests
+...
+MIDEARTH+Accounts
+
+root# getent passwd
+root:x:0:0:root:/root:/bin/bash
+bin:x:1:1:bin:/bin:/bin/bash
+...
+maryo:x:15000:15003:Mary Orville:/home/MIDEARTH/maryo:/bin/false
+

    + “ + But the following command just fails: +” +

    +root# chown 'maryo' a_file
+chown: `maryo': invalid user
+

    +“ +This is driving me nuts! What can be wrong? +” +

    + Your system is likely running nscd, the name service + caching daemon. Shut it down, do NOT restart it! You will find your problem resolved. +

    Prev Up Next
    Chapter 24. Desktop Profile Management Home Chapter 26. Integrating MS Windows networks with Samba
    diff --git a/docs/htmldocs/passdb.html b/docs/htmldocs/passdb.html index 2c68f50c87..4d5432fd70 100644 --- a/docs/htmldocs/passdb.html +++ b/docs/htmldocs/passdb.html @@ -1,26 +1,27 @@ -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

    Gerald (Jerry) Carter

    Samba Team

    Jeremy Allison

    Samba Team

    John H. Terpstra

    Samba Team

    Olivier (lem) Lemaire

    IDEALX

    May 24, 2003

    Table of Contents

    Features and Benefits
    Technical Information
    Important Notes About Security
    Mapping User Identifiers between MS Windows and Unix
    Account Management Tools
    The smbpasswd Command
    The pdbedit Command
    Password Backends
    Plain Text
    smbpasswd - Encrypted Password Database
    tdbsam
    ldapsam
    MySQL
    XML
    Common Errors
    Users can not logon - Users not in Samba SAM
    Users are being added to the wrong backend database
    auth methods does not work

    -Samba-3 implements a new capability to work concurrently with multiple account backends. -The possible new combinations of password backends allows Samba-3 a degree of flexibility +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

    Gerald (Jerry) Carter

    Samba Team

    Jeremy Allison

    Samba Team

    John H. Terpstra

    Samba Team

    Olivier (lem) Lemaire

    IDEALX

    May 24, 2003

    Table of Contents

    Features and Benefits
    Backwards Compatibility Backends
    New Backends
    Technical Information
    Important Notes About Security
    Mapping User Identifiers between MS Windows and UNIX
    Mapping Common UIDs/GIDs on Distributed Machines
    Account Management Tools
    The smbpasswd Command
    The pdbedit Command
    Password Backends
    Plain Text
    smbpasswd - Encrypted Password Database
    tdbsam
    ldapsam
    MySQL
    XML
    Common Errors
    Users can not logon
    Users being added to wrong backend database
    auth methods does not work

    +Samba 3 implements a new capability to work concurrently with multiple account backends. +The possible new combinations of password backends allows Samba 3 a degree of flexibility and scalability that previously could be achieved only with MS Windows Active Directory. This chapter describes the new functionality and how to get the most out of it.

    In the course of development of Samba-3, a number of requests were received to provide the ability to migrate MS Windows NT4 SAM accounts to Samba-3 without the need to provide -matching Unix/Linux accounts. We called this the Non Unix Accounts (NUA) +matching UNIX/Linux accounts. We called this the Non UNIX Accounts (NUA) capability. The intent was that an administrator could decide to use the tdbsam -backend and by simply specifying "passdb backend = tdbsam_nua, guest" -this would allow Samba-3 to implement a solution that did not use Unix accounts per se. Late +backend and by simply specifying passdb backend = tdbsam_nua +this would allow Samba-3 to implement a solution that did not use UNIX accounts per se. Late in the development cycle, the team doing this work hit upon some obstacles that prevents this solution from being used. Given the delays with Samba-3 release a decision was made to NOT deliver this functionality until a better method of recognising NT Group SIDs from NT User SIDs could be found. This feature may thus return during the life cycle for the Samba-3 series.

    Note

    -Samba-3.0.0 does NOT support Non-Unix Account (NUA) operation. -

    Features and Benefits

    +Samba-3 does NOT support Non-UNIX Account (NUA) operation for user accounts. +Samba-3 does support NUA operation for machine accounts. +

    Features and Benefits

    Samba-3 provides for complete backwards compatibility with Samba-2.2.x functionality as follows: -

    Backwards Compatibility Backends

    Plain Text:

    - This option uses nothing but the Unix/Linux /etc/passwd +

    Backwards Compatibility Backends

    Plain Text:

    + This option uses nothing but the UNIX/Linux /etc/passwd style back end. On systems that have PAM (Pluggable Authentication Modules) support all PAM modules are supported. The behaviour is just as it was with Samba-2.2.x, and the protocol limitations imposed by MS Windows clients @@ -42,13 +43,9 @@ as follows: This option is provided primarily as a migration tool, although there is no reason to force migration at this time. Note that this tool will eventually be deprecated. -

    +

    New Backends

    Samba-3 introduces the following new password backend capabilities: -

    New Backends

    guest:

    - This is always required as the last backend specified. - It provides the ability to handle guest account requirements for access to - resources like IPC$ which is used for browsing. -

    tdbsam:

    +

    tdbsam:

    This backend provides a rich database backend for local servers. This backend is NOT suitable for multiple domain controller (ie: PDC + one or more BDC) installations. @@ -90,10 +87,7 @@ Samba-3 introduces the following new password backend capabilities: The xmlsam option can be useful for account migration between database backends or backups. Use of this tool will allow the data to be edited before migration into another backend format. -

    nisplussam:

    - The NIS+ based passdb backend. Takes name NIS domain as an - optional argument. Only works with Sun NIS+ servers. -

    Technical Information

    +

    Technical Information

    Old windows clients send plain text passwords over the wire. Samba can check these passwords by crypting them and comparing them to the hash stored in the unix user database.

    @@ -108,10 +102,10 @@ Samba-3 introduces the following new password backend capabilities: In addition to differently encrypted passwords, windows also stores certain data for each user that is not stored in a unix user database. e.g: workstations the user may logon from, the location where the users' profile is stored, and so on. Samba retrieves and stores this - information using a passdb backend. Commonly available backends are LDAP, plain text + information using a passdb backend. Commonly available backends are LDAP, plain text file, MySQL and nisplus. For more information, see the man page for smb.conf regarding the - passdb backend parameter. -

    Important Notes About Security

    + passdb backend parameter. +

    Figure 11.1. IDMAP

    IDMAP

    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 @@ -135,12 +129,12 @@ Samba-3 introduces the following new password backend capabilities:

    The following versions of MS 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 [se]
    Windows Me

    Note

    +

    • MS DOS Network client 3.0 with the basic network redirector installed

    • Windows 95 with the network redirector update installed

    • Windows 98 [se]

    • Windows Me

    Note

    MS Windows XP Home does not have facilities to become a domain member and it can not 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

    +

    • Windows NT 3.5x

    • Windows NT 4.0

    • Windows 2000 Professional

    • Windows 200x Server/Advanced Server

    • Windows XP Professional

    All current release 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. @@ -153,7 +147,7 @@ Samba-3 introduces the following new password backend capabilities: (broken) only the cached (encrypted) password will be sent to the resource server to affect a 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

    • Plain text passwords are not passed across +

      Advantages of Encrypted Passwords

      • Plain text passwords are not passed across the network. Someone using a network sniffer cannot just record passwords going to the SMB server.

      • Plain text passwords are not stored anywhere in memory or on disk.

      • WinNT doesn't like talking to a server @@ -164,32 +158,44 @@ Samba-3 introduces the following new password backend capabilities: only things 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

      • Plain text passwords are not kept + operation.

      Advantages of non-encrypted passwords

      • Plain text passwords are not kept on disk, and are NOT cached in memory.

      • Uses same password file as other unix services such as login and ftp

      • Use of other services (such as telnet and ftp) which send plain text passwords over the net, so sending them for SMB - isn't such a big deal.

    Mapping User Identifiers between MS Windows and Unix

    - Every operation in Unix/Linux requires a user identifier (UID), just as in + isn't such a big deal.

    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. + two means for mapping an MS Windows user to a UNIX/Linux UID.

    Firstly, all Samba SAM (Security Account Manager database) accounts require - a Unix/Linux UID that the account will map to. As users are added to the account - information database, Samba-3 will call the add user script - interface to add the account to the Samba host OS. In essence, all accounts in + 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 affect Windows SID to Unix UID mapping is via the + The second way to affect Windows SID to UNIX UID mapping is via the idmap uid, 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 SAM server. -

    Account Management Tools

    -Samba-3 provides two (2) tools for management of User and machine accounts. These tools are +

    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 (eg: 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. Administrators should NOT set this + parameter except when an LDAP based passdb backend is in use. An example of use is: +

    +

    Example 11.1. 

    [global]
    idmap backend = ldapsam://ldap-server.quenya.org:636

    +

    Account Management Tools

    +Samba provides two (2) tools for management of User and machine accounts. These tools are called smbpasswd and pdbedit. A third tool is under development but is NOT expected to ship in time for Samba-3.0.0. The new tool will be a TCL/TK GUI tool that looks much like the MS Windows NT4 Domain User Manager - hopefully this will be announced in time for the Samba-3.0.1 release. -

    The smbpasswd Command

    +

    The smbpasswd Command

    The smbpasswd utility is a utility similar to the passwd or yppasswd programs. It maintains the two 32 byte password fields in the passdb backend. @@ -203,19 +209,19 @@ be announced in time for the Samba-3.0.1 release. 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

    +

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

    - 

    -		$ smbpasswd
-		Old SMB password: secret
-

    +

    +$ smbpasswd
+Old SMB password: secret
+

    For secret type old value here - or hit return if there was no old password - 

    -		New SMB Password: new secret
-		Repeat New SMB Password: new secret
-

    +

    +New SMB Password: new secret
+Repeat New SMB Password: new secret
+

    If the old value does not match the current value stored for that user, or the two new values do not match each other, then the password will not be changed. @@ -235,10 +241,10 @@ be announced in time for the Samba-3.0.1 release.

    For more details on using smbpasswd refer to the man page (the definitive reference). -

    The pdbedit Command

    +

    The pdbedit Command

    pdbedit is a tool that can be used only by root. It is used to manage the passdb backend. pdbedit can be used to: -

    add, remove or modify user accounts
    listing user accounts
    migrate user accounts

    +

    • add, remove or modify user accounts

    • listing user accounts

    • migrate user accounts

    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 super set of them. @@ -250,50 +256,60 @@ be announced in time for the Samba-3.0.1 release. The following is an example of the user account information that is stored in a tdbsam password backend. This listing was produced by running: 

    -		$ pdbedit -Lv met
-		Unix username:        met
-		NT username:
-		Account Flags:        [UX         ]
-		User SID:             S-1-5-21-1449123459-1407424037-3116680435-2004
-		Primary Group SID:    S-1-5-21-1449123459-1407424037-3116680435-1201
-		Full Name:            Melissa E Terpstra
-		Home Directory:       \\frodo\met\Win9Profile
-		HomeDir Drive:        H:
-		Logon Script:         scripts\logon.bat
-		Profile Path:         \\frodo\Profiles\met
-		Domain:               MIDEARTH
-		Account desc:
-		Workstations:         melbelle
-		Munged dial:
-		Logon time:           0
-		Logoff time:          Mon, 18 Jan 2038 20:14:07 GMT
-		Kickoff time:         Mon, 18 Jan 2038 20:14:07 GMT
-		Password last set:    Sat, 14 Dec 2002 14:37:03 GMT
-		Password can change:  Sat, 14 Dec 2002 14:37:03 GMT
-		Password must change: Mon, 18 Jan 2038 20:14:07 GMT
-

    Password Backends

    -Samba-3 offers the greatest flexibility in backend account database design of any SMB/CIFS server +$ pdbedit -Lv met +UNIX username: met +NT username: +Account Flags: [UX ] +User SID: S-1-5-21-1449123459-1407424037-3116680435-2004 +Primary Group SID: S-1-5-21-1449123459-1407424037-3116680435-1201 +Full Name: Melissa E Terpstra +Home Directory: \\frodo\met\Win9Profile +HomeDir Drive: H: +Logon Script: scripts\logon.bat +Profile Path: \\frodo\Profiles\met +Domain: MIDEARTH +Account desc: +Workstations: melbelle +Munged dial: +Logon time: 0 +Logoff time: Mon, 18 Jan 2038 20:14:07 GMT +Kickoff time: Mon, 18 Jan 2038 20:14:07 GMT +Password last set: Sat, 14 Dec 2002 14:37:03 GMT +Password can change: Sat, 14 Dec 2002 14:37:03 GMT +Password must change: Mon, 18 Jan 2038 20:14:07 GMT +

    + The pdbedit tool allows migration of authentication (account) + databases from one backend to another. For example: To migrate accounts from an + old smbpasswd database to a tdbsam + backend: +

    1. + Set the passdb backend = tdbsam, smbpasswd. +

    2. + Execute: +

      +root# pdbedit -i smbpassed -e tdbsam
+

      +

    3. + Now remove the smbpasswd from the passdb backend + configuration in smb.conf. +

    Password Backends

    +Samba offers the greatest flexibility in backend account database design of any SMB/CIFS server technology available today. The flexibility is immediately obvious as one begins to explore this capability.

    It is possible to specify not only multiple different password backends, but even multiple backends of the same type. For example, to use two different tdbsam databases:

    -

    -[globals]
-		passdb backend = tdbsam:/etc/samba/passdb.tdb, \
-		tdbsam:/etc/samba/old-passdb.tdb, guest
-

    -

    Plain Text

    +

    passdb backend = tdbsam:/etc/samba/passdb.tdb, tdbsam:/etc/samba/old-passdb.tdb

    +

    Plain Text

    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. eg: On Linux systems that is done via PAM. -

    smbpasswd - Encrypted Password Database

    - Traditionally, when configuring encrypt - passwords = yes in Samba's smb.conf file, user account +

    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 very large numbers of users (counted @@ -319,10 +335,10 @@ backends of the same type. For example, to use two different tdbsam databases: is commonly referred to as the samdb interface (previously this was called the passdb API, and is still so named in the Samba CVS trees).

    - Samba-3 provides an enhanced set of passdb backends that overcome the deficiencies + Samba provides an enhanced set of passdb backends that overcome the deficiencies of the smbpasswd plain text database. These are tdbsam, ldapsam, and xmlsam. Of these ldapsam will be of most interest to large corporate or enterprise sites. -

    tdbsam

    Samba can store user and machine account data in a "TDB" (Trivial Database). +

    tdbsam

    Samba can store user and machine account data in a "TDB" (Trivial Database). Using this backend doesn't require any additional configuration. This backend is recommended for new installations that do not require LDAP.

    @@ -330,7 +346,7 @@ backends of the same type. For example, to use two different tdbsam databases: that have 250 or more users. Additionally, tdbsam is not capable of scaling for use in sites that require PDB/BDC implementations that requires replication of the account database. Clearly, for reason of scalability, the use of ldapsam should be encouraged. -

    ldapsam

    +

    ldapsam

    There are a few points to stress that the ldapsam does not provide. The LDAP support referred to in the this documentation does not include:

    Two additional Samba resources which 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 group in such a Samba-LDAP Domain Controller configuration. -

    Supported LDAP Servers

    +

    Supported LDAP Servers

    The LDAP ldapsam code has been developed and tested using the OpenLDAP 2.0 and 2.1 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 Bug reporting facility. -

    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.0 in examples/LDAP/samba.schema. The sambaSamAccount objectclass is given here: 

    -objectclass ( 1.3.6.1.4.1.7165.2.2.3 NAME 'sambaSamAccount' SUP top AUXILIARY
-    DESC 'Samba Auxiliary Account'
-    MUST ( uid $ rid )
-    MAY  ( cn $ lmPassword $ ntPassword $ pwdLastSet $ logonTime $
-           logoffTime $ kickoffTime $ pwdCanChange $ pwdMustChange $ acctFlags $
-           displayName $ smbHome $ homeDrive $ scriptPath $ profilePath $
-           description $ userWorkstations $ primaryGroupID $ domain ))
+objectclass ( 1.3.6.1.4.1.7165.2.2.6 NAME 'sambaSamAccount' SUP top AUXILIARY
+    DESC 'Samba 3.0 Auxiliary SAM Account'
+    MUST ( uid $ sambaSID )
+    MAY  ( cn $ sambaLMPassword $ sambaNTPassword $ sambaPwdLastSet $
+          sambaLogonTime $ sambaLogoffTime $ sambaKickoffTime $
+          sambaPwdCanChange $ sambaPwdMustChange $ sambaAcctFlags $
+          displayName $ sambaHomePath $ sambaHomeDrive $ sambaLogonScript $
+          sambaProfilePath $ description $ sambaUserWorkstations $
+          sambaPrimaryGroupSID $ sambaDomainName ))

    The samba.schema file has been formatted for OpenLDAP 2.0/2.1. @@ -398,7 +416,7 @@ objectclass ( 1.3.6.1.4.1.7165.2.2.3 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 @@ -432,7 +450,7 @@ include /etc/openldap/schema/nis.schema like in the following example, to speed up searches made on sambaSamAccount objectclasses (and possibly posixAccount and posixGroup as well).

    -

    +
     # Indices to maintain
 ## required by OpenLDAP
 index objectclass             eq
@@ -459,7 +477,7 @@ index   default               sub
 		Create the new index by executing:
 		
    
 
    -./sbin/slapindex -f slapd.conf
+root# ./sbin/slapindex -f slapd.conf
 
    
 
    
 		Remember to restart slapd after making these changes:
@@ -467,34 +485,34 @@ index   default               sub
 
     root# /etc/init.d/slapd restart
 
    
-

    Initialise the LDAP database

    +

    Initialise 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 (ie: Your DNS entries, etc.).

    -

    +
     # Organization for Samba Base
-dn: dc=plainjoe,dc=org
+dn: dc=quenya,dc=org
 objectclass: dcObject
 objectclass: organization
-dc: plainjoe
-o: Terpstra Org Network
+dc: quenya
+o: Quenya Org Network
 description: The Samba-3 Network LDAP Example
 
 # Organizational Role for Directory Management
-dn: cn=Manager,dc=plainjoe,dc=org
+dn: cn=Manager,dc=quenya,dc=org
 objectclass: organizationalRole
 cn: Manager
 description: Directory Manager
 
 # Setting up container for users
-dn: ou=People,dc=plainjoe,dc=org
+dn: ou=People,dc=quenya,dc=org
 objectclass: top
 objectclass: organizationalUnit
 ou: People
 
 # Setting up admin handle for People OU
-dn: cn=admin,ou=People,dc=plainjoe,dc=org
+dn: cn=admin,ou=People,dc=quenya,dc=org
 cn: admin
 objectclass: top
 objectclass: organizationalRole
@@ -516,70 +534,39 @@ userPassword: {SSHA}c3ZM9tBaBo9autm1dL3waDS21+JSfQVz
 		
    Note
    
 		Before Samba can access the LDAP server you need to store the LDAP admin password
 		into the Samba-3 secrets.tdb database by:
-		
    -root#  smbpasswd -w secret
-		
    
-

    Configuring Samba

    +

    +root# smbpasswd -w secret
+

    +

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

    +

    LDAP related smb.conf options: + passdb backend = ldapsam:url, + ldap ssl, + ldap admin dn, + ldap suffix, + ldap filter, + ldap machine suffix, + ldap user suffix, + ldap delete dn, + ldap passwd sync, + ldap trust ids. +

    These are described in the smb.conf man page and so will not be repeated here. However, a sample smb.conf file for use with an LDAP directory could appear as

    -

    -## /usr/local/samba/lib/smb.conf
-[global]
-     security = user
-     encrypt passwords = yes
-
-     netbios name = TASHTEGO
-     workgroup = NARNIA
-
-     # ldap related parameters
-
-     # define the DN to use when binding to the directory servers
-     # The password for this DN is not stored in smb.conf.  Rather it
-     # must be set by using 'smbpasswd -w secretpw' to store the
-     # passphrase in the secrets.tdb file.  If the "ldap admin dn" values
-     # change, this password will need to be reset.
-     ldap admin dn = "cn=Samba Manager,ou=people,dc=samba,dc=org"
-
-     # Define the SSL option when connecting to the directory
-     # ('off', 'start tls', or 'on' (default))
-     ldap ssl = start tls
-
-     # syntax: passdb backend = ldapsam:ldap://server-name[:port]
-     passdb backend = ldapsam:ldap://funball.samba.org, guest
-
-     # smbpasswd -x delete the entire dn-entry
-     ldap delete dn = no
-
-     # the machine and user suffix added to the base suffix
-     # wrote WITHOUT quotes. NULL suffixes by default
-     ldap user suffix = ou=People
-     ldap machine suffix = ou=Systems
-
-     # Trust unix account information in LDAP
-     #  (see the smb.conf manpage for details)
-     ldap trust ids = Yes
-
-     # specify the base DN to use when searching the directory
-     ldap suffix = "ou=people,dc=samba,dc=org"
-
-     # generally the default ldap search filter is ok
-     # ldap filter = "(&(uid=%u)(objectclass=sambaSamAccount))"
-

    -

    Accounts and Groups management

    +

    Example 11.2. Configuration with LDAP

    [global]
    security = user
    encrypt passwords = yes
    netbios name = TASHTEGO
    workgroup = NARNIA
    # ldap related parameters
    # define the DN to use when binding to the directory servers
    # The password for this DN is not stored in smb.conf. Rather it
    # must be set by using 'smbpasswd -w secretpw' to store the
    # passphrase in the secrets.tdb file. If the "ldap admin dn" values
    # change, this password will need to be reset.
    ldap admin dn = "cn=Samba Manager,ou=people,dc=samba,dc=org"
    # Define the SSL option when connecting to the directory
    # ('off', 'start tls', or 'on' (default))
    ldap ssl = start tls
    # syntax: passdb backend = ldapsam:ldap://server-name[:port]
    passdb backend = ldapsam:ldap://funball.samba.org
    # smbpasswd -x delete the entire dn-entry
    ldap delete dn = no
    # the machine and user suffix added to the base suffix
    # wrote WITHOUT quotes. NULL suffixes by default
    ldap user suffix = ou=People
    ldap machine suffix = ou=Systems
    # Trust unix account information in LDAP
    # (see the smb.conf manpage for details)
    ldap trust ids = Yes
    # specify the base DN to use when searching the directory
    ldap suffix = "ou=people,dc=samba,dc=org"
    # generally the default ldap search filter is ok
    ldap filter = "(&(uid=%u)(objectclass=sambaSamAccount))"

    +

    Accounts and Groups management

    As users accounts are managed through the sambaSamAccount objectclass, you should modify your existing administration tools to deal with sambaSamAccount attributes.

    Machines accounts are managed with the sambaSamAccount objectclass, just like users accounts. However, it's up to you to store those accounts in a different tree of your LDAP namespace: you should use - "ou=Groups,dc=plainjoe,dc=org" to store groups and - "ou=People,dc=plainjoe,dc=org" to store users. Just configure your + "ou=Groups,dc=quenya,dc=org" to store groups and + "ou=People,dc=quenya,dc=org" to store users. Just configure your NSS and PAM accordingly (usually, in the /etc/ldap.conf configuration file).

    @@ -587,7 +574,7 @@ userPassword: {SSHA}c3ZM9tBaBo9autm1dL3waDS21+JSfQVz 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). -

    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 lmPassword or @@ -598,13 +585,13 @@ userPassword: {SSHA}c3ZM9tBaBo9autm1dL3waDS21+JSfQVz on the details of LM/NT password hashes, refer to the Account Information Database section of this chapter.

      - To remedy the first security issue, the ldap ssl smb.conf parameter defaults - to require an encrypted session (ldap ssl = on) using + 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 is possible to use the use the StartTLS LDAP extended operation in the place of LDAPS. In either case, you are strongly discouraged to disable this security - (ldap ssl = off). + (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 @@ -617,84 +604,83 @@ userPassword: {SSHA}c3ZM9tBaBo9autm1dL3waDS21+JSfQVz 

       ## allow the "ldap admin dn" access, but deny everyone else
 access to attrs=lmPassword,ntPassword
-     by dn="cn=Samba Admin,ou=people,dc=plainjoe,dc=org" write
+     by dn="cn=Samba Admin,ou=people,dc=quenya,dc=org" write
      by * none

      -

    LDAP special attributes for sambaSamAccounts

    +

    LDAP special attributes for sambaSamAccounts

    The sambaSamAccount objectclass is composed of the following attributes:

    -

    Table 11.1. Attributes in the sambaSamAccount objectclass (LDAP)

    lmPasswordthe LANMAN password 16-byte hash stored as a character - representation of a hexadecimal string.
    ntPasswordthe NT password hash 16-byte stored as a character - representation of a hexadecimal string.
    pwdLastSetThe integer time in seconds since 1970 when the - lmPassword and ntPassword attributes were last set. -
    acctFlagsstring of 11 characters surrounded by square brackets [] +

    Table 11.1. Attributes in the sambaSamAccount objectclass (LDAP)

    sambaLMPasswordthe LANMAN password 16-byte hash stored as a character +representation of a hexadecimal string.
    sambaNTPasswordthe NT password hash 16-byte stored as a character + representation of a hexadecimal string.
    sambaPwdLastSetThe integer time in seconds since 1970 when the + sambaLMPassword and sambaNTPassword attributes were last set. +
    sambaAcctFlagsstring of 11 characters surrounded by square brackets [] representing account flags such as U (user), W(workstation), X(no password expiration), I(Domain trust account), H(Home dir required), S(Server trust account), - and D(disabled).
    logonTimeInteger value currently unused
    logoffTimeInteger value currently unused
    kickoffTimeInteger value currently unused
    pwdCanChangeInteger value currently unused
    pwdMustChangeInteger value currently unused
    homeDrivespecifies the drive letter to which to map the - UNC path specified by homeDirectory. The drive letter must be specified in the form "X:" + and D(disabled).
    sambaLogonTimeInteger value currently unused
    sambaLogoffTimeInteger value currently unused
    sambaKickoffTimeInteger value currently unused
    sambaPwdCanChangeInteger value currently unused
    sambaPwdMustChangeInteger value currently unused
    sambaHomeDrivespecifies the drive letter to which to map the + UNC path specified by sambaHomePath. The drive letter must be specified in the form "X:" where X is the letter of the drive to map. Refer to the "logon drive" parameter in the - smb.conf(5) man page for more information.
    scriptPathThe scriptPath property specifies the path of + smb.conf(5) man page for more information.
    sambaLogonScriptThe sambaLogonScript property specifies the path of the user's logon script, .CMD, .EXE, or .BAT file. The string can be null. The path - is relative to the netlogon share. Refer to the "logon script" parameter in the - smb.conf(5) man page for more information.
    profilePathspecifies a path to the user's profile. + is relative to the netlogon share. Refer to the logon script parameter in the + smb.conf man page for more information.
    sambaProfilePathspecifies a path to the user's profile. This value can be a null string, a local absolute path, or a UNC path. Refer to the - "logon path" parameter in the smb.conf(5) man page for more information.
    smbHomeThe homeDirectory property specifies the path of - the home directory for the user. The string can be null. If homeDrive is set and specifies - a drive letter, homeDirectory should be a UNC path. The path must be a network - UNC path of the form \\server\share\directory. This value can be a null string. - Refer to the logon home parameter in the smb.conf man page for more information. -
    userWorkstationcharacter string value currently unused. -
    ridthe integer representation of the user's relative identifier - (RID).
    primaryGroupIDthe relative identifier (RID) of the primary group - of the user.
    domaindomain the user is part of.

    + logon path parameter in the smb.conf man page for more information.

    sambaHomePathThe sambaHomePath property specifies the path of +the home directory for the user. The string can be null. If sambaHomeDrive is set and specifies +a drive letter, sambaHomePath should be a UNC path. The path must be a network +UNC path of the form \\server\share\directory. This value can be a null string. +Refer to the logon home parameter in the smb.conf man page for more information. +
    sambaUserWorkstationscharacter string value currently unused. +
    sambaSIDThe security identifier(SID) of the user. The windows equivalent of unix uid's.
    sambaPrimaryGroupSIDthe relative identifier (RID) 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 the Samba as a primary domain controller chapter for details on how to configure Samba as a Primary Domain Controller). The following four attributes are only stored with the sambaSamAccount entry if the values are non-default values: -

    smbHome
    scriptPath
    logonPath
    homeDrive

    +

    • sambaHomePath

    • sambaLogonScript

    • sambaProfilePath

    • sambaHomeDrive

    These attributes are only stored with the sambaSamAccount entry if the values are non-default values. For example, assume TASHTEGO has now been - configured as a PDC and that logon home = \\%L\%u was defined in + configured as a PDC and that logon home = \\%L\%u was defined in its smb.conf file. When a user named "becky" logons to the domain, - the logon home string is expanded to \\TASHTEGO\becky. + the logon home string is expanded to \\TASHTEGO\becky. If the smbHome attribute exists in the entry "uid=becky,ou=people,dc=samba,dc=org", this value is used. However, if this attribute does not exist, then the value - of the logon home parameter is used in its place. Samba + 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 with the inclusion of the posixAccount objectclass: 

    -	dn: uid=guest2, ou=people,dc=plainjoe,dc=org
-	ntPassword: 878D8014606CDA29677A44EFA1353FC7
-	pwdMustChange: 2147483647
-	primaryGroupID: 1201
-	lmPassword: 552902031BEDE9EFAAD3B435B51404EE
-	pwdLastSet: 1010179124
-	logonTime: 0
+	dn: uid=guest2, ou=people,dc=quenya,dc=org
+	sambaNTPassword: 878D8014606CDA29677A44EFA1353FC7
+	sambaPwdMustChange: 2147483647
+	sambaPrimaryGroupSID: S-1-5-21-2447931902-1787058256-3961074038-513
+	sambaNTPassword: 552902031BEDE9EFAAD3B435B51404EE
+	sambaPwdLastSet: 1010179124
+	sambaLogonTime: 0
 	objectClass: sambaSamAccount
 	uid: guest2
-	kickoffTime: 2147483647
-	acctFlags: [UX         ]
-	logoffTime: 2147483647
-	rid: 19006
-	pwdCanChange: 0
+	sambaKickoffTime: 2147483647
+	sambaAcctFlags: [UX         ]
+	sambaLogoffTime: 2147483647
+	sambaSID: S-1-5-21-2447931902-1787058256-3961074038-5006
+	sambaPwdCanChange: 0

    The following is an LDIF entry for using both the sambaSamAccount and posixAccount objectclasses: 

    -	dn: uid=gcarter, ou=people,dc=plainjoe,dc=org
-	logonTime: 0
+	dn: uid=gcarter, ou=people,dc=quenya,dc=org
+	sambaLogonTime: 0
 	displayName: Gerald Carter
-	lmPassword: 552902031BEDE9EFAAD3B435B51404EE
-	primaryGroupID: 1201
+	sambaLMPassword: 552902031BEDE9EFAAD3B435B51404EE
+	sambaPrimaryGroupSID: S-1-5-21-2447931902-1787058256-3961074038-1201
 	objectClass: posixAccount
 	objectClass: sambaSamAccount
-	acctFlags: [UX         ]
+	sambaAcctFlags: [UX         ]
 	userPassword: {crypt}BpM2ej8Rkzogo
 	uid: gcarter
 	uidNumber: 9000
@@ -702,60 +688,59 @@ access to attrs=lmPassword,ntPassword
 	loginShell: /bin/bash
 	logoffTime: 2147483647
 	gidNumber: 100
-	kickoffTime: 2147483647
-	pwdLastSet: 1010179230
-	rid: 19000
+	sambaKickoffTime: 2147483647
+	sambaPwdLastSet: 1010179230
+	sambaSID: S-1-5-21-2447931902-1787058256-3961074038-5004
 	homeDirectory: /home/tashtego/gcarter
-	pwdCanChange: 0
-	pwdMustChange: 2147483647
-	ntPassword: 878D8014606CDA29677A44EFA1353FC7
+	sambaPwdCanChange: 0
+	sambaPwdMustChange: 2147483647
+	sambaNTPassword: 878D8014606CDA29677A44EFA1353FC7

    -

    Password synchronisation

    +

    Password synchronisation

    Since version 3.0 samba 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 following values:

    yes

    When the user changes his password, update +

    The ldap passwd sync options can have the following values:

    yes

    When the user changes his password, update ntPassword, lmPassword - and the password fields.

    no

    Only update ntPassword and lmPassword.

    only

    Only update the LDAP password and let the LDAP server worry - about the other fields. This option is only available when the LDAP server supports LDAP_EXOP_X_MODIFY_PASSWD.

    More information can be found in the smb.conf manpage. -

    MySQL

    + and the password fields.

    no

    Only update ntPassword and lmPassword.

    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. [3]

    More information can be found in the smb.conf manpage. +

    MySQL

    Every so often someone will come along with a great new idea. Storing of user accounts in an SQL backend is one of them. Those who want to do this are in the best position to know what the specific benefits are to them. This may sound like a cop-out, but in truth we can not attempt to document every nitty little detail why certain things of marginal utility to the bulk of Samba users might make sense to the rest. In any case, the following instructions should help the determined SQL user to implement a working system. -

    Creating the database

    +

    Creating the database

    You either can set up your own table and specify the field names to pdb_mysql (see below for the column names) or use the default table. The file examples/pdb/mysql/mysql.dump contains the correct queries to create the required tables. Use the command : - 

    $ mysql -uusername -hhostname -ppassword \
-databasename < /path/to/samba/examples/pdb/mysql/mysql.dump

    -

    Configuring

    This plugin lacks some good documentation, but here is some short info:

    Add a the following to the passdb backend variable in your smb.conf: - 

    -			passdb backend = [other-plugins] mysql:identifier [other-plugins]
-

    +

    +$ mysql -uusername -hhostname -ppassword \
+databasename < /path/to/samba/examples/pdb/mysql/mysql.dump
+

    +

    Configuring

    This plugin lacks some good documentation, but here is some short info:

    Add a the following to the passdb backend variable in your smb.conf: +

    passdb backend = [other-plugins] mysql:identifier [other-plugins]

    The identifier can be any string you like, as long as it doesn't collide with the identifiers of other plugins or other instances of pdb_mysql. If you - specify multiple pdb_mysql.so entries in passdb backend, you also need to + specify multiple pdb_mysql.so entries in passdb backend, you also need to use different identifiers!

    Additional options can be given through the smb.conf file in the [global] section.

    -

    Table 11.2. Basic smb.conf options for MySQL passdb backend

    FieldContents
    identifier:mysql hosthost name, defaults to 'localhost'
    identifier:mysql password 
    identifier:mysql userdefaults to 'samba'
    identifier:mysql databasedefaults to 'samba'
    identifier:mysql portdefaults to 3306
    identifier:tableName of the table containing users

    +

    Table 11.2. Basic smb.conf options for MySQL passdb backend

    FieldContents
    mysql hosthost name, defaults to 'localhost'
    mysql password 
    mysql userdefaults to 'samba'
    mysql databasedefaults to 'samba'
    mysql portdefaults to 3306
    tableName of the table containing users

    Warning

    Since the password for the MySQL user is stored in the - smb.conf file, you should make the the smb.conf file + smb.conf file, you should make the smb.conf file readable only to the user that runs Samba This is considered a security bug and will be fixed soon.

    Names of the columns in this table (I've added column types those columns should have first):

    -

    Table 11.3. MySQL field names for MySQL passdb backend

    FieldTypeContents
    identifier:logon time columnint(9) 
    identifier:logoff time columnint(9) 
    identifier:kickoff time columnint(9) 
    identifier:pass last set time columnint(9) 
    identifier:pass can change time columnint(9) 
    identifier:pass must change time columnint(9) 
    identifier:username columnvarchar(255)unix username
    identifier:domain columnvarchar(255)NT domain user is part of
    identifier:nt username columnvarchar(255)NT username
    identifier:fullname columnvarchar(255)Full name of user
    identifier:home dir columnvarchar(255)Unix homedir path
    identifier:dir drive columnvarchar(2)Directory drive path (eg: 'H:')
    identifier:logon script columnvarchar(255)Batch file to run on client side when logging on
    identifier:profile path columnvarchar(255)Path of profile
    identifier:acct desc columnvarchar(255)Some ASCII NT user data
    identifier:workstations columnvarchar(255)Workstations user can logon to (or NULL for all)
    identifier:unknown string columnvarchar(255)unknown string
    identifier:munged dial columnvarchar(255)?
    identifier:user sid columnvarchar(255)NT user SID
    identifier:group sid columnvarchar(255)NT group ID
    identifier:lanman pass columnvarchar(255)encrypted lanman password
    identifier:nt pass columnvarchar(255)encrypted nt passwd
    identifier:plain pass columnvarchar(255)plaintext password
    identifier:acct control columnint(9)nt user data
    identifier:unknown 3 columnint(9)unknown
    identifier:logon divs columnint(9)?
    identifier:hours len columnint(9)?
    identifier:unknown 5 columnint(9)unknown
    identifier:unknown 6 columnint(9)unknown

    +

    Table 11.3. MySQL field names for MySQL passdb backend

    FieldTypeContents
    logon time columnint(9) 
    logoff time columnint(9) 
    kickoff time columnint(9) 
    pass last set time columnint(9) 
    pass can change time columnint(9) 
    pass must change time columnint(9) 
    username columnvarchar(255)unix username
    domain columnvarchar(255)NT domain user is part of
    nt username columnvarchar(255)NT username
    fullname columnvarchar(255)Full name of user
    home dir columnvarchar(255)UNIX homedir path
    dir drive columnvarchar(2)Directory drive path (eg: 'H:')
    logon script columnvarchar(255)Batch file to run on client side when logging on
    profile path columnvarchar(255)Path of profile
    acct desc columnvarchar(255)Some ASCII NT user data
    workstations columnvarchar(255)Workstations user can logon to (or NULL for all)
    unknown string columnvarchar(255)unknown string
    munged dial columnvarchar(255)?
    user sid columnvarchar(255)NT user SID
    group sid columnvarchar(255)NT group ID
    lanman pass columnvarchar(255)encrypted lanman password
    nt pass columnvarchar(255)encrypted nt passwd
    plain pass columnvarchar(255)plaintext password
    acct control columnint(9)nt user data
    unknown 3 columnint(9)unknown
    logon divs columnint(9)?
    hours len columnint(9)?
    unknown 5 columnint(9)unknown
    unknown 6 columnint(9)unknown

    Eventually, you can put a colon (:) after the name of each column, which should specify the column to update when updating the table. You can also specify nothing behind the colon - then the data from the field will not be updated. -

    Using plaintext passwords or encrypted password

    +

    Using plaintext passwords or encrypted password

    I strongly discourage the use of plaintext passwords, however, you can use them:

    If you would like to use plaintext passwords, set @@ -765,7 +750,7 @@ access to attrs=lmPassword,ntPassword

    If you use encrypted passwords, set the 'identifier:plain pass column' to 'NULL' (without the quotes). This is the default. -

    Getting non-column data from the table

    +

    Getting non-column data from the table

    It is possible to have not all data in the database and making some 'constant'.

    For example, you can set 'identifier:fullname column' to : @@ -780,33 +765,21 @@ access to attrs=lmPassword,ntPassword

    To import data, use: $ pdbedit -i xml:filename -

    Common Errors

    Users can not logon - Users not in Samba SAM

    - People forget to put their users in their backend and then complain Samba won't authorize them. -

    Users are being added to the wrong backend database

    +

    Common Errors

    Users can not 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 section Account Management Tools for details.

    Users being added to wrong backend database

    A few complaints have been received from users that just moved to Samba-3. The following smb.conf file entries were causing problems, new accounts were being added to the old smbpasswd file, not to the tdbsam passdb.tdb file:

    - 

    -	[globals]
-		...
-		passdb backend = smbpasswd, tdbsam, guest
-		...
-

    +

    [global]
    ...
    passdb backend = smbpasswd, tdbsam
    ...

    Samba will add new accounts to the first entry in the passdb backend parameter entry. If you want to update to the tdbsam, then change the entry to:

    - 

    -	[globals]
-		...
-		passdb backend = tdbsam, smbpasswd, guest
-		...
-

    -

    auth methods does not work

    - If you explicitly set an 'auth methods' parameter, guest must be specified as the first - entry on the line. Eg: auth methods = guest sam. +

    [globals]
    ...
    passdb backend = tdbsam, smbpasswd
    ...

    +

    auth methods does not work

    + If you explicitly set an auth methods parameter, guest must be specified as the first + entry on the line. Eg: auth methods = guest sam.

    - This is the exact opposite of the requirement for the passdb backed + This is the exact opposite of the requirement for the passdb backend option, where it must be the LAST parameter on the line. -

    Prev Up Next
    Chapter 10. Samba / MS Windows Network Browsing Guide Home Chapter 12. Mapping MS Windows and Unix Groups
    +


    [3] Only when the LDAP server supports LDAP_EXOP_X_MODIFY_PASSWD

    Prev Up Next
    Chapter 10. Samba / MS Windows Network Browsing Guide Home Chapter 12. Mapping MS Windows and UNIX Groups
    diff --git a/docs/htmldocs/pdbedit.8.html b/docs/htmldocs/pdbedit.8.html index 368a6911b7..39a901923f 100644 --- a/docs/htmldocs/pdbedit.8.html +++ b/docs/htmldocs/pdbedit.8.html @@ -1,4 +1,4 @@ -pdbedit

    Name

    pdbedit — manage the SAM database

    Synopsis

    pdbedit [-L] [-v] [-w] [-u username] [-f fullname] [-h homedir] [-D drive] [-S script] [-p profile] [-a] [-m] [-x] [-i passdb-backend] [-e passdb-backend] [-b passdb-backend] [-g] [-d debuglevel] [-s configfile] [-P account-policy] [-C value]

    DESCRIPTION

    This tool is part of the Samba(7) suite.

    The pdbedit program is used to manage the users accounts +pdbedit

    Name

    pdbedit — manage the SAM database

    Synopsis

    pdbedit [-L] [-v] [-w] [-u username] [-f fullname] [-h homedir] [-D drive] [-S script] [-p profile] [-a] [-m] [-r] [-x] [-i passdb-backend] [-e passdb-backend] [-b passdb-backend] [-g] [-d debuglevel] [-s configfile] [-P account-policy] [-C value] [-c account-control]

    DESCRIPTION

    This tool is part of the Samba(7) suite.

    The pdbedit program is used to manage the users accounts stored in the sam database and can only be run by root.

    The pdbedit tool uses the passdb modular interface and is independent from the kind of users database used (currently there are smbpasswd, ldap, nis+ and tdb based and more can be added @@ -31,7 +31,7 @@ Home Directory: \\BERSERKER\samba HomeDir Drive: Logon Script: Profile Path: \\BERSERKER\profile -

    -w

    This option sets the "smbpasswd" listing format. +

    -w

    This option sets the "smbpasswd" listing format. It will make pdbedit list the users in the database, printing out the account fields in a format compatible with the smbpasswd file format. (see the @@ -44,18 +44,18 @@ samba:45:0F2B255F7B67A7A9AAD3B435B51404EE:BC281CE3F53B6A5146629CD4751D3490:[UX operations and optional in list operations.

    -f fullname

    This option can be used while adding or modifing a user account. It will specify the user's full - name.

    Example: -f "Simo Sorce"

    -h homedir

    This option can be used while adding or + name.

    Example: -f "Simo Sorce"

    -h homedir

    This option can be used while adding or modifing a user account. It will specify the user's home - directory network path.

    Example: -h "\\\\BERSERKER\\sorce" + directory network path.

    Example: -h "\\\\BERSERKER\\sorce"

    -D drive

    This option can be used while adding or modifing a user account. It will specify the windows drive - letter to be used to map the home directory.

    Example: -d "H:" + letter to be used to map the home directory.

    Example: -d "H:"

    -S script

    This option can be used while adding or modifing a user account. It will specify the user's logon - script path.

    Example: -s "\\\\BERSERKER\\netlogon\\sorce.bat" + script path.

    Example: -s "\\\\BERSERKER\\netlogon\\sorce.bat"

    -p profile

    This option can be used while adding or modifing a user account. It will specify the user's profile - directory.

    Example: -p "\\\\BERSERKER\\netlogon" + directory.

    Example: -p "\\\\BERSERKER\\netlogon"

    -G SID|rid

    This option can be used while adding or modifying a user account. It will specify the users' new primary group SID (Security Identifier) or @@ -65,7 +65,7 @@ samba:45:0F2B255F7B67A7A9AAD3B435B51404EE:BC281CE3F53B6A5146629CD4751D3490:[UX rid.

    Example: -U S-1-5-21-2447931902-1787058256-3961074038-5004

    -c account-control

    This option can be used while adding or modifying a user account. It will specify the users' account control property. Possible flags that can be set are: N, D, H, L, X. -

    Example: -c "[X ]"

    -a

    This option is used to add a user into the +

    Example: -c "[X ]"

    -a

    This option is used to add a user into the database. This command needs a user name specified with the -u switch. When adding a new user, pdbedit will also ask for the password to be used.

    Example: pdbedit -a -u sorce @@ -94,12 +94,12 @@ retype new password applies to the group mapping instead of the user database.

    This option will ease migration from one passdb backend to another and will ease backing up.

    -b passdb-backend

    Use a different default passdb backend.

    Example: pdbedit -b xml:/root/pdb-backup.xml -l

    -P account-policy

    Display an account policy

    Valid policies are: minimum password age, reset count minutes, disconnect time, user must logon to change password, password history, lockout duration, min password length, - maximum password age and bad lockout attempt.

    Example: pdbedit -P "bad lockout attempt"

    +		maximum password age and bad lockout attempt.
    Example: pdbedit -P "bad lockout attempt"
     account policy value for bad lockout attempt is 0
    -C account-policy-value

    Sets an account policy to a specified value. This option may only be used in conjunction with the -P option. -

    Example: pdbedit -P "bad lockout attempt" -C 3

    +		
    Example: pdbedit -P "bad lockout attempt" -C 3
     account policy value for bad lockout attempt was 0
 account policy value for bad lockout attempt is now 3
    -h|--help

    Print a summary of command line options. @@ -109,8 +109,7 @@ configuration details required by the server. The information in this file includes server-specific information such as what printcap file to use, as well as descriptions of all the services that the server is -to provide. See -smb.conf(5) for more information. +to provide. See smb.conf for more information. The default configuration file name is determined at compile time.

    -d|--debug=debuglevel

    debuglevel is an integer from 0 to 10. The default value if this parameter is @@ -124,10 +123,9 @@ amounts of log data, and should only be used when investigating a problem. Levels above 3 are designed for use only by developers and generate HUGE amounts of log data, most of which is extremely cryptic.

    Note that specifying this parameter here will -override the log -level parameter in the -smb.conf(5) file.

    -l|--logfile=logbasename

    File name for log/debug files. The extension -".client" will be appended. The log file is +override the log level parameter +in the smb.conf file.

    -l|--logfile=logbasename

    File name for log/debug files. The extension +".client" will be appended. The log file is never removed by the client.

    NOTES

    This command may be used only by root.

    VERSION

    This man page is correct for version 3.0 of the Samba suite.

    SEE ALSO

    smbpasswd(5), samba(7)

    AUTHOR

    The original Samba software and related utilities diff --git a/docs/htmldocs/pr01.html b/docs/htmldocs/pr01.html new file mode 100644 index 0000000000..193564ca32 --- /dev/null +++ b/docs/htmldocs/pr01.html @@ -0,0 +1,5 @@ +Legal Notice

    Legal Notice
    Prev   Next

    Legal Notice

    +This documentation is distributed under the GNU General Public License (GPL) +version 2. A copy of the license is included with the Samba source +distribution. A copy can be found on-line at http://www.fsf.org/licenses/gpl.txt +

    Prev Up Next
    SAMBA Project Documentation Home Attributions
    diff --git a/docs/htmldocs/pr02.html b/docs/htmldocs/pr02.html new file mode 100644 index 0000000000..08a02a7142 --- /dev/null +++ b/docs/htmldocs/pr02.html @@ -0,0 +1 @@ +Attributions
    Attributions
    Prev   Next

    Attributions

    Introduction to Samba

    How to Install and Test SAMBA

    Fast Start for the Impatient

    Server Types and Security Modes

    Domain Control

    Backup Domain Control

    Domain Membership

    Stand-Alone Servers

    MS Windows Network Configuration Guide

    Samba / MS Windows Network Browsing Guide

    Account Information Databases

    Mapping MS Windows and UNIX Groups

    File, Directory and Share Access Controls

    File and Record Locking

    Securing Samba

    Interdomain Trust Relationships

    Hosting a Microsoft Distributed File System tree on Samba

    Classical Printing Support

    CUPS Printing Support in Samba 3.0

    Stackable VFS modules

    • Jelmer R. Vernooij <jelmer@samba.org>

    • John H. Terpstra <jht@samba.org>

    • Tim Potter

    • Simo Sorce (original vfs_skel README)

    • Alexander Bokovoy (original vfs_netatalk docs)

    • Stefan Metzmacher (Update for multiple modules)

    Advanced Network Management

    System and Account Policies

    Desktop Profile Management

    PAM based Distributed Authentication

    Integrating MS Windows networks with Samba

    Unicode/Charsets

    Samba Backup Techniques

    High Availability Options

    Upgrading from Samba-2.x to Samba-3.0.0

    Migration from NT4 PDC to Samba-3 PDC

    SWAT - The Samba Web Administration Tool

    The Samba checklist

    Analysing and solving samba problems

    Reporting Bugs

    How to compile Samba

    Portability

    Samba and other CIFS clients

    Samba Performance Tuning

    DNS and DHCP Configuration Guide

    Further Resources

    Prev Up Next
    Legal Notice Home Part I. General Installation
    diff --git a/docs/htmldocs/printing.html b/docs/htmldocs/printing.html index 089bba6e0f..2b0abb56e6 100644 --- a/docs/htmldocs/printing.html +++ b/docs/htmldocs/printing.html @@ -1,12 +1,11 @@ -Chapter 18. Classical Printing Support
    Chapter 18. Classical Printing Support
    Prev Part III. Advanced Configuration Next

    Chapter 18. Classical Printing Support

    Kurt Pfeifle

    Danka Deutschland GmbH

    Gerald (Jerry) Carter

    Samba Team

    May 32, 2003

    Table of Contents

    Features and Benefits
    Technical Introduction
    What happens if you send a Job from a Client
    Printing Related Configuration Parameters
    Parameters Recommended for Use
    Parameters for Backwards Compatibility
    Parameters no longer in use
    A simple Configuration to Print with Samba-3
    Verification of "Settings in Use" with testparm
    A little Experiment to warn you
    Extended Sample Configuration to Print with Samba-3
    Detailed Explanation of the Example's Settings
    The [global] Section
    The [printers] Section
    Any [my_printer_name] Section
    Print Commands
    Default Print Commands for various Unix Print Subsystems
    Setting up your own Print Commands
    Innovations in Samba Printing since 2.2
    Client Drivers on Samba Server for Point'n'Print
    The [printer$] Section is removed from Samba-3
    Creating the [print$] Share
    Parameters in the [print$] Section
    Subdirectory Structure in [print$]
    Installing Drivers into [print$]
    Setting Drivers for existing Printers with a Client GUI
    Setting Drivers for existing Printers with -rpcclient
    "The Proof of the Pudding lies in the Eating" (Client Driver Install -Procedure)
    The first Client Driver Installation
    IMPORTANT! Setting Device Modes on new Printers
    Further Client Driver Install Procedures
    Always make first Client Connection as root or "printer admin"
    Other Gotchas
    Setting Default Print Options for the Client Drivers
    Supporting large Numbers of Printers
    Adding new Printers with the Windows NT APW
    Weird Error Message Cannot connect under a -different Name
    Be careful when assembling Driver Files
    Samba and Printer Ports
    Avoiding the most common Misconfigurations of the Client Driver
    The Imprints Toolset
    What is Imprints?
    Creating Printer Driver Packages
    The Imprints Server
    The Installation Client
    Add Network Printers at Logon without User Interaction
    The addprinter command
    Migration of "Classical" printing to Samba-3
    Publishing Printer Information in Active Directory or LDAP
    Common Errors and Problems
    I give my root password but I don't get access
    My printjobs get spooled into the spooling directory, but then get lost

    Features and Benefits

    +Chapter 18. Classical Printing Support

    Chapter 18. Classical Printing Support
    Prev Part III. Advanced Configuration Next

    Chapter 18. Classical Printing Support

    Kurt Pfeifle

    Danka Deutschland GmbH

    Gerald (Jerry) Carter

    Samba Team

    May 31, 2003

    Table of Contents

    Features and Benefits
    Technical Introduction
    What happens if you send a Job from a Client
    Printing Related Configuration Parameters
    Parameters Recommended for Use
    A simple Configuration to Print
    Verification of "Settings in Use" with testparm
    A little Experiment to warn you
    Extended Sample Configuration to Print
    Detailed Explanation of the Example's Settings
    The [global] Section
    The [printers] Section
    Any [my_printer_name] Section
    Print Commands
    Default Print Commands for various UNIX Print Subsystems
    Setting up your own Print Commands
    Innovations in Samba Printing since 2.2
    Client Drivers on Samba Server for Point'n'Print
    The [printer$] Section is removed from Samba 3
    Creating the [print$] Share
    Parameters in the [print$] Section
    Subdirectory Structure in [print$]
    Installing Drivers into [print$]
    Setting Drivers for existing Printers with a Client GUI
    Setting Drivers for existing Printers with +rpcclient
    Client Driver Install Procedure
    The first Client Driver Installation
    IMPORTANT! Setting Device Modes on new Printers
    Further Client Driver Install Procedures
    Always make first Client Connection as root or "printer admin"
    Other Gotchas
    Setting Default Print Options for the Client Drivers
    Supporting large Numbers of Printers
    Adding new Printers with the Windows NT APW
    Weird Error Message Cannot connect under a +different Name
    Be careful when assembling Driver Files
    Samba and Printer Ports
    Avoiding the most common Misconfigurations of the Client Driver
    The Imprints Toolset
    What is Imprints?
    Creating Printer Driver Packages
    The Imprints Server
    The Installation Client
    Add Network Printers at Logon 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 don't get access
    My printjobs 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-3.0 print service may be run on a Standalone or a Domain +A Samba print service may be run on a Standalone or a Domain member server, side by side with file serving functions, or on a dedicated print server. It can be made as tight or as loosely secured as needs dictate. Configurations may be simple or complex. Available @@ -30,24 +29,24 @@ implemented by the more traditional UNIX (BSD- and System V-style) printing systems. Many things apply to CUPS, the newer Common UNIX Printing System, too; so if you use CUPS, you might be tempted to jump to the next chapter -- but you will certainly miss a few things if you -do so. Better read this chapter too. +do so. Better to read this chapter too.

    Note

    Most of the given examples have been verified on Windows XP Professional clients. Where this document describes the responses to commands given, bear in mind that Windows 2000 clients are very similar, but may differ in details. Windows NT 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 +subsystem of the UNIX OS it runs on. Samba is a "middleman". It takes printfiles from Windows (or other SMB) clients and passes them to the real printing system for further processing. Therefore it needs to -"talk" to two sides: to the Windows print clients and to the Unix +"talk" to two sides: to the Windows print clients and to the UNIX printing system. Hence we must differentiate between the various client OS types each of which behave differently, as well as the various UNIX print subsystems, which themselves have different features and are accessed differently. This part of the Samba HOWTO -Collection deals with the "traditional" way of Unix printing first; +Collection deals with the "traditional" way of UNIX printing first; the next chapter covers in great detail the more modern Common UNIX Printing System (CUPS). @@ -55,15 +54,15 @@ the next chapter covers in great detail the more modern

    Important

    CUPS users, be warned: don't just jump on to the next chapter. You might miss important information contained only here!

    -

    What happens if you send a Job from a Client

    +

    What happens if you send a Job from a Client

    To successfully print a job from a Windows client via a Samba print server to a UNIX printer, there are 6 (potentially 7) stages: -

    1. Windows opens a connection to the printershare

    2. Samba must authenticate the user

    3. Windows sends a copy of the printfile over the network +

      1. Windows opens a connection to the printer share

      2. Samba must authenticate the user

      3. Windows sends a copy of the printfile over the network into Samba's spooling area

      4. Windows closes the connection again

      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 +to the UNIX print subsystem's spooling area

      7. The UNIX print subsystem processes the print job

      8. The printfile may need to be explicitly deleted -from the Samba spooling area.

    Printing Related Configuration Parameters

    +from the Samba spooling area.

    Printing Related Configuration Parameters

    There are a number of configuration parameters in controlling Samba's printing behaviour. Please also refer to the man page for smb.conf to @@ -71,74 +70,65 @@ acquire an overview about these. As with other parameters, there are Global Level (tagged with a "G" in the listings) and Service Level ("S") parameters.

    Service Level Parameters

    These may go into the -[global] section of -. In this case they define the default +[global] section of smb.conf. +In this case they define the default behaviour of all individual or service level shares (provided those don't have a different setting defined for the same parameter, thus overriding the global default).

    Global Parameters

    These may not go into individual shares. If they go in by error, the "testparm" utility can discover -this (if you run it) and tell you so.

    Parameters Recommended for Use

    The following smb.conf parameters directly -related to printing are used in Samba-3. See also the +this (if you run it) and tell you so.

    Parameters Recommended for Use

    The following smb.conf parameters directly +related to printing are used in Samba. See also the smb.conf man page for detailed explanations: -

    List of printing related parameters in Samba-3.  -

    Global level parameters:

    • addprinter command (G)

    • deleteprinter command (G)

    • disable spoolss (G)

    • enumports command (G)

    • load printers (G)

    • lpq cache time (G)

    • os2 driver map (G)

    • printcap name (G), printcap (G)

    • show add printer wizard (G)

    • total print jobs (G)

    • use client driver (G)

    - -

    Service level parameters:

    • hosts allow (S)

    • hosts deny (S)

    • lppause command (S)

    • lpq command (S)

    • lpresume command (S)

    • lprm command (S)

    • max print jobs (S)

    • min print space (S)

    • print command (S)

    • printable (S), print ok (S)

    • printer name (S), printer (S)

    • printer admin (S)

    • printing = [cups|bsd|lprng...] (S)

    • queuepause command (S)

    • queueresume command (S)

    • total print jobs (S)

    +

    Global level parameters: addprinter command, +deleteprinter command, +disable spoolss, +enumports command, +load printers, +lpq cache time, +os2 driver map, +printcap name, printcap, +show add printer wizard, +total print jobs, +use client driver. +

    Service level parameters: hosts allow, +hosts deny, +lppause command, +lpq command, +lpresume command, +lprm command, +max print jobs, +min print space, +print command, +printable, print ok , +printer name, printer, +printer admin, +printing = [cups|bsd|lprng...], +queuepause command, +queueresume command, +total print jobs.

    Samba's printing support implements the Microsoft Remote Procedure Calls (MS-RPC) methods for printing. These are used by Windows NT (and later) print servers. The old "LanMan" protocol is still supported as a fallback resort, and for older clients to use. More details will follow further beneath. -

    Parameters for Backwards Compatibility

    -Two new parameters that were added in Samba 2.2.2, are still present -in Samba-3.0. Both of these options are described in the -smb.conf man page and are disabled by -default. Use them with caution! -

    disable spoolss(G)

    This is -provided for better support of Samba 2.0.x backwards capability. It -will disable Samba's support for MS-RPC printing and yield identical -printing behaviour to Samba 2.0.x.

    use client driver (G)

    was provided -for using local printer drivers on Windows NT/2000 clients. It does -not apply to Windows 95/98/ME clients.

    Parameters "for backward compatibility only", use with caution.  -

    • disable spoolss (G)

    • use client driver (S)

    -

    Parameters no longer in use

    -Samba users upgrading from 2.2.x to 3.0 need to be aware that some -previously available settings are no longer supported (as was -announced some time ago). Here is a list of them: -

    "old" parameters, removed in Samba-3.  -The following smb.conf parameters have been -deprecated already in Samba 2.2 and are now completely removed from -Samba-3. You cannot use them in new 3.0 installations: - -

    • printer driver file (G)

    • total print jobs (G)

    • postscript (S)

    • printer driver (S)

    • printer driver location (S)

    -

    A simple Configuration to Print with Samba-3

    +

    A simple Configuration to Print

    Here is a very simple example configuration for print related settings -in the file. If you compare it with your -own system's , you probably find some +in the file. If you compare it with your own system's , you probably find some additional parameters included there (as pre-configured by your OS vendor). Further below is a discussion and explanation of the parameters. Note, that this example doesn't use many parameters. However, in many environments these are enough to provide a valid - which enables all clients to print. -

    - [global]
-         printing = bsd
-         load printers = yes
-
- [printers]
-         path = /var/spool/samba
-         printable = yes
-         public = yes
-         writable = no
-

    -This is only an example configuration. Many settings, if not -explicitly set to a specific value, are used and set by Samba -implicitly to its own default, because these have been compiled in. -To see all settings, let root use the testparm -utility. testparm also gives warnings if you have -mis-configured certain things. Its complete output is easily 340 lines -and more. You may want to pipe it through a pager program. +smb.conf file which enables all clients to print. +

    Example 18.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. On the whole 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 setting, both default as well as smb.conf file +settings. Testparm gives warnings for all mis-configured +settings. The complete output is easily 340 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 @@ -147,7 +137,7 @@ reminder: It even tolerates some spelling errors (like "browsable" instead of "browseable"). Most spelling is case-insensitive. Also, you can use "Yes|No" or "True|False" for boolean settings. Lists of names may be separated by commas, spaces or tabs. -

    Verification of "Settings in Use" with testparm

    +

    Verification of "Settings in Use" with testparm

    To see all (or at least most) printing related settings in Samba, including the implicitly used ones, try the command outlined below (hit "ENTER" twice!). It greps for all occurrences of "lp", "print", @@ -198,20 +188,20 @@ as shown above: You can easily verify which settings were implicitly added by Samba's default behaviour. Don't forget about this point: it may be important in your future dealings with Samba. -

    Note

    testparm in Samba-3.0 behaves differently from 2.2.x: used +

    Note

    testparm in samba 3 behaves differently from 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.

    A little Experiment to warn you

    +configuration used, add the "-v" parameter to testparm.

    A little Experiment to warn you

    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 an example from personal experience as a warning, -try to just "comment out" the load printers" +try to just "comment out" the load printers" parameter. If your 2.2.x system behaves like mine, you'll see this: 

     root# grep "load printers" /etc/samba/smb.conf
  #      load printers = Yes
-        # This setting is commented ooouuuuut!!
-
+ # This setting is commented ooouuuuut!!
+ 
 root# testparm -v /etc/samba/smb.conf | egrep "(load printers)"
         load printers = Yes
 
@@ -232,7 +222,7 @@ any more... at least not by this ;-)

    Only when setting the parameter explicitly to -"load printers = No" +"load printers = No" would Samba recognize my intentions. So my strong advice is:

    • Never rely on "commented out" parameters!

    • Always set it up explicitly as you intend it to behave.

    • Use testparm to uncover hidden @@ -258,7 +248,7 @@ ask testparm what the Samba print configuration would be, if you used this minimalistic file as your real : 

      -root#  testparm -v /etc/samba/smb.conf-minimal | egrep "(print|lpq|spool|driver|ports|[)"
+root# testparm -v smb.conf-minimal | egrep "(print|lpq|spool|driver|ports|[)"
  Processing section "[printers]"
  WARNING: [printers] service MUST be printable!
  No path in service printers - using /tmp
@@ -291,8 +281,8 @@ testparm issued 2 warnings:
 [printers] section as printable,
 and

    • because we didn't tell it which spool directory to use.

    -However, this was not fatal, and Samba-3.0 will default to values that -will work here. But, please!, don't rely on this and don't use this +However, this was not fatal, and samba will default to values that +will work here. Please, don't rely on this and don't use this example! This was only meant to make you careful to design and specify your setup to be what you really want it to be. The outcome on your system may vary for some parameters, since you may have a Samba built @@ -304,61 +294,20 @@ comment sign at the front). At first I regarded this as a bug in my Samba version(s). But the man page states: “Internal whitespace in a parameter value is retained verbatim.” This means that a line consisting of, for example, -

    -printing = lprng     #This defines LPRng as the printing system"
-

    +

    # 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. And this is an invalid value that will be ignored, and a default value used instead.] -

    Extended Sample Configuration to Print with Samba-3

    -Here we show a more verbose example configuration for print related -settings in an . Below is a discussion +

    Extended Sample Configuration to Print

    + In the extended BSD configuration example we show a more verbose example configuration for print related + settings in BSD-printing style environment . Below is a discussion and explanation of the various parameters. We chose to use BSD-style printing here, because we guess it is still the most commonly used system on legacy Linux installations (new installs now predominantly have CUPS, which is discussed entirely in the next chapter of this document). Note, that this example explicitly names many parameters -which don't need to be stated because they are set by default. You -might be able to do with a leaner .

    Tip

    -if you read access it with the Samba Web Administration Tool (SWAT), -and then write it to disk again, it will be optimized in a way such -that it doesn't contain any superfluous parameters and comments. SWAT -organizes the file for best performance. Remember that each smbd -re-reads the Samba configuration once a minute, and that each -connection spawns an smbd process of its own, so it is not a bad idea -to optimize the in environments with -hundreds or thousands of clients.

    - [global]
-         printing = bsd
-         load printers = yes
-         show add printer wizard = yes
-         printcap name = /etc/printcap
-         printer admin = @ntadmin, root
-         total 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
-         writeable = no
-         hosts allow = 0.0.0.0
-         hosts deny = turbo_xp, 10.160.50.23, 10.160.51.60
-         guest ok = no
-

    +which don't need to be specified because they are set by default. You +might be able to do with a leaner smb.conf file.

    Example 18.2. Extended configuration with BSD printing

    [global]
    printing = bsd
    load printers = yes
    show add printer wizard = yes
    printcap name = /etc/printcap
    printer admin = @ntadmin, root
    total 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
    writeable = no
    hosts allow = 0.0.0.0
    hosts deny = turbo_xp, 10.160.50.23, 10.160.51.60
    guest ok = no

    This also is only an example configuration. You may not find all the settings in your own (as pre-configured by your OS @@ -368,31 +317,31 @@ default, because these have been compiled in. To see all settings, let root use the testparm utility. testparm also gives warnings if you have mis-configured certain things.. -

    Detailed Explanation of the Example's Settings

    +

    Detailed Explanation of the Example's Settings

    Following is a discussion of the settings from above shown example. -

    The [global] Section

    +

    The [global] Section

    The [global] section is one of 4 special sections (along with [[homes], [printers] and [print$]...) It contains all parameters which apply to the server as a whole. It is the place for parameters which -have only a "global" meaning (G). It may also contain service level -parameters (S) which then define default settings for all other +have only a "global" meaning. It may also contain service level +parameters which then define default settings for all other sections and shares. This way you can simplify the configuration and avoid setting the same value repeatedly. (Within each individual section or share you may however override these globally set "share level" settings and specify other values). -

    printing = bsd

    this causes Samba to use default print commands +

    printing = bsd

    this causes Samba to use default print commands applicable for the BSD (a.k.a. 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 +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.0 no longer -supports the SOFTQ printing system.

    load printers = yes

    this tells Samba to create automatically all +printer shares that are not defined differently. Samba 3 no longer +supports the SOFTQ printing system.

    load printers = yes

    this 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 @@ -401,8 +350,7 @@ share will clone the configuration options found in the [printers] section. (A load printers = no setting will allow you to specify each UNIX printer you want to share separately, leaving out some you don't want to be -publicly visible and available).

    show add printer wizard = -yes

    this setting is normally +publicly visible and available).

    show add printer wizard = yes

    this setting is normally enabled by default (even if the parameter is not written into the ). It makes the Add Printer Wizard icon show up in the Printers folder of the Samba host's @@ -413,38 +361,38 @@ will not suffice!). The Add Printer Wizard lets you upload printer drivers to the [print$] share and associate it with a printer (if the respective queue exists there before the action), or exchange a printer's driver against any other previously -uploaded driver.

    total print jobs = 100

    this setting sets the upper limit to 100 print jobs +uploaded driver.

    total print jobs = 100

    this setting sets the upper limit to 100 print jobs being active on the Samba server at any one time. Should a client submit a job which 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 "0" (the default) means there is no limit at all! -

    printcap name = /etc/printcap

    this tells Samba where to look for a list of +

    printcap name = /etc/printcap

    this tells Samba where to look for a list of available printer names. (If you use CUPS, make sure that a printcap file is written: this is controlled by the "Printcap" directive of cupsd.conf). -

    printer admin = @ntadmin

    members of the ntadmin group should be able to add +

    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 in +printer admin. The "@" sign precedes group names in . A printer admin can do anything to printers via the remote administration interfaces offered by MS-RPC -(see below). Note that the printer admin +(see below). Note that the printer admin parameter is normally a share level parameter, so you may associate different groups to different printer shares in larger installations, -if you use the printer admin parameter on the +if you use the printer admin parameter on the share levels). -

    lpq cache time = 20

    this controls the cache time for the results of the +

    lpq cache time = 20

    this controls the cache time for the results of the lpq command. It prevents the lpq command being called too often and reduces load on a heavily used print server. -

    use client driver = no

    if set to yes, this setting only +

    use client driver = no

    if set to yes, this setting only takes effect for Win NT/2k/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) which have valid drivers installed on the Samba server! For more detailed explanations see the man page of smb.conf. -

    The [printers] Section

    +

    The [printers] Section

    This 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, @@ -454,41 +402,40 @@ section as a general convenience shortcut to share all printers with minimal configuration. It is also a container for settings which should apply as default to all printers. (For more details see the smb.conf man page.) Settings inside this -container must be share level parameters (S). -

    comment = All printers

    the comment is shown next to +container must be share level parameters. +

    comment = All printers

    the comment is shown next to the share if a client queries the server, either via Network Neighbourhood or with the net view command to list available shares. -

    printable = yes

    please note well, that the +

    printable = yes

    please note well, that the [printers] service must be declared as printable. If you specify otherwise, smbd will refuse to load at startup. This parameter allows connected clients to open, write to and submit spool files into the -directory specified with the path parameter for +directory specified with the path parameter for this service. It is used by Samba to differentiate printer shares from -file shares.

    path = /var/spool/samba

    this must point to a directory used by Samba to spool +file shares.

    path = /var/spool/samba

    this must point to a directory used by Samba to spool incoming print files. It must not be the same as the spool directory specified in the configuration of your UNIX print subsystem! The path would typically point to a directory which is world writeable, with the "sticky" bit set to it. -

    browseable = no

    this is always set to no if -printable = yes. It makes the +

    browseable = no

    this is always set to no if +printable = yes. It makes the [printer] share itself invisible in the list of available shares in a net view command or in the Explorer browse list. (Note that you will of course see the individual printers). -

    guest ok = yes

    +

    guest ok = yes

    if set to yes, then no password is required to connect to the printers service. Access will be granted with the -privileges of the guest account. On many systems the +privileges of the guest account. On many systems the guest account will map to a user named "nobody". This user is in the UNIX passwd file with an empty password, but with no valid UNIX login. (Note: on some systems the guest account might not have the privilege to be able to print. Test this by logging in as your guest user using su - guest and run a system print command like -

    lpr -P printername /etc/motd

    public = yes

    this is a synonym for guest ok = -yes. Since we have guest ok = yes, +

    lpr -P printername /etc/motd

    public = yes

    this is a synonym for guest ok = yes. Since we have guest ok = yes, it really doesn't need to be here! (This leads to the interesting question: “What, if I by accident have to contradictory settings for the same share?” The answer is: the last one encountered by @@ -497,16 +444,16 @@ complain about different settings of the same parameter for the same share! You can test this by setting up multiple lines for the "guest account" parameter with different usernames, and then run testparm to see which one is actually used by Samba.) -

    read only = yes

    this normally (for other types of shares) prevents +

    read only = yes

    this normally (for other types of shares) prevents users creating or modifying files in the service's directory. However, in a "printable" service, it is always allowed to write to the directory (if user privileges allow the connection), but only via print spooling operations. "Normal" write operations are not -allowed.

    writeable = no

    -synonym for read only = yes -

    Any [my_printer_name] Section

    +allowed.

    writeable = no

    +synonym for read only = yes +

    Any [my_printer_name] Section

    If a section appears in the , which is -tagged as printable = yes, Samba presents it as +tagged as printable = yes, Samba presents it as a printer share to its clients. Note, that Win95/98/ME clients may have problems with connecting or loading printer drivers if the share name has more than 8 characters! Also be very careful if you give a @@ -515,37 +462,36 @@ client's connection request to a certain sharename, Samba always tries to find file shares with that name first; if it finds one, it will connect to this and will never ultimately connect to a printer with the same name! -

    comment = Printer with Restricted Access

    the comment says it all. -

    path = /var/spool/samba_my_printer

    here we set the spooling area for this printer to +

    comment = Printer with Restricted Access

    the comment says it all. +

    path = /var/spool/samba_my_printer

    here we set the spooling area for this printer to another directory than the default. It is not a requirement to set it differently, but the option is available. -

    printer admin = kurt

    the printer admin definition is different for this +

    printer admin = kurt

    the printer admin definition is different for this explicitly defined printer share from the general [printers] share. It is not a requirement; we did it to show that it is possible if you want it. -

    browseable = yes

    we also made this printer browseable (so that the +

    browseable = yes

    we also made this printer browseable (so that the clients may conveniently find it when browsing the Network Neighbourhood). -

    printable = yes

    see explanation in last subsection. -

    writeable = no

    see explanation in last subsection. -

    hosts allow = 10.160.50.,10.160.51.

    here we exercise a certain degree of access control -by using the hosts allow and hosts deny parameters. Note, that +

    printable = yes

    see explanation in last subsection. +

    writeable = no

    see explanation in last subsection. +

    hosts allow = 10.160.50.,10.160.51.

    here we exercise a certain degree of access control +by using the hosts allow and hosts deny parameters. Note, that this is not by any means a safe bet. It is not a way to secure your printers. This line accepts all clients from a certain subnet in a first evaluation of access control -

    hosts deny = turbo_xp,10.160.50.23,10.160.51.60 -

    all listed hosts are not allowed here (even if they +

    hosts deny = turbo_xp,10.160.50.23,10.160.51.60

    all listed hosts are not allowed here (even if they belong to the "allowed subnets"). As 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

    +

    guest ok = no

    this printer is not open for the guest account! +

    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 which have been placed into the Samba print spool directory for that printer. (That spool directory was, if you -remember, set up with the path +remember, set up with the path parameter). Typically, this command will submit the spool file to the Samba host's print subsystem, using the suitable system print command. But there is no requirement that this needs to be the @@ -557,24 +503,24 @@ 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 Print Commands for various Unix Print Subsystems

    +

    Default Print Commands for various UNIX Print Subsystems

    You learned earlier on, that Samba in most cases uses its built-in settings for many parameters if it can not 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 +print command. The default print command varies +depending on the printing parameter setting. In the commands listed below, you will notice some parameters of the form %X where X is p, s, J etc. These letters stand for "printername", "spoolfile" and "job ID" respectively. They are explained in more detail further below. Here is an overview (excluding the special case of CUPS, which is discussed in the next chapter): -

    If this setting is active......this is used in lieu of an explicit command:
    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)

    +

    If this setting is active......this is used in lieu of an explicit command:
    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)

    We excluded the special CUPS case here, because it is discussed in the next chapter. Just a short summary. For printing = CUPS: If SAMBA is compiled against libcups, it uses the CUPS API to submit jobs, etc. (It is a good idea also to set -printcap = cups in case your +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, i.e. it uses @@ -597,9 +543,9 @@ check which command takes effect. Then check that this command is adequate and actually works for your installed print subsystem. It is always a good idea to explicitly set up your configuration files the way you want them to work and not rely on any built-in defaults. -

    Setting up your own Print Commands

    +

    Setting up your own Print Commands

    After a print job has finished spooling to a service, the -print command will be used by Samba via a +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 @@ -652,22 +598,16 @@ expand the included environment variables as usual. (The syntax to include a UNIX environment variable $variable in or in the Samba print command is %$variable.) To give you a working -print command example, the following will log a +print command example, the following will log a print job to /tmp/print.log, print the file, then remove it. Note that ';' 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
-

    Innovations in Samba Printing since 2.2

    +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

    Innovations in Samba Printing since 2.2

    Before version 2.2.0, Samba's print server support for Windows clients was limited to the level of LanMan printing calls. This is the same protocol level as Windows 9x PCs offer when @@ -682,16 +622,14 @@ The additional functionality provided by the new SPOOLSS support includes: 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 (refer to http://imprints.sourceforge.net); +Imprints tool set.

  • Support for the native MS-RPC printing calls such as -StartDocPrinter, EnumJobs(), etc... (See the MSDN documentation -at http://msdn.microsoft.com/ -for more information on the Win32 printing API);

  • Support for NT Access Control + StartDocPrinter, EnumJobs(), etc... (See the MSDN documentation for more information on the Win32 printing API);

  • Support for NT Access Control Lists (ACL) on printer objects;

  • Improved support for printer queue manipulation through the use of internal databases for spooled job information (implemented by various *.tdb files).

    • -One other benefit of an update is this: Samba-3 is able to publish +One other benefit of an update is this: Samba 3 is able to publish all its printers in Active Directory (or LDAP)!

    One slight difference is here: it is possible on a Windows NT print @@ -708,7 +646,7 @@ default permissions assigned by Windows NT to a printer gives the "Print" permissions to the well-known Everyone group. (The older clients of type Win9x can only print to "shared" printers). -

    Client Drivers on Samba Server for Point'n'Print

    +

    Client Drivers on Samba Server for Point'n'Print

    There is still confusion about what all this means: Is it or is it not a requirement for printer drivers to be installed on a Samba host in order to support printing from Windows clients? The @@ -743,10 +681,10 @@ does not use these uploaded drivers in any way to process spooled files. Drivers are utilized entirely by the clients, who download and install them via the "Point'n'Print" mechanism supported by Samba. The clients use these drivers to generate print files in the -format the printer (or the Unix print system) requires. Print files -received by Samba are handed over to the Unix printing system, which +format the printer (or the UNIX print system) requires. Print files +received by Samba are handed over to the UNIX printing system, which is responsible for all further processing, if needed. -

    The [printer$] Section is removed from Samba-3

    +

    The [printer$] Section is removed from Samba 3

    [print$] vs. [printer$] .  Versions of Samba prior to 2.2 made it possible to use a share @@ -762,7 +700,7 @@ files associated with that printer. Another parameter named printer driver provided a means of defining the printer driver name to be sent to the client. These parameters, including the printer driver file parameter, -are now removed and can not be used in installations of Samba-3.0. +are now removed and can not be used in installations of samba-3. Now the share name [print$] is used for the location of downloadable printer drivers. It is taken from the [print$] service created by Windows NT PCs when @@ -772,7 +710,7 @@ access (in the context of its ACLs) in order to support printer driver down- and uploads. Don't fear -- this does not mean Windows 9x clients are thrown aside now. They can use Samba's [print$] share support just fine. -

    Creating the [print$] Share

    +

    Creating the [print$] Share

    In order to support the up- and downloading of printer driver files, you must first configure a file share named [print$]. The "public" name of this share is @@ -786,42 +724,25 @@ 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): -

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

    Parameters in the [print$] Section

    +path parameter exists on the UNIX file system. +

    Parameters in the [print$] Section

    [print$] is a special section in . It contains settings relevant to potential printer driver download and local installation by clients. -

    comment = Printer Driver -Download Area

    the comment appears next to the share name if it is +

    comment = Printer Driver + Download Area

    the comment appears next to the share name if it is listed in a share list (usually Windows clients won't see it often but it will also appear up in a smbclient -L sambaserver - output).

    path = /etc/samba/printers

    this is the path to the location of the Windows + output).

    path = /etc/samba/printers

    this is the path to the location of the Windows driver file deposit from the UNIX point of -view.

    browseable = no

    this makes the [print$] share +view.

    browseable = no

    this makes the [print$] share "invisible" in Network Neighbourhood to clients. However, you can still "mount" it from any client using the net use g:\\sambaserver\print$ command in a "DOS box" or the "Connect network drive" menu from Windows -Explorer.

    guest ok = yes

    this gives read only access to this share for all +Explorer.

    guest ok = yes

    this gives read only access to this share for all guest users. Access may be used to download and install printer drivers on clients. The requirement for guest ok = yes depends upon how your site is configured. If users @@ -834,13 +755,13 @@ validated by the Domain Controller in order to logon to the Windows NT session), then guest access is not necessary. Of course, in a workgroup environment where you just want to be able to print without worrying about silly accounts and security, then configure the share -for guest access. You'll probably want to add map to guest -= Bad User in the [global] section +for guest access. You'll probably want to add map to guest = Bad User in the +[global] section as well. Make sure you understand what this parameter does before using it. -

    read only = yes

    as we don't want everybody to upload driver files (or +

    read only = yes

    as we don't want everybody to upload driver files (or even change driver settings) we tagged this share as not -writeable.

    write list = @ntadmin,root

    since the [print$] was made +writeable.

    write list = @ntadmin,root

    since the [print$] was made read only by the previous setting, we need to create a "write list" also. UNIX groups (denoted with a leading "@" character) and users listed here are allowed write access (as an exception to the general @@ -849,13 +770,13 @@ share. Normally you will want to only name administrative level user accounts in this setting. Check the file system permissions to make sure these accounts 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 +printer admin parameter. See the man page for more information on -configuring file shares.

    Subdirectory Structure in [print$]

    +configuring file shares.

    Subdirectory Structure in [print$]

    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 +(i.e. the UNIX directory named by the path parameter). These correspond to each of the supported client architectures. Samba follows this model as well. Just like the name of the [print$] share itself, the subdirectories @@ -890,7 +811,7 @@ client workstation. Open Network Neighbourhood or Once you have located the server, navigate to its Printers and Faxes folder. You should see an initial listing of printers that matches the printer shares defined on your Samba host. -

    Installing Drivers into [print$]

    +

    Installing Drivers into [print$]

    You have successfully created the [print$] share in ? And Samba has re-read its configuration? Good. But you are not yet ready to take off. The @@ -908,11 +829,11 @@ Properties and Add Printer Wizard

    The latter option is probably the easier one (even if the only entrance to this realm seems a little bit weird at first). -

    Setting Drivers for existing Printers with a Client GUI

    +

    Setting Drivers for existing Printers with a Client GUI

    The initial listing of printers in the Samba host's Printers folder accessed from a client's Explorer -will have no real printer driver assigned to them. By default, in -Samba-3 (as in 2.2.1 and later) this driver name is set to a NULL +will have no real printer driver assigned to them. By default +this driver name is set to a NULL string. This must be changed now. The local Add Printer Wizard, run from NT/2000/XP clients, will help us in this task. @@ -943,18 +864,18 @@ Once the APW is started, the procedure is exactly the same as the one you are familiar with in Windows (we assume here that you are familiar with the printer driver installations procedure on Windows NT). Make sure your connection is in fact setup as a user with -printer admin privileges (if in doubt, use +printer admin privileges (if in doubt, use smbstatus to check for this). If you wish to install printer drivers for client operating systems other than Windows NT x86, you will need to use the Sharing tab of the printer properties dialog.

    Assuming you have connected with an administrative (or root) account -(as named by the printer admin parameter), +(as named by the printer admin parameter), you will also be able to modify other printer properties such as ACLs and default device settings using this dialog. For the default device settings, please consider the advice given further below. -

    Setting Drivers for existing Printers with +

    Setting Drivers for existing Printers with rpcclient

    The second way to install printer drivers into [print$] and set them up in a valid way can be @@ -969,7 +890,7 @@ time with the setdriver subcommand.

    We will provide detailed hints for each of these steps in the next few paragraphs. -

    Identifying the Driver Files

    +

    Identifying the Driver Files

    To find out about the driver files, you have two options: you could investigate the driver CD which comes with your printer. Study the *.inf file on the CD, if it is contained. This @@ -1017,35 +938,35 @@ create scripts to automate the procedure for a large number of printers and drivers. Note the different quotes used to overcome the different spaces in between words: 

    -root# rpcclient -U'Danka%xxxx' -c 'getdriver "Heidelberg Digimaster 9110 (PS)" 3' TURBO_XP
-  cmd = getdriver "Heidelberg Digimaster 9110 (PS)" 3
+root# rpcclient -U'Danka%xxxx' -c \
+	'getdriver "Heidelberg Digimaster 9110 (PS)" 3' TURBO_XP
+cmd = getdriver "Heidelberg Digimaster 9110 (PS)" 3
 
-  [Windows NT x86]
-  Printer Driver Info 3:
-          Version: [2]
-          Driver Name: [Heidelberg Digimaster 9110 (PS)]
-          Architecture: [Windows NT x86]
-          Driver Path: [C:\WINNT\System32\spool\DRIVERS\W32X86\2\HDNIS01_de.DLL]
-          Datafile: [C:\WINNT\System32\spool\DRIVERS\W32X86\2\Hddm91c1_de.ppd]
-          Configfile: [C:\WINNT\System32\spool\DRIVERS\W32X86\2\HDNIS01U_de.DLL]
-          Helpfile: [C:\WINNT\System32\spool\DRIVERS\W32X86\2\HDNIS01U_de.HLP]
+[Windows NT x86]
+Printer Driver Info 3:
+  Version: [2]
+  Driver Name: [Heidelberg Digimaster 9110 (PS)]
+  Architecture: [Windows NT x86]
+  Driver Path: [C:\WINNT\System32\spool\DRIVERS\W32X86\2\HDNIS01_de.DLL]
+  Datafile: [C:\WINNT\System32\spool\DRIVERS\W32X86\2\Hddm91c1_de.ppd]
+  Configfile: [C:\WINNT\System32\spool\DRIVERS\W32X86\2\HDNIS01U_de.DLL]
+  Helpfile: [C:\WINNT\System32\spool\DRIVERS\W32X86\2\HDNIS01U_de.HLP]
   
-          Dependentfiles: [C:\WINNT\System32\spool\DRIVERS\W32X86\2\Hddm91c1_de.DLL]
-          Dependentfiles: [C:\WINNT\System32\spool\DRIVERS\W32X86\2\Hddm91c1_de.INI]
-          Dependentfiles: [C:\WINNT\System32\spool\DRIVERS\W32X86\2\Hddm91c1KMMin.DLL]
-          Dependentfiles: [C:\WINNT\System32\spool\DRIVERS\W32X86\2\Hddm91c1_de.dat]
-          Dependentfiles: [C:\WINNT\System32\spool\DRIVERS\W32X86\2\Hddm91c1_de.cat]
-          Dependentfiles: [C:\WINNT\System32\spool\DRIVERS\W32X86\2\Hddm91c1_de.def]
-          Dependentfiles: [C:\WINNT\System32\spool\DRIVERS\W32X86\2\Hddm91c1_de.hre]
-          Dependentfiles: [C:\WINNT\System32\spool\DRIVERS\W32X86\2\Hddm91c1_de.vnd]
-          Dependentfiles: [C:\WINNT\System32\spool\DRIVERS\W32X86\2\Hddm91c1_de.hlp]
-          Dependentfiles: [C:\WINNT\System32\spool\DRIVERS\W32X86\2\Hddm91c1_de_reg.HLP]
-          Dependentfiles: [C:\WINNT\System32\spool\DRIVERS\W32X86\2\HDNIS01Aux.dll]
-          Dependentfiles: [C:\WINNT\System32\spool\DRIVERS\W32X86\2\HDNIS01_de.NTF]
+  Dependentfiles: [C:\WINNT\System32\spool\DRIVERS\W32X86\2\Hddm91c1_de.DLL]
+  Dependentfiles: [C:\WINNT\System32\spool\DRIVERS\W32X86\2\Hddm91c1_de.INI]
+  Dependentfiles: [C:\WINNT\System32\spool\DRIVERS\W32X86\2\Hddm91c1KMMin.DLL]
+  Dependentfiles: [C:\WINNT\System32\spool\DRIVERS\W32X86\2\Hddm91c1_de.dat]
+  Dependentfiles: [C:\WINNT\System32\spool\DRIVERS\W32X86\2\Hddm91c1_de.cat]
+  Dependentfiles: [C:\WINNT\System32\spool\DRIVERS\W32X86\2\Hddm91c1_de.def]
+  Dependentfiles: [C:\WINNT\System32\spool\DRIVERS\W32X86\2\Hddm91c1_de.hre]
+  Dependentfiles: [C:\WINNT\System32\spool\DRIVERS\W32X86\2\Hddm91c1_de.vnd]
+  Dependentfiles: [C:\WINNT\System32\spool\DRIVERS\W32X86\2\Hddm91c1_de.hlp]
+  Dependentfiles: [C:\WINNT\System32\spool\DRIVERS\W32X86\2\Hddm91c1_de_reg.HLP]
+  Dependentfiles: [C:\WINNT\System32\spool\DRIVERS\W32X86\2\HDNIS01Aux.dll]
+  Dependentfiles: [C:\WINNT\System32\spool\DRIVERS\W32X86\2\HDNIS01_de.NTF]
   
-          Monitorname: []
-          Defaultdatatype: []
-
+  Monitorname: []
+  Defaultdatatype: []

    You may notice, that this driver has quite a big number of Dependentfiles (I know worse cases however). Also, @@ -1072,7 +993,7 @@ Windows 2000 changed this. While it still can use the Kernel Mode drivers (if this is enabled by the Admin), its native mode for printer drivers is User Mode execution. This requires drivers designed for this. These type of drivers install into the "3" subdirectory. -

    Collecting the Driver Files from a Windows Host's +

    Collecting the Driver Files from a Windows Host's [print$] Share

    Now we need to collect all the driver files we identified. in our previous step. Where do we get them from? Well, why not retrieve them @@ -1085,15 +1006,15 @@ listing is edited to include linebreaks for readability: root# smbclient //TURBO_XP/print\$ -U'Danka%xxxx' \ -c 'cd W32X86/2;mget HD*_de.* \ hd*ppd Hd*_de.* Hddm*dll HDN*Aux.DLL' - added interface ip=10.160.51.60 bcast=10.160.51.255 nmask=255.255.252.0 - Got a positive name query response from 10.160.50.8 ( 10.160.50.8 ) - Domain=[DEVELOPMENT] OS=[Windows 5.1] Server=[Windows 2000 LAN Manager] - Get file Hddm91c1_de.ABD? n - Get file Hddm91c1_de.def? y - getting file \W32X86\2\Hddm91c1_de.def of size 428 as Hddm91c1_de.def (22.0 kb/s) (average 22.0 kb/s) - Get file Hddm91c1_de.DLL? y - getting file \W32X86\2\Hddm91c1_de.DLL of size 876544 as Hddm91c1_de.DLL (737.3 kb/s) (average 737.3 kb/s) - [...] +added interface ip=10.160.51.60 bcast=10.160.51.255 nmask=255.255.252.0 +Got a positive name query response from 10.160.50.8 ( 10.160.50.8 ) +Domain=[DEVELOPMENT] OS=[Windows 5.1] Server=[Windows 2000 LAN Manager] +Get file Hddm91c1_de.ABD? n +Get file Hddm91c1_de.def? y +getting file \W32X86\2\Hddm91c1_de.def of size 428 as Hddm91c1_de.def +Get file Hddm91c1_de.DLL? y +getting file \W32X86\2\Hddm91c1_de.DLL of size 876544 as Hddm91c1_de.DLL +[...]

    After this command is complete, the files are in our current local @@ -1108,7 +1029,7 @@ files for these architectures are in the WIN40/0/ subdir. Once we are complete, we can run smbclient ... put to store the collected files on the Samba server's [print$] share. -

    Depositing the Driver Files into [print$]

    +

    Depositing the Driver Files into [print$]

    So, now we are going to put the driver files into the [print$] share. Remember, the UNIX path to this share has been defined previously in your @@ -1129,7 +1050,8 @@ running getdriver against the original store the files into a Samba/UNIX print server's [print$] share... 

    -root# smbclient //SAMBA-CUPS/print\$ -U'root%xxxx' -c 'cd W32X86; put HDNIS01_de.DLL; \
+		root# smbclient //SAMBA-CUPS/print\$ -U'root%xxxx' -c \
+ 'cd W32X86; put HDNIS01_de.DLL; \
   put Hddm91c1_de.ppd; put HDNIS01U_de.DLL;        \
   put HDNIS01U_de.HLP; put Hddm91c1_de.DLL;        \
   put Hddm91c1_de.INI; put Hddm91c1KMMin.DLL;      \
@@ -1138,26 +1060,25 @@ store the files into a Samba/UNIX print s
   put Hddm91c1_de.vnd; put Hddm91c1_de.hlp;        \
   put Hddm91c1_de_reg.HLP; put HDNIS01Aux.dll;     \
   put HDNIS01_de.NTF'
- added interface ip=10.160.51.60 bcast=10.160.51.255 nmask=255.255.252.0
- Got a positive name query response from 10.160.51.162 ( 10.160.51.162 )
- Domain=[CUPS-PRINT] OS=[Unix] Server=[Samba 2.2.7a]
- putting file HDNIS01_de.DLL as \W32X86\HDNIS01_de.DLL (4465.5 kb/s) (average 4465.5 kb/s)
- putting file Hddm91c1_de.ppd as \W32X86\Hddm91c1_de.ppd (12876.8 kb/s) (average 4638.9 kb/s)
- putting file HDNIS01U_de.DLL as \W32X86\HDNIS01U_de.DLL (20249.8 kb/s) (average 5828.3 kb/s)
- putting file HDNIS01U_de.HLP as \W32X86\HDNIS01U_de.HLP (9652.8 kb/s) (average 5899.8 kb/s)
- putting file Hddm91c1_de.DLL as \W32X86\Hddm91c1_de.DLL (23777.7 kb/s) (average 10400.6 kb/s)
- putting file Hddm91c1_de.INI as \W32X86\Hddm91c1_de.INI (98.6 kb/s) (average 10329.0 kb/s)
- putting file Hddm91c1KMMin.DLL as \W32X86\Hddm91c1KMMin.DLL (22931.5 kb/s) (average 10501.7 kb/s)
- putting file Hddm91c1_de.dat as \W32X86\Hddm91c1_de.dat (2462.8 kb/s) (average 10393.0 kb/s)
- putting file Hddm91c1_de.dat as \W32X86\Hddm91c1_de.dat (4925.3 kb/s) (average 10356.3 kb/s)
- putting file Hddm91c1_de.def as \W32X86\Hddm91c1_de.def (417.9 kb/s) (average 10290.1 kb/s)
- putting file Hddm91c1_de.hre as \W32X86\Hddm91c1_de.hre (22571.3 kb/s) (average 11338.5 kb/s)
- putting file Hddm91c1_de.vnd as \W32X86\Hddm91c1_de.vnd (3384.6 kb/s) (average 10754.3 kb/s)
- putting file Hddm91c1_de.hlp as \W32X86\Hddm91c1_de.hlp (18406.8 kb/s) (average 10839.8 kb/s)
- putting file Hddm91c1_de_reg.HLP as \W32X86\Hddm91c1_de_reg.HLP (20278.3 kb/s) (average 11386.3 kb/s)
- putting file HDNIS01Aux.dll as \W32X86\HDNIS01Aux.dll (14994.6 kb/s) (average 11405.2 kb/s)
- putting file HDNIS01_de.NTF as \W32X86\HDNIS01_de.NTF (23390.2 kb/s) (average 13170.8 kb/s)
-
+added interface ip=10.160.51.60 bcast=10.160.51.255 nmask=255.255.252.0
+Got a positive name query response from 10.160.51.162 ( 10.160.51.162 )
+Domain=[CUPS-PRINT] OS=[UNIX] Server=[Samba 2.2.7a]
+putting file HDNIS01_de.DLL as \W32X86\HDNIS01_de.DLL
+putting file Hddm91c1_de.ppd as \W32X86\Hddm91c1_de.ppd
+putting file HDNIS01U_de.DLL as \W32X86\HDNIS01U_de.DLL
+putting file HDNIS01U_de.HLP as \W32X86\HDNIS01U_de.HLP
+putting file Hddm91c1_de.DLL as \W32X86\Hddm91c1_de.DLL
+putting file Hddm91c1_de.INI as \W32X86\Hddm91c1_de.INI
+putting file Hddm91c1KMMin.DLL as \W32X86\Hddm91c1KMMin.DLL
+putting file Hddm91c1_de.dat as \W32X86\Hddm91c1_de.dat
+putting file Hddm91c1_de.dat as \W32X86\Hddm91c1_de.dat
+putting file Hddm91c1_de.def as \W32X86\Hddm91c1_de.def
+putting file Hddm91c1_de.hre as \W32X86\Hddm91c1_de.hre
+putting file Hddm91c1_de.vnd as \W32X86\Hddm91c1_de.vnd
+putting file Hddm91c1_de.hlp as \W32X86\Hddm91c1_de.hlp
+putting file Hddm91c1_de_reg.HLP as \W32X86\Hddm91c1_de_reg.HLP
+putting file HDNIS01Aux.dll as \W32X86\HDNIS01Aux.dll
+putting file HDNIS01_de.NTF as \W32X86\HDNIS01_de.NTF

    Phewww -- that was a lot of typing! Most drivers are a lot smaller -- many only having 3 generic PostScript driver files plus 1 PPD. Note, @@ -1169,47 +1090,47 @@ re-location will automatically be done by the don't forget to also put the files for the Win95/98/ME architecture into the WIN40/ subdirectory should you need them). -

    Check if the Driver Files are there (with smbclient)

    +

    Check if the Driver Files are there (with smbclient)

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

    -root# smbclient //SAMBA-CUPS/print\$ -U 'root%xxxx' -c 'cd W32X86; pwd; dir; cd 2; pwd; dir'
+root# smbclient //SAMBA-CUPS/print\$ -U 'root%xxxx' \
+	-c 'cd W32X86; pwd; dir; cd 2; pwd; dir'
  added interface ip=10.160.51.60 bcast=10.160.51.255 nmask=255.255.252.0
- Got a positive name query response from 10.160.51.162 ( 10.160.51.162 )
- Domain=[CUPS-PRINT] OS=[Unix] Server=[Samba 2.2.7a]
+Got a positive name query response from 10.160.51.162 ( 10.160.51.162 )
+Domain=[CUPS-PRINT] OS=[UNIX] Server=[Samba 2.2.7a]
 
-  Current directory is \\SAMBA-CUPS\print$\W32X86\
-  .                                   D        0  Sun May  4 03:56:35 2003
-  ..                                  D        0  Thu Apr 10 23:47:40 2003
-  2                                   D        0  Sun May  4 03:56:18 2003
-  HDNIS01Aux.dll                      A    15356  Sun May  4 03:58:59 2003
-  Hddm91c1KMMin.DLL                   A    46966  Sun May  4 03:58:59 2003
-  HDNIS01_de.DLL                      A   434400  Sun May  4 03:58:59 2003
-  HDNIS01_de.NTF                      A   790404  Sun May  4 03:56:35 2003
-  Hddm91c1_de.DLL                     A   876544  Sun May  4 03:58:59 2003
-  Hddm91c1_de.INI                     A      101  Sun May  4 03:58:59 2003
-  Hddm91c1_de.dat                     A     5044  Sun May  4 03:58:59 2003
-  Hddm91c1_de.def                     A      428  Sun May  4 03:58:59 2003
-  Hddm91c1_de.hlp                     A    37699  Sun May  4 03:58:59 2003
-  Hddm91c1_de.hre                     A   323584  Sun May  4 03:58:59 2003
-  Hddm91c1_de.ppd                     A    26373  Sun May  4 03:58:59 2003
-  Hddm91c1_de.vnd                     A    45056  Sun May  4 03:58:59 2003
-  HDNIS01U_de.DLL                     A   165888  Sun May  4 03:58:59 2003
-  HDNIS01U_de.HLP                     A    19770  Sun May  4 03:58:59 2003
-  Hddm91c1_de_reg.HLP                 A   228417  Sun May  4 03:58:59 2003
-                40976 blocks of size 262144. 709 blocks available
-
-  Current directory is \\SAMBA-CUPS\print$\W32X86\2\
-  .                                   D        0  Sun May  4 03:56:18 2003
-  ..                                  D        0  Sun May  4 03:56:35 2003
-  ADOBEPS5.DLL                        A   434400  Sat May  3 23:18:45 2003
-  laserjet4.ppd                       A     9639  Thu Apr 24 01:05:32 2003
-  ADOBEPSU.DLL                        A   109568  Sat May  3 23:18:45 2003
-  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
+Current directory is \\SAMBA-CUPS\print$\W32X86\
+.                                   D        0  Sun May  4 03:56:35 2003
+..                                  D        0  Thu Apr 10 23:47:40 2003
+2                                   D        0  Sun May  4 03:56:18 2003
+HDNIS01Aux.dll                      A    15356  Sun May  4 03:58:59 2003
+Hddm91c1KMMin.DLL                   A    46966  Sun May  4 03:58:59 2003
+HDNIS01_de.DLL                      A   434400  Sun May  4 03:58:59 2003
+HDNIS01_de.NTF                      A   790404  Sun May  4 03:56:35 2003
+Hddm91c1_de.DLL                     A   876544  Sun May  4 03:58:59 2003
+Hddm91c1_de.INI                     A      101  Sun May  4 03:58:59 2003
+Hddm91c1_de.dat                     A     5044  Sun May  4 03:58:59 2003
+Hddm91c1_de.def                     A      428  Sun May  4 03:58:59 2003
+Hddm91c1_de.hlp                     A    37699  Sun May  4 03:58:59 2003
+Hddm91c1_de.hre                     A   323584  Sun May  4 03:58:59 2003
+Hddm91c1_de.ppd                     A    26373  Sun May  4 03:58:59 2003
+Hddm91c1_de.vnd                     A    45056  Sun May  4 03:58:59 2003
+HDNIS01U_de.DLL                     A   165888  Sun May  4 03:58:59 2003
+HDNIS01U_de.HLP                     A    19770  Sun May  4 03:58:59 2003
+Hddm91c1_de_reg.HLP                 A   228417  Sun May  4 03:58:59 2003
+              40976 blocks of size 262144. 709 blocks available
 
+Current directory is \\SAMBA-CUPS\print$\W32X86\2\
+.                                   D        0  Sun May  4 03:56:18 2003
+..                                  D        0  Sun May  4 03:56:35 2003
+ADOBEPS5.DLL                        A   434400  Sat May  3 23:18:45 2003
+laserjet4.ppd                       A     9639  Thu Apr 24 01:05:32 2003
+ADOBEPSU.DLL                        A   109568  Sat May  3 23:18:45 2003
+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 subdir (probably from a previous @@ -1222,7 +1143,7 @@ Point'n'Print. The reason is: Samba doesn't know yet that these files are something special, namely printer driver files and it doesn't know yet to which print queue(s) these driver files belong. -

    Running rpcclient with +

    Running rpcclient with adddriver

    So, next you must tell Samba about the special category of the files you just uploaded into the [print$] share. This @@ -1231,21 +1152,23 @@ prompt Samba to register the driver files into its internal TDB database files. The following command and its output has been edited, again, for readability: 

    -root# rpcclient -Uroot%xxxx -c 'adddriver "Windows NT x86" "dm9110:HDNIS01_de.DLL: \
-  Hddm91c1_de.ppd:HDNIS01U_de.DLL:HDNIS01U_de.HLP:   \
-  NULL:RAW:Hddm91c1_de.DLL,Hddm91c1_de.INI,          \
-  Hddm91c1_de.dat,Hddm91c1_de.def,Hddm91c1_de.hre,   \
-  Hddm91c1_de.vnd,Hddm91c1_de.hlp,Hddm91c1KMMin.DLL, \
-  HDNIS01Aux.dll,HDNIS01_de.NTF,                     \
-  Hddm91c1_de_reg.HLP' SAMBA-CUPS
+		root# rpcclient -Uroot%xxxx -c 'adddriver "Windows NT x86" \
+"dm9110:HDNIS01_de.DLL: \
+Hddm91c1_de.ppd:HDNIS01U_de.DLL:HDNIS01U_de.HLP:   \
+ NULL:RAW:Hddm91c1_de.DLL,Hddm91c1_de.INI,          \
+ Hddm91c1_de.dat,Hddm91c1_de.def,Hddm91c1_de.hre,   \
+ Hddm91c1_de.vnd,Hddm91c1_de.hlp,Hddm91c1KMMin.DLL, \
+ HDNIS01Aux.dll,HDNIS01_de.NTF,                     \
+ Hddm91c1_de_reg.HLP' SAMBA-CUPS
 
- cmd = adddriver "Windows NT x86" "dm9110:HDNIS01_de.DLL:Hddm91c1_de.ppd:HDNIS01U_de.DLL:    \
-  HDNIS01U_de.HLP:NULL:RAW:Hddm91c1_de.DLL,Hddm91c1_de.INI, \
-  Hddm91c1_de.dat,Hddm91c1_de.def,Hddm91c1_de.hre,          \
-  Hddm91c1_de.vnd,Hddm91c1_de.hlp,Hddm91c1KMMin.DLL,        \
-  HDNIS01Aux.dll,HDNIS01_de.NTF,Hddm91c1_de_reg.HLP"
+cmd = adddriver "Windows NT x86" \
+"dm9110:HDNIS01_de.DLL:Hddm91c1_de.ppd:HDNIS01U_de.DLL:    \
+ HDNIS01U_de.HLP:NULL:RAW:Hddm91c1_de.DLL,Hddm91c1_de.INI, \
+ Hddm91c1_de.dat,Hddm91c1_de.def,Hddm91c1_de.hre,          \
+ Hddm91c1_de.vnd,Hddm91c1_de.hlp,Hddm91c1KMMin.DLL,        \
+ HDNIS01Aux.dll,HDNIS01_de.NTF,Hddm91c1_de_reg.HLP"
 
- Printer Driver dm9110 successfully installed.
+Printer Driver dm9110 successfully installed.

    After this step the driver should be recognized by Samba on the print @@ -1257,7 +1180,7 @@ files successfully, but render the driver unworkable. So take care! Hints about the syntax of the adddriver command are in the man page. The CUPS printing chapter of this HOWTO collection provides a more detailed description, if you should need it. -

    Check how Driver Files have been moved after +

    Check how Driver Files have been moved after adddriver finished

    One indication for Samba's recognition of the files as driver files is the successfully installed message. @@ -1266,9 +1189,9 @@ Another one is the fact, that our files have been moved by the subdirectory. You can check this again with smbclient: 

    -root# smbclient //SAMBA-CUPS/print\$ -Uroot%xxxx -c 'cd W32X86;dir;pwd;cd 2;dir;pwd'
+root# smbclient //SAMBA-CUPS/print\$ -Uroot%xx -c 'cd W32X86;dir;pwd;cd 2;dir;pwd'
  added interface ip=10.160.51.162 bcast=10.160.51.255 nmask=255.255.252.0
- Domain=[CUPS-PRINT] OS=[Unix] Server=[Samba 2.2.7a]
+ Domain=[CUPS-PRINT] OS=[UNIX] Server=[Samba 2.2.7a]
 
   Current directory is \\SAMBA-CUPS\print$\W32X86\
   .                                   D        0  Sun May  4 04:32:48 2003
@@ -1305,7 +1228,7 @@ subdirectory. You can check this again with

    Another verification is that the timestamp of the printing TDB files is now updated (and possibly their filesize has increased). -

    Check if the Driver is recognized by Samba

    +

    Check if the Driver is recognized by Samba

    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 @@ -1349,19 +1272,19 @@ time. Our new driver only shows up 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. -

    A side note: you are not bound to specific driver names

    +

    A side note: you are not bound to specific driver names

    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: 

     root# rpcclient -Uroot%xxxx                                        \
-      -c 'adddriver "Windows NT x86"                     \
-      "myphantasydrivername:HDNIS01_de.DLL:              \
-      Hddm91c1_de.ppd:HDNIS01U_de.DLL:HDNIS01U_de.HLP:   \
-      NULL:RAW:Hddm91c1_de.DLL,Hddm91c1_de.INI,          \
-      Hddm91c1_de.dat,Hddm91c1_de.def,Hddm91c1_de.hre,   \
-      Hddm91c1_de.vnd,Hddm91c1_de.hlp,Hddm91c1KMMin.DLL, \
-      HDNIS01Aux.dll,HDNIS01_de.NTF,Hddm91c1_de_reg.HLP' SAMBA-CUPS
+  -c 'adddriver "Windows NT x86"                     \
+  "myphantasydrivername:HDNIS01_de.DLL:              \
+  Hddm91c1_de.ppd:HDNIS01U_de.DLL:HDNIS01U_de.HLP:   \
+  NULL:RAW:Hddm91c1_de.DLL,Hddm91c1_de.INI,          \
+  Hddm91c1_de.dat,Hddm91c1_de.def,Hddm91c1_de.hre,   \
+  Hddm91c1_de.vnd,Hddm91c1_de.hlp,Hddm91c1KMMin.DLL, \
+  HDNIS01Aux.dll,HDNIS01_de.NTF,Hddm91c1_de_reg.HLP' SAMBA-CUPS
   
 
  cmd = adddriver "Windows NT x86" 
@@ -1383,7 +1306,7 @@ repeatedly. Each run "consumes" the files you had put into the
 respective subdirectories. So you must precede an
 smbclient ... put command before each
 rpcclient ...  adddriver" command.
-

    La Grande Finale: Running rpcclient with +

    Running rpcclient with setdriver

    Samba still needs to know which printer's driver this is. It needs to create a mapping of the driver to a printer, and @@ -1413,20 +1336,19 @@ known to Samba already. A bug in 2.2.x prevented Samba from recognizing freshly installed printers. You had to restart Samba, or at least send a HUP signal to all running smbd processes to work around this: -kill -HUP `pidof smbd`.

    "The Proof of the Pudding lies in the Eating" (Client Driver Install -Procedure)

    +kill -HUP `pidof smbd`.

    Client Driver Install Procedure

    A famous philosopher said once: “The Proof of the Pudding lies 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. -

    The first Client Driver Installation

    +

    The 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 setup and shouldn't need further attention. What follows is a description for the recommended first procedure. You work now from a client workstation. First you should guarantee that your connection is not unwittingly mapped to -bad user "nobody". In a DOS box type: +bad user "nobody". In a DOS box type:

    net use \\SAMBA-SERVER\print$ /user:root

    Replace root, if needed, by another valid printer admin user as given in the definition. @@ -1462,7 +1384,7 @@ Data" set is still incomplete.

    You must now make sure that a valid "Device Mode" is set for the driver. Don't fear -- we will explain now what that means. -

    IMPORTANT! Setting Device Modes on new Printers

    +

    IMPORTANT! Setting Device Modes on new Printers

    In order for a printer to be truly usable by a Windows NT/2K/XP client, it must possess:

    • a valid Device Mode generated by @@ -1489,7 +1411,7 @@ This can be achieved by accessing the drivers remotely from an NT (or 2k/XP) client, as is discussed in the next paragraphs.

      Be aware, that a valid Device Mode can only be initiated by a -printer admin, or root (the reason should be +printer admin, or root (the reason should be obvious). Device Modes can only correctly be set by executing the printer driver program itself. Since Samba can not execute this Win32 platform driver code, it sets this field initially to NULL (which is @@ -1534,7 +1456,7 @@ 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. -

    Further Client Driver Install Procedures

    +

    Further Client Driver Install Procedures

    Every further driver may be done by any user, along the lines described above: Browse network, open printers folder on Samba server, right-click printer and choose Connect.... Once @@ -1554,12 +1476,12 @@ 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 that the very first connection from a client as -printer admin. This is to make sure that: +printer admin. This is to make sure that:

    • a first valid Device Mode is really initialized (see above for more explanation details), and that

    • the default print settings of your printer for all @@ -1573,20 +1495,23 @@ set to Letter, when you are all using

      To connect as root to a Samba printer, try this command from a Windows 2K/XP DOS box command prompt: -

      runas /netonly /user:root "rundll32 printui.dll,PrintUIEntry /p /t3 /n \\SAMBA-SERVER\printername" +

      +C:\> runas /netonly /user:root "rundll32 printui.dll,PrintUIEntry /p /t3 /n 
+	\\SAMBA-SERVER\printername"
+

      You will be prompted for root's Samba-password; type it, wait a few seconds, click on Printing Defaults... and proceed to set the job options as should be used as defaults by all clients. Alternatively, instead of root you can name one other member -of the printer admins from the setting. +of the printer admin from the setting.

      Now all the other users downloading and installing the driver the same way (called Point'n'Print) will have the same defaults set for them. If you miss this step you'll get a lot of helpdesk calls from your users. But maybe you like to talk to people.... ;-) -

    Other Gotchas

    +

    Other Gotchas

    Your driver is installed. It is ready for Point'n'Print installation by the clients now. You may have tried to download and use it @@ -1596,7 +1521,7 @@ example, suppose you didn't manage to "set the defaults" on the printer, as advised in the preceding paragraphs? And your users complain about various issues (such as “We need to set the paper size for each job from Letter to A4 and it won't store it!”) -

    Setting Default Print Options for the Client Drivers

    +

    Setting Default Print Options for the Client Drivers

    The last sentence might be viewed with mixed feelings by some users and admins. They have struggled for hours and hours and couldn't arrive at a point were their settings seemed to be saved. It is not their @@ -1651,7 +1576,7 @@ either. However, only the last one, which you arrived at with steps C.1.-6. will permanently save any settings which will then become the defaults for new users. If you want all clients to have the same defaults, you need to conduct these steps as administrator -(printer admin in ) +(printer admin in ) before a client downloads the driver (the clients can later set their own per-user defaults by following the procedures A. @@ -1685,7 +1610,7 @@ to see the tab with the Printing Preferences... button (the one which doesn't set system-wide defaults). You can start the commands from inside a DOS box" or from the Start -- Run... menu. -

    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 100's of printers. Using Windows NT APW here is somewhat awkward (to say the least). If you @@ -1735,7 +1660,8 @@ following is an example of how this could be accomplished: 

    -root# rpcclient SAMBA-CUPS -U root%secret -c 'setdriver dm9110 "Heidelberg Digimaster 9110 (PS)"'
+root# rpcclient SAMBA-CUPS -U root%secret -c \
+  'setdriver dm9110 "Heidelberg Digimaster 9110 (PS)"'
  cmd = setdriver dm9110 Heidelberg Digimaster 9110 (PPD)
  Successfully set dm9110 to driver Heidelberg Digimaster 9110 (PS).

    @@ -1745,7 +1671,8 @@ following is an example of how this could be accomplished: cmd = enumprinters flags:[0x800000] name:[\\SAMBA-CUPS\dm9110] - description:[\\SAMBA-CUPS\dm9110,Heidelberg Digimaster 9110 (PS),110ppm HiVolume DANKA Stuttgart] + description:[\\SAMBA-CUPS\dm9110,Heidelberg Digimaster 9110 (PS),\ + 110ppm HiVolume DANKA Stuttgart] comment:[110ppm HiVolume DANKA Stuttgart] [....]

    @@ -1761,7 +1688,8 @@ following is an example of how this could be accomplished: cmd = enumprinters flags:[0x800000] name:[\\SAMBA-CUPS\dm9110] - description:[\\SAMBA-CUPS\dm9110,myphantasydrivername,110ppm HiVolume DANKA Stuttgart] + description:[\\SAMBA-CUPS\dm9110,myphantasydrivername,\ + 110ppm HiVolume DANKA Stuttgart] comment:[110ppm HiVolume DANKA Stuttgart] [....]

    @@ -1772,7 +1700,7 @@ commas in the "description" field). After the setdriver command succeeded, all is well. (The CUPS Printing chapter has more info about the installation of printer drivers with the help of rpcclient). -

    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 @@ -1780,29 +1708,29 @@ is the Windows NT Add Printer Wizard icon. The APW will be shown only if:

    • ...the connected user is able to successfully execute an OpenPrinterEx(\\server) with administrative -privileges (i.e. root or printer admin). +privileges (i.e. root or printer admin).

      Tip

      Try this from a Windows 2K/XP DOS box command prompt:

      runas /netonly /user:root rundll32 printui.dll,PrintUIEntry /p /t0 /n \\SAMBA-SERVER\printersharename

      and click on Printing Preferences...

    • ... contains the setting -show add printer wizard = yes (the +show add printer wizard = yes (the default).

    The APW can do various things:

    • upload a new driver to the Samba [print$] share;

    • associate an uploaded driver with an existing (but still "driverless") print queue;

    • exchange the currently used driver for an existing print queue with one that has been uploaded before;

    • add an entirely new printer to the Samba host (only in -conjunction with a working add printer command; -a corresponding delete printer command for +conjunction with a working add printer command; +a corresponding delete printer command for removing entries from the Printers... folder may be provided too)

    The last one (add a new printer) requires more effort than the previous ones. In order to use the APW to successfully add a printer -to a Samba server, the add printer command must +to a Samba server, the add printer command must have a defined value. The program hook must successfully add the -printer to the Unix print system (i.e. to +printer to the UNIX print system (i.e. to /etc/printcap, /etc/cups/printers.conf or other appropriate files) and to if necessary. @@ -1812,13 +1740,11 @@ exist, smbd will execute the add printer command and reparse to the to attempt to locate the new printer share. If the share is still not defined, an error of Access Denied is -returned to the client. Note that the add printer -command is executed under the context of the connected -user, not necessarily a root account. A map to guest = bad -user may have connected you unwittingly under the wrong +returned to the client. Note that the add printer command is executed under the context of the connected +user, not 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. -

    Weird Error Message Cannot connect under a +

    Weird 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 @@ -1848,7 +1774,7 @@ message. You close all Explorer Windows and start it again. You try to connect - and this times it works! Windows seems to cache connection info somewhere and doesn't keep it up to date (if you are unlucky you might need to reboot to get rid of the error message). -

    Be careful when assembling Driver Files

    +

    Be careful when assembling Driver Files

    You need to be very careful when you take notes about the files and belonging to a particular driver. Don't confuse the files for driver version "0" (for Win95/98/ME, going into @@ -1989,7 +1915,7 @@ In my example were even more differences than shown here. Conclusion: you must be very careful to select the correct driver files for each driver version. Don't rely on the names alone. 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:, etc. Samba @@ -2008,20 +1934,20 @@ multiple ports as a form of load balancing or fail over. If you require that multiple ports be defined for some reason or another (“My users and my Boss should not know that they are working with Samba”), possesses a -enumports command which can be used to define +enumports command which can be used to define an external program that generates a listing of ports on a system. -

    Avoiding the most common Misconfigurations of the Client Driver

    +

    Avoiding the most common Misconfigurations of the Client Driver

    So - printing works, but there are still problems. Most jobs print well, some don't print at all. Some jobs have problems with fonts, which don't look good at all. Some jobs print fast, and some are dead-slow. We can't cover it all; but we want to encourage you to read the little paragraph about "Avoiding the wrong PostScript Driver Settings" in the CUPS Printing part of this document. -

    The Imprints Toolset

    +

    The Imprints Toolset

    The Imprints tool set provides a UNIX equivalent of the Windows NT Add Printer Wizard. For complete information, please refer to the Imprints web site -athttp://imprints.sourceforge.net/ +at http://imprints.sourceforge.net/ as well as the documentation included with the imprints source distribution. This section will only provide a brief introduction to the features of Imprints. @@ -2034,20 +1960,20 @@ coordinate your efforts on the samba-technical 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.

    What is Imprints?

    +future.

    What is Imprints?

    Imprints is a collection of tools for supporting these goals:

    • Providing a central repository information regarding Windows NT and 95/98 printer driver packages

    • Providing the tools necessary for creating the Imprints printer driver packages.

    • Providing an installation client which 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

    +servers.

    Creating Printer Driver Packages

    The process of creating printer driver packages is beyond the scope of this document (refer to Imprints.txt also 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 @@ -2055,7 +1981,7 @@ package is digitally signed via GnuPG which can be used to verify that 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 in the Imprints-Client-HOWTO.ps file included with the imprints source package. @@ -2096,7 +2022,7 @@ if is has not already been installed? 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 NT driver is installed first. -

    Add Network Printers at Logon without User Interaction

    +

    Add Network Printers at Logon 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. ( http://support.microsoft.com/default.aspx?scid=kb;en-us;189105 @@ -2121,13 +2047,7 @@ printers via Samba, but works for Windows-based print servers too): rundll32 printui.dll,PrintUIEntry /y /n "\\sambacupsserver\infotec2105-PS"

    Here is a list of the used commandline parameters: -

    /dn

    deletes a network printer

    /q

    quiet modus

    /n

    names a printer

    /in

    adds a network printer connection

    /y

    sets printer as default printer

    -I have tested this with a Samba 2.2.7a and a Samba-3alpha24 -installation and Windows XP Professional clients. Note that this -specific command set works with network print queues (installing -local print queues requires different parameters, but this is of no -interest here). -

    • Line 1 deletes a possibly existing previous network +

      /dn

      deletes a network printer

      /q

      quiet modus

      /n

      names a printer

      /in

      adds a network printer connection

      /y

      sets printer as default printer

      • Line 1 deletes a possibly existing previous network printer infotec2105-IPDS (which had used native Windows drivers with LPRng that were removed from the server which was converted to CUPS). The /q at the end eliminates @@ -2171,7 +2091,7 @@ 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 on 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 @@ -2183,7 +2103,7 @@ on legacy systems, or execute the lpadmin command on more modern systems) and create the associated share in , then the APW will in effect really create a new printer on Samba and the UNIX print subsystem! -

      Migration of "Classical" printing to Samba-3

      +

      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 @@ -2194,14 +2114,13 @@ is more of an effort. Please read the appropriate release notes and the HOWTO Collection for 2.2. You can follow several paths. Here are possible scenarios for migration:

      • You need to study and apply the new Windows NT printer -and driver support. Previously used parameters "printer -driver file", " printer driver" and -"printer driver location" are no longer +and driver support. Previously used parameters printer +driver file, printer driver and +printer driver location are no longer supported.

      • If you want to take advantage of WinNT printer driver support you also need to migrate the Win9x/ME drivers to the new setup.

      • An existing printers.def file -(the one specified in the now removed parameter printer -driver file = ...) will work no longer with Samba-3.0. In + (the one specified in the now removed parameter printer driver file) will work no longer with samba 3. In 3.0, smbd attempts to locate a Win9x/ME driver files for the printer in [print$] and additional settings in the TDB and only there; if it fails it will not (as 2.2.x @@ -2217,24 +2136,21 @@ only solution is to use the Windows NT APW to install the NT drivers and the 9x drivers. This can be scripted using smbclient and rpcclient. See the Imprints installation client at:

        -http://imprints.sourceforge.net/ + http://imprints.sourceforge.net/

        for an example. See also the discussion of rpcclient usage in the -"CUPS Printing" section.

      Publishing Printer Information in Active Directory or LDAP

      +"CUPS Printing" section.

    Publishing Printer Information in Active Directory or LDAP

    We will publish an update to this section shortly. -

    Common Errors and Problems

    -Here are a few typical errors and problems people have -encountered. You can avoid them. Read on. -

    I give my root password but I don't get access

    -Don't confuse the root password which is valid for the Unix system +

    Common Errors

    I give my root password but I don't get access

    +Don't 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 doesn't know the UNIX password; for root to access Samba resources via Samba-type access, a Samba account for root must be created first. This is often done with the smbpasswd command. -

    My printjobs get spooled into the spooling directory, but then get lost

    -Don't use the existing Unix print system spool directory for the Samba +

    My printjobs get spooled into the spooling directory, but then get lost

    +Don't use the existing UNIX print system spool directory for the Samba spool directory. It may seem convenient and a saving of space, but it only leads to problems. The two must be separate. -

    Prev Up Next
    Chapter 17. Hosting a Microsoft Distributed File System tree on Samba Home Chapter 19. CUPS Printing Support in Samba 3.0
    +

    Prev Up Next
    Chapter 17. Hosting a Microsoft Distributed File System tree on Samba Home Chapter 19. CUPS Printing Support in Samba 3.0
    diff --git a/docs/htmldocs/problems.html b/docs/htmldocs/problems.html index 6628a7d8fe..24ddc7c02c 100644 --- a/docs/htmldocs/problems.html +++ b/docs/htmldocs/problems.html @@ -1,11 +1,16 @@ -Chapter 34. Analysing and solving samba problems
    Chapter 34. Analysing and solving samba problems
    Prev Part V. Troubleshooting Next

    Chapter 34. Analysing and solving samba problems

    Gerald (Jerry) Carter

    Samba Team

    Jelmer R. Vernooij

    The Samba Team

    David Bannon

    Samba Team

    8 Apr 2003

    Table of Contents

    Diagnostics tools
    Installing 'Network Monitor' on an NT Workstation or a Windows 9x box
    Useful URLs
    Getting help from the mailing lists
    How to get off the mailing lists

    +Chapter 34. Analysing and solving samba problems

    Chapter 34. Analysing and solving samba problems
    Prev Part V. Troubleshooting Next

    Chapter 34. Analysing and solving samba problems

    Gerald (Jerry) Carter

    Samba Team

    Jelmer R. Vernooij

    The Samba Team

    David Bannon

    Samba Team

    8 Apr 2003

    Table of Contents

    Diagnostics tools
    Debugging with Samba itself
    Tcpdump
    Ethereal
    The Windows Network Monitor
    Useful URLs
    Getting help from the mailing lists
    How to get off the mailing lists

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

    Diagnostics tools

    +general SMB topics such as browsing.

    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, analyses the data sent on it and displays it +on the screen.

    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 what -debug level at which to run. See the man pages on smbd, nmbd and +debug level at which to run. See the man pages on smbd, nmbd and smb.conf for more information on debugging options. The debug level can range from 1 (the default) to 10 (100 for debugging passwords).

    @@ -24,14 +29,19 @@ typing in your password, you can attach gdb and continue.

    Some useful samba commands worth investigating: 

    -	$ testparm | more
-	$ smbclient -L //{netbios name of server}
-

    -An SMB enabled version of tcpdump is available from -http://www.tcpdup.org/. -Ethereal, another good packet sniffer for Unix and Win32 -hosts, can be downloaded from http://www.ethereal.com. -

    +$ testparm | more +$ smbclient -L //{netbios name of server} +

    Tcpdump

    Tcpdump was the first +unix sniffer with SMB support. It is a command-line utility and +nowadays, it's SMB support is somewhat less then that of ethereal +and tethereal.

    Ethereal

    +Ethereal is a graphical +sniffer, available for both unix (Gtk) and Windows. Ethereal's +SMB support is very good.

    For details on the use of ethereal, read the well-written +ethereal User Guide.

    +Listen for data on ports 137, 138, 139 and 445. E.g. +use the filter port 137 or port 138 or port 139 or port 445.

    A console version of ethereal is available as well and is called +tethereal.

    The Windows Network Monitor

    For tracing things on the Microsoft Windows NT, Network Monitor (aka. netmon) is available on the Microsoft Developer Network CD's, the Windows NT Server install CD and the SMS CD's. The version of @@ -41,7 +51,7 @@ 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 or a Windows 9x box

    +

    Installing 'Network Monitor' on an NT Workstation

    Installing netmon on an NT workstation requires a couple of steps. The following are for installing Netmon V4.00.349, which comes with Microsoft Windows NT Server 4.0, on Microsoft Windows NT @@ -74,17 +84,17 @@ Now copy the files from the NT Server in %SYSTEMROOT%\Syste 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 an 9x Workstation

    To install Netmon on a Windows 9x box install the network monitor agent from the Windows 9x CD (\admin\nettools\netmon). There is a readme file located with the netmon driver files on the CD if you need information on how to do this. Copy the files from a working Netmon installation. -

    Useful URLs

    • See how Scott Merrill simulates a BDC behavior at +

    Useful URLs

    Getting help from the mailing lists

    + ftp://ftp.microsoft.com/developr/drg/CIFS/

    Getting help from the mailing lists

    There are a number of Samba related mailing lists. Go to http://samba.org, click on your nearest mirror and then click on Support and then click on Samba related mailing lists. @@ -94,10 +104,10 @@ For questions relating to Samba TNG go to It has been requested that you don't post questions about Samba-TNG to the main stream Samba lists.

    If you post a message to one of the lists please observe the following guide lines : -

    • Always remember that the developers are volunteers, they are +

      • Always remember that the developers are volunteers, they are not paid and they never guarantee to produce a particular feature at a particular time. Any time lines are 'best guess' and nothing more. -

      • Always mention what version of samba you are using and what +

      • Always mention what version of samba you are using and what operating system its running under. You should probably list the relevant sections of your smb.conf file, at least the options in [global] that affect PDC support.

      • In addition to the version, if you obtained Samba via @@ -118,12 +128,11 @@ error messages.

      • (Possibly) If you have a complete netmon trace ( 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 +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 you went to to get on it. Go to http://lists.samba.org, click on your nearest mirror and then click on Support and -then click on Samba related mailing lists. Or perhaps see -here +then click on Samba related mailing lists.

    Please don't post messages to the list asking to be removed, you will just be referred to the above address (unless that process failed in some way...) -

    Prev Up Next
    Chapter 33. The Samba checklist Home Chapter 35. Reporting Bugs
    +

    Prev Up Next
    Chapter 33. The Samba checklist Home Chapter 35. Reporting Bugs
    diff --git a/docs/htmldocs/rpcclient.1.html b/docs/htmldocs/rpcclient.1.html index 47c4d914a5..e1ff391cbc 100644 --- a/docs/htmldocs/rpcclient.1.html +++ b/docs/htmldocs/rpcclient.1.html @@ -5,10 +5,9 @@ have now written scripts around it to manage Windows NT clients from their UNIX workstation.

    OPTIONS

    server

    NetBIOS name of Server to which to connect. The server can be any SMB/CIFS server. The name is - resolved using the - name resolve order line from smb.conf(5).

    -c|--command='command string'

    execute semicolon separated commands (listed + resolved using the name resolve order line from smb.conf(5).

    -c|--command='command string'

    execute semicolon separated commands (listed below))

    -I IP-address

    IP address is the address of the server to connect to. - It should be specified in standard "a.b.c.d" notation.

    Normally the client would attempt to locate a named + It should be specified in standard "a.b.c.d" notation.

    Normally the client would attempt to locate a named SMB/CIFS server by looking it up via the NetBIOS name resolution mechanism described above in the name resolve order parameter above. Using this parameter will force the client @@ -22,8 +21,7 @@ configuration details required by the server. The information in this file includes server-specific information such as what printcap file to use, as well as descriptions of all the services that the server is -to provide. See -smb.conf(5) for more information. +to provide. See smb.conf for more information. The default configuration file name is determined at compile time.

    -d|--debug=debuglevel

    debuglevel is an integer from 0 to 10. The default value if this parameter is @@ -37,10 +35,9 @@ amounts of log data, and should only be used when investigating a problem. Levels above 3 are designed for use only by developers and generate HUGE amounts of log data, most of which is extremely cryptic.

    Note that specifying this parameter here will -override the log -level parameter in the -smb.conf(5) file.

    -l|--logfile=logbasename

    File name for log/debug files. The extension -".client" will be appended. The log file is +override the log level parameter +in the smb.conf file.

    -l|--logfile=logbasename

    File name for log/debug files. The extension +".client" will be appended. The log file is never removed by the client.

    -N

    If specified, this parameter suppresses the normal password prompt from the client to the user. This is useful when @@ -73,10 +70,10 @@ via the ps command. To be safe always allow rpcclient to prompt for a password and type it in directly.

    -n <primary NetBIOS name>

    This option allows you to override the NetBIOS name that Samba uses for itself. This is identical -to setting the NetBIOS -name parameter in the smb.conf(5) file. However, a command +to setting the netbios name parameter in the smb.conf file. +However, a command line setting will take precedence over settings in -smb.conf(5).

    -i <scope>

    This specifies a NetBIOS scope that +smb.conf.

    -i <scope>

    This specifies a NetBIOS scope that nmblookup will use to communicate with when generating NetBIOS names. For details on the use of NetBIOS scopes, see rfc1001.txt and rfc1002.txt. NetBIOS scopes are @@ -88,7 +85,7 @@ smb.conf. If the domain specified is the same as the servers NetBIOS name, it causes the client to log on using the servers local SAM (as opposed to the Domain SAM).

    -O socket options

    TCP socket options to set on the client socket. See the socket options parameter in -the smb.conf(5) manual page for the list of valid +the smb.conf manual page for the list of valid options.

    -h|--help

    Print a summary of command line options.

    COMMANDS

    LSARPC

    lsaquery

    Query info policy

    lookupsids

    Resolve a list of SIDs to usernames. @@ -111,10 +108,10 @@ Help File Name:\ Language Monitor Name:\ Default Data Type:\ Comma Separated list of Files -

    Any empty fields should be enter as the string "NULL".

    Samba does not need to support the concept of Print Monitors +

    Any empty fields should be enter as the string "NULL".

    Samba does not need to support the concept of Print Monitors since these only apply to local printers whose driver can make use of a bi-directional link for communication. This field should - be "NULL". On a remote NT print server, the Print Monitor for a + be "NULL". On a remote NT print server, the Print Monitor for a driver must already be installed prior to adding the driver or else the RPC will fail.

    addprinter <printername> <sharename> <drivername> <port>

    @@ -158,9 +155,9 @@ Comma Separated list of Files Execute a GetPrinterDriverDirectory() RPC to retrieve the SMB share name and subdirectory for storing printer driver files for a given architecture. Possible - values for arch are "Windows 4.0" - (for Windows 95/98), "Windows NT x86", "Windows NT PowerPC", "Windows - Alpha_AXP", and "Windows NT R4000".

    getprinter <printername>

    Retrieve the current printer information. This command + values for arch are "Windows 4.0" + (for Windows 95/98), "Windows NT x86", "Windows NT PowerPC", "Windows + Alpha_AXP", and "Windows NT R4000".

    getprinter <printername>

    Retrieve the current printer information. This command corresponds to the GetPrinter() MS Platform SDK function.

    getprintprocdir

    Get print processor diff --git a/docs/htmldocs/samba-bdc.html b/docs/htmldocs/samba-bdc.html index 4c2045642d..c3be7504e2 100644 --- a/docs/htmldocs/samba-bdc.html +++ b/docs/htmldocs/samba-bdc.html @@ -1,22 +1,21 @@ -Chapter 6. Backup Domain Control

    Chapter 6. Backup Domain Control
    Prev Part II. Server Configuration Basics Next

    Chapter 6. Backup Domain Control

    John H. Terpstra

    Samba Team

    Volker Lendecke

    Samba Team

    Table of Contents

    Features And Benefits
    Essential Background Information
    MS Windows NT4 Style Domain Control
    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, what can I do?
    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 6. Backup Domain Control

    Chapter 6. Backup Domain Control
    Prev Part II. Server Configuration Basics Next

    Chapter 6. Backup Domain Control

    John H. Terpstra

    Samba Team

    Volker Lendecke

    Samba Team

    Table of Contents

    Features And Benefits
    Essential Background Information
    MS Windows NT4 Style Domain Control
    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, what can I do?
    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 in this section, please make sure that you are comfortable -with configuring a Samba Domain Controller as described in the -Domain Control chapter. -

    Features And Benefits

    +with configuring a Samba Domain Controller as described in chapter on setting up Samba as a PDC. +

    Features And Benefits

    This is one of the most difficult chapters to summarise. 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. Since this HOWTO is already so large and -extensive, we have taken the decision to provide sufficient (but not comprehensive) -information regarding Backup Domain Control. In the event that you should have a persistent -concern that is not addressed in this HOWTO document then please email +effectively using a totally different approach. In the event that you should have a persistent +concern that is not addressed in this book then 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 is capable of acting as a Backup Domain Controller to another Samba Primary Domain -Controller. A Samba-3 PDC can operate with an LDAP Account backend. The Samba-3 BDC can -operate with a slave LDAP server for the Account backend. This effectively gives samba a high -degree of scalability. This is a very sweet (nice) solution for large organisations. +Controller. 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 may still be able to log onto the network. +This effectively gives samba a high degree of scalability iand is a very sweet (nice) solution +for large organisations.

    While it is possible to run a Samba-3 BDC with non-LDAP backend, the administrator will need to figure out precisely what is the best way to replicate (copy / distribute) the @@ -41,8 +40,9 @@ lets consider each possible option and look at the pro's and con's for each theo

    Arguments Against: Complexity

  • - Passdb Backend is tdbsam based, BDCs use cron based "net rpc vampire" to - suck down the Accounts database from the PDC + Passdb Backend is tdbsam based, BDCs use cron based net rpc vampire to + obtain the Accounts database from the PDC and place them into the Samba SAM. + net rpc vampire is a Samba function of the "net" command.

    Arguments For: It would be a nice solution

    @@ -63,7 +63,7 @@ lets consider each possible option and look at the pro's and con's for each theo Arguments Against: All machine trust accounts and user accounts will be locally maintained. Domain users will NOT be able to roam from office to office. This is a broken and flawed solution. Do NOT do this. -

    • 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. @@ -73,7 +73,7 @@ and with it a new form of the network logon service that has extended functional 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 very complex array of services that are implemented over a complex 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 the username and password that the user entered are valid. If the information entered @@ -131,32 +131,29 @@ one of the BDCs can be promoted to a PDC. If this happens while the original PDC line then it is automatically demoted to a BDC. This is an important aspect of Domain Controller management. The tool that is used to affect a promotion or a demotion is the Server Manager for Domains. -

    Example PDC Configuration

    +

    Example PDC Configuration

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

    -	workgroup = SAMBA
-	domain master = yes
-	domain logons = yes
-

    -Several other things like a [homes] and a [netlogon] share also need to be set along with +

    Example 6.1. Minimal smb.conf for being a PDC

    workgroup = MIDEARTH
    domain master = yes
    domain logons = yes

    +Several other things like a [homes] and a +[netlogon] share also need to be set along with settings for the profile path, the users home drive, etc.. This will not be covered in this -chapter, for more information please refer to the chapter on Domain Control. -

    Active Directory Domain Control

    +chapter, for more information please refer to the chapter about samba as a PDC. +

    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 can not be an Active Directory server. This means that Samba-3 also can NOT act as a Backup Domain Controller 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 SAMBA has to register the NetBIOS group name SAMBA<#1c> with the WINS server and/or by broadcast on the local network. The PDC also registers the unique NetBIOS name SAMBA<#1b> with the WINS server. The name type <#1b> name is normally reserved for the Domain Master Browser, a role that has nothing to do with anything related to authentication, but the Microsoft Domain implementation requires the domain master browser to be on the same machine as the PDC. -

    How does a Workstation find its domain controller?

    +

    How does a Workstation find its domain controller?

    An MS Windows NT4 / 200x / XP Professional workstation in the domain SAMBA that wants a local user to be authenticated has to find the domain controller for SAMBA. It does this by doing a NetBIOS name query for the group name SAMBA<#1c>. It assumes that each @@ -164,22 +161,22 @@ 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. -

    Backup Domain Controller Configuration

    +

    Backup Domain Controller Configuration

    Several things have to be done:

    • The domain SID has to be the same on the PDC and the BDC. This used to be stored in the file private/MACHINE.SID. This file is not created - anymore since Samba 2.2.5 or even earlier. Nowadays the domain SID is - stored in the file private/secrets.tdb. Simply copying the secrets.tdb + since Samba 2.2.5. Nowadays the domain SID is stored in the file + private/secrets.tdb. Simply copying the secrets.tdb from the PDC to the BDC does not work, as the BDC would generate a new SID for itself and override the domain SID with this new BDC SID.

      To retrieve the domain SID from the PDC or an existing BDC and store it in the secrets.tdb, execute: 

      -	root# net rpc getsid
-

    • - The Unix user database has to be synchronized from the PDC to the +root# net rpc getsid +

    • + 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 to the BDC. This can be done manually whenever changes are made, or the PDC is set up as a NIS master @@ -199,23 +196,30 @@ Several things have to be done: BDC. This can be done manually whenever login scripts are changed, or it can be done automatically together with the smbpasswd synchronization. -

    Example Configuration

    +

    Example Configuration

    Finally, the BDC has to be found by the workstations. This can be done by setting: -

    -	workgroup = SAMBA
-	domain master = no
-	domain logons = yes
-

    -in the [global]-section of the smb.conf of the BDC. This makes the BDC +

    Example 6.2. Minimal setup for being a BDC

    workgroup = MIDEARTH
    domain master = no
    domain logons = yes
    idmap backend = ldapsam://slave-ldap.quenya.org

    +In the [global]-section of the smb.conf of the BDC. This makes the BDC only register the name SAMBA<#1c> with the WINS server. This is no problem as the name SAMBA<#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 SAMBA<#1b> which as a unique NetBIOS +be registered by more than one machine. The parameter +domain master = no +forces the BDC not to register SAMBA<#1b> which as a unique NetBIOS name is reserved for the Primary Domain Controller. -

    Common Errors

    +

    +The idmap backend will redirect the winbindd utility to +use the LDAP database to resolve all UIDs and GIDs for UNIX accounts. +

    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 of NT Domain User and Group +SIDs. One of the new facilities provides for explicitly ensuring that UNIX / Linux UID and GID values +will be consistent on the PDC, all BDCs and all Domain Member servers. The parameter that controls this +is called idmap backend. Please refer to the man page for smb.conf for more information +regarding it's behaviour. Do NOT set this parameter except where an LDAP backend (ldapsam) is in use. +

    Common Errors

    As this is a rather new area for Samba there are not many examples that we may refer to. Keep watching for updates to this section. -

    Machine Accounts keep expiring, what can I do?

    +

    Machine Accounts keep expiring, what can I do?

    This problem will occur when occur when the passdb (SAM) files are copied from a central server but the local Backup Domain Controllers. Local machine trust account password updates are not copied back to the central server. The newer machine account password is then over @@ -226,18 +230,15 @@ to proceed and the account expiry error will be reported.

    The solution: use a more robust passdb backend, such as the ldapsam backend, setting up an 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?

    With version 2.2, no. The native NT4 SAM replication protocols have not yet been fully implemented. The Samba Team is working on understanding and implementing the protocols, -but this work has not been finished for version 2.2. -

    -With version 3.0, the work on both the replication protocols and a suitable storage -mechanism has progressed, and some form of NT4 BDC support is expected soon. +but this work has not been finished for Samba-3.

    -Can I get the benefits of a BDC with Samba? Yes. The main reason for implementing a +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. @@ -251,9 +252,9 @@ 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 very 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 this will not occur often). -

    Prev Up Next
    Chapter 5. Domain Control Home Chapter 7. Domain Membership
    +

    Prev Up Next
    Chapter 5. Domain Control Home Chapter 7. Domain Membership
    diff --git a/docs/htmldocs/samba-doc.html b/docs/htmldocs/samba-doc.html new file mode 100644 index 0000000000..f5dfd49888 --- /dev/null +++ b/docs/htmldocs/samba-doc.html @@ -0,0 +1,72 @@ +SAMBA Project Documentation
    SAMBA Project Documentation
       Next

    SAMBA Project Documentation

    Edited by

    Jelmer R. Vernooij

    John H. Terpstra

    Gerald (Jerry) Carter

    Monday April 21, 2003

    Abstract

    +This book is a collection of HOWTOs added to Samba documentation over the years. +Samba is always under development, and so is its' documentation. This release of the +documentation represents a major revision or layout as well as contents. +The most recent version of this document can be found at +http://www.samba.org/ +on the "Documentation" page. Please send updates to +Jelmer Vernooij, +John H. Terpstra or +Gerald (Jerry) Carter. +

    +The Samba-Team would like to express sincere thanks to the many people who have with +or without their knowledge contributed to this update. The size and scope of this +project would not have been possible without significant community contribution. A not +insignificant number of ideas for inclusion (if not content itself) has been obtained +from a number of Unofficial HOWTOs - to each such author a big "Thank-you" is also offered. +Please keep publishing your Unofficial HOWTOs - they are a source of inspiration and +application knowledge that is most to be desired by many Samba users and administrators. +

    Table of Contents

    Legal Notice
    Attributions
    I. General Installation
    1. Introduction to Samba
    Background
    Terminology
    Related Projects
    SMB Methodology
    Epilogue
    Miscellaneous
    2. How to Install and Test SAMBA
    Obtaining and installing samba
    Configuring samba (smb.conf)
    Example Configuration
    SWAT
    Try listing the shares available on your + server
    Try connecting with the unix client
    Try connecting from another SMB client
    What If Things Don't Work?
    Common Errors
    Large number of smbd processes
    "open_oplock_ipc: Failed to get local UDP socket for address 100007f. Error was Cannot assign requested"
    "The network name cannot be found"
    3. Fast Start for the Impatient
    Note
    II. Server Configuration Basics
    4. 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
    5. Domain Control
    Features and Benefits
    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 can not log you on (C000019B)....
    The machine trust account not accessible
    Account disabled
    Domain Controller Unavailable
    Can not log onto domain member workstation after joining domain
    6. Backup Domain Control
    Features And Benefits
    Essential Background Information
    MS Windows NT4 Style Domain Control
    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, what can I do?
    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?
    7. Domain Membership
    Features and Benefits
    MS Windows Workstation/Server Machine Trust Accounts
    Manual Creation of Machine Trust Accounts
    Using NT4 Server Manager to Add Machine Accounts to the Domain
    "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
    Setup your smb.conf
    Setup your /etc/krb5.conf
    Create the computer account
    Test your server setup
    Testing with smbclient
    Notes
    Common Errors
    Can Not Add Machine Back to Domain
    Adding Machine to Domain Fails
    I can't join a Windows 2003 PDC
    8. Stand-Alone Servers
    Features and Benefits
    Background
    Example Configuration
    Reference Documentation Server
    Central Print Serving
    Common Errors
    9. MS Windows Network Configuration Guide
    Note
    III. Advanced Configuration
    10. Samba / MS Windows Network Browsing Guide
    Features and Benefits
    What is Browsing?
    Discussion
    NetBIOS over TCP/IP
    TCP/IP - without NetBIOS
    DNS and Active Directory
    How Browsing Functions
    Setting up WORKGROUP Browsing
    Setting up DOMAIN Browsing
    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
    Setting up a WINS server
    WINS Replication
    Static WINS Entries
    Helpful Hints
    Windows Networking Protocols
    Name Resolution Order
    Technical Overview of browsing
    Browsing support in Samba
    Problem resolution
    Browsing across subnets
    Common Errors
    How can one flush the Samba NetBIOS name cache without restarting Samba?
    My client reports "This server is not configured to list shared resources"
    I get an Unable to browse the network error
    11. Account Information Databases
    Features and Benefits
    Backwards Compatibility Backends
    New Backends
    Technical Information
    Important Notes About Security
    Mapping User Identifiers between MS Windows and UNIX
    Mapping Common UIDs/GIDs on Distributed Machines
    Account Management Tools
    The smbpasswd Command
    The pdbedit Command
    Password Backends
    Plain Text
    smbpasswd - Encrypted Password Database
    tdbsam
    ldapsam
    MySQL
    XML
    Common Errors
    Users can not logon
    Users being added to wrong backend database
    auth methods does not work
    12. Mapping MS Windows and UNIX Groups
    Features and Benefits
    Discussion
    Example Configuration
    Configuration Scripts
    Sample smb.conf add group script
    Script to configure Group Mapping
    Common Errors
    Adding Groups Fails
    Adding MS Windows Groups to MS Windows Groups Fails
    Adding Domain Users to the Power Users group
    13. 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
    Common Errors
    Users can not write to a public share
    I have set force user but Samba still makes root the owner of all the files I touch!
    MS Word with Samba changes owner of file
    14. File and Record Locking
    Features and Benefits
    Discussion
    Opportunistic Locking Overview
    Samba Opportunistic Locking Control
    Example Configuration
    MS Windows Opportunistic Locking 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
    15. 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 a IPC$ share deny
    NTLMv2 Security
    Upgrading Samba
    Common Errors
    Smbclient works on localhost, but the network is dead
    Why can users access home directories of other users?
    16. 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
    Inter-Domain 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
    17. Hosting a Microsoft Distributed File System tree on Samba
    Features and Benefits
    Common Errors
    18. Classical Printing Support
    Features and Benefits
    Technical Introduction
    What happens if you send a Job from a Client
    Printing Related Configuration Parameters
    Parameters Recommended for Use
    A simple Configuration to Print
    Verification of "Settings in Use" with testparm
    A little Experiment to warn you
    Extended Sample Configuration to Print
    Detailed Explanation of the Example's Settings
    The [global] Section
    The [printers] Section
    Any [my_printer_name] Section
    Print Commands
    Default Print Commands for various UNIX Print Subsystems
    Setting up your own Print Commands
    Innovations in Samba Printing since 2.2
    Client Drivers on Samba Server for Point'n'Print
    The [printer$] Section is removed from Samba 3
    Creating the [print$] Share
    Parameters in the [print$] Section
    Subdirectory Structure in [print$]
    Installing Drivers into [print$]
    Setting Drivers for existing Printers with a Client GUI
    Setting Drivers for existing Printers with +rpcclient
    Client Driver Install Procedure
    The first Client Driver Installation
    IMPORTANT! Setting Device Modes on new Printers
    Further Client Driver Install Procedures
    Always make first Client Connection as root or "printer admin"
    Other Gotchas
    Setting Default Print Options for the Client Drivers
    Supporting large Numbers of Printers
    Adding new Printers with the Windows NT APW
    Weird Error Message Cannot connect under a +different Name
    Be careful when assembling Driver Files
    Samba and Printer Ports
    Avoiding the most common Misconfigurations of the Client Driver
    The Imprints Toolset
    What is Imprints?
    Creating Printer Driver Packages
    The Imprints Server
    The Installation Client
    Add Network Printers at Logon 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 don't get access
    My printjobs get spooled into the spooling directory, but then get lost
    19. CUPS Printing Support in Samba 3.0
    Introduction
    Features and Benefits
    Overview
    Basic Configuration of CUPS support
    Linking of smbd with libcups.so
    Simple smb.conf Settings for CUPS
    More complex smb.conf Settings for +CUPS
    Advanced Configuration
    Central spooling vs. "Peer-to-Peer" printing
    CUPS/Samba as a "spooling-only" Print Server; "raw" printing +with Vendor Drivers on Windows Clients
    Driver Installation Methods on Windows Clients
    Explicitly enable "raw" printing for +application/octet-stream!
    Three familiar Methods for driver upload plus a new one
    Using CUPS/Samba in an advanced Way -- 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
    CUPS can use all 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
    Filter Requirements
    Prefilters
    pstops
    pstoraster
    imagetops and imagetoraster
    rasterto [printers specific]
    CUPS Backends
    cupsomatic/Foomatic -- how do they fit into the Picture?
    The Complete Picture
    mime.convs
    "Raw" printing
    "application/octet-stream" printing
    PostScript Printer Descriptions (PPDs) for non-PS Printers
    Difference between cupsomatic/foomatic-rip and +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 -- UNIX/Samba Print +Servers)
    From Windows Clients to a CUPS/Samba Print Server
    Samba receiving Jobfiles and passing them to CUPS
    Network PostScript RIP: CUPS Filters on Server -- clients use +PostScript Driver with CUPS-PPDs
    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
    Setting up CUPS for driver Download
    cupsaddsmb: the unknown Utility
    Prepare your smb.conf for cupsaddsmb
    CUPS Package of "PostScript Driver for WinNT/2k/XP"
    Recognize the different Driver Files
    Acquiring the Adobe Driver Files
    ESP Print Pro Package of "PostScript Driver for +WinNT/2k/XP"
    Caveats to be considered
    Benefits of using "CUPS PostScript Driver for +Windows NT/2k/XP" instead of 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
    What is required 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
    Auto-Deletion or Preservation of CUPS Spool Files
    CUPS Configuration Settings explained
    Pre-conditions
    Manual Configuration
    In Case of Trouble.....
    Printing from CUPS to Windows attached +Printers
    More CUPS filtering Chains
    Common Errors
    Win9x client can't install driver
    "cupsaddsmb" keeps asking for root password in + neverending loop
    "cupsaddsmb" gives "No PPD file for printer..." + message while PPD file is present
    Client can't connect to Samba printer
    Can't reconnect to Samba under new account + from Win2K/XP
    Avoid being connected to the Samba server as the + "wrong" user
    Upgrading to CUPS drivers from Adobe drivers on + NT/2K/XP clients gives problems
    Can't use "cupsaddsmb" on Samba server which is + a PDC
    Deleted Win2K printer driver is still shown
    Win2K/XP "Local Security + Policies"
    WinXP clients: "Administrator can not install + printers for all local users"
    "Print Change Notify" functions on + NT-clients
    WinXP-SP1
    Print options for all users can't be set on Win2K/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
    Printer named "lp" +intermittently swallows jobs and spits out completely different +ones
    Location of Adobe PostScript driver files necessary for "cupsaddsmb"
    An Overview of the CUPS Printing Processes
    20. Stackable VFS modules
    Features and Benefits
    Discussion
    Included modules
    audit
    extd_audit
    fake_perms
    recycle
    netatalk
    VFS modules available elsewhere
    DatabaseFS
    vscan
    21. Winbind: Use of Domain Accounts
    Features and Benefits
    Introduction
    What Winbind Provides
    Target Uses
    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
    22. Advanced Network Management
    Features and Benefits
    Remote Server Administration
    Remote Desktop Management
    Remote Management from NoMachines.Com
    Network Logon Script Magic
    Adding printers without user intervention
    Common Errors
    23. 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
    Samba Editreg Toolset
    Windows NT4/200x
    Samba PDC
    System Startup and Logon Processing Overview
    Common Errors
    Policy Does Not Work
    24. Desktop Profile Management
    Features and Benefits
    Roaming Profiles
    Samba Configuration for Profile Handling
    Windows Client Profile Configuration Information
    Sharing Profiles between W9x/Me and NT4/200x/XP workstations
    Profile Migration from Windows NT4/200x Server to Samba
    Mandatory profiles
    Creating/Managing Group Profiles
    Default Profile for Windows Users
    MS Windows 9x/Me
    MS Windows NT4 Workstation
    MS Windows 200x/XP
    Common Errors
    Setting up roaming profiles for just a few user's or group's?
    Can NOT use Roaming Profiles
    Changing the default profile
    25. 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
    26. 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 in one way
    Very Slow Network Connections
    Samba server name change problem
    27. Unicode/Charsets
    Features and Benefits
    What are charsets and unicode?
    Samba and charsets
    Conversion from old names
    Japanese charsets
    Common errors
    CP850.so can't be found
    28. Samba Backup Techniques
    Note
    Features and Benefits
    29. High Availability Options
    Note
    IV. Migration and Updating
    30. Upgrading from Samba-2.x to Samba-3.0.0
    New Features in Samba-3
    Configuration Parameter Changes
    Removed Parameters
    New Parameters
    Modified Parameters (changes in behavior):
    New Functionality
    Databases
    Changes in Behavior
    Charsets
    Passdb Backends and Authentication
    Charsets
    LDAP
    31. 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
    32. SWAT - The Samba Web Administration Tool
    Features and Benefits
    Enabling SWAT for use
    Securing SWAT through SSL
    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
    33. The Samba checklist
    Introduction
    Assumptions
    The tests
    34. Analysing and solving samba problems
    Diagnostics tools
    Debugging with Samba itself
    Tcpdump
    Ethereal
    The Windows Network Monitor
    Useful URLs
    Getting help from the mailing lists
    How to get off the mailing lists
    35. Reporting Bugs
    Introduction
    General info
    Debug levels
    Internal errors
    Attaching to a running process
    Patches
    VI. Appendixes
    36. How to compile Samba
    Access Samba source code via CVS
    Introduction
    CVS 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 and nmbd
    Starting from inetd.conf
    Alternative: starting it as a daemon
    37. Portability
    HPUX
    SCO UNIX
    DNIX
    RedHat Linux Rembrandt-II
    AIX
    Sequential Read Ahead
    Solaris
    Locking improvements
    Winbind on Solaris 9
    38. Samba and other CIFS clients
    Macintosh clients?
    OS2 Client
    Configuring OS/2 Warp Connect or + OS/2 Warp 4 as a client for Samba
    Configuring OS/2 Warp 3 (not Connect), + OS/2 1.2, 1.3 or 2.x for Samba
    Printer driver download for for OS/2 clients?
    Windows for Workgroups
    Latest TCP/IP stack from Microsoft
    Delete .pwl files after password change
    Configuring WfW password handling
    Case handling of passwords
    Use TCP/IP as default protocol
    Speed improvement
    Windows '95/'98
    Speed improvement
    Windows 2000 Service Pack 2
    Windows NT 3.1
    39. Samba Performance Tuning
    Comparisons
    Socket options
    Read size
    Max xmit
    Log level
    Read raw
    Write raw
    Slow Logins
    Client tuning
    Samba performance problem due changing kernel
    Corrupt tdb Files
    40. DNS and DHCP Configuration Guide
    Note
    41. Further Resources
    Websites
    Related updates from Microsoft
    Index

    List of Figures

    5.1. An Example Domain
    10.1. Cross subnet browsing example
    11.1. IDMAP
    12.1. IDMAP groups
    13.1. Overview of unix permissions field
    16.1. Trusts overview
    19.1. Windows Printing to a local Printer
    19.2. Printing to a Postscript Printer
    19.3. Ghostscript as a RIP for non-postscript printers
    19.4. Prefiltering in CUPS to form Postscript
    19.5. Adding Device-specific Print Options
    19.6. Postscript to intermediate Raster format
    19.7. CUPS-raster production using Ghostscript
    19.8. Image format to CUPS-raster format conversion
    19.9. Raster to Printer Specific formats
    19.10. cupsomatic/foomatic processing versus Native CUPS
    19.11. PDF to socket chain
    19.12. PDF to USB chain
    19.13. Print Driver execution on the Client
    19.14. Print Driver execution on the Server
    19.15. Printing via CUPS/samba server
    19.16. cupsaddsmb flowchart
    19.17. Filtering chain 1
    19.18. Filtering chain with cupsomatic
    19.19. CUPS Printing Overview

    List of Tables

    7.1. Assumptions
    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. Attributes in the sambaSamAccount objectclass (LDAP)
    11.2. Basic smb.conf options for MySQL passdb backend
    11.3. MySQL field names for MySQL passdb backend
    13.1. Managing directories with unix and windows
    13.2. User and Group Based Controls
    13.3. File and Directory Permission Based Controls
    13.4. Other Controls
    19.1. PPD's shipped with CUPS
    20.1. Extended Auditing Log Information
    24.1. User Shell Folder registry keys default values
    24.2. Defaults of profile settings registry keys
    24.3. Defaults of default user profile paths registry keys
    25.1. Options recognized by pam_smbpass
    26.1. Unique NetBIOS names
    26.2. Group Names
    30.1. TDB File Descriptions
    31.1. The 3 Major Site Types
    31.2. Nature of the Conversion Choices

    List of Examples

    2.1. Simplest possible smb.conf file
    5.1. smb.conf for being a PDC
    5.2. smb.conf for being a PDC
    6.1. Minimal smb.conf for being a PDC
    6.2. Minimal setup for being a BDC
    8.1. smb.conf for Reference Documentation Server
    8.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.
    11.2. Configuration with LDAP
    12.1. smbgrpadd.sh
    13.1. Example File
    14.1. Share with some files oplocked
    14.2.
    17.1. smb.conf with DFS configured
    18.1. Simple configuration with BSD printing
    18.2. Extended configuration with BSD printing
    18.3. [print\$] example
    19.1. Simplest printing-related smb.conf
    19.2. Overriding global CUPS settings for one printer
    19.3. smb.conf for cupsaddsmb usage
    20.1. smb.conf with VFS modules
    20.2. smb.conf with multiple VFS modules
    21.1. smb.conf for winbind set-up
    33.1. smb.conf with [tmp] share
    38.1. Minimal profile share
       Next
       Legal Notice
    diff --git a/docs/htmldocs/samba-pdc.html b/docs/htmldocs/samba-pdc.html index 930315b3f5..aab2d4207c 100644 --- a/docs/htmldocs/samba-pdc.html +++ b/docs/htmldocs/samba-pdc.html @@ -1,8 +1,4 @@ -Chapter 5. Domain Control
    Chapter 5. Domain Control
    Prev Part II. Server Configuration Basics Next

    Chapter 5. Domain Control

    John H. Terpstra

    Samba Team

    Gerald (Jerry) Carter

    Samba Team

    David Bannon

    Samba Team

    Table of Contents

    Features and Benefits
    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 Problems and Errors
    I cannot include a '$' in a machine name
    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.
    The system can not log you on (C000019B)....
    The machine trust account for this computer either does not -exist or is not accessible.
    When I attempt to login to a Samba Domain from a NT4/W2K workstation, -I get a message about my account being disabled.
    Until a few minutes after Samba has started, clients get the error "Domain Controller Unavailable"

    The Essence of Learning:  +Chapter 5. Domain Control

    Chapter 5. Domain Control
    Prev Part II. Server Configuration Basics Next

    Chapter 5. Domain Control

    John H. Terpstra

    Samba Team

    Gerald (Jerry) Carter

    Samba Team

    David Bannon

    Samba Team

    Table of Contents

    Features and Benefits
    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 can not log you on (C000019B)....
    The machine trust account not accessible
    Account disabled
    Domain Controller Unavailable
    Can not log onto domain member workstation after joining domain

    The Essence of Learning:  There are many who approach MS Windows networking with incredible misconceptions. That's OK, because it gives the rest of us plenty of opportunity to be of assistance. Those who really want help would be well advised to become familiar with information @@ -10,18 +6,18 @@ that is already available.

    The reader is advised NOT to tackle this section without having first understood and mastered some basics. MS Windows networking is not particularly forgiving of -misconfiguration. Users of MS Windows networking are likely to complain bitterly -of persistent niggles that may be caused by broken network or system configuration. +misconfiguration. Users of MS Windows networking are likely to complain +of persistent niggles that may be caused by a broken network configuration. To a great many people however, MS Windows networking starts with a domain controller that in some magical way is expected to solve all ills. -

    +

    Figure 5.1. An Example Domain

    An Example Domain

    From the Samba mailing list one can readily identify many common networking issues. If you are not clear on the following subjects, then it will do much good to read the sections of this HOWTO that deal with it. These are the most common causes of MS Windows networking problems: -

    Basic TCP/IP configuration
    NetBIOS name resolution
    Authentication configuration
    User and Group configuration
    Basic File and Directory Permission Control in Unix/Linux
    Understanding of how MS Windows clients interoperate in a network - environment

    -Do not be put off; on the surface of it MS Windows networking seems so simple that any fool +

    • Basic TCP/IP configuration

    • NetBIOS name resolution

    • Authentication configuration

    • User and Group configuration

    • Basic File and Directory Permission Control in UNIX/Linux

    • Understanding of how MS Windows clients interoperate in a network + environment

    +Do not be put off; on the surface of it MS Windows networking seems so simple that anyone can do it. In fact, it is not a good idea to set up an MS Windows network with inadequate training and preparation. But let's get our first indelible principle out of the way: It is perfectly OK to make mistakes! In the right place and at @@ -32,7 +28,7 @@ burden on an organisation. Where is the right place to make mistakes? Only out of harm's way! If you are going to make mistakes, then please do this on a test network, away from users and in such a way as to not inflict pain on others. Do your learning on a test network. -

    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 @@ -43,13 +39,18 @@ and they will be able to log onto the network and access resources (shares, file 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 fully available to those sites that deploy a Samba PDC. +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 +know only of local security identifiers.

    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 account). Please refer to the chapter on -Domain Membership for more information. +setting up samba as a domain member for more information.

    The following functionalities are new to the Samba-3 release:

    • @@ -57,8 +58,7 @@ The following functionalities are new to the Samba-3 release:

    • Adding users via the User Manager for Domains. This can be done on any MS Windows client using the Nexus toolkit that is available from Microsoft's web site. - At some later date Samba-3 may get support for the use of the Microsoft Management - Console for user management. + Samba-3 supports the use of the Microsoft Management Console for user management.

    • Introduces replaceable and multiple user account (authentication) back ends. In the case where the back end is placed in an LDAP database, @@ -72,14 +72,18 @@ 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) + (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 or + replicate account data to Windows-BDC's.

      • Acting as a Windows 2000 Domain Controller (i.e. Kerberos and Active Directory) - In point of fact, Samba-3 DOES have some Active Directory Domain Control ability that is at this time purely experimental AND that is certain to change as it becomes a fully supported feature some time - during the Samba-3 (or later) life cycle. + during the Samba-3 (or later) life cycle. However, Active Directory is + more then just SMB - it's also LDAP, Kerberos, DHCP and other protocols + (with proprietary extensions, of course).

      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 @@ -88,67 +92,33 @@ for some time. These clients use the old LanMan Network Logon facilities that ar in Samba since approximately the Samba-1.9.15 series.

      Samba-3 has an implementation of group mapping between Windows NT groups -and Unix groups (this is really quite complicated to explain in a short space). This is -discussed more fully in the Group Mapping chapter. +and UNIX groups (this is really quite complicated to explain in a short space). This is +discussed more fully in the chapter on group mapping.

      Samba-3, like an MS Windows NT4 PDC or a Windows 200x Active Directory, needs to store -user and machine trust account information in a suitable backend data store. With Samba-3 -there can be multiple back-ends for this including: -

      • - smbpasswd - the plain ASCII file stored used by - earlier versions of Samba. This file configuration option requires - a Unix/Linux system account for EVERY entry (ie: both for user and for - machine accounts). This file will be located in the private - directory (default is /usr/local/samba/lib/private or on linux /etc/samba). -

      • - tdbsam - a binary database backend that will be - stored in the private directory in a file called - passdb.tdb. The key benefit of this binary format - file is that it can store binary objects that can not be accommodated - in the traditional plain text smbpasswd file. These permit the extended - account controls that MS Windows NT4 and later also have. -

      • - ldapsam - An LDAP based back-end. Permits the - LDAP server to be specified. eg: ldap://localhost or ldap://frodo.murphy.com. - Like the tdbsam, ldapsam permits the storing of extended account attributes - for control of things like: Permitted access times, password activation and - expiry, permitted points of access (workstation names), per user profile - location, and much more. -

      • - ldapsam_compat - An LDAP back-end that maintains backwards - compatibility with the behaviour of samba-2.2.x. You should use this in the process - of migrating from samba-2.2.x to samba-3 if you do not want to rebuild your LDAP - database. -

      -Read the chapter about Account Information Database for details -regarding the choices available and how to configure them. -

      Note

      -The new tdbsam and ldapsam account backends store substantially more information than -smbpasswd is capable of. The new backend database includes capacity to specify -per user settings for many parameters, over-riding global settings given in the -smb.conf file. eg: logon drive, logon home, logon path, etc. -Thus, with samba-3 it is possible to have a default system configuration for profiles, -and on a per user basis to over-ride this for those users who should not be subject -to the default configuration. -

    Basics of Domain Control

    +user and machine trust account information in a suitable backend data store. +Refer to the section on machine trust accounts. With Samba-3 there can be multiple +back-ends for this. A complete discussion of account database backends can be found in +the chapter on Account Information Databases. +

    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

    • Primary Domain Controller

    • Backup Domain Controller

    • ADS Domain Controller

    +

    Domain Controller Types

    • Primary Domain Controller

    • Backup Domain Controller

    • ADS Domain Controller

    The Primary Domain Controller or PDC plays an important role in the MS -Windows NT4 and Windows 200x Domain Control architecture, but not in the manner that so many -expect. There is folk lore that dictates that because of it's role in the MS Windows -network, the PDC should be the most powerful and most capable machine in the network. +Windows NT4. In Windows 200x Domain Control architecture this role is held by domain controllers. +There is folk lore that dictates that because of it's role in the MS Windows +network, the domain controllers should be the most powerful and most capable machine in the network. As strange as it may seem to say this here, good over all network performance dictates that -the entire infrastructure needs to be balanced. It is advisable to invest more in the Backup -Domain Controllers and Stand-Alone (or Domain Member) servers than in the PDC. +the entire infrastructure needs to be balanced. It is advisable to invest more in Stand-Alone +(or Domain Member) servers than in the domain controllers.

    -In the case of MS Windows NT4 style domains, it is the PDC seeds the Domain Control database, -a part of the Windows registry called the SAM (Security Account Manager). It plays a key +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 SAM (Security Account Manager). It plays a key part in NT4 type domain user authentication and in synchronisation of the domain authentication database with Backup Domain Controllers.

    -With MS Windows 200x Server based Active Directory domains, one domain controller seeds a potential +With MS Windows 200x Server based Active Directory domains, one domain controller initiates a potential hierarchy of domain controllers, each with their own area of delegated control. The master domain controller has the ability to override any down-stream controller, but a down-line controller has control only over it's down-line. With Samba-3 this functionality can be implemented using an @@ -156,9 +126,7 @@ LDAP based user and machine account back end.

    New to Samba-3 is the ability to use a back-end database that holds the same type of data as the NT4 style SAM (Security Account Manager) database (one of the registry files). -The Samba-3 SAM can be specified via the smb.conf file parameter -passwd backend and valid options include -smbpasswd, tdbsam, ldapsam, nisplussam, xmlsam, mysqlsam, guest. +[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. @@ -182,11 +150,14 @@ excluding the SAM replication components. However, please be aware that Samba-3 MS Windows 200x domain control protocols also.

    At this time any appearance that Samba-3 is capable of acting as an -ADS Domain Controller is limited and experimental in nature. +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 configuration and -management requirements. -

    Preparing for Domain Control

    +management requirements. Samba can act as a NT4-style DC in a Windows 2000/XP +environment. However, there are certain compromises: + +

    • No machine policy files

    • No Group Policy Objects

    • No synchronously executed AD logon scripts

    • Can't use ANY Active Directory management tools to manage users and machines

    • Registry changes tattoo the main registry, while with AD they do NOT. ie: Leave permanent changes in effect

    • Without AD you can not peprform the function of exporting specific 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 Stand-Alone systems, more commonly called Workgroup members, or as full participants in a security system, @@ -208,23 +179,22 @@ Domain it triggers a machine password change.

    Note

    When running a Domain all MS Windows NT / 200x / XP Professional clients should be configured as full Domain Members - IF A SECURE NETWORK IS WANTED. If the machine is NOT made a member of the -Domain, then it will operate like a workgroup (stand-alone) machine. Please refer the -Domain Membership chapter for information regarding - HOW to make your MS Windows clients Domain members. +Domain, then it will operate like a workgroup (stand-alone) machine. Please refer to +the chapter on domain membership for information regarding HOW to make your MS Windows clients Domain members.

    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 (See chapter on Browsing and on - MS Windows network Integration)
    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 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 (See chapter on Network Browsing and on + Integrating Unix into Windows networks)

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

    +

    • Configuration of basic TCP/IP and MS Windows Networking

    • Correct designation of the Server Role (security = user)

    • Network Logon Configuration (Since Windows 9x / 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 the Profile Management and -Policy Management chapters of this document. However, these are not necessarily specific -to a Samba PDC as much as they are related to Windows NT networking concepts. +Policy Management chapters of this document. However, these are not +necessarily specific to a Samba PDC as much as they are related to Windows NT networking concepts.

    A Domain Controller is an SMB/CIFS server that:

    • @@ -239,120 +209,86 @@ A Domain Controller is an SMB/CIFS server that: Provides a share called NETLOGON

    For Samba to provide these is rather easy to configure. Each Samba Domain Controller must provide -the NETLOGON service which Samba calls the domain logons functionality +the NETLOGON service which Samba calls the domain logons functionality (after the name of the parameter in the smb.conf file). Additionally, one (1) server in a Samba-3 -Domain must advertise itself as the domain master browser. This causes the Primary Domain Controller +Domain must advertise itself as the domain master browser[2]. This causes the Primary Domain Controller to claim domain specific NetBIOS name that identifies it as a domain master browser for its given domain/workgroup. Local master browsers in the same domain/workgroup on broadcast-isolated subnets then ask for a complete copy of the browse list for the whole wide area network. Browser clients will then contact their local master browser, and will receive the domain-wide browse list, instead of just the list for their broadcast-isolated subnet. -

    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. Here we attempt to explain the parameters that are covered in -the smb.conf man page. -

    -Here is an example smb.conf for acting as a PDC: -

    -	[global]
-	    ; Basic server settings
-	    netbios name = POGO
-	    workgroup = NARNIA
-
-	    ; User and Machine Account Backends
-	    ; Choices are: tdbsam, smbpasswd, ldapsam, mysqlsam, xmlsam, guest
-	    passdb backend = ldapsam, guest
-
-	    ; we should act as the domain and local master browser
-	    os level = 64
-	    preferred master = yes
-	    domain master = yes
-	    local master = yes
-	    
-	    ; security settings (must user security = user)
-	    security = user
-	    
-	    ; encrypted passwords are a requirement for a PDC (default = Yes)
-	    encrypt passwords = yes
-	    
-	    ; support domain logons
-	    domain logons = yes
-	    
-	    ; where to store user profiles?
-	    logon path = \\%N\profiles\%u
-	    
-	    ; where is a user's home directory and where should it be mounted at?
-	    logon drive = H:
-	    logon home = \\homeserver\%u\winprofile
-	    
-	    ; specify a generic logon script for all users
-	    ; this is a relative **DOS** path to the [netlogon] share
-	    logon script = logon.cmd
-
-	; necessary share for domain controller
-	[netlogon]
-	    path = /usr/local/samba/lib/netlogon
-	    read only = yes
-	    write list = ntadmin
-	    
-	; share for storing user profiles
-	[profiles]
-	    path = /export/smb/ntprofile
-	    read only = no
-	    create mask = 0600
-	    directory mask = 0700
-

    Note

    +in smb.conf. An example smb.conf for acting as a PDC can be found in the example +for being a PDC. +

    +

    Example 5.1. smb.conf for being a PDC

    [global]
    netbios name = BELERIAND
    workgroup = MIDEARTH
    passdb backend = ldapsam, guest
    os level = 33
    preferred master = yes
    domain master = yes
    local master = yes
    security = user
    encrypt passwords = yes
    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
    write list = ntadmin
    [profiles]
    path = /var/lib/samba/profiles
    read only = no
    create mask = 0600
    directory mask = 0700

    +

    +The basic options shown above are explained as follows: +

    passdb backend

    + This contains all the user and group account information. Acceptable values for a PDC + are: smbpasswd, tdbsam, ldapsam. The 'guest' entry provides needed + default accounts.

    + Where is is intended to use backup domain controllers (BDCs) the only logical choice is + to use LDAP so that the passdb backend can be distributed. The tdbsam and smbpasswd files + can not effectively be distributed and therefore should not be used. +

    Domain Control Parameters

    + The parameters os level, preferred master, domain master, security, + encrypt passwords, 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 domain master browser, 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 the chapter on account information databases. +

    Environment Parameters

    + The parameters logon path, logon home, logon drive, 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. Eash 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 + allow a Samba administrator to make the directory read only to everyone. Of course this is useful + only after the profile has been properly created. +

    Note

    The above parameters make for a full set of parameters that may define the server's mode -of operation. The following parameters are the essentials alone: - -

    -	workgroup = NARNIA
-	domain logons = Yes
-	domain master = Yes
-	security = User
-

    - -The additional parameters shown in the longer listing above just makes for a -more complete environment. -

    -There are a couple of points to emphasize in the above configuration. -

    • - Encrypted passwords must be enabled. For more details on how - to do this, refer to Account Information Database chapter. -

    • - The server must support domain logons and have a - [netlogon] share -

    • - The server must be the domain master browser in order for Windows - client to locate the server as a DC. Please refer to the various - Network Browsing documentation included with this distribution for - details. -

    Samba ADS Domain Control

    -Samba-3 is not and can not act as an Active Directory Server. It can not truly function as +of operation. The following smb.conf parameters are the essentials alone: +

    +

    netbios name = BELERIAND
    workgroup = MIDEARTH
    domain logons = Yes
    domain master = Yes
    security = User

    +

    +The additional parameters shown in the longer listing above just makes for +more complete explanation. +

    Samba ADS Domain Control

    +Samba-3 is not, and can not act as, an Active Directory Server. It can not truly function as an Active Directory Primary Domain Controller. The protocols for some of the functionality -the Active Directory Domain Controllers is have been partially implemented on an experimental -only basis. Please do NOT expect Samba-3 to support these protocols - nor should you depend -on any such functionality either now or in the future. The Samba-Team may well remove such -experimental features or may change their behaviour. -

    Domain and Network Logon Configuration

    -The subject of Network or Domain Logons is discussed here because it rightly forms +the 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 depend +on any such functionality either now or in the future. The Samba-Team may remove these +experimental features or may change their behaviour. This is mentioned for the benefit of those +who have discovered secret capabilities in samba-3 and who have asked when this functionality will be +completed. The answer is: Maybe 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 contollers do not have. In short, Samba-3 is not NT4 and it +is not Windows Server 200x and it is not an Active Directory server. We hope this is plain and simple +enough for all to understand. +

    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 Primary Domain Controller); on ALL Backup Domain Controllers domain master = No +in Samba). One Domain Controller must be configured with domain master = Yes +(the Primary Domain Controller); on ALL Backup Domain Controllers domain master = No must be set. -

    Example Configuration

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

    Note

    +

    Example Configuration

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

    Note

    MS Windows XP Home Edition does not have the ability to join any type of Domain security facility. Unlike, MS Windows 9x / Me, MS Windows XP Home Edition also completely lacks the ability to log onto a network. @@ -364,8 +300,10 @@ MS Windows XP Professional.

    Now that this has been said, please do NOT ask the mailing list, or email any of the Samba-Team members with your questions asking how to make this work. It can't be done. -

    The Special Case of Windows 9x / Me

    -A domain and a workgroup are exactly the same thing in terms of network +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

    +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 network. Also, different access rights can be granted to users if they @@ -386,7 +324,7 @@ which are the focus of this section. When an SMB client in a domain wishes to logon, 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 very stupid) to create a domain where the user +It is possible (but ill advised ) to create a domain where the user database is not shared between servers, i.e. they are effectively workgroup servers advertising themselves as participating in a domain. This demonstrates how authentication is quite different from but closely @@ -437,14 +375,17 @@ The main difference between a PDC and a Windows 9x logon server configuration is

    • Password encryption is not required for a Windows 9x logon server. But note that beginning with MS Windows 98 the default setting is that plain-text - password support has been disabled. It can be re-enabled with the registry + password support is disabled. It can be re-enabled with the registry changes that are documented in the chapter on Policies.

    • Windows 9x/ME clients do not require and do not use machine trust accounts.

    A Samba PDC will act as a Windows 9x logon server; after all, it does provide the network logon services that MS Windows 9x / Me expect to find. -

    Security Mode and Master Browsers

    +

    Note

    +Use of plain-text passwords is strongly discouraged. Where used they are easily detected +using a sniffer tool to examine network traffic. +

    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 or not it is ok to configure Samba as a Domain Controller in security @@ -461,24 +402,25 @@ are two distinctly different functions), it is not a good idea to do so. You should remember that the DC must register the DOMAIN<#1b> NetBIOS name. This is the name used by Windows clients to locate the DC. Windows clients do not distinguish between the DC and the DMB. +A DMB is a Domain Master Browser - see Domain Master Browser. For this reason, it is very wise to configure the Samba DC as the DMB.

    Now back to the issue of configuring a Samba DC to use a mode other -than security = user. If a Samba host is configured to use +than security = user. If a Samba host is configured to use another SMB server or DC in order to validate user connection requests, then it is a fact that some other machine on the network -(the password server) knows more about the user than the Samba host. +(the password server) knows more about the user than the Samba host. 99% of the time, this other host is a domain controller. Now -in order to operate in domain mode security, the workgroup parameter +in order to operate in domain mode security, the workgroup parameter must be set to the name of the Windows NT domain (which already has a domain controller). If the domain does NOT already have a Domain Controller then you do not yet have a Domain!

    Configuring a Samba box as a DC for a domain that already by definition has a PDC is asking for trouble. Therefore, you should always configure the Samba DC -to be the DMB for its domain and set security = user. +to be the DMB for its domain and set security = user. This is the only officially supported mode of operation. -

    Common Problems and Errors

    I cannot include a '$' in a 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. FreeBSD (and other BSD systems?) won't create a user with a '$' in their name. @@ -486,24 +428,26 @@ systems?) won't create a user with a '$' in their name. 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 ID! -

    I get told "You already have a connection to the Domain...." +

    Note

    +The UNIX tool vipw is a common tool for directly editting the /etc/passwd file. +

    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.

    +existing set.." when creating a machine trust account.”

    This happens if you try to create a machine trust account from the machine itself and already have a connection (e.g. mapped drive) to a share (or IPC$) on the Samba PDC. The following command will remove all network drive connections: 

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

    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 can not log you on (C000019B)....

    I joined the domain successfully but after upgrading +

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

    “I joined the domain successfully but after upgrading to a newer version of the Samba code I get the message, The system can not log you on (C000019B), Please try again or consult your -system administrator when attempting to logon. +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 @@ -518,14 +462,18 @@ The reset or change the domain SID you can use the net command as follows: root# net getlocalsid 'OLDNAME' root# net setlocalsid 'SID'

    -

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

    -When I try to join the domain I get the message The machine account +

    +Workstation machine trust accounts work only with the Domain (or network) SID. If this SID changes +then 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 re-join +it to the domain. +

    The machine trust account 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? +wrong?”

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

    @@ -541,10 +489,22 @@ 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. -

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

    +

    Account disabled

    “When I attempt to login to a Samba Domain from a NT4/W2K 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. -

    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 on the network who it is. This usually takes a while. -

    Prev Up Next
    Chapter 4. Server Types and Security Modes Home Chapter 6. Backup Domain Control
    +

    Can not 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 can not be found, the other claiming that the + account does not exist in the domain or that the password is incorrect.

    This may be due to incompatible settings between + the Windows client and the Samba-3 server for schannel (secure channel) settings + or smb signing settings. Check your samba settings for + client schannel, server schannel, client signing, server signing by executing: + testparm -v | more and looking for the value of these parameters. +

    + Also use the Microsoft Management Console - Local Security Settings. This tool is available from the + Control Panel. The Policy settings are found in the Local Policies / Securty Options area and are prefixed by + Secure Channel: ..., and Digitally sign .... +

    + It is important that these be set consistently with the Samba-3 server settings. +


    [1] See also the chapter on Account Information Databases.

    [2] See also the chapter about network browsing

    Prev Up Next
    Chapter 4. Server Types and Security Modes Home Chapter 6. Backup Domain Control
    diff --git a/docs/htmldocs/samba.7.html b/docs/htmldocs/samba.7.html index 222bdee995..a0e5b8937c 100644 --- a/docs/htmldocs/samba.7.html +++ b/docs/htmldocs/samba.7.html @@ -57,7 +57,9 @@

    profiles(1)

    profiles is a command-line utility that can be used to replace all occurences of a certain SID with another SID. -

    vfstest(1)

    vfstest is a utility +

    log2pcap(1)

    log2pcap is a utility + for generating pcap trace files from Samba log + files.

    vfstest(1)

    vfstest is a utility that can be used to test vfs modules.

    ntlm_auth(1)

    ntlm_auth is a helper-utility for external programs wanting to do NTLM-authentication.

    smbmount(8), smbumount(8), smbmount(8)

    smbmount,smbmnt and smbmnt are commands that can be used to diff --git a/docs/htmldocs/samba.css b/docs/htmldocs/samba.css new file mode 100644 index 0000000000..3d926e8e74 --- /dev/null +++ b/docs/htmldocs/samba.css @@ -0,0 +1,80 @@ +BODY { + font-family: helvetica, arial, lucida sans, sans-serif; + background-color: white; +} + +H1, H2, H3 { + color: blue; + font-size: 120%; + padding: 2px; + margin-top: 0px; +} + +H1 { + background-color: #EEEEFF; + color: blue; +} + +H2 { + background-color: #DDDDFF; + color: blue; +} + +H3 { + background-color: #CCCCFF; + color: blue; +} + +H4 { + color: blue; +} + +TR.qandadiv TD { + padding-top: 1em; +} + +DIV.navhead { + font-size: 80%; +} + +A:link { + color: #36F; +} + +A:visited { + color: #96C; +} + +A:active { + color: #F63; +} + +TR.question { + color: #33C; + font-weight: bold; +} + +TR.question TD { + padding-top: 1em; +} + +DIV.variablelist { + padding-left: 2em; + color: #33C; +} + +P { + color: black; +} + +DIV.note, DIV.warning, DIV.caution, DIV.tip, DIV.important { + border: dashed 1px; + background-color: #EEEEFF; + width: 40em; +} + +PRE.programlisting, PRE.screen { + border: #630 1px dashed; + color: #630; +} + diff --git a/docs/htmldocs/securing-samba.html b/docs/htmldocs/securing-samba.html index a790816d02..492780765e 100644 --- a/docs/htmldocs/securing-samba.html +++ b/docs/htmldocs/securing-samba.html @@ -1,4 +1,4 @@ -Chapter 15. Securing Samba

    Chapter 15. Securing Samba
    Prev Part III. Advanced Configuration Next

    Chapter 15. 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 a IPC$ share deny
    NTLMv2 Security
    Upgrading Samba
    Common Errors
    Smbclient works on localhost, but the network is dead
    Why can users access home directories of other users?

    Introduction

    +Chapter 15. Securing Samba

    Chapter 15. Securing Samba
    Prev Part III. Advanced Configuration Next

    Chapter 15. 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 a IPC$ share deny
    NTLMv2 Security
    Upgrading Samba
    Common Errors
    Smbclient works on localhost, but the network is dead
    Why can users access home directories of other users?

    Introduction

    This note was attached to the Samba 2.2.8 release notes as it contained an important security fix. The information contained here applies to Samba installations in general. @@ -10,7 +10,7 @@ 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 level at which security principals must be observed in order to render a site at least moderately secure. These are: the perimeter firewall, the configuration of the host server that is running Samba, and Samba itself. @@ -22,58 +22,50 @@ Samba may be secured from connections that originate from outside the local netw 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 that smbd will bind only to specifically permitted interfaces. It is also -possible to set specific share or resource based exclusions, eg: on the IPC$ -auto-share. The IPC$ share is used for browsing purposes as well as to establish +possible to set specific share or resource based exclusions, eg: on the [IPC$] +auto-share. 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 way of setting Access Control Entries in an Access Control List on the shares themselves. This is discussed in the chapter on File, Directory and Share Access Control. -

    Technical Discussion of Protective Measures and Issues

    +

    Technical Discussion of Protective Measures and Issues

    The key challenge of security is the fact 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 that 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 for outside your immediate network. By default Samba will accept 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 only + 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 only allow access to your server 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 only allow SMB connections 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 a 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 [globals] section put: - 

    -		valid users = @smbusers, jacko
-

    + method may be of use. In the smb.conf [global] section put: +

    valid users = @smbusers, jacko

    What this does is, it restricts all server access to either the user jacko or to members of the system group smbusers. -

    Using interface protection

    +

    Using interface protection

    By default Samba will accept connections on any network interface that it finds on your system. That means if you have a 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 behaviour using options like the following: - 

    -		interfaces = eth* lo
-		bind interfaces only = yes
-

    +

    interfaces = eth* lo
    bind interfaces only = yes

    This tells Samba to only listen for connections on interfaces with a name starting with 'eth' such as eth0, eth1, plus on the loopback interface called 'lo'. The name you will need to use depends on what @@ -85,7 +77,7 @@ before someone will find yet another vulnerability. connection refused reply. In that case no Samba code is run at all as the operating system has been told not to pass connections from that interface to any samba process. -

    Using a firewall

    +

    Using a firewall

    Many people use a firewall to deny access to services that they don't want exposed outside their network. This can be a very good idea, although I would recommend using it in conjunction with the above @@ -98,7 +90,7 @@ before someone will find yet another vulnerability. The last one is important as many older firewall setups may not be aware of it, given that this port was only added to the protocol in recent years. -

    Using a IPC$ share deny

    +

    Using a IPC$ share deny

    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 @@ -106,11 +98,7 @@ before someone will find yet another vulnerability. hosts.

    To do that 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 would tell Samba that IPC$ connections are not allowed from anywhere but the two listed places (localhost and a local subnet). Connections to other shares would still be allowed. As the @@ -125,42 +113,44 @@ before someone will find yet another vulnerability.

    This is not recommended unless you cannot use one of the other methods listed above for some reason. -

    NTLMv2 Security

    +

    NTLMv2 Security

    To configure NTLMv2 authentication the following registry keys are worth knowing about:

    - 

    +		
     		[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa]
 		"lmcompatibilitylevel"=dword:00000003
-
+		
    
+	
    
 		0x3 - Send NTLMv2 response only. Clients will use NTLMv2 authentication,
 		use NTLMv2 session security if the server supports it. Domain
 		controllers accept LM, NTLM and NTLMv2 authentication.
-
+	
    
+		
     		[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa\MSV1_0]
 		"NtlmMinClientSec"=dword:00080000
-
+		
    
+	
    
 		0x80000 - NTLMv2 session security. If either NtlmMinClientSec or
 		NtlmMinServerSec is set to 0x80000, the connection will fail if NTLMv2
 		session security is not 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 when a security vulnerability -is discovered. -

    Common Errors

    +is discovered. Check with your OS vendor for OS specific upgrades. +

    Common Errors

    If all of samba and host platform configuration were really as intuitive as one might like then this section would not be necessary. Security issues are often vexing for a support person to resolve, not because of the complexity of the problem, but for reason that 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 very common problem. Red Hat Linux (as do others) will install a default firewall. With the default firewall in place only traffic on the loopback adapter (IP address 127.0.0.1) will be allowed through the firewall.

    The solution is either to remove the firewall (stop it) or to modify the firewall script to allow SMB networking traffic through. See section above in this chapter. -

    Why can users access home directories of other users?

    +

    Why can users access home directories of other users?

    “ 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 @@ -189,18 +179,14 @@ out to be a security problem request are totally convinced that the problem is w the policies and permissions he or she desires.

    Samba does allow the setup you require when you have set the - only user = yes option on the share, is that you have not set the + only user = yes option on the share, is that you have not set the valid users list for the share.

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

    -	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 14. File and Record Locking Home Chapter 16. Interdomain Trust Relationships
    +

    Prev Up Next
    Chapter 14. File and Record Locking Home Chapter 16. Interdomain Trust Relationships
    diff --git a/docs/htmldocs/smb.conf.5.html b/docs/htmldocs/smb.conf.5.html index f22afa5884..b6eb609bb0 100644 --- a/docs/htmldocs/smb.conf.5.html +++ b/docs/htmldocs/smb.conf.5.html @@ -21,7 +21,7 @@ values, but is preserved in string values. Some items such as create modes are numeric.

    SECTION DESCRIPTIONS

    Each section in the configuration file (except for the [global] section) describes a shared resource (known - as a "share"). The section name is the name of the + as a "share"). The section name is the name of the shared resource and the parameters within the section define the shares attributes.

    There are three special sections, [global], [homes] and [printers], which are @@ -38,14 +38,14 @@ privileges in this case.

    Sections other than guest services will require a password to access them. The client provides the username. As older clients only provide passwords and not usernames, you may specify a list - of usernames to check against the password using the "user =" + of usernames to check against the password using the "user =" option in the share definition. For modern clients such as Windows 95/98/ME/NT/2000, this should not be necessary.

    Note that the access rights granted by the server are masked by the access rights granted to the specified or guest UNIX user by the host system. The server does not grant more access than the host system grants.

    The following sample section defines a file space share. The user has write access to the path /home/bar. - The share is accessed via the share name "foo":

    +	The share is accessed via the share name "foo":
     
 [foo]
 	path = /home/bar
@@ -83,7 +83,7 @@
 		for your PCs than for UNIX access.
    This is a fast and simple way to give a large number 
 		of clients access to their home directories with a minimum 
 		of fuss.
    A similar process occurs if the requested section 
-		name is "homes", except that the share name is not 
+		name is "homes", except that the share name is not 
 		changed to that of the requesting user. This method of using
 		the [homes] section works well if different users share 
 		a client PC.
    The [homes] section can specify all the parameters 
@@ -147,8 +147,8 @@ alias|alias|alias|alias...
 		components (if there are more than one) are separated by vertical 
 		bar symbols ('|').
    Note
    On SYSV systems which use lpstat to determine what 
 		printers are defined on the system you may be able to use
-		"printcap name = lpstat" to automatically obtain a list 
-		of printers. See the "printcap name" option 
+		"printcap name = lpstat" to automatically obtain a list 
+		of printers. See the "printcap name" option 
 		for more details.

    PARAMETERS

    parameters define the specific attributes of sections.

    Some parameters are specific to the [global] section (e.g., security). Some parameters are usable in all sections (e.g., create mode). All others @@ -164,16 +164,16 @@ alias|alias|alias|alias... not create best bedfellows, but at least you can find them! Where there are synonyms, the preferred synonym is described, others refer to the preferred synonym.

    VARIABLE SUBSTITUTIONS

    Many of the strings that are settable in the config file - can take substitutions. For example the option "path = - /tmp/%u" would be interpreted as "path = - /tmp/john" if the user connected with the username john.

    These substitutions are mostly noted in the descriptions below, + can take substitutions. For example the option "path = + /tmp/%u" would be interpreted as "path = + /tmp/john" if the user connected with the username john.

    These substitutions are mostly noted in the descriptions below, but there are some general substitutions which apply whenever they might be relevant. These are:

    %U

    session user name (the user name that the client wanted, not necessarily the same as the one they got).

    %G

    primary group name of %U.

    %h

    the Internet hostname that Samba is running on.

    %m

    the NetBIOS name of the client machine (very useful).

    %L

    the NetBIOS name of the server. This allows you to change your config based on what the client calls you. Your - server can have a "dual personality".

    Note that this parameter is not available when Samba listens + server can have a "dual personality".

    Note that this parameter is not available when Samba listens on port 445, as clients no longer send this information

    %M

    the Internet name of the client machine.

    %R

    the selected protocol level after protocol negotiation. It can be one of CORE, COREPLUS, @@ -182,7 +182,7 @@ alias|alias|alias|alias... machine. Only some are recognized, and those may not be 100% reliable. It currently recognizes Samba, WfWg, Win95, WinNT and Win2k. Anything else will be known as - "UNKNOWN". If it gets it wrong then sending a level + "UNKNOWN". If it gets it wrong then sending a level 3 log to samba@samba.org should allow it to be fixed.

    %I

    The IP address of the client machine.

    %T

    the current date and time.

    %D

    Name of the domain or workgroup of the current user.

    %$(envvar)

    The value of the environment variable envar.

    The following substitutes apply only to some configuration options(only those @@ -193,33 +193,33 @@ alias|alias|alias|alias... not compiled Samba with the --with-automount option then this value will be the same as %L.

    %p

    the path of the service's home directory, obtained from your NIS auto.map entry. The NIS auto.map entry - is split up as "%N:%p".

    There are some quite creative things that can be done - with these substitutions and other smb.conf options.

    NAME MANGLING

    Samba supports "name mangling" so that DOS and + is split up as "%N:%p".

    There are some quite creative things that can be done + with these substitutions and other smb.conf options.

    NAME MANGLING

    Samba supports "name mangling" so that DOS and Windows clients can use files that don't conform to the 8.3 format. It can also be set to adjust the case of 8.3 format filenames.

    There are several options that control the way mangling is performed, and they are grouped here rather than listed separately. For the defaults look at the output of the testparm program.

    All of these options can be set separately for each service (or globally, of course).

    The options are:

    mangle case = yes/no

    controls if names that have characters that - aren't of the "default" case are mangled. For example, - if this is yes then a name like "Mail" would be mangled. + aren't of the "default" case are mangled. For example, + if this is yes then a name like "Mail" would be mangled. Default no.

    case sensitive = yes/no

    controls whether filenames are case sensitive. If they aren't then Samba must do a filename search and match on passed names. Default no.

    default case = upper/lower

    controls what the default case is for new filenames. Default lower.

    preserve case = yes/no

    controls if new files are created with the case that the client passes, or if they are forced to be the - "default" case. Default yes. + "default" case. Default yes.

    short preserve case = yes/no

    controls if new files which conform to 8.3 syntax, that is all in upper case and of suitable length, are created - upper case, or if they are forced to be the "default" - case. This option can be use with "preserve case = yes" + upper case, or if they are forced to be the "default" + case. This option can be use with "preserve case = yes" to permit long filenames to retain their case, while short names are lowercased. Default yes.

    By default, Samba 3.0 has the same semantics as a Windows NT server, in that it is case insensitive but case preserving.

    NOTE ABOUT USERNAME/PASSWORD VALIDATION

    There are a number of ways in which a user can connect to a service. The server uses the following steps in determining if it will allow a connection to a specified service. If all the steps fail, then the connection request is rejected. However, if one of the - steps succeeds, then the following steps are not checked.

    If the service is marked "guest only = yes" and the - server is running with share-level security ("security = share") + steps succeeds, then the following steps are not checked.

    If the service is marked "guest only = yes" and the + server is running with share-level security ("security = share") then steps 1 to 5 are skipped.

    1. If the client has passed a username/password pair and that username/password pair is validated by the UNIX system's password programs then the connection is made as that @@ -232,23 +232,28 @@ alias|alias|alias|alias... they match then the connection is allowed as the corresponding user.

    2. If the client has previously validated a username/password pair with the server and the client has passed - the validation token then that username is used.

    3. If a "user = " field is given in the + the validation token then that username is used.

    4. If a "user = " field is given in the smb.conf file for the service and the client has supplied a password, and that password matches (according to the UNIX system's password checking) with one of the usernames - from the "user =" field then the connection is made as - the username in the "user =" line. If one - of the username in the "user =" list begins with a + from the "user =" field then the connection is made as + the username in the "user =" line. If one + of the username in the "user =" list begins with a '@' then that name expands to a list of names in the group of the same name.

    5. If the service is a guest service then a - connection is made as the username given in the "guest - account =" for the service, irrespective of the + connection is made as the username given in the "guest + account =" for the service, irrespective of the supplied password.

    COMPLETE LIST OF GLOBAL PARAMETERS

    Here is a list of all global parameters. See the section of - each parameter for details. Note that some are synonyms.

    COMPLETE LIST OF SERVICE PARAMETERS

    Here is a list of all service parameters. See the section on - each parameter for details. Note that some are synonyms.

    EXPLANATION OF EACH PARAMETER

    abort shutdown script (G)

    This parameter only exists in the HEAD cvs branch + each parameter for details. Note that some are synonyms.

    COMPLETE LIST OF SERVICE PARAMETERS

    Here is a list of all service parameters. See the section on + each parameter for details. Note that some are synonyms.

    EXPLANATION OF EACH PARAMETER

    abort shutdown script (G)

    This parameter only exists in the HEAD cvs branch This a full path name to a script called by smbd(8) that should stop a shutdown procedure issued by the - shutdown script.

    This command will be run as user.

    Default: None.

    Example: abort shutdown script = /sbin/shutdown -c

    add group script (G)

    This is the full pathname to a script that will be run + shutdown script.

    This command will be run as user.

    Default: None.

    Example: abort shutdown script = /sbin/shutdown -c

    acl compatibility (S)

    This parameter specifies what OS ACL semantics should + be compatible with. Possible values are winnt for Windows NT 4, + win2k for Windows 2000 and above and auto. + If you specify auto, the value for this parameter + will be based upon the version of the client. There should + be no reason to change this parameter from the default.

    Default: acl compatibility = Auto

    Example: acl compatibility = win2k

    add group script (G)

    This is the full pathname to a script that will be run AS ROOT by smbd(8) when a new group is requested. It will expand any %g to the group name passed. This script is only useful for installations using the Windows NT @@ -264,7 +269,7 @@ alias|alias|alias|alias... machines -c Machine -d /dev/null -s /bin/false %u

    addprinter command (G)

    With the introduction of MS-RPC based printing support for Windows NT/2000 clients in Samba 2.2, The MS Add Printer Wizard (APW) icon is now also available in the - "Printers..." folder displayed a share listing. The APW + "Printers..." folder displayed a share listing. The APW allows for printers to be add remotely to a Samba or Windows NT/2000 print server.

    For a Samba host this means that the printer must be physically added to the underlying printing system. The add @@ -275,15 +280,15 @@ alias|alias|alias|alias... shared by smbd(8).

    The addprinter command is automatically invoked with the following parameter (in order):

    • printer name

    • share name

    • port name

    • driver name

    • location

    • Windows 9x driver location

    All parameters are filled in from the PRINTER_INFO_2 structure sent - by the Windows NT/2000 client with one exception. The "Windows 9x - driver location" parameter is included for backwards compatibility + by the Windows NT/2000 client with one exception. The "Windows 9x + driver location" parameter is included for backwards compatibility only. The remaining fields in the structure are generated from answers to the APW questions.

    Once the addprinter command has been executed, smbd will reparse the smb.conf to determine if the share defined by the APW exists. If the sharename is still invalid, then smbd will return an ACCESS_DENIED error to the client.

    - The "add printer command" program can output a single line of text, + The "add printer command" program can output a single line of text, which Samba will set as the port the new printer is connected to. If this line isn't output, Samba won't reload its printer shares.

    See also @@ -322,7 +327,7 @@ alias|alias|alias|alias... created for all users accessing files on this server. For sites that use Windows NT account databases as their primary user database creating these users and keeping the user list in sync with the - Windows NT PDC is an onerous task. This option allows smbd to create the required UNIX users + Windows NT PDC is an onerous task. This option allows smbd to create the required UNIX users ON DEMAND when a user accesses the Samba server.

    In order to use this option, smbd(8) must NOT be set to security = share and add user script must be set to a full pathname for a script that will create a UNIX @@ -367,7 +372,7 @@ alias|alias|alias|alias... security option is set to server or domain. If it is set to no, then attempts to connect to a resource from - a domain or workgroup other than the one which smbd is running + a domain or workgroup other than the one which smbd is running in will fail, even if that domain is trusted by the remote server doing the authentication.

    This is useful if you only want your Samba server to serve resources to users in the domain it is a member of. As @@ -378,8 +383,8 @@ alias|alias|alias|alias... Samba server even if they do not have an account in DOMA. This can make implementing a security boundary difficult.

    Default: allow trusted domains = yes

    announce as (G)

    This specifies what type of server nmbd(8) will announce itself as, to a network neighborhood browse list. By default this is set to Windows NT. The valid options - are : "NT Server" (which can also be written as "NT"), - "NT Workstation", "Win95" or "WfW" meaning Windows NT Server, + are : "NT Server" (which can also be written as "NT"), + "NT Workstation", "Win95" or "WfW" meaning Windows NT Server, Windows NT Workstation, Windows 95 and Windows for Workgroups respectively. Do not change this parameter unless you have a specific need to stop Samba appearing as an NT server as this @@ -402,7 +407,7 @@ alias|alias|alias|alias... method of authentication for remote domain users; deprecated in favour of winbind method), trustdomain (authenticate trusted users by contacting the remote DC directly from smbd; deprecated in favour of winbind method).

    Default: auth methods = <empty string>

    Example: auth methods = guest sam winbind

    auto services (G)

    This is a synonym for the - preload.

    available (S)

    This parameter lets you "turn off" a service. If + preload.

    available (S)

    This parameter lets you "turn off" a service. If available = no, then ALL attempts to connect to the service will fail. Such failures are logged.

    Default: available = yes

    bind interfaces only (G)

    This global parameter allows the Samba admin @@ -410,7 +415,7 @@ alias|alias|alias|alias... affects file service smbd(8) and name service nmbd(8) in a slightly different ways.

    For name service it causes nmbd to bind to ports 137 and 138 on the interfaces listed in the interfaces parameter. nmbd also - binds to the "all addresses" interface (0.0.0.0) + binds to the "all addresses" interface (0.0.0.0) on ports 137 and 138 for the purposes of reading broadcast messages. If this option is not set then nmbd will service name requests on all of these sockets. If bind interfaces @@ -447,7 +452,7 @@ alias|alias|alias|alias... 127.0.0.1 to determine if they are running. Not adding 127.0.0.1 will cause smbd and nmbd to always show - "not running" even if they really are. This can prevent + "not running" even if they really are. This can prevent swat from starting/stopping/restarting smbd and nmbd.

    Default: bind interfaces only = no

    blocking locks (S)

    This parameter controls the behavior of smbd(8) when given a request by a client @@ -474,7 +479,7 @@ alias|alias|alias|alias... a client doing a NetServerEnum call. Normally set to yes. You should never need to change this.

    Default: browse list = yes

    case sensitive (S)

    See the discussion in the section NAME MANGLING.

    Default: case sensitive = no

    casesignames (S)

    Synonym for case sensitive.

    change notify timeout (G)

    This SMB allows a client to tell a server to - "watch" a particular directory for any changes and only reply to + "watch" a particular directory for any changes and only reply to the SMB request when a change has occurred. Such constant scanning of a directory is expensive under UNIX, hence an smbd(8) daemon only performs such a scan on each requested directory once every change notify @@ -499,17 +504,49 @@ alias|alias|alias|alias... with the new share.

    This parameter is only used modify existing file shares definitions. To modify - printer shares, use the "Printers..." folder as seen when browsing the Samba host. + printer shares, use the "Printers..." folder as seen when browsing the Samba host.

    See also add share command, delete share command. -

    Default: none

    Example: change share command = /usr/local/bin/addshare

    client use spnego (G)

    This variable controls controls whether samba clients will try +

    Default: none

    Example: change share command = /usr/local/bin/addshare

    client lanman auth (G)

    This parameter determines whether or not smbclient(8) and other samba client + tools will attempt to authenticate itself to servers using the + weaker LANMAN password hash. If disabled, only server which support NT + password hashes (e.g. Windows NT/2000, Samba, etc... but not + Windows 95/98) will be able to be connected from the Samba client.

    The LANMAN encrypted response is easily broken, due to it's + case-insensitive nature, and the choice of algorithm. Clients + without Windows 95/98 servers are advised to disable + this option.

    Disabling this option will also disable the client plaintext auth option

    Likewise, if the client ntlmv2 + auth parameter is enabled, then only NTLMv2 logins will be + attempted. Not all servers support NTLMv2, and most will require + special configuration to us it.

    Default : client lanman auth = yes

    client ntlmv2 auth (G)

    This parameter determines whether or not smbclient(8) will attempt to + authenticate itself to servers using the NTLMv2 encrypted password + response.

    If enabled, only an NTLMv2 and LMv2 response (both much more + secure than earlier versions) will be sent. Many servers + (including NT4 < SP4, Win9x and Samba 2.2) are not compatible with + NTLMv2.

    If disabled, an NTLM response (and possibly a LANMAN response) + will be sent by the client, depending on the value of client lanman auth.

    Note that some sites (particularly + those following 'best practice' security polices) only allow NTLMv2 + responses, and not the weaker LM or NTLM.

    Default : client ntlmv2 auth = no

    client plaintext auth (G)

    Specifies whether a client should send a plaintext + password if the server does not support encrypted passwords.

    Default: client plaintext auth = yes

    client schannel (G)

    This controls whether the client offers or even + demands the use of the netlogon schannel. + client schannel = no does not + offer the schannel, server schannel = + auto offers the schannel but does not + enforce it, and server schannel = + yes denies access if the server is not + able to speak netlogon schannel.

    Default: client schannel = auto

    Example: client schannel = yes

    client signing (G)

    This controls whether the client offers or requires + the server it talks to to use SMB signing. Possible values + are auto, mandatory + and disabled. +

    When set to auto, SMB signing is offered, but not enforced. + When set to mandatory, SMB signing is required and if set + to disabled, SMB signing is not offered either.

    Default: client signing = auto

    client use spnego (G)

    This variable controls controls whether samba clients will try to use Simple and Protected NEGOciation (as specified by rfc2478) with WindowsXP and Windows2000 servers to agree upon an authentication mechanism. - SPNEGO client support with Sign and Seal is currently broken, so - you might want to turn this option off when doing joins to - Windows 2003 domains. + SPNEGO client support for SMB Signing is currently broken, so + you might want to turn this option off when operating with + Windows 2003 domain controllers in particular.

    Default: client use spnego = yes

    comment (S)

    This is a text field that is seen next to a share when a client does a queries the server, either via the network neighborhood or via net view to list what shares @@ -523,7 +560,7 @@ alias|alias|alias|alias... the new config file.

    This option takes the usual substitutions, which can be very useful.

    If the config file doesn't exist then it won't be loaded (allowing you to special case the config files of just a few - clients).

    Example: config file = /usr/local/samba/lib/smb.conf.%m

    copy (S)

    This parameter allows you to "clone" service + clients).

    Example: config file = /usr/local/samba/lib/smb.conf.%m

    copy (S)

    This parameter allows you to "clone" service entries. The specified service is simply duplicated under the current service's name. Any parameters specified in the current section will override those in the section being copied.

    This feature lets you set up a 'template' service and @@ -556,7 +593,7 @@ alias|alias|alias|alias... policy, and specifies how clients capable of offline caching will cache the files in the share. The valid values are: manual, documents, programs, disable.

    These values correspond to those used on Windows servers.

    For example, shares containing roaming profiles can have - offline caching disabled using csc policy = disable.

    Default: csc policy = manual

    Example: csc policy = programs

    dead time (G)

    The value of the parameter (a decimal integer) + offline caching disabled using csc policy = disable.

    Default: csc policy = manual

    Example: csc policy = programs

    deadtime (G)

    The value of the parameter (a decimal integer) represents the number of minutes of inactivity before a connection is considered dead, and it is disconnected. The deadtime only takes effect if the number of open files is zero.

    This is useful to stop a server's resources being @@ -569,7 +606,7 @@ alias|alias|alias|alias... boolean parameter adds microsecond resolution to the timestamp message header when turned on.

    Note that the parameter debug timestamp must be on for this to have an - effect.

    Default: debug hires timestamp = no

    debug level (G)

    Synonym for + effect.

    Default: debug hires timestamp = no

    debuglevel (G)

    Synonym for log level.

    debug pid (G)

    When using only one log file for more then one forked smbd(8)-process there may be hard to follow which process outputs which message. This boolean parameter @@ -619,8 +656,8 @@ alias|alias|alias|alias... read-only service.

    Also note that the apparent service name will be changed to equal that of the requested service, this is very useful as it allows you to use macros like %S to make - a wildcard service.

    Note also that any "_" characters in the name of the service - used in the default service will get mapped to a "/". This allows for + a wildcard service.

    Note also that any "_" characters in the name of the service + used in the default service will get mapped to a "/". This allows for interesting things.

    Example:

     [global]
 	default service = pub
@@ -641,7 +678,7 @@ alias|alias|alias|alias...
     from the print system and from smb.conf.
     
    The deleteprinter command is 
     automatically called with only one parameter: 
-    "printer name".
    Once the deleteprinter command has 
+    "printer name".
    Once the deleteprinter command has 
     been executed, smbd will reparse the 
     smb.conf to associated printer no longer exists.  
     If the sharename is still valid, then smbd
@@ -703,8 +740,8 @@ alias|alias|alias|alias...
 	should only be used on systems where a problem occurs with the
 	internal disk space calculations. This has been known to happen
 	with Ultrix, but may occur with other operating systems. The
-	symptom that was seen was an error of "Abort Retry
-	Ignore" at the end of each directory listing.
    This setting allows the replacement of the internal routines to
+	symptom that was seen was an error of "Abort Retry
+	Ignore" at the end of each directory listing.
    This setting allows the replacement of the internal routines to
 	calculate the total disk space and amount available with an external
 	routine. The example below gives a possible script that might fulfill
 	this function.
    The external program will be passed a single parameter indicating 
@@ -718,10 +755,10 @@ alias|alias|alias|alias...
 	determining the disk capacity and remaining space will be used.
 	
    Example: dfree command = /usr/local/samba/bin/dfree
    Where the script dfree (which must be made executable) could be:
     
 #!/bin/sh
-df $1 | tail -1 | awk '{print $2" "$4}'
+df $1 | tail -1 | awk '{print $2" "$4}'
 
    or perhaps (on Sys V based systems):
     
 #!/bin/sh
-/usr/bin/df -k $1 | tail -1 | awk '{print $3" "$5}'
+/usr/bin/df -k $1 | tail -1 | awk '{print $3" "$5}'
 
    Note that you may have to replace the command names with full path names on some systems.
    directory (S)

    Synonym for path.

    directory mask (S)

    This parameter is the octal modes which are used when converting DOS modes to UNIX modes when creating UNIX directories.

    When a directory is created, the necessary permissions are @@ -756,7 +793,7 @@ df $1 | tail -1 | awk '{print $2" "$4}' meaning a user is allowed to modify all the user/group/world permissions on a directory.

    Note that users who can access the Samba server through other means can easily bypass this restriction, - so it is primarily useful for standalone "appliance" systems. + so it is primarily useful for standalone "appliance" systems. Administrators of most normal systems will probably want to leave it as the default of 0777.

    See also the force directory security mode, @@ -820,7 +857,7 @@ df $1 | tail -1 | awk '{print $2" "$4}' of interest to clients or are infinitely deep (recursive). This parameter allows you to specify a comma-delimited list of directories that the server should always show as empty.

    Note that Samba can be very fussy about the exact format - of the "dont descend" entries. For example you may need + of the "dont descend" entries. For example you may need ./proc instead of just /proc. Experimentation is the best policy :-)

    Default: none (i.e., all directories are OK to descend)

    Example: dont descend = /proc,/dev

    dos charset (G)

    DOS SMB clients assume the server has @@ -857,11 +894,18 @@ df $1 | tail -1 | awk '{print $2" "$4}' timestamp on a file if the user smbd is acting on behalf of is not the file owner. Setting this option to yes allows DOS semantics and smbd(8) will change the file - timestamp as DOS requires.

    Default: dos filetimes = no

    encrypt passwords (G)

    This boolean controls whether encrypted passwords + timestamp as DOS requires.

    Default: dos filetimes = no

    enable rid algorithm (G)

    This option is used to control whether or not smbd in Samba 3.0 should fallback + to the algorithm used by Samba 2.2 to generate user and group RIDs. The longterm + development goal is to remove the algorithmic mappings of RIDs altogether, but + this has proved to be difficult. This parameter is mainly provided so that + developers can turn the algorithm on and off and see what breaks. This parameter + should not be disabled by non-developers because certain features in Samba will fail + to work without it. +

    Default: enable rid algorithm = <yes>

    encrypt passwords (G)

    This boolean controls whether encrypted passwords will be negotiated with the client. Note that Windows NT 4.0 SP3 and above and also Windows 98 will by default expect encrypted passwords unless a registry entry is changed. To use encrypted passwords in - Samba see the chapter "User Database" in the Samba HOWTO Collection.

    In order for encrypted passwords to work correctly + Samba see the chapter "User Database" in the Samba HOWTO Collection.

    In order for encrypted passwords to work correctly smbd(8) must either have access to a local smbpasswd(5) file (see the smbpasswd(8) program for information on how to set up and maintain this file), or set the security = [server|domain|ads] parameter which @@ -877,16 +921,16 @@ df $1 | tail -1 | awk '{print $2" "$4}' workgroups not disappearing from browse lists. Due to the restrictions of the browse protocols these enhancements can cause a empty workgroup to stay around forever which can be annoying.

    In general you should leave this option enabled as it makes - cross-subnet browse propagation much more reliable.

    Default: enhanced browsing = yes

    enumports command (G)

    The concept of a "port" is fairly foreign + cross-subnet browse propagation much more reliable.

    Default: enhanced browsing = yes

    enumports command (G)

    The concept of a "port" is fairly foreign to UNIX hosts. Under Windows NT/2000 print servers, a port is associated with a port monitor and generally takes the form of a local port (i.e. LPT1:, COM1:, FILE:) or a remote port (i.e. LPD Port Monitor, etc...). By default, Samba has only one - port defined--"Samba Printer Port". Under + port defined--"Samba Printer Port". Under Windows NT/2000, all printers must have a valid port name. If you wish to have a list of ports displayed (smbd does not use a port name for anything) other than - the default "Samba Printer Port", you + the default "Samba Printer Port", you can define enumports command to point to a program which should generate a list of ports, one per line, to standard output. This listing will then be used in response @@ -968,7 +1012,7 @@ df $1 | tail -1 | awk '{print $2" "$4}' allows a user to modify all the user/group/world permissions on a directory without restrictions.

    Note that users who can access the Samba server through other means can easily bypass this restriction, - so it is primarily useful for standalone "appliance" systems. + so it is primarily useful for standalone "appliance" systems. Administrators of most normal systems will probably want to leave it set as 0000.

    See also the directory security mask, @@ -1005,7 +1049,7 @@ df $1 | tail -1 | awk '{print $2" "$4}' and allows a user to modify all the user/group/world permissions on a file, with no restrictions.

    Note that users who can access the Samba server through other means can easily bypass this restriction, - so it is primarily useful for standalone "appliance" systems. + so it is primarily useful for standalone "appliance" systems. Administrators of most normal systems will probably want to leave this set to 0000.

    See also the force directory security mode, @@ -1017,7 +1061,7 @@ df $1 | tail -1 | awk '{print $2" "$4}' as using it incorrectly can cause security problems.

    This user name only gets used once a connection is established. Thus clients still need to connect as a valid user and supply a valid password. Once connected, all file operations will be performed - as the "forced user", no matter what username the client connected + as the "forced user", no matter what username the client connected as. This can be very useful.

    In Samba 2.0.5 and above this parameter also causes the primary group of the forced user to be used as the primary group for all file activity. Prior to 2.0.5 the primary group was left @@ -1027,7 +1071,13 @@ df $1 | tail -1 | awk '{print $2" "$4}' for a share. The default type is NTFS for compatibility with Windows NT but this can be changed to other strings such as Samba or FAT - if required.

    Default: fstype = NTFS

    Example: fstype = Samba

    getwd cache (G)

    This is a tuning option. When this is enabled a + if required.

    Default: fstype = NTFS

    Example: fstype = Samba

    get quota command (G)

    The get quota command should only be used + whenever there is no operating system API available from the OS that + samba can use.

    This parameter should specify the path to a script that + queries the quota information for the specified + user/group for the partition that + the specified directory is on.

    Such a script should take 3 arguments:

    • directory

    • type of query

    • uid of user or gid of group

    The type of query can be one of :

    • 1 - user quotas

    • 2 - user default quotas (uid = -1)

    • 3 - group quotas

    • 4 - group default quotas (gid = -1)

    This script should print its output according to the following format:

    • Line 1 - quota flags (0 = no quotas, 1 = quotas enabled, 2 = quotas enabled and enforced)

    • Line 2 - number of currently used blocks

    • Line 3 - the softlimit number of blocks

    • Line 4 - the hardlimit number of blocks

    • Line 5 - currently used number of inodes

    • Line 6 - the softlimit number of inodes

    • Line 7 - the hardlimit number of inodes

    • Line 8(optional) - the number of bytes in a block(default is 1024)

    See also the set quota command parameter. +

    Default: get quota command =

    Example: get quota command = /usr/local/sbin/query_quota

    getwd cache (G)

    This is a tuning option. When this is enabled a caching algorithm will be used to reduce the time taken for getwd() calls. This can have a significant impact on performance, especially when the wide links @@ -1037,17 +1087,17 @@ df $1 | tail -1 | awk '{print $2" "$4}' guest ok (see below). Whatever privileges this user has will be available to any client connecting to the guest service. Typically this user will exist in the password file, but will not - have a valid login. The user account "ftp" is often a good choice + have a valid login. The user account "ftp" is often a good choice for this parameter. If a username is specified in a given service, the specified username overrides this one. -

    One some systems the default guest account "nobody" may not +

    One some systems the default guest account "nobody" may not be able to print. Use another account in this case. You should test this by trying to log in as your guest user (perhaps by using the su - command) and trying to print using the system print command such as lpr(1) or lp(1).

    This parameter does not accept % macros, because many parts of the system require this value to be - constant for correct operation.

    Default: specified at compile time, usually "nobody"

    Example: guest account = ftp

    guest ok (S)

    If this parameter is yes for + constant for correct operation.

    Default: specified at compile time, usually "nobody"

    Example: guest account = ftp

    guest ok (S)

    If this parameter is yes for a service, then no password is required to connect to the service. Privileges will be those of the guest account.

    This paramater nullifies the benifits of setting @@ -1102,7 +1152,7 @@ df $1 | tail -1 | awk '{print $2" "$4}' to browse Dfs trees hosted on the server.

    See also the msdfs root share level parameter. For more information on setting up a Dfs tree on Samba, - refer to msdfs_setup.html. + refer to ???.

    Default: host msdfs = no

    hostname lookups (G)

    Specifies whether samba should use (expensive) hostname lookups or use the ip addresses instead. An example place where hostname lookups are currently used is when checking @@ -1122,7 +1172,7 @@ df $1 | tail -1 | awk '{print $2" "$4}' hosts deny option.

    You can also specify hosts by network/netmask pairs and by netgroup names if your system supports netgroups. The EXCEPT keyword can also be used to limit a - wildcard list. The following examples may provide some help:

    Example 1: allow all IPs in 150.203.*.*; except one

    hosts allow = 150.203. EXCEPT 150.203.6.66

    Example 2: allow hosts that match the given network/netmask

    hosts allow = 150.203.15.0/255.255.255.0

    Example 3: allow a couple of hosts

    hosts allow = lapland, arvidsjaur

    Example 4: allow only hosts in NIS netgroup "foonet", but + wildcard list. The following examples may provide some help:

    Example 1: allow all IPs in 150.203.*.*; except one

    hosts allow = 150.203. EXCEPT 150.203.6.66

    Example 2: allow hosts that match the given network/netmask

    hosts allow = 150.203.15.0/255.255.255.0

    Example 3: allow a couple of hosts

    hosts allow = lapland, arvidsjaur

    Example 4: allow only hosts in NIS netgroup "foonet", but deny access from one particular host

    hosts allow = @foonet

    hosts deny = pirate

    Note

    Note that access still requires suitable user-level passwords.

    See testparm(1) for a way of testing your host access to see if it does what you expect.

    Default: none (i.e., all hosts permitted access)

    Example: allow hosts = 150.203.5. myhost.mynet.edu.au

    hosts deny (S)

    The opposite of hosts allow - hosts listed here are NOT permitted access to @@ -1142,7 +1192,13 @@ df $1 | tail -1 | awk '{print $2" "$4}' hosts equiv option be only used if you really know what you are doing, or perhaps on a home network where you trust your spouse and kids. And only if you really trust - them :-).

    Default: no host equivalences

    Example: hosts equiv = /etc/hosts.equiv

    idmap gid (G)

    The idmap gid parameter specifies the range of group ids that are allocated for + them :-).

    Default: no host equivalences

    Example: hosts equiv = /etc/hosts.equiv

    idmap backend (G)

    + The purpose of the idmap backend parameter is to allow idmap to NOT use the local idmap + tdb file to obtain SID to UID / GID mappings, but instead to obtain them from a common + LDAP backend. This way all domain members and controllers will have the same UID and GID + to SID mappings. This avoids the risk of UID / GID inconsistencies across UNIX / Linux + systems that are sharing information over protocols other than SMB/CIFS (ie: NFS). +

    Default: idmap backend = <empty string>

    Example: idmap backend = ldap:ldap://ldapslave.example.com

    idmap gid (G)

    The idmap gid parameter specifies the range of group ids that are allocated for the purpose of mapping UNX groups to NT group SIDs. This range of group ids should have no existing local or NIS groups within it as strange conflicts can occur otherwise.

    The availability of an idmap gid range is essential for correct operation of all group mapping.

    Default: idmap gid = <empty string>

    Example: idmap gid = 10000-20000

    idmap uid (G)

    The idmap uid parameter specifies the range of user ids that are allocated for use @@ -1185,11 +1241,11 @@ df $1 | tail -1 | awk '{print $2" "$4}' interfaces except 127.0.0.1 that are broadcast capable.

    The option takes a list of interface strings. Each string can be in any of the following forms:

    • a network interface name (such as eth0). This may include shell-like wildcards so eth* will match - any interface starting with the substring "eth"

    • an IP address. In this case the netmask is + any interface starting with the substring "eth"

    • an IP address. In this case the netmask is determined from the list of interfaces obtained from the - kernel

    • an IP/mask pair.

    • a broadcast/mask pair.

    The "mask" parameters can either be a bit length (such + kernel

  • an IP/mask pair.

  • a broadcast/mask pair.

    • The "mask" parameters can either be a bit length (such as 24 for a C class network) or a full netmask in dotted - decimal form.

    The "IP" parameters above can either be a full dotted + decimal form.

    The "IP" parameters above can either be a full dotted decimal IP address or a hostname which will be looked up via the OS's normal hostname resolution mechanisms.

    For example, the following line:

    interfaces = eth0 192.168.2.10/24 192.168.3.10/255.255.255.0

    would configure three network interfaces corresponding to the eth0 device and IP addresses 192.168.2.10 and 192.168.3.10. @@ -1218,7 +1274,12 @@ df $1 | tail -1 | awk '{print $2" "$4}' a client is still present and responding.

    Keepalives should, in general, not be needed if the socket being used has the SO_KEEPALIVE attribute set on it (see socket options). - Basically you should only use this option if you strike difficulties.

    Default: keepalive = 300

    Example: keepalive = 600

    kernel oplocks (G)

    For UNIXes that support kernel based + Basically you should only use this option if you strike difficulties.

    Default: keepalive = 300

    Example: keepalive = 600

    kernel change notify (G)

    This parameter specifies whether Samba should ask the + kernel for change notifications in directories so that + SMB clients can refresh whenever the data on the server changes. +

    This parameter is only usd when your kernel supports + change notification to user programs, using the F_NOTIFY fcntl. +

    Default: Yes

    kernel oplocks (G)

    For UNIXes that support kernel based oplocks (currently only IRIX and the Linux 2.4 kernel), this parameter allows the use of them to be turned on or off.

    Kernel oplocks support allows Samba oplocks @@ -1263,7 +1324,12 @@ df $1 | tail -1 | awk '{print $2" "$4}' The default is to match the login name with the uid attribute for all entries matching the sambaAccount objectclass. Note that this filter should only return one entry. -

    Default: ldap filter = (&(uid=%u)(objectclass=sambaAccount))

    ldap machine suffix (G)

    It specifies where machines should be added to the ldap tree.

    Default: none

    ldap passwd sync (G)

    This option is used to define whether +

    Default: ldap filter = (&(uid=%u)(objectclass=sambaAccount))

    ldap group suffix (G)

    This parameters specifies the suffix that is + used for groups when these are added to the LDAP directory. + If this parameter is unset, the value of ldap suffix will be used instead.

    Default: none

    Example: dc=samba,ou=Groups

    ldap idmap suffix (G)

    This parameters specifies the suffix that is + used when storing idmap mappings. If this parameter + is unset, the value of ldap suffix + will be used instead.

    Default: none

    Example: dc=samba,ou=Idmap

    ldap machine suffix (G)

    It specifies where machines should be added to the ldap tree.

    Default: none

    ldap passwd sync (G)

    This option is used to define whether or not Samba should sync the LDAP password with the NT and LM hashes for normal accounts (NOT for workstation, server or domain trusts) on a password @@ -1295,16 +1361,8 @@ df $1 | tail -1 | awk '{print $2" "$4}' tree. Can be overriden by ldap user suffix and ldap machine suffix. It also used as the base dn for all ldap - searches.

    Default: none

    ldap trust ids (G)

    Normally, Samba validates each entry in the LDAP server - against getpwnam(). This allows LDAP to be used for Samba with - the unix system using NIS (for example) and also ensures that - Samba does not present accounts that do not otherwise exist. -

    This option is used to disable this functionality, and - instead to rely on the presence of the appropriate attributes - in LDAP directly, which can result in a significant performance - boost in some situations. Setting this option to yes effectivly - assumes that the local machine is running nss_ldap against the same LDAP - server.

    Default: ldap trust ids = No

    ldap user suffix (G)

    It specifies where users are added to the tree.

    Default: none

    level2 oplocks (S)

    This parameter controls whether Samba supports + searches.

    Default: none

    ldap user suffix (G)

    This parameter specifies where users are added to the tree. + If this parameter is not specified, the value from ldap suffix.

    Default: none

    level2 oplocks (S)

    This parameter controls whether Samba supports level2 (read-only) oplocks on a share.

    Level2, or read-only oplocks allow Windows NT clients that have an oplock on a file to downgrade from a read-write oplock to a read-only oplock once a second client opens the file (instead @@ -1315,7 +1373,7 @@ df $1 | tail -1 | awk '{print $2" "$4}' for many accesses of files that are not commonly written (such as application .EXE files).

    Once one of the clients which have a read-only oplock writes to the file all clients are notified (no reply is needed - or waited for) and told to break their oplocks to "none" and + or waited for) and told to break their oplocks to "none" and delete any read-ahead caches.

    It is recommended that this parameter be turned on to speed access to shared executables.

    For more discussions on level2 oplocks see the CIFS spec.

    Currently, if kernel oplocks are supported then level2 oplocks are @@ -1376,7 +1434,7 @@ df $1 | tail -1 | awk '{print $2" "$4}' in case the lock could later be aquired. This behavior is used to support PC database formats such as MS Access and FoxPro. -

    Default: lock spin count = 2

    lock spin time (G)

    The time in microseconds that smbd should +

    Default: lock spin count = 3

    lock spin time (G)

    The time in microseconds that smbd should pause before attempting to gain a failed lock. See lock spin count for more details.

    Default: lock spin time = 10

    log file (G)

    This option allows you to override the name @@ -1407,14 +1465,14 @@ df $1 | tail -1 | awk '{print $2" "$4}' logon home. This broke net use /home but allowed profiles outside the home directory. The current implementation is correct, and can be used for profiles if you use the above trick.

    This option is only useful if Samba is set up as a logon - server.

    Default: logon home = "\\%N\%U"

    Example: logon home = "\\remote_smb_server\%U"

    logon path (G)

    This parameter specifies the home directory + server.

    Default: logon home = "\\%N\%U"

    Example: logon home = "\\remote_smb_server\%U"

    logon path (G)

    This parameter specifies the home directory where roaming profiles (NTuser.dat etc files for Windows NT) are stored. Contrary to previous versions of these manual pages, it has nothing to do with Win 9X roaming profiles. To find out how to handle roaming profiles for Win 9X system, see the logon home parameter.

    This option takes the standard substitutions, allowing you to have separate logon scripts for each user or machine. It also - specifies the directory from which the "Application Data", + specifies the directory from which the "Application Data", (desktop, start menu, network neighborhood, programs and other folders, and their contents, are loaded and displayed on @@ -1443,8 +1501,8 @@ df $1 | tail -1 | awk '{print $2" "$4}' suggested command would be to add NET TIME \\SERVER /SET /YES, to force every machine to synchronize clocks with the same time server. Another use would be to add NET USE - U: \\SERVER\UTILS for commonly used utilities, or - NET USE Q: \\SERVER\ISO9001_QA for example.

    Note that it is particularly important not to allow write + U: \\SERVER\UTILS for commonly used utilities, or 

    +	NET USE Q: \\SERVER\ISO9001_QA

    for example.

    Note that it is particularly important not to allow write access to the [netlogon] share, or to grant users write permission on the batch files in a secure environment, as this would allow the batch files to be arbitrarily modified and security to be @@ -1519,8 +1577,8 @@ df $1 | tail -1 | awk '{print $2" "$4}' parameter.

    Default: depends on the setting of printing

    Example 1: lprm command = /usr/bin/lprm -P%p %j

    Example 2: lprm command = /usr/bin/cancel %p-%j

    machine password timeout (G)

    If a Samba server is a member of a Windows NT Domain (see the security = domain) - parameter) then periodically a running - smbd(8) process will try and change the MACHINE ACCOUNT + parameter) then periodically a running smbd + process will try and change the MACHINE ACCOUNT PASSWORD stored in the TDB called private/secrets.tdb . This parameter specifies how often this password will be changed, in seconds. The default is one week (expressed in @@ -1552,12 +1610,12 @@ df $1 | tail -1 | awk '{print $2" "$4}' you would use:

    mangled map = (*.html *.htm)

    One very useful case is to remove the annoying ;1 off the ends of filenames on some CDROMs (only visible under some UNIXes). To do this use a map of (*;1 *;).

    Default: no mangled map

    Example: mangled map = (*;1 *;)

    mangled names (S)

    This controls whether non-DOS names under UNIX - should be mapped to DOS-compatible names ("mangled") and made visible, + should be mapped to DOS-compatible names ("mangled") and made visible, or whether non-DOS names should simply be ignored.

    See the section on NAME MANGLING for details on how to control the mangling process.

    If mangling is used then the mangling algorithm is as follows:

    • The first (up to) five alphanumeric characters before the rightmost dot of the filename are preserved, forced to upper case, and appear as the first (up to) five characters - of the mangled name.

    • A tilde "~" is appended to the first part of the mangled + of the mangled name.

    • A tilde "~" is appended to the first part of the mangled name, followed by a two-character unique sequence, based on the original root name (i.e., the original filename minus its final extension). The final extension is included in the hash calculation @@ -1569,9 +1627,9 @@ df $1 | tail -1 | awk '{print $2" "$4}' extension of the mangled name. The final extension is defined as that part of the original filename after the rightmost dot. If there are no dots in the filename, the mangled name will have no extension (except - in the case of "hidden files" - see below).

    • Files whose UNIX name begins with a dot will be + in the case of "hidden files" - see below).

    • Files whose UNIX name begins with a dot will be presented as DOS hidden files. The mangled name will be created as - for other filenames, but with the leading dot removed and "___" as + for other filenames, but with the leading dot removed and "___" as its extension regardless of actual original extension (that's three underscores).

    The two-digit hash value consists of upper case alphanumeric characters.

    This algorithm can cause name collisions only if files in a directory share the same first five alphanumeric characters. @@ -1579,7 +1637,7 @@ df $1 | tail -1 | awk '{print $2" "$4}' copied between UNIX directories from Windows/DOS while retaining the long UNIX filename. UNIX files can be renamed to a new extension from Windows/DOS and will retain the same basename. Mangled names - do not change between sessions.

    Default: mangled names = yes

    mangling stack (G)

    This parameter controls the number of mangled names + do not change between sessions.

    Default: mangled names = yes

    mangled stack (G)

    This parameter controls the number of mangled names that should be cached in the Samba server smbd(8).

    This stack is a list of recently mangled base names (extensions are only maintained if they are longer than 3 characters or contains upper case characters).

    The larger this value, the more likely it is that mangled @@ -1587,17 +1645,19 @@ df $1 | tail -1 | awk '{print $2" "$4}' However, large stack sizes will slow most directory accesses. Smaller stacks save memory in the server (each stack element costs 256 bytes).

    It is not possible to absolutely guarantee correct long - filenames, so be prepared for some surprises!

    Default: mangled stack = 50

    Example: mangled stack = 100

    mangling prefix (G)

    controls the number of prefix + filenames, so be prepared for some surprises!

    Default: mangled stack = 50

    Example: mangled stack = 100

    mangle prefix (G)

    controls the number of prefix characters from the original name used when generating the mangled names. A larger value will give a weaker hash and therefore more name collisions. The minimum - value is 1 and the maximum value is 6.

    Default: mangle prefix = 1

    Example: mangle prefix = 4

    mangling char (S)

    This controls what character is used as + value is 1 and the maximum value is 6.

    + mangle prefix is effective only when mangling method is hash2. +

    Default: mangle prefix = 1

    Example: mangle prefix = 4

    mangling char (S)

    This controls what character is used as the magic character in name mangling. The default is a '~' but this may interfere with some software. Use this option to set - it to whatever you prefer.

    Default: mangling char = ~

    Example: mangling char = ^

    mangling method (G)

    controls the algorithm used for the generating - the mangled names. Can take two different values, "hash" and - "hash2". "hash" is the default and is the algorithm that has been - used in Samba for many years. "hash2" is a newer and considered + it to whatever you prefer. This is effective only when mangling method is hash.

    Default: mangling char = ~

    Example: mangling char = ^

    mangling method (G)

    controls the algorithm used for the generating + the mangled names. Can take two different values, "hash" and + "hash2". "hash" is the default and is the algorithm that has been + used in Samba for many years. "hash2" is a newer and considered a better algorithm (generates less collisions) in the names. However, many Win32 applications store the mangled names and so changing to the new algorithm must not be done @@ -1638,18 +1698,18 @@ df $1 | tail -1 | awk '{print $2" "$4}' with an invalid password are treated as a guest login and mapped into the guest account. Note that this can cause problems as it means that any user incorrectly typing - their password will be silently logged on as "guest" - and + their password will be silently logged on as "guest" - and will not know the reason they cannot access files they think they should - there will have been no message given to them that they got their password wrong. Helpdesk services will hate you if you set the map to - guest parameter this way :-).

    Note that this parameter is needed to set up "Guest" + guest parameter this way :-).

    Note that this parameter is needed to set up "Guest" share services when using security modes other than share. This is because in these modes the name of the resource being requested is not sent to the server until after the server has successfully authenticated the client so the server cannot make authentication decisions at the correct time (connection - to the share) for "Guest" shares.

    For people familiar with the older Samba releases, this + to the share) for "Guest" shares.

    For people familiar with the older Samba releases, this parameter maps to the old compile-time setting of the GUEST_SESSSETUP value in local.h.

    Default: map to guest = Never

    Example: map to guest = Bad User

    max connections (S)

    This option allows the number of simultaneous connections to a service to be limited. If max connections is greater than 0 then connections @@ -1679,8 +1739,8 @@ df $1 | tail -1 | awk '{print $2" "$4}' by the UNIX per-process file descriptor limit rather than this parameter so you should never need to touch this parameter.

    Default: max open files = 10000

    max print jobs (S)

    This parameter limits the maximum number of jobs allowable in a Samba printer queue at any given moment. - If this number is exceeded, smbd(8) will remote "Out of Space" to the client. - See all total + If this number is exceeded, smbd(8) will remote "Out of Space" to the client. + See all total print jobs.

    Default: max print jobs = 1000

    Example: max print jobs = 5000

    max protocol (G)

    The value of the parameter (a string) is the highest protocol level that will be supported by the server.

    Possible values are :

    • CORE: Earliest version. No @@ -1697,7 +1757,7 @@ df $1 | tail -1 | awk '{print $2" "$4}' A value of zero means there is no limit on the number of print jobs reported. - See all total + See all total print jobs and max print jobs parameters.

      Default: max reported print jobs = 0

      Example: max reported print jobs = 1000

    max smbd processes (G)

    This parameter limits the maximum number of smbd(8) processes concurrently running on a system and is intended @@ -1779,16 +1839,15 @@ df $1 | tail -1 | awk '{print $2" "$4}' Dfs links are specified in the share directory by symbolic links of the form msdfs:serverA\\shareA,serverB\\shareB and so on. For more information on setting up a Dfs tree - on Samba, refer to "Hosting a Microsoft - Distributed File System tree on Samba" document.

    See also host msdfs

    Default: msdfs root = no

    name cache timeout (G)

    Specifies the number of seconds it takes before + on Samba, refer to ???.

    See also host msdfs

    Default: msdfs root = no

    name cache timeout (G)

    Specifies the number of seconds it takes before entries in samba's hostname resolve cache time out. If the timeout is set to 0. the caching is disabled.

    Default: name cache timeout = 660

    Example: name cache timeout = 0

    name resolve order (G)

    This option is used by the programs in the Samba suite to determine what naming services to use and in what order to resolve host names to IP addresses. Its main purpose to is to control how netbios name resolution is performed. The option takes a space - separated string of name resolution options.

    The options are: "lmhosts", "host", - "wins" and "bcast". They cause names to be + separated string of name resolution options.

    The options are: "lmhosts", "host", + "wins" and "bcast". They cause names to be resolved as follows:

    • lmhosts : Lookup an IP address in the Samba lmhosts file. If the line in lmhosts has no name type attached to the NetBIOS name (see the lmhosts(5) for details) then @@ -1811,7 +1870,7 @@ df $1 | tail -1 | awk '{print $2" "$4}' first, followed by a broadcast attempt, followed by a normal system hostname lookup.

      When Samba is functioning in ADS security mode (security = ads) it is advised to use following settings for name resolve order:

      name resolve order = wins bcast

      DC lookups will still be done via DNS, but fallbacks to netbios names will - not inundate your DNS servers with needless querys for DOMAIN<0x1c> lookups.

    netbios aliases (G)

    This is a list of NetBIOS names that nmbd(8) will + not inundate your DNS servers with needless querys for DOMAIN<0x1c> lookups.

    netbios aliases (G)

    This is a list of NetBIOS names that nmbd will advertise as additional names by which the Samba server is known. This allows one machine to appear in browse lists under multiple names. If a machine is acting as a browse server or logon server none of these names will be advertised as either browse server or logon @@ -1842,16 +1901,7 @@ df $1 | tail -1 | awk '{print $2" "$4}' homedir map and return the server listed there.

    Note that for this option to work there must be a working NIS system and the Samba server with this option must also - be a logon server.

    Default: nis homedir = no

    non unix account range (G)

    The non unix account range parameter specifies - the range of 'user ids' that are allocated by the various 'non unix - account' passdb backends. These backends allow - the storage of passwords for users who don't exist in /etc/passwd. - This is most often used for machine account creation. - This range of ids should have no existing local or NIS users within - it as strange conflicts can occur otherwise.

    Note

    These userids never appear on the system and Samba will never - 'become' these users. They are used only to ensure that the algorithmic - RID mapping does not conflict with normal users. -

    Default: non unix account range = <empty string>

    Example: non unix account range = 10000-20000

    nt acl support (S)

    This boolean parameter controls whether smbd(8) will attempt to map + be a logon server.

    Default: nis homedir = no

    nt acl support (S)

    This boolean parameter controls whether smbd(8) will attempt to map UNIX permissions into Windows NT access control lists. This parameter was formally a global parameter in releases prior to 2.2.2.

    Default: nt acl support = yes

    ntlm auth (G)

    This parameter determines whether or not smbd(8) will attempt to @@ -1926,9 +1976,8 @@ df $1 | tail -1 | awk '{print $2" "$4}' names to OS/2 printer driver names. The format is:

    <nt driver name> = <os2 driver name>.<device name>

    For example, a valid entry using the HP LaserJet 5 printer driver would appear as HP LaserJet 5L = LASERJET.HP LaserJet 5L.

    The need for the file is due to the printer driver namespace - problem described in the Samba - Printing HOWTO. For more details on OS/2 clients, please - refer to the OS2-Client-HOWTO containing in the Samba documentation.

    Default: os2 driver map = <empty string>

    os level (G)

    This integer value controls what level Samba + problem described in ???. For more details on OS/2 clients, please + refer to ???.

    Default: os2 driver map = <empty string>

    os level (G)

    This integer value controls what level Samba advertises itself as for browse elections. The value of this parameter determines whether nmbd(8) has a chance of becoming a local master browser for the @@ -1947,7 +1996,7 @@ df $1 | tail -1 | awk '{print $2" "$4}' passwd chat parameter for most setups.

    Default: pam password change = no

    panic action (G)

    This is a Samba developer option that allows a system command to be called when either smbd(8) or smbd(8) crashes. This is usually used to - draw attention to the fact that a problem occurred.

    Default: panic action = <empty string>

    Example: panic action = "/bin/sleep 90000"

    paranoid server security (G)

    Some version of NT 4.x allow non-guest + draw attention to the fact that a problem occurred.

    Default: panic action = <empty string>

    Example: panic action = "/bin/sleep 90000"

    paranoid server security (G)

    Some version of NT 4.x allow non-guest users with a bad passowrd. When this option is enabled, samba will not use a broken NT 4.x server as password server, but instead complain to the logs and exit. @@ -1978,12 +2027,8 @@ df $1 | tail -1 | awk '{print $2" "$4}' The MySQL based passdb backend. Takes an identifier as argument. Read the Samba HOWTO Collection for configuration details. -

  • guest - - Very simple backend that only provides one user: the guest user. - Only maps the NT guest user to the guest account. - Required in pretty much all situations.

    • -

    Default: passdb backend = smbpasswd

    Example: passdb backend = tdbsam:/etc/samba/private/passdb.tdb smbpasswd:/etc/samba/smbpasswd guest

    Example: passdb backend = ldapsam:ldaps://ldap.example.com guest

    Example: passdb backend = mysql:my_plugin_args tdbsam:/etc/samba/private/passdb.tdb guest

    passwd chat (G)

    This string controls the "chat" +

    Default: passdb backend = smbpasswd

    Example: passdb backend = tdbsam:/etc/samba/private/passdb.tdb smbpasswd:/etc/samba/smbpasswd

    Example: passdb backend = ldapsam:ldaps://ldap.example.com

    Example: passdb backend = mysql:my_plugin_args tdbsam

    passwd chat (G)

    This string controls the "chat" conversation that takes places between smbd(8) and the local password changing program to change the user's password. The string describes a sequence of response-receive pairs that smbd(8) uses to determine what to send to the @@ -2005,7 +2050,7 @@ df $1 | tail -1 | awk '{print $2" "$4}' give line-feed, carriage-return, tab and space. The chat sequence string can also contain a '*' which matches any sequence of characters. Double quotes can be used to collect strings with spaces in them into a single string.

    If the send string in any part of the chat sequence is a full - stop ".", then no string is sent. Similarly, if the + stop ".", then no string is sent. Similarly, if the expect string is a full stop then no string is expected.

    If the pam password change parameter is set to yes, the chat pairs may be matched in any order, and success is determined by the PAM result, @@ -2015,9 +2060,9 @@ df $1 | tail -1 | awk '{print $2" "$4}' passwd program , passwd chat debug and pam password change.

    Default: passwd chat = *new*password* %n\\n - *new*password* %n\\n *changed*

    Example: passwd chat = "*Enter OLD password*" %o\\n - "*Enter NEW password*" %n\\n "*Reenter NEW password*" %n\\n - "*Password changed*"

    passwd chat debug (G)

    This boolean specifies if the passwd chat script + *new*password* %n\\n *changed*

    Example: passwd chat = "*Enter OLD password*" %o\\n + "*Enter NEW password*" %n\\n "*Reenter NEW password*" %n\\n + "*Password changed*"

    passwd chat debug (G)

    This boolean specifies if the passwd chat script parameter is run in debug mode. In this mode the strings passed to and received from the passwd chat are printed in the smbd(8) log with a @@ -2041,8 +2086,8 @@ df $1 | tail -1 | awk '{print $2" "$4}' it.

    Note that if the unix password sync parameter is set to yes then this program is called AS ROOT - before the SMB password in the smbpasswd(5) - file is changed. If this UNIX password change fails, then + before the SMB password in the smbpasswd + file is changed. If this UNIX password change fails, then smbd will fail to change the SMB password also (this is by design).

    If the unix password sync parameter is set this parameter MUST USE ABSOLUTE PATHS @@ -2057,10 +2102,10 @@ df $1 | tail -1 | awk '{print $2" "$4}' family of operating systems. These clients upper case clear text passwords even when NT LM 0.12 selected by the protocol negotiation request/response.

    This parameter defines the maximum number of characters - that may be upper case in passwords.

    For example, say the password given was "FRED". If + that may be upper case in passwords.

    For example, say the password given was "FRED". If password level is set to 1, the following combinations - would be tried if "FRED" failed:

    "Fred", "fred", "fRed", "frEd","freD"

    If password level was set to 2, - the following combinations would also be tried:

    "FRed", "FrEd", "FreD", "fREd", "fReD", "frED", ..

    And so on.

    The higher value this parameter is set to the more likely + would be tried if "FRED" failed:

    "Fred", "fred", "fRed", "frEd","freD"

    If password level was set to 2, + the following combinations would also be tried:

    "FRed", "FrEd", "FreD", "fREd", "fReD", "frED", ..

    And so on.

    The higher value this parameter is set to the more likely it is that a mixed case password will be matched against a single case password. However, you should be aware that use of this parameter reduces security and increases the time taken to @@ -2080,7 +2125,7 @@ df $1 | tail -1 | awk '{print $2" "$4}' parameter name resolve order and so may resolved by any method and order described in that parameter.

    The password server must be a machine capable of using - the "LM1.2X002" or the "NT LM 0.12" protocol, and it must be in + the "LM1.2X002" or the "NT LM 0.12" protocol, and it must be in user level security mode.

    Note

    Using a password server means your UNIX box (running Samba) is only as secure as your password server. DO NOT CHOOSE A PASSWORD SERVER THAT YOU DON'T COMPLETELY TRUST. @@ -2145,11 +2190,11 @@ df $1 | tail -1 | awk '{print $2" "$4}' whenever the service is disconnected. It takes the usual substitutions. The command may be run as the root on some systems.

    An interesting example may be to unmount server - resources:

    postexec = /etc/umount /cdrom

    See also preexec.

    Default: none (no command executed)

    Example: postexec = echo \"%u disconnected from %S from %m (%I)\" >> /tmp/log

    preexec (S)

    This option specifies a command to be run whenever + resources:

    postexec = /etc/umount /cdrom

    See also preexec.

    Default: none (no command executed)

    Example: postexec = echo \"%u disconnected from %S from %m (%I)\" >> /tmp/log

    preexec (S)

    This option specifies a command to be run whenever the service is connected to. It takes the usual substitutions.

    An interesting example is to send the users a welcome message every time they log in. Maybe a message of the day? Here - is an example:

    preexec = csh -c 'echo \"Welcome to %S!\" | /usr/local/samba/bin/smbclient -M %m -I %I' &

    Of course, this could get annoying after a while :-)

    See also preexec close and postexec - .

    Default: none (no command executed)

    Example: preexec = echo \"%u connected to %S from %m (%I)\" >> /tmp/log

    preexec close (S)

    This boolean option controls whether a non-zero + is an example:

    preexec = csh -c 'echo \"Welcome to %S!\" | /usr/local/samba/bin/smbclient -M %m -I %I' &

    Of course, this could get annoying after a while :-)

    See also preexec close and postexec + .

    Default: none (no command executed)

    Example: preexec = echo \"%u connected to %S from %m (%I)\" >> /tmp/log

    preexec close (S)

    This boolean option controls whether a non-zero return code from preexec should close the service being connected to.

    Default: preexec close = no

    prefered master (G)

    Synonym for preferred master for people who cannot spell :-).

    preferred master (G)

    This boolean parameter controls if @@ -2171,8 +2216,7 @@ df $1 | tail -1 | awk '{print $2" "$4}' printcap file loaded then the load printers option is easier.

    Default: no preloaded services

    Example: preload = fred lp colorlp

    preload modules (G)

    This is a list of paths to modules that should be loaded into smbd before a client connects. This improves - the speed of smbd when reacting to new connections somewhat.

    It is recommended to only use this option on heavy-performance - servers.

    Default: preload modules =

    Example: preload modules = /usr/lib/samba/passdb/mysql.so+++

    preserve case (S)

    This controls if new filenames are created + the speed of smbd when reacting to new connections somewhat.

    Default: preload modules =

    Example: preload modules = /usr/lib/samba/passdb/mysql.so+++

    preserve case (S)

    This controls if new filenames are created with the case that the client passes, or if they are forced to be the default case .

    Default: preserve case = yes

    See the section on NAME MANGLING for a fuller discussion.

    printable (S)

    If this parameter is yes, then @@ -2189,7 +2233,7 @@ df $1 | tail -1 | awk '{print $2" "$4}' . This should be supplemented by an addtional setting printing = cups in the [global] section. printcap name = cups will use the - "dummy" printcap created by CUPS, as specified in your CUPS + "dummy" printcap created by CUPS, as specified in your CUPS configuration file.

    On System V systems that use lpstat to list available printers you can use printcap name = lpstat @@ -2272,7 +2316,30 @@ print5|My Printer 5 printable.

    private dir (G)

    This parameters defines the directory smbd will use for storing such files as smbpasswd and secrets.tdb. -

    Default :private dir = ${prefix}/private

    protocol (G)

    Synonym for +

    Default :private dir = ${prefix}/private

    profile acls (S)

    This boolean parameter controls whether smbd(8) + This boolean parameter was added to fix the problems that people have been + having with storing user profiles on Samba shares from Windows 2000 or + Windows XP clients. New versions of Windows 2000 or Windows XP service + packs do security ACL checking on the owner and ability to write of the + profile directory stored on a local workstation when copied from a Samba + share. +

    When not in domain mode with winbindd then the security info copied + onto the local workstation has no meaning to the logged in user (SID) on + that workstation so the profile storing fails. Adding this parameter + onto a share used for profile storage changes two things about the + returned Windows ACL. Firstly it changes the owner and group owner + of all reported files and directories to be BUILTIN\\Administrators, + BUILTIN\\Users respectively (SIDs S-1-5-32-544, S-1-5-32-545). Secondly + it adds an ACE entry of "Full Control" to the SID BUILTIN\\Users to + every returned ACL. This will allow any Windows 2000 or XP workstation + user to access the profile.

    Note that if you have multiple users logging + on to a workstation then in order to prevent them from being able to access + each others profiles you must remove the "Bypass traverse checking" advanced + user right. This will prevent access to other users profile directories as + the top level profile directory (named after the user) is created by the + workstation profile code and has an ACL restricting entry to the directory + tree to the owning user. +

    Default: profile acls = no

    protocol (G)

    Synonym for max protocol.

    public (S)

    Synonym for guest ok.

    queuepause command (S)

    This parameter specifies the command to be executed on the server host in order to pause the printer queue.

    This command should be a program or script which takes @@ -2297,8 +2364,8 @@ print5|My Printer 5 path in the command as the PATH may not be available to the server.

    Default: depends on the setting of printing

    Example: queuepause command = enable %p

    read bmpx (G)

    This boolean parameter controls whether - smbd(8) will support the "Read - Block Multiplex" SMB. This is now rarely used and defaults to + smbd(8) will support the "Read + Block Multiplex" SMB. This is now rarely used and defaults to no. You should never need to set this parameter.

    Default: read bmpx = no

    read list (S)

    This is a list of users that are given read-only access to a service. If the connecting user is in this list then @@ -2349,8 +2416,7 @@ print5|My Printer 5 the workgroup parameter is used instead.

    The IP addresses you choose would normally be the broadcast addresses of the remote networks, but can also be the IP addresses - of known browse masters if your network config is that stable.

    See the documentation file BROWSING - in the docs/ directory.

    Default: remote announce = <empty string>

    remote browse sync (G)

    This option allows you to setup nmbd(8) to periodically request + of known browse masters if your network config is that stable.

    See ???.

    Default: remote announce = <empty string>

    remote browse sync (G)

    This option allows you to setup nmbd(8) to periodically request synchronization of browse lists with the master browser of a Samba server that is on a remote segment. This option will allow you to gain browse lists for multiple workgroups across routed networks. This @@ -2384,20 +2450,20 @@ print5|My Printer 5 by setting guest ok = yes on any share.

    Default: restrict anonymous = 0

    root (G)

    Synonym for - root directory". + root directory".

    root dir (G)

    Synonym for - root directory". + root directory".

    root directory (G)

    The server will chroot() (i.e. Change its root directory) to this directory on startup. This is not strictly necessary for secure operation. Even without it the server will deny access to files not in one of the service entries. It may also check for, and deny access to, soft links to other - parts of the filesystem, or attempts to use ".." in file names + parts of the filesystem, or attempts to use ".." in file names to access other directories (depending on the setting of the wide links parameter).

    Adding a root directory entry other - than "/" adds an extra level of security, but at a price. It + than "/" adds an extra level of security, but at a price. It absolutely ensures that no access is given to files not in the sub-tree specified in the root directory option, including some files needed for @@ -2421,7 +2487,7 @@ print5|My Printer 5 preexec and preexec close.

    Default: root preexec close = no

    security (G)

    This option affects how clients respond to Samba and is one of the most important settings in the - smb.conf file.

    The option sets the "security mode bit" in replies to + smb.conf file.

    The option sets the "security mode bit" in replies to protocol negotiations with smbd(8) to turn share level security on or off. Clients decide based on this bit whether (and how) to transfer user and password information to the server.

    The default is security = user, as this is @@ -2432,8 +2498,8 @@ print5|My Printer 5 security = share mainly because that was the only option at one stage.

    There is a bug in WfWg that has relevance to this setting. When in user or server level security a WfWg client - will totally ignore the password you type in the "connect - drive" dialog box. This makes it very difficult (if not impossible) + will totally ignore the password you type in the "connect + drive" dialog box. This makes it very difficult (if not impossible) to connect to a Samba service as anyone except the user that you are logged into WfWg as.

    If your PCs use usernames that are the same as their usernames on the UNIX machine then you will want to use @@ -2487,7 +2553,7 @@ print5|My Printer 5 in share-level security as to which UNIX username will eventually be used in granting access.

    See also the section NOTE ABOUT USERNAME/PASSWORD VALIDATION.

    SECURITY = USER

    This is the default security setting in Samba 3.0. - With user-level security a client must first "log-on" with a + With user-level security a client must first "log-on" with a valid username and password (which can be mapped using the username map parameter). Encrypted passwords (see the @@ -2536,7 +2602,7 @@ print5|My Printer 5 does not support them. However note that if encrypted passwords have been negotiated then Samba cannot revert back to checking the UNIX password file, it must have a valid smbpasswd file to check - users against. See the chapter about the User Database in the Samba HOWTO Collection for details on how to set this up.

    Note this mode of operation has + users against. See the chapter about the User Database in the Samba HOWTO Collection for details on how to set this up.

    Note

    This mode of operation has significant pitfalls, due to the fact that is activly initiates a man-in-the-middle attack on the remote SMB server. In particular, this mode of operation can cause significant resource consuption on @@ -2544,11 +2610,11 @@ print5|My Printer 5 of the user's session. Furthermore, if this connection is lost, there is no way to reestablish it, and futher authenticaions to the Samba server may fail. (From a single client, till it disconnects). -

    Note that from the client's point of +

    Note

    From the client's point of view security = server is the same as security = user. It only affects how the server deals with the authentication, it does - not in any way affect what the client sees.

    Note that the name of the resource being + not in any way affect what the client sees.

    Note that the name of the resource being requested is not sent to the server until after the server has successfully authenticated the client. This is why guest shares don't work in user level security without allowing @@ -2558,6 +2624,13 @@ print5|My Printer 5 parameter for details on doing this.

    See also the section NOTE ABOUT USERNAME/PASSWORD VALIDATION.

    See also the password server parameter and the + encrypted passwords parameter.

    SECURITY = ADS

    In this mode, Samba will act as a domain member in an ADS realm. To operate + in this mode, the machine running Samba will need to have Kerberos installed + and configured and Samba will need to be joined to the ADS realm using the + net utility.

    Note that this mode does NOT make Samba operate as a Active Directory Domain + Controller.

    Read the chapter about Domain Membership in the HOWTO for details.

    See also the ads server + parameter, the realm + paramter and the encrypted passwords parameter.

    Default: security = USER

    Example: security = DOMAIN

    security mask (S)

    This parameter controls what UNIX permission bits can be modified when a Windows NT client is manipulating the UNIX permission on a file using the native NT security @@ -2570,7 +2643,7 @@ print5|My Printer 5

    Note that users who can access the Samba server through other means can easily bypass this restriction, so it is primarily useful for standalone - "appliance" systems. Administrators of most normal systems will + "appliance" systems. Administrators of most normal systems will probably want to leave it set to 0777.

    See also the force directory security mode, directory @@ -2586,7 +2659,13 @@ print5|My Printer 5 for Windows NT4 before SP4.

    Please note that with this set to no you will have to apply the WindowsXP requireSignOrSeal-Registry patch found in - the docs/Registry subdirectory.

    Default: server schannel = auto

    Example: server schannel = yes

    server string (G)

    This controls what string will show up in the printer comment box in print + the docs/Registry subdirectory.

    Default: server schannel = auto

    Example: server schannel = yes

    server signing (G)

    This controls whether the server offers or requires + the client it talks to to use SMB signing. Possible values + are auto, mandatory + and disabled. +

    When set to auto, SMB signing is offered, but not enforced. + When set to mandatory, SMB signing is required and if set + to disabled, SMB signing is not offered either.

    Default: client signing = False

    server string (G)

    This controls what string will show up in the printer comment box in print manager and next to the IPC connection in net view. It can be any string that you wish to show to your users.

    It also sets what will appear in browse lists next to the machine name.

    A %v will be replaced with the Samba @@ -2604,7 +2683,13 @@ print5|My Printer 5 vampire. %u will be replaced with the user whose primary group is to be set. %g will be replaced with the group to - set.

    Default: No default value

    Example: set primary group script = /usr/sbin/usermod -g '%g' '%u'

    share modes (S)

    This enables or disables the honoring of + set.

    Default: No default value

    Example: set primary group script = /usr/sbin/usermod -g '%g' '%u'

    set quota command (G)

    The set quota command should only be used + whenever there is no operating system API available from the OS that + samba can use.

    This parameter should specify the path to a script that + can set quota for the specified arguments.

    The specified script should take the following arguments:

    • 1 - quota type +

      • 1 - user quotas

      • 2 - user default quotas (uid = -1)

      • 3 - group quotas

      • 4 - group default quotas (gid = -1)

      +

    • 2 - id (uid for user, gid for group, -1 if N/A)

    • 3 - quota state (0 = disable, 1 = enable, 2 = enable and enforce)

    • 4 - block softlimit

    • 5 - block hardlimit

    • 6 - inode softlimit

    • 7 - inode hardlimit

    • 8(optional) - block size, defaults to 1024

    The script should output at least one line of data.

    See also the get quota command parameter. +

    Default: set quota command =

    Example: set quota command = /usr/local/sbin/set_quota

    share modes (S)

    This enables or disables the honoring of the share modes during a file open. These modes are used by clients to gain exclusive read or write access to a file.

    These open modes are not directly supported by UNIX, so @@ -2622,7 +2707,7 @@ print5|My Printer 5 . This option can be use with preserve case = yes to permit long filenames to retain their case, while short names are lowered.

    See the section on NAME MANGLING.

    Default: short preserve case = yes

    show add printer wizard (G)

    With the introduction of MS-RPC based printing support - for Windows NT/2000 client in Samba 2.2, a "Printers..." folder will + for Windows NT/2000 client in Samba 2.2, a "Printers..." folder will appear on Samba hosts in the share listing. Normally this folder will contain an icon for the MS Add Printer Wizard (APW). However, it is possible to disable this feature regardless of the level of privilege @@ -2648,13 +2733,13 @@ print5|My Printer 5 switch -r. It means reboot after shutdown for NT.

  • %f will be substituted with the switch -f. It means force the shutdown - even if applications do not respond for NT.

    • Default: None.

    Example: abort shutdown script = /usr/local/samba/sbin/shutdown %m %t %r %f

    Shutdown script example: + even if applications do not respond for NT.

    Default: None.

    Example: shutdown script = /usr/local/samba/sbin/shutdown %m %t %r %f

    Shutdown script example: 

     #!/bin/bash
 		
 $time=0
-let "time/60"
-let "time++"
+let "time/60"
+let "time++"
 
 /sbin/shutdown $3 $4 +$time $1 &

    @@ -2675,7 +2760,7 @@ Shutdown does not return so we need to launch it in background. suggest you read the appropriate documentation for your operating system first (perhaps man setsockopt will help).

    You may find that on some systems Samba will say - "Unknown socket option" when you supply an option. This means you + "Unknown socket option" when you supply an option. This means you either incorrectly typed it or you need to add an include file to includes.h for your OS. If the latter is the case please send the patch to @@ -2690,15 +2775,13 @@ Shutdown does not return so we need to launch it in background. might be:

    socket options = IPTOS_LOWDELAY

    If you have a local network then you could try:

    socket options = IPTOS_LOWDELAY TCP_NODELAY

    If you are on a wide area network then perhaps try setting IPTOS_THROUGHPUT.

    Note that several of the options may cause your Samba server to fail completely. Use these options with caution!

    Default: socket options = TCP_NODELAY

    Example: socket options = IPTOS_LOWDELAY

    source environment (G)

    This parameter causes Samba to set environment - variables as per the content of the file named.

    If the value of this parameter starts with a "|" character + variables as per the content of the file named.

    If the value of this parameter starts with a "|" character then Samba will treat that value as a pipe command to open and will set the environment variables from the output of the pipe.

    The contents of the file or the output of the pipe should be formatted as the output of the standard Unix env(1) command. This is of the form:

    Example environment entry:

    SAMBA_NETBIOS_NAME = myhostname

    Default: No default value

    Examples: source environment = |/etc/smb.conf.sh

    Example: source environment = /usr/local/smb_env_vars

    stat cache (G)

    This parameter determines if smbd(8) will use a cache in order to speed up case insensitive name mappings. You should never need - to change this parameter.

    Default: stat cache = yes

    stat cache size (G)

    This parameter determines the number of - entries in the stat cache. You should - never need to change this parameter.

    Default: stat cache size = 50

    strict allocate (S)

    This is a boolean that controls the handling of + to change this parameter.

    Default: stat cache = yes

    strict allocate (S)

    This is a boolean that controls the handling of disk space allocation in the server. When this is set to yes the server will change from UNIX behaviour of not committing real disk storage blocks when a file is extended to the Windows behaviour @@ -2755,23 +2838,17 @@ Shutdown does not return so we need to launch it in background. string %D is present it is substituted with the user's Windows NT domain name. If the string %U is present it - is substituted with the user's Windows NT user name.

    Default: template homedir = /home/%D/%U

    template shell (G)

    When filling out the user information for a Windows NT + is substituted with the user's Windows NT user name.

    Default: template homedir = /home/%D/%U

    template primary group (G)

    This option defines the default primary group for + each user created by winbindd(8)'s local account management + functions (similar to the 'add user script'). +

    Default: template primary group = nobody

    template shell (G)

    When filling out the user information for a Windows NT user, the winbindd(8) daemon uses this parameter to fill in the login shell for that user.

    Default: template shell = /bin/false

    time offset (G)

    This parameter is a setting in minutes to add to the normal GMT to local time conversion. This is useful if you are serving a lot of PCs that have incorrect daylight saving time handling.

    Default: time offset = 0

    Example: time offset = 60

    time server (G)

    This parameter determines if nmbd(8) advertises itself as a time server to Windows clients.

    Default: time server = no

    timestamp logs (G)

    Synonym for - debug timestamp.

    total print jobs (G)

    This parameter accepts an integer value which defines - a limit on the maximum number of print jobs that will be accepted - system wide at any given time. If a print job is submitted - by a client which will exceed this number, then smbd(8) will return an - error indicating that no space is available on the server. The - default value of 0 means that no such limit exists. This parameter - can be used to prevent a server from exceeding its capacity and is - designed as a printing throttle. See also - max print jobs. -

    Default: total print jobs = 0

    Example: total print jobs = 5000

    unicode (G)

    Specifies whether Samba should try + debug timestamp.

    unicode (G)

    Specifies whether Samba should try to use unicode on the wire by default. Note: This does NOT mean that samba will assume that the unix machine uses unicode!

    Default: unicode = yes

    unix charset (G)

    Specifies the charset the unix machine @@ -2782,7 +2859,7 @@ Shutdown does not return so we need to launch it in background. These extensions enable Samba to better serve UNIX CIFS clients by supporting features such as symbolic links, hard links, etc... These extensions require a similarly enabled client, and are of - no current use to Windows clients.

    Default: unix extensions = no

    unix password sync (G)

    This boolean parameter controls whether Samba + no current use to Windows clients.

    Default: unix extensions = yes

    unix password sync (G)

    This boolean parameter controls whether Samba attempts to synchronize the UNIX password with the SMB password when the encrypted SMB password in the smbpasswd file is changed. If this is set to yes the program specified in the passwd @@ -2826,7 +2903,7 @@ Shutdown does not return so we need to launch it in background. logged on user. If the user possesses local administator rights but not root privilegde on the Samba host (often the case), the OpenPrinterEx() call will fail. The result is that the client will - now display an "Access Denied; Unable to connect" message + now display an "Access Denied; Unable to connect" message in the printer queue window (even though jobs may successfully be printed).

    If this parameter is enabled for a printer, then any attempt to open the printer with the PRINTER_ACCESS_ADMINISTER right is mapped @@ -2910,8 +2987,8 @@ Shutdown does not return so we need to launch it in background. to the UNIX name sys you would use:

    sys = @system

    You can have as many mappings as you like in a username map file.

    If your system supports the NIS NETGROUP option then the netgroup database is checked before the /etc/group database for matching groups.

    You can map Windows usernames that have spaces in them - by using double quotes around the name. For example:

    tridge = "Andrew Tridgell"

    would map the windows username "Andrew Tridgell" to the - unix username "tridge".

    The following example would map mary and fred to the + by using double quotes around the name. For example:

    tridge = "Andrew Tridgell"

    would map the windows username "Andrew Tridgell" to the + unix username "tridge".

    The following example would map mary and fred to the unix user sys, and map the rest to guest. Note the use of the '!' to tell Samba to stop processing if it gets a match on that line.

    @@ -3032,7 +3109,13 @@ veto files = /.AppleDouble/.bin/.AppleDesktop/Network Trash Folder/
 	that Samba has to  do in order to perform the link checks.
    Default: wide links = yes
    winbind cache time (G)

    This parameter specifies the number of seconds the winbindd(8) daemon will cache user and group information before querying a Windows NT server - again.

    Default: winbind cache type = 15

    winbind enum groups (G)

    On large installations using winbindd(8) it may be necessary to suppress + again.

    Default: winbind cache type = 300

    winbind enable local accounts (G)

    This parameter controls whether or not winbindd + will act as a stand in replacement for the various account + management hooks in smb.conf (e.g. 'add user script'). + If enabled, winbindd will support the creation of local + users and groups as another source of UNIX account information + available via getpwnam() or getgrgid(), etc... +

    Default: winbind enable local accounts = yes

    winbind enum groups (G)

    On large installations using winbindd(8) it may be necessary to suppress the enumeration of groups through the setgrent(), getgrent() and endgrent() group of system calls. If @@ -3060,10 +3143,16 @@ veto files = /.AppleDouble/.bin/.AppleDesktop/Network Trash Folder/ and nss_winbind.so modules for UNIX services.

    Please note that setting this parameter to + causes problems with group membership at least on glibc systems, as the character + - is used as a special character for NIS in /etc/group.

    Default: winbind separator = '\'

    Example: winbind separator = +

    winbind uid (G)

    This parameter is now an alias for idmap uid

    The winbind gid parameter specifies the range of user ids that are allocated by the + is used as a special character for NIS in /etc/group.

    Default: winbind separator = '\'

    Example: winbind separator = +

    winbind trusted domains only (G)

    This parameter is designed to allow Samba servers that + are members of a Samba controlled domain to use UNIX accounts + distributed vi NIS, rsync, or LDAP as the uid's for winbindd users + in the hosts primary domain. Therefore, the user 'SAMBA\user1' would + be mapped to the account 'user1' in /etc/passwd instead of allocating + a new uid for him or her. +

    Default: winbind trusted domains only = <no>

    winbind uid (G)

    This parameter is now an alias for idmap uid

    The winbind gid parameter specifies the range of user ids that are allocated by the winbindd(8) daemon. This range of ids should have no existing local or NIS users within it as strange - conflicts can occur otherwise.

    Default: winbind uid = <empty string>

    Example: winbind uid = 10000-20000

    winbind used default domain (G)

    This parameter specifies whether the + conflicts can occur otherwise.

    Default: winbind uid = <empty string>

    Example: winbind uid = 10000-20000

    winbind use default domain (G)

    This parameter specifies whether the winbindd(8) daemon should operate on users without domain component in their username. Users without a domain component are treated as is part of the winbindd server's own @@ -3075,11 +3164,11 @@ veto files = /.AppleDouble/.bin/.AppleDesktop/Network Trash Folder/ dynamic update of external name resolution databases such as dynamic DNS.

    The wins hook parameter specifies the name of a script or executable that will be called as follows:

    wins_hook operation name nametype ttl IP_list

    • The first argument is the operation and is - one of "add", "delete", or - "refresh". In most cases the operation + one of "add", "delete", or + "refresh". In most cases the operation can be ignored as the rest of the parameters provide sufficient information. Note that - "refresh" may sometimes be called when + "refresh" may sometimes be called when the name has not previously been added, in that case it should be treated as an add.

    • The second argument is the NetBIOS name. If the name is not a legal name then the wins hook is not called. @@ -3090,7 +3179,7 @@ veto files = /.AppleDouble/.bin/.AppleDesktop/Network Trash Folder/ addresses currently registered for that name. If this list is empty then the name should be deleted.

    An example script that calls the BIND dynamic DNS update program nsupdate is provided in the examples - directory of the Samba source code.

    wins partner (G)

    A space separated list of partners' IP addresses for + directory of the Samba source code.

    wins partners (G)

    A space separated list of partners' IP addresses for WINS replication. WINS partners are always defined as push/pull partners as defining only one way WINS replication is unreliable. WINS replication is currently experimental and unreliable between @@ -3106,7 +3195,7 @@ veto files = /.AppleDouble/.bin/.AppleDesktop/Network Trash Folder/ seperated from the ip address by a colon.

    Note

    You need to set up Samba to point to a WINS server if you have multiple subnets and wish cross-subnet - browsing to work correctly.

    See the documentation file Browsing in the samba howto collection.

    Default: not enabled

    Example: wins server = mary:192.9.200.1 fred:192.168.3.199 mary:192.168.2.61

    For this example when querying a certain name, 192.19.200.1 will + browsing to work correctly.

    See the ???.

    Default: not enabled

    Example: wins server = mary:192.9.200.1 fred:192.168.3.199 mary:192.168.2.61

    For this example when querying a certain name, 192.19.200.1 will be asked first and if that doesn't respond 192.168.2.61. If either of those doesn't know the name 192.168.3.199 will be queried.

    Example: wins server = 192.9.200.1 192.168.2.61

    wins support (G)

    This boolean controls if the nmbd(8) process in Samba will act as a WINS server. You should diff --git a/docs/htmldocs/smbcacls.1.html b/docs/htmldocs/smbcacls.1.html index d7c5fed1b5..1c3cc5a2d3 100644 --- a/docs/htmldocs/smbcacls.1.html +++ b/docs/htmldocs/smbcacls.1.html @@ -10,10 +10,10 @@ only the ones specified on the command line. All other ACLs are erased. Note that the ACL specified must contain at least a revision, type, owner and group for the call to succeed.

    -U username

    Specifies a username used to connect to the - specified service. The username may be of the form "username" in + specified service. The username may be of the form "username" in which case the user is prompted to enter in a password and the workgroup specified in the smb.conf(5) file is - used, or "username%password" or "DOMAIN\username%password" and the + used, or "username%password" or "DOMAIN\username%password" and the password and workgroup names are used as provided.

    -C name

    The owner of a file or directory can be changed to the name given using the -C option. The name can be a sid in the form S-1-x-y-z or a name resolved @@ -34,8 +34,7 @@ configuration details required by the server. The information in this file includes server-specific information such as what printcap file to use, as well as descriptions of all the services that the server is -to provide. See -smb.conf(5) for more information. +to provide. See smb.conf for more information. The default configuration file name is determined at compile time.

    -d|--debug=debuglevel

    debuglevel is an integer from 0 to 10. The default value if this parameter is @@ -49,10 +48,9 @@ amounts of log data, and should only be used when investigating a problem. Levels above 3 are designed for use only by developers and generate HUGE amounts of log data, most of which is extremely cryptic.

    Note that specifying this parameter here will -override the log -level parameter in the -smb.conf(5) file.

    -l|--logfile=logbasename

    File name for log/debug files. The extension -".client" will be appended. The log file is +override the log level parameter +in the smb.conf file.

    -l|--logfile=logbasename

    File name for log/debug files. The extension +".client" will be appended. The log file is never removed by the client.

    ACL FORMAT

    The format of an ACL is one or more ACL entries separated by either commas or newlines. An ACL entry is one of the following: 

     
diff --git a/docs/htmldocs/smbclient.1.html b/docs/htmldocs/smbclient.1.html
index ecb85d6e85..1ee5fd26da 100644
--- a/docs/htmldocs/smbclient.1.html
+++ b/docs/htmldocs/smbclient.1.html
@@ -84,12 +84,7 @@
 		messages. 
    -p port
    This number is the TCP port number that will be used 
 		when making connections to the server. The standard (well-known)
 		TCP port number for an SMB/CIFS server is 139, which is the 
-		default. 
    -l logfilename
    If specified, logfilename specifies a base filename 
-		into which operational data from the running client will be 
-		logged. 
    The default base name is specified at compile time.
    The base name is used to generate actual log file names.
-		For example, if the name specified was "log", the debug file 
-		would be log.client.
    The log file generated is never removed by the client. 		
-		
    -h|--help
    Print a summary of command line options.
+		default. 
    -h|--help
    Print a summary of command line options.
 
    -I IP-address
    IP address is the address of the server to connect to. 
 		It should be specified in standard "a.b.c.d" notation. 
    Normally the client would attempt to locate a named 
 		SMB/CIFS server by looking it up via the NetBIOS name resolution 
@@ -126,8 +121,7 @@ configuration details required by the server.  The
 information in this file includes server-specific
 information such as what printcap file to use, as well 
 as descriptions of all the services that the server is 
-to provide. See 
-smb.conf(5) for more information.
+to provide. See smb.conf for more information.
 The default configuration file name is determined at 
 compile time.
    -d|--debug=debuglevel
    debuglevel is an integer 
 from 0 to 10.  The default value if this parameter is 
@@ -141,9 +135,8 @@ amounts of log data, and should only be used when
 investigating a problem. Levels above 3 are designed for 
 use only by developers and generate HUGE amounts of log
 data, most of which is extremely cryptic.
    Note that specifying this parameter here will 
-override the log
-level parameter in the 
-smb.conf(5) file.
    -l|--logfile=logbasename
    File name for log/debug files. The extension
+override the log level parameter
+in the smb.conf file.
    -l|--logfile=logbasename
    File name for log/debug files. The extension
 ".client" will be appended. The log file is
 never removed by the client.
 
    -N
    If specified, this parameter suppresses the normal
@@ -177,10 +170,10 @@ via the ps command.  To be safe always allow
 rpcclient to prompt for a password and type
 it in directly. 
    -n <primary NetBIOS name>
    This option allows you to override
 the NetBIOS name that Samba uses for itself. This is identical
-to setting the NetBIOS
-name parameter in the smb.conf(5) file.  However, a command
+to setting the netbios name parameter in the smb.conf file. 
+However, a command
 line setting will take precedence over settings in
-smb.conf(5).
    -i <scope>
    This specifies a NetBIOS scope that
+smb.conf.
    -i <scope>
    This specifies a NetBIOS scope that
 nmblookup will use to communicate with when
 generating NetBIOS names. For details on the use of NetBIOS
 scopes, see rfc1001.txt and rfc1002.txt. NetBIOS scopes are
@@ -192,7 +185,7 @@ smb.conf.  If the domain specified is the same as the servers
 NetBIOS name, it causes the client to log on using the servers local 
 SAM (as opposed to the Domain SAM). 
    -O socket options
    TCP socket options to set on the client
 socket. See the socket options parameter in
-the smb.conf(5) manual page for the list of valid
+the smb.conf manual page for the list of valid
 options. 
    -T tar options
    smbclient may be used to create tar(1)
 		 compatible backups of all the files on an SMB/CIFS
 		share. The secondary tar flags that can be given to this option 
diff --git a/docs/htmldocs/smbcontrol.1.html b/docs/htmldocs/smbcontrol.1.html
index 21344b9ade..e7ccd27f26 100644
--- a/docs/htmldocs/smbcontrol.1.html
+++ b/docs/htmldocs/smbcontrol.1.html
@@ -5,8 +5,7 @@ configuration details required by the server.  The
 information in this file includes server-specific
 information such as what printcap file to use, as well 
 as descriptions of all the services that the server is 
-to provide. See 
-smb.conf(5) for more information.
+to provide. See smb.conf for more information.
 The default configuration file name is determined at 
 compile time.
    -i
    Run interactively. Individual commands 
 		of the form destination message-type parameters can be entered 
@@ -58,7 +57,9 @@ compile time.
    -i
    Run interactiv
 	talloc(pool) memory usage by the specified daemon/process. Available 
 	for both smbd and nmbd.
    drvupgrade
    Force clients of printers using specified driver 
 	to update their local version of the driver. Can only be 
-	sent to smbd.

    VERSION

    This man page is correct for version 3.0 of + sent to smbd.

    reload-config

    Force daemon to reload smb.conf configuration file. Can be sent + to smbd, nmbd, or winbindd. +

    VERSION

    This man page is correct for version 3.0 of the Samba suite.

    SEE ALSO

    nmbd(8) and smbd(8).

    AUTHOR

    The original Samba software and related utilities were created by Andrew Tridgell. Samba is now developed by the Samba Team as an Open Source project similar diff --git a/docs/htmldocs/smbcquotas.1.html b/docs/htmldocs/smbcquotas.1.html index 468edd1d61..59dcd106ed 100644 --- a/docs/htmldocs/smbcquotas.1.html +++ b/docs/htmldocs/smbcquotas.1.html @@ -14,8 +14,7 @@ configuration details required by the server. The information in this file includes server-specific information such as what printcap file to use, as well as descriptions of all the services that the server is -to provide. See -smb.conf(5) for more information. +to provide. See smb.conf for more information. The default configuration file name is determined at compile time.

    -d|--debug=debuglevel

    debuglevel is an integer from 0 to 10. The default value if this parameter is @@ -29,9 +28,8 @@ amounts of log data, and should only be used when investigating a problem. Levels above 3 are designed for use only by developers and generate HUGE amounts of log data, most of which is extremely cryptic.

    Note that specifying this parameter here will -override the log -level parameter in the -smb.conf(5) file.

    -l|--logfile=logbasename

    File name for log/debug files. The extension +override the log level parameter +in the smb.conf file.

    -l|--logfile=logbasename

    File name for log/debug files. The extension ".client" will be appended. The log file is never removed by the client.

    -N

    If specified, this parameter suppresses the normal diff --git a/docs/htmldocs/smbd.8.html b/docs/htmldocs/smbd.8.html index 5b71bd7196..291ddbc0f6 100644 --- a/docs/htmldocs/smbd.8.html +++ b/docs/htmldocs/smbd.8.html @@ -54,8 +54,7 @@ configuration details required by the server. The information in this file includes server-specific information such as what printcap file to use, as well as descriptions of all the services that the server is -to provide. See -smb.conf(5) for more information. +to provide. See smb.conf for more information. The default configuration file name is determined at compile time.

    -d|--debug=debuglevel

    debuglevel is an integer from 0 to 10. The default value if this parameter is @@ -69,9 +68,8 @@ amounts of log data, and should only be used when investigating a problem. Levels above 3 are designed for use only by developers and generate HUGE amounts of log data, most of which is extremely cryptic.

    Note that specifying this parameter here will -override the log -level parameter in the -smb.conf(5) file.

    -l|--logfile=logbasename

    File name for log/debug files. The extension +override the log level parameter +in the smb.conf file.

    -l|--logfile=logbasename

    File name for log/debug files. The extension ".client" will be appended. The log file is never removed by the client.

    -h|--help

    Print a summary of command line options. @@ -82,7 +80,8 @@ never removed by the client. file will be created for informational and debug messages from the running server. The log file generated is never removed by the server although - its size may be controlled by the max log size + its size may be controlled by the + max log size option in the smb.conf(5) file. Beware: If the directory specified does not exist, smbd will log to the default debug log location defined at compile time. @@ -104,18 +103,15 @@ never removed by the client. in the above situation.

    FILES

    /etc/inetd.conf

    If the server is to be run by the inetd meta-daemon, this file must contain suitable startup information for the - meta-daemon. See the "How to Install and Test SAMBA" - document for details. + meta-daemon.

    /etc/rc

    or whatever initialization script your system uses).

    If running the server as a daemon at startup, this file will need to contain an appropriate startup - sequence for the server. See the "How to Install and Test SAMBA" - document for details.

    /etc/services

    If running the server via the + sequence for the server.

    /etc/services

    If running the server via the meta-daemon inetd, this file must contain a mapping of service name (e.g., netbios-ssn) to service port (e.g., 139) and protocol type (e.g., tcp). - See the "How to Install and Test SAMBA" - document for details.

    /usr/local/samba/lib/smb.conf

    This is the default location of the smb.conf(5) server configuration file. Other common places that systems +

    /usr/local/samba/lib/smb.conf

    This is the default location of the smb.conf(5) server configuration file. Other common places that systems install this file are /usr/samba/lib/smb.conf and /etc/samba/smb.conf.

    This file describes all the services the server is to make available to clients. See smb.conf(5) for more information.

    LIMITATIONS

    On some systems smbd cannot change uid back @@ -131,8 +127,7 @@ never removed by the client. is not specific to the server, however.

    PAM INTERACTION

    Samba uses PAM for authentication (when presented with a plaintext password), for account checking (is this account disabled?) and for session management. The degree too which samba supports PAM is restricted - by the limitations of the SMB protocol and the obey - pam restricions smb.conf(5) paramater. When this is set, the following restrictions apply: + by the limitations of the SMB protocol and the obey pam restrictions smb.conf(5) paramater. When this is set, the following restrictions apply:

    • Account Validation: All accesses to a samba server are checked against PAM to see if the account is vaild, not disabled and is permitted to diff --git a/docs/htmldocs/smbmount.8.html b/docs/htmldocs/smbmount.8.html index 233dee51d7..64968b5de7 100644 --- a/docs/htmldocs/smbmount.8.html +++ b/docs/htmldocs/smbmount.8.html @@ -1,14 +1,14 @@ smbmount

      Name

      smbmount — mount an smbfs filesystem

      Synopsis

      smbmount {service} {mount-point} [-o options]

      DESCRIPTION

      smbmount mounts a Linux SMB filesystem. It is usually invoked as mount.smbfs by the mount(8) command when using the - "-t smbfs" option. This command only works in Linux, and the kernel must + "-t smbfs" option. This command only works in Linux, and the kernel must support the smbfs filesystem.

      Options to smbmount are specified as a comma-separated list of key=value pairs. It is possible to send options other than those listed here, assuming that smbfs supports them. If you get mount failures, check your kernel log for errors on unknown options.

      smbmount is a daemon. After mounting it keeps running until the mounted smbfs is umounted. It will log things that happen - when in daemon mode using the "machine name" smbmount, so + when in daemon mode using the "machine name" smbmount, so typically this output will end up in log.smbmount. The smbmount process may also be called mount.smbfs.

      Note

      smbmount calls smbmnt(8) to do the actual mount. You @@ -16,8 +16,8 @@ that it can be found.

      OPTIONS

      username=<arg>

      specifies the username to connect as. If this is not given, then the environment variable USER is used. This option can also take the - form "user%password" or "user/workgroup" or - "user/workgroup%password" to allow the password and workgroup + form "user%password" or "user/workgroup" or + "user/workgroup%password" to allow the password and workgroup to be specified as part of the username.

      password=<arg>

      specifies the SMB password. If this option is not given then the environment variable PASSWD is used. If it can find diff --git a/docs/htmldocs/smbpasswd.5.html b/docs/htmldocs/smbpasswd.5.html index 556b637f4f..feb899f946 100644 --- a/docs/htmldocs/smbpasswd.5.html +++ b/docs/htmldocs/smbpasswd.5.html @@ -19,8 +19,8 @@ Note that this password hash is regarded as weak as it is vulnerable to dictionary attacks and if two users choose the same password this entry will be identical (i.e. the password - is not "salted" as the UNIX password is). If the user has a - null password this field will contain the characters "NO PASSWORD" + is not "salted" as the UNIX password is). If the user has a + null password this field will contain the characters "NO PASSWORD" as the start of the hex string. If the hex string is equal to 32 'X' characters then the user's account is marked as disabled and the user will not be able to @@ -43,7 +43,7 @@ password and uses a much higher quality hashing algorithm. However, it is still the case that if two users choose the same password this entry will be identical (i.e. the password is - not "salted" as the UNIX password is).

      WARNING !!. Note that, due to + not "salted" as the UNIX password is).

      WARNING !!. Note that, due to the challenge-response nature of the SMB/CIFS authentication protocol, anyone with a knowledge of this password hash will be able to impersonate the user on the network. For this @@ -59,20 +59,21 @@ 13 characters in length (including the '[' and ']' characters). The contents of this field may be any of the following characters:

      • U - This means - this is a "User" account, i.e. an ordinary user. Only User + this is a "User" account, i.e. an ordinary user. Only User and Workstation Trust accounts are currently supported in the smbpasswd file.

      • N - This means the account has no password (the passwords in the fields LANMAN Password Hash and NT Password Hash are ignored). Note that this will only allow users to log on with no password if the - null passwords parameter is set in the smb.conf(5) config file.

      • D - This means the account + null passwords parameter is set in the + smb.conf(5) config file.

      • D - This means the account is disabled and no SMB/CIFS logins will be allowed for this user.

      • W - This means this account - is a "Workstation Trust" account. This kind of account is used + is a "Workstation Trust" account. This kind of account is used in the Samba PDC code stream to allow Windows NT Workstations and Servers to join a Domain hosted by a Samba PDC.

      Other flags may be added as the code is extended in future. The rest of this field space is filled in with spaces.

      Last Change Time

      This field consists of the time the account was last modified. It consists of the characters 'LCT-' (standing for - "Last Change Time") followed by a numeric encoding of the UNIX time + "Last Change Time") followed by a numeric encoding of the UNIX time in seconds since the epoch (1970) that the last change was made.

      All other colon separated fields are ignored at this time.

      VERSION

      This man page is correct for version 3.0 of the Samba suite.

      SEE ALSO

      smbpasswd(8), Samba(7), and diff --git a/docs/htmldocs/smbpasswd.8.html b/docs/htmldocs/smbpasswd.8.html index 7612fdd775..7c98e4b080 100644 --- a/docs/htmldocs/smbpasswd.8.html +++ b/docs/htmldocs/smbpasswd.8.html @@ -16,7 +16,7 @@ for their new password twice, to ensure that the new password was typed correctly. No passwords will be echoed on the screen whilst being typed. If you have a blank SMB password (specified by - the string "NO PASSWORD" in the smbpasswd file) then just press + the string "NO PASSWORD" in the smbpasswd file) then just press the <Enter> key when asked for your old password.

      smbpasswd can also be used by a normal user to change their SMB password on remote machines, such as Windows NT Primary Domain Controllers. See the (-r) and -U options @@ -64,10 +64,10 @@ HUGE amounts of log data, most of which is extremely cryptic.

      -n

      This option specifies that the username following should have their password set to null (i.e. a blank password) in - the local smbpasswd file. This is done by writing the string "NO - PASSWORD" as the first part of the first password stored in the + the local smbpasswd file. This is done by writing the string "NO + PASSWORD" as the first part of the first password stored in the smbpasswd file.

      Note that to allow users to logon to a Samba server once - the password has been set to "NO PASSWORD" in the smbpasswd + the password has been set to "NO PASSWORD" in the smbpasswd file the administrator must set the following parameter in the [global] section of the smb.conf file :

      null passwords = yes

      This option is only available when running smbpasswd as root.

      -r remote machine name

      This option allows a user to specify what machine @@ -89,7 +89,7 @@ a real password database so it is not possible to change passwords specifying a Win95/98 machine as remote machine target.

      -R name resolve order

      This option allows the user of smbpasswd to determine what name resolution services to use when looking up the NetBIOS - name of the host being connected to.

      The options are :"lmhosts", "host", "wins" and "bcast". They + name of the host being connected to.

      The options are :"lmhosts", "host", "wins" and "bcast". They cause names to be resolved as follows:

      • lmhosts: Lookup an IP address in the Samba lmhosts file. If the line in lmhosts has no name type attached to the NetBIOS name (see the lmhosts(5) for details) then @@ -127,8 +127,7 @@ has been configured to use the experimental --with-ldapsam option. The -w switch is used to specify the password to be used with the - ldap admin - dn. Note that the password is stored in + ldap admin dn. Note that the password is stored in the secrets.tdb and is keyed off of the admin's DN. This means that if the value of ldap admin dn ever changes, the password will need to be @@ -148,10 +147,8 @@ smbd running on the local machine by specifying either allow hosts or deny hosts entry in the smb.conf(5) file and neglecting to - allow "localhost" access to the smbd.

        In addition, the smbpasswd command is only useful if Samba - has been set up to use encrypted passwords. See the document - "LanMan and NT Password Encryption in Samba" in the docs directory for details - on how to do this.

      VERSION

      This man page is correct for version 3.0 of the Samba suite.

      SEE ALSO

      smbpasswd(5), Samba(7).

      AUTHOR

      The original Samba software and related utilities + allow "localhost" access to the smbd.

      In addition, the smbpasswd command is only useful if Samba + has been set up to use encrypted passwords.

      VERSION

      This man page is correct for version 3.0 of the Samba suite.

      SEE ALSO

      smbpasswd(5), Samba(7).

      AUTHOR

      The original Samba software and related utilities were created by Andrew Tridgell. Samba is now developed by the Samba Team as an Open Source project similar to the way the Linux kernel is developed.

      The original Samba man pages were written by Karl Auer. diff --git a/docs/htmldocs/smbsh.1.html b/docs/htmldocs/smbsh.1.html index 935576af6b..d1360d849d 100644 --- a/docs/htmldocs/smbsh.1.html +++ b/docs/htmldocs/smbsh.1.html @@ -1,4 +1,4 @@ -smbsh

      Name

      smbsh — Allows access to Windows NT filesystem +smbsh

      Name

      smbsh — Allows access to remote SMB shares using UNIX commands

      Synopsis

      smbsh [-W workgroup] [-U username] [-P prefix] [-R <name resolve order>] [-d <debug level>] [-l logfile] [-L libdir]

      DESCRIPTION

      This tool is part of the Samba(7) suite.

      smbsh allows you to access an NT filesystem using UNIX commands such as ls, egrep, and rcp. You must use a @@ -19,8 +19,7 @@ configuration details required by the server. The information in this file includes server-specific information such as what printcap file to use, as well as descriptions of all the services that the server is -to provide. See -smb.conf(5) for more information. +to provide. See smb.conf for more information. The default configuration file name is determined at compile time.

      -d|--debug=debuglevel

      debuglevel is an integer from 0 to 10. The default value if this parameter is @@ -34,12 +33,11 @@ amounts of log data, and should only be used when investigating a problem. Levels above 3 are designed for use only by developers and generate HUGE amounts of log data, most of which is extremely cryptic.

      Note that specifying this parameter here will -override the log -level parameter in the -smb.conf(5) file.

      -R <name resolve order>

      This option is used to determine what naming +override the log level parameter +in the smb.conf file.

      -R <name resolve order>

      This option is used to determine what naming services and in what order to resolve host names to IP addresses. The option takes a space-separated -string of different name resolution options.

      The options are: "lmhosts", "host", "wins" and "bcast". +string of different name resolution options.

      The options are: "lmhosts", "host", "wins" and "bcast". They cause names to be resolved as follows :

      • lmhosts: Lookup an IP address in the Samba lmhosts file. If the line in lmhosts has no name type attached to the @@ -67,11 +65,11 @@ parameter. This is the least reliable of the name resolution methods as it depends on the target host being on a locally connected subnet.

      If this parameter is not set then the name resolve order -defined in the smb.conf(5) file parameter -(name resolve order) will be used.

      The default order is lmhosts, host, wins, bcast. Without -this parameter or any entry in the name resolve order - parameter of the smb.conf(5) file, the name resolution methods -will be attempted in this order.

      -L libdir

      This parameter specifies the location of the +defined in the smb.conf file parameter +(name resolve order) will be used. +

      The default order is lmhosts, host, wins, bcast. Without +this parameter or any entry in the name resolve order parameter of the smb.conf file, the name +resolution methods will be attempted in this order.

      -L libdir

      This parameter specifies the location of the shared libraries used by smbsh. The default value is specified at compile time.

      EXAMPLES

      To use the smbsh command, execute @@ -93,7 +91,7 @@ will be attempted in this order.

      -L libdir command to change directories, vi to edit files, and rcp to copy files.

      VERSION

      This man page is correct for version 3.0 of the Samba suite.

      BUGS

      smbsh works by intercepting the standard libc calls with the dynamically loaded versions in - smbwrapper.o. Not all calls have been "wrapped", so + smbwrapper.o. Not all calls have been "wrapped", so some programs may not function correctly under smbsh .

      Programs which are not dynamically linked cannot make use of smbsh's functionality. Most versions diff --git a/docs/htmldocs/smbspool.8.html b/docs/htmldocs/smbspool.8.html index 186f30ebcf..7366ab458f 100644 --- a/docs/htmldocs/smbspool.8.html +++ b/docs/htmldocs/smbspool.8.html @@ -3,7 +3,7 @@ are position-dependent for compatibility with the Common UNIX Printing System, but you can use smbspool with any printing system or from a program or script.

      DEVICE URI

      smbspool specifies the destination using a Uniform Resource - Identifier ("URI") with a method of "smb". This string can take + Identifier ("URI") with a method of "smb". This string can take a number of forms:

      • smb://server/printer

      • smb://workgroup/server/printer

      • smb://username:password@server/printer

      • smb://username:password@workgroup/server/printer

      smbspool tries to get the URI from argv[0]. If argv[0] contains the name of the program then it looks in the DEVICE_URI environment variable.

      Programs using the exec(2) functions can diff --git a/docs/htmldocs/smbstatus.1.html b/docs/htmldocs/smbstatus.1.html index c1be6234c3..99b152e75c 100644 --- a/docs/htmldocs/smbstatus.1.html +++ b/docs/htmldocs/smbstatus.1.html @@ -7,8 +7,7 @@ configuration details required by the server. The information in this file includes server-specific information such as what printcap file to use, as well as descriptions of all the services that the server is -to provide. See -smb.conf(5) for more information. +to provide. See smb.conf for more information. The default configuration file name is determined at compile time.

      -d|--debug=debuglevel

      debuglevel is an integer from 0 to 10. The default value if this parameter is @@ -22,9 +21,8 @@ amounts of log data, and should only be used when investigating a problem. Levels above 3 are designed for use only by developers and generate HUGE amounts of log data, most of which is extremely cryptic.

      Note that specifying this parameter here will -override the log -level parameter in the -smb.conf(5) file.

      -l|--logfile=logbasename

      File name for log/debug files. The extension +override the log level parameter +in the smb.conf file.

      -l|--logfile=logbasename

      File name for log/debug files. The extension ".client" will be appended. The log file is never removed by the client.

      -v|--verbose

      gives verbose output.

      -L|--locks

      causes smbstatus to only list locks.

      -B|--byterange

      causes smbstatus to include byte range locks. diff --git a/docs/htmldocs/smbtar.1.html b/docs/htmldocs/smbtar.1.html index 30058d1860..95aabf1bc3 100644 --- a/docs/htmldocs/smbtar.1.html +++ b/docs/htmldocs/smbtar.1.html @@ -2,7 +2,7 @@ directly to UNIX tape drives

      Synopsis

      smbtar [-r] [-i] [-a] [-v] {-s server} [-p password] [-x services] [-X] [-N filename] [-b blocksize] [-d directory] [-l loglevel] [-u user] [-t tape] {filenames}

      DESCRIPTION

      This tool is part of the Samba(7) suite.

      smbtar is a very small shell script on top of smbclient(1) which dumps SMB shares directly to tape.

      OPTIONS

      -s server

      The SMB/CIFS server that the share resides upon.

      -x service

      The share name on the server to connect to. - The default is "backup".

      -X

      Exclude mode. Exclude filenames... from tar + The default is "backup".

      -X

      Exclude mode. Exclude filenames... from tar create or restore.

      -d directory

      Change to initial directory before restoring / backing up files.

      -v

      Verbose mode.

      -p password

      The password to use to access a share. Default: none

      -u user

      The user id to connect as. Default: diff --git a/docs/htmldocs/smbtree.1.html b/docs/htmldocs/smbtree.1.html index 6cf24ddf91..cc683838dd 100644 --- a/docs/htmldocs/smbtree.1.html +++ b/docs/htmldocs/smbtree.1.html @@ -1,6 +1,6 @@ smbtree

      Name

      smbtree — A text based smb network browser

      Synopsis

      smbtree [-b] [-D] [-S]

      DESCRIPTION

      This tool is part of the Samba(7) suite.

      smbtree is a smb browser program - in text mode. It is similar to the "Network Neighborhood" found + in text mode. It is similar to the "Network Neighborhood" found on Windows computers. It prints a tree with all the known domains, the servers in those domains and the shares on the servers. @@ -17,8 +17,7 @@ configuration details required by the server. The information in this file includes server-specific information such as what printcap file to use, as well as descriptions of all the services that the server is -to provide. See -smb.conf(5) for more information. +to provide. See smb.conf for more information. The default configuration file name is determined at compile time.

      -d|--debug=debuglevel

      debuglevel is an integer from 0 to 10. The default value if this parameter is @@ -32,10 +31,9 @@ amounts of log data, and should only be used when investigating a problem. Levels above 3 are designed for use only by developers and generate HUGE amounts of log data, most of which is extremely cryptic.

      Note that specifying this parameter here will -override the log -level parameter in the -smb.conf(5) file.

      -l|--logfile=logbasename

      File name for log/debug files. The extension -".client" will be appended. The log file is +override the log level parameter +in the smb.conf file.

      -l|--logfile=logbasename

      File name for log/debug files. The extension +".client" will be appended. The log file is never removed by the client.

      -N

      If specified, this parameter suppresses the normal password prompt from the client to the user. This is useful when diff --git a/docs/htmldocs/speed.html b/docs/htmldocs/speed.html index 626d5e0193..47f19abb70 100644 --- a/docs/htmldocs/speed.html +++ b/docs/htmldocs/speed.html @@ -1,4 +1,4 @@ -Chapter 39. Samba Performance Tuning

      Chapter 39. Samba Performance Tuning
      Prev Part VI. Appendixes Next

      Chapter 39. 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 changing kernel
      Corrupt tdb Files

      Comparisons

      +Chapter 39. Samba Performance Tuning

      Chapter 39. Samba Performance Tuning
      Prev Part VI. Appendixes Next

      Chapter 39. 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 changing kernel
      Corrupt tdb Files

      Comparisons

      The Samba server uses TCP to talk to the client. Thus 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,14 +20,14 @@ suspect the biggest factor is not Samba vs 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.

      The socket options that Samba uses are settable both on the command line with the -O option, or in the smb.conf file.

      -The socket options section of the smb.conf manual page describes how +The socket options section of the smb.conf manual page describes how to set these and gives recommendations.

      Getting the socket options right can make a big difference to your @@ -36,11 +36,11 @@ much. The correct settings are very dependent on your local network.

      The socket option TCP_NODELAY is the one that seems to make the biggest single difference for most networks. Many people report that -adding socket options = TCP_NODELAY doubles the read +adding socket options = TCP_NODELAY doubles the read performance of a Samba drive. The best explanation I have seen for this is that the Microsoft TCP/IP stack is slow in sending tcp ACKs. -

      Read size

      -The option read size affects the overlap of disk +

      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 SMBreadbraw) is larger than this value then the server begins writing @@ -56,10 +56,10 @@ The default value is 16384, but very little experimentation has been done 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

      -At startup the client and server negotiate a maximum transmit size, +

      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 +maximum size that Samba will negotiate using the max xmit option in smb.conf. Note that this is the maximum size of SMB requests that Samba will accept, but not the maximum size that the *client* will accept. The client maximum receive size is sent to Samba by the client and Samba @@ -70,41 +70,41 @@ 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

      -If you set the log level (also known as debug level) higher than 2 +

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

      Read raw

      -The read raw operation is designed to be an optimised, low-latency +

      Read raw

      +The read raw operation is designed to be an optimised, low-latency file read operation. A server may choose to not support it, -however. and Samba makes support for read raw optional, with it +however. and Samba makes support for read raw optional, with it being enabled by default.

      -In some cases clients don't handle read raw very well and actually +In some cases clients don't handle read raw very well and actually 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 +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

      -The write raw operation is designed to be an optimised, low-latency +

      Write raw

      +The write raw operation is designed to be an optimised, low-latency file write operation. A server may choose to not support it, -however. and Samba makes support for write raw optional, with 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 +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

      +the lowest practical password level will improve things. +

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

      Samba performance problem due changing kernel

      +

      Samba performance problem due changing kernel

      Hi everyone. I am running Gentoo on my server and samba 2.2.8a. Recently I changed kernel version from linux-2.4.19-gentoo-r10 to linux-2.4.20-wolk4.0s. And now I have performance issue with samba. Ok @@ -119,7 +119,7 @@ Grab 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, etc... look normal for ethernet. -

      Corrupt tdb Files

      +

      Corrupt tdb Files

      Well today it happened, Our first major problem using samba. Our samba PDC server has been hosting 3 TB of data to our 500+ users [Windows NT/XP] for the last 3 years using samba, no problem. @@ -137,4 +137,4 @@ Q2) What I also would like to mention is that the service latency seems a lot lower then before the locks cleanup, any ideas on keeping it top notch?

      A2) Yes! Same answer as for Q1! -

      Prev Up Next
      Chapter 38. Samba and other CIFS clients Home Chapter 40. DNS and DHCP Configuration Guide
      +

      Prev Up Next
      Chapter 38. Samba and other CIFS clients Home Chapter 40. DNS and DHCP Configuration Guide
      diff --git a/docs/htmldocs/swat.8.html b/docs/htmldocs/swat.8.html index e0719dce3d..a7f2eaaf5b 100644 --- a/docs/htmldocs/swat.8.html +++ b/docs/htmldocs/swat.8.html @@ -19,8 +19,7 @@ configuration details required by the server. The information in this file includes server-specific information such as what printcap file to use, as well as descriptions of all the services that the server is -to provide. See -smb.conf(5) for more information. +to provide. See smb.conf for more information. The default configuration file name is determined at compile time.

      -d|--debug=debuglevel

      debuglevel is an integer from 0 to 10. The default value if this parameter is @@ -34,10 +33,9 @@ amounts of log data, and should only be used when investigating a problem. Levels above 3 are designed for use only by developers and generate HUGE amounts of log data, most of which is extremely cryptic.

      Note that specifying this parameter here will -override the log -level parameter in the -smb.conf(5) file.

      -l|--logfile=logbasename

      File name for log/debug files. The extension -".client" will be appended. The log file is +override the log level parameter +in the smb.conf file.

      -l|--logfile=logbasename

      File name for log/debug files. The extension +".client" will be appended. The log file is never removed by the client.

      -h|--help

      Print a summary of command line options.

      INSTALLATION

      Swat is included as binary package with most distributions. The @@ -62,7 +60,7 @@ never removed by the client. and /etc/inetd.conf you need to send a HUP signal to inetd. To do this use kill -1 PID where PID is the process ID of the inetd daemon.

    LAUNCHING

    To launch SWAT just run your favorite web browser and - point it at "http://localhost:901/".

    Note that you can attach to SWAT from any IP connected + point it at "http://localhost:901/".

    Note that you can attach to SWAT from any IP connected machine but connecting from a remote machine leaves your connection open to password sniffing as passwords will be sent in the clear over the wire.

    FILES

    /etc/inetd.conf

    This file must contain suitable startup diff --git a/docs/htmldocs/testprns.1.html b/docs/htmldocs/testprns.1.html index ff7d4efd33..b63483d5de 100644 --- a/docs/htmldocs/testprns.1.html +++ b/docs/htmldocs/testprns.1.html @@ -1,11 +1,11 @@ testprns

    Name

    testprns — check printer name for validity with smbd

    Synopsis

    testprns {printername} [printcapname]

    DESCRIPTION

    This tool is part of the Samba(7) suite.

    testprns is a very simple test program to determine whether a given printer name is valid for use in - a service to be provided by smbd(8).

    "Valid" in this context means "can be found in the - printcap specified". This program is very stupid - so stupid in + a service to be provided by smbd(8).

    "Valid" in this context means "can be found in the + printcap specified". This program is very stupid - so stupid in fact that it would be wisest to always specify the printcap file to use.

    OPTIONS

    printername

    The printer name to validate.

    Printer names are taken from the first field in each record in the printcap file, single printer names and sets - of aliases separated by vertical bars ("|") are recognized. + of aliases separated by vertical bars ("|") are recognized. Note that no validation or checking of the printcap syntax is done beyond that required to extract the printer name. It may be that the print spooling system is more forgiving or less @@ -16,9 +16,9 @@ specified at compile time.

    FILES

    /etc/printcap

    This is usually the default printcap file to scan. See printcap (5).

    DIAGNOSTICS

    If a printer is found to be valid, the message - "Printer name <printername> is valid" will be + "Printer name <printername> is valid" will be displayed.

    If a printer is found to be invalid, the message - "Printer name <printername> is not valid" will be + "Printer name <printername> is not valid" will be displayed.

    All messages that would normally be logged during operation of the Samba daemons are logged by this program to the file test.log in the current directory. The diff --git a/docs/htmldocs/troubleshooting.html b/docs/htmldocs/troubleshooting.html index 582beeb6b0..d18399caeb 100644 --- a/docs/htmldocs/troubleshooting.html +++ b/docs/htmldocs/troubleshooting.html @@ -1 +1 @@ -Part V. Troubleshooting

    Part V. Troubleshooting
    Prev   Next

    Troubleshooting

    Table of Contents

    33. The Samba checklist
    Introduction
    Assumptions
    The tests
    Still having troubles?
    34. Analysing and solving samba problems
    Diagnostics tools
    Installing 'Network Monitor' on an NT Workstation or a Windows 9x box
    Useful URLs
    Getting help from the mailing lists
    How to get off the mailing lists
    35. Reporting Bugs
    Introduction
    General info
    Debug levels
    Internal errors
    Attaching to a running process
    Patches
    Prev Up Next
    Chapter 32. SWAT - The Samba Web Administration Tool Home Chapter 33. The Samba checklist
    +Part V. Troubleshooting
    Part V. Troubleshooting
    Prev   Next

    Troubleshooting

    Table of Contents

    33. The Samba checklist
    Introduction
    Assumptions
    The tests
    34. Analysing and solving samba problems
    Diagnostics tools
    Debugging with Samba itself
    Tcpdump
    Ethereal
    The Windows Network Monitor
    Useful URLs
    Getting help from the mailing lists
    How to get off the mailing lists
    35. Reporting Bugs
    Introduction
    General info
    Debug levels
    Internal errors
    Attaching to a running process
    Patches
    Prev Up Next
    Chapter 32. SWAT - The Samba Web Administration Tool Home Chapter 33. The Samba checklist
    diff --git a/docs/htmldocs/type.html b/docs/htmldocs/type.html index 209c177a0b..5322995de4 100644 --- a/docs/htmldocs/type.html +++ b/docs/htmldocs/type.html @@ -1,9 +1,5 @@ -Part II. Server Configuration Basics
    Part II. Server Configuration Basics
    Prev   Next

    Server Configuration Basics

    First Steps in Server Configuration

    +Part II. Server Configuration Basics

    Part II. Server Configuration Basics
    Prev   Next

    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

    4. 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)
    Seamless Windows Network Integration
    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
    5. Domain Control
    Features and Benefits
    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 Problems and Errors
    I cannot include a '$' in a machine name
    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.
    The system can not log you on (C000019B)....
    The machine trust account for this computer either does not -exist or is not accessible.
    When I attempt to login to a Samba Domain from a NT4/W2K workstation, -I get a message about my account being disabled.
    Until a few minutes after Samba has started, clients get the error "Domain Controller Unavailable"
    6. Backup Domain Control
    Features And Benefits
    Essential Background Information
    MS Windows NT4 Style Domain Control
    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, what can I do?
    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?
    7. Domain Membership
    Features and Benefits
    MS Windows Workstation/Server Machine Trust Accounts
    Manual Creation of Machine Trust Accounts
    Using NT4 Server Manager to Add Machine Accounts to the Domain
    "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
    Setup your smb.conf
    Setup your /etc/krb5.conf
    Create the computer account
    Test your server setup
    Testing with smbclient
    Notes
    Common Errors
    Can Not Add Machine Back to Domain
    Adding Machine to Domain Fails
    8. Stand-Alone Servers
    Features and Benefits
    Background
    Example Configuration
    Reference Documentation Server
    Central Print Serving
    Common Errors
    9. MS Windows Network Configuration Guide
    Note
    Prev Up Next
    Chapter 3. Fast Start for the Impatient Home Chapter 4. Server Types and Security Modes
    +

    Table of Contents

    4. 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
    5. Domain Control
    Features and Benefits
    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 can not log you on (C000019B)....
    The machine trust account not accessible
    Account disabled
    Domain Controller Unavailable
    Can not log onto domain member workstation after joining domain
    6. Backup Domain Control
    Features And Benefits
    Essential Background Information
    MS Windows NT4 Style Domain Control
    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, what can I do?
    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?
    7. Domain Membership
    Features and Benefits
    MS Windows Workstation/Server Machine Trust Accounts
    Manual Creation of Machine Trust Accounts
    Using NT4 Server Manager to Add Machine Accounts to the Domain
    "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
    Setup your smb.conf
    Setup your /etc/krb5.conf
    Create the computer account
    Test your server setup
    Testing with smbclient
    Notes
    Common Errors
    Can Not Add Machine Back to Domain
    Adding Machine to Domain Fails
    I can't join a Windows 2003 PDC
    8. Stand-Alone Servers
    Features and Benefits
    Background
    Example Configuration
    Reference Documentation Server
    Central Print Serving
    Common Errors
    9. MS Windows Network Configuration Guide
    Note
    Prev Up Next
    Chapter 3. Fast Start for the Impatient Home Chapter 4. Server Types and Security Modes
    diff --git a/docs/htmldocs/unicode.html b/docs/htmldocs/unicode.html index a971602e81..a4f568576d 100644 --- a/docs/htmldocs/unicode.html +++ b/docs/htmldocs/unicode.html @@ -1,4 +1,4 @@ -Chapter 27. Unicode/Charsets
    Chapter 27. Unicode/Charsets
    Prev Part III. Advanced Configuration Next

    Chapter 27. Unicode/Charsets

    Jelmer R. Vernooij

    The Samba Team

    TAKAHASHI Motonobu

    25 March 2003

    Table of Contents

    Features and Benefits
    What are charsets and unicode?
    Samba and charsets
    Conversion from old names
    Japanese charsets

    Features and Benefits

    +Chapter 27. Unicode/Charsets

    Chapter 27. Unicode/Charsets
    Prev Part III. Advanced Configuration Next

    Chapter 27. Unicode/Charsets

    Jelmer R. Vernooij

    The Samba Team

    TAKAHASHI Motonobu

    25 March 2003

    Table of Contents

    Features and Benefits
    What are charsets and unicode?
    Samba and charsets
    Conversion from old names
    Japanese charsets
    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 @@ -6,14 +6,13 @@ ago it was common for software to be written for exclusive use in the country of origin.

    Of all the effort that has been brought to bear on providing native language support -for all computer users, the efforts of the Openi18n organisation is deserving of -special mention. For more information about Openi18n please refer to: -http://www.openi18n.org/. +for all computer users, the efforts of the Openi18n organisation 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 trans-global file and printer sharing platform. -

    What are charsets and unicode?

    +

    What are charsets and unicode?

    Computers communicate in numbers. In texts, each number will be translated to a corresponding letter. The meaning that will be assigned to a certain number depends on the character set(charset) @@ -30,45 +29,39 @@ is more then all possible characters one could think of. They are called multibyte charsets (because they use more then one byte to store one character).

    -A standardised multibyte charset is unicode, info is available at -www.unicode.org. -A big advantage of using a multibyte charset is that you only need one; no -need to make sure two computers use the same charset when they are + A standardised multibyte charset is 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 used to use single-byte charsets, named +

    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 protocol. Thus, you -have to make sure you are using the same charset when talking to an old client. +have to make sure you are using the same charset when talking to an older client. Newer clients (Windows NT, 2K, XP) talk unicode over the wire. -

    Samba and charsets

    +

    Samba and charsets

    As of samba 3.0, samba can (and will) talk unicode over the wire. Internally, samba knows of three kinds of character sets: -

    unix charset

    +

    unix charset

    This is the charset used internally by your operating system. - The default is ASCII, which is fine for most - systems. -

    display charset

    This is the charset samba will use to print messages + The default is UTF-8, which is fine for most + systems. The default in previous samba releases was ASCII. +

    display charset

    This is the charset samba will use to print messages on your screen. It should generally be the same as the unix charset. -

    dos charset

    This is the charset samba uses when communicating with +

    dos charset

    This is the charset samba uses when communicating with DOS and Windows 9x clients. It will talk unicode to all newer clients. 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

    Because previous samba versions did not do any charset conversion, +

    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.

    The following script from Steve Langasek converts all -filenames from CP850 to the iso8859-15 charset.

    -#find /path/to/share -type f -exec bash -c 'CP="{}"; ISO=`echo -n "$CP" | iconv -f cp850 \ - -t iso8859-15`; if [ "$CP" != "$ISO" ]; then mv "$CP" "$ISO"; fi' \; - -

    Japanese charsets

    Samba doesn't work correctly with Japanese charsets yet. Here are -points of attention when setting it up:

    • You should set mangling method = -hash

    • There are various iconv() implementations around and not +for the local charset used by the DOS/Windows clients.

      Bjoern Jacke has written a utility named convm that can convert whole directory + structures to different charsets with one single command. +

    Japanese charsets

    Samba doesn't work correctly with Japanese charsets yet. Here are +points of attention when setting it up:

    • You should set mangling method = hash

    • There are various iconv() implementations around and not all of them work equally well. glibc2's iconv() has a critical problem in CP932. libiconv-1.8 works with CP932 but still has some problems and -does not work with EUC-JP.

    • You should set dos charset = CP932, not -Shift_JIS, SJIS...

    • Currently only unix charset = CP932 +does not work with EUC-JP.

    • You should set dos charset = CP932, not +Shift_JIS, SJIS...

    • Currently only unix charset = CP932 will work (but still has some problems...) because of iconv() issues. -unix charset = EUC-JP doesn't work well because of -iconv() issues.

    • Currently Samba 3.0 does not support unix charset -= UTF8-MAC/CAP/HEX/JIS*

    More information (in Japanese) is available at: http://www.atmarkit.co.jp/flinux/special/samba3/samba3a.html.

    Prev Up Next
    Chapter 26. Integrating MS Windows networks with Samba Home Chapter 28. Samba Backup Techniques
    +unix charset = EUC-JP doesn't work well because of +iconv() issues.

  • Currently Samba 3.0 does not support unix charset = UTF8-MAC/CAP/HEX/JIS*

    • More information (in Japanese) is available at: http://www.atmarkit.co.jp/flinux/special/samba3/samba3a.html.

    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 don't have any dos clients, you can safely ignore this message.

    CP850 should be supported by your local iconv implementation. Make sure you have all the required packages installed. If you compiled samba from source, make sure configure found iconv.

    Prev Up Next
    Chapter 26. Integrating MS Windows networks with Samba Home Chapter 28. Samba Backup Techniques
    diff --git a/docs/htmldocs/upgrading-to-3.0.html b/docs/htmldocs/upgrading-to-3.0.html index ac559fa129..e7c1c61234 100644 --- a/docs/htmldocs/upgrading-to-3.0.html +++ b/docs/htmldocs/upgrading-to-3.0.html @@ -1,19 +1,176 @@ -Chapter 30. Upgrading from Samba-2.x to Samba-3.0.0
    Chapter 30. Upgrading from Samba-2.x to Samba-3.0.0
    Prev Part IV. Migration and Updating Next

    Chapter 30. Upgrading from Samba-2.x to Samba-3.0.0

    Jelmer R. Vernooij

    The Samba Team

    25 October 2002

    Table of Contents

    Charsets
    Obsolete configuration options
    Password Backend

    Charsets

    You might experience problems with special characters -when communicating with old DOS clients. Codepage -support has changed in samba 3.0. Read the chapter -Unicode support for details. -

    Obsolete configuration options

    -In 3.0, the following configuration options have been removed. -

    printer driver (replaced by new driver procedures)
    printer driver file (replaced by new driver procedures)
    printer driver location (replaced by new driver procedures)
    use rhosts
    postscript
    client code page (replaced by dos charset)
    vfs path
    vfs options

    Password Backend

    -Effective with the release of samba-3 it is now imperative that the password backend -be correctly defined in smb.conf. -

    -Those migrating from samba-2.x with plaintext password support need the following: -passdb backend = guest. -

    -Those migrating from samba-2.x with encrypted password support should add to smb.conf -passdb backend = smbpasswd, guest. -

    -LDAP using Samba-2.x systems can continue to operate with the following entry -passdb backend = ldapsam_compat, guest. -

    Prev Up Next
    Part IV. Migration and Updating Home Chapter 31. Migration from NT4 PDC to Samba-3 PDC
    +Chapter 30. Upgrading from Samba-2.x to Samba-3.0.0
    Chapter 30. Upgrading from Samba-2.x to Samba-3.0.0
    Prev Part IV. Migration and Updating Next

    Chapter 30. Upgrading from Samba-2.x to Samba-3.0.0

    Jelmer R. Vernooij

    The Samba Team

    John H. Terpstra

    Samba Team

    Gerald (Jerry) Carter

    Samba Team

    June 30, 2003

    Table of Contents

    New Features in Samba-3
    Configuration Parameter Changes
    Removed Parameters
    New Parameters
    Modified Parameters (changes in behavior):
    New Functionality
    Databases
    Changes in Behavior
    Charsets
    Passdb Backends and Authentication
    Charsets
    LDAP

    New Features in Samba-3

    +Major new features: +

    1. + Active Directory support. This release is able to join a 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 now a much better infrastructure for multi-byte + 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 auth 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. This needs lots of testing. +

    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", at the moment only a few things are + implemented. +

    6. + Samba now negotiates NT-style status32 codes on the wire. This + improves error handling a lot. +

    7. + Better Windows 2000/XP/2003 printing support including publishing + printer attributes in active directory +

    8. + New loadable RPC modules +

    9. + New dual-daemon winbindd support (-B) 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. +

    +Plus lots of other improvements! +

    Configuration Parameter Changes

    +This section contains a brief listing of changes to smb.conf options +in the 3.0.0 release. Please refer to the smb.conf(5) man page for +complete descriptions of new or modified parameters. +

    Removed Parameters

    (order alphabetically):

    • admin log

    • alternate permissions

    • character set

    • client codepage

    • code page directory

    • coding system

    • domain admin group

    • domain guest group

    • force unknown acl user

    • nt smb support

    • post script

    • printer driver

    • printer driver file

    • printer driver location

    • status

    • total print jobs

    • use rhosts

    • valid chars

    • vfs options

    New Parameters

    (new parameters have been 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

    • set primary group script

    Authentication

    • auth methods

    • ads server

    • realm

    Protocol Options

    • client lanman auth

    • client NTLMv2 auth

    • client schannel

    • client signing

    • client use spnego

    • disable netbios

    • ntlm auth

    • paranoid server security

    • server schannel

    • smb ports

    • use spnego

    File Service

    • get quota command

    • hide special files

    • hide unwriteable files

    • hostname lookups

    • kernel change notify

    • mangle prefix

    • msdfs proxy

    • set quota command

    • use sendfile

    • vfs objects

    Printing

    • max reported print jobs

    UNICODE and Character Sets

    • display charset

    • dos charset

    • unicode

    • unix charset

    SID to uid/gid Mappings

    • idmap backend

    • idmap gid

    • idmap only

    • idmap uid

    LDAP

    • ldap delete dn

    • ldap group suffix

    • ldap idmap suffix

    • ldap machine suffix

    • ldap passwd sync

    • ldap trust ids

    • ldap user suffix

    General Configuration

    • preload modules

    • privatedir

    Modified Parameters (changes in behavior):

    • encrypt passwords (enabled by default)

    • mangling method (set to 'hash2' by default)

    • passwd chat

    • passwd program

    • restrict anonymous (integer value)

    • security (new 'ads' value)

    • strict locking (enabled by default)

    • winbind cache time (increased to 5 minutes)

    • winbind uid (deprecated in favor of 'idmap uid')

    • winbind gid (deprecated in favor of 'idmap gid')

    New Functionality

    Databases

    + This section contains brief descriptions of any new databases + introduced in Samba 3.0. Please remember to backup your existing + ${lock directory}/*tdb before upgrading to Samba 3.0. Samba will + upgrade databases as they are opened (if necessary), but downgrading + from 3.0 to 2.2 is an unsupported path. +

    Table 30.1. TDB File Descriptions

    NameDescriptionBackup?
    account_policyUser policy settingsyes
    gencacheGeneric caching dbno
    group_mapping

    Mapping table from Windows groups/SID to unix groups

    		yes
    idmap

    new ID map table from SIDS to UNIX uids/gids

    		yes
    namecacheName resolution cache entriesno
    netlogon_unigrp

    Cache of universal group membership obtained when operating + as a member of a Windows domain

    		no
    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 db tables via the winreg RPCs

    		no

    Changes in Behavior

    + The following issues are known changes in behavior between Samba 2.2 and + Samba 3.0 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.0 + rejects the connection as NT_STATUS_LOGON_FAILURE. There is no + current work around to re-establish the 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.0 introduces a new 'add machine + script' that must be specified for this purpose. Samba 3.0 will + not fall back to using the 'add user script' in the absence of + an 'add machine script' +

    Charsets

    + You might experience problems with special characters when communicating with old DOS + clients. Codepage support has changed in samba 3.0. Read the chapter + Unicode support for details. +

    Passdb Backends and Authentication

    + There have been a few new changes that Samba administrators should be + aware of when moving to Samba 3.0. +

    1. + Encrypted passwords have been enabled by default in order to + inter-operate 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.0 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 the chapter about 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(8) tool have been split between the + new smbpasswd(8) utility, the net(8) tool, and the new pdbedit(8) + utility. See the respective man pages for details. +

    Charsets

    + You might experience problems with special characters when communicating with old DOS + clients. Codepage support has changed in samba 3.0. Read the chapter + Unicode support for details. +

    LDAP

    + This section outlines the new features affecting Samba / LDAP integration. +

    New Schema

    + A new object class (sambaSamAccount) has been introduced to replace + the old sambaAccount. This change aids us in the renaming of attributes + to prevent clashes with attributes from other vendors. There is a + conversion script (examples/LDAP/convertSambaAccount) to modify and LDIF + file to the new schema. +

    + Example: + 

    +		$ ldapsearch .... -b "ou=people,dc=..." > old.ldif
+		$ convertSambaAccount <DOM SID> old.ldif new.ldif
+

    + The <DOM SID> can be obtained by running 'net getlocalsid <DOMAINNAME> + on the Samba PDC as root. +

    + 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 + the schema file and must be uncommented before use if needed. + The 2.2 object class declaration for a sambaAccount has not changed + in the 3.0 samba.schema file. +

    + 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

    + 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 sub-suffix parameters. In this case, the order of the suffix + listings in smb.conf is important. Always place the 'ldap suffix' first + in the list. +

    + Due to a limitation in Samba's smb.conf parsing, you should not surround + the DN's with quotation marks. +

    IdMap LDAP support

    + Samba 3.0 supports an ldap backend for the idmap subsystem. The + following options would inform Samba that the idmap table should be + stored on the directory server onterose in the "ou=idmap,dc=plainjoe, + dc=org" partition. +

    [global]
    ...
    idmap backend = ldap:ldap://onterose/
    ldap idmap suffix = ou=idmap,dc=plainjoe,dc=org
    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. +

    Prev Up Next
    Part IV. Migration and Updating Home Chapter 31. Migration from NT4 PDC to Samba-3 PDC
    diff --git a/docs/htmldocs/vfstest.1.html b/docs/htmldocs/vfstest.1.html index 7b124c070f..2cfbfad283 100644 --- a/docs/htmldocs/vfstest.1.html +++ b/docs/htmldocs/vfstest.1.html @@ -14,8 +14,7 @@ configuration details required by the server. The information in this file includes server-specific information such as what printcap file to use, as well as descriptions of all the services that the server is -to provide. See -smb.conf(5) for more information. +to provide. See smb.conf for more information. The default configuration file name is determined at compile time.

    -d|--debug=debuglevel

    debuglevel is an integer from 0 to 10. The default value if this parameter is @@ -29,10 +28,9 @@ amounts of log data, and should only be used when investigating a problem. Levels above 3 are designed for use only by developers and generate HUGE amounts of log data, most of which is extremely cryptic.

    Note that specifying this parameter here will -override the log -level parameter in the -smb.conf(5) file.

    -l|--logfile=logbasename

    File name for log/debug files. The extension -".client" will be appended. The log file is +override the log level parameter +in the smb.conf file.

    -l|--logfile=logbasename

    File name for log/debug files. The extension +".client" will be appended. The log file is never removed by the client.

    COMMANDS

    VFS COMMANDS

    • load <module.so> - Load specified VFS module

    • populate <char> <size> - Populate a data buffer with the specified data

    • showdata [<offset> <len>] - Show data currently in data buffer diff --git a/docs/htmldocs/wbinfo.1.html b/docs/htmldocs/wbinfo.1.html index 4aa9ddab12..f5f5af0a27 100644 --- a/docs/htmldocs/wbinfo.1.html +++ b/docs/htmldocs/wbinfo.1.html @@ -1,22 +1,32 @@ -wbinfo

      Name

      wbinfo — Query information from winbind daemon

      Synopsis

      wbinfo [-u] [-g] [-N netbios-name] [-I ip] [-n name] [-s sid] [-U uid] [-G gid] [-S sid] [-Y sid] [-t] [-m] [--sequence] [-r user] [-a user%password] [--set-auth-user user%password] [--get-auth-user] [-p]

      DESCRIPTION

      This tool is part of the Samba(7) suite.

      The wbinfo program queries and returns information +wbinfo

      Name

      wbinfo — Query information from winbind daemon

      Synopsis

      wbinfo [-a user%password] [-c username] [-C groupname] [--domain domain] [-I ip] [-s sid] [-u] [-U uid] [-g] [--get-auth-user] [-G gid] [-m] [-n name] [-N netbios-name] [-o user:group] [-O user:group] [-p] [-r user] [--set-auth-user user%password] [--sequence] [-S sid] [-t] [-x username] [-X groupname] [-Y sid]

      DESCRIPTION

      This tool is part of the Samba(7) suite.

      The wbinfo program queries and returns information created and used by the winbindd(8) daemon.

      The winbindd(8) daemon must be configured and running for the wbinfo program to be able - to return information.

      OPTIONS

      -u

      This option will list all users available - in the Windows NT domain for which the winbindd(8) daemon is operating in. Users in all trusted domains - will also be listed. Note that this operation does not assign - user ids to any users that have not already been seen by winbindd(8) - .

      -g

      This option will list all groups available + to return information.

      OPTIONS

      -a username%password

      Attempt to authenticate a user via winbindd. + This checks both authenticaion methods and reports its results. +

      -c user

      Create a local winbind user. +

      -C group

      Create a local winbindd group. +

      --domain name

      This parameter sets the domain on which any specified + operations will performed. If special domain name '.' is used to represent + the current domain to which winbindd belongs. Currently only the + --sequence, + -u, and -g options honor this parameter. +

      -g

      This option will list all groups available in the Windows NT domain for which the Samba(7) daemon is operating in. Groups in all trusted domains will also be listed. Note that this operation does not assign group ids to any groups that have not already been - seen by winbindd(8).

      -N name

      The -N option - queries winbindd(8) to query the WINS - server for the IP address associated with the NetBIOS name - specified by the name parameter. -

      -I ip

      The -I option + seen by winbindd(8).

      --get-auth-user

      Print username and password used by winbindd + during session setup to a domain controller. Username + and password can be set using '-A'. Only available for + root.

      -G gid

      Try to convert a UNIX group id to a Windows + NT SID. If the gid specified does not refer to one within + the idmap gid range then the operation will fail.

      -I ip

      The -I option queries winbindd(8) to send a node status request to get the NetBIOS name associated with the IP address specified by the ip parameter. +

      -m

      Produce a list of domains trusted by the + Windows NT server winbindd(8) contacts + when resolving names. This list does not include the Windows + NT domain the server is a Primary Domain Controller for.

      -n name

      The -n option queries winbindd(8) for the SID associated with the name specified. Domain names can be specified @@ -24,40 +34,43 @@ For example CWDOM1/Administrator refers to the Administrator user in the domain CWDOM1. If no domain is specified then the domain used is the one specified in the smb.conf(5) workgroup - parameter.

      -s sid

      Use -s to resolve + parameter.

      -N name

      The -N option + queries winbindd(8) to query the WINS + server for the IP address associated with the NetBIOS name + specified by the name parameter. +

      -o user:group

      Add a winbindd local group as a secondary group + for the specified winbindd local user. +

      -O user:group

      Remove a winbindd local group as a secondary group + for the specified winbindd local user. +

      -p

      Check whether winbindd is still alive. + Prints out either 'succeeded' or 'failed'. +

      -r username

      Try to obtain the list of UNIX group ids + to which the user belongs. This only works for users + defined on a Domain Controller. +

      -s sid

      Use -s to resolve a SID to a name. This is the inverse of the -n option above. SIDs must be specified as ASCII strings in the traditional Microsoft format. For example, - S-1-5-21-1455342024-3071081365-2475485837-500.

      -U uid

      Try to convert a UNIX user id to a Windows NT - SID. If the uid specified does not refer to one within - the winbind uid range then the operation will fail.

      -G gid

      Try to convert a UNIX group id to a Windows - NT SID. If the gid specified does not refer to one within - the winbind gid range then the operation will fail.

      -S sid

      Convert a SID to a UNIX user id. If the SID - does not correspond to a UNIX user mapped by winbindd(8) then the operation will fail.

      -Y sid

      Convert a SID to a UNIX group id. If the SID - does not correspond to a UNIX group mapped by winbindd(8) then - the operation will fail.

      -t

      Verify that the workstation trust account - created when the Samba server is added to the Windows NT - domain is working.

      -m

      Produce a list of domains trusted by the - Windows NT server winbindd(8) contacts - when resolving names. This list does not include the Windows - NT domain the server is a Primary Domain Controller for. -

      --sequence

      Show sequence numbers of - all known domains

      -r username

      Try to obtain the list of UNIX group ids - to which the user belongs. This only works for users - defined on a Domain Controller. -

      -a username%password

      Attempt to authenticate a user via winbindd. - This checks both authenticaion methods and reports its results. -

      --set-auth-user username%password

      Store username and password used by winbindd + S-1-5-21-1455342024-3071081365-2475485837-500.

      --set-auth-user username%password

      Store username and password used by winbindd during session setup to a domain controller. This enables winbindd to operate in a Windows 2000 domain with Restrict Anonymous turned on (a.k.a. Permissions compatiable with Windows 2000 servers only). -

      --get-auth-user

      Print username and password used by winbindd - during session setup to a domain controller. Username - and password can be set using '-A'. Only available for - root.

      -p

      Check whether winbindd is still alive. - Prints out either 'succeeded' or 'failed'. -

      -V

      Prints the version number for +

      --sequence

      Show sequence numbers of + all known domains

      -S sid

      Convert a SID to a UNIX user id. If the SID + does not correspond to a UNIX user mapped by winbindd(8) then the operation will fail.

      -t

      Verify that the workstation trust account + created when the Samba server is added to the Windows NT + domain is working.

      -u

      This option will list all users available + in the Windows NT domain for which the winbindd(8) daemon is operating in. Users in all trusted domains + will also be listed. Note that this operation does not assign + user ids to any users that have not already been seen by winbindd(8) + .

      -U uid

      Try to convert a UNIX user id to a Windows NT + SID. If the uid specified does not refer to one within + the idmap uid range then the operation will fail.

      -x user

      Delete an existing local winbind user. +

      -X group

      Delete an existing local winbindd group. +

      -Y sid

      Convert a SID to a UNIX group id. If the SID + does not correspond to a UNIX group mapped by winbindd(8) then + the operation will fail.

      -V

      Prints the version number for smbd.

      -h|--help

      Print a summary of command line options.

      EXIT STATUS

      The wbinfo program returns 0 if the operation succeeded, or 1 if the operation failed. If the winbindd(8) daemon is not working wbinfo will always return diff --git a/docs/htmldocs/winbind.html b/docs/htmldocs/winbind.html index 567e882367..1ee1de9f2f 100644 --- a/docs/htmldocs/winbind.html +++ b/docs/htmldocs/winbind.html @@ -1,14 +1,38 @@ -Chapter 21. Integrated Logon Support using Winbind

      Chapter 21. Integrated Logon Support using Winbind
      Prev Part III. Advanced Configuration Next

      Chapter 21. Integrated Logon Support using Winbind

      Tim Potter

      Samba Team

      Andrew Tridgell

      Samba Team

      Naag Mummaneni

      Jelmer R. Vernooij

      The Samba Team

      John H. Terpstra

      Samba Team

      27 June 2002

      Table of Contents

      Features and Benefits
      Introduction
      What Winbind Provides
      Target Uses
      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

      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. We present - winbind, a component of the Samba suite - of programs as a solution to the unified logon problem. Winbind - uses a UNIX implementation - of Microsoft RPC calls, Pluggable Authentication Modules, and the Name - Service Switch to allow Windows NT domain users to appear and operate - as UNIX users on a UNIX machine. This paper describes the winbind - system, explaining the functionality it provides, how it is configured, - and how it works internally.

      Introduction

      It is well known that UNIX and Microsoft Windows NT have +Chapter 21. Winbind: Use of Domain Accounts

      Chapter 21. Winbind: Use of Domain Accounts
      Prev Part III. Advanced Configuration Next

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

      27 June 2002

      Table of Contents

      Features and Benefits
      Introduction
      What Winbind Provides
      Target Uses
      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

      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 + solves the unified logon problem. Winbind uses a UNIX implementation of Microsoft + RPC calls, Pluggable Authentication Modules, and the Name Service Switch to + allow Windows NT domain users to appear and operate as UNIX users on a UNIX + machine. This chapter describes the winbind system, explaining the functionality + it provides, how it is configured, and how it works internally. +

      + Winbind provides three separate functions: +

      • + Authentication of user credentials (via PAM) +

      • + Identity resolution (via NSS)` +

      • + Windindd 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 stored the UID/GID + allocated from the idmap uid/gid range that it has mapped to the NT SID. + If idmap backend has been specified as ldapsam:url + then instead of using a local mapping winbindd will obtain this information + from the LDAP database. +

      Note

      + If winbindd is not running, then 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. +

      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 @@ -29,7 +53,7 @@ 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

      Winbind unifies UNIX and Windows NT account management by + problem.

      What Winbind Provides

      Winbind unifies UNIX and Windows NT account management by allowing a UNIX box to become a full member of a 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 @@ -53,7 +77,7 @@ to provide authentication via a 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

      Winbind is targeted at organizations that have an + 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 organizations to deploy UNIX workstations without having to @@ -63,12 +87,12 @@ 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.

      How Winbind Works

      The winbind system is designed around a client/server + the appliance into the domain.

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

      The technologies used to implement winbind are described - in detail below.

      Microsoft Remote Procedure Calls

      Over the last few years, efforts have been underway + in detail below.

      Microsoft Remote Procedure Calls

      Over the last few years, efforts have been underway by various Samba Team members to decode various aspects of the Microsoft Remote Procedure Call (MSRPC) system. This system is used for most network related operations between @@ -81,7 +105,7 @@ 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

      + NT account information onto UNIX user and group names.

      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. @@ -90,7 +114,7 @@ same way as a Win2k client would, and in so doing provide a much more efficient and effective winbind implementation. -

      Name Service Switch

      The Name Service Switch, or NSS, is a feature that is +

      Name Service Switch

      The Name Service Switch, or 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 @@ -112,7 +136,7 @@ the C library looks in /etc/nsswitch.conf for a line which matches the service type being requested, for example the "passwd" service type is used when user or group names - are looked up. This config line species which implementations + are looked up. This config line specifies which implementations of that service should be tried and in what order. If the passwd config line is:

       passwd: files example
@@ -127,7 +151,7 @@ passwd: files example
 		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, also known as PAM, + resolve user and group names.

      Pluggable Authentication Modules

      Pluggable Authentication Modules, also known as PAM, is 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 @@ -152,7 +176,7 @@ passwd: files example is copied to /lib/security/ and the PAM control files for relevant services are updated to allow authentication via winbind. See the PAM documentation - for more details.

      User and Group ID Allocation

      When a user or group is created under Windows NT + for more details.

      User and Group ID Allocation

      When a user or group is created under Windows NT is it allocated a numerical relative identifier (RID). This is slightly different to UNIX which has a range of numbers that are used to identify users, and the same range in which to identify @@ -165,7 +189,7 @@ passwd: files example 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

      An active system can generate a lot of user and group + RIDs are mapped to UNIX IDs in a consistent way.

      Result Caching

      An active 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 @@ -176,23 +200,12 @@ passwd: files example 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

      -Many thanks to John Trostel jtrostel@snapserver.com -for providing the HOWTO for this section. -

      -This HOWTO describes how to get winbind services up and running -to control access and authenticate users on your Linux box using -the winbind services which come with SAMBA 3.0. -

      Introduction

      + from the PDC.

      Installation and Configuration

      Introduction

      This section describes the procedures used to get winbind up and -running on a RedHat 7.1 system. Winbind is capable of providing access +running. Winbind is capable of providing access and authentication control for Windows Domain users through an NT or Win2K PDC for 'regular' services, such as telnet a nd ftp, as well for SAMBA services. -

      -This HOWTO has been written from a 'RedHat-centric' perspective, so if -you are using another distribution, you may have to modify the instructions -somewhat to fit the way your distribution works.

      • Why should I to this?

        This allows the SAMBA administrator to rely on the @@ -208,7 +221,7 @@ somewhat to fit the way your distribution works. SAMBA server, this HOWTO is for you. That said, I am no NT or PAM expert, so you may find a better or easier way to accomplish these tasks. -

      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 @@ -235,33 +248,18 @@ winbind modules, you should have at least the pam libraries resident on your system. For recent RedHat systems (7.1, for instance), that means pam-0.74-22. For best results, it is helpful to also install the development packages in pam-devel-0.74-22. -

    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, you will want to make sure that you have the -standard PAM package (for RedHat) which supplies the /etc/pam.d +standard PAM package which supplies the /etc/pam.d directory structure, including the pam modules are used by pam-aware services, several pam libraries, and the /usr/doc and /usr/man entries for pam. Winbind built better in SAMBA if the pam-devel package was also installed. This package includes the header files needed to compile pam-aware applications. -

    Configure and compile SAMBA

    -The configuration and compilation of SAMBA is pretty straightforward. -The first three steps may not be necessary depending upon -whether or not you have previously built the Samba binaries. -

    -root# autoconf
-root# make clean
-root# rm config.cache
-root# ./configure
-root# make
-root# make install
-

    -This will, by default, install SAMBA in /usr/local/samba. -See the main SAMBA documentation if you want to install SAMBA somewhere else. -It will also build the winbindd executable and libraries. -

    Configure nsswitch.conf and the +

    Configure nsswitch.conf and the winbind libraries on Linux and Solaris

    The libraries needed to run the winbindd daemon through nsswitch need to be copied to their proper locations, so @@ -296,7 +294,7 @@ is faster (and you don't need to reboot) if you do it manually:

    This makes libnss_winbind available to winbindd and echos back a check to you. -

    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 @@ -316,40 +314,25 @@ Programming Concepts for AIX": "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. Configure smb.conf These are described in more detail in the winbindd(8) man page. My smb.conf file was modified to include the following entries in the [global] section: -

    -[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 21.1. smb.conf for winbind set-up

    [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
    winbind 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

    Enter the following command to make the SAMBA server join the PDC domain, where DOMAIN is the name of your Windows domain and Administrator is a domain user who has administrative privileges in the domain.

    -root# /usr/local/samba/bin/net join -S PDC -U Administrator +root# /usr/local/samba/bin/net rpc join -S PDC -U Administrator

    The proper response to the command should be: "Joined the domain DOMAIN" where DOMAIN is your DOMAIN name. -

    Start up the winbindd daemon and test it!

    +

    Start up the winbindd daemon and test it!

    Eventually, you will want to modify your smb 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 @@ -391,8 +374,7 @@ your PDC. For example, I get the following response: CEO+krbtgt CEO+TsInternetUser

    -Obviously, I have named my domain 'CEO' and my winbind -separator is '+'. + 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: @@ -421,7 +403,7 @@ directories and default shells. 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. @@ -487,7 +469,7 @@ stop() { echo "" return $RETVAL } -

    Solaris

    Winbind doesn't work on Solaris 9, see the Portability chapter for details.

    On Solaris, you need to modify the +

    Solaris

    Winbind doesn't work on Solaris 9, see the Portability chapter 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, @@ -550,11 +532,11 @@ in the script above with: 

     	/usr/local/samba/bin/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 @@ -574,7 +556,7 @@ your other pam security modules. On my RedHat system, this was the modules reside in /usr/lib/security.

    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: 

    @@ -601,7 +583,7 @@ 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.
+template homedir.
 
    
 The /etc/pam.d/ftp file can be changed 
 to allow winbind ftp access in a manner similar to the
@@ -634,10 +616,10 @@ same way.  It now looks like this:
 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
+
    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 that my Domain users can logon both locally as well as telnet.The following are the changes that I made.You can customize the pam.conf file as per your requirements,but @@ -709,15 +691,15 @@ annoying double prompts for passwords.

    Now restart your Samba and try connecting through your application that you configured in the pam.conf. -

    Conclusion

    The winbind system, through the use of the Name Service +

    Conclusion

    The winbind system, through the use of the Name Service Switch, Pluggable Authentication Modules, 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

    Winbind has a number of limitations in its current + cost of running a mixed UNIX and NT network.

    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 and IRIX operating systems, although ports to other operating + the Linux, Solaris, AIX and IRIX operating systems, although ports to other operating systems are certainly possible. For such ports to be feasible, we require the C library of the target operating system to support the Name Service Switch and Pluggable Authentication @@ -729,4 +711,11 @@ configured in the pam.conf. containing this information is corrupted or destroyed.

    • Currently the winbind PAM module does not take into account possible workstation and logon time restrictions that may be been set for Windows NT users, this is - instead up to the PDC to enforce.

    Prev Up Next
    Chapter 20. Stackable VFS modules Home Chapter 22. Advanced Network Management
    + instead up to the PDC to enforce.

    NSCD Problem Warning

    Note

    + Do NOT under ANY circumstances run nscd on any system + on which winbind 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. +

    Prev Up Next
    Chapter 20. Stackable VFS modules Home Chapter 22. Advanced Network Management
    diff --git a/docs/htmldocs/winbindd.8.html b/docs/htmldocs/winbindd.8.html index c1a64d6a00..7b2d6e0261 100644 --- a/docs/htmldocs/winbindd.8.html +++ b/docs/htmldocs/winbindd.8.html @@ -1,5 +1,5 @@ winbindd

    Name

    winbindd — Name Service Switch daemon for resolving names - from NT servers

    Synopsis

    winbindd [-F] [-S] [-i] [-B] [-d <debug level>] [-s <smb config file>] [-n]

    DESCRIPTION

    This program is part of the Samba(7) suite.

    winbindd is a daemon that provides + from NT servers

    Synopsis

    winbindd [-F] [-S] [-i] [-Y] [-d <debug level>] [-s <smb config file>] [-n]

    DESCRIPTION

    This program is part of the Samba(7) suite.

    winbindd is a daemon that provides a service for the Name Service Switch capability that is present in most modern C libraries. The Name Service Switch allows user and system information to be obtained from different databases @@ -55,8 +55,7 @@ configuration details required by the server. The information in this file includes server-specific information such as what printcap file to use, as well as descriptions of all the services that the server is -to provide. See -smb.conf(5) for more information. +to provide. See smb.conf for more information. The default configuration file name is determined at compile time.

    -d|--debug=debuglevel

    debuglevel is an integer from 0 to 10. The default value if this parameter is @@ -70,10 +69,9 @@ amounts of log data, and should only be used when investigating a problem. Levels above 3 are designed for use only by developers and generate HUGE amounts of log data, most of which is extremely cryptic.

    Note that specifying this parameter here will -override the log -level parameter in the -smb.conf(5) file.

    -l|--logfile=logbasename

    File name for log/debug files. The extension -".client" will be appended. The log file is +override the log level parameter +in the smb.conf file.

    -l|--logfile=logbasename

    File name for log/debug files. The extension +".client" will be appended. The log file is never removed by the client.

    -h|--help

    Print a summary of command line options.

    -i

    Tells winbindd to not @@ -88,11 +86,10 @@ never removed by the client. slower. The results will however be more accurate, since results from the cache might not be up-to-date. This might also temporarily hang winbindd if the DC doesn't respond. -

    -B

    Dual daemon mode. This means winbindd will run - as 2 threads. The first will answer all requests from the cache, - thus making responses to clients faster. The other will - update the cache for the query that the first has just responded. - Advantage of this is that responses stay accurate and are faster. +

    -Y

    Single daemon mode. This means winbindd will run + as a single process (the mode of operation in Samba 2.2). Winbindd's + default behavior is to launch a child process that is responsible for + updating expired cache entries.

    NAME AND ID RESOLUTION

    Users and groups on a Windows NT server are assigned a relative id (rid) which is unique for the domain when the user or group is created. To convert the Windows NT user or group @@ -110,16 +107,16 @@ never removed by the client. determine which user and group ids correspond to Windows NT user and group rids.

    CONFIGURATION

    Configuration of the winbindd daemon is done through configuration parameters in the smb.conf(5) file. All parameters should be specified in the - [global] section of smb.conf.

    EXAMPLE SETUP

    To setup winbindd for user and group lookups plus + [global] section of smb.conf.

    EXAMPLE SETUP

    To setup winbindd for user and group lookups plus authentication from a domain controller use something like the following setup. This was tested on a RedHat 6.2 Linux box.

    In /etc/nsswitch.conf put the following: @@ -138,7 +135,7 @@ auth required /lib/security/pam_pwdb.so use_first_pass shadow nullok

    The next step is to join the domain. To do that use the net program like this:

    net join -S PDC -U Administrator

    The username after the -U can be any Domain user that has administrator privileges on the machine. - Substitute the name or IP of your PDC for "PDC".

    Next copy libnss_winbind.so to + Substitute the name or IP of your PDC for "PDC".

    Next copy libnss_winbind.so to /lib and pam_winbind.so to /lib/security. A symbolic link needs to be made from /lib/libnss_winbind.so to @@ -152,8 +149,8 @@ auth required /lib/security/pam_pwdb.so use_first_pass shadow nullok winbind cache time = 10 template shell = /bin/bash template homedir = /home/%D/%U - winbind uid = 10000-20000 - winbind gid = 10000-20000 + idmap uid = 10000-20000 + idmap gid = 10000-20000 workgroup = DOMAIN security = domain password server = * @@ -179,7 +176,7 @@ auth required /lib/security/pam_pwdb.so use_first_pass shadow nullok apply any parameter changes to the running version of winbindd. This signal also clears any cached user and group information. The list of other domains trusted - by winbindd is also reloaded.

    SIGUSR1

    The SIGUSR1 signal will cause + by winbindd is also reloaded.

    SIGUSR2

    The SIGUSR2 signal will cause winbindd to write status information to the winbind log file including information about the number of user and group ids allocated by winbindd.

    Log files are stored in the filename specified by the -- cgit