diff -u -r --new-file --exclude .svn --exclude CVS samba-3.3.10//docs/htmldocs/manpages/cifs.upcall.8.html samba-3.3.11//docs/htmldocs/manpages/cifs.upcall.8.html --- samba-3.3.10//docs/htmldocs/manpages/cifs.upcall.8.html 2010-01-14 11:20:06.000000000 +0100 +++ samba-3.3.11//docs/htmldocs/manpages/cifs.upcall.8.html 2010-02-22 16:53:37.000000000 +0100 @@ -1,13 +1,13 @@ -cifs.upcall

Name

cifs.upcall — Userspace upcall helper for Common Internet File System (CIFS)

Synopsis

cifs.upcall [--trust-dns|-t] [--version|-v] {keyid}

DESCRIPTION

This tool is part of the samba(7) suite.

cifs.upcall is a userspace helper program for the linux CIFS client +cifs.upcall

Name

cifs.upcall — Userspace upcall helper for Common Internet File System (CIFS)

Synopsis

cifs.upcall [--trust-dns|-t] [--version|-v] {keyid}

DESCRIPTION

This tool is part of the samba(7) suite.

cifs.upcall is a userspace helper program for the linux CIFS client filesystem. There are a number of activities that the kernel cannot easily do itself. This program is a callout program that does these things for the kernel and then returns the result.

cifs.upcall is generally intended to be run when the kernel calls request-key(8) for a particular key type. While it can be run directly from the command-line, it's not generally intended -to be run that way.

OPTIONS

-c

This option is deprecated and is currently ignored. +to be run that way.

OPTIONS

-c

This option is deprecated and is currently ignored.

--trust-dns|-t

With krb5 upcalls, the name used as the host portion of the service principal defaults to the hostname portion of the UNC. This option allows the upcall program to reverse resolve the network address of the server in order to get the hostname.

This is less secure than not trusting DNS. When using this option, it's possible that an attacker could get control of DNS and trick the client into mounting a different server altogether. It's preferable to instead add server principals to the KDC for every possible hostname, but this option exists for cases where that isn't possible. The default is to not trust reverse hostname lookups in this fashion.

--version|-v

Print version number and exit. -

CONFIGURATION FOR KEYCTL

cifs.upcall is designed to be called from the kernel via the +

CONFIGURATION FOR KEYCTL

cifs.upcall is designed to be called from the kernel via the request-key callout program. This requires that request-key be told where and how to call this program. The current cifs.upcall program handles two different key types: @@ -20,10 +20,10 @@ create dns_resolver * * /usr/local/sbin/cifs.upcall %k

See request-key.conf(5) for more info on each field. -

SEE ALSO

+

AUTHOR

Igor Mammedov wrote the cifs.upcall program.

Jeff Layton authored this manpage.

The maintainer of the Linux CIFS VFS is Steve French.

The Linux +

AUTHOR

Igor Mammedov wrote the cifs.upcall program.

Jeff Layton authored this manpage.

The maintainer of the Linux CIFS VFS is Steve French.

The Linux CIFS Mailing list is the preferred place to ask questions regarding these programs.

diff -u -r --new-file --exclude .svn --exclude CVS samba-3.3.10//docs/htmldocs/manpages/eventlogadm.8.html samba-3.3.11//docs/htmldocs/manpages/eventlogadm.8.html --- samba-3.3.10//docs/htmldocs/manpages/eventlogadm.8.html 2010-01-14 11:20:07.000000000 +0100 +++ samba-3.3.11//docs/htmldocs/manpages/eventlogadm.8.html 2010-02-22 16:53:37.000000000 +0100 @@ -1,4 +1,4 @@ -eventlogadm

Name

eventlogadm — push records into the Samba event log store

Synopsis

eventlogadm [-d] [-h] -o +eventlogadm

Name

eventlogadm — push records into the Samba event log store

Synopsis

eventlogadm [-d] [-h] -o addsource EVENTLOG SOURCENAME @@ -6,10 +6,10 @@

eventlogadm [-d] [-h] -o write EVENTLOG -

DESCRIPTION

This tool is part of the samba(1) suite.

eventlogadm is a filter that accepts +

DESCRIPTION

This tool is part of the samba(1) suite.

eventlogadm is a filter that accepts formatted event log records on standard input and writes them to the Samba event log store. Windows client can then manipulate - these record using the usual administration tools.

OPTIONS

-d

+ these record using the usual administration tools.

OPTIONS

-d

The -d option causes eventlogadm to emit debugging information.

@@ -31,56 +31,56 @@ event log store named by EVENTLOG.

-h

Print usage information. -

EVENTLOG RECORD FORMAT

For the write operation, eventlogadm +

EVENTLOG RECORD FORMAT

For the write operation, eventlogadm expects to be able to read structured records from standard input. These records are a sequence of lines, with the record key and data separated by a colon character. Records are separated - by at least one or more blank line.

The event log record field are:

  • + by at least one or more blank line.

    The event log record field are:

    • LEN - This field should be 0, since eventlogadm will calculate this value. -

    • +

    • RS1 - This must be the value 1699505740. -

    • +

    • RCN - This field should be 0. -

    • +

    • TMG - The time the eventlog record was generated; format is the number of seconds since 00:00:00 January 1, 1970, UTC. -

    • +

    • TMW - The time the eventlog record was written; format is the number of seconds since 00:00:00 January 1, 1970, UTC. -

    • +

    • EID - The eventlog ID. -

    • +

    • ETP - The event type -- one of "INFO", "ERROR", "WARNING", "AUDIT SUCCESS" or "AUDIT FAILURE". -

    • +

    • ECT - The event category; this depends on the message file. It is primarily used as a means of filtering in the eventlog viewer. -

    • +

    • RS2 - This field should be 0. -

    • +

    • CRN - This field should be 0. -

    • +

    • USL - This field should be 0. -

    • +

    • SRC - This field contains the source name associated with the event log. If a message file is used with an event log, there will be a registry entry for associating this source name with a message file DLL. -

    • +

    • SRN - The name of the machine on which the eventlog was generated. This is typically the host name. -

    • +

    • STR - The text associated with the eventlog. There may be more than one string in a record. -

    • +

    • DAT - This field should be left unset. -

EXAMPLES

An example of the record format accepted by eventlogadm:

+		

EXAMPLES

An example of the record format accepted by eventlogadm:

 	LEN: 0
 	RS1: 1699505740
 	RCN: 0
@@ -103,7 +103,7 @@
 	tail -f /var/log/messages | \\
 		my_program_to_parse_into_eventlog_records | \\
 	      	eventlogadm SystemLogEvents
-	

VERSION

This man page is correct for version 3.0.25 of the Samba suite.

AUTHOR

The original Samba software and related utilities were +

VERSION

This man page is correct for version 3.0.25 of the Samba suite.

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.

diff -u -r --new-file --exclude .svn --exclude CVS samba-3.3.10//docs/htmldocs/manpages/findsmb.1.html samba-3.3.11//docs/htmldocs/manpages/findsmb.1.html --- samba-3.3.10//docs/htmldocs/manpages/findsmb.1.html 2010-01-14 11:20:09.000000000 +0100 +++ samba-3.3.11//docs/htmldocs/manpages/findsmb.1.html 2010-02-22 16:53:36.000000000 +0100 @@ -1,12 +1,12 @@ -findsmb

Name

findsmb — list info about machines that respond to SMB - name queries on a subnet

Synopsis

findsmb [subnet broadcast address]

DESCRIPTION

This perl script is part of the samba(7) +findsmb

Name

findsmb — list info about machines that respond to SMB + name queries on a subnet

Synopsis

findsmb [subnet broadcast address]

DESCRIPTION

This perl script is part of the samba(7) suite.

findsmb is a perl script that prints out several pieces of information about machines on a subnet that respond to SMB name query requests. It uses nmblookup(1) and smbclient(1) to obtain this information. -

OPTIONS

-r

Controls whether findsmb takes +

OPTIONS

-r

Controls whether findsmb takes bugs in Windows95 into account when trying to find a Netbios name registered of the remote machine. This option is disabled by default because it is specific to Windows 95 and Windows 95 machines only. @@ -16,7 +16,7 @@ findsmb(1) is run. This value is passed to nmblookup(1) - as part of the -B option.

EXAMPLES

The output of findsmb lists the following + as part of the -B option.

EXAMPLES

The output of findsmb lists the following information for all machines that respond to the initial nmblookup for any name: IP address, NetBIOS name, Workgroup name, operating system, and SMB server version.

There will be a '+' in front of the workgroup name for @@ -48,10 +48,10 @@ 192.168.35.88 SCNT2 +[MVENGR] [Windows NT 4.0] [NT LAN Manager 4.0] 192.168.35.93 FROGSTAR-PC [MVENGR] [Windows 5.0] [Windows 2000 LAN Manager] 192.168.35.97 HERBNT1 *[HERB-NT] [Windows NT 4.0] [NT LAN Manager 4.0] -

VERSION

This man page is correct for version 3 of - the Samba suite.

SEE ALSO

nmbd(8), +

VERSION

This man page is correct for version 3 of + the Samba suite.

AUTHOR

The original Samba software and related utilities +

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 -u -r --new-file --exclude .svn --exclude CVS samba-3.3.10//docs/htmldocs/manpages/idmap_ad.8.html samba-3.3.11//docs/htmldocs/manpages/idmap_ad.8.html --- samba-3.3.10//docs/htmldocs/manpages/idmap_ad.8.html 2010-01-14 11:20:10.000000000 +0100 +++ samba-3.3.11//docs/htmldocs/manpages/idmap_ad.8.html 2010-02-22 16:53:37.000000000 +0100 @@ -1,10 +1,10 @@ -idmap_ad

Name

idmap_ad — Samba's idmap_ad Backend for Winbind

DESCRIPTION

The idmap_ad plugin provides a way for Winbind to read +idmap_ad

Name

idmap_ad — Samba's idmap_ad Backend for Winbind

DESCRIPTION

The idmap_ad plugin provides a way for Winbind to read id mappings from an AD server that uses RFC2307/SFU schema extensions. This module implements only the "idmap" API, and is READONLY. Mappings must be provided in advance by the administrator by adding the posixAccount/posixGroup classes and relative attribute/value pairs to the user and - group objects in the AD.

IDMAP OPTIONS

range = low - high

+ group objects in the AD.

IDMAP OPTIONS

range = low - high

Defines the available matching UID and GID range for which the backend is authoritative. Note that the range acts as a filter. If specified any UID or GID stored in AD that fall outside the @@ -16,7 +16,7 @@ Active Directory regarding user and group information. This can be either the RFC2307 schema support included in Windows 2003 R2 or the Service for Unix (SFU) schema. -

EXAMPLES

+

EXAMPLES

The following example shows how to retrieve idmappings from our principal and and trusted AD domains. If trusted domains are present id conflicts must be resolved beforehand, there is no @@ -32,7 +32,7 @@ idmap config CORP : backend = ad idmap config CORP : range = 1000-999999 -

AUTHOR

+

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 -u -r --new-file --exclude .svn --exclude CVS samba-3.3.10//docs/htmldocs/manpages/idmap_adex.8.html samba-3.3.11//docs/htmldocs/manpages/idmap_adex.8.html --- samba-3.3.10//docs/htmldocs/manpages/idmap_adex.8.html 2010-01-14 11:20:11.000000000 +0100 +++ samba-3.3.11//docs/htmldocs/manpages/idmap_adex.8.html 2010-02-22 16:53:37.000000000 +0100 @@ -1,4 +1,4 @@ -idmap_adex

Name

idmap_adex — Samba's idmap_adex Backend for Winbind

DESCRIPTION

+idmap_adex

Name

idmap_adex — Samba's idmap_adex Backend for Winbind

DESCRIPTION

The idmap_adex plugin provides a way for Winbind to read id mappings from an AD server that uses RFC2307 schema extensions. This module implements both the idmap and nss_info @@ -13,7 +13,7 @@ attributes to the partial attribute set of the forest global catalog servers. This can be done using the Active Directory Schema Management MMC plugin (schmmgmt.dll). -

NSS_INFO

+

NSS_INFO

The nss_info plugin supports reading the unixHomeDirectory, gidNumber, loginShell, and uidNumber attributes from the user object and the gidNumber attribute from the group object to @@ -25,7 +25,7 @@ Username aliases are implement by setting the uid attribute on the user object. While group name aliases are implemented by reading the displayname attribute from the group object. -

EXAMPLES

+

EXAMPLES

The following example shows how to retrieve idmappings and NSS data from our principal and trusted AD domains.

@@ -36,7 +36,7 @@
 
 	winbind nss info = adex
 	winbind normalize names = yes
-	

AUTHOR

+

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 -u -r --new-file --exclude .svn --exclude CVS samba-3.3.10//docs/htmldocs/manpages/idmap_hash.8.html samba-3.3.11//docs/htmldocs/manpages/idmap_hash.8.html --- samba-3.3.10//docs/htmldocs/manpages/idmap_hash.8.html 2010-01-14 11:20:12.000000000 +0100 +++ samba-3.3.11//docs/htmldocs/manpages/idmap_hash.8.html 2010-02-22 16:53:37.000000000 +0100 @@ -1,16 +1,16 @@ -idmap_hash

Name

idmap_hash — Samba's idmap_hash Backend for Winbind

DESCRIPTION

The idmap_hash plugin implements a hashing algorithm used +idmap_hash

Name

idmap_hash — Samba's idmap_hash Backend for Winbind

DESCRIPTION

The idmap_hash plugin implements a hashing algorithm used map SIDs for domain users and groups to a 31-bit uid and gid. This plugin also implements the nss_info API and can be used to support a local name mapping files if enabled via the "winbind normlaize names" and "winbind nss info" parameters in smb.conf. -

IDMAP OPTIONS

name_map

+

IDMAP OPTIONS

name_map

Specifies the absolute path to the name mapping file used by the nss_info API. Entries in the file are of the form "unix name = qualified domain name". Mapping of both user and group names is supported. -

EXAMPLES

The following example utilizes the idmap_hash plugin for +

EXAMPLES

The following example utilizes the idmap_hash plugin for the idmap and nss_info information.

 	[global]
@@ -21,7 +21,7 @@
 	winbind nss info = hash
 	winbind normalize names = yes
 	idmap_hash:name_map = /etc/samba/name_map.cfg
-	

AUTHOR

+

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 -u -r --new-file --exclude .svn --exclude CVS samba-3.3.10//docs/htmldocs/manpages/idmap_ldap.8.html samba-3.3.11//docs/htmldocs/manpages/idmap_ldap.8.html --- samba-3.3.10//docs/htmldocs/manpages/idmap_ldap.8.html 2010-01-14 11:20:14.000000000 +0100 +++ samba-3.3.11//docs/htmldocs/manpages/idmap_ldap.8.html 2010-02-22 16:53:37.000000000 +0100 @@ -1,4 +1,4 @@ -idmap_ldap

Name

idmap_ldap — Samba's idmap_ldap Backend for Winbind

DESCRIPTION

The idmap_ldap plugin provides a means for Winbind to +idmap_ldap

Name

idmap_ldap — Samba's idmap_ldap Backend for Winbind

DESCRIPTION

The idmap_ldap plugin provides a means for Winbind to store and retrieve SID/uid/gid mapping tables in an LDAP directory service.

@@ -19,7 +19,7 @@ any explicitly configured domain with idmap backend ldap should have the same range as the default range, since it needs to use the global uid / gid allocator. See the example below. -

IDMAP OPTIONS

ldap_base_dn = DN

+

IDMAP OPTIONS

ldap_base_dn = DN

Defines the directory base suffix to use when searching for SID/uid/gid mapping entries. If not defined, idmap_ldap will default to using the "ldap idmap suffix" option from smb.conf. @@ -36,7 +36,7 @@ If the parameter is absent, Winbind fails over to use the "idmap uid" and "idmap gid" options from smb.conf. -

IDMAP ALLOC OPTIONS

ldap_base_dn = DN

+

IDMAP ALLOC OPTIONS

ldap_base_dn = DN

Defines the directory base suffix under which new SID/uid/gid mapping entries should be stored. If not defined, idmap_ldap will default to using the "ldap idmap suffix" option from smb.conf. @@ -47,7 +47,7 @@ Specifies the LDAP server to which modify/add/delete requests should be sent. If not defined, idmap_ldap will assume that ldap://localhost/ should be used. -

EXAMPLES

+

EXAMPLES

The follow sets of a LDAP configuration which uses two LDAP directories, one for storing the ID mappings and one for retrieving new IDs. @@ -60,12 +60,12 @@ idmap alloc backend = ldap idmap alloc config : ldap_url = ldap://id-master/ idmap alloc config : ldap_base_dn = ou=idmap,dc=example,dc=com -

NOTE

In order to use authentication against ldap servers you may +

NOTE

In order to use authentication against ldap servers you may need to provide a DN and a password. To avoid exposing the password in plain text in the configuration file we store it into a security store. The "net idmap " command is used to store a secret for the DN specified in a specific idmap domain. -

AUTHOR

+

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 -u -r --new-file --exclude .svn --exclude CVS samba-3.3.10//docs/htmldocs/manpages/idmap_nss.8.html samba-3.3.11//docs/htmldocs/manpages/idmap_nss.8.html --- samba-3.3.10//docs/htmldocs/manpages/idmap_nss.8.html 2010-01-14 11:20:15.000000000 +0100 +++ samba-3.3.11//docs/htmldocs/manpages/idmap_nss.8.html 2010-02-22 16:53:37.000000000 +0100 @@ -1,10 +1,10 @@ -idmap_nss

Name

idmap_nss — Samba's idmap_nss Backend for Winbind

DESCRIPTION

The idmap_nss plugin provides a means to map Unix users and groups +idmap_nss

Name

idmap_nss — Samba's idmap_nss Backend for Winbind

DESCRIPTION

The idmap_nss plugin provides a means to map Unix users and groups to Windows accounts and obseletes the "winbind trusted domains only" smb.conf option. This provides a simple means of ensuring that the SID for a Unix user named jsmith is reported as the one assigned to DOMAIN\jsmith which is necessary for reporting ACLs on files and printers stored on a Samba member server. -

EXAMPLES

+

EXAMPLES

This example shows how to use idmap_nss to check the local accounts for its own domain while using allocation to create new mappings for trusted domains

@@ -15,7 +15,7 @@
 
 	idmap config SAMBA : backend  = nss
 	idmap config SAMBA : range = 1000-999999
-	

AUTHOR

+

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 -u -r --new-file --exclude .svn --exclude CVS samba-3.3.10//docs/htmldocs/manpages/idmap_rid.8.html samba-3.3.11//docs/htmldocs/manpages/idmap_rid.8.html --- samba-3.3.10//docs/htmldocs/manpages/idmap_rid.8.html 2010-01-14 11:20:16.000000000 +0100 +++ samba-3.3.11//docs/htmldocs/manpages/idmap_rid.8.html 2010-02-22 16:53:37.000000000 +0100 @@ -1,6 +1,6 @@ -idmap_rid

Name

idmap_rid — Samba's idmap_rid Backend for Winbind

DESCRIPTION

The idmap_rid backend provides a way to use an algorithmic +idmap_rid

Name

idmap_rid — Samba's idmap_rid Backend for Winbind

DESCRIPTION

The idmap_rid backend provides a way to use an algorithmic mapping scheme to map UIDs/GIDs and SIDs. No database is required - in this case as the mapping is deterministic.

IDMAP OPTIONS

range = low - high

+ in this case as the mapping is deterministic.

IDMAP OPTIONS

range = low - high

Defines the available matching uid and gid range for which the backend is authoritative. Note that the range acts as a filter. If algorithmically determined UID or GID fall outside the @@ -15,7 +15,7 @@ ID = RID - BASE_RID + LOW RANGE ID.

Use of this parameter is deprecated. -

EXAMPLES

This example shows how to configure a domain with idmap_rid

+		

EXAMPLES

This example shows how to configure a domain with idmap_rid

 	[global]
 	idmap backend = tdb
 	idmap uid = 1000000-1999999
@@ -23,7 +23,7 @@
 
 	idmap config TRUSTED : backend  = rid
 	idmap config TRUSTED : range    = 50000 - 99999
-	

AUTHOR

+

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 -u -r --new-file --exclude .svn --exclude CVS samba-3.3.10//docs/htmldocs/manpages/idmap_tdb2.8.html samba-3.3.11//docs/htmldocs/manpages/idmap_tdb2.8.html --- samba-3.3.10//docs/htmldocs/manpages/idmap_tdb2.8.html 2010-01-14 11:20:17.000000000 +0100 +++ samba-3.3.11//docs/htmldocs/manpages/idmap_tdb2.8.html 2010-02-22 16:53:37.000000000 +0100 @@ -1,4 +1,4 @@ -idmap_tdb2

Name

idmap_tdb2 — Samba's idmap_tdb2 Backend for Winbind

DESCRIPTION

+idmap_tdb2

Name

idmap_tdb2 — Samba's idmap_tdb2 Backend for Winbind

DESCRIPTION

The idmap_tdb2 plugin is a substitute for the default idmap_tdb backend used by winbindd for storing SID/uid/gid mapping tables in clustered environments with Samba and CTDB. @@ -20,13 +20,13 @@ any explicitly configured domain with idmap backend tdb2 should have the same range as the default range, since it needs to use the global uid / gid allocator. See the example below. -

IDMAP OPTIONS

range = low - high

+

IDMAP OPTIONS

range = low - high

Defines the available matching uid and gid range for which the backend is authoritative. If the parameter is absent, Winbind fails over to use the "idmap uid" and "idmap gid" options from smb.conf. -

IDMAP SCRIPT

+

IDMAP SCRIPT

The tdb2 idmap backend supports a script for performing id mappings through the smb.conf option idmap : script. The script should accept the following command line options. @@ -47,7 +47,7 @@ that can be passed in for SID to Unix ID mapping, since otherwise SIDs unmapped by the script might get mapped to IDs that had previously been mapped by the script. -

EXAMPLES

+

EXAMPLES

This example shows how tdb2 is used as a the default idmap backend. It configures the idmap range through the global options for all domains encountered. This same range is used for uid/gid allocation. @@ -56,7 +56,7 @@ idmap backend = tdb2 idmap uid = 1000000-2000000 idmap gid = 1000000-2000000 -

AUTHOR

+

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 -u -r --new-file --exclude .svn --exclude CVS samba-3.3.10//docs/htmldocs/manpages/idmap_tdb.8.html samba-3.3.11//docs/htmldocs/manpages/idmap_tdb.8.html --- samba-3.3.10//docs/htmldocs/manpages/idmap_tdb.8.html 2010-01-14 11:20:19.000000000 +0100 +++ samba-3.3.11//docs/htmldocs/manpages/idmap_tdb.8.html 2010-02-22 16:53:37.000000000 +0100 @@ -1,4 +1,4 @@ -idmap_tdb

Name

idmap_tdb — Samba's idmap_tdb Backend for Winbind

DESCRIPTION

+idmap_tdb

Name

idmap_tdb — Samba's idmap_tdb Backend for Winbind

DESCRIPTION

The idmap_tdb plugin is the default backend used by winbindd for storing SID/uid/gid mapping tables.

@@ -19,13 +19,13 @@ any explicitly configured domain with idmap backend tdb should have the same range as the default range, since it needs to use the global uid / gid allocator. See the example below. -

IDMAP OPTIONS

range = low - high

+

IDMAP OPTIONS

range = low - high

Defines the available matching uid and gid range for which the backend is authoritative. If the parameter is absent, Winbind fails over to use the "idmap uid" and "idmap gid" options from smb.conf. -

EXAMPLES

+

EXAMPLES

This example shows how tdb is used as a the default idmap backend. It configures the idmap range through the global options for all domains encountered. This same range is used for uid/gid allocation. @@ -53,7 +53,7 @@ idmap config DOM1 : backend = tdb idmap config DOM1 : range = 1000000-2000000 -

AUTHOR

+

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 -u -r --new-file --exclude .svn --exclude CVS samba-3.3.10//docs/htmldocs/manpages/index.html samba-3.3.11//docs/htmldocs/manpages/index.html --- samba-3.3.10//docs/htmldocs/manpages/index.html 2010-01-14 11:23:42.000000000 +0100 +++ samba-3.3.11//docs/htmldocs/manpages/index.html 2010-02-22 16:53:36.000000000 +0100 @@ -1,4 +1,4 @@ -


cifs.upcall(8)

Userspace upcall helper for Common Internet File System (CIFS) +


cifs.upcall(8)

Userspace upcall helper for Common Internet File System (CIFS)

eventlogadm(8)

push records into the Samba event log store

findsmb(1)

list info about machines that respond to SMB name queries on a subnet diff -u -r --new-file --exclude .svn --exclude CVS samba-3.3.10//docs/htmldocs/manpages/ldb.3.html samba-3.3.11//docs/htmldocs/manpages/ldb.3.html --- samba-3.3.10//docs/htmldocs/manpages/ldb.3.html 2010-01-14 11:20:20.000000000 +0100 +++ samba-3.3.11//docs/htmldocs/manpages/ldb.3.html 2010-02-22 16:53:37.000000000 +0100 @@ -1,4 +1,4 @@ -ldb

Name

ldbThe Samba Project — A light-weight database library

Synopsis

#include <ldb.h>

description

+ldb

Name

ldb

The Samba Project

— A light-weight database library

Synopsis

#include <ldb.h>

description

ldb is a light weight embedded database library and API. With a programming interface that is very similar to LDAP, ldb can store its data either in a tdb(3) database or in a real LDAP database. @@ -34,97 +34,97 @@ for ldbsearch(1) and ldbedit(1), and experimenting with a local database. Then I suggest you look at the ldb_connect(3) and ldb_search(3) manual pages. -

TOOLS

  • +

TOOLS

  • ldbsearch(1) - command line ldb search utility -

  • +

  • ldbedit(1) - edit all or part of a ldb database using your favourite editor -

  • +

  • ldbadd(1) - add records to a ldb database using LDIF formatted input -

  • +

  • ldbdel(1) - delete records from a ldb database -

  • +

  • ldbmodify(1) - modify records in a ldb database using LDIF formatted input -

FUNCTIONS

  • +

FUNCTIONS

  • ldb_connect(3) - connect to a ldb backend -

  • +

  • ldb_search(3) - perform a database search -

  • +

  • ldb_add(3) - add a record to the database -

  • +

  • ldb_delete(3) - delete a record from the database -

  • +

  • ldb_modify(3) - modify a record in the database -

  • +

  • ldb_errstring(3) - retrieve extended error information from the last operation -

  • +

  • ldb_ldif_write(3) - write a LDIF formatted message -

  • +

  • ldb_ldif_write_file(3) - write a LDIF formatted message to a file -

  • +

  • ldb_ldif_read(3) - read a LDIF formatted message -

  • +

  • ldb_ldif_read_free(3) - free the result of a ldb_ldif_read() -

  • +

  • ldb_ldif_read_file(3) - read a LDIF message from a file -

  • +

  • ldb_ldif_read_string(3) - read a LDIF message from a string -

  • +

  • ldb_msg_find_element(3) - find an element in a ldb_message -

  • +

  • ldb_val_equal_exact(3) - compare two ldb_val structures -

  • +

  • ldb_msg_find_val(3) - find an element by value -

  • +

  • ldb_msg_add_empty(3) - add an empty message element to a ldb_message -

  • +

  • ldb_msg_add(3) - add a non-empty message element to a ldb_message -

  • +

  • ldb_msg_element_compare(3) - compare two ldb_message_element structures -

  • +

  • ldb_msg_find_int(3) - return an integer value from a ldb_message -

  • +

  • ldb_msg_find_uint(3) - return an unsigned integer value from a ldb_message -

  • +

  • ldb_msg_find_double(3) - return a double value from a ldb_message -

  • +

  • ldb_msg_find_string(3) - return a string value from a ldb_message -

  • +

  • ldb_set_alloc(3) - set the memory allocation function to be used by ldb -

  • +

  • ldb_set_debug(3) - set a debug handler to be used by ldb -

  • +

  • ldb_set_debug_stderr(3) - set a debug handler for stderr output -

Author

+

Author

ldb was written by Andrew Tridgell.

diff -u -r --new-file --exclude .svn --exclude CVS samba-3.3.10//docs/htmldocs/manpages/ldbadd.1.html samba-3.3.11//docs/htmldocs/manpages/ldbadd.1.html --- samba-3.3.10//docs/htmldocs/manpages/ldbadd.1.html 2010-01-14 11:20:21.000000000 +0100 +++ samba-3.3.11//docs/htmldocs/manpages/ldbadd.1.html 2010-02-22 16:53:36.000000000 +0100 @@ -1,13 +1,13 @@ -ldbadd

Name

ldbadd — Command-line utility for adding records to an LDB

Synopsis

ldbadd [-h] [-H LDB-URL] [ldif-file1] [ldif-file2] [...]

DESCRIPTION

ldbadd adds records to an ldb(7) database. It reads +ldbadd

Name

ldbadd — Command-line utility for adding records to an LDB

Synopsis

ldbadd [-h] [-H LDB-URL] [ldif-file1] [ldif-file2] [...]

DESCRIPTION

ldbadd adds records to an ldb(7) database. It reads the ldif(5) files specified on the command line and adds the records from these files to the LDB database, which is specified by the -H option or the LDB_URL environment variable.

If - is specified as a ldb file, the ldif input is read from - standard input.

OPTIONS

-h

+ standard input.

OPTIONS

-h

Show list of available options.

-H <ldb-url>

LDB URL to connect to. See ldb(7) for details. -

ENVIRONMENT

LDB_URL

LDB URL to connect to (can be overrided by using the - -H command-line option.)

VERSION

This man page is correct for version 4.0 of the Samba suite.

SEE ALSO

ldb(7), ldbmodify, ldbdel, ldif(5)

AUTHOR

ldb was written by +

ENVIRONMENT

LDB_URL

LDB URL to connect to (can be overrided by using the + -H command-line option.)

VERSION

This man page is correct for version 4.0 of the Samba suite.

SEE ALSO

ldb(7), ldbmodify, ldbdel, ldif(5)

AUTHOR

ldb was written by Andrew Tridgell.

If you wish to report a problem or make a suggestion then please see diff -u -r --new-file --exclude .svn --exclude CVS samba-3.3.10//docs/htmldocs/manpages/ldbdel.1.html samba-3.3.11//docs/htmldocs/manpages/ldbdel.1.html --- samba-3.3.10//docs/htmldocs/manpages/ldbdel.1.html 2010-01-14 11:20:23.000000000 +0100 +++ samba-3.3.11//docs/htmldocs/manpages/ldbdel.1.html 2010-02-22 16:53:37.000000000 +0100 @@ -1,12 +1,12 @@ -ldbdel

Name

ldbdel — Command-line program for deleting LDB records

Synopsis

ldbdel [-h] [-H LDB-URL] [dn] [...]

DESCRIPTION

ldbdel deletes records from an ldb(7) database. +ldbdel

Name

ldbdel — Command-line program for deleting LDB records

Synopsis

ldbdel [-h] [-H LDB-URL] [dn] [...]

DESCRIPTION

ldbdel deletes records from an ldb(7) database. It deletes the records identified by the dn's specified on the command-line.

ldbdel uses either the database that is specified with the -H option or the database specified by the LDB_URL environment - variable.

OPTIONS

-h

+ variable.

OPTIONS

-h

Show list of available options.

-H <ldb-url>

LDB URL to connect to. See ldb(7) for details. -

ENVIRONMENT

LDB_URL

LDB URL to connect to (can be overrided by using the - -H command-line option.)

VERSION

This man page is correct for version 4.0 of the Samba suite.

SEE ALSO

ldb(7), ldbmodify, ldbadd, ldif(5)

AUTHOR

ldb was written by +

ENVIRONMENT

LDB_URL

LDB URL to connect to (can be overrided by using the + -H command-line option.)

VERSION

This man page is correct for version 4.0 of the Samba suite.

SEE ALSO

ldb(7), ldbmodify, ldbadd, ldif(5)

AUTHOR

ldb was written by Andrew Tridgell.

If you wish to report a problem or make a suggestion then please see diff -u -r --new-file --exclude .svn --exclude CVS samba-3.3.10//docs/htmldocs/manpages/ldbedit.1.html samba-3.3.11//docs/htmldocs/manpages/ldbedit.1.html --- samba-3.3.10//docs/htmldocs/manpages/ldbedit.1.html 2010-01-14 11:20:24.000000000 +0100 +++ samba-3.3.11//docs/htmldocs/manpages/ldbedit.1.html 2010-02-22 16:53:37.000000000 +0100 @@ -1,8 +1,8 @@ -ldbedit

Name

ldbedit — Edit LDB databases using your preferred editor

Synopsis

ldbedit [-?] [--usage] [-s base|one|sub] [-b basedn] [-a] [-e editor] [-H LDB-URL] [expression] [attributes...]

DESCRIPTION

ldbedit is a utility that allows you to edit LDB entries (in +ldbedit

Name

ldbedit — Edit LDB databases using your preferred editor

Synopsis

ldbedit [-?] [--usage] [-s base|one|sub] [-b basedn] [-a] [-e editor] [-H LDB-URL] [expression] [attributes...]

DESCRIPTION

ldbedit is a utility that allows you to edit LDB entries (in tdb files, sqlite files or LDAP servers) using your preferred editor. ldbedit generates an LDIF file based on your query, allows you to edit the LDIF, and then merges that LDIF back into the LDB backend. -

OPTIONS

-?, --help

+

OPTIONS

-?, --help

Show list of available options, and a phrase describing what that option does.

--usage

@@ -34,14 +34,14 @@ operations that are being performed. Without this option, ldbedit will only provide a summary change line. -

ENVIRONMENT

LDB_URL

LDB URL to connect to. This can be +

ENVIRONMENT

LDB_URL

LDB URL to connect to. This can be overridden by using the -H command-line option.)

VISUAL and EDITOR

Environment variables used to determine what editor to use. VISUAL takes precedence over EDITOR, and both are overridden by the -e command-line option. -

VERSION

This man page is correct for version 4.0 of the Samba suite.

SEE ALSO

ldb(7), ldbmodify(1), ldbdel(1), ldif(5), vi(1)

AUTHOR

+

VERSION

This man page is correct for version 4.0 of the Samba suite.

SEE ALSO

ldb(7), ldbmodify(1), ldbdel(1), ldif(5), vi(1)

AUTHOR

ldb was written by Andrew Tridgell.

diff -u -r --new-file --exclude .svn --exclude CVS samba-3.3.10//docs/htmldocs/manpages/ldbmodify.1.html samba-3.3.11//docs/htmldocs/manpages/ldbmodify.1.html --- samba-3.3.10//docs/htmldocs/manpages/ldbmodify.1.html 2010-01-14 11:20:25.000000000 +0100 +++ samba-3.3.11//docs/htmldocs/manpages/ldbmodify.1.html 2010-02-22 16:53:36.000000000 +0100 @@ -1,11 +1,11 @@ -ldbmodify

Name

ldbmodify — Modify records in a LDB database

Synopsis

ldbmodify [-H LDB-URL] [ldif-file]

DESCRIPTION

+ldbmodify

Name

ldbmodify — Modify records in a LDB database

Synopsis

ldbmodify [-H LDB-URL] [ldif-file]

DESCRIPTION

ldbmodify changes, adds and deletes records in a LDB database. The changes that should be made to the LDB database are read from the specified LDIF-file. If - is specified as the filename, input is read from stdin. -

For now, see ldapmodify(1) for details on the LDIF file format.

OPTIONS

-H <ldb-url>

+

For now, see ldapmodify(1) for details on the LDIF file format.

OPTIONS

-H <ldb-url>

LDB URL to connect to. See ldb(7) for details. -

ENVIRONMENT

LDB_URL

LDB URL to connect to (can be overrided by using the - -H command-line option.)

VERSION

This man page is correct for version 4.0 of the Samba suite.

SEE ALSO

ldb(7), ldbedit

AUTHOR

ldb was written by +

ENVIRONMENT

LDB_URL

LDB URL to connect to (can be overrided by using the + -H command-line option.)

VERSION

This man page is correct for version 4.0 of the Samba suite.

SEE ALSO

ldb(7), ldbedit

AUTHOR

ldb was written by Andrew Tridgell.

If you wish to report a problem or make a suggestion then please see diff -u -r --new-file --exclude .svn --exclude CVS samba-3.3.10//docs/htmldocs/manpages/ldbrename.1.html samba-3.3.11//docs/htmldocs/manpages/ldbrename.1.html --- samba-3.3.10//docs/htmldocs/manpages/ldbrename.1.html 2010-01-14 11:20:27.000000000 +0100 +++ samba-3.3.11//docs/htmldocs/manpages/ldbrename.1.html 2010-02-22 16:53:36.000000000 +0100 @@ -1,13 +1,13 @@ -ldbrename

Name

ldbrename — Edit LDB databases using your favorite editor

Synopsis

ldbrename [-h] [-o options] {olddn} {newdb}

DESCRIPTION

ldbrename is a utility that allows you to rename trees in +ldbrename

Name

ldbrename — Edit LDB databases using your favorite editor

Synopsis

ldbrename [-h] [-o options] {olddn} {newdb}

DESCRIPTION

ldbrename is a utility that allows you to rename trees in an LDB database based by DN. This utility takes two arguments: the original DN name of the top element and the DN to change it to. -

OPTIONS

-h

+

OPTIONS

-h

Show list of available options.

-H <ldb-url>

LDB URL to connect to. See ldb(7) for details.

-o options

Extra ldb options, such as - modules.

ENVIRONMENT

LDB_URL

LDB URL to connect to (can be overrided by using the - -H command-line option.)

VERSION

This man page is correct for version 4.0 of the Samba suite.

SEE ALSO

ldb(7), ldbmodify, ldbdel, ldif(5)

AUTHOR

ldb was written by + modules.

ENVIRONMENT

LDB_URL

LDB URL to connect to (can be overrided by using the + -H command-line option.)

VERSION

This man page is correct for version 4.0 of the Samba suite.

SEE ALSO

ldb(7), ldbmodify, ldbdel, ldif(5)

AUTHOR

ldb was written by Andrew Tridgell.

If you wish to report a problem or make a suggestion then please see diff -u -r --new-file --exclude .svn --exclude CVS samba-3.3.10//docs/htmldocs/manpages/ldbsearch.1.html samba-3.3.11//docs/htmldocs/manpages/ldbsearch.1.html --- samba-3.3.10//docs/htmldocs/manpages/ldbsearch.1.html 2010-01-14 11:20:28.000000000 +0100 +++ samba-3.3.11//docs/htmldocs/manpages/ldbsearch.1.html 2010-02-22 16:53:37.000000000 +0100 @@ -1,12 +1,12 @@ -ldbsearch

Name

ldbsearch — Search for records in a LDB database

Synopsis

ldbsearch [-h] [-s base|one|sub] [-b basedn] [-i] [-H LDB-URL] [expression] [attributes]

DESCRIPTION

ldbsearch searches a LDB database for records matching the +ldbsearch

Name

ldbsearch — Search for records in a LDB database

Synopsis

ldbsearch [-h] [-s base|one|sub] [-b basedn] [-i] [-H LDB-URL] [expression] [attributes]

DESCRIPTION

ldbsearch searches a LDB database for records matching the specified expression (see the ldapsearch(1) manpage for a description of the expression format). For each record, the specified attributes are printed. -

OPTIONS

-h

+

OPTIONS

-h

Show list of available options.

-H <ldb-url>

LDB URL to connect to. See ldb(7) for details. -

-s one|sub|base

Search scope to use. One-level, subtree or base.

-i

Read search expressions from stdin.

-b basedn

Specify Base DN to use.

ENVIRONMENT

LDB_URL

LDB URL to connect to (can be overrided by using the - -H command-line option.)

VERSION

This man page is correct for version 4.0 of the Samba suite.

SEE ALSO

ldb(7), ldbedit(1)

AUTHOR

ldb was written by +

-s one|sub|base

Search scope to use. One-level, subtree or base.

-i

Read search expressions from stdin.

-b basedn

Specify Base DN to use.

ENVIRONMENT

LDB_URL

LDB URL to connect to (can be overrided by using the + -H command-line option.)

VERSION

This man page is correct for version 4.0 of the Samba suite.

SEE ALSO

ldb(7), ldbedit(1)

AUTHOR

ldb was written by Andrew Tridgell.

If you wish to report a problem or make a suggestion then please see diff -u -r --new-file --exclude .svn --exclude CVS samba-3.3.10//docs/htmldocs/manpages/libsmbclient.7.html samba-3.3.11//docs/htmldocs/manpages/libsmbclient.7.html --- samba-3.3.10//docs/htmldocs/manpages/libsmbclient.7.html 2010-01-14 11:20:29.000000000 +0100 +++ samba-3.3.11//docs/htmldocs/manpages/libsmbclient.7.html 2010-02-22 16:53:37.000000000 +0100 @@ -1,8 +1,8 @@ -libsmbclient

Name

libsmbclient — An extension library for browsers and that can be used as a generic browsing API.

Synopsis

+libsmbclient

Name

libsmbclient — An extension library for browsers and that can be used as a generic browsing API.

Synopsis

Browser URL: smb://[[[domain:]user[:password@]]server[/share[/path[/file]]]] [?options] -

DESCRIPTION

+

DESCRIPTION

This tool is part of the samba(7) suite.

libsmbclient is a library toolset that permits applications to manipulate CIFS/SMB network @@ -14,7 +14,7 @@ libsmbclient can not be used directly from the command line, instead it provides an extension of the capabilities of tools such as file managers and browsers. This man page describes the configuration options for this tool so that the user may obtain greatest utility of use. -

OPTIONS

+

OPTIONS

What the URLs mean:

smb://

Shows all workgroups or domains that are visible in the network. The behavior matches @@ -46,11 +46,11 @@ libsmbclient will check the users shell environment for the USER parameter and will use its value when if the user parameter was not included in the URL. -

PROGRAMMERS GUIDE

+

PROGRAMMERS GUIDE

Watch this space for future updates. -

VERSION

+

VERSION

This man page is correct for version 3 of the Samba suite. -

AUTHOR

+

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. diff -u -r --new-file --exclude .svn --exclude CVS samba-3.3.10//docs/htmldocs/manpages/lmhosts.5.html samba-3.3.11//docs/htmldocs/manpages/lmhosts.5.html --- samba-3.3.10//docs/htmldocs/manpages/lmhosts.5.html 2010-01-14 11:20:31.000000000 +0100 +++ samba-3.3.11//docs/htmldocs/manpages/lmhosts.5.html 2010-02-22 16:53:36.000000000 +0100 @@ -1,11 +1,11 @@ -lmhosts

Name

lmhosts — The Samba NetBIOS hosts file

Synopsis

lmhosts is the samba(7) NetBIOS name to IP address mapping file.

DESCRIPTION

This file is part of the samba(7) suite.

lmhosts is the Samba +lmhosts

Name

lmhosts — The Samba NetBIOS hosts file

Synopsis

lmhosts is the samba(7) NetBIOS name to IP address mapping file.

DESCRIPTION

This file is part of the samba(7) suite.

lmhosts is the Samba NetBIOS name to IP address mapping file. It is very similar to the /etc/hosts file format, except that the hostname component must correspond - to the NetBIOS naming format.

FILE FORMAT

It is an ASCII file containing one line for NetBIOS name. + to the NetBIOS naming format.

FILE FORMAT

It is an ASCII file containing one line for NetBIOS name. The two fields on each line are separated from each other by white space. Any entry beginning with '#' is ignored. Each line - in the lmhosts file contains the following information:

  • IP Address - in dotted decimal format.

  • NetBIOS Name - This name format is a + in the lmhosts file contains the following information:

    • IP Address - in dotted decimal format.

    • NetBIOS Name - This name format is a maximum fifteen character host name, with an optional trailing '#' character followed by the NetBIOS name type as two hexadecimal digits.

      If the trailing '#' is omitted then the given IP @@ -25,10 +25,10 @@ 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.

    FILES

    lmhosts is loaded from the configuration directory. This is + is in the same directory as the smb.conf(5) file.

    FILES

    lmhosts is loaded from the configuration directory. This is usually /etc/samba or /usr/local/samba/lib. -

    VERSION

    This man page is correct for version 3 of the Samba suite.

    AUTHOR

    The original Samba software and related utilities +

    VERSION

    This man page is correct for version 3 of the Samba suite.

    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 -u -r --new-file --exclude .svn --exclude CVS samba-3.3.10//docs/htmldocs/manpages/log2pcap.1.html samba-3.3.11//docs/htmldocs/manpages/log2pcap.1.html --- samba-3.3.10//docs/htmldocs/manpages/log2pcap.1.html 2010-01-14 11:20:32.000000000 +0100 +++ samba-3.3.11//docs/htmldocs/manpages/log2pcap.1.html 2010-02-22 16:53:37.000000000 +0100 @@ -1,11 +1,11 @@ -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 +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 +

    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 @@ -17,13 +17,13 @@ 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:

    +

    EXAMPLES

    Extract all network traffic from all samba log files:

     			$ log2pcap < /var/log/* > 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 of the Samba suite.

    BUGS

    Only SMB data is extracted from the samba logs, no LDAP, +

    VERSION

    This man page is correct for version 3 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.

    AUTHOR

    The original Samba software and related utilities + checksum.

    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 -u -r --new-file --exclude .svn --exclude CVS samba-3.3.10//docs/htmldocs/manpages/mount.cifs.8.html samba-3.3.11//docs/htmldocs/manpages/mount.cifs.8.html --- samba-3.3.10//docs/htmldocs/manpages/mount.cifs.8.html 2010-01-14 11:20:33.000000000 +0100 +++ samba-3.3.11//docs/htmldocs/manpages/mount.cifs.8.html 2010-02-22 16:53:37.000000000 +0100 @@ -1,4 +1,4 @@ -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 +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 @@ -23,12 +23,12 @@

    mount.cifs causes the cifs vfs to launch a thread named cifsd. After mounting it keeps running until the mounted resource is unmounted (usually via the umount utility). -

    OPTIONS

    user=arg

    specifies the username to connect as. If +

    OPTIONS

    user=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 "workgroup/user" or "workgroup/user%password" to allow the password and workgroup to be specified as part of the username. -

    Note

    +

    Note

    The cifs vfs accepts the parameter user=, or for users familiar with smbfs it accepts the longer form of the parameter username=. Similarly the longer smbfs style parameter names may be accepted as synonyms for the shorter cifs parameters pass=,dom= and cred=.

    password=arg

    specifies the CIFS password. If this option is not given then the environment variable @@ -166,9 +166,9 @@ module. POSIX ACL support can be disabled on a per mount basis by specifying "noacl" on mount.

    nocase

    Request case insensitive path name matching (case sensitive is the default if the server suports it). -

    sec=

    Security mode. Allowed values are:

    • none attempt to connection as a null user (no name)

    • krb5 Use Kerberos version 5 authentication

    • krb5i Use Kerberos authentication and packet signing

    • ntlm Use NTLM password hashing (default)

    • ntlmi Use NTLM password hashing with signing (if +

    sec=

    Security mode. Allowed values are:

    • none attempt to connection as a null user (no name)

    • krb5 Use Kerberos version 5 authentication

    • krb5i Use Kerberos authentication and packet signing

    • ntlm Use NTLM password hashing (default)

    • ntlmi Use NTLM password hashing with signing (if /proc/fs/cifs/PacketSigningEnabled on or if - server requires signing also can be the default)

    • ntlmv2 Use NTLMv2 password hashing

    • ntlmv2i Use NTLMv2 password hashing with packet signing

    [NB This [sec parameter] is under development and expected to be available in cifs kernel module 1.40 and later] + server requires signing also can be the default)

  • ntlmv2 Use NTLMv2 password hashing

  • ntlmv2i Use NTLMv2 password hashing with packet signing

[NB This [sec parameter] is under development and expected to be available in cifs kernel module 1.40 and later]

nobrl

Do not send byte range lock requests to the server. This is necessary for certain applications that break with cifs style mandatory byte range locks (and most @@ -218,11 +218,11 @@

wsize=arg

default network write size (default 57344) maximum wsize currently allowed by CIFS is 57344 (fourteen - 4096 byte pages)

--verbose

Print additional debugging information for the mount. Note that this parameter must be specified before the -o. For example:

mount -t cifs //server/share /mnt --verbose -o user=username

SERVICE FORMATTING AND DELIMITERS

+ 4096 byte pages)

--verbose

Print additional debugging information for the mount. Note that this parameter must be specified before the -o. For example:

mount -t cifs //server/share /mnt --verbose -o user=username

SERVICE FORMATTING AND DELIMITERS

It's generally preferred to use forward slashes (/) as a delimiter in service names. They are considered to be the "universal delimiter" since they are generally not allowed to be embedded within path components on Windows machines and the client can convert them to blackslashes (\) unconditionally. Conversely, backslash characters are allowed by POSIX to be part of a path component, and can't be automatically converted in the same way.

mount.cifs will attempt to convert backslashes to forward slashes where it's able to do so, but it cannot do so in any path component following the sharename. -

ENVIRONMENT VARIABLES

+

ENVIRONMENT VARIABLES

The variable USER may contain the username of the person to be used to authenticate to the server. The variable can be used to set both username and @@ -234,7 +234,7 @@ 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, unless installed setuid, in which case the noeexec and nosuid mount flags are enabled.

CONFIGURATION

+

NOTES

This command may be used only by root, unless installed setuid, in which case the noeexec and nosuid mount flags are enabled.

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 @@ -245,7 +245,7 @@ cifs.ko which will list the options that may be passed to cifs during module installation (device driver load). For more information see the kernel file fs/cifs/README. -

BUGS

Mounting using the CIFS URL specification is currently not supported. +

BUGS

Mounting using the CIFS URL specification is currently not supported.

The credentials file does not handle usernames or passwords with leading space.

Note that the typical response to a bug report is a suggestion @@ -253,11 +253,11 @@ and always include which versions you use of relevant software when reporting bugs (minimum: mount.cifs (try mount.cifs -V), kernel (see /proc/version) and server type you are trying to contact. -

VERSION

This man page is correct for version 1.52 of - the cifs vfs filesystem (roughly Linux kernel 2.6.24).

SEE ALSO

+

VERSION

This man page is correct for version 1.52 of + the cifs vfs filesystem (roughly Linux kernel 2.6.24).

SEE ALSO

Documentation/filesystems/cifs.txt and fs/cifs/README in the linux kernel source tree may contain additional options and information. -

umount.cifs(8)

AUTHOR

Steve French

The syntax and manpage were loosely based on that of smbmount. It +

umount.cifs(8)

AUTHOR

Steve French

The syntax and manpage were loosely based on that of smbmount. It was converted to Docbook/XML by Jelmer Vernooij.

The maintainer of the Linux cifs vfs and the userspace tool mount.cifs is Steve French. The Linux CIFS Mailing list diff -u -r --new-file --exclude .svn --exclude CVS samba-3.3.10//docs/htmldocs/manpages/net.8.html samba-3.3.11//docs/htmldocs/manpages/net.8.html --- samba-3.3.10//docs/htmldocs/manpages/net.8.html 2010-01-14 11:20:37.000000000 +0100 +++ samba-3.3.11//docs/htmldocs/manpages/net.8.html 2010-02-22 16:53:37.000000000 +0100 @@ -1,13 +1,13 @@ -net

Name

net — Tool for administration of Samba and remote +net

Name

net — Tool for administration of Samba and remote CIFS servers. -

Synopsis

net {<ads|rap|rpc>} [-h] [-w workgroup] [-W myworkgroup] [-U user] [-I ip-address] [-p port] [-n myname] [-s conffile] [-S server] [-l] [-P] [-d debuglevel] [-V] [--request-timeout seconds]

DESCRIPTION

This tool is part of the samba(7) suite.

The Samba net utility is meant to work just like the net utility +

Synopsis

net {<ads|rap|rpc>} [-h] [-w workgroup] [-W myworkgroup] [-U user] [-I ip-address] [-p port] [-n myname] [-s conffile] [-S server] [-l] [-P] [-d debuglevel] [-V] [--request-timeout seconds]

DESCRIPTION

This tool is part of the samba(7) suite.

The Samba net utility is meant to work just like the net utility available for windows and DOS. The first argument should be used to specify the protocol to use when executing a certain command. ADS is used for ActiveDirectory, RAP is using for old (Win9x/NT3) clients and RPC can be used for NT4 and Windows 2000. If this argument is omitted, net will try to determine it automatically. Not all commands are available on all protocols. -

OPTIONS

-h|--help

Print a summary of command line options. +

OPTIONS

-h|--help

Print a summary of command line options.

-w target-workgroup

Sets target workgroup or domain. You have to specify either this option or the IP address or the name of a server. @@ -57,18 +57,18 @@ 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 parameter -in the smb.conf file.

COMMANDS

CHANGESECRETPW

This command allows the Samba machine account password to be set from an external application +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 +

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 -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]] [createupn=UPN] [createcomputer=OU] [options]

+

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]] [createupn=UPN] [createcomputer=OU] [options]

Join a domain. If the account already exists on the server, and [TYPE] is MEMBER, the machine will attempt to join automatically. (Assuming that the machine has been created in server manager) @@ -85,81 +85,81 @@ a '/'. Please note that '\' is used for escape by both the shell and ldap, so it may need to be doubled or quadrupled to pass through, and it is not used as a delimiter. -

[RPC] OLDJOIN [options]

Join a domain. Use the OLDJOIN option to join the domain +

[RPC] OLDJOIN [options]

Join a domain. Use the OLDJOIN option to join the domain using the old style of domain joining - you need to create a trust -account in server manager first.

[RPC|ADS] USER

[RPC|ADS] USER

List all users

[RPC|ADS] USER DELETE target

Delete specified user

[RPC|ADS] USER INFO target

List the domain groups of the specified user.

[RPC|ADS] USER RENAME oldname newname

Rename specified user.

[RPC|ADS] USER ADD name [password] [-F user flags] [-C comment]

Add specified user.

[RPC|ADS] GROUP

[RPC|ADS] GROUP [misc options] [targets]

List user groups.

[RPC|ADS] GROUP DELETE name [misc. options]

Delete specified group.

[RPC|ADS] GROUP ADD name [-C comment]

Create specified group.

[RAP|RPC] SHARE

[RAP|RPC] SHARE [misc. options] [targets]

Enumerates all exported resources (network shares) on target server.

[RAP|RPC] SHARE ADD name=serverpath [-C comment] [-M maxusers] [targets]

Adds a share from a server (makes the export active). Maxusers +account in server manager first.

[RPC|ADS] USER

[RPC|ADS] USER

List all users

[RPC|ADS] USER DELETE target

Delete specified user

[RPC|ADS] USER INFO target

List the domain groups of the specified user.

[RPC|ADS] USER RENAME oldname newname

Rename specified user.

[RPC|ADS] USER ADD name [password] [-F user flags] [-C comment]

Add specified user.

[RPC|ADS] GROUP

[RPC|ADS] GROUP [misc options] [targets]

List user groups.

[RPC|ADS] GROUP DELETE name [misc. options]

Delete specified group.

[RPC|ADS] GROUP ADD name [-C comment]

Create specified group.

[RAP|RPC] SHARE

[RAP|RPC] SHARE [misc. options] [targets]

Enumerates all exported resources (network shares) on target server.

[RAP|RPC] SHARE ADD name=serverpath [-C comment] [-M maxusers] [targets]

Adds a share from a server (makes the export active). Maxusers specifies the number of users that can be connected to the -share simultaneously.

SHARE DELETE sharename

Delete specified share.

[RPC|RAP] FILE

[RPC|RAP] FILE

List all open files on remote server.

[RPC|RAP] FILE CLOSE fileid

Close file with specified fileid on -remote server.

[RPC|RAP] FILE INFO fileid

+share simultaneously.

SHARE DELETE sharename

Delete specified share.

[RPC|RAP] FILE

[RPC|RAP] FILE

List all open files on remote server.

[RPC|RAP] FILE CLOSE fileid

Close file with specified fileid on +remote server.

[RPC|RAP] FILE INFO fileid

Print information on specified fileid. Currently listed are: file-id, username, locks, path, permissions. -

[RAP|RPC] FILE USER user

+

[RAP|RPC] FILE USER user

List files opened by specified user. Please note that net rap file user does not work against Samba servers. -

SESSION

RAP SESSION

Without any other options, SESSION enumerates all active SMB/CIFS -sessions on the target server.

RAP SESSION DELETE|CLOSE CLIENT_NAME

Close the specified sessions.

RAP SESSION INFO CLIENT_NAME

Give a list with all the open files in specified session.

RAP SERVER DOMAIN

List all servers in specified domain or workgroup. Defaults -to local domain.

RAP DOMAIN

Lists all domains and workgroups visible on the -current network.

RAP PRINTQ

RAP PRINTQ INFO QUEUE_NAME

Lists the specified print queue and print jobs on the server. +

SESSION

RAP SESSION

Without any other options, SESSION enumerates all active SMB/CIFS +sessions on the target server.

RAP SESSION DELETE|CLOSE CLIENT_NAME

Close the specified sessions.

RAP SESSION INFO CLIENT_NAME

Give a list with all the open files in specified session.

RAP SERVER DOMAIN

List all servers in specified domain or workgroup. Defaults +to local domain.

RAP DOMAIN

Lists all domains and workgroups visible on the +current network.

RAP PRINTQ

RAP PRINTQ INFO QUEUE_NAME

Lists the specified print queue and print jobs on the server. If the QUEUE_NAME is omitted, all -queues are listed.

RAP PRINTQ DELETE JOBID

Delete job with specified id.

RAP VALIDATE user [password]

+queues are listed.

RAP PRINTQ DELETE JOBID

Delete job with specified id.

RAP VALIDATE user [password]

Validate whether the specified user can log in to the remote server. If the password is not specified on the commandline, it will be prompted. -

Note

Currently NOT implemented.

RAP GROUPMEMBER

RAP GROUPMEMBER LIST GROUP

List all members of the specified group.

RAP GROUPMEMBER DELETE GROUP USER

Delete member from group.

RAP GROUPMEMBER ADD GROUP USER

Add member to group.

RAP ADMIN command

Execute the specified command on +

Note

Currently NOT implemented.

RAP GROUPMEMBER

RAP GROUPMEMBER LIST GROUP

List all members of the specified group.

RAP GROUPMEMBER DELETE GROUP USER

Delete member from group.

RAP GROUPMEMBER ADD GROUP USER

Add member to group.

RAP ADMIN command

Execute the specified command on the remote server. Only works with OS/2 servers. -

Note

Currently NOT implemented.

RAP SERVICE

RAP SERVICE START NAME [arguments...]

Start the specified service on the remote server. Not implemented yet.

Note

Currently NOT implemented.

RAP SERVICE STOP

Stop the specified service on the remote server.

Note

Currently NOT implemented.

RAP PASSWORD USER OLDPASS NEWPASS

+

Note

Currently NOT implemented.

RAP SERVICE

RAP SERVICE START NAME [arguments...]

Start the specified service on the remote server. Not implemented yet.

Note

Currently NOT implemented.

RAP SERVICE STOP

Stop the specified service on the remote server.

Note

Currently NOT implemented.

RAP PASSWORD USER OLDPASS NEWPASS

Change password of USER from OLDPASS to NEWPASS. -

LOOKUP

LOOKUP HOST HOSTNAME [TYPE]

+

LOOKUP

LOOKUP HOST HOSTNAME [TYPE]

Lookup the IP address of the given host with the specified type (netbios suffix). The type defaults to 0x20 (workstation). -

LOOKUP LDAP [DOMAIN]

Give IP address of LDAP server of specified DOMAIN. Defaults to local domain.

LOOKUP KDC [REALM]

Give IP address of KDC for the specified REALM. -Defaults to local realm.

LOOKUP DC [DOMAIN]

Give IP's of Domain Controllers for specified -DOMAIN. Defaults to local domain.

LOOKUP MASTER DOMAIN

Give IP of master browser for specified DOMAIN -or workgroup. Defaults to local domain.

CACHE

Samba uses a general caching interface called 'gencache'. It +

LOOKUP LDAP [DOMAIN]

Give IP address of LDAP server of specified DOMAIN. Defaults to local domain.

LOOKUP KDC [REALM]

Give IP address of KDC for the specified REALM. +Defaults to local realm.

LOOKUP DC [DOMAIN]

Give IP's of Domain Controllers for specified +DOMAIN. Defaults to local domain.

LOOKUP MASTER DOMAIN

Give IP of master browser for specified DOMAIN +or workgroup. Defaults to local domain.

CACHE

Samba uses a general caching interface called 'gencache'. It can be controlled using 'NET CACHE'.

All the timeout parameters support the suffixes: -

s - Seconds
m - Minutes
h - Hours
d - Days
w - Weeks

+

s - Seconds
m - Minutes
h - Hours
d - Days
w - Weeks

-

CACHE ADD key data time-out

Add specified key+data to the cache with the given timeout.

CACHE DEL key

Delete key from the cache.

CACHE SET key data time-out

Update data of existing cache entry.

CACHE SEARCH PATTERN

Search for the specified pattern in the cache data.

CACHE LIST

+

CACHE ADD key data time-out

Add specified key+data to the cache with the given timeout.

CACHE DEL key

Delete key from the cache.

CACHE SET key data time-out

Update data of existing cache entry.

CACHE SEARCH PATTERN

Search for the specified pattern in the cache data.

CACHE LIST

List all current items in the cache. -

CACHE FLUSH

Remove all the current items from the cache.

GETLOCALSID [DOMAIN]

Prints the SID of the specified domain, or if the parameter is -omitted, the SID of the local server.

SETLOCALSID S-1-5-21-x-y-z

Sets SID for the local server to the specified SID.

GETDOMAINSID

Prints the local machine SID and the SID of the current -domain.

SETDOMAINSID

Sets the SID of the current domain.

GROUPMAP

Manage the mappings between Windows group SIDs and UNIX groups. -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

+

CACHE FLUSH

Remove all the current items from the cache.

GETLOCALSID [DOMAIN]

Prints the SID of the specified domain, or if the parameter is +omitted, the SID of the local server.

SETLOCALSID S-1-5-21-x-y-z

Sets SID for the local server to the specified SID.

GETDOMAINSID

Prints the local machine SID and the SID of the current +domain.

SETDOMAINSID

Sets the SID of the current domain.

GROUPMAP

Manage the mappings between Windows group SIDs and UNIX groups. +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}] [ntgroup=string] [comment=string]
 

-

GROUPMAP DELETE

Delete a group mapping entry. If more than one group name matches, the first entry found is deleted.

net groupmap delete {ntgroup=string|sid=SID}

GROUPMAP MODIFY

Update en existing group entry.

+

GROUPMAP DELETE

Delete a group mapping entry. If more than one group name matches, the first entry found is deleted.

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 +

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

RPC INFO

Print information about the domain of the remote server, such as domain name, domain sid and number of users and groups. -

[RPC|ADS] TESTJOIN

Check whether participation in a domain is still valid.

[RPC|ADS] CHANGETRUSTPW

Force change of domain trust password.

RPC TRUSTDOM

RPC TRUSTDOM ADD DOMAIN

Add a interdomain trust account for DOMAIN. +

[RPC|ADS] TESTJOIN

Check whether participation in a domain is still valid.

[RPC|ADS] CHANGETRUSTPW

Force change of domain trust password.

RPC TRUSTDOM

RPC TRUSTDOM ADD DOMAIN

Add a interdomain trust account for DOMAIN. This is in fact a Samba account named DOMAIN$ with the account flag 'I' (interdomain trust account). If the command is used against localhost it has the same effect as smbpasswd -a -i DOMAIN. Please note that both commands expect a appropriate UNIX account. -

RPC TRUSTDOM DEL DOMAIN

Remove interdomain trust account for +

RPC TRUSTDOM DEL DOMAIN

Remove interdomain trust account for DOMAIN. If it is used against localhost it has the same effect as smbpasswd -x DOMAIN$. -

RPC TRUSTDOM ESTABLISH DOMAIN

+

RPC TRUSTDOM ESTABLISH DOMAIN

Establish a trust relationship to a trusting domain. Interdomain account must already be created on the remote PDC. -

RPC TRUSTDOM REVOKE DOMAIN

Abandon relationship to trusted domain

RPC TRUSTDOM LIST

List all current interdomain trust relationships.

RPC RIGHTS

This subcommand is used to view and manage Samba's rights assignments (also +

RPC TRUSTDOM REVOKE DOMAIN

Abandon relationship to trusted domain

RPC TRUSTDOM LIST

List all current interdomain trust relationships.

RPC RIGHTS

This subcommand is used to view and manage Samba's rights assignments (also referred to as privileges). There are three options currently available: list, grant, and revoke. More details on Samba's privilege model and its use -can be found in the Samba-HOWTO-Collection.

RPC ABORTSHUTDOWN

Abort the shutdown of a remote server.

RPC SHUTDOWN [-t timeout] [-r] [-f] [-C message]

Shut down the remote server.

-r

+can be found in the Samba-HOWTO-Collection.

RPC ABORTSHUTDOWN

Abort the shutdown of a remote server.

RPC SHUTDOWN [-t timeout] [-r] [-f] [-C message]

Shut down the remote server.

-r

Reboot after shutdown.

-f

Force shutting down all applications. @@ -167,23 +167,23 @@ Timeout before system will be shut down. An interactive user of the system can use this time to cancel the shutdown.

-C message

Display the specified message on the screen to -announce the shutdown.

RPC SAMDUMP

Print out sam database of remote server. You need -to run this against the PDC, from a Samba machine joined as a BDC.

RPC VAMPIRE

Export users, aliases and groups from remote server to +announce the shutdown.

RPC SAMDUMP

Print out sam database of remote server. You need +to run this against the PDC, from a Samba machine joined as a BDC.

RPC VAMPIRE

Export users, aliases and groups from remote server to local server. You need to run this against the PDC, from a Samba machine joined as a BDC. -

RPC VAMPIRE KEYTAB

Dump remote SAM database to local Kerberos keytab file. -

RPC VAMPIRE LDIF

Dump remote SAM database to local LDIF file or standard output. -

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

RPC VAMPIRE KEYTAB

Dump remote SAM database to local Kerberos keytab file. +

RPC VAMPIRE LDIF

Dump remote SAM database to local LDIF file or standard output. +

RPC 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]

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

ADS DN DN (attributes)

+

ADS DN DN (attributes)

Perform a raw LDAP search on a ADS server and dump the results. The DN standard LDAP DN, and the attributes are a list of LDAP fields to show in the result. -

Example: net ads dn 'CN=administrator,CN=Users,DC=my,DC=domain' SAMAccountName

ADS WORKGROUP

Print out workgroup name for specified kerberos realm.

SAM CREATEBUILTINGROUP <NAME>

+

Example: net ads dn 'CN=administrator,CN=Users,DC=my,DC=domain' SAMAccountName

ADS WORKGROUP

Print out workgroup name for specified kerberos realm.

SAM CREATEBUILTINGROUP <NAME>

(Re)Create a BUILTIN group. Only a wellknown set of BUILTIN groups can be created with this command. This is the list of currently recognized group names: Administrators, @@ -193,84 +193,84 @@ This command requires a running Winbindd with idmap allocation properly configured. The group gid will be allocated out of the winbindd range. -

SAM CREATELOCALGROUP <NAME>

+

SAM CREATELOCALGROUP <NAME>

Create a LOCAL group (also known as Alias). This command requires a running Winbindd with idmap allocation properly configured. The group gid will be allocated out of the winbindd range. -

SAM DELETELOCALGROUP <NAME>

+

SAM DELETELOCALGROUP <NAME>

Delete an existing LOCAL group (also known as Alias). -

SAM MAPUNIXGROUP <NAME>

+

SAM MAPUNIXGROUP <NAME>

Map an existing Unix group and make it a Domain Group, the domain group will have the same name. -

SAM UNMAPUNIXGROUP <NAME>

+

SAM UNMAPUNIXGROUP <NAME>

Remove an existing group mapping entry. -

SAM ADDMEM <GROUP> <MEMBER>

+

SAM ADDMEM <GROUP> <MEMBER>

Add a member to a Local group. The group can be specified only by name, the member can be specified by name or SID. -

SAM DELMEM <GROUP> <MEMBER>

+

SAM DELMEM <GROUP> <MEMBER>

Remove a member from a Local group. The group and the member must be specified by name. -

SAM LISTMEM <GROUP>

+

SAM LISTMEM <GROUP>

List Local group members. The group must be specified by name. -

SAM LIST <users|groups|localgroups|builtin|workstations> [verbose]

+

SAM LIST <users|groups|localgroups|builtin|workstations> [verbose]

List the specified set of accounts by name. If verbose is specified, the rid and description is also provided for each account. -

SAM RIGHTS LIST

+

SAM RIGHTS LIST

List all available privileges. -

SAM RIGHTS GRANT <NAME> <PRIVILEGE>

+

SAM RIGHTS GRANT <NAME> <PRIVILEGE>

Grant a certain privilege to a user. -

SAM RIGHTS REVOKE <NAME> <PRIVILEGE>

+

SAM RIGHTS REVOKE <NAME> <PRIVILEGE>

Revoke a certain privilege from a user. -

SAM SHOW <NAME>

+

SAM SHOW <NAME>

Show the full DOMAIN\\NAME the SID and the type for the corresponding account. -

SAM SET HOMEDIR <NAME> <DIRECTORY>

+

SAM SET HOMEDIR <NAME> <DIRECTORY>

Set the home directory for a user account. -

SAM SET PROFILEPATH <NAME> <PATH>

+

SAM SET PROFILEPATH <NAME> <PATH>

Set the profile path for a user account. -

SAM SET COMMENT <NAME> <COMMENT>

+

SAM SET COMMENT <NAME> <COMMENT>

Set the comment for a user or group account. -

SAM SET FULLNAME <NAME> <FULL NAME>

+

SAM SET FULLNAME <NAME> <FULL NAME>

Set the full name for a user account. -

SAM SET LOGONSCRIPT <NAME> <SCRIPT>

+

SAM SET LOGONSCRIPT <NAME> <SCRIPT>

Set the logon script for a user account. -

SAM SET HOMEDRIVE <NAME> <DRIVE>

+

SAM SET HOMEDRIVE <NAME> <DRIVE>

Set the home drive for a user account. -

SAM SET WORKSTATIONS <NAME> <WORKSTATIONS>

+

SAM SET WORKSTATIONS <NAME> <WORKSTATIONS>

Set the workstations a user account is allowed to log in from. -

SAM SET DISABLE <NAME>

+

SAM SET DISABLE <NAME>

Set the "disabled" flag for a user account. -

SAM SET PWNOTREQ <NAME>

+

SAM SET PWNOTREQ <NAME>

Set the "password not required" flag for a user account. -

SAM SET AUTOLOCK <NAME>

+

SAM SET AUTOLOCK <NAME>

Set the "autolock" flag for a user account. -

SAM SET PWNOEXP <NAME>

+

SAM SET PWNOEXP <NAME>

Set the "password do not expire" flag for a user account. -

SAM SET PWDMUSTCHANGENOW <NAME> [yes|no]

+

SAM SET PWDMUSTCHANGENOW <NAME> [yes|no]

Set or unset the "password must change" flag for a user account. -

SAM POLICY LIST

+

SAM POLICY LIST

List the available account policies. -

SAM POLICY SHOW <account policy>

+

SAM POLICY SHOW <account policy>

Show the account policy value. -

SAM POLICY SET <account policy> <value>

+

SAM POLICY SET <account policy> <value>

Set a value for the account policy. Valid values can be: "forever", "never", "off", or a number. -

SAM PROVISION

+

SAM PROVISION

Only available if ldapsam:editposix is set and winbindd is running. Properly populates the ldap tree with the basic accounts (Administrator) and groups (Domain Users, Domain Admins, Domain Guests) on the ldap tree. -

IDMAP DUMP <local tdb file name>

+

IDMAP DUMP <local tdb file name>

Dumps the mappings contained in the local tdb file specified. This command is useful to dump only the mappings produced by the idmap_tdb backend. -

IDMAP RESTORE [input file]

+

IDMAP RESTORE [input file]

Restore the mappings from the specified file or stdin. -

IDMAP SECRET <DOMAIN>|ALLOC <secret>

+

IDMAP SECRET <DOMAIN>|ALLOC <secret>

Store a secret for the specified domain, used primarily for domains that use idmap_ldap as a backend. In this case the secret is used as the password for the user DN used to bind to the ldap server. -

USERSHARE

Starting with version 3.0.23, a Samba server now supports the ability for +

USERSHARE

Starting with version 3.0.23, a Samba server now supports the ability for non-root users to add user defined shares to be exported using the "net usershare" commands.

@@ -297,9 +297,9 @@ can create user defined shares on demand using the commands below.

The usershare commands are: -

net usershare add sharename path [comment] [acl] [guest_ok=[y|n]] - to add or change a user defined share.
net usershare delete sharename - to delete a user defined share.
net usershare info [-l|--long] [wildcard sharename] - to print info about a user defined share.
net usershare list [-l|--long] [wildcard sharename] - to list user defined shares.

+

net usershare add sharename path [comment] [acl] [guest_ok=[y|n]] - to add or change a user defined share.
net usershare delete sharename - to delete a user defined share.
net usershare info [-l|--long] [wildcard sharename] - to print info about a user defined share.
net usershare list [-l|--long] [wildcard sharename] - to list user defined shares.

-

USERSHARE ADD sharename path [comment] [acl] [guest_ok=[y|n]]

+

USERSHARE ADD sharename path [comment] [acl] [guest_ok=[y|n]]

Add or replace a new user defined share, with name "sharename".

"path" specifies the absolute pathname on the system to be exported. @@ -336,11 +336,11 @@ you wish. The Samba smbd daemon notices user defined share modifications at connect time so will see the change immediately, there is no need to restart smbd on adding, deleting or changing a user defined share. -

USERSHARE DELETE sharename

+

USERSHARE DELETE sharename

Deletes the user defined share by name. The Samba smbd daemon immediately notices this change, although it will not disconnect any users currently connected to the deleted share. -

USERSHARE INFO [-l|--long] [wildcard sharename]

+

USERSHARE INFO [-l|--long] [wildcard sharename]

Get info on user defined shares owned by the current user matching the given pattern, or all users.

net usershare info on its own dumps out info on the user defined shares that were @@ -359,7 +359,7 @@ And is a list of the current settings of the user defined share that can be modified by the "net usershare add" command. -

USERSHARE LIST [-l|--long] wildcard sharename

+

USERSHARE LIST [-l|--long] wildcard sharename

List all the user defined shares owned by the current user matching the given pattern, or all users.

net usershare list on its own list out the names of the user defined shares that were @@ -367,28 +367,28 @@ wildcard pattern ('*' matches one or more characters, '?' matches only one character). If the '-l' or '--long' option is also given, it includes the names of user defined shares created by other users. -

CONF

Starting with version 3.2.0, a Samba server can be configured by data +

CONF

Starting with version 3.2.0, a Samba server can be configured by data stored in registry. This configuration data can be edited with the new "net conf" commands.

The deployment of this configuration data can be activated in two levels from the smb.conf file: Share definitions from registry are activated by setting registry shares to -yes in the [global] section and global configuration options are +“yes” in the [global] section and global configuration options are activated by setting include = registry in the [global] section for a mixed configuration or by setting config backend = registry in the [global] section for a registry-only configuration. See the smb.conf(5) manpage for details.

The conf commands are: -

net conf list - Dump the complete configuration in smb.conf like +

net conf list - Dump the complete configuration in smb.conf like format.
net conf import - Import configuration from file in smb.conf format.
net conf listshares - List the registry shares.
net conf drop - Delete the complete configuration from registry.
net conf showshare - Show the definition of a registry share.
net conf addshare - Create a new registry share.
net conf delshare - Delete a registry share.
net conf setparm - Store a parameter.
net conf getparm - Retrieve the value of a parameter.
net conf delparm - Delete a parameter.
net conf getincludes - Show the includes of a share definition.
net conf setincludes - Set includes for a share.
net conf delincludes - Delete includes from a share definition.

-

CONF LIST

+

CONF LIST

Print the configuration data stored in the registry in a smb.conf-like format to standard output. -

CONF IMPORT [--test|-T] filename [section]

+

CONF IMPORT [--test|-T] filename [section]

This command imports configuration from a file in smb.conf format. If a section encountered in the input file is present in registry, its contents is replaced. Sections of registry configuration that have @@ -398,30 +398,30 @@ import command to that specific section. A test mode is enabled by specifying the parameter "-T" on the commandline. In test mode, no changes are made to the registry, and the resulting configuration is printed to standard output instead. -

CONF LISTSHARES

+

CONF LISTSHARES

List the names of the shares defined in registry. -

CONF DROP

+

CONF DROP

Delete the complete configuration data from registry. -

CONF SHOWSHARE sharename

+

CONF SHOWSHARE sharename

Show the definition of the share or section specified. It is valid to specify "global" as sharename to retrieve the global configuration options from registry. -

CONF ADDSHARE sharename path [writeable={y|N} [guest_ok={y|N} [comment]]]

Create a new share definition in registry. +

CONF ADDSHARE sharename path [writeable={y|N} [guest_ok={y|N} [comment]]]

Create a new share definition in registry. The sharename and path have to be given. The share name may not be "global". Optionally, values for the very common options "writeable", "guest ok" and a "comment" may be specified. The same result may be obtained by a sequence of "net conf setparm" commands. -

CONF DELSHARE sharename

+

CONF DELSHARE sharename

Delete a share definition from registry. -

CONF SETPARM section parameter value

+

CONF SETPARM section parameter value

Store a parameter in registry. The section may be global or a sharename. The section is created if it does not exist yet. -

CONF GETPARM section parameter

+

CONF GETPARM section parameter

Show a parameter stored in registry. -

CONF DELPARM section parameter

+

CONF DELPARM section parameter

Delete a parameter stored in registry. -

CONF GETINCLUDES section

+

CONF GETINCLUDES section

Get the list of includes for the provided section (global or share).

Note that due to the nature of the registry database and the nature of include directives, @@ -437,36 +437,36 @@ Further note that currently, only files can be included from registry configuration. In the future, there will be the ability to include configuration data from other registry keys. -

CONF SETINCLUDES section [filename]+

+

CONF SETINCLUDES section [filename]+

Set the list of includes for the provided section (global or share) to the given list of one or more filenames. The filenames may contain the usual smb.conf macros like %I. -

CONF DELINCLUDES section

+

CONF DELINCLUDES section

Delete the list of includes from the provided section (global or share). -

DOM

Starting with version 3.2.0 Samba has support for remote join and unjoin APIs, both client and server-side. Windows supports remote join capabilities since Windows 2000. +

DOM

Starting with version 3.2.0 Samba has support for remote join and unjoin APIs, both client and server-side. Windows supports remote join capabilities since Windows 2000.

In order for Samba to be joined or unjoined remotely an account must be used that is either member of the Domain Admins group, a member of the local Administrators group or a user that is granted the SeMachineAccountPrivilege privilege.

The client side support for remote join is implemented in the net dom commands which are: -

net dom join - Join a remote computer into a domain.
net dom unjoin - Unjoin a remote computer from a domain.

-

DOM JOIN domain=DOMAIN ou=OU account=ACCOUNT password=PASSWORD reboot

+

net dom join - Join a remote computer into a domain.
net dom unjoin - Unjoin a remote computer from a domain.

+

DOM JOIN domain=DOMAIN ou=OU account=ACCOUNT password=PASSWORD reboot

Joins a computer into a domain. This command supports the following additional parameters: -

  • DOMAIN can be a NetBIOS domain name (also known as short domain name) or a DNS domain name for Active Directory Domains. As in Windows, it is also possible to control which Domain Controller to use. This can be achieved by appending the DC name using the \ separator character. Example: MYDOM\MYDC. The DOMAIN parameter cannot be NULL.

  • OU can be set to a RFC 1779 LDAP DN, like ou=mymachines,cn=Users,dc=example,dc=com in order to create the machine account in a non-default LDAP containter. This optional parameter is only supported when joining Active Directory Domains.

  • ACCOUNT defines a domain account that will be used to join the machine to the domain. This domain account needs to have sufficient privileges to join machines.

  • PASSWORD defines the password for the domain account defined with ACCOUNT.

  • REBOOT is an optional parameter that can be set to reboot the remote machine after successful join to the domain.

+

  • DOMAIN can be a NetBIOS domain name (also known as short domain name) or a DNS domain name for Active Directory Domains. As in Windows, it is also possible to control which Domain Controller to use. This can be achieved by appending the DC name using the \ separator character. Example: MYDOM\MYDC. The DOMAIN parameter cannot be NULL.

  • OU can be set to a RFC 1779 LDAP DN, like ou=mymachines,cn=Users,dc=example,dc=com in order to create the machine account in a non-default LDAP containter. This optional parameter is only supported when joining Active Directory Domains.

  • ACCOUNT defines a domain account that will be used to join the machine to the domain. This domain account needs to have sufficient privileges to join machines.

  • PASSWORD defines the password for the domain account defined with ACCOUNT.

  • REBOOT is an optional parameter that can be set to reboot the remote machine after successful join to the domain.

Note that you also need to use standard net parameters to connect and authenticate to the remote machine that you want to join. These additional parameters include: -S computer and -U user.

Example: net dom join -S xp -U XP\\administrator%secret domain=MYDOM account=MYDOM\\administrator password=topsecret reboot.

This example would connect to a computer named XP as the local administrator using password secret, and join the computer into a domain called MYDOM using the MYDOM domain administrator account and password topsecret. After successful join, the computer would reboot. -

DOM UNJOIN account=ACCOUNT password=PASSWORD reboot

+

DOM UNJOIN account=ACCOUNT password=PASSWORD reboot

Unjoins a computer from a domain. This command supports the following additional parameters: -

  • ACCOUNT defines a domain account that will be used to unjoin the machine from the domain. This domain account needs to have sufficient privileges to unjoin machines.

  • PASSWORD defines the password for the domain account defined with ACCOUNT.

  • REBOOT is an optional parameter that can be set to reboot the remote machine after successful unjoin from the domain.

+

  • ACCOUNT defines a domain account that will be used to unjoin the machine from the domain. This domain account needs to have sufficient privileges to unjoin machines.

  • PASSWORD defines the password for the domain account defined with ACCOUNT.

  • REBOOT is an optional parameter that can be set to reboot the remote machine after successful unjoin from the domain.

Note that you also need to use standard net parameters to connect and authenticate to the remote machine that you want to unjoin. These additional parameters include: -S computer and -U user.

Example: net dom unjoin -S xp -U XP\\administrator%secret account=MYDOM\\administrator password=topsecret reboot.

This example would connect to a computer named XP as the local administrator using password secret, and unjoin the computer from the domain using the MYDOM domain administrator account and password topsecret. After successful unjoin, the computer would reboot. -

HELP [COMMAND]

Gives usage information for the specified command.

VERSION

This man page is complete for version 3 of the Samba - suite.

AUTHOR

The original Samba software and related utilities +

HELP [COMMAND]

Gives usage information for the specified command.

VERSION

This man page is complete for version 3 of the Samba + suite.

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 net manpage was written by Jelmer Vernooij.

diff -u -r --new-file --exclude .svn --exclude CVS samba-3.3.10//docs/htmldocs/manpages/nmbd.8.html samba-3.3.11//docs/htmldocs/manpages/nmbd.8.html --- samba-3.3.10//docs/htmldocs/manpages/nmbd.8.html 2010-01-14 11:20:38.000000000 +0100 +++ samba-3.3.11//docs/htmldocs/manpages/nmbd.8.html 2010-02-22 16:53:36.000000000 +0100 @@ -1,5 +1,5 @@ -nmbd

Name

nmbd — NetBIOS name server to provide NetBIOS - over IP naming services to clients

Synopsis

nmbd [-D] [-F] [-S] [-a] [-i] [-o] [-h] [-V] [-d <debug level>] [-H <lmhosts file>] [-l <log directory>] [-p <port number>] [-s <configuration file>]

DESCRIPTION

This program is part of the samba(7) suite.

nmbd is a server that understands +nmbd

Name

nmbd — NetBIOS name server to provide NetBIOS + over IP naming services to clients

Synopsis

nmbd [-D] [-F] [-S] [-a] [-i] [-o] [-h] [-V] [-d <debug level>] [-H <lmhosts file>] [-l <log directory>] [-p <port number>] [-s <configuration file>]

DESCRIPTION

This program is part of the samba(7) suite.

nmbd is a server that understands and can reply to NetBIOS over IP name service requests, like those produced by SMB/CIFS clients such as Windows 95/98/ME, Windows NT, Windows 2000, Windows XP and LanManager clients. It also @@ -22,7 +22,7 @@ replying to queries from clients for these names.

In addition, nmbd can act as a WINS proxy, relaying broadcast queries from clients that do not understand how to talk the WINS protocol to a WINS - server.

OPTIONS

-D

If specified, this parameter causes + server.

OPTIONS

-D

If specified, this parameter causes nmbd to operate as a daemon. That is, it detaches itself and runs in the background, fielding requests on the appropriate port. By default, nmbd @@ -88,7 +88,7 @@ This option changes the default UDP port number (normally 137) that nmbd responds to name queries on. Don't use this option unless you are an expert, in which case you - won't need help!

FILES

/etc/inetd.conf

If the server is to be run by the + 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. @@ -115,7 +115,7 @@ will store the browsing database in the file browse.dat in the var/locks directory configured under wherever Samba was configured to install itself. -

SIGNALS

To shut down an nmbd process it is recommended +

SIGNALS

To shut down an nmbd process it is recommended that SIGKILL (-9) NOT be used, except as a last resort, as this may leave the name database in an inconsistent state. The correct way to terminate nmbd is to send it @@ -129,13 +129,13 @@ using smbcontrol(1) (SIGUSR[1|2] signals are no longer used since Samba 2.2). This is to allow transient problems to be diagnosed, whilst still running - at a normally low log level.

VERSION

This man page is correct for version 3 of - the Samba suite.

SEE ALSO

+ at a normally low log level.

VERSION

This man page is correct for version 3 of + the Samba suite.

SEE ALSO

inetd(8), smbd(8), smb.conf(5), smbclient(1), testparm(1), testprns(1), and the Internet RFC's rfc1001.txt, rfc1002.txt. In addition the CIFS (formerly SMB) specification is available as a link from the Web page - http://samba.org/cifs/.

AUTHOR

The original Samba software and related utilities + http://samba.org/cifs/.

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 -u -r --new-file --exclude .svn --exclude CVS samba-3.3.10//docs/htmldocs/manpages/nmblookup.1.html samba-3.3.11//docs/htmldocs/manpages/nmblookup.1.html --- samba-3.3.10//docs/htmldocs/manpages/nmblookup.1.html 2010-01-14 11:20:40.000000000 +0100 +++ samba-3.3.11//docs/htmldocs/manpages/nmblookup.1.html 2010-02-22 16:53:37.000000000 +0100 @@ -1,9 +1,9 @@ -nmblookup

Name

nmblookup — NetBIOS over TCP/IP client used to lookup NetBIOS - names

Synopsis

nmblookup [-M] [-R] [-S] [-r] [-A] [-h] [-B <broadcast address>] [-U <unicast address>] [-d <debug level>] [-s <smb config file>] [-i <NetBIOS scope>] [-T] [-f] {name}

DESCRIPTION

This tool is part of the samba(7) suite.

nmblookup is used to query NetBIOS names +nmblookup

Name

nmblookup — NetBIOS over TCP/IP client used to lookup NetBIOS + names

Synopsis

nmblookup [-M] [-R] [-S] [-r] [-A] [-h] [-B <broadcast address>] [-U <unicast address>] [-d <debug level>] [-s <smb config file>] [-i <NetBIOS scope>] [-T] [-f] {name}

DESCRIPTION

This tool is part of the samba(7) suite.

nmblookup is used to query NetBIOS names and map them to IP addresses in a network using NetBIOS over TCP/IP queries. The options allow the name queries to be directed at a particular IP broadcast area or to a particular machine. All queries - are done over UDP.

OPTIONS

-M

Searches for a master browser by looking + 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 @@ -88,12 +88,12 @@ If a NetBIOS name then the different name types may be specified by appending '#<type>' to the name. This name may also be '*', which will return all registered names within a broadcast - area.

EXAMPLES

nmblookup can be used to query + area.

EXAMPLES

nmblookup can be used to query a WINS server (in the same way nslookup is used to query DNS servers). To query a WINS server, nmblookup must be called like this:

nmblookup -U server -R 'name'

For example, running :

nmblookup -U samba.org -R 'IRIX#1B'

would query the WINS server samba.org for the domain - master browser (1B name type) for the IRIX workgroup.

VERSION

This man page is correct for version 3 of - the Samba suite.

AUTHOR

The original Samba software and related utilities + master browser (1B name type) for the IRIX workgroup.

VERSION

This man page is correct for version 3 of + the Samba suite.

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 -u -r --new-file --exclude .svn --exclude CVS samba-3.3.10//docs/htmldocs/manpages/ntlm_auth.1.html samba-3.3.11//docs/htmldocs/manpages/ntlm_auth.1.html --- samba-3.3.10//docs/htmldocs/manpages/ntlm_auth.1.html 2010-01-14 11:20:41.000000000 +0100 +++ samba-3.3.11//docs/htmldocs/manpages/ntlm_auth.1.html 2010-02-22 16:53:37.000000000 +0100 @@ -1,18 +1,18 @@ -ntlm_auth

Name

ntlm_auth — tool to allow external access to Winbind's NTLM authentication function

Synopsis

ntlm_auth [-d debuglevel] [-l logdir] [-s <smb config file>]

DESCRIPTION

This tool is part of the samba(7) suite.

ntlm_auth is a helper utility that authenticates +ntlm_auth

Name

ntlm_auth — tool to allow external access to Winbind's NTLM authentication function

Synopsis

ntlm_auth [-d debuglevel] [-l logdir] [-s <smb config file>]

DESCRIPTION

This tool is part of the samba(7) suite.

ntlm_auth is a helper utility that authenticates users using NT/LM authentication. It returns 0 if the users is authenticated successfully and 1 if access was denied. ntlm_auth uses winbind to access the user and authentication data for a domain. This utility - is only indended to be used by other programs (currently + is only intended to be used by other programs (currently Squid and mod_ntlm_winbind) -

OPERATIONAL REQUIREMENTS

+

OPERATIONAL REQUIREMENTS

The winbindd(8) daemon must be operational for many of these commands to function.

Some of these commands also require access to the directory winbindd_privileged in $LOCKDIR. This should be done either by running this command as root or providing group access to the winbindd_privileged directory. For - security reasons, this directory should not be world-accessable.

OPTIONS

--helper-protocol=PROTO

+ security reasons, this directory should not be world-accessable.

OPTIONS

--helper-protocol=PROTO

Operate as a stdio-based helper. Valid helper protocols are:

squid-2.4-basic

Server-side helper for use with Squid 2.4's basic (plaintext) @@ -60,37 +60,37 @@ finished supplying data to the other. (Which in turn could cause the helper to authenticate the user).

Curently implemented parameters from the - external program to the helper are:

Warning

Implementors should take care to base64 encode + external program to the helper are:

Warning

Implementors should take care to base64 encode any data (such as usernames/passwords) that may contain malicous user data, such as a newline. They may also need to decode strings from the helper, which likewise may have been base64 encoded.
Username

The username, expected to be in Samba's unix charset. -

Example 1. 

Username: bob


Example 2. 

Username:: Ym9i


Username

The user's domain, expected to be in +

Example 1. 

Username: bob


Example 2. 

Username:: Ym9i


Username

The user's domain, expected to be in Samba's unix charset. -

Example 3. 

Domain: WORKGROUP


Example 4. 

Domain:: V09SS0dST1VQ


Full-Username

The fully qualified username, expected to be in +

Example 3. 

Domain: WORKGROUP


Example 4. 

Domain:: V09SS0dST1VQ


Full-Username

The fully qualified username, expected to be in Samba's unix charset and qualified with the winbind separator. -

Example 5. 

Full-Username: WORKGROUP\bob


Example 6. 

Full-Username:: V09SS0dST1VQYm9i


LANMAN-Challenge

The 8 byte LANMAN Challenge value, +

Example 5. 

Full-Username: WORKGROUP\bob


Example 6. 

Full-Username:: V09SS0dST1VQYm9i


LANMAN-Challenge

The 8 byte LANMAN Challenge value, generated randomly by the server, or (in cases such as MSCHAPv2) generated in some way by both the server and the client. -

Example 7. 

LANMAN-Challege: 0102030405060708


LANMAN-Response

The 24 byte LANMAN Response value, +

Example 7. 

LANMAN-Challege: 0102030405060708


LANMAN-Response

The 24 byte LANMAN Response value, calculated from the user's password and the supplied LANMAN Challenge. Typically, this is provided over the network by a client wishing to authenticate. -

Example 8. 

LANMAN-Response: 0102030405060708090A0B0C0D0E0F101112131415161718


NT-Response

The >= 24 byte NT Response +

Example 8. 

LANMAN-Response: 0102030405060708090A0B0C0D0E0F101112131415161718


NT-Response

The >= 24 byte NT Response calculated from the user's password and the supplied LANMAN Challenge. Typically, this is provided over the network by a client wishing to authenticate. -

Example 9. 

NT-Response: 0102030405060708090A0B0C0D0E0F101112131415161718


Password

The user's password. This would be +

Example 9. 

NT-Response: 0102030405060708090A0B0C0D0E0F101112131415161718


Password

The user's password. This would be provided by a network client, if the helper is being used in a legacy situation that exposes plaintext passwords in this way. -

Example 10. 

Password: samba2


Example 11. 

Password:: c2FtYmEy


Request-User-Session-Key

Apon sucessful authenticaiton, return +

Example 10. 

Password: samba2


Example 11. 

Password:: c2FtYmEy


Request-User-Session-Key

Apon sucessful authenticaiton, return the user session key associated with the login. -

Example 12. 

Request-User-Session-Key: Yes


Request-LanMan-Session-Key

Apon sucessful authenticaiton, return +

Example 12. 

Request-User-Session-Key: Yes


Request-LanMan-Session-Key

Apon sucessful authenticaiton, return the LANMAN session key associated with the login. -

Example 13. 

Request-LanMan-Session-Key: Yes


--username=USERNAME

+

Example 13. 

Request-LanMan-Session-Key: Yes


--username=USERNAME

Specify username of user to authenticate

--domain=DOMAIN

Specify domain of user to authenticate @@ -128,7 +128,7 @@ ".progname" will be appended (e.g. log.smbclient, log.smbd, etc...). The log file is never removed by the client.

-h|--help

Print a summary of command line options. -

EXAMPLE SETUP

To setup ntlm_auth for use by squid 2.5, with both basic and +

EXAMPLE SETUP

To setup ntlm_auth for use by squid 2.5, with both basic and NTLMSSP authentication, the following should be placed in the squid.conf file.

@@ -137,20 +137,20 @@
 auth_param basic children 5
 auth_param basic realm Squid proxy-caching web server
 auth_param basic credentialsttl 2 hours
-

Note

This example assumes that ntlm_auth has been installed into your +

Note

This example assumes that ntlm_auth has been installed into your path, and that the group permissions on winbindd_privileged are as described above.

To setup ntlm_auth for use by squid 2.5 with group limitation in addition to the above example, the following should be added to the squid.conf file.

 auth_param ntlm program ntlm_auth --helper-protocol=squid-2.5-ntlmssp --require-membership-of='WORKGROUP\Domain Users'
 auth_param basic program ntlm_auth --helper-protocol=squid-2.5-basic --require-membership-of='WORKGROUP\Domain Users'
-

TROUBLESHOOTING

If you're experiencing problems with authenticating Internet Explorer running +

TROUBLESHOOTING

If you're experiencing problems with authenticating Internet Explorer running under MS Windows 9X or Millenium Edition against ntlm_auth's NTLMSSP authentication helper (--helper-protocol=squid-2.5-ntlmssp), then please read the Microsoft Knowledge Base article #239869 and follow instructions described there. -

VERSION

This man page is correct for version 3 of the Samba - suite.

AUTHOR

The original Samba software and related utilities +

VERSION

This man page is correct for version 3 of the Samba + suite.

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 ntlm_auth manpage was written by Jelmer Vernooij and diff -u -r --new-file --exclude .svn --exclude CVS samba-3.3.10//docs/htmldocs/manpages/pam_winbind.8.html samba-3.3.11//docs/htmldocs/manpages/pam_winbind.8.html --- samba-3.3.10//docs/htmldocs/manpages/pam_winbind.8.html 2010-01-14 11:20:43.000000000 +0100 +++ samba-3.3.11//docs/htmldocs/manpages/pam_winbind.8.html 2010-02-22 16:53:37.000000000 +0100 @@ -1,6 +1,6 @@ -pam_winbind

Name

pam_winbind — PAM module for Winbind

DESCRIPTION

This tool is part of the samba(7) suite.

+pam_winbind

Name

pam_winbind — PAM module for Winbind

DESCRIPTION

This tool is part of the samba(7) suite.

pam_winbind is a PAM module that can authenticate users against the local domain by talking to the Winbind daemon. -

SYNOPSIS

+

SYNOPSIS

Edit the PAM system config /etc/pam.d/service and modify it as the following example shows:

 			    ...
@@ -19,7 +19,7 @@
 
 		Make sure that pam_winbind is one of the first modules in the session part. It may retrieve
 		kerberos tickets which are needed by other modules.
-	

OPTIONS

+

OPTIONS

pam_winbind supports several options which can either be set in the PAM configuration files or in the pam_winbind configuration @@ -82,7 +82,7 @@ going to expire. Defaults to 14 days.

-

PAM DATA EXPORTS

This section describes the data exported in the PAM stack which could be used in other PAM modules.

PAM_WINBIND_HOMEDIR

+

PAM DATA EXPORTS

This section describes the data exported in the PAM stack which could be used in other PAM modules.

PAM_WINBIND_HOMEDIR

This is the Windows Home Directory set in the profile tab in the user settings on the Active Directory Server. This could be a local path or a directory on a share mapped to a drive. @@ -95,7 +95,7 @@

PAM_WINBIND_PROFILEPATH

This is the profile path set in the profile tab in the user settings. Noramlly the home directory is synced with this directory on a share. -

VERSION

This man page is correct for version 3 of Samba.

AUTHOR

+

VERSION

This man page is correct for version 3 of Samba.

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 and Guenther Deschner.

diff -u -r --new-file --exclude .svn --exclude CVS samba-3.3.10//docs/htmldocs/manpages/pdbedit.8.html samba-3.3.11//docs/htmldocs/manpages/pdbedit.8.html --- samba-3.3.10//docs/htmldocs/manpages/pdbedit.8.html 2010-01-14 11:20:44.000000000 +0100 +++ samba-3.3.11//docs/htmldocs/manpages/pdbedit.8.html 2010-02-22 16:53:37.000000000 +0100 @@ -1,10 +1,10 @@ -pdbedit

Name

pdbedit — manage the SAM database (Database of Samba Users)

Synopsis

pdbedit [-L] [-v] [-w] [-u username] [-f fullname] [-h homedir] [-D drive] [-S script] [-p profile] [-a] [-t, --password-from-stdin] [-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] [-y]

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 (Database of Samba Users)

Synopsis

pdbedit [-L] [-v] [-w] [-u username] [-f fullname] [-h homedir] [-D drive] [-S script] [-p profile] [-a] [-t, --password-from-stdin] [-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] [-y]

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 without changing the tool).

There are five main ways to use pdbedit: adding a user account, removing a user account, modifing a user account, listing user - accounts, importing users accounts.

OPTIONS

-L

This option lists all the user accounts + accounts, importing users accounts.

OPTIONS

-L

This option lists all the user accounts present in the users database. This option prints a list of user/uid pairs separated by the ':' character.

Example: pdbedit -L

@@ -69,7 +69,7 @@
 		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 are listed below.

-

  • N: No password required

  • D: Account disabled

  • H: Home directory required

  • T: Temporary duplicate of other account

  • U: Regular user account

  • M: MNS logon user account

  • W: Workstation Trust Account

  • S: Server Trust Account

  • L: Automatic Locking

  • X: Password does not expire

  • I: Domain Trust Account

+

  • N: No password required

  • D: Account disabled

  • H: Home directory required

  • T: Temporary duplicate of other account

  • U: Regular user account

  • M: MNS logon user account

  • W: Workstation Trust Account

  • S: Server Trust Account

  • L: Automatic Locking

  • X: Password does not expire

  • I: Domain Trust Account

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 @@ -77,7 +77,7 @@

new password:
 retype new password
 

-

Note

pdbedit does not call the unix password syncronisation +

Note

pdbedit does not call the unix password syncronisation script if unix password sync has been set. It only updates the data in the Samba user database. @@ -144,8 +144,8 @@ compile time.

-l|--log-basename=logdirectory

Base directory name for log/debug files. The extension ".progname" will be appended (e.g. log.smbclient, log.smbd, etc...). 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 of - the Samba suite.

AUTHOR

The original Samba software and related utilities +

NOTES

This command may be used only by root.

VERSION

This man page is correct for version 3 of + the Samba suite.

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 pdbedit manpage was written by Simo Sorce and Jelmer Vernooij.

diff -u -r --new-file --exclude .svn --exclude CVS samba-3.3.10//docs/htmldocs/manpages/profiles.1.html samba-3.3.11//docs/htmldocs/manpages/profiles.1.html --- samba-3.3.10//docs/htmldocs/manpages/profiles.1.html 2010-01-14 11:20:45.000000000 +0100 +++ samba-3.3.11//docs/htmldocs/manpages/profiles.1.html 2010-02-22 16:53:37.000000000 +0100 @@ -1,12 +1,12 @@ -profiles

Name

profiles — A utility to report and change SIDs in registry files -

Synopsis

profiles [-v] [-c SID] [-n SID] {file}

DESCRIPTION

This tool is part of the samba(7) suite.

profiles is a utility that +profiles

Name

profiles — A utility to report and change SIDs in registry files +

Synopsis

profiles [-v] [-c SID] [-n SID] {file}

DESCRIPTION

This tool is part of the samba(7) suite.

profiles is a utility that reports and changes SIDs in windows registry files. It currently only supports NT. -

OPTIONS

file

Registry file to view or edit.

-v,--verbose

Increases verbosity of messages. +

OPTIONS

file

Registry file to view or edit.

-v,--verbose

Increases verbosity of messages.

-c SID1 -n SID2

Change all occurences of SID1 in file by SID2.

-h|--help

Print a summary of command line options. -

VERSION

This man page is correct for version 3 of the Samba - suite.

AUTHOR

The original Samba software and related utilities +

VERSION

This man page is correct for version 3 of the Samba + suite.

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 profiles man page was written by Jelmer Vernooij.

diff -u -r --new-file --exclude .svn --exclude CVS samba-3.3.10//docs/htmldocs/manpages/rpcclient.1.html samba-3.3.11//docs/htmldocs/manpages/rpcclient.1.html --- samba-3.3.10//docs/htmldocs/manpages/rpcclient.1.html 2010-01-14 11:20:47.000000000 +0100 +++ samba-3.3.11//docs/htmldocs/manpages/rpcclient.1.html 2010-02-22 16:53:37.000000000 +0100 @@ -1,9 +1,9 @@ -rpcclient

Name

rpcclient — tool for executing client side - MS-RPC functions

Synopsis

rpcclient [-A authfile] [-c <command string>] [-d debuglevel] [-h] [-l logdir] [-N] [-s <smb config file>] [-U username[%password]] [-W workgroup] [-N] [-I destinationIP] {server}

DESCRIPTION

This tool is part of the samba(7) suite.

rpcclient is a utility initially developed +rpcclient

Name

rpcclient — tool for executing client side + MS-RPC functions

Synopsis

rpcclient [-A authfile] [-c <command string>] [-d debuglevel] [-h] [-l logdir] [-N] [-s <smb config file>] [-U username[%password]] [-W workgroup] [-N] [-I destinationIP] {server}

DESCRIPTION

This tool is part of the samba(7) suite.

rpcclient is a utility initially developed to test MS-RPC functionality in Samba itself. It has undergone several stages of development and stability. Many system administrators 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. + 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 below))

-I IP-address

IP address is the address of the server to connect to. @@ -48,6 +48,8 @@ be silently ingnored and no password will be used.

-k|--kerberos

Try to authenticate with kerberos. Only useful in an Active Directory environment. +

-C|--use-ccache

+Try to use the credentials cached by winbind.

-A|--authentication-file=filename

This option allows you to specify a file from which to read the username and password used in the connection. The format of the file is @@ -89,11 +91,11 @@ socket. See the socket options parameter in 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 +

COMMANDS

LSARPC

lsaquery

Query info policy

lookupsids

Resolve a list of SIDs to usernames.

lookupnames

Resolve a list of usernames to SIDs. -

enumtrusts

Enumerate trusted domains

enumprivs

Enumerate privileges

getdispname

Get the privilege name

lsaenumsid

Enumerate the LSA SIDS

lsaenumprivsaccount

Enumerate the privileges of an SID

lsaenumacctrights

Enumerate the rights of an SID

lsaenumacctwithright

Enumerate accounts with a right

lsaaddacctrights

Add rights to an account

lsaremoveacctrights

Remove rights from an account

lsalookupprivvalue

Get a privilege value given its name

lsaquerysecobj

Query LSA security object

LSARPC-DS

dsroledominfo

Get Primary Domain Information

DFS

dfsexist

Query DFS support

dfsadd

Add a DFS share

dfsremove

Remove a DFS share

dfsgetinfo

Query DFS share info

dfsenum

Enumerate dfs shares

REG

shutdown

Remote Shutdown

abortshutdown

Abort Shutdown

SRVSVC

srvinfo

Server query info

netshareenum

Enumerate shares

netfileenum

Enumerate open files

netremotetod

Fetch remote time of day

SAMR

queryuser

Query user info

querygroup

Query group info

queryusergroups

Query user groups

querygroupmem

Query group membership

queryaliasmem

Query alias membership

querydispinfo

Query display info

querydominfo

Query domain info

enumdomusers

Enumerate domain users

enumdomgroups

Enumerate domain groups

enumalsgroups

Enumerate alias groups

createdomuser

Create domain user

samlookupnames

Look up names

samlookuprids

Look up names

deletedomuser

Delete domain user

samquerysecobj

Query SAMR security object

getdompwinfo

Retrieve domain password info

lookupdomain

Look up domain

SPOOLSS

adddriver <arch> <config> [<version>]

+

enumtrusts

Enumerate trusted domains

enumprivs

Enumerate privileges

getdispname

Get the privilege name

lsaenumsid

Enumerate the LSA SIDS

lsaenumprivsaccount

Enumerate the privileges of an SID

lsaenumacctrights

Enumerate the rights of an SID

lsaenumacctwithright

Enumerate accounts with a right

lsaaddacctrights

Add rights to an account

lsaremoveacctrights

Remove rights from an account

lsalookupprivvalue

Get a privilege value given its name

lsaquerysecobj

Query LSA security object

LSARPC-DS

dsroledominfo

Get Primary Domain Information

DFS

dfsexist

Query DFS support

dfsadd

Add a DFS share

dfsremove

Remove a DFS share

dfsgetinfo

Query DFS share info

dfsenum

Enumerate dfs shares

REG

shutdown

Remote Shutdown

abortshutdown

Abort Shutdown

SRVSVC

srvinfo

Server query info

netshareenum

Enumerate shares

netfileenum

Enumerate open files

netremotetod

Fetch remote time of day

SAMR

queryuser

Query user info

querygroup

Query group info

queryusergroups

Query user groups

querygroupmem

Query group membership

queryaliasmem

Query alias membership

querydispinfo

Query display info

querydominfo

Query domain info

enumdomusers

Enumerate domain users

enumdomgroups

Enumerate domain groups

enumalsgroups

Enumerate alias groups

createdomuser

Create domain user

samlookupnames

Look up names

samlookuprids

Look up names

deletedomuser

Delete domain user

samquerysecobj

Query SAMR security object

getdompwinfo

Retrieve domain password info

lookupdomain

Look up domain

SPOOLSS

adddriver <arch> <config> [<version>]

Execute an AddPrinterDriver() RPC to install the printer driver information on the server. Note that the driver files should already exist in the directory returned by @@ -178,11 +180,11 @@ already be correctly installed on the print server.

See also the enumprinters and enumdrivers commands for obtaining a list of of installed printers and drivers.

addform

Add form

setform

Set form

getform

Get form

deleteform

Delete form

enumforms

Enumerate form

setprinter

Set printer comment

setprinterdata

Set REG_SZ printer data

setprintername <printername> - <newprintername>

Set printer name

rffpcnex

Rffpcnex test

NETLOGON

logonctrl2

Logon Control 2

logonctrl

Logon Control

samsync

Sam Synchronisation

samdeltas

Query Sam Deltas

samlogon

Sam Logon

GENERAL COMMANDS

debuglevel

Set the current + <newprintername>

Set printer name

rffpcnex

Rffpcnex test

NETLOGON

logonctrl2

Logon Control 2

logonctrl

Logon Control

samsync

Sam Synchronisation

samdeltas

Query Sam Deltas

samlogon

Sam Logon

GENERAL COMMANDS

debuglevel

Set the current debug level used to log information.

help (?)

Print a listing of all known commands or extended help on a particular command.

quit (exit)

Exit rpcclient - .

BUGS

rpcclient is designed as a developer testing tool + .

BUGS

rpcclient is designed as a developer testing tool and may not be robust in certain areas (such as command line parsing). It has been known to generate a core dump upon failures when invalid parameters where passed to the interpreter.

From Luke Leighton's original rpcclient man page:

WARNING! The MSRPC over SMB code has @@ -195,8 +197,8 @@ versions of smbd(8) and rpcclient(1) that are incompatible for some commands or services. Additionally, the developers are sending reports to Microsoft, and problems found or reported to Microsoft are fixed in Service Packs, which may - result in incompatibilities.

VERSION

This man page is correct for version 3 of the Samba - suite.

AUTHOR

The original Samba software and related utilities + result in incompatibilities.

VERSION

This man page is correct for version 3 of the Samba + suite.

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 rpcclient man page was written by Matthew diff -u -r --new-file --exclude .svn --exclude CVS samba-3.3.10//docs/htmldocs/manpages/samba.7.html samba-3.3.11//docs/htmldocs/manpages/samba.7.html --- samba-3.3.10//docs/htmldocs/manpages/samba.7.html 2010-01-14 11:20:49.000000000 +0100 +++ samba-3.3.11//docs/htmldocs/manpages/samba.7.html 2010-02-22 16:53:36.000000000 +0100 @@ -1,4 +1,4 @@ -samba

Name

samba — A Windows SMB/CIFS fileserver for UNIX

Synopsis

samba

DESCRIPTION

The Samba software suite is a collection of programs +samba

Name

samba — A Windows SMB/CIFS fileserver for UNIX

Synopsis

samba

DESCRIPTION

The Samba software suite is a collection of programs that implements the Server Message Block (commonly abbreviated as SMB) protocol for UNIX systems. This protocol is sometimes also referred to as the Common Internet File System (CIFS). For a @@ -63,7 +63,7 @@ smbmnt(8)

smbmount,smbumount and smbmnt are commands that can be used to mount CIFS/SMB shares on Linux.

smbcquotas(1)

smbcquotas is a tool that - can set remote QUOTA's on server with NTFS 5.

COMPONENTS

The Samba suite is made up of several components. Each + can set remote QUOTA's on server with NTFS 5.

COMPONENTS

The Samba suite is made up of several components. Each component is described in a separate manual page. It is strongly recommended that you read the documentation that comes with Samba and the manual pages of those components that you use. If the @@ -72,7 +72,7 @@ for information on how to file a bug report or submit a patch.

If you require help, visit the Samba webpage at http://www.samba.org/ and explore the many option available to you. -

AVAILABILITY

The Samba software suite is licensed under the +

AVAILABILITY

The Samba software suite is licensed under the GNU Public License(GPL). A copy of that license should have come with the package in the file COPYING. You are encouraged to distribute copies of the Samba suite, but @@ -86,14 +86,14 @@ the README file that comes with Samba.

If you have access to a WWW viewer (such as Mozilla or Konqueror) then you will also find lots of useful information, including back issues of the Samba mailing list, at - http://lists.samba.org.

VERSION

This man page is correct for version 3 of the - Samba suite.

CONTRIBUTIONS

If you wish to contribute to the Samba project, + http://lists.samba.org.

VERSION

This man page is correct for version 3 of the + Samba suite.

CONTRIBUTIONS

If you wish to contribute to the Samba project, then I suggest you join the Samba mailing list at http://lists.samba.org.

If you have patches to submit, visit http://devel.samba.org/ for information on how to do it properly. We prefer patches - in diff -u format.

CONTRIBUTORS

Contributors to the project are now too numerous + in diff -u format.

CONTRIBUTORS

Contributors to the project are now too numerous to mention here but all deserve the thanks of all Samba users. To see a full list, look at the change-log in the source package @@ -101,7 +101,7 @@ http://cvs.samba.org/ for the contributors to Samba post-CVS. CVS is the Open Source source code control system used by the Samba Team to develop - Samba. The project would have been unmanageable without it.

AUTHOR

The original Samba software and related utilities + Samba. The project would have been unmanageable without it.

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 -u -r --new-file --exclude .svn --exclude CVS samba-3.3.10//docs/htmldocs/manpages/sharesec.1.html samba-3.3.11//docs/htmldocs/manpages/sharesec.1.html --- samba-3.3.10//docs/htmldocs/manpages/sharesec.1.html 2010-01-14 11:20:50.000000000 +0100 +++ samba-3.3.11//docs/htmldocs/manpages/sharesec.1.html 2010-02-22 16:53:37.000000000 +0100 @@ -1,5 +1,5 @@ -sharesec

Name

sharesec — Set or get share ACLs

Synopsis

sharesec {sharename} [-r, --remove=ACL] [-m, --modify=ACL] [-a, --add=ACL] [-R, --replace=ACLs] [-D, --delete] [-v, --view] [-M, --machine-sid] [-F, --force] [-d, --debuglevel=DEBUGLEVEL] [-s, --configfile=CONFIGFILE] [-l, --log-basename=LOGFILEBASE] [-V, --version] [-?, --help] [--usage]

DESCRIPTION

This tool is part of the samba(7) suite.

The sharesec program manipulates share permissions - on SMB file shares.

OPTIONS

The following options are available to the sharesec program. +sharesec

Name

sharesec — Set or get share ACLs

Synopsis

sharesec {sharename} [-r, --remove=ACL] [-m, --modify=ACL] [-a, --add=ACL] [-R, --replace=ACLs] [-D, --delete] [-v, --view] [-M, --machine-sid] [-F, --force] [-d, --debuglevel=DEBUGLEVEL] [-s, --configfile=CONFIGFILE] [-l, --log-basename=LOGFILEBASE] [-V, --version] [-?, --help] [--usage]

DESCRIPTION

This tool is part of the samba(7) suite.

The sharesec program manipulates share permissions + on SMB file shares.

OPTIONS

The following options are available to the sharesec program. The format of ACLs is described in the section ACL FORMAT

-a|--add=ACL

Add the ACEs specified to the ACL list.

-D|--delete

Delete the entire security descriptor.

-F|--force

Force storing the ACL. @@ -33,7 +33,7 @@ compile time.

-l|--log-basename=logdirectory

Base directory name for log/debug files. The extension ".progname" will be appended (e.g. log.smbclient, log.smbd, etc...). The log file is never removed by the client. -

ACL FORMAT

The format of an ACL is one or more ACL entries separated by +

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:

 	REVISION:<revision number>
 	OWNER:<sid or name>
@@ -54,16 +54,16 @@
 	

The mask is a value which expresses the access right granted to the SID. It can be given as a decimal or hexadecimal value, or by using one of the following text strings which map to the NT - file permissions of the same name.

  • R - Allow read access

  • W - Allow write access

  • X - Execute permission on the object

  • D - Delete the object

  • P - Change permissions

  • O - Take ownership

The following combined permissions can be specified:

  • READ - Equivalent to 'RX' - permissions

  • CHANGE - Equivalent to 'RXWD' permissions -

  • FULL - Equivalent to 'RWXDPO' - permissions

EXIT STATUS

The sharesec program sets the exit status + file permissions of the same name.

  • R - Allow read access

  • W - Allow write access

  • X - Execute permission on the object

  • D - Delete the object

  • P - Change permissions

  • O - Take ownership

The following combined permissions can be specified:

  • READ - Equivalent to 'RX' + permissions

  • CHANGE - Equivalent to 'RXWD' permissions +

  • FULL - Equivalent to 'RWXDPO' + permissions

EXIT STATUS

The sharesec program sets the exit status depending on the success or otherwise of the operations performed. The exit status may be one of the following values.

If the operation succeeded, sharesec returns and exit status of 0. If sharesec couldn't connect to the specified server, or there was an error getting or setting the ACLs, an exit status of 1 is returned. If there was an error parsing any command line - arguments, an exit status of 2 is returned.

EXAMPLES

Add full access for SID + arguments, an exit status of 2 is returned.

EXAMPLES

Add full access for SID S-1-5-21-1866488690-1365729215-3963860297-17724 on share:

@@ -76,7 +76,7 @@
 	GROUP:(NULL SID)
 	ACL:S-1-1-0:ALLOWED/0/0x101f01ff
 	ACL:S-1-5-21-1866488690-1365729215-3963860297-17724:ALLOWED/0/FULL
-	

VERSION

This man page is correct for version 3 of the Samba suite.

AUTHOR

The original Samba software and related utilities +

VERSION

This man page is correct for version 3 of the Samba suite.

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.

diff -u -r --new-file --exclude .svn --exclude CVS samba-3.3.10//docs/htmldocs/manpages/smbcacls.1.html samba-3.3.11//docs/htmldocs/manpages/smbcacls.1.html --- samba-3.3.10//docs/htmldocs/manpages/smbcacls.1.html 2010-01-14 11:20:51.000000000 +0100 +++ samba-3.3.11//docs/htmldocs/manpages/smbcacls.1.html 2010-02-22 16:53:37.000000000 +0100 @@ -1,5 +1,5 @@ -smbcacls

Name

smbcacls — Set or get ACLs on an NT file or directory names

Synopsis

smbcacls {//server/share} {filename} [-D acls] [-M acls] [-a acls] [-S acls] [-C name] [-G name] [--numeric] [-t] [-U username] [-h] [-d]

DESCRIPTION

This tool is part of the samba(7) suite.

The smbcacls program manipulates NT Access Control - Lists (ACLs) on SMB file shares.

OPTIONS

The following options are available to the smbcacls program. +smbcacls

Name

smbcacls — Set or get ACLs on an NT file or directory names

Synopsis

smbcacls {//server/share} {filename} [-D acls] [-M acls] [-a acls] [-S acls] [-C name] [-G name] [--numeric] [-t] [-U username] [-h] [-d]

DESCRIPTION

This tool is part of the samba(7) suite.

The smbcacls program manipulates NT Access Control + Lists (ACLs) on SMB file shares.

OPTIONS

The following options are available to the smbcacls program. The format of ACLs is described in the section ACL FORMAT

-a acls

Add the ACLs specified to the ACL list. Existing access control entries are unchanged.

-M acls

Modify the mask value (permissions) for the ACLs specified on the command line. An error will be printed for each @@ -52,7 +52,7 @@ compile time.

-l|--log-basename=logdirectory

Base directory name for log/debug files. The extension ".progname" will be appended (e.g. log.smbclient, log.smbd, etc...). The log file is never removed by the client. -

ACL FORMAT

The format of an ACL is one or more ACL entries separated by +

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:

 
 REVISION:<revision number>
 OWNER:<sid or name>
@@ -70,20 +70,20 @@
 	resides.  The type, flags and mask values determine the type of 
 	access granted to the SID. 

The type can be either ALLOWED or DENIED to allow/deny access to the SID. The flags values are generally zero for file ACLs and - either 9 or 2 for directory ACLs. Some common flags are:

  • #define SEC_ACE_FLAG_OBJECT_INHERIT 0x1

  • #define SEC_ACE_FLAG_CONTAINER_INHERIT 0x2

  • #define SEC_ACE_FLAG_NO_PROPAGATE_INHERIT 0x4

  • #define SEC_ACE_FLAG_INHERIT_ONLY 0x8

At present flags can only be specified as decimal or + either 9 or 2 for directory ACLs. Some common flags are:

  • #define SEC_ACE_FLAG_OBJECT_INHERIT 0x1

  • #define SEC_ACE_FLAG_CONTAINER_INHERIT 0x2

  • #define SEC_ACE_FLAG_NO_PROPAGATE_INHERIT 0x4

  • #define SEC_ACE_FLAG_INHERIT_ONLY 0x8

At present flags can only be specified as decimal or hexadecimal values.

The mask is a value which expresses the access right granted to the SID. It can be given as a decimal or hexadecimal value, or by using one of the following text strings which map to the NT - file permissions of the same name.

  • R - Allow read access

  • W - Allow write access

  • X - Execute permission on the object

  • D - Delete the object

  • P - Change permissions

  • O - Take ownership

The following combined permissions can be specified:

  • READ - Equivalent to 'RX' - permissions

  • CHANGE - Equivalent to 'RXWD' permissions -

  • FULL - Equivalent to 'RWXDPO' - permissions

EXIT STATUS

The smbcacls program sets the exit status + file permissions of the same name.

  • R - Allow read access

  • W - Allow write access

  • X - Execute permission on the object

  • D - Delete the object

  • P - Change permissions

  • O - Take ownership

The following combined permissions can be specified:

  • READ - Equivalent to 'RX' + permissions

  • CHANGE - Equivalent to 'RXWD' permissions +

  • FULL - Equivalent to 'RWXDPO' + permissions

EXIT STATUS

The smbcacls program sets the exit status depending on the success or otherwise of the operations performed. The exit status may be one of the following values.

If the operation succeeded, smbcacls returns and exit status of 0. If smbcacls couldn't connect to the specified server, or there was an error getting or setting the ACLs, an exit status of 1 is returned. If there was an error parsing any command line - arguments, an exit status of 2 is returned.

VERSION

This man page is correct for version 3 of the Samba suite.

AUTHOR

The original Samba software and related utilities + arguments, an exit status of 2 is returned.

VERSION

This man page is correct for version 3 of the Samba suite.

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.

smbcacls was written by Andrew Tridgell diff -u -r --new-file --exclude .svn --exclude CVS samba-3.3.10//docs/htmldocs/manpages/smbclient.1.html samba-3.3.11//docs/htmldocs/manpages/smbclient.1.html --- samba-3.3.10//docs/htmldocs/manpages/smbclient.1.html 2010-01-14 11:20:53.000000000 +0100 +++ samba-3.3.11//docs/htmldocs/manpages/smbclient.1.html 2010-02-22 16:53:37.000000000 +0100 @@ -1,11 +1,11 @@ -smbclient

Name

smbclient — ftp-like client to access SMB/CIFS resources - on servers

Synopsis

smbclient [-b <buffer size>] [-d debuglevel] [-e] [-L <netbios name>] [-U username] [-I destinationIP] [-M <netbios name>] [-m maxprotocol] [-A authfile] [-N] [-g] [-i scope] [-O <socket options>] [-p port] [-R <name resolve order>] [-s <smb config file>] [-k] [-P] [-c <command>]

smbclient {servicename} [password] [-b <buffer size>] [-d debuglevel] [-e] [-D Directory] [-U username] [-W workgroup] [-M <netbios name>] [-m maxprotocol] [-A authfile] [-N] [-g] [-l log-basename] [-I destinationIP] [-E] [-c <command string>] [-i scope] [-O <socket options>] [-p port] [-R <name resolve order>] [-s <smb config file>] [-T<c|x>IXFqgbNan] [-k]

DESCRIPTION

This tool is part of the samba(7) suite.

smbclient is a client that can +smbclient

Name

smbclient — ftp-like client to access SMB/CIFS resources + on servers

Synopsis

smbclient [-b <buffer size>] [-d debuglevel] [-e] [-L <netbios name>] [-U username] [-I destinationIP] [-M <netbios name>] [-m maxprotocol] [-A authfile] [-N] [-g] [-i scope] [-O <socket options>] [-p port] [-R <name resolve order>] [-s <smb config file>] [-k] [-P] [-c <command>]

smbclient {servicename} [password] [-b <buffer size>] [-d debuglevel] [-e] [-D Directory] [-U username] [-W workgroup] [-M <netbios name>] [-m maxprotocol] [-A authfile] [-N] [-g] [-l log-basename] [-I destinationIP] [-E] [-c <command string>] [-i scope] [-O <socket options>] [-p port] [-R <name resolve order>] [-s <smb config file>] [-T<c|x>IXFqgbNan] [-k]

DESCRIPTION

This tool is part of the samba(7) suite.

smbclient is a client that can 'talk' to an SMB/CIFS server. It offers an interface similar to that of the ftp program (see ftp(1)). Operations include things like getting files from the server to the local machine, putting files from the local machine to the server, retrieving directory information from the server - and so on.

OPTIONS

servicename

servicename is the name of the service + and so on.

OPTIONS

servicename

servicename is the name of the service you want to use on the server. A service name takes the form //server/service where server is the NetBIOS name of the SMB/CIFS server @@ -40,21 +40,21 @@ suite 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". They - cause names to be resolved as follows:

  • lmhosts: Lookup an IP + 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 - any name type matches for lookup.

    • host: Do a standard host + any name type matches for lookup.

    • host: Do a standard host name to IP address resolution, using the system /etc/hosts , NIS, or DNS lookups. This method of name resolution is operating system dependent, for instance on IRIX or Solaris this may be controlled by the /etc/nsswitch.conf file). Note that this method is only used if the NetBIOS name type being queried is the 0x20 (server) name type, otherwise - it is ignored.

    • wins: Query a name with + it is ignored.

    • wins: Query a name with the IP address listed in the wins server parameter. If no WINS server has - been specified this method will be ignored.

    • bcast: Do a broadcast on + been specified this method will be ignored.

    • bcast: Do a broadcast on each of the known local interfaces listed in the interfaces parameter. This is the least reliable of the name resolution @@ -161,6 +161,8 @@ be silently ingnored and no password will be used.

-k|--kerberos

Try to authenticate with kerberos. Only useful in an Active Directory environment. +

-C|--use-ccache

+Try to use the credentials cached by winbind.

-A|--authentication-file=filename

This option allows you to specify a file from which to read the username and password used in the connection. The format of the file is @@ -204,48 +206,48 @@ 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 - are :

  • c - Create a tar file on UNIX. + are :

    • c - Create a tar file on UNIX. Must be followed by the name of a tar file, tape device or "-" for standard output. If using standard output you must turn the log level to its lowest value -d0 to avoid corrupting your tar file. This flag is mutually exclusive with the - x flag.

    • x - Extract (restore) a local + x flag.

    • x - Extract (restore) a local tar file back to a share. Unless the -D option is given, the tar files will be restored from the top level of the share. Must be followed by the name of the tar file, device or "-" for standard input. Mutually exclusive with the c flag. Restored files have their creation times (mtime) set to the date saved in the tar file. Directories currently do not get - their creation dates restored properly.

    • I - Include files and directories. + their creation dates restored properly.

    • I - Include files and directories. Is the default behavior when filenames are specified above. Causes files to be included in an extract or create (and therefore everything else to be excluded). See example below. Filename globbing - works in one of two ways. See r below.

    • X - Exclude files and directories. + works in one of two ways. See r below.

    • X - Exclude files and directories. Causes files to be excluded from an extract or create. See example below. Filename globbing works in one of two ways now. - See r below.

    • F - File containing a list of files and directories. + See r below.

    • F - File containing a list of files and directories. The F causes the name following the tarfile to create to be read as a filename that contains a list of files and directories to be included in an extract or create (and therefore everything else to be excluded). See example below. Filename globbing works in one of two ways. See r below. -

    • b - Blocksize. Must be followed +

    • b - Blocksize. Must be followed by a valid (greater than zero) blocksize. Causes tar file to be written out in blocksize*TBLOCK (usually 512 byte) blocks. -

    • g - Incremental. Only back up +

    • g - Incremental. Only back up files that have the archive bit set. Useful only with the - c flag.

    • q - Quiet. Keeps tar from printing + c flag.

    • q - Quiet. Keeps tar from printing diagnostics as it works. This is the same as tarmode quiet. -

    • r - Regular expression include +

    • r - Regular expression include or exclude. Uses regular expression matching for excluding or excluding files if compiled with HAVE_REGEX_H. However this mode can be very slow. If not compiled with HAVE_REGEX_H, does a limited wildcard match on '*' and '?'. -

    • N - Newer than. Must be followed +

    • N - Newer than. Must be followed by the name of a file whose date is compared against files found on the share during a create. Only files newer than the file specified are backed up to the tar file. Useful only with the - c flag.

    • a - Set archive bit. Causes the + c flag.

    • a - Set archive bit. Causes the archive bit to be reset when a file is backed up. Useful with the g and c flags.

    Tar Long File Names

    smbclient's tar option now supports long @@ -270,7 +272,7 @@ only of any use with the tar -T option.

-c command string

command string is a semicolon-separated list of commands to be executed instead of prompting from stdin. -N is implied by -c.

This is particularly useful in scripts and for printing stdin - to the server, e.g. -c 'print -'.

OPERATIONS

Once the client is running, the user is presented with + to the server, e.g. -c 'print -'.

OPERATIONS

Once the client is running, the user is presented with a prompt :

smb:\>

The backslash ("\\") indicates the current working directory on the server, and will change if the current working directory is changed.

The prompt indicates that the client is ready and waiting to @@ -468,14 +470,14 @@

vuid <number>

Changes the currently used vuid in the protocol to the given arbitrary number. Without an argument prints out the current vuid being used. Used for internal Samba testing purposes. -

NOTES

Some servers are fussy about the case of supplied usernames, +

NOTES

Some servers are fussy about the case of supplied usernames, passwords, share names (AKA service names) and machine names. If you fail to connect try giving all parameters in uppercase.

It is often necessary to use the -n option when connecting to some types of servers. For example OS/2 LanManager insists on a valid NetBIOS name being used, so you need to supply a valid name that would be known to the server.

smbclient supports long file names where the server - supports the LANMAN2 protocol or above.

ENVIRONMENT VARIABLES

The variable USER may contain the + supports the LANMAN2 protocol or above.

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 PASSWD may contain @@ -485,7 +487,7 @@ the path, executed with system(), which the client should connect to instead of connecting to a server. This functionality is primarily intended as a development aid, and works best when using a LMHOSTS - file

INSTALLATION

The location of the client program is a matter for + file

INSTALLATION

The location of the client program is a matter for individual system administrators. The following are thus suggestions only.

It is recommended that the smbclient software be installed in the /usr/local/samba/bin/ or @@ -496,11 +498,11 @@ and writeable only by the user.

To test the client, you will need to know the name of a running SMB/CIFS server. It is possible to run smbd(8) as an ordinary user - running that server as a daemon on a user-accessible port (typically any port number over 1024) - would provide a suitable test server.

DIAGNOSTICS

Most diagnostics issued by the client are logged in a + would provide a suitable test server.

DIAGNOSTICS

Most diagnostics issued by the client are logged in a specified log file. The log file name is specified at compile time, but may be overridden on the command line.

The number and nature of diagnostics available depends on the debug level used by the client. If you have problems, - set the debug level to 3 and peruse the log files.

VERSION

This man page is correct for version 3.2 of the Samba suite.

AUTHOR

The original Samba software and related utilities + set the debug level to 3 and peruse the log files.

VERSION

This man page is correct for version 3.2 of the Samba suite.

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 -u -r --new-file --exclude .svn --exclude CVS samba-3.3.10//docs/htmldocs/manpages/smb.conf.5.html samba-3.3.11//docs/htmldocs/manpages/smb.conf.5.html --- samba-3.3.10//docs/htmldocs/manpages/smb.conf.5.html 2010-01-14 11:21:10.000000000 +0100 +++ samba-3.3.11//docs/htmldocs/manpages/smb.conf.5.html 2010-02-22 16:53:37.000000000 +0100 @@ -1,9 +1,9 @@ -smb.conf

Name

smb.conf — The configuration file for the Samba suite

SYNOPSIS

+smb.conf

Name

smb.conf — The configuration file for the Samba suite

SYNOPSIS

The smb.conf file is a configuration file for the Samba suite. smb.conf contains runtime configuration information for the Samba programs. The smb.conf file is designed to be configured and administered by the swat(8) program. The complete description of the file format and possible parameters held within are here for reference purposes. -

FILE FORMAT

+

FILE FORMAT

The file consists of sections and parameters. A section begins with the name of the section in square brackets and continues until the next section begins. Sections contain parameters of the form:

@@ -18,17 +18,17 @@
 	and trailing whitespace in a parameter value is discarded. Internal whitespace within a parameter value is
 	retained verbatim.
 	

- Any line beginning with a semicolon (;) or a hash (#) + Any line beginning with a semicolon (“;”) or a hash (“#”) character is ignored, as are lines containing only whitespace.

- Any line ending in a \ is continued on the next line in the customary UNIX fashion. + Any line ending in a “\” is continued on the next line in the customary UNIX fashion.

The values following the equals sign in parameters are all either a string (no quotes needed) or a boolean, which may be given as yes/no, 1/0 or true/false. Case is not significant in boolean values, but is preserved in string values. Some items such as create masks are numeric. -

SECTION DESCRIPTIONS

+

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 shared resource and the parameters within the + 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 described under @@ -69,10 +69,10 @@ printable = yes guest ok = yes

-

SPECIAL SECTIONS

The [global] section

+

SPECIAL SECTIONS

The [global] section

Parameters in this section apply to the server as a whole, or are defaults for sections that do not specifically define certain items. See the notes under PARAMETERS for more information. -

The [homes] section

+

The [homes] section

If a section called [homes] is included in the configuration file, services connecting clients to their home directories can be created on the fly by the server.

@@ -82,9 +82,9 @@ [homes] section.

Some modifications are then made to the newly created share: -

  • +

    • The share name is changed from homes to the located username. -

    • +

    • If no path was given, the path is set to the user's home directory.

    If you decide to use a path = line in your [homes] section, it may be useful @@ -97,7 +97,7 @@ 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 + A similar process occurs if the requested section 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.

    @@ -115,7 +115,7 @@ The browseable flag for auto home directories will be inherited from the global browseable flag, not the [homes] browseable flag. This is useful as it means setting browseable = no in the [homes] section will hide the [homes] share but make any auto home directories visible. -

The [printers] section

+

The [printers] section

This section works like [homes], but for printers.

If a [printers] section occurs in the configuration file, users are able to connect to any printer @@ -128,7 +128,7 @@ [printers] section.

A few modifications are then made to the newly created share: -

  • The share name is set to the located printer name

  • If no printer name was given, the printer name is set to the located printer name

  • If the share does not permit guest access and no username was given, the username is set +

    • The share name is set to the located printer name

    • If no printer name was given, the printer name is set to the located printer name

    • If the share does not permit guest access and no username was given, the username is set to the located printer name.

    The [printers] service MUST be printable - if you specify otherwise, the server will refuse to load the configuration file. @@ -156,11 +156,11 @@

    An alias, by the way, is defined as any component of the first entry of a printcap record. Records are separated by newlines, components (if there are more than one) are separated by vertical bar symbols (|). -

    Note

    +

    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 for more details. -

USERSHARES

Starting with Samba version 3.0.23 the capability for non-root users to add, modify, and delete +

USERSHARES

Starting with Samba version 3.0.23 the capability for non-root users to add, modify, and delete their own share definitions has been added. This capability is called usershares and is controlled by a set of parameters in the [global] section of the smb.conf. The relevant parameters are : @@ -184,7 +184,7 @@ to the global section of your smb.conf. Members of the group foo may then manipulate the user defined shares - using the following commands.

net usershare add sharename path [comment] [acl] [guest_ok=[y|n]]

To create or modify (overwrite) a user defined share.

net usershare delete sharename

To delete a user defined share.

net usershare list wildcard-sharename

To list user defined shares.

net usershare info wildcard-sharename

To print information about user defined shares.

PARAMETERS

Parameters define the specific attributes of sections.

+ using the following commands.

net usershare add sharename path [comment] [acl] [guest_ok=[y|n]]

To create or modify (overwrite) a user defined share.

net usershare delete sharename

To delete a user defined share.

net usershare list wildcard-sharename

To list user defined shares.

net usershare info wildcard-sharename

To print information about user defined shares.

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 mask). All others are permissible only in normal sections. For the purposes of the following descriptions the [homes] and [printers] sections will be @@ -196,9 +196,9 @@ Parameters are arranged here in alphabetical order - this may 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

+

VARIABLE SUBSTITUTIONS

Many of the strings that are settable in the config file can take substitutions. For example the option - path = /tmp/%u is interpreted as path = /tmp/john if the user connected with the + “path = /tmp/%u” is 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 @@ -210,7 +210,7 @@ 139. This will cause Samba to not listen on port 445 and will permit include functionality to function as it did with Samba 2.x.

%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. + the client calls you. Your server can have a “dual personality”.

%M

the Internet name of the client machine.

%R

the selected protocol level after protocol negotiation. It can be one of CORE, COREPLUS, LANMAN1, LANMAN2 or NT1.

%d

the process id of the current server @@ -238,7 +238,7 @@ 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

+

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.

@@ -276,50 +276,50 @@ options are set as follows, "case sensitive = yes", "case preserve = no", "short preserve case = no" then the "default case" option will be applied and will modify all filenames sent from the client when accessing this share. -

NOTE ABOUT USERNAME/PASSWORD VALIDATION

+

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, the connection request is rejected. However, if one of the steps succeeds, 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 1 to 5 are skipped. -

  1. + If the service is marked “guest only = yes” and the server is running with share-level + security (“security = share”, 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, the connection is made as that username. This includes the \\server\service%username method of passing a username. -

    2. +

    3. If the client has previously registered a username with the system and now supplies a correct password for that username, the connection is allowed. -

    4. +

    5. The client's NetBIOS name and any previously used usernames are checked against the supplied password. If they match, the connection is allowed as the corresponding user. -

    6. +

    7. If the client has previously validated a username/password pair with the server and the client has passed the validation token, that username is used. -

    8. +

    9. 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, the connection is made as the username in the user = line. If one of the usernames in the user = list begins with a @, that name expands to a list of names in the group of the same name. -

    10. +

    11. If the service is a guest service, a connection is made as the username given in the guest account = for the service, irrespective of the supplied password. -

REGISTRY-BASED CONFIGURATION

+

REGISTRY-BASED CONFIGURATION

Starting with Samba version 3.2.0, the capability to store Samba configuration in the registry is available. The configuration is stored in the registry key HKLM\Software\Samba\smbconf. There are two levels of registry configuration: -

  1. Share definitions stored in registry are used. +

    1. Share definitions stored in registry are used. This is triggered by setting the global parameter registry shares - to yes in smb.conf. + to “yes” in smb.conf.

      The registry shares are loaded not at startup but on demand at runtime by smbd. Shares defined in smb.conf take priority over shares of the same name defined in - registry.

    2. Global smb.conf + registry.

    3. Global smb.conf options stored in registry are used. This can be activated in two different ways:

      Firstly, a registry only configuration is triggered by setting @@ -360,19 +360,19 @@ registry based configuration locally, i.e. directly accessing the database file, circumventing the server. -

    EXPLANATION OF EACH PARAMETER

    +

    EXPLANATION OF EACH PARAMETER

    abort shutdown script (G) -

    This a full path name to a script called by smbd(8) that +

    This a full path name to a script called by smbd(8) that should stop a shutdown procedure issued by the shutdown script.

    If the connected user posseses the SeRemoteShutdownPrivilege, right, this command will be run as root.

    Default: abort shutdown script = ""

    Example: abort shutdown script = /sbin/shutdown -c -

    +

    acl check permissions (S) -

    This boolean parameter controls what smbd(8)does on receiving a protocol request of "open for delete" +

    This boolean parameter controls what smbd(8)does on receiving a protocol request of "open for delete" from a Windows client. If a Windows client doesn't have permissions to delete a file then they expect this to be denied at open time. POSIX systems normally only detect restrictions on delete by actually attempting to delete the file or directory. As Windows clients can (and do) "back out" a @@ -392,10 +392,10 @@ with slightly different semantics was introduced in 3.0.20. That older version is not documented here.

    Default: acl check permissions = True -

    +

    acl compatibility (G) -

    This parameter specifies what OS ACL semantics should +

    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 @@ -404,10 +404,10 @@

    Example: acl compatibility = win2k -

    +

    acl group control (S) -

    +

    In a POSIX filesystem, only the owner of a file or directory and the superuser can modify the permissions and ACLs on a file. If this parameter is set, then Samba overrides this restriction, and also allows the primary group owner of a file or directory to modify the permissions and ACLs @@ -434,10 +434,10 @@ dos filemode option.

    Default: acl group control = no -

    +

    acl map full control (S) -

    +

    This boolean parameter controls whether smbd(8)maps a POSIX ACE entry of "rwx" (read/write/execute), the maximum allowed POSIX permission set, into a Windows ACL of "FULL CONTROL". If this parameter is set to true any POSIX ACE entry of "rwx" will be returned in a Windows ACL as "FULL CONTROL", is this parameter is set to false any @@ -445,10 +445,10 @@ execute.

    Default: acl map full control = True -

    +

    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 domain administration tools. The script is free to create a group with @@ -458,10 +458,10 @@

    Example: add group script = /usr/sbin/groupadd %g -

    +

    add machine script (G) -

    +

    This is the full pathname to a script that will be run by smbd(8) when a machine is added to Samba's domain and a Unix account matching the machine's name appended with a "$" does not @@ -472,22 +472,22 @@

    Example: add machine script = /usr/sbin/adduser -n -g machines -c Machine -d /var/lib/nobody -s /bin/false %u -

    +

    add port command (G) -

    Samba 3.0.23 introduced support for adding printer ports +

    Samba 3.0.23 introduced support for adding printer ports remotely using the Windows "Add Standard TCP/IP Port Wizard". This option defines an external program to be executed when smbd receives a request to add a new Port to the system. - The script is passed two parameters:

    • port name

    • device URI

    The deviceURI is in the for of socket://<hostname>[:<portnumber>] + The script is passed two parameters:

    • port name

    • device URI

    The deviceURI is in the for of socket://<hostname>[:<portnumber>] or lpd://<hostname>/<queuename>.

    Default: add port command =

    Example: add port command = /etc/samba/scripts/addport.sh -

    +

    addprinter command (G) -

    With the introduction of MS-RPC based printing +

    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 @@ -501,7 +501,7 @@ to the smb.conf file in order that it can be 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 + 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 only. The remaining fields in the structure are generated from answers @@ -518,10 +518,10 @@

    Example: addprinter command = /usr/bin/addprinter -

    +

    add share command (G) -

    +

    Samba 2.2.0 introduced the ability to dynamically add and delete shares via the Windows NT 4.0 Server Manager. The add share command is used to define an external program or script which will add a new service definition to @@ -537,13 +537,13 @@

    When executed, smbd will automatically invoke the add share command with five parameters. -

    • configFile - the location of the global smb.conf file. -

    • shareName - the name of the new share. -

    • pathName - path to an **existing** +

      • configFile - the location of the global smb.conf file. +

      • shareName - the name of the new share. +

      • pathName - path to an **existing** directory on disk. -

      • comment - comment string to associate with the new +

      • comment - comment string to associate with the new share. -

      • max +

      • max connections Number of maximum simultaneous connections to this share. @@ -553,10 +553,10 @@

        Example: add share command = /usr/local/bin/addshare -

    +

    add user script (G) -

    +

    This is the full pathname to a script that will be run AS ROOT by smbd(8) under special circumstances described below. @@ -591,10 +591,10 @@

    Example: add user script = /usr/local/samba/bin/add_user %u -

    +

    add user to group script (G) -

    +

    Full path to the script that will be called when a user is added to a group using the Windows NT domain administration tools. It will be run by smbd(8) AS ROOT. Any %g will be replaced with the group name and @@ -606,20 +606,20 @@

    Example: add user to group script = /usr/sbin/adduser %u %g -

    +

    administrative share (S) -

    If this parameter is set to yes for +

    If this parameter is set to yes for a share, then the share will be an administrative share. The Administrative Shares are the default network shares created by all Windows NT-based operating systems. These are shares like C$, D$ or ADMIN$. The type of these shares is STYPE_DISKTREE_HIDDEN.

    See the section below on security for more information about this option.

    Default: administrative share = no -

    +

    admin users (S) -

    This is a list of users who will be granted +

    This is a list of users who will be granted administrative privileges on the share. This means that they will do all file operations as the super-user (root).

    You should use this option very carefully, as any user in this list will be able to do anything they like on the share, @@ -628,20 +628,20 @@

    Example: admin users = jason -

    +

    afs share (S) -

    This parameter controls whether special AFS features are enabled +

    This parameter controls whether special AFS features are enabled for this share. If enabled, it assumes that the directory exported via the path parameter is a local AFS import. The special AFS features include the attempt to hand-craft an AFS token if you enabled --with-fake-kaserver in configure.

    Default: afs share = no -

    +

    afs username map (G) -

    If you are using the fake kaserver AFS feature, you might +

    If you are using the fake kaserver AFS feature, you might want to hand-craft the usernames you are creating tokens for. For example this is necessary if you have users from several domain in your AFS Protection Database. One possible scheme to code users @@ -651,10 +651,10 @@

    Example: afs username map = %u@afs.samba.org -

    +

    aio read size (S) -

    If Samba has been built with asynchronous I/O support and this +

    If Samba has been built with asynchronous I/O support and this integer parameter is set to non-zero value, Samba will read from file asynchronously when size of request is bigger than this value. Note that it happens only for non-chained and non-chaining @@ -665,10 +665,10 @@ # Use asynchronous I/O for reads bigger than 16KB request size -

    +

    aio write behind (S) -

    If Samba has been built with asynchronous I/O support, +

    If Samba has been built with asynchronous I/O support, Samba will not wait until write requests are finished before returning the result to the client for files listed in this parameter. Instead, Samba will immediately return that the write @@ -683,10 +683,10 @@

    Example: aio write behind = /*.tmp/ -

    +

    aio write size (S) -

    If Samba has been built with asynchronous I/O support and this +

    If Samba has been built with asynchronous I/O support and this integer parameter is set to non-zero value, Samba will write to file asynchronously when size of request is bigger than this value. Note that it happens only for non-chained and non-chaining @@ -697,10 +697,10 @@ # Use asynchronous I/O for writes bigger than 16KB request size -

    +

    algorithmic rid base (G) -

    This determines how Samba will use its +

    This determines how Samba will use its algorithmic mapping from uids/gid to the RIDs needed to construct NT Security Identifiers.

    Setting this option to a larger value could be useful to sites @@ -715,10 +715,10 @@

    Example: algorithmic rid base = 100000 -

    +

    allocation roundup size (S) -

    This parameter allows an administrator to tune the +

    This parameter allows an administrator to tune the allocation size reported to Windows clients. The default size of 1Mb generally results in improved Windows client performance. However, rounding the allocation size may cause @@ -730,10 +730,10 @@

    Example: allocation roundup size = 0 # (to disable roundups) -

    +

    allow trusted domains (G) -

    +

    This option only takes effect when the security option is set to server, domain or ads. If it is set to no, then attempts to connect to a resource from @@ -748,10 +748,10 @@ 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 +

    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, @@ -763,20 +763,20 @@

    Example: announce as = Win95 -

    +

    announce version (G) -

    This specifies the major and minor version numbers +

    This specifies the major and minor version numbers that nmbd will use when announcing itself as a server. The default is 4.9. Do not change this parameter unless you have a specific need to set a Samba server to be a downlevel server.

    Default: announce version = 4.9

    Example: announce version = 2.0 -

    +

    auth methods (G) -

    +

    This option allows the administrator to chose what authentication methods smbd will use when authenticating a user. This option defaults to sensible values based on security. This should be considered a developer option and used only in rare circumstances. In the majority (if not all) @@ -797,18 +797,18 @@

    Example: auth methods = guest sam winbind -

    +

    available (S) -

    This parameter lets you "turn off" a service. If +

    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 +

    This global parameter allows the Samba admin to limit what interfaces on a machine will serve SMB requests. It 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 @@ -849,10 +849,10 @@ from starting/stopping/restarting smbd and nmbd.

    Default: bind interfaces only = no -

    +

    blocking locks (S) -

    This parameter controls the behavior +

    This parameter controls the behavior of smbd(8) when given a request by a client to obtain a byte range lock on a region of an open file, and the request has a time limit associated with it.

    If this parameter is set and the lock range requested @@ -863,10 +863,10 @@ will fail the lock request immediately if the lock range cannot be obtained.

    Default: blocking locks = yes -

    +

    block size (S) -

    This parameter controls the behavior of smbd(8) when reporting disk free +

    This parameter controls the behavior of smbd(8) when reporting disk free sizes. By default, this reports a disk block size of 1024 bytes.

    Changing this parameter may have some effect on the efficiency of client writes, this is not yet confirmed. This @@ -880,42 +880,42 @@

    Example: block size = 4096 -

    +

    browsable -

    This parameter is a synonym for browseable.

    +

    This parameter is a synonym for browseable.

    browseable (S) -

    This controls whether this share is seen in +

    This controls whether this share is seen in the list of available shares in a net view and in the browse list.

    Default: browseable = yes -

    +

    browse list (G) -

    This controls whether smbd(8) will serve a browse list to +

    This controls whether smbd(8) will serve a browse list to a client doing a NetServerEnum call. Normally set to yes. You should never need to change this.

    Default: browse list = yes -

    +

    casesignames -

    This parameter is a synonym for case sensitive.

    +

    This parameter is a synonym for case sensitive.

    case sensitive (S) -

    See the discussion in the section name mangling.

    Default: case sensitive = no +

    See the discussion in the section name mangling.

    Default: case sensitive = no -

    +

    change notify (S) -

    This parameter specifies whether Samba should reply +

    This parameter specifies whether Samba should reply to a client's file change notify requests.

    You should never need to change this parameter

    Default: change notify = yes -

    +

    change share command (G) -

    +

    Samba 2.2.0 introduced the ability to dynamically add and delete shares via the Windows NT 4.0 Server Manager. The change share command is used to define an external program or script which will modify an existing service definition in smb.conf. @@ -930,15 +930,15 @@

    When executed, smbd will automatically invoke the change share command with five parameters. -

    • configFile - the location +

      • configFile - the location of the global smb.conf file. -

      • shareName - the name of the new +

      • shareName - the name of the new share. -

      • pathName - path to an **existing** +

      • pathName - path to an **existing** directory on disk. -

      • comment - comment string to associate +

      • comment - comment string to associate with the new share. -

      • max +

      • max connections Number of maximum simultaneous connections to this share. @@ -950,10 +950,10 @@

        Example: change share command = /usr/local/bin/changeshare -

    +

    check password script (G) -

    The name of a program that can be used to check password +

    The name of a program that can be used to check password complexity. The password is sent to the program's standard input.

    The program must return 0 on a good password, or any other value if the password is bad. In case the password is considered weak (the program does not return 0) the @@ -962,10 +962,10 @@

    Example: check password script = /usr/local/sbin/crackcheck -

    +

    client lanman auth (G) -

    This parameter determines whether or not smbclient(8) and other samba client +

    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 @@ -976,10 +976,10 @@ auth parameter is enabled, then only NTLMv2 logins will be attempted.

    Default: client lanman auth = no -

    +

    client ldap sasl wrapping (G) -

    +

    The client ldap sasl wrapping defines whether ldap traffic will be signed or signed and encrypted (sealed). Possible values are plain, sign @@ -1007,10 +1007,10 @@ seal.

    Default: client ldap sasl wrapping = plain -

    +

    client ntlmv2 auth (G) -

    This parameter determines whether or not smbclient(8) will attempt to +

    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 @@ -1022,16 +1022,16 @@ 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 +

    Specifies whether a client should send a plaintext password if the server does not support encrypted passwords.

    Default: client plaintext auth = no -

    +

    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, client schannel = auto offers the schannel but does not @@ -1041,10 +1041,10 @@

    Example: client schannel = yes -

    +

    client signing (G) -

    This controls whether the client is allowed or required to use SMB signing. Possible values +

    This controls whether the client is allowed or required to use SMB signing. Possible values are auto, mandatory and disabled.

    When set to auto, SMB signing is offered, but not enforced. @@ -1052,19 +1052,19 @@ to disabled, SMB signing is not offered either.

    Default: client signing = auto -

    +

    client use spnego (G) -

    This variable controls whether Samba clients will try +

    This variable controls whether Samba clients will try to use Simple and Protected NEGOciation (as specified by rfc2478) with supporting servers (including WindowsXP, Windows2000 and Samba 3.0) to agree upon an authentication mechanism. This enables Kerberos authentication in particular.

    Default: client use spnego = yes -

    +

    cluster addresses (G) -

    With this parameter you can add additional addresses +

    With this parameter you can add additional addresses nmbd will register with a WINS server. These addresses are not necessarily present on all nodes simultaneously, but they will be registered with the WINS server so that clients can contact @@ -1073,20 +1073,20 @@

    Example: cluster addresses = 10.0.0.1 10.0.0.2 10.0.0.3 -

    +

    clustering (G) -

    This parameter specifies whether Samba should contact +

    This parameter specifies whether Samba should contact ctdb for accessing its tdb files and use ctdb as a backend for its messaging backend.

    Set this parameter to yes only if you have a cluster setup with ctdb running.

    Default: clustering = no -

    +

    comment (S) -

    This is a text field that is seen next to a share +

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

    If you want to set the string that is displayed next to the @@ -1095,10 +1095,10 @@

    Example: comment = Fred's Files -

    +

    config backend (G) -

    +

    This controls the backend for storing the configuration. Possible values are file (the default) and registry. @@ -1116,10 +1116,10 @@

    Example: config backend = registry -

    +

    config file (G) -

    This allows you to override the config file +

    This allows you to override the config file to use, instead of the default (usually smb.conf). There is a chicken and egg problem here as this option is set in the config file!

    For this reason, if the name of the config file has changed @@ -1129,10 +1129,10 @@ (allowing you to special case the config files of just a few clients).

    No default

    Example: config file = /usr/local/samba/lib/smb.conf.%m -

    +

    copy (S) -

    This parameter allows you to "clone" service +

    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 @@ -1142,13 +1142,13 @@

    Example: copy = otherservice -

    +

    create mode -

    This parameter is a synonym for create mask.

    +

    This parameter is a synonym for create mask.

    create mask (S) -

    +

    When a file is created, the necessary permissions are calculated according to the mapping from DOS modes to UNIX permissions, and the resulting UNIX mode is then bit-wise 'AND'ed with this parameter. This parameter may be thought of as a bit-wise MASK for the UNIX modes of a file. Any bit not set here will @@ -1169,10 +1169,10 @@

    Example: create mask = 0775 -

    +

    csc policy (S) -

    +

    This stands for client-side caching policy, and specifies how clients capable of offline caching will cache the files in the share. The valid values are: manual, documents, programs, disable.

    @@ -1184,10 +1184,10 @@

    Example: csc policy = programs -

    +

    ctdbd socket (G) -

    If you set clustering=yes, +

    If you set clustering=yes, you need to tell Samba where ctdbd listens on its unix domain socket. The default path as of ctdb 1.0 is /tmp/ctdb.socket which you have to explicitly set for Samba in smb.conf. @@ -1195,10 +1195,10 @@

    Example: ctdbd socket = /tmp/ctdb.socket -

    +

    cups connection timeout (G) -

    +

    This parameter is only applicable if printing is set to cups.

    If set, this option specifies the number of seconds that smbd will wait @@ -1208,10 +1208,10 @@

    Example: cups connection timeout = 60 -

    +

    cups options (S) -

    +

    This parameter is only applicable if printing is set to cups. Its value is a free form string of options passed directly to the cups library. @@ -1233,10 +1233,10 @@

    Example: cups options = "raw media=a4" -

    +

    cups server (G) -

    +

    This parameter is only applicable if printing is set to cups.

    If set, this option overrides the ServerName option in the CUPS client.conf. This is @@ -1250,10 +1250,10 @@

    Example: cups server = mycupsserver:1631 -

    +

    deadtime (G) -

    The value of the parameter (a decimal integer) +

    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 @@ -1265,10 +1265,10 @@

    Example: deadtime = 15 -

    +

    debug class (G) -

    +

    With this boolean parameter enabled, the debug class (DBGC_CLASS) will be displayed in the debug header.

    @@ -1276,20 +1276,20 @@ section about log level.

    Default: debug class = no -

    +

    debug hires timestamp (G) -

    +

    Sometimes the timestamps in the log messages are needed with a resolution of higher that seconds, this 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 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 is adds the process-id to the timestamp message headers in the logfile when turned on. @@ -1297,10 +1297,10 @@ Note that the parameter debug timestamp must be on for this to have an effect.

    Default: debug pid = no -

    +

    debug prefix timestamp (G) -

    +

    With this option enabled, the timestamp message header is prefixed to the debug message without the filename and function information that is included with the debug timestamp parameter. This gives timestamps to the messages without adding an additional line. @@ -1308,38 +1308,38 @@ Note that this parameter overrides the debug timestamp parameter.

    Default: debug prefix timestamp = no -

    +

    timestamp logs -

    This parameter is a synonym for debug timestamp.

    +

    This parameter is a synonym for debug timestamp.

    debug timestamp (G) -

    +

    Samba debug log messages are timestamped by default. If you are running at a high debug level these timestamps can be distracting. This boolean parameter allows timestamping to be turned off.

    Default: debug timestamp = yes -

    +

    debug uid (G) -

    +

    Samba is sometimes run as root and sometime run as the connected user, this boolean parameter inserts the current euid, egid, uid and gid to the timestamp message headers in the log file if turned on.

    Note that the parameter debug timestamp must be on for this to have an effect.

    Default: debug uid = no -

    +

    default case (S) -

    See the section on name mangling. +

    See the section on name mangling. Also note the short preserve case parameter.

    Default: default case = lower -

    +

    default devmode (S) -

    This parameter is only applicable to printable services. +

    This parameter is only applicable to printable services. When smbd is serving Printer Drivers to Windows NT/2k/XP clients, each printer on the Samba server has a Device Mode which defines things such as paper size and orientation and duplex settings. The device mode can only correctly be @@ -1362,13 +1362,13 @@ see the MSDN documentation.

    Default: default devmode = yes -

    +

    default -

    This parameter is a synonym for default service.

    +

    This parameter is a synonym for default service.

    default service (G) -

    This parameter specifies the name of a service +

    This parameter specifies the name of a service which will be connected to if the service actually requested cannot be found. Note that the square brackets are NOT given in the parameter value (see example below).

    There is no default value for this parameter. If this @@ -1382,10 +1382,10 @@

    Example: default service = pub -

    +

    defer sharing violations (G) -

    +

    Windows allows specifying how a file will be shared with other processes when it is opened. Sharing violations occur when a file is opened by a different process using options that violate @@ -1398,19 +1398,19 @@ designed to enable Samba to more correctly emulate Windows.

    Default: defer sharing violations = True -

    +

    delete group script (G) -

    This is the full pathname to a script that will +

    This is the full pathname to a script that will be run AS ROOT smbd(8) when a group is requested to be deleted. It will expand any %g to the group name passed. This script is only useful for installations using the Windows NT domain administration tools.

    Default: delete group script = -

    +

    deleteprinter command (G) -

    With the introduction of MS-RPC based printer +

    With the introduction of MS-RPC based printer support for Windows NT/2000 clients in Samba 2.2, it is now possible to delete a printer at run time by issuing the DeletePrinter() RPC call.

    For a Samba host this means that the printer must be @@ -1428,18 +1428,18 @@

    Example: deleteprinter command = /usr/bin/removeprinter -

    +

    delete readonly (S) -

    This parameter allows readonly files to be deleted. +

    This parameter allows readonly files to be deleted. This is not normal DOS semantics, but is allowed by UNIX.

    This option may be useful for running applications such as rcs, where UNIX file ownership prevents changing file permissions, and DOS semantics prevent deletion of a read only file.

    Default: delete readonly = no -

    +

    delete share command (G) -

    +

    Samba 2.2.0 introduced the ability to dynamically add and delete shares via the Windows NT 4.0 Server Manager. The delete share command is used to define an external program or script which will remove an existing service definition from @@ -1454,9 +1454,9 @@

    When executed, smbd will automatically invoke the delete share command with two parameters. -

    • configFile - the location +

      • configFile - the location of the global smb.conf file. -

      • shareName - the name of +

      • shareName - the name of the existing service.

      This parameter is only used to remove file shares. To delete printer shares, @@ -1465,10 +1465,10 @@

      Example: delete share command = /usr/local/bin/delshare -

    +

    delete user from group script (G) -

    Full path to the script that will be called when +

    Full path to the script that will be called when a user is removed from a group using the Windows NT domain administration tools. It will be run by smbd(8) AS ROOT. Any %g will be replaced with the group name and @@ -1477,10 +1477,10 @@

    Example: delete user from group script = /usr/sbin/deluser %u %g -

    +

    delete user script (G) -

    This is the full pathname to a script that will +

    This is the full pathname to a script that will be run by smbd(8) when managing users with remote RPC (NT) tools.

    This script is called when a remote client removes a user @@ -1489,10 +1489,10 @@

    Example: delete user script = /usr/local/samba/bin/del_user %u -

    +

    delete veto files (S) -

    This option is used when Samba is attempting to +

    This option is used when Samba is attempting to delete a directory that contains one or more vetoed directories (see the veto files option). If this option is set to no (the default) then if a vetoed @@ -1506,10 +1506,10 @@ directories to be transparently deleted when the parent directory is deleted (so long as the user has permissions to do so).

    Default: delete veto files = no -

    +

    dfree cache time (S) -

    +

    The dfree cache time 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 @@ -1522,10 +1522,10 @@ By default this parameter is zero, meaning no caching will be done.

    No default

    Example: dfree cache time = dfree cache time = 60 -

    +

    dfree command (S) -

    +

    The dfree command setting 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" @@ -1563,13 +1563,13 @@ By default internal routines for determining the disk capacity and remaining space will be used.

    No default

    Example: dfree command = /usr/local/samba/bin/dfree -

    +

    directory mode -

    This parameter is a synonym for directory mask.

    +

    This parameter is a synonym for directory mask.

    directory mask (S) -

    This parameter is the octal modes which are +

    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 calculated according to the mapping from DOS modes to UNIX permissions, @@ -1587,10 +1587,10 @@

    Example: directory mask = 0775 -

    +

    directory security mask (S) -

    This parameter controls what UNIX permission bits +

    This parameter controls what UNIX permission bits will be set when a Windows NT client is manipulating the UNIX permission on a directory using the native NT security dialog box.

    @@ -1610,19 +1610,19 @@

    Example: directory security mask = 0700 -

    +

    disable netbios (G) -

    Enabling this parameter will disable netbios support +

    Enabling this parameter will disable netbios support in Samba. Netbios is the only available form of browsing in - all windows versions except for 2000 and XP.

    Note

    Clients that only support netbios won't be able to + all windows versions except for 2000 and XP.

    Note

    Clients that only support netbios won't be able to see your samba server when netbios support is disabled.

    Default: disable netbios = no -

    +

    disable spoolss (G) -

    Enabling this parameter will disable Samba's support +

    Enabling this parameter will disable Samba's support for the SPOOLSS set of MS-RPC's and will yield identical behavior as Samba 2.0.x. Windows NT/2000 clients will downgrade to using Lanman style printing commands. Windows 9x/ME will be unaffected by @@ -1634,10 +1634,10 @@ Be very careful about enabling this parameter.

    Default: disable spoolss = no -

    +

    display charset (G) -

    +

    Specifies the charset that samba will use to print messages to stdout and stderr. The default value is "LOCALE", which means automatically set, depending on the current locale. The value should generally be the same as the value of the parameter @@ -1646,10 +1646,10 @@

    Example: display charset = UTF8 -

    +

    dmapi support (S) -

    This parameter specifies whether Samba should use DMAPI to +

    This parameter specifies whether Samba should use DMAPI to determine whether a file is offline or not. This would typically be used in conjunction with a hierarchical storage system that automatically migrates files to tape. @@ -1664,10 +1664,10 @@

    Default: dmapi support = no -

    +

    dns proxy (G) -

    Specifies that nmbd(8) when acting as a WINS server and +

    Specifies that nmbd(8) when acting as a WINS server and finding that a NetBIOS name has not been registered, should treat the NetBIOS name word-for-word as a DNS name and do a lookup with the DNS server for that name on behalf of the name-querying client.

    Note that the maximum length for a NetBIOS name is 15 @@ -1676,10 +1676,10 @@ DNS name lookup requests, as doing a name lookup is a blocking action.

    Default: dns proxy = yes -

    +

    domain logons (G) -

    +

    If set to yes, the Samba server will provide the netlogon service for Windows 9X network logons for the workgroup it is in. @@ -1689,10 +1689,10 @@ Samba HOWTO Collection.

    Default: domain logons = no -

    +

    domain master (G) -

    +

    Tell smbd(8) to enable WAN-wide browse list collation. Setting this option causes nmbd to claim a special domain specific NetBIOS name that identifies it as a domain master browser for its given @@ -1718,10 +1718,10 @@ Samba will function as a BDC. In general, this parameter should be set to 'No' only on a BDC.

    Default: domain master = auto -

    +

    dont descend (S) -

    There are certain directories on some systems +

    There are certain directories on some systems (e.g., the /proc tree under Linux) that are either not of interest to clients or are infinitely deep (recursive). This parameter allows you to specify a comma-delimited list of directories @@ -1732,18 +1732,18 @@

    Example: dont descend = /proc,/dev -

    +

    dos charset (G) -

    DOS SMB clients assume the server has +

    DOS SMB clients assume the server has the same charset as they do. This option specifies which charset Samba should talk to DOS clients.

    The default depends on which charsets you have installed. Samba tries to use charset 850 but falls back to ASCII in - case it is not available. Run testparm(1) to check the default on your system.

    No default

    + case it is not available. Run testparm(1) to check the default on your system.

    No default

    dos filemode (S) -

    The default behavior in Samba is to provide +

    The default behavior in Samba is to provide UNIX-like behavior where only the owner of a file/directory is able to change the permissions on it. However, this behavior is often confusing to DOS/Windows users. Enabling this parameter @@ -1754,10 +1754,10 @@ the group is only granted read access. Ownership of the file/directory may also be changed.

    Default: dos filemode = no -

    +

    dos filetime resolution (S) -

    Under the DOS and Windows FAT filesystem, the finest +

    Under the DOS and Windows FAT filesystem, the finest granularity on time resolution is two seconds. Setting this parameter for a share causes Samba to round the reported time down to the nearest two second boundary when a query call that requires one second @@ -1772,10 +1772,10 @@ this option causes the two timestamps to match, and Visual C++ is happy.

    Default: dos filetime resolution = no -

    +

    dos filetimes (S) -

    Under DOS and Windows, if a user can write to a +

    Under DOS and Windows, if a user can write to a file they can change the timestamp on it. Under POSIX semantics, only the owner of the file or root may change the timestamp. By default, Samba runs with POSIX semantics and refuses to change the @@ -1789,20 +1789,20 @@ shared between users.

    Default: dos filetimes = yes -

    +

    ea support (S) -

    This boolean parameter controls whether smbd(8) will allow clients to attempt to store OS/2 style Extended +

    This boolean parameter controls whether smbd(8) will allow clients to attempt to store OS/2 style Extended attributes on a share. In order to enable this parameter the underlying filesystem exported by the share must support extended attributes (such as provided on XFS and EXT3 on Linux, with the correct kernel patches). On Linux the filesystem must have been mounted with the mount option user_xattr in order for extended attributes to work, also extended attributes must be compiled into the Linux kernel.

    Default: ea support = no -

    +

    enable asu support (G) -

    Hosts running the "Advanced Server for Unix (ASU)" product +

    Hosts running the "Advanced Server for Unix (ASU)" product require some special accomodations such as creating a builtin [ADMIN$] share that only supports IPC connections. The has been the default behavior in smbd for many years. However, certain Microsoft applications @@ -1810,20 +1810,20 @@ an [ADMIN$} file share. Disabling this parameter allows for creating an [ADMIN$] file share in smb.conf.

    Default: enable asu support = no -

    +

    enable core files (G) -

    This parameter specifies whether core dumps should be written +

    This parameter specifies whether core dumps should be written on internal exits. Normally set to yes. You should never need to change this.

    Default: enable core files = yes

    Example: enable core files = no -

    +

    enable privileges (G) -

    +

    This parameter controls whether or not smbd will honor privileges assigned to specific SIDs via either net rpc rights or one of the Windows user and group manager tools. This parameter is enabled by default. It can be disabled to prevent members of the Domain Admins group from being able to @@ -1836,10 +1836,10 @@ Please read the extended description provided in the Samba HOWTO documentation.

    Default: enable privileges = yes -

    +

    encrypt passwords (G) -

    This boolean controls whether encrypted passwords +

    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 @@ -1862,10 +1862,10 @@ causes smbd to authenticate against another server.

    Default: encrypt passwords = yes -

    +

    enhanced browsing (G) -

    This option enables a couple of enhancements to +

    This option enables a couple of enhancements to cross-subnet browse propagation that have been added in Samba but which are not standard in Microsoft implementations.

    The first enhancement to browse propagation consists of a regular @@ -1878,10 +1878,10 @@ 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 +

    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 @@ -1898,10 +1898,10 @@

    Example: enumports command = /usr/bin/listports -

    +

    eventlog list (G) -

    This option defines a list of log names that Samba will +

    This option defines a list of log names that Samba will report to the Microsoft EventViewer utility. The listed eventlogs will be associated with tdb file on disk in the $(lockdir)/eventlog. @@ -1914,10 +1914,10 @@

    Example: eventlog list = Security Application Syslog Apache -

    +

    fake directory create times (S) -

    NTFS and Windows VFAT file systems keep a create +

    NTFS and Windows VFAT file systems keep a create time for all files and directories. This is not the same as the ctime - status change time - that Unix keeps, so Samba by default reports the earliest of the various times Unix does keep. Setting @@ -1939,10 +1939,10 @@ ensures directories always predate their contents and an NMAKE build will proceed as expected.

    Default: fake directory create times = no -

    +

    fake oplocks (S) -

    Oplocks are the way that SMB clients get permission +

    Oplocks are the way that SMB clients get permission from a server to locally cache file operations. If a server grants an oplock (opportunistic lock) then the client is free to assume that it is the only one accessing the file and it will aggressively @@ -1958,10 +1958,10 @@ files read-write at the same time you can get data corruption. Use this option carefully!

    Default: fake oplocks = no -

    +

    follow symlinks (S) -

    +

    This parameter allows the Samba administrator to stop smbd(8) from following symbolic links in a particular share. Setting this parameter to no prevents any file or directory that is a symbolic link from being followed (the user will get an error). This option is very useful to stop users from adding a symbolic @@ -1971,10 +1971,10 @@ This option is enabled (i.e. smbd will follow symbolic links) by default.

    Default: follow symlinks = yes -

    +

    force create mode (S) -

    This parameter specifies a set of UNIX mode bit +

    This parameter specifies a set of UNIX mode bit permissions that will always be set on a file created by Samba. This is done by bitwise 'OR'ing these bits onto the mode bits of a file that is being created. The default for this parameter is (in octal) @@ -1986,10 +1986,10 @@

    Example: force create mode = 0755 -

    +

    force directory mode (S) -

    This parameter specifies a set of UNIX mode bit +

    This parameter specifies a set of UNIX mode bit permissions that will always be set on a directory created by Samba. This is done by bitwise 'OR'ing these bits onto the mode bits of a directory that is being created. The default for this @@ -2002,10 +2002,10 @@

    Example: force directory mode = 0755 -

    +

    force directory security mode (S) -

    +

    This parameter controls what UNIX permission bits can be modified when a Windows NT client is manipulating the UNIX permission on a directory using the native NT security dialog box.

    @@ -2018,7 +2018,7 @@

    If not set explicitly this parameter is 0000, which allows a user to modify all the user/group/world permissions on a directory without restrictions. -

    Note

    +

    Note

    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 probably want to leave it set as 0000. @@ -2026,13 +2026,13 @@

    Example: force directory security mode = 700 -

    +

    group -

    This parameter is a synonym for force group.

    +

    This parameter is a synonym for force group.

    force group (S) -

    This specifies a UNIX group name that will be +

    This specifies a UNIX group name that will be assigned as the default primary group for all users connecting to this service. This is useful for sharing files by ensuring that all access to files on service will use the named group for @@ -2056,10 +2056,10 @@

    Example: force group = agroup -

    +

    force printername (S) -

    When printing from Windows NT (or later), +

    When printing from Windows NT (or later), each printer in smb.conf has two associated names which can be used by the client. The first is the sharename (or shortname) defined in smb.conf. This @@ -2082,10 +2082,10 @@ not be able to delete printer connections from their local Printers folder.

    Default: force printername = no -

    +

    force security mode (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 dialog box.

    @@ -2105,10 +2105,10 @@

    Example: force security mode = 700 -

    +

    force unknown acl user (S) -

    +

    If this parameter is set, a Windows NT ACL that contains an unknown SID (security descriptor, or representation of a user or group id) as the owner or group owner of the file will be silently mapped into the current UNIX uid or gid of the currently connected user. @@ -2122,10 +2122,10 @@ Try using this parameter when XCOPY /O gives an ACCESS_DENIED error.

    Default: force unknown acl user = no -

    +

    force user (S) -

    This specifies a UNIX user name that will be +

    This 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. You should also use it carefully as using it incorrectly can cause security problems.

    This user name only gets used once a connection is established. @@ -2139,10 +2139,10 @@

    Example: force user = auser -

    +

    fstype (S) -

    +

    This parameter allows the administrator to configure the string that specifies the type of filesystem a share is using that is reported by smbd(8) when a client queries the filesystem type for a share. The default type is NTFS for compatibility @@ -2152,10 +2152,10 @@

    Example: fstype = Samba -

    +

    get quota command (G) -

    The get quota command should only be used +

    The get quota command should only be used whenever there is no operating system API available from the OS that samba can use.

    This option is only available you have compiled Samba with the --with-sys-quotas option or on Linux with @@ -2163,23 +2163,23 @@ was found in the system.

    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 one line as output with spaces between the arguments. The arguments are: -

    • Arg 1 - quota flags (0 = no quotas, 1 = quotas enabled, 2 = quotas enabled and enforced)

    • Arg 2 - number of currently used blocks

    • Arg 3 - the softlimit number of blocks

    • Arg 4 - the hardlimit number of blocks

    • Arg 5 - currently used number of inodes

    • Arg 6 - the softlimit number of inodes

    • Arg 7 - the hardlimit number of inodes

    • Arg 8(optional) - the number of bytes in a block(default is 1024)

    Default: get quota command = + 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 one line as output with spaces between the arguments. The arguments are: +

    • Arg 1 - quota flags (0 = no quotas, 1 = quotas enabled, 2 = quotas enabled and enforced)

    • Arg 2 - number of currently used blocks

    • Arg 3 - the softlimit number of blocks

    • Arg 4 - the hardlimit number of blocks

    • Arg 5 - currently used number of inodes

    • Arg 6 - the softlimit number of inodes

    • Arg 7 - the hardlimit number of inodes

    • Arg 8(optional) - the number of bytes in a block(default is 1024)

    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 +

    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 smbconfoptions parameter is set to no.

    Default: getwd cache = yes -

    +

    guest account (G) -

    This is a username which will be used for access +

    This is a username which will be used for access to services which are specified as guest ok (see below). Whatever privileges this user has will be available to any client connecting to the guest service. This user must exist in the password file, but does not require @@ -2197,40 +2197,40 @@

    Example: guest account = ftp -

    +

    public -

    This parameter is a synonym for guest ok.

    +

    This parameter is a synonym for guest ok.

    guest ok (S) -

    If this parameter is yes for +

    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 restrict anonymous = 2

    See the section below on security for more information about this option.

    Default: guest ok = no -

    +

    only guest -

    This parameter is a synonym for guest only.

    +

    This parameter is a synonym for guest only.

    guest only (S) -

    If this parameter is yes for +

    If this parameter is yes for a service, then only guest connections to the service are permitted. This parameter will have no effect if guest ok is not set for the service.

    See the section below on security for more information about this option.

    Default: guest only = no -

    +

    hide dot files (S) -

    This is a boolean parameter that controls whether +

    This is a boolean parameter that controls whether files starting with a dot appear as hidden files.

    Default: hide dot files = yes -

    +

    hide files (S) -

    This is a list of files or directories that are not +

    This is a list of files or directories that are not visible but are accessible. The DOS 'hidden' attribute is applied to any files or directories that match.

    Each entry in the list must be separated by a '/', which allows spaces to be included in the entry. '*' @@ -2252,32 +2252,32 @@

    Default: hide files = # no file are hidden -

    +

    hide special files (S) -

    +

    This parameter prevents clients from seeing special files such as sockets, devices and fifo's in directory listings.

    Default: hide special files = no -

    +

    hide unreadable (S) -

    This parameter prevents clients from seeing the +

    This parameter prevents clients from seeing the existance of files that cannot be read. Defaults to off.

    Default: hide unreadable = no -

    +

    hide unwriteable files (S) -

    +

    This parameter prevents clients from seeing the existance of files that cannot be written to. Defaults to off. Note that unwriteable directories are shown as usual.

    Default: hide unwriteable files = no -

    +

    homedir map (G) -

    +

    If nis homedir is yes, and smbd(8) is also acting as a Win95/98 logon server then this parameter specifies the NIS (or YP) map from which the server for the user's home directory should be extracted. At present, only the Sun auto.home map format is understood. The form of the map is: @@ -2286,16 +2286,16 @@

    and the program will extract the servername from before the first ':'. There should probably be a better parsing system that copes with different map formats and also Amd (another automounter) maps. -

    Note

    +

    Note

    A working NIS client is required on the system for this option to work.

    Default: homedir map =

    Example: homedir map = amd.homedir -

    +

    host msdfs (G) -

    +

    If set to yes, Samba will act as a Dfs server, and allow Dfs-aware clients to browse Dfs trees hosted on the server.

    @@ -2303,10 +2303,10 @@ setting up a Dfs tree on Samba, refer to the MSFDS chapter in the book Samba3-HOWTO.

    Default: host msdfs = yes -

    +

    hostname lookups (G) -

    Specifies whether samba should use (expensive) +

    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 the hosts deny and hosts allow. @@ -2314,13 +2314,13 @@

    Example: hostname lookups = yes -

    +

    allow hosts -

    This parameter is a synonym for hosts allow.

    +

    This parameter is a synonym for hosts allow.

    hosts allow (S) -

    A synonym for this parameter is allow hosts.

    This parameter is a comma, space, or tab delimited +

    A synonym for this parameter is allow hosts.

    This parameter is a comma, space, or tab delimited set of hosts which are permitted to access a service.

    If specified in the [global] section then it will apply to all services, regardless of whether the individual service has a different setting.

    You can specify the hosts by name or IP number. For @@ -2334,19 +2334,19 @@ 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 - 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 + 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: hosts allow = # none (i.e., all hosts permitted access)

    Example: hosts allow = 150.203.5. myhost.mynet.edu.au -

    +

    deny hosts -

    This parameter is a synonym for hosts deny.

    +

    This parameter is a synonym for hosts deny.

    hosts deny (S) -

    The opposite of hosts allow +

    The opposite of hosts allow - hosts listed here are NOT permitted access to services unless the specific services have their own lists to override this one. Where the lists conflict, the allow @@ -2360,10 +2360,10 @@

    Example: hosts deny = 150.203.4. badhost.mynet.edu.au -

    +

    idmap alloc backend (G) -

    +

    The idmap alloc backend provides a plugin interface for Winbind to use when allocating Unix uids/gids for Windows SIDs. This option refers to the name of the idmap module which will provide the id allocation @@ -2380,18 +2380,18 @@ Also refer to the idmap alloc config option.

    No default

    Example: idmap alloc backend = tdb -

    +

    idmap alloc config (G) -

    +

    The idmap alloc config prefix provides a means of managing settings for the backend defined by the idmap alloc backend parameter. Refer to the man page for each idmap plugin regarding specific configuration details. -

    No default

    +

    No default

    idmap backend (G) -

    +

    The idmap backend provides a plugin interface for Winbind to use varying backends to store SID/uid/gid mapping tables.

    @@ -2412,17 +2412,17 @@ and ad (idmap_ad(8)).

    Default: idmap backend = tdb -

    +

    idmap cache time (G) -

    This parameter specifies the number of seconds that Winbind's +

    This parameter specifies the number of seconds that Winbind's idmap interface will cache positive SID/uid/gid query results.

    Default: idmap cache time = 604800 (one week) -

    +

    idmap config (G) -

    +

    The idmap config prefix provides a means of managing each trusted domain separately. The idmap config prefix should be followed by the name of the domain, a colon, and a setting specific to the chosen @@ -2454,13 +2454,13 @@ idmap config CORP : backend = ad idmap config CORP : range = 1000-999999 -

    No default

    +

    No default

    winbind gid -

    This parameter is a synonym for idmap gid.

    +

    This parameter is a synonym for idmap gid.

    idmap gid (G) -

    The idmap gid parameter specifies the range of group ids +

    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 @@ -2470,20 +2470,20 @@

    Example: idmap gid = 10000-20000 -

    +

    idmap negative cache time (G) -

    This parameter specifies the number of seconds that Winbind's +

    This parameter specifies the number of seconds that Winbind's idmap interface will cache negative SID/uid/gid query results.

    Default: idmap negative cache time = 120 -

    +

    winbind uid -

    This parameter is a synonym for idmap uid.

    +

    This parameter is a synonym for idmap uid.

    idmap uid (G) -

    +

    The idmap uid parameter specifies the range of user ids that are allocated for use in mapping UNIX users to NT user SIDs. This range of ids should have no existing local @@ -2493,10 +2493,10 @@

    Example: idmap uid = 10000-20000 -

    +

    include (G) -

    +

    This allows you to include one config file inside another. The file is included literally, as though typed in place.

    @@ -2514,10 +2514,10 @@

    Example: include = /usr/local/samba/lib/admin_smb.conf -

    +

    inherit acls (S) -

    This parameter can be used to ensure that if default acls +

    This parameter can be used to ensure that if default acls exist on parent directories, they are always honored when creating a new file or subdirectory in these parent directories. The default behavior is to use the unix mode specified when creating the directory. @@ -2525,10 +2525,10 @@ default directory acls are propagated.

    Default: inherit acls = no -

    +

    inherit owner (S) -

    The ownership of new files and directories +

    The ownership of new files and directories is normally governed by effective uid of the connected user. This option allows the Samba administrator to specify that the ownership for new files and directories should be controlled @@ -2537,10 +2537,10 @@ delete them and to ensure that newly create files in a user's roaming profile directory are actually owner by the user.

    Default: inherit owner = no -

    +

    inherit permissions (S) -

    +

    The permissions on new files and directories are normally governed by create mask, directory mask, force create mode and force directory mode but the boolean inherit permissions parameter overrides this.

    New directories inherit the mode of the parent directory, @@ -2552,10 +2552,10 @@ many users, perhaps several thousand, to allow a single [homes] share to be used flexibly by each user.

    Default: inherit permissions = no -

    +

    init logon delayed hosts (G) -

    +

    This parameter takes a list of host names, addresses or networks for which the initial samlogon reply should be delayed (so other DCs get preferred by XP workstations if there are any). @@ -2566,28 +2566,28 @@

    Example: init logon delayed hosts = 150.203.5. myhost.mynet.de -

    +

    init logon delay (G) -

    +

    This parameter specifies a delay in milliseconds for the hosts configured for delayed initial samlogon with init logon delayed hosts.

    Default: init logon delay = 100 -

    +

    interfaces (G) -

    This option allows you to override the default +

    This option allows you to override the default network interfaces list that Samba will use for browsing, name registration and other NetBIOS over TCP/IP (NBT) traffic. By default Samba will query the kernel for the list of all active interfaces and use any 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). + 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 IP address or a hostname which will be looked up via @@ -2602,10 +2602,10 @@

    Example: interfaces = eth0 192.168.2.10/24 192.168.3.10/255.255.255.0 -

    +

    invalid users (S) -

    This is a list of users that should not be allowed +

    This is a list of users that should not be allowed to login to this service. This is really a paranoid check to absolutely ensure an improper setting does not breach your security.

    A name starting with a '@' is interpreted as an NIS @@ -2625,10 +2625,10 @@

    Example: invalid users = root fred admin @wheel -

    +

    iprint server (G) -

    +

    This parameter is only applicable if printing is set to iprint.

    If set, this option overrides the ServerName option in the CUPS client.conf. This is @@ -2637,10 +2637,10 @@

    Example: iprint server = MYCUPSSERVER -

    +

    keepalive (G) -

    The value of the parameter (an integer) represents +

    The value of the parameter (an integer) represents the number of seconds between keepalive packets. If this parameter is zero, no keepalive packets will be sent. Keepalive packets, if sent, allow the server to tell whether @@ -2650,20 +2650,20 @@

    Example: keepalive = 600 -

    +

    kernel change notify (S) -

    This parameter specifies whether Samba should ask the +

    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 used when your kernel supports change notification to user programs using the inotify interface.

    Default: kernel change notify = yes -

    +

    kernel oplocks (G) -

    For UNIXes that support kernel based oplocks +

    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 to be broken whenever a local UNIX process or NFS operation @@ -2673,10 +2673,10 @@ to a no-op on systems that no not have the necessary kernel support. You should never need to touch this parameter.

    Default: kernel oplocks = yes -

    +

    lanman auth (G) -

    This parameter determines whether or not smbd(8) will attempt to +

    This parameter determines whether or not smbd(8) will attempt to authenticate users or permit password changes using the LANMAN password hash. If disabled, only clients which support NT password hashes (e.g. Windows NT/2000 clients, smbclient, but not @@ -2693,22 +2693,22 @@ permited. Not all clients support NTLMv2, and most will require special configuration to use it.

    Default: lanman auth = no -

    +

    large readwrite (G) -

    This parameter determines whether or not +

    This parameter determines whether or not smbd(8) supports the new 64k - streaming read and write varient SMB requests introduced with + streaming read and write variant SMB requests introduced with Windows 2000. Note that due to Windows 2000 client redirector bugs this requires Samba to be running on a 64-bit capable operating system such as IRIX, Solaris or a Linux 2.4 kernel. Can improve performance by 10% with Windows 2000 clients. Defaults to on. Not as tested as some other Samba code paths.

    Default: large readwrite = yes -

    +

    ldap admin dn (G) -

    +

    The ldap admin dn defines the Distinguished Name (DN) name used by Samba to contact the ldap server when retreiving user account information. The ldap admin dn is used in conjunction with the admin dn password stored in the private/secrets.tdb @@ -2716,10 +2716,10 @@ man page for more information on how to accomplish this.

    The ldap admin dn requires a fully specified DN. The ldap suffix is not appended to the ldap admin dn. -

    No default

    +

    No default

    ldap connection timeout (G) -

    +

    This parameter tells the LDAP library calls which timeout in seconds they should honor during initial connection establishments to LDAP servers. It is very useful in failover scenarios in particular. If one or more LDAP @@ -2731,10 +2731,10 @@ and not establishing an initial connection.

    Default: ldap connection timeout = 2 -

    +

    ldap debug level (G) -

    +

    This parameter controls the debug level of the LDAP library calls. In the case of OpenLDAP, it is the same bit-field as understood by the server and documented in the @@ -2751,10 +2751,10 @@

    Example: ldap debug level = 1 -

    +

    ldap debug threshold (G) -

    +

    This parameter controls the Samba debug level at which the ldap library debug output is printed in the Samba logs. See the description of @@ -2763,28 +2763,28 @@

    Example: ldap debug threshold = 5 -

    +

    ldap delete dn (G) -

    This parameter specifies whether a delete +

    This parameter specifies whether a delete operation in the ldapsam deletes the complete entry or only the attributes specific to Samba.

    Default: ldap delete dn = no -

    +

    ldap group suffix (G) -

    This parameter specifies the suffix that is +

    This parameter 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. The suffix string is pre-pended to the ldap suffix string so use a partial DN.

    Default: ldap group suffix =

    Example: ldap group suffix = 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. The suffix string is pre-pended to the ldap suffix string so use a partial DN. @@ -2792,10 +2792,10 @@

    Example: ldap idmap suffix = ou=Idmap -

    +

    ldap machine suffix (G) -

    +

    It specifies where machines should be added to the ldap tree. If this parameter is unset, the value of ldap suffix will be used instead. The suffix string is pre-pended to the ldap suffix string so use a partial DN. @@ -2803,10 +2803,10 @@

    Example: ldap machine suffix = ou=Computers -

    +

    ldap page size (G) -

    +

    This parameter specifies the number of entries per page.

    If the LDAP server supports paged results, clients can request subsets of search results (pages) instead of the entire list. @@ -2815,24 +2815,24 @@

    Example: ldap page size = 512 -

    +

    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 change via SAMBA.

    The ldap passwd sync can be set to one of three values: -

    • Yes = Try - to update the LDAP, NT and LM passwords and update the pwdLastSet time.

    • No = Update NT and - LM passwords and update the pwdLastSet time.

    • Only = Only update +

      • Yes = Try + to update the LDAP, NT and LM passwords and update the pwdLastSet time.

      • No = Update NT and + LM passwords and update the pwdLastSet time.

      • Only = Only update the LDAP password and let the LDAP server do the rest.

      Default: ldap passwd sync = no -

    +

    ldap replication sleep (G) -

    +

    When Samba is asked to write to a read-only LDAP replica, we are redirected to talk to the read-write master server. This server then replicates our changes back to the 'local' server, however the replication might take some seconds, especially over slow links. Certain client activities, particularly domain joins, can become confused by the 'success' @@ -2845,10 +2845,10 @@ The value is specified in milliseconds, the maximum value is 5000 (5 seconds).

    Default: ldap replication sleep = 1000 -

    +

    ldapsam:editposix (G) -

    +

    Editposix is an option that leverages ldapsam:trusted to make it simpler to manage a domain controller eliminating the need to set up custom scripts to add and manage the posix users and groups. This option will instead directly manipulate the ldap tree to create, remove and modify user and group entries. @@ -2926,10 +2926,10 @@

    Default: ldapsam:editposix = no -

    +

    ldapsam:trusted (G) -

    +

    By default, Samba as a Domain Controller with an LDAP backend needs to use the Unix-style NSS subsystem to access user and group information. Due to the way Unix stores user information in /etc/passwd and /etc/group this inevitably leads to inefficiencies. One important question a user needs to know is the list of groups he @@ -2947,10 +2947,10 @@ is easily achieved.

    Default: ldapsam:trusted = no -

    +

    ldap ssl ads (G) -

    This option is used to define whether or not Samba should +

    This option is used to define whether or not Samba should use SSL when connecting to the ldap server using ads methods. Rpc methods are not affected by this parameter. Please note, that @@ -2960,10 +2960,10 @@ for more information on ldap ssl.

    Default: ldap ssl ads = no -

    +

    ldap ssl (G) -

    This option is used to define whether or not Samba should +

    This option is used to define whether or not Samba should use SSL when connecting to the ldap server This is NOT related to Samba's previous SSL support which was enabled by specifying the @@ -2974,8 +2974,8 @@ Start_tls or by specifying ldaps:// in the URL argument of passdb backend.

    The ldap ssl can be set to one of - two values:

    • Off = Never - use SSL when querying the directory.

    • start tls = Use + two values:

      • Off = Never + use SSL when querying the directory.

      • start tls = Use the LDAPv3 StartTLS extended operation (RFC2830) for communicating with the directory server.

      Please note that this parameter does only affect rpc @@ -2988,10 +2988,10 @@ for more information on ldap ssl ads.

      Default: ldap ssl = start tls -

    +

    ldap suffix (G) -

    Specifies the base for all ldap suffixes and for storing the sambaDomain object.

    +

    Specifies the base for all ldap suffixes and for storing the sambaDomain object.

    The ldap suffix will be appended to the values specified for the ldap user suffix, ldap group suffix, ldap machine suffix, and the ldap idmap suffix. Each of these should be given only a DN relative to the @@ -3000,17 +3000,17 @@

    Example: ldap suffix = dc=samba,dc=org -

    +

    ldap timeout (G) -

    +

    This parameter defines the number of seconds that Samba should use as timeout for LDAP operations.

    Default: ldap timeout = 15 -

    +

    ldap user suffix (G) -

    +

    This parameter specifies where users are added to the tree. If this parameter is unset, the value of ldap suffix will be used instead. The suffix string is pre-pended to the ldap suffix string so use a partial DN. @@ -3018,10 +3018,10 @@

    Example: ldap user suffix = ou=people -

    +

    level2 oplocks (S) -

    This parameter controls whether Samba supports +

    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 @@ -3041,10 +3041,10 @@ parameter must be set to yes on this share in order for this parameter to have any effect.

    Default: level2 oplocks = yes -

    +

    lm announce (G) -

    This parameter determines if nmbd(8) will produce Lanman announce +

    This parameter determines if nmbd(8) will produce Lanman announce broadcasts that are needed by OS/2 clients in order for them to see the Samba server in their browse list. This parameter can have three values, yes, no, or @@ -3060,10 +3060,10 @@

    Example: lm announce = yes -

    +

    lm interval (G) -

    If Samba is set to produce Lanman announce +

    If Samba is set to produce Lanman announce broadcasts needed by OS/2 clients (see the lm announce parameter) then this parameter defines the frequency in seconds with which they will be @@ -3073,18 +3073,18 @@

    Example: lm interval = 120 -

    +

    load printers (G) -

    A boolean variable that controls whether all +

    A boolean variable that controls whether all printers in the printcap will be loaded for browsing by default. See the printers section for more details.

    Default: load printers = yes -

    +

    local master (G) -

    This option allows nmbd(8) to try and become a local master browser +

    This option allows nmbd(8) to try and become a local master browser on a subnet. If set to no then nmbd will not attempt to become a local master browser on a subnet and will also lose in all browsing elections. By @@ -3094,13 +3094,13 @@ will participate in elections for local master browser.

    Setting this value to no will cause nmbd never to become a local master browser.

    Default: local master = yes -

    +

    lock dir -

    This parameter is a synonym for lock directory.

    +

    This parameter is a synonym for lock directory.

    lock directory (G) -

    This option specifies the directory where lock +

    This option specifies the directory where lock files will be placed. The lock files are used to implement the max connections option.

    @@ -3110,10 +3110,10 @@

    Example: lock directory = /var/run/samba/locks -

    +

    locking (S) -

    This controls whether or not locking will be +

    This controls whether or not locking will be performed by the server in response to lock requests from the client.

    If locking = no, all lock and unlock requests will appear to succeed and all lock queries will report @@ -3123,18 +3123,18 @@ CDROM drives), although setting this parameter of no is not really recommended even in this case.

    Be careful about disabling locking either globally or in a specific service, as lack of locking may result in data corruption. - You should never need to set this parameter.

    No default

    + You should never need to set this parameter.

    No default

    lock spin count (G) -

    This parameter has been made inoperative in Samba 3.0.24. +

    This parameter has been made inoperative in Samba 3.0.24. The functionality it contolled is now controlled by the parameter lock spin time.

    Default: lock spin count = 0 -

    +

    lock spin time (G) -

    The time in microseconds that smbd should +

    The time in microseconds that smbd should keep waiting to see if a failed lock request can be granted. This parameter has changed in default value from Samba 3.0.23 from 10 to 200. The associated @@ -3142,36 +3142,36 @@ no longer used in Samba 3.0.24. You should not need to change the value of this parameter.

    Default: lock spin time = 200 -

    +

    log file (G) -

    +

    This option allows you to override the name of the Samba log file (also known as the debug file).

    This option takes the standard substitutions, allowing you to have separate log files for each user or machine.

    No default

    Example: log file = /usr/local/samba/var/log.%m -

    +

    debuglevel -

    This parameter is a synonym for log level.

    +

    This parameter is a synonym for log level.

    log level (G) -

    +

    The value of the parameter (a astring) allows the debug level (logging level) to be specified in the smb.conf file.

    This parameter has been extended since the 2.2.x series, now it allows to specify the debug level for multiple debug classes. This is to give greater flexibility in the configuration of the system. The following debug classes are currently implemented: -

    • all

    • tdb

    • printdrivers

    • lanman

    • smb

    • rpc_parse

    • rpc_srv

    • rpc_cli

    • passdb

    • sam

    • auth

    • winbind

    • vfs

    • idmap

    • quota

    • acls

    • locking

    • msdfs

    • dmapi

    • registry

    Default: log level = 0 +

    • all

    • tdb

    • printdrivers

    • lanman

    • smb

    • rpc_parse

    • rpc_srv

    • rpc_cli

    • passdb

    • sam

    • auth

    • winbind

    • vfs

    • idmap

    • quota

    • acls

    • locking

    • msdfs

    • dmapi

    • registry

    Default: log level = 0

    Example: log level = 3 passdb:5 auth:10 winbind:2 -

    +

    logon drive (G) -

    +

    This parameter specifies the local path to which the home directory will be connected (see logon home) and is only used by NT Workstations. @@ -3181,10 +3181,10 @@

    Example: logon drive = h: -

    +

    logon home (G) -

    +

    This parameter specifies the home directory location when a Win95/98 or NT Workstation logs into a Samba PDC. It allows you to do

    @@ -3215,10 +3215,10 @@

    Example: logon home = \\remote_smb_server\%U -

    +

    logon path (G) -

    +

    This parameter specifies the directory where roaming profiles (Desktop, NTuser.dat, etc) 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 @@ -3240,8 +3240,8 @@ this parameter to \\%N\homes\profile_path will cause problems).

    This option takes the standard substitutions, allowing you to have separate logon scripts for each user or machine. -

    Warning

    - Do not quote the value. Setting this as \\%N\profile\%U +

    Warning

    + Do not quote the value. Setting this as “\\%N\profile\%U” will break profile handling. Where the tdbsam or ldapsam passdb backend is used, at the time the user account is created the value configured for this parameter is written to the passdb backend and that value will @@ -3262,10 +3262,10 @@

    Default: logon path = \\%N\%U\profile -

    +

    logon script (G) -

    +

    This parameter specifies the batch file (.bat) or NT command file (.cmd) to be downloaded and run on a machine when a user successfully logs in. The file must contain the DOS style CR/LF line endings. Using a DOS-style editor to create the file is recommended. @@ -3296,10 +3296,10 @@

    Example: logon script = scripts\%U.bat -

    +

    lppause command (S) -

    This parameter specifies the command to be +

    This parameter specifies the command to be executed on the server host in order to stop printing or spooling a specific print job.

    This command should be a program or script which takes a printer name and job number to pause the print job. One way @@ -3323,10 +3323,10 @@

    Example: lppause command = /usr/bin/lpalt %p-%j -p0 -

    +

    lpq cache time (G) -

    This controls how long lpq info will be cached +

    This controls how long lpq info will be cached for to prevent the lpq command being called too often. A separate cache is kept for each variation of the lpq command used by the system, so if you use different @@ -3339,10 +3339,10 @@

    Example: lpq cache time = 10 -

    +

    lpq command (S) -

    This parameter specifies the command to be +

    This parameter specifies the command to be executed on the server host in order to obtain lpq -style printer status information.

    This command should be a program or script which takes a printer name as its only parameter and outputs printer @@ -3364,10 +3364,10 @@

    Example: lpq command = /usr/bin/lpq -P%p -

    +

    lpresume command (S) -

    This parameter specifies the command to be +

    This parameter specifies the command to be executed on the server host in order to restart or continue printing or spooling a specific print job.

    This command should be a program or script which takes a printer name and job number to resume the print job. See @@ -3380,10 +3380,10 @@ parameter is SYSV, in which case the default is:

    lp -i %p-%j -H resume

    or if the value of the printing parameter is SOFTQ, then the default is:

    qstat -s -j%j -r

    No default

    Example: lpresume command = /usr/bin/lpalt %p-%j -p2 -

    +

    lprm command (S) -

    This parameter specifies the command to be +

    This parameter specifies the command to be executed on the server host in order to delete a print job.

    This command should be a program or script which takes a printer name and job number, and deletes the print job.

    If a %p is given then the printer name is put in its place. A %j is replaced with @@ -3400,10 +3400,10 @@

    Default: lprm command = determined by printing parameter -

    +

    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 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 @@ -3413,22 +3413,22 @@ and the security = domain parameter.

    Default: machine password timeout = 604800 -

    +

    magic output (S) -

    +

    This parameter specifies the name of a file which will contain output created by a magic script (see the magic script parameter below). -

    Warning

    If two clients use the same magic script +

    Warning

    If two clients use the same magic script in the same directory the output file content is undefined.

    Default: magic output = <magic script name>.out

    Example: magic output = myfile.txt -

    +

    magic script (S) -

    This parameter specifies the name of a file which, +

    This parameter specifies the name of a file which, if opened, will be executed by the server when the file is closed. This allows a UNIX script to be sent to the Samba host and executed on behalf of the connected user.

    Scripts executed in this way will be deleted upon @@ -3444,23 +3444,23 @@

    Example: magic script = user.csh -

    +

    mangled names (S) -

    This controls whether non-DOS names under UNIX +

    This controls whether non-DOS names under UNIX 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 + 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 only if it contains any upper case characters or is longer than three characters.

        Note that the character to use may be specified using the mangling char - option, if you don't like '~'.

      • Files whose UNIX name begins with a dot will be + option, if you don't like '~'.

      • 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 its extension regardless of actual original extension (that's three @@ -3472,10 +3472,10 @@ from Windows/DOS and will retain the same basename. Mangled names do not change between sessions.

        Default: mangled names = yes -

    +

    mangle prefix (G) -

    controls the number of prefix +

    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 @@ -3485,20 +3485,20 @@

    Example: mangle prefix = 4 -

    +

    mangling char (S) -

    This controls what character is used as +

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

    controls the algorithm used for the generating the mangled names. Can take two different values, "hash" and "hash2". "hash" is the algorithm that was used used in Samba for many years and was the default in Samba 2.2.x "hash2" is @@ -3509,10 +3509,10 @@

    Example: mangling method = hash -

    +

    map acl inherit (S) -

    This boolean parameter controls whether smbd(8) will attempt to map the 'inherit' and 'protected' +

    This boolean parameter controls whether smbd(8) will attempt to map the 'inherit' and 'protected' access control entry flags stored in Windows ACLs into an extended attribute called user.SAMBA_PAI. This parameter only takes effect if Samba is being run on a platform that supports extended attributes (Linux and IRIX so far) and @@ -3520,10 +3520,10 @@ POSIX ACL mapping code.

    Default: map acl inherit = no -

    +

    map archive (S) -

    +

    This controls whether the DOS archive attribute should be mapped to the UNIX owner execute bit. The DOS archive bit is set when a file has been modified since its last backup. One @@ -3536,26 +3536,26 @@ create mask for details.

    Default: map archive = yes -

    +

    map hidden (S) -

    +

    This controls whether DOS style hidden files should be mapped to the UNIX world execute bit.

    Note that this requires the create mask to be set such that the world execute bit is not masked out (i.e. it must include 001). See the parameter create mask for details. -

    No default

    +

    No default

    map read only (S) -

    +

    This controls how the DOS read only attribute should be mapped from a UNIX filesystem.

    This parameter can take three different values, which tell smbd(8) how to display the read only attribute on files, where either store dos attributes is set to No, or no extended attribute is present. If store dos attributes is set to yes then this parameter is ignored. This is a new parameter introduced in Samba version 3.0.21. -

    The three settings are :

    • +

      The three settings are :

      • Yes - The read only DOS attribute is mapped to the inverse of the user or owner write bit in the unix permission mode set. If the owner write bit is not set, the read only attribute is reported as being set on the file. @@ -3563,20 +3563,20 @@ others write bits to zero. Write bits set in an ACL are ignored by Samba. If the read only DOS attribute is unset, Samba simply sets the write bit of the owner to one. -

      • +

      • Permissions - The read only DOS attribute is mapped to the effective permissions of the connecting user, as evaluated by smbd(8) by reading the unix permissions and POSIX ACL (if present). If the connecting user does not have permission to modify the file, the read only attribute is reported as being set on the file. -

      • +

      • No - The read only DOS attribute is unaffected by permissions, and can only be set by the store dos attributes method. This may be useful for exporting mounted CDs.

      Default: map read only = yes -

    +

    map system (S) -

    +

    This controls whether DOS style system files should be mapped to the UNIX group execute bit.

    Note that this requires the create mask to be set such that the group @@ -3584,20 +3584,20 @@ create mask for details.

    Default: map system = no -

    +

    map to guest (G) -

    This parameter is only useful in SECURITY = +

    This parameter is only useful in SECURITY = security modes other than security = share and security = server - i.e. user, and domain.

    This parameter can take four different values, which tell smbd(8) what to do with user - login requests that don't match a valid UNIX user in some way.

    The four settings are :

    • Never - Means user login + login requests that don't match a valid UNIX user in some way.

      The four settings are :

      • Never - Means user login requests with an invalid password are rejected. This is the - default.

      • Bad User - Means user + default.

      • Bad User - Means user logins with an invalid password are rejected, unless the username does not exist, in which case it is treated as a guest login and - mapped into the guest account.

      • Bad Password - Means user logins + mapped into the guest account.

      • Bad Password - Means user logins 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 @@ -3606,7 +3606,7 @@ 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 :-).

      • Bad Uid - Is only applicable when Samba is configured + guest parameter this way :-).

      • Bad Uid - Is only applicable when Samba is configured in some type of domain mode security (security = {domain|ads}) and means that user logins which are successfully authenticated but which have no valid Unix user account (and smbd is unable to create one) should be mapped to the defined @@ -3629,10 +3629,10 @@

        Example: map to guest = Bad User -

    +

    max connections (S) -

    This option allows the number of simultaneous connections to a service to be limited. +

    This option allows the number of simultaneous connections to a service to be limited. If max connections is greater than 0 then connections will be refused if this number of connections to the service are already open. A value of zero mean an unlimited number of connections may be made.

    Record lock files are used to implement this feature. The lock files will be stored in @@ -3640,10 +3640,10 @@

    Example: max connections = 10 -

    +

    max disk size (G) -

    This option allows you to put an upper limit +

    This option allows you to put an upper limit on the apparent size of disks. If you set this option to 100 then all shares will appear to be not larger than 100 MB in size.

    Note that this option does not limit the amount of @@ -3657,10 +3657,10 @@

    Example: max disk size = 1000 -

    +

    max log size (G) -

    +

    This option (an integer in kilobytes) specifies the max size the log file should grow to. Samba periodically checks the size and if it is exceeded it will rename the file, adding a .old extension. @@ -3669,17 +3669,17 @@

    Example: max log size = 1000 -

    +

    max mux (G) -

    This option controls the maximum number of +

    This option controls the maximum number of outstanding simultaneous SMB operations that Samba tells the client it will allow. You should never need to set this parameter.

    Default: max mux = 50 -

    +

    max open files (G) -

    This parameter limits the maximum number of +

    This parameter limits the maximum number of open files that one smbd(8) file serving process may have open for a client at any one time. The default for this parameter is set very high (10,000) as Samba uses @@ -3687,38 +3687,38 @@ 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 +

    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.

    Default: max print jobs = 1000

    Example: max print jobs = 5000 -

    +

    protocol -

    This parameter is a synonym for max protocol.

    +

    This parameter is a synonym for max protocol.

    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 - concept of user names.

    • COREPLUS: Slight improvements on - CORE for efficiency.

    • LANMAN1: First +

    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 + concept of user names.

    • COREPLUS: Slight improvements on + CORE for efficiency.

    • LANMAN1: First modern version of the protocol. Long filename - support.

    • LANMAN2: Updates to Lanman1 protocol.

    • NT1: Current up to date version of the protocol. + support.

    • LANMAN2: Updates to Lanman1 protocol.

    • NT1: Current up to date version of the protocol. Used by Windows NT. Known as CIFS.

    Normally this option should not be set as the automatic negotiation phase in the SMB protocol takes care of choosing the appropriate protocol.

    Default: max protocol = NT1

    Example: max protocol = LANMAN1 -

    +

    max reported print jobs (S) -

    +

    This parameter limits the maximum number of jobs displayed in a port monitor for Samba printer queue at any given moment. If this number is exceeded, the excess jobs will not be shown. A value of zero means there is no limit on the number of @@ -3727,10 +3727,10 @@

    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 +

    This parameter limits the maximum number of smbd(8) processes concurrently running on a system and is intended as a stopgap to prevent degrading service to clients in the event that the server has insufficient resources to handle more than this number of connections. Remember that under normal operating conditions, each user will have an smbd(8) associated with him or her to handle connections to all @@ -3738,10 +3738,10 @@

    Example: max smbd processes = 1000 -

    +

    max stat cache size (G) -

    This parameter limits the size in memory of any +

    This parameter limits the size in memory of any stat cache being used to speed up case insensitive name mappings. It represents the number of kilobyte (1024) units the stat cache can use. @@ -3752,27 +3752,27 @@

    Example: max stat cache size = 100 -

    +

    max ttl (G) -

    This option tells nmbd(8) what the default 'time to live' +

    This option tells nmbd(8) what the default 'time to live' of NetBIOS names should be (in seconds) when nmbd is requesting a name using either a broadcast packet or from a WINS server. You should never need to change this parameter. The default is 3 days.

    Default: max ttl = 259200 -

    +

    max wins ttl (G) -

    This option tells smbd(8) when acting as a WINS server +

    This option tells smbd(8) when acting as a WINS server (wins support = yes) what the maximum 'time to live' of NetBIOS names that nmbd will grant will be (in seconds). You should never need to change this parameter. The default is 6 days (518400 seconds).

    Default: max wins ttl = 518400 -

    +

    max xmit (G) -

    This option controls the maximum packet size +

    This option controls the maximum packet size that will be negotiated by Samba. The default is 16644, which matches the behavior of Windows 2000. A value below 2048 is likely to cause problems. You should never need to change this parameter from its default value. @@ -3780,10 +3780,10 @@

    Example: max xmit = 8192 -

    +

    message command (G) -

    This specifies what command to run when the +

    This specifies what command to run when the server receives a WinPopup style message.

    This would normally be a command that would deliver the message somehow. How this is to be done is up to your imagination.

    An example is: @@ -3799,9 +3799,9 @@ The command takes the standard substitutions, although %u won't work (%U may be better in this case).

    Apart from the standard substitutions, some additional - ones apply. In particular:

    • %s = the filename containing - the message.

    • %t = the destination that - the message was sent to (probably the server name).

    • %f = who the message + ones apply. In particular:

      • %s = the filename containing + the message.

      • %t = the destination that + the message was sent to (probably the server name).

      • %f = who the message is from.

      You could make this command send mail, or whatever else takes your fancy. Please let us know of any really interesting ideas you have.

      @@ -3822,20 +3822,20 @@

      Example: message command = csh -c 'xedit %s; rm %s' & -

    +

    min print space (S) -

    This sets the minimum amount of free disk +

    This sets the minimum amount of free disk space that must be available before a user will be able to spool a print job. It is specified in kilobytes. The default is 0, which means a user can always spool a print job.

    Default: min print space = 0

    Example: min print space = 2000 -

    +

    min protocol (G) -

    The value of the parameter (a string) is the +

    The value of the parameter (a string) is the lowest SMB protocol dialect than Samba will support. Please refer to the max protocol parameter for a list of valid protocol names and a brief description @@ -3847,10 +3847,10 @@

    Example: min protocol = NT1 -

    +

    min receivefile size (G) -

    This option changes the behavior of smbd(8) when processing SMBwriteX calls. Any incoming +

    This option changes the behavior of smbd(8) when processing SMBwriteX calls. Any incoming SMBwriteX call on a non-signed SMB/CIFS connection greater than this value will not be processed in the normal way but will be passed to any underlying kernel recvfile or splice system call (if there is no such call Samba will emulate in user space). This allows zero-copy writes directly from network @@ -3859,19 +3859,19 @@ normal way. To enable POSIX large write support (SMB/CIFS writes up to 16Mb) this option must be nonzero. The maximum value is 128k. Values greater than 128k will be silently set to 128k.

    Note this option will have NO EFFECT if set on a SMB signed connection.

    The default is zero, which diables this option.

    Default: min receivefile size = 0 -

    +

    min wins ttl (G) -

    This option tells nmbd(8) +

    This option tells nmbd(8) when acting as a WINS server (wins support = yes) what the minimum 'time to live' of NetBIOS names that nmbd will grant will be (in seconds). You should never need to change this parameter. The default is 6 hours (21600 seconds).

    Default: min wins ttl = 21600 -

    +

    msdfs proxy (S) -

    This parameter indicates that the share is a +

    This parameter indicates that the share is a stand-in for another CIFS share whose location is specified by the value of the parameter. When clients attempt to connect to this share, they are redirected to the proxied share using @@ -3879,10 +3879,10 @@ msdfs root and host msdfs options to find out how to set up a Dfs root share.

    No default

    Example: msdfs proxy = \otherserver\someshare -

    +

    msdfs root (S) -

    If set to yes, Samba treats the +

    If set to yes, Samba treats the share as a Dfs root and allows clients to browse the distributed file system tree rooted at the share directory. Dfs links are specified in the share directory by symbolic @@ -3890,39 +3890,39 @@ and so on. For more information on setting up a Dfs tree on Samba, refer to the MSDFS chapter in the Samba3-HOWTO book.

    Default: msdfs root = no -

    +

    name cache timeout (G) -

    Specifies the number of seconds it takes before +

    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 +

    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 - resolved as follows:

    • + 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 manpage for lmhosts for details) then any name type matches for lookup. -

      • +

      • host : Do a standard host name to IP address resolution, using the system /etc/hosts , NIS, or DNS lookups. This method of name resolution is operating system depended for instance on IRIX or Solaris this may be controlled by the /etc/nsswitch.conf file. Note that this method is used only if the NetBIOS name type being queried is the 0x20 (server) name type or 0x1c (domain controllers). The latter case is only useful for active directory domains and results in a DNS query for the SRV RR entry matching _ldap._tcp.domain. -

      • wins : Query a name with +

      • wins : Query a name with the IP address listed in the WINSSERVER parameter. If no WINS server has - been specified this method will be ignored.

      • bcast : Do a broadcast on + been specified this method will be ignored.

      • bcast : Do a broadcast on each of the known local interfaces listed in the interfaces parameter. This is the least reliable of the name resolution methods as it depends on the target host being on a locally @@ -3934,10 +3934,10 @@

        Example: name resolve order = lmhosts bcast host -

    +

    netbios aliases (G) -

    This is a list of NetBIOS names that nmbd will +

    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 @@ -3947,10 +3947,10 @@

    Example: netbios aliases = TEST TEST1 TEST2 -

    +

    netbios name (G) -

    +

    This sets the NetBIOS name by which a Samba server is known. By default it is the same as the first component of the host's DNS name. If a machine is a browse server or logon server this name (or the first component of the hosts DNS name) will be the name that these services are advertised under. @@ -3963,17 +3963,17 @@

    Example: netbios name = MYNAME -

    +

    netbios scope (G) -

    This sets the NetBIOS scope that Samba will +

    This sets the NetBIOS scope that Samba will operate under. This should not be set unless every machine on your LAN also sets this value.

    Default: netbios scope = -

    +

    nis homedir (G) -

    Get the home share server from a NIS map. For +

    Get the home share server from a NIS map. For UNIX systems that use an automounter, the user's home directory will often be mounted on a workstation on demand from a remote server.

    When the Samba logon server is not the actual home directory @@ -3992,20 +3992,20 @@ NIS system and the Samba server with this option must also be a logon server.

    Default: nis homedir = no -

    +

    nt acl support (S) -

    This boolean parameter controls whether smbd(8) will attempt to map +

    This boolean parameter controls whether smbd(8) will attempt to map UNIX permissions into Windows NT access control lists. The UNIX permissions considered are the the traditional UNIX owner and group permissions, as well as POSIX ACLs set on any files or directories. 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 +

    This parameter determines whether or not smbd(8) will attempt to authenticate users using the NTLM encrypted password response. If disabled, either the lanman password hash or an NTLMv2 response will need to be sent by the client.

    If this option, and lanman @@ -4013,33 +4013,33 @@ permited. Not all clients support NTLMv2, and most will require special configuration to use it.

    Default: ntlm auth = yes -

    +

    nt pipe support (G) -

    This boolean parameter controls whether +

    This boolean parameter controls whether smbd(8) will allow Windows NT clients to connect to the NT SMB specific IPC$ pipes. This is a developer debugging option and can be left alone.

    Default: nt pipe support = yes -

    +

    nt status support (G) -

    This boolean parameter controls whether smbd(8) will negotiate NT specific status +

    This boolean parameter controls whether smbd(8) will negotiate NT specific status support with Windows NT/2k/XP clients. This is a developer debugging option and should be left alone. If this option is set to no then Samba offers exactly the same DOS error codes that versions prior to Samba 2.2.3 reported.

    You should not need to ever disable this parameter.

    Default: nt status support = yes -

    +

    null passwords (G) -

    Allow or disallow client access to accounts that have null passwords.

    See also smbpasswd(5).

    Default: null passwords = no +

    Allow or disallow client access to accounts that have null passwords.

    See also smbpasswd(5).

    Default: null passwords = no -

    +

    obey pam restrictions (G) -

    When Samba 3.0 is configured to enable PAM support +

    When Samba 3.0 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 @@ -4049,10 +4049,10 @@ authentication mechanism needed in the presence of SMB password encryption.

    Default: obey pam restrictions = no -

    +

    only user (S) -

    This is a boolean option that controls whether +

    This is a boolean option that controls whether connections with usernames not in the user list will be allowed. By default this option is disabled so that a client can supply a username to be used by the server. Enabling @@ -4065,22 +4065,22 @@ will be just the service name, which for home directories is the name of the user.

    Default: only user = no -

    +

    oplock break wait time (G) -

    +

    This is a tuning parameter added due to bugs in both Windows 9x and WinNT. If Samba responds to a client too quickly when that client issues an SMB that can cause an oplock break request, then the network client can fail and not respond to the break request. This tuning parameter (which is set in milliseconds) is the amount of time Samba will wait before sending an oplock break request to such (broken) clients. -

    Warning

    +

    Warning

    DO NOT CHANGE THIS PARAMETER UNLESS YOU HAVE READ AND UNDERSTOOD THE SAMBA OPLOCK CODE.

    Default: oplock break wait time = 0 -

    +

    oplock contention limit (S) -

    +

    This is a very advanced smbd(8) tuning option to improve the efficiency of the granting of oplocks under multiple client contention for the same file.

    @@ -4088,14 +4088,14 @@ approximate number of clients contending for an oplock on the same file goes over this limit. This causes smbd to behave in a similar way to Windows NT. -

    Warning

    +

    Warning

    DO NOT CHANGE THIS PARAMETER UNLESS YOU HAVE READ AND UNDERSTOOD THE SAMBA OPLOCK CODE.

    Default: oplock contention limit = 2 -

    +

    oplocks (S) -

    +

    This boolean option tells smbd whether to issue oplocks (opportunistic locks) to file open requests on this share. The oplock code can dramatically (approx. 30% or more) improve @@ -4114,10 +4114,10 @@ kernel oplocks parameter for details.

    Default: oplocks = yes -

    +

    os2 driver map (G) -

    The parameter is used to define the absolute +

    The parameter is used to define the absolute path to a file containing a mapping of Windows NT printer driver 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 @@ -4127,10 +4127,10 @@ details on OS/2 clients, please refer to chapter on other clients in the Samba3-HOWTO book.

    Default: os2 driver map = -

    +

    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 workgroup in the local broadcast area.

    @@ -4146,10 +4146,10 @@

    Example: os level = 65 -

    +

    pam password change (G) -

    With the addition of better PAM support in Samba 2.2, +

    With the addition of better PAM support in Samba 2.2, this parameter, it is possible to use PAM's password change control flag for Samba. If enabled, then PAM will be used for password changes when requested by an SMB client instead of the program listed in @@ -4157,20 +4157,20 @@ It should be possible to enable this without changing your passwd chat parameter for most setups.

    Default: pam password change = no -

    +

    panic action (G) -

    This is a Samba developer option that allows a +

    This is a Samba developer option that allows a system command to be called when either smbd(8) or nmbd(8) crashes. This is usually used to draw attention to the fact that a problem occurred.

    Default: panic action =

    Example: panic action = "/bin/sleep 90000" -

    +

    paranoid server security (G) -

    Some version of NT 4.x allow non-guest +

    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. @@ -4178,19 +4178,19 @@ this check, which involves deliberatly attempting a bad logon to the remote server.

    Default: paranoid server security = yes -

    +

    passdb backend (G) -

    This option allows the administrator to chose which backend +

    This option allows the administrator to chose which backend will be used for storing user and possibly group information. This allows you to swap between different storage mechanisms without recompile.

    The parameter value is divided into two parts, the backend's name, and a 'location' string that has meaning only to that particular backed. These are separated by a : character.

    Available backends can include: -

    • smbpasswd - The default smbpasswd +

      • smbpasswd - The default smbpasswd backend. Takes a path to the smbpasswd file as an optional argument. -

      • tdbsam - The TDB based password storage +

      • tdbsam - The TDB based password storage backend. Takes a path to the TDB as an optional argument (defaults to passdb.tdb - in the private dir directory.

      • ldapsam - The LDAP based passdb + in the private dir directory.

      • ldapsam - The LDAP based passdb backend. Takes an LDAP URL as an optional argument (defaults to ldap://localhost)

        LDAP connections should be secured where possible. This may be done using either Start-TLS (see ldap ssl) or by @@ -4214,19 +4214,19 @@ passdb backend = ldapsam:"ldap://ldap-1.example.com ldap-2.example.com"

        Default: passdb backend = smbpasswd -

    +

    passdb expand explicit (G) -

    +

    This parameter controls whether Samba substitutes %-macros in the passdb fields if they are explicitly set. We used to expand macros here, but this turned out to be a bug because the Windows client can expand a variable %G_osver% in which %G would have been substituted by the user's primary group.

    Default: passdb expand explicit = no -

    +

    passwd chat debug (G) -

    This boolean specifies if the passwd chat script +

    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 @@ -4239,18 +4239,18 @@ pam password change parameter is set. This parameter is off by default.

    Default: passwd chat debug = no -

    +

    passwd chat timeout (G) -

    This integer specifies the number of seconds smbd will wait for an initial +

    This integer specifies the number of seconds smbd will wait for an initial answer from a passwd chat script being run. Once the initial answer is received the subsequent answers must be received in one tenth of this time. The default it two seconds.

    Default: passwd chat timeout = 2 -

    +

    passwd chat (G) -

    This string controls the "chat" +

    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 @@ -4281,10 +4281,10 @@

    Example: passwd chat = "*Enter NEW password*" %n\n "*Reenter NEW password*" %n\n "*Password changed*" -

    +

    passwd program (G) -

    The name of a program that can be used to set +

    The name of a program that can be used to set UNIX user passwords. Any occurrences of %u will be replaced with the user name. The user name is checked for existence before calling the password changing program.

    Also note that many passwd programs insist in reasonable @@ -4305,10 +4305,10 @@

    Example: passwd program = /bin/passwd %u -

    +

    password level (G) -

    Some client/server combinations have difficulty +

    Some client/server combinations have difficulty with mixed-case passwords. One offending client is Windows for Workgroups, which for some reason forces passwords to upper case when using the LANMAN1 protocol, but leaves them alone when @@ -4330,10 +4330,10 @@

    Example: password level = 4 -

    +

    password server (G) -

    By specifying the name of another SMB server +

    By specifying the name of another SMB server or Active Directory domain controller with this option, and using security = [ads|domain|server] it is possible to get Samba @@ -4348,7 +4348,7 @@ 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 - user level security mode.

    Note

    Using a password server means your UNIX box (running + 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.

    Never point a Samba server at itself for password serving. @@ -4377,13 +4377,13 @@ this list by locating the closest DC.

    If the security parameter is set to server, then there are different restrictions that security = domain doesn't - suffer from:

    • You may list several password servers in + suffer from:

      • You may list several password servers in the password server parameter, however if an smbd makes a connection to a password server, and then the password server fails, no more users will be able to be authenticated from this smbd. This is a restriction of the SMB/CIFS protocol when in security = server - mode and cannot be fixed in Samba.

      • If you are using a Windows NT server as your + mode and cannot be fixed in Samba.

      • If you are using a Windows NT server as your password server then you will have to ensure that your users are able to login from the Samba server, as when in security = server mode the network logon will appear to @@ -4393,13 +4393,13 @@

        Example: password server = windc.mydomain.com:389 192.168.1.101 * -

    +

    directory -

    This parameter is a synonym for path.

    +

    This parameter is a synonym for path.

    path (S) -

    This parameter specifies a directory to which +

    This parameter specifies a directory to which the user of the service is to be given access. In the case of printable services, this is where print data will spool prior to being submitted to the host for printing.

    For a printable service offering guest access, the service @@ -4416,19 +4416,19 @@

    Example: path = /home/fred -

    +

    pid directory (G) -

    +

    This option specifies the directory where pid files will be placed.

    Default: pid directory = ${prefix}/var/locks

    Example: pid directory = pid directory = /var/run/ -

    +

    posix locking (S) -

    +

    The smbd(8) daemon maintains an database of file locks obtained by SMB clients. The default behavior is to map this internal database to POSIX locks. This means that file locks obtained by SMB clients are @@ -4436,10 +4436,10 @@ method (e.g. NFS or local file access). You should never need to disable this parameter.

    Default: posix locking = yes -

    +

    postexec (S) -

    This option specifies a command to be run +

    This option specifies a command to be run 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 @@ -4447,21 +4447,21 @@

    Example: postexec = echo \"%u disconnected from %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 -

    +

    exec -

    This parameter is a synonym for preexec.

    +

    This parameter is a synonym for preexec.

    preexec (S) -

    This option specifies a command to be run whenever +

    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:

    @@ -4473,13 +4473,13 @@

    Example: preexec = echo \"%u connected to %S from %m (%I)\" >> /tmp/log -

    +

    prefered master -

    This parameter is a synonym for preferred master.

    +

    This parameter is a synonym for preferred master.

    preferred master (G) -

    +

    This boolean parameter controls if nmbd(8) is a preferred master browser for its workgroup.

    If this is set to yes, on startup, nmbd will force @@ -4493,22 +4493,22 @@ capabilities.

    Default: preferred master = auto -

    +

    preload modules (G) -

    This is a list of paths to modules that should +

    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.

    Default: preload modules =

    Example: preload modules = /usr/lib/samba/passdb/mysql.so -

    +

    auto services -

    This parameter is a synonym for preload.

    +

    This parameter is a synonym for preload.

    preload (G) -

    This is a list of services that you want to be +

    This is a list of services that you want to be automatically added to the browse lists. This is most useful for homes and printers services that would otherwise not be visible.

    @@ -4519,33 +4519,33 @@

    Example: preload = fred lp colorlp -

    +

    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.

    See the section on NAME MANGLING for a fuller discussion.

    Default: preserve case = yes -

    +

    print ok -

    This parameter is a synonym for printable.

    +

    This parameter is a synonym for printable.

    printable (S) -

    If this parameter is yes, then +

    If this parameter is yes, then clients may open, write to and submit spool files on the directory specified for the service.

    Note that a printable service will ALWAYS allow writing to the service path (user privileges permitting) via the spooling of print data. The read only parameter controls only non-printing access to the resource.

    Default: printable = no -

    +

    printcap cache time (G) -

    This option specifies the number of seconds before the printing +

    This option specifies the number of seconds before the printing subsystem is again asked for the known printers. If the value is greater than 60 the initial waiting time is set to 60 seconds to allow an earlier first rescan of the printing subsystem. @@ -4555,13 +4555,13 @@

    Example: printcap cache time = 600 -

    +

    printcap -

    This parameter is a synonym for printcap name.

    +

    This parameter is a synonym for printcap name.

    printcap name (G) -

    +

    This parameter may be used to override the compiled-in default printcap name used by the server (usually /etc/printcap). See the discussion of the [printers] section above for reasons why you might want to do this.

    @@ -4589,17 +4589,17 @@

    where the '|' separates aliases of a printer. The fact that the second alias has a space in it gives a hint to Samba that it's a comment. -

    Note

    +

    Note

    Under AIX the default printcap name is /etc/qconfig. Samba will assume the file is in AIX qconfig format if the string qconfig appears in the printcap filename.

    Default: printcap name = /etc/printcap

    Example: printcap name = /etc/myprintcap -

    +

    print command (S) -

    After a print job has finished spooling to +

    After a print job has finished spooling to a service, this command will be used via a system() call to process the spool file. Typically the command specified will submit the spool file to the host's printing subsystem, but there @@ -4641,10 +4641,10 @@ and if SAMBA is compiled against libcups, any manually set print command will be ignored.

    No default

    Example: print command = /usr/local/samba/bin/myprintscript %p %s -

    +

    printer admin (S) -

    +

    This lists users who can do anything to printers via the remote administration interfaces offered by MS-RPC (usually using a NT workstation). @@ -4660,13 +4660,13 @@

    Example: printer admin = admin, @staff -

    +

    printer -

    This parameter is a synonym for printer name.

    +

    This parameter is a synonym for printer name.

    printer name (S) -

    +

    This parameter specifies the name of the printer to which print jobs spooled through a printable service will be sent.

    @@ -4679,10 +4679,10 @@

    Example: printer name = laserwriter -

    +

    printing (S) -

    This parameters controls how printer status information is +

    This parameters controls how printer status information is interpreted on your system. It also affects the default values for the print command, lpq command, lppause command , lpresume command, and lprm command if specified in the [global] section.

    Currently nine printing styles are supported. They are @@ -4699,27 +4699,27 @@ [printers] section.

    Default: printing = Depends on the operating system, see testparm -v. -

    +

    printjob username (S) -

    This parameter specifies which user information will be +

    This parameter specifies which user information will be passed to the printing system. Usually, the username is sent, but in some cases, e.g. the domain prefix is useful, too.

    Default: printjob username = %U

    Example: printjob username = %D\%U -

    +

    private dir (G) -

    This parameters defines the directory +

    This parameters defines the directory smbd will use for storing such files as smbpasswd and secrets.tdb.

    Default: private dir = ${prefix}/private -

    +

    profile acls (S) -

    +

    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 @@ -4747,10 +4747,10 @@ tree to the owning user.

    Default: profile acls = no -

    +

    queuepause command (S) -

    This parameter specifies the command to be +

    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 a printer name as its only parameter and stops the printer queue, such that no longer jobs are submitted to the printer.

    This command is not supported by Windows for Workgroups, @@ -4761,10 +4761,10 @@ path in the command as the PATH may not be available to the server.

    No default

    Example: queuepause command = disable %p -

    +

    queueresume command (S) -

    This parameter specifies the command to be +

    This parameter specifies the command to be executed on the server host in order to resume the printer queue. It is the command to undo the behavior that is caused by the previous parameter (queuepause command).

    This command should be a program or script which takes @@ -4779,10 +4779,10 @@

    Example: queueresume command = enable %p -

    +

    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 they will not be given write access, no matter what the read only option is set to. The list can include group names using the syntax described in the invalid users @@ -4792,19 +4792,19 @@

    Example: read list = mary, @students -

    +

    read only (S) -

    An inverted synonym is writeable.

    If this parameter is yes, then users +

    An inverted synonym is writeable.

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

    Note that a printable service (printable = yes) will ALWAYS allow writing to the directory (user privileges permitting), but only via spooling operations.

    Default: read only = yes -

    +

    read raw (G) -

    This parameter controls whether or not the server +

    This parameter controls whether or not the server will support the raw read SMB requests when transferring data to clients.

    If enabled, raw reads allow reads of 65535 bytes in one packet. This typically provides a major performance benefit. @@ -4813,20 +4813,20 @@ sizes, and for these clients you may need to disable raw reads.

    In general this parameter should be viewed as a system tuning tool and left severely alone.

    Default: read raw = yes -

    +

    realm (G) -

    This option specifies the kerberos realm to use. The realm is +

    This option specifies the kerberos realm to use. The realm is used as the ADS equivalent of the NT4 domain. It is usually set to the DNS name of the kerberos server.

    Default: realm =

    Example: realm = mysambabox.mycompany.com -

    +

    registry shares (G) -

    +

    This turns on or off support for share definitions read from registry. Shares defined in smb.conf take precedence over shares with the same name defined in @@ -4841,10 +4841,10 @@

    Example: registry shares = yes -

    +

    remote announce (G) -

    +

    This option allows you to setup nmbd(8) to periodically announce itself to arbitrary IP addresses with an arbitrary workgroup name.

    @@ -4868,10 +4868,10 @@ See the chapter on Network Browsing in the Samba-HOWTO book.

    Default: remote announce = -

    +

    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 @@ -4903,17 +4903,17 @@ each network has its own WINS server.

    Default: remote browse sync = -

    +

    rename user script (G) -

    +

    This is the full pathname to a script that will be run as root by smbd(8) under special circumstances described below.

    When a user with admin authority or SeAddUserPrivilege rights renames a user (e.g.: from the NT4 User Manager for Domains), this script will be run to rename the POSIX user. Two variables, %uold and %unew, will be substituted with the old and new usernames, respectively. The script should return 0 upon successful completion, and nonzero otherwise. -

    Note

    +

    Note

    The script has all responsibility to rename all the necessary data that is accessible in this posix method. This can mean different requirements for different backends. The tdbsam and smbpasswd backends will take care of the contents of their respective files, so the script is responsible only for changing the POSIX username, and @@ -4924,10 +4924,10 @@ needs to change for other applications using the same directory.

    Default: rename user script = no -

    +

    reset on zero vc (G) -

    +

    This boolean option controls whether an incoming session setup should kill other connections coming from the same IP. This matches the default Windows 2003 behaviour. @@ -4946,10 +4946,10 @@

    Default: reset on zero vc = no -

    +

    restrict anonymous (G) -

    The setting of this parameter determines whether user and +

    The setting of this parameter determines whether user and group list information is returned for an anonymous connection. and mirrors the effects of the

    @@ -4967,21 +4967,21 @@
         The security advantage of using restrict anonymous = 1 is dubious,
         as user and group list information can be obtained using other
     	means.
    -	

    Note

    +

    Note

    The security advantage of using restrict anonymous = 2 is removed by setting guest ok = yes on any share.

    Default: restrict anonymous = 0 -

    +

    root -

    This parameter is a synonym for root directory.

    +

    This parameter is a synonym for root directory.

    root dir -

    This parameter is a synonym for root directory.

    +

    This parameter is a synonym for root directory.

    root directory (G) -

    The server will chroot() (i.e. +

    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. @@ -5004,34 +5004,34 @@

    Example: root directory = /homes/smb -

    +

    root postexec (S) -

    +

    This is the same as the postexec parameter except that the command is run as root. This is useful for unmounting filesystems (such as CDROMs) after a connection is closed.

    Default: root postexec = -

    +

    root preexec close (S) -

    This is the same as the preexec close +

    This is the same as the preexec close parameter except that the command is run as root.

    Default: root preexec close = no -

    +

    root preexec (S) -

    +

    This is the same as the preexec parameter except that the command is run as root. This is useful for mounting filesystems (such as CDROMs) when a connection is opened.

    Default: root preexec = -

    +

    security mask (S) -

    +

    This parameter controls what UNIX permission bits will be set when a Windows NT client is manipulating the UNIX permission on a file using the native NT security dialog box.

    @@ -5050,10 +5050,10 @@

    Example: security mask = 0770 -

    +

    security (G) -

    This option affects how clients respond to +

    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 protocol negotiations with smbd(8) to turn share level security on or off. Clients decide @@ -5092,19 +5092,19 @@ in share level security, smbd uses several techniques to determine the correct UNIX user to use on behalf of the client.

    A list of possible UNIX usernames to match with the given - client password is constructed using the following methods :

    • If the guest only parameter is set, then all the other + client password is constructed using the following methods :

      • If the guest only parameter is set, then all the other stages are missed and only the guest account username is checked. -

      • Is a username is sent with the share connection +

      • Is a username is sent with the share connection request, then this username (after mapping - see username map), is added as a potential username. -

      • If the client did a previous logon +

      • If the client did a previous logon request (the SessionSetup SMB call) then the username sent in this SMB will be added as a potential username. -

      • The name of the service the client requested is +

      • The name of the service the client requested is added as a potential username. -

      • The NetBIOS name of the client is added to +

      • The NetBIOS name of the client is added to the list as a potential username. -

      • Any users on the user list are added as potential usernames. +

      • Any users on the user list are added as potential usernames.

      If the guest only parameter is not set, then this list is then tried with the supplied password. The first user for whom the password matches will be used as the @@ -5150,7 +5150,7 @@ server 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 +

      Note

      This mode of operation has significant pitfalls since it is more vulnerable to man-in-the-middle attacks and server impersonation. In particular, this mode of operation can cause significant resource consuption on @@ -5158,7 +5158,7 @@ of the user's session. Furthermore, if this connection is lost, there is no way to reestablish it, and futher authentications to the Samba server may fail (from a single client, till it disconnects). -

      Note

      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 @@ -5177,10 +5177,10 @@

      Example: security = DOMAIN -

    +

    server schannel (G) -

    +

    This controls whether the server offers or even demands the use of the netlogon schannel. server 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 client is not able to speak netlogon schannel. This is only the case for Windows NT4 before SP4. @@ -5191,20 +5191,20 @@

    Example: server schannel = yes -

    +

    server signing (G) -

    This controls whether the client is allowed or required to use SMB signing. Possible values +

    This controls whether the client is allowed or required 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: server signing = Disabled -

    +

    server string (G) -

    This controls what string will show up in the printer comment box in print +

    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 @@ -5213,10 +5213,10 @@

    Example: server string = University of GNUs Samba Server -

    +

    set directory (S) -

    +

    If set directory = no, then users of the service may not use the setdir command to change directory.

    @@ -5225,10 +5225,10 @@ for details.

    Default: set directory = no -

    +

    set primary group script (G) -

    Thanks to the Posix subsystem in NT a Windows User has a +

    Thanks to the Posix subsystem in NT a Windows User has a primary group in addition to the auxiliary groups. This script sets the primary group in the unix userdatase when an administrator sets the primary group from the windows user @@ -5240,23 +5240,23 @@

    Example: set primary group script = /usr/sbin/usermod -g '%g' '%u' -

    +

    set quota command (G) -

    The set quota command should only be used +

    The set quota command should only be used whenever there is no operating system API available from the OS that samba can use.

    This option is only available if Samba was configured with the argument --with-sys-quotas or on linux when ./configure --with-quotas was used and a working quota api was found in the system. Most packages are configured with these options already.

    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 on success. And nothing on failure.

    Default: set quota command = + 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 on success. And nothing on failure.

    Default: set quota command =

    Example: set quota command = /usr/local/sbin/set_quota -

    +

    share modes (S) -

    This enables or disables the honoring of +

    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.

    This is a deprecated option from old versions of @@ -5268,20 +5268,20 @@ by default.

    You should NEVER turn this parameter off as many Windows applications will break if you do so.

    Default: share modes = yes -

    +

    short preserve case (S) -

    +

    This boolean parameter 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 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 +

    With the introduction of MS-RPC based printing support 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 @@ -5296,21 +5296,21 @@ icon will not be displayed.

    Disabling the show add printer wizard parameter will always cause the OpenPrinterEx() on the server to fail. Thus the APW icon will never be displayed. -

    Note

    This does not prevent the same user from having +

    Note

    This does not prevent the same user from having administrative privilege on an individual printer.

    Default: show add printer wizard = yes -

    +

    shutdown script (G) -

    This a full path name to a script called by +

    This a full path name to a script called by smbd(8) that should start a shutdown procedure.

    If the connected user posseses the SeRemoteShutdownPrivilege, - right, this command will be run as root.

    The %z %t %r %f variables are expanded as follows:

    • %z will be substituted with the - shutdown message sent to the server.

    • %t will be substituted with the + right, this command will be run as root.

      The %z %t %r %f variables are expanded as follows:

      • %z will be substituted with the + shutdown message sent to the server.

      • %t will be substituted with the number of seconds to wait before effectively starting the - shutdown procedure.

      • %r will be substituted with the + shutdown procedure.

      • %r will be substituted with the switch -r. It means reboot after shutdown - for NT.

      • %f will be substituted with the + for NT.

      • %f will be substituted with the switch -f. It means force the shutdown even if applications do not respond for NT.

      Shutdown script example:

      @@ -5328,10 +5328,10 @@
       
       

      Example: shutdown script = /usr/local/samba/sbin/shutdown %m %t %r %f -

    +

    smb encrypt (S) -

    This is a new feature introduced with Samba 3.2 and above. It is an +

    This is a new feature introduced with Samba 3.2 and above. It is an extension to the SMB/CIFS protocol negotiated as part of the UNIX extensions. SMB encryption uses the GSSAPI (SSPI on Windows) ability to encrypt and sign every request/response in a SMB protocol stream. When @@ -5359,10 +5359,10 @@ When set to mandatory, SMB encryption is required and if set to disabled, SMB encryption can not be negotiated.

    Default: smb encrypt = auto -

    +

    smb passwd file (G) -

    This option sets the path to the encrypted smbpasswd file. By +

    This option sets the path to the encrypted smbpasswd file. By default the path to the smbpasswd file is compiled into Samba.

    An example of use is:

    @@ -5370,15 +5370,15 @@
     

    Default: smb passwd file = ${prefix}/private/smbpasswd -

    +

    smb ports (G) -

    Specifies which ports the server should listen on for SMB traffic.

    Default: smb ports = 445 139 +

    Specifies which ports the server should listen on for SMB traffic.

    Default: smb ports = 445 139 -

    +

    socket address (G) -

    This option allows you to control what +

    This option allows you to control what address Samba will listen for connections on. This is used to support multiple virtual interfaces on the one server, each with a different configuration.

    Setting this option should never be necessary on usual Samba @@ -5387,10 +5387,10 @@

    Example: socket address = 192.168.2.20 -

    +

    socket options (G) -

    This option allows you to set socket options +

    This option allows you to set socket options to be used when talking with the client.

    Socket options are controls on the networking layer of the operating systems which allow the connection to be tuned.

    This option will typically be used to tune your Samba server @@ -5406,7 +5406,7 @@ send the patch to samba-technical@samba.org.

    Any of the supported socket options may be combined in any way you like, as long as your OS allows it.

    This is the list of socket options currently settable - using this option:

    • SO_KEEPALIVE

    • SO_REUSEADDR

    • SO_BROADCAST

    • TCP_NODELAY

    • IPTOS_LOWDELAY

    • IPTOS_THROUGHPUT

    • SO_SNDBUF *

    • SO_RCVBUF *

    • SO_SNDLOWAT *

    • SO_RCVLOWAT *

    Those marked with a '*' take an integer + using this option:

    • SO_KEEPALIVE

    • SO_REUSEADDR

    • SO_BROADCAST

    • TCP_NODELAY

    • IPTOS_LOWDELAY

    • IPTOS_THROUGHPUT

    • SO_SNDBUF *

    • SO_RCVBUF *

    • SO_SNDLOWAT *

    • SO_RCVLOWAT *

    Those marked with a '*' take an integer argument. The others can optionally take a 1 or 0 argument to enable or disable the option, by default they will be enabled if you don't specify 1 or 0.

    To specify an argument use the syntax SOME_OPTION = VALUE @@ -5418,17 +5418,17 @@

    Example: socket options = IPTOS_LOWDELAY -

    +

    stat cache (G) -

    This parameter determines if smbd(8) will use a cache in order to +

    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 -

    +

    store dos attributes (S) -

    +

    If this parameter is set Samba attempts to first read DOS attributes (SYSTEM, HIDDEN, ARCHIVE or READ-ONLY) from a filesystem extended attribute, before mapping DOS attributes to UNIX permission bits (such as occurs with map hidden and map readonly). When set, DOS @@ -5440,10 +5440,10 @@ extended attributes to work, also extended attributes must be compiled into the Linux kernel.

    Default: store dos attributes = no -

    +

    strict allocate (S) -

    This is a boolean that controls the handling of +

    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 @@ -5455,10 +5455,10 @@ out of quota messages on systems that are restricting the disk quota of users.

    Default: strict allocate = no -

    +

    strict locking (S) -

    +

    This is an enumerated type that controls the handling of file locking in the server. When this is set to yes, the server will check every read and write access for file locks, and deny access if locks exist. This can be slow on some systems. @@ -5474,10 +5474,10 @@ strict locking = no is acceptable.

    Default: strict locking = Auto -

    +

    strict sync (S) -

    Many Windows applications (including the Windows 98 explorer +

    Many Windows applications (including the Windows 98 explorer shell) seem to confuse flushing buffer contents to disk with doing a sync to disk. Under UNIX, a sync call forces the process to be suspended until the kernel has ensured that all outstanding data in @@ -5491,10 +5491,10 @@ addition, this fixes many performance problems that people have reported with the new Windows98 explorer shell file copies.

    Default: strict sync = no -

    +

    svcctl list (G) -

    This option defines a list of init scripts that smbd +

    This option defines a list of init scripts that smbd will use for starting and stopping Unix services via the Win32 ServiceControl API. This allows Windows administrators to utilize the MS Management Console plug-ins to manage a @@ -5507,10 +5507,10 @@

    Example: svcctl list = cups postfix portmap httpd -

    +

    sync always (S) -

    This is a boolean parameter that controls +

    This is a boolean parameter that controls whether writes will always be written to stable storage before the write call returns. If this is no then the server will be guided by the client's request in each write call (clients can @@ -5521,19 +5521,19 @@ yes in order for this parameter to have any affect.

    Default: sync always = no -

    +

    syslog only (G) -

    +

    If this parameter is set then Samba debug messages are logged into the system syslog only, and not to the debug log files. There still will be some logging to log.[sn]mbd even if syslog only is enabled.

    Default: syslog only = no -

    +

    syslog (G) -

    +

    This parameter maps how Samba debug messages are logged onto the system syslog logging levels. Samba debug level zero maps onto syslog LOG_ERR, debug level one maps onto LOG_WARNING, debug level two maps onto LOG_NOTICE, @@ -5544,10 +5544,10 @@ logging to log.[sn]mbd even if syslog only is enabled.

    Default: syslog = 1 -

    +

    template homedir (G) -

    When filling out the user information for a Windows NT +

    When filling out the user information for a Windows NT user, the winbindd(8) daemon uses this parameter to fill in the home directory for that user. If the string %D is present it @@ -5555,31 +5555,31 @@ 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 +

    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.

    No default

    + parameter to fill in the login shell for that user.

    No default

    time offset (G) -

    This parameter is a setting in minutes to add +

    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 +

    This parameter determines if nmbd(8) advertises itself as a time server to Windows clients.

    Default: time server = no -

    +

    unix charset (G) -

    Specifies the charset the unix machine +

    Specifies the charset the unix machine Samba runs on uses. Samba needs to know this in order to be able to convert text to the charsets other SMB clients use.

    This is also the charset Samba will use when specifying arguments @@ -5588,20 +5588,23 @@

    Example: unix charset = ASCII -

    +

    unix extensions (G) -

    This boolean parameter controls whether Samba +

    This boolean parameter controls whether Samba implements the CIFS UNIX extensions, as defined by HP. 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 = yes + no current use to Windows clients.

    + Note if this parameter is turned on, the wide links + parameter will automatically be disabled. +

    Default: unix extensions = yes -

    +

    unix password sync (G) -

    This boolean parameter controls whether Samba +

    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 @@ -5610,10 +5613,10 @@ old UNIX password (as the SMB password change code has no access to the old password cleartext, only the new).

    Default: unix password sync = no -

    +

    update encrypted (G) -

    +

    This boolean parameter allows a user logging on with a plaintext password to have their encrypted (hashed) password in the smbpasswd file to be updated automatically as they log on. This option allows a site to migrate from plaintext password authentication (users authenticate with plaintext password over the @@ -5631,10 +5634,10 @@ passwords.

    Default: update encrypted = no -

    +

    use client driver (S) -

    This parameter applies only to Windows NT/2000 +

    This parameter applies only to Windows NT/2000 clients. It has no effect on Windows 95/98/ME clients. When serving a printer to Windows NT/2000 clients without first installing a valid printer driver on the Samba host, the client will be required @@ -5659,10 +5662,10 @@ on a print share which has valid print driver installed on the Samba server.

    Default: use client driver = no -

    +

    use kerberos keytab (G) -

    +

    Specifies whether Samba should attempt to maintain service principals in the systems keytab file for host/FQDN and cifs/FQDN.

    @@ -5674,10 +5677,10 @@

    Default: use kerberos keytab = False -

    +

    use mmap (G) -

    This global parameter determines if the tdb internals of Samba can +

    This global parameter determines if the tdb internals of Samba can depend on mmap working correctly on the running system. Samba requires a coherent mmap/read-write system memory cache. Currently only HPUX does not have such a coherent cache, and so this parameter is set to no by @@ -5686,10 +5689,10 @@ the tdb internal code.

    Default: use mmap = yes -

    +

    username level (G) -

    This option helps Samba to try and 'guess' at +

    This option helps Samba to try and 'guess' at the real UNIX username, as many DOS clients send an all-uppercase username. By default Samba tries all lowercase, followed by the username with the first letter capitalized, and fails if the @@ -5704,10 +5707,10 @@

    Example: username level = 5 -

    +

    username map script (G) -

    This script is a mutually exclusive alternative to the +

    This script is a mutually exclusive alternative to the username map parameter. This parameter specifies and external program or script that must accept a single command line option (the username transmitted in the authentication @@ -5718,10 +5721,10 @@

    Example: username map script = /etc/samba/scripts/mapusers.sh -

    +

    username map (G) -

    +

    This option allows you to specify a file containing a mapping of usernames from the clients to the server. This can be used for several purposes. The most common is to map usernames that users use on DOS or Windows machines to those that the UNIX box uses. The other is to map multiple users to a single username so that they @@ -5805,16 +5808,16 @@

    Default: username map = # no username map -

    +

    user -

    This parameter is a synonym for username.

    +

    This parameter is a synonym for username.

    users -

    This parameter is a synonym for username.

    +

    This parameter is a synonym for username.

    username (S) -

    Multiple users may be specified in a comma-delimited +

    Multiple users may be specified in a comma-delimited list, in which case the supplied password will be tested against each username in turn (left to right).

    The username line is needed only when the PC is unable to supply its own username. This is the case @@ -5852,28 +5855,28 @@

    Example: username = fred, mary, jack, jane, @users, @pcgroup -

    +

    usershare allow guests (G) -

    This parameter controls whether user defined shares are allowed +

    This parameter controls whether user defined shares are allowed to be accessed by non-authenticated users or not. It is the equivalent of allowing people who can create a share the option of setting guest ok = yes in a share definition. Due to its security sensitive nature, the default is set to off.

    Default: usershare allow guests = no -

    +

    usershare max shares (G) -

    This parameter specifies the number of user defined shares +

    This parameter specifies the number of user defined shares that are allowed to be created by users belonging to the group owning the usershare directory. If set to zero (the default) user defined shares are ignored.

    Default: usershare max shares = 0 -

    +

    usershare owner only (G) -

    This parameter controls whether the pathname exported by +

    This parameter controls whether the pathname exported by a user defined shares must be owned by the user creating the user defined share or not. If set to True (the default) then smbd checks that the directory path being shared is owned by @@ -5883,10 +5886,10 @@ regardless of who owns it.

    Default: usershare owner only = True -

    +

    usershare path (G) -

    This parameter specifies the absolute path of the directory on the +

    This parameter specifies the absolute path of the directory on the filesystem used to store the user defined share definition files. This directory must be owned by root, and have no access for other, and be writable only by the group owner. In addition the @@ -5907,10 +5910,10 @@ In this case, only members of the group "power_users" can create user defined shares.

    Default: usershare path = NULL -

    +

    usershare prefix allow list (G) -

    This parameter specifies a list of absolute pathnames +

    This parameter specifies a list of absolute pathnames the root of which are allowed to be exported by user defined share definitions. If the pathname to be exported doesn't start with one of the strings in this list, the user defined share will not be allowed. This allows the Samba @@ -5925,10 +5928,10 @@

    Example: usershare prefix allow list = /home /data /space -

    +

    usershare prefix deny list (G) -

    This parameter specifies a list of absolute pathnames +

    This parameter specifies a list of absolute pathnames the root of which are NOT allowed to be exported by user defined share definitions. If the pathname exported starts with one of the strings in this list the user defined share will not be allowed. Any pathname not @@ -5944,10 +5947,10 @@

    Example: usershare prefix deny list = /etc /dev /private -

    +

    usershare template share (G) -

    User defined shares only have limited possible parameters +

    User defined shares only have limited possible parameters such as path, guest ok, etc. This parameter allows usershares to "cloned" from an existing share. If "usershare template share" is set to the name of an existing share, then all usershares @@ -5962,10 +5965,10 @@

    Example: usershare template share = template_share -

    +

    use sendfile (S) -

    If this parameter is yes, and the sendfile() +

    If this parameter is yes, and the sendfile() system call is supported by the underlying operating system, then some SMB read calls (mainly ReadAndX and ReadRaw) will use the more efficient sendfile system call for files that are exclusively oplocked. This may make more efficient use of the system CPU's @@ -5974,10 +5977,10 @@ Windows 9x (using sendfile from Linux will cause these clients to fail).

    Default: use sendfile = false -

    +

    use spnego (G) -

    This variable controls controls whether samba will try +

    This variable controls controls whether samba will try to use Simple and Protected NEGOciation (as specified by rfc2478) with WindowsXP and Windows2000 clients to agree upon an authentication mechanism.

    @@ -5985,10 +5988,10 @@ implementation, there is no reason this should ever be disabled.

    Default: use spnego = yes -

    +

    utmp directory (G) -

    This parameter is only available if Samba has +

    This parameter is only available if Samba has been configured and compiled with the option --with-utmp. It specifies a directory pathname that is used to store the utmp or utmpx files (depending on the UNIX system) that @@ -6000,10 +6003,10 @@

    Example: utmp directory = /var/run/utmp -

    +

    utmp (G) -

    +

    This boolean parameter is only available if Samba has been configured and compiled with the option --with-utmp. If set to yes then Samba will attempt to add utmp or utmpx records @@ -6015,10 +6018,10 @@ to find this number. This may impede performance on large installations.

    Default: utmp = no -

    +

    valid users (S) -

    +

    This is a list of users that should be allowed to login to this service. Names starting with '@', '+' and '&' are interpreted using the same rules as described in the invalid users parameter. @@ -6034,10 +6037,10 @@

    Example: valid users = greg, @pcusers -

    +

    -valid (S) -

    This parameter indicates whether a share is +

    This parameter indicates whether a share is valid and thus can be used. When this parameter is set to false, the share will be in no way visible nor accessible.

    @@ -6046,10 +6049,10 @@ Samba uses this option internally to mark shares as deleted.

    Default: -valid = yes -

    +

    veto files (S) -

    +

    This is a list of files and directories that are neither visible nor accessible. Each entry in the list must be separated by a '/', which allows spaces to be included in the entry. '*' and '?' can be used to specify multiple files or directories as in DOS wildcards. @@ -6080,10 +6083,10 @@

    Default: veto files = No files or directories are vetoed. -

    +

    veto oplock files (S) -

    +

    This parameter is only valid when the oplocks parameter is turned on for a share. It allows the Samba administrator to selectively turn off the granting of oplocks on selected files that @@ -6104,42 +6107,47 @@

    Default: veto oplock files = # No files are vetoed for oplock grants -

    +

    vfs object -

    This parameter is a synonym for vfs objects.

    +

    This parameter is a synonym for vfs objects.

    vfs objects (S) -

    This parameter specifies the backend names which +

    This parameter specifies the backend names which are used for Samba VFS I/O operations. By default, normal disk I/O operations are used but these can be overloaded with one or more VFS objects.

    Default: vfs objects =

    Example: vfs objects = extd_audit recycle -

    +

    volume (S) -

    This allows you to override the volume label +

    This allows you to override the volume label returned for a share. Useful for CDROMs with installation programs that insist on a particular volume label.

    Default: volume = # the name of the share -

    +

    wide links (S) -

    This parameter controls whether or not links +

    This parameter controls whether or not links in the UNIX file system may be followed by the server. Links that point to areas within the directory tree exported by the server are always allowed; this parameter controls access only - to areas that are outside the directory tree being exported.

    Note that setting this parameter can have a negative - effect on your server performance due to the extra system calls - that Samba has to do in order to perform the link checks.

    Default: wide links = yes + to areas that are outside the directory tree being exported.

    Note: Turning this parameter on when UNIX extensions are enabled + will allow UNIX clients to create symbolic links on the share that + can point to files or directories outside restricted path exported + by the share definition. This can cause access to areas outside of + the share. Due to this problem, this parameter will be automatically + disabled (with a message in the log file) if the + unix extensions option is on. +

    Default: wide links = no -

    +

    winbind cache time (G) -

    This parameter specifies the number of +

    This parameter specifies the number of seconds the winbindd(8) daemon will cache user and group information before querying a Windows NT server again.

    @@ -6147,36 +6155,36 @@ evaluated in real time unless the winbind offline logon option has been enabled.

    Default: winbind cache time = 300 -

    +

    winbind enum groups (G) -

    On large installations using winbindd(8) it may be necessary to suppress +

    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 the winbind enum groups parameter is no, calls to the getgrent() system - call will not return any data.

    Warning

    Turning off group enumeration may cause some programs to behave oddly.

    Default: winbind enum groups = no + call will not return any data.

    Warning

    Turning off group enumeration may cause some programs to behave oddly.

    Default: winbind enum groups = no -

    +

    winbind enum users (G) -

    On large installations using winbindd(8) it may be +

    On large installations using winbindd(8) it may be necessary to suppress the enumeration of users through the setpwent(), getpwent() and endpwent() group of system calls. If the winbind enum users parameter is no, calls to the getpwent system call - will not return any data.

    Warning

    Turning off user + will not return any data.

    Warning

    Turning off user enumeration may cause some programs to behave oddly. For example, the finger program relies on having access to the full user list when searching for matching usernames.

    Default: winbind enum users = no -

    +

    winbind expand groups (G) -

    This option controls the maximum depth that winbindd +

    This option controls the maximum depth that winbindd will traverse when flattening nested group memberships of Windows domain groups. This is different from the winbind nested groups option @@ -6188,10 +6196,10 @@ must perform the group unrolling and will be unable to answer incoming NSS or authentication requests during this time.

    Default: winbind expand groups = 1 -

    +

    winbind nested groups (G) -

    If set to yes, this parameter activates the support for nested +

    If set to yes, this parameter activates the support for nested groups. Nested groups are also called local groups or aliases. They work like their counterparts in Windows: Nested groups are defined locally on any machine (they are shared @@ -6199,10 +6207,10 @@ global groups from any trusted SAM. To be able to use nested groups, you need to run nss_winbind.

    Default: winbind nested groups = yes -

    +

    winbind normalize names (G) -

    This parameter controls whether winbindd will replace +

    This parameter controls whether winbindd will replace whitespace in user and group names with an underscore (_) character. For example, whether the name "Space Kadet" should be replaced with the string "space_kadet". @@ -6216,23 +6224,23 @@ version. Please refer to the manpage for the configured idmap and nss_info plugin for the specifics on how to configure name aliasing for a specific configuration. Name aliasing takes - precendence (and is mutually exclusive) over the whitespace + precedence (and is mutually exclusive) over the whitespace replacement mechanism discussed previsouly.

    Default: winbind normalize names = no

    Example: winbind normalize names = yes -

    +

    winbind nss info (G) -

    This parameter is designed to control how Winbind retrieves Name +

    This parameter is designed to control how Winbind retrieves Name Service Information to construct a user's home directory and login shell. Currently the following settings are available: -

    • template +

      • template - The default, using the parameters of template shell and template homedir) -

      • <sfu | rfc2307 > +

      • <sfu | rfc2307 > - When Samba is running in security = ads and your Active Directory Domain Controller does support the Microsoft "Services for Unix" (SFU) LDAP schema, winbind can retrieve the login shell and the home @@ -6247,10 +6255,10 @@

        Example: winbind nss info = template sfu -

    +

    winbind offline logon (G) -

    This parameter is designed to control whether Winbind should +

    This parameter is designed to control whether Winbind should allow to login with the pam_winbind module using Cached Credentials. If enabled, winbindd will store user credentials from successful logins encrypted in a local cache. @@ -6258,37 +6266,37 @@

    Example: winbind offline logon = true -

    +

    winbind reconnect delay (G) -

    This parameter specifies the number of +

    This parameter specifies the number of seconds the winbindd(8) daemon will wait between attempts to contact a Domain controller for a domain that is determined to be down or not contactable.

    Default: winbind reconnect delay = 30 -

    +

    winbind refresh tickets (G) -

    This parameter is designed to control whether Winbind should refresh Kerberos Tickets +

    This parameter is designed to control whether Winbind should refresh Kerberos Tickets retrieved using the pam_winbind module.

    Default: winbind refresh tickets = false

    Example: winbind refresh tickets = true -

    +

    winbind rpc only (G) -

    +

    Setting this parameter to yes forces winbindd to use RPC instead of LDAP to retrieve information from Domain Controllers.

    Default: winbind rpc only = no -

    +

    winbind separator (G) -

    This parameter allows an admin to define the character +

    This parameter allows an admin to define the character used when listing a username of the form of DOMAIN \user. This parameter is only applicable when using the pam_winbind.so @@ -6299,10 +6307,10 @@

    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 via NIS, rsync, or LDAP as the uid's for winbindd users in the hosts primary domain. @@ -6313,10 +6321,10 @@ Refer to the idmap_nss(8) man page for more information.

    Default: winbind trusted domains only = no -

    +

    winbind use default domain (G) -

    This parameter specifies whether the +

    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 @@ -6326,48 +6334,48 @@

    Example: winbind use default domain = yes -

    +

    wins hook (G) -

    When Samba is running as a WINS server this +

    When Samba is running as a WINS server this allows you to call an external program for all changes to the WINS database. The primary use for this option is to allow the 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 + 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 can be ignored as the rest of the parameters provide sufficient information. Note that "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 + 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. Legal names contain only letters, digits, hyphens, underscores - and periods.

      • The third argument is the NetBIOS name - type as a 2 digit hexadecimal number.

      • The fourth argument is the TTL (time to live) - for the name in seconds.

      • The fifth and subsequent arguments are the IP + and periods.

      • The third argument is the NetBIOS name + type as a 2 digit hexadecimal number.

      • The fourth argument is the TTL (time to live) + for the name in seconds.

      • The fifth and subsequent arguments are the IP 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.

      No default

    + directory of the Samba source code.

    No default

    wins proxy (G) -

    This is a boolean that controls if nmbd(8) will respond to broadcast name +

    This is a boolean that controls if nmbd(8) will respond to broadcast name queries on behalf of other hosts. You may need to set this to yes for some older clients.

    Default: wins proxy = no -

    +

    wins server (G) -

    This specifies the IP address (or DNS name: IP +

    This specifies the IP address (or DNS name: IP address for preference) of the WINS server that nmbd(8) should register with. If you have a WINS server on your network then you should set this to the WINS server's IP.

    You should point this at your WINS server if you have a multi-subnetted network.

    If you want to work in multiple namespaces, you can give every wins server a 'tag'. For each tag, only one (working) server will be queried for a name. The tag should be separated from the ip address by a colon. -

    Note

    You need to set up Samba to point +

    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 chapter in the Samba3-HOWTO on Network Browsing.

    Default: wins server = @@ -6379,19 +6387,19 @@

    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 +

    This boolean controls if the nmbd(8) process in Samba will act as a WINS server. You should not set this to yes unless you have a multi-subnetted network and you wish a particular nmbd to be your WINS server. Note that you should NEVER set this to yes on more than one machine in your network.

    Default: wins support = no -

    +

    workgroup (G) -

    This controls what workgroup your server will +

    This controls what workgroup your server will appear to be in when queried by clients. Note that this parameter also controls the Domain name used with the security = domain @@ -6399,18 +6407,18 @@

    Example: workgroup = MYGROUP -

    +

    writable -

    This parameter is a synonym for writeable.

    +

    This parameter is a synonym for writeable.

    writeable (S) -

    Inverted synonym for read only.

    Default: writeable = no +

    Inverted synonym for read only.

    Default: writeable = no -

    +

    write cache size (S) -

    If this integer parameter is set to non-zero value, +

    If this integer parameter is set to non-zero value, Samba will create an in-memory cache for each oplocked file (it does not do this for non-oplocked files). All writes that the client does not request @@ -6428,10 +6436,10 @@

    Example: write cache size = 262144 # for a 256k cache size per file -

    +

    write list (S) -

    +

    This is a list of users that are given read-write access to a service. If the connecting user is in this list then they will be given write access, no matter what the read only option is set to. The list can @@ -6446,17 +6454,17 @@

    Example: write list = admin, root, @staff -

    +

    write raw (G) -

    This parameter controls whether or not the server +

    This parameter controls whether or not the server will support raw write SMB's when transferring data from clients. You should never need to change this parameter.

    Default: write raw = yes -

    +

    wtmp directory (G) -

    +

    This parameter is only available if Samba has been configured and compiled with the option --with-utmp. It specifies a directory pathname that is used to store the wtmp or wtmpx files (depending on the UNIX system) that record user connections to a Samba server. The difference with the utmp directory is the fact @@ -6468,7 +6476,7 @@

    Example: wtmp directory = /var/log/wtmp -

    WARNINGS

    +

    WARNINGS

    Although the configuration file permits service names to contain spaces, your client software may not. Spaces will be ignored in comparisons anyway, so it shouldn't be a problem - but be aware of the possibility.

    @@ -6481,8 +6489,8 @@ for an administrator easy, but the various combinations of default attributes can be tricky. Take extreme care when designing these sections. In particular, ensure that the permissions on spool directories are correct. -

    VERSION

    This man page is correct for version 3 of the Samba suite.

    AUTHOR

    +

    VERSION

    This man page is correct for version 3 of the Samba suite.

    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.

    diff -u -r --new-file --exclude .svn --exclude CVS samba-3.3.10//docs/htmldocs/manpages/smbcontrol.1.html samba-3.3.11//docs/htmldocs/manpages/smbcontrol.1.html --- samba-3.3.10//docs/htmldocs/manpages/smbcontrol.1.html 2010-01-14 11:21:11.000000000 +0100 +++ samba-3.3.11//docs/htmldocs/manpages/smbcontrol.1.html 2010-02-22 16:53:37.000000000 +0100 @@ -1,5 +1,5 @@ -smbcontrol

    Name

    smbcontrol — send messages to smbd, nmbd or winbindd processes

    Synopsis

    smbcontrol [-i] [-s]

    smbcontrol [destination] [message-type] [parameter]

    DESCRIPTION

    This tool is part of the samba(7) suite.

    smbcontrol is a very small program, which - sends messages to a smbd(8), a nmbd(8), or a winbindd(8) daemon running on the system.

    OPTIONS

    -h|--help

    Print a summary of command line options. +smbcontrol

    Name

    smbcontrol — send messages to smbd, nmbd or winbindd processes

    Synopsis

    smbcontrol [-i] [-s]

    smbcontrol [destination] [message-type] [parameter]

    DESCRIPTION

    This tool is part of the samba(7) suite.

    smbcontrol is a very small program, which + sends messages to a smbd(8), a nmbd(8), or a winbindd(8) daemon running on the system.

    OPTIONS

    -h|--help

    Print a summary of command line options.

    -s|--configfile <configuration file>

    The file specified contains the configuration details required by the server. The information in this file includes server-specific @@ -22,7 +22,7 @@ winbindd.pid file.

    If a single process ID is given, the message is sent to only that process.

    message-type

    Type of message to send. See the section MESSAGE-TYPES for details. -

    parameters

    any parameters required for the message-type

    MESSAGE-TYPES

    Available message types are:

    close-share

    Order smbd to close the client +

    parameters

    any parameters required for the message-type

    MESSAGE-TYPES

    Available message types are:

    close-share

    Order smbd to close the client connections to the named share. Note that this doesn't affect client connections to any other shares. This message-type takes an argument of the share name for which client connections will be closed, or the @@ -57,7 +57,7 @@ Note that this message only sends notification that an event has occured. It doesn't actually cause the event to happen. -

    This message can only be sent to smbd.

    samsync

    Order smbd to synchronise sam database from PDC (being BDC). Can only be sent to smbd.

    Note

    Not working at the moment

    samrepl

    Send sam replication message, with specified serial. Can only be sent to smbd. Should not be used manually.

    dmalloc-mark

    Set a mark for dmalloc. Can be sent to both smbd and nmbd. Only available if samba is built with dmalloc support.

    dmalloc-log-changed

    +

    This message can only be sent to smbd.

    samsync

    Order smbd to synchronise sam database from PDC (being BDC). Can only be sent to smbd.

    Note

    Not working at the moment

    samrepl

    Send sam replication message, with specified serial. Can only be sent to smbd. Should not be used manually.

    dmalloc-mark

    Set a mark for dmalloc. Can be sent to both smbd and nmbd. Only available if samba is built with dmalloc support.

    dmalloc-log-changed

    Dump the pointers that have changed since the mark set by dmalloc-mark. Can be sent to both smbd and nmbd. Only available if samba is built with dmalloc support.

    shutdown

    Shut down specified daemon. Can be sent to both smbd and nmbd.

    pool-usage

    Print a human-readable description of all talloc(pool) memory usage by the specified daemon/process. Available @@ -65,8 +65,8 @@ to update their local version of the driver. Can only be 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 of - the Samba suite.

    SEE ALSO

    nmbd(8) and smbd(8).

    AUTHOR

    The original Samba software and related utilities +

    VERSION

    This man page is correct for version 3 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 to the way the Linux kernel is developed.

    The original Samba man pages were written by Karl Auer. diff -u -r --new-file --exclude .svn --exclude CVS samba-3.3.10//docs/htmldocs/manpages/smbcquotas.1.html samba-3.3.11//docs/htmldocs/manpages/smbcquotas.1.html --- samba-3.3.10//docs/htmldocs/manpages/smbcquotas.1.html 2010-01-14 11:21:12.000000000 +0100 +++ samba-3.3.11//docs/htmldocs/manpages/smbcquotas.1.html 2010-02-22 16:53:37.000000000 +0100 @@ -1,4 +1,4 @@ -smbcquotas

    Name

    smbcquotas — Set or get QUOTAs of NTFS 5 shares

    Synopsis

    smbcquotas {//server/share} [-u user] [-L] [-F] [-S QUOTA_SET_COMMAND] [-n] [-t] [-v] [-d debuglevel] [-s configfile] [-l logdir] [-V] [-U username] [-N] [-k] [-A]

    DESCRIPTION

    This tool is part of the samba(7) suite.

    The smbcquotas program manipulates NT Quotas on SMB file shares.

    OPTIONS

    The following options are available to the smbcquotas program.

    -u user

    Specifies the user of whom the quotas are get or set. +smbcquotas

    Name

    smbcquotas — Set or get QUOTAs of NTFS 5 shares

    Synopsis

    smbcquotas {//server/share} [-u user] [-L] [-F] [-S QUOTA_SET_COMMAND] [-n] [-t] [-v] [-d debuglevel] [-s configfile] [-l logdir] [-V] [-U username] [-N] [-k] [-A]

    DESCRIPTION

    This tool is part of the samba(7) suite.

    The smbcquotas program manipulates NT Quotas on SMB file shares.

    OPTIONS

    The following options are available to the smbcquotas program.

    -u user

    Specifies the user of whom the quotas are get or set. By default the current user's username will be used.

    -L

    Lists all quota records of the share.

    -F

    Show the share quota status and default limits.

    -S QUOTA_SET_COMMAND

    This command sets/modifies quotas for a user or on the share, depending on the QUOTA_SET_COMMAND parameter which is described later.

    -n

    This option displays all QUOTA information in numeric format. The default is to convert SIDs to names and QUOTA limits @@ -40,6 +40,8 @@ be silently ingnored and no password will be used.

    -k|--kerberos

    Try to authenticate with kerberos. Only useful in an Active Directory environment. +

    -C|--use-ccache

    +Try to use the credentials cached by winbind.

    -A|--authentication-file=filename

    This option allows you to specify a file from which to read the username and password used in the connection. The format of the file is @@ -62,7 +64,7 @@ many systems the command line of a running process may be seen via the ps command. To be safe always allow rpcclient to prompt for a password and type -it in directly.

    QUOTA_SET_COMAND

    The format of an the QUOTA_SET_COMMAND is an operation +it in directly.

    QUOTA_SET_COMAND

    The format of an the QUOTA_SET_COMMAND is an operation name followed by a set of parameters specific to that operation.

    To set user quotas for the user specified by -u or for the current username:

    @@ -74,13 +76,13 @@ To change the share quota settings:

    FSQFLAGS:QUOTA_ENABLED/DENY_DISK/LOG_SOFTLIMIT/LOG_HARD_LIMIT -

    All limits are specified as a number of bytes.

    EXIT STATUS

    The smbcquotas program sets the exit status +

    All limits are specified as a number of bytes.

    EXIT STATUS

    The smbcquotas program sets the exit status depending on the success or otherwise of the operations performed. The exit status may be one of the following values.

    If the operation succeeded, smbcquotas returns an exit status of 0. If smbcquotas couldn't connect to the specified server, or when there was an error getting or setting the quota(s), an exit status of 1 is returned. If there was an error parsing any command line - arguments, an exit status of 2 is returned.

    VERSION

    This man page is correct for version 3 of the Samba suite.

    AUTHOR

    The original Samba software and related utilities + arguments, an exit status of 2 is returned.

    VERSION

    This man page is correct for version 3 of the Samba suite.

    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.

    smbcquotas was written by Stefan Metzmacher.

    diff -u -r --new-file --exclude .svn --exclude CVS samba-3.3.10//docs/htmldocs/manpages/smbd.8.html samba-3.3.11//docs/htmldocs/manpages/smbd.8.html --- samba-3.3.10//docs/htmldocs/manpages/smbd.8.html 2010-01-14 11:21:14.000000000 +0100 +++ samba-3.3.11//docs/htmldocs/manpages/smbd.8.html 2010-02-22 16:53:37.000000000 +0100 @@ -1,4 +1,4 @@ -smbd

    Name

    smbd — server to provide SMB/CIFS services to clients

    Synopsis

    smbd [-D] [-F] [-S] [-i] [-h] [-V] [-b] [-d <debug level>] [-l <log directory>] [-p <port number(s)>] [-P <profiling level>] [-O <socket option>] [-s <configuration file>]

    DESCRIPTION

    This program is part of the samba(7) suite.

    smbd is the server daemon that +smbd

    Name

    smbd — server to provide SMB/CIFS services to clients

    Synopsis

    smbd [-D] [-F] [-S] [-i] [-h] [-V] [-b] [-d <debug level>] [-l <log directory>] [-p <port number(s)>] [-P <profiling level>] [-O <socket option>] [-s <configuration file>]

    DESCRIPTION

    This program is part of the samba(7) suite.

    smbd is the server daemon that provides filesharing and printing services to Windows clients. The server provides filespace and printer services to clients using the SMB (or CIFS) protocol. This is compatible @@ -21,7 +21,7 @@ can force a reload by sending a SIGHUP to the server. Reloading the configuration file will not affect connections to any service that is already established. Either the user will have to - disconnect from the service, or smbd killed and restarted.

    OPTIONS

    -D

    If specified, this parameter causes + disconnect from the service, or smbd killed and restarted.

    OPTIONS

    -D

    If specified, this parameter causes the server to operate as a daemon. That is, it detaches itself and runs in the background, fielding requests on the appropriate port. Operating the server as a @@ -44,7 +44,7 @@ than a file.

    -i

    If this parameter is specified it causes 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 deamon mode when run from the + parameter negates the implicit daemon mode when run from the command line. smbd also logs to standard output, as if the -S parameter had been given. @@ -82,7 +82,7 @@ number specifying the level of profiling data to be collected. 0 turns off profiling, 1 turns on counter profiling only, 2 turns on complete profiling, and 3 resets all profiling data. -

    FILES

    /etc/inetd.conf

    If the server is to be run by the +

    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. @@ -96,31 +96,31 @@

    /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 + is to make available to clients. See smb.conf(5) for more information.

    LIMITATIONS

    On some systems smbd cannot change uid back to root after a setuid() call. Such systems are called trapdoor uid systems. If you have such a system, you will be unable to connect from a client (such as a PC) as two different users at once. Attempts to connect the second user will result in access denied or - similar.

    ENVIRONMENT VARIABLES

    PRINTER

    If no printer name is specified to + similar.

    ENVIRONMENT VARIABLES

    PRINTER

    If no printer name is specified to printable services, most systems will use the value of this variable (or lp if this variable is not defined) as the name of the printer to use. This - is not specific to the server, however.

    PAM INTERACTION

    Samba uses PAM for authentication (when presented with a plaintext + 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 restrictions smb.conf(5) paramater. When this is set, the following restrictions apply: -

    • Account Validation: All accesses to a +

      • 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 login at this time. This also applies to encrypted logins. -

      • Session Management: When not using share +

      • Session Management: When not using share level secuirty, users must pass PAM's session checks before access is granted. Note however, that this is bypassed in share level secuirty. Note also that some older pam configuration files may need a line added for session support. -

    VERSION

    This man page is correct for version 3 of - the Samba suite.

    DIAGNOSTICS

    Most diagnostics issued by the server are logged +

VERSION

This man page is correct for version 3 of + the Samba suite.

DIAGNOSTICS

Most diagnostics issued by the server are logged in a specified log file. The log file name is specified at compile time, but may be overridden on the command line.

The number and nature of diagnostics available depends on the debug level used by the server. If you have problems, set @@ -129,10 +129,10 @@ available in the source code to warrant describing each and every diagnostic. At this stage your best bet is still to grep the source code and inspect the conditions that gave rise to the - diagnostics you are seeing.

TDB FILES

Samba stores it's data in several TDB (Trivial Database) files, usually located in /var/lib/samba.

+ diagnostics you are seeing.

TDB FILES

Samba stores it's data in several TDB (Trivial Database) files, usually located in /var/lib/samba.

(*) information persistent across restarts (but not necessarily important to backup). -

account_policy.tdb*

NT account policy settings such as pw expiration, etc...

brlock.tdb

byte range locks

browse.dat

browse lists

connections.tdb

share connections (used to enforce max connections, etc...)

gencache.tdb

generic caching db

group_mapping.tdb*

group mapping information

locking.tdb

share modes & oplocks

login_cache.tdb*

bad pw attempts

messages.tdb

Samba messaging system

netsamlogon_cache.tdb*

cache of user net_info_3 struct from net_samlogon() request (as a domain member)

ntdrivers.tdb*

installed printer drivers

ntforms.tdb*

installed printer forms

ntprinters.tdb*

installed printer information

printing/

directory containing tdb per print queue of cached lpq output

registry.tdb

Windows registry skeleton (connect via regedit.exe)

sessionid.tdb

session information (e.g. support for 'utmp = yes')

share_info.tdb*

share acls

winbindd_cache.tdb

winbindd's cache of user lists, etc...

winbindd_idmap.tdb*

winbindd's local idmap db

wins.dat*

wins database when 'wins support = yes'

SIGNALS

Sending the smbd a SIGHUP will cause it to +

account_policy.tdb*

NT account policy settings such as pw expiration, etc...

brlock.tdb

byte range locks

browse.dat

browse lists

connections.tdb

share connections (used to enforce max connections, etc...)

gencache.tdb

generic caching db

group_mapping.tdb*

group mapping information

locking.tdb

share modes & oplocks

login_cache.tdb*

bad pw attempts

messages.tdb

Samba messaging system

netsamlogon_cache.tdb*

cache of user net_info_3 struct from net_samlogon() request (as a domain member)

ntdrivers.tdb*

installed printer drivers

ntforms.tdb*

installed printer forms

ntprinters.tdb*

installed printer information

printing/

directory containing tdb per print queue of cached lpq output

registry.tdb

Windows registry skeleton (connect via regedit.exe)

sessionid.tdb

session information (e.g. support for 'utmp = yes')

share_info.tdb*

share acls

winbindd_cache.tdb

winbindd's cache of user lists, etc...

winbindd_idmap.tdb*

winbindd's local idmap db

wins.dat*

wins database when 'wins support = yes'

SIGNALS

Sending the smbd a SIGHUP will cause it to reload its smb.conf configuration file within a short period of time.

To shut down a user's smbd process it is recommended that SIGKILL (-9) NOT @@ -147,11 +147,11 @@ smbd is in a state of waiting for an incoming SMB before issuing them. It is possible to make the signal handlers safe by un-blocking the signals before the select call and re-blocking - them after, however this would affect performance.

SEE ALSO

hosts_access(5), inetd(8), nmbd(8), smb.conf(5), smbclient(1), testparm(1), testprns(1), and the + them after, however this would affect performance.

SEE ALSO

hosts_access(5), inetd(8), nmbd(8), smb.conf(5), smbclient(1), testparm(1), testprns(1), and the Internet RFC's rfc1001.txt, rfc1002.txt. In addition the CIFS (formerly SMB) specification is available as a link from the Web page - http://samba.org/cifs/.

AUTHOR

The original Samba software and related utilities + http://samba.org/cifs/.

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 -u -r --new-file --exclude .svn --exclude CVS samba-3.3.10//docs/htmldocs/manpages/smbget.1.html samba-3.3.11//docs/htmldocs/manpages/smbget.1.html --- samba-3.3.10//docs/htmldocs/manpages/smbget.1.html 2010-01-14 11:21:15.000000000 +0100 +++ samba-3.3.11//docs/htmldocs/manpages/smbget.1.html 2010-02-22 16:53:36.000000000 +0100 @@ -1,14 +1,14 @@ -smbget

Name

smbget — wget-like utility for download files over SMB

Synopsis

smbget [-a, --guest] [-r, --resume] [-R, --recursive] [-u, --username=STRING] [-p, --password=STRING] [-w, --workgroup=STRING] [-n, --nonprompt] [-d, --debuglevel=INT] [-D, --dots] [-P, --keep-permissions] [-o, --outputfile] [-f, --rcfile] [-q, --quiet] [-v, --verbose] [-b, --blocksize] [-?, --help] [--usage] {smb://host/share/path/to/file} [smb://url2/] [...]

DESCRIPTION

This tool is part of the samba(7) suite.

smbget is a simple utility with wget-like semantics, that can download files from SMB servers. You can specify the files you would like to download on the command-line. +smbget

Name

smbget — wget-like utility for download files over SMB

Synopsis

smbget [-a, --guest] [-r, --resume] [-R, --recursive] [-u, --username=STRING] [-p, --password=STRING] [-w, --workgroup=STRING] [-n, --nonprompt] [-d, --debuglevel=INT] [-D, --dots] [-P, --keep-permissions] [-o, --outputfile] [-f, --rcfile] [-q, --quiet] [-v, --verbose] [-b, --blocksize] [-?, --help] [--usage] {smb://host/share/path/to/file} [smb://url2/] [...]

DESCRIPTION

This tool is part of the samba(7) suite.

smbget is a simple utility with wget-like semantics, that can download files from SMB servers. You can specify the files you would like to download on the command-line.

The files should be in the smb-URL standard, e.g. use smb://host/share/file for the UNC path \\\\HOST\\SHARE\\file. -

OPTIONS

-a, --guest

Work as user guest

-r, --resume

Automatically resume aborted files

-R, --recursive

Recursively download files

-u, --username=STRING

Username to use

-p, --password=STRING

Password to use

-w, --workgroup=STRING

Workgroup to use (optional)

-n, --nonprompt

Don't ask anything (non-interactive)

-d, --debuglevel=INT

Debuglevel to use

-D, --dots

Show dots as progress indication

-P, --keep-permissions

Set same permissions on local file as are set on remote file.

-o, --outputfile

Write the file that is being download to the specified file. Can not be used together with -R.

-f, --rcfile

Use specified rcfile. This will be loaded in the order it was specified - e.g. if you specify any options before this one, they might get overriden by the contents of the rcfile.

-q, --quiet

Be quiet

-v, --verbose

Be verbose

-b, --blocksize

Number of bytes to download in a block. Defaults to 64000.

-?, --help

Show help message

--usage

Display brief usage message

SMB URLS

SMB URL's should be specified in the following format:

+	

OPTIONS

-a, --guest

Work as user guest

-r, --resume

Automatically resume aborted files

-R, --recursive

Recursively download files

-u, --username=STRING

Username to use

-p, --password=STRING

Password to use

-w, --workgroup=STRING

Workgroup to use (optional)

-n, --nonprompt

Don't ask anything (non-interactive)

-d, --debuglevel=INT

Debuglevel to use

-D, --dots

Show dots as progress indication

-P, --keep-permissions

Set same permissions on local file as are set on remote file.

-o, --outputfile

Write the file that is being download to the specified file. Can not be used together with -R.

-f, --rcfile

Use specified rcfile. This will be loaded in the order it was specified - e.g. if you specify any options before this one, they might get overriden by the contents of the rcfile.

-q, --quiet

Be quiet

-v, --verbose

Be verbose

-b, --blocksize

Number of bytes to download in a block. Defaults to 64000.

-?, --help

Show help message

--usage

Display brief usage message

SMB URLS

SMB URL's should be specified in the following format:

 smb://[[[domain;]user[:password@]]server[/share[/path[/file]]]]
 
 smb:// means all the workgroups
 
 smb://name/ means, if name is a workgroup, all the servers in this workgroup, or if name is a server, all the shares on this server.
-

EXAMPLES

+

EXAMPLES

 # Recursively download 'src' directory
 smbget -R smb://rhonwyn/jelmer/src
 # Download FreeBSD ISO and enable resuming
@@ -17,10 +17,10 @@
 smbget -Rr smb://rhonwyn/isos
 # Backup my data on rhonwyn
 smbget -Rr smb://rhonwyn/
-

BUGS

Permission denied is returned in some cases where the cause of the error is unknown +

BUGS

Permission denied is returned in some cases where the cause of the error is unknown (such as an illegally formatted smb:// url or trying to get a directory without -R -turned on).

VERSION

This man page is correct for version 3 of - the Samba suite.

AUTHOR

The original Samba software and related utilities +turned on).

VERSION

This man page is correct for version 3 of + the Samba suite.

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 smbget manpage was written by Jelmer Vernooij.

diff -u -r --new-file --exclude .svn --exclude CVS samba-3.3.10//docs/htmldocs/manpages/smbgetrc.5.html samba-3.3.11//docs/htmldocs/manpages/smbgetrc.5.html --- samba-3.3.10//docs/htmldocs/manpages/smbgetrc.5.html 2010-01-14 11:21:17.000000000 +0100 +++ samba-3.3.11//docs/htmldocs/manpages/smbgetrc.5.html 2010-02-22 16:53:36.000000000 +0100 @@ -1,17 +1,17 @@ -smbgetrc

Name

smbgetrc — configuration file for smbget

Synopsis

smbgetrc

DESCRIPTION

+smbgetrc

Name

smbgetrc — configuration file for smbget

Synopsis

smbgetrc

DESCRIPTION

This manual page documents the format and options of the smbgetrc file. This is the configuration file used by the smbget(1) utility. The file contains of key-value pairs, one pair on each line. The key and value should be separated by a space.

By default, smbget reads its configuration from $HOME/.smbgetrc, though - other locations can be specified using the command-line options.

OPTIONS

+ other locations can be specified using the command-line options.

OPTIONS

The following keys can be set:

resume on|off

Whether aborted downloads should be automatically resumed.

recursive on|off

Whether directories should be downloaded recursively

username name

Username to use when logging in to the remote server. Use an empty string for anonymous access. -

password pass

Password to use when logging in.

workgroup wg

Workgroup to use when logging in

nonprompt on|off

Turns off asking for username and password. Useful for scripts.

debuglevel int

(Samba) debuglevel to run at. Useful for tracking down protocol level problems.

dots on|off

Whether a single dot should be printed for each block that has been downloaded, instead of the default progress indicator.

blocksize int

Number of bytes to put in a block.

VERSION

This man page is correct for version 3 of - the Samba suite.

SEE ALSO

smbget(1) and Samba(7). -

AUTHOR

The original Samba software and related utilities +

password pass

Password to use when logging in.

workgroup wg

Workgroup to use when logging in

nonprompt on|off

Turns off asking for username and password. Useful for scripts.

debuglevel int

(Samba) debuglevel to run at. Useful for tracking down protocol level problems.

dots on|off

Whether a single dot should be printed for each block that has been downloaded, instead of the default progress indicator.

blocksize int

Number of bytes to put in a block.

VERSION

This man page is correct for version 3 of + the Samba suite.

SEE ALSO

smbget(1) and 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.

This manual page was written by Jelmer Vernooij

diff -u -r --new-file --exclude .svn --exclude CVS samba-3.3.10//docs/htmldocs/manpages/smbpasswd.5.html samba-3.3.11//docs/htmldocs/manpages/smbpasswd.5.html --- samba-3.3.10//docs/htmldocs/manpages/smbpasswd.5.html 2010-01-14 11:21:18.000000000 +0100 +++ samba-3.3.11//docs/htmldocs/manpages/smbpasswd.5.html 2010-02-22 16:53:37.000000000 +0100 @@ -1,8 +1,8 @@ -smbpasswd

Name

smbpasswd — The Samba encrypted password file

Synopsis

smbpasswd

DESCRIPTION

This tool is part of the samba(7) suite.

smbpasswd is the Samba encrypted password file. It contains +smbpasswd

Name

smbpasswd — The Samba encrypted password file

Synopsis

smbpasswd

DESCRIPTION

This tool is part of the samba(7) suite.

smbpasswd is the Samba encrypted password file. It contains the username, Unix user id and the SMB hashed passwords of the user, as well as account flag information and the time the password was last changed. This file format has been evolving with - Samba and has had several different formats in the past.

FILE FORMAT

The format of the smbpasswd file used by Samba 2.2 + Samba and has had several different formats in the past.

FILE FORMAT

The format of the smbpasswd file used by Samba 2.2 is very similar to the familiar Unix passwd(5) file. It is an ASCII file containing one line for each user. Each field ithin each line is separated from the next by a colon. Any entry @@ -58,15 +58,15 @@ '[' and ']' characters and is always 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.

  • N - This means the +

    • U - This means + this is a "User" account, i.e. an ordinary user.

    • 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 - is disabled and no SMB/CIFS logins will be allowed for this user.

    • X - This means the password - does not expire.

    • W - This means this account + smb.conf(5) config file.

    • D - This means the account + is disabled and no SMB/CIFS logins will be allowed for this user.

    • X - This means the password + does not expire.

    • W - This means this account 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. @@ -76,10 +76,10 @@ last modified. It consists of the characters 'LCT-' (standing for "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 of - the Samba suite.

SEE ALSO

smbpasswd(8), Samba(7), and +

All other colon separated fields are ignored at this time.

VERSION

This man page is correct for version 3 of + the Samba suite.

SEE ALSO

smbpasswd(8), Samba(7), and the Internet RFC1321 for details on the MD4 algorithm. -

AUTHOR

The original Samba software and related utilities +

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 -u -r --new-file --exclude .svn --exclude CVS samba-3.3.10//docs/htmldocs/manpages/smbpasswd.8.html samba-3.3.11//docs/htmldocs/manpages/smbpasswd.8.html --- samba-3.3.10//docs/htmldocs/manpages/smbpasswd.8.html 2010-01-14 11:21:19.000000000 +0100 +++ samba-3.3.11//docs/htmldocs/manpages/smbpasswd.8.html 2010-02-22 16:53:37.000000000 +0100 @@ -1,4 +1,4 @@ -smbpasswd

Name

smbpasswd — change a user's SMB password

Synopsis

smbpasswd [-a] [-c <config file>] [-x] [-d] [-e] [-D debuglevel] [-n] [-r <remote machine>] [-R <name resolve order>] [-m] [-U username[%password]] [-h] [-s] [-w pass] [-W] [-i] [-L] [username]

DESCRIPTION

This tool is part of the samba(7) suite.

The smbpasswd program has several different +smbpasswd

Name

smbpasswd — change a user's SMB password

Synopsis

smbpasswd [-a] [-c <config file>] [-x] [-d] [-e] [-D debuglevel] [-n] [-r <remote machine>] [-R <name resolve order>] [-m] [-U username[%password]] [-h] [-s] [-w pass] [-W] [-i] [-L] [username]

DESCRIPTION

This tool is part of the samba(7) suite.

The smbpasswd program has several different functions, depending on whether it is run by the root user or not. When run as a normal user it allows the user to change the password used for their SMB sessions on any machines that store @@ -25,7 +25,7 @@ the attributes of the user in this file to be made. When run by root, smbpasswd accesses the local smbpasswd file directly, thus enabling changes to be made even if smbd is not - running.

OPTIONS

-a

+ running.

OPTIONS

-a

This option specifies that the username following should be added to the local smbpasswd file, with the new password typed (type <Enter> for the old password). This option is ignored if the username following already exists in the smbpasswd file and it is treated like a regular change password command. Note that the @@ -92,20 +92,20 @@ 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 - cause names to be resolved as follows:

  • lmhosts: Lookup an IP + 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 - any name type matches for lookup.

    • host: Do a standard host + any name type matches for lookup.

    • host: Do a standard host name to IP address resolution, using the system /etc/hosts , NIS, or DNS lookups. This method of name resolution is operating system depended for instance on IRIX or Solaris this may be controlled by the /etc/nsswitch.conf file). Note that this method is only used if the NetBIOS name type being queried is the 0x20 (server) name type, otherwise - it is ignored.

    • wins: Query a name with + it is ignored.

    • wins: Query a name with the IP address listed in the wins server parameter. If no WINS server has been specified this method - will be ignored.

    • bcast: Do a broadcast on + will be ignored.

    • bcast: Do a broadcast on each of the known local interfaces listed in the interfaces parameter. This is the least reliable of the name resolution methods as it depends on the @@ -151,7 +151,7 @@ root only options to operate on. Only root can specify this parameter as only root has the permission needed to modify attributes directly in the local smbpasswd file. -

NOTES

Since smbpasswd works in client-server +

NOTES

Since smbpasswd works in client-server mode communicating with a local smbd for a non-root user then the smbd daemon must be running for this to work. A common problem is to add a restriction to the hosts that may access the @@ -159,7 +159,7 @@ 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.

VERSION

This man page is correct for version 3 of the Samba suite.

AUTHOR

The original Samba software and related utilities + has been set up to use encrypted passwords.

VERSION

This man page is correct for version 3 of the Samba suite.

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 -u -r --new-file --exclude .svn --exclude CVS samba-3.3.10//docs/htmldocs/manpages/smbspool.8.html samba-3.3.11//docs/htmldocs/manpages/smbspool.8.html --- samba-3.3.10//docs/htmldocs/manpages/smbspool.8.html 2010-01-14 11:21:21.000000000 +0100 +++ samba-3.3.11//docs/htmldocs/manpages/smbspool.8.html 2010-02-22 16:53:37.000000000 +0100 @@ -1,29 +1,29 @@ -smbspool

Name

smbspool — send a print file to an SMB printer

Synopsis

smbspool {job} {user} {title} {copies} {options} [filename]

DESCRIPTION

This tool is part of the samba(7) suite.

smbspool is a very small print spooling program that +smbspool

Name

smbspool — send a print file to an SMB printer

Synopsis

smbspool {job} {user} {title} {copies} {options} [filename]

DESCRIPTION

This tool is part of the samba(7) suite.

smbspool is a very small print spooling program that sends a print file to an SMB printer. The command-line arguments 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 - a number of forms:

  • smb://server[:port]/printer

  • smb://workgroup/server[:port]/printer

  • smb://username:password@server[:port]/printer

  • smb://username:password@workgroup/server[:port]/printer

smbspool tries to get the URI from the environment variable + a number of forms:

  • smb://server[:port]/printer

  • smb://workgroup/server[:port]/printer

  • smb://username:password@server[:port]/printer

  • smb://username:password@workgroup/server[:port]/printer

smbspool tries to get the URI from the environment variable DEVICE_URI. If DEVICE_URI is not present, - smbspool will use argv[0] if that starts with smb:// + smbspool will use argv[0] if that starts with “smb://” or argv[1] if that is not the case.

Programs using the exec(2) functions can pass the URI in argv[0], while shell scripts must set the DEVICE_URI environment variable prior to - running smbspool.

OPTIONS

  • The job argument (argv[1]) contains the + running smbspool.

OPTIONS

  • The job argument (argv[1]) contains the job ID number and is presently not used by smbspool. -

  • The user argument (argv[2]) contains the +

  • The user argument (argv[2]) contains the print user's name and is presently not used by smbspool. -

  • The title argument (argv[3]) contains the +

  • The title argument (argv[3]) contains the job title string and is passed as the remote file name - when sending the print job.

  • The copies argument (argv[4]) contains + when sending the print job.

  • The copies argument (argv[4]) contains the number of copies to be printed of the named file. If no filename is provided then this argument is not used by - smbspool.

  • The options argument (argv[5]) contains + smbspool.

  • The options argument (argv[5]) contains the print options in a single string and is currently - not used by smbspool.

  • The filename argument (argv[6]) contains the + not used by smbspool.

  • The filename argument (argv[6]) contains the name of the file to print. If this argument is not specified - then the print file is read from the standard input.

VERSION

This man page is correct for version 3 of the Samba suite.

SEE ALSO

smbd(8) and samba(7).

AUTHOR

smbspool was written by Michael Sweet + then the print file is read from the standard input.

VERSION

This man page is correct for version 3 of the Samba suite.

SEE ALSO

smbd(8) and samba(7).

AUTHOR

smbspool was written by Michael Sweet at Easy Software Products.

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 -u -r --new-file --exclude .svn --exclude CVS samba-3.3.10//docs/htmldocs/manpages/smbstatus.1.html samba-3.3.11//docs/htmldocs/manpages/smbstatus.1.html --- samba-3.3.10//docs/htmldocs/manpages/smbstatus.1.html 2010-01-14 11:21:22.000000000 +0100 +++ samba-3.3.11//docs/htmldocs/manpages/smbstatus.1.html 2010-02-22 16:53:36.000000000 +0100 @@ -1,5 +1,5 @@ -smbstatus

Name

smbstatus — report on current Samba connections

Synopsis

smbstatus [-P] [-b] [-d <debug level>] [-v] [-L] [-B] [-p] [-S] [-s <configuration file>] [-u <username>]

DESCRIPTION

This tool is part of the samba(7) suite.

smbstatus is a very simple program to - list the current Samba connections.

OPTIONS

-P|--profile

If samba has been compiled with the +smbstatus

Name

smbstatus — report on current Samba connections

Synopsis

smbstatus [-P] [-b] [-d <debug level>] [-v] [-L] [-B] [-p] [-S] [-s <configuration file>] [-u <username>]

DESCRIPTION

This tool is part of the samba(7) suite.

smbstatus is a very simple program to + list the current Samba connections.

OPTIONS

-P|--profile

If samba has been compiled with the profiling option, print only the contents of the profiling shared memory area.

-b|--brief

gives brief output.

-d|--debuglevel=level

level is an integer from 0 to 10. The default value if this parameter is @@ -28,8 +28,8 @@

-v|--verbose

gives verbose output.

-L|--locks

causes smbstatus to only list locks.

-B|--byterange

causes smbstatus to include byte range locks.

-p|--processes

print a list of smbd(8) processes and exit. Useful for scripting.

-S|--shares

causes smbstatus to only list shares.

-h|--help

Print a summary of command line options. -

-u|--user=<username>

selects information relevant to username only.

VERSION

This man page is correct for version 3 of - the Samba suite.

SEE ALSO

smbd(8) and smb.conf(5).

AUTHOR

The original Samba software and related utilities +

-u|--user=<username>

selects information relevant to username only.

VERSION

This man page is correct for version 3 of + the Samba suite.

SEE ALSO

smbd(8) and smb.conf(5).

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 -u -r --new-file --exclude .svn --exclude CVS samba-3.3.10//docs/htmldocs/manpages/smbtar.1.html samba-3.3.11//docs/htmldocs/manpages/smbtar.1.html --- samba-3.3.10//docs/htmldocs/manpages/smbtar.1.html 2010-01-14 11:21:23.000000000 +0100 +++ samba-3.3.11//docs/htmldocs/manpages/smbtar.1.html 2010-02-22 16:53:37.000000000 +0100 @@ -1,6 +1,6 @@ -smbtar

Name

smbtar — shell script for backing up SMB/CIFS shares - 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 +smbtar

Name

smbtar — shell script for backing up SMB/CIFS shares + 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 create or restore.

-d directory

Change to initial directory @@ -17,14 +17,14 @@ up if they have the archive bit set. The archive bit is reset after each file is read.

-r

Restore. Files are restored to the share from the tar file.

-l log level

Log (debug) level. Corresponds to the - -d flag of smbclient(1).

ENVIRONMENT VARIABLES

The $TAPE variable specifies the + -d flag of smbclient(1).

ENVIRONMENT VARIABLES

The $TAPE variable specifies the default tape device to write to. May be overridden - with the -t option.

BUGS

The smbtar script has different - options from ordinary tar and from smbclient's tar command.

CAVEATS

Sites that are more careful about security may not like + with the -t option.

BUGS

The smbtar script has different + options from ordinary tar and from smbclient's tar command.

CAVEATS

Sites that are more careful about security may not like the way the script handles PC passwords. Backup and restore work on entire shares; should work on file lists. smbtar works best - with GNU tar and may not work well with other versions.

DIAGNOSTICS

See the DIAGNOSTICS section for the smbclient(1) command.

VERSION

This man page is correct for version 3 of - the Samba suite.

AUTHOR

The original Samba software and related utilities + with GNU tar and may not work well with other versions.

DIAGNOSTICS

See the DIAGNOSTICS section for the smbclient(1) command.

VERSION

This man page is correct for version 3 of + the Samba suite.

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.

Ricky Poulten diff -u -r --new-file --exclude .svn --exclude CVS samba-3.3.10//docs/htmldocs/manpages/smbtree.1.html samba-3.3.11//docs/htmldocs/manpages/smbtree.1.html --- samba-3.3.10//docs/htmldocs/manpages/smbtree.1.html 2010-01-14 11:21:24.000000000 +0100 +++ samba-3.3.11//docs/htmldocs/manpages/smbtree.1.html 2010-02-22 16:53:37.000000000 +0100 @@ -1,10 +1,10 @@ -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 +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 on Windows computers. It prints a tree with all the known domains, the servers in those domains and the shares on the servers. -

OPTIONS

-b

Query network nodes by sending requests +

OPTIONS

-b

Query network nodes by sending requests as broadcasts instead of querying the local master browser.

-D

Only print a list of all the domains known on broadcast or by the @@ -44,6 +44,8 @@ be silently ingnored and no password will be used.

-k|--kerberos

Try to authenticate with kerberos. Only useful in an Active Directory environment. +

-C|--use-ccache

+Try to use the credentials cached by winbind.

-A|--authentication-file=filename

This option allows you to specify a file from which to read the username and password used in the connection. The format of the file is @@ -67,8 +69,8 @@ via the ps command. To be safe always allow rpcclient to prompt for a password and type it in directly.

-h|--help

Print a summary of command line options. -

VERSION

This man page is correct for version 3 of the Samba - suite.

AUTHOR

The original Samba software and related utilities +

VERSION

This man page is correct for version 3 of the Samba + suite.

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 smbtree man page was written by Jelmer Vernooij.

diff -u -r --new-file --exclude .svn --exclude CVS samba-3.3.10//docs/htmldocs/manpages/swat.8.html samba-3.3.11//docs/htmldocs/manpages/swat.8.html --- samba-3.3.10//docs/htmldocs/manpages/swat.8.html 2010-01-14 11:21:26.000000000 +0100 +++ samba-3.3.11//docs/htmldocs/manpages/swat.8.html 2010-02-22 16:53:37.000000000 +0100 @@ -1,8 +1,8 @@ -swat

Name

swat — Samba Web Administration Tool

Synopsis

swat [-s <smb config file>] [-a] [-P]

DESCRIPTION

This tool is part of the samba(7) suite.

swat allows a Samba administrator to +swat

Name

swat — Samba Web Administration Tool

Synopsis

swat [-s <smb config file>] [-a] [-P]

DESCRIPTION

This tool is part of the samba(7) suite.

swat allows a Samba administrator to configure the complex smb.conf(5) file via a Web browser. In addition, a swat configuration page has help links to all the configurable options in the smb.conf file allowing an - administrator to easily look up the effects of any change.

swat is run from inetd

OPTIONS

-s smb configuration file

The default configuration file path is + administrator to easily look up the effects of any change.

swat is run from inetd

OPTIONS

-s smb configuration file

The default configuration file path is determined at compile time. The file specified contains the configuration details required by the smbd(8) server. This is the file that swat will modify. @@ -41,14 +41,14 @@ ".progname" will be appended (e.g. log.smbclient, log.smbd, etc...). 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 +

INSTALLATION

Swat is included as binary package with most distributions. The package manager in this case takes care of the installation and configuration. This section is only for those who have compiled swat from scratch.

After you compile SWAT you need to run make install to install the swat binary and the various help files and images. A default install would put - these in:

  • /usr/local/samba/sbin/swat

  • /usr/local/samba/swat/images/*

  • /usr/local/samba/swat/help/*

Inetd Installation

You need to edit your /etc/inetd.conf + these in:

  • /usr/local/samba/sbin/swat

  • /usr/local/samba/swat/images/*

  • /usr/local/samba/swat/help/*

Inetd Installation

You need to edit your /etc/inetd.conf and /etc/services to enable SWAT to be launched via inetd.

In /etc/services you need to add a line like this:

swat 901/tcp

Note for NIS/YP and LDAP users - you may need to rebuild the @@ -62,21 +62,21 @@ /usr/local/samba/sbin/swat swat

Once you have edited /etc/services 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 + 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 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 + in the clear over the wire.

FILES

/etc/inetd.conf

This file must contain suitable startup information for the meta-daemon.

/etc/services

This file must contain a mapping of service name (e.g., swat) to service port (e.g., 901) and protocol type (e.g., tcp).

/usr/local/samba/lib/smb.conf

This is the default location of the smb.conf(5) server configuration file that swat edits. Other common places that systems install this file are /usr/samba/lib/smb.conf and /etc/smb.conf . This file describes all the services the server - is to make available to clients.

WARNINGS

swat will rewrite your smb.conf(5) file. It will rearrange the entries and delete all + is to make available to clients.

WARNINGS

swat will rewrite your smb.conf(5) file. It will rearrange the entries and delete all comments, include= and copy= options. If you have a carefully crafted - smb.conf then back it up or don't use swat!

VERSION

This man page is correct for version 3 of the Samba suite.

SEE ALSO

inetd(5), smbd(8), smb.conf(5)

AUTHOR

The original Samba software and related utilities + smb.conf then back it up or don't use swat!

VERSION

This man page is correct for version 3 of the Samba suite.

SEE ALSO

inetd(5), smbd(8), smb.conf(5)

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 -u -r --new-file --exclude .svn --exclude CVS samba-3.3.10//docs/htmldocs/manpages/tdbbackup.8.html samba-3.3.11//docs/htmldocs/manpages/tdbbackup.8.html --- samba-3.3.10//docs/htmldocs/manpages/tdbbackup.8.html 2010-01-14 11:21:27.000000000 +0100 +++ samba-3.3.11//docs/htmldocs/manpages/tdbbackup.8.html 2010-02-22 16:53:37.000000000 +0100 @@ -1,8 +1,8 @@ -tdbbackup

Name

tdbbackup — tool for backing up and for validating the integrity of samba .tdb files

Synopsis

tdbbackup [-s suffix] [-v] [-h]

DESCRIPTION

This tool is part of the samba(1) suite.

tdbbackup is a tool that may be used to backup samba .tdb +tdbbackup

Name

tdbbackup — tool for backing up and for validating the integrity of samba .tdb files

Synopsis

tdbbackup [-s suffix] [-v] [-h]

DESCRIPTION

This tool is part of the samba(1) suite.

tdbbackup is a tool that may be used to backup samba .tdb files. This tool may also be used to verify the integrity of the .tdb files prior to samba startup or during normal operation. If it finds file damage and it finds a prior backup the backup file will be restored. -

OPTIONS

-h

+

OPTIONS

-h

Get help information.

-s suffix

The -s option allows the adminisistrator to specify a file @@ -11,7 +11,7 @@

-v

The -v will check the database for damages (currupt data) which if detected causes the backup to be restored. -

COMMANDS

GENERAL INFORMATION

+

COMMANDS

GENERAL INFORMATION

The tdbbackup utility can safely be run at any time. It was designed so that it can be used at any time to validate the integrity of tdb files, even during Samba operation. Typical usage for the command will be: @@ -20,16 +20,16 @@

tdbbackup -v [-s suffix] *.tdb

Samba .tdb files are stored in various locations, be sure to run backup all .tdb file on the system. Important files includes: -

  • +

    • secrets.tdb - usual location is in the /usr/local/samba/private directory, or on some systems in /etc/samba. -

    • +

    • passdb.tdb - usual location is in the /usr/local/samba/private directory, or on some systems in /etc/samba. -

    • +

    • *.tdb located in the /usr/local/samba/var directory or on some systems in the /var/cache or /var/lib/samba directories. -

VERSION

This man page is correct for version 3 of the Samba suite.

AUTHOR

+

VERSION

This man page is correct for version 3 of the Samba suite.

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. diff -u -r --new-file --exclude .svn --exclude CVS samba-3.3.10//docs/htmldocs/manpages/tdbdump.8.html samba-3.3.11//docs/htmldocs/manpages/tdbdump.8.html --- samba-3.3.10//docs/htmldocs/manpages/tdbdump.8.html 2010-01-14 11:21:28.000000000 +0100 +++ samba-3.3.11//docs/htmldocs/manpages/tdbdump.8.html 2010-02-22 16:53:37.000000000 +0100 @@ -1,9 +1,9 @@ -tdbdump

Name

tdbdump — tool for printing the contents of a TDB file

Synopsis

tdbdump {filename}

DESCRIPTION

This tool is part of the samba(1) suite.

tdbdump is a very simple utility that 'dumps' the +tdbdump

Name

tdbdump — tool for printing the contents of a TDB file

Synopsis

tdbdump {filename}

DESCRIPTION

This tool is part of the samba(1) suite.

tdbdump is a very simple utility that 'dumps' the contents of a TDB (Trivial DataBase) file to standard output in a human-readable format.

This tool can be used when debugging problems with TDB files. It is intended for those who are somewhat familiar with Samba internals. -

VERSION

This man page is correct for version 3 of the Samba suite.

AUTHOR

+

VERSION

This man page is correct for version 3 of the Samba suite.

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. diff -u -r --new-file --exclude .svn --exclude CVS samba-3.3.10//docs/htmldocs/manpages/tdbtool.8.html samba-3.3.11//docs/htmldocs/manpages/tdbtool.8.html --- samba-3.3.10//docs/htmldocs/manpages/tdbtool.8.html 2010-01-14 11:21:30.000000000 +0100 +++ samba-3.3.11//docs/htmldocs/manpages/tdbtool.8.html 2010-02-22 16:53:37.000000000 +0100 @@ -1,12 +1,12 @@ -tdbtool

Name

tdbtool — manipulate the contents TDB files

Synopsis

tdbtool

tdbtool +tdbtool

Name

tdbtool — manipulate the contents TDB files

Synopsis

tdbtool

tdbtool TDBFILE [ COMMANDS - ...]

DESCRIPTION

This tool is part of the + ...]

DESCRIPTION

This tool is part of the samba(1) suite.

tdbtool a tool for displaying and altering the contents of Samba TDB (Trivial DataBase) files. Each of the commands listed below can be entered interactively or - provided on the command line.

COMMANDS

create + provided on the command line.

COMMANDS

create TDBFILE

Create a new database named TDBFILE.

open @@ -59,10 +59,10 @@

quit

Exit tdbtool. -

CAVEATS

The contents of the Samba TDB files are private +

CAVEATS

The contents of the Samba TDB files are private to the implementation and should not be altered with tdbtool. -

VERSION

This man page is correct for version 3.0.25 of the Samba suite.

AUTHOR

The original Samba software and related utilities were +

VERSION

This man page is correct for version 3.0.25 of the Samba suite.

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.

diff -u -r --new-file --exclude .svn --exclude CVS samba-3.3.10//docs/htmldocs/manpages/testparm.1.html samba-3.3.11//docs/htmldocs/manpages/testparm.1.html --- samba-3.3.10//docs/htmldocs/manpages/testparm.1.html 2010-01-14 11:21:31.000000000 +0100 +++ samba-3.3.11//docs/htmldocs/manpages/testparm.1.html 2010-02-22 16:53:37.000000000 +0100 @@ -1,5 +1,5 @@ -testparm

Name

testparm — check an smb.conf configuration file for - internal correctness

Synopsis

testparm [-s] [-h] [-v] [-L <servername>] [-t <encoding>] {config filename} [hostname hostIP]

DESCRIPTION

This tool is part of the samba(7) suite.

testparm is a very simple test program +testparm

Name

testparm — check an smb.conf configuration file for + internal correctness

Synopsis

testparm [-s] [-h] [-v] [-L <servername>] [-t <encoding>] {config filename} [hostname hostIP]

DESCRIPTION

This tool is part of the samba(7) suite.

testparm is a very simple test program to check an smbd(8) configuration file for internal correctness. If this program reports no problems, you can use the configuration file with confidence that smbd @@ -11,7 +11,7 @@ has access to each service.

If testparm finds an error in the smb.conf file it returns an exit code of 1 to the calling program, else it returns an exit code of 0. This allows shell scripts - to test the output from testparm.

OPTIONS

-s

Without this option, testparm + to test the output from testparm.

OPTIONS

-s

Without this option, testparm will prompt for a carriage return after printing the service names and before dumping the service definitions.

-h|--help

Print a summary of command line options.

-V|--version

Prints the program version number. @@ -41,14 +41,14 @@ this parameter is supplied, the hostIP parameter must also be supplied.

hostIP

This is the IP address of the host specified in the previous parameter. This address must be supplied - if the hostname parameter is supplied.

FILES

smb.conf(5)

This is usually the name of the configuration + if the hostname parameter is supplied.

FILES

smb.conf(5)

This is usually the name of the configuration file used by smbd(8). -

DIAGNOSTICS

The program will issue a message saying whether the +

DIAGNOSTICS

The program will issue a message saying whether the configuration file loaded OK or not. This message may be preceded by errors and warnings if the file did not load. If the file was loaded OK, the program then dumps all known service details - to stdout.

VERSION

This man page is correct for version 3 of - the Samba suite.

AUTHOR

The original Samba software and related utilities + to stdout.

VERSION

This man page is correct for version 3 of + the Samba suite.

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 -u -r --new-file --exclude .svn --exclude CVS samba-3.3.10//docs/htmldocs/manpages/umount.cifs.8.html samba-3.3.11//docs/htmldocs/manpages/umount.cifs.8.html --- samba-3.3.10//docs/htmldocs/manpages/umount.cifs.8.html 2010-01-14 11:21:32.000000000 +0100 +++ samba-3.3.11//docs/htmldocs/manpages/umount.cifs.8.html 2010-02-22 16:53:37.000000000 +0100 @@ -1,4 +1,4 @@ -umount.cifs

Name

umount.cifs — for normal, non-root users, to unmount their own Common Internet File System (CIFS) mounts

Synopsis

umount.cifs {mount-point} [-nVvhfle]

DESCRIPTION

This tool is part of the samba(7) suite.

umount.cifs unmounts a Linux CIFS filesystem. It can be invoked +umount.cifs

Name

umount.cifs — for normal, non-root users, to unmount their own Common Internet File System (CIFS) mounts

Synopsis

umount.cifs {mount-point} [-nVvhfle]

DESCRIPTION

This tool is part of the samba(7) suite.

umount.cifs unmounts a Linux CIFS filesystem. It can be invoked indirectly by the umount(8) command when umount.cifs is in /sbin directory, unless you specify the "-i" option to umount. Specifying -i to umount avoids execution of umount helpers such as umount.cifs. The umount.cifs command only works in Linux, and the kernel must @@ -11,24 +11,24 @@ It is possible to set the mode for umount.cifs to setuid root (or equivalently update the /etc/permissions file) to allow non-root users to umount shares to directories for which they have write permission. The umount.cifs utility is typically not needed if unmounts need only be performed by root users, or if user mounts and unmounts -can rely on specifying explicit entries in /etc/fstab See

fstab(5)

OPTIONS

--verbose

print additional debugging information

--no-mtab

Do not update the mtab even if unmount completes successfully (/proc/mounts will still display the correct information)

NOTES

This command is normally intended to be installed setuid (since root users can already run unmount). An alternative to using umount.cifs is to add specfic entries for the user mounts that you wish a particular user or users to mount and unmount to /etc/fstab

CONFIGURATION

+can rely on specifying explicit entries in /etc/fstab See

fstab(5)

OPTIONS

--verbose

print additional debugging information

--no-mtab

Do not update the mtab even if unmount completes successfully (/proc/mounts will still display the correct information)

NOTES

This command is normally intended to be installed setuid (since root users can already run unmount). An alternative to using umount.cifs is to add specfic entries for the user mounts that you wish a particular user or users to mount and unmount to /etc/fstab

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

At this time umount.cifs does not lock the mount table using the same lock as the umount utility does, so do not attempt to do multiple unmounts from different processes (and in particular unmounts of a cifs mount and another type of filesystem mount at the same time). +

BUGS

At this time umount.cifs does not lock the mount table using the same lock as the umount utility does, so do not attempt to do multiple unmounts from different processes (and in particular unmounts of a cifs mount and another type of filesystem mount at the same time).

If the same mount point is mounted multiple times by cifs, umount.cifs will remove all of the matching entries from the mount table (although umount.cifs will actually only unmount the last one), rather than only removing the last matching entry in /etc/mtab. The pseudofile /proc/mounts will display correct information though, and the lack of an entry in /etc/mtab does not prevent subsequent unmounts.

Note that the typical response to a bug report is a 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: umount.cifs (try umount.cifs -V), kernel (see /proc/version) and server type you are trying to contact. -

VERSION

This man page is correct for version 1.34 of - the cifs vfs filesystem (roughly Linux kernel 2.6.12).

SEE ALSO

+

VERSION

This man page is correct for version 1.34 of + the cifs vfs filesystem (roughly Linux kernel 2.6.12).

SEE ALSO

Documentation/filesystems/cifs.txt and fs/cifs/README in the linux kernel source tree may contain additional options and information. -

mount.cifs(8)

AUTHOR

Steve French

The syntax was loosely based on the umount utility and the manpage was loosely based on that of mount.cifs.8. The man page was created by Steve French

The maintainer of the Linux cifs vfs and the userspace +

mount.cifs(8)

AUTHOR

Steve French

The syntax was loosely based on the umount utility and the manpage was loosely based on that of mount.cifs.8. The man page was created by Steve French

The maintainer of the Linux cifs vfs and the userspace tool umount.cifs is Steve French. The Linux CIFS Mailing list is the preferred place to ask questions regarding these programs. diff -u -r --new-file --exclude .svn --exclude CVS samba-3.3.10//docs/htmldocs/manpages/vfs_acl_tdb.8.html samba-3.3.11//docs/htmldocs/manpages/vfs_acl_tdb.8.html --- samba-3.3.10//docs/htmldocs/manpages/vfs_acl_tdb.8.html 2010-01-14 11:21:34.000000000 +0100 +++ samba-3.3.11//docs/htmldocs/manpages/vfs_acl_tdb.8.html 2010-02-22 16:53:36.000000000 +0100 @@ -1,4 +1,4 @@ -vfs_acl_tdb

Name

vfs_acl_tdb — Save NTFS-ACLs in a tdb file

Synopsis

vfs objects = acl_tdb

DESCRIPTION

This VFS module is part of the +vfs_acl_tdb

Name

vfs_acl_tdb — Save NTFS-ACLs in a tdb file

Synopsis

vfs objects = acl_tdb

DESCRIPTION

This VFS module is part of the samba(7) suite.

The vfs_acl_tdb VFS module stores NTFS Access Control Lists (ACLs) in a tdb file. This enables the full mapping of Windows ACLs on Samba @@ -8,9 +8,9 @@ $LOCKDIR/file_ntacls.tdb.

Please note that this module is experimental! -

This module is stackable.

OPTIONS

+

This module is stackable.

OPTIONS

There are no options for vfs_acl_tdb. -

AUTHOR

The original Samba software and related utilities +

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.

diff -u -r --new-file --exclude .svn --exclude CVS samba-3.3.10//docs/htmldocs/manpages/vfs_acl_xattr.8.html samba-3.3.11//docs/htmldocs/manpages/vfs_acl_xattr.8.html --- samba-3.3.10//docs/htmldocs/manpages/vfs_acl_xattr.8.html 2010-01-14 11:21:35.000000000 +0100 +++ samba-3.3.11//docs/htmldocs/manpages/vfs_acl_xattr.8.html 2010-02-22 16:53:37.000000000 +0100 @@ -1,4 +1,4 @@ -vfs_acl_xattr

Name

vfs_acl_xattr — Save NTFS-ACLs in Extended Attributes (EAs)

Synopsis

vfs objects = acl_xattr

DESCRIPTION

This VFS module is part of the +vfs_acl_xattr

Name

vfs_acl_xattr — Save NTFS-ACLs in Extended Attributes (EAs)

Synopsis

vfs objects = acl_xattr

DESCRIPTION

This VFS module is part of the samba(7) suite.

The vfs_acl_xattr VFS module stores NTFS Access Control Lists (ACLs) in Extended Attributes (EAs). This enables the full mapping of Windows ACLs on Samba @@ -12,9 +12,9 @@ ).

Please note that this module is experimental! -

This module is stackable.

OPTIONS

+

This module is stackable.

OPTIONS

There are no options for vfs_acl_xattr. -

AUTHOR

The original Samba software and related utilities +

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.

diff -u -r --new-file --exclude .svn --exclude CVS samba-3.3.10//docs/htmldocs/manpages/vfs_audit.8.html samba-3.3.11//docs/htmldocs/manpages/vfs_audit.8.html --- samba-3.3.10//docs/htmldocs/manpages/vfs_audit.8.html 2010-01-14 11:21:36.000000000 +0100 +++ samba-3.3.11//docs/htmldocs/manpages/vfs_audit.8.html 2010-02-22 16:53:37.000000000 +0100 @@ -1,19 +1,19 @@ -vfs_audit

Name

vfs_audit — record selected Samba VFS operations in the system log

Synopsis

vfs objects = audit

DESCRIPTION

This VFS module is part of the +vfs_audit

Name

vfs_audit — record selected Samba VFS operations in the system log

Synopsis

vfs objects = audit

DESCRIPTION

This VFS module is part of the samba(7) suite.

The vfs_audit VFS module records selected client operations to the system log using - syslog(3).

The following Samba VFS operations are recorded:

connect
disconnect
opendir
mkdir
rmdir
open
close
rename
unlink
chmod
fchmod
chmod_acl
fchmod_acl

This module is stackable.

OPTIONS

audit:facility = FACILITY

Log messages to the named + syslog(3).

The following Samba VFS operations are recorded:

connect
disconnect
opendir
mkdir
rmdir
open
close
rename
unlink
chmod
fchmod
chmod_acl
fchmod_acl

This module is stackable.

OPTIONS

audit:facility = FACILITY

Log messages to the named syslog(3) facility.

audit:priority = PRIORITY

Log messages with the named syslog(3) priority. -

EXAMPLES

Log operations on all shares using the LOCAL1 facility +

EXAMPLES

Log operations on all shares using the LOCAL1 facility and NOTICE priority:

         [global]
 	vfs objects = audit
 	audit:facility = LOCAL1
 	audit:priority = NOTICE
-

VERSION

This man page is correct for version 3.0.25 of the Samba suite. -

AUTHOR

The original Samba software and related utilities +

VERSION

This man page is correct for version 3.0.25 of the Samba suite. +

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.

diff -u -r --new-file --exclude .svn --exclude CVS samba-3.3.10//docs/htmldocs/manpages/vfs_cacheprime.8.html samba-3.3.11//docs/htmldocs/manpages/vfs_cacheprime.8.html --- samba-3.3.10//docs/htmldocs/manpages/vfs_cacheprime.8.html 2010-01-14 11:21:37.000000000 +0100 +++ samba-3.3.11//docs/htmldocs/manpages/vfs_cacheprime.8.html 2010-02-22 16:53:37.000000000 +0100 @@ -1,4 +1,4 @@ -vfs_cacheprime

Name

vfs_cacheprime — prime the kernel file data cache

Synopsis

vfs objects = cacheprime

DESCRIPTION

This VFS module is part of the +vfs_cacheprime

Name

vfs_cacheprime — prime the kernel file data cache

Synopsis

vfs objects = cacheprime

DESCRIPTION

This VFS module is part of the samba(7) suite.

The vfs_cacheprime VFS module reads chunks of file data near the range requested by clients in order to make sure the data is present in the kernel file data cache at @@ -7,20 +7,20 @@ cacheprime:rsize option. All disk read operations are aligned on boundaries that are a multiple of this size. Each range of the file data is primed at most once during the time the client - has the file open.

This module is stackable.

OPTIONS

cacheprime:rsize = BYTES

The number of bytes with which to prime - the kernel data cache.

The following suffixes may be applied to BYTES:

  • K - BYTES is a number of kilobytes

  • M - BYTES is a number of megabytes

  • G - BYTES is a number of gigabytes

EXAMPLES

For a hypothetical disk array, it is necessary to ensure + has the file open.

This module is stackable.

OPTIONS

cacheprime:rsize = BYTES

The number of bytes with which to prime + the kernel data cache.

The following suffixes may be applied to BYTES:

  • K - BYTES is a number of kilobytes

  • M - BYTES is a number of megabytes

  • G - BYTES is a number of gigabytes

EXAMPLES

For a hypothetical disk array, it is necessary to ensure that all read operations are of size 1 megabyte (1048576 bytes), and aligned on 1 megabyte boundaries:

 	[hypothetical]
 	vfs objects = cacheprime
 	cacheprime:rsize = 1M
-

CAVEATS

cacheprime is not a a substitute for +

CAVEATS

cacheprime is not a a substitute for a general-purpose readahead mechanism. It is intended for use only in very specific environments where disk operations must be aligned and sized to known values (as much as that is possible). -

VERSION

This man page is correct for version 3.0.25 of the Samba suite. -

AUTHOR

The original Samba software and related utilities +

VERSION

This man page is correct for version 3.0.25 of the Samba suite. +

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.

diff -u -r --new-file --exclude .svn --exclude CVS samba-3.3.10//docs/htmldocs/manpages/vfs_cap.8.html samba-3.3.11//docs/htmldocs/manpages/vfs_cap.8.html --- samba-3.3.10//docs/htmldocs/manpages/vfs_cap.8.html 2010-01-14 11:21:39.000000000 +0100 +++ samba-3.3.11//docs/htmldocs/manpages/vfs_cap.8.html 2010-02-22 16:53:37.000000000 +0100 @@ -1,17 +1,17 @@ -vfs_cap

Name

vfs_cap — CAP encode filenames

Synopsis

vfs objects = cap

DESCRIPTION

This VFS module is part of the +vfs_cap

Name

vfs_cap — CAP encode filenames

Synopsis

vfs objects = cap

DESCRIPTION

This VFS module is part of the samba(7) suite.

CAP (Columbia Appletalk Protocol) encoding is a technique for representing non-ASCII filenames in ASCII. The vfs_cap VFS module translates filenames to and from CAP format, allowing users to name files in their native encoding.

CAP encoding is most commonly - used in Japanese language environments.

This module is stackable.

EXAMPLES

On a system using GNU libiconv, use CAP encoding to support + used in Japanese language environments.

This module is stackable.

EXAMPLES

On a system using GNU libiconv, use CAP encoding to support users in the Shift_JIS locale:

         [global]
 	dos charset = CP932
 	dos charset = CP932
 	vfs objects = cap
-

VERSION

This man page is correct for version 3.0.25 of the Samba suite. -

AUTHOR

The original Samba software and related utilities +

VERSION

This man page is correct for version 3.0.25 of the Samba suite. +

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.

diff -u -r --new-file --exclude .svn --exclude CVS samba-3.3.10//docs/htmldocs/manpages/vfs_catia.8.html samba-3.3.11//docs/htmldocs/manpages/vfs_catia.8.html --- samba-3.3.10//docs/htmldocs/manpages/vfs_catia.8.html 2010-01-14 11:21:40.000000000 +0100 +++ samba-3.3.11//docs/htmldocs/manpages/vfs_catia.8.html 2010-02-22 16:53:37.000000000 +0100 @@ -1,14 +1,14 @@ -vfs_catia

Name

vfs_catia — translate illegal characters in Catia filenames

Synopsis

vfs objects = catia

DESCRIPTION

This VFS module is part of the +vfs_catia

Name

vfs_catia — translate illegal characters in Catia filenames

Synopsis

vfs objects = catia

DESCRIPTION

This VFS module is part of the samba(7) suite.

The Catia CAD package commonly creates filenames that use characters that are illegal in CIFS filenames. The vfs_catia VFS module implements a fixed character mapping so that these files can be shared with CIFS clients. -

This module is stackable.

EXAMPLES

Map Catia filenames on the [CAD] share:

+	

This module is stackable.

EXAMPLES

Map Catia filenames on the [CAD] share:

         [CAD]
 	path = /data/cad
 	vfs objects = catia
-

VERSION

This man page is correct for version 3.0.25 of the Samba suite. -

AUTHOR

The original Samba software and related utilities +

VERSION

This man page is correct for version 3.0.25 of the Samba suite. +

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.

diff -u -r --new-file --exclude .svn --exclude CVS samba-3.3.10//docs/htmldocs/manpages/vfs_commit.8.html samba-3.3.11//docs/htmldocs/manpages/vfs_commit.8.html --- samba-3.3.10//docs/htmldocs/manpages/vfs_commit.8.html 2010-01-14 11:21:41.000000000 +0100 +++ samba-3.3.11//docs/htmldocs/manpages/vfs_commit.8.html 2010-02-22 16:53:37.000000000 +0100 @@ -1,4 +1,4 @@ -vfs_commit

Name

vfs_commit — flush dirty data at specified intervals

Synopsis

vfs objects = commit

DESCRIPTION

This VFS module is part of the +vfs_commit

Name

vfs_commit — flush dirty data at specified intervals

Synopsis

vfs objects = commit

DESCRIPTION

This VFS module is part of the samba(7) suite.

The vfs_commit VFS module keeps track of the amount of data written to a file and synchronizes it to disk when a specified amount accumulates. @@ -7,18 +7,18 @@ impact of unexpected power loss can be minimized by a small commit:dthresh value. Secondly, write performance can be improved on some systems by flushing file data early and at - regular intervals.

This module is stackable.

OPTIONS

commit:dthresh = BYTES

Synchronize file data each time the specified + regular intervals.

This module is stackable.

OPTIONS

commit:dthresh = BYTES

Synchronize file data each time the specified number of bytes has been written. -

The following suffixes may be applied to BYTES:

  • K - BYTES is a number of kilobytes

  • M - BYTES is a number of megabytes

  • G - BYTES is a number of gigabytes

EXAMPLES

Synchronize the file data on the [precious] share after +

The following suffixes may be applied to BYTES:

  • K - BYTES is a number of kilobytes

  • M - BYTES is a number of megabytes

  • G - BYTES is a number of gigabytes

EXAMPLES

Synchronize the file data on the [precious] share after every 512 kilobytes (524288 bytes) of data is written:

         [precious]
 	path = /data/precious
 	vfs objects = commit
 	commit:dthresh = 512K
-

CAVEATS

On some systems, the data synchronization performed by +

CAVEATS

On some systems, the data synchronization performed by commit may reduce performance. -

VERSION

This man page is correct for version 3.0.25 of the Samba suite. -

AUTHOR

The original Samba software and related utilities +

VERSION

This man page is correct for version 3.0.25 of the Samba suite. +

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.

diff -u -r --new-file --exclude .svn --exclude CVS samba-3.3.10//docs/htmldocs/manpages/vfs_default_quota.8.html samba-3.3.11//docs/htmldocs/manpages/vfs_default_quota.8.html --- samba-3.3.10//docs/htmldocs/manpages/vfs_default_quota.8.html 2010-01-14 11:21:42.000000000 +0100 +++ samba-3.3.11//docs/htmldocs/manpages/vfs_default_quota.8.html 2010-02-22 16:53:37.000000000 +0100 @@ -1,4 +1,4 @@ -vfs_default_quota

Name

vfs_default_quota — store default quota records for Windows clients

Synopsis

vfs objects = default_quota

DESCRIPTION

This VFS module is part of the +vfs_default_quota

Name

vfs_default_quota — store default quota records for Windows clients

Synopsis

vfs objects = default_quota

DESCRIPTION

This VFS module is part of the samba(7) suite.

Many common quota implementations only store quotas for users and groups, but do not store a default quota. The @@ -9,7 +9,7 @@ refuses to update them. vfs_default_quota maps the default quota to the quota record of a user. By default the root user is taken because quota limits for root are typically - not enforced.

This module is stackable.

OPTIONS

default_quota:uid = UID

UID specifies the user ID of the quota record where the + not enforced.

This module is stackable.

OPTIONS

default_quota:uid = UID

UID specifies the user ID of the quota record where the default user quota values are stored.

default_quota:gid = GID

GID specifies the group ID of the quota record where the default group quota values are stored. @@ -21,15 +21,15 @@ quota record is storing the default group quota will be reported as having a quota of NO_LIMIT. Otherwise, the stored values will be reported. -

EXAMPLES

Store the default quota record in the quota record for +

EXAMPLES

Store the default quota record in the quota record for the user with ID 65535 and report that user as having no quota limits:

         [global]
 	vfs objects = default_quota
 	default_quota:uid = 65535
 	default_quota:uid nolimit = yes
-

VERSION

This man page is correct for version 3.0.25 of the Samba suite. -

AUTHOR

The original Samba software and related utilities +

VERSION

This man page is correct for version 3.0.25 of the Samba suite. +

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.

diff -u -r --new-file --exclude .svn --exclude CVS samba-3.3.10//docs/htmldocs/manpages/vfs_dirsort.8.html samba-3.3.11//docs/htmldocs/manpages/vfs_dirsort.8.html --- samba-3.3.10//docs/htmldocs/manpages/vfs_dirsort.8.html 2010-01-14 11:21:43.000000000 +0100 +++ samba-3.3.11//docs/htmldocs/manpages/vfs_dirsort.8.html 2010-02-22 16:53:37.000000000 +0100 @@ -1,11 +1,11 @@ -vfs_dirsort

Name

vfs_dirsort — Sort directory contents

Synopsis

vfs objects = dirsort

DESCRIPTION

This VFS module is part of the +vfs_dirsort

Name

vfs_dirsort — Sort directory contents

Synopsis

vfs objects = dirsort

DESCRIPTION

This VFS module is part of the samba(7) suite.

The vfs_dirsort module sorts directory entries alphabetically before sending them to the client.

Please be aware that adding this module might have negative - performance implications for large directories.

EXAMPLES

Sort directories for all shares:

+	performance implications for large directories.

EXAMPLES

Sort directories for all shares:

         [global]
 	vfs objects = dirsort
-

VERSION

This man page is correct for version 3.3 of the Samba suite. -

AUTHOR

The original Samba software and related utilities +

VERSION

This man page is correct for version 3.3 of the Samba suite. +

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.

diff -u -r --new-file --exclude .svn --exclude CVS samba-3.3.10//docs/htmldocs/manpages/vfs_extd_audit.8.html samba-3.3.11//docs/htmldocs/manpages/vfs_extd_audit.8.html --- samba-3.3.10//docs/htmldocs/manpages/vfs_extd_audit.8.html 2010-01-14 11:21:45.000000000 +0100 +++ samba-3.3.11//docs/htmldocs/manpages/vfs_extd_audit.8.html 2010-02-22 16:53:37.000000000 +0100 @@ -1,4 +1,4 @@ -vfs_extd_audit

Name

vfs_extd_audit — record selected Samba VFS operations

Synopsis

vfs objects = extd_audit

DESCRIPTION

This VFS module is part of the +vfs_extd_audit

Name

vfs_extd_audit — record selected Samba VFS operations

Synopsis

vfs objects = extd_audit

DESCRIPTION

This VFS module is part of the samba(7) suite.

The extd_audit VFS module records selected client operations to both the smbd(8) log and @@ -7,8 +7,8 @@ smbd(8) log, vfs_extd_audit is identical to vfs_audit(8). -

This module is stackable.

VERSION

This man page is correct for version 3.0.25 of the Samba suite. -

AUTHOR

The original Samba software and related utilities +

This module is stackable.

VERSION

This man page is correct for version 3.0.25 of the Samba suite. +

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.

diff -u -r --new-file --exclude .svn --exclude CVS samba-3.3.10//docs/htmldocs/manpages/vfs_fake_perms.8.html samba-3.3.11//docs/htmldocs/manpages/vfs_fake_perms.8.html --- samba-3.3.10//docs/htmldocs/manpages/vfs_fake_perms.8.html 2010-01-14 11:21:46.000000000 +0100 +++ samba-3.3.11//docs/htmldocs/manpages/vfs_fake_perms.8.html 2010-02-22 16:53:36.000000000 +0100 @@ -1,4 +1,4 @@ -vfs_fake_perms

Name

vfs_fake_perms — enable read only Roaming Profiles

Synopsis

vfs objects = fake_perms

DESCRIPTION

This VFS module is part of the +vfs_fake_perms

Name

vfs_fake_perms — enable read only Roaming Profiles

Synopsis

vfs objects = fake_perms

DESCRIPTION

This VFS module is part of the samba(7) suite.

The vfs_fake_perms VFS 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, @@ -6,12 +6,12 @@ the Profile files and directories are writeable. This satisfies the client even though the files will never be overwritten as the client logs out or shuts down. -

This module is stackable.

EXAMPLES

+	

This module is stackable.

VERSION

This man page is correct for version 3.0.25 of the Samba suite. -

AUTHOR

The original Samba software and related utilities +

VERSION

This man page is correct for version 3.0.25 of the Samba suite. +

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.

diff -u -r --new-file --exclude .svn --exclude CVS samba-3.3.10//docs/htmldocs/manpages/vfs_fileid.8.html samba-3.3.11//docs/htmldocs/manpages/vfs_fileid.8.html --- samba-3.3.10//docs/htmldocs/manpages/vfs_fileid.8.html 2010-01-14 11:21:47.000000000 +0100 +++ samba-3.3.11//docs/htmldocs/manpages/vfs_fileid.8.html 2010-02-22 16:53:36.000000000 +0100 @@ -1,5 +1,5 @@ -vfs_fileid

Name

vfs_fileid — Generates file_id structs with unique device id values for - cluster setups

Synopsis

vfs objects = fileid

DESCRIPTION

This VFS module is part of the +vfs_fileid

Name

vfs_fileid — Generates file_id structs with unique device id values for + cluster setups

Synopsis

vfs objects = fileid

DESCRIPTION

This VFS module is part of the samba(7) suite.

Samba uses file_id structs to uniquely identify files for locking purpose. By default the file_id contains the device @@ -9,7 +9,7 @@ SMB_VFS_FILE_ID_CREATE() operation and generates the device number based on the configured algorithm (see the "fileid:algorithm" option). -

OPTIONS

fileid:algorithm = ALGORITHM

Available algorithms are fsname +

OPTIONS

fileid:algorithm = ALGORITHM

Available algorithms are fsname and fsid. The default value is fsname.

The fsname algorithm generates @@ -20,13 +20,13 @@

fileid:mapping = ALGORITHM

This option is the legacy version of the fileid:algorithm option, which was used in earlier versions of fileid mapping feature in custom Samba 3.0 versions. -

EXAMPLES

Usage of the fileid module with the +

EXAMPLES

Usage of the fileid module with the fsid algorithm:

         [global]
 	vfs objects = fileid
 	fileid:algorithm = fsid
-

VERSION

This man page is correct for version 3.2 of the Samba suite. -

AUTHOR

The original Samba software and related utilities +

VERSION

This man page is correct for version 3.2 of the Samba suite. +

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.

diff -u -r --new-file --exclude .svn --exclude CVS samba-3.3.10//docs/htmldocs/manpages/vfs_full_audit.8.html samba-3.3.11//docs/htmldocs/manpages/vfs_full_audit.8.html --- samba-3.3.10//docs/htmldocs/manpages/vfs_full_audit.8.html 2010-01-14 11:21:49.000000000 +0100 +++ samba-3.3.11//docs/htmldocs/manpages/vfs_full_audit.8.html 2010-02-22 16:53:36.000000000 +0100 @@ -1,8 +1,8 @@ -vfs_full_audit

Name

vfs_full_audit — record Samba VFS operations in the system log

Synopsis

vfs objects = full_audit

DESCRIPTION

This VFS module is part of the +vfs_full_audit

Name

vfs_full_audit — record Samba VFS operations in the system log

Synopsis

vfs objects = full_audit

DESCRIPTION

This VFS module is part of the samba(7) suite.

The vfs_full_audit VFS module records selected client operations to the system log using syslog(3).

vfs_full_audit is able to record the - complete set of Samba VFS operations:

aio_cancel
aio_error
aio_fsync
aio_read
aio_return
aio_suspend
aio_write
chdir
chflags
chmod
chmod_acl
chown
close
closedir
connect
disconnect
disk_free
fchmod
fchmod_acl
fchown
fget_nt_acl
fgetxattr
flistxattr
fremovexattr
fset_nt_acl
fsetxattr
fstat
fsync
ftruncate
get_nt_acl
get_quota
get_shadow_copy_data
getlock
getwd
getxattr
kernel_flock
lgetxattr
link
linux_setlease
listxattr
llistxattr
lock
lremovexattr
lseek
lsetxattr
lstat
mkdir
mknod
open
opendir
pread
pwrite
read
readdir
readlink
realpath
removexattr
rename
rewinddir
rmdir
seekdir
sendfile
set_nt_acl
set_quota
setxattr
stat
statvfs
symlink
sys_acl_add_perm
sys_acl_clear_perms
sys_acl_create_entry
sys_acl_delete_def_file
sys_acl_free_acl
sys_acl_free_qualifier
sys_acl_free_text
sys_acl_get_entry
sys_acl_get_fd
sys_acl_get_file
sys_acl_get_perm
sys_acl_get_permset
sys_acl_get_qualifier
sys_acl_get_tag_type
sys_acl_init
sys_acl_set_fd
sys_acl_set_file
sys_acl_set_permset
sys_acl_set_qualifier
sys_acl_set_tag_type
sys_acl_to_text
sys_acl_valid
telldir
unlink
utime
write

In addition to these operations, + complete set of Samba VFS operations:

aio_cancel
aio_error
aio_fsync
aio_read
aio_return
aio_suspend
aio_write
chdir
chflags
chmod
chmod_acl
chown
close
closedir
connect
disconnect
disk_free
fchmod
fchmod_acl
fchown
fget_nt_acl
fgetxattr
flistxattr
fremovexattr
fset_nt_acl
fsetxattr
fstat
fsync
ftruncate
get_nt_acl
get_quota
get_shadow_copy_data
getlock
getwd
getxattr
kernel_flock
lgetxattr
link
linux_setlease
listxattr
llistxattr
lock
lremovexattr
lseek
lsetxattr
lstat
mkdir
mknod
open
opendir
pread
pwrite
read
readdir
readlink
realpath
removexattr
rename
rewinddir
rmdir
seekdir
sendfile
set_nt_acl
set_quota
setxattr
stat
statvfs
symlink
sys_acl_add_perm
sys_acl_clear_perms
sys_acl_create_entry
sys_acl_delete_def_file
sys_acl_free_acl
sys_acl_free_qualifier
sys_acl_free_text
sys_acl_get_entry
sys_acl_get_fd
sys_acl_get_file
sys_acl_get_perm
sys_acl_get_permset
sys_acl_get_qualifier
sys_acl_get_tag_type
sys_acl_init
sys_acl_set_fd
sys_acl_set_file
sys_acl_set_permset
sys_acl_set_qualifier
sys_acl_set_tag_type
sys_acl_to_text
sys_acl_valid
telldir
unlink
utime
write

In addition to these operations, vfs_full_audit recognizes the special operation names "all" and "none ", which refer to all the VFS operations and none of the VFS operations respectively. @@ -10,7 +10,7 @@ format consisting of fields separated by '|' characters. The format is:

 		smbd_audit: PREFIX|OPERATION|RESULT|FILE
-	

The record fields are:

  • PREFIX - the result of the full_audit:prefix string after variable substitutions

  • OPERATION - the name of the VFS operation

  • RESULT - whether the operation succeeded or failed

  • FILE - the name of the file or directory the operation was performed on

This module is stackable.

OPTIONS

vfs_full_audit:prefix = STRING

Prepend audit messages with STRING. STRING is +

The record fields are:

  • PREFIX - the result of the full_audit:prefix string after variable substitutions

  • OPERATION - the name of the VFS operation

  • RESULT - whether the operation succeeded or failed

  • FILE - the name of the file or directory the operation was performed on

This module is stackable.

OPTIONS

vfs_full_audit:prefix = STRING

Prepend audit messages with STRING. STRING is processed for standard substitution variables listed in smb.conf(5). The default prefix is "%u|%I".

vfs_full_audit:success = LIST

LIST is a list of VFS operations that should be @@ -24,7 +24,7 @@

full_audit:priority = PRIORITY

Log messages with the named syslog(3) priority. -

EXAMPLES

Log file and directory open operations on the [records] +

EXAMPLES

Log file and directory open operations on the [records] share using the LOCAL7 facility and ALERT priority, including the username and IP address:

         [records]
@@ -35,8 +35,8 @@
 	full_audit:failure = all
 	full_audit:facility = LOCAL7
 	full_audit:priority = ALERT
-

VERSION

This man page is correct for version 3.0.25 of the Samba suite. -

AUTHOR

The original Samba software and related utilities +

VERSION

This man page is correct for version 3.0.25 of the Samba suite. +

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.

diff -u -r --new-file --exclude .svn --exclude CVS samba-3.3.10//docs/htmldocs/manpages/vfs_gpfs.8.html samba-3.3.11//docs/htmldocs/manpages/vfs_gpfs.8.html --- samba-3.3.10//docs/htmldocs/manpages/vfs_gpfs.8.html 2010-01-14 11:21:50.000000000 +0100 +++ samba-3.3.11//docs/htmldocs/manpages/vfs_gpfs.8.html 2010-02-22 16:53:37.000000000 +0100 @@ -1,35 +1,35 @@ -vfs_gpfs

Name

vfs_gpfs — gpfs specific samba extensions like acls and prealloc

Synopsis

vfs objects = gpfs

DESCRIPTION

This VFS module is part of the +vfs_gpfs

Name

vfs_gpfs — gpfs specific samba extensions like acls and prealloc

Synopsis

vfs objects = gpfs

DESCRIPTION

This VFS module is part of the samba(7) suite.

The gpfs VFS module is the home for all gpfs extensions that Samba requires for proper integration with GPFS. It uses the GPL library interfaces provided by GPFS.

Currently the gpfs vfs module provides extensions in following areas : -

  • NFSv4 ACL Interfaces with configurable options for GPFS

  • Kernel oplock support on GPFS

  • Lease support on GPFS

+

  • NFSv4 ACL Interfaces with configurable options for GPFS

  • Kernel oplock support on GPFS

  • Lease support on GPFS

NOTE:This module follows the posix-acl behaviour and hence allows permission stealing via chown. Samba might allow at a later point in time, to restrict the chown via this module as such restrictions are the responsibility of the underlying filesystem than of Samba. -

This module is stackable.

OPTIONS

nfs4:mode = [ simple | special ]

+

This module is stackable.

OPTIONS

nfs4:mode = [ simple | special ]

Enable/Disable substitution of special IDs on GPFS. This parameter should not affect the windows users in anyway. It only ensures that Samba sets the special IDs - OWNER@ and GROUP@ ( mappings to simple uids ) that are relevant to GPFS. -

The following MODEs are understood by the module:

  • simple(default) - do not use special IDs in GPFS ACEs

  • special - use special IDs in GPFS ACEs.

nfs4:acedup = [dontcare|reject|ignore|merge]

+

The following MODEs are understood by the module:

  • simple(default) - do not use special IDs in GPFS ACEs

  • special - use special IDs in GPFS ACEs.

nfs4:acedup = [dontcare|reject|ignore|merge]

This parameter configures how Samba handles duplicate ACEs encountered in GPFS ACLs. GPFS allows/creates duplicate ACE for different bits for same ID. -

Following is the behaviour of Samba for different values :

  • dontcare (default) - copy the ACEs as they come

  • reject - stop operation and exit with error on ACL set op

  • ignore - don't include the second matching ACE

  • merge - bitwise OR the 2 ace.flag fields and 2 ace.mask fields of the 2 duplicate ACEs into 1 ACE

nfs4:chown = [yes|no]

This parameter allows enabling or disabling the chown supported +

Following is the behaviour of Samba for different values :

  • dontcare (default) - copy the ACEs as they come

  • reject - stop operation and exit with error on ACL set op

  • ignore - don't include the second matching ACE

  • merge - bitwise OR the 2 ace.flag fields and 2 ace.mask fields of the 2 duplicate ACEs into 1 ACE

nfs4:chown = [yes|no]

This parameter allows enabling or disabling the chown supported by the underlying filesystem. This parameter should be enabled with care as it might leave your system insecure.

Some filesystems allow chown as a) giving b) stealing. It is the latter - that is considered a risk.

Following is the behaviour of Samba for different values :

  • yes - Enable chown if as supported by the under filesystem

  • no (default) - Disable chown

EXAMPLES

A GPFS mount can be exported via Samba as follows :

+		that is considered a risk.

Following is the behaviour of Samba for different values :

  • yes - Enable chown if as supported by the under filesystem

  • no (default) - Disable chown

EXAMPLES

A GPFS mount can be exported via Samba as follows :

         [samba_gpfs_share]
 	vfs objects = gpfs
 	path = /test/gpfs_mount
 	nfs4: mode = special
 	nfs4: acedup = merge
-

CAVEATS

The gpfs gpl libraries are required by gpfs VFS +

CAVEATS

The gpfs gpl libraries are required by gpfs VFS module during both compilation and runtime. Also this VFS module is tested to work on SLES 9/10 and RHEL 4.4 -

VERSION

This man page is correct for version 3.0.25 of the Samba suite. -

AUTHOR

The original Samba software and related utilities +

VERSION

This man page is correct for version 3.0.25 of the Samba suite. +

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 GPFS VFS module was created with contributions from diff -u -r --new-file --exclude .svn --exclude CVS samba-3.3.10//docs/htmldocs/manpages/vfs_netatalk.8.html samba-3.3.11//docs/htmldocs/manpages/vfs_netatalk.8.html --- samba-3.3.10//docs/htmldocs/manpages/vfs_netatalk.8.html 2010-01-14 11:21:51.000000000 +0100 +++ samba-3.3.11//docs/htmldocs/manpages/vfs_netatalk.8.html 2010-02-22 16:53:37.000000000 +0100 @@ -1,15 +1,15 @@ -vfs_netatalk

Name

vfs_netatalk — hide .AppleDouble files from CIFS clients

Synopsis

vfs objects = netatalk

DESCRIPTION

This VFS module is part of the +vfs_netatalk

Name

vfs_netatalk — hide .AppleDouble files from CIFS clients

Synopsis

vfs objects = netatalk

DESCRIPTION

This VFS module is part of the samba(7) suite.

The vfs_netatalk VFS module dynamically hides .AppleDouble files, preventing spurious errors on some CIFS clients. .AppleDouble files may be created by historic - implementations of AFP (Apple Filing Protocol) on servers.

This module is stackable.

EXAMPLES

Hide .AppleDouble files on the [data] share:

+	implementations of AFP (Apple Filing Protocol) on servers. 

This module is stackable.

EXAMPLES

Hide .AppleDouble files on the [data] share:

         [data]
 	vfs objects = netatalk
-

CAVEATS

This module is largely historic and unlikely to be of use +

CAVEATS

This module is largely historic and unlikely to be of use in modern networks since current Apple systems are able to mount CIFS shares natively. -

VERSION

This man page is correct for version 3.0.25 of the Samba suite. -

AUTHOR

The original Samba software and related utilities +

VERSION

This man page is correct for version 3.0.25 of the Samba suite. +

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.

diff -u -r --new-file --exclude .svn --exclude CVS samba-3.3.10//docs/htmldocs/manpages/vfs_notify_fam.8.html samba-3.3.11//docs/htmldocs/manpages/vfs_notify_fam.8.html --- samba-3.3.10//docs/htmldocs/manpages/vfs_notify_fam.8.html 2010-01-14 11:21:52.000000000 +0100 +++ samba-3.3.11//docs/htmldocs/manpages/vfs_notify_fam.8.html 2010-02-22 16:53:37.000000000 +0100 @@ -1,12 +1,12 @@ -vfs_notify_fam

Name

vfs_notify_fam — FAM support for file change notifications

Synopsis

vfs objects = notify_fam

DESCRIPTION

This VFS module is part of the +vfs_notify_fam

Name

vfs_notify_fam — FAM support for file change notifications

Synopsis

vfs objects = notify_fam

DESCRIPTION

This VFS module is part of the samba(7) suite.

The vfs_notify_fam module makes use of the system FAM (File Alteration Monitor) daemon to implement file change notifications for Windows clients. FAM is generally - present only on IRIX and some BSD systems.

This module is not stackable.

EXAMPLES

Support FAM notifications globally:

+	present only on IRIX and some BSD systems.

This module is not stackable.

EXAMPLES

Support FAM notifications globally:

         [global]
 	vfs objects = notify_fam
-

VERSION

This man page is correct for version 3.0.25 of the Samba suite. -

AUTHOR

The original Samba software and related utilities +

VERSION

This man page is correct for version 3.0.25 of the Samba suite. +

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.

diff -u -r --new-file --exclude .svn --exclude CVS samba-3.3.10//docs/htmldocs/manpages/vfs_prealloc.8.html samba-3.3.11//docs/htmldocs/manpages/vfs_prealloc.8.html --- samba-3.3.10//docs/htmldocs/manpages/vfs_prealloc.8.html 2010-01-14 11:21:54.000000000 +0100 +++ samba-3.3.11//docs/htmldocs/manpages/vfs_prealloc.8.html 2010-02-22 16:53:36.000000000 +0100 @@ -1,22 +1,22 @@ -vfs_prealloc

Name

vfs_prealloc — preallocate matching files to a predetermined size

Synopsis

vfs objects = prealloc

DESCRIPTION

This VFS module is part of the +vfs_prealloc

Name

vfs_prealloc — preallocate matching files to a predetermined size

Synopsis

vfs objects = prealloc

DESCRIPTION

This VFS module is part of the samba(7) suite.

The vfs_prealloc VFS module preallocates files to a specified size each time a new file is created. This is useful in environments where files are of a predetermined size will be written to a disk subsystem where extending file - allocations is expensive.

This module is stackable.

OPTIONS

prealloc:EXT = BYTES

Preallocate all files with the extension EXT to + allocations is expensive.

This module is stackable.

OPTIONS

prealloc:EXT = BYTES

Preallocate all files with the extension EXT to the size specified by BYTES. -

The following suffixes may be applied to BYTES:

  • K - BYTES is a number of kilobytes

  • M - BYTES is a number of megabytes

  • G - BYTES is a number of gigabytes

EXAMPLES

A process writes TIFF files to a Samba share, and the +

The following suffixes may be applied to BYTES:

  • K - BYTES is a number of kilobytes

  • M - BYTES is a number of megabytes

  • G - BYTES is a number of gigabytes

EXAMPLES

A process writes TIFF files to a Samba share, and the is known these files will almost always be around 4 megabytes (4194304 bytes):

         [frames]
 	path = /data/frames
 	vfs objects = prealloc
 	prealloc:tiff = 4M
-

CAVEATS

vfs_prealloc is not supported on all +

CAVEATS

vfs_prealloc is not supported on all platforms and filesystems. Currently only XFS filesystems on Linux and IRIX are supported. -

VERSION

This man page is correct for version 3.0.25 of the Samba suite. -

AUTHOR

The original Samba software and related utilities +

VERSION

This man page is correct for version 3.0.25 of the Samba suite. +

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.

diff -u -r --new-file --exclude .svn --exclude CVS samba-3.3.10//docs/htmldocs/manpages/vfs_preopen.8.html samba-3.3.11//docs/htmldocs/manpages/vfs_preopen.8.html --- samba-3.3.10//docs/htmldocs/manpages/vfs_preopen.8.html 2010-01-14 11:21:55.000000000 +0100 +++ samba-3.3.11//docs/htmldocs/manpages/vfs_preopen.8.html 2010-02-22 16:53:36.000000000 +0100 @@ -1,11 +1,11 @@ -vfs_preopen

Name

vfs_preopen — Hide read latencies for applications reading numbered files

Synopsis

vfs objects = preopen

DESCRIPTION

This VFS module is part of the +vfs_preopen

Name

vfs_preopen — Hide read latencies for applications reading numbered files

Synopsis

vfs objects = preopen

DESCRIPTION

This VFS module is part of the samba(7) suite.

This module assists applications that want to read numbered files in sequence with very strict latency requirements. One area where this happens in video streaming applications that want to read one file per frame.

When you use this module, a number of helper processes is started that speculatively open files and read a number of bytes to prime the file system cache, so that later on when the real - application's request comes along, no disk access is necessary.

This module is stackable.

OPTIONS

preopen:names = /pattern/

+ application's request comes along, no disk access is necessary.

This module is stackable.

OPTIONS

preopen:names = /pattern/

preopen:names specifies the file name pattern which should trigger the preopen helpers to do their work. We assume that the files are numbered incrementally. So if your file names @@ -19,8 +19,8 @@

preopen:queuelen = NUM-FILES

Number of files that should be speculatively opened. Defaults to the 10 subsequent files. -

VERSION

This man page is correct for version 3.3 of the Samba suite. -

AUTHOR

The original Samba software and related utilities +

VERSION

This man page is correct for version 3.3 of the Samba suite. +

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 PREOPEN VFS module was created with contributions from diff -u -r --new-file --exclude .svn --exclude CVS samba-3.3.10//docs/htmldocs/manpages/vfs_readahead.8.html samba-3.3.11//docs/htmldocs/manpages/vfs_readahead.8.html --- samba-3.3.10//docs/htmldocs/manpages/vfs_readahead.8.html 2010-01-14 11:21:56.000000000 +0100 +++ samba-3.3.11//docs/htmldocs/manpages/vfs_readahead.8.html 2010-02-22 16:53:37.000000000 +0100 @@ -1,4 +1,4 @@ -vfs_readahead

Name

vfs_readahead — pre-load the kernel buffer cache

Synopsis

vfs objects = readahead

DESCRIPTION

This VFS module is part of the +vfs_readahead

Name

vfs_readahead — pre-load the kernel buffer cache

Synopsis

vfs objects = readahead

DESCRIPTION

This VFS module is part of the samba(7) suite.

This vfs_readahead VFS module detects read requests at multiples of a given offset (hex 0x80000 by default) and then tells the kernel via either the readahead @@ -12,14 +12,14 @@ readahead:length option. By default this is set to the same value as the readahead:offset option and if not set explicitly will use the current value of - readahead:offset.

This module is stackable.

OPTIONS

The following suffixes may be applied to BYTES:

  • K - BYTES is a number of kilobytes

  • M - BYTES is a number of megabytes

  • G - BYTES is a number of gigabytes

readahead:offset = BYTES

The offset multiple that causes readahead to be + readahead:offset.

This module is stackable.

OPTIONS

The following suffixes may be applied to BYTES:

  • K - BYTES is a number of kilobytes

  • M - BYTES is a number of megabytes

  • G - BYTES is a number of gigabytes

readahead:offset = BYTES

The offset multiple that causes readahead to be requested of the kernel buffer cache.

readahead:length = BYTES

The number of bytes requested to be read into the kernel buffer cache on each - readahead call.

EXAMPLES

+		readahead call.

EXAMPLES

 	[hypothetical]
 	vfs objects = readahead
-

VERSION

This man page is correct for version 3.0.25 of the Samba suite. -

AUTHOR

The original Samba software and related utilities +

VERSION

This man page is correct for version 3.0.25 of the Samba suite. +

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.

diff -u -r --new-file --exclude .svn --exclude CVS samba-3.3.10//docs/htmldocs/manpages/vfs_readonly.8.html samba-3.3.11//docs/htmldocs/manpages/vfs_readonly.8.html --- samba-3.3.10//docs/htmldocs/manpages/vfs_readonly.8.html 2010-01-14 11:21:57.000000000 +0100 +++ samba-3.3.11//docs/htmldocs/manpages/vfs_readonly.8.html 2010-02-22 16:53:37.000000000 +0100 @@ -1,15 +1,15 @@ -vfs_readonly

Name

vfs_readonly — make a Samba share read only for a specified time period

Synopsis

vfs objects = readonly

DESCRIPTION

This VFS module is part of the +vfs_readonly

Name

vfs_readonly — make a Samba share read only for a specified time period

Synopsis

vfs objects = readonly

DESCRIPTION

This VFS module is part of the samba(7) suite.

The vfs_readonly VFS module marks a share as read only for all clients connecting within the configured time period. Clients connecting during this time will be denied write access to all files in the share, irrespective of ther - actual access privileges.

This module is stackable.

OPTIONS

readonly:period = BEGIN, END

Only mark the share as read only if the client + actual access privileges.

This module is stackable.

OPTIONS

readonly:period = BEGIN, END

Only mark the share as read only if the client connection was made between the times marked by the BEGIN and END date specifiers. The syntax of these date specifiers is the same as that accepted by the -d option of GNU date(1). -

EXAMPLES

Mark all shares read only:

+		

EXAMPLES

Mark all shares read only:

         [global]
 	vfs objects = readonly
 

Mark the [backup] share as read only during business hours:

@@ -17,8 +17,8 @@
 	path = /readonly
 	vfs objects = readonly
 	readonly:period = readonly:period = "today 9:00","today 17:00"
-

VERSION

This man page is correct for version 3.0.25 of the Samba suite. -

AUTHOR

The original Samba software and related utilities +

VERSION

This man page is correct for version 3.0.25 of the Samba suite. +

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.

diff -u -r --new-file --exclude .svn --exclude CVS samba-3.3.10//docs/htmldocs/manpages/vfs_recycle.8.html samba-3.3.11//docs/htmldocs/manpages/vfs_recycle.8.html --- samba-3.3.10//docs/htmldocs/manpages/vfs_recycle.8.html 2010-01-14 11:21:59.000000000 +0100 +++ samba-3.3.11//docs/htmldocs/manpages/vfs_recycle.8.html 2010-02-22 16:53:37.000000000 +0100 @@ -1,4 +1,4 @@ -vfs_recycle

Name

vfs_recycle — Samba VFS recycle bin

Synopsis

vfs objects = recycle

DESCRIPTION

This VFS module is part of the +vfs_recycle

Name

vfs_recycle — Samba VFS recycle bin

Synopsis

vfs objects = recycle

DESCRIPTION

This VFS module is part of the samba(7) suite.

The vfs_recycle intercepts file deletion requests and moves the affected files to a temporary repository rather than deleting them immediately. This gives the same effect @@ -10,7 +10,7 @@ of the created directory depends on recycle:repository. Users can recover files from the recycle bin. If the recycle:keeptree option has been specified, deleted files will be found in a path - identical with that from which the file was deleted.

This module is stackable.

OPTIONS

recycle:repository = PATH

Path of the directory where deleted files should be moved. + identical with that from which the file was deleted.

This module is stackable.

OPTIONS

recycle:repository = PATH

Path of the directory where deleted files should be moved.

If this option is not set, the default path .recycle is used.

recycle:directory_mode = MODE

Set MODE to the octal mode the recycle repository should be created with. The recycle repository will be @@ -47,7 +47,7 @@

recycle:noversions = LIST

Specifies a list of paths (wildcards such as * and ? are supported) for which no versioning should be used. Only useful when recycle:versions is enabled. -

EXAMPLES

Move files "deleted" on share to +

EXAMPLES

Move files "deleted" on share to /data/share/.recycle instead of deleting them:

         [share]
@@ -56,8 +56,8 @@
 	recycle:repository = .recycle
 	recycle:keeptree = yes
 	recycle:versions = yes
-

VERSION

This man page is correct for version 3.0.25 of the Samba suite. -

AUTHOR

The original Samba software and related utilities +

VERSION

This man page is correct for version 3.0.25 of the Samba suite. +

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.

diff -u -r --new-file --exclude .svn --exclude CVS samba-3.3.10//docs/htmldocs/manpages/vfs_shadow_copy2.8.html samba-3.3.11//docs/htmldocs/manpages/vfs_shadow_copy2.8.html --- samba-3.3.10//docs/htmldocs/manpages/vfs_shadow_copy2.8.html 2010-01-14 11:22:00.000000000 +0100 +++ samba-3.3.11//docs/htmldocs/manpages/vfs_shadow_copy2.8.html 2010-02-22 16:53:37.000000000 +0100 @@ -1,14 +1,14 @@ -vfs_shadow_copy2

Name

vfs_shadow_copy2 — Expose snapshots to Windows clients as shadow copies.

Synopsis

vfs objects = shadow_copy2

DESCRIPTION

This VFS module is part of the +vfs_shadow_copy2

Name

vfs_shadow_copy2 — Expose snapshots to Windows clients as shadow copies.

Synopsis

vfs objects = shadow_copy2

DESCRIPTION

This VFS module is part of the samba(7) suite.

The vfs_shadow_copy2 VFS module functionality that is similar to Microsoft Shadow Copy services. When setup properly, this module allows Microsoft Shadow Copy clients to browse "shadow copies" on Samba shares.

This is a 2nd implementation of a shadow copy module. This - version has the following features:

  1. You don't need to populate your shares with symlinks to the + version has the following features:

    1. You don't need to populate your shares with symlinks to the snapshots. This can be very important when you have thousands of - shares, or use [homes].

    2. The inode number of the files is altered so it is different + shares, or use [homes].

    3. The inode number of the files is altered so it is different from the original. This allows the 'restore' button to work - without a sharing violation.

    This module is stackable.

CONFIGURATION

vfs_shadow_copy2 relies on a filesystem + without a sharing violation.

This module is stackable.

CONFIGURATION

vfs_shadow_copy2 relies on a filesystem snapshot implementation. Many common filesystems have native support for this.

Filesystem snapshots must be mounted on @@ -16,12 +16,12 @@ vfs_shadow_copy2. The snapshot mount points must be immediate children of a the directory being shared.

The snapshot naming convention is @GMT-YYYY.MM.DD-hh.mm.ss, where: -

  • YYYY is the 4 digit year

  • MM is the 2 digit month

  • DD is the 2 digit day

  • hh is the 2 digit hour

  • mm is the 2 digit minute

  • ss is the 2 digit second.

+

  • YYYY is the 4 digit year

  • MM is the 2 digit month

  • DD is the 2 digit day

  • hh is the 2 digit hour

  • mm is the 2 digit minute

  • ss is the 2 digit second.

The vfs_shadow_copy2 snapshot naming convention can be produced with the following date(1) command:

 	TZ=GMT date +@GMT-%Y.%m.%d-%H.%M.%S
-	

OPTIONS

shadow:snapdir = SNAPDIR +

OPTIONS

shadow:snapdir = SNAPDIR

Path to the directory where snapshots are kept.

shadow:basedir = BASEDIR

Path to the base directory that snapshots are from. @@ -34,19 +34,19 @@ files (such as happens with GPFS snapshots). If you don't set this option then the 'restore' button in the shadow copy UI will fail with a sharing violation. -

EXAMPLES

Add shadow copy support to user home directories:

+                

EXAMPLES

Add shadow copy support to user home directories:

         [homes]
 	vfs objects = shadow_copy2
 	shadow:snapdir = /data/snaphots
 	shadow:basedir = /data/home
-

CAVEATS

This is not a backup, archival, or version control solution. +

CAVEATS

This is not a backup, archival, or version control solution.

With Samba or Windows servers, vfs_shadow_copy2 is designed to be an end-user tool only. It does not replace or enhance your backup and archival solutions and should in no way be considered as such. Additionally, if you need version control, implement a - version control system.

VERSION

This man page is correct for version 3.2.7 of the Samba suite. -

AUTHOR

The original Samba software and related utilities + version control system.

VERSION

This man page is correct for version 3.2.7 of the Samba suite. +

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.

diff -u -r --new-file --exclude .svn --exclude CVS samba-3.3.10//docs/htmldocs/manpages/vfs_shadow_copy.8.html samba-3.3.11//docs/htmldocs/manpages/vfs_shadow_copy.8.html --- samba-3.3.10//docs/htmldocs/manpages/vfs_shadow_copy.8.html 2010-01-14 11:22:01.000000000 +0100 +++ samba-3.3.11//docs/htmldocs/manpages/vfs_shadow_copy.8.html 2010-02-22 16:53:37.000000000 +0100 @@ -1,9 +1,9 @@ -vfs_shadow_copy

Name

vfs_shadow_copy — Make a Samba share read only for a specified time period

Synopsis

vfs objects = shadow_copy

DESCRIPTION

This VFS module is part of the +vfs_shadow_copy

Name

vfs_shadow_copy — Make a Samba share read only for a specified time period

Synopsis

vfs objects = shadow_copy

DESCRIPTION

This VFS module is part of the samba(7) suite.

The vfs_shadow_copy VFS module functionality that is similar to Microsoft Shadow Copy services. When setup properly, this module allows Microsoft Shadow Copy clients to browse "shadow copies" on Samba shares. -

This module is stackable.

CONFIGURATION

vfs_shadow_copy relies on a filesystem +

This module is stackable.

CONFIGURATION

vfs_shadow_copy relies on a filesystem snapshot implementation. Many common filesystems have native support for this.

Filesystem snapshots must be mounted on @@ -11,22 +11,22 @@ vfs_shadow_copy. The snapshot mount points must be immediate children of a the directory being shared.

The snapshot naming convention is @GMT-YYYY.MM.DD-hh.mm.ss, where: -

  • YYYY is the 4 digit year

  • MM is the 2 digit month

  • DD is the 2 digit day

  • hh is the 2 digit hour

  • mm is the 2 digit minute

  • ss is the 2 digit second.

+

  • YYYY is the 4 digit year

  • MM is the 2 digit month

  • DD is the 2 digit day

  • hh is the 2 digit hour

  • mm is the 2 digit minute

  • ss is the 2 digit second.

The vfs_shadow_copy snapshot naming convention can be produced with the following date(1) command:

 	TZ=GMT date +@GMT-%Y.%m.%d-%H.%M.%S
-	

EXAMPLES

Add shadow copy support to user home directories:

+	

EXAMPLES

Add shadow copy support to user home directories:

         [homes]
 	vfs objects = shadow_copy
-

CAVEATS

This is not a backup, archival, or version control solution. +

CAVEATS

This is not a backup, archival, or version control solution.

With Samba or Windows servers, vfs_shadow_copy is designed to be an end-user tool only. It does not replace or enhance your backup and archival solutions and should in no way be considered as such. Additionally, if you need version control, implement a - version control system.

VERSION

This man page is correct for version 3.0.25 of the Samba suite. -

AUTHOR

The original Samba software and related utilities + version control system.

VERSION

This man page is correct for version 3.0.25 of the Samba suite. +

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.

diff -u -r --new-file --exclude .svn --exclude CVS samba-3.3.10//docs/htmldocs/manpages/vfs_smb_traffic_analyzer.8.html samba-3.3.11//docs/htmldocs/manpages/vfs_smb_traffic_analyzer.8.html --- samba-3.3.10//docs/htmldocs/manpages/vfs_smb_traffic_analyzer.8.html 2010-01-14 11:22:03.000000000 +0100 +++ samba-3.3.11//docs/htmldocs/manpages/vfs_smb_traffic_analyzer.8.html 2010-02-22 16:53:36.000000000 +0100 @@ -1,5 +1,5 @@ -smb_traffic_analyzer

Name

vfs_smb_traffic_analyzer — log Samba VFS read and write operations through a socket - to a helper application

Synopsis

vfs objects = smb_traffic_analyzer

DESCRIPTION

This VFS module is part of the +smb_traffic_analyzer

Name

vfs_smb_traffic_analyzer — log Samba VFS read and write operations through a socket + to a helper application

Synopsis

vfs objects = smb_traffic_analyzer

DESCRIPTION

This VFS module is part of the samba(7) suite.

The vfs_smb_traffic_analyzer VFS module logs client write and read operations on a Samba server and sends this data over a socket to a helper program, which feeds a SQL database. More @@ -7,15 +7,15 @@ homepage of the project at: http://holger123.wordpress.com/smb-traffic-analyzer/

vfs_smb_traffic_analyzer currently is aware - of the following VFS operations:

write
pwrite
read
pread

vfs_smb_traffic_analyzer sends the following data + of the following VFS operations:

write
pwrite
read
pread

vfs_smb_traffic_analyzer sends the following data in a fixed format seperated by a comma through either an internet or a unix domain socket:

 	BYTES|USER|DOMAIN|READ/WRITE|SHARE|FILENAME|TIMESTAMP
 	

Description of the records: -

  • BYTES - the length in bytes of the VFS operation

  • USER - the user who initiated the operation

  • DOMAIN - the domain of the user

  • READ/WRITE - either "W" for a write operation or "R" for read

  • SHARE - the name of the share on which the VFS operation occured

  • FILENAME - the name of the file that was used by the VFS operation

  • TIMESTAMP - a timestamp, formatted as "yyyy-mm-dd hh-mm-ss.ms" indicating when the VFS operation occured

+

  • BYTES - the length in bytes of the VFS operation

  • USER - the user who initiated the operation

  • DOMAIN - the domain of the user

  • READ/WRITE - either "W" for a write operation or "R" for read

  • SHARE - the name of the share on which the VFS operation occured

  • FILENAME - the name of the file that was used by the VFS operation

  • TIMESTAMP - a timestamp, formatted as "yyyy-mm-dd hh-mm-ss.ms" indicating when the VFS operation occured

-

This module is stackable.

OPTIONS

smb_traffic_analyzer:mode = STRING

If STRING matches to "unix_domain_socket", the module will +

This module is stackable.

OPTIONS

smb_traffic_analyzer:mode = STRING

If STRING matches to "unix_domain_socket", the module will use a unix domain socket located at /var/tmp/stadsocket, if STRING contains an different string or is not defined, the module will use an internet domain socket for data transfer.

smb_traffic_analyzer:host = STRING

The module will send the data to the system named with @@ -28,7 +28,7 @@ smb_traffic_analyzer:anonymize_prefix, without generating an additional hash number. This means that any transfer data will be mapped to a single user, leading to a total - anonymization of user related data.

EXAMPLES

The module running on share "example_share", using a unix domain socket

+		anonymization of user related data.

EXAMPLES

The module running on share "example_share", using a unix domain socket

 	[example_share]
 	path = /data/example
 	vfs objects = smb_traffic_analyzer
@@ -49,8 +49,8 @@
 	smb_traffic_analyzer:host = examplehost
 	smb_traffic_analyzer:port = 3491
 	smb_traffic_analyzer:anonymize_prefix = User
-	

VERSION

This man page is correct for version 3.3 of the Samba suite. -

AUTHOR

The original Samba software and related utilities +

VERSION

This man page is correct for version 3.3 of the Samba suite. +

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 version of the VFS module and the diff -u -r --new-file --exclude .svn --exclude CVS samba-3.3.10//docs/htmldocs/manpages/vfs_streams_depot.8.html samba-3.3.11//docs/htmldocs/manpages/vfs_streams_depot.8.html --- samba-3.3.10//docs/htmldocs/manpages/vfs_streams_depot.8.html 2010-01-14 11:22:04.000000000 +0100 +++ samba-3.3.11//docs/htmldocs/manpages/vfs_streams_depot.8.html 2010-02-22 16:53:37.000000000 +0100 @@ -1,15 +1,15 @@ -vfs_streams_depot

Name

vfs_streams_depot — EXPERIMENTAL module to store alternate data streams in a +vfs_streams_depot

Name

vfs_streams_depot — EXPERIMENTAL module to store alternate data streams in a central directory. -

Synopsis

vfs objects = streams_depot

DESCRIPTION

This EXPERIMENTAL VFS module is part of the +

Synopsis

vfs objects = streams_depot

DESCRIPTION

This EXPERIMENTAL VFS module is part of the samba(7) suite.

The vfs_streams_depot enables storing of NTFS alternate data streams in the file system. As a normal posix file system does not support the concept of multiple data streams per file, the streams_depot module stores the data in files in a separate - directory.

OPTIONS

streams_depot:directory = PATH

Path of the directory where the alternate data streams - should be stored. Defaults to the sharepath/.streams.

EXAMPLES

+	directory.

OPTIONS

streams_depot:directory = PATH

Path of the directory where the alternate data streams + should be stored. Defaults to the sharepath/.streams.

EXAMPLES

         [share]
 	vfs objects = streams_depot
-

AUTHOR

The original Samba software and related utilities +

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.

diff -u -r --new-file --exclude .svn --exclude CVS samba-3.3.10//docs/htmldocs/manpages/vfs_streams_xattr.8.html samba-3.3.11//docs/htmldocs/manpages/vfs_streams_xattr.8.html --- samba-3.3.10//docs/htmldocs/manpages/vfs_streams_xattr.8.html 2010-01-14 11:22:05.000000000 +0100 +++ samba-3.3.11//docs/htmldocs/manpages/vfs_streams_xattr.8.html 2010-02-22 16:53:36.000000000 +0100 @@ -1,4 +1,4 @@ -vfs_streams_xattr

Name

vfs_streams_xattr — Store alternate data streams in posix xattrs

Synopsis

vfs objects = streams_xattr

DESCRIPTION

This VFS module is part of the +vfs_streams_xattr

Name

vfs_streams_xattr — Store alternate data streams in posix xattrs

Synopsis

vfs objects = streams_xattr

DESCRIPTION

This VFS module is part of the samba(7) suite.

The vfs_streams_xattr enables storing of NTFS alternate data streams in the file system. As a normal posix file system does not support the concept of multiple data streams per file, @@ -8,10 +8,10 @@ support xattrs.

Please note that most file systems have severe limitations on the size of xattrs. So this module might work for applications like IE that stores small zone information in streams but will fail for - applications that store serious amounts of data in ADSs.

EXAMPLES

+	applications that store serious amounts of data in ADSs.

EXAMPLES

         [share]
 	vfs objects = streams_xattr
-

AUTHOR

The original Samba software and related utilities +

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.

diff -u -r --new-file --exclude .svn --exclude CVS samba-3.3.10//docs/htmldocs/manpages/vfstest.1.html samba-3.3.11//docs/htmldocs/manpages/vfstest.1.html --- samba-3.3.10//docs/htmldocs/manpages/vfstest.1.html 2010-01-14 11:22:07.000000000 +0100 +++ samba-3.3.11//docs/htmldocs/manpages/vfstest.1.html 2010-02-22 16:53:37.000000000 +0100 @@ -1,8 +1,8 @@ -vfstest

Name

vfstest — tool for testing samba VFS modules

Synopsis

vfstest [-d debuglevel] [-c command] [-l logdir] [-h]

DESCRIPTION

This tool is part of the samba(7) suite.

vfstest is a small command line +vfstest

Name

vfstest — tool for testing samba VFS modules

Synopsis

vfstest [-d debuglevel] [-c command] [-l logdir] [-h]

DESCRIPTION

This tool is part of the samba(7) suite.

vfstest is a small command line utility that has the ability to test dso samba VFS modules. It gives the user the ability to call the various VFS functions manually and supports cascaded VFS modules. -

OPTIONS

-c|--command=command

Execute the specified (colon-separated) commands. +

OPTIONS

-c|--command=command

Execute the specified (colon-separated) commands. See below for the commands that are available.

-h|--help

Print a summary of command line options.

-l|--logfile=logbasename

File name for log/debug files. The extension @@ -32,10 +32,10 @@ compile time.

-l|--log-basename=logdirectory

Base directory name for log/debug files. The extension ".progname" will be appended (e.g. log.smbclient, log.smbd, etc...). 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 -

  • connect - VFS connect()

  • disconnect - VFS disconnect()

  • disk_free - VFS disk_free()

  • opendir - VFS opendir()

  • readdir - VFS readdir()

  • mkdir - VFS mkdir()

  • rmdir - VFS rmdir()

  • closedir - VFS closedir()

  • open - VFS open()

  • close - VFS close()

  • read - VFS read()

  • write - VFS write()

  • lseek - VFS lseek()

  • rename - VFS rename()

  • fsync - VFS fsync()

  • stat - VFS stat()

  • fstat - VFS fstat()

  • lstat - VFS lstat()

  • unlink - VFS unlink()

  • chmod - VFS chmod()

  • fchmod - VFS fchmod()

  • chown - VFS chown()

  • fchown - VFS fchown()

  • chdir - VFS chdir()

  • getwd - VFS getwd()

  • utime - VFS utime()

  • ftruncate - VFS ftruncate()

  • lock - VFS lock()

  • symlink - VFS symlink()

  • readlink - VFS readlink()

  • link - VFS link()

  • mknod - VFS mknod()

  • realpath - VFS realpath()

GENERAL COMMANDS

  • conf <smb.conf> - Load a different configuration file

  • help [<command>] - Get list of commands or info about specified command

  • debuglevel <level> - Set debug level

  • freemem - Free memory currently in use

  • exit - Exit vfstest

VERSION

This man page is correct for version 3 of the Samba - suite.

AUTHOR

The original Samba software and related utilities +

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 +

  • connect - VFS connect()

  • disconnect - VFS disconnect()

  • disk_free - VFS disk_free()

  • opendir - VFS opendir()

  • readdir - VFS readdir()

  • mkdir - VFS mkdir()

  • rmdir - VFS rmdir()

  • closedir - VFS closedir()

  • open - VFS open()

  • close - VFS close()

  • read - VFS read()

  • write - VFS write()

  • lseek - VFS lseek()

  • rename - VFS rename()

  • fsync - VFS fsync()

  • stat - VFS stat()

  • fstat - VFS fstat()

  • lstat - VFS lstat()

  • unlink - VFS unlink()

  • chmod - VFS chmod()

  • fchmod - VFS fchmod()

  • chown - VFS chown()

  • fchown - VFS fchown()

  • chdir - VFS chdir()

  • getwd - VFS getwd()

  • utime - VFS utime()

  • ftruncate - VFS ftruncate()

  • lock - VFS lock()

  • symlink - VFS symlink()

  • readlink - VFS readlink()

  • link - VFS link()

  • mknod - VFS mknod()

  • realpath - VFS realpath()

GENERAL COMMANDS

  • conf <smb.conf> - Load a different configuration file

  • help [<command>] - Get list of commands or info about specified command

  • debuglevel <level> - Set debug level

  • freemem - Free memory currently in use

  • exit - Exit vfstest

VERSION

This man page is correct for version 3 of the Samba + suite.

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 vfstest man page was written by Jelmer Vernooij.

diff -u -r --new-file --exclude .svn --exclude CVS samba-3.3.10//docs/htmldocs/manpages/vfs_xattr_tdb.8.html samba-3.3.11//docs/htmldocs/manpages/vfs_xattr_tdb.8.html --- samba-3.3.10//docs/htmldocs/manpages/vfs_xattr_tdb.8.html 2010-01-14 11:22:08.000000000 +0100 +++ samba-3.3.11//docs/htmldocs/manpages/vfs_xattr_tdb.8.html 2010-02-22 16:53:36.000000000 +0100 @@ -1,12 +1,12 @@ -vfs_xattr_tdb

Name

vfs_xattr_tdb — Save Extended Attributes (EAs) in a tdb file

Synopsis

vfs objects = xattr_tdb

DESCRIPTION

This VFS module is part of the +vfs_xattr_tdb

Name

vfs_xattr_tdb — Save Extended Attributes (EAs) in a tdb file

Synopsis

vfs objects = xattr_tdb

DESCRIPTION

This VFS module is part of the samba(7) suite.

The vfs_xattr_tdb VFS module stores Extended Attributes (EAs) in a tdb file. This enables the usage of Extended Attributes on OS and filesystems which do not support Extended Attributes by themselves. -

This module is stackable.

OPTIONS

xattr_tdb:file = PATH

Name of the tdb file the EAs are stored in. +

This module is stackable.

OPTIONS

xattr_tdb:file = PATH

Name of the tdb file the EAs are stored in. If this option is not set, the default filename - xattr.tdb is used.

AUTHOR

The original Samba software and related utilities + xattr.tdb is used.

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.

diff -u -r --new-file --exclude .svn --exclude CVS samba-3.3.10//docs/htmldocs/manpages/wbinfo.1.html samba-3.3.11//docs/htmldocs/manpages/wbinfo.1.html --- samba-3.3.10//docs/htmldocs/manpages/wbinfo.1.html 2010-01-14 11:22:10.000000000 +0100 +++ samba-3.3.11//docs/htmldocs/manpages/wbinfo.1.html 2010-02-22 16:53:37.000000000 +0100 @@ -1,9 +1,9 @@ -wbinfo

Name

wbinfo — Query information from winbind daemon

Synopsis

wbinfo [-a user%password] [--all-domains] [--allocate-gid] [--allocate-uid] [-D domain] [--domain domain] [-g] [--getdcname domain] [--get-auth-user] [-G gid] [-h] [-i user] [-I ip] [-K user%password] [-m] [-n name] [-N netbios-name] [--own-domain] [-p] [-r user] [--remove-uid-mapping uid,sid] [--remove-gid-mapping gid,sid] [-s sid] [--separator] [--sequence] [--set-auth-user user%password] [--set-uid-mapping uid,sid] [--set-gid-mapping gid,sid] [-S sid] [-t] [-u] [--uid-info uid] [--user-domgroups sid] [--user-sids sid] [-U uid] [-V] [-Y sid] [--verbose]

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] [--all-domains] [--allocate-gid] [--allocate-uid] [-D domain] [--domain domain] [-g] [--getdcname domain] [--get-auth-user] [-G gid] [-h] [-i user] [-I ip] [-K user%password] [-m] [-n name] [-N netbios-name] [--own-domain] [-p] [-r user] [--remove-uid-mapping uid,sid] [--remove-gid-mapping gid,sid] [-s sid] [--separator] [--sequence] [--set-auth-user user%password] [--set-uid-mapping uid,sid] [--set-gid-mapping gid,sid] [-S sid] [-t] [-u] [--uid-info uid] [--user-domgroups sid] [--user-sids sid] [-U uid] [-V] [-Y sid] [--verbose]

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

-a|--authenticate username%password

Attempt to authenticate a user via winbindd. + to return information.

OPTIONS

-a|--authenticate username%password

Attempt to authenticate a user via winbindd. This checks both authenticaion methods and reports its results. -

Note

Do not be tempted to use this +

Note

Do not be tempted to use this functionality for authentication in third-party applications. Instead use ntlm_auth(1).

--allocate-gid

Get a new GID out of idmap

--allocate-uid

Get a new UID out of idmap @@ -86,10 +86,10 @@ mapping in the IDmap backend.

--set-gid-mapping gid,sid

Create a new or modify an existing gid to sid mapping in the IDmap backend.

-V|--version

Prints the program version number.

-h|--help

Print a summary of command line options. -

EXIT STATUS

The wbinfo program returns 0 if the operation +

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

VERSION

This man page is correct for version 3 of - the Samba suite.

AUTHOR

The original Samba software and related utilities + failure.

VERSION

This man page is correct for version 3 of + the Samba suite.

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.

wbinfo and winbindd diff -u -r --new-file --exclude .svn --exclude CVS samba-3.3.10//docs/htmldocs/manpages/winbindd.8.html samba-3.3.11//docs/htmldocs/manpages/winbindd.8.html --- samba-3.3.10//docs/htmldocs/manpages/winbindd.8.html 2010-01-14 11:22:11.000000000 +0100 +++ samba-3.3.11//docs/htmldocs/manpages/winbindd.8.html 2010-02-22 16:53:36.000000000 +0100 @@ -1,5 +1,5 @@ -winbindd

Name

winbindd — Name Service Switch daemon for resolving names - from NT servers

Synopsis

winbindd [-D] [-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 +winbindd

Name

winbindd — Name Service Switch daemon for resolving names + from NT servers

Synopsis

winbindd [-D] [-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 number of services to the Name Service Switch capability found in most modern C libraries, to arbitrary applications via PAM and ntlm_auth and to Samba itself.

Even if winbind is not used for nsswitch, it still provides a @@ -11,7 +11,7 @@ parameters are not required. (This is known as `netlogon proxy only mode'.)

The Name Service Switch allows user and system information to be obtained from different databases services such as NIS or DNS. The exact behaviour can be configured - throught the /etc/nsswitch.conf file. + through the /etc/nsswitch.conf file. Users and groups are allocated as they are resolved to a range of user and group ids specified by the administrator of the Samba system.

The service provided by winbindd is called `winbind' and @@ -60,7 +60,7 @@ resolve hostnames from /etc/hosts and then from the WINS server.

 hosts:		files wins
-

OPTIONS

-F

If specified, this parameter causes +

OPTIONS

-F

If specified, this parameter causes the main winbindd process to not daemonize, i.e. double-fork and disassociate with the terminal. Child processes are still created as normal to service @@ -113,7 +113,7 @@ 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 +

NAME AND ID RESOLUTION

Users and groups on a Windows NT server are assigned a security id (SID) which is globally unique when the user or group is created. To convert the Windows NT user or group into a unix user or group, a mapping between SIDs and unix user @@ -127,24 +127,24 @@ where the user and group mappings are stored by winbindd. If this store 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.

CONFIGURATION

Configuration of the winbindd daemon + 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

+

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 an early Red Hat Linux box. @@ -163,7 +163,7 @@ auth required /lib/security/pam_unix.so \ use_first_pass shadow nullok

-

Note

+

Note

The PAM module pam_unix has recently replaced the module pam_pwdb. Some Linux systems use the module pam_unix2 in place of pam_unix.

Note in particular the use of the sufficient @@ -195,7 +195,7 @@ and that you can login to your unix box as a domain user, using the DOMAIN+user syntax for the username. You may wish to use the commands getent passwd and getent group - to confirm the correct operation of winbindd.

NOTES

The following notes are useful when configuring and + to confirm the correct operation of winbindd.

NOTES

The following notes are useful when configuring and running winbindd:

nmbd(8) must be running on the local machine for winbindd to work.

PAM is really easy to misconfigure. Make sure you know what you are doing when modifying PAM configuration files. It is possible @@ -203,7 +203,7 @@ then in general the user and groups ids allocated by winbindd will not be the same. The user and group ids will only be valid for the local machine, unless a shared idmap backend is configured.

If the the Windows NT SID to UNIX user and group id mapping - file is damaged or destroyed then the mappings will be lost.

SIGNALS

The following signals can be used to manipulate the + file is damaged or destroyed then the mappings will be lost.

SIGNALS

The following signals can be used to manipulate the winbindd daemon.

SIGHUP

Reload the smb.conf(5) file and apply any parameter changes to the running version of winbindd. This signal also clears any cached @@ -211,7 +211,7 @@ by winbindd is also reloaded.

SIGUSR2

The SIGUSR2 signal will cause winbindd to write status information to the winbind log file.

Log files are stored in the filename specified by the - log file parameter.

FILES

/etc/nsswitch.conf(5)

Name service switch configuration file.

/tmp/.winbindd/pipe

The UNIX pipe over which clients communicate with + log file parameter.

FILES

/etc/nsswitch.conf(5)

Name service switch configuration file.

/tmp/.winbindd/pipe

The UNIX pipe over which clients communicate with the winbindd program. For security reasons, the winbind client will only attempt to connect to the winbindd daemon if both the /tmp/.winbindd directory @@ -232,8 +232,8 @@ compiled using the --with-lockdir option. This directory is by default /usr/local/samba/var/locks .

$LOCKDIR/winbindd_cache.tdb

Storage for cached user and group information. -

VERSION

This man page is correct for version 3 of - the Samba suite.

AUTHOR

The original Samba software and related utilities +

VERSION

This man page is correct for version 3 of + the Samba suite.

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.

wbinfo and winbindd were diff -u -r --new-file --exclude .svn --exclude CVS samba-3.3.10//docs/htmldocs/manpages/winbind_krb5_locator.7.html samba-3.3.11//docs/htmldocs/manpages/winbind_krb5_locator.7.html --- samba-3.3.10//docs/htmldocs/manpages/winbind_krb5_locator.7.html 2010-01-14 11:22:13.000000000 +0100 +++ samba-3.3.11//docs/htmldocs/manpages/winbind_krb5_locator.7.html 2010-02-22 16:53:36.000000000 +0100 @@ -1,4 +1,4 @@ -winbind_krb5_locator

Name

winbind_krb5_locator — A plugin for MIT and Heimdal Kerberos for detecting KDCs using Windows semantics.

DESCRIPTION

+winbind_krb5_locator

Name

winbind_krb5_locator — A plugin for MIT and Heimdal Kerberos for detecting KDCs using Windows semantics.

DESCRIPTION

This plugin is part of the samba(7) suite.

winbind_krb5_locator is a plugin that permits MIT and @@ -8,7 +8,7 @@ of closest dc. The plugin uses the public locator API provided by most modern Kerberos implementations. -

PREREQUISITES

+

PREREQUISITES

MIT Kerberos (at least version 1.5) or Heimdal Kerberos (at least version 1.0) is required.

@@ -32,9 +32,9 @@ Users should be able to kinit into their kerberized Windows environment without any modification or servers being put manually into /etc/krb5.conf. -

VERSION

+

VERSION

This man page is correct for version 3 of the Samba suite. -

AUTHOR

+

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. diff -u -r --new-file --exclude .svn --exclude CVS samba-3.3.10//docs/htmldocs/Samba3-ByExample/2000users.html samba-3.3.11//docs/htmldocs/Samba3-ByExample/2000users.html --- samba-3.3.10//docs/htmldocs/Samba3-ByExample/2000users.html 2010-01-14 11:24:12.000000000 +0100 +++ samba-3.3.11//docs/htmldocs/Samba3-ByExample/2000users.html 2010-02-22 16:53:36.000000000 +0100 @@ -1,4 +1,4 @@ -Chapter 6. A Distributed 2000-User Network

Chapter 6. A Distributed 2000-User Network

+Chapter 6. A Distributed 2000-User Network

Chapter 6. A Distributed 2000-User Network

There is something indeed mystical about things that are big. Large networks exhibit a certain magnetism and exude a sense of importance that obscures reality. You and I know that it is no more @@ -30,7 +30,7 @@ Samba are largely under control. So in this section you focus on the specifics of implementing LDAP changes, Samba changes, and approach and design of the solution and its deployment. -

Introduction

+

Introduction

Abmas is a miracle company. Most businesses would have collapsed under the weight of rapid expansion that this company has experienced. Samba is flexible, so there is no need to reinstall the whole operating @@ -39,19 +39,19 @@ and then do a near-live conversion. There is no need to reinstall a Samba server just to change the way your network should function.

- + Network growth is common to all organizations. In this exercise, your preoccupation is with the mechanics of implementing Samba and LDAP so that network users on each network segment can work without impediment. -

Assignment Tasks

+

Assignment Tasks

Starting with the configuration files for the server called MASSIVE in “Making Happy Users”, you now deal with the issues that are particular to large distributed networks. Your task is simple identify the challenges, consider the alternatives, and then design and implement a solution.

- + Remember, you have users based in London (UK), Los Angeles, Washington. DC, and, three buildings in New York. A significant portion of your workforce have notebook computers and roam all over the @@ -72,18 +72,18 @@ You have outsourced all desktop deployment and management to DirectPointe. Your concern is server maintenance and third-level support. Build a plan and show what must be done. -

Dissection and Discussion

- - +

Dissection and Discussion

+ + In “Making Happy Users”, you implemented an LDAP server that provided the passdb backend for the Samba servers. You explored ways to accelerate Windows desktop profile handling and you took control of network performance.

- - - - + + + + The implementation of an LDAP-based passdb backend (known as ldapsam in Samba parlance), or some form of database that can be distributed, is essential to permit the deployment of Samba @@ -96,8 +96,8 @@ support the range of account facilities demanded by modern network managers.

- - + + The new tdbsam facility supports functionality that is similar to an ldapsam, but the lack of distributed infrastructure sorely limits the scope for its @@ -105,10 +105,10 @@ an XML-based backend, or for that matter, why not use an SQL-based backend? Is support for these tools broken? Answers to these questions require a bit of background.

- - - - + + + + What is a directory? A directory is a collection of information regarding objects that can be accessed to rapidly find information that is relevant in a particular and @@ -116,19 +116,19 @@ generally more often searched (read) than updated. As a consequence, the information is organized to facilitate read access rather than to support transaction processing.

- - - - + + + + The Lightweight Directory Access Protocol (LDAP) differs considerably from a traditional database. It has a simple search facility that uniquely makes a highly preferred mechanism for managing user identities. LDAP provides a scalable mechanism for distributing the data repository and for keeping all copies (slaves) in sync with the master repository.

- - - + + + Samba is a flexible and powerful file and print sharing technology. It can use many external authentication sources and can be part of a total authentication and identity management @@ -136,7 +136,7 @@ are Microsoft Active Directory and LDAP. Sites that specifically wish to avoid the proprietary implications of Microsoft Active Directory naturally gravitate toward OpenLDAP.

- + In “Making Happy Users”, you had to deal with a locally routed network. All deployment concerns focused around making users happy, and that simply means taking control over all network practices and @@ -147,12 +147,12 @@ between offices. You must take into account the way users need to access information globally. And you must make the network robust enough so that it can sustain partial breakdown without causing loss of -productivity.

Technical Issues

+productivity.

Technical Issues

There are at least three areas that need to be addressed as you approach the challenge of designing a network solution for the newly expanded business: -

  • - User needs such as mobility and data access

  • The nature of Windows networking protocols

  • Identity management infrastructure needs

Let's look at each in turn.

User Needs

+

  • + User needs such as mobility and data access

  • The nature of Windows networking protocols

  • Identity management infrastructure needs

Let's look at each in turn.

User Needs

The new company has three divisions. Staff for each division are spread across the company. Some staff are office-bound and some are mobile users. Mobile users travel globally. Some spend considerable periods working in other offices. @@ -163,7 +163,7 @@ curtail user needs. Parts of the global Internet infrastructure remain shielded off for reasons outside the scope of this discussion.

- + Decisions must be made regarding where data is to be stored, how it will be replicated (if at all), and what the network bandwidth implications are. For example, one decision that can be made is to give each office its own master @@ -174,8 +174,8 @@ This way, they can synchronize all files that have changed since each logon to the network.

- - + + No matter which way you look at this, the bandwidth requirements for acceptable performance are substantial even if only 10 percent of staff are global data users. A company with 3,500 employees, @@ -188,11 +188,11 @@ profile involves a transfer of over 750 KB from the profile server to and from the client.

- + Obviously then, user needs and wide-area practicalities dictate the economic and technical aspects of your network design as well as for standard operating procedures. -

The Nature of Windows Networking Protocols

- +

The Nature of Windows Networking Protocols

+ Network logons that include roaming profile handling requires from 140 KB to 2 MB. The inclusion of support for a minimal set of common desktop applications can push the size of a complete profile to over 15 MB. This has substantial implications @@ -200,8 +200,8 @@ determining the nature and style of mandatory profiles that may be enforced as part of a total service-level assurance program that might be implemented.

- - + + One way to reduce the network bandwidth impact of user logon traffic is through folder redirection. In “Making Happy Users”, you implemented this in the new Windows XP Professional standard @@ -210,14 +210,14 @@ also be excluded from synchronization to and from the server on logon or logout. Redirected folders are analogous to network drive connections. -

+

Of course, network applications should only be run off local application servers. As a general rule, even with 2 Mb/sec network bandwidth, it would not make sense at all for someone who is working out of the London office to run applications off a server that is located in New York.

- + When network bandwidth becomes a precious commodity (that is most of the time), there is a significant demand to understand network processes and to mold the limits of acceptability around the @@ -225,22 +225,22 @@

When a Windows NT4/200x/XP Professional client user logs onto the network, several important things must happen. -

  • - +

    • + The client obtains an IP address via DHCP. (DHCP is necessary so that users can roam between offices.) -

    • - - +

    • + + The client must register itself with the WINS and/or DNS server. -

    • - +

    • + The client must locate the closest domain controller. -

    • +

    • The client must log onto a domain controller and obtain as part of that process the location of the user's profile, load it, connect to redirected folders, and establish all network drive and printer connections. -

    • +

    • The domain controller must be able to resolve the user's credentials before the logon process is fully implemented.

    @@ -256,15 +256,15 @@ name both by broadcast and Unicast registration that is directed at the WINS server.

    - - + + Given that the client is already a domain member, it then sends a directed (Unicast) request to the WINS server seeking the list of IP addresses for domain controllers (NetBIOS name type 0x1C). The WINS server replies with the information requested.

    - - - + + + The client sends two netlogon mailslot broadcast requests to the local network and to each of the IP addresses returned by the WINS server. Whichever answers this request first appears to @@ -274,9 +274,9 @@ was listed in the WINS server response to a request for the list of domain controllers.

    - - - + + + The logon process begins with negotiation of the SMB/CIFS protocols that are to be used; this is followed by an exchange of information that ultimately includes the client sending the @@ -287,10 +287,10 @@ needs. A secondary fact we need to know is, what happens when local domain controllers fail or break?

    - - - - + + + + Under most circumstances, the nearest domain controller responds to the netlogon mailslot broadcast. The exception to this norm occurs when the nearest domain controller is too busy or is out @@ -299,18 +299,18 @@ domain controllers. Since there can be only one PDC, all additional domain controllers are by definition BDCs.

    - - + + The provision of sufficient servers that are BDCs is an important design factor. The second important design factor involves how each of the BDCs obtains user authentication data. That is the subject of the next section, which involves key decisions regarding Identity Management facilities. -

Identity Management Needs

- - - - +

Identity Management Needs

+ + + + Network managers recognize that in large organizations users generally need to be given resource access based on needs, while being excluded from other resources for reasons of privacy. It is @@ -319,9 +319,9 @@ by which user credentials are validated and filtered and appropriate rights and privileges are allocated.

- - - + + + Unfortunately, network resources tend to have their own Identity Management facilities, the quality and manageability of which varies from quite poor to exceptionally good. Corporations that use a mixture @@ -333,7 +333,7 @@ What was once called Yellow Pages is today known as Network Information System (NIS).

- + NIS gained a strong following throughout the UNIX/VMS space in a short period of time and retained that appeal and use for over a decade. Security concerns and inherent limitations have caused it to enter its @@ -343,9 +343,9 @@ demands as the demand for directory services that can be coupled with other information systems is catching on.

- - - + + + Nevertheless, both NIS and NIS+ continue to hold ground in business areas where UNIX still has major sway. Examples of organizations that remain firmly attached to the use of NIS and @@ -353,14 +353,14 @@ and large corporations that have a scientific or engineering focus.

- - + + Today's networking world needs a scalable, distributed Identity Management infrastructure, commonly called a directory. The most popular technologies today are Microsoft Active Directory service and a number of LDAP implementations.

- + The problem of managing multiple directories has become a focal point over the past decade, creating a large market for metadirectory products and services that allow organizations that @@ -369,15 +369,15 @@ another. The attendant benefit to end users is the promise of having to remember and deal with fewer login identities and passwords.

- + The challenge of every large network is to find the optimum balance of internal systems and facilities for Identity Management resources. How well the solution is chosen and implemented has potentially significant impact on network bandwidth and systems response needs.

- - - + + + In “Making Happy Users”, you implemented a single LDAP server for the entire network. This may work for smaller networks, but almost certainly fails to meet the needs of large and complex networks. The @@ -386,8 +386,8 @@ What is the best method for implementing master/slave LDAP servers within the context of a distributed 2,000-user network is a question that remains to be answered.

- - + + One possibility that has great appeal is to create a single, large distributed domain. The practical implications of this design (see “Network Topology 2000 User Complex Design A”) demands the placement of @@ -398,7 +398,7 @@ productivity against the cost of network management and maintenance.

- + The network design in “Network Topology 2000 User Complex Design B” takes the approach that management of networks that are too remote to be managed effectively from New York ought to be given a certain degree of @@ -409,22 +409,22 @@ the ability for network users to roam globally without some compromise in how they may access global resources.

- + Desk-bound users need not be negatively affected by this design, since the use of interdomain trusts can be used to satisfy the need for global data sharing.

- - - + + + When Samba-3 is configured to use an LDAP backend, it stores the domain account information in a directory entry. This account entry contains the domain SID. An unintended but exploitable side effect is that this makes it possible to operate with more than one PDC on a distributed network.

- - - + + + How might this peculiar feature be exploited? The answer is simple. It is imperative that each network segment have its own WINS server. Major servers on remote network segments can be given a static WINS entry in @@ -434,8 +434,8 @@ same domain SID. Since all domain account information can be stored in a single LDAP backend, users have unfettered ability to roam.

- - + + This concept has not been exhaustively validated, though we can see no reason why this should not work. The important facets are the following: The name of the domain must be identical in all locations. Each network segment must have @@ -446,10 +446,10 @@ on every network segment. Finally, the BDCs should each use failover LDAP servers that are in fact slave LDAP servers on the local segments.

- - - - + + + + With a single master LDAP server, all network updates are effected on a single server. In the event that this should become excessively fragile or network bandwidth limiting, one could implement a delegated LDAP domain. This is also @@ -463,7 +463,7 @@ administrators must of necessity follow the same standard procedures for managing the directory, because retroactive correction of inconsistent directory information can be exceedingly difficult. -

Political Issues

+

Political Issues

As organizations grow, the number of points of control increases also. In a large distributed organization, it is important that the Identity Management system be capable of being updated from @@ -471,11 +471,11 @@ become usable in a reasonable period, typically minutes rather than days (the old limitation of highly manual systems). -

Implementation

- - - - +

Implementation

+ + + + Samba-3 has the ability to use multiple password (authentication and identity resolution) backends. The diagram in “Samba and Authentication Backend Search Pathways” demonstrates how Samba uses winbind, LDAP, and NIS, the traditional system @@ -483,13 +483,13 @@ authentication and identity resolution (obtaining a UNIX UID/GID) using the specific systems shown.

Figure 6.1. Samba and Authentication Backend Search Pathways

Samba and Authentication Backend Search Pathways

- - - - - - - + + + + + + + Samba is capable of using the smbpasswd, tdbsam, xmlsam, and mysqlsam authentication databases. The SMB @@ -497,7 +497,7 @@ backend. LDAP is the preferred passdb backend for distributed network operations.

- + Additionally, it is possible to use multiple passdb backends concurrently as well as have multiple LDAP backends. As a result, you can specify a failover LDAP backend. The syntax for specifying a @@ -509,8 +509,8 @@

This configuration tells Samba to use a single LDAP server, as shown in “Samba Configuration to Use a Single LDAP Server”.

Figure 6.2. Samba Configuration to Use a Single LDAP Server

Samba Configuration to Use a Single LDAP Server


- - + + The addition of a failover LDAP server can simply be done by adding a second entry for the failover server to the single ldapsam entry, as shown here (note the particular use of the double quotes): @@ -532,7 +532,7 @@ ldapsam:ldap://slave.abmas.biz ...

- + The effect of this style of entry is that Samba lists the users that are in both LDAP databases. If both contain the same information, it results in each record being shown twice. This is, of course, not the @@ -543,7 +543,7 @@ well be an advantageous way to effectively integrate multiple LDAP databases into one seemingly contiguous directory. Only the first database will be updated. An example of this configuration is shown in “Samba Configuration to Use Two LDAP Databases - The result is additive.”. -

Figure 6.5. Samba Configuration to Use Two LDAP Databases - The result is additive.

Samba Configuration to Use Two LDAP Databases - The result is additive.

Note

+

Figure 6.5. Samba Configuration to Use Two LDAP Databases - The result is additive.

Samba Configuration to Use Two LDAP Databases - The result is additive.

Note

When the use of ldapsam is specified twice, as shown here, it is imperative that the two LDAP directories must be disjoint. If the entries are for a master LDAP server as well as its own slave server, updates to the LDAP @@ -553,9 +553,9 @@ It is assumed that the network you are working with follows in a pattern similar to what was covered in “Making Happy Users”. The following steps permit the operation of a master/slave OpenLDAP arrangement. -

Procedure 6.1. Implementation Steps for an LDAP Slave Server

  1. - - +

    Procedure 6.1. Implementation Steps for an LDAP Slave Server

    1. + + Log onto the master LDAP server as root. You are about to change the configuration of the LDAP server, so it makes sense to temporarily halt it. Stop OpenLDAP from running on @@ -567,11 +567,11 @@

       root#  service ldap stop
       

      -

    2. - +

    3. + Edit the /etc/openldap/slapd.conf file so it matches the content of “LDAP Master Server Configuration File /etc/openldap/slapd.conf”. -

    4. +

    5. Create a file called admin-accts.ldif with the following contents:

       dn: cn=updateuser,dc=abmas,dc=biz
      @@ -586,14 +586,14 @@
       sn: sambaadmin
       userPassword: buttercup
       

      -

    6. - Add an account called updateuser to the master LDAP server as shown here: +

    7. + Add an account called “updateuser” to the master LDAP server as shown here:

       root#  slapadd -v -l admin-accts.ldif
       

      -

    8. - - +

    9. + + Change directory to a suitable place to dump the contents of the LDAP server. The dump file (and LDIF file) is used to preload the slave LDAP server database. You can dump the database by executing: @@ -601,16 +601,16 @@ root# slapcat -v -l LDAP-transfer-LDIF.txt

      Each record is written to the file. -

    10. - +

    11. + Copy the file LDAP-transfer-LDIF.txt to the intended slave LDAP server. A good location could be in the directory /etc/openldap/preload. -

    12. +

    13. Log onto the slave LDAP server as root. You can now configure this server so the /etc/openldap/slapd.conf file matches the content of “LDAP Slave Configuration File /etc/openldap/slapd.conf”. -

    14. +

    15. Change directory to the location in which you stored the LDAP-transfer-LDIF.txt file (/etc/openldap/preload). While in this directory, execute: @@ -640,7 +640,7 @@ added: "cn=Finances,ou=Groups,dc=abmas,dc=biz" (00000012) added: "cn=PIOps,ou=Groups,dc=abmas,dc=biz" (00000013)

      -

    16. +

    17. Now start the LDAP server and set it to run automatically on system reboot by executing:

       root#  rcldap start
      @@ -651,10 +651,10 @@
       root#  service ldap start
       root#  chkconfig ldap on
       

      -

    18. - - - +

    19. + + + Go back to the master LDAP server. Execute the following to start LDAP as well as slurpd, the synchronization daemon, as shown here:

      @@ -663,16 +663,16 @@
       root#  rcslurpd start
       root#  chkconfig slurpd on
       

      - + On Red Hat Linux, check the equivalent command to start slurpd. -

    20. - +

    21. + On the master LDAP server you may now add an account to validate that replication is working. Assuming the configuration shown in “Making Happy Users”, execute:

       root#  /var/lib/samba/sbin/smbldap-useradd -a fruitloop
       

      -

    22. +

    23. On the slave LDAP server, change to the directory /var/lib/ldap. There should now be a file called replogfile. If replication worked as expected, the content of this file should be: @@ -696,10 +696,10 @@ modifyTimestamp: 20031227004338Z -

      -

    24. +

    25. Given that this first slave LDAP server is now working correctly, you may now implement additional slave LDAP servers as required. -

    26. +

    27. On each machine (PDC and BDCs) after the respective smb.conf files have been created as shown in Primary Domain Controller smb.conf File Part A + B + C and on BDCs the Backup Domain Controller smb.conf File Part A @@ -791,72 +791,72 @@ index sambaPrimaryGroupSID eq index sambaDomainName eq index default sub -


Example 6.3. Primary Domain Controller smb.conf File Part A

# Global parameters
[global]
unix charset = LOCALE
workgroup = MEGANET2
passdb backend = ldapsam:ldap://massive.abmas.biz
username map = /etc/samba/smbusers
log level = 1
syslog = 0
log file = /var/log/samba/%m
max log size = 0
smb ports = 139
name resolve order = wins bcast hosts
time server = Yes
printcap name = CUPS
add user script = /opt/IDEALX/sbin/smbldap-useradd -m '%u'
delete user script = /opt/IDEALX/sbin/smbldap-userdel '%u'
add group script = /opt/IDEALX/sbin/smbldap-groupadd -p '%g'
delete group script = /opt/IDEALX/sbin/smbldap-groupdel '%g'
add user to group script = /opt/IDEALX/sbin/smbldap-groupmod -m '%g' '%u'
delete user from group script = /opt/IDEALX/sbin/smbldap-groupmod -x '%g' '%u'
set primary group script = /opt/IDEALX/sbin/smbldap-usermod -g '%g' '%u'
add machine script = /opt/IDEALX/sbin/smbldap-useradd -w '%u'
shutdown script = /var/lib/samba/scripts/shutdown.sh
abort shutdown script = /sbin/shutdown -c
logon script = scripts\logon.bat
logon path = \\%L\profiles\%U
logon drive = X:
domain logons = Yes
domain master = Yes
wins support = Yes
ldap suffix = dc=abmas,dc=biz
ldap machine suffix = ou=People
ldap user suffix = ou=People
ldap group suffix = ou=Groups
ldap idmap suffix = ou=Idmap
ldap admin dn = cn=sambaadmin,dc=abmas,dc=biz
idmap backend = ldap://massive.abmas.biz
idmap uid = 10000-20000
idmap gid = 10000-20000
printer admin = root
printing = cups

Example 6.4. Primary Domain Controller smb.conf File Part B

[IPC$]
path = /tmp
[accounts]
comment = Accounting Files
path = /data/accounts
read only = No
[service]
comment = Financial Services Files
path = /data/service
read only = No
[pidata]
comment = Property Insurance Files
path = /data/pidata
read only = No
[homes]
comment = Home Directories
valid users = %S
read only = No
browseable = No
[printers]
comment = SMB Print Spool
path = /var/spool/samba
guest ok = Yes
printable = Yes
browseable = No

Example 6.5. Primary Domain Controller smb.conf File Part C

[apps]
comment = Application Files
path = /apps
admin users = bjones
read only = No
[netlogon]
comment = Network Logon Service
path = /var/lib/samba/netlogon
admin users = root, Administrator
guest ok = Yes
locking = No
[profiles]
comment = Profile Share
path = /var/lib/samba/profiles
read only = No
profile acls = Yes
[profdata]
comment = Profile Data Share
path = /var/lib/samba/profdata
read only = No
profile acls = Yes
[print$]
comment = Printer Drivers
path = /var/lib/samba/drivers
write list = root
admin users = root, Administrator

Example 6.6. Backup Domain Controller smb.conf File Part A

# # Global parameters
[global]
unix charset = LOCALE
workgroup = MEGANET2
netbios name = BLDG1
passdb backend = ldapsam:ldap://lapdc.abmas.biz
username map = /etc/samba/smbusers
log level = 1
syslog = 0
log file = /var/log/samba/%m
max log size = 50
smb ports = 139
name resolve order = wins bcast hosts
printcap name = CUPS
show add printer wizard = No
logon script = scripts\logon.bat
logon path = \\%L\profiles\%U
logon drive = X:
domain logons = Yes
os level = 63
domain master = No
wins server = 192.168.2.1
ldap suffix = dc=abmas,dc=biz
ldap machine suffix = ou=People
ldap user suffix = ou=People
ldap group suffix = ou=Groups
ldap idmap suffix = ou=Idmap
ldap admin dn = cn=sambaadmin,dc=abmas,dc=biz
utmp = Yes
idmap backend = ldap://massive.abmas.biz
idmap uid = 10000-20000
idmap gid = 10000-20000
printing = cups
[accounts]
comment = Accounting Files
path = /data/accounts
read only = No
[service]
comment = Financial Services Files
path = /data/service
read only = No

Example 6.7. Backup Domain Controller smb.conf File Part B

[pidata]
comment = Property Insurance Files
path = /data/pidata
read only = No
[homes]
comment = Home Directories
valid users = %S
read only = No
browseable = No
[printers]
comment = SMB Print Spool
path = /var/spool/samba
guest ok = Yes
printable = Yes
browseable = No
[apps]
comment = Application Files
path = /apps
admin users = bjones
read only = No
[netlogon]
comment = Network Logon Service
path = /var/lib/samba/netlogon
guest ok = Yes
locking = No
[profiles]
comment = Profile Share
path = /var/lib/samba/profiles
read only = No
profile acls = Yes
[profdata]
comment = Profile Data Share
path = /var/lib/samba/profdata
read only = No
profile acls = Yes

Key Points Learned

  • - +


Example 6.3. Primary Domain Controller smb.conf File Part A

# Global parameters
[global]
unix charset = LOCALE
workgroup = MEGANET2
passdb backend = ldapsam:ldap://massive.abmas.biz
username map = /etc/samba/smbusers
log level = 1
syslog = 0
log file = /var/log/samba/%m
max log size = 0
smb ports = 139
name resolve order = wins bcast hosts
time server = Yes
printcap name = CUPS
add user script = /opt/IDEALX/sbin/smbldap-useradd -m '%u'
delete user script = /opt/IDEALX/sbin/smbldap-userdel '%u'
add group script = /opt/IDEALX/sbin/smbldap-groupadd -p '%g'
delete group script = /opt/IDEALX/sbin/smbldap-groupdel '%g'
add user to group script = /opt/IDEALX/sbin/smbldap-groupmod -m '%g' '%u'
delete user from group script = /opt/IDEALX/sbin/smbldap-groupmod -x '%g' '%u'
set primary group script = /opt/IDEALX/sbin/smbldap-usermod -g '%g' '%u'
add machine script = /opt/IDEALX/sbin/smbldap-useradd -w '%u'
shutdown script = /var/lib/samba/scripts/shutdown.sh
abort shutdown script = /sbin/shutdown -c
logon script = scripts\logon.bat
logon path = \\%L\profiles\%U
logon drive = X:
domain logons = Yes
domain master = Yes
wins support = Yes
ldap suffix = dc=abmas,dc=biz
ldap machine suffix = ou=People
ldap user suffix = ou=People
ldap group suffix = ou=Groups
ldap idmap suffix = ou=Idmap
ldap admin dn = cn=sambaadmin,dc=abmas,dc=biz
idmap backend = ldap://massive.abmas.biz
idmap uid = 10000-20000
idmap gid = 10000-20000
printer admin = root
printing = cups

Example 6.4. Primary Domain Controller smb.conf File Part B

[IPC$]
path = /tmp
[accounts]
comment = Accounting Files
path = /data/accounts
read only = No
[service]
comment = Financial Services Files
path = /data/service
read only = No
[pidata]
comment = Property Insurance Files
path = /data/pidata
read only = No
[homes]
comment = Home Directories
valid users = %S
read only = No
browseable = No
[printers]
comment = SMB Print Spool
path = /var/spool/samba
guest ok = Yes
printable = Yes
browseable = No

Example 6.5. Primary Domain Controller smb.conf File Part C

[apps]
comment = Application Files
path = /apps
admin users = bjones
read only = No
[netlogon]
comment = Network Logon Service
path = /var/lib/samba/netlogon
admin users = root, Administrator
guest ok = Yes
locking = No
[profiles]
comment = Profile Share
path = /var/lib/samba/profiles
read only = No
profile acls = Yes
[profdata]
comment = Profile Data Share
path = /var/lib/samba/profdata
read only = No
profile acls = Yes
[print$]
comment = Printer Drivers
path = /var/lib/samba/drivers
write list = root
admin users = root, Administrator

Example 6.6. Backup Domain Controller smb.conf File Part A

# # Global parameters
[global]
unix charset = LOCALE
workgroup = MEGANET2
netbios name = BLDG1
passdb backend = ldapsam:ldap://lapdc.abmas.biz
username map = /etc/samba/smbusers
log level = 1
syslog = 0
log file = /var/log/samba/%m
max log size = 50
smb ports = 139
name resolve order = wins bcast hosts
printcap name = CUPS
show add printer wizard = No
logon script = scripts\logon.bat
logon path = \\%L\profiles\%U
logon drive = X:
domain logons = Yes
os level = 63
domain master = No
wins server = 192.168.2.1
ldap suffix = dc=abmas,dc=biz
ldap machine suffix = ou=People
ldap user suffix = ou=People
ldap group suffix = ou=Groups
ldap idmap suffix = ou=Idmap
ldap admin dn = cn=sambaadmin,dc=abmas,dc=biz
utmp = Yes
idmap backend = ldap://massive.abmas.biz
idmap uid = 10000-20000
idmap gid = 10000-20000
printing = cups
[accounts]
comment = Accounting Files
path = /data/accounts
read only = No
[service]
comment = Financial Services Files
path = /data/service
read only = No

Example 6.7. Backup Domain Controller smb.conf File Part B

[pidata]
comment = Property Insurance Files
path = /data/pidata
read only = No
[homes]
comment = Home Directories
valid users = %S
read only = No
browseable = No
[printers]
comment = SMB Print Spool
path = /var/spool/samba
guest ok = Yes
printable = Yes
browseable = No
[apps]
comment = Application Files
path = /apps
admin users = bjones
read only = No
[netlogon]
comment = Network Logon Service
path = /var/lib/samba/netlogon
guest ok = Yes
locking = No
[profiles]
comment = Profile Share
path = /var/lib/samba/profiles
read only = No
profile acls = Yes
[profdata]
comment = Profile Data Share
path = /var/lib/samba/profdata
read only = No
profile acls = Yes

Key Points Learned

  • + Where Samba-3 is used as a domain controller, the use of LDAP is an essential component to permit the use of BDCs. -

  • - +

  • + Replication of the LDAP master server to create a network of BDCs is an important mechanism for limiting WAN traffic. -

  • +

  • Network administration presents many complex challenges, most of which can be satisfied by good design but that also require sound communication and unification of management practices. This can be highly challenging in a large, globally distributed network. -

  • +

  • Roaming profiles must be contained to the local network segment. Any departure from this may clog wide-area arteries and slow legitimate network traffic to a crawl. -

Figure 6.6. Network Topology 2000 User Complex Design A

Network Topology 2000 User Complex Design A

Figure 6.7. Network Topology 2000 User Complex Design B

Network Topology 2000 User Complex Design B

Questions and Answers

+

Figure 6.6. Network Topology 2000 User Complex Design A

Network Topology 2000 User Complex Design A

Figure 6.7. Network Topology 2000 User Complex Design B

Network Topology 2000 User Complex Design B

Questions and Answers

There is much rumor and misinformation regarding the use of MS Windows networking protocols. These questions are just a few of those frequently asked. -

+

Is it true that DHCP uses lots of WAN bandwidth? -
+
How much background communication takes place between a master LDAP server and its slave LDAP servers? -
+
LDAP has a database. Is LDAP not just a fancy database front end? -
+
Can Active Directory obtain account information from an OpenLDAP server? -
+
What are the parts of a roaming profile? How large is each part? -
+
Can the My Documents folder be stored on a network drive? -
+
How much WAN bandwidth does WINS consume? -
+
How many BDCs should I have? What is the right number of Windows clients per server? -
+
I've heard that you can store NIS accounts in LDAP. Is LDAP not just a smarter way to run an NIS server? -
+
Can I use NIS in place of LDAP? -

- - +

+ + Is it true that DHCP uses lots of WAN bandwidth?

- - - + + + It is a smart practice to localize DHCP servers on each network segment. As a rule, there should be two DHCP servers per network segment. This means that if one server fails, there is always another to service user needs. DHCP requests use only UDP broadcast protocols. It is possible to run a DHCP Relay Agent on network routers. This makes it possible to run fewer DHCP servers.

- - + + A DHCP network address request and confirmation usually results in about six UDP packets. The packets are from 60 to 568 bytes in length. Let us consider a site that has 300 DHCP clients and that uses a 24-hour IP address lease. This means that all clients renew @@ -874,28 +874,28 @@

From this can be seen that the traffic impact would be minimal.

- - + + Even when DHCP is configured to do DNS update (dynamic DNS) over a wide-area link, the impact of the update is no more than the DHCP IP address renewal traffic and thus still insignificant for most practical purposes. -

- - +

+ + How much background communication takes place between a master LDAP server and its slave LDAP servers?

- + The process that controls the replication of data from the master LDAP server to the slave LDAP servers is called slurpd. The slurpd remains nascent (quiet) until an update must be propagated. The propagation traffic per LDAP slave to update (add/modify/delete) two user accounts requires less than 10KB traffic. -

+

LDAP has a database. Is LDAP not just a fancy database front end?

- - - - + + + + LDAP does store its data in a database of sorts. In fact, the LDAP backend is an application-specific data storage system. This type of database is indexed so that records can be rapidly located, but the database is not generic and can be used only in particular pre-programmed ways. General external @@ -904,57 +904,57 @@ orientation and typically allows external programs to perform ad hoc queries, even across data tables. An LDAP front end is a purpose-built tool that has a search orientation that is designed around specific simple queries. The term database is heavily overloaded and thus much misunderstood. -

- +

+ Can Active Directory obtain account information from an OpenLDAP server?

- + No, at least not directly. It is possible to provision Active Directory from and/or to an OpenLDAP database through use of a metadirectory server. Microsoft MMS (now called MIIS) can interface to OpenLDAP using standard LDAP queries and updates. -

+

What are the parts of a roaming profile? How large is each part? -

+

A roaming profile consists of -

  • +

    • Desktop folders such as Desktop, My Documents, My Pictures, My Music, Internet Files, Cookies, Application Data, Local Settings, and more. See “Making Happy Users”, “Windows XP Professional User Shared Folders”.

      - + Each of these can be anywhere from a few bytes to gigabytes in capacity. Fortunately, all such folders can be redirected to network drive resources. See “Configuration of Default Profile with Folder Redirection” for more information regarding folder redirection. -

    • +

    • A static or rewritable portion that is typically only a few files (2-5 KB of information). -

    • - - +

    • + + The registry load file that modifies the HKEY_LOCAL_USER hive. This is the NTUSER.DAT file. It can be from 0.4 to 1.5 MB.

    - + Microsoft Outlook PST files may be stored in the Local Settings\Application Data folder. It can be up to 2 GB in size per PST file. -

+

Can the My Documents folder be stored on a network drive?

- - + + Yes. More correctly, such folders can be redirected to network shares. No specific network drive connection is required. Registry settings permit this to be redirected directly to a UNC (Universal Naming Convention) resource, though it is possible to specify a network drive letter instead of a UNC name. See “Configuration of Default Profile with Folder Redirection”. -

- - - +

+ + + How much WAN bandwidth does WINS consume?

- - - + + + MS Windows clients cache information obtained from WINS lookups in a local NetBIOS name cache. This keeps WINS lookups to a minimum. On a network with 3500 MS Windows clients and a central WINS server, the total bandwidth demand measured at the WINS server, averaged over an 8-hour working day, @@ -966,7 +966,7 @@

In conclusion, the total load afforded through WINS traffic is again marginal to total operational usage as it should be. -

+

How many BDCs should I have? What is the right number of Windows clients per server?

It is recommended to have at least one BDC per network segment, including the segment served @@ -980,19 +980,19 @@

As unsatisfactory as the answer might sound, it all depends on network and server load characteristics. -

- +

+ I've heard that you can store NIS accounts in LDAP. Is LDAP not just a smarter way to run an NIS server?

The correct answer to both questions is yes. But do understand that an LDAP server has a configurable schema that can store far more information for many more purposes than just NIS. -

+

Can I use NIS in place of LDAP?

- - + + No. The NIS database does not have provision to store Microsoft encrypted passwords and does not deal with the types of data necessary for interoperability with Microsoft Windows networking. The use of LDAP with Samba requires the use of a number of schemas, one of which is the NIS schema, but also diff -u -r --new-file --exclude .svn --exclude CVS samba-3.3.10//docs/htmldocs/Samba3-ByExample/apa.html samba-3.3.11//docs/htmldocs/Samba3-ByExample/apa.html --- samba-3.3.10//docs/htmldocs/Samba3-ByExample/apa.html 2010-01-14 11:24:29.000000000 +0100 +++ samba-3.3.11//docs/htmldocs/Samba3-ByExample/apa.html 2010-02-22 16:53:36.000000000 +0100 @@ -1,50 +1,50 @@ -Appendix A.  GNU General Public License version 3

Appendix A.  - GNU General Public License version 3 -

Table of Contents

A. +

Version 3, 29 June 2007 @@ -54,7 +54,7 @@

Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed. -

+

Preamble

The GNU General Public License is a free, copyleft @@ -118,9 +118,9 @@

The precise terms and conditions for copying, distribution and modification follow. -

+

TERMS AND CONDITIONS -

+

0. Definitions.

“This License” refers to version 3 of the GNU @@ -162,7 +162,7 @@ License, and how to view a copy of this License. If the interface presents a list of user commands or options, such as a menu, a prominent item in the list meets this criterion. -

+

1. Source Code.

The “source code” for a work means the preferred form of the @@ -202,7 +202,7 @@ automatically from other parts of the Corresponding Source.

The Corresponding Source for a work in source code form is that same work. -

+

2. Basic Permissions.

All rights granted under this License are granted for the term of copyright @@ -227,7 +227,7 @@ Conveying under any other circumstances is permitted solely under the conditions stated below. Sublicensing is not allowed; section 10 makes it unnecessary. -

+

3. Protecting Users’ Legal Rights From Anti-Circumvention Law.

No covered work shall be deemed part of an effective technological measure @@ -242,7 +242,7 @@ the work as a means of enforcing, against the work’s users, your or third parties’ legal rights to forbid circumvention of technological measures. -

+

4. Conveying Verbatim Copies.

You may convey verbatim copies of the Program’s source code as you @@ -255,21 +255,21 @@

You may charge any price or no price for each copy that you convey, and you may offer support or warranty protection for a fee. -

+

5. Conveying Modified Source Versions.

You may convey a work based on the Program, or the modifications to produce it from the Program, in the form of source code under the terms of section 4, provided that you also meet all of these conditions: -

  1. +

    1. The work must carry prominent notices stating that you modified it, and giving a relevant date. -

    2. +

    3. The work must carry prominent notices stating that it is released under this License and any conditions added under section 7. This requirement modifies the requirement in section 4 to “keep intact all notices”. -

    4. +

    5. You must license the entire work, as a whole, under this License to anyone who comes into possession of a copy. This License will therefore apply, along with any applicable section 7 additional terms, to the @@ -277,7 +277,7 @@ packaged. This License gives no permission to license the work in any other way, but it does not invalidate such permission if you have separately received it. -

    6. +

    7. If the work has interactive user interfaces, each must display Appropriate Legal Notices; however, if the Program has interactive interfaces that do not display Appropriate Legal Notices, your work need @@ -291,18 +291,18 @@ or legal rights of the compilation’s users beyond what the individual works permit. Inclusion of a covered work in an aggregate does not cause this License to apply to the other parts of the aggregate. -

      +

      6. Conveying Non-Source Forms.

      You may convey a covered work in object code form under the terms of sections 4 and 5, provided that you also convey the machine-readable Corresponding Source under the terms of this License, in one of these ways: -

      1. +

        1. Convey the object code in, or embodied in, a physical product (including a physical distribution medium), accompanied by the Corresponding Source fixed on a durable physical medium customarily used for software interchange. -

        2. +

        3. Convey the object code in, or embodied in, a physical product (including a physical distribution medium), accompanied by a written offer, valid for at least three years and valid for as long as you offer spare parts @@ -313,12 +313,12 @@ price no more than your reasonable cost of physically performing this conveying of source, or (2) access to copy the Corresponding Source from a network server at no charge. -

        4. +

        5. Convey individual copies of the object code with a copy of the written offer to provide the Corresponding Source. This alternative is allowed only occasionally and noncommercially, and only if you received the object code with such an offer, in accord with subsection 6b. -

        6. +

        7. Convey the object code by offering access from a designated place (gratis or for a charge), and offer equivalent access to the Corresponding Source in the same way through the same place at no @@ -331,7 +331,7 @@ Regardless of what server hosts the Corresponding Source, you remain obligated to ensure that it is available for as long as needed to satisfy these requirements. -

        8. +

        9. Convey the object code using peer-to-peer transmission, provided you inform other peers where the object code and Corresponding Source of the work are being offered to the general public at no charge under @@ -386,7 +386,7 @@ (and with an implementation available to the public in source code form), and must require no special password or key for unpacking, reading or copying. -

          +

          7. Additional Terms.

          “Additional permissions” are terms that supplement the terms of @@ -408,24 +408,24 @@ Notwithstanding any other provision of this License, for material you add to a covered work, you may (if authorized by the copyright holders of that material) supplement the terms of this License with terms: -

          1. +

            1. Disclaiming warranty or limiting liability differently from the terms of sections 15 and 16 of this License; or -

            2. +

            3. Requiring preservation of specified reasonable legal notices or author attributions in that material or in the Appropriate Legal Notices displayed by works containing it; or -

            4. +

            5. Prohibiting misrepresentation of the origin of that material, or requiring that modified versions of such material be marked in reasonable ways as different from the original version; or -

            6. +

            7. Limiting the use for publicity purposes of names of licensors or authors of the material; or -

            8. +

            9. Declining to grant rights under trademark law for use of some trade names, trademarks, or service marks; or -

            10. +

            11. Requiring indemnification of licensors and authors of that material by anyone who conveys the material (or modified versions of it) with contractual assumptions of liability to the recipient, for any @@ -450,7 +450,7 @@ Additional terms, permissive or non-permissive, may be stated in the form of a separately written license, or stated as exceptions; the above requirements apply either way. -

              +

              8. Termination.

              You may not propagate or modify a covered work except as expressly provided @@ -476,7 +476,7 @@ License. If your rights have been terminated and not permanently reinstated, you do not qualify to receive new licenses for the same material under section 10. -

              +

              9. Acceptance Not Required for Having Copies.

              You are not required to accept this License in order to receive or run a @@ -487,7 +487,7 @@ These actions infringe copyright if you do not accept this License. Therefore, by modifying or propagating a covered work, you indicate your acceptance of this License to do so. -

              +

              10. Automatic Licensing of Downstream Recipients.

              Each time you convey a covered work, the recipient automatically receives a @@ -512,7 +512,7 @@ or counterclaim in a lawsuit) alleging that any patent claim is infringed by making, using, selling, offering for sale, or importing the Program or any portion of it. -

              +

              11. Patents.

              A “contributor” is a copyright holder who authorizes use under @@ -579,7 +579,7 @@ Nothing in this License shall be construed as excluding or limiting any implied license or other defenses to infringement that may otherwise be available to you under applicable patent law. -

              +

              12. No Surrender of Others’ Freedom.

              If conditions are imposed on you (whether by court order, agreement or @@ -591,7 +591,7 @@ to collect a royalty for further conveying from those to whom you convey the Program, the only way you could satisfy both those terms and this License would be to refrain entirely from conveying the Program. -

              +

              13. Use with the GNU Affero General Public License.

              Notwithstanding any other provision of this License, you have permission to @@ -602,7 +602,7 @@ requirements of the GNU Affero General Public License, section 13, concerning interaction through a network will apply to the combination as such. -

              +

              14. Revised Versions of this License.

              The Free Software Foundation may publish revised and/or new versions of the @@ -627,7 +627,7 @@ Later license versions may give you additional or different permissions. However, no additional obligations are imposed on any author or copyright holder as a result of your choosing to follow a later version. -

              +

              15. Disclaimer of Warranty.

              THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE @@ -638,7 +638,7 @@ THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION. -

              +

              16. Limitation of Liability.

              IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING WILL @@ -650,7 +650,7 @@ PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. -

              +

              17. Interpretation of Sections 15 and 16.

              If the disclaimer of warranty and limitation of liability provided above @@ -659,9 +659,9 @@ waiver of all civil liability in connection with the Program, unless a warranty or assumption of liability accompanies a copy of the Program in return for a fee. -

              +

              END OF TERMS AND CONDITIONS -

              +

              How to Apply These Terms to Your New Programs

              If you develop a new program, and you want it to be of the greatest possible diff -u -r --new-file --exclude .svn --exclude CVS samba-3.3.10//docs/htmldocs/Samba3-ByExample/appendix.html samba-3.3.11//docs/htmldocs/Samba3-ByExample/appendix.html --- samba-3.3.10//docs/htmldocs/Samba3-ByExample/appendix.html 2010-01-14 11:24:26.000000000 +0100 +++ samba-3.3.11//docs/htmldocs/Samba3-ByExample/appendix.html 2010-02-22 16:53:36.000000000 +0100 @@ -1,26 +1,26 @@ -Chapter 15. A Collection of Useful Tidbits

              Chapter 15. A Collection of Useful Tidbits

              - - +Chapter 15. A Collection of Useful Tidbits

              Chapter 15. A Collection of Useful Tidbits

              + + Information presented here is considered to be either basic or well-known material that is informative yet helpful. Over the years, I have observed an interesting behavior. There is an expectation that the process for joining a Windows client to a Samba-controlled Windows domain may somehow involve steps different from doing so with Windows NT4 or a Windows ADS domain. Be assured that the steps are identical, as shown in the example given below. -

              Joining a Domain: Windows 200x/XP Professional

              - +

              Joining a Domain: Windows 200x/XP Professional

              + Microsoft Windows NT/200x/XP Professional platforms can participate in Domain Security. This section steps through the process for making a Windows 200x/XP Professional machine a member of a Domain Security environment. It should be noted that this process is identical when joining a domain that is controlled by Windows NT4/200x as well as a Samba PDC. -

              Procedure 15.1. Steps to Join a Domain

              1. +

                Procedure 15.1. Steps to Join a Domain

                1. Click Start. -

                2. +

                3. Right-click My Computer, and then select Properties. -

                4. +

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

                  Figure 15.1. The General Panel.

                  The General Panel.


                  -

                6. +

                7. Click the Computer Name tab. This panel shows the Computer Description, the Full computer name, and the Workgroup or Domain name. @@ -29,40 +29,40 @@ Samba-3. If you wish to change the computer name, or join or leave the domain, click the Change button. See “The Computer Name Panel.”.

                  Figure 15.2. The Computer Name Panel.

                  The Computer Name Panel.


                  -

                8. +

                9. Click on Change. This panel shows that our example machine (TEMPTATION) is in a workgroup called WORKGROUP. We join the domain called MIDEARTH. See “The Computer Name Changes Panel”.

                  Figure 15.3. The Computer Name Changes Panel

                  The Computer Name Changes Panel


                  -

                10. +

                11. Enter the name MIDEARTH in the field below the Domain radio button.

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

                  Figure 15.4. The Computer Name Changes Panel Domain MIDEARTH

                  The Computer Name Changes Panel Domain MIDEARTH


                  -

                12. +

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

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

                  Figure 15.5. Computer Name Changes User name and Password Panel

                  Computer Name Changes User name and Password Panel


                  -

                14. +

                15. Click OK.

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

                - - + + The screen capture shown in “The Computer Name Changes Panel Domain MIDEARTH” has a button labeled More.... This button opens a panel in which you can set (or change) the Primary DNS suffix of the computer. This is a parameter that mainly affects members of Microsoft Active Directory. Active Directory is heavily oriented around the DNS namespace.

                - - + + Where NetBIOS technology uses WINS as well as UDP broadcast as key mechanisms for name resolution, Active Directory servers register their services with the Microsoft Dynamic DNS server. Windows clients must be able to query the correct DNS server to find the services (like which machines are domain controllers or which machines have the Netlogon service running).

                - + The default setting of the Primary DNS suffix is the Active Directory domain name. When you change the Primary DNS suffix, this does not affect domain membership, but it can break network browsing and the ability to resolve your computer name to a valid IP address. @@ -70,12 +70,12 @@ The Primary DNS suffix parameter principally affects MS Windows clients that are members of an Active Directory domain. Where the client is a member of a Samba domain, it is preferable to leave this field blank.

                - - According to Microsoft documentation, If this computer belongs to a group with Group Policy + + According to Microsoft documentation, “If this computer belongs to a group with Group Policy enabled on Primary DNS suffice of this computer, the string specified in the Group Policy is used as the primary DNS suffix and you might need to restart your computer to view the correct setting. The local setting is - used only if Group Policy is disabled or unspecified. -

              Samba System File Location

              + used only if Group Policy is disabled or unspecified.” +

              Samba System File Location

              One of the frustrations expressed by subscribers to the Samba mailing lists revolves around the choice of where the default Samba Team build and installation process locates its Samba files. The location, chosen in the early 1990s, for the default installation is in the /usr/local/samba directory. This is a perfectly reasonable location, particularly given all the other @@ -83,7 +83,7 @@

              Several UNIX vendors, and Linux vendors in particular, elected to locate the Samba files in a location other than the Samba Team default. -

              +

              Linux vendors, working in conjunction with the Free Standards Group (FSG), Linux Standards Base (LSB), and File Hierarchy System (FHS), have elected to locate the configuration files under the /etc/samba directory, common binary files (those used by users) in the /usr/bin directory, and the administrative files (daemons) in the @@ -92,13 +92,13 @@ /usr/share/swat. There are additional support files for smbd in the /usr/lib/samba directory tree. The files located there include the dynamically loadable modules for the passdb backend as well as for the VFS modules. -

              +

              Samba creates runtime control files and generates log files. The runtime control files (tdb and dat files) are stored in the /var/lib/samba directory. Log files are created in /var/log/samba.

              When Samba is built and installed using the default Samba Team process, all files are located under the /usr/local/samba directory tree. This makes it simple to find the files that Samba owns. -

              +

              One way to find the Samba files that are installed on your UNIX/Linux system is to search for the location of all files called smbd. Here is an example:

              @@ -131,7 +131,7 @@
               	

              Many people have been caught by installation of Samba using the default Samba Team process when it was already installed by the platform vendor's method. If your platform uses RPM format packages, you can check to see if Samba is installed by - executing: + executing:

               root#  rpm -qa | grep samba
               samba3-pdb-3.0.20-1
              @@ -143,9 +143,9 @@
               samba3-doc-3.0.20-1
               samba3-client-3.0.20-1
               samba3-cifsmount-3.0.20-1
              -	

              +

              The package names, of course, vary according to how the vendor, or the binary package builder, prepared them. -

              Starting Samba

              +

              Starting Samba

              Samba essentially consists of two or three daemons. A daemon is a UNIX application that runs in the background and provides services. An example of a service is the Apache Web server for which the daemon is called httpd. In the case of Samba, there are three daemons, two of which are needed as a minimum. @@ -186,19 +186,19 @@ fi exit 0


              nmbd

              - - + + This daemon handles all name registration and resolution requests. It is the primary vehicle involved in network browsing. It handles all UDP-based protocols. The nmbd daemon should be the first command started as part of the Samba startup process.

              smbd

              - - + + This daemon handles all TCP/IP-based connection services for file- and print-based operations. It also manages local authentication. It should be started immediately following the startup of nmbd.

              winbindd

              - - + + This daemon should be started when Samba is a member of a Windows NT4 or ADS domain. It is also needed when Samba has trust relationships with another domain. The winbindd daemon will check the smb.conf file for the presence of the idmap uid and idmap gid @@ -252,22 +252,22 @@ echo "Usage: smb {start|stop|restart|status}" exit 1 esac -


              +


              SUSE Linux implements individual control over each Samba daemon. A Samba control script that can be conveniently executed from the command line is shown in “A Useful Samba Control Script for SUSE Linux”. This can be located in the directory /sbin in a file called samba. This type of control script should be owned by user root and group root, and set so that only root can execute it. -

              +

              A sample startup script for a Red Hat Linux system is shown in “A Sample Samba Control Script for Red Hat Linux”. This file could be located in the directory /etc/rc.d and can be called samba. A similar startup script is required to control winbind. If you want to find more information regarding startup scripts please refer to the packaging section of the Samba source code distribution tarball. The packaging files for each platform include a startup control file. -

            DNS Configuration Files

            +

            DNS Configuration Files

            The following files are common to all DNS server configurations. Rather than repeat them multiple times, they are presented here for general reference. -

            The Forward Zone File for the Loopback Adaptor

            +

            The Forward Zone File for the Loopback Adaptor

            The forward zone file for the loopback address never changes. An example file is shown in “DNS Localhost Forward Zone File: /var/lib/named/localhost.zone”. All traffic destined for an IP address that is hosted on a physical interface on the machine itself is routed to the loopback adaptor. This is @@ -284,7 +284,7 @@ IN NS @ IN A 127.0.0.1 -


            The Reverse Zone File for the Loopback Adaptor

            +


        The Reverse Zone File for the Loopback Adaptor

        The reverse zone file for the loopback address as shown in “DNS Localhost Reverse Zone File: /var/lib/named/127.0.0.zone” is necessary so that references to the address 127.0.0.1 can be resolved to the correct name of the interface. @@ -344,21 +344,21 @@ . 3600000 NS M.ROOT-SERVERS.NET. M.ROOT-SERVERS.NET. 3600000 A 202.12.27.33 ; End of File -


    DNS Root Server Hint File

    +


DNS Root Server Hint File

The content of the root hints file as shown in “DNS Root Name Server Hint File: /var/lib/named/root.hint” changes slowly over time. Periodically this file should be updated from the source shown. Because of its size, this file is located at the end of this chapter. -

Alternative LDAP Database Initialization

+

Alternative LDAP Database Initialization

The following procedure may be used as an alternative means of configuring the initial LDAP database. Many administrators prefer to have greater control over how system files get configured. -

Initialization of the LDAP Database

+

Initialization of the LDAP Database

The first step to get the LDAP server ready for action is to create the LDIF file from which the LDAP database will be preloaded. This is necessary to create the containers into which the user, group, and other accounts are written. It is also necessary to preload the well-known Windows NT Domain Groups, as they must have the correct SID so that they can be recognized as special NT Groups by the MS Windows clients. -

Procedure 15.2. LDAP Directory Pre-Load Steps

  1. +

    Procedure 15.2. LDAP Directory Pre-Load Steps

    1. Create a directory in which to store the files you use to generate the LDAP LDIF file for your system. Execute the following:

      @@ -366,16 +366,16 @@
       root#  chown root:root /etc/openldap/SambaInit
       root#  chmod 700 /etc/openldap/SambaInit
       

      -

    2. +

    3. Install the files shown in “LDAP Pre-configuration Script: SMBLDAP-ldif-preconfig.sh Part A”, “LDAP Pre-configuration Script: SMBLDAP-ldif-preconfig.sh Part B”, and “LDAP Pre-configuration Script: SMBLDAP-ldif-preconfig.sh Part C” into the directory /etc/openldap/SambaInit/SMBLDAP-ldif-preconfig.sh. These three files are, respectively, parts A, B, and C of the SMBLDAP-ldif-preconfig.sh file. -

    4. +

    5. Install the files shown in “LDIF Pattern File Used to Pre-configure LDAP Part A” and “LDIF Pattern File Used to Pre-configure LDAP Part B” into the directory /etc/openldap/SambaInit/. These two files are parts A and B, respectively, of the init-ldif.pat file. -

    6. +

    7. Change to the /etc/openldap/SambaInit directory. Execute the following:

       root#  sh SMBLDAP-ldif-preconfig.sh
      @@ -415,7 +415,7 @@
       root# 
       

      This creates a file called MEGANET2.ldif. -

    8. +

    9. It is now time to preload the LDAP database with the following command:

      @@ -466,14 +466,14 @@
       modifyTimestamp: 20031217055747Z
       entryCSN: 2003121705:57:47Z#0x000a#0#0000
       

      -

    10. +

    11. Your LDAP database is ready for testing. You can now start the LDAP server using the system tool for your Linux operating system. For SUSE Linux, you can do this as follows:

       root#  rcldap start
       

      -

    12. +

    13. It is now a good idea to validate that the LDAP server is running correctly. Execute the following:

      @@ -705,14 +705,14 @@
       sambaGroupType: 2
       displayName: Domain Users
       description: Domain Users
      -

The LDAP Account Manager

- - - - - - - +


The LDAP Account Manager

+ + + + + + + The LDAP Account Manager (LAM) is an application suite that has been written in PHP. LAM can be used with any Web server that has PHP4 support. It connects to the LDAP server either using unencrypted connections or via SSL/TLS. LAM can be used to manage @@ -724,29 +724,29 @@ The current version of LAM is 0.4.9. Release of version 0.5 is expected in the third quarter of 2005.

- - - + + + Requirements: -

  • A web server that will work with PHP4.

  • PHP4 (available from the PHP home page.)

  • OpenLDAP 2.0 or later.

  • A Web browser that supports CSS.

  • Perl.

  • The gettext package.

  • mcrypt + mhash (optional).

  • It is also a good idea to install SSL support.

+

  • A web server that will work with PHP4.

  • PHP4 (available from the PHP home page.)

  • OpenLDAP 2.0 or later.

  • A Web browser that supports CSS.

  • Perl.

  • The gettext package.

  • mcrypt + mhash (optional).

  • It is also a good idea to install SSL support.

LAM is a useful tool that provides a simple Web-based device that can be used to manage the contents of the LDAP directory to: - - - -

  • Display user/group/host and Domain entries.

  • Manage entries (Add/Delete/Edit).

  • Filter and sort entries.

  • Store and use multiple operating profiles.

  • Edit organizational units (OUs).

  • Upload accounts from a file.

  • Is compatible with Samba-2.2.x and Samba-3.

+ + + +

  • Display user/group/host and Domain entries.

  • Manage entries (Add/Delete/Edit).

  • Filter and sort entries.

  • Store and use multiple operating profiles.

  • Edit organizational units (OUs).

  • Upload accounts from a file.

  • Is compatible with Samba-2.2.x and Samba-3.

When correctly configured, LAM allows convenient management of UNIX (Posix) and Samba user, group, and windows domain member machine accounts.

- - - - -The default password is lam. It is highly recommended that you use only + + + + +The default password is “lam.” It is highly recommended that you use only an SSL connection to your Web server for all remote operations involving LAM. If you want secure connections, you must configure your Apache Web server to permit connections to LAM using only SSL. -

Procedure 15.3. Apache Configuration Steps for LAM

  1. +

    Procedure 15.3. Apache Configuration Steps for LAM

    1. Extract the LAM package by untarring it as shown here:

       root#  tar xzf ldap-account-manager_0.4.9.tar.gz
      @@ -755,12 +755,12 @@
       

       root#  dpkg -i ldap-account-manager_0.4.9.all.deb
       

      -

    2. +

    3. Copy the extracted files to the document root directory of your Web server. For example, on SUSE Linux Enterprise Server 9, copy to the /srv/www/htdocs directory. -

    4. - +

    5. + Set file permissions using the following commands:

       root#  chown -R wwwrun:www /srv/www/htdocs/lam
      @@ -769,8 +769,8 @@
       root#  chmod 755 /srv/www/htdocs/lam/config
       root#  chmod 755 /srv/www/htdocs/lam/lib/*pl
       

      -

    6. - +

    7. + Using your favorite editor create the following config.cfg LAM configuration file:

      @@ -778,13 +778,13 @@
       root#  cp config.cfg_sample config.cfg
       root#  vi config.cfg
       

      - - + + An example file is shown in “Example LAM Configuration File config.cfg”. This is the minimum configuration that must be completed. The LAM profile file can be created using a convenient wizard that is part of the LAM configuration suite. -

    8. +

    9. Start your Web server then, using your Web browser, connect to LAM URL. Click on the the Configuration Login link then click on the @@ -794,7 +794,7 @@ lam.conf then, using your favorite editor, change the settings to match local site needs.

    - + An example of a working file is shown here in “LAM Profile Control File lam.conf”. This file has been stripped of comments to keep the size small. The comments and help information provided in the profile file that the wizard creates @@ -802,12 +802,12 @@ Your configuration file obviously reflects the configuration options that are preferred at your site.

    - + It is important that your LDAP server is running at the time that LAM is being configured. This permits you to validate correct operation. An example of the LAM login screen is provided in “The LDAP Account Manager Login Screen”.

    Figure 15.6. The LDAP Account Manager Login Screen

    The LDAP Account Manager Login Screen

    - + The LAM configuration editor has a number of options that must be managed correctly. An example of use of the LAM configuration editor is shown in “The LDAP Account Manager Configuration Screen”. It is important that you correctly set the minimum and maximum UID/GID values that are @@ -817,13 +817,13 @@ the initial settings to be made. Do not forget to reset these to sensible values before using LAM to add additional users and groups.

    Figure 15.7. The LDAP Account Manager Configuration Screen

    The LDAP Account Manager Configuration Screen

    - + LAM has some nice, but unusual features. For example, one unexpected feature in most application screens permits the generation of a PDF file that lists configuration information. This is a well thought out facility. This option has been edited out of the following screen shots to conserve space.

    - + When you log onto LAM the opening screen drops you right into the user manager as shown in “The LDAP Account Manager User Edit Screen”. This is a logical action as it permits the most-needed facility to be used immediately. The editing of an existing user, as with the addition of a new user, @@ -837,7 +837,7 @@ shows a sub-screen from the group editor that permits users to be assigned secondary group memberships.

    Figure 15.9. The LDAP Account Manager Group Edit Screen

    The LDAP Account Manager Group Edit Screen

    Figure 15.10. The LDAP Account Manager Group Membership Edit Screen

    The LDAP Account Manager Group Membership Edit Screen

    - + The final screen presented here is one that you should not normally need to use. Host accounts will be automatically managed using the smbldap-tools scripts. This means that the screen “The LDAP Account Manager Host Edit Screen” will, in most cases, not be used. @@ -883,7 +883,7 @@ samba3: yes cachetimeout: 5 pwdhash: SSHA -


IDEALX Management Console

+


IDEALX Management Console

IMC (the IDEALX Mamagement Console) is a tool that can be used as the basis for a comprehensive web-based management interface for UNIX and Linux systems.

@@ -897,7 +897,7 @@

For further information regarding IMC refer to the web site. Prebuilt RPM packages are also available. -

Effect of Setting File and Directory SUID/SGID Permissions Explained

+

Effect of Setting File and Directory SUID/SGID Permissions Explained

The setting of the SUID/SGID bits on the file or directory permissions flag has particular consequences. If the file is executable and the SUID bit is set, it executes with the privilege of (with the UID of) the owner of the file. For example, if you are logged onto a system as @@ -967,34 +967,34 @@ total 1 drw-rw-r-- 2 bobj Domain Users 12346 Dec 18 18:11 maryvfile.txt

-

Shared Data Integrity

+

Shared Data Integrity

The integrity of shared data is often viewed as a particularly emotional issue, especially where there are concurrent problems with multiuser data access. Contrary to the assertions of some who have experienced problems in either area, the cause has nothing to do with the phases of the moons of Jupiter.

The solution to concurrent multiuser data access problems must consider three separate areas - from which the problem may stem: -

  • application-level locking controls

  • client-side locking controls

  • server-side locking controls

+ from which the problem may stem: +

  • application-level locking controls

  • client-side locking controls

  • server-side locking controls

Many database applications use some form of application-level access control. An example of one well-known application that uses application-level locking is Microsoft Access. Detailed guidance is provided here because this is the most common application for which problems have been reported. -

+

Common applications that are affected by client- and server-side locking controls include MS Excel and Act!. Important locking guidance is provided here. -

Microsoft Access

+

Microsoft Access

The best advice that can be given is to carefully read the Microsoft knowledgebase articles that cover this area. Examples of relevant documents include: -

  • http://support.microsoft.com/default.aspx?scid=kb;en-us;208778

  • http://support.microsoft.com/default.aspx?scid=kb;en-us;299373

+

  • http://support.microsoft.com/default.aspx?scid=kb;en-us;208778

  • http://support.microsoft.com/default.aspx?scid=kb;en-us;299373

Make sure that your MS Access database file is configured for multiuser access (not set for exclusive open). Open MS Access on each client workstation, then set the following: (Menu bar) Tools+Options+[tab] General. Set network path to Default database folder: \\server\share\folder.

You can configure MS Access file sharing behavior as follows: click [tab] Advanced. - Set: -

  • Default open mode: Shared

  • Default Record Locking: Edited Record

  • Open databases using record_level locking

+ Set: +

  • Default open mode: Shared

  • Default Record Locking: Edited Record

  • Open databases using record_level locking

You must now commit the changes so that they will take effect. To do so, click ApplyOk. At this point, you should exit MS Access, restart it, and then validate that these settings have not changed. -

Act! Database Sharing

+

Act! Database Sharing

Where the server sharing the ACT! database(s) is running Samba,or Windows NT, 200x, or XP, you must disable opportunistic locking on the server and all workstations. Failure to do so results in data corruption. This information is available from the Act! Web site @@ -1002,7 +1002,7 @@ 1998223162925 as well as from article 200110485036. -

+

These documents clearly state that opportunistic locking must be disabled on both the server (Samba in the case we are interested in here), as well as on every workstation from which the centrally shared Act! database will be accessed. Act! provides @@ -1010,18 +1010,18 @@ registry settings that may otherwise interfere with the operation of Act! Registered Act! users may download this utility from the Act! Web site. -

Opportunistic Locking Controls

+

Opportunistic Locking Controls

Third-party Windows applications may not be compatible with the use of opportunistic file - and record locking. For applications that are known not to be compatible,[14] oplock + and record locking. For applications that are known not to be compatible,[14] oplock support may need to be disabled both on the Samba server and on the Windows workstations. -

+

Oplocks enable a Windows client to cache parts of a file that are being edited. Another windows client may then request to open the file with the ability to write to it. The server will then ask the original workstation that had the file open with a write lock to release its lock. Before doing so, that workstation must flush the file from cache memory to the disk or network drive. -

+

Disabling of Oplocks usage may require server and client changes. Oplocks may be disabled by file, by file pattern, on the share, or on the Samba server. diff -u -r --new-file --exclude .svn --exclude CVS samba-3.3.10//docs/htmldocs/Samba3-ByExample/Big500users.html samba-3.3.11//docs/htmldocs/Samba3-ByExample/Big500users.html --- samba-3.3.10//docs/htmldocs/Samba3-ByExample/Big500users.html 2010-01-14 11:24:05.000000000 +0100 +++ samba-3.3.11//docs/htmldocs/Samba3-ByExample/Big500users.html 2010-02-22 16:53:36.000000000 +0100 @@ -1,4 +1,4 @@ -Chapter 4. The 500-User Office

Chapter 4. The 500-User Office

+Chapter 4. The 500-User Office

Chapter 4. The 500-User Office

The Samba-3 networking you explored in “Secure Office Networking” covers the finer points of configuration of peripheral services such as DHCP and DNS, and WINS. You experienced implementation of a simple configuration of the services that are important adjuncts @@ -6,9 +6,9 @@

An analysis of the history of postings to the Samba mailing list easily demonstrates that the two most prevalent Samba problem areas are -

  • +

    • Defective resolution of a NetBIOS name to its IP address -

    • +

    • Printing problems

    The exercises @@ -17,9 +17,9 @@ that same approach to printing, but “Making Happy Users” presents an opportunity to make printing more complex for the administrator while making it easier for the user.

    - - - + + + “Secure Office Networking” demonstrates operation of a DHCP server and a DNS server as well as a central WINS server. You validated the operation of these services and saw an effective implementation of a Samba domain controller using the @@ -41,7 +41,7 @@ improve network management and control while reducing human resource overheads. You should take the opportunity to innovate and expand on the methods presented here and explore them to the fullest. -

    Introduction

    +

    Introduction

    Business continues to go well for Abmas. Mr. Meany is driving your success and the network continues to grow thanks to the hard work Christine has done. You recently hired Stanley Soroka as manager of information systems. Christine recommended Stan @@ -66,7 +66,7 @@ and to allow Stan and Christine to fully stage the new network and test it before it is rolled out. Your strategy is to complete the new network so that it is ready for operation when the old office moves into the new premises. -

    Assignment Tasks

    +

    Assignment Tasks

    The acquired business had 280 network users. The old Abmas building housed 220 network users in unbelievably cramped conditions. The network that initially served 130 users now handles 220 users quite well. @@ -107,7 +107,7 @@ DirectPointe Inc. receives from you a new standard desktop configuration every four months. They automatically roll that out to each desktop system. You must keep DirectPointe informed of all changes. -

    +

    The new network has a single Samba Primary Domain Controller (PDC) located in the Network Operation Center (NOC). Buildings 1 and 2 each have a local server for local application servicing. It is a domain member. The new system @@ -115,8 +115,8 @@

    Printing is based on raw pass-through facilities just as it has been used so far. All printer drivers are installed on the desktop and notebook computers. -

    Dissection and Discussion

    - +

    Dissection and Discussion

    + The example you are building in this chapter is of a network design that works, but this does not make it a design that is recommended. As a general rule, there should be at least one Backup Domain Controller (BDC) per 150 Windows network clients. The principle behind @@ -127,22 +127,22 @@ responsiveness. This network will have 500 clients serviced by one central domain controller. This is not a good omen for user satisfaction. You, of course, address this very soon (see “Making Happy Users”). -

    Technical Issues

    +

    Technical Issues

    Stan has talked you into a horrible compromise, but it is addressed. Just make certain that the performance of this network is well validated before going live.

    Design decisions made in this design include the following: -

    • - - - +

      • + + + A single PDC is being implemented. This limitation is based on the choice not to use LDAP. Many network administrators fear using LDAP because of the perceived complexity of implementation and management of an LDAP-based backend for all user identity management as well as to store network access credentials. -

      • - - +

      • + + Because of the refusal to use an LDAP (ldapsam) passdb backend at this time, the only choice that makes sense with 500 users is to use the tdbsam passwd backend. This type of backend is not receptive to replication to BDCs. If the tdbsam @@ -151,63 +151,63 @@ memory but not yet written to disk will not be replicated, and (2) domain member machines periodically change the secret machine password. When this happens, there is no mechanism to return the changed password to the PDC. -

      • +

      • All domain user, group, and machine accounts are managed on the PDC. This makes for a simple mode of operation but has to be balanced with network performance and integrity of operations considerations. -

      • - +

      • + A single central WINS server is being used. The PDC is also the WINS server. Any attempt to operate a routed network without a WINS server while using NetBIOS over TCP/IP protocols does not work unless on each client the name resolution entries for the PDC are added to the LMHOSTS. This file is normally located on the Windows XP Professional client in the C:\WINDOWS\SYSTEM32\ETC\DRIVERS directory. -

      • +

      • At this time the Samba WINS database cannot be replicated. That is why a single WINS server is being implemented. This should work without a problem. -

      • - +

      • + BDCs make use of winbindd to provide access to domain security credentials for file system access and object storage. -

      • - - +

      • + + Configuration of Windows XP Professional clients is achieved using DHCP. Each subnet has its own DHCP server. Backup DHCP serving is provided by one alternate DHCP server. This necessitates enabling of the DHCP Relay agent on all routers. The DHCP Relay agent must be programmed to pass DHCP Requests from the network directed at the backup DHCP server. -

      • +

      • All network users are granted the ability to print to any printer that is network-attached. All printers are available from each server. Print jobs that are spooled to a printer that is not on the local network segment are automatically routed to the print spooler that is in control of that printer. The specific details of how this might be done are demonstrated for one example only. -

      • +

      • The network address and subnetmask chosen provide 1022 usable IP addresses in each subnet. If in the future more addresses are required, it would make sense to add further subnets rather than change addressing. -

    Political Issues

    +

Political Issues

This case gets close to the real world. You and I know the right way to implement domain control. Politically, we have to navigate a minefield. In this case, the need is to get the PDC rolled out in compliance with expectations and also to be ready to save the day by having the real solution ready before it is needed. That real solution is presented in “Making Happy Users”. -

Implementation

+

Implementation

The following configuration process begins following installation of Red Hat Fedora Core2 on the three servers shown in the network topology diagram in “Network Topology 500 User Network Using tdbsam passdb backend.”. You have selected hardware that is appropriate to the task. -

Figure 4.1. Network Topology 500 User Network Using tdbsam passdb backend.

Network Topology 500 User Network Using tdbsam passdb backend.

Installation of DHCP, DNS, and Samba Control Files

+

Figure 4.1. Network Topology 500 User Network Using tdbsam passdb backend.

Network Topology 500 User Network Using tdbsam passdb backend.

Installation of DHCP, DNS, and Samba Control Files

Carefully install the configuration files into the correct locations as shown in “Domain: MEGANET, File Locations for Servers”. You should validate that the full file path is correct as shown.

The abbreviation shown in this table as {VLN} refers to the directory location beginning with /var/lib/named. -

Table 4.1. Domain: MEGANET, File Locations for Servers

File InformationServer Name
SourceTarget LocationMASSIVEBLDG1BLDG2
“Server: MASSIVE (PDC), File: /etc/samba/smb.conf”/etc/samba/smb.confYesNoNo
“Server: MASSIVE (PDC), File: /etc/samba/dc-common.conf”/etc/samba/dc-common.confYesNoNo
“Common Samba Configuration File: /etc/samba/common.conf”/etc/samba/common.confYesYesYes
“Server: BLDG1 (Member), File: smb.conf”/etc/samba/smb.confNoYesNo
“Server: BLDG2 (Member), File: smb.conf”/etc/samba/smb.confNoNoYes
“Common Domain Member Include File: dom-mem.conf”/etc/samba/dommem.confNoYesYes
“Server: MASSIVE, File: dhcpd.conf”/etc/dhcpd.confYesNoNo
“Server: BLDG1, File: dhcpd.conf”/etc/dhcpd.confNoYesNo
“Server: BLDG2, File: dhcpd.conf”/etc/dhcpd.confNoNoYes
“Server: MASSIVE, File: named.conf, Part: A”/etc/named.conf (part A)YesNoNo
“Server: MASSIVE, File: named.conf, Part: B”/etc/named.conf (part B)YesNoNo
“Server: MASSIVE, File: named.conf, Part: C”/etc/named.conf (part C)YesNoNo
“Forward Zone File: abmas.biz.hosts”{VLN}/master/abmas.biz.hostsYesNoNo
“Forward Zone File: abmas.biz.hosts”{VLN}/master/abmas.us.hostsYesNoNo
“Servers: BLDG1/BLDG2, File: named.conf, Part: A”/etc/named.conf (part A)NoYesYes
“Servers: BLDG1/BLDG2, File: named.conf, Part: B”/etc/named.conf (part B)NoYesYes
“DNS Localhost Forward Zone File: /var/lib/named/localhost.zone”{VLN}/localhost.zoneYesYesYes
“DNS Localhost Reverse Zone File: /var/lib/named/127.0.0.zone”{VLN}/127.0.0.zoneYesYesYes
“DNS Root Name Server Hint File: /var/lib/named/root.hint”{VLN}/root.hintYesYesYes

Server Preparation: All Servers

+

Table 4.1. Domain: MEGANET, File Locations for Servers

File InformationServer Name
SourceTarget LocationMASSIVEBLDG1BLDG2
“Server: MASSIVE (PDC), File: /etc/samba/smb.conf”/etc/samba/smb.confYesNoNo
“Server: MASSIVE (PDC), File: /etc/samba/dc-common.conf”/etc/samba/dc-common.confYesNoNo
“Common Samba Configuration File: /etc/samba/common.conf”/etc/samba/common.confYesYesYes
“Server: BLDG1 (Member), File: smb.conf”/etc/samba/smb.confNoYesNo
“Server: BLDG2 (Member), File: smb.conf”/etc/samba/smb.confNoNoYes
“Common Domain Member Include File: dom-mem.conf”/etc/samba/dommem.confNoYesYes
“Server: MASSIVE, File: dhcpd.conf”/etc/dhcpd.confYesNoNo
“Server: BLDG1, File: dhcpd.conf”/etc/dhcpd.confNoYesNo
“Server: BLDG2, File: dhcpd.conf”/etc/dhcpd.confNoNoYes
“Server: MASSIVE, File: named.conf, Part: A”/etc/named.conf (part A)YesNoNo
“Server: MASSIVE, File: named.conf, Part: B”/etc/named.conf (part B)YesNoNo
“Server: MASSIVE, File: named.conf, Part: C”/etc/named.conf (part C)YesNoNo
“Forward Zone File: abmas.biz.hosts”{VLN}/master/abmas.biz.hostsYesNoNo
“Forward Zone File: abmas.biz.hosts”{VLN}/master/abmas.us.hostsYesNoNo
“Servers: BLDG1/BLDG2, File: named.conf, Part: A”/etc/named.conf (part A)NoYesYes
“Servers: BLDG1/BLDG2, File: named.conf, Part: B”/etc/named.conf (part B)NoYesYes
“DNS Localhost Forward Zone File: /var/lib/named/localhost.zone”{VLN}/localhost.zoneYesYesYes
“DNS Localhost Reverse Zone File: /var/lib/named/127.0.0.zone”{VLN}/127.0.0.zoneYesYesYes
“DNS Root Name Server Hint File: /var/lib/named/root.hint”{VLN}/root.hintYesYesYes

Server Preparation: All Servers

The following steps apply to all servers. Follow each step carefully. -

Procedure 4.1. Server Preparation Steps

  1. +

    Procedure 4.1. Server Preparation Steps

    1. Using the UNIX/Linux system tools, set the name of the server as shown in the network topology diagram in “Network Topology 500 User Network Using tdbsam passdb backend.”. For SUSE Linux products, the tool that permits this is called yast2; for Red Hat Linux products, @@ -220,17 +220,17 @@

       root#  hostname -f
       

      -

    2. - - +

    3. + + Edit your /etc/hosts file to include the primary names and addresses of all network interfaces that are on the host server. This is necessary so that during startup the system is able to resolve all its own names to the IP address prior to startup of the DNS server. You should check the startup order of your system. If the CUPS print server is started before the DNS server (named), you should also include an entry for the printers in the /etc/hosts file. -

    4. - +

    5. + All DNS name resolution should be handled locally. To ensure that the server is configured correctly to handle this, edit /etc/resolv.conf so it has the following content: @@ -240,9 +240,9 @@

      This instructs the name resolver function (when configured correctly) to ask the DNS server that is running locally to resolve names to addresses. -

    6. - - +

    7. + + Add the root user to the password backend:

       root#  smbpasswd -a root
      @@ -254,9 +254,9 @@
       			This account is essential in the regular maintenance of your Samba server. It must never be
       			deleted. If for any reason the account is deleted, you may not be able to recreate this account
       			without considerable trouble.
      -			

    8. - - +

    9. + + Create the username map file to permit the root account to be called Administrator from the Windows network environment. To do this, create the file /etc/samba/smbusers with the following contents: @@ -282,39 +282,39 @@ # End of File ####

      -

    10. +

    11. Configure all network-attached printers to have a fixed IP address. -

    12. +

    13. Create an entry in the DNS database on the server MASSIVE in both the forward lookup database for the zone abmas.biz.hosts and in the reverse lookup database for the network segment that the printer is located in. Example configuration files for similar zones were presented in “Secure Office Networking”, “DNS Abmas.biz Forward Zone File” and “DNS 192.168.2 Reverse Zone File”. -

    14. +

    15. Follow the instructions in the printer manufacturer's manuals to permit printing to port 9100. Use any other port the manufacturer specifies for direct mode, raw printing. This allows the CUPS spooler to print using raw mode protocols. - - -

    16. - + + +

    17. + Only on the server to which the printer is attached configure the CUPS Print Queues as follows:

       root#  lpadmin -p printque -v socket://printer-name.abmas.biz:9100 -E
       

      - + This step creates the necessary print queue to use no assigned print filter. This is ideal for raw printing, that is, printing without use of filters. The name printque is the name you have assigned for the particular printer. -

    18. +

    19. Print queues may not be enabled at creation. Make certain that the queues you have just created are enabled by executing the following:

       root#  /usr/bin/enable printque
       

      -

    20. +

    21. Even though your print queue may be enabled, it is still possible that it does not accept print jobs. A print queue services incoming printing requests only when configured to do so. Ensure that your print queue is @@ -322,10 +322,10 @@

       root#  /usr/bin/accept printque
       

      -

    22. - - - +

    23. + + + This step, as well as the next one, may be omitted where CUPS version 1.1.18 or later is in use. Although it does no harm to follow it anyway, and may help to avoid time spent later trying to figure out why print jobs may be @@ -335,41 +335,41 @@

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

      -

    24. - +

    25. + Edit the file /etc/cups/mime.types to uncomment the line:

       application/octet-stream
       

      -

    26. +

    27. Refer to the CUPS printing manual for instructions regarding how to configure CUPS so that print queues that reside on CUPS servers on remote networks route print jobs to the print server that owns that queue. The default setting on your CUPS server may automatically discover remotely installed printers and may permit this functionality without requiring specific configuration. -

    28. +

    29. As part of the roll-out program, you need to configure the application's server shares. This can be done once on the central server and may then be replicated using a tool such as rsync. Refer to the man page for rsync for details regarding use. The notes in “Application Share Configuration” may help in your decisions to use an application server facility. -

    Note

    +

Note

Logon scripts that are run from a domain controller (PDC or BDC) are capable of using semi-intelligent processes to automap Windows client drives to an application server that is nearest to the client. This is considerably more difficult when a single PDC is used on a routed network. It can be done, but not as elegantly as you see in the next chapter. -

Server-Specific Preparation

+

Server-Specific Preparation

There are some steps that apply to particular server functionality only. Each step is critical to correct server operation. The following step-by-step installation guidance will assist you in working through the process of configuring the PDC and then both BDC's. -

Configuration for Server: MASSIVE

+

Configuration for Server: MASSIVE

The steps presented here attempt to implement Samba installation in a generic manner. While some steps are clearly specific to Linux, it should not be too difficult to apply them to your platform of choice. -

Procedure 4.2. Primary Domain Controller Preparation

  1. - - +

    Procedure 4.2. Primary Domain Controller Preparation

    1. + + The host server acts as a router between the two internal network segments as well as for all Internet access. This necessitates that IP forwarding be enabled. This can be achieved by adding to the /etc/rc.d/boot.local an entry as follows: @@ -378,7 +378,7 @@

      To ensure that your kernel is capable of IP forwarding during configuration, you may wish to execute that command manually also. This setting permits the Linux system to act as a router. -

    2. +

    3. This server is dual hosted (i.e., has two network interfaces) one goes to the Internet and the other to a local network that has a router that is the gateway to the remote networks. You must therefore configure the server with route table entries so that it can find machines @@ -396,46 +396,46 @@ not persistent across system reboots. You may add these commands directly to the local startup files as follows: (SUSE) /etc/rc.d/boot.local, (Red Hat) /etc/rc.d/init.d/rc.local. -

    4. - +

    5. + The final step that must be completed is to edit the /etc/nsswitch.conf file. This file controls the operation of the various resolver libraries that are part of the Linux Glibc libraries. Edit this file so that it contains the following entries:

       hosts:      files dns wins
       

      -

    6. - +

    7. + Create and map Windows domain groups to UNIX groups. A sample script is provided in “Initialize Groups Script, File: /etc/samba/initGrps.sh”. Create a file containing this script. You called yours /etc/samba/initGrps.sh. Set this file so it can be executed and then execute the script. An example of the execution of this script as well as its validation are shown in Section 4.3.2, Step 5. -

    8. - - - +

    9. + + + For each user who needs to be given a Windows domain account, make an entry in the /etc/passwd file as well as in the Samba password backend. Use the system tool of your choice to create the UNIX system account, and use the Samba smbpasswd to create a domain user account.

      - - - + + + There are a number of tools for user management under UNIX, such as useradd, adduser, as well as a plethora of custom tools. With the tool of your choice, create a home directory for each user. -

    10. +

    11. Using the preferred tool for your UNIX system, add each user to the UNIX groups created previously as necessary. File system access control is based on UNIX group membership. -

    12. +

    13. Create the directory mount point for the disk subsystem that is to be mounted to provide data storage for company files, in this case, the mount point indicated in the smb.conf file is /data. Format the file system as required and mount the formatted file system partition using appropriate system tools. -

    14. - +

    15. + Create the top-level file storage directories for data and applications as follows:

       root#  mkdir -p /data/{accounts,finsvcs,pidata}
      @@ -453,7 +453,7 @@
       			The directory root of the finsvcs share is /data/finsvcs.
       			The /apps directory is the root of the apps share
       			that provides the application server infrastructure.
      -			

    16. +

    17. The smb.conf file specifies an infrastructure to support roaming profiles and network logon services. You can now create the file system infrastructure to provide the locations on disk that these services require. Adequate planning is essential @@ -474,9 +474,9 @@ root# chown 'username':users /var/lib/samba/profiles/'username' root# chmod ug+wrx,o+rx,-w /var/lib/samba/profiles/'username'

      -

    18. - - +

    19. + + Create a logon script. It is important that each line is correctly terminated with a carriage return and line-feed combination (i.e., DOS encoding). The following procedure works if the right tools (unxi2dos and dos2unix) are installed. @@ -491,7 +491,7 @@ root# dos2unix < /var/lib/samba/netlogon/scripts/logon.bat.unix \ > /var/lib/samba/netlogon/scripts/logon.bat

      -

    20. +

    21. There is one preparatory step without which you cannot have a working Samba network environment. You must add an account for each network user. You can do this by executing the following steps for each user: @@ -508,18 +508,18 @@ Added user username.

      You do, of course, use a valid user login ID in place of username. -

    22. +

    23. Follow the processes shown in “Process Startup Configuration” to start all services. -

    24. +

    25. Your server is ready for validation testing. Do not proceed with the steps in “Configuration Specific to Domain Member Servers: BLDG1, BLDG2” until after the operation of the server has been validated following the same methods as outlined in “Secure Office Networking”, “Validation”. -

Configuration Specific to Domain Member Servers: BLDG1, BLDG2

+

Configuration Specific to Domain Member Servers: BLDG1, BLDG2

The following steps will guide you through the nuances of implementing BDCs for the broadcast isolated network segments. Remember that if the target installation platform is not Linux, it may be necessary to adapt some commands to the equivalent on the target platform. -

Procedure 4.3. Backup Domain Controller Configuration Steps

  1. - +

    Procedure 4.3. Backup Domain Controller Configuration Steps

    1. + The final step that must be completed is to edit the /etc/nsswitch.conf file. This file controls the operation of the various resolver libraries that are part of the Linux Glibc libraries. Edit this file so that it contains the following entries: @@ -528,27 +528,27 @@ group: files winbind hosts: files dns wins

      -

    2. +

    3. Follow the steps outlined in “Process Startup Configuration” to start all services. Do not start Samba at this time. Samba is controlled by the process called smb. -

    4. - +

    5. + You must now attempt to join the domain member servers to the domain. The following instructions should be executed to effect this:

       root#  net rpc join 
       

      -

    6. - +

    7. + You now start the Samba services by executing:

       root#  service smb start
       

      -

    8. +

    9. Your server is ready for validation testing. Do not proceed with the steps in “Configuration Specific to Domain Member Servers: BLDG1, BLDG2” until after the operation of the server has been validated following the same methods as outlined in “Validation”. -

Example 4.1. Server: MASSIVE (PDC), File: /etc/samba/smb.conf

# Global parameters
[global]
workgroup = MEGANET
netbios name = MASSIVE
interfaces = eth1, lo
bind interfaces only = Yes
passdb backend = tdbsam
smb ports = 139
add user script = /usr/sbin/useradd -m '%u'
delete user script = /usr/sbin/userdel -r '%u'
add group script = /usr/sbin/groupadd '%g'
delete group script = /usr/sbin/groupdel '%g'
add user to group script = /usr/sbin/usermod -G '%g' '%u'
add machine script = /usr/sbin/useradd -s /bin/false -d /var/lib/nobody '%u'
preferred master = Yes
wins support = Yes
include = /etc/samba/dc-common.conf
[accounts]
comment = Accounting Files
path = /data/accounts
read only = No
[service]
comment = Financial Services Files
path = /data/service
read only = No
[pidata]
comment = Property Insurance Files
path = /data/pidata
read only = No

Example 4.2. Server: MASSIVE (PDC), File: /etc/samba/dc-common.conf

# Global parameters
[global]
shutdown script = /var/lib/samba/scripts/shutdown.sh
abort shutdown script = /sbin/shutdown -c
logon script = scripts\logon.bat
logon path = \%L\profiles\%U
logon drive = X:
logon home = \%L\%U
domain logons = Yes
preferred master = Yes
include = /etc/samba/common.conf
[homes]
comment = Home Directories
valid users = %S
read only = No
browseable = No
[netlogon]
comment = Network Logon Service
path = /var/lib/samba/netlogon
guest ok = Yes
locking = No
[profiles]
comment = Profile Share
path = /var/lib/samba/profiles
read only = No
profile acls = Yes

Example 4.3. Common Samba Configuration File: /etc/samba/common.conf

[global]
username map = /etc/samba/smbusers
log level = 1
syslog = 0
log file = /var/log/samba/%m
max log size = 50
smb ports = 139
name resolve order = wins bcast hosts
time server = Yes
printcap name = CUPS
show add printer wizard = No
shutdown script = /var/lib/samba/scripts/shutdown.sh
abort shutdown script = /sbin/shutdown -c
utmp = Yes
map acl inherit = Yes
printing = cups
veto files = /*.eml/*.nws/*.{*}/
veto oplock files = /*.doc/*.xls/*.mdb/
include =
# Share and Service Definitions are common to all servers
[printers]
comment = SMB Print Spool
path = /var/spool/samba
guest ok = Yes
printable = Yes
use client driver = Yes
default devmode = Yes
browseable = No
[apps]
comment = Application Files
path = /apps
admin users = bjordan
read only = No

Example 4.4. Server: BLDG1 (Member), File: smb.conf

# Global parameters
[global]
workgroup = MEGANET
netbios name = BLDG1
include = /etc/samba/dom-mem.conf

Example 4.5. Server: BLDG2 (Member), File: smb.conf

# Global parameters
[global]
workgroup = MEGANET
netbios name = BLDG2
include = /etc/samba/dom-mem.conf

Example 4.6. Common Domain Member Include File: dom-mem.conf

# Global parameters
[global]
shutdown script = /var/lib/samba/scripts/shutdown.sh
abort shutdown script = /sbin/shutdown -c
preferred master = Yes
wins server = 172.16.0.1
idmap uid = 15000-20000
idmap gid = 15000-20000
include = /etc/samba/common.conf

Example 4.7. Server: MASSIVE, File: dhcpd.conf

+                        

Example 4.1. Server: MASSIVE (PDC), File: /etc/samba/smb.conf

# Global parameters
[global]
workgroup = MEGANET
netbios name = MASSIVE
interfaces = eth1, lo
bind interfaces only = Yes
passdb backend = tdbsam
smb ports = 139
add user script = /usr/sbin/useradd -m '%u'
delete user script = /usr/sbin/userdel -r '%u'
add group script = /usr/sbin/groupadd '%g'
delete group script = /usr/sbin/groupdel '%g'
add user to group script = /usr/sbin/usermod -G '%g' '%u'
add machine script = /usr/sbin/useradd -s /bin/false -d /var/lib/nobody '%u'
preferred master = Yes
wins support = Yes
include = /etc/samba/dc-common.conf
[accounts]
comment = Accounting Files
path = /data/accounts
read only = No
[service]
comment = Financial Services Files
path = /data/service
read only = No
[pidata]
comment = Property Insurance Files
path = /data/pidata
read only = No

Example 4.2. Server: MASSIVE (PDC), File: /etc/samba/dc-common.conf

# Global parameters
[global]
shutdown script = /var/lib/samba/scripts/shutdown.sh
abort shutdown script = /sbin/shutdown -c
logon script = scripts\logon.bat
logon path = \%L\profiles\%U
logon drive = X:
logon home = \%L\%U
domain logons = Yes
preferred master = Yes
include = /etc/samba/common.conf
[homes]
comment = Home Directories
valid users = %S
read only = No
browseable = No
[netlogon]
comment = Network Logon Service
path = /var/lib/samba/netlogon
guest ok = Yes
locking = No
[profiles]
comment = Profile Share
path = /var/lib/samba/profiles
read only = No
profile acls = Yes

Example 4.3. Common Samba Configuration File: /etc/samba/common.conf

[global]
username map = /etc/samba/smbusers
log level = 1
syslog = 0
log file = /var/log/samba/%m
max log size = 50
smb ports = 139
name resolve order = wins bcast hosts
time server = Yes
printcap name = CUPS
show add printer wizard = No
shutdown script = /var/lib/samba/scripts/shutdown.sh
abort shutdown script = /sbin/shutdown -c
utmp = Yes
map acl inherit = Yes
printing = cups
veto files = /*.eml/*.nws/*.{*}/
veto oplock files = /*.doc/*.xls/*.mdb/
include =
# Share and Service Definitions are common to all servers
[printers]
comment = SMB Print Spool
path = /var/spool/samba
guest ok = Yes
printable = Yes
use client driver = Yes
default devmode = Yes
browseable = No
[apps]
comment = Application Files
path = /apps
admin users = bjordan
read only = No

Example 4.4. Server: BLDG1 (Member), File: smb.conf

# Global parameters
[global]
workgroup = MEGANET
netbios name = BLDG1
include = /etc/samba/dom-mem.conf

Example 4.5. Server: BLDG2 (Member), File: smb.conf

# Global parameters
[global]
workgroup = MEGANET
netbios name = BLDG2
include = /etc/samba/dom-mem.conf

Example 4.6. Common Domain Member Include File: dom-mem.conf

# Global parameters
[global]
shutdown script = /var/lib/samba/scripts/shutdown.sh
abort shutdown script = /sbin/shutdown -c
preferred master = Yes
wins server = 172.16.0.1
idmap uid = 15000-20000
idmap gid = 15000-20000
include = /etc/samba/common.conf

Example 4.7. Server: MASSIVE, File: dhcpd.conf

 # Abmas Accounting Inc.
 
 default-lease-time 86400;
@@ -897,9 +897,9 @@
 net groupmap add ntgroup="Accounts Dept"       unixgroup=acctsdep type=d
 net groupmap add ntgroup="Financial Services"  unixgroup=finsrvcs type=d
 net groupmap add ntgroup="Insurance Group"     unixgroup=piops type=d
-

Process Startup Configuration

- - +


Process Startup Configuration

+ + There are two essential steps to process startup configuration. A process must be configured so that it is automatically restarted each time the server is rebooted. This step involves use of the chkconfig tool that @@ -908,7 +908,7 @@ directories. Links are created so that when the system run-level is changed, the necessary start or kill script is run.

- + In the event that a service is provided not as a daemon but via the internetworking super daemon (inetd or xinetd), then the chkconfig tool makes the necessary entries in the /etc/xinetd.d directory @@ -918,10 +918,10 @@ Last, each service must be started to permit system validation to proceed. The following steps are for a Red Hat Linux system, please adapt them to suit the target OS platform on which you are installing Samba. -

Procedure 4.4. Process Startup Configuration Steps

  1. +

    Procedure 4.4. Process Startup Configuration Steps

    1. Use the standard system tool to configure each service to restart automatically at every system reboot. For example, - +

       root#  chkconfig dhpc on
       root#  chkconfig named on
      @@ -929,10 +929,10 @@
       root#  chkconfig smb on
       root#  chkconfig swat on
       

      -

    2. - - - +

    3. + + + Now start each service to permit the system to be validated. Execute each of the following in the sequence shown: @@ -943,70 +943,70 @@ root# service smb restart root# service swat restart

      -

Windows Client Configuration

+

Windows Client Configuration

The procedure for desktop client configuration for the network in this chapter is similar to that used for the previous one. There are a few subtle changes that should be noted. -

Procedure 4.5. Windows Client Configuration Steps

  1. +

    Procedure 4.5. Windows Client Configuration Steps

    1. Install MS Windows XP Professional. During installation, configure the client to use DHCP for TCP/IP protocol configuration. - - + + DHCP configures all Windows clients to use the WINS Server address that has been defined for the local subnet. -

    2. +

    3. Join the Windows domain MEGANET. Use the domain administrator username root and the SMB password you assigned to this account. A detailed step-by-step procedure for joining a Windows 200x/XP Professional client to a Windows domain is given in “A Collection of Useful Tidbits”, “Joining a Domain: Windows 200x/XP Professional”. Reboot the machine as prompted and then log on using the domain administrator account (root). -

    4. +

    5. Verify that the server called MEGANET is visible in My Network Places, that it is possible to connect to it and see the shares accounts, apps, and finsvcs, and that it is possible to open each share to reveal its contents. -

    6. +

    7. Create a drive mapping to the apps share on a server. At this time, it does not particularly matter which application server is used. It is necessary to manually set a persistent drive mapping to the local applications server on each workstation at the time of installation. This step is avoided by the improvements to the design of the network configuration in the next chapter. -

    8. +

    9. Perform an administrative installation of each application to be used. Select the options that you wish to use. Of course, you choose to run applications over the network, correct? -

    10. +

    11. Now install all applications to be installed locally. Typical tools include Adobe Acrobat, NTP-based time synchronization software, drivers for specific local devices such as fingerprint scanners, and the like. Probably the most significant application to be locally installed is antivirus software. -

    12. +

    13. Now install all four printers onto the staging system. The printers you install include the accounting department HP LaserJet 6 and Minolta QMS Magicolor printers, and you also configure use of the identical printers that are located in the financial services department. Install printers on each machine using the following steps: -

      Procedure 4.6. Steps to Install Printer Drivers on Windows Clients

      1. +

        Procedure 4.6. Steps to Install Printer Drivers on Windows Clients

        1. Click StartSettingsPrinters+Add Printer+Next. Do not click Network printer. Ensure that Local printer is selected. -

        2. +

        3. Click Next. In the Manufacturer: panel, select HP. In the Printers: panel, select the printer called HP LaserJet 6. Click Next. -

        4. +

        5. In the Available ports: panel, select FILE:. Accept the default printer name by clicking - Next. When asked, Would you like to print a - test page?, click No. Click + Next. When asked, “Would you like to print a + test page?”, click No. Click Finish. -

        6. +

        7. You may be prompted for the name of a file to print to. If so, close the dialog panel. Right-click HP LaserJet 6Properties. -

        8. +

        9. In the Network panel, enter the name of the print queue on the Samba server as follows: \\BLDG1\hplj6a. Click OK+OK to complete the installation. -

        10. +

        11. Repeat the printer installation steps above for both HP LaserJet 6 printers as well as for both QMS Magicolor laser printers. Remember to install all printers but to set the destination port for each to the server on the @@ -1018,69 +1018,69 @@ configuration (as well as the applications server drive mapping) to the server on the network segment on which the workstation is to be located.

        -

      2. +

      3. When you are satisfied that the staging systems are complete, use the appropriate procedure to remove the client from the domain. Reboot the system, and then log on as the local administrator and clean out all temporary files stored on the system. Before shutting down, use the disk defragmentation tool so that the file system is in optimal condition before replication. -

      4. +

      5. Boot the workstation using the Norton (Symantec) Ghosting disk (or CD-ROM) and image the machine to a network share on the server. -

      6. +

      7. You may now replicate the image using the appropriate Norton Ghost procedure to the target machines. Make sure to use the procedure that ensures each machine has a unique Windows security identifier (SID). When the installation of the disk image is complete, boot the PC. -

      8. +

      9. Log onto the machine as the local Administrator (the only option), and join the machine to the domain following the procedure set out in “A Collection of Useful Tidbits”, “Joining a Domain: Windows 200x/XP Professional”. You must now set the persistent drive mapping to the applications server that the user is to use. The system is now ready for the user to log on, provided you have created a network logon account for that user, of course. -

      10. +

      11. Instruct all users to log onto the workstation using their assigned username and password. -

    Key Points Learned

    +

Key Points Learned

The network you have just deployed has been a valuable exercise in forced constraint. You have deployed a network that works well, although you may soon start to see performance problems, at which time the modifications demonstrated in “Making Happy Users” bring the network to life. The following key learning points were experienced: -

  • +

    • The power of using smb.conf include files -

    • +

    • Use of a single PDC over a routed network -

    • +

    • Joining a Samba-3 domain member server to a Samba-3 domain -

    • +

    • Configuration of winbind to use domain users and groups for Samba access to resources on the domain member servers -

    • +

    • The introduction of roaming profiles -

Questions and Answers

-

Questions and Answers

+

The example smb.conf files in this chapter make use of the include facility. How may I get to see what the actual working smb.conf settings are? -
+
Why does the include file common.conf have an empty include statement? -
+
I accept that the simplest configuration necessary to do the job is the best. The use of tdbsam passdb backend is much simpler than having to manage an LDAP-based ldapsam passdb backend. I tried using rsync to replicate the passdb.tdb, and it seems to work fine! So what is the problem? -
+
You are using DHCP Relay enabled on the routers as well as a local DHCP server. Will this cause a clash? -
+
How does the Windows client find the PDC? -
+
Why did you enable IP forwarding (routing) only on the server called MASSIVE? -
+
You did nothing special to implement roaming profiles. Why? -
+
On the domain member computers, you configured winbind in the /etc/nsswitch.conf file. You did not configure any PAM settings. Is this an omission? -
+
You are starting SWAT up on this example but have not discussed that anywhere. Why did you do this? -
+
The domain controller has an auto-shutdown script. Isn't that dangerous? -

+

The example smb.conf files in this chapter make use of the include facility. How may I get to see what the actual working smb.conf settings are?

@@ -1088,7 +1088,7 @@

 root#  testparm -s | less
 

-

+

Why does the include file common.conf have an empty include statement?

The use of the empty include statement nullifies further includes. For example, let's say you @@ -1101,7 +1101,7 @@ If the include parameter was not in the common.conf file, the final smb.conf file leaves the include in place, even though the file it points to has already been included. This is a bug that will be fixed at a future date. -

+

I accept that the simplest configuration necessary to do the job is the best. The use of tdbsam passdb backend is much simpler than having to manage an LDAP-based ldapsam passdb backend. I tried using rsync to replicate the passdb.tdb, and it seems to work fine! @@ -1111,7 +1111,7 @@ contents between the PDC and BDCs. The most notable symptom is that workstations may not be able to log onto the network following a reboot and may have to rejoin the domain to recover network access capability. -

+

You are using DHCP Relay enabled on the routers as well as a local DHCP server. Will this cause a clash?

No. It is possible to have as many DHCP servers on a network segment as makes sense. A DHCP server @@ -1120,26 +1120,26 @@

The only exception to this rule is when the client makes a directed request from a specific DHCP server for renewal of the lease it has. This means that under normal circumstances there is no risk of a clash. -

+

How does the Windows client find the PDC?

The Windows client obtains the WINS server address from the DHCP lease information. It also obtains from the DHCP lease information the parameter that causes it to use directed UDP (UDP Unicast) to register itself with the WINS server and to obtain enumeration of vital network information to enable it to operate successfully. -

+

Why did you enable IP forwarding (routing) only on the server called MASSIVE?

The server called MASSIVE is acting as a router to the Internet. No other server (BLDG1 or BLDG2) has any need for IP forwarding because they are attached only to their own network. Route table entries are needed to direct MASSIVE to send all traffic intended for the remote network segments to the router that is its gateway to them. -

+

You did nothing special to implement roaming profiles. Why?

Unless configured to do otherwise, the default behavior with Samba-3 and Windows XP Professional clients is to use roaming profiles. -

+

On the domain member computers, you configured winbind in the /etc/nsswitch.conf file. You did not configure any PAM settings. Is this an omission?

@@ -1148,7 +1148,7 @@ member servers using Windows networking usernames and passwords, it is necessary to configure PAM to enable the use of winbind. Samba makes use only of the identity resolution facilities of the name service switch (NSS). -

+

You are starting SWAT up on this example but have not discussed that anywhere. Why did you do this?

Oh, I did not think you would notice that. It is there so that it can be used. This is more fully discussed @@ -1157,7 +1157,7 @@ of smb.conf include files because SWAT optimizes them out into an aggregated file but leaves in place a broken reference to the top-layer include file. SWAT was not designed to handle this functionality gracefully. -

+

The domain controller has an auto-shutdown script. Isn't that dangerous?

Well done, you spotted that! I guess it is dangerous. It is good to know that you can do this, though. diff -u -r --new-file --exclude .svn --exclude CVS samba-3.3.10//docs/htmldocs/Samba3-ByExample/ch14.html samba-3.3.11//docs/htmldocs/Samba3-ByExample/ch14.html --- samba-3.3.10//docs/htmldocs/Samba3-ByExample/ch14.html 2010-01-14 11:24:24.000000000 +0100 +++ samba-3.3.11//docs/htmldocs/Samba3-ByExample/ch14.html 2010-02-22 16:53:36.000000000 +0100 @@ -1,12 +1,12 @@ -Chapter 14. Samba Support

Chapter 14. Samba Support

- -One of the most difficult to answer questions in the information technology industry is, What is -support?. That question irritates some folks, as much as common answers may annoy others. +Chapter 14. Samba Support

Chapter 14. Samba Support

+ +One of the most difficult to answer questions in the information technology industry is, “What is +support?”. That question irritates some folks, as much as common answers may annoy others.

- + The most aggravating situation pertaining to support is typified when, as a Linux user, a call is made to an Internet service provider who, instead of listening to the problem to find a solution, blandly replies: -Oh, Linux? We do not support Linux!. It has happened to me, and similar situations happen +“Oh, Linux? We do not support Linux!”. It has happened to me, and similar situations happen through-out the IT industry. Answers like that are designed to inform us that there are some customers that a business just does not want to deal with, and well may we feel the anguish of the rejection that is dished out. @@ -15,50 +15,50 @@ at the right time, no matter the situation. Support is all that it takes to take away pain, disruption, inconvenience, loss of productivity, disorientation, uncertainty, and real or perceived risk.

- - - + + + One of the forces that has become a driving force for the adoption of open source software is the fact that many IT businesses have provided services that have perhaps failed to deliver what the customer expected, or that have been found wanting for other reasons.

- - + + In recognition of the need for needs satisfaction as the primary experience an information technology user or consumer expects, the information provided in this chapter may help someone to avoid an unpleasant experience in respect of problem resolution.

- - - + + + In the open source software arena there are two support options: free support and paid-for (commercial) support. -

Free Support

- - - - - - +

Free Support

+ + + + + + Free support may be obtained from friends, colleagues, user groups, mailing lists, and interactive help facilities. An example of an interactive dacility is the Internet relay chat (IRC) channels that host user supported mutual assistance.

- - - - - + + + + + The Samba project maintains a mailing list that is commonly used to discuss solutions to Samba deployments. Information regarding subscription to the Samba mailing list can be found on the Samba web site. The public mailing list that can be used to obtain free, user contributed, support is called the samba list. The email address for this list is at mail:samba@samba.org. Information regarding the Samba IRC channels may be found on the Samba IRC web page.

- - - - + + + + As a general rule, it is considered poor net behavior to contact a Samba Team member directly for free support. Most active members of the Samba Team work exceptionally long hours to assist users who have demonstrated a qualified problem. Some team members may respond to direct email @@ -66,9 +66,9 @@ Team members actually provide professional paid-for Samba support and it is therefore wise to show appropriate discretion and reservation in all direct contact.

- - - + + + When you stumble across a Samba bug, often the quickest way to get it resolved is by posting a bug report. All such reports are mailed to the responsible code maintainer for action. The better the report, and the more serious it is, @@ -76,16 +76,16 @@ the reported bug it is likely to be rejected. It is up to you to provide sufficient information that will permit the problem to be reproduced.

- + We all recognize that sometimes free support does not provide the answer that is sought within the time-frame required. At other times the problem is elusive and you may lack the experience necessary to isolate the problem and thus to resolve it. This is a situation where is may be prudent to purchase paid-for support. -

Commercial Support

+

Commercial Support

There are six basic support oriented services that are most commonly sought by Samba sites: -

  • Assistance with network design

  • Staff Training

  • Assistance with Samba network deployment and installation

  • Priority telephone or email Samba configuration assistance

  • Trouble-shooting and diagnostic assistance

  • Provision of quality assured ready-to-install Samba binary packages

- - +

  • Assistance with network design

  • Staff Training

  • Assistance with Samba network deployment and installation

  • Priority telephone or email Samba configuration assistance

  • Trouble-shooting and diagnostic assistance

  • Provision of quality assured ready-to-install Samba binary packages

+ + Information regarding companies that provide professional Samba support can be obtained by performing a Google search, as well as by reference to the Samba Support web page. Companies who notify the Samba Team that they provide commercial support are given a free listing that is sorted by the country of origin. @@ -93,13 +93,13 @@ provider and to satisfy yourself that both the company and its staff are able to deliver what is required of them.

- + The policy within the Samba Team is to treat all commercial support providers equally and to show no preference. As a result, Samba Team members who provide commercial support are lumped in with everyone else. You are encouraged to obtain the services needed from a company in your local area. The open source movement is pro-community; so do what you can to help a local business to prosper.

- + Open source software support can be found in any quality, at any price and in any place you can to obtain it. Over 180 companies around the world provide Samba support, there is no excuse for suffering in the mistaken belief that Samba is unsupported software it is supported. diff -u -r --new-file --exclude .svn --exclude CVS samba-3.3.10//docs/htmldocs/Samba3-ByExample/DMSMig.html samba-3.3.11//docs/htmldocs/Samba3-ByExample/DMSMig.html --- samba-3.3.10//docs/htmldocs/Samba3-ByExample/DMSMig.html 2010-01-14 11:24:20.000000000 +0100 +++ samba-3.3.11//docs/htmldocs/Samba3-ByExample/DMSMig.html 2010-02-22 16:53:36.000000000 +0100 @@ -1,4 +1,4 @@ -Part II. Domain Members, Updating Samba and Migration

Part II. Domain Members, Updating Samba and Migration

Domain Members, Updating Samba and Migration

+Part II. Domain Members, Updating Samba and Migration

Part II. Domain Members, Updating Samba and Migration

Domain Members, Updating Samba and Migration

This section Samba-3 by Example covers two main topics: How to add Samba Domain Member Servers and Samba Domain Member Clients to a Samba domain, the other subject is that of how to migrate from and NT4 Domain, a NetWare server, or from an earlier @@ -7,4 +7,4 @@ Those who are making use of the chapter on Adding UNIX clients and servers running Samba to a Samba or a Windows networking domain may also benefit by referring to the book The Official Samba-3 HOWTO and Reference Guide. -

+

diff -u -r --new-file --exclude .svn --exclude CVS samba-3.3.10//docs/htmldocs/Samba3-ByExample/DomApps.html samba-3.3.11//docs/htmldocs/Samba3-ByExample/DomApps.html --- samba-3.3.10//docs/htmldocs/Samba3-ByExample/DomApps.html 2010-01-14 11:24:23.000000000 +0100 +++ samba-3.3.11//docs/htmldocs/Samba3-ByExample/DomApps.html 2010-02-22 16:53:36.000000000 +0100 @@ -1,9 +1,9 @@ -Chapter 12. Integrating Additional Services

Chapter 12. Integrating Additional Services

- - - - - +Chapter 12. Integrating Additional Services

Chapter 12. Integrating Additional Services

+ + + + + You've come a long way now. You have pretty much mastered Samba-3 for most uses it can be put to. Up until now, you have cast Samba-3 in the leading role, and where authentication was required, you have used one or another of @@ -14,7 +14,7 @@ implementing Samba and Samba-supported services in a domain controlled by the latest Windows authentication technologies. Let's get started this is leading edge. -

Introduction

+

Introduction

Abmas has continued its miraculous growth; indeed, nothing seems to be able to stop its diversification into multiple (and seemingly unrelated) fields. Its latest acquisition is Abmas Snack Foods, a big player in the snack-food @@ -30,17 +30,17 @@ You have decided to set the ball rolling by introducing Samba-3 into the network gradually, taking over key services and easing the way to a full migration and, therefore, integration into Abmas's existing business later. -

Assignment Tasks

- - +

Assignment Tasks

+ + You've promised the skeptical Abmas Snack Foods management team that you can show them how Samba can ease itself and other Open Source technologies into their existing infrastructure and deliver sound business advantages. Cost cutting is high on their agenda (a major promise of the acquisition). You have chosen Web proxying and caching as your proving ground.

- - + + Abmas Snack Foods has several thousand users housed at its head office and multiple regional offices, plants, and warehouses. A high proportion of the business's work is done online, so Internet access for most of these @@ -50,9 +50,9 @@ the team soon discovered proxying and caching. In fact, they became one of the earliest commercial users of Microsoft ISA.

- - - + + + The team is not happy with ISA. Because it never lived up to its marketing promises, it underperformed and had reliability problems. You have pounced on the opportunity to show what Open Source can do. The one thing they do like, however, is ISA's @@ -63,30 +63,30 @@

This is a hands-on exercise. You build software applications so that you obtain the functionality Abmas needs. -

Dissection and Discussion

+

Dissection and Discussion

The key requirements in this business example are straightforward. You are not required to do anything new, just to replicate an existing system, not lose any existing features, and improve performance. The key points are: -

  • +

    • Internet access for most employees -

    • +

    • Distributed system to accommodate load and geographical distribution of users -

    • +

    • Seamless and transparent interoperability with the existing Active Directory domain -

    Technical Issues

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

Technical Issues

+ + + + + + + + + + + + + Functionally, the user's Internet Explorer requests a browsing session with the Squid proxy, for which it offers its AD authentication token. Squid hands off the authentication request to the Samba-3 authentication helper application @@ -99,79 +99,79 @@ This process is entirely transparent and seamless to the user.

Enabling this consists of: -

  • +

    • Preparing the necessary environment using preconfigured packages -

    • +

    • Setting up raw Kerberos authentication against the Active Directory domain -

    • +

    • Configuring, compiling, and then installing the supporting Samba-3 components -

    • +

    • Tying it all together -

Political Issues

+

Political Issues

You are a stranger in a strange land, and all eyes are upon you. Some would even like to see you fail. For you to gain the trust of your newly acquired IT people, it is essential that your solution does everything the old one did, but does it better in every way. Only then will the entrenched positions consider taking up your new way of doing things on a wider scale. -

Implementation

- +

Implementation

+ First, your system needs to be prepared and in a known good state to proceed. This consists of making sure that everything the system depends on is present and that everything that could interfere or conflict with the system is removed. You will be configuring the Squid and Samba-3 packages and updating them if necessary. If conflicting packages of these programs are installed, they must be removed.

- + The following packages should be available on your Red Hat Linux system: -

  • - - +

    • + + krb5-libs -

    • +

    • krb5-devel -

    • +

    • krb5-workstation -

    • +

    • krb5-server -

    • +

    • pam_krb5

    - + In the case of SUSE Linux, these packages are called: -

    • +

      • heimdal-lib -

      • +

      • heimdal-devel -

      • - +

      • + heimdal -

      • +

      • pam_krb5

      If the required packages are not present on your system, you must install them from the vendor's installation media. Follow the administrative guide for your Linux system to ensure that the packages are correctly updated. -

      Note

      - - - +

      Note

      + + + If the requirement is for interoperation with MS Windows Server 2003, it will be necessary to ensure that you are using MIT Kerberos version 1.3.1 or later. Red Hat Linux 9 ships with MIT Kerberos 1.2.7 and thus requires updating.

      - - + + Heimdal 0.6 or later is required in the case of SUSE Linux. SUSE Enterprise Linux Server 8 ships with Heimdal 0.4. SUSE 9 ships with the necessary version. -

      Removal of Pre-Existing Conflicting RPMs

      - +

      Removal of Pre-Existing Conflicting RPMs

      + If Samba and/or Squid RPMs are installed, they should be updated. You can build both from source.

      - - - + + + Locating the packages to be un-installed can be achieved by running:

       root#  rpm -qa | grep -i samba
      @@ -181,11 +181,11 @@
       

       root#  rpm -e samba-common
       

      -

      Kerberos Configuration

      - - - - +

      Kerberos Configuration

      + + + + The systems Kerberos installation must be configured to communicate with your primary Active Directory server (ADS KDC).

      @@ -193,13 +193,13 @@ although the current default Red Hat MIT version 1.2.7 gives acceptable results unless you are using Windows 2003 servers.

      - - - - - - - + + + + + + + Officially, neither MIT (1.3.4) nor Heimdal (0.63) Kerberos needs an /etc/krb5.conf file in order to work correctly. All ADS domains automatically create SRV records in the DNS zone Kerberos.REALM.NAME for each KDC in the realm. Since both @@ -207,30 +207,30 @@ automatically find the KDCs. In addition, krb5.conf allows specifying only a single KDC, even if there is more than one. Using the DNS lookup allows the KRB5 libraries to use whichever KDCs are available. -

      Procedure 12.1. Kerberos Configuration Steps

      1. - +

        Procedure 12.1. Kerberos Configuration Steps

        1. + If you find the need to manually configure the krb5.conf, you should edit it to have the contents shown in “Kerberos Configuration File: /etc/krb5.conf”. The final fully qualified path for this file should be /etc/krb5.conf. -

        2. - - - - - - - - - - - - - +

        3. + + + + + + + + + + + + + The following gotchas often catch people out. Kerberos is case sensitive. Your realm must - be in UPPERCASE, or you will get an error: Cannot find KDC for requested realm while getting - initial credentials. Kerberos is picky about time synchronization. The time + be in UPPERCASE, or you will get an error: “Cannot find KDC for requested realm while getting + initial credentials”. Kerberos is picky about time synchronization. The time according to your participating servers must be within 5 minutes or you get an error: - kinit(v5): Clock skew too great while getting initial credentials. + “kinit(v5): Clock skew too great while getting initial credentials”. Clock skew limits are, in fact, configurable in the Kerberos protocols (the default is 5 minutes). A better solution is to implement NTP throughout your server network. Kerberos needs to be able to do a reverse DNS lookup on the IP address of your KDC. @@ -240,8 +240,8 @@ /etc/hosts entry mapping the IP address of your KDC to its NetBIOS name. If Kerberos cannot do this reverse lookup, you will get a local error when you try to join the realm. -

        4. - +

        5. + You are now ready to test your installation by issuing the command:

           root#  kinit [USERNAME@REALM]
          @@ -261,57 +261,57 @@
           	LONDON.ABMAS.BIZ = {
           	kdc = w2k3s.london.abmas.biz
           	}
          -

      +


      The command

       root#  klist -e 
       

      shows the Kerberos tickets cached by the system. -

      Samba Configuration

      - +

      Samba Configuration

      + Samba must be configured to correctly use Active Directory. Samba-3 must be used, since it has the necessary components to interface with Active Directory. -

      Procedure 12.2. Securing Samba-3 With ADS Support Steps

      1. - - - - - +

        Procedure 12.2. Securing Samba-3 With ADS Support Steps

        1. + + + + + Download the latest stable Samba-3 for Red Hat Linux from the official Samba Team FTP site. The official Samba Team RPMs for Red Hat Fedora Linux contain the ntlm_auth tool needed, and are linked against MIT KRB5 version 1.3.1 and therefore are ready for use.

          - - + + The necessary, validated RPM packages for SUSE Linux may be obtained from the SerNet FTP site that is located in Germany. All SerNet RPMs are validated, have the necessary ntlm_auth tool, and are statically linked against suitably patched Heimdal 0.6 libraries. -

        2. +

        3. Using your favorite editor, change the /etc/samba/smb.conf file so it has contents similar to the example shown in “Samba Configuration File: /etc/samba/smb.conf”. -

        4. - - - i - - +

        5. + + + i + + Next you need to create a computer account in the Active Directory. This sets up the trust relationship needed for other clients to authenticate to the Samba server with an Active Directory Kerberos ticket. - This is done with the net ads join -U [Administrator%Password] + This is done with the “net ads join -U [Administrator%Password]” command, as follows:

           root#  net ads join -U administrator%vulcon
           

          -

        6. - - - - - +

        7. + + + + + Your new Samba binaries must be started in the standard manner as is applicable to the platform you are running on. Alternatively, start your Active Directory-enabled Samba with the following commands:

          @@ -319,12 +319,12 @@
           root#  nmbd -D
           root#  winbindd -D
           

          -

        8. - - - - - +

        9. + + + + + We now need to test that Samba is communicating with the Active Directory domain; most specifically, we want to see whether winbind is enumerating users and groups. Issue the following commands: @@ -356,9 +356,9 @@ LONDON+DnsUpdateProxy

          This enumerates all the groups in your Active Directory tree. -

        10. - - +

        11. + + Squid uses the ntlm_auth helper build with Samba-3. You may test ntlm_auth with the command:

          @@ -369,20 +369,20 @@
           

           root#  NT_STATUS_OK: Success (0x0)
           

          -

        12. - - - - - - - - +

        13. + + + + + + + + The ntlm_auth helper, when run from a command line as the user - root, authenticates against your Active Directory domain (with + “root”, authenticates against your Active Directory domain (with the aid of winbind). It manages this by reading from the winbind privileged pipe. - Squid is running with the permissions of user squid and group - squid and is not able to do this unless we make a vital change. + Squid is running with the permissions of user “squid” and group + “squid” and is not able to do this unless we make a vital change. Squid cannot read from the winbind privilege pipe unless you change the permissions of its directory. This is the single biggest cause of failure in the whole process. Remember to issue the following command (for Red Hat Linux): @@ -395,77 +395,77 @@ root# chgrp squid /var/lib/samba/winbindd_privileged root# chmod 750 /var/lib/samba/winbindd_privileged

          -

      NSS Configuration

      - - - +

NSS Configuration

+ + + For Squid to benefit from Samba-3, NSS must be updated to allow winbind as a valid route to user authentication.

Edit your /etc/nsswitch.conf file so it has the parameters shown in “NSS Configuration File Extract File: /etc/nsswitch.conf”. -

Example 12.2. Samba Configuration File: /etc/samba/smb.conf

[global]
workgroup = LONDON
netbios name = W2K3S
realm = LONDON.ABMAS.BIZ
security = ads
encrypt passwords = yes
password server = w2k3s.london.abmas.biz
# 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
winbind user default domain = yes

Example 12.3. NSS Configuration File Extract File: /etc/nsswitch.conf

+	

Example 12.2. Samba Configuration File: /etc/samba/smb.conf

[global]
workgroup = LONDON
netbios name = W2K3S
realm = LONDON.ABMAS.BIZ
security = ads
encrypt passwords = yes
password server = w2k3s.london.abmas.biz
# 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
winbind user default domain = yes

Example 12.3. NSS Configuration File Extract File: /etc/nsswitch.conf

 passwd: files winbind
 shadow: files
 group: files winbind
-

Squid Configuration

- - +


Squid Configuration

+ + Squid must be configured correctly to interact with the Samba-3 components that handle Active Directory authentication. -

Configuration

Procedure 12.3. Squid Configuration Steps

  1. - - - +

Configuration

Procedure 12.3. Squid Configuration Steps

  1. + + + If your Linux distribution is SUSE Linux 9, the version of Squid supplied is already enabled to use the winbind helper agent. You can therefore omit the steps that would build the Squid binary programs. -

  2. - - - - - +

  3. + + + + + Squid, by default, runs as the user nobody. You need to add a system user squid and a system group squid if they are not set up already (if the default Red Hat squid rpms were installed, they will be). Set up a squid user in /etc/passwd and a squid group in /etc/group if these aren't there already. -

  4. - - +

  5. + + You now need to change the permissions on Squid's var directory. Enter the following command:

     root#  chown -R squid /var/cache/squid
     

    -

  6. - - +

  7. + + Squid must also have control over its logging. Enter the following commands:

     root#  chown -R chown squid:squid /var/log/squid
     root#  chmod 770 /var/log/squid
     

    -

  8. +

  9. Finally, Squid must be able to write to its disk cache! Enter the following commands:

     root#  chown -R chown squid:squid /var/cache/squid
     root#  chmod 770 /var/cache/squid
     

    -

  10. - +

  11. + The /etc/squid/squid.conf file must be edited to include the lines from “Squid Configuration File Extract /etc/squid.conf [ADMINISTRATIVE PARAMETERS Section]” and “Squid Configuration File extract File: /etc/squid.conf [AUTHENTICATION PARAMETERS Section]”. -

  12. - +

  13. + You must create Squid's cache directories before it may be run. Enter the following command:

     root#  squid -z
     

    -

  14. +

  15. Finally, start Squid and enjoy transparent Active Directory authentication. Enter the following command:

    @@ -487,23 +487,23 @@
     	auth_param basic credentialsttl 2 hours
     	acl AuthorizedUsers proxy_auth REQUIRED
     	http_access allow all AuthorizedUsers
    -

Key Points Learned

- - - - - +


Key Points Learned

+ + + + + Microsoft Windows networking protocols permeate the spectrum of technologies that Microsoft Windows clients use, even when accessing traditional services such as Web browsers. Depending on whom you discuss this with, this is either good or bad. No matter how you might evaluate this, the use of NTLMSSP as the authentication protocol for Web proxy access has some advantages over the cookie-based authentication regime used by all competing browsers. It is Samba's implementation of NTLMSSP that makes it attractive to implement the solution that has been demonstrated in this chapter. -

Questions and Answers

- - - - +

Questions and Answers

+ + + + The development of the ntlm_auth module was first discussed in many Open Source circles in 2002. At the SambaXP conference in Goettingen, Germany, Mr. Francesco Chemolli demonstrated the use of ntlm_auth during one of the late developer meetings that took place. Since that time, the @@ -515,41 +515,41 @@ wishes to remain anonymous, the sustained transaction load on this server hovers around 140 hits/sec. The following comments were made with respect to questions regarding the performance of this installation:

- [In our] EXTREMELY optimized environment . . . [the] performance impact is almost [nothing]. The almost + [In our] EXTREMELY optimized environment . . . [the] performance impact is almost [nothing]. The “almost” part is due to the brain damage of the ntlm-over-http protocol definition. Suffice to say that its worst-case scenario triples the number of hits needed to perform the same transactions versus basic or digest auth[entication].

You would be well-advised to recognize that all cache-intensive proxying solutions demand a lot of memory. Make certain that your Squid proxy server is equipped with sufficient memory to permit all proxy operations to run out of memory without invoking the overheads involved in the use of memory that has to be swapped to disk. -

+

What does Samba have to do with Web proxy serving? -
+
What other services does Samba provide? -
+
Does use of Samba (ntlm_auth) improve the performance of Squid? -

+

What does Samba have to do with Web proxy serving?

- - - - - + + + + + To provide transparent interoperability between Windows clients and the network services that are used from them, Samba had to develop tools and facilities that deliver that feature. The benefit of Open Source software is that it can readily be reused. The current ntlm_auth module is basically a wrapper around authentication code from the core of the Samba project.

- - - - - - - - - + + + + + + + + + The ntlm_auth module supports basic plain-text authentication and NTLMSSP protocols. This module makes it possible for Web and FTP proxy requests to be authenticated without the user being interrupted via his or her Windows logon credentials. This facility is available with @@ -557,36 +557,36 @@ There are a few open source initiatives to provide support for these protocols in the Apache Web server also.

- + The short answer is that by adding a wrapper around key authentication components of Samba, other projects (like Squid) can benefit from the labors expended in meeting user interoperability needs. -

+

What other services does Samba provide?

- - - - - + + + + + Samba-3 is a file and print server. The core components that provide this functionality are smbd, nmbd, and the identity resolver daemon, winbindd.

- - + + Samba-3 is an SMB/CIFS client. The core component that provides this is called smbclient.

- - - - - + + + + + Samba-3 includes a number of helper tools, plug-in modules, utilities, and test and validation facilities. Samba-3 includes glue modules that help provide interoperability between MS Windows clients and UNIX/Linux servers and clients. It includes Winbind agents that make it possible to authenticate UNIX/Linux access attempts as well as logins to an SMB/CIFS authentication server backend. Samba-3 includes name service switch (NSS) modules to permit identity resolution via SMB/CIFS servers (Windows NT4/200x, Samba, and a host of other commercial server products). -

+

Does use of Samba (ntlm_auth) improve the performance of Squid?

Not really. Samba's ntlm_auth module handles only authentication. It requires that diff -u -r --new-file --exclude .svn --exclude CVS samba-3.3.10//docs/htmldocs/Samba3-ByExample/ExNetworks.html samba-3.3.11//docs/htmldocs/Samba3-ByExample/ExNetworks.html --- samba-3.3.10//docs/htmldocs/Samba3-ByExample/ExNetworks.html 2010-01-14 11:24:12.000000000 +0100 +++ samba-3.3.11//docs/htmldocs/Samba3-ByExample/ExNetworks.html 2010-02-22 16:53:36.000000000 +0100 @@ -1,4 +1,4 @@ -Part I. Example Network Configurations

Part I. Example Network Configurations

Example Network Configurations

+Part I. Example Network Configurations

Part I. Example Network Configurations

Example Network Configurations

This section of Samba-3 by Example provides example network configurations that can be copied, or modified as needed, and deployed as-is. The contents have been marginally updated to reflect changes made in Samba=3.0.23. @@ -20,4 +20,4 @@ commercial support options may be obtained from the commercial support pages from the Samba web site. -

Table of Contents

1. No-Frills Samba Servers
Introduction
Assignment Tasks
Drafting Office
Charity Administration Office
Accounting Office
Questions and Answers
2. Small Office Networking
Introduction
Assignment Tasks
Dissection and Discussion
Technical Issues
Political Issues
Implementation
Validation
Notebook Computers: A Special Case
Key Points Learned
Questions and Answers
3. Secure Office Networking
Introduction
Assignment Tasks
Dissection and Discussion
Technical Issues
Political Issues
Implementation
Basic System Configuration
Samba Configuration
Configuration of DHCP and DNS Servers
Printer Configuration
Process Startup Configuration
Validation
Application Share Configuration
Windows Client Configuration
Key Points Learned
Questions and Answers
4. The 500-User Office
Introduction
Assignment Tasks
Dissection and Discussion
Technical Issues
Political Issues
Implementation
Installation of DHCP, DNS, and Samba Control Files
Server Preparation: All Servers
Server-Specific Preparation
Process Startup Configuration
Windows Client Configuration
Key Points Learned
Questions and Answers
5. Making Happy Users
Regarding LDAP Directories and Windows Computer Accounts
Introduction
Assignment Tasks
Dissection and Discussion
Technical Issues
Political Issues
Installation Checklist
Samba Server Implementation
OpenLDAP Server Configuration
PAM and NSS Client Configuration
Samba-3 PDC Configuration
Install and Configure Idealx smbldap-tools Scripts
LDAP Initialization and Creation of User and Group Accounts
Printer Configuration
Samba-3 BDC Configuration
Miscellaneous Server Preparation Tasks
Configuring Directory Share Point Roots
Configuring Profile Directories
Preparation of Logon Scripts
Assigning User Rights and Privileges
Windows Client Configuration
Configuration of Default Profile with Folder Redirection
Configuration of MS Outlook to Relocate PST File
Configure Delete Cached Profiles on Logout
Uploading Printer Drivers to Samba Servers
Software Installation
Roll-out Image Creation
Key Points Learned
Questions and Answers
6. A Distributed 2000-User Network
Introduction
Assignment Tasks
Dissection and Discussion
Technical Issues
Political Issues
Implementation
Key Points Learned
Questions and Answers
+

Table of Contents

1. No-Frills Samba Servers
Introduction
Assignment Tasks
Drafting Office
Charity Administration Office
Accounting Office
Questions and Answers
2. Small Office Networking
Introduction
Assignment Tasks
Dissection and Discussion
Technical Issues
Political Issues
Implementation
Validation
Notebook Computers: A Special Case
Key Points Learned
Questions and Answers
3. Secure Office Networking
Introduction
Assignment Tasks
Dissection and Discussion
Technical Issues
Political Issues
Implementation
Basic System Configuration
Samba Configuration
Configuration of DHCP and DNS Servers
Printer Configuration
Process Startup Configuration
Validation
Application Share Configuration
Windows Client Configuration
Key Points Learned
Questions and Answers
4. The 500-User Office
Introduction
Assignment Tasks
Dissection and Discussion
Technical Issues
Political Issues
Implementation
Installation of DHCP, DNS, and Samba Control Files
Server Preparation: All Servers
Server-Specific Preparation
Process Startup Configuration
Windows Client Configuration
Key Points Learned
Questions and Answers
5. Making Happy Users
Regarding LDAP Directories and Windows Computer Accounts
Introduction
Assignment Tasks
Dissection and Discussion
Technical Issues
Political Issues
Installation Checklist
Samba Server Implementation
OpenLDAP Server Configuration
PAM and NSS Client Configuration
Samba-3 PDC Configuration
Install and Configure Idealx smbldap-tools Scripts
LDAP Initialization and Creation of User and Group Accounts
Printer Configuration
Samba-3 BDC Configuration
Miscellaneous Server Preparation Tasks
Configuring Directory Share Point Roots
Configuring Profile Directories
Preparation of Logon Scripts
Assigning User Rights and Privileges
Windows Client Configuration
Configuration of Default Profile with Folder Redirection
Configuration of MS Outlook to Relocate PST File
Configure Delete Cached Profiles on Logout
Uploading Printer Drivers to Samba Servers
Software Installation
Roll-out Image Creation
Key Points Learned
Questions and Answers
6. A Distributed 2000-User Network
Introduction
Assignment Tasks
Dissection and Discussion
Technical Issues
Political Issues
Implementation
Key Points Learned
Questions and Answers
diff -u -r --new-file --exclude .svn --exclude CVS samba-3.3.10//docs/htmldocs/Samba3-ByExample/go01.html samba-3.3.11//docs/htmldocs/Samba3-ByExample/go01.html --- samba-3.3.10//docs/htmldocs/Samba3-ByExample/go01.html 2010-01-14 11:24:30.000000000 +0100 +++ samba-3.3.11//docs/htmldocs/Samba3-ByExample/go01.html 2010-02-22 16:53:36.000000000 +0100 @@ -1,4 +1,4 @@ -Glossary

Glossary

Access Control List

+Glossary

Glossary

Access Control List

A detailed list of permissions granted to users or groups with respect to file and network resource access.

Active Directory Service

@@ -11,7 +11,7 @@ the Internet hype in the 1990s. At about the time that the SMB protocol was renamed to CIFS, an additional dialect of the SMB protocol was in development. The need for the deployment of the NetBIOS layer was also removed, thus paving the way for use of the SMB - protocol natively over TCP/IP (known as NetBIOS-less SMB or naked TCP + protocol natively over TCP/IP (known as NetBIOS-less SMB or “naked” TCP transport).

Common UNIX Printing System

A recent implementation of a high-capability printing system for UNIX developed by @@ -96,8 +96,8 @@ DER refers to Distinguished Encoding Rules. These are a set of common rules for creating binary encodings in a platform-independent manner. Samba has support for SPNEGO.

The Official Samba-3 HOWTO and Reference Guide, Second Edition

- This book makes repeated reference to The Official Samba-3 HOWTO and Reference Guide, Second - Edition by John H. Terpstra and Jelmer R. Vernooij. This publication is available from + This book makes repeated reference to “The Official Samba-3 HOWTO and Reference Guide, Second + Edition” by John H. Terpstra and Jelmer R. Vernooij. This publication is available from Amazon.com. Publisher: Prentice Hall PTR (August 2005), ISBN: 013122282.

User IDentifier

@@ -111,5 +111,5 @@ freely available for UNIX/Linux and Microsoft Windows systems from the Wireshark Web site.

diff -u -r --new-file --exclude .svn --exclude CVS samba-3.3.10//docs/htmldocs/Samba3-ByExample/HA.html samba-3.3.11//docs/htmldocs/Samba3-ByExample/HA.html --- samba-3.3.10//docs/htmldocs/Samba3-ByExample/HA.html 2010-01-14 11:24:24.000000000 +0100 +++ samba-3.3.11//docs/htmldocs/Samba3-ByExample/HA.html 2010-02-22 16:53:36.000000000 +0100 @@ -1,7 +1,7 @@ -Chapter 13. Performance, Reliability, and Availability

Chapter 13. Performance, Reliability, and Availability

- - - +Chapter 13. Performance, Reliability, and Availability

Chapter 13. Performance, Reliability, and Availability

+ + + Well, you have reached one of the last chapters of this book. It is customary to attempt to wrap up the theme and contents of a book in what is generally regarded as the chapter that should draw conclusions. This book is a suspense thriller, and since @@ -10,8 +10,8 @@ regarding some of the things everyone can do to deliver a reliable Samba-3 network.

 

In a world so full of noise, how can the sparrow be heard? -

 
 --Anonymous

Introduction

- +

 
 --Anonymous

Introduction

+ The sparrow is a small bird whose sounds are drowned out by the noise of the busy world it lives in. Likewise, the simple steps that can be taken to improve the reliability and availability of a Samba network are often drowned out by the volume @@ -20,22 +20,22 @@ itself to discussion of clustering because each clustering methodology uses its own custom tools and methods. Only passing comments are offered concerning these methods.

- - - + + + A search - for samba cluster produced 71,600 hits. And a search for highly available samba - and highly available windows produced an amazing number of references. + for “samba cluster” produced 71,600 hits. And a search for “highly available samba” + and “highly available windows” produced an amazing number of references. It is clear from the resources on the Internet that Windows file and print services availability, reliability, and scalability are of vital interest to corporate network users.

- + So without further background, you can review a checklist of simple steps that can be taken to ensure acceptable network performance while keeping costs of ownership well under control. -

Dissection and Discussion

- - +

Dissection and Discussion

+ + If it is your purpose to get the best mileage out of your Samba servers, there is one rule that must be obeyed. If you want the best, keep your implementation as simple as possible. You may well be forced to introduce some complexities, but you should do so only as a last resort. @@ -44,8 +44,8 @@ make life easier for your successor. Simple implementations can be more readily audited than can complex ones.

- - + + Problems reported by users fall into three categories: configurations that do not work, those that have broken behavior, and poor performance. The term broken behavior means that the function of a particular Samba component appears to work sometimes, but not at @@ -54,12 +54,12 @@ list of Windows machines in MS Explorer changes, sometimes listing machines that are running and at other times not listing them even though the machines are in use on the network.

- - - - - - + + + + + + A significant number of reports concern problems with the smbfs file system driver that is part of the Linux kernel, not part of Samba. Users continue to interpret that smbfs is part of Samba, simply because Samba includes the front-end tools @@ -70,32 +70,32 @@ common infrastructure with some Samba components, but they are not maintained as part of Samba and are really foreign to it.

- + The new project, cifsfs, is destined to replace smbfs. It, too, is not part of Samba, even though one of the Samba Team members is a prime mover in this project.

Table 13.1 lists typical causes of: -

  • Not Working (NW)

  • Broken Behavior (BB)

  • Poor Performance (PP)

Table 13.1. Effect of Common Problems

Problem

NW

BB

PP

File locking

-

X

-

Hardware problems

X

X

X

Incorrect authentication

X

X

-

Incorrect configuration

X

X

X

LDAP problems

X

X

-

Name resolution

X

X

X

Printing problems

X

X

-

Slow file transfer

-

-

X

Winbind problems

X

X

-


- +

  • Not Working (NW)

  • Broken Behavior (BB)

  • Poor Performance (PP)

Table 13.1. Effect of Common Problems

Problem

NW

BB

PP

File locking

-

X

-

Hardware problems

X

X

X

Incorrect authentication

X

X

-

Incorrect configuration

X

X

X

LDAP problems

X

X

-

Name resolution

X

X

X

Printing problems

X

X

-

Slow file transfer

-

-

X

Winbind problems

X

X

-


+ It is obvious to all that the first requirement (as a matter of network hygiene) is to eliminate problems that affect basic network operation. This book has provided sufficient working examples to help you to avoid all these problems. -

Guidelines for Reliable Samba Operation

- - +

Guidelines for Reliable Samba Operation

+ + Your objective is to provide a network that works correctly, can grow at all times, is resilient at times of extreme demand, and can scale to meet future needs. The following subject areas provide pointers that can help you today. -

Name Resolution

+

Name Resolution

There are three basic current problem areas: bad hostnames, routed networks, and network collisions. These are covered in the following discussion. -

Bad Hostnames

- - - - - +

Bad Hostnames

+ + + + + When configured as a DHCP client, a number of Linux distributions set the system hostname to localhost. If the parameter netbios name is not specified to something other than localhost, the Samba server appears @@ -107,13 +107,13 @@ the local Windows machine itself. Hostnames must be valid for Windows networking to function correctly.

- + A few sites have tried to name Windows clients and Samba servers with a name that begins with the digits 1-9. This does not work either because it may result in the client or server attempting to use that name as an IP address.

- - + + A Samba server called FRED in a NetBIOS domain called COLLISION in a network environment that is part of the fully-qualified Internet domain namespace known as parrots.com, results in DNS name lookups for fred.parrots.com @@ -121,50 +121,50 @@ (workgroup) collision.parrots.com, since this results in DNS lookup attempts to resolve fred.parrots.com.parrots.com, which most likely fails given that you probably do not have this in your DNS namespace. -

Note

- - - +

Note

+ + + An Active Directory realm called collision.parrots.com is perfectly okay, although it too must be capable of being resolved via DNS, something that functions correctly if Windows 200x ADS has been properly installed and configured. -

Routed Networks

- - - +

Routed Networks

+ + + NetBIOS networks (Windows networking with NetBIOS over TCP/IP enabled) makes extensive use of UDP-based broadcast traffic, as you saw during the exercises in “Networking Primer”.

- - - + + + UDP broadcast traffic is not forwarded by routers. This means that NetBIOS broadcast-based networking cannot function across routed networks (i.e., multi-subnet networks) unless special provisions are made: -

  • - - - +

    • + + + Either install on every Windows client an LMHOSTS file (located in the directory C:\windows\system32\drivers\etc). It is also necessary to add to the Samba server smb.conf file the parameters remote announce and remote browse sync. For more information, refer to the online manual page for the smb.conf file. -

    • - +

    • + Or configure Samba as a WINS server, and configure all network clients to use that WINS server in their TCP/IP configuration. -

    Note

    - - +

Note

+ + The use of DNS is not an acceptable substitute for WINS. DNS does not store specific information regarding NetBIOS networking particulars that get stored in the WINS name resolution database and that Windows clients require and depend on. -

Network Collisions

- - - - +

Network Collisions

+ + + + Excessive network activity causes NetBIOS network timeouts. Timeouts may result in blue screen of death (BSOD) experiences. High collision rates may be caused by excessive UDP broadcast activity, by defective networking hardware, or through excessive network @@ -173,9 +173,9 @@ The use of WINS is highly recommended to reduce network broadcast traffic, as outlined in “Networking Primer”.

- - - + + + Under no circumstances should the facility be supported by many routers, known as NetBIOS forwarding, unless you know exactly what you are doing. Inappropriate use of this facility can result in UDP broadcast storms. In one case in 1999, a university network became @@ -183,13 +183,13 @@ testing of a Samba server. The maximum throughput on a 100-Base-T (100 MB/sec) network was less than 15 KB/sec. After the NetBIOS forwarding was turned off, file transfer performance immediately returned to 11 MB/sec. -

Samba Configuration

+

Samba Configuration

As a general rule, the contents of the smb.conf file should be kept as simple as possible. No parameter should be specified unless you know it is essential to operation.

- - - + + + Many UNIX administrators like to fully document the settings in the smb.conf file. This is a bad idea because it adds content to the file. The smb.conf file is re-read by every smbd process every time the file timestamp changes (or, on systems where this does not work, every 20 seconds or so). @@ -197,7 +197,7 @@ As the size of the smb.conf file grows, the risk of introducing parsing errors also increases. It is recommended to keep a fully documented smb.conf file on hand, and then to operate Samba only with an optimized file. -

+

The preferred way to maintain a documented file is to call it something like smb.conf.master. You can generate the optimized file by executing:

@@ -223,7 +223,7 @@
 Server role: ROLE_DOMAIN_PDC
 Press enter to see a dump of your service definitions
 

- + You now, of course, press the enter key to complete the command, or else abort it by pressing Ctrl-C. The important thing to note is the noted Server role, as well as warning messages. Noted configuration conflicts must be remedied before proceeding. For example, the following error message represents a @@ -233,28 +233,28 @@ cannot be set in the smb.conf file. nmbd will abort with this setting.

- - - + + + There are two parameters that can cause severe network performance degradation: socket options and socket address. The socket options parameter was often necessary when Samba was used with the Linux 2.2.x kernels. Later kernels are largely self-tuning and seldom benefit from this parameter being set. Do not use either parameter unless it has been proven necessary to use them.

- - - - + + + + Another smb.conf parameter that may cause severe network performance degradation is the strict sync parameter. Do not use this at all. There is no good reason to use this with any modern Windows client. The strict sync is often used with the sync always parameter. This, too, can severely degrade network performance, so do not set it; if you must, do so with caution.

- - - - + + + + Finally, many network administrators deliberately disable opportunistic locking support. While this does not degrade Samba performance, it significantly degrades Windows client performance because this disables local file caching on Windows clients and forces every file read and written to @@ -262,12 +262,12 @@ support, do so only on the share on which it is required. That way, all other shares can provide oplock support for operations that are tolerant of it. See “Shared Data Integrity” for more information. -

Use and Location of BDCs

- - - - - +

Use and Location of BDCs

+ + + + + On a network segment where there is a PDC and a BDC, the BDC carries the bulk of the network logon processing. If the BDC is a heavily loaded server, the PDC carries a greater proportion of authentication and logon processing. When a sole BDC on a routed network segment gets heavily @@ -275,13 +275,13 @@ to a BDC on a distant network segment. This significantly hinders WAN operations and is undesirable.

- - + + As a general guide, instead of adding domain member servers to a network, you would be better advised to add BDCs until there are fewer than 30 Windows clients per BDC. Beyond that ratio, you should add domain member servers. This practice ensures that there are always sufficient domain controllers to handle logon requests and authentication traffic. -

Use One Consistent Version of MS Windows Client

+

Use One Consistent Version of MS Windows Client

Every network client has its own peculiarities. From a management perspective, it is easier to deal with one version of MS Windows that is maintained to a consistent update level than it is to deal with a mixture of clients. @@ -289,61 +289,61 @@ On a number of occasions, particular Microsoft service pack updates of a Windows server or client have necessitated special handling from the Samba server end. If you want to remain sane, keep you client workstation configurations consistent. -

For Scalability, Use SAN-Based Storage on Samba Servers

- - +

For Scalability, Use SAN-Based Storage on Samba Servers

+ + Many SAN-based storage systems permit more than one server to share a common data store. Use of a shared SAN data store means that you do not need to use time- and resource-hungry data synchronization techniques.

- - + + The use of a collection of relatively low-cost front-end Samba servers that are coupled to a shared backend SAN data store permits load distribution while containing costs below that of installing and managing a complex clustering facility. -

Distribute Network Load with MSDFS

- - +

Distribute Network Load with MSDFS

+ + Microsoft DFS (distributed file system) technology has been implemented in Samba. MSDFS permits data to be accessed from a single share and yet to actually be distributed across multiple actual servers. Refer to TOSHARG2, Chapter 19, for information regarding implementation of an MSDFS installation.

- - + + The combination of multiple backend servers together with a front-end server and use of MSDFS can achieve almost the same as you would obtain with a clustered Samba server. -

Replicate Data to Conserve Peak-Demand Wide-Area Bandwidth

- - - +

Replicate Data to Conserve Peak-Demand Wide-Area Bandwidth

+ + + Consider using rsync to replicate data across the WAN during times of low utilization. Users can then access the replicated data store rather than needing to do so across the WAN. This works best for read-only data, but with careful planning can be implemented so that modified files get replicated back to the point of origin. Be careful with your implementation if you choose to permit modification and return replication of the modified file; otherwise, you may inadvertently overwrite important data. -

Hardware Problems

- - - - - - +

Hardware Problems

+ + + + + + Networking hardware prices have fallen sharply over the past 5 years. A surprising number of Samba networking problems over this time have been traced to defective network interface cards (NICs) or defective HUBs, switches, and cables.

- + Not surprising is the fact that network administrators do not like to be shown to have made a bad decision. Money saved in buying low-cost hardware may result in high costs incurred in corrective action.

- - - - - + + + + + Defective NICs, HUBs, and switches may appear as intermittent network access problems, intermittent or persistent data corruption, slow network throughput, low performance, or even as BSOD problems with MS Windows clients. In one case, a company updated several workstations with newer, faster @@ -352,14 +352,14 @@

Defective hardware problems may take patience and persistence before the real cause can be discovered.

- + Networking hardware defects can significantly impact perceived Samba performance, but defective RAID controllers as well as SCSI and IDE hard disk controllers have also been known to impair Samba server operations. One business came to this realization only after replacing a Samba installation with MS Windows Server 2000 running on the same hardware. The root of the problem completely eluded the network administrator until the entire server was replaced. While you may well think that this would never happen to you, experience shows that given the right (unfortunate) circumstances, this can happen to anyone. -

Large Directories

+

Large Directories

There exist applications that create or manage directories containing many thousands of files. Such applications typically generate many small files (less than 100 KB). At the best of times, under UNIX, listing of the files in a directory that contains many files is slow. By default, Windows NT, 200x, @@ -399,7 +399,7 @@ All files and directories under the path directory must be in the same case as specified in the smb.conf stanza. This means that smbd will not be able to find lower case filenames with these settings. Note, this is done on a per-share basis. -

Key Points Learned

+

Key Points Learned

This chapter has touched in broad sweeps on a number of simple steps that can be taken to ensure that your Samba network is resilient, scalable, and reliable, and that it performs well. @@ -408,7 +408,7 @@ In the long term, that may not be you. Spare a thought for your successor and give him or her an even break.

- + Last, but not least, you should not only keep the network design simple, but also be sure it is well documented. This book may serve as your pattern for documenting every aspect of your design, its implementation, and particularly the objects and assumptions diff -u -r --new-file --exclude .svn --exclude CVS samba-3.3.10//docs/htmldocs/Samba3-ByExample/happy.html samba-3.3.11//docs/htmldocs/Samba3-ByExample/happy.html --- samba-3.3.10//docs/htmldocs/Samba3-ByExample/happy.html 2010-01-14 11:24:10.000000000 +0100 +++ samba-3.3.11//docs/htmldocs/Samba3-ByExample/happy.html 2010-02-22 16:53:36.000000000 +0100 @@ -1,12 +1,12 @@ -Chapter 5. Making Happy Users

Chapter 5. Making Happy Users

- It is said that a day that is without troubles is not fulfilling. Rather, give - me a day of troubles well handled so that I can be content with my achievements. +Chapter 5. Making Happy Users

Chapter 5. Making Happy Users

+ It is said that “a day that is without troubles is not fulfilling. Rather, give + me a day of troubles well handled so that I can be content with my achievements.

In the world of computer networks, problems are as varied as the people who create them or experience them. The design of the network implemented in “The 500-User Office” may create problems for some network users. The following lists some of the problems that may occur: -

Caution

+

Caution

A significant number of network administrators have responded to the guidance given here. It should be noted that there are sites that have a single PDC for many hundreds of concurrent network clients. Network bandwidth, network bandwidth utilization, and server load @@ -19,8 +19,8 @@ overloaded or network bandwidth is overloaded. The guidance given for PDC/BDC ratio to Windows clients is conservative and if followed will minimize problems but it is not absolute.

Users experiencing difficulty logging onto the network

- - + + When a Windows client logs onto the network, many data packets are exchanged between the client and the server that is providing the network logon services. Each request between the client and the server must complete within a specific @@ -30,9 +30,9 @@ 30 to 150 clients. The actual limits are determined by network operational characteristics.

- - - + + + If the domain controller provides only network logon services and all file and print activity is handled by domain member servers, one domain controller per 150 clients on a single network segment may suffice. In any @@ -46,42 +46,42 @@ that can be supported is limited by the CPU speed, memory and the workload on the Samba server as well as network bandwidth utilization.

Slow logons and log-offs

- + Slow logons and log-offs may be caused by many factors that include: -

  • - - +

    • + + Excessive delays in the resolution of a NetBIOS name to its IP address. This may be observed when an overloaded domain controller is also the WINS server. Another cause may be the failure to use a WINS server (this assumes that there is a single network segment). -

    • - - - +

    • + + + Network traffic collisions due to overloading of the network segment. One short-term workaround to this may be to replace network HUBs with Ethernet switches. -

    • - +

    • + Defective networking hardware. Over the past few years, we have seen on the Samba mailing list a significant increase in the number of problems that were traced to a defective network interface controller, a defective HUB or Ethernet switch, or defective cabling. In most cases, it was the erratic nature of the problem that ultimately pointed to the cause of the problem. -

    • - - +

    • + + Excessively large roaming profiles. This type of problem is typically the result of poor user education as well as poor network management. It can be avoided by users not storing huge quantities of email in MS Outlook PST files as well as by not storing files on the desktop. These are old bad habits that require much discipline and vigilance on the part of network management. -

    • - +

    • + You should verify that the Windows XP WebClient service is not running. The use of the WebClient service has been implicated in many Windows networking-related problems. @@ -89,27 +89,27 @@

Loss of access to network drives and printer resources

Loss of access to network resources during client operation may be caused by a number of factors, including: -

  • - +

    • + Network overload (typically indicated by a high network collision rate) -

    • +

    • Server overload -

    • - +

    • + Timeout causing the client to close a connection that is in use but has been latent (no traffic) for some time (5 minutes or more) -

    • - +

    • + Defective networking hardware

    - + No matter what the cause, a sudden loss of access to network resources can result in BSOD (blue screen of death) situations that necessitate rebooting of the client workstation. In the case of a mild problem, retrying to access the network drive of the printer may restore operations, but in any case this is a serious problem that may lead to the next problem, data corruption.

Potential data corruption

- + Data corruption is one of the most serious problems. It leads to uncertainty, anger, and frustration, and generally precipitates immediate corrective demands. Management response to this type of problem may be rational, as well as highly irrational. There have been @@ -123,48 +123,48 @@ anticipate and combat network performance issues. You can work through complex and thorny methods to improve the reliability of your network environment, but be warned that all such steps demand the price of complexity. -

Regarding LDAP Directories and Windows Computer Accounts

- +

Regarding LDAP Directories and Windows Computer Accounts

+ Computer (machine) accounts can be placed wherever you like in an LDAP directory subject to some constraints that are described in this section.

- - - - + + + + The POSIX and SambaSAMAccount components of computer (machine) accounts are both used by Samba. That is, machine accounts are treated inside Samba in the same way that Windows NT4/200X treats them. A user account and a machine account are indistinguishable from each other, except that the machine account ends in a $ character, as do trust accounts.

- - + + The need for Windows user, group, machine, trust, and other such accounts to be tied to a valid UNIX UID is a design decision that was made a long way back in the history of Samba development. It is unlikely that this decision will be reversed or changed during the remaining life of the Samba-3.x series.

- - + + The resolution of a UID from the Windows SID is achieved within Samba through a mechanism that must refer back to the host operating system on which Samba is running. The name service switch (NSS) is the preferred mechanism that shields applications (like Samba) from the need to know everything about every host OS it runs on.

- Samba asks the host OS to provide a UID via the passwd, shadow - and group facilities in the NSS control (configuration) file. The best tool + Samba asks the host OS to provide a UID via the “passwd”, “shadow” + and “group” facilities in the NSS control (configuration) file. The best tool for achieving this is left up to the UNIX administrator to determine. It is not imposed by Samba. Samba provides winbindd together with its support libraries as one method. It is possible to do this via LDAP, and for that Samba provides the appropriate hooks so that all account entities can be located in an LDAP directory.

- + For many the weapon of choice is to use the PADL nss_ldap utility. This utility must be configured so that computer accounts can be resolved to a POSIX/UNIX account UID. That is fundamentally an LDAP design question. The information provided on the Samba list and in the documentation is directed at providing working examples only. The design of an LDAP directory is a complex subject that is beyond the scope of this documentation. -

Introduction

+

Introduction

You just opened an email from Christine that reads:

Good morning, @@ -193,8 +193,8 @@ regain control of our vital IT operations.

 
 --Christine

- - + + Every compromise has consequences. Having a large routed (i.e., multisegment) network with only a single domain controller is a poor design that has obvious operational effects that may frustrate users. Here is your reply: @@ -204,56 +204,56 @@ boost staff morale. Please go ahead with your plans. If you have any problems, please let me know. Please let Stan know what the estimated cost will be so I can approve the expense. Do not wait for approval; I appreciate the urgency. -

 
 --Bob

Assignment Tasks

+

 
 --Bob

Assignment Tasks

The priority of assigned tasks in this chapter is: -

  1. - - - - +

    1. + + + + Implement Backup Domain Controllers (BDCs) in each building. This involves a change from a tdbsam backend that was used in the previous chapter to an LDAP-based backend.

      You can implement a single central LDAP server for this purpose. -

    2. - - - - +

    3. + + + + Rectify the problem of excessive logon times. This involves redirection of folders to network shares as well as modification of all user desktops to exclude the redirected folders from being loaded at login time. You can also create a new default profile that can be used for all new users.

    - + You configure a new MS Windows XP Professional workstation disk image that you roll out to all desktop users. The instructions you have created are followed on a staging machine from which all changes can be carefully tested before inflicting them on your network users.

    - + This is the last network example in which specific mention of printing is made. The example again makes use of the CUPS printing system. -

Dissection and Discussion

- - - +

Dissection and Discussion

+ + + The implementation of Samba BDCs necessitates the installation and configuration of LDAP. For this site, you use OpenLDAP, the open source software LDAP server platform. Commercial LDAP servers in current use with Samba-3 include: -

  • - +

    • + Novell eDirectory is being successfully used by some sites. Information on how to use eDirectory can be obtained from the Samba mailing lists or from Novell. -

    • - +

    • + IBM Tivoli Directory Server can be used to provide the Samba LDAP backend. Example schema files are provided in the Samba source code tarball under the directory ~samba/example/LDAP. -

    • - +

    • + Sun ONE Identity Server product suite provides an LDAP server that can be used for Samba. Example schema files are provided in the Samba source code tarball under the directory @@ -264,19 +264,19 @@ initialize the LDAP directory database. OpenLDAP itself has only command-line tools to help you to get OpenLDAP and Samba-3 running as required, albeit with some learning curve challenges.

      - + For most sites, the deployment of Microsoft Active Directory from the shrink-wrapped installation is quite adequate. If you are migrating from Microsoft Active Directory, be warned that OpenLDAP does not include GUI-based directory management tools. Even a simple task such as adding users to the OpenLDAP database requires an understanding of what you are doing, why you are doing it, and the tools that you must use.

      - - - - - - - + + + + + + + When installed and configured, an OpenLDAP Identity Management backend for Samba functions well. High availability operation may be obtained through directory replication/synchronization and master/slave server configurations. OpenLDAP is a mature platform to host the organizational @@ -286,10 +286,10 @@ contents with greater ability to back up, restore, and modify the directory than is generally possible with Microsoft Active Directory.

      - - - - + + + + A comparison of OpenLDAP with Microsoft Active Directory does not do justice to either. OpenLDAP is an LDAP directory tool-set. Microsoft Active Directory Server is an implementation of an LDAP server that is largely preconfigured for a specific task orientation. It comes with a set of administrative tools that is entirely customized @@ -300,8 +300,8 @@ MS ADAM that provides more generic LDAP services, yet it does not have the vanilla-like services of OpenLDAP.

      - - + + You may wish to consider outsourcing the development of your OpenLDAP directory to an expert, particularly if you find the challenge of learning about LDAP directories, schemas, configuration, and management tools and the creation of shell and Perl scripts a bit @@ -309,7 +309,7 @@ many ready-to-use schemas. Samba-3 provides an OpenLDAP schema file that is required for use as a passdb backend.

      - + For those who are willing to brave the process of installing and configuring LDAP and Samba-3 interoperability, there are a few nice Web-based tools that may help you to manage your users and groups more effectively. The Web-based tools you might like to consider include the @@ -323,7 +323,7 @@ LDAP Browser/Editor ; JXplorer (by Computer Associates); and phpLDAPadmin. -

      Note

      +

      Note

      The following prescriptive guidance is not an LDAP tutorial. The LDAP implementation expressly uses minimal security controls. No form of secure LDAP communications is attempted. The LDAP configuration information provided is considered to consist of the barest essentials only. You are strongly encouraged to learn more about @@ -334,10 +334,10 @@ LDAP System Administration, by Jerry Carter quite useful.

      - - - - + + + + Mary's problems are due to two factors. First, the absence of a domain controller on the local network is the main cause of the errors that result in blue screen crashes. Second, Mary has a large profile that must be loaded over the WAN connection. The addition of BDCs on each network segment significantly @@ -345,31 +345,31 @@ user desktops, and this must be done in a way that wins their support and does not cause further loss of staff morale. The following procedures solve this problem.

      - + There is also an opportunity to implement smart printing features. You add this to the Samba configuration so that future printer changes can be managed without need to change desktop configurations.

      You add the ability to automatically download new printer drivers, even if they are not installed in the default desktop profile. Only one example of printing configuration is given. It is assumed that you can extrapolate the principles and use them to install all printers that may be needed. -

      Technical Issues

      - - - +

      Technical Issues

      + + + The solution provided is a minimal approach to getting OpenLDAP running as an identity management directory server for UNIX system accounts as well as for Samba. From the OpenLDAP perspective, UNIX system accounts are stored POSIX schema extensions. Samba provides its own schema to permit storage of account attributes Samba needs. Samba-3 can use the LDAP backend to store: -

      • Windows Networking User Accounts

      • Windows NT Group Accounts

      • Mapping Information between UNIX Groups and Windows NT Groups

      • ID Mappings for SIDs to UIDs (also for foreign Domain SIDs)

      - - - - - - - - - +

      • Windows Networking User Accounts

      • Windows NT Group Accounts

      • Mapping Information between UNIX Groups and Windows NT Groups

      • ID Mappings for SIDs to UIDs (also for foreign Domain SIDs)

      + + + + + + + + + The use of LDAP with Samba-3 makes it necessary to store UNIX accounts as well as Windows Networking accounts in the LDAP backend. This implies the need to use the PADL LDAP tools. The resolution @@ -378,16 +378,16 @@ that integrates with the NSS. The same requirements exist for resolution of the UNIX username to the UID. The relationships are demonstrated in “The Interaction of LDAP, UNIX Posix Accounts and Samba Accounts”.

      Figure 5.1. The Interaction of LDAP, UNIX Posix Accounts and Samba Accounts

      The Interaction of LDAP, UNIX Posix Accounts and Samba Accounts

      - - + + You configure OpenLDAP so that it is operational. Before deploying the OpenLDAP, you really ought to learn how to configure secure communications over LDAP so that site security is not at risk. This is not covered in the following guidance.

      - - - - + + + + When OpenLDAP has been made operative, you configure the PDC called MASSIVE. You initialize the Samba secrets.tdb file. Then you create the LDAP Interchange Format (LDIF) file from which the LDAP database can be initialized. @@ -395,27 +395,27 @@ You can also find on the enclosed CD-ROM, in the Chap06 directory, a few tools that help to manage user and group configuration.

      - - - + + + In order to effect folder redirection and to add robustness to the implementation, create a network default profile. All network users workstations are configured to use the new profile. Roaming profiles will automatically be deleted from the workstation when the user logs off.

      - + The profile is configured so that users cannot change the appearance of their desktop. This is known as a mandatory profile. You make certain that users are able to use their computers efficiently.

      - + A network logon script is used to deliver flexible but consistent network drive connections. -

      Addition of Machines to the Domain

      - - - - +

      Addition of Machines to the Domain

      + + + + Samba versions prior to 3.0.11 necessitated the use of a domain administrator account that maps to the UNIX UID=0. The UNIX operating system permits only the root user to add user and group accounts. Samba 3.0.11 introduced a new facility known as @@ -425,13 +425,13 @@ In this network example use is made of one of the supported privileges purely to demonstrate how any user can now be given the ability to add machines to the domain using a normal user account that has been given the appropriate privileges. -

      Roaming Profile Background

      +

      Roaming Profile Background

      As XP roaming profiles grow, so does the amount of time it takes to log in and out.

      - - - - + + + + An XP roaming profile consists of the HKEY_CURRENT_USER hive file NTUSER.DAT and a number of folders (My Documents, Application Data, Desktop, Start Menu, Templates, NetHood, Favorites, and so on). When a user logs onto the @@ -453,20 +453,20 @@ user to not place large files on the desktop and to use his or her mapped home directory instead of the My Documents folder for saving documents.

      - + Using a folder other than My Documents is a nuisance for some users, since many applications use it by default.

      - - - + + + The secret to rapid loading of roaming profiles is to prevent unnecessary data from being copied back and forth, without losing any functionality. This is not difficult; it can be done by making changes to the Local Group Policy on each client as well as changing some paths in each user's NTUSER.DAT hive.

      - - + + Every user profile has its own NTUSER.DAT file. This means you need to edit every user's profile, unless a better method can be followed. Fortunately, with the right preparations, this is not difficult. @@ -474,11 +474,11 @@ user's profile. Then just create a Network Default Profile. Of course, it is necessary to copy all files from redirected folders to the network share to which they are redirected. -

      The Local Group Policy

      - - - - +

      The Local Group Policy

      + + + + Without an Active Directory PDC, you cannot take full advantage of Group Policy Objects. However, you can still make changes to the Local Group Policy by using the Group Policy editor (gpedit.msc). @@ -487,31 +487,31 @@ be found under User ConfigurationAdministrative TemplatesSystemUser Profiles. By default this setting contains - Local Settings; Temporary Internet Files; History; Temp. + “Local Settings; Temporary Internet Files; History; Temp”.

      Simply add the folders you do not wish to be copied back and forth to this semicolon-separated list. Note that this change must be made on all clients that are using roaming profiles. -

      Profile Changes

      - - +

      Profile Changes

      + + There are two changes that should be done to each user's profile. Move each of the directories that you have excluded from being copied back and forth out of the usual profile path. Modify each user's NTUSER.DAT file to point to the new paths that are shared over the network instead of to the default path (C:\Documents and Settings\%USERNAME%).

      - - + + The above modifies existing user profiles. So that newly created profiles have these settings, you need to modify the NTUSER.DAT in the C:\Documents and Settings\Default User folder on each client machine, changing the same registry keys. You could do this by copying NTUSER.DAT to a Linux box and using regedt32. The basic method is described under “Configuration of Default Profile with Folder Redirection”. -

      Using a Network Default User Profile

      - - +

      Using a Network Default User Profile

      + + If you are using Samba as your PDC, you should create a file share called NETLOGON and within that create a directory called Default User, which is a copy of the desired default user @@ -520,20 +520,20 @@ the first login from a new account pulls its configuration from it. See also the Real Men Don't Click Web site. -

      Installation of Printer Driver Auto-Download

      - - - +

      Installation of Printer Driver Auto-Download

      + + + The subject of printing is quite topical. Printing problems run second place to name resolution issues today. So far in this book, you have experienced only what is generally - known as dumb printing. Dumb printing is the arrangement by which all drivers + known as “dumb” printing. Dumb printing is the arrangement by which all drivers are manually installed on each client and the printing subsystems perform no filtering or intelligent processing. Dumb printing is easily understood. It usually works without many problems, but it has its limitations also. Dumb printing is better known as Raw-Print-Through printing.

      - - + + Samba permits the configuration of smart printing using the Microsoft Windows point-and-click (also called drag-and-drop) printing. What this provides is essentially the ability to print to any printer. If the local client does not yet have a @@ -547,9 +547,9 @@ then invokes a suitable print filter to convert the incoming data stream into a format suited to the printer to which the job is dispatched.

      - - - + + + The CUPS printing subsystem is capable of intelligent printing. It has the capacity to detect the data format and apply a print filter. This means that it is feasible to install on all Windows clients a single printer driver for use with all printers that are routed @@ -566,7 +566,7 @@ This book is about Samba-3, so you can confine the printing style to just the smart style of installation. Those interested in further information regarding intelligent printing should review documentation on the Easy Software Products Web site. -

      Avoiding Failures: Solving Problems Before They Happen

      +

      Avoiding Failures: Solving Problems Before They Happen

      It has often been said that there are three types of people in the world: those who have sharp minds and those who forget things. Please do not ask what the third group is like! Well, it seems that many of us have company in the second group. There must @@ -574,12 +574,12 @@ simple problems efficiently and effectively.

      Here are some diagnostic guidelines that can be referred to when things go wrong: -

      Preliminary Advice: Dangers Can Be Avoided

      - The best advice regarding how to mend a broken leg is Never break a leg! +

      Preliminary Advice: Dangers Can Be Avoided

      + The best advice regarding how to mend a broken leg is “Never break a leg!

      - + Newcomers to Samba and LDAP seem to struggle a great deal at first. If you want advice - regarding the best way to remedy LDAP and Samba problems: Avoid them like the plague! + regarding the best way to remedy LDAP and Samba problems: “Avoid them like the plague!

      If you are now asking yourself how problems can be avoided, the best advice is to start out your learning experience with a known-good configuration. After @@ -589,11 +589,11 @@ The examples in this chapter (also in the book as a whole) are known to work. That means that they could serve as the kick-off point for your journey through fields of knowledge. Use this resource carefully; we hope it serves you well. -

      Warning

      +

      Warning

      Do not be lulled into thinking that you can easily adopt the examples in this book and adapt them without first working through the examples provided. A little thing overlooked can cause untold pain and may permanently tarnish your experience. -

      The Name Service Caching Daemon

      +

      The Name Service Caching Daemon

      The name service caching daemon (nscd) is a primary cause of difficulties with name resolution, particularly where winbind is used. Winbind does its own caching, thus nscd causes double caching which can lead to peculiar problems during @@ -660,17 +660,17 @@ root# chkconfig nscd off root# rcnscd off

      -

      Debugging LDAP

      - - - +

      Debugging LDAP

      + + + In the example /etc/openldap/slapd.conf control file (see “LDAP DB_CONFIG File”) there is an entry for loglevel 256. To enable logging via the syslog infrastructure, it is necessary to uncomment this parameter and restart slapd.

      - - + + LDAP log information can be directed into a file that is separate from the normal system log files by changing the /etc/syslog.conf file so it has the following contents: @@ -689,7 +689,7 @@ local site needs. The configuration used later in this chapter reflects such customization with the intent that LDAP log files will be stored at a location that meets local site needs and wishes more fully. -

      Debugging NSS_LDAP

      +

      Debugging NSS_LDAP

      The basic mechanism for diagnosing problems with the nss_ldap utility involves adding to the /etc/ldap.conf file the following parameters:

      @@ -702,7 +702,7 @@
       

      The diagnostic process should follow these steps: -

      Procedure 5.1. NSS_LDAP Diagnostic Steps

      1. +

        Procedure 5.1. NSS_LDAP Diagnostic Steps

        1. Verify the nss_base_passwd, nss_base_shadow, nss_base_group entries in the /etc/ldap.conf file and compare them closely with the directory tree location that was chosen when the directory was first created. @@ -739,7 +739,7 @@ will be evaluated sequentially. Let us consider an example of use where the following DIT has been implemented:

          -

          • User accounts are stored under the DIT: ou=Users, dc=abmas, dc=biz

          • User login accounts are under the DIT: ou=People, ou-Users, dc=abmas, dc=biz

          • Computer accounts are under the DIT: ou=Computers, ou=Users, dc=abmas, dc=biz

          +

          • User accounts are stored under the DIT: ou=Users, dc=abmas, dc=biz

          • User login accounts are under the DIT: ou=People, ou-Users, dc=abmas, dc=biz

          • Computer accounts are under the DIT: ou=Computers, ou=Users, dc=abmas, dc=biz

          The appropriate multiple entry for the nss_base_passwd directive in the /etc/ldap.conf file may be: @@ -747,7 +747,7 @@ nss_base_passwd ou=People,ou=Users,dc=abmas,dc=org?one nss_base_passwd ou=Computers,ou=Users,dc=abmas,dc=org?one

          -

        2. +

        3. Perform lookups such as:

           root#  getent passwd
          @@ -755,7 +755,7 @@
           			Each such lookup will create an entry in the /data/log directory
           			for each such process executed. The contents of each file created in this directory
           			may provide a hint as to the cause of the a problem that is under investigation. 
          -			

        4. +

        5. For additional diagnostic information, check the contents of the /var/log/messages to see what error messages are being generated as a result of the LDAP lookups. Here is an example of a successful lookup: @@ -788,11 +788,11 @@ slapd[12164]: conn=1 fd=10 closed

          -

        6. +

        7. Check that the bindpw entry in the /etc/ldap.conf or in the /etc/ldap.secrets file is correct, as specified in the /etc/openldap/slapd.conf file. -

      Debugging Samba

      +

Debugging Samba

The following parameters in the smb.conf file can be useful in tracking down Samba-related problems:

 [global]
@@ -822,17 +822,17 @@
 		

Search for hints of what may have failed by looking for the words fail and error. -

Debugging on the Windows Client

+

Debugging on the Windows Client

MS Windows 2000 Professional and Windows XP Professional clients can be configured to create a netlogon.log file that can be very helpful in diagnosing network logon problems. Search the Microsoft knowledge base for detailed instructions. The techniques vary a little with each version of MS Windows. -

Political Issues

+

Political Issues

MS Windows network users are generally very sensitive to limits that may be imposed when confronted with locked-down workstation configurations. The challenge you face must be promoted as a choice between reliable, fast network operation and a constant flux of problems that result in user irritation. -

Installation Checklist

+

Installation Checklist

You are starting a complex project. Even though you went through the installation of a complex network in “The 500-User Office”, this network is a bigger challenge because of the large number of complex applications that must be configured before the first few steps @@ -840,18 +840,18 @@ frequently review the steps ahead while making at least a mental note of what has already been completed. The following task list may help you to keep track of the task items that are covered: -

  • Samba-3 PDC Server Configuration

    1. DHCP and DNS servers

    2. OpenLDAP server

    3. PAM and NSS client tools

    4. Samba-3 PDC

    5. Idealx smbldap scripts

    6. LDAP initialization

    7. Create user and group accounts

    8. Printers

    9. Share point directory roots

    10. Profile directories

    11. Logon scripts

    12. Configuration of user rights and privileges

  • Samba-3 BDC Server Configuration

    1. DHCP and DNS servers

    2. PAM and NSS client tools

    3. Printers

    4. Share point directory roots

    5. Profiles directories

  • Windows XP Client Configuration

    1. Default profile folder redirection

    2. MS Outlook PST file relocation

    3. Delete roaming profile on logout

    4. Upload printer drivers to Samba servers

    5. Install software

    6. Creation of roll-out images

Samba Server Implementation

- - +

  • Samba-3 PDC Server Configuration

    1. DHCP and DNS servers

    2. OpenLDAP server

    3. PAM and NSS client tools

    4. Samba-3 PDC

    5. Idealx smbldap scripts

    6. LDAP initialization

    7. Create user and group accounts

    8. Printers

    9. Share point directory roots

    10. Profile directories

    11. Logon scripts

    12. Configuration of user rights and privileges

  • Samba-3 BDC Server Configuration

    1. DHCP and DNS servers

    2. PAM and NSS client tools

    3. Printers

    4. Share point directory roots

    5. Profiles directories

  • Windows XP Client Configuration

    1. Default profile folder redirection

    2. MS Outlook PST file relocation

    3. Delete roaming profile on logout

    4. Upload printer drivers to Samba servers

    5. Install software

    6. Creation of roll-out images

Samba Server Implementation

+ + The network design shown in “Network Topology 500 User Network Using ldapsam passdb backend” is not comprehensive. It is assumed that you will install additional file servers and possibly additional BDCs.

Figure 5.2. Network Topology 500 User Network Using ldapsam passdb backend

Network Topology 500 User Network Using ldapsam passdb backend

- - + + All configuration files and locations are shown for SUSE Linux 9.2 and are equally valid for SUSE Linux Enterprise Server 9. The file locations for Red Hat Linux are similar. You may need to adjust the locations for your particular Linux system distribution/implementation. -

Note

+

Note

The following information applies to Samba-3.0.20 when used with the Idealx smbldap-tools scripts version 0.9.1. If using a different version of Samba or of the smbldap-tools tarball, please verify that the versions you are about to use are matching. The smbldap-tools package @@ -867,23 +867,23 @@ have completed the network implementation shown in that chapter. If you are starting with newly installed Linux servers, you must complete the steps shown in “Installation of DHCP, DNS, and Samba Control Files” before commencing at “OpenLDAP Server Configuration”. -

OpenLDAP Server Configuration

- - - +

OpenLDAP Server Configuration

+ + + Confirm that the packages shown in “Required OpenLDAP Linux Packages” are installed on your system.

Table 5.2. Required OpenLDAP Linux Packages

SUSE Linux 8.xSUSE Linux 9.xRed Hat Linux
nss_ldapnss_ldapnss_ldap
pam_ldappam_ldappam_ldap
openldap2openldap2openldap
openldap2-clientopenldap2-client 

Samba-3 and OpenLDAP will have a degree of interdependence that is unavoidable. The method for bootstrapping the LDAP and Samba-3 configuration is relatively straightforward. If you follow these guidelines, the resulting system should work fine. -

Procedure 5.2. OpenLDAP Server Configuration Steps

  1. - +

    Procedure 5.2. OpenLDAP Server Configuration Steps

    1. + Install the file shown in “LDAP Master Configuration File /etc/openldap/slapd.conf Part A” in the directory /etc/openldap. -

    2. - - - +

    3. + + + Remove all files from the directory /data/ldap, making certain that the directory exists with permissions:

      @@ -891,19 +891,19 @@
       drwx------   2 ldap    ldap       48 Dec 15 22:11 ldap
       

      This may require you to add a user and a group account for LDAP if they do not exist. -

    4. - +

    5. + Install the file shown in “LDAP DB_CONFIG File” in the directory /data/ldap. In the event that this file is added after ldap has been started, it is possible to cause the new settings to take effect by shutting down the LDAP server, executing the db_recover command inside the /data/ldap directory, and then restarting the LDAP server. -

    6. - +

    7. + Performance logging can be enabled and should preferably be sent to a file on a file system that is large enough to handle significantly sized logs. To enable the logging at a verbose level to permit detailed analysis, uncomment the entry in - the /etc/openldap/slapd.conf shown as loglevel 256. + the /etc/openldap/slapd.conf shown as “loglevel 256”.

      Edit the /etc/syslog.conf file to add the following at the end of the file: @@ -974,32 +974,32 @@ index sambaPrimaryGroupSID eq index sambaDomainName eq index default sub -


PAM and NSS Client Configuration

- - - +


PAM and NSS Client Configuration

+ + + The steps that follow involve configuration of LDAP, NSS LDAP-based resolution of users and groups. Also, so that LDAP-based accounts can log onto the system, the steps ahead configure the Pluggable Authentication Modules (PAM) to permit LDAP-based authentication.

- - + + Since you have chosen to put UNIX user and group accounts into the LDAP database, it is likely that you may want to use them for UNIX system (Linux) local machine logons. This necessitates correct configuration of PAM. The pam_ldap open source package provides the PAM modules that most people would use. On SUSE Linux systems, the pam_unix2.so module also has the ability to redirect authentication requests through LDAP.

- - - - + + + + You have chosen to configure these services by directly editing the system files, but of course, you know that this configuration can be done using system tools provided by the Linux system vendor. SUSE Linux has a facility in YaST (the system admin tool) through yastsystemldap-client that permits configuration of SUSE Linux as an LDAP client. Red Hat Linux provides the authconfig tool for this. -

Procedure 5.3. PAM and NSS Client Configuration Steps

Example 5.4. Configuration File for NSS LDAP Support /etc/ldap.conf

+	

Procedure 5.3. PAM and NSS Client Configuration Steps

Example 5.4. Configuration File for NSS LDAP Support /etc/ldap.conf

 host 127.0.0.1
 
 base dc=abmas,dc=biz
@@ -1041,23 +1041,23 @@
 nss_base_group  ou=Groups,dc=abmas,dc=biz?one
 
 ssl off
-

  1. - - - +


  1. + + + Execute the following command to find where the nss_ldap module expects to find its control file:

     root#  strings /lib/libnss_ldap.so.2 | grep conf
     

    The preferred and usual location is /etc/ldap.conf. -

  2. +

  3. On the server MASSIVE, install the file shown in “Configuration File for NSS LDAP Support /etc/ldap.conf” into the path that was obtained from the step above. On the servers called BLDG1 and BLDG2, install the file shown in “Configuration File for NSS LDAP Clients Support /etc/ldap.conf” into the path that was obtained from the step above. -

  4. - +

  5. + Edit the NSS control file (/etc/nsswitch.conf) so that the lines that control user and group resolution will obtain information from the normal system files as well as from ldap: @@ -1071,7 +1071,7 @@ added, you can validate resolution of the LDAP resolver process. The inclusion of WINS-based hostname resolution is deliberate so that all MS Windows client hostnames can be resolved to their IP addresses, whether or not they are DHCP clients. -

    Note

    +

    Note

    Some Linux systems (Novell SUSE Linux in particular) add entries to the nsswitch.conf file that may cause operational problems with the configuration methods adopted in this book. It is advisable to comment out the entries passwd_compat and group_compat @@ -1079,8 +1079,8 @@

    Even at the risk of overstating the issue, incorrect and inappropriate configuration of the nsswitch.conf file is a significant cause of operational problems with LDAP. -

  6. - +

  7. + For PAM LDAP configuration on this SUSE Linux 9.0 system, the simplest solution is to edit the following files in the /etc/pam.d directory: login, password, samba, sshd. In each file, locate every entry that has the @@ -1102,7 +1102,7 @@ session required pam_limits.so

    - + On other Linux systems that do not have an LDAP-enabled pam_unix2.so module, you must edit these files by adding the pam_ldap.so modules as shown here:

    @@ -1125,15 +1125,15 @@
     		demonstrates the use of the pam_ldap.so module. You can use either
     		implementation, but if the pam_unix2.so on your system supports
     		LDAP, you probably want to use it rather than add an additional module.
    -		

Samba-3 PDC Configuration

- +

Samba-3 PDC Configuration

+ Verify that the Samba-3.0.20 (or later) packages are installed on each SUSE Linux server before following the steps below. If Samba-3.0.20 (or later) is not installed, you have the choice to either build your own or obtain the packages from a dependable source. Packages for SUSE Linux 8.x, 9.x, and SUSE Linux Enterprise Server 9, as well as for Red Hat Fedora Core and Red Hat Enterprise Linux Server 3 and 4, are included on the CD-ROM that is included with this book. -

Procedure 5.4. Configuration of PDC Called MASSIVE

  1. +

    Procedure 5.4. Configuration of PDC Called MASSIVE

    1. Install the files in “LDAP Based smb.conf File, Server: MASSIVE global Section: Part A”, “LDAP Based smb.conf File, Server: MASSIVE global Section: Part B”, “LDAP Based smb.conf File, Shares Section Part A”, and “LDAP Based smb.conf File, Shares Section Part B” into the /etc/samba/ @@ -1142,8 +1142,8 @@ smb.conf.master and then to perform all file edits on the master file. The operational smb.conf is then generated as shown in the next step. -

    2. - +

    3. + Create and verify the contents of the smb.conf file that is generated by:

       root#  testparm -s smb.conf.master > smb.conf
      @@ -1170,7 +1170,7 @@
       Server role: ROLE_DOMAIN_PDC
       Press enter to see a dump of your service definitions
       

      -

    4. +

    5. Delete all runtime files from prior Samba operation by executing (for SUSE Linux):

      @@ -1179,9 +1179,9 @@
       root#  rm /var/lib/samba/*dat
       root#  rm /var/log/samba/*
       

      -

    6. - - +

    7. + + Samba-3 communicates with the LDAP server. The password that it uses to authenticate to the LDAP server must be stored in the secrets.tdb file. Execute the following to create the new secrets.tdb files @@ -1193,9 +1193,9 @@

       Setting stored password for "cn=Manager,dc=abmas,dc=biz" in secrets.tdb
       

      -

    8. - - +

    9. + + Samba-3 generates a Windows Security Identifier (SID) only when smbd has been started. For this reason, you start Samba. After a few seconds delay, execute: @@ -1226,13 +1226,13 @@ may be misconfigured. In this case, carefully check the smb.conf file for typographical errors (the most common problem). The use of the testparm is highly recommended to validate the contents of this file. -

    10. +

    11. When a positive domain SID has been reported, stop Samba. -

    12. - - - - +

    13. + + + + Configure the NFS server for your Linux system. So you can complete the steps that follow, enter into the /etc/exports the following entry:

      @@ -1250,8 +1250,8 @@
       		

    Your Samba-3 PDC is now ready to communicate with the LDAP password backend. Let's get on with configuration of the LDAP server. -

    Example 5.6. LDAP Based smb.conf File, Server: MASSIVE global Section: Part A

    # Global parameters
    [global]
    unix charset = LOCALE
    workgroup = MEGANET2
    netbios name = MASSIVE
    interfaces = eth1, lo
    bind interfaces only = Yes
    passdb backend = ldapsam:ldap://massive.abmas.biz
    enable privileges = Yes
    username map = /etc/samba/smbusers
    log level = 1
    syslog = 0
    log file = /var/log/samba/%m
    max log size = 50
    smb ports = 139
    name resolve order = wins bcast hosts
    time server = Yes
    printcap name = CUPS
    show add printer wizard = No
    add user script = /opt/IDEALX/sbin/smbldap-useradd -m "%u"
    delete user script = /opt/IDEALX/sbin/smbldap-userdel "%u"
    add group script = /opt/IDEALX/sbin/smbldap-groupadd -p "%g"
    delete group script = /opt/IDEALX/sbin/smbldap-groupdel "%g"
    add user to group script = /opt/IDEALX/sbin/smbldap-groupmod -m "%u" "%g"
    delete user from group script = /opt/IDEALX/sbin/smbldap-groupmod -x "%u" "%g"
    set primary group script = /opt/IDEALX/sbin/smbldap-usermod -g "%g" "%u"
    add machine script = /opt/IDEALX/sbin/smbldap-useradd -w "%u"

    Example 5.7. LDAP Based smb.conf File, Server: MASSIVE global Section: Part B

    logon script = scripts\logon.bat
    logon path = \\%L\profiles\%U
    logon drive = X:
    domain logons = Yes
    preferred master = Yes
    wins support = Yes
    ldap suffix = dc=abmas,dc=biz
    ldap machine suffix = ou=People
    ldap user suffix = ou=People
    ldap group suffix = ou=Groups
    ldap idmap suffix = ou=Idmap
    ldap admin dn = cn=Manager,dc=abmas,dc=biz
    idmap backend = ldap:ldap://massive.abmas.biz
    idmap uid = 10000-20000
    idmap gid = 10000-20000
    map acl inherit = Yes
    printing = cups
    printer admin = root, chrisr

Install and Configure Idealx smbldap-tools Scripts

- +

Example 5.6. LDAP Based smb.conf File, Server: MASSIVE global Section: Part A

# Global parameters
[global]
unix charset = LOCALE
workgroup = MEGANET2
netbios name = MASSIVE
interfaces = eth1, lo
bind interfaces only = Yes
passdb backend = ldapsam:ldap://massive.abmas.biz
enable privileges = Yes
username map = /etc/samba/smbusers
log level = 1
syslog = 0
log file = /var/log/samba/%m
max log size = 50
smb ports = 139
name resolve order = wins bcast hosts
time server = Yes
printcap name = CUPS
show add printer wizard = No
add user script = /opt/IDEALX/sbin/smbldap-useradd -m "%u"
delete user script = /opt/IDEALX/sbin/smbldap-userdel "%u"
add group script = /opt/IDEALX/sbin/smbldap-groupadd -p "%g"
delete group script = /opt/IDEALX/sbin/smbldap-groupdel "%g"
add user to group script = /opt/IDEALX/sbin/smbldap-groupmod -m "%u" "%g"
delete user from group script = /opt/IDEALX/sbin/smbldap-groupmod -x "%u" "%g"
set primary group script = /opt/IDEALX/sbin/smbldap-usermod -g "%g" "%u"
add machine script = /opt/IDEALX/sbin/smbldap-useradd -w "%u"

Example 5.7. LDAP Based smb.conf File, Server: MASSIVE global Section: Part B

logon script = scripts\logon.bat
logon path = \\%L\profiles\%U
logon drive = X:
domain logons = Yes
preferred master = Yes
wins support = Yes
ldap suffix = dc=abmas,dc=biz
ldap machine suffix = ou=People
ldap user suffix = ou=People
ldap group suffix = ou=Groups
ldap idmap suffix = ou=Idmap
ldap admin dn = cn=Manager,dc=abmas,dc=biz
idmap backend = ldap:ldap://massive.abmas.biz
idmap uid = 10000-20000
idmap gid = 10000-20000
map acl inherit = Yes
printing = cups
printer admin = root, chrisr

Install and Configure Idealx smbldap-tools Scripts

+ The Idealx scripts, or equivalent, are necessary to permit Samba-3 to manage accounts on the LDAP server. You have chosen the Idealx scripts because they are the best-known LDAP configuration scripts. The use of these scripts will help avoid the necessity @@ -1261,16 +1261,16 @@ from this site also. Alternatively, you may obtain the smbldap-tools-0.9.1-1.src.rpm file that may be used to build an installable RPM package for your Linux system. -

Note

+

Note

The smbldap-tools scripts can be installed in any convenient directory of your choice, in which case you must change the path to them in your smb.conf file on the PDC (MASSIVE).

The smbldap-tools are located in /opt/IDEALX/sbin. The scripts are not needed on BDC machines because all LDAP updates are handled by the PDC alone. -

Installation of smbldap-tools from the Tarball

+

Installation of smbldap-tools from the Tarball

To perform a manual installation of the smbldap-tools scripts, the following procedure may be used: -

Procedure 5.5. Unpacking and Installation Steps for the smbldap-tools Tarball

  1. +

    Procedure 5.5. Unpacking and Installation Steps for the smbldap-tools Tarball

    1. Create the /opt/IDEALX/sbin directory, and set its permissions and ownership as shown here:

      @@ -1281,11 +1281,11 @@
       root#  chown root:root /etc/smbldap-tools
       root#  chmod 755 /etc/smbldap-tools
       

      -

    2. +

    3. If you wish to use the downloaded tarball, unpack the smbldap-tools in a suitable temporary location. Change into either the directory extracted from the tarball or the smbldap-tools directory in your /usr/share/doc/packages directory tree. -

    4. +

    5. Copy all the smbldap-* and the configure.pl files into the /opt/IDEALX/sbin directory, as shown here:

      @@ -1297,7 +1297,7 @@
       root#  chmod 640 /etc/smbldap-tools/smbldap.conf
       root#  chmod 600 /etc/smbldap-tools/smbldap_bind.conf
       

      -

    6. +

    7. The smbldap-tools scripts master control file must now be configured. Change to the /opt/IDEALX/sbin directory, then edit the smbldap_tools.pm to affect the changes @@ -1310,7 +1310,7 @@ my $smbldap_bind_conf="/etc/smbldap-tools/smbldap_bind.conf"; ...

      -

    8. +

    9. To complete the configuration of the smbldap-tools, set the permissions and ownership by executing the following commands:

      @@ -1320,15 +1320,15 @@
       

      The smbldap-tools scripts are now ready for the configuration step outlined in “Configuration of smbldap-tools”. -

Installing smbldap-tools from the RPM Package

+

Installing smbldap-tools from the RPM Package

In the event that you have elected to use the RPM package provided by Idealx, download the source RPM smbldap-tools-0.9.1-1.src.rpm, then follow this procedure: -

Procedure 5.6. Installation Steps for smbldap-tools RPM's

  1. +

    Procedure 5.6. Installation Steps for smbldap-tools RPM's

    1. Install the source RPM that has been downloaded as follows:

       root#  rpm -i smbldap-tools-0.9.1-1.src.rpm
       

      -

    2. +

    3. Change into the directory in which the SPEC files are located. On SUSE Linux:

       root#  cd /usr/src/packages/SPECS
      @@ -1337,7 +1337,7 @@
       

       root#  cd /usr/src/redhat/SPECS
       

      -

    4. +

    5. Edit the smbldap-tools.spec file to change the value of the _sysconfig macro as shown here:

      @@ -1345,14 +1345,14 @@
       %define _sysconfdir /etc
       

      Note: Any suitable directory can be specified. -

    6. +

    7. Build the package by executing:

       root#  rpmbuild -ba -v smbldap-tools.spec
       

      A build process that has completed without error will place the installable binary files in the directory ../RPMS/noarch. -

    8. +

    9. Install the binary package by executing:

       root#  rpm -Uvh ../RPMS/noarch/smbldap-tools-0.9.1-1.noarch.rpm
      @@ -1360,7 +1360,7 @@
       		

    The Idealx scripts should now be ready for configuration using the steps outlined in Configuration of smbldap-tools. -

Configuration of smbldap-tools

+

Configuration of smbldap-tools

Prior to use, the smbldap-tools must be configured to match the settings in the smb.conf file and to match the settings in the /etc/openldap/slapd.conf file. The assumption is made that the smb.conf file has correct contents. The following procedure ensures that @@ -1368,12 +1368,12 @@

The smbldap-tools require that the NetBIOS name (machine name) of the Samba server be included in the smb.conf file. -

Procedure 5.7. Configuration Steps for smbldap-tools to Enable Use

  1. +

    Procedure 5.7. Configuration Steps for smbldap-tools to Enable Use

    1. Change into the directory that contains the configure.pl script.

       root#  cd /opt/IDEALX/sbin
       

      -

    2. +

    3. Execute the configure.pl script as follows:

       root#  ./configure.pl
      @@ -1469,12 +1469,12 @@
       		Since a slave LDAP server has not been configured, it is necessary to specify the IP
       		address of the master LDAP server for both the master and the slave configuration
       		prompts.
      -		

    4. +

    5. Change to the directory that contains the smbldap.conf file, then verify its contents.

    The smbldap-tools are now ready for use. -

LDAP Initialization and Creation of User and Group Accounts

+

LDAP Initialization and Creation of User and Group Accounts

The LDAP database must be populated with well-known Windows domain user accounts and domain group accounts before Samba can be used. The following procedures step you through the process.

@@ -1486,13 +1486,13 @@ does not need to ask LDAP.

Addition of an account to the LDAP backend can be done in two ways: -

  • - - - - - - +

    • + + + + + + If you always have a user account in the /etc/passwd on every server or in a NIS(+) backend, it is not necessary to add POSIX accounts for them in LDAP. In this case, you can add Windows domain user accounts using the @@ -1503,27 +1503,27 @@ expects the POSIX account to be in LDAP also. It is possible to use the PADL account migration tool to migrate all system accounts from either the /etc/passwd files, or from NIS, to LDAP. -

    • +

    • If you decide that it is probably a good idea to add both the PosixAccount attributes as well as the SambaSamAccount attributes for each user, then a suitable script is needed. In the example system you are installing in this exercise, you are making use of the Idealx smbldap-tools scripts. A copy of these tools, preconfigured for this system, is included on the enclosed CD-ROM under Chap06/Tools.

    - + If you wish to have more control over how the LDAP database is initialized or if you don't want to use the Idealx smbldap-tools, you should refer to “A Collection of Useful Tidbits”, “Alternative LDAP Database Initialization”.

    - + The following steps initialize the LDAP database, and then you can add user and group accounts that Samba can use. You use the smbldap-populate to seed the LDAP database. You then manually add the accounts shown in “Abmas Network Users and Groups”. The list of users does not cover all 500 network users; it provides examples only. -

    Note

    - - - +

    Note

    + + + In the following examples, as the LDAP database is initialized, we do create a container for Computer (machine) accounts. In the Samba-3 smb.conf files, specific use is made of the People container, not the Computers container, for domain member accounts. This is not a @@ -1540,15 +1540,15 @@ can be found. Alternatively, by placing all machine accounts in the People container, we are able to sidestep this limitation. This is the simpler solution that has been adopted in this chapter. -

    Table 5.3. Abmas Network Users and Groups

    Account NameTypeIDPassword
    Robert JordanUserbobjn3v3r2l8
    Stanley SorokaUserstansimpl13dst4r
    Christine RobersonUserchrisrS9n0nw4ll
    Mary VortexisUsermaryvkw13t0n3
    AccountsGroupAccounts 
    FinancesGroupFinances 
    InsuranceGroupPIOps 

    Procedure 5.8. LDAP Directory Initialization Steps

    1. +

    Table 5.3. Abmas Network Users and Groups

    Account NameTypeIDPassword
    Robert JordanUserbobjn3v3r2l8
    Stanley SorokaUserstansimpl13dst4r
    Christine RobersonUserchrisrS9n0nw4ll
    Mary VortexisUsermaryvkw13t0n3
    AccountsGroupAccounts 
    FinancesGroupFinances 
    InsuranceGroupPIOps 

    Procedure 5.8. LDAP Directory Initialization Steps

    1. Start the LDAP server by executing:

       root#  rcldap start
       Starting ldap-server                           done
       

      -

    2. +

    3. Change to the /opt/IDEALX/sbin directory. -

    4. +

    5. Execute the script that will populate the LDAP database as shown here:

       root#  ./smbldap-populate -a root -k 0 -m 0
      @@ -1579,7 +1579,7 @@
       adding new entry: cn=Backup Operators,ou=Groups,dc=abmas,dc=biz
       adding new entry: cn=Replicators,ou=Groups,dc=abmas,dc=biz
       

      -

    6. +

    7. Edit the /etc/smbldap-tools/smbldap.conf file so that the following information is changed from:

      @@ -1592,15 +1592,15 @@
       #sambaUnixIdPooldn="cn=NextFreeUnixId,${suffix}"
       sambaUnixIdPooldn="sambaDomainName=MEGANET2,dc=abmas,dc=biz"
       

      -

    8. +

    9. It is necessary to restart the LDAP server as shown here:

       root#  rcldap restart
       Shutting down ldap-server                            done
       Starting ldap-server                                 done
       

      -

    10. - +

    11. + So that we can use a global IDMAP repository, the LDAP directory must have a container object for IDMAP data. There are several ways you can check that your LDAP database is able to receive IDMAP information. One of the simplest is to execute: @@ -1609,7 +1609,7 @@ dn: ou=Idmap,dc=abmas,dc=biz ou: idmap

      - + If the execution of this command does not return IDMAP entries, you need to create an LDIF template file (see “LDIF IDMAP Add-On Load File File: /etc/openldap/idmap.LDIF”). You can add the required entries using the following command: @@ -1618,8 +1618,8 @@ -w not24get < /etc/openldap/idmap.LDIF

      Samba automatically populates this LDAP directory container when it needs to. -

    12. - +

    13. + It looks like all has gone well, as expected. Let's confirm that this is the case by running a few tests. First we check the contents of the database directly by running slapcat as follows (the output has been cut down): @@ -1656,8 +1656,8 @@ modifyTimestamp: 20031217234206Z

      This looks good so far. -

    14. - +

    15. + The next step is to prove that the LDAP server is running and responds to a search request. Execute the following as shown (output has been cut to save space):

      @@ -1701,8 +1701,8 @@
       # numEntries: 19
       

      Good. It is all working just fine. -

    16. - +

    17. + You must now make certain that the NSS resolver can interrogate LDAP also. Execute the following commands:

      @@ -1715,16 +1715,16 @@
       Domain Guests:x:514:
       Domain Computers:x:553:
       

      - + This demonstrates that the nss_ldap library is functioning as it should. If these two steps fail to produce this information, refer to “Avoiding Failures: Solving Problems Before They Happen” for diagnostic procedures that can be followed to isolate the cause of the problem. Proceed to the next step only when the previous steps have been successfully completed. -

    18. - - - +

    19. + + + Our database is now ready for the addition of network users. For each user for whom an account must be created, execute the following:

      @@ -1739,8 +1739,8 @@
       Retype new SMB password: XXXXXXXX
       

      where username is the login ID for each user. -

    20. - +

    21. + Now verify that the UNIX (POSIX) accounts can be resolved via NSS by executing the following:

      @@ -1756,7 +1756,7 @@
       maryv:x:1003:513:System User:/home/maryv:/bin/bash
       

      This demonstrates that user account resolution via LDAP is working. -

    22. +

    23. This step will determine whether or not identity resolution is working correctly. Do not procede is this step fails, rather find the cause of the failure. The id command may be used to validate your configuration so far, @@ -1767,8 +1767,8 @@

      This confirms that the UNIX (POSIX) user account information can be resolved from LDAP by system tools that make a getentpw() system call. -

    24. - +

    25. + The root account must have UID=0; if not, this means that operations conducted from a Windows client using tools such as the Domain User Manager fails under UNIX because the management of user and group accounts requires that the UID=0. Additionally, it is @@ -1779,7 +1779,7 @@ root# cd /opt/IDEALX/sbin root# ./smbldap-usermod -u 0 -d /root -s /bin/bash root

      -

    26. +

    27. Verify that the changes just made to the root account were accepted by executing:

      @@ -1788,7 +1788,7 @@
       root:x:0:512:Netbios Domain Administrator:/root:/bin/bash
       

      This demonstrates that the changes were accepted. -

    28. +

    29. Make certain that a home directory has been created for every user by listing the directories in /home as follows:

      @@ -1801,9 +1801,9 @@
       drwx------   7 stans  Domain Users     568 Dec 17 01:43 stans/
       

      This is precisely what we want to see. -

    30. - - +

    31. + + The final validation step involves making certain that Samba-3 can obtain the user accounts from the LDAP ldapsam passwd backend. Execute the following command as shown:

      @@ -1833,8 +1833,8 @@
       Logon hours         : FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF
       

      This looks good. Of course, you fully expected that it would all work, didn't you? -

    32. - +

    33. + Now you add the group accounts that are used on the Abmas network. Execute the following exactly as shown:

      @@ -1844,8 +1844,8 @@
       

      The addition of groups does not involve keyboard interaction, so the lack of console output is of no concern. -

    34. - +

    35. + You really do want to confirm that UNIX group resolution from LDAP is functioning as it should. Let's do this as shown here:

      @@ -1861,8 +1861,8 @@
       

      The well-known special accounts (Domain Admins, Domain Users, Domain Guests), as well as our own site-specific group accounts, are correctly listed. This is looking good. -

    36. - +

    37. + The final step we need to validate is that Samba can see all the Windows domain groups and that they are correctly mapped to the respective UNIX group account. To do this, just execute the following command: @@ -1879,7 +1879,7 @@ This is looking good. Congratulations it works! Note that in the above output the lines were shortened by replacing the middle value (1010554828) of the SID with the ellipsis (...). -

    38. +

    39. The server you have so carefully built is now ready for another important step. You start the Samba-3 server and validate its operation. Execute the following to render all the processes needed fully operative so that, on system reboot, they are automatically @@ -1895,7 +1895,7 @@ root# rcsmb start root# rcwinbind start

      -

    40. +

    41. The next step might seem a little odd at this point, but take note that you are about to start winbindd, which must be able to authenticate to the PDC via the localhost interface with the smbd process. This account can be @@ -1910,14 +1910,14 @@ Joined domain MEGANET2.

      This indicates that the domain security account for the PDC has been correctly created. -

    42. +

    43. At this time it is necessary to restart winbindd so that it can correctly authenticate to the PDC. The following command achieves that:

       root#  rcwinbind restart
       

      -

    44. - +

    45. + You may now check Samba-3 operation as follows:

       root#  smbclient -L massive -U%
      @@ -1943,7 +1943,7 @@
               MEGANET2             MASSIVE
       

      This shows that an anonymous connection is working. -

    46. +

    47. For your finale, let's try an authenticated connection:

       root#  smbclient //massive/bobj -Ubobj%n3v3r2l8
      @@ -1962,47 +1962,47 @@
       		Well done. All is working fine.
       		

    The server MASSIVE is now configured, and it is time to move onto the next task. -

    Printer Configuration

    - +

    Printer Configuration

    + The configuration for Samba-3 to enable CUPS raw-print-through printing has already been taken care of in the smb.conf file. The only preparation needed for smart printing to be possible involves creation of the directories in which Samba-3 stores Windows printing driver files. -

    Procedure 5.9. Printer Configuration Steps

    1. +

      Procedure 5.9. Printer Configuration Steps

      1. Configure all network-attached printers to have a fixed IP address. -

      2. +

      3. Create an entry in the DNS database on the server MASSIVE in both the forward lookup database for the zone abmas.biz.hosts and in the reverse lookup database for the network segment that the printer is to be located in. Example configuration files for similar zones were presented in “Secure Office Networking”, “DNS Abmas.biz Forward Zone File” and in “DNS 192.168.2 Reverse Zone File”. -

      4. +

      5. Follow the instructions in the printer manufacturers' manuals to permit printing to port 9100. Use any other port the manufacturer specifies for direct mode, raw printing. This allows the CUPS spooler to print using raw mode protocols. - - -

      6. - - + + +

      7. + + Only on the server to which the printer is attached, configure the CUPS Print Queues as follows:

         root#  lpadmin -p printque
         	 -v socket://printer-name.abmas.biz:9100 -E
         

        - + This step creates the necessary print queue to use no assigned print filter. This is ideal for raw printing, that is, printing without use of filters. The name printque is the name you have assigned for the particular printer. -

      8. +

      9. Print queues may not be enabled at creation. Make certain that the queues you have just created are enabled by executing the following:

         root#  /usr/bin/enable printque
         

        -

      10. +

      11. Even though your print queue may be enabled, it is still possible that it may not accept print jobs. A print queue will service incoming printing requests only when configured to do so. Ensure that your print queue is @@ -2010,27 +2010,27 @@

         root#  /usr/bin/accept printque
         

        -

      12. - - - +

      13. + + + Edit the file /etc/cups/mime.convs to uncomment the line:

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

        -

      14. - +

      15. + Edit the file /etc/cups/mime.types to uncomment the line:

         application/octet-stream
         

        -

      16. +

      17. Refer to the CUPS printing manual for instructions regarding how to configure CUPS so that print queues that reside on CUPS servers on remote networks route print jobs to the print server that owns that queue. The default setting on your CUPS server may automatically discover remotely installed printers and may permit this functionality without requiring specific configuration. -

      18. +

      19. The following action creates the necessary directory subsystem. Follow these steps to printing heaven:

        @@ -2038,17 +2038,17 @@
         root#  chown -R root:root /var/lib/samba/drivers
         root#  chmod -R ug=rwx,o=rx /var/lib/samba/drivers
         

        -

    Samba-3 BDC Configuration

    Procedure 5.10. Configuration of BDC Called: BLDG1

    1. +

Samba-3 BDC Configuration

Procedure 5.10. Configuration of BDC Called: BLDG1

  1. Install the files in “LDAP Based smb.conf File, Server: BLDG1”, “LDAP Based smb.conf File, Shares Section Part A”, and “LDAP Based smb.conf File, Shares Section Part B” into the /etc/samba/ directory. The three files should be added together to form the smb.conf file. -

  2. +

  3. Verify the smb.conf file as in step 2 of “Samba-3 PDC Configuration”. -

  4. +

  5. Carefully follow the steps outlined in “PAM and NSS Client Configuration”, taking particular note to install the correct ldap.conf. -

  6. +

  7. Verify that the NSS resolver is working. You may need to cycle the run level to 1 and back to 5 before the NSS LDAP resolver functions. Follow these commands: @@ -2080,8 +2080,8 @@ bldg1$:x:1006:553:bldg1$:/dev/null:/bin/false

    This is the correct output. If the accounts that have UIDs above 512 are not shown, there is a problem. -

  8. - +

  9. + The next step in the verification process involves testing the operation of UNIX group resolution via the NSS LDAP resolver. Execute these commands:

    @@ -2110,15 +2110,15 @@
     

    This is also the correct and desired output, because it demonstrates that the LDAP client is able to communicate correctly with the LDAP server (MASSIVE). -

  10. - +

  11. + You must now set the LDAP administrative password into the Samba-3 secrets.tdb file by executing this command:

     root#  smbpasswd -w not24get
     Setting stored password for "cn=Manager,dc=abmas,dc=biz" in secrets.tdb
     

    -

  12. +

  13. Now you must obtain the domain SID from the PDC and store it into the secrets.tdb file also. This step is not necessary with an LDAP passdb backend because Samba-3 obtains the domain SID from the @@ -2135,15 +2135,15 @@ domain controller that is running on the localhost and must be able to authenticate, thus requiring that the BDC should be joined to the domain. The process of joining the domain creates the necessary authentication accounts. -

  14. +

  15. To join the Samba BDC to the domain, execute the following:

     root#  net rpc join -U root%not24get
     Joined domain MEGANET2.
     

    This indicates that the domain security account for the BDC has been correctly created. -

  16. - +

  17. + Verify that user and group account resolution works via Samba-3 tools as follows:

     root#  pdbedit -L
    @@ -2169,7 +2169,7 @@
     PIOps (S-1-5-21-3504140859-1010554828-2431957765-3005) -> PIOps
     

    These results show that all things are in order. -

  18. +

  19. The server you have so carefully built is now ready for another important step. Now start the Samba-3 server and validate its operation. Execute the following to render all the processes needed fully operative so that, upon system reboot, they are automatically @@ -2185,7 +2185,7 @@ root# rcwinbind start

    Samba-3 should now be running and is ready for a quick test. But not quite yet! -

  20. +

  21. Your new BLDG1, BLDG2 servers do not have home directories for users. To rectify this using the SUSE yast2 utility or by manually editing the /etc/fstab file, add a mount entry to mount the home directory that has been exported @@ -2205,7 +2205,7 @@ root# df | grep home massive:/home 29532988 283388 29249600 1% /home

    -

  22. +

  23. Implement a quick check using one of the users that is in the LDAP database. Here you go:

     root#  smbclient //bldg1/bobj -Ubobj%n3v3r2l8
    @@ -2224,26 +2224,26 @@
     		

Now that the first BDC (BDLG1) has been configured it is time to build and configure the second BDC server (BLDG2) as follows: -

Procedure 5.11. Configuration of BDC Called BLDG2

  1. +

    Procedure 5.11. Configuration of BDC Called BLDG2

    1. Install the files in “LDAP Based smb.conf File, Server: BLDG2”, “LDAP Based smb.conf File, Shares Section Part A”, and “LDAP Based smb.conf File, Shares Section Part B” into the /etc/samba/ directory. The three files should be added together to form the smb.conf file. -

    2. +

    3. Follow carefully the steps shown in “Samba-3 BDC Configuration”, starting at step 2. -

    Example 5.8. LDAP Based smb.conf File, Server: BLDG1

    # Global parameters
    [global]
    unix charset = LOCALE
    workgroup = MEGANET2
    netbios name = BLDG1
    passdb backend = ldapsam:ldap://massive.abmas.biz
    enable privileges = Yes
    username map = /etc/samba/smbusers
    log level = 1
    syslog = 0
    log file = /var/log/samba/%m
    max log size = 50
    smb ports = 139
    name resolve order = wins bcast hosts
    printcap name = CUPS
    show add printer wizard = No
    logon script = scripts\logon.bat
    logon path = \\%L\profiles\%U
    logon drive = X:
    domain logons = Yes
    domain master = No
    wins server = 172.16.0.1
    ldap suffix = dc=abmas,dc=biz
    ldap machine suffix = ou=People
    ldap user suffix = ou=People
    ldap group suffix = ou=Groups
    ldap idmap suffix = ou=Idmap
    ldap admin dn = cn=Manager,dc=abmas,dc=biz
    idmap backend = ldap:ldap://massive.abmas.biz
    idmap uid = 10000-20000
    idmap gid = 10000-20000
    printing = cups
    printer admin = root, chrisr

    Example 5.9. LDAP Based smb.conf File, Server: BLDG2

    # Global parameters
    [global]
    unix charset = LOCALE
    workgroup = MEGANET2
    netbios name = BLDG2
    passdb backend = ldapsam:ldap://massive.abmas.biz
    enable privileges = Yes
    username map = /etc/samba/smbusers
    log level = 1
    syslog = 0
    log file = /var/log/samba/%m
    max log size = 50
    smb ports = 139
    name resolve order = wins bcast hosts
    printcap name = CUPS
    show add printer wizard = No
    logon script = scripts\logon.bat
    logon path = \\%L\profiles\%U
    logon drive = X:
    domain logons = Yes
    domain master = No
    wins server = 172.16.0.1
    ldap suffix = dc=abmas,dc=biz
    ldap machine suffix = ou=People
    ldap user suffix = ou=People
    ldap group suffix = ou=Groups
    ldap idmap suffix = ou=Idmap
    ldap admin dn = cn=Manager,dc=abmas,dc=biz
    idmap backend = ldap:ldap://massive.abmas.biz
    idmap uid = 10000-20000
    idmap gid = 10000-20000
    printing = cups
    printer admin = root, chrisr

    Example 5.10. LDAP Based smb.conf File, Shares Section Part A

    [accounts]
    comment = Accounting Files
    path = /data/accounts
    read only = No
    [service]
    comment = Financial Services Files
    path = /data/service
    read only = No
    [pidata]
    comment = Property Insurance Files
    path = /data/pidata
    read only = No
    [homes]
    comment = Home Directories
    valid users = %S
    read only = No
    browseable = No
    [printers]
    comment = SMB Print Spool
    path = /var/spool/samba
    guest ok = Yes
    printable = Yes
    browseable = No

    Example 5.11. LDAP Based smb.conf File, Shares Section Part B

    [apps]
    comment = Application Files
    path = /apps
    admin users = bjordan
    read only = No
    [netlogon]
    comment = Network Logon Service
    path = /var/lib/samba/netlogon
    guest ok = Yes
    locking = No
    [profiles]
    comment = Profile Share
    path = /var/lib/samba/profiles
    read only = No
    profile acls = Yes
    [profdata]
    comment = Profile Data Share
    path = /var/lib/samba/profdata
    read only = No
    profile acls = Yes
    [print$]
    comment = Printer Drivers
    path = /var/lib/samba/drivers
    browseable = yes
    guest ok = no
    read only = yes
    write list = root, chrisr

    Example 5.12. LDIF IDMAP Add-On Load File File: /etc/openldap/idmap.LDIF

    +		

Example 5.8. LDAP Based smb.conf File, Server: BLDG1

# Global parameters
[global]
unix charset = LOCALE
workgroup = MEGANET2
netbios name = BLDG1
passdb backend = ldapsam:ldap://massive.abmas.biz
enable privileges = Yes
username map = /etc/samba/smbusers
log level = 1
syslog = 0
log file = /var/log/samba/%m
max log size = 50
smb ports = 139
name resolve order = wins bcast hosts
printcap name = CUPS
show add printer wizard = No
logon script = scripts\logon.bat
logon path = \\%L\profiles\%U
logon drive = X:
domain logons = Yes
domain master = No
wins server = 172.16.0.1
ldap suffix = dc=abmas,dc=biz
ldap machine suffix = ou=People
ldap user suffix = ou=People
ldap group suffix = ou=Groups
ldap idmap suffix = ou=Idmap
ldap admin dn = cn=Manager,dc=abmas,dc=biz
idmap backend = ldap:ldap://massive.abmas.biz
idmap uid = 10000-20000
idmap gid = 10000-20000
printing = cups
printer admin = root, chrisr

Example 5.9. LDAP Based smb.conf File, Server: BLDG2

# Global parameters
[global]
unix charset = LOCALE
workgroup = MEGANET2
netbios name = BLDG2
passdb backend = ldapsam:ldap://massive.abmas.biz
enable privileges = Yes
username map = /etc/samba/smbusers
log level = 1
syslog = 0
log file = /var/log/samba/%m
max log size = 50
smb ports = 139
name resolve order = wins bcast hosts
printcap name = CUPS
show add printer wizard = No
logon script = scripts\logon.bat
logon path = \\%L\profiles\%U
logon drive = X:
domain logons = Yes
domain master = No
wins server = 172.16.0.1
ldap suffix = dc=abmas,dc=biz
ldap machine suffix = ou=People
ldap user suffix = ou=People
ldap group suffix = ou=Groups
ldap idmap suffix = ou=Idmap
ldap admin dn = cn=Manager,dc=abmas,dc=biz
idmap backend = ldap:ldap://massive.abmas.biz
idmap uid = 10000-20000
idmap gid = 10000-20000
printing = cups
printer admin = root, chrisr

Example 5.10. LDAP Based smb.conf File, Shares Section Part A

[accounts]
comment = Accounting Files
path = /data/accounts
read only = No
[service]
comment = Financial Services Files
path = /data/service
read only = No
[pidata]
comment = Property Insurance Files
path = /data/pidata
read only = No
[homes]
comment = Home Directories
valid users = %S
read only = No
browseable = No
[printers]
comment = SMB Print Spool
path = /var/spool/samba
guest ok = Yes
printable = Yes
browseable = No

Example 5.11. LDAP Based smb.conf File, Shares Section Part B

[apps]
comment = Application Files
path = /apps
admin users = bjordan
read only = No
[netlogon]
comment = Network Logon Service
path = /var/lib/samba/netlogon
guest ok = Yes
locking = No
[profiles]
comment = Profile Share
path = /var/lib/samba/profiles
read only = No
profile acls = Yes
[profdata]
comment = Profile Data Share
path = /var/lib/samba/profdata
read only = No
profile acls = Yes
[print$]
comment = Printer Drivers
path = /var/lib/samba/drivers
browseable = yes
guest ok = no
read only = yes
write list = root, chrisr

Example 5.12. LDIF IDMAP Add-On Load File File: /etc/openldap/idmap.LDIF

 dn: ou=Idmap,dc=abmas,dc=biz
 objectClass: organizationalUnit
 ou: idmap
 structuralObjectClass: organizationalUnit
-

Miscellaneous Server Preparation Tasks

- My father would say, Dinner is not over until the dishes have been done. +


Miscellaneous Server Preparation Tasks

+ My father would say, “Dinner is not over until the dishes have been done.” The makings of a great network environment take a lot of effort and attention to detail. So far, you have completed most of the complex (and to many administrators, the interesting part of server configuration) steps, but remember to tie it all together. Here are a few more steps that must be completed so that your network runs like a well-rehearsed orchestra. -

Configuring Directory Share Point Roots

+

Configuring Directory Share Point Roots

In your smb.conf file, you have specified Windows shares. Each has a path parameter. Even though it is obvious to all, one of the common Samba networking problems is caused by forgetting to verify that every such share root directory actually exists and that it @@ -2261,7 +2261,7 @@ root# chmod -R ug+rwxs,o-rwx /data root# chmod -R ug+rwx,o+rx-w /apps

-

Configuring Profile Directories

+

Configuring Profile Directories

You made a conscious decision to do everything it would take to improve network client performance. One of your decisions was to implement folder redirection. This means that Windows user desktop profiles are now made up of two components: a dynamically loaded part and a set of file @@ -2286,17 +2286,17 @@ root# chmod -R 750 username

- - + + You have three options insofar as the dynamically loaded portion of the roaming profile is concerned: -

  • You may permit the user to obtain a default profile.

  • You can create a mandatory profile.

  • You can create a group profile (which is almost always a mandatory profile).

+

  • You may permit the user to obtain a default profile.

  • You can create a mandatory profile.

  • You can create a group profile (which is almost always a mandatory profile).

Mandatory profiles cannot be overwritten by a user. The change from a user profile to a mandatory profile is effected by renaming the NTUSER.DAT to NTUSER.MAN, that is, just by changing the filename extension.

- - + + The location of the profile that a user can obtain is set in the user's account in the LDAP passdb backend. You can manage this using the Idealx smbldap-tools or using the Windows NT4 Domain User Manager. @@ -2309,8 +2309,8 @@ /var/lib/samba/profiles/username root# chmod 700 /var/lib/samba/profiles/username

-

Preparation of Logon Scripts

- +

Preparation of Logon Scripts

+ The use of a logon script with Windows XP Professional is an option that every site should consider. Unless you have locked down the desktop so the user cannot change anything, there is risk that a vital network drive setting may be broken or that printer connections may be lost. Logon scripts @@ -2335,7 +2335,7 @@ You should research the options for logon script implementation by referring to TOSHARG2, Chapter 24, Section 24.4. A quick Web search will bring up a host of options. One of the most popular logon facilities in use today is called KiXtart. -

Assigning User Rights and Privileges

+

Assigning User Rights and Privileges

The ability to perform tasks such as joining Windows clients to the domain can be assigned to normal user accounts. By default, only the domain administrator account (root on UNIX systems because it has UID=0) can add accounts. New to Samba 3.0.11 is the ability to grant @@ -2347,9 +2347,9 @@ Samba limits privileges on a per-server basis. This is a deliberate limitation so that users who are granted rights can be restricted to particular machines. It is left to the network administrator to determine which rights should be provided and to whom. -

Procedure 5.12. Steps for Assignment of User Rights and Privileges

  1. +

    Procedure 5.12. Steps for Assignment of User Rights and Privileges

    1. Log onto the PDC as the root account. -

    2. +

    3. Execute the following command to grant the Domain Admins group all rights and privileges:

      @@ -2361,7 +2361,7 @@
       

      Repeat this step on each domain controller, in each case substituting the name of the server (e.g., BLDG1, BLDG2) in place of the PDC called MASSIVE. -

    4. +

    5. In this step the privilege will be granted to Bob Jordan (bobj) to add Windows workstations to the domain. Execute the following only on the PDC. It is not necessary to do this on BDCs or on DMS machines because machine accounts are only ever added by the PDC: @@ -2370,7 +2370,7 @@ "MEGANET2\bobj" SeMachineAccountPrivilege Successfully granted rights.

      -

    6. +

    7. Verify that privilege assignments have been correctly applied by executing:

       net rpc rights list accounts -Uroot%not24get
      @@ -2405,8 +2405,8 @@
       SeRemoteShutdownPrivilege
       SeDiskOperatorPrivilege
       

      -

Windows Client Configuration

- +

Windows Client Configuration

+ In the next few sections, you can configure a new Windows XP Professional disk image on a staging machine. You will configure all software, printer settings, profile and policy handling, and desktop default profile settings on this system. When it is complete, you copy the contents of the @@ -2418,60 +2418,60 @@ "How to Create a Base Profile for All Users." -

Configuration of Default Profile with Folder Redirection

- +

Configuration of Default Profile with Folder Redirection

+ Log onto the Windows XP Professional workstation as the local Administrator. It is necessary to expose folders that are generally hidden to provide access to the Default User folder. -

Procedure 5.13. Expose Hidden Folders

  1. +

    Procedure 5.13. Expose Hidden Folders

    1. Launch the Windows Explorer by clicking StartMy ComputerToolsFolder OptionsView Tab. Select Show hidden files and folders, and click OK. Exit Windows Explorer. -

    2. - +

    3. + Launch the Registry Editor. Click StartRun. Key in regedt32, and click OK.

    -

    Procedure 5.14. Redirect Folders in Default System User Profile

    1. - - +

      Procedure 5.14. Redirect Folders in Default System User Profile

      1. + + Give focus to HKEY_LOCAL_MACHINE hive entry in the left panel. Click FileLoad Hive...Documents and SettingsDefault UserNTUSEROpen. In the dialog box that opens, enter the key name Default and click OK. -

      2. +

      3. Browse inside the newly loaded Default folder to:

         HKEY_LOCAL_MACHINE\Default\Software\Microsoft\Windows\
                              CurrentVersion\Explorer\User Shell Folders\
         

        The right panel reveals the contents as shown in “Windows XP Professional User Shared Folders”. -

      4. - - +

      5. + + You edit hive keys. Acceptable values to replace the %USERPROFILE% variable includes: -

        • A drive letter such as U:

        • A direct network path such as - \\MASSIVE\profdata

        • A network redirection (UNC name) that contains a macro such as

          %LOGONSERVER%\profdata\

        -

      6. - +

        • A drive letter such as U:

        • A direct network path such as + \\MASSIVE\profdata

        • A network redirection (UNC name) that contains a macro such as

          %LOGONSERVER%\profdata\

        +

      7. + Set the registry keys as shown in “Default Profile Redirections”. Your implementation makes the assumption that users have statically located machines. Notebook computers (mobile users) need to be accommodated using local profiles. This is not an uncommon assumption. -

      8. +

      9. Click back to the root of the loaded hive Default. Click FileUnload Hive...Yes. -

      10. - +

      11. + Click FileExit. This exits the Registry Editor. -

      12. +

      13. Now follow the procedure given in “The Local Group Policy”. Make sure that each folder you have redirected is in the exclusion list. -

      14. - You are now ready to copy[11] +

      15. + You are now ready to copy[11] the Default User profile to the Samba domain controllers. Launch Microsoft Windows Explorer, and use it to copy the full contents of the directory Default User that is in the C:\Documents and Settings to the root directory of the @@ -2482,14 +2482,14 @@ Before punching out new desktop images for the client workstations, it is perhaps a good idea that desktop behavior should be returned to the original Microsoft settings. The following steps achieve that ojective: -

        Procedure 5.15. Reset Folder Display to Original Behavior

        • +

          Procedure 5.15. Reset Folder Display to Original Behavior

          • To launch the Windows Explorer, click StartMy ComputerToolsFolder OptionsView Tab. Deselect Show hidden files and folders, and click OK. Exit Windows Explorer. -

          Figure 5.3. Windows XP Professional User Shared Folders

          Windows XP Professional User Shared Folders

          Table 5.4. Default Profile Redirections

          Registry KeyRedirected Value
          Cache%LOGONSERVER%\profdata\%USERNAME%\InternetFiles
          Cookies%LOGONSERVER%\profdata\%USERNAME%\Cookies
          History%LOGONSERVER%\profdata\%USERNAME%\History
          Local AppData%LOGONSERVER%\profdata\%USERNAME%\AppData
          Local Settings%LOGONSERVER%\profdata\%USERNAME%\LocalSettings
          My Pictures%LOGONSERVER%\profdata\%USERNAME%\MyPictures
          Personal%LOGONSERVER%\profdata\%USERNAME%\MyDocuments
          Recent%LOGONSERVER%\profdata\%USERNAME%\Recent

        Configuration of MS Outlook to Relocate PST File

        - - +

      Figure 5.3. Windows XP Professional User Shared Folders

      Windows XP Professional User Shared Folders

      Table 5.4. Default Profile Redirections

      Registry KeyRedirected Value
      Cache%LOGONSERVER%\profdata\%USERNAME%\InternetFiles
      Cookies%LOGONSERVER%\profdata\%USERNAME%\Cookies
      History%LOGONSERVER%\profdata\%USERNAME%\History
      Local AppData%LOGONSERVER%\profdata\%USERNAME%\AppData
      Local Settings%LOGONSERVER%\profdata\%USERNAME%\LocalSettings
      My Pictures%LOGONSERVER%\profdata\%USERNAME%\MyPictures
      Personal%LOGONSERVER%\profdata\%USERNAME%\MyDocuments
      Recent%LOGONSERVER%\profdata\%USERNAME%\Recent

    Configuration of MS Outlook to Relocate PST File

    + + Microsoft Outlook can store a Personal Storage file, generally known as a PST file. It is the nature of email storage that this file grows, at times quite rapidly. So that users' email is available to them at every workstation they may log onto, @@ -2498,19 +2498,19 @@

    To redirect the Outlook PST file in Outlook 2003 (older versions of Outlook behave slightly differently), follow these steps: -

    Procedure 5.16. Outlook PST File Relocation

    1. +

      Procedure 5.16. Outlook PST File Relocation

      1. Close Outlook if it is open. -

      2. +

      3. From the Control Panel, launch the Mail icon. -

      4. +

      5. Click Email Accounts. -

      6. +

      7. Make a note of the location of the PST file(s). From this location, move the files to the desired new target location. The most desired new target location may well be the users' home directory. -

      8. +

      9. Add a new data file, selecting the PST file in the new desired target location. - Give this entry (not the filename) a new name such as Personal Mail Folders. + Give this entry (not the filename) a new name such as “Personal Mail Folders.

        Note: If MS Outlook has been configured to use an IMAP account configuration there may be problems following these instructions. Feedback from users suggests that where IMAP is used the PST @@ -2518,21 +2518,21 @@ MS Outlook's Send/Receive button. If anyone has sucessfully relocated PST files where IMAP is used please email jht@samba.org with useful tips and suggestions so that this warning can be removed or modified. -

      10. +

      11. Close the Date Files windows, then click Email Accounts. -

      12. +

      13. Select View of Change exiting email accounts, click Next. -

      14. +

      15. Change the Mail Delivery Location so as to use the data file in the new target location. -

      16. +

      17. Go back to the Data Files window, then delete the old data file entry. -

      Note

      - +

    Note

    + You may have to remove and reinstall the Outlook Address Book (Contacts) entries, otherwise the user may be not be able to retrieve contacts when addressing a new email message. -

    Note

    - +

    Note

    + Outlook Express is not at all like MS OutLook. It stores file very differently also. Outlook Express storage files can not be redirected to network shares. The options panel will not permit this, but they can be moved to folders outside of the user's profile. They can also be excluded @@ -2541,34 +2541,34 @@ While it is possible to redirect the data stores for Outlook Express data stores by editing the registry, experience has shown that data corruption and loss of email messages will result.

    - - + + In the same vane as MS Outlook, Outlook Express data stores can become very large. When used with roaming profiles this can result in excruciatingly long login and logout behavior will files are synchronized. For this reason, it is highly recommended not to use Outlook Express where roaming profiles are used.

    - + Microsoft does not support storing PST files on network shares, although the practice does appear to be rather popular. Anyone who does relocation the PST file to a network resource should refer the Microsoft reference to better understand the issues.

    - + Apart from manually moving PST files to a network share, it is possible to set the default PST location for new accounts by following the instructions at the WindowsITPro web site.

    - + User feedback suggests that disabling of oplocks on PST files will significantly improve network performance by reducing locking overheads. One way this can be done is to add to the smb.conf file stanza for the share the PST file the following:

     veto oplock files = /*.pdf/*.PST/
     

    -

    Configure Delete Cached Profiles on Logout

    +

    Configure Delete Cached Profiles on Logout

    Configure the Windows XP Professional client to auto-delete roaming profiles on logout:

    - + Click StartRun. In the dialog box, enter MMC and click OK.

    @@ -2576,94 +2576,94 @@ profiles are deleted as network users log out of the system. Click FileAdd/Remove Snap-inAddGroup PolicyAddFinishCloseOK.

    - + The Microsoft Management Console now shows the Group Policy utility that enables you to set the policies needed. In the left panel, click Local Computer PolicyAdministrative TemplatesSystemUser Profiles. In the right panel, set the properties shown here by double-clicking on each item as shown: -

    • Do not check for user ownership of Roaming Profile Folders = Enabled

    • Delete cached copies of roaming profiles = Enabled

    +

    • Do not check for user ownership of Roaming Profile Folders = Enabled

    • Delete cached copies of roaming profiles = Enabled

    Close the Microsoft Management Console. The settings take immediate effect and persist onto all image copies made of this system to deploy the new standard desktop system. -

    Uploading Printer Drivers to Samba Servers

    - +

    Uploading Printer Drivers to Samba Servers

    + Users want to be able to use network printers. You have a vested interest in making it easy for them to print. You have chosen to install the printer drivers onto the Samba servers and to enable point-and-click (drag-and-drop) printing. This process results in Samba being able to automatically provide the Windows client with the driver necessary to print to the printer chosen. The following procedure must be followed for every network printer: -

    Procedure 5.17. Steps to Install Printer Drivers on the Samba Servers

    1. +

      Procedure 5.17. Steps to Install Printer Drivers on the Samba Servers

      1. Join your Windows XP Professional workstation (the staging machine) to the MEGANET2 domain. If you are not sure of the procedure, follow the guidance given in “A Collection of Useful Tidbits”, “Joining a Domain: Windows 200x/XP Professional”. -

      2. +

      3. After the machine has rebooted, log onto the workstation as the domain root (this is the Administrator account for the operating system that is the host platform for this implementation of Samba. -

      4. +

      5. Launch MS Windows Explorer. Navigate in the left panel. Click My Network PlacesEntire NetworkMicrosoft Windows NetworkMeganet2Massive. Click on Massive Printers and Faxes. -

      6. +

      7. Identify a printer that is shown in the right panel. Let us assume the printer is called ps01-color. Right-click on the ps01-color icon and select the Properties entry. This opens a dialog box that indicates - that The printer driver is not installed on this computer. Some printer properties + that “The printer driver is not installed on this computer. Some printer properties will not be accessible unless you install the printer driver. Do you want to install the - driver now? It is important at this point you answer No. -

      8. + driver now?” It is important at this point you answer No. +

      9. The printer properties panel for the ps01-color printer on the server MASSIVE is displayed. Click the Advanced tab. Note that the box labeled Driver is empty. Click the New Driver - button that is next to the Driver box. This launches the Add Printer Wizard. -

      10. - - - The Add Printer Driver Wizard on MASSIVE panel + button that is next to the Driver box. This launches the “Add Printer Wizard”. +

      11. + + + The “Add Printer Driver Wizard on MASSIVE” panel is now presented. Click Next to continue. From the left panel, select the printer manufacturer. In your case, you are adding a driver for a printer manufactured by Lexmark. In the right panel, select the printer (Lexmark Optra Color 40 PS). Click Next, and then Finish to commence driver upload. A progress bar appears and instructs you as each file is being uploaded and that it is being directed at the network server \\massive\ps01-color. -

      12. - - - - - - +

      13. + + + + + + The driver upload completes in anywhere from a few seconds to a few minutes. When it completes, you are returned to the Advanced tab in the Properties panel. You can set the Location (under the General tab) and Security settings (under the Security tab). Under the Sharing tab it is possible to - load additional printer drivers; there is also a check-box in this tab called List in the - directory. When this box is checked, the printer will be published in Active Directory + load additional printer drivers; there is also a check-box in this tab called “List in the + directory”. When this box is checked, the printer will be published in Active Directory (Applicable to Active Directory use only.) -

      14. - +

      15. + Click OK. It will take a minute or so to upload the settings to the server. You are now returned to the Printers and Faxes on Massive monitor. Right-click on the printer, click PropertiesDevice Settings. Now change the settings to suit your requirements. BE CERTAIN TO CHANGE AT LEAST ONE SETTING and apply the changes even if you need to reverse the changes back to their original settings. -

      16. +

      17. This is necessary so that the printer settings are initialized in the Samba printers database. Click Apply to commit your settings. Revert any settings you changed just to initialize the Samba printers database entry for this printer. If you need to revert a setting, click Apply again. -

      18. - +

      19. + Verify that all printer settings are at the desired configuration. When you are satisfied that they are, click the General tab. Now click the Print Test Page button. A test page should print. Verify that it has printed correctly. Then click OK in the panel that is newly presented. Click OK on the ps01-color on massive Properties panel. -

      20. +

      21. You must repeat this process for all network printers (i.e., for every printer on each server). When you have finished uploading drivers to all printers, close all applications. The next task is to install software your users require to do their work. -

    Software Installation

    +

Software Installation

Your network has both fixed desktop workstations as well as notebook computers. As a general rule, it is a good idea to not tamper with the operating system that is provided by the notebook computer manufacturer. Notebooks require special handling that is beyond the scope of this chapter. @@ -2678,7 +2678,7 @@ When you believe that the overall configuration is complete, be sure to create a shared group profile and migrate that to the Samba server for later reuse when creating custom mandatory profiles, just in case a user may have specific needs you had not anticipated. -

Roll-out Image Creation

+

Roll-out Image Creation

The final steps before preparing the distribution Norton Ghost image file you might follow are:

Unjoin the domain Each workstation requires a unique name and must be independently @@ -2687,7 +2687,7 @@ Defragment the hard disk While not obvious to the uninitiated, defragmentation results in better performance and often significantly reduces the size of the compressed disk image. That also means it will take less time to deploy the image onto 500 workstations. -

Key Points Learned

+

Key Points Learned

This chapter introduced many new concepts. Is it a sad fact that the example presented deliberately avoided any consideration of security. Security does not just happen; you must design it into your total network. Security begins with a systems design and implementation that anticipates hostile behavior from @@ -2696,8 +2696,8 @@ practices, you must not deploy the design presented in this book in an environment where there is risk of compromise.

- - + + As a minimum, the LDAP server must be protected by way of Access Control Lists (ACLs), and it must be configured to use secure protocols for all communications over the network. Of course, secure networking does not result just from systems design and implementation but involves constant user education @@ -2708,53 +2708,53 @@ as well as security considerations.

The substance of this chapter that has been deserving of particular attention includes: -

  • +

    • Implementation of an OpenLDAP-based passwd backend, necessary to support distributed domain control. -

    • +

    • Implementation of Samba primary and secondary domain controllers with a common LDAP backend for user and group accounts that is shared with the UNIX system through the PADL nss_ldap and pam_ldap tool-sets. -

    • +

    • Use of the Idealx smbldap-tools scripts for UNIX (POSIX) account management as well as to manage Samba Windows user and group accounts. -

    • +

    • The basics of implementation of Group Policy controls for Windows network clients. -

    • +

    • Control over roaming profiles, with particular focus on folder redirection to network drives. -

    • +

    • Use of the CUPS printing system together with Samba-based printer driver auto-download. -

Questions and Answers

+

Questions and Answers

Well, here we are at the end of this chapter and we have only ten questions to help you to remember so much. There are bound to be some sticky issues here. -

+

Why did you not cover secure practices? Isn't it rather irresponsible to instruct network administrators to implement insecure solutions? -
+
You have focused much on SUSE Linux and little on the market leader, Red Hat. Do you have a problem with Red Hat Linux? Doesn't that make your guidance irrelevant to the Linux I might be using? -
+
You did not use SWAT to configure Samba. Is there something wrong with it? -
+
You have exposed a well-used password not24get. Is that not irresponsible? -
+
The Idealx smbldap-tools create many domain group accounts that are not used. Is that a good thing? -
+
Can I use LDAP just for Samba accounts and not for UNIX system accounts? -
+
Why are the Windows domain RID portions not the same as the UNIX UID? -
+
Printer configuration examples all show printing to the HP port 9100. Does this mean that I must have HP printers for these solutions to work? -
+
Is folder redirection dangerous? I've heard that you can lose your data that way. -
+
Is it really necessary to set a local Group Policy to exclude the redirected folders from the roaming profile? -

+

Why did you not cover secure practices? Isn't it rather irresponsible to instruct network administrators to implement insecure solutions?

@@ -2773,7 +2773,7 @@ This book makes little mention of backup techniques. Does that mean that I am recommending that you should implement a network without provision for data recovery and for disaster management? Back to our focus: The deployment of Samba has been clearly demonstrated. -

+

You have focused much on SUSE Linux and little on the market leader, Red Hat. Do you have a problem with Red Hat Linux? Doesn't that make your guidance irrelevant to the Linux I might be using? @@ -2800,7 +2800,7 @@ of open source software. I favor neither and respect both. I like particular features of both products (companies also). No bias in presentation is intended. Oh, before I forget, I particularly like Debian Linux; that is my favorite playground. -

+

You did not use SWAT to configure Samba. Is there something wrong with it?

That is a good question. As it is, the smb.conf file configurations are presented @@ -2811,14 +2811,14 @@ There are people in the Linux and open source community who feel that SWAT is dangerous and insecure. Many will not touch it with a barge-pole. By not introducing SWAT, I hope to have brought their interests on board. SWAT is well covered is TOSHARG2. -

+

You have exposed a well-used password not24get. Is that not irresponsible?

Well, I had to use a password of some sort. At least this one has been consistently used throughout. I guess you can figure out that in a real deployment it would make sense to use a more secure and original password. -

+

The Idealx smbldap-tools create many domain group accounts that are not used. Is that a good thing?

@@ -2826,7 +2826,7 @@ Let's give Idealx some credit for the contribution they have made. I appreciate their work and, besides, it does no harm to create accounts that are not now used at some time Samba may well use them. -

+

Can I use LDAP just for Samba accounts and not for UNIX system accounts?

Yes, you can do that for user accounts only. Samba requires there to be a POSIX (UNIX) @@ -2834,7 +2834,7 @@ the system password account, how do you plan to keep all domain controller system password files in sync? I think that having everything in LDAP makes a lot of sense for the UNIX administrator who is still learning the craft and is migrating from MS Windows. -

+

Why are the Windows domain RID portions not the same as the UNIX UID?

Samba uses a well-known public algorithm for assigning RIDs from UIDs and GIDs. @@ -2843,7 +2843,7 @@ assignment used the calculation: RID = UID x 2 + 1000. Of course, Samba does permit you to override that to some extent. See the smb.conf man page entry for algorithmic rid base. -

+

Printer configuration examples all show printing to the HP port 9100. Does this mean that I must have HP printers for these solutions to work?

@@ -2853,7 +2853,7 @@ inkjet printer. Use the appropriate device URI (Universal Resource Interface) argument to the lpadmin -v option that is right for your printer. -

+

Is folder redirection dangerous? I've heard that you can lose your data that way.

The only loss of data I know of that involved folder redirection was caused by @@ -2863,13 +2863,13 @@ he declined to move the data because he thought it was still in the local profile folder. That was not the case, so by declining to move the data back, he wiped out the data. You cannot hold the tool responsible for that. Caveat emptor still applies. -

+

Is it really necessary to set a local Group Policy to exclude the redirected folders from the roaming profile?

Yes. If you do not do this, the data will still be copied from the network folder (share) to the local cached copy of the profile. -



[11] +



[11] There is an alternate method by which a default user profile can be added to the NETLOGON share. This facility in the Windows System tool permits profiles to be exported. The export target may be a particular user or Dateien samba-3.3.10//docs/htmldocs/Samba3-ByExample/images/AccountingNetwork.png und samba-3.3.11//docs/htmldocs/Samba3-ByExample/images/AccountingNetwork.png sind verschieden. Dateien samba-3.3.10//docs/htmldocs/Samba3-ByExample/images/acct2net.png und samba-3.3.11//docs/htmldocs/Samba3-ByExample/images/acct2net.png sind verschieden. Dateien samba-3.3.10//docs/htmldocs/Samba3-ByExample/images/ch7-dual-additive-LDAP-Ok.png und samba-3.3.11//docs/htmldocs/Samba3-ByExample/images/ch7-dual-additive-LDAP-Ok.png sind verschieden. Dateien samba-3.3.10//docs/htmldocs/Samba3-ByExample/images/ch7-dual-additive-LDAP.png und samba-3.3.11//docs/htmldocs/Samba3-ByExample/images/ch7-dual-additive-LDAP.png sind verschieden. Dateien samba-3.3.10//docs/htmldocs/Samba3-ByExample/images/ch7-fail-overLDAP.png und samba-3.3.11//docs/htmldocs/Samba3-ByExample/images/ch7-fail-overLDAP.png sind verschieden. Dateien samba-3.3.10//docs/htmldocs/Samba3-ByExample/images/ch7-singleLDAP.png und samba-3.3.11//docs/htmldocs/Samba3-ByExample/images/ch7-singleLDAP.png sind verschieden. Dateien samba-3.3.10//docs/htmldocs/Samba3-ByExample/images/ch8-migration.png und samba-3.3.11//docs/htmldocs/Samba3-ByExample/images/ch8-migration.png sind verschieden. Dateien samba-3.3.10//docs/htmldocs/Samba3-ByExample/images/chap4-net.png und samba-3.3.11//docs/htmldocs/Samba3-ByExample/images/chap4-net.png sind verschieden. Dateien samba-3.3.10//docs/htmldocs/Samba3-ByExample/images/chap5-net.png und samba-3.3.11//docs/htmldocs/Samba3-ByExample/images/chap5-net.png sind verschieden. Dateien samba-3.3.10//docs/htmldocs/Samba3-ByExample/images/chap6-net.png und samba-3.3.11//docs/htmldocs/Samba3-ByExample/images/chap6-net.png sind verschieden. Dateien samba-3.3.10//docs/htmldocs/Samba3-ByExample/images/chap7-idresol.png und samba-3.3.11//docs/htmldocs/Samba3-ByExample/images/chap7-idresol.png sind verschieden. Dateien samba-3.3.10//docs/htmldocs/Samba3-ByExample/images/chap9-ADSDC.png und samba-3.3.11//docs/htmldocs/Samba3-ByExample/images/chap9-ADSDC.png sind verschieden. Dateien samba-3.3.10//docs/htmldocs/Samba3-ByExample/images/chap9-SambaDC.png und samba-3.3.11//docs/htmldocs/Samba3-ByExample/images/chap9-SambaDC.png sind verschieden. Dateien samba-3.3.10//docs/htmldocs/Samba3-ByExample/images/Charity-Network.png und samba-3.3.11//docs/htmldocs/Samba3-ByExample/images/Charity-Network.png sind verschieden. Dateien samba-3.3.10//docs/htmldocs/Samba3-ByExample/images/UNIX-Samba-and-LDAP.png und samba-3.3.11//docs/htmldocs/Samba3-ByExample/images/UNIX-Samba-and-LDAP.png sind verschieden. diff -u -r --new-file --exclude .svn --exclude CVS samba-3.3.10//docs/htmldocs/Samba3-ByExample/index.html samba-3.3.11//docs/htmldocs/Samba3-ByExample/index.html --- samba-3.3.10//docs/htmldocs/Samba3-ByExample/index.html 2010-01-14 11:24:52.000000000 +0100 +++ samba-3.3.11//docs/htmldocs/Samba3-ByExample/index.html 2010-02-22 16:53:36.000000000 +0100 @@ -1,47 +1,47 @@ -Samba-3 by Example

Samba-3 by Example

Practical Exercises in Successful Samba Deployment

John H. Terpstra

Samba Team

July, 2006


Table of Contents

About the Cover Artwork
Acknowledgments
Foreword
By John M. Weathersby, Executive Director, OSSI
Preface
Why Is This Book Necessary?
Samba 3.0.20 Update Edition
Prerequisites
Approach
Summary of Topics
Conventions Used
I. Example Network Configurations
1. No-Frills Samba Servers
Introduction
Assignment Tasks
Drafting Office
Charity Administration Office
Accounting Office
Questions and Answers
2. Small Office Networking
Introduction
Assignment Tasks
Dissection and Discussion
Technical Issues
Political Issues
Implementation
Validation
Notebook Computers: A Special Case
Key Points Learned
Questions and Answers
3. Secure Office Networking
Introduction
Assignment Tasks
Dissection and Discussion
Technical Issues
Political Issues
Implementation
Basic System Configuration
Samba Configuration
Configuration of DHCP and DNS Servers
Printer Configuration
Process Startup Configuration
Validation
Application Share Configuration
Windows Client Configuration
Key Points Learned
Questions and Answers
4. The 500-User Office
Introduction
Assignment Tasks
Dissection and Discussion
Technical Issues
Political Issues
Implementation
Installation of DHCP, DNS, and Samba Control Files
Server Preparation: All Servers
Server-Specific Preparation
Process Startup Configuration
Windows Client Configuration
Key Points Learned
Questions and Answers
5. Making Happy Users
Regarding LDAP Directories and Windows Computer Accounts
Introduction
Assignment Tasks
Dissection and Discussion
Technical Issues
Political Issues
Installation Checklist
Samba Server Implementation
OpenLDAP Server Configuration
PAM and NSS Client Configuration
Samba-3 PDC Configuration
Install and Configure Idealx smbldap-tools Scripts
LDAP Initialization and Creation of User and Group Accounts
Printer Configuration
Samba-3 BDC Configuration
Miscellaneous Server Preparation Tasks
Configuring Directory Share Point Roots
Configuring Profile Directories
Preparation of Logon Scripts
Assigning User Rights and Privileges
Windows Client Configuration
Configuration of Default Profile with Folder Redirection
Configuration of MS Outlook to Relocate PST File
Configure Delete Cached Profiles on Logout
Uploading Printer Drivers to Samba Servers
Software Installation
Roll-out Image Creation
Key Points Learned
Questions and Answers
6. A Distributed 2000-User Network
Introduction
Assignment Tasks
Dissection and Discussion
Technical Issues
Political Issues
Implementation
Key Points Learned
Questions and Answers
II. Domain Members, Updating Samba and Migration
7. Adding Domain Member Servers and Clients
Introduction
Assignment Tasks
Dissection and Discussion
Technical Issues
Political Issues
Implementation
Samba Domain with Samba Domain Member Server Using NSS LDAP
NT4/Samba Domain with Samba Domain Member Server: Using NSS and Winbind
NT4/Samba Domain with Samba Domain Member Server without NSS Support
Active Directory Domain with Samba Domain Member Server
UNIX/Linux Client Domain Member
Key Points Learned
Questions and Answers
8. Updating Samba-3
Introduction
Cautions and Notes
Upgrading from Samba 1.x and 2.x to Samba-3
Samba 1.9.x and 2.x Versions Without LDAP
Applicable to All Samba 2.x to Samba-3 Upgrades
Samba-2.x with LDAP Support
Updating a Samba-3 Installation
Samba-3 to Samba-3 Updates on the Same Server
Migrating Samba-3 to a New Server
Migration of Samba Accounts to Active Directory
9. Migrating NT4 Domain to Samba-3
Introduction
Assignment Tasks
Dissection and Discussion
Technical Issues
Political Issues
Implementation
NT4 Migration Using LDAP Backend
NT4 Migration Using tdbsam Backend
Key Points Learned
Questions and Answers
10. Migrating NetWare Server to Samba-3
Introduction
Assignment Tasks
Dissection and Discussion
Technical Issues
Implementation
NetWare Migration Using LDAP Backend
III. Reference Section
11. Active Directory, Kerberos, and Security
Introduction
Assignment Tasks
Dissection and Discussion
Technical Issues
Implementation
Share Access Controls
Share Definition Controls
Share Point Directory and File Permissions
Managing Windows 200x ACLs
Key Points Learned
Questions and Answers
12. Integrating Additional Services
Introduction
Assignment Tasks
Dissection and Discussion
Technical Issues
Political Issues
Implementation
Removal of Pre-Existing Conflicting RPMs
Key Points Learned
Questions and Answers
13. Performance, Reliability, and Availability
Introduction
Dissection and Discussion
Guidelines for Reliable Samba Operation
Name Resolution
Samba Configuration
Use and Location of BDCs
Use One Consistent Version of MS Windows Client
For Scalability, Use SAN-Based Storage on Samba Servers
Distribute Network Load with MSDFS
Replicate Data to Conserve Peak-Demand Wide-Area Bandwidth
Hardware Problems
Large Directories
Key Points Learned
14. Samba Support
Free Support
Commercial Support
15. A Collection of Useful Tidbits
Joining a Domain: Windows 200x/XP Professional
Samba System File Location
Starting Samba
DNS Configuration Files
The Forward Zone File for the Loopback Adaptor
The Reverse Zone File for the Loopback Adaptor
DNS Root Server Hint File
Alternative LDAP Database Initialization
Initialization of the LDAP Database
The LDAP Account Manager
IDEALX Management Console
Effect of Setting File and Directory SUID/SGID Permissions Explained
Shared Data Integrity
Microsoft Access
Act! Database Sharing
Opportunistic Locking Controls
16. Networking Primer
Requirements and Notes
Introduction
Assignment Tasks
Exercises
Single-Machine Broadcast Activity
Second Machine Startup Broadcast Interaction
Simple Windows Client Connection Characteristics
Windows 200x/XP Client Interaction with Samba-3
Conclusions to Exercises
Dissection and Discussion
Technical Issues
Questions and Answers
A. - GNU General Public License version 3 -
A. +Samba-3 by Example

Samba-3 by Example

Practical Exercises in Successful Samba Deployment

John H. Samba Team Terpstra

Samba Team

July, 2006


Table of Contents

About the Cover Artwork
Acknowledgments
Foreword
By John M. Weathersby, Executive Director, OSSI
Preface
Why Is This Book Necessary?
Samba 3.0.20 Update Edition
Prerequisites
Approach
Summary of Topics
Conventions Used
I. Example Network Configurations
1. No-Frills Samba Servers
Introduction
Assignment Tasks
Drafting Office
Charity Administration Office
Accounting Office
Questions and Answers
2. Small Office Networking
Introduction
Assignment Tasks
Dissection and Discussion
Technical Issues
Political Issues
Implementation
Validation
Notebook Computers: A Special Case
Key Points Learned
Questions and Answers
3. Secure Office Networking
Introduction
Assignment Tasks
Dissection and Discussion
Technical Issues
Political Issues
Implementation
Basic System Configuration
Samba Configuration
Configuration of DHCP and DNS Servers
Printer Configuration
Process Startup Configuration
Validation
Application Share Configuration
Windows Client Configuration
Key Points Learned
Questions and Answers
4. The 500-User Office
Introduction
Assignment Tasks
Dissection and Discussion
Technical Issues
Political Issues
Implementation
Installation of DHCP, DNS, and Samba Control Files
Server Preparation: All Servers
Server-Specific Preparation
Process Startup Configuration
Windows Client Configuration
Key Points Learned
Questions and Answers
5. Making Happy Users
Regarding LDAP Directories and Windows Computer Accounts
Introduction
Assignment Tasks
Dissection and Discussion
Technical Issues
Political Issues
Installation Checklist
Samba Server Implementation
OpenLDAP Server Configuration
PAM and NSS Client Configuration
Samba-3 PDC Configuration
Install and Configure Idealx smbldap-tools Scripts
LDAP Initialization and Creation of User and Group Accounts
Printer Configuration
Samba-3 BDC Configuration
Miscellaneous Server Preparation Tasks
Configuring Directory Share Point Roots
Configuring Profile Directories
Preparation of Logon Scripts
Assigning User Rights and Privileges
Windows Client Configuration
Configuration of Default Profile with Folder Redirection
Configuration of MS Outlook to Relocate PST File
Configure Delete Cached Profiles on Logout
Uploading Printer Drivers to Samba Servers
Software Installation
Roll-out Image Creation
Key Points Learned
Questions and Answers
6. A Distributed 2000-User Network
Introduction
Assignment Tasks
Dissection and Discussion
Technical Issues
Political Issues
Implementation
Key Points Learned
Questions and Answers
II. Domain Members, Updating Samba and Migration
7. Adding Domain Member Servers and Clients
Introduction
Assignment Tasks
Dissection and Discussion
Technical Issues
Political Issues
Implementation
Samba Domain with Samba Domain Member Server Using NSS LDAP
NT4/Samba Domain with Samba Domain Member Server: Using NSS and Winbind
NT4/Samba Domain with Samba Domain Member Server without NSS Support
Active Directory Domain with Samba Domain Member Server
UNIX/Linux Client Domain Member
Key Points Learned
Questions and Answers
8. Updating Samba-3
Introduction
Cautions and Notes
Upgrading from Samba 1.x and 2.x to Samba-3
Samba 1.9.x and 2.x Versions Without LDAP
Applicable to All Samba 2.x to Samba-3 Upgrades
Samba-2.x with LDAP Support
Updating a Samba-3 Installation
Samba-3 to Samba-3 Updates on the Same Server
Migrating Samba-3 to a New Server
Migration of Samba Accounts to Active Directory
9. Migrating NT4 Domain to Samba-3
Introduction
Assignment Tasks
Dissection and Discussion
Technical Issues
Political Issues
Implementation
NT4 Migration Using LDAP Backend
NT4 Migration Using tdbsam Backend
Key Points Learned
Questions and Answers
10. Migrating NetWare Server to Samba-3
Introduction
Assignment Tasks
Dissection and Discussion
Technical Issues
Implementation
NetWare Migration Using LDAP Backend
III. Reference Section
11. Active Directory, Kerberos, and Security
Introduction
Assignment Tasks
Dissection and Discussion
Technical Issues
Implementation
Share Access Controls
Share Definition Controls
Share Point Directory and File Permissions
Managing Windows 200x ACLs
Key Points Learned
Questions and Answers
12. Integrating Additional Services
Introduction
Assignment Tasks
Dissection and Discussion
Technical Issues
Political Issues
Implementation
Removal of Pre-Existing Conflicting RPMs
Key Points Learned
Questions and Answers
13. Performance, Reliability, and Availability
Introduction
Dissection and Discussion
Guidelines for Reliable Samba Operation
Name Resolution
Samba Configuration
Use and Location of BDCs
Use One Consistent Version of MS Windows Client
For Scalability, Use SAN-Based Storage on Samba Servers
Distribute Network Load with MSDFS
Replicate Data to Conserve Peak-Demand Wide-Area Bandwidth
Hardware Problems
Large Directories
Key Points Learned
14. Samba Support
Free Support
Commercial Support
15. A Collection of Useful Tidbits
Joining a Domain: Windows 200x/XP Professional
Samba System File Location
Starting Samba
DNS Configuration Files
The Forward Zone File for the Loopback Adaptor
The Reverse Zone File for the Loopback Adaptor
DNS Root Server Hint File
Alternative LDAP Database Initialization
Initialization of the LDAP Database
The LDAP Account Manager
IDEALX Management Console
Effect of Setting File and Directory SUID/SGID Permissions Explained
Shared Data Integrity
Microsoft Access
Act! Database Sharing
Opportunistic Locking Controls
16. Networking Primer
Requirements and Notes
Introduction
Assignment Tasks
Exercises
Single-Machine Broadcast Activity
Second Machine Startup Broadcast Interaction
Simple Windows Client Connection Characteristics
Windows 200x/XP Client Interaction with Samba-3
Conclusions to Exercises
Dissection and Discussion
Technical Issues
Questions and Answers
A. + GNU General Public License version 3 +
A. Preamble -
A. +
A. TERMS AND CONDITIONS -
A. +
A. 0. Definitions. -
A. +
A. 1. Source Code. -
A. +
A. 2. Basic Permissions. -
A. +
A. 3. Protecting Users’ Legal Rights From Anti-Circumvention Law. -
A. +
A. 4. Conveying Verbatim Copies. -
A. +
A. 5. Conveying Modified Source Versions. -
A. +
A. 6. Conveying Non-Source Forms. -
A. +
A. 7. Additional Terms. -
A. +
A. 8. Termination. -
A. +
A. 9. Acceptance Not Required for Having Copies. -
A. +
A. 10. Automatic Licensing of Downstream Recipients. -
A. +
A. 11. Patents. -
A. +
A. 12. No Surrender of Others’ Freedom. -
A. +
A. 13. Use with the ???TITLE??? Affero General Public License. -
A. +
A. 14. Revised Versions of this License. -
A. +
A. 15. Disclaimer of Warranty. -
A. +
A. 16. Limitation of Liability. -
A. +
A. 17. Interpretation of Sections 15 and 16. -
A. +
A. END OF TERMS AND CONDITIONS -
A. +
A. How to Apply These Terms to Your New Programs -
Glossary
Index

List of Figures

1.1. Charity Administration Office Network
1.2. Accounting Office Network Topology
2.1. Abmas Accounting 52-User Network Topology
3.1. Abmas Network Topology 130 Users
4.1. Network Topology 500 User Network Using tdbsam passdb backend.
5.1. The Interaction of LDAP, UNIX Posix Accounts and Samba Accounts
5.2. Network Topology 500 User Network Using ldapsam passdb backend
5.3. Windows XP Professional User Shared Folders
6.1. Samba and Authentication Backend Search Pathways
6.2. Samba Configuration to Use a Single LDAP Server
6.3. Samba Configuration to Use a Dual (Fail-over) LDAP Server
6.4. Samba Configuration to Use Dual LDAP Databases - Broken - Do Not Use!
6.5. Samba Configuration to Use Two LDAP Databases - The result is additive.
6.6. Network Topology 2000 User Complex Design A
6.7. Network Topology 2000 User Complex Design B
7.1. Open Magazine Samba Survey
7.2. Samba Domain: Samba Member Server
7.3. Active Directory Domain: Samba Member Server
9.1. Schematic Explaining the net rpc vampire Process
9.2. View of Accounts in NT4 Domain User Manager
15.1. The General Panel.
15.2. The Computer Name Panel.
15.3. The Computer Name Changes Panel
15.4. The Computer Name Changes Panel Domain MIDEARTH
15.5. Computer Name Changes User name and Password Panel
15.6. The LDAP Account Manager Login Screen
15.7. The LDAP Account Manager Configuration Screen
15.8. The LDAP Account Manager User Edit Screen
15.9. The LDAP Account Manager Group Edit Screen
15.10. The LDAP Account Manager Group Membership Edit Screen
15.11. The LDAP Account Manager Host Edit Screen
15.12. The IMC Samba User Account Screen
16.1. Windows Me Broadcasts The First 10 Minutes
16.2. Windows Me Later Broadcast Sample
16.3. Typical Windows 9x/Me Host Announcement
16.4. Typical Windows 9x/Me NULL SessionSetUp AndX Request
16.5. Typical Windows 9x/Me User SessionSetUp AndX Request
16.6. Typical Windows XP NULL Session Setup AndX Request
16.7. Typical Windows XP User Session Setup AndX Request

List of Examples

1.1. Drafting Office smb.conf File
1.2. Charity Administration Office smb.conf New-style File
1.3. Charity Administration Office smb.conf Old-style File
1.4. Windows Me Registry Edit File: Disable Password Caching
1.5. Accounting Office Network smb.conf Old Style Configuration File
2.1. Script to Map Windows NT Groups to UNIX Groups
2.2. Abmas Accounting DHCP Server Configuration File /etc/dhcpd.conf
2.3. Accounting Office Network smb.conf File [globals] Section
2.4. Accounting Office Network smb.conf File Services and Shares Section
3.1. Estimation of Memory Requirements
3.2. Estimation of Disk Storage Requirements
3.3. NAT Firewall Configuration Script
3.4. 130 User Network with tdbsam [globals] Section
3.5. 130 User Network with tdbsam Services Section Part A
3.6. 130 User Network with tdbsam Services Section Part B
3.7. Script to Map Windows NT Groups to UNIX Groups
3.8. DHCP Server Configuration File /etc/dhcpd.conf
3.9. DNS Master Configuration File /etc/named.conf Master Section
3.10. DNS Master Configuration File /etc/named.conf Forward Lookup Definition Section
3.11. DNS Master Configuration File /etc/named.conf Reverse Lookup Definition Section
3.12. DNS 192.168.1 Reverse Zone File
3.13. DNS 192.168.2 Reverse Zone File
3.14. DNS Abmas.biz Forward Zone File
3.15. DNS Abmas.us Forward Zone File
4.1. Server: MASSIVE (PDC), File: /etc/samba/smb.conf
4.2. Server: MASSIVE (PDC), File: /etc/samba/dc-common.conf
4.3. Common Samba Configuration File: /etc/samba/common.conf
4.4. Server: BLDG1 (Member), File: smb.conf
4.5. Server: BLDG2 (Member), File: smb.conf
4.6. Common Domain Member Include File: dom-mem.conf
4.7. Server: MASSIVE, File: dhcpd.conf
4.8. Server: BLDG1, File: dhcpd.conf
4.9. Server: BLDG2, File: dhcpd.conf
4.10. Server: MASSIVE, File: named.conf, Part: A
4.11. Server: MASSIVE, File: named.conf, Part: B
4.12. Server: MASSIVE, File: named.conf, Part: C
4.13. Forward Zone File: abmas.biz.hosts
4.14. Forward Zone File: abmas.biz.hosts
4.15. Servers: BLDG1/BLDG2, File: named.conf, Part: A
4.16. Servers: BLDG1/BLDG2, File: named.conf, Part: B
4.17. Initialize Groups Script, File: /etc/samba/initGrps.sh
5.1. LDAP DB_CONFIG File
5.2. LDAP Master Configuration File /etc/openldap/slapd.conf Part A
5.3. LDAP Master Configuration File /etc/openldap/slapd.conf Part B
5.4. Configuration File for NSS LDAP Support /etc/ldap.conf
5.5. Configuration File for NSS LDAP Clients Support /etc/ldap.conf
5.6. LDAP Based smb.conf File, Server: MASSIVE global Section: Part A
5.7. LDAP Based smb.conf File, Server: MASSIVE global Section: Part B
5.8. LDAP Based smb.conf File, Server: BLDG1
5.9. LDAP Based smb.conf File, Server: BLDG2
5.10. LDAP Based smb.conf File, Shares Section Part A
5.11. LDAP Based smb.conf File, Shares Section Part B
5.12. LDIF IDMAP Add-On Load File File: /etc/openldap/idmap.LDIF
6.1. LDAP Master Server Configuration File /etc/openldap/slapd.conf
6.2. LDAP Slave Configuration File /etc/openldap/slapd.conf
6.3. Primary Domain Controller smb.conf File Part A
6.4. Primary Domain Controller smb.conf File Part B
6.5. Primary Domain Controller smb.conf File Part C
6.6. Backup Domain Controller smb.conf File Part A
6.7. Backup Domain Controller smb.conf File Part B
7.1. Samba Domain Member in Samba Domain Using LDAP smb.conf File
7.2. LDIF IDMAP Add-On Load File File: /etc/openldap/idmap.LDIF
7.3. Configuration File for NSS LDAP Support /etc/ldap.conf
7.4. NSS using LDAP for Identity Resolution File: /etc/nsswitch.conf
7.5. Samba Domain Member Server Using Winbind smb.conf File for NT4 Domain
7.6. Samba Domain Member Server Using Local Accounts smb.conf File for NT4 Domain
7.7. Samba Domain Member smb.conf File for Active Directory Membership
7.8. Example smb.conf File Using idmap_rid
7.9. Typical ADS Style Domain smb.conf File
7.10. ADS Membership Using RFC2307bis Identity Resolution smb.conf File
7.11. SUSE: PAM login Module Using Winbind
7.12. SUSE: PAM xdm Module Using Winbind
7.13. Red Hat 9: PAM System Authentication File: /etc/pam.d/system-auth Module Using Winbind
9.1. NT4 Migration Samba-3 Server smb.conf Part: A
9.2. NT4 Migration Samba-3 Server smb.conf Part: B
9.3. NT4 Migration LDAP Server Configuration File: /etc/openldap/slapd.conf Part A
9.4. NT4 Migration LDAP Server Configuration File: /etc/openldap/slapd.conf Part B
9.5. NT4 Migration NSS LDAP File: /etc/ldap.conf
9.6. NT4 Migration NSS Control File: /etc/nsswitch.conf (Stage:1)
9.7. NT4 Migration NSS Control File: /etc/nsswitch.conf (Stage:2)
10.1. A Rough Tool to Create an LDIF File from the System Account Files
10.2. NSS LDAP Control File /etc/ldap.conf
10.3. The PAM Control File /etc/security/pam_unix2.conf
10.4. Samba Configuration File smb.conf Part A
10.5. Samba Configuration File smb.conf Part B
10.6. Samba Configuration File smb.conf Part C
10.7. Samba Configuration File smb.conf Part D
10.8. Samba Configuration File smb.conf Part E
10.9. Rsync Script
10.10. Rsync Files Exclusion List /root/excludes.txt
10.11. Idealx smbldap-tools Control File Part A
10.12. Idealx smbldap-tools Control File Part B
10.13. Idealx smbldap-tools Control File Part C
10.14. Idealx smbldap-tools Control File Part D
10.15. Kixtart Control File File: logon.kix
10.16. Kixtart Control File File: main.kix
10.17. Kixtart Control File File: setup.kix, Part A
10.18. Kixtart Control File File: setup.kix, Part B
10.19. Kixtart Control File File: acct.kix
12.1. Kerberos Configuration File: /etc/krb5.conf
12.2. Samba Configuration File: /etc/samba/smb.conf
12.3. NSS Configuration File Extract File: /etc/nsswitch.conf
12.4. Squid Configuration File Extract /etc/squid.conf [ADMINISTRATIVE PARAMETERS Section]
12.5. Squid Configuration File extract File: /etc/squid.conf [AUTHENTICATION PARAMETERS Section]
15.1. A Useful Samba Control Script for SUSE Linux
15.2. A Sample Samba Control Script for Red Hat Linux
15.3. DNS Localhost Forward Zone File: /var/lib/named/localhost.zone
15.4. DNS Localhost Reverse Zone File: /var/lib/named/127.0.0.zone
15.5. DNS Root Name Server Hint File: /var/lib/named/root.hint
15.6. LDAP Pre-configuration Script: SMBLDAP-ldif-preconfig.sh Part A
15.7. LDAP Pre-configuration Script: SMBLDAP-ldif-preconfig.sh Part B
15.8. LDAP Pre-configuration Script: SMBLDAP-ldif-preconfig.sh Part C
15.9. LDIF Pattern File Used to Pre-configure LDAP Part A
15.10. LDIF Pattern File Used to Pre-configure LDAP Part B
15.11. Example LAM Configuration File config.cfg
15.12. LAM Profile Control File lam.conf
+
Glossary
Index

List of Figures

1.1. Charity Administration Office Network
1.2. Accounting Office Network Topology
2.1. Abmas Accounting 52-User Network Topology
3.1. Abmas Network Topology 130 Users
4.1. Network Topology 500 User Network Using tdbsam passdb backend.
5.1. The Interaction of LDAP, UNIX Posix Accounts and Samba Accounts
5.2. Network Topology 500 User Network Using ldapsam passdb backend
5.3. Windows XP Professional User Shared Folders
6.1. Samba and Authentication Backend Search Pathways
6.2. Samba Configuration to Use a Single LDAP Server
6.3. Samba Configuration to Use a Dual (Fail-over) LDAP Server
6.4. Samba Configuration to Use Dual LDAP Databases - Broken - Do Not Use!
6.5. Samba Configuration to Use Two LDAP Databases - The result is additive.
6.6. Network Topology 2000 User Complex Design A
6.7. Network Topology 2000 User Complex Design B
7.1. Open Magazine Samba Survey
7.2. Samba Domain: Samba Member Server
7.3. Active Directory Domain: Samba Member Server
9.1. Schematic Explaining the net rpc vampire Process
9.2. View of Accounts in NT4 Domain User Manager
15.1. The General Panel.
15.2. The Computer Name Panel.
15.3. The Computer Name Changes Panel
15.4. The Computer Name Changes Panel Domain MIDEARTH
15.5. Computer Name Changes User name and Password Panel
15.6. The LDAP Account Manager Login Screen
15.7. The LDAP Account Manager Configuration Screen
15.8. The LDAP Account Manager User Edit Screen
15.9. The LDAP Account Manager Group Edit Screen
15.10. The LDAP Account Manager Group Membership Edit Screen
15.11. The LDAP Account Manager Host Edit Screen
15.12. The IMC Samba User Account Screen
16.1. Windows Me Broadcasts The First 10 Minutes
16.2. Windows Me Later Broadcast Sample
16.3. Typical Windows 9x/Me Host Announcement
16.4. Typical Windows 9x/Me NULL SessionSetUp AndX Request
16.5. Typical Windows 9x/Me User SessionSetUp AndX Request
16.6. Typical Windows XP NULL Session Setup AndX Request
16.7. Typical Windows XP User Session Setup AndX Request

List of Examples

1.1. Drafting Office smb.conf File
1.2. Charity Administration Office smb.conf New-style File
1.3. Charity Administration Office smb.conf Old-style File
1.4. Windows Me Registry Edit File: Disable Password Caching
1.5. Accounting Office Network smb.conf Old Style Configuration File
2.1. Script to Map Windows NT Groups to UNIX Groups
2.2. Abmas Accounting DHCP Server Configuration File /etc/dhcpd.conf
2.3. Accounting Office Network smb.conf File [globals] Section
2.4. Accounting Office Network smb.conf File Services and Shares Section
3.1. Estimation of Memory Requirements
3.2. Estimation of Disk Storage Requirements
3.3. NAT Firewall Configuration Script
3.4. 130 User Network with tdbsam [globals] Section
3.5. 130 User Network with tdbsam Services Section Part A
3.6. 130 User Network with tdbsam Services Section Part B
3.7. Script to Map Windows NT Groups to UNIX Groups
3.8. DHCP Server Configuration File /etc/dhcpd.conf
3.9. DNS Master Configuration File /etc/named.conf Master Section
3.10. DNS Master Configuration File /etc/named.conf Forward Lookup Definition Section
3.11. DNS Master Configuration File /etc/named.conf Reverse Lookup Definition Section
3.12. DNS 192.168.1 Reverse Zone File
3.13. DNS 192.168.2 Reverse Zone File
3.14. DNS Abmas.biz Forward Zone File
3.15. DNS Abmas.us Forward Zone File
4.1. Server: MASSIVE (PDC), File: /etc/samba/smb.conf
4.2. Server: MASSIVE (PDC), File: /etc/samba/dc-common.conf
4.3. Common Samba Configuration File: /etc/samba/common.conf
4.4. Server: BLDG1 (Member), File: smb.conf
4.5. Server: BLDG2 (Member), File: smb.conf
4.6. Common Domain Member Include File: dom-mem.conf
4.7. Server: MASSIVE, File: dhcpd.conf
4.8. Server: BLDG1, File: dhcpd.conf
4.9. Server: BLDG2, File: dhcpd.conf
4.10. Server: MASSIVE, File: named.conf, Part: A
4.11. Server: MASSIVE, File: named.conf, Part: B
4.12. Server: MASSIVE, File: named.conf, Part: C
4.13. Forward Zone File: abmas.biz.hosts
4.14. Forward Zone File: abmas.biz.hosts
4.15. Servers: BLDG1/BLDG2, File: named.conf, Part: A
4.16. Servers: BLDG1/BLDG2, File: named.conf, Part: B
4.17. Initialize Groups Script, File: /etc/samba/initGrps.sh
5.1. LDAP DB_CONFIG File
5.2. LDAP Master Configuration File /etc/openldap/slapd.conf Part A
5.3. LDAP Master Configuration File /etc/openldap/slapd.conf Part B
5.4. Configuration File for NSS LDAP Support /etc/ldap.conf
5.5. Configuration File for NSS LDAP Clients Support /etc/ldap.conf
5.6. LDAP Based smb.conf File, Server: MASSIVE global Section: Part A
5.7. LDAP Based smb.conf File, Server: MASSIVE global Section: Part B
5.8. LDAP Based smb.conf File, Server: BLDG1
5.9. LDAP Based smb.conf File, Server: BLDG2
5.10. LDAP Based smb.conf File, Shares Section Part A
5.11. LDAP Based smb.conf File, Shares Section Part B
5.12. LDIF IDMAP Add-On Load File File: /etc/openldap/idmap.LDIF
6.1. LDAP Master Server Configuration File /etc/openldap/slapd.conf
6.2. LDAP Slave Configuration File /etc/openldap/slapd.conf
6.3. Primary Domain Controller smb.conf File Part A
6.4. Primary Domain Controller smb.conf File Part B
6.5. Primary Domain Controller smb.conf File Part C
6.6. Backup Domain Controller smb.conf File Part A
6.7. Backup Domain Controller smb.conf File Part B
7.1. Samba Domain Member in Samba Domain Using LDAP smb.conf File
7.2. LDIF IDMAP Add-On Load File File: /etc/openldap/idmap.LDIF
7.3. Configuration File for NSS LDAP Support /etc/ldap.conf
7.4. NSS using LDAP for Identity Resolution File: /etc/nsswitch.conf
7.5. Samba Domain Member Server Using Winbind smb.conf File for NT4 Domain
7.6. Samba Domain Member Server Using Local Accounts smb.conf File for NT4 Domain
7.7. Samba Domain Member smb.conf File for Active Directory Membership
7.8. Example smb.conf File Using idmap_rid
7.9. Typical ADS Style Domain smb.conf File
7.10. ADS Membership Using RFC2307bis Identity Resolution smb.conf File
7.11. SUSE: PAM login Module Using Winbind
7.12. SUSE: PAM xdm Module Using Winbind
7.13. Red Hat 9: PAM System Authentication File: /etc/pam.d/system-auth Module Using Winbind
9.1. NT4 Migration Samba-3 Server smb.conf Part: A
9.2. NT4 Migration Samba-3 Server smb.conf Part: B
9.3. NT4 Migration LDAP Server Configuration File: /etc/openldap/slapd.conf Part A
9.4. NT4 Migration LDAP Server Configuration File: /etc/openldap/slapd.conf Part B
9.5. NT4 Migration NSS LDAP File: /etc/ldap.conf
9.6. NT4 Migration NSS Control File: /etc/nsswitch.conf (Stage:1)
9.7. NT4 Migration NSS Control File: /etc/nsswitch.conf (Stage:2)
10.1. A Rough Tool to Create an LDIF File from the System Account Files
10.2. NSS LDAP Control File /etc/ldap.conf
10.3. The PAM Control File /etc/security/pam_unix2.conf
10.4. Samba Configuration File smb.conf Part A
10.5. Samba Configuration File smb.conf Part B
10.6. Samba Configuration File smb.conf Part C
10.7. Samba Configuration File smb.conf Part D
10.8. Samba Configuration File smb.conf Part E
10.9. Rsync Script
10.10. Rsync Files Exclusion List /root/excludes.txt
10.11. Idealx smbldap-tools Control File Part A
10.12. Idealx smbldap-tools Control File Part B
10.13. Idealx smbldap-tools Control File Part C
10.14. Idealx smbldap-tools Control File Part D
10.15. Kixtart Control File File: logon.kix
10.16. Kixtart Control File File: main.kix
10.17. Kixtart Control File File: setup.kix, Part A
10.18. Kixtart Control File File: setup.kix, Part B
10.19. Kixtart Control File File: acct.kix
12.1. Kerberos Configuration File: /etc/krb5.conf
12.2. Samba Configuration File: /etc/samba/smb.conf
12.3. NSS Configuration File Extract File: /etc/nsswitch.conf
12.4. Squid Configuration File Extract /etc/squid.conf [ADMINISTRATIVE PARAMETERS Section]
12.5. Squid Configuration File extract File: /etc/squid.conf [AUTHENTICATION PARAMETERS Section]
15.1. A Useful Samba Control Script for SUSE Linux
15.2. A Sample Samba Control Script for Red Hat Linux
15.3. DNS Localhost Forward Zone File: /var/lib/named/localhost.zone
15.4. DNS Localhost Reverse Zone File: /var/lib/named/127.0.0.zone
15.5. DNS Root Name Server Hint File: /var/lib/named/root.hint
15.6. LDAP Pre-configuration Script: SMBLDAP-ldif-preconfig.sh Part A
15.7. LDAP Pre-configuration Script: SMBLDAP-ldif-preconfig.sh Part B
15.8. LDAP Pre-configuration Script: SMBLDAP-ldif-preconfig.sh Part C
15.9. LDIF Pattern File Used to Pre-configure LDAP Part A
15.10. LDIF Pattern File Used to Pre-configure LDAP Part B
15.11. Example LAM Configuration File config.cfg
15.12. LAM Profile Control File lam.conf
diff -u -r --new-file --exclude .svn --exclude CVS samba-3.3.10//docs/htmldocs/Samba3-ByExample/ix01.html samba-3.3.11//docs/htmldocs/Samba3-ByExample/ix01.html --- samba-3.3.10//docs/htmldocs/Samba3-ByExample/ix01.html 2010-01-14 11:24:52.000000000 +0100 +++ samba-3.3.11//docs/htmldocs/Samba3-ByExample/ix01.html 2010-02-22 16:53:36.000000000 +0100 @@ -1 +1 @@ -Index

Index

Symbols

%LOGONSERVER%, Configuration of Default Profile with Folder Redirection
%USERNAME%, Roaming Profile Background, Profile Changes
%USERPROFILE%, Configuration of Default Profile with Folder Redirection
/data/ldap, OpenLDAP Server Configuration
/etc/cups/mime.convs, Implementation, Implementation
/etc/cups/mime.types, Implementation, Implementation
/etc/dhcpd.conf, Implementation, Validation, Configuration of DHCP and DNS Servers, Validation
/etc/exports, Samba-3 PDC Configuration
/etc/group, Technical Issues, Samba Domain with Samba Domain Member Server Using NSS LDAP, Replacing a Domain Member Server, Questions and Answers, Removal of Pre-Existing Conflicting RPMs
/etc/hosts, Implementation, Implementation, Basic System Configuration, Validation, Server Preparation: All Servers, Questions and Answers, Kerberos Configuration, Bad Hostnames
/etc/krb5.conf, IDMAP Storage in LDAP using Winbind, Kerberos Configuration
/etc/ldap.conf, PAM and NSS Client Configuration, IDMAP Storage in LDAP using Winbind, IDMAP and NSS Using LDAP from ADS with RFC2307bis Schema Extension, NT4 Migration Using LDAP Backend, LDAP Server Configuration
/etc/mime.convs, Implementation, Printer Configuration, Server Preparation: All Servers, Printer Configuration
/etc/mime.types, Implementation, Printer Configuration, Server Preparation: All Servers, Printer Configuration
/etc/named.conf, Configuration of DHCP and DNS Servers
/etc/nsswitch.conf, Implementation, Configuration of DHCP and DNS Servers, Validation, Configuration for Server: MASSIVE, Configuration Specific to Domain Member Servers: BLDG1, BLDG2, PAM and NSS Client Configuration, NT4/Samba Domain with Samba Domain Member Server: Using NSS and Winbind, IDMAP_RID with Winbind, IDMAP and NSS Using LDAP from ADS with RFC2307bis Schema Extension, Questions and Answers, NT4 Migration Using LDAP Backend
/etc/openldap/slapd.conf, Debugging LDAP, OpenLDAP Server Configuration, Implementation
/etc/passwd, Implementation, Samba Configuration, Configuration for Server: MASSIVE, LDAP Initialization and Creation of User and Group Accounts, Samba Domain with Samba Domain Member Server Using NSS LDAP, NT4/Samba Domain with Samba Domain Member Server: Using NSS and Winbind, Questions and Answers, Replacing a Domain Member Server, Technical Issues, Questions and Answers, Technical Issues, Share Point Directory and File Permissions, Removal of Pre-Existing Conflicting RPMs, Findings and Comments
/etc/rc.d/boot.local, Basic System Configuration, Configuration for Server: MASSIVE
/etc/rc.d/rc.local, Implementation
/etc/resolv.conf, Configuration of DHCP and DNS Servers, Server Preparation: All Servers
/etc/samba, Samba System File Location
/etc/samba/secrets.tdb, Active Directory Domain with Samba Domain Member Server
/etc/samba/smbusers, Server Preparation: All Servers
/etc/shadow, Replacing a Domain Member Server, Technical Issues
/etc/squid/squid.conf, Removal of Pre-Existing Conflicting RPMs
/etc/syslog.conf, Debugging LDAP
/etc/xinetd.d, Process Startup Configuration, Process Startup Configuration
/lib/libnss_ldap.so.2, PAM and NSS Client Configuration
/opt/IDEALX/sbin, NT4 Migration Using LDAP Backend
/proc/sys/net/ipv4/ip_forward, Implementation, Basic System Configuration
/usr/bin, Samba System File Location
/usr/lib/samba, Samba System File Location
/usr/local, Samba System File Location
/usr/local/samba, Samba System File Location
/usr/local/samba/var/locks, Samba 1.9.x and 2.x Versions Without LDAP
/usr/sbin, Samba System File Location
/usr/share, Samba System File Location
/usr/share/samba/swat, Samba System File Location
/usr/share/swat, Samba System File Location
/var/cache/samba, Samba 1.9.x and 2.x Versions Without LDAP
/var/lib/samba, Samba 1.9.x and 2.x Versions Without LDAP, Samba System File Location
/var/log/ldaplogs, Debugging LDAP
/var/log/samba, Samba System File Location
8-bit, International Language Support

A

abmas-netfw.sh, Basic System Configuration
accept, Printer Configuration
accepts liability, Dissection and Discussion
access, Technical Issues, Checkpoint Controls
access control, Kerberos Exposed, Using the MMC Computer Management Interface
Access Control Lists (see ACLs)
access control settings, Share Access Controls
access controls, Technical Issues, Share Definition Controls
accessible, Share Point Directory and File Permissions
account, Regarding LDAP Directories and Windows Computer Accounts, Share Access Controls
ADS Domain, Technical Issues
account credentials, Findings and Comments
account information, Questions and Answers
account names, Questions and Answers
account policies, The LDAP Account Manager
accountable, Introduction, Dissection and Discussion
accounts
authoritative, Technical Issues
Domain, Introduction, Questions and Answers
group, Introduction, Questions and Answers, Introduction
machine, Introduction, Questions and Answers
manage, The LDAP Account Manager
user, Introduction, Questions and Answers, Introduction
ACL, Security Identifiers (SIDs), Checkpoint Controls
ACLs, Key Points Learned, Share Access Controls, Share Definition Controls
acquisitions, Introduction
Act!, Shared Data Integrity
ACT! database, Act! Database Sharing
Act!Diag, Act! Database Sharing
Active Directory, Dissection and Discussion, The Local Group Policy, Dissection and Discussion, Assignment Tasks, Active Directory Domain with Samba Domain Member Server, IDMAP_RID with Winbind, Questions and Answers, Introduction, Key Points Learned, Questions and Answers, Integrating Additional Services, Assignment Tasks, Technical Issues, Samba Configuration, Joining a Domain: Windows 200x/XP Professional
authentication, Squid Configuration
domain, Samba Configuration
join, Active Directory Domain with Samba Domain Member Server
management tools, Technical Issues
realm, Bad Hostnames
Replacement, Technical Issues
server, Active Directory Domain with Samba Domain Member Server, Kerberos Configuration
Server, Technical Issues
tree, Samba Configuration
active directory, Technical Issues
AD printer publishing, Uploading Printer Drivers to Samba Servers
ADAM, Dissection and Discussion, IDMAP Storage in LDAP using Winbind
add group script, Applicable to All Samba 2.x to Samba-3 Upgrades
add machine script, Applicable to All Samba 2.x to Samba-3 Upgrades
Add Printer Wizard
APW, Uploading Printer Drivers to Samba Servers
add user script, Applicable to All Samba 2.x to Samba-3 Upgrades
add user to group script, Applicable to All Samba 2.x to Samba-3 Upgrades
adduser, Implementation, Samba Configuration, Configuration for Server: MASSIVE
adequate precautions, Introduction
administrative installation, Application Share Configuration
administrative rights, Checkpoint Controls
administrator, Implementation, Samba Configuration, Server Preparation: All Servers
ADMT, Migration of Samba Accounts to Active Directory
ADS, IDMAP Storage in LDAP using Winbind, Technical Issues, Kerberos Configuration, Bad Hostnames
server, Technical Issues
ADS Domain, Technical Issues
affordability, The Nature of Windows Networking Protocols
alarm, Introduction
algorithm, Technical Issues
allow trusted domains, IDMAP_RID with Winbind
alternative, Dissection and Discussion
analysis, Technical Issues
anonymous connection, Validation, Validation
Apache Web server, Questions and Answers
appliance mode, Technical Issues
application server, Technical Issues, Application Share Configuration
application servers, The Nature of Windows Networking Protocols
application/octet-stream, Implementation, Implementation, Implementation, Printer Configuration, Server Preparation: All Servers, Printer Configuration
APW, Uploading Printer Drivers to Samba Servers
arp, Validation
assessment, Introduction
assistance, Free Support
assumptions, Key Points Learned
authconfig, PAM and NSS Client Configuration
authenticate, LDAP Server Configuration, Samba Configuration
authenticated, Assignment Tasks
authenticated connection, Validation, Validation
authentication, The Nature of Windows Networking Protocols, Questions and Answers, Dissection and Discussion, Integrating Additional Services, Technical Issues, NSS Configuration, Questions and Answers
plain-text, Questions and Answers
authentication process, Implementation
authentication protocols, Key Points Learned
authoritative, Technical Issues
authorized location, Kerberos Exposed
auto-generated SID, Questions and Answers
automatically allocate, Technical Issues
availability, Performance, Reliability, and Availability

C

cache, Opportunistic Locking Controls
cache directories, Removal of Pre-Existing Conflicting RPMs
caching, Samba Configuration
case-sensitive, Kerberos Configuration
centralized storage, Questions and Answers
character set, International Language Support
check samba daemons, Validation, Validation
check-point, Share Definition Controls
check-point controls, Checkpoint Controls
Checkpoint Controls, Checkpoint Controls
chgrp, Samba Configuration
chkconfig, Implementation, Implementation, Implementation, Implementation, Process Startup Configuration, Process Startup Configuration, Implementation
chmod, Samba Configuration
choice, Dissection and Discussion, Technical Issues
chown, Removal of Pre-Existing Conflicting RPMs
CIFS, Security Identifiers (SIDs), Findings
cifsfs, Dissection and Discussion
clean database, Questions and Answers
clients per DC, Making Happy Users
Clock skew, Kerberos Configuration
cluster, Introduction
clustering, Introduction, For Scalability, Use SAN-Based Storage on Samba Servers
code maintainer, Free Support
codepage, International Language Support
collision rates, Network Collisions
commercial, Dissection and Discussion
commercial software, Dissection and Discussion
commercial support, Samba Support, Commercial Support
Common Internet File System (see CIFS)
comparison
Active Directory & OpenLDAP, Dissection and Discussion
compat, Samba Domain with Samba Domain Member Server Using NSS LDAP
compatible, Technical Issues
compile-time, Location of config files
complexities, Dissection and Discussion
compromise, Introduction, Introduction, Technical Issues
computer account, Samba Configuration
Computer Management, Share Access Controls, Questions and Answers
computer name, Security Identifiers (SIDs)
condemns, Technical Issues
conferences, Technical Issues
configuration files, Introduction
configure.pl, NT4 Migration Using LDAP Backend
connection, Share Access Controls
connectivity, Questions and Answers
consequential risk, Technical Issues
consultant, Drafting Office, Introduction, Dissection and Discussion
consumer, Dissection and Discussion, Technical Issues
consumer expects, Samba Support
contiguous directory, Implementation
contributions, Updating Samba-3
control files, Updating a Samba-3 Installation
convmv, International Language Support
copy, Questions and Answers
corrective action, Hardware Problems
cost, Dissection and Discussion
cost-benefit, Assignment Tasks
country of origin, Commercial Support
Courier-IMAP, LDAP Server Configuration
credential, Share Definition Controls
credentials, NT4/Samba Domain with Samba Domain Member Server: Using NSS and Winbind, Technical Issues
crippled, Dissection and Discussion
criticism, Active Directory, Kerberos, and Security, Introduction
Critics, Technical Issues
Cryptographic, Technical Issues
CUPS, Dissection and Discussion, Technical Issues, Implementation, Key Points Learned, Implementation, Printer Configuration, Server Preparation: All Servers, Assignment Tasks, Installation of Printer Driver Auto-Download, Printer Configuration
queue, Implementation, Printer Configuration, Server Preparation: All Servers, Printer Configuration
cupsd, Basic System Configuration
customer expected, Samba Support
customers, Samba Support

D

daemon, Validation, Basic System Configuration, Security Identifiers (SIDs), Technical Issues, Questions and Answers, Starting Samba
daemon control, Process Startup Configuration
data
corruption, Making Happy Users
integrity, Questions and Answers
data corruption, Hardware Problems, Act! Database Sharing
data integrity, Hardware Problems, Shared Data Integrity
data storage, Implementation
database, Dissection and Discussion, Questions and Answers, Dissection and Discussion
database applications, Shared Data Integrity
DB_CONFIG, OpenLDAP Server Configuration
DCE, Kerberos Exposed
DDNS (see dynamic DNS)
Debian, Migrating NetWare Server to Samba-3
default installation, Samba System File Location
default password, The LDAP Account Manager
default profile, Assignment Tasks, Technical Issues
Default User, Profile Changes, Configuration of Default Profile with Folder Redirection
defective
cables, Hardware Problems
HUBs, Hardware Problems
switches, Hardware Problems
defects, Technical Issues
defensible standards, Technical Issues
defragmentation, Windows Client Configuration
delete group script, Applicable to All Samba 2.x to Samba-3 Upgrades
delete user from group script, Applicable to All Samba 2.x to Samba-3 Upgrades
delimiter, Checkpoint Controls
dependability, Technical Issues
deployment, Free Support
desired security setting, Setting Posix ACLs in UNIX/Linux
development, Technical Issues
DHCP, Technical Issues, Implementation, Key Points Learned, Windows Client Configuration, Windows Client Configuration, The Nature of Windows Networking Protocols, Questions and Answers
client, Bad Hostnames
relay, Technical Issues
Relay Agent, Questions and Answers
request, Questions and Answers
requests, Technical Issues
servers, Questions and Answers
traffic, Questions and Answers
dhcp client validation, Validation, Validation
DHCP Server, Implementation
DHCP server, Technical Issues
diagnostic, IDMAP Storage in LDAP using Winbind
diffusion, Technical Issues
digital rights, Technical Issues
digital sign'n'seal, Technical Issues
digits, Bad Hostnames
diligence, Technical Issues
directory, Dissection and Discussion, Political Issues, Location of config files
Computers container, LDAP Initialization and Creation of User and Group Accounts
management, Dissection and Discussion
People container, LDAP Initialization and Creation of User and Group Accounts
replication, Dissection and Discussion
schema, Dissection and Discussion
server, Technical Issues
synchronization, Dissection and Discussion
directory tree, Setting Posix ACLs in UNIX/Linux
disable, Introduction
disaster recovery, Introduction
disk image, Assignment Tasks
disruptive, Dissection and Discussion
distributed, Identity Management Needs, Implementation, Questions and Answers, Distribute Network Load with MSDFS
distributed domain, Identity Management Needs
DMB, Questions and Answers
DMS, Security Identifiers (SIDs), Replacing a Domain Member Server
DNS, Technical Issues, Implementation, Technical Issues, The Nature of Windows Networking Protocols, LDAP Server Configuration, Bad Hostnames, Routed Networks, Joining a Domain: Windows 200x/XP Professional
configuration, Questions and Answers
Dynamic, Questions and Answers
dynamic, Joining a Domain: Windows 200x/XP Professional
lookup, Questions and Answers, Kerberos Configuration
name lookup, Bad Hostnames
SRV records, Kerberos Configuration
suffix, Joining a Domain: Windows 200x/XP Professional
DNS server, Implementation, Configuration of DHCP and DNS Servers
document the settings, Samba Configuration
documentation, Dissection and Discussion, Technical Issues
documented, Samba Configuration
Domain, Technical Issues
groups, Technical Issues
domain
Active Directory, Technical Issues
controller, Replacing a Domain Controller
joining, A Collection of Useful Tidbits
trusted, Questions and Answers
Domain accounts, Technical Issues
Domain Administrator, Share Access Controls
Domain Controller, Key Points Learned, The Nature of Windows Networking Protocols, Technical Issues, Implementation, Use and Location of BDCs
closest, The Nature of Windows Networking Protocols
domain controller, Security Identifiers (SIDs), Applicable to All Samba 2.x to Samba-3 Upgrades
domain controllers, Technical Issues
Domain Controllers, Questions and Answers
Domain Groups
well-known, Initialization of the LDAP Database
Domain join, Samba Domain with Samba Domain Member Server Using NSS LDAP
domain master, NT4 Migration Using LDAP Backend, NT4 Migration Using tdbsam Backend
Domain Master Browser (see DMB)
Domain Member, Use and Location of BDCs
authoritative
local accounts, Technical Issues
client, Implementation
desktop, Introduction
server, Introduction, Technical Issues, Implementation, Active Directory Domain with Samba Domain Member Server
servers, Questions and Answers, Checkpoint Controls
workstations, Implementation
domain member
servers, Technical Issues
Domain Member server, Technical Issues, Questions and Answers
Domain Member servers, Questions and Answers
domain members, Questions and Answers
domain name space, Identity Management Needs
domain replication, Questions and Answers
domain SID, Security Identifiers (SIDs)
Domain SID, Technical Issues, Questions and Answers
domain tree, Identity Management Needs
Domain User Manager, Configuring Profile Directories
Domain users, Technical Issues
DOS, Security Identifiers (SIDs)
dos2unix, Samba Configuration, Configuration for Server: MASSIVE
down-grade, Introduction
drive letters, LDAP Server Configuration
drive mapping, Technical Issues
dumb printing, Installation of Printer Driver Auto-Download
dump, Technical Issues, Questions and Answers
duplicate accounts, NT4/Samba Domain with Samba Domain Member Server: Using NSS and Winbind
dynamic DNS, Technical Issues

F

fail, The Nature of Windows Networking Protocols
fail-over, Identity Management Needs, Implementation
failed, Samba Domain with Samba Domain Member Server Using NSS LDAP
failed join, Samba Domain with Samba Domain Member Server Using NSS LDAP, Active Directory Domain with Samba Domain Member Server, IDMAP_RID with Winbind
failure, Samba Configuration
familiar, Technical Issues
fatal problem, Samba Configuration
fear, Technical Issues
fears, Technical Issues
Fedora, Drafting Office
FHS, Samba System File Location
file and print server, Questions and Answers
file and print service, Dissection and Discussion
file caching, Samba Configuration, Opportunistic Locking Controls
File Hierarchy System (see FHS)
file locations, Samba System File Location
file permissions, The LDAP Account Manager
file server
read-only, Dissection and Discussion
file servers, Samba Server Implementation
file system, Technical Issues
access control, Samba Configuration
Ext3, Implementation
permissions, Samba Configuration, Configuration for Server: MASSIVE
file system security, Questions and Answers
filter, Share Access Controls
financial responsibility, Introduction
firewall, Technical Issues, Basic System Configuration, Introduction
fix, Dissection and Discussion
flaws, Introduction
flexibility, Technical Issues
flush
cache memory, Opportunistic Locking Controls
folder redirection, Technical Issues, Configuration of Default Profile with Folder Redirection, Questions and Answers
force group, Override Controls, Questions and Answers
force user, Dissection and Discussion, Override Controls, Questions and Answers
forced settings, Override Controls
foreign, Samba Domain with Samba Domain Member Server Using NSS LDAP
foreign SID, Samba Domain with Samba Domain Member Server Using NSS LDAP
forwarded, Routed Networks
foundation members, Technical Issues
Free Standards Group (see FSG)
free support, Samba Support, Free Support
front-end, Dissection and Discussion
server, Distribute Network Load with MSDFS
frustration, Introduction
FSG, Samba System File Location
FTP
proxy, Questions and Answers
full control, Share Access Controls, Using MS Windows Explorer (File Manager)
fully qualified, Checkpoint Controls
functional differences, Cautions and Notes

G

generation, Cautions and Notes
Gentoo, Migrating NetWare Server to Samba-3
getent, LDAP Initialization and Creation of User and Group Accounts, Samba-3 BDC Configuration, Samba Domain with Samba Domain Member Server Using NSS LDAP, NT4/Samba Domain with Samba Domain Member Server: Using NSS and Winbind, Active Directory Domain with Samba Domain Member Server, IDMAP_RID with Winbind
getfacl, Setting Posix ACLs in UNIX/Linux
getgrnam, Technical Issues
getpwnam, Technical Issues, Samba Domain with Samba Domain Member Server Using NSS LDAP
getpwnam(), Questions and Answers
GID, Implementation, Questions and Answers, Questions and Answers
Goettingen, Questions and Answers
government, Identity Management Needs
GPL, Comments Regarding Software Terms of Use
group account, Implementation, OpenLDAP Server Configuration
group management, Implementation
group mapping, LDAP Server Configuration
group membership, Implementation, Samba Configuration, Samba Domain with Samba Domain Member Server Using NSS LDAP, Share Point Directory and File Permissions
group names, Questions and Answers
group policies, Introduction
Group Policy, Joining a Domain: Windows 200x/XP Professional
Group Policy editor, The Local Group Policy
Group Policy Objects, The Local Group Policy
groupadd, Implementation, Implementation, Applicable to All Samba 2.x to Samba-3 Upgrades, Questions and Answers
groupdel, Applicable to All Samba 2.x to Samba-3 Upgrades, Questions and Answers
groupmem, NT4 Migration Using LDAP Backend
groupmod, Applicable to All Samba 2.x to Samba-3 Upgrades, Questions and Answers
GSS-API, Windows 200x/XP Client Interaction with Samba-3
guest account, Findings and Comments, Dissection and Discussion, Technical Issues, Questions and Answers

I

Idealx, Applicable to All Samba 2.x to Samba-3 Upgrades, NT4 Migration Using LDAP Backend
smbldap-tools, Install and Configure Idealx smbldap-tools Scripts, LDAP Initialization and Creation of User and Group Accounts
identifiers, Technical Issues
identity, Questions and Answers, Kerberos Exposed
management, Technical Issues
identity management, Technical Issues, Dissection and Discussion, Political Issues, Dissection and Discussion
Identity Management, Dissection and Discussion, The Nature of Windows Networking Protocols, Identity Management Needs
Identity management, UNIX/Linux Client Domain Member
Identity resolution, Samba Domain with Samba Domain Member Server Using NSS LDAP, Active Directory Domain with Samba Domain Member Server, UNIX/Linux Client Domain Member, Questions and Answers
Identity resolver, Questions and Answers
IDMAP, Samba Domain with Samba Domain Member Server Using NSS LDAP, IDMAP_RID with Winbind
idmap backend, Technical Issues
IDMAP backend, Questions and Answers
idmap gid, IDMAP_RID with Winbind
idmap uid, IDMAP_RID with Winbind
idmap_rid, IDMAP_RID with Winbind
IMAP, Technical Issues
import, Technical Issues
income, Dissection and Discussion
independent expert, Introduction
inetd, Process Startup Configuration
inetOrgPerson, Technical Issues
inheritance, Setting Posix ACLs in UNIX/Linux
initGrps.sh, Implementation, Samba Configuration, Configuration for Server: MASSIVE
initial credentials, Kerberos Configuration
inoperative, Dissection and Discussion
install, Updating Samba-3
installation, Dissection and Discussion
integrate, Technical Issues
integrity, Introduction, Kerberos Exposed
inter-domain, Applicable to All Samba 2.x to Samba-3 Upgrades
inter-operability, Dissection and Discussion, Technical Issues, Key Points Learned, Questions and Answers
interactive help, Free Support
interdomain trusts, Identity Management Needs
interfaces, Implementation
intermittent, Hardware Problems
internationalization, International Language Support
Internet Explorer, Technical Issues
Internet Information Server, Questions and Answers
interoperability, Dissection and Discussion
IP forwarding, Implementation, Basic System Configuration, Configuration for Server: MASSIVE
IPC$, Findings and Comments
iptables, Technical Issues
IRC, Free Support
isolated, Introduction
Italian, Questions and Answers

L

LAM, The LDAP Account Manager
configuration editor, The LDAP Account Manager
configuration file, The LDAP Account Manager
login screen, The LDAP Account Manager
opening screen, The LDAP Account Manager
profile, The LDAP Account Manager
wizard, The LDAP Account Manager
large domain, IDMAP_RID with Winbind
LDAP, Technical Issues, Assignment Tasks, Dissection and Discussion, Technical Issues, Preliminary Advice: Dangers Can Be Avoided, PAM and NSS Client Configuration, Introduction, Dissection and Discussion, Identity Management Needs, Implementation, Key Points Learned, Questions and Answers, Technical Issues, NT4/Samba Domain with Samba Domain Member Server: Using NSS and Winbind, Active Directory Domain with Samba Domain Member Server, Questions and Answers, Security Identifiers (SIDs), Applicable to All Samba 2.x to Samba-3 Upgrades, Assignment Tasks, Technical Issues, Questions and Answers, Dissection and Discussion, LDAP Server Configuration, Technical Issues
backend, Identity Management Needs
database, LDAP Initialization and Creation of User and Group Accounts, Identity Management Needs, Questions and Answers, Alternative LDAP Database Initialization
directory, Regarding LDAP Directories and Windows Computer Accounts, Identity Management Needs
fail-over, Implementation
initial configuration, Alternative LDAP Database Initialization
master, Identity Management Needs
master/slave
background communication, Questions and Answers
preload, Implementation
schema, Updating from Samba Versions between 3.0.6 and 3.0.10
secure, Technical Issues
server, Questions and Answers
slave, Identity Management Needs
updates, Identity Management Needs
ldap, Samba Domain with Samba Domain Member Server Using NSS LDAP
LDAP Account Manager (see LAM)
LDAP backend, Technical Issues
LDAP database, Questions and Answers
LDAP Interchange Format (see LDIF)
LDAP server, Identity Management Needs
LDAP-transfer-LDIF.txt, Implementation
ldap.conf, Samba Domain with Samba Domain Member Server Using NSS LDAP
ldapadd, LDAP Initialization and Creation of User and Group Accounts, Samba Domain with Samba Domain Member Server Using NSS LDAP
ldapsam, LDAP Initialization and Creation of User and Group Accounts, Dissection and Discussion, Samba Domain with Samba Domain Member Server Using NSS LDAP, NT4/Samba Domain with Samba Domain Member Server: Using NSS and Winbind, Updating from Samba Versions between 3.0.6 and 3.0.10, Assignment Tasks, Integrating Additional Services
ldapsam backend, Samba Domain with Samba Domain Member Server Using NSS LDAP
ldapsearch, LDAP Initialization and Creation of User and Group Accounts
LDIF, Technical Issues, Implementation, Technical Issues, LDAP Server Configuration, Initialization of the LDAP Database
leadership, Technical Issues
Lightweight Directory Access Protocol (see LDAP)
limit, Questions and Answers
Linux desktop, Introduction
Linux Standards Base (see LSB)
LMB, Findings, Questions and Answers
LMHOSTS, Routed Networks
load distribution, For Scalability, Use SAN-Based Storage on Samba Servers
local accounts, Technical Issues
Local Group Policy, Roaming Profile Background
Local Master Announcement, Findings
Local Master Browser (see LMB)
localhost, Basic System Configuration, Bad Hostnames
lock directory, Samba 1.9.x and 2.x Versions Without LDAP
locking
Application level, Shared Data Integrity
Client side, Shared Data Integrity
Server side, Shared Data Integrity
logging, Removal of Pre-Existing Conflicting RPMs
login, Technical Issues
loglevel, Debugging LDAP
logon credentials, Questions and Answers
logon hours, Technical Issues, Key Points Learned
logon machines, Technical Issues
logon path, Implementation
logon process, Implementation
logon scrip, Samba Configuration
logon script, Implementation, Technical Issues, Preparation of Logon Scripts, Technical Issues
logon server, The Nature of Windows Networking Protocols
logon services, Implementation
logon time, Assignment Tasks
logon traffic, The Nature of Windows Networking Protocols
logon.kix, LDAP Server Configuration
loopback, Validation
low performance, Hardware Problems
lower-case, Implementation
lpadmin, Implementation, Implementation, Implementation, Printer Configuration, Printer Configuration
LSB, Samba System File Location

M

machine, Security Identifiers (SIDs)
machine account, Regarding LDAP Directories and Windows Computer Accounts
machine accounts, Questions and Answers
machine secret password, Technical Issues
MACHINE.SID, Security Identifiers (SIDs)
mailing list, Free Support
mailing lists, Free Support
managed, Technical Issues
management, Political Issues, Questions and Answers
group, Technical Issues
User, Technical Issues
mandatory profile, Technical Issues, Configuring Profile Directories
Mandrake, Migrating NetWare Server to Samba-3
mapped drives, Questions and Answers
mapping, Technical Issues, Kerberos Configuration
consistent, Samba Domain with Samba Domain Member Server Using NSS LDAP
Mars_NWE, Migrating NetWare Server to Samba-3
master, Dissection and Discussion
material, A Collection of Useful Tidbits
memberUID, LDAP Server Configuration
memory requirements, Hardware Requirements
merge, Technical Issues, Questions and Answers
merged, Technical Issues
meta-directory, Questions and Answers
meta-service, Questions and Answers
Microsoft Access, Shared Data Integrity
Microsoft Excel, Shared Data Integrity
Microsoft ISA, Assignment Tasks
Microsoft Management Console (see MMC)
Microsoft Office, Application Share Configuration, Share Point Directory and File Permissions
Microsoft Outlook
PST files, Questions and Answers
migrate, Updating Samba-3, Technical Issues
migration, Implementation, Implementation, Assignment Tasks, Introduction, Questions and Answers, Migrating NetWare Server to Samba-3
objectives, Dissection and Discussion
Migration speed, Questions and Answers
mime type, Implementation, Implementation, Printer Configuration, Server Preparation: All Servers, Printer Configuration
mime types, Implementation
missing RPC's, Technical Issues
MIT, Implementation, Kerberos Configuration
MIT Kerberos, Active Directory Domain with Samba Domain Member Server, Kerberos Exposed
MIT kerberos, IDMAP Storage in LDAP using Winbind
MIT KRB5, Samba Configuration
mixed mode, Active Directory Domain with Samba Domain Member Server
mixed-mode, Questions and Answers
MMC, Configure Delete Cached Profiles on Logout, Technical Issues, Questions and Answers
mobile computing, Dissection and Discussion
mobility, Technical Issues
modularization, Technical Issues
modules, Questions and Answers
MS Access
validate, Microsoft Access
MS Outlook, Configuration of MS Outlook to Relocate PST File
PST, Configuration of MS Outlook to Relocate PST File
PST file, Making Happy Users
MS Windows Server 2003, Implementation
MS Word, Share Point Directory and File Permissions
MSDFS, Distribute Network Load with MSDFS
multi-subnet, Routed Networks
multi-user
access, Microsoft Access
data access, Shared Data Integrity
multiple directories, Identity Management Needs
multiple domain controllers, Making Happy Users
multiple group mappings, Questions and Answers
mutual assistance, Free Support
My Documents, Roaming Profile Background
My Network Places, Implementation
mysqlsam, Implementation

N

name resolution, Configuration of DHCP and DNS Servers, Questions and Answers, Assignment Tasks
Defective, Active Directory Domain with Samba Domain Member Server
name resolve order, Implementation
name service switch, Implementation (see NSS)
named, Basic System Configuration, Validation, Server Preparation: All Servers
NAT, Technical Issues
native, Questions and Answers
net
ads
info, Active Directory Domain with Samba Domain Member Server
join, Active Directory Domain with Samba Domain Member Server, Questions and Answers, Samba Configuration
status, Active Directory Domain with Samba Domain Member Server
getlocalsid, Samba-3 PDC Configuration, Security Identifiers (SIDs)
group, NT4 Migration Using tdbsam Backend
groupmap
add, Samba Configuration
list, Samba Configuration, LDAP Initialization and Creation of User and Group Accounts
modify, Samba Configuration
rpc
info, Security Identifiers (SIDs)
join, Configuration Specific to Domain Member Servers: BLDG1, BLDG2, Samba Domain with Samba Domain Member Server Using NSS LDAP, NT4/Samba Domain with Samba Domain Member Server: Using NSS and Winbind, NT4/Samba Domain with Samba Domain Member Server without NSS Support, Active Directory Domain with Samba Domain Member Server, Questions and Answers, NT4 Migration Using tdbsam Backend
vampire, Updating Samba-3, NT4 Migration Using tdbsam Backend
setlocalsid, Security Identifiers (SIDs)
NetBIOS, The Nature of Windows Networking Protocols, Questions and Answers, Bad Hostnames, Routed Networks, Questions and Answers
name cache, Questions and Answers
name resolution
delays, Making Happy Users
Node Type, Questions and Answers
netbios
machine name, Change of hostname
netbios forwarding, Network Collisions
NetBIOS name, Kerberos Configuration
aliases, Identity Management Needs
netbios name, Security Identifiers (SIDs), Change of hostname, Bad Hostnames
NETLOGON, Using a Network Default User Profile, Windows Client Configuration
netlogon, The Nature of Windows Networking Protocols, LDAP Server Configuration
Netlogon, Joining a Domain: Windows 200x/XP Professional
netmask, Implementation
Netware, Small Office Networking
NetWare, Migrating NetWare Server to Samba-3, LDAP Server Configuration
network
administrators, Technical Issues
analyzer, Assignment Tasks
bandwidth, Identity Management Needs, Questions and Answers
broadcast, Introduction
captures, Requirements and Notes
collisions, Network Collisions
load, Network Collisions
logon, Making Happy Users
logon scripts, Dissection and Discussion
management, Introduction
multi-segment, Introduction
overload, Making Happy Users
performance, Samba Configuration
routed, Dissection and Discussion
secure, Introduction
segment, Dissection and Discussion
services, Questions and Answers
sniffer, Requirements and Notes
timeout, Making Happy Users
timeouts, Network Collisions
trace, Assignment Tasks
traffic
observation, Technical Issues
wide-area, Dissection and Discussion, NT4/Samba Domain with Samba Domain Member Server: Using NSS and Winbind
Network Address Translation (see NAT)
network administrators, Technical Issues
network attached storage (see NAS)
network bandwidth
utilization, Making Happy Users
Network Default Profile, Roaming Profile Background
network hardware
defective, Making Happy Users
network hygiene, Dissection and Discussion
network Identities, Questions and Answers
network load factors, Dissection and Discussion
Network Neighborhood, Validation, Technical Issues
network segment, Use and Location of BDCs
network segments, Hardware Requirements
network share, Assignment Tasks
networking
client, Security Identifiers (SIDs)
networking hardware
defective, Making Happy Users
networking protocols, Technical Issues
next generation, Technical Issues
NextFreeUnixId, NT4 Migration Using LDAP Backend
NFS server, Samba-3 PDC Configuration
NICs, Hardware Problems
NIS, LDAP Initialization and Creation of User and Group Accounts, Identity Management Needs, Questions and Answers, Technical Issues, Political Issues, Questions and Answers
nis, Samba Domain with Samba Domain Member Server Using NSS LDAP
NIS schema, Questions and Answers
NIS server, Questions and Answers
NIS+, Identity Management Needs
nisplus, Samba Domain with Samba Domain Member Server Using NSS LDAP
NLM, Migrating NetWare Server to Samba-3
nmap, Validation
nmbd, Validation, Validation, Samba 1.9.x and 2.x Versions Without LDAP, Replacing a Domain Member Server, Samba Configuration, Starting Samba
nobody, Removal of Pre-Existing Conflicting RPMs, Findings and Comments
Novell, Migrating NetWare Server to Samba-3, Introduction
Novell SUSE SLES 9, NT4 Migration Using LDAP Backend
NSS, Regarding LDAP Directories and Windows Computer Accounts, Technical Issues, PAM and NSS Client Configuration, Technical Issues, Samba Domain with Samba Domain Member Server Using NSS LDAP, NT4/Samba Domain with Samba Domain Member Server: Using NSS and Winbind, IDMAP_RID with Winbind, UNIX/Linux Client Domain Member, Questions and Answers, LDAP Server Configuration, NSS Configuration (see same service switch)
nss_ldap, Regarding LDAP Directories and Windows Computer Accounts, Technical Issues, OpenLDAP Server Configuration, PAM and NSS Client Configuration, LDAP Initialization and Creation of User and Group Accounts, Technical Issues, Samba Domain with Samba Domain Member Server Using NSS LDAP, IDMAP and NSS Using LDAP from ADS with RFC2307bis Schema Extension, Replacing a Domain Member Server, NT4 Migration Using LDAP Backend
nt acl support, Dissection and Discussion
NT4 registry, Dissection and Discussion
NTLM, Technical Issues
NTLM authentication daemon, Technical Issues
NTLMSSP, Key Points Learned, Questions and Answers, Windows 200x/XP Client Interaction with Samba-3
NTLMSSP_AUTH, Windows 200x/XP Client Interaction with Samba-3
ntlm_auth, Samba Configuration, Questions and Answers
NTP, Kerberos Configuration
NTUSER.DAT, Roaming Profile Background, Profile Changes, Using a Network Default User Profile, Questions and Answers
NULL connection, Validation
NULL session, Findings and Comments
NULL-Session, Discussion

P

package, Implementation
package names, Samba System File Location
packages, Updating a Samba-3 Installation
PADL, Technical Issues, IDMAP Storage in LDAP using Winbind
PADL LDAP tools, Technical Issues
PADL Software, Samba Domain with Samba Domain Member Server Using NSS LDAP
paid-for support, Samba Support
PAM, PAM and NSS Client Configuration, UNIX/Linux Client Domain Member, LDAP Server Configuration
pam_ldap, OpenLDAP Server Configuration
pam_ldap.so, PAM and NSS Client Configuration
pam_unix2.so, PAM and NSS Client Configuration
use_ldap, PAM and NSS Client Configuration
parameters, Applicable to All Samba 2.x to Samba-3 Upgrades
passdb backend, Implementation, The 500-User Office, Dissection and Discussion, Dissection and Discussion, Implementation, Technical Issues, Questions and Answers, Updating Samba-3, Security Identifiers (SIDs), Applicable to All Samba 2.x to Samba-3 Upgrades, Updating from Samba Versions between 3.0.6 and 3.0.10, Assignment Tasks, Questions and Answers
passdb.tdb, Technical Issues
passwd, Implementation, Implementation, Samba Configuration
password
backend, Implementation, Samba Configuration, Configuration for Server: MASSIVE
password caching, Implementation
password change, Key Points Learned
password length, Simple Windows Client Connection Characteristics, Windows 200x/XP Client Interaction with Samba-3
payroll, Introduction
pdbedit, LDAP Initialization and Creation of User and Group Accounts, Samba-3 BDC Configuration, NT4 Migration Using tdbsam Backend, Questions and Answers
PDC, Assignment Tasks, Technical Issues, Making Happy Users, Technical Issues, The Local Group Policy, The Nature of Windows Networking Protocols, Technical Issues, Questions and Answers, Security Identifiers (SIDs), Applicable to All Samba 2.x to Samba-3 Upgrades, Implementation, NT4 Migration Using LDAP Backend, NT4 Migration Using tdbsam Backend, Use and Location of BDCs
PDC/BDC ratio, Making Happy Users
PDF, The LDAP Account Manager
performance, Dissection and Discussion, Questions and Answers, Performance, Reliability, and Availability, Introduction, Network Collisions
performance degradation, Override Controls, Samba Configuration
Perl, LDAP Server Configuration, The LDAP Account Manager
permission, Share Point Directory and File Permissions
permissions, Implementation, Technical Issues, Share Access Controls, Checkpoint Controls, Share Point Directory and File Permissions, Removal of Pre-Existing Conflicting RPMs
excessive, Technical Issues
group, Share Point Directory and File Permissions
user, Share Point Directory and File Permissions
Permissions, Using the MMC Computer Management Interface
permits, Technical Issues
permitted group, Using the MMC Computer Management Interface
PHP, The LDAP Account Manager
PHP4, The LDAP Account Manager
pile-driver, Share Definition Controls
ping, Validation
pitfalls, The LDAP Account Manager
plain-text, Questions and Answers
Pluggable Authentication Modules (see PAM)
policy, Questions and Answers, Introduction
poor performance, Dissection and Discussion
POP3, Technical Issues
Posix, Dissection and Discussion, Technical Issues, Questions and Answers, Implementation, Questions and Answers, The LDAP Account Manager
POSIX, Regarding LDAP Directories and Windows Computer Accounts, LDAP Server Configuration
Posix accounts, LDAP Initialization and Creation of User and Group Accounts, Technical Issues
Posix ACLs, Managing Windows 200x ACLs
PosixAccount, LDAP Initialization and Creation of User and Group Accounts
posixAccount, LDAP Server Configuration
Postfix, LDAP Server Configuration
Postscript, Installation of Printer Driver Auto-Download
powers, Share Definition Controls
practices, Introduction
precaution, Introduction
presence and leadership, Technical Issues
price paid, Dissection and Discussion
primary group, Samba Domain with Samba Domain Member Server Using NSS LDAP, Share Point Directory and File Permissions
principals, Kerberos Exposed
print filter, Implementation, Printer Configuration, Server Preparation: All Servers, Printer Configuration
print queue, Charity Administration Office, Dissection and Discussion
print spooler, Charity Administration Office
Print Test Page, Uploading Printer Drivers to Samba Servers
printcap name, Implementation
printer validation, Validation, Validation
printers
Advanced, Uploading Printer Drivers to Samba Servers
Default Settings, Uploading Printer Drivers to Samba Servers
General, Uploading Printer Drivers to Samba Servers
Properties, Uploading Printer Drivers to Samba Servers
Security, Uploading Printer Drivers to Samba Servers
Sharing, Uploading Printer Drivers to Samba Servers
printing, Implementation
drag-and-drop, Installation of Printer Driver Auto-Download, Uploading Printer Drivers to Samba Servers
dumb, Installation of Printer Driver Auto-Download
point-n-click, Installation of Printer Driver Auto-Download
raw, Dissection and Discussion
privacy, Identity Management Needs
Privilege Attribute Certificates (see PAC)
privilege controls, Share Point Directory and File Permissions
privileged pipe, Samba Configuration
privileges, Identity Management Needs, Updating from Samba Versions after 3.0.6 to a Current Release, Technical Issues, Share Definition Controls
problem report, Free Support
problem resolution, Samba Support
product defects, Dissection and Discussion
professional support, Free Support
profile
default, Assignment Tasks
mandatory, The Nature of Windows Networking Protocols
roaming, Making Happy Users
profile path, Technical Issues
profile share, Implementation
profiles, Security Identifiers (SIDs)
profiles share, Dissection and Discussion
programmer, Dissection and Discussion
project, Free Support
project maintainers, Technical Issues
Properties, Using the MMC Computer Management Interface
proprietary, Technical Issues
protected, Technical Issues
protection, Technical Issues
protocol
negotiation, The Nature of Windows Networking Protocols
protocol analysis, Requirements and Notes
protocols, Technical Issues
provided services, Samba Support
proxy, Assignment Tasks, Technical Issues
PST file, Configuration of MS Outlook to Relocate PST File
public specifications, Technical Issues
purchase support, Free Support

Q

Qbasic, LDAP Server Configuration
qualified problem, Free Support

R

RAID, Hardware Requirements
RAID controllers, Hardware Problems
Raw Print Through, Installation of Printer Driver Auto-Download
raw printing, Implementation, Printer Configuration, Server Preparation: All Servers, Printer Configuration
Rbase, LDAP Server Configuration
rcldap, Implementation
realm, IDMAP_RID with Winbind, IDMAP Storage in LDAP using Winbind, Kerberos Configuration
recognize, Technical Issues
record locking, Microsoft Access
recursively, Setting Posix ACLs in UNIX/Linux
Red Hat, Drafting Office, Migrating NetWare Server to Samba-3
Red Hat Fedora Linux, Samba Configuration
Red Hat Linux, Dissection and Discussion, Accounting Office, Samba Server Implementation, PAM and NSS Client Configuration, Implementation, Active Directory Domain with Samba Domain Member Server, Implementation, Samba Configuration
redirected folders, Roaming Profile Background, The Nature of Windows Networking Protocols
refereed standards, Technical Issues
regedit, Implementation
regedt32, Profile Changes, Configuration of Default Profile with Folder Redirection
registry, Questions and Answers
keys
SAM, Dissection and Discussion
SECURITY, Dissection and Discussion
registry change, Questions and Answers
Registry Editor, Configuration of Default Profile with Folder Redirection
registry hacks, Questions and Answers
registry keys, Configuration of Default Profile with Folder Redirection
reimburse, Dissection and Discussion
rejected, Samba Domain with Samba Domain Member Server Using NSS LDAP, Share Access Controls
rejoin, Questions and Answers
reliability, Performance, Reliability, and Availability
remote announce, Routed Networks
remote browse sync, Routed Networks
remote procedure call (see RPC)
replicate, Questions and Answers, Replicate Data to Conserve Peak-Demand Wide-Area Bandwidth
replicated, Dissection and Discussion
requesting payment, Free Support
resilient, Guidelines for Reliable Samba Operation
resolution, Replacing a Domain Member Server
resolve, Technical Issues, Bad Hostnames
response, IDMAP_RID with Winbind
responsibility, Dissection and Discussion
responsible, Technical Issues
restrict anonymous, Samba Domain with Samba Domain Member Server Using NSS LDAP
restricted export, Kerberos Exposed
Restrictive security, Active Directory Domain with Samba Domain Member Server
reverse DNS, Kerberos Configuration
rfc2307bis, IDMAP and NSS Using LDAP from ADS with RFC2307bis Schema Extension
RID, IDMAP_RID with Winbind, LDAP Server Configuration
risk, Technical Issues, Questions and Answers, Questions and Answers, Introduction
road-map, Technical Issues
published, Technical Issues
roaming profile, Technical Issues, Roaming Profile Background, Configuring Profile Directories, User Needs, Questions and Answers
roaming profiles, Technical Issues, Implementation, Roaming Profile Background
routed network, Use and Location of BDCs
router, Implementation
routers, Questions and Answers, Routed Networks
RPC, Active Directory Domain with Samba Domain Member Server, Kerberos Exposed
rpc, Security Identifiers (SIDs)
rpcclient, Security Identifiers (SIDs)
RPM, Security Identifiers (SIDs), Samba 1.9.x and 2.x Versions Without LDAP, Dissection and Discussion
install, Implementation
rpm, Removal of Pre-Existing Conflicting RPMs, Samba System File Location
RPMs, Samba Configuration
rpms, Removal of Pre-Existing Conflicting RPMs
rsync, Samba-3 PDC Configuration, Questions and Answers, LDAP Server Configuration, Replicate Data to Conserve Peak-Demand Wide-Area Bandwidth
rsyncd.conf, LDAP Server Configuration
run-time control files, Samba System File Location

S

safe-guards, Technical Issues
SAM, Dissection and Discussion
samba, Removal of Pre-Existing Conflicting RPMs
starting samba, Implementation
Samba, Samba Configuration
Samba accounts, Technical Issues
samba cluster, Introduction
samba control script, Starting Samba
Samba Domain, NT4/Samba Domain with Samba Domain Member Server: Using NSS and Winbind, Questions and Answers
Samba Domain server, Using the MMC Computer Management Interface
Samba RPM Packages, Samba-3 PDC Configuration
Samba Tea, Samba Configuration
sambaDomainName, NT4 Migration Using LDAP Backend
sambaGroupMapping, LDAP Server Configuration
SambaSAMAccount, Regarding LDAP Directories and Windows Computer Accounts
SambaSamAccount, LDAP Initialization and Creation of User and Group Accounts
sambaSamAccount, LDAP Server Configuration
SambaXP conference, Questions and Answers
SAN, For Scalability, Use SAN-Based Storage on Samba Servers
SAS, Security Identifiers (SIDs)
scalability, Introduction
scalable, Identity Management Needs
schannel, Technical Issues, Key Points Learned, Questions and Answers
schema, IDMAP and NSS Using LDAP from ADS with RFC2307bis Schema Extension, Questions and Answers, Samba-2.x with LDAP Support, Updating from Samba Versions between 3.0.6 and 3.0.10
scripts, The LDAP Account Manager
secondary group, Samba Domain with Samba Domain Member Server Using NSS LDAP
secret, Kerberos Exposed
secrets.tdb, Technical Issues, Samba-3 PDC Configuration, Security Identifiers (SIDs), Location of config files
secure, Introduction
secure account password, Questions and Answers
secure connections, The LDAP Account Manager
secure networking, Technical Issues
secure networking protocols, Technical Issues
security, Technical Issues, Questions and Answers, Security Identifiers (SIDs), Introduction, Technical Issues, Share Point Directory and File Permissions, Questions and Answers
identifier, Security Identifiers (SIDs)
share mode, Dissection and Discussion
user mode, Dissection and Discussion
Security, Technical Issues, Using the MMC Computer Management Interface
Security Account Manager (see SAM)
security controls, Technical Issues
security descriptors, Dissection and Discussion
security fixes, Technical Issues
security updates, Technical Issues
SerNet, Active Directory Domain with Samba Domain Member Server, Samba Configuration
server
domain member, Security Identifiers (SIDs)
stand-alone, Security Identifiers (SIDs)
service, Implementation
smb
start, Configuration Specific to Domain Member Servers: BLDG1, BLDG2
Service Packs, Application Share Configuration
services, Key Points Learned
services provided, Samba Support
session setup, Simple Windows Client Connection Characteristics, Windows 200x/XP Client Interaction with Samba-3
Session Setup, Simple Windows Client Connection Characteristics
SessionSetUpAndX, Security Identifiers (SIDs)
set primary group script, Applicable to All Samba 2.x to Samba-3 Upgrades
setfacl, Setting Posix ACLs in UNIX/Linux
severely degrade, Samba Configuration
SFU, IDMAP, Active Directory, and MS Services for UNIX 3.5
SGID, Dissection and Discussion, Share Point Directory and File Permissions, Effect of Setting File and Directory SUID/SGID Permissions Explained
shadow-utils, Questions and Answers
Share Access Controls, Share Access Controls
share ACLs, Questions and Answers
share definition, Technical Issues
Share Definition
Controls, Share Definition Controls
share definition controls, Share Definition Controls, Checkpoint Controls, Share Point Directory and File Permissions, Questions and Answers
share level access controls, Questions and Answers
share level ACL, Questions and Answers
Share Permissions, Share Access Controls
shared resource, Technical Issues, Setting Posix ACLs in UNIX/Linux
shares, Technical Issues
SID, Windows Client Configuration, Regarding LDAP Directories and Windows Computer Accounts, Identity Management Needs, Technical Issues, IDMAP_RID with Winbind, Security Identifiers (SIDs), Change of Workgroup (Domain) Name, Questions and Answers, Initialization of the LDAP Database
side effects, Managing Windows 200x ACLs
Sign'n'seal, Key Points Learned, Questions and Answers
silent return, Active Directory Domain with Samba Domain Member Server
simple, Dissection and Discussion
Single Sign-On (see SSO)
slapcat, LDAP Initialization and Creation of User and Group Accounts, Samba Domain with Samba Domain Member Server Using NSS LDAP, LDAP Server Configuration
slapd, Debugging LDAP
slapd.conf, NT4 Migration Using LDAP Backend
slave, Dissection and Discussion
slow logon, Making Happy Users
slow network, Hardware Problems
slurpd, Implementation, Questions and Answers
smart printing, Dissection and Discussion
SMB, Security Identifiers (SIDs)
SMB passwords, Implementation
SMB/CIFS, Questions and Answers
smbclient, Validation, Validation, LDAP Initialization and Creation of User and Group Accounts, Questions and Answers
smbd, Validation, Implementation, Validation, Validation, Samba-3 PDC Configuration, Technical Issues, Active Directory Domain with Samba Domain Member Server, Security Identifiers (SIDs), Location of config files, Samba 1.9.x and 2.x Versions Without LDAP, Replacing a Domain Member Server, Samba Configuration, Questions and Answers, Starting Samba
location of files, Samba System File Location
smbfs, Dissection and Discussion
smbldap-groupadd, LDAP Initialization and Creation of User and Group Accounts, LDAP Server Configuration
smbldap-groupmod, LDAP Server Configuration
smbldap-passwd, LDAP Initialization and Creation of User and Group Accounts
smbldap-populate, LDAP Initialization and Creation of User and Group Accounts
smbldap-tools, NT4 Migration Using LDAP Backend, LDAP Server Configuration, The LDAP Account Manager
smbldap-tools updating, NT4 Migration Using LDAP Backend
smbldap-useradd, LDAP Initialization and Creation of User and Group Accounts, Implementation
smbldap-usermod, LDAP Initialization and Creation of User and Group Accounts, LDAP Server Configuration
smbmnt, Dissection and Discussion
smbmount, Dissection and Discussion
smbpasswd, Implementation, Technical Issues, Implementation, Technical Issues, Samba Configuration, Server Preparation: All Servers, Configuration for Server: MASSIVE, Samba-3 PDC Configuration, LDAP Initialization and Creation of User and Group Accounts, Samba-3 BDC Configuration, Dissection and Discussion, Implementation, Questions and Answers, Updating Samba-3, Security Identifiers (SIDs), Applicable to All Samba 2.x to Samba-3 Upgrades, Technical Issues, Questions and Answers, Integrating Additional Services
smbumnt, Dissection and Discussion
smbumount, Dissection and Discussion
SMTP, Technical Issues
snap-shot, Dissection and Discussion
socket address, Samba Configuration
socket options, Samba Configuration
software, Dissection and Discussion
solve, Dissection and Discussion
source code, Dissection and Discussion
SPNEGO, Windows 200x/XP Client Interaction with Samba-3
SQL, Dissection and Discussion, Questions and Answers
Squid, Implementation, Removal of Pre-Existing Conflicting RPMs, Samba Configuration, Squid Configuration
squid, Removal of Pre-Existing Conflicting RPMs, Samba Configuration
Squid proxy, Technical Issues
SRVTOOLS.EXE, Implementation, Configuring Profile Directories, Questions and Answers, Questions and Answers
SSL, The LDAP Account Manager
stand-alone server, Security Identifiers (SIDs)
starting CUPS, Implementation, Implementation, Process Startup Configuration, Process Startup Configuration
starting dhcpd, Implementation, Process Startup Configuration, Process Startup Configuration
starting samba, Implementation, Implementation, Implementation, Implementation, Process Startup Configuration, Process Startup Configuration
nmbd, Starting Samba
smbd, Starting Samba
winbindd, Starting Samba
startingCUPS, Implementation
startup script, Starting Samba
sticky bit, Implementation
storage capacity, Hardware Requirements
strategic, Technical Issues
strategy, Questions and Answers
straw-man, Active Directory, Kerberos, and Security
strict sync, Samba Configuration
stripped, Samba 1.9.x and 2.x Versions Without LDAP
strong cryptography, Kerberos Exposed
subscription, Free Support
SUID, Dissection and Discussion, Questions and Answers, Effect of Setting File and Directory SUID/SGID Permissions Explained
Sun ONE Identity Server, Dissection and Discussion
super daemon, Process Startup Configuration
support, Dissection and Discussion, Samba Support
survey, Adding Domain Member Servers and Clients
SUSE, Migrating NetWare Server to Samba-3
SUSE Enterprise Linux Server, Charity Administration Office, Basic System Configuration, Implementation
SUSE Linux, Dissection and Discussion, Samba Server Implementation, PAM and NSS Client Configuration, Implementation, Active Directory Domain with Samba Domain Member Server, Implementation, Removal of Pre-Existing Conflicting RPMs
SWAT, Samba System File Location
sync always, Samba Configuration
synchronization, Kerberos Configuration, For Scalability, Use SAN-Based Storage on Samba Servers
synchronize, User Needs, LDAP Server Configuration
synchronized, Questions and Answers
syslog, OpenLDAP Server Configuration
system level logins, Questions and Answers
system security, Technical Issues

T

tattooing, Questions and Answers
TCP/IP, Questions and Answers
tdbdump, NT4/Samba Domain with Samba Domain Member Server: Using NSS and Winbind, Active Directory Domain with Samba Domain Member Server, NT4 Migration Using LDAP Backend
tdbsam, Technical Issues, Implementation, The 500-User Office, Assignment Tasks, Dissection and Discussion, Implementation, NT4/Samba Domain with Samba Domain Member Server: Using NSS and Winbind, Questions and Answers, Applicable to All Samba 2.x to Samba-3 Upgrades, Updating from Samba Versions between 3.0.6 and 3.0.10, Technical Issues, Questions and Answers
testparm, Validation, Validation, Samba-3 PDC Configuration, Active Directory Domain with Samba Domain Member Server, Samba 1.9.x and 2.x Versions Without LDAP, Samba Configuration
ticket, Samba Configuration
time server, Implementation
Tivoli Directory Server, Dissection and Discussion
TLS, LDAP Server Configuration
token, Technical Issues
tool, Questions and Answers, Dissection and Discussion
TOSHARG2, Implementation
track record, Dissection and Discussion
traffic collisions, Making Happy Users
transaction processing, Dissection and Discussion
transactional, Questions and Answers
transfer, Questions and Answers
translate, Managing Windows 200x ACLs
traverse, NT4/Samba Domain with Samba Domain Member Server: Using NSS and Winbind
tree, Dissection and Discussion
Tree Connect, Simple Windows Client Connection Characteristics
trust account, Regarding LDAP Directories and Windows Computer Accounts
trusted computing, Introduction
Trusted Domains, Technical Issues
trusted domains, Questions and Answers
trusted third-party, Kerberos Exposed
trusting, Kerberos Exposed
turn-around time, Technical Issues

U

UDP
broadcast, Routed Networks
UID, Dissection and Discussion, Regarding LDAP Directories and Windows Computer Accounts, Technical Issues, Implementation, Questions and Answers, Questions and Answers
un-join, Questions and Answers
unauthorized activities, Kerberos Exposed
UNC name, Questions and Answers
unencrypted, The LDAP Account Manager
Unicast, The Nature of Windows Networking Protocols
unicode, International Language Support
Universal Naming Convention (see UNC name)
UNIX, LDAP Server Configuration
groups, Technical Issues, Implementation
UNIX accounts, Technical Issues
UNIX/Linux server, Technical Issues
unix2dos, Samba Configuration, Configuration for Server: MASSIVE
unknown, Technical Issues
unsupported software, Commercial Support
update, Introduction, Cautions and Notes
updates, Introduction, Technical Issues
updating smbldap-tools, NT4 Migration Using LDAP Backend
upgrade, Introduction, Cautions and Notes, LDAP Server Configuration
uppercase, Implementation
user
management, Implementation, Samba Configuration, Configuration for Server: MASSIVE
user account, Making Happy Users, OpenLDAP Server Configuration
User and Group Controls, Technical Issues
user credentials, Identity Management Needs, UNIX/Linux Client Domain Member
user errors, Questions and Answers
user groups, Free Support
user identities, Implementation
user logins, Questions and Answers
user management, Implementation
User Manager, NT4 Migration Using LDAP Backend
User Mode, Implementation, Simple Windows Client Connection Characteristics, Windows 200x/XP Client Interaction with Samba-3
useradd, Implementation, Implementation, Implementation, Samba Configuration, Configuration for Server: MASSIVE, Applicable to All Samba 2.x to Samba-3 Upgrades
userdel, Applicable to All Samba 2.x to Samba-3 Upgrades
usermod, Applicable to All Samba 2.x to Samba-3 Upgrades, NT4 Migration Using LDAP Backend
username, Security Identifiers (SIDs)
username map, Implementation, Samba Configuration, Server Preparation: All Servers
UTF-8, International Language Support
utilities, Questions and Answers

W

wbinfo, Samba Domain with Samba Domain Member Server Using NSS LDAP, NT4/Samba Domain with Samba Domain Member Server: Using NSS and Winbind, Active Directory Domain with Samba Domain Member Server, Samba Configuration
weakness, Technical Issues
web
caching, Assignment Tasks
proxying, Assignment Tasks
Web
proxy, Questions and Answers
access, Key Points Learned
Web browsers, Key Points Learned
WebClient, Making Happy Users
WHATSNEW.txt, Samba-2.x with LDAP Support
white-pages, Technical Issues, LDAP Server Configuration
wide-area, User Needs, Identity Management Needs, Key Points Learned, Questions and Answers, NT4/Samba Domain with Samba Domain Member Server: Using NSS and Winbind
wide-area network, Use and Location of BDCs, Replicate Data to Conserve Peak-Demand Wide-Area Bandwidth
winbind, Implementation, Dissection and Discussion, NT4/Samba Domain with Samba Domain Member Server: Using NSS and Winbind, Questions and Answers, Introduction, Technical Issues, Technical Issues, Samba Configuration, NSS Configuration
Winbind, Questions and Answers, Technical Issues, Key Points Learned
winbind trusted domains only, Technical Issues, Questions and Answers
winbind use default domain, Checkpoint Controls
winbindd, Validation, Validation, Technical Issues, Technical Issues, Samba Domain with Samba Domain Member Server Using NSS LDAP, Questions and Answers, Samba 1.9.x and 2.x Versions Without LDAP, Updating from Samba Versions after 3.0.6 to a Current Release, Replacing a Domain Member Server, Samba Configuration, Questions and Answers, Starting Samba
winbindd_cache.tdb, Technical Issues
winbindd_idmap.tdb, Technical Issues
Windows, LDAP Server Configuration
client, Security Identifiers (SIDs)
NT, Security Identifiers (SIDs)
Windows 2000 ACLs, Managing Windows 200x ACLs
Windows 2003 Serve, Introduction
Windows 200x ACLs, Questions and Answers
Windows accounts, Technical Issues
Windows ACLs, Setting Posix ACLs in UNIX/Linux
Windows Address Book, LDAP Server Configuration
Windows ADS Domain, NT4/Samba Domain with Samba Domain Member Server: Using NSS and Winbind
Windows clients, Questions and Answers
Windows Explorer, Validation
Windows explorer, Questions and Answers
Windows security identifier (see SID)
Windows Servers, Introduction
Windows Services for UNIX (see SUS)
Windows XP, Assignment Tasks
WINS, Implementation, Technical Issues, Implementation, Windows Client Configuration, Technical Issues, Windows Client Configuration, The Nature of Windows Networking Protocols, Identity Management Needs, Questions and Answers, Questions and Answers
lookup, Questions and Answers
name resolution, Routed Networks
server, Making Happy Users, Routed Networks
WINS server, The 500-User Office, Questions and Answers
WINS serving, Implementation
wins support, Implementation
wins.dat, Identity Management Needs, Replacing a Domain Member Server
Wireshark, Requirements and Notes
wireshark, Exercises
Word, Share Point Directory and File Permissions
workgroup, Implementation, Security Identifiers (SIDs), Change of Workgroup (Domain) Name
Workgroup Announcement, Findings
workstation, Implementation
wrapper, Questions and Answers
write lock, Opportunistic Locking Controls

Y

YaST, PAM and NSS Client Configuration
Yellow Pages, Identity Management Needs
yellow pages (see NIS)
+Index

Index

Symbols

%LOGONSERVER%, Configuration of Default Profile with Folder Redirection
%USERNAME%, Roaming Profile Background, Profile Changes
%USERPROFILE%, Configuration of Default Profile with Folder Redirection
/data/ldap, OpenLDAP Server Configuration
/etc/cups/mime.convs, Implementation, Implementation
/etc/cups/mime.types, Implementation, Implementation
/etc/dhcpd.conf, Implementation, Validation, Configuration of DHCP and DNS Servers, Validation
/etc/exports, Samba-3 PDC Configuration
/etc/group, Technical Issues, Samba Domain with Samba Domain Member Server Using NSS LDAP, Replacing a Domain Member Server, Questions and Answers, Removal of Pre-Existing Conflicting RPMs
/etc/hosts, Implementation, Implementation, Basic System Configuration, Validation, Server Preparation: All Servers, Questions and Answers, Kerberos Configuration, Bad Hostnames
/etc/krb5.conf, IDMAP Storage in LDAP using Winbind, Kerberos Configuration
/etc/ldap.conf, PAM and NSS Client Configuration, IDMAP Storage in LDAP using Winbind, IDMAP and NSS Using LDAP from ADS with RFC2307bis Schema Extension, NT4 Migration Using LDAP Backend, LDAP Server Configuration
/etc/mime.convs, Implementation, Printer Configuration, Server Preparation: All Servers, Printer Configuration
/etc/mime.types, Implementation, Printer Configuration, Server Preparation: All Servers, Printer Configuration
/etc/named.conf, Configuration of DHCP and DNS Servers
/etc/nsswitch.conf, Implementation, Configuration of DHCP and DNS Servers, Validation, Configuration for Server: MASSIVE, Configuration Specific to Domain Member Servers: BLDG1, BLDG2, PAM and NSS Client Configuration, NT4/Samba Domain with Samba Domain Member Server: Using NSS and Winbind, IDMAP_RID with Winbind, IDMAP and NSS Using LDAP from ADS with RFC2307bis Schema Extension, Questions and Answers, NT4 Migration Using LDAP Backend
/etc/openldap/slapd.conf, Debugging LDAP, OpenLDAP Server Configuration, Implementation
/etc/passwd, Implementation, Samba Configuration, Configuration for Server: MASSIVE, LDAP Initialization and Creation of User and Group Accounts, Samba Domain with Samba Domain Member Server Using NSS LDAP, NT4/Samba Domain with Samba Domain Member Server: Using NSS and Winbind, Questions and Answers, Replacing a Domain Member Server, Technical Issues, Questions and Answers, Technical Issues, Share Point Directory and File Permissions, Removal of Pre-Existing Conflicting RPMs, Findings and Comments
/etc/rc.d/boot.local, Basic System Configuration, Configuration for Server: MASSIVE
/etc/rc.d/rc.local, Implementation
/etc/resolv.conf, Configuration of DHCP and DNS Servers, Server Preparation: All Servers
/etc/samba, Samba System File Location
/etc/samba/secrets.tdb, Active Directory Domain with Samba Domain Member Server
/etc/samba/smbusers, Server Preparation: All Servers
/etc/shadow, Replacing a Domain Member Server, Technical Issues
/etc/squid/squid.conf, Removal of Pre-Existing Conflicting RPMs
/etc/syslog.conf, Debugging LDAP
/etc/xinetd.d, Process Startup Configuration, Process Startup Configuration
/lib/libnss_ldap.so.2, PAM and NSS Client Configuration
/opt/IDEALX/sbin, NT4 Migration Using LDAP Backend
/proc/sys/net/ipv4/ip_forward, Implementation, Basic System Configuration
/usr/bin, Samba System File Location
/usr/lib/samba, Samba System File Location
/usr/local, Samba System File Location
/usr/local/samba, Samba System File Location
/usr/local/samba/var/locks, Samba 1.9.x and 2.x Versions Without LDAP
/usr/sbin, Samba System File Location
/usr/share, Samba System File Location
/usr/share/samba/swat, Samba System File Location
/usr/share/swat, Samba System File Location
/var/cache/samba, Samba 1.9.x and 2.x Versions Without LDAP
/var/lib/samba, Samba 1.9.x and 2.x Versions Without LDAP, Samba System File Location
/var/log/ldaplogs, Debugging LDAP
/var/log/samba, Samba System File Location
8-bit, International Language Support

A

abmas-netfw.sh, Basic System Configuration
accept, Printer Configuration
accepts liability, Dissection and Discussion
access, Technical Issues, Checkpoint Controls
access control, Kerberos Exposed, Using the MMC Computer Management Interface
Access Control Lists (see ACLs)
access control settings, Share Access Controls
access controls, Technical Issues, Share Definition Controls
accessible, Share Point Directory and File Permissions
account, Regarding LDAP Directories and Windows Computer Accounts, Share Access Controls
ADS Domain, Technical Issues
account credentials, Findings and Comments
account information, Questions and Answers
account names, Questions and Answers
account policies, The LDAP Account Manager
accountable, Introduction, Dissection and Discussion
accounts
authoritative, Technical Issues
Domain, Introduction, Questions and Answers
group, Introduction, Questions and Answers, Introduction
machine, Introduction, Questions and Answers
manage, The LDAP Account Manager
user, Introduction, Questions and Answers, Introduction
ACL, Security Identifiers (SIDs), Checkpoint Controls
ACLs, Key Points Learned, Share Access Controls, Share Definition Controls
acquisitions, Introduction
Act!, Shared Data Integrity
ACT! database, Act! Database Sharing
Act!Diag, Act! Database Sharing
Active Directory, Dissection and Discussion, The Local Group Policy, Dissection and Discussion, Assignment Tasks, Active Directory Domain with Samba Domain Member Server, IDMAP_RID with Winbind, Questions and Answers, Introduction, Key Points Learned, Questions and Answers, Integrating Additional Services, Assignment Tasks, Technical Issues, Samba Configuration, Joining a Domain: Windows 200x/XP Professional
authentication, Squid Configuration
domain, Samba Configuration
join, Active Directory Domain with Samba Domain Member Server
management tools, Technical Issues
realm, Bad Hostnames
Replacement, Technical Issues
server, Active Directory Domain with Samba Domain Member Server, Kerberos Configuration
Server, Technical Issues
tree, Samba Configuration
active directory, Technical Issues
AD printer publishing, Uploading Printer Drivers to Samba Servers
ADAM, Dissection and Discussion, IDMAP Storage in LDAP using Winbind
add group script, Applicable to All Samba 2.x to Samba-3 Upgrades
add machine script, Applicable to All Samba 2.x to Samba-3 Upgrades
Add Printer Wizard
APW, Uploading Printer Drivers to Samba Servers
add user script, Applicable to All Samba 2.x to Samba-3 Upgrades
add user to group script, Applicable to All Samba 2.x to Samba-3 Upgrades
adduser, Implementation, Samba Configuration, Configuration for Server: MASSIVE
adequate precautions, Introduction
administrative installation, Application Share Configuration
administrative rights, Checkpoint Controls
administrator, Implementation, Samba Configuration, Server Preparation: All Servers
ADMT, Migration of Samba Accounts to Active Directory
ADS, IDMAP Storage in LDAP using Winbind, Technical Issues, Kerberos Configuration, Bad Hostnames
server, Technical Issues
ADS Domain, Technical Issues
affordability, The Nature of Windows Networking Protocols
alarm, Introduction
algorithm, Technical Issues
allow trusted domains, IDMAP_RID with Winbind
alternative, Dissection and Discussion
analysis, Technical Issues
anonymous connection, Validation, Validation
Apache Web server, Questions and Answers
appliance mode, Technical Issues
application server, Technical Issues, Application Share Configuration
application servers, The Nature of Windows Networking Protocols
application/octet-stream, Implementation, Implementation, Implementation, Printer Configuration, Server Preparation: All Servers, Printer Configuration
APW, Uploading Printer Drivers to Samba Servers
arp, Validation
assessment, Introduction
assistance, Free Support
assumptions, Key Points Learned
authconfig, PAM and NSS Client Configuration
authenticate, LDAP Server Configuration, Samba Configuration
authenticated, Assignment Tasks
authenticated connection, Validation, Validation
authentication, The Nature of Windows Networking Protocols, Questions and Answers, Dissection and Discussion, Integrating Additional Services, Technical Issues, NSS Configuration, Questions and Answers
plain-text, Questions and Answers
authentication process, Implementation
authentication protocols, Key Points Learned
authoritative, Technical Issues
authorized location, Kerberos Exposed
auto-generated SID, Questions and Answers
automatically allocate, Technical Issues
availability, Performance, Reliability, and Availability

C

cache, Opportunistic Locking Controls
cache directories, Removal of Pre-Existing Conflicting RPMs
caching, Samba Configuration
case-sensitive, Kerberos Configuration
centralized storage, Questions and Answers
character set, International Language Support
check samba daemons, Validation, Validation
check-point, Share Definition Controls
check-point controls, Checkpoint Controls
Checkpoint Controls, Checkpoint Controls
chgrp, Samba Configuration
chkconfig, Implementation, Implementation, Implementation, Implementation, Process Startup Configuration, Process Startup Configuration, Implementation
chmod, Samba Configuration
choice, Dissection and Discussion, Technical Issues
chown, Removal of Pre-Existing Conflicting RPMs
CIFS, Security Identifiers (SIDs), Findings
cifsfs, Dissection and Discussion
clean database, Questions and Answers
clients per DC, Making Happy Users
Clock skew, Kerberos Configuration
cluster, Introduction
clustering, Introduction, For Scalability, Use SAN-Based Storage on Samba Servers
code maintainer, Free Support
codepage, International Language Support
collision rates, Network Collisions
commercial, Dissection and Discussion
commercial software, Dissection and Discussion
commercial support, Samba Support, Commercial Support
Common Internet File System (see CIFS)
comparison
Active Directory & OpenLDAP, Dissection and Discussion
compat, Samba Domain with Samba Domain Member Server Using NSS LDAP
compatible, Technical Issues
compile-time, Location of config files
complexities, Dissection and Discussion
compromise, Introduction, Introduction, Technical Issues
computer account, Samba Configuration
Computer Management, Share Access Controls, Questions and Answers
computer name, Security Identifiers (SIDs)
condemns, Technical Issues
conferences, Technical Issues
configuration files, Introduction
configure.pl, NT4 Migration Using LDAP Backend
connection, Share Access Controls
connectivity, Questions and Answers
consequential risk, Technical Issues
consultant, Drafting Office, Introduction, Dissection and Discussion
consumer, Dissection and Discussion, Technical Issues
consumer expects, Samba Support
contiguous directory, Implementation
contributions, Updating Samba-3
control files, Updating a Samba-3 Installation
convmv, International Language Support
copy, Questions and Answers
corrective action, Hardware Problems
cost, Dissection and Discussion
cost-benefit, Assignment Tasks
country of origin, Commercial Support
Courier-IMAP, LDAP Server Configuration
credential, Share Definition Controls
credentials, NT4/Samba Domain with Samba Domain Member Server: Using NSS and Winbind, Technical Issues
crippled, Dissection and Discussion
criticism, Active Directory, Kerberos, and Security, Introduction
Critics, Technical Issues
Cryptographic, Technical Issues
CUPS, Dissection and Discussion, Technical Issues, Implementation, Key Points Learned, Implementation, Printer Configuration, Server Preparation: All Servers, Assignment Tasks, Installation of Printer Driver Auto-Download, Printer Configuration
queue, Implementation, Printer Configuration, Server Preparation: All Servers, Printer Configuration
cupsd, Basic System Configuration
customer expected, Samba Support
customers, Samba Support

D

daemon, Validation, Basic System Configuration, Security Identifiers (SIDs), Technical Issues, Questions and Answers, Starting Samba
daemon control, Process Startup Configuration
data
corruption, Making Happy Users
integrity, Questions and Answers
data corruption, Hardware Problems, Act! Database Sharing
data integrity, Hardware Problems, Shared Data Integrity
data storage, Implementation
database, Dissection and Discussion, Questions and Answers, Dissection and Discussion
database applications, Shared Data Integrity
DB_CONFIG, OpenLDAP Server Configuration
DCE, Kerberos Exposed
DDNS (see dynamic DNS)
Debian, Migrating NetWare Server to Samba-3
default installation, Samba System File Location
default password, The LDAP Account Manager
default profile, Assignment Tasks, Technical Issues
Default User, Profile Changes, Configuration of Default Profile with Folder Redirection
defective
cables, Hardware Problems
HUBs, Hardware Problems
switches, Hardware Problems
defects, Technical Issues
defensible standards, Technical Issues
defragmentation, Windows Client Configuration
delete group script, Applicable to All Samba 2.x to Samba-3 Upgrades
delete user from group script, Applicable to All Samba 2.x to Samba-3 Upgrades
delimiter, Checkpoint Controls
dependability, Technical Issues
deployment, Free Support
desired security setting, Setting Posix ACLs in UNIX/Linux
development, Technical Issues
DHCP, Technical Issues, Implementation, Key Points Learned, Windows Client Configuration, Windows Client Configuration, The Nature of Windows Networking Protocols, Questions and Answers
client, Bad Hostnames
relay, Technical Issues
Relay Agent, Questions and Answers
request, Questions and Answers
requests, Technical Issues
servers, Questions and Answers
traffic, Questions and Answers
dhcp client validation, Validation, Validation
DHCP Server, Implementation
DHCP server, Technical Issues
diagnostic, IDMAP Storage in LDAP using Winbind
diffusion, Technical Issues
digital rights, Technical Issues
digital sign'n'seal, Technical Issues
digits, Bad Hostnames
diligence, Technical Issues
directory, Dissection and Discussion, Political Issues, Location of config files
Computers container, LDAP Initialization and Creation of User and Group Accounts
management, Dissection and Discussion
People container, LDAP Initialization and Creation of User and Group Accounts
replication, Dissection and Discussion
schema, Dissection and Discussion
server, Technical Issues
synchronization, Dissection and Discussion
directory tree, Setting Posix ACLs in UNIX/Linux
disable, Introduction
disaster recovery, Introduction
disk image, Assignment Tasks
disruptive, Dissection and Discussion
distributed, Identity Management Needs, Implementation, Questions and Answers, Distribute Network Load with MSDFS
distributed domain, Identity Management Needs
DMB, Questions and Answers
DMS, Security Identifiers (SIDs), Replacing a Domain Member Server
DNS, Technical Issues, Implementation, Technical Issues, The Nature of Windows Networking Protocols, LDAP Server Configuration, Bad Hostnames, Routed Networks, Joining a Domain: Windows 200x/XP Professional
configuration, Questions and Answers
Dynamic, Questions and Answers
dynamic, Joining a Domain: Windows 200x/XP Professional
lookup, Questions and Answers, Kerberos Configuration
name lookup, Bad Hostnames
SRV records, Kerberos Configuration
suffix, Joining a Domain: Windows 200x/XP Professional
DNS server, Implementation, Configuration of DHCP and DNS Servers
document the settings, Samba Configuration
documentation, Dissection and Discussion, Technical Issues
documented, Samba Configuration
Domain, Technical Issues
groups, Technical Issues
domain
Active Directory, Technical Issues
controller, Replacing a Domain Controller
joining, A Collection of Useful Tidbits
trusted, Questions and Answers
Domain accounts, Technical Issues
Domain Administrator, Share Access Controls
Domain Controller, Key Points Learned, The Nature of Windows Networking Protocols, Technical Issues, Implementation, Use and Location of BDCs
closest, The Nature of Windows Networking Protocols
domain controller, Security Identifiers (SIDs), Applicable to All Samba 2.x to Samba-3 Upgrades
domain controllers, Technical Issues
Domain Controllers, Questions and Answers
Domain Groups
well-known, Initialization of the LDAP Database
Domain join, Samba Domain with Samba Domain Member Server Using NSS LDAP
domain master, NT4 Migration Using LDAP Backend, NT4 Migration Using tdbsam Backend
Domain Master Browser (see DMB)
Domain Member, Use and Location of BDCs
authoritative
local accounts, Technical Issues
client, Implementation
desktop, Introduction
server, Introduction, Technical Issues, Implementation, Active Directory Domain with Samba Domain Member Server
servers, Questions and Answers, Checkpoint Controls
workstations, Implementation
domain member
servers, Technical Issues
Domain Member server, Technical Issues, Questions and Answers
Domain Member servers, Questions and Answers
domain members, Questions and Answers
domain name space, Identity Management Needs
domain replication, Questions and Answers
domain SID, Security Identifiers (SIDs)
Domain SID, Technical Issues, Questions and Answers
domain tree, Identity Management Needs
Domain User Manager, Configuring Profile Directories
Domain users, Technical Issues
DOS, Security Identifiers (SIDs)
dos2unix, Samba Configuration, Configuration for Server: MASSIVE
down-grade, Introduction
drive letters, LDAP Server Configuration
drive mapping, Technical Issues
dumb printing, Installation of Printer Driver Auto-Download
dump, Technical Issues, Questions and Answers
duplicate accounts, NT4/Samba Domain with Samba Domain Member Server: Using NSS and Winbind
dynamic DNS, Technical Issues

F

fail, The Nature of Windows Networking Protocols
fail-over, Identity Management Needs, Implementation
failed, Samba Domain with Samba Domain Member Server Using NSS LDAP
failed join, Samba Domain with Samba Domain Member Server Using NSS LDAP, Active Directory Domain with Samba Domain Member Server, IDMAP_RID with Winbind
failure, Samba Configuration
familiar, Technical Issues
fatal problem, Samba Configuration
fear, Technical Issues
fears, Technical Issues
Fedora, Drafting Office
FHS, Samba System File Location
file and print server, Questions and Answers
file and print service, Dissection and Discussion
file caching, Samba Configuration, Opportunistic Locking Controls
File Hierarchy System (see FHS)
file locations, Samba System File Location
file permissions, The LDAP Account Manager
file server
read-only, Dissection and Discussion
file servers, Samba Server Implementation
file system, Technical Issues
access control, Samba Configuration
Ext3, Implementation
permissions, Samba Configuration, Configuration for Server: MASSIVE
file system security, Questions and Answers
filter, Share Access Controls
financial responsibility, Introduction
firewall, Technical Issues, Basic System Configuration, Introduction
fix, Dissection and Discussion
flaws, Introduction
flexibility, Technical Issues
flush
cache memory, Opportunistic Locking Controls
folder redirection, Technical Issues, Configuration of Default Profile with Folder Redirection, Questions and Answers
force group, Override Controls, Questions and Answers
force user, Dissection and Discussion, Override Controls, Questions and Answers
forced settings, Override Controls
foreign, Samba Domain with Samba Domain Member Server Using NSS LDAP
foreign SID, Samba Domain with Samba Domain Member Server Using NSS LDAP
forwarded, Routed Networks
foundation members, Technical Issues
Free Standards Group (see FSG)
free support, Samba Support, Free Support
front-end, Dissection and Discussion
server, Distribute Network Load with MSDFS
frustration, Introduction
FSG, Samba System File Location
FTP
proxy, Questions and Answers
full control, Share Access Controls, Using MS Windows Explorer (File Manager)
fully qualified, Checkpoint Controls
functional differences, Cautions and Notes

G

generation, Cautions and Notes
Gentoo, Migrating NetWare Server to Samba-3
getent, LDAP Initialization and Creation of User and Group Accounts, Samba-3 BDC Configuration, Samba Domain with Samba Domain Member Server Using NSS LDAP, NT4/Samba Domain with Samba Domain Member Server: Using NSS and Winbind, Active Directory Domain with Samba Domain Member Server, IDMAP_RID with Winbind
getfacl, Setting Posix ACLs in UNIX/Linux
getgrnam, Technical Issues
getpwnam, Technical Issues, Samba Domain with Samba Domain Member Server Using NSS LDAP
getpwnam(), Questions and Answers
GID, Implementation, Questions and Answers, Questions and Answers
Goettingen, Questions and Answers
government, Identity Management Needs
GPL, Comments Regarding Software Terms of Use
group account, Implementation, OpenLDAP Server Configuration
group management, Implementation
group mapping, LDAP Server Configuration
group membership, Implementation, Samba Configuration, Samba Domain with Samba Domain Member Server Using NSS LDAP, Share Point Directory and File Permissions
group names, Questions and Answers
group policies, Introduction
Group Policy, Joining a Domain: Windows 200x/XP Professional
Group Policy editor, The Local Group Policy
Group Policy Objects, The Local Group Policy
groupadd, Implementation, Implementation, Applicable to All Samba 2.x to Samba-3 Upgrades, Questions and Answers
groupdel, Applicable to All Samba 2.x to Samba-3 Upgrades, Questions and Answers
groupmem, NT4 Migration Using LDAP Backend
groupmod, Applicable to All Samba 2.x to Samba-3 Upgrades, Questions and Answers
GSS-API, Windows 200x/XP Client Interaction with Samba-3
guest account, Findings and Comments, Dissection and Discussion, Technical Issues, Questions and Answers

I

Idealx, Applicable to All Samba 2.x to Samba-3 Upgrades, NT4 Migration Using LDAP Backend
smbldap-tools, Install and Configure Idealx smbldap-tools Scripts, LDAP Initialization and Creation of User and Group Accounts
identifiers, Technical Issues
identity, Questions and Answers, Kerberos Exposed
management, Technical Issues
identity management, Technical Issues, Dissection and Discussion, Political Issues, Dissection and Discussion
Identity Management, Dissection and Discussion, The Nature of Windows Networking Protocols, Identity Management Needs
Identity management, UNIX/Linux Client Domain Member
Identity resolution, Samba Domain with Samba Domain Member Server Using NSS LDAP, Active Directory Domain with Samba Domain Member Server, UNIX/Linux Client Domain Member, Questions and Answers
Identity resolver, Questions and Answers
IDMAP, Samba Domain with Samba Domain Member Server Using NSS LDAP, IDMAP_RID with Winbind
idmap backend, Technical Issues
IDMAP backend, Questions and Answers
idmap gid, IDMAP_RID with Winbind
idmap uid, IDMAP_RID with Winbind
idmap_rid, IDMAP_RID with Winbind
IMAP, Technical Issues
import, Technical Issues
income, Dissection and Discussion
independent expert, Introduction
inetd, Process Startup Configuration
inetOrgPerson, Technical Issues
inheritance, Setting Posix ACLs in UNIX/Linux
initGrps.sh, Implementation, Samba Configuration, Configuration for Server: MASSIVE
initial credentials, Kerberos Configuration
inoperative, Dissection and Discussion
install, Updating Samba-3
installation, Dissection and Discussion
integrate, Technical Issues
integrity, Introduction, Kerberos Exposed
inter-domain, Applicable to All Samba 2.x to Samba-3 Upgrades
inter-operability, Dissection and Discussion, Technical Issues, Key Points Learned, Questions and Answers
interactive help, Free Support
interdomain trusts, Identity Management Needs
interfaces, Implementation
intermittent, Hardware Problems
internationalization, International Language Support
Internet Explorer, Technical Issues
Internet Information Server, Questions and Answers
interoperability, Dissection and Discussion
IP forwarding, Implementation, Basic System Configuration, Configuration for Server: MASSIVE
IPC$, Findings and Comments
iptables, Technical Issues
IRC, Free Support
isolated, Introduction
Italian, Questions and Answers

L

LAM, The LDAP Account Manager
configuration editor, The LDAP Account Manager
configuration file, The LDAP Account Manager
login screen, The LDAP Account Manager
opening screen, The LDAP Account Manager
profile, The LDAP Account Manager
wizard, The LDAP Account Manager
large domain, IDMAP_RID with Winbind
LDAP, Technical Issues, Assignment Tasks, Dissection and Discussion, Technical Issues, Preliminary Advice: Dangers Can Be Avoided, PAM and NSS Client Configuration, Introduction, Dissection and Discussion, Identity Management Needs, Implementation, Key Points Learned, Questions and Answers, Technical Issues, NT4/Samba Domain with Samba Domain Member Server: Using NSS and Winbind, Active Directory Domain with Samba Domain Member Server, Questions and Answers, Security Identifiers (SIDs), Applicable to All Samba 2.x to Samba-3 Upgrades, Assignment Tasks, Technical Issues, Questions and Answers, Dissection and Discussion, LDAP Server Configuration, Technical Issues
backend, Identity Management Needs
database, LDAP Initialization and Creation of User and Group Accounts, Identity Management Needs, Questions and Answers, Alternative LDAP Database Initialization
directory, Regarding LDAP Directories and Windows Computer Accounts, Identity Management Needs
fail-over, Implementation
initial configuration, Alternative LDAP Database Initialization
master, Identity Management Needs
master/slave
background communication, Questions and Answers
preload, Implementation
schema, Updating from Samba Versions between 3.0.6 and 3.0.10
secure, Technical Issues
server, Questions and Answers
slave, Identity Management Needs
updates, Identity Management Needs
ldap, Samba Domain with Samba Domain Member Server Using NSS LDAP
LDAP Account Manager (see LAM)
LDAP backend, Technical Issues
LDAP database, Questions and Answers
LDAP Interchange Format (see LDIF)
LDAP server, Identity Management Needs
LDAP-transfer-LDIF.txt, Implementation
ldap.conf, Samba Domain with Samba Domain Member Server Using NSS LDAP
ldapadd, LDAP Initialization and Creation of User and Group Accounts, Samba Domain with Samba Domain Member Server Using NSS LDAP
ldapsam, LDAP Initialization and Creation of User and Group Accounts, Dissection and Discussion, Samba Domain with Samba Domain Member Server Using NSS LDAP, NT4/Samba Domain with Samba Domain Member Server: Using NSS and Winbind, Updating from Samba Versions between 3.0.6 and 3.0.10, Assignment Tasks, Integrating Additional Services
ldapsam backend, Samba Domain with Samba Domain Member Server Using NSS LDAP
ldapsearch, LDAP Initialization and Creation of User and Group Accounts
LDIF, Technical Issues, Implementation, Technical Issues, LDAP Server Configuration, Initialization of the LDAP Database
leadership, Technical Issues
Lightweight Directory Access Protocol (see LDAP)
limit, Questions and Answers
Linux desktop, Introduction
Linux Standards Base (see LSB)
LMB, Findings, Questions and Answers
LMHOSTS, Routed Networks
load distribution, For Scalability, Use SAN-Based Storage on Samba Servers
local accounts, Technical Issues
Local Group Policy, Roaming Profile Background
Local Master Announcement, Findings
Local Master Browser (see LMB)
localhost, Basic System Configuration, Bad Hostnames
lock directory, Samba 1.9.x and 2.x Versions Without LDAP
locking
Application level, Shared Data Integrity
Client side, Shared Data Integrity
Server side, Shared Data Integrity
logging, Removal of Pre-Existing Conflicting RPMs
login, Technical Issues
loglevel, Debugging LDAP
logon credentials, Questions and Answers
logon hours, Technical Issues, Key Points Learned
logon machines, Technical Issues
logon path, Implementation
logon process, Implementation
logon scrip, Samba Configuration
logon script, Implementation, Technical Issues, Preparation of Logon Scripts, Technical Issues
logon server, The Nature of Windows Networking Protocols
logon services, Implementation
logon time, Assignment Tasks
logon traffic, The Nature of Windows Networking Protocols
logon.kix, LDAP Server Configuration
loopback, Validation
low performance, Hardware Problems
lower-case, Implementation
lpadmin, Implementation, Implementation, Implementation, Printer Configuration, Printer Configuration
LSB, Samba System File Location

M

machine, Security Identifiers (SIDs)
machine account, Regarding LDAP Directories and Windows Computer Accounts
machine accounts, Questions and Answers
machine secret password, Technical Issues
MACHINE.SID, Security Identifiers (SIDs)
mailing list, Free Support
mailing lists, Free Support
managed, Technical Issues
management, Political Issues, Questions and Answers
group, Technical Issues
User, Technical Issues
mandatory profile, Technical Issues, Configuring Profile Directories
Mandrake, Migrating NetWare Server to Samba-3
mapped drives, Questions and Answers
mapping, Technical Issues, Kerberos Configuration
consistent, Samba Domain with Samba Domain Member Server Using NSS LDAP
Mars_NWE, Migrating NetWare Server to Samba-3
master, Dissection and Discussion
material, A Collection of Useful Tidbits
memberUID, LDAP Server Configuration
memory requirements, Hardware Requirements
merge, Technical Issues, Questions and Answers
merged, Technical Issues
meta-directory, Questions and Answers
meta-service, Questions and Answers
Microsoft Access, Shared Data Integrity
Microsoft Excel, Shared Data Integrity
Microsoft ISA, Assignment Tasks
Microsoft Management Console (see MMC)
Microsoft Office, Application Share Configuration, Share Point Directory and File Permissions
Microsoft Outlook
PST files, Questions and Answers
migrate, Updating Samba-3, Technical Issues
migration, Implementation, Implementation, Assignment Tasks, Introduction, Questions and Answers, Migrating NetWare Server to Samba-3
objectives, Dissection and Discussion
Migration speed, Questions and Answers
mime type, Implementation, Implementation, Printer Configuration, Server Preparation: All Servers, Printer Configuration
mime types, Implementation
missing RPC's, Technical Issues
MIT, Implementation, Kerberos Configuration
MIT Kerberos, Active Directory Domain with Samba Domain Member Server, Kerberos Exposed
MIT kerberos, IDMAP Storage in LDAP using Winbind
MIT KRB5, Samba Configuration
mixed mode, Active Directory Domain with Samba Domain Member Server
mixed-mode, Questions and Answers
MMC, Configure Delete Cached Profiles on Logout, Technical Issues, Questions and Answers
mobile computing, Dissection and Discussion
mobility, Technical Issues
modularization, Technical Issues
modules, Questions and Answers
MS Access
validate, Microsoft Access
MS Outlook, Configuration of MS Outlook to Relocate PST File
PST, Configuration of MS Outlook to Relocate PST File
PST file, Making Happy Users
MS Windows Server 2003, Implementation
MS Word, Share Point Directory and File Permissions
MSDFS, Distribute Network Load with MSDFS
multi-subnet, Routed Networks
multi-user
access, Microsoft Access
data access, Shared Data Integrity
multiple directories, Identity Management Needs
multiple domain controllers, Making Happy Users
multiple group mappings, Questions and Answers
mutual assistance, Free Support
My Documents, Roaming Profile Background
My Network Places, Implementation
mysqlsam, Implementation

N

name resolution, Configuration of DHCP and DNS Servers, Questions and Answers, Assignment Tasks
Defective, Active Directory Domain with Samba Domain Member Server
name resolve order, Implementation
name service switch, Implementation (see NSS)
named, Basic System Configuration, Validation, Server Preparation: All Servers
NAT, Technical Issues
native, Questions and Answers
net
ads
info, Active Directory Domain with Samba Domain Member Server
join, Active Directory Domain with Samba Domain Member Server, Questions and Answers, Samba Configuration
status, Active Directory Domain with Samba Domain Member Server
getlocalsid, Samba-3 PDC Configuration, Security Identifiers (SIDs)
group, NT4 Migration Using tdbsam Backend
groupmap
add, Samba Configuration
list, Samba Configuration, LDAP Initialization and Creation of User and Group Accounts
modify, Samba Configuration
rpc
info, Security Identifiers (SIDs)
join, Configuration Specific to Domain Member Servers: BLDG1, BLDG2, Samba Domain with Samba Domain Member Server Using NSS LDAP, NT4/Samba Domain with Samba Domain Member Server: Using NSS and Winbind, NT4/Samba Domain with Samba Domain Member Server without NSS Support, Active Directory Domain with Samba Domain Member Server, Questions and Answers, NT4 Migration Using tdbsam Backend
vampire, Updating Samba-3, NT4 Migration Using tdbsam Backend
setlocalsid, Security Identifiers (SIDs)
NetBIOS, The Nature of Windows Networking Protocols, Questions and Answers, Bad Hostnames, Routed Networks, Questions and Answers
name cache, Questions and Answers
name resolution
delays, Making Happy Users
Node Type, Questions and Answers
netbios
machine name, Change of hostname
netbios forwarding, Network Collisions
NetBIOS name, Kerberos Configuration
aliases, Identity Management Needs
netbios name, Security Identifiers (SIDs), Change of hostname, Bad Hostnames
NETLOGON, Using a Network Default User Profile, Windows Client Configuration
netlogon, The Nature of Windows Networking Protocols, LDAP Server Configuration
Netlogon, Joining a Domain: Windows 200x/XP Professional
netmask, Implementation
Netware, Small Office Networking
NetWare, Migrating NetWare Server to Samba-3, LDAP Server Configuration
network
administrators, Technical Issues
analyzer, Assignment Tasks
bandwidth, Identity Management Needs, Questions and Answers
broadcast, Introduction
captures, Requirements and Notes
collisions, Network Collisions
load, Network Collisions
logon, Making Happy Users
logon scripts, Dissection and Discussion
management, Introduction
multi-segment, Introduction
overload, Making Happy Users
performance, Samba Configuration
routed, Dissection and Discussion
secure, Introduction
segment, Dissection and Discussion
services, Questions and Answers
sniffer, Requirements and Notes
timeout, Making Happy Users
timeouts, Network Collisions
trace, Assignment Tasks
traffic
observation, Technical Issues
wide-area, Dissection and Discussion, NT4/Samba Domain with Samba Domain Member Server: Using NSS and Winbind
Network Address Translation (see NAT)
network administrators, Technical Issues
network attached storage (see NAS)
network bandwidth
utilization, Making Happy Users
Network Default Profile, Roaming Profile Background
network hardware
defective, Making Happy Users
network hygiene, Dissection and Discussion
network Identities, Questions and Answers
network load factors, Dissection and Discussion
Network Neighborhood, Validation, Technical Issues
network segment, Use and Location of BDCs
network segments, Hardware Requirements
network share, Assignment Tasks
networking
client, Security Identifiers (SIDs)
networking hardware
defective, Making Happy Users
networking protocols, Technical Issues
next generation, Technical Issues
NextFreeUnixId, NT4 Migration Using LDAP Backend
NFS server, Samba-3 PDC Configuration
NICs, Hardware Problems
NIS, LDAP Initialization and Creation of User and Group Accounts, Identity Management Needs, Questions and Answers, Technical Issues, Political Issues, Questions and Answers
nis, Samba Domain with Samba Domain Member Server Using NSS LDAP
NIS schema, Questions and Answers
NIS server, Questions and Answers
NIS+, Identity Management Needs
nisplus, Samba Domain with Samba Domain Member Server Using NSS LDAP
NLM, Migrating NetWare Server to Samba-3
nmap, Validation
nmbd, Validation, Validation, Samba 1.9.x and 2.x Versions Without LDAP, Replacing a Domain Member Server, Samba Configuration, Starting Samba
nobody, Removal of Pre-Existing Conflicting RPMs, Findings and Comments
Novell, Migrating NetWare Server to Samba-3, Introduction
Novell SUSE SLES 9, NT4 Migration Using LDAP Backend
NSS, Regarding LDAP Directories and Windows Computer Accounts, Technical Issues, PAM and NSS Client Configuration, Technical Issues, Samba Domain with Samba Domain Member Server Using NSS LDAP, NT4/Samba Domain with Samba Domain Member Server: Using NSS and Winbind, IDMAP_RID with Winbind, UNIX/Linux Client Domain Member, Questions and Answers, LDAP Server Configuration, NSS Configuration (see same service switch)
nss_ldap, Regarding LDAP Directories and Windows Computer Accounts, Technical Issues, OpenLDAP Server Configuration, PAM and NSS Client Configuration, LDAP Initialization and Creation of User and Group Accounts, Technical Issues, Samba Domain with Samba Domain Member Server Using NSS LDAP, IDMAP and NSS Using LDAP from ADS with RFC2307bis Schema Extension, Replacing a Domain Member Server, NT4 Migration Using LDAP Backend
nt acl support, Dissection and Discussion
NT4 registry, Dissection and Discussion
NTLM, Technical Issues
NTLM authentication daemon, Technical Issues
NTLMSSP, Key Points Learned, Questions and Answers, Windows 200x/XP Client Interaction with Samba-3
NTLMSSP_AUTH, Windows 200x/XP Client Interaction with Samba-3
ntlm_auth, Samba Configuration, Questions and Answers
NTP, Kerberos Configuration
NTUSER.DAT, Roaming Profile Background, Profile Changes, Using a Network Default User Profile, Questions and Answers
NULL connection, Validation
NULL session, Findings and Comments
NULL-Session, Discussion

P

package, Implementation
package names, Samba System File Location
packages, Updating a Samba-3 Installation
PADL, Technical Issues, IDMAP Storage in LDAP using Winbind
PADL LDAP tools, Technical Issues
PADL Software, Samba Domain with Samba Domain Member Server Using NSS LDAP
paid-for support, Samba Support
PAM, PAM and NSS Client Configuration, UNIX/Linux Client Domain Member, LDAP Server Configuration
pam_ldap, OpenLDAP Server Configuration
pam_ldap.so, PAM and NSS Client Configuration
pam_unix2.so, PAM and NSS Client Configuration
use_ldap, PAM and NSS Client Configuration
parameters, Applicable to All Samba 2.x to Samba-3 Upgrades
passdb backend, Implementation, The 500-User Office, Dissection and Discussion, Dissection and Discussion, Implementation, Technical Issues, Questions and Answers, Updating Samba-3, Security Identifiers (SIDs), Applicable to All Samba 2.x to Samba-3 Upgrades, Updating from Samba Versions between 3.0.6 and 3.0.10, Assignment Tasks, Questions and Answers
passdb.tdb, Technical Issues
passwd, Implementation, Implementation, Samba Configuration
password
backend, Implementation, Samba Configuration, Configuration for Server: MASSIVE
password caching, Implementation
password change, Key Points Learned
password length, Simple Windows Client Connection Characteristics, Windows 200x/XP Client Interaction with Samba-3
payroll, Introduction
pdbedit, LDAP Initialization and Creation of User and Group Accounts, Samba-3 BDC Configuration, NT4 Migration Using tdbsam Backend, Questions and Answers
PDC, Assignment Tasks, Technical Issues, Making Happy Users, Technical Issues, The Local Group Policy, The Nature of Windows Networking Protocols, Technical Issues, Questions and Answers, Security Identifiers (SIDs), Applicable to All Samba 2.x to Samba-3 Upgrades, Implementation, NT4 Migration Using LDAP Backend, NT4 Migration Using tdbsam Backend, Use and Location of BDCs
PDC/BDC ratio, Making Happy Users
PDF, The LDAP Account Manager
performance, Dissection and Discussion, Questions and Answers, Performance, Reliability, and Availability, Introduction, Network Collisions
performance degradation, Override Controls, Samba Configuration
Perl, LDAP Server Configuration, The LDAP Account Manager
permission, Share Point Directory and File Permissions
permissions, Implementation, Technical Issues, Share Access Controls, Checkpoint Controls, Share Point Directory and File Permissions, Removal of Pre-Existing Conflicting RPMs
excessive, Technical Issues
group, Share Point Directory and File Permissions
user, Share Point Directory and File Permissions
Permissions, Using the MMC Computer Management Interface
permits, Technical Issues
permitted group, Using the MMC Computer Management Interface
PHP, The LDAP Account Manager
PHP4, The LDAP Account Manager
pile-driver, Share Definition Controls
ping, Validation
pitfalls, The LDAP Account Manager
plain-text, Questions and Answers
Pluggable Authentication Modules (see PAM)
policy, Questions and Answers, Introduction
poor performance, Dissection and Discussion
POP3, Technical Issues
Posix, Dissection and Discussion, Technical Issues, Questions and Answers, Implementation, Questions and Answers, The LDAP Account Manager
POSIX, Regarding LDAP Directories and Windows Computer Accounts, LDAP Server Configuration
Posix accounts, LDAP Initialization and Creation of User and Group Accounts, Technical Issues
Posix ACLs, Managing Windows 200x ACLs
PosixAccount, LDAP Initialization and Creation of User and Group Accounts
posixAccount, LDAP Server Configuration
Postfix, LDAP Server Configuration
Postscript, Installation of Printer Driver Auto-Download
powers, Share Definition Controls
practices, Introduction
precaution, Introduction
presence and leadership, Technical Issues
price paid, Dissection and Discussion
primary group, Samba Domain with Samba Domain Member Server Using NSS LDAP, Share Point Directory and File Permissions
principals, Kerberos Exposed
print filter, Implementation, Printer Configuration, Server Preparation: All Servers, Printer Configuration
print queue, Charity Administration Office, Dissection and Discussion
print spooler, Charity Administration Office
Print Test Page, Uploading Printer Drivers to Samba Servers
printcap name, Implementation
printer validation, Validation, Validation
printers
Advanced, Uploading Printer Drivers to Samba Servers
Default Settings, Uploading Printer Drivers to Samba Servers
General, Uploading Printer Drivers to Samba Servers
Properties, Uploading Printer Drivers to Samba Servers
Security, Uploading Printer Drivers to Samba Servers
Sharing, Uploading Printer Drivers to Samba Servers
printing, Implementation
drag-and-drop, Installation of Printer Driver Auto-Download, Uploading Printer Drivers to Samba Servers
dumb, Installation of Printer Driver Auto-Download
point-n-click, Installation of Printer Driver Auto-Download
raw, Dissection and Discussion
privacy, Identity Management Needs
Privilege Attribute Certificates (see PAC)
privilege controls, Share Point Directory and File Permissions
privileged pipe, Samba Configuration
privileges, Identity Management Needs, Updating from Samba Versions after 3.0.6 to a Current Release, Technical Issues, Share Definition Controls
problem report, Free Support
problem resolution, Samba Support
product defects, Dissection and Discussion
professional support, Free Support
profile
default, Assignment Tasks
mandatory, The Nature of Windows Networking Protocols
roaming, Making Happy Users
profile path, Technical Issues
profile share, Implementation
profiles, Security Identifiers (SIDs)
profiles share, Dissection and Discussion
programmer, Dissection and Discussion
project, Free Support
project maintainers, Technical Issues
Properties, Using the MMC Computer Management Interface
proprietary, Technical Issues
protected, Technical Issues
protection, Technical Issues
protocol
negotiation, The Nature of Windows Networking Protocols
protocol analysis, Requirements and Notes
protocols, Technical Issues
provided services, Samba Support
proxy, Assignment Tasks, Technical Issues
PST file, Configuration of MS Outlook to Relocate PST File
public specifications, Technical Issues
purchase support, Free Support

Q

Qbasic, LDAP Server Configuration
qualified problem, Free Support

R

RAID, Hardware Requirements
RAID controllers, Hardware Problems
Raw Print Through, Installation of Printer Driver Auto-Download
raw printing, Implementation, Printer Configuration, Server Preparation: All Servers, Printer Configuration
Rbase, LDAP Server Configuration
rcldap, Implementation
realm, IDMAP_RID with Winbind, IDMAP Storage in LDAP using Winbind, Kerberos Configuration
recognize, Technical Issues
record locking, Microsoft Access
recursively, Setting Posix ACLs in UNIX/Linux
Red Hat, Drafting Office, Migrating NetWare Server to Samba-3
Red Hat Fedora Linux, Samba Configuration
Red Hat Linux, Dissection and Discussion, Accounting Office, Samba Server Implementation, PAM and NSS Client Configuration, Implementation, Active Directory Domain with Samba Domain Member Server, Implementation, Samba Configuration
redirected folders, Roaming Profile Background, The Nature of Windows Networking Protocols
refereed standards, Technical Issues
regedit, Implementation
regedt32, Profile Changes, Configuration of Default Profile with Folder Redirection
registry, Questions and Answers
keys
SAM, Dissection and Discussion
SECURITY, Dissection and Discussion
registry change, Questions and Answers
Registry Editor, Configuration of Default Profile with Folder Redirection
registry hacks, Questions and Answers
registry keys, Configuration of Default Profile with Folder Redirection
reimburse, Dissection and Discussion
rejected, Samba Domain with Samba Domain Member Server Using NSS LDAP, Share Access Controls
rejoin, Questions and Answers
reliability, Performance, Reliability, and Availability
remote announce, Routed Networks
remote browse sync, Routed Networks
remote procedure call (see RPC)
replicate, Questions and Answers, Replicate Data to Conserve Peak-Demand Wide-Area Bandwidth
replicated, Dissection and Discussion
requesting payment, Free Support
resilient, Guidelines for Reliable Samba Operation
resolution, Replacing a Domain Member Server
resolve, Technical Issues, Bad Hostnames
response, IDMAP_RID with Winbind
responsibility, Dissection and Discussion
responsible, Technical Issues
restrict anonymous, Samba Domain with Samba Domain Member Server Using NSS LDAP
restricted export, Kerberos Exposed
Restrictive security, Active Directory Domain with Samba Domain Member Server
reverse DNS, Kerberos Configuration
rfc2307bis, IDMAP and NSS Using LDAP from ADS with RFC2307bis Schema Extension
RID, IDMAP_RID with Winbind, LDAP Server Configuration
risk, Technical Issues, Questions and Answers, Questions and Answers, Introduction
road-map, Technical Issues
published, Technical Issues
roaming profile, Technical Issues, Roaming Profile Background, Configuring Profile Directories, User Needs, Questions and Answers
roaming profiles, Technical Issues, Implementation, Roaming Profile Background
routed network, Use and Location of BDCs
router, Implementation
routers, Questions and Answers, Routed Networks
RPC, Active Directory Domain with Samba Domain Member Server, Kerberos Exposed
rpc, Security Identifiers (SIDs)
rpcclient, Security Identifiers (SIDs)
RPM, Security Identifiers (SIDs), Samba 1.9.x and 2.x Versions Without LDAP, Dissection and Discussion
install, Implementation
rpm, Removal of Pre-Existing Conflicting RPMs, Samba System File Location
RPMs, Samba Configuration
rpms, Removal of Pre-Existing Conflicting RPMs
rsync, Samba-3 PDC Configuration, Questions and Answers, LDAP Server Configuration, Replicate Data to Conserve Peak-Demand Wide-Area Bandwidth
rsyncd.conf, LDAP Server Configuration
run-time control files, Samba System File Location

S

safe-guards, Technical Issues
SAM, Dissection and Discussion
samba, Removal of Pre-Existing Conflicting RPMs
starting samba, Implementation
Samba, Samba Configuration
Samba accounts, Technical Issues
samba cluster, Introduction
samba control script, Starting Samba
Samba Domain, NT4/Samba Domain with Samba Domain Member Server: Using NSS and Winbind, Questions and Answers
Samba Domain server, Using the MMC Computer Management Interface
Samba RPM Packages, Samba-3 PDC Configuration
Samba Tea, Samba Configuration
sambaDomainName, NT4 Migration Using LDAP Backend
sambaGroupMapping, LDAP Server Configuration
SambaSAMAccount, Regarding LDAP Directories and Windows Computer Accounts
SambaSamAccount, LDAP Initialization and Creation of User and Group Accounts
sambaSamAccount, LDAP Server Configuration
SambaXP conference, Questions and Answers
SAN, For Scalability, Use SAN-Based Storage on Samba Servers
SAS, Security Identifiers (SIDs)
scalability, Introduction
scalable, Identity Management Needs
schannel, Technical Issues, Key Points Learned, Questions and Answers
schema, IDMAP and NSS Using LDAP from ADS with RFC2307bis Schema Extension, Questions and Answers, Samba-2.x with LDAP Support, Updating from Samba Versions between 3.0.6 and 3.0.10
scripts, The LDAP Account Manager
secondary group, Samba Domain with Samba Domain Member Server Using NSS LDAP
secret, Kerberos Exposed
secrets.tdb, Technical Issues, Samba-3 PDC Configuration, Security Identifiers (SIDs), Location of config files
secure, Introduction
secure account password, Questions and Answers
secure connections, The LDAP Account Manager
secure networking, Technical Issues
secure networking protocols, Technical Issues
security, Technical Issues, Questions and Answers, Security Identifiers (SIDs), Introduction, Technical Issues, Share Point Directory and File Permissions, Questions and Answers
identifier, Security Identifiers (SIDs)
share mode, Dissection and Discussion
user mode, Dissection and Discussion
Security, Technical Issues, Using the MMC Computer Management Interface
Security Account Manager (see SAM)
security controls, Technical Issues
security descriptors, Dissection and Discussion
security fixes, Technical Issues
security updates, Technical Issues
SerNet, Active Directory Domain with Samba Domain Member Server, Samba Configuration
server
domain member, Security Identifiers (SIDs)
stand-alone, Security Identifiers (SIDs)
service, Implementation
smb
start, Configuration Specific to Domain Member Servers: BLDG1, BLDG2
Service Packs, Application Share Configuration
services, Key Points Learned
services provided, Samba Support
session setup, Simple Windows Client Connection Characteristics, Windows 200x/XP Client Interaction with Samba-3
Session Setup, Simple Windows Client Connection Characteristics
SessionSetUpAndX, Security Identifiers (SIDs)
set primary group script, Applicable to All Samba 2.x to Samba-3 Upgrades
setfacl, Setting Posix ACLs in UNIX/Linux
severely degrade, Samba Configuration
SFU, IDMAP, Active Directory, and MS Services for UNIX 3.5
SGID, Dissection and Discussion, Share Point Directory and File Permissions, Effect of Setting File and Directory SUID/SGID Permissions Explained
shadow-utils, Questions and Answers
Share Access Controls, Share Access Controls
share ACLs, Questions and Answers
share definition, Technical Issues
Share Definition
Controls, Share Definition Controls
share definition controls, Share Definition Controls, Checkpoint Controls, Share Point Directory and File Permissions, Questions and Answers
share level access controls, Questions and Answers
share level ACL, Questions and Answers
Share Permissions, Share Access Controls
shared resource, Technical Issues, Setting Posix ACLs in UNIX/Linux
shares, Technical Issues
SID, Windows Client Configuration, Regarding LDAP Directories and Windows Computer Accounts, Identity Management Needs, Technical Issues, IDMAP_RID with Winbind, Security Identifiers (SIDs), Change of Workgroup (Domain) Name, Questions and Answers, Initialization of the LDAP Database
side effects, Managing Windows 200x ACLs
Sign'n'seal, Key Points Learned, Questions and Answers
silent return, Active Directory Domain with Samba Domain Member Server
simple, Dissection and Discussion
Single Sign-On (see SSO)
slapcat, LDAP Initialization and Creation of User and Group Accounts, Samba Domain with Samba Domain Member Server Using NSS LDAP, LDAP Server Configuration
slapd, Debugging LDAP
slapd.conf, NT4 Migration Using LDAP Backend
slave, Dissection and Discussion
slow logon, Making Happy Users
slow network, Hardware Problems
slurpd, Implementation, Questions and Answers
smart printing, Dissection and Discussion
SMB, Security Identifiers (SIDs)
SMB passwords, Implementation
SMB/CIFS, Questions and Answers
smbclient, Validation, Validation, LDAP Initialization and Creation of User and Group Accounts, Questions and Answers
smbd, Validation, Implementation, Validation, Validation, Samba-3 PDC Configuration, Technical Issues, Active Directory Domain with Samba Domain Member Server, Security Identifiers (SIDs), Location of config files, Samba 1.9.x and 2.x Versions Without LDAP, Replacing a Domain Member Server, Samba Configuration, Questions and Answers, Starting Samba
location of files, Samba System File Location
smbfs, Dissection and Discussion
smbldap-groupadd, LDAP Initialization and Creation of User and Group Accounts, LDAP Server Configuration
smbldap-groupmod, LDAP Server Configuration
smbldap-passwd, LDAP Initialization and Creation of User and Group Accounts
smbldap-populate, LDAP Initialization and Creation of User and Group Accounts
smbldap-tools, NT4 Migration Using LDAP Backend, LDAP Server Configuration, The LDAP Account Manager
smbldap-tools updating, NT4 Migration Using LDAP Backend
smbldap-useradd, LDAP Initialization and Creation of User and Group Accounts, Implementation
smbldap-usermod, LDAP Initialization and Creation of User and Group Accounts, LDAP Server Configuration
smbmnt, Dissection and Discussion
smbmount, Dissection and Discussion
smbpasswd, Implementation, Technical Issues, Implementation, Technical Issues, Samba Configuration, Server Preparation: All Servers, Configuration for Server: MASSIVE, Samba-3 PDC Configuration, LDAP Initialization and Creation of User and Group Accounts, Samba-3 BDC Configuration, Dissection and Discussion, Implementation, Questions and Answers, Updating Samba-3, Security Identifiers (SIDs), Applicable to All Samba 2.x to Samba-3 Upgrades, Technical Issues, Questions and Answers, Integrating Additional Services
smbumnt, Dissection and Discussion
smbumount, Dissection and Discussion
SMTP, Technical Issues
snap-shot, Dissection and Discussion
socket address, Samba Configuration
socket options, Samba Configuration
software, Dissection and Discussion
solve, Dissection and Discussion
source code, Dissection and Discussion
SPNEGO, Windows 200x/XP Client Interaction with Samba-3
SQL, Dissection and Discussion, Questions and Answers
Squid, Implementation, Removal of Pre-Existing Conflicting RPMs, Samba Configuration, Squid Configuration
squid, Removal of Pre-Existing Conflicting RPMs, Samba Configuration
Squid proxy, Technical Issues
SRVTOOLS.EXE, Implementation, Configuring Profile Directories, Questions and Answers, Questions and Answers
SSL, The LDAP Account Manager
stand-alone server, Security Identifiers (SIDs)
starting CUPS, Implementation, Implementation, Process Startup Configuration, Process Startup Configuration
starting dhcpd, Implementation, Process Startup Configuration, Process Startup Configuration
starting samba, Implementation, Implementation, Implementation, Implementation, Process Startup Configuration, Process Startup Configuration
nmbd, Starting Samba
smbd, Starting Samba
winbindd, Starting Samba
startingCUPS, Implementation
startup script, Starting Samba
sticky bit, Implementation
storage capacity, Hardware Requirements
strategic, Technical Issues
strategy, Questions and Answers
straw-man, Active Directory, Kerberos, and Security
strict sync, Samba Configuration
stripped, Samba 1.9.x and 2.x Versions Without LDAP
strong cryptography, Kerberos Exposed
subscription, Free Support
SUID, Dissection and Discussion, Questions and Answers, Effect of Setting File and Directory SUID/SGID Permissions Explained
Sun ONE Identity Server, Dissection and Discussion
super daemon, Process Startup Configuration
support, Dissection and Discussion, Samba Support
survey, Adding Domain Member Servers and Clients
SUSE, Migrating NetWare Server to Samba-3
SUSE Enterprise Linux Server, Charity Administration Office, Basic System Configuration, Implementation
SUSE Linux, Dissection and Discussion, Samba Server Implementation, PAM and NSS Client Configuration, Implementation, Active Directory Domain with Samba Domain Member Server, Implementation, Removal of Pre-Existing Conflicting RPMs
SWAT, Samba System File Location
sync always, Samba Configuration
synchronization, Kerberos Configuration, For Scalability, Use SAN-Based Storage on Samba Servers
synchronize, User Needs, LDAP Server Configuration
synchronized, Questions and Answers
syslog, OpenLDAP Server Configuration
system level logins, Questions and Answers
system security, Technical Issues

T

tattooing, Questions and Answers
TCP/IP, Questions and Answers
tdbdump, NT4/Samba Domain with Samba Domain Member Server: Using NSS and Winbind, Active Directory Domain with Samba Domain Member Server, NT4 Migration Using LDAP Backend
tdbsam, Technical Issues, Implementation, The 500-User Office, Assignment Tasks, Dissection and Discussion, Implementation, NT4/Samba Domain with Samba Domain Member Server: Using NSS and Winbind, Questions and Answers, Applicable to All Samba 2.x to Samba-3 Upgrades, Updating from Samba Versions between 3.0.6 and 3.0.10, Technical Issues, Questions and Answers
testparm, Validation, Validation, Samba-3 PDC Configuration, Active Directory Domain with Samba Domain Member Server, Samba 1.9.x and 2.x Versions Without LDAP, Samba Configuration
ticket, Samba Configuration
time server, Implementation
Tivoli Directory Server, Dissection and Discussion
TLS, LDAP Server Configuration
token, Technical Issues
tool, Questions and Answers, Dissection and Discussion
TOSHARG2, Implementation
track record, Dissection and Discussion
traffic collisions, Making Happy Users
transaction processing, Dissection and Discussion
transactional, Questions and Answers
transfer, Questions and Answers
translate, Managing Windows 200x ACLs
traverse, NT4/Samba Domain with Samba Domain Member Server: Using NSS and Winbind
tree, Dissection and Discussion
Tree Connect, Simple Windows Client Connection Characteristics
trust account, Regarding LDAP Directories and Windows Computer Accounts
trusted computing, Introduction
Trusted Domains, Technical Issues
trusted domains, Questions and Answers
trusted third-party, Kerberos Exposed
trusting, Kerberos Exposed
turn-around time, Technical Issues

U

UDP
broadcast, Routed Networks
UID, Dissection and Discussion, Regarding LDAP Directories and Windows Computer Accounts, Technical Issues, Implementation, Questions and Answers, Questions and Answers
un-join, Questions and Answers
unauthorized activities, Kerberos Exposed
UNC name, Questions and Answers
unencrypted, The LDAP Account Manager
Unicast, The Nature of Windows Networking Protocols
unicode, International Language Support
Universal Naming Convention (see UNC name)
UNIX, LDAP Server Configuration
groups, Technical Issues, Implementation
UNIX accounts, Technical Issues
UNIX/Linux server, Technical Issues
unix2dos, Samba Configuration, Configuration for Server: MASSIVE
unknown, Technical Issues
unsupported software, Commercial Support
update, Introduction, Cautions and Notes
updates, Introduction, Technical Issues
updating smbldap-tools, NT4 Migration Using LDAP Backend
upgrade, Introduction, Cautions and Notes, LDAP Server Configuration
uppercase, Implementation
user
management, Implementation, Samba Configuration, Configuration for Server: MASSIVE
user account, Making Happy Users, OpenLDAP Server Configuration
User and Group Controls, Technical Issues
user credentials, Identity Management Needs, UNIX/Linux Client Domain Member
user errors, Questions and Answers
user groups, Free Support
user identities, Implementation
user logins, Questions and Answers
user management, Implementation
User Manager, NT4 Migration Using LDAP Backend
User Mode, Implementation, Simple Windows Client Connection Characteristics, Windows 200x/XP Client Interaction with Samba-3
useradd, Implementation, Implementation, Implementation, Samba Configuration, Configuration for Server: MASSIVE, Applicable to All Samba 2.x to Samba-3 Upgrades
userdel, Applicable to All Samba 2.x to Samba-3 Upgrades
usermod, Applicable to All Samba 2.x to Samba-3 Upgrades, NT4 Migration Using LDAP Backend
username, Security Identifiers (SIDs)
username map, Implementation, Samba Configuration, Server Preparation: All Servers
UTF-8, International Language Support
utilities, Questions and Answers

W

wbinfo, Samba Domain with Samba Domain Member Server Using NSS LDAP, NT4/Samba Domain with Samba Domain Member Server: Using NSS and Winbind, Active Directory Domain with Samba Domain Member Server, Samba Configuration
weakness, Technical Issues
web
caching, Assignment Tasks
proxying, Assignment Tasks
Web
proxy, Questions and Answers
access, Key Points Learned
Web browsers, Key Points Learned
WebClient, Making Happy Users
WHATSNEW.txt, Samba-2.x with LDAP Support
white-pages, Technical Issues, LDAP Server Configuration
wide-area, User Needs, Identity Management Needs, Key Points Learned, Questions and Answers, NT4/Samba Domain with Samba Domain Member Server: Using NSS and Winbind
wide-area network, Use and Location of BDCs, Replicate Data to Conserve Peak-Demand Wide-Area Bandwidth
winbind, Implementation, Dissection and Discussion, NT4/Samba Domain with Samba Domain Member Server: Using NSS and Winbind, Questions and Answers, Introduction, Technical Issues, Technical Issues, Samba Configuration, NSS Configuration
Winbind, Questions and Answers, Technical Issues, Key Points Learned
winbind trusted domains only, Technical Issues, Questions and Answers
winbind use default domain, Checkpoint Controls
winbindd, Validation, Validation, Technical Issues, Technical Issues, Samba Domain with Samba Domain Member Server Using NSS LDAP, Questions and Answers, Samba 1.9.x and 2.x Versions Without LDAP, Updating from Samba Versions after 3.0.6 to a Current Release, Replacing a Domain Member Server, Samba Configuration, Questions and Answers, Starting Samba
winbindd_cache.tdb, Technical Issues
winbindd_idmap.tdb, Technical Issues
Windows, LDAP Server Configuration
client, Security Identifiers (SIDs)
NT, Security Identifiers (SIDs)
Windows 2000 ACLs, Managing Windows 200x ACLs
Windows 2003 Serve, Introduction
Windows 200x ACLs, Questions and Answers
Windows accounts, Technical Issues
Windows ACLs, Setting Posix ACLs in UNIX/Linux
Windows Address Book, LDAP Server Configuration
Windows ADS Domain, NT4/Samba Domain with Samba Domain Member Server: Using NSS and Winbind
Windows clients, Questions and Answers
Windows Explorer, Validation
Windows explorer, Questions and Answers
Windows security identifier (see SID)
Windows Servers, Introduction
Windows Services for UNIX (see SUS)
Windows XP, Assignment Tasks
WINS, Implementation, Technical Issues, Implementation, Windows Client Configuration, Technical Issues, Windows Client Configuration, The Nature of Windows Networking Protocols, Identity Management Needs, Questions and Answers, Questions and Answers
lookup, Questions and Answers
name resolution, Routed Networks
server, Making Happy Users, Routed Networks
WINS server, The 500-User Office, Questions and Answers
WINS serving, Implementation
wins support, Implementation
wins.dat, Identity Management Needs, Replacing a Domain Member Server
Wireshark, Requirements and Notes
wireshark, Exercises
Word, Share Point Directory and File Permissions
workgroup, Implementation, Security Identifiers (SIDs), Change of Workgroup (Domain) Name
Workgroup Announcement, Findings
workstation, Implementation
wrapper, Questions and Answers
write lock, Opportunistic Locking Controls

Y

YaST, PAM and NSS Client Configuration
Yellow Pages, Identity Management Needs
yellow pages (see NIS)
diff -u -r --new-file --exclude .svn --exclude CVS samba-3.3.10//docs/htmldocs/Samba3-ByExample/kerberos.html samba-3.3.11//docs/htmldocs/Samba3-ByExample/kerberos.html --- samba-3.3.10//docs/htmldocs/Samba3-ByExample/kerberos.html 2010-01-14 11:24:22.000000000 +0100 +++ samba-3.3.11//docs/htmldocs/Samba3-ByExample/kerberos.html 2010-02-22 16:53:36.000000000 +0100 @@ -1,10 +1,10 @@ -Chapter 11. Active Directory, Kerberos, and Security

Chapter 11. Active Directory, Kerberos, and Security

+Chapter 11. Active Directory, Kerberos, and Security

Chapter 11. Active Directory, Kerberos, and Security

By this point in the book, you have been exposed to many Samba-3 features and capabilities. More importantly, if you have implemented the examples given, you are well on your way to becoming a Samba-3 networking guru who knows a lot about Microsoft Windows. If you have taken the time to practice, you likely have thought of improvements and scenarios with which you can experiment. You are rather well plugged in to the many flexible ways Samba can be used. -

+

This is a book about Samba-3. Understandably, its intent is to present it in a positive light. The casual observer might conclude that this book is one-eyed about Samba. It is what would you expect? This chapter exposes some criticisms that have been raised concerning @@ -13,13 +13,13 @@ Some criticism always comes from deep inside ranks that one would expect to be supportive of a particular decision. Criticism can be expected from the outside. Let's see how the interesting dynamic of criticism develops with respect to Abmas. -

+

This chapter provides a shameless self-promotion of Samba-3. The objections raised were not pulled out of thin air. They were drawn from comments made by Samba users and from criticism during discussions with Windows network administrators. The tone of the objections reflects as closely as possible that of the original. The case presented is a straw-man example that is designed to permit each objection to be answered as it might occur in real life. -

Introduction

+

Introduction

Abmas is continuing its meteoric growth with yet further acquisitions. The investment community took note of the spectacular projection of Abmas onto the global business stage. Abmas is building an interesting portfolio of companies that includes accounting services, financial advice, investment @@ -28,42 +28,42 @@ interesting business growth and development plan. Abmas Video Rentals was recently acquired. During the time that the acquisition was closing, the Video Rentals business upgraded its Windows NT4-based network to Windows 2003 Server and Active Directory. -

+

You have accepted the fact that Abmas Video Rentals will use Microsoft Active Directory. The IT team, led by Stan Soroka, is committed to Samba-3 and to maintaining a uniform technology platform. Stan Soroka's team voiced its disapproval over the decision to permit this business to continue to - operate with a solution that is viewed by Christine and her group as an island of broken - technologies. This comment was made by one of Christine's staff as they were installing a new + operate with a solution that is viewed by Christine and her group as “an island of broken + technologies.” This comment was made by one of Christine's staff as they were installing a new Samba-3 server at the new business. -

+

Abmas Video Rentals' head of IT heard of this criticism. He was offended that a junior engineer should make such a comment. He felt that he had to prepare in case he might be criticized for his decision to use Active Directory. He decided he would defend his decision by hiring the services - of an outside security systems consultant to report[12] on his unit's operations + of an outside security systems consultant to report[12] on his unit's operations and to investigate the role of Samba at his site. Here are key extracts from this hypothetical report: -

+

... the implementation of Microsoft Active Directory at the Abmas Video Rentals, Bamingsham site, has been examined. We find no evidence to support a notion that vulnerabilities exist at your site. ... we took additional steps to validate the integrity of the installation and operation of Active Directory and are pleased that your staff are following sound practices.

... -

+

User and group accounts, and respective privileges, have been well thought out. File system shares are appropriately secured. Backup and disaster recovery plans are well managed and validated regularly, and effective off-site storage practices are considered to exceed industry norms. -

+

Your staff are justifiably concerned that the use of Samba may compromise their good efforts to maintain a secure network. -

+

The recently installed Linux file and application server uses a tool called winbind that is indiscriminate about security. All user accounts in Active Directory can be used to access data stored on the Linux system. We are alarmed that secure information is accessible to staff who should not even be aware that it exists. We share the concerns of your network management staff who have gone to great lengths to set fine-grained controls that limit information access to those who need access. It seems incongruous to us that Samba winbind should be permitted to be used considering that it voids this fine work. -

+

Graham Judd [head of network administration] has locked down the security of all systems and is following the latest Microsoft guidelines. ... null session connections have been disabled ... the internal network is isolated from the outside world, the [product name removed] firewall is under current contract @@ -72,7 +72,7 @@ detail and for following Microsoft recommended best practices.

... -

+

Regarding the use of Samba, we offer the following comments: Samba is in use in nearly half of all sites we have surveyed. ... It is our opinion that Samba offers no better security than Microsoft ... what worries us regarding Samba is the need to disable essential Windows security features such as @@ -80,14 +80,14 @@ mixed mode so that Samba clients and servers can authenticate all of it. Additionally, we are concerned that Samba is not at the full capabilities of Microsoft Windows NT4 server. Microsoft has moved well beyond that with trusted computing initiatives that the Samba developers do not participate in. -

+

One wonders about the integrity of an open source program that is developed by a team of hackers who cannot be held accountable for the flaws in their code. The sheer number of updates and bug fixes they have released should ring alarm bells in any business. -

+

Another factor that should be considered is that buying Microsoft products and services helps to provide employment in the IT industry. Samba and Open Source software place those jobs at risk. -

+

This is also a challenge to rise above the trouble spot. You call Stan's team together for a simple discussion, but it gets further out of hand. When you return to your office, you find the following email in your in-box: @@ -100,23 +100,23 @@ I also wish to advise that two of the recent recruits want to implement Kerberos authentication across all systems. I concur with the desire to improve security. One of the new guys who is championing the move to Kerberos was responsible for the comment that caused the embarrassment. -

+

I am experiencing difficulty in handling the sharp push for Kerberos. He claims that Kerberos, OpenLDAP, plus Samba-3 will seamlessly replace Microsoft Active Directory. I am a little out of my depth with respect to the feasibility of such a move, but have taken steps to pull both of them into line. With your consent, I would like to hire the services of a well-known Samba consultant to set the record straight. -

+

I intend to use this report to answer the criticism raised and would like to establish a policy that we will approve the use of Microsoft Windows Servers (and Active Directory) subject to all costs being covered out of the budget of the division that wishes to go its own way. I propose that dissenters will still remain responsible to meet the budgeted contribution to IT operations as a whole. I believe we should not coerce use of any centrally proposed standards, but make all noncompliance the financial responsibility of the out-of-step division. Hopefully, this will encourage all divisions to walk with us and not alone. -

 
 --Stan

Assignment Tasks

+

 
 --Stan

Assignment Tasks

You agreed with Stan's recommendations and hired a consultant to help defuse the powder keg. The consultant's task is to provide a tractable answer to each of the issues raised. The consultant must be able to support his or her claims, keep emotions to the side, and answer technically. -

Dissection and Discussion

+

Dissection and Discussion

Samba-3 is a tool. No one is pounding your door to make you use Samba. That is a choice that you are free to make or reject. It is likely that your decision to use Samba can greatly benefit your company. The Samba Team obviously believes that the Samba software is a worthy choice. @@ -124,18 +124,18 @@ someone to help manage your Samba installation, you can create income and employment. Alternately, money saved by not spending in the IT area can be spent elsewhere in the business. All money saved or spent creates employment. -

+

In the long term, the use of Samba must be economically sustainable. In some situations, Samba is adopted purely to provide file and print service interoperability on platforms that otherwise cannot provide access to data and to printers for Microsoft Windows clients. Samba is used by some businesses to effect a reduction in the cost of providing IT services. Obviously, it is also used by some as an alternative to the use of a Microsoft file and print serving platforms with no consideration of costs. -

+

It would be foolish to adopt a technology that might put any data or users at risk. Security affects everyone. The Samba-Team is fully cognizant of the responsibility they have to their users. The Samba documentation clearly reveals that full responsibility is accepted to fix anything that is broken. -

+

There is a mistaken perception in the IT industry that commercial software providers are fully accountable for the defects in products. Open Source software comes with no warranty, so it is often assumed that its use confers a higher degree of risk. Everyone should read commercial software @@ -143,49 +143,49 @@ extent of liability that is accepted. Doing so soon dispels the popular notion that commercial software vendors are willingly accountable for product defects. In many cases, the commercial vendor accepts liability only to reimburse the price paid for the software. -

+

The real issues that a consumer (like you) needs answered are What is the way of escape from technical problems, and how long will it take? The average problem turnaround time in the Open Source community is approximately 48 hours. What does the EULA offer? What is the track record in the commercial software industry? What happens when your commercial vendor decides to cease providing support? -

+

Open Source software at least puts you in possession of the source code. This means that when all else fails, you can hire a programmer to solve the problem. -

Technical Issues

+

Technical Issues

Each issue is now discussed and, where appropriate, example implementation steps are provided. -

Winbind and Security

+

Winbind and Security

Windows network administrators may be dismayed to find that winbind exposes all domain users so that they may use their domain account credentials to log on to a UNIX/Linux system. The fact that all users in the domain can see the UNIX/Linux server in their Network Neighborhood and can browse the shares on the server seems to excite them further. -

+

winbind provides for the UNIX/Linux domain member server or client, the same as one would obtain by adding a Microsoft Windows server or client to the domain. The real objection is the fact that Samba is not MS Windows and therefore requires handling a little differently from the familiar Windows systems. One must recognize fear of the unknown. -

+

Windows network administrators need to recognize that winbind does not, and cannot, override account controls set using the Active Directory management tools. The control is the same. Have no fear. -

+

Where Samba and the ADS domain account information obtained through the use of winbind permits access, by browsing or by the drive mapping to a share, to data that should be better protected. This can only happen when security controls have not been properly implemented. Samba permits access controls to be set on: -

  • Shares themselves (i.e., the logical share itself)

  • The share definition in smb.conf

  • The shared directories and files using UNIX permissions

  • Using Windows 2000 ACLs if the file system is POSIX enabled

+

  • Shares themselves (i.e., the logical share itself)

  • The share definition in smb.conf

  • The shared directories and files using UNIX permissions

  • Using Windows 2000 ACLs if the file system is POSIX enabled

Examples of each are given in “Implementation”. -

User and Group Controls

+

User and Group Controls

User and group management facilities as known in the Windows ADS environment may be used to provide equivalent access control constraints or to provide equivalent permissions and privileges on Samba servers. Samba offers greater flexibility in the use of user and group controls because it has additional layers of control compared to Windows 200x/XP. For example, access controls on a Samba server may be set within the share definition in a manner for which Windows has no equivalent. -

+

In any serious analysis of system security, it is important to examine the safeguards that remain when all other protective measures fail. An administrator may inadvertently set excessive permissions on the file system of a shared resource, or he may set excessive @@ -193,35 +193,35 @@ the data would indeed be laid bare to abuse. Yet, within a Samba share definition, it is possible to guard against that by enforcing controls on the share definition itself. You see a practical example of this a little later in this chapter. -

+

The report that is critical of Samba really ought to have exercised greater due diligence: the real weakness is on the side of a Microsoft Windows environment. -

Security Overall

+

Security Overall

Samba is designed in such a manner that weaknesses inherent in the design of Microsoft Windows networking ought not to expose the underlying UNIX/Linux file system in any way. All software has potential defects, and Samba is no exception. What matters more is how defects that are discovered get dealt with. -

+

The Samba Team totally agrees with the necessity to observe and fully implement every security facility to provide a level of protection and security that is necessary and that the end user (or network administrator) needs. Never would the Samba Team recommend a compromise to system security, nor would deliberate defoliation of security be publicly condoned; yet this is the practice by many Windows network administrators just to make happy users who have no notion of consequential risk. -

+

The report condemns Samba for releasing updates and security fixes, yet Microsoft online updates need to be applied almost weekly. The answer to the criticism lies in the fact that Samba development is continuing, documentation is improving, user needs are being increasingly met or exceeded, and security updates are issued with a short turnaround time. -

+

The release of Samba-4 is expected around late 2004 to early 2005 and involves a near complete rewrite to permit extensive modularization and to prepare Samba for new functionality planned for addition during the next-generation series. The Samba Team is responsible and can be depended upon; the history to date suggests a high degree of dependability and on charter development consistent with published roadmap projections. -

+

Not well published is the fact that Microsoft was a foundation member of the Common Internet File System (CIFS) initiative, together with the participation of the network attached storage (NAS) industry. Unfortunately, for the past few years, @@ -230,7 +230,7 @@ space. The Samba Team has maintained consistent presence and leadership at all CIFS conferences and at the interoperability laboratories run concurrently with them. -

Cryptographic Controls (schannel, sign'n'seal)

+

Cryptographic Controls (schannel, sign'n'seal)

The report correctly mentions that Samba did not support the most recent schannel and digital sign'n'seal features of Microsoft Windows NT/200x/XPPro products. This is one of the key features @@ -238,7 +238,7 @@ seldom a reflection of current practice, and in many respects reports are like a pathology report they reflect accurately (at best) status at a snapshot in time. Meanwhile, the world moves on. -

+

It should be pointed out that had clear public specifications for the protocols been published, it would have been much easier to implement these features and would have taken less time to do. The sole mechanism used to find an algorithm that is compatible @@ -246,7 +246,7 @@ and trial-and-error implementation of potential techniques. The real value of public and defensible standards is obvious to all and would have enabled more secure networking for everyone. -

+

Critics of Samba often ignore fundamental problems that may plague (or may have plagued) the users of Microsoft's products also. Those who are first to criticize Samba for not rushing into release of digital sign'n'seal support @@ -258,7 +258,7 @@ implementation of sign'n'seal. They provide a work-around that is not trivial for many Windows networking sites. From notes such as this it is clear that there are benefits from not rushing new technology out of the door too soon. -

+

One final comment is warranted. If companies want more secure networking protocols, the most effective method by which this can be achieved is by users seeking and working together to help define open and publicly refereed standards. The @@ -274,7 +274,7 @@ of them that uses RPCs that are not supported by any of these component technologies and yet by which they are made to interoperate in ways that the components do not support. -

+

In order to make the popular request for Samba to be an Active Directory Server a reality, it is necessary to add to OpenLDAP, Kerberos, as well as Samba, RPC calls that are not presently supported. The Samba Team has not been able to gain critical @@ -282,34 +282,34 @@ challenge of developing and integrating the necessary technologies. Therefore, if the Samba Team does not make it a priority to absorb Kerberos and LDAP functionality into the Samba project, this dream request cannot become a reality. -

+

At this time, the integration of LDAP, Kerberos, and the missing RPCs is not on the Samba development roadmap. If it is not on the published roadmap, it cannot be delivered anytime soon. Ergo, ADS server support is not a current goal for Samba development. The Samba Team is most committed to permitting Samba to be a full ADS domain member that is increasingly capable of being managed using Microsoft Windows MMC tools. -

Kerberos Exposed

+

Kerberos Exposed

Kerberos is a network authentication protocol that provides secure authentication for client-server applications by using secret-key cryptography. Firewalls are an insufficient barrier mechanism in today's networking world; at best they only restrict incoming network traffic but cannot prevent network traffic that comes from authorized locations from performing unauthorized activities. -

+

Kerberos was created by MIT as a solution to network security problems. The Kerberos protocol uses strong cryptography so that a client can prove its identity to a server (and vice versa) across an insecure network connection. After a client and server has used Kerberos to prove their identity, they can also encrypt all of their communications to assure privacy and data integrity as they go about their business. -

+

Kerberos is a trusted third-party service. That means that there is a third party (the kerberos server) that is trusted by all the entities on the network (users and services, usually called principals). All principals share a secret password (or key) with the kerberos server and this enables principals to verify that the messages from the kerberos server are authentic. Therefore, trusting the kerberos server, users and services can authenticate each other.

- - - + + + Kerberos was, until recently, a technology that was restricted from being exported from the United States. For many years that hindered global adoption of more secure networking technologies both within the United States and abroad. A free and unencumbered implementation of MIT Kerberos has been produced in Europe @@ -319,11 +319,11 @@ significant surge forward in the development of Kerberos-enabled applications and in the general deployment and use of Kerberos across the spectrum of the information technology industry.

- + A storm has broken out concerning interoperability between MIT Kerberos and Microsofts' implementation of it. For example, a 2002 IDG - report[13] by + report[13] by states:

A Microsoft Corp. executive testified at the software giant's remedy hearing that the company goes to @@ -331,7 +331,7 @@ with Windows. But a lawyer with the states suing Microsoft pointed out that when it comes to the company's use of the Kerberos authentication specification, not everyone agrees.

- + Robert Short, vice president of Windows core technology at Microsoft, wrote in his direct testimony prepared before his appearance that non-Microsoft operating systems can disregard the portion of the Kerberos version 5 specification that Windows clients use for proprietary purposes and still achieve interoperability with @@ -339,8 +339,8 @@ Windows-specific authorization data, Short wrote. The designers of Kerberos left these fields undefined so that software developers could add their own authorization information, he said.

- - + + It so happens that Microsoft Windows clients depend on and expect the contents of the unspecified fields in the Kerberos 5 communications data stream for their Windows interoperability, particularly when Samba is expected to emulate a Windows Server 200x domain controller. But the interoperability @@ -352,7 +352,7 @@ Microsoft makes the following comment in a reference in a technet article: -

+

The DCE Security Services are also layered on the Kerberos protocol. DCE authentication services use RPC representation of Kerberos protocol messages. In addition, DCE uses the authorization data field in Kerberos tickets to convey Privilege Attribute Certificates (PACs) that define user identity and group membership. @@ -360,52 +360,52 @@ Windows NT services will not be able to translate DCE PACs into Windows NT user and group identifiers. This is not an issue with Kerberos interoperability, but rather an issue of interoperability between DCE and Windows NT access control information. -

Implementation

+

Implementation

The following procedures outline the implementation of the security measures discussed so far. -

Share Access Controls

+

Share Access Controls

Access control entries placed on the share itself act as a filter at the time a when CIFS/SMB client (such as Windows XP Pro) attempts to make a connection to the Samba server. -

Procedure 11.1. Create/Edit/Delete Share ACLs

  1. +

    Procedure 11.1. Create/Edit/Delete Share ACLs

    1. From a Windows 200x/XP Professional workstation, log on to the domain using the Domain Administrator account (on Samba domains, this is usually the account called root). -

    2. +

    3. Click StartSettingsControl PanelAdministrative ToolsComputer Management. -

    4. +

    5. In the left panel, [Right mouse menu item] Computer Management (Local)Connect to another computer ...Browse...AdvancedFind Now. In the lower panel, click on the name of the server you wish to - administer. Click OKOKOK. + administer. Click OKOKOK. In the left panel, the entry Computer Management (Local) should now reflect the change made. For example, if the server you are administering is called FRODO, the Computer Management entry should now say Computer Management (FRODO). -

    6. +

    7. In the left panel, click Computer Management (FRODO)[+] Shared FoldersShares. -

    8. +

    9. In the right panel, double-click on the share on which you wish to set/edit ACLs. This will bring up the Properties panel. Click the Share Permissions tab. -

    10. +

    11. You may now edit/add/remove access control settings. Be very careful. Many problems have been created by people who decided that everyone should be rejected but one particular group should have full control. This is a catch-22 situation because members of that particular group also belong to the group Everyone, which therefore overrules any permissions set for the permitted group. -

    12. +

    13. When you are done with editing, close all panels by clicking through the OK buttons. -

Share Definition Controls

+

Share Definition Controls

Share-definition-based access controls can be used like a checkpoint or like a pile-driver. Just as a checkpoint can be used to require someone who wants to get through to meet certain requirements, so it is possible to require the user (or group the user belongs to) to meet specified credential-related objectives. It can be likened to a pile-driver by overriding default controls in that having met the credential-related objectives, the user can be granted powers and privileges that would not normally be available under default settings. -

+

It must be emphasized that the controls discussed here can act as a filter or give rights of passage that act as a superstructure over normal directory and file access controls. However, share-level ACLs act at a higher level than do share definition controls because the user must filter through the share-level controls to get to the share-definition controls. The proper hierarchy of controls implemented by Samba and Windows networking consists of: -

  1. Share-level ACLs

  2. Share-definition controls

  3. Directory and file permissions

  4. Directory and file POSIX ACLs

Checkpoint Controls

+

  1. Share-level ACLs

  2. Share-definition controls

  3. Directory and file permissions

  4. Directory and file POSIX ACLs

Checkpoint Controls

Consider the following extract from a smb.conf file defining the share called Apps:

 [Apps]
@@ -416,19 +416,19 @@
 

This definition permits only those who are members of the group called Employees to access the share. -

Note

+

Note

On domain member servers and clients, even when the winbind use default domain has been specified, the use of domain accounts in security controls requires fully qualified domain specification, for example, valid users = @"MEGANET\Northern Engineers". Note the necessity to use the double quotes to avoid having the space in the Windows group name interpreted as a delimiter. -

+

If there is an ACL on the share itself to permit read/write access for all Employees as well as read/write for the group Doctors, both groups are permitted through to the share. However, at the moment an attempt is made to set up a connection to the share, a member of the group Doctors, who is not also a member of the group Employees, would immediately fail to validate. -

+

Consider another example. In this case, you want to permit all members of the group Employees except the user patrickj to access the Apps share. This can be easily achieved by setting a share-level ACL permitting only Employees to access the share, @@ -441,7 +441,7 @@ read only = Yes invalid users = patrickj

- + Let us assume that you want to permit the user gbshaw to manage any file in the UNIX/Linux file system directory /data/apps, but you do not want to grant any write permissions beyond that directory tree. Here is one way this can be done: @@ -453,7 +453,7 @@ invalid users = patrickj admin users = gbshaw

- + Now we have a set of controls that permits only Employees who are also members of the group Doctors, excluding the user patrickj, to have read-only privilege, but the user gbshaw is granted administrative rights. @@ -475,11 +475,11 @@ admin users = gbshaw write list = peters

- + This is a particularly complex example at this point, but it begins to demonstrate the possibilities. You should refer to the online manual page for the smb.conf file for more information regarding the checkpoint controls that Samba implements. -

Override Controls

+

Override Controls

Override controls implemented by Samba permit actions like the adoption of a different identity during file system operations, the forced overwriting of normal file and directory permissions, and so on. You should refer to the online manual page for the smb.conf file for more information regarding @@ -497,14 +497,14 @@ force user = billc force group = Mentors

- + That is all there is to it. Well, it is almost that simple. The downside of this method is that users are logged onto the Windows client as themselves, and then immediately before accessing the file, Samba makes system calls to change the effective user and group to the forced settings specified, completes the file transaction, and then reverts to the actually logged-on identity. This imposes significant overhead on Samba. The alternative way to effectively achieve the same result (but with lower system CPU overheads) is described next. -

+

The use of the force user or the force group may also have a severe impact on system (particularly on Windows client) performance. If opportunistic locking is enabled on the share (the default), it causes an oplock break to be @@ -514,7 +514,7 @@ waiting for the file system transaction (read or write) to complete. The result can be a profound apparent performance degradation as the client continually attempts to reconnect to overcome the effect of the lost oplock break, or time-out. -

Share Point Directory and File Permissions

+

Share Point Directory and File Permissions

Samba has been designed and implemented so that it respects as far as is feasible the security and user privilege controls that are built into the UNIX/Linux operating system. Samba does nothing with respect to file system access that violates file system permission settings, unless it is @@ -522,29 +522,29 @@ UNIX file system controls, this chapter does not document simple information that can be obtained from a basic UNIX training guide. Instead, one common example of a typical problem is used to demonstrate the most effective solution referred to in the immediately preceding paragraph. -

+

One of the common issues that repeatedly pops up on the Samba mailing lists involves the saving of Microsoft Office files (Word and Excel) to a network drive. Here is the typical sequence: -

  1. +

    1. A user opens a Word document from a network drive. The file was owned by user janetp and [users], and was set read/write-enabled for everyone. A user opens a Word document from a network drive. The file was owned by user janetp and users, and was set read/write-enabled for everyone. -

    2. +

    3. File changes and edits are made. -

    4. +

    5. The file is saved, and MS Word is closed. -

    6. +

    7. The file is now owned by the user billc and group doctors, and is set read/write by billc, read-only by doctors, and no access by everyone. -

    8. - The original owner cannot now access her own file and is justifiably upset. +

    9. + The original owner cannot now access her own file and is “justifiably” upset.

    There have been many postings over the years that report the same basic problem. Frequently Samba users - want to know when this bug will be fixed. The fact is, this is not a bug in Samba at all. + want to know when this “bug” will be fixed. The fact is, this is not a bug in Samba at all. Here is the real sequence of what happens in this case. -

    +

    When the user saves a file, MS Word creates a new (temporary) file. This file is naturally owned by the user who creates the file (billc) and has the permissions that follow that user's default settings within the operating system (UNIX/Linux). When MS Word has finished writing @@ -557,12 +557,12 @@ perhaps have the same ownership and permissions as the old file. To Samba, these are entirely independent operations.

    - The question is, How can we solve the problem? + The question is, “How can we solve the problem?

    The solution is simple. Use UNIX file system permissions and controls to your advantage. Follow these simple steps to create a share in which all files will consistently be owned by the same user and the same group: -

    Procedure 11.2. Using Directory Permissions to Force File User and Group Ownership

    1. +

      Procedure 11.2. Using Directory Permissions to Force File User and Group Ownership

      1. Change your share definition so that it matches this pattern:

         [finance]
        @@ -570,18 +570,18 @@
                 browseable = Yes
                 read only = No
         

        -

      2. +

      3. Set consistent user and group permissions recursively down the directory tree as shown here:

         root#  chown -R janetp.users /usr/data/finance
         

        -

      4. +

      5. Set the files and directory permissions to be read/write for owner and group, and not accessible to others (everyone), using the following command:

         root#  chmod ug+rwx,o-rwx /usr/data/finance
         

        -

      6. +

      7. Set the SGID (supergroup) bit on all directories from the top down. This means all files can be created with the permissions of the group set on the directory. It means all users who are members of the group finance can read and write all files in @@ -591,11 +591,11 @@ root# find /usr/data/finance -type d -exec chmod ug+s {}\;

        -

      8. +

      9. Make sure all users that must have read/write access to the directory have finance group membership as their primary group, for example, the group they belong to in /etc/passwd. -

    Managing Windows 200x ACLs

    +

Managing Windows 200x ACLs

Samba must translate Windows 2000 ACLs to UNIX POSIX ACLs. This has some interesting side effects because there is not a one-to-one equivalence between them. The as-close-as-possible ACLs match means that some transactions are not possible from MS Windows clients. One of these is to reset the ownership @@ -603,62 +603,62 @@

There are two possible ways to set ACLs on UNIX/Linux file systems from a Windows network workstation, either via File Manager or via the Microsoft Management Console (MMC) Computer Management interface. -

Using the MMC Computer Management Interface

  1. +

    Using the MMC Computer Management Interface

    1. From a Windows 200x/XP Professional workstation, log on to the domain using the Domain Administrator account (on Samba domains, this is usually the account called root). -

    2. +

    3. Click StartSettingsControl PanelAdministrative ToolsComputer Management. -

    4. +

    5. In the left panel, [Right mouse menu item] Computer Management (Local)Connect to another computer ...Browse...AdvancedFind Now. In the lower panel, click on the name of the server you wish to administer. Click OKOKOK. In the left panel, the entry Computer Management (Local) should now reflect the change made. For example, if the server you are administering is called FRODO, the Computer Management entry should now say: Computer Management (FRODO). -

    6. +

    7. In the left panel, click Computer Management (FRODO)[+] Shared FoldersShares. -

    8. +

    9. In the right panel, double-click on the share on which you wish to set/edit ACLs. This brings up the Properties panel. Click the Security tab. It is best to edit ACLs using the Advanced editing features. Click the Advanced button. This opens a panel that has four tabs. Only the functionality under the Permissions tab can be utilized with respect to a Samba domain server. -

    10. +

    11. You may now edit/add/remove access control settings. Be very careful. Many problems have been created by people who decided that everyone should be rejected but one particular group should have full control. This is a catch-22 situation because members of that particular group also belong to the group Everyone, which therefore overrules any permissions set for the permitted group. -

    12. +

    13. When you are done with editing, close all panels by clicking through the OK buttons until the last panel closes. -

    Using MS Windows Explorer (File Manager)

    +

Using MS Windows Explorer (File Manager)

The following alternative method may be used from a Windows workstation. In this example we work with a domain called MEGANET, a server called MASSIVE, and a share called Apps. The underlying UNIX/Linux share point for this share is /data/apps. -

  1. +

    1. Click Start[right-click] My ComputerExplore[left panel] [+] My Network Places[+] Entire Network[+] Microsoft Windows Network[+] Meganet[+] Massive[right-click] AppsPropertiesSecurityAdvanced. This opens a panel that has four tabs. Only the functionality under the Permissions tab can be utilized for a Samba domain server. -

    2. +

    3. You may now edit/add/remove access control settings. Be very careful. Many problems have been created by people who decided that everyone should be rejected but one particular group should have full control. This is a catch-22 situation because members of that particular group also belong to the group Everyone, which therefore overrules any permissions set for the permitted group. -

    4. +

    5. When you are done with editing, close all panels by clicking through the OK buttons until the last panel closes. -

Setting Posix ACLs in UNIX/Linux

+

Setting Posix ACLs in UNIX/Linux

Yet another alternative method for setting desired security settings on the shared resource files and directories can be achieved by logging into UNIX/Linux and setting POSIX ACLs directly using command-line tools. Here is an example session on the same resource as in the immediately preceding example on a SUSE 9 Linux system: -

  1. +

    1. Log into the Linux system as the user root. -

    2. +

    3. Change directory to the location of the exported (shared) Windows file share (Apps), which is in the directory /data. Execute the following:

      @@ -674,7 +674,7 @@
       group::rwx
       other::r-x
       

      -

    4. +

    5. You want to add permission for AppsMgrs to enable them to manage the applications (apps) share. It is important to set the ACL recursively so that the AppsMgrs have this capability throughout the directory tree that is @@ -697,111 +697,111 @@ other::r-x

      This confirms that the change of POSIX ACL permissions has been effective. -

    6. +

    7. It is highly recommended that you read the online manual page for the setfacl and getfacl commands. This provides information regarding how to set/read the default ACLs and how that may be propagated through the directory tree. In Windows ACLs terms, this is the equivalent of setting inheritance properties. -

Key Points Learned

+

Key Points Learned

The mish-mash of issues were thrown together into one chapter because it seemed like a good idea. Looking back, this chapter could be broken into two, but it's too late now. It has been done. The highlights covered are as follows: -

  • +

    • Winbind honors and does not override account controls set in Active Directory. This means that password change, logon hours, and so on, are (or soon will be) enforced by Samba winbind. At this time, an out-of-hours login is denied and password change is enforced. At this time, if logon hours expire, the user is not forcibly logged off. That may be implemented at some later date. -

    • +

    • Sign'n'seal (plus schannel support) has been implemented in Samba-3. Beware of potential problems acknowledged by Microsoft as having been fixed but reported by some as still possibly an open issue. -

    • +

    • The combination of Kerberos 5, plus OpenLDAP, plus Samba, cannot replace Microsoft Active Directory. The possibility to do this is not planned in the current Samba-3 roadmap. Samba-3 does aim to provide further improvements in interoperability so that UNIX/Linux systems may be fully integrated into Active Directory domains. -

    • +

    • This chapter reviewed mechanisms by which Samba servers may be kept secure. Each of the four key methodologies was reviewed with specific reference to example deployment techniques. -

Questions and Answers

-

Questions and Answers

+

Does Samba-3 require the Sign'n'seal registry hacks needed by Samba-2? -
+
Does Samba-3 support Active Directory? -
+
When Samba-3 is used with Active Directory, is it necessary to run mixed-mode operation, as was necessary with Samba-2? -
+
Is it safe to set share-level access controls in Samba? -
+
Is it mandatory to set share ACLs to get a secure Samba-3 server? -
+
The valid users did not work on the [homes]. Has this functionality been restored yet? -
+
Is the bias against use of the force user and force group really warranted? -
+
The example given for file and directory access control forces all files to be owned by one particular user. I do not like that. Is there any way I can see who created the file? -
+
In the book, “The Official Samba-3 HOWTO and Reference Guide”, you recommended use of the Windows NT4 Server Manager (part of the SRVTOOLS.EXE) utility. Why have you mentioned only the use of the Windows 200x/XP MMC Computer Management utility? -
+
I tried to set valid users = @Engineers, but it does not work. My Samba server is an Active Directory domain member server. Has this been fixed now? -

+

Does Samba-3 require the Sign'n'seal registry hacks needed by Samba-2? -

+

No. Samba-3 fully supports Sign'n'seal as well as schannel operation. The registry change should not be applied when Samba-3 is used as a domain controller. -

+

Does Samba-3 support Active Directory? -

+

Yes. Samba-3 can be a fully participating native mode Active Directory client. Samba-3 does not provide Active Directory services. It cannot be used to replace a Microsoft Active Directory server implementation. Samba-3 can function as an Active Directory client (workstation) toolkit, and it can function as an Active Directory domain member server. -

+

When Samba-3 is used with Active Directory, is it necessary to run mixed-mode operation, as was necessary with Samba-2? -

+

No. Samba-3 can be used with NetBIOS over TCP/IP disabled, just as can be done with Windows 200x Server and 200x/XPPro client products. It is no longer necessary to run mixed-mode operation, because Samba-3 can join a native Windows 2003 Server ADS domain. -

+

Is it safe to set share-level access controls in Samba?

Yes. Share-level access controls have been supported since early versions of Samba-2. This is very mature technology. Not enough sites make use of this powerful capability, neither on Windows server or with Samba servers. -

+

Is it mandatory to set share ACLs to get a secure Samba-3 server? -

+

No. Samba-3 honors UNIX/Linux file system security, supports Windows 200x ACLs, and provides means of securing shares through share definition controls in the smb.conf file. The additional support for share-level ACLs is like frosting on the cake. It adds to security but is not essential to it. -

+

The valid users did not work on the [homes]. Has this functionality been restored yet? -

+

Yes. This was fixed in Samba-3.0.2. The use of this parameter is strongly recommended as a safeguard on the [homes] meta-service. The correct way to specify this is: valid users = %S. -

+

Is the bias against use of the force user and force group really warranted? -

+

There is no bias. There is a determination to recommend the right tool for the task at hand. After all, it is better than putting users through performance problems, isn't it? -

+

The example given for file and directory access control forces all files to be owned by one particular user. I do not like that. Is there any way I can see who created the file? -

+

Sure. You do not have to set the SUID bit on the directory. Simply execute the following command to permit file ownership to be retained by the user who created it:

@@ -809,20 +809,20 @@
 

Note that this required no more than removing the u argument so that the SUID bit is not set for the owner. -

- In the book, The Official Samba-3 HOWTO and Reference Guide, you recommended use +

+ In the book, “The Official Samba-3 HOWTO and Reference Guide”, you recommended use of the Windows NT4 Server Manager (part of the SRVTOOLS.EXE) utility. Why have you mentioned only the use of the Windows 200x/XP MMC Computer Management utility? -

+

Either tool can be used with equal effect. There is no benefit of one over the other, except that the MMC utility is present on all Windows 200x/XP systems and does not require additional software to be downloaded and installed. Note that if you want to manage user and group accounts in your Samba-controlled domain, the only tool that permits that is the NT4 Domain User Manager, which is provided as part of the SRVTOOLS.EXE utility. -

+

I tried to set valid users = @Engineers, but it does not work. My Samba server is an Active Directory domain member server. Has this been fixed now?

The use of this parameter has always required the full specification of the domain account, for example, valid users = @"MEGANET2\Domain Admins". -



[13] ITWorld.com
+



[13] ITWorld.com
diff -u -r --new-file --exclude .svn --exclude CVS samba-3.3.10//docs/htmldocs/Samba3-ByExample/ntmigration.html samba-3.3.11//docs/htmldocs/Samba3-ByExample/ntmigration.html --- samba-3.3.10//docs/htmldocs/Samba3-ByExample/ntmigration.html 2010-01-14 11:24:18.000000000 +0100 +++ samba-3.3.11//docs/htmldocs/Samba3-ByExample/ntmigration.html 2010-02-22 16:53:36.000000000 +0100 @@ -1,4 +1,4 @@ -Chapter 9. Migrating NT4 Domain to Samba-3

Chapter 9. Migrating NT4 Domain to Samba-3

+Chapter 9. Migrating NT4 Domain to Samba-3

Chapter 9. Migrating NT4 Domain to Samba-3

Ever since Microsoft announced that it was discontinuing support for Windows NT4, Samba users started to ask for detailed instructions on how to migrate from NT4 to Samba-3. This chapter provides background information that should @@ -6,23 +6,23 @@

One wonders how many NT4 systems will be left in service by the time you read this book though. -

Introduction

+

Introduction

Network administrators who want to migrate off a Windows NT4 environment know one thing with certainty. They feel that NT4 has been abandoned, and they want to update. The desire to get off NT4 and to not adopt Windows 200x and Active Directory is driven by a mixture of concerns over complexity, cost, fear of failure, and much more.

- - - - + + + + The migration from NT4 to Samba-3 can involve a number of factors, including migration of data to another server, migration of network environment controls such as group policies, and migration of the users, groups, and machine accounts.

- + It should be pointed out now that it is possible to migrate some systems from a Windows NT4 domain environment to a Samba-3 domain environment. This is certainly not possible in every case. It is possible to just migrate the domain accounts @@ -30,10 +30,10 @@ the exception than the rule. Most systems require some tweaking after migration before an environment that is acceptable for immediate use is obtained. -

Assignment Tasks

- - - +

Assignment Tasks

+ + + You are about to migrate an MS Windows NT4 domain accounts database to a Samba-3 server. The Samba-3 server is using a passdb backend based on LDAP. The @@ -42,27 +42,27 @@

Your objective is to document the process of migrating user and group accounts from several NT4 domains into a single Samba-3 LDAP backend database. -

Dissection and Discussion

- - - - - - +

Dissection and Discussion

+ + + + + + The migration process takes a snapshot of information that is stored in the Windows NT4 registry-based accounts database. That information resides in the Security Account Manager (SAM) portion of the NT4 registry under keys called SAM and SECURITY. -

Warning

- - +

Warning

+ + The Windows NT4 registry keys called SAM and SECURITY are protected so that you cannot view the contents. If you change the security setting to reveal the contents under these hive keys, your Windows NT4 domain is crippled. Do not do this unless you are willing to render your domain controller inoperative.

- - + + Before commencing an NT4 to Samba-3 migration, you should consider what your objectives are. While in some cases it is possible simply to migrate an NT4 domain to a single Samba-3 server, that may not be a good idea from an administration perspective. Since the process involves going @@ -70,9 +70,9 @@ review the structure of the network, how Windows clients are controlled and how they interact with the network environment.

- - - + + + MS Windows NT4 was introduced some time around 1996. Many environments in which NT4 was deployed have done little to keep the NT4 server environment up to date with more recent Windows releases, particularly Windows XP Professional. The migration provides opportunity to revise and update @@ -83,9 +83,9 @@ as a good time to update desktop systems also. In all, the extra effort should constitute no real disruption to users, but rather, with due diligence and care, should make their network experience a much happier one. -

Technical Issues

- - +

Technical Issues

+ + Migration of an NT4 domain user and group database to Samba-3 involves a certain strategic element. Many sites have asked for instructions regarding merging of multiple NT4 domains into one Samba-3 LDAP database. It seems that this is viewed as a significant @@ -93,35 +93,35 @@ Directory. The diagram in “Schematic Explaining the net rpc vampire Process” illustrates the effect of migration from a Windows NT4 domain to a Samba domain.

Figure 9.1. Schematic Explaining the net rpc vampire Process

Schematic Explaining the net rpc vampire Process

- - + + If you want to merge multiple NT4 domain account databases into one Samba domain, you must now dump the contents of the first migration and edit it as appropriate. Now clean out (remove) the tdbsam backend file (passdb.tdb) or the LDAP database files. You must start each migration with a new database into which you merge your NT4 domains. -

+

At this point, you are ready to perform the second migration, following the same steps as for the first. In other words, dump the database, edit it, and then you may merge the dump for the first and second migrations. -

+

You must be careful. If you choose to migrate to an LDAP backend, your dump file now contains the full account information, including the domain SID. The domain SID for each of the two NT4 domains will be different. You must choose one and change the domain portion of the account SIDs so that all are the same.

- - - - - - - - - - - - + + + + + + + + + + + + If you choose to use a tdbsam (passdb.tdb) backend file, your best choice is to use pdbedit to export the contents of the tdbsam file into an smbpasswd data file. This automatically strips out all domain-specific information, @@ -131,7 +131,7 @@ file must have an account in /etc/passwd. The resulting smbpasswd file may be exported or imported into either a tdbsam (passdb.tdb) or an LDAP backend. -

Figure 9.2. View of Accounts in NT4 Domain User Manager

View of Accounts in NT4 Domain User Manager

Political Issues

+

Figure 9.2. View of Accounts in NT4 Domain User Manager

View of Accounts in NT4 Domain User Manager

Political Issues

The merging of multiple Windows NT4-style domains into a single LDAP-backend-based Samba-3 domain may be seen by those who had power over them as a loss of prestige or a loss of power. The imposition of a single domain may even be seen as a threat. So in migrating and @@ -141,7 +141,7 @@ The best advice that can be given to those who set out to merge NT4 domains into a single Samba-3 domain is to promote (sell) the action as one that reduces costs and delivers greater network interoperability and manageability. -

Implementation

+

Implementation

From feedback on the Samba mailing lists, it seems that most Windows NT4 migrations to Samba-3 are being performed using a new server or a new installation of a Linux or UNIX server. If you contemplate doing this, please note that the steps that follow in this @@ -160,28 +160,28 @@ (machine names, computer names, domain names, workgroup names ALL names!).

The migration process involves the following steps: -

  • +

    • Prepare the target Samba-3 server. This involves configuring Samba-3 for migration to either a tdbsam or an ldapsam backend. -

    • - - - +

    • + + + Clean up the source NT4 PDC. Delete all accounts that need not be migrated. Delete all files that should not be migrated. Where possible, change NT group names so there are no spaces or uppercase characters. This is important if the target UNIX host insists on POSIX-compliant all lowercase user and group names. -

    • +

    • Step through the migration process. -

    • +

    • Remove the NT4 PDC from the network. -

    • +

    • Upgrade the Samba-3 server from a BDC to a PDC, and validate all account information.

    It may help to use the above outline as a pre-migration checklist. -

    NT4 Migration Using LDAP Backend

    +

    NT4 Migration Using LDAP Backend

    In this example, the migration is of an NT4 PDC to a Samba-3 PDC with an LDAP backend. The accounts about to be migrated are shown in “View of Accounts in NT4 Domain User Manager”. In this example use is made of the smbldap-tools scripts to add the accounts that are migrated into the ldapsam passdb backend. @@ -194,28 +194,28 @@ that should be passed to them before attempting to perform the account migration. Note also that the deletion scripts must be commented out during migration. These should be uncommented following successful migration of the NT4 Domain accounts. -

    Warning

    +

    Warning

    Under absolutely no circumstances should the Samba daemons be started until instructed to do so. Delete the /etc/samba/secrets.tdb file and all Samba control tdb files before commencing the following configuration steps. -

    Table 9.1. Samba smb.conf Scripts Essential to Samba Operation

    Entityldapsam Scripttdbsam Script
    Add User Accountssmbldap-useradduseradd
    Delete User Accountssmbldap-userdeluserdel
    Add Group Accountssmbldap-groupaddgroupadd
    Delete Group Accountssmbldap-groupdelgroupdel
    Add User to Groupsmbldap-groupmodusermod (See Note)
    Add Machine Accountssmbldap-useradduseradd

    Note

    - - - +

    Table 9.1. Samba smb.conf Scripts Essential to Samba Operation

    Entityldapsam Scripttdbsam Script
    Add User Accountssmbldap-useradduseradd
    Delete User Accountssmbldap-userdeluserdel
    Add Group Accountssmbldap-groupaddgroupadd
    Delete Group Accountssmbldap-groupdelgroupdel
    Add User to Groupsmbldap-groupmodusermod (See Note)
    Add Machine Accountssmbldap-useradduseradd

    Note

    + + + The UNIX/Linux usermod utility does not permit simple user addition to (or deletion of users from) groups. This is a feature provided by the smbldap-tools scripts. If you want this capability, you must create your own tool to do this. Alternately, you can search the Web to locate a utility called groupmem (by George Kraft) that provides this functionality. The groupmem utility was contributed to the shadow package but has not surfaced in the formal commands provided by Linux distributions (March 2004). -

    Note

    - +

    Note

    + The tdbdump utility is a utility that you can build from the Samba source-code tree. Not all Linux binary distributions include this tool. If it is missing from your Linux distribution, you will need to build this yourself or else forgo its use.

    - + Before starting the migration, all dead accounts were removed from the NT4 domain using the User Manager for Domains. -

    Procedure 9.1. User Migration Steps

    Example 9.1. NT4 Migration Samba-3 Server smb.conf Part: A

    [global]
    workgroup = DAMNATION
    netbios name = MERLIN
    passdb backend = ldapsam:ldap://localhost
    log level = 1
    syslog = 0
    log file = /var/log/samba/%m
    max log size = 0
    smb ports = 139 445
    name resolve order = wins bcast hosts
    add user script = /opt/IDEALX/sbin/smbldap-useradd -m '%u'
    #delete user script = /opt/IDEALX/sbin/smbldap-userdel '%u'
    add group script = /opt/IDEALX/sbin/smbldap-groupadd '%g'
    #delete group script = /opt/IDEALX/sbin/smbldap-groupdel '%g'
    add user to group script = /opt/IDEALX/sbin/ smbldap-groupmod -m '%u' '%g'
    #delete user from group script = /opt/IDEALX/sbin/smbldap-groupmod -x '%u' '%g'
    set primary group script = /opt/IDEALX/sbin/smbldap-usermod -g '%g' '%u'
    add machine script = /opt/IDEALX/sbin/smbldap-useradd -w '%u'
    logon script = scripts\logon.cmd
    logon path = \\%L\profiles\%U
    logon home = \\%L\%U
    logon drive = X:
    domain logons = Yes
    domain master = No
    #wins support = Yes
    wins server = 192.168.123.124
    ldap admin dn = cn=Manager,dc=terpstra-world,dc=org
    ldap group suffix = ou=Groups
    ldap idmap suffix = ou=Idmap
    ldap machine suffix = ou=People
    ldap passwd sync = Yes
    ldap suffix = dc=terpstra-world,dc=org
    ldap ssl = no
    ldap timeout = 20
    ldap user suffix = ou=People
    idmap backend = ldap:ldap://localhost
    idmap uid = 15000-20000
    idmap gid = 15000-20000
    winbind nested groups = Yes
    ea support = Yes
    map acl inherit = Yes

    Example 9.2. NT4 Migration Samba-3 Server smb.conf Part: B

    [apps]
    comment = Application Data
    path = /data/home/apps
    read only = No
    [homes]
    comment = Home Directories
    path = /home/users/%U/Documents
    valid users = %S
    read only = No
    browseable = No
    [printers]
    comment = SMB Print Spool
    path = /var/spool/samba
    guest ok = Yes
    printable = Yes
    use client driver = No
    browseable = No
    [netlogon]
    comment = Network Logon Service
    path = /var/lib/samba/netlogon
    guest ok = Yes
    locking = No
    [profiles]
    comment = Profile Share
    path = /var/lib/samba/profiles
    read only = No
    profile acls = Yes
    [profdata]
    comment = Profile Data Share
    path = /var/lib/samba/profdata
    read only = No
    profile acls = Yes
    [print$]
    comment = Printer Drivers
    path = /var/lib/samba/drivers

    Example 9.3. NT4 Migration LDAP Server Configuration File: /etc/openldap/slapd.conf Part A

    +	

    Procedure 9.1. User Migration Steps

    Example 9.1. NT4 Migration Samba-3 Server smb.conf Part: A

    [global]
    workgroup = DAMNATION
    netbios name = MERLIN
    passdb backend = ldapsam:ldap://localhost
    log level = 1
    syslog = 0
    log file = /var/log/samba/%m
    max log size = 0
    smb ports = 139 445
    name resolve order = wins bcast hosts
    add user script = /opt/IDEALX/sbin/smbldap-useradd -m '%u'
    #delete user script = /opt/IDEALX/sbin/smbldap-userdel '%u'
    add group script = /opt/IDEALX/sbin/smbldap-groupadd '%g'
    #delete group script = /opt/IDEALX/sbin/smbldap-groupdel '%g'
    add user to group script = /opt/IDEALX/sbin/ smbldap-groupmod -m '%u' '%g'
    #delete user from group script = /opt/IDEALX/sbin/smbldap-groupmod -x '%u' '%g'
    set primary group script = /opt/IDEALX/sbin/smbldap-usermod -g '%g' '%u'
    add machine script = /opt/IDEALX/sbin/smbldap-useradd -w '%u'
    logon script = scripts\logon.cmd
    logon path = \\%L\profiles\%U
    logon home = \\%L\%U
    logon drive = X:
    domain logons = Yes
    domain master = No
    #wins support = Yes
    wins server = 192.168.123.124
    ldap admin dn = cn=Manager,dc=terpstra-world,dc=org
    ldap group suffix = ou=Groups
    ldap idmap suffix = ou=Idmap
    ldap machine suffix = ou=People
    ldap passwd sync = Yes
    ldap suffix = dc=terpstra-world,dc=org
    ldap ssl = no
    ldap timeout = 20
    ldap user suffix = ou=People
    idmap backend = ldap:ldap://localhost
    idmap uid = 15000-20000
    idmap gid = 15000-20000
    winbind nested groups = Yes
    ea support = Yes
    map acl inherit = Yes

    Example 9.2. NT4 Migration Samba-3 Server smb.conf Part: B

    [apps]
    comment = Application Data
    path = /data/home/apps
    read only = No
    [homes]
    comment = Home Directories
    path = /home/users/%U/Documents
    valid users = %S
    read only = No
    browseable = No
    [printers]
    comment = SMB Print Spool
    path = /var/spool/samba
    guest ok = Yes
    printable = Yes
    use client driver = No
    browseable = No
    [netlogon]
    comment = Network Logon Service
    path = /var/lib/samba/netlogon
    guest ok = Yes
    locking = No
    [profiles]
    comment = Profile Share
    path = /var/lib/samba/profiles
    read only = No
    profile acls = Yes
    [profdata]
    comment = Profile Data Share
    path = /var/lib/samba/profdata
    read only = No
    profile acls = Yes
    [print$]
    comment = Printer Drivers
    path = /var/lib/samba/drivers

    Example 9.3. NT4 Migration LDAP Server Configuration File: /etc/openldap/slapd.conf Part A

     include         /etc/openldap/schema/core.schema
     include         /etc/openldap/schema/cosine.schema
     include         /etc/openldap/schema/inetorgperson.schema
    @@ -330,24 +330,24 @@
     aliases:        files
     #passwd_compat: ldap       #Not needed.
     #group_compat:  ldap      #Not needed.
    -

    1. +


    1. Configure the Samba smb.conf file to create a BDC. An example configuration is given in “NT4 Migration Samba-3 Server smb.conf Part: A”. The delete scripts are commented out so that during the process of migration no account information can be deleted. -

    2. - +

    3. + Configure OpenLDAP in preparation for the migration. An example sladp.conf file is shown in “NT4 Migration LDAP Server Configuration File: /etc/openldap/slapd.conf Part A”. The rootpw value is an encrypted password string that can be obtained by executing the slappasswd command. -

    4. - - +

    5. + + Install the PADL nss_ldap tool set, then configure the /etc/ldap.conf as shown in “NT4 Migration NSS LDAP File: /etc/ldap.conf”. -

    6. - +

    7. + Edit the /etc/nsswitch.conf file so it has the entries shown in “NT4 Migration NSS Control File: /etc/nsswitch.conf (Stage:1)”. Note that the LDAP entries have been commented out. This is deliberate. If these entries are active (not commented out), and the @@ -357,7 +357,7 @@ open and therefore cannot gain exclusive control of it. By commenting these entries out, it is possible to avoid this gridlock situation and thus the overall installation and configuration will progress more smoothly. -

    8. +

    9. Validate the the target NT4 PDC name is being correctly resolved to its IP address by executing the following:

      @@ -373,7 +373,7 @@
       

      Do not proceed to the next step if this step fails. It is imperative that the name of the PDC can be resolved to its IP address. If this is broken, fix it. -

    10. +

    11. Pull the domain SID from the NT4 domain that is being migrated as follows:

       root#  net rpc getsid -S TRANGRESSION -U Administrator%not24get
      @@ -391,11 +391,11 @@
       

       root#  net setlocalsid S-1-5-21-1385457007-882775198-1210191635
       

      -

    12. - - - - +

    13. + + + + Install the Idealx smbldap-tools software package, following the instructions given in “Install and Configure Idealx smbldap-tools Scripts”. The resulting perl scripts should be located in the /opt/IDEALX/sbin directory. @@ -489,10 +489,10 @@ /etc/smbldap-tools/smbldap.conf done. /etc/smbldap-tools/smbldap_bind.conf done.

      - - - - + + + + Note that the NT4 domain SID that was previously obtained was entered above. Also, the sambaUnixIdPooldn object was specified as sambaDomainName=DAMNATION. This is the location into which the Idealx smbldap-tools store the next available UID/GID @@ -501,16 +501,16 @@ was stored in the sambaUnixIdPooldn DIT location cn=NextFreeUnixId. Where smbldap-tools are being upgraded to version 0.9.1 it is appropriate to update this to the new location only if the directory information is also relocated. -

    14. +

    15. Start the LDAP server using the system interface script. On Novell SLES9 this is done as shown here:

       root#  rcldap start
       

      -

    16. +

    17. Edit the /etc/nsswitch.conf file so it has the entries shown in “NT4 Migration NSS Control File: /etc/nsswitch.conf (Stage:2)”. Note that the LDAP entries have now been uncommented. -

    18. +

    19. The LDAP management password must be installed into the secrets.tdb file as follows:

      @@ -518,7 +518,7 @@
       Setting stored password for 
                   "cn=Manager,dc=terpstra-world,dc=org" in secrets.tdb
       

      -

    20. +

    21. Populate the LDAP directory as shown here:

       root#  /opt/IDEALX/sbin/smbldap-populate -a root -k 0 -m 0
      @@ -544,8 +544,8 @@
       

      The script tries to add the ou=People container twice, hence the error message. This is expected behavior. -

    22. - +

    23. + Restart the LDAP server following initialization of the LDAP directory. Execute the system control script provided on your system. The following steps can be used on Novell SUSE SLES 9: @@ -553,7 +553,7 @@ root# rcldap restart root# chkconfig ldap on

      -

    24. +

    25. Verify that the new user accounts that have been added to the LDAP directory can be resolved as follows:

      @@ -584,8 +584,8 @@
       Backup Operators:x:551:
       Replicators:x:552:
       

      - In both cases the LDAP accounts follow the +::0: entry. -

    26. + In both cases the LDAP accounts follow the “+::0:” entry. +

    27. Now it is time to join the Samba BDC to the target NT4 domain that is being migrated to Samba-3 by executing the following:

      @@ -594,7 +594,7 @@
                                -U Administrator%not24get
       Joined domain DAMNATION.
       

      -

    28. +

    29. Set the new domain administrator (root) password for both UNIX and Windows as shown here:

       root#  /opt/IDEALX/sbin/smbldap-passwd root
      @@ -604,7 +604,7 @@
       

      Note: During account migration, the Windows Administrator account will not be migrated to the Samba server. -

    30. +

    31. Now validate that these accounts can be resolved using Samba's tools as shown here for user accounts:

      @@ -632,7 +632,7 @@
       Replicators (S-1-5-32-552) -> Replicators
       

      These are the expected results for a correctly configured system. -

    32. +

    33. Commence migration as shown here:

       root#  net rpc vampire -S TRANSGRESSION \
      @@ -640,7 +640,7 @@
       

      Check the vampire log to confirm that only expected errors have been reported. See “Migration Log Validation”. -

    34. +

    35. The migration of user accounts can be quickly validated as follows:

       root#  pdbedit -Lw
      @@ -675,7 +675,7 @@
       SCAVENGER$:26:B6288EB6D147B56F8963805A19B0ED49:...
       merlin$:27:820C50523F368C54AB9D85AE603AD09D:...
       

      -

    36. +

    37. The mapping of UNIX and Windows groups can be validated as show here:

       root#  net groupmap list
      @@ -707,13 +707,13 @@
       

      It is of vital importance that the domain SID portions of all group accounts are identical. -

    38. +

    39. The final responsibility in the migration process is to create identical shares and printing resources on the new Samba-3 server, copy all data across, set up privileges, and set share and file/directory access controls. -

    40. - - +

    41. + + Edit the smb.conf file to reset the parameter domain master = Yes so that the Samba server functions as a PDC for the purpose of migration. @@ -736,18 +736,18 @@ Server role: ROLE_DOMAIN_PDC Press enter to see a dump of your service definitions

      -

    42. +

    43. Now shut down the old NT4 PDC. Only when the old NT4 PDC and all NT4 BDCs have been shut down can the Samba-3 PDC be started. -

    44. +

    45. All workstations should function as they did with the old NT4 PDC. All interdomain trust accounts should remain in place and fully functional. All machine accounts and user logon accounts should also function correctly. -

    46. +

    47. The configuration of Samba-3 BDC servers can be accomplished now or at any convenient time in the future. Please refer to the carefully detailed process for doing so is outlined in “Samba-3 BDC Configuration”. -

    Migration Log Validation

    +

Migration Log Validation

The following vampire.log file is typical of a valid migration.

 adding user Administrator to group Domain Admins
@@ -841,7 +841,7 @@
 Creating unix group: 'Server Operators'
 Creating unix group: 'Users'
 

-

NT4 Migration Using tdbsam Backend

+

NT4 Migration Using tdbsam Backend

In this example, we change the domain name of the NT4 server from DRUGPREP to MEGANET prior to the use of the vampire (migration) tool. This migration process makes use of Linux system tools @@ -849,22 +849,22 @@ UNIX/Linux /etc/passwd and /etc/group databases. These entries must therefore be present, and correct options specified, in your smb.conf file, or else the migration does not work as it should. -

Procedure 9.2. Migration Steps Using tdbsam

  1. +

    Procedure 9.2. Migration Steps Using tdbsam

    1. Prepare a Samba-3 server precisely per the instructions shown in “The 500-User Office”. Set the workgroup name to MEGANET. -

    2. +

    3. Edit the smb.conf file to temporarily change the parameter domain master = No so the Samba server functions as a BDC for the purpose of migration. -

    4. +

    5. Start Samba as you have done previously. -

    6. +

    7. Join the NT4 Domain as a BDC, as shown here:

       root#  net rpc join -S oldnt4pdc -W MEGANET -UAdministrator%not24get
       Joined domain MEGANET.
       

      -

    8. +

    9. You may vampire the accounts from the NT4 PDC by executing the command, as shown here:

       root#  net rpc vampire -S oldnt4pdc -U Administrator%not24get
      @@ -904,7 +904,7 @@
       Fetching BUILTIN database
       SAM_DELTA_DOMAIN_INFO not handled
       

      -

    10. +

    11. At this point, we can validate our migration. Let's look at the accounts in the form in which they are seen in a smbpasswd file. This achieves that:

      @@ -936,7 +936,7 @@
       maryk:509:3636AB7E12EBE79AB79AE2610DD89D4C:
            CF271B744F7A55AFDA277FF88D80C527:[UX         ]:LCT-3E8B4270:
       

      -

    12. +

    13. An expanded view of a user account entry shows more of what was obtained from the NT4 PDC:

      @@ -962,7 +962,7 @@
       Password can change:  0
       Password must change: Mon, 18 Jan 2038 20:14:07 GMT
       

      -

    14. +

    15. The following command lists the long names of the groups that have been imported (vampired) from the NT4 PDC:

      @@ -979,68 +979,68 @@
       Users                 Ordinary users
       

      Everything looks well and in order. -

    16. +

    17. Edit the smb.conf file to reset the parameter domain master = Yes so the Samba server functions as a PDC for the purpose of migration. -

Key Points Learned

+

Key Points Learned

Migration of an NT4 PDC database to a Samba-3 PDC is possible. -

  • +

    • An LDAP backend is a suitable vehicle for NT4 migrations. -

    • +

    • A tdbsam backend can be used to perform a migration. -

    • +

    • Multiple NT4 domains can be merged into a single Samba-3 domain. -

    • +

    • The net Samba-3 domain most likely requires some administration and updating before going live. -

Questions and Answers

-

Questions and Answers

+

Why must I start each migration with a clean database? -
+
Is it possible to set my domain SID to anything I like? -
+
When using a tdbsam passdb backend, why must I have all domain user and group accounts in /etc/passwd and /etc/group? -
+
Why did you validate connectivity before attempting migration? -
+
How would you merge 10 tdbsam-based domains into an LDAP database? -
+
I want to change my domain name after I migrate all accounts from an NT4 domain to a Samba-3 domain. Does it make any sense to migrate the machine accounts in that case? -
+
After merging multiple NT4 domains into a Samba-3 domain, I lost all multiple group mappings. Why? -
+
How can I reset group membership after loading the account information into the LDAP database? -
+
What are the limits or constraints that apply to group names? -
+
My Windows NT4 PDC has 323,000 user accounts. How long will it take to migrate them to a Samba-3 LDAP backend system using the vampire process? -

+

Why must I start each migration with a clean database? -

+

This is a recommendation that permits the data from each NT4 domain to be kept separate until you are ready to merge them. Also, if you do not start with a clean database, you may find errors due to users or groups from multiple domains having the same name but different SIDs. It is better to permit each migration to complete without undue errors and then to handle the merging of vampired data under proper supervision. -

+

Is it possible to set my domain SID to anything I like? -

+

Yes, so long as the SID you create has the same structure as an autogenerated SID. The typical SID looks like this: S-1-5-21-XXXXXXXXXX-XXXXXXXXXX-XXXXXXXXXX, where the XXXXXXXXXX can be any number with from 6 to 10 digits. On the other hand, why would you really want to create your own SID? I cannot think of a good reason. You may want to set the SID to one that is already in use somewhere on your network, but that is a little different from straight out creating your own domain SID. -

+

When using a tdbsam passdb backend, why must I have all domain user and group accounts in /etc/passwd and /etc/group? -

+

Samba-3 must be able to tie all user and group account SIDs to a UNIX UID or GID. Samba does not fabricate the UNIX IDs from thin air, but rather requires them to be located in a suitable place. @@ -1055,15 +1055,15 @@ migration to the LDAP database, the accounts may be removed from the UNIX database files. In short then, all UNIX and Windows networking accounts, both in tdbsam as well as in LDAP, require UIDs/GIDs. -

+

Why did you validate connectivity before attempting migration?

Access validation before attempting to migrate NT4 domain accounts helps to pinpoint potential problems that may otherwise affect or impede account migration. I am always mindful of the 4 P's of migration: Planning Prevents Poor Performance. -

+

How would you merge 10 tdbsam-based domains into an LDAP database? -

+

If you have 10 tdbsam Samba domains, there is considerable risk that there are a number of accounts that have the same UNIX identifier (UID/GID). This means that you almost certainly have to edit a lot of data. It would be easiest to dump each database in smbpasswd @@ -1073,17 +1073,17 @@ tdbsam and then to LDAP. The final choice is yours. Just remember to verify all accounts that you have migrated before handing over access to a user. After all, too many users with a bad migration experience may threaten your career. -

+

I want to change my domain name after I migrate all accounts from an NT4 domain to a Samba-3 domain. Does it make any sense to migrate the machine accounts in that case? -

+

I would recommend not to migrate the machine account. The machine accounts should still work, but there are registry entries on each Windows NT4 and upward client that have a tattoo of the old domain name. If you unjoin the domain and then rejoin the newly renamed Samba-3 domain, you can be certain to avoid this tattooing effect. -

+

After merging multiple NT4 domains into a Samba-3 domain, I lost all multiple group mappings. Why? -

+

Samba-3 currently does not implement multiple group membership internally. If you use the Windows NT4 Domain User Manager to manage accounts and you have an LDAP backend, the multiple group membership is stored in the POSIX groups area. If you use either tdbsam or smbpasswd backend, @@ -1092,14 +1092,14 @@ file to which you migrated the NT4 Domain data, do not forget to edit the UNIX /etc/passwd and /etc/group information also. That is where the multiple group information is most closely at your fingertips. -

+

How can I reset group membership after loading the account information into the LDAP database? -

+

You can use the NT4 Domain User Manager that can be downloaded from the Microsoft Web site. The installation file is called SRVTOOLS.EXE. -

+

What are the limits or constraints that apply to group names? -

+

A Windows 200x group name can be up to 254 characters long, while in Windows NT4 the group name is limited to 20 characters. Most UNIX systems limit this to 32 characters. Windows groups can contain upper- and lowercase characters, as well as spaces. @@ -1111,7 +1111,7 @@ of the POSIX standards and likewise do not permit uppercase or space characters in group or user account names. You have to experiment with your system to find what its peculiarities are. -

+

My Windows NT4 PDC has 323,000 user accounts. How long will it take to migrate them to a Samba-3 LDAP backend system using the vampire process?

@@ -1120,7 +1120,7 @@ you would not be able to migrate 323,000 accounts because this number cannot fit into a 16-bit unsigned integer. UNIX/Linux systems that have a 32-bit UID/GID can easily handle this number of accounts. Please check this carefully before you attempt to effect a migration using the vampire process. -

+

Migration speed depends much on the processor speed, the network speed, disk I/O capability, and LDAP update overheads. On a dual processor AMD MP1600+ with 1 GB memory that was mirroring LDAP to a second identical system over 1 Gb Ethernet, I was able to migrate around 180 user accounts diff -u -r --new-file --exclude .svn --exclude CVS samba-3.3.10//docs/htmldocs/Samba3-ByExample/nw4migration.html samba-3.3.11//docs/htmldocs/Samba3-ByExample/nw4migration.html --- samba-3.3.10//docs/htmldocs/Samba3-ByExample/nw4migration.html 2010-01-14 11:24:20.000000000 +0100 +++ samba-3.3.11//docs/htmldocs/Samba3-ByExample/nw4migration.html 2010-02-22 16:53:36.000000000 +0100 @@ -1,6 +1,6 @@ -Chapter 10. Migrating NetWare Server to Samba-3

Chapter 10. Migrating NetWare Server to Samba-3

- - +Chapter 10. Migrating NetWare Server to Samba-3

Chapter 10. Migrating NetWare Server to Samba-3

+ + Novell is a company any seasoned IT manager has to admire. It has become increasingly Linux-friendly and is emerging out of a deep regression that almost saw the company disappear into obscurity. Novell's SUSE Linux hosts the NetWare server and it is the @@ -8,24 +8,24 @@ It will be interesting to see what becomes of NetWare over time. Meanwhile, there can be no denying that Novell is a Linux company.

- - - - + + + + Whatever flavor of Linux is preferred in your environment, whether Red Hat, Debian, Gentoo, Mandrake, or SUSE (Novell), the information in this chapter should be read with the knowledge that file locations may vary a little; even so, the information in this chapter should provide something of value.

- + Contributions to this chapter were made by Misty Stanley-Jones, a UNIX administrator of many years who surfaced on the Samba mailing list with a barrage of questions and who regularly helps other administrators to solve thorny Samba migration questions.

- - - - + + + + One wonders how many NetWare servers remain in active service. Many are being migrated to Samba on Linux. Red Hat Linux, SUSE Linux 9.x, and SUSE Linux Enterprise Server 9 are ideal target platforms to which a NetWare server may be migrated. The migration method @@ -49,28 +49,28 @@ File paths have been modified to permit use of RPM packages provided by Novell. In the original documentation contributed by Misty, the Courier-IMAP package had been built directly from the original source tarball. -

Introduction

- +

Introduction

+ Misty Stanley-Jones was recruited by Abmas to administer a network that had not received much attention for some years and was much in need of a makeover. As a brand-new sysadmin to this company, she inherited a very old Novell file server and came with a determination to change things for the better.

A site survey turned up the following details for the old NetWare server: -

200 MHz MMX processor

512K RAM

24 GB disk space in RAID1

Novell 4.11 patched to service pack 7

60+ users

7 network-attached printers

+

200 MHz MMX processor

512K RAM

24 GB disk space in RAID1

Novell 4.11 patched to service pack 7

60+ users

7 network-attached printers

The company had outgrown this server several years before and was dealing with severe growing pains. Some of the problems experienced were: -

  • Very slow performance

  • Available storage hovering around the 5% range

    • Extremely slow print spooling.

    • +

      • Very slow performance

      • Available storage hovering around the 5% range

        • Extremely slow print spooling.

        • Users storing information on their local hard drives, causing backup integrity problems

      - + At one point disk space had filled up to 100 percent, causing the payroll database to become corrupt. This caused the accounting department to be down for over a week and necessitated deployment of another file server. The replacement server was created with very poor security and design considerations from a discarded desktop PC. -

      Assignment Tasks

      +

      Assignment Tasks

      Misty has provided this summary of her migration experience in the hope that it will help someone to avoid the challenges she faced. Perhaps her configuration files and background will accelerate your learning as you @@ -89,12 +89,12 @@ is the result of treatment given to her files in an attempt to make the overall information more useful to you.

      - + After management reviewed a cost-benefit report as well as an estimated time-to-completion, approval was given proceed with the solution proposed. The server was built from purchased components. The total project cost was $3,000. A brief description of the configuration follows: -

      +

      3.0 GHz P4 Processor

      1 GB RAM

      @@ -111,33 +111,33 @@

      The new system has operated for 6 months without problems. Over the past months much attention has been focused on cleaning up desktops and user profiles. -

      Dissection and Discussion

      - - - - +

      Dissection and Discussion

      + + + + A decision to use LDAP was made even though I knew nothing about LDAP except that - I had been reading the book LDAP System Administration, by Gerald Carter. + I had been reading the book “LDAP System Administration,” by Gerald Carter. LDAP seemed to provide some of the functionality of Novell's e-Directory Services and would provide centralized authentication and identity management.

      - - - + + + Building the LDAP database took a while and a lot of trial and error. Following - the guidance I obtained from LDAP System - Administration, I installed OpenLDAP (from RPM; later I compiled + the guidance I obtained from “LDAP System + Administration,” I installed OpenLDAP (from RPM; later I compiled a more current version from source) and built my initial LDAP tree. -

      Technical Issues

      - - - - - - - - - +

      Technical Issues

      + + + + + + + + + The first challenge was to create a company white pages, followed by manually entering everything from the printed company directory. This used only the inetOrgPerson object class from the OpenLDAP schemas. The next step was to write a shell script that @@ -146,7 +146,7 @@ imported into LDAP. This would allow use of LDAP for Linux authentication, IMAP, POP3, and SMTP.

      - Because a decision was made to use Courier-IMAP the schema authldap.schema + Because a decision was made to use Courier-IMAP the schema “authldap.schema” from the Courier-IMAP source, tarball is necessary to resolve Courier-specific LDAP directory needs. Where the Courier-IMAP file provided by SUSE is used, this file is named courier.schema. @@ -183,21 +183,21 @@ echo "loginShell: $loginShell" echo "userPassword: $userPassword" done -


      Note

      +


      Note

      The PADL MigrationTools are recommended for migration of the UNIX account information into the LDAP directory. The tools consist of a set of Perl scripts for migration of users, groups, aliases, hosts, netgroups, networks, protocols, PRCs, and services from the existing ASCII text files (or from a name service such as NIS). This too set can be obtained from the PADL Web site. -

      Implementation

      -

      NetWare Migration Using LDAP Backend

      +

      Implementation

      +

      NetWare Migration Using LDAP Backend

      The following software must be installed on the SUSE Linux Enterprise Server to perform this migration: -

      courier-imap

      courier-imap-ldap

      nss_ldap

      openldap2-client

      openldap2-devel (only for Samba compilation)

      openldap2

      pam_ldap

      samba-3.0.20 or later

      samba-client-3.0.20 or later

      samba-winbind-3.0.20 or later

      smbldap-tools Version 0.9.1

      +

      courier-imap

      courier-imap-ldap

      nss_ldap

      openldap2-client

      openldap2-devel (only for Samba compilation)

      openldap2

      pam_ldap

      samba-3.0.20 or later

      samba-client-3.0.20 or later

      samba-winbind-3.0.20 or later

      smbldap-tools Version 0.9.1

      Each software application must be carefully configured in preparation for migration. The configuration files used at Abmas are provided as a guide and should be modified to meet needs at your site. -

      LDAP Server Configuration

      +

      LDAP Server Configuration

      The /etc/openldap/slapd.conf file Misty used is shown here:

       #/etc/openldap/slapd.conf
      @@ -362,7 +362,7 @@
         by * read
       

      - + The /etc/ldap.conf file used is listed in “NSS LDAP Control File /etc/ldap.conf”.

      Example 10.2. NSS LDAP Control File /etc/ldap.conf

       # /etc/ldap.conf
      @@ -416,8 +416,8 @@
       # possibilities to store hosts, services, ethers, and lots of other things.
       

      - - + + In my setup, users authenticate via PAM and NSS using LDAP-based accounts. The configuration file that controls the behavior of the PAM pam_unix2 module is shown in “The PAM Control File /etc/security/pam_unix2.conf” file. @@ -458,9 +458,9 @@ account: use_ldap password: use_ldap session: none -


      • +


      • If your LDAP database goes down, nobody can authenticate except for root. -

      • +

      • If failover is configured incorrectly, weird behavior can occur. For example, DNS can fail to resolve.

      @@ -468,31 +468,31 @@ of this document, and steps for implementing it are well documented.

      The following services authenticate using LDAP: -

      UNIX login/ssh

      Postfix (SMTP)

      Courier-IMAP/IMAPS/POP3/POP3S

      - - +

      UNIX login/ssh

      Postfix (SMTP)

      Courier-IMAP/IMAPS/POP3/POP3S

      + + Companywide white pages can be searched using an LDAP client such as the one in the Windows Address Book.

      - - + + Having gained a solid understanding of LDAP and a relatively workable LDAP tree thus far, it was time to configure Samba. I compiled the latest stable Samba and also installed the latest smbldap-tools from Idealx.

      The Samba smb.conf file was configured as shown in “Samba Configuration File smb.conf Part A”. -

      Example 10.4. Samba Configuration File smb.conf Part A

      # Global parameters
      [global]
      workgroup = MEGANET2
      netbios name = MASSIVE
      server string = Corp File Server
      passdb backend = ldapsam:ldap://localhost
      pam password change = Yes
      username map = /etc/samba/smbusers
      log level = 1
      log file = /data/samba/log/%m.log
      name resolve order = wins host bcast
      time server = Yes
      printcap name = cups
      show add printer wizard = No
      cups options = Raw
      add user script = /opt/IDEALX/sbin/smbldap-useradd -m "%u"
      add group script = /opt/IDEALX/sbin/smbldap-groupadd -p "%g"
      add user to group script = /opt/IDEALX/sbin/smbldap-groupmod -m "%u" "%g"
      delete user from group script = /opt/IDEALX/sbin/smbldap-groupmod -x "%u" "%g"
      set primary group script = /opt/IDEALX/sbin/smbldap-usermod -g "%g" "%u"
      add machine script = /usr/local/sbin/smbldap-useradd -w "%m"
      logon script = logon.bat
      logon path = \\%L\profiles\%U\%a
      logon drive = H:
      logon home = \\%L\%U
      domain logons = Yes
      wins support = Yes
      ldap admin dn = cn=Manager,dc=abmas,dc=biz
      ldap group suffix = ou=Groups
      ldap idmap suffix = ou=People
      ldap machine suffix = ou=People
      ldap passwd sync = Yes
      ldap suffix = ou=MEGANET2,dc=abmas,dc=biz
      ldap ssl = no
      ldap user suffix = ou=People
      admin users = root, "@Domain Admins"
      printer admin = "@Domain Admins"
      force printername = Yes

      Example 10.5. Samba Configuration File smb.conf Part B

      [netlogon]
      comment = Network logon service
      path = /data/samba/netlogon
      write list = "@Domain Admins"
      guest ok = Yes
      [profiles]
      comment = Roaming Profile Share
      path = /data/samba/profiles/
      read only = No
      profile acls = Yes
      veto files = desktop.ini
      browseable = No
      [homes]
      comment = Home Directories
      valid users = %S
      read only = No
      create mask = 0770
      veto files = desktop.ini
      hide files = desktop.ini
      browseable = No
      [software]
      comment = Software for %a computers
      path = /data/samba/shares/software/%a
      guest ok = Yes
      [public]
      comment = Public Files
      path = /data/samba/shares/public
      read only = No
      guest ok = Yes
      [PDF]
      comment = Location of documents printed to PDFCreator printer
      path = /data/samba/shares/pdf
      guest ok = Yes

      Example 10.6. Samba Configuration File smb.conf Part C

      [EVERYTHING]
      comment = All shares
      path = /data/samba
      valid users = "@Domain Admins"
      read only = No
      [CDROM]
      comment = CD-ROM on MASSIVE
      path = /mnt
      guest ok = Yes
      [print$]
      comment = Printer Drivers Share
      path = /data/samba/drivers
      write list = root
      browseable = No
      [printers]
      comment = All Printers
      path = /data/samba/spool
      create mask = 0644
      printable = Yes
      browseable = No
      [acct_hp8500]
      comment = "Accounting Color Laser Printer"
      path = /data/samba/spool/private
      valid users = @acct, @acct_admin, @hr, "@Domain Admins",@Receptionist, dwayne, terri, danae, jerry
      create mask = 0644
      printable = Yes
      copy = printers
      [plotter]
      comment = Engineering Plotter
      path = /data/samba/spool
      create mask = 0644
      printable = Yes
      use client driver = Yes
      copy = printers

      Example 10.7. Samba Configuration File smb.conf Part D

      [APPS]
      path = /data/samba/shares/Apps
      force group = "Domain Users"
      read only = No
      [ACCT]
      path = /data/samba/shares/Accounting
      valid users = @acct, "@Domain Admins"
      force group = acct
      read only = No
      create mask = 0660
      directory mask = 0770
      [ACCT_ADMIN]
      path = /data/samba/shares/Acct_Admin
      valid users = @â€acct_adminâ€
      force group = acct_admin
      [HR_PR]
      path = /data/samba/shares/HR_PR
      valid users = @hr, @acct_admin
      force group = hr
      [ENGR]
      path = /data/samba/shares/Engr
      valid users = @engr, @receptionist, @truss, "@Domain Admins", cheri
      force group = engr
      read only = No
      create mask = 0770
      [DATA]
      path = /data/samba/shares/DATA
      valid users = @engr, @receptionist, @truss, "@Domain Admins", cheri
      force group = engr
      read only = No
      create mask = 0770
      copy = engr

      Example 10.8. Samba Configuration File smb.conf Part E

      [X]
      path = /data/samba/shares/X
      valid users = @engr, @acct
      force group = engr
      read only = No
      create mask = 0770
      copy = engr
      [NETWORK]
      path = /data/samba/shares/network
      valid users = "@Domain Users"
      read only = No
      create mask = 0770
      guest ok = Yes
      [UTILS]
      path = /data/samba/shares/Utils
      write list = "@Domain Admins"
      [SYS]
      path = /data/samba/shares/SYS
      valid users = chad
      read only = No
      browseable = No

      - - - +

      Example 10.4. Samba Configuration File smb.conf Part A

      # Global parameters
      [global]
      workgroup = MEGANET2
      netbios name = MASSIVE
      server string = Corp File Server
      passdb backend = ldapsam:ldap://localhost
      pam password change = Yes
      username map = /etc/samba/smbusers
      log level = 1
      log file = /data/samba/log/%m.log
      name resolve order = wins host bcast
      time server = Yes
      printcap name = cups
      show add printer wizard = No
      cups options = Raw
      add user script = /opt/IDEALX/sbin/smbldap-useradd -m "%u"
      add group script = /opt/IDEALX/sbin/smbldap-groupadd -p "%g"
      add user to group script = /opt/IDEALX/sbin/smbldap-groupmod -m "%u" "%g"
      delete user from group script = /opt/IDEALX/sbin/smbldap-groupmod -x "%u" "%g"
      set primary group script = /opt/IDEALX/sbin/smbldap-usermod -g "%g" "%u"
      add machine script = /usr/local/sbin/smbldap-useradd -w "%m"
      logon script = logon.bat
      logon path = \\%L\profiles\%U\%a
      logon drive = H:
      logon home = \\%L\%U
      domain logons = Yes
      wins support = Yes
      ldap admin dn = cn=Manager,dc=abmas,dc=biz
      ldap group suffix = ou=Groups
      ldap idmap suffix = ou=People
      ldap machine suffix = ou=People
      ldap passwd sync = Yes
      ldap suffix = ou=MEGANET2,dc=abmas,dc=biz
      ldap ssl = no
      ldap user suffix = ou=People
      admin users = root, "@Domain Admins"
      printer admin = "@Domain Admins"
      force printername = Yes

      Example 10.5. Samba Configuration File smb.conf Part B

      [netlogon]
      comment = Network logon service
      path = /data/samba/netlogon
      write list = "@Domain Admins"
      guest ok = Yes
      [profiles]
      comment = Roaming Profile Share
      path = /data/samba/profiles/
      read only = No
      profile acls = Yes
      veto files = desktop.ini
      browseable = No
      [homes]
      comment = Home Directories
      valid users = %S
      read only = No
      create mask = 0770
      veto files = desktop.ini
      hide files = desktop.ini
      browseable = No
      [software]
      comment = Software for %a computers
      path = /data/samba/shares/software/%a
      guest ok = Yes
      [public]
      comment = Public Files
      path = /data/samba/shares/public
      read only = No
      guest ok = Yes
      [PDF]
      comment = Location of documents printed to PDFCreator printer
      path = /data/samba/shares/pdf
      guest ok = Yes

      Example 10.6. Samba Configuration File smb.conf Part C

      [EVERYTHING]
      comment = All shares
      path = /data/samba
      valid users = "@Domain Admins"
      read only = No
      [CDROM]
      comment = CD-ROM on MASSIVE
      path = /mnt
      guest ok = Yes
      [print$]
      comment = Printer Drivers Share
      path = /data/samba/drivers
      write list = root
      browseable = No
      [printers]
      comment = All Printers
      path = /data/samba/spool
      create mask = 0644
      printable = Yes
      browseable = No
      [acct_hp8500]
      comment = "Accounting Color Laser Printer"
      path = /data/samba/spool/private
      valid users = @acct, @acct_admin, @hr, "@Domain Admins",@Receptionist, dwayne, terri, danae, jerry
      create mask = 0644
      printable = Yes
      copy = printers
      [plotter]
      comment = Engineering Plotter
      path = /data/samba/spool
      create mask = 0644
      printable = Yes
      use client driver = Yes
      copy = printers

      Example 10.7. Samba Configuration File smb.conf Part D

      [APPS]
      path = /data/samba/shares/Apps
      force group = "Domain Users"
      read only = No
      [ACCT]
      path = /data/samba/shares/Accounting
      valid users = @acct, "@Domain Admins"
      force group = acct
      read only = No
      create mask = 0660
      directory mask = 0770
      [ACCT_ADMIN]
      path = /data/samba/shares/Acct_Admin
      valid users = @â€acct_adminâ€
      force group = acct_admin
      [HR_PR]
      path = /data/samba/shares/HR_PR
      valid users = @hr, @acct_admin
      force group = hr
      [ENGR]
      path = /data/samba/shares/Engr
      valid users = @engr, @receptionist, @truss, "@Domain Admins", cheri
      force group = engr
      read only = No
      create mask = 0770
      [DATA]
      path = /data/samba/shares/DATA
      valid users = @engr, @receptionist, @truss, "@Domain Admins", cheri
      force group = engr
      read only = No
      create mask = 0770
      copy = engr

      Example 10.8. Samba Configuration File smb.conf Part E

      [X]
      path = /data/samba/shares/X
      valid users = @engr, @acct
      force group = engr
      read only = No
      create mask = 0770
      copy = engr
      [NETWORK]
      path = /data/samba/shares/network
      valid users = "@Domain Users"
      read only = No
      create mask = 0770
      guest ok = Yes
      [UTILS]
      path = /data/samba/shares/Utils
      write list = "@Domain Admins"
      [SYS]
      path = /data/samba/shares/SYS
      valid users = chad
      read only = No
      browseable = No

      + + + Most of these shares are only used by one company group, but they are required because of some ancient Qbasic and Rbase applications were that written expecting their own drive letters.

      - - - + + + Note: During the process of building the new server, I kept data files up to date with the Novell server via use of rsync. On a separate system (my workstation in fact), which could be rebooted @@ -556,8 +556,8 @@

       root#  smbpasswd -w verysecret
       

      - where verysecret is replaced by the LDAP bind password. -

      Note

      + where “verysecret” is replaced by the LDAP bind password. +

      Note

      The Idealx smbldap-tools package can be configured using a script called configure.pl that is provided as part of the tool. See “Making Happy Users” for an example of its use. Many administrators, like Misty, choose to do this manually @@ -739,7 +739,7 @@ with_smbpasswd="0" smbpasswd="/usr/bin/smbpasswd"


      - + Note: I chose not to take advantage of the TLS capability of this. Eventually I may go back and tweak it. Also, I chose not to take advantage of the master/slave configuration as I heard horror stories that it was @@ -813,11 +813,11 @@ ...

      - - - - - + + + + + With the LDAP directory now initialized, it was time to create the Windows and POSIX (UNIX) group accounts as well as the mappings from Windows groups to UNIX groups. The easiest way to do this was to use smbldap-groupadd command. @@ -825,34 +825,34 @@ unique GID, and an automatically determined RID. I learned the hard way not to try to do this by hand.

      - - - + + + After I had my group mappings in place, I added users to the groups (the users don't really have to exist yet). I used the smbldap-groupmod command to accomplish this. It can also be done manually by adding memberUID attributes to the group entries in LDAP.

      - - - + + + The most monumental task of all was adding the sambaSamAccount information to each already existent posixAccount entry. I did it one at a time as I moved people onto the new server, by issuing the command:

       root#  smbldap-usermod -a -P username
       

      - - - + + + I completed that step for every user after asking the person what his or her current NetWare password was. The wiser way to have done it would probably have been to dump the entire database to an LDIF file. This can be done by executing:

       root#  slapcat > somefile.ldif
       

      - - + + Then update the LDIF file created by using a Perl script to parse and add the appropriate attributes and objectClasses to each entry, followed by re-importing the entire database into the LDAP directory. @@ -933,7 +933,7 @@ sambaAcctFlags: [W ]

      - + So now I could log on with a test user from the machine w2kengrspare. It was all well and good, but that user was in no groups yet and so had pretty boring access. I fixed that by writing the login script! To write the login script, I used @@ -942,7 +942,7 @@ easier to learn and more powerful than the standard netlogon scripts I have seen. I also did not have to do a logon script per user or per group.

      - + I downloaded Kixtart and put the following files in my netlogon share:

       KIX32.EXE
      @@ -954,7 +954,7 @@
                 We can get around the need.
       

      - + I then wrote the logon.kix file that is shown in “Kixtart Control File File: logon.kix”. I chose to keep it all in one file, but it can be split up and linked via include directives. @@ -1137,7 +1137,7 @@ have only three such machines, and one is going away in the very near future, so it was easier to do it by hand.

      - + At this point I was able to add the users. This is the part that really falls into upgrade. I moved the users over one group at a time, starting with the people who used the least amount of resources on the network. With each group @@ -1151,34 +1151,34 @@ copy the user's profile to the new server. This was very important, and I really struggled with the most effective way to do it. Here is the method that worked for every one of my users on Windows NT, 2000, and XP: -

      1. +

        1. Log in as the user on the domain. This creates the local copy of the user's profile and copies it to the server as he or she logs out. -

        2. +

        3. Reboot the computer and log in as the local machine administrator. -

        4. +

        5. Right-click My Computer, click Properties, and navigate to the user profiles tab (varies per version of Windows). -

        6. +

        7. Select the user's local profile (COMPUTERNAME\username), and click the Copy To button. -

        8. +

        9. In the next dialog, copy it directly to the profiles share on the Samba server (in my case \\PDCname\profiles\user\<architecture>. You will have had to make a connection to the share as that user (e.g., Windows Explorer type \\PDCname\profiles\username). -

        10. +

        11. When the copy is complete (it can take a while) log out, and log back in as the user. All of his or her settings and all contents of My Documents, Favorites, and the registry should have been copied successfully. -

        12. +

        13. If it doesn't look right (the dead giveaway is the desktop background), shut down the computer without logging out (power cycle) and try logging in as the user again. If it still doesn't work, repeat the steps above. I only had to ever repeat it once.

        Words to the Wise: -

        • +

          • If the user was anything other than a standard user on his or her system before, you will save yourself some headaches by giving him or her identical permissions (on the local machine) as his or her domain account before @@ -1186,7 +1186,7 @@ in the Control Panel, after joining the computer to the domain and before logging on as that user for the first time. Otherwise the user will have trouble with permissions on his or her registry keys. -

          • +

          • If any application was installed for the user only, rather than for the entire system, it will probably not work without being reinstalled.

          diff -u -r --new-file --exclude .svn --exclude CVS samba-3.3.10//docs/htmldocs/Samba3-ByExample/pr01.html samba-3.3.11//docs/htmldocs/Samba3-ByExample/pr01.html --- samba-3.3.10//docs/htmldocs/Samba3-ByExample/pr01.html 2010-01-14 11:23:54.000000000 +0100 +++ samba-3.3.11//docs/htmldocs/Samba3-ByExample/pr01.html 2010-02-22 16:53:36.000000000 +0100 @@ -1,6 +1,6 @@ -About the Cover Artwork

          About the Cover Artwork

          +About the Cover Artwork

          About the Cover Artwork

          The cover artwork of this book continues the freedom theme of the first - edition of Samba-3 by Example. The history of civilization + edition of “Samba-3 by Example”. The history of civilization demonstrates the fragile nature of freedom. It can be lost in a moment, and once lost, the cost of recovering liberty can be incredible. The last edition cover featured Alfred the Great who liberated England from the diff -u -r --new-file --exclude .svn --exclude CVS samba-3.3.10//docs/htmldocs/Samba3-ByExample/pr02.html samba-3.3.11//docs/htmldocs/Samba3-ByExample/pr02.html --- samba-3.3.10//docs/htmldocs/Samba3-ByExample/pr02.html 2010-01-14 11:23:54.000000000 +0100 +++ samba-3.3.11//docs/htmldocs/Samba3-ByExample/pr02.html 2010-02-22 16:53:36.000000000 +0100 @@ -1,4 +1,4 @@ -Acknowledgments

          Acknowledgments

          +Acknowledgments

          Acknowledgments

          Samba-3 by Example would not have been written except as a result of feedback provided by reviewers and readers of the book The Official Samba-3 HOWTO and Reference Guide. This second edition diff -u -r --new-file --exclude .svn --exclude CVS samba-3.3.10//docs/htmldocs/Samba3-ByExample/pr03.html samba-3.3.11//docs/htmldocs/Samba3-ByExample/pr03.html --- samba-3.3.10//docs/htmldocs/Samba3-ByExample/pr03.html 2010-01-14 11:23:54.000000000 +0100 +++ samba-3.3.11//docs/htmldocs/Samba3-ByExample/pr03.html 2010-02-22 16:53:36.000000000 +0100 @@ -1,4 +1,4 @@ -Foreword

          Foreword

          By John M. Weathersby, Executive Director, OSSI

          +Foreword

          Foreword

          By John M. Weathersby, Executive Director, OSSI

          The Open Source Software Institute (OSSI) is comprised of representatives from a broad spectrum of business and non-business organizations that share a common interest in the promotion of development and implementation of open source software solutions globally, and in particular within the United States of America. diff -u -r --new-file --exclude .svn --exclude CVS samba-3.3.10//docs/htmldocs/Samba3-ByExample/preface.html samba-3.3.11//docs/htmldocs/Samba3-ByExample/preface.html --- samba-3.3.10//docs/htmldocs/Samba3-ByExample/preface.html 2010-01-14 11:23:55.000000000 +0100 +++ samba-3.3.11//docs/htmldocs/Samba3-ByExample/preface.html 2010-02-22 16:53:36.000000000 +0100 @@ -1,4 +1,4 @@ -Preface

          Preface

          +Preface

          Preface

          Network administrators live busy lives. We face distractions and pressures that drive us to seek proven, working case scenarios that can be easily implemented. Often this approach lands us in trouble. There is a @@ -33,11 +33,11 @@ detailed information regarding secure operation and configuration of peripheral services and applications such as OpenLDAP, DNS and DHCP, the need for which can be met from other resources that are dedicated to the subject. -

          Why Is This Book Necessary?

          +

          Why Is This Book Necessary?

          This book is the result of observations and feedback. The feedback from the Samba-HOWTO-Collection has been positive and complimentary. There have been requests for far more worked examples, a - Samba Cookbook, and for training materials to + “Samba Cookbook,” and for training materials to help kick-start the process of mastering Samba.

          The Samba mailing lists users have asked for sample configuration files @@ -53,7 +53,7 @@ All example case configuration files, scripts, and other tools are provided on the CD-ROM. This book is descriptive, provides detailed diagrams, and makes deployment of Samba-3 a breeze. -

          Samba 3.0.20 Update Edition

          +

          Samba 3.0.20 Update Edition

          The Samba 3.0.x series has been remarkably popular. At the time this book first went to print samba-3.0.2 was being released. There have been significant modifications and enhancements between samba-3.0.2 and samba-3.0.14 (the current release) that @@ -111,8 +111,8 @@

      Symbolically linked files and directories on the UNIX host to absolute paths will - now be followed. This can be turned off using wide links = No in - the share stanza in the smb.conf file. Turning off wide links + now be followed. This can be turned off using “wide links = No” in + the share stanza in the smb.conf file. Turning off “wide links” support will degrade server performance because each path must be checked.

      @@ -122,11 +122,11 @@

      Versions of Samba prior to samba-3.0.11 required the use of the UNIX root - account from network Windows clients. The new enable privileges = Yes capability + account from network Windows clients. The new “enable privileges = Yes” capability means that functions such as adding machines to the domain, managing printers, etc. can now be delegated to normal user accounts or to groups of users.

      -

Prerequisites

+


Prerequisites

This book is not a tutorial on UNIX or Linux administration. UNIX and Linux training is best obtained from books dedicated to the subject. This book assumes that you have at least the basic skill necessary to use these operating @@ -139,7 +139,7 @@ find yourself at times intimidated by assumptions made. In this situation, you may need to refer to administrative guides or manuals for your operating system platform to find what is the best method to achieve what the text of this book describes. -

Approach

+

Approach

The first chapter deals with some rather thorny network analysis issues. Do not be put off by this. The information you glean, even without a detailed understanding of network protocol analysis, can help you understand how Windows networking functions. @@ -167,7 +167,7 @@

Each chapter has a set of questions and answers to help you to to understand and digest key attributes of the solutions presented. -

Summary of Topics

+

Summary of Topics

The contents of this second edition of Samba-3 by Example have been rearranged based on feedback from purchasers of the first edition.

@@ -187,12 +187,12 @@ so let's see how far we can get. If successful, Abmas grows quickly and soon needs to replace all servers and workstations.

TechInfo This chapter demands: -

  • Case 1: The simplest smb.conf file that may +

    • Case 1: The simplest smb.conf file that may reasonably be used. Works with Samba-2.x also. This configuration uses Share Mode security. Encrypted passwords are not used, so there is no smbpasswd file. -

    • Case 2: Another simple smb.conf file that adds +

    • Case 2: Another simple smb.conf file that adds WINS support and printing support. This case deals with a special requirement that demonstrates how to deal with purpose-built software that has a particular requirement @@ -200,7 +200,7 @@ configuration uses Share Mode security and also works with Samba-2.x. Encrypted passwords are not used, so there is no smbpasswd file. -

    • Case 3: This smb.conf configuration uses User Mode +

    • Case 3: This smb.conf configuration uses User Mode security. The file share configuration demonstrates the ability to provide master access to an administrator while restricting all staff to their own work areas. @@ -338,7 +338,7 @@ network. Avoid name resolution problems, identify potential causes of network collisions, avoid Samba configuration options that will weigh the server down. MS distributed file services to make your network fly and much more. This chapter contains a good deal of - Did I tell you about this...? type of hints to help keep your name on the top + “Did I tell you about this...?” type of hints to help keep your name on the top performers list.

      Chapter 14 Samba Support.

      This chapter has been added specifically to help those who are seeking professional @@ -364,23 +364,23 @@ have seen some of the information a Windows client sends to a file and print server to create a connection over which file and print operations may take place. -

Conventions Used

+

Conventions Used

The following notation conventions are used throughout this book: -

  • - TOSHARG2 is used as an abbreviation for the book, The Official Samba-3 - HOWTO and Reference Guide, Second Edition Editors: John H. Terpstra and Jelmer R. Vernooij, +

    • + TOSHARG2 is used as an abbreviation for the book, “The Official Samba-3 + HOWTO and Reference Guide, Second Edition” Editors: John H. Terpstra and Jelmer R. Vernooij, Publisher: Prentice Hall, ISBN: 0131882228. -

    • - S3bE2 is used as an abbreviation for the book, Samba-3 by Example, Second Edition +

    • + S3bE2 is used as an abbreviation for the book, “Samba-3 by Example, Second Edition” Editors: John H. Terpstra, Publisher: Prentice Hall, ISBN: 013188221X. -

    • +

    • Directories and filenames appear in mono-font. For example, /etc/pam.conf. -

    • +

    • Executable names are bolded. For example, smbd. -

    • +

    • Menu items and buttons appear in bold. For example, click Next. -

    • +

    • Selecting a menu item is indicated as: StartControl PanelAdministrative ToolsActive Directory Users and Computers

diff -u -r --new-file --exclude .svn --exclude CVS samba-3.3.10//docs/htmldocs/Samba3-ByExample/primer.html samba-3.3.11//docs/htmldocs/Samba3-ByExample/primer.html --- samba-3.3.10//docs/htmldocs/Samba3-ByExample/primer.html 2010-01-14 11:24:28.000000000 +0100 +++ samba-3.3.11//docs/htmldocs/Samba3-ByExample/primer.html 2010-02-22 16:53:36.000000000 +0100 @@ -1,14 +1,14 @@ -Chapter 16. Networking Primer

Chapter 16. Networking Primer

+Chapter 16. Networking Primer

Chapter 16. Networking Primer

You are about to use the equivalent of a microscope to look at the information that runs through the veins of a Windows network. We do more to observe the information than to interrogate it. When you are done with this primer, you should have a good understanding of the types of information that flow over the network. Do not worry, this is not - a biology lesson. We won't lose you in unnecessary detail. Think to yourself, This - is easy, then tackle each exercise without fear. + a biology lesson. We won't lose you in unnecessary detail. Think to yourself, “This + is easy,” then tackle each exercise without fear.

Samba can be configured with a minimum of complexity. Simplicity should be mastered before you get too deeply into complexities. Let's get moving: we have work to do. -

Requirements and Notes

+

Requirements and Notes

Successful completion of this primer requires two Microsoft Windows 9x/Me Workstations as well as two Microsoft Windows XP Professional Workstations, each equipped with an Ethernet card connected using a hub. Also required is one additional server (either Windows @@ -16,7 +16,7 @@ sniffer and analysis application (Wireshark is a good choice). All work should be undertaken on a quiet network where there is no other traffic. It is best to use a dedicated hub with only the machines under test connected at the time of the exercises. -

+

Wireshark (formerly Ethereal) has become the network protocol analyzer of choice for many network administrators. You may find more information regarding this tool from the Wireshark Web site. Wireshark installation @@ -29,18 +29,18 @@

To obtain Wireshark for your system, please visit the Wireshark download site. -

Note

+

Note

The successful completion of this chapter requires that you capture network traffic using Wireshark. It is recommended that you use a hub, not an Ethernet switch. It is necessary for the device used to act as a repeater, not as a filter. Ethernet switches may filter out traffic that is not directed at the machine that is used to monitor traffic; this would not allow you to complete the projects.

- + Do not worry too much if you do not have access to all this equipment; network captures from the exercises are provided on the enclosed CD-ROM. This makes it possible to dive directly into the analytical part of the exercises if you so desire. -

+

Please do not be alarmed at the use of a high-powered analysis tool (Wireshark) in this primer. We expose you only to a minimum of detail necessary to complete the exercises. If you choose to use any other network sniffer and protocol @@ -54,11 +54,11 @@

“Questions and Answers” also provides useful information that may help you to avoid significantly time-consuming networking problems. -

Introduction

+

Introduction

The purpose of this chapter is to create familiarity with key aspects of Microsoft Windows network computing. If you want a solid technical grounding, do not gloss over these exercises. The points covered are recurrent issues on the Samba mailing lists. -

+

You can see from these exercises that Windows networking involves quite a lot of network broadcast traffic. You can look into the contents of some packets, but only to see some particular information that the Windows client sends to a server in the course of @@ -72,31 +72,31 @@ preparatory reading.

Recommended preparatory reading: The Official Samba-3 HOWTO and Reference Guide, Second - Edition (TOSHARG2) Chapter 9, Network Browsing, and Chapter 3, - Server Types and Security Modes. -

Assignment Tasks

+ Edition (TOSHARG2) Chapter 9, “Network Browsing,” and Chapter 3, + “Server Types and Security Modes.” +

Assignment Tasks

You are about to witness how Microsoft Windows computer networking functions. The exercises step through identification of how a client machine establishes a connection to a remote Windows server. You observe how Windows machines find each other (i.e., how browsing works) and how the two key types of user identification (share mode security and user mode security) are affected. -

+

The networking protocols used by MS Windows networking when working with Samba use TCP/IP as the transport protocol. The protocols that are specific to Windows networking are encapsulated in TCP/IP. The network analyzer we use (Wireshark) is able to show you the contents of the TCP/IP packets (or messages). -

Procedure 16.1. Diagnostic Tasks

  1. +

    Procedure 16.1. Diagnostic Tasks

    1. Examine network traces to witness SMB broadcasts, host announcements, and name resolution processes. -

    2. +

    3. Examine network traces to witness how share mode security functions. -

    4. +

    5. Examine network traces to witness the use of user mode security. -

    6. +

    7. Review traces of network logons for a Windows 9x/Me client as well as a domain logon for a Windows XP Professional client. -

Exercises

- +

Exercises

+ You are embarking on a course of discovery. The first part of the exercise requires two MS Windows 9x/Me systems. We called one machine WINEPRESSME and the other MILGATE98. Each needs an IP address; we used 10.1.1.10 @@ -108,10 +108,10 @@

For these exercises, our test environment consisted of a SUSE 9.2 Professional Linux Workstation running VMWare 4.5. The following VMWare images were prepared: -

  • Windows 98 name: MILGATE98

  • Windows Me name: WINEPRESSME

  • Windows XP Professional name: LightrayXP

  • Samba-3.0.20 running on a SUSE Enterprise Linux 9

+

  • Windows 98 name: MILGATE98

  • Windows Me name: WINEPRESSME

  • Windows XP Professional name: LightrayXP

  • Samba-3.0.20 running on a SUSE Enterprise Linux 9

Choose a workgroup name (MIDEARTH) for each exercise.

- + The network captures provided on the CD-ROM included with this book were captured using Ethereal version 0.10.6. A later version suffices without problems (i.e. you should be using Wireshark), but an earlier version may not expose all the information needed. Each capture file has been decoded and listed as a trace file. A summary of all @@ -119,140 +119,140 @@ perform the time-consuming equipment configuration and test work. This is a good time to point out that the value that can be derived from this book really does warrant your taking sufficient time to practice each exercise with care and attention to detail. -

Single-Machine Broadcast Activity

+

Single-Machine Broadcast Activity

In this section, we start a single Windows 9x/Me machine, then monitor network activity for 30 minutes. -

Procedure 16.2. Monitoring Windows 9x Steps

  1. +

    Procedure 16.2. Monitoring Windows 9x Steps

    1. Start the machine from which network activity will be monitored (using Wireshark). Launch Wireshark, click CaptureStart.

      Click the following: -

      1. Update list of packets in real time

      2. Automatic scrolling in live capture

      3. Enable MAC name resolution

      4. Enable network name resolution

      5. Enable transport name resolution

      +

      1. Update list of packets in real time

      2. Automatic scrolling in live capture

      3. Enable MAC name resolution

      4. Enable network name resolution

      5. Enable transport name resolution

      Click OK. -

    2. +

    3. Start the Windows 9x/Me machine to be monitored. Let it run for a full 30 minutes. While monitoring, do not press any keyboard keys, do not click any on-screen icons or menus, and do not answer any dialog boxes. -

    4. +

    5. At the conclusion of 30 minutes, stop the capture. Save the capture to a file so you can go back to it later. Leave this machine running in preparation for the task in “Second Machine Startup Broadcast Interaction”. -

    6. +

    7. Analyze the capture. Identify each discrete message type that was captured. Note what transport protocol was used. Identify the timing between messages of identical types. -

    Findings

    +

Findings

The summary of the first 10 minutes of the packet capture should look like “Windows Me Broadcasts The First 10 Minutes”. A screenshot of a later stage of the same capture is shown in “Windows Me Later Broadcast Sample”. -

Figure 16.1. Windows Me Broadcasts The First 10 Minutes

Windows Me Broadcasts The First 10 Minutes

Figure 16.2. Windows Me Later Broadcast Sample

Windows Me Later Broadcast Sample

+

Figure 16.1. Windows Me Broadcasts The First 10 Minutes

Windows Me Broadcasts The First 10 Minutes

Figure 16.2. Windows Me Later Broadcast Sample

Windows Me Later Broadcast Sample

Broadcast messages observed are shown in “Windows Me Startup Broadcast Capture Statistics”. Actual observations vary a little, but not by much. Early in the startup process, the Windows Me machine broadcasts its name for two reasons: first to ensure that its name would not result in a name clash, and second to establish its presence with the Local Master Browser (LMB). -

Table 16.1. Windows Me Startup Broadcast Capture Statistics

MessageTypeNumNotes
WINEPRESSME<00>Reg84 lots of 2, 0.6 sec apart
WINEPRESSME<03>Reg84 lots of 2, 0.6 sec apart
WINEPRESSME<20>Reg84 lots of 2, 0.75 sec apart
MIDEARTH<00>Reg84 lots of 2, 0.75 sec apart
MIDEARTH<1d>Reg84 lots of 2, 0.75 sec apart
MIDEARTH<1e>Reg84 lots of 2, 0.75 sec apart
MIDEARTH<1b>Qry84300 sec apart at stable operation
__MSBROWSE__Reg8Registered after winning election to Browse Master
JHT<03>Reg84 x 2. This is the name of the user that logged onto Windows
Host Announcement WINEPRESSMEAnn2Observed at 10 sec
Domain/Workgroup Announcement MIDEARTHAnn18300 sec apart at stable operation
Local Master Announcement WINEPRESSMEAnn18300 sec apart at stable operation
Get Backup List RequestQry126 x 2 early in startup, 0.5 sec apart
Browser Election RequestAnn105 x 2 early in startup
Request Announcement WINEPRESSMEAnn4Early in startup

+

Table 16.1. Windows Me Startup Broadcast Capture Statistics

MessageTypeNumNotes
WINEPRESSME<00>Reg84 lots of 2, 0.6 sec apart
WINEPRESSME<03>Reg84 lots of 2, 0.6 sec apart
WINEPRESSME<20>Reg84 lots of 2, 0.75 sec apart
MIDEARTH<00>Reg84 lots of 2, 0.75 sec apart
MIDEARTH<1d>Reg84 lots of 2, 0.75 sec apart
MIDEARTH<1e>Reg84 lots of 2, 0.75 sec apart
MIDEARTH<1b>Qry84300 sec apart at stable operation
__MSBROWSE__Reg8Registered after winning election to Browse Master
JHT<03>Reg84 x 2. This is the name of the user that logged onto Windows
Host Announcement WINEPRESSMEAnn2Observed at 10 sec
Domain/Workgroup Announcement MIDEARTHAnn18300 sec apart at stable operation
Local Master Announcement WINEPRESSMEAnn18300 sec apart at stable operation
Get Backup List RequestQry126 x 2 early in startup, 0.5 sec apart
Browser Election RequestAnn105 x 2 early in startup
Request Announcement WINEPRESSMEAnn4Early in startup

From the packet trace, it should be noted that no messages were propagated over TCP/IP; all messages employed UDP/IP. When steady-state operation has been achieved, there is a cycle of various announcements, re-election of a browse master, and name queries. These create the symphony of announcements by which network browsing is made possible. -

+

For detailed information regarding the precise behavior of the CIFS/SMB protocols, - refer to the book Implementing CIFS: The Common Internet File System, + refer to the book “Implementing CIFS: The Common Internet File System,” by Christopher Hertel, (Prentice Hall PTR, ISBN: 013047116X). -

Second Machine Startup Broadcast Interaction

+

Second Machine Startup Broadcast Interaction

At this time, the machine you used to capture the single-system startup trace should still be running. The objective of this task is to identify the interaction of two machines in respect to broadcast activity. -

Procedure 16.3. Monitoring of Second Machine Activity

  1. +

    Procedure 16.3. Monitoring of Second Machine Activity

    1. On the machine from which network activity will be monitored (using Wireshark), launch Wireshark and click CaptureStart.

      Click: -

      1. Update list of packets in real time

      2. Automatic scrolling in live capture

      3. Enable MAC name resolution

      4. Enable network name resolution

      5. Enable transport name resolution

      +

      1. Update list of packets in real time

      2. Automatic scrolling in live capture

      3. Enable MAC name resolution

      4. Enable network name resolution

      5. Enable transport name resolution

      Click OK. -

    2. +

    3. Start the second Windows 9x/Me machine. Let it run for 15 to 20 minutes. While monitoring, do not press any keyboard keys, do not click any on-screen icons or menus, and do not answer any dialog boxes. -

    4. +

    5. At the conclusion of the capture time, stop the capture. Be sure to save the captured data so you can examine the network data capture again at a later date should that be necessary. -

    6. +

    7. Analyze the capture trace, taking note of the transport protocols used, the types of messages observed, and what interaction took place between the two machines. Leave both machines running for the next task. -

    Findings

    +

Findings

“Second Machine (Windows 98) Capture Statistics” summarizes capture statistics observed. As in the previous case, all announcements used UDP/IP broadcasts. Also, as was observed with the last example, the second Windows 9x/Me machine broadcasts its name on startup to ensure that there exists no name clash (i.e., the name is already registered by another machine) on the network segment. Those wishing to explore the inner details of the precise mechanism of how this functions should refer to - Implementing CIFS: The Common Internet File System. + “Implementing CIFS: The Common Internet File System.

Table 16.2. Second Machine (Windows 98) Capture Statistics

MessageTypeNumNotes
MILGATE98<00>Reg84 lots of 2, 0.6 sec apart
MILGATE98<03>Reg84 lots of 2, 0.6 sec apart
MILGATE98<20>Reg84 lots of 2, 0.75 sec apart
MIDEARTH<00>Reg84 lots of 2, 0.75 sec apart
MIDEARTH<1d>Reg84 lots of 2, 0.75 sec apart
MIDEARTH<1e>Reg84 lots of 2, 0.75 sec apart
MIDEARTH<1b>Qry18900 sec apart at stable operation
JHT<03>Reg2This is the name of the user that logged onto Windows
Host Announcement MILGATE98Ann14Every 120 sec
Domain/Workgroup Announcement MIDEARTHAnn6900 sec apart at stable operation
Local Master Announcement WINEPRESSMEAnn6Insufficient detail to determine frequency

- - - + + + Observation of the contents of Host Announcements, Domain/Workgroup Announcements, and Local Master Announcements is instructive. These messages convey a significant level of detail regarding the nature of each machine that is on the network. An example dissection of a Host Announcement is given in “Typical Windows 9x/Me Host Announcement”. -

Figure 16.3. Typical Windows 9x/Me Host Announcement

Typical Windows 9x/Me Host Announcement

Simple Windows Client Connection Characteristics

+

Figure 16.3. Typical Windows 9x/Me Host Announcement

Typical Windows 9x/Me Host Announcement

Simple Windows Client Connection Characteristics

The purpose of this exercise is to discover how Microsoft Windows clients create (establish) connections with remote servers. The methodology involves analysis of a key aspect of how Windows clients access remote servers: the session setup protocol. -

Procedure 16.4. Client Connection Exploration Steps

  1. +

    Procedure 16.4. Client Connection Exploration Steps

    1. Configure a Windows 9x/Me machine (MILGATE98) with a share called Stuff. Create a Full Access control password on this share. -

    2. +

    3. Configure another Windows 9x/Me machine (WINEPRESSME) as a client. Make sure that it exports no shared resources. -

    4. +

    5. Start both Windows 9x/Me machines and allow them to stabilize for 10 minutes. Log on to both machines using a user name (JHT) of your choice. Wait approximately 2 minutes before proceeding. -

    6. +

    7. Start Wireshark (or the network sniffer of your choice). -

    8. +

    9. From the WINEPRESSME machine, right-click Network Neighborhood, select Explore, select My Network PlacesEntire NetworkMIDEARTHMILGATE98Stuff. Enter the password you set for the Full Control mode for the Stuff share. -

    10. +

    11. When the share called Stuff is being displayed, stop the capture. Save the captured data in case it is needed for later analysis. -

    12. - +

    13. + From the top of the packets captured, scan down to locate the first packet that has interpreted as Session Setup AndX, User: anonymous; Tree Connect AndX, Path: \\MILGATE98\IPC$. -

    14. +

    15. In the dissection (analysis) panel, expand the SMB, Session Setup AndX Request, and Tree Connect AndX Request. Examine both operations. Identify the name of the user Account and what password was used. The Account name should be empty. This is a NULL session setup packet. -

    16. +

    17. Return to the packet capture sequence. There will be a number of packets that have been decoded of the type Session Setup AndX. Locate the last such packet that was targeted at the \\MILGATE98\IPC$ service. -

    18. - - +

    19. + + Dissect this packet as per the previous one. This packet should have a password length of 24 (characters) and should have a password field, the contents of which is a long hexadecimal number. Observe the name in the Account field. This is a User Mode session setup packet. -

    Findings and Comments

    - - The IPC$ share serves a vital purpose[15] +

Findings and Comments

+ + The IPC$ share serves a vital purpose[15] in SMB/CIFS-based networking. A Windows client connects to this resource to obtain the list of resources that are available on the server. The server responds with the shares and print queues that are available. In most but not all cases, the connection is made with a NULL username and a NULL password.

- + The two packets examined are material evidence of how Windows clients may interoperate with Samba. Samba requires every connection setup to be authenticated using valid UNIX account credentials (UID/GID). This means that even a NULL session setup can be established only by automatically mapping it to a valid UNIX account.

- - + + Samba has a special name for the NULL, or empty, user account: it calls it the guest account. The default value of this parameter is nobody; however, this can be @@ -261,9 +261,9 @@ FTP account. A sample NULL Session Setup AndX packet dissection is shown in “Typical Windows 9x/Me NULL SessionSetUp AndX Request”.

Figure 16.4. Typical Windows 9x/Me NULL SessionSetUp AndX Request

Typical Windows 9x/Me NULL SessionSetUp AndX Request

- - - + + + When a UNIX/Linux system does not have a nobody user account (/etc/passwd), the operation of the NULL account cannot validate and thus connections that utilize the guest account @@ -271,12 +271,12 @@ problem reported on the Samba mailing list. A sample User Mode session setup AndX is shown in “Typical Windows 9x/Me User SessionSetUp AndX Request”.

Figure 16.5. Typical Windows 9x/Me User SessionSetUp AndX Request

Typical Windows 9x/Me User SessionSetUp AndX Request

- + The User Mode connection packet contains the account name and the domain name. The password is provided in Microsoft encrypted form, and its length is shown as 24 characters. This is the length of Microsoft encrypted passwords. -

Windows 200x/XP Client Interaction with Samba-3

- By now you may be asking, Why did you choose to work with Windows 9x/Me? +

Windows 200x/XP Client Interaction with Samba-3

+ By now you may be asking, “Why did you choose to work with Windows 9x/Me?

First, we want to demonstrate the simple case. This book is not intended to be a detailed treatise on the Windows networking protocols, but rather to provide prescriptive guidance for deployment of Samba. @@ -290,55 +290,55 @@ To complete this exercise, you need a Windows XP Professional client that has been configured as a domain member of either a Samba-controlled domain or a Windows NT4 or 200x Active Directory domain. Here we do not provide details for how to configure this, as full coverage is provided earlier in this book. -

Procedure 16.5. Steps to Explore Windows XP Pro Connection Set-up

  1. +

    Procedure 16.5. Steps to Explore Windows XP Pro Connection Set-up

    1. Start your domain controller. Also, start the Wireshark monitoring machine, launch Wireshark, and then wait for the next step to complete. -

    2. +

    3. Start the Windows XP Client and wait 5 minutes before proceeding. -

    4. +

    5. On the machine from which network activity will be monitored (using Wireshark), launch Wireshark and click CaptureStart.

      Click: -

      1. Update list of packets in real time

      2. Automatic scrolling in live capture

      3. Enable MAC name resolution

      4. Enable network name resolution

      5. Enable transport name resolution

      +

      1. Update list of packets in real time

      2. Automatic scrolling in live capture

      3. Enable MAC name resolution

      4. Enable network name resolution

      5. Enable transport name resolution

      Click OK. -

    6. +

    7. On the Windows XP Professional client, press Ctrl-Alt-Delete to bring up the domain logon screen. Log in using valid credentials for a domain user account. -

    8. +

    9. Now proceed to connect to the domain controller as follows: Start(right-click) My Network PlacesExplore{Left Panel} [+] Entire Network{Left Panel} [+] Microsoft Windows Network{Left Panel} [+] Midearth{Left Panel} [+] Frodo{Left Panel} [+] data. Close the explorer window.

      In this step, our domain name is Midearth, the domain controller is called Frodo, and we have connected to a share called data. -

    10. +

    11. Stop the capture on the Wireshark monitoring machine. Be sure to save the captured data to a file so that you can refer to it again later. -

    12. +

    13. If desired, the Windows XP Professional client and the domain controller are no longer needed for exercises in this chapter. -

    14. - - +

    15. + + From the top of the packets captured, scan down to locate the first packet that has interpreted as Session Setup AndX Request, NTLMSSP_AUTH. -

    16. - - - +

    17. + + + In the dissection (analysis) panel, expand the SMB, Session Setup AndX Request. Expand the packet decode information, beginning at the Security Blob: entry. Expand the GSS-API -> SPNEGO -> netTokenTarg -> responseToken -> NTLMSSP keys. This should reveal that this is a NULL session setup packet. The User name: NULL so indicates. An example decode is shown in “Typical Windows XP NULL Session Setup AndX Request”. -

    18. +

    19. Return to the packet capture sequence. There will be a number of packets that have been decoded of the type Session Setup AndX Request. Click the last such packet that has been decoded as Session Setup AndX Request, NTLMSSP_AUTH. -

    20. - +

    21. + In the dissection (analysis) panel, expand the SMB, Session Setup AndX Request. Expand the packet decode information, beginning at the Security Blob: entry. Expand the GSS-API -> SPNEGO -> netTokenTarg -> responseToken -> NTLMSSP @@ -348,38 +348,38 @@ decode includes the Lan Manager Response: and the NTLM Response:. The values of these two parameters are the Microsoft encrypted password hashes: respectively, the LanMan password and then the NT (case-preserving) password hash. -

    22. - - +

    23. + + The passwords are 24-character hexadecimal numbers. This packet confirms that this is a User Mode session setup packet. -

    Figure 16.6. Typical Windows XP NULL Session Setup AndX Request

    Typical Windows XP NULL Session Setup AndX Request

    Figure 16.7. Typical Windows XP User Session Setup AndX Request

    Typical Windows XP User Session Setup AndX Request

    Discussion

    +

Figure 16.6. Typical Windows XP NULL Session Setup AndX Request

Typical Windows XP NULL Session Setup AndX Request

Figure 16.7. Typical Windows XP User Session Setup AndX Request

Typical Windows XP User Session Setup AndX Request

Discussion

This exercise demonstrates that, while the specific protocol for the Session Setup AndX is handled in a more sophisticated manner by recent MS Windows clients, the underlying rules or principles remain the same. Thus it is demonstrated that MS Windows XP Professional clients still use a NULL-Session connection to query and locate resources on an advanced network technology server (one using Windows NT4/200x or Samba). It also demonstrates that an authenticated connection must be made before resources can be used. -

Conclusions to Exercises

+

Conclusions to Exercises

In summary, the following points have been established in this chapter: -

  • +

    • When NetBIOS over TCP/IP protocols are enabled, MS Windows networking employs broadcast-oriented messaging protocols to provide knowledge of network services. -

    • +

    • Network browsing protocols query information stored on browse masters that manage information provided by NetBIOS Name Registrations and by way of ongoing host announcements and workgroup announcements. -

    • +

    • All Samba servers must be configured with a mechanism for mapping the NULL-Session to a valid but nonprivileged UNIX system account. -

    • +

    • The use of Microsoft encrypted passwords is built right into the fabric of Windows networking operations. Such passwords cannot be provided from the UNIX /etc/passwd database and thus must be stored elsewhere on the UNIX system in a manner that Samba can use. Samba-2.x permitted such encrypted passwords to be stored in the smbpasswd file or in an LDAP database. Samba-3 permits use of multiple passdb backend - databases in concurrent deployment. Refer to TOSHARG2, Chapter 10, Account Information Databases. -

Dissection and Discussion

- + databases in concurrent deployment. Refer to TOSHARG2, Chapter 10, “Account Information Databases.” +

Dissection and Discussion

+ The exercises demonstrate the use of the guest account, the way that MS Windows clients and servers resolve computer names to a TCP/IP address, and how connections between a client and a server are established. @@ -387,53 +387,53 @@ Those wishing background information regarding NetBIOS name types should refer to the Microsoft knowledgebase article Q102878. -

Technical Issues

- +

Technical Issues

+ Network browsing involves SMB broadcast announcements, SMB enumeration requests, connections to the IPC$ share, share enumerations, and SMB connection setup processes. The use of anonymous connections to a Samba server involve the use of the guest account that must map to a valid UNIX UID. -

Questions and Answers

+

Questions and Answers

The questions and answers given in this section are designed to highlight important aspects of Microsoft Windows networking. -

+

What is the significance of the MIDEARTH<1b> type query? -
+
What is the significance of the MIDEARTH<1d> type name registration? -
+
What is the role and significance of the <01><02>__MSBROWSE__<02><01> name registration? -
+
What is the significance of the MIDEARTH<1e> type name registration? -
+
What is the significance of the guest account in smb.conf? -
+
Is it possible to reduce network broadcast activity with Samba-3? -
+
Can I just use plain-text passwords with Samba? -
+
What parameter in the smb.conf file is used to enable the use of encrypted passwords? -
+
Is it necessary to specify encrypt passwords = Yes when Samba-3 is configured as a domain member? -
+
Is it necessary to specify a guest account when Samba-3 is configured as a domain member server? -

+

What is the significance of the MIDEARTH<1b> type query?

- - + + This is a broadcast announcement by which the Windows machine is attempting to locate a Domain Master Browser (DMB) in the event that it might exist on the network. - Refer to TOSHARG2, Chapter 9, Section 9.7, Technical Overview of Browsing, + Refer to TOSHARG2, Chapter 9, Section 9.7, “Technical Overview of Browsing,” for details regarding the function of the DMB and its role in network browsing. -

+

What is the significance of the MIDEARTH<1d> type name registration?

- - + + This name registration records the machine IP addresses of the LMBs. Network clients can query this name type to obtain a list of browser servers from the master browser. @@ -441,35 +441,35 @@ The LMB is responsible for monitoring all host announcements on the local network and for collating the information contained within them. Using this information, it can provide answers to other Windows network clients that request information such as: -

  • +

    • The list of machines known to the LMB (i.e., the browse list) -

    • +

    • The IP addresses of all domain controllers known for the domain -

    • +

    • The IP addresses of LMBs -

    • +

    • The IP address of the DMB (if one exists) -

    • +

    • The IP address of the LMB on the local segment -

+

What is the role and significance of the <01><02>__MSBROWSE__<02><01> name registration?

- + This name is registered by the browse master to broadcast and receive domain announcements. Its scope is limited to the local network segment, or subnet. By querying this name type, master browsers on networks that have multiple domains can find the names of master browsers for each domain. -

+

What is the significance of the MIDEARTH<1e> type name registration?

- + This name is registered by all browse masters in a domain or workgroup. The registration name type is known as the Browser Election Service. Master browsers register themselves with this name type so that DMBs can locate them to perform cross-subnet browse list updates. This name type is also used to initiate elections for Master Browsers. -

- +

+ What is the significance of the guest account in smb.conf?

This parameter specifies the default UNIX account to which MS Windows networking @@ -482,27 +482,27 @@ Samba operation. Either the operating system must have an account called nobody or there must be an entry in the smb.conf file with a valid UNIX account, such as guest account = ftp. -

+

Is it possible to reduce network broadcast activity with Samba-3?

- - + + Yes, there are two ways to do this. The first involves use of WINS (See TOSHARG2, Chapter 9, - Section 9.5, WINS The Windows Inter-networking Name Server); the + Section 9.5, “WINS The Windows Inter-networking Name Server”); the alternate method involves disabling the use of NetBIOS over TCP/IP. This second method requires - a correctly configured DNS server (see TOSHARG2, Chapter 9, Section 9.3, Discussion). + a correctly configured DNS server (see TOSHARG2, Chapter 9, Section 9.3, “Discussion”).

- - - + + + The use of WINS reduces network broadcast traffic. The reduction is greatest when all network clients are configured to operate in Hybrid Mode. This can be effected through use of DHCP to set the NetBIOS node type to type 8 for all network clients. Additionally, it is beneficial to configure Samba to use name resolve order = wins host cast. -

Note

+

Note

Use of SMB without NetBIOS is possible only on Windows 200x/XP Professional clients and servers, as well as with Samba-3. -

+

Can I just use plain-text passwords with Samba?

Yes, you can configure Samba to use plain-text passwords, though this does create a few problems. @@ -525,17 +525,17 @@ a UNIX system account for that user. On systems that run winbindd to access the Samba PDC/BDC to provide Windows user and group accounts, the idmap uid, idmap gid ranges set in the smb.conf file provide the local UID/GIDs needed for local identity management purposes. -

+

What parameter in the smb.conf file is used to enable the use of encrypted passwords?

The parameter in the smb.conf file that controls this behavior is known as encrypt passwords. The default setting for this in Samba-3 is Yes (Enabled). -

+

Is it necessary to specify encrypt passwords = Yes when Samba-3 is configured as a domain member?

No. This is the default behavior. -

+

Is it necessary to specify a guest account when Samba-3 is configured as a domain member server?

@@ -543,6 +543,6 @@ nobody. If this account does not exist on the UNIX server, then it is necessary to provide a guest account = an_account, where an_account is a valid local UNIX user account. -



[15] TOSHARG2, Sect 4.5.1



[15] TOSHARG2, Sect 4.5.1

diff -u -r --new-file --exclude .svn --exclude CVS samba-3.3.10//docs/htmldocs/Samba3-ByExample/RefSection.html samba-3.3.11//docs/htmldocs/Samba3-ByExample/RefSection.html --- samba-3.3.10//docs/htmldocs/Samba3-ByExample/RefSection.html 2010-01-14 11:24:29.000000000 +0100 +++ samba-3.3.11//docs/htmldocs/Samba3-ByExample/RefSection.html 2010-02-22 16:53:36.000000000 +0100 @@ -1,52 +1,52 @@ -Part III. Reference Section

Part III. Reference Section

Reference Section

+Part III. Reference Section

Part III. Reference Section

Reference Section

This section Samba-3 by Example provides important reference material that may help you to solve network performance issues, to answer some of the critiques published regarding Samba, or just to gain a more broad understanding of how Samba can play in a Windows networking world. -

Table of Contents

11. Active Directory, Kerberos, and Security
Introduction
Assignment Tasks
Dissection and Discussion
Technical Issues
Implementation
Share Access Controls
Share Definition Controls
Share Point Directory and File Permissions
Managing Windows 200x ACLs
Key Points Learned
Questions and Answers
12. Integrating Additional Services
Introduction
Assignment Tasks
Dissection and Discussion
Technical Issues
Political Issues
Implementation
Removal of Pre-Existing Conflicting RPMs
Key Points Learned
Questions and Answers
13. Performance, Reliability, and Availability
Introduction
Dissection and Discussion
Guidelines for Reliable Samba Operation
Name Resolution
Samba Configuration
Use and Location of BDCs
Use One Consistent Version of MS Windows Client
For Scalability, Use SAN-Based Storage on Samba Servers
Distribute Network Load with MSDFS
Replicate Data to Conserve Peak-Demand Wide-Area Bandwidth
Hardware Problems
Large Directories
Key Points Learned
14. Samba Support
Free Support
Commercial Support
15. A Collection of Useful Tidbits
Joining a Domain: Windows 200x/XP Professional
Samba System File Location
Starting Samba
DNS Configuration Files
The Forward Zone File for the Loopback Adaptor
The Reverse Zone File for the Loopback Adaptor
DNS Root Server Hint File
Alternative LDAP Database Initialization
Initialization of the LDAP Database
The LDAP Account Manager
IDEALX Management Console
Effect of Setting File and Directory SUID/SGID Permissions Explained
Shared Data Integrity
Microsoft Access
Act! Database Sharing
Opportunistic Locking Controls
16. Networking Primer
Requirements and Notes
Introduction
Assignment Tasks
Exercises
Single-Machine Broadcast Activity
Second Machine Startup Broadcast Interaction
Simple Windows Client Connection Characteristics
Windows 200x/XP Client Interaction with Samba-3
Conclusions to Exercises
Dissection and Discussion
Technical Issues
Questions and Answers
A. - GNU General Public License version 3 -
A. +

Table of Contents

11. Active Directory, Kerberos, and Security
Introduction
Assignment Tasks
Dissection and Discussion
Technical Issues
Implementation
Share Access Controls
Share Definition Controls
Share Point Directory and File Permissions
Managing Windows 200x ACLs
Key Points Learned
Questions and Answers
12. Integrating Additional Services
Introduction
Assignment Tasks
Dissection and Discussion
Technical Issues
Political Issues
Implementation
Removal of Pre-Existing Conflicting RPMs
Key Points Learned
Questions and Answers
13. Performance, Reliability, and Availability
Introduction
Dissection and Discussion
Guidelines for Reliable Samba Operation
Name Resolution
Samba Configuration
Use and Location of BDCs
Use One Consistent Version of MS Windows Client
For Scalability, Use SAN-Based Storage on Samba Servers
Distribute Network Load with MSDFS
Replicate Data to Conserve Peak-Demand Wide-Area Bandwidth
Hardware Problems
Large Directories
Key Points Learned
14. Samba Support
Free Support
Commercial Support
15. A Collection of Useful Tidbits
Joining a Domain: Windows 200x/XP Professional
Samba System File Location
Starting Samba
DNS Configuration Files
The Forward Zone File for the Loopback Adaptor
The Reverse Zone File for the Loopback Adaptor
DNS Root Server Hint File
Alternative LDAP Database Initialization
Initialization of the LDAP Database
The LDAP Account Manager
IDEALX Management Console
Effect of Setting File and Directory SUID/SGID Permissions Explained
Shared Data Integrity
Microsoft Access
Act! Database Sharing
Opportunistic Locking Controls
16. Networking Primer
Requirements and Notes
Introduction
Assignment Tasks
Exercises
Single-Machine Broadcast Activity
Second Machine Startup Broadcast Interaction
Simple Windows Client Connection Characteristics
Windows 200x/XP Client Interaction with Samba-3
Conclusions to Exercises
Dissection and Discussion
Technical Issues
Questions and Answers
A. + GNU General Public License version 3 +
A. Preamble -
A. +
A. TERMS AND CONDITIONS -
A. +
A. 0. Definitions. -
A. +
A. 1. Source Code. -
A. +
A. 2. Basic Permissions. -
A. +
A. 3. Protecting Users’ Legal Rights From Anti-Circumvention Law. -
A. +
A. 4. Conveying Verbatim Copies. -
A. +
A. 5. Conveying Modified Source Versions. -
A. +
A. 6. Conveying Non-Source Forms. -
A. +
A. 7. Additional Terms. -
A. +
A. 8. Termination. -
A. +
A. 9. Acceptance Not Required for Having Copies. -
A. +
A. 10. Automatic Licensing of Downstream Recipients. -
A. +
A. 11. Patents. -
A. +
A. 12. No Surrender of Others’ Freedom. -
A. +
A. 13. Use with the ???TITLE??? Affero General Public License. -
A. +
A. 14. Revised Versions of this License. -
A. +
A. 15. Disclaimer of Warranty. -
A. +
A. 16. Limitation of Liability. -
A. +
A. 17. Interpretation of Sections 15 and 16. -
A. +
A. END OF TERMS AND CONDITIONS -
A. +
A. How to Apply These Terms to Your New Programs
diff -u -r --new-file --exclude .svn --exclude CVS samba-3.3.10//docs/htmldocs/Samba3-ByExample/secure.html samba-3.3.11//docs/htmldocs/Samba3-ByExample/secure.html --- samba-3.3.10//docs/htmldocs/Samba3-ByExample/secure.html 2010-01-14 11:24:02.000000000 +0100 +++ samba-3.3.11//docs/htmldocs/Samba3-ByExample/secure.html 2010-02-22 16:53:36.000000000 +0100 @@ -1,4 +1,4 @@ -Chapter 3. Secure Office Networking

Chapter 3. Secure Office Networking

+Chapter 3. Secure Office Networking

Chapter 3. Secure Office Networking

Congratulations, your Samba networking skills are developing nicely. You started out with three simple networks in “No-Frills Samba Servers”, and then in “Small Office Networking” you designed and built a network that provides a high degree of flexibility, integrity, @@ -11,7 +11,7 @@ so caution is advised for anyone who tries to use Samba-2.2.x with the guidance here given. To avoid confusion, this book is all about Samba-3. Let's get the exercises in this chapter underway. -

Introduction

+

Introduction

You have made Mr. Meany a very happy man. Recently he paid you a fat bonus for work well done. It is one year since the last network upgrade. You have been quite busy. Two months ago Mr. Meany gave approval to hire Christine Roberson, who has taken over @@ -40,7 +40,7 @@ Occasionally she wants to work with you on a challenging problem. When you told her about your move, she almost resigned, although she was reassured that a new manager would be hired to run Information Technology, and she would be responsible only for operations. -

Assignment Tasks

+

Assignment Tasks

You promised the staff Internet services including Web browsing, electronic mail, virus protection, and a company Web site. Christine is eager to help turn the vision into reality. Let's see how close you can get to the promises made. @@ -83,13 +83,13 @@ of users had to share a PC while waiting for new machines to arrive. This presented some problems with desktop computers and software installation into the new users' desktop profiles. -

Dissection and Discussion

+

Dissection and Discussion

Many of the conclusions you draw here are obvious. Some requirements are not very clear or may simply be your means of drawing the most out of Samba-3. Much can be done more simply than you will demonstrate here, but keep in mind that the network must scale to at least 500 users. This means that some functionality will be overdesigned for the current 130-user environment. -

Technical Issues

+

Technical Issues

In this exercise we use a 24-bit subnet mask for the two local networks. This, of course, limits our network to a maximum of 253 usable IP addresses. The network address range chosen is one assigned by RFC1918 for private networks. @@ -97,14 +97,14 @@ addresses, it is a good idea to switch to a network address specified in RFC1918 in the 172.16.0.0/16 range. This is done in subsequent chapters.

- - + + The high growth rates projected are a good reason to use the tdbsam passdb backend. The use of smbpasswd for the backend may result in performance problems. The tdbsam passdb backend offers features that are not available with the older, flat ASCII-based smbpasswd database.

- + The proposed network design uses a single server to act as an Internet services host for electronic mail, Web serving, remote administrative access via SSH, Samba-based file and print services. This design is often chosen by sites that feel @@ -117,10 +117,10 @@ Samba will be configured to specifically not operate on the Ethernet interface that is directly connected to the Internet.

- - - - + + + + You know that your ISP is providing full firewall services, but you cannot rely on that. Always assume that human error will occur, so be prepared by using Linux firewall facilities based on iptables to effect NAT. Block all @@ -131,7 +131,7 @@ generic antivirus handling are beyond the scope of this book and therefore are not covered except insofar as this affects Samba-3.

- + Notebook computers are configured to use a network login when in the office and a local account to log in while away from the office. Users store all work done in transit (away from the office) by using a local share for work files. Standard procedures @@ -141,26 +141,26 @@ This is a preventative measure to protect client information as well as private business records.

- + All applications are served from the central server from a share called apps. Microsoft Office XP Professional and OpenOffice 1.1.0 will be installed using a network (or administrative) installation. Accounting and financial management software can also be run only from the central application server. Notebook users are provided with locally installed applications on a need-to-have basis only.

- + The introduction of roaming profiles support means that users can move between desktop computer systems without constraint while retaining full access to their data. The desktop travels with them as they move.

- + The DNS server implementation must now address both internal and external needs. You forward DNS lookups to your ISP-provided server as well as the abmas.us external secondary DNS server.

- - - + + + Compared with the DHCP server configuration in “Small Office Networking”, “Abmas Accounting DHCP Server Configuration File /etc/dhcpd.conf”, the configuration used in this example has to deal with the presence of an Internet connection. The scope set for it ensures that no DHCP services will be offered on the external @@ -184,8 +184,8 @@ a problem because Christine is to install and configure one single workstation and then clone that configuration, using Norton Ghost, to all workstations. Each machine is identical, so this should pose no problem. -

Hardware Requirements

- +

Hardware Requirements

+ This server runs a considerable number of services. From similarly configured Linux installations, the approximate calculated memory requirements are as shown in “Estimation of Memory Requirements”. @@ -213,7 +213,7 @@ as the system load builds up. Given the low cost of memory, it does not make sense to compromise in this area.

- + Aggregate input/output loads should be considered for sizing network configuration as well as disk subsystems. For network bandwidth calculations, one would typically use an estimate of 0.1 MB/sec per user. This suggests that 100-Base-T (approx. 10 MB/sec) @@ -222,8 +222,8 @@ to a 1 Gb Ethernet switch that provides connectivity to an expandable array of 100-Base-T switched ports.

- - + + Considering the choice of 1 Gb Ethernet interfaces for the two local network segments, the aggregate network I/O capacity will be 2100 Mb/sec (about 230 MB/sec), an I/O demand that would require a fast disk storage I/O capability. Peak disk throughput is @@ -255,10 +255,10 @@ Add 50% buffer 303 GBytes Recommended Storage: 908 GBytes


- + The preferred storage capacity should be approximately 1 Terabyte. Use of RAID level 5 with two hot spare drives would require an 8-drive by 200 GB capacity per drive array. -

Political Issues

+

Political Issues

Your industry is coming under increasing accountability pressures. Increased paranoia is necessary so you can demonstrate that you have acted with due diligence. You must not trust your Internet connection. @@ -267,12 +267,12 @@ an application server, your primary reason for the decision to implement this is that it gives you greater control over software licensing.

- + You are well aware that the current configuration results in some performance issues as the size of the desktop profile grows. Given that users use Microsoft Outlook Express, you know that the storage implications of the .PST file is something that needs to be addressed later. -

Implementation

+

Implementation

“Abmas Network Topology 130 Users” demonstrates the overall design of the network that you will implement.

The information presented here assumes that you are already familiar with many basic steps. @@ -283,49 +283,49 @@ here, there are many other good reference books on these subjects.

The smb.conf file has the following noteworthy features: -

  • +

    • The NetBIOS name of the Samba server is set to DIAMOND. -

    • +

    • The Domain name is set to PROMISES. -

    • - - - +

    • + + + Ethernet interface eth0 is attached to the Internet connection and is externally exposed. This interface is explicitly not available for Samba to use. Samba listens on this interface for broadcast messages but does not broadcast any information on eth0, nor does it accept any connections from it. This is achieved by way of the interfaces parameter and the bind interfaces only entry. -

    • - - - +

    • + + + The passdb backend parameter specifies the creation and use of the tdbsam password backend. This is a binary database that has excellent scalability for a large number of user account entries. -

    • - - - +

    • + + + WINS serving is enabled by the wins support = Yes, and name resolution is set to use it by means of the name resolve order = wins bcast hosts entry. -

    • - +

    • + The Samba server is configured for use by Windows clients as a time server. -

    • - - - +

    • + + + Samba is configured to directly interface with CUPS via the direct internal interface that is provided by CUPS libraries. This is achieved with the printing = CUPS as well as the printcap name = CUPS entries. -

    • - - - +

    • + + + External interface scripts are provided to enable Samba to interface smoothly to essential operating system functions for user and group management. This is important to enable workstations to join the Domain and is also important so that you can use @@ -333,20 +333,20 @@ are provided as part of the SRVTOOLS.EXE toolkit that can be downloaded from the Microsoft FTP site. -

    • - +

    • + The smb.conf file specifies that the Samba server will operate in (default) - security = user mode[5] + security = user mode[5] (User Mode). -

    • - - +

    • + + Domain logon services as well as a Domain logon script are specified. The logon script will be used to add robustness to the overall network configuration. -

    • - - - +

    • + + + Roaming profiles are enabled through the specification of the parameter, logon path = \\%L\profiles\%U. The value of this parameter translates the %L to the name by which the Samba server is called by the client (for this @@ -355,42 +355,42 @@ It is the administrator's responsibility to ensure there is a directory in the root of the profile share for each user. This directory must be owned by the user also. An exception to this requirement is when a profile is created for group use. -

    • - - +

    • + + Precautionary veto is effected for particular Windows file names that have been targeted by virus-related activity. Additionally, Microsoft Office files are vetoed from opportunistic locking controls. This should help to prevent lock contention-related file access problems. -

    • +

    • Every user has a private home directory on the UNIX/Linux host. This is mapped to a network drive that is the same for all users.

    The configuration of the server is the most complex so far. The following steps are used: -

    1. +

      1. Basic System Configuration -

      2. +

      3. Samba Configuration -

      4. +

      5. DHCP and DNS Server Configuration -

      6. +

      7. Printer Configuration -

      8. +

      9. Process Start-up Configuration -

      10. +

      11. Validation -

      12. +

      13. Application Share Configuration -

      14. +

      15. Windows Client Configuration

      The following sections cover each step in logical and defined detail. -

      Basic System Configuration

      - +

      Basic System Configuration

      + The preparation in this section assumes that your SUSE Enterprise Linux Server 8.0 system has been freshly installed. It prepares basic files so that the system is ready for comprehensive operation in line with the network diagram shown in “Abmas Network Topology 130 Users”. -

      Procedure 3.1. Server Configuration Steps

      1. - +

        Procedure 3.1. Server Configuration Steps

        1. + Using the UNIX/Linux system tools, name the server server.abmas.us. Verify that your hostname is correctly set by running:

          @@ -402,9 +402,9 @@
           root#  hostname -f
           server.abmas.us
           

          -

        2. - - +

        3. + + Edit your /etc/hosts file to include the primary names and addresses of all network interfaces that are on the host server. This is necessary so that during startup the system can resolve all its own names to the IP address prior to @@ -425,15 +425,15 @@ 192.168.2.20 qmsf.abmas.biz qmsf 192.168.2.30 hplj6f.abmas.biz hplj6f

          - - - + + + The printer entries are not necessary if named is started prior to startup of cupsd, the CUPS daemon. -

        4. - - - +

        5. + + + The host server is acting as a router between the two internal network segments as well as for all Internet access. This necessitates that IP forwarding be enabled. This can be achieved by adding to the /etc/rc.d/boot.local an entry as follows: @@ -442,10 +442,10 @@

          To ensure that your kernel is capable of IP forwarding during configuration, you may wish to execute that command manually also. This setting permits the Linux system to - act as a router.[6] -

        6. - - + act as a router.[6] +

        7. + + Installation of a basic firewall and NAT facility is necessary. The following script can be installed in the /usr/local/sbin directory. It is executed from the /etc/rc.d/boot.local startup @@ -497,7 +497,7 @@ echo "1" > /proc/sys/net/ipv4/ip_forward echo -e "\nNAT firewall done.\n"


      -

    2. +

    3. Execute the following to make the script executable:

       root#  chmod 755 /usr/local/sbin/abmas-natfw.sh
      @@ -524,15 +524,15 @@
       /usr/local/sbin/abmas-natfw.sh
       

    - + The server is now ready for Samba configuration. During the validation step, you remove the entry for the Samba server diamond from the /etc/hosts file. This is done after you are satisfied that DNS-based name resolution is functioning correctly. -

Samba Configuration

+

Samba Configuration

When you have completed this section, the Samba server is ready for testing and validation; however, testing and validation have to wait until DHCP, DNS, and printing (CUPS) services have been configured. -

Procedure 3.2. Samba Configuration Steps

  1. +

    Procedure 3.2. Samba Configuration Steps

    1. Install the Samba-3 binary RPM from the Samba-Team FTP site. Assuming that the binary RPM file is called samba-3.0.20-1.i386.rpm, one way to install this file is as follows: @@ -542,18 +542,18 @@ This operation must be performed while logged in as the root user. Successful operation is clearly indicated. If this installation should fail for any reason, refer to the operating system manufacturer's documentation for guidance. -

    2. +

    3. Install the smb.conf file shown in “130 User Network with tdbsam [globals] Section”, “130 User Network with tdbsam Services Section Part A”, and “130 User Network with tdbsam Services Section Part B”. Concatenate (join) all three files to make a single smb.conf file. The final, fully qualified path for this file should be /etc/samba/smb.conf. -

      Example 3.4. 130 User Network with tdbsam [globals] Section

      # Global parameters
      [global]
      workgroup = PROMISES
      netbios name = DIAMOND
      interfaces = eth1, eth2, lo
      bind interfaces only = Yes
      passdb backend = tdbsam
      pam password change = Yes
      passwd program = /usr/bin/passwd %u
      passwd chat = *New*Password* %n\n *Re-enter*new*password*%n\n *Password*changed*
      username map = /etc/samba/smbusers
      unix password sync = Yes
      log level = 1
      syslog = 0
      log file = /var/log/samba/%m
      max log size = 50
      smb ports = 139
      name resolve order = wins bcast hosts
      time server = Yes
      printcap name = CUPS
      show add printer wizard = No
      add user script = /usr/sbin/useradd -m '%u'
      delete user script = /usr/sbin/userdel -r '%u'
      add group script = /usr/sbin/groupadd '%g'
      delete group script = /usr/sbin/groupdel '%g'
      add user to group script = /usr/sbin/usermod -G '%g' '%u'
      add machine script = /usr/sbin/useradd -s /bin/false -d /tmp '%u'
      shutdown script = /var/lib/samba/scripts/shutdown.sh
      abort shutdown script = /sbin/shutdown -c
      logon script = scripts\logon.bat
      logon path = \\%L\profiles\%U
      logon drive = X:
      logon home = \\%L\%U
      domain logons = Yes
      preferred master = Yes
      wins support = Yes
      utmp = Yes
      map acl inherit = Yes
      printing = cups
      cups options = Raw
      veto files = /*.eml/*.nws/*.{*}/
      veto oplock files = /*.doc/*.xls/*.mdb/


      +

      Example 3.4. 130 User Network with tdbsam [globals] Section

      # Global parameters
      [global]
      workgroup = PROMISES
      netbios name = DIAMOND
      interfaces = eth1, eth2, lo
      bind interfaces only = Yes
      passdb backend = tdbsam
      pam password change = Yes
      passwd program = /usr/bin/passwd %u
      passwd chat = *New*Password* %n\n *Re-enter*new*password*%n\n *Password*changed*
      username map = /etc/samba/smbusers
      unix password sync = Yes
      log level = 1
      syslog = 0
      log file = /var/log/samba/%m
      max log size = 50
      smb ports = 139
      name resolve order = wins bcast hosts
      time server = Yes
      printcap name = CUPS
      show add printer wizard = No
      add user script = /usr/sbin/useradd -m '%u'
      delete user script = /usr/sbin/userdel -r '%u'
      add group script = /usr/sbin/groupadd '%g'
      delete group script = /usr/sbin/groupdel '%g'
      add user to group script = /usr/sbin/usermod -G '%g' '%u'
      add machine script = /usr/sbin/useradd -s /bin/false -d /tmp '%u'
      shutdown script = /var/lib/samba/scripts/shutdown.sh
      abort shutdown script = /sbin/shutdown -c
      logon script = scripts\logon.bat
      logon path = \\%L\profiles\%U
      logon drive = X:
      logon home = \\%L\%U
      domain logons = Yes
      preferred master = Yes
      wins support = Yes
      utmp = Yes
      map acl inherit = Yes
      printing = cups
      cups options = Raw
      veto files = /*.eml/*.nws/*.{*}/
      veto oplock files = /*.doc/*.xls/*.mdb/


      -

      Example 3.5. 130 User Network with tdbsam Services Section Part A

      [homes]
      comment = Home Directories
      valid users = %S
      read only = No
      browseable = No
      [printers]
      comment = SMB Print Spool
      path = /var/spool/samba
      guest ok = Yes
      printable = Yes
      use client driver = Yes
      default devmode = Yes
      browseable = No
      [netlogon]
      comment = Network Logon Service
      path = /var/lib/samba/netlogon
      guest ok = Yes
      locking = No
      [profiles]
      comment = Profile Share
      path = /var/lib/samba/profiles
      read only = No
      profile acls = Yes
      [accounts]
      comment = Accounting Files
      path = /data/accounts
      read only = No


      +

      Example 3.5. 130 User Network with tdbsam Services Section Part A

      [homes]
      comment = Home Directories
      valid users = %S
      read only = No
      browseable = No
      [printers]
      comment = SMB Print Spool
      path = /var/spool/samba
      guest ok = Yes
      printable = Yes
      use client driver = Yes
      default devmode = Yes
      browseable = No
      [netlogon]
      comment = Network Logon Service
      path = /var/lib/samba/netlogon
      guest ok = Yes
      locking = No
      [profiles]
      comment = Profile Share
      path = /var/lib/samba/profiles
      read only = No
      profile acls = Yes
      [accounts]
      comment = Accounting Files
      path = /data/accounts
      read only = No


      -

      Example 3.6. 130 User Network with tdbsam Services Section Part B

      [service]
      comment = Financial Services Files
      path = /data/service
      read only = No
      [pidata]
      comment = Property Insurance Files
      path = /data/pidata
      read only = No
      [apps]
      comment = Application Files
      path = /apps
      read only = Yes
      admin users = bjordan


      -

    4. - +

      Example 3.6. 130 User Network with tdbsam Services Section Part B

      [service]
      comment = Financial Services Files
      path = /data/service
      read only = No
      [pidata]
      comment = Property Insurance Files
      path = /data/pidata
      read only = No
      [apps]
      comment = Application Files
      path = /apps
      read only = Yes
      admin users = bjordan


      +

    5. + Add the root user to the password backend as follows:

       root#  smbpasswd -a root
      @@ -565,8 +565,8 @@
       		This account is essential in the regular maintenance of your Samba server. It must never be
       		deleted. If for any reason the account is deleted, you may not be able to recreate this account
       		without considerable trouble.
      -		

    6. - +

    7. + Create the username map file to permit the root account to be called Administrator from the Windows network environment. To do this, create the file /etc/samba/smbusers with the following contents: @@ -592,17 +592,17 @@ # End of File ####

      -

    8. - - - - +

    9. + + + + Create and map Windows Domain Groups to UNIX groups. A sample script is provided in “Small Office Networking”, “Script to Map Windows NT Groups to UNIX Groups”. Create a file containing this script. We called ours /etc/samba/initGrps.sh. Set this file so it can be executed, and then execute the script. Sample output should be as follows: -

      Example 3.7. Script to Map Windows NT Groups to UNIX Groups

      +

      Example 3.7. Script to Map Windows NT Groups to UNIX Groups

       #!/bin/bash
       #
       # initGrps.sh
      @@ -654,14 +654,14 @@
       System Operators (S-1-5-32-549) -> -1
       Users (S-1-5-32-545) -> -1
       

      -

    10. - - - - - - - +

    11. + + + + + + + There is one preparatory step without which you will not have a working Samba network environment. You must add an account for each network user. For each user who needs to be given a Windows Domain account, make an entry in the @@ -685,19 +685,19 @@ Added user username.

      You do of course use a valid user login ID in place of username. -

    12. - - - +

    13. + + + Using the preferred tool for your UNIX system, add each user to the UNIX groups created previously as necessary. File system access control will be based on UNIX group membership. -

    14. +

    15. Create the directory mount point for the disk subsystem that can be mounted to provide data storage for company files. In this case the mount point is indicated in the smb.conf file is /data. Format the file system as required, and mount the formatted file system partition using appropriate system tools. -

    16. - +

    17. + Create the top-level file storage directories for data and applications as follows:

       root#  mkdir -p /data/{accounts,finsrvcs}
      @@ -714,7 +714,7 @@
                       The directory root of the finsvcs share is /data/finsvcs.
       		The /apps directory is the root of the apps share
       		that provides the application server infrastructure.
      -		

    18. +

    19. The smb.conf file specifies an infrastructure to support roaming profiles and network logon services. You can now create the file system infrastructure to provide the locations on disk that these services require. Adequate planning is essential, @@ -737,10 +737,10 @@ root# chown 'username':users /var/lib/samba/profiles/'username' root# chmod ug+wrx,o+rx,-w /var/lib/samba/profiles/'username'

      -

    20. - - - +

    21. + + + Create a logon script. It is important that each line is correctly terminated with a carriage return and line-feed combination (i.e., DOS encoding). The following procedure works if the right tools (unix2dos and dos2unix) are installed. @@ -756,12 +756,12 @@ root# unix2dos < /var/lib/samba/netlogon/scripts/logon.bat.unix \ > /var/lib/samba/netlogon/scripts/logon.bat

      -

Configuration of DHCP and DNS Servers

+

Configuration of DHCP and DNS Servers

DHCP services are a basic component of the entire network client installation. DNS operation is foundational to Internet access as well as to trouble-free operation of local networking. When you have completed this section, the server should be ready for solid duty operation. -

Procedure 3.3. DHCP and DNS Server Configuration Steps

  1. - +

    Procedure 3.3. DHCP and DNS Server Configuration Steps

    1. + Create a file called /etc/dhcpd.conf with the contents as shown in “DHCP Server Configuration File /etc/dhcpd.conf”. @@ -811,19 +811,19 @@ subnet 123.45.67.64 netmask 255.255.255.252 { }


-

  • - +

  • + Create a file called /etc/named.conf that has the combined contents of the “DNS Master Configuration File /etc/named.conf Master Section”, “DNS Master Configuration File /etc/named.conf Forward Lookup Definition Section”, and “DNS Master Configuration File /etc/named.conf Reverse Lookup Definition Section” files that are concatenated (merged) in this specific order. -

  • +

  • Create the files shown in their respective directories as shown in DNS (named) Resource Files.

    Table 3.2. DNS (named) Resource Files


    -

    Example 3.9. DNS Master Configuration File /etc/named.conf Master Section

    +

    Example 3.9. DNS Master Configuration File /etc/named.conf Master Section

     ###
     # Abmas Biz DNS Control File
     ###
    @@ -1007,8 +1007,8 @@
     dns                     CNAME   server
     


    -

  • - +

  • + All DNS name resolution should be handled locally. To ensure that the server is configured correctly to handle this, edit /etc/resolv.conf to have the following content: @@ -1017,13 +1017,13 @@ nameserver 127.0.0.1 nameserver 123.45.54.23

    - + This instructs the name resolver function (when configured correctly) to ask the DNS server that is running locally to resolve names to addresses. In the event that the local name server is not available, ask the name server provided by the ISP. The latter, of course, does not resolve purely local names to IP addresses. -

  • - +

  • + The final step is to edit the /etc/nsswitch.conf file. This file controls the operation of the various resolver libraries that are part of the Linux Glibc libraries. Edit this file so that it contains the following entries: @@ -1035,24 +1035,24 @@ there are a few more steps along the road. First, configure the print spooling and print processing system. Then you can configure the server so that all services start automatically on reboot. You must also manually start all services prior to validation testing. -

  • Printer Configuration

    +

    Printer Configuration

    Network administrators who are new to CUPS based-printing typically experience some difficulty mastering its powerful features. The steps outlined in this section are designed to navigate around the distractions of learning CUPS. Instead of implementing smart features and capabilities, our approach is to use it as a transparent print queue that performs no filtering, and only minimal handling of each print job that is submitted to it. In other words, our configuration turns CUPS into a raw-mode print queue. This means that the correct printer driver must be installed on all clients. -

    Procedure 3.4. Printer Configuration Steps

    1. +

      Procedure 3.4. Printer Configuration Steps

      1. Configure each printer to be a DHCP client, carefully following the manufacturer's guidelines. -

      2. +

      3. Follow the instructions in the printer manufacturer's manuals to permit printing to port 9100. Use any other port the manufacturer specifies for direct-mode raw printing, and adjust the port as necessary in the following example commands. This allows the CUPS spooler to print using raw mode protocols. - - -

      4. - + + +

      5. + Configure the CUPS Print Queues as follows:

         root#  lpadmin -p qmsa -v socket://qmsa.abmas.biz:9100 -E
        @@ -1060,9 +1060,9 @@
         root#  lpadmin -p qmsf -v socket://qmsf.abmas.biz:9100 -E
         root#  lpadmin -p hplj6f -v socket://hplj6f.abmas.biz:9100 -E
         

        - + This creates the necessary print queues with no assigned print filter. -

      6. +

      7. Print queues may not be enabled at creation. Use lpc stat to check the status of the print queues and, if necessary, make certain that the queues you have just created are enabled by executing the following: @@ -1072,7 +1072,7 @@ root# /usr/bin/enable qmsf root# /usr/bin/enable hplj6f

        -

      8. +

      9. Even though your print queues may be enabled, it is still possible that they are not accepting print jobs. A print queue services incoming printing requests only when configured to do so. Ensure that your print queues are @@ -1083,29 +1083,29 @@ root# /usr/sbin/accept qmsf root# /usr/sbin/accept hplj6f

        -

      10. - - - +

      11. + + + Edit the file /etc/cups/mime.convs to uncomment the line:

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

        -

      12. - +

      13. + Edit the file /etc/cups/mime.types to uncomment the line:

         application/octet-stream
         

        -

      14. +

      15. Printing drivers are installed on each network client workstation.

      Note: If the parameter cups options = Raw is specified in the smb.conf file, the last two steps can be omitted with CUPS version 1.1.18, or later.

      The UNIX system print queues have been configured and are ready for validation testing. -

    Process Startup Configuration

    - +

    Process Startup Configuration

    + There are two essential steps to process startup configuration. First, the process must be configured so that it automatically restarts each time the server is rebooted. This step involves use of the chkconfig tool that @@ -1114,11 +1114,11 @@ directories. Links are created so that when the system run level is changed, the necessary start or kill script is run.

    - - - - - + + + + + In the event that a service is not run as a daemon, but via the internetworking super daemon (inetd or xinetd), then the chkconfig tool makes the necessary entries in the /etc/xinetd.d directory @@ -1126,20 +1126,20 @@ re-read its control files.

    Last, each service must be started to permit system validation to proceed. -

    1. +

      1. Use the standard system tool to configure each service to restart automatically at every system reboot. For example, - +

         root#  chkconfig dhpcd on
         root#  chkconfig named on
         root#  chkconfig cups on
         root#  chkconfig smb on
         

        -

      2. - - - +

      3. + + + Now start each service to permit the system to be validated. Execute each of the following in the sequence shown: @@ -1149,8 +1149,8 @@ root# /etc/rc.d/init.d/cups restart root# /etc/rc.d/init.d/smb restart

        -

    Validation

    - +

    Validation

    + Complex networking problems are most often caused by simple things that are poorly or incorrectly configured. The validation process adopted here should be followed carefully; it is the result of the experience gained from years of making and correcting the most common mistakes. Shortcuts often lead to basic errors. You should @@ -1160,8 +1160,8 @@ days. A well debugged network is a foundation for happy network users and network administrators. Later in this book you learn how to make users happier. For now, it is enough to learn to validate. Let's get on with it. -

    Procedure 3.5. Server Validation Steps

    1. - +

      Procedure 3.5. Server Validation Steps

      1. + One of the most important facets of Samba configuration is to ensure that name resolution functions correctly. You can check name resolution with a few simple tests. The most basic name resolution is provided from the @@ -1186,8 +1186,8 @@

        This proves that name resolution via the /etc/hosts file is working. -

      2. - +

      3. + So far, your installation is going particularly well. In this step we validate DNS server and name resolution operation. Using your favorite UNIX system editor, change the /etc/nsswitch.conf file so that the @@ -1195,8 +1195,8 @@

         hosts:        dns
         

        -

      4. - +

      5. + Before you test DNS operation, it is a good idea to verify that the DNS server is running by executing the following:

        @@ -1210,7 +1210,7 @@
          2552 pts/2    S      0:00 grep named
         

        This means that we are ready to check DNS operation. Do so by executing: - +

         root#  ping diamond
         PING sleeth1.abmas.biz (192.168.1.1) 56(84) bytes of data.
        @@ -1226,12 +1226,12 @@
         root#  host -f diamond.abmas.biz
         sleeth1.abmas.biz has address 192.168.1.1
         

        - + You may now remove the entry called diamond from the /etc/hosts file. It does not hurt to leave it there, but its removal reduces the number of administrative steps for this name. -

      6. - +

      7. + WINS is a great way to resolve NetBIOS names to their IP address. You can test the operation of WINS by starting nmbd (manually or by way of the Samba startup method shown in “Process Startup Configuration”). You must edit @@ -1250,7 +1250,7 @@ 64 bytes from 192.168.1.1: icmp_seq=1 ttl=64 time=0.094 ms 64 bytes from 192.168.1.1: icmp_seq=2 ttl=64 time=0.479 ms

        - + Now that you can relax with the knowledge that all three major forms of name resolution to IP address resolution are working, edit the /etc/nsswitch.conf again. This time you add all three forms of name resolution to this file. @@ -1259,7 +1259,7 @@ hosts: files dns wins

        The system is looking good. Let's move on. -

      8. +

      9. It would give you peace of mind to know that the DHCP server is running and available for service. You can validate DHCP services by running: @@ -1270,8 +1270,8 @@

        This shows that the server is running. The proof of whether or not it is working comes when you try to add the first DHCP client to the network. -

      10. - +

      11. + This is a good point at which to start validating Samba operation. You are content that name resolution is working for basic TCP/IP needs. Let's move on. If your smb.conf file has bogus options or parameters, this may cause Samba @@ -1342,11 +1342,11 @@ ### Remainder cut to save space ###

        Clear away all errors before proceeding. -

      12. - - - - +

      13. + + + + Check that the Samba server is running:

         root#  ps ax | grep mbd
        @@ -1359,10 +1359,10 @@
         14295 ?        S     0:00 /usr/sbin/winbindd -D
         

        The winbindd daemon is running in split mode (normal), so there are also - two instances[7] of it. -

      14. - - + two instances[7] of it. +

      15. + + Check that an anonymous connection can be made to the Samba server:

         root#  smbclient -L localhost -U%
        @@ -1393,10 +1393,10 @@
         			of browsing the server from a Windows client to obtain a list of shares on the server.
         			The -U% argument means to send a NULL username and
         			a NULL password.
        -			

      16. - - - +

      17. + + + Verify that each printer has the IP address assigned in the DHCP server configuration file. The easiest way to do this is to ping the printer name. Immediately after the ping response has been received, execute arp -a to find the MAC address of the printer @@ -1411,12 +1411,12 @@ root# arp -a hplj6a (192.168.1.30) at 00:03:47:CB:81:E0 [ether] on eth0

        - + The MAC address 00:03:47:CB:81:E0 matches that specified for the IP address from which the printer has responded and with the entry for it in the /etc/dhcpd.conf file. Repeat this for each printer configured. -

      18. - +

      19. + Make an authenticated connection to the server using the smbclient tool:

         root#  smbclient //diamond/accounts -U gholmes
        @@ -1434,8 +1434,8 @@
                         55974 blocks of size 65536. 33968 blocks available
         smb: \> q
         

        -

      20. - +

      21. + Your new server is connected to an Internet-accessible connection. Before you start your firewall, you should run a port scanner against your system. You should repeat that after the firewall has been started. This helps you understand to what extent the @@ -1509,9 +1509,9 @@ Nmap run completed -- 1 IP address (1 host up) scanned in 168 seconds

        -

    Application Share Configuration

    - - +

    Application Share Configuration

    + + The use of an application server is a key mechanism by which desktop administration overheads can be reduced. Check the application manual for your software to identify how best to create an administrative installation. @@ -1519,20 +1519,20 @@ Some Windows software will only run locally on the desktop computer. Such software is typically not suited for administrative installation. Administratively installed software permits one or more of the following installation choices: -

    • +

      • Install software fully onto a workstation, storing data files on the same workstation. -

      • +

      • Install software fully onto a workstation with central network data file storage. -

      • +

      • Install software to run off a central application server with data files stored on the local workstation. This is often called a minimum installation, or a network client installation. -

      • +

      • Install software to run off a central application server with data files stored on a central network share. This type of installation often prevents storage of work files on the local workstation.

      - + A common application deployed in this environment is an office suite. Enterprise editions of Microsoft Office XP Professional can be administratively installed by launching the installation from a command shell. The command that achieves this is @@ -1549,8 +1549,8 @@ A network workstation (minimum) installation requires typically 10 MB to 15 MB of local disk space. In the latter case, when the applications are used, they load over the network.

      - - + + Microsoft Office Service Packs can be unpacked to update an administrative share. This makes it possible to update MS Office XP Professional for all users from a single installation of the service pack and generally circumvents the need to run updates on each network @@ -1559,7 +1559,7 @@ The default location for MS Office XP Professional data files can be set through registry editing or by way of configuration options inside each Office XP Professional application.

      - + OpenOffice.Org OpenOffice Version 1.1.0 can be installed locally. It can also be installed to run off a network share. The latter is a most desirable solution for office-bound network users and for administrative staff alike. It permits quick and easy updates @@ -1572,7 +1572,7 @@ prompted on screen for the target installation location. This is the administrative share point. The full administrative OpenOffice share takes approximately 150 MB of disk space. -

      Comments Regarding Software Terms of Use

      +

      Comments Regarding Software Terms of Use

      Many single-user products can be installed into an administrative share, but personal versions of products such as Microsoft Office XP Professional do not permit this. Many people do not like terms of use typical with commercial products, so a few comments @@ -1596,142 +1596,142 @@ also. Whatever the licensing terms may be, if you do not approve of the terms of use, please do not use the software.

      - + Samba is provided under the terms of the GNU GPL Version 2, a copy of which is provided with the source code. -

      Windows Client Configuration

      +

    Windows Client Configuration

    Christine needs to roll out 130 new desktop systems. There is no doubt that she also needs to reinstall many of the notebook computers that will be recycled for use with the new network configuration. The smartest way to handle the challenge of the roll-out program is to build a staged system for each type of target machine, and then use an image replication tool such as Norton Ghost (enterprise edition) to replicate the staged machine to its target desktops. The same can be done with notebook computers as long as they are identical or sufficiently similar. -

    Procedure 3.6. Windows Client Configuration Procedure

    1. - - +

      Procedure 3.6. Windows Client Configuration Procedure

      1. + + Install MS Windows XP Professional. During installation, configure the client to use DHCP for TCP/IP protocol configuration. DHCP configures all Windows clients to use the WINS Server address that has been defined for the local subnet. -

      2. +

      3. Join the Windows Domain PROMISES. Use the Domain Administrator username root and the SMB password you assigned to this account. A detailed step-by-step procedure for joining a Windows 200x/XP Professional client to a Windows Domain is given in “A Collection of Useful Tidbits”, “Joining a Domain: Windows 200x/XP Professional”. Reboot the machine as prompted and then log on using the Domain Administrator account (root). -

      4. +

      5. Verify DIAMOND is visible in My Network Places, that it is possible to connect to it and see the shares accounts, apps, and finsvcs, and that it is possible to open each share to reveal its contents. -

      6. +

      7. Create a drive mapping to the apps share on the server DIAMOND. -

      8. +

      9. Perform an administrative installation of each application to be used. Select the options that you wish to use. Of course, you can choose to run applications over the network, correct? -

      10. +

      11. Now install all applications to be installed locally. Typical tools include Adobe Acrobat, NTP-based time synchronization software, drivers for specific local devices such as fingerprint scanners, and the like. Probably the most significant application for local installation is antivirus software. -

      12. +

      13. Now install all four printers onto the staging system. The printers you install include the accounting department HP LaserJet 6 and Minolta QMS Magicolor printers. You will also configure identical printers that are located in the financial services department. Install printers on each machine following the steps shown in the Windows client printer preparation procedure below. -

      14. - +

      15. + When you are satisfied that the staging systems are complete, use the appropriate procedure to remove the client from the domain. Reboot the system and then log on as the local administrator and clean out all temporary files stored on the system. Before shutting down, use the disk defragmentation tool so that the file system is in optimal condition before replication. -

      16. +

      17. Boot the workstation using the Norton (Symantec) Ghosting diskette (or CD-ROM) and image the machine to a network share on the server. -

      18. - - +

      19. + + You may now replicate the image to the target machines using the appropriate Norton Ghost procedure. Make sure to use the procedure that ensures each machine has a unique Windows security identifier (SID). When the installation of the disk image has completed, boot the PC. -

      20. +

      21. Log on to the machine as the local Administrator (the only option), and join the machine to the Domain, following the procedure set out in “A Collection of Useful Tidbits”, “Joining a Domain: Windows 200x/XP Professional”. The system is now ready for the user to log on, provided you have created a network logon account for that user, of course. -

      22. +

      23. Instruct all users to log on to the workstation using their assigned username and password. -

      Procedure 3.7. Windows Client Printer Preparation Procedure

      1. +

      Procedure 3.7. Windows Client Printer Preparation Procedure

      1. Click StartSettingsPrinters+Add Printer+Next. Do not click Network printer. Ensure that Local printer is selected. -

      2. +

      3. Click Next. In the Manufacturer: panel, select HP. In the Printers: panel, select the printer called HP LaserJet 6. Click Next. -

      4. +

      5. In the Available ports: panel, select FILE:. Accept the default printer name by clicking - Next. When asked, Would you like to print a - test page?, click No. Click + Next. When asked, “Would you like to print a + test page?,” click No. Click Finish. -

      6. +

      7. You may be prompted for the name of a file to print to. If so, close the dialog panel. Right-click HP LaserJet 6PropertiesDetails (Tab)Add Port. -

      8. +

      9. In the Network panel, enter the name of the print queue on the Samba server as follows: \\DIAMOND\hplj6a. Click OK+OK to complete the installation. -

      10. +

      11. Repeat the printer installation steps above for both HP LaserJet 6 printers as well as for both QMS Magicolor laser printers. -

    Key Points Learned

    +

    Key Points Learned

    How do you feel? You have built a capable network, a truly ambitious project. Future network updates can be handled by your staff. You must be a satisfied manager. Let's review the achievements. -

    • +

      • A simple firewall has been configured to protect the server in the event that the ISP firewall service should fail. -

      • +

      • The Samba configuration uses measures to ensure that only local network users can connect to SMB/CIFS services. -

      • +

      • Samba uses the new tdbsam passdb backend facility. Considerable complexity was added to Samba functionality. -

      • +

      • A DHCP server was configured to implement dynamic DNS (DDNS) updates to the DNS server. -

      • +

      • The DNS server was configured to permit DDNS only for local network clients. This server also provides primary DNS services for the company Internet presence. -

      • +

      • You introduced an application server as well as the concept of cloning a Windows client in order to effect improved standardization of desktops and to reduce the costs of network management. -

    Questions and Answers

    -

    1. +

    Questions and Answers

    +

    1. What is the maximum number of account entries that the tdbsam passdb backend can handle? -
    2. +
    2. Would Samba operate any better if the OS level is set to a value higher than 35? -
    3. +
    3. Why in this example have you provided UNIX group to Windows Group mappings for only Domain Groups? -
    4. +
    4. Why has a path been specified in the IPC$ share? -
    5. +
    5. Why does the smb.conf file in this exercise include an entry for smb ports? -
    6. +
    6. What is the difference between a print queue and a printer? -
    7. +
    7. Can all MS Windows application software be installed onto an application server share? -
    8. +
    8. Why use dynamic DNS (DDNS)? -
    9. +
    9. Why would you use WINS as well as DNS-based name resolution? -
    10. +
    10. What are the major benefits of using an application server? -

    1.

    +

    1.

    What is the maximum number of account entries that the tdbsam passdb backend can handle?

    @@ -1757,26 +1757,26 @@ at which most networks tend to want backup domain controllers (BDCs). Samba-3 does not provide a mechanism for replicating tdbsam data so it can be used by a BDC. The limitation of 250 users per tdbsam is predicated only on the need for replication, - not on the limits[8] of the tdbsam backend itself. -

    2.

    + not on the limits[8] of the tdbsam backend itself. +

    2.

    Would Samba operate any better if the OS level is set to a value higher than 35?

    No. MS Windows workstations and servers do not use a value higher than 33. Setting this to a value of 35 already assures Samba of precedence over MS Windows products in browser elections. There is no gain to be had from setting this higher. -

    3.

    +

    3.

    Why in this example have you provided UNIX group to Windows Group mappings for only Domain Groups?

    At this time, Samba has the capacity to use only Domain Groups mappings. It is possible that at a later date Samba may make use of Windows Local Groups, as well as of the Active Directory special Groups. Proper operation requires Domain Groups to be mapped to valid UNIX groups. -

    4.

    +

    4.

    Why has a path been specified in the IPC$ share?

    This is done so that in the event that a software bug may permit a client connection to the IPC$ share to obtain access to the file system, it does so at a location that presents least risk. Under normal operation this type of paranoid step should not be necessary. The use of this parameter should not be necessary. -

    5.

    +

    5.

    Why does the smb.conf file in this exercise include an entry for smb ports?

    The default order by which Samba-3 attempts to communicate with MS Windows clients is via port 445 (the TCP port @@ -1785,7 +1785,7 @@ specifying the use of only port 139, the intent is to reduce unsuccessful service connection attempts. The result of this is improved network performance. Where Samba-3 is installed as an Active Directory Domain member, the default behavior is highly beneficial and should not be changed. -

    6.

    +

    6.

    What is the difference between a print queue and a printer?

    A printer is a physical device that is connected either directly to the network or to a computer @@ -1799,7 +1799,7 @@ print requests. When the data stream has been fully received, the input stream is closed, and the job is then submitted to a sequential print queue where the job is stored until the printer is ready to receive the job. -

    7.

    +

    7.

    Can all MS Windows application software be installed onto an application server share?

    Much older Windows software is not compatible with installation to and execution from @@ -1807,21 +1807,21 @@ be installed to an application server. Retail consumer versions of Microsoft Office XP Professional do not permit installation to an application server share and can be installed and used only to/from a local workstation hard disk. -

    8.

    +

    8.

    Why use dynamic DNS (DDNS)?

    When DDNS records are updated directly from the DHCP server, it is possible for network clients that are not NetBIOS-enabled, and thus cannot use WINS, to locate Windows clients via DNS. -

    9.

    +

    9.

    Why would you use WINS as well as DNS-based name resolution?

    WINS is to NetBIOS names as DNS is to fully qualified domain names (FQDN). The FQDN is - a name like myhost.mydomain.tld where tld + a name like “myhost.mydomain.tld” where tld means top-level domain. A FQDN is a longhand but easy-to-remember expression that may be up to 1024 characters in length and that represents an IP address. A NetBIOS name is always 16 characters long. The 16th character - is a name type indicator. A specific name type is registered[9] for each + is a name type indicator. A specific name type is registered[9] for each type of service that is provided by the Windows server or client and that may be registered where a WINS server is in use.

    @@ -1836,24 +1836,24 @@ which it has control.

    Windows 200x Active Directory requires the registration in the DNS zone for the domain it - controls of service locator[10] records + controls of service locator[10] records that Windows clients and servers will use to locate Kerberos and LDAP services. ADS also requires the registration of special records that are called global catalog (GC) entries and site entries by which domain controllers and other essential ADS servers may be located. -

    10.

    +

    10.

    What are the major benefits of using an application server?

    The use of an application server can significantly reduce application update maintenance. By providing a centralized application share, software updates need be applied to only one location for all major applications used. This results in faster update roll-outs and significantly better application usage control. -



    [5] See TOSHARG2, Chapter 3. +



    [5] See TOSHARG2, Chapter 3. This is necessary so that Samba can act as a Domain Controller (PDC); see - TOSHARG2, Chapter 4, for additional information.

    [6] You may want to do the echo command last and include - "0" in the init scripts, since it opens up your network for a short time.

    [7] For more information regarding winbindd, see TOSHARG2, + TOSHARG2, Chapter 4, for additional information.

    [6] You may want to do the echo command last and include + "0" in the init scripts, since it opens up your network for a short time.

    [7] For more information regarding winbindd, see TOSHARG2, Chapter 23, Section 23.3. The single instance of smbd is normal. One additional smbd slave process is spawned for each SMB/CIFS client - connection.

    [8] Bench tests have shown that tdbsam is a very + connection.

    [8] Bench tests have shown that tdbsam is a very effective database technology. There is surprisingly little performance loss even - with over 4000 users.

    [9] - See TOSHARG2, Chapter 9, for more information.

    [10] See TOSHARG2, Chapter 9, Section 9.3.3.

    + with over 4000 users.

    [9] + See TOSHARG2, Chapter 9, for more information.

    [10] See TOSHARG2, Chapter 9, Section 9.3.3.

    diff -u -r --new-file --exclude .svn --exclude CVS samba-3.3.10//docs/htmldocs/Samba3-ByExample/simple.html samba-3.3.11//docs/htmldocs/Samba3-ByExample/simple.html --- samba-3.3.10//docs/htmldocs/Samba3-ByExample/simple.html 2010-01-14 11:23:58.000000000 +0100 +++ samba-3.3.11//docs/htmldocs/Samba3-ByExample/simple.html 2010-02-22 16:53:36.000000000 +0100 @@ -1,13 +1,13 @@ -Chapter 1. No-Frills Samba Servers

    Chapter 1. No-Frills Samba Servers

    +Chapter 1. No-Frills Samba Servers

    Chapter 1. No-Frills Samba Servers

    This is the start of the real journey toward the successful deployment of Samba. For some this chapter is the end of the road because their needs will have been adequately met. For others, this chapter is the beginning of a journey that will take them well past the contents of this book. This book provides example configurations of, for the greater part, complete networking solutions. The intent of this book is to help you to get your Samba installation working with the least amount of pain and aggravation. -

    Introduction

    +

    Introduction

    This chapter lays the groundwork for understanding the basics of Samba operation. Instead of a bland technical discussion, each principle is demonstrated by way of a - real-world scenario for which a working solution[1] is fully described. + real-world scenario for which a working solution[1] is fully described.

    The practical exercises take you on a journey through a drafting office, a charity administration office, and an accounting office. You may choose to apply any or all of these exercises to your own environment. @@ -17,7 +17,7 @@ find much improved solutions compared with those presented here. By the time you complete this book, you should aim to be a Samba expert, so do attempt to find better solutions and try them as you work your way through the examples. -

    Assignment Tasks

    +

    Assignment Tasks

    Each case presented highlights different aspects of Windows networking for which a simple Samba-based solution can be provided. Each has subtly different requirements taken from real-world cases. The cases are briefly reviewed to cover important points. Instructions are based @@ -25,10 +25,10 @@

    This chapter has three assignments built around fictitious companies:

    -

    • A drafting office

    • A charity administration office

    • An accounting office

    +

    • A drafting office

    • A charity administration office

    • An accounting office

    Let's get started. -

    Drafting Office

    +

    Drafting Office

    Our fictitious company is called Abmas Design, Inc. This is a three-person computer-aided design (CAD) business that often has more work than can be handled. The business owner hires contract draftspeople from wherever he can. They bring their own @@ -38,15 +38,15 @@ plans that are stored on a central server one day per month. She knows how to upload plans from each machine. The files available from the server must remain read-only. Anyone should be able to access the plans at any time and without barriers or difficulty. -

    - +

    + Mr. Bob Jordan has asked you to install the new server as economically as possible. The central server has a Pentium-IV 1.6GHz CPU, 768MB RAM, a 20GB IDE boot drive, a 160GB IDE second disk to store plans, and a 100-base-T Ethernet card. You have already installed Red Hat Fedora CoreX and have upgraded Samba to version 3.0.20 using the RPM package that is provided from the Samba FTP sites. (Note: Fedora CoreX indicates your favorite version.) -

    +

    The four permanent drafting machines (Microsoft Windows workstations) have attached printers and plotters that are shared on a peer-to-peer basis by any and all network users. The intent is to continue to share printers in this manner. The three permanent staff work together with @@ -55,15 +55,15 @@ area is copied to the central server and the files are removed from the main weekly storage machine. The office works best with this arrangement and does not want to change anything. Old habits are too ingrained. -

    Dissection and Discussion

    - +

    Dissection and Discussion

    + The requirements for this server installation demand simplicity. An anonymous read-only file server adequately meets all needs. The network consultant determines how to upload all files from the weekly storage area to the server. This installation should focus only on critical aspects of the installation.

    It is not necessary to have specific users on the server. The site has a method for storing - all design files (plans). Each plan is stored in a directory that is named YYYYWW,[2] where + all design files (plans). Each plan is stored in a directory that is named YYYYWW,[2] where YYYY is the year, and WW is the week of the year. This arrangement allows work to be stored by week of year to preserve the filing technique the site is familiar with. There is also a customer directory that is alphabetically listed. At the top level are 26 @@ -73,24 +73,24 @@ plans to be located both by customer name and by the date the work was performed, without demanding the disk space that would be needed if a duplicate file copy were to be stored. The share containing the plans is called Plans. -

    Implementation

    +

    Implementation

    It is assumed that the server is fully installed and ready for installation and configuration of Samba 3.0.20 and any support files needed. All TCP/IP addresses have been hard-coded. In our case the IP address of the Samba server is 192.168.1.1 and the netmask is 255.255.255.0. The hostname of the server used is server. -

    Procedure 1.1. Samba Server Configuration

    1. +

      Procedure 1.1. Samba Server Configuration

      1. Download the Samba-3 RPM packages for Red Hat Fedora Core2 from the Samba FTP servers. -

      2. - - +

      3. + + Install the RPM package using either the Red Hat Linux preferred GUI tool or the rpm:

         root#  rpm -Uvh samba-3.0.20-1.i386.rpm
         

        -

      4. +

      5. Create a mount point for the file system that will be used to store all data files. You can create a directory called /plans:

        @@ -100,60 +100,60 @@
         			The 755 permissions on this directory (mount point) permit the owner to read, write,
         			and execute, and the group and everyone else to read and execute only.
         			

        - + Use Red Hat Linux system tools (refer to Red Hat instructions) to format the 160GB hard drive with a suitable file system. An Ext3 file system is suitable. Configure this drive to automatically mount using the /plans directory as the mount point. -

      6. +

      7. Install the smb.conf file shown in “Drafting Office smb.conf File” in the /etc/samba directory. -

        Example 1.1. Drafting Office smb.conf File

        # Global Parameters
        [global]
        workgroup = MIDEARTH
        security = SHARE
        [Plans]
        path = /plans
        read only = Yes
        guest ok = Yes


        -

      8. - +

        Example 1.1. Drafting Office smb.conf File

        # Global Parameters
        [global]
        workgroup = MIDEARTH
        security = SHARE
        [Plans]
        path = /plans
        read only = Yes
        guest ok = Yes


        +

      9. + Verify that the /etc/hosts file contains the following entry:

         192.168.1.1	server
         

        -

      10. - - - +

      11. + + + Use the standard system tool to start Samba and to configure it to restart automatically at every system reboot. For example,

         root#  chkconfig smb on
         root#  /etc/rc.d/init.d/smb restart
         

        -

      Procedure 1.2. Windows Client Configuration

      1. +

      Procedure 1.2. Windows Client Configuration

      1. Make certain that all clients are set to the same network address range as used for the Samba server. For example, one client might have an IP address 192.168.1.10. -

      2. - +

      3. + Ensure that the netmask used on the Windows clients matches that used for the Samba server. All clients must have the same netmask, such as 255.255.255.0. -

      4. - +

      5. + Set the workgroup name on all clients to MIDEARTH. -

      6. +

      7. Verify on each client that the machine called SERVER is visible in the Network Neighborhood, that it is possible to connect to it and see the share Plans, and that it is possible to open that share to reveal its contents. -

    Validation

    - +

    Validation

    + The first priority in validating the new Samba configuration should be to check that Samba answers on the loop-back interface. Then it is time to check that Samba answers its own name correctly. Last, check that a client can connect to the Samba server. -

    1. - - - +

      1. + + + To check the ability to access the smbd daemon services, execute the following:

        @@ -172,13 +172,13 @@
                 ---------          --------
                 MIDEARTH           SERVER 
         

        - - + + This indicates that Samba is able to respond on the loopback interface to a NULL connection. The -U% means send an empty username and an empty password. This command should be repeated after Samba has been running for 15 minutes. -

      2. +

      3. Now verify that Samba correctly handles being passed a username and password, and that it answers its own name. Execute the following:

        @@ -187,13 +187,13 @@
         			The output should be identical to the previous response. Samba has been
         			configured to ignore all usernames given; instead it uses the
         			guest account for all connections.
        -			

      4. - - +

      5. + + From the Windows 9x/Me client, launch Windows Explorer: [Desktop: right-click] Network Neighborhood+Explore[Left Panel] [+] Entire Network[Left Panel] [+] Server[Left Panel] [+] Plans. In the right panel you should see the files and directories (folders) that are in the Plans share. -

    Charity Administration Office

    +

    Charity Administration Office

    The fictitious charity organization is called Abmas Vision NL. This office has five networked computers. Staff are all volunteers, staff changes are frequent. Ms. Amy May, the director of operations, wants a no-hassle network. Anyone should be able to @@ -216,8 +216,8 @@ that if the share name is not in lowercase, the application claims it cannot find the file share.

    - - + + Printer handling in Samba results in a significant level of confusion. Samba presents to the MS Windows client only a print queue. The Samba smbd process passes a print job sent to it from the Windows client to the native UNIX printing system. The native @@ -231,7 +231,7 @@ to prevent leakage of confidential information. Only the five PCs owned by Abmas Vision NL are used on this network.

    - + The central server was donated by a local computer store. It is a dual processor Pentium-III server, has 1GB RAM, a 3-Ware IDE RAID Controller that has four 200GB IDE hard drives, and a 100-base-T network card. The office has 100-base-T permanent network connections that go to @@ -242,11 +242,11 @@ office and letter printing. Your recommendation to allow only the Linux server to print directly to the printers was accepted. You have supplied SUSE Enterprise Linux Server 9 and have upgraded Samba to version 3.0.20. -

    Dissection and Discussion

    - - - - +

    Dissection and Discussion

    + + + + This installation demands simplicity. Frequent turnover of volunteer staff indicates that a network environment that requires users to logon might be problematic. It is suggested that the best solution for this office would be one where the user can log onto any PC with any username @@ -258,26 +258,26 @@ access control lists (Posix type) cannot be written to any file or directory. This prevents an inadvertent ACL from overriding actual file permissions.

    - - - + + + This organization is a prime candidate for Share Mode security. The force user allows all files to be owned by the same user and group. In addition, it would not hurt to set SUID and set SGID shared directories. This means that all new files that are created, no matter who creates it, are owned by the owner or group of the directory in which they are created. For further information regarding the significance of the SUID/SGID settings, see “A Collection of Useful Tidbits”, “Effect of Setting File and Directory SUID/SGID Permissions Explained”.

    - - - - + + + + All client workstations print to a print queue on the server. This ensures that print jobs continue to print in the event that a user shuts down the workstation immediately after sending a job to the printer. Today, both Red Hat Linux and SUSE Linux use CUPS-based printing. Older Linux systems offered a choice between the LPRng printing system or CUPS. It appears, however, that CUPS has become the leading UNIX printing technology.

    - + The print queues are set up as Raw devices, which means that CUPS will not do intelligent print processing, and vendor-supplied drivers must be installed locally on the Windows clients. @@ -297,21 +297,21 @@ printer. In this example, therefore, the resource called PRINTQ really is just a print queue. The name of the print queue is representative of the device to which the print spooler delivers print jobs. -

    Implementation

    +

    Implementation

    It is assumed that the server is fully installed and ready for configuration of Samba 3.0.20 and for necessary support files. All TCP/IP addresses should be hard-coded. In our case, the IP address of the Samba server is 192.168.1.1 and the netmask is 255.255.255.0. The hostname of the server used is server. The office network is built as shown in “Charity Administration Office Network”. -

    Figure 1.1. Charity Administration Office Network

    Charity Administration Office Network

    Procedure 1.3. Samba Server Configuration

    1. - +

      Figure 1.1. Charity Administration Office Network

      Charity Administration Office Network

      Procedure 1.3. Samba Server Configuration

      1. + Create a group account for office file storage:

         root#  groupadd office
         

        -

      2. - - +

      3. + + Create a user account for office file storage:

         root#  useradd -m abmas 
        @@ -322,13 +322,13 @@
         Password changed
         

        where XXXXXXXX is a secret password. -

      4. +

      5. Use the 3-Ware IDE RAID Controller firmware utilities to configure the four 200GB drives as a single RAID level 5 drive, with one drive set aside as the hot spare. (Refer to the 3-Ware RAID Controller Manual for the manufacturer's preferred procedure.) The resulting drive has a capacity of approximately 500GB of usable space. -

      6. - +

      7. + Create a mount point for the file system that can be used to store all data files. Create a directory called /data:

        @@ -337,12 +337,12 @@
         

        The 755 permissions on this directory (mount point) permit the owner to read, write, and execute, and the group and everyone else to read and execute only. -

      8. +

      9. Use SUSE Linux system tools (refer to the SUSE Administrators Guide for correct procedures) to format the partition with a suitable file system. The reiserfs file system is suitable. Configure this drive to automount using the /data directory as the mount point. It must be mounted before proceeding. -

      10. +

      11. Under the directory called /data, create two directories named ftmfiles and officefiles, and set ownership and permissions: @@ -360,7 +360,7 @@ /data/officefiles/invitations /data/officefiles/misc

        - + The chown operation sets the owner to the user abmas and the group to office on all directories just created. It recursively sets the permissions so that the owner and group have SUID/SGID with read, write, and execute @@ -368,9 +368,9 @@ directories are created with the same owner and group as the directory in which they are created. Any new directories created still have the same owner, group, and permissions as the directory they are in. This should eliminate all permissions-based file access problems. For - more information on this subject, refer to TOSHARG2[3] or refer + more information on this subject, refer to TOSHARG2[3] or refer to the UNIX man page for the chmod and the chown commands. -

      12. +

      13. Install the smb.conf file shown in “Charity Administration Office smb.conf New-style File” in the /etc/samba directory. This newer smb.conf file uses user-mode security and is more suited to the mode of operation of Samba-3 than the older share-mode security @@ -379,82 +379,82 @@ Note: If you want to use the older-style configuration that uses share-mode security, you can install the file shown in “Charity Administration Office smb.conf Old-style File” in the /etc/samba directory. -

      14. - +

      15. + We must ensure that the smbd can resolve the name of the Samba server to its IP address. Verify that the /etc/hosts file contains the following entry:

         192.168.1.1	server
         

        -

      16. +

      17. Configure the printers with the IP address as shown in “Charity Administration Office Network”. Follow the instructions in the manufacturer's manual to permit printing to port 9100 so that the CUPS spooler can print using raw mode protocols. -

      18. - +

      19. + Configure the CUPS Print Queues:

         root#  lpadmin -p PRINTQ -v socket://192.168.1.20:9100 -E
         root#  lpadmin -p hplj5 -v socket://192.168.1.30:9100 -E
         

        This creates the necessary print queues with no assigned print filter. -

      20. - - - +

      21. + + + Edit the file /etc/cups/mime.convs to uncomment the line:

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

        -

      22. - +

      23. + Edit the file /etc/cups/mime.types to uncomment the line:

         application/octet-stream
         

        -

      24. - +

      25. + Use the standard system tool to start Samba and CUPS to configure them to restart automatically at every system reboot. For example,

        - - - + + +

         root#  chkconfig smb on
         root#  chkconfig cups on
         root#  /etc/rc.d/init.d/smb restart
         root#  /etc/rc.d/init.d/cups restart
         

        -

      Example 1.2. Charity Administration Office smb.conf New-style File

      # Global Parameters - Newer Configuration
      [global]
      workgroup = MIDEARTH
      printing = CUPS
      printcap name = CUPS
      map to guest = Bad User
      show add printer wizard = No
      wins support = yes
      [FTMFILES]
      comment = Funds Tracking & Management Files
      path = /data/ftmfiles
      read only = No
      force user = abmas
      force group = office
      guest ok = Yes
      nt acl support = No
      [office]
      comment = General Office Files
      path = /data/officefiles
      read only = No
      force user = abmas
      force group = office
      guest ok = Yes
      nt acl support = No
      [printers]
      comment = Print Temporary Spool Configuration
      path = /var/spool/samba
      printable = Yes
      guest ok = Yes
      use client driver = Yes
      browseable = No

      Example 1.3. Charity Administration Office smb.conf Old-style File

      # Global Parameters - Older Style Configuration
      [global]
      workgroup = MIDEARTH
      security = SHARE
      printing = CUPS
      printcap name = CUPS
      disable spoolss = Yes
      show add printer wizard = No
      wins support = yes
      [FTMFILES]
      comment = Funds Tracking & Management Files
      path = /data/ftmfiles
      read only = No
      force user = abmas
      force group = office
      guest ok = Yes
      nt acl support = No
      [office]
      comment = General Office Files
      path = /data/officefiles
      read only = No
      force user = abmas
      force group = office
      guest ok = Yes
      nt acl support = No
      [printers]
      comment = Print Temporary Spool Configuration
      path = /var/spool/samba
      printable = Yes
      guest ok = Yes
      use client driver = Yes
      browseable = No

      Procedure 1.4. Windows Client Configuration

      1. +

      Example 1.2. Charity Administration Office smb.conf New-style File

      # Global Parameters - Newer Configuration
      [global]
      workgroup = MIDEARTH
      printing = CUPS
      printcap name = CUPS
      map to guest = Bad User
      show add printer wizard = No
      wins support = yes
      [FTMFILES]
      comment = Funds Tracking & Management Files
      path = /data/ftmfiles
      read only = No
      force user = abmas
      force group = office
      guest ok = Yes
      nt acl support = No
      [office]
      comment = General Office Files
      path = /data/officefiles
      read only = No
      force user = abmas
      force group = office
      guest ok = Yes
      nt acl support = No
      [printers]
      comment = Print Temporary Spool Configuration
      path = /var/spool/samba
      printable = Yes
      guest ok = Yes
      use client driver = Yes
      browseable = No

      Example 1.3. Charity Administration Office smb.conf Old-style File

      # Global Parameters - Older Style Configuration
      [global]
      workgroup = MIDEARTH
      security = SHARE
      printing = CUPS
      printcap name = CUPS
      disable spoolss = Yes
      show add printer wizard = No
      wins support = yes
      [FTMFILES]
      comment = Funds Tracking & Management Files
      path = /data/ftmfiles
      read only = No
      force user = abmas
      force group = office
      guest ok = Yes
      nt acl support = No
      [office]
      comment = General Office Files
      path = /data/officefiles
      read only = No
      force user = abmas
      force group = office
      guest ok = Yes
      nt acl support = No
      [printers]
      comment = Print Temporary Spool Configuration
      path = /var/spool/samba
      printable = Yes
      guest ok = Yes
      use client driver = Yes
      browseable = No

      Procedure 1.4. Windows Client Configuration

      1. Configure clients to the network settings shown in “Charity Administration Office Network”. -

      2. +

      3. Ensure that the netmask used on the Windows clients matches that used for the Samba server. All clients must have the same netmask, such as 255.255.255.0. -

      4. - +

      5. + On all Windows clients, set the WINS Server address to 192.168.1.1, the IP address of the server. -

      6. +

      7. Set the workgroup name on all clients to MIDEARTH. -

      8. - - Install the Client for Microsoft Networks. Ensure that the only option - enabled in its properties is the option Logon and restore network connections. -

      9. +

      10. + + Install the “Client for Microsoft Networks.” Ensure that the only option + enabled in its properties is the option “Logon and restore network connections.” +

      11. Click OK when you are prompted to reboot the system. Reboot the system, then log on using any username and password you choose. -

      12. - +

      13. + Verify on each client that the machine called SERVER is visible in My Network Places, that it is possible to connect to it and see the share office, and that it is possible to open that share to reveal its contents. -

      14. - - +

      15. + + Disable password caching on all Windows 9x/Me machines using the registry change file shown in “Windows Me Registry Edit File: Disable Password Caching”. Be sure to remove all files that have the PWL extension that are in the C:\WINDOWS @@ -471,70 +471,70 @@

         C:\WINDOWS: regedit ME-dpwc.reg
         

        -

      16. +

      17. Instruct all users to log onto the workstation using a name and password of their own choosing. The Samba server has been configured to ignore the username and password given. -

      18. +

      19. On each Windows Me workstation, configure a network drive mapping to drive G: that redirects to the uniform naming convention (UNC) resource \\server\office. Make this a permanent drive connection: -

        1. +

          1. My NetworkMap Network Drive... -

          2. - In the box labeled Drive:, type G. -

          3. - In the box labeled Path:, enter +

          4. + In the box labeled “Drive:”, type G. +

          5. + In the box labeled “Path:”, enter \\server\officefiles. -

          6. +

          7. Click Reconnect at logon. Click OK. -

        2. +

      20. On each workstation, install the FTM software following the manufacturer's instructions. -

        1. +

          1. During installation, you are prompted for the name of the Windows 98 server. Enter the name SERVER. -

          2. +

          3. You are prompted for the name of the data share. The prompt defaults to FTMFILES. Press enter to accept the default value. -

          4. +

          5. You are now prompted for the print queue name. The default prompt is the name of the server you entered (SERVER as follows: \\SERVER\PRINTQ). Simply accept the default and press enter to continue. The software now completes the installation. -

        2. +

      21. Install an office automation software package of the customer's choice. Either Microsoft Office 2003 Standard or OpenOffice 1.1.0 suffices for any functions the office may need to perform. Repeat this on each workstation. -

      22. +

      23. Install a printer on each workstation using the following steps: -

        1. +

          1. Click StartSettingsPrinters+Add Printer+Next. Do not click Network printer. Ensure that Local printer is selected. -

          2. +

          3. Click Next. In the Manufacturer: panel, select HP. In the Printers: panel, select the printer called HP LaserJet 5/5M Postscript. Click Next. -

          4. +

          5. In the Available ports: panel, select FILE:. Accept the default printer name by clicking Next. When asked, - Would you like to print a test page?, click + “Would you like to print a test page?”, click No. Click Finish. -

          6. +

          7. You may be prompted for the name of a file to print to. If so, close the dialog panel. Right-click HP LaserJet 5/5M PostscriptPropertiesDetails (Tab)Add Port. -

          8. +

          9. In the Network panel, enter the name of the print queue on the Samba server as follows: \\SERVER\hplj5. Click OK+OK to complete the installation. -

          10. +

          11. It is a good idea to test the functionality of the complete installation before handing the newly configured network over to the Charity Administration Office for production use. -

      Validation

      +

    Validation

    Use the same validation process as was followed in “Validation”. -

    Accounting Office

    +

    Accounting Office

    Abmas Accounting is a 40-year-old family-run business. There are nine permanent computer users. The network clients were upgraded two years ago. All computers run Windows 2000 Professional. This year the server will be upgraded from an old Windows NT4 server (actually @@ -551,18 +551,18 @@ and enter an assigned password; they do not need to enter a password when accessing their files on the server.

    - + The new server will run Red Hat Fedora Core2. You should install Samba-3.0.20 and copy all files from the old system to the new one. The existing Windows NT4 server has a parallel port HP LaserJet 4 printer that is shared by all. The printer driver is installed on each workstation. You must not change anything on the workstations. Mr. Meany gave instructions to - replace the server, but leave everything else alone to avoid staff unrest. + replace the server, “but leave everything else alone to avoid staff unrest.

    You have tried to educate Mr. Meany and found that he has no desire to understand networking. - He believes that Windows for Workgroups 3.11 was the best server Microsoft ever sold - and that Windows NT and 2000 are too fang-dangled complex! -

    Dissection and Discussion

    - + He believes that Windows for Workgroups 3.11 was “the best server Microsoft ever sold + ” and that Windows NT and 2000 are “too fang-dangled complex!” +

    Dissection and Discussion

    + The requirements of this network installation are not unusual. The staff are not interested in the details of networking. Passwords are never changed. In this example solution, we demonstrate the use of User Mode security in a simple context. Directories should be set SGID to ensure that members @@ -573,7 +573,7 @@

    You have finished configuring the new hardware and have just completed installation of Red Hat Fedora Core2. Roll up your sleeves and let's get to work. -

    Implementation

    +

    Implementation

    The workstations have fixed IP addresses. The old server runs Windows NT4 Workstation, so it cannot be running as a WINS server. It is best that the new configuration preserves the same configuration. The office does not use Internet access, so security really is not an issue. @@ -582,30 +582,30 @@ share name is given in “Accounting Office Network Information”. The overall network topology is shown in “Accounting Office Network Topology”. All machines have been configured as indicated prior to the start of Samba configuration. The following prescriptive steps may now commence. -

    Figure 1.2. Accounting Office Network Topology

    Accounting Office Network Topology

    Table 1.1. Accounting Office Network Information

    UserLogin-IDPasswordShare NameDirectoryWkst
    Alan Meanyalanalm1961alan/dataPC1
    James Meanyjamesjimm1962james/data/jamesPC2
    Jeannie Meanyjeanniejema1965jeannie/data/jeanniePC3
    Suzy Millicentsuzysuzy1967suzy/data/suzyPC4
    Ursula Jenningujenujen1974ursula/data/ursulaPC5
    Peter Panpeterpete1984peter/data/peterPC6
    Dale Rolanddaledale1986dale/data/dalePC7
    Bertrand E Paolettiericeric1993eric/data/ericPC8
    Russell Lewisrussruss2001russell/data/russellPC9

    Procedure 1.5. Migration from Windows NT4 Workstation System to Samba-3

    1. +

      Figure 1.2. Accounting Office Network Topology

      Accounting Office Network Topology

      Table 1.1. Accounting Office Network Information

      UserLogin-IDPasswordShare NameDirectoryWkst
      Alan Meanyalanalm1961alan/dataPC1
      James Meanyjamesjimm1962james/data/jamesPC2
      Jeannie Meanyjeanniejema1965jeannie/data/jeanniePC3
      Suzy Millicentsuzysuzy1967suzy/data/suzyPC4
      Ursula Jenningujenujen1974ursula/data/ursulaPC5
      Peter Panpeterpete1984peter/data/peterPC6
      Dale Rolanddaledale1986dale/data/dalePC7
      Bertrand E Paolettiericeric1993eric/data/ericPC8
      Russell Lewisrussruss2001russell/data/russellPC9

      Procedure 1.5. Migration from Windows NT4 Workstation System to Samba-3

      1. Rename the old server from CASHPOOL to STABLE by logging onto the console as the Administrator. Restart the machine following system prompts. -

      2. +

      3. Name the new server CASHPOOL using the standard configuration method. Restart the machine following system prompts. -

      4. +

      5. Install the latest Samba-3 binary Red Hat Linux RPM that is available from the Samba FTP site. -

      6. - - +

      7. + + Add a group account for the office to use. Execute the following:

         root#  groupadd accts
         

        -

      8. - Install the smb.conf file shown[4] +

      9. + Install the smb.conf file shown[4] in “Accounting Office Network smb.conf Old Style Configuration File”. -

      10. - - - +

      11. + + + For each user who uses this system (see “Accounting Office Network Information”), execute the following:

        @@ -619,8 +619,8 @@
         Retype new SMB password: XXXXXXXXX
         Added user "LoginID"
         

        -

      12. - +

      13. + Create the directory structure for the file shares by executing the following:

         root#  mkdir -p /data
        @@ -634,59 +634,59 @@
         root#  chmod -R ug+rwxs,o-r+x /data
         

        The data storage structure is now prepared for use. -

      14. - +

      15. + Configure the CUPS Print Queues:

         root#  lpadmin -p hplj -v parallel:/dev/lp0 -E
         

        This creates the necessary print queues with no assigned print filter. -

      16. - - +

      17. + + Edit the file /etc/cups/mime.convs to uncomment the line:

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

        -

      18. - - +

      19. + + Edit the file /etc/cups/mime.types to uncomment the line:

         application/octet-stream
         

        -

      20. - +

      21. + Use the standard system tool to start Samba and CUPS to configure them to restart automatically at every system reboot. For example,

        - - - + + +

         root#  chkconfig smb on
         root#  chkconfig cups on
         root#  /etc/rc.d/init.d/smb restart
         root#  /etc/rc.d/init.d/cups restart
         

        -

      22. +

      23. On Alan's workstation, use Windows Explorer to migrate the files from the old server to the new server. The new server should appear in the Network Neighborhood with the name of the old server (CASHPOOL). -

        1. +

          1. Log on to Alan's workstation as the user alan. -

          2. +

          3. Launch a second instance of Windows Explorer and navigate to the share called files on the server called STABLE. -

          4. +

          5. Click in the right panel, and press Ctrl-A to select all files and directories. Press Ctrl-C to instruct Windows that you wish to copy all selected items. -

          6. +

          7. Launch the Windows Explorer, and navigate to the share called files on the server called CASHPOOL. Click in the right panel, and then press Ctrl-V to commence the copying process. -

        2. +

      24. Verify that the files are being copied correctly from the Windows NT4 machine to the Samba-3 server. This is best done on the Samba-3 server. Check the contents of the directory tree under /data by executing the following command: @@ -703,44 +703,44 @@ root# chgrp -R accts /data root# chmod -R ug+rwxs,o-r+x /data

        -

      25. +

      26. The migration of all data should now be complete. It is time to validate the installation. For this, you should make sure all applications, including printing, work before asking the customer to test drive the new network. -

      Example 1.5. Accounting Office Network smb.conf Old Style Configuration File

      # Global parameters
      [global]
      workgroup = BILLMORE
      printcap name = CUPS
      disable spoolss = Yes
      show add printer wizard = No
      printing = cups
      [files]
      comment = Work area files
      path = /data/%U
      read only = No
      [master]
      comment = Master work area files
      path = /data
      valid users = alan
      read only = No
      [printers]
      comment = Print Temporary Spool Configuration
      path = /var/spool/samba
      printable = Yes
      guest ok = Yes
      use client driver = Yes
      browseable = No

    Questions and Answers

    +

    Example 1.5. Accounting Office Network smb.conf Old Style Configuration File

    # Global parameters
    [global]
    workgroup = BILLMORE
    printcap name = CUPS
    disable spoolss = Yes
    show add printer wizard = No
    printing = cups
    [files]
    comment = Work area files
    path = /data/%U
    read only = No
    [master]
    comment = Master work area files
    path = /data
    valid users = alan
    read only = No
    [printers]
    comment = Print Temporary Spool Configuration
    path = /var/spool/samba
    printable = Yes
    guest ok = Yes
    use client driver = Yes
    browseable = No

    Questions and Answers

    The following questions and answers draw from the examples in this chapter. Many design decisions are impacted by the configurations chosen. The intent is to expose some of the hidden implications. -

    +

    What makes an anonymous Samba server more simple than a non-anonymous Samba server? -
    +
    How is the operation of the parameter force user different from setting the root directory of the share SUID? -
    +
    When would you both use the per share parameter force user and set the share root directory SUID? -
    +
    What is better about CUPS printing than LPRng printing? -
    +
    When should Windows client IP addresses be hard-coded? -
    +
    Under what circumstances is it best to use a DHCP server? -
    +
    What is the purpose of setting the parameter guest ok on a share? -
    +
    When would you set the global parameter disable spoolss? -
    +
    Why would you disable password caching on Windows 9x/Me clients? -
    +
    The example of Abmas Accounting uses User Mode security. How does this provide anonymous access? -

    +

    What makes an anonymous Samba server more simple than a non-anonymous Samba server?

    In the anonymous server, the only account used is the guest account. In a non-anonymous configuration, it is necessary to add real user accounts to both the UNIX system and to the Samba configuration. Non-anonymous servers require additional administration. -

    +

    How is the operation of the parameter force user different from setting the root directory of the share SUID?

    @@ -754,14 +754,14 @@

    The parameter force user has potential security implications that go beyond the actual share root directory. Be careful and wary of using this parameter. -

    +

    When would you both use the per share parameter force user and set the share root directory SUID?

    You would use both parameters when it is necessary to guarantee that all share handling operations are conducted as the forced user, while all file and directory creation are done as the SUID directory owner. -

    +

    What is better about CUPS printing than LPRng printing?

    CUPS is a print spooling system that has integrated remote management facilities, provides completely @@ -779,7 +779,7 @@

    Which spooling system is better is a matter of personal taste. It depends on what you want to do and how you want to do it and manage it. Most modern Linux systems ship with CUPS as the default print management system. -

    +

    When should Windows client IP addresses be hard-coded?

    When there are few MS Windows clients, little client change, no mobile users, and users are not @@ -788,7 +788,7 @@ user ability to access network configuration controls, fixed configuration eliminates the need for a DHCP server. This reduces maintenance overheads and eliminates a possible point of network failure. -

    +

    Under what circumstances is it best to use a DHCP server?

    In network configurations where there are mobile users, or where Windows client PCs move around @@ -804,12 +804,12 @@ Another benefit of modern DHCP servers is their ability to register dynamically assigned IP addresses with the DNS server. The benefits of Dynamic DNS (DDNS) are considerable in a large Windows network environment. -

    +

    What is the purpose of setting the parameter guest ok on a share?

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

    +

    When would you set the global parameter disable spoolss?

    Setting this parameter to Yes disables Samba's support for the SPOOLSS set of @@ -830,17 +830,17 @@ considers the printer to be local, it attempts to issue the OpenPrinterEx() call requesting access rights associated with the logged on user. If the user possesses local administrator rights but not root privilege on the Samba host (often the case), the OpenPrinterEx() call fails. The result is - that the client now displays an Access Denied; Unable to connect message in the printer queue window + that the client now displays an “Access Denied; Unable to connect” message in the printer queue window (even though jobs may be printed successfully). This parameter MUST not be enabled on a print share that has a valid print driver installed on the Samba server. -

    +

    Why would you disable password caching on Windows 9x/Me clients?

    Windows 9x/Me workstations that are set at default (password caching enabled) store the username and password in files located in the Windows master directory. Such files can be scavenged (read off a client machine) and decrypted, thus revealing the user's access credentials for all systems the user may have accessed. It is most insecure to allow any Windows 9x/Me client to operate with password caching enabled. -

    +

    The example of Abmas Accounting uses User Mode security. How does this provide anonymous access?

    The example used does not provide anonymous access. Since the clients are all Windows 2000 Professional, @@ -848,14 +848,14 @@ a remote server using currently logged in user credentials. By ensuring that the user's login ID and password are the same as those set on the Samba server, access is transparent and does not require separate user authentication. -



    [1] The examples given mirror those documented +



    [1] The examples given mirror those documented in The Official Samba-3 HOWTO and Reference Guide, Second Edition (TOSHARG2) Chapter 2, Section 2.3.1. You may gain additional insight from the standalone server configurations covered in TOSHARG2, sections 2.3.1.2 through 2.3.1.4. -

    [2] +

    [2] This information is given purely as an example of how data may be stored in such a way that it will be easy to locate records at a later date. The example is not meant to imply any instructions that may be construed as essential to the design of the solution; this is something you will almost - certainly want to determine for yourself.

    [4] This example uses the + certainly want to determine for yourself.

    [4] This example uses the smbpasswd file in an obtuse way, since the use of the passdb backend has not been specified in the smb.conf file. This means that you are depending on correct default behavior.

    diff -u -r --new-file --exclude .svn --exclude CVS samba-3.3.10//docs/htmldocs/Samba3-ByExample/small.html samba-3.3.11//docs/htmldocs/Samba3-ByExample/small.html --- samba-3.3.10//docs/htmldocs/Samba3-ByExample/small.html 2010-01-14 11:23:59.000000000 +0100 +++ samba-3.3.11//docs/htmldocs/Samba3-ByExample/small.html 2010-02-22 16:53:36.000000000 +0100 @@ -1,4 +1,4 @@ -Chapter 2. Small Office Networking

    Chapter 2. Small Office Networking

    +Chapter 2. Small Office Networking

    Chapter 2. Small Office Networking

    “No-Frills Samba Servers” focused on the basics of simple yet effective network solutions. Network administrators who take pride in their work (that's most of us, right?) take care to deliver what our users want, @@ -8,7 +8,7 @@ operates. Some creativity is helpful, but keep it under control good advice that the following two scenarios illustrate.

    - + In one case the network administrator of a mid-sized company spent three months building a new network to replace an old Netware server. What he delivered had all the bells and whistles he could muster. There were a @@ -33,10 +33,10 @@ features, and yet he had happy users. Months later he was still adding new innovations. He always asked the users if a particular feature was what they wanted. He asked his boss for a raise - and got it. He often told me, Always keep a few new tricks up your - sleeves for when you need them. Was he smart? You decide. Let's + and got it. He often told me, “Always keep a few new tricks up your + sleeves for when you need them.” Was he smart? You decide. Let's get on with our next exercise. -

    Introduction

    +

    Introduction

    Abmas Accounting has grown. Mr. Meany likes you and says he knew you were the right person for the job. That's why he asked you to install the new server. The past few months have been hard work. You advised Mr. Meany @@ -47,8 +47,8 @@ Some of the Windows clients are nearly past their use-by date. You found damaged and unusable software on some of the workstations that came with the acquired business and found some machines in need of both hardware and software maintenance. -

    Assignment Tasks

    - +

    Assignment Tasks

    + Mr. Meany is retiring in 12 months. Before he goes, he wants you to help ensure that the business is running efficiently. Many of the new staff want notebook computers. They visit customer business premises and need to use local network @@ -80,28 +80,28 @@ Mr. Meany also asked if it would be possible for one of the staff to manage user accounts from the Windows desktop. That person will be responsible for basic operations. -

    Dissection and Discussion

    +

    Dissection and Discussion

    What are the key requirements in this business example? A quick review indicates a need for -

    • +

      • Scalability, from 52 to over 100 users in 12 months -

      • +

      • Mobile computing capability - -

      • + +

      • Improved reliability and usability -

      • +

      • Easier administration

      In this instance the installed Linux system is assumed to be a Red Hat Linux Fedora Core2 server (as in “Accounting Office”). -

      Technical Issues

      - - - - - +

      Technical Issues

      + + + + + It is time to implement a domain security environment. You will use the smbpasswd (default) backend. You should implement a DHCP server. There is no need to run DNS at this time, but the system will use WINS. The domain name will be @@ -110,7 +110,7 @@ All printers will be configured as DHCP clients. The DHCP server will assign the printer a fixed IP address by way of its Ethernet interface (MAC) address. See “Abmas Accounting DHCP Server Configuration File /etc/dhcpd.conf”. -

      Note

      +

      Note

      The smb.conf file you are creating in this exercise can be used with equal effectiveness with Samba-2.2.x series releases. This is deliberate so that in the next chapter it is possible to start with the installation that you have created here, migrate it @@ -122,7 +122,7 @@ Later on, when the Internet connection is implemented, you will add DNS as well as other enhancements. It is important that you plan accordingly.

      - + You have split the network into two separate areas. Each has its own Ethernet switch. There are 20 users on the accounting network and 32 users on the financial services network. The server has two network interfaces, one serving each network. The @@ -137,8 +137,8 @@ Given that DNS will not be used, you will configure WINS name resolution for UNIX hostname name resolution.

      - - + + It is necessary to map Windows Domain Groups to UNIX groups. It is advisable to also map Windows Local Groups to UNIX groups. Additionally, the two key staff groups in the firm are accounting staff and financial services staff. @@ -155,10 +155,10 @@ TOSHARG2, Chapter 11, Section 11.3.1, Example 11.1, for more information.

      - + Vendor-supplied printer drivers will be installed on each client. The CUPS print spooler on the UNIX host will be operated in raw mode. -

      Political Issues

      +

      Political Issues

      Mr. Meany is an old-school manager. He sets the rules and wants to see compliance. He is willing to spend money on things he believes are of value. You need more time to convince him of real priorities. @@ -166,8 +166,8 @@ Go ahead, buy better notebooks. Wouldn't it be neat if they happened to be supplied with antivirus software? Above all, demonstrate good purchase value and remember to make your users happy. -

      Implementation

      - +

      Implementation

      + In this example, the assumption is made that this server is being configured from a clean start. The alternate approach could be to demonstrate the migration of the system that is documented in “Implementation” to meet the new requirements. The decision to treat this case, as with @@ -175,23 +175,23 @@ the migration steps from the information provided in “Migrating NT4 Domain to Samba-3”. Additionally, a fresh installation makes the example easier to follow.

      - + Each user will be given a home directory on the UNIX system, which will be available as a private share. Two additional shares will be created, one for the accounting department and the other for the financial services department. Network users will be given access to these shares by way of group membership.

      - + UNIX group membership is the primary mechanism by which Windows Domain users will be granted rights and privileges within the Windows environment.

      - + The user alanm will be made the owner of all files. This will be preserved by setting the sticky bit (set UID/GID) on the top-level directories. -

      Figure 2.1. Abmas Accounting 52-User Network Topology

      Abmas Accounting 52-User Network Topology

      Procedure 2.1. Server Installation Steps

      1. +

        Figure 2.1. Abmas Accounting 52-User Network Topology

        Abmas Accounting 52-User Network Topology

        Procedure 2.1. Server Installation Steps

        1. Using UNIX/Linux system tools, name the server sleeth. -

        2. - +

        3. + Place an entry for the machine sleeth in the /etc/hosts. The printers are network attached, so there should be entries for the network printers also. An example /etc/hosts file is shown here: @@ -202,15 +202,15 @@ 192.168.1.11 hplj4 192.168.2.10 qms

          -

        4. +

        5. Install the Samba-3 binary RPM from the Samba-Team FTP site. -

        6. +

        7. Install the ISC DHCP server using the UNIX/Linux system tools available to you. -

        8. - - - - +

        9. + + + + Because Samba will be operating over two network interfaces and clients on each side may want to be able to reach clients on the other side, it is imperative that IP forwarding is enabled. Use the system tool of your choice to enable IP forwarding. In the @@ -220,12 +220,12 @@ echo 1 > /proc/sys/net/ipv4/ip_forward

          This causes the Linux kernel to forward IP packets so that it acts as a router. -

        10. +

        11. Install the smb.conf file as shown in “Accounting Office Network smb.conf File [globals] Section” and “Accounting Office Network smb.conf File Services and Shares Section”. Combine these two examples to form a single /etc/samba/smb.conf file. -

        12. - +

        13. + Add the user root to the Samba password backend:

           root#  smbpasswd -a root
          @@ -233,13 +233,13 @@
           Retype new SMB password: XXXXXXX
           root# 
           

          - + This is the Windows Domain Administrator password. Never delete this account from the password backend after Windows Domain Groups have been initialized. If you delete this account, your system is crippled. You cannot restore this account, and your Samba server can no longer be administered. -

        14. - +

        15. + Create the username map file to permit the root account to be called Administrator from the Windows network environment. To do this, create the file /etc/samba/smbusers with the following contents: @@ -265,14 +265,14 @@ # End of File ####

          -

        16. - +

        17. + Create and map Windows Domain Groups to UNIX groups. A sample script is provided in “Script to Map Windows NT Groups to UNIX Groups”. Create a file containing this script. We called ours /etc/samba/initGrps.sh. Set this file so it can be executed, and then execute the script. Sample output should be as follows: -

          Example 2.1. Script to Map Windows NT Groups to UNIX Groups

          +

          Example 2.1. Script to Map Windows NT Groups to UNIX Groups

           #!/bin/bash
           #
           # initGrps.sh
          @@ -321,31 +321,31 @@
           System Operators (S-1-5-32-549) -> -1
           Users (S-1-5-32-545) -> -1
           

          -

        18. - - - +

        19. + + + For each user who needs to be given a Windows Domain account, make an entry in the /etc/passwd file as well as in the Samba password backend. Use the system tool of your choice to create the UNIX system accounts, and use the Samba smbpasswd program to create the Domain user accounts.

          - - - + + + There are a number of tools for user management under UNIX, such as useradd and adduser, as well as a plethora of custom tools. With the tool of your choice, create a home directory for each user. -

        20. +

        21. Using the preferred tool for your UNIX system, add each user to the UNIX groups created previously, as necessary. File system access control will be based on UNIX group membership. -

        22. +

        23. Create the directory mount point for the disk subsystem that is mounted to provide data storage for company files. In this case the mount point is indicated in the smb.conf file is /data. Format the file system as required, mount the formatted file system partition using mount, and make the appropriate changes in /etc/fstab. -

        24. +

        25. Create the top-level file storage directories are follows:

           root#  mkdir -p /data/{accounts,finsvcs}
          @@ -357,42 +357,42 @@
           		Each department is responsible for creating its own directory structure within its
           		share. The directory root of the accounts share is /data/accounts.
           		The directory root of the finsvcs share is /data/finsvcs.
          -		

        26. +

        27. Configure the printers with the IP addresses as shown in “Abmas Accounting 52-User Network Topology”. Follow the instructions in the manufacturers' manuals to permit printing to port 9100. This allows the CUPS spooler to print using raw mode protocols. - - -

        28. - - + + +

        29. + + Configure the CUPS Print Queues as follows:

           root#  lpadmin -p hplj4 -v socket://192.168.1.11:9100 -E
           root#  lpadmin -p hplj6 -v socket://192.168.1.10:9100 -E
           root#  lpadmin -p qms -v socket://192.168.2.10:9100 -E
           

          - + This creates the necessary print queues with no assigned print filter. -

        30. - - - +

        31. + + + Edit the file /etc/cups/mime.convs to uncomment the line:

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

          -

        32. - +

        33. + Edit the file /etc/cups/mime.types to uncomment the line:

           application/octet-stream
           

          -

        34. - +

        35. + Using your favorite system editor, create an /etc/dhcpd.conf with the contents as shown in “Abmas Accounting DHCP Server Configuration File /etc/dhcpd.conf”. -

          Example 2.2. Abmas Accounting DHCP Server Configuration File /etc/dhcpd.conf

          +

          Example 2.2. Abmas Accounting DHCP Server Configuration File /etc/dhcpd.conf

           default-lease-time 86400;
           max-lease-time 172800;
           default-lease-time 86400;
          @@ -436,15 +436,15 @@
           subnet 127.0.0.0 netmask 255.0.0.0 {
           	}
           


          -

        36. +

        37. Use the standard system tool to start Samba and CUPS and configure them to start automatically at every system reboot. For example,

          - - - - - + + + + +

           root#  chkconfig dhcp on
           root#  chkconfig smb on
          @@ -453,13 +453,13 @@
           root#  /etc/rc.d/init.d/smb restart
           root#  /etc/rc.d/init.d/cups restart
           

          -

        38. - - - - - - +

        39. + + + + + + Configure the name service switch (NSS) to handle WINS-based name resolution. Since this system does not use a DNS server, it is safe to remove this option from the NSS configuration. Edit the /etc/nsswitch.conf file so that @@ -467,11 +467,11 @@

           hosts:	files wins
           

          -

        Example 2.3. Accounting Office Network smb.conf File [globals] Section

        # Global parameters
        [global]
        workgroup = BILLMORE
        passwd chat = *New*Password* %n\n*Re-enter*new*password* %n\n *Password*changed*
        username map = /etc/samba/smbusers
        syslog = 0
        name resolve order = wins bcast hosts
        printcap name = CUPS
        show add printer wizard = No
        add user script = /usr/sbin/useradd -m -G users '%u'
        delete user script = /usr/sbin/userdel -r '%u'
        add group script = /usr/sbin/groupadd '%g'
        delete group script = /usr/sbin/groupdel '%g'
        add user to group script = /usr/sbin/usermod -A '%g' '%u'
        add machine script = /usr/sbin/useradd -s /bin/false -d /var/lib/nobody '%u'
        logon script = scripts\login.bat
        logon path =
        logon drive = X:
        domain logons = Yes
        preferred master = Yes
        wins support = Yes
        printing = CUPS

        Example 2.4. Accounting Office Network smb.conf File Services and Shares Section

        [homes]
        comment = Home Directories
        valid users = %S
        read only = No
        browseable = No
        [printers]
        comment = SMB Print Spool
        path = /var/spool/samba
        printable = Yes
        guest ok = Yes
        use client driver = Yes
        browseable = No
        [netlogon]
        comment = Network Logon Service
        path = /data/%U
        valid users = %S
        read only = No
        [accounts]
        comment = Accounting Files
        path = /data/accounts
        valid users = %G
        read only = No
        [finsvcs]
        comment = Financial Service Files
        path = /data/finsvcs
        valid users = %G
        read only = No

        Validation

        +

      Example 2.3. Accounting Office Network smb.conf File [globals] Section

      # Global parameters
      [global]
      workgroup = BILLMORE
      passwd chat = *New*Password* %n\n*Re-enter*new*password* %n\n *Password*changed*
      username map = /etc/samba/smbusers
      syslog = 0
      name resolve order = wins bcast hosts
      printcap name = CUPS
      show add printer wizard = No
      add user script = /usr/sbin/useradd -m -G users '%u'
      delete user script = /usr/sbin/userdel -r '%u'
      add group script = /usr/sbin/groupadd '%g'
      delete group script = /usr/sbin/groupdel '%g'
      add user to group script = /usr/sbin/usermod -A '%g' '%u'
      add machine script = /usr/sbin/useradd -s /bin/false -d /var/lib/nobody '%u'
      logon script = scripts\login.bat
      logon path =
      logon drive = X:
      domain logons = Yes
      preferred master = Yes
      wins support = Yes
      printing = CUPS

      Example 2.4. Accounting Office Network smb.conf File Services and Shares Section

      [homes]
      comment = Home Directories
      valid users = %S
      read only = No
      browseable = No
      [printers]
      comment = SMB Print Spool
      path = /var/spool/samba
      printable = Yes
      guest ok = Yes
      use client driver = Yes
      browseable = No
      [netlogon]
      comment = Network Logon Service
      path = /data/%U
      valid users = %S
      read only = No
      [accounts]
      comment = Accounting Files
      path = /data/accounts
      valid users = %G
      read only = No
      [finsvcs]
      comment = Financial Service Files
      path = /data/finsvcs
      valid users = %G
      read only = No

      Validation

      Does everything function as it ought? That is the key question at this point. Here are some simple steps to validate your Samba server configuration. -

      Procedure 2.2. Validation Steps

      1. - +

        Procedure 2.2. Validation Steps

        1. + If your smb.conf file has bogus options or parameters, this may cause Samba to refuse to start. The first step should always be to validate the contents of this file by running: @@ -517,11 +517,11 @@ Ignoring unknown parameter "dogbert"

          Clear away all errors before proceeding, and start or restart samba as necessary. -

        2. - - - - +

        3. + + + + Check that the Samba server is running:

           root#  ps ax | grep mbd
          @@ -537,8 +537,8 @@
           			two instances of it. For more information regarding winbindd, see
           			TOSHARG2, Chapter 23, Section 23.3. The single instance of
           			smbd is normal.
          -			

        4. - +

        5. + Check that an anonymous connection can be made to the Samba server:

           root#  smbclient -L localhost -U%
          @@ -566,10 +566,10 @@
           			of browsing the server from a Windows client to obtain a list of shares on the server.
           			The -U% argument means to send a NULL username and
           			a NULL password.
          -			

        6. - - - +

        7. + + + Verify that the printers have the IP addresses assigned in the DHCP server configuration file. The easiest way to do this is to ping the printer name. Immediately after the ping response has been received, execute arp -a to find the MAC address of the printer @@ -587,8 +587,8 @@ The MAC address 08:00:46:7A:35:E4 matches that specified for the IP address from which the printer has responded and the entry for it in the /etc/dhcpd.conf file. -

        8. - +

        9. + Make an authenticated connection to the server using the smbclient tool:

           root#  smbclient //sleeth/accounts -U alanm
          @@ -605,53 +605,53 @@
                      65387 blocks of size 65536. 28590 blocks available
           smb: \> q
           

          -

      Procedure 2.3. Windows XP Professional Client Configuration

      1. +

      Procedure 2.3. Windows XP Professional Client Configuration

      1. Configure clients to the network settings shown in “Abmas Accounting 52-User Network Topology”. All clients use DHCP for TCP/IP protocol stack configuration. - - + + DHCP configures all Windows clients to use the WINS Server address 192.168.1.1. -

      2. +

      3. Join the Windows Domain called BILLMORE. Use the Domain Administrator username root and the SMB password you assigned to this account. A detailed step-by-step procedure for joining a Windows 200x/XP Professional client to a Windows Domain is given in “A Collection of Useful Tidbits”, “Joining a Domain: Windows 200x/XP Professional”. Reboot the machine as prompted and then log on using a Domain User account. -

      4. +

      5. Verify on each client that the machine called SLEETH is visible in My Network Places, that it is possible to connect to it and see the shares accounts and finsvcs, and that it is possible to open that share to reveal its contents. -

      6. +

      7. Instruct all users to log onto the workstation using their assigned username and password. -

      8. +

      9. Install a printer on each using the following steps: -

        1. +

          1. Click StartSettingsPrinters+Add Printer+Next. Do not click Network printer. Ensure that Local printer is selected. -

          2. +

          3. Click Next. In the Manufacturer: panel, select HP. In the Printers: panel, select the printer called HP LaserJet 4. Click Next. -

          4. +

          5. In the Available ports: panel, select FILE:. Accept the default printer name by clicking - Next. When asked, Would you like to print a - test page?, click No. Click + Next. When asked, “Would you like to print a + test page?”, click No. Click Finish. -

          6. +

          7. You may be prompted for the name of a file to print to. If so, close the dialog panel. Right-click HP LaserJet 4PropertiesDetails (Tab)Add Port. -

          8. +

          9. In the Network panel, enter the name of the print queue on the Samba server as follows: \\SERVER\hplj4. Click OK+OK to complete the installation. -

          10. +

          11. Repeat the printer installation steps above for the HP LaserJet 6 printer as well as for the QMS Magicolor XXXX laser printer. -

        Notebook Computers: A Special Case

        +

    Notebook Computers: A Special Case

    As a network administrator, you already know how to create local machine accounts for Windows 200x/XP Professional systems. This is the preferred solution to provide continuity of work for notebook users so that absence from the office network environment does not become a barrier to productivity. @@ -661,56 +661,56 @@ transparently access network resources as if logged onto the domain itself. There are some trade-offs that mean that as the network is more tightly secured, it becomes necessary to modify Windows client configuration somewhat. -

    Key Points Learned

    +

    Key Points Learned

    In this network design and implementation exercise, you created a Windows NT4-style Domain Controller using Samba-3.0.20. Following these guidelines, you experienced and implemented several important aspects of Windows networking. In the next chapter, you build on the experience. These are the highlights from this chapter: -

    • - +

      • + You implemented a DHCP server, and Microsoft Windows clients were able to obtain all necessary network configuration settings from this server. -

      • - +

      • + You created a Windows Domain Controller. You were able to use the network logon service and successfully joined Windows 200x/XP Professional clients to the Domain. -

      • - +

      • + You created raw print queues in the CUPS printing system. You maintained a simple printing system so that all users can share centrally managed printers. You installed native printer drivers on the Windows clients. -

      • +

      • You experienced the benefits of centrally managed user accounts on the server. -

      • +

      • You offered Mobile notebook users a solution that allows them to continue to work while away from the office and not connected to the corporate network. -

    Questions and Answers

    +

    Questions and Answers

    Your new Domain Controller is ready to serve you. What does it mean? Here are some questions and answers that may help. -

    1. +

    1. What is the key benefit of using DHCP to configure Windows client TCP/IP stacks? -
    2. +
    2. Are there any DHCP server configuration parameters in the /etc/dhcpd.conf that should be noted in particular? -
    3. +
    3. Is it possible to create a Windows Domain account that is specifically called Administrator? -
    4. +
    4. Why is it necessary to give the Windows Domain Administrator a UNIX UID of 0? -
    5. +
    5. One of my junior staff needs the ability to add machines to the Domain, but I do not want to give him root access. How can we do this? -
    6. +
    6. Why must I map Windows Domain Groups to UNIX groups? -
    7. +
    7. I deleted my root account and now I cannot add it back! What can I do? -
    8. +
    8. When I run net groupmap list, it reports a group called Administrators as well as Domain Admins. What is the difference between them? -
    9. +
    9. What is the effect of changing the name of a Samba server or of changing the Domain name? -
    10. +
    10. How can I manage user accounts from my Windows XP Professional workstation? -

    1.

    +

    1.

    What is the key benefit of using DHCP to configure Windows client TCP/IP stacks?

    First and foremost, portability. It means that notebook users can move between @@ -719,7 +719,7 @@ either using DHCP assigned addressing or when using dial-up networking, settings such as default routes and DNS server addresses that apply only to the Abmas office environment do not interfere with remote operations. This is an extremely important feature of DHCP. -

    2.

    +

    2.

    Are there any DHCP server configuration parameters in the /etc/dhcpd.conf that should be noted in particular?

    @@ -728,14 +728,14 @@ with the WINS server, and then instructs the client to first query the WINS server when a NetBIOS machine name needs to be resolved to an IP Address. This configuration results in far lower UDP broadcast traffic than would be the case if WINS was not used. -

    3.

    +

    3.

    Is it possible to create a Windows Domain account that is specifically called Administrator?

    You can surely create a Windows Domain account called Administrator. It is also possible to map that account so that it has the effective UNIX UID of 0. This way it isn't necessary to use the username map facility to map this account to the UNIX account called root. -

    4.

    +

    4.

    Why is it necessary to give the Windows Domain Administrator a UNIX UID of 0?

    The Windows Domain Administrator account is the most privileged account that @@ -745,7 +745,7 @@ Administrator to manage accounts as well as permissions, privileges, and security settings within the Domain and on the Samba server, equivalent rights must be assigned. This is achieved with the root UID equal to 0. -

    5.

    +

    5.

    One of my junior staff needs the ability to add machines to the Domain, but I do not want to give him root access. How can we do this?

    @@ -754,25 +754,25 @@ (or the equivalent wheel on some UNIX systems) that has a GID of 0. This must be the primary GID of the account of the user who is a member of the Windows Domain Admins account. -

    6.

    +

    6.

    Why must I map Windows Domain Groups to UNIX groups?

    Samba-3 does not permit a Domain Group to become visible to Domain network clients unless the account has a UNIX group account equivalent. The Domain groups that should be given UNIX equivalents are Domain Guests, Domain Users, and Domain Admins. -

    7.

    +

    7.

    I deleted my root account and now I cannot add it back! What can I do?

    This is a nasty problem. Fortunately, there is a solution. -

    1. +

      1. Back up your existing configuration files in case you need to restore them. -

      2. +

      3. Rename the group_mapping.tdb file. -

      4. +

      5. Use the smbpasswd to add the root account. -

      6. +

      7. Restore the group_mapping.tdb file. -

    8.

    +

    8.

    When I run net groupmap list, it reports a group called Administrators as well as Domain Admins. What is the difference between them?

    @@ -780,7 +780,7 @@ present as the Local Group account on a Domain Member server or workstation. Samba uses only Domain Groups at this time. A Workstation or Server Local Group has no meaning in a Samba context. This may change at some later date. These accounts are provided only so that security objects are correctly shown. -

    9.

    +

    9.

    What is the effect of changing the name of a Samba server or of changing the Domain name?

    If you elect to change the name of the Samba server, on restarting smbd, @@ -792,7 +792,7 @@ SID before the change is made. You can back up the SID using the net getlocalsid (Samba-3) or the smbpasswd (Samba-2.2.x). To change the SID, you use the same tool. Be sure to check the man page for this command for detailed instructions regarding the steps involved. -

    10.

    +

    10.

    How can I manage user accounts from my Windows XP Professional workstation?

    Samba-3 implements a Windows NT4-style security domain architecture. This type of Domain cannot diff -u -r --new-file --exclude .svn --exclude CVS samba-3.3.10//docs/htmldocs/Samba3-ByExample/unixclients.html samba-3.3.11//docs/htmldocs/Samba3-ByExample/unixclients.html --- samba-3.3.10//docs/htmldocs/Samba3-ByExample/unixclients.html 2010-01-14 11:24:16.000000000 +0100 +++ samba-3.3.11//docs/htmldocs/Samba3-ByExample/unixclients.html 2010-02-22 16:53:36.000000000 +0100 @@ -1,4 +1,4 @@ -Chapter 7. Adding Domain Member Servers and Clients

    Chapter 7. Adding Domain Member Servers and Clients

    +Chapter 7. Adding Domain Member Servers and Clients

    Chapter 7. Adding Domain Member Servers and Clients

    The most frequently discussed Samba subjects over the past 2 years have focused around domain control and printing. It is well known that Samba is a file and print server. A recent survey conducted by Open Magazine found that of all respondents, 97 percent use Samba for file and print services, and 68 percent use Samba for Domain Control. See the @@ -11,16 +11,16 @@ exciting aspects of Samba deployment. This chapter directs your attention to provide important information on the addition of Samba servers into your present Windows network whatever the controlling technology may be. So let's get back to our good friends at Abmas. -

    Introduction

    +

    Introduction

    Looking back over the achievements of the past year or two, daily events at Abmas are rather straightforward with not too many distractions or problems. Your team is doing well, but a number of employees are asking for Linux desktop systems. Your network has grown and demands additional domain member servers. Let's get on with this; Christine and Stan are ready to go. -

    +

    Stan is firmly in control of the department of the future, while Christine is enjoying a stable and predictable network environment. It is time to add more servers and to add Linux desktops. It is time to meet the demands of future growth and endure trial by fire. -

    Assignment Tasks

    +

    Assignment Tasks

    You must now add UNIX/Linux domain member servers to your network. You have a friend who has a Windows 2003 Active Directory domain network who wants to add a Samba/Linux server and has asked Christine to help him out. Your real objective is to help Christine to see more of the way the Microsoft world lives and use @@ -30,8 +30,8 @@ these systems to make sure that Abmas is not building islands of technology. You ask Christine to do likewise at Swodniw Biz NL (your friend's company) to help them to evaluate a Linux desktop. You want to make the right decision, don't you? -

    Dissection and Discussion

    - +

    Dissection and Discussion

    + Recent Samba mailing-list activity is witness to how many sites are using winbind. Some have no trouble at all with it, yet to others the problems seem insurmountable. Periodically there are complaints concerning an inability to achieve identical user and group IDs between Windows and UNIX environments. @@ -39,57 +39,57 @@ You provide step-by-step implementations of the various tools that can be used for identity resolution. You also provide working examples of solutions for integrated authentication for both UNIX/Linux and Windows environments. -

    Technical Issues

    - One of the great challenges we face when people ask us, What is the best way to solve - this problem? is to get beyond the facts so we not only can clearly comprehend +

    Technical Issues

    + One of the great challenges we face when people ask us, “What is the best way to solve + this problem?” is to get beyond the facts so we not only can clearly comprehend the immediate technical problem, but also can understand how needs may change.

    - + There are a few facts we should note when dealing with the question of how best to integrate UNIX/Linux clients and servers into a Windows networking environment: -

    • - - - - - +

      • + + + + + A domain controller (PDC or BDC) is always authoritative for all accounts in its domain. This means that a BDC must (of necessity) be able to resolve all account UIDs and GIDs to the same values that the PDC resolved them to. -

      • - - - - +

      • + + + + A domain member can be authoritative for local accounts, but is never authoritative for domain accounts. If a user is accessing a domain member server and that user's account is not known locally, the domain member server must resolve the identity of that user from the domain in which that user's account resides. It must then map that ID to a UID/GID pair that it can use locally. This is handled by winbindd. -

      • +

      • Samba, when running on a domain member server, can resolve user identities from a number of sources: -

        • - - - - - +

          • + + + + + By executing a system getpwnam() or getgrnam() call. On systems that support it, this utilizes the name service switch (NSS) facility to resolve names according to the configuration of the /etc/nsswitch.conf file. NSS can be configured to use LDAP, winbind, NIS, or local files. -

          • - - - +

          • + + + Performing, via NSS, a direct LDAP search (where an LDAP passdb backend has been configured). This requires the use of the PADL nss_ldap tool (or equivalent). -

          • - - - - +

          • + + + + Directly by querying winbindd. The winbindd contacts a domain controller to attempt to resolve the identity of the user or group. It receives the Windows networking security identifier (SID) for that appropriate @@ -97,8 +97,8 @@ creates an entry in its winbindd_idmap.tdb and winbindd_cache.tdb files.

            - - + + If the parameter idmap backend = ldap:ldap://myserver.domain was specified and the LDAP server has been configured with a container in which it may store the IDMAP entries, all domain members may share a common mapping. @@ -110,38 +110,38 @@ Which of the resolver methods is chosen is determined by the way that Samba is configured in the smb.conf file. Some of the configuration options are rather less than obvious to the casual user. -

          • - - - +

          • + + + If you wish to make use of accounts (users and/or groups) that are local to (i.e., capable of being resolved using) the NSS facility, it is possible to use the winbind trusted domains only = Yes in the smb.conf file. This parameter specifically applies to domain controllers, and to domain member servers.

          - - - + + + For many administrators, it should be plain that the use of an LDAP-based repository for all network accounts (both for POSIX accounts and for Samba accounts) provides the most elegant and controllable facility. You eventually appreciate the decision to use LDAP.

          - - - + + + If your network account information resides in an LDAP repository, you should use it ahead of any alternative method. This means that if it is humanly possible to use the nss_ldap tools to resolve UNIX account UIDs/GIDs via LDAP, this is the preferred solution, because it provides a more readily controllable method for asserting the exact same user and group identifiers throughout the network.

          - - - - - - + + + + + + In the situation where UNIX accounts are held on the domain member server itself, the only effective way to use them involves the smb.conf entry winbind trusted domains only = Yes. This forces @@ -149,10 +149,10 @@ then be controlled via /etc/nsswitch.conf file settings. The use of this parameter disables the use of Samba with trusted domains (i.e., external domains).

          - - - - + + + + Winbind can be used to create an appliance mode domain member server. In this capacity, winbindd is configured to automatically allocate UIDs/GIDs from numeric ranges set in the smb.conf file. The allocation is made for all accounts that connect to that domain member server, whether within its own domain or from @@ -161,16 +161,16 @@ same UID/GID on both servers however, this is transparent to the Windows network user. This data is stored in the winbindd_idmap.tdb and winbindd_cache.tdb files.

          - + The use of an LDAP backend for the Winbind IDMAP facility permits Windows domain SIDs mappings to UIDs/GIDs to be stored centrally. The result is a consistent mapping across all domain member servers so configured. This solves one of the major headaches for network administrators who need to copy files between or across network file servers. -

        Political Issues

        - - - - +

        Political Issues

        + + + + One of the most fierce conflicts recently being waged is resistance to the adoption of LDAP, in particular OpenLDAP, as a replacement for UNIX NIS (previously called Yellow Pages). Let's face it, LDAP is different and requires a new approach to the need for a better identity management solution. The more @@ -182,23 +182,23 @@ you can't use Windows Active Directory in a heterogenous environment it can be done, it just requires commercial integration products. But it's not what Active Directory was designed for.

        - - + + A number of long-term UNIX devotees have recently commented in various communications that the Samba Team is the first application group to almost force network administrators to use LDAP. It should be pointed out that we resisted this for as long as we could. It is not out of laziness or malice that LDAP has finally emerged as the preferred identity management backend for Samba. We recommend LDAP for your total organizational directory needs. -

      Implementation

      - - - +

    Implementation

    + + + The domain member server and the domain member client are at the center of focus in this chapter. Configuration of Samba-3 domain controller is covered in earlier chapters, so if your interest is in domain controller configuration, you will not find that here. You will find good oil that helps you to add domain member servers and clients.

    - + In practice, domain member servers and domain member workstations are very different entities, but in terms of technology they share similar core infrastructure. A technologist would argue that servers and workstations are identical. Many users would argue otherwise, given that in a well-disciplined @@ -206,15 +206,15 @@ are located on servers. A workstation is frequently viewed as a disposable (easy to replace) item, but a server is viewed as a core component of the business.

    - + We can look at this another way. If a workstation breaks down, one user is affected, but if a server breaks down, hundreds of users may not be able to work. The services that a workstation must provide are document- and file-production oriented; a server provides information storage and is distribution oriented.

    - - - + + + Why is this important? For starters, we must identify what components of the operating system and its environment must be configured. Also, it is necessary to recognize where the interdependencies between the various services to be used are. @@ -225,13 +225,13 @@

    So, in this chapter we demonstrate how to implement the technology. It is done within a context of what type of service need must be fulfilled. -

    Samba Domain with Samba Domain Member Server Using NSS LDAP

    - - - - - - +

    Samba Domain with Samba Domain Member Server Using NSS LDAP

    + + + + + + In this example, it is assumed that you have Samba PDC/BDC servers. This means you are using an LDAP ldapsam backend. We are adding to the LDAP backend database (directory) containers for use by the IDMAP facility. This makes it possible to have globally consistent @@ -247,9 +247,9 @@ idmap gid ranges. Where LDAP is used, the mappings can be stored in LDAP so that all domain member servers can use a consistent mapping.

    - - - + + + If your installation is accessed only from clients that are members of your own domain, and all user accounts are present in a local passdb backend then it is not necessary to run winbindd. The local passdb backend can be in smbpasswd, tdbsam, or in ldapsam. @@ -258,38 +258,38 @@ user and group account information. The POSIX information is usually obtained using the getpwnam() system call. On NSS-enabled systems, the actual POSIX account source can be provided from -

    • - - +

      • + + Accounts in /etc/passwd or in /etc/group. -

      • - - - - - - - - - +

      • + + + + + + + + + Resolution via NSS. On NSS-enabled systems, there is usually a facility to resolve IDs via multiple methods. The methods typically include files, compat, db, ldap, nis, nisplus, hesiod. When correctly installed, Samba adds to this list the winbindd facility. The ldap facility is frequently the nss_ldap tool provided by PADL Software. -

      Note

      +

    Note

    To advoid confusion the use of the term local passdb backend means that the user account backend is not shared by any other Samba server instead, it is used only locally on the Samba domain member server under discussion.

    - + The diagram in “Samba Domain: Samba Member Server” demonstrates the relationship of Samba and system components that are involved in the identity resolution process where Samba is used as a domain member server within a Samba domain control network.

    Figure 7.2. Samba Domain: Samba Member Server

    Samba Domain: Samba Member Server

    - - + + In this example configuration, Samba will directly search the LDAP-based passwd backend ldapsam to obtain authentication and user identity information. The IDMAP information is stored in the LDAP backend so that it can be shared by all domain member servers so that every user will have a @@ -300,11 +300,11 @@ The instructions given here apply to the Samba environment shown in “Making Happy Users” and “A Distributed 2000-User Network”. If the network does not have an LDAP slave server (i.e., “Making Happy Users” configuration), change the target LDAP server from lapdc to massive. -

    Procedure 7.1. Configuration of NSS_LDAP-Based Identity Resolution

    1. +

      Procedure 7.1. Configuration of NSS_LDAP-Based Identity Resolution

      1. Create the smb.conf file as shown in “Samba Domain Member in Samba Domain Using LDAP smb.conf File”. Locate this file in the directory /etc/samba. -

      2. - +

      3. + Configure the file that will be used by nss_ldap to locate and communicate with the LDAP server. This file is called ldap.conf. If your implementation of nss_ldap is consistent with @@ -322,12 +322,12 @@ root# strings /lib/libnss_ldap* | grep ldap.conf /etc/ldap.conf

        -

      4. +

      5. Configure the NSS control file so it matches the one shown in “NSS using LDAP for Identity Resolution File: /etc/nsswitch.conf”. -

      6. - - +

      7. + + Before proceeding to configure Samba, validate the operation of the NSS identity resolution via LDAP by executing:

        @@ -362,9 +362,9 @@
         PIOps:x:1002:
         sammy:x:4321:
         

        - - - + + + This shows that all is working as it should be. Notice that in the LDAP database the users' primary and secondary group memberships are identical. It is not necessary to add secondary group memberships (in the group database) if the @@ -373,8 +373,8 @@ doubling up of group memberships and may cause problems with winbind under certain conditions. It is intended that these limitations with winbind will be resolved soon after Samba-3.0.20 has been released. -

      8. - +

      9. + The LDAP directory must have a container object for IDMAP data. There are several ways you can check that your LDAP database is able to receive IDMAP information. One of the simplest is to execute: @@ -383,7 +383,7 @@ dn: ou=Idmap,dc=abmas,dc=biz ou: idmap

        - + If the execution of this command does not return IDMAP entries, you need to create an LDIF template file (see “LDIF IDMAP Add-On Load File File: /etc/openldap/idmap.LDIF”). You can add the required entries using the following command: @@ -391,16 +391,16 @@ root# ldapadd -x -D "cn=Manager,dc=abmas,dc=biz" \ -w not24get < /etc/openldap/idmap.LDIF

        -

      10. +

      11. Samba automatically populates the LDAP directory container when it needs to. To permit Samba write access to the LDAP directory it is necessary to set the LDAP administrative password in the secrets.tdb file as shown here:

         root#  smbpasswd -w not24get
         

        -

      12. - - +

      13. + + The system is ready to join the domain. Execute the following:

         root#  net rpc join -U root%not24get
        @@ -411,17 +411,17 @@
         		Failure to join the domain could be caused by any number of variables. The most common
         		causes of failure to join are:
         		

        -

        • Broken resolution of NetBIOS names to the respective IP address.

        • Incorrect username and password credentials.

        • The NT4 restrict anonymous is set to exclude anonymous +

          • Broken resolution of NetBIOS names to the respective IP address.

          • Incorrect username and password credentials.

          • The NT4 restrict anonymous is set to exclude anonymous connections.

          The connection setup can be diagnosed by executing:

           root#  net rpc join -S 'pdc-name' -U administrator%password -d 5
           

          - - - - + + + + Note: Use "root" for UNIX/Linux and Samba, use "Administrator" for Windows NT4/200X. If the cause of the failure appears to be related to a rejected or failed NT_SESSION_SETUP* or an error message that says NT_STATUS_ACCESS_DENIED immediately check the Windows registry setting that controls the @@ -448,8 +448,8 @@ NT_STATUS_ACCESS_DENIED Join to 'MEGANET2' failed.

        -

      14. - +

      15. + Just joining the domain is not quite enough; you must now provide a privileged set of credentials through which winbindd can interact with the domain servers. Execute the following to implant the necessary credentials: @@ -457,10 +457,10 @@ root# wbinfo --set-auth-user=Administrator%not24get

        The configuration is now ready to obtain the Samba domain user and group information. -

      16. +

      17. You may now start Samba in the usual manner, and your Samba domain member server is ready for use. Just add shares as required. -

      Example 7.1. Samba Domain Member in Samba Domain Using LDAP smb.conf File

      # Global parameters
      [global]
      unix charset = LOCALE
      workgroup = MEGANET2
      security = DOMAIN
      username map = /etc/samba/smbusers
      log level = 10
      syslog = 0
      log file = /var/log/samba/%m
      max log size = 50
      smb ports = 139
      name resolve order = wins bcast hosts
      printcap name = CUPS
      wins server = 192.168.2.1
      ldap suffix = dc=abmas,dc=biz
      ldap machine suffix = ou=People
      ldap user suffix = ou=People
      ldap group suffix = ou=Groups
      ldap idmap suffix = ou=Idmap
      ldap admin dn = cn=Manager,dc=abmas,dc=biz
      idmap backend = ldap:ldap://lapdc.abmas.biz
      idmap uid = 10000-20000
      idmap gid = 10000-20000
      winbind trusted domains only = Yes
      printer admin = root
      printing = cups
      [homes]
      comment = Home Directories
      valid users = %S
      read only = No
      browseable = No
      [printers]
      comment = SMB Print Spool
      path = /var/spool/samba
      guest ok = Yes
      printable = Yes
      browseable = No
      [print$]
      comment = Printer Drivers
      path = /var/lib/samba/drivers
      admin users = root, Administrator
      write list = root

      Example 7.2. LDIF IDMAP Add-On Load File File: /etc/openldap/idmap.LDIF

      +		

    Example 7.1. Samba Domain Member in Samba Domain Using LDAP smb.conf File

    # Global parameters
    [global]
    unix charset = LOCALE
    workgroup = MEGANET2
    security = DOMAIN
    username map = /etc/samba/smbusers
    log level = 10
    syslog = 0
    log file = /var/log/samba/%m
    max log size = 50
    smb ports = 139
    name resolve order = wins bcast hosts
    printcap name = CUPS
    wins server = 192.168.2.1
    ldap suffix = dc=abmas,dc=biz
    ldap machine suffix = ou=People
    ldap user suffix = ou=People
    ldap group suffix = ou=Groups
    ldap idmap suffix = ou=Idmap
    ldap admin dn = cn=Manager,dc=abmas,dc=biz
    idmap backend = ldap:ldap://lapdc.abmas.biz
    idmap uid = 10000-20000
    idmap gid = 10000-20000
    winbind trusted domains only = Yes
    printer admin = root
    printing = cups
    [homes]
    comment = Home Directories
    valid users = %S
    read only = No
    browseable = No
    [printers]
    comment = SMB Print Spool
    path = /var/spool/samba
    guest ok = Yes
    printable = Yes
    browseable = No
    [print$]
    comment = Printer Drivers
    path = /var/lib/samba/drivers
    admin users = root, Administrator
    write list = root

    Example 7.2. LDIF IDMAP Add-On Load File File: /etc/openldap/idmap.LDIF

     dn: ou=Idmap,dc=abmas,dc=biz
     objectClass: organizationalUnit
     ou: idmap
    @@ -497,28 +497,28 @@
     bootparams:     files
     automount:      files
     aliases:        files
    -

    NT4/Samba Domain with Samba Domain Member Server: Using NSS and Winbind

    +


    NT4/Samba Domain with Samba Domain Member Server: Using NSS and Winbind

    You need to use this method for creating a Samba domain member server if any of the following conditions prevail: -

    • +

      • LDAP support (client) is not installed on the system. -

      • +

      • There are mitigating circumstances forcing a decision not to use LDAP. -

      • +

      • The Samba domain member server must be part of a Windows NT4 Domain, or a Samba Domain.

      - - - + + + Later in the chapter, you can see how to configure a Samba domain member server for a Windows ADS domain. Right now your objective is to configure a Samba server that can be a member of a Windows NT4-style domain and/or does not use LDAP. -

      Note

      - +

      Note

      + If you use winbind for identity resolution, make sure that there are no duplicate accounts.

      - + For example, do not have more than one account that has UID=0 in the password database. If there is an account called root in the /etc/passwd database, it is okay to have an account called root in the LDAP ldapsam or in the @@ -526,32 +526,32 @@ break. This means that the Administrator account must be called root.

      - - - + + + Winbind will break if there is an account in /etc/passwd that has the same UID as an account that is in LDAP ldapsam (or in tdbsam) but that differs in name only.

      - - - - - + + + + + The following configuration uses CIFS/SMB protocols alone to obtain user and group credentials. The winbind information is locally cached in the winbindd_cache.tdb winbindd_idmap.tdb files. This provides considerable performance benefits compared with the LDAP solution, particularly where the LDAP lookups must traverse WAN links. You may examine the contents of these files using the tool tdbdump, though you may have to build this from the Samba source code if it has not been supplied as part of a binary package distribution that you may be using. -

      Procedure 7.2. Configuration of Winbind-Based Identity Resolution

      1. +

        Procedure 7.2. Configuration of Winbind-Based Identity Resolution

        1. Using your favorite text editor, create the smb.conf file so it has the contents shown in “Samba Domain Member Server Using Winbind smb.conf File for NT4 Domain”. -

        2. - +

        3. + Edit the /etc/nsswitch.conf so it has the entries shown in “NSS using LDAP for Identity Resolution File: /etc/nsswitch.conf”. -

        4. - +

        5. + The system is ready to join the domain. Execute the following:

           net rpc join -U root%not2g4et
          @@ -559,9 +559,9 @@
           

          This indicates that the domain join succeed. -

        6. - - +

        7. + + Validate operation of winbind using the wbinfo tool as follows:

          @@ -587,10 +587,10 @@
           MEGANET2+PIOps
           

          This shows that domain groups have been correctly obtained also. -

        8. - - - +

        9. + + + The next step verifies that NSS is able to obtain this information correctly from winbind also.

          @@ -629,9 +629,9 @@
           MEGANET2+Finances:x:10004:
           MEGANET2+PIOps:x:10005:
           

          -

        10. +

        11. The Samba member server of a Windows NT4 domain is ready for use. -

        Example 7.5. Samba Domain Member Server Using Winbind smb.conf File for NT4 Domain

        # Global parameters
        [global]
        unix charset = LOCALE
        workgroup = MEGANET2
        security = DOMAIN
        username map = /etc/samba/smbusers
        log level = 1
        syslog = 0
        log file = /var/log/samba/%m
        max log size = 0
        smb ports = 139
        name resolve order = wins bcast hosts
        printcap name = CUPS
        wins server = 192.168.2.1
        idmap uid = 10000-20000
        idmap gid = 10000-20000
        template primary group = "Domain Users"
        template shell = /bin/bash
        winbind separator = +
        printer admin = root
        hosts allow = 192.168.2., 192.168.3., 127.
        printing = cups
        [homes]
        comment = Home Directories
        valid users = %S
        read only = No
        browseable = No
        [printers]
        comment = SMB Print Spool
        path = /var/spool/samba
        guest ok = Yes
        printable = Yes
        browseable = No
        [print$]
        comment = Printer Drivers
        path = /var/lib/samba/drivers
        admin users = root, Administrator
        write list = root

      NT4/Samba Domain with Samba Domain Member Server without NSS Support

      +

    Example 7.5. Samba Domain Member Server Using Winbind smb.conf File for NT4 Domain

    # Global parameters
    [global]
    unix charset = LOCALE
    workgroup = MEGANET2
    security = DOMAIN
    username map = /etc/samba/smbusers
    log level = 1
    syslog = 0
    log file = /var/log/samba/%m
    max log size = 0
    smb ports = 139
    name resolve order = wins bcast hosts
    printcap name = CUPS
    wins server = 192.168.2.1
    idmap uid = 10000-20000
    idmap gid = 10000-20000
    template primary group = "Domain Users"
    template shell = /bin/bash
    winbind separator = +
    printer admin = root
    hosts allow = 192.168.2., 192.168.3., 127.
    printing = cups
    [homes]
    comment = Home Directories
    valid users = %S
    read only = No
    browseable = No
    [printers]
    comment = SMB Print Spool
    path = /var/spool/samba
    guest ok = Yes
    printable = Yes
    browseable = No
    [print$]
    comment = Printer Drivers
    path = /var/lib/samba/drivers
    admin users = root, Administrator
    write list = root

    NT4/Samba Domain with Samba Domain Member Server without NSS Support

    No matter how many UNIX/Linux administrators there may be who believe that a UNIX operating system that does not have NSS and PAM support to be outdated, the fact is there are still many such systems in use today. Samba can be used without NSS support, but this @@ -642,24 +642,24 @@ to the Samba server will cause the look-up of the incoming username. If the account is found, it is used. If the account is not found, one will be automatically created on the local machine so that it can then be used for all access controls. -

    Procedure 7.3. Configuration Using Local Accounts Only

    1. +

      Procedure 7.3. Configuration Using Local Accounts Only

      1. Using your favorite text editor, create the smb.conf file so it has the contents shown in “Samba Domain Member Server Using Local Accounts smb.conf File for NT4 Domain”. -

      2. +

      3. The system is ready to join the domain. Execute the following:

         net rpc join -U root%not24get
         Joined domain MEGANET2.
         

        This indicates that the domain join succeed. -

      4. +

      5. Be sure to run all three Samba daemons: smbd, nmbd, winbindd. -

      6. +

      7. The Samba member server of a Windows NT4 domain is ready for use. -

      Example 7.6. Samba Domain Member Server Using Local Accounts smb.conf File for NT4 Domain

      # Global parameters
      [global]
      unix charset = LOCALE
      workgroup = MEGANET3
      netbios name = BSDBOX
      security = DOMAIN
      username map = /etc/samba/smbusers
      log level = 1
      syslog = 0
      add user script = /usr/sbin/useradd -m '%u'
      add machine script = /usr/sbin/useradd -M '%u'
      add group script = /usr/sbin/groupadd '%g'
      log file = /var/log/samba/%m
      max log size = 0
      smb ports = 139
      name resolve order = wins bcast hosts
      printcap name = CUPS
      wins server = 192.168.2.1
      printer admin = root
      hosts allow = 192.168.2., 192.168.3., 127.
      printing = cups
      [homes]
      comment = Home Directories
      valid users = %S
      read only = No
      browseable = No
      [printers]
      comment = SMB Print Spool
      path = /var/spool/samba
      guest ok = Yes
      printable = Yes
      browseable = No
      [print$]
      comment = Printer Drivers
      path = /var/lib/samba/drivers
      admin users = root, Administrator
      write list = root

    Active Directory Domain with Samba Domain Member Server

    - - - +

    Example 7.6. Samba Domain Member Server Using Local Accounts smb.conf File for NT4 Domain

    # Global parameters
    [global]
    unix charset = LOCALE
    workgroup = MEGANET3
    netbios name = BSDBOX
    security = DOMAIN
    username map = /etc/samba/smbusers
    log level = 1
    syslog = 0
    add user script = /usr/sbin/useradd -m '%u'
    add machine script = /usr/sbin/useradd -M '%u'
    add group script = /usr/sbin/groupadd '%g'
    log file = /var/log/samba/%m
    max log size = 0
    smb ports = 139
    name resolve order = wins bcast hosts
    printcap name = CUPS
    wins server = 192.168.2.1
    printer admin = root
    hosts allow = 192.168.2., 192.168.3., 127.
    printing = cups
    [homes]
    comment = Home Directories
    valid users = %S
    read only = No
    browseable = No
    [printers]
    comment = SMB Print Spool
    path = /var/spool/samba
    guest ok = Yes
    printable = Yes
    browseable = No
    [print$]
    comment = Printer Drivers
    path = /var/lib/samba/drivers
    admin users = root, Administrator
    write list = root

    Active Directory Domain with Samba Domain Member Server

    + + + One of the much-sought-after features new to Samba-3 is the ability to join an Active Directory domain using Kerberos protocols. This makes it possible to operate an entire Windows network without the need to run NetBIOS over TCP/IP and permits more secure networking in general. An @@ -667,10 +667,10 @@ later book may explore the intricacies of the NetBIOS-less operation that Samba-3 can participate in. For now, we simply focus on how a Samba-3 server can be made a domain member server.

    - - - - + + + + The diagram in “Active Directory Domain: Samba Member Server” demonstrates how Samba-3 interfaces with Microsoft Active Directory components. It should be noted that if Microsoft Windows Services for UNIX (SFU) has been installed and correctly configured, it is possible to use client LDAP @@ -694,8 +694,8 @@ name of the server is W2K3S. In ADS realm terms, the domain controller is known as w2k3s.london.abmas.biz. In NetBIOS nomenclature, the domain name is LONDON and the server name is W2K3S. -

    Figure 7.3. Active Directory Domain: Samba Member Server

    Active Directory Domain: Samba Member Server

    Procedure 7.4. Joining a Samba Server as an ADS Domain Member

    1. - +

      Figure 7.3. Active Directory Domain: Samba Member Server

      Active Directory Domain: Samba Member Server

      Procedure 7.4. Joining a Samba Server as an ADS Domain Member

      1. + Before you try to use Samba-3, you want to know for certain that your executables have support for Kerberos and for LDAP. Execute the following to identify whether or not this build is perhaps suitable for use: @@ -761,16 +761,16 @@

        This does look promising; smbd has been built with Kerberos and LDAP support. You are relieved to know that it is safe to progress. -

      2. - - - - - - - - - +

      3. + + + + + + + + + The next step is to identify which version of the Kerberos libraries have been used. In order to permit Samba-3 to interoperate with Windows 2003 Active Directory, it is essential that it has been linked with either MIT Kerberos version 1.3.1 or later, @@ -791,25 +791,25 @@

        From this point on, you are certain that the Samba-3 build you are using has the necessary capabilities. You can now configure Samba-3 and the NSS. -

      4. +

      5. Using you favorite editor, configure the smb.conf file that is located in the /etc/samba directory so that it has the contents shown in “Samba Domain Member smb.conf File for Active Directory Membership”. -

      6. +

      7. Edit or create the NSS control file so it has the contents shown in “NSS using LDAP for Identity Resolution File: /etc/nsswitch.conf”. -

      8. - +

      9. + Delete the file /etc/samba/secrets.tdb if it exists. Of course, you do keep a backup, don't you? -

      10. +

      11. Delete the tdb files that cache Samba information. You keep a backup of the old files, of course. You also remove all files to ensure that nothing can pollute your nice, new configuration. Execute the following (example is for SUSE Linux):

         root#  rm /var/lib/samba/*tdb
         

        -

      12. - +

      13. + Validate your smb.conf file using testparm (as you have done previously). Correct all errors reported before proceeding. The command you execute is: @@ -818,9 +818,9 @@

        Now that you are satisfied that your Samba server is ready to join the Windows ADS domain, let's move on. -

      14. - - +

      15. + + This is a good time to double-check everything and then execute the following command when everything you have done has checked out okay:

        @@ -831,38 +831,38 @@
         		You have successfully made your Samba-3 server a member of the ADS domain
         		using Kerberos protocols.
         		

        - - + + In the event that you receive no output messages, a silent return means that the domain join failed. You should use ethereal to identify what may be failing. Common causes of a failed join include: -

        • - +

          • + Defective or misconfigured DNS name resolution. -

          • - +

          • + Restrictive security settings on the Windows 200x ADS domain controller preventing needed communications protocols. You can check this by searching the Windows Server 200x Event Viewer. -

          • +

          • Incorrectly configured smb.conf file settings. -

          • +

          • Lack of support of necessary Kerberos protocols because the version of MIT Kerberos (or Heimdal) in use is not up to date enough to support the necessary functionality.

          - - - + + + In any case, never execute the net rpc join command in an attempt to join the Samba server to the domain, unless you wish not to use the Kerberos security protocols. Use of the older RPC-based domain join facility requires that Windows Server 200x ADS has been configured appropriately for mixed mode operation. -

        • - - +

        • + + If the tdbdump is installed on your system (not essential), you can look inside the /etc/samba/secrets.tdb file. If you wish to do this, execute: @@ -889,11 +889,11 @@ }

        This is given to demonstrate to the skeptics that this process truly does work. -

      16. +

      17. It is now time to start Samba in the usual way (as has been done many time before in this book). -

      18. - +

      19. + This is a good time to verify that everything is working. First, check that winbind is able to obtain the list of users and groups from the ADS domain controller. Execute the following: @@ -919,7 +919,7 @@ LONDON+DnsUpdateProxy

        Excellent. That worked also, as expected. -

      20. +

      21. Now repeat this via NSS to validate that full identity resolution is functional as required. Execute:

        @@ -951,10 +951,10 @@
         LONDON+DnsUpdateProxy:x:10008:
         

        This is very pleasing. Everything works as expected. -

      22. - - - +

      23. + + + You may now perform final verification that communications between Samba-3 winbind and the Active Directory server is using Kerberos protocols. Execute the following:

        @@ -971,8 +971,8 @@
         		It should be noted that Kerberos protocols are time-clock critical. You should
         		keep all server time clocks synchronized using the network time protocol (NTP).
         		In any case, the output we obtained confirms that all systems are operational.
        -		

      24. - +

      25. + There is one more action you elect to take, just because you are paranoid and disbelieving, so you execute the following command:

        @@ -1142,40 +1142,40 @@
         

        Now all is revealed. Your curiosity, as well as that of your team, has been put at ease. May this server serve well all who happen upon it. -

        Example 7.7. Samba Domain Member smb.conf File for Active Directory Membership

        # Global parameters
        [global]
        unix charset = LOCALE
        workgroup = LONDON
        realm = LONDON.ABMAS.BIZ
        server string = Samba 3.0.20
        security = ADS
        username map = /etc/samba/smbusers
        log level = 1
        syslog = 0
        log file = /var/log/samba/%m
        max log size = 50
        printcap name = CUPS
        ldap ssl = no
        idmap uid = 10000-20000
        idmap gid = 10000-20000
        template primary group = "Domain Users"
        template shell = /bin/bash
        winbind separator = +
        printing = cups
        [homes]
        comment = Home Directories
        valid users = %S
        read only = No
        browseable = No
        [printers]
        comment = SMB Print Spool
        path = /var/spool/samba
        guest ok = Yes
        printable = Yes
        browseable = No
        [print$]
        comment = Printer Drivers
        path = /var/lib/samba/drivers
        admin users = root, Administrator
        write list = root

        IDMAP_RID with Winbind

        - - - - +

        Example 7.7. Samba Domain Member smb.conf File for Active Directory Membership

        # Global parameters
        [global]
        unix charset = LOCALE
        workgroup = LONDON
        realm = LONDON.ABMAS.BIZ
        server string = Samba 3.0.20
        security = ADS
        username map = /etc/samba/smbusers
        log level = 1
        syslog = 0
        log file = /var/log/samba/%m
        max log size = 50
        printcap name = CUPS
        ldap ssl = no
        idmap uid = 10000-20000
        idmap gid = 10000-20000
        template primary group = "Domain Users"
        template shell = /bin/bash
        winbind separator = +
        printing = cups
        [homes]
        comment = Home Directories
        valid users = %S
        read only = No
        browseable = No
        [printers]
        comment = SMB Print Spool
        path = /var/spool/samba
        guest ok = Yes
        printable = Yes
        browseable = No
        [print$]
        comment = Printer Drivers
        path = /var/lib/samba/drivers
        admin users = root, Administrator
        write list = root

        IDMAP_RID with Winbind

        + + + + The idmap_rid facility is a new tool that, unlike native winbind, creates a predictable mapping of MS Windows SIDs to UNIX UIDs and GIDs. The key benefit of this method of implementing the Samba IDMAP facility is that it eliminates the need to store the IDMAP data in a central place. The downside is that it can be used only within a single ADS domain and is not compatible with trusted domain implementations.

        - - - - + + + + This alternate method of SID to UID/GID mapping can be achieved with the idmap_rid plug-in. This plug-in uses the RID of the user SID to derive the UID and GID by adding the RID to a base value specified. This utility requires that the parameter - allow trusted domains = No must be specified, as it is not compatible + “allow trusted domains = No” must be specified, as it is not compatible with multiple domain environments. The idmap uid and idmap gid ranges must be specified.

        - - + + The idmap_rid facility can be used both for NT4/Samba-style domains as well as with Active Directory. To use this with an NT4 domain, the realm is not used. Additionally the method used to join the domain uses the net rpc join process.

        An example smb.conf file for an ADS domain environment is shown in “Example smb.conf File Using idmap_rid”. -

        Example 7.8. Example smb.conf File Using idmap_rid

        # Global parameters
        [global]
        workgroup = KPAK
        netbios name = BIGJOE
        realm = CORP.KPAK.COM
        server string = Office Server
        security = ADS
        allow trusted domains = No
        idmap backend = idmap_rid:KPAK=500-100000000
        idmap uid = 500-100000000
        idmap gid = 500-100000000
        template shell = /bin/bash
        winbind use default domain = Yes
        winbind enum users = No
        winbind enum groups = No
        winbind nested groups = Yes
        printer admin = "KPAK\Domain Admins"

        - - - - +

        Example 7.8. Example smb.conf File Using idmap_rid

        # Global parameters
        [global]
        workgroup = KPAK
        netbios name = BIGJOE
        realm = CORP.KPAK.COM
        server string = Office Server
        security = ADS
        allow trusted domains = No
        idmap backend = idmap_rid:KPAK=500-100000000
        idmap uid = 500-100000000
        idmap gid = 500-100000000
        template shell = /bin/bash
        winbind use default domain = Yes
        winbind enum users = No
        winbind enum groups = No
        winbind nested groups = Yes
        printer admin = "KPAK\Domain Admins"

        + + + + In a large domain with many users, it is imperative to disable enumeration of users and groups. For example, at a site that has 22,000 users in Active Directory the winbind-based user and group resolution is unavailable for nearly 12 minutes following first start-up of @@ -1185,8 +1185,8 @@ commands. It will be possible to perform the lookup for individual users, as shown in the procedure below.

        - - + + The use of this tool requires configuration of NSS as per the native use of winbind. Edit the /etc/nsswitch.conf so it has the following parameters:

        @@ -1200,11 +1200,11 @@
         

        The following procedure can be used to utilize the idmap_rid facility: -

        1. +

          1. Create or install and smb.conf file with the above configuration. -

          2. +

          3. Edit the /etc/nsswitch.conf file as shown above. -

          4. +

          5. Execute:

             root#  net ads join -UAdministrator%password
            @@ -1212,7 +1212,7 @@
             Joined 'BIGJOE' to realm 'CORP.KPAK.COM'
             

            - + An invalid or failed join can be detected by executing:

             root#  net ads testjoin
            @@ -1224,34 +1224,34 @@
                             The specific error message may differ from the above because it depends on the type of failure that
                             may have occurred. Increase the log level to 10, repeat the above test,
                             and then examine the log files produced to identify the nature of the failure.
            -                

          6. +

          7. Start the nmbd, winbind, and smbd daemons in the order shown. -

          8. +

          9. Validate the operation of this configuration by executing: - +

             root#  getent passwd administrator
             administrator:x:1000:1013:Administrator:/home/BE/administrator:/bin/bash
             

            -

        IDMAP Storage in LDAP using Winbind

        - - +

    IDMAP Storage in LDAP using Winbind

    + + The storage of IDMAP information in LDAP can be used with both NT4/Samba-3-style domains as well as with ADS domains. OpenLDAP is a commonly used LDAP server for this purpose, although any standards-compliant LDAP server can be used. It is therefore possible to deploy this IDMAP configuration using the Sun iPlanet LDAP server, Novell eDirectory, Microsoft ADS plus ADAM, and so on.

    The example in “Typical ADS Style Domain smb.conf File” is for an ADS-style domain. -

    Example 7.9. Typical ADS Style Domain smb.conf File

    # Global parameters
    [global]
    workgroup = SNOWSHOW
    netbios name = GOODELF
    realm = SNOWSHOW.COM
    server string = Samba Server
    security = ADS
    log level = 1 ads:10 auth:10 sam:10 rpc:10
    ldap admin dn = cn=Manager,dc=SNOWSHOW,dc=COM
    ldap idmap suffix = ou=Idmap
    ldap suffix = dc=SNOWSHOW,dc=COM
    idmap backend = ldap:ldap://ldap.snowshow.com
    idmap uid = 150000-550000
    idmap gid = 150000-550000
    template shell = /bin/bash
    winbind use default domain = Yes

    - +

    Example 7.9. Typical ADS Style Domain smb.conf File

    # Global parameters
    [global]
    workgroup = SNOWSHOW
    netbios name = GOODELF
    realm = SNOWSHOW.COM
    server string = Samba Server
    security = ADS
    log level = 1 ads:10 auth:10 sam:10 rpc:10
    ldap admin dn = cn=Manager,dc=SNOWSHOW,dc=COM
    ldap idmap suffix = ou=Idmap
    ldap suffix = dc=SNOWSHOW,dc=COM
    idmap backend = ldap:ldap://ldap.snowshow.com
    idmap uid = 150000-550000
    idmap gid = 150000-550000
    template shell = /bin/bash
    winbind use default domain = Yes

    + In the case of an NT4 or Samba-3-style domain the realm is not used, and the command used to join the domain is net rpc join. The above example also demonstrates advanced error reporting techniques that are documented in the chapter called "Reporting Bugs" in - The Official Samba-3 HOWTO and Reference Guide, Second Edition (TOSHARG2). + “The Official Samba-3 HOWTO and Reference Guide, Second Edition” (TOSHARG2).

    - - - + + + Where MIT kerberos is installed (version 1.3.4 or later), edit the /etc/krb5.conf file so it has the following contents:

    @@ -1290,7 +1290,7 @@
     [domain_realm]
             .snowshow.com = SNOWSHOW.COM
     

    -

    Note

    +

    Note

    Samba cannot use the Heimdal libraries if there is no /etc/krb5.conf file. So long as there is an empty file, the Heimdal kerberos libraries will be usable. There is no need to specify any settings because Samba, using the Heimdal libraries, can figure this out automatically. @@ -1306,8 +1306,8 @@ ...

    - - + + You will need the PADL nss_ldap tool set for this solution. Configure the /etc/ldap.conf file so it has the information needed. The following is an example of a working file: @@ -1326,16 +1326,16 @@

    The following procedure may be followed to affect a working configuration: -

    1. +

      1. Configure the smb.conf file as shown above. -

      2. +

      3. Create the /etc/krb5.conf file following the indications above. -

      4. +

      5. Configure the /etc/nsswitch.conf file as shown above. -

      6. +

      7. Download, build, and install the PADL nss_ldap tool set. Configure the /etc/ldap.conf file as shown above. -

      8. +

      9. Configure an LDAP server and initialize the directory with the top-level entries needed by IDMAP as shown in the following LDIF file:

        @@ -1355,35 +1355,35 @@
         objectClass: organizationalUnit
         ou: idmap
         

        -

      10. +

      11. Execute the command to join the Samba domain member server to the ADS domain as shown here:

         root#  net ads testjoin
         Using short domain name -- SNOWSHOW
         Joined 'GOODELF' to realm 'SNOWSHOW.COM'
         

        -

      12. +

      13. Store the LDAP server access password in the Samba secrets.tdb file as follows:

         root#  smbpasswd -w not24get
         

        -

      14. +

      15. Start the nmbd, winbind, and smbd daemons in the order shown.

      - + Follow the diagnostic procedures shown earlier in this chapter to identify success or failure of the join. In many cases a failure is indicated by a silent return to the command prompt with no indication of the reason for failure. -

    IDMAP and NSS Using LDAP from ADS with RFC2307bis Schema Extension

    - - +

    IDMAP and NSS Using LDAP from ADS with RFC2307bis Schema Extension

    + + The use of this method is messy. The information provided in this section is for guidance only and is very definitely not complete. This method does work; it is used in a number of large sites and has an acceptable level of performance.

    An example smb.conf file is shown in “ADS Membership Using RFC2307bis Identity Resolution smb.conf File”. -

    Example 7.10. ADS Membership Using RFC2307bis Identity Resolution smb.conf File

    # Global parameters
    [global]
    workgroup = BUBBAH
    netbios name = MADMAX
    realm = BUBBAH.COM
    server string = Samba Server
    security = ADS
    idmap uid = 150000-550000
    idmap gid = 150000-550000
    template shell = /bin/bash
    winbind use default domain = Yes
    winbind trusted domains only = Yes
    winbind nested groups = Yes

    - +

    Example 7.10. ADS Membership Using RFC2307bis Identity Resolution smb.conf File

    # Global parameters
    [global]
    workgroup = BUBBAH
    netbios name = MADMAX
    realm = BUBBAH.COM
    server string = Samba Server
    security = ADS
    idmap uid = 150000-550000
    idmap gid = 150000-550000
    template shell = /bin/bash
    winbind use default domain = Yes
    winbind trusted domains only = Yes
    winbind nested groups = Yes

    + The DMS must be joined to the domain using the usual procedure. Additionally, it is necessary to build and install the PADL nss_ldap tool set. Be sure to build this tool set with the following: @@ -1392,7 +1392,7 @@ make install

    - + The following /etc/nsswitch.conf file contents are required:

     ...
    @@ -1404,52 +1404,52 @@
     ...
     

    - - + + The /etc/ldap.conf file must be configured also. Refer to the PADL documentation and source code for nss_ldap instructions.

    The next step involves preparation on the ADS schema. This is briefly discussed in the remaining part of this chapter. -

    IDMAP, Active Directory, and MS Services for UNIX 3.5

    - +

    IDMAP, Active Directory, and MS Services for UNIX 3.5

    + The Microsoft Windows Service for UNIX version 3.5 is available for free download from the Microsoft Web site. You will need to download this tool and install it following Microsoft instructions. -

    IDMAP, Active Directory, and AD4UNIX

    +

    IDMAP, Active Directory, and AD4UNIX

    Instructions for obtaining and installing the AD4UNIX tool set can be found from the Geekcomix Web site. -

    UNIX/Linux Client Domain Member

    +

    UNIX/Linux Client Domain Member

    So far this chapter has been mainly concerned with the provision of file and print services for domain member servers. However, an increasing number of UNIX/Linux workstations are being installed that do not act as file or print servers to anyone other than a single desktop user. The key demand for desktop systems is to be able to log onto any UNIX/Linux or Windows desktop using the same network user credentials. -

    +

    The ability to use a common set of user credential across a variety of network systems is generally regarded as a single sign-on (SSO) solution. SSO systems are sold by a large number of vendors and include a range of technologies such as: -

    • +

      • Proxy sign-on -

      • +

      • Federated directory provisioning -

      • +

      • Metadirectory server solutions -

      • +

      • Replacement authentication systems -

      +

    There are really four solutions that provide integrated authentication and user identity management facilities: -

    • +

      • Samba winbind (free). Samba-3.0.20 introduced a complete replacement for Winbind that now provides a greater level of scalability in large ADS environments. -

      • +

      • PADL PAM and LDAP tools (free). -

      • +

      • Vintela Authentication Services (commercial). -

      • +

      • Centrify DirectControl (commercial). Centrify's commercial product allows UNIX and Linux systems to use Active Directory security, directory and policy services. Enhancements include a centralized ID mapping that @@ -1464,75 +1464,75 @@ provides logon services for UNIX/Linux users, while Windows users obtain their sign-on support via Samba-3.

        - + On the other hand, if the authentication and identity resolution backend must be provided by a Windows NT4-style domain or from an Active Directory Domain that does not have the Microsoft Windows Services for UNIX installed, winbind is your best friend. Specific guidance for these situations now follows.

        - - - + + + To permit users to log on to a Linux system using Windows network credentials, you need to configure identity resolution (NSS) and PAM. This means that the basic steps include those outlined above with the addition of PAM configuration. Given that most workstations (desktop/client) usually do not need to provide file and print services to a group of users, the configuration of shares and printers is generally less important. Often this allows the share specifications to be entirely removed from the smb.conf file. That is obviously an administrator decision. -

        NT4 Domain Member

        +

        NT4 Domain Member

        The following steps provide a Linux system that users can log onto using Windows NT4 (or Samba-3) domain network credentials: -

        1. +

          1. Follow the steps outlined in “NT4/Samba Domain with Samba Domain Member Server: Using NSS and Winbind” and ensure that all validation tests function as shown. -

          2. +

          3. Identify what services users must log on to. On Red Hat Linux, if it is intended that the user shall be given access to all services, it may be most expeditious to simply configure the file /etc/pam.d/system-auth. -

          4. +

          5. Carefully make a backup copy of all PAM configuration files before you begin making changes. If you break the PAM configuration, please note that you may need to use an emergency boot process to recover your Linux system. It is possible to break the ability to log into the system if PAM files are incorrectly configured. The entire directory /etc/pam.d should be backed up to a safe location. -

          6. +

          7. If you require only console login support, edit the /etc/pam.d/login so it matches “SUSE: PAM login Module Using Winbind”. -

          8. +

          9. To provide the ability to log onto the graphical desktop interface, you must edit the files gdm and xdm in the /etc/pam.d directory. -

          10. +

          11. Edit only one file at a time. Carefully validate its operation before attempting to reboot the machine. -

        ADS Domain Member

        +

    ADS Domain Member

    This procedure should be followed to permit a Linux network client (workstation/desktop) to permit users to log on using Microsoft Active Directory-based user credentials. -

    1. +

      1. Follow the steps outlined in “Active Directory Domain with Samba Domain Member Server” and ensure that all validation tests function as shown. -

      2. +

      3. Identify what services users must log on to. On Red Hat Linux, if it is intended that the user shall be given access to all services, it may be most expeditious to simply configure the file /etc/pam.d/system-auth as shown in “Red Hat 9: PAM System Authentication File: /etc/pam.d/system-auth Module Using Winbind”. -

      4. +

      5. Carefully make a backup copy of all PAM configuration files before you begin making changes. If you break the PAM configuration, please note that you may need to use an emergency boot process to recover your Linux system. It is possible to break the ability to log into the system if PAM files are incorrectly configured. The entire directory /etc/pam.d should be backed up to a safe location. -

      6. +

      7. If you require only console login support, edit the /etc/pam.d/login so it matches “SUSE: PAM login Module Using Winbind”. -

      8. +

      9. To provide the ability to log onto the graphical desktop interface, you must edit the files gdm and xdm in the /etc/pam.d directory. -

      10. +

      11. Edit only one file at a time. Carefully validate its operation before attempting to reboot the machine.

    Example 7.11. SUSE: PAM login Module Using Winbind

    @@ -1587,74 +1587,74 @@
     session     required      /lib/security/$ISA/pam_limits.so
     session     sufficient    /lib/security/$ISA/pam_unix.so
     session     sufficient    /lib/security/$ISA/pam_winbind.so use_first_pass
    -

    Key Points Learned

    +


    Key Points Learned

    The addition of UNIX/Linux Samba servers and clients is a common requirement. In this chapter, you learned how to integrate such servers so that the UID/GID mappings they use can be consistent across all domain member servers. You also discovered how to implement the ability to use Samba or Windows domain account credentials to log on to a UNIX/Linux client.

    The following are key points made in this chapter: -

    • +

      • Domain controllers are always authoritative for the domain. -

      • +

      • Domain members may have local accounts and must be able to resolve the identity of domain user accounts. Domain user account identity must map to a local UID/GID. That local UID/GID can be stored in LDAP. This way, it is possible to share the IDMAP data across all domain member machines. -

      • +

      • Resolution of user and group identities on domain member machines may be implemented using direct LDAP services or using winbind. -

      • +

      • On NSS/PAM enabled UNIX/Linux systems, NSS is responsible for identity management and PAM is responsible for authentication of logon credentials (username and password). -

    Questions and Answers

    +

    Questions and Answers

    The following questions were obtained from the mailing list and also from private discussions with Windows network administrators. -

    +

    We use NIS for all UNIX accounts. Why do we need winbind? -
    +
    Our IT management people do not like LDAP but are looking at Microsoft Active Directory. Which is better? -
    +
    We want to implement a Samba PDC, four Samba BDCs, and 10 Samba servers. Is it possible to use NIS in place of LDAP? -
    +
    Are you suggesting that users should not log on to a domain member server? If so, why? -
    +
    We want to ensure that only users from our own domain plus from trusted domains can use our Samba servers. In the smb.conf file on all servers, we have enabled the winbind trusted domains only parameter. We now find that users from trusted domains cannot access our servers, and users from Windows clients that are not domain members can also access our servers. Is this a Samba bug? -
    +
    What are the benefits of using LDAP for my domain member servers? -
    +
    Is proper DNS operation necessary for Samba-3 plus LDAP? If so, what must I put into my DNS configuration? -
    +
    Our Windows 2003 Server Active Directory domain runs with NetBIOS disabled. Can we use Samba-3 with that configuration? -
    +
    When I tried to execute net ads join, I got no output. It did not work, so I think that it failed. I then executed net rpc join and that worked fine. That is okay, isn't it? -

    +

    We use NIS for all UNIX accounts. Why do we need winbind?

    - - - - - - + + + + + + You can use NIS for your UNIX accounts. NIS does not store the Windows encrypted passwords that need to be stored in one of the acceptable passdb backends. Your choice of backend is limited to smbpasswd or tdbsam. Winbind is needed to handle the resolution of SIDs from trusted domains to local UID/GID values.

    - - + + On a domain member server, you effectively map Windows domain users to local users that are in your NIS database by specifying the winbind trusted domains only. This causes user and group account lookups to be routed via @@ -1662,17 +1662,17 @@ this pushes the resolution of users and groups out through NIS.

    As a general rule, it is always a good idea to run winbind on all Samba servers. -

    +

    Our IT management people do not like LDAP but are looking at Microsoft Active Directory. - Which is better? -

    + Which is better? +

    Microsoft Active Directory is an LDAP server that is intricately tied to a Kerberos infrastructure. Most IT managers who object to LDAP do so because an LDAP server is most often supplied as a raw tool that needs to be configured and for which the administrator must create the schema, create the administration tools, and devise the backup and recovery facilities in a site-dependent manner. LDAP servers in general are seen as a high-energy, high-risk facility. -

    +

    Microsoft Active Directory by comparison is easy to install and configure and is supplied with all tools necessary to implement and manage the directory. For sites that lack a lot of technical competence, Active Directory is a good choice. For sites @@ -1681,28 +1681,28 @@ the site want? If management wants a choice to use an alternative, they may want to consider the options. On the other hand, if management just wants a solution that works, Microsoft Active Directory is a good solution. -

    +

    We want to implement a Samba PDC, four Samba BDCs, and 10 Samba servers. Is it possible to use NIS in place of LDAP? -

    +

    Yes, it is possible to use NIS in place of LDAP, but there may be problems with keeping the Windows (SMB) encrypted passwords database correctly synchronized across the entire network. Workstations (Windows client machines) periodically change their domain membership secure account password. How can you keep changes that are on remote BDCs synchronized on the PDC? -

    +

    LDAP is a more elegant solution because it permits centralized storage and management of all network identities (user, group, and machine accounts) together with all information Samba needs to provide to network clients and their users. -

    +

    Are you suggesting that users should not log on to a domain member server? If so, why? -

    +

    Many UNIX administrators mock the model that the personal computer industry has adopted as normative since the early days of Novell NetWare. The old perception of the necessity to keep users off file and print servers was a result of fears concerning the security and integrity of data. It was a simple and generally effective measure to keep users away from servers, except through mapped drives. -

    +

    UNIX administrators are fully correct in asserting that UNIX servers and workstations are identical in terms of the software that is installed. They correctly assert that in a well-secured environment it is safe to store files on a system that has hundreds @@ -1711,25 +1711,25 @@ server the risk to operations through simple user errors. Only then can one begin to appraise the best strategy and adopt a site-specific policy that best protects the needs of users and of the organization alike. -

    +

    From experience, it is my recommendation to keep general system-level logins to a practical minimum and to eliminate them if possible. This should not be taken as a hard rule, though. The better question is, what works best for the site? -

    +

    We want to ensure that only users from our own domain plus from trusted domains can use our Samba servers. In the smb.conf file on all servers, we have enabled the winbind trusted domains only parameter. We now find that users from trusted domains cannot access our servers, and users from Windows clients that are not domain members can also access our servers. Is this a Samba bug? -

    +

    The manual page for this winbind trusted domains only parameter says, - This parameter is designed to allow Samba servers that are members of a Samba-controlled + “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 UIDs 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. This clearly suggests that you are trying + of allocating a new UID for him or her.” This clearly suggests that you are trying to use this parameter inappropriately. -

    +

    A far better solution is to use the valid users by specifying precisely the domain users and groups that should be permitted access to the shares. You could, for example, set the following parameters: @@ -1738,24 +1738,24 @@ path = /export/demodata valid users = @"Domain Users", @"OTHERDOMAIN\Domain Users"

    -

    +

    What are the benefits of using LDAP for my domain member servers? -

    +

    The key benefit of using LDAP is that the UID of all users and the GID of all groups are globally consistent on domain controllers as well as on domain member servers. This means that it is possible to copy/replicate files across servers without loss of identity. -

    +

    When use is made of account identity resolution via winbind, even when an IDMAP backend is stored in LDAP, the UID/GID on domain member servers is consistent, but differs from the ID that the user/group has on domain controllers. The winbind allocated UID/GID that is stored in LDAP (or locally) will be in the numeric range specified in the idmap uid/gid in the smb.conf file. On domain controllers, the UID/GID is that of the POSIX value assigned in the LDAP directory as part of the POSIX account information. -

    +

    Is proper DNS operation necessary for Samba-3 plus LDAP? If so, what must I put into my DNS configuration? -

    +

    Samba depends on correctly functioning resolution of hostnames to their IP address. Samba makes no direct DNS lookup calls, but rather redirects all name-to-address calls via the getXXXbyXXX() function calls. The configuration of the hosts @@ -1768,23 +1768,23 @@ this means that a hostname lookup first tries the /etc/hosts. If this fails to resolve, it attempts a DNS lookup, and if that fails, it tries a WINS lookup. -

    +

    The addition of the WINS-based name lookup makes sense only if NetBIOS over TCP/IP has been enabled on all Windows clients. Where NetBIOS over TCP/IP has been disabled, DNS is the preferred name resolution technology. This usually makes most sense when Samba is a client of an Active Directory domain, where NetBIOS use has been disabled. In this case, the Windows 200x autoregisters all locator records it needs with its own DNS server or servers. -

    +

    Our Windows 2003 Server Active Directory domain runs with NetBIOS disabled. Can we use Samba-3 with that configuration?

    Yes. -

    +

    When I tried to execute net ads join, I got no output. It did not work, so I think that it failed. I then executed net rpc join and that worked fine. That is okay, isn't it? -

    +

    No. This is not okay. It means that your Samba-3 client has joined the ADS domain as a Windows NT4 client, and Samba-3 will not be using Kerberos-based authentication.

    diff -u -r --new-file --exclude .svn --exclude CVS samba-3.3.10//docs/htmldocs/Samba3-ByExample/upgrades.html samba-3.3.11//docs/htmldocs/Samba3-ByExample/upgrades.html --- samba-3.3.10//docs/htmldocs/Samba3-ByExample/upgrades.html 2010-01-14 11:24:17.000000000 +0100 +++ samba-3.3.11//docs/htmldocs/Samba3-ByExample/upgrades.html 2010-02-22 16:53:36.000000000 +0100 @@ -1,14 +1,14 @@ -Chapter 8. Updating Samba-3

    Chapter 8. Updating Samba-3

    - - +Chapter 8. Updating Samba-3

    Chapter 8. Updating Samba-3

    + + It was a little difficult to select an appropriate title for this chapter. From email messages on the Samba mailing lists it is clear that many people consider the updating and upgrading of Samba to be a migration matter. Others talk about migrating Samba servers when in fact the issue at hand is one of installing a new Samba server to replace an older existing Samba server.

    - - + + There has also been much talk about migration of Samba-3 from an smbpasswd passdb backend to the use of the tdbsam or ldapsam facilities that are new to Samba-3. @@ -17,22 +17,22 @@ people apply to these modes by which Samba servers are updated. This is further highlighted by an email posting that included the following neat remark:

    - -I like the net rpc vampire on NT4, but that to my surprise does + +I like the “net rpc vampire” on NT4, but that to my surprise does not seem to work against a Samba PDC and, if addressed in the Samba to Samba context in either book, I could not find it.

    - + So in response to the significant request for these situations to be better documented, this chapter has now been added. User contributions and documentation of real-world experiences are a most welcome addition to this chapter. -

    Introduction

    - - - +

    Introduction

    + + + A Windows network administrator explained in an email what changes he was -planning to make and followed with the question: Anyone done this -before? Many of us have upgraded and updated Samba without incident. +planning to make and followed with the question: “Anyone done this +before?” Many of us have upgraded and updated Samba without incident. Others have experienced much pain and user frustration. So it is to be hoped that the notes in this chapter will make a positive difference by assuring that someone will be saved a lot of discomfort. @@ -43,29 +43,29 @@ this precautionary step, users will punish an administrator who fails to take adequate steps to avoid situations that may inflict lost productivity on them. -

    Warning

    - - +

    Warning

    + + Samba makes it possible to upgrade and update configuration files, but it is not possible to downgrade the configuration files. Please ensure that all configuration and control files are backed up to permit a down-grade in the rare event that this may be necessary.

    - - + + It is prudent also to backup all data files on the server before attempting to perform a major upgrade. Many administrators have experienced the consequences of failure to take adequate precautions. So what is adequate? That is simple! If data is lost during an upgrade or update and it can not be restored, the precautions taken were inadequate. If a backup was not needed, but was available, caution was on the side of the victor. -

    Cautions and Notes

    - Someone once said, It is good to be sorry, but better never to need to be! +

    Cautions and Notes

    + Someone once said, “It is good to be sorry, but better never to need to be!” These are wise words of advice to those contemplating a Samba upgrade or update.

    - - - + + + This is as good a time as any to define the terms upgrade and update. The term upgrade refers to the installation of a version of Samba that is a whole generation or more ahead of @@ -73,12 +73,12 @@ number. So far Samba has been released in generations 1.x, 2.x, 3.x, and currently 4.0 is in development.

    - + The term update refers to a minor version number installation in place of one of the same generation. For example, updating from Samba 3.0.10 to 3.0.14 is an update. The move from Samba 2.0.7 to 3.0.14 is an upgrade.

    - + While the use of these terms is an exercise in semantics, what needs to be realized is that there are major functional differences between a Samba 2.x release and a Samba 3.0.x release. Such differences may require a significantly different approach to @@ -86,17 +86,17 @@ latest documentation to identify precisely how the new installation may need to be modified to preserve prior functionality.

    - There is an old axiom that says, The greater the volume of the documentation, + There is an old axiom that says, “The greater the volume of the documentation, the greater the risk that noone will read it, but where there is no documentation, - noone can read it! While true, some documentation is an evil necessity. + noone can read it!” While true, some documentation is an evil necessity. It is hoped that this update to the documentation will avoid both extremes. -

    Security Identifiers (SIDs)

    - - - - - - +

    Security Identifiers (SIDs)

    + + + + + + Before the days of Windows NT and OS/2, every Windows and DOS networking client that used the SMB protocols was an entirely autonomous entity. There was no concept of a security identifier for a machine or a user outside of the username, the @@ -104,46 +104,46 @@ in the same context as the way that the SID is used since the development of Windows NT 3.10.

    - - - - - - + + + + + + Versions of Samba prior to 1.9 did not make use of a SID. Instead they make exclusive use of the username that is embedded in the SessionSetUpAndX component of the connection setup process between a Windows client and an SMB/CIFS server.

    - - - + + + Around November 1997 support was added to Samba-1.9 to handle the Windows security RPC-based protocols that implemented support for Samba to store a machine SID. This information was stored in a file called MACHINE.SID.

    - - - + + + Within the lifetime of the early Samba 2.x series, the machine SID information was relocated into a tdb file called secrets.tdb, which is where it is still located in Samba 3.0.x along with other information that pertains to the local machine and its role within a domain security context.

    - - - - + + + + There are two types of SID, those pertaining to the machine itself and the domain to which it may belong, and those pertaining to users and groups within the security context of the local machine, in the case of standalone servers (SAS) and domain member servers (DMS).

    - - - - - - + + + + + + When the Samba smbd daemon is first started, if the secrets.tdb file does not exist, it is created at the first client connection attempt. If this file does exist, smbd checks that there is a machine SID (if it is a domain controller, @@ -153,31 +153,31 @@ manner. This means that each time it is generated for a particular combination of machine name (hostname) and domain name (workgroup), it will be different.

    - + The SID is the key used by MS Windows networking for all networking operations. This means that when the machine or domain SID changes, all security-encoded objects such as profiles and ACLs may become unusable. -

    Note

    +

    Note

    It is of paramount importance that the machine and domain SID be backed up so that in the event of a change of hostname (machine name) or domain name (workgroup) the SID can be restored to its previous value.

    - - - - - - - - - - + + + + + + + + + + In Samba-3 on a domain controller (PDC or BDC), the domain name controls the domain SID. On all prior versions the hostname (computer name, or NetBIOS name) controlled the SID. On a standalone server the hostname still controls the SID.

    - - + + The local machine SID can be backed up using this procedure (Samba-3):

     root#  net getlocalsid > /etc/samba/my-local-SID
    @@ -200,7 +200,7 @@
     	ability to read the older tdb file and to perform an in-situ update to the latest tdb format.
     	This is not a reversible process  it is a one-way upgrade.
     	

    - + In the course of the Samba 2.0.x series the smbpasswd was modified to permit the domain SID to be captured to the secrets.tdb file by executing:

    @@ -217,8 +217,8 @@
     root#  smbpasswd -W S-1-5-21-726309263-4128913605-1168186429
     

    - - + + Domain security information, which includes the domain SID, can be obtained from Samba-2.2.x systems by executing:

    @@ -237,9 +237,9 @@
     	It is a very good practice to store this SID information in a safely kept file, just in
     	case it is ever needed at a later date.
     	

    - - - + + + Take note that the domain SID is used extensively in Samba. Where LDAP is used for the passdb backend, all user, group, and trust accounts are encoded with the domain SID. This means that if the domain SID changes for any reason, the entire @@ -250,9 +250,9 @@ root# slapcat -v -l filename.ldif

    - - - + + + When the domain SID has changed, roaming profiles cease to be functional. The recovery of roaming profiles necessitates resetting of the domain portion of the user SID that owns the profile. This is encoded in the NTUser.DAT and can be @@ -261,9 +261,9 @@ complain to the Samba Team if this utility is missing; that issue that must be addressed to the creator of the RPM package. The Samba Team do their best to make available all the tools needed to manage a Samba-based Windows networking environment. -

    Change of hostname

    - - +

    Change of hostname

    + + Samba uses two methods by which the primary NetBIOS machine name (also known as a computer name or the hostname) may be determined: If the smb.conf file contains a netbios name entry, its value will be used directly. In the absence @@ -273,26 +273,26 @@ hostname was changed for one reason or another. Such a change will cause a new machine SID to be generated. If this happens on a domain controller, it will also change the domain SID. These SIDs can be updated (restored) using the procedure outlined previously. -

    Note

    +

    Note

    Do NOT change the hostname or the netbios name. If this is changed, be sure to reset the machine SID to the original setting. Otherwise there may be serious interoperability and/or operational problems. -

    Change of Workgroup (Domain) Name

    - +

    Change of Workgroup (Domain) Name

    + The domain name of a Samba server is identical to the workgroup name and is set in the smb.conf file using the workgroup parameter. This has been consistent throughout the history of Samba and across all versions.

    - + Be aware that when the workgroup name is changed, a new SID will be generated. The old domain SID can be reset using the procedure outlined earlier in this chapter. -

    Location of config files

    +

    Location of config files

    The Samba-Team has maintained a constant default location for all Samba control files throughout the life of the project. People who have produced binary packages of Samba have varied the location of the Samba control files. This has led to some confusion for network administrators.

    - + The Samba 1.9.x smb.conf file may be found either in the /etc directory or in /usr/local/samba/lib.

    @@ -300,12 +300,12 @@ on Linux systems to the /etc/samba directory where it remains located also for Samba 3.0.x installations.

    - + Samba 2.x introduced the secrets.tdb file that is also stored in the /etc/samba directory, or in the /usr/local/samba/lib directory subsystem.

    - + The location at which smbd expects to find all configuration and control files is determined at the time of compilation of Samba. For versions of Samba prior to 3.0, one way to find the expected location of these files is to execute: @@ -317,7 +317,7 @@ Note: The smbd executable may be located in the path /usr/local/samba/sbin.

    - + Samba-3 provides a neat new way to track the location of all control files as well as to find the compile-time options used as the Samba package was built. Here is how the dark secrets of the internals of the location of control files within Samba executables can @@ -348,37 +348,37 @@ ...

    - + It is important that both the smb.conf file and the secrets.tdb be backed up before attempting any upgrade. The secrets.tdb file is version-encoded, and therefore a newer version may not work with an older version of Samba. A backup means that it is always possible to revert a failed or problematic upgrade. -

    International Language Support

    - - - - +

    International Language Support

    + + + + Samba-2.x had no support for Unicode; instead, all national language character-set support in file names was done using particular locale codepage mapping techniques. Samba-3 supports Unicode in file names, thus providing true internationalization support.

    - + Non-English users whose national language character set has special characters and who upgrade naively will find that many files that have the special characters in the file name will see them garbled and jumbled up. This typically happens with umlauts and accents because these characters were particular to the codepage that was in use with Samba-2.x using an 8-bit encoding scheme.

    - + Files that are created with Samba-3 will use UTF-8 encoding. Should the file system ever end up with a mix of codepage (unix charset)-encoded file names and UTF-8-encoded file names, the mess will take some effort to set straight.

    - + A very helpful tool is available from Bjorn Jacke's convmv work. Convmv is a tool that can be used to convert file and directory names from one encoding method to another. The most common use for this tool is to convert locale-encoded files to UTF-8 Unicode encoding. -

    Updates and Changes in Idealx smbldap-tools

    +

    Updates and Changes in Idealx smbldap-tools

    The smbldap-tools have been maturing rapidly over the past year. With maturation comes change. The location of the smbldap.conf and the smbldap_bind.conf configuration files have been moved from the directory /etc/smbldap-tools to @@ -392,7 +392,7 @@ sambaDomainName. Anyone who updates from an older version to the current release should note that the information stored under NextFreeUnixId must now be relocated to the DIT object sambaDomainName. -

    Upgrading from Samba 1.x and 2.x to Samba-3

    +

    Upgrading from Samba 1.x and 2.x to Samba-3

    Sites that are being upgraded from Samba-2 (or earlier versions) to Samba-3 may experience little difficulty or may require a lot of effort, depending on the complexity of the configuration. Samba-1.9.x upgrades to Samba-3 will @@ -402,31 +402,31 @@ There are two basic modes of use of Samba versions prior to Samba-3. The first does not use LDAP, the other does. Samba-1.9.x did not provide LDAP support. Samba-2.x could be compiled with LDAP support. -

    Samba 1.9.x and 2.x Versions Without LDAP

    +

    Samba 1.9.x and 2.x Versions Without LDAP

    Where it is necessary to upgrade an old Samba installation to Samba-3, the following procedure can be followed: -

    Procedure 8.1. Upgrading from a Pre-Samba-3 Version

    1. - - - +

      Procedure 8.1. Upgrading from a Pre-Samba-3 Version

      1. + + + Stop Samba. This can be done using the appropriate system tool that is particular for each operating system or by executing the kill command on smbd, nmbd, and winbindd. -

      2. +

      3. Find the location of the Samba smb.conf file and back it up to a safe location. -

      4. +

      5. Find the location of the smbpasswd file and back it up to a safe location. -

      6. +

      7. Find the location of the secrets.tdb file and back it up to a safe location. -

      8. - - - - +

      9. + + + + Find the location of the lock directory. This is the directory in which Samba stores all its tdb control files. The default location used by the Samba Team is in @@ -436,8 +436,8 @@ Linux Standards Base specified location is now under the /var/lib/samba directory. Copy all the tdb files to a safe location. -

      10. - +

      11. + It is now safe to upgrade the Samba installation. On Linux systems it is not necessary to remove the Samba RPMs because a simple upgrade installation will automatically remove the old files. @@ -446,17 +446,17 @@ it is advisable either to delete the Samba old installation or to move it out of the way by renaming the directories that contain the Samba binary files. -

      12. +

      13. When the Samba upgrade has been installed, the first step that should be completed is to identify the new target locations for the control files. Follow the steps shown in “Location of config files” to locate the correct directories to which each control file must be moved. -

      14. +

      15. Do not change the hostname. -

      16. +

      17. Do not change the workgroup name. -

      18. - +

      19. + Execute the testparm to validate the smb.conf file. This process will flag any parameters that are no longer supported. It will also flag configuration settings that may be in conflict. @@ -468,67 +468,67 @@ root# cd /etc/samba root# testparm -s smb.conf.master > smb.conf

        - + The resulting smb.conf file will be stripped of all comments and of all nonconforming configuration settings. -

      20. - +

      21. + It is now safe to start Samba using the appropriate system tool. Alternately, it is possible to just execute nmbd, smbd, and winbindd for the command line while logged in as the root user. -

    Applicable to All Samba 2.x to Samba-3 Upgrades

    - - - +

    Applicable to All Samba 2.x to Samba-3 Upgrades

    + + + Samba 2.x servers that were running as a domain controller (PDC) require changes to the configuration of the scripting interface tools that Samba uses to perform OS updates for users, groups, and trust accounts (machines and interdomain).

    - + The following parameters are new to Samba-3 and should be correctly configured. Please refer to “Secure Office Networking” through “A Distributed 2000-User Network” in this book for examples of use of the new parameters shown here: - - - - - - - + + + + + + +

    -

    add group script

    add machine script

    add user to group script

    delete group script

    delete user from group script

    passdb backend

    set primary group script

    +

    add group script

    add machine script

    add user to group script

    delete group script

    delete user from group script

    passdb backend

    set primary group script

    - - + + The add machine script functionality was previously handled by the add user script, which in Samba-3 is used exclusively to add user accounts.

    - - - - - - - - - + + + + + + + + + Where the passdb backend used is either smbpasswd (the default) or the new tdbsam, the system interface scripts are typically used. These involve use of OS tools such as useradd, usermod, userdel, groupadd, groupmod, groupdel, and so on.

    - - - + + + Where the passdb backend makes use of an LDAP directory, it is necessary either to use the smbldap-tools provided by Idealx or to use an alternate toolset provided by a third party or else home-crafted to manage the LDAP directory accounts. -

    Samba-2.x with LDAP Support

    +

    Samba-2.x with LDAP Support

    Samba version 2.x could be compiled for use either with or without LDAP. The LDAP control settings in the smb.conf file in this old version are completely different (and less complete) than they are with Samba-3. This @@ -538,8 +538,8 @@ Follow the procedure outlined in “Samba 1.9.x and 2.x Versions Without LDAP” to affect a migration of all files to the correct locations.

    - - + + The Samba SAM schema required for Samba-3 is significantly different from that used with Samba 2.x. This means that the LDAP directory must be updated using the procedure outlined in the Samba WHATSNEW.txt file that accompanies @@ -694,19 +694,19 @@ Due to a limitation in Samba's smb.conf parsing, you should not surround the DN's with quotation marks.

    -

    Updating a Samba-3 Installation

    +

    Updating a Samba-3 Installation

    The key concern in this section is to deal with the changes that have been affected in Samba-3 between the Samba-3.0.0 release and the current update. Network administrators have expressed concerns over the steps that should be taken to update Samba-3 versions.

    - + The information in “Location of config files” would not be necessary if every person who has ever produced Samba executable (binary) files could agree on the preferred location of the smb.conf file and other Samba control files. Clearly, such agreement is further away than a pipedream.

    - + Vendors and packagers who produce Samba binary installable packages do not, as a rule, use the default paths used by the Samba-Team for the location of the binary files, the smb.conf file, and the Samba control files (tdb's @@ -719,54 +719,54 @@ uninformed administrator deals with apparent failure of the update to take effect.

    - + The best advice for those lacking in code compilation experience is to use only vendor (or Samba-Team) provided binary packages. The Samba packages that are provided by the Samba-Team are generally built to use file paths that are compatible with the original OS vendor's practices.

    - - + + If you are not sure whether a binary package complies with the OS vendor's practices, it is better to ask the package maintainer via email than to waste much time dealing with the nuances. Alternately, just diagnose the paths specified by the binary files following the procedure outlined above. -

    Samba-3 to Samba-3 Updates on the Same Server

    +

    Samba-3 to Samba-3 Updates on the Same Server

    The guidance in this section deals with updates to an existing Samba-3 server installation. -

    Updating from Samba Versions Earlier than 3.0.5

    +

    Updating from Samba Versions Earlier than 3.0.5

    With the provision that the binary Samba-3 package has been built with the same path and feature settings as the existing Samba-3 package that is being updated, an update of Samba-3 versions 3.0.0 through 3.0.4 can be updated to 3.0.5 without loss of functionality and without need to change either the smb.conf file or, where used, the LDAP schema. -

    Updating from Samba Versions between 3.0.6 and 3.0.10

    - - +

    Updating from Samba Versions between 3.0.6 and 3.0.10

    + + When updating versions of Samba-3 prior to 3.0.6 to 3.0.6 through 3.0.10, it is necessary only to update the LDAP schema (where LDAP is used). Always use the LDAP schema file that is shipped with the latest Samba-3 update.

    - - - + + + Samba-3.0.6 introduced the ability to remember the last n number of passwords a user has used. This information will work only with the tdbsam and ldapsam passdb backend facilities.

    After updating the LDAP schema, do not forget to re-index the LDAP database. -

    Updating from Samba Versions after 3.0.6 to a Current Release

    - +

    Updating from Samba Versions after 3.0.6 to a Current Release

    + Samba-3.0.8 introduced changes in how the username map behaves. It also included a change in behavior of winbindd. Please refer to the man page for smb.conf before implementing any update from versions prior to 3.0.8 to a current version.

    - + In Samba-3.0.11 a new privileges interface was implemented. Please refer to “Addition of Machines to the Domain” for information regarding this new feature. It is not necessary to implement the privileges interface, but it @@ -788,12 +788,12 @@ below the machine suffix. Previous Samba releases would fall back to searching the 'ldap suffix' in some cases.

    -

    Migrating Samba-3 to a New Server

    +

    Migrating Samba-3 to a New Server

    The two most likely candidates for replacement of a server are domain member servers and domain controllers. Each needs to be handled slightly differently. -

    Replacing a Domain Member Server

    - +

    Replacing a Domain Member Server

    + Replacement of a domain member server should be done using the same procedure as outlined in “Adding Domain Member Servers and Clients”.

    @@ -802,12 +802,12 @@ that the new server be renamed to that of the old server. This will change its SID and will necessitate rejoining to the domain.

    - - - - - - + + + + + + Following a change of hostname (NetBIOS name) it is a good idea on all servers to shut down the Samba smbd, nmbd, and winbindd services, delete the wins.dat @@ -817,10 +817,10 @@ resolution problems. These problems usually clear within 45 minutes of a name change, but can persist for a longer period of time.

    - - - - + + + + If the old domain member server had local accounts, it is necessary to create on the new domain member server the same accounts with the same UID and GID for each account. Where the passdb backend database @@ -831,13 +831,13 @@ /etc/group files. In this case, be sure to copy these account entries to the new target server.

    - + Where the user accounts for both UNIX and Samba are stored in LDAP, the new target server must be configured to use the nss_ldap tool set. This will automatically ensure that the appropriate user entities are available on the new server. -

    Replacing a Domain Controller

    - +

    Replacing a Domain Controller

    + In the past, people who replaced a Windows NT4 domain controller typically installed a new server, created printers and file shares on it, then migrate across all data that was destined to reside on it. The same can of course be done with @@ -847,7 +847,7 @@ have the intent to just replace the old Samba server with a new one with the same name as the old one. In this case, simply follow the same process as for upgrading a Samba 2.x system and do the following: -

    • +

      • Where UNIX (POSIX) user and group accounts are stored in the system /etc/passwd, /etc/shadow, and /etc/group files, be sure to add the same accounts @@ -862,19 +862,19 @@ slapadd command. Do not forget to install and configure the nss_ldap tool and the /etc/nsswitch.conf (as shown in “Making Happy Users”). -

      • +

      • Copy the smb.conf file from the old server to the new server into the correct location as indicated previously in this chapter. -

      • +

      • Copy the secrets.tdb file, the smbpasswd file (if it is used), the /etc/samba/passdb.tdb file (only used by the tdbsam backend), and all the tdb control files from the old system to the correct location on the new system. -

      • +

      • Before starting the Samba daemons, verify that the hostname of the new server is identical to that of the old one. Note: The IP address can be different from that of the old server. -

      • +

      • Copy all files from the old server to the new server, taking precaution to preserve all file ownership and permissions as well as any POSIX ACLs that may have been created on the old server. @@ -890,31 +890,31 @@ or the netbios name is set to the original server name, Samba should correctly pick up the original SID and preserve all other settings. It is sound advice to validate this before turning the system over to users. -

    Migration of Samba Accounts to Active Directory

    +

    Migration of Samba Accounts to Active Directory

    Yes, it works. The Windows ADMT tool can be used to migrate Samba accounts to MS Active Directory. There are a few pitfalls to be aware of: -

    Procedure 8.2. Migration to Active Directory

    1. +

      Procedure 8.2. Migration to Active Directory

      1. Administrator password must be THE SAME on the Samba server, the 2003 ADS, and the local Administrator account on the workstations. Perhaps this goes without saying, but there needs to be an account called Administrator in your Samba domain, with full administrative (root) rights to that domain. -

      2. +

      3. In the Advanced/DNS section of the TCP/IP settings on your Windows workstations, make sure the DNS suffix for this connection field is blank. -

      4. +

      5. Because you are migrating from Samba, user passwords cannot be migrated. You'll have to reset everyone's passwords. (If you were migrating from NT4 to ADS, you could migrate passwords as well.)

        To date this has not been attempted with roaming profile support; it has been documented as working with local profiles. -

      6. +

      7. Disable the Windows Firewall on all workstations. Otherwise, workstations won't be migrated to the new domain. -

      8. - +

      9. + When migrating machines, always test first (using ADMT's test mode) and satisfy all errors before committing the migration. Note that the test will always fail, because the machine will not have been actually @@ -922,23 +922,23 @@ failure was due to a problem or simply to the fact that it was just a test.

      - + There are some significant benefits of using the ADMT, besides just migrating user accounts. ADMT can be found on the Windows 2003 CD. -

      • +

        • You can migrate workstations remotely. You can specify that SIDs be simply added instead of replaced, giving you the option of joining a workstation back to the old domain if something goes awry. The workstations will be joined to the new domain. -

        • +

        • Not only are user accounts migrated from the old domain to the new domain, but ACLs on the workstations are migrated as well. Like SIDs, ACLs can be added instead of replaced. -

        • +

        • Locally stored user profiles on workstations are migrated as well, presenting almost no disruption to the user. Saved passwords will be lost, just as when you administratively reset the password in Windows ADS. -

        • +

        • The ADMT lets you test all operations before actually performing the migration. Accounts and workstations can be migrated individually or in batches. User accounts can be safely migrated all at once (since no diff -u -r --new-file --exclude .svn --exclude CVS samba-3.3.10//docs/htmldocs/Samba3-Developers-Guide/architecture.html samba-3.3.11//docs/htmldocs/Samba3-Developers-Guide/architecture.html --- samba-3.3.10//docs/htmldocs/Samba3-Developers-Guide/architecture.html 2010-01-14 11:24:58.000000000 +0100 +++ samba-3.3.11//docs/htmldocs/Samba3-Developers-Guide/architecture.html 2010-02-22 16:53:36.000000000 +0100 @@ -1,4 +1,4 @@ -Chapter 3. Samba Architecture

          Chapter 3. Samba Architecture

          Dan Shearer

          November 1997

          Introduction

          +Chapter 3. Samba Architecture

          Chapter 3. Samba Architecture

          Dan Shearer

          November 1997

          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 @@ -6,10 +6,10 @@ protocol.

          It also tries to answer some of the frequently asked questions such as: -

          1. +

            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. @@ -26,32 +26,32 @@ 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. +

      1. It's not only to create threads instead of processes, but you must care about all variables if they have to be thread specific (currently they would be global). -

      2. +

      3. if one thread dies (eg. a seg fault) then all threads die. We can immediately throw robustness out the window. -

      4. +

      5. many of the system calls we make are blocking. Non-blocking equivalents of many calls are either not available or are awkward (and slow) to use. So while we block in one thread all clients are waiting. Imagine if one share is a slow NFS filesystem and the others are fast, we will end up slowing all clients to the speed of NFS. -

      6. +

      7. you can't run as a different uid in different threads. This means we would have to switch uid/gid on _every_ SMB packet. It would be horrendously slow. -

      8. +

      9. the per process file descriptor limit would mean that we could only support a limited number of clients. -

      10. +

      11. 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 @@ -78,7 +78,7 @@ 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 diff -u -r --new-file --exclude .svn --exclude CVS samba-3.3.10//docs/htmldocs/Samba3-Developers-Guide/CodingSuggestions.html samba-3.3.11//docs/htmldocs/Samba3-Developers-Guide/CodingSuggestions.html --- samba-3.3.10//docs/htmldocs/Samba3-Developers-Guide/CodingSuggestions.html 2010-01-14 11:24:58.000000000 +0100 +++ samba-3.3.11//docs/htmldocs/Samba3-Developers-Guide/CodingSuggestions.html 2010-02-22 16:53:36.000000000 +0100 @@ -1,4 +1,4 @@ -Chapter 6. Coding Suggestions

    Chapter 6. Coding Suggestions

    Steve French

    Simo Sorce

    Andrew Bartlett

    Tim Potter

    Martin Pool

    +Chapter 6. Coding Suggestions

    Chapter 6. Coding Suggestions

    Steve French

    Simo Sorce

    Andrew Bartlett

    Tim Potter

    Martin Pool

    So you want to add code to Samba ...

    One of the daunting tasks facing a programmer attempting to write code for @@ -39,91 +39,91 @@ Standard) perfectly.

    Here are some other suggestions: -

    1. +

      1. use d_printf instead of printf for display text reason: enable auto-substitution of translated language text -

      2. +

      3. use SAFE_FREE instead of free reason: reduce traps due to null pointers -

      4. +

      5. don't use bzero use memset, or ZERO_STRUCT and ZERO_STRUCTP macros reason: not POSIX -

      6. +

      7. don't use strcpy and strlen (use safe_* equivalents) reason: to avoid traps due to buffer overruns -

      8. +

      9. don't use getopt_long, use popt functions instead reason: portability -

      10. +

      11. explicitly add const qualifiers on parm passing in functions where parm is input only (somewhat controversial but const can be #defined away) -

      12. +

      13. when passing a va_list as an arg, or assigning one to another please use the VA_COPY() macro reason: on some platforms, va_list is a struct that must be initialized in each function...can SEGV if you don't. -

      14. +

      15. discourage use of threads reason: portability (also see architecture.doc) -

      16. +

      17. don't explicitly include new header files in C files - new h files should be included by adding them once to includes.h reason: consistency -

      18. +

      19. don't explicitly extern functions (they are autogenerated by "make proto" into proto.h) reason: consistency -

      20. +

      21. use endian safe macros when unpacking SMBs (see byteorder.h and internals.doc) reason: not everyone uses Intel -

      22. +

      23. Note Unicode implications of charset handling (see internals.doc). See pull_* and push_* and convert_string functions. reason: Internationalization -

      24. +

      25. Don't assume English only reason: See above -

      26. +

      27. Try to avoid using in/out parameters (functions that return data which overwrites input parameters) reason: Can cause stability problems -

      28. +

      29. Ensure copyright notices are correct, don't append Tridge's name to code that he didn't write. If you did not write the code, make sure that it can coexist with the rest of the Samba GPLed code. -

      30. +

      31. Consider usage of DATA_BLOBs for length specified byte-data. reason: stability -

      32. +

      33. Take advantage of tdbs for database like function reason: consistency -

      34. +

      35. Don't access the SAM_ACCOUNT structure directly, they should be accessed via pdb_get...() and pdb_set...() functions. reason: stability, consistency -

      36. +

      37. Don't check a password directly against the passdb, always use the check_password() interface. reason: long term pluggability -

      38. +

      39. Try to use asprintf rather than pstrings and fstrings where possible -

      40. +

      41. Use normal C comments / * instead of C++ comments // like this. Although the C++ comment format is part of the C99 standard, some older vendor C compilers do not accept it. -

      42. +

      43. Try to write documentation for API functions and structures explaining the point of the code, the way it should be used, and any special conditions or results. Mark these with a double-star comment start / ** so that they can be picked up by Doxygen, as in this file. -

      44. +

      45. Keep the scope narrow. This means making functions/variables static whenever possible. We don't want our namespace polluted. Each module should have a minimal number of externally visible functions or variables. -

      46. +

      47. Use function pointers to keep knowledge about particular pieces of code isolated in one place. We don't want a particular piece of functionality to be spread out across lots of places - that makes @@ -131,7 +131,7 @@ and use tables containing function pointers to implement specific functionality. This is particularly important for command interpreters. -

      48. +

      49. Think carefully about what it will be like for someone else to add to and maintain your code. If it would be hard for someone else to maintain then do it another way. diff -u -r --new-file --exclude .svn --exclude CVS samba-3.3.10//docs/htmldocs/Samba3-Developers-Guide/contributing.html samba-3.3.11//docs/htmldocs/Samba3-Developers-Guide/contributing.html --- samba-3.3.10//docs/htmldocs/Samba3-Developers-Guide/contributing.html 2010-01-14 11:24:59.000000000 +0100 +++ samba-3.3.11//docs/htmldocs/Samba3-Developers-Guide/contributing.html 2010-02-22 16:53:36.000000000 +0100 @@ -1,4 +1,4 @@ -Chapter 7. Contributing code

        Chapter 7. Contributing code

        Jelmer R. Vernooij

        The Samba Team

        Here are a few tips and notes that might be useful if you are +Chapter 7. Contributing code

        Chapter 7. Contributing code

        Jelmer R. The Samba Team Vernooij

        The Samba Team

        Here are a few tips and notes that might be useful if you are interested in modifying samba source code and getting it into samba's main branch.

        Retrieving the source

        In order to contribute code to samba, make sure you have the latest source. Retrieving the samba source code from CVS is @@ -16,14 +16,14 @@

        If you are modifying a copy of samba you retrieved from CVS, you can easily generate a diff file of these changes by running cvs diff -u.

        Points of attention when modifying samba source code

        -

        • Don't simply copy code from other places and modify it until it +

          • Don't simply copy code from other places and modify it until it works. Code needs to be clean and logical. Duplicate - code is to be avoided.

          • Test your patch. It might take a while before one of us looks + code is to be avoided.

          • Test your patch. It might take a while before one of us looks at your patch so it will take longer before your patch when your patch - needs to go thru the review cycle again.

          • Don't put separate patches in one large diff file. This makes + needs to go thru the review cycle again.

          • Don't put separate patches in one large diff file. This makes it harder to read, understand and test the patch. You might also risk not getting a good patch committed because you mixed it - with one that had issues.

          • Make sure your patch complies to the samba coding style as + with one that had issues.

          • Make sure your patch complies to the samba coding style as suggested in the coding-suggestions chapter.

        Sending in bugfixes

        Bugfixes to bugs in samba should be submitted to samba's bugzilla system, diff -u -r --new-file --exclude .svn --exclude CVS samba-3.3.10//docs/htmldocs/Samba3-Developers-Guide/debug.html samba-3.3.11//docs/htmldocs/Samba3-Developers-Guide/debug.html --- samba-3.3.10//docs/htmldocs/Samba3-Developers-Guide/debug.html 2010-01-14 11:24:58.000000000 +0100 +++ samba-3.3.11//docs/htmldocs/Samba3-Developers-Guide/debug.html 2010-02-22 16:53:36.000000000 +0100 @@ -1,4 +1,4 @@ -Chapter 4. The samba DEBUG system

        Chapter 4. The samba DEBUG system

        Chris Hertel

        July 1998

        New Output Syntax

        +Chapter 4. The samba DEBUG system

        Chapter 4. The samba DEBUG system

        Chris Hertel

        July 1998

        New Output Syntax

        The syntax of a debugging log file is represented as:

           >debugfile< :== { >debugmsg< }
        @@ -25,12 +25,12 @@
         

        LINE is the line number of the debug statement that generated the message. -

        Basically, what that all means is:

        1. +

          Basically, what that all means is:

          1. A debugging log file is made up of debug messages. -

          2. +

          3. Each debug message is made up of a header and text. The header is separated from the text by a newline. -

          4. +

          5. The header begins with the timestamp and debug level of the message enclosed in brackets. The filename, function, and line number at which the message was generated follow. The filename is @@ -38,7 +38,7 @@ parenthesis which contain the line number. Depending upon the compiler, the function name may be missing (it is generated by the __FUNCTION__ macro, which is not universally implemented, dangit). -

          6. +

          7. The message text is made up of zero or more lines, each terminated by a newline.

          Here's some example output:

          @@ -51,7 +51,7 @@
           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. @@ -102,7 +102,7 @@ [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 @@ -116,7 +116,7 @@ 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: @@ -143,15 +143,15 @@ 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 dbgtext() function is explained below.)

          There are a few advantages to this scheme:

          1. The test is performed only once. -

          2. +

          3. You can allocate variables off of the stack that will only be used within the DEBUGLVL() block. -

          4. +

          5. 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 @@ -160,7 +160,7 @@ 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 @@ -168,7 +168,7 @@

    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 diff -u -r --new-file --exclude .svn --exclude CVS samba-3.3.10//docs/htmldocs/Samba3-Developers-Guide/devprinting.html samba-3.3.11//docs/htmldocs/Samba3-Developers-Guide/devprinting.html --- samba-3.3.10//docs/htmldocs/Samba3-Developers-Guide/devprinting.html 2010-01-14 11:25:00.000000000 +0100 +++ samba-3.3.11//docs/htmldocs/Samba3-Developers-Guide/devprinting.html 2010-02-22 16:53:36.000000000 +0100 @@ -1,27 +1,27 @@ -Chapter 15. Samba Printing Internals

    Chapter 15. Samba Printing Internals

    Gerald Carter

    October 2002

    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 function prototypes are defined in the printif structure declared in printing.h. -

    • retrieve the contents of a print queue

    • pause the print queue

    • resume a paused print queue

    • delete a job from the queue

    • pause a job in the print queue

    • result a paused print job in the queue

    • submit a job to the print queue

    +

    • retrieve the contents of a print queue

    • pause the print queue

    • resume a paused print queue

    • delete a job from the queue

    • pause a job in the print queue

    • result a paused print job in the queue

    • submit a job to the print queue

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

    +

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

    Print Queue TDB's

    Samba provides periodic caching of the output from the "lpq command" @@ -77,12 +77,12 @@

    When updating a print queue, smbd will perform the following steps ( refer to print.c:print_queue_update() ): -

    1. Check to see if another smbd is currently in +

      1. Check to see if another smbd is currently in the process of updating the queue contents by checking the pid stored in LOCK/printer_name. - If so, then do not update the TDB.

      2. Lock the mutex entry in the TDB and store our own pid. - Check that this succeeded, else fail.

      3. Store the updated time stamp for the new cache - listing

      4. Retrieve the queue listing via "lpq command"

      5. +	If so, then do not update the TDB.

      6. Lock the mutex entry in the TDB and store our own pid. + Check that this succeeded, else fail.

      7. Store the updated time stamp for the new cache + listing

      8. Retrieve the queue listing via "lpq command"

      9.  	foreach job in the queue
              	{
         		if the job is a UNIX job, create a new entry;
        @@ -94,8 +94,8 @@
         			else
         				update the job status only
         		}
        -	}
      10. Delete any jobs in the TDB that are not - in the in the lpq listing

      11. Store the print queue status in the TDB

      12. update the cache time stamp again

      + }

    2. Delete any jobs in the TDB that are not + in the in the lpq listing

    3. Store the print queue status in the TDB

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

    @@ -110,11 +110,11 @@ 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 @@ -127,10 +127,10 @@ a printer object.

    The basic set of RPC's used to implement change notification are -

    • RemoteFindFirstPrinterChangeNotifyEx ( RFFPCN )

    • RemoteFindNextPrinterChangeNotifyEx ( RFNPCN )

    • FindClosePrinterChangeNotify( FCPCN )

    • ReplyOpenPrinter

    • ReplyClosePrinter

    • RouteRefreshPrinterChangeNotify ( RRPCN )

    +

    • RemoteFindFirstPrinterChangeNotifyEx ( RFFPCN )

    • RemoteFindNextPrinterChangeNotifyEx ( RFNPCN )

    • FindClosePrinterChangeNotify( FCPCN )

    • ReplyOpenPrinter

    • ReplyClosePrinter

    • RouteRefreshPrinterChangeNotify ( RRPCN )

    One additional RPC is available to a server, but is never used by the Windows spooler service: -

    • RouteReplyPrinter()

    +

    • RouteReplyPrinter()

    The opnum for all of these RPC's are defined in include/rpc_spoolss.h

    Windows NT print servers use a bizarre method of sending print @@ -172,7 +172,7 @@

    The current list of notification events supported by Samba can be found by examining the internal tables in srv_spoolss_nt.c -

    • printer_notify_table[]

    • job_notify_table[]

    +

    • printer_notify_table[]

    • job_notify_table[]

    When an event occurs that could be monitored, smbd sends a message to itself about the change. The list of events to be transmitted are queued by the smbd process sending the message to prevent an @@ -192,24 +192,24 @@

    The actual change notification is performed using the RRPCN request RPC. This packet contains -

    • the printer handle registered with the -client's spooler on which the change occurred

    • The change_low value which was sent as part -of the last RFNPCN request from the client

    • The SPOOL_NOTIFY_INFO container with the event +

      • the printer handle registered with the +client's spooler on which the change occurred

      • The change_low value which was sent as part +of the last RFNPCN request from the client

      • The SPOOL_NOTIFY_INFO container with the event information

      A SPOOL_NOTIFY_INFO contains: -

      • the version and flags field are predefined -and should not be changed

      • The count field is the number of entries +

        • the version and flags field are predefined +and should not be changed

        • The count field is the number of entries in the SPOOL_NOTIFY_INFO_DATA array

        The SPOOL_NOTIFY_INFO_DATA entries contain: -

        • The type defines whether or not this event -is for a printer or a print job

        • The field is the flag identifying the event

        • the notify_data union contains the new valuie of the -attribute

        • The enc_type defines the size of the structure for marshalling -and unmarshalling

        • (a) the id must be 0 for a printer event on a printer handle. +

          • The type defines whether or not this event +is for a printer or a print job

          • The field is the flag identifying the event

          • the notify_data union contains the new valuie of the +attribute

          • The enc_type defines the size of the structure for marshalling +and unmarshalling

          • (a) the id must be 0 for a printer event on a printer handle. (b) the id must be the job id for an event on a printer job (c) the id must be the matching number of the printer index used in the response packet to the RFNPCN when using a print server 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, +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.