From ff78c3bf5c3a73cf90f6517d9b2d6b8c12d22d68 Mon Sep 17 00:00:00 2001 From: Jelmer Vernooij Date: Tue, 18 Feb 2003 22:14:04 +0000 Subject: Regenerate (This used to be commit 1ab5a3b17feb677425bb1071357c3dbabcc46c7e) --- docs/htmldocs/Samba-Developers-Guide.html | 145 +- docs/htmldocs/Samba-HOWTO-Collection.html | 8652 +++++++++++++++-------------- docs/htmldocs/ads.html | 86 +- docs/htmldocs/appendixes.html | 177 +- docs/htmldocs/browsing-quick.html | 70 +- docs/htmldocs/bugreport.html | 31 +- docs/htmldocs/cvs-access.html | 35 +- docs/htmldocs/diagnosis.html | 67 +- docs/htmldocs/domain-security.html | 227 +- docs/htmldocs/findsmb.1.html | 195 +- docs/htmldocs/groupmapping.html | 11 +- docs/htmldocs/groupprofiles.html | 565 ++ docs/htmldocs/improved-browsing.html | 81 +- docs/htmldocs/install.html | 89 +- docs/htmldocs/integrate-ms-networks.html | 105 +- docs/htmldocs/introduction.html | 213 +- docs/htmldocs/lmhosts.5.html | 94 +- docs/htmldocs/msdfs.html | 15 +- docs/htmldocs/net.8.html | 45 +- docs/htmldocs/nmbd.8.html | 370 +- docs/htmldocs/nmblookup.1.html | 95 +- docs/htmldocs/optional.html | 608 +- docs/htmldocs/other-clients.html | 59 +- docs/htmldocs/pam.html | 19 +- docs/htmldocs/passdb.html | 1646 ++++++ docs/htmldocs/pdb-mysql.html | 67 +- docs/htmldocs/pdb-xml.html | 15 +- docs/htmldocs/pdbedit.8.html | 215 +- docs/htmldocs/portability.html | 23 +- docs/htmldocs/printing.html | 107 +- docs/htmldocs/pwencrypt.html | 39 +- docs/htmldocs/rpcclient.1.html | 100 +- docs/htmldocs/samba-bdc.html | 62 +- docs/htmldocs/samba-howto-collection.html | 673 ++- docs/htmldocs/samba-ldap-howto.html | 55 +- docs/htmldocs/samba-pdc.html | 121 +- docs/htmldocs/samba.7.html | 160 +- docs/htmldocs/securitylevels.html | 11 +- docs/htmldocs/smb.conf.5.html | 3246 ++++++----- docs/htmldocs/smbcacls.1.html | 77 +- docs/htmldocs/smbclient.1.html | 177 +- docs/htmldocs/smbcontrol.1.html | 96 +- docs/htmldocs/smbd.8.html | 345 +- docs/htmldocs/smbgroupedit.8.html | 156 +- docs/htmldocs/smbmnt.8.html | 25 +- docs/htmldocs/smbmount.8.html | 84 +- docs/htmldocs/smbpasswd.5.html | 67 +- docs/htmldocs/smbpasswd.8.html | 216 +- docs/htmldocs/smbsh.1.html | 179 +- docs/htmldocs/smbspool.8.html | 61 +- docs/htmldocs/smbstatus.1.html | 79 +- docs/htmldocs/smbtar.1.html | 120 +- docs/htmldocs/smbumount.8.html | 23 +- docs/htmldocs/speed.html | 57 +- docs/htmldocs/swat.8.html | 115 +- docs/htmldocs/testparm.1.html | 136 +- docs/htmldocs/testprns.1.html | 87 +- docs/htmldocs/type.html | 182 +- docs/htmldocs/unix-permissions.html | 63 +- docs/htmldocs/vfs.html | 59 +- docs/htmldocs/vfstest.1.html | 51 +- docs/htmldocs/wbinfo.1.html | 189 +- docs/htmldocs/winbind.html | 169 +- docs/htmldocs/winbindd.8.html | 230 +- 64 files changed, 12765 insertions(+), 8872 deletions(-) create mode 100644 docs/htmldocs/groupprofiles.html create mode 100644 docs/htmldocs/passdb.html (limited to 'docs/htmldocs') diff --git a/docs/htmldocs/Samba-Developers-Guide.html b/docs/htmldocs/Samba-Developers-Guide.html index b90d99bf66..5d9702e49e 100644 --- a/docs/htmldocs/Samba-Developers-Guide.html +++ b/docs/htmldocs/Samba-Developers-Guide.html @@ -5,7 +5,7 @@ >SAMBA Developers Guide
10.4. ChangeID & Client Caching of Printer InformationChangeID and Client Caching of Printer Information
10.5. The smbpasswd file>The smbpasswd file
14. RPC Pluggable Modules
14.1. About
14.2. General Overview

This is a short document that describes some of the issues that confront a SMB implementation on unix, and how Samba copes with -them. They may help people who are looking at unix<->PC +them. They may help people who are looking at unix<->PC interoperability.

It was written to help out a person who was writing a paper on unix to @@ -2881,14 +2900,14 @@ example, if I'm using a csh style shell:

strace -f -p 3872 >& strace.outstrace -f -p 3872 >& strace.out

or with a sh style shell:

strace -f -p 3872 > strace.out 2>&1strace -f -p 3872 > strace.out 2>&1

Note the "-f" option. This is only available on some systems, and @@ -6985,7 +7004,7 @@ CLASS="emphasis" >Note: mailslots will contain a response mailslot, to which the response - should be sent. the target NetBIOS name is REQUEST_NAME<20>, where + should be sent. the target NetBIOS name is REQUEST_NAME<20>, where REQUEST_NAME is the name of the machine that sent the request.

9.7.2. Protocol

C->S ReqChal,Cc S->C Cs

C->S ReqChal,Cc S->C Cs

C & S compute session key Ks = E(PW[9..15],E(PW[0..6],Add(Cc,Cs)))

C & S compute session key Ks = E(PW[9..15],E(PW[0..6],Add(Cc,Cs)))

C: Rc = Cred(Ks,Cc) C->S Authenticate,Rc S: Rs = Cred(Ks,Cs), -assert(Rc == Cred(Ks,Cc)) S->C Rs C: assert(Rs == Cred(Ks,Cs))

On joining the domain the client will optionally attempt to change its password and the domain controller may refuse to update it depending on registry settings. This will also occur weekly afterwards.

C: Tc = Time(), Rc' = Cred(Ks,Rc+Tc) C->S ServerPasswordSet,Rc',Tc, +>C: Tc = Time(), Rc' = Cred(Ks,Rc+Tc) C->S ServerPasswordSet,Rc',Tc, arc4(Ks[0..7,16],lmowf(randompassword()) C: Rc = Cred(Ks,Rc+Tc+1) S: assert(Rc' == Cred(Ks,Rc+Tc)), Ts = Time() S: Rs' = Cred(Ks,Rs+Tc+1) S->C Rs',Ts C: assert(Rs' == Cred(Ks,Rs+Tc+1)) S: Rs = Rs'

User: U with password P wishes to login to the domain (incidental data such as workstation and domain omitted)

C: Tc = Time(), Rc' = Cred(Ks,Rc+Tc) C->S NetLogonSamLogon,Rc',Tc,U, +>C: Tc = Time(), Rc' = Cred(Ks,Rc+Tc) C->S NetLogonSamLogon,Rc',Tc,U, arc4(Ks[0..7,16],16,ntowf(P),16), arc4(Ks[0..7,16],16,lmowf(P),16) S: assert(Rc' == Cred(Ks,Rc+Tc)) assert(passwords match those in SAM) S: Ts = Time()

10.4. ChangeID & Client Caching of Printer Information10.4. ChangeID and Client Caching of Printer Information

[To be filled in later]

For example, when you call 

<
-NTSTATUS sam_get_account_by_name(const SAM_CONTEXT *context, const
+>NTSTATUS sam_get_account_by_name(const SAM_CONTEXT *context, const
 NT_USER_TOKEN *access_token, uint32 access_desired, const char *domain,
 const char *name, SAM_ACCOUNT_HANDLE **account)

13.3. The smbpasswd file>The smbpasswd file

In order for Samba to participate in the above protocol it must be able to look up the 16 byte hashed values given a user name. @@ -9131,7 +9149,7 @@ CLASS="FILENAME" CLASS="FILENAME" >/etc/passwd file use the following command :

file use the following command:

file.

Chapter 14. RPC Pluggable Modules

14.1. About

This document describes how to make use the new RPC Pluggable Modules features +of Samba 3.0. This architecture was added to increase the maintainability of +Samba allowing RPC Pipes to be worked on separately from the main CVS branch. +The RPM architecture will also allow third-party vendors to add functionality +to Samba through plug-ins.

14.2. General Overview

When an RPC call is sent to smbd, smbd tries to load a shared library by the +name librpc_<pipename>.so to handle the call if +it doesn't know how to handle the call internally. For instance, LSA calls +are handled by librpc_lsass.so.. +These shared libraries should be located in the <sambaroot>/lib/rpc. smbd then attempts to call the rpc_pipe_init function within +the shared library.

In the rpc_pipe_init function, the library should call +rpc_pipe_register_commands(). This function takes the following arguments:

int rpc_pipe_register_commands(const char *clnt, const char *srv,
+                               const struct api_struct *cmds, int size);

clnt

the Client name of the named pipe

srv

the Server name of the named pipe

cmds

a list of api_structs that map RPC ordinal numbers to function calls

size

the number of api_structs contained in cmds

See rpc_server/srv_reg.c and rpc_server/srv_reg_nt.c for a small example of +how to use this library.

SAMBA Project DocumentationLast Update : Thu Aug 15 12:48:45 CDT 2002

: Wed Jan 15

This book is a collection of HOWTOs added to Samba documentation over the years. I try to ensure that all are current, but sometimes the is a larger job @@ -59,6 +59,11 @@ on the "Documentation" page. Please send updates to jerry@samba.org or +jelmer@samba.org.

This documentation is distributed under the GNU General Public License (GPL) @@ -79,7 +84,7 @@ CLASS="TOC" >

I. General installation
1.1. Read the man pages
1.2. Building the Binaries
1.3. The all important step
1.4. Create the smb configuration file.
1.5. Test your config file with
1.6. Starting the smbd and nmbd
1.7. Try listing the shares available on your server
1.8. Try connecting with the unix client
1.9. Try connecting from a DOS, WfWg, Win9x, WinNT, Win2k, OS/2, etc... client
1.10. What If Things Don't Work?
2. Improved browsing in sambaQuick Cross Subnet Browsing / Cross Workgroup Browsing guide
2.1. Overview of browsingDiscussion
2.2. Browsing support in sambaUse of the "Remote Announce" parameter
2.3. Problem resolutionUse of the "Remote Browse Sync" parameter
2.4. Browsing across subnetsUse of WINS
2.5. Setting up a WINS serverDo NOT use more than one (1) protocol on MS Windows machines
2.6. Setting up Browsing in a WORKGROUP
2.7. Setting up Browsing in a DOMAIN
2.8. Forcing samba to be the master
2.9. Making samba the domain master
2.10. Note about broadcast addresses
2.11. Multiple interfacesName Resolution Order
3. OplocksUser information database
3.1. What are oplocks?
4. Quick Cross Subnet Browsing / Cross Workgroup Browsing guide
4.1. Discussion
4.2. Use of the "Remote Announce" parameter
4.3. Use of the "Remote Browse Sync" parameterIntroduction
4.4. Use of WINS3.2. Important Notes About Security
4.5. Do NOT use more than one (1) protocol on MS Windows machines3.3. The smbpasswd Command
4.6. Name Resolution Order3.4. Plain text
5. LanMan and NT Password Encryption in Samba3.5. TDB
5.1. Introduction3.6. LDAP
5.2. Important Notes About Security3.7. MySQL
5.3. The smbpasswd Command3.8. Passdb XML plugin
II. Type of installation
6. 4. User and Share security level (for servers not in a domain)
5. How to Configure Samba as a NT4 Primary Domain ControllerSamba as a NT4 or Win2k Primary Domain Controller
6.1. 5.1. Prerequisite Reading
6.2. 5.2. Background
6.3. 5.3. Configuring the Samba Domain Controller
6.4. 5.4. Creating Machine Trust Accounts and Joining Clients to the Domain
6.5. 5.5. Common Problems and Errors
6.6. 5.6. System Policies and Profiles
6.7. 5.7. What other help can I get?
6.8. 5.8. Domain Control for Windows 9x/ME
6.9. DOMAIN_CONTROL.txt : Windows NT Domain Control & Samba5.9. DOMAIN_CONTROL.txt : Windows NT Domain Control & Samba
7. 6. How to Act as a Backup Domain Controller in a Purely Samba Controlled Domain
7.1. 6.1. Prerequisite Reading
7.2. 6.2. Background
7.3. 6.3. What qualifies a Domain Controller on the network?
7.4. Can Samba be a Backup Domain Controller?6.4. Can Samba be a Backup Domain Controller to an NT PDC?
7.5. 6.5. How do I set up a Samba BDC?
8. 7. Samba as a ADS domain member
8.1. 7.1. Installing the required packages for Debian
8.2. 7.2. Installing the required packages for RedHat
8.3. 7.3. Compile Samba
8.4. 7.4. Setup your /etc/krb5.conf
8.5. 7.5. Create the computer account
8.6. 7.6. Test your server setup
8.7. 7.7. Testing with smbclient
8.8. 7.8. Notes
9. 8. Samba as a NT4 domain memberSamba as a NT4 or Win2k domain member
9.1. Joining an NT Domain with Samba 2.28.1. Joining an NT Domain with Samba 3.0
9.2. 8.2. Samba and Windows 2000 Domains
9.3. 8.3. Why is this better than security = server?
III. Optional configuration
10. 9. Integrating MS Windows networks with Samba
10.1. 9.1. Agenda
10.2. 9.2. Name Resolution in a pure Unix/Linux world
10.3. 9.3. Name resolution as used within MS Windows networking
10.4. 9.4. How browsing functions and how to deploy stable and dependable browsing using Samba
10.5. 9.5. MS Windows security options and how to configure Samba for seemless integration
10.6. 9.6. Conclusions
11. 10. UNIX Permission Bits and Windows NT Access Control Lists
11.1. 10.1. Viewing and changing UNIX permissions using the NT security dialogs
11.2. 10.2. How to view file security on a Samba share
11.3. 10.3. Viewing file ownership
11.4. 10.4. Viewing file or directory permissions
11.5. 10.5. Modifying file or directory permissions
11.6. 10.6. Interaction with the standard Samba create mask parameters
11.7. 10.7. Interaction with the standard Samba file attribute mapping
12. 11. Configuring PAM for distributed but centrally managed authentication
12.1. 11.1. Samba and PAM
12.2. 11.2. Distributed Authentication
12.3. 11.3. PAM Configuration in smb.conf
13. 12. Hosting a Microsoft Distributed File System tree on Samba
13.1. 12.1. Instructions
14. 13. Printing Support
14.1. 13.1. Introduction
14.2. 13.2. Configuration
14.3. 13.3. The Imprints Toolset
14.4. 13.4. Diagnosis
15. Security levels
15.1. Introduction
15.2. More complete description of security levels
16. 14. Unified Logons between Windows NT and UNIX using Winbind
16.1. 14.1. Abstract
16.2. 14.2. Introduction
16.3. 14.3. What Winbind Provides
16.4. 14.4. How Winbind Works
16.5. 14.5. Installation and Configuration
16.6. 14.6. Limitations
16.7. 14.7. Conclusion
17. Passdb MySQL plugin15. Improved browsing in samba
17.1. Building
17.2. Configuring
17.3. Using plaintext passwords or encrypted password
17.4. Getting non-column data from the table15.1. Overview of browsing
18. Passdb XML plugin15.2. Browsing support in samba
18.1. Building15.3. Problem resolution
18.2. Usage15.4. Browsing across subnets
19. Storing Samba's User/Machine Account information in an LDAP Directory15.5. Setting up a WINS server
19.1. Purpose15.6. Setting up Browsing in a WORKGROUP
19.2. Introduction15.7. Setting up Browsing in a DOMAIN
19.3. Supported LDAP Servers15.8. Forcing samba to be the master
19.4. Schema and Relationship to the RFC 2307 posixAccount15.9. Making samba the domain master
19.5. Configuring Samba with LDAP15.10. Note about broadcast addresses
19.6. Accounts and Groups management15.11. Multiple interfaces
19.7. Security and sambaAccount16. Stackable VFS modules
19.8. LDAP specials attributes for sambaAccounts16.1. Introduction and configuration
19.9. Example LDIF Entries for a sambaAccount16.2. Included modules
19.10. Comments16.3. VFS modules available elsewhere
20. 17. HOWTO Access Samba source code via CVSAccess Samba source code via CVS
20.1. 17.1. Introduction
20.2. 17.2. CVS Access to samba.org
21. 18. Group mapping HOWTO
22. 19. Samba performance issues
22.1. 19.1. Comparisons
22.2. Oplocks
22.3. 19.2. Socket options
22.4. 19.3. Read size
22.5. 19.4. Max xmit
22.6. Locking
22.7. Share modes
22.8. 19.5. Log level
22.9. Wide lines
22.10. 19.6. Read raw
22.11. 19.7. Write raw
22.12. Read prediction19.8. Slow Clients
22.13. Memory mapping19.9. Slow Logins
22.14. Slow Clients19.10. Client tuning
22.15. Slow Logins20. Creating Group Profiles
22.16. Client tuning20.1. Windows '9x
20.2. Windows NT 4
22.17. My Results20.3. Windows 2000/XP
IV. Appendixes
23. 21. Portability
23.1. 21.1. HPUX
23.2. 21.2. SCO Unix
23.3. 21.3. DNIX
23.4. 21.4. RedHat Linux Rembrandt-II
24. 22. Samba and other CIFS clients
24.1. 22.1. Macintosh clients?
24.2. 22.2. OS2 Client
24.3. 22.3. Windows for Workgroups
24.4. 22.4. Windows '95/'98
24.5. 22.5. Windows 2000 Service Pack 2
25. 23. Reporting Bugs
25.1. 23.1. Introduction
25.2. 23.2. General info
25.3. 23.3. Debug levels
25.4. 23.4. Internal errors
25.5. 23.5. Attaching to a running process
25.6. 23.6. Patches
26. 24. Diagnosing your samba server
26.1. 24.1. Introduction
26.2. 24.2. Assumptions
26.3. 24.3. Tests
26.4. 24.4. Still having troubles?

Introduction

1.1. Read the man pages
1.2. Building the Binaries
1.3. The all important step
1.4. Create the smb configuration file.
1.5. Test your config file with
1.6. Starting the smbd and nmbd
1.6.1. Starting from inetd.conf
1.6.2. Alternative: starting it as a daemon
1.7. Try listing the shares available on your server
1.8. Try connecting with the unix client
1.9. Try connecting from a DOS, WfWg, Win9x, WinNT, Win2k, OS/2, etc... client
1.10. What If Things Don't Work?
1.10.1. Diagnosing Problems
1.10.2. Scope IDs
1.10.3. Choosing the Protocol Level
1.10.4. Printing from UNIX to a Client PC
1.10.5. Locking
1.10.6. Mapping Usernames
2. Improved browsing in sambaQuick Cross Subnet Browsing / Cross Workgroup Browsing guide
2.1. Overview of browsingDiscussion
2.2. Browsing support in sambaUse of the "Remote Announce" parameter
2.3. Problem resolutionUse of the "Remote Browse Sync" parameter
2.4. Browsing across subnets
2.4.1. How does cross subnet browsing work ?Use of WINS
2.5. Setting up a WINS serverDo NOT use more than one (1) protocol on MS Windows machines
2.6. Setting up Browsing in a WORKGROUPName Resolution Order
2.7. Setting up Browsing in a DOMAIN3. User information database
2.8. Forcing samba to be the master3.1. Introduction
2.9. Making samba the domain master3.2. Important Notes About Security
2.10. Note about broadcast addresses3.2.1. Advantages of SMB Encryption
2.11. Multiple interfaces3.2.2. Advantages of non-encrypted passwords
3. Oplocks3.3. The smbpasswd Command
3.1. What are oplocks?3.4. Plain text
4. Quick Cross Subnet Browsing / Cross Workgroup Browsing guide3.5. TDB
3.6. LDAP
4.1. Discussion3.6.1. Introduction
4.2. Use of the "Remote Announce" parameter3.6.2. Introduction
4.3. Use of the "Remote Browse Sync" parameter3.6.3. Supported LDAP Servers
4.4. Use of WINS3.6.4. Schema and Relationship to the RFC 2307 posixAccount
4.5. Do NOT use more than one (1) protocol on MS Windows machines3.6.5. Configuring Samba with LDAP
4.6. Name Resolution Order3.6.6. Accounts and Groups management
3.6.7. Security and sambaAccount
3.6.8. LDAP specials attributes for sambaAccounts
3.6.9. Example LDIF Entries for a sambaAccount
5. LanMan and NT Password Encryption in Samba3.7. MySQL
5.1. Introduction3.7.1. Building
5.2. Important Notes About Security3.7.2. Creating the database
5.2.1. Advantages of SMB Encryption3.7.3. Configuring
5.2.2. Advantages of non-encrypted passwords3.7.4. Using plaintext passwords or encrypted password
3.7.5. Getting non-column data from the table
5.3. The smbpasswd Command3.8. Passdb XML plugin
3.8.1. Building
3.8.2. Usage

1.1. Read the man pages

1.2. Building the Binaries

1.3. The all important step

1.4. Create the smb configuration file.

1.5. Test your config file with

1.6. Starting the smbd and nmbd

1.6.1. Starting from inetd.conf

1.6.2. Alternative: starting it as a daemon

1.7. Try listing the shares available on your server

1.8. Try connecting with the unix client

1.9. Try connecting from a DOS, WfWg, Win9x, WinNT, Win2k, OS/2, etc... client

1.10. What If Things Don't Work?

1.10.1. Diagnosing Problems

1.10.2. Scope IDs

1.10.3. Choosing the Protocol Level

1.10.4. Printing from UNIX to a Client PC

1.10.5. Locking

1.10.6. Mapping Usernames

Chapter 2. Improved browsing in samba

Chapter 2. Quick Cross Subnet Browsing / Cross Workgroup Browsing guide

This document should be read in conjunction with Browsing and may +be taken as the fast track guide to implementing browsing across subnets +and / or across workgroups (or domains). WINS is the best tool for resolution +of NetBIOS names to IP addesses. WINS is NOT involved in browse list handling +except by way of name to address mapping.

2.1. Overview of browsing

2.1. Discussion

SMB networking provides a mechanism by which clients can access a list -of machines in a network, a so-called "browse list". This list -contains machines that are ready to offer file and/or print services -to other machines within the network. Thus it does not include -machines which aren't currently able to do server tasks. The browse -list is heavily used by all SMB clients. Configuration of SMB -browsing has been problematic for some Samba users, hence this -document.

Firstly, all MS Windows networking is based on SMB (Server Message +Block) based messaging. SMB messaging is implemented using NetBIOS. Samba +implements NetBIOS by encapsulating it over TCP/IP. MS Windows products can +do likewise. NetBIOS based networking uses broadcast messaging to affect +browse list management. When running NetBIOS over TCP/IP this uses UDP +based messaging. UDP messages can be broadcast or unicast.

Browsing will NOT work if name resolution from NetBIOS names to IP -addresses does not function correctly. Use of a WINS server is highly -recommended to aid the resolution of NetBIOS (SMB) names to IP addresses. -WINS allows remote segment clients to obtain NetBIOS name_type information -that can NOT be provided by any other means of name resolution.

Normally, only unicast UDP messaging can be forwarded by routers. The +"remote announce" parameter to smb.conf helps to project browse announcements +to remote network segments via unicast UDP. Similarly, the "remote browse sync" +parameter of smb.conf implements browse list collation using unicast UDP.

Secondly, in those networks where Samba is the only SMB server technology +wherever possible nmbd should be configured on one (1) machine as the WINS +server. This makes it easy to manage the browsing environment. If each network +segment is configured with it's own Samba WINS server, then the only way to +get cross segment browsing to work is by using the "remote announce" and +the "remote browse sync" parameters to your smb.conf file.

If only one WINS server is used then the use of the "remote announce" and the +"remote browse sync" parameters should NOT be necessary.

Samba WINS does not support MS-WINS replication. This means that when setting up +Samba as a WINS server there must only be one nmbd configured as a WINS server +on the network. Some sites have used multiple Samba WINS servers for redundancy +(one server per subnet) and then used "remote browse sync" and "remote announce" +to affect browse list collation across all segments. Note that this means +clients will only resolve local names, and must be configured to use DNS to +resolve names on other subnets in order to resolve the IP addresses of the +servers they can see on other subnets. This setup is not recommended, but is +mentioned as a practical consideration (ie: an 'if all else fails' scenario).

Lastly, take note that browse lists are a collection of unreliable broadcast +messages that are repeated at intervals of not more than 15 minutes. This means +that it will take time to establish a browse list and it can take up to 45 +minutes to stabilise, particularly across network segments.

2.2. Browsing support in samba

Samba now fully supports browsing. The browsing is supported by nmbd -and is also controlled by options in the smb.conf file (see smb.conf(5)).

Samba can act as a local browse master for a workgroup and the ability -for samba to support domain logons and scripts is now available. See -DOMAIN.txt for more information on domain logons.

Samba can also act as a domain master browser for a workgroup. This -means that it will collate lists from local browse masters into a -wide area network server list. In order for browse clients to -resolve the names they may find in this list, it is recommended that -both samba and your clients use a WINS server.

Note that you should NOT set Samba to be the domain master for a -workgroup that has the same name as an NT Domain: on each wide area -network, you must only ever have one domain master browser per workgroup, -regardless of whether it is NT, Samba or any other type of domain master -that is providing this service.

2.2. Use of the "Remote Announce" parameter

[Note that nmbd can be configured as a WINS server, but it is not -necessary to specifically use samba as your WINS server. NTAS can -be configured as your WINS server. In a mixed NT server and -samba environment on a Wide Area Network, it is recommended that -you use the NT server's WINS server capabilities. In a samba-only -environment, it is recommended that you use one and only one nmbd -as your WINS server].

The "remote announce" parameter of smb.conf can be used to forcibly ensure +that all the NetBIOS names on a network get announced to a remote network. +The syntax of the "remote announce" parameter is: +
	remote announce = a.b.c.d [e.f.g.h] ...
+_or_ +
	remote announce = a.b.c.d/WORKGROUP [e.f.g.h/WORKGROUP] ...
+ +where: +

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

To get browsing to work you need to run nmbd as usual, but will need -to use the "workgroup" option in smb.conf to control what workgroup -Samba becomes a part of.

is either the LMB (Local Master Browser) IP address +or the broadcst address of the remote network. +ie: the LMB is at 192.168.1.10, or the address +could be given as 192.168.1.255 where the netmask +is assumed to be 24 bits (255.255.255.0). +When the remote announcement is made to the broadcast +address of the remote network every host will receive +our announcements. This is noisy and therefore +undesirable but may be necessary if we do NOT know +the IP address of the remote LMB.

WORKGROUP

Samba also has a useful option for a Samba server to offer itself for -browsing on another subnet. It is recommended that this option is only -used for 'unusual' purposes: announcements over the internet, for -example. See "remote announce" in the smb.conf man page.

is optional and can be either our own workgroup +or that of the remote network. If you use the +workgroup name of the remote network then our +NetBIOS machine names will end up looking like +they belong to that workgroup, this may cause +name resolution problems and should be avoided.

2.3. Problem resolution

2.3. Use of the "Remote Browse Sync" parameter

If something doesn't work then hopefully the log.nmb file will help -you track down the problem. Try a debug level of 2 or 3 for finding -problems. Also note that the current browse list usually gets stored -in text form in a file called browse.dat.

The "remote browse sync" parameter of smb.conf is used to announce to +another LMB that it must synchronise it's NetBIOS name list with our +Samba LMB. It works ONLY if the Samba server that has this option is +simultaneously the LMB on it's network segment.

Note that if it doesn't work for you, then you should still be able to -type the server name as \\SERVER in filemanager then hit enter and -filemanager should display the list of available shares.

The syntax of the "remote browse sync" parameter is: + +
remote browse sync = a.b.c.d
+ +where a.b.c.d is either the IP address of the remote LMB or else is the network broadcast address of the remote segment.

2.4. Use of WINS

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

Use of WINS (either Samba WINS _or_ MS Windows NT Server WINS) is highly +recommended. Every NetBIOS machine registers it's name together with a +name_type value for each of of several types of service it has available. +eg: It registers it's name directly as a unique (the type 0x03) name. +It also registers it's name if it is running the lanmanager compatible +server service (used to make shares and printers available to other users) +by registering the server (the type 0x20) name.

Also, a lot of people are getting bitten by the problem of too many -parameters on the command line of nmbd in inetd.conf. This trick is to -not use spaces between the option and the parameter (eg: -d2 instead -of -d 2), and to not use the -B and -N options. New versions of nmbd -are now far more likely to correctly find your broadcast and network -address, so in most cases these aren't needed.

All NetBIOS names are up to 15 characters in length. The name_type variable +is added to the end of the name - thus creating a 16 character name. Any +name that is shorter than 15 characters is padded with spaces to the 15th +character. ie: All NetBIOS names are 16 characters long (including the +name_type information).

The other big problem people have is that their broadcast address, -netmask or IP address is wrong (specified with the "interfaces" option -in smb.conf)

WINS can store these 16 character names as they get registered. A client +that wants to log onto the network can ask the WINS server for a list +of all names that have registered the NetLogon service name_type. This saves +broadcast traffic and greatly expedites logon processing. Since broadcast +name resolution can not be used across network segments this type of +information can only be provided via WINS _or_ via statically configured +"lmhosts" files that must reside on all clients in the absence of WINS.

WINS also serves the purpose of forcing browse list synchronisation by all +LMB's. LMB's must synchronise their browse list with the DMB (domain master +browser) and WINS helps the LMB to identify it's DMB. By definition this +will work only within a single workgroup. Note that the domain master browser +has NOTHING to do with what is referred to as an MS Windows NT Domain. The +later is a reference to a security environment while the DMB refers to the +master controller for browse list information only.

Use of WINS will work correctly only if EVERY client TCP/IP protocol stack +has been configured to use the WINS server/s. Any client that has not been +configured to use the WINS server will continue to use only broadcast based +name registration so that WINS may NEVER get to know about it. In any case, +machines that have not registered with a WINS server will fail name to address +lookup attempts by other clients and will therefore cause workstation access +errors.

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

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

DO NOT EVER use both "wins support = yes" together with "wins server = a.b.c.d" +particularly not using it's own IP address.

2.4. Browsing across subnets

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

With the release of Samba 1.9.17(alpha1 and above) Samba has been -updated to enable it to support the replication of browse lists -across subnet boundaries. New code and options have been added to -achieve this. This section describes how to set this feature up -in different settings.

A very common cause of browsing problems results from installing more than +one protocol on an MS Windows machine.

To see browse lists that span TCP/IP subnets (ie. networks separated -by routers that don't pass broadcast traffic) you must set up at least -one WINS server. The WINS server acts as a DNS for NetBIOS names, allowing -NetBIOS name to IP address translation to be done by doing a direct -query of the WINS server. This is done via a directed UDP packet on -port 137 to the WINS server machine. The reason for a WINS server is -that by default, all NetBIOS name to IP address translation is done -by broadcasts from the querying machine. This means that machines -on one subnet will not be able to resolve the names of machines on -another subnet without using a WINS server.

Every NetBIOS machine take part in a process of electing the LMB (and DMB) +every 15 minutes. A set of election criteria is used to determine the order +of precidence for winning this election process. A machine running Samba or +Windows NT will be biased so that the most suitable machine will predictably +win and thus retain it's role.

Remember, for browsing across subnets to work correctly, all machines, -be they Windows 95, Windows NT, or Samba servers must have the IP address -of a WINS server given to them by a DHCP server, or by manual configuration -(for Win95 and WinNT, this is in the TCP/IP Properties, under Network -settings) for Samba this is in the smb.conf file.

The election process is "fought out" so to speak over every NetBIOS network +interface. In the case of a Windows 9x machine that has both TCP/IP and IPX +installed and has NetBIOS enabled over both protocols the election will be +decided over both protocols. As often happens, if the Windows 9x machine is +the only one with both protocols then the LMB may be won on the NetBIOS +interface over the IPX protocol. Samba will then lose the LMB role as Windows +9x will insist it knows who the LMB is. Samba will then cease to function +as an LMB and thus browse list operation on all TCP/IP only machines will +fail.

The safest rule of all to follow it this - USE ONLY ONE PROTOCOL!

2.4.1. How does cross subnet browsing work ?

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

2.6. Name Resolution Order

Consider a network set up as follows :

Resolution of NetBIOS names to IP addresses can take place using a number +of methods. The only ones that can provide NetBIOS name_type information +are:

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

WINS: the best tool!
LMHOSTS: is static and hard to maintain.
Broadcast: uses UDP and can not resolve names across remote segments.

Consisting of 3 subnets (1, 2, 3) connected by two routers -(R1, R2) - these do not pass broadcasts. Subnet 1 has 5 machines -on it, subnet 2 has 4 machines, subnet 3 has 4 machines. Assume -for the moment that all these machines are configured to be in the -same workgroup (for simplicities sake). Machine N1_C on subnet 1 -is configured as Domain Master Browser (ie. it will collate the -browse lists for the workgroup). Machine N2_D is configured as -WINS server and all the other machines are configured to register -their NetBIOS names with it.

As all these machines are booted up, elections for master browsers -will take place on each of the three subnets. Assume that machine -N1_C wins on subnet 1, N2_B wins on subnet 2, and N3_D wins on -subnet 3 - these machines are known as local master browsers for -their particular subnet. N1_C has an advantage in winning as the -local master browser on subnet 1 as it is set up as Domain Master -Browser.

Alternative means of name resolution includes:

On each of the three networks, machines that are configured to -offer sharing services will broadcast that they are offering -these services. The local master browser on each subnet will -receive these broadcasts and keep a record of the fact that -the machine is offering a service. This list of records is -the basis of the browse list. For this case, assume that -all the machines are configured to offer services so all machines -will be on the browse list.

For each network, the local master browser on that network is -considered 'authoritative' for all the names it receives via -local broadcast. This is because a machine seen by the local -master browser via a local broadcast must be on the same -network as the local master browser and thus is a 'trusted' -and 'verifiable' resource. Machines on other networks that -the local master browsers learn about when collating their -browse lists have not been directly seen - these records are -called 'non-authoritative'.

At this point the browse lists look as follows (these are -the machines you would see in your network neighborhood if -you looked in it on a particular network right now).

Subnet           Browse Master   List
-------           -------------   ----
-Subnet1          N1_C            N1_A, N1_B, N1_C, N1_D, N1_E
-
-Subnet2          N2_B            N2_A, N2_B, N2_C, N2_D
-
-Subnet3          N3_D            N3_A, N3_B, N3_C, N3_D

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

Note that at this point all the subnets are separate, no -machine is seen across any of the subnets.

Now examine subnet 2. As soon as N2_B has become the local -master browser it looks for a Domain master browser to synchronize -its browse list with. It does this by querying the WINS server -(N2_D) for the IP address associated with the NetBIOS name -WORKGROUP>1B<. This name was registerd by the Domain master -browser (N1_C) with the WINS server as soon as it was booted.

Once N2_B knows the address of the Domain master browser it -tells it that is the local master browser for subnet 2 by -sending a MasterAnnouncement packet as a UDP port 138 packet. -It then synchronizes with it by doing a NetServerEnum2 call. This -tells the Domain Master Browser to send it all the server -names it knows about. Once the domain master browser receives -the MasterAnnouncement packet it schedules a synchronization -request to the sender of that packet. After both synchronizations -are done the browse lists look like :

Subnet           Browse Master   List
-------           -------------   ----
-Subnet1          N1_C            N1_A, N1_B, N1_C, N1_D, N1_E, 
-                                 N2_A(*), N2_B(*), N2_C(*), N2_D(*)
-
-Subnet2          N2_B            N2_A, N2_B, N2_C, N2_D
-                                 N1_A(*), N1_B(*), N1_C(*), N1_D(*), N1_E(*)
-
-Subnet3          N3_D            N3_A, N3_B, N3_C, N3_D
-
-Servers with a (*) after them are non-authoritative names.

At this point users looking in their network neighborhood on -subnets 1 or 2 will see all the servers on both, users on -subnet 3 will still only see the servers on their own subnet.

The same sequence of events that occured for N2_B now occurs -for the local master browser on subnet 3 (N3_D). When it -synchronizes browse lists with the domain master browser (N1_A) -it gets both the server entries on subnet 1, and those on -subnet 2. After N3_D has synchronized with N1_C and vica-versa -the browse lists look like.

Many sites want to restrict DNS lookups and want to avoid broadcast name
+resolution traffic. The "name resolve order" parameter is of great help here.
+The syntax of the "name resolve order" parameter is:
+
Subnet           Browse Master   List
-------           -------------   ----
-Subnet1          N1_C            N1_A, N1_B, N1_C, N1_D, N1_E, 
-                                 N2_A(*), N2_B(*), N2_C(*), N2_D(*),
-                                 N3_A(*), N3_B(*), N3_C(*), N3_D(*)
-
-Subnet2          N2_B            N2_A, N2_B, N2_C, N2_D
-                                 N1_A(*), N1_B(*), N1_C(*), N1_D(*), N1_E(*)
-
-Subnet3          N3_D            N3_A, N3_B, N3_C, N3_D
-                                 N1_A(*), N1_B(*), N1_C(*), N1_D(*), N1_E(*),
-                                 N2_A(*), N2_B(*), N2_C(*), N2_D(*)
-
-Servers with a (*) after them are non-authoritative names.
At this point users looking in their network neighborhood on
-subnets 1 or 3 will see all the servers on all sunbets, users on
-subnet 2 will still only see the servers on subnets 1 and 2, but not 3.
Finally, the local master browser for subnet 2 (N2_B) will sync again
-with the domain master browser (N1_C) and will recieve the missing
-server entries.  Finally - and as a steady state (if no machines
-are removed or shut off) the browse lists will look like :
name resolve order = wins lmhosts bcast host

+_or_
+
Subnet           Browse Master   List
-------           -------------   ----
-Subnet1          N1_C            N1_A, N1_B, N1_C, N1_D, N1_E, 
-                                 N2_A(*), N2_B(*), N2_C(*), N2_D(*),
-                                 N3_A(*), N3_B(*), N3_C(*), N3_D(*)
-
-Subnet2          N2_B            N2_A, N2_B, N2_C, N2_D
-                                 N1_A(*), N1_B(*), N1_C(*), N1_D(*), N1_E(*)
-                                 N3_A(*), N3_B(*), N3_C(*), N3_D(*)
-
-Subnet3          N3_D            N3_A, N3_B, N3_C, N3_D
-                                 N1_A(*), N1_B(*), N1_C(*), N1_D(*), N1_E(*),
-                                 N2_A(*), N2_B(*), N2_C(*), N2_D(*)
-	
-Servers with a (*) after them are non-authoritative names.
Synchronizations between the domain master browser and local
-master browsers will continue to occur, but this should be a
-steady state situation.
If either router R1 or R2 fails the following will occur:
  1. name resolve order = wins lmhosts  	(eliminates bcast and host)
+The default is: +
name  resolve order = host lmhost wins bcast
. +where "host" refers the the native methods used by the Unix system +to implement the gethostbyname() function call. This is normally +controlled by /etc/host.conf, /etc/nsswitch.conf and /etc/resolv.conf.

Chapter 3. User information database

3.1. Introduction

Names of computers on each side of the inaccessible network fragments - will be maintained for as long as 36 minutes, in the network neighbourhood - lists. +>Old windows clients send plain text passwords over the wire. + Samba can check these passwords by crypting them and comparing them + to the hash stored in the unix user database.

  • Attempts to connect to these inaccessible computers will fail, but the - names will not be removed from the network neighbourhood lists. +> Newer windows clients send encrypted passwords (so-called + Lanman and NT hashes) over + the wire, instead of plain text passwords. The newest clients + will only send encrypted passwords and refuse to send plain text + passwords, unless their registry is tweaked.

  • If one of the fragments is cut off from the WINS server, it will only - be able to access servers on its local subnet, by using subnet-isolated - broadcast NetBIOS name resolution. The effects are similar to that of - losing access to a DNS server. +>These passwords can't be converted to unix style encrypted + passwords. Because of that you can't use the standard unix + user database, and you have to store the Lanman and NT hashes + somewhere else.

    Next to a differently encrypted passwords, + windows also stores certain data for each user + that is not stored in a unix user database, e.g. + workstations the user may logon from, the location where his/her + profile is stored, etc. + Samba retrieves and stores this information using a "passdb backend". + Commonly + available backends are LDAP, plain text file, MySQL and nisplus. + For more information, see the documentation about the + passdb backend = parameter.

    • 2.5. Setting up a WINS server

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

    3.2. Important Notes About Security

    wins support = yes

    The unix and SMB password encryption techniques seem similar + on the surface. This similarity is, however, only skin deep. The unix + scheme typically sends clear text passwords over the network when + logging in. This is bad. The SMB encryption scheme never sends the + cleartext password over the network but it does store the 16 byte + hashed values on disk. This is also bad. Why? Because the 16 byte hashed + values are a "password equivalent". You cannot derive the user's + password from them, but they could potentially be used in a modified + client to gain access to a server. This would require considerable + technical knowledge on behalf of the attacker but is perfectly possible. + You should thus treat the data stored in whatever + passdb backend you use (smbpasswd file, ldap, mysql) as though it contained the + cleartext passwords of all your users. Its contents must be kept + secret, and the file should be protected accordingly.

    Versions of Samba previous to 1.9.17 had this parameter default to -yes. If you have any older versions of Samba on your network it is -strongly suggested you upgrade to 1.9.17 or above, or at the very -least set the parameter to 'no' on all these machines.

    Ideally we would like a password scheme which neither requires + plain text passwords on the net or on disk. Unfortunately this + is not available as Samba is stuck with being compatible with + other SMB systems (WinNT, WfWg, Win95 etc).

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

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

    To set up a Windows NT Server as a WINS server you need to set up -the WINS service - see your NT documentation for details. Note that -Windows NT WINS Servers can replicate to each other, allowing more -than one to be set up in a complex subnet environment. As Microsoft -refuse to document these replication protocols Samba cannot currently -participate in these replications. It is possible in the future that -a Samba->Samba WINS replication protocol may be defined, in which -case more than one Samba machine could be set up as a WINS server -but currently only one Samba server should have the "wins support = yes" -parameter set.

    Note that Windows NT 4.0 Service pack 3 changed the + default for permissible authentication so that plaintext + passwords are never sent over the wire. + The solution to this is either to switch to encrypted passwords + with Samba or edit the Windows NT registry to re-enable plaintext + passwords. See the document WinNT.txt for details on how to do + this.

    After the WINS server has been configured you must ensure that all -machines participating on the network are configured with the address -of this WINS server. If your WINS server is a Samba machine, fill in -the Samba machine IP address in the "Primary WINS Server" field of -the "Control Panel->Network->Protocols->TCP->WINS Server" dialogs -in Windows 95 or Windows NT. To tell a Samba server the IP address -of the WINS server add the following line to the [global] section of -all smb.conf files :

    Other Microsoft operating systems which also exhibit + this behavior includes

    wins server = >name or IP address<

    MS DOS Network client 3.0 with + the basic network redirector installed
    Windows 95 with the network redirector + update installed
    Windows 98 [se]
    Windows 2000

    where >name or IP address< is either the DNS name of the WINS server -machine or its IP address.

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

    There are two possible scenarios for setting up cross subnet browsing. -The first details setting up cross subnet browsing on a network containing -Windows 95, Samba and Windows NT machines that are not configured as -part of a Windows NT Domain. The second details setting up cross subnet -browsing on networks that contain NT Domains.

    Note :All current release of + Microsoft SMB/CIFS clients support authentication via the + SMB Challenge/Response mechanism described here. Enabling + clear text authentication does not disable the ability + of the client to participate in encrypted authentication.

    2.6. Setting up Browsing in a WORKGROUP

    To set up cross subnet browsing on a network containing machines -in up to be in a WORKGROUP, not an NT Domain you need to set up one -Samba server to be the Domain Master Browser (note that this is *NOT* -the same as a Primary Domain Controller, although in an NT Domain the -same machine plays both roles). The role of a Domain master browser is -to collate the browse lists from local master browsers on all the -subnets that have a machine participating in the workgroup. Without -one machine configured as a domain master browser each subnet would -be an isolated workgroup, unable to see any machines on any other -subnet. It is the presense of a domain master browser that makes -cross subnet browsing possible for a workgroup.

    In an WORKGROUP environment the domain master browser must be a -Samba server, and there must only be one domain master browser per -workgroup name. To set up a Samba server as a domain master browser, -set the following option in the [global] section of the smb.conf file :

    domain master = yes

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

            domain master = yes
-        local master = yes
-        preferred master = yes
-        os level = 65

    The domain master browser may be the same machine as the WINS -server, if you require.

    Next, you should ensure that each of the subnets contains a -machine that can act as a local master browser for the -workgroup. Any NT machine should be able to do this, as will -Windows 95 machines (although these tend to get rebooted more -often, so it's not such a good idea to use these). To make a -Samba server a local master browser set the following -options in the [global] section of the smb.conf file :

    3.2.1. Advantages of SMB Encryption

            domain master = no
-        local master = yes
-        preferred master = yes
-        os level = 65

    plain text passwords are not passed across + the network. Someone using a network sniffer cannot just + record passwords going to the SMB server.
    WinNT doesn't like talking to a server + that isn't using SMB encrypted passwords. It will refuse + to browse the server if the server is also in user level + security mode. It will insist on prompting the user for the + password on each connection, which is very annoying. The + only things you can do to stop this is to use SMB encryption. +

    Do not do this for more than one Samba server on each subnet, -or they will war with each other over which is to be the local -master browser.

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

    If you have an NT machine on the subnet that you wish to -be the local master browser then you can disable Samba from -becoming a local master browser by setting the following -options in the [global] section of the smb.conf file :

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

    2.7. Setting up Browsing in a DOMAIN

    If you are adding Samba servers to a Windows NT Domain then -you must not set up a Samba server as a domain master browser. -By default, a Windows NT Primary Domain Controller for a Domain -name is also the Domain master browser for that name, and many -things will break if a Samba server registers the Domain master -browser NetBIOS name (DOMAIN>1B<) with WINS instead of the PDC.

    For subnets other than the one containing the Windows NT PDC -you may set up Samba servers as local master browsers as -described. To make a Samba server a local master browser set -the following options in the [global] section of the smb.conf -file :

    3.2.2. Advantages of non-encrypted passwords

            domain master = no
-        local master = yes
-        preferred master = yes
-        os level = 65

    plain text passwords are not kept + on disk.
    uses same password file as other unix + services such as login and ftp
    you are probably already using other + services (such as telnet and ftp) which send plain text + passwords over the net, so sending them for SMB isn't + such a big deal.

    If you wish to have a Samba server fight the election with machines -on the same subnet you may set the "os level" parameter to lower -levels. By doing this you can tune the order of machines that -will become local master browsers if they are running. For -more details on this see the section "FORCING SAMBA TO BE THE MASTER" -below.

    If you have Windows NT machines that are members of the domain -on all subnets, and you are sure they will always be running then -you can disable Samba from taking part in browser elections and -ever becoming a local master browser by setting following options -in the [global] section of the smb.conf file :

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

    2.8. Forcing samba to be the master

    3.3. The smbpasswd Command

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

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

    A "os level" of 2 would make it beat WfWg and Win95, but not NTAS. A -NTAS domain controller uses level 32.

    The maximum os level is 255

    If you want samba to force an election on startup, then set the -"preferred master" global option in smb.conf to "yes". Samba will -then have a slight advantage over other potential master browsers -that are not preferred master browsers. Use this parameter with -care, as if you have two hosts (whether they are windows 95 or NT or -samba) on the same local subnet both set with "preferred master" to -"yes", then periodically and continually they will force an election -in order to become the local master browser.

    If you want samba to be a "domain master browser", then it is -recommended that you also set "preferred master" to "yes", because -samba will not become a domain master browser for the whole of your -LAN or WAN if it is not also a local master browser on its own -broadcast isolated subnet.

    It is possible to configure two samba servers to attempt to become -the domain master browser for a domain. The first server that comes -up will be the domain master browser. All other samba servers will -attempt to become the domain master browser every 5 minutes. They -will find that another samba server is already the domain master -browser and will fail. This provides automatic redundancy, should -the current domain master browser fail.

    2.9. Making samba the domain master

    The smbpasswd utility is a utility similar to the + passwd or yppasswd programs. + It maintains the two 32 byte password fields + in the passdb backend.

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

    smbpasswd works in a client-server mode + where it contacts the local smbd to change the user's password on its + behalf. This has enormous benefits - as follows.

    Note that you should NOT set Samba to be the domain master for a -workgroup that has the same name as an NT Domain.

    smbpasswd has the capability + to change passwords on Windows NT servers (this only works when + the request is sent to the NT Primary Domain Controller if you + are changing an NT Domain user's password).

    When samba is the domain master and the master browser it will listen -for master announcements (made roughly every twelve minutes) from local -master browsers on other subnets and then contact them to synchronise -browse lists.

    To run smbpasswd as a normal user just type :

    If you want samba to be the domain master then I suggest you also set -the "os level" high enough to make sure it wins elections, and set -"preferred master" to "yes", to get samba to force an election on -startup.

    $ smbpasswd

    Note that all your servers (including samba) and clients should be -using a WINS server to resolve NetBIOS names. If your clients are only -using broadcasting to resolve NetBIOS names, then two things will occur:

    Old SMB password: <type old value here - + or hit return if there was no old password>

    New SMB Password: <type new value> +

    1. your local master browsers will be unable to find a domain master - browser, as it will only be looking on the local subnet. -

    2. Repeat New SMB Password: <re-type new value +

      if a client happens to get hold of a domain-wide browse list, and - a user attempts to access a host in that list, it will be unable to - resolve the NetBIOS name of that host. -

    If the old value does not match the current value stored for + that user, or the two new values do not match each other, then the + password will not be changed.

    If, however, both samba and your clients are using a WINS server, then:

    If invoked by an ordinary user it will only allow the user + to change his or her own Samba password.

    1. If run by the root user smbpasswd may take an optional + argument, specifying the user name whose SMB password you wish to + change. Note that when run as root smbpasswd does not prompt for + or check the old password value, thus allowing root to set passwords + for users who have forgotten their passwords.

      your local master browsers will contact the WINS server and, as long as - samba has registered that it is a domain master browser with the WINS - server, your local master browser will receive samba's ip address - as its domain master browser. -

    2. smbpasswd is designed to work in the same way + and be familiar to UNIX users who use the passwd or + yppasswd commands.

      when a client receives a domain-wide browse list, and a user attempts - to access a host in that list, it will contact the WINS server to - resolve the NetBIOS name of that host. as long as that host has - registered its NetBIOS name with the same WINS server, the user will - be able to see that host. -

    For more details on using smbpasswd refer + to the man page which will always be the definitive reference.

    2.10. Note about broadcast addresses

    3.4. Plain text

    If your network uses a "0" based broadcast address (for example if it -ends in a 0) then you will strike problems. Windows for Workgroups -does not seem to support a 0's broadcast and you will probably find -that browsing and name lookups won't work.

    Older versions of samba retrieved user information from the unix user database +and eventually some other fields from the file /etc/samba/smbpasswd +or /etc/smbpasswd. When password encryption is disabled, no +data is stored at all.

    2.11. Multiple interfaces

    3.5. TDB

    Samba now supports machines with multiple network interfaces. If you -have multiple interfaces then you will need to use the "interfaces" -option in smb.conf to configure them. See smb.conf(5) for details.

    Samba can also store the user data in a "TDB" (Trivial Database). Using this backend +doesn't require any additional configuration. This backend is recommended for new installations who +don't require LDAP.

    Chapter 3. Oplocks

    3.1. What are oplocks?

    When a client opens a file it can request an "oplock" or file -lease. This is (to simplify a bit) a guarentee that no one else -has the file open simultaneously. It allows the client to not -send any updates on the file to the server, thus reducing a -network file access to local access (once the file is in -client cache). An "oplock break" is when the server sends -a request to the client to flush all its changes back to -the server, so the file is in a consistent state for other -opens to succeed. If a client fails to respond to this -asynchronous request then the file can be corrupted. Hence -the "turn off oplocks" answer if people are having multi-user -file access problems.

    Unless the kernel is "oplock aware" (SGI IRIX and Linux are -the only two UNIXes that are at the moment) then if a local -UNIX process accesses the file simultaneously then Samba -has no way of telling this is occuring, so the guarentee -to the client is broken. This can corrupt the file. Short -answer - it you have UNIX clients accessing the same file -as smbd locally or via NFS and you're not running Linux or -IRIX then turn off oplocks for that file or share.

    "Share modes". These are modes of opening a file, that -guarentee an invarient - such as DENY_WRITE - which means -that if any other opens are requested with write access after -this current open has succeeded then they should be denied -with a "sharing violation" error message. Samba handles these -internally inside smbd. UNIX clients accessing the same file -ignore these invarients. Just proving that if you need simultaneous -file access from a Windows and UNIX client you *must* have an -application that is written to lock records correctly on both -sides. Few applications are written like this, and even fewer -are cross platform (UNIX and Windows) so in practice this isn't -much of a problem.

    "Locking". This really means "byte range locking" - such as -lock 10 bytes at file offset 24 for write access. This is the -area in which well written UNIX and Windows apps will cooperate. -Windows locks (at least from NT or above) are 64-bit unsigned -offsets. UNIX locks are either 31 bit or 63 bit and are signed -(the top bit is used for the sign). Samba handles these by -first ensuring that all the Windows locks don't conflict (ie. -if other Windows clients have competing locks then just reject -immediately) - this allows us to support 64-bit Windows locks -on 32-bit filesystems. Secondly any locks that are valid are -then mapped onto UNIX fcntl byte range locks. These are the -locks that will be seen by UNIX processes. If there is a conflict -here the lock is rejected.

    Note that if a client has an oplock then it "knows" that no -other client can have the file open so usually doesn't bother -to send to lock request to the server - this means once again -if you need to share files between UNIX and Windows processes -either use IRIX or Linux, or turn off oplocks for these -files/shares.

    Chapter 4. Quick Cross Subnet Browsing / Cross Workgroup Browsing guide

    This document should be read in conjunction with Browsing and may -be taken as the fast track guide to implementing browsing across subnets -and / or across workgroups (or domains). WINS is the best tool for resolution -of NetBIOS names to IP addesses. WINS is NOT involved in browse list handling -except by way of name to address mapping.

    3.6. LDAP

    4.1. Discussion

    3.6.1. Introduction

    Firstly, all MS Windows networking is based on SMB (Server Message -Block) based messaging. SMB messaging is implemented using NetBIOS. Samba -implements NetBIOS by encapsulating it over TCP/IP. MS Windows products can -do likewise. NetBIOS based networking uses broadcast messaging to affect -browse list management. When running NetBIOS over TCP/IP this uses UDP -based messaging. UDP messages can be broadcast or unicast.

    This document describes how to use an LDAP directory for storing Samba user +account information traditionally stored in the smbpasswd(5) file. It is +assumed that the reader already has a basic understanding of LDAP concepts +and has a working directory server already installed. For more information +on LDAP architectures and Directories, please refer to the following sites.

    Normally, only unicast UDP messaging can be forwarded by routers. The -"remote announce" parameter to smb.conf helps to project browse announcements -to remote network segments via unicast UDP. Similarly, the "remote browse sync" -parameter of smb.conf implements browse list collation using unicast UDP.

    • Secondly, in those networks where Samba is the only SMB server technology -wherever possible nmbd should be configured on one (1) machine as the WINS -server. This makes it easy to manage the browsing environment. If each network -segment is configured with it's own Samba WINS server, then the only way to -get cross segment browsing to work is by using the "remote announce" and -the "remote browse sync" parameters to your smb.conf file.

      OpenLDAP - http://www.openldap.org/

    • If only one WINS server is used then the use of the "remote announce" and the -"remote browse sync" parameters should NOT be necessary.

      iPlanet Directory Server - http://iplanet.netscape.com/directory

    Samba WINS does not support MS-WINS replication. This means that when setting up -Samba as a WINS server there must only be one nmbd configured as a WINS server -on the network. Some sites have used multiple Samba WINS servers for redundancy -(one server per subnet) and then used "remote browse sync" and "remote announce" -to affect browse list collation across all segments. Note that this means -clients will only resolve local names, and must be configured to use DNS to -resolve names on other subnets in order to resolve the IP addresses of the -servers they can see on other subnets. This setup is not recommended, but is -mentioned as a practical consideration (ie: an 'if all else fails' scenario).

    Note that O'Reilly Publishing is working on +a guide to LDAP for System Administrators which has a planned release date of +early summer, 2002.

    Lastly, take note that browse lists are a collection of unreliable broadcast -messages that are repeated at intervals of not more than 15 minutes. This means -that it will take time to establish a browse list and it can take up to 45 -minutes to stabilise, particularly across network segments.

    Two additional Samba resources which may prove to be helpful are

    • The Samba-PDC-LDAP-HOWTO + maintained by Ignacio Coupeau.

    • The NT migration scripts from IDEALX that are + geared to manage users and group in such a Samba-LDAP Domain Controller configuration. +

    4.2. Use of the "Remote Announce" parameter

    3.6.2. Introduction

    The "remote announce" parameter of smb.conf can be used to forcibly ensure -that all the NetBIOS names on a network get announced to a remote network. -The syntax of the "remote announce" parameter is: -

    	remote announce = a.b.c.d [e.f.g.h] ...
    Traditionally, when configuring "encrypt +passwords = yes" in Samba's smb.conf file, user account +information such as username, LM/NT password hashes, password change times, and account +flags have been stored in the smbpasswd(5) file. There are several +disadvantages to this approach for sites with very large numbers of users (counted +in the thousands).

    • The first is that all lookups must be performed sequentially. Given that +there are approximately two lookups per domain logon (one for a normal +session connection such as when mapping a network drive or printer), this +is a performance bottleneck for lareg sites. What is needed is an indexed approach +such as is used in databases.

    • The second problem is that administrators who desired to replicate a +smbpasswd file to more than one Samba server were left to use external +tools such as rsync(1) and ssh(1) -_or_ -

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

    • And finally, the amount of information which is stored in an +smbpasswd entry leaves no room for additional attributes such as +a home directory, password expiration time, or even a Relative +Identified (RID).

    As a result of these defeciencies, a more robust means of storing user attributes +used by smbd was developed. The API which defines access to user accounts +is commonly referred to as the samdb interface (previously this was called the passdb +API, and is still so named in the CVS trees). In Samba 2.2.3, enabling support +for a samdb backend (e.g. --with-ldapsam or +--with-tdbsam) requires compile time support.

    When compiling Samba to include the --with-ldapsam autoconf +option, smbd (and associated tools) will store and lookup user accounts in +an LDAP directory. In reality, this is very easy to understand. If you are +comfortable with using an smbpasswd file, simply replace "smbpasswd" with +"LDAP directory" in all the documentation.

    There are a few points to stress about what the --with-ldapsam - -where: -

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

    • is either the LMB (Local Master Browser) IP address -or the broadcst address of the remote network. -ie: the LMB is at 192.168.1.10, or the address -could be given as 192.168.1.255 where the netmask -is assumed to be 24 bits (255.255.255.0). -When the remote announcement is made to the broadcast -address of the remote network every host will receive -our announcements. This is noisy and therefore -undesirable but may be necessary if we do NOT know -the IP address of the remote LMB.

    WORKGROUP
    A means of retrieving user account information from + an Windows 2000 Active Directory server.

  • is optional and can be either our own workgroup -or that of the remote network. If you use the -workgroup name of the remote network then our -NetBIOS machine names will end up looking like -they belong to that workgroup, this may cause -name resolution problems and should be avoided.

    • A means of replacing /etc/passwd.

    The second item can be accomplished by using LDAP NSS and PAM modules. LGPL +versions of these libraries can be obtained from PADL Software +(http://www.padl.com/). However, +the details of configuring these packages are beyond the scope of this document.

    4.3. Use of the "Remote Browse Sync" parameter

    The "remote browse sync" parameter of smb.conf is used to announce to -another LMB that it must synchronise it's NetBIOS name list with our -Samba LMB. It works ONLY if the Samba server that has this option is -simultaneously the LMB on it's network segment.

    3.6.3. Supported LDAP Servers

    The syntax of the "remote browse sync" parameter is: -

    	remote browse sync = a.b.c.d
    - -where a.b.c.d is either the IP address of the remote LMB or else is the network broadcast address of the remote segment.

    The LDAP samdb code in 2.2.3 has been developed and tested using the OpenLDAP +2.0 server and client libraries. The same code should be able to work with +Netscape's Directory Server and client SDK. However, due to lack of testing +so far, there are bound to be compile errors and bugs. These should not be +hard to fix. If you are so inclined, please be sure to forward all patches to +samba-patches@samba.org and +jerry@samba.org.

    4.4. Use of WINS

    3.6.4. Schema and Relationship to the RFC 2307 posixAccount

    Use of WINS (either Samba WINS _or_ MS Windows NT Server WINS) is highly -recommended. Every NetBIOS machine registers it's name together with a -name_type value for each of of several types of service it has available. -eg: It registers it's name directly as a unique (the type 0x03) name. -It also registers it's name if it is running the lanmanager compatible -server service (used to make shares and printers available to other users) -by registering the server (the type 0x20) name.

    Samba 3.0 includes the necessary schema file for OpenLDAP 2.0 in +examples/LDAP/samba.schema. The sambaAccount objectclass is given here:

    All NetBIOS names are up to 15 characters in length. The name_type variable -is added to the end of the name - thus creating a 16 character name. Any -name that is shorter than 15 characters is padded with spaces to the 15th -character. ie: All NetBIOS names are 16 characters long (including the -name_type information).

    objectclass ( 1.3.1.5.1.4.1.7165.2.2.2 NAME 'sambaAccount' SUP top STRUCTURAL
+     DESC 'Samba Account'
+     MUST ( uid $ rid )
+     MAY  ( cn $ lmPassword $ ntPassword $ pwdLastSet $ logonTime $
+            logoffTime $ kickoffTime $ pwdCanChange $ pwdMustChange $ acctFlags $
+            displayName $ smbHome $ homeDrive $ scriptPath $ profilePath $
+            description $ userWorkstations $ primaryGroupID $ domain ))

    WINS can store these 16 character names as they get registered. A client -that wants to log onto the network can ask the WINS server for a list -of all names that have registered the NetLogon service name_type. This saves -broadcast traffic and greatly expedites logon processing. Since broadcast -name resolution can not be used across network segments this type of -information can only be provided via WINS _or_ via statically configured -"lmhosts" files that must reside on all clients in the absence of WINS.

    WINS also serves the purpose of forcing browse list synchronisation by all -LMB's. LMB's must synchronise their browse list with the DMB (domain master -browser) and WINS helps the LMB to identify it's DMB. By definition this -will work only within a single workgroup. Note that the domain master browser -has NOTHING to do with what is referred to as an MS Windows NT Domain. The -later is a reference to a security environment while the DMB refers to the -master controller for browse list information only.

    Use of WINS will work correctly only if EVERY client TCP/IP protocol stack -has been configured to use the WINS server/s. Any client that has not been -configured to use the WINS server will continue to use only broadcast based -name registration so that WINS may NEVER get to know about it. In any case, -machines that have not registered with a WINS server will fail name to address -lookup attempts by other clients and will therefore cause workstation access -errors.

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

    The samba.schema file has been formatted for OpenLDAP 2.0. The OID's are +owned by the Samba Team and as such is legal to be openly published. +If you translate the schema to be used with Netscape DS, please +submit the modified schema file as a patch to jerry@samba.org

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

    Just as the smbpasswd file is mean to store information which supplements a +user's /etc/passwd entry, so is the sambaAccount object +meant to supplement the UNIX user account information. A sambaAccount is a +STRUCTURAL objectclass so it can be stored individually +in the directory. However, there are several fields (e.g. uid) which overlap +with the posixAccount objectclass outlined in RFC2307. This is by design.

    DO NOT EVER use both "wins support = yes" together with "wins server = a.b.c.d" -particularly not using it's own IP address.

    In order to store all user account information (UNIX and Samba) in the directory, +it is necessary to use the sambaAccount and posixAccount objectclasses in +combination. However, smbd will still obtain the user's UNIX account +information via the standard C library calls (e.g. getpwnam(), et. al.). +This means that the Samba server must also have the LDAP NSS library installed +and functioning correctly. This division of information makes it possible to +store all Samba account information in LDAP, but still maintain UNIX account +information in NIS while the network is transitioning to a full LDAP infrastructure.

    3.6.5. Configuring Samba with LDAP

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

    3.6.5.1. OpenLDAP configuration

    A very common cause of browsing problems results from installing more than -one protocol on an MS Windows machine.

    To include support for the sambaAccount object in an OpenLDAP directory +server, first copy the samba.schema file to slapd's configuration directory.

    Every NetBIOS machine take part in a process of electing the LMB (and DMB) -every 15 minutes. A set of election criteria is used to determine the order -of precidence for winning this election process. A machine running Samba or -Windows NT will be biased so that the most suitable machine will predictably -win and thus retain it's role.

    root# cp samba.schema /etc/openldap/schema/

    The election process is "fought out" so to speak over every NetBIOS network -interface. In the case of a Windows 9x machine that has both TCP/IP and IPX -installed and has NetBIOS enabled over both protocols the election will be -decided over both protocols. As often happens, if the Windows 9x machine is -the only one with both protocols then the LMB may be won on the NetBIOS -interface over the IPX protocol. Samba will then lose the LMB role as Windows -9x will insist it knows who the LMB is. Samba will then cease to function -as an LMB and thus browse list operation on all TCP/IP only machines will -fail.

    Next, include the samba.schema file in slapd.conf. +The sambaAccount object contains two attributes which depend upon other schema +files. The 'uid' attribute is defined in cosine.schema and +the 'displayName' attribute is defined in the inetorgperson.schema +file. Both of these must be included before the samba.schema file.

    The safest rule of all to follow it this - USE ONLY ONE PROTOCOL!

    ## /etc/openldap/slapd.conf
+
+## schema files (core.schema is required by default)
+include	           /etc/openldap/schema/core.schema
+
+## needed for sambaAccount
+include            /etc/openldap/schema/cosine.schema
+include            /etc/openldap/schema/inetorgperson.schema
+include            /etc/openldap/schema/samba.schema
+
+## uncomment this line if you want to support the RFC2307 (NIS) schema
+## include         /etc/openldap/schema/nis.schema
+
+....

    It is recommended that you maintain some indices on some of the most usefull attributes, +like in the following example, to speed up searches made on sambaAccount objectclasses +(and possibly posixAccount and posixGroup as well).

    # Indices to maintain
+## required by OpenLDAP 2.0
+index objectclass   eq
+
+## support pb_getsampwnam()
+index uid           pres,eq
+## support pdb_getsambapwrid()
+index rid           eq
+
+## uncomment these if you are storing posixAccount and
+## posixGroup entries in the directory as well
+##index uidNumber     eq
+##index gidNumber     eq
+##index cn            eq
+##index memberUid     eq

    4.6. Name Resolution Order

    3.6.5.2. Configuring Samba

    The following parameters are available in smb.conf only with --with-ldapsam +was included with compiling Samba.

    Resolution of NetBIOS names to IP addresses can take place using a number -of methods. The only ones that can provide NetBIOS name_type information -are: -

    WINS: the best tool!
    LMHOSTS: is static and hard to maintain.
    Broadcast: uses UDP and can not resolve names across remote segments.

    These are described in the smb.conf(5) man +page and so will not be repeated here. However, a sample smb.conf file for +use with an LDAP directory could appear as

    ## /usr/local/samba/lib/smb.conf
+[global]
+     security = user
+     encrypt passwords = yes
+
+     netbios name = TASHTEGO
+     workgroup = NARNIA
+
+     # ldap related parameters
+
+     # define the DN to use when binding to the directory servers
+     # The password for this DN is not stored in smb.conf.  Rather it
+     # must be set by using 'smbpasswd -w secretpw' to store the
+     # passphrase in the secrets.tdb file.  If the "ldap admin dn" values
+     # changes, this password will need to be reset.
+     ldap admin dn = "cn=Samba Manager,ou=people,dc=samba,dc=org"
+
+     #  specify the LDAP server's hostname (defaults to locahost)
+     ldap server = ahab.samba.org
+
+     # Define the SSL option when connecting to the directory
+     # ('off', 'start tls', or 'on' (default))
+     ldap ssl = start tls
+
+     # define the port to use in the LDAP session (defaults to 636 when
+     # "ldap ssl = on")
+     ldap port = 389
+
+     # specify the base DN to use when searching the directory
+     ldap suffix = "ou=people,dc=samba,dc=org"
+
+     # generally the default ldap search filter is ok
+     # ldap filter = "(&(uid=%u)(objectclass=sambaAccount))"

    3.6.6. Accounts and Groups management

    As users accounts are managed thru the sambaAccount objectclass, you should +modify you existing administration tools to deal with sambaAccount attributes.

    Machines accounts are managed with the sambaAccount objectclass, just +like users accounts. However, it's up to you to stored thoses accounts +in a different tree of you LDAP namespace: you should use +"ou=Groups,dc=plainjoe,dc=org" to store groups and +"ou=People,dc=plainjoe,dc=org" to store users. Just configure your +NSS and PAM accordingly (usually, in the /etc/ldap.conf configuration +file).

    In Samba release 3.0, the group management system is based on posix +groups. This means that Samba make usage of the posixGroup objectclass. +For now, there is no NT-like group system management (global and local +groups).

    3.6.7. Security and sambaAccount

    There are two important points to remember when discussing the security +of sambaAccount entries in the directory.

    • Never retrieve the lmPassword or + ntPassword attribute values over an unencrypted LDAP session.

    • Never allow non-admin users to + view the lmPassword or ntPassword attribute values.

    These password hashes are clear text equivalents and can be used to impersonate +the user without deriving the original clear text strings. For more information +on the details of LM/NT password hashes, refer to the ENCRYPTION chapter of the Samba-HOWTO-Collection.

    To remedy the first security issue, the "ldap ssl" smb.conf parameter defaults +to require an encrypted session (ldap ssl = on) using +the default port of 636 +when contacting the directory server. When using an OpenLDAP 2.0 server, it +is possible to use the use the StartTLS LDAP extended operation in the place of +LDAPS. In either case, you are strongly discouraged to disable this security +(ldap ssl = off).

    Note that the LDAPS protocol is deprecated in favor of the LDAPv3 StartTLS +extended operation. However, the OpenLDAP library still provides support for +the older method of securing communication between clients and servers.

    The second security precaution is to prevent non-administrative users from +harvesting password hashes from the directory. This can be done using the +following ACL in slapd.conf:

    ## allow the "ldap admin dn" access, but deny everyone else
+access to attrs=lmPassword,ntPassword
+     by dn="cn=Samba Admin,ou=people,dc=plainjoe,dc=org" write
+     by * none

    3.6.8. LDAP specials attributes for sambaAccounts

    The sambaAccount objectclass is composed of the following attributes:

    • lmPassword: the LANMAN password 16-byte hash stored as a character + representation of a hexidecimal string.

    • ntPassword: the NT password hash 16-byte stored as a character + representation of a hexidecimal string.

    • pwdLastSet: The integer time in seconds since 1970 when the + lmPassword and ntPassword attributes were last set. +

    • acctFlags: string of 11 characters surrounded by square brackets [] + representing account flags such as U (user), W(workstation), X(no password expiration), and + D(disabled).

    • logonTime: Integer value currently unused

    • logoffTime: Integer value currently unused

    • kickoffTime: Integer value currently unused

    • pwdCanChange: Integer value currently unused

    • pwdMustChange: Integer value currently unused

    • homeDrive: specifies the drive letter to which to map the + UNC path specified by homeDirectory. The drive letter must be specified in the form "X:" + where X is the letter of the drive to map. Refer to the "logon drive" parameter in the + smb.conf(5) man page for more information.

    • scriptPath: The scriptPath property specifies the path of + the user's logon script, .CMD, .EXE, or .BAT file. The string can be null. The path + is relative to the netlogon share. Refer to the "logon script" parameter in the + smb.conf(5) man page for more information.

    • profilePath: specifies a path to the user's profile. + This value can be a null string, a local absolute path, or a UNC path. Refer to the + "logon path" parameter in the smb.conf(5) man page for more information.

    • smbHome: The homeDirectory property specifies the path of + the home directory for the user. The string can be null. If homeDrive is set and specifies + a drive letter, homeDirectory should be a UNC path. The path must be a network + UNC path of the form \\server\share\directory. This value can be a null string. + Refer to the "logon home" parameter in the smb.conf(5) man page for more information. +

    • userWorkstation: character string value currently unused. +

    • rid: the integer representation of the user's relative identifier + (RID).

    • primaryGroupID: the relative identifier (RID) of the primary group + of the user.

    The majority of these parameters are only used when Samba is acting as a PDC of +a domain (refer to the Samba-PDC-HOWTO for details on +how to configure Samba as a Primary Domain Controller). The following four attributes +are only stored with the sambaAccount entry if the values are non-default values:

    • smbHome

    • scriptPath

    • logonPath

    • homeDrive

    These attributes are only stored with the sambaAccount entry if +the values are non-default values. For example, assume TASHTEGO has now been +configured as a PDC and that logon home = \\%L\%u was defined in +its smb.conf file. When a user named "becky" logons to the domain, +the logon home string is expanded to \\TASHTEGO\becky. +If the smbHome attribute exists in the entry "uid=becky,ou=people,dc=samba,dc=org", +this value is used. However, if this attribute does not exist, then the value +of the logon home parameter is used in its place. Samba +will only write the attribute value to the directory entry is the value is +something other than the default (e.g. \\MOBY\becky).

    3.6.9. Example LDIF Entries for a sambaAccount

    The following is a working LDIF with the inclusion of the posixAccount objectclass:

    Alternative means of name resolution includes: -

    dn: uid=guest2, ou=people,dc=plainjoe,dc=org
+ntPassword: 878D8014606CDA29677A44EFA1353FC7
+pwdMustChange: 2147483647
+primaryGroupID: 1201
+lmPassword: 552902031BEDE9EFAAD3B435B51404EE
+pwdLastSet: 1010179124
+logonTime: 0
+objectClass: sambaAccount
+uid: guest2
+kickoffTime: 2147483647
+acctFlags: [UX         ]
+logoffTime: 2147483647
+rid: 19006
+pwdCanChange: 0

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

    The following is an LDIF entry for using both the sambaAccount and +posixAccount objectclasses:

    Many sites want to restrict DNS lookups and want to avoid broadcast name -resolution traffic. The "name resolve order" parameter is of great help here. -The syntax of the "name resolve order" parameter is: -

    	name resolve order = wins lmhosts bcast host
    -_or_ -
    	name resolve order = wins lmhosts  	(eliminates bcast and host)
    -The default is: -
    	name  resolve order = host lmhost wins bcast
    .
-where "host" refers the the native methods used by the Unix system
-to implement the gethostbyname() function call. This is normally
-controlled by /etc/host.conf, /etc/nsswitch.conf and /etc/resolv.conf.
    dn: uid=gcarter, ou=people,dc=plainjoe,dc=org
+logonTime: 0
+displayName: Gerald Carter
+lmPassword: 552902031BEDE9EFAAD3B435B51404EE
+primaryGroupID: 1201
+objectClass: posixAccount
+objectClass: sambaAccount
+acctFlags: [UX         ]
+userPassword: {crypt}BpM2ej8Rkzogo
+uid: gcarter
+uidNumber: 9000
+cn: Gerald Carter
+loginShell: /bin/bash
+logoffTime: 2147483647
+gidNumber: 100
+kickoffTime: 2147483647
+pwdLastSet: 1010179230
+rid: 19000
+homeDirectory: /home/tashtego/gcarter
+pwdCanChange: 0
+pwdMustChange: 2147483647
+ntPassword: 878D8014606CDA29677A44EFA1353FC7

    Chapter 5. LanMan and NT Password Encryption in Samba

    3.7. MySQL

    5.1. Introduction

    3.7.1. Building

    Newer windows clients send encrypted passwords over - the wire, instead of plain text passwords. The newest clients - will only send encrypted passwords and refuse to send plain text - passwords, unless their registry is tweaked.

    To build the plugin, run make bin/pdb_mysql.so +in the source/ directory of samba distribution.

    These passwords can't be converted to unix style encrypted - passwords. Because of that you can't use the standard unix - user database, and you have to store the Lanman and NT hashes - somewhere else. For more information, see the documentation - about the Next, copy pdb_mysql.so to any location you want. I +strongly recommend installing it in $PREFIX/lib or /usr/lib/samba/

    3.7.2. Creating the database

    You either can set up your own table and specify the field names to pdb_mysql (see below +for the column names) or use the default table. The file examples/pdb/mysql/mysql.dump +contains the correct queries to create the required tables. Use the command : + +passdb backend = parameter. -

    mysql -uusername -hhostname -ppassword databasename < /path/to/samba/examples/pdb/mysql/mysql.dump

    5.2. Important Notes About Security

    3.7.3. Configuring

    The unix and SMB password encryption techniques seem similar - on the surface. This similarity is, however, only skin deep. The unix - scheme typically sends clear text passwords over the network when - logging in. This is bad. The SMB encryption scheme never sends the - cleartext password over the network but it does store the 16 byte - hashed values on disk. This is also bad. Why? Because the 16 byte hashed - values are a "password equivalent". You cannot derive the user's - password from them, but they could potentially be used in a modified - client to gain access to a server. This would require considerable - technical knowledge on behalf of the attacker but is perfectly possible. - You should thus treat the smbpasswd file as though it contained the - cleartext passwords of all your users. Its contents must be kept - secret, and the file should be protected accordingly.

    This plugin lacks some good documentation, but here is some short info:

    Ideally we would like a password scheme which neither requires - plain text passwords on the net or on disk. Unfortunately this - is not available as Samba is stuck with being compatible with - other SMB systems (WinNT, WfWg, Win95 etc).

    Add a the following to the passdb backend variable in your smb.conf: +
    passdb backend = [other-plugins] plugin:/location/to/pdb_mysql.so:identifier [other-plugins]

    The identifier can be any string you like, as long as it doesn't collide with +the identifiers of other plugins or other instances of pdb_mysql. If you +specify multiple pdb_mysql.so entries in 'passdb backend', you also need to +use different identifiers!

    Additional options can be given thru the smb.conf file in the [global] section.

    identifier:mysql host                     - host name, defaults to 'localhost'
+identifier:mysql password
+identifier:mysql user                     - defaults to 'samba'
+identifier:mysql database                 - defaults to 'samba'
+identifier:mysql port                     - defaults to 3306
+identifier:table                          - Name of the table containing users

    Warning

    Note that Windows NT 4.0 Service pack 3 changed the - default for permissible authentication so that plaintext - passwords are never sent over the wire. - The solution to this is either to switch to encrypted passwords - with Samba or edit the Windows NT registry to re-enable plaintext - passwords. See the document WinNT.txt for details on how to do - this.

    Other Microsoft operating systems which also exhibit - this behavior includes

    • MS DOS Network client 3.0 with - the basic network redirector installed

    • Windows 95 with the network redirector - update installed

    • Since the password for the mysql user is stored in the +smb.conf file, you should make the the smb.conf file +readable only to the user that runs samba. This is considered a security +bug and will be fixed soon.

    Windows 98 [se]

  • Names of the columns in this table(I've added column types those columns should have first):

    Windows 2000

    • identifier:logon time column             - int(9)
+identifier:logoff time column            - int(9)
+identifier:kickoff time column           - int(9)
+identifier:pass last set time column     - int(9)
+identifier:pass can change time column   - int(9)
+identifier:pass must change time column  - int(9)
+identifier:username column               - varchar(255) - unix username
+identifier:domain column                 - varchar(255) - NT domain user is part of
+identifier:nt username column            - varchar(255) - NT username
+identifier:fullname column            - varchar(255) - Full name of user
+identifier:home dir column               - varchar(255) - Unix homedir path
+identifier:dir drive column              - varchar(2) - Directory drive path (eg: 'H:')
+identifier:logon script column           - varchar(255) - Batch file to run on client side when logging on
+identifier:profile path column           - varchar(255) - Path of profile
+identifier:acct desc column              - varchar(255) - Some ASCII NT user data
+identifier:workstations column           - varchar(255) - Workstations user can logon to (or NULL for all)
+identifier:unknown string column         - varchar(255) - unknown string
+identifier:munged dial column            - varchar(255) - ?
+identifier:uid column                    - int(9) - Unix user ID (uid)
+identifier:gid column                    - int(9) - Unix user group (gid)
+identifier:user sid column               - varchar(255) - NT user SID
+identifier:group sid column              - varchar(255) - NT group ID
+identifier:lanman pass column            - varchar(255) - encrypted lanman password
+identifier:nt pass column                - varchar(255) - encrypted nt passwd
+identifier:plain pass column             - varchar(255) - plaintext password
+identifier:acct control column           - int(9) - nt user data
+identifier:unknown 3 column              - int(9) - unknown
+identifier:logon divs column             - int(9) - ?
+identifier:hours len column              - int(9) - ?
+identifier:unknown 5 column              - int(9) - unknown
+identifier:unknown 6 column              - int(9) - unknown

    Note :All current release of - Microsoft SMB/CIFS clients support authentication via the - SMB Challenge/Response mechanism described here. Enabling - clear text authentication does not disable the ability - of the client to participate in encrypted authentication.

    Eventually, you can put a colon (:) after the name of each column, which +should specify the column to update when updating the table. You can also +specify nothing behind the colon - then the data from the field will not be +updated.

    5.2.1. Advantages of SMB Encryption

    3.7.4. Using plaintext passwords or encrypted password

    • I strongly discourage the use of plaintext passwords, however, you can use them:

      plain text passwords are not passed across - the network. Someone using a network sniffer cannot just - record passwords going to the SMB server.

    • If you would like to use plaintext passwords, set 'identifier:lanman pass column' and 'identifier:nt pass column' to 'NULL' (without the quotes) and 'identifier:plain pass column' to the name of the column containing the plaintext passwords.

      WinNT doesn't like talking to a server - that isn't using SMB encrypted passwords. It will refuse - to browse the server if the server is also in user level - security mode. It will insist on prompting the user for the - password on each connection, which is very annoying. The - only things you can do to stop this is to use SMB encryption. -

    If you use encrypted passwords, set the 'identifier:plain pass column' to 'NULL' (without the quotes). This is the default.

    5.2.2. Advantages of non-encrypted passwords

    3.7.5. Getting non-column data from the table

    • It is possible to have not all data in the database and making some 'constant'.

      plain text passwords are not kept - on disk.

    • For example, you can set 'identifier:fullname column' to : +CONCAT(First_name,' ',Sur_name)

      uses same password file as other unix - services such as login and ftp

    • Or, set 'identifier:workstations column' to : +NULL

      you are probably already using other - services (such as telnet and ftp) which send plain text - passwords over the net, so sending them for SMB isn't - such a big deal.

    See the MySQL documentation for more language constructs.

    5.3. The smbpasswd Command

    The smbpasswd command maintains the two 32 byte password fields - in the smbpasswd file. If you wish to make it similar to the unix - passwd or yppasswd programs, - install it in /usr/local/samba/bin/ (or your - main Samba binary directory).

    3.8. Passdb XML plugin

    3.8.1. Building

    smbpasswd now works in a client-server mode - where it contacts the local smbd to change the user's password on its - behalf. This has enormous benefits - as follows.

    This module requires libxml2 to be installed.

    To build pdb_xml, run: smbpasswd now has the capability - to change passwords on Windows NT servers (this only works when - the request is sent to the NT Primary Domain Controller if you - are changing an NT Domain user's password).

    To run smbpasswd as a normal user just type :

    $ smbpasswd

    Old SMB password: <type old value here - - or hit return if there was no old password>

    New SMB Password: <type new value> -

    Repeat New SMB Password: <re-type new value -

    If the old value does not match the current value stored for - that user, or the two new values do not match each other, then the - password will not be changed.

    If invoked by an ordinary user it will only allow the user - to change his or her own Samba password.

    If run by the root user smbpasswd may take an optional - argument, specifying the user name whose SMB password you wish to - change. Note that when run as root smbpasswd does not prompt for - or check the old password value, thus allowing root to set passwords - for users who have forgotten their passwords.

    make bin/pdb_xml.so in +the directory source/.

    3.8.2. Usage

    smbpasswd is designed to work in the same way - and be familiar to UNIX users who use the passwd or - The usage of pdb_xml is pretty straightforward. To export data, use: + +yppasswd commands.

    pdbedit -e plugin:/usr/lib/samba/pdb_xml.so:filename + +(where filename is the name of the file to put the data in)

    For more details on using To import data, use: +smbpasswd refer - to the man page which will always be the definitive reference.

    pdbedit -i plugin:/usr/lib/samba/pdb_xml.so:filename -e current-pdb + +Where filename is the name to read the data from and current-pdb to put it in.

    Introduction

    This part contains information on using samba in a (NT 4 or ADS) domain. -If you wish to run samba as a domain member or DC, read the appropriate chapter in -this part.

    Samba can operate in various SMB networks. This part contains information on configuring samba +for various environments.

    Table of Contents
    6. 4. User and Share security level (for servers not in a domain)
    5. How to Configure Samba as a NT4 Primary Domain ControllerSamba as a NT4 or Win2k Primary Domain Controller
    6.1. 5.1. Prerequisite Reading
    6.2. 5.2. Background
    6.3. 5.3. Configuring the Samba Domain Controller
    6.4. 5.4. Creating Machine Trust Accounts and Joining Clients to the Domain
    6.4.1. 5.4.1. Manual Creation of Machine Trust Accounts
    6.4.2. 5.4.2. "On-the-Fly" Creation of Machine Trust Accounts
    6.4.3. 5.4.3. Joining the Client to the Domain
    6.5. 5.5. Common Problems and Errors
    6.6. 5.6. System Policies and Profiles
    6.7. 5.7. What other help can I get?
    6.8. 5.8. Domain Control for Windows 9x/ME
    6.8.1. 5.8.1. Configuration Instructions: Network Logons
    6.8.2. 5.8.2. Configuration Instructions: Setting up Roaming User Profiles
    6.9. DOMAIN_CONTROL.txt : Windows NT Domain Control & Samba5.9. DOMAIN_CONTROL.txt : Windows NT Domain Control & Samba
    7. 6. How to Act as a Backup Domain Controller in a Purely Samba Controlled Domain
    7.1. 6.1. Prerequisite Reading
    7.2. 6.2. Background
    7.3. 6.3. What qualifies a Domain Controller on the network?
    7.3.1. 6.3.1. How does a Workstation find its domain controller?
    7.3.2. 6.3.2. When is the PDC needed?
    7.4. Can Samba be a Backup Domain Controller?6.4. Can Samba be a Backup Domain Controller to an NT PDC?
    7.5. 6.5. How do I set up a Samba BDC?
    7.5.1. 6.5.1. How do I replicate the smbpasswd file?
    6.5.2. Can I do this all with LDAP?
    8. 7. Samba as a ADS domain member
    8.1. 7.1. Installing the required packages for Debian
    8.2. 7.2. Installing the required packages for RedHat
    8.3. 7.3. Compile Samba
    8.4. 7.4. Setup your /etc/krb5.conf
    8.5. 7.5. Create the computer account
    8.5.1. 7.5.1. Possible errors
    8.6. 7.6. Test your server setup
    8.7. 7.7. Testing with smbclient
    8.8. 7.8. Notes
    9. 8. Samba as a NT4 domain memberSamba as a NT4 or Win2k domain member
    9.1. Joining an NT Domain with Samba 2.28.1. Joining an NT Domain with Samba 3.0
    9.2. 8.2. Samba and Windows 2000 Domains
    9.3. 8.3. Why is this better than security = server?

    Chapter 4. User and Share security level (for servers not in a domain)

    A SMB server tells the client at startup what "security level" it is +running. There are two options "share level" and "user level". Which +of these two the client receives affects the way the client then tries +to authenticate itself. It does not directly affect (to any great +extent) the way the Samba server does security. I know this is +strange, but it fits in with the client/server approach of SMB. In SMB +everything is initiated and controlled by the client, and the server +can only tell the client what is available and whether an action is +allowed.

    I'll describe user level security first, as its simpler. In user level +security the client will send a "session setup" command directly after +the protocol negotiation. This contains a username and password. The +server can either accept or reject that username/password +combination. Note that at this stage the server has no idea what +share the client will eventually try to connect to, so it can't base +the "accept/reject" on anything other than:

    1. the username/password

    2. the machine that the client is coming from

    If the server accepts the username/password then the client expects to +be able to mount any share (using a "tree connection") without +specifying a password. It expects that all access rights will be as +the username/password specified in the "session setup".

    It is also possible for a client to send multiple "session setup" +requests. When the server responds it gives the client a "uid" to use +as an authentication tag for that username/password. The client can +maintain multiple authentication contexts in this way (WinDD is an +example of an application that does this)

    Ok, now for share level security. In share level security the client +authenticates itself separately for each share. It will send a +password along with each "tree connection" (share mount). It does not +explicitly send a username with this operation. The client is +expecting a password to be associated with each share, independent of +the user. This means that samba has to work out what username the +client probably wants to use. It is never explicitly sent the +username. Some commercial SMB servers such as NT actually associate +passwords directly with shares in share level security, but samba +always uses the unix authentication scheme where it is a +username/password that is authenticated, not a "share/password".

    Many clients send a "session setup" even if the server is in share +level security. They normally send a valid username but no +password. Samba records this username in a list of "possible +usernames". When the client then does a "tree connection" it also adds +to this list the name of the share they try to connect to (useful for +home directories) and any users listed in the "user =" smb.conf +line. The password is then checked in turn against these "possible +usernames". If a match is found then the client is authenticated as +that user.

    Finally "server level" security. In server level security the samba +server reports to the client that it is in user level security. The +client then does a "session setup" as described earlier. The samba +server takes the username/password that the client sends and attempts +to login to the "password server" by sending exactly the same +username/password that it got from the client. If that server is in +user level security and accepts the password then samba accepts the +clients connection. This allows the samba server to use another SMB +server as the "password server".

    You should also note that at the very start of all this, where the +server tells the client what security level it is in, it also tells +the client if it supports encryption. If it does then it supplies the +client with a random "cryptkey". The client will then send all +passwords in encrypted form. You have to compile samba with encryption +enabled to support this feature, and you have to maintain a separate +smbpasswd file with SMB style encrypted passwords. It is +cryptographically impossible to translate from unix style encryption +to SMB style encryption, although there are some fairly simple management +schemes by which the two could be kept in sync.

    "security = server" means that Samba reports to clients that +it is running in "user mode" but actually passes off all authentication +requests to another "user mode" server. This requires an additional +parameter "password server =" that points to the real authentication server. +That real authentication server can be another Samba server or can be a +Windows NT server, the later natively capable of encrypted password support.

    Chapter 6. How to Configure Samba as a NT4 Primary Domain Controller

    Chapter 5. Samba as a NT4 or Win2k Primary Domain Controller

    6.1. Prerequisite Reading

    5.1. Prerequisite Reading

    Before you continue reading in this chapter, please make sure that you are comfortable with configuring basic files services @@ -3885,9 +4339,9 @@ CLASS="SECT1" >

    6.2. Background

    5.2. Background

    Note

    6.3. Configuring the Samba Domain Controller

    5.3. Configuring the Samba Domain Controller

    The first step in creating a working Samba PDC is to understand the parameters necessary in smb.conf. I will not @@ -4249,9 +4703,9 @@ CLASS="SECT1" >

    6.4. Creating Machine Trust Accounts and Joining Clients to the +>5.4. Creating Machine Trust Accounts and Joining Clients to the Domain

    A machine trust account is a Samba account that is used to @@ -4323,9 +4777,9 @@ CLASS="SECT2" >

    6.4.1. Manual Creation of Machine Trust Accounts

    5.4.1. Manual Creation of Machine Trust Accounts

    The first step in manually creating a machine trust account is to manually create the corresponding Unix account in @@ -4477,7 +4931,7 @@ WIDTH="25" ALIGN="CENTER" VALIGN="TOP" >Warning

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

    5.4.2. "On-the-Fly" Creation of Machine Trust Accounts

    The second (and recommended) way of creating machine trust accounts is simply to allow the Samba server to create them as needed when the client @@ -4541,7 +4995,7 @@ be created manually.

    [global]
-   # <...remainder of parameters...>
+   # <...remainder of parameters...>
    add user script = /usr/sbin/useradd -d /dev/null -g 100 -s /bin/false -M %u

    6.4.3. Joining the Client to the Domain

    5.4.3. Joining the Client to the Domain

    The procedure for joining a client to the domain varies with the version of Windows.

    6.5. Common Problems and Errors

    5.5. Common Problems and Errors

    6.6. System Policies and Profiles

    5.6. System Policies and Profiles

    Much of the information necessary to implement System Policies and Roving User Profiles in a Samba domain is the same as that for @@ -5005,9 +5459,9 @@ CLASS="SECT1" >

    6.7. What other help can I get?

    5.7. What other help can I get?

    There are many sources of information available in the form of mailing lists, RFC's and documentation. The docs that come @@ -5425,9 +5879,9 @@ CLASS="SECT1" >

    6.8. Domain Control for Windows 9x/ME

    5.8. Domain Control for Windows 9x/ME

    Note

  • The client broadcasts (to the IP broadcast address of the subnet it is in) - a NetLogon request. This is sent to the NetBIOS name DOMAIN<1c> at the + a NetLogon request. This is sent to the NetBIOS name DOMAIN<1c> at the NetBIOS layer. The client chooses the first response it receives, which contains the NetBIOS name of the logon server to use in the format of \\SERVER. @@ -5559,9 +6013,9 @@ CLASS="SECT2" >

    6.8.1. Configuration Instructions: Network Logons

    5.8.1. Configuration Instructions: Network Logons

    The main difference between a PDC and a Windows 9x logon server configuration is that

    Warning

    6.8.2. Configuration Instructions: Setting up Roaming User Profiles

    5.8.2. Configuration Instructions: Setting up Roaming User Profiles

    Warning

    6.8.2.1. Windows NT Configuration

    5.8.2.1. Windows NT Configuration

    To support WinNT clients, in the [global] section of smb.conf set the following (for example):

    Note

    6.8.2.2. Windows 9X Configuration

    5.8.2.2. Windows 9X Configuration

    To support Win9X clients, you must use the "logon home" parameter. Samba has now been fixed so that "net use/home" now works as well, and it, too, relies @@ -5800,9 +6254,9 @@ CLASS="SECT3" >

    6.8.2.3. Win9X and WinNT Configuration

    5.8.2.3. Win9X and WinNT Configuration

    You can support profiles for both Win9X and WinNT clients by setting both the "logon home" and "logon path" parameters. For example:

    Note

    6.8.2.4. Windows 9X Profile Setup

    5.8.2.4. Windows 9X Profile Setup

    When a user first logs in on Windows 9X, the file user.DAT is created, as are folders "Start Menu", "Desktop", "Programs" and "Nethood". @@ -6005,9 +6459,9 @@ CLASS="SECT3" >

    6.8.2.5. Windows NT Workstation 4.0

    5.8.2.5. Windows NT Workstation 4.0

    When a user first logs in to a Windows NT Workstation, the profile NTuser.DAT is created. The profile location can be now specified @@ -6026,7 +6480,7 @@ WIDTH="25" ALIGN="CENTER" VALIGN="TOP" >NoteNote

    6.8.2.6. Windows NT Server

    5.8.2.6. Windows NT Server

    There is nothing to stop you specifying any path that you like for the location of users' profiles. Therefore, you could specify that the @@ -6133,9 +6587,9 @@ CLASS="SECT3" >

    6.8.2.7. Sharing Profiles between W95 and NT Workstation 4.0

    5.8.2.7. Sharing Profiles between W95 and NT Workstation 4.0

    WarningNote

    6.9. DOMAIN_CONTROL.txt : Windows NT Domain Control & Samba

    5.9. DOMAIN_CONTROL.txt : Windows NT Domain Control & Samba

    WarningChapter 7. How to Act as a Backup Domain Controller in a Purely Samba Controlled DomainChapter 6. How to Act as a Backup Domain Controller in a Purely Samba Controlled Domain

    7.1. Prerequisite Reading

    6.1. Prerequisite Reading

    Before you continue reading in this chapter, please make sure that you are comfortable with configuring a Samba PDC @@ -6388,9 +6842,9 @@ CLASS="SECT1" >

    7.2. Background

    6.2. Background

    What is a Domain Controller? It is a machine that is able to answer logon requests from workstations in a Windows NT Domain. Whenever a @@ -6433,9 +6887,9 @@ CLASS="SECT1" >

    7.3. What qualifies a Domain Controller on the network?

    6.3. What qualifies a Domain Controller on the network?

    Every machine that is a Domain Controller for the domain SAMBA has to register the NetBIOS group name SAMBA#1c with the WINS server and/or @@ -6450,9 +6904,9 @@ CLASS="SECT2" >

    7.3.1. How does a Workstation find its domain controller?

    6.3.1. How does a Workstation find its domain controller?

    A NT workstation in the domain SAMBA that wants a local user to be authenticated has to find the domain controller for SAMBA. It does @@ -6469,9 +6923,9 @@ CLASS="SECT2" >

    7.3.2. When is the PDC needed?

    6.3.2. When is the PDC needed?

    Whenever a user wants to change his password, this has to be done on the PDC. To find the PDC, the workstation does a NetBIOS name query @@ -6485,15 +6939,19 @@ CLASS="SECT1" >

    7.4. Can Samba be a Backup Domain Controller?

    6.4. Can Samba be a Backup Domain Controller to an NT PDC?

    With version 2.2, no. The native NT SAM replication protocols have not yet been fully implemented. The Samba Team is working on understanding and implementing the protocols, but this work has not been finished for version 2.2.

    With version 3.0, the work on both the replication protocols and a +suitable storage mechanism has progressed, and some form of NT4 BDC +support is expected soon.

    Can I get the benefits of a BDC with Samba? Yes. The main reason for implementing a BDC is availability. If the PDC is a Samba machine, a second Samba machine can be set up to @@ -6504,9 +6962,9 @@ CLASS="SECT1" >

    7.5. How do I set up a Samba BDC?

    6.5. How do I set up a Samba BDC?

    Several things have to be done:

    7.5.1. How do I replicate the smbpasswd file?

    6.5.1. How do I replicate the smbpasswd file?

    Replication of the smbpasswd file is sensitive. It has to be done whenever changes to the SAM are made. Every user's password change is @@ -6587,6 +7045,21 @@ rsync. rsync can use ssh as a transport. ssh itself can be set up to accept *only* rsync transfer without requiring the user to type a password.

    6.5.2. Can I do this all with LDAP?

    The simple answer is YES. Samba's pdb_ldap code supports +binding to a replica LDAP server, and will also follow referrals and +rebind to the master if it ever needs to make a modification to the +database. (Normally BDCs are read only, so this will not occur +often).

    Chapter 8. Samba as a ADS domain memberChapter 7. Samba as a ADS domain member

    This is a rough guide to setting up Samba 3.0 with kerberos authentication against a +Windows2000 KDC.

    Pieces you need before you begin:

    This is a VERY ROUGH guide to setting up the current (November 2001) -pre-alpha version of Samba 3.0 with kerberos authentication against a -Windows2000 KDC. The procedures listed here are likely to change as -the code develops.

    Pieces you need before you begin: -

    8.1. Installing the required packages for Debian

    7.1. Installing the required packages for Debian

    On Debian you need to install the following packages:

    On Debian you need to install the following packages: -

    8.2. Installing the required packages for RedHat

    7.2. Installing the required packages for RedHat

    On RedHat this means you should have at least:

    On RedHat this means you should have at least: -

    8.3. Compile Samba

    7.3. Compile Samba

    If your kerberos libraries are in a non-standard location then remember to add the configure option --with-krb5=DIR.

    After you run configure make sure that include/config.h contains +>After you run configure make sure that include/config.h it + generates contains lines like this:

      realm = YOUR.KERBEROS.REALM
-  ads server = your.kerberos.server
   security = ADS
   encrypt passwords = yes
    Strictly speaking, you can omit the realm name and you can use an IP
-  address for the ads server. In that case Samba will auto-detect these.
    In case samba can't figure out your ads server using your realm name, use the 
+ads server option in smb.conf:
+
      ads server = your.kerberos.server
    You do *not* need a smbpasswd file, although it won't do any harm
-  and if you have one then Samba will be able to fall back to normal
-  password security for older clients. I expect that the above
+>You do *not* need a smbpasswd file, and older clients will
+  be authenticated as if "security = domain", although it won't do any harm
+  and allows you to have local users not in the domain.
+  I expect that the above
   required options will change soon when we get better active
   directory integration.
    8.4. Setup your /etc/krb5.conf
    7.4. Setup your /etc/krb5.conf
    The minimal configuration for krb5.conf is:
    	[realms]
+>[realms]
     YOUR.KERBEROS.REALM = {
 	kdc = your.kerberos.server
     }
    If all you want is kerberos support in smbclient then you can skip
 straight to step 5 now. Step 3 is only needed if you want kerberos
-support in smbd.
    8.5. Create the computer account
    7.5. Create the computer account
    Do a "kinit" as a user that has authority to change arbitrary
-passwords on the KDC ("Administrator" is a good choice). Then as a
-user that has write permission on the Samba private directory
+>As a user that has write permission on the Samba private directory
 (usually root) run:
 
    8.5.1. Possible errors
    7.5.1. Possible errors
    "bash: kinit: command not found"
    kinit is in the krb5-workstation RPM on RedHat systems, and is in /usr/kerberos/bin, so it won't be in the path until you log in again (or open a new terminal)
    "ADS support not compiled in"
    8.6. Test your server setup
    7.6. Test your server setup
    On a Windows 2000 client try 
    8.7. Testing with smbclient
    7.7. Testing with smbclient
    On your Samba server try to login to a Win2000 server or your Samba
 server using smbclient and kerberos. Use smbclient as usual, but
@@ -6866,9 +7343,9 @@ CLASS="SECT1"
 >
    8.8. Notes
    7.8. Notes
    You must change administrator password at least once after DC install,
  to create the right encoding types
    Chapter 9. Samba as a NT4 domain memberChapter 8. Samba as a NT4 or Win2k domain member
    9.1. Joining an NT Domain with Samba 2.2
    8.1. Joining an NT Domain with Samba 3.0
    Assume you have a Samba 2.x server with a NetBIOS name of 
+>Assume you have a Samba 3.0 server with a NetBIOS name of 
 	SERV1 and are joining an NT domain called
+> and are joining an or Win2k NT domain called
 	DOM.
    In order to join the domain, first stop all Samba daemons 
-	and run the command:
    root# smbpasswd -j DOM -r DOMPDC
-	-UAdministrator%password
    as we are joining the domain DOM and the PDC for that domain 
-	(the only machine that has write access to the domain SAM database) 
-	is DOMPDC. The Administrator%password is 
-	the login name and password for an account which has the necessary 
-	privilege to add machines to the domain.  If this is successful 
-	you will see the message:
    smbpasswd: Joined domain DOM.
-	
    in your terminal window. See the 	smbpasswd(8) man page for more details.
    There is existing development code to join a domain
-	without having to create the machine trust account on the PDC
-	beforehand.  This code will hopefully be available soon
-	in release branches as well.
    This command goes through the machine account password 
-	change protocol, then writes the new (random) machine account 
-	password for this Samba server into a file in the same directory 
-	in which an smbpasswd file would be stored - normally :
    /usr/local/samba/private
    In Samba 2.0.x, the filename looks like this:
    <NT DOMAIN NAME>.<Samba 
-	Server Name>.mac
    The .mac suffix stands for machine account 
-	password file. So in our example above, the file would be called:
    DOM.SERV1.mac
    In Samba 2.2, this file has been replaced with a TDB 
-	(Trivial Database) file named secrets.tdb.
-	
    This file is created and owned by root and is not 
-	readable by any other user. It is the key to the domain-level 
-	security for your system, and should be treated as carefully 
-	as a shadow password file.
    Now, before restarting the Samba daemons you must 
-	edit your Firstly, you must edit your security = domain
     or
+	security = ads depending on if the PDC is
+	NT4 or running Active Directory respectivly.
    Next change the  line in the [global]
 	section to read: 
    password server = DOMPDC DOMBDC1 DOMBDC2
    password server = DOMPDC DOMBDC1 DOMBDC2
    These are the primary and backup domain controllers Samba 
+	will attempt to contact in order to authenticate users. Samba will 
+	try to contact each of these servers in order, so you may want to 
+	rearrange this list in order to spread out the authentication load 
+	among domain controllers.
    Alternatively, if you want smbd to automatically determine 
+	the list of Domain controllers to use for authentication, you may 
+	set this line to be :
    password server = *
    This method, allows Samba to use exactly the same
+        mechanism that NT does. This 
+	method either broadcasts or uses a WINS database in order to
+	find domain controllers to authenticate against.
    In order to actually join the domain, you must run this
+        command:
    root# net join -S DOMPDC
+	-UAdministrator%password
    as we are joining the domain DOM and the PDC for that domain 
+	(the only machine that has write access to the domain SAM database) 
+	is DOMPDC. The Administrator%password is 
+	the login name and password for an account which has the necessary 
+	privilege to add machines to the domain.  If this is successful 
+	you will see the message:
    Joined domain DOM.
+	or Joined 'SERV1' to realm 'MYREALM'
+	
    in your terminal window. See the 	net(8) man page for more details.
    These are the primary and backup domain controllers Samba 
-	will attempt to contact in order to authenticate users. Samba will 
-	try to contact each of these servers in order, so you may want to 
-	rearrange this list in order to spread out the authentication load 
-	among domain controllers.
    This process joins the server to thedomain
+	without having to create the machine trust account on the PDC
+	beforehand.
    Alternatively, if you want smbd to automatically determine 
-	the list of Domain controllers to use for authentication, you may 
-	set this line to be :
    This command goes through the machine account password 
+	change protocol, then writes the new (random) machine account 
+	password for this Samba server into a file in the same directory 
+	in which an smbpasswd file would be stored - normally :
    password server = */usr/local/samba/private/secrets.tdb
    This method, which was introduced in Samba 2.0.6, 
-	allows Samba to use exactly the same mechanism that NT does. This 
-	method either broadcasts or uses a WINS database in order to
-	find domain controllers to authenticate against.
    This file is created and owned by root and is not 
+	readable by any other user. It is the key to the domain-level 
+	security for your system, and should be treated as carefully 
+	as a shadow password file.
    Finally, restart your Samba daemons and get ready for 
 	clients to begin using domain security!
    9.2. Samba and Windows 2000 Domains
    8.2. Samba and Windows 2000 Domains
    Many people have asked regarding the state of Samba's ability to participate in
 a Windows 2000 Domain.  Samba 3.0 is able to act as a member server of a Windows
-2000 domain operating in mixed or native mode.
    There is much confusion between the circumstances that require a "mixed" mode
-Win2k DC and a when this host can be switched to "native" mode.  A "mixed" mode
-Win2k domain controller is only needed if Windows NT BDCs must exist in the same
-domain.  By default, a Win2k DC in "native" mode will still support
-NetBIOS and NTLMv1 for authentication of legacy clients such as Windows 9x and 
-NT 4.0.  Samba has the same requirements as a Windows NT 4.0 member server.
    The steps for adding a Samba 2.2 host to a Win2k domain are the same as those
-for adding a Samba server to a Windows NT 4.0 domain. The only exception is that 
-the "Server Manager" from NT 4 has been replaced by the "Active Directory Users and 
-Computers" MMC (Microsoft Management Console) plugin.
    9.3. Why is this better than security = server?
    8.3. Why is this better than security = server?
    Currently, domain security in Samba doesn't free you from 
 	having to create local Unix users to represent the users attaching 
@@ -7203,13 +7640,7 @@ CLASS="COMMAND"
 >And finally, acting in the same manner as an NT server 
 	authenticating to a PDC means that as part of the authentication 
 	reply, the Samba server gets the user identification information such 
-	as the user SID, the list of NT groups the user belongs to, etc. All 
-	this information will allow Samba to be extended in the future into 
-	a mode the developers currently call appliance mode. In this mode, 
-	no local Unix users will be necessary, and Samba will generate Unix 
-	uids and gids from the information passed back from the PDC when a 
-	user is authenticated, making a Samba server truly plug and play 
-	in an NT domain environment. Watch for this code soon.
    Introduction
    Table of Contents
    10. 9. Integrating MS Windows networks with Samba
    10.1. 9.1. Agenda
    10.2. 9.2. Name Resolution in a pure Unix/Linux world
    10.2.1. 9.2.1. /etc/hosts
    10.2.2. 9.2.2. /etc/resolv.conf
    10.2.3. 9.2.3. /etc/host.conf
    10.2.4. 9.2.4. /etc/nsswitch.conf
    10.3. 9.3. Name resolution as used within MS Windows networking
    10.3.1. 9.3.1. The NetBIOS Name Cache
    10.3.2. 9.3.2. The LMHOSTS file
    10.3.3. 9.3.3. HOSTS file
    10.3.4. 9.3.4. DNS Lookup
    10.3.5. 9.3.5. WINS Lookup
    10.4. 9.4. How browsing functions and how to deploy stable and 
 dependable browsing using Samba
    10.5. 9.5. MS Windows security options and how to configure 
 Samba for seemless integration
    10.5.1. 9.5.1. Use MS Windows NT as an authentication server
    10.5.2. 9.5.2. Make Samba a member of an MS Windows NT security domain
    10.5.3. 9.5.3. Configure Samba as an authentication server
    10.6. 9.6. Conclusions
    11. 10. UNIX Permission Bits and Windows NT Access Control Lists
    11.1. 10.1. Viewing and changing UNIX permissions using the NT 
 	security dialogs
    11.2. 10.2. How to view file security on a Samba share
    11.3. 10.3. Viewing file ownership
    11.4. 10.4. Viewing file or directory permissions
    11.4.1. 10.4.1. File Permissions
    11.4.2. 10.4.2. Directory Permissions
    11.5. 10.5. Modifying file or directory permissions
    11.6. 10.6. Interaction with the standard Samba create mask 
 	parameters
    11.7. 10.7. Interaction with the standard Samba file attribute 
 	mapping
    12. 11. Configuring PAM for distributed but centrally 
 managed authentication
    12.1. 11.1. Samba and PAM
    12.2. 11.2. Distributed Authentication
    12.3. 11.3. PAM Configuration in smb.conf
    13. 12. Hosting a Microsoft Distributed File System tree on Samba
    13.1. 12.1. Instructions
    13.1.1. 12.1.1. Notes
    14. 13. Printing Support
    14.1. 13.1. Introduction
    14.2. 13.2. Configuration
    14.2.1. 13.2.1. Creating [print$]
    14.2.2. 13.2.2. Setting Drivers for Existing Printers
    14.2.3. 13.2.3. Support a large number of printers
    14.2.4. 13.2.4. Adding New Printers via the Windows NT APW
    14.2.5. 13.2.5. Samba and Printer Ports
    14.3. 13.3. The Imprints Toolset
    14.3.1. 13.3.1. What is Imprints?
    14.3.2. 13.3.2. Creating Printer Driver Packages
    14.3.3. 13.3.3. The Imprints server
    14.3.4. 13.3.4. The Installation Client
    14.4. 13.4. Diagnosis
    14.4.1. 13.4.1. Introduction
    14.4.2. 13.4.2. Debugging printer problems
    14.4.3. 13.4.3. What printers do I have?
    14.4.4. 13.4.4. Setting up printcap and print servers
    14.4.5. 13.4.5. Job sent, no output
    14.4.6. 13.4.6. Job sent, strange output
    14.4.7. 13.4.7. Raw PostScript printed
    14.4.8. 13.4.8. Advanced Printing
    14.4.9. 13.4.9. Real debugging
    15. Security levels
    15.1. Introduction
    15.2. More complete description of security levels
    16. 14. Unified Logons between Windows NT and UNIX using Winbind
    16.1. 14.1. Abstract
    16.2. 14.2. Introduction
    16.3. 14.3. What Winbind Provides
    16.3.1. 14.3.1. Target Uses
    16.4. 14.4. How Winbind Works
    16.4.1. 14.4.1. Microsoft Remote Procedure Calls
    16.4.2. 14.4.2. Microsoft Active Directory Services
    14.4.3. Name Service Switch
    16.4.3. 14.4.4. Pluggable Authentication Modules
    16.4.4. 14.4.5. User and Group ID Allocation
    16.4.5. 14.4.6. Result Caching
    16.5. 14.5. Installation and Configuration
    16.5.1. 14.5.1. Introduction
    16.5.2. 14.5.2. Requirements
    16.5.3. 14.5.3. Testing Things Out
    16.6. 14.6. Limitations
    16.7. 14.7. Conclusion
    17. Passdb MySQL plugin15. Improved browsing in samba
    17.1. Building
    17.2. Configuring15.1. Overview of browsing
    17.3. Using plaintext passwords or encrypted password15.2. Browsing support in samba
    17.4. Getting non-column data from the table15.3. Problem resolution
    18. Passdb XML plugin15.4. Browsing across subnets
    18.1. Building
    18.2. Usage15.4.1. How does cross subnet browsing work ?
    19. Storing Samba's User/Machine Account information in an LDAP Directory15.5. Setting up a WINS server
    19.1. Purpose15.6. Setting up Browsing in a WORKGROUP
    19.2. Introduction15.7. Setting up Browsing in a DOMAIN
    19.3. Supported LDAP Servers15.8. Forcing samba to be the master
    19.4. Schema and Relationship to the RFC 2307 posixAccount15.9. Making samba the domain master
    19.5. Configuring Samba with LDAP15.10. Note about broadcast addresses
    15.11. Multiple interfaces
    16. Stackable VFS modules
    19.5.1. OpenLDAP configuration16.1. Introduction and configuration
    19.5.2. Configuring Samba16.2. Included modules
    19.6. Accounts and Groups management16.2.1. audit
    19.7. Security and sambaAccount16.2.2. recycle
    19.8. LDAP specials attributes for sambaAccounts16.2.3. netatalk
    19.9. Example LDIF Entries for a sambaAccount16.3. VFS modules available elsewhere
    19.10. Comments16.3.1. DatabaseFS
    16.3.2. vscan
    20. 17. HOWTO Access Samba source code via CVSAccess Samba source code via CVS
    20.1. 17.1. Introduction
    20.2. 17.2. CVS Access to samba.org
    20.2.1. 17.2.1. Access via CVSweb
    20.2.2. 17.2.2. Access via cvs
    21. 18. Group mapping HOWTO
    22. 19. Samba performance issues
    22.1. 19.1. Comparisons
    22.2. Oplocks
    22.2.1. Overview
    22.2.2. Level2 Oplocks19.2. Socket options
    22.2.3. Old 'fake oplocks' option - deprecated19.3. Read size
    22.3. Socket options19.4. Max xmit
    22.4. Read size19.5. Log level
    22.5. Max xmit19.6. Read raw
    22.6. Locking19.7. Write raw
    22.7. Share modes19.8. Slow Clients
    22.8. Log level19.9. Slow Logins
    22.9. Wide lines19.10. Client tuning
    22.10. Read raw20. Creating Group Profiles
    22.11. Write raw20.1. Windows '9x
    22.12. Read prediction20.2. Windows NT 4
    22.13. Memory mapping20.2.1. Side bar Notes
    22.14. Slow Clients20.2.2. Mandatory profiles
    22.15. Slow Logins20.2.3. moveuser.exe
    22.16. Client tuning20.2.4. Get SID
    22.17. My Results20.3. Windows 2000/XP
    Chapter 10. Integrating MS Windows networks with SambaChapter 9. Integrating MS Windows networks with Samba
    10.1. Agenda
    9.1. Agenda
    To identify the key functional mechanisms of MS Windows networking 
 to enable the deployment of Samba as a means of extending and/or 
@@ -8099,9 +8519,9 @@ CLASS="SECT1"
 >
    10.2. Name Resolution in a pure Unix/Linux world
    9.2. Name Resolution in a pure Unix/Linux world
    The key configuration files covered in this section are:
    10.2.1. 9.2.1. /etc/hosts
    10.2.2. 9.2.2. /etc/resolv.conf
    10.2.3. 9.2.3. /etc/host.conf
    10.2.4. 9.2.4. /etc/nsswitch.conf
    10.3. Name resolution as used within MS Windows networking
    9.3. Name resolution as used within MS Windows networking
    MS Windows networking is predicated about the name each machine 
 is given. This name is known variously (and inconsistently) as 
@@ -8380,16 +8800,16 @@ the client/server.
    	Unique NetBIOS Names:
-		MACHINENAME<00>	= Server Service is running on MACHINENAME
-		MACHINENAME<03> = Generic Machine Name (NetBIOS name)
-		MACHINENAME<20> = LanMan Server service is running on MACHINENAME
-		WORKGROUP<1b> = Domain Master Browser
+		MACHINENAME<00>	= Server Service is running on MACHINENAME
+		MACHINENAME<03> = Generic Machine Name (NetBIOS name)
+		MACHINENAME<20> = LanMan Server service is running on MACHINENAME
+		WORKGROUP<1b> = Domain Master Browser
 
 	Group Names:
-		WORKGROUP<03> = Generic Name registered by all members of WORKGROUP
-		WORKGROUP<1c> = Domain Controllers / Netlogon Servers
-		WORKGROUP<1d> = Local Master Browsers
-		WORKGROUP<1e> = Internet Name Resolvers
    It should be noted that all NetBIOS machines register their own 
@@ -8408,7 +8828,7 @@ be needed. An example of this is what happens when an MS Windows client
 wants to locate a domain logon server. It find this service and the IP 
 address of a server that provides it by performing a lookup (via a 
 NetBIOS broadcast) for enumeration of all machines that have 
-registered the name type *<1c>. A logon request is then sent to each 
+registered the name type *<1c>. A logon request is then sent to each 
 IP address that is returned in the enumerated list of IP addresses. Which 
 ever machine first replies then ends up providing the logon services.
    10.3.1. The NetBIOS Name Cache
    9.3.1. The NetBIOS Name Cache
    All MS Windows machines employ an in memory buffer in which is 
 stored the NetBIOS names and IP addresses for all external 
@@ -8470,9 +8890,9 @@ CLASS="SECT2"
 >
    10.3.2. The LMHOSTS file
    9.3.2. The LMHOSTS file
    This file is usually located in MS Windows NT 4.0 or 
 2000 in 
    10.3.3. HOSTS file
    9.3.3. HOSTS file
    This file is usually located in MS Windows NT 4.0 or 2000 in 
 
    10.3.4. DNS Lookup
    9.3.4. DNS Lookup
    This capability is configured in the TCP/IP setup area in the network 
 configuration facility. If enabled an elaborate name resolution sequence 
@@ -8615,9 +9035,9 @@ CLASS="SECT2"
 >
    10.3.5. WINS Lookup
    9.3.5. WINS Lookup
    A WINS (Windows Internet Name Server) service is the equivaent of the 
 rfc1001/1002 specified NBNS (NetBIOS Name Server). A WINS server stores 
@@ -8658,9 +9078,9 @@ CLASS="SECT1"
 >
    10.4. How browsing functions and how to deploy stable and 
+>9.4. How browsing functions and how to deploy stable and 
 dependable browsing using Samba
    As stated above, MS Windows machines register their NetBIOS names 
@@ -8725,9 +9145,9 @@ CLASS="SECT1"
 >
    10.5. MS Windows security options and how to configure 
+>9.5. MS Windows security options and how to configure 
 Samba for seemless integration
    MS Windows clients may use encrypted passwords as part of a 
@@ -8862,9 +9282,9 @@ CLASS="SECT2"
 >
    10.5.1. Use MS Windows NT as an authentication server
    9.5.1. Use MS Windows NT as an authentication server
    This method involves the additions of the following parameters 
 in the smb.conf file:
    10.5.2. Make Samba a member of an MS Windows NT security domain
    9.5.2. Make Samba a member of an MS Windows NT security domain
    This method involves additon of the following paramters in the smb.conf file:
    10.5.3. Configure Samba as an authentication server
    9.5.3. Configure Samba as an authentication server
    This mode of authentication demands that there be on the 
 Unix/Linux system both a Unix style account as well as an 
@@ -8998,9 +9418,9 @@ CLASS="SECT3"
 >
    10.5.3.1. Users
    9.5.3.1. Users
    A user account that may provide a home directory should be 
 created. The following Linux system commands are typical of 
@@ -9021,9 +9441,9 @@ CLASS="SECT3"
 >
    10.5.3.2. MS Windows NT Machine Accounts
    9.5.3.2. MS Windows NT Machine Accounts
    These are required only when Samba is used as a domain 
 controller.  Refer to the Samba-PDC-HOWTO for more details.
    10.6. Conclusions
    9.6. Conclusions
    Samba provides a flexible means to operate as...
    Chapter 11. UNIX Permission Bits and Windows NT Access Control ListsChapter 10. UNIX Permission Bits and Windows NT Access Control Lists
    11.1. Viewing and changing UNIX permissions using the NT 
+>10.1. Viewing and changing UNIX permissions using the NT 
 	security dialogs
    New in the Samba 2.0.4 release is the ability for Windows 
@@ -9099,35 +9519,15 @@ NAME="AEN1593"
 	the security of the UNIX host Samba is running on, and 
 	still obeys all the file permission rules that a Samba 
 	administrator can set.
    In Samba 2.0.4 and above the default value of the 
-	parameter 	nt acl support has been changed from 
-	false to true, so 
- 	manipulation of permissions is turned on by default.
    11.2. How to view file security on a Samba share
    10.2. How to view file security on a Samba share
    From an NT 4.0 client, single-click with the right 
 	mouse button on any file or directory in a Samba mounted 
@@ -9195,9 +9595,9 @@ CLASS="SECT1"
 >
    11.3. Viewing file ownership
    10.3. Viewing file ownership
    Clicking on the 
    11.4. Viewing file or directory permissions
    10.4. Viewing file or directory permissions
    The third button is the 
    11.4.1. File Permissions
    10.4.1. File Permissions
    The standard UNIX user/group/world triple and 
 		the corresponding "read", "write", "execute" permissions 
@@ -9413,9 +9813,9 @@ CLASS="SECT2"
 >
    11.4.2. Directory Permissions
    10.4.2. Directory Permissions
    Directories on an NT NTFS file system have two 
 		different sets of permissions. The first set of permissions 
@@ -9445,9 +9845,9 @@ CLASS="SECT1"
 >
    11.5. Modifying file or directory permissions
    10.5. Modifying file or directory permissions
    Modifying file and directory permissions is as simple 
 	as changing the displayed permissions in the dialog box, and 
@@ -9543,9 +9943,9 @@ CLASS="SECT1"
 >
    11.6. Interaction with the standard Samba create mask 
+>10.6. Interaction with the standard Samba create mask 
 	parameters
    Note that with Samba 2.0.5 there are four new parameters 
@@ -9820,9 +10220,9 @@ CLASS="SECT1"
 >
    11.7. Interaction with the standard Samba file attribute 
+>10.7. Interaction with the standard Samba file attribute 
 	mapping
    Samba maps some of the DOS attribute bits (such as "read 
@@ -9869,16 +10269,16 @@ CLASS="CHAPTER"
 >Chapter 12. Configuring PAM for distributed but centrally 
+>Chapter 11. Configuring PAM for distributed but centrally 
 managed authentication
    12.1. Samba and PAM
    11.1. Samba and PAM
    A number of Unix systems (eg: Sun Solaris), as well as the 
 xxxxBSD family and Linux, now utilize the Pluggable Authentication 
@@ -10090,9 +10490,9 @@ CLASS="SECT1"
 >
    12.2. Distributed Authentication
    11.2. Distributed Authentication
    The astute administrator will realize from this that the 
 combination of 
    12.3. PAM Configuration in smb.conf
    11.3. PAM Configuration in smb.conf
    There is an option in smb.conf called Chapter 13. Hosting a Microsoft Distributed File System tree on SambaChapter 12. Hosting a Microsoft Distributed File System tree on Samba
    13.1. Instructions
    12.1. Instructions
    The Distributed File System (or Dfs) provides a means of 
 	separating the logical view of files and directories that users 
@@ -10319,9 +10719,9 @@ CLASS="SECT2"
 >
    13.1.1. Notes
    12.1.1. Notes
      Chapter 14. Printing SupportChapter 13. Printing Support
      14.1. Introduction
      13.1. Introduction
      Beginning with the 2.2.0 release, Samba supports 
 the native Windows NT printing mechanisms implemented via 
@@ -10443,9 +10843,9 @@ CLASS="SECT1"
 >
      14.2. Configuration
      13.2. Configuration
      Warning
    Next

    Chapter 3. Quick Cross Subnet Browsing / Cross Workgroup Browsing guide

    Chapter 2. Quick Cross Subnet Browsing / Cross Workgroup Browsing guide

    This document should be read in conjunction with Browsing and may be taken as the fast track guide to implementing browsing across subnets @@ -85,7 +86,9 @@ CLASS="SECT1" >

    3.1. Discussion

    2.1. Discussion

    Firstly, all MS Windows networking is based on SMB (Server Message Block) based messaging. SMB messaging is implemented using NetBIOS. Samba @@ -129,7 +132,9 @@ CLASS="SECT1" >

    3.2. Use of the "Remote Announce" parameter

    2.2. Use of the "Remote Announce" parameter

    The "remote announce" parameter of smb.conf can be used to forcibly ensure that all the NetBIOS names on a network get announced to a remote network. @@ -185,7 +190,9 @@ CLASS="SECT1" >

    3.3. Use of the "Remote Browse Sync" parameter

    2.3. Use of the "Remote Browse Sync" parameter

    The "remote browse sync" parameter of smb.conf is used to announce to another LMB that it must synchronise it's NetBIOS name list with our @@ -193,9 +200,10 @@ Samba LMB. It works ONLY if the Samba server that has this option is simultaneously the LMB on it's network segment.

    The syntax of the "remote browse sync" parameter is: + 

    	remote browse sync = a.b.c.d
    remote browse sync = a.b.c.d where a.b.c.d is either the IP address of the remote LMB or else is the network broadcast address of the remote segment.

    3.4. Use of WINS

    2.4. Use of WINS

    Use of WINS (either Samba WINS _or_ MS Windows NT Server WINS) is highly recommended. Every NetBIOS machine registers it's name together with a @@ -265,7 +275,9 @@ CLASS="SECT1" >

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

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

    A very common cause of browsing problems results from installing more than one protocol on an MS Windows machine.

    3.6. Name Resolution Order

    2.6. Name Resolution Order

    Resolution of NetBIOS names to IP addresses can take place using a number of methods. The only ones that can provide NetBIOS name_type information -are: -

    14.2.1. Creating [print$]

    13.2.1. Creating [print$]

    In order to support the uploading of printer driver files, you must first configure a file share named [print$]. @@ -10590,7 +10990,7 @@ WIDTH="25" ALIGN="CENTER" VALIGN="TOP" >Note

    		Warning

    14.2.2. Setting Drivers for Existing Printers

    13.2.2. Setting Drivers for Existing Printers

    The initial listing of printers in the Samba host's Printers folder will have no real printer driver assigned @@ -10804,9 +11204,9 @@ CLASS="SECT2" >

    14.2.3. Support a large number of printers

    13.2.3. Support a large number of printers

    One issue that has arisen during the development phase of Samba 2.2 is the need to support driver downloads for @@ -10870,9 +11270,9 @@ CLASS="SECT2" >

    14.2.4. Adding New Printers via the Windows NT APW

    13.2.4. Adding New Printers via the Windows NT APW

    By default, Samba offers all printer shares defined in

    14.2.5. Samba and Printer Ports

    13.2.5. Samba and Printer Ports

    Windows NT/2000 print servers associate a port with each printer. These normally take the form of LPT1:, COM1:, FILE:, etc... Samba must also support the @@ -11076,9 +11476,9 @@ CLASS="SECT1" >

    14.3. The Imprints Toolset

    13.3. The Imprints Toolset

    The Imprints tool set provides a UNIX equivalent of the Windows NT Add Printer Wizard. For complete information, please @@ -11094,9 +11494,9 @@ CLASS="SECT2" >

    14.3.1. What is Imprints?

    13.3.1. What is Imprints?

    Imprints is a collection of tools for supporting the goals of

    14.3.2. Creating Printer Driver Packages

    13.3.2. Creating Printer Driver Packages

    The process of creating printer driver packages is beyond the scope of this document (refer to Imprints.txt also included @@ -11142,9 +11542,9 @@ CLASS="SECT2" >

    14.3.3. The Imprints server

    13.3.3. The Imprints server

    The Imprints server is really a database server that may be queried via standard HTTP mechanisms. Each printer @@ -11166,9 +11566,9 @@ CLASS="SECT2" >

    14.3.4. The Installation Client

    13.3.4. The Installation Client

    More information regarding the Imprints installation client is available in the

    14.4. Diagnosis

    13.4. Diagnosis

    14.4.1. Introduction

    13.4.1. Introduction

    This is a short description of how to debug printing problems with Samba. This describes how to debug problems with printing from a SMB @@ -11343,9 +11743,9 @@ CLASS="SECT2" >

    14.4.2. Debugging printer problems

    13.4.2. Debugging printer problems

    One way to debug printing problems is to start by replacing these command with shell scripts that record the arguments and the contents @@ -11361,7 +11761,7 @@ CLASS="PROGRAMLISTING" /usr/bin/id -p >/tmp/tmp.print # we run the command and save the error messages # replace the command with the one appropriate for your system - /usr/bin/lpr -r -P$1 $2 2>>&/tmp/tmp.print

    Then you print a file and try removing it. You may find that the @@ -11400,9 +11800,9 @@ CLASS="SECT2" >

    14.4.3. What printers do I have?

    13.4.3. What printers do I have?

    You can use the 'testprns' program to check to see if the printer name you are using is recognized by Samba. For example, you can @@ -11429,9 +11829,9 @@ CLASS="SECT2" >

    14.4.4. Setting up printcap and print servers

    13.4.4. Setting up printcap and print servers

    You may need to set up some printcaps for your Samba system to use. It is strongly recommended that you use the facilities provided by @@ -11513,9 +11913,9 @@ CLASS="SECT2" >

    14.4.5. Job sent, no output

    13.4.5. Job sent, no output

    This is the most frustrating part of printing. You may have sent the job, verified that the job was forwarded, set up a wrapper around @@ -11558,9 +11958,9 @@ CLASS="SECT2" >

    14.4.6. Job sent, strange output

    13.4.6. Job sent, strange output

    Once you have the job printing, you can then start worrying about making it print nicely.

    14.4.7. Raw PostScript printed

    13.4.7. Raw PostScript printed

    This is a problem that is usually caused by either the print spooling system putting information at the start of the print job that makes @@ -11619,9 +12019,9 @@ CLASS="SECT2" >

    14.4.8. Advanced Printing

    13.4.8. Advanced Printing

    Note that you can do some pretty magic things by using your imagination with the "print command" option and some shell scripts. @@ -11635,9 +12035,9 @@ CLASS="SECT2" >

    14.4.9. Real debugging

    13.4.9. Real debugging

    If the above debug tips don't help, then maybe you need to bring in the bug guns, system tracing. See Tracing.txt in this directory.

    Chapter 15. Security levels

    15.1. Introduction

    Samba supports the following options to the global smb.conf parameter

    [global]
-security = [share|user(default)|server|domain|ads]

    Please refer to the smb.conf man page for usage information and to the document -DOMAIN_MEMBER.html for further background details -on domain mode security. The Windows 2000 Kerberos domain security model -(security = ads) is described in the ADS-HOWTO.html.

    Of the above, "security = server" means that Samba reports to clients that -it is running in "user mode" but actually passes off all authentication -requests to another "user mode" server. This requires an additional -parameter "password server =" that points to the real authentication server. -That real authentication server can be another Samba server or can be a -Windows NT server, the later natively capable of encrypted password support.

    15.2. More complete description of security levels

    A SMB server tells the client at startup what "security level" it is -running. There are two options "share level" and "user level". Which -of these two the client receives affects the way the client then tries -to authenticate itself. It does not directly affect (to any great -extent) the way the Samba server does security. I know this is -strange, but it fits in with the client/server approach of SMB. In SMB -everything is initiated and controlled by the client, and the server -can only tell the client what is available and whether an action is -allowed.

    I'll describe user level security first, as its simpler. In user level -security the client will send a "session setup" command directly after -the protocol negotiation. This contains a username and password. The -server can either accept or reject that username/password -combination. Note that at this stage the server has no idea what -share the client will eventually try to connect to, so it can't base -the "accept/reject" on anything other than:

    1. the username/password

    2. the machine that the client is coming from

    If the server accepts the username/password then the client expects to -be able to mount any share (using a "tree connection") without -specifying a password. It expects that all access rights will be as -the username/password specified in the "session setup".

    It is also possible for a client to send multiple "session setup" -requests. When the server responds it gives the client a "uid" to use -as an authentication tag for that username/password. The client can -maintain multiple authentication contexts in this way (WinDD is an -example of an application that does this)

    Ok, now for share level security. In share level security the client -authenticates itself separately for each share. It will send a -password along with each "tree connection" (share mount). It does not -explicitly send a username with this operation. The client is -expecting a password to be associated with each share, independent of -the user. This means that samba has to work out what username the -client probably wants to use. It is never explicitly sent the -username. Some commercial SMB servers such as NT actually associate -passwords directly with shares in share level security, but samba -always uses the unix authentication scheme where it is a -username/password that is authenticated, not a "share/password".

    Many clients send a "session setup" even if the server is in share -level security. They normally send a valid username but no -password. Samba records this username in a list of "possible -usernames". When the client then does a "tree connection" it also adds -to this list the name of the share they try to connect to (useful for -home directories) and any users listed in the "user =" smb.conf -line. The password is then checked in turn against these "possible -usernames". If a match is found then the client is authenticated as -that user.

    Finally "server level" security. In server level security the samba -server reports to the client that it is in user level security. The -client then does a "session setup" as described earlier. The samba -server takes the username/password that the client sends and attempts -to login to the "password server" by sending exactly the same -username/password that it got from the client. If that server is in -user level security and accepts the password then samba accepts the -clients connection. This allows the samba server to use another SMB -server as the "password server".

    You should also note that at the very start of all this, where the -server tells the client what security level it is in, it also tells -the client if it supports encryption. If it does then it supplies the -client with a random "cryptkey". The client will then send all -passwords in encrypted form. You have to compile samba with encryption -enabled to support this feature, and you have to maintain a separate -smbpasswd file with SMB style encrypted passwords. It is -cryptographically impossible to translate from unix style encryption -to SMB style encryption, although there are some fairly simple management -schemes by which the two could be kept in sync.

    Chapter 16. Unified Logons between Windows NT and UNIX using Winbind

    Chapter 14. Unified Logons between Windows NT and UNIX using Winbind

    16.1. Abstract

    14.1. Abstract

    Integration of UNIX and Microsoft Windows NT through a unified logon has been considered a "holy grail" in heterogeneous @@ -11831,9 +12083,9 @@ CLASS="SECT1" >

    16.2. Introduction

    14.2. Introduction

    It is well known that UNIX and Microsoft Windows NT have different models for representing user and group information and @@ -11885,9 +12137,9 @@ CLASS="SECT1" >

    16.3. What Winbind Provides

    14.3. What Winbind Provides

    Winbind unifies UNIX and Windows NT account management by allowing a UNIX box to become a full member of a NT domain. Once @@ -11927,9 +12179,9 @@ CLASS="SECT2" >

    16.3.1. Target Uses

    14.3.1. Target Uses

    Winbind is targeted at organizations that have an existing NT based domain infrastructure into which they wish @@ -11951,9 +12203,9 @@ CLASS="SECT1" >

    16.4. How Winbind Works

    14.4. How Winbind Works

    The winbind system is designed around a client/server architecture. A long running

    16.4.1. Microsoft Remote Procedure Calls

    14.4.1. Microsoft Remote Procedure Calls

    Over the last two years, efforts have been underway +>Over the last few years, efforts have been underway by various Samba Team members to decode various aspects of the Microsoft Remote Procedure Call (MSRPC) system. This system is used for most network related operations between @@ -11997,9 +12249,28 @@ CLASS="SECT2" >

    14.4.2. Microsoft Active Directory Services

    Since late 2001, Samba has gained the ability to + interact with Microsoft Windows 2000 using its 'Native + Mode' protocols, rather than the NT4 RPC services. + Using LDAP and Kerberos, a domain member running + winbind can enumerate users and groups in exactly the + same way as a Win2k client would, and in so doing + provide a much more efficient and + effective winbind implementation. +

    16.4.2. Name Service Switch

    14.4.3. Name Service Switch

    The Name Service Switch, or NSS, is a feature that is present in many UNIX operating systems. It allows system @@ -12077,9 +12348,9 @@ CLASS="SECT2" >

    16.4.3. Pluggable Authentication Modules

    14.4.4. Pluggable Authentication Modules

    Pluggable Authentication Modules, also known as PAM, is a system for abstracting authentication and authorization @@ -12126,9 +12397,9 @@ CLASS="SECT2" >

    16.4.4. User and Group ID Allocation

    14.4.5. User and Group ID Allocation

    When a user or group is created under Windows NT is it allocated a numerical relative identifier (RID). This is @@ -12152,9 +12423,9 @@ CLASS="SECT2" >

    16.4.5. Result Caching

    14.4.6. Result Caching

    An active system can generate a lot of user and group name lookups. To reduce the network cost of these lookups winbind @@ -12175,9 +12446,9 @@ CLASS="SECT1" >

    16.5. Installation and Configuration

    14.5. Installation and Configuration

    Many thanks to John Trostel

    16.5.1. Introduction

    14.5.1. Introduction

    This HOWTO describes the procedures used to get winbind up and running on my RedHat 7.1 system. Winbind is capable of providing access @@ -12261,9 +12532,9 @@ CLASS="SECT2" >

    16.5.2. Requirements

    14.5.2. Requirements

    If you have a samba configuration file that you are currently using...

    16.5.3. Testing Things Out

    14.5.3. Testing Things Out

    Before starting, it is probably best to kill off all the SAMBA related daemons running on your server. Kill off all

    16.5.3.1. Configure and compile SAMBA

    14.5.3.1. Configure and compile SAMBA

    The configuration and compilation of SAMBA is pretty straightforward. The first three steps may not be necessary depending upon @@ -12412,7 +12683,7 @@ CLASS="PROMPT" >root# ./configure --with-winbind./configure

    16.5.3.2. Configure 14.5.3.2. Configure nsswitch.conf and the @@ -12547,9 +12818,9 @@ CLASS="SECT3" >

    16.5.3.3. Configure smb.conf

    14.5.3.3. Configure smb.conf

    Several parameters are needed in the smb.conf file to control the behavior of 

    [global]
-     <...>
+     <...>
      # separate domain and username with '+', like DOMAIN+username
      
    16.5.3.4. Join the SAMBA server to the PDC domain
    14.5.3.4. Join the SAMBA server to the PDC domain
    Enter the following command to make the SAMBA server join the 
 PDC domain, where root# /usr/local/samba/bin/net rpc join -S PDC -U Administrator/usr/local/samba/bin/net join -S PDC -U Administrator
    The proper response to the command should be: "Joined the domain 
@@ -12668,9 +12939,9 @@ CLASS="SECT3"
 >
    16.5.3.5. Start up the winbindd daemon and test it!
    14.5.3.5. Start up the winbindd daemon and test it!
    Eventually, you will want to modify your smb startup script to 
 automatically invoke the winbindd daemon when the other parts of 
@@ -12791,17 +13062,17 @@ CLASS="SECT3"
 >
    16.5.3.6. Fix the init.d startup scripts
    14.5.3.6. Fix the init.d startup scripts
    16.5.3.6.1. Linux
    14.5.3.6.1. Linux
    The 
    16.5.3.6.2. Solaris
    14.5.3.6.2. Solaris
    On solaris, you need to modify the 
 
    16.5.3.6.3. Restarting
    14.5.3.6.3. Restarting
    If you restart the 
    16.5.3.7. Configure Winbind and PAM
    14.5.3.7. Configure Winbind and PAM
    If you have made it this far, you know that winbindd and samba are working
 together.  If you want to use winbind to provide authentication for other 
@@ -13048,9 +13319,9 @@ CLASS="SECT4"
 >
    16.5.3.7.1. Linux/FreeBSD-specific PAM configuration
    14.5.3.7.1. Linux/FreeBSD-specific PAM configuration
    The 
    16.5.3.7.2. Solaris-specific configuration
    14.5.3.7.2. Solaris-specific configuration
    The /etc/pam.conf needs to be changed. I changed this file so that my Domain
 users can logon both locally as well as telnet.The following are the changes
@@ -13253,7 +13524,7 @@ dtsession auth required	/usr/lib/security/$ISA/pam_unix.so.1
 >I also added a try_first_pass line after the winbind.so line to get rid of
 annoying double prompts for passwords.
    Now restart your Samba & try connecting through your application that you
+>Now restart your Samba and try connecting through your application that you
 configured in the pam.conf.

    16.6. Limitations

    14.6. Limitations

    Winbind has a number of limitations in its current released version that we hope to overcome in future @@ -13277,7 +13548,7 @@ NAME="AEN2566" >

  • Winbind is currently only available for - the Linux operating system, although ports to other operating + the Linux, Solaris and IRIX operating systems, although ports to other operating systems are certainly possible. For such ports to be feasible, we require the C library of the target operating system to support the Name Service Switch and Pluggable Authentication @@ -13286,1116 +13557,1027 @@ NAME="AEN2566" >

  • The mappings of Windows NT RIDs to UNIX ids - is not made algorithmically and depends on the order in which - unmapped users or groups are seen by winbind. It may be difficult - to recover the mappings of rid to UNIX id mapping if the file - containing this information is corrupted or destroyed.

  • The mappings of Windows NT RIDs to UNIX ids + is not made algorithmically and depends on the order in which + unmapped users or groups are seen by winbind. It may be difficult + to recover the mappings of rid to UNIX id mapping if the file + containing this information is corrupted or destroyed.

  • Currently the winbind PAM module does not take + into account possible workstation and logon time restrictions + that may be been set for Windows NT users, this is + instead up to the PDC to enforce.

    • 14.7. Conclusion

    The winbind system, through the use of the Name Service + Switch, Pluggable Authentication Modules, and appropriate + Microsoft RPC calls have allowed us to provide seamless + integration of Microsoft Windows NT domain users on a + UNIX system. The result is a great reduction in the administrative + cost of running a mixed UNIX and NT network.

    Chapter 15. Improved browsing in samba

    15.1. Overview of browsing

    SMB networking provides a mechanism by which clients can access a list +of machines in a network, a so-called "browse list". This list +contains machines that are ready to offer file and/or print services +to other machines within the network. Thus it does not include +machines which aren't currently able to do server tasks. The browse +list is heavily used by all SMB clients. Configuration of SMB +browsing has been problematic for some Samba users, hence this +document.

    Browsing will NOT work if name resolution from NetBIOS names to IP +addresses does not function correctly. Use of a WINS server is highly +recommended to aid the resolution of NetBIOS (SMB) names to IP addresses. +WINS allows remote segment clients to obtain NetBIOS name_type information +that can NOT be provided by any other means of name resolution.

    15.2. Browsing support in samba

    Samba now fully supports browsing. The browsing is supported by nmbd +and is also controlled by options in the smb.conf file (see smb.conf(5)).

    Samba can act as a local browse master for a workgroup and the ability +for samba to support domain logons and scripts is now available. See +DOMAIN.txt for more information on domain logons.

    Samba can also act as a domain master browser for a workgroup. This +means that it will collate lists from local browse masters into a +wide area network server list. In order for browse clients to +resolve the names they may find in this list, it is recommended that +both samba and your clients use a WINS server.

    Note that you should NOT set Samba to be the domain master for a +workgroup that has the same name as an NT Domain: on each wide area +network, you must only ever have one domain master browser per workgroup, +regardless of whether it is NT, Samba or any other type of domain master +that is providing this service.

    [Note that nmbd can be configured as a WINS server, but it is not +necessary to specifically use samba as your WINS server. NTAS can +be configured as your WINS server. In a mixed NT server and +samba environment on a Wide Area Network, it is recommended that +you use the NT server's WINS server capabilities. In a samba-only +environment, it is recommended that you use one and only one nmbd +as your WINS server].

    To get browsing to work you need to run nmbd as usual, but will need +to use the "workgroup" option in smb.conf to control what workgroup +Samba becomes a part of.

    Currently the winbind PAM module does not take - into account possible workstation and logon time restrictions - that may be been set for Windows NT users.

    Samba also has a useful option for a Samba server to offer itself for +browsing on another subnet. It is recommended that this option is only +used for 'unusual' purposes: announcements over the internet, for +example. See "remote announce" in the smb.conf man page.

    16.7. Conclusion

    15.3. Problem resolution

    The winbind system, through the use of the Name Service - Switch, Pluggable Authentication Modules, and appropriate - Microsoft RPC calls have allowed us to provide seamless - integration of Microsoft Windows NT domain users on a - UNIX system. The result is a great reduction in the administrative - cost of running a mixed UNIX and NT network.

    If something doesn't work then hopefully the log.nmb file will help +you track down the problem. Try a debug level of 2 or 3 for finding +problems. Also note that the current browse list usually gets stored +in text form in a file called browse.dat.

    Note that if it doesn't work for you, then you should still be able to +type the server name as \\SERVER in filemanager then hit enter and +filemanager should display the list of available shares.

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

    Also, a lot of people are getting bitten by the problem of too many +parameters on the command line of nmbd in inetd.conf. This trick is to +not use spaces between the option and the parameter (eg: -d2 instead +of -d 2), and to not use the -B and -N options. New versions of nmbd +are now far more likely to correctly find your broadcast and network +address, so in most cases these aren't needed.

    The other big problem people have is that their broadcast address, +netmask or IP address is wrong (specified with the "interfaces" option +in smb.conf)

    Chapter 17. Passdb MySQL plugin

    17.1. Building

    15.4. Browsing across subnets

    To build the plugin, run make bin/pdb_mysql.so -in the source/ directory of samba distribution.

    With the release of Samba 1.9.17(alpha1 and above) Samba has been +updated to enable it to support the replication of browse lists +across subnet boundaries. New code and options have been added to +achieve this. This section describes how to set this feature up +in different settings.

    Next, copy pdb_mysql.so to any location you want. I -strongly recommend installing it in $PREFIX/lib or /usr/lib/samba/

    To see browse lists that span TCP/IP subnets (ie. networks separated +by routers that don't pass broadcast traffic) you must set up at least +one WINS server. The WINS server acts as a DNS for NetBIOS names, allowing +NetBIOS name to IP address translation to be done by doing a direct +query of the WINS server. This is done via a directed UDP packet on +port 137 to the WINS server machine. The reason for a WINS server is +that by default, all NetBIOS name to IP address translation is done +by broadcasts from the querying machine. This means that machines +on one subnet will not be able to resolve the names of machines on +another subnet without using a WINS server.

    Remember, for browsing across subnets to work correctly, all machines, +be they Windows 95, Windows NT, or Samba servers must have the IP address +of a WINS server given to them by a DHCP server, or by manual configuration +(for Win95 and WinNT, this is in the TCP/IP Properties, under Network +settings) for Samba this is in the smb.conf file.

    17.2. Configuring

    15.4.1. How does cross subnet browsing work ?

    This plugin lacks some good documentation, but here is some short info:

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

    Add a the following to the passdb backend variable in your smb.conf: -

    Consider a network set up as follows :
    passdb backend = [other-plugins] plugin:/location/to/pdb_mysql.so:identifier [other-plugins]
                                       (DMB)
+             N1_A      N1_B        N1_C       N1_D        N1_E
+              |          |           |          |           |
+          -------------------------------------------------------
+            |          subnet 1                       |
+          +---+                                      +---+
+          |R1 | Router 1                  Router 2   |R2 |
+          +---+                                      +---+
+            |                                          |
+            |  subnet 2              subnet 3          |
+  --------------------------       ------------------------------------
+  |     |     |      |               |        |         |           |
+ N2_A  N2_B  N2_C   N2_D           N3_A     N3_B      N3_C        N3_D 
+                    (WINS)

    The identifier can be any string you like, as long as it doesn't collide with -the identifiers of other plugins or other instances of pdb_mysql. If you -specify multiple pdb_mysql.so entries in 'passdb backend', you also need to -use different identifiers!

    Consisting of 3 subnets (1, 2, 3) connected by two routers +(R1, R2) - these do not pass broadcasts. Subnet 1 has 5 machines +on it, subnet 2 has 4 machines, subnet 3 has 4 machines. Assume +for the moment that all these machines are configured to be in the +same workgroup (for simplicities sake). Machine N1_C on subnet 1 +is configured as Domain Master Browser (ie. it will collate the +browse lists for the workgroup). Machine N2_D is configured as +WINS server and all the other machines are configured to register +their NetBIOS names with it.

    As all these machines are booted up, elections for master browsers +will take place on each of the three subnets. Assume that machine +N1_C wins on subnet 1, N2_B wins on subnet 2, and N3_D wins on +subnet 3 - these machines are known as local master browsers for +their particular subnet. N1_C has an advantage in winning as the +local master browser on subnet 1 as it is set up as Domain Master +Browser.

    On each of the three networks, machines that are configured to +offer sharing services will broadcast that they are offering +these services. The local master browser on each subnet will +receive these broadcasts and keep a record of the fact that +the machine is offering a service. This list of records is +the basis of the browse list. For this case, assume that +all the machines are configured to offer services so all machines +will be on the browse list.

    For each network, the local master browser on that network is +considered 'authoritative' for all the names it receives via +local broadcast. This is because a machine seen by the local +master browser via a local broadcast must be on the same +network as the local master browser and thus is a 'trusted' +and 'verifiable' resource. Machines on other networks that +the local master browsers learn about when collating their +browse lists have not been directly seen - these records are +called 'non-authoritative'.

    At this point the browse lists look as follows (these are +the machines you would see in your network neighborhood if +you looked in it on a particular network right now).

    Subnet           Browse Master   List
+------           -------------   ----
+Subnet1          N1_C            N1_A, N1_B, N1_C, N1_D, N1_E
+
+Subnet2          N2_B            N2_A, N2_B, N2_C, N2_D
+
+Subnet3          N3_D            N3_A, N3_B, N3_C, N3_D

    Note that at this point all the subnets are separate, no +machine is seen across any of the subnets.

    Now examine subnet 2. As soon as N2_B has become the local +master browser it looks for a Domain master browser to synchronize +its browse list with. It does this by querying the WINS server +(N2_D) for the IP address associated with the NetBIOS name +WORKGROUP>1B<. This name was registerd by the Domain master +browser (N1_C) with the WINS server as soon as it was booted.

    Once N2_B knows the address of the Domain master browser it +tells it that is the local master browser for subnet 2 by +sending a MasterAnnouncement packet as a UDP port 138 packet. +It then synchronizes with it by doing a NetServerEnum2 call. This +tells the Domain Master Browser to send it all the server +names it knows about. Once the domain master browser receives +the MasterAnnouncement packet it schedules a synchronization +request to the sender of that packet. After both synchronizations +are done the browse lists look like :

    Subnet           Browse Master   List
+------           -------------   ----
+Subnet1          N1_C            N1_A, N1_B, N1_C, N1_D, N1_E, 
+                                 N2_A(*), N2_B(*), N2_C(*), N2_D(*)
+
+Subnet2          N2_B            N2_A, N2_B, N2_C, N2_D
+                                 N1_A(*), N1_B(*), N1_C(*), N1_D(*), N1_E(*)
+
+Subnet3          N3_D            N3_A, N3_B, N3_C, N3_D
+
+Servers with a (*) after them are non-authoritative names.

    At this point users looking in their network neighborhood on +subnets 1 or 2 will see all the servers on both, users on +subnet 3 will still only see the servers on their own subnet.

    The same sequence of events that occured for N2_B now occurs +for the local master browser on subnet 3 (N3_D). When it +synchronizes browse lists with the domain master browser (N1_A) +it gets both the server entries on subnet 1, and those on +subnet 2. After N3_D has synchronized with N1_C and vica-versa +the browse lists look like.

    Subnet           Browse Master   List
+------           -------------   ----
+Subnet1          N1_C            N1_A, N1_B, N1_C, N1_D, N1_E, 
+                                 N2_A(*), N2_B(*), N2_C(*), N2_D(*),
+                                 N3_A(*), N3_B(*), N3_C(*), N3_D(*)
+
+Subnet2          N2_B            N2_A, N2_B, N2_C, N2_D
+                                 N1_A(*), N1_B(*), N1_C(*), N1_D(*), N1_E(*)
+
+Subnet3          N3_D            N3_A, N3_B, N3_C, N3_D
+                                 N1_A(*), N1_B(*), N1_C(*), N1_D(*), N1_E(*),
+                                 N2_A(*), N2_B(*), N2_C(*), N2_D(*)
+
+Servers with a (*) after them are non-authoritative names.

    At this point users looking in their network neighborhood on +subnets 1 or 3 will see all the servers on all sunbets, users on +subnet 2 will still only see the servers on subnets 1 and 2, but not 3.

    Additional options can be given thru the smb.conf file in the [global] section.

    Finally, the local master browser for subnet 2 (N2_B) will sync again +with the domain master browser (N1_C) and will recieve the missing +server entries. Finally - and as a steady state (if no machines +are removed or shut off) the browse lists will look like :

    identifier:mysql host                     - host name, defaults to 'localhost'
-identifier:mysql password
-identifier:mysql user                     - defaults to 'samba'
-identifier:mysql database                 - defaults to 'samba'
-identifier:mysql port                     - defaults to 3306
-identifier:table                          - Name of the table containing users
    Subnet Browse Master List +------ ------------- ---- +Subnet1 N1_C N1_A, N1_B, N1_C, N1_D, N1_E, + N2_A(*), N2_B(*), N2_C(*), N2_D(*), + N3_A(*), N3_B(*), N3_C(*), N3_D(*) + +Subnet2 N2_B N2_A, N2_B, N2_C, N2_D + N1_A(*), N1_B(*), N1_C(*), N1_D(*), N1_E(*) + N3_A(*), N3_B(*), N3_C(*), N3_D(*) + +Subnet3 N3_D N3_A, N3_B, N3_C, N3_D + N1_A(*), N1_B(*), N1_C(*), N1_D(*), N1_E(*), + N2_A(*), N2_B(*), N2_C(*), N2_D(*) + +Servers with a (*) after them are non-authoritative names.

    Names of the columns in this table(I've added column types those columns should have first):

    Synchronizations between the domain master browser and local +master browsers will continue to occur, but this should be a +steady state situation.

    identifier:logon time column             - int(9)
-identifier:logoff time column            - int(9)
-identifier:kickoff time column           - int(9)
-identifier:pass last set time column     - int(9)
-identifier:pass can change time column   - int(9)
-identifier:pass must change time column  - int(9)
-identifier:username column               - varchar(255) - unix username
-identifier:domain column                 - varchar(255) - NT domain user is part of
-identifier:nt username column            - varchar(255) - NT username
-identifier:fullname column            - varchar(255) - Full name of user
-identifier:home dir column               - varchar(255) - Unix homedir path
-identifier:dir drive column              - varchar(2) - Directory drive path (eg: 'H:')
-identifier:logon script column           - varchar(255) - Batch file to run on client side when logging on
-identifier:profile path column           - varchar(255) - Path of profile
-identifier:acct desc column              - varchar(255) - Some ASCII NT user data
-identifier:workstations column           - varchar(255) - Workstations user can logon to (or NULL for all)
-identifier:unknown string column         - varchar(255) - unknown string
-identifier:munged dial column            - varchar(255) - ?
-identifier:uid column                    - int(9) - Unix user ID (uid)
-identifier:gid column                    - int(9) - Unix user group (gid)
-identifier:user sid column               - varchar(255) - NT user SID
-identifier:group sid column              - varchar(255) - NT group ID
-identifier:lanman pass column            - varchar(255) - encrypted lanman password
-identifier:nt pass column                - varchar(255) - encrypted nt passwd
-identifier:plaintext pass column         - varchar(255) - plaintext password
-identifier:acct control column           - int(9) - nt user data
-identifier:unknown 3 column              - int(9) - unknown
-identifier:logon divs column             - int(9) - ?
-identifier:hours len column              - int(9) - ?
-identifier:unknown 5 column              - int(9) - unknown
-identifier:unknown 6 column              - int(9) - unknown

    If either router R1 or R2 fails the following will occur:

    Eventually, you can put a colon (:) after the name of each column, which -should specify the column to update when updating the table. You can also -specify nothing behind the colon - then the data from the field will not be -updated.

    17.3. Using plaintext passwords or encrypted password

    1. I strongly discourage the use of plaintext passwords, however, you can use them:

      Names of computers on each side of the inaccessible network fragments + will be maintained for as long as 36 minutes, in the network neighbourhood + lists. +

    2. If you would like to use plaintext passwords, set 'identifier:lanman pass column' and 'identifier:nt pass column' to 'NULL' (without the quotes) and 'identifier:plaintext pass column' to the name of the column containing the plaintext passwords.

      Attempts to connect to these inaccessible computers will fail, but the + names will not be removed from the network neighbourhood lists. +

    3. If you use encrypted passwords, set the 'identifier:plaintext pass column' to 'NULL' (without the quotes). This is the default.

      If one of the fragments is cut off from the WINS server, it will only + be able to access servers on its local subnet, by using subnet-isolated + broadcast NetBIOS name resolution. The effects are similar to that of + losing access to a DNS server. +

    17.4. Getting non-column data from the table

    It is possible to have not all data in the database and making some 'constant'.

    15.5. Setting up a WINS server

    For example, you can set 'identifier:fullname column' to : -CONCAT(First_name,' ',Sur_name)

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

    Or, set 'identifier:workstations column' to : -NULL wins support = yes

    See the MySQL documentation for more language constructs.

    Chapter 18. Passdb XML plugin

    18.1. Building

    This module requires libxml2 to be installed.

    To build pdb_xml, run: make bin/pdb_xml.so in -the directory source/.

    18.2. Usage

    Versions of Samba previous to 1.9.17 had this parameter default to +yes. If you have any older versions of Samba on your network it is +strongly suggested you upgrade to 1.9.17 or above, or at the very +least set the parameter to 'no' on all these machines.

    The usage of pdb_xml is pretty straightforward. To export data, use: - -Machines with "pdbedit -e plugin:/usr/lib/samba/pdb_xml.so:filename - -(where filename is the name of the file to put the data in)

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

    To import data, use: -You should set up only ONE wins server. Do NOT set the +"pdbedit -i plugin:/usr/lib/samba/pdb_xml.so:filename -e current-pdb - -Where filename is the name to read the data from and current-pdb to put it in.

    Chapter 19. Storing Samba's User/Machine Account information in an LDAP Directory

    19.1. Purpose

    This document describes how to use an LDAP directory for storing Samba user -account information traditionally stored in the smbpasswd(5) file. It is -assumed that the reader already has a basic understanding of LDAP concepts -and has a working directory server already installed. For more information -on LDAP architectures and Directories, please refer to the following sites.

    wins support = yes" option on more than one Samba +server.

    • To set up a Windows NT Server as a WINS server you need to set up +the WINS service - see your NT documentation for details. Note that +Windows NT WINS Servers can replicate to each other, allowing more +than one to be set up in a complex subnet environment. As Microsoft +refuse to document these replication protocols Samba cannot currently +participate in these replications. It is possible in the future that +a Samba->Samba WINS replication protocol may be defined, in which +case more than one Samba machine could be set up as a WINS server +but currently only one Samba server should have the "wins support = yes" +parameter set.

      OpenLDAP - http://www.openldap.org/

    • After the WINS server has been configured you must ensure that all +machines participating on the network are configured with the address +of this WINS server. If your WINS server is a Samba machine, fill in +the Samba machine IP address in the "Primary WINS Server" field of +the "Control Panel->Network->Protocols->TCP->WINS Server" dialogs +in Windows 95 or Windows NT. To tell a Samba server the IP address +of the WINS server add the following line to the [global] section of +all smb.conf files :

      iPlanet Directory Server - http://iplanet.netscape.com/directorywins server = >name or IP address<

    Note that O'Reilly Publishing is working on -a guide to LDAP for System Administrators which has a planned release date of -early summer, 2002.

    Two additional Samba resources which may prove to be helpful are

    • where >name or IP address< is either the DNS name of the WINS server +machine or its IP address.

      The Samba-PDC-LDAP-HOWTO - maintained by Ignacio Coupeau.

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

      The NT migration scripts from IDEALX that are - geared to manage users and group in such a Samba-LDAP Domain Controller configuration. -

    There are two possible scenarios for setting up cross subnet browsing. +The first details setting up cross subnet browsing on a network containing +Windows 95, Samba and Windows NT machines that are not configured as +part of a Windows NT Domain. The second details setting up cross subnet +browsing on networks that contain NT Domains.

    19.2. Introduction

    Traditionally, when configuring "encrypt -passwords = yes" in Samba's smb.conf file, user account -information such as username, LM/NT password hashes, password change times, and account -flags have been stored in the smbpasswd(5) file. There are several -disadvantages to this approach for sites with very large numbers of users (counted -in the thousands).

    15.6. Setting up Browsing in a WORKGROUP

    • To set up cross subnet browsing on a network containing machines +in up to be in a WORKGROUP, not an NT Domain you need to set up one +Samba server to be the Domain Master Browser (note that this is *NOT* +the same as a Primary Domain Controller, although in an NT Domain the +same machine plays both roles). The role of a Domain master browser is +to collate the browse lists from local master browsers on all the +subnets that have a machine participating in the workgroup. Without +one machine configured as a domain master browser each subnet would +be an isolated workgroup, unable to see any machines on any other +subnet. It is the presense of a domain master browser that makes +cross subnet browsing possible for a workgroup.

      The first is that all lookups must be performed sequentially. Given that -there are approximately two lookups per domain logon (one for a normal -session connection such as when mapping a network drive or printer), this -is a performance bottleneck for lareg sites. What is needed is an indexed approach -such as is used in databases.

    • In an WORKGROUP environment the domain master browser must be a +Samba server, and there must only be one domain master browser per +workgroup name. To set up a Samba server as a domain master browser, +set the following option in the [global] section of the smb.conf file :

      The second problem is that administrators who desired to replicate a -smbpasswd file to more than one Samba server were left to use external -tools such as rsync(1) and ssh(1) -and wrote custom, in-house scripts.

    • domain master = yes

      And finally, the amount of information which is stored in an -smbpasswd entry leaves no room for additional attributes such as -a home directory, password expiration time, or even a Relative -Identified (RID).

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

    As a result of these defeciencies, a more robust means of storing user attributes -used by smbd was developed. The API which defines access to user accounts -is commonly referred to as the samdb interface (previously this was called the passdb -API, and is still so named in the CVS trees). In Samba 2.2.3, enabling support -for a samdb backend (e.g. --with-ldapsam or ---with-tdbsam) requires compile time support.

            domain master = yes
+        local master = yes
+        preferred master = yes
+        os level = 65

    When compiling Samba to include the --with-ldapsam autoconf -option, smbd (and associated tools) will store and lookup user accounts in -an LDAP directory. In reality, this is very easy to understand. If you are -comfortable with using an smbpasswd file, simply replace "smbpasswd" with -"LDAP directory" in all the documentation.

    The domain master browser may be the same machine as the WINS +server, if you require.

    There are a few points to stress about what the --with-ldapsam -does not provide. The LDAP support referred to in the this documentation does not -include:

    Next, you should ensure that each of the subnets contains a +machine that can act as a local master browser for the +workgroup. Any NT machine should be able to do this, as will +Windows 95 machines (although these tend to get rebooted more +often, so it's not such a good idea to use these). To make a +Samba server a local master browser set the following +options in the [global] section of the smb.conf file :

            domain master = no
+        local master = yes
+        preferred master = yes
+        os level = 65

    • A means of retrieving user account information from - an Windows 2000 Active Directory server.

    • Do not do this for more than one Samba server on each subnet, +or they will war with each other over which is to be the local +master browser.

      A means of replacing /etc/passwd.

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

    The second item can be accomplished by using LDAP NSS and PAM modules. LGPL -versions of these libraries can be obtained from PADL Software -(http://www.padl.com/). However, -the details of configuring these packages are beyond the scope of this document.

    19.3. Supported LDAP Servers

    If you have an NT machine on the subnet that you wish to +be the local master browser then you can disable Samba from +becoming a local master browser by setting the following +options in the [global] section of the smb.conf file :

    The LDAP samdb code in 2.2.3 has been developed and tested using the OpenLDAP -2.0 server and client libraries. The same code should be able to work with -Netscape's Directory Server and client SDK. However, due to lack of testing -so far, there are bound to be compile errors and bugs. These should not be -hard to fix. If you are so inclined, please be sure to forward all patches to -samba-patches@samba.org and -jerry@samba.org.

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

    19.4. Schema and Relationship to the RFC 2307 posixAccount

    15.7. Setting up Browsing in a DOMAIN

    Samba 2.2.3 includes the necessary schema file for OpenLDAP 2.0 in -examples/LDAP/samba.schema. (Note that this schema -file has been modified since the experimental support initially included -in 2.2.2). The sambaAccount objectclass is given here:

    If you are adding Samba servers to a Windows NT Domain then +you must not set up a Samba server as a domain master browser. +By default, a Windows NT Primary Domain Controller for a Domain +name is also the Domain master browser for that name, and many +things will break if a Samba server registers the Domain master +browser NetBIOS name (DOMAIN>1B<) with WINS instead of the PDC.

    For subnets other than the one containing the Windows NT PDC +you may set up Samba servers as local master browsers as +described. To make a Samba server a local master browser set +the following options in the [global] section of the smb.conf +file :

    objectclass ( 1.3.1.5.1.4.1.7165.2.2.2 NAME 'sambaAccount' SUP top STRUCTURAL
-     DESC 'Samba Account'
-     MUST ( uid $ rid )
-     MAY  ( cn $ lmPassword $ ntPassword $ pwdLastSet $ logonTime $
-            logoffTime $ kickoffTime $ pwdCanChange $ pwdMustChange $ acctFlags $
-            displayName $ smbHome $ homeDrive $ scriptPath $ profilePath $
-            description $ userWorkstations $ primaryGroupID $ domain ))
    domain master = no + local master = yes + preferred master = yes + os level = 65

    The samba.schema file has been formatted for OpenLDAP 2.0. The OID's are -owned by the Samba Team and as such is legal to be openly published. -If you translate the schema to be used with Netscape DS, please -submit the modified schema file as a patch to jerry@samba.org

    If you wish to have a Samba server fight the election with machines +on the same subnet you may set the "os level" parameter to lower +levels. By doing this you can tune the order of machines that +will become local master browsers if they are running. For +more details on this see the section "FORCING SAMBA TO BE THE MASTER" +below.

    Just as the smbpasswd file is mean to store information which supplements a -user's /etc/passwd entry, so is the sambaAccount object -meant to supplement the UNIX user account information. A sambaAccount is a -STRUCTURAL objectclass so it can be stored individually -in the directory. However, there are several fields (e.g. uid) which overlap -with the posixAccount objectclass outlined in RFC2307. This is by design.

    If you have Windows NT machines that are members of the domain +on all subnets, and you are sure they will always be running then +you can disable Samba from taking part in browser elections and +ever becoming a local master browser by setting following options +in the [global] section of the smb.conf file :

    In order to store all user account information (UNIX and Samba) in the directory, -it is necessary to use the sambaAccount and posixAccount objectclasses in -combination. However, smbd will still obtain the user's UNIX account -information via the standard C library calls (e.g. getpwnam(), et. al.). -This means that the Samba server must also have the LDAP NSS library installed -and functioning correctly. This division of information makes it possible to -store all Samba account information in LDAP, but still maintain UNIX account -information in NIS while the network is transitioning to a full LDAP infrastructure.

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

    19.5. Configuring Samba with LDAP

    19.5.1. OpenLDAP configuration

    15.8. Forcing samba to be the master

    To include support for the sambaAccount object in an OpenLDAP directory -server, first copy the samba.schema file to slapd's configuration directory.

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

    root# cp samba.schema /etc/openldap/schema/

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

    Next, include the samba.schema file in slapd.conf. -The sambaAccount object contains two attributes which depend upon other schema -files. The 'uid' attribute is defined in cosine.schema and -the 'displayName' attribute is defined in the inetorgperson.schema -file. Both of these must be included before the samba.schema file.

    A "os level" of 2 would make it beat WfWg and Win95, but not NTAS. A +NTAS domain controller uses level 32.

    ## /etc/openldap/slapd.conf
-
-## schema files (core.schema is required by default)
-include	           /etc/openldap/schema/core.schema
-
-## needed for sambaAccount
-include            /etc/openldap/schema/cosine.schema
-include            /etc/openldap/schema/inetorgperson.schema
-include            /etc/openldap/schema/samba.schema
-
-## uncomment this line if you want to support the RFC2307 (NIS) schema
-## include         /etc/openldap/schema/nis.schema
-
-....

    The maximum os level is 255

    It is recommended that you maintain some indices on some of the most usefull attributes, -like in the following example, to speed up searches made on sambaAccount objectclasses -(and possibly posixAccount and posixGroup as well).

    If you want samba to force an election on startup, then set the +"preferred master" global option in smb.conf to "yes". Samba will +then have a slight advantage over other potential master browsers +that are not preferred master browsers. Use this parameter with +care, as if you have two hosts (whether they are windows 95 or NT or +samba) on the same local subnet both set with "preferred master" to +"yes", then periodically and continually they will force an election +in order to become the local master browser.

    # Indices to maintain
-## required by OpenLDAP 2.0
-index objectclass   eq
-
-## support pb_getsampwnam()
-index uid           pres,eq
-## support pdb_getsambapwrid()
-index rid           eq
-
-## uncomment these if you are storing posixAccount and
-## posixGroup entries in the directory as well
-##index uidNumber     eq
-##index gidNumber     eq
-##index cn            eq
-##index memberUid     eq

    If you want samba to be a "domain master browser", then it is +recommended that you also set "preferred master" to "yes", because +samba will not become a domain master browser for the whole of your +LAN or WAN if it is not also a local master browser on its own +broadcast isolated subnet.

    It is possible to configure two samba servers to attempt to become +the domain master browser for a domain. The first server that comes +up will be the domain master browser. All other samba servers will +attempt to become the domain master browser every 5 minutes. They +will find that another samba server is already the domain master +browser and will fail. This provides automatic redundancy, should +the current domain master browser fail.

    19.5.2. Configuring Samba

    15.9. Making samba the domain master

    The following parameters are available in smb.conf only with --with-ldapsam -was included with compiling Samba.

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

    • Note that you should NOT set Samba to be the domain master for a +workgroup that has the same name as an NT Domain.

      ldap ssl

    • When samba is the domain master and the master browser it will listen +for master announcements (made roughly every twelve minutes) from local +master browsers on other subnets and then contact them to synchronise +browse lists.

      ldap server

    • If you want samba to be the domain master then I suggest you also set +the "os level" high enough to make sure it wins elections, and set +"preferred master" to "yes", to get samba to force an election on +startup.

      ldap admin dn

    • Note that all your servers (including samba) and clients should be +using a WINS server to resolve NetBIOS names. If your clients are only +using broadcasting to resolve NetBIOS names, then two things will occur:

      ldap suffix

      1. ldap filter

        your local master browsers will be unable to find a domain master + browser, as it will only be looking on the local subnet. +

      2. ldap port

        if a client happens to get hold of a domain-wide browse list, and + a user attempts to access a host in that list, it will be unable to + resolve the NetBIOS name of that host. +

    These are described in the smb.conf(5) man -page and so will not be repeated here. However, a sample smb.conf file for -use with an LDAP directory could appear as

    If, however, both samba and your clients are using a WINS server, then:

    ## /usr/local/samba/lib/smb.conf
-[global]
-     security = user
-     encrypt passwords = yes
-
-     netbios name = TASHTEGO
-     workgroup = NARNIA
-
-     # ldap related parameters
-
-     # define the DN to use when binding to the directory servers
-     # The password for this DN is not stored in smb.conf.  Rather it
-     # must be set by using 'smbpasswd -w secretpw' to store the
-     # passphrase in the secrets.tdb file.  If the "ldap admin dn" values
-     # changes, this password will need to be reset.
-     ldap admin dn = "cn=Samba Manager,ou=people,dc=samba,dc=org"
-
-     #  specify the LDAP server's hostname (defaults to locahost)
-     ldap server = ahab.samba.org
-
-     # Define the SSL option when connecting to the directory
-     # ('off', 'start tls', or 'on' (default))
-     ldap ssl = start tls
-
-     # define the port to use in the LDAP session (defaults to 636 when
-     # "ldap ssl = on")
-     ldap port = 389
-
-     # specify the base DN to use when searching the directory
-     ldap suffix = "ou=people,dc=samba,dc=org"
-
-     # generally the default ldap search filter is ok
-     # ldap filter = "(&(uid=%u)(objectclass=sambaAccount))"

    1. your local master browsers will contact the WINS server and, as long as + samba has registered that it is a domain master browser with the WINS + server, your local master browser will receive samba's ip address + as its domain master browser. +

    2. when a client receives a domain-wide browse list, and a user attempts + to access a host in that list, it will contact the WINS server to + resolve the NetBIOS name of that host. as long as that host has + registered its NetBIOS name with the same WINS server, the user will + be able to see that host. +

    19.6. Accounts and Groups management

    As users accounts are managed thru the sambaAccount objectclass, you should -modify you existing administration tools to deal with sambaAccount attributes.

    Machines accounts are managed with the sambaAccount objectclass, just -like users accounts. However, it's up to you to stored thoses accounts -in a different tree of you LDAP namespace: you should use -"ou=Groups,dc=plainjoe,dc=org" to store groups and -"ou=People,dc=plainjoe,dc=org" to store users. Just configure your -NSS and PAM accordingly (usually, in the /etc/ldap.conf configuration -file).

    15.10. Note about broadcast addresses

    In Samba release 2.2.3, the group management system is based on posix -groups. This meand that Samba make usage of the posixGroup objectclass. -For now, there is no NT-like group system management (global and local -groups).

    If your network uses a "0" based broadcast address (for example if it +ends in a 0) then you will strike problems. Windows for Workgroups +does not seem to support a 0's broadcast and you will probably find +that browsing and name lookups won't work.

    19.7. Security and sambaAccount

    There are two important points to remember when discussing the security -of sambaAccount entries in the directory.

    • 15.11. Multiple interfaces

      Never retrieve the lmPassword or - ntPassword attribute values over an unencrypted LDAP session.

    • Samba now supports machines with multiple network interfaces. If you +have multiple interfaces then you will need to use the "interfaces" +option in smb.conf to configure them. See smb.conf(5) for details.

    Chapter 16. Stackable VFS modules

    16.1. Introduction and configuration

    Never allow non-admin users to - view the lmPassword or ntPassword attribute values.

    Since samba 3.0, samba supports stackable VFS(Virtual File System) modules. +Samba passes each request to access the unix file system thru the loaded VFS modules. +This chapter covers all the modules that come with the samba source and references to +some external modules.

    These password hashes are clear text equivalents and can be used to impersonate -the user without deriving the original clear text strings. For more information -on the details of LM/NT password hashes, refer to the ENCRYPTION chapter of the Samba-HOWTO-Collection.

    You may have problems to compile these modules, as shared libraries are +compiled and linked in different ways on different systems. +They currently have been tested against GNU/linux and IRIX.

    To remedy the first security issue, the "ldap ssl" smb.conf parameter defaults -to require an encrypted session (ldap ssl = on) using -the default port of 636 -when contacting the directory server. When using an OpenLDAP 2.0 server, it -is possible to use the use the StartTLS LDAP extended operation in the place of -LDAPS. In either case, you are strongly discouraged to disable this security -(To use the VFS modules, create a share similar to the one below. The +important parameter is the ldap ssl = off).

    Note that the LDAPS protocol is deprecated in favor of the LDAPv3 StartTLS -extended operation. However, the OpenLDAP library still provides support for -the older method of securing communication between clients and servers.

    The second security precaution is to prevent non-administrative users from -harvesting password hashes from the directory. This can be done using the -following ACL in slapd.conf:

    vfs object parameter which must point to
+the exact pathname of the shared library objects. For example, to log all access 
+to files and use a recycle bin:
+
+
    ## allow the "ldap admin dn" access, but deny everyone else
-access to attrs=lmPassword,ntPassword
-     by dn="cn=Samba Admin,ou=people,dc=plainjoe,dc=org" write
-     by * none
           [audit]
+                comment = Audited /data directory
+                path = /data
+                vfs object = /path/to/audit.so /path/to/recycle.so
+                writeable = yes
+                browseable = yes

    The modules are used in the order they are specified.

    Further documentation on writing VFS modules for Samba can be found in +the Samba Developers Guide.

    19.8. LDAP specials attributes for sambaAccounts

    The sambaAccount objectclass is composed of the following attributes:

    16.2. Included modules

    16.2.1. audit

    A simple module to audit file access to the syslog +facility. The following operations are logged: +

    • lmPassword: the LANMAN password 16-byte hash stored as a character - representation of a hexidecimal string.

    • ntPassword: the NT password hash 16-byte stored as a character - representation of a hexidecimal string.

    • pwdLastSet: The integer time in seconds since 1970 when the - lmPassword and ntPassword attributes were last set. -

    • acctFlags: string of 11 characters surrounded by square brackets [] - representing account flags such as U (user), W(workstation), X(no password expiration), and - D(disabled).

    • logonTime: Integer value currently unused

    • logoffTime: Integer value currently unused

    • kickoffTime: Integer value currently unused

    • pwdCanChange: Integer value currently unused

    • pwdMustChange: Integer value currently unused

    • share
      connect/disconnect
      directory opens/create/remove
      file open/close/rename/unlink/chmod

      homeDrive: specifies the drive letter to which to map the - UNC path specified by homeDirectory. The drive letter must be specified in the form "X:" - where X is the letter of the drive to map. Refer to the "logon drive" parameter in the - smb.conf(5) man page for more information.

    16.2.2. recycle

    scriptPath: The scriptPath property specifies the path of - the user's logon script, .CMD, .EXE, or .BAT file. The string can be null. The path - is relative to the netlogon share. Refer to the "logon script" parameter in the - smb.conf(5) man page for more information.

  • A recycle-bin like modules. When used any unlink call +will be intercepted and files moved to the recycle +directory instead of beeing deleted.

    profilePath: specifies a path to the user's profile. - This value can be a null string, a local absolute path, or a UNC path. Refer to the - "logon path" parameter in the smb.conf(5) man page for more information.

  • Supported options: +

    vfs_recycle_bin:repository

    smbHome: The homeDirectory property specifies the path of - the home directory for the user. The string can be null. If homeDrive is set and specifies - a drive letter, homeDirectory should be a UNC path. The path must be a network - UNC path of the form \\server\share\directory. This value can be a null string. - Refer to the "logon home" parameter in the smb.conf(5) man page for more information. -

  • FIXME

    vfs_recycle_bin:keeptree

    userWorkstation: character string value currently unused. -

  • FIXME

    vfs_recycle_bin:versions

    rid: the integer representation of the user's relative identifier - (RID).

  • FIXME

    vfs_recycle_bin:touch

    primaryGroupID: the relative identifier (RID) of the primary group - of the user.

    • FIXME

    vfs_recycle_bin:maxsize

    The majority of these parameters are only used when Samba is acting as a PDC of -a domain (refer to the Samba-PDC-HOWTO for details on -how to configure Samba as a Primary Domain Controller). The following four attributes -are only stored with the sambaAccount entry if the values are non-default values:

    FIXME

    vfs_recycle_bin:exclude

    • FIXME

    vfs_recycle_bin:exclude_dir

    smbHome

  • FIXME

    • vfs_recycle_bin:noversions

    scriptPath

  • FIXME

    • 16.2.3. netatalk

    logonPath

  • A netatalk module, that will ease co-existence of samba and +netatalk file sharing services.

    homeDrive

    • Advantages compared to the old netatalk module: +

    it doesn't care about creating of .AppleDouble forks, just keeps ones in sync
    if share in smb.conf doesn't contain .AppleDouble item in hide or veto list, it will be added automatically

    These attributes are only stored with the sambaAccount entry if -the values are non-default values. For example, assume TASHTEGO has now been -configured as a PDC and that logon home = \\%L\%u was defined in -its smb.conf file. When a user named "becky" logons to the domain, -the logon home string is expanded to \\TASHTEGO\becky. -If the smbHome attribute exists in the entry "uid=becky,ou=people,dc=samba,dc=org", -this value is used. However, if this attribute does not exist, then the value -of the logon home parameter is used in its place. Samba -will only write the attribute value to the directory entry is the value is -something other than the default (e.g. \\MOBY\becky).

    19.9. Example LDIF Entries for a sambaAccount

    16.3. VFS modules available elsewhere

    The following is a working LDIF with the inclusion of the posixAccount objectclass:

    This section contains a listing of various other VFS modules that +have been posted but don't currently reside in the Samba CVS +tree for one reason ot another (e.g. it is easy for the maintainer +to have his or her own CVS tree).

    dn: uid=guest2, ou=people,dc=plainjoe,dc=org
-ntPassword: 878D8014606CDA29677A44EFA1353FC7
-pwdMustChange: 2147483647
-primaryGroupID: 1201
-lmPassword: 552902031BEDE9EFAAD3B435B51404EE
-pwdLastSet: 1010179124
-logonTime: 0
-objectClass: sambaAccount
-uid: guest2
-kickoffTime: 2147483647
-acctFlags: [UX         ]
-logoffTime: 2147483647
-rid: 19006
-pwdCanChange: 0
    No statemets about the stability or functionality any module +should be implied due to its presence here.

    16.3.1. DatabaseFS

    URL: http://www.css.tayloru.edu/~elorimer/databasefs/index.php

    The following is an LDIF entry for using both the sambaAccount and -posixAccount objectclasses:

    By Eric Lorimer.

    dn: uid=gcarter, ou=people,dc=plainjoe,dc=org
-logonTime: 0
-displayName: Gerald Carter
-lmPassword: 552902031BEDE9EFAAD3B435B51404EE
-primaryGroupID: 1201
-objectClass: posixAccount
-objectClass: sambaAccount
-acctFlags: [UX         ]
-userPassword: {crypt}BpM2ej8Rkzogo
-uid: gcarter
-uidNumber: 9000
-cn: Gerald Carter
-loginShell: /bin/bash
-logoffTime: 2147483647
-gidNumber: 100
-kickoffTime: 2147483647
-pwdLastSet: 1010179230
-rid: 19000
-homeDirectory: /home/tashtego/gcarter
-pwdCanChange: 0
-pwdMustChange: 2147483647
-ntPassword: 878D8014606CDA29677A44EFA1353FC7

    I have created a VFS module which implements a fairly complete read-only +filesystem. It presents information from a database as a filesystem in +a modular and generic way to allow different databases to be used +(originally designed for organizing MP3s under directories such as +"Artists," "Song Keywords," etc... I have since applied it to a student +roster database very easily). The directory structure is stored in the +database itself and the module makes no assumptions about the database +structure beyond the table it requires to run.

    Any feedback would be appreciated: comments, suggestions, patches, +etc... If nothing else, hopefully it might prove useful for someone +else who wishes to create a virtual filesystem.

    19.10. Comments

    16.3.2. vscan

    Please mail all comments regarding this HOWTO to URL: jerry@samba.org. This documents was -last updated to reflect the Samba 2.2.3 release.

    http://www.openantivirus.org/

    samba-vscan is a proof-of-concept module for Samba, which +uses the VFS (virtual file system) features of Samba 2.2.x/3.0 +alphaX. Of couse, Samba has to be compiled with VFS support. +samba-vscan supports various virus scanners and is maintained +by Rainer Link.

    Chapter 20. HOWTO Access Samba source code via CVSChapter 17. Access Samba source code via CVS

    20.1. Introduction

    17.1. Introduction

    Samba is developed in an open environment. Developers use CVS (Concurrent Versioning System) to "checkin" (also known as @@ -14432,9 +14614,9 @@ CLASS="SECT1" >

    20.2. CVS Access to samba.org

    17.2. CVS Access to samba.org

    The machine samba.org runs a publicly accessible CVS repository for access to the source code of several packages, @@ -14445,9 +14627,9 @@ CLASS="SECT2" >

    20.2.1. Access via CVSweb

    17.2.1. Access via CVSweb

    You can access the source code via your favourite WWW browser. This allows you to access the contents of @@ -14466,9 +14648,9 @@ CLASS="SECT2" >

    20.2.2. Access via cvs

    17.2.2. Access via cvs

    You can also access the source code via a normal cvs client. This gives you much more control over you can @@ -14576,7 +14758,7 @@ CLASS="CHAPTER" >Chapter 21. Group mapping HOWTOChapter 18. Group mapping HOWTO

    Starting with Samba 3.0 alpha 2, a new group mapping function is available. The @@ -14677,135 +14859,46 @@ CLASS="CHAPTER" >Chapter 22. Samba performance issuesChapter 19. Samba performance issues

    22.1. Comparisons

    19.1. Comparisons

    The Samba server uses TCP to talk to the client. Thus if you are trying to see if it performs well you should really compare it to programs that use the same protocol. The most readily available programs for file transfer that use TCP are ftp or another TCP based -SMB server.

    If you want to test against something like a NT or WfWg server then -you will have to disable all but TCP on either the client or -server. Otherwise you may well be using a totally different protocol -(such as Netbeui) and comparisons may not be valid.

    Generally you should find that Samba performs similarly to ftp at raw -transfer speed. It should perform quite a bit faster than NFS, -although this very much depends on your system.

    Several people have done comparisons between Samba and Novell, NFS or -WinNT. In some cases Samba performed the best, in others the worst. I -suspect the biggest factor is not Samba vs some other system but the -hardware and drivers used on the various systems. Given similar -hardware Samba should certainly be competitive in speed with other -systems.

    22.2. Oplocks

    22.2.1. Overview

    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 agressively cache file -data. With some oplock types the client may even cache file open/close -operations. This can give enormous performance benefits.

    With the release of Samba 1.9.18 we now correctly support opportunistic -locks. This is turned on by default, and can be turned off on a share- -by-share basis by setting the parameter :

    oplocks = False

    We recommend that you leave oplocks on however, as current benchmark -tests with NetBench seem to give approximately a 30% improvement in -speed with them on. This is on average however, and the actual -improvement seen can be orders of magnitude greater, depending on -what the client redirector is doing.

    Previous to Samba 1.9.18 there was a 'fake oplocks' option. This -option has been left in the code for backwards compatibility reasons -but it's use is now deprecated. A short summary of what the old -code did follows.

    22.2.2. Level2 Oplocks

    With Samba 2.0.5 a new capability - level2 (read only) oplocks is -supported (although the option is off by default - see the smb.conf -man page for details). Turning on level2 oplocks (on a share-by-share basis) -by setting the parameter :

    level2 oplocks = true

    should speed concurrent access to files that are not commonly written -to, such as application serving shares (ie. shares that contain common -.EXE files - such as a Microsoft Office share) as it allows clients to -read-ahread cache copies of these files.

    22.2.3. Old 'fake oplocks' option - deprecated

    Samba can also fake oplocks, by granting a oplock whenever a client -asks for one. This is controlled using the smb.conf option "fake -oplocks". If you set "fake oplocks = yes" then you are telling the -client that it may agressively cache the file data for all opens.

    If you want to test against something like a NT or WfWg server then +you will have to disable all but TCP on either the client or +server. Otherwise you may well be using a totally different protocol +(such as Netbeui) and comparisons may not be valid.

    Enabling 'fake oplocks' on all read-only shares or shares that you know -will only be accessed from one client at a time you will see a big -performance improvement on many operations. If you enable this option -on shares where multiple clients may be accessing the files read-write -at the same time you can get data corruption.

    Generally you should find that Samba performs similarly to ftp at raw +transfer speed. It should perform quite a bit faster than NFS, +although this very much depends on your system.

    Several people have done comparisons between Samba and Novell, NFS or +WinNT. In some cases Samba performed the best, in others the worst. I +suspect the biggest factor is not Samba vs some other system but the +hardware and drivers used on the various systems. Given similar +hardware Samba should certainly be competitive in speed with other +systems.

    22.3. Socket options

    19.2. Socket options

    There are a number of socket options that can greatly affect the performance of a TCP based server like Samba.

    22.4. Read size

    19.3. Read size

    The option "read size" affects the overlap of disk reads/writes with network reads/writes. If the amount of data being transferred in @@ -14857,9 +14950,9 @@ CLASS="SECT1" >

    22.5. Max xmit

    19.4. Max xmit

    At startup the client and server negotiate a "maximum transmit" size, which limits the size of nearly all SMB commands. You can set the @@ -14880,331 +14973,626 @@ CLASS="SECT1" >

    22.6. Locking

    By default Samba does not implement strict locking on each read/write -call (although it did in previous versions). If you enable strict -locking (using "strict locking = yes") then you may find that you -suffer a severe performance hit on some systems.

    19.5. Log level

    The performance hit will probably be greater on NFS mounted -filesystems, but could be quite high even on local disks.

    If you set the log level (also known as "debug level") higher than 2 +then you may suffer a large drop in performance. This is because the +server flushes the log file after each operation, which can be very +expensive.

    22.7. Share modes

    19.6. Read raw

    Some people find that opening files is very slow. This is often -because of the "share modes" code needed to fully implement the dos -share modes stuff. You can disable this code using "share modes = -no". This will gain you a lot in opening and closing files but will -mean that (in some cases) the system won't force a second user of a -file to open the file read-only if the first has it open -read-write. For many applications that do their own locking this -doesn't matter, but for some it may. Most Windows applications -depend heavily on "share modes" working correctly and it is -recommended that the Samba share mode support be left at the -default of "on".

    The "read raw" operation is designed to be an optimised, low-latency +file read operation. A server may choose to not support it, +however. and Samba makes support for "read raw" optional, with it +being enabled by default.

    The share mode code in Samba has been re-written in the 1.9.17 -release following tests with the Ziff-Davis NetBench PC Benchmarking -tool. It is now believed that Samba 1.9.17 implements share modes -similarly to Windows NT.

    In some cases clients don't handle "read raw" very well and actually +get lower performance using it than they get using the conventional +read operations.

    NOTE: In the most recent versions of Samba there is an option to use -shared memory via mmap() to implement the share modes. This makes -things much faster. See the Makefile for how to enable this.

    So you might like to try "read raw = no" and see what happens on your +network. It might lower, raise or not affect your performance. Only +testing can really tell.

    22.8. Log level

    19.7. Write raw

    If you set the log level (also known as "debug level") higher than 2 -then you may suffer a large drop in performance. This is because the -server flushes the log file after each operation, which can be very -expensive.

    The "write raw" operation is designed to be an optimised, low-latency +file write operation. A server may choose to not support it, +however. and Samba makes support for "write raw" optional, with it +being enabled by default.

    Some machines may find "write raw" slower than normal write, in which +case you may wish to change this option.

    22.9. Wide lines

    19.8. Slow Clients

    The "wide links" option is now enabled by default, but if you disable -it (for better security) then you may suffer a performance hit in -resolving filenames. The performance loss is lessened if you have -"getwd cache = yes", which is now the default.

    One person has reported that setting the protocol to COREPLUS rather +than LANMAN2 gave a dramatic speed improvement (from 10k/s to 150k/s).

    I suspect that his PC's (386sx16 based) were asking for more data than +they could chew. I suspect a similar speed could be had by setting +"read raw = no" and "max xmit = 2048", instead of changing the +protocol. Lowering the "read size" might also help.

    22.10. Read raw

    The "read raw" operation is designed to be an optimised, low-latency -file read operation. A server may choose to not support it, -however. and Samba makes support for "read raw" optional, with it -being enabled by default.

    19.9. Slow Logins

    In some cases clients don't handle "read raw" very well and actually -get lower performance using it than they get using the conventional -read operations.

    So you might like to try "read raw = no" and see what happens on your -network. It might lower, raise or not affect your performance. Only -testing can really tell.

    Slow logins are almost always due to the password checking time. Using +the lowest practical "password level" will improve things a lot. You +could also enable the "UFC crypt" option in the Makefile.

    22.11. Write raw

    19.10. Client tuning

    The "write raw" operation is designed to be an optimised, low-latency -file write operation. A server may choose to not support it, -however. and Samba makes support for "write raw" optional, with it -being enabled by default.

    Often a speed problem can be traced to the client. The client (for +example Windows for Workgroups) can often be tuned for better TCP +performance.

    Some machines may find "write raw" slower than normal write, in which -case you may wish to change this option.

    See your client docs for details. In particular, I have heard rumours +that the WfWg options TCPWINDOWSIZE and TCPSEGMENTSIZE can have a +large impact on performance.

    Also note that some people have found that setting DefaultRcvWindow in +the [MSTCP] section of the SYSTEM.INI file under WfWg to 3072 gives a +big improvement. I don't know why.

    My own experience wth DefaultRcvWindow is that I get much better +performance with a large value (16384 or larger). Other people have +reported that anything over 3072 slows things down enourmously. One +person even reported a speed drop of a factor of 30 when he went from +3072 to 8192. I don't know why.

    It probably depends a lot on your hardware, and the type of unix box +you have at the other end of the link.

    Paul Cochrane has done some testing on client side tuning and come +to the following conclusions:

    Install the W2setup.exe file from www.microsoft.com. This is an +update for the winsock stack and utilities which improve performance.

    Configure the win95 TCPIP registry settings to give better +perfomance. I use a program called MTUSPEED.exe which I got off the +net. There are various other utilities of this type freely available. +The setting which give the best performance for me are:

    1. MaxMTU Remove

    2. RWIN Remove

    3. MTUAutoDiscover Disable

    4. MTUBlackHoleDetect Disable

    5. Time To Live Enabled

    6. Time To Live - HOPS 32

    7. NDI Cache Size 0

    I tried virtually all of the items mentioned in the document and +the only one which made a difference to me was the socket options. It +turned out I was better off without any!!!!!

    In terms of overall speed of transfer, between various win95 clients +and a DX2-66 20MB server with a crappy NE2000 compatible and old IDE +drive (Kernel 2.0.30). The transfer rate was reasonable for 10 baseT.

    The figures are:          Put              Get 
+P166 client 3Com card:    420-440kB/s      500-520kB/s
+P100 client 3Com card:    390-410kB/s      490-510kB/s
+DX4-75 client NE2000:     370-380kB/s      330-350kB/s

    I based these test on transfer two files a 4.5MB text file and a 15MB +textfile. The results arn't bad considering the hardware Samba is +running on. It's a crap machine!!!!

    The updates mentioned in 1 and 2 brought up the transfer rates from +just over 100kB/s in some clients.

    A new client is a P333 connected via a 100MB/s card and hub. The +transfer rates from this were good: 450-500kB/s on put and 600+kB/s +on get.

    Looking at standard FTP throughput, Samba is a bit slower (100kB/s +upwards). I suppose there is more going on in the samba protocol, but +if it could get up to the rate of FTP the perfomance would be quite +staggering.

    Chapter 20. Creating Group Profiles

    22.12. Read prediction

    Samba can do read prediction on some of the SMB commands. Read -prediction means that Samba reads some extra data on the last file it -read while waiting for the next SMB command to arrive. It can then -respond more quickly when the next read request arrives.

    20.1. Windows '9x

    This is disabled by default. You can enable it by using "read -prediction = yes".

    You need the Win98 Group Policy Editor to +set Group Profiles up under Windows '9x. It can be found on the Original +full product Win98 installation CD under +tools/reskit/netadmin/poledit. You install this +using the Add/Remove Programs facility and then click on the 'Have Disk' +tab.

    Note that read prediction is only used on files that were opened read -only.

    Use the Group Policy Editor to create a policy file that specifies the +location of user profiles and/or the My Documents etc. +stuff. You then save these settings in a file called +Config.POL that needs to be placed in +the root of the [NETLOGON] share. If your Win98 is configured to log onto +the Samba Domain, it will automatically read this file and update the +Win98 registry of the machine that is logging on.

    Read prediction should particularly help for those silly clients (such -as "Write" under NT) which do lots of very small reads on a file.

    All of this is covered in the Win98 Resource Kit documentation.

    Samba will not read ahead more data than the amount specified in the -"read size" option. It always reads ahead on 1k block boundaries.

    If you do not do it this way, then every so often Win98 will check the +integrity of the registry and will restore it's settings from the back-up +copy of the registry it stores on each Win98 machine. Hence, you will notice +things changing back to the original settings.

    20.2. Windows NT 4

    Unfortunately, the Resource Kit info is Win NT4/2K version specific.

    Here is a quick guide:

    • On your NT4 Domain Controller, right click on 'My Computer', then +select the tab labelled 'User Profiles'.

    • Select a user profile you want to migrate and click on it.

      I am using the term "migrate" lossely. You can copy a profile to +create a group profile. You can give the user 'Everyone' rights to the +profile you copy this to. That is what you need to do, since your samba +domain is not a member of a trust relationship with your NT4 PDC.

    • Click the 'Copy To' button.

    • In the box labelled 'Copy Profile to' add your new path, eg: +c:\temp\foobar

    • Click on the button labelled 'Change' in the "Permitted to use" box.

    • Click on the group 'Everyone' and then click OK. This closes the +'chose user' box.

    • Now click OK.

    Follow the above for every profile you need to migrate.

    20.2.1. Side bar Notes

    You should obtain the SID of your NT4 domain. You can use smbpasswd to do +this. Read the man page.

    With Samba-3.0.0 alpha code you can import all you NT4 domain accounts +using the net samsync method. This way you can retain your profile +settings as well as all your users.

    20.2.2. Mandatory profiles

    The above method can be used to create mandatory profiles also. To convert +a group profile into a mandatory profile simply locate the NTUser.DAT file +in the copied profile and rename it to NTUser.MAN.

    22.13. Memory mapping

    Samba supports reading files via memory mapping them. One some -machines this can give a large boost to performance, on others it -makes not difference at all, and on some it may reduce performance.

    20.2.3. moveuser.exe

    To enable you you have to recompile Samba with the -DUSE_MMAP option -on the FLAGS line of the Makefile.

    Note that memory mapping is only used on files opened read only, and -is not used by the "read raw" operation. Thus you may find memory -mapping is more effective if you disable "read raw" using "read raw = -no".

    The W2K professional resource kit has moveuser.exe. moveuser.exe changes +the security of a profile from one user to another. This allows the account +domain to change, and/or the user name to change.

    22.14. Slow Clients

    20.2.4. Get SID

    One person has reported that setting the protocol to COREPLUS rather -than LANMAN2 gave a dramatic speed improvement (from 10k/s to 150k/s).

    You can identify the SID by using GetSID.exe from the Windows NT Server 4.0 +Resource Kit.

    I suspect that his PC's (386sx16 based) were asking for more data than -they could chew. I suspect a similar speed could be had by setting -"read raw = no" and "max xmit = 2048", instead of changing the -protocol. Lowering the "read size" might also help.

    Windows NT 4.0 stores the local profile information in the registry under +the following key: +HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileList

    Under the ProfileList key, there will be subkeys named with the SIDs of the +users who have logged on to this computer. (To find the profile information +for the user whose locally cached profile you want to move, find the SID for +the user with the GetSID.exe utility.) Inside of the appropriate user's +subkey, you will see a string value named ProfileImagePath.

    22.15. Slow Logins

    20.3. Windows 2000/XP

    Slow logins are almost always due to the password checking time. Using -the lowest practical "password level" will improve things a lot. You -could also enable the "UFC crypt" option in the Makefile.

    You must first convert the profile from a local profile to a domain +profile on the MS Windows workstation as follows:

    • Log on as the LOCAL workstation administrator.

    • Right click on the 'My Computer' Icon, select 'Properties'

    • Click on the 'User Profiles' tab

    • Select the profile you wish to convert (click on it once)

    • Click on the button 'Copy To'

    • In the "Permitted to use" box, click on the 'Change' button.

    • Click on the 'Look in" area that lists the machine name, when you click +here it will open up a selection box. Click on the domain to which the +profile must be accessible.

      22.16. Client tuning

      Often a speed problem can be traced to the client. The client (for -example Windows for Workgroups) can often be tuned for better TCP -performance.

      See your client docs for details. In particular, I have heard rumours -that the WfWg options TCPWINDOWSIZE and TCPSEGMENTSIZE can have a -large impact on performance.

      You will need to log on if a logon box opens up. Eg: In the connect +as: MIDEARTH\root, password: mypassword.

    • Also note that some people have found that setting DefaultRcvWindow in -the [MSTCP] section of the SYSTEM.INI file under WfWg to 3072 gives a -big improvement. I don't know why.

      To make the profile capable of being used by anyone select 'Everyone'

    • My own experience wth DefaultRcvWindow is that I get much better -performance with a large value (16384 or larger). Other people have -reported that anything over 3072 slows things down enourmously. One -person even reported a speed drop of a factor of 30 when he went from -3072 to 8192. I don't know why.

      Click OK. The Selection box will close.

    • It probably depends a lot on your hardware, and the type of unix box -you have at the other end of the link.

      Now click on the 'Ok' button to create the profile in the path you +nominated.

    Paul Cochrane has done some testing on client side tuning and come -to the following conclusions:

    Done. You now have a profile that can be editted using the samba-3.0.0 +profiles tool.

    Install the W2setup.exe file from www.microsoft.com. This is an -update for the winsock stack and utilities which improve performance.

    Configure the win95 TCPIP registry settings to give better -perfomance. I use a program called MTUSPEED.exe which I got off the -net. There are various other utilities of this type freely available. -The setting which give the best performance for me are:

    Under NT/2K the use of mandotory profiles forces the use of MS Exchange +storage of mail data. That keeps desktop profiles usable.

      • MaxMTU Remove

        This is a security check new to Windows XP (or maybe only +Windows XP service pack 1). It can be disabled via a group policy in +Active Directory. The policy is:

        "Computer Configuration\Administrative Templates\System\User +Profiles\Do not check for user ownership of Roaming Profile Folders"

        ...and it should be set to "Enabled". +Does the new version of samba have an Active Directory analogue? If so, +then you may be able to set the policy through this.

        If you cannot set group policies in samba, then you may be able to set +the policy locally on each machine. If you want to try this, then do +the following (N.B. I don't know for sure that this will work in the +same way as a domain group policy):

      • RWIN Remove

        On the XP workstation log in with an Administrator account.

      • MTUAutoDiscover Disable

        Click: "Start", "Run"

      • MTUBlackHoleDetect Disable

        Type: "mmc"

      • Time To Live Enabled

        Click: "OK"

      • Time To Live - HOPS 32

        A Microsoft Management Console should appear.

      • NDI Cache Size 0

        Click: File, "Add/Remove Snap-in...", "Add"

      • I tried virtually all of the items mentioned in the document and -the only one which made a difference to me was the socket options. It -turned out I was better off without any!!!!!

        Double-Click: "Group Policy"

      • In terms of overall speed of transfer, between various win95 clients -and a DX2-66 20MB server with a crappy NE2000 compatible and old IDE -drive (Kernel 2.0.30). The transfer rate was reasonable for 10 baseT.

        Click: "Finish", "Close"

      • FIXME -The figures are: Put Get -P166 client 3Com card: 420-440kB/s 500-520kB/s -P100 client 3Com card: 390-410kB/s 490-510kB/s -DX4-75 client NE2000: 370-380kB/s 330-350kB/s

        Click: "OK"

      • I based these test on transfer two files a 4.5MB text file and a 15MB -textfile. The results arn't bad considering the hardware Samba is -running on. It's a crap machine!!!!

        In the "Console Root" window:

      • The updates mentioned in 1 and 2 brought up the transfer rates from -just over 100kB/s in some clients.

        Expand: "Local Computer Policy", "Computer Configuration",

      • A new client is a P333 connected via a 100MB/s card and hub. The -transfer rates from this were good: 450-500kB/s on put and 600+kB/s -on get.

        "Administrative Templates", "System", "User Profiles"

      • Looking at standard FTP throughput, Samba is a bit slower (100kB/s -upwards). I suppose there is more going on in the samba protocol, but -if it could get up to the rate of FTP the perfomance would be quite -staggering.

        22.17. My Results

        Double-Click: "Do not check for user ownership of Roaming Profile

      • Folders"

      • Some people want to see real numbers in a document like this, so here -they are. I have a 486sx33 client running WfWg 3.11 with the 3.11b -tcp/ip stack. It has a slow IDE drive and 20Mb of ram. It has a SMC -Elite-16 ISA bus ethernet card. The only WfWg tuning I've done is to -set DefaultRcvWindow in the [MSTCP] section of system.ini to 16384. My -server is a 486dx3-66 running Linux. It also has 20Mb of ram and a SMC -Elite-16 card. You can see my server config in the examples/tridge/ -subdirectory of the distribution.

        Select: "Enabled"

      • I get 490k/s on reading a 8Mb file with copy. -I get 441k/s writing the same file to the samba server.

        Click: OK"

      • Of course, there's a lot more to benchmarks than 2 raw throughput -figures, but it gives you a ballpark figure.

        Close the whole console. You do not need to save the settings (this +refers to the console settings rather than the policies you have +changed).

      • I've also tested Win95 and WinNT, and found WinNT gave me the best -speed as a samba client. The fastest client of all (for me) is -smbclient running on another linux box. Maybe I'll add those results -here someday ...

        Reboot

    Table of Contents
    23. 21. Portability
    23.1. 21.1. HPUX
    23.2. 21.2. SCO Unix
    23.3. 21.3. DNIX
    23.4. 21.4. RedHat Linux Rembrandt-II
    24. 22. Samba and other CIFS clients
    24.1. 22.1. Macintosh clients?
    24.2. 22.2. OS2 Client
    24.2.1. 22.2.1. How can I configure OS/2 Warp Connect or OS/2 Warp 4 as a client for Samba?
    24.2.2. 22.2.2. How can I configure OS/2 Warp 3 (not Connect), OS/2 1.2, 1.3 or 2.x for Samba?
    24.2.3. 22.2.3. Are there any other issues when OS/2 (any version) is used as a client?
    24.2.4. 22.2.4. How do I get printer driver download working for OS/2 clients?
    24.3. 22.3. Windows for Workgroups
    24.3.1. 22.3.1. Use latest TCP/IP stack from Microsoft
    24.3.2. 22.3.2. Delete .pwl files after password change
    24.3.3. 22.3.3. Configure WfW password handling
    24.3.4. 22.3.4. Case handling of passwords
    24.4. 22.4. Windows '95/'98
    24.5. 22.5. Windows 2000 Service Pack 2
    25. 23. Reporting Bugs
    25.1. 23.1. Introduction
    25.2. 23.2. General info
    25.3. 23.3. Debug levels
    25.4. 23.4. Internal errors
    25.5. 23.5. Attaching to a running process
    25.6. 23.6. Patches
    26. 24. Diagnosing your samba server
    26.1. 24.1. Introduction
    26.2. 24.2. Assumptions
    26.3. 24.3. Tests
    26.3.1. 24.3.1. Test 1
    26.3.2. 24.3.2. Test 2
    26.3.3. 24.3.3. Test 3
    26.3.4. 24.3.4. Test 4
    26.3.5. 24.3.5. Test 5
    26.3.6. 24.3.6. Test 6
    26.3.7. 24.3.7. Test 7
    26.3.8. 24.3.8. Test 8
    26.3.9. 24.3.9. Test 9
    26.3.10. 24.3.10. Test 10
    26.3.11. 24.3.11. Test 11
    26.4. 24.4. Still having troubles?
    Chapter 23. PortabilityChapter 21. Portability

    Samba works on a wide range of platforms but the interface all the platforms provide is not always compatible. This chapter contains @@ -15479,9 +15867,9 @@ CLASS="SECT1" >

    23.1. HPUX

    21.1. HPUX

    HP's implementation of supplementary groups is, er, non-standard (for hysterical reasons). There are two group files, /etc/group and @@ -15509,9 +15897,9 @@ CLASS="SECT1" >

    23.2. SCO Unix

    21.2. SCO Unix

    If you run an old version of SCO Unix then you may need to get important @@ -15526,9 +15914,9 @@ CLASS="SECT1" >

    23.3. DNIX

    21.3. DNIX

    DNIX has a problem with seteuid() and setegid(). These routines are needed for Samba to work correctly, but they were left out of the DNIX @@ -15633,9 +16021,9 @@ CLASS="SECT1" >

    23.4. RedHat Linux Rembrandt-II

    21.4. RedHat Linux Rembrandt-II

    By default RedHat Rembrandt-II during installation adds an entry to /etc/hosts as follows: @@ -15659,7 +16047,7 @@ CLASS="CHAPTER" >Chapter 24. Samba and other CIFS clientsChapter 22. Samba and other CIFS clients

    This chapter contains client-specific information.

    24.1. Macintosh clients?

    22.1. Macintosh clients?

    Yes.

    24.2. OS2 Client

    22.2. OS2 Client

    24.2.1. How can I configure OS/2 Warp Connect or +>22.2.1. How can I configure OS/2 Warp Connect or OS/2 Warp 4 as a client for Samba?

    A more complete answer to this question can be @@ -15780,9 +16168,9 @@ CLASS="SECT2" >

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

    You can use the free Microsoft LAN Manager 2.2c Client @@ -15824,9 +16212,9 @@ CLASS="SECT2" >

    24.2.3. Are there any other issues when OS/2 (any version) +>22.2.3. Are there any other issues when OS/2 (any version) is used as a client?

    When you do a NET VIEW or use the "File and Print @@ -15846,9 +16234,9 @@ CLASS="SECT2" >

    24.2.4. How do I get printer driver download working +>22.2.4. How do I get printer driver download working for OS/2 clients?

    First, create a share called [PRINTDRV] that is @@ -15897,17 +16285,17 @@ CLASS="SECT1" >

    24.3. Windows for Workgroups

    22.3. Windows for Workgroups

    24.3.1. Use latest TCP/IP stack from Microsoft

    22.3.1. Use latest TCP/IP stack from Microsoft

    Use the latest TCP/IP stack from microsoft if you use Windows for workgroups.

    24.3.2. Delete .pwl files after password change

    22.3.2. Delete .pwl files after password change

    WfWg does a lousy job with passwords. I find that if I change my password on either the unix box or the PC the safest thing to do is to @@ -15947,9 +16335,9 @@ CLASS="SECT2" >

    24.3.3. Configure WfW password handling

    22.3.3. Configure WfW password handling

    There is a program call admincfg.exe on the last disk (disk 8) of the WFW 3.11 disk set. To install it @@ -15966,9 +16354,9 @@ CLASS="SECT2" >

    24.3.4. Case handling of passwords

    22.3.4. Case handling of passwords

    Windows for Workgroups uppercases the password before sending it to the server. Unix passwords can be case-sensitive though. Check the

    24.4. Windows '95/'98

    22.4. Windows '95/'98

    When using Windows 95 OEM SR2 the following updates are recommended where Samba is being used. Please NOTE that the above change will affect you once these @@ -16033,9 +16421,9 @@ CLASS="SECT1" >

    24.5. Windows 2000 Service Pack 2

    22.5. Windows 2000 Service Pack 2

    There are several annoyances with Windows 2000 SP2. One of which @@ -16117,15 +16505,15 @@ CLASS="CHAPTER" >Chapter 25. Reporting BugsChapter 23. Reporting Bugs

    25.1. Introduction

    23.1. Introduction

    The email address for bug reports for stable releases is

    25.2. General info

    23.2. General info

    Before submitting a bug report check your config for silly errors. Look in your log files for obvious messages that tell you that @@ -16193,9 +16581,9 @@ CLASS="SECT1" >

    25.3. Debug levels

    23.3. Debug levels

    If the bug has anything to do with Samba behaving incorrectly as a server (like refusing to open a file) then the log files will probably @@ -16263,9 +16651,9 @@ CLASS="SECT1" >

    25.4. Internal errors

    23.4. Internal errors

    If you get a "INTERNAL ERROR" message in your log files it means that Samba got an unexpected signal while running. It is probably a @@ -16307,9 +16695,9 @@ CLASS="SECT1" >

    25.5. Attaching to a running process

    23.5. Attaching to a running process

    Unfortunately some unixes (in particular some recent linux kernels) refuse to dump a core file if the task has changed uid (which smbd @@ -16324,9 +16712,9 @@ CLASS="SECT1" >

    25.6. Patches

    23.6. Patches

    The best sort of bug report is one that includes a fix! If you send us patches please use Chapter 26. Diagnosing your samba serverChapter 24. Diagnosing your samba server

    26.1. Introduction

    24.1. Introduction

    This file contains a list of tests you can perform to validate your Samba server. It also tells you what the likely cause of the problem @@ -16375,9 +16763,9 @@ CLASS="SECT1" >

    26.2. Assumptions

    24.2. Assumptions

    In all of the tests it is assumed you have a Samba server called BIGSERVER and a PC called ACLIENT both in workgroup TESTGROUP.

    26.3. Tests

    24.3. Tests

    26.3.1. Test 1

    24.3.1. Test 1

    In the directory in which you store your smb.conf file, run the command "testparm smb.conf". If it reports any errors then your smb.conf @@ -16443,9 +16831,9 @@ CLASS="SECT2" >

    26.3.2. Test 2

    24.3.2. Test 2

    Run the command "ping BIGSERVER" from the PC and "ping ACLIENT" from the unix box. If you don't get a valid response then your TCP/IP @@ -16469,9 +16857,9 @@ CLASS="SECT2" >

    26.3.3. Test 3

    24.3.3. Test 3

    Run the command "smbclient -L BIGSERVER" on the unix box. You should get a list of available shares back.

    26.3.4. Test 4

    24.3.4. Test 4

    Run the command "nmblookup -B BIGSERVER __SAMBA__". You should get the IP address of your Samba server back.

    26.3.5. Test 5

    24.3.5. Test 5

    run the command

    26.3.6. Test 6

    24.3.6. Test 6

    Run the command

    26.3.7. Test 7

    24.3.7. Test 7

    Run the command

    26.3.8. Test 8

    24.3.8. Test 8

    On the PC type the command

    26.3.9. Test 9

    24.3.9. Test 9

    Run the command

    26.3.10. Test 10

    24.3.10. Test 10

    Run the command

    26.3.11. Test 11

    24.3.11. Test 11

    From file manager try to browse the server. Your samba server should appear in the browse list of your local workgroup (or the one you @@ -16853,9 +17241,9 @@ CLASS="SECT1" >

    26.4. Still having troubles?

    24.4. Still having troubles?

    Try the mailing list or newsgroup, or use the ethereal utility to sniff the problem. The official samba mailing list can be reached at diff --git a/docs/htmldocs/ads.html b/docs/htmldocs/ads.html index 26ec1d04a7..2c556b61f3 100644 --- a/docs/htmldocs/ads.html +++ b/docs/htmldocs/ads.html @@ -5,8 +5,7 @@ >Samba as a ADS domain member

    Chapter 8. Samba as a ADS domain member

    Chapter 7. Samba as a ADS domain member

    This is a rough guide to setting up Samba 3.0 with kerberos authentication against a Windows2000 KDC.

    Pieces you need before you begin: -

    Pieces you need before you begin:

    8.1. Installing the required packages for Debian

    7.1. Installing the required packages for Debian

    On Debian you need to install the following packages:

    On Debian you need to install the following packages: -

    8.2. Installing the required packages for RedHat

    7.2. Installing the required packages for RedHat

    On RedHat this means you should have at least:

    On RedHat this means you should have at least: -

    8.3. Compile Samba

    7.3. Compile Samba

    If your kerberos libraries are in a non-standard location then remember to add the configure option --with-krb5=DIR.

    After you run configure make sure that include/config.h contains +>After you run configure make sure that include/config.h it + generates contains lines like this:

      ads server = your.kerberos.server

    You do *not* need a smbpasswd file, although it won't do any harm - and if you have one then Samba will be able to fall back to normal - password security for older clients. I expect that the above +>You do *not* need a smbpasswd file, and older clients will + be authenticated as if "security = domain", although it won't do any harm + and allows you to have local users not in the domain. + I expect that the above required options will change soon when we get better active directory integration.

    8.4. Setup your /etc/krb5.conf

    7.4. Setup your /etc/krb5.conf

    The minimal configuration for krb5.conf is:

    	[realms]
+>[realms]
     YOUR.KERBEROS.REALM = {
 	kdc = your.kerberos.server
     }

    If all you want is kerberos support in smbclient then you can skip straight to step 5 now. Step 3 is only needed if you want kerberos -support in smbd.

    8.5. Create the computer account

    7.5. Create the computer account

    Do a "kinit" as a user that has authority to change arbitrary -passwords on the KDC ("Administrator" is a good choice). Then as a -user that has write permission on the Samba private directory +>As a user that has write permission on the Samba private directory (usually root) run:

    8.5.1. Possible errors

    7.5.1. Possible errors

    8.5.1. Possible errors
    "bash: kinit: command not found"

    kinit is in the krb5-workstation RPM on RedHat systems, and is in /usr/kerberos/bin, so it won't be in the path until you log in again (or open a new terminal)

    "ADS support not compiled in"

    8.6. Test your server setup

    7.6. Test your server setup

    On a Windows 2000 client try

    8.7. Testing with smbclient

    7.7. Testing with smbclient

    On your Samba server try to login to a Win2000 server or your Samba server using smbclient and kerberos. Use smbclient as usual, but @@ -335,7 +349,9 @@ CLASS="SECT1" >

    8.8. Notes

    7.8. Notes

    You must change administrator password at least once after DC install, to create the right encoding types

    Samba as a NT4 domain memberSamba as a NT4 or Win2k domain member
    AppendixesPrev

    Table of Contents
    23. 21. Portability
    23.1. 21.1. HPUX
    23.2. 21.2. SCO Unix
    23.3. 21.3. DNIX
    23.4. 21.4. RedHat Linux Rembrandt-II
    24. 22. Samba and other CIFS clients
    24.1. 22.1. Macintosh clients?
    24.2. 22.2. OS2 Client
    24.2.1. 22.2.1. How can I configure OS/2 Warp Connect or OS/2 Warp 4 as a client for Samba?
    24.2.2. 22.2.2. How can I configure OS/2 Warp 3 (not Connect), OS/2 1.2, 1.3 or 2.x for Samba?
    24.2.3. 22.2.3. Are there any other issues when OS/2 (any version) is used as a client?
    24.2.4. 22.2.4. How do I get printer driver download working for OS/2 clients?
    24.3. 22.3. Windows for Workgroups
    24.3.1. 22.3.1. Use latest TCP/IP stack from Microsoft
    24.3.2. 22.3.2. Delete .pwl files after password change
    24.3.3. 22.3.3. Configure WfW password handling
    24.3.4. 22.3.4. Case handling of passwords
    24.4. 22.4. Windows '95/'98
    24.5. 22.5. Windows 2000 Service Pack 2
    25. 23. Reporting Bugs
    25.1. 23.1. Introduction
    25.2. 23.2. General info
    25.3. 23.3. Debug levels
    25.4. 23.4. Internal errors
    25.5. 23.5. Attaching to a running process
    25.6. 23.6. Patches
    26. 24. Diagnosing your samba server
    26.1. 24.1. Introduction
    26.2. 24.2. Assumptions
    26.3. 24.3. Tests
    26.3.1. 24.3.1. Test 1
    26.3.2. 24.3.2. Test 2
    26.3.3. 24.3.3. Test 3
    26.3.4. 24.3.4. Test 4
    26.3.5. 24.3.5. Test 5
    26.3.6. 24.3.6. Test 6
    26.3.7. 24.3.7. Test 7
    26.3.8. 24.3.8. Test 8
    26.3.9. 24.3.9. Test 9
    26.3.10. 24.3.10. Test 10
    26.3.11. 24.3.11. Test 11
    26.4. 24.4. Still having troubles?
    PrevSamba performance issuesCreating Group Profiles

    		Quick Cross Subnet Browsing / Cross Workgroup Browsing guidePrev

    Alternative means of name resolution includes: -

    Alternative means of name resolution includes:

    Many sites want to restrict DNS lookups and want to avoid broadcast name resolution traffic. The "name resolve order" parameter is of great help here. The syntax of the "name resolve order" parameter is: 

    	name resolve order = wins lmhosts bcast host
    name resolve order = wins lmhosts bcast host _or_ 
    	name resolve order = wins lmhosts  	(eliminates bcast and host)
    name resolve order = wins lmhosts (eliminates bcast and host) The default is: 
    	name  resolve order = host lmhost wins bcast
    name resolve order = host lmhost wins bcast. where "host" refers the the native methods used by the Unix system to implement the gethostbyname() function call. This is normally @@ -388,7 +400,7 @@ WIDTH="33%" ALIGN="left" VALIGN="top" >PrevNextImproved browsing in sambaHow to Install and Test SAMBALanMan and NT Password Encryption in SambaUser information database
    Reporting Bugs

    Chapter 25. Reporting Bugs

    Chapter 23. Reporting Bugs

    25.1. Introduction

    23.1. Introduction

    The email address for bug reports for stable releases is

    25.2. General info

    23.2. General info

    Before submitting a bug report check your config for silly errors. Look in your log files for obvious messages that tell you that @@ -145,7 +150,9 @@ CLASS="SECT1" >

    25.3. Debug levels

    23.3. Debug levels

    If the bug has anything to do with Samba behaving incorrectly as a server (like refusing to open a file) then the log files will probably @@ -213,7 +220,9 @@ CLASS="SECT1" >

    25.4. Internal errors

    23.4. Internal errors

    If you get a "INTERNAL ERROR" message in your log files it means that Samba got an unexpected signal while running. It is probably a @@ -255,7 +264,9 @@ CLASS="SECT1" >

    25.5. Attaching to a running process

    23.5. Attaching to a running process

    Unfortunately some unixes (in particular some recent linux kernels) refuse to dump a core file if the task has changed uid (which smbd @@ -270,7 +281,9 @@ CLASS="SECT1" >

    25.6. Patches

    23.6. Patches

    The best sort of bug report is one that includes a fix! If you send us patches please use HOWTO Access Samba source code via CVSAccess Samba source code via CVSPrev

    Chapter 20. HOWTO Access Samba source code via CVS

    Chapter 17. Access Samba source code via CVS

    20.1. Introduction

    17.1. Introduction

    Samba is developed in an open environment. Developers use CVS (Concurrent Versioning System) to "checkin" (also known as @@ -99,7 +102,9 @@ CLASS="SECT1" >

    20.2. CVS Access to samba.org

    17.2. CVS Access to samba.org

    The machine samba.org runs a publicly accessible CVS repository for access to the source code of several packages, @@ -110,7 +115,9 @@ CLASS="SECT2" >

    20.2.1. Access via CVSweb

    17.2.1. Access via CVSweb

    You can access the source code via your favourite WWW browser. This allows you to access the contents of @@ -129,7 +136,9 @@ CLASS="SECT2" >

    20.2.2. Access via cvs

    17.2.2. Access via cvs

    You can also access the source code via a normal cvs client. This gives you much more control over you can @@ -247,7 +256,7 @@ WIDTH="33%" ALIGN="left" VALIGN="top" >PrevStoring Samba's User/Machine Account information in an LDAP DirectoryStackable VFS modulesDiagnosing your samba server

    Chapter 26. Diagnosing your samba server

    Chapter 24. Diagnosing your samba server

    26.1. Introduction

    24.1. Introduction

    This file contains a list of tests you can perform to validate your Samba server. It also tells you what the likely cause of the problem @@ -92,7 +95,9 @@ CLASS="SECT1" >

    26.2. Assumptions

    24.2. Assumptions

    In all of the tests it is assumed you have a Samba server called BIGSERVER and a PC called ACLIENT both in workgroup TESTGROUP.

    26.3. Tests

    24.3. Tests

    26.3.1. Test 1

    24.3.1. Test 1

    In the directory in which you store your smb.conf file, run the command "testparm smb.conf". If it reports any errors then your smb.conf @@ -154,7 +163,9 @@ CLASS="SECT2" >

    26.3.2. Test 2

    24.3.2. Test 2

    Run the command "ping BIGSERVER" from the PC and "ping ACLIENT" from the unix box. If you don't get a valid response then your TCP/IP @@ -178,7 +189,9 @@ CLASS="SECT2" >

    26.3.3. Test 3

    24.3.3. Test 3

    Run the command "smbclient -L BIGSERVER" on the unix box. You should get a list of available shares back.

    26.3.4. Test 4

    24.3.4. Test 4

    Run the command "nmblookup -B BIGSERVER __SAMBA__". You should get the IP address of your Samba server back.

    26.3.5. Test 5

    24.3.5. Test 5

    run the command

    26.3.6. Test 6

    24.3.6. Test 6

    Run the command

    26.3.7. Test 7

    24.3.7. Test 7

    Run the command

    26.3.8. Test 8

    24.3.8. Test 8

    On the PC type the command

    26.3.9. Test 9

    24.3.9. Test 9

    Run the command

    26.3.10. Test 10

    24.3.10. Test 10

    Run the command

    26.3.11. Test 11

    24.3.11. Test 11

    From file manager try to browse the server. Your samba server should appear in the browse list of your local workgroup (or the one you @@ -544,7 +573,9 @@ CLASS="SECT1" >

    26.4. Still having troubles?

    24.4. Still having troubles?

    Try the mailing list or newsgroup, or use the ethereal utility to sniff the problem. The official samba mailing list can be reached at diff --git a/docs/htmldocs/domain-security.html b/docs/htmldocs/domain-security.html index 670d96ba5f..fcb40641e4 100644 --- a/docs/htmldocs/domain-security.html +++ b/docs/htmldocs/domain-security.html @@ -2,11 +2,10 @@ Samba as a NT4 domain memberSamba as a NT4 or Win2k domain member

    Chapter 9. Samba as a NT4 domain member

    Chapter 8. Samba as a NT4 or Win2k domain member

    9.1. Joining an NT Domain with Samba 2.2

    8.1. Joining an NT Domain with Samba 3.0

    Assume you have a Samba 2.x server with a NetBIOS name of +>Assume you have a Samba 3.0 server with a NetBIOS name of SERV1 and are joining an NT domain called +> and are joining an or Win2k NT domain called DOM.

    In order to join the domain, first stop all Samba daemons - and run the command:

    root# smbpasswd -j DOM -r DOMPDC - -UAdministrator%password

    as we are joining the domain DOM and the PDC for that domain - (the only machine that has write access to the domain SAM database) - is DOMPDC. The Administrator%password is - the login name and password for an account which has the necessary - privilege to add machines to the domain. If this is successful - you will see the message:

    smbpasswd: Joined domain DOM. -

    in your terminal window. See the smbpasswd(8) man page for more details.

    There is existing development code to join a domain - without having to create the machine trust account on the PDC - beforehand. This code will hopefully be available soon - in release branches as well.

    This command goes through the machine account password - change protocol, then writes the new (random) machine account - password for this Samba server into a file in the same directory - in which an smbpasswd file would be stored - normally :

    /usr/local/samba/private

    In Samba 2.0.x, the filename looks like this:

    <NT DOMAIN NAME>.<Samba - Server Name>.mac

    The .mac suffix stands for machine account - password file. So in our example above, the file would be called:

    DOM.SERV1.mac

    In Samba 2.2, this file has been replaced with a TDB - (Trivial Database) file named secrets.tdb. -

    This file is created and owned by root and is not - readable by any other user. It is the key to the domain-level - security for your system, and should be treated as carefully - as a shadow password file.

    Now, before restarting the Samba daemons you must - edit your Firstly, you must edit your security = domain

    or + security = ads depending on if the PDC is + NT4 or running Active Directory respectivly.

    Next change the password server = *

    This method, which was introduced in Samba 2.0.6, - allows Samba to use exactly the same mechanism that NT does. This +>This method, allows Samba to use exactly the same + mechanism that NT does. This method either broadcasts or uses a WINS database in order to find domain controllers to authenticate against.

    In order to actually join the domain, you must run this + command:

    root# net join -S DOMPDC + -UAdministrator%password

    as we are joining the domain DOM and the PDC for that domain + (the only machine that has write access to the domain SAM database) + is DOMPDC. The Administrator%password is + the login name and password for an account which has the necessary + privilege to add machines to the domain. If this is successful + you will see the message:

    Joined domain DOM. + or Joined 'SERV1' to realm 'MYREALM' +

    in your terminal window. See the net(8) man page for more details.

    This process joins the server to thedomain + without having to create the machine trust account on the PDC + beforehand.

    This command goes through the machine account password + change protocol, then writes the new (random) machine account + password for this Samba server into a file in the same directory + in which an smbpasswd file would be stored - normally :

    /usr/local/samba/private/secrets.tdb

    This file is created and owned by root and is not + readable by any other user. It is the key to the domain-level + security for your system, and should be treated as carefully + as a shadow password file.

    Finally, restart your Samba daemons and get ready for clients to begin using domain security!

    9.2. Samba and Windows 2000 Domains

    8.2. Samba and Windows 2000 Domains

    Many people have asked regarding the state of Samba's ability to participate in a Windows 2000 Domain. Samba 3.0 is able to act as a member server of a Windows -2000 domain operating in mixed or native mode.

    There is much confusion between the circumstances that require a "mixed" mode -Win2k DC and a when this host can be switched to "native" mode. A "mixed" mode -Win2k domain controller is only needed if Windows NT BDCs must exist in the same -domain. By default, a Win2k DC in "native" mode will still support -NetBIOS and NTLMv1 for authentication of legacy clients such as Windows 9x and -NT 4.0. Samba has the same requirements as a Windows NT 4.0 member server.

    The steps for adding a Samba 2.2 host to a Win2k domain are the same as those -for adding a Samba server to a Windows NT 4.0 domain. The only exception is that -the "Server Manager" from NT 4 has been replaced by the "Active Directory Users and -Computers" MMC (Microsoft Management Console) plugin.

    9.3. Why is this better than security = server?

    8.3. Why is this better than security = server?

    Currently, domain security in Samba doesn't free you from having to create local Unix users to represent the users attaching @@ -387,13 +354,7 @@ CLASS="COMMAND" >And finally, acting in the same manner as an NT server authenticating to a PDC means that as part of the authentication reply, the Samba server gets the user identification information such - as the user SID, the list of NT groups the user belongs to, etc. All - this information will allow Samba to be extended in the future into - a mode the developers currently call appliance mode. In this mode, - no local Unix users will be necessary, and Samba will generate Unix - uids and gids from the information passed back from the PDC when a - user is authenticated, making a Samba server truly plug and play - in an NT domain environment. Watch for this code soon.

    + findsmb

    findsmb

    findsmb

    Synopsis

    findsmb [subnet broadcast address]

    [subnet broadcast address]

    DESCRIPTION

    This perl script is part of the Samba suite.

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

    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. + It uses nmblookup(1) + and smbclient(1) + to obtain this information.

    OPTIONS

    nmblookupnmblookup(1) will be called with findsmb     will probe the subnet of the machine where - findsmb is run. This value is passed - to nmblookup as part of the - findsmb(1) + is run. This value is passed to + nmblookup(1) + as part of the -B option.

    EXAMPLES

    -r     option - must be run on a system without nmbd running. + must be run on a system without nmbd(8) running. + If nmbdFor example, running findsmb without - + without -r option set would yield output similar to the following

    IP ADDR         NETBIOS NAME   WORKGROUP/OS/VERSION 
 --------------------------------------------------------------------- 
 192.168.35.10   MINESET-TEST1  [DMVENGR]
@@ -219,17 +223,12 @@ CLASS="COMPUTEROUTPUT"
 192.168.35.78   HERBDHCP1     +[HERB]
 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

    SEE ALSO

    nmbd(8), - smbclient(1) - , and nmblookup(1)nmbd(8), + smbclient(1), and nmblookup(1)

    AUTHOR

    The original Samba man pages were written by Karl Auer. The man page sources were converted to YODL format (another - excellent piece of Open Source software, available at - ftp://ftp.icce.rug.nl/pub/unix/) and updated for the Samba 2.0 - release by Jeremy Allison. The conversion to DocBook for - Samba 2.2 was done by Gerald Carter

    ftp://ftp.icce.rug.nl/pub/unix/) + and updated for the Samba 2.0 release by Jeremy Allison. The conversion to DocBook for + Samba 2.2 was done by Gerald Carter. The conversion to DocBook + XML 4.2 for Samba 3.0 was done by Alexander Bokovoy.

    Group mapping HOWTO

    Chapter 21. Group mapping HOWTO

    Chapter 18. Group mapping HOWTO

    Starting with Samba 3.0 alpha 2, a new group mapping function is available. The @@ -212,7 +213,7 @@ ACCESSKEY="N" WIDTH="33%" ALIGN="left" VALIGN="top" ->HOWTO Access Samba source code via CVSAccess Samba source code via CVS +Creating Group Profiles

    SAMBA Project Documentation
    PrevNext

    Chapter 20. Creating Group Profiles

    20.1. Windows '9x

    You need the Win98 Group Policy Editor to +set Group Profiles up under Windows '9x. It can be found on the Original +full product Win98 installation CD under +tools/reskit/netadmin/poledit. You install this +using the Add/Remove Programs facility and then click on the 'Have Disk' +tab.

    Use the Group Policy Editor to create a policy file that specifies the +location of user profiles and/or the My Documents etc. +stuff. You then save these settings in a file called +Config.POL that needs to be placed in +the root of the [NETLOGON] share. If your Win98 is configured to log onto +the Samba Domain, it will automatically read this file and update the +Win98 registry of the machine that is logging on.

    All of this is covered in the Win98 Resource Kit documentation.

    If you do not do it this way, then every so often Win98 will check the +integrity of the registry and will restore it's settings from the back-up +copy of the registry it stores on each Win98 machine. Hence, you will notice +things changing back to the original settings.

    20.2. Windows NT 4

    Unfortunately, the Resource Kit info is Win NT4/2K version specific.

    Here is a quick guide:

    • On your NT4 Domain Controller, right click on 'My Computer', then +select the tab labelled 'User Profiles'.

    • Select a user profile you want to migrate and click on it.

      I am using the term "migrate" lossely. You can copy a profile to +create a group profile. You can give the user 'Everyone' rights to the +profile you copy this to. That is what you need to do, since your samba +domain is not a member of a trust relationship with your NT4 PDC.

    • Click the 'Copy To' button.

    • In the box labelled 'Copy Profile to' add your new path, eg: +c:\temp\foobar

    • Click on the button labelled 'Change' in the "Permitted to use" box.

    • Click on the group 'Everyone' and then click OK. This closes the +'chose user' box.

    • Now click OK.

    Follow the above for every profile you need to migrate.

    20.2.1. Side bar Notes

    You should obtain the SID of your NT4 domain. You can use smbpasswd to do +this. Read the man page.

    With Samba-3.0.0 alpha code you can import all you NT4 domain accounts +using the net samsync method. This way you can retain your profile +settings as well as all your users.

    20.2.2. Mandatory profiles

    The above method can be used to create mandatory profiles also. To convert +a group profile into a mandatory profile simply locate the NTUser.DAT file +in the copied profile and rename it to NTUser.MAN.

    20.2.3. moveuser.exe

    The W2K professional resource kit has moveuser.exe. moveuser.exe changes +the security of a profile from one user to another. This allows the account +domain to change, and/or the user name to change.

    20.2.4. Get SID

    You can identify the SID by using GetSID.exe from the Windows NT Server 4.0 +Resource Kit.

    Windows NT 4.0 stores the local profile information in the registry under +the following key: +HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileList

    Under the ProfileList key, there will be subkeys named with the SIDs of the +users who have logged on to this computer. (To find the profile information +for the user whose locally cached profile you want to move, find the SID for +the user with the GetSID.exe utility.) Inside of the appropriate user's +subkey, you will see a string value named ProfileImagePath.

    20.3. Windows 2000/XP

    You must first convert the profile from a local profile to a domain +profile on the MS Windows workstation as follows:

    • Log on as the LOCAL workstation administrator.

    • Right click on the 'My Computer' Icon, select 'Properties'

    • Click on the 'User Profiles' tab

    • Select the profile you wish to convert (click on it once)

    • Click on the button 'Copy To'

    • In the "Permitted to use" box, click on the 'Change' button.

    • Click on the 'Look in" area that lists the machine name, when you click +here it will open up a selection box. Click on the domain to which the +profile must be accessible.

      You will need to log on if a logon box opens up. Eg: In the connect +as: MIDEARTH\root, password: mypassword.

    • To make the profile capable of being used by anyone select 'Everyone'

    • Click OK. The Selection box will close.

    • Now click on the 'Ok' button to create the profile in the path you +nominated.

    Done. You now have a profile that can be editted using the samba-3.0.0 +profiles tool.

    Under NT/2K the use of mandotory profiles forces the use of MS Exchange +storage of mail data. That keeps desktop profiles usable.

    • This is a security check new to Windows XP (or maybe only +Windows XP service pack 1). It can be disabled via a group policy in +Active Directory. The policy is:

      "Computer Configuration\Administrative Templates\System\User +Profiles\Do not check for user ownership of Roaming Profile Folders"

      ...and it should be set to "Enabled". +Does the new version of samba have an Active Directory analogue? If so, +then you may be able to set the policy through this.

      If you cannot set group policies in samba, then you may be able to set +the policy locally on each machine. If you want to try this, then do +the following (N.B. I don't know for sure that this will work in the +same way as a domain group policy):

    • On the XP workstation log in with an Administrator account.

    • Click: "Start", "Run"

    • Type: "mmc"

    • Click: "OK"

    • A Microsoft Management Console should appear.

    • Click: File, "Add/Remove Snap-in...", "Add"

    • Double-Click: "Group Policy"

    • Click: "Finish", "Close"

    • Click: "OK"

    • In the "Console Root" window:

    • Expand: "Local Computer Policy", "Computer Configuration",

    • "Administrative Templates", "System", "User Profiles"

    • Double-Click: "Do not check for user ownership of Roaming Profile

    • Folders"

    • Select: "Enabled"

    • Click: OK"

    • Close the whole console. You do not need to save the settings (this +refers to the console settings rather than the policies you have +changed).

    • Reboot

    PrevHomeNext
    Samba performance issuesUpAppendixes
    \ No newline at end of file diff --git a/docs/htmldocs/improved-browsing.html b/docs/htmldocs/improved-browsing.html index 4e9d7f639e..b912cb57e5 100644 --- a/docs/htmldocs/improved-browsing.html +++ b/docs/htmldocs/improved-browsing.html @@ -5,20 +5,19 @@ >Improved browsing in sambaPrevNext

    Chapter 2. Improved browsing in samba

    Chapter 15. Improved browsing in samba

    2.1. Overview of browsing

    15.1. Overview of browsing

    SMB networking provides a mechanism by which clients can access a list of machines in a network, a so-called "browse list". This list @@ -101,7 +104,9 @@ CLASS="SECT1" >

    2.2. Browsing support in samba

    15.2. Browsing support in samba

    Samba now fully supports browsing. The browsing is supported by nmbd and is also controlled by options in the smb.conf file (see smb.conf(5)).

    2.3. Problem resolution

    15.3. Problem resolution

    If something doesn't work then hopefully the log.nmb file will help you track down the problem. Try a debug level of 2 or 3 for finding @@ -176,7 +183,9 @@ CLASS="SECT1" >

    2.4. Browsing across subnets

    15.4. Browsing across subnets

    With the release of Samba 1.9.17(alpha1 and above) Samba has been updated to enable it to support the replication of browse lists @@ -205,7 +214,9 @@ CLASS="SECT2" >

    2.4.1. How does cross subnet browsing work ?

    15.4.1. How does cross subnet browsing work ?

    Cross subnet browsing is a complicated dance, containing multiple moving parts. It has taken Microsoft several years to get the code @@ -415,7 +426,9 @@ CLASS="SECT1" >

    2.5. Setting up a WINS server

    15.5. Setting up a WINS server

    Either a Samba machine or a Windows NT Server machine may be set up as a WINS server. To set a Samba machine to be a WINS server you must @@ -496,7 +509,9 @@ CLASS="SECT1" >

    2.6. Setting up Browsing in a WORKGROUP

    15.6. Setting up Browsing in a WORKGROUP

    To set up cross subnet browsing on a network containing machines in up to be in a WORKGROUP, not an NT Domain you need to set up one @@ -578,7 +593,9 @@ CLASS="SECT1" >

    2.7. Setting up Browsing in a DOMAIN

    15.7. Setting up Browsing in a DOMAIN

    If you are adding Samba servers to a Windows NT Domain then you must not set up a Samba server as a domain master browser. @@ -627,7 +644,9 @@ CLASS="SECT1" >

    2.8. Forcing samba to be the master

    15.8. Forcing samba to be the master

    Who becomes the "master browser" is determined by an election process using broadcasts. Each election packet contains a number of parameters @@ -673,7 +692,9 @@ CLASS="SECT1" >

    2.9. Making samba the domain master

    15.9. Making samba the domain master

    The domain master is responsible for collating the browse lists of multiple subnets so that browsing can occur between subnets. You can @@ -744,7 +765,9 @@ CLASS="SECT1" >

    2.10. Note about broadcast addresses

    15.10. Note about broadcast addresses

    If your network uses a "0" based broadcast address (for example if it ends in a 0) then you will strike problems. Windows for Workgroups @@ -756,7 +779,9 @@ CLASS="SECT1" >

    2.11. Multiple interfaces

    15.11. Multiple interfaces

    Samba now supports machines with multiple network interfaces. If you have multiple interfaces then you will need to use the "interfaces" @@ -779,7 +804,7 @@ WIDTH="33%" ALIGN="left" VALIGN="top" >PrevNextHow to Install and Test SAMBAUnified Logons between Windows NT and UNIX using WinbindUpQuick Cross Subnet Browsing / Cross Workgroup Browsing guideStackable VFS modules

    How to Install and Test SAMBANext

    Chapter 1. How to Install and Test SAMBA

    Chapter 1. How to Install and Test SAMBA

    1.1. Read the man pages

    1.1. Read the man pages

    The man pages distributed with SAMBA contain lots of useful info that will help to get you started. @@ -119,7 +122,9 @@ CLASS="SECT1" >

    1.2. Building the Binaries

    1.2. Building the Binaries

    To do this, first run the program

    1.3. The all important step

    1.3. The all important step

    At this stage you must fetch yourself a coffee or other drink you find stimulating. Getting the rest @@ -231,7 +238,9 @@ CLASS="SECT1" >

    1.4. Create the smb configuration file.

    1.4. Create the smb configuration file.

    There are sample configuration files in the examples subdirectory in the distribution. I suggest you read them @@ -285,7 +294,9 @@ CLASS="SECT1" >

    1.5. Test your config file with +NAME="AEN82" +>1.5. Test your config file with testparm

    1.6. Starting the smbd and nmbd

    1.6. Starting the smbd and nmbd

    You must choose to start smbd and nmbd either as daemons or from

    1.6.1. Starting from inetd.conf

    1.6.1. Starting from inetd.conf

    NOTE; The following will be different if you use NIS or NIS+ to distributed services maps.

    1.6.2. Alternative: starting it as a daemon

    1.6.2. Alternative: starting it as a daemon

    To start the server as a daemon you should create a script something like this one, perhaps calling @@ -508,7 +525,9 @@ CLASS="SECT1" >

    1.7. Try listing the shares available on your +NAME="AEN145" +>1.7. Try listing the shares available on your server

    1.8. Try connecting with the unix client

    1.8. Try connecting with the unix client

    1.9. Try connecting from a DOS, WfWg, Win9x, WinNT, +NAME="AEN170" +>1.9. Try connecting from a DOS, WfWg, Win9x, WinNT, Win2k, OS/2, etc... client

    Try mounting disks. eg:

    1.10. What If Things Don't Work?

    1.10. What If Things Don't Work?

    If nothing works and you start to think "who wrote this pile of trash" then I suggest you do step 2 again (and @@ -676,7 +701,9 @@ CLASS="SECT2" >

    1.10.1. Diagnosing Problems

    1.10.1. Diagnosing Problems

    If you have installation problems then go to the

    1.10.2. Scope IDs

    1.10.2. Scope IDs

    By default Samba uses a blank scope ID. This means all your windows boxes must also have a blank scope ID. @@ -705,7 +734,9 @@ CLASS="SECT2" >

    1.10.3. Choosing the Protocol Level

    1.10.3. Choosing the Protocol Level

    The SMB protocol has many dialects. Currently Samba supports 5, called CORE, COREPLUS, LANMAN1, @@ -744,7 +775,9 @@ CLASS="SECT2" >

    1.10.4. Printing from UNIX to a Client PC

    1.10.4. Printing from UNIX to a Client PC

    To use a printer that is available via a smb-based server from a unix host with LPR you will need to compile the @@ -763,7 +796,9 @@ CLASS="SECT2" >

    1.10.5. Locking

    1.10.5. Locking

    One area which sometimes causes trouble is locking.

    1.10.6. Mapping Usernames

    1.10.6. Mapping Usernames

    If you have different usernames on the PCs and the unix server then take a look at the "username map" option. @@ -863,7 +900,7 @@ WIDTH="33%" ALIGN="right" VALIGN="top" >NextImproved browsing in sambaQuick Cross Subnet Browsing / Cross Workgroup Browsing guide

    Integrating MS Windows networks with Samba

    Chapter 10. Integrating MS Windows networks with Samba

    Chapter 9. Integrating MS Windows networks with Samba

    10.1. Agenda

    9.1. Agenda

    To identify the key functional mechanisms of MS Windows networking to enable the deployment of Samba as a means of extending and/or @@ -144,7 +147,9 @@ CLASS="SECT1" >

    10.2. Name Resolution in a pure Unix/Linux world

    9.2. Name Resolution in a pure Unix/Linux world

    The key configuration files covered in this section are:

    10.2.1. 9.2.1. /etc/hosts

    10.2.2. 9.2.2. /etc/resolv.conf

    10.2.3. 9.2.3. /etc/host.conf

    10.2.4. 9.2.4. /etc/nsswitch.conf

    10.3. Name resolution as used within MS Windows networking

    9.3. Name resolution as used within MS Windows networking

    MS Windows networking is predicated about the name each machine is given. This name is known variously (and inconsistently) as @@ -413,16 +428,16 @@ the client/server.

    	Unique NetBIOS Names:
-		MACHINENAME<00>	= Server Service is running on MACHINENAME
-		MACHINENAME<03> = Generic Machine Name (NetBIOS name)
-		MACHINENAME<20> = LanMan Server service is running on MACHINENAME
-		WORKGROUP<1b> = Domain Master Browser
+		MACHINENAME<00>	= Server Service is running on MACHINENAME
+		MACHINENAME<03> = Generic Machine Name (NetBIOS name)
+		MACHINENAME<20> = LanMan Server service is running on MACHINENAME
+		WORKGROUP<1b> = Domain Master Browser
 
 	Group Names:
-		WORKGROUP<03> = Generic Name registered by all members of WORKGROUP
-		WORKGROUP<1c> = Domain Controllers / Netlogon Servers
-		WORKGROUP<1d> = Local Master Browsers
-		WORKGROUP<1e> = Internet Name Resolvers

    It should be noted that all NetBIOS machines register their own @@ -441,7 +456,7 @@ be needed. An example of this is what happens when an MS Windows client wants to locate a domain logon server. It find this service and the IP address of a server that provides it by performing a lookup (via a NetBIOS broadcast) for enumeration of all machines that have -registered the name type *<1c>. A logon request is then sent to each +registered the name type *<1c>. A logon request is then sent to each IP address that is returned in the enumerated list of IP addresses. Which ever machine first replies then ends up providing the logon services.

    10.3.1. The NetBIOS Name Cache

    9.3.1. The NetBIOS Name Cache

    All MS Windows machines employ an in memory buffer in which is stored the NetBIOS names and IP addresses for all external @@ -501,7 +518,9 @@ CLASS="SECT2" >

    10.3.2. The LMHOSTS file

    9.3.2. The LMHOSTS file

    This file is usually located in MS Windows NT 4.0 or 2000 in

    10.3.3. HOSTS file

    9.3.3. HOSTS file

    This file is usually located in MS Windows NT 4.0 or 2000 in

    10.3.4. DNS Lookup

    9.3.4. DNS Lookup

    This capability is configured in the TCP/IP setup area in the network configuration facility. If enabled an elaborate name resolution sequence @@ -640,7 +663,9 @@ CLASS="SECT2" >

    10.3.5. WINS Lookup

    9.3.5. WINS Lookup

    A WINS (Windows Internet Name Server) service is the equivaent of the rfc1001/1002 specified NBNS (NetBIOS Name Server). A WINS server stores @@ -681,7 +706,9 @@ CLASS="SECT1" >

    10.4. How browsing functions and how to deploy stable and +NAME="AEN1643" +>9.4. How browsing functions and how to deploy stable and dependable browsing using Samba

    As stated above, MS Windows machines register their NetBIOS names @@ -746,7 +773,9 @@ CLASS="SECT1" >

    10.5. MS Windows security options and how to configure +NAME="AEN1653" +>9.5. MS Windows security options and how to configure Samba for seemless integration

    MS Windows clients may use encrypted passwords as part of a @@ -881,7 +910,9 @@ CLASS="SECT2" >

    10.5.1. Use MS Windows NT as an authentication server

    9.5.1. Use MS Windows NT as an authentication server

    This method involves the additions of the following parameters in the smb.conf file:

    10.5.2. Make Samba a member of an MS Windows NT security domain

    9.5.2. Make Samba a member of an MS Windows NT security domain

    This method involves additon of the following paramters in the smb.conf file:

    10.5.3. Configure Samba as an authentication server

    9.5.3. Configure Samba as an authentication server

    This mode of authentication demands that there be on the Unix/Linux system both a Unix style account as well as an @@ -1011,7 +1046,9 @@ CLASS="SECT3" >

    10.5.3.1. Users

    9.5.3.1. Users

    A user account that may provide a home directory should be created. The following Linux system commands are typical of @@ -1032,7 +1069,9 @@ CLASS="SECT3" >

    10.5.3.2. MS Windows NT Machine Accounts

    9.5.3.2. MS Windows NT Machine Accounts

    These are required only when Samba is used as a domain controller. Refer to the Samba-PDC-HOWTO for more details.

    10.6. Conclusions

    9.6. Conclusions

    Samba provides a flexible means to operate as...

    General installation

    Introduction

    This part contains general info on how to install samba @@ -206,155 +209,199 @@ HREF="install.html#AEN219" >

    • 2. Improved browsing in sambaQuick Cross Subnet Browsing / Cross Workgroup Browsing guide
    2.1. Overview of browsingDiscussion
    2.2. Browsing support in sambaUse of the "Remote Announce" parameter
    2.3. Problem resolutionUse of the "Remote Browse Sync" parameter
    2.4. Browsing across subnets
    2.4.1. How does cross subnet browsing work ?Use of WINS
    2.5. Setting up a WINS serverDo NOT use more than one (1) protocol on MS Windows machines
    2.6. Setting up Browsing in a WORKGROUPName Resolution Order
    2.7. Setting up Browsing in a DOMAIN3. User information database
    2.8. Forcing samba to be the master3.1. Introduction
    2.9. Making samba the domain master3.2. Important Notes About Security
    2.10. Note about broadcast addresses3.2.1. Advantages of SMB Encryption
    2.11. Multiple interfaces3.2.2. Advantages of non-encrypted passwords
    3. Quick Cross Subnet Browsing / Cross Workgroup Browsing guide3.3. The smbpasswd Command
    3.4. Plain text
    3.5. TDB
    3.6. LDAP
    3.1. Discussion3.6.1. Introduction
    3.2. Use of the "Remote Announce" parameter3.6.2. Introduction
    3.3. Use of the "Remote Browse Sync" parameter3.6.3. Supported LDAP Servers
    3.4. Use of WINS3.6.4. Schema and Relationship to the RFC 2307 posixAccount
    3.5. Do NOT use more than one (1) protocol on MS Windows machines3.6.5. Configuring Samba with LDAP
    3.6. Name Resolution Order3.6.6. Accounts and Groups management
    3.6.7. Security and sambaAccount
    3.6.8. LDAP specials attributes for sambaAccounts
    3.6.9. Example LDIF Entries for a sambaAccount
    4. LanMan and NT Password Encryption in Samba3.7. MySQL
    4.1. Introduction3.7.1. Building
    4.2. Important Notes About Security3.7.2. Creating the database
    4.2.1. Advantages of SMB Encryption3.7.3. Configuring
    4.2.2. Advantages of non-encrypted passwords3.7.4. Using plaintext passwords or encrypted password
    3.7.5. Getting non-column data from the table
    4.3. The smbpasswd Command3.8. Passdb XML plugin
    3.8.1. Building
    3.8.2. Usage
    lmhosts

    lmhosts

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

    DESCRIPTION

    This file is part of the SambaThis file is part of the Samba(7) suite.

    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 :

      An example follows :

      An example follows:

      #
@@ -118,7 +121,6 @@ CLASS="PROGRAMLISTING"
 192.9.200.20	NTSERVER#20
 192.9.200.21	SAMBASERVER

      Contains three IP to NetBIOS name mappings. The first and third will be returned for any queries for the names "TESTPC" @@ -133,58 +135,57 @@ CLASS="PROGRAMLISTING" CLASS="FILENAME" >lmhosts file - is in the same directory as the - smb.conf(5)>smb.conf(5) file.

      VERSION

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

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

      SEE ALSO

      smbclient(1) - , smb.conf(5), and smbpasswd(8)smbclient(1), smb.conf(5), and smbpasswd(8)

      AUTHOR

      ftp://ftp.icce.rug.nl/pub/unix/) and updated for the Samba 2.0 release by Jeremy Allison. The conversion to DocBook for - Samba 2.2 was done by Gerald Carter

      Hosting a Microsoft Distributed File System tree on Samba

      Chapter 13. Hosting a Microsoft Distributed File System tree on Samba

      Chapter 12. Hosting a Microsoft Distributed File System tree on Samba

      13.1. Instructions

      12.1. Instructions

      The Distributed File System (or Dfs) provides a means of separating the logical view of files and directories that users @@ -226,7 +229,9 @@ CLASS="SECT2" >

      13.1.1. Notes

      12.1.1. Notes

        net

        net

        DESCRIPTION

        This tool is part of the SambaThis tool is part of the Samba(7) suite.

        The samba net utility is meant to work just like the net utility @@ -60,7 +62,7 @@ TARGET="_top" >

        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. +> Sets target workgroup or domain. You have to specify + either this option or the IP address or the name of a server.

        -I ip-address

        IP address of target server to use. You have to specify either this option or a target workgroup or a target server. +> IP address of target server to use. You have to + specify either this option or a target workgroup or a target server.

        -S server

        Name of target server. You should specify either this option or a target workgroup or a target IP address. +> Name of target server. You should specify either + this option or a target workgroup or a target IP address.

        TIME

        SYSTEM

        Displays the time on the remote server in a format ready for /bin/date +> Displays the time on the remote server in a format ready for /bin/date

        Tries to set the date and time of the local server to that on - the remote server using /bin/date. + the remote server using /bin/date.

        RPC

      USER ADD <name> [password] [-F user flags] [misc. options
      USER ADD <name> [password] [-F user flags] [misc. options]

      Add specified user @@ -373,7 +384,7 @@ CLASS="VARIABLELIST" >

      VERSION

      AUTHOR

      + nmbd

      nmbd

      nmbd

      Synopsis

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

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

      DESCRIPTION

      This program is part of the Samba suite.

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

      -n option (see OPTIONS below). Thus nmbd to respond on can be set - via parameters in the smb.conf(5)smb.conf(5) configuration file.

      OPTIONS

      nmbd       also logs to standard - output, as if the -S-S       parameter had been given.

      .

      -H <filename>
      -H <filename>

      NetBIOS lmhosts file. The lmhosts @@ -242,28 +253,39 @@ CLASS="COMMAND" resolution mechanism name resolve order described in smb.conf(5)name resolve + order - to resolve any NetBIOS name queries needed by the server. Note - that the contents of this file are described in smb.conf(5) to resolve any + NetBIOS name queries needed by the server. Note + that the contents of this file are NOT used by nmbd to answer any name queries. Adding a line to this file affects name NetBIOS resolution - from this host ONLY.

      The default path to this file is compiled into @@ -278,17 +300,14 @@ CLASS="FILENAME" > or /etc/lmhosts. See the - lmhosts(5) - man page for details on the contents of this file.

      /etc/samba/lmhosts      . See the lmhosts(5) man page for details on the contents of this file.

      -V
      .

      -d <debug level>
      -d <debug level>

      debuglevel is an integer @@ -325,19 +344,23 @@ CLASS="COMMAND" the log level - parameter in the smb.conf(5)log level + parameter in the smb.conf(5) file.

      -l <log directory>
      -l <log directory>

      The -l parameter specifies a directory @@ -357,9 +380,12 @@ CLASS="FILENAME" /var/log/log.nmb. . Beware: If the directory specified does not exist,

      -n <primary NetBIOS name>
      -n <primary NetBIOS name>

      This option allows you to override @@ -377,24 +403,31 @@ CLASS="COMMAND" to setting the NetBIOS name parameter in the - smb.confNetBIOS + name parameter in the smb.conf(5) file. However, a command line setting will take precedence over settings in - smb.confsmb.conf(5).

      -p <UDP port number>
      -p <UDP port number>

      UDP port number is a positive integer value. @@ -407,7 +440,7 @@ CLASS="COMMAND" won't need help!

      -s <configuration file>
      -s <configuration file>

      The default configuration file name @@ -418,13 +451,12 @@ CLASS="FILENAME" this may be changed when Samba is autoconfigured.

      The file specified contains the configuration details - required by the server. See smb.conf(5)smb.conf(5) for more information.

      FILES

      meta-daemon, this file must contain suitable startup information for the meta-daemon. See the UNIX_INSTALL.htmlinstall document for details.

      If running the server as a daemon at startup, this file will need to contain an appropriate startup sequence for the server. See the UNIX_INSTALL.html"How to Install and Test SAMBA" document for details.

      UNIX_INSTALL.html"How to Install and Test SAMBA" document for details.

      This is the default location of the - smb.conf - server configuration file. Other common places that systems +>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/smb.conf/etc/samba/smb.conf.

      When run as a WINS server (see the wins supportwins support - parameter in the smb.conf(5)smb.conf(5) man page), If nmbd is acting as a is acting as a browse master (see the local masterlocal master - parameter in the smb.conf(5) man page, - smb.conf(5) man page, nmbd @@ -590,7 +635,7 @@ CLASS="FILENAME" >

      SIGNALS

      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 log.nmb       file.

      The debug log level of nmbd may be raised or lowered using - smbcontrol(1) - (SIGUSR[1|2] signals are no longer used in Samba 2.2). This is - to allow transient problems to be diagnosed, whilst still running +>The debug log level of nmbd may be raised or lowered + 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

      SEE ALSO

      inetd(8), smbd(8), - smb.conf(5) - , smbclient(1) - , testparm(1), testprns(1), and the Internet RFC's - inetd(8), smbd(8), smb.conf(5), smbclient(1), testparm(1), testprns(1), and the Internet + RFC's rfc1001.txt,

      AUTHOR

      The original Samba man pages were written by Karl Auer. The man page sources were converted to YODL format (another - excellent piece of Open Source software, available at - ftp://ftp.icce.rug.nl/pub/unix/) and updated for the Samba 2.0 release by Jeremy Allison. The conversion to DocBook for - Samba 2.2 was done by Gerald Carter

      nmblookup

      DESCRIPTION

      This tool is part of the SambaThis tool is part of the Samba(7) suite.

      OPTIONS

      nmbd(8) - daemon is running on this machine it also binds to this port. + in addition, if the nmbd(8) daemon is running on this machine it also binds to this port.

      parameter of the smb.conf (5) parameter of the smb.conf(5) file.

      EXAMPLES

      nslookup       is - used to query DNS servers). To query a WINS server, - nmblookup must be called like this:

      + must be called like this:

      VERSION

      SEE ALSO

      nmbd(8), - samba(7), and smb.conf(5) -

      nmbd(8), samba(7), and smb.conf(5).

      AUTHOR

      The original Samba man pages were written by Karl Auer. The man page sources were converted to YODL format (another - excellent piece of Open Source software, available at - ftp://ftp.icce.rug.nl/pub/unix/) and updated for the Samba 2.0 release by Jeremy Allison. The conversion to DocBook for - Samba 2.2 was done by Gerald Carter

      Optional configuration

      Introduction

      Samba has several features that you might want or might not want to use. The chapters in this @@ -91,51 +94,51 @@ CLASS="TOC" >Table of Contents

      10. 9. Integrating MS Windows networks with Samba
      10.1. 9.1. Agenda
      10.2. 9.2. Name Resolution in a pure Unix/Linux world
      10.2.1. 9.2.1. /etc/hosts
      10.2.2. 9.2.2. /etc/resolv.conf
      10.2.3. 9.2.3. /etc/host.conf
      10.2.4. 9.2.4. /etc/nsswitch.conf
      10.3. 9.3. Name resolution as used within MS Windows networking
      10.3.1. 9.3.1. The NetBIOS Name Cache
      10.3.2. 9.3.2. The LMHOSTS file
      10.3.3. 9.3.3. HOSTS file
      10.3.4. 9.3.4. DNS Lookup
      10.3.5. 9.3.5. WINS Lookup
      10.4. 9.4. How browsing functions and how to deploy stable and dependable browsing using Samba
      10.5. 9.5. MS Windows security options and how to configure Samba for seemless integration
      10.5.1. 9.5.1. Use MS Windows NT as an authentication server
      10.5.2. 9.5.2. Make Samba a member of an MS Windows NT security domain
      10.5.3. 9.5.3. Configure Samba as an authentication server
      10.6. 9.6. Conclusions
      11. 10. UNIX Permission Bits and Windows NT Access Control Lists
      11.1. 10.1. Viewing and changing UNIX permissions using the NT security dialogs
      11.2. 10.2. How to view file security on a Samba share
      11.3. 10.3. Viewing file ownership
      11.4. 10.4. Viewing file or directory permissions
      11.4.1. 10.4.1. File Permissions
      11.4.2. 10.4.2. Directory Permissions
      11.5. 10.5. Modifying file or directory permissions
      11.6. 10.6. Interaction with the standard Samba create mask parameters
      11.7. 10.7. Interaction with the standard Samba file attribute mapping
      12. 11. Configuring PAM for distributed but centrally managed authentication
      12.1. 11.1. Samba and PAM
      12.2. 11.2. Distributed Authentication
      12.3. 11.3. PAM Configuration in smb.conf
      13. 12. Hosting a Microsoft Distributed File System tree on Samba
      13.1. 12.1. Instructions
      13.1.1. 12.1.1. Notes
      14. 13. Printing Support
      14.1. 13.1. Introduction
      14.2. 13.2. Configuration
      14.2.1. 13.2.1. Creating [print$]
      14.2.2. 13.2.2. Setting Drivers for Existing Printers
      14.2.3. 13.2.3. Support a large number of printers
      14.2.4. 13.2.4. Adding New Printers via the Windows NT APW
      14.2.5. 13.2.5. Samba and Printer Ports
      14.3. 13.3. The Imprints Toolset
      14.3.1. 13.3.1. What is Imprints?
      14.3.2. 13.3.2. Creating Printer Driver Packages
      14.3.3. 13.3.3. The Imprints server
      14.3.4. 13.3.4. The Installation Client
      14.4. 13.4. Diagnosis
      14.4.1. 13.4.1. Introduction
      14.4.2. 13.4.2. Debugging printer problems
      14.4.3. 13.4.3. What printers do I have?
      14.4.4. 13.4.4. Setting up printcap and print servers
      14.4.5. 13.4.5. Job sent, no output
      14.4.6. 13.4.6. Job sent, strange output
      14.4.7. 13.4.7. Raw PostScript printed
      14.4.8. 13.4.8. Advanced Printing
      14.4.9. 13.4.9. Real debugging
      15. 14. Unified Logons between Windows NT and UNIX using Winbind
      15.1. 14.1. Abstract
      15.2. 14.2. Introduction
      15.3. 14.3. What Winbind Provides
      15.3.1. 14.3.1. Target Uses
      15.4. 14.4. How Winbind Works
      15.4.1. 14.4.1. Microsoft Remote Procedure Calls
      15.4.2. 14.4.2. Microsoft Active Directory Services
      14.4.3. Name Service Switch
      15.4.3. 14.4.4. Pluggable Authentication Modules
      15.4.4. 14.4.5. User and Group ID Allocation
      15.4.5. 14.4.6. Result Caching
      15.5. 14.5. Installation and Configuration
      15.5.1. 14.5.1. Introduction
      15.5.2. 14.5.2. Requirements
      15.5.3. 14.5.3. Testing Things Out
      15.6. 14.6. Limitations
      15.7. 14.7. Conclusion
      16. Passdb MySQL plugin15. Improved browsing in samba
      16.1. Building15.1. Overview of browsing
      16.2. Configuring15.2. Browsing support in samba
      16.3. Using plaintext passwords or encrypted password15.3. Problem resolution
      16.4. Getting non-column data from the table15.4. Browsing across subnets
      15.4.1. How does cross subnet browsing work ?
      17. Passdb XML plugin15.5. Setting up a WINS server
      17.1. Building15.6. Setting up Browsing in a WORKGROUP
      17.2. Usage15.7. Setting up Browsing in a DOMAIN
      15.8. Forcing samba to be the master
      15.9. Making samba the domain master
      15.10. Note about broadcast addresses
      15.11. Multiple interfaces
      18. 16. Stackable VFS modules
      18.1. 16.1. Introduction and configuration
      18.2. 16.2. Included modules
      18.2.1. 16.2.1. audit
      18.2.2. 16.2.2. recycle
      18.2.3. 16.2.3. netatalk
      18.3. 16.3. VFS modules available elsewhere
      18.3.1. 16.3.1. DatabaseFS
      18.3.2. 16.3.2. vscan
      19. Storing Samba's User/Machine Account information in an LDAP Directory
      19.1. Purpose
      19.2. Introduction
      19.3. Supported LDAP Servers
      19.4. Schema and Relationship to the RFC 2307 posixAccount
      19.5. Configuring Samba with LDAP
      19.5.1. OpenLDAP configuration
      19.5.2. Configuring Samba
      19.6. Accounts and Groups management
      19.7. Security and sambaAccount
      19.8. LDAP specials attributes for sambaAccounts
      19.9. Example LDIF Entries for a sambaAccount
      19.10. Comments
      20. 17. HOWTO Access Samba source code via CVSAccess Samba source code via CVS
      20.1. 17.1. Introduction
      20.2. 17.2. CVS Access to samba.org
      20.2.1. 17.2.1. Access via CVSweb
      20.2.2. 17.2.2. Access via cvs
      21. 18. Group mapping HOWTO
      22. 19. Samba performance issues
      22.1. 19.1. Comparisons
      22.2. 19.2. Socket options
      22.3. 19.3. Read size
      22.4. 19.4. Max xmit
      22.5. 19.5. Log level
      22.6. 19.6. Read raw
      22.7. 19.7. Write raw
      22.8. 19.8. Slow Clients
      22.9. 19.9. Slow Logins
      22.10. 19.10. Client tuning
      20. Creating Group Profiles
      20.1. Windows '9x
      20.2. Windows NT 4
      20.2.1. Side bar Notes
      20.2.2. Mandatory profiles
      20.2.3. moveuser.exe
      20.2.4. Get SID
      20.3. Windows 2000/XP
      Samba as a NT4 domain memberSamba as a NT4 or Win2k domain memberSamba and other CIFS clients

      Chapter 24. Samba and other CIFS clients

      Chapter 22. Samba and other CIFS clients

      This chapter contains client-specific information.

      24.1. Macintosh clients?

      22.1. Macintosh clients?

      Yes.

      24.2. OS2 Client

      22.2. OS2 Client

      24.2.1. How can I configure OS/2 Warp Connect or +NAME="AEN3322" +>22.2.1. How can I configure OS/2 Warp Connect or OS/2 Warp 4 as a client for Samba?

      A more complete answer to this question can be @@ -188,7 +195,9 @@ CLASS="SECT2" >

      24.2.2. How can I configure OS/2 Warp 3 (not Connect), +NAME="AEN3337" +>22.2.2. How can I configure OS/2 Warp 3 (not Connect), OS/2 1.2, 1.3 or 2.x for Samba?

      You can use the free Microsoft LAN Manager 2.2c Client @@ -230,7 +239,9 @@ CLASS="SECT2" >

      24.2.3. Are there any other issues when OS/2 (any version) +NAME="AEN3346" +>22.2.3. Are there any other issues when OS/2 (any version) is used as a client?

      When you do a NET VIEW or use the "File and Print @@ -250,7 +261,9 @@ CLASS="SECT2" >

      24.2.4. How do I get printer driver download working +NAME="AEN3350" +>22.2.4. How do I get printer driver download working for OS/2 clients?

      First, create a share called [PRINTDRV] that is @@ -299,13 +312,17 @@ CLASS="SECT1" >

      24.3. Windows for Workgroups

      22.3. Windows for Workgroups

      24.3.1. Use latest TCP/IP stack from Microsoft

      22.3.1. Use latest TCP/IP stack from Microsoft

      Use the latest TCP/IP stack from microsoft if you use Windows for workgroups.

      24.3.2. Delete .pwl files after password change

      22.3.2. Delete .pwl files after password change

      WfWg does a lousy job with passwords. I find that if I change my password on either the unix box or the PC the safest thing to do is to @@ -343,7 +362,9 @@ CLASS="SECT2" >

      24.3.3. Configure WfW password handling

      22.3.3. Configure WfW password handling

      There is a program call admincfg.exe on the last disk (disk 8) of the WFW 3.11 disk set. To install it @@ -360,7 +381,9 @@ CLASS="SECT2" >

      24.3.4. Case handling of passwords

      22.3.4. Case handling of passwords

      Windows for Workgroups uppercases the password before sending it to the server. Unix passwords can be case-sensitive though. Check the

      24.4. Windows '95/'98

      22.4. Windows '95/'98

      When using Windows 95 OEM SR2 the following updates are recommended where Samba is being used. Please NOTE that the above change will affect you once these @@ -423,7 +448,9 @@ CLASS="SECT1" >

      24.5. Windows 2000 Service Pack 2

      22.5. Windows 2000 Service Pack 2

      There are several annoyances with Windows 2000 SP2. One of which diff --git a/docs/htmldocs/pam.html b/docs/htmldocs/pam.html index ba2bf6c922..a64de2a1b4 100644 --- a/docs/htmldocs/pam.html +++ b/docs/htmldocs/pam.html @@ -6,8 +6,7 @@ managed authentication

      Chapter 12. Configuring PAM for distributed but centrally +NAME="PAM" +>Chapter 11. Configuring PAM for distributed but centrally managed authentication

      12.1. Samba and PAM

      11.1. Samba and PAM

      A number of Unix systems (eg: Sun Solaris), as well as the xxxxBSD family and Linux, now utilize the Pluggable Authentication @@ -293,7 +296,9 @@ CLASS="SECT1" >

      12.2. Distributed Authentication

      11.2. Distributed Authentication

      The astute administrator will realize from this that the combination of

      12.3. PAM Configuration in smb.conf

      11.3. PAM Configuration in smb.conf

      There is an option in smb.conf called +User information database

      SAMBA Project Documentation
      PrevNext

      Chapter 3. User information database

      3.1. Introduction

      Old windows clients send plain text passwords over the wire. + Samba can check these passwords by crypting them and comparing them + to the hash stored in the unix user database. +

      Newer windows clients send encrypted passwords (so-called + Lanman and NT hashes) over + the wire, instead of plain text passwords. The newest clients + will only send encrypted passwords and refuse to send plain text + passwords, unless their registry is tweaked. +

      These passwords can't be converted to unix style encrypted + passwords. Because of that you can't use the standard unix + user database, and you have to store the Lanman and NT hashes + somewhere else.

      Next to a differently encrypted passwords, + windows also stores certain data for each user + that is not stored in a unix user database, e.g. + workstations the user may logon from, the location where his/her + profile is stored, etc. + Samba retrieves and stores this information using a "passdb backend". + Commonly + available backends are LDAP, plain text file, MySQL and nisplus. + For more information, see the documentation about the + passdb backend = parameter. +

      3.2. Important Notes About Security

      The unix and SMB password encryption techniques seem similar + on the surface. This similarity is, however, only skin deep. The unix + scheme typically sends clear text passwords over the network when + logging in. This is bad. The SMB encryption scheme never sends the + cleartext password over the network but it does store the 16 byte + hashed values on disk. This is also bad. Why? Because the 16 byte hashed + values are a "password equivalent". You cannot derive the user's + password from them, but they could potentially be used in a modified + client to gain access to a server. This would require considerable + technical knowledge on behalf of the attacker but is perfectly possible. + You should thus treat the data stored in whatever + passdb backend you use (smbpasswd file, ldap, mysql) as though it contained the + cleartext passwords of all your users. Its contents must be kept + secret, and the file should be protected accordingly.

      Ideally we would like a password scheme which neither requires + plain text passwords on the net or on disk. Unfortunately this + is not available as Samba is stuck with being compatible with + other SMB systems (WinNT, WfWg, Win95 etc).

      Note that Windows NT 4.0 Service pack 3 changed the + default for permissible authentication so that plaintext + passwords are never sent over the wire. + The solution to this is either to switch to encrypted passwords + with Samba or edit the Windows NT registry to re-enable plaintext + passwords. See the document WinNT.txt for details on how to do + this.

      Other Microsoft operating systems which also exhibit + this behavior includes

      MS DOS Network client 3.0 with + the basic network redirector installed
      Windows 95 with the network redirector + update installed
      Windows 98 [se]
      Windows 2000

      Note :All current release of + Microsoft SMB/CIFS clients support authentication via the + SMB Challenge/Response mechanism described here. Enabling + clear text authentication does not disable the ability + of the client to participate in encrypted authentication.

      3.2.1. Advantages of SMB Encryption

      plain text passwords are not passed across + the network. Someone using a network sniffer cannot just + record passwords going to the SMB server.
      WinNT doesn't like talking to a server + that isn't using SMB encrypted passwords. It will refuse + to browse the server if the server is also in user level + security mode. It will insist on prompting the user for the + password on each connection, which is very annoying. The + only things you can do to stop this is to use SMB encryption. +

      3.2.2. Advantages of non-encrypted passwords

      plain text passwords are not kept + on disk.
      uses same password file as other unix + services such as login and ftp
      you are probably already using other + services (such as telnet and ftp) which send plain text + passwords over the net, so sending them for SMB isn't + such a big deal.

      3.3. The smbpasswd Command

      The smbpasswd utility is a utility similar to the + passwd or yppasswd programs. + It maintains the two 32 byte password fields + in the passdb backend.

      smbpasswd works in a client-server mode + where it contacts the local smbd to change the user's password on its + behalf. This has enormous benefits - as follows.

      smbpasswd has the capability + to change passwords on Windows NT servers (this only works when + the request is sent to the NT Primary Domain Controller if you + are changing an NT Domain user's password).

      To run smbpasswd as a normal user just type :

      $ smbpasswd

      Old SMB password: <type old value here - + or hit return if there was no old password>

      New SMB Password: <type new value> +

      Repeat New SMB Password: <re-type new value +

      If the old value does not match the current value stored for + that user, or the two new values do not match each other, then the + password will not be changed.

      If invoked by an ordinary user it will only allow the user + to change his or her own Samba password.

      If run by the root user smbpasswd may take an optional + argument, specifying the user name whose SMB password you wish to + change. Note that when run as root smbpasswd does not prompt for + or check the old password value, thus allowing root to set passwords + for users who have forgotten their passwords.

      smbpasswd is designed to work in the same way + and be familiar to UNIX users who use the passwd or + yppasswd commands.

      For more details on using smbpasswd refer + to the man page which will always be the definitive reference.

      3.4. Plain text

      Older versions of samba retrieved user information from the unix user database +and eventually some other fields from the file /etc/samba/smbpasswd +or /etc/smbpasswd. When password encryption is disabled, no +data is stored at all.

      3.5. TDB

      Samba can also store the user data in a "TDB" (Trivial Database). Using this backend +doesn't require any additional configuration. This backend is recommended for new installations who +don't require LDAP.

      3.6. LDAP

      3.6.1. Introduction

      This document describes how to use an LDAP directory for storing Samba user +account information traditionally stored in the smbpasswd(5) file. It is +assumed that the reader already has a basic understanding of LDAP concepts +and has a working directory server already installed. For more information +on LDAP architectures and Directories, please refer to the following sites.

      Note that O'Reilly Publishing is working on +a guide to LDAP for System Administrators which has a planned release date of +early summer, 2002.

      Two additional Samba resources which may prove to be helpful are

      • The Samba-PDC-LDAP-HOWTO + maintained by Ignacio Coupeau.

      • The NT migration scripts from IDEALX that are + geared to manage users and group in such a Samba-LDAP Domain Controller configuration. +

      3.6.2. Introduction

      Traditionally, when configuring "encrypt +passwords = yes" in Samba's smb.conf file, user account +information such as username, LM/NT password hashes, password change times, and account +flags have been stored in the smbpasswd(5) file. There are several +disadvantages to this approach for sites with very large numbers of users (counted +in the thousands).

      • The first is that all lookups must be performed sequentially. Given that +there are approximately two lookups per domain logon (one for a normal +session connection such as when mapping a network drive or printer), this +is a performance bottleneck for lareg sites. What is needed is an indexed approach +such as is used in databases.

      • The second problem is that administrators who desired to replicate a +smbpasswd file to more than one Samba server were left to use external +tools such as rsync(1) and ssh(1) +and wrote custom, in-house scripts.

      • And finally, the amount of information which is stored in an +smbpasswd entry leaves no room for additional attributes such as +a home directory, password expiration time, or even a Relative +Identified (RID).

      As a result of these defeciencies, a more robust means of storing user attributes +used by smbd was developed. The API which defines access to user accounts +is commonly referred to as the samdb interface (previously this was called the passdb +API, and is still so named in the CVS trees). In Samba 2.2.3, enabling support +for a samdb backend (e.g. --with-ldapsam or +--with-tdbsam) requires compile time support.

      When compiling Samba to include the --with-ldapsam autoconf +option, smbd (and associated tools) will store and lookup user accounts in +an LDAP directory. In reality, this is very easy to understand. If you are +comfortable with using an smbpasswd file, simply replace "smbpasswd" with +"LDAP directory" in all the documentation.

      There are a few points to stress about what the --with-ldapsam +does not provide. The LDAP support referred to in the this documentation does not +include:

      • A means of retrieving user account information from + an Windows 2000 Active Directory server.

      • A means of replacing /etc/passwd.

      The second item can be accomplished by using LDAP NSS and PAM modules. LGPL +versions of these libraries can be obtained from PADL Software +(http://www.padl.com/). However, +the details of configuring these packages are beyond the scope of this document.

      3.6.3. Supported LDAP Servers

      The LDAP samdb code in 2.2.3 has been developed and tested using the OpenLDAP +2.0 server and client libraries. The same code should be able to work with +Netscape's Directory Server and client SDK. However, due to lack of testing +so far, there are bound to be compile errors and bugs. These should not be +hard to fix. If you are so inclined, please be sure to forward all patches to +samba-patches@samba.org and +jerry@samba.org.

      3.6.4. Schema and Relationship to the RFC 2307 posixAccount

      Samba 3.0 includes the necessary schema file for OpenLDAP 2.0 in +examples/LDAP/samba.schema. The sambaAccount objectclass is given here:

      objectclass ( 1.3.1.5.1.4.1.7165.2.2.2 NAME 'sambaAccount' SUP top STRUCTURAL
+     DESC 'Samba Account'
+     MUST ( uid $ rid )
+     MAY  ( cn $ lmPassword $ ntPassword $ pwdLastSet $ logonTime $
+            logoffTime $ kickoffTime $ pwdCanChange $ pwdMustChange $ acctFlags $
+            displayName $ smbHome $ homeDrive $ scriptPath $ profilePath $
+            description $ userWorkstations $ primaryGroupID $ domain ))

      The samba.schema file has been formatted for OpenLDAP 2.0. The OID's are +owned by the Samba Team and as such is legal to be openly published. +If you translate the schema to be used with Netscape DS, please +submit the modified schema file as a patch to jerry@samba.org

      Just as the smbpasswd file is mean to store information which supplements a +user's /etc/passwd entry, so is the sambaAccount object +meant to supplement the UNIX user account information. A sambaAccount is a +STRUCTURAL objectclass so it can be stored individually +in the directory. However, there are several fields (e.g. uid) which overlap +with the posixAccount objectclass outlined in RFC2307. This is by design.

      In order to store all user account information (UNIX and Samba) in the directory, +it is necessary to use the sambaAccount and posixAccount objectclasses in +combination. However, smbd will still obtain the user's UNIX account +information via the standard C library calls (e.g. getpwnam(), et. al.). +This means that the Samba server must also have the LDAP NSS library installed +and functioning correctly. This division of information makes it possible to +store all Samba account information in LDAP, but still maintain UNIX account +information in NIS while the network is transitioning to a full LDAP infrastructure.

      3.6.5. Configuring Samba with LDAP

      3.6.5.1. OpenLDAP configuration

      To include support for the sambaAccount object in an OpenLDAP directory +server, first copy the samba.schema file to slapd's configuration directory.

      root# cp samba.schema /etc/openldap/schema/

      Next, include the samba.schema file in slapd.conf. +The sambaAccount object contains two attributes which depend upon other schema +files. The 'uid' attribute is defined in cosine.schema and +the 'displayName' attribute is defined in the inetorgperson.schema +file. Both of these must be included before the samba.schema file.

      ## /etc/openldap/slapd.conf
+
+## schema files (core.schema is required by default)
+include	           /etc/openldap/schema/core.schema
+
+## needed for sambaAccount
+include            /etc/openldap/schema/cosine.schema
+include            /etc/openldap/schema/inetorgperson.schema
+include            /etc/openldap/schema/samba.schema
+
+## uncomment this line if you want to support the RFC2307 (NIS) schema
+## include         /etc/openldap/schema/nis.schema
+
+....

      It is recommended that you maintain some indices on some of the most usefull attributes, +like in the following example, to speed up searches made on sambaAccount objectclasses +(and possibly posixAccount and posixGroup as well).

      # Indices to maintain
+## required by OpenLDAP 2.0
+index objectclass   eq
+
+## support pb_getsampwnam()
+index uid           pres,eq
+## support pdb_getsambapwrid()
+index rid           eq
+
+## uncomment these if you are storing posixAccount and
+## posixGroup entries in the directory as well
+##index uidNumber     eq
+##index gidNumber     eq
+##index cn            eq
+##index memberUid     eq

      3.6.5.2. Configuring Samba

      The following parameters are available in smb.conf only with --with-ldapsam +was included with compiling Samba.

      These are described in the smb.conf(5) man +page and so will not be repeated here. However, a sample smb.conf file for +use with an LDAP directory could appear as

      ## /usr/local/samba/lib/smb.conf
+[global]
+     security = user
+     encrypt passwords = yes
+
+     netbios name = TASHTEGO
+     workgroup = NARNIA
+
+     # ldap related parameters
+
+     # define the DN to use when binding to the directory servers
+     # The password for this DN is not stored in smb.conf.  Rather it
+     # must be set by using 'smbpasswd -w secretpw' to store the
+     # passphrase in the secrets.tdb file.  If the "ldap admin dn" values
+     # changes, this password will need to be reset.
+     ldap admin dn = "cn=Samba Manager,ou=people,dc=samba,dc=org"
+
+     #  specify the LDAP server's hostname (defaults to locahost)
+     ldap server = ahab.samba.org
+
+     # Define the SSL option when connecting to the directory
+     # ('off', 'start tls', or 'on' (default))
+     ldap ssl = start tls
+
+     # define the port to use in the LDAP session (defaults to 636 when
+     # "ldap ssl = on")
+     ldap port = 389
+
+     # specify the base DN to use when searching the directory
+     ldap suffix = "ou=people,dc=samba,dc=org"
+
+     # generally the default ldap search filter is ok
+     # ldap filter = "(&(uid=%u)(objectclass=sambaAccount))"

      3.6.6. Accounts and Groups management

      As users accounts are managed thru the sambaAccount objectclass, you should +modify you existing administration tools to deal with sambaAccount attributes.

      Machines accounts are managed with the sambaAccount objectclass, just +like users accounts. However, it's up to you to stored thoses accounts +in a different tree of you LDAP namespace: you should use +"ou=Groups,dc=plainjoe,dc=org" to store groups and +"ou=People,dc=plainjoe,dc=org" to store users. Just configure your +NSS and PAM accordingly (usually, in the /etc/ldap.conf configuration +file).

      In Samba release 3.0, the group management system is based on posix +groups. This means that Samba make usage of the posixGroup objectclass. +For now, there is no NT-like group system management (global and local +groups).

      3.6.7. Security and sambaAccount

      There are two important points to remember when discussing the security +of sambaAccount entries in the directory.

      • Never retrieve the lmPassword or + ntPassword attribute values over an unencrypted LDAP session.

      • Never allow non-admin users to + view the lmPassword or ntPassword attribute values.

      These password hashes are clear text equivalents and can be used to impersonate +the user without deriving the original clear text strings. For more information +on the details of LM/NT password hashes, refer to the ENCRYPTION chapter of the Samba-HOWTO-Collection.

      To remedy the first security issue, the "ldap ssl" smb.conf parameter defaults +to require an encrypted session (ldap ssl = on) using +the default port of 636 +when contacting the directory server. When using an OpenLDAP 2.0 server, it +is possible to use the use the StartTLS LDAP extended operation in the place of +LDAPS. In either case, you are strongly discouraged to disable this security +(ldap ssl = off).

      Note that the LDAPS protocol is deprecated in favor of the LDAPv3 StartTLS +extended operation. However, the OpenLDAP library still provides support for +the older method of securing communication between clients and servers.

      The second security precaution is to prevent non-administrative users from +harvesting password hashes from the directory. This can be done using the +following ACL in slapd.conf:

      ## allow the "ldap admin dn" access, but deny everyone else
+access to attrs=lmPassword,ntPassword
+     by dn="cn=Samba Admin,ou=people,dc=plainjoe,dc=org" write
+     by * none

      3.6.8. LDAP specials attributes for sambaAccounts

      The sambaAccount objectclass is composed of the following attributes:

      • lmPassword: the LANMAN password 16-byte hash stored as a character + representation of a hexidecimal string.

      • ntPassword: the NT password hash 16-byte stored as a character + representation of a hexidecimal string.

      • pwdLastSet: The integer time in seconds since 1970 when the + lmPassword and ntPassword attributes were last set. +

      • acctFlags: string of 11 characters surrounded by square brackets [] + representing account flags such as U (user), W(workstation), X(no password expiration), and + D(disabled).

      • logonTime: Integer value currently unused

      • logoffTime: Integer value currently unused

      • kickoffTime: Integer value currently unused

      • pwdCanChange: Integer value currently unused

      • pwdMustChange: Integer value currently unused

      • homeDrive: specifies the drive letter to which to map the + UNC path specified by homeDirectory. The drive letter must be specified in the form "X:" + where X is the letter of the drive to map. Refer to the "logon drive" parameter in the + smb.conf(5) man page for more information.

      • scriptPath: The scriptPath property specifies the path of + the user's logon script, .CMD, .EXE, or .BAT file. The string can be null. The path + is relative to the netlogon share. Refer to the "logon script" parameter in the + smb.conf(5) man page for more information.

      • profilePath: specifies a path to the user's profile. + This value can be a null string, a local absolute path, or a UNC path. Refer to the + "logon path" parameter in the smb.conf(5) man page for more information.

      • smbHome: The homeDirectory property specifies the path of + the home directory for the user. The string can be null. If homeDrive is set and specifies + a drive letter, homeDirectory should be a UNC path. The path must be a network + UNC path of the form \\server\share\directory. This value can be a null string. + Refer to the "logon home" parameter in the smb.conf(5) man page for more information. +

      • userWorkstation: character string value currently unused. +

      • rid: the integer representation of the user's relative identifier + (RID).

      • primaryGroupID: the relative identifier (RID) of the primary group + of the user.

      The majority of these parameters are only used when Samba is acting as a PDC of +a domain (refer to the Samba-PDC-HOWTO for details on +how to configure Samba as a Primary Domain Controller). The following four attributes +are only stored with the sambaAccount entry if the values are non-default values:

      • smbHome

      • scriptPath

      • logonPath

      • homeDrive

      These attributes are only stored with the sambaAccount entry if +the values are non-default values. For example, assume TASHTEGO has now been +configured as a PDC and that logon home = \\%L\%u was defined in +its smb.conf file. When a user named "becky" logons to the domain, +the logon home string is expanded to \\TASHTEGO\becky. +If the smbHome attribute exists in the entry "uid=becky,ou=people,dc=samba,dc=org", +this value is used. However, if this attribute does not exist, then the value +of the logon home parameter is used in its place. Samba +will only write the attribute value to the directory entry is the value is +something other than the default (e.g. \\MOBY\becky).

      3.6.9. Example LDIF Entries for a sambaAccount

      The following is a working LDIF with the inclusion of the posixAccount objectclass:

      dn: uid=guest2, ou=people,dc=plainjoe,dc=org
+ntPassword: 878D8014606CDA29677A44EFA1353FC7
+pwdMustChange: 2147483647
+primaryGroupID: 1201
+lmPassword: 552902031BEDE9EFAAD3B435B51404EE
+pwdLastSet: 1010179124
+logonTime: 0
+objectClass: sambaAccount
+uid: guest2
+kickoffTime: 2147483647
+acctFlags: [UX         ]
+logoffTime: 2147483647
+rid: 19006
+pwdCanChange: 0

      The following is an LDIF entry for using both the sambaAccount and +posixAccount objectclasses:

      dn: uid=gcarter, ou=people,dc=plainjoe,dc=org
+logonTime: 0
+displayName: Gerald Carter
+lmPassword: 552902031BEDE9EFAAD3B435B51404EE
+primaryGroupID: 1201
+objectClass: posixAccount
+objectClass: sambaAccount
+acctFlags: [UX         ]
+userPassword: {crypt}BpM2ej8Rkzogo
+uid: gcarter
+uidNumber: 9000
+cn: Gerald Carter
+loginShell: /bin/bash
+logoffTime: 2147483647
+gidNumber: 100
+kickoffTime: 2147483647
+pwdLastSet: 1010179230
+rid: 19000
+homeDirectory: /home/tashtego/gcarter
+pwdCanChange: 0
+pwdMustChange: 2147483647
+ntPassword: 878D8014606CDA29677A44EFA1353FC7

      3.7. MySQL

      3.7.1. Building

      To build the plugin, run make bin/pdb_mysql.so +in the source/ directory of samba distribution.

      Next, copy pdb_mysql.so to any location you want. I +strongly recommend installing it in $PREFIX/lib or /usr/lib/samba/

      3.7.2. Creating the database

      You either can set up your own table and specify the field names to pdb_mysql (see below +for the column names) or use the default table. The file examples/pdb/mysql/mysql.dump +contains the correct queries to create the required tables. Use the command : + +mysql -uusername -hhostname -ppassword databasename < /path/to/samba/examples/pdb/mysql/mysql.dump

      3.7.3. Configuring

      This plugin lacks some good documentation, but here is some short info:

      Add a the following to the passdb backend variable in your smb.conf: +

      passdb backend = [other-plugins] plugin:/location/to/pdb_mysql.so:identifier [other-plugins]

      The identifier can be any string you like, as long as it doesn't collide with +the identifiers of other plugins or other instances of pdb_mysql. If you +specify multiple pdb_mysql.so entries in 'passdb backend', you also need to +use different identifiers!

      Additional options can be given thru the smb.conf file in the [global] section.

      identifier:mysql host                     - host name, defaults to 'localhost'
+identifier:mysql password
+identifier:mysql user                     - defaults to 'samba'
+identifier:mysql database                 - defaults to 'samba'
+identifier:mysql port                     - defaults to 3306
+identifier:table                          - Name of the table containing users

      Since the password for the mysql user is stored in the +smb.conf file, you should make the the smb.conf file +readable only to the user that runs samba. This is considered a security +bug and will be fixed soon.

      Names of the columns in this table(I've added column types those columns should have first):

      identifier:logon time column             - int(9)
+identifier:logoff time column            - int(9)
+identifier:kickoff time column           - int(9)
+identifier:pass last set time column     - int(9)
+identifier:pass can change time column   - int(9)
+identifier:pass must change time column  - int(9)
+identifier:username column               - varchar(255) - unix username
+identifier:domain column                 - varchar(255) - NT domain user is part of
+identifier:nt username column            - varchar(255) - NT username
+identifier:fullname column            - varchar(255) - Full name of user
+identifier:home dir column               - varchar(255) - Unix homedir path
+identifier:dir drive column              - varchar(2) - Directory drive path (eg: 'H:')
+identifier:logon script column           - varchar(255) - Batch file to run on client side when logging on
+identifier:profile path column           - varchar(255) - Path of profile
+identifier:acct desc column              - varchar(255) - Some ASCII NT user data
+identifier:workstations column           - varchar(255) - Workstations user can logon to (or NULL for all)
+identifier:unknown string column         - varchar(255) - unknown string
+identifier:munged dial column            - varchar(255) - ?
+identifier:uid column                    - int(9) - Unix user ID (uid)
+identifier:gid column                    - int(9) - Unix user group (gid)
+identifier:user sid column               - varchar(255) - NT user SID
+identifier:group sid column              - varchar(255) - NT group ID
+identifier:lanman pass column            - varchar(255) - encrypted lanman password
+identifier:nt pass column                - varchar(255) - encrypted nt passwd
+identifier:plain pass column             - varchar(255) - plaintext password
+identifier:acct control column           - int(9) - nt user data
+identifier:unknown 3 column              - int(9) - unknown
+identifier:logon divs column             - int(9) - ?
+identifier:hours len column              - int(9) - ?
+identifier:unknown 5 column              - int(9) - unknown
+identifier:unknown 6 column              - int(9) - unknown

      Eventually, you can put a colon (:) after the name of each column, which +should specify the column to update when updating the table. You can also +specify nothing behind the colon - then the data from the field will not be +updated.

      3.7.4. Using plaintext passwords or encrypted password

      I strongly discourage the use of plaintext passwords, however, you can use them:

      If you would like to use plaintext passwords, set 'identifier:lanman pass column' and 'identifier:nt pass column' to 'NULL' (without the quotes) and 'identifier:plain pass column' to the name of the column containing the plaintext passwords.

      If you use encrypted passwords, set the 'identifier:plain pass column' to 'NULL' (without the quotes). This is the default.

      3.7.5. Getting non-column data from the table

      It is possible to have not all data in the database and making some 'constant'.

      For example, you can set 'identifier:fullname column' to : +CONCAT(First_name,' ',Sur_name)

      Or, set 'identifier:workstations column' to : +NULL

      See the MySQL documentation for more language constructs.

      3.8. Passdb XML plugin

      3.8.1. Building

      This module requires libxml2 to be installed.

      To build pdb_xml, run: make bin/pdb_xml.so in +the directory source/.

      3.8.2. Usage

      The usage of pdb_xml is pretty straightforward. To export data, use: + +pdbedit -e plugin:/usr/lib/samba/pdb_xml.so:filename + +(where filename is the name of the file to put the data in)

      To import data, use: +pdbedit -i plugin:/usr/lib/samba/pdb_xml.so:filename -e current-pdb + +Where filename is the name to read the data from and current-pdb to put it in.

      PrevHomeNext
      Quick Cross Subnet Browsing / Cross Workgroup Browsing guideUpType of installation
      \ No newline at end of file diff --git a/docs/htmldocs/pdb-mysql.html b/docs/htmldocs/pdb-mysql.html index abca946f6f..e98d0c30d0 100644 --- a/docs/htmldocs/pdb-mysql.html +++ b/docs/htmldocs/pdb-mysql.html @@ -5,8 +5,7 @@ >Passdb MySQL plugin

      Chapter 16. Passdb MySQL plugin

      Chapter 16. Passdb MySQL plugin

      16.1. Building

      16.1. Building

      To build the plugin, run

      16.2. Configuring

      16.2. Creating the database

      You either can set up your own table and specify the field names to pdb_mysql (see below +for the column names) or use the default table. The file examples/pdb/mysql/mysql.dump +contains the correct queries to create the required tables. Use the command : + +mysql -uusername -hhostname -ppassword databasename < /path/to/samba/examples/pdb/mysql/mysql.dump

      16.3. Configuring

      This plugin lacks some good documentation, but here is some short info:

      16.3. Using plaintext passwords or encrypted password

      16.4. Using plaintext passwords or encrypted password

      I strongly discourage the use of plaintext passwords, however, you can use them:

      16.4. Getting non-column data from the table

      16.5. Getting non-column data from the table

      It is possible to have not all data in the database and making some 'constant'.

      Passdb XML plugin

      Chapter 17. Passdb XML plugin

      Chapter 17. Passdb XML plugin

      17.1. Building

      17.1. Building

      This module requires libxml2 to be installed.

      17.2. Usage

      17.2. Usage

      The usage of pdb_xml is pretty straightforward. To export data, use: diff --git a/docs/htmldocs/pdbedit.8.html b/docs/htmldocs/pdbedit.8.html index e3cf1e4fba..14497f522c 100644 --- a/docs/htmldocs/pdbedit.8.html +++ b/docs/htmldocs/pdbedit.8.html @@ -1,12 +1,11 @@ - + pdbedit

      pdbedit

      pdbedit

      Synopsis

      pdbedit [-l] [-v] [-w] [-u username] [-f fullname] [-h homedir] [-D drive] [-S script] [-p profile] [-a] [-m] [-x] [-i passdb-backend] [-e passdb-backend] [-b passdb-backend] [-d debuglevel] [-s configfile] [-P account-policy] [-V value]

      [-l] [-v] [-w] [-u username] [-f fullname] [-h homedir] [-D drive] [-S script] [-p profile] [-a] [-m] [-x] [-i passdb-backend] [-e passdb-backend] [-b passdb-backend] [-d debuglevel] [-s configfile] [-P account-policy] [-V value]

      DESCRIPTION

      This tool is part of the SambaThis tool is part of the Samba(7) suite.

      The pdbedit program is used to manage the users accounts @@ -65,7 +70,7 @@ TARGET="_top" >

      OPTIONS

      pdbedit -l

      		sorce:500:Simo Sorce
-		samba:45:Test User
-
      sorce:500:Simo Sorce +samba:45:Test User

      pdbedit -l -v

      		---------------
-		username:       sorce
-		user ID/Group:  500/500
-		user RID/GRID:  2000/2001
-		Full Name:      Simo Sorce
-		Home Directory: \\BERSERKER\sorce
-		HomeDir Drive:  H:
-		Logon Script:   \\BERSERKER\netlogon\sorce.bat
-		Profile Path:   \\BERSERKER\profile
-		---------------
-		username:       samba
-		user ID/Group:  45/45
-		user RID/GRID:  1090/1091
-		Full Name:      Test User
-		Home Directory: \\BERSERKER\samba
-		HomeDir Drive:  
-		Logon Script:   
-		Profile Path:   \\BERSERKER\profile
-
      --------------- +username: sorce +user ID/Group: 500/500 +user RID/GRID: 2000/2001 +Full Name: Simo Sorce +Home Directory: \\BERSERKER\sorce +HomeDir Drive: H: +Logon Script: \\BERSERKER\netlogon\sorce.bat +Profile Path: \\BERSERKER\profile +--------------- +username: samba +user ID/Group: 45/45 +user RID/GRID: 1090/1091 +Full Name: Test User +Home Directory: \\BERSERKER\samba +HomeDir Drive: +Logon Script: +Profile Path: \\BERSERKER\profile

      smbpasswd file format. (see the smbpasswd(5) file format. (see the + smbpasswd(5) for details)

      Example: pdbedit -l -w

      		sorce:500:508818B733CE64BEAAD3B435B51404EE:D2A2418EFC466A8A0F6B1DBB5C3DB80C:[UX         ]:LCT-00000000:
-		samba:45:0F2B255F7B67A7A9AAD3B435B51404EE:BC281CE3F53B6A5146629CD4751D3490:[UX         ]:LCT-3BFA1E8D:
-

      sorce:500:508818B733CE64BEAAD3B435B51404EE:D2A2418EFC466A8A0F6B1DBB5C3DB80C:[UX ]:LCT-00000000: +samba:45:0F2B255F7B67A7A9AAD3B435B51404EE:BC281CE3F53B6A5146629CD4751D3490:[UX ]:LCT-3BFA1E8D:
      -u username

      This option specifies the username to be used for the operation requested (listing, adding, removing). - It is required in add, remove and modify - operations and optional in list operations.

      pdbedit -a -u sorce       - 
      new password:
-		retype new password
      -

      -m
      pdbedit -P "bad lockout attempt"

      		account policy value for bad lockout attempt is 0
-
      account policy value for bad lockout attempt is 0

      pdbedit -P "bad lockout attempt" -V 3

      		account policy value for bad lockout attempt was 0
-		account policy value for bad lockout attempt is now 3
-
      account policy value for bad lockout attempt was 0 +account policy value for bad lockout attempt is now 3

      Print a summary of command line options.

      -s <configuration file>
      -s <configuration file>

      The file specified contains the @@ -517,7 +466,7 @@ compile time.

      NOTES

      VERSION

      SEE ALSO

      smbpasswd(8), - samba(7) -

      smbpasswd(5), samba(7)

      AUTHOR

      The original Samba man pages were written by Karl Auer. The man page sources were converted to YODL format (another - excellent piece of Open Source software, available at - ftp://ftp.icce.rug.nl/pub/unix/) and updated for the Samba 2.0 release by Jeremy Allison. The conversion to DocBook for - Samba 2.2 was done by Gerald Carter

      Portability

      Chapter 23. Portability

      Chapter 21. Portability

      Samba works on a wide range of platforms but the interface all the platforms provide is not always compatible. This chapter contains @@ -83,7 +84,9 @@ CLASS="SECT1" >

      23.1. HPUX

      21.1. HPUX

      HP's implementation of supplementary groups is, er, non-standard (for hysterical reasons). There are two group files, /etc/group and @@ -111,7 +114,9 @@ CLASS="SECT1" >

      23.2. SCO Unix

      21.2. SCO Unix

      If you run an old version of SCO Unix then you may need to get important @@ -126,7 +131,9 @@ CLASS="SECT1" >

      23.3. DNIX

      21.3. DNIX

      DNIX has a problem with seteuid() and setegid(). These routines are needed for Samba to work correctly, but they were left out of the DNIX @@ -231,7 +238,9 @@ CLASS="SECT1" >

      23.4. RedHat Linux Rembrandt-II

      21.4. RedHat Linux Rembrandt-II

      By default RedHat Rembrandt-II during installation adds an entry to /etc/hosts as follows: diff --git a/docs/htmldocs/printing.html b/docs/htmldocs/printing.html index 46ebbcdf84..92eb52c7cc 100644 --- a/docs/htmldocs/printing.html +++ b/docs/htmldocs/printing.html @@ -5,8 +5,7 @@ >Printing Support

      Chapter 14. Printing Support

      Chapter 13. Printing Support

      14.1. Introduction

      13.1. Introduction

      Beginning with the 2.2.0 release, Samba supports the native Windows NT printing mechanisms implemented via @@ -160,7 +163,9 @@ CLASS="SECT1" >

      14.2. Configuration

      13.2. Configuration

      Warning

      14.2.1. Creating [print$]

      13.2.1. Creating [print$]

      In order to support the uploading of printer driver files, you must first configure a file share named [print$]. @@ -303,7 +310,7 @@ WIDTH="25" ALIGN="CENTER" VALIGN="TOP" >NoteWarning

      14.2.2. Setting Drivers for Existing Printers

      13.2.2. Setting Drivers for Existing Printers

      The initial listing of printers in the Samba host's Printers folder will have no real printer driver assigned @@ -515,7 +524,9 @@ CLASS="SECT2" >

      14.2.3. Support a large number of printers

      13.2.3. Support a large number of printers

      One issue that has arisen during the development phase of Samba 2.2 is the need to support driver downloads for @@ -579,7 +590,9 @@ CLASS="SECT2" >

      14.2.4. Adding New Printers via the Windows NT APW

      13.2.4. Adding New Printers via the Windows NT APW

      By default, Samba offers all printer shares defined in

      14.2.5. Samba and Printer Ports

      13.2.5. Samba and Printer Ports

      Windows NT/2000 print servers associate a port with each printer. These normally take the form of LPT1:, COM1:, FILE:, etc... Samba must also support the @@ -781,7 +796,9 @@ CLASS="SECT1" >

      14.3. The Imprints Toolset

      13.3. The Imprints Toolset

      The Imprints tool set provides a UNIX equivalent of the Windows NT Add Printer Wizard. For complete information, please @@ -797,7 +814,9 @@ CLASS="SECT2" >

      14.3.1. What is Imprints?

      13.3.1. What is Imprints?

      Imprints is a collection of tools for supporting the goals of

      14.3.2. Creating Printer Driver Packages

      13.3.2. Creating Printer Driver Packages

      The process of creating printer driver packages is beyond the scope of this document (refer to Imprints.txt also included @@ -841,7 +862,9 @@ CLASS="SECT2" >

      14.3.3. The Imprints server

      13.3.3. The Imprints server

      The Imprints server is really a database server that may be queried via standard HTTP mechanisms. Each printer @@ -863,7 +886,9 @@ CLASS="SECT2" >

      14.3.4. The Installation Client

      13.3.4. The Installation Client

      More information regarding the Imprints installation client is available in the

      14.4. Diagnosis

      13.4. Diagnosis

      14.4.1. Introduction

      13.4.1. Introduction

      This is a short description of how to debug printing problems with Samba. This describes how to debug problems with printing from a SMB @@ -1034,7 +1063,9 @@ CLASS="SECT2" >

      14.4.2. Debugging printer problems

      13.4.2. Debugging printer problems

      One way to debug printing problems is to start by replacing these command with shell scripts that record the arguments and the contents @@ -1050,7 +1081,7 @@ CLASS="PROGRAMLISTING" /usr/bin/id -p >/tmp/tmp.print # we run the command and save the error messages # replace the command with the one appropriate for your system - /usr/bin/lpr -r -P$1 $2 2>>&/tmp/tmp.print

      Then you print a file and try removing it. You may find that the @@ -1089,7 +1120,9 @@ CLASS="SECT2" >

      14.4.3. What printers do I have?

      13.4.3. What printers do I have?

      You can use the 'testprns' program to check to see if the printer name you are using is recognized by Samba. For example, you can @@ -1116,7 +1149,9 @@ CLASS="SECT2" >

      14.4.4. Setting up printcap and print servers

      13.4.4. Setting up printcap and print servers

      You may need to set up some printcaps for your Samba system to use. It is strongly recommended that you use the facilities provided by @@ -1198,7 +1233,9 @@ CLASS="SECT2" >

      14.4.5. Job sent, no output

      13.4.5. Job sent, no output

      This is the most frustrating part of printing. You may have sent the job, verified that the job was forwarded, set up a wrapper around @@ -1241,7 +1278,9 @@ CLASS="SECT2" >

      14.4.6. Job sent, strange output

      13.4.6. Job sent, strange output

      Once you have the job printing, you can then start worrying about making it print nicely.

      14.4.7. Raw PostScript printed

      13.4.7. Raw PostScript printed

      This is a problem that is usually caused by either the print spooling system putting information at the start of the print job that makes @@ -1298,7 +1339,9 @@ CLASS="SECT2" >

      14.4.8. Advanced Printing

      13.4.8. Advanced Printing

      Note that you can do some pretty magic things by using your imagination with the "print command" option and some shell scripts. @@ -1312,7 +1355,9 @@ CLASS="SECT2" >

      14.4.9. Real debugging

      13.4.9. Real debugging

      If the above debug tips don't help, then maybe you need to bring in the bug guns, system tracing. See Tracing.txt in this directory.

      LanMan and NT Password Encryption in SambaNext

      Chapter 4. LanMan and NT Password Encryption in Samba

      Chapter 4. LanMan and NT Password Encryption in Samba

      4.1. Introduction

      4.1. Introduction

      Newer windows clients send encrypted passwords over the wire, instead of plain text passwords. The newest clients @@ -101,7 +104,9 @@ CLASS="SECT1" >

      4.2. Important Notes About Security

      4.2. Important Notes About Security

      The unix and SMB password encryption techniques seem similar on the surface. This similarity is, however, only skin deep. The unix @@ -135,7 +140,7 @@ WIDTH="25" ALIGN="CENTER" VALIGN="TOP" >Warning

      4.2.1. Advantages of SMB Encryption

      4.2.1. Advantages of SMB Encryption

        4.2.2. Advantages of non-encrypted passwords

        4.2.2. Advantages of non-encrypted passwords

          4.3. The smbpasswd Command

          4.3. The smbpasswd Command

          The smbpasswd command maintains the two 32 byte password fields in the smbpasswd file. If you wish to make it similar to the unix @@ -401,7 +412,7 @@ WIDTH="33%" ALIGN="right" VALIGN="top" >NextType of installationUser information database

      rpcclient

      rpcclient

      DESCRIPTION

      This tool is part of the SambaThis tool is part of the Samba(7) suite.

      OPTIONS

      name resolve order       line from - smb.conf(5) line from smb.conf(5).

      		username = <value> 
-		password = <value>
-		domain   = <value>
-
      username = <value> +password = <value> +domain = <value>

      Make certain that the permissions on the file restrict @@ -124,6 +127,12 @@ CLASS="PROGRAMLISTING" below))

      -h|--help

      Print a summary of command line options.

      -d|--debug=debuglevel

      file.

      -h|--help

      Print a summary of command line options.

      -I IP-address

      COMMANDS

      		Long Printer Name:\
-		Driver File Name:\
-		Data File Name:\
-		Config File Name:\
-		Help File Name:\
-		Language Monitor Name:\
-		Default Data Type:\
-		Comma Separated list of Files
-
      Long Printer Name:\ +Driver File Name:\ +Data File Name:\ +Config File Name:\ +Help File Name:\ +Language Monitor Name:\ +Default Data Type:\ +Comma Separated list of Files

      Any empty fields should be enter as the string "NULL".

      BUGS

      "WARNING!WARNING!       The MSRPC over SMB code has been developed from examining Network traces. No documentation is @@ -734,23 +736,28 @@ CLASS="EMPHASIS" to be... a bit flaky in places.

      The development of Samba's implementation is also a bit rough, - and as more of the services are understood, it can even result in - versions of smbd(8) and rpcclient(1) - that are incompatible for some commands or services. Additionally, + and as more of the services are understood, it can even result in + 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

      AUTHOR

      The original rpcclient man page was written by Matthew Geddes, Luke Kenneth Casson Leighton, and rewritten by Gerald Carter. The conversion to DocBook for Samba 2.2 was done by Gerald - Carter.

      How to Act as a Backup Domain Controller in a Purely Samba Controlled Domain

      Chapter 7. How to Act as a Backup Domain Controller in a Purely Samba Controlled Domain

      Chapter 6. How to Act as a Backup Domain Controller in a Purely Samba Controlled Domain

      7.1. Prerequisite Reading

      6.1. Prerequisite Reading

      Before you continue reading in this chapter, please make sure that you are comfortable with configuring a Samba PDC @@ -94,7 +97,9 @@ CLASS="SECT1" >

      7.2. Background

      6.2. Background

      What is a Domain Controller? It is a machine that is able to answer logon requests from workstations in a Windows NT Domain. Whenever a @@ -137,7 +142,9 @@ CLASS="SECT1" >

      7.3. What qualifies a Domain Controller on the network?

      6.3. What qualifies a Domain Controller on the network?

      Every machine that is a Domain Controller for the domain SAMBA has to register the NetBIOS group name SAMBA#1c with the WINS server and/or @@ -152,7 +159,9 @@ CLASS="SECT2" >

      7.3.1. How does a Workstation find its domain controller?

      6.3.1. How does a Workstation find its domain controller?

      A NT workstation in the domain SAMBA that wants a local user to be authenticated has to find the domain controller for SAMBA. It does @@ -169,7 +178,9 @@ CLASS="SECT2" >

      7.3.2. When is the PDC needed?

      6.3.2. When is the PDC needed?

      Whenever a user wants to change his password, this has to be done on the PDC. To find the PDC, the workstation does a NetBIOS name query @@ -183,13 +194,19 @@ CLASS="SECT1" >

      7.4. Can Samba be a Backup Domain Controller?

      6.4. Can Samba be a Backup Domain Controller to an NT PDC?

      With version 2.2, no. The native NT SAM replication protocols have not yet been fully implemented. The Samba Team is working on understanding and implementing the protocols, but this work has not been finished for version 2.2.

      With version 3.0, the work on both the replication protocols and a +suitable storage mechanism has progressed, and some form of NT4 BDC +support is expected soon.

      Can I get the benefits of a BDC with Samba? Yes. The main reason for implementing a BDC is availability. If the PDC is a Samba machine, a second Samba machine can be set up to @@ -200,7 +217,9 @@ CLASS="SECT1" >

      7.5. How do I set up a Samba BDC?

      6.5. How do I set up a Samba BDC?

      Several things have to be done:

      7.5.1. How do I replicate the smbpasswd file?

      6.5.1. How do I replicate the smbpasswd file?

      Replication of the smbpasswd file is sensitive. It has to be done whenever changes to the SAM are made. Every user's password change is @@ -279,6 +300,21 @@ rsync. rsync can use ssh as a transport. ssh itself can be set up to accept *only* rsync transfer without requiring the user to type a password.

      6.5.2. Can I do this all with LDAP?

      The simple answer is YES. Samba's pdb_ldap code supports +binding to a replica LDAP server, and will also follow referrals and +rebind to the master if it ever needs to make a modification to the +database. (Normally BDCs are read only, so this will not occur +often).

      How to Configure Samba as a NT4 Primary Domain ControllerSamba as a NT4 or Win2k Primary Domain ControllerSAMBA Project Documentation

      SAMBA Project Documentation

      SAMBA Project Documentation

      SAMBA Team

      SAMBA Team

      Abstract

      Abstract

      2. Improved browsing in sambaQuick Cross Subnet Browsing / Cross Workgroup Browsing guide
      2.1. Overview of browsingDiscussion
      2.2. Browsing support in sambaUse of the "Remote Announce" parameter
      2.3. Problem resolutionUse of the "Remote Browse Sync" parameter
      2.4. Browsing across subnetsUse of WINS
      2.5. Setting up a WINS serverDo NOT use more than one (1) protocol on MS Windows machines
      2.6. Setting up Browsing in a WORKGROUP
      2.7. Setting up Browsing in a DOMAIN
      2.8. Forcing samba to be the master
      2.9. Making samba the domain master
      2.10. Note about broadcast addresses
      2.11. Multiple interfacesName Resolution Order
      3. Quick Cross Subnet Browsing / Cross Workgroup Browsing guideUser information database
      3.1. DiscussionIntroduction
      3.2. Use of the "Remote Announce" parameterImportant Notes About Security
      3.3. Use of the "Remote Browse Sync" parameterThe smbpasswd Command
      3.4. Use of WINSPlain text
      3.5. Do NOT use more than one (1) protocol on MS Windows machinesTDB
      3.6. Name Resolution OrderLDAP
      4. LanMan and NT Password Encryption in Samba3.7. MySQL
      4.1. Introduction
      4.2. Important Notes About Security
      4.3. The smbpasswd Command3.8. Passdb XML plugin
      5. 4. User and Share security level (for servers not in a domain)
      6. 5. How to Configure Samba as a NT4 Primary Domain ControllerSamba as a NT4 or Win2k Primary Domain Controller
      6.1. 5.1. Prerequisite Reading
      6.2. 5.2. Background
      6.3. 5.3. Configuring the Samba Domain Controller
      6.4. 5.4. Creating Machine Trust Accounts and Joining Clients to the Domain
      6.5. 5.5. Common Problems and Errors
      6.6. 5.6. System Policies and Profiles
      6.7. 5.7. What other help can I get?
      6.8. 5.8. Domain Control for Windows 9x/ME
      6.9. DOMAIN_CONTROL.txt : Windows NT Domain Control & Samba5.9. DOMAIN_CONTROL.txt : Windows NT Domain Control & Samba
      7. 6. How to Act as a Backup Domain Controller in a Purely Samba Controlled Domain
      7.1. 6.1. Prerequisite Reading
      7.2. 6.2. Background
      7.3. 6.3. What qualifies a Domain Controller on the network?
      7.4. Can Samba be a Backup Domain Controller?6.4. Can Samba be a Backup Domain Controller to an NT PDC?
      7.5. 6.5. How do I set up a Samba BDC?
      8. 7. Samba as a ADS domain member
      8.1. 7.1. Installing the required packages for Debian
      8.2. 7.2. Installing the required packages for RedHat
      8.3. 7.3. Compile Samba
      8.4. 7.4. Setup your /etc/krb5.conf
      8.5. 7.5. Create the computer account
      8.6. 7.6. Test your server setup
      8.7. 7.7. Testing with smbclient
      8.8. 7.8. Notes
      9. 8. Samba as a NT4 domain memberSamba as a NT4 or Win2k domain member
      9.1. Joining an NT Domain with Samba 2.28.1. Joining an NT Domain with Samba 3.0
      9.2. 8.2. Samba and Windows 2000 Domains
      9.3. 8.3. Why is this better than security = server?
      10. 9. Integrating MS Windows networks with Samba
      10.1. 9.1. Agenda
      10.2. 9.2. Name Resolution in a pure Unix/Linux world
      10.3. 9.3. Name resolution as used within MS Windows networking
      10.4. 9.4. How browsing functions and how to deploy stable and dependable browsing using Samba
      10.5. 9.5. MS Windows security options and how to configure Samba for seemless integration
      10.6. 9.6. Conclusions
      11. 10. UNIX Permission Bits and Windows NT Access Control Lists
      11.1. 10.1. Viewing and changing UNIX permissions using the NT security dialogs
      11.2. 10.2. How to view file security on a Samba share
      11.3. 10.3. Viewing file ownership
      11.4. 10.4. Viewing file or directory permissions
      11.5. 10.5. Modifying file or directory permissions
      11.6. 10.6. Interaction with the standard Samba create mask parameters
      11.7. 10.7. Interaction with the standard Samba file attribute mapping
      12. 11. Configuring PAM for distributed but centrally managed authentication
      12.1. 11.1. Samba and PAM
      12.2. 11.2. Distributed Authentication
      12.3. 11.3. PAM Configuration in smb.conf
      13. 12. Hosting a Microsoft Distributed File System tree on Samba
      13.1. 12.1. Instructions
      14. 13. Printing Support
      14.1. 13.1. Introduction
      14.2. 13.2. Configuration
      14.3. 13.3. The Imprints Toolset
      14.4. 13.4. Diagnosis
      15. 14. Unified Logons between Windows NT and UNIX using Winbind
      15.1. 14.1. Abstract
      15.2. 14.2. Introduction
      15.3. 14.3. What Winbind Provides
      15.4. 14.4. How Winbind Works
      15.5. 14.5. Installation and Configuration
      15.6. 14.6. Limitations
      15.7. 14.7. Conclusion
      16. Passdb MySQL plugin15. Improved browsing in samba
      16.1. Building15.1. Overview of browsing
      16.2. Configuring15.2. Browsing support in samba
      16.3. Using plaintext passwords or encrypted password15.3. Problem resolution
      16.4. Getting non-column data from the table15.4. Browsing across subnets
      17. Passdb XML plugin15.5. Setting up a WINS server
      17.1. Building15.6. Setting up Browsing in a WORKGROUP
      17.2. Usage15.7. Setting up Browsing in a DOMAIN
      18. Stackable VFS modules15.8. Forcing samba to be the master
      18.1. Introduction and configuration15.9. Making samba the domain master
      18.2. Included modules15.10. Note about broadcast addresses
      18.3. VFS modules available elsewhere15.11. Multiple interfaces
      19. Storing Samba's User/Machine Account information in an LDAP Directory16. Stackable VFS modules
      19.1. Purpose
      19.2. Introduction
      19.3. Supported LDAP Servers
      19.4. Schema and Relationship to the RFC 2307 posixAccount
      19.5. Configuring Samba with LDAP
      19.6. Accounts and Groups management
      19.7. Security and sambaAccount
      19.8. LDAP specials attributes for sambaAccounts16.1. Introduction and configuration
      19.9. Example LDIF Entries for a sambaAccount16.2. Included modules
      19.10. Comments16.3. VFS modules available elsewhere
      20. 17. HOWTO Access Samba source code via CVSAccess Samba source code via CVS
      20.1. 17.1. Introduction
      20.2. 17.2. CVS Access to samba.org
      21. 18. Group mapping HOWTO
      22. 19. Samba performance issues
      22.1. 19.1. Comparisons
      22.2. 19.2. Socket options
      22.3. 19.3. Read size
      22.4. 19.4. Max xmit
      22.5. 19.5. Log level
      22.6. 19.6. Read raw
      22.7. 19.7. Write raw
      22.8. 19.8. Slow Clients
      22.9. 19.9. Slow Logins
      22.10. 19.10. Client tuning
      20. Creating Group Profiles
      20.1. Windows '9x
      20.2. Windows NT 4
      20.3. Windows 2000/XP
      23. 21. Portability
      23.1. 21.1. HPUX
      23.2. 21.2. SCO Unix
      23.3. 21.3. DNIX
      23.4. 21.4. RedHat Linux Rembrandt-II
      24. 22. Samba and other CIFS clients
      24.1. 22.1. Macintosh clients?
      24.2. 22.2. OS2 Client
      24.3. 22.3. Windows for Workgroups
      24.4. 22.4. Windows '95/'98
      24.5. 22.5. Windows 2000 Service Pack 2
      25. 23. Reporting Bugs
      25.1. 23.1. Introduction
      25.2. 23.2. General info
      25.3. 23.3. Debug levels
      25.4. 23.4. Internal errors
      25.5. 23.5. Attaching to a running process
      25.6. 23.6. Patches
      26. 24. Diagnosing your samba server
      26.1. 24.1. Introduction
      26.2. 24.2. Assumptions
      26.3. 24.3. Tests
      26.4. 24.4. Still having troubles?
      Storing Samba's User/Machine Account information in an LDAP Directory

      Chapter 19. Storing Samba's User/Machine Account information in an LDAP Directory

      Chapter 17. Storing Samba's User/Machine Account information in an LDAP Directory

      19.1. Purpose

      17.1. Purpose

      This document describes how to use an LDAP directory for storing Samba user account information traditionally stored in the smbpasswd(5) file. It is @@ -145,7 +148,9 @@ CLASS="SECT1" >

      19.2. Introduction

      17.2. Introduction

      Traditionally, when configuring

      19.3. Supported LDAP Servers

      17.3. Supported LDAP Servers

      The LDAP samdb code in 2.2.3 has been developed and tested using the OpenLDAP 2.0 server and client libraries. The same code should be able to work with @@ -283,7 +290,9 @@ CLASS="SECT1" >

      19.4. Schema and Relationship to the RFC 2307 posixAccount

      17.4. Schema and Relationship to the RFC 2307 posixAccount

      Samba 2.2.3 includes the necessary schema file for OpenLDAP 2.0 in

      19.5. Configuring Samba with LDAP

      17.5. Configuring Samba with LDAP

      19.5.1. OpenLDAP configuration

      17.5.1. OpenLDAP configuration

      To include support for the sambaAccount object in an OpenLDAP directory server, first copy the samba.schema file to slapd's configuration directory.

      19.5.2. Configuring Samba

      17.5.2. Configuring Samba

      The following parameters are available in smb.conf only with

      19.6. Accounts and Groups management

      17.6. Accounts and Groups management

      As users accounts are managed thru the sambaAccount objectclass, you should modify you existing administration tools to deal with sambaAccount attributes.

      19.7. Security and sambaAccount

      17.7. Security and sambaAccount

      There are two important points to remember when discussing the security of sambaAccount entries in the directory.

      19.8. LDAP specials attributes for sambaAccounts

      17.8. LDAP specials attributes for sambaAccounts

      The sambaAccount objectclass is composed of the following attributes:

      19.9. Example LDIF Entries for a sambaAccount

      17.9. Example LDIF Entries for a sambaAccount

      The following is a working LDIF with the inclusion of the posixAccount objectclass:

      19.10. Comments

      17.10. Comments

      Please mail all comments regarding this HOWTO to How to Configure Samba as a NT4 Primary Domain ControllerSamba as a NT4 or Win2k Primary Domain Controller

      Chapter 6. How to Configure Samba as a NT4 Primary Domain Controller

      Chapter 5. Samba as a NT4 or Win2k Primary Domain Controller

      6.1. Prerequisite Reading

      5.1. Prerequisite Reading

      Before you continue reading in this chapter, please make sure that you are comfortable with configuring basic files services @@ -105,7 +108,9 @@ CLASS="SECT1" >

      6.2. Background

      5.2. Background

      Note

      6.3. Configuring the Samba Domain Controller

      5.3. Configuring the Samba Domain Controller

      The first step in creating a working Samba PDC is to understand the parameters necessary in smb.conf. I will not @@ -465,7 +472,9 @@ CLASS="SECT1" >

      6.4. Creating Machine Trust Accounts and Joining Clients to the +NAME="AEN810" +>5.4. Creating Machine Trust Accounts and Joining Clients to the Domain

      A machine trust account is a Samba account that is used to @@ -537,7 +546,9 @@ CLASS="SECT2" >

      6.4.1. Manual Creation of Machine Trust Accounts

      5.4.1. Manual Creation of Machine Trust Accounts

      The first step in manually creating a machine trust account is to manually create the corresponding Unix account in @@ -689,7 +700,7 @@ WIDTH="25" ALIGN="CENTER" VALIGN="TOP" >Warning

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

      5.4.2. "On-the-Fly" Creation of Machine Trust Accounts

      The second (and recommended) way of creating machine trust accounts is simply to allow the Samba server to create them as needed when the client @@ -751,7 +764,7 @@ be created manually.

      [global]
-   # <...remainder of parameters...>
+   # <...remainder of parameters...>
    add user script = /usr/sbin/useradd -d /dev/null -g 100 -s /bin/false -M %u

      6.4.3. Joining the Client to the Domain

      5.4.3. Joining the Client to the Domain

      The procedure for joining a client to the domain varies with the version of Windows.

      6.5. Common Problems and Errors

      5.5. Common Problems and Errors

      6.6. System Policies and Profiles

      5.6. System Policies and Profiles

      Much of the information necessary to implement System Policies and Roving User Profiles in a Samba domain is the same as that for @@ -1209,7 +1228,9 @@ CLASS="SECT1" >

      6.7. What other help can I get?

      5.7. What other help can I get?

      There are many sources of information available in the form of mailing lists, RFC's and documentation. The docs that come @@ -1627,7 +1648,9 @@ CLASS="SECT1" >

      6.8. Domain Control for Windows 9x/ME

      5.8. Domain Control for Windows 9x/ME

      Note

    • The client broadcasts (to the IP broadcast address of the subnet it is in) - a NetLogon request. This is sent to the NetBIOS name DOMAIN<1c> at the + a NetLogon request. This is sent to the NetBIOS name DOMAIN<1c> at the NetBIOS layer. The client chooses the first response it receives, which contains the NetBIOS name of the logon server to use in the format of \\SERVER. @@ -1759,7 +1782,9 @@ CLASS="SECT2" >

      6.8.1. Configuration Instructions: Network Logons

      5.8.1. Configuration Instructions: Network Logons

      The main difference between a PDC and a Windows 9x logon server configuration is that

      Warning

      6.8.2. Configuration Instructions: Setting up Roaming User Profiles

      5.8.2. Configuration Instructions: Setting up Roaming User Profiles

      Warning

      6.8.2.1. Windows NT Configuration

      5.8.2.1. Windows NT Configuration

      To support WinNT clients, in the [global] section of smb.conf set the following (for example):

      Note

      6.8.2.2. Windows 9X Configuration

      5.8.2.2. Windows 9X Configuration

      To support Win9X clients, you must use the "logon home" parameter. Samba has now been fixed so that "net use/home" now works as well, and it, too, relies @@ -1992,7 +2023,9 @@ CLASS="SECT3" >

      6.8.2.3. Win9X and WinNT Configuration

      5.8.2.3. Win9X and WinNT Configuration

      You can support profiles for both Win9X and WinNT clients by setting both the "logon home" and "logon path" parameters. For example:

      Note

      6.8.2.4. Windows 9X Profile Setup

      5.8.2.4. Windows 9X Profile Setup

      When a user first logs in on Windows 9X, the file user.DAT is created, as are folders "Start Menu", "Desktop", "Programs" and "Nethood". @@ -2193,7 +2228,9 @@ CLASS="SECT3" >

      6.8.2.5. Windows NT Workstation 4.0

      5.8.2.5. Windows NT Workstation 4.0

      When a user first logs in to a Windows NT Workstation, the profile NTuser.DAT is created. The profile location can be now specified @@ -2212,7 +2249,7 @@ WIDTH="25" ALIGN="CENTER" VALIGN="TOP" >NoteNote

      6.8.2.6. Windows NT Server

      5.8.2.6. Windows NT Server

      There is nothing to stop you specifying any path that you like for the location of users' profiles. Therefore, you could specify that the @@ -2317,7 +2356,9 @@ CLASS="SECT3" >

      6.8.2.7. Sharing Profiles between W95 and NT Workstation 4.0

      5.8.2.7. Sharing Profiles between W95 and NT Workstation 4.0

      WarningNote

      6.9. DOMAIN_CONTROL.txt : Windows NT Domain Control & Samba

      5.9. DOMAIN_CONTROL.txt : Windows NT Domain Control & Samba

      Warningsamba

      samba

      Name

      SAMBA -- A Windows SMB/CIFS fileserver for UNIX
      Samba -- A Windows SMB/CIFS fileserver for UNIX
      smbdsmbd(8)

      The smbd - daemon provides the file and print services to +>smbd daemon provides the file and print services to SMB clients, such as Windows 95/98, Windows NT, Windows for Workgroups or LanManager. The configuration file - for this daemon is described in smb.confsmb.conf(5)

      nmbdnmbd(8)

      daemon provides NetBIOS nameservice and browsing support. The configuration file for this daemon - is described in smb.confsmb.conf(5)

      smbclientsmbclient(1)

      testparmtestparm(1)

      testparm - utility is a simple syntax checker for Samba's - smb.confconfiguration file.

      smb.conf(5) configuration file.

      testprnstestprns(1)

      smbstatussmbstatus(1)

      .

      nmblookupnmblookup(1)

      make_smbcodepagesmbgroupedit(8)

      The make_smbcodepagesmbgroupedit - utility provides a means of creating SMB code page - definition files for your smbd server.

      smbpasswdsmbpasswd(8)

      COMPONENTS

      AVAILABILITY

      If you have access to a WWW viewer (such as Netscape - or Mosaic) then you will also find lots of useful information, +>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

      VERSION

      This man page is correct for version 2.2 of the +>This man page is correct for version 3.0 of the Samba suite.

      CONTRIBUTIONS

      http://devel.samba.org/ - for information on how to do it properly. We prefer patches in - diff -u format.

      CONTRIBUTORS

      AUTHOR

      The original Samba man pages were written by Karl Auer. The man page sources were converted to YODL format (another - excellent piece of Open Source software, available at - ftp://ftp.icce.rug.nl/pub/unix/) and updated for the Samba 2.0 release by Jeremy Allison. The conversion to DocBook for - Samba 2.2 was done by Gerald Carter

      User and Share security level (for servers not in a domain)

      Chapter 5. User and Share security level (for servers not in a domain)

      Chapter 4. User and Share security level (for servers not in a domain)

      A SMB server tells the client at startup what "security level" it is running. There are two options "share level" and "user level". Which @@ -225,7 +226,7 @@ ACCESSKEY="U" WIDTH="33%" ALIGN="right" VALIGN="top" ->How to Configure Samba as a NT4 Primary Domain ControllerSamba as a NT4 or Win2k Primary Domain Controller

      + smb.conf

      smb.conf

      smb.conf
      The smb.conf file is a configuration +> file is a configuration file for the Samba suite. smb.conf contains - runtime configuration information for the Samba programs. The - 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 + 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

      SECTION DESCRIPTIONS

      There are three special sections, [global], [homes] and [printers], which are - described under special sections. The following notes apply to ordinary section descriptions.

      Sections may be designated Sections may be designated guest services, in which case no password is required to access them. A specified - UNIX guest account is used to define access privileges in this case.

      /home/bar. The share is accessed via the share name "foo":

      	 	[foo]
- 		path = /home/bar
- 		read only = no
-	
-
      [foo] + path = /home/bar + read only = no

      The following sample section defines a printable share. The share is readonly, but printable. That is, the only write access permitted is via calls to open, write to and close a - spool file. The guest ok parameter means access will be permitted as the default guest user (specified elsewhere):

      	 	[aprinter]
- 		path = /usr/spool/public
- 		read only = yes
- 		printable = yes
- 		guest ok = yes
-	
-
      [aprinter] + path = /usr/spool/public + read only = yes + printable = yes + guest ok = yes

      SPECIAL SECTIONS

      The [global] section

      The [homes] section

      • If you decide to use a If you decide to use a path = line in your [homes] section then you may find it useful to use the %S macro. For example :

      			 	[homes]
- 			read only = no
-		
-
      [homes] + read only = no

      An important point is that if guest access is specified in the [homes] section, all home directories will be - visible to all clients without a password. In the very unlikely event that this is actually desirable, it - would be wise to also specify read only access.

      Note that the Note that 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

      	 	[printers]
- 			path = /usr/spool/public
- 			guest ok = yes
- 			printable = yes 
-		[printers]
+	path = /usr/spool/public
+	guest ok = yes
+	printable = yes

      All aliases given for a printer in the printcap file are legitimate printer names as far as the server is concerned. If your printing subsystem doesn't work like that, you will have to set up a pseudo-printcap. This is a file consisting of one or more lines like this:

      			        alias|alias|alias|alias...    
-		
-
      alias|alias|alias|alias...

      Each alias should be an acceptable printer name for your printing subsystem. In the [global] section, specify @@ -471,7 +443,7 @@ CLASS="COMPUTEROUTPUT" >

      PARAMETERS

      parameters define the specific attributes of sections.

      Some parameters are specific to the [global] section - (e.g., security). Some parameters are usable - in all sections (e.g., create mode). All others are permissible only in normal sections. For the purposes of the following descriptions the [homes] and [printers] - sections will be considered normal. The letter G in parentheses indicates that a parameter is specific to the - [global] section. The letter S indicates that a parameter can be specified in a service specific - section. Note that all S parameters can also be specified in the [global] section - in which case they will define the default behavior for all services.

      VARIABLE SUBSTITUTIONS

      the name of your NIS home directory server. This is obtained from your NIS auto.map entry. If you have - not compiled Samba with the --with-automount option then this value will be the same as %L.

      NAME MANGLING

      controls if names that have characters that aren't of the "default" case are mangled. For example, if this is yes then a name like "Mail" would be mangled. - Default no.

      controls whether filenames are case sensitive. If they aren't then Samba must do a filename search and match on passed - names. Default no.

      controls what the default case is for new - filenames. Default lower.

      controls if new files are created with the case that the client passes, or if they are forced to be the - "default" case. Default yes.

      yes.

      NOTE ABOUT USERNAME/PASSWORD VALIDATION

      COMPLETE LIST OF GLOBAL PARAMETERS

      COMPLETE LIST OF SERVICE PARAMETERS

      EXPLANATION OF EACH PARAMETER

      abort shutdown script (G)
      >abort shutdown script (G)

      This parameter only exists in the HEAD cvs branch - This a full path name to a script called by - smbd(8) that + This a full path name to a script called by smbd(8) that should stop a shutdown procedure issued by the

      This command will be run as user.

      Default: Default: None.

      Example: addprinter command (G)>addprinter command (G)

      With the introduction of MS-RPC based printing @@ -4771,14 +4780,12 @@ CLASS="PARAMETER" CLASS="FILENAME" >smb.conf file in order that it can be - shared by smbd(8) - smbd(8).

      The is automatically invoked with the following parameter (in - order:

        Default: Default: none

        Example: add share command (G)>add share command (G)

        Samba 2.2.0 introduced the ability to dynamically @@ -5043,9 +5053,12 @@ CLASS="PARAMETER" >.

        Default: Default: none

        Example: add machine script (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 + be run by smbd(8) when a machine is added to it's domain using the administrator username and password method.

        This option is only required when using sam back-ends tied to the @@ -5074,7 +5089,7 @@ TARGET="_top" >

        Default: add machine script = <empty string> +>add machine script = <empty string>

        ads server (G)>ads server (G)

        If this option is specified, samba does @@ -5110,18 +5125,22 @@ CLASS="COMMAND" >add user script (G)>add user script (G)

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

        Normally, a Samba server requires that UNIX users are @@ -5133,19 +5152,26 @@ HREF="smbd.8.html" TARGET="_top" >smbd to create the required UNIX users - ON DEMAND when a user accesses the Samba server.

        In order to use this option, smbd - must In order to use this option, smbd(8) must NOT be set to

        When the Windows user attempts to access the Samba server, - at login (session setup in the SMB protocol) time, smbdsmbd(8) contacts the smbd will - call the specified script AS ROOT, expanding any

        Default: add user script = <empty string> +>add user script = <empty string>

        add group script (G)>add group script (G)

        This is the full pathname to a script that will - be run AS ROOT by smbd(8) by smbd(8) when a new group is requested. It will expand any admin users (S)>admin users (S)

        This is a list of users who will be granted @@ -5299,9 +5335,12 @@ NAME="ADMINUSERS" this list will be able to do anything they like on the share, irrespective of file permissions.

        Default: Default: no admin users

        Example: add user to group script (G)>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) - smbd(8) AS ROOT. Any . + Any %g will be - replaced with the group name and any will be replaced with the group name and + any %u will - be replaced with the user name. +> will be replaced with the user name.

        Default: allow hosts (S)>allow hosts (S)

        Synonym for algorithmic rid base (G)>algorithmic rid base (G)

        This determines how Samba will use its @@ -5404,7 +5447,7 @@ CLASS="COMMAND" >allow trusted domains (G)>allow trusted domains (G)

        This option only takes effect when the announce as (G)>announce as (G)

        This specifies what type of server - nmbd - 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, @@ -5486,7 +5526,7 @@ CLASS="COMMAND" >announce version (G)>announce version (G)

        This specifies the major and minor version numbers @@ -5508,7 +5548,7 @@ CLASS="COMMAND" >auto services (G)>auto services (G)

        This is a synonym for the auth methods (G)>auth methods (G)

        This option allows the administrator to chose what @@ -5550,7 +5590,7 @@ CLASS="PARAMETER" >

        Default: auth methods = <empty string>auth methods = <empty string>

        Example: available (S)>available (S)

        This parameter lets you "turn off" a service. If @@ -5571,9 +5611,12 @@ CLASS="PARAMETER" >available = no, then , then ALL attempts to connect to the service will fail. Such failures are logged.

        bind interfaces only (G)>bind interfaces only (G)

        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 slightly - different ways.

        smbd(8) and name service nmbd(8) in a slightly different ways.

        For name service it causes nmbd.

        For file service it causes smbd(8) - to bind only to the interface list given in the For file service it causes smbd(8) to bind only to the interface list + given in the interfaces parameter. This restricts the networks that @@ -5680,40 +5727,42 @@ CLASS="PARAMETER" >bind interfaces only is set then - unless the network address 127.0.0.1 is added to the interfaces parameter list smbpasswd(8) - and swat(8) may - not work as expected due to the reasons covered below.

        parameter list smbpasswd(8) and swat(8) may not work as expected due to the reasons covered below.

        To change a users SMB password, the smbpasswd - by default connects to the localhost - 127.0.0.1 address as an SMB client to issue the password change request. If bind interfaces only is set then unless the - network address 127.0.0.1 is added to the smbpasswd can be forced to use the primary IP interface - of the local host by using its smbpasswd(8) -r - parameter, with remote machinenmbd at the address - 127.0.0.1 to determine if they are running. - Not adding 127.0.0.1 will cause smbdblocking locks (S)>blocking locks (S)

        This parameter controls the behavior of smbd(8)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.

        block size (S)>block size (S)

        This parameter controls the behavior of - smbd(8)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 option does not change the disk free reporting size, just the block size unit reported to the client.

        Default: block size = 1024

        Example: block size = 65536

        browsable (S)
        >browsable (S)

        See the browse list (G)>browse list (G)

        This controls whether smbd(8)This controls whether smbd(8) will serve a browse list to a client doing a browseable (S)>browseable (S)

        This controls whether this share is seen in @@ -5940,11 +5993,11 @@ CLASS="COMMAND" >case sensitive (S)>case sensitive (S)

        See the discussion in the section NAME MANGLING.

        casesignames (S)>casesignames (S)

        Synonym for change notify timeout (G)>change notify timeout (G)

        This SMB allows a client to tell a server to "watch" a particular directory for any changes and only reply to the SMB request when a change has occurred. Such constant scanning of - a directory is expensive under UNIX, hence an smbd(8)smbd(8) daemon only performs such a scan on each requested directory once every change share command (G)>change share command (G)

        Samba 2.2.0 introduced the ability to dynamically @@ -6125,9 +6177,12 @@ CLASS="PARAMETER" >.

        Default: Default: none

        Example: comment (S)>comment (S)

        This is a text field that is seen next to a share @@ -6161,9 +6216,12 @@ CLASS="PARAMETER" > parameter.

        Default: Default: No comment string

        Example: config file (G)>config file (G)

        This allows you to override the config file @@ -6207,7 +6265,7 @@ CLASS="COMMAND" >copy (S)>copy (S)

        This parameter allows you to "clone" service @@ -6220,9 +6278,12 @@ NAME="COPY" copied must occur earlier in the configuration file than the service doing the copying.

        Default: Default: no value

        Example: create mask (S)>create mask (S)

        A synonym for this parameter is @@ -6253,9 +6314,12 @@ CLASS="PARAMETER" 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 be removed from the modes set on a file when it is created.

        create mode (S)>create mode (S)

        This is a synonym for csc policy (S)>csc policy (S)

        This stands for 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.

        deadtime (G)>deadtime (G)

        The value of the parameter (a decimal integer) @@ -6429,7 +6496,7 @@ CLASS="COMMAND" >debug hires timestamp (G)>debug hires timestamp (G)

        Sometimes the timestamps in the log messages @@ -6457,7 +6524,7 @@ CLASS="COMMAND" >debug pid (G)>debug pid (G)

        When using only one log file for more then one @@ -6489,7 +6556,7 @@ CLASS="COMMAND" >debug timestamp (G)>debug timestamp (G)

        Samba debug log messages are timestamped @@ -6514,7 +6581,7 @@ CLASS="COMMAND" >debug uid (G)>debug uid (G)

        Samba is sometimes run as root and sometime @@ -6542,7 +6609,7 @@ CLASS="COMMAND" >debuglevel (G)>debuglevel (G)

        Synonym for default (G)>default (G)

        A synonym for default case (S)>default case (S)

        See the section on NAME MANGLING. Also note the default devmode (S)>default devmode (S)

        This parameter is only applicable to default service (G)>default service (G)

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

        Example:

        [global]
 	default service = pub
         
 [pub]
-	path = /%S
-

        delete group script (G)
        >delete group script (G)

        This is the full pathname to a script that will - be run AS ROOT by smbd(8) when a group is requested to be deleted. It will expand any 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. +> to the group name passed. + This script is only useful for installations using the Windows NT domain administration tools.

        deleteprinter command (G)
        >deleteprinter command (G)

        With the introduction of MS-RPC based printer @@ -6829,9 +6896,12 @@ CLASS="PARAMETER" >

        Default: Default: none

        Example: delete readonly (S)>delete readonly (S)

        This parameter allows readonly files to be deleted. @@ -6863,7 +6933,7 @@ CLASS="COMMAND" >delete share command (G)>delete share command (G)

        Samba 2.2.0 introduced the ability to dynamically @@ -6967,9 +7037,12 @@ CLASS="PARAMETER" >.

        Default: Default: none

        Example: delete user script (G)>delete user script (G)

        This is the full pathname to a script that will - be run by smbd(8) - when managing user's with remote RPC (NT) tools. + be run by smbd(8) when managing users + with remote RPC (NT) tools.

        This script is called when a remote client removes a user @@ -7009,7 +7081,7 @@ CLASS="COMMAND" >

        Default: delete user script = <empty string> +>delete user script = <empty string>

        delete user from group script (G)>delete user from group script (G)

        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) - smbd(8) AS ROOT. Any . + Any %g will be - replaced with the group name and any will be replaced with the group name and + any %u will - be replaced with the user name. +> will be replaced with the user name.

        Default: delete veto files (S)>delete veto files (S)

        This option is used when Samba is attempting to @@ -7126,7 +7202,7 @@ CLASS="COMMAND" >deny hosts (S)>deny hosts (S)

        Synonym for dfree command (G)>dfree command (G)

        The

        Note: Your script should Note: Your script should NOT be setuid or setgid and should be owned by (and writeable only by) root!

        Default: Default: By default internal routines for determining the disk capacity and remaining space will be used.

        Example:

        Where the script dfree (which must be made executable) could be:

         
-		#!/bin/sh
-		df $1 | tail -1 | awk '{print $2" "$4}'
-

        or perhaps (on Sys V based systems):

         
-		#!/bin/sh
-		/usr/bin/df -k $1 | tail -1 | awk '{print $3" "$5}'
-

        Note that you may have to replace the command names @@ -7239,7 +7301,7 @@ CLASS="PROGRAMLISTING" >directory (S)>directory (S)

        Synonym for directory mask (S)>directory mask (S)

        This parameter is the octal modes which are @@ -7268,9 +7330,12 @@ NAME="DIRECTORYMASK" 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 directory. Any bit not set here will be removed from the modes set on a directory when it is created.

        directory mode (S)>directory mode (S)

        Synonym for directory security mask (S)>directory security mask (S)

        This parameter controls what UNIX permission bits @@ -7396,9 +7461,12 @@ NAME="DIRECTORYSECURITYMASK" meaning a user is allowed to modify all the user/group/world permissions on a directory.

        Note that users who can access the Samba server through other means can easily bypass this restriction, so it is primarily useful for standalone "appliance" systems. @@ -7450,7 +7518,7 @@ CLASS="COMMAND" >disable netbios (G)>disable netbios (G)

        Enabling this parameter will disable netbios support @@ -7475,7 +7543,7 @@ CLASS="COMMAND" >disable spoolss (G)>disable spoolss (G)

        Enabling this parameter will disable Samba's support @@ -7487,9 +7555,12 @@ NAME="DISABLESPOOLSS" Wizard or by using the NT printer properties dialog window. It will also disable the capability of Windows NT/2000 clients to download print drivers from the Samba host upon demand. - Be very careful about enabling this parameter.

        display charset (G)>display charset (G)

        Specifies the charset that samba will use @@ -7533,18 +7604,19 @@ CLASS="COMMAND" >dns proxy (G)>dns proxy (G)

        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.

        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 characters, so the DNS name (or DNS alias) can likewise only be @@ -7576,7 +7648,7 @@ CLASS="COMMAND" >domain logons (G)>domain logons (G)

        If set to domain master (G)>domain master (G)

        Tell nmbd(8)Tell smbd(8) to enable WAN-wide browse list collation. Setting this option causes nmbd their local browse lists, - and then ask smbd(8) - for a complete copy of the browse list for the whole wide area - network. Browser clients will then contact their local master browser, - and will receive the domain-wide browse list, instead of just the list - for their broadcast-isolated subnet.

        smbd(8) for a complete copy of the browse + list for the whole wide area network. Browser clients will then contact + their local master browser, and will receive the domain-wide browse list, + instead of just the list for their broadcast-isolated subnet.

        Note that Windows NT Primary Domain Controllers expect to be able to claim this dont descend (S)>dont descend (S)

        There are certain directories on some systems @@ -7743,10 +7812,13 @@ CLASS="FILENAME" >. Experimentation is the best policy :-)

        Default: Default: none (i.e., all directories are OK to descend)

        Example: dos charset (G)>dos charset (G)

        DOS SMB clients assume the server has @@ -7768,11 +7840,12 @@ NAME="DOSCHARSET" >

        The default depends on which charsets you have instaled. Samba tries to use charset 850 but falls back to ASCII in - case it is not available. Run testparm(1) - testparm(1) to check the default on your system.

        dos filemode (S)>dos filemode (S)

        The default behavior in Samba is to provide @@ -7803,21 +7876,19 @@ CLASS="COMMAND" >dos filetime resolution (S)>dos filetime resolution (S)

        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 - resolution is made to smbd(8) - smbd(8).

        This option is mainly used as a compatibility option for Visual @@ -7840,7 +7911,7 @@ CLASS="COMMAND" >dos filetimes (S)>dos filetimes (S)

        Under DOS and Windows, if a user can write to a @@ -7854,10 +7925,12 @@ CLASS="COMMAND" on behalf of is not the file owner. Setting this option to yes allows DOS semantics and smbd allows DOS semantics and smbd(8) will change the file timestamp as DOS requires.

        encrypt passwords (G)>encrypt passwords (G)

        This boolean controls whether encrypted passwords @@ -7884,29 +7957,25 @@ CLASS="FILENAME" > shipped with the source code.

        In order for encrypted passwords to work correctly - smbd(8)smbd(8) must either - have access to a local smbpasswd(5) - file (see the smbpasswd(8)smbpasswd(5) file (see the smbpasswd(8) program for information on how to set up and maintain this file), or set the enhanced browsing (G)>enhanced browsing (G)

        This option enables a couple of enhancements to @@ -7958,7 +8027,7 @@ CLASS="COMMAND" >enumports command (G)>enumports command (G)

        The concept of a "port" is fairly foreign @@ -7990,9 +8059,12 @@ CLASS="PARAMETER" to standard output. This listing will then be used in response to the level 1 and 2 EnumPorts() RPC.

        Default: Default: no enumports command

        Example: exec (S)>exec (S)

        This is a synonym for fake directory create times (S)>fake directory create times (S)

        NTFS and Windows VFAT file systems keep a create @@ -8060,7 +8132,7 @@ CLASS="COMMAND" >fake oplocks (S)>fake oplocks (S)

        Oplocks are the way that SMB clients get permission @@ -8113,19 +8185,18 @@ CLASS="COMMAND" >follow symlinks (S)>follow symlinks (S)

        This parameter allows the Samba administrator - to stop smbd(8) - from following symbolic links in a particular share. Setting this + to stop smbd(8) from following symbolic + links in a particular share. Setting this parameter to noforce create mode (S)>force create mode (S)

        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 or having its @@ -8214,13 +8288,16 @@ CLASS="COMMAND" >force directory mode (S)>force directory mode (S)

        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 @@ -8273,7 +8350,7 @@ CLASS="COMMAND" >force directory security mode (S)>force directory security mode (S)

        This parameter controls what UNIX permission bits @@ -8290,9 +8367,12 @@ NAME="FORCEDIRECTORYSECURITYMODE" allows a user to modify all the user/group/world permissions on a directory without restrictions.

        Note that users who can access the Samba server through other means can easily bypass this restriction, so it is primarily useful for standalone "appliance" systems. @@ -8341,7 +8421,7 @@ CLASS="COMMAND" >force group (S)>force group (S)

        This specifies a UNIX group name that will be @@ -8402,9 +8482,12 @@ CLASS="PARAMETER" >.

        Default: Default: no forced group

        Example: force security mode (S)>force security mode (S)

        This parameter controls what UNIX permission @@ -8434,9 +8517,12 @@ NAME="FORCESECURITYMODE" and allows a user to modify all the user/group/world permissions on a file, with no restrictions.

        Note that users who can access the Samba server through other means can easily bypass this restriction, so it is primarily useful for standalone "appliance" systems. @@ -8485,7 +8571,7 @@ CLASS="COMMAND" >force user (S)>force user (S)

        This specifies a UNIX user name that will be @@ -8515,9 +8601,12 @@ CLASS="PARAMETER" >

        Default: Default: no forced user

        Example: fstype (S)>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) - smbd(8) when a client queries the filesystem type for a share. The default type is getwd cache (G)>getwd cache (G)

        This is a tuning option. When this is enabled a @@ -8600,7 +8687,7 @@ CLASS="COMMAND" >group (S)>group (S)

        Synonym for guest account (S)>guest account (S)

        This is a username which will be used for access @@ -8656,10 +8743,13 @@ CLASS="COMMAND" many parts of the system require this value to be constant for correct operation.

        Default: Default: specified at compile time, usually "nobody"

        Example: guest ok (S)>guest ok (S)

        If this parameter is .

        See the section below on This paramater nullifies the benifits of setting + restrict + anonymous = 2

        See the section below on guest only (S)>guest only (S)

        If this parameter is hide dot files (S)>hide dot files (S)

        This is a boolean parameter that controls whether @@ -8762,7 +8864,7 @@ CLASS="COMMAND" >hide files(S)>hide files(S)

        This is a list of files or directories that are not @@ -8811,9 +8913,12 @@ CLASS="PARAMETER" >.

        Default: Default: no file are hidden

        Example: hide local users(G)>hide local users(G)

        This parameter toggles the hiding of local UNIX @@ -8850,7 +8955,7 @@ CLASS="COMMAND" >hide unreadable (G)>hide unreadable (G)

        This parameter prevents clients from seeing the @@ -8865,7 +8970,7 @@ CLASS="COMMAND" >hide unwriteable files (G)>hide unwriteable files (G)

        This parameter prevents clients from seeing @@ -8882,7 +8987,7 @@ CLASS="COMMAND" >hide special files (G)>hide special files (G)

        This parameter prevents clients from seeing @@ -8899,7 +9004,7 @@ CLASS="COMMAND" >homedir map (G)>homedir map (G)

        If is yes, and smbd(8), and smbd(8) is also acting as a Win95/98

        NOTE :A working NIS client is required on the system for this option to work.

        Default: homedir map = <empty string>homedir map = <empty string>

        Example: host msdfs (G)>host msdfs (G)

        This boolean parameter is only available @@ -9022,7 +9129,7 @@ CLASS="COMMAND" >hostname lookups (G)>hostname lookups (G)

        Specifies whether samba should use (expensive) @@ -9051,7 +9158,7 @@ CLASS="COMMAND" >hosts allow (S)>hosts allow (S)

        A synonym for this parameter is

        You can also specify hosts by network/netmask pairs and by netgroup names if your system supports netgroups. The - EXCEPT keyword can also be used to limit a wildcard list. The following examples may provide some help:

        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.

        See testparm(1) for a way of testing your host access + to see if it does what you expect.

        Default: Default: none (i.e., all hosts permitted access)

        Example: hosts deny (S)>hosts deny (S)

        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 list takes precedence.

        Default: Default: none (i.e., no hosts specifically excluded)

        Example: hosts equiv (G)>hosts equiv (G)

        If this global parameter is a non-null string, @@ -9228,9 +9345,12 @@ CLASS="PARAMETER" > may be useful for NT clients which will not supply passwords to Samba.

        NOTE : The use of option be only used if you really know what you are doing, or perhaps on a home network where you trust - your spouse and kids. And only if you really trust them :-).

        Default: Default: no host equivalences

        Example: include (G)>include (G)

        This allows you to include one config file @@ -9293,9 +9419,12 @@ CLASS="PARAMETER" >.

        Default: Default: no file included

        Example: inherit acls (S)>inherit acls (S)

        This parameter can be used to ensure @@ -9330,7 +9459,7 @@ CLASS="COMMAND" >inherit permissions (S)>inherit permissions (S)

        The permissions on new files and directories @@ -9405,9 +9534,12 @@ CLASS="PARAMETER" as usual.

        Note that the setuid bit is Note that the setuid bit is never set via inheritance (the code explicitly prohibits this).

        interfaces (G)>interfaces (G)

        This option allows you to override the default @@ -9527,23 +9659,29 @@ CLASS="PARAMETER" >.

        Default: Default: all active interfaces except 127.0.0.1 that are broadcast capable

        invalid users (S)
        >invalid users (S)

        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 '+' is interpreted only by looking in the UNIX group database. A name starting with - '&' is interpreted only by looking in the NIS netgroup database + '&' is interpreted only by looking in the NIS netgroup database (this requires NIS to be working on your system). The characters - '+' and '&' may be used at the start of the name in either order + '+' and '&' may be used at the start of the name in either order so the value +&group+&group means check the UNIX group database, followed by the NIS netgroup database, and the value &+group&+group means check the NIS netgroup database, followed by the UNIX group database (the @@ -9592,9 +9730,12 @@ CLASS="PARAMETER" >.

        Default: Default: no invalid users

        Example: keepalive (G)>keepalive (G)

        The value of the parameter (an integer) represents @@ -9647,7 +9788,7 @@ CLASS="COMMAND" >kernel oplocks (G)>kernel oplocks (G)

        For UNIXes that support kernel based to be broken whenever a local UNIX process or NFS operation - accesses a file that smbd(8) - has oplocked. This allows complete data consistency between - SMB/CIFS, NFS and local file access (and is a smbd(8) has oplocked. This allows complete + data consistency between SMB/CIFS, NFS and local file access (and is + a very - cool feature :-).

        cool feature :-).

        This parameter defaults to lanman auth (G)>lanman auth (G)

        This parameter determines whether or not smbd will - attempt to authenticate users using the LANMAN password hash. - If disabled, only clients which support NT password hashes (e.g. Windows - NT/2000 clients, smbclient, etc... but not Windows 95/98 or the MS DOS - network client) will be able to connect to the Samba host.

        This parameter determines whether or not smbd(8) will attempt to authenticate users + using the LANMAN password hash. If disabled, only clients which support NT + password hashes (e.g. Windows NT/2000 clients, smbclient, etc... but not + Windows 95/98 or the MS DOS network client) will be able to connect to the Samba host.

        Default : large readwrite (G)>large readwrite (G)

        This parameter determines whether or not smbd - supports the new 64k streaming read and write varient SMB requests introduced +>This parameter determines whether or not smbd(8) supports the new 64k streaming + read and write varient 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 @@ -9767,7 +9912,7 @@ CLASS="COMMAND" >ldap admin dn (G)>ldap admin dn (G)

        The private/secrets.tdb file. See the - smbpasswd(8) man - page for more information on how to accmplish this. + smbpasswd(8) man page for more information on how + to accmplish this.

        Default : Default : none

        ldap filter (G)
        >ldap filter (G)

        This parameter specifies the RFC 2254 compliant LDAP search filter. @@ -9825,14 +9972,14 @@ CLASS="CONSTANT" >

        Default : ldap filter = (&(uid=%u)(objectclass=sambaAccount))ldap filter = (&(uid=%u)(objectclass=sambaAccount))

        ldap port (G)
        >ldap port (G)

        This parameter is only available if Samba has been @@ -9876,7 +10023,7 @@ CLASS="COMMAND" >ldap server (G)>ldap server (G)

        This parameter is only available if Samba has been @@ -9900,14 +10047,17 @@ CLASS="COMMAND" >ldap ssl (G)>ldap ssl (G)

        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 ldap suffix (G)>ldap suffix (G)

        Specifies where user and machine accounts are added to the tree. Can be overriden by ldap machine suffix. It also used as the base dn for all ldap searches.

        Default : Default : none

        ldap user suffix (G)
        >ldap user suffix (G)

        It specifies where users are added to the tree.

        Default : Default : none

        ldap machine suffix (G)
        >ldap machine suffix (G)

        It specifies where machines should be added to the ldap tree.

        Default : Default : none

        ldap passwd sync (G)
        >ldap passwd sync (G)

        This option is used to define whether @@ -10098,7 +10257,7 @@ CLASS="COMMAND" >ldap trust ids (G)>ldap trust ids (G)

        Normally, Samba validates each entry @@ -10127,7 +10286,7 @@ CLASS="COMMAND" >level2 oplocks (S)>level2 oplocks (S)

        This parameter controls whether Samba supports @@ -10211,16 +10370,15 @@ CLASS="COMMAND" >lm announce (G)>lm announce (G)

        This parameter determines if nmbd(8)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 @@ -10291,7 +10449,7 @@ CLASS="COMMAND" >lm interval (G)>lm interval (G)

        If Samba is set to produce Lanman announce @@ -10339,13 +10497,13 @@ CLASS="COMMAND" >load printers (G)>load printers (G)

        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.

        local master (G)>local master (G)

        This option allows nmbd(8)This option allows nmbd(8) to try and become a local master browser on a subnet. If set to yes doesn't - mean that Samba will become the local master browser on a subnet, just that nmbd will will participate in elections for local master browser.

        Setting this value to nmbd - never to become a local master browser.

        Default: lock dir (G)>lock dir (G)

        Synonym for lock directory (G)>lock directory (G)

        This option specifies the directory where lock @@ -10466,7 +10632,7 @@ CLASS="COMMAND" >lock spin count (G)>lock spin count (G)

        This parameter controls the number of times @@ -10489,7 +10655,7 @@ CLASS="COMMAND" >lock spin time (G)>lock spin time (G)

        The time in microseconds that smbd should @@ -10516,7 +10682,7 @@ CLASS="COMMAND" >locking (S)>locking (S)

        This controls whether or not locking will be @@ -10536,13 +10702,19 @@ CLASS="COMMAND" >, real locking will be performed by the server.

        This option This option may be useful for read-only - filesystems which may not need locking (such as CDROM drives), although setting this parameter of log file (G)>log file (G)

        This option allows you to override the name @@ -10582,7 +10754,7 @@ CLASS="COMMAND" >log level (G)>log level (G)

        The value of the parameter (a astring) allows @@ -10608,7 +10780,7 @@ CLASS="COMMAND" >logon drive (G)>logon drive (G)

        This parameter specifies the local path to @@ -10640,7 +10812,7 @@ CLASS="COMMAND" >logon home (G)>logon home (G)

        This parameter specifies the home directory @@ -10721,7 +10893,7 @@ CLASS="COMMAND" >logon path (G)>logon path (G)

        This parameter specifies the home directory @@ -10767,9 +10939,12 @@ CLASS="FILENAME" >Thereafter, the directories and any of the contents can, if required, be made read-only. It is not advisable that the NTuser.dat file be made read-only - rename it to NTuser.man to - achieve the desired effect (a MANdatory profile).

        logon script (G)>logon script (G)

        This parameter specifies the batch file (.bat) or @@ -10859,9 +11034,12 @@ CLASS="COMMAND" >This option is only useful if Samba is set up as a logon server.

        Default: Default: no logon script defined

        Example: lppause command (S)>lppause command (S)

        This parameter specifies the command to be @@ -10971,7 +11149,7 @@ CLASS="COMMAND" >lpq cache time (G)>lpq cache time (G)

        This controls how long lpq info will be cached @@ -11036,7 +11214,7 @@ CLASS="COMMAND" >lpq command (S)>lpq command (S)

        This parameter specifies the command to be @@ -11106,7 +11284,9 @@ CLASS="PARAMETER" > parameter.

        Default: Default: depends on the setting of printing

        Example: lpresume command (S)>lpresume command (S)

        This parameter specifies the command to be @@ -11222,7 +11403,7 @@ CLASS="COMMAND" >lprm command (S)>lprm command (S)

        This parameter specifies the command to be @@ -11265,7 +11446,9 @@ CLASS="PARAMETER" > parameter.

        Default: Default: depends on the setting of

        Example 1: machine password timeout (G)>machine password timeout (G)

        If a Samba server is a member of a Windows @@ -11313,14 +11497,12 @@ CLASS="FILENAME" will be changed, in seconds. The default is one week (expressed in seconds), the same as a Windows NT Domain member server.

        See also smbpasswd(8) - See also smbpasswd(8), and the security = domainmagic output (S)>magic output (S)

        This parameter specifies the name of a file @@ -11362,7 +11544,7 @@ CLASS="PARAMETER" >

        Default: magic output = <magic script name>.out +>magic output = <magic script name>.out

        magic script (S)>magic script (S)

        This parameter specifies the name of a file which, @@ -11401,24 +11583,36 @@ CLASS="PARAMETER" >Note that some shells are unable to interpret scripts containing CR/LF instead of CR as the end-of-line marker. Magic scripts must be executable - as is on the host, which for some hosts and some shells will require filtering at the DOS end.

        Magic scripts are Magic scripts are EXPERIMENTAL and - should NOT be relied upon.

        Default: Default: None. Magic scripts disabled.

        Example: mangle case (S)>mangle case (S)

        See the section on NAME MANGLING

        mangled map (S)>mangled map (S)

        This is for those who want to directly map UNIX @@ -11485,9 +11679,12 @@ CLASS="FILENAME" > off the ends of filenames on some CDROMs (only visible under some UNIXes). To do this use a map of (*;1 *;).

        Default: Default: no mangled map

        Example: mangled names (S)>mangled names (S)

        This controls whether non-DOS names under UNIX @@ -11507,7 +11704,7 @@ NAME="MANGLEDNAMES" or whether non-DOS names should simply be ignored.

        See the section on NAME MANGLING for details on how to control the mangling process.

        mangling method (G)>mangling method (G)

        controls the algorithm used for the generating @@ -11610,7 +11807,7 @@ CLASS="COMMAND" >mangle prefix (G)>mangle prefix (G)

        controls the number of prefix @@ -11633,14 +11830,16 @@ CLASS="COMMAND" >mangled stack (G)>mangled stack (G)

        This parameter controls the number of mangled names - that should be cached in the Samba server smbd(8)smbd(8).

        This stack is a list of recently mangled base names @@ -11670,15 +11869,18 @@ CLASS="COMMAND" >mangling char (S)>mangling char (S)

        This controls what character is used as - the magic character in name mangling. The default is a '~' but this may interfere with some software. Use this option to set @@ -11698,7 +11900,7 @@ CLASS="COMMAND" >map archive (S)>map archive (S)

        This controls whether the DOS archive attribute @@ -11734,7 +11936,7 @@ CLASS="COMMAND" >map hidden (S)>map hidden (S)

        This controls whether DOS style hidden files @@ -11766,7 +11968,7 @@ CLASS="COMMAND" >map system (S)>map system (S)

        This controls whether DOS style system files @@ -11798,7 +12000,7 @@ CLASS="COMMAND" >map to guest (G)>map to guest (G)

        This parameter is only useful in .

        This parameter can take three different values, which tell - smbd(8)smbd(8) what to do with user login requests that don't match a valid UNIX user in some way.

        hate you if you set the modes other than share. This is because in these modes the name of the resource being - requested is not sent to the server until after the server has successfully authenticated the client so the server cannot make authentication decisions at the correct time (connection @@ -11926,7 +12136,7 @@ CLASS="COMMAND" >max connections (S)>max connections (S)

        This option allows the number of simultaneous @@ -11966,7 +12176,7 @@ CLASS="COMMAND" >max disk size (G)>max disk size (G)

        This option allows you to put an upper limit @@ -12011,7 +12221,7 @@ CLASS="COMMAND" >max log size (G)>max log size (G)

        This option (an integer in kilobytes) specifies @@ -12038,7 +12248,7 @@ CLASS="COMMAND" >max mux (G)>max mux (G)

        This option controls the maximum number of @@ -12054,14 +12264,16 @@ CLASS="COMMAND" >max open files (G)>max open files (G)

        This parameter limits the maximum number of - open files that one smbd(8)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 @@ -12080,18 +12292,17 @@ CLASS="COMMAND" >max print jobs (S)>max print jobs (S)

        This parameter limits the maximum number of jobs allowable in a Samba printer queue at any given moment. - If this number is exceeded, smbd(8)smbd(8) will remote "Out of Space" to the client. See all max protocol (G)>max protocol (G)

        The value of the parameter (a string) is the highest @@ -12150,9 +12361,12 @@ CLASS="CONSTANT" >LANMAN1: First : First modern version of the protocol. Long filename support.

        max smbd processes (G)>max smbd processes (G)

        This parameter limits the maximum number of @@ -12219,10 +12433,12 @@ CLASS="COMMAND" 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 smbdsmbd(8) associated with him or her to handle connections to all shares from a given host.

        max ttl (G)>max ttl (G)

        This option tells nmbd(8)This option tells nmbd(8) what the default 'time to live' of NetBIOS names should be (in seconds) when max wins ttl (G)>max wins ttl (G)

        This option tells nmbd(8) - This option tells smbd(8) when acting as a WINS server ( max xmit (G)>max xmit (G)

        This option controls the maximum packet size @@ -12333,7 +12552,7 @@ CLASS="COMMAND" >message command (G)>message command (G)

        This specifies what command to run when the @@ -12347,7 +12566,7 @@ NAME="MESSAGECOMMAND" >

        message command = csh -c 'xedit %s;rm %s' &message command = csh -c 'xedit %s;rm %s' &

        xedit, then - removes it afterwards. NOTE THAT IT IS VERY IMPORTANT THAT THIS COMMAND RETURN IMMEDIATELY. That's why I - have the '&' on the end. If it doesn't return immediately then + have the '&' on the end. If it doesn't return immediately then your PCs may freeze when sending messages (they should recover after 30 seconds, hopefully).

        message command = /bin/mail -s 'message from %f on - %m' root < %s; rm %s

        If you don't have a message command then the message @@ -12440,22 +12662,25 @@ CLASS="COMMAND" >message command = rm %s

        Default: Default: no message command

        Example: message command = csh -c 'xedit %s; - rm %s' &

        min passwd length (G)
        >min passwd length (G)

        Synonym for min password length (G)>min password length (G)

        This option sets the minimum length in characters @@ -12519,7 +12744,7 @@ CLASS="COMMAND" >min print space (S)>min print space (S)

        This sets the minimum amount of free disk @@ -12552,7 +12777,7 @@ CLASS="COMMAND" >min protocol (G)>min protocol (G)

        The value of the parameter (a string) is the @@ -12602,13 +12827,15 @@ CLASS="COMMAND" >min wins ttl (G)>min wins ttl (G)

        This option tells nmbd(8)This option tells nmbd(8) when acting as a WINS server (msdfs proxy (S)>msdfs proxy (S)

        This boolean parameter is only available if @@ -12691,15 +12918,15 @@ CLASS="CONSTANT" Dfs links are specified in the share directory by symbolic links of the form msdfs:serverA\shareA,serverB\shareBmsdfs:serverA\\shareA,serverB\\shareB and so on. For more information on setting up a Dfs tree on Samba, refer to msdfs_setup.html - .

        "Hosting a Microsoft + Distributed File System tree on Samba" document.

        See also name cache timeout (G)>name cache timeout (G)

        Specifies the number of seconds it takes before @@ -12743,7 +12970,7 @@ CLASS="COMMAND" >name resolve order (G)>name resolve order (G)

        This option is used by the programs in the Samba @@ -12848,7 +13075,7 @@ CLASS="COMMAND" >netbios aliases (G)>netbios aliases (G)

        This is a list of NetBIOS names that .

        Default: Default: empty string (no additional names)

        Example: netbios name (G)>netbios name (G)

        This sets the NetBIOS name by which a Samba @@ -12909,9 +13139,12 @@ CLASS="PARAMETER" >.

        Default: Default: machine DNS name

        Example: netbios scope (G)>netbios scope (G)

        This sets the NetBIOS scope that Samba will @@ -12934,7 +13167,7 @@ NAME="NETBIOSSCOPE" >nis homedir (G)>nis homedir (G)

        Get the home share server from a NIS map. For @@ -12978,7 +13211,7 @@ CLASS="COMMAND" >non unix account range (G)>non unix account range (G)

        The non unix account range parameter specifies @@ -12996,7 +13229,7 @@ NAME="NONUNIXACCOUNTRANGE" >

        Default: non unix account range = <empty string> +>non unix account range = <empty string>

        nt acl support (S)>nt acl support (S)

        This boolean parameter controls whether @@ -13031,14 +13264,16 @@ CLASS="COMMAND" >nt pipe support (G)>nt pipe support (G)

        This boolean parameter controls whether - smbd(8)smbd(8) will allow Windows NT clients to connect to the NT SMB specific nt status support (G)>nt status support (G)

        This boolean parameter controls whether null passwords (G)>null passwords (G)

        Allow or disallow client access to accounts that have null passwords.

        See also smbpasswd (5)See also smbpasswd(5).

        Default: obey pam restrictions (G)>obey pam restrictions (G)

        When Samba 2.2 is configured to enable PAM support @@ -13135,7 +13372,7 @@ CLASS="COMMAND" >only user (S)>only user (S)

        This is a boolean option that controls whether @@ -13195,7 +13432,7 @@ CLASS="COMMAND" >only guest (S)>only guest (S)

        A synonym for oplock break wait time (G)>oplock break wait time (G)

        This is a tuning parameter added due to bugs in @@ -13223,10 +13460,13 @@ NAME="OPLOCKBREAKWAITTIME" is the amount of time Samba will wait before sending an oplock break request to such (broken) clients.

        DO NOT CHANGE THIS PARAMETER UNLESS YOU HAVE READ AND UNDERSTOOD THE SAMBA OPLOCK CODE.

        Default: oplock contention limit (S)>oplock contention limit (S)

        This is a This is a very advanced

        In brief it specifies a number, which causes smbd not to - grant an oplock even when requested if the approximate number of - clients contending for an oplock on the same file goes over this +>In brief it specifies a number, which causes smbd(8)not to grant an oplock even when requested + if the 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.

        DO NOT CHANGE THIS PARAMETER UNLESS YOU HAVE READ AND UNDERSTOOD THE SAMBA OPLOCK CODE.

        Default: oplocks (S)>oplocks (S)

        This boolean option tells ntlm auth (G)>ntlm auth (G)

        This parameter determines whether or not smbdThis parameter determines + whether or not smbd(8) will attempt to authenticate users using the NTLM password hash. If disabled, only the lanman password hashes will be used. @@ -13366,7 +13616,8 @@ TARGET="_top" >Please note that at least this option or lanman auth should be enabled in order to be able to log in. +> should + be enabled in order to be able to log in.

        Default : os level (G)>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)nmbd(8) has a chance of becoming a local master browser for the in the local broadcast area.

        Note :By default, Samba will win a local master browsing election over all Microsoft operating systems except a Windows NT 4.0/2000 Domain Controller. This @@ -13426,15 +13682,15 @@ CLASS="COMMAND" >os2 driver map (G)>os2 driver map (G)

        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>

        <nt driver name> = <os2 driver + name>.<device name>

        For example, a valid entry using the HP LaserJet 5 printer driver would appear as

        The need for the file is due to the printer driver namespace problem described in the Samba Printing HOWTO. For more details on OS/2 clients, please - refer to the OS2-Client-HOWTO - containing in the Samba documentation.

        Default: os2 driver map = <empty string> +>os2 driver map = <empty string>

        pam password change (G)>pam password change (G)

        With the addition of better PAM support in Samba 2.2, @@ -13505,25 +13756,28 @@ CLASS="COMMAND" >panic action (G)>panic action (G)

        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.

        smbd(8) or smbd(8) crashes. This is usually used to + draw attention to the fact that a problem occurred.

        Default: panic action = <empty string>panic action = <empty string>

        Example: paranoid server security (G)>paranoid server security (G)

        Some version of NT 4.x allow non-guest users with a bad passowrd. When this option is enabled, samba will not use a broken NT 4.x server as password server, but instead complain - to the logs and exit. + to the logs and exit.

        Disabling this option prevents Samba from making + this check, which involves deliberatly attempting a + bad logon to the remote server.

        Default: paranoid server security = yespassdb backend (G)>passdb backend (G)

        This option allows the administrator to chose which backends to retrieve and store passwords with. This allows (for example) both @@ -13765,23 +14023,30 @@ CLASS="COMMAND" >passwd chat (G)>passwd chat (G)

        This parameter indicates that the share is a @@ -12668,14 +12895,14 @@ CLASS="PARAMETER" >

        Example: msdfs proxy = \otherserver\somesharemsdfs proxy = \\\\otherserver\\someshare

        msdfs root (S)
        >msdfs root (S)

        This string controls the This string controls the "chat" - conversation that takes places between smbdsmbd(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)smbd(8) uses to determine what to send to the yes. This - sequence is then called AS ROOT when the SMB password in the smbpasswd file is being changed, without access to the old password cleartext. This means that root must be able to reset the user's password @@ -13835,16 +14103,16 @@ CLASS="PARAMETER" for the new password. The chat sequence can also contain the standard macros \n\\n, \r\\r, \t \\t and \s\\s to give line-feed, carriage-return, tab and space. The chat sequence string can also contain a '*' which matches any sequence of characters. @@ -13909,14 +14177,14 @@ CLASS="PARAMETER" >

        Default: passwd chat = *new*password* %n\n - *new*password* %n\n *changed*passwd chat = *new*password* %n\\n + *new*password* %n\\n *changed*

        Example: passwd chat = "*Enter OLD password*" %o\n - "*Enter NEW password*" %n\n "*Reenter NEW password*" %n\n "*Password +>passwd chat = "*Enter OLD password*" %o\\n + "*Enter NEW password*" %n\\n "*Reenter NEW password*" %n\\n "*Password changed*"

        passwd chat debug (G)>passwd chat debug (G)

        This boolean specifies if the passwd chat script - parameter is run in debug mode. In this mode the strings passed to and received from the passwd chat are printed - in the smbd(8)smbd(8) log with a passwd program (G)>passwd program (G)

        By specifying the name of another SMB server (such @@ -14216,15 +14504,21 @@ CLASS="PARAMETER" the "LM1.2X002" or the "NT LM 0.12" protocol, and it must be in user level security mode.

        NOTE: Using a password server means your UNIX box (running Samba) is only as secure as your - password server. DO NOT CHOOSE A PASSWORD SERVER THAT YOU DON'T COMPLETELY TRUST.

        Never point a Samba server at itself for password @@ -14281,7 +14575,7 @@ CLASS="PARAMETER" Primary or Backup Domain controllers to authenticate against by doing a query for the name WORKGROUP<1C>WORKGROUP<1C> and then contacting each server returned in the list of IP addresses from the name resolution source.

        Default: password server = <empty string>password server = <empty string>

        path (S)>path (S)

        This parameter specifies a directory to which @@ -14419,9 +14713,12 @@ CLASS="PARAMETER" > if one was specified.

        Default: Default: none

        Example: pid directory (G)>pid directory (G)

        This option specifies the directory where pid @@ -14454,16 +14751,15 @@ CLASS="COMMAND" >posix locking (S)>posix locking (S)

        The smbd(8)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 @@ -14481,7 +14777,7 @@ CLASS="COMMAND" >postexec (S)>postexec (S)

        This option specifies a command to be run @@ -14508,23 +14804,26 @@ CLASS="PARAMETER" .

        Default: Default: none (no command executed)

        Example: postexec = echo \"%u disconnected from %S - from %m (%I)\" >> /tmp/log

        postscript (S)
        >postscript (S)

        This parameter forces a printer to interpret @@ -14547,7 +14846,7 @@ CLASS="COMMAND" >preexec (S)>preexec (S)

        This option specifies a command to be run whenever @@ -14560,7 +14859,7 @@ NAME="PREEXEC" >preexec = csh -c 'echo \"Welcome to %S!\" | - /usr/local/samba/bin/smbclient -M %m -I %I' &

        Of course, this could get annoying after a while :-)

        .

        Default: Default: none (no command executed)

        Example: preexec = echo \"%u connected to %S from %m - (%I)\" >> /tmp/log

        preexec close (S)
        >preexec close (S)

        This boolean option controls whether a non-zero @@ -14624,7 +14926,7 @@ CLASS="COMMAND" >preferred master (G)>preferred master (G)

        This boolean parameter controls if prefered master (G)>prefered master (G)

        Synonym for preload (G)>preload (G)

        This is a list of services that you want to be @@ -14722,9 +15024,12 @@ CLASS="PARAMETER" > option is easier.

        Default: Default: no preloaded services

        Example: preserve case (S)>preserve case (S)

        This controls if new filenames are created @@ -14758,7 +15063,7 @@ CLASS="COMMAND" >

        See the section on NAME MANGLING for a fuller discussion.

        print command (S)>print command (S)

        After a print job has finished spooling to @@ -14800,9 +15105,12 @@ CLASS="COMMAND" >%z - the size of the spooled print job (in bytes)

        The print command The print command MUST contain at least one occurrence of

        print command = echo Printing %s >> +>print command = echo Printing %s >> /tmp/print.log; lpr -P %p %s; rm %s

        print ok (S)>print ok (S)

        Synonym for printable (S)>printable (S)

        If this parameter is printcap (G)>printcap (G)

        Synonym for printcap name (G)>printcap name (G)

        This parameter may be used to override the @@ -15011,7 +15319,7 @@ NAME="PRINTCAPNAME" CLASS="FILENAME" > /etc/printcap). See the discussion of the [printers] section above for reasons why you might want to do this.

        A minimal printcap file would look something like this:

        		print1|My Printer 1
-		print2|My Printer 2
-		print3|My Printer 3
-		print4|My Printer 4
-		print5|My Printer 5
-
        print1|My Printer 1 +print2|My Printer 2 +print3|My Printer 3 +print4|My Printer 4 +print5|My Printer 5

        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: Under AIX the default printcap name is printer admin (S)>printer admin (S)

        This is a list of users that can do anything to @@ -15124,7 +15425,7 @@ NAME="PRINTERADMIN" >

        Default: printer admin = <empty string>printer admin = <empty string>

        printer driver (S)>printer driver (S)

        Note :This is a deprecated parameter and will be removed in the next major release following version 2.2. Please see the instructions in the Samba 2.2. Printing HOWTOprinter driver file (G)>printer driver file (G)

        Note :This is a deprecated parameter and will be removed in the next major release following version 2.2. Please see the instructions in the Samba 2.2. Printing HOWTO.

        Default: Default: None (set in compile).

        Example: printer driver location (S)>printer driver location (S)

        Note :This is a deprecated parameter and will be removed in the next major release following version 2.2. Please see the instructions in the Samba 2.2. Printing HOWTOprinter name (S)>printer name (S)

        This parameter specifies the name of the printer @@ -15343,13 +15656,16 @@ NAME="PRINTERNAME" name given will be used for any printable service that does not have its own printer name specified.

        Default: Default: none (but may be lp on many systems)

        Example: printer (S)>printer (S)

        Synonym for printing (S)>printing (S)

        This parameters controls how printer status @@ -15458,7 +15774,7 @@ TARGET="_top" >This option can be set on a per printer basis

        See also the discussion in the [printers] section.

        private dir (G)>private dir (G)

        This parameters defines the directory @@ -15489,7 +15805,7 @@ CLASS="COMMAND" >protocol (G)>protocol (G)

        Synonym for public (S)>public (S)

        Synonym for queuepause command (S)>queuepause command (S)

        This parameter specifies the command to be @@ -15551,7 +15867,9 @@ CLASS="PARAMETER" path in the command as the PATH may not be available to the server.

        Default: Default: depends on the setting of

        Example: queueresume command (S)>queueresume command (S)

        This parameter specifies the command to be @@ -15608,7 +15927,9 @@ CLASS="PARAMETER" path in the command as the PATH may not be available to the server.

        Default: Default: depends on the setting of

        read bmpx (G)>read bmpx (G)

        This boolean parameter controls whether read list (S)>read list (S)

        This is a list of users that are given read-only @@ -15702,7 +16024,7 @@ CLASS="PARAMETER" >

        Default: read list = <empty string>read list = <empty string>

        Example: read only (S)>read only (S)

        An inverted synonym is printable = yes) - will ALWAYS allow writing to the directory (user privileges permitting), but only via spooling operations.

        read raw (G)>read raw (G)

        This parameter controls whether or not the server @@ -15788,7 +16113,7 @@ CLASS="COMMAND" >read size (G)>read size (G)

        The option realm (G)>realm (G)

        This option specifies the kerberos realm to use. The realm is @@ -15854,7 +16179,7 @@ CLASS="COMMAND" >remote announce (G)>remote announce (G)

        This option allows you to setup

        See the documentation file BROWSING.txtSee the documentation file BROWSING in the

        Default: remote announce = <empty string> +>remote announce = <empty string>

        remote browse sync (G)>remote browse sync (G)

        This option allows you to setup

        Default: remote browse sync = <empty string> +>remote browse sync = <empty string>

        restrict anonymous (G)>restrict anonymous (G)

        This is a integer parameter, and @@ -15987,7 +16313,7 @@ CLASS="COMMAND" >root (G)>root (G)

        Synonym for root dir (G)>root dir (G)

        Synonym for root directory (G)>root directory (G)

        The server will root directory - option, including some files needed for complete operation of the server. To maintain full operability of the server you will need to mirror some system files @@ -16092,7 +16421,7 @@ CLASS="COMMAND" >root postexec (S)>root postexec (S)

        This is the same as the

        Default: root postexec = <empty string> +>root postexec = <empty string>

        root preexec (S)>root preexec (S)

        This is the same as the

        Default: root preexec = <empty string> +>root preexec = <empty string>

        root preexec close (S)>root preexec close (S)

        This is the same as the security (G)>security (G)

        This option affects how clients respond to @@ -16214,11 +16543,12 @@ CLASS="FILENAME" > file.

        The option sets the "security mode bit" in replies to - protocol negotiations with smbd(8) - smbd(8) to turn share level security on or off. Clients decide based on this bit whether (and how) to transfer user and password information to the server.

        It is possible to use smbd in a in a hybrid mode where it is offers both user and share level security under different >SECURITY = SHARE

        When clients connect to a share level security server they @@ -16333,9 +16669,12 @@ CLASS="COMMAND" >Note that smbd ALWAYS uses a valid UNIX user to act on behalf of the client, even in

      • If the client did a previous 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.

        , then this guest user will be used, otherwise access is denied.

        Note that it can be Note that it can be very confusing in share-level security as to which UNIX username will eventually be used in granting access.

        See also the section NOTE ABOUT USERNAME/PASSWORD VALIDATION.

        >SECURITY = USER

        This is the default security setting in Samba 2.2. +>This is the default security setting in Samba 3.0. With user-level security a client must first "log-on" with a valid username and password (which can be mapped using the

        Note that the name of the resource being - requested is not sent to the server until after the server has successfully authenticated the client. This is why guest shares don't work in user level security without allowing @@ -16545,62 +16899,87 @@ CLASS="PARAMETER" > parameter for details on doing this.

        See also the section NOTE ABOUT USERNAME/PASSWORD VALIDATION.

        >SECURITY = SERVER +>SECURITY = DOMAIN +

        In this mode Samba will try to validate the username/password - by passing it to another SMB server, such as an NT box. If this - fails it will revert to security = user, but 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 - documentation file in the docs/ directory - ENCRYPTION.txt for details on how to set this - up.

        This mode will only work correctly if net(8) has been used to add this + machine into a Windows NT Domain. It expects the encrypted passwords + parameter to be set to yes. In this + mode Samba will try to validate the username/password by passing + it to a Windows NT Primary or Backup Domain Controller, in exactly + the same way that a Windows NT Server would do.

        Note that from the client's point of - view that a valid UNIX user must still + exist as well as the account on the Domain Controller to allow + Samba to have a valid UNIX account to map file access to.

        Note that from the client's point + of view security = serversecurity = domain is the same as security = user. It only affects how the server deals - with the authentication, it does not in any way affect what the - client sees.

        security = user +         . It only affects how the server deals with the authentication, + it does not in any way affect what the client sees.

        Note that the name of the resource being - requested is not sent to the server until after the server has successfully authenticated the client. This is why guest shares don't work in user level security without allowing @@ -16625,7 +17004,7 @@ CLASS="PARAMETER" > parameter for details on doing this.

        See also the section NOTE ABOUT USERNAME/PASSWORD VALIDATION.

        parameter.

        >SECURITY = DOMAIN +>SECURITY = SERVER

        This mode will only work correctly if smbpasswd(8) has been used to add this - machine into a Windows NT Domain. It expects the In this mode Samba will try to validate the username/password + by passing it to another SMB server, such as an NT box. If this + fails it will revert to security = + user. It expects the parameter to be set to parameter to be set to + yes. In this - mode Samba will try to validate the username/password by passing - it to a Windows NT Primary or Backup Domain Controller, in exactly - the same way that a Windows NT Server would do.

        , unless the remote 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 + documentation file in the docs/ directory + ENCRYPTION.txt for details on how to set this + up.

        Note that a valid UNIX user must still - exist as well as the account on the Domain Controller to allow - Samba to have a valid UNIX account to map file access to.

        this mode of operation + has significant pitfalls, due to the fact that is + activly initiates a man-in-the-middle attack on the + remote SMB server. In particular, this mode of + operation can cause significant resource consuption on + the PDC, as it must maintain an active connection for + the duration of the user's session. Furthermore, if + this connection is lost, there is no way to + reestablish it, and futher authenticaions to the Samba + server may fail. (From a single client, till it + disconnects).

        Note that from the client's point - of view that from the client's point of + view security = domainsecurity = server is the same as security = user - . It only affects how the server deals with the authentication, - it does not in any way affect what the client sees.

        security = user        . It only affects how the server deals + with the authentication, it does not in any way affect what the + client sees.

        Note that the name of the resource being - requested is not sent to the server until after the server has successfully authenticated the client. This is why guest shares don't work in user level security without allowing @@ -16731,22 +17148,8 @@ CLASS="PARAMETER" parameter for details on doing this.

        BUG: There is currently a bug in the - implementation of security = domain with respect - to multi-byte character set usernames. The communication with a - Domain Controller must be done in UNICODE and Samba currently - does not widen multi-byte user names to UNICODE correctly, thus - a multi-byte username will not be recognized correctly at the - Domain Controller. This issue will be addressed in a future release.

        See also the section NOTE ABOUT USERNAME/PASSWORD VALIDATION.

        security mask (S)>security mask (S)

        This parameter controls what UNIX permission @@ -16802,9 +17205,12 @@ NAME="SECURITYMASK" a user to modify all the user/group/world permissions on a file.

        Note that users who can access the Samba server through other means can easily bypass this restriction, so it is primarily useful for standalone @@ -16856,7 +17262,7 @@ CLASS="COMMAND" >server string (G)>server string (G)

        This controls what string will show up in the @@ -16901,7 +17307,7 @@ CLASS="COMMAND" >set directory (S)>set directory (S)

        If share modes (S)>share modes (S)

        This enables or disables the honoring of @@ -16971,9 +17377,12 @@ CLASS="CONSTANT" >This option gives full share compatibility and enabled by default.

        You should You should NEVER turn this parameter off as many Windows applications will break if you do so.

        short preserve case (S)>short preserve case (S)

        This boolean parameter controls if new files @@ -17012,7 +17421,7 @@ CLASS="COMMAND" names are lowered.

        See the section on NAME MANGLING.

        show add printer wizard (G)>show add printer wizard (G)

        With the introduction of MS-RPC based printing support @@ -17056,9 +17465,12 @@ CLASS="PARAMETER" > 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 administrative privilege on an individual printer.

        shutdown script (G)>shutdown script (G)

        This parameter only exists in the HEAD cvs branch This a full path name to a script called by %r will be substituted with the - switch -r. It means reboot after shutdown for NT.

        %f         will be substituted with the - switch -f. It means force the shutdown even if applications do not respond for NT.

        Default: Default: None.

        Example:

        Shutdown script example: - 
        		#!/bin/bash
+>#!/bin/bash
 		
-		$time=0
-		let "time/60"
-		let "time++"
+$time=0
+let "time/60"
+let "time++"
 
-		/sbin/shutdown $3 $4 +$time $1 &
-
        Shutdown does not return so we need to launch it in background.

        smb passwd file (G)>smb passwd file (G)

        This option sets the path to the encrypted @@ -17234,7 +17648,7 @@ CLASS="COMMAND" >smb ports (G)>smb ports (G)

        Specifies which ports the server should listen on @@ -17250,7 +17664,7 @@ CLASS="COMMAND" >socket address (G)>socket address (G)

        This option allows you to control what @@ -17271,7 +17685,7 @@ CLASS="COMMAND" >socket options (G)>socket options (G)

        This option allows you to set socket options @@ -17352,9 +17766,12 @@ TARGET="_top" >

        • The name of a program that can be used to set @@ -14027,18 +14300,24 @@ CLASS="PARAMETER" 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 Also note that many passwd programs insist in reasonable passwords, such as a minimum length, or the inclusion of mixed case chars and digits. This can pose a problem as some clients (such as Windows for Workgroups) uppercase the password before sending it.

        Note that if the yes then this program is called then this program is called AS ROOT before the SMB password in the unix password sync parameter - is set this parameter MUST USE ABSOLUTE PATHS - for ALL programs called, and must be examined for security implications. Note that by default password level (G)>password level (G)

        Some client/server combinations have difficulty @@ -14176,7 +14464,7 @@ CLASS="COMMAND" >password server (G)>password server (G)

      Those marked with a 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 @@ -17402,7 +17819,7 @@ CLASS="COMMAND" >source environment (G)>source environment (G)

      This parameter causes Samba to set environment @@ -17426,9 +17843,12 @@ CLASS="COMMAND" >SAMBA_NETBIOS_NAME = myhostname

      Default: Default: No default value

      Examples: use spnego (G)>use spnego (G)

      This variable controls controls whether samba will try to use Simple and Protected NEGOciation (as specified by rfc2478) with WindowsXP and Windows2000sp2 clients to agree upon an authentication mechanism. As of samba 3.0alpha it must be set to "no" for these clients to join a samba domain controller. It can be set to "yes" to allow samba to participate in an AD domain controlled by a Windows2000 domain controller.

      This variable controls controls whether samba will try + to use Simple and Protected NEGOciation (as specified by rfc2478) with + WindowsXP and Windows2000sp2 clients to agree upon an authentication mechanism. + Unless further issues are discovered with our SPNEGO + implementation, there is no reason this should ever be + disabled.

      Default: Default: use spnego = yes

      stat cache (G)
      >stat cache (G)

      This parameter determines if smbd(8)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.

      stat cache size (G)>stat cache size (G)

      This parameter determines the number of @@ -17502,7 +17932,7 @@ CLASS="COMMAND" >strict allocate (S)>strict allocate (S)

      This is a boolean that controls the handling of @@ -17539,7 +17969,7 @@ CLASS="COMMAND" >strict locking (S)>strict locking (S)

      This is a boolean that controls the handling of @@ -17572,7 +18002,7 @@ CLASS="COMMAND" >strict sync (S)>strict sync (S)

      Many Windows applications (including the Windows @@ -17585,10 +18015,12 @@ NAME="STRICTSYNC" CLASS="CONSTANT" >no (the - default) means that smbdsmbd(8) ignores the Windows applications requests for a sync call. There is only a possibility of losing data if the operating system itself that Samba is running on crashes, so there is @@ -17616,7 +18048,7 @@ CLASS="COMMAND" >strip dot (G)>strip dot (G)

      This is a boolean that controls whether to @@ -17632,7 +18064,7 @@ CLASS="COMMAND" >sync always (S)>sync always (S)

      This is a boolean parameter that controls @@ -17683,7 +18115,7 @@ CLASS="COMMAND" >syslog (G)>syslog (G)

      This parameter maps how Samba debug messages @@ -17718,7 +18150,7 @@ CLASS="COMMAND" >syslog only (G)>syslog only (G)

      If this parameter is set then Samba debug @@ -17734,7 +18166,7 @@ CLASS="COMMAND" >template homedir (G)>template homedir (G)

      When filling out the user information for a Windows NT @@ -17768,14 +18200,16 @@ CLASS="COMMAND" >template shell (G)>template shell (G)

      When filling out the user information for a Windows NT - user, the winbindd(8)winbindd(8) daemon uses this parameter to fill in the login shell for that user.

      time offset (G)>time offset (G)

      This parameter is a setting in minutes to add @@ -17810,14 +18244,15 @@ CLASS="COMMAND" >time server (G)>time server (G)

      This parameter determines if - nmbd(8)This parameter determines if nmbd(8) advertises itself as a time server to Windows clients.

      timestamp logs (G)>timestamp logs (G)

      Synonym for total print jobs (G)>total print jobs (G)

      This parameter accepts an integer value which defines a limit on the maximum number of print jobs that will be accepted system wide at any given time. If a print job is submitted - by a client which will exceed this number, then smbdsmbd(8) will return an error indicating that no space is available on the server. The default value of 0 means that no such limit exists. This parameter @@ -17887,7 +18324,7 @@ CLASS="COMMAND" >unicode (G)>unicode (G)

      Specifies whether Samba should try @@ -17904,7 +18341,7 @@ CLASS="COMMAND" >unix charset (G)>unix charset (G)

      Specifies the charset the unix machine @@ -17914,19 +18351,19 @@ NAME="UNIXCHARSET" >

      Default: unix charset = ASCIIunix charset = UTF8

      Example: unix charset = UTF8unix charset = ASCII

      unix extensions(G)
      >unix extensions(G)

      This boolean parameter controls whether Samba @@ -17945,7 +18382,7 @@ CLASS="COMMAND" >unix password sync (G)>unix password sync (G)

      This boolean parameter controls whether Samba @@ -17960,9 +18397,12 @@ CLASS="PARAMETER" >passwd programparameter is called parameter is called AS ROOT - to allow the new UNIX password to be set without access to the old UNIX password (as the SMB password change code has no @@ -17996,7 +18436,7 @@ CLASS="COMMAND" >update encrypted (G)>update encrypted (G)

      This boolean parameter allows a user logging @@ -18051,7 +18491,7 @@ CLASS="COMMAND" >use client driver (S)>use client driver (S)

      This parameter applies only to Windows NT/2000 @@ -18080,11 +18520,14 @@ CLASS="COMMAND" >If this parameter is enabled for a printer, then any attempt to open the printer with the PRINTER_ACCESS_ADMINISTER right is mapped to PRINTER_ACCESS_USE instead. Thus allowing the OpenPrinterEx() - call to succeed. This parameter MUST not be able enabled on a print share which has valid print driver installed on the Samba server.

      See also use mmap (G)>use mmap (G)

      This global parameter determines if the tdb internals of Samba can @@ -18126,7 +18569,7 @@ CLASS="COMMAND" >use rhosts (G)>use rhosts (G)

      If this global parameter is

      NOTE: The use of user (S)>user (S)

      Synonym for users (S)>users (S)

      Synonym for username (S)>username (S)

      Multiple users may be specified in a comma-delimited @@ -18268,7 +18714,7 @@ CLASS="PARAMETER" will be looked up only in the UNIX groups database and will expand to a list of all users in the group of that name.

      If any of the usernames begin with a '&'then the name +>If any of the usernames begin with a '&' then the name will be looked up only in the NIS netgroups database (if Samba is compiled with netgroup support) and will expand to a list of all users in the netgroup group of that name.

      See the section NOTE ABOUT USERNAME/PASSWORD VALIDATION for more information on how @@ -18287,7 +18733,7 @@ HREF="#AEN238" >Default: The guest account if a guest service, - else <empty string>.

      Examples:username level (G)>username level (G)

      This option helps Samba to try and 'guess' at @@ -18334,7 +18780,7 @@ CLASS="COMMAND" >username map (G)>username map (G)

      This option allows you to specify a file containing @@ -18424,20 +18870,10 @@ CLASS="COMMAND" '!' to tell Samba to stop processing if it gets a match on that line.

      		!sys = mary fred
-		guest = *
-
      !sys = mary fred +guest = *

      Note that the remapping is applied to all occurrences @@ -18474,9 +18910,12 @@ CLASS="PARAMETER" trouble deleting print jobs as PrintManager under WfWg will think they don't own the print job.

      Default: Default: no username map

      Example: use sendfile (S)>use sendfile (S)

      If this parameter is utmp (G)>utmp (G)

      This boolean parameter is only available if @@ -18553,7 +18992,7 @@ CLASS="COMMAND" >utmp directory(G)>utmp directory(G)

      This parameter is only available if Samba has @@ -18578,9 +19017,12 @@ CLASS="FILENAME" >/var/run/utmp on Linux).

      Default: Default: no utmp directory

      Example: wtmp directory(G)>wtmp directory(G)

      This parameter is only available if Samba has @@ -18621,9 +19063,12 @@ CLASS="FILENAME" >/var/run/wtmp on Linux).

      Default: Default: no wtmp directory

      Example: valid users (S)>valid users (S)

      This is a list of users that should be allowed - to login to this service. Names starting with '@', '+' and '&' + to login to this service. Names starting with '@', '+' and '&' are interpreted using the same rules as described in the

      Default: Default: No valid users list (anyone can login)

      Example: veto files(S)>veto files(S)

      This is a list of files and directories that @@ -18701,9 +19149,12 @@ NAME="VETOFILES" or directories as in DOS wildcards.

      Each entry must be a unix path, not a DOS path and - must not include the unix directory separator '/'.

      fail unless you also set the .

      Default: Default: No files or directories are vetoed.

      Examples:
      Examples:
      ; Veto any files containing the word Security, 
 ; any ending in .tmp, and any directory containing the
@@ -18781,16 +19232,13 @@ veto files = /*Security*/*.tmp/*root*/
 ; Veto the Apple specific files that a NetAtalk server
 ; creates.
 veto files = /.AppleDouble/.bin/.AppleDesktop/Network Trash Folder/

      veto oplock files (S)
      >veto oplock files (S)

      This parameter is only valid when the parameter.

      Default: Default: No files are vetoed for oplock grants

      You might want to do this on files that you know will @@ -18843,7 +19294,7 @@ CLASS="COMMAND" >vfs path (S)>vfs path (S)

      This parameter specifies the directory @@ -18868,7 +19319,7 @@ CLASS="COMMAND" >vfs object (S)>vfs object (S)

      This parameter specifies a shared object files that @@ -18876,16 +19327,19 @@ NAME="VFSOBJECT" disk I/O operations are used but these can be overloaded with one or more VFS objects.

      Default : Default : no value

      vfs options (S)
      >vfs options (S)

      This parameter allows parameters to be passed @@ -18900,32 +19354,38 @@ CLASS="PARAMETER" >.

      Default : Default : no value

      volume (S)
      >volume (S)

      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: Default: the name of the share

      wide links (S)
      >wide links (S)

      This parameter controls whether or not links @@ -18947,14 +19407,16 @@ CLASS="COMMAND" >winbind cache time (G)>winbind cache time (G)

      This parameter specifies the number of seconds the - winbindd(8)This parameter specifies the number of + seconds the winbindd(8) daemon will cache user and group information before querying a Windows NT server again.

      winbind enum users (G)>winbind enum users (G)

      On large installations using - winbindd(8)On large installations using winbindd(8) it may be - necessary to suppress the enumeration of users through the - setpwent()setpwent(), system call 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 @@ -19023,19 +19488,19 @@ CLASS="COMMAND" >winbind enum groups (G)>winbind enum groups (G)

      On large installations using - winbindd(8) it may be - necessary to suppress the enumeration of groups through the - On large installations using winbindd(8) it may be necessary to suppress + the enumeration of groups through the setgrent()setgrent(), system call will not return any data.

      Warning: Turning off group enumeration may cause some programs to behave oddly.

      winbind gid (G)>winbind gid (G)

      The winbind gid parameter specifies the range of group - ids that are allocated by the winbindd(8)winbindd(8) daemon. This range of group ids should have no existing local or NIS groups within it as strange conflicts can occur otherwise.

      Default: winbind gid = <empty string> +>winbind gid = <empty string>

      winbind separator (G)>winbind separator (G)

      This parameter allows an admin to define the character @@ -19148,21 +19618,23 @@ CLASS="COMMAND" >winbind uid (G)>winbind uid (G)

      The winbind gid parameter specifies the range of group - ids that are allocated by the winbindd(8)winbindd(8) daemon. This range of ids should have no existing local or NIS users within it as strange conflicts can occur otherwise.

      Default: winbind uid = <empty string> +>winbind uid = <empty string>

      winbind use default domain, winbind use default domain (G)
      >winbind use default domain (G)

      This parameter specifies whether the winbindd(8) - daemon should operate on users without domain component in their username. +>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 domain. While this does not benifit Windows users, it makes SSH, FTP and e-mail function in a way much closer to the way they would in a native unix system.

      Default: winbind use default domain = <no> +>winbind use default domain = <no>

      wins hook (G)>wins hook (G)

      When Samba is running as a WINS server this @@ -19268,7 +19742,7 @@ CLASS="COMMAND" >wins proxy (G)>wins proxy (G)

      This is a boolean that controls if wins server (G)>wins server (G)

      This specifies the IP address (or DNS name: IP - address for preference) of the WINS server that nmbd(8)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.

      NOTE. You need to set up Samba to point to a WINS server if you have multiple subnets and wish cross-subnet browsing to work correctly.

      See the documentation file BROWSING.txtSee the documentation file BROWSING in the docs/ directory of your Samba source distribution.

      Default: Default: not enabled

      Example: wins support (G)>wins support (G)

      This boolean controls if the - nmbd(8)This boolean controls if the nmbd(8) process in Samba will act as a WINS server. You should not set this to nmbd to be your WINS server. - Note that you should NEVER set this to yesworkgroup (G)>workgroup (G)

      This controls what workgroup your server will @@ -19381,9 +19868,12 @@ CLASS="COMMAND" > setting.

      Default: Default: set at compile time to WORKGROUP

      Example: writable (S)>writable (S)

      Synonym for write cache size (S)>write cache size (S)

      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 to be flushed directly to disk will be stored in this cache if possible. @@ -19453,7 +19946,7 @@ CLASS="COMMAND" >write list (S)>write list (S)

      This is a list of users that are given read-write @@ -19486,7 +19979,7 @@ CLASS="PARAMETER" >

      Default: write list = <empty string> +>write list = <empty string>

      wins partners (G)>wins partners (G)

      A space separated list of partners' IP addresses for @@ -19524,7 +20017,7 @@ CLASS="COMMAND" >write ok (S)>write ok (S)

      Inverted synonym for write raw (G)>write raw (G)

      This parameter controls whether or not the server @@ -19557,7 +20050,7 @@ CLASS="COMMAND" >writeable (S)>writeable (S)

      Inverted synonym for

      WARNINGS

      On a similar note, many clients - especially DOS clients - - limit service names to eight characters. smbd(8) - smbd(8) has no such limitation, but attempts to connect from such clients will fail if they truncate the service names. For this reason you should probably keep your service names down to eight characters @@ -19606,97 +20100,81 @@ TARGET="_top" >

      VERSION

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

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

      SEE ALSO

      samba(7), - smbpasswd(8), - swat(8), - smbd(8), - nmbd(8), - smbclient(1), - nmblookup(1), - testparm(1), - testprns(1) -

      samba(7), smbpasswd(8), swat(8), smbd(8), nmbd(8), smbclient(1), nmblookup(1), testparm(1), testprns(1).

      AUTHOR

      The original Samba man pages were written by Karl Auer. The man page sources were converted to YODL format (another - excellent piece of Open Source software, available at - ftp://ftp.icce.rug.nl/pub/unix/) and updated for the Samba 2.0 release by Jeremy Allison. The conversion to DocBook for - Samba 2.2 was done by Gerald Carter

      smbcacls

      smbcacls

      DESCRIPTION

      This tool is part of the SambaThis tool is part of the Samba(7) suite.

      The

      OPTIONS

      Specifies a username used to connect to the specified service. The username may be of the form "username" in which case the user is prompted to enter in a password and the - workgroup specified in the smb.confsmb.conf(5) file is used, or "username%password" or "DOMAIN\username%password" and the password and workgroup names are used as provided.

      ACL FORMAT

      The revision of the ACL specifies the internal Windows @@ -211,34 +215,45 @@ ACL:<sid or name>:<type>/<flags>/<mask> the file or directory resides.

      ACLs specify permissions granted to the SID. This SID again - can be specified in CWS-1-x-y-z format or as a name in which case - it is resolved against the server on which the file or directory - resides. The type, flags and mask values determine the type of - access granted to the SID.

      The type can be either 0 or 1 corresponding to ALLOWED or - DENIED 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_OBJECT_INHERIT 0x1

      • #define SEC_ACE_FLAG_CONTAINER_INHERIT 0x2

        #define SEC_ACE_FLAG_CONTAINER_INHERIT 0x2

      • #define SEC_ACE_FLAG_NO_PROPAGATE_INHERIT 0x4 -

        #define SEC_ACE_FLAG_NO_PROPAGATE_INHERIT 0x4

      • #define SEC_ACE_FLAG_INHERIT_ONLY 0x8

        #define SEC_ACE_FLAG_INHERIT_ONLY 0x8

      EXIT STATUS

      VERSION

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

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

      AUTHOR

      The conversion to DocBook for Samba 2.2 was done - by Gerald Carter

      smbclient

      smbclient

      smbclient {servicename} [password] [-b <buffer size>] [-d debuglevel] [-D Directory] [-U username] [-W workgroup] [-M <netbios name>] [-m maxprotocol] [-A authfile] [-N] [-l logfile] [-L <netbios name>] [-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]

      {servicename} [password] [-b <buffer size>] [-d debuglevel] [-D Directory] [-U username] [-W workgroup] [-M <netbios name>] [-m maxprotocol] [-A authfile] [-N] [-l logfile] [-L <netbios name>] [-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 SambaThis 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)ftp(1)). Operations include things like getting files from the server to the local machine, putting files from the local machine to @@ -71,7 +76,7 @@ CLASS="COMMAND" >

      OPTIONS

      smbclient       or - using the name resolve order parameter in the smb.confsmb.conf(5) file, allowing an administrator to change the order and methods by which server names are looked up.

      -s smb.conf

      Specifies the location of the all important - smb.confSpecifies the location of the all + important smb.conf(5) file.

      TCP socket options to set on the client - socket. See the socket options parameter in the smb.conf (5) manpage for the list of valid + socket. See the socket options parameter in + the smb.conf(5) manual page for the list of valid options.

      The options are :"lmhosts", "host", "wins" and "bcast". They - cause names to be resolved as follows :

        lmhosts : Lookup an IP +>: 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)lmhosts(5) for details) then any name type matches for lookup.

        host : Do a standard host +>: Do a standard host name to IP address resolution, using the system /etc/hosts @@ -248,7 +267,7 @@ CLASS="FILENAME" >wins : Query a name with +>: Query a name with the IP address listed in the bcast : Do a broadcast on +>: Do a broadcast on each of the known local interfaces listed in the

      If this parameter is not set then the name resolve order - defined in the smb.confsmb.conf(5) file parameter (name resolve order) will be used.

      name resolve order parameter of the smb.conf parameter of the smb.conf(5) file the name resolution methods will be attempted in this order.

      options useful, as they allow you to control the FROM and TO parts of the message.

      See the message command parameter in the smb.conf(5)See the message command parameter in the smb.conf(5) for a description of how to handle incoming WinPopup messages in Samba.

      username = <value> password = <value> -domain = <value> -

      If the domain parameter is missing the current workgroup name @@ -690,12 +722,14 @@ CLASS="COMMAND" >

      Override the default workgroup (domain) specified - in the workgroup parameter of the smb.conf - file for this connection. This may be needed to connect to some - servers.

      smb.conf(5) file for this connection. This may be + needed to connect to some servers.

      -T tar options

      All file names can be given as DOS path names (with '\' +>All file names can be given as DOS path names (with '\\' as the component separator) or as UNIX path names (with '/' as the component separator).

      -c 'print -'.

      -k

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

      OPERATIONS

      smb:\>

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

      NOTES

      ENVIRONMENT VARIABLES

      INSTALLATION

      To test the client, you will need to know the name of a - running SMB/CIFS server. It is possible to run smbd(8) - 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

      VERSION

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

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

      AUTHOR

      The original Samba man pages were written by Karl Auer. The man page sources were converted to YODL format (another - excellent piece of Open Source software, available at - ftp://ftp.icce.rug.nl/pub/unix/) and updated for the Samba 2.0 release by Jeremy Allison. The conversion to DocBook for - Samba 2.2 was done by Gerald Carter

      smbcontrol

      smbcontrol

      DESCRIPTION

      This tool is part of the SambaThis tool is part of the Samba(7) suite.

      smbcontrol is a very small program, which - sends messages to an smbd(8), - an nmbd(8) - or a winbindd(8) - daemon running on the system.

      smbd(8), a nmbd(8), or a winbindd(8) daemon running on the system.

      OPTIONS

      nmbd       - , smbd

      VERSION

      SEE ALSO

      nmbd(8), - and smbd(8). -

      nmbd(8) and smbd(8).

      AUTHOR

      The original Samba man pages were written by Karl Auer. The man page sources were converted to YODL format (another - excellent piece of Open Source software, available at - ftp://ftp.icce.rug.nl/pub/unix/) and updated for the Samba 2.0 release by Jeremy Allison. The conversion to DocBook for - Samba 2.2 was done by Gerald Carter

      + smbd

      smbd

      smbd

      Synopsis

      smbd [-D] [-F] [-S] [-i] [-h] [-V] [-b] [-d <debug level>] [-l <log directory>] [-p <port number>] [-O <socket option>] [-s <configuration file>]

      [-D] [-F] [-S] [-i] [-h] [-V] [-b] [-d <debug level>] [-l <log directory>] [-p <port number>] [-O <socket option>] [-s <configuration file>]

      DESCRIPTION

      This program is part of the Samba suite.

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

      An extensive description of the services that the server can provide is given in the man page for the configuration file controlling the attributes of those - services (see smb.conf(5) - smb.conf(5). This man page will not describe the services, but will concentrate on the administrative aspects of running the server.

      Please note that there are significant security - implications to running this server, and the smb.conf(5) - manpage should be regarded as mandatory reading before + implications to running this server, and the smb.conf(5) manual page should be regarded as mandatory reading before proceeding with installation.

      A session is created whenever a client requests one. @@ -104,7 +109,7 @@ CLASS="COMMAND" >

      OPTIONS

      -d <debug level>
      -d <debug level>

      log - level parameter in the smb.conf(5) parameter in the smb.conf(5) file.

      -l <log directory>
      -l <log directory>

      If specified, @@ -280,18 +289,25 @@ CLASS="REPLACEABLE" its size may be controlled by the max log size - option in the smb.conf(5)max log size file. + option in the smb.conf(5) file. Beware: If the directory specified does not exist,

      -O <socket options>
      -O <socket options>

      See the socket options - parameter in the smb.conf(5) - socket options + parameter in the smb.conf(5) file for details.

      -p <port number>
      -p <port number>

      -s <configuration file>
      -s <configuration file>

      The file specified contains the @@ -362,13 +381,12 @@ CLASS="REPLACEABLE" information in this file includes server-specific information such as what printcap file to use, as well as descriptions of all the services that the server is - to provide. See smb.conf(5)smb.conf(5) for more information. The default configuration file name is determined at compile time.

      FILES

      meta-daemon, this file must contain suitable startup information for the meta-daemon. See the UNIX_INSTALL.html"How to Install and Test SAMBA" document for details.

      If running the server as a daemon at startup, this file will need to contain an appropriate startup sequence for the server. See the UNIX_INSTALL.html"How to Install and Test SAMBA" document for details.

      UNIX_INSTALL.html"How to Install and Test SAMBA" document for details.

      This is the default location of the - smb.conf - server configuration file. Other common places that systems +>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/smb.conf/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.

      smb.conf(5) for more information.

      LIMITATIONS

      ENVIRONMENT VARIABLES

      PAM INTERACTION

      Samba uses PAM for authentication (when presented with a plaintext password), for account checking (is this account disabled?) and for session management. The degree too which samba supports PAM is restricted - by the limitations of the SMB protocol and the - obey pam restricions - smb.conf paramater. When this is set, the following restrictions apply: +>obey + pam restricions smb.conf(5) paramater. When this is set, the following restrictions apply:

      • Account Validation: All accesses to a samba server are checked against PAM to see if the account is vaild, not disabled and is permitted to @@ -573,9 +600,12 @@ CLASS="EMPHASIS" >

      • 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. @@ -588,7 +618,7 @@ CLASS="EMPHASIS" >

        VERSION

        DIAGNOSTICS

        SIGNALS

        SIGKILL (-9)         NOT be used, except as a last resort, as this may leave the shared memory area in an inconsistent state. The safe way to terminate @@ -660,16 +693,14 @@ CLASS="COMMAND" CLASS="COMMAND" >smbd may be raised - or lowered using smbcontrol(1) - program (SIGUSR[1|2] signals are no longer used in - Samba 2.2). This is to allow transient problems to be diagnosed, + or lowered using smbcontrol(1) program (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.

        Note that as the signal handlers send a debug write, @@ -688,55 +719,55 @@ CLASS="COMMAND" >

        SEE ALSO

        hosts_access(5), inetd(8), - nmbd(8), - smb.conf(5) - , smbclient(1) - , testparm(1), testprns(1), and the Internet RFC's - hosts_access(5), inetd(8), nmbd(8), smb.conf(5), smbclient(1), testparm(1), testprns(1), and the + Internet RFC's rfc1001.txt,

        AUTHOR

        The original Samba man pages were written by Karl Auer. The man page sources were converted to YODL format (another - excellent piece of Open Source software, available at - ftp://ftp.icce.rug.nl/pub/unix/) and updated for the Samba 2.0 release by Jeremy Allison. The conversion to DocBook for - Samba 2.2 was done by Gerald Carter

        + smbgroupedit

        smbgroupedit

        smbgroupedit

        Synopsis

        smbroupedit [-v [l|s]] [-a UNIX-groupname [-d NT-groupname|-p privilege|]]

        [-v [l|s]] [-a UNIX-groupname [-d NT-groupname|-p privilege|]]

        DESCRIPTION

        This program is part of the Samba -suite.

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

        The smbgroupedit command allows for mapping unix groups to NT Builtin, Domain, or Local groups. Also @@ -59,7 +63,7 @@ etc.

        OPTIONS

        give a long listing, of the format:

        "NT Group Name"
@@ -100,20 +98,10 @@ CLASS="PROGRAMLISTING"
     Group type     :
     Comment        :
     Privilege      :

        For examples,

        For example:
+
        Users
     SID       : S-1-5-32-545
@@ -121,9 +109,6 @@ CLASS="PROGRAMLISTING"
     Group type: Local group
     Comment   :
     Privilege : No privilege

        display a short listing of the format:

        NTGroupName(SID) -> UnixGroupName

        For example,

        For example:
+
        Users (S-1-5-32-545) -> -1

      • map this domadm group to the 'domain admins' group: -

        map this domadm group to the 'domain admins' group:

        1. Get the SID for the Windows NT "Domain Admins" - group:

          Get the SID for the Windows NT "Domain Admins" group:

          smbgroupedit -vs | grep "Domain Admins"
 Domain Admins (S-1-5-21-1108995562-3116817432-1375597819-512) -> -1

        2. map the unix domadm group to the Windows NT "Domain Admins" group, by running the command: -

          warning: don't copy and paste this sample, the Domain Admins SID (the S-1-5-21-...-512) is different for every PDC.

        To verify that your mapping has taken effect:

        To verify that your mapping has taken effect:
+
        smbgroupedit -vs|grep "Domain Admins"
 Domain Admins (S-1-5-21-1108995562-3116817432-1375597819-512) -> domadm

        To give access to a certain directory on a domain member machine (an NT/W2K or a samba server running winbind) to some users who are member -of a group on your samba PDC, flag that group as a domain group:

        smbgroupedit -a unixgroup -td

      VERSION

      SEE ALSO

      smb.conf(5)smb.conf(5)

      AUTHOR

      smbgroupedit       was written by Jean Francois Micouleau. The current set of manpages and documentation is maintained -by the Samba Team in the same fashion as the Samba source code.

      smbmnt

      smbmnt

      smbmnt program is normally invoked - by smbmount(8) - smbmount(8). It should not be invoked directly by users.

      smbmount searches the normal PATH for smbmnt. You must ensure @@ -81,7 +79,7 @@ CLASS="COMMAND" >

      OPTIONS

      AUTHOR

      The conversion of this manpage for Samba 2.2 was performed - by Gerald Carter

      smbmount

      smbmount

      mount.smbfs by - the mount(8)mount(8) command when using the "-t smbfs" option. This command only works in Linux, and the kernel must support the smbfs filesystem.

      log.smbmount      . The - . The smbmount smbmount process may also be called mount.smbfs.

      smbmount - calls smbmnt(8)smbmnt(8) to do the actual mount. You must make sure that

      OPTIONS

      credentials=<filename>

      specifies a file that contains a username - and/or password. The format of the file is:

      specifies a file that contains a username and/or password. 
+The format of the file is:
+
      		username = <value>
-		password = <value>
-		
      
-		
      username = <value>
+password = <value>

      This is preferred over having passwords in plaintext in a shared file, such as sets the TCP socket options. See the smb.conf - smb.conf(5)

      ENVIRONMENT VARIABLES

      BUGS

      SEE ALSO

      FreeBSD also has a smbfs, but it is not related to smbmount

      For Solaris, HP-UX and others you may want to look at - smbsh(1) or at other - solutions, such as sharity or perhaps replacing the SMB server with - a NFS server.

      For Solaris, HP-UX and others you may want to look at smbsh(1) or at other solutions, such as + Sharity or perhaps replacing the SMB server with a NFS server.

      AUTHOR

      The conversion of this manpage for Samba 2.2 was performed - by Gerald Carter

      smbpasswd

      smbpasswd

      DESCRIPTION

      This tool is part of the SambaThis tool is part of the Samba(7) suite.

      smbpasswd is the Samba encrypted password file. It contains @@ -62,7 +64,7 @@ TARGET="_top" >

      FILE FORMAT

      parameter is set in the smb.conf(5) - smb.conf(5) config file.

      D - This means the account - is disabled and no SMB/CIFS logins will be allowed for - this user.

    • VERSION

      SEE ALSO

      smbpasswd(8), - samba(7)smbpasswd(8), Samba(7), and the Internet RFC1321 for details on the MD4 algorithm.

      AUTHOR

      The original Samba man pages were written by Karl Auer. The man page sources were converted to YODL format (another - excellent piece of Open Source software, available at - ftp://ftp.icce.rug.nl/pub/unix/) and updated for the Samba 2.0 release by Jeremy Allison. The conversion to DocBook for - Samba 2.2 was done by Gerald Carter

      + smbpasswd

      smbpasswd

      smbpasswd

      Synopsis

      smbpasswd [-a] [-x] [-d] [-e] [-D debuglevel] [-n] [-r <remote machine>] [-R <name resolve order>] [-m] [-U username[%password]] [-h] [-s] [-w pass] [-i] [-L] [username]

      [-a] [-x] [-d] [-e] [-D debuglevel] [-n] [-r <remote machine>] [-R <name resolve order>] [-m] [-U username[%password]] [-h] [-s] [-w pass] [-i] [-L] [username]

      DESCRIPTION

      This tool is part of the SambaThis 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 +> 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 SMB passwords.

      passwd(1) program works. - program works. smbpasswd smbpasswd differs from how the passwd program works - however in that it is not setuid root but works in - a client-server mode and communicates with a locally running - smbd(8)smbd(8). As a consequence in order for this to succeed the smbd daemon must be running on the local machine. On a UNIX machine the encrypted SMB passwords are usually stored in - the smbpasswd(5)smbpasswd(5) file.

      When run by an ordinary user with no options, smbpasswd @@ -91,18 +107,28 @@ CLASS="FILENAME" was typed correctly. No passwords will be echoed on the screen whilst being typed. If you have a blank SMB password (specified by the string "NO PASSWORD" in the smbpasswd file) then just press - the <Enter> key when asked for your old password.

      smbpasswd can also be used by a normal user to change their SMB password on remote machines, such as Windows NT Primary Domain - Controllers. See the (-r) and -U options below.

      -r) and -U options + below.

      When run by root, smbpasswd allows new users to be added and deleted in the smbpasswd file, as well as allows changes to - the attributes of the user in this file to be made. When run by root, - smbpasswd smbpasswd accesses the local smbpasswd file directly, thus enabling changes to be made even if smbd is not running.

      OPTIONS

      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 + 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 default passdb backends require @@ -169,10 +195,12 @@ CLASS="CONSTANT" >

      If the smbpasswd file is in the 'old' format (pre-Samba 2.0 format) there is no space in the user's password entry to write - this information and the command will FAIL. See smbpasswd(5) - smbpasswd(5) for details on the 'old' and new password file formats.

      smbpasswd will FAIL to enable the account. - See smbpasswd (5)smbpasswd(5) for details on the 'old' and new password file formats.

      Note that Windows 95/98 do not have a real password database so it is not possible to change passwords specifying a Win95/98 machine as remote machine target.

      The options are :"lmhosts", "host", "wins" and "bcast". They - cause names to be resolved as follows :

        lmhosts : Lookup an IP +>: 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)lmhosts(5) for details) then any name type matches for lookup.

        host : Do a standard host +>: Do a standard host name to IP address resolution, using the system /etc/hosts @@ -353,7 +389,7 @@ CLASS="FILENAME" >wins : Query a name with +>: Query a name with the IP address listed in the bcast : Do a broadcast on +>: Do a broadcast on each of the known local interfaces listed in the lmhosts, host, wins, bcast - and without this parameter or any entry in the - smb.confsmb.conf(5) file the name resolution methods will be attempted in this order.

      • . Note that the password is stored in the private/secrets.tdbsecrets.tdb and is keyed off of the admin's DN. This means that if the value of

      This specifies the username for all of the - 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. @@ -523,7 +564,7 @@ CLASS="EMPHASIS" >

      NOTES

      smbd       running on the local machine by specifying a - running on the local machine by specifying either allow hostsallow + hosts or deny hosts - entry in the smb.conf entry in + the smb.conf(5) file and neglecting to allow "localhost" access to the smbd.

      In addition, the smbpasswd command is only useful if Samba - has been set up to use encrypted passwords. See the file - ENCRYPTION.txt "LanMan and NT Password Encryption in Samba" in the docs directory for details on how to do this.

      VERSION

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

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

      SEE ALSO

      smbpasswd(5), - samba(7) -

      smbpasswd(5), Samba(7).

      AUTHOR

      The original Samba man pages were written by Karl Auer. The man page sources were converted to YODL format (another - excellent piece of Open Source software, available at - ftp://ftp.icce.rug.nl/pub/unix/) and updated for the Samba 2.0 release by Jeremy Allison. The conversion to DocBook for - Samba 2.2 was done by Gerald Carter

      + smbsh

      smbsh

      smbsh

      Synopsis

      smbsh [-W workgroup] [-U username] [-P prefix] [-R <name resolve order>] [-d <debug level>] [-l logfile] [-L libdir]

      [-W workgroup] [-U username] [-P prefix] [-R <name resolve order>] [-d <debug level>] [-l logfile] [-L libdir]

      DESCRIPTION

      This tool is part of the SambaThis tool is part of the Samba(7) suite.

      OPTIONS

      Override the default workgroup specified in the - workgroup parameter of the smb.confsmb.conf(5) file for this session. This may be needed to connect to some servers.

      This option allows the user to set the directory prefix for SMB access. The default value if this option is not specified is - smb.

      -R <name resolve order>
      -R <name resolve order>

      This option is used to determine what naming @@ -127,7 +138,7 @@ CLASS="EMPHASIS" 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". +>The options are: "lmhosts", "host", "wins" and "bcast". They cause names to be resolved as follows :

      lmhosts : +>: Lookup an IP address in the Samba lmhosts file. If the line in lmhosts has no name type attached to the NetBIOS name - (see the lmhosts(5) - for details) then any name type matches for lookup. + (see the lmhosts(5) for details) + then any name type matches for lookup.

    • host : +>: Do a standard host name to IP address resolution, using the system wins : +>: Query a name with the IP address listed in the bcast : +>: Do a broadcast on each of the known local interfaces listed in the

      If this parameter is not set then the name resolve order - defined in the smb.confsmb.conf(5) file parameter - (name resolve order) will be used.

      name resolve order      ) will be used.

      The default order is lmhosts, host, wins, bcast. Without this parameter or any entry in the name resolve order parameter of the smb.conf - file, the name resolution methods will be attempted in this - order.

      parameter of the smb.conf(5) file, the name resolution methods + will be attempted in this order.

      • -d <debug level>
      -d <debug level>

      debug level is an integer from 0 to 10.

      The higher this value, the more detail will be logged - about the activities of nmblookupnmblookup(1). At level 0, only critical errors and serious warnings will be logged.

      EXAMPLES

      smbsh       from the prompt and enter the username and password that authenticates you to the machine running the Windows NT - operating system.

      	system% smbsh
-	Username: user
-	Password: XXXXXXX
-

      Any dynamically linked command you execute from @@ -357,7 +372,7 @@ CLASS="COMMAND" the workgroup MYGROUP. The command ls /smb/MYGROUP/<machine-name>ls /smb/MYGROUP/<machine-name> will show the share names for that machine. You could then, for example, use the

      VERSION

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

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

      BUGS

      SEE ALSO

      smbd(8), - smb.conf(5) -

      smbd(8), smb.conf(5)

      AUTHOR

      The original Samba man pages were written by Karl Auer. The man page sources were converted to YODL format (another - excellent piece of Open Source software, available at - ftp://ftp.icce.rug.nl/pub/unix/) and updated for the Samba 2.0 release by Jeremy Allison. The conversion to DocBook for - Samba 2.2 was done by Gerald Carter

      smbspool

      smbspool

      DESCRIPTION

      This tool is part of the SambaThis tool is part of the Samba(7) suite.

      smbspool is a very small print spooling program that @@ -87,8 +89,7 @@ CLASS="EMPHASIS" >

    • smb://username:password@workgroup/server/printer -

      smb://username:password@workgroup/server/printer

      • OPTIONS

      VERSION

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

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

      SEE ALSO

      smbd(8), - and samba(7). -

      smbd(8) and Samba(7).

      AUTHOR

      The original Samba man pages were written by Karl Auer. The man page sources were converted to YODL format (another - excellent piece of Open Source software, available at - ftp://ftp.icce.rug.nl/pub/unix/) and updated for the Samba 2.0 release by Jeremy Allison. The conversion to DocBook for - Samba 2.2 was done by Gerald Carter

      smbstatus

      smbstatus

      DESCRIPTION

      This tool is part of the SambaThis tool is part of the Samba(7) suite.

      OPTIONS

      -p|--processes

      print a list of smbd(8)print a list of smbd(8) processes and exit. Useful for scripting.

      The default configuration file name is determined at compile time. The file specified contains the - configuration details required by the server. See smb.conf(5) - smb.conf(5) for more information.

      VERSION

      SEE ALSO

      smbd(8) and - smb.conf(5)smbd(8) and smb.conf(5).

      AUTHOR

      The original Samba man pages were written by Karl Auer. The man page sources were converted to YODL format (another - excellent piece of Open Source software, available at - ftp://ftp.icce.rug.nl/pub/unix/) and updated for the Samba 2.0 release by Jeremy Allison. The conversion to DocBook for - Samba 2.2 was done by Gerald Carter

      smbtar

      smbtar

      DESCRIPTION

      This tool is part of the SambaThis 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.

      smbclient(1) which dumps SMB shares directly to tape.

      OPTIONS

      -d       flag of smbclient(1) - .

      flag of smbclient(1).

      ENVIRONMENT VARIABLES

      BUGS

      CAVEATS

      DIAGNOSTICS

      DIAGNOSTICS       section for the - smbclient(1) - section for the smbclient(1) command.

      VERSION

      SEE ALSO

      smbd(8), - smbclient(1), - smb.conf(5), -

      smbd(8), smbclient(1), smb.conf(5).

      AUTHOR

      . Many thanks to everyone who suggested extensions, improvements, bug fixes, etc. The man page sources were converted to YODL format (another - excellent piece of Open Source software, available at - ftp://ftp.icce.rug.nl/pub/unix/) and updated for the Samba 2.0 release by Jeremy Allison. The conversion to DocBook for - Samba 2.2 was done by Gerald Carter.

      smbumount

      smbumount

      SEE ALSO

      smbmount(8) - smbmount(8)

      AUTHOR

      The conversion of this manpage for Samba 2.2 was performed - by Gerald Carter

      Samba performance issuesNext

      Chapter 22. Samba performance issues

      Chapter 19. Samba performance issues

      22.1. Comparisons

      19.1. Comparisons

      The Samba server uses TCP to talk to the client. Thus if you are trying to see if it performs well you should really compare it to @@ -108,7 +111,9 @@ CLASS="SECT1" >

      22.2. Socket options

      19.2. Socket options

      There are a number of socket options that can greatly affect the performance of a TCP based server like Samba.

      22.3. Read size

      19.3. Read size

      The option "read size" affects the overlap of disk reads/writes with network reads/writes. If the amount of data being transferred in @@ -158,7 +165,9 @@ CLASS="SECT1" >

      22.4. Max xmit

      19.4. Max xmit

      At startup the client and server negotiate a "maximum transmit" size, which limits the size of nearly all SMB commands. You can set the @@ -179,7 +188,9 @@ CLASS="SECT1" >

      22.5. Log level

      19.5. Log level

      If you set the log level (also known as "debug level") higher than 2 then you may suffer a large drop in performance. This is because the @@ -191,7 +202,9 @@ CLASS="SECT1" >

      22.6. Read raw

      19.6. Read raw

      The "read raw" operation is designed to be an optimised, low-latency file read operation. A server may choose to not support it, @@ -211,7 +224,9 @@ CLASS="SECT1" >

      22.7. Write raw

      19.7. Write raw

      The "write raw" operation is designed to be an optimised, low-latency file write operation. A server may choose to not support it, @@ -226,7 +241,9 @@ CLASS="SECT1" >

      22.8. Slow Clients

      19.8. Slow Clients

      One person has reported that setting the protocol to COREPLUS rather than LANMAN2 gave a dramatic speed improvement (from 10k/s to 150k/s).

      22.9. Slow Logins

      19.9. Slow Logins

      Slow logins are almost always due to the password checking time. Using the lowest practical "password level" will improve things a lot. You @@ -252,7 +271,9 @@ CLASS="SECT1" >

      22.10. Client tuning

      19.10. Client tuning

      Often a speed problem can be traced to the client. The client (for example Windows for Workgroups) can often be tuned for better TCP @@ -386,7 +407,7 @@ WIDTH="33%" ALIGN="right" VALIGN="top" >NextAppendixesCreating Group Profiles

      swat

      swat

      DESCRIPTION

      This tool is part of the SambaThis tool is part of the Samba(7) suite.

      swat allows a Samba administrator to - configure the complex smb.conf(5)smb.conf(5) file via a Web browser. In addition, a

      OPTIONS

      The default configuration file path is determined at compile time. The file specified contains - the configuration details required by the smbd - server. This is the file that smbd(8) server. This is the file + that swat will modify. @@ -147,7 +151,7 @@ CLASS="EMPHASIS" >

      INSTALLATION

      Inetd Installation

      Launching

      FILES

      This is the default location of the smb.conf(5) - 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

      WARNINGS

      swat will rewrite your smb.conf - will rewrite your smb.conf(5) file. It will rearrange the entries and delete all comments,

      VERSION

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

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

      SEE ALSO

      inetd(5), - smbd(8), - smb.conf(5) -

      , smbd(8), smb.conf(5)

      AUTHOR

      The original Samba man pages were written by Karl Auer. The man page sources were converted to YODL format (another - excellent piece of Open Source software, available at - ftp://ftp.icce.rug.nl/pub/unix/) and updated for the Samba 2.0 release by Jeremy Allison. The conversion to DocBook for - Samba 2.2 was done by Gerald Carter

      + testparm

      testparm

      testparm

      Synopsis

      testparm [-s] [-h] [-v] [-L <servername>] [-t <encoding>] {config filename} [hostname hostIP]

      [-s] [-h] [-v] [-L <servername>] [-t <encoding>] {config filename} [hostname hostIP]

      DESCRIPTION

      This tool is part of the SambaThis tool is part of the Samba(7) suite.

      testparm is a very simple test program - to check an smbdsmbd(8) configuration file for internal correctness. If this program reports no problems, you can use the configuration file with confidence that will successfully load the configuration file.

      Note that this is Note that this is NOT a guarantee that the services specified in the configuration file will be available or will operate as expected.

      OPTIONS

      If this option is specified, testparm - will also output all options that were not used in - smb.conf and are thus set to - their defaults.

      smb.conf(5) and are thus set to their defaults.

      -t encoding

      This is the name of the configuration file to check. If this parameter is not present then the - default smb.confsmb.conf(5) file will be checked.

      hosts deny - parameters in the smb.confsmb.conf(5) file to determine if the hostname with this IP address would be allowed access to the

      FILES

      smb.confsmb.conf(5)

      This is usually the name of the configuration - file used by smbdsmbd(8).

      DIAGNOSTICS

      VERSION

      SEE ALSO

      smb.conf(5), - smbd(8) -

      smb.conf(5), smbd(8)

      AUTHOR

      The original Samba man pages were written by Karl Auer. The man page sources were converted to YODL format (another - excellent piece of Open Source software, available at - ftp://ftp.icce.rug.nl/pub/unix/) and updated for the Samba 2.0 release by Jeremy Allison. The conversion to DocBook for - Samba 2.2 was done by Gerald Carter

      testprns

      testprns

      DESCRIPTION

      This tool is part of the SambaThis tool is part of the Samba(7) suite.

      testprns is a very simple test program to determine whether a given printer name is valid for use in - a service to be provided by smbd(8).

      smbd(8).

      "Valid" in this context means "can be found in the printcap specified". This program is very stupid - so stupid in @@ -75,7 +76,7 @@ CLASS="COMMAND" >

      OPTIONS

      testprns       finds the printer then - smbd finds the printer then smbd(8) should do so as well.

      FILES

      DIAGNOSTICS

      VERSION

      SEE ALSO

      printcap(5), - smbd(8), - smbclient(1) -

      smbd(8), smbclient(1)

      AUTHOR

      The original Samba man pages were written by Karl Auer. The man page sources were converted to YODL format (another - excellent piece of Open Source software, available at - ftp://ftp.icce.rug.nl/pub/unix/) and updated for the Samba 2.0 release by Jeremy Allison. The conversion to DocBook for - Samba 2.2 was done by Gerald Carter

      Type of installationPrev

      Introduction

      Samba can operate in various SMB networks. This part contains information on configuring samba @@ -91,233 +94,238 @@ CLASS="TOC" >Table of Contents

      5. 4. User and Share security level (for servers not in a domain)
      6. 5. How to Configure Samba as a NT4 Primary Domain ControllerSamba as a NT4 or Win2k Primary Domain Controller
      6.1. 5.1. Prerequisite Reading
      6.2. 5.2. Background
      6.3. 5.3. Configuring the Samba Domain Controller
      6.4. 5.4. Creating Machine Trust Accounts and Joining Clients to the Domain
      6.4.1. 5.4.1. Manual Creation of Machine Trust Accounts
      6.4.2. 5.4.2. "On-the-Fly" Creation of Machine Trust Accounts
      6.4.3. 5.4.3. Joining the Client to the Domain
      6.5. 5.5. Common Problems and Errors
      6.6. 5.6. System Policies and Profiles
      6.7. 5.7. What other help can I get?
      6.8. 5.8. Domain Control for Windows 9x/ME
      6.8.1. 5.8.1. Configuration Instructions: Network Logons
      6.8.2. 5.8.2. Configuration Instructions: Setting up Roaming User Profiles
      6.9. DOMAIN_CONTROL.txt : Windows NT Domain Control & Samba5.9. DOMAIN_CONTROL.txt : Windows NT Domain Control & Samba
      7. 6. How to Act as a Backup Domain Controller in a Purely Samba Controlled Domain
      7.1. 6.1. Prerequisite Reading
      7.2. 6.2. Background
      7.3. 6.3. What qualifies a Domain Controller on the network?
      7.3.1. 6.3.1. How does a Workstation find its domain controller?
      7.3.2. 6.3.2. When is the PDC needed?
      7.4. Can Samba be a Backup Domain Controller?6.4. Can Samba be a Backup Domain Controller to an NT PDC?
      7.5. 6.5. How do I set up a Samba BDC?
      7.5.1. 6.5.1. How do I replicate the smbpasswd file?
      6.5.2. Can I do this all with LDAP?
      8. 7. Samba as a ADS domain member
      8.1. 7.1. Installing the required packages for Debian
      8.2. 7.2. Installing the required packages for RedHat
      8.3. 7.3. Compile Samba
      8.4. 7.4. Setup your /etc/krb5.conf
      8.5. 7.5. Create the computer account
      8.5.1. 7.5.1. Possible errors
      8.6. 7.6. Test your server setup
      8.7. 7.7. Testing with smbclient
      8.8. 7.8. Notes
      9. 8. Samba as a NT4 domain memberSamba as a NT4 or Win2k domain member
      9.1. Joining an NT Domain with Samba 2.28.1. Joining an NT Domain with Samba 3.0
      9.2. 8.2. Samba and Windows 2000 Domains
      9.3. 8.3. Why is this better than security = server?
      PrevLanMan and NT Password Encryption in SambaUser information databaseUNIX Permission Bits and Windows NT Access Control Lists

      Chapter 11. UNIX Permission Bits and Windows NT Access Control Lists

      Chapter 10. UNIX Permission Bits and Windows NT Access Control Lists

      11.1. Viewing and changing UNIX permissions using the NT +NAME="AEN1744" +>10.1. Viewing and changing UNIX permissions using the NT security dialogs

      New in the Samba 2.0.4 release is the ability for Windows @@ -91,33 +94,15 @@ NAME="AEN1605">11.1. Viewing and changing UNIX permissions using the NT the security of the UNIX host Samba is running on, and still obeys all the file permission rules that a Samba administrator can set.

      In Samba 2.0.4 and above the default value of the - parameter nt acl support has been changed from - false to true, so - manipulation of permissions is turned on by default.

      11.2. How to view file security on a Samba share

      10.2. How to view file security on a Samba share

      From an NT 4.0 client, single-click with the right mouse button on any file or directory in a Samba mounted @@ -185,7 +170,9 @@ CLASS="SECT1" >

      11.3. Viewing file ownership

      10.3. Viewing file ownership

      Clicking on the

      11.4. Viewing file or directory permissions

      10.4. Viewing file or directory permissions

      The third button is the

      11.4.1. File Permissions

      10.4.1. File Permissions

      The standard UNIX user/group/world triple and the corresponding "read", "write", "execute" permissions @@ -397,7 +388,9 @@ CLASS="SECT2" >

      11.4.2. Directory Permissions

      10.4.2. Directory Permissions

      Directories on an NT NTFS file system have two different sets of permissions. The first set of permissions @@ -427,7 +420,9 @@ CLASS="SECT1" >

      11.5. Modifying file or directory permissions

      10.5. Modifying file or directory permissions

      Modifying file and directory permissions is as simple as changing the displayed permissions in the dialog box, and @@ -523,7 +518,9 @@ CLASS="SECT1" >

      11.6. Interaction with the standard Samba create mask +NAME="AEN1837" +>10.6. Interaction with the standard Samba create mask parameters

      Note that with Samba 2.0.5 there are four new parameters @@ -798,7 +795,9 @@ CLASS="SECT1" >

      11.7. Interaction with the standard Samba file attribute +NAME="AEN1901" +>10.7. Interaction with the standard Samba file attribute mapping

      Samba maps some of the DOS attribute bits (such as "read diff --git a/docs/htmldocs/vfs.html b/docs/htmldocs/vfs.html index 11934ae47c..0e39297ebb 100644 --- a/docs/htmldocs/vfs.html +++ b/docs/htmldocs/vfs.html @@ -5,8 +5,7 @@ >Stackable VFS modulesPrevNext

      Chapter 18. Stackable VFS modules

      Chapter 16. Stackable VFS modules

      18.1. Introduction and configuration

      16.1. Introduction and configuration

      Since samba 3.0, samba supports stackable VFS(Virtual File System) modules. Samba passes each request to access the unix file system thru the loaded VFS modules. @@ -118,13 +121,17 @@ CLASS="SECT1" >

      18.2. Included modules

      16.2. Included modules

      18.2.1. audit

      16.2.1. audit

      A simple module to audit file access to the syslog facility. The following operations are logged: @@ -160,7 +167,9 @@ CLASS="SECT2" >

      18.2.2. recycle

      16.2.2. recycle

      A recycle-bin like modules. When used any unlink call will be intercepted and files moved to the recycle @@ -229,7 +238,9 @@ CLASS="SECT2" >

      18.2.3. netatalk

      16.2.3. netatalk

      A netatalk module, that will ease co-existence of samba and netatalk file sharing services.

      18.3. VFS modules available elsewhere

      16.3. VFS modules available elsewhere

      This section contains a listing of various other VFS modules that have been posted but don't currently reside in the Samba CVS @@ -274,7 +287,9 @@ CLASS="SECT2" >

      18.3.1. DatabaseFS

      16.3.1. DatabaseFS

      URL:

      18.3.2. vscan

      16.3.2. vscan

      URL: PrevNextPassdb XML pluginImproved browsing in sambaStoring Samba's User/Machine Account information in an LDAP DirectoryAccess Samba source code via CVS

      + vfstest

      vfstest

      vfstest

      Synopsis

      vfstest [-d debuglevel] [-c command] [-l logfile] [-h]

      [-d debuglevel] [-c command] [-l logfile] [-h]

      DESCRIPTION

      This tool is part of the SambaThis tool is part of the Samba(7) suite.

      OPTIONS

      COMMANDS

      VFS COMMANDS

      load <module.so>load <module.so> - Load specified VFS module

    • populate <char> <size>populate <char> <size> - Populate a data buffer with the specified data

      • showdata [<offset> <len>]showdata [<offset> <len>] - Show data currently in data buffer

      GENERAL COMMANDS

      conf <smb.conf>conf <smb.conf> - Load a different configuration file

    • help [<command>]help [<command>] - Get list of commands or info about specified command

    • debuglevel <level>debuglevel <level> - Set debug level

    • VERSION

      AUTHOR

      wbinfo

      wbinfo

      DESCRIPTION

      This tool is part of the SambaThis tool is part of the Samba(7) suite.

      The wbinfo program queries and returns information - created and used by the winbindd(8)winbindd(8) daemon.

      The winbindd(8)The winbindd(8) daemon must be configured and running for the

      OPTIONS

      This option will list all users available - in the Windows NT domain for which the winbindd(8) - winbindd(8) daemon is operating in. Users in all trusted domains will also be listed. Note that this operation does not assign - user ids to any users that have not already been seen by - winbindd(8).

      winbindd(8) + .

      -g

      This option will list all groups available - in the Windows NT domain for which the winbindd(8) - Samba(7) daemon is operating in. Groups in all trusted domains will also be listed. Note that this operation does not assign - group ids to any groups that have not already been seen by - winbindd(8)winbindd(8).

      -N option - queries winbindd(8)winbindd(8) to query the WINS server for the IP address associated with the NetBIOS name specified by the -I option - queries winbindd(8)winbindd(8) to send a node status request to get the NetBIOS name associated with the IP address specified by the -n option - queries winbindd(8)winbindd(8) for the SID associated with the name specified. Domain names can be specified before the user name by using the winbind separator character. For example CWDOM1/Administrator refers to the Administrator user in the domain CWDOM1. If no domain is specified then the - domain used is the one specified in the smb.conf - smb.conf(5) workgroupworkgroup + parameter.

      Convert a SID to a UNIX user id. If the SID - does not correspond to a UNIX user mapped by winbindd(8)winbindd(8) then the operation will fail.

      Convert a SID to a UNIX group id. If the SID - does not correspond to a UNIX group mapped by winbindd(8) then the operation will fail.

      winbindd(8) then + the operation will fail.

      -t

      Produce a list of domains trusted by the - Windows NT server winbindd(8)winbindd(8) contacts when resolving names. This list does not include the Windows NT domain the server is a Primary Domain Controller for. @@ -308,16 +344,18 @@ CLASS="COMMAND" >

      EXIT STATUS

      The wbinfo program returns 0 if the operation - succeeded, or 1 if the operation failed. If the winbindd(8) - winbindd(8) daemon is not working wbinfo

      VERSION

      SEE ALSO

      winbindd(8) - winbindd(8)

      AUTHOR

      The conversion to DocBook for Samba 2.2 was done - by Gerald Carter

      Unified Logons between Windows NT and UNIX using WinbindNext

      Chapter 15. Unified Logons between Windows NT and UNIX using Winbind

      Chapter 14. Unified Logons between Windows NT and UNIX using Winbind

      15.1. Abstract

      14.1. Abstract

      Integration of UNIX and Microsoft Windows NT through a unified logon has been considered a "holy grail" in heterogeneous @@ -104,7 +107,9 @@ CLASS="SECT1" >

      15.2. Introduction

      14.2. Introduction

      It is well known that UNIX and Microsoft Windows NT have different models for representing user and group information and @@ -156,7 +161,9 @@ CLASS="SECT1" >

      15.3. What Winbind Provides

      14.3. What Winbind Provides

      Winbind unifies UNIX and Windows NT account management by allowing a UNIX box to become a full member of a NT domain. Once @@ -196,7 +203,9 @@ CLASS="SECT2" >

      15.3.1. Target Uses

      14.3.1. Target Uses

      Winbind is targeted at organizations that have an existing NT based domain infrastructure into which they wish @@ -218,7 +227,9 @@ CLASS="SECT1" >

      15.4. How Winbind Works

      14.4. How Winbind Works

      The winbind system is designed around a client/server architecture. A long running

      15.4.1. Microsoft Remote Procedure Calls

      14.4.1. Microsoft Remote Procedure Calls

      Over the last two years, efforts have been underway +>Over the last few years, efforts have been underway by various Samba Team members to decode various aspects of the Microsoft Remote Procedure Call (MSRPC) system. This system is used for most network related operations between @@ -260,7 +273,28 @@ CLASS="SECT2" >

      15.4.2. Name Service Switch

      14.4.2. Microsoft Active Directory Services

      Since late 2001, Samba has gained the ability to + interact with Microsoft Windows 2000 using its 'Native + Mode' protocols, rather than the NT4 RPC services. + Using LDAP and Kerberos, a domain member running + winbind can enumerate users and groups in exactly the + same way as a Win2k client would, and in so doing + provide a much more efficient and + effective winbind implementation. +

      14.4.3. Name Service Switch

      The Name Service Switch, or NSS, is a feature that is present in many UNIX operating systems. It allows system @@ -338,7 +372,9 @@ CLASS="SECT2" >

      15.4.3. Pluggable Authentication Modules

      14.4.4. Pluggable Authentication Modules

      Pluggable Authentication Modules, also known as PAM, is a system for abstracting authentication and authorization @@ -385,7 +421,9 @@ CLASS="SECT2" >

      15.4.4. User and Group ID Allocation

      14.4.5. User and Group ID Allocation

      When a user or group is created under Windows NT is it allocated a numerical relative identifier (RID). This is @@ -409,7 +447,9 @@ CLASS="SECT2" >

      15.4.5. Result Caching

      14.4.6. Result Caching

      An active system can generate a lot of user and group name lookups. To reduce the network cost of these lookups winbind @@ -430,7 +470,9 @@ CLASS="SECT1" >

      15.5. Installation and Configuration

      14.5. Installation and Configuration

      Many thanks to John Trostel

      15.5.1. Introduction

      14.5.1. Introduction

      This HOWTO describes the procedures used to get winbind up and running on my RedHat 7.1 system. Winbind is capable of providing access @@ -512,7 +556,9 @@ CLASS="SECT2" >

      15.5.2. Requirements

      14.5.2. Requirements

      If you have a samba configuration file that you are currently using...

      15.5.3. Testing Things Out

      14.5.3. Testing Things Out

      Before starting, it is probably best to kill off all the SAMBA related daemons running on your server. Kill off all

      15.5.3.1. Configure and compile SAMBA

      14.5.3.1. Configure and compile SAMBA

      The configuration and compilation of SAMBA is pretty straightforward. The first three steps may not be necessary depending upon @@ -657,7 +707,7 @@ CLASS="PROMPT" >root# ./configure --with-winbind./configure

      15.5.3.2. Configure 14.5.3.2. Configure nsswitch.conf and the @@ -790,7 +842,9 @@ CLASS="SECT3" >

      15.5.3.3. Configure smb.conf

      14.5.3.3. Configure smb.conf

      Several parameters are needed in the smb.conf file to control the behavior of 

      [global]
-     <...>
+     <...>
      # separate domain and username with '+', like DOMAIN+username
      
      15.5.3.4. Join the SAMBA server to the PDC domain
      14.5.3.4. Join the SAMBA server to the PDC domain
      Enter the following command to make the SAMBA server join the 
 PDC domain, where root# /usr/local/samba/bin/net rpc join -S PDC -U Administrator/usr/local/samba/bin/net join -S PDC -U Administrator
      The proper response to the command should be: "Joined the domain 
@@ -907,7 +963,9 @@ CLASS="SECT3"
 >
      15.5.3.5. Start up the winbindd daemon and test it!
      14.5.3.5. Start up the winbindd daemon and test it!
      Eventually, you will want to modify your smb startup script to 
 automatically invoke the winbindd daemon when the other parts of 
@@ -1028,13 +1086,17 @@ CLASS="SECT3"
 >
      15.5.3.6. Fix the init.d startup scripts
      14.5.3.6. Fix the init.d startup scripts
      15.5.3.6.1. Linux
      14.5.3.6.1. Linux
      The 
      15.5.3.6.2. Solaris
      14.5.3.6.2. Solaris
      On solaris, you need to modify the 
 
      15.5.3.6.3. Restarting
      14.5.3.6.3. Restarting
      If you restart the 
      15.5.3.7. Configure Winbind and PAM
      14.5.3.7. Configure Winbind and PAM
      If you have made it this far, you know that winbindd and samba are working
 together.  If you want to use winbind to provide authentication for other 
@@ -1275,7 +1343,9 @@ CLASS="SECT4"
 >
      15.5.3.7.1. Linux/FreeBSD-specific PAM configuration
      14.5.3.7.1. Linux/FreeBSD-specific PAM configuration
      The 
      15.5.3.7.2. Solaris-specific configuration
      14.5.3.7.2. Solaris-specific configuration
      The /etc/pam.conf needs to be changed. I changed this file so that my Domain
 users can logon both locally as well as telnet.The following are the changes
@@ -1476,7 +1548,7 @@ dtsession auth required	/usr/lib/security/$ISA/pam_unix.so.1
 >I also added a try_first_pass line after the winbind.so line to get rid of
 annoying double prompts for passwords.
      Now restart your Samba & try connecting through your application that you
+>Now restart your Samba and try connecting through your application that you
 configured in the pam.conf.

      15.6. Limitations

      14.6. Limitations

      Winbind has a number of limitations in its current released version that we hope to overcome in future @@ -1498,7 +1572,7 @@ NAME="AEN2542">15.6. Limitations

    • Winbind is currently only available for - the Linux operating system, although ports to other operating + the Linux, Solaris and IRIX operating systems, although ports to other operating systems are certainly possible. For such ports to be feasible, we require the C library of the target operating system to support the Name Service Switch and Pluggable Authentication @@ -1517,7 +1591,8 @@ NAME="AEN2542">15.6. Limitations

      Currently the winbind PAM module does not take into account possible workstation and logon time restrictions - that may be been set for Windows NT users.

      • 15.7. Conclusion

      14.7. Conclusion

      The winbind system, through the use of the Name Service Switch, Pluggable Authentication Modules, and appropriate @@ -1570,7 +1647,7 @@ WIDTH="33%" ALIGN="right" VALIGN="top" >NextPassdb MySQL pluginImproved browsing in samba

      + winbindd

      winbindd

      winbindd

      Synopsis

      winbindd [-F] [-S] [-i] [-B] [-d <debug level>] [-s <smb config file>] [-n]

      [-F] [-S] [-i] [-B] [-d <debug level>] [-s <smb config file>] [-n]

      DESCRIPTION

      This program is part of the SambaThis program is part of the Samba(7) suite.

      /etc/group and then from the - Windows NT server. 

      passwd:         files winbind
-group:          files winbind
-

      The following simple configuration in the @@ -198,7 +192,7 @@ CLASS="FILENAME" >

      OPTIONS

      Specifies the location of the all-important - smb.confsmb.conf(5) file.

      • NAME AND ID RESOLUTION

      CONFIGURATION

      winbindd       daemon - is done through configuration parameters in the smb.conf(5) - smb.conf(5) file. All parameters should be specified in the [global] section of smb.conf.

      EXAMPLE SETUP

      /etc/nsswitch.conf       put the - following:

      passwd:     files winbind
-group:      files winbind
-

      In /etc/pam.d/* replace the - replace the auth auth lines with something like this: 

       lines with something like this:
+
      auth       required	/lib/security/pam_securetty.so
 auth       required	/lib/security/pam_nologin.so
 auth       sufficient	/lib/security/pam_winbind.so
-auth       required     /lib/security/pam_pwdb.so use_first_pass shadow nullok
-

      Note in particular the use of the sufficientsufficient + - keyword and the keyword and the use_first_pass

      smbpasswd -j DOMAIN -r PDC -U - Administratornet join -S PDC -U Administrator

      The username after the can be any Domain user that has administrator privileges on the machine. - Substitute your domain name for "DOMAIN" and the name of your PDC - for "PDC".

      Next copy /lib and pam_winbind.so - to pam_winbind.so + to /lib/security. A symbolic link needs to be @@ -624,19 +598,15 @@ CLASS="FILENAME" >/lib/libnss_winbind.so.1.

      Finally, setup a smb.confFinally, setup a smb.conf(5) containing directives like the - following: 

      [global]
 	winbind separator = +
@@ -647,11 +617,7 @@ CLASS="PROGRAMLISTING"
         winbind gid = 10000-20000
         workgroup = DOMAIN
         security = domain
-        password server = *
-

      Now start winbindd and you should find that your user and @@ -670,7 +636,7 @@ CLASS="COMMAND" >

      NOTES

      winbindd      :

      nmbdnmbd(8) must be running on the local machine for to work. winbindd - queries the list of trusted domains for the Windows NT server +> queries + the list of trusted domains for the Windows NT server on startup and when a SIGHUP is received. Thus, for a running winbindd

      SIGNALS

      SIGHUP

      Reload the smb.conf(5) - file and apply any parameter changes to the running +>Reload the smb.conf(5) file and + apply any parameter changes to the running version of winbindd. This signal also clears any cached user and group information. The list of other domains trusted by winbindd is also reloaded.

      FILES

      VERSION

      SEE ALSO

      nsswitch.conf(5), - samba(7), - wbinfo(1), - smb.conf(5), Samba(7), wbinfo(8), smb.conf(5)

      AUTHOR

      and winbindd - were written by Tim Potter.

      were + written by Tim Potter.

      The conversion to DocBook for Samba 2.2 was done - by Gerald Carter